WO2024086996A1

WO2024086996A1 - Address allocation method and device

Info

Publication number: WO2024086996A1
Application number: PCT/CN2022/127158
Authority: WO
Inventors: 郭伯仁; 郭雅莉
Original assignee: Oppo广东移动通信有限公司
Priority date: 2022-10-24
Filing date: 2022-10-24
Publication date: 2024-05-02

Abstract

Embodiments of the present application provide an address allocation method and a device. The address allocation method comprises: a first device receives an address set, the address set being used for allocating an address for a first terminal device associated with the first device. According to the embodiments of the present application, an address can be allocated for a device accessing a communication network.

Description

Address allocation method and device

Technical Field

The present application relates to the field of communications, and more specifically, to an address allocation method and device.

Background technique

When a terminal accesses the network, it may access through other terminals in some cases. For example, a device that cannot directly access the 5G core network (5GC) accesses the 5G Core through the 3rd Generation Partnership Project (3GPP) user equipment (UE). In this scenario, how to assign an address to the device is a technical problem that needs to be solved.

Summary of the invention

The embodiments of the present application provide an address allocation method and device, which can allocate addresses to devices accessing a communication network.

The present application provides an address allocation method, including:

The first device receives an address set, where the address set is used to allocate an address to a first terminal device associated with the first device.

The present application provides an address allocation method, including:

The first network device determines an address set, and the address set is used to allocate an address to a first terminal device associated with the first device.

The present application provides an address allocation method, including:

The server device receives a second address request from the first device;

The server device allocates an address to the first terminal device associated with the first device according to the second address request.

The present application provides an address allocation method, including:

The third network device determines an address set, where the address set is used to allocate an address to a first terminal device associated with the first device.

The present application embodiment provides a first device, including:

The first receiving module is used to receive an address set, where the address set is used to allocate an address to a first terminal device associated with the first device.

An embodiment of the present application provides a first network device, including:

The first determination module is used to determine an address set, where the address set is used to allocate an address to a first terminal device associated with the first device.

The present application provides a server device, including:

A third receiving module, configured to receive a second address request from the first device;

The allocation module is used to allocate an address to a first terminal device associated with the first device according to the second address request.

The embodiment of the present application provides a third network device, including:

The second determination module is used to determine an address set, where the address set is used to allocate an address to a first terminal device associated with the first device.

An embodiment of the present application provides a communication device, including: a processor and a memory, the memory is used to store a computer program, the processor is used to call and run the computer program stored in the memory, and execute any address allocation method as in the embodiments of the present application.

An embodiment of the present application provides a chip, including: a processor, used to call and run a computer program from a memory, so that a device equipped with the chip executes any address allocation method as in the embodiments of the present application.

An embodiment of the present application provides a computer-readable storage medium for storing a computer program, wherein the computer program enables a computer to execute any address allocation method as described in the embodiments of the present application.

An embodiment of the present application provides a computer program product, including computer program instructions, which enable a computer to execute any address allocation method as described in the embodiments of the present application.

An embodiment of the present application provides a computer program, which enables a computer to execute any address allocation method as described in the embodiments of the present application.

In the embodiment of the present application, by the first device receiving an address set for allocating an address to the first terminal device, it is possible to allocate an address to the first terminal device associated with the first device.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic diagram of application scenario 1 of an embodiment of the present application.

FIG. 2 is a schematic diagram of application scenario 2 of an embodiment of the present application.

3A-3C are schematic diagrams showing three modes of communication between PINEs.

FIG. 4 is a schematic diagram of a frame routing address configuration method.

FIG5 is a schematic flowchart of an address allocation method 500 according to an embodiment of the present application.

FIG. 6 is a schematic flowchart of an address allocation method 600 according to an embodiment of the present application.

FIG. 7 is a schematic flowchart of a second address allocation method 700 according to an embodiment of the present application.

FIG. 8 is a schematic flowchart of a third address allocation method 800 according to an embodiment of the present application.

FIG9 is an implementation flowchart according to the first embodiment of the present application.

FIG. 10 is an implementation flowchart according to the second embodiment of the present application.

FIG. 11 is an implementation flowchart according to the third embodiment of the present application.

FIG12 is an implementation flowchart according to the fourth embodiment of the present application.

FIG. 13 is a schematic flowchart of an address allocation method 1300 according to an embodiment of the present application.

FIG. 14 is a schematic flowchart of an address allocation method 1400 according to an embodiment of the present application.

FIG. 15 is a schematic flowchart of an address allocation method 1500 according to an embodiment of the present application.

FIG. 16 is a schematic structural diagram of a first device 1600 according to an embodiment of the present application.

FIG. 17 is a schematic diagram of the structure of a first device 1700 according to an embodiment of the present application.

FIG. 18 is a schematic diagram of the structure of a first network device 1800 according to an embodiment of the present application.

FIG. 19 is a schematic diagram of the structure of a first network device 1900 according to an embodiment of the present application.

FIG. 20 is a schematic diagram of the structure of a server device 2000 according to an embodiment of the present application.

FIG. 21 is a schematic diagram of the structure of a server device 2100 according to an embodiment of the present application.

Figure 22 is a schematic diagram of the structure of a third network device 2200 according to an embodiment of the present application.

FIG. 23 is a schematic diagram of the structure of a third network device 2300 according to an embodiment of the present application.

FIG. 24 is a schematic structural diagram of a communication device 2400 according to an embodiment of the present application.

FIG. 25 is a schematic structural diagram of a chip 2500 according to an embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application.

It should be noted that the terms "first", "second", etc. in the description and claims of the embodiments of the present application and the above drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. The objects described by the "first" and "second" described at the same time may be the same or different.

The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Global System of Mobile communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, Advanced long term evolution (LTE-A) system, New Radio (NR) system, and NR system. Evolved systems, LTE-based access to unlicensed spectrum (LTE-U) systems, NR-based access to unlicensed spectrum (NR-U) systems, non-terrestrial communication networks (NTN) systems, universal mobile communication systems (UMTS), wireless local area networks (WLAN), wireless fidelity (WiFi), fifth-generation communication (5th-Generation, 5G) systems or other communication systems, etc.

Generally speaking, traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communications, but will also support, for example, device to device (Device to Device, D2D) communication, machine to machine (Machine to Machine, M2M) communication, machine type communication (Machine Type Communication, MTC), vehicle to vehicle (V2V) communication, or vehicle to everything (V2X) communication, etc. The embodiments of the present application can also be applied to these communication systems.

In one implementation, the communication system in the embodiment of the present application can be applied to a carrier aggregation (CA) scenario, a dual connectivity (DC) scenario, or a standalone (SA) networking scenario.

In one embodiment, the communication system in the embodiment of the present application can be applied to an unlicensed spectrum, wherein the unlicensed spectrum can also be considered as a shared spectrum; or, the communication system in the embodiment of the present application can also be applied to an authorized spectrum, wherein the authorized spectrum can also be considered as an unshared spectrum.

The embodiments of the present application describe various embodiments in conjunction with network equipment and terminal equipment, wherein the terminal equipment may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent or user device, etc.

The terminal device can be a station (STAION, ST) in a WLAN, a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA) device, a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in the next generation communication system such as the NR network, or a terminal device in the future evolved Public Land Mobile Network (PLMN) network, etc.

In the embodiments of the present application, the terminal device can be deployed on land, including indoors or outdoors, handheld, wearable or vehicle-mounted; it can also be deployed on the water surface (such as ships, etc.); it can also be deployed in the air (for example, on airplanes, balloons and satellites, etc.).

In the embodiments of the present application, the terminal device may be a mobile phone, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical, a wireless terminal device in smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, or a wireless terminal device in a smart home, etc.

As an example but not limitation, in the embodiments of the present application, the terminal device may also be a wearable device. Wearable devices may also be referred to as wearable smart devices, which are a general term for wearable devices that are intelligently designed and developed using wearable technology for daily wear, such as glasses, gloves, watches, clothing, and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also powerful functions achieved through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include full-featured, large-sized, and fully or partially independent of smartphones, such as smart watches or smart glasses, as well as devices that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various types of smart bracelets and smart jewelry for vital sign monitoring.

In an embodiment of the present application, the network device may be a device for communicating with a mobile device. The network device may be an access point (AP) in WLAN, a base station (BTS) in GSM or CDMA, a base station (NodeB, NB) in WCDMA, an evolved base station (Evolutional Node B, eNB or eNodeB) in LTE, or a relay station or access point, or a vehicle-mounted device, a wearable device, a network device (gNB) in an NR network, or a network device in a future evolved PLMN network, or a network device in an NTN network, etc.

As an example but not limitation, in an embodiment of the present application, the network device may have a mobile feature, for example, the network device may be a mobile device. Optionally, the network device may be a satellite or a balloon station. For example, the satellite may be a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, a high elliptical orbit (HEO) satellite, etc. Optionally, the network device may also be a base station set up in a location such as land or water.

In an embodiment of the present application, a network device can provide services for a cell, and a terminal device communicates with the network device through transmission resources used by the cell (for example, frequency domain resources, or spectrum resources). The cell can be a cell corresponding to a network device (for example, a base station), and the cell can belong to a macro base station or a base station corresponding to a small cell. The small cells here may include: metro cells, micro cells, pico cells, femto cells, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.

Fig. 1 exemplarily shows a communication system 100. The communication system includes a network device 110 and two terminal devices 120. In one embodiment, the communication system 100 may include multiple network devices 110, and each network device 110 may include other number of terminal devices 120 within its coverage area, which is not limited in the embodiment of the present application.

In one implementation, the communication system 100 may also include other network entities such as a Mobility Management Entity (MME) and an Access and Mobility Management Function (AMF), but this is not limited to the embodiments of the present application.

Among them, the network equipment may include access network equipment and core network equipment. That is, the wireless communication system also includes multiple core networks for communicating with the access network equipment. The access network equipment may be an evolutionary base station (evolutional node B, referred to as eNB or e-NodeB) macro base station, micro base station (also called "small base station"), pico base station, access point (AP), transmission point (TP) or new generation Node B (gNodeB) in a long-term evolution (LTE) system, a next-generation (mobile communication system) (next radio, NR) system or an authorized auxiliary access long-term evolution (LAA-LTE) system.

It should be understood that the device with communication function in the network/system in the embodiment of the present application can be called a communication device. Taking the communication system shown in Figure 1 as an example, the communication device may include a network device and a terminal device with communication function, and the network device and the terminal device may be specific devices in the embodiment of the present application, which will not be repeated here; the communication device may also include other devices in the communication system, such as other network entities such as a network controller and a mobile management entity, which is not limited in the embodiment of the present application.

It should be understood that the terms "system" and "network" are often used interchangeably in this article. The term "and/or" in this article is only a description of the association relationship of associated objects, indicating that there can be three relationships. For example, A and/or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character "/" in this article generally indicates that the associated objects before and after are in an "or" relationship.

It should be understood that the "indication" mentioned in the embodiments of the present application can be a direct indication, an indirect indication, or an indication of an association relationship. For example, A indicates B, which can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association relationship between A and B.

In the description of the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between two items, or an association relationship between the two items, or a relationship of indication and being indicated, configuration and being configured, etc.

To facilitate understanding of the technical solutions of the embodiments of the present application, the relevant technologies of the embodiments of the present application are described below. The following related technologies can be arbitrarily combined with the technical solutions of the embodiments of the present application as optional solutions, and they all belong to the protection scope of the embodiments of the present application.

When a terminal accesses the network, it will access through other terminals in some cases. For example, a device that cannot directly access the 5G core network (5GC) accesses the 5GC through the third generation partnership project 3GPP UE. Taking the personal Internet of Things (PIN) scenario as an example, a personal IoT device (PINE, PIN Element) can access the 5G system (5GS, 5G System) through a personal IoT device with gateway capability (PEGC, PIN Element with Gateway Capability) or an IoT device with management capability (PEMC, PIN Element with Management Capability). IoT devices can be divided into wearable devices (such as cameras, headphones, watches, earphones, health monitors), home life devices (such as smart lights, cameras, thermostats, door sensors, voice assistants, speakers, refrigerators, washing machines, lawn mowers, robots), and office or factory equipment (such as printers, meters, sensors). Users can use these IoT devices to create (e.g., plan, change topology) personal networks in their homes, offices, factories, or around their bodies.

Currently, some wearable devices and other types of IoT devices can only access the Internet through relay devices and gateways or access the mobile network through mobile phones. In both cases, the mobile core network cannot realize that the IoT device is connected to the mobile network. However, in order to fully utilize the 5G system to assist in the management and business support of IoT devices, it is essential to enable the 5G system to participate in the personal IoT.

As shown in Figure 2, the personal Internet of Things (PIN) created by the user consists of three types of devices: ordinary personal Internet of Things devices (PINE), personal Internet of Things devices with gateway capabilities (PEGC), and Internet of Things devices with management capabilities (PEMC). Among them, the general PINE has basic communication capabilities and can communicate with each other directly through WiFi, Bluetooth, etc. or through PEGC. PEGC and PEMC have the ability to access the 5G system and can use the 5G system to provide data forwarding services and management services for other PINEs.

FIG3A-3C are schematic diagrams showing three modes of communication between PINEs. FIG3A is a mode 1 for communication between PINEs, in which PINEs are directly connected to each other; as shown in FIG3A , PINE 1 and PINE 2 directly exchange data through communication technologies such as WiFi and Bluetooth. FIG3B is a mode 2 for communication between PINEs, in which data is forwarded between PINEs via PEGC; as shown in FIG3B , PINE 1 and PINE 2 are connected to the same PEGC via communication technologies such as WiFi or Bluetooth, and PEGC provides data forwarding services for them. FIG3C is a mode 3 for communication between PINEs, in which data is forwarded between PINEs via 5GS; as shown in FIG3C , data can be forwarded between PINE 1 and PINE 2 via 5GS. For example, when the PDU session created by PEGC for PINE 1 and PINE 2 is connected to the same user plane function (UPF), data can be forwarded through the UPF. When the PDU session established by PEGC for PINE is connected to different UPFs, data can be forwarded through the N19 interface between UPFs. In addition, data can also be forwarded through the interface N6 between UPF and the data network.

As shown in Figure 4, when the existing PINE device accesses the 5G network through PEGC, the 5GC uses framed routing to assign IP addresses to the PINE connected to the PEGC. The 5G network supports frame routing only for PDU session definitions of IP types (IPv4, IPv6, IPv4v6) and allows support for IP networks behind PEGC, so a range of IPv4 addresses or IPv6 prefixes can be accessed in a single PDU session.

A PDU session can be associated with multiple frame routes. Each frame route refers to a series of IPv4 addresses (i.e., IPv4 address and IPv4 address mask) or a series of IPv6 prefixes (i.e., IPv6 prefix and IPv6 prefix length). One or a group of frame routes associated with a PDU session is included in the routing information. 5GC does not send frame routing information to PEGC, but sends the IP address to the PINE connected to PEGC through a specific application layer method.

The frame routing information is provided to the PSAUPF by the Session Management Function (SMF) as part of the packet detection rules associated with the network-side N6 interface of the UPF. The SMF can obtain the frame routing information from the Data Network (DN)-Authentication Authorization Accounting (AAA) server during the secondary authentication and authorization process or by consulting the session management contract message in the UDM.

The IP address allocated by 5GC to PEGC during the PDU session establishment process can be an address in the frame routing information or an IP address outside the frame routing information.

If the Unified Data Management (UDM) or DN-AAA updates the frame routing information during the life cycle of the PDU session, the SMF releases the PDU session and can include an indication in the release request to allow the UE to re-establish the PDU session. The topology information of the PIN network is often flexible and changeable, and the association between PEGC and PINE is often dynamically changing. The frame routing information in 5GC is often static address information and will not be sent to PEGC. As shown in Figure 4, the IP gateway (IP-gateway) in the frame routing information is an address statically assigned to PEGC, while IP-a and IP-b are static addresses assigned to PINE-a and PINE-b. When a new PINE-c needs to access 5GC through PEGC, if there is no frame routing information corresponding to PINE-c in the network, an IP address cannot be assigned to it. Even if the frame routing information in UDM and DN-AAA can be updated through application layer interaction, PEGC needs to release the existing PDU session and establish a new PDU session based on the new frame routing information, which will seriously affect the service quality of PINE-a and PINE-b, and PINE-c needs to wait for the update of the frame routing information.

The embodiment of the present application proposes an address allocation method, which can be applied to PIN networks, and can also be applied to other scenarios where devices that cannot directly access 5GC apply for addresses through 3GPP UE. The address allocated in the embodiment of the present application can be an IPv4 address and/or an IPv6 prefix.

Fig. 5 is a schematic flow chart of an address allocation method 500 according to an embodiment of the present application, which can be applied to any system shown in Figs. 1-4, but is not limited thereto. The method includes at least part of the following contents.

S510: The first device receives an address set, where the address set is used to allocate an address to a first terminal device associated with the first device.

The first terminal device accesses the network through the first device, that is, the first device is associated with the first terminal device. After receiving the address set, the first device can select an address from the address set and assign the selected address to the first terminal device associated with the first device, thereby allocating an address to the first terminal device.

After allocating an address to the second network device, the first device can send the address to the first terminal device. In this way, when the first device needs to access the network, it can use the address to access without waiting for the frame routing information to be updated.

Among them, the address set can be determined by the first network device. That is, the first network device determines an address set, and the address set is used to assign an address to the first terminal device associated with the first device. In this way, even if the association relationship between the first terminal device and the first device changes, as long as the address assigned by the first device to the first terminal device is selected from the address set, there is no need to re-establish the session process. For example, when a new first terminal device is connected to the first device and an IP address needs to be assigned to it by the first device, the first device can select an unused address from the address set assigned by the first network device or reuse the address of the disconnected first terminal device.

The first device may carry first indication information, and the first indication information is used to request to obtain an address set; the first indication information may be sent directly to the first network device, or forwarded to the first network device by an intermediate device; after receiving the first indication information, the first network device determines the address set, and sends the address set directly to the first device, or forwards it to the first device by the intermediate device; the first device then selects an address from the address set and assigns the address to the first terminal device. In this case, the first device acts as a DHCP server to perform address allocation. The first network device may include one or more of SMF, UPF, and AMF. Alternatively, the first device may send a first indication information to a PEGC or PEMC; based on the first indication information, the PEGC or PEMC may determine the address set, or obtain the address set from other network elements, and send the address set to the first device; the first device then selects an address from the address set and assigns the address to the first terminal device.

In some other embodiments, the first device sends a first address request, which carries an identifier of the first terminal device and is used to request an address to be allocated to the first terminal device; the first address request can be sent directly to the first network device, or forwarded to the first network device by an intermediate device. The first network device may include one or more of SMF, UPF, and AMF. The first network device may select an address allocated to the first terminal device from a determined address set and send the address. In this case, the first network device acts as a DHCP server to allocate addresses.

In other implementations, the first device sends a first address request to a server device (or an application server, a data network (DN), an application function (AF), etc.), where the first address request carries an identifier of the first terminal device and is used to request address allocation for the first terminal device; the server device allocates an address to the first terminal device. In this case, the server device acts as a Dynamic Host Configuration Protocol (DHCP) server to perform address allocation.

In the above-mentioned cases, the address set can be represented by frame routing information, IPv4 address and subnet mask, IPv6 address and IPv6 prefix, etc. Among them, the IPv6 prefix can also be called the IPv6 prefix length. The address set represented by the frame routing information can be a continuous address segment or multiple scattered addresses.

The first device may be a PEGC, and the first terminal device may be a PINE. The first network device may be an SMF, a UPF, or other network elements. Taking the address allocation of a PINE associated with a PEGC as an example, the address allocation method proposed in this embodiment includes at least the following three methods:

1. PEGC acts as a DHCP server. This method has at least the following two situations:

Case 1: Expanding the existing frame routing method, 5GC no longer allocates addresses for each PINE, but sends frame routing information to PEGC, which dynamically selects a suitable IP address from the frame routing information and allocates it to the PEGC associated with it based on the current PINE-PEGC association relationship.

In case 2, 5GC allocates an IP address set to PEGC, and PEGC can dynamically select an IP address from the allocated IP address set to allocate to the PINE associated with it. Specifically, SMF can allocate an IPv4 mask or IPv6 prefix to PEGC, and set the IPv4 mask/IPv6 prefix as the destination address in the PDR.

2. SMF and other 5GC network elements act as DHCP servers to dynamically allocate IP addresses for PINE.

3. The server device outside the core network acts as a DHCP server. After PGEC establishes a PDU session, it interacts with the DHCP server outside the core network through the data plane to obtain the IP address of PINE.

FIG6 is a schematic flow chart of an address allocation method 600 according to an embodiment of the present application, including:

S610. The first device (such as PEGC) sends first indication information, and the first indication information is used to request to obtain an address set. The first indication information can be sent to the first network device directly or via other devices, and the first network device can include one or more of SMF, UPF, and AMF. The first indication information can be sent via a NAS message, such as the first device sends a NAS message, and the NAS message carries the first indication information. The NAS message also carries at least one of the identifier of the first device (such as PEGC ID), the identifier of the network to which the first device and the first terminal device (such as PINE) belong (PIN ID), and the number of addresses requested to be obtained.

S620: The first network device determines an address set, where the address set is used to allocate an address to a first terminal device associated with the first device.

The address set may be represented by frame routing information or by an IP address segment.

Specifically, the first network device may determine frame routing information, which includes an address set. The frame routing information may also include an address of the first device, so as to allocate an address to the first device.

The first network device may determine the frame routing information in at least one of the following ways:

Obtain frame routing information by searching for contract information;

Obtain frame routing information from the DN-AAA server;

Generate frame routing information;

Frame routing information is obtained from the second network device.

Therefore, the first network device can solve the frame routing acquisition method in the related art, and can also adopt a new frame routing acquisition method to acquire frame routing information that can contain an address set.

Among them, the second network device can be a network element such as UPF.

Alternatively, the first network device may determine an IPv4 address and a subnet mask, where the IPv4 address and the subnet mask are used to represent an address set; and/or,

The first network device may determine an IPv6 address and a prefix, where the IPv6 address and the prefix are used to represent a set of addresses.

The first network device may determine the address set in at least one of the following ways:

Acquire the address set by searching the contract information;

Acquire the address set from the DN-AAA server;

Assign address set;

A set of addresses is obtained from a second network device.

Among them, the second network device can be a network element such as UPF.

S630. The first network device adds the address set to the packet detection rule (PDR) corresponding to the session (such as the protocol data unit (PDU) session) that the first device requests to establish or modify, and provides the PDR to the second network device.

S640: The first network device sends the address set.

For example, the first network device sends a Namf_Communication_N1N2MessageTransfer message, and the Namf_Communication_N1N2MessageTransfer message carries an address set. The Namf_Communication_N1N2MessageTransfer message may also carry at least one of an identifier of the first device (such as PEGC ID), an address of the first device (such as PEGC IP), an identifier of the first terminal device (such as PINE ID), and an identifier of the network to which the first device and the first terminal device belong (such as PIN ID). The message carrying the address set may be sent to other network elements (such as AMF), and the other network elements (such as AMF) send the address set to the first device. When the first network device sends the address set, it synchronously sends the aforementioned addresses and/or identification information, which can facilitate the first device that receives the address set to distinguish the address set and avoid address allocation errors caused by errors in the message transmission process.

The first device receives the address set, and the address set is used to allocate an address to the first terminal device associated with the first device. For example, the first device receives a NAS message, and the NAS message carries the address set. The NAS message may also carry at least one of an identifier of the first device (such as PEGC ID), an address of the first device (such as PEGC IP), an identifier of the first terminal device (such as PINE ID), and an identifier of the network to which the first device and the first terminal device belong (such as PIN ID).

S660: The first device allocates an address to a first terminal device associated with the first device from the received address set. For example, after receiving an address request from the first terminal device, an address is selected from the address set and the selected address is distributed to the first terminal device. The step of receiving an address request from the first terminal device may be performed before obtaining the address set or after obtaining the address set.

In this example, the first device acts as a DHCP server to allocate an address to the first terminal device.

FIG. 7 is a schematic flow chart of a second address allocation method 700 according to an embodiment of the present application, including:

S710. The first network device (such as a network element such as SMF or UPF) configures an address set in the PDR corresponding to the session (such as a PDU session) established by the first device (such as PEGC). Specifically, the first network device may configure frame routing information for the first device, the frame routing information includes the address set, and the frame routing information may also include the address of the first device; or, the first network device may configure an IP address segment for the first device, such as configuring an IPv4 address and a subnet mask, the IPv4 address and the subnet mask are used to represent the address set; and/or, configuring an IPv6 address and a prefix, the IPv6 address and the prefix are used to represent the address set. The IPv4 address or the IPv6 address may also represent the address of the first device.

S720. The first network device receives a first address request, and the first address request carries an identifier of the first terminal device (such as a PINE ID). The first address request may be sent directly by the first device to the first network device, or forwarded to the first network device via other network elements. This step may also be performed before step S710. The first address request may also carry at least one of an identifier of the first device (such as a PEGC ID), an address of the first device (such as a PEGC IP), and an identifier of the network to which the first device and the first terminal device belong (such as a PIN ID).

S730. The first network device selects an address assigned to the first terminal device from the address set and sends the address. The first network device may send the address directly to the first device, or forward it to the first device via other network elements. When sending the address, the first network device may also send at least one of the identifier of the first terminal device (such as PINE ID), the identifier of the first device (such as PEGC ID), the address of the first device (such as PEGC IP), and the identifier of the network to which the first device and the first terminal device belong (such as PIN ID).

In this example, the first network device acts as a DHCP server to allocate an address to the first terminal device. In this example, the network device acts as a DHCP server to allocate addresses, which can reduce the requirements on the terminal device functions and reduce the burden on the terminal device.

FIG8 is a schematic flow chart of a third address allocation method 800 according to an embodiment of the present application, including:

S810. A server device (such as a DN, AF or application server) receives a second address request from a first device; the second address request carries an identifier of the first terminal device (such as a PINE ID). The second address request may be sent directly by the first device to the server device, or forwarded to the server device via other network elements. The second address request may also carry at least one of an identifier of the first device (such as a PEGC ID), an address of the first device (such as a PEGC IP), and an identifier of a network to which the first device and the first terminal device belong (such as a PIN ID).

S820. The server device allocates an address to the first terminal device associated with the first device according to the second address request. Furthermore, the server device may also record the routing relationship between the address of the first device and the address of the first terminal device. Later, when data needs to be sent to the first terminal device, the server device may send the data to the first device that has a routing relationship with the first terminal device according to the routing relationship, and include the routing relationship in the data to indicate to which first terminal device the first device should send the data.

S830: The server device sends the address allocated to the first terminal device to the first device. The first device may then send the address to the first terminal device.

In this example, the server device acts as a DHCP server to allocate an address to the first terminal device.

The following takes the first device being PEGC, the first terminal device being PINE, and the first network device being SMF as an example, and describes in detail the address allocation method of the present application with reference to a specific embodiment.

Embodiment 1:

FIG9 is a flowchart of the implementation of the first embodiment of the present application. In the first embodiment, the 5GC configures the frame routing information for the PEGC. The address of the frame routing information is no longer fixedly assigned by the 5GC to the PINE behind the PEGC, but is dynamically assigned by the PEGC to the PIEN connected to it. The specific process is as follows:

1.PINE is connected to PEGC, and needs to interact with 5GC through PEGC and send an IP address allocation request to PEGC, which contains PINE ID and PIN ID. The IP address allocation request message can be sent to PEGC through the PIN protocol stack or application layer. The IP address can be an IPv4 address and/or an IPv6 prefix.

2. PEGC sends PEGC indication information (PEGC indication) to AMF to inform 5GC that it is PEGC and needs to obtain a set of IP addresses. The PEGC indication information can be sent to AMF via NAS messages. Specifically, PEGC initiates the PDU session establishment or modification process, and includes fields such as PEGC indication, PEGC ID, PIN ID, and the number of IP addresses requested to be allocated in the PDU session establishment/modification request message to inform 5GC that it is PEGC and needs to allocate addresses to the devices behind it.

3.AMF forwards the PEGC indication to SMF; in addition to the PEGC indication, AMF can also forward the PEGC ID, PIN ID, and the number of IP addresses requested to be allocated to SMF. The PEGC indication, PEGC ID, PIN ID, and the number of IP addresses requested to be allocated can be carried in the Nsmf_PDUSession_CreateSMContext Request message.

4. SMF obtains the frame routing information of PEGC. The frame routing information can be obtained by consulting the contract message in the UDM, or obtained from the DN-AAA server through the secondary authentication process, or generated locally by the SMF, or obtained from the UPF. Specifically, the frame routing information contains the address of the PEGC, and an address set, which contains a certain number of IP addresses. These IP addresses can be a set consisting of continuous IP address segments or a set of discontinuous IP addresses. The IP address assigned to PEGC can be an address in the address set or an IP address that does not belong to the address set.

5.SMF configures the packet detection rule (PDR) for the PDU session established or modified by PEGC, that is, adds the frame routing information to the PDR corresponding to the PDU session, and provides the PDR to UPF.

6.SMF sends the frame routing information corresponding to the PEGC to AMF. The frame routing information can be carried by the Namf_Communication_N1N2MessageTransfer message. In addition, the message may also contain PEGC ID, PEGC IP address, and PIN ID.

7.AMF sends the frame routing information to PEGC. The frame routing information can be carried by the N2NAS message. In addition, the message may also contain PEGC ID, PEGC IP address, PINE ID, PIN ID.

8. PEGC can select an available address from the IP address set in the frame routing information and dynamically assign it to the PINE associated with it.

In this embodiment, the PEGC acts as a DHCP server to allocate addresses to the PINE associated with it; the address set obtained by the PEGC is represented by frame routing.

Embodiment 2:

FIG10 is a flowchart of the implementation of the second embodiment of the present application. In the second embodiment, the 5GC allocates an IP address segment to the PEGC, and the IP address segment is an IPv4 address and subnet mask and/or an IPv6 address and prefix length. The PEGC selects an IP address from the obtained IP address segment and allocates it to the PINE associated with it. The specific process is as follows:

3.AMF forwards the PEGC indication, PEGC ID, PIN ID, and the number of IP addresses requested to be allocated to SMF. The PEGC indication, PEGC ID, PIN ID, and the number of IP addresses requested to be allocated can be carried in the Nsmf_PDUSession_CreateSMContext Request message.

4. SMF obtains the frame routing information of PEGC to obtain the address set (or address segment), which can be represented by the IPv4 address and subnet mask, and/or the IPv6 address and prefix length. The IPv4 address and subnet mask, and/or the IPv6 address and prefix length can be obtained in at least four ways:

a.SMF consults the contract information in UDM to obtain the IPv4 address and subnet mask, and/or the IPv6 address and prefix length.

b.SMF obtains the IPv4 address and subnet mask, and/or the IPv6 address and prefix length from the DN-AAA server.

c.SMF allocates IPv4 addresses and subnet masks, and/or IPv6 addresses and prefix lengths on its own.

d.SMF instructs UPF to generate an IPv4 address and subnet mask, and/or an IPv6 address and prefix length; and obtains the IPv4 address and subnet mask, and/or an IPv6 address and prefix length from UPF.

5.SMF configures packet detection rules (PDR) for the PDU session that PEGC requests to establish or modify, that is, uses the IPv4 address and subnet mask, and/or IPv6 address and prefix length to configure the IP packet filter settings (IP Packet Filter Set) in the PDR corresponding to the above PDU session, and provides the PDR to UPF.

6.SMF sends the IP address set (i.e., IPv4 address and subnet mask and/or IPv6 address and prefix length) to AMF. The IP address set can be carried by the Namf_Communication_N1N2MessageTransfer message. In addition, the message may also contain PEGC ID, PEGC IP address, PINE ID, and PIN ID.

7.AMF sends the IP address set (i.e., IPv4 address and subnet mask and/or IPv6 address and prefix length) to PEGC. The IP address set can be carried by the N2NAS message. In addition, the message may also contain PEGC ID, PEGC IP address, PINE ID, and PIN ID.

8. The PEGC may select an available IP address from the IP address set and dynamically assign it to the PINE associated with it.

This embodiment is similar to the first embodiment, in which PEGC acts as a DHCP server to allocate addresses to the PINE associated therewith; the difference is that the address set obtained by PEGC is represented by an IPv4 address and subnet mask, and/or an IPv6 address and prefix length.

Embodiment three:

Figure 11 is a flowchart of the implementation of Example 3 of the present application. In Example 3, SMF acts as a DHCP server to allocate an IP address to PINE. After PEGC establishes a PDU session, SMF configures frame routing information or an IP address segment for the PDU session as part of the PDR. Subsequently, whenever a new PINE requests an IP address from 5GC through PEGC, SMF can select an IP address from the frame routing information or the above IP address segment and allocate it to PINE. The specific process is as follows:

1. After PEGC establishes a PDU session, SMF configures frame routing information or an IP address segment for the PDU session as part of the PDR.

2. PINE is connected to PEGC, and needs to interact with 5GC through PEGC and send an IP address allocation request to PEGC, which contains PINE ID and PIN ID. The IP address allocation request message can be sent to PEGC through the PIN protocol stack or application layer. The IP address can be an IPv4 address and/or an IPv6 prefix. This step can also be performed before step 1.

3.PEGC sends an IP address request to AMF through a NAS message. The request message includes PINE ID, PIN ID, PEGC ID, and PEGC IP address.

4.AMF sends an IP address request to SMF. The IP address request message includes PINE ID, PIN ID, PEGC ID, and PEGC IP address.

5.SMF selects an IP address from the frame routing information or IP address segment corresponding to the PDU session established by PEGC and assigns it to PINE.

6.SMF sends PINE’s IP address information to AMF. In addition, the message may also contain PEGC ID, PEGC IP address, PINE ID, and PIN ID.

7.AMF sends PINE’s IP address information to PEGC. In addition, the message may also contain PEGC ID, PEGC IP address, PINE ID, and PIN ID.

8. PEGC sends its IP address to PINE. In addition, the message may also contain PEGC ID, PEGC IP address, PINE ID, PIN ID.

In this embodiment, the core network element (such as SMF) acts as a DHCP server to allocate addresses to PINEs associated with PEGC. In this embodiment, SMF is used as an example to illustrate the DHCP server. In other implementations, 5GC network elements such as UPF and other network elements can also be selected as DHCP servers to allocate addresses to PINEs.

Embodiment 4:

FIG12 is a flowchart of the implementation of the fourth embodiment of the present application. In the fourth embodiment, DN acts as a DHCP server to assign an address to PINE. After PEGC establishes a PDU session, it can interact with DN through the user plane to report the PEGC IP address and obtain the address information of PINE. DN will record the routing relationship between the PEGC IP address and the PINE IP address, and send the data packet sent to PINE to PEGC, which will then forward it. The specific process is as follows:

2. PEGC establishes a PDU session and obtains the IP address assigned to it by 5GC. This step can also occur before step 1.

3.PEGC sends an IP address request to DN through the user plane from the application layer. The IP address request contains PINE ID, PIN ID, PEGC ID, and PEGC IP address.

4. DN assigns an IP address to PINE, which can be an IPv4 address and/or an IPv6 prefix, and records the routing relationship between the PEGC IP address and the PINE IP address. When data needs to be sent to PINE, the data packet can be sent to PEGC, and the data packet contains routing information to indicate that the data packet needs to be sent to PINE.

5. DN sends the IP address of PINE (ie, IPv4 address and/or IPv6 prefix) to PEGC.

6. PEGC sends PINE's IP address (ie, IPv4 address and/or IPv6 prefix) to PINE.

From the above embodiments, it can be seen that in embodiments one and two, 5GC sends an available IP address set to PEGC through frame routing information, IPv4 subnet mask and/or IPv6 address prefix, and PEGC can select an IP address from the set to allocate to the PINE associated with it. Frame routing information has been added to the PDR, and all data packets sent to the IP address set can be sent to PEGC first and then forwarded by PEGC. Therefore, even if the association between PINE and PEGC changes, as long as the address allocated by PEGC to PINE is selected from the above IP address set, there is no need to re-establish the PDU session process. For example, when a new PINE is connected to PEGC and an IP address needs to be allocated to it through PEGC, PEGC can select an unused address from the IP address set allocated by 5GC or reuse the IP address of the disconnected PINE.

Embodiment 3 is similar to

Embodiment

1 and 2. The SMF configures the frame routing information or an IP address segment for the PDU session established for the PEGC. Whenever a new PINE needs to interact with the 5GC through the PEGC, the SMF can select an IP address from the configured frame routing information or IP address segment and assign it to the PINE without repeatedly establishing and modifying the PDU session already established for the PEGC.

In the fourth embodiment, the allocation of the IP address of PINE can be achieved through the application layer interaction between PEGC and DN. The routing relationship between PINE and PEGC can be encapsulated in the packet header of the data packet without being configured in the 5GC. DN can send the data packet belonging to PINE to PEGC, and then PEGC forwards the data packet to PINE according to the routing information in the data packet header. At this time, PINE is invisible to 5GC. Therefore, even if the topological relationship between PINE and PEGC changes, the PDU session established by PEGC does not need to be changed.

The addresses involved in the above embodiments may include IPv4 addresses and/or IPv6 prefixes. In the above embodiments, the personal Internet of Things (PIN) scenario is used as an example for explanation. However, the address allocation method of this solution is not only applicable to the PIN scenario, but also to other scenarios where devices that cannot directly access 5GC apply for IP addresses through 3GPP UE.

Fig. 13 is a schematic flow chart of an address allocation method 1300 according to an embodiment of the present application, which can be applied to any system shown in Figs. 1-4, but is not limited thereto. The method includes at least part of the following contents.

S1310. A first network device determines an address set, where the address set is used to allocate an address to a first terminal device associated with the first device.

Among them, the first network device may include SMF, UPF or other core network elements, the first device may include PEGC, and the first terminal device may include PINE.

In one implementation, the first network device determining the address set may include: the first network device determining frame routing information, wherein the frame routing information includes the address set.

In one implementation, the frame routing information further includes an address of the first device.

Acquire the frame routing information by searching the contract information;

Acquire the frame routing information from the DN-AAA server;

generating the frame routing information;

The frame routing information is obtained from the second network device.

Among them, the second network device can be UPF.

In one implementation, the first network device determines the address set, including:

The first network device obtains an IPv4 address and a subnet mask, where the IPv4 address and the subnet mask are used to represent the address set; and/or,

The first network device obtains an IPv6 address and a prefix, where the IPv6 address and the prefix are used to represent the address set.

The IPv4 address or the IPv6 address may also represent the address of the first device.

In one implementation, the first network device may determine the address set in at least one of the following ways:

Acquire the address set by searching the contract information;

Acquire the address set from the DN-AAA server;

allocating the address set;

The address set is obtained from a second network device, wherein the second network device may be a UPF.

In one embodiment, the method further includes: the first network device adds the address set to a PDR corresponding to a session that the first device requests to establish or modify, and provides the PDR to the second network device.

In one implementation, the method further includes: the first network device sending the address set.

The first network device sending address set may include:

The first network device sends a Namf_Communication_N1N2MessageTransfer message, and the Namf_Communication_N1N2MessageTransfer message carries the address set.

In one implementation, the Namf_Communication_N1N2MessageTransfer message may also carry at least one of the following:

an identifier of the first device;

an address of the first device;

an identifier of the first terminal device;

An identifier of the network to which the first device and the first terminal device belong.

In one embodiment, the method further includes: the first network device receives first indication information, where the first indication information is used to request to obtain an address set.

The first network device receiving the first indication information may include:

The first network device receives a Nsmf_PDUSession_CreateSMContext Request message, and the Nsmf_PDUSession_CreateSMContext Request message carries the first indication information.

In one implementation, the Nsmf_PDUSession_CreateSMContext Request message also carries at least one of the following:

an identifier of the first device;

An identifier of a network to which the first device and the first terminal device belong;

The number of addresses requested.

In one implementation, the method further includes: the first network device configuring the address set in a PDR corresponding to a session established by the first device.

In one embodiment, the method further includes: the first network device receives a first address request, the first address request carries an identifier of the first terminal device; the first network device selects an address allocated to the first terminal device from the address set, and sends the address.

The first address request may also carry at least one of the following:

an identifier of the first device;

an address of the first device;

For other details of the address allocation method of this embodiment, reference may be made to the relevant introduction of the first network device in the above embodiment, which will not be repeated here.

Fig. 14 is a schematic flow chart of an address allocation method 1400 according to an embodiment of the present application, which can be applied to any system shown in Figs. 1-4, but is not limited thereto. The method includes at least part of the following contents.

S1410, the server device receives a second address request from the first device;

S1420. The server device allocates an address to the first terminal device associated with the first device according to the second address request.

The server device may be a DN, an AF, an application server, etc. The first device may include a PEGC, and the first terminal device may include a PINE.

In one implementation, the method further includes: the server device sending the address allocated to the first terminal device to the first device.

In one implementation, the second address request may carry at least one of the following:

an identifier of the first device;

an address of the first device;

an identifier of the first terminal device;

In one implementation, the method further includes: the server device recording a routing relationship between the address of the first device and the address of the first terminal device.

In one embodiment, the method further includes: when data needs to be sent to the first terminal device, according to the routing relationship, sending the data to the first device that has a routing relationship with the first terminal device, and including the routing relationship in the data.

For other details of the address allocation method of this embodiment, reference may be made to the relevant introduction of the server device in the above embodiment, which will not be repeated here.

Fig. 15 is a schematic flow chart of an address allocation method 1500 according to an embodiment of the present application, which can be applied to any system shown in Figs. 1-4, but is not limited thereto. The method includes at least part of the following contents.

S1510. The third network device determines an address set, where the address set is used to allocate an address to a first terminal device associated with the first device.

Among them, the third network device may include network elements such as UPF, SMF, AMF, etc., the first device may include PEGC, and the first terminal device may include PINE.

In one implementation, the method further includes: the third network device providing the address set to the first network device.

Among them, the first network device may include network elements such as SMF, UPF, AMF, etc.

In one implementation, the third network device determining the address set includes: the third network device determining frame routing information, where the frame routing information includes the address set.

The frame routing information may also include the address of the first device.

In one implementation, the third network device determines the address set including:

The third network device determines an IPv4 address and a subnet mask, where the IPv4 address and the subnet mask are used to represent the address set; and/or,

The third network device determines an IPv6 address and a prefix, where the IPv6 address and the prefix are used to represent the address set.

For other details of the address allocation method of this embodiment, reference may be made to the relevant introduction of the third network device in the above embodiment, which will not be repeated here.

The embodiment of the present application further provides a first device. FIG. 16 is a schematic structural diagram of the first device 1600 according to the embodiment of the present application, including:

The first receiving module 1610 is used to receive an address set, where the address set is used to allocate an address to a first terminal device associated with the first device.

FIG17 is a schematic diagram of the structure of a first device 1700 according to an embodiment of the present application. The first device 1700 includes one or more features of the above-mentioned first device 1600 embodiment. In a possible implementation, in the embodiment of the present application, it also includes:

The selection module 1720 is configured to select an address from the address set and allocate the address to a first terminal device associated with the first device.

In some embodiments, it further comprises:

The first sending module 1730 is configured to send an address to a first terminal device.

In some implementations, the first receiving module 1610 is configured to receive frame routing information, where the frame routing information includes an address set.

In some implementations, the frame routing information further includes an address of the first device.

In some implementations, the first receiving module 1610 is configured to:

receiving an IPv4 address and a subnet mask, wherein the IPv4 address and the subnet mask are used to represent a set of addresses; and/or,

Receives an IPv6 address and prefix, which are used to represent a collection of addresses.

In some embodiments, the IPv4 address or the IPv6 address also represents the address of the first device.

In some implementations, the first receiving module 1610 is configured to receive a NAS message, where the NAS message carries an address set.

In some implementations, the NAS message also carries at least one of the following:

an identifier of the first device;

the address of the first device;

The identifier of the first terminal device;

In some implementations, the first sending module 1730 is further used to send first indication information, where the first indication information is used to request to obtain an address set.

In some implementations, the first sending module 1730 is configured to send a NAS message, where the NAS message carries the first indication information.

In some implementations, the NAS message further carries at least one of the following:

an identifier of the first device;

The number of addresses requested.

In some embodiments, the first device comprises a PEGC.

In some implementations, the first terminal device includes a PINE.

It should be understood that the above and other operations and/or functions of the modules in the first device according to the embodiment of the present application are respectively for implementing the corresponding processes of the first device in method 500 of Figure 5, and for the sake of brevity, they are not repeated here.

The embodiment of the present application further provides a first network device. FIG. 18 is a schematic diagram of the structure of the first network device 1800 according to the embodiment of the present application, including:

The first determination module 1810 is used to determine an address set, where the address set is used to allocate an address to a first terminal device associated with a first device.

In some implementations, the first determination module 1810 is used to determine frame routing information, where the frame routing information includes an address set.

In some implementations, the first network device determines the frame routing information by at least one of the following methods:

Obtain frame routing information by searching for contract information;

Obtain frame routing information from the DN-AAA server;

Generate frame routing information;

Frame routing information is obtained from the second network device.

In some implementations, the first determining module 1810 is configured to:

Obtaining an IPv4 address and a subnet mask, where the IPv4 address and the subnet mask are used to represent a set of addresses; and/or,

Gets an IPv6 address and prefix. The IPv6 address and prefix are used to represent an address set.

In some implementations, the first network device determines the address set by using at least one of the following methods:

Get the address set by searching the contract information;

Obtain the address set from the DN-AAA server;

Assign address set;

A set of addresses is obtained from a second network device.

FIG19 is a schematic diagram of the structure of a first network device 1900 according to an embodiment of the present application. The first network device 1900 includes one or more features of the first network device 1800 embodiment described above. In a possible implementation, in the embodiment of the present application, it further includes:

The adding module 1920 is used to add the address set to the PDR corresponding to the session that the first device requests to establish or modify, and provide the PDR to the second network device.

In some embodiments, it further comprises:

The second sending module 1930 is used to send an address set.

In some implementations, the second sending module 1930 is used to send a Namf_Communication_N1N2MessageTransfer message, where the Namf_Communication_N1N2MessageTransfer message carries an address set.

In some implementations, the Namf_Communication_N1N2MessageTransfer message further carries at least one of the following:

an identifier of the first device;

the address of the first device;

The identifier of the first terminal device;

In some embodiments, it further comprises:

The second receiving module 1940 is used to receive first indication information, where the first indication information is used to request to obtain an address set.

In some embodiments, the second receiving module 1940 is used to receive an Nsmf_PDUSession_CreateSMContext Request message, and the Nsmf_PDUSession_CreateSMContext Request message carries the first indication information.

In some implementations, the Nsmf_PDUSession_CreateSMContext Request message also carries at least one of the following:

an identifier of the first device;

The number of addresses requested.

In some embodiments, it further comprises:

The configuration module 1950 is used to configure an address set in a PDR corresponding to a session established by the first device.

In some implementations, the address selection module 1960 is further included, configured to:

receiving a first address request, where the first address request carries an identifier of a first terminal device;

An address allocated to the first terminal device is selected from the address set, and the address is sent.

In some implementations, the first address request further carries at least one of the following:

an identifier of the first device;

the address of the first device;

In some embodiments, the first network device includes SMF, UPF or other core network elements.

In some embodiments, the first device comprises a PEGC.

In some implementations, the first terminal device includes a PINE.

In some implementations, the second network device includes a UPF.

It should be understood that the above and other operations and/or functions of the module in the first network device according to the embodiment of the present application are respectively for implementing the corresponding processes of the first network device in method 1300 of Figure 13, and for the sake of brevity, they are not repeated here.

The embodiment of the present application further provides a server device. FIG. 20 is a schematic diagram of the structure of a server device 2000 according to the embodiment of the present application, including:

The third receiving module 2010 is used to receive a second address request from the first device;

The allocation module 2020 is used to allocate an address to the first terminal device associated with the first device according to the second address request.

FIG21 is a schematic diagram of the structure of a server device 2100 according to an embodiment of the present application. The server device 2100 includes one or more features of the above-mentioned server device 2000 embodiment. In a possible implementation, in the embodiment of the present application, it also includes:

The third sending module 2130 is used to send the address allocated to the first terminal device to the first device.

In some implementations, the second address request carries at least one of the following:

an identifier of the first device;

the address of the first device;

The identifier of the first terminal device;

In some embodiments, it further comprises:

The recording module 2140 is used to record the routing relationship between the address of the first device and the address of the first terminal device.

In some implementations, the recording module 2140 is further configured to:

When data needs to be sent to the first terminal device, the data is sent to the first device having a routing relationship with the first terminal device according to the routing relationship, and the routing relationship is included in the data.

In some embodiments, the first device comprises a PEGC.

In some implementations, the first terminal device includes a PINE.

It should be understood that the above-mentioned and other operations and/or functions of the modules in the server device according to the embodiment of the present application are respectively for implementing the corresponding processes of the server device in method 1400 of Figure 14, and for the sake of brevity, they are not repeated here.

The embodiment of the present application further proposes a third network device. FIG. 22 is a schematic diagram of the structure of the third network device 2200 according to the embodiment of the present application, including:

The second determination module 2210 is used to determine an address set, where the address set is used to allocate an address to a first terminal device associated with the first device.

FIG23 is a schematic diagram of the structure of a third network device 2300 according to an embodiment of the present application. The third network device 2300 includes one or more features of the third network device 2200 embodiment described above. In a possible implementation, in the embodiment of the present application, it also includes:

A providing module 2320 is provided for providing the address set to the first network device.

In some implementations, the second determination module 2210 is used to determine frame routing information, where the frame routing information includes an address set.

In some implementations, the second determining module 2210 is configured to:

Determine an IPv4 address and a subnet mask, wherein the IPv4 address and the subnet mask are used to represent a set of addresses; and/or,

Determine the IPv6 address and prefix, which are used to represent a set of addresses.

In some embodiments, the third network device includes a UPF.

In some embodiments, the first device comprises a PEGC.

In some embodiments, the first terminal device includes a PINE.

In some implementations, the first network device includes a SMF.

It should be understood that the above and other operations and/or functions of the modules in the third network device according to the embodiment of the present application are respectively for implementing the corresponding processes of the third network device in method 1400 of Figure 14, and for the sake of brevity, they are not repeated here.

It should be noted that the functions described in the various modules (submodules, units or components, etc.) in the communication device of the embodiment of the present application can be implemented by different modules (submodules, units or components, etc.) or by the same module (submodules, units or components, etc.). For example, the first receiving module and the second receiving module can be different modules or the same module, and both can implement their corresponding functions in the embodiment of the present application. In addition, the sending module and the receiving module in the embodiment of the present application can be implemented by the transceiver of the device, and some or all of the remaining modules can be implemented by the processor of the device.

Fig. 24 is a schematic structural diagram of a communication device 2400 according to an embodiment of the present application. The communication device 2400 shown in Fig. 24 includes a processor 2410, and the processor 2410 can call and run a computer program from a memory to implement the method in the embodiment of the present application.

In some implementations, as shown in FIG24 , the communication device 2400 may further include a memory 2420. The processor 2410 may call and run a computer program from the memory 2420 to implement the communication device in the embodiment of the present application.

The memory 2420 may be a separate device independent of the processor 2410 , or may be integrated into the processor 2410 .

In some embodiments, as shown in FIG. 24 , the communication device 2400 may further include a transceiver 2430 , and the processor 2410 may control the transceiver 2430 to communicate with other devices, specifically, may send information or data to other devices, or receive information or data sent by other devices.

The transceiver 2430 may include a transmitter and a receiver. The transceiver 2430 may further include an antenna, and the number of antennas may be one or more.

In some embodiments, the communication device 2400 may be the communication device of the embodiment of the present application, and the communication device 2400 may implement the corresponding processes implemented by the communication device in each method of the embodiment of the present application, which will not be repeated here for the sake of brevity.

Fig. 25 is a schematic structural diagram of a chip 2500 according to an embodiment of the present application. The chip 2500 shown in Fig. 25 includes a processor 2510, and the processor 2510 can call and run a computer program from a memory to implement the method in the embodiment of the present application.

In some implementations, as shown in FIG25 , the chip 2500 may further include a memory 2520. The processor 2510 may call and run a computer program from the memory 2520 to implement the method in the embodiment of the present application.

The memory 2520 may be a separate device independent of the processor 2510 , or may be integrated into the processor 2510 .

In some implementations, the chip 2500 may further include an input interface 2530. The processor 2510 may control the input interface 2530 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

In some implementations, the chip 2500 may further include an output interface 2540. The processor 2510 may control the output interface 2540 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

In some embodiments, the chip can be applied to the communication device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the network device in each method of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

The processor mentioned above may be a general-purpose processor, a digital signal processor (DSP), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC) or other programmable logic devices, transistor logic devices, discrete hardware components, etc. Among them, the general-purpose processor mentioned above may be a microprocessor or any conventional processor, etc.

The memory mentioned above may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM).

It should be understood that the above-mentioned memory is exemplary but not restrictive. For example, the memory in the embodiment of the present application may also be 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, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM), etc. That is to say, the memory in the embodiment of the present application is intended to include but not limited to these and any other suitable types of memory.

In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can 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. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, The computer instructions can be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (Digital Subscriber Line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid state drive (SSD)), etc.

It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

An address allocation method, comprising:

The first device receives an address set, where the address set is used to allocate an address to a first terminal device associated with the first device.
The method according to claim 1, further comprising:

The first device selects an address from the address set, and allocates the address to a first terminal device associated with the first device.
The method according to claim 2, further comprising:

The first device sends the address to the first terminal device.
The method according to any one of claims 1 to 3, wherein the first device receives the address set, comprising:

The first device receives frame routing information, where the frame routing information includes the address set.
The method according to claim 4, wherein the frame routing information further includes an address of the first device.
The method according to any one of claims 1 to 3, wherein the first device receives the address set, comprising:

The first device receives an IPv4 address and a subnet mask, where the IPv4 address and the subnet mask are used to represent the address set; and/or,

The first device receives an IPv6 address and a prefix, where the IPv6 address and the prefix are used to represent the address set.
The method according to claim 6, wherein the IPv4 address or the IPv6 address also represents the address of the first device.
The method according to any one of claims 1 to 7, wherein the first device receives the address set, comprising:

The first device receives a NAS message, where the NAS message carries the address set.
The method according to claim 8, wherein the NAS message further carries at least one of the following:

an identifier of the first device;

an address of the first device;

an identifier of the first terminal device;

An identifier of the network to which the first device and the first terminal device belong.
The method according to any one of claims 1 to 9, further comprising:

The first device sends first indication information, where the first indication information is used to request to obtain an address set.
The method according to claim 10, wherein the first device sending the first indication information comprises:

The first device sends a NAS message, where the NAS message carries the first indication information.
The method according to claim 11, wherein the NAS message further carries at least one of the following:

an identifier of the first device;

An identifier of a network to which the first device and the first terminal device belong;

The number of addresses requested.
The method according to any one of claims 1-12, wherein the first device comprises a PEGC.
The method according to any one of claims 1-13, wherein the first terminal device comprises a PINE.
An address allocation method, comprising:

The first network device determines an address set, where the address set is used to allocate an address to a first terminal device associated with the first device.
The method according to claim 15, wherein the first network device determines the address set, comprising:

The first network device determines frame routing information, wherein the frame routing information includes the address set.
The method according to claim 16, wherein the frame routing information further includes an address of the first device.
The method according to claim 16 or 17, wherein the first network device determines the frame routing information by at least one of the following methods:

Acquire the frame routing information by searching the contract information;

Acquire the frame routing information from the DN-AAA server;

generating the frame routing information;

The frame routing information is obtained from the second network device.
The method according to claim 15, wherein the first network device determines the address set, comprising:

The first network device obtains an IPv4 address and a subnet mask, where the IPv4 address and the subnet mask are used to represent the address set; and/or,

The first network device obtains an IPv6 address and a prefix, where the IPv6 address and the prefix are used to represent the address set.
The method according to claim 19, wherein the IPv4 address or the IPv6 address also represents an address of the first device.
The method according to claim 19 or 20, wherein the first network device determines the address set by at least one of the following methods:

Acquire the address set by searching the contract information;

Acquire the address set from the DN-AAA server;

allocating the address set;

The address set is obtained from the second network device.
The method according to any one of claims 15 to 21, further comprising:

The first network device adds the address set to the PDR corresponding to the session that the first device requests to establish or modify, and provides the PDR to the second network device.
The method according to any one of claims 15-22 further includes: the first network device sending the address set.
The method according to claim 23, wherein the first network device sending the address set comprises:

The first network device sends a Namf_Communication_N1N2MessageTransfer message, and the Namf_Communication_N1N2MessageTransfer message carries the address set.
The method according to claim 24, wherein

The Namf_Communication_N1N2MessageTransfer message also carries at least one of the following:

an identifier of the first device;

an address of the first device;

an identifier of the first terminal device;

An identifier of the network to which the first device and the first terminal device belong.
The method according to any one of claims 15 to 25, further comprising:

The first network device receives first indication information, where the first indication information is used to request to obtain an address set.
The method according to claim 26, wherein the first network device receiving the first indication information comprises:

The first network device receives a Nsmf_PDUSession_CreateSMContext Request message, and the Nsmf_PDUSession_CreateSMContext Request message carries the first indication information.
The method according to claim 27, wherein

The Nsmf_PDUSession_CreateSMContext Request message also carries at least one of the following:

an identifier of the first device;

An identifier of a network to which the first device and the first terminal device belong;

The number of addresses requested.
The method of claim 15, 16, 17, 19 or 20, further comprising:

The first network device configures the address set in a PDR corresponding to the session established by the first device.
The method according to claim 15 or 29, further comprising:

The first network device receives a first address request, where the first address request carries an identifier of the first terminal device;

The first network device selects an address allocated to the first terminal device from the address set, and sends the address.
The method according to claim 30, wherein the first address request further carries at least one of the following:

an identifier of the first device;

an address of the first device;

An identifier of the network to which the first device and the first terminal device belong.
According to any method described in claims 15-31, the first network device includes SMF, UPF or other core network elements.
The method according to any one of claims 15-32, wherein the first device comprises a PEGC.
The method according to any one of claims 15-33, wherein the first terminal device comprises a PINE.
The method according to claim 18 or 21, wherein the second network device comprises a UPF.
An address allocation method, comprising:

The server device receives a second address request from the first device;

The server device allocates an address to a first terminal device associated with the first device according to the second address request.
The method according to claim 36, further comprising,

The server device sends the address allocated to the first terminal device to the first device.
The method according to claim 36 or 37, wherein the second address request carries at least one of the following:

an identifier of the first device;

an address of the first device;

an identifier of the first terminal device;

An identifier of the network to which the first device and the first terminal device belong.
The method according to any one of claims 36 to 38, further comprising:

The server device records a routing relationship between the address of the first device and the address of the first terminal device.
The method according to claim 39, further comprising:

When data needs to be sent to the first terminal device, the data is sent to the first device having a routing relationship with the first terminal device according to the routing relationship, and the routing relationship is included in the data.
The method according to any one of claims 36-40, wherein the first device comprises a PEGC.
The method according to any one of claims 36-41, wherein the first terminal device comprises a PINE.
An address allocation method, comprising:

The third network device determines an address set, where the address set is used to allocate an address to a first terminal device associated with the first device.
The method of claim 43, further comprising the third network device providing the address set to the first network device.
The method according to claim 43 or 44, wherein the third network device determines the address set comprises:

The third network device determines frame routing information, wherein the frame routing information includes the address set.
The method of claim 45, wherein the frame routing information further includes an address of the first device.
The method according to claim 43 or 44, wherein the third network device determines the address set comprises:

The third network device determines an IPv4 address and a subnet mask, wherein the IPv4 address and the subnet mask are used to represent the address set; and/or,

The third network device determines an IPv6 address and a prefix, where the IPv6 address and the prefix are used to represent the address set.
The method according to claim 47, wherein the IPv4 address or the IPv6 address also represents the address of the first device.
The method according to any one of claims 43-48, wherein the third network device includes a UPF.
The method according to any one of claims 43-49, wherein the first device comprises a PEGC.
The method according to any one of claims 43-50, wherein the first terminal device comprises a PINE.
The method of claim 44, wherein the first network device comprises an SMF.
A first device includes:

The first receiving module is used to receive an address set, where the address set is used to allocate an address to a first terminal device associated with the first device.
A first network device includes:

The first determination module is used to determine an address set, where the address set is used to allocate an address to a first terminal device associated with the first device.
A server device, comprising:

A third receiving module, configured to receive a second address request from the first device;

An allocation module is used to allocate an address to a first terminal device associated with the first device according to the second address request.
A third network device, comprising:

The second determination module is used to determine an address set, where the address set is used to allocate an address to a first terminal device associated with the first device.
A communication device comprises: a processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory to execute a method as described in any one of claims 1 to 14, 15 to 35, 36 to 42, or 43 to 52.
A chip, comprising: a processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes a method as described in any one of claims 1 to 14, 15 to 35, 36 to 42, or 43 to 52.
A computer-readable storage medium for storing a computer program, wherein the computer program causes a computer to execute the method according to any one of claims 1 to 14, 15 to 35, 36 to 42, or 43 to 52.
A computer program product comprising computer program instructions, the computer program instructions causing a computer to execute the method according to any one of claims 1 to 14, 15 to 35, 36 to 42, or 43 to 52.
A computer program causing a computer to execute the method of any one of claims 1 to 14, 15 to 35, 36 to 42, or 43 to 52.