WO2012068728A1 - 获取用户的ip地址的方法和网络实体 - Google Patents

获取用户的ip地址的方法和网络实体 Download PDF

Info

Publication number
WO2012068728A1
WO2012068728A1 PCT/CN2010/079071 CN2010079071W WO2012068728A1 WO 2012068728 A1 WO2012068728 A1 WO 2012068728A1 CN 2010079071 W CN2010079071 W CN 2010079071W WO 2012068728 A1 WO2012068728 A1 WO 2012068728A1
Authority
WO
WIPO (PCT)
Prior art keywords
user
address
network element
identifier
information
Prior art date
Application number
PCT/CN2010/079071
Other languages
English (en)
French (fr)
Inventor
周汉
吴问付
Original Assignee
华为技术有限公司
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 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2010/079071 priority Critical patent/WO2012068728A1/zh
Priority to EP10860007.3A priority patent/EP2637378A4/en
Priority to CN201080004950.1A priority patent/CN102668489B/zh
Publication of WO2012068728A1 publication Critical patent/WO2012068728A1/zh
Priority to US13/901,046 priority patent/US20130250968A1/en

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements, protocols or services for addressing or naming
    • H04L61/09Mapping addresses
    • H04L61/10Mapping addresses of different types
    • H04L61/106Mapping addresses of different types across networks, e.g. mapping telephone numbers to data network addresses
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements, protocols or services for addressing or naming
    • H04L61/50Address allocation
    • H04L61/5007Internet protocol [IP] addresses
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2101/00Indexing scheme associated with group H04L61/00
    • H04L2101/60Types of network addresses
    • H04L2101/618Details of network addresses
    • H04L2101/654International mobile subscriber identity [IMSI] numbers

Definitions

  • the embodiments of the present invention relate to the field of communications technologies, and in particular, to a method for acquiring an IP address of a user and a network entity. Background technique
  • LTE Long Term Evolution
  • EPS evolved packet system
  • the core network of the wireless evolved network mainly includes three logical functions: MME, Serving Gateway, and PDN Gateway.
  • MME is a mobility management entity responsible for NAS signaling and NAS signaling encryption, roaming, and tracking functions. , assign user temporary identity, security function, etc., which corresponds to the control plane part of the current SGSN system SGSN.
  • the Serving Gateway (S-GW) is responsible for local mobility anchors and mobility anchors within the 3GPP system as well as lawful interception related information; the PDN Gateway (P-GW) is responsible for policy enforcement and billing and for legitimate interception related functions.
  • the communication model described in Figure 1 is currently mainly for H2H (Human to Human) communication applications, and the M2M (Machine to Machine) application refers to one or more network elements without human intervention.
  • Network communication such as traffic control and management, factory monitoring, remote meter reading and other applications.
  • the M2M terminal device can connect to the application server for data communication through the wireless evolution network.
  • the M2M application can still rely on the network architecture described in Figure 1. With the development, the future network architecture diagram may be different.
  • MTC Server application server
  • the network triggering terminal initiates the connection establishment process is an activation process initiated by the network side.
  • the gateway receives the data packet sent to the user, if there is no PDP context (bearer) information of the user on the gateway, the gateway performs the following processing: The gateway learns the IP address of the user according to the received data packet, and the gateway according to the configured IP address and The mapping relationship between the user IMSIs is used to know the IMSI of the user. The gateway learns the information of the mobility management network element attached to the user according to the learned IMSI addressing subscription database.
  • the gateway sends a packet notification request message to the learned mobility management network element, and the mobility management network element sends a message requesting activation of the PDP context to the user, and the user initiates a PDP context activation process after receiving the message, thereby initiating a service connection. Establish a process.
  • an activation process initiated by the network side requires that the user needs to have a static IP address, and the network needs to configure the static IP address of the user in the subscription database and the different network elements of the gateway, and the application server also You need to configure the user's IP address information. On the gateway, you also need to configure the mapping between the user's static IP address and the user's identity IMSI. If the network-side activation mechanism is triggered by the network to the M2M terminal device in the M2M scenario, the mapping between the static IP address of the user and the identity IMSI of the user needs to be met.
  • the IP address will be short. Further, it also causes a large amount of configuration information to be configured on the gateway (GGSN/PGW). Since the gateway does not have a dedicated database function, the gateway implementation is quite complicated. In addition, the static IP address of the M2M terminal device needs to be configured on different NEs of the subscription database, gateway and application server, which will greatly increase the workload of operation and maintenance. Summary of the invention
  • An embodiment of the present invention provides a method for acquiring an IP address of a user and a network entity, which are used to solve the present problem.
  • An embodiment of the present invention provides a method for obtaining an IP address of a user, where: the first network element receives a message that is sent by the second network element to obtain an IP address of the user; and the first network element allocates an IP address to the user, where The IP address is sent to the second network element; the query message that carries the IP address sent by the gateway is received, the identifier of the user is obtained, and the identifier of the user is sent to the gateway.
  • the embodiment of the present invention provides another method for obtaining an IP address of a user, including: receiving, by the first network element, a message that is sent by the second network element to obtain an IP address of the user; and acquiring, by the first network element, the IP address of the user according to the The message learns the identifier of the user, and assigns an IP address to the user, and sends the identifier of the user and the IP address to the gateway; after receiving the notification message sent by the gateway, the first network element sends the IP address of the user. Send to the second network element.
  • the embodiment of the present invention provides a network entity, including: a receiving unit, a first learning unit, an allocating unit, and a sending unit, where the receiving unit receives a message that is sent by the second network element to obtain an IP address of the user; The sending unit sends the IP address to the second network element; the receiving unit receives the query message that is sent by the gateway and carries the IP address; the first learning unit obtains the identifier of the user according to the IP address; The unit sends the identity of the user to the gateway.
  • the embodiment of the present invention provides another network entity, including: a receiving unit, a sending unit, an allocating unit, and a first learning unit, where the receiving unit receives a message that is sent by the second network element to obtain an IP address of the user; Obtaining an identifier of the user according to the message of obtaining the IP address of the user, the allocation unit assigns an IP address to the user; the sending unit sends the identifier of the user and the IP address to the gateway; and the receiving unit receives the notification message sent by the gateway. Afterwards, the sending unit sends the IP address of the user to the second network element.
  • the first network element allocates an IP address to the user, and the second network element and the gateway obtain the IP address, so that the second network element can establish a connection with the user, thus solving the existing
  • the static IP cannot be configured for the M2M terminal.
  • the address causes the problem that the second network element cannot obtain an IP address.
  • FIG. 1 is a network structure diagram of a prior art provided
  • FIG. 2 is a schematic flowchart of a method for obtaining an IP address of a user according to Embodiment 1 of the present invention
  • FIG. 3 is a schematic signaling diagram of a method for obtaining an IP address of a user according to Embodiment 2 of the present invention
  • 3 is a schematic flowchart of a method for obtaining an IP address of a user provided by FIG. 5
  • FIG. 5 is a schematic signaling diagram of a method for obtaining an IP address of a user according to Embodiment 4 of the present invention
  • FIG. 6 is a schematic diagram of acquiring an IP of a user according to Embodiment 5 of the present invention
  • FIG. 7 is a schematic structural diagram of a network entity for obtaining an IP address of a user according to Embodiment 6 of the present invention
  • FIG. 8 is a schematic structural diagram of a system for obtaining an IP address of a user according to Embodiment 7 of the present invention.
  • the first network element in the embodiment of the present invention is a network element having the function of addressing the user (triggering the user to initiate connection establishment), that is, providing the identifier of the user to the core network element (for example: IMSI or MSISDN or IM ⁇ , etc.)
  • the core network element for example: IMSI or MSISDN or IM ⁇ , etc.
  • core network elements for example: SGSN/MME or GGSN/PGW or HLR/HSS, etc.
  • the network element that triggers the function of the user to initiate the connection establishment process (the PDP activation process or the PDN connection establishment process, etc.) according to the identifier of the user.
  • the first network element assigns an IP address to the user in the process of addressing the user (triggering the user to initiate connection establishment).
  • the specific representation of the first network element may be a network element entity having a DNS server or a DHCP server or an AAA server function (ie, a DNS server or a DHCP server or an AAA server function is separately deployed as a separate functional entity device), or A logical network element or a network element entity of a plurality of network elements combined with the foregoing functions (for example, in an M2M application, specifically, an M2M platform or an M2M Proxy, or the first network element is composed of a DNS server and an AAA server)
  • the network element entity or the logical network element of the other logical network element or the network element entity, or other representations, is not limited by the present invention.
  • the first network element may further have the following functions: a.
  • the first network element may maintain a binding (association) relationship between the user name and the IP address of the user; b.
  • the first network element may further have The function of IP address allocation.
  • the second network element in the embodiment of the present invention is a network element that has a function of pushing a service function to a user, and needs to obtain a user's IP address according to a user name (for example, a user's domain name or URI or URL). . Further, after obtaining the IP address of the user, the second network element may send data to the user according to the obtained IP address.
  • the specific representation of the second network element may be an application server (for example, in an M2M application, specifically, an MTC server), or a network element entity of other representations, which is not limited by the present invention.
  • FIG. 2 is a schematic flowchart of a method for obtaining an IP address of a user according to Embodiment 1 of the present invention. In this embodiment, an IP address is allocated to a user by the first network element, and the IP address is sent to the second network element. After receiving the query message carrying the IP address, the gateway sends the IP address of the user to the gateway.
  • the first network element receives a message that is sent by the second network element to obtain an IP address of the user.
  • the message of the user's IP address carries the user's ID or user name.
  • the mapping between the user name and the user's identity is stored in the first network element.
  • the first network element allocates an IP address to the user, and sends the IP address to the second network element. After the IP address is assigned to the user, the first network element allocates an IP address to the user and the identifier of the user or Usernames are associated.
  • the message that obtains the IP address of the user carries the identifier of the user, and establishes a correspondence between the IP address and the identifier of the user.
  • the first network element obtains the identifier of the user by querying the storage information according to the user name, and then establishes a correspondence between the IP address and the identifier of the user.
  • the correspondence between the IP address and the user name is established.
  • the mapping between the user name and the identifier of the user is stored in the first network element, and the identifier of the user's IP address carries the identifier of the user or the user name, and the IP address, the user name, and the identifier of the user are established.
  • the corresponding relationship between the three is stored in the first network element, and the identifier of the user's IP address carries the identifier of the user or the user name, and the IP address, the user name, and the identifier of the user are established. The corresponding relationship between the three.
  • the gateway receives an IP address query message sent by the gateway, and send the identifier of the user to the gateway.
  • the first network element obtains the IP address in the query message, and obtains the identifier of the user according to the IP address query correspondence, or obtains the user name according to the IP address query in the query message, and then queries the storage information according to the user name. Get the user's identity.
  • the method further includes: the gateway learns the mobility management network element of the service user, and sends a notification to the user to establish a connection by using the mobility management network element.
  • the gateway learns that the mobility management network element of the service user is specifically: the first network element learns the information of the mobility management network element of the service user (the address of the SGSN/MME of the service user or the domain name of the SGSN/MME), and the service user The information of the mobility management network element is sent to the gateway; or the first network element learns the location information of the user (the cell information of the user, or the tracking area information, or the routing area information, or the tracking area list information, or the access network identifier).
  • the location information of the user is sent to the gateway, and the gateway queries the server to learn the mobility management network element of the service user according to the location information of the user; or the gateway queries the HSS/HLR to obtain the service user according to the identifier of the user sent by the first network element.
  • the mobility management network element information is sent to the gateway, and the gateway queries the server to learn the mobility management network element of the service user according to the location information of the user; or the gateway queries the HSS/HLR to obtain the service user according to the identifier of the user sent by the first network element.
  • the information about the mobility management network element of the service user is obtained by the first network element as follows: Querying the storage information according to the user name or the identifier of the user or querying the HSS/HLR according to the identifier of the user to obtain the information of the mobility management network element of the service user.
  • the first network element knows the location information of the user, and specifically: querying the storage information according to the user name or the identifier of the user to obtain the location information of the user.
  • the second embodiment is a specific implementation manner of the first embodiment, and is described by using a specific signaling process.
  • Step 1 The second network element sends a message for obtaining the IP address of the user to the first network element (for example, an IP address query or an IP address request message).
  • a message for obtaining the IP address of the user for example, an IP address query or an IP address request message.
  • the message that obtains the IP address of the user carries the user name or user identifier. Specifically, a mapping relationship between the user name and the identifier of the user is stored in the first network element.
  • Step 2 The first network element allocates an IP address to the user.
  • the first network element sends the IP address assigned to the user to the second network element.
  • the first network element learns the identifier of the user according to the storage information according to the user name. For example, the first network element obtains the identifier of the user by querying the mapping relationship between the user name and the identifier of the user according to the user name.
  • the first network element directly obtains the identifier of the user.
  • the step further includes: the first network element associates the IP address assigned to the user with the identity or user name of the user.
  • the first network element may directly establish an association relationship between the IP address assigned by the user and the identifier of the user, or the first network element establishes an IP address to be associated with the user and the user name (because the first network element exists).
  • the correspondence between the user name and the IP address can be further found by the user name, or the first network element establishes a relationship between the IP address, the user name, and the user identifier assigned by the user.
  • Step 3 The second network element sends a data packet to the user according to the obtained IP address of the user, where the data packet is first sent to the gateway.
  • Step 4 After receiving the data packet, the gateway (GGSN/PGW) queries the first network element for the information of the user. Specifically, the GGSN/PGW receives the data packet of the user, and the GGSN/PGW learns the IP address of the user according to the data packet. If there is no context information (bearer or PDP context) of the user (the IP address) on the GGSN/PGW, the GGSN/PGW acquires information of the user (the IP address) from the first network element. For example, the GGSN/PGW queries the first network element for the user's information according to the IP address. The first network element returns information of the user to the GGSN/PGW. The GGSN/PGW queries the first network element for the user's information through a new message or an existing message. The query message carries the IP address of the user.
  • the GGSN/PGW receives the data packet of the user, and the GGSN/PGW learns the IP address of the user according to the data packet. If there is
  • Step 5 The first network element receives the GGSN/PGW query message, and returns the identifier of the user to the GGSN/PGW according to the IP address in the query message. Specifically, after receiving the query message sent by the GGSN/PGW, the first network element obtains the IP address in the query message, and the first network element queries the stored information according to the IP address (for example: the IP address of the user and the user. The associated relationship of the identifier), and the identifier of the user associated with (corresponding to) the above IP address is queried.
  • the IP address for example: the IP address of the user and the user.
  • the associated relationship of the identifier the identifier of the user associated with (corresponding to) the above IP address is queried.
  • the first network element may further carry location information (such as cell information) where the user (especially for a low mobility user, that is, a user whose location is fixed or only moves in a specific area) is located in the query response message.
  • location information such as cell information
  • the specific process is as follows:
  • the first network element stores the location information of the user or the information of the SGSN/MME of the service user, and the first network element queries the location information of the user or the SGSN/MME of the service user according to the obtained user name or the identifier of the user.
  • Information The information about the location of the user on the first network element or the information of the SGSN/MME of the service user may be: a.
  • the location information of the user or the information of the SGSN/MME of the service user may be tied to the identifier or username of the user. Pre-configured in the first network element; b.
  • the GGSN/PGW In the PDP context activation initiated by the user or the PDN connection establishment process (including the Attach process), the GGSN/PGW notifies the location information of the user or the information of the SGSN/MME of the service user.
  • the GGSN obtains the location information of the user or the information of the SGSN/MME of the serving user, and the GGSN/PGW is directed to the first network element.
  • the Register message carries the identifier of the user, and the location information of the user or the information of the SGSN/MME of the service user
  • the first network element stores the location information of the user or the information of the SGSN/MME of the service user (first network) Yuan will be the user's location
  • the information of the SGSN/MME of the information or service user is bound to the identifier of the user, or the location information of the user or the SGSN/MME of the service user may be used because of the relationship between the identifier of the user and the username on the first network element. Bind to the username).
  • the PDP context or PDN connection of the user may be deleted (including the user being in an isolated state).
  • the first network element may also query the information of the serving user's SGSN/MME (the SGSN/MME information attached by the user) through the HLR/HSS. Specifically, the first network element sends a query message to the HLR/HSS, where the query message carries the identifier of the user.
  • the HLR/HSS obtains the SGSN/MME attached to the user by querying the user's registration information according to the user's identity, and the HLR/HSS sends the SGSN/MME to which the user attaches to the first network element.
  • the first network element may further provide the APN information in the query response message to the GGSN.
  • the APN information used by the user is stored in the first network element.
  • the first network element queries the APN used by the user according to the user name or the identifier of the user.
  • the first network element needs to be addressed to the GGSN/PGW that can serve the user under the first network element.
  • the first network element configuration may serve information of the GGSN/PGW of the above user (for example: address or FQDN of the GGSN/PGW).
  • the first network element configures the information of the GGSN/PGW that can serve the above group according to the group identification of the group to which the user belongs (for example: Group ID, APN, IMSI number segment, etc.).
  • the first network element learns the group to which the user belongs according to the identifier of the user or the APN used by the user, and then the first network element according to the obtained group to which the user belongs.
  • the group identifier queries the information of the GGSN/PGW corresponding to the group identifier configured on the group identifier.
  • the Diameter or Radius protocol can be used between the first network element and the GGSN/PGW (requires enhanced extension).
  • Step 6 If the first network element provides the location information of the user or the SGSN/MME of the serving user to the GGSN/PGW in step 5, the GGSN/PGW may be based on the location information of the user or the information of the SGSN/MME of the serving user. Know the SGSN/MME of the service user (user can attach Or the SGSN/MME to which the user has attached.
  • the first network element provides information to the GGSN/PGW of the serving user's SGSN/MME (for example, the address or FQDN of the SGSN/MME), the SGSN/MME of the serving user is directly informed.
  • the GGSN/PGW can query the server according to the location information of the user (for example, a DNS server, or The GGSN's own server) gets the information of the SGSN/MME.
  • the GGSN/PGW sends a query request to the DNS server, where the query message carries the RA or the TA or the access network identifier, and the DNS server parses the information of the SGSN/MME according to the RA or the TA or the access network identifier, and sends the information to the GGSN. /PGW.
  • the association between the RA and the SGSN or the information of the TA and the MME is configured on the GGSN/PGW.
  • the GGSN/PGW queries the mapping relationship to obtain the SGSN/MME.
  • Step 7 If, in step 5, the first network element does not provide the GGSN with the location information of the user or the SGSN/MME of the serving user in the connection establishment request message, the GGSN requests the SGSN of the service user from the HLR according to the identifier of the user. /MME.
  • the process in which the GGSN obtains the information of the SGSN that the user attaches to the HLR belongs to the prior art, and details are not described herein again.
  • Step 8 The GGSN/PGW knows the SGSN/MME that can serve the user in step 6 or step 7.
  • the GGSN/PGW sends a connection establishment indication message to the learned SGSN/MME.
  • the connection establishment indication message may be a PDU Notification Request message (the GGSN sends to the SGSN).
  • the PDU Notification Request message carries the identifier of the user (for example, IMSI).
  • the GGSN carries the location information of the user to the SGSN in the PDU Notification Request message.
  • the GGSN carries the APN used by the user to the SGSN in the PDU Notification Request message.
  • the SGSN can notify the APN To the user, the user is prompted to initiate a connection establishment according to the APN.
  • the connection establishment indication message may be a Downlink Notification Request message (the PGW is sent to the SGW, and the SGW is sent to the MME).
  • the Downlink Notification Request message carries the identifier of the user (for example, IMSI).
  • the PGW carries the location information of the user to the MME in the Downlink Notification Request message.
  • Step 9 The SGSN/MME triggers the user to initiate a connection establishment process.
  • the connection establishment process refers to a PDP context activation process or a PDN connection establishment process.
  • the SGSN In GERAN/UTRAN, if the user is in the attached state and the user is in the connected state, the SGSN sends a Request PDP Context Activation message to the user. If the user is in the idle state (Idle or Standby state), the SGSN pages the user. After the user receives the paging message, the user establishes a connection with the SGSN, and the SGSN sends a Request PDP Context Activation message to the user. After receiving the above Request PDP Context Activation message, the user initiates a PDP context activation process. If, in step 5, the SGSN obtains the location of the user (for example, the RA where the user is located), the SGSN pages the user within the location range of the user.
  • the SGSN sends a paging message to the user, where the paging message carries the IMSI of the user.
  • the user After the user receives the IMSI paging message, the user initiates an attach procedure.
  • the SGSN sends a Request PDP Context Activation message to the user.
  • the user After the user receives the Request PDP Context Activation message, the user initiates a PDP context activation process.
  • the SGSN sends a paging message to the user, where the paging message carries the IMSI of the user.
  • the IMSI paging message further carries the indication information indicating that the user initiates the PDP context activation process. .
  • the user After the user receives the IMSI paging message, the user initiates an attach procedure, and then the user initiates a PDP context activation process according to the foregoing indication information.
  • the SGSN obtains the location of the user (for example, the RA where the user is located), the SGSN pages the user within the location range of the user.
  • the MME sends a paging message to the user, where the paging message carries the IMSI of the user.
  • the user After the user receives the IMSI paging message, the user initiates an attach procedure. In the attach process, the user establishes a PDN connection.
  • the MME obtains the location where the user is located (for example, the TA where the user is located), the MME pages the user within the location range in which the user is located.
  • Step 10 The user initiates a PDP context activation process or a PDN connection establishment process.
  • the user initiates a PDP context activation process or a PDN connection establishment process according to the trigger of the SGSN/MME.
  • the gateway sends the data packet to the terminal, thereby establishing a connection between the user and the second network element.
  • the IP address is allocated to the user by the first network element, and the IP address is sent to the second network element.
  • the gateway After receiving the query message carrying the IP address, the gateway sends the IP address of the user to the gateway, so the gateway And the second network element obtains the IP address of the user, so that the user can establish a connection with the second network element, and the second network element cannot be configured because the static IP address cannot be configured for the M2M terminal when the network side push service is used in the prior art. Get the problem with the IP address.
  • FIG. 4 is a schematic flowchart of another method for obtaining an IP address of a user according to Embodiment 3 of the present invention.
  • an IP address is allocated by the first network element, and after the user establishes a connection, the IP address is sent to the second. Network element.
  • the first network element receives a message that is sent by the second network element and obtains an IP address of the user.
  • the message carries the identity of the user or the username.
  • the first network element obtains the identifier of the user according to the message for obtaining the IP address of the user, and assigns an IP address to the user, and sends the identifier of the user and the IP address to the gateway.
  • the first network element Obtaining, by the first network element, the identifier of the user according to the message of obtaining the IP address of the user, the message that the user obtains the IP address of the user carries the identifier of the user, where the first network element obtains the user from the user
  • the user of the IP address obtains the identifier of the user; or the message of the user's IP address carries the user name, and the first network element queries the storage information according to the user name to obtain the identifier of the user.
  • the method further includes: the gateway knowing the mobility management network element of the service user;
  • the sexual management network element sends a notification to the user to establish a connection establishment request.
  • the gateway sends a notification message to the first network element.
  • the gateway is informed that the mobility management network element of the service user is: the first network element learns information about the mobility management network element of the service user (the address of the SGSN/MME of the service user or the domain name of the SGSN/MME), and the service user
  • the information of the mobility management network element is sent to the gateway; or the first network element obtains location information (cell information, or tracking area information, or routing area information, or tracking area list information, or access network identifier) of the user.
  • the gateway Sending the location information of the user to the gateway, the gateway querying the server to learn the mobility management network element serving the user according to the location information of the user; or the gateway according to the identifier of the user sent by the first network element to the HSS/HLR Query the information of the mobility management network element of the service user.
  • the information that the first network element learns about the mobility management network element of the service user is: querying the storage information according to the user name or the identifier of the user, or querying the HSS/HLR according to the identifier of the user to obtain the information of the mobility management network element of the service user. .
  • the first network element obtains the location information of the user by: querying the storage information according to the user name or the identifier of the user to obtain the location information of the user.
  • the first network element After receiving the notification message sent by the gateway, the first network element sends the IP address of the user to the second network element.
  • Embodiment 4 is a specific implementation manner of Embodiment 3, and is described by a specific signaling process.
  • Step 1 The second network element (application server, for example, MTC Server) sends a message (for example, an IP address query or an IP address request message) to the first network element (M2M platform/M2M Proxy) to obtain the user's IP address.
  • a message for example, an IP address query or an IP address request message
  • the message carries the username or carries the identifier of the user.
  • Step 2, 3 After the first network element receives the request message for obtaining the IP address sent by the second network element, the first network element allocates an IP address to the user, and the IP address is in the connection establishment request message. Carry it to the gateway.
  • the first network element passes through a gateway (GGSN/PGW) to enable a user to initiate a connection establishment procedure (a PDP context activation or a PDN connection establishment procedure).
  • the first network element sends a connection establishment request message to the gateway, where the message carries the identifier of the user (IMSI or MSISDN or IM ⁇ , etc.).
  • the first network element may obtain the identifier of the user by querying the storage information according to the username carried in the message sent by the second network element in step 1.
  • the specific method is that the first network element stores an association between the identifier of the user and the user name, and the first network element queries the association relationship according to the username sent by the second network element to obtain the identifier of the user.
  • the first network element may also obtain the identifier of the user directly in the message sent by the application server in step 1. For the specific process, refer to the corresponding part of step 2 in the second embodiment.
  • the first network element may carry the APN used by the user in the connection establishment request message.
  • the specific process refer to the corresponding part of step 5 in the second embodiment.
  • the first network element carries information (the address or FQDN of the SGSN/MME) of the mobility management network element of the service user (user attached) in the connection establishment request message.
  • the method for obtaining the mobility management network element information of the service user by the first network element may be (for the specific process, refer to the corresponding part of step 5 in the second embodiment).
  • the first network element sends a query message to the HLR/HSS, and queries the user to attach the
  • the query message carries the identifier of the user (IMSI or MSISDN or IM ⁇ , etc.).
  • the HLR/HSS queries the registration information of the user according to the identifier of the user to obtain the information of the SGSN/MME to which the user is attached, and then sends the information to the first network element.
  • the first network element queries the storage information according to the user name of the user or the identifier of the user to obtain information about the mobility management network element of the service user.
  • the first network element obtains the user name or the identifier of the user, and then queries the stored user name or the binding relationship table between the user identifier and the information of the SGSN/MME of the service user, thereby obtaining the mobile user's mobile Information about the management of network elements.
  • the first network element obtains the user name or the identifier of the user, and then queries the stored user name or the binding relationship table between the user identifier and the information of the SGSN/MME of the service user, thereby obtaining the mobile user's mobile Information about the management of network elements.
  • the first network element After the first network element obtains the user name or the identifier of the user, query the locally stored user name or the user's identifier and the location information of the user (for example, the cell information of the user, or the tracking area information, or the route) The binding relationship table between the area information, or the tracking area list information or the identification information of the access network, thereby obtaining the location information of the user.
  • the first network element is obtained according to the obtained location information of the user.
  • the server (for example, a DNS server) queries information of the mobility management network element of the service user.
  • the first network element carries the location information of the user in the connection establishment request message and sends the location information to the gateway.
  • Step 4 If, in step 3, the first network element does not send information or location information of the mobility management network element of the service user to the gateway, the gateway may query the HLR/HSS for mobility of the monthly service user. Manage information about network elements. Specifically, the gateway sends a routing information message to the HLR/HSS, where the message carries the identifier of the user. The HLR/HSS queries the information registered by the user, and sends the information of the mobility management network element of the service user to the gateway.
  • the gateway queries the location information according to the location information.
  • the specific method of the mobility management network element of the user service may be that the gateway is based on the obtained location information of the user (for example, cell information, tracking area information, routing area information, tracking area list, or access network identifier, etc.)
  • a server for example, a DNS server
  • a binding (association) relationship between the location information and information capable of serving a mobility management network element of a user in the location area is stored in the server.
  • Step 5 The gateway sends a connection establishment indication message to the learned SGSN/MME, where the message carries the IP address of the user and the identifier of the user.
  • connection establishment indication message may be a PDU Notification Request message (the GGSN sends to the SGSN).
  • the PDU Notification Request message carries the identifier of the user (for example, IMSI).
  • the first network element provides the GGSN with the location of the user (for example, the RA where the user is located), the first network element carries the location information of the user to the SGSN in the PDU Notification Request message.
  • the GGSN carries the APN used by the user to the SGSN in the PDU Notification Request message.
  • the connection establishment indication message may be a Downlink Notification Request message (the PGW is sent to the SGW, and the SGW is sent to the MME again).
  • the above Downlink Notification Request message carries the identifier of the user (for example: IMSI).
  • the PGW if the first network element provides the location information of the user to the PGW (for example, the TA where the user is located), the PGW carries the location information of the user to the MME in the Downlink Notification Request message.
  • the PGW carries the APN information used by the user to the MME in the Downlink Notification Request message.
  • Step 6 The SGSN/MME triggers the user to initiate a connection establishment process.
  • the connection establishment process refers to a PDP context activation process or a PDN connection establishment process (including an attachment process).
  • the SGSN carries the IP address assigned by the first network element to the user, and the SGSN triggers the user to carry the connection establishment process to carry the IP address of the user to the user, and the user carries the IP address in the activation PDP context request message.
  • the SGSN In GERAN/UTRAN, if the user is in the attached state and the user is in the connected state, the SGSN sends a Request PDP ContextActivation message to the user. If the user is in the idle state (Idle or Standby state), the SGSN pages the user. After the user receives the paging message, the connection between the user and the SGSN is established, and the SGSN sends a Request PDP Context Activation message to the user. After receiving the above Request PDP Context Activation message, the user initiates a PDP context activation process.
  • the SGSN sends a paging message to the user, where the paging message carries the IMSI of the user. After the user receives the IMSI paging message, the user initiates an attach procedure. After the user initiates the attach procedure, the SGSN sends a Request PDP Context Activation message to the user. After the user receives the Request PDP Context Activation message, the user initiates a PDP context activation process.
  • the SGSN obtains the IP address assigned by the first network element to the user in step 5, the SGSN carries the IP address of the user to the user in the Request PDP ContextActivation message, and the user carries the above in the Activate PDP Context Request message. IP address. Or, if the user is in the detached state, the SGSN sends a paging message to the user, where the paging message carries the IMSI of the user. Further, the IMSI paging message further carries the indication information indicating that the user initiates the PDP context activation process. . After the user receives the IMSI paging message, the user initiates an attach procedure, and then the user initiates a PDP context activation process according to the foregoing indication information. If, in step 5, the SGSN obtains the location of the user (for example, the RA where the user is located), the SGSN pages the user within the location range of the user.
  • the SGSN obtains the location of the user (for example, the
  • the MME sends a paging message to the user, and the paging message carries the IMSI of the user.
  • the user After the user receives the IMSI paging message, the user initiates an attaching process.
  • the attach process the user establishes a PDN connection. If, in step 5, the MME obtains the location of the user (for example, the TA where the user is located), the MME pages the user within the location range of the user.
  • Step 7 The user initiates a PDP activation process or a PDN connection establishment process.
  • the user receives the Request PDP Context Activation message sent by the SGSN. If the message carries the IP address assigned by the first network element to the user, the user carries the IP address in the activated PDP context message, and the GSN/PGW is used.
  • the first network element is an IP address assigned by the user as the IP address of the user.
  • Step 8 The gateway sends a notification message to the first network element.
  • the notification message carries the identifier or username of the user.
  • the notification message is used to indicate that the first network element has an IP address assigned to the user.
  • Step 9 The first network element sends the IP address of the user to the second network element (MTC Server).
  • Step 10 The second network element sends data to the user according to the IP address.
  • the IP address and the identifier of the user are sent to the gateway by the IP address assigned by the first network element, and after the user establishes the connection, the IP address is sent to the second network element. Therefore, the gateway and the second network element both obtain the IP address of the user, so that the user can establish a connection with the second network element, and the second network can be configured because the static IP address cannot be configured for the M2M terminal when the network side push service is used in the prior art. The yuan could not get the IP address.
  • FIG. 6 is a schematic structural diagram of a network entity 60 for acquiring an IP address of a user according to Embodiment 5 of the present invention, including a receiving unit 601, a first learning unit 605, an allocating unit 603, and a sending unit 607, where the receiving unit 601 receives the second a message sent by the network element to obtain the IP address of the user; the allocating unit 603 assigns an IP address to the user; the sending unit 607 sends the IP address to the second network element; and the receiving unit 601 receives the IP address that is sent by the gateway and carries the IP address. Querying the message; the first learning unit 605 obtains the identifier of the user according to the IP address; the sending unit 607 sends the identifier of the user to the gateway.
  • the network entity of this embodiment may further include a second learning unit 602, configured to learn, according to the message of acquiring the IP address of the user, the identifier of the user, specifically: the second learning unit 602 The message of obtaining the IP address of the user obtains the identifier of the user; or the message of the user IP address carries the user name, and the second learning unit 602 queries the storage information according to the user name to obtain the identifier of the user.
  • a second learning unit 602 configured to learn, according to the message of acquiring the IP address of the user, the identifier of the user, specifically: the second learning unit 602 The message of obtaining the IP address of the user obtains the identifier of the user; or the message of the user IP address carries the user name, and the second learning unit 602 queries the storage information according to the user name to obtain the identifier of the user.
  • the network entity in this embodiment may further include a relationship establishing unit 604.
  • the second obtaining unit obtains the identifier of the user and the allocating unit 603 allocates an IP address to the user
  • the establishing relationship unit 604 establishes a correspondence between the IP address and the identifier of the user.
  • the first obtaining unit 605 obtains the identifier of the user according to the IP address, and specifically obtains the identifier of the user according to the correspondence between the IP address and the identifier of the user.
  • the establishing relationship unit 604 establishes a correspondence between the IP address and the user name
  • the first learning unit 605 obtains the identifier of the user.
  • the user name is obtained by querying the correspondence between the IP address and the user name according to the IP address in the query message, and then the storage information is obtained according to the user name to obtain the identifier of the user.
  • the network entity of this embodiment may further include a third learning unit 606, where the third learning unit 606 learns information about the mobility management network element of the service user according to the user name or the identifier of the user, and the sending unit 607
  • the information of the mobility management network element of the service user is also sent to the gateway; or the second learning unit obtains the location information of the user according to the user name or the identifier of the user.
  • the sending unit 607 also sends the location information of the user to the gateway.
  • FIG. 7 is a schematic structural diagram of a network entity 70 for obtaining an IP address of a user according to Embodiment 6 of the present invention, including a receiving unit 701, an allocating unit 702, a first learning unit 703, and a sending unit 705, where
  • the receiving unit 701 receives the message of acquiring the IP address of the user sent by the second network element; the first learning unit 703 learns the identifier of the user according to the message of acquiring the IP address of the user; the allocating unit 702 allocates an IP address to the user; The unit 705 sends the identifier of the user and the IP address to the gateway. After the receiving unit 701 receives the notification message sent by the gateway, the sending unit 705 sends the IP address of the user to the second network element.
  • the first obtaining unit 703 according to the message for obtaining the IP address of the user, knows that the identifier of the user specifically includes:
  • the first learning unit obtains the identifier of the user from the message of obtaining the IP address of the user; or the message of the user IP address carries the user name, and the first learning unit queries the storage information according to the user name. Get the user's identity.
  • the network entity of this embodiment may further include a second learning unit 704, where the second learning unit 704 learns information about the mobility management network element of the service user according to the user name or the identifier of the user, and the sending unit 705 The information of the mobility management network element of the service user is sent to the gateway; or the second learning unit 704 learns the location information of the user according to the user name or the identifier of the user, and the sending unit 705 sends the location information of the user to the gateway.
  • the second learning unit 704 learns information about the mobility management network element of the service user according to the user name or the identifier of the user
  • the sending unit 705 sends the location information of the user to the gateway.
  • FIG. 8 is a schematic structural diagram of a network entity for obtaining an IP address of a user according to Embodiment 7 of the present invention.
  • the foregoing method embodiments and device embodiments which are not repeated here.
  • a person skilled in the art can understand that all or part of the steps of implementing the above method embodiments may be completed by using hardware related to program instructions, and the foregoing program may be stored in a computer readable storage medium, and the program is executed when executed.
  • the foregoing storage medium includes: ROM, RAM, magnetic disk or optical disk, etc., which can store various program codes.

Landscapes

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

Description

获取用户的 IP地址的方法和网络实体
技术领域
本发明实施例涉及通信技术领域, 特别涉及一种获取用户的 IP地址的方 法及网络实体。 背景技术
为了应对无线宽带技术的挑战, 保持 3GPP网络的领先优势, 3GPP在 2004年底制定了长期演进计划( LTE, Long Term Evolution )。 在该演进计划 的指导下定义了新的移动通信网络的架构, 该架构与现在的 GPRS/UMTS更 加扁平,并且只保留了分组域, 因此可以称为演进的分组网络( EPS, evolved packet system )。
如图 1所示, 无线演进网络的核心网主要包含 MME、 Serving Gateway, PDN Gateway三个逻辑功能体, 其中的 MME是移动管理实体, 负责 NAS 信令和 NAS信令加密以及漫游、 跟踪等功能, 分配用户临时身份标识、 安全 功能等, 它对应于当前 UMTS 系统内部 SGSN 的控制平面部分。 Serving Gateway (S-GW)负责本地的移动性锚点和 3GPP 系统内部的移动性锚点以 及合法监听相关信息; PDN Gateway (P-GW)则负责策略执行和计费以及合 法监听相关功能。 图 1 所述的通信模型, 当前主要是针对 H2H ( Human to Human )通信的应用, 而 M2M(Machine to Machine)应用指的是一个或者多 个网元之间在不需要人为参与的情况下进行的网络通讯, 如交通控制与管理、 工厂监控、 远程抄表等应用。 M2M的终端设备可以通过无线演进网络连接到 应用服务器进行数据通信。目前 M2M应用仍然可以依托于图 1所述的网络架 构, 随着发展, 以后的网络架构图可能与此不同。
无论是 H2H , 还是 M2M的通信过程中, 都存在网络侧触发终端建立承 载的需求。 尤其是在 M2M应用中, 在 M2M应用中, 由于不存在人为参与, 所以存在行业用户或者应用服务器(MTC Server )触发 M2M终端设备发起 业务的需求。 M2M 终端设备收到触发消息后, M2M 终端设备需要发起连接 建立, 通过无线演进网络与应用服务器进行数据通信。
现在有技术在 H2H的通信系统下, 网络触发终端发起连接建立流程是网 络侧发起的一次激活流程。 网关收到发给用户的数据包后, 如果在网关上没 有用户的 PDP上下文(承载)信息, 则网关执行以下处理: 网关根据接收的 数据包获知用户的 IP地址, 网关根据配置的 IP地址和用户 IMSI之间的映射 关系,获知用户的 IMSI。 网关根据获知的 IMSI寻址签约数据库获知用户所附 着的移动性管理网元的信息。 网关向获知的移动性管理网元发送数据包通知 请求消息, 移动性管理网元向用户发送请求激活 PDP上下文的消息, 用户收 到所述消息后发起 PDP上下文一次激活的流程,从而发起业务连接建立流程。
如上所述, 在 H2H通信系统中网络侧发起的一次激活流程需要的条件是 用户需要有静态 IP地址,网络需要将用户的静态 IP地址分别配置在签约数据 库和网关不同网元上, 应用服务器也需要配置用户的 IP地址信息。 在网关上 还要配置用户静态 IP地址和用户的标识 IMSI之间的映射关系。 如果网络侧 一次激活的机制应用在 M2M场景下由网络对 M2M终端设备进行触发, 则需 要也需要满足配置用户静态 IP地址和用户的标识 IMSI之间的映射关系。 但 是在 M2M应用中, 由于存在海量的 M2M终端设备, 如果为每个 M2M终端 设备都分配静态 IP地址, 将会导致 IP地址短缺。 进一步, 还会导致在网关 ( GGSN/PGW )上配置海量的配置信息, 由于网关并不具有专门的数据库的 功能, 将导致网关实现相当复杂。 另外, M2M终端设备的静态 IP地址需要 配置在签约数据库, 网关和应用服务器不同的网元上, 将会极大的增加操作 维护的工作量。 发明内容
本发明实施例提供一种获取用户的 IP地址方法和网络实体, 用以解决现 有技术中无法为 M2M终端配置静态 IP地址造成网络推送业务时无法获得 IP 地址的问题。
本发明实施例提供了一种获取用户的 IP地址的方法, 包括: 第一网元接 收第二网元发送的获取用户的 IP 地址的消息; 第一网元为所述用户分配 IP 地址,将 IP地址发送给所述第二网元;接收网关发送的携带所述 IP地址的查 询消息, 获知用户的标识, 将所述用户的标识发送给网关。
本发明实施例提供了又一种获取用户的 IP地址的方法, 包括: 第一网元 接收第二网元发送的获取用户的 ip地址的消息; 第一网元根据所述获取用户 的 IP地址的消息获知所述用户的标识,并为用户分配 IP地址,将所述用户的 标识和所述 IP地址发送给网关; 第一网元接收网关发送的通知消息后, 将所 述用户的 IP地址发送给所述第二网元。
本发明实施例提供了一种网络实体, 包括: 接收单元, 第一获知单元, 分配单元和发送单元, 其中, 接收单元接收第二网元发送的获取用户的 IP地 址的消息; 分配单元为用户分配 IP地址;发送单元将 IP地址发送给所述第二 网元; 接收单元接收网关发送的携带所述 IP地址的查询消息; 所述第一获知 单元根据所述 IP地址获得用户的标识; 发送单元将所述用户的标识发送给网 关。
本发明实施例提供了又一种网络实体, 包括: 接收单元, 发送单元, 分 配单元和第一获知单元, 其中接收单元接收第二网元发送的获取用户的 IP地 址的消息; 第一获知单元根据所述获取用户的 IP地址的消息获知所述用户的 标识, 分配单元为用户分配 IP 地址; 发送单元将所述用户的标识和所述 IP 地址发送给网关; 接收单元接收网关发送的通知消息后, 发送单元将所述用 户的 IP地址发送给所述第二网元。
由上述技术方案可知, 本发明实施例中由第一网元为用户分配 IP地址, 第二网元以及网关获得所述 IP地址, 从而第二网元可以和用户建立连接, 因 此解决了现有技术中网络侧推送业务时, 由于无法为 M2M终端配置静态 IP 地址造成第二网元无法获得 IP地址的问题。 附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案, 下面将对实 施例或现有技术描述中所需要使用的附图作简单地介绍, 显而易见地, 下面 描述中的附图仅仅是本发明的一些实施例, 对于本领域普通技术人员来讲, 在不付出创造性劳动的前提下, 还可以根据这些附图获得其他的附图。
图 1为提供的现有技术的网络结构图;
图 2为本发明实施例一提供的获取用户的 IP地址的方法的流程示意图; 图 3为本发明实施例二提供的获取用户的 IP地址的方法的信令示意图; 图 4为本发明实施例三提供的获取用户的 IP地址的方法的流程示意图; 图 5为本发明实施例四提供的获取用户的 IP地址的方法的信令示意图; 图 6为本发明实施例五提供的获取用户的 IP地址的网络实体结构示意图; 图 7为本发明实施例六提供的获取用户的 IP地址的网络实体结构示意图; 图 8为本发明实施例七提供的获取用户的 IP地址的系统结构示意图。 具体实施方式
下面将结合本发明实施例中的附图, 对本发明实施例中的技术方案进行清 楚、 完整地描述, 显然, 所描述的实施例仅仅是本发明一部分实施例, 而不是 全部的实施例。 基于本发明中的实施例, 本领域普通技术人员在没有做出创造 性劳动前提下所获得的所有其他实施例, 都属于本发明保护的范围。 另外本发 明实施例要解决的问题虽然由 M2M应用引起的,但是本发明实施例的技术方案 也可以应用在 H2H通信系统, 以及其他涉及用户的 IP地址的通信系统。
本发明实施例中的第一网元为具有寻址用户 (触发用户发起连接建立) 的 功能的网元, 即向核心网网元提供用户的标识(例如: IMSI或 MSISDN或 IM曰 等), 以供核心网网元(例如: SGSN/MME或 GGSN/PGW或 HLR/HSS等) 根据所述用户的标识触发用户发起连接建立流程的功能( PDP激活流程或 PDN 连接建立流程等), 的网元。所述第一网元在寻址用户(触发用户发起连接建立) 的过程中会为用户分配 IP地址。所述第一网元的具体表现形式可以是具有 DNS 服务器或 DHCP服务器或 AAA服务器功能的网元实体(即 DNS服务器或 DHCP 服务器或 AAA服务器功能单独部署, 为单独的功能实体设备), 或者由具有上 述功能的多个网元组合的逻辑网元或网元实体(例如, 在 M2M应用中, 具体可 以是一个 M2M平台或 M2M Proxy, 或者所述第一网元是 DNS服务器和 AAA 服务器组成的一个其他逻辑网元或网元实体), 或者其他表现形式的网元实体或 逻辑网元, 本发明不作限制。 其中, 第一网元还可以进一步具有以下功能: a、 所述第一网元可以保存用户名和用户的 IP地址之间的绑定(关联)关系; b、 所述第一网元还可以具有 IP地址分配的功能。
本发明实施例中的第二网元为具有向用户推送业务功能的服务器, 需要根 据用户名 (例如: 用户的域名或 URI或 URL等)到其他网元获取用户的 IP地 址的功能的网元。 进一步的, 获得了用户的 IP地址之后, 所述第二网元可以根 据获得的 IP地址向用户发送数据。 所述第二网元的具体表现形式可以是应用服 务器(Application Server, 例如, 在 M2M应用中, 具体可以是 MTC server ), 或者其他表现形式的网元实体, 本发明不作限制。 图 2为本发明实施例一提供的一种获取用户的 IP地址方法的流程示意图, 该实施例中由第一网元为用户分配 IP地址,并将 IP地址发送给第二网元。 当收 到网关携带 IP地址的查询消息后, 向网关发送用户的 IP地址。
201、 第一网元接收第二网元发送的获取用户的 IP地址的消息;
获取用户的 IP地址的消息中携带用户的标识或者用户名; 在第一网元中存 储了用户名和用户的标识之间的映射关系。
202、 第一网元为用户分配 IP地址, 将 IP地址发送给第二网元; 为用户分配 I P地址之后,第一网元将为用户分配的 I P地址与用户的标识或 者用户名关联起来。
具体的,当获取用户的 IP地址的消息中携带了用户的标识, 建立 IP地址与 用户的标识的对应关系。 或者, 当获取用户的 IP地址的消息中携带用户名时, 第一网元根据用户名查询存储信息获得用户的标识, 再建立 IP地址与用户的 标识的对应关系。 或者, 当获取用户的 IP地址的消息中携带用户名时, 建立 IP地址与用户名的对应关系。 或者, 由于第一网元中存储了用户名和用户的标 识之间的映射关系, 无论获取用户的 IP地址的消息中携带了用户的标识还是用 户名, 建立 IP地址、 用户名、 用户的标识的三者对应关系。
203、 接收网关发送的携带 IP地址查询消息, 将用户的标识发送给网关。 具体为:第一网元获得查询消息的中的 IP地址,并才艮据 IP地址查询对应关 系获得用户的标识, 或者根据查询消息中的 IP地址查询获得用户名, 再根据用 户名查询存储信息获得用户的标识。
203之后还包括: 网关获知服务用户的移动性管理网元, 通过移动性管理 网元发送通知用户建立连接。
网关获知服务用户的移动性管理网元具体为: 第一网元获知服务用户的 移动性管理网元的信息 (为服务用户的 SGSN/MME的地址或 SGSN/MME的 域名), 将服务用户的移动性管理网元的信息发送给网关; 或者, 第一网元获 知用户的位置信息 (用户所在的小区信息, 或跟踪区信息, 或路由区信息, 或 跟踪区列表信息, 或接入网标识), 将用户的位置信息发送给网关, 网关根据 的用户的位置信息查询服务器获知服务用户的移动性管理网元; 或者网关根 据第一网元发送的用户的标识向 HSS/HLR 查询获得服务用户的移动性管理 网元的信息。
第一网元获知服务用户的移动性管理网元的信息具体为: 根据用户名或 者用户的标识查询存储信息或者根据用户的标识查询 HSS/HLR 获得服务用 户的移动性管理网元的信息。 第一网元获知用户的位置信息具体为: 根据用 户名或者用户的标识查询存储信息获得用户的位置信息。 如图 3所示, 实施例二为实施例一的具体实现方式, 通过具体的信令流程 进行描述。
步骤 1、 第二网元向第一网元发送获取用户的 IP地址的消息(例如: IP地 址查询或 IP地址请求消息)。
其中, 获取用户的 IP地址的消息中携带用户名或者用户标识。 具体地, 在 第一网元中存储了用户名和用户的标识之间的映射关系。
步骤 2、 第一网元为用户分配 IP地址。 第一网元将为用户分配的 IP地址发 送给第二网元。
如果步骤 1中获取用户的 IP地址的消息携带了用户名, 则第一网元根据根 据用户名查询存储信息获知用户的标识。 例如: 第一网元才艮据用户名查询用户 名和用户的标识之间的映射关系表获得用户的标识。
如果步骤 1中获取用户的 IP地址的消息携带了用户标识, 则第一网元直接 获得用户的标识。
所述步骤进一步包括: 第一网元将为用户分配的 IP地址和用户的标识或用 户名关联起来。 具体的, 第一网元可以直接建立为用户分配的 IP地址和用户的 标识的关联关系,或第一网元建立将为用户分配的 IP地址和用户名关联起来(由 于第一网元上存在用户名和 IP地址的对应关系, 可以进一步通过用户名查找到 用户的标识), 或第一网元将建立为用户分配的 IP地址、 用户名和用户标识三 者关联起来关系。
步骤 3、 第二网元根据获得的用户的 IP地址向用户发送数据包, 所述数据 包先发送到网关。
步骤 4、 网关(GGSN/PGW )收到数据包后, 向第一网元查询用户的信息。 具体地, GGSN/PGW收到用户的数据包, GGSN/PGW根据数据包获知用户的 IP地址。 如果 GGSN/PGW上没有所述用户 (所述 IP地址)的上下文信息(承 载或 PDP上下文), GGSN/PGW向所述第一网元获取用户 (所述 IP地址)的 信息。 例如: GGSN/PGW才艮据 IP地址向所述第一网元中查询用户的信息, 所 述第一网元向 GGSN/PGW返回用户的信息。 GGSN/PGW通过一条新增消息 或现有消息向所述第一网元查询用户的信息。 所述查询消息中携带用户的 IP地 址。
步骤 5、 第一网元收到 GGSN/PGW的查询消息, 根据查询消息中的 IP地 址,向 GGSN/PGW返回用户的标识。具体的,上述第一网元收到 GGSN/PGW 发送的查询消息后,获得上述查询消息中的 IP地址,第一网元根据上述 IP地址 查询存储的信息(例如: 用户的 IP地址和用户的标识的关联关系), 查询到与 上述 IP地址关联(对应) 的用户的标识。
进一步的, 第一网元还可以在查询响应消息中携带用户 (尤其是对于低移 动用户 (Low mobility ), 即位置固定或只在特定的区域移动的用户)所在的位 置信息(如小区信息, 或跟踪区信息 TA, 或路由区信息 RA, 或跟踪区列表信 息, 或接入网标识(RNC ID, eNodeB ID, 或 BSC ID ) ), 或者服务用户的 SGSN/MME的信息(用户可以附着的或用户已经附着的 SGSN/MME, 该信息 具体可以是: SGSN/MME的地址或 SGSN/MME的 FQDN )。 具体过程如下: 第一网元中存储了用户的位置信息或者服务用户的 SGSN/MME 的信息, 第一 网元根据获得的用户名或用户的标识查询用户的位置信息或者服务用户的 SGSN/MME的信息。其中存储在第一网元上的用户的位置信息或者服务用户的 SGSN/MME 的信息具体可以是: a、 用户的位置信息或者服务用户的 SGSN/MME的信息可以与用户的标识或用户名绑定预先配置在第一网元中; b、 在用户主动发起的 PDP上下文激活或 PDN连接建立流程 (包含 Attach流程 ) 中, GGSN/PGW将用户的位置信息或者服务用户的 SGSN/MME的信息通知 给第一网元, 例如: GGSN/PGW在用户发起的 PDP激活流程或 PDN连接建 立流程中, GGSN获得了用户的位置信息或者服务用户的 SGSN/MME的信息, GGSN/PGW向第一网元发送 Register消息, 上述 Register消息中携带用户的 标识, 和用户的位置信息或者服务用户的 SGSN/MME 的信息, 第一网元保存 用户的位置信息或者服务用户的 SGSN/MME 的信息(第一网元将用户的位置 信息或者服务用户的 SGSN/MME 的信息与用户的标识绑定, 或者由于第一网 元上有用户的标识和用户名的关系, 也可以将用户的位置信息或者服务用户的 SGSN/MME的信息与用户名绑定)。 当 GGSN/PGW将用户的位置信息或者服 务用户的 SGSN/MME的信息与通知到第一网元后,用户的 PDP上下文或 PDN 连接可以被删除(包含用户处于分离态)。
第一网元还可以通过 HLR/HSS查询服务用户的 SGSN/MME的信息(用户 所附着的 SGSN/MME信息)。具体可以是第一网元向 HLR/HSS发送查询消息, 上述查询消息中携带用户的标识。 HLR/HSS才艮据用户的标识查询用户的注册信 息得到用户附着的 SGSN/MME, HLR/HSS将用户附着的 SGSN/MME发送给 第一网元。
另外, 如果第一网元中存储了用户使用的 APN信息, 则第一网元还可以向 GGSN在查询响应消息中提供 APN信息。具体地,在第一网元中存储了用户使 用的 APN信息, 第一网元获得了用户名或用户的标识后, 第一网元根据用户名 或用户的标识查询用户使用的 APN。 第一网元在向 GGSN/PGW发送连接建立 请求之前, 第一网元需要寻址到可以服务第一网元下的用户的 GGSN/PGW。 具体地, 第一网元配置可以服务上述用户的 GGSN/PGW 的信息 (例如: GGSN/PGW的地址或 FQDN )。 例如: 第一网元按照用户所属的群组的群组标 识(例如: Group ID, APN , IMSI号段等)配置可以服务上述群组的 GGSN/PGW 的信息。 当第一网元获得了用户的标识或用户使用的 APN之后, 第一网元根据 用户的标识或用户使用的 APN获知用户所属的群组, 然后第一网元根据获得的 用户所属的群组的群组标识查询其上配置的与上述群组标识对应的 GGSN/PGW 的信息。 第一网元和 GGSN/PGW之间可以釆用 Diameter或 Radius协议(需要作增强扩展)。
步骤 6、 如果在步骤 5中第一网元向 GGSN/PGW提供了用户的位置信息 或者服务用户的 SGSN/MME的信息, GGSN/PGW可以根据用户的位置信息 或者服务用户的 SGSN/MME的信息获知服务用户的 SGSN/MME (用户可以附 着的或用户已经附着的 SGSN/MME )。
如果在步骤 5 中, 第一网元向 GGSN/PGW 提供的是服务用户的 SGSN/MME的信息(例如: SGSN/MME的地址或 FQDN ), 则直接获知服务 用户的 SGSN/MME。
如果在步骤 5中, 第一网元向 GGSN/PGW提供的是用户的位置信息(例 如: 用户所在的 RA或 TA ), 则 GGSN/PGW可以根据用户的位置信息查询服 务器(例如 DNS服务器, 或者 GGSN 自身的服务器)得到 SGSN/MME的信 息。 例如: GGSN/PGW向 DNS服务器发送查询请求, 所述查询消息中携带 RA或 TA或接入网标识, DNS服务器根据 RA或 TA或接入网标识解析得到 SGSN/MME的信息, 并发送给 GGSN/PGW。 或者, GGSN/PGW上配置 RA 与 SGSN或 TA与 MME的信息之间的关联, GGSN/PGW获得 RA或 TA之后, 查询上述映射关系得到 SGSN/MME。
步骤 7、 如果在步骤 5中, 第一网元没有在连接建立请求消息中向 GGSN 提供用户的位置信息或者服务用户的 SGSN/MME的信息, 则 GGSN根据用户 的标识向 HLR请求服务用户的 SGSN/MME。
具体 GGSN向 HLR获取用户附着的 SGSN的信息的流程属于现有技术, 在此不再赘述。
步骤 8、 GGSN/PGW 在步骤 6 或步骤 7 中获知了可以服务用户的 SGSN/MME。 GGSN/PGW向获知的 SGSN/MME发送连接建立指示消息。
在 GERAN/UTRAN 中, 上述连接建立指示消息可以是 PDU Notification Request消息( GGSN发送给 SGSN )。 上述 PDU Notification Request消息中 携带了用户的标识(例如: IMSI )。 在步骤 5中, 如果第一网元向 GGSN提供 了用户所在的位置(例如:用户所在的 RA ),则 GGSN在上述 PDU Notification Request消息中携带用户所在的位置信息给 SGSN。 在步骤 5中, 如果第一网 元还向 GGSN提供了用户使用的 APN , 则 GGSN 在上述 PDU Notification Request消息中携带用户使用的 APN给 SGSN。 SGSN可以将所述 APN通知 给用户, 使用户根据所述 APN发起连接建立。
在 E-UTRAN 中, 上述连接建立指示消息可以是 Downlink Notification Request消息(PGW发送给 SGW, SGW再发送给 MME )。 上述 Downlink Notification Request消息中携带了用户的标识(例如: IMSI )。 在步骤 5中, 如 果第一网元向 PGW提供了用户所在的位置信息(例如: 用户所在的 TA ), 则 PGW在上述 Downlink Notification Request消息中携带用户所在的位置信息给 MME。
步骤 9、 SGSN/MME触发用户发起连接建立流程。 所述连接建立流程是指 PDP上下文激活流程或者 PDN连接建立流程。
在 GERAN/UTRAN中,如果用户处于附着态且用户处于连接态,则 SGSN 向用户发送 Request PDP Context Activation消息。 如果用户处于空闲态( Idle 或 Standby状态 ), 则 SGSN寻呼用户, 用户收到寻呼消息后, 用户与 SGSN 之间建立连接, SGSN向用户发送 Request PDP Context Activation消息。 用 户收到上述 Request PDP Context Activation消息后, 用户发起 PDP上下文激 活流程。 如果在步骤 5中, SGSN获得了用户所在的位置(例如: 用户所在的 RA ), 则 SGSN在上述用户所在的位置范围内寻呼用户。
在 GERAN/UTRAN中, 如果用户出于分离态, 则 SGSN向用户发送寻呼 消息, 所述寻呼消息中携带用户的 IMSI, 用户收到上述 IMSI寻呼消息后, 用户 将发起附着流程。 用户发起附着流程后, SGSN 向用户发送 Request PDP Context Activation消息。 用户收到上述 Request PDP Context Activation消息 后, 用户发起 PDP上下文激活流程。 或者, 如果用户出于分离态, 则 SGSN 向用户发送寻呼消息, 所述寻呼消息中携带用户的 IMSI, 进一步的, 上述 IMSI 寻呼消息中还携带指示用户发起 PDP上下文激活流程的指示信息。用户收到上 述 IMSI寻呼消息后, 用户将发起附着流程, 然后用户将根据上述指示信息发起 PDP上下文激活流程。如果在步骤 5中, SGSN获得了用户所在的位置 (例如: 用户所在的 RA ), 则 SGSN在上述用户所在的位置范围内寻呼用户。 在 E-UTRAN中, 如果用户出于分离态, 则 MME向用户发送寻呼消息, 所 述寻呼消息中携带用户的 IMSI,用户收到上述 IMSI寻呼消息后,用户将发起附 着流程。 在附着流程中, 用户建立 PDN连接。 如果在步骤 5中, MME获得了 用户所在的位置(例如: 用户所在的 TA ), 则 MME在上述用户所在的位置范围 内寻呼用户。
步骤 10、 用户发起 PDP上下文激活流程或 PDN连接建立流程。 用户根据 SGSN/MME的触发发起 PDP上下文激活流程或 PDN连接建立流程, 在连接 建立后, 网关将数据包发送给终端, 从而建立了用户与第二网元之间的连接。
上述实施例中, 通过由第一网元为用户分配 IP地址, 并将 IP地址发送给 第二网元, 当收到网关携带 IP地址的查询消息后, 向网关发送用户的 IP地址, 因此网关和第二网元都获得用户的 IP地址, 从而用户可以与第二网元建立连 接,解决了现有技术中网络侧推送业务时, 由于无法为 M2M终端配置静态 IP 地址造成第二网元无法获得 IP地址的问题。 图 4 为本发明实施例三提供的另一种获取用户的 IP地址方法的流程示意 图, 该实施例中由第一网元分配 IP地址, 并且等用户建立连接后, 将 IP地址发 送给第二网元。
401. 第一网元接收第二网元发送的获取用户的 IP地址的消息;
所述消息携带用户的标识或者用户名。
402. 第一网元才艮据所述获取用户的 IP地址的消息获知用户的标识,并为用 户分配 IP地址, 将所述用户的标识和所述 IP地址发送给网关;
所述第一网元根据所述获取用户的 IP地址的消息获取所述用户的标识包 括: 所述获取用户的 IP地址的消息中携带用户的标识, 所述第一网元从所述 获取用户的 IP地址的消息中获得用户的标识;或者所述获取用户的 IP地址的 消息中携带用户名, 所述第一网元根据用户名查询存储信息获得用户的标识。
该步骤之后还包括: 网关获知服务用户的移动性管理网元; 通过所述移动 性管理网元发送通知用户连接建立请求, 为用户建立连接后, 网关向第一网元 发送通知消息。
网关获知服务用户的移动性管理网元具体为: 所述第一网元获知服务用 户的移动性管理网元的信息(服务用户的 SGSN/MME的地址或 SGSN/MME 的域名), 将服务用户的移动性管理网元的信息发送给网关; 或者, 所述第一 网元获知用户的位置信息 (小区信息, 或跟踪区信息, 或路由区信息, 或跟 踪区列表信息, 或接入网标识), 将用户的位置信息发送给网关, 网关根据所 述的用户的位置信息查询服务器获知服务所述用户的移动性管理网元; 或者 网关根据第一网元发送的用户的标识向 HSS/HLR 查询获得服务用户的移动 性管理网元的信息。
所述第一网元获知服务用户的移动性管理网元的信息具体为: 根据用户 名或者用户的标识查询存储信息或者根据用户的标识查询 HSS/HLR 获得服 务用户的移动性管理网元的信息。 所述第一网元获知用户的位置信息具体为: 根据用户名或者用户的标识查询存储信息获得用户的位置信息。
403. 第一网元接收网关发送的通知消息后,将所述用户的 IP地址发送给所 述第二网元。
如图 5所示, 实施例四为实施例三的具体实现方式, 通过具体的信令流程 进行描述。
步骤 1 : 第二网元(应用服务器, 例如 MTC Server )向第一网元(M2M 平台 /M2M Proxy )发送获取用户的 IP地址的消息(例如: IP地址查询或 IP地 址请求消息)。
所述消息中携带用户名或者携带用户的标识。
步骤 2, 3: 所述第一网元收到第二网元发送的获取 IP地址的请求消息后, 所述第一网元为用户分配 IP地址,并且将所述 IP地址在连接建立请求消息中携 带给网关。 所述第一网元通过网关( GGSN/PGW )以使用户发起连接建立流程 ( PDP上下文激活或 PDN连接建立流程 )。 所述第一网元向所述网关发送连接建立请求消息, 所述消息中携带用户的 标识 ( IMSI或 MSISDN或 IM曰等)。所述第一网元可以根据步骤 1第二网元发 送的消息中携带的用户名查询存储信息获得用户的标识。 具体方法是所述第一 网元中存储了用户的标识和用户名之间的关联关系, 所述第一网元根据第二网 元发送的用户名查询上述关联关系获得用户的标识。 所述第一网元还可以直接 在应用服务器在步骤 1 发送的消息中获得用户的标识。 具体的过程也可以参见 实施例二中步骤 2对应部分。
可选的, 如果所述第一网元上存储有用户使用的 APN, 则所述第一网元可 以在所述连接建立请求消息中携带用户使用的 APN。 具体的过程也可以参见实 施例二中步骤 5对应部分。
可选的, 所述第一网元在所述连接建立请求消息中携带服务用户 (用户附 着) 的移动性管理网元的信息(SGSN/MME的地址或 FQDN )。 所述第一网元 获得服务用户的移动性管理网元信息的方法可以有(具体的过程也可以参见实 施例二中步骤 5对应部分 )··
1 )、 所述第一网元向 HLR/HSS 发送查询消息, 查询用户所附着的
SGSN/MME的信息(地址或 FQDN )。 所述查询消息中携带用户的标识( IMSI 或 MSISDN或 IM曰等)。 HLR/HSS根据用户的标识查询用户在其上的注册信 息得到用户所附着的 SGSN/MME的信息, 然后发送给所述第一网元。 或, 2 )、 所述第一网元根据用户的用户名或用户的标识查询存储信息获得服务 用户的移动性管理网元的信息。 具体包括, 所述第一网元获得了用户名或用户 的标识后查询存储的用户名或用户的标识和 Λ良务用户的 SGSN/MME 的信息的 绑定关系表, 从而获得服务用户的移动性管理网元的信息。 或,
3 )、 所述第一网元获得了用户名或用户的标识后查询本地存储的用户名或用户 的标识和用户所在的位置信息 (例如, 用户所在的小区信息, 或跟踪区信息, 或路由区信息, 或跟踪区列表信息或接入网的标识信息)之间的绑定关系表, 从而获得用户所在的位置信息。 所述第一网元根据获得的用户所在位置信息向 服务器(例如, DNS服务器)查询服务用户的移动性管理网元的信息。
可选的, 如果所述第一网元上存储了用户的位置信息, 所述第一网元在连 接建立请求消息中携带用户的位置信息发送给网关。
步骤 4:如果在步骤 3中,所述第一网元没有向所述网关发送服务用户的移 动性管理网元的信息或位置信息,则网关可以向 HLR/HSS查询月良务用户的移动 性管理网元的信息。 具体可以是, 网关向 HLR/HSS发送路由信息消息, 所述消 息中携带用户的标识。 HLR/HSS查询其上用户注册的信息, 将服务用户的移动 性管理网元的信息发送给网关。
如果在步骤 3 中, 所述第一网元没有向所述网关发送服务用户的移动性管 理网元的信息, 而提供了用户的位置信息, 则所述网关才艮据位置信息查询获知 为所述用户服务的移动性管理网元的具体方法可以是所述网关根据获得的用户 的位置信息(例如, 小区信息, 跟踪区信息, 路由区信息、 跟踪区列表或接入 网标识等信息)向服务器(例如, DNS服务器)查询能够在上述位置服务用户 的移动性管理网元的信息。 在所述服务器中存储了所述位置信息和能够服务所 述位置区域中的用户的移动性管理网元的信息之间的绑定(关联) 关系。
步骤 5: 网关向获知的 SGSN/MME发送连接建立指示消息,所述消息中携 带用户的 IP地址和用户的标识。
本实施例中具体举例了两条消息代表上述连接建立指示消息, 当然, 也可 以由其他消息代表上述连接建立指示消息。在 GERAN/UTRAN中,上述连接建 立指示消息可以是 PDU Notification Request消息( GGSN发送给 SGSN )。 上 述 PDU Notification Request消息中携带了用户的标识 (例如: IMSI )。 在步骤 3中,如果第一网元向 GGSN提供了用户所在的位置(例如: 用户所在的 RA ), 则第一网元在上述 PDU Notification Request消息中携带用户所在的位置信息 给 SGSN。 在步骤 3中, 如果第一网元还向 GGSN提供了用户使用的 APN , 则 GGSN在上述 PDU Notification Request消息中携带用户使用的 APN给 SGSN。 在 E-UTRAN 中, 上述连接建立指示消息可以是 Downlink Notification Request消息(PGW发送给 SGW, SGW再发送给 MME )。 上述 Downlink Notification Request消息中携带了用户的标识(例如: IMSI )。 在步骤 3中, 如 果第一网元向 PGW提供了用户所在的位置信息(例如: 用户所在的 TA ), 则 PGW在上述 Downlink Notification Request消息中携带用户所在的位置信息给 MME。 在步骤 3中, 如果第一网元向 PGW提供了用户使用的 APN , 则 PGW 在上述 Downlink Notification Request 消息中携带用户使用的 APN 信息给 MME。
步骤 6: SGSN/MME触发用户发起连接建立流程。 所述连接建立流程是指 PDP上下文激活流程或者 PDN连接建立流程 (包括附着流程 )。
由于 SGSN获得了第一网元为用户分配的 IP地址, 则 SGSN触发用户发 起连接建立流程时将所述用户的 IP地址携带给用户, 用户在激活 PDP上下文 请求消息中携带上述 IP地址。
在 GERAN/UTRAN中,如果用户处于附着态且用户处于连接态,则 SGSN 向用户发送 Request PDP ContextActivation消息。 如果用户处于空闲态( Idle 或 Standby状态 ), 则 SGSN寻呼用户, 用户收到寻呼消息后, 用户与 SGSN 之间连接建立, SGSN向用户发送 Request PDP Context Activation消息。 用 户收到上述 Request PDP Context Activation消息后, 用户发起 PDP上下文激 活流程。
在 GERAN/UTRAN中, 如果用户出于分离态, 则 SGSN向用户发送寻呼 消息, 所述寻呼消息中携带用户的 IMSI, 用户收到上述 IMSI寻呼消息后, 用户 将发起附着流程。 用户发起附着流程后, SGSN 向用户发送 Request PDP Context Activation消息。 用户收到上述 Request PDP Context Activation消息 后, 用户发起 PDP上下文激活流程。 如果在步骤 5中, SGSN获得了第一网元 为用户分配的 IP地址, 则则 SGSN在 Request PDP ContextActivation消息将 所述用户的 IP地址携带给用户, 用户在激活 PDP上下文请求消息中携带上述 IP地址。 或者, 如果用户出于分离态, 则 SGSN向用户发送寻呼消息, 所述寻 呼消息中携带用户的 IMSI,进一步的,上述 IMSI寻呼消息中还携带指示用户发 起 PDP上下文激活流程的指示信息。 用户收到上述 IMSI寻呼消息后, 用户将 发起附着流程, 然后用户将根据上述指示信息发起 PDP上下文激活流程。 如果 在步骤 5中, SGSN获得了用户所在的位置(例如:用户所在的 RA ),则 SGSN 在上述用户所在的位置范围内寻呼用户。
在 E-UTRAN中, 如果用户出于分离态, 则 MME向用户发送寻呼消息, 所 述寻呼消息中携带用户的 IMSI,用户收到上述 IMSI寻呼消息后,用户将发起附 着流程。 在附着流程中, 用户建立 PDN连接。 如果在步骤 5中, MME获得了 用户所在的位置(例如: 用户所在的 TA ), 则 MME在上述用户所在的位置范围 内寻呼用户。
步骤 7:用户发起 PDP激活流程或 PDN连接建立流程。用户在收到 SGSN 发送的 Request PDP Context Activation消息,如果所述消息中携带了第一网元 为用户分配的 IP地址, 则用户在激活 PDP上下文消息中携带所述 IP地址, 则 GSN/PGW使用所述第一网元为用户分配的 IP地址作为用户的 IP地址。
步骤 8: 网关向所述第一网元发送通知消息。
所述通知消息中携带用户的标识或用户名。 所述通知消息用于指示所述第 一网元其为用户分配的 IP地址可用。
步骤 9: 所述第一网元将用户的 IP地址发送给第二网元 ( MTC Server )。 步骤 10: 第二网元根据所述 IP地址发送数据给用户。
上述实施例中, 通过由第一网元分配 IP地址, 将所述 IP地址和用户的标 识发送给网关, 并且当用户建立连接后, 将 IP地址发送给第二网元。 因此网关 和第二网元都获得用户的 IP地址, 从而用户可以与第二网元建立连接, 解决 了现有技术中网络侧推送业务时, 由于无法为 M2M终端配置静态 IP地址造 成第二网元无法获得 IP地址的问题。 图 6为本发明实施例五提供的获取用户的 IP地址的网络实体 60的结构 示意图, 包括接收单元 601 , 第一获知单元 605, 分配单元 603和发送单元 607, 其中, 接收单元 601接收第二网元发送的获取用户的 IP地址的消息; 分配单元 603为用户分配 IP地址; 发送单元 607将 IP地址发送给所述第二 网元; 包括接收单元 601接收网关发送的携带所述 IP地址的查询消息; 所述 第一获知单元 605根据所述 IP地址获得用户的标识;发送单元 607将所述用 户的标识发送给网关。
进一步的, 本实施例的网络实体还可以还包括第二获知单元 602, 用于 根据所述获取用户的 IP地址的消息获知所述用户的标识, 具体为: 所述第二 获知单元 602从所述获取用户的 IP地址的消息中获得用户的标识; 或者所述 获取用户 IP地址的消息中携带用户名, 所述第二获知单元 602根据用户名查 询存储信息获得用户的标识。
进一步的, 本实施例的网络实体还可以包括建立关系单元 604 , 当第二获知单元获得用户的标识以及分配单元 603为用户分配 IP地址之 后,建立关系单元 604建立 IP地址与用户的标识的对应关系,所述第一获知单 元 605根据所述 IP地址获得用户的标识具体为, 根据所述 IP地址查询 IP地 址与用户的标识的对应关系获得用户的标识。
或者, 当获取用户的 IP地址的消息携带用户名以及分配单元 603为用户 分配 IP地址之后, 建立关系单元 604建立 IP地址与用户名的对应关系, 所述 第一获知单元 605获得用户的标识具体为, 根据查询消息中的 IP地址查询建 立 IP地址与用户名的对应关系获得用户名, 再根据用户名查询存储信息获得用 户的标识。
进一步的, 本实施例的网络实体还可以还包括第三获知单元 606, 所述 第三获知单元 606根据用户名或者用户的标识获知服务用户的移动性管理网 元的信息, 所述发送单元 607还将服务用户的移动性管理网元的信息发送给 网关; 或者第二获知单元根据用户名或者用户的标识获知用户的位置信息, 所述发送单元 607还将用户的位置信息发送给网关。
该网元与其他网元相互之间的具体交互过程可以参考上述的方法实施 例, 在此不再重复。 图 7为本发明实施例六提供的获取用户的 IP地址的网络实体 70的结构 示意图, 包括接收单元 701 , 分配单元 702, 第一获知单元 703, 发送单元 705, 其中
接收单元 701接收第二网元发送的获取用户的 IP地址的消息; 第一获知 单元 703根据所述获取用户的 IP地址的消息获知所述用户的标识; 分配单元 702为用户分配 IP地址; 发送单元 705将所述用户的标识和所述 IP地址发 送给网关; 接收单元 701接收网关发送的通知消息后, 发送单元 705将所述 用户的 IP地址发送给所述第二网元。
其中, 第一获知单元 703根据所述获取用户的 IP地址的消息获知所述用 户的标识具体包括:
所述第一获知单元从所述获取用户的 IP地址的消息中获得用户的标识; 或者所述获取用户 IP地址的消息中携带用户名, 所述第一获知单元根据所述 用户名查询存储信息获得用户的标识。
进一步的, 本实施例的网络实体还可以还包括第二获知单元 704, 所述 第二获知单元 704根据用户名或者用户的标识获知服务用户的移动性管理网 元的信息, 所述发送单元 705将服务用户的移动性管理网元的信息发送给网 关;或者第二获知单元 704根据用户名或者用户的标识获知用户的位置信息, 所述发送单元 705将用户的位置信息发送给网关。
该网元与其他网元相互之间的具体交互过程可以参考上述的方法实施 例, 在此不再重复。 图 8为本发明实施例七提供的获取用户的 IP地址的网络实体的结构示意 图, 第二网元 801 , 第一网元 802, 网关 803, 移动性管理实体 804。 其各个 网元的功能与相互之间的流程交互可以参考上述的方法实施例以及装置实施 例, 在此不再重复。 本领域普通技术人员可以理解: 实现上述方法实施例的全部或部分步骤 可以通过程序指令相关的硬件来完成, 前述的程序可以存储于一计算机可读 取存储介质中, 该程序在执行时, 执行包括上述方法实施例的步骤; 而前述 的存储介质包括: ROM、 RAM, 磁碟或者光盘等各种可以存储程序代码的介 最后应说明的是: 以上实施例仅用以说明本发明的技术方案, 而非对其 限制; 尽管参照前述实施例对本发明进行了详细的说明, 本领域的普通技术 人员应当理解: 其依然可以对前述各实施例所记载的技术方案进行修改, 或 者对其中部分技术特征进行等同替换; 而这些修改或者替换, 并不使相应技 术方案的本质脱离本发明各实施例技术方案的精神和范围。

Claims

权利 要求
1、 一种获取用户的 IP地址的方法, 其特征在于,
第一网元接收第二网元发送的获取用户的 I P地址的消息;
第一网元为所述用户分配 IP地址, 将 IP地址发送给所述第二网元; 接收网关发送的携带所述 IP地址的查询消息, 获知用户的标识, 将所述 用户的标识发送给网关。
2、 根据权利要求 1所述的方法, 其特征在于, 所述方法还包括, 所述获 取用户的 IP地址的消息中携带了用户的标识或者用户名。
3、 根据权利要求 2所述的方法, 其特征在于, 当所述获取用户 IP地址 的消息中携带用户名时, 所述方法还包括, 所述第一网元根据用户名查询存 储信息获得用户的标识。
4、 根据权利要求 2或 3所述的方法, 其特征在于, 第一网元为用户分配 IP地址之后还包括,建立 IP地址与用户的标识的对应关系,所述获知用户的标 识步骤具体为, 根据查询消息中的 IP地址获得用户的标识。
5、 根据权利要求 2所述的方法, 其特征在于, 当所述获取用户 IP地址 的消息中携带用户名时, 第一网元为用户分配 IP地址之后还包括, 建立 IP地 址与用户名的对应关系, 所述获知用户的标识步骤具体为, 根据查询消息中的
IP地址查询获得用户名, 再根据用户名查询存储信息获得用户的标识。
6、 根据权利要求 1或 2或 3所述的方法, 其特征在于, 将所述用户的标 识发送给网关后还包括:
网关获知服务用户的移动性管理网元,
通过所述移动性管理网元发送通知用户建立连接。
7、 根据权利要求 6所述的方法, 其特征在于, 网关获知服务用户的移动 性管理网元具体为:
所述第一网元获知服务用户的移动性管理网元的信息, 将服务用户的移 动性管理网元的信息发送给网关; 或者, 所述第一网元获知用户的位置信息, 将用户的位置信息发送给网关, 网 关根据所述的用户的位置信息查询服务器获知服务所述用户的移动性管理网 元; 或者
网关根据第一网元发送的用户的标识向 HSS/HLR 查询获得服务用户的 移动性管理网元的信息。
8、 根据权利要求 7所述的方法, 其特征在于, 所述第一网元获知服务用 户的移动性管理网元的信息具体为:
根据用户名或者用户的标识查询存储信息或者根据用户的标识查询 HSS/HLR获得服务用户的移动性管理网元的信息。
9、 根据权利要求 7所述的方法, 其特征在于, 所述第一网元获知用户的 位置信息具体为: 根据用户名或者用户的标识查询存储信息获得用户的位置 信息。
10、 如权利要求 7或 8所述的方法, 所述服务用户的移动性管理网元的 信息为服务用户的 SGSN/MME的地址或 SGSN/MME的域名。
11、 如权利要求 7或 9所述的方法, 所述位置信息为用户所在的小区信 息, 或跟踪区信息, 或路由区信息, 或跟踪区列表信息, 或接入网标识。
12、 一种获取用户的 IP地址的方法, 其特征在于,
第一网元接收第二网元发送的获取用户的 I P地址的消息;
第一网元才艮据所述获取用户的 IP地址的消息获知所述用户的标识, 并为 用户分配 IP地址, 将所述用户的标识和所述 IP地址发送给网关;
第一网元接收网关发送的通知消息后, 将所述用户的 IP地址发送给所述 第二网元。
13、 根据权利要求 12所述的方法, 其特征在于, 所述第一网元根据所述 获取用户的 IP地址的消息获取所述用户的标识包括:
所述获取用户的 IP地址的消息中携带用户的标识, 所述第一网元从所述 获取用户的 IP地址的消息中获得用户的标识; 或者
所述获取用户的 IP地址的消息中携带用户名, 所述第一网元根据用户名 查询存储信息获得用户的标识。
14、 根据权利要求 12或 13所述的方法, 其特征在于, 将所述用户的标 识和所述 IP地址发送给网关之后还包括:
网关获知服务用户的移动性管理网元,
通过所述移动性管理网元发送通知用户建立连接, 为用户连接建立后, 网关向第一网元发送所述通知消息。
15、 根据权利要求 14所述的方法, 其特征在于, 网关获知服务用户的移 动性管理网元具体为:
所述第一网元获知服务用户的移动性管理网元的信息, 将服务用户的移 动性管理网元的信息发送给网关; 或者,
所述第一网元获知用户的位置信息, 将用户的位置信息发送给网关, 网 关根据所述的用户的位置信息查询服务器获知服务所述用户的移动性管理网 元; 或者
网关根据第一网元发送的用户的标识向 HSS/HLR 查询获得服务用户的 移动性管理网元的信息。
16、 根据权利要求 15所述的方法, 其特征在于, 所述第一网元获知服务 用户的移动性管理网元的信息具体为:
根据用户名或者用户的标识查询存储信息或者根据用户的标识查询
HSS/HLR获得服务用户的移动性管理网元的信息。
17、 根据权利要求 15所述的方法, 其特征在于, 所述第一网元获知用户 的位置信息具体为: 根据用户名或者用户的标识查询存储信息获得用户的位 置信息。
18、 如权利要求 15或 16所述的方法, 所述服务用户的移动性管理网元 的信息为服务用户的 SGSN/MME的地址或 SGSN/MME的域名。
19、 如权利要求 15或 17所述的方法, 所述位置信息为用户所在的小区 信息, 或跟踪区信息, 或路由区信息, 或跟踪区列表信息, 或接入网标识。
20、 一种用于获取用户的 IP地址的网络实体, 其特征在于, 包括: 接收 单元, 第一获知单元, 分配单元和发送单元, 其中,
接收单元接收第二网元发送的获取用户的 IP地址的消息; 分配单元为用 户分配 IP地址;发送单元将 IP地址发送给所述第二网元;接收单元接收网关 发送的携带所述 IP地址的查询消息;所述第一获知单元根据所述 IP地址获得 用户的标识; 发送单元将所述用户的标识发送给网关。
21、 根据权利要求 20所述的网络实体, 其特征在于, 所述网络实体还包 括第二获知单元, 用于根据所述获取用户的 IP地址的消息获知所述用户的标 识, 具体为: 所述第二获知单元从所述获取用户的 IP地址的消息中获得用户 的标识; 或者所述获取用户 IP地址的消息中携带用户名, 所述第二获知单元 根据用户名查询存储信息获得用户的标识。
22、 根据权利要求 20所述的网络实体, 其特征在于, 所述网络实体还包 括建立关系单元,当第二获知单元获得用户的标识以及分配单元为用户分配 IP 地址之后, 建立关系单元建立 IP地址与用户的标识的对应关系, 所述第一获知 单元根据所述 IP地址获得用户的标识具体为, 根据所述 IP地址查询 IP地址 与用户的标识的对应关系获得用户的标识。
23、 根据权利要求 20所述的网络实体, 其特征在于, 所述网络实体还包 括建立关系单元, 其中
如果获取用户的 IP地址的消息携带用户名以及分配单元为用户分配 IP地 址之后, 建立关系单建立 IP地址与用户名的对应关系, 所述第一获知单元获 得用户的标识具体为, 根据查询消息中的 IP地址查询建立 IP地址与用户名的 对应关系获得用户名, 再根据用户名查询存储信息获得用户的标识。
24、 根据权利要求 22所述的网络实体, 其特征在于, 还包括第三获知单 元, 所述第三获知单元根据用户名或者用户的标识获知服务用户的移动性管 网关; 或者第二获知单元根据用户名或者用户的标识获知用户的位置信息, 所述发送单元还将用户的位置信息发送给网关。
25、 一种获取用户的 IP地址的网络实体, 其特征在于, 包括: 接收单元, 发送单元, 分配单元和第一获知单元, 其中
接收单元接收第二网元发送的获取用户的 IP地址的消息;
第一获知单元根据所述获取用户的 IP地址的消息获知所述用户的标识, 分配单元为用户分配 IP地址,
发送单元将所述用户的标识和所述 IP地址发送给网关;
接收单元接收网关发送的通知消息后, 发送单元将所述用户的 IP地址发 送给所述第二网元。
26、 如权利要求 25所述的网络实体, 其特征在于, 第一获知单元根据所 述获取用户的 IP地址的消息获知所述用户的标识具体包括:
所述第一获知单元从所述获取用户的 IP地址的消息中获得用户的标识; 或者所述获取用户 IP地址的消息中携带用户名, 所述第一获知单元根据所述 用户名查询存储信息获得用户的标识。
27、 如权利要求 25或 26所述的网络实体, 其特征在于: 还包括第二获 知单元, 所述第二获知单元根据用户名或者用户的标识获知服务用户的移动 给网关; 或者第二获知单元根据用户名或者用户的标识获知用户的位置信息, 所述发送单元将用户的位置信息发送给网关。
PCT/CN2010/079071 2010-11-24 2010-11-24 获取用户的ip地址的方法和网络实体 WO2012068728A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
PCT/CN2010/079071 WO2012068728A1 (zh) 2010-11-24 2010-11-24 获取用户的ip地址的方法和网络实体
EP10860007.3A EP2637378A4 (en) 2010-11-24 2010-11-24 METHOD AND NETWORK UNITS FOR DETERMINING THE IP ADDRESS OF A USER
CN201080004950.1A CN102668489B (zh) 2010-11-24 2010-11-24 获取用户的ip地址的方法和网络实体
US13/901,046 US20130250968A1 (en) 2010-11-24 2013-05-23 Method and network entity for obtaining ip address of user

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2010/079071 WO2012068728A1 (zh) 2010-11-24 2010-11-24 获取用户的ip地址的方法和网络实体

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US13/901,046 Continuation US20130250968A1 (en) 2010-11-24 2013-05-23 Method and network entity for obtaining ip address of user

Publications (1)

Publication Number Publication Date
WO2012068728A1 true WO2012068728A1 (zh) 2012-05-31

Family

ID=46145356

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2010/079071 WO2012068728A1 (zh) 2010-11-24 2010-11-24 获取用户的ip地址的方法和网络实体

Country Status (4)

Country Link
US (1) US20130250968A1 (zh)
EP (1) EP2637378A4 (zh)
CN (1) CN102668489B (zh)
WO (1) WO2012068728A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103650551A (zh) * 2013-06-26 2014-03-19 华为技术有限公司 一种对业务处理的方法、系统以及相关设备
CN106465443A (zh) * 2015-05-18 2017-02-22 华为技术有限公司 D2d通信中的ip地址分配方法及用户设备

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2911424B1 (en) * 2012-11-13 2019-08-14 Huawei Technologies Co., Ltd. Method and network element for obtaining packet information
KR101922100B1 (ko) 2014-02-10 2018-11-27 지티이 코포레이션 M2m 통신을 도모하는 방법 및 장치
EP3105909A4 (en) * 2014-02-10 2017-03-08 ZTE Corporation Techniques for mapping machine to machine communication to different underlying networks
CN106165374A (zh) 2014-02-10 2016-11-23 中兴通讯股份有限公司 使能在机器对机器通信系统中的不同的设备触发方面
CN104994078B (zh) * 2015-06-10 2019-07-19 杭州海康威视数字技术股份有限公司 局域网内的信息发送、获取方法及装置、信息处理系统
US9961562B2 (en) * 2015-06-15 2018-05-01 Motorola Solutions, Inc. System and method for extending coverage of a communication network
US9749908B2 (en) * 2015-07-29 2017-08-29 Verizon Patent And Licensing Inc. Local breakout service
US10805217B2 (en) * 2015-11-10 2020-10-13 At&T Intellectual Property I, L.P. Control plane device selection for broadcast session exchange
US11356298B2 (en) 2017-09-21 2022-06-07 Nippon Telegraph And Telephone Corporation Access management apparatus and access management method
US11576042B2 (en) * 2018-05-18 2023-02-07 Interdigital Patent Holdings, Inc. Identity layer for IoT devices
CN111511044B (zh) * 2020-04-16 2023-05-05 蓓安科仪(北京)技术有限公司 基于5g网络实现远程医疗的数据通信方法

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1460349A (zh) * 2000-08-29 2003-12-03 摩托罗拉公司 为移动台分配地址
CN101651662A (zh) * 2008-08-11 2010-02-17 华为技术有限公司 简单互联网协议地址的分配方法与装置

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1560368A1 (fr) * 2004-01-30 2005-08-03 France Telecom Procédé d'établissement d'une session multimédia entre un équipement appelant et un équipement appelé d'un réseau du type à sous domaine multimédia et système de communication mettant en oeuvre ce procédé
CN1835475A (zh) * 2005-03-14 2006-09-20 华为技术有限公司 通用分组无线业务网络侧激活的方法
CN101399842B (zh) * 2007-09-28 2012-07-04 华为技术有限公司 一种wap网关和ggsn及二者间交换用户信息的方法
GB2456184A (en) * 2008-01-07 2009-07-08 Cvon Innovations Ltd System for selecting an information provider or service provider
CN101754305A (zh) * 2008-12-04 2010-06-23 华为技术有限公司 实现数据网关切换的方法、装置和系统
US9596596B2 (en) * 2010-02-15 2017-03-14 Telefonaktiebolaget Lm Ericsson (Publ) Machine-to-machine device triggering using session initiation protocol uniform resourse identifier

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1460349A (zh) * 2000-08-29 2003-12-03 摩托罗拉公司 为移动台分配地址
CN101651662A (zh) * 2008-08-11 2010-02-17 华为技术有限公司 简单互联网协议地址的分配方法与装置

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"3GPP Technical Specification Group Services and System Aspects", 3GPP TS 22.368 V10.0.0: SERVICE REQUIREMENTS FOR MACHINE-TYPE COMMUNICATIONS (MTC); STAGE 1 (RELEASE 10). 3RD GENERATION PARTNERSHIP PROJECT (3GPP), 1 April 2010 (2010-04-01), XP050402279 *
See also references of EP2637378A4 *

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103650551A (zh) * 2013-06-26 2014-03-19 华为技术有限公司 一种对业务处理的方法、系统以及相关设备
CN103650551B (zh) * 2013-06-26 2017-11-17 华为技术有限公司 一种对业务处理的方法、系统以及相关设备
CN106465443A (zh) * 2015-05-18 2017-02-22 华为技术有限公司 D2d通信中的ip地址分配方法及用户设备
CN106465443B (zh) * 2015-05-18 2020-01-17 华为技术有限公司 D2d通信中的ip地址分配方法及用户设备
CN111147622A (zh) * 2015-05-18 2020-05-12 华为技术有限公司 D2d通信中的ip地址分配方法及用户设备
US10798054B2 (en) 2015-05-18 2020-10-06 Huawei Technologies Co., Ltd. IP address allocation method in D2D communication and user equipment

Also Published As

Publication number Publication date
EP2637378A1 (en) 2013-09-11
EP2637378A4 (en) 2014-10-08
CN102668489B (zh) 2015-07-08
US20130250968A1 (en) 2013-09-26
CN102668489A (zh) 2012-09-12

Similar Documents

Publication Publication Date Title
WO2012068728A1 (zh) 获取用户的ip地址的方法和网络实体
EP2448297B1 (en) Information processing method and system, and mobility management network element
US11910292B2 (en) Support of user plane transactions over a mobile network
WO2011140884A1 (zh) Mtc组选择分组数据网网关的方法及移动性管理网元
US8855045B2 (en) Method and system for controlling establishment of local IP access
WO2011054299A1 (zh) 机器类通讯终端信息的获取方法和系统
JP2014505445A (ja) ネットワーク・アプリケーション・サーバからのueアプリケーション・トリガー要求について、モバイル・ネットワークを通じてユーザ装置ueに通知
WO2011134329A1 (zh) 一种小数据包传输的方法和系统
US20110182244A1 (en) Method for supporting context management by home node-b
WO2015062098A1 (zh) 一种网络选择方法及核心网设备
EP2870819B1 (en) Method for revocable deletion of pdn connection
WO2012130085A1 (zh) 与网管系统建立连接的方法、设备及通信系统
WO2010121495A1 (zh) 一种ip地址分配方法及系统
WO2012094957A1 (zh) 一种对mtc终端进行移动性管理的方法和系统
WO2011047589A1 (zh) 网络连接建立方法及装置、pcc策略制定方法及系统
US20150296445A1 (en) Method, device and system for managing packet data network type
WO2011157189A2 (zh) 位置上报方法、设备和系统
WO2011134336A1 (zh) 机器类通信事件上报方法、装置及系统
WO2012130098A1 (zh) 一种获取机器类型通信设备ip地址的方法及系统
WO2011020435A1 (zh) M2m应用服务器下发数据包的方法及系统
WO2011063762A1 (zh) 保证业务连接的方法、网络设备和用户设备
Kunz et al. Machine type communications in 3GPP: From release 10 to release 12
JP6191768B2 (ja) 移動無線通信装置からのデータ転送
WO2011050688A1 (zh) 机器类通讯终端信息的获取方法和系统
WO2011134370A1 (zh) 机器类通信事件上报方法及系统

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 201080004950.1

Country of ref document: CN

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 10860007

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2010860007

Country of ref document: EP