WO2006037269A1

WO2006037269A1 - A method for service registration based on ip access

Info

Publication number: WO2006037269A1
Application number: PCT/CN2005/001599
Authority: WO
Inventors: Wenlin Zhang; Jie Wang; Xiaoqin Duan
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2004-10-07
Filing date: 2005-09-29
Publication date: 2006-04-13
Also published as: CN100370774C; CN1758614A

Abstract

A method for service registration based on IP access includes: a, the current user terminal sending the service registration request to the IP port; b, the IP port which has received the current user terminal service registration request storing the service registration information of the user, then returning the service registration response to the current user terminal. This method can enable the user information storage unit to know the IP port address information registered by the current user terminal to return the IP port information to other entities so as to implement that the user terminal do the service registration by the IP port, and can inform the user information storage unit of the information of the IP port in time to insure the following complete service flow can be performed completely.

Description

Service registration method based on IP access

The present invention relates to a service registration technology, and more particularly to a service registration method based on IP access. Background of the invention

Due to the increasing demand for wireless access rates, wireless local area networks (WLANs) have emerged to provide high-speed wireless data access in a small range. Wireless LAN includes a variety of different technologies. One of the most widely used technical standards is IEEE 802.11b, which uses the 2.4 GHz band and has a maximum data transmission rate of 11 Mbps. IEEE 802.11g and Bluetooth technology are also used in this band. Among them, 802.11g has a maximum data transfer rate of 54Mbps. Other new technologies such as IEEE 802.11a and ETSI BRAN Hiperlan2 use the 5GHz band and the maximum transfer rate is 54Mbps.

Although there are many different wireless access technologies, most WLANs are used to transport Internet Protocol (IP) packet data packets. For a wireless IP network, the specific WLAN access technology used is generally transparent to the upper layer IP. The basic structure is to use the access point (AP) to complete the wireless access of the user terminal, and to form an IP transmission network through network control and connection device connection.

With the rise and development of WLAN technology, WLAN and various wireless mobile communication networks, such as: GSM, Code Division Multiple Access (CDMA) systems, Wideband Code Division Multiple Access (WCDMA) systems, Time Division-synchronous Code Division Multiple Access (TD) -SCDMA) Interoperability of systems and CDMA2000 systems is becoming the focus of current research. In the 3rd Generation Partnership Project (3GPP) standardization organization, the user terminal can be connected to the Internet (Internet), the intranet (Intranet) through the WLAN access network, and can also access the home network of the 3GPP system via the WLAN access network. Or access network connection of the 3GPP system, specifically, when the WLAN user terminal accesses locally, it is connected to the home network of 3GPP via the WLAN access network, as shown in FIG. 2; The WLAN access network is connected to the access network of the 3GPP, and some entities in the 3GPP access network are respectively interconnected with corresponding entities in the 3GPP home network, for example: 3GPP Authentication and Authorization Accounting (AAA) proxy and 3GPP home network in the 3GPP access network. 3GPP authentication and authorization billing

(AAA) server; the wireless local area network access gateway (WAG) in the 3GPP access network and the packet data gateway (PDG) in the 3GPP home network, etc., as shown in FIG. Figure 1 and Figure 2 are schematic diagrams of the networking structure of the WLAN system interworking with the 3GPP system in the case of roaming and non-roaming.

Referring to FIG. 1 and FIG. 2, in the 3GPP system, a primary subscription subscriber server is mainly included.

(HSS) / Home Location Register (HLR), 3GPP AAA Server, 3GPP AAA Proxy, WAG, Packet Data Gateway, Offline Charging System and Online Accounting System (OCS). The user terminal, the WLAN access network and all the entities of the 3GPP system form a 3GPP-WLAN interactive network, and the 3GPP-WLAN interactive network can be used as a wireless local area network service system. The 3GPP AAA server is responsible for user authentication, authorization, and charging, and the charging information sent by the WLAN access network is collected and transmitted to the charging system; the packet data gateway is responsible for connecting user data from the WLAN access network to the 3GPP network. Or other packet network data transmission; the charging system mainly receives and records the user charging information transmitted by the network, and further includes the OCS instructing the network to periodically transmit the online charging information according to the online charging user's fee situation, and performing statistics and control. .

In the non-roaming situation, when the WLAN user terminal wants to directly access the Internet/Intranet, after the user terminal completes the access authentication and authorization through the WLAN access network and the AAA server (AS), the user terminal can access through the WLAN access network. Internet/Intranet. If the WLAN user terminal also wants to access the 3GPP packet-switched (PS) domain service, the service of the interworking scenario 3 (Scenario3) can be further applied to the 3GPP home network, that is, the WLAN user terminal initiates the interworking scenario 3 to the AS of the 3GPP home network. The service authorization request, the AS of the 3GPP home network performs service authentication and authorization for the service authorization request, and if successful, the AS sends the access permission to the user terminal. The message, and the AS allocates a corresponding PDG to the user terminal, and after establishing a tunnel between the user terminal and the allocated PDG, the 3GPP PS domain service can be accessed. At the same time, the offline charging system and the OCS record the charging information according to the network usage of the user terminal. In the case of roaming, when the WLAN user terminal wishes to directly access the Internet/Intranet, the user terminal can apply to the 3GPP home network to access the Internet/Intmnet through the 3GPP access network. If the user terminal also wants to apply for the interworking scenario 3 service and access the 3GPP PS domain service, the user terminal needs to initiate a service authorization process to the 3GPP home network through the 3GPP access network, and the service authorization process is also performed on the user terminal and the AS of the 3GPP home network. After the authorization succeeds, the AS allocates a corresponding home PDG to the user terminal. After the user terminal establishes a tunnel between the WAG in the 3GPP access network and the allocated PDG, the user terminal can access the 3GPP PS domain of the home network. business.

According to the 3GPP protocol, in the existing 3GPP-WLAN interactive network, the authentication and authorization process of the WLAN user accessing the network is as shown in FIG. 3, and includes the following steps:

Steps 301 to 302: The current LAN user terminal establishes a wireless connection with the WLAN access network according to the procedure specified by the 3GPP protocol; and then initiates an access authentication process between the current WLAN user terminal and the 3GPP AAA server, and the access authentication is passed. Extended Authentication Protocol (EAP) is performed to respond to message interactions.

Steps 303 to 304: After receiving the access authentication request, the 3GPP AAA server determines whether the authentication information for the current WLAN user terminal exists. If not, the authentication information of the current WLAN user terminal is obtained from the HSS, for example: Authentication quintuple/ternary. Moreover, if the user subscription information of the current WLAN user terminal does not exist in the 3GPP AAA server, for example, the authorization information and the temporary identifier of the user are also obtained from the HSS. That is to say, if the 3GPP AAA server does not have user information itself, it needs to be obtained from the HSS.

Step 305: The 3GPP AAA server may send the policy execution information to the WAG in the access public land mobile network (VPLMN) that the current WLAN user terminal roams. Is optional.

Step 306: If the authentication and the authorization are successful, the 3GPP AAA server sends an access-access message to the WLAN access network, and the EAP Success message is included in the message. The success message carries the connection authorization information, for example: Into filter rules, tunnel properties, and more.

Step 307: After receiving the allowed access message, the WLAN access network sends an authentication success message to the current WLAN user terminal. EAP Success ₀

Step 308: If the current WLAN user terminal does not have registration information for the access authentication 3GPP AAA server currently provided in the HSS, the 3GPP AAA server that provides authentication for the current WLAN user terminal is registered in the HSS, and the registration message is based on the user. Temporary identity to identify the user.

In addition, according to the discussion of the 3GPP protocol, the network architecture and process related to the short message service (SMS over WLAN) on the LAN in 3GPP is as shown in FIG. FIG. 4 is a short message support architecture based on IP access. As can be seen from FIG. 4, the UE can interact with the mobile switching center (GMSC/SMS-IWMSC) of the gateway mobile switching center/short message-interworking function through the MSC or SGSN. The UE may also interact with the GMSC/SMS-IWMSC through an IP short message gateway (IP-MESSAGE-GW), where the IP-MESSAGE-GW is a new network entity added to the existing 3GPP-WLAN interaction architecture. The transmission of short messages between the IP client (Client) and the GSM/UMTS network is provided, where the UE is the IP Client. That is, the IP-MESSAGE-GW can interact with the GMSC/SMS-IWMSC using the Mobile Application Protocol (MAP), receive short messages from the GMSC/SMS-IWMSC, or send to the GMSC/SMS-IWMSC. Short message; you can also use the IP bearer-based protocol to interact with the IP Client, receive short messages from the IP Client, or send short messages to the IP Client.

The SM-MO (Short Message Mobile Origination) process in the 3GPP specification, namely: IP Client to Short Message Service Centre (SM-SC, Short Message Service Centre) The sending process is shown in Figure 5, including the following steps:

Step 501: The IP client establishes a tunnel with the PDG. Here, the IP client is a WLAN UE. Step 502: After the tunnel is established, the IP client registers with the IP-MESSAGE-GW.

Step 503: The IP client forwards the short message to the IP-MESSAGE-GW by using an IP bearer-based protocol, where the IP bearer-based protocol may be WAP, SMPP, MMPP, XML, SIP,

SMTP.

■ Step 504: The IP-MESSAGE-GW parses the short message from the IP message, and forwards the parsed short message to the SMS-IWMSC by using standard MAP signaling similar to that used by the MSC or the SGSN to send the short message to the SMS-IWMSC. The standard MAP signaling is defined in 3GPP TS 23.040.

Steps 505 to 506: After receiving the short message sent by the IP-MESSAGE-GW, the SMS-IWMSC forwards the short message to the SM-SC. After receiving the short message, the SM-SC sends a short message transmission report to the SMS-IWMSC. The forwarding process and the transmission reporting process are all defined in 3GPP TS 23.040.

Steps 507~508: After receiving the report, the SMS-IWMSC sends a short message transmission report to the IP-MESSAGE-GW; and the IP-MESSAGE-GW sends a short message transmission report to the IP Client. The process by which the SMS-IWMSC sends a report to the IP-MESSAGE-GW is defined in 3GPP TS 23.040.

The SM-MT (Short Message Mobile Termination) process in the 3GPP specification, that is, the sending process of the SM-SC to the IP client is as shown in FIG. 6, and includes the following steps:

Step 601: The SM-SC forwards the short message to the GMSC.

Step 602: The GMSC sends a sendRoutinglnfoForShortMsg message to the HLR/HSS to obtain routing information of the UE. If the IP Client has been registered in the IP-MESSAGE-GW, the HLR/HSS returns the address information of the IP-MESSAGE-GW. Step 603: The GMSC sends a short message to the IP-MESSAGE-GW, similar to the MAP signaling used when sending the short message to the SMS-IWMSC to the MSC or SGSN.

Step 604a: When the notification setting of the short message is valid, the IP-MESSAGE-GW sends an SMS notification request message to the IP Client to notify the IP Client that there is a short message to be sent.

Step 604b: When the notification setting of the short message is valid, and the IP Client receives the SMS notification request message, the IP Client responds to the SMS notification request message to indicate whether it is willing to receive the short message.

Step 605: After the notification setting of the short message is invalid, or the IP-MESSAGE-GW receives the indication that the IP client is willing to receive the short message, the IP-MESSAGE-GW forwards the short message to the IP client, using the protocol based on the IP bearer. Such as: WAP, SMPP, MMPP, XML, SIP, SMTP.

Steps 606 to 607: The IP-MESSAGE-GW sends a short message transmission report to the SMS-GMSC; after receiving the short message transmission report, the SMS-GMSC sends a short message transmission status message to the HLR/HSS. Both the transmission report and the transmission status procedure are defined in 3GPP TS 23.040.

Step 608: The SMS-GMSC sends a short message transmission report to the SM-SC, and the process of transmitting the report is also defined in 3GPP TS 23.040.

Currently, the 3GPP specification only states that the IP Client needs to register in the IP-MESSAGE-GW before using the short message service, but does not define the specific process of registration, nor defines how to implement the IP Client in the IP-MESSAGE-GW. The registered information informs the HLR that when the GMSC or the SMS-IWMSC obtains the routing information of the IP client from the HLR/HSS, the HLR/HSS cannot return the IP-MESSAGE-GW address, so that the IP Client cannot use the services in the 3GPP network. It can be seen that there are imperfections in the prior art process, which affects the availability of the process. Summary of the invention

In view of this, the main purpose of the present invention is to provide a service registration method based on IP access, which can implement user registration through the IP gateway, and can notify the user information storage unit of the information of the IP gateway in time.

In order to achieve the above object, the technical solution of the present invention is achieved as follows:

A service registration method based on IP access, the method comprising the following steps:

a. The user terminal initiates a service registration request to the IP gateway;

b. The IP gateway stores the service registration information of the user, and then returns a service registration response to the current user terminal.

The request for initiating a service registration in step a specifically includes:

Al. The current user terminal registers in the AAA server, establishes an IP tunnel with the packet data gateway associated with the service, and then sends a service registration request carrying the user terminal identification information to the packet data gateway through the established tunnel;

A2. The packet data gateway receiving the service registration request forwards the received service registration request to the IP gateway.

The packet data gateway in step a2 further includes: checking the legality of the user terminal according to the source IP address and the assigned tunnel identifier in the request sent by the current user terminal, and then forwarding the industry after the check is passed. 'Service registration request.

The IP gateway is an IP gateway associated with the packet data gateway, and the forwarding in step a2 is: The packet data gateway receiving the service registration request directly forwards the service registration request to the IP gateway associated with itself.

The IP gateway is an IP gateway to which the current user terminal belongs, and the step a2 further includes: the packet data gateway receiving the service registration request parses the IP gateway to which the current user terminal belongs according to the user terminal identifier carried in the service registration request, and then The IP gateway that the current user terminal belongs to forwards the service registration request. In the above solution, the service registration request described in step a1 further carries IP gateway identification information. Step a2 further includes: the packet data gateway receiving the service registration request parses the address information of the IP gateway according to the IP gateway identifier carried in the service registration request, and then forwards the service registration request to the parsed IP gateway.

In the above solution, the service registration information of the storage user in step b is: the IP gateway registers its own information with the user information storage unit.

The service registration request in the step a carries the user terminal identifier, and the service registration information of the IP gateway storing the user in the step b includes:

Bl l. The IP gateway parses the address information of the AAA server to which the current user terminal is registered according to the user terminal identifier carried in the request, and then sends a request user information message to the AAA server;

After receiving the requesting user information message, the AAA server obtains the relevant registration information of the user terminal according to the user terminal identifier carried in the message, and then sends a registration request to the user information storage unit;

Bl3. After receiving the registration request, the user information storage unit stores the address information of the IP gateway, and returns a registration response to the AAA server. After receiving the response, the AAA server returns a user information message to the IP gateway.

Step M3 further includes: storing a correspondence between the permanent identifier of the user terminal and the IP address of the user terminal. The correspondence is stored in a separately set database located in the IP gateway or in the AAA server. After the step bl3, the method further includes: the IP gateway storing a correspondence between the packet data gateway and the IP address of the user terminal.

The user terminal identifier is a network access identifier. The address information of the IP gateway is the SS7 address information of the IP gateway of the IP gateway.

After the user information storage unit receives the registration request, the step M3 further includes: the user information storage unit notifying the application server that the user terminal can access the network service through the IP. The service registration request in the step a carries the user terminal identifier, and the service registration information of the user stored in the IP gateway of the step b includes:

B21. The IP gateway parses the address information of the user information storage unit to which the current user terminal belongs according to the user terminal identifier carried in the request, and then sends the user information to the user information storage unit;

B22. After receiving the registration request, the user information storage unit acquires related information of the user terminal stored by itself according to the user terminal identifier, and stores address information of the IP gateway, and then returns a registration response to the IP gateway.

The address information of the IP gateway is the SS7 address information of the IP gateway of the IP gateway. The step b22 further includes: storing a correspondence between the permanent identifier of the user terminal and the IP address of the user terminal. The correspondence is stored in a separately set database located in the IP gateway or in the AAA server. After the step b22, the method further includes: the IP gateway storing a correspondence between the packet data gateway and the IP address of the user terminal.

After the user information storage unit receives the registration request, the step b22 further includes: the user information storage unit notifying the application server that the user terminal can access the network service through the IP.

The method further includes:

B23. After receiving the registration response, the IP gateway notifies the AAA server that the current user terminal is registered in the IP gateway, and the AAA server stores the address information of the IP gateway.

In the foregoing solution, the user terminal is permanently identified as an MSISDN or an IMSI. The user terminal is an IP client accessed through an IP network. The user information storage unit is a home location register or a home subscription subscriber server.

The IP access-based service registration method provided by the present invention, the WLAN IP Client registers in the IP-GW before using the service of the 3GPP network, and is registered by the IP-GW in the user information storage unit, so that the user The information storage unit can learn the IP-GW address information registered by the current IP client, so that the WLAN IP client can be returned to other entities. IP-GW address information, which in turn ensures that the entire business process can be fully executed. In addition, the service registration process provided by the present invention can further implement the process of authenticating the IP client service capability, so that the service of the 3GPP network can be provided to the WLAN IP client securely and reliably. BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic diagram of a network structure in which a WLAN system communicates with a 3GPP system;

2 is a schematic diagram of a networking structure of a WLAN operation network;

3 is a flow chart of authentication and authorization of a WLAN user terminal in the prior art; FIG. 4 is a schematic diagram of an IP-based short message support architecture;

Figure 5 is a schematic diagram of a process of sending an IP client to an SM-SC;

FIG. 6 is a schematic diagram of a sending process of an SM-SC to an IP client;

FIG. 7 is a flowchart of processing according to an embodiment of the present invention; FIG.

FIG. 8 is a flowchart of processing according to another embodiment of the present invention. Mode for carrying out the invention

The core idea of the present invention is to provide a service registration procedure based on IP access, which is applicable to a case where a user terminal accesses a 3GPP network through an IP and uses a PS domain service, and the present invention provides a user terminal to register with an IP-GW. The implementation process and the process of the IP-GW notifying the HLR/HSS of the registration information of the user terminal.

The specific method is as follows: In the existing 3GPP-WLAN interaction network, a functional entity IP gateway (IP-GW) is set to implement service registration of the user terminal, and complete interaction with the HLR/HSS regarding user terminal information. When the user terminal needs to access the 3GPP network through the IP network, the user terminal first sends a service registration request to the PDG, and after the PDG is verified, the PDG sends a service registration request carrying the user terminal identification information to the IP-GW, and the service registration is performed. After requesting registration with the user information storage unit, the IP-GW returns a service registration response to the user terminal via the PDG. Here, The user terminal is an IP client, that is, a WLAN user terminal; the PDG is a PDG supporting the requested service; and the user information storage unit may be an HLR or an HSS.

Here, the IP-GW may be a logical function entity that only supports a certain service registration, for example: an IP-MESSAGE-GW that only supports short message service registration; or a logical function entity that supports multiple service registrations at the same time. The IP-GW may be configured in one or more. The IP-GW may be set independently or may be configured as a logical function module in an existing network device, for example, in an AAA server.

In the above process, the mentioned service registration request may be registered in the user information storage unit. The IP-GW may directly register the current service registration request with the user information storage unit. The server registers the current service registration request with the user information storage unit. The user information storage unit may be an HLR or an HSS.

In the above process, the IP-GW that interacts with the PDG may be a specified IP-GW, for example, the IP-GW carried by the IP Client when the service registration request is initiated, or the IP-GW that is directly connected to the PDG. For example, the IP-GW of the access network of the user terminal that is associated with the PDG; or the IP-GW to which the IP client belongs.

The specific implementation flow of the method of the present invention will be described in detail below by means of two specific embodiments and the accompanying drawings.

Embodiment 1:

In this embodiment, the user terminal is an IP client, the IP-GW is an IP-MESSAGE-GW that supports short message service registration, the user information storage unit is an HLR/HSS, and the IP-MESSAGE-GW registers the current service through an AAA server. Request to register on the HLR/HSS. The specific processing procedure of this embodiment is shown in FIG. 7, and includes the following steps:

Step 701: The IP client interacts with the related PDG to establish an IP tunnel. The tunnel establishment process is an existing process specified by the standard, and is not described here. The PDG is business related PDG.

Step 702: The IP client sends a service registration request message to the PDG via the tunnel established with the PDG, where the request message carries the IP-MESSAGE-GW identification information and the identity information of the IP client itself. The IP-MESSAGE-GW identification information may be sent in a domain name format, and the PDG obtains the address information of the IP-MESSAGE-GW by using the domain name resolution manner; the IP client's own identification information may adopt a network access identifier (NAI) .

It should be noted that: the service registration request sent by the IP client may not carry the IP-MESSAGE-GW identification information, and the PDG directly uses the IP-MESSAGE-GW contacted by itself to forward the service registration request to the IP-MESSAGE-GW contacted by itself. Or, the PDG parses the IP-MESSAGE-GW to which the IP client belongs according to the IP client identification information carried in the service registration request, such as the NAI, and forwards the service registration request to the parsed IP-MESSAGE-GW.

Step 703 704: After receiving the service registration request, the PDG checks the correspondence between the source IP address and the assigned tunnel identifier (Tunnel lD) in the request sent by the IP client, and ensures that the IP client registers the request. After the check is passed, the PDG obtains the The IP-MESSAGE-GW address information is forwarded to the corresponding IP-MESSAGE-GW, and the forwarded service registration request carries the IP client identification information.

Here, the PDG obtains the IP-MESSAGE-GW address information, which may be obtained according to the information in the service registration request, or may be obtained according to the IP-MESSAGE-GW information of the contact.

Step 705: The IP-MESSAGE-GW that receives the service registration request parses the address information of the AAA server to which the current IP client is registered according to the IP client identification information in the request, and then the IP-MESSAGE-GW obtains the address information according to the obtained address information. The AAA server sends a request user information message, which may carry IP Client identification information, such as NAI, and SS7 address information of the IP-MESSAGE-GW.

Here, before the IP client establishes a tunnel with the PDG, the IP client needs to register to the AAA. In the server, the process of registering in the AAA server is an existing process specified by the standard, and is not described here.

Step 706: After receiving the requesting user information message, the AAA server obtains the relevant registration information of the IP client in the AAA server according to the IP client identification information carried in the message, such as the NAI, and then initiates a registration process to the HLR/HSS, namely: The HLR/HSS sends a registration request, which carries the permanent identifier of the IP client and the address information of the IP-MESSAGE-GW, and notifies the HLR/HSS that the service information of the IP client has been registered in the IP-MESSAGE-GW.

Here, the permanent identifier of the IP client may be MSISDN or IMSI; the address information of the IP-MESSAGE-GW is sent in SS7 encoding.

Step 707: After receiving the registration request, the HLR/HSS stores the SS7 address information of the IP-MESSAGE-GW, and learns that the IP client can access the PS domain of the 3GPP through the IP network, and uses the services of the PS domain. At this time, the HLR/HSS can store the corresponding identifier, such as storing the IP-attached, indicating that the IP client can use the IP to access the services of the PS domain. The HLR/HSS then returns a registration response to the AAA server.

Here, optionally, the HLR/HSS may further notify the application server (AS, the registration information of the IP client in the HLR/HSS, such as the IP-MESSAGE-GW address information.

Application Server).

In this embodiment, IP client identification information can be statically configured in the HLR/HSS.

The correspondence between the IP-MESSAGE-GW addresses. In this case, it is not necessary to dynamically notify the HLR/HSS of the IP-MESSAGE-GW information registered by the IP Client every time the service is registered. Therefore, the above step 706 and Step 707 can be omitted.

Step 708: After receiving the successful registration response returned by the HLR/HSS, the AAA server returns a user information message to the IP-MESSAGE-GW, where the message can carry the IP address.

Permanent identification information of the client, such as MSISDN or IMSI;

The IP-MESSAGE-GW stores the permanent ID of the IP Client and the IP address of the IP Client. Corresponding relationship, further, the IP-MESSAGE-GW can also store the correspondence between the PDG address learned in step 702 and the IP address of the IP client.

Here, the correspondence between the IP client's permanent identity and the IP client's IP address can be stored in a separate database by the IP-MESSAGE-GW or AAA server, which can be opened to other network entities for access.

Steps 709 to 710: The IP-MESSAGE-GW returns a service registration response message to the PDG, and after receiving the PDG, returns a service registration response message to the IP client. Embodiment 2:

In this embodiment, the user terminal is an IP client, the IP-GW is an IP-MESSAGE-GW that supports short message service registration, and the user information storage unit is an HLR/HSS, and the IP-MESSAGE-GW directly registers the current service registration request. Go to HLR/HSS. The specific processing procedure of this embodiment is shown in FIG. 8, and includes the following steps:

Steps 801 to 804: The entire processing and description of steps 701 to 704 in the first embodiment are completely the same.

Step 805: After receiving the service registration request, the IP-MESSAGE-GW parses the permanent identification information of the IP client, such as the IMSI, according to the IP client identification information in the request, and obtains the address information of the HLR/HSS to which the IP client belongs according to the IMSI. Then, the IP-MESSAGE-GW sends a registration request message to the HLR/HSS, where the registration request may carry the IP Client identification information, such as the IMSI obtained by the NAI parsing, and may also carry the SS7 address information of the IP-MESSAGE-GW.

Step 806: After receiving the registration request of the IP-MESSAGE-GW, the HLR/HSS obtains information about the IP Client stored by the IP client, such as the MSISDN, the service information, etc. according to the identity information of the IP client, such as the IMSI; and, the HLR /HSS stores the SS7 address information of the IP-MESSAGE-GW.

Through this registration request HLR/HSS, it can be known that the IP Client can access the PS domain of the 3GPP through the IP network and use the services of the PS domain. At this point, the HLR/HSS can store the corresponding identification. If IP-attached is stored, it indicates that the IP client can access the services of the PS domain through IP.

Then, the HLR/HSS returns a registration response to the IP-MESSAGE-GW, where the response carries information about the IP Client, such as MSISDN, service information, AAA server address information, and the like.

Here, optionally, the HLR/HSS may further notify the application server of the registration information of the IP client in the HLR/HSS, such as the address information of the IP-MESSAGE-GW.

In this embodiment, the mapping between the IP client identification information and the IP-MESSAGE-GW address can be statically configured in the HLR/HSS. In this case, the IP client is not required to be dynamically registered every time the service is registered. The IP-MESSAGE-GW information is notified to the HLR/HSS, and therefore, the above steps 805 and 806 may be omitted.

Step 807: The IP-MESSAGE-GW stores the IP client related information obtained from the HLR/HSS, for example, the correspondence between the permanent identifier MSIDSN of the IP client and the IP address of the IP client; further, IP-MESSAGE at this time The GW may also store the correspondence between the PDG address learned in step 802 and the IP address of the IP client.

Then, the IP-MESSAGE-GW sends a registration request to the AAA server according to the AAA server address information returned by the HLR/HSS, and carries the IP Client identification information and the IP-MESSAGE-GW address information. Wherein, 1? (^1^ identification information may be]\^180 IP-MESSAGE-GW address information may be address information in SS7 format.

After receiving the registration request, the AAA server stores the IP-MESSAGE-GW address information of the IP client.

Steps 808 to 809: The IP-MESSAGE-GW returns a service registration response message to the PDG. After receiving the service registration response sent by the IP-MESSAGE-GW, the PDG returns a service registration response message to the IP client. For the above two embodiments, after the IP client completes the service registration process in the IP-MESSAGE-GW, the MO process or the MT process of the short message service may be subsequently performed. In the SM-MO process, the IP client sends a short message to the IP-MESSAGE-GW via the PDG. After receiving the short message of the IP client, the IP-MESSAGE-GW can send an authentication request to the AAA server requesting the AAA server to the IP address. The client sends the short message service capability for authentication. After the authentication succeeds, the IP-MESSAGE-GW sends the short message to the SM-SC via the SMS-IWMSC/SMS-GMSC.

For the second embodiment, since the IP-MESSAGE-GW can obtain the service information of the IP client from the HLR/HSS in steps 806-807, in the SM-MO process, the IP client can be sent by the IP-MESSAGE-GW. The service capability of the short message is authenticated, and the AAA server does not need to be authenticated.

In the SM-MT process, when the GMSC/SMS-IWMSC obtains the routing information of the IP client from the HLR/HSS, the HLR/HSS can return the SS7 address of the IP-MESSAGE-GW; the GMSC/SMS-IWMSC can be sent to the corresponding IP- The MESSAGE-GW sends a short message, and the message carries the user identifier that needs to receive the short message, such as the MSISDN. After receiving the short message, the IP-MESSAGE-GW may first send an authentication request to the AAA server, requesting the AAA server to correspond to the MSISDN. The user can receive the service capability of the short message for authentication. After the AAA server is successfully authenticated, the IP-MESSAGE-GW matches the IP address of the corresponding IP client according to the MSISDN, and matches the IP address of the IP client to the corresponding PDG. The address sends a short message to the corresponding PDG. The PDG sends a short message to the IP client through the tunnel established with the IP client.

For the second embodiment, since the IP-MESSAGE-GW can obtain the service information of the IP client from the HLR/HSS in step 806 807, in the SM-MT process, the IP client can be shortly received by the IP-MESSAGE-GW. The service capability of the message is authenticated, and there is no need to request an AAA server for authentication.

In the processing flow of the above two embodiments, IP-MESSAGE-GW is used for WLAN IP. The client accesses the service gateway of the SMS service in the 3GPP PS domain. In practical applications, since the registration process of other services, such as the LCS service, is similar to the registration process of the short message described above, the IP-MESSAGE-GW can be replaced with an IP-GW that supports different service registrations. The above registration process can also be used universally. The WLAN IP Client accesses the service registration process before all services in the 3GPP PS domain.

The above is only the preferred embodiment of the present invention and is not intended to limit the scope of the present invention.

Claims

Claim

A service registration method based on IP access, characterized in that the method comprises the following steps:

The method according to claim 1, wherein the initiating service registration request in step a specifically includes:

The method according to claim 2, wherein the packet data gateway in step a2 further comprises, before forwarding the service registration request,: checking according to the source IP address in the request sent by the current user terminal and the assigned tunnel identifier After the validity of the user terminal is checked, the service registration request is forwarded.

The method according to claim 2 or 3, wherein the IP gateway is an IP gateway associated with the packet data gateway, and the forwarding in step a2 is: a packet receiving a service registration request. The data gateway forwards the service registration request directly to the IP gateway that is associated with itself.

The method according to claim 2 or 3, wherein the IP gateway is an IP gateway to which the current user terminal belongs, and the step a2 further comprises: the packet data gateway receiving the service registration request is carried according to the service registration request. The user terminal identifier resolves the IP gateway to which the current user terminal belongs, and then forwards the service registration request to the IP gateway to which the current user terminal belongs.

6. The method according to claim 2 or 3, characterized in that the business described in step a1 The IP registration identifier information is further carried in the registration request.

The method according to claim 6, wherein the step a2 further comprises: the packet data gateway receiving the service registration request parses the address information of the IP gateway according to the IP gateway identifier carried in the service registration request, and then The parsed IP gateway forwards the service registration request.

The method according to claim 2 or 3, wherein the user terminal is identified as a network access identifier.

9. The method according to claim 1, wherein the storing the user's service registration information in step b is: the IP gateway registers its own information with the user information storage unit.

The method according to claim 1, 2, 3 or 9, wherein the service registration request carries the user terminal identifier in step a, and the IP gateway stores the service registration information of the user in step b. Includes:

The IP gateway resolves the address information of the AAA server to which the current user terminal is registered according to the user terminal identifier carried in the request, and then sends a request user information message to the AAA server;

The method according to claim 10, wherein the user terminal is an IP client accessed through an IP network.

The method according to claim 10, wherein the user information storage unit is a home location register or a home subscription subscriber server.

The method according to claim 10, wherein the address of the IP gateway is The SS7 address information of the SS7 is the IP gateway.

The method according to claim 10, wherein the step M3 further comprises: storing a correspondence between the permanent identifier of the user terminal and the IP address of the user terminal.

15. The method according to claim 14, wherein the correspondence is stored in a separately set database, the database is located in an IP gateway, or is located in an AAA server.

The method according to claim 10, further comprising the step of: bl3 further comprising: storing, by the IP gateway, a correspondence between the packet data gateway and the IP address of the user terminal.

17. The method according to claim 14, wherein the user terminal is permanently identified as MSISDN or is IMSI.

The method according to claim 10, wherein after the user information storage unit receives the registration request, the step bl3 further comprises: the user information storage unit notifying the application server that the user terminal can access the network service through the IP.

The method according to claim 1, 2, 3 or 9, wherein the service registration request carries the user terminal identifier in the step a, and the service registration information of the IP gateway storage user in the step b is specifically included. :

B21. The IP gateway parses the address information of the user information storage unit to which the current user terminal belongs according to the user terminal identifier carried in the request, and then sends a registration request to the user information storage unit;

20. The method according to claim 19, wherein the user terminal is an IP client accessed through an IP network.

21. The method according to claim 19, wherein the user information storage list The element is the home location register, or is the home subscription server.

The method according to claim 19, wherein the address information of the IP gateway is SS7 address information of the IP gateway of the IP gateway.

The method according to claim 19, wherein the step b22 further comprises: storing a correspondence between the permanent identifier of the user terminal and the IP address of the user terminal.

24. The method according to claim 23, wherein the correspondence is stored in a separately set database, the database is located in an IP gateway, or is located in an AAA server.

The method according to claim 19, wherein the step b22 further comprises: the IP gateway storing a correspondence between the packet data gateway and the user terminal IP address.

The method according to claim 23, wherein the user terminal is permanently identified as an MSISDN or an IMSI.

The method according to claim 19, wherein after the user information storage unit receives the registration request, the step b22 includes: the user information storage unit notifies the application server that the user terminal can access the network service through the IP.

The method according to claim 19, wherein the method further comprises: b23. After receiving the registration response, the IP gateway notifies the AAA server that the current user terminal is registered.

In the IP gateway, the AAA server stores the address information of the IP gateway.

The method according to claim 1, 2, 3 or 9, wherein the user terminal is an IP client accessed through an IP network.

30. The method according to claim 1, 2, 3 or 9, wherein the user information storage unit is a home location register or a home subscription subscriber server.