WO2008134930A1

WO2008134930A1 - Method, apparatus and system for message processing in ims network

Info

Publication number: WO2008134930A1
Application number: PCT/CN2008/000857
Authority: WO
Inventors: Kai Wen
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2007-04-30
Filing date: 2008-04-28
Publication date: 2008-11-13
Also published as: CN101043526A; CN101043526B

Abstract

A method for message processing in IMS comprises: receiving register request message of the user by the original home domain, querying the correspondence between IMSI number and the target home domain name according to the IMSI contained in the said register request message, and determining the target domain name; and the said original home domain processing the register request message according to the determined target home domain name. Besides a server and an IMS network system are disclosed.

Description

Method, device and system for processing messages in an IMS network

The present invention relates to a next generation communication network, and more particularly to a method, apparatus and system for processing messages in an IMS network. Background technique

As a next-generation network supporting fixed and mobile convergence, IMS networks have become the focus of current industry discussions. Many IMS-related specifications have been defined in 3GPP and TISPAN standards.

Each IMS user has at least one private user ID and one public user ID. The private identifier is specified by the user's home domain operator. This identifier is used for user registration, authentication, management, and accounting. The user's private identity is not used to route SIP messages. The user's private identity is determined by the network access identifier defined in FC2486. The form of NAI).

The public user identity is used by the user to request communication with other users, similar to the telephone number referred to in a traditional telecommunications network (such as PSTN), which often appears on business cards. The user's public identity is in SIP URI or Tel URJ format; the Tel URI is defined in protocol RFC 3966, and the traditional E.164 number is represented by URL syntax. SIP URIs are defined in protocols RFC 3261 and RFC 2396.

The IMS network uses the registration process of the SIP protocol to implement user access to the IMS network. During the user registration process, the IMS network authenticates the user's private identity and establishes an access domain security channel. The user registration success will establish the relationship between the user's public identity and the current location of the user in the home domain service-call session control function S-CSCF. Whether the current registered location of the user is in its home domain or in a certain roaming domain, the call with the public identity of the user as the called party can be routed to the corresponding user equipment.

The IMS network is based on the SIP protocol. The public user ID is the SIP URL. The public user ID format can be simply expressed as "sip:user@domain". The domain is the domain name. Each IMS domain operated by the operator has a corresponding domain name, for example, IMS. At the beginning of the deployment, the operator ABC operates an IMS network with the domain name "ABC.com", and Alice's public user ID at the operator ABC is usually "sip: Alice@ABC.com".

In the IMS network system, the home domain domain name of the IMS network is used to identify the IMS network to which the IMS user belongs, and the home domain domain name of the IMS user is usually stored in the user's ISIM card (IMS Subscriber Identity Module). During the registration process, the Request-URI in the registration request message sent by the user equipment UE is filled in as the home IMS network domain name of the user, and the proxy-call session control function P-CSCF in the IMS network queries the domain name server DNS according to the domain name, and will register. The request message is routed to the user's home domain. For user equipment that uses an ISIM card, the home domain domain name of the IMS user is typically stored in the ISIM card. For user equipment using USIM cards and SIM cards, the home domain domain name can be derived from the user's IMSI number information according to the definition of 3GPP standard 23003. The IMSI numbering rules are shown in Figure 1A, where:

- Mobile Country Number (MCC): A 3-digit number that uniquely identifies the country to which the mobile user belongs; for example, China is 460.

- Mobile Network Number (MNC): Identify the mobile network to which the mobile subscriber belongs, using 2 to 3 digits; for example, China uses 2 digits.

- Mobile Subscriber Identity (MSIN): Uniquely identifies mobile users.

The format of the exported home domain domain name is: ims.mnc(0xx).mcc(460).3gppnetwork.org, where "XX" - the assignment of the mobile network number MNC, assigning only one mobile network number to one operator, for example, In China, the code of the operator A is "00", and the code of the operator B is "01". Therefore, the operator A's user exports his own home domain name to "ims.000.460.3gppnetwork.org". The domain name "3gppnetwork.org" is managed by the GSMA (Global System for Mobile Communications Association), "ims.000.460.3gppnetwork.org" There is a record in the GSMA's DNS system that can correspond to the corresponding operator A's I-CSCF entity. Thus, the request-uri in the registration request of the operator of the operator A is filled in as "ims.000.460.3gppnetwork.org", and the registration request will be routed to the I-CSCF entity of the IMS network of the operator A registered in the aforementioned DNS system. .

In this paper, the home domain derived from the user IMSI number is referred to as the original home domain, and the network corresponding to the original home domain domain name is referred to as the original home network, and the IMS network corresponding to the user's true home belongs. The home domain is called the destination home domain, and the network corresponding to the destination home domain domain name is called the destination home network. The method for deriving the above-mentioned home domain name implies that one operator has only one IMS network, but one operator may operate multiple IMS networks at the same time, and each IMS network corresponds to a different domain. Therefore, for an operator to operate multiple IMS domains at the same time, the original home domain domain name cannot be mapped to the user's destination home domain based on the above-mentioned domain name export method. (Because an operator only assigns one mobile network number MNC, The original home domain name that is exported can only correspond to a specific IMS network. If the user is served by another IMS network, it cannot be matched. Summary of the invention

Embodiments of the present invention provide a method, apparatus, and system for processing a message in an IMS network, so that a user's destination home domain can be correctly determined.

A method of processing a message in an IMS network, comprising the steps of:

The original home domain receives the registration request message of the user, and queries the correspondence between the IMSI number information and the domain name of the destination home domain according to the IMSI number information in the registration request message, and determines the domain name domain of the user;

The original home domain processes the registration request message according to the determined destination home domain domain name.

An inquiry call session control function entity includes:

a receiving module, configured to receive a registration request message of the user;

a querying module, configured to query, according to the IMSI number information in the registration request message, a correspondence between the IMSI number information and the domain name of the destination home domain;

And a sending module, configured to forward the registration request message to the corresponding network device according to the query result. A server, comprising:

a storage module, configured to store a correspondence between the IMSI number information of the user and the domain name of the destination home domain;

a receiving module, configured to receive a registration status query request message that includes the IMSI number information of the user, where the query module is configured to query the corresponding one of the storage modules according to the IMSI number information Relationship

The sending module is configured to return a message containing the result of the query to the requesting party.

An IMS network system, comprising:

a server, configured to store a correspondence between the IMSI number information of the user and the domain name of the destination home domain;

a proxy call session control function entity, configured to route the registration request message to a user's original home domain according to a home domain domain name in a registration request message of the user;

The query call session control function entity is configured to query the correspondence relationship according to the IMSI number information in the received registration request message to determine the destination home domain domain name of the user, and forward the registration request message to the network device of the destination home domain. DRAWINGS

1A is a schematic diagram of a numbering rule of an IMSI in the prior art;

Figure B is a schematic diagram of the relationship between the network entities of the IMS network in the prior art;

2 is a schematic diagram of a network structure of multiple IMS network domains of an operator according to an embodiment of the present invention; FIG. 3A is a schematic diagram of a correspondence between distributed storage IMSI number information and a destination home domain domain name according to an embodiment of the present invention;

FIG. 3B is a schematic diagram showing the network structure of two sub-domain services in an IMS network according to an embodiment of the present invention; FIG.

4 is a main flowchart of processing a registration request message in an embodiment of the present invention;

5 is a specific flowchart of processing a registration request message in a specific example of the embodiment of the present invention; FIG. 6 is a schematic structural diagram of an inquiry call session control function entity according to an embodiment of the present invention; Schematic diagram of the user server. detailed description

Figure 1B shows a portion of the network entity of the IMS network system, including proxy call session control functions The P-CSCF entity, the Incoming Call Session Control Function I-CSCF entity, the Serving Call Session Control Function S-CSCF entity and the Home Subscriber Server HSS. The P-CSCF entity is the first contact point of the user in the IMS system, forwards the request of the user equipment to the designated target device, and processes and forwards the response; the I-CSCF entity is connected to all in one operating network. The contact point provided by the connection of a certain user in the network, the functions performed by the I-CSCF entity include: contacting the HSS to obtain the name of the S-CSCF entity serving the user, based on the capability set received from the HSS To specify an S-CSCF entity, etc.; the S-CSCF entity is the core of the IMS, located in the home domain, for session control and registration services for user equipment; HSS is the main data storage for all user and service related data in IMS These data mainly include user identity, registration information, access parameters, and server trigger information.

In this embodiment, when the operator operates multiple IMS networks, the correspondence between the IMSI number information of all the IMS users of the operator and the destination home domain domain name is established in the network device of the original home network, so that the IMSI can be based on the IMSI. The number information finds the destination home domain of any one of the operators. The IMSI number information may be an IMSI number, an IMSI number segment, or a mobile subscriber identity MSIN in the IMSI number, or an MSIN number segment.

FIG. 2 shows the IMS network domain 1 and the IMS network domain 2 operated by the same carrier A in this embodiment. Of course, the IMS network domain 1 and the IMS network domain 2 are not limited thereto. For example, in another embodiment, the same carrier can operate 5 IMS network. The IMS network domain 1 and the IMS network domain 2 respectively cover a certain area, and each IMS network domain has multiple IMS users. In the scenario shown in FIG. 2, the IP address of an I-CSCF entity of one of the IMS network domains is the IP address corresponding to the home domain domain name derived from the IMSI number. For example, for the aforementioned operator A, the IP address of the I-CSCF1 entity in the IMS network domain 1 is the IP address corresponding to the domain name "ims.000.460.3gppnetwork.org" (IMS network domain 1 may be carrier A's) The IMS network operated by the subordinate company (subsidiary), that is, the IMS network domain 1 is the original home network. The IMSI number of the user 1 is 46000123456789, and the home domain name derived by the IMSI number is "ims.000.460.3gppnetwork.org", corresponding to the IMS network domain 1 in FIG. 2, and the destination home domain of the user 1 is "site2.aaa.com". , corresponding to IMS network domain 2 in Figure 2, site2.aaa.com in DNS After parsing, it is the address of I-CSCF2. Therefore, the record of "46000123456789" corresponding to "site2.aaa.com" is stored in the network device of the IMS network domain 1, that is, the destination home domain name "site2.aaa.com" of the user 1 can be queried through the IMSI number.

The correspondence between the IMSI number information and its destination home domain domain name can be saved in various ways, for example, it can be saved in the I-CSCF entity or saved in the subscriber location function entity SLF (Subscriber Location Function) / Home Subscriber Server HSS. , or distributed in these network elements.

An example of a distributed storage mode is shown in FIG. 3A, which is stored according to the IMSI number semicolon segment. The number segment 1 is configured in the I-CSCF and processed by the home subscriber server HSS2, and the segment 2-9 is used to locate the function entity. SLF1 processing. In the user positioning function entity SLF1, the corresponding number segment relationship is also assigned to the next-level user positioning function entity SLF according to the number segment configuration, for example, in FIG. 3A, the number segment 2-5 to the user positioning function entity SLF21 Processing, number 6-9 to the user positioning function entity SLF22 processing. For example, for the "46000123456789" number, the I-CSCF entity can finally obtain the destination home domain name "site2.aaa.com" corresponding to "46000123456789" from the home subscriber server HSS2 by querying.

When the correspondence between the IMSI number information and the destination home domain domain name is stored in the home subscriber server HSS/user location function entity SLF, in some scenarios, the user access request UAR/user access in the Cx/Dx interface needs to be extended. The request responds to the UAA interaction. When the user does not belong to the original home network, the user's destination home domain name is returned to the I-CSCF entity, and the I-CSCF entity routes the registration request message to the destination home network according to the destination home domain name.

According to the correspondence between the IMSI and the destination home domain, when the user belongs to the original home network, the Cx/Dx interface does not need to be extended. As shown in FIG. 3B, one IMS network is two sub-domains of sub-domain 1 and sub-domain 2. ^^, different subdomains have different HSS and S-CSCF entities, but share a group of I-CSCF entities. The I-CSCF entity can find a sub-domain serving the user according to the IMSI number information, that is, the I-CSCF can locate the corresponding HSS that provides the service for the user, by using the foregoing manner of saving the correspondence between the MSI number information and the domain name of the destination home domain. , after the query data is obtained, the note will be The request message is routed to the S-CSCF of the corresponding sub-domain, apparently in this scenario without the need to extend the Cx/Dx interface. In this particular scenario, unlike the foregoing, destination destination 3 corresponds to the corresponding HSS / S-CSCF within the IMS network, rather than to another IMS network.

In a scenario similar to that shown in Figure 2, the main processing flow when using the USIM card or SIM card user equipment to initiate a registration request message is shown in Figure 4:

Step 400: The user equipment UE of the USIM or the SIM card initiates a registration request, where the Request-uri in the REGISTER request is the original home domain domain name derived from the IMSI number.

Step 410: After receiving the registration request, the P-CSCF entity on the network side routes the registration request message to the corresponding original home domain according to the original home domain domain name.

Step 420: After receiving the registration request message, the network device in the original home network obtains the IMSI number information in the registration request message, and queries the correspondence between the IMSI number information and the IMS domain name to obtain the destination home domain.

When the IMSI number information is MSIN, the MSIN number is extracted from the ISMI number segment and then the corresponding relationship is queried. The matching query is performed when the IMSI number information is an IMSI number segment or an MSIN number segment.

Step 430: The original home domain processes the registration request message according to the queried destination home domain name. When the destination home domain domain name is the original home domain domain name, the user is registered in the original home domain; when the destination home domain domain name is not the original home domain domain name, the original home domain routes the registration request message to the destination attribution. The domain registers the user in the destination home network.

In the scenario shown in FIG. 2, in a specific example, the IMS network domain 1 serves as the original home domain, and the IMS network domain 2 serves as the destination home domain of the user A, and the user A uses the terminal device of the USIM card or the SIM card. The specific processing flow when the roaming network initiates the registration request message is as shown in FIG. 5 (the IMSI number information is exemplified by the IMSI number):

Step 500: The user equipment UE that uses the USIM card or the SIM card by the user A initiates a registration request in the roaming network, and the IMSI number of the user A is " 46000123456789 " , the Request-url in the registration request is ims.000.460.3gppnetwork.org. The public user ID and the private user ID in the request message are the same, for example: 46000123456789@ims.000.460.3gppnetwork.org.

Step 501: After receiving the registration request, the proxy call session control function P-CSCF entity in the roaming network obtains the IP of the query call session control function entity I-CSCF1 according to the DNS query "ims.000.460.3gppnetwork.org" The address, and the registration request message is routed to the inquiry call session control function entity I-CSCF1.

Step 502: The inquiring call session control function entity I-CSCF1 sends a user access query request UAR to the home subscriber server HSS1 of the IMS network domain through the Cx interface.

Step 503: The home subscriber server HSS1 stores the destination home domain domain name corresponding to the IMSI of the user A. Therefore, the home subscriber server HSS1 queries the destination home domain domain name "site2.aaa.com" according to "46000123456789" (ie, the real user of the user) The IMS home domain name is determined to be different from the domain name of the IMS network domain 1. Therefore, the UAB is returned to the query call session control function entity I-CSCFL by the user access query.

Steps 504-507, the query call session control function entity I-CSCF1 queries the DNS according to the obtained destination home domain domain name to obtain the corresponding IP address, and then routes the registration request to the query call session control function entity I-CSCF2 of the IMS network domain 2, The query call session control function entity I-CSCF2 transmits the registration request to the service call session control function entity S-CSCF2, and performs registration processing on the user. The processing procedure is the same as the existing registration process, and will not be described again.

After the IMS network domain 2 receives the registration of the user A, the user equipment obtains the service route service-route, and the message such as the session request INVITE sent by the user equipment does not need to be performed by the query call session control function entity I-CSCF1. routing.

In another specific example, the IMS network domain 1 serves as the destination home domain of the user B. After the user B initiates the registration request message by using the terminal device of the USIM card or the SIM card, the HSS query correspondence relationship is determined differently from the foregoing process. If the destination home domain name is the same as the domain name of the IMS network domain 1, the existing Cx/Dx interface is kept unchanged, and the HSS directly queries the call session control function entity. The I-CSCF 1 returns the user data, and then queries the call session control function entity I-CSCF1 to forward the registration request message to the serving call session control function entity S-CSCF in the network according to the user data, and completes the user in the original home network. B registration processing.

In the embodiment of the distributed storage mode shown in FIG. 3A, the processing flow of the query destination home domain is different from the foregoing steps 502-503, and the I-CSCF entity may first query the corresponding relationship in the entity (I). The -CSCF entity saves the correspondence between the partial IMSI number information and the destination home domain domain name. When the user's destination home domain is not queried, the user locates the function entity SLF1 to send a query request to learn the user's destination home domain. According to the actual IMSI number information, the user location function entity SLF1 may obtain the user's destination home domain name after re-sending the query request message.

In the scenario where the correspondence between the IMSI number information and the destination home domain domain name is stored in the network entity other than the I-CSCF entity and the HSS/SLF, the network entity is responsible for returning the destination attribution to the I-CSCF entity after querying the corresponding relationship. Domain domain name. It is determined by the I-CSCF entity whether the destination home domain and the original home domain are the same domain.

An I-CSCF entity in this embodiment, as shown in FIG. 6, includes: a receiving module 601, a querying module 602, and a sending module 603, where the receiving module 601 receives a registration request message sent by the user equipment, where the registration request message is The original home domain domain name of the IMS user that is derived from the IMSI number is included; the query module 602 queries the correspondence between the IMSI number information and the destination home domain domain name of the user according to the IMSI number information in the registration request message, and obtains the destination home domain domain name of the user; The sending module 603 routes the registration request message to the corresponding network device according to the queried destination home domain name, for example, to the designated service call session control function S-CSCF entity. Further, the I-CSCF entity may further include a storage module 604, configured to store a correspondence between the IMSI number information of the IMS user and the destination home domain domain name. The query module 602 can query the correspondence between the IMSI number information and the destination home domain domain name from the device or/and other devices.

As shown in FIG. 7 , an HSS or user positioning function entity SLF in this embodiment includes a storage module 701, a receiving module 702, a query module 703, and a sending module 704. The corresponding relationship between the IMSI number information of the IMS user and the destination home domain domain name is stored; the receiving module 702 receives the registration status query request message including the IMSI number information; the query module 703 queries the storage module based on the IMSI number information. Corresponding relationship, if the user's destination home domain domain name is the original home domain domain name of the original home network where the HSS is located, the user data is obtained, otherwise, the corresponding destination home domain domain name is obtained; the sending module 704 returns the query result to the requesting party. .

In the embodiment of the present invention, the registration request message is routed to the corresponding original home domain according to the original home domain domain name of the IMS user derived from the IMSI number, and then the user is determined by querying the correspondence between the IMSI number information and the destination home domain domain name. The destination is in the domain, and the user is registered in the destination home domain, so that the user equipment can be accessed to the actual destination home domain in the scenario that one operator has multiple IMS network domains.

It is apparent that those skilled in the art can make various modifications and variations to the invention without departing from the spirit and scope of the invention. Therefore, it is intended that the present invention cover the modifications and variations of the invention as claimed.

Claims

Rights request

A method for processing a message in an IMS network, comprising:

The original home i or the user's registration request message, and the IMSI number information in the registration request message is used to query the correspondence between the IMSI number information and the destination home domain domain name, and determine the user's destination home domain domain name;

The original home domain registers the user in the corresponding destination home domain according to the determined destination home domain domain name.

2. The method according to claim 1, wherein the mapping between the query IMSI number information and the destination home domain domain name comprises the steps of:

The query call session control function entity in the original home domain sends a query message including IMSI number information to the network entity storing the corresponding relationship;

The network entity queries the correspondence between the IMSI number information and the destination home domain domain name according to the IMSI number information, and returns a query result to the query call session control function entity.

The method of claim 2, wherein the network entity queries the associated other network entity when determining that the entity does not include the mapping between the IMSI number information and the destination home domain domain name, and The result of the query is returned to the query call session control function entity.

4. The method according to claim 2, wherein the network entity is a home user server or a user location function entity.

The method according to claim 1, wherein the IMSI number information is an IMSI number segment, an IMSI number, or a mobile subscriber identity code MSIN or MSIN segment in the IMSI number.

The method according to any one of claims 1 to 5, wherein the destination home domain domain name is the same as the original home domain domain name; or the destination home domain domain name is different from the original home domain domain name.

The method according to claim 6, wherein, when the destination home domain domain name is different from the original home domain domain name, the destination home domain receives the registration request message and completes the user note After the book, subsequent messages between the user and the home domain of the destination no longer pass through the original home domain.

8. An inquiry call session control function entity, comprising:

The query module is configured to: use the IMSI number information in the registration request message, query the correspondence between the IMSI number information and the destination home domain domain name, and obtain the destination home domain domain name of the user;

And a sending module, configured to forward the registration request message to the network device of the corresponding destination home domain according to the query result.

9. The query call session control function entity of claim 8, further comprising:

The storage module is configured to store a correspondence between the IMSI number information of the user and the domain name of the destination home domain.

10. A server, comprising:

a receiving module, configured to receive a registration status query request message that includes the user's IMSI number information, and a querying module, configured to query the corresponding relationship in the storage module according to the IMSI number information in the registration status query request message, and obtain Destination domain domain name;

The server according to claim 10, wherein the server is a home user server or a user location function entity.

12. An IMS network system, comprising:

a proxy call session control function entity, configured to route the registration request message to an inquiry call session control function entity of a user's original home domain according to a home domain domain name in a registration request message of the user;

Querying the call session control function entity, configured to query the correspondence between the IMSI number information of the user and the domain name of the destination home domain according to the IMSI number information in the received registration request message, determine the destination home domain of the user, and according to the query result User equipment destination domain network device forwarding office The registration request message.

The IMS network system according to claim 12, wherein the system further comprises: a server, configured to store a correspondence between the IMSI number information of the user and the domain name of the destination home domain; The function entity directly queries the server; or the query call session control function entity first queries locally, and then queries the server when the local domain domain name is not queried locally.

14. The IMS network system according to claim 12 or 13, wherein the server comprises a home subscriber server and/or a subscriber location function entity.