[go: up one dir, main page]

WO2012065298A1 - Procédé et entité réseau pour l'acquisition d'une adresse de protocole internet (ip) d'un utilisateur - Google Patents

Procédé et entité réseau pour l'acquisition d'une adresse de protocole internet (ip) d'un utilisateur Download PDF

Info

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
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2010/078766
Other languages
English (en)
Chinese (zh)
Inventor
周汉
吴问付
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to PCT/CN2010/078766 priority Critical patent/WO2012065298A1/fr
Priority to CN201080004998.2A priority patent/CN102742323B/zh
Publication of WO2012065298A1 publication Critical patent/WO2012065298A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

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)

Abstract

L'invention concerne un procédé et une entité réseau pour l'acquisition d'une adresse de protocole Internet (IP) d'un utilisateur. Le procédé consiste en ce que: un premier élément de réseau reçoit un message, envoyé par un second élément réseau, pour acquérir l'adresse IP d'un utilisateur; en fonction du message d'acquisition de l'adresse IP d'un utilisateur, le premier élément de réseau acquiert un identifiant de l'utilisateur et le transmet à une passerelle; le premier élément de réseau reçoit l'adresse IP de l'utilisateur transmise par la passerelle, et la transmet à son tour à l'utilisateur au second élément de réseau. En d'autres termes, le premier élément de réseau acquiert une adresse IP, laquelle est attribuée à un utilisateur par un réseau au cours de l'établissement d'une connexion et transmise par une passerelle, puis l'envoie au second élément de réseau. L'invention permet ainsi de résoudre le problème de l'art antérieur qui empêche le second élément de réseau d'acquérir une adresse IP, du fait qu'une adresse IP statique ne peut être attribuée à un terminal machine à machine (M2M) lorsqu'un côté réseau transmet un service.
PCT/CN2010/078766 2010-11-16 2010-11-16 Procédé et entité réseau pour l'acquisition d'une adresse de protocole internet (ip) d'un utilisateur Ceased WO2012065298A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2010/078766 WO2012065298A1 (fr) 2010-11-16 2010-11-16 Procédé et entité réseau pour l'acquisition d'une adresse de protocole internet (ip) d'un utilisateur
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 (fr) 2010-11-16 2010-11-16 Procédé et entité réseau pour l'acquisition d'une adresse de protocole internet (ip) d'un utilisateur

Publications (1)

Publication Number Publication Date
WO2012065298A1 true WO2012065298A1 (fr) 2012-05-24

Family

ID=46083478

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2010/078766 Ceased WO2012065298A1 (fr) 2010-11-16 2010-11-16 Procédé et entité réseau pour l'acquisition d'une adresse de protocole internet (ip) d'un utilisateur

Country Status (2)

Country Link
CN (1) CN102742323B (fr)
WO (1) WO2012065298A1 (fr)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
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)

* Cited by examiner, † Cited by third party
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)

* Cited by examiner, † Cited by third party
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 电信科学技术研究院 演进分组交换系统承载激活的方法及装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
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
CN102742323A (zh) 2012-10-17
CN102742323B (zh) 2014-12-24

Similar Documents

Publication Publication Date Title
CN102668489B (zh) 获取用户的ip地址的方法和网络实体
US20240306069A1 (en) Support of user plane transactions over a mobile network
CN102244854B (zh) Mtc组选择分组数据网网关的方法及移动性管理网元
EP2448297B1 (fr) Procédé et système de traitement d&#39;informations, et élément réseau de gestion de mobilité
US20110182244A1 (en) Method for supporting context management by home node-b
WO2010121495A1 (fr) Procédé et système d&#39;attribution d&#39;adresse ip
WO2011054299A1 (fr) Procédé et système pour obtenir des informations de terminal de communication de type machine
KR20130135912A (ko) 네트워크 애플리케이션 서버로부터 사용자 장비(ｕｅ) 애플리케이션 트리거 요청을 이동 네트워크를 통해 ｕｅ에 통지
EP2803209B1 (fr) Fonction mandataire pour communication de type machine
WO2012094957A1 (fr) Procédé et système pour effecteur une gestion de mobilité sur un terminal mtc
CN103814622A (zh) 通信系统、通信方法和通信程序
WO2010072149A1 (fr) Procédé, appareil, et système pour réaliser un transfert intercellulaire d&#39;équipement d&#39;utilisateur
WO2011134336A1 (fr) Procédé, dispositif et système de rapport d&#39;événements de communication de type machine
CN103974237B (zh) 移动性管理方法及实体
WO2012130098A1 (fr) Procédé et système conçus pour obtenir l&#39;adresse ip d&#39;un dispositif de communication de type machine (mtc)
WO2011020435A1 (fr) Procédé et système permettant de transmettre des paquets de données au niveau d&#39;un serveur d&#39;application de machine à machine (m2m)
Kunz et al. Machine type communications in 3GPP: From release 10 to release 12
CN107925662B (zh) 用于邻近服务的合法监听的方法和装置
CN102812771A (zh) 用于处理移动终端的通信的服务网关
WO2011134370A1 (fr) Procédé de rapport d&#39;événement de communication de type machine et système associé
EP2999244B1 (fr) Procédé et passerelle de transmission de données
CN102369700B (zh) 业务发起方法及系统、网关设备
CN102318436B (zh) 数据的传输方法、装置及系统
WO2011050723A1 (fr) Procédé, système et dispositif de sélection d&#39;entité de gestion de mobilité (mme) cible durant un processus de commutation de terminal mobile
CN102177757B (zh) 一种实现注册的方法、装置和系统

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