WO2006131071A1

WO2006131071A1 - A service route control method

Info

Publication number: WO2006131071A1
Application number: PCT/CN2006/001239
Authority: WO
Inventors: Dongming Zhu; Hai Zhang; Xiaoqin Duan; Peng Zhang
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2005-06-07
Filing date: 2006-06-07
Publication date: 2006-12-14

Abstract

A service route control method, comprises the step: when a user transmitting/receiving the service, the routing policy decision point selects CS domain or IMS domain to provide the service for the user according to a routing decision assistance information. Through the method, the network can control the routing for the service flexibly according to the outing decision assistance information.

Description

Service routing control method

The present invention relates to the field of mobile communications, and in particular, to a service routing control method. Background of the invention

With the development of broadband networks, standards organizations such as 3GPP and 3GPP2 have launched IP-based Multimedia Subsystem (IMS) architectures, driven by multiple applications, with the goal of using a standardized open architecture in mobile networks. To achieve a wide range of multimedia applications. The IMS system consists of Call Session Control Fimction (CSCF) > Media Gateway Control Function (MGCF), Media Resource Function (MRF) and Home Subscriber Server (HSS). ) and other functional entities. The CSCF can be divided into three logical entities: a service CSCF (S-CSCF), a proxy CSCF (P-CSCF), and a query CSCF (I-CSCF). The S-CSCF is a service switching center of the IMS, and performs user registration management and session. Control, maintain session state, manage user information, generate billing information, etc.; P-CSCF is an access point for terminal users to access IMS, complete user access control, and complete two-way message forwarding between users and other IMS network nodes. Responsible for QoS control and security management, generating billing data, etc.; I-CSCF is responsible for interworking between IMS domains, managing the allocation of S-CSCF, hiding network topology and configuration, and generating billing data. The MGCF control gateway is used to implement interworking between the IMS network and other circuit switched (CS) networks; the MRF is used to provide media resources such as audio and video, codec and multimedia conference bridges. The HSS is the most important database for each user, and holds all the information related to the contract. It is used to support the processing of calls and sessions by various network entities, including: user identification, numbering and addressing information; user security information; The location information of the user, the description information of the user, and the like. There is an interface between the HSS and multiple entities in the network.

Since the structure of the IMS network is independent of the underlying bearer network, the 3GPP defined IMS The network can also be applied to other packet networks other than the 3GPP defined packet domain network, such as the packet network defined in 3GPP2, the LAN network, and the NGN network, etc., which realizes the independence from the user using the terminal type and the access network. Type independence.

Starting from the 3GPP el-6 release, 3GPP introduces non-3GPP access networks such as WLANs as access networks for 3GPP systems. Access to IMS systems through such access networks can provide features other than 3GPP access networks, such as: Relatively high access rate, relatively low tariff, etc. Therefore, in some cases, for example, in the case of WLAN coverage, the user will preferentially select such an access network to access the IMS service, which will appear as follows Situation: Some services (such as voice services) can be provided through the traditional CS domain network, and can also be provided through the IMS domain, and the user may register in both the CS domain and the IMS domain. At this time, when the user initiates/uses as the calling party In the case of a service, the network may decide which domain to provide the service to the calling user. When the user receives/uses the service as the called party, the network may decide which domain to provide the service to the called user.

Here, the service may be a voice service. When the network determines that the voice service is provided by the IMS domain to the user, the entity in the IMS domain needs to perform service control on the voice service of the user, and when the network decides to provide voice to the user by the CS domain. In the case of service, the entity of the CS domain controls the voice service of the user. The service may also be a supplementary service, such as call forwarding, call barring, etc., when the network decides to provide supplementary services to the user by the IMS domain, the entity in the IMS domain needs to be used by the user. The supplementary service performs service control. When the network decides to provide supplementary services to the user by the CS domain, the entity of the CS domain performs service control on the supplementary service of the user.

Further, the control for controlling the previous service by one field, at a certain time, it may be allowed to switch to another service domain to continue the _Q

At present, because the IMS domain has more flexible service scalability and more open network access, in most cases, it is inclined to judge whether the service used by the user in the CS domain needs to perform service control in the IMS domain. The services used by the user in the IMS domain continue to be controlled in the IMS domain. In order to achieve the above requirements, when the calling user initiates a service in the CS domain, the service initiated by the calling user in the CS domain needs to be firstly routed to the calling user's home IMS domain, and which end is used. The domain performs the service control judgment. Similarly, when the called user receives the service in the CS domain, it needs to firstly route the service received by the called user in the CS domain to the called user's home IMS domain, and finally use it. Which domain performs the judgment of business control.

In the existing 3GPP technical research report, TR 23.806 proposes a method for implementing caller service routing control when the user is simultaneously registered in the CS domain and the IMS domain. As shown in FIG. 1, the CS domain and the IMS domain are set. There is a Routing Policy Decision Point (RPDP) for decision routing connected to the CS domain GSM service control function (gsmSCF) and the IMS domain AS. Whether the service request is triggered from the CS domain, the service request is triggered to the gsmSCF, or the call service request from the IMS domain is triggered. After the service request is triggered to the AS, the gsmSCF/AS requests further routing decisions from the RPDP. On the other hand, the RPDP determines whether the service request of the calling user performs service control in the CS domain or the IMS domain according to the preference set by the user and the call policy of the operator.

At the same time, in the existing 3GPP technical research report, TR 23.806 also proposes a method when the user is simultaneously registered in the CS domain and the IMS domain. The method for implementing the routing control of the called service, as shown in FIG. 2, is provided between the CS domain and the IMS domain with an RPDP connected to the home location register (HLR) and the HSS for decision routing. Whether it is a route query request sent from the CS domain to the HLR or a route query request sent from the IMS domain to the HSS, the HLR/HSS requests further routing decisions from the RPDP, and the RPDP is based on the current registration status of the user in the two domains. And the current user-set preferences and the operator's call policy, and finally determine whether the called service is routed from the CS domain or the IMS domain to the user.

In the existing 3GPP technical research report, TR 23.806 proposes another method for implementing the routing control of the called service when the user is simultaneously registered in the CS domain and the IMS domain, and the scheme is similar to the foregoing scheme of the routing control of the calling service. As shown in FIG. 1, a routing policy decision point RPDP for determining a route connected to the CS domain gsmSCF and the IMS domain AS is set between the CS domain and the IMS domain. Whether it is from the CS domain for the service request of the called user, the service request is triggered to the gsmSCF; or the service request from the IMS domain for the called user, after the service request is triggered to the AS, the gsmSCF/AS will Further routing decisions are required to the RPDP, and the RPDP determines whether the service request for the called user is in the CS domain or the IMS based on the preferences set by the user and the operator's calling policy. Business control in the domain.

In summary, in the structure shown in FIG. 1, the service logic is executed according to the following steps to implement the primary and called side service route control:

Steps 1~2: The initial address message (IAM) from the external network or the call originator in the GSM network for the called user or the call setup message initiated by the calling user Setup When the MSC/GMSC arrives, the service logic is called.

In the CS domain, the gsmSCF queries the routing policy decision point RPDP for the routing policy of the calling or called user.

Step 3~6: For the calling service process, the RPDP decides to continue to control the service in a certain domain according to the stored preference setting of the calling party user and the call policy information of the operator; for the called service process, the RPDP goes according to the service logic. Query the HLR and the HSS to obtain the current registration status of the user in the CS domain and the IMS domain, and then the RPDP returns routing decision information to the gsmSCF based on the obtained registration status, the called user's preference setting, and the operator's call policy information, gsmSCF The MSC is controlled to route the call to the called user UE in the IMS domain or the CS domain according to the routing decision information.

Steps 7 to 12: When the IAM message or the INVITE message arrives at the IMS system, the same processing as steps 2 to 6 is performed, that is, the service logic is invoked; the AS of the IMS domain queries the RPDP for the calling or called user according to the service logic. Routing policy, for the calling service process, the RPDP decides to continue to control the service in a certain domain according to the stored preference setting of the calling party user and the call policy information of the operator. For the called service process, the RPDP queries the HLR according to the service logic. And the HSS, to obtain the current registration status of the user in the CS domain and the IMS domain, and then the RPDP returns routing decision information to the AS based on the obtained registration status, the preference of the called user, and the call policy information of the operator, and the AS according to the route The decision information controls the S-CSCF to route the call to the called user UE in the IMS domain or CS domain.

Although the above solution can implement service routing control between the CS domain and the IMS domain, the following disadvantages exist:

1. The network does not have the ability to make routing decisions based on the called service attributes, because within the current framework, the routing query request to the HLR/HSS has blocked the service attributes of the called service, such as the industry. Type of service, bearing requirements, etc.

2. The routing policy decision point in the network does not consider the main user terminal capability and the access network capability when performing routing, and cannot flexibly perform routing according to the changing terminal function and the newly added service of the access network. Summary of the invention

The present invention provides a service route control method, which enables a network to flexibly control traffic based on route decision assistance information.

In order to achieve the above object, the technical solution provided by the present invention is:

A service route control method, the method includes: when a user initiates/receives a service, the route policy decision point in the network selects, by the CS domain or the IMS domain, the service for the user according to the route decision assistance information.

The routing decision assistance information includes, but is not limited to, user terminal capability information, and/or access network capability information currently accessed by the user, and/or service attribute information.

The method further includes: setting a capability information and a routing comparison table; storing the user terminal capability information, and/or the access network capability information in the capability information and routing comparison table, and combining the predetermined routing with the user or the operator The corresponding preferred route determined by the policy; the specific method for selecting the routing policy decision point is: searching the comparison table according to the user terminal capability information of the current user and/or the access network capability information currently accessed by the user, determining the selection Routing. The capability information and the routing comparison table are set in the routing policy decision point or in a separate database that is interfaced with the routing policy decision point.

In the foregoing solution, the routing decision assistance information is service attribute information, where the service attribute information includes but is not limited to: service type, service QoS type, bit rate, delay, jitter, bit error rate, bit error rate, or Any combination of more than one attribute. The service attribute information is carried by a routing decision query initiated by the route query entity to the routing policy decision point in the network.

The method further includes: setting a routing table; storing, in the routing table, a service attribute, and a corresponding preferred route determined by a routing policy determined by a user or an operator; The specific method for selecting the policy decision point is as follows: After receiving the routing decision query request carrying the service attribute information, the routing policy decision point queries the routing table according to the service attribute information to obtain the selected route. The routing table is stored in a routing policy decision point or in a separate database that is interfaced with the routing policy decision point.

The routing decision assistance information is service attribute information and user terminal capability information, and/or access network capability information currently accessed by the user; the routing table further stores user terminal capability information, and/or the current user access The access network capability information is entered; the routing policy decision point further selects the service routing control by the CS domain or the IMS domain according to the user terminal capability information and/or the access network capability information currently accessed by the user.

In the above solution, the user terminal capability information and/or the access network capability information is stored in a presentation system server of the network or stored in a capability information management module; the routing policy decision point receives a routing decision query initiated by the network entity. After the request, the user terminal capability information and/or the access network capability information are obtained from the presence system server or the capability information management module.

The method for storing the user terminal capability information is: releasing, by the user terminal or a network entity that can learn the user terminal capability information, the user terminal capability information to the presentation system server or the capability information management module; or by presenting the system server or capability information The management module initiates the capability information query to obtain the user terminal capability information to the user terminal; or sets a database for storing the user terminal capability information, and the presence system server queries the database according to the user terminal identifier to obtain the user terminal capability information.

The method for storing the user terminal capability information is: the user terminal or the network entity capable of obtaining the user terminal capability information is advertised to the presence system server or the capability information management module; the time of the release is: when the new account is registered, or When a new user terminal is added under the same IP multimedia public identity, or when the terminal capability is updated, when the terminal is registered, or when the network requests, or according to the user/operator setting.

The method for storing the user terminal capability information is: setting a database for storing user terminal capability information; the database is set in an existing network entity, or is an independent network entity. The database is an independent network entity; then the interface between the database and the presentation system server is an existing network interface. Or a new interface defined according to an existing protocol, or a protocol interface customized for the operator.

The access network capability information storage method is: publishing, by the user terminal or the network entity, the access network capability information to the presence system server; or setting an access network capability database for storing the access network capability information, and presenting the system server according to the user The access network identifier and the cell identifier carried in the registration query the database to obtain the access network capability information.

The method for storing the access network capability information is: setting an access network capability database for storing access network capability information; the database is set in an existing network entity, or is an independent network entity. The database is an independent network entity; then the interface between the database and the presentation system server is an existing network interface, or a new interface defined according to an existing protocol, or an operator-defined protocol interface.

If the user terminal capability information or the access network capability information currently accessed by the user indicates that the service is not supported, the service is processed according to the failure process specified by the service itself, or is sent to the specific service according to the setting of the operator/user. Server processing.

The method further includes: the routing policy decision point obtaining the registration status of the called user in the CS domain and/or the IMS domain; the routing policy decision point according to the routing decision assistance information and the obtained called in the CS domain and/or the IMS domain Registration status, choose to provide services for the called user by CS domain or IMS domain.

In the above solution, the capability information management module is a device management server.

The service route control method provided by the invention has the following advantages and features:

1) The present invention utilizes an interface with a presence server (Presence server) or an enhanced capability information management module to implement the network's perception of user terminal capabilities and access network capabilities, ie, to the presence system server or the capability information management module. The capability information of the user terminal and the access network is provided, and when the network makes a routing decision, the related entity can obtain and perform routing according to the capability information.

2) The invention carries the service attribute information when the network entity initiates the routing decision query request message, so that the routing policy decision point can know the service attribute of the current call, thereby implementing the routing of the service according to the service attribute, and better satisfying the continuous Adding and changing new services to the transport network selection requirements. 3) When performing the service processing, the present invention can perform routing for the calling and called users according to the obtained user terminal and/or access network capability. Therefore, the user terminal and the access network with different capabilities can be selected for service routing. Moreover, it can be determined whether the user terminal or the access network capability supports the current service, and when the user terminal or the access network capability does not support the current service, the process of performing other corresponding processing on the user service is implemented.

4) When the routing decision is made, the present invention can also select a route in combination with the requirements of the user or the operator, can effectively improve the performance of the routing decision, better adapt to the complex service provision environment, and give the operator more flexible control. The method provided by the service also gives the user a more flexible way of selecting the way the service is provided. BRIEF DESCRIPTION OF THE DRAWINGS

1 is a schematic diagram of a prior art service route control method;

The figure is the second schematic diagram of the prior art service routing control method;

3 is a flowchart of a service route control method according to Embodiment 1 of the present invention;

4 is a flowchart of a service route control method according to Embodiment 2 of the present invention;

FIG. 5 is a flowchart of a service route control method according to Embodiment 3 of the present invention;

FIG. 6 is a flowchart of a service route control method according to Embodiment 4 of the present invention. Mode for carrying out the invention

The main idea of the service routing control method of the present invention is: when the primary/called user initiates/receives the service, the routing policy decision point in the network performs routing according to the obtained routing decision auxiliary information; further, when the called user receives the service The routing policy decision point in the network may also select to route the service to the called user by the CS domain or the IMS domain in combination with the obtained registration status of the called domain in the CS domain and/or the IMS domain.

Here, the routing decision assistance information is used to assist the network to perform service routing when performing service routing decision, and the routing decision assistance information includes but is not limited to: user terminal capability information and/or radio access network capability information, And/or business attribute information.

Here, the service attribute information includes but is not limited to: service type, service QoS type, ratio The rate, delay, jitter, bit error rate, bit error rate, or any combination of more than one attribute, the service attribute information is usually carried in a routing decision query message initiated by the routing query entity in the network to the routing policy decision point.

In the present invention, the user terminal capability information and the access network capability information may be pre-stored in the network, and there are mainly two implementation manners:

The first implementation is to register the capabilities of the user terminal and the capabilities of accessing the network into the presence system server.

Here, the capability of the user terminal may be released by the user terminal to the presence system server, or may be obtained by the presence system server to the user terminal; or may be published by the network entity instead of the user terminal to the presence system server, for example: when the user registers, The capabilities of the user terminal are registered by the S-CSCF to the presence system server. The network entity that can be registered with the presence system server instead of the user terminal refers to any entity that contacts the user terminal and is likely to know the user terminal information, including but not limited to: 3GPP AAA server, packet data gateway (PDG), HSS/HLR , S-CSCF, Mobile Switching Center (MSC), MSC Server, Visitor Location Register (VLR), Serving GPRS Support Node (SGSN), Gateway GPRS Support Node (GGSN), Gateway Mobile Location Center (GMLC)<, in these cases The capability information of the user terminal can be directly stored in the presence system server.

A database may also be set in the network to store the capability information of the user terminal. When the user terminal issues its own information to the presentation system server, the user terminal may provide the presentation system server with index information such as identification information and type information of the user terminal or the user, and present the system. The server uses the index information to query and obtain the capability information of the user terminal in the set database. The database can be set up separately, or it can be part of a CS domain network entity, an IMS network entity, or a presence system server. If it is set separately, the interface with the presentation system server can utilize the existing interface. In this case, the signaling content and parameters need to be extended; the interface of the presentation system server can also be a newly defined interface, and the specific implementation can adopt CAMEL. Application Part Protocol (CAP), Mobile Application Part Protocol (MAP), Remote Dial-In User Service Authentication Protocol (RADIUS), Diameter Protocol, Initial Session Protocol (SIP), or other carrier-defined protocols. The capability information of the user terminal that needs to be distributed to the presence system server includes, but is not limited to, the capability of the terminal to support VoIP, the wireless capability of the terminal, the service support capability of the terminal, and the processing capability of the terminal.

The capability information of the user terminal can be triggered to be distributed to the presence system server at the following time: when the new account is registered, when the user terminal is added under the same IP multimedia public identity (IMPU), when the terminal capability is updated, when the terminal is registered, and when the network is proposed Any time required, or according to user settings / operator settings.

The access network capability information may be published by the user terminal to the presence system server, or may be published by the network entity to the presence system server.

In the case that the network entity issues the access network capability information to the presence system server, when the user registers with the IMS domain, the user terminal carries the P-Access-Network-Info header field in the registration message, in the P-Access-Network. The -Info header field contains the access network type and the cell number. Other information can be used to search the access network capability database according to the access network type and the cell number. The database is newly added and can be set independently or combined with other network entities. Including, it is combined with the S-CSCF, and the specific AS is set up.

The P-CSCF, the S-CSCF, and the AS in the security domain in the IMS network can obtain related access network capability information, and the presentation system server can obtain the information as the AS. If the access network capability database is separately set, the interface with the presentation system server can utilize the existing interface. In this case, the signaling content and parameters need to be extended; or the newly defined interface can be used. Existing agreements, or other operator-defined agreements.

In the case that the user terminal sends the access network capability information to the presence system server, the user terminal directly issues the access network capability information to the presence system server, including but not limited to: access network type, access network wireless capability, access Network identification, cell identification. The access network capability database may be separately set to store the access network capability information, and the user terminal only needs to release the basic information such as the access network identifier and the cell identifier that the access system server accesses, and the presentation system server accesses according to the basic information. The network capability database is entered into the ff query.

The second implementation manner is to register the capability of the user terminal and the capability of accessing the network into a capability information management module for managing user terminal capabilities and accessing network capabilities. The capability information management module implements a function similar to the presentation system server, and has the capability of receiving the user terminal and the user terminal and the access network capability information sent by the network; and providing the corresponding capability information to the user terminal and the access network capability information query entity. The ability to actively acquire user terminal and access network capability information; has the ability to actively publish user terminals and access network capability information to network entities. The capability information management module can be independently set in the network or can be combined with other network entities, for example: Device Management Server defined by the Open Mobile Alliance (OMA), or HLR/ HSS is set up, etc. If the capability information management module is independently set, the entity that interfaces with the capability information management module may include: user terminal, 3GPP AAA server, PDG, HSS/HLR, S-CSCF, MSC, MSC Server, VLR, SGSN, GGSN, GMLC, etc. The corresponding interface protocol may be CAP, MAP, RADIUS, Diameter, SIP or other operator-defined protocols.

A detailed description of the service routing control method when a user initiates/receives a service call is described below in conjunction with a specific embodiment.

Embodiment 1:

Referring to Figure 3, Figure 3 shows the service routing control flow when calls from other networks are accessed from the CS domain of the local network. In this embodiment, the routing decision assistance information includes capability information of the user terminal and/or capability information of the access network, and/or service attribute information, and the capability of the user terminal and the capability of accessing the network are registered to the presentation system. The server or device management server specifically includes the following steps:

Step 31: When the call arrives at the gateway mobile switching center (GMSC) and needs to be routed to the called user, the GMSC initiates a routing query to the HLR;

Step 32: The HLR initiates a routing decision request to the routing policy decision point RPDP, and carries the registered state of the called user in the local domain, that is, the CS domain.

Step 33: According to the network operator's call policy, the RPDP may query the HSS for the current registration status of the called user in the IMS domain.

Step 34: The RPDP goes to the presence server to obtain the capability information of the user terminal and the access network capability information currently accessed by the user. Step 35: The RPDP performs routing decision according to the obtained user terminal capability information and the access network capability information, and the acquired registration status of the called user in the CS domain and the IMS domain. The decision result includes: routing the service from the CS domain to the called party. The user routes the service from the IMS domain to the called user, or because the user terminal capability information and the access network capability information indicate that the called service is not supported, the service is routed to the specific service server or the connection is directly returned to the calling user. The specific decision-making method is:

A comparison table of capability information and routing is pre-stored in the RPDP or a separate database, and several records are stored in the comparison table, and each record includes the following field information: user identifier, user preference, carrier call policy, user terminal The capability information, the access network capability information, and the corresponding routing decision result; when determining the preferred route, the routing may be further performed according to a routing decision policy preset by the user or the operator. Table 1 is a specific example of the capability information and routing comparison table.

Table I

The capability information and routing comparison table can be modified or added correspondingly according to the capabilities of the user terminal and the access network capability, which is very flexible and convenient;

In the current service call process, the RPDP determines, according to the registration status of the called user in the CS domain and the IMS domain, in which domain the called user has already registered, if the user has only made a note in one domain. If the user has already registered in the two domains, the RPDP may further query the capability information according to the obtained user terminal capability information and the access network capability information. The routing comparison table matches the corresponding routing route. If the user does not register in both domains, the RPDP can sign the inaccessible service according to the user in a certain domain, so that the routing decision result is to route the service call to Signed an unreachable domain for business control.

Step 36: The RPDP returns a routing decision response to the HLR, and informs the HLR which domain the called service should route to the user terminal; the notified route is the route finally selected in step 35; Step 37, the HLR returns a route query response to the GMSC. Carrying routing information determined according to the current routing decision for the GMSC to perform subsequent routing control.

Embodiment 2:

Figure 4: After receiving the service call, the mobile switching center of the network uses the gsmSCF and the PDP to be combined, and the presence system server or the device management server stores the user terminal capability information and the access network capability information, and the gsmSCF/RPDP is used as the routing policy decision point. The process of performing service route control includes the following steps:

Step 41: When the MSC receives the call service for the calling/called user, the MSC invokes the service logic, and the MSC performs a route query to the routing policy decision point gsmSCF/RPDP, and carries the service attribute information in the route query message;

Step 42: For the case that the service call is for the called user, the gsmSCF/RPDP queries the HLR for the current registration status of the called user in the CS domain; if the service call is initiated by the calling user, the step is omitted.

Step 43: For the case that the service call is for the called user, the gsmSCF/RPDP queries the HSS for the current registration status of the called user in the IMS domain. For the case where the service call is initiated by the calling user, the step is omitted.

Step 44: The gsmSCF/RPDP obtains the user terminal capability information of the master/called party and the access network capability information currently accessed by the master/called party from the presence system server or the device management server. Step 45: The gsmSCF/RPDP performs routing decision according to the obtained capability information and service attribute information. Further, for the case that the service call is for the called user, the gsmSCF/RPDP may also be based on the called user obtained in steps 42 and 43. The registration status of the CS domain and the IMS domain is used for routing decisions. The specific decision method may be: pre-storing a comparison table of capability information and routing in the gsmSCF/RPDP or a separate database, and storing a plurality of records in the comparison table, each record including the following field information: user terminal capability information, The network capability information and the corresponding routing result are selected; in the current service call, the gsmSCF/RPDP matches the obtained user terminal capability information and the access network capability information query capability information and the routing comparison table to match the corresponding routing route. Here, the comparison table may use the comparison table shown in Table 1;

Step 46: The gsmSCF RPDP returns the routing decision result to the MSC through the routing decision response, so that the MSC performs subsequent routing control on the call service according to the routing decision result.

When the method of the present invention uses the user's service attribute information, or the user's service attribute information and the user terminal capability information and/or the access network capability information, a comparison table of service attributes and route selections may be pre-stored in the network. The comparison table between the service attribute and the routing may be stored in the routing policy decision point, or may be stored in a separate database that is interfaced with the routing policy decision point. The comparison table of the service attribute and the routing may be referred to as a routing table, and the routing table includes at least: service attribute information, user terminal capability information, and/or access network capability information (optional), combined with the user or The preferred route determined by the operator's predetermined routing policy, that is, the routing decision result.

The user terminal capability information and the access network capability information can still be pre-stored in the network by using the two implementation methods described above.

After receiving the routing decision query requesting the service attribute information initiated by the network entity, the routing policy decision point obtains the user terminal capability information and/or the access network capability information from the presence system server or the capability information management module; The service attribute information, and/or the user terminal capability information and/or the access network capability information query the routing table to obtain a route selection. If the access network capability information currently accessed by the user or the called user terminal capability information indicates that the service is not supported, the service is processed according to the service failure process, or sent to a specific service server for processing. Embodiment 3:

Referring to FIG. 5, FIG. 5 is a flow chart of the call routing service when the call from the other IMS network arrives at the local network for routing query and the IMS domain accesses. In this embodiment, the routing decision assistance information includes the capability information of the user terminal. And/or capability information of the access network, and/or service attribute information, and the capability of the user terminal and/or the capability of accessing the network are registered in the presence system server or the device management server, and specifically includes the following steps:

Step 51: When an IMS call from another IMS network needs to be routed to the called user, the I-CSCF in the network where the called user is located initiates a route query to the HSS, and the route query message carries the service of the called user. Attributes;

Step 52: The HSS initiates a routing decision request to the RPDP, where the routing decision request carries the service attribute information of the called user, and the step may be implemented by using the extended MAP protocol. Optionally, the called user may be carried in the routing decision request. Registration status in this domain;

Step 53: The RPDP may select to go to the HLR to query the current registration status of the user in the CS domain. Step 54: If the user system capability information and/or the access network capability information are stored in the presentation system server or the device management server, the RPDP may select to go. The presence system server/or the device management server acquires user terminal capability information and/or access network capability information currently accessed by the user;

Step 55: The RPDP performs routing decision according to the obtained capability information and the registration status of the called user in the CS domain and the IMS domain, and the specific method is:

The routing table is pre-stored in the RPDP or a separate database, and several records are stored in the routing table, and each record may include the following field information: user identifier, user preference, carrier call policy, service attribute, user terminal Capability information (optional), access network capability information (optional), and corresponding routing decision results. Table 2 is a specific example of the routing table.

User identification user preference operator call service attribute user terminal capability (accessible network capability terminal routing decision strategy selection) End capability (optional) Result User A's preference preference for negative streaming media multimedia industry mode terminal (supports UTRAN) From IMS IMSI, cheaper and lighter network services, requiring VOIP in bandwidth IMS; supporting WLAN domain, passing 384 kbps with GSM voice service) WLAN routing User B's service quality guarantees the best session-type voice service dual-mode terminal (supports UTRAN; from CS domain IMSI priority service quality IMS in IMS; WLAN routing

Holding GSM voice service)

User C's service quality guarantees the best streaming media multimedia industry GSM terminal UTRAN; from CS domain IMSI priority traffic shield service, required bandwidth does not pass any access route

128kbps network registered in IMS

The RPDP queries the routing table according to the service attribute information carried in the routing decision request, and/or the user terminal capability information and/or the access network capability information obtained from the presence system server, and matches the corresponding routing route;

Step 56: The RPDP returns a routing decision response to the HSS, and notifies which domain the called service should be routed to the user; the route that is notified is the route finally selected in step 55;

Step 57: The HSS returns a route query response to the I-CSCF, and carries the routing information determined according to the current routing decision, so that the IMS performs subsequent route control.

If the user terminal capability information and the access network capability information indicate that the called service is not supported, the service needs to be processed according to the service unreachable process, or the service is routed to a specific service server, or the connection is directly returned to the calling user. .

Similarly, when the called user is in the CS domain, the routing decision process to the called CS domain is similar to the flow shown in Figure 5.

Embodiment 4:

Figure 6 shows that when the IMS domain receives a service call, the AS and RPDP are combined. The presence system server or the device management server stores the user terminal capability information and the access network capability information, and the AS RPDP is used as the routing policy decision point for routing. The process specifically includes the following steps:

Step 61: When the IMS network receives the call for the master/called party, the service logic is invoked, and the S-CSCF in the IMS network performs a route query to the AS/RPDP, and carries the service attribute information in the route query message; Step 62 When the service call is directed to the called user, the AS/RPDP queries the HLR for the current registration status of the called user in the CS domain. For the case where the service call is initiated by the calling user, this step Can be omitted.

Step 63: For the case that the service call is for the called user, the AS/RPDP queries the HSS for the registration status of the called user in the IMS domain. For the case where the service call is initiated by the calling user, this step may be omitted.

Step 64: The AS/RPDP obtains the capability information of the calling/called user terminal and/or the access network capability information currently accessed by the primary/called user from the presence system server or the device management server.

Step 65: The AS RJPDP performs routing decision according to the obtained capability information and service attribute information. Further, for the case that the service call is for the called user, the AS/RPDP may also be based on the called user obtained in steps 62 and 63 in the CS. The registration status of the domain and/or the IMS domain is used for the routing decision. The specific method may be the same as the process step 45 in FIG. 4, and is not repeated here;

Step 66: The AS/RPDP returns the routing decision result to the S-CSCF through the routing decision response, and the S-CSCF performs subsequent routing control on the call service according to the routing decision result.

In summary, the above description is only a preferred embodiment of the present invention and is not intended to limit the scope of the present invention.

Claims

Claim

A service route control method, characterized in that the method comprises:

When the user initiates/receives the service, the routing policy decision point in the network selects the CS domain or the IMS domain to provide services for the user according to the routing decision assistance information.

The method according to claim 1, wherein the routing decision assistance information includes but is not limited to: user terminal capability information, and/or access network capability information currently accessed by the user, and/or service attribute. information.

The method according to claim 1, wherein the routing decision assistance information is: user terminal capability information, and/or access network capability information currently accessed by the user.

The method according to claim 3, wherein the method further comprises: setting a capability information and a routing comparison table; storing the user terminal capability information in the capability information and routing comparison table, and/or The incoming network capability information, and the corresponding preferred route determined by the routing policy selected by the user or the operator;

The specific method for selecting the routing policy decision point is: searching the comparison table according to the user terminal capability information of the current user and/or the access network capability information currently accessed by the user, and determining the selected route.

The method according to claim 4, wherein the capability information and the routing reference table are set in a routing policy decision point or in a separate database that is interfaced with the routing policy decision point.

The method according to claim 1, wherein the routing decision assistance information is service attribute information, and the service attribute information includes but is not limited to: a service type, a service QoS type, a bit rate, a delay, Jitter, bit error rate, bit error rate, or any combination of more than one attribute.

The method according to claim 6, wherein the service attribute information is carried by a routing decision query initiated by the routing query entity in the network to the routing policy decision point.

8. The method of claim 7, wherein the method further comprises: setting a way a selection table; the routing parameter stores a service attribute, and a corresponding preferred route determined by a routing policy determined by a user or an operator;

The specific method for selecting the routing policy decision point is as follows: After receiving the routing decision query request carrying the service attribute information, the routing policy decision point queries the routing table according to the service attribute information to obtain the selected route.

The method according to claim 8, wherein the routing table is stored in a routing policy decision point or in a separate database that is interfaced with a routing policy decision point.

The method according to claim 8, wherein the routing decision assistance information is service attribute information and user terminal capability information, and/or access network capability information currently accessed by the user; the routing table Further storing user terminal capability information, and/or access network capability information currently accessed by the user;

The routing policy decision point further selects the service routing control by the CS domain or the IMS domain according to the user terminal capability information and/or the access network capability information currently accessed by the user.

The method according to claim 3 or 10, wherein the user terminal capability information and/or access network capability information is stored in a presentation system server of the network or stored in a capability information management module; After receiving the routing decision query request initiated by the network entity, the routing policy decision point obtains the user terminal capability information and/or the access network capability information from the presence system server or the capability information management module.

The method according to claim 11, wherein the method for storing the capability information of the user terminal is:

The user terminal capability information is issued by the user terminal or the network entity capable of knowing the user terminal capability information to the presentation system server or the capability information management module; or

The capability information query is initiated by the presence system server or the capability information management module to the user terminal to obtain the user terminal capability information; or

A database for storing user terminal capability information is set, and the presentation system server queries the database according to the user terminal identifier to obtain user terminal capability information.

The method according to claim 11, wherein the method for storing the user terminal capability information is: the user terminal or a network entity capable of knowing the user terminal capability information to the presentation system server or the capability information management module Release

The time of the release is: when the new account is registered, when the user terminal is added under the same IP multimedia public identity, or when the terminal capability is updated, when the terminal is registered, when the network is requested, or according to the user/operator setting. Any time.

The method according to claim 11, wherein the method for storing user terminal capability information is: setting a database for storing user terminal capability information; the database is set in an existing network entity, or A separate network entity.

The method according to claim 14, wherein the database is an independent network entity; and the interface between the database and the presentation system server is an existing network interface, or a new interface defined according to an existing protocol, Or customize the protocol interface for the operator.

The method according to claim 11, wherein the access network capability information storage method is:

The access network capability information is sent by the user terminal or the network entity to the presence system server; or the access network capability database for storing the access network capability information is set, and the access network identifier and the cell identifier carried by the system server according to the user registration are presented. Query the database to obtain access network capability information.

The method according to claim 1, wherein the method for storing access network capability information is: setting an access network capability database for storing access network capability information; In a network entity, or an independent network entity.

The method according to claim 17, wherein the database is an independent network entity; and the interface between the database and the presentation system server is an existing network interface, or a new interface defined according to an existing protocol, Or customize the protocol interface for the operator.

The method according to claim 3 or 10, wherein if the user terminal capability information or the access network capability information currently accessed by the user indicates that the service is not supported, the service is serviced according to the service. The failure process specified by itself is processed accordingly, or sent to a specific business server for processing according to the settings of the operator/user.

20. The method according to claim 1, 2, 3, 6 or 10, wherein the method further comprises: obtaining, by the routing policy decision point, the registration status of the called user in the CS domain and/or the IMS domain; The routing policy decision point is based on the routing decision assistance information and the obtained called in the CS domain and/or

The registration status of the IMS domain is selected to provide services for the called user by the CS domain or the IMS domain.

The method according to claim 11, wherein the capability information management module is a device management server.