WO2007085196A1

WO2007085196A1 - Registration method and system in ip multimedia subsystem

Info

Publication number: WO2007085196A1
Application number: PCT/CN2007/000287
Authority: WO
Inventors: Wenfu Wu; Lan Liu; Weihua Hu; Sihong Zhou; Wenlin Ye; Zhiming Zhu; Jie Wang; Wenlin Zhang; Jin Zhang; Xu Wang
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2006-01-25
Filing date: 2007-01-25
Publication date: 2007-08-02

Abstract

A terminal performs network attachment, and obtains address information of IP multimedia subsystem IMS; performs IMS registration according to the IMS address information. The terminal performs IMS registration when or after network attachment in the present invention, thus the terminal can immediately originate a call or receive a call from IMS domain.

Description

— WtlP multimedia subsystem registration method and system

The present invention relates to the field of communications, and in particular, to a method and system for registering an IP multimedia subsystem. Background technique

The existing GPRS (General Package Radio Service) I UMTS (Universal Mobile Telecommunications System) network structure is shown in Figure 1, which adopts a structure similar to that of the second generation mobile communication system. Including radio access networks, such as UMTS (Universal Mobile Telecommunications System) UMTS Territorial Radio Access Network (UTRAN) or GSM/EDGE Radio Access Network (GERAN) ), Core Network (C) and Terminal (User Equipment, UE). Wherein, GERAN/UTRAN is used to connect the terminal to the core network CN; CN can be used to implement the external network,

CS) and Packet Switched Domain (PS) support traditional voice services and IP-based data services, respectively.

The CS domain includes nodes such as the Mobile Switching Center Server (MSC-Server), the Media Gateway (MGW), and the Gateway Mobile Services Switch Center Server (GMSC-Server). The MSC-Server is used to transmit the control plane data of the CS domain, and implements functions such as mobility management, call control, and authentication encryption. The GMSC-Server is used to implement the control plane function of the call control and mobility control of the GMSC. To achieve the transmission of user plane data.

The PS domain includes nodes such as the Serving General Packet Radio Service Support Node (SGSN) and the Gateway General Packet Radio Service Support Node (GGSN). The GGSN is mainly responsible for interfacing with the external network. At the same time, the GGSN is also responsible for realizing the transmission of user plane data. The core functions of the SGSN are to implement functions such as route forwarding, mobility management, session management, and user information storage.

The Home Location Register (HLR) is used to store user subscription information. Both CS and PS domains use this device.

3 GPP (Third Generation Partnership Project) superimposes the IMS (IP Multimedia Subsystem) network based on the existing PS domain network, as shown in Figure 2, introducing the Session Initiation Protocol ( The Session Initiation Protocol (SIP), as a service control protocol, provides a rich multimedia service by separating the service control from the bearer control by utilizing the features of SIP, simple expansion, and convenient media combination.

The core processing component of the IMS network is a Call Session Control Function (CSCF), which is used to control functions such as user registration and session control. According to the function, CSCF can be divided into proxy call session control function entity (Proxy CSCF, P-CSCF), query call session control function entity (Interrogating CSCF, I-CSCF) and service call session control function entity (Serving CSCF, S -CSCF ) Three logical entities.

The P-CSCF is a preliminary entry point for the unified IMS access domain control plane, and implements the transfer of SIP messages (eg, registration, multimedia sessions, etc.) from the visited access network to the S-CSCF of its home location (according to the registration). Time recorded information) or I-CSCF (according to the home domain name carried by the SIP user agent:) and other functions.

The I-CSCF is a preliminary entry point for the unified control plane of the IMS home domain. In the IMS registration process, the user is assigned an S-CSCF according to the user subscription and CSCF capability information returned by the Home Subscriber Server (HSS), and The registration request is forwarded to the S-CSCF, and it is also responsible for reselecting the S-CSCF when the expected response returned by the S-CSCF is not received within the timeout period.

The S-CSCF is in a core control position in the session control of the entire IMS network, and has a registration request that the user from the IMS visited domain is forwarded by the P-CSCF, and cooperates with the HSS to authenticate the IMS user equipment user, and from the HSS. Download the IMS basic subscription data, perform the basic session routing function for the calling and called IMS users, and evaluate the IMS subscription triggering rules.

The HSS is used to store the subscription information of the IMS user in the home network, and the database used as the storage user information in the IMS is located at the top of the IMS network architecture. Includes basic identification, routing information, and business contract information.

In order to enhance the competitiveness of future networks, 3GPP is studying an evolved 3GPP network system. System. An evolved packet network architecture is shown in FIG. 3, including a Mobility Management Entity (MME), a User Plane Entity (UPE), and a user plane between different access systems (Inter Access). System Anchor, Inter AS Anchor ) Three logical functional entities. The MME is responsible for the mobility management of the control plane, including user context and mobility state management, and assigning temporary identifiers of users; the UPE is responsible for initiating paging for downlink data in idle state, managing and storing IP bearer parameters and routing information in the network; Inter AS Anchor acts as a user plane anchor between different access systems. The Policy and Charging Rule Function (PCRF) is used for billing and policy control. The Home Subscriber Server (HSS) is used to store user subscription information.

In Figure 3, the three functional modules MME, UPE, and Inter AS Anchor can be set separately or combined in one entity.

According to the requirements of the evolved packet core network, a default IP access bearer can be provided between the UE and the evolved packet core network while the UE completes the attach. A flow of network attachment in a non-roaming scenario is described in 3GPP TR 23.882 vO.9.0: 3GPP System Architecture Evolution: Report on Technical Options and Conclusions (Release 7), as shown in FIG. 4: The following steps are included: Step 401 The UE sends a network discovery and access system selection message to the evolved access network, and initiates network discovery and access (Network Discovery and Access System Selection). ^ If there is network sharing, then a shared network will be selected.

Step 402: The UE initiates an attach request (Attach Request) to the MME/UPE, where the request includes previously registered information (for example, a temporary identifier). If the UE does not have previous registration information, it includes its permanent identity.

In the case of network sharing, the attach request message should include the selected network or MME/UPE ₀

Considering the redundancy of the MME/UPE, the evolved access network selects an MME/UPE.

The attach request may include information of the default IP access bearer (e.g., a user selected IP address or APN).

Step 403: If the UE reports the previous registration information, the MME/UPE sends the Send old registration information Searches the user's information from the original MME/UPE.

Step 404: The original MME/UPE sends the user information (Send user information) to the target MME/UPE (for example: the permanent identifier of the user).

Step 405: Perform authentication on the target MME/UPE.

Step 406: The target MME/UPE registers with the HSS as a service MME/UPE (Register MME) of the UE.

Step 407: The information of the user on the original MME/UPE is deleted or annotated as Delete UE registration information.

Step 408: The HSS confirms the registration of the target MME/UPE ( Confirm Registration).

The subscription information of the authorized default IP access bearer is transmitted to the target MME/UPE. The default bearer-related policy and charging control information is also transmitted to the target MME/UPE.

Step 409: Select an Inter AS Anchor (Selection of Intersystem Mobility Anchor GW).

The IP address configuration is determined by the user's preferences or subscription data, or the policy of the HPLMN or VPLMN.

Step 410: The Inter AS Anchor performs an IP Plane Configuration according to the determined IP address of the UE. The user plane is established and the default policy and charging procedures are applied.

Step 411: The MME/UPE provides a default bearer QoS configuration (for example, an upper limit of the data rate) to the evolved access network. This QoS configuration may require an additional triggering mechanism (eg, the need to send upstream or downstream data).

Step 412: The MME/UPE sends an attach message (Accept Accept) of the receiving UE and allocates a temporary identifier to the UE, and the IP address of the UE is also sent to the UE. In a roaming scenario, the roaming limit is checked and if it is violated the attachment will be rejected.

Step 413: The UE confirms the attach success (Attach Confirm).

In the above prior art, only the packet domain and the circuit domain are in the evolved network architecture. In this case, the voice session service also needs to be completed by the packet domain, and all voice calls are completed by the IMS. In the above process, the UE does not perform IMS registration when the network is attached, and the call made by the UE after the UE is attached to the IMS cannot be completed. Summary of the invention

The embodiment of the present invention provides an IP multimedia subsystem registration method and system, which is used to solve the problem that when the terminal performs network attachment in the existing network system, the IMS registration is not performed when the network is attached or the network is attached, and the IMS is passed through the IMS. The problem of the voice service being carried out cannot be completed in time.

An IP multimedia subsystem IMS registration method, which is applied under a wireless evolved network architecture, and includes:

The core network receives an attach request initiated by the terminal;

The core network performs an attach operation for the terminal to obtain IMS address information.

The core network sends the IMS address information to the terminal;

The core network performs IMS registration for the terminal according to the IMS registration request of the terminal, where the IMS registration request is sent by the terminal according to the IMS address information.

Receiving, by the core network, an attach request initiated by the terminal, where the attach request carries the indication information of the IMS address information.

When the indication information indicates that IMS address information is required, the core network performs an attach operation for the terminal to obtain IMS address information.

The core network sends the IMS address information to the terminal;

An IP multimedia subsystem IMS registration system, which is applied under a wireless evolution network architecture, and includes:

An IMS address information acquiring unit, configured to acquire IMS address information when receiving a network attach request of the terminal; The IMS address information storage unit is configured to store the IMS address information.

In the embodiment of the present invention, when the terminal performs network attachment or the network is attached, the IMS is registered, so that the terminal can immediately initiate a calling (SIP call) or receive a called call from the IMS domain. DRAWINGS

1 is a schematic diagram of a network architecture of a GPRS/UMTS in the prior art;

2 is a network architecture diagram of superimposed IMS on a PS domain network in the prior art;

3 is a schematic diagram of an evolved packet core network architecture in the prior art;

4 is a schematic flowchart of UE attachment in TR 23.882 in the prior art;

FIG. 5 is a schematic flowchart of Embodiment 1 of the present invention; FIG.

FIG. 6 is a schematic flowchart of Embodiment 2 of the present invention. detailed description

Specific embodiments of the present invention are described below in conjunction with the drawings.

The present invention can be applied to a 3GPP evolved network. The following describes the 3GPP evolution network as an example. The embodiment provided by the present invention acquires IMS address information during the network attachment process of the terminal. The terminal performs IMS registration according to the IMS address information, and completes IMS registration in the process of network attachment or after the network is attached, so that the terminal can immediately initiate a calling (SIP call) or receive a called from the IMS domain. call.

Embodiment 1:

First, an IMS address information is stored in the user subscription information in the HSS, and an identifier bit is used to identify whether to allow the UE to perform network attachment while performing IMS registration, which is called an IMS registration identifier.

When the UE initiates the attach request, the evolved packet core network obtains the address information of the IMS and the identifier bit information from the HSS, and the evolved packet core network sends the address information of the IMS to the UE, and the UE can perform IMS registration. , ,

In the above-mentioned embodiment, the IMS address information may be an IP address of the P-CSCF of the IMS, or may be a special access point name (APN) information connected to the IMS.

The network element that the core network attaches to the UE may be an MME and/or a UPE, or a core network element with other similar functions.

As shown in FIG. 5, it is a schematic flowchart of the first embodiment. In this embodiment, an evolved packet core network is taken as an example for description. As can be seen from the figure, the following steps are included:

Step 501 The UE discovers the evolved access network, and then initiates network selection and access.

After the UE discovers the evolved access network, the network selection and access procedure can be initiated. If there is network sharing, the shared network will be selected.

Step 502: The UE initiates an attach request to the target MME/UPE in the evolved packet core network, including information of registration of the UE.

The UE initiates an attach request to the target MME/UPE, and carries the relevant UE identification information in the request. If there is previously registered information (for example, a temporary identifier), the previously registered information is carried in the request. If the UE does not have previous registration information, its permanent identity is included.

In the case of network sharing, the attach request message should include the selected network or

Considering the redundancy of the MME/UPE, the evolved RAN will select an MME/UPE to include the information of the default IP access bearer in the request (for example: the IP address selected by the user or the APN).

Step 503: If the previous registration information is reported by the UE, the target MME/UPE retrieves the information of the user from the original ΌΡΕ/ΌΡΕ by sending the previous registration information.

Step 504: The original MME/UPE sends the user information to the target MME/UPE (for example: the permanent identifier of the user).

The above steps 503 and 504 are based on the premise that the UE has previously registered information, and if the UE does not have previously registered information, the processing may be omitted.

Step 505 The UE performs authentication on the target MME/UPE.

Step 506: The target MME/UPE registers with the HSS as the serving MME/UPE of the UE. After the authentication is passed, the target MME/UPE registers with the HSS as the serving MME/UPE of the UE, and the UE's mobility management is completed by the target MME/UPE.

Step 507: The information of the UE on the original MME/UPE is deleted or annotated as non-existent. When the target MME/UPE is registered as the serving MME/UPE of the UE, the user information stored on the original MME/UPE is deleted or annotated as non-existent.

Step 508: The HSS confirms the registration of the target MME/UPE, and the HSS sends the IMS address information and the IMS registration identifier to the MME/UPE.

The registration operation of the MME/UPE is confirmed between the HSS and the target MME/UPE, and the subscription information of the default IP access bearer of the HSS is transmitted to the MME/UPE. The default bearer related policy and charging control information is also transmitted to the MME UPE. The IMS address information and the IMS registration identifier are also sent to the MME/UPE.

Step 509: The target MME/UPE selects an Inter AS Anchor _0.

The step further includes assigning an IP address to the UE, and the IP address configuration is determined by user preference or subscription data, or a policy of the HPLMN or the VPLMN.

Step 510: The Inter AS Anchor performs IP layer configuration according to the determined UE IP address. The user plane is established and the default policy and charging procedures are applied.

The establishment of the user plane may be initiated by the UE or by the MME UPE.

Step 511: The MME/UPE provides a default QoS configuration (for example, an upper limit of the data rate) to the evolved RAN. The QoS configuration can be implemented by adding a trigger mechanism, such as the need to send uplink or downlink data.

Step 512: The MME/UPE sends an attach message accepting the UE, and allocates a temporary identifier to the UE, and the UE IP address is also sent to the UE. In a roaming scenario, the roaming limit is checked and if it is violated the attachment will be rejected. The MME/UPE also delivers the IMS address information and the IMS registration identifier to the UE if it is determined that the IMS registration identifier is the UE attachment.

Step 513: After receiving the configured IP address, the IMS address information, and the IMS registration identifier, the UE immediately performs IMS registration.

After the UE receives the configured IP address, IMS address information, and IMS registration identifier, the root According to the indication of the IMS registration identifier information, the IMS registration can be initiated.

If the default IMS address information obtained in this step is the IP address information of the P-CSCF of the IMS, the UE may directly use the IP address of the P-CSCF of the IMS for IMS registration, if the connected IP multimedia sub-portion The address information of the system is the access point name information of the IP multimedia subsystem, and the step of the UE querying the domain name server and obtaining the IP address of the P-CSCF of the IMS.

The process of querying and obtaining the IP address of the IP multimedia subsystem from the domain name server may refer to the APN information received by the SGSN in the existing UMTS system to query the DNS for the IP address of the GGSN, and the DNS returns the IP of the GGSN to the SGSN according to the APN information. The SGSN sends the PDP context establishment information to the GGSN and sends the APN information reported by the UE to the GGSN.

Step 514: The UE confirms that the attach is successful.

The operations of the foregoing steps 513 and 514 may be performed in sequence, such as performing step 513 and then performing step 514, or performing step 514 and then performing step 513, or may be performed in parallel without prioritization. Embodiment 2:

Embodiment 2 sets IMS address information in the evolved packet core network.

In this solution, the IMS address information may be an IP address of the P-CSCF of the IMS, or may be an APN information that is connected to the IMS. The second embodiment uses the IP address of the P-CSCF as an example for description.

The network element that is attached to the UE may be an MME and/or a UPE, or a network side network element having other similar functions.

As shown in FIG. 6 , it is a schematic flowchart of the second embodiment of the present invention. In the second embodiment, the core network of the evolved packet is taken as an example, and the solution of the present invention is also applicable to other core networks. As can be seen from the figure, the terminal attachment process includes the following steps:

Step 601: The UE discovers an evolved access network (Evolved RAN), and then initiates network selection and access.

In this step, the UE sends a network discovery and access system selection to an evolved access network (Evolved RAN). Network Discovery and Access System Selection, select the network and access system;

Step 602: The UE sends an attach request message to the MME UPE, where the attach request message carries indication information of whether the UE needs the IP address of the P-CSCF.

As an embodiment of the present invention, the MS network capability (MS network capability) cell in the attach request message carries the indication information of whether the UE needs the IP address of the P-CSCF, and specifically, a flag bit IP indicator is added. Indicates whether the UE needs the IP address of the P-CSCF. When this flag is 1, it indicates that the P-CSCF IP address (Mobile station need P-CSCF IP address) is required; when this flag is 0, it indicates that The P-CSCF IP address (Mobile station need not P-CSCF IP address) is required. The example structure of the MS network capability cell is as follows:

The attachment request message may also carry the access point name APN information of the IMS network, and the core network may search for the IP address information of the P-CSCF of the IMS network according to the APN information.

Step 603: If the original request information is carried in the attach request message, the MME/UPE sends The original registration information (Send old registration information) to the original MME/UPE acquisition user's letter step 604, the original MME/UPE transmission user information (Send user information); Steps 603 and 604 are based on the premise that the UE has the original registration information. If the UE does not have previously registered information, the processing can be omitted.

Step 605: The MME/UPE authenticates the UE.

Step 606: Register the target MME/UPE into the HSS (Register MME/UPE); Step 607: Delete the UE information in the original MME/UPE (Delete HE registration information);

Step 608: The HSS confirms the registration of the target MME/UPE (Confirm Registration); Step 609, the MME/UPE selects an Inter AS Anchor (Selection of Intersystem Mobility Anchor GW);

Step 610: The Inter AS Anchor performs IP layer configuration by using the allocated IP address of the UE, the user plane between the UE and the Inter AS Anchor is established, the default charging and policy rules are used, and the evolved packet core network obtains the configured P- The IP address of the CSCF;

As another implementation manner of the present invention, the evolved packet core network may configure an IP address of a P-CSCF used by each APN (Access Point Name), and the evolved packet core network acquires the UE according to the APN used by the UE. The IP address of the P-CSCF used.

It should be noted that the IP address configuration of the P-CSCF is related to the internal configuration of the evolved packet core network, and is related to the design of the network and the operation strategy of the operator, and the present invention is not limited thereto.

Step 611: Configure QoS (Configure IP Bearer QoS) used by the default IP access bearer between the MME/UPE and the evolved radio access network;

Step 612: The MME/UPE accepts the attach request of the UE, and allocates the temporary identifier of the UE, and the MME/UPE evolved packet core network carries the IP address of the P-CSCF it acquires to the UE in the attach accept message. , the UE saves the IP address of the P-CSCF; For an example of the present invention, by adding the P-CSCF IP address cell to the IP address of the P-CSCF in the Attach Accept message, the following example structure of the Attach Accept message containing the P-CSCF IP address cell is as follows:

Step 613: The UE confirms the attach confirmation ( Attach Confirm);

Step 614: The UE uses the IP address of the obtained P-CSCF to perform IMS registration. For the registration process, refer to 3GPP TS 23.228, which is hereby incorporated by reference.

The IP address of the P-CSCF obtained by the evolved packet core network in the UE attaching process in the foregoing Embodiment 2 is completed in step 610. The actual implementation is not limited thereto, and may be completed in other steps. Embodiment 3:

Embodiment 3 of the present invention provides an IMS registration system for a terminal, where the system is applied to wireless Under the evolved network architecture, the system includes:

The IMS address information acquiring unit is configured to: when the network attachment request of the terminal is received, acquire the IMS information; and the IMS address information storage unit is configured to store the IMS address information.

In the above system, the IMS address information storage unit may be located in the evolved core network, integrated with other functional entities in the core network or separately; or integrated in the home subscriber server HSS.

The evolved core network may further include an IP address obtaining unit of the second P-CSCF, where the unit is configured to obtain an IP address of the P-CSCF of the IMS according to the access point name of the IMS.

The system may further include, in the terminal UE, an IP address obtaining unit of the first proxy call session function entity P-CSCF, where the unit is configured to acquire an IP address of the IMS P-CSCF from the domain name server according to the access point name of the IMS connection.

The terminal may further include an indication information setting unit, where the unit is configured to set, in the network attachment request, indication information of whether the terminal needs IMS address information.

The present invention performs IMS registration in the process of network attachment by the UE in the evolved network or immediately after the network is attached. Thus, since the evolved network has no circuit domain, all calls need to be completed in the packet domain, and the IMS is performed at the same time as the attachment or the network is attached. The registered UE can immediately initiate a calling (SIP call) or a called call from the IMS domain.

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. Thus, it is intended that the present invention cover the modifications and variations of the inventions

Claims

Rights request

An IP multimedia subsystem IMS registration method, wherein the method is applied to a wireless evolved network architecture, including:

The core network receives an attach request initiated by the terminal;

The core network sends the IMS address information to the terminal;

The core network performs IMS registration for the terminal according to the IMS registration request of the terminal, and the IMS registration request is sent by the terminal according to the IMS address information.

2. The method according to claim 1, wherein, when the core network obtains the IMS address information, the IMS registration identifier information is also obtained, and the IMS registration identifier information is used to allow the IMS to register when the UE attaches to the network. .

The method of claim 2, wherein, when the core network sends the IMS address information to the terminal, the IMS registration identifier information is sent to the terminal.

The method according to any one of claims 1 to 3, wherein the IMS address information is an IP address information of a proxy call session function entity P-CSCF of the IMS or an access point name connected to the IMS. information.

The method according to claim 4, wherein, if the IMS address information is access point name information of the IMS connection, the core network performs the terminal for the terminal according to the IMS registration request of the terminal. When the IMS is registered, the domain name server DNS queries and returns the IP address of the IMS P-CSCF according to the request of the terminal.

The method according to claim 2, wherein the IMS registration identifier information and the IMS address information are configured in the same network entity.

The method according to claim 1, wherein the IMS address information is configured in a home subscriber server HSS or in a network entity of an evolved core network.

8. The method according to claim 1, wherein the connection request initiated by the terminal carries the access point name information of the connection IMS.

The method of claim 8, wherein the core network obtains the IMS address information, and the core network obtains the access point name of the IMS according to the access point name information of the IMS. The IP address information of the proxy call session function entity P-CSCF of the IMS corresponding to the information.

An IP multimedia subsystem IMS registration method, wherein the method is applied to a wireless evolution network terminal architecture, including:

The core network sends the IMS address information to the terminal;

The method according to claim 10, wherein the terminal needs indication information of the IMS address information, and is carried by the mobile station network capability cell MS network capability of the attach request.

12. An IP multimedia subsystem IMS registration system, wherein the system is applied to a wireless evolved network architecture, and the method includes:

An IMS address information acquiring unit, configured to acquire IMS address information when receiving a network attach request of the terminal;

The IMS address information storage unit is configured to store the IMS address information.

The system according to claim 12, wherein the IMS address information storage unit is located in an evolved core network or integrated in a home subscriber server HSS.

The system according to claim 12, wherein the system further comprises: an IP address obtaining unit of the first proxy call session function entity P-CSCF, located at the terminal, configured to associate the access point name according to the IMS Obtain the IP address of the IMS P-CSCF from the domain name server.

The system according to claim 12, wherein the system further comprises: an IP address obtaining unit of the second P-CSCF, located in the evolved core network, configured to connect to the IMS according to The access point name, obtain the IP address of the IMS P-CSCF.

The system according to claim 12, wherein the system further comprises: an indication information setting unit, located at the terminal, configured to set, in the attach request, indication information of whether the terminal needs IMS address information.