CN108064039B

CN108064039B - Method, device and computer storage medium for acquiring IP address

Info

Publication number: CN108064039B
Application number: CN201810143115.4A
Authority: CN
Inventors: 陈璇; 童磊; 赵雨田; 葛瑾
Original assignee: China United Network Communications Group Co Ltd
Current assignee: China United Network Communications Group Co Ltd
Priority date: 2018-02-11
Filing date: 2018-02-11
Publication date: 2021-05-25
Anticipated expiration: 2038-02-11
Also published as: CN108064039A

Abstract

The application discloses a method and a device for acquiring an IP address and a computer storage medium, relates to the technical field of communication, and is used for enabling a target mobility management network element to successfully acquire the network type of a network which is accessed by a terminal last time. The method comprises the following steps: a terminal acquires a network type of a first network, wherein the first network is a network accessed by the terminal; if the terminal moves from the management range of the first mobility management network element to the management range of the second mobility management network element, the terminal sends the network type of the first network to the second mobility management network element, the network type is used for the second mobility management network element to obtain the IP address of the first mobility management network element, and the first mobility management network element is a mobility management network element in the first network.

Description

Method, device and computer storage medium for acquiring IP address

Technical Field

The present application relates to the field of communications technologies, and in particular, to a method and an apparatus for acquiring an Internet Protocol (IP) address, and a computer storage medium.

Background

In the process of terminal movement, the process of terminal switching the mobility management network element of service can be involved. If the mobility management network element serving the terminal before the handover decision is called a source mobility management network element, the mobility management network element deciding the handover is called a target mobility management network element. In the handover process, in order to perform network registration on the network to which the target mobility management network element belongs, the terminal needs to acquire data such as an International Mobile Subscriber Identity (IMSI) and authentication of the terminal in the source mobility management network element. Therefore, the target mobility management network element needs to acquire the network type of the network that the terminal has accessed last time, perform Domain Name System (DNS) query according to the network type of the network that the terminal has accessed last time to acquire the IP address of the source mobility management network element, and further acquire data such as IMSI and authentication of the terminal according to the IP address.

Currently, some mobility management network elements may obtain a network type of a network that the terminal has previously accessed through a Location Area Identity (LAI)/a Mobility Management Entity Group Identity (MMEGI) configured in the terminal or a globally unique temporary user equipment identity (GUTI) reported by the terminal. However, not all mobility management network elements can obtain the network type of the network to which the terminal has been previously accessed through LAI, MMEGI, or GUTI, so that some target mobility management network elements cannot obtain the network type of the network to which the terminal has been previously accessed, and the terminal fails to register on the network to which the target mobility management network element belongs.

Disclosure of Invention

The embodiment of the application provides a method and a device for acquiring an IP address and a computer storage medium, which are used for enabling a target mobility management network element to successfully acquire the network type of a network accessed by a terminal last time.

In a first aspect, a method for acquiring an IP address is provided, including: a terminal acquires a network type of a first network, wherein the first network is a network accessed by the terminal; if the terminal moves from the management range of the first mobility management network element to the management range of the second mobility management network element, the terminal sends the network type of the first network to the second mobility management network element, the network type is used for the second mobility management network element to obtain the IP address of the first mobility management network element, and the first mobility management network element is a mobility management network element in the first network.

A possible implementation manner is that a terminal acquires a network type of a first network, and includes: the terminal receives the network type identification of the first network from the first mobility management network element, and acquires the network type of the first network according to the network type identification.

A possible implementation manner that a terminal sends a network type of a first network to a second mobility management network element includes: and the terminal sends a request message to the second mobility management network element, wherein the request message comprises a historical network type field, and the historical network type field is used for indicating the network type of the first network.

In a second aspect, a method for acquiring an IP address is provided, including: the second mobility management network element receives the network type of a first network from the terminal, the first network is a network which is accessed by the terminal before the terminal moves from the management range of the first mobility management network element to the management range of the second mobility management network element, and the first mobility management network element is a mobility management network element in the first network; the second mobility management network element constructs an FQDN according to the network type of the first network; and the second mobility management network element queries the DNS according to the FQDN to obtain the IP address of the first mobility management network element.

One possible implementation manner in which the second mobility management network element receives the network type of the first network from the terminal includes: the second mobility management network element receives a request message from the terminal, wherein the request message comprises a historical network type field, and the historical network type field is used for indicating the network type of the first network; and the second mobility management network element determines the network type of the first network according to the historical network type field.

In a third aspect, an apparatus for acquiring an IP address is provided, including: a processing unit and a communication unit; a processing unit, configured to acquire a network type of a first network, where the first network is a network to which a device accesses; if the device moves from the management range of the first mobility management network element to the management range of the second mobility management network element, the communication unit is configured to send the network type of the first network to the second mobility management network element, and the communication unit is configured to obtain the IP address of the first mobility management network element by the second mobility management network element, where the first mobility management network element is a mobility management network element in the first network.

In one possible implementation, the processing unit is specifically configured to: and receiving the network type identifier of the first network from the first mobility management network element through the communication unit, and acquiring the network type of the first network according to the network type identifier.

In one possible implementation, the communication unit is further configured to: and sending a request message to a second mobility management network element, wherein the request message comprises a historical network type field, and the historical network type field is used for indicating the network type of the first network.

In a fourth aspect, an apparatus for acquiring an IP address is provided, including: a communication unit and a processing unit; a communication unit, configured to receive a network type of a first network from a terminal, where the first network is a network to which the terminal accesses before the terminal moves from a management range of a first mobility management network element to a management range of a device, and the first mobility management network element is a mobility management network element in the first network; the processing unit is used for constructing a fully qualified domain name FQDN according to the network type of the first network; and the processing unit is also used for inquiring a Domain Name System (DNS) according to the FQDN to obtain the IP address of the first mobility management network element.

In a possible implementation manner, the communication unit is specifically configured to receive a request message from the terminal, where the request message includes a historical network type field, and the historical network type field is used to indicate a network type of the first network; and the processing unit is also used for determining the network type of the first network according to the historical network type field.

In a fifth aspect, a computer storage medium is provided that comprises instructions for performing any one of the methods provided by the first or second aspects.

In the method, the apparatus, and the computer storage medium provided in the foregoing aspects, the terminal acquires the network type of the first network and reports the network type of the first network to the second mobility management network element, so that the second mobility management network element can directly determine the network type of the first network. The method does not depend on LAI, MMEGI or GUTI, and can be applied to all mobility management network elements by only carrying out simple configuration and enabling two communication parties to identify the network types by adopting the same rule, so that the terminal can be successfully registered on the network to which the second mobility management network element belongs, the registration success rate of the user is improved, and the situation of short network disconnection of the terminal is prevented. Compared with the existing mode of constructing the FQDN for DNS query, the method can avoid secondary query, reduce the signaling overhead of DNS query and improve the DNS query efficiency.

Drawings

Fig. 1 is a schematic view of an application scenario provided in an embodiment of the present application;

fig. 2 is a flowchart of a method for acquiring an IP address according to an embodiment of the present disclosure;

fig. 3 is a flowchart of another method for acquiring an IP address according to an embodiment of the present disclosure;

fig. 4 is a flowchart of another method for acquiring an IP address according to an embodiment of the present application;

fig. 5 is a schematic diagram illustrating a device for acquiring an IP address according to an embodiment of the present disclosure;

fig. 6 is a schematic diagram illustrating a composition of another apparatus for acquiring an IP address according to an embodiment of the present application;

fig. 7 is a schematic diagram illustrating a configuration of another apparatus for acquiring an IP address according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application. Where in the description of the present application, "/" indicates an OR meaning, for example, A/B may indicate A or B; "and/or" herein is merely an association describing an associated object, and means that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, in the description of the present application, "a plurality" means two or more than two.

In this embodiment, the 2G network may be a General Packet Radio Service (GPRS) system, the 3G network may be a Universal Mobile Telecommunications System (UMTS) and a Wideband Code Division Multiple Access (WCDMA) system, the 4G network may be an Evolved Packet Core (EPC) network, and the 5G network may be a New Radio (NR) system.

Currently, the method for acquiring the network type of the network that the terminal previously accessed may be:

in a first way,

When the terminal moves to the 2/3G network, because the network types of the networks that the terminal accessed last time are different, and the high-order of the LAI configured in the terminal is different, the mobility management network element in the 2/3G network can determine the network type of the network that the terminal accessed last time according to the high-order of the LAI configured in the terminal.

When the terminal moves to the 4G network, because the network types of the networks that the terminal previously accessed are different, the high-order of the MMEGI configured in the terminal is different, so the mobility management network element in the 4G network can determine the network type of the network that the terminal previously accessed according to the high-order of the MMEGI configured in the terminal.

The second way,

The terminal reports Old packet temporary mobile subscriber identity (Old P-TMSI Signature for short) or Additional GUTI or GUTI Type fields to the target mobility management network element, marks whether the existing GUTI is native or mapped (the native GUTI is logged in the 4G network last time, and the mapped GUTI is logged in the 2/3G network last time), so that the target mobility management network element determines the network Type of the network which the terminal previously accesses according to the GUTI.

In the first and second modes, different areas may have different modes for configuring LAI and MMEGI, and not all terminals support reporting of GUTI, and not all mobility management network elements support obtaining the network type of the network to which the terminal has previously accessed through LAI, MMEGI or GUTI, so that some target mobility management network elements cannot obtain the network type of the network to which the terminal has previously accessed, and further, the terminal fails to register on the network to which the target mobility management network element belongs. At this time, the terminal may be temporarily disconnected.

It should be noted that, when the target mobility management element cannot determine the network type of the network to which the terminal has previously accessed, the target mobility management element may first construct a Fully Qualified Domain Name (FQDN) of one network type for DNS query, and if the query fails, then construct an FQDN of another network type for DNS query, so that secondary query is sometimes required, and DNS query efficiency is reduced.

In order to solve the above problem, an embodiment of the present application provides a method for acquiring an IP address, where a target mobility management network element acquires a network type of a network to which a terminal has previously accessed through a terminal by recording and reporting the network type, so as to construct a corresponding FQDN, obtain an IP address of a source mobility management network element through one-time query, improve DNS query efficiency, and improve a success rate of network registration. Meanwhile, the phenomenon of network disconnection in the terminal moving process is reduced, and user perception is improved. The methods provided in the examples of the present application are described in detail below.

The method provided by the embodiment of the present application may be applied to a scenario in which a terminal moves, for example, referring to fig. 1, if the terminal moves from a management range of a first mobility management network element to a management range of a second mobility management network element, the following method may be executed.

An embodiment of the present application provides a method for acquiring an IP address, as shown in fig. 2, the method includes:

201. the terminal acquires the network type of a first network, wherein the first network is a network accessed by the terminal.

The network type of the network may be a 2G network, a 3G network, a 4G network, or a 5G network.

Optionally, when implemented specifically, step 201 may include: and the terminal receives the network type identifier of the first network from the first mobility management network element and acquires the network type of the first network according to the network type identifier. The network type identifier is used to indicate the network type.

When the terminal performs network attachment again in the first network, if the first mobility management network element agrees to perform the attachment of the terminal, an attachment acceptance response is sent to the terminal, and the network type identifier of the first network is carried in the attachment acceptance response. When a terminal performs Routing Area Update (RAU) in a first network, if a first mobility management network element agrees to perform RAU for the terminal, sending an RAU acceptance response to the terminal, and carrying a network type identifier of the first network in the RAU acceptance response. When a terminal performs tracking area update (TAU for short) in a first network, if a first mobility management network element agrees to perform TAU on the terminal, a TAU accept response is sent to the terminal, and the TAU accept response carries a network type identifier of the first network.

The network type identifier may be any identifier that can be recognized by the terminal, for example, the network type identifier may be a value of two bits (bits), if the network type represented by the two bits is a 4G network when the two bits are 11, the terminal may determine that the network type is the 4G network according to the identifier, and if the network type represented by the two bits is a 3G network when the two bits are 10, the terminal may determine that the network type is the 3G network according to the identifier.

202. And if the terminal moves from the management range of the first mobility management network element to the management range of the second mobility management network element, the terminal sends the network type of the first network to the second mobility management network element. Accordingly, the second mobility management network element receives the network type of the first network from the terminal.

Wherein the first mobility management network element is a mobility management network element in the first network (i.e. the source mobility management network element in the foregoing). The second mobility management network element may be a mobility management network element in the second network (i.e. the target mobility management network element above). The second network may be a 2G network, a 3G network, a 4G network, or a 5G network. The first network and the second network may be the same or different, and this is not particularly limited in this embodiment of the application.

If the network type of the network is a 2G/3G network, the mobility management network element in the network is a serving general packet radio service support node (SGSN), and if the network type of the network is a 4G network, the mobility management network element in the network is a Mobility Management Entity (MME).

In this embodiment, the terminal may be an idle terminal, and in this case, when the terminal moves from the management range of the first mobility management element to the management range of the second mobility management element, the terminal may need to perform network attachment, RAU, or TAU again. Specifically, the terminal will generate an RAU when moving across a Routing Area (RA), at this time, the second network may be a 4G network, the terminal will generate a TAU when moving across a Tracking Area (TA), at this time, the second network may be a 2G/3G network; when the terminal is powered on or logs on to the network for the first time, the terminal may need to re-attach to the network. Optionally, the process of determining, by the second mobility management network element, the network type of the first network may include: 11) the terminal sends a request message to the second mobility management network element, wherein the request message comprises a historical network type field, and the historical network type field is used for indicating the network type of the first network. Correspondingly, the second mobility management network element receives a request message from the terminal. 12) And the second mobility management network element determines the network type of the first network according to the historical network type field.

When the terminal performs network attachment again in the second network, the terminal may send an attachment request to the second mobility management network element through the access network, where the attachment request may include information of the network type of the first network. When the terminal performs RAU in the second network, the terminal may send an RAU request to the second mobility management network element through the access network, where the RAU request may include information of the network type of the first network. When the terminal performs TAU in the second network, the terminal may send a TAU request to the second mobility management network element through the access network, where the TAU request may include information of the network type of the first network.

Specifically, the request message carrying the information of the network TYPE of the first network may include a historical network TYPE field (hereinafter referred to as "OLD RAT TYPE field"). The terminal may add a bit value representing the network TYPE to the field after determining the network TYPE of the first network, and the second mobility management network element may determine the network TYPE of the first network according to the value of the OLD RAT TYPE field in the request message.

For example, if the network TYPE is a 2G network, the value of the OLD RAT TYPE field may be 001, if the network TYPE is a 3G network, the value of the OLD RAT TYPE field may be 010, and if the network TYPE is a 4G network, the value of the OLD RAT TYPE field may be 011.

203. And the second mobility management network element constructs the FQDN according to the network type of the first network.

It should be noted that, if the network type of the first network is a 2G/3G network, the first mobility management network element may manage multiple RAs, where the multiple RAs may belong to one or more Location Areas (LAs), an FQDN constructed according to the network type of the first network may be referred to as a Routing Area Code (RAC) FQDN, and the RAC FQDN includes a Location Area Code (LAC) and RAC information where the terminal is located in the first network. If the network type of the first network is a 4G network, the FQDN constructed according to the network type of the first network may be referred to as MME FQDN, and the MME FQDN includes information of an MMEGI and an MMEC (MME code, i.e., MME identifier) where the terminal is located in the first network.

204. And the second mobility management network element queries the DNS according to the FQDN to obtain the IP address of the first mobility management network element.

Specifically, step 204 may be implemented by: and the second mobility management network element sends the FQDN to the DNS, and the DNS queries the IP address of the first mobility management network element according to the FQDN.

If the network type of the first network is a 2G/3G network, the DNS can search according to LAC and RAC information included in RAC FQDN to obtain the IP address of the first mobility management network element. Illustratively, if SGSN1 manages LAC1 (i.e., LA identified as 1) and LAC2 (i.e., LA identified as 2), SGSN2 manages LAC3 (i.e., LA identified as 3) and LAC4 (i.e., LA identified as 4). LAC1 includes RAC1 (i.e., RA identified as 1) and RAC2 (i.e., RA identified as 2), LAC2 includes RAC1, LAC3 includes RAC1 and RAC2, and LAC4 includes RAC 1. It should be noted that RAC1 included in LAC1, LAC2, LAC3, and LAC4 are not the same RAC, but are identified identically, and RAC2 has the same meaning, that is, the RACs in any two LACs may be independent. Therefore, when the area where the terminal is located is determined, the area must be determined by both LAC and RAC. Referring to table 1, if the IP address of the SGSN1 is IP address 1, the IP address of the SGSN2 is IP address 2, and the LAC and RAC information included in the RAC FQDN are LAC2 and RAC1, respectively, the DNS may determine that the IP address of the first mobility management network element is IP address 1 according to table 1.

TABLE 1

If the network type of the first network is a 4G network, the DNS can search according to the MMEGI and MMEC information included in the MME FQDN to obtain the IP address of the first mobility management network element. Illustratively, if a 4G network includes MMEGI1 (i.e., an MMEG identified as 1) and MMEGI2 (i.e., an MMEG identified as 2). MMEGI1 includes MMEC1 (i.e., MME identified as 1) and MMEC2 (i.e., MME identified as 2), MMEGI2 includes MMEC1, MMEC2, and MMEC3 (i.e., MME identified as 3). It should be noted that MMEC1 included in MMEGI1 and MMEGI2 are not the same MMEC, but are simply identified identically, and MMEC2 has the same meaning, that is, the MMECs in any two MMEGI may be independent. Therefore, when the area where the terminal is located is determined, the area must be determined by MMEGI and MMEC together. Referring to table 2, if the MMEGI and MMEC information included in the MME FQDN are MMEGI2 and MMEC2, respectively, the DNS may determine that the IP address of the first mobility management network element is IP address 4 according to table 2.

TABLE 2

It should be noted that, since the 2G network and the 3G network share the core network device SGSN, the 2G network scenario is the same as the 3G network scenario.

In the method provided by the embodiment of the application, the terminal acquires the network type of the first network and reports the network type of the first network to the second mobility management network element, so that the second mobility management network element can directly determine the network type of the first network. The method does not depend on LAI, MMEGI or GUTI, and can be applied to all mobility management network elements by only carrying out simple configuration and enabling two communication parties to identify the network types by adopting the same rule, so that the terminal can be successfully registered on the network to which the second mobility management network element belongs, the registration success rate of the user is improved, and the situation of short network disconnection of the terminal is prevented. Compared with the existing mode of constructing the FQDN for DNS query, the method can avoid secondary query, reduce the signaling overhead of DNS query and improve the DNS query efficiency.

The above process is described in more detail below by way of example 1 and example 2.

Example 1

In this embodiment, the terminal moves from the management range of the first mobility management network element to the management range of the second mobility management network element, and the second mobility management network element is a mobility management network element in the 3G network. As shown in fig. 3, the method may include:

if the terminal performs network attachment, step 301 is executed, and if the terminal performs RAU, step 302 is executed.

301. And the second SGSN judges whether the terminal carries the IMSI of the terminal.

Wherein the second SGSN is a second mobility management network element.

If not, go to step 302, and if yes, go to step 303.

302. The second SGSN determines whether a packet temporary mobile subscriber identity (P-TMSI) is allocated to the local office.

If yes, go to step 303, otherwise go to step 304.

303. The second SGSN acquires user information.

The user information can be IMSI, P-TMSI, authentication and other data of the terminal.

After step 303, the subsequent flow after acquiring the user information is executed.

304. The second SGSN determines the network type of the first network.

If the network type of the first network is a 2G/3G network, step 305 is performed, and if the network type of the first network is a 4G network, step 306 is performed.

305. And the second SGSN constructs RAC FQDN and carries out DNS query according to the RAC FQDN.

Specifically, the attach request or RAU request message sent by the terminal to the second SGSN may include RA and LA in the network that the terminal was accessed in the previous time, where the RA in the network that the terminal was accessed in the previous time is indicated by OLD (routing area identity, RAI for short), the TA in the network that the terminal was accessed in the previous time is indicated by OLD LAI, and the second SGSN may construct RAC FQDN according to the OLD RAI and the OLD LAI. The second SGSN sends a DNS query request to the DNS, the DNS query request including a RAC FQDN.

It should be noted that, if the network type of the first network is a 2G/3G network, one SGSN may manage multiple LAs, one LA may include multiple RAs, and the terminal may send the LAI and the RAI to the second mobility management network element, so that the second mobility management network element may construct an RAC FQDN.

The format of the RAC FQDN may be: RAC < X1X1X1X1 >. LAC < X2X2X2X 2. mnc X3X3.mcc X4X4.gprs.

306. And the second SGSN constructs an MME FQDN and carries out DNS query according to the MME FQDN.

It should be noted that, if the network type of the first network is a 4G network, the 4G network may include multiple MMEGI, one MMEGI may include multiple MMECs, and the terminal may send the MMEGI and the MMEC to the second mobility management network element, so that the second mobility management network element may construct an MME FQDN, and the format of the MME FQDN may be: mmec < X1X1X1X1 >. mmegi < X2X2X2X 2. mme. epc. mcc. X3X3.mcc X4X4.3gppnetwork. org.

And the SGSN constructs an MME FQDN according to the OLD GUTI field reported in the request message, and specifically constructs the MME FQDN according to the MMEGI and the MMEC in the OLD GUTI field.

307. And the second SGSN acquires the IP address of the first mobility management network element.

308. And the second SGSN acquires the user information according to the IP address of the first mobility management network element.

309. And the second SGSN carries out network registration in the second network according to the user information.

If the registration is successful, the following steps are executed:

310. and the second SGSN sends the network type identification of the second network to the terminal.

311. And the terminal determines the network type of the second network according to the network type identifier of the second network.

Example 2

In this embodiment, the terminal moves from the management range of the first mobility management network element to the management range of the second mobility management network element, where the second mobility management network element is a mobility management network element in a 4G network. As shown in fig. 4, the method may include:

if the terminal performs network attachment, step 401 is executed, and if the terminal performs TAU, step 402 is executed.

401. And the second MME judges whether the terminal carries the IMSI of the terminal.

Wherein the second MME is a second mobility management network element.

If not, go to step 402, and if so, go to step 403.

402. And the MME judges whether the GUTI is distributed for the local office or not.

If yes, go to step 403, otherwise go to step 404.

403. And the second MME acquires the user information.

The user information may be data of IMSI, GUTI, authentication, etc. of the terminal.

After step 403, the subsequent flow after acquiring the user information is executed.

404. The second MME determines a network type of the first network.

If the network type of the first network is a 2G or 3G network, step 405 is executed, and if the network type of the first network is a 4G network, step 406 is executed.

405. And the second MME constructs RAC FQDN and carries out DNS query according to the RAC FQDN.

The process of constructing the RAC FQDN can be found above and will not be described further herein.

406. And the second MME constructs an MME FQDN and carries out DNS query according to the MME FQDN.

The process of constructing the MME FQDN can be referred to above and is not described herein again.

407. And the second MME acquires the IP address of the first mobility management network element.

408. And the second MME acquires the user information according to the IP address of the first mobility management network element.

409. And the second MME performs network registration in the second network according to the user information.

If the registration is successful, the following steps are executed:

410. and the second MME sends the network type identification of the second network to the terminal.

411. And the terminal determines the network type of the second network according to the network type identifier of the second network.

The above description has presented the embodiments of the present application primarily from a method perspective. It is understood that the device for acquiring the IP address includes a hardware structure and/or a software module for performing the above functions. Those of skill in the art would readily appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as hardware or combinations of hardware and computer software. Whether a function is performed as hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

In the embodiment of the present application, the device for acquiring an IP address may perform functional unit division according to the above method example, for example, each functional unit may be divided corresponding to each function, or two or more functions may be integrated into one processing unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit. It should be noted that the division of the unit in the embodiment of the present application is schematic, and is only a logic function division, and there may be another division manner in actual implementation.

The embodiment of the present application further provides an apparatus 50 for acquiring an IP address, referring to fig. 5, including: a processing unit 501 and a communication unit 502;

a processing unit 501, configured to obtain a network type of a first network, where the first network is a network to which a device accesses;

if the apparatus moves from the management range of the first mobility management network element to the management range of the second mobility management network element, the communication unit 502 is configured to send the network type of the first network to the second mobility management network element, and is configured to obtain the IP address of the first mobility management network element by the second mobility management network element, where the first mobility management network element is a mobility management network element in the first network.

Optionally, the processing unit 501 is specifically configured to: the network type identifier of the first network is received from the first mobility management network element through the communication unit 502, and the network type of the first network is obtained according to the network type identifier.

Optionally, the communication unit 502 is further configured to: and sending a request message to a second mobility management network element, wherein the request message comprises a historical network type field, and the historical network type field is used for indicating the network type of the first network.

The units in the apparatus 50 are configured to perform the above method, and therefore, the beneficial effects of the apparatus 50 can be referred to the beneficial effects of the above method, which are not described herein again.

The embodiment of the present application further provides an apparatus 60 for acquiring an IP address, as shown in fig. 6, including: a communication unit 601 and a processing unit 602;

a communication unit 601, configured to receive a network type of a first network from a terminal, where the first network is a network to which the terminal accesses before the terminal moves from a management range of a first mobility management network element to a management range of a device, and the first mobility management network element is a mobility management network element in the first network;

a processing unit 602, configured to construct a fully qualified domain name FQDN according to a network type of a first network;

the processing unit 602 is further configured to query a domain name system DNS according to the FQDN to obtain an IP address of the first mobility management network element.

Optionally, the communication unit 601 is specifically configured to receive a request message from the terminal, where the request message includes a historical network type field, and the historical network type field is used to indicate a network type of the first network;

the processing unit 602 is further configured to determine a network type of the first network according to the historical network type field.

The units in the apparatus 60 are used for executing the above method, and therefore, the beneficial effects of the apparatus 50 can be referred to the beneficial effects of the above method, which are not described herein again.

The processing unit may be a processor or a controller, and may be, for example, a Central Processing Unit (CPU), a general purpose processor, a Digital Signal Processor (DSP), an application-specific integrated circuit (ASIC), a Field Programmable Gate Array (FPGA), other programmable logic devices (programmable gate array), a transistor logic device, a hardware component, or any combination thereof. Which may implement or perform the various illustrative logical blocks, modules, and circuits described in connection with the disclosure. The processor may also be a combination of computing functions, e.g., comprising one or more microprocessors, DSPs, and microprocessors, among others. The communication unit may be a communication interface, a transceiver, a transceiving circuit, etc., wherein the communication interface is a generic term and may comprise one or more interfaces.

When the processing unit is a processor and the communication unit is a communication interface, a schematic composition diagram of the apparatus for acquiring an IP address according to the embodiment of the present application may be shown in fig. 7. Fig. 7 includes a processor 701 and a communication interface 702. Optionally, fig. 7 may further include: a communication bus 703. The processor 701 and the communication interface 702 are connected to each other via a communication bus 703. The communication bus 703 may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The communication bus 703 may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 7, but this is not intended to represent only one bus or type of bus.

When the apparatus 50 for acquiring an IP address is shown in fig. 7, the processor 701 may be configured to perform the actions performed by the processing unit 501 shown in fig. 5, and the communication interface 702 may be configured to perform the actions performed by the communication unit 502 shown in fig. 5. Specifically, the processor 701 is configured to control and manage the actions of the apparatus 50 for acquiring the IP address, for example, the processor 701 is configured to support the apparatus 50 to perform the actions performed by the apparatus 50 as shown in steps 201 and 202 in fig. 2, step 301 and 310 in fig. 3, step 401 and 410 in fig. 4, and other parts described in this embodiment.

When the apparatus 60 for acquiring an IP address is shown in fig. 7, the processor 701 may be configured to perform the actions performed by the processing unit 602 shown in fig. 6, and the communication interface 702 may be configured to perform the actions performed by the communication unit 601 shown in fig. 6. Specifically, the processor 701 is configured to control and manage the actions of the apparatus 60 for acquiring an IP address, for example, the processor 701 is configured to support the apparatus 60 to perform the actions performed by the apparatus 60 described in other parts in the embodiments of the present application, such as steps 203 and 204 in fig. 2, step 311 in fig. 3, step 411 in fig. 4, and so on.

Embodiments of the present application also provide a computer-readable storage medium, which includes instructions that, when executed on a computer, cause the computer to perform the above-mentioned method.

Embodiments of the present application also provide a computer program product containing instructions which, when run on a computer, cause the computer to perform the above method.

The embodiment of the present application further provides an apparatus, which exists in the form of a chip product, and the apparatus includes a processor, a memory, and a transceiver module, where the transceiver module includes an input/output circuit, the memory is used to store computer execution instructions, and the processor implements the method by executing the computer execution instructions stored in the memory.

In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented using a software program, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. The procedures or functions described in accordance with the embodiments of the present application are all or partially generated upon loading and execution of computer program instructions on a computer. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored on a computer readable storage medium or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wire (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)), or wireless (e.g., infrared, wireless, microwave, etc.). Computer-readable storage media can be any available media that can be accessed by a computer or can comprise one or more data storage devices, such as servers, data centers, and the like, that can be integrated with the media. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.

While the present application has been described in connection with various embodiments, other variations to the disclosed embodiments can be understood and effected by those skilled in the art in practicing the claimed application, from a review of the drawings, the disclosure, and the appended claims. In the claims, the word "comprising" does not exclude other elements or steps, and the word "a" or "an" does not exclude a plurality. A single processor or other unit may fulfill the functions of several items recited in the claims. The mere fact that certain measures are recited in mutually different dependent claims does not indicate that a combination of these measures cannot be used to advantage.

Although the present application has been described in conjunction with specific features and embodiments thereof, it will be evident that various modifications and combinations can be made thereto without departing from the spirit and scope of the application. Accordingly, the specification and figures are merely exemplary of the present application as defined in the appended claims and are intended to cover any and all modifications, variations, combinations, or equivalents within the scope of the present application. It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.

Claims

1. A method for obtaining an internet protocol, IP, address, comprising:

a terminal receives a network type identifier of a first network from a first mobility management network element, and acquires the network type of the first network according to the network type identifier, wherein the first network is a network to which the terminal is accessed;

if the terminal moves from the management range of a first mobility management network element to the management range of a second mobility management network element, the terminal sends the network type of the first network to the second mobility management network element, so that the second mobility management network element obtains the IP address of the first mobility management network element, and the first mobility management network element is a mobility management network element in the first network.

2. The method of claim 1, wherein the sending, by the terminal, the network type of the first network to the second mobility management network element comprises:

the terminal sends a request message to the second mobility management network element, wherein the request message comprises a historical network type field, and the historical network type field is used for indicating the network type of the first network.

3. A method for obtaining an internet protocol, IP, address, comprising:

the method comprises the steps that a second mobility management network element receives a network type of a first network from a terminal, the first network is a network accessed by the terminal before the terminal moves from a management range of the first mobility management network element to a management range of the second mobility management network element, and the first mobility management network element is a mobility management network element in the first network;

the second mobility management network element constructs a fully qualified domain name FQDN according to the network type of the first network;

and the second mobility management network element queries a Domain Name System (DNS) according to the FQDN to obtain the IP address of the first mobility management network element.

4. The method of claim 3, wherein the second mobility management network element receiving the network type of the first network from the terminal comprises:

the second mobility management network element receives a request message from the terminal, wherein the request message comprises a historical network type field, and the historical network type field is used for indicating the network type of the first network;

and the second mobility management network element determines the network type of the first network according to the historical network type field.

5. An apparatus for obtaining an internet protocol, IP, address, comprising: a processing unit and a communication unit;

the processing unit is configured to receive, through the communication unit, a network type identifier of a first network from a first mobility management network element, and acquire a network type of the first network according to the network type identifier, where the first network is a network to which the apparatus is accessed;

if the apparatus moves from the management range of a first mobility management network element to the management range of a second mobility management network element, the communication unit is configured to send the network type of the first network to the second mobility management network element, and is configured to obtain the IP address of the first mobility management network element by the second mobility management network element, where the first mobility management network element is a mobility management network element in the first network.

6. The apparatus of claim 5, wherein the communication unit is further configured to:

sending a request message to the second mobility management network element, wherein the request message includes a historical network type field, and the historical network type field is used for indicating the network type of the first network.

7. An apparatus for obtaining an internet protocol, IP, address, comprising: a communication unit and a processing unit;

the communication unit is configured to receive a network type of a first network from a terminal, where the first network is a network to which the terminal accesses before the terminal moves from a management range of a first mobility management network element to a management range of the apparatus, and the first mobility management network element is a mobility management network element in the first network;

the processing unit is used for constructing a fully qualified domain name FQDN according to the network type of the first network;

and the processing unit is further configured to query a Domain Name System (DNS) according to the FQDN to obtain an IP address of the first mobility management network element.

8. The apparatus of claim 7,

the communication unit is specifically configured to receive a request message from the terminal, where the request message includes a historical network type field, and the historical network type field is used to indicate a network type of the first network;

the processing unit is further configured to determine a network type of the first network according to the historical network type field.

9. A computer storage medium characterized by containing a program for executing the method of any one of claims 1 to 4.