WO2012065298A1 - 获取用户ip地址的方法和网络实体 - Google Patents
获取用户ip地址的方法和网络实体 Download PDFInfo
- Publication number
- WO2012065298A1 WO2012065298A1 PCT/CN2010/078766 CN2010078766W WO2012065298A1 WO 2012065298 A1 WO2012065298 A1 WO 2012065298A1 CN 2010078766 W CN2010078766 W CN 2010078766W WO 2012065298 A1 WO2012065298 A1 WO 2012065298A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- user
- network element
- address
- identifier
- message
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/26—Network addressing or numbering for mobility support
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/50—Address allocation
- H04L61/5007—Internet protocol [IP] addresses
Definitions
- the embodiments of the present invention relate to the field of communications technologies, and in particular, to a method for acquiring a user IP address, a network entity, and a communication system. 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 N AS signaling encryption, roaming, tracking, etc. Function, 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 equipment, if there is no PDP context (bearer) information of the user equipment on the gateway, the gateway performs the following processing: The gateway learns the IP address of the user equipment according to the received data packet, and the gateway according to the configuration The mapping between the IP address and the user equipment IMSI is used to learn the IMSI of the user equipment. The gateway learns the information of the mobility management network element to which the user equipment is attached 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 equipment, and the user equipment initiates a PDP context activation process after receiving the message, thereby initiating a process.
- Business connection establishment process
- an activation process initiated by the network side requires that the user equipment needs to have a static IP address, and the network needs to configure the static IP address of the user equipment in the subscription database and the different network elements of the gateway.
- the server also needs to configure the IP address information of the user equipment.
- the mapping relationship between the static IP address of the user equipment and the identifier IMSI of the user is also configured on the gateway. 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 equipment and the identifier IMSI of the user needs to be met.
- the embodiment of the present invention provides a method for acquiring an IP address of a user, and a network entity, which is used to solve the problem that the IP address cannot be obtained when the network push service cannot be configured for the M2M terminal in the prior art.
- An embodiment of the present invention provides a method for obtaining a user IP address, including: receiving, by a first network element, a message for acquiring a user IP address sent by a second network element; the first network element obtaining a message according to the message for obtaining a user IP address.
- the identifier of the user is sent to the gateway; the first network element receives the IP address of the user sent by the gateway, and sends the IP address of the user to the second network element.
- the embodiment of the present invention provides another method for obtaining a user IP address, including: receiving, by a first network element, a message for acquiring a user IP address sent by a second network element; and acquiring, by the first network element, the message obtained by acquiring the user IP address
- the user's identification, the mobility management network element of the service user is obtained; the mobility management network element of the service user is sent to the mobility management network element of the service user, and the user is notified by the mobility management network element of the service user to establish a connection;
- a network element receives an IP address assigned by the network in the connection establishment process for the user equipment, and sends the IP address of the user equipment to the second network element.
- the embodiment of the present invention provides another method for obtaining a user IP address, including: receiving, by a first network element, a notification message sent by a gateway, where the notification message includes an IP address allocated by the network to the user in the connection establishment process; The network element receives the message that the second network element sends the user IP address, and the first network element sends the IP address to the second network element.
- the embodiment of the present invention provides a network entity for acquiring a user IP address, including a receiving unit, a first learning unit, and a sending unit, where the receiving unit receives a message for acquiring a user IP address sent by the second network element; The unit learns the identifier of the user according to the message for obtaining the user IP address; the sending unit sends the identifier of the user to the gateway; the receiving unit receives the IP address of the user sent by the gateway; the sending unit sends the user The IP address is sent to the second network element.
- the embodiment of the present invention provides a network entity for acquiring a user IP address, including a receiving unit, a first learning unit, a second learning unit, and a sending unit, where the receiving unit receives the acquiring user IP address sent by the second network element.
- the first learned unit obtains the user's IP address according to the The message acquires the identifier of the user, the second learning unit learns the mobility management network element of the service user; the mobility management network element of the service user notifies the user to establish a connection; and the receiving unit receives the network sent by the gateway in the connection establishment process as the user The IP address assigned by the device; the sending unit sends the IP address of the user equipment to the second network element.
- the embodiment of the present invention provides another network entity for acquiring a user IP address, including: the receiving unit receives a notification message sent by the gateway, where the notification message includes an IP address allocated by the network to the user in the connection establishment process; An obtaining unit obtains an IP address from the notification message; the receiving unit receives a message for acquiring a user IP address sent by the second network element; and the sending unit sends the IP address to the second network element.
- the first network element in the embodiment of the present invention obtains an IP address allocated by the network sent by the gateway in the process of establishing a connection, and sends the IP address to the second network element, thereby solving the existing
- the problem that the second network element cannot obtain the IP address cannot be obtained because the static IP address cannot be configured for the M2M terminal.
- FIG. 1 is a network structure diagram of a prior art provided
- FIG. 2 is a schematic flowchart of a method for obtaining a user IP address according to Embodiment 1 of the present invention
- FIG. 3 is a schematic signaling diagram of a method for obtaining a user IP address according to Embodiment 2 of the present invention
- FIG. 5 is a schematic flowchart of a method for obtaining a user IP address according to Embodiment 4 of the present invention
- FIG. 6 is a flowchart of a method for obtaining a user IP address according to Embodiment 5 of the present invention
- schematic diagram FIG. 7 is a schematic diagram of signaling of a method for obtaining a user IP address according to Embodiment 6 of the present invention
- FIG. 8 is a schematic structural diagram of a network entity for obtaining a user IP address according to Embodiments 7, 8, and 9 of the present invention;
- FIG. 9 is a schematic structural diagram of a system for obtaining a user IP address according to Embodiment 10 of the present invention. detailed description
- 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, 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 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) Other logical network elements or network element entities;), or other representations of network element entities or logical network elements, the invention is not limited.
- 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 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 be configured according to The obtained IP address sends data to the user equipment.
- the specific representation of the second network element may be an application server (for example, in an M2M application, specifically, an MTC server), or another representation of a network element entity, which is not limited by the present invention.
- 2 is a schematic flowchart of a method for obtaining a user IP address according to Embodiment 1 of the present invention.
- the first gateway sends the identifier of the user to the gateway, and the gateway triggers the user to establish a connection, and the IP address allocated by the network side during the establishment of the connection process.
- the first network element is sent to the first network element, and the first network element sends the IP address to the second network element, including the following steps:
- the first network element receives the message of the user IP address sent by the second network element, and the first network element obtains the identifier of the user according to the message of obtaining the user IP address, and sends the identifier of the user to the gateway.
- the first network element may obtain the identifier of the user, which may be: if the message of the user's IP address carries the identifier of the user, the identifier of the user may be directly obtained; if the message for obtaining the IP address of the user is carried in the message
- the user name can be used to query the storage information according to the user name to know the user's identity.
- Sending the identity of the user to the gateway may specifically be to the GGSN or
- the PGW sends a request message for the user connection establishment.
- the first network element may also send the user's identification to the gateway through other messages, and the name of the message is not limited to this patent.
- the first network element receives the IP address of the user sent by the gateway, and sends the IP address of the user to the second network element.
- the gateway sends the first network element to the IP address of the corresponding user according to the identifier of the user; or the gateway triggers the user to initiate connection establishment according to the identifier of the user.
- the network side assigns an IP address to the user.
- the gateway After the gateway knows the IP address, the gateway sends the IP address to the first network element.
- the first network element After obtaining the IP address of the user, the first network element sends the IP address of the user to the second network element. For example, the response message or the IP address request response message can be queried through the IP address.
- the specific triggering user initiates the connection establishment process as follows:
- the gateway learns the mobility management of the service user.
- a network element eg, MME, SGSN
- sending, by the mobility management network element, a notification user connection establishment request the gateway acquiring an IP address allocated by the network to the user equipment during the connection establishment process.
- the process for the gateway to learn the mobility management network element of the service user includes the following three types: a) the first network element learns the information of the mobility management network element of the service user according to the user name or the identifier of the user (according to the user name or The identifier of the user queries the storage information or queries the HSS/HLR to obtain the information of the mobility management network element of the service user according to the identifier of the user.
- the information of the mobility management network element of the service user is sent to the gateway, and the gateway learns the service user. Mobility management network element.
- the information of the mobility management network element of the service user may be the address of the SGSN/MME of the service user or the domain name of the SGSN/MME, and the SGSN/MME refers to the SGSN or the MME.
- the first network element obtains the location information of the user according to the user name or the identifier of the user (inquiring the storage information according to the user name or the identifier of the user to obtain the location information of the user), and transmitting the location information of the user to the gateway, where the gateway The location information querying user of the user is informed of the mobility management network element of the user.
- the location information of the user may be the cell information (CGI or ECGI, etc.) where the user is located, or tracking area information (TAI), or routing area information (RAI), or tracking area list information (TA List), or access network identification ( eNodeB ID or RNC ID or BSC ID, etc.).
- the gateway queries the HSS/HLR to obtain the information of the mobility management network element of the service user according to the identifier of the user sent by the first network element, and learns the mobility management network element that serves the user.
- the IP address of the user sent by the first network element receiving gateway is allocated by the network to the user equipment in the connection establishment process, and the process of obtaining the IP address by the gateway is:
- the gateway obtains an IP address allocated by the network to the UE in the connection establishment process, and the gateway sends the IP address to the first network element;
- the UE After the connection establishment is completed, the UE obtains the IP address allocated by the network side to the UE in the connection establishment process, and the UE sends the IP address allocated by the network to the UE in the establishment process.
- the gateway sends the IP address to the first network element.
- the second embodiment is a specific implementation manner of the first embodiment, and is described by using a specific signaling process.
- Step 1 The first network element receives an IP address query or an IP address request message sent by the second network element.
- the IP address query message or the IP address request message takes as an example a message carrying a user name (user FQDN, or URI or URL, etc.).
- Step 2 The first network element sends a connection establishment request message to the GGSN/PGW, where the connection establishment request message carries the identifier of the user.
- the connection establishment request message may also be other messages, and the patent does not limit the message name of the message.
- the first network element After the first network element obtains the user name in step 1, the first network element obtains the identifier of the user according to the user name, and specifically, the first network element obtains the user according to the mapping relationship between the user name and the user identifier according to the user name.
- the mapping between the user name and the user identifier may be in the following two cases: a. a binding relationship between the pre-configured user name and the user's identifier; b. in other previous processes (such as connecting) Establish the binding relationship between the user name established in the process and the user's identity.
- the GGSN/PGW notifies the first network element of the identifier of the user, for example, the GGSN obtains the PDP activation process initiated by the user, and the GGSN obtains the GGSN.
- the user identifier for example: IMSI or MSISDN or IMEI
- the GGSN sends a Register message to the first network element, where the Register message carries the identifier of the user and the user name, and the first network element stores the identifier of the user.
- the first network element is bound to the user's identity and user name obtained from the above Register message).
- the user's PDP context or PDN connection can be deleted (including the user being in an isolated state).
- the first network element may further carry location information (such as cell information, or the location information (such as cell information) of the user (especially for a low mobility user Low mobility, that is, a user whose location is fixed or only moves in a specific area) in the connection establishment request message.
- location information such as cell information, or the location information (such as cell information) of the user (especially for a low mobility user Low mobility, that is, a user whose location is fixed or only moves in a specific area) in the connection establishment request message.
- information of the SGSN/MME of the serving user the SGSN/MME to which the user can attach or the user has attached, the information specific It can be: the address of the SGSN/MME or the FQDN of the SGSN/MME).
- 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 which is stored in the first network
- the location information of the user 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 pre-configured with the identifier of the user or the username.
- the GGSN/PGW in the PDP context activation initiated by the user or the PDN connection establishment process (including the Attach process), notifies the first network element of the location information of the user or 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 service user, and the GGSN/PGW sends a Register message to the first network element,
- the 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, and the first network element stores the location information of the user or the information of the SGSN/MME of the service user (the location information of the user or the service user)
- the information of the SGSN/MME is bound to the identifier of the user, or the relationship between the identifier of the user and the username on the first network element may also be used.
- the location information of the user or the information of the SGSN/MME of the service user is bound to the username.
- the GGSN/PGW notifies the location information of the user or the information of the SGSN/MME of the serving user to the first network element, 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 connection establishment request 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 can serve information about the GGSN/PGW of the user.
- the first network element configures the information of the GGSN/PGW that can serve the group according to the group identifier of the group to which the user belongs (for example, Group ID, APN, IMSI number segment, etc.). After the first network element obtains the identifier of the user or the APN used by the user, 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 3 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 2, the GGSN/PGW may be based on the location information of the user or the information of the SGSN/MME of the serving user.
- the SGSN/MME of the service user (the SGSN/MME to which the user can attach or the user has attached) is known.
- 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, and the DNS server obtains the information of the SGSN/MME according to the RA or the TA, 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, and after the GGSN/PGW obtains the RA or the TA, the mapping relationship is queried to obtain the SGSN/MME.
- Step 4 If, in step 2, 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 flow of obtaining the information of the SGSN attached to the user by the specific GGSN to the HLR belongs to the prior art. I will not repeat them here.
- Step 5 The GGSN/PGW learns the SGSN/MME of the service user in step 3 or step 4.
- 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 may notify the user of the APN, and cause the user to initiate 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.
- 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 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 the user receives the 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. 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 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 context activation process or a PDN connection establishment process.
- the network allocates an IP address to the user.
- the GGSN/PGW obtains an example in which the network assigns an IP address to a user.
- the IP address allocated by the network to the user equipment during the connection establishment process of the GGSN/PGW includes:
- the gateway after the gateway (GGSN/PGW) receives the session management request message (Create PDP Context Request/Create Session Request) sent by the mobility management network element (SGSN/MME), the gateway is configured according to the configuration.
- the IP address range assigns an IP address to the user; or,
- the gateway After the gateway (GGSN/PGW) receives the session management request message (Create PDP Context Request/Create Session Request) sent by the mobility management network element (SGSN/MME), the gateway sends the gateway to the DHCP server or AAA.
- the server requests to assign IP addresses to users. Address.
- the DHCP server or the AAA server assigns an IP address to the user, the IP address is sent to the GGSN/PGW.
- Step 8 After the GGSN/PGW obtains the IP address of the user in step 7, the GGSN/PGW sends the IP address of the user to the first network element. Specifically, the GGSN/PGW sends a Register IP Address message to the first network element, where the Register IP Address message carries the identifier of the user (for example: IMSI) and the IP address of the user.
- the Register IP Address message carries the identifier of the user (for example: IMSI) and the IP address of the user.
- the first network element learns the IP address of the user, and the first network element can also associate the user identifier, the user name, and the IP address of the user (for example, the user identifier, the user name, and the user's IP address are tied. set).
- the second network element obtains the IP address of the user from the first network element (see step 1), if the first network element stores the user's IP address ( The valid IP address), the first network element returns the IP address of the user to the second network element. If the IP address of the user is not stored in the first network element (or the IP address of the stored user is invalid), the first network element triggers the process described in this embodiment, and the user is assigned an IP address by using the embodiment. Establish a connection with the network side.
- Step 9 The first network element sends the IP address of the user to the second network element.
- the first network element sends a Return IP Address message to the second network element, where the Return IP Address message carries the username and the IP address of the user.
- Step 10 The second network element constructs a data packet according to the obtained IP address, and sends a data packet to the user.
- the GGSN/PGW initiates the update process.
- the IP address of the user saved in the first network element is notified to be invalid.
- the GGSN/PGW sends a Release (IP address of the user) / Uptate (IP address of the updated user) IP Address message to the first network element, where the Release/Uptate IP Address message carries the username and/or the IP address of the user.
- the first network element receives the above Release/Uptate IP Address. After the message is processed by the first network element, the DNS Server function module in the first network element releases or modifies the IP address of the user.
- the first network element can actively notify the second network element that the IP address of the user is invalid or modified. For example, the first network element sends a Notify IP Address message to the second network element, where the message carries the user name and indication information indicating that the user's IP address is unavailable (invalid). If the second network element receives the above-mentioned Notify IP Address message, the second network element needs to obtain the user's IP address from the first network element before sending the data packet to the user next time (see step 1 for details).
- FIG. 4 is a schematic flowchart of another method for obtaining a user IP address according to Embodiment 3 of the present invention.
- another network architecture is provided, and an interface exists between the first network element and the SGSN/MME, so A network element may directly send a connection establishment request message to the SGSN/MME.
- the first network element receives a message that is sent by the second network element to obtain a user IP address.
- the first network element obtains the identifier of the user according to the message for obtaining the user IP address, and obtains the mobility management network element of the monthly service user.
- the first network element Obtaining, by the first network element, the identifier of the user according to the message of acquiring the user IP address, the message that the user IP address is obtained, the identifier of the user is carried, and the first network element obtains the user IP address from the user
- the message of the user is obtained in the message; or the message of the user device 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 information about the mobility management network element of the service user includes: the first network element queries the storage information according to the user name or the identifier of the user to obtain the information of the mobility management network element of the service user; or the first network element queries the HSS according to the identifier of the user.
- the HLR obtains information of the mobility management network element of the service user; or
- the first network element queries the storage information according to the user name or the identifier of the user to obtain the location information of the user, and queries the server (the DNS server or the server thereof) to obtain the mobility management network of the service user according to the obtained location information of the user.
- the process of the query can refer to the above embodiment.
- the first network element sends the identifier of the user to the mobility management network element of the service user, where the mobility management network element of the service user notifies the user to establish a connection.
- the first network element sends a connection establishment indication message to the mobility management network element, where the message carries the identifier of the user; the mobility management network element triggers the user to initiate a connection establishment process.
- the process of connection establishment can be referred to the above embodiment.
- the network sent by the first network element receiving gateway is allocated to the user equipment in a connection establishment process.
- An IP address, and the IP address of the user equipment is sent to the second network element.
- the specific process for the gateway to obtain the IP address assigned by the network to the user in the connection establishment process may also refer to step 202.
- Embodiment 4 is a specific implementation manner of Embodiment 3, and is described by a specific signaling process.
- Step 1 The second network element sends an IP address acquisition message to the first network element.
- the message carries the username or the identifier of the user.
- Step 2 The first network element obtains the identifier of the user, and obtains the mobility management network element of the knowledge user.
- Embodiment 1 For the method of obtaining the identifier of the user, refer to Embodiment 1 or Embodiment 2.
- the methods for knowing the mobility management network element of the service user may include:
- the first network element sends an inquiry message to the HLR/HSS, where the query message carries the identifier of the user (IMSI or MSISDN or IMEI, etc.), and obtains information (address) of the mobility management network element of the user of the monthly service. Or FQDN).
- the HLR/HSS queries the registration information of the user according to the identifier of the user, and obtains the information of the SGSN/MME attached to the user, 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 equipment or the identifier of the user to obtain information about the mobility management network element of the service user. Specifically, the first network element obtains a username or After the identifier of the user, the stored user name or the binding relationship table of the identifier of the user and the information of the SGSN/MME of the service user is queried, so that the information of the mobility management network element of the service user is obtained.
- the first network element After the first network element obtains the user name or the identifier of the user, query the stored user name or the identifier of the user and the location information of the user (for example, the cell information where the user is located, or the tracking area information, or the routing area) The binding relationship table between the 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 queries the server (for example, a DNS server) for information about a mobility management network element capable of serving the user according to the obtained location information of the user.
- Step 3 After the first network element obtains the mobility management network element information of the service user, the first network element sends a connection establishment request message to the mobility management network element.
- the connection establishment message may also be other messages, and the patent does not limit the name of the above message;
- the message carries the identifier of the user.
- the message further carries the location information of the user (cell information, or tracking area information, or routing area information, or tracking area list information or identification information of the access network). ). If the APN used by the user is stored on the first network element, the APN information used by the user may also be carried in the message. For the process of obtaining the APN, refer to Step 2 of Embodiment 2 above.
- FIG. 6 is a schematic flowchart of another method for obtaining a user IP address according to Embodiment 5 of the present invention.
- the first network element first acquires an IP address allocated by the network for the user in the connection establishment process, and when the second When the network element obtains an IP address, the IP address is sent to the second network element.
- the first network element receives a notification message sent by the gateway, where the notification message includes an IP address allocated by the network to the user in the connection establishment process;
- the first network element receives a message that is sent by the second network element to obtain a user IP address.
- the first network element sends the IP address to the second network element.
- Embodiment 6 is a specific implementation manner of Embodiment 7, and is described by a specific signaling process.
- Step 1 The user initiates a connection establishment process, and the connection establishment process may include a user initiated PDP activation process or a PDN connection establishment process.
- the network assigns an IP address to the user.
- the method for the specific network to assign an IP address to the user refer to the method described in step 7 of Embodiment 2 above.
- Step 2 The gateway (GGSN/PGW) notifies the first network element of the IP address of the user.
- the notification message carries the user's IP address and the user's information (the user's identity or user name).
- the first network element stores a binding relationship between the user's information (the user's identity or username) and the user's IP address.
- Step 3 The application server (for example, the MTC Server) requests the first network element for the user's IP address.
- the application server sends a message obtained by the IP address to the first network element, where the IP address acquisition message carries the identifier or user name of the user.
- the first network element queries the stored identity of the user or the binding relationship between the user name and the IP address of the user, and sends the IP address of the user to the application server.
- FIG. 8 is a schematic structural diagram of a network entity 80 for obtaining a user IP address according to the seventh, eighth, and ninth embodiments of the present invention, including a receiving unit 801, a first learning unit 802, a sending unit 803, or a second learning unit 804.
- the receiving unit 801 receives the message of obtaining the user IP address sent by the second network element; the first learning unit 802 learns the identifier of the user according to the message for obtaining the user IP address; the sending unit 803 sends the identifier of the user to the gateway.
- the receiving unit 801 receives the IP address of the user sent by the gateway; the sending unit 803 sends the IP address of the user to the second network element.
- the first learning unit 802 according to the message for acquiring the user's IP address, knows that the identifier of the user specifically includes: the first learning unit 802 obtains the identifier of the user from the message for obtaining the user IP address; or The message of the user equipment IP address carries the user name, and the first learning unit 802 queries the storage information according to the user name to obtain the identifier of the user.
- a second learning unit 804 is further included, and the second learning unit 804 is based on a user name or a user.
- the identifier is used to learn the information of the mobility management network element of the service user, and the sending unit 803 sends the information of the mobility management network element of the service user to the gateway; or the second learning unit 804 learns the user according to the user name or the identifier of the user.
- Location information the sending unit 803 sends the location information of the user to the gateway.
- the receiving unit 801 receives the message of the user IP address sent by the second network element.
- the first learning unit 802 acquires the identifier of the user according to the message for obtaining the user IP address, and the second learning unit 804 learns the mobility management of the service user.
- the sending unit 803 sends the identifier of the user to the mobility management network element of the service user, and notifies the user to establish a connection by using the mobility management network element of the service user; the receiving unit 801 receives the network sent by the gateway in the connection establishment.
- the process is an IP address assigned by the user equipment; the sending unit 803 sends the IP address of the user equipment to the second network element.
- the first obtaining the identifier of the user according to the message of obtaining the user IP address specifically includes: the first obtaining the identifier of the user obtained from the message of obtaining the user IP address; or obtaining the IP address of the user equipment
- the message carries the user name, and the first knowledge is obtained by querying the storage information according to the user name to obtain the identifier of the user.
- the second learning unit 804 knows that the mobility management network element of the service user specifically includes: the second learning unit 804 queries the storage information according to the user name or the identifier of the user to obtain the information of the mobility management network element of the service user; or the second learning unit 804 The information about the mobility management network element of the service user is obtained by the HSS/HLR according to the identifier of the user; or the second learning unit 804 queries the storage information according to the user name or the identifier of the user to obtain the location information of the user, and according to the obtained user's location information. The location information is queried by the server to obtain information about the mobility management network element of the service user.
- the receiving unit 801 receives the notification message sent by the gateway, where the notification message includes an IP address allocated by the network for the user in the connection establishment process, and the receiving unit 801 receives the message of acquiring the user IP address sent by the second network element.
- 802 obtains an IP address; sending unit 803 will IP address The address is sent to the second network element.
- FIG. 9 is a schematic structural diagram of a network entity for obtaining a user IP address according to Embodiment 10 of the present invention, a second network element 901, a first network element 902, a gateway 903, and a mobility management entity 904.
- a network entity for obtaining a user IP address according to Embodiment 10 of the present invention, a second network element 901, a first network element 902, a gateway 903, and a mobility management entity 904.
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (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 信令和 N AS信令加密以及漫游、 跟踪等功能, 分配用户临时身份标识、 安全 功能等, 它对应于当前 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地址短缺。进一步, 还会导致在网关上配置海量的配置信息, 由于网关并不具有专门的数据库的 功能, 将导致网关实现相当复杂。 另外, 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地址; 发送单元将所述用户设备的 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地址的方法的网络实体 结构示意图;
图 9为本发明实施例十提供的获取用户 IP地址的方法的***结构示意图。 具体实施方式
下面将结合本发明实施例中的附图, 对本发明实施例中的技术方案进行清 楚、 完整地描述, 显然, 所描述的实施例仅仅是本发明一部分实施例, 而不是 全部的实施例。 基于本发明中的实施例, 本领域普通技术人员在没有做出创造 性劳动前提下所获得的所有其他实施例, 都属于本发明保护的范围。 另外本发 明实施例要解决的问题虽然由 M2M应用引起的,但是本发明实施例的技术方案 也可以应用在 H2H通信***, 以及其他涉及用户的 IP地址的通信***。
本发明实施例中的第一网元为具有寻址用户 (触发用户发起连接建立) 的 功能的网元, 即向核心网网元提供用户的标识(例如: IMSI或 MSISDN或 IM曰 等), 以供核心网网元(例如: SGSN/MME或 GGSN/PGW或 HLR/HSS等) 根据所述用户的标识触发用户发起连接建立流程的功能( PDP激活流程或 PDN 连接建立流程等)的网元。 所述第一网元的具体表现形式可以是具有 DNS服务 器或 DHCP服务器或 AAA服务器功能的网元实体(即 DNS服务器或 DHCP 服务器或 AAA服务器功能单独部署, 为单独的功能实体设备), 或者由具有上 述功能的多个网元组合的逻辑网元或网元实体(例如, 在 M2M应用中, 具体可 以是一个 M2M平台或 M2M Proxy, 或者所述第一网元是 DNS服务器和 AAA 服务器组成的其他逻辑网元或网元实体;), 或者其他表现形式的网元实体或逻辑 网元, 本发明不作限制。
本发明实施例中的第二网元为具有向用户推送业务功能的服务器, 需要根 据用户名 (例如: 用户的域名或 URI或 URL等)到其他网元获取用户 IP地址 的功能的网元。 进一步的, 获得了用户的 IP地址之后, 所述第二网元可以根据
获得的 IP地址向用户设备发送数据。 所述第二网元的具体表现形式可以是应用 月良务器( Application Server,例如,在 M2M应用中,具体可以是 MTC server ), 或者其他表现形式的网元实体, 本发明不作限制。 图 2为本发明实施例一提供的获取用户 IP地址的方法的流程示意图, 第一 网关将用户的标识发送给网关, 网关触发用户建立连接, 并将网络侧在建立连 接过程中分配的 IP地址通知给第一网元,再由第一网元将 IP地址发送给第二网 元, 包括以下步骤:
201、 第一网元接收第二网元发送的获取用户 IP地址的消息; 第一网元根 据所述获取用户 IP地址的消息获知所述用户的标识, 将所述用户的标识发送给 网关;
其中, 第一网元获知用户的标识具体可以是: 如果所述获取用户 IP地址的 消息中携带了用户的标识, 则可以直接获知用户的标识; 如果所述获取用户 IP 地址的消息中携带了用户名, 则可以才艮据用户名查询存储信息获知用户的标识。
将所述用户的标识发送给网关 (GGSN或 PGW)具体可以通过向 GGSN或
PGW发送为用户连接建立请求消息。第一网元也可以通过其他消息把用户的标 识发送给网关, 对所述消息的名称本专利不作限制。
202、 第一网元接收网关发送的所述用户的 IP地址, 并将所述用户的 IP地 址发送给所述第二网元。
如果之前用户已经建立过连接, 网关上已经获得用户的 IP地址, 则网关才艮 据用户的标识将对应用户的 IP地址发送第一网元; 或者网关根据用户的标识触 发用户发起连接建立, 在连接建立流程中, 网络侧为用户分配 IP地址。 网关获 知该 IP地址后, 并将所述 IP地址发送给第一网元。 第一网元获得用户的 IP地 址后,将用户的 IP地址发送给上述第二网元, 例如: 可以通过 IP地址查询响应 消息或 I P地址请求响应消息。
具体的触发用户发起连接建立流程如下: 网关获知服务用户的移动性管理
网元(例如: MME, SGSN ); 通过所述移动性管理网元发送通知用户连接建立 请求; 所述网关获取在连接建立过程中网络为所述用户设备分配的 IP地址。
其中, 网关获知服务用户的移动性管理网元的过程包括如下三种: a)所述第 一网元根据用户名或者用户的标识获知服务用户的移动性管理网元的信息(根 据用户名或者用户的标识查询存储信息或者才艮据用户的标识查询 HSS/HLR获 得服务用户的移动性管理网元的信息), 将服务用户的移动性管理网元的信息发 送给网关, 则网关获知服务用户的移动性管理网元。 服务用户的移动性管理网 元的信息可以是服务用户的 SGSN/MME 的地址或 SGSN/MME 的域名, SGSN/MME是指 SGSN或 MME。 b)所述第一网元根据用户名或者用户的标识 获知用户的位置信息(根据用户名或者用户的标识查询存储信息获得用户的位 置信息), 将用户的位置信息发送给网关, 网关根据所述的用户的位置信息查询 月良务器获知 务所述用户的移动性管理网元。 用户的位置信息可以为用户所在 的小区信息(CGI或 ECGI等), 或跟踪区信息(TAI ), 或路由区信息 (RAI), 或 跟踪区列表信息(TA List ), 或接入网标识(eNodeB ID或 RNC ID或 BSC ID 等)。 c)网关根据第一网元发送的所述用户的标识向 HSS/HLR查询获得服务用 户的移动性管理网元的信息, 获知服务所述用户的移动性管理网元。
所述第一网元接收网关发送的所述用户的 IP地址为网络在连接建立流程为 所述用户设备分配的, 网关获得该 IP地址的过程为:
1 )、 在连接建立过程中, 网关就获得网络侧在连接建立流程中为 UE分配 的 IP地址, 网关将所述 IP地址发送给所述第一网元; 或,
2 )、 在连接建立完成后, UE获得连接建立流程中网络侧为 UE分配的 IP 地址后, UE向网关发送网络在建立流程中为 UE分配的 IP地址。 网关将所述 IP地址发送给所述第一网元。
如图 3所示, 实施例二为实施例一的具体实现方式, 通过具体的信令流程 进行描述。
步骤 1、 第一网元接收第二网元发送的 IP地址查询或 IP地址请求消息。
在此, IP地址查询消息或 IP地址请求消息中以携带用户名 (用户 FQDN, 或 URI或 URL等)信息为例。
步骤 2、 第一网元向 GGSN/PGW发送连接建立请求消息, 上述连接建立 请求消息中携带用户的标识。 所述连接建立请求消息还可以是其他消息, 本专 利对此消息的消息名称不作限制。
第一网元在步骤 1 中获得了用户名后, 第一网元根据用户名获得用户的标 识, 具体可以是第一网元根据用户名查询用户名和用户的标识之间的映射关系 表获得用户的标识, 所述用户名和用户的标识之间的映射关系表可以是以下两 种情况: a、 预先配置的用户名和用户的标识之间的绑定关系; b、 在之前的其 他流程(如连接建立流程) 中建立的用户名和用户的标识之间的绑定关系。 在 用户主动发起的 PDP上下文激活或 PDN连接建立流程 (包含 Attach流程 )中, GGSN/PGW将用户的标识通知给所述第一网元, 例如: GGSN在用户发起的 PDP激活流程中, GGSN获得了用户的标识(例如: IMSI或 MSISDN或 IMEI ), GGSN向所述第一网元发送 Register消息,上述 Register消息中携带用户的标 识和用户名, 所述第一网元保存用户的标识(所述第一网元将从上述 Register 消息中获得的用户的标识和用户名绑定)。 当 GGSN/PGW将用户的标识通知到 所述第一网元后, 用户的 PDP上下文或 PDN连接可以被删除(包含用户处于 分离态)。
进一步的, 第一网元还可以在连接建立请求消息中携带用户 (尤其是对于 低移动用户 Low mobility, 即位置固定或只在特定的区域移动的用户)所在的位 置信息(如小区信息, 或跟踪区信息 TA, 或路由区信息 RA, 或跟踪区列表信 息, 或接入网标识), 或者服务用户的 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协议(需要作增强扩展)。
步骤 3、 如果在步骤 2中第一网元向 GGSN/PGW提供了用户的位置信息 或者服务用户的 SGSN/MME的信息, GGSN/PGW可以根据用户的位置信息 或者服务用户的 SGSN/MME的信息获知服务用户的 SGSN/MME (用户可以附 着的或用户已经附着的 SGSN/MME )。
如果在步骤 2 中, 第一网元向 GGSN/PGW 提供的是服务用户的 SGSN/MME的信息(例如: SGSN/MME的地址或 FQDN ), 则直接获知服务 用户的 SGSN/MME。
如果在步骤 2中, 第一网元向 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。
步骤 4、 如果在步骤 2中, 第一网元没有在连接建立请求消息中向 GGSN 提供用户的位置信息或者服务用户的 SGSN/MME的信息, 则 GGSN根据用户 的标识向 HLR请求服务用户的 SGSN/MME。
具体 GGSN向 HLR获取用户附着的 SGSN的信息的流程属于现有技术,
在此不再赘述。
步骤 5、 GGSN/PGW在步骤 3或步骤 4中获知服务用户的 SGSN/MME。 GGSN/PGW向获知的 SGSN/MME发送连接建立指示消息。
在 GERAN/UTRAN 中, 上述连接建立指示消息可以是 PDU Notification Request消息( GGSN发送给 SGSN )。 上述 PDU Notification Request消息中 携带了用户的标识(例如: IMSI )。 在步骤 2中, 如果第一网元向 GGSN提供 了用户所在的位置(例如:用户所在的 RA ),则 GGSN在上述 PDU Notification Request消息中携带用户所在的位置信息给 SGSN。 在步骤 2中, 如果第一网 元还向 GGSN提供了用户使用的 APN, 则 GGSN 在上述 PDU Notification Request消息中携带用户使用的 APN给 SGSN。 SGSN可以将所述 APN通知 给用户, 使用户根据所述 APN发起连接建立。
在 E-UTRAN 中, 上述连接建立指示消息可以是 Downlink Notification Request消息(PGW发送给 SGW, SGW再发送给 MME )。 上述 Downlink Notification Request消息中携带了用户的标识(例如: IMSI )。 在步骤 2中, 如 果第一网元向 PGW提供了用户所在的位置信息(例如: 用户所在的 TA ), 则 PGW在上述 Downlink Notification Request消息中携带用户所在的位置信息给 MME。
步骤 6、 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在上述用户所在的位置范围 内寻呼用户。
步骤 7、用户发起 PDP上下文激活流程或 PDN连接建立流程,在上述 PDP 上下文激活流程或 PDN连接建立流程中, 网络为用户分配 IP地址。
在此以在连接建立过程中, GGSN/PGW就获得网络为用户分配 IP地址这 种方式为例。 网关 GGSN/PGW获得连接建立过程中网络为所述用户设备分配 的 IP具体包括:
1 )、 网关(GGSN/PGW )在收到移动性管理网元(SGSN/MME )为用 户发送的会话管理请求消息 (Create PDP Context Request/Create Session Request )后, 所述网关才艮据配置的 IP地址范围为用户分配 IP地址; 或,
2 )、 网关(GGSN/PGW )在收到移动性管理网元(SGSN/MME )为用 户发送的会话管理请求消息 (Create PDP Context Request/Create Session Request )后, 所述网关向 DHCP服务器或 AAA服务器请求为用户分配 IP地
址。所述 DHCP服务器或 AAA服务器为用户分配了 IP地址后,将所述 IP地址 发送给 GGSN/PGW。
步骤 8、 GGSN/PGW通过步骤 7获得用户的 IP地址后, GGSN/PGW将 用户的 IP地址发送给第一网元。具体的, GGSN/PGW向第一网元发送 Register IP Address消息,上述 Register IP Address消息中携带用户的标识(例如: IMSI ) 和用户的 IP地址。
通过本步骤, 第一网元获知了用户的 IP地址, 第一网元还可以将用户的标 识, 用户名和用户的 IP地址关联在一起(例如: 将用户的标识, 用户名和用户 的 IP地址绑定)。 这样, 当后续有第二网元向用户发送数据包时, 第二网元向 第一网元获取用户的 IP地址(见步骤 1描述), 如果第一网元中存储了用户的 IP地址(有效的 IP地址), 则第一网元会向第二网元返回用户的 IP地址。 如果 第一网元中没有存储用户的 IP地址(或存储的用户的 IP地址为无效), 则第一 网元触发本实施例描述的流程, 通过本实施例为用户分配了 IP地址, 使用户和 网络侧之间建立连接。
步骤 9、 第一网元将用户的 IP地址发送给第二网元。
具体的,第一网元向第二网元发送 Return IP Address消息,上述 Return IP Address消息中携带用户名和用户的 IP地址。
步骤 10、 第二网元根据获得的 IP地址构造数据包, 向用户发送数据包。 后续的过程中: 当用户的 IP地址皮释放或改变后 (例如: 用户的 PDP上 下文或 PDN连接被释放或者用户的 PDP或承载上下文发生修改导致用户的 IP 地址改变), GGSN/PGW发起更新流程,通知第一网元其中保存的用户的 IP地 址无效。 具体的, GGSN/PGW向第一网元发送 Release (释放用户的 IP地址) /Uptate(更新用户的 IP地址) IP Address消息,上述 Release/Uptate IP Address 消息中携带用户名和 /或用户的 IP地址(如果是 Release IP Address消息, 则 消息中只需要携带用户名即可。如果是 Update IP Address消息, 则消息中需要 携带用户名和用户的 IP地址)。 第一网元收到上述 Release/Uptate IP Address
消息后,通过第一网元内部处理,第一网元中的 DNS Server功能模块释放或修 改用户的 IP地址。
当然, 如果第一网元获知了用户的 IP地址释放或修改, 则第一网元可以主 动通知第二网元所述用户的 IP地址无效或修改。 例如: 第一网元向第二网元发 送 Notify IP Address消息, 上述消息中携带用户名和指示用户的 IP地址不可用 (无效)的指示信息。 如果第二网元收到上述 Notify IP Address消息后, 第二 网元下次向用户发送数据包之前需要向第一网元获取用户的 IP地址(具体见步 骤 1 )。
本实施例提供了一种地址分配的方法, 满足了行业用户触发用户设备发起 业务的需求, 同时避免了为用户分配静态 IP地址而导致的 IP地址短缺的问题, 进一步, 本实施例还避免了在网关和其他多个设备上配置海量的静态数据的问 题, 减少了操作维护的工作量和对网关实现的影响。 图 4 为本发明实施例三提供的另一种获取用户 IP地址的方法的流程示意 图, 该实施例中提供了另一种网络架构, 第一网元与 SGSN/MME之间存在接 口, 因此第一网元可以直接向 SGSN/MME发送连接建立请求消息。
401、 第一网元接收第二网元发送的获取用户 IP地址的消息;
402、 第一网元根据所述获取用户 IP地址的消息获取所述用户的标识, 获 知月良务用户的移动性管理网元;
所述第一网元根据所述获取用户 IP地址的消息获取所述用户的标识包括: 所述获取用户 IP地址的消息中携带用户的标识, 所述第一网元从所述获取用户 IP地址的消息中获得用户的标识;或者所述获取用户设备 IP地址的消息中携带 用户名, 所述第一网元根据用户名查询存储信息获得用户的标识。
获知服务用户的移动性管理网元具体包括: 第一网元根据用户名或者用户 的标识查询存储信息获得服务用户的移动性管理网元的信息; 或者第一网元 根据用户的标识查询 HSS/HLR获得服务用户的移动性管理网元的信息;或者
所述第一网元根据用户名或者用户的标识查询存储信息获得用户的位置信 息, 并根据获得的用户的位置信息向服务器 (DNS服务器, 或者自身的服务 器) 查询获得服务用户的移动性管理网元的信息, 查询的过程可以参考上述 实施例。
403、 第一网元将所述用户的标识发送给所述服务用户的移动性管理网元, 所述服务用户的移动性管理网元通知用户建立连接;
具体为: 第一网元向所述移动性管理网元发送连接建立指示消息, 所述消 息中携带了用户的标识; 移动性管理网元触发用户发起连接建立流程。 连接建 立的流程可以参考上述的实施例。
404、第一网元接收网关发送的网络在连接建立流程为所述用户设备分配的
IP地址, 并将所述用户设备的 IP地址发送给所述第二网元。 网关获得网络在连 接建立流程中为用户分配的 IP地址的具体过程也可以参考步骤 202。
如图 5所述, 实施例四为实施例三的具体实现方式, 通过具体的信令流程 进行描述。
步骤 1 : 第二网元向第一网元发送 IP地址获取消息。
所述消息中携带用户名或者用户的标识。
步骤 2: 第一网元获取所述用户的标识,并且获知 务用户的移动性管理网 元。
获取用户的标识的方法可以参考实施例一或实施例二。 获知服务用户的移 动性管理网元的方法可以有:
1 ) 所述第一网元向 HLR/HSS发送查询消息, 所述查询消息中携带用户 的标识( IMSI或 MSISDN或 IMEI等),获得获知月良务用户的移动性管理网元的 信息(地址或 FQDN )。 HLR/HSS才艮据用户的标识查询用户在其上的注册信息 得到用户所附着的 SGSN/MME的信息, 然后发送给所述第一网元。
2 ) 所述第一网元根据用户设备的用户名或用户的标识查询存储信息获得 服务用户的移动性管理网元的信息。 具体包括, 所述第一网元获得了用户名或
用户的标识后查询存储的用户名或用户的标识和服务用户的 SGSN/MME 的信 息的绑定关系表, 从而获得服务用户的移动性管理网元的信息。
3 )、 所述第一网元获得了用户名或用户的标识后查询存储的用户名或用户 的标识和用户所在的位置信息 (例如, 用户所在的小区信息, 或跟踪区信息, 或路由区信息, 或跟踪区列表信息或接入网的标识信息)之间的绑定关系表, 从而获得用户所在的位置信息。 所述第一网元根据获得的用户所在的位置信息 向服务器(例如, DNS服务器)查询能够服务用户的移动性管理网元的信息。
步骤 3: 所述第一网元获得了服务用户的移动性管理网元信息后,所述第一 网元向所述移动性管理网元发送连接建立请求消息。 所述连接建立消息也可以 是其他消息, 本专利不对上述消息的名称作限制;
所述消息中携带用户的标识, 可选的, 所述消息中还携带了用户的位置信 息(小区信息, 或跟踪区信息, 或路由区信息, 或跟踪区列表信息或接入网的 标识信息)。如果在所述第一网元上存储了用户使用的 APN,则所述消息中还可 以携带用户使用的 APN信息。 具体获取 APN的过程可以参考上述的实施例二 步骤 2。
步骤 4~8: 可以参见上述实施例二中类似的步骤 6~10。 图 6为本发明实施例五提供的另一种获取用户 IP地址的方法的流程示意 图,该实施例中由第一网元先获取网络在连接建立流程中为用户分配的 IP地址, 当第二网元获取 IP地址时, 就将所述的 IP地址发送给第二网元。
601. 第一网元接收网关发送的通知消息, 所述通知消息中包含网络在连 接建立流程中为用户分配的 IP地址;
602. 第一网元接收第二网元发送的获取用户 IP地址的消息;
603. 第一网元将所述 IP地址发送给所述第二网元;
如图 7所示, 实施例六为实施例七的具体实现方式, 通过具体的信令流程 进行描述。
步骤 1 : 用户发起连接建立流程, 所述连接建立流程可以包括用户发起的 PDP激活流程或 PDN连接建立流程。 在所述流程中, 网络为用户分配了 IP地 址。 具体网络为用户分配 IP地址的方法可以参考上述实施例 2步骤 7所述的方 法。
步骤 2: 网关( GGSN/PGW )将所述用户的 IP地址通知给所述第一网元。 所述通知消息中携带用户的 IP地址和用户的信息(用户的标识或用户名)。 所 述第一网元保存用户的信息(用户的标识或用户名 )和用户的 IP地址之间的绑 定关系。
步骤 3: 应用服务器(例如: MTC Server )向所述第一网元请求用户的 IP 地址。应用服务器向所述第一网元发送 IP地址获取的消息,所述 IP地址获取消 息中携带用户的标识或用户名。 所述第一网元查询存储的用户的标识或用户名 与用户的 IP地址之间的绑定关系, 将用户的 IP地址发送给应用服务器。 图 8为本发明实施例七、 八、 九提供的获取用户 IP地址的网络实体 80 的结构示意图, 包括接收单元 801, 第一获知单元 802, 发送单元 803, 或 者还可以包括第二获知单元 804
A ): 实施例七
接收单元 801接收第二网元发送的获取用户 IP地址的消息; 第一获知单 元 802根据所述获取用户 IP地址的消息获知所述用户的标识; 发送单元 803 将所述用户的标识发送给网关; 接收单元 801接收网关发送的所述用户的 IP 地址; 发送单元 803将所述用户的 IP地址发送给所述第二网元。
第一获知单元 802才艮据所述获取用户 IP地址的消息获知所述用户的标识 具体包括: 所述第一获知单元 802从所述获取用户 IP地址的消息中获得用户 的标识; 或者所述获取用户设备 IP地址的消息中携带用户名, 所述第一获知 单元 802根据所述用户名查询存储信息获得用户的标识。
还包括第二获知单元 804, 所述第二获知单元 804根据用户名或者用户
的标识获知服务用户的移动性管理网元的信息, 所述发送单元 803将服务用 户的移动性管理网元的信息发送给网关; 或者第二获知单元 804根据用户名 或者用户的标识获知用户的位置信息, 所述发送单元 803将用户的位置信息 发送给网关。
B ): 实施例八
接收单元 801接收第二网元发送的获取用户 IP地址的消息; 第一获知单 元 802根据所述获取用户 IP地址的消息获取所述用户的标识, 第二获知单元 804获知服务用户的移动性管理网元; 发送单元 803将所述用户的标识发送 给所述服务用户的移动性管理网元, 通过服务用户的移动性管理网元通知用 户建立连接; 接收单元 801接收网关发送的网络在连接建立流程为所述用户 设备分配的 IP地址; 发送单元 803将所述用户设备的 IP地址发送给所述第 二网元。
第一获知根据所述获取用户 IP 地址的消息获知所述用户的标识具体包 括: 所述第一获知从所述获取用户 IP地址的消息中获得用户的标识; 或者所 述获取用户设备 IP地址的消息中携带用户名, 所述第一获知才艮据所述用户名 查询存储信息获得用户的标识。
第二获知单元 804获知服务用户的移动性管理网元具体包括: 第二获知 单元 804根据用户名或者用户的标识查询存储信息获得服务用户的移动性管 理网元的信息; 或者第二获知单元 804才艮据用户的标识查询 HSS/HLR获得 服务用户的移动性管理网元的信息; 或者第二获知单元 804根据用户名或者 用户的标识查询存储信息获得用户的位置信息, 并根据获得的用户的位置信 息向 务器查询获得 务用户的移动性管理网元的信息。
C ): 实施例八
接收单元 801接收网关发送的通知消息, 所述通知消息中包含网络在连 接建立流程中为用户分配的 IP地址;接收单元 801接收第二网元发送的获取 用户 IP地址的消息; 第一获知单元 802获取 IP地址; 发送单元 803将 IP地
址发送给所述第二网元。
当所述通知消息还进一步包括用户的标识或用户名, 所述获取用户 IP地 址的消息中还携带用户名或用户标识时,第一获取单元获取 IP地址具体包括: 第一获取单元根据获取用户 IP地址的消息中携带的用户名或用户标识查询获 得所述 IP地址。 图 9 为本发明实施例十提供的获取用户 IP地址的网络实体的结构示意 图, 第二网元 901, 第一网元 902, 网关 903, 移动性管理实体 904。 其各个 网元的功能与相互之间的流程交互可以参考上述的方法实施例以及装置实施 例, 在此不再重复。 本领域普通技术人员可以理解: 实现上述方法实施例的全部或部分步骤 可以通过程序指令相关的硬件来完成, 前述的程序可以存储于一计算机可读 取存储介质中, 该程序在执行时, 执行包括上述方法实施例的步骤; 而前述 的存储介质包括: ROM、 RAM , 磁碟或者光盘等各种可以存储程序代码的介 质。
最后应说明的是: 以上实施例仅用以说明本发明的技术方案, 而非对其 限制; 尽管参照前述实施例对本发明进行了详细的说明, 本领域的普通技术 人员应当理解: 其依然可以对前述各实施例所记载的技术方案进行修改, 或 者对其中部分技术特征进行等同替换; 而这些修改或者替换, 并不使相应技 术方案的本质脱离本发明各实施例技术方案的精神和范围。
Claims
1、 一种获取用户的 IP地址的方法, 其特征在于,
第一网元接收第二网元发送的获取用户 I P地址的消息;
第一网元才艮据所述获取用户 IP地址的消息获知所述用户的标识, 将所述 用户的标识发送给网关;
第一网元接收网关发送的所述用户的 IP地址,并将所述用户的 IP地址发 送给所述第二网元。
2、 根据权利要求 1所述的方法, 其特征在于, 所述第一网元根据所述获 取用户 IP地址的消息获取所述用户的标识包括:
所述获取用户 IP地址的消息中携带用户的标识, 所述第一网元从所述获 取用户 IP地址的消息中获得用户的标识; 或者
所述获取用户设备 IP地址的消息中携带用户名, 所述第一网元根据用户 名查询存储信息获得用户的标识。
3、 根据权利要求 1或 2所述的方法, 其特征在于, 将所述用户设备的用 户的标识发送给网关之后, 第一网元收网关发送的网络为所述用户分配的 IP 地址之前还包括:
网关获知服务用户的移动性管理网元;
通过所述移动性管理网元通知用户建立连接;
所述网关获取在连接建立过程中网络为所述用户设备分配的 IP地址。
4、 根据权利要求 3所述的方法, 其特征在于, 网关获知服务用户的移动 性管理网元具体为:
所述第一网元获知服务用户的移动性管理网元的信息, 将服务用户的移 动性管理网元的信息发送给网关; 或者,
所述第一网元获知用户的位置信息, 将用户的位置信息发送给网关, 网 关根据所述的用户的位置信息查询服务器获知服务所述用户的移动性管理网 it; 或者 网关根据第一网元发送的用户的标识向 HSS/HLR 查询获得服务用户的 移动性管理网元的信息。
5、 根据权利要求 4所述的方法, 其特征在于, 所述第一网元获知服务用 户的移动性管理网元的信息具体为:
根据用户名或者用户的标识查询存储信息或者根据用户的标识查询
HSS/HLR获得服务用户的移动性管理网元的信息。
6、 根据权利要求 4所述的方法, 其特征在于, 所述第一网元获知用户的 位置信息具体为: 根据用户名或者用户的标识查询存储信息获得用户的位置 信息。
7、 如权利要求 4或 5所述的方法, 所述服务用户的移动性管理网元的信 息为服务用户的 SGSN/MME的地址或 SGSN/MME的域名。
8、如权利要求 4或 6所述的方法,所述位置信息为用户所在的小区信息, 或跟踪区信息, 或路由区信息, 或跟踪区列表信息, 或接入网标识。
9、 一种获取用户的 IP地址的方法, 其特征在于,
第一网元接收第二网元发送的获取用户 I P地址的消息;
第一网元根据所述获取用户 IP地址的消息获取所述用户的标识, 获知服 务用户的移动性管理网元;
将所述用户的标识发送给所述服务用户的移动性管理网元, 通过服务用 户的移动性管理网元通知用户建立连接;
第一网元接收网关发送的网络在连接建立流程为所述用户设备分配的 IP 地址, 并将所述用户设备的 IP地址发送给所述第二网元。
10、 根据权利要求 9所述的方法, 其特征在于, 所述第一网元根据所述 获取用户 IP地址的消息获取所述用户的标识包括:
所述获取用户 IP地址的消息中携带用户的标识, 所述第一网元从所述获 取用户 IP地址的消息中获得用户的标识; 或者 所述获取用户设备 IP地址的消息中携带用户名, 所述第一网元根据用户 名查询存储信息获得用户的标识。
11、 根据权利要求 9或 10所述的方法, 其特征在于, 所述第一网元获知 服务用户的移动性管理网元具体为:
第一网元根据用户名或者用户的标识查询存储信息获得服务用户的移动 性管理网元的信息; 或者
第一网元根据用户的标识查询 HSS/HLR获得服务用户的移动性管理网 元的信息; 或者
所述第一网元根据用户名或者用户的标识查询存储信息获得用户的位置 信息, 并根据获得的用户的位置信息向服务器查询获得服务用户的移动性管 理网元的信息。
12、 如权利要求 11所述的方法, 所述服务用户的移动性管理网元的信息 为服务用户的 SGSN/MME的地址或 SGSN/MME的域名,
13、 如权利要求 11所述的方法, 所述位置信息为用户所在的小区信息, 或跟踪区信息, 或路由区信息, 或跟踪区列表信息, 或接入网标识。
14、 一种获取用户的 IP地址的方法, 其特征在于,
第一网元接收网关发送的通知消息, 所述通知消息中包含网络在连接建 立流程中为用户分配的 IP地址;
第一网元接收第二网元发送的获取用户 IP地址的消息;
第一网元将所述 IP地址发送给所述第二网元。
15、 如权利要求 14所述的方法, 其特征在于, 当所述通知消息中包含用 户的标识或用户名, 所述获取用户 IP地址的消息中还携带用户名或用户标识 时, 第一网元将所述 IP地址发送给所述第二网元之前还包括: 第一网元根据 获取用户 IP地址的消息中携带的用户名或用户标识查询获得所述 IP地址。
16、一种用于获取用户 IP地址的网络实体,其特征在于, 包括接收单元, 第一获知单元和发送单元, 其中
接收单元接收第二网元发送的获取用户 IP地址的消息; 第一获知单元根 据所述获取用户 IP地址的消息获知所述用户的标识; 发送单元将所述用户的 标识发送给网关; 接收单元接收网关发送的所述用户的 IP地址; 发送单元将 所述用户的 IP地址发送给所述第二网元。
17、 如权利要求 16所述的网络实体, 其特征在于, 第一获知单元根据所 述获取用户 IP地址的消息获知所述用户的标识具体包括:
所述第一获知单元从所述获取用户 IP地址的消息中获得用户的标识; 或 者所述获取用户设备 IP地址的消息中携带用户名, 所述第一获知单元根据所 述用户名查询存储信息获得用户的标识。
18、 如权利要求 16或 17所述的网络实体, 其特征在于: 还包括第二获 知单元, 所述第二获知单元根据用户名或者用户的标识获知服务用户的移动 性管理网元的信息, 所述发送单元将服务用户的移动性管理网元的信息发送 给网关; 或者第二获知单元根据用户名或者用户的标识获知用户的位置信息, 所述发送单元将用户的位置信息发送给网关。
19、一种用于获取用户 IP地址的网络实体,其特征在于, 包括接收单元, 第一获知单元, 第二获知单元和发送单元, 其中
接收单元接收第二网元发送的获取用户 IP地址的消息; 第一获知单元根 据所述获取用户 IP地址的消息获取所述用户的标识, 第二获知单元获知服务 移动性管理网元, 通过服务用户的移动性管理网元通知用户建立连接; 接收 单元接收网关发送的网络在连接建立流程为所述用户设备分配的 IP地址; 发 送单元将所述用户设备的 IP地址发送给所述第二网元。
20、 如权利要求 19所述的网络实体, 其特征在于, 第一获知根据所述获 取用户 IP地址的消息获知所述用户的标识具体包括:
所述第一获知从所述获取用户 IP地址的消息中获得用户的标识; 或者所 述获取用户设备 IP地址的消息中携带用户名, 所述第一获知才艮据所述用户名 查询存储信息获得用户的标识。
21、 根据权利要求 19或 20所述的网络实体, 其特征在于, 第二获知单 元获知服务用户的移动性管理网元具体包括:
第二获知单元根据用户名或者用户的标识查询存储信息获得服务用户的 移动性管理网元的信息; 或者
第二获知单元根据用户的标识查询 HSS/HLR 获得服务用户的移动性管 理网元的信息; 或者
第二获知单元根据用户名或者用户的标识查询存储信息获得用户的位置 信息, 并根据获得的用户的位置信息向服务器查询获得服务用户的移动性管 理网元的信息。
22、 一种用于获取用户 IP地址的网络实体, 其特征在于, 包括第一获取 单元, 接收单元, 发送单元, 其中
接收单元接收网关发送的通知消息, 所述通知消息中包含网络在连接建 立流程中为用户分配的 IP地址;
接收单元接收第二网元发送的获取用户 IP地址的消息;
第一获取单元获取 IP地址;
发送单元将 IP地址发送给所述第二网元。
23、 如权利要求 22所述的网络实体, 其特征在于, 当所述通知消息还进 一步包括用户的标识或用户名, 所述获取用户 IP地址的消息中还携带用户名 或用户标识时, 第一获取单元获取 IP地址具体包括: 第一获取单元根据获取 用户 IP地址的消息中携带的用户名或用户标识查询获得所述 IP地址。
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2010/078766 WO2012065298A1 (zh) | 2010-11-16 | 2010-11-16 | 获取用户ip地址的方法和网络实体 |
CN201080004998.2A CN102742323B (zh) | 2010-11-16 | 2010-11-16 | 获取用户ip地址的方法和网络实体 |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2010/078766 WO2012065298A1 (zh) | 2010-11-16 | 2010-11-16 | 获取用户ip地址的方法和网络实体 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2012065298A1 true WO2012065298A1 (zh) | 2012-05-24 |
Family
ID=46083478
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2010/078766 WO2012065298A1 (zh) | 2010-11-16 | 2010-11-16 | 获取用户ip地址的方法和网络实体 |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN102742323B (zh) |
WO (1) | WO2012065298A1 (zh) |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN111065135B (zh) * | 2019-11-29 | 2021-11-12 | 北京长焜科技有限公司 | 一种3g网关到4g网关的切换方法 |
CN111511044B (zh) * | 2020-04-16 | 2023-05-05 | 蓓安科仪(北京)技术有限公司 | 基于5g网络实现远程医疗的数据通信方法 |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2009294922A (ja) * | 2008-06-05 | 2009-12-17 | Nippon Telegr & Teleph Corp <Ntt> | ゲートウェイ装置及びゲートウェイ制御プログラム |
CN101674665A (zh) * | 2009-10-22 | 2010-03-17 | 华为技术有限公司 | 一种无线传输接口建立方法和无线传输网元 |
CN101754305A (zh) * | 2008-12-04 | 2010-06-23 | 华为技术有限公司 | 实现数据网关切换的方法、装置和*** |
Family Cites Families (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
GB2366705B (en) * | 2000-08-29 | 2004-07-14 | Motorola Inc | Communications system, communications unit and method of operation |
CN1835475A (zh) * | 2005-03-14 | 2006-09-20 | 华为技术有限公司 | 通用分组无线业务网络侧激活的方法 |
CN101388828B (zh) * | 2007-09-10 | 2011-07-13 | 电信科学技术研究院 | 演进分组交换***承载激活的方法及装置 |
-
2010
- 2010-11-16 CN CN201080004998.2A patent/CN102742323B/zh active Active
- 2010-11-16 WO PCT/CN2010/078766 patent/WO2012065298A1/zh active Application Filing
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2009294922A (ja) * | 2008-06-05 | 2009-12-17 | Nippon Telegr & Teleph Corp <Ntt> | ゲートウェイ装置及びゲートウェイ制御プログラム |
CN101754305A (zh) * | 2008-12-04 | 2010-06-23 | 华为技术有限公司 | 实现数据网关切换的方法、装置和*** |
CN101674665A (zh) * | 2009-10-22 | 2010-03-17 | 华为技术有限公司 | 一种无线传输接口建立方法和无线传输网元 |
Also Published As
Publication number | Publication date |
---|---|
CN102742323B (zh) | 2014-12-24 |
CN102742323A (zh) | 2012-10-17 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN102668489B (zh) | 获取用户的ip地址的方法和网络实体 | |
EP2448297B1 (en) | Information processing method and system, and mobility management network element | |
WO2011140884A1 (zh) | Mtc组选择分组数据网网关的方法及移动性管理网元 | |
US11910292B2 (en) | Support of user plane transactions over a mobile network | |
US8855045B2 (en) | Method and system for controlling establishment of local IP access | |
US20180199277A1 (en) | Network selection method and base station | |
US20110182244A1 (en) | Method for supporting context management by home node-b | |
WO2011054299A1 (zh) | 机器类通讯终端信息的获取方法和*** | |
WO2010121495A1 (zh) | 一种ip地址分配方法及*** | |
WO2015062098A1 (zh) | 一种网络选择方法及核心网设备 | |
KR20130135912A (ko) | 네트워크 애플리케이션 서버로부터 사용자 장비(ue) 애플리케이션 트리거 요청을 이동 네트워크를 통해 ue에 통지 | |
EP2803209B1 (en) | Machine-type communication proxy function | |
WO2012094957A1 (zh) | 一种对mtc终端进行移动性管理的方法和*** | |
CN102413453B (zh) | 一种mtc设备用户号码的共享方法和*** | |
WO2010072149A1 (zh) | 实现用户设备切换的方法、装置及*** | |
WO2013047200A1 (ja) | 通信システム、通信方法及び通信プログラム | |
WO2011134336A1 (zh) | 机器类通信事件上报方法、装置及*** | |
CN101867986B (zh) | 一种csfb功能的激活方法及*** | |
WO2012130098A1 (zh) | 一种获取机器类型通信设备ip地址的方法及*** | |
WO2011020435A1 (zh) | M2m应用服务器下发数据包的方法及*** | |
Kunz et al. | Machine type communications in 3GPP: From release 10 to release 12 | |
WO2011050688A1 (zh) | 机器类通讯终端信息的获取方法和*** | |
WO2011134370A1 (zh) | 机器类通信事件上报方法及*** | |
EP2999244B1 (en) | Data transmission method and gateway | |
WO2013013622A1 (zh) | 获取目的ip地址的方法及装置 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 201080004998.2 Country of ref document: CN |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 10859790 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 10859790 Country of ref document: EP Kind code of ref document: A1 |