WO2006037269A1 - Procede d'enregistrement de service par acces ip - Google Patents

Procede d'enregistrement de service par acces ip Download PDF

Info

Publication number
WO2006037269A1
WO2006037269A1 PCT/CN2005/001599 CN2005001599W WO2006037269A1 WO 2006037269 A1 WO2006037269 A1 WO 2006037269A1 CN 2005001599 W CN2005001599 W CN 2005001599W WO 2006037269 A1 WO2006037269 A1 WO 2006037269A1
Authority
WO
WIPO (PCT)
Prior art keywords
gateway
user terminal
registration request
service registration
information
Prior art date
Application number
PCT/CN2005/001599
Other languages
English (en)
Chinese (zh)
Inventor
Wenlin Zhang
Jie Wang
Xiaoqin Duan
Original Assignee
Huawei Technologies Co., Ltd.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Publication of WO2006037269A1 publication Critical patent/WO2006037269A1/fr

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/51Discovery or management thereof, e.g. service location protocol [SLP] or web services

Definitions

  • 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
  • Wireless LAN includes a variety of different technologies.
  • 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.
  • 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.
  • WLANs are used to transport Internet Protocol (IP) packet data packets.
  • IP Internet Protocol
  • 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.
  • AP access point
  • 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.
  • 3GPP 3rd Generation Partnership Project
  • 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.
  • Internet Internet
  • Intranet intranet
  • WLAN access network 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.
  • 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.
  • AAA 3GPP Authentication and Authorization Accounting
  • 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.
  • a primary subscription subscriber server is mainly included.
  • 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. .
  • the WLAN user terminal wants to directly access the Internet/Intranet
  • the user terminal 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.
  • the offline charging system and the OCS record the charging information according to the network usage of the user terminal.
  • the user terminal can apply to the 3GPP home network to access the Internet/Intmnet through the 3GPP access network.
  • 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.
  • the AS allocates a corresponding home PDG to the user terminal.
  • 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.
  • 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.
  • VPN public land mobile network
  • 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 0
  • 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.
  • FIG. 4 is a short message support architecture based on IP access.
  • 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.
  • IP-MESSAGE-GW IP short message gateway
  • 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.
  • MAP Mobile Application Protocol
  • the SM-MO Short Message Mobile Origination
  • 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.
  • 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,
  • IP bearer-based protocol may be WAP, SMPP, MMPP, XML, SIP,
  • 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.
  • 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.
  • 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
  • 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.
  • a service registration method based on IP access comprising the following steps:
  • the user terminal initiates a service registration request to the IP gateway;
  • 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:
  • 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;
  • 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
  • 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.
  • 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.
  • 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:
  • 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;
  • 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;
  • the user information storage unit After receiving the registration request, 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.
  • 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.
  • 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:
  • 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;
  • the user information storage unit After receiving the registration request, 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.
  • the method further includes: the IP gateway storing a correspondence between the packet data gateway and the IP address of the user terminal.
  • 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:
  • the IP gateway 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.
  • 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 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.
  • 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.
  • FIG. 1 is a schematic diagram of a network structure in which a WLAN system communicates with a 3GPP system;
  • FIG. 2 is a schematic diagram of a networking structure of a WLAN operation network
  • FIG. 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. 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.
  • IP-GW functional entity IP gateway
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • Embodiment 1 is a diagrammatic representation of Embodiment 1:
  • 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
  • the IP-MESSAGE-GW registers the current service through an AAA server. Request to register on the HLR/HSS.
  • FIG. 7 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) .
  • NAI network access identifier
  • the service registration request sent by the IP client may not carry the IP-MESSAGE-GW identification information
  • 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.
  • 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.
  • tunnel lD tunnel identifier
  • 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.
  • the IP client Before the IP client establishes a tunnel with the PDG, the IP client needs to register to the AAA.
  • 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.
  • 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.
  • 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.
  • 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.
  • AS application server
  • the registration information of the IP client in the HLR/HSS such as the IP-MESSAGE-GW address information.
  • IP client identification information can be statically configured in the HLR/HSS.
  • 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.
  • 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 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.
  • 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
  • the IP-MESSAGE-GW directly registers the current service registration request. Go to HLR/HSS.
  • FIG. 8 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.
  • 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.
  • the HLR/HSS 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.
  • HLR/HSS 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.
  • 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.
  • 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.
  • the mapping between the IP client identification information and the IP-MESSAGE-GW address can be statically configured in the HLR/HSS.
  • 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.
  • 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.
  • 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.
  • 1? ( ⁇ 1 ⁇ identification information may be] ⁇ 180 IP-MESSAGE-GW address information may be address information in SS7 format.
  • the AAA server 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.
  • the MO process or the MT process of the short message service may be subsequently performed.
  • the IP client sends a short message to the IP-MESSAGE-GW via the PDG.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • IP-MESSAGE-GW is used for WLAN IP.
  • the client accesses the service gateway of the SMS service in the 3GPP PS domain.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Cette invention concerne un procédé d'enregistrement de service par accès IP comprenant les opérations suivantes: (a)le terminal utilisateur actuel envoie la demande d'enregistrement IP au port IP; (b) le port IP qui a reçu la demande d'enregistrement de service du terminal utilisateur actuel stocke l'information d'enregistrement de l'utilisateur, puis adresse une réponse au terminal utilisateur actuel. Ce procédé permet à l'unité de stockage d'informations utilisateur de connaître l'information d'adresse fournie par le port IP et enregistrée par le terminal actuel, de transmettre cette information à d'autres entités pour que le terminal utilisateur effectue l'enregistrement service par le port IP, et de transmettre à l'unité de stockage d'informations utilisateur l'information du port IP à temps pour que la totalité du flux de service puisse être assurée.
PCT/CN2005/001599 2004-10-07 2005-09-29 Procede d'enregistrement de service par acces ip WO2006037269A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200410079318.X 2004-10-07
CNB200410079318XA CN100370774C (zh) 2004-10-07 2004-10-07 一种基于ip接入的业务注册方法

Publications (1)

Publication Number Publication Date
WO2006037269A1 true WO2006037269A1 (fr) 2006-04-13

Family

ID=36142293

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2005/001599 WO2006037269A1 (fr) 2004-10-07 2005-09-29 Procede d'enregistrement de service par acces ip

Country Status (2)

Country Link
CN (1) CN100370774C (fr)
WO (1) WO2006037269A1 (fr)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102098278B (zh) * 2009-12-15 2015-01-21 华为技术有限公司 用户接入方法、系统及接入服务器、接入设备
CN101754355B (zh) * 2009-12-17 2014-03-05 北京握奇数据系统有限公司 一种用户业务注册方法及系统
CN102149133B (zh) * 2010-02-10 2013-10-30 广州科讯技术有限公司 一种移动通信网络业务接入系统及方法
EP2567555A1 (fr) * 2010-05-03 2013-03-13 Interdigital Patent Holdings, Inc. Allocation d'adresses internet (ip) et d'usage pendant une émission de service de messages courts (sms)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6721793B1 (en) * 2000-05-10 2004-04-13 Cisco Technology, Inc. Intellectual property over non-internet protocol systems and networks
KR20040048494A (ko) * 2002-12-03 2004-06-10 엘지전자 주식회사 무선 랜과 범용 이동통신 시스템 망간 연동 방안
WO2004071011A1 (fr) * 2003-02-10 2004-08-19 Telefonaktiebolaget Lm Ericsson (Publ) Pre-initialisation d'une provision de quota prepaye dans des reseaux mobiles 3g

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FI104869B (fi) * 1995-05-24 2000-04-14 Ericsson Telefon Ab L M Menetelmä verkkojen välisen puheyhteyden muodostamiseksi ja älyverkkopalvelu
AU2001264181A1 (en) * 2000-05-30 2001-12-11 Nokia Corporation System and method of controlling application level access of a subscriber to a network
KR101009819B1 (ko) * 2002-06-06 2011-01-19 톰슨 라이센싱 Wlan과 이동 통신 시스템 간의 상호 연동시하이브리드 결합을 위한 논리 지원 노드인 wlan
US8374631B2 (en) * 2003-01-15 2013-02-12 Nokia Corporation Provision of location information in a communication system

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6721793B1 (en) * 2000-05-10 2004-04-13 Cisco Technology, Inc. Intellectual property over non-internet protocol systems and networks
KR20040048494A (ko) * 2002-12-03 2004-06-10 엘지전자 주식회사 무선 랜과 범용 이동통신 시스템 망간 연동 방안
WO2004071011A1 (fr) * 2003-02-10 2004-08-19 Telefonaktiebolaget Lm Ericsson (Publ) Pre-initialisation d'une provision de quota prepaye dans des reseaux mobiles 3g

Also Published As

Publication number Publication date
CN100370774C (zh) 2008-02-20
CN1758614A (zh) 2006-04-12

Similar Documents

Publication Publication Date Title
US9392435B2 (en) Method, system and apparatus for accessing a visited network
EP2560331B1 (fr) Procédé, appareil et système d'accès radio
EP1693988B1 (fr) Procede de selection par un terminal d'abonne de la passerelle de paquets de donnees dans un reseau local sans fil
US8208898B2 (en) Method for managing local terminal equipment accessing a network
US20060109827A1 (en) Method for transmitting service data to wireless local area network users
WO2005004403A1 (fr) Procede de traitement d'informations selectionnees reseau au niveau du terminal d'utilisateur dans un reseau local sans fil
KR20070058614A (ko) 이종 네트워크에서 상호 작업을 위한 고속 컨텍스트 확립
WO2006031927A2 (fr) Procedes, systemes, et produits-programmes informatiques de fonctionnalite d'enregistreur de localisation des visiteurs (vlr) a passerelle sans fil wi-fi
WO2011137644A1 (fr) Procédé, appareil et système pour l'accès d'un terminal à un service
WO2008000192A1 (fr) Procédé d'accès au réseau de terminaux, système d'accès au réseau et équipement de passerelle
WO2005039110A1 (fr) Analyse du traitement d'acces a un service selectionne dans un reseau local radio
WO2009000124A1 (fr) Procede de selection de passerelle dans un reseau sans fil
WO2004064418A1 (fr) Cn0400032 procede de fourniture d'un service de localisation pour utilisateur de reseau local sans fil
WO2005004384A1 (fr) Procede de rejet d'alternative pour information de selection de reseau d'un terminal utilisateur dans un reseau local sans fil
WO2007101389A1 (fr) Procédé, système et dispositif pour localiser un terminal
WO2005071981A1 (fr) Methode interactive de determination par un terminal d'abonne d'informations de selection d'un reseau local sans fil
WO2007000110A1 (fr) Procede de transmission de message par protocole ip a base de protocole de transfert de message
WO2006037269A1 (fr) Procede d'enregistrement de service par acces ip
WO2013110224A1 (fr) Procédé, dispositif, et système de déclenchement de dispositif mtc
WO2006037268A1 (fr) Procede de desenregistrement de service en fonction de l'access ip
WO2005062631A1 (fr) Procede de redirectionnement de passerelle de donnees en paquets dans un reseau local sans fil
WO2004114589A1 (fr) Procede pour transmettre des donnees de trafic a des utilisateurs d'un reseau local radio
WO2005074192A1 (fr) Procede de collecte d'adresse de passerelle de donnees paquets (pdg) pour terminal utilisateur sur reseau local sans fil (wlan)
WO2007085196A1 (fr) Procédé et système d'enregistrement dans un sous-système multimédia ip
CN101166134A (zh) 一种基于ip接入的业务去注册方法

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KM KP KR KZ LC LK LR LS LT LU LV LY MA MD MG MK MN MW MX MZ NA NG NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SM SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): BW GH GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LT LU LV MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase