CN1319350C - System and method for implementing route control - Google Patents

Abstract

The invention discloses a method for realizing routing control, which is applied in the routing control process including IMS domain and CS domain. The method includes setting routing policy decision points in advance, and setting routing policy information in the routing policy decision points; The query entity queries the current routing decision from the routing policy decision point; the routing policy decision point determines the current routing decision information according to the current routing policy information and the routing decision-related information stored in the CS/IMS domain; the routing policy decision point returns to the routing decision query entity The determined current routing decision information; the routing decision query entity completes subsequent routing control according to the routing decision information. At the same time, the invention also discloses a routing control system based on the above method. The invention solves the problem of routing control for routing query requests from CS domain and IMS domain.

Description

System and method for implementing routing control

technical field

The present invention relates to the technical field of communication, in particular to a system and method for realizing routing control.

Background technique

Starting from the third generation mobile communication standardization partnership project (3GPP) R5 stage, the universal mobile telecommunications system (UMTS) core network is divided into circuit switched (CS, Circuit Switched Domain) domain, packet switched (PS) domain and IP multimedia subsystem ( IMS), where the CS domain is used to provide users with circuit-type service connections, including mobile switching center (MSC) (composed of MSC server Server/circuit domain media gateway (CS-MGW)), gateway mobile switching center GMSC, interworking function (IWF). MSC is used to complete the switching and signaling control functions of circuit-switched services; GMSC is an MSC that completes the routing and addressing function of mobile users in a certain network, and can be set up together with MSC or separately; IWF is used to be closely related to MSC, Complete the intercommunication between the Public Land Mobile Network (PLMN) network and the Integrated Services Digital Network (ISDN), Public Switched Telephone Network (PSTN), and Public Data Network (PDN) networks (mainly complete the signaling conversion function), the specific functions are based on business It is different from the type of network.

PS Domain (Packet Switched Domain): used to provide users with packet-based service connections, including: General Packet Radio Service Support Node (GSN) and Border Gateway (BG). Among them, the GSN is used to complete the transmission of the packet of the packet service user, and the GSN includes a Serving General Packet Radio Service Support Node (SGSN) and a Gateway General Packet Radio Service Support Node (GGSN). The SGSN provides the connection between the core network and the Base Station Subsystem (BSS) and Radio Network Subsystem (RNS) in the wireless access system, completes functions such as mobility management and session management of packet data services, and manages the mobile station (MS) in mobile For mobile and communication services within the network, GGSN serves as the interface between the mobile communication system and other public data networks, and also has the function of querying location information. Both SGSN and GGSN provide billing information. BG is used to complete the intercommunication between the two GPRS networks to ensure the security of the network intercommunication.

In addition, the functional entities shared by the CS domain and the PS domain also include: Home Location Register (HLR)/Authentication Center (AuC): HLR completes user subscription data (Mobile Subscriber Integrated Services Digital Network Number (MSISDN), International Mobile Subscriber Identity Code ( IMSI), packet data protocol address (PDPADDRESS), contracted telecommunication services and supplementary services and their scope of application, etc.) and location information (mobile subscriber roaming number (MSRN), MSC/Visitor Location Register (VLR) number, SGSN number, Gateway Mobile Location Center (GMLC), etc.), AUC stores the user's authentication algorithm and key; others include VLR that processes various data information of visiting users, and stores the user equipment identifier International Mobile Equipment Identity (IMEI) Information equipment identification register (EIR) and short message center gateway MSC (SMS-GMSC/SMS IMSC), etc.

IMS (IP Multimedia Subsystem) is a subsystem superimposed on the existing packet domain in the wideband code division multiple access (WCDMA) network added in the 3GPP R5 stage. The packet domain is used as the upper layer control signaling and media transmission. Bearer channel, introduce the Session Initiation Protocol (SIP) protocol as a service control protocol, use the characteristics of SIP's simplicity, easy expansion, and convenient media combination, and provide rich multimedia services by separating service control from bearer control; the main functional entity in IMS Including Call Session Control Entity (CSCF) that controls functions such as user registration and session control, Application Server (AS) that provides various business logic control functions, Home Subscriber Server (HSS) that centrally manages user subscription data, and is used to implement and circuit The Media Gateway Control Function (MGCF)/IMS Multimedia Gateway (IM-MGW) for switching network interworking, the user accesses the IMS through the current proxy node P-CSCF, and the session and service trigger control and service control interaction with the AS are registered by it The local home domain service node S-CSCF completes.

The HSS in the IMS system is a superset of the HLR and can be functionally compatible with the HLR. However, due to factors such as the network construction process, the HSS and CS/PS HLR in the specific network are likely to be set up separately.

The IMS architecture defined by the 3GPP standard comprehensively solves key operational issues such as roaming billing, quality of service (QoS), and security guarantees that need to be solved in providing multimedia services under the IP bearer. Its architecture and ideas have been recognized by the industry. 3GPP2 , Advanced Network Telecommunications and Internet Converged Services and Protocols (TISPAN) have defined the corresponding IP multimedia network architecture and service system based on the 3GPP model and with reference. Communication system (UMTS) interworking (I-WLAN), fixed broadband access to IMS (FBI), and all-IP network (AIPN) for multiple access technologies. Users will be able to use a single multi-mode terminal according to their subscription Or multiple types of different terminals access the IMS via access networks of different access technologies to obtain unified multimedia services, including voice over IP (VoIP) services.

In addition, Mobile Number Portability (MNP, Mobile Number Portability) is a capability that allows users to change the contracted network without changing their MSISDN number. The main idea is to build a shared number portability between the different contracted networks The database (NPDB) records the user's current subscription network, and when each network determines the user's called route, the query to the NPDB is completed through an intelligent network or signaling relay to determine the user's current subscription network.

However, since MNP actually solves the problem of changing the ownership of a user and its identity, the ownership of the user and its identity at a certain moment is unique, but our current situation is different from this, and the user identity is in different networks. Domain (CS/IMS) sharing, users can use their terminals with different access technologies to access CS/IMS at the same time or only one of the CS/IMS according to their wishes, and the network needs to ensure that as long as the user is reachable in any network domain, Calls from other users can be received, or a network domain connection can be preferentially selected according to user wishes or operating policies when both domains are available. Since the user's access situation in different domains and the user's willingness or operation strategy are flexible, the current MNP is not completely suitable for solving this flexible policy-controlled routing decision-making problem.

Contents of the invention

In view of this, the object of the present invention is to provide a system and method for implementing routing control, so that when terminals using different access technologies access IMS or CS, they can be connected to other users according to preset policies. call.

A kind of method that realizes routing control that the present invention provides is realized like this:

A method for realizing routing control, applied to the routing control process including the Internet Multimedia Subsystem IMS domain and the circuit switching CS domain, pre-setting routing policy decision point (RPDP), and routing policy information is set in the routing policy decision point, The method also includes:

A. The routing decision query entity queries the current routing decision from the routing policy decision point;

B. The routing policy decision point determines the current routing decision information according to the current routing policy information and the routing decision-related information stored in the CS/IMS domain;

C. The routing policy decision point returns the determined current routing decision information to the routing decision query entity;

D. The routing decision query entity completes subsequent routing control according to the routing decision information.

The routing decision-related information in step B is obtained by the routing policy decision point from the HLR/HSS in the CS/IMS domain.

The routing policy decision point uses the MAP protocol to query the routing decision-related information from the home location register/home subscription server HLR/HSS of the CS/IMS domain, and the routing decision-related information is obtained by querying the mobile application part MAP at any time , or the MAP queries the user subscription data at any time to obtain it;

Alternatively, the Diameter protocol is used for communication between the HSS and the routing policy decision point, and the routing decision-related information uses Diameter user data request/user data response UDR/UDA operations, or Diameter user registration status query/user registration status response UAR/UAA Operation, or Diameter location information query/location information response LIR/LIA operation implementation.

The routing decision-related information in step B is pre-saved by the routing policy decision point.

Further include before step B:

The HLR/HSS actively updates the information related to the routing decision of the user in the CS/IMS domain saved by the routing strategy decision point through the interface between the HLR/HSS and the routing strategy decision point, then the information related to the routing decision from the HLR/HSS Information related to routing decisions in the CS/IMS domain stored by the routing policy decision point itself.

The HLR/HSS and the routing policy decision point interface use the MAP protocol to communicate and interact, and the information related to the routing decision is realized through the MAP location update operation and the MAP insertion/deletion user operation,

Or, the Diameter protocol is used for communication between the HSS and the routing policy decision point, and the information related to the routing decision of the user in the CS/IMS domain stored in the updated routing policy decision point is operated by Diameter server allocation request/server allocation response SAR/SAA , or Diameter update user subscription data request/update user subscription data response PPR/PPA operation, or Diameter subscription user data change request/subscribe user data change response SNR/SNA and notify user data change request/notify user data change response PNR/PNA The operation is realized.

The routing strategy query entity is the home location register HLR, the gateway mobile switching center GMSC or the short message gateway mobile switching center SMS-GMSC in the CS domain; or the home subscription server HSS and the service call session control function S-CSCF in the IMS domain .

When the routing decision query entity in step A is HLR/HSS, the routing decision query request further includes relevant information of the user in the CS/IMS domain required by RPDP for routing decision.

When the routing decision query entity is HLR or GMSC in the CS domain, step A includes:

A11, the CS domain GMSC receives the incoming call setup request, and sends a route query request to the HLR;

After A12, HLR receives this routing query request, determine query mode, if adopt direct query mode, then execute step A13, if adopt GMSC query mode, then execute step A14;

A13, the HLR directly sends a routing decision query request to the RPDP, and then performs step B;

A14. The HLR returns a routing query response to the GMSC, which contains the CAMEL subscription information T-CSI of the called user's mobile network enhancement logic on the called side; after receiving the routing query response, the GMSC triggers the called side according to the T-CSI For the CAMEL service, send a routing decision query request IDP to the RPDP serving as the global system for mobile communication service control function gsmSCF, and then perform step B.

The query method described in step A12 is pre-configured, or based on the CAMEL support capability carried by the GMSC in the routing query message, the user’s incoming call blocking service recorded in the HLR, the incoming call blocking service status determined by the operator, and the HLR’s It is determined by one or several factors in the local setting information.

When the direct query method is adopted in step A12, if the determined current routing decision is IMS domain routing connection, the current routing decision information in step C further includes a virtual roaming number pointing to the CS/IMS interworking gateway media gateway control function MGCF;

Step D includes:

D11, after the HLR receives the current routing decision information returned by the routing policy decision point, if the current routing decision is a CS domain routing connection, then perform step D12; if it is determined to be an IMS domain routing connection according to the routing decision, then perform step D13;

D12. HLR sends a request for providing a roaming number to the mobile switching center VMSC where the called user is currently visiting, and returns the roaming number returned by VMSC in the response of providing a roaming number to GMSC in the route query response, and GMSC routes the call according to the roaming number Go to the VMSC where the called party is located, and end this process;

D13. The HLR returns the virtual roaming number pointing to the CS/IMS interworking gateway MGCF provided by the RPDP in the current routing decision information to the GMSC in the route query response, and the GMSC routes the call to the MGCF according to the virtual roaming number and the MGCF continues The routing connection of the IMS domain is performed, and this process ends.

When the GMSC query method is adopted in step A12, if the current routing decision is an IMS domain routing connection, the current routing decision information in step C further includes: a redirection number pointing to the CS/IMS interworking gateway MGCF;

Then step D includes:

D21. After the GMSC receives the current routing decision information, if the current routing decision is a CS domain routing connection, then perform step D22, and if the current routing decision is an IMS domain routing connection, then perform step D23;

D22. The GMSC initiates a route query request to the HLR to suppress the CAMEL subscription information on the called side; after the HLR receives the route query request, it sends a request to provide a roaming number to the VMSC where the called user is currently located, and returns the VMSC in a response to provide a roaming number The roaming number of the user is returned to the GMSC in the routing query response, and the GMSC will route the call to the VMSC where the called party is located, and end this process;

D23. The GMSC routes the call to the MGCF according to the redirection number, and the MGCF continues routing in the IMS domain, and ends this process.

When the routing decision query entity is an SMS-GMSC in the CS domain, step A includes:

After A21, the SMS-GMSC receives the termination short message, it sends a short message routing query request to the HLR;

A22. After receiving the short message routing query request, the HLR directly sends a routing decision query request to the RPDP.

The current routing decision determined in the step B is an IMS domain routing connection or a CS domain routing connection; if it is an IMS domain routing connection, the current routing decision information in the step C further includes returning the address information of the CS/IMS short message interworking gateway to the HLR;

Step D includes:

D31, after the HLR receives the current routing decision information returned by the routing policy decision point, if the current routing decision is a CS domain routing connection, then perform step D32; if it is determined to be an IMS domain routing connection according to the routing decision, then perform step D33;

D32. The HLR returns the VMSC address information to the SMS-GMSC in the short message routing query response, and the SMS-GMSC routes the termination short message to the VMSC where the called party is located, and ends this process;

D33. HLR returns the address information of the CS/IMS SMS interworking gateway returned by RPDP in the current routing decision information to the SMS-GMSC in the short message routing query response, and the SMS-GMSC routes the termination short message to the CS/IMS SMS interworking gateway And the CS/IMS short message interworking gateway continues to perform intercommunication and short message routing processing in the IMS domain.

When the routing decision query entity is the HSS or S-CSCF in the IMS domain, step A includes:

A31. After receiving the IMS service request sent to the user in this domain, the query call session control function I-CSCF sends a route query request to the HSS;

A32. The HSS judges the query method. If it is determined to use the direct query method to complete the cross-domain routing control, then perform step A33. If it determines to use the S-CSCF query method to complete the cross-domain routing control, then perform step A34;

A33. The HSS sends a routing decision query request to the RPDP, and performs step B;

A34. The HSS returns a routing query response to the I-CSCF, which contains the S-CSCF domain name allocated for the called user or the S-CSCF capability requirement information required for the I-CSCF to complete the S-CSCF allocation;

A35. After receiving the query response, the I-CSCF forwards the IMS service request to the S-CSCF corresponding to the S-CSCF domain name assigned to the called user or determined according to the S-CSCF capability requirement information. The IMS service trigger data in the subscription data is used for service triggering, and the IMS service request is forwarded to the RPDP as the application server AS as a routing decision query request, and step B is performed.

The query method described in step A32 is judged according to the local setting information of the HSS, or

When the routing query request in step A31 further includes the service attributes and related information carried by the I-CSCF in the routing query message extension, the query method in step A32 is based on the local setting information of the HSS and/or in the routing query message It is judged by the business attributes and related information carried by the extension.

When step A32 determines that the direct query method is used to complete the cross-domain routing control, if the current routing decision determined in step B is CS domain routing connection, the current routing decision information in step C includes: CS/IMS interworking gateway MGCF domain name,

Step D includes:

D41. After the HSS receives the current routing decision information, if the current routing decision is a CS domain routing connection, then perform step D42, and if it is determined to be an IMS domain routing connection according to the routing decision, then perform step D43;

D42. The HSS returns the domain name of the CS/IMS interworking gateway MGCF returned by the RPDP to the I-CSCF as the S-CSCF domain name in the route query response, and the I-CSCF forwards the IMS service request to what it regards as the S-CSCF MGCF, and the MGCF continues routing in the CS domain, ending this process;

D43. The HSS returns the S-CSCF domain name or the S-CSCF capability requirement information required by the I-CSCF to complete the S-CSCF assignment to the I-CSCF in the route query response, and the I-CSCF forwards the IMS service request to the specified destination. the S-CSCF, and the S-CSCF continues to complete the triggering of the IMS service and the subsequent routing control in the IMS, and ends this procedure.

When step A32 determines that the cross-domain routing control is completed by means of direct query, and the current routing decision determined in step B is CS domain routing connection, the current routing decision information in step C includes: a link pointing to the CS/IMS interworking gateway MGCF E.164 number,

Then step D includes:

D51. After the HSS receives the current routing decision information, if the current routing decision is CS domain routing connection, then execute step D52;

D52. The HSS inserts the E.164 number pointing to the CS/IMS interworking gateway MGCF in the routing decision information into the AS that will be triggered in the user's current business processing through the update user data operation. At the same time, the HSS inserts the S-CSCF domain name or The S-CSCF capability requirement information required by the I-CSCF to complete the S-CSCF allocation is returned to the I-CSCF in the route query response; the I-CSCF forwards the IMS service request to the S-CSCF determined thereby, and the S-CSCF performs The IMS service is triggered, and the IMS service request is routed to the MGCF through the egress gateway control function BGCF under the control of the above-mentioned AS, and the MGCF continues to perform routing control in the CS domain, and ends this process.

When step A32 determines to use the S-CSCF query method to complete the cross-domain routing control,

If the current routing decision determined in step B is CS domain routing connection, the current routing decision information in step C includes: an E.164 number pointing to the CS/IMS interworking gateway MGCF, then the routing policy decision point in step C is directed to the routing The steps for the decision query entity to return the determined current routing decision information include: the routing policy decision point modifies the request uniform locator in the IMS service request received from the S-CSCF as a routing decision query request to point to the CS/IMS interworking gateway E.164 number of MGCF, and send IMS service request to S-CSCF;

If the current routing decision determined in step B is a CS domain routing connection, the step in which the routing policy decision point in step C returns the determined current routing decision information to the routing decision query entity includes: the routing policy decision point is incorrect and received from the S-CSCF Modify the request uniform locator in the IMS service request as the routing decision query request, and send the IMS service request to the S-CSCF.

Step D includes:

D61. After the S-CSCF receives the current routing decision information, if the current routing decision is a CS domain routing connection, then execute step D62, and if it is determined to be an IMS domain routing connection according to the routing decision, then execute step D63;

D62. The S-CSCF routes the IMS service request to the MGCF via the BGCF according to the E.164 number in the modified request uniform locator pointing to the CS/IMS interworking gateway MGCF in the IMS service request returned by the RPDP of the AS, and the MGCF continues Perform routing in the CS domain;

D63. The S-CSCF continues to complete subsequent IMS service triggering and routing in the IMS according to the unmodified request uniform locator in the IMS service request returned by the RPDP of the AS.

A kind of system that realizes routing control provided by the present invention is realized like this:

A system for realizing routing control, including: HSS/HLR, routing policy decision point RPDP and routing control entity, wherein, HSS/HLR is connected with RPDP and routing control entity,

HSS/HLR is used to save IMS/CS user subscription data and user current status/location information, and provide RPDP with user information in the IMS/CS domain; obtain current routing decision information directly from RPDP according to the routing query request of the routing control entity, and Provide the routing information determined according to the routing decision information to the routing control entity, or return the routing query result information to the routing control entity according to the user subscription data and the user's current status/location information;

RPDP, when receiving the routing decision query request from the routing control entity or HSS/HLR, use the current routing strategy saved by itself and the called user information in the HSS/HLR to determine the current routing decision information, and send the current routing decision information Return to routing control entity or HSS/HLR;

The routing control entity is configured to send a routing query request to the HSS/HLR, and/or send a routing decision query request to the RPDP, and perform routing control according to the routing query result information returned by the HSS/HLR or the current routing decision information returned by the RPDP.

The routing control entity is the GMSC or the CSCF of the IMS domain.

The RPDP further includes an interface with the operation support system OSS, which is used to receive the operator's operation signal, and add, delete, query, save and modify the policy information saved by itself.

The RPDP further includes an interface with the user, which is used for receiving user operation signals, and adding, deleting, querying, saving and modifying the policy information saved by itself.

After the HSS/HLR receives the routing query request from the routing control entity, it is further used to determine the query mode. If it is a direct query mode, it directly obtains the current routing decision information from the RPDP and provides it according to the routing information determined by the routing decision information. to the routing control entity, otherwise, return the routing query result information to the routing control entity according to the user subscription data and the user's current state/location information.

The query method is preset, or according to the CAMEL support capability carried by the routing decision query entity in the routing query message, or the service type and related information of the IMS service request carried in the query message, or HLR/HSS It is determined by one or several factors in the user's incoming call blocking operation equipment stored in the user's account, the state of the incoming call blocking service determined by the operator, or the local setting information of the HLR/HSS.

The routing control entity is further configured to expand and carry the service attribute and related information of the received IMS service request in the routing query message sent to the HSS, for the HSS to use as a basis for selecting a routing decision query mode.

When the routing control entity is a GMSC, the GMSC is connected to the RPDP, and communicates through the CAP protocol interface of the CAMEL application part,

The GMSC is further used to: trigger the CAMEL service on the called side according to the CAMEL subscription information provided by the HLR in the routing query result information, and send a routing decision query request to the RPDP, and then perform routing according to the current routing decision information determined by the RPDP;

When the routing control entity is a CSCF, the CSCF further includes a query CSCF and a serving CSCF, the serving CSCF is connected to the RPDP, and communicates through a session initiation protocol (SIP) protocol interface,

Querying the CSCF is further used to: determine the serving CSCF according to the serving CSCF domain name provided by the HLR in the route query result information or the serving CSCF capability requirement information required for allocating the serving CSCF, and route the IMS service request to the serving CSCF;

The serving CSCF is further used to: trigger the IMS called side service according to the IMS service trigger information in the user subscription data, and send a routing decision query request to the RPDP, and then perform routing according to the current routing decision information determined by the RPDP.

The HLR/HSS and the RPDP communicate using the MAP protocol, and/or the HSS and the RPDP communicate using the Diameter protocol.

Another system for implementing routing control provided by the present invention includes: HLR, routing policy decision point RPDP, and SMS-GMSC in the CS domain, wherein the HLR is connected to the SMS-GMSC and RPDP respectively, wherein,

SMS-GMSC, after receiving the terminating short message from the originating side of the short message, sends a short message routing query request to the HLR, and routes the terminating short message according to the routing information returned by the HLR;

HLR sends a routing decision query request to RPDP according to the received short message routing query request, and determines and returns routing information to SMS-GMSC according to the routing decision information from RPDP;

RPDP is used to determine the current routing decision information by using the current routing strategy saved by itself and the called user information in the CS/IMS domain according to the routing decision query request of the HLR, and return the current routing decision information to the HLR.

The route information returned by the HLR to the SMS-GMSC is the address information pointing to the CS/IMS short message interworking gateway, or the address information of the VMSC where the user is currently located.

The present invention provides a method that when a user chooses to use terminals of different access technologies to access IMS or CS, according to a certain strategy and whether the user is accessible in different domains, it is determined as the service that both CS/IMS can provide. An enhanced cross-domain routing control system and method for connection routing when called.

Through the present invention, cross-domain routing control can be realized as required in different network application environments, and cross-domain routing control for short message services widely used in circuit domains can be provided, which improves the service experience of users and further promotes Application of CS, WLAN and IMS networks.

Description of drawings

Fig. 1 is a schematic flow chart of the method for realizing cross-routing control in the present invention

Figure 2a is a schematic diagram of the system architecture proposed by the present invention;

FIG. 2b is a schematic diagram of a networking embodiment of a system for realizing cross-routing control in the present invention;

FIG. 3 is a schematic flow diagram of Embodiment 1 for realizing the method of the present invention;

Fig. 4 is a schematic flow diagram of Embodiment 2 for realizing the method of the present invention;

FIG. 5 is a schematic flow diagram of Embodiment 3 for realizing the method of the present invention;

FIG. 6 is a schematic flow diagram of Embodiment 4 for realizing the method of the present invention;

FIG. 7 is a schematic flow diagram of Embodiment 5 for realizing the method of the present invention;

Fig. 8 is a schematic diagram of another specific networking based on the method of the present invention;

FIG. 9 is a schematic flowchart of an embodiment of implementing the method of the present invention based on FIG. 8 .

Detailed ways

The main idea of the method of the present invention is: pre-setting routing policy decision point, and routing policy information is set in routing policy decision point, routing decision query entity inquires current routing decision to routing policy decision point; Routing policy decision point is based on current routing policy information , and the routing decision-related information stored in the CS/IMS domain determine the current routing decision information; the policy decision point returns the determined current routing decision information to the routing decision query entity; the routing decision query entity completes subsequent routing control according to the routing decision.

Referring to shown in Fig. 1, the method that the present invention realizes cross-routing control comprises the following steps:

Step 101: The routing decision query entity queries the routing policy decision point for the current routing decision.

Step 102: The routing policy decision point determines the current routing decision according to the current routing policy information and the information related to the routing decision obtained from the HLR/HSS.

Moreover, there may be many ways to determine the current routing strategy, and the present invention does not limit it here, and only a certain way of determining the strategy is exemplified below. For example, when the user is only available in one domain of IMS or CS, all incoming calls are selected to be connected in this user's reachable domain; According to factors such as user/network settings or combination time, CS or IMS can be used to connect first, or it can be forced to connect in CS or IMS according to user/network settings or combination time, regardless of the current availability status of the user in the two domains.

Step 103: The routing policy decision point returns the determined current routing decision information to the routing decision query entity.

Step 104: The routing decision query entity completes subsequent routing control according to the routing decision information.

The aforementioned routing policy query entity is an entity that can directly obtain routing decision information from a routing policy decision point. Therefore, the routing policy query entity can be the HLR/HSS in the CS/IMS domain, or the routing control entity in the CS/IMS domain, such as the routing control entity in the IMS domain is CSCF (including querying CSCF (I-CSCF) and service CSCF (S-CSCF)), the routing control entity in the CS domain is GMSC or SMS-GMSC, etc.

If the routing policy query entity is HLR or HSS, that is: after the HLR/HSS receives the routing query message from the network node, it directly sends a routing decision query request to the routing policy decision point, thereby obtaining the called routing decision determined by the routing policy decision point information, the present invention refers to this method of querying routing decisions as a direct query method, correspondingly, other query methods are called indirect query methods, and sending routing decision query requests for different network entities can also be called GMSC, SMS- GMSC or CSCF query method.

For the non-direct query mode, its routing query is implemented in this way: network entities such as GMSC, SMS-GMSC or CSCF send a routing query request to the HLR, and the HLR sends a routing query response to the network entity after receiving the routing query request; After receiving the response, the entity sends a routing decision query request to the RPDP, and obtains routing decision information from the RPDP.

In addition, the present invention can also support the above two query methods at the same time. The specific idea is: after the HLR/HSS receives the routing query request sent by the routing control entity, it judges which query method to use. If the direct query method is adopted, it directly sends a routing decision query request to the RPDP, and obtains routing decision information from the RPDP. Then send the routing information determined according to the routing decision information to the routing control entity, and the routing control entity performs routing control accordingly; if the indirect query method is used, send a routing query response to the routing control entity that initiated the routing query and return the routing query result The routing information is directly inquired from the RPDP, and the routing query node obtains the routing decision information from the RPDP, and then performs routing connection according to the routing decision information. In addition, if there is a pre-established connection between the routing control entity and the RPDP, the communication can be performed directly through the pre-established connection, or the routing control entity can use the customer application (CAMEL ) User subscription information triggers CAMEL services, or triggers IMS services based on IMS domain service trigger information, and then establishes a service connection with RPDP to realize communication with RPDP; it can also communicate through other wired or wireless methods.

FIG. 2 is a system architecture proposed by the present invention for simultaneously supporting the above two query methods.

Referring to Fig. 2a, the system of the present invention includes HSS/HLR, RPDP and routing control entity. Wherein, the RPDP is connected with the routing control entity and the HSS/HLR that needs to perform routing decision query, and the routing control entity is connected with the HSS/HLR. Moreover, when the routing control entity is a CSCF, the RPDP is connected to a serving CSCF (S-CSCF) in the CSCF.

HSS/HLR is used to save IMS/CS user subscription data and user current status information, and provide RPDP with user information in the IMS/CS domain; and determine the query method according to the routing query request of the routing control entity, and directly according to the query method Obtain the current routing decision information from RPDP and provide the routing information determined according to the routing decision information to the routing control entity, or return the routing query result information, and the routing control entity will directly query RPDP.

RPDP, when receiving the routing decision query request from the routing control entity or HSS/HLR, use the current routing strategy saved by itself and the called user information in the HSS/HLR to determine the current routing decision information, and send the current routing decision information Return to routing control entity or HSS/HLR. RPDP can be implemented in one physical entity, and can also be implemented by a combination of different physical entities in the case of supporting the combination of various functions.

The routing control entity is used to send a routing query request to HSS/HLR; and when it needs to directly query RPDP, send a routing decision query request to RPDP through an established connection, or directly receive HLR/HSS to determine according to routing decision information Routing information; Finally, routing control is performed according to the current routing decision information received or the routing information determined by the HLR/HSS according to the routing decision information.

Of course, if the connection between RPDP and the routing control entity is not established, then further, the routing control entity can trigger the CAMEL service on the called side according to the CAMEL subscription information provided by the HSS/HLR, or trigger the IMS domain service triggering information according to the HSS. business, establish a connection with RPDP.

In addition, the basis for judging which query method HLR adopts is: the pre-agreed method, or the support capability for CAMEL carried by the routing control entity GMSC in the routing query message, or the user's incoming call blocking service recorded locally by the HLR, or determined by the operator. The incoming call blocking service status, or one or more information in the local setting information of the HLR is determined.

Judging by this query method, if the routing control entity GMSC does not support CAMEL network conditions or the user currently has an active inbound blocking service or an inbound blocking service determined by the operator, it conflicts with the CAMEL service according to the original CS business logic relationship. In the case of the above situation, the HLR directly completes the routing decision query, and provides a CS/IMS cross-domain routing control solution in the above case.

The basis for determining which query method the HSS adopts is: a pre-agreed method, or one or more of the service attributes and related information carried by the I-CSCF in the routing query message extension and the local setting information of the HSS.

Through the judgment of this query method, for IMS service requests that need to be processed differently according to the specific information in the service request, the S-CSCF query method can be used, so that cross-domain routing control based on the incoming call attribute (service request type) can be realized need.

Figure 2b shows a specific embodiment of the system implementing the present invention. The network structure provided by this embodiment includes HSS, HLR, RPDP, GMSC, SMS-GMSC, I-CSCF/S-CSCF/AS. RPDP includes RPDP business logic, Global System for Mobile Communications Service Control Function (gsmSCF), Spanning Tree Protocol (STP), and AS logic function modules. RPDP business logic is used to store routing policies, make logical judgments, and forward data between HLR and HSS; gsmSCF is used to establish CAMEL service connections with GMSC and realize signaling interaction of CAMEL application part with GMSC; STP is used for Establish a connection with the GMSC to realize the signaling interaction with the Mobile Application Part (MAP) between the GMSC; the X-CSCF includes the I-CSCF and the S-CSCF, which are connected to each other through the Mw interface based on the IMS standard SIP protocol, and the AS in the RPDP implements The signaling connection with the S-CSCF in the X-CSCF realizes the SIP signaling interaction with the S-CSCF.

Among them, HSS is connected with RPDP business logic through interface 8, connected with I-CSCF in X-CSCF through interface 7, and connected with other ASs through interface 10; HLR is connected with RPDP business logic through interface 6, and connected with RPDP middle The STP in RPDP is connected to SMS-GMSC through interface 12 and the GMSC through interface 4; the STP in RPDP is connected to GMSC through interface 3a, the gsmSCF in RPDP is connected to GMSC through interface 5, and the AS in RPDP is connected to GMSC through interface 9 The S-CSCF is connected; the S-CSCF is connected to other ASs through an interface 11 . At the same time, the RPDP service logic provides an interface 13 to the operation support system (OSS) and an interface 14 to users. The SMS-GMSC receives the termination short message from the CS domain through the interface 3, the GMSC receives the call establishment request from the CS domain through the interface 1, and the I-CSCF receives the IMS service request from the IMS domain through the interface 2.

The technical solution of the present invention will be described in detail below in conjunction with the accompanying drawings and specific embodiments.

Since the current routing method can be CS domain or IMS domain, for the call/session of CS/IMS domain, the routing policy decision point can finally determine the route in the CS domain, or determine the route in the IMS domain, in the following embodiments , both show the processing of these two different situations, and at the same time, for the convenience of description, routing decision 1 and routing decision 2 are used to distinguish these two situations.

Referring to Fig. 2 and Fig. 3 below, it is explained that for a call request in the CS domain, the HLR judges and uses the GMSC query routing decision-making method to complete the process of cross-domain routing control. The concrete process of this embodiment is as follows:

Step 301: After receiving an incoming call establishment request through interface 1, the GMSC in the CS domain sends a route query request to the HLR through interface 4.

Steps 302-303: After the HLR receives the routing query request, according to the support capability for CAMEL carried by the GMSC in the routing query message, the locally recorded user incoming blocking service and/or the operator's determined incoming blocking service status and One or more factors in the local settings of the HLR judge and decide to use the GMSC query routing decision-making method to complete the cross-domain routing control, so return the routing query response to the GMSC through interface 4, which contains the called side CAMEL subscription information of the called user ( T-CSI).

Steps 304-305: After receiving the routing query response, the GMSC triggers the CAMEL service on the called side according to the T-CSI, establishes a service connection with the RPDP, and sends a routing decision query request (IDP) to the RPDP as the gsmSCF through interface 5.

Steps 306-308: After receiving the IDP, the RPDP serving as the gsmSCF interacts with the HLR and HSS to query the relevant information of the user in the CS and IMS respectively through interface 6 and interface 8 according to the current routing strategy, and obtains the information according to the query. The relevant information and the current policy determine the routing decision.

Steps 309-310: When the determined routing decision is IMS routing (referred to as routing decision 1 in the figure), the RPDP as the gsmSCF sends a CONNECT message to the GMSC through interface 5, which contains a modification pointing to the CS/IMS interworking gateway MGCF. Send the number; the GMSC executes routing decision 1 according to the redirected number, routes the call to the MGCF and the MGCF continues the routing in the IMS domain, and ends this process.

Steps 311-317: When the routing decision is to continue routing at the CS (referred to as routing decision 2 in the figure), RPDP as gsmSCF sends a CONTINUE message through interface 5 to instruct GMSC to continue routing according to the original called number, and GMSC executes accordingly Routing decision 2: initiate a route query request to suppress the called side CAMEL subscription information (suppress T-CSI) to the HLR through interface 4; Send a request to provide a roaming number, and return the roaming number returned by the VMSC in the response to provide a roaming number, and return the routing query response returned through interface 4 to the GMSC, and the GMSC will route the call to the called VMSC accordingly.

Referring to Fig. 2 and Fig. 4 below, it is a schematic flow chart illustrating how the HLR judges and completes the routing control by directly querying the routing decision-making method for a call request in the CS domain.

Referring to Fig. 4, the concrete processing procedure of the present embodiment is as follows:

Steps 400-401: After receiving the incoming call setup request through interface 1, the GMSC in the CS domain sends a route query request to the HLR through interface 4.

Steps 402 to 403: According to one or more of the CAMEL support capability carried by the GMSC in the routing query message, the locally recorded user incoming blocking service, the incoming calling blocking service status determined by the operator, and the local setting of the HLR, the HLR Based on these factors, it is judged that the cross-domain routing control is completed by directly querying the routing decision method, so the routing decision query request is directly sent to the RPDP through interface 6.

Steps 404-407: After receiving the routing decision query request, the RPDP can optionally interact with the HLR and HSS through interface 6 and interface 8 to query the relevant information of the user in the CS and IMS according to the needs of the current routing strategy. The information and the current policy are determined and returned to the HLR through the interface 6 for routing decisions.

Steps 408-410: When the determined routing decision is IMS routing (referred to as routing decision 1 in the figure), the HLR returns the virtual roaming number pointing to the CS/IMS interworking gateway MGCF in the routing query response to the RPDP to it. GMSC, GMSC executes routing decision 1 accordingly, routes the call to the MGCF and the MGCF continues routing in the IMS domain, and ends this process.

Steps 411-415: When the routing decision is to continue routing in the CS (referred to as routing decision 2 in the figure), the HLR sends a roaming number request to the VMSC where the called user is currently located according to the RPDP instruction to continue routing in the CS, and sends the VMSC a roaming number request. The roaming number returned in the response of providing the roaming number is returned to the GMSC in the route query response, and the GMSC executes routing decision 2 accordingly, and routes the call to the VMSC where the called party is located.

FIG. 5 is a schematic flow diagram of the HSS judging that the S-CSCF query routing decision-making method is used to complete the cross-domain routing control for the service connection request in the IMS domain.

Referring to Figure 5, the specific process of this embodiment is as follows:

Step 501: The I-CSCF in the IMS domain receives the IMS service request sent to the user in the local domain, and sends a route query request to the HSS. Optionally, the I-CSCF may expand the service attributes and related information carried in the route query message.

Steps 502-503: The HSS decides to use the S-CSCF query routing decision-making method to complete the cross-domain routing control according to the business attributes and related information carried in the routing query message expanded by the I-CSCF, and/or the local settings of the HSS and other factors. Therefore, in the returned routing query response, the S-CSCF domain name allocated for the called user or the S-CSCF capability requirement information required by the I-CSCF to complete the S-CSCF allocation is returned to the I-CSCF.

Steps 504-506: I-CSCF determines and forwards the IMS service request to the S-CSCF assigned to the user, and the S-CSCF triggers the service according to the IMS service trigger data in the user subscription data, and sends the route to RPDP as the AS Decision query request (forwarded IMS service request).

Steps 507-509: After receiving the routing decision query request, the RPDP as the AS optionally interacts with the HLR and the HSS to query the relevant information of the user in the CS and IMS according to the needs of the current routing policy, and according to the relevant information obtained through the query, And/or the information carried in the S-CSCF routing decision query request (forwarded IMS service request) and the current policy determine the routing decision.

Steps 510-511: When the determined routing decision is routed at CS (referred to as routing decision 1 in the figure), RPDP as the AS modifies the request uniform locator in the IMS service request returned to the S-CSCF to a pointing CS /IMS interworking gateway MGCF's E.164 number, based on which the S-CSCF executes routing decision 1, routes the IMS service request to the MGCF through the egress gateway control function (BGCF), and the MGCF continues routing in the CS domain.

Steps 512-513: When the routing decision is to continue routing in the IMS (referred to as routing decision 2 in the figure), RPDP as the AS does not modify the request uniform locator in the IMS service request returned to the S-CSCF, and the S-CSCF Based on this, the CSCF executes routing decision 2, continues to trigger the subsequent IMS service, and then routes the IMS service request to the P-CSCF accessed by the user.

FIG. 6 shows a flow diagram of the IMS incoming call, the HSS judges that the cross-domain routing control is completed by directly querying the routing decision mode, and the control mode 1.

Step 601: The I-CSCF in the IMS domain receives the IMS service request sent to the user in the local domain, and sends a route query request to the HSS. Optionally, the I-CSCF can expand the service attributes and related information carried in the route query message.

Steps 602-603: The HSS decides to use the direct query routing decision-making method to complete the cross-domain routing control according to the business attributes and related information carried in the routing query message extension carried by the I-CSCF, and/or the local settings of the HSS and other factors. Send a routing decision query request to RPDP.

Steps 604-607: Step RPDP receives the routing decision query request, and optionally interacts with the HLR and HSS to query the relevant information of the user in the CS and IMS according to the current routing strategy, and obtains the relevant information and the current strategy according to the query. Determine and return routing decisions to the HSS.

Steps 608-610: When the determined routing decision is routing in the CS (referred to as routing decision 1 in the figure), RPDP returns a domain name of the CS/IMS interworking gateway MGCF to the HSS, and the HSS uses it as the domain name of the S-CSCF in routing The query response is returned to the I-CSCF, and the I-CSCF executes routing decision 1 accordingly, forwards the IMS service request to the MGCF which it regards as the S-CSCF, and the MGCF continues routing in the CS domain.

Steps 611-613: When the routing decision is to continue routing in the IMS (referred to as routing decision 2 in the figure), RPDP returns a corresponding instruction to the HSS, and the HSS returns the S-CSCF domain name to the I-CSCF in the routing query response accordingly. CSCF and I-CSCF execute routing decision 2 accordingly, forward the IMS service request to the S-CSCF, and the S-CSCF continues to complete the IMS service trigger and then routes the call to the P-CSCF accessed by the user.

FIG. 7 is a flow chart diagram of the second control mode for an IMS incoming call, and the HSS judges that the cross-domain routing control is completed by directly querying the routing decision mode. The difference between this embodiment and the previous embodiment mainly lies in the way of executing the routing decision.

Referring to Fig. 7, the specific processing procedure of this embodiment is as follows:

Step 701: The I-CSCF in the IMS domain receives the IMS service request sent to the user in the local domain, and sends a routing query request to the HSS. Optionally, the I-CSCF can expand the service attributes and related information carried in the routing query message.

Steps 702-703: The HSS decides to use the direct query routing decision-making method to complete the cross-domain routing control according to the business attributes and related information carried in the routing query message extended by the I-CSCF, and/or the local settings of the HSS and other factors. Send a routing decision query request to RPDP.

Steps 704-706: After receiving the routing decision query request, the RPDP can optionally interact with the HLR and HSS to query the relevant information of the user in the CS and IMS according to the current routing strategy, and determine the relevant information according to the query and the current strategy. routing decisions.

Steps 707-713: RPDP returns the determined routing decision information to the HSS. When the determined routing decision is routing in CS (referred to as routing decision 1 in the figure), the routing decision information includes a CS/IMS interworking gateway The E.164 number of MGCF, HSS inserts it into the AS that will be triggered in the current service processing of the user through the operation of updating user data, and at the same time, regardless of whether the routing decision is made in CS routing or IMS routing, HSS will - The CSCF domain name is returned to the I-CSCF in the route query response, based on which the I-CSCF forwards the IMS service request to the S-CSCF, and the S-CSCF triggers the IMS service, triggering the HSS to insert data when the routing decision is CS routing AS.

Steps 714-716: When the determined routing decision is routing at the CS (referred to as routing decision 1 in the figure), after the S-CSCF triggers the IMS service, the AS assigns the request uniform locator in the service request according to the data inserted by the HSS Modify it to the E.164 number pointing to the CS/IMS interworking gateway MGCF, and return the service request to the S-CSCF, and under the control of the above-mentioned AS, the S-CSCF will The IMS service request is routed to the MGCF via the BGCF, and the MGCF continues routing in the CS domain.

Steps 717-719: When the routing decision is to continue routing in the IMS (referred to as routing decision 2 in the figure), after the S-CSCF triggers the IMS service, the AS uniformly locates the request in the service request according to the data inserted by the HSS No modification is made to the character, and the service request is returned to the S-CSCF, and the S-CSCF continues to complete the triggering of the IMS service and then routes the call to the P-CSCF accessed by the user.

In addition, FIG. 8 is a schematic diagram of a specific networking based on the above method of the present invention.

Referring to FIG. 8 , the networking architecture of this embodiment includes: HLR, routing policy decision point RPDP and SMS-GMSC in the CS domain, wherein the HLR is connected to the SMS-GMSC and RPDP respectively.

The SMS-GMSC, after receiving the termination short message from the originating side of the short message, sends a short message routing query request to the HLR. The HLR is used to send a routing decision query request to the RPDP according to the received short message routing query request, and determine and return routing information to the SMS-GMSC according to the routing decision information from the RPDP. RPDP is used to determine the current routing decision information by using the current routing strategy saved by itself and the called user information in the CS/IMS domain according to the routing decision query request of the HLR, and return the current routing decision information to the HLR. In addition, the routing information returned by the HLR to the SMS-GMSC may be address information pointing to the CS/IMS short message interworking gateway or the address information of the VMSC where the user is currently located.

FIG. 9 is a schematic flow diagram of the short message in the circuit domain, and the HLR querying the routing decision to complete the cross-domain routing control.

Referring to Figure 9, the specific process of this embodiment is as follows:

Step 901: The short message gateway MSC SMS-GMSC in the CS domain receives the termination short message, and sends a short message routing inquiry request to the HLR.

Step 902: the HLR directly sends a routing decision query request to the RPDP;

Steps 903-906: After receiving the routing decision query request, the RPDP can optionally interact with the HLR and HSS to query the relevant information of the user in the CS and IMS according to the current routing policy, and determine the relevant information according to the query and the current policy. And return the current routing decision to the HLR.

Steps 907-909: When the determined routing decision is IMS routing (routing decision 1), RPDP returns the address information pointing to the CS/IMS short message interworking gateway to the HLR, and the HLR returns it to the SMS- The GMSC and the SMS-GMSC execute routing decision 1 accordingly, routing the terminated short message to the CS/IMS short message interworking gateway, and the CS/IMS short message interworking gateway continues the interworking and short message routing processing in the IMS domain.

Steps 910-912: When the routing decision is to continue routing in the CS (routing decision 2), the RPDP instructs the HLR to continue routing in the CS, and the HLR returns the VMSC address information to the SMS-GMSC in the short message routing query response accordingly, and the SMS- Based on this, the GMSC executes routing decision 2, and routes the terminating short message to the VMSC where the called party is located.

The present invention provides a method that when a user chooses to use terminals of different access technologies to access IMS or CS, according to a certain strategy and whether the user is accessible in different domains, it is determined as the service that both CS/IMS can provide. An enhanced cross-domain routing control system and method for connection routing when called, the system and method take into account the requirements for adapting to different network application environments, as well as the requirements for cross-domain routing control of CS/IMS other types of service requests.

Claims (32)

1. A method for realizing routing control, which is applied in the routing control process including the Internet Multimedia Subsystem IMS domain and the circuit switching CS domain, is characterized in that the routing policy decision point RPDP is preset, and is set in the routing policy decision point Routing policy information, the method also includes the following steps: A. The routing decision query entity queries the current routing decision from the routing policy decision point; B. The routing policy decision point determines the current routing decision information according to the current routing policy information and the routing decision-related information stored in the CS/IMS domain; C. The routing policy decision point returns the determined current routing decision information to the routing decision query entity; D. The routing decision query entity completes subsequent routing control according to the routing decision information. 2. The method according to claim 1, wherein the information related to the routing decision in step B is obtained by the routing policy decision point from the Home Location Register/Home Subscription Server (HLR/HSS) of the CS/IMS domain. 3. The method according to claim 2, wherein the routing policy decision point uses the Mobile Application Part MAP protocol to query routing decision-related information from the HLR/HSS in the CS/IMS domain, and the routing decision-related information It is obtained by using the MAP query operation at any time, or the MAP query user subscription data operation at any time; Alternatively, the Diameter protocol is used for communication between the HSS and the routing policy decision point, and the routing decision-related information uses Diameter user data request/user data response UDR/UDA operations, or Diameter user registration status query/user registration status response UAR/UAA Operation, or Diameter location information query/location information response LIR/LIA operation implementation. 4. The method according to claim 1, characterized in that the routing decision-related information in step B is pre-saved by the routing policy decision point. 5. The method according to claim 4, further comprising: before step B: The HLR/HSS actively updates the information related to the routing decision of the user in the CS/IMS domain saved by the routing strategy decision point through the interface between the HLR/HSS and the routing strategy decision point, then the information related to the routing decision from the HLR/HSS Information related to routing decisions in the CS/IMS domain stored by the routing policy decision point itself. 6. The method according to claim 5, characterized in that, the HLR/HSS and the routing policy decision point interface use the MAP protocol to communicate and interact, and the routing decision-related information is updated through the MAP location update operation, MAP insertion/deletion User actions are implemented, Or, the Diameter protocol is used for communication between the HSS and the routing policy decision point, and the information related to the routing decision of the user in the CS/IMS domain stored in the updated routing policy decision point is operated by Diameter server allocation request/server allocation response SAR/SAA , or Diameter update user subscription data request/update user subscription data response PPR/PPA operation, or Diameter subscription user data change request/subscribe user data change response SNR/SNA and notify user data change request/notify user data change response PNR/PNA The operation is realized. 7. The method according to claim 1, wherein the routing policy query entity is a Home Location Register (HLR), a Gateway Mobile Switching Center (GMSC) or a Short Message Gateway Mobile Switching Center (SMS-GMSC) in the CS domain; or an IMS domain The Home Subscription Server HSS and the Serving Call Session Control Function S-CSCF. 8. The method according to claim 2, characterized in that, when the routing decision query entity in step A is HLR/HSS, the routing decision query request further includes the CS/IMS information required by RPDP for routing decision. information about the domain. 9. The method according to claim 1, wherein when the routing decision query entity is an HLR or GMSC in the CS domain, step A includes: A11, the CS domain GMSC receives the incoming call setup request, and sends a route query request to the HLR; After A12, HLR receives this routing query request, determine query mode, if adopt direct query mode, then execute step A13, if adopt GMSC query mode, then execute step A14; A13, the HLR directly sends a routing decision query request to the RPDP, and then performs step B; A14. The HLR returns a routing query response to the GMSC, which contains the CAMEL subscription information T-CSI of the called user's mobile network enhancement logic on the called side; after receiving the routing query response, the GMSC triggers the called side according to the T-CSI For the CAMEL service, send a routing decision query request IDP to the RPDP serving as the global system for mobile communication service control function gsmSCF, and then perform step B. 10. The method according to claim 9, characterized in that the query method in step A12 is pre-configured, or based on the CAMEL support capability carried in the route query message by the GMSC and the user's incoming call recorded in the HLR It is determined by one or several factors in the blocking service, the status of the incoming call blocking service determined by the operator, and the local setting information of the HLR. 11. The method according to claim 9, wherein when the direct query method is adopted in step A12, if the determined current routing decision is an IMS domain routing connection, the current routing decision information in step C further includes points to CS /Virtual roaming number of IMS Interworking Gateway Media Gateway Control Function MGCF; Step D includes: D11, after the HLR receives the current routing decision information returned by the routing policy decision point, if the current routing decision is a CS domain routing connection, then perform step D12; if it is determined to be an IMS domain routing connection according to the routing decision, then perform step D13; D12. HLR sends a request for providing a roaming number to the mobile switching center VMSC where the called user is currently visiting, and returns the roaming number returned by VMSC in the response of providing a roaming number to GMSC in the route query response, and GMSC routes the call according to the roaming number Go to the VMSC where the called party is located, and end this process; D13. The HLR returns the virtual roaming number pointing to the CS/IMS interworking gateway MGCF provided by the RPDP in the current routing decision information to the GMSC in the route query response, and the GMSC routes the call to the MGCF according to the virtual roaming number and the MGCF continues The routing connection of the IMS domain is performed, and this process ends. 12. The method according to claim 9, wherein when the GMSC query method is adopted in step A12, if the current routing decision is IMS domain routing connection, the current routing decision information in step C further includes : point to the redirection number of the CS/IMS interworking gateway MGCF; Then step D includes: D21. After the GMSC receives the current routing decision information, if the current routing decision is a CS domain routing connection, then perform step D22, and if the current routing decision is an IMS domain routing connection, then perform step D23; D22. The GMSC initiates a route query request to the HLR to suppress the CAMEL subscription information on the called side; after the HLR receives the route query request, it sends a request to provide a roaming number to the VMSC where the called user is currently located, and returns the VMSC in a response to provide a roaming number The roaming number of the user is returned to the GMSC in the routing query response, and the GMSC will route the call to the VMSC where the called party is located, and end this process; D23. The GMSC routes the call to the MGCF according to the redirection number, and the MGCF continues routing in the IMS domain, and ends this process. 13. The method according to claim 1, wherein when the routing decision query entity is an SMS-GMSC in the CS domain, step A includes: After A21, the SMS-GMSC receives the termination short message, it sends a short message routing query request to the HLR; A22. After receiving the short message routing query request, the HLR directly sends a routing decision query request to the RPDP. 14. The method according to claim 13, wherein the current routing decision determined in step B is IMS domain routing connection or CS domain routing connection; if it is IMS domain routing connection, the current routing decision information in step C Further comprising returning the address information of the CS/IMS short message interworking gateway to the HLR; Step D includes: D31, after the HLR receives the current routing decision information returned by the routing policy decision point, if the current routing decision is a CS domain routing connection, then perform step D32; if it is determined to be an IMS domain routing connection according to the routing decision, then perform step D33; D32. The HLR returns the VMSC address information to the SMS-GMSC in the short message routing query response, and the SMS-GMSC routes the termination short message to the VMSC where the called party is located, and ends this process; D33. HLR returns the address information of the CS/IMS SMS interworking gateway returned by RPDP in the current routing decision information to the SMS-GMSC in the short message routing query response, and the SMS-GMSC routes the termination short message to the CS/IMS SMS interworking gateway And the CS/IMS short message interworking gateway continues to perform intercommunication and short message routing processing in the IMS domain. 15. The method according to claim 1, wherein when the routing decision query entity is the HSS or S-CSCF in the IMS domain, step A includes: A31. After receiving the IMS service request sent to the user in this domain, the query call session control function I-CSCF sends a route query request to the HSS; A32. The HSS judges the query method. If it is determined to use the direct query method to complete the cross-domain routing control, then perform step A33. If it determines to use the S-CSCF query method to complete the cross-domain routing control, then perform step A34; A33. The HSS sends a routing decision query request to the RPDP, and performs step B; A34. The HSS returns a routing query response to the I-CSCF, which contains the S-CSCF domain name allocated for the called user or the S-CSCF capability requirement information required for the I-CSCF to complete the S-CSCF allocation; A35. After receiving the query response, the I-CSCF forwards the IMS service request to the S-CSCF corresponding to the S-CSCF domain name assigned to the called user or determined according to the S-CSCF capability requirement information. The IMS service trigger data in the subscription data is used for service triggering, and the IMS service request is forwarded to the RPDP as the application server AS as a routing decision query request, and step B is performed. 16. The method of claim 15, wherein: The query method described in step A32 is judged according to the local setting information of the HSS, or When the routing query request in step A31 further includes the service attributes and related information carried by the I-CSCF in the routing query message extension, the query method in step A32 is based on the local setting information of the HSS and/or in the routing query message It is judged by the business attributes and related information carried by the extension. 17. The method according to claim 15, characterized in that when step A32 determines that the cross-domain routing control is completed by means of direct inquiry, if the current routing decision determined in step B is CS domain routing connection, then the The current routing decision information includes: the domain name of the CS/IMS interworking gateway MGCF, Step D includes: D41. After the HSS receives the current routing decision information, if the current routing decision is a CS domain routing connection, then perform step D42, and if it is determined to be an IMS domain routing connection according to the routing decision, then perform step D43; D42. The HSS returns the domain name of the CS/IMS interworking gateway MGCF returned by the RPDP to the I-CSCF as the S-CSCF domain name in the route query response, and the I-CSCF forwards the IMS service request to what it regards as the S-CSCF MGCF, and the MGCF continues routing in the CS domain, ending this process; D43. The HSS returns the S-CSCF domain name or the S-CSCF capability requirement information required by the I-CSCF to complete the S-CSCF assignment to the I-CSCF in the route query response, and the I-CSCF forwards the IMS service request to the specified destination. the S-CSCF, and the S-CSCF continues to complete the triggering of the IMS service and the subsequent routing control in the IMS, and ends this procedure. 18. The method according to claim 15, characterized in that when step A32 determines that the cross-domain routing control is completed by means of direct inquiry, and the current routing decision determined in step B is CS domain routing connection, then in step C The current routing decision information includes: an E.164 number pointing to the CS/IMS interworking gateway MGCF, Then step D includes: D51. After the HSS receives the current routing decision information, if the current routing decision is CS domain routing connection, then execute step D52; D52. The HSS inserts the E.164 number pointing to the CS/IMS interworking gateway MGCF in the routing decision information into the AS that will be triggered in the user's current business processing through the update user data operation. At the same time, the HSS inserts the S-CSCF domain name or The S-CSCF capability requirement information required by the I-CSCF to complete the S-CSCF allocation is returned to the I-CSCF in the route query response; the I-CSCF forwards the IMS service request to the S-CSCF determined thereby, and the S-CSCF performs The IMS service is triggered, and the IMS service request is routed to the MGCF through the egress gateway control function BGCF under the control of the above-mentioned AS, and the MGCF continues to perform routing control in the CS domain, and ends this process. 19. The method according to claim 15, characterized in that when step A32 determines that cross-domain routing control is completed by means of S-CSCF query, If the current routing decision determined in step B is CS domain routing connection, the current routing decision information in step C includes: an E.164 number pointing to the CS/IMS interworking gateway MGCF, then the routing policy decision point in step C is directed to the routing The steps for the decision query entity to return the determined current routing decision information include: the routing policy decision point modifies the request uniform locator in the IMS service request received from the S-CSCF as a routing decision query request to point to the CS/IMS interworking gateway E.164 number of MGCF, and send IMS service request to S-CSCF; If the current routing decision determined in step B is a CS domain routing connection, the step in which the routing policy decision point in step C returns the determined current routing decision information to the routing decision query entity includes: the routing policy decision point is incorrect and received from the S-CSCF Modify the request uniform locator in the IMS service request as the routing decision query request, and send the IMS service request to the S-CSCF. 20. The method according to claim 19, wherein step D comprises: D61. After the S-CSCF receives the current routing decision information, if the current routing decision is a CS domain routing connection, then execute step D62, and if it is determined to be an IMS domain routing connection according to the routing decision, then execute step D63; D62. The S-CSCF routes the IMS service request to the MGCF via the BGCF according to the E.164 number in the modified request uniform locator pointing to the CS/IMS interworking gateway MGCF in the IMS service request returned by the RPDP of the AS, and the MGCF continues Perform routing in the CS domain; D63. The S-CSCF continues to complete subsequent IMS service triggering and routing in the IMS according to the unmodified request uniform locator in the IMS service request returned by the RPDP of the AS. 21. A system for implementing routing control, characterized in that it includes: HSS/HLR, routing policy decision point RPDP and routing control entity, wherein HSS/HLR is connected to RPDP and routing control entity, HSS/HLR is used to save IMS/CS user subscription data and user current status/location information, and provide RPDP with user information in the IMS/CS domain; obtain current routing decision information directly from RPDP according to the routing query request of the routing control entity, and Provide the routing information determined according to the routing decision information to the routing control entity, or return the routing query result information to the routing control entity according to the user subscription data and the user's current status/location information; RPDP, when receiving the routing decision query request from the routing control entity or HSS/HLR, use the current routing strategy saved by itself and the called user information in the HSS/HLR to determine the current routing decision information, and send the current routing decision information Return to routing control entity or HSS/HLR; The routing control entity is configured to send a routing query request to the HSS/HLR, and/or send a routing decision query request to the RPDP, and perform routing control according to the routing query result information returned by the HSS/HLR or the current routing decision information returned by the RPDP. 22. The system according to claim 21, wherein the routing control entity is a GMSC or a CSCF of the IMS domain. 23. The system according to claim 21, characterized in that the RPDP further includes an interface with the operation support system OSS, which is used to receive operator operation signals from operators, and to add, delete, and query the policy information stored by itself , Save and Modify. 24. The system according to claim 21, wherein the RPDP further includes an interface with the user, for receiving user operation signals, and adding, deleting, querying, saving and modifying the policy information saved by itself. 25. The system according to claim 21, characterized in that, after the HSS/HLR receives the routing query request from the routing control entity, it is further used to determine the query mode, and if it is a direct query mode, it directly obtains the current routing information from the RPDP. The routing decision information and the routing information determined according to the routing decision information are provided to the routing control entity, otherwise, the routing query result information is returned to the routing control entity according to the user subscription data and the user's current status/location information. 26. The system according to claim 21, wherein the query method is preset, or according to the CAMEL support capability carried by the routing decision query entity in the routing query message, or the CAMEL capability carried in the query message One or several factors of the service type requested by the IMS service and its related information, or the user's incoming call blocking service stored in the HLR/HSS, the state of the incoming call blocking service determined by the operator, or the local setting information of the HLR/HSS decided. 27. The system according to claim 26, wherein the routing control entity is further configured to extend and carry the service attribute and related information of the received IMS service request in the routing query message sent to the HSS, The HSS is used as the basis for selecting the routing decision query mode. 28. The system according to claim 21, characterized in that, when the routing control entity is GMSC, GMSC is connected to RPDP, and communicates through the CAMEL application part CAP protocol interface, The GMSC is further used to: trigger the CAMEL service on the called side according to the CAMEL subscription information provided by the HLR in the routing query result information, and send a routing decision query request to the RPDP, and then perform routing according to the current routing decision information determined by the RPDP. 29. The system according to claim 21, wherein when the routing control entity is a CSCF, the CSCF further includes a query CSCF and a serving CSCF, and the serving CSCF is connected to the RPDP through a session initiation protocol (SIP) interface communication, Querying the CSCF is further used to: determine the serving CSCF according to the serving CSCF domain name provided by the HLR in the route query result information or the serving CSCF capability requirement information required for allocating the serving CSCF, and route the IMS service request to the serving CSCF; The serving CSCF is further used to: trigger the IMS called side service according to the IMS service trigger information in the user subscription data, and send a routing decision query request to the RPDP, and then perform routing according to the current routing decision information determined by the RPDP. 30. The system according to claim 21, characterized in that HLR/HSS and RPDP use MAP protocol for communication, and/or HSS and RPDP use Diameter protocol for communication. 31. A system for implementing routing control, characterized in that it includes: HLR, routing policy decision point RPDP, and SMS-GMSC in the CS domain, wherein the HLR is connected to the SMS-GMSC and RPDP respectively, wherein, SMS-GMSC, after receiving the terminating short message from the originating side of the short message, sends a short message routing query request to the HLR, and routes the terminating short message according to the routing information returned by the HLR; HLR sends a routing decision query request to RPDP according to the received short message routing query request, and determines and returns routing information to SMS-GMSC according to the routing decision information from RPDP; RPDP is used to determine the current routing decision information by using the current routing strategy saved by itself and the called user information in the CS/IMS domain according to the routing decision query request of the HLR, and return the current routing decision information to the HLR. 32. The system according to claim 31, wherein the route information returned by the HLR to the SMS-GMSC is the address information pointing to the CS/IMS short message interworking gateway, or the address information of the VMSC where the user is currently located.

Images