CN116938806A

CN116938806A - Message sending method, PIN management method, communication device and communication system

Info

Publication number: CN116938806A
Application number: CN202210383990.6A
Authority: CN
Inventors: 臧昕; 周润泽; 徐艺珊
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2022-04-12
Filing date: 2022-04-12
Publication date: 2023-10-24
Also published as: WO2023197737A1

Abstract

The embodiment of the application provides a message sending method, a PIN management method, a communication device and a communication system. The method comprises the following steps: the user plane network element receives a message, wherein the message comprises the address of the PIN element network element; the user plane network element determines a packet detection rule matched with the address of the PIN element network element; and the user plane network element sends the message to the PIN gateway network element according to the tunnel information of the PIN gateway network element in the forwarding action rule corresponding to the packet detection rule. According to the scheme, the user plane network element sends the received message which needs to be sent to the PIN element network element to the PIN gateway network element according to the corresponding relation between the PIN gateway network element and the PIN element network element, and the PIN gateway network element sends the message to the PIN element network element, so that the message can be sent correctly and quickly.

Description

Message sending method, PIN management method, communication device and communication system

Technical Field

The present application relates to the field of communications technologies, and in particular, to a packet sending method, a PIN management method, a communication device, and a communication system.

Background

The third generation partnership project (3rd generation partnership project,3GPP) proposes that the fifth generation (5th generation,5G) network needs to be aware of internet of things (Internet of Things, ioT) devices. The user may create his own personal internet of things (Personal IoT Networks, PIN).

How to realize the correct sending of the messages related to the PIN is to be solved.

Disclosure of Invention

The embodiment of the application provides a message sending method, a PIN management method, a communication device and a communication system, which are used for realizing the correct sending of messages related to PIN.

In a first aspect, an embodiment of the present application provides a method for sending a message, where the method may be performed by a user plane network element or a module (such as a chip) in the user plane network element. Taking the user plane network element to execute the method as an example, the method comprises the following steps: the user plane network element receives a message, wherein the message comprises the address of the PIN element network element; the user plane network element determines a packet detection rule matched with the address of the PIN element network element; and the user plane network element sends the message to the PIN gateway network element according to the tunnel information of the PIN gateway network element in the forwarding action rule corresponding to the packet detection rule.

According to the scheme, the user plane network element sends the received message which needs to be sent to the PIN element network element to the PIN gateway network element according to the corresponding relation between the PIN gateway network element and the PIN element network element, and the PIN gateway network element sends the message to the PIN element network element, so that the message can be sent correctly and quickly.

In a possible implementation method, the user plane network element receives the packet detection rule and the forwarding action rule from a session management network element.

In a possible implementation method, the user plane network element receives the packet detection rule and the forwarding action rule from the session management network element, including: the user plane network element receives a session request message from the session management network element, wherein the session request message comprises the packet detection rule and the forwarding action rule; or, the user plane network element receives a session update message from the session management network element, the session update message including the packet detection rule and the forwarding action rule.

In a second aspect, an embodiment of the present application provides a method for sending a message, where the method may be performed by a user plane network element or a module (such as a chip) in the user plane network element. Taking the user plane network element to execute the method as an example, the method comprises the following steps: the user plane network element receives a message, wherein the message comprises the address of the PIN element network element; the user plane network element determines a packet detection rule matched with the address of the PIN element network element; the user plane network element determines a plurality of forwarding action rules corresponding to the packet detection rules, each forwarding action rule in the plurality of forwarding action rules comprising tunnel information of a PIN gateway network element; the user plane network element selects a PIN gateway network element from the PIN gateway network elements according to loads of the PIN gateway network elements corresponding to the forwarding action rules; the user plane network element sends the message to the selected PIN gateway network element according to the tunnel information of the selected PIN gateway network element.

According to the scheme, the user plane network element sends the received message which needs to be sent to the PIN element network element to the PIN gateway network element according to the corresponding relation between the PIN gateway network element and the PIN element network element and the load of the PIN gateway network element, and the PIN gateway network element sends the message to the PIN element network element, so that the accurate and rapid sending of the message is facilitated.

In a possible implementation method, the user plane network element receives the packet detection rule and the plurality of forwarding action rules from a session management network element.

In one possible implementation, the plurality of forwarding action rules includes a first forwarding action rule and a second forwarding action rule; the user plane network element receiving the packet detection rule and the plurality of forwarding action rules from a session management network element, comprising: the user plane network element receiving a first session request message from the session management network element, the first session request message comprising the packet detection rule and the first forwarding operation rule; the user plane network element receives a second session request message from the session management network element, the second session request message comprising the packet detection rule and the second forwarding action rule.

In one possible implementation, the plurality of forwarding action rules includes a first forwarding action rule and a second forwarding action rule; the user plane network element receiving the packet detection rule and the plurality of forwarding action rules from a session management network element, comprising: the user plane network element receiving a first session update message from the session management network element, the first session update message comprising the packet detection rule and the first forwarding operation rule; the user plane network element receives a second session update message from the session management network element, the second session update message comprising the packet detection rule and the second forwarding action rule.

In a possible implementation method, the user plane network element selects a PIN gateway network element from a plurality of PIN gateway network elements according to loads of the PIN gateway network elements corresponding to the forwarding action rules, where the method includes: the user plane network element selects a PIN gateway network element with the lightest load from the PIN gateway network elements according to the loads of the PIN gateway network elements; or the user plane network element randomly selects one PIN gateway network element from N PIN gateway network elements with the lightest load in the PIN gateway network elements according to the loads of the PIN gateway network elements, wherein N is an integer greater than 1.

In a third aspect, embodiments of the present application provide a PIN management method, which may be performed by a session management network element or a module (e.g. a chip) in the session management network element. Taking the session management network element as an example, the method comprises the following steps: the method comprises the steps that a session management network element receives a session establishment request message from a PIN gateway network element, wherein the session establishment request message requests to establish a session, and the session establishment request message comprises indication information which indicates that the session is a PIN session; the session management network element sends a request message to the PIN network function network element according to the indication information, wherein the request message comprises identification information of the PIN gateway network element, and the request message is used for acquiring the identification information of the PIN element network element corresponding to the PIN gateway network element; the session management network element receives identification information of a PIN element network element corresponding to the PIN gateway network element from the PIN network function network element; the session management network element sends the tunnel information of the PIN gateway network element and the identification information of the PIN element network element corresponding to the PIN gateway network element to the user plane network element.

The proposal is realized that the user plane network element is configured with the corresponding relation between the PIN gateway network element and the PIN element network element, so that the user plane network element can send the received message which needs to be sent to the PIN element network element to the PIN gateway network element according to the corresponding relation, and the PIN gateway network element sends the message to the PIN element network element, thereby being beneficial to realizing the correct and rapid sending of the message.

In a possible implementation method, the session management network element sends tunnel information of the PIN gateway network element and identification information of the PIN element network element corresponding to the PIN gateway network element to a user plane network element, including: the session management network element sends at least one packet detection rule and a forwarding action rule corresponding to the at least one packet detection rule to the user plane network element, wherein the at least one packet detection rule respectively comprises identification information of one PIN element network element in identification information of the PIN element network element corresponding to the PIN gateway network element, and the forwarding action rule comprises tunnel information of the PIN gateway network element.

In a possible implementation method, the session management network element sends at least one packet detection rule and a forwarding action rule corresponding to the at least one packet detection rule to the user plane network element, including: the session management network element sends a session request message to the user plane network element, wherein the session request message comprises the at least one packet detection rule and the forwarding action rule; or, the session management network element sends a session update message to the user plane network element, the session update message including the at least one packet detection rule and the forwarding action rule.

In a possible implementation method, the session management network element receives identification information of an updated PIN element network element corresponding to the PIN gateway network element from the PIN network function network element; the session management network element sends the tunnel information of the PIN gateway network element and the identification information of the updated PIN element network element to the user plane network element.

By the scheme, the corresponding relation between the PIN gateway network element and the PIN element network element on the user plane network element can be updated in time, and accurate sending of the message is facilitated.

In a fourth aspect, embodiments of the present application provide a PIN management method, which may be performed by a PIN management network element or a module (e.g. a chip) in the PIN management network element. Taking the PIN management network element as an example, the method comprises the following steps: the PIN management network element receives a first notification message from a first PIN gateway network element, wherein the first notification message comprises identification information of the first PIN gateway network element, identification information of a PIN element network element and indication information, and the indication information indicates that the first PIN gateway network element cannot route messages of the PIN element network element; the PIN management network element sends a second notification message to a second PIN gateway network element, wherein the second notification message comprises identification information of the PIN element network element, and the second notification message indicates that the second PIN gateway network element provides routing service for the PIN element network element; the PIN management network element sends a third notification message to the PIN element network element, the third notification message including identification information of the second PIN gateway network element, the third notification message indicating that the second PIN gateway network element provides routing services for the PIN element network element.

According to the scheme, when the PIN gateway network elements are overloaded and cannot provide routing service for one or some PIN element network elements, one PIN gateway network element can be reselected, and the newly selected PIN gateway network element provides routing service for one or more PIN element network elements, so that load balancing among a plurality of PIN gateway network elements is realized, and correct and rapid sending of messages is facilitated.

In a possible implementation method, the PIN management network element selects the target UE as the second PIN gateway network element.

In a possible implementation method, the target UE is one of a plurality of PIN element network elements of the first PIN gateway network element providing the routing service.

In a possible implementation method, the PIN management network element selects the PIN management network element as the second PIN gateway network element.

In a possible implementation method, the PIN management network element sends a request message to the PIN network function network element, where the request message includes identification information of the PIN, and the request message requests to select a PIN gateway network element for the PIN.

In a fifth aspect, an embodiment of the present application provides a communication device, where the device may be a user plane network element or a module (e.g. a chip) in the user plane network element. The apparatus has the function of implementing any implementation method of the first aspect or the second aspect. The functions can be realized by hardware, and can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the functions described above.

In a sixth aspect, embodiments of the present application provide a communication device, which may be a session management network element or a module (e.g. a chip) in the session management network element. The apparatus has a function of implementing any implementation method of the third aspect. The functions can be realized by hardware, and can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the functions described above.

In a seventh aspect, embodiments of the present application provide a communications device, which may be a PIN management network element or a module (e.g., a chip) in a PIN management network element. The apparatus has a function of implementing any implementation method of the fourth aspect. The functions can be realized by hardware, and can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the functions described above.

In an eighth aspect, an embodiment of the present application provides a communication device, including a processor and an interface circuit, where the processor is configured to communicate with other devices through the interface circuit, and perform any implementation method of the first aspect to the fourth aspect. The processor includes one or more.

In a ninth aspect, an embodiment of the present application provides a communication apparatus, including a processor and a memory; the memory is configured to store computer instructions that, when executed by the apparatus, cause the apparatus to perform any of the implementation methods of the first to fourth aspects.

In a tenth aspect, embodiments of the present application provide a communication device comprising means for performing the steps of any of the implementation methods of the first to fourth aspects described above.

In an eleventh aspect, an embodiment of the present application provides a communication device, including a processor coupled to a memory, where the processor is configured to invoke a program stored in the memory to perform any implementation method of the first aspect to the fourth aspect. The memory may be located within the device or may be located external to the device. And the processor may be one or more.

In a twelfth aspect, embodiments of the present application further provide a computer-readable storage medium having instructions stored therein that, when executed on a communication device, cause any implementation method of the first to fourth aspects described above to be performed.

In a thirteenth aspect, embodiments of the present application also provide a computer program product comprising a computer program or instructions which, when executed by a communication device, cause any of the implementation methods of the first to fourth aspects described above to be performed.

In a fourteenth aspect, an embodiment of the present application further provides a chip system, including: a processor configured to perform any implementation method of the first to fourth aspects.

In a fifteenth aspect, an embodiment of the present application further provides a communication system, including a PIN gateway network element, and a user plane network element for performing any of the methods of the first aspect; the PIN gateway network element is used for receiving the message from the user plane network element.

In a sixteenth aspect, an embodiment of the present application further provides a communication system, including a PIN gateway network element, and a user plane network element for performing any of the methods of the second aspect; the PIN gateway network element is used for receiving the message from the user plane network element.

In a seventeenth aspect, an embodiment of the present application further provides a communication system, including a user plane network element, and a session management network element for performing any of the methods of the third aspect; the user plane network element is configured to receive tunnel information of a PIN gateway network element and identification information of a PIN element network element corresponding to the PIN gateway network element from the session management network element.

In an eighteenth aspect, an embodiment of the present application further provides a communication system, including a PIN element network element, and a PIN management network element for performing any of the methods of the fourth aspect; the PIN element network element is configured to receive a third notification message from the PIN management network element, where the third notification message includes identification information of a second PIN gateway network element, and the third notification message indicates that the second PIN gateway network element provides a routing service for the PIN element network element.

Drawings

FIG. 1 is a schematic diagram of a 5G network architecture based on a servitization architecture;

FIG. 2 is a schematic diagram of a PIN architecture;

fig. 3 (a) is a flow chart of a message sending method according to an embodiment of the present application;

fig. 3 (b) is a flow chart of a message sending method according to an embodiment of the present application;

fig. 3 (c) is a schematic flow chart of a PIN management method according to an embodiment of the present application;

fig. 3 (d) is a schematic flow chart of a PIN management method according to an embodiment of the present application;

fig. 4 is a schematic flow chart of a PIN management method according to an embodiment of the present application;

fig. 5 is a schematic flow chart of a PIN management method according to an embodiment of the present application;

fig. 6 is a schematic flow chart of a PIN management method according to an embodiment of the present application;

fig. 7 is a schematic flow chart of a PIN management method according to an embodiment of the present application;

fig. 8 is a schematic diagram of a communication device according to an embodiment of the present application;

fig. 9 is a schematic diagram of a communication device according to an embodiment of the present application.

Detailed Description

Fig. 1 is a schematic diagram of a 5G network architecture based on a servitization architecture. The 5G network architecture shown in fig. 1 includes a Data Network (DN) and an operator network. The following provides a brief description of the functionality of some of the network elements.

The operator network may include one or more of the following network elements: an authentication server function (Authentication Server Function, AUSF) network element (not shown in the figure), a unified data management (unified data management, UDM) network element, a unified database (Unified Data Repository, UDR) network element, a network storage function (Network Repository Function, NRF) network element (not shown in the figure), a network opening function (network exposure function, NEF) network element (not shown in the figure), an application function (application function, AF) network element, a policy control function (policy control function, PCF) network element, a PIN network function (PINnetwork function, PNF) network element, an access and mobility management function (access and mobility management function, AMF) network element, a session management function (session management function, SMF) network element, a UPF network element, a radio access network (radio access network, RAN) device, etc. In the above-mentioned operator network, the network elements or devices other than the radio access network device may be referred to as core network elements or core network devices.

The radio access network device may be a base station (base station), an evolved NodeB (eNodeB), a transmission and reception point (transmission reception point, TRP), a next generation NodeB (gNB) in a 5G mobile communication system, a next generation base station in a sixth generation (6th generation,6G) mobile communication system, a base station in a future mobile communication system, or an access node in a wireless fidelity (wireless fidelity, wiFi) system, etc.; the present application may also be a module or unit that performs a function of a base station part, for example, a Central Unit (CU) or a Distributed Unit (DU). The radio access network device may be a macro base station, a micro base station, an indoor station, a relay node, a donor node, or the like. The embodiment of the application does not limit the specific technology and the specific equipment form adopted by the wireless access network equipment. For convenience of explanation, the embodiment of the present application will be described with a base station as an example of a radio access network device.

A terminal device in communication with the RAN may also be referred to as a terminal, user Equipment (UE). The terminal device may be widely applied to various scenes, for example, device-to-device (D2D), vehicle-to-device (vehicle to everything, V2X) communication, machine-type communication (MTC), internet of things (internet of things, ioT), virtual reality, augmented reality, industrial control, autopilot, telemedicine, smart grid, smart furniture, smart office, smart wear, smart transportation, smart city, etc. The terminal equipment can be a mobile phone, a tablet personal computer, a computer with a wireless receiving and transmitting function, a wearable device, a vehicle, an unmanned aerial vehicle, a helicopter, an airplane, a ship, a robot, a mechanical arm, intelligent household equipment and the like. The embodiment of the application does not limit the specific technology and the specific equipment form adopted by the terminal equipment.

The radio access network device and the terminal device may be fixed in location or may be mobile. The radio access network device and the terminal device may be deployed on land, including indoor or outdoor, hand-held or vehicle-mounted; the device can be deployed on the water surface; but also on aerial planes, balloons and satellites. The embodiment of the application does not limit the application scenes of the wireless access network equipment and the terminal equipment.

The mobility management network element is a control plane network element provided by the operator network and is responsible for access control and mobility management of the terminal equipment accessing the operator network, for example, the mobility management comprises the functions of mobility state management, user temporary identity identification allocation, user authentication, user authorization and the like. In 5G, the mobility management element may be an AMF element, and in future communications such as the sixth generation (the 6th generation,6G), the mobility management element may still be an AMF element, or have other names, which is not limited by the present application.

The session management network element is a control plane network element provided by the operator network and is responsible for managing protocol data unit (protocol data unit, PDU) sessions of the terminal devices. A PDU session is a channel for transmitting PDUs, and the terminal device needs to transmit PDUs to each other through the PDU session and DN. The PDU session is responsible for establishment, maintenance, deletion, etc. by the SMF network element. Session management network elements include session management (e.g., session establishment, modification, and release, including tunnel maintenance between user plane network elements and radio access network devices), selection and control of user plane network elements, traffic and session continuity (Service and Session Continuity, SSC) mode selection, roaming, and like session related functions. In 5G, the session management network element may be an SMF network element, and in future communications such as 6G, the session management network element may still be an SMF network element, or have other names, which is not limited by the present application.

The user plane network element is a gateway provided by an operator, and is a gateway for the operator network to communicate with the DN. The UPF network element comprises functions related to user planes such as data packet routing and transmission, packet detection, traffic reporting, quality of service (Quality of Service, qoS) processing, lawful interception, uplink packet detection, downlink data packet storage and the like. In 5G, the user plane element may be a UPF element, and in future communications such as 6G, the user plane element may still be a UPF element, or have other names, which is not limited by the present application.

The data management network element is a control plane network element provided by an operator and is responsible for storing information such as a user permanent identifier (subscriber permanent identifier, SUPI), a trust (security context), subscription data and the like of an signing user in an operator network. This information stored by the data management network element may be used for authentication and authorization of the terminal device to access the operator network. In 5G, the data management network element may be a UDM network element, and in future communications such as 6G, the data management network element may still be a UDM network element, or have other names, which is not limited by the present application.

The unified database network element is a control plane network element provided by an operator and comprises an access function for executing type data such as subscription data, policy data, application data and the like. In 5G, the unified database network element may be a UDR network element, and in future communications such as 6G, the unified database network element may still be a UDR network element, or have other names, which is not limited by the present application.

The network opening network element is a control plane network element provided by an operator. The network opening network element opens an external interface of the operator network to the third party in a secure manner. When the session management network element needs to communicate with the network element of the third party, the network opening network element can be used as a relay for the session management network element to communicate with the network element of the third party. When the network opens the network element as a relay, the network element can be used as the translation of the identification information of the contracted user and the translation of the identification information of the network element of a third party. For example, when the network opening element transmits the SUPI of the subscriber from the operator network to the third party, the SUPI may be translated into its corresponding external Identity (ID). Conversely, when the network element opens the network element to send the external ID (the network element ID of the third party) to the operator network, it may be translated into SUPI. In 5G, the network opening network element may be a NEF network element, and in future communications such as 6G, the network opening network element may still be a NEF network element, or have other names, which is not limited by the present application.

The application function network element is used for transmitting the requirement of the application side to the network side, such as QoS requirement or user state event subscription. The application function network element may be a third party function entity or an application server deployed by an operator. In 5G, the application function element may be an AF element, and in future communications such as 6G, the application function element may still be an AF element, or have other names, which is not limited by the present application.

The policy control network element is a control plane function provided by the operator for providing the session management network element with policies for PDU sessions. Policies may include charging related policies, qoS related policies, and authorization related policies, among others. In 5G, the policy control network element may be a PCF network element, and in future communications, such as 6G, the policy control network element may still be a PCF network element, or have other names, which is not limited by the present application.

The network storage function network element can be used for providing a network element discovery function and providing network element information corresponding to the network element type based on the request of other network elements. Network storage function the network element also provides network element management services such as network element registration, updating, deregistration, network element state subscription and push, etc. In 5G, the network storage function element may be an NRF element, and in future communications such as 6G, the network storage function element may still be an NRF element, or have other names, which is not limited by the present application.

The PIN network function network element can create the PIN according to the received PIN creation request, allocate the identification information of the PIN, store the PIN information and the like. In 5G, the PIN network function element may be a PNF element, and in future communications such as 6G, the PIN network function element may still be a PNF element, or may have other names, which the present application is not limited to.

The DN is a network outside the operator network, the operator network can be accessed to a plurality of DNs, a plurality of services can be deployed on the DNs, and services such as data and/or voice can be provided for the terminal equipment. For example, the DN is a private network of an intelligent plant, the sensors installed in the plant of the intelligent plant may be terminal devices, a control server of the sensors is disposed in the DN, and the control server may serve the sensors. The sensor may communicate with the control server, obtain instructions from the control server, transmit collected sensor data to the control server, etc., according to the instructions. For another example, DN is an internal office network of a company, where a mobile phone or a computer of an employee of the company may be a terminal device, and the mobile phone or the computer of the employee may access information, data resources, etc. on the internal office network of the company.

Npcf, nudr, nudm, naf, namf, nsmf, npnf in fig. 1 is a service interface provided by the PCF network element, the UDR network element, the UDM network element, the AF network element, the AMF network element, the SMF network element, and the PNF network element, respectively, for invoking a corresponding service operation. N1, N2, N3, N4, and N6 are interface serial numbers, and the meaning of these interface serial numbers is as follows:

1) N1: the interface between the AMF network element and the UE may be used to communicate non-access stratum (non access stratum, NAS) signaling (e.g., including QoS rules from the AMF network element) to the UE, etc.

2) N2: the interface between the AMF network element and the radio access network device may be used to transfer radio bearer control information from the core network side to the radio access network device, etc.

3) N3: the interface between the wireless access network device and the UPF network element is mainly used for transmitting uplink user plane data and/or downlink user plane data between the wireless access network device and the UPF network element.

4) N4: the interface between the SMF network element and the UPF network element can be used for transferring information between the control plane and the user plane, including controlling the issuing of forwarding rules, qoS rules, flow statistics rules and the like facing the user plane and the information reporting of the user plane.

5) N6: and the interface of the UPF network element and the DN is used for transmitting uplink user data flow and/or downlink user data flow between the UPF network element and the DN.

It will be appreciated that the network elements or functions described above may be either network elements in a hardware device, software functions running on dedicated hardware, or virtualized functions instantiated on a platform (e.g., a cloud platform). Alternatively, the network element or the function may be implemented by one device, or may be implemented by a plurality of devices together, or may be a functional module in one device, which is not specifically limited in the embodiment of the present application.

Fig. 2 is a schematic diagram of a PIN architecture. One PIN contains one or more PIN management network elements, one or more PIN gateway network elements, and one or more PIN element (PIN) network elements. In fig. 2, the PIN includes 1 PIN management network element, 2 PIN gateway network elements, and 4 PIN network elements as examples.

The PIN management network element, also referred to as PIN element with management function (PIN elements with management capability, PEMC) network element, hereinafter abbreviated as PEMC. PEMC is responsible for managing the addition, removal, resource allocation, etc. of elements in PIN (e.g., PINE, PEGC), and PINE Number (PINE Number) may be allocated to PINE in PIN. The PEMC may be a 3GPP terminal device. Wherein the PIN number is identification information of the PIN in the PIN.

The PIN gateway network element is also called a PIN element (PIN elements with gateway capability, PEGC) network element with gateway function, hereinafter abbreviated as PEGC. The PEGC has a gateway function as a transit node between the PIN and the network side, and is responsible for transferring a message from the network (e.g., a 5G core network) to the PEMC or the PIN on the one hand, and transferring a message from the PEMC or the PIN to the network on the other hand. The PEGC may be a 3GPP terminal device.

The PINE network element may be simply referred to as PINE. The PINs may communicate with other PINs, PEMCs or PEGCs within the PIN by device-to-device communication (Device to Device Communication, D2D), such as PC5 connectivity communication, bluetooth communication or wireless fidelity (wireless fidelity, wiFi) communication, but may also be 3GPP based communication. The PINE may be a 3GPP terminal device or a non-3 GPP terminal device.

The PEMC may have a PIN function as a PIN, as well as a PIN management function. Similarly, PEGC may have a PIN function as well as a PIN management function.

In the embodiment of the application, PEGC and PEMC in PIN support PIN element functions (PIN element function, PEF) defined between a transport layer and an application layer, while PIN may or may not support PEF. When the PIN does not support PEF, the PIN may initiate a request to join in the PIN, but when the PIN receives a message related to PEF, the PIN cannot parse the message, the PIN needs to send the message to PEMC/PEGC, and the PEMC/PEGC converts the message into a message with a detachable underlying protocol, and then the PIN/PEGC/PEMC sends the converted message to other PINs.

In the embodiment of the present application, the identification information of the PEGC may be an internet protocol (Internet Protocol, IP) address, a medium access control (medium access control, MAC) address, or a general public subscription identifier (generic public subscription identifier, GPSI) of the PEGC. The identification information of the PINE may be an IP address, a MAC address, a GPSI, or the like of the PINE. The description is unified and not repeated.

Fig. 3 (a) is a flow chart of a message sending method according to an embodiment of the present application, where one pin provides a routing service by one PEGC, and one PEGC may provide a routing service for one or more pins.

The method comprises the following steps:

in step 301a, the upf receives a message, where the message includes an address of the pin.

The message is a message which needs to be sent to the PINE in the PIN, and the address of the PINE in the message is the address of the PINE which receives the message. The address may be an IP address or a MAC address, etc.

Step 302a, upf determines packet detection rules (Packet Detection Rule, PDR) matching the address of the PINE.

The UPF stores a plurality of PDRs and forwarding rules (Forwarding Action Rule, FAR) corresponding to the PDRs. The PDR includes identification information of the pin, which may be an IP address, a MAC address, SUPI, GPSI, or the like. The FAR includes tunnel information of PEGC, which may be N3 tunnel information.

In one implementation, the UPF receives the PDR and the FAR corresponding to the PDR from the SMF. For example, the UPF receives a session request message from the SMF, the session request message including a PDR and a FAR. For another example, the UPF receives a session update message from the SMF, the session update message including a PDR and a FAR.

Illustratively, the UPF stores the following information 1) and 2):

1) The PDR1, the PDR2 and the FAR1, wherein the PDR1 and the FAR1 have a corresponding relation, the PDR2 and the FAR1 have a corresponding relation, the PDR1 comprises identification information of PINE1, the PDR2 comprises identification information of PINE2, and the FAR1 comprises N3 tunnel information of PEGC 1;

2) The PDR3, the PDR4 and the FAR2, wherein the PDR3 and the FAR2 have a corresponding relation, the PDR4 and the FAR2 have a corresponding relation, the PDR3 comprises identification information of PINE3, the PDR4 comprises identification information of PINE4, and the FAR2 comprises N3 tunnel information of PEGC 2.

Thus, in the above example, routing services are provided by PEGC1 for PINE1 and PINE2, and PEGC2 provides routing services for PINE3 and PINE 4.

After the UPF receives the message, the address of the PINE in the message is obtained, and then the PDR matched with the address of the PINE in the message is determined from a plurality of PDRs stored by the UPF. For example, if the message includes the address of PINE1, the UPF determines that the PDR matching the message is PDR1. For another example, if the message includes the address of PINE2, the UPF determines that the PDR matching the message is PDR2.

Step 303a, the UPF sends a message to the PEGC according to the tunnel information of the PEGC in the FAR corresponding to the PDR.

And the UPF further determines the FAR corresponding to the PDR in the PDR matched with the message, and then sends the message to the PEGC according to the tunnel information of the PEGC in the FAR.

For example, in the foregoing example, if the UPF determines that the PDR matching the packet is PDR1, the UPF sends the packet to PEGC1 according to the N3 tunnel information of PEGC 1.

And step 304a, the PEGC sends a message to the PINE.

And after the PEGC receives the message, the message is sent to the PINE according to the address of the PINE in the message. For example, in the foregoing example, if the packet received by PEGC1 includes the address of PINE1, PEGC1 sends the packet to PINE 1.

According to the scheme, the corresponding relation between the PEGC and the PINE is configured by the UPF, the UPF sends the received message which needs to be sent to the PINE to the PEGC according to the corresponding relation, and the PEGC sends the message to the PINE, so that the message can be accurately and quickly sent.

Fig. 3 (b) is a flow chart of a message sending method according to an embodiment of the present application, where one pin is provided with a routing service by multiple PEGCs, and one PEGC may provide a routing service for one or multiple pins. The method comprises the following steps:

in step 301b, the upf receives a message, where the message includes an address of the pin.

Step 302b, upf determines PDR matching the address of PINE.

The UPF stores a plurality of PDRs and a plurality of FARs corresponding to the PDRs. The PDR includes identification information of the pin, which may be an IP address, a MAC address, SUPI, GPSI, or the like. The FAR includes tunnel information of PEGC, which may be N3 tunnel information.

In one implementation, a UPF receives a plurality of PDRs and a plurality of FARs respectively corresponding to the plurality of PDRs from an SMF. As an example, taking a PDR as two FAR, a first FAR and a second FAR, respectively, the UPF may receive a first session request message from the SMF, the first session request message including the PDR and the first FAR, and a second session request message from the SMF, the second session request message including the PDR and the second FAR. Alternatively, the UPF may receive a first session update message from the SMF, the first session update message comprising the PDR and the first FAR, and a second session update message from the SMF, the second session update message comprising the PDR and the second FAR.

Illustratively, UPFs have stored therein PDR1, PDR2, PDR3, PDR4, FAR1, and FAR2. Wherein, PDR1, PDR2, PDR3, PDR4 all have correspondence with FAR1, PDR2, PDR3, PDR4 also all have correspondence with FAR2, PDR1 contains identification information of PINE1, PDR2 contains identification information of PINE2, PDR3 contains identification information of PINE3, PDR4 contains identification information of PINE4, FAR1 contains N3 tunnel information of PEGC1, FAR2 contains N3 tunnel information of PEGC 2.

Thus, in the above example, routing services are provided by PEGC1 for PDR1, PDR2, PDR3, and PDR4, and PEGC2 also provides routing services for PDR1, PDR2, PDR3, and PDR 4. That is, PDR1, PDR2, PDR3, and PDR4 may each provide routing services by PEGC1 and PEGC 2.

In step 303b, the upf determines a plurality of FAR corresponding to the PDR, each FAR of the plurality of FAR including tunnel information of one PEGC.

And the UPF further determines the FAR corresponding to the PDR in the PDR which is determined to be matched with the message. For example, in the foregoing example, if the UPF determines that the PDR matching the packet is PDR1, the UPF determines that the FAR corresponding to PDR1 includes FAR1 and FAR2.

And step 304b, the UPF selects one PEGC from the plurality of PEGC according to loads of the plurality of PEGC corresponding to the plurality of FARs.

In one implementation, the UPF selects one PEGC with the lightest load from among the PEGCs, and routes the packet from the PEGC to the pin. In another implementation method, the UPF randomly selects one PEGC from N PEGCs with the lightest load among the plurality of PEGCs, where N is an integer greater than 1, and routes the packet from the selected PEGC to the pin.

Taking the foregoing example as an example, if the UPF determines that the PDR matched with the packet is PDR1, the UPF selects one PEGC with a lighter load from PEGC1 and PEGC2, for example, PEGC1 is loaded with a lighter load, and the UPF selects PEGC1.

Step 305b, the UPF sends the message to the selected PEGC according to the tunnel information of the selected PEGC.

For example, in the foregoing example, if the UPF selects PEGC1 from PEGC1 and PEGC2, the UPF sends the received message to PEGC1.

In step 306b, the pegc sends a message to the PINE.

And after the PEGC receives the message, the message is sent to the PINE according to the address of the PINE in the message. For example, in the foregoing example, if the UPF sends a packet to PEGC1, where the packet includes the address of PINE1, PEGC1 sends the packet to PINE 1.

According to the scheme, the UPF configures the corresponding relation between the PEGC and the PINE, and the UPF sends the received message to be sent to the PINE to the PEGC according to the corresponding relation and the load of the PEGC, so that the PEGC sends the message to the PINE, and the realization of correct and rapid sending of the message is facilitated.

Fig. 3 (c) is a flow chart of a PIN management method according to an embodiment of the present application, where the method is used to configure a correspondence between PEGC and PIN for UPF.

The method comprises the following steps:

At step 301c, the smf receives a session establishment request message from the PEGC, the session establishment request message requesting establishment of a session, the session establishment request message including indication information indicating that the session is a PIN session.

The session establishment request message may be a PDU session establishment request message.

And step 302c, the SMF sends a request message to the PNF according to the indication information, wherein the request message comprises the identification information of the PEGC, and the request message is used for acquiring the identification information of the PINE corresponding to the PEGC.

The indication information triggers the SMF to send a request message to the PNF for acquiring the identification information of the PINE corresponding to the PEGC.

The PNF stores the correspondence between the PEGC identification information and the PINE identification information. One PEGC may provide a routing service for a plurality of pins, and thus, there may be a correspondence between identification information of one PEGC and identification information of a plurality of pins.

The correspondence between PEGC identification information stored on the PNF and pin identification information may be determined by the PEMC and sent to the PNF.

In step 303c, the smf receives identification information of a pin corresponding to the PEGC from the PNF.

The PNF transmits identification information of PINE corresponding to the identification information of PEGC to the PNF according to the request of the SMF.

In step 304c, the smf transmits tunnel information of the PEGC and identification information of the PINE corresponding to the PEGC to the UPF.

The tunnel information of the PEGC may be N3 tunnel information, where the N3 tunnel is allocated by the SMF, and is used for packet transmission between the UPF and the PEGC.

In an implementation method, the step 304c may specifically be: the SMF may transmit at least one PDR including identification information of one pin among identification information of pins corresponding to the PEGC, respectively, and a FAR corresponding to the at least one PDR including tunnel information of the PEGC, to the UPF. For example, the SMF may send a session request message to the UPF, the session request message including at least one PDR and a FAR corresponding to the at least one PDR, or the SMF may send a session update message to the UPF, the session update message including at least one PDR and a FAR corresponding to the at least one PDR.

For example, assuming that the SMF needs to send tunnel information of PEGC1 and identification information of PINE1, identification information of PINE2, and identification information of PINE3 corresponding to PEGC1 to the UPF, the SMF may send PDR1, PDR2, PDR3, and FAR1 to the UPF, where PDR1 includes identification information of PINE1, PDR2 includes identification information of PINE2, PDR3 includes identification information of PINE3, and FAR1 includes tunnel information of PEGC 1.

The above scheme is implemented as that the UPF configures the correspondence between PEGC and pin, so that the UPF can send the received message to be sent to the pin to the PEGC according to the correspondence, and the PEGC sends the message to the pin, thereby being beneficial to implementing the correct and rapid sending of the message.

If the SMF receives the updated pin identification information corresponding to the PEGC from the PNF, the SMF may transmit the tunnel information of the PEGC and the updated pin identification information to the UPF. Specifically, the SMF may send a session update message to the UPF, the session update message including at least one PDR and a FAR corresponding to the at least one PDR, each PDR of the at least one PDR including identification information of one updated pin, the FAR including tunnel information of the PEGC. Illustratively, assuming that a PINE corresponding to PEGC1 is updated to be PINE1, PINE2, and PINE4 by PINE1, PINE2, and PINE3, the SMF receives the identification information of PEGC1, the identification information of PINE2, and the identification information of PINE3 from the PNF, and then the SMF transmits FAR1, PDR2, and PDR4 to the UPF, wherein PDR1 includes the identification information of PINE1, PDR2 includes the identification information of PINE2, PDR4 includes the identification information of PINE4, and FAR1 includes tunnel information of PEGC 1.

Fig. 3 (d) is a flow chart of a PIN management method according to an embodiment of the present application, where the method includes the following steps:

in step 301d, the pemc receives a first notification message from the first PEGC, where the first notification message includes identification information of the first PEGC, identification information of the pin, and indication information, where the indication information indicates that the first PEGC cannot route a message of the pin.

For example, since the first PEGC is overloaded, i.e., the load exceeds the load threshold, or the first PEGC fails, the first PEGC sends a first notification message to the PEMC to notify the PEGC: the first PEGC cannot route messages of the PINE, which is currently provided with the routing service by the first PEGC.

In step 302d, the pemc sends a second notification message to the second PEGC, where the second notification message includes identification information of the PINE, and the second notification message indicates that the second PEGC provides a routing service for the PINE.

After the PEMC receives the first notification message, if it is determined that the first PEGC cannot provide the routing service for the PINE, one PEGC may be reselected for the PINE, and the reselected PEGC is referred to as a second PEGC. The second PEGC may be one UE (may be referred to as a target UE) newly joining the PIN, may be one of the PINs provided by the first PEGC for the routing service, or may be PEMC.

In one implementation, the PEMC sends a request message to the PNF, where the request message includes identification information of the PIN, the request message requests that one PEGC be selected for the PIN, and then the PNF sends identification information of the selected PEGC, that is, identification information of the second PEGC, to the PEMC. In another implementation, one PEGC is reselected by the PEMC as the second PEGC.

The PEGC obtains the identification information of the second PEGC, and then sends a second notification message to the second PEGC to instruct the second PEGC to provide routing services for the PINE.

In step 303d, the pemc sends a third notification message to the PINE, where the third notification message includes identification information of the second PEGC, and the third notification message indicates that the second PEGC provides a routing service for the PINE.

According to the scheme, when the PEGC is overloaded and cannot provide routing service for one or some PINs, one PEGC can be reselected, and the newly selected PEGC provides routing service for the one or more PINs, so that load balancing among a plurality of PEGs is realized, and correct and rapid sending of the message is facilitated.

The embodiments of fig. 3 (a) to 3 (d) described above will be described below with reference to specific examples shown in fig. 4 to 7. The following embodiment of fig. 4 is a specific example of the embodiment of fig. 3 (a) and fig. 3 (c) described above. The following embodiment of fig. 5 is a specific example of the embodiment of fig. 3 (a) and fig. 3 (c) described above in combination. The following embodiment of fig. 6 is a specific example of the embodiment of fig. 3 (b) and fig. 3 (c) described above in combination. The following embodiment of fig. 7 is a specific example of the embodiment of fig. 3 (a) and fig. 3 (d) described above, or the embodiment of fig. 3 (b) and fig. 3 (d) described above.

Fig. 4 is a flow chart of a PIN management method according to an embodiment of the present application. Taking the PIN architecture shown in fig. 2 as an example, the PEMC establishes and manages PINs, the PINs include PEGC1 and PEGC2, and PEGC1 provides routing services for PINE1 and PINE2, and PEGC2 provides routing services for PINE3 and PINE 4. A context is established in the PEMC, and the context includes a correspondence 1 between the identification information of the PEGC1 and the identification information of the PINE2, and a correspondence 2 between the identification information of the PEGC2 and the identification information of the PINE3 and the identification information of the PINE 4.

The following description will take the configuration of the correspondence relation 1 for the UPF as an example. The method for configuring the corresponding relation 2 for the UPF is similar to the method for configuring the corresponding relation 1 for the UPF, and will not be described again.

The method comprises the following steps:

in step 401, the pemc sends configuration information to the AMF, where the configuration information includes the identification information of PEGC1, the identification information of PINE1, and the identification information of PINE 2.

Wherein the PINE1 and the PINE2 are provided with a routing service by the PEGC1, and the PEMC determines that the PEGC1 provides the routing service for the PINE1 and the PINE 2.

In an implementation method, the step 401 specifically includes: the PEMC sends a NAS message to the AMF, which carries the configuration information described above.

In yet another implementation method, the step 401 specifically includes: the PEMC sends NAS information to the AMF, wherein the NAS information comprises a PIN container, the PIN container carries the configuration information, or the PIN container is the configuration information.

In step 402, the amf sends configuration information to the PNF.

That is, the AMF forwards the received configuration information to the PNF, which records the configuration information.

An implementation method, the AMF sends a PNF service request message to the PNF, where the PIN NF service request message includes the configuration information.

In step 403, the pnf sends a response message to the AMF.

In one implementation, the response message is a PNF service response message.

This step is an optional step.

At step 404, the AMF sends a response message to the PEMC.

In one implementation, this step 404 may be: the AMF sends a NAS message to the PEMC, the NAS message including the response message.

In yet another implementation, the step 404 may be: the AMF sends a NAS message to the PEMC, the NAS message including a PIN container containing the response message.

This step is an optional step.

In step 405, pegc1 sends a PDU session establishment request message to the SMF, the PDU session establishment request message being used to request establishment of a PDU session.

The PDU session request message carries indication information indicating that the PDU session is a PIN session or that the PDU session is for a PIN.

In step 406, the smf sends a request message to the PNF according to the indication information, where the request message includes identification information of PEGC1, and the request message is used to obtain identification information of a pin corresponding to PEGC 1.

That is, the SMF is triggered to request the PNF to acquire the identification information of the pin corresponding to PEGC 1.

In step 407, the pnf sends configuration information to the SMF, where the configuration information includes the identification information of PEGC1, the identification information of PINE1, and the identification information of PINE 2.

In step 408, the smf sends an N4 session request message to the UPF, the N4 session request message including session configuration information.

The session configuration information includes PDR1, PDR2, and FAR, the PDR1 includes identification information of PINE1, the PDR2 includes identification information of PINE2, and the FAR includes N3 tunnel information of PEGC 1. Wherein, there is a correspondence between PDR1 and FAR, and a correspondence between PDR2 and FAR.

Step 409, the upf sends an N4 session response message to the SMF.

This step 409 is an optional step.

In step 410, the smf sends a PDU session establishment response message to PEGC 1.

Subsequently, when the UPF receives the downlink message, if the destination address in the downlink message is the address of the PINE1, the downlink message may be matched to the PDR1, then the UPF sends the downlink message to the PEGC1 through the N3 tunnel of the PEGC1 according to the FAR corresponding to the PDR1, and then the PEGC1 sends the downlink message to the PINE1.

When the UPF receives the downlink message, if the destination address in the downlink message is the address of the PINE2, the downlink message may be matched to the PDR2, then the UPF sends the downlink message to the PEGC1 through the N3 tunnel of the PEGC1 according to the FAR corresponding to the PDR2, and then the PEGC1 sends the downlink message to the PINE2.

In the embodiment of fig. 4, the routing service provided by only one PEGC per pin is described as an example. Of course, each pin may also be provided with a routing service by two or more PEGCs, in which, in this scenario, in combination with the embodiment of fig. 4, configuration information sent by the PEMC to the PNF via the AMF includes one or more pins 'identification information, one or more PEGCs' identification information, and a correspondence between pin's identification information and PEGC's identification information, where one pin's identification information may correspond to one or more PEGCs' identification information, and one PEGC's identification information may correspond to one or more pins' identification information. Subsequently, when the SMF receives PDU session establishment request messages initiated by multiple PEGCs, if the SMF determines that the multiple PEGCs all correspond to the same pin, the SMF may select one PEGC from the multiple PEGCs, provide a routing service for the pin by the selected PEGC, and then send a correspondence between identification information of the selected PEGC and identification information of the pin to the UPF.

Fig. 5 is a flow chart of a PIN management method according to an embodiment of the present application. Taking the PIN architecture shown in fig. 2 as an example, the PEMC establishes and manages PINs, the PINs include PEGC1 and PEGC2, and PEGC1 provides routing services for PINE1 and PINE2, and PEGC2 provides routing services for PINE3 and PINE 4. A context is established in the PEMC, and the context includes a correspondence 1 between the identification information of the PEGC1 and the identification information of the PINE2, and a correspondence 2 between the identification information of the PEGC2 and the identification information of the PINE3 and the identification information of the PINE 4.

Subsequently, for some reason, such as that PEGC1 is overloaded, and PEMC determines that PEGC2 is lightly loaded, then PEMC determines to provide PEGC1 with routing service for PINE1, and updates PEGC2 to provide routing service for PINE 1. Therefore, before updating, PEGC1 provides routing services for PINE1 and PINE2, PEGC2 provides routing services for PINE3 and PINE4, and after updating, PEGC1 provides routing services for PINE2, PEGC2 provides routing services for PINE1, PINE3 and PINE 4. The load is excessive, for example, the load exceeds the load threshold 1, that is, the amount of messages to be processed in a period of time exceeds the load threshold 1. The load is lighter, such as the load is lower than the load threshold 2, i.e. the amount of messages that need to be processed in a period of time is lower than the load threshold 2. The load threshold 1 is greater than the load threshold 2.

The method comprises the following steps:

in step 501, the pemc sends configuration information to the AMF.

In an implementation method, the configuration information includes identification information of PEGC1, identification information of PEGC2, identification information of PINE1, and indication information indicating that PEGC1 provides a routing service for PINE1 to PEGC2 provides a routing service for PINE 1.

In another implementation method, the configuration information includes identification information of PEGC1 and identification information of PINE2 corresponding to the PEGC1, and also includes identification information of PEGC2 and identification information of PINE1, identification information of PINE3 and identification information of PINE4 corresponding to the PEGC 2.

In an implementation method, the step 501 specifically includes: the PEMC sends a NAS message to the AMF, the NAS message including the above configuration information.

In yet another implementation method, the step 501 specifically includes: the PEMC sends NAS information to the AMF, wherein the NAS information comprises a PIN container, the PIN container carries the configuration information, or the PIN container is the configuration information.

Before step 501, PEGC1 may further send a notification message to PEMC, where the notification message includes the identification information of PEGC1, the identification information of PINE1, and the indication information, where the indication information indicates that PEGC1 cannot route the packet of PINE 1. And then the PEMC re-selects a PEGC2 with lighter load for the PINE1 according to the notification message, wherein the PEGC2 provides routing service for the PINE1, namely the PEMC determines that the PEGC2 has the capability of providing routing service for the PINE1, and the PEMC determines that the PEGC2 provides routing service for the PINE 1.

In step 502, the amf sends configuration information to the PNF.

That is, the AMF forwards the received configuration information to the PNF. Before step 501, the PNF stores the identification information of PEGC1, the identification information of PINE1 and the identification information of PINE2 corresponding to the PEGC1, and also stores the identification information of PEGC2, the identification information of PINE3 and the identification information of PINE4 corresponding to the PEGC 2. The PNF updates the locally stored information according to the configuration information received in step 502, where the updated information includes: the identification information of PEGC1 and the identification information of PINE2 corresponding to the PEGC1, and also includes the identification information of PEGC2 and the identification information of PINE1, the identification information of PINE3, and the identification information of PINE4 corresponding to the PEGC 2.

An implementation method, this step 502 specifically is: the AMF sends a PNF service request message to the PNF, the PIN NF service request message including the configuration information.

At step 503, the pnf sends a response message to the AMF.

In one implementation, the response message is a PNF service response message.

This step is an optional step.

At step 504, the AMF sends a response message to the PEMC.

In one implementation, this step 504 may be: the AMF sends a NAS message to the PEMC, the NAS message including the response message.

In yet another implementation, the step 504 may be: the AMF sends a NAS message to the PEMC, the NAS message including a PIN container containing the response message.

This step is an optional step.

In step 505, the pnf sends configuration information to the SMF.

At step 506, the smf sends a response message to the PNF.

This step 506 is an optional step.

In step 507, the smf sends an N4 session update message to the UPF, the N4 session update message including session configuration information.

The session configuration information includes PDR1, PDR2, PDR3, PDR4, FAR1, and FAR2, the PDR1 includes identification information of PINE1, the PDR2 includes identification information of PINE2, the PDR3 includes identification information of PINE3, the PDR4 includes identification information of PINE4, the FAR1 includes N3 tunnel information of PEGC1, and the FAR2 includes N3 tunnel information of PEGC 2. Wherein, there is a correspondence between PDR2 and FAR1, and there is a correspondence between PDR1, PDR3 and PDR4 and FAR 2.

Step 508, the upf sends an N4 session response message to the SMF.

This step 508 is an optional step.

Subsequently, when the UPF receives the downlink message, if the destination address in the downlink message is the address of the PINE1, the downlink message may be matched to the PDR1, then the UPF sends the downlink message to the PEGC2 through the N3 tunnel of the PEGC2 according to the FAR2 corresponding to the PDR1, and then the PEGC2 sends the downlink message to the PINE1.

When the UPF receives the downlink message, if the destination address in the downlink message is the address of the PINE2, the downlink message may be matched to the PDR2, then the UPF sends the downlink message to the PEGC1 through the N3 tunnel of the PEGC1 according to the FAR1 corresponding to the PDR2, and then the PEGC1 sends the downlink message to the PINE2.

When the UPF receives the downlink message, if the destination address in the downlink message is the address of the PINE3, the downlink message may be matched to the PDR3, then the UPF sends the downlink message to the PEGC2 through the N3 tunnel of the PEGC2 according to the FAR2 corresponding to the PDR3, and then the PEGC2 sends the downlink message to the PINE3.

When the UPF receives the downlink message, if the destination address in the downlink message is the address of the PINE4, the downlink message may be matched to the PDR4, then the UPF sends the downlink message to the PEGC2 through the N3 tunnel of the PEGC2 according to the FAR2 corresponding to the PDR4, and then the PEGC2 sends the downlink message to the PINE4.

The scheme is realized in that the UPF updates the corresponding relation between the PEGC and the PINE, and the UPF sends the received message which needs to be sent to the PINE to the PEGC according to the updated corresponding relation, and the PEGC sends the message to the PINE to realize the correct and rapid sending of the message.

It should be noted that, if the PEGC1 fails, all pins of the PEGC1 service, that is, the pins 1 and the pins 2, may be updated to provide the routing service by the PEGC2, and the implementation process is similar to the above scheme and will not be repeated.

In the embodiment of fig. 5, the routing service provided by only one PEGC per pin is described as an example. Of course, each pin may also be provided with a routing service by two or more PEGCs, in which, in this scenario, in combination with the embodiment of fig. 5, configuration information sent by the PEMC to the PNF via the AMF includes one or more pins 'identification information, one or more PEGCs' identification information, and a correspondence between pin's identification information and PEGC's identification information, where one pin's identification information may correspond to one or more PEGCs' identification information, and one PEGC's identification information may correspond to one or more pins' identification information. Subsequently, when the SMF receives PDU session establishment request messages initiated by multiple PEGCs, if the SMF determines that the multiple PEGCs all correspond to the same pin, the SMF may select one PEGC from the multiple PEGCs, provide a routing service for the pin by the selected PEGC, and then send a correspondence between identification information of the selected PEGC and identification information of the pin to the UPF.

Fig. 6 is a flow chart of a PIN management method according to an embodiment of the present application. In this embodiment, the PEMC establishes and manages a PIN including PEGC1 and PEGC2, and PEGC1 provides routing services for PINE1, PINE2, PINE3, and PINE4, and PEGC2 also provides routing services for PINE1, PINE2, PINE3, and PINE 4. A context is established in the PEMC, and the context includes a correspondence 1 between the identification information of the PEGC1 and the identification information of the PINE1, the identification information of the PINE2, the identification information of the PINE3, and the identification information of the PINE4, and a correspondence 2 between the identification information of the PEGC2 and the identification information of the PINE1, the identification information of the PINE2, the identification information of the PINE3, and the identification information of the PINE 4.

The method comprises the following steps:

in step 601, the pemc sends configuration information to the AMF, where the configuration information includes identification information of PEGC1, identification information of PEGC2, identification information of PINE1, identification information of PINE2, identification information of PINE3, and identification information of PINE 4.

In an implementation method, the step 601 specifically includes: the PEMC sends a NAS message to the AMF, the NAS message including the above configuration information.

In yet another implementation method, the step 601 specifically includes: the PEMC sends NAS information to the AMF, wherein the NAS information comprises a PIN container, the PIN container carries the configuration information, or the PIN container is the configuration information.

In step 602, the amf sends configuration information to the PNF.

In step 603, the pnf sends a response message to the AMF.

In one implementation, the response message is a PNF service response message.

This step is an optional step.

The amf sends a response message to the PEMC, step 604.

In one implementation, this step 604 may be: the AMF sends a NAS message to the PEMC, the NAS message including the response message.

In yet another implementation, the step 604 may be: the AMF sends a NAS message to the PEMC, the NAS message including a PIN container containing the response message.

This step is an optional step.

In step 605, pegc1 sends a PDU session establishment request message to the SMF, the PDU session establishment request message requesting establishment of a PDU session.

In step 606, the smf sends a request message to the PNF according to the indication information, where the request message includes identification information of PEGC1, and the request message is used to obtain identification information of a pin corresponding to PEGC 1.

In step 607, the pnf transmits configuration information to the SMF, where the configuration information includes identification information of PEGC1, identification information of PINE2, identification information of PINE3, and identification information of PINE 4.

At step 608, the smf sends an N4 session request message to the UPF, the N4 session request message including session configuration information.

The session configuration information includes PDR1, PDR2, PDR3, PDR4, and FAR1, the PDR1 includes identification information of PINE1, the PDR2 includes identification information of PINE2, the PDR3 includes identification information of PINE3, the PDR4 includes identification information of PINE4, and the FAR1 includes N3 tunnel information of PEGC 1. Wherein, PDR1, PDR2, PDR3 and PDR4 have corresponding relations with FAR 1.

The upf sends an N4 session response message to the SMF, step 609.

This step 609 is an optional step.

At step 610, the smf sends a PDU session establishment response message to PEGC 1.

For PEGC2, steps similar to the above steps 605 to 610 are also performed, which are not shown in fig. 6, so that PDR1, PDR2, PDR3, PDR4, and FAR2 are configured for UPF, the FAR2 includes N3 tunnel information of PEGC2, and PDR1, PDR2, PDR3, PDR4 each have a correspondence with FAR 2.

Subsequently, when the UPF receives the downlink message, if the destination address in the downlink message is the address of the pin 1, the downlink message may be matched to the PDR1, the UPF determines that the PDR1 corresponds to the FAR1 and the FAR2, and then the UPF selects the PEGC with lighter load from the PEGC1 and the PEGC 2. If the load of the PEGC1 is lighter, the UPF sends the downlink message to the PEGC1 through an N3 tunnel of the PEGC1 according to the FAR1 corresponding to the PDR, and then the PEGC1 sends the downlink message to the PINE1. If the PEGC2 is lightly loaded, the UPF sends the downlink message to the PEGC2 through the N3 tunnel of the PEGC2 according to the FAR2 corresponding to the PDR, and then the PEGC2 sends the downlink message to the PINE1. The UPF may determine the load of PEGC1 according to the load of the session of PEGC1, and determine the load of PEGC2 according to the load of the session of PEGC 2.

If the destination address in the downlink message received by the UPF is the address of the PINE2, the address of the PINE3 or the address of the PINE4, the UPF performs similar processing, and will not be described again.

According to the scheme, the UPF can dynamically select the PEGC with lighter load according to the loads of the PEGC, and send the message to the PINE through the PEGC, so that the message can be sent correctly and quickly.

In an implementation method, in the embodiments of fig. 4 to fig. 6, the configuration information sent by the PEMC to the PNF may further include aging information, where the aging information is used to indicate a validity period of a pin in the configuration information, or indicate a validity period of a correspondence between the PEGC and the pin in the configuration information. The PNF receives configuration information from the PEMC, and if the configuration information comprises aging information, the PNF manages the corresponding relation between the PEGC and the PINE according to the aging information. If the configuration information does not include age information, the PNF may also determine age information by itself, where the age information is used to indicate a validity period of a PINE in the configuration information or indicate a validity period of a correspondence between PEGC and a PINE in the configuration information. And then the PNF manages the corresponding relation between the PEGC and the PINE according to the aging information. The PNF manages the correspondence between PEGC and PINE, for example: when the correspondence between a certain PEGC and a certain PIN exceeds the validity period, or the PIN joining time has exceeded the validity period, the PNF may delete the correspondence.

Fig. 7 is a flow chart of a PIN management method according to an embodiment of the present application. In this embodiment, the PEMC establishes and manages a PIN including PEGC1 therein, and PEGC1 provides routing services for PINE1, PINE2, and PINE 3. A context is established in the PEMC, and the context includes a correspondence between the identification information of the PEGC1 and the identification information of the PINE1, the identification information of the PINE2, and the identification information of the PINE 3.

The method comprises the following steps:

in step 701, pegc1 determines that the load is too heavy to route the packet of PINE 1.

Here, the load is too heavy, for example, the load exceeds a load threshold, that is, the amount of messages that need to be processed in a period of time exceeds the load threshold.

The inability to route the message of the PINE1 means that when the PEGC1 receives the message from the PINE1, the message cannot be transmitted to the outside, or the PEGC1 receives the message to be sent to the PINE1, and the message cannot be sent to the PINE 1.

In step 702, the PEGC sends a notification message to the PEMC, where the notification message includes the identification information of the PEGC1, the identification information of the PINE1, and the indication information, where the indication information indicates that the PEGC1 cannot route the packet of the PINE 1.

In step 703, the pemc sends a request message to the PNF, the request message including identification information of the PIN, the request message requesting selection of one PEGC.

In step 704, the PNF determines UE-A as PEGC2.

Specifically, the PNF initially selects UE-A as PEGC2, and then the PNF transmits a query message to the UDM, the query message including identification information of the UE-A, the query message requesting a query as to whether the UE-A is authorized to be used as PEGC. If the UE-A is authorized to be used as PEGC, the UDM sends a query result to the PNF, the query result being that UE2 is authorized to be used as PEGC, so that the PNF determines the UE-A as PEGC2.

The identification information of one or more UEs capable of functioning as PEGC stored in the UDM may be that the UE registers with the UDM in the registration procedure.

In step 705, the pnf transmits a notification message to the UE-a, the notification message including identification information of the PIN, identification information of the PEMC, and indication information indicating the UE-a as the PEGC.

In step 706, the UE-A sends a request message to the PEMC, the request message including identification information of the UE-A and identification information of the PIN, the request message requesting to join the PIN.

In step 707, the PEMC sends a response message to the UE-A indicating that the UE-A is authorized to join the PIN.

In step 708, the pemc sends a notification message to the PINE1, the notification message including identification information of the PEGC2, the notification message indicating that the PEGC2 provides a routing service for the PINE 1.

The identification information of PEGC2 is the identification information of the UE-A. The UE-A is PEGC2.

Subsequently, when the PINE1 needs to send the message to the outside, the PINE1 sends the message to the PEGC2, and the PEGC2 forwards the message to the outside.

In step 709, the pemc transmits a notification message to the UE-a (i.e., PEGC 2), the notification message including identification information of the PINE1, the notification message indicating that the UE-a (i.e., PEGC 2) provides a routing service for the PINE 1.

Subsequently, when the PEGC2 receives the message from the PINE1, the message is forwarded to the outside.

Optionally, the PEMC may further configure the updated correspondence between the PEGC and the pin to the UPF, so that when the UPF receives a message that needs to be sent to the pin 1 in the downlink direction, the message is sent to the PEGC2, and is not sent to the PEGC1 any more. The implementation method of configuring the updated correspondence between PEGC and pin by the PEMC to UPF is similar to the embodiment of fig. 5, and will not be described again.

In the embodiment of fig. 7 described above, a new PEGC, PEGC2, is selected by the PNF. As another implementation method, a new PEGC may be selected by the PEMC, that is, PEGC2, for example, the PEMC selects UE-a as PEGC2, then the PEMC carries the identification information of the pin and the identification information of the UE-a in the request message of step 703, and then step 704 is replaced with: the PNF determines whether UE-a is authorized for PEGC, and if so, proceeds to steps 705 to 709 described above. The method for judging whether the UE-A is authorized to be used as the PEGC by the PNF can be as follows: the PNF sends a query message to the UDM, the query message including identification information of the UE-a, the query message requesting a query as to whether the UE-a is authorized to be used as PEGC. If the UE-A is authorized to be used as PEGC, the UDM sends a query result to the PNF, the query result being that UE2 is authorized to be used as PEGC, so that the PNF determines the UE-A as PEGC2.

In the embodiment of fig. 7 described above, a new UE is selected by the PNF as PEGC2. As still another implementation method, a certain PIN may be selected by the PNF or the PEMC as the PEGC2, for example, a PIN 1, a PIN 2, a PIN 3, or a PIN 4 may be selected as the PEGC2, or a PEMC may be selected as the PEGC2, that is, the PEMC has the functions of managing PINs and providing routes at the same time.

It will be appreciated that, in order to implement the functions in the above embodiments, the user plane network element, the session management network element or the PIN management network element comprises corresponding hardware structures and/or software modules for performing the respective functions. Those of skill in the art will readily appreciate that the various illustrative elements and method steps described in connection with the embodiments disclosed herein may be implemented as hardware or combinations of hardware and computer software. Whether a function is implemented as hardware or computer software driven hardware depends upon the particular application scenario and design constraints imposed on the solution.

Fig. 8 and 9 are schematic structural diagrams of a possible communication device according to an embodiment of the present application. These communication devices may be used to implement the functions of the user plane network element, the session management network element, or the PIN management network element in the above method embodiments, so that the beneficial effects of the above method embodiments may also be implemented. In the embodiment of the application, the communication device may be a user plane network element, a session management network element or a PIN management network element, or may be a module (such as a chip) in the user plane network element, a module (such as a chip) in the session management network element or a module (such as a chip) in the PIN management network element.

The communication device 800 shown in fig. 8 includes a processing unit 810 and a transceiving unit 820. The communication device 800 is configured to implement the functions of the user plane network element, the session management network element, or the PIN management network element in the above-described method embodiment. The transceiver unit 820 may be used to implement corresponding communication functions. The transceiver unit 820 may also be referred to as a communication interface or a communication unit. The processing unit 810 may be adapted to implement corresponding processing functions. Optionally, the communication device 800 further includes a storage unit, where the storage unit may be configured to store instructions and/or data, and the processing unit 810 may read the instructions and/or data in the storage unit, so that the communication device 800 implements actions of the user plane network element, the session management network element, or the PIN management network element in the foregoing method embodiments.

When the communication device 800 is configured to implement the function of the user plane network element in the above method embodiment, the transceiver unit 820 is configured to receive a packet, where the packet includes an address of the PIN element network element; a processing unit 810, configured to determine a packet detection rule matching the address of the PIN element network element; the transceiver 820 is further configured to send the packet to the PIN gateway network element according to the tunnel information of the PIN gateway network element in the forwarding rule corresponding to the packet detection rule.

In a possible implementation method, the transceiver unit 820 is further configured to receive the packet detection rule and the forwarding action rule from the session management network element.

In a possible implementation method, the transceiver unit 820 is specifically configured to receive a session request message from the session management network element, where the session request message includes the packet detection rule and the forwarding action rule; or receiving a session update message from the session management network element, the session update message including the packet detection rule and the forwarding action rule.

When the communication device 800 is configured to implement the function of the user plane network element in the above method embodiment, the transceiver unit 820 is configured to receive a packet, where the packet includes an address of the PIN element network element; a processing unit 810, configured to determine a packet detection rule matching the address of the PIN element network element; determining a plurality of forwarding action rules corresponding to the packet detection rules, each forwarding action rule of the plurality of forwarding action rules including tunnel information of a PIN gateway network element; selecting a PIN gateway network element from the PIN gateway network elements according to loads of the PIN gateway network elements corresponding to the forwarding action rules; the transceiver unit 820 is further configured to send the message to the selected PIN gateway network element according to the tunnel information of the selected PIN gateway network element.

In a possible implementation method, the transceiver unit 820 is further configured to receive the packet detection rule and the forwarding action rules from the session management network element.

In one possible implementation, the plurality of forwarding action rules includes a first forwarding action rule and a second forwarding action rule; a transceiver unit 820, configured to receive a first session request message from the session management network element, where the first session request message includes the packet detection rule and the first forwarding operation rule; a second session request message is received from the session management network element, the second session request message comprising the packet detection rule and the second forwarding action rule.

In one possible implementation, the plurality of forwarding action rules includes a first forwarding action rule and a second forwarding action rule; a transceiver unit 820, configured to receive a first session update message from the session management network element, where the first session update message includes the packet detection rule and the first forwarding operation rule; a second session update message is received from the session management network element, the second session update message including the packet detection rule and the second forwarding action rule.

In a possible implementation method, the processing unit 810 is specifically configured to select, according to loads of the plurality of PIN gateway network elements, a PIN gateway network element with a lightest load from the plurality of PIN gateway network elements; or according to the loads of the PIN gateway network elements, randomly selecting one PIN gateway network element from N PIN gateway network elements with the lightest loads in the PIN gateway network elements, wherein N is an integer larger than 1.

When the communication device 800 is configured to implement the function of the session management network element in the above method embodiment, the transceiver unit 820 is configured to receive a session establishment request message from the PIN gateway network element, where the session establishment request message requests to establish a session, and the session establishment request message includes indication information, where the indication information indicates that the session is a PIN session; a processing unit 810, configured to send a request message to a PIN network function network element according to the indication information, where the request message includes identification information of the PIN gateway network element, and the request message is used to obtain identification information of a PIN element network element corresponding to the PIN gateway network element; a transceiver unit 820, configured to receive identification information of a PIN element network element corresponding to the PIN gateway network element from the PIN network function network element; and transmitting the tunnel information of the PIN gateway network element and the identification information of the PIN element network element corresponding to the PIN gateway network element to the user plane network element.

In a possible implementation method, the transceiver unit 820 is specifically configured to send at least one packet detection rule and a forwarding action rule corresponding to the at least one packet detection rule to the user plane network element, where the at least one packet detection rule includes identification information of one PIN element network element in identification information of the PIN element network element corresponding to the PIN gateway network element, and the forwarding action rule includes tunnel information of the PIN gateway network element.

In a possible implementation method, the transceiver unit 820 is specifically configured to send a session request message to the user plane network element, where the session request message includes the at least one packet detection rule and the forwarding action rule; or, sending a session update message to the user plane network element, the session update message comprising the at least one packet detection rule and the forwarding action rule.

In a possible implementation method, the transceiver unit 820 is further configured to receive identification information of an updated PIN element network element corresponding to the PIN gateway network element from the PIN network function network element; and transmitting the tunnel information of the PIN gateway network element and the identification information of the updated PIN element network element to the user plane network element.

When the communication device 800 is configured to implement the function of the PIN management network element in the above method embodiment, the transceiver unit 820 is configured to receive a first notification message from a first PIN gateway network element, where the first notification message includes identification information of the first PIN gateway network element, identification information of a PIN element network element, and indication information, where the indication information indicates that the first PIN gateway network element cannot route a packet of the PIN element network element; sending a second notification message to a second PIN gateway network element, wherein the second notification message comprises identification information of the PIN element network element, and the second notification message indicates that the second PIN gateway network element provides routing service for the PIN element network element; and sending a third notification message to the PIN element network element, wherein the third notification message comprises the identification information of the second PIN gateway network element, and the third notification message indicates that the second PIN gateway network element provides routing service for the PIN element network element.

In a possible implementation method, the processing unit 810 is configured to select the target UE as the second PIN gateway network element.

In a possible implementation method, the processing unit 810 is configured to select the PIN management network element as the second PIN gateway network element.

In a possible implementation method, the transceiver unit 820 is further configured to send a request message to the PIN network function network element, where the request message includes identification information of the PIN, and the request message requests to select a PIN gateway network element for the PIN.

The more detailed descriptions of the processing unit 810 and the transceiver unit 820 may be directly obtained by referring to the related descriptions in the above method embodiments, and are not repeated herein.

The communication device 900 shown in fig. 9 includes a processor 910 and an interface circuit 920. The processor 910 and the interface circuit 920 are coupled to each other. It is understood that the interface circuit 920 may be a transceiver or an input-output interface. Optionally, the communication device 900 may further include a memory 930 for storing instructions executed by the processor 910 or for storing input data required by the processor 910 to execute the instructions or for storing data generated after the processor 910 executes the instructions.

When the communication device 900 is used to implement the above-mentioned method embodiments, the processor 910 is used to implement the functions of the above-mentioned processing unit 810, and the interface circuit 920 is used to implement the functions of the above-mentioned transceiver unit 820.

It is to be appreciated that the processor in embodiments of the application may be a central processing unit (central processing unit, CPU), other general purpose processor, digital signal processor (digital signal processor, DSP), application specific integrated circuit (application specific integrated circuit, ASIC), field programmable gate array (field programmable gate array, FPGA) or other programmable logic device, transistor logic device, hardware components, or any combination thereof. The general purpose processor may be a microprocessor, but in the alternative, it may be any conventional processor.

The method steps in the embodiments of the present application may be implemented by hardware, or may be implemented by executing software instructions by a processor. The software instructions may be comprised of corresponding software modules that may be stored in random access memory, flash memory, read only memory, programmable read only memory, erasable programmable read only memory, electrically erasable programmable read only memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. The processor and the storage medium may reside as discrete components in a base station or terminal.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are performed in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, a base station, a user equipment, or other programmable apparatus. The computer program or instructions may 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 program or instructions may be transmitted from one website site, computer, server, or data center to another website site, computer, server, or data center by wired or wireless means. The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that integrates one or more available media. The usable medium may be a magnetic medium, e.g., floppy disk, hard disk, tape; but also optical media such as digital video discs; but also semiconductor media such as solid state disks. The computer readable storage medium may be volatile or nonvolatile storage medium, or may include both volatile and nonvolatile types of storage medium.

In various embodiments of the application, where no special description or logic conflict exists, terms and/or descriptions between the various embodiments are consistent and may reference each other, and features of the various embodiments may be combined to form new embodiments based on their inherent logic.

In the present application, "at least one" means one or more, and "a plurality" means two or more. "and/or", describes an association relationship of an association object, and indicates that there may be three relationships, for example, a and/or B, and may indicate: a alone, a and B together, and B alone, wherein a, B may be singular or plural. In the text description of the present application, the character "/", generally indicates that the associated objects are an or relationship; in the formula of the present application, the character "/" indicates that the front and rear associated objects are a "division" relationship.

It will be appreciated that the various numerical numbers referred to in the embodiments of the present application are merely for ease of description and are not intended to limit the scope of the embodiments of the present application. The sequence number of each process does not mean the sequence of the execution sequence, and the execution sequence of each process should be determined according to the function and the internal logic.

Claims

1. A method for sending a message, comprising:

the user plane network element receives a message, wherein the message comprises an address of a personal networking PIN element network element;

the user plane network element determines a packet detection rule matched with the address of the PIN element network element;

and the user plane network element sends the message to the PIN gateway network element according to the tunnel information of the PIN gateway network element in the forwarding action rule corresponding to the packet detection rule.

2. The method as recited in claim 1, further comprising:

the user plane network element receives the packet detection rule and the forwarding action rule from a session management network element.

3. The method of claim 2, wherein the user plane network element receiving the packet detection rule and the forwarding action rule from a session management network element comprises:

the user plane network element receives a session request message from the session management network element, wherein the session request message comprises the packet detection rule and the forwarding action rule; or alternatively, the process may be performed,

the user plane network element receives a session update message from the session management network element, the session update message including the packet detection rule and the forwarding action rule.

4. A method for sending a message, comprising:

the user plane network element determines a plurality of forwarding action rules corresponding to the packet detection rules, wherein each forwarding action rule in the plurality of forwarding action rules comprises tunnel information of a PIN gateway network element;

the user plane network element selects one PIN gateway network element from the PIN gateway network elements according to loads of the PIN gateway network elements corresponding to the forwarding action rules;

and the user plane network element sends the message to the selected PIN gateway network element according to the tunnel information of the selected PIN gateway network element.

5. The method as recited in claim 4, further comprising:

the user plane network element receives the packet detection rule and the plurality of forwarding action rules from a session management network element.

6. The method of claim 5, wherein the plurality of forwarding action rules includes a first forwarding action rule and a second forwarding action rule;

The user plane network element receiving the packet detection rule and the plurality of forwarding action rules from a session management network element, comprising:

the user plane network element receives a first session request message from the session management network element, wherein the first session request message comprises the packet detection rule and the first forwarding operation rule;

the user plane network element receives a second session request message from the session management network element, the second session request message including the packet detection rule and the second forwarding action rule.

7. The method of claim 5, wherein the plurality of forwarding action rules includes a first forwarding action rule and a second forwarding action rule;

the user plane network element receives a first session update message from the session management network element, the first session update message comprising the packet detection rule and the first forwarding initiation rule;

the user plane network element receives a second session update message from the session management network element, the second session update message including the packet detection rule and the second forwarding action rule.

8. The method according to any one of claims 4 to 7, wherein the user plane element selecting one PIN gateway element from the plurality of PIN gateway elements according to loads of the plurality of PIN gateway elements corresponding to the plurality of forwarding action rules, comprises:

the user plane network element selects a PIN gateway network element with the lightest load from the PIN gateway network elements according to the loads of the PIN gateway network elements; or alternatively, the process may be performed,

and the user plane network element randomly selects one PIN gateway network element from N PIN gateway network elements with the lightest load in the PIN gateway network elements according to the loads of the PIN gateway network elements, wherein N is an integer greater than 1.

9. The personal internet of things PIN management method is characterized by comprising the following steps of:

the method comprises the steps that a session management network element receives a session establishment request message from a PIN gateway network element, wherein the session establishment request message requests to establish a session, and the session establishment request message comprises indication information which indicates that the session is a PIN session;

the session management network element sends a request message to a PIN network function network element according to the indication information, wherein the request message comprises identification information of the PIN gateway network element, and the request message is used for acquiring the identification information of the PIN element network element corresponding to the PIN gateway network element;

The session management network element receives identification information of a PIN element network element corresponding to the PIN gateway network element from the PIN network function network element;

and the session management network element sends the tunnel information of the PIN gateway network element and the identification information of the PIN element network element corresponding to the PIN gateway network element to a user plane network element.

10. The method of claim 9, wherein the session management network element sending the tunnel information of the PIN gateway network element and the identification information of the PIN element network element corresponding to the PIN gateway network element to a user plane network element comprises:

the session management network element sends at least one packet detection rule and a forwarding action rule corresponding to the at least one packet detection rule to the user plane network element, wherein the at least one packet detection rule respectively comprises identification information of one PIN element network element in identification information of the PIN element network element corresponding to the PIN gateway network element, and the forwarding action rule comprises tunnel information of the PIN gateway network element.

11. The method of claim 10, wherein the session management network element sending at least one packet detection rule and a forwarding action rule corresponding to the at least one packet detection rule to the user plane network element comprises:

The session management network element sends a session request message to the user plane network element, wherein the session request message comprises the at least one packet detection rule and the forwarding action rule; or alternatively, the process may be performed,

the session management network element sends a session update message to the user plane network element, the session update message comprising the at least one packet detection rule and the forwarding action rule.

12. The method of any one of claims 9 to 11, further comprising:

the session management network element receives the identification information of the updated PIN element network element corresponding to the PIN gateway network element from the PIN network function network element;

and the session management network element sends the tunnel information of the PIN gateway network element and the identification information of the updated PIN element network element to the user plane network element.

13. The personal internet of things PIN management method is characterized by comprising the following steps of:

the PIN management network element receives a first notification message from a first PIN gateway network element, wherein the first notification message comprises identification information of the first PIN gateway network element, identification information of a PIN element network element and indication information, and the indication information indicates that the first PIN gateway network element cannot route messages of the PIN element network element;

The PIN management network element sends a second notification message to a second PIN gateway network element, wherein the second notification message comprises identification information of the PIN element network element, and the second notification message indicates that the second PIN gateway network element provides routing service for the PIN element network element;

the PIN management network element sends a third notification message to the PIN element network element, wherein the third notification message comprises the identification information of the second PIN gateway network element, and the third notification message indicates that the second PIN gateway network element provides routing service for the PIN element network element.

14. The method as recited in claim 13, further comprising:

and the PIN management network element selects the target UE as the second PIN gateway network element.

15. The method of claim 14, wherein the target UE is one of a plurality of PIN element network elements of which the first PIN gateway network element provides routing services.

16. The method as recited in claim 13, further comprising:

and the PIN management network element selects the PIN management network element as the second PIN gateway network element.

17. The method as recited in claim 13, further comprising:

The PIN management network element sends a request message to the PIN network function network element, wherein the request message comprises identification information of the PIN, and the request message requests to select a PIN gateway network element for the PIN.

18. A communication device, comprising: a processor and a memory; the memory is configured to store computer instructions that, when executed by the communication device, cause the processor to perform the method of any one of claims 1 to 3, or perform the method of any one of claims 4 to 8, or perform the method of any one of claims 9 to 12, or perform the method of any one of claims 13 to 17.

19. A communication device comprising a processor and interface circuitry for receiving signals from other communication devices than the communication device and transmitting to the processor or sending signals from the processor to other communication devices than the communication device, the processor being configured to implement the method of any one of claims 1 to 3, or to implement the method of any one of claims 4 to 8, or to implement the method of any one of claims 9 to 12, or to implement the method of any one of claims 13 to 17, by logic circuitry or execution of code instructions.

20. A computer program product comprising a computer program which, when executed by a communication device, implements the method of any of claims 1 to 17.

21. A computer readable storage medium, characterized in that the storage medium has stored therein a computer program or instructions which, when executed by a communication device, implement the method of any of claims 1 to 17.

22. A communication system comprising a PIN gateway network element and a user plane network element for performing the method of any one of claims 1 to 3;

the PIN gateway network element is used for receiving the message from the user plane network element.

23. A communication system comprising a PIN gateway network element and a user plane network element for performing the method of any of claims 4 to 8;

24. A communication system comprising a user plane network element and a session management network element for performing the method of any of claims 9 to 12;

the user plane network element is configured to receive tunnel information of a PIN gateway network element and identification information of a PIN element network element corresponding to the PIN gateway network element from the session management network element.

25. A communication system comprising a PIN element network element and a PIN management network element for performing the method of any of claims 13 to 17;

the PIN element network element is configured to receive a third notification message from the PIN management network element, where the third notification message includes identification information of a second PIN gateway network element, and the third notification message indicates that the second PIN gateway network element provides routing service for the PIN element network element.