WO2023143412A1

WO2023143412A1 - Ip address assignment method, device, and readable storage medium

Info

Publication number: WO2023143412A1
Application number: PCT/CN2023/073273
Authority: WO
Inventors: 李欢; 谢振华
Original assignee: 维沃移动通信有限公司
Priority date: 2022-01-27
Filing date: 2023-01-20
Publication date: 2023-08-03
Also published as: CN116566949A

Abstract

The present application belongs to the technical field of communication and discloses an IP address assignment method, a device, and a readable storage medium. The method comprises: a first terminal sends a first request message to a first network element, the first request message being used for requesting to assign an IP address to a second terminal; the first terminal receives a first IP address from the first network element, the first IP address being an IP address assigned to the second terminal; and the first terminal sends a second IP address to the second terminal according to the first IP address.

Description

IP address allocation method, device and readable storage medium

Cross References to Related Applications

This application claims priority to Chinese Patent Application No. 202210102833.3 filed in China on January 27, 2022, the entire contents of which are hereby incorporated by reference.

technical field

The application belongs to the field of communication technology, and in particular relates to an Internet Protocol (Internet Protocol, IP) address allocation method, device and readable storage medium.

Background technique

In the prior art, non-3rd Generation Partnership Project (3rd Generation Partnership Project, 3GPP) equipment can perform network communication through 3GPP equipment, for example: a mobile phone can set up a wireless fidelity (Wireless Fidelity, WiFi) hotspot for a notebook, so that the notebook can pass through Mobile Internet. However, the notebook is a non-3GPP device, and the communication network cannot know that the notebook is surfing the Internet, and it is also difficult to identify the business flow of the notebook, so that it cannot perform management operations such as policy control and billing. Therefore, in the scenario of personal IoT and fixed-mobile convergence, how to identify the service flow of non-3GPP devices is an urgent problem to be solved.

Contents of the invention

The embodiment of the present application provides an IP address allocation method, device and readable storage medium, which can solve the problem that the network cannot identify the service flow of the non-3GPP device.

In a first aspect, an IP address assignment method, device, and readable storage medium are provided, the method including:

the first terminal sends a first request message to the first network element, where the first request message is used to request to assign an IP address to the second terminal;

receiving, by the first terminal, a first IP address from the first network element, where the first IP address is an IP address assigned to the second terminal;

The first terminal sends the second IP address to the second terminal according to the first IP address.

In a second aspect, a method for assigning an IP address is provided, including:

receiving, by the first network element, a first request message from the first terminal, where the first request message is used to request allocation of an IP address for the second terminal;

The first network element sends the first IP address to the first terminal.

In a third aspect, an IP address allocation device is provided, including:

A first sending module, configured for the first terminal to send a first request message to the first network element, where the first request message is used to request to assign an IP address to the second terminal;

A first receiving module, configured for the first terminal to receive a first IP address from the first network element, where the first IP address is an IP address assigned to the second terminal;

The second sending module is configured for the first terminal to send a second IP address to the second terminal according to the first IP address.

In a fourth aspect, an IP address allocation device is provided, including:

A second receiving module, configured for the first network element to receive a first request message from the first terminal, where the first request message is used to request to assign an IP address to the second terminal;

A third sending module, configured for the first network element to send the first IP address to the first terminal.

In a fifth aspect, a terminal is provided, the terminal includes a processor and a memory, the memory stores programs or instructions that can run on the processor, and when the programs or instructions are executed by the processor, the following The steps of the method in one aspect.

According to a sixth aspect, a terminal is provided, including a processor and a communication interface, wherein the communication interface is used for the first terminal to send a first request message to the first network element, and the first request message is used for requesting to be the first network element. Assigning an IP address to the second terminal; the first terminal receives a first IP address from the first network element, and the first IP address is an IP address assigned to the second terminal; the first terminal receives the first IP address according to the the first IP address, and send the second IP address to the second terminal.

In a seventh aspect, a network-side device is provided, the network-side device includes a processor and a memory, the memory stores programs or instructions that can run on the processor, and the programs or instructions are executed by the processor When realizing the steps of the method as described in the first aspect.

In an eighth aspect, a network side device is provided, including a processor and a communication interface, wherein the communication interface is used for a first network element to receive a first request message from a first terminal, and the first request message is used for requesting to assign an IP address to the second terminal; the communication interface is used for the first network element to communicate with the The first terminal sends the first IP address.

In the ninth aspect, a readable storage medium is provided, and programs or instructions are stored on the readable storage medium, and when the programs or instructions are executed by a processor, the steps of the method described in the first aspect are realized, or the steps of the method described in the first aspect are realized, or The steps of the method described in the second aspect.

In a tenth aspect, a chip is provided, the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the method as described in the first aspect steps, or realize the steps of the method as described in the second aspect.

In an eleventh aspect, a computer program product is provided, the computer program product is stored in a storage medium, and the computer program product is executed by at least one processor to implement the steps of the method described in the first aspect, or The steps of the method described in the second aspect are implemented.

In this embodiment of the application, the first terminal assists the second terminal in requesting the allocation of an IP address. In the scenario where the second terminal accesses the communication network, the network can identify the corresponding service flow based on the IP address of the second terminal, and then Take administrative control.

Description of drawings

Fig. 1a is a schematic structural diagram of a wireless communication system provided by an embodiment of the present application;

Figure 1b is a schematic diagram of a personal Internet of Things architecture;

Figure 1c is a schematic diagram of a fixed-mobile fusion architecture;

FIG. 2 is one of the schematic flow diagrams of the IP address allocation method provided by the embodiment of the present application;

Fig. 3 is the second schematic flow diagram of the IP address allocation method provided by the embodiment of the present application;

Fig. 4a is one of the schematic flow charts of the application example provided by the embodiment of the present application;

Figure 4b is the second schematic flow diagram of the application example provided by the embodiment of the present application;

Fig. 4c is the third schematic flow diagram of the application example provided by the embodiment of the present application;

Fig. 4d is the fourth schematic flow diagram of the application example provided by the embodiment of the present application;

FIG. 5 is one of the structural schematic diagrams of the IP address allocation device provided by the embodiment of the present application;

FIG. 6 is the second structural schematic diagram of the IP address allocation method provided by the embodiment of the present application;

FIG. 7 is a schematic structural diagram of a communication device provided by an embodiment of the present application;

FIG. 8 is a schematic structural diagram of a terminal provided in an embodiment of the present application;

FIG. 9 is a schematic structural diagram of a network side device provided by an embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present application will be clearly described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, but not all of them. All other embodiments obtained by persons of ordinary skill in the art based on the embodiments in this application belong to the protection scope of this application.

The terms "first", "second" and the like in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specific sequence or sequence. It is to be understood that the terms so used are interchangeable under appropriate circumstances such that the embodiments of the application are capable of operation in sequences other than those illustrated or described herein and that "first" and "second" distinguish objects. It is usually one category, and the number of objects is not limited. For example, there may be one or more first objects. In addition, "and/or" in the description and claims means at least one of the connected objects, and the character "/" generally means that the related objects are an "or" relationship.

It is worth pointing out that the technology described in the embodiment of this application is not limited to the Long Term Evolution (Long Term Evolution, LTE)/LTE-Advanced (LTE-Advanced, LTE-A) system, and can also be used in other wireless communication systems, such as code Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access, OFDMA), Single-carrier Frequency Division Multiple Access (Single-carrier Frequency Division Multiple Access, SC-FDMA) and other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the described technology can be used for the above-mentioned system and radio technology, and can also be used for other systems and radio technologies. The following description describes the New Radio (NR) system for illustrative purposes, and uses NR terminology in most of the following descriptions, but these techniques can also be applied to applications other than NR system applications, such as the 6th generation (6 ^th Generation, 6G) communication system.

Fig. 1a shows a block diagram of a wireless communication system to which the embodiment of the present application is applicable. Department of Wireless Communication The system includes a terminal 11 and a network side device 12. Wherein, the terminal 11 can be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer) or a notebook computer, a personal digital assistant (Personal Digital Assistant, PDA), a palmtop computer, a netbook, a super mobile personal computer (ultra-mobile personal computer, UMPC), mobile Internet device (Mobile Internet Device, MID), augmented reality (augmented reality, AR) / virtual reality (virtual reality, VR) equipment, robot, wearable device (Wearable Device) , vehicle equipment (VUE), pedestrian terminal (PUE), smart home (home equipment with wireless communication functions, such as refrigerators, TVs, washing machines or furniture, etc.), game consoles, personal computers (personal computers, PCs), teller machines or self-service Wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart anklets, etc.), Smart wristbands, smart clothing, etc. It should be noted that, the embodiment of the present application does not limit the specific type of the terminal 11 . The network side device 12 may include an access network device or a core network device, wherein the access network device 12 may also be called a radio access network device, a radio access network (Radio Access Network, RAN), a radio access network function, or Wireless access network unit. The access network device 12 may include a base station, a wireless local area network (Wireless Local Area Network, WLAN) access point or a WiFi node, etc., and the base station may be called a node B, an evolved node B (eNB), an access point, or a base transceiver station (Base Transceiver Station, BTS), radio base station, radio transceiver, Basic Service Set (BSS), Extended Service Set (Extended Service Set, ESS), Home Node B, Home Evolved Node B, sending and receiving point (Transmitting Receiving Point, TRP) or some other appropriate term in the field, as long as the same technical effect is achieved, the base station is not limited to specific technical terms. It should be noted that in the embodiment of this application, only the NR system The base station in the example is introduced as an example, and the specific type of the base station is not limited. The core network equipment may include but not limited to at least one of the following: core network node, core network function, mobility management entity (Mobility Management Entity, MME), access mobility management function (Access and Mobility Management Function, AMF), session management function (Session Management Function, SMF), User Plane Function (UPF), Policy Control Function (Policy Control Function, PCF), Policy and Charging Rules Function Unit (Policy and Charging Rules Function, PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (Home Subscriber Server, HSS), centralized network configuration (Centralized network configuration, CNC), network storage function (Network Repository Function, NRF), network exposure function (Network Exposure Function, NEF), local NEF (Local NEF, or L-NEF), binding Support function (Binding Support Function, BSF), application function (Application Function, AF), etc. It should be noted that, in the embodiment of the present application, only the core network equipment in the NR system is used as an example for introduction, and the specific type of the core network equipment is not limited. It should be noted that the functions of the above-mentioned core network device may be realized by multiple devices, or the functions of multiple core network devices may be realized by one device, which is not limited in this embodiment of the present application. In the embodiment of the present application, if the functions of multiple core network devices are implemented by one device, the interaction among the multiple core network devices in the embodiment of the present application is an internal operation of the device.

In order to better understand the technical solution of this application, the following contents are firstly introduced:

Personal IoT Network (PIN)

Fig. 1b shows a personal internet of things architecture, a PIN is a group consisting of at least one PIN element (PIN element, PINE), wherein at least one PIN element is a UE. PIN elements communicate with each other. Two PIN elements can communicate through a direct connection between them, or indirectly through a communication network.

A PIN element is a UE or a non-3GPP device. A PIN element may also be a Non-5G-Capable over WLAN (N5CW) device on a wireless local area network. Non-3GPP devices refer to devices that do not use credentials defined by 3GPP, devices that do not support the Non-access stratum (Non-access stratum, NAS) protocol defined by 3GPP, or devices that do not support 3GPP access technologies (such as 3G/4G/5G air interface technology ) and only supports non-3GPP access technologies (such as WiFi, fixed network, Bluetooth and other access technologies). It is worth noting that when the PIN element is UE, when it accesses the communication network through PEGC, it can also execute the process of non-3GPP equipment or N5CW equipment, for example, the NAS of UE is not used to interact with the communication network.

There can be one or more PINEs (PIN element with gateway capability, PEGC) in a PIN. The PIN elements in the PIN can communicate with each other directly or through PEGC. The PIN element in the PIN can communicate with other devices or application servers outside the PIN through the PEGC. PEGC can be a gateway in a smart home scenario, or a mobile phone in a wearable device scenario.

Fixed Mobile Convergence (Wireline Wireless Convergence, WWC)

Referring to Figure 1c, the current 3GPP 5G core network supports fixed network access. It includes support for residential gateways (Residential Gateway, RG) to access the 5G core network through fixed networks and 3GPP networks, and also includes the access of 3GPP terminal devices to the 5G core network through residential gateways.

In the prior art, the mobile phone can set up a WiFi hotspot for other devices, such as enabling a notebook to access the Internet through the mobile phone. However, the notebook is a non-3GPP device, and the communication network cannot know that the notebook is surfing the Internet, and it is also difficult to identify the business flow of the notebook, so that it cannot perform management operations such as policy control and billing. In the scenario of personal IoT and fixed-mobile convergence, how to identify the service flow of non-3GPP devices is an urgent problem to be solved.

The IP address allocation method provided by the embodiment of the present application will be described in detail below through some embodiments and application scenarios with reference to the accompanying drawings.

Referring to Fig. 2, the embodiment of the present application provides a method for assigning an IP address, including:

Step 201: the first terminal sends a first request message to the first network element, where the first request message is used to request to assign an IP address to the second terminal;

Step 202: the first terminal receives a first IP address from the first network element, where the first IP address is an IP address assigned to the second terminal;

Step 203: the first terminal sends the second IP address to the second terminal according to the first IP address;

In the embodiment of the present application, the first terminal is a personal Internet of Things gateway or a home gateway, and the second terminal is a device that cannot use the NAS protocol. As an optional implementation, the second terminal is a non-3GPP device or a personal Internet of Things device. As another optional implementation, the second terminal is a 3GPP device, and the connection between the second terminal and the first terminal The connection does not support NAS protocol transfers.

Optionally, a non-3GPP technology is used to establish a connection between the first terminal and the second terminal. For example, A connection may be established between the first terminal and the second terminal through WiFi, Bluetooth or passive Internet of Things (Passive IoT) technology. It is worth noting that when the first terminal and the second terminal establish a connection through the passive Internet of Things, the second terminal can be a 3GPP device or a non-3GPP device, and the passive Internet of Things technology can also be a 3GPP access technology or a non-3GPP access technology. into technology.

In the embodiment of the present application, the first terminal assists the second terminal to request IP address allocation, and in the scenario where non-3GPP devices access the communication network through the personal Internet of Things network or home network, the network can be based on the allocation of IP addresses for non-3GPP devices. The IP address identifies the service flow of non-3GPP equipment, and then performs management and control.

It should be noted that, in the application scenario of the embodiment of the present application, since the number of second terminals connected to the first terminal may be one or more, correspondingly, the first network element may also be the one or more second terminals The second terminal allocates one or more first IP addresses.

In a possible implementation manner, the first network element is a mobility management function (Access and Mobility Management Function, AMF) or a session management function (Session Management Function, SMF).

In a possible implementation manner, the first terminal is a personal Internet of Things gateway or a home gateway.

In a possible implementation manner, the second terminal is a non-3GPP device or a personal Internet of Things device.

In a possible implementation manner, the connection between the first terminal and the second terminal is established through WiFi, Bluetooth or passive Internet of Things (Passive IoT) technology. It is worth noting that when the first terminal and the second terminal establish a connection through the passive Internet of Things, the second terminal can be a 3GPP device or a non-3GPP device, and the passive Internet of Things technology can also be a 3GPP access technology or a non-3GPP access technology. into technology.

In a possible implementation manner, the first request message carries one or more of the following:

(1) the identification of the first terminal;

(2) PIN instructions;

(3) Non-3GPP instructions;

(4) N5CW instructions;

(5) an indication of requesting an IP address for a terminal that does not support NAS;

(6) Passive IoT indication.

In a possible implementation manner, the first terminal sends the first request message to the first network element, including:

The first terminal sends the first request message to the first network element through the NAS connection with the first network element.

In a possible implementation manner, the first request message carries identification information of the second terminal;

Correspondingly, before the first terminal sends the first request message to the first network element, the method may further include:

The first terminal acquires the identification information of the second terminal.

Exemplarily, the first terminal obtains the identification information of the second terminal, including:

The first terminal receives a second request message from the second terminal, where the second request message carries identification information of the second terminal, and the second request message is used to request to assign an IP address to the second terminal.

Exemplarily, the foregoing second request message may be an IP address configuration request message.

In a possible implementation manner, the second IP address is the same as the first IP address, or the second IP address has a mapping relationship with the first IP address.

In the embodiment of the present application, the IP address may specifically be an Internet Protocol version 4 (Internet Protocol version 4, IPv4) address or an Internet Protocol version 6 (Internet Protocol version 6, IPv6) address; the above-mentioned second IP address is the same as the first IP address It may refer to: the IPv4 address sent by the first terminal to the second terminal is the same as the IPv4 address allocated by the first network element to the second terminal, or the IPv6 address sent by the first terminal to the second terminal is the same as the IPv6 address sent by the first network element. The IPv6 addresses assigned by the two terminals are the same; the above-mentioned second IP address having a mapping relationship with the first IP address may refer to: the IPv4 address sent by the first terminal to the second terminal is the same as the IPv4 address assigned by the first network element to the second terminal The local area network IPv4 address corresponding to the address, or the IPv6 address sent by the first terminal to the second terminal is a local area network IPv6 address corresponding to the IPv6 address allocated by the first network element to the second terminal. For example, the first address is the IP address of the second address after network address translation. vice versa.

Optionally, the first IP address includes an IPv6 prefix and a local identifier assigned by the first network element, or the first IP address is an IPv6 prefix, and the second IP address includes the first IP address and a local identifier assigned by the first terminal. to identify.

In this embodiment of the application, the first network may allocate an IPv6 prefix and a local identifier to the second terminal, or the first network may allocate an IPv6 prefix to the second terminal, and then the first terminal allocates an IPv6 prefix to the second terminal. local identification;

Finally, the IPv6 address of the second terminal is composed of the IPv6 prefix and the local identifier, that is, the second IP address. Correspondingly, the first terminal can send the IPv6 address composed of the IPv6 prefix and the local identifier to the second terminal, or send Send the LAN IPv6 address corresponding to the IPv6 address composed of the IPv6 prefix and the local identifier.

In a possible implementation manner, the first request message includes any of the following:

(1) NAS message;

(2) Protocol Data Unit (Protocol Data Unit, PDU) session request establishment request message;

(3) PDU session modification request message.

In a possible implementation manner, the identification information of the second terminal includes one or more of the following:

(1) the Media Access Control (Media Access Control, MAC) address of the second terminal;

(2) the device identification of the second terminal;

(3) International Mobile Subscriber Identity (IMSI) of the second terminal;

(4) Subscription Permanent Identifier (SUPI) of the second terminal;

(5) Generic Public Subscription Identifier (Generic Public Subscription Identifier, GPSI) of the second terminal.

Referring to Fig. 3, the embodiment of the present application provides a method for assigning an IP address, including:

Step 301: The first network element receives a first request message from the first terminal, where the first request message is used to request to assign an IP address to the second terminal;

Step 302: the first network element sends the first IP address to the first terminal;

Optionally, the first terminal is a 3GPP device, the second terminal is a non-3GPP device, and the connection between the first terminal and the second terminal is established through non-3GPP.

In the embodiment of this application, the non-3GPP device (ie, the second terminal) is assisted by the 3GPP device (ie, the first terminal) to request the allocation of an IP address. , so that the network can identify the service flow of the non-3GPP device based on the IP address assigned to the non-3GPP device, and then perform management and control.

In a possible implementation manner, after the first network element receives the first request message from the first terminal, the method further includes:

The first network element allocates the first IP address to the second terminal.

In a possible implementation manner, the connection between the first terminal and the second terminal is established through WiFi, Bluetooth or passive Internet of Things (such as Passive IoT). It is worth noting that when the first terminal and the second terminal establish a connection through the passive Internet of Things, the second terminal can be a 3GPP device or a non-3GPP device, and the passive Internet of Things technology can also be a 3GPP access technology or a non-3GPP access technology. into technology.

(1) the identification of the first terminal;

(2) PIN instructions;

(3) Non-3GPP instructions;

(4) N5CW instruction;

(6) Passive IoT indication.

In a possible implementation manner, the first network element receives the first request message from the first terminal, including:

The first network element receives the first request from the first network element through the NAS connection with the first terminal Ask for news.

In a possible implementation manner, the first request message carries identification information of the second terminal.

In a possible implementation manner, when the first network element is prepared as an AMF, the first network element assigns the first IP address to the second terminal, including:

(1) The first network element sends a third request message to the SMF, and the third request message is used to request to allocate an IP address for the second terminal;

(2) The first network element receives the first IP address from the SMF.

As a possible implementation manner, when the first network element is an AMF, after receiving the first request from the first terminal, the AMF sends a request message to the SMF to request allocation of an IP address for the second terminal.

Exemplarily, the third request message may be an N11 message.

In a possible implementation manner, the third request message carries one or more of the following:

(1) the identification of the first terminal;

(2) PIN instructions;

(3) Non-3GPP instructions;

(4) N5CW instructions;

(6) Passive IoT indication.

As another possible implementation manner, the first network element is prepared as an SMF. The first network element can be any of the following:

(1) SMF with PIN capability;

(2) SMF with the ability to assign IP addresses to non-3GPP devices;

(3) The SMF serving the target PDU session, the first request message carries the identifier of the target PDU session.

Further, the first network element allocates the first IP address to the second terminal, including:

The first network element allocates the first IP address to the second terminal according to the subscription data of the first terminal and/or operator configuration.

In this embodiment of the present application, if the first network element is an SMF that satisfies the above conditions, the SMF may assign the first IP address to the second terminal according to the subscription data of the first terminal and/or operator configuration.

In a possible implementation manner, the method also includes:

The first network element sends the first IP address and the policy control rule to the user plane function (User Plane Function, UPF), and the policy control rule is used to indicate that the first IP address is forwarded by the target PDU session, and the first request message carries The ID of the target PDU session.

In a possible implementation manner, the method also includes:

The first network element sends the first IP address to the AMF, that is, the SMF sends the first IP address to the AMF after allocating the first IP address to the second terminal.

In a possible implementation manner, the method also includes:

The first network element triggers an authentication process of the second terminal;

Correspondingly, the first network element allocates the first IP address to the second terminal, including:

After the second terminal is successfully authenticated, the first network element allocates the first IP address to the second terminal.

In the embodiment of the present application, the SMF triggers the authentication process of the second terminal, and assigns the first IP address to the second terminal after the authentication is successful. The authentication process may be an extensible authentication protocol (Extensible Authentication Protocol, EAP) process or other authentication protocols. For example, use Challenge Handshake Authentication Protocol-Password Authentication Protocol (CHAP-PAP) for authentication. In the authentication process of the second terminal, the authentication server that performs authentication for the second terminal may be a unified data management function, an authentication authorization server, or an application server related to the second terminal. This embodiment of the present application does not make any limit.

(1) NAS message;

(2) PDU session request establishment request message;

(3) PDU session modification request message.

(1) MAC address of the second terminal;

(2) the device identification of the second terminal;

(3) IMSI of the second terminal;

(4) SUPI of the second terminal;

(5) GPSI of the second terminal.

The technical solutions of the embodiments of the present application are described below in conjunction with specific application examples. The embodiment of the present application takes the 5G network as an example, but the solution described in the embodiment of the present application can also be used in other intergenerational communication networks.

Example 1, see Figure 4a:

Step 0. The PEGC obtains the identification information of the PINE.

As a possible implementation, the PEGC initiates an authentication process to obtain the identification information of the PINE. PINE sends its own identification information to PEGC during the authentication process.

As another possible implementation, PINE sends an Internet Key Exchange (IKEv2) message to PEGC, which includes the identification information of PINE.

As yet another possible implementation manner, the PINE may use other L2 or L1 protocols to send its own identification information to the PEGC, which is not limited in this embodiment.

Exemplarily, PEGC and PINE use the EAP authentication process. For example, PEGC sends an EAP-Req/Identity message to PINE. PINE sends an EAP-Res/Identity message to PEGC, which includes its own identity. The identity of the PINE may be sent in the form of a Network Access Identity (NAI). Optionally, PINE can indicate that it does not support NAS access to 5GC, or that it wishes to access 5GC without NAS. For example, the field 5gc-nn may be included in the NAI to indicate that it does not support NAS access to 5GC, or it wishes to access 5GC without NAS.

In the embodiment of this application, 5GC is also called 5G Core Network (5G Core Network).

Exemplarily, the NAI sent by PINE can be:

type1.rid678.schid0.useriduser17@nai.5gc-nn.mnc123.mcc45.3gppnetwork.org.

The identification information of the PINE is used to identify the PINE in the PIN or in the 5G system, for example, it can be the MAC address of the PINE, the device identification of the PINE, IMSI, SUPI, user hidden identification (Subscription Concealed Identifier, SUCI), or Generic Public Subscription Identifier (GPSI), etc.

Step 1. PINE sends an IP configuration request message to PEGC.

Exemplarily, the IP configuration request message is a Dynamic Host Configuration Protocol (Dynamic Host Configuration Protocol, DHCP) request message.

The IP configuration request message may include the identifier of PINE. In this case, step 0 can be considered to be implemented by step 1.

Step 1 is optional.

Step 2. The PEGC sends a NAS message to the AMF, indicating that it requests an IP address for the PINE.

The NAS message includes at least one of the identifier of the PEGC and the identifier of the PINE.

Optionally, the NAS message may also carry a PIN indication, which is used to indicate to request an IP address for a PINE, or to indicate to request an IP address for a non-3GPP device. Alternatively, the N5CW indication or the passive Internet of Things indication may also be carried in the NAS message, indicating that an IP address is requested for the N5CW device or the passive Internet of Things device. Alternatively, the NAS message may also include an indication to request an IP address for a terminal that does not support NAS, indicating to request an IP address for a device that does not support NAS when accessing the 5GC through the PEGC.

Optionally, the NAS message may also include the type of the requested IP address, such as IPv4, IPv6, or IPv4v6.

Optionally, the NAS message may also include session parameters required by PINE, such as Data Network Name (Data Network Name, DNN), Single-Network Slice Selection Assistance Information (S-NSSAI), service ID , Session and Service Continuity mode (Session and Service Continuity mode, SSC mode), etc.

Exemplarily, the PEGC sends a NAS message to the AMF, which includes a PDU session establishment request message. The PDU Session Establishment Request message may indicate that an IP address is requested for the PINE. For example, the PDU session establishment request message includes at least one of the above parameters, such as the identifier of the PEGC, the identifier of the PINE, the PIN indication, the type of the requested IP address, and the session parameters required by the PINE. Optionally, the PDU session establishment request message may be a PINE session establishment request message or a non-3GPP device session establishment request message. The identity of the PINE itself may also indicate that the PINE needs to be connected to the core network.

The PEGC can send the above NAS message through the NAS connection between itself and the AMF. The AMF is an AMF serving PEGC.

Step 3. The AMF sends an N11 message to the SMF, indicating that the IP address is requested for the PINE.

The N11 message includes at least one of the above parameters, such as the identifier of the PEGC, the identifier of the PINE, the PIN indication, the type of the requested IP address, and the session parameters required by the PINE.

Optionally, the N11 message also includes an indication indicating whether an IP address needs to be allocated to the PEGC. If the PEGC already has an IP address, or if the PEGC does not share the PDU session with the PINE, there is no need to assign an IP address to the PEGC. Otherwise, it may be necessary to assign an IP address to the PEGC.

Exemplarily, the AMF sends the PDU session establishment request message received in step 2 to the SMF.

Optionally, the AMF selects the SMF according to the capability of the SMF. For example, the AMF selects an SMF that can support the ability to assign IP addresses to PINEs connected to the PEGC.

Optionally, when the SMF goes online, the following process can be performed: the SMF sends a network element registration request to the NRF, which includes the PIN capability indication information of the SMF, and the PIN capability indication information indicates that the SMF can support IP allocation for the PINE connected to the PEGC address. The AMF can send a query message to the NRF to query the SMF with PIN capability. AMF acquires PIN capable SMF from NRF.

The SMF may be the SMF serving the PEGC, or may not be the SMF serving the PEGC.

Optionally, the AMF selects the SMF from the SMFs serving the PEGC according to the session parameters received in step 2. Alternatively, the AMF selects the SMF according to the operator's configuration information.

Step 4. The SMF obtains the subscription data of the PEGC from the UDM.

The SMF can determine that the PINE device is allowed to access from the PEGC according to the subscription data of the PEGC and the configuration of the operator. For example, if the subscription data of the PEGC stores the identification information of the PINE, it means that the PINE device indicated by the identification of the PINE is allowed to access from the PEGC.

For example, if the SMF has already stored the subscription data of the PEGC, this step is optional.

Step 5. The SMF sends an N4 session establishment request message to the UPF to allocate session resources for the PINE.

N4 The session establishment request message can include the IP address assigned by the SMF to PINE, and the IP address specified by the PCC but.

SMF can assign one or more IPv4 addresses, one or more IPv6 addresses, or one IPv6 prefix and multiple local identifiers, or one IPv6 prefix to one or more PINEs.

Optionally, the N4 session establishment request message may also include the IP address assigned by the SMF to the PEGC. If the SMF allocates multiple IP addresses, the SMF needs to ensure that the multiple IP addresses can be served by the same UPF.

Optionally, a PIN indication is also included. The PIN indication is used to indicate that the UPF needs to handle service flows of multiple devices.

The FAR in the PCC rule indicates that data packets with multiple IP addresses can be forwarded by this PDU session. For example, the destination IP address of the downlink packet detection template in the FAR includes multiple IP addresses allocated by the SMF. Alternatively, the source IP address of the upstream packet detection template in the FAR includes multiple IP addresses allocated by the SMF.

Optionally, the SMF selects a UPF capable of serving the PINE connected to the PEGC. Optionally, the UPF reports its own PIN capability to the SMF, and the SMF selects a UPF with the PIN capability according to the acquired UPF capability information.

Step 6. The UPF sends an N4 session establishment response message to the SMF to indicate that the N4 session has been established.

The N4 session establishment request message and response message in steps 5 and 6 can be replaced with N4 session modification request message and response message. Through the above steps, the N4 session between SMF and UPF has been established or modified.

Step 7. The SMF sends a response message to the N11 message to the AMF. Indicates that the IP address of PINE has been allocated successfully, or indicates that network resources have been allocated for PINE.

The response message of the N11 message may include the IP address assigned by the SMF to the PINE. Optionally, the IP address allocated for the PEGC may also be included. Optionally, at least one of identification information of PINE and identification information of PEGC may also be included.

Exemplarily, the N11 message includes a PDU session establishment response message. The above parameters are included in the PDU session establishment response message.

Step 8. AMF sends NAS message to PEGC.

The NAS message indicates that the IP address of the PINE has been allocated successfully, or indicates that the network resource has been allocated for the PINE. Optionally, the NAS message includes at least one of a PEGC identifier and a PINE identifier. Exemplarily, the NAS message includes a PDU session establishment response message.

Step 9. The PEGC sends an IP configuration response message to the PINE, which carries the IP address allocated for the PINE.

Exemplarily, the IP configuration response message is a DHCP message.

There are several implementation methods for assigning IP addresses to PINE:

1) SMF assigns one or more IPv4 addresses to PINEs connected to PEGC, and PEGC assigns an IPv4 address to each PINE. The IPv4 address may be the same as the IPv4 address assigned by the SMF, or may be a local area network IPv4 address corresponding to the IPv4 address assigned by the SMF.

2) SMF assigns one or more IPv6 addresses to PINEs connected to PEGC, and PEGC assigns an IPv6 address to each PINE. The IPv6 address may be the same as the IPv6 address assigned by the SMF, or may be a local area network IPv6 address corresponding to the IPv6 address assigned by the SMF.

3) SMF assigns an IPv6 prefix and multiple local identifiers to PINEs connected to PEGC, and PEGC assigns an IPv6 address to each PINE. The IPv6 address includes the IPv6 prefix assigned by the SMF and a local identifier, or may also include a local area network IPv6 address corresponding to the IPv6 address composed of the IPv6 prefix assigned by the SMF and a local identifier.

4) SMF assigns an IPv6 prefix to PINEs connected to PEGC, and PEGC assigns an IPv6 address to each PINE. This IPv6 address includes the local identifier determined by the PEGC. The IPv6 address may include the same IPv6 prefix as the IPv6 prefix assigned by the SMF, or may include a local area network IPv6 prefix corresponding to the IPv6 prefix assigned by the SMF.

It is worth noting that the IP addresses assigned by PEGC to different PINEs may be different or the same.

Step 9 is optional. For example, when step 9 is not executed, it can be considered that the PEGC stores the IP address allocated to the PINE, or the PEGC stores the relationship between the IP address allocated to the PINE by the SMF and the corresponding IP address allocated to the PINE by the PEGC. The process of PEGC assigning IP addresses to PINE can also Execute in step 1.

Step 10. The SMF sends the identification information of the PINE and the corresponding IP address to the PIN server.

Step 10 is optional.

It should be noted that this example uses the PDU session establishment request and response as an example, and this message can also be replaced with a PDU session modification request and response.

As a possible implementation manner, the PEGC has not yet established a PDU session, and at this time, the PEGC requests to establish a PDU session to serve the PEGC and the PINE connected to the PEGC. At this time, the PEGC sends a PDU session establishment request message to request IP addresses for the PEGC and the PINE.

As another possible implementation manner, the PEGC may already have its own PDU session, and the PEGC requests to establish a separate PDU session for the PINE connected to it. At this time, the PEGC sends a PDU session establishment request message to request an IP address for the PINE.

As yet another possible implementation manner, the PEGC has established a PDU session, and the PDU session may also serve the PINE, or the PEGC may serve the PDU session with the PINE. At this time, the PEGC sends a PDU session modification request message, and sends the identification information of the PDU session. The PEGC indicates that the PDU session modification request is to request an IP address for the PINE. As an example, before this procedure, the PEGC requests a PDU session establishment. The PEGC sends a NAS message to the AMF, which includes a PDU session establishment request, and optionally includes a PIN indication. The PIN indication may indicate that the PEGC has PIN capability, ie allows the PINE to connect to the PEGC. The PIN indication can also be represented by the logo of the PEGC. or. The AMF acquires the subscription data of the PEGC, and the subscription data of the PEGC indicates that the PEGC has a PIN capability, or indicates that the PEGC has a PIN gateway capability. The AMF selects an SMF with PIN capability according to the PIN indication or the PIN capability of the PEGC. Optionally, the AMF stores the PIN indication in the PDU session context. In step 3 of this example, the AMF selects an SMF serving the PDU session according to the PDU session identifier in the NAS message.

As yet another possible implementation manner, the PEGC has established a PDU session, and the PDU session may also serve the PINE, or the PEGC may serve the PDU session with the PINE. At this time, the PEGC sends a PDU session establishment request message, and sends the identification information of the PDU session. And indicate that the PDU session establishment request is to request an IP address for PINE. In step 3, AMF according to NAS message The PDU session identifier in the message selects the SMF serving the PDU session.

It is worth noting that, through step 0 or 1, PEGC can obtain the identification information of one or more PINEs. In the subsequent process, the PINE identification information may include identification information of one or more PINEs. SMF can assign IP addresses to one or more PINEs.

In this example, PEGC can be replaced by RG, and PINE can also be replaced by other non-3GPP devices.

Through this example, the PEGC indicates to the PINE connected to the PEGC that an IP address needs to be allocated for the PINE, and the PEGC can create a new PDU session or make a request in an existing PDU session, so that the AMF can choose an SMF with PIN capability, and the SMF can choose to have a PIN Capable UPF, and the SMF allocates one or more IP addresses in this PDU session establishment or modification process, which satisfies the use of PINE connected to the PEGC.

Example 2, see Figure 4b:

1. PINE sends an IP configuration request message to PEGC.

For step 1, refer to the description of step 1 in Example 1.

2. The PEGC sends a NAS message to the AMF, including a PDU session establishment request message.

Optionally, the NAS message carries a PIN indication. The PIN indication indicates that this PDU session can be used to serve the PINE connected to this PEGC. Or it means assigning an IP address to the PINE connected to the PEGC. Alternatively, the NAS message includes an indication to request an IP address for the non-3GPP device. Alternatively, the N5CW indication or the passive Internet of Things indication may also be carried in the NAS message, indicating that an IP address is requested for the N5CW device or the passive Internet of Things device. Alternatively, the NAS message may also include an indication to request an IP address for a terminal that does not support NAS, indicating to request an IP address for a device that does not support NAS when accessing the 5GC through the PEGC.

3. The AMF sends an N11 message to the SMF, which includes a PDU session establishment request message.

Optionally, the AMF selects an SMF with PIN capability according to the subscription data of the PEGC. How the AMF selects the SMF with the PIN capability can refer to the description in Step 3 of Example 1.

Optionally, the AMF may also select an SMF with PIN capability according to the PIN instruction received in step 2.

The PIN indication is included in the N11 message.

4. The SMF obtains the subscription data of the PEGC from the UDM.

For step 4, refer to the description of step 4 in Example 1.

5. The SMF sends an N4 Setup Request message to the UPF.

The N4 establishment request message includes the IP address assigned by the SMF to the PEGC.

6. The UPF sends an N4 Setup Response message to the SMF.

Optionally, the SMF may assign one or more IP addresses to the PINE connected to the PEGC according to the PIN instruction. The SMF can determine the number and type of allocated IP addresses according to the operator's configuration or the PEGC's contract. If the SMF assigns an IP address to PINE, for step 5-6, reference may be made to the description of step 5-6 in Example 1.

7. The SMF sends a response message of the N11 message to the AMF, which includes a PDU session establishment response message.

The response message of the N11 message may include the IP address assigned by the SMF to the PEGC. Optionally, one or more IP addresses allocated by PINE are also included.

8. The AMF sends a NAS message to the PEGC, including a PDU session establishment response message.

9. The PEGC sends an IP configuration response message to the PINE, which carries the IP address allocated for the PINE.

For step 9, refer to the description of step 9 in Example 1.

It is worth noting that step 1 may occur before step 9, and there is no sequence limitation with other steps.

Through this example, PEGC can indicate that an IP address needs to be assigned to PINE during the process of PDU session establishment request, so that AMF selects SMF with PIN capability, SMF selects UPF with PIN capability, and SMF allocates an IP address in this PDU session establishment process. or multiple IP addresses, satisfying the use of PINE connected to PEGC. It is worth noting that when PEGC uses this process to request an IP address for PINE, PINE may not be connected to PEGC yet.

Example 3, see Figure 4c:

1. An L2 connection is established between PINE and PEGC.

Exemplarily, the PINE is associated with or connected to the WLAN of the PEGC.

2. PEGC initiates the authentication process to obtain the identification information of PINE.

For step 2, refer to the description of step 0 in Example 1.

3. The authentication process between PINE and 5GC.

Exemplarily, an EAP process may be used for authentication between PINE and 5GC. Step 3 is optional.

4. The PEGC sends a NAS message to the AMF, indicating that it requests an IP address for the PINE.

For step 4, refer to the description of step 2 in Example 1.

5. The AMF sends an N11 message to the SMF, indicating that the PINE requests an IP address.

For step 5, refer to the description of step 3 in Example 1.

6-7. N4 session establishment process between SMF and UPF.

8-9. SMF sends the IP address allocated for PINE to PEGC through AMF.

For the above steps 6-9, reference may be made to the description of steps 5-8 in Example 1.

10. The process of PEGC configuring an IP address for PINE.

For step 10, refer to the description of steps 1 and 9 in Example 1.

It is worth noting that step 3 can also occur after step 5. That is, after receiving the N11 message in step 5, the SMF triggers the authentication procedure for PINE. As an example, the SMF sends an authentication request to the AMF, and the request is PINE authentication. The authentication request message may include the identifier of PINE. Optionally, the logo of PEGC may also be included.

Through this example, the PEGC obtains the identification information of the PINE through the establishment of an L2 connection with the PINE or an EAP message, and requests to allocate an IP address for the PINE through its own NAS connection.

Example 4, see Figure 4d:

1. Establish a connection between PINE and PEGC and obtain an IP address.

Exemplarily, the PINE associates or connects to the WLAN of the PEGC, and obtains an IP address from the WLAN of the PEGC. PINE can request an IP address with a DHCP request or other message. This example is not limited.

Optionally, the PEGC may first authenticate the PINE and then assign an IP address to the PINE. PEGC What information is used for PINE authentication is not limited in this application example.

2. PINE establishes an IP security association (IPsec Security Association, IPSec SA) with PEGC.

Exemplarily, IKE initial messages are exchanged between PINE and PEGC.

3. PINE sends an IKE_AUTH request message to PEGC.

As a possible implementation manner, the IKE_AUTH request message includes the identification information of the PINE. For the identification information of PINE, refer to the description of Example 1.

As another possible implementation manner, the PINE sends an IKE_AUTH request message to the PEGC, which does not carry the AUTH parameter, indicating that EAP authentication is required. PEGC sends IKE_AUTH response message to PINE, which includes EAP request message. The PINE sends an IKE_AUTH request message to the PEGC, which includes an EAP response message, including the identification information of the PINE.

4. The authentication process between PINE and 5GC.

For step 4, refer to the description of step 3 in Example 3.

5. The PEGC sends a NAS message to the AMF, indicating that it requests an IP address for the PINE.

For step 5, refer to the description of step 2 in Example 1.

6. The AMF sends an N11 message to the SMF, indicating that the PINE requests an IP address.

For step 6, refer to the description of step 3 in Example 1.

7-8. N4 session establishment process between SMF and UPF.

9-10. SMF sends the IP address allocated for PINE to PEGC through AMF.

For the above steps 7-10, reference may be made to the description of steps 5-8 in Example 1.

11. The PEGC sends an IKEv2 message to PINE, which carries the IP address allocated for PINE.

For the implementation of PEGC assigning IP addresses to PINEs, reference may be made to the description of Step 9 in Example 1.

It is worth noting that step 4 can also occur after step 6. That is, after receiving the N11 message in step 6, the SMF triggers the authentication procedure for PINE. As an example, the SMF sends an authentication request to the AMF, and the request is PINE authentication. The authentication request message may include the identifier of PINE. Optionally, the logo of PEGC may also be included.

In this example, PEGC obtains the identification information of PINE through the IKEv2 message between PEGC and PINE, and requests to allocate an IP address for PINE through its own NAS connection.

Through the above steps, PINE successfully connected to 5GC. It can also be considered that the session channel of the PINE is established or the network has successfully allocated resources for the PINE.

The IP address allocation method provided in the embodiment of the present application may be executed by an IP address allocation device. In the embodiment of the present application, the method for allocating the IP address performed by the IP address allocating device is taken as an example to describe the IP address allocating device provided in the embodiment of the present application.

Referring to FIG. 5, an embodiment of the present application provides an IP address allocation device 500, including:

The first sending module 501 is configured for the first terminal to send a first request message to the first network element, where the first request message is used to request to assign an IP address to the second terminal;

A first receiving module 502, configured for the first terminal to receive a first IP address from the first network element, where the first IP address is an IP address assigned to the second terminal;

The second sending module 503 is configured for the first terminal to send a second IP address to the second terminal according to the first IP address;

Optionally, the first terminal is a 3GPP device, the second terminal is a non-3GPP device, and the connection between the first terminal and the second terminal is established through a non-3GPP technology.

an identification of the first terminal;

Personal IoT PIN indication;

Not indicated by 3GPP;

N5CW instruction;

An indication to request an IP address for a terminal that does not support NAS;

Passive IoT indication.

In a possible implementation manner, the first sending module is specifically configured to:

The first terminal sends the first request message to the first network element through a non-access stratum NAS connection with the first network element.

In a possible implementation manner, the first request message carries the identification information of the second terminal, and the apparatus further includes:

An acquiring module, configured for the first terminal to acquire the identification information of the second terminal.

In a possible implementation manner, the acquiring module is specifically configured to:

The first terminal receives a second request message from the second terminal, the second request message carries identification information of the second terminal, and the second request message is used to request to be the second terminal Assign IP addresses.

In a possible implementation manner, the first IP address includes an IPv6 prefix and a local identifier;

Alternatively, the first IP address is an IPv6 prefix, and the second IP address includes the first IP address and a local identifier assigned by the first terminal.

In a possible implementation manner, the first network element is a mobility management function AMF or a session management function SMF.

NAS message;

Protocol data unit PDU session request establishment request message;

PDU session modification request message.

The medium access control MAC address of the second terminal;

a device identifier of the second terminal;

The International Mobile Subscriber Identity IMSI of the second terminal;

the User Permanent Identifier SUPI of said second terminal;

a user concealed identifier SUCI of said second terminal;

The general public user identity GPSI of the second terminal.

In a possible implementation manner, the connection between the first terminal and the second terminal is established through Wi-Fi, Bluetooth or Passive IoT. It is worth noting that when the first terminal and the second terminal establish a connection through the passive Internet of Things, the second terminal can be a 3GPP device or a non-3GPP device, and the passive Internet of Things technology can also be a 3GPP access technology or a non-3GPP access technology. into technology.

Referring to FIG. 6, an embodiment of the present application provides an IP address allocation device 600, including:

The second receiving module 601 is configured for the first network element to receive a first request message from the first terminal, where the first request message is used to request to assign an IP address to the second terminal;

A third sending module 602, configured for the first network element to send the first IP address to the first terminal;

In a possible implementation manner, the IP address allocation device 600 further includes:

An allocation module, configured to allocate a first IP address to the second terminal by the first network element after the first network element receives the first request message from the first terminal;

an identification of the first terminal;

PIN instruction;

Not indicated by 3GPP;

N5CW instruction;

Passive IoT indication.

In a possible implementation manner, the second receiving module is specifically configured to:

The first network element receives the first request message from the first network element through the NAS connection with the first terminal.

In a possible implementation manner, the first network element is prepared as an AMF, and the allocation module is specifically configured to:

The first network element sends a third request message to the SMF, where the third request message is used to request to assign an IP address to the second terminal;

The first network element receives the first IP address from the SMF.

an identification of the first terminal;

PIN instruction;

Not indicated by 3GPP;

N5CW instruction;

Passive IoT indication.

In a possible implementation manner, the first network element is any one of the following:

SMF with PIN capability;

SMF with the ability to assign IP addresses to non-3GPP devices;

The SMF serving the target PDU session, the first request message carries the identifier of the target PDU session.

In a possible implementation manner, the allocation module is specifically used for:

In a possible implementation manner, the device also includes:

In a fourth sending module, the first network element sends the first IP address and a policy control rule to a user plane function UPF, where the policy control rule is used to indicate that the first IP address is forwarded by a target PDU session.

In a possible implementation manner, the device also includes:

A fifth sending module, configured for the first network element to send the first IP address to the AMF.

In a possible implementation manner, the device also includes:

an authentication module, configured for the first network element to trigger an authentication process of the second terminal;

The allocation module is specifically used for:

After the second terminal is successfully authenticated, the first network element allocates a first IP address to the second terminal.

NAS message;

PDU session request establishment request message;

PDU session modification request message.

the MAC address of the second terminal;

a device identifier of the second terminal;

the IMSI of the second terminal;

the SUPI of the second terminal;

the SUCI of the second terminal;

GPSI of the second terminal.

In a possible implementation manner, the second terminal is a personal Internet of Things device.

In a possible implementation manner, the connection between the first terminal and the second terminal is established through WiFi, Bluetooth or Passive IoT. It is worth noting that when the first terminal and the second terminal establish a connection through the passive Internet of Things, the second terminal can be a 3GPP device or a non-3GPP device, and the passive Internet of Things technology can also be a 3GPP access technology or a non-3GPP access technology. into technology.

The IP address allocation apparatus in this embodiment of the present application may be an electronic device, such as an electronic device with an operating system, or a component in the electronic device, such as an integrated circuit or a chip. The electronic device may be a terminal, or other devices other than the terminal. Exemplarily, the terminal may include but not limited to the types of terminal 11 listed above, and other devices may be servers, network attached storage Storage (Network Attached Storage, NAS), etc., which are not specifically limited in this embodiment of the present application.

The IP address allocation device provided by the embodiment of the present application can realize each process realized by the method embodiments in FIG. 2 to FIG. 3 , and achieve the same technical effect. To avoid repetition, details are not repeated here.

Optionally, as shown in FIG. 7 , this embodiment of the present application also provides a communication device 700, including a processor 701 and a memory 702, and the memory 702 stores programs or instructions that can run on the processor 701, for example , when the communication device 700 is a terminal, when the program or instruction is executed by the processor 701, each step of the above IP address allocation method embodiment can be realized, and the same technical effect can be achieved. When the communication device 700 is a network-side device, when the program or instruction is executed by the processor 701, each step of the above-mentioned IP address allocation method embodiment can be achieved, and the same technical effect can be achieved. To avoid repetition, details are not repeated here.

The embodiment of the present application also provides a terminal, including a processor and a communication interface, the communication interface is used for the first terminal to send a first request message to the first network element, and the first request message is used to request to assign an IP address to the second terminal address; the first terminal receives a first IP address from the first network element, and the first IP address is an IP address assigned by the first network element to the second terminal; the first terminal Sending a second IP address to the second terminal according to the first IP address; wherein, the first terminal is a 3GPP device, the second terminal is a non-3GPP device, and the first terminal and the second terminal are connected to each other. The connection between the two terminals is established through a non-3GPP technology. This terminal embodiment corresponds to the above-mentioned terminal-side method embodiment, and each implementation process and implementation mode of the above-mentioned method embodiment can be applied to this terminal embodiment, and can achieve the same technical effect.

Specifically, FIG. 8 is a schematic diagram of a hardware structure of a terminal implementing an embodiment of the present application.

The terminal 800 includes but not limited to: a radio frequency unit 801, a network module 802, an audio output unit 803, an input unit 804, a sensor 805, a display unit 806, a user input unit 807, an interface unit 808, a memory 809, and a processor 810, etc. At least some parts.

Those skilled in the art can understand that the terminal 800 may also include a power supply (such as a battery) for supplying power to various components, and the power supply may be logically connected to the processor 810 through the power management system, so as to manage charging, discharging, and power consumption through the power management system. Management and other functions. The terminal structure shown in FIG. 8 does not constitute a limitation on the terminal, and the terminal may include more or fewer components than those shown in the figure, or Or combine certain components, or arrange different components, which will not be repeated here.

It should be understood that, in the embodiment of the present application, the input unit 804 may include a graphics processing unit (Graphics Processing Unit, GPU) 8041 and a microphone 8042, and the graphics processor 8041 is used in a video capture mode or an image capture mode by an image capture device ( Such as the image data of the still picture or video obtained by the camera) for processing. The display unit 806 may include a display panel 8061, and the display panel 8061 may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like. The user input unit 807 includes at least one of a touch panel 8071 and other input devices 8072 . The touch panel 8071 is also called a touch screen. The touch panel 8071 may include two parts, a touch detection device and a touch controller. Other input devices 8072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, switch buttons, etc.), trackballs, mice, and joysticks, which will not be repeated here.

In the embodiment of the present application, the radio frequency unit 801 may transmit the downlink data from the network side device to the processor 810 for processing after receiving the downlink data; in addition, the radio frequency unit 801 may send uplink data to the network side device. Generally, the radio frequency unit 801 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like.

The memory 809 can be used to store software programs or instructions as well as various data. The memory 809 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, an application program or instructions required by at least one function (such as a sound playing function, image playback function, etc.), etc. Furthermore, memory 809 may include volatile memory or nonvolatile memory, or, memory 809 may include both volatile and nonvolatile memory. Wherein, the non-volatile memory may be a read-only memory (Read-Only Memory, ROM), a programmable read-only memory (Programmable ROM, PROM), an erasable programmable read-only memory (Erasable PROM, EPROM), an electronically programmable Erase Programmable Read-Only Memory (Electrically EPROM, EEPROM) or Flash. Volatile memory can be random access memory (Random Access Memory, RAM), static random access memory (Static RAM, SRAM), dynamic random access memory (Dynamic RAM, DRAM), synchronous dynamic random access memory (Synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (Double Data Rate SDRAM, DDRSDRAM), enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), synchronous connection dynamic random access memory (Synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DRRAM). The memory 809 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.

The processor 810 may include one or more processing units; optionally, the processor 810 integrates an application processor and a modem processor, wherein the application processor mainly processes operations related to the operating system, user interface, and application programs, etc., Modem processors mainly process wireless communication signals, such as baseband processors. It can be understood that the foregoing modem processor may not be integrated into the processor 810 .

A radio frequency unit 801, configured for the first terminal to send a first request message to the first network element, where the first request message is used to request to assign an IP address to the second terminal;

A radio frequency unit 801, configured for the first terminal to receive a first IP address from the first network element, where the first IP address is an IP address allocated for the second terminal;

a radio frequency unit 801, configured for the first terminal to send a second IP address to the second terminal according to the first IP address;

an identification of the first terminal;

Personal IoT PIN indication;

Not indicated by 3GPP;

N5CW instruction;

Passive IoT indication.

In a possible implementation manner, the radio frequency unit 801 is specifically configured to:

In a possible implementation manner, the first request message carries the identification information of the second terminal, and the radio frequency unit 801 is used for the first terminal to obtain the identification information of the second terminal interest.

NAS message;

Protocol data unit PDU session request establishment request message;

PDU session modification request message.

The medium access control MAC address of the second terminal;

a device identifier of the second terminal;

The International Mobile Subscriber Identity IMSI of the second terminal;

the User Permanent Identifier SUPI of said second terminal;

a user concealed identifier SUCI of said second terminal;

The general public user identity GPSI of the second terminal.

In a possible implementation manner, the second terminal is a non-3GPP device or a personal IoT network equipment.

The embodiment of the present application also provides a network side device, including a processor and a communication interface, the communication interface is used for the first network element to receive the first request message from the first terminal, and the first request message is used to request the second The terminal assigns an IP address; the processor is used for the first network element to assign the first IP address to the second terminal; the communication interface is used for the first network element to send the first IP address to the first terminal. The network-side device embodiment corresponds to the above-mentioned network-side device method embodiment, and each implementation process and implementation mode of the above-mentioned method embodiment can be applied to this network-side device embodiment, and can achieve the same technical effect.

Specifically, the embodiment of the present application also provides a network side device. As shown in FIG. 9 , the network side device 900 includes: a processor 901 , a network interface 902 and a memory 903 . Wherein, the network interface 902 is, for example, a common public radio interface (common public radio interface, CPRI).

Specifically, the network-side device 900 in this embodiment of the present invention further includes: instructions or programs stored in the memory 903 and executable on the processor 901, and the processor 901 calls the instructions or programs in the memory 903 to execute the various programs shown in FIG. The method of module execution, and to achieve the same technical effect, in order to avoid repetition, it is not repeated here

The embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored, and when the program or instruction is executed by a processor, each process of the above-mentioned IP address allocation method embodiment is realized, and can achieve The same technical effects are not repeated here to avoid repetition.

Wherein, the processor is the processor in the terminal described in the foregoing embodiments. The readable storage medium includes a computer-readable storage medium, such as a computer read-only memory ROM, a random access memory RAM, a magnetic disk or an optical disk, and the like.

The embodiment of the present application further provides a chip, the chip includes a processor and a communication interface, the The communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned IP address allocation method embodiment, and can achieve the same technical effect. To avoid repetition, details are not repeated here.

It should be understood that the chip mentioned in the embodiment of the present application may also be called a system-on-chip, a system-on-chip, a system-on-a-chip, or a system-on-a-chip.

The embodiment of the present application further provides a computer program/program product, the computer program/program product is stored in a storage medium, and the computer program/program product is executed by at least one processor to implement the implementation of the above IP address allocation method Each process of the example, and can achieve the same technical effect, in order to avoid repetition, will not repeat them here.

It should be noted that, in this document, the term "comprising", "comprising" or any other variation thereof is intended to cover a non-exclusive inclusion such that a process, method, article or apparatus comprising a set of elements includes not only those elements, It also includes other elements not expressly listed, or elements inherent in the process, method, article, or device. Without further limitations, an element defined by the phrase "comprising a ..." does not preclude the presence of additional identical elements in the process, method, article, or apparatus comprising that element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved. Functions are performed, for example, the described methods may be performed in an order different from that described, and various steps may also be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

Through the description of the above embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus a necessary general-purpose hardware platform, and of course also by hardware, but in many cases the former is better implementation. Based on such an understanding, the technical solution of the present application can be embodied in the form of computer software products, which are stored in a storage medium (such as ROM/RAM, magnetic disk, etc.) , CD-ROM), including several instructions to make a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) execute the methods described in the various embodiments of the present application.

The embodiments of the present application have been described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementations. The above-mentioned specific implementations are only illustrative and not restrictive. Those of ordinary skill in the art will Under the inspiration of this application, without departing from the purpose of this application and the scope of protection of the claims, many forms can also be made, all of which belong to the protection of this application.

Claims

A method for assigning an Internet Protocol IP address, comprising:

the first terminal sends a first request message to the first network element, where the first request message is used to request to assign an IP address to the second terminal;

receiving, by the first terminal, a first IP address from the first network element, where the first IP address is an IP address assigned to the second terminal;

The first terminal sends the second IP address to the second terminal according to the first IP address.
The method according to claim 1, wherein the first request message carries one or more of the following:

an identification of the first terminal;

Personal IoT PIN indication;

Non-3rd Generation Partnership Project 3GPP Directive;

There is no 5G capability N5CW indication in the wireless LAN;

An indication of requesting an IP address for a terminal that does not support non-access stratum NAS;

Passive IoT indication.
The method according to claim 1, wherein the first terminal sending the first request message to the first network element includes:

The first terminal sends the first request message to the first network element through the NAS connection with the first network element.
The method according to claim 1, wherein the first request message carries the identification information of the second terminal, the method further comprising:

The first terminal acquires the identification information of the second terminal.
The method according to claim 4, wherein obtaining the identification information of the second terminal by the first terminal comprises:

The first terminal receives a second request message from the second terminal, the second request message carries identification information of the second terminal, and the second request message is used to request to be the second terminal Assign IP addresses.
The method according to claim 1, wherein the second IP address is the same as the first IP address, or the second IP address has a mapping relationship with the first IP address.
The method of claim 6, wherein,

The first IP address includes an IPv6 prefix and a local identifier;

or,

The first IP address is an IPv6 prefix, and the second IP address includes the first IP address and a local identifier assigned by the first terminal.
The method according to claim 1, wherein the first network element is a mobility management function (AMF) or a session management function (SMF).
The method according to claim 1, wherein the first request message includes any of the following:

NAS message;

Protocol data unit PDU session request establishment request message;

PDU session modification request message.
The method according to claim 4, wherein the identification information of the second terminal includes one or more of the following:

The medium access control MAC address of the second terminal;

a device identifier of the second terminal;

The International Mobile Subscriber Identity IMSI of the second terminal;

the User Permanent Identifier SUPI of said second terminal;

a user concealed identifier SUCI of said second terminal;

The general public user identity GPSI of the second terminal.
The method according to claim 1, wherein the first terminal is a personal Internet of Things gateway or a home gateway.
The method according to claim 1, wherein the second terminal is a non-3GPP device or a personal internet of things device.
The method according to claim 1, wherein the first terminal and the second terminal The connection between them is established through wireless fidelity WiFi, Bluetooth or Passive IoT technology.
A method for assigning an IP address, comprising:

receiving, by the first network element, a first request message from the first terminal, where the first request message is used to request allocation of an IP address for the second terminal;

The first network element sends the first IP address to the first terminal.
The method according to claim 14, wherein, after the first network element receives the first request message from the first terminal, the method further comprises:

The first network element allocates a first IP address to the second terminal.
The method according to claim 14, wherein the first request message carries one or more of the following:

an identification of the first terminal;

PIN instruction;

Not indicated by 3GPP;

N5CW instruction;

An indication to request an IP address for a terminal that does not support NAS;

Passive IoT indication.
The method according to claim 14, wherein the first network element receiving the first request message from the first terminal comprises:

The first network element receives the first request message from the first network element through the NAS connection with the first terminal.
The method according to claim 14, wherein the first request message carries identification information of the second terminal.
The method according to claim 15, wherein the first network element is an AMF, and the first network element allocates a first IP address to the second terminal, comprising:

The first network element sends a third request message to the SMF, where the third request message is used to request to assign an IP address to the second terminal;

The first network element receives the first IP address from the SMF.
The method according to claim 19, wherein the third request message carries one or more of the following:

an identification of the first terminal;

PIN instruction;

Not indicated by 3GPP;

N5CW instruction;

An indication to request an IP address for a terminal that does not support NAS;

Passive IoT indication.
The method according to claim 15, wherein the first network element is any one of the following:

SMF with PIN capability;

SMF with the ability to assign IP addresses to non-3GPP devices;

The SMF serving the target PDU session, the first request message carries the identifier of the target PDU session.
The method according to claim 21, wherein the first network element assigning the first IP address to the second terminal comprises:

The first network element allocates the first IP address to the second terminal according to the subscription data of the first terminal and/or operator configuration.
The method according to claim 21, wherein said method further comprises:

The first network element sends the first IP address and a policy control rule to a user plane function UPF, where the policy control rule is used to indicate that the first IP address is forwarded by a target PDU session.
The method according to claim 21, wherein said method further comprises:

The first network element sends the first IP address to the AMF.
The method according to claim 21, wherein said method further comprises:

The first network element triggers an authentication process of the second terminal;

The first network element assigning the first IP address to the second terminal includes:

After the second terminal is successfully authenticated, the first network element allocates a first IP address to the second terminal.
The method according to claim 14, wherein the first request message includes any of the following:

NAS message;

PDU session request establishment request message;

PDU session modification request message.
The method according to claim 18, wherein the identification information of the second terminal includes one or more of the following:

the MAC address of the second terminal;

a device identifier of the second terminal;

the IMSI of the second terminal;

the SUPI of the second terminal;

the SUCI of the second terminal;

GPSI of the second terminal.
The method according to claim 14, wherein the first terminal is a personal IoT gateway or a home gateway.
The method according to claim 14, wherein the second terminal is a non-3GPP device or a personal internet of things device.
The method according to claim 14, wherein the connection between the first terminal and the second terminal is established through WiFi, Bluetooth or Passive IoT technology.
A device for assigning an IP address, comprising:

A first sending module, configured for the first terminal to send a first request message to the first network element, where the first request message is used to request to assign an IP address to the second terminal;

A first receiving module, configured for the first terminal to receive a first IP address from the first network element, where the first IP address is an IP address assigned to the second terminal;

The second sending module is configured for the first terminal to send a second IP address to the second terminal according to the first IP address.
A device for assigning an IP address, comprising:

A second receiving module, configured for the first network element to receive a first request message from the first terminal, where the first request message is used to request to assign an IP address to the second terminal;

A third sending module, configured for the first network element to send the first IP address to the first terminal.
A terminal, including a processor and a memory, the memory stores programs or instructions that can run on the processor, and when the programs or instructions are executed by the processor, the process described in any one of claims 1 to 13 is implemented. The steps of the IP address allocation method described above.
A network side device, comprising a processor and a memory, the memory stores programs or instructions that can run on the processor, and when the programs or instructions are executed by the processor, any one of claims 14 to 29 can be implemented. The steps of the IP address allocation method described in item.
A readable storage medium, on which a program or instruction is stored, and when the program or instruction is executed by a processor, the method for assigning an IP address as claimed in any one of claims 1 to 13 is realized, or the method as described in The steps of the IP address allocation method described in any one of claims 14 to 30.