Service-based user plane registration method and device, communication device, system and storage medium

Abstract

The application discloses a service user plane registration method, a user plane determination method, a user plane service information subscription method, a device, a communication device, a system and a storage medium, and belongs to the technical field of communication. The service user plane registration method comprises the following steps: a first network element sends a target request to a second network element, the target request is a registration request or a registration update request, and the target request is used for requesting to register the first network element into the second network element; wherein, in the case that the first network element is registered into the second network element, other network elements can find the first network element through the second network element.

Description

Technical Field

[0001] This application belongs to the field of communication technology, and specifically relates to a service-oriented user plane registration method, a user plane determination method, a user plane service information subscription method, apparatus, communication equipment, system and storage medium. Background Technology

[0002] With the continuous development of communication technology, the 5th generation (5G) th In the 5G core network, most network elements and interfaces have been service-oriented. However, the User Plane Function (UPF) network elements in the 5G core network are currently non-service-oriented. Other network elements cannot call the services of UPF network elements, and UPF network elements are only controlled by Session Management Function (SMF) network elements and cannot use the services of other 5G network elements. However, no specific solution has been provided for designing a service-oriented UPF network element. Therefore, how to design a service-oriented UPF network element is an urgent problem to be solved. Summary of the Invention

[0003] This application provides a service-oriented user plane registration method, a user plane determination method, a user plane service information subscription method, apparatus, communication equipment, system, and storage medium, which can solve the problem of how to design service-oriented UPF network elements.

[0004] Firstly, a service-oriented user plane registration method is provided, which includes: a first network element sending a target request to a second network element, the target request being a registration request or a registration update request, the target request being used to request the first network element to register in the second network element; wherein, when the first network element is registered in the second network element, other network elements are supported in finding the first network element through the second network element.

[0005] Secondly, a service-oriented user plane registration device is provided, comprising: a sending module. The sending module is used to send a target request to a second network element, the target request being a registration request or a registration update request, the target request being used to request the first network element to register with the second network element; wherein, when the first network element is registered with the second network element, other network elements can find the first network element through the second network element.

[0006] Thirdly, a method for determining the user plane is provided, the method comprising: a third network element sending a query request to a second network element, the query request being used to request the second network element to search for a first network element, the query request including second target indication information, the second target indication information being used to indicate the first network element that meets the target conditions.

[0007] Fourthly, a user plane determination device is provided, comprising: a sending module. The sending module is configured to send a query request to a second network element, the query request being used to request the second network element to locate a first network element, the query request including second target indication information, the second target indication information being used to indicate a first network element that meets the target conditions.

[0008] Fifthly, a method for subscribing to user plane service information is provided. The method includes: a fourth network element sending a subscription request to a first network element, the subscription request being used to request subscription to relevant services of the first network element, the subscription request including relevant information of the first network element; and the fourth network element receiving notification information sent by the first network element, the notification information including relevant services of the first network element.

[0009] Sixthly, a user plane service information subscription device is provided, comprising a sending module and a receiving module. The sending module is used to send a subscription request to a first network element, the subscription request requesting subscription to relevant services of the first network element, the subscription request including relevant information of the first network element. The receiving module is used to receive notification information sent by the first network element, the notification information including relevant services of the first network element.

[0010] In a seventh aspect, a network element is provided, the network element including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the service-oriented user plane registration method as described in the first aspect.

[0011] Eighthly, a network element is provided, including a processor and a communication interface, wherein the communication interface is used to send a target request to a second network element, the target request being a registration request or a registration update request, the target request being used to request the first network element to be registered in the second network element; wherein, when the first network element is registered in the second network element, other network elements are supported in finding the first network element through the second network element.

[0012] In a ninth aspect, a network element is provided, the network element including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the user plane determination method as described in the third aspect.

[0013] In a tenth aspect, a network element is provided, including a processor and a communication interface, wherein the communication interface is used to send a query request to a second network element, the query request being used to request the second network element to search for a first network element, the query request including second target indication information, the second target indication information being used to indicate a first network element that meets target conditions.

[0014] In an eleventh aspect, a network element is provided, the network element including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the user plane service information subscription method as described in the fifth aspect.

[0015] In a twelfth aspect, a network element is provided, including a processor and a communication interface, wherein the communication interface is used to send a subscription request to a first network element, the subscription request being used to request subscription to relevant services of the first network element, the subscription request including relevant information of the first network element; and to receive notification information sent by the first network element, the notification information including relevant services of the first network element.

[0016] In a thirteenth aspect, a communication system is provided, comprising: a service-oriented user plane registration device as described in the second aspect, a user plane determination device as described in the fourth aspect, and a user plane service information subscription device as described in the sixth aspect; or, comprising: a network element as described in the seventh, ninth, and eleventh aspects; or, comprising: a network element as described in the eighth, tenth, and twelfth aspects. The network element may be used to perform the steps of the methods described in the first, third, and fifth aspects.

[0017] In a fourteenth aspect, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the first aspect, or the steps of the method described in the third aspect, or the steps of the method described in the fifth aspect.

[0018] In a fifteenth aspect, a chip is provided, the chip including a processor and a communication interface coupled to the processor, the processor being configured to run a program or instructions to implement the method as described in the first aspect, or the method as described in the third aspect, or the method as described in the fifth aspect.

[0019] In a sixteenth aspect, a computer program / program product is provided, which is stored in a storage medium and is executed by at least one processor to implement the steps of the service-oriented user plane registration method as described in the first aspect, or the steps of the user plane determination method as described in the third aspect, or the steps of the user plane service information subscription method as described in the fifth aspect.

[0020] In this embodiment, the first network element can register with the second network element through a registration response or a registration update response, so that other network elements can find the first network element through the second network element, thereby solving the problem of how the UPF network element registers with the NRF network element and can be found by the SMF network element.

[0021] The third network element can request the second network element to find the first network element through a query request. Since the query request includes second target indication information indicating the first network element that meets the target conditions, the second network element can quickly and accurately find the first network element that meets the target conditions (i.e., meets the requirements of the third network element).

[0022] When the third network element finds the first network element, the fourth network element can subscribe to the relevant services of the first network element by sending a subscription request directly or indirectly to the first network element. That is, it can directly subscribe to the relevant services of the first network element, or indirectly subscribe to the relevant services of the first network element through the third network element, so as to obtain the relevant services opened by the first network element. Attached Figure Description

[0023] Figure 1 This is a schematic diagram of the architecture of a wireless communication system provided in an embodiment of this application;

[0024] Figure 2 This is a schematic diagram of the architecture of a device in a 5G network provided in an embodiment of this application;

[0025] Figure 3 This is one of the flowcharts of a service-oriented user plane registration method provided in the embodiments of this application;

[0026] Figure 4 This is a second flowchart of a service-oriented user plane registration method provided in an embodiment of this application;

[0027] Figure 5 This is one of the flowcharts of a method for determining a user plane provided in an embodiment of this application;

[0028] Figure 6 This is a second flowchart of a method for determining a user plane provided in an embodiment of this application;

[0029] Figure 7 This is one of the flowcharts of a user plane service information subscription method provided in the embodiments of this application;

[0030] Figure 8 This is a second flowchart of a user plane service information subscription method provided in the embodiments of this application;

[0031] Figure 9 This is the third flowchart of a user plane service information subscription method provided in the embodiments of this application;

[0032] Figure 10 This is the fourth flowchart of a user plane service information subscription method provided in the embodiments of this application;

[0033] Figure 11This is the fifth flowchart of a user plane service information subscription method provided in the embodiments of this application;

[0034] Figure 12 This is the third flowchart of a service-oriented user plane registration method provided in the embodiments of this application;

[0035] Figure 13 This is the third flowchart of a method for determining a user plane provided in an embodiment of this application;

[0036] Figure 14 This is the sixth flowchart of a user plane service information subscription method provided in the embodiments of this application;

[0037] Figure 15 This is the seventh flowchart of a user plane service information subscription method provided in the embodiments of this application;

[0038] Figure 16 This is the eighth flowchart of a user plane service information subscription method provided in the embodiments of this application;

[0039] Figure 17 This is the ninth flowchart of a user plane service information subscription method provided in the embodiments of this application;

[0040] Figure 18 This is a schematic diagram of the structure of a registration device for a service-oriented user plane provided in an embodiment of this application;

[0041] Figure 19 This application provides a schematic diagram of the structure of a user plane determination device;

[0042] Figure 20 This is a schematic diagram of the structure of a user plane service information subscription device provided in an embodiment of this application;

[0043] Figure 21 This is a schematic diagram of the hardware structure of a communication device provided in an embodiment of this application;

[0044] Figure 22 This is a schematic diagram of the hardware structure of a network element provided in an embodiment of this application. Detailed Implementation

[0045] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0046] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, a first object can be one or more. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0047] It is worth noting that the technologies described in this application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency Division Multiple Access (SC-FDMA), and other systems. The terms "system" and "network" in this application are often used interchangeably, and the described technologies can be used with the systems and radio technologies mentioned above, as well as with other systems and radio technologies. The following description describes New Radio (NR) systems for illustrative purposes, and NR terminology is used in most of the following description; however, these technologies can also be applied to applications beyond NR systems, such as 6th generation (6G) radio systems. th Generation 6G communication system.

[0048] Figure 1This diagram illustrates a block diagram of a wireless communication system applicable to embodiments of this application. The wireless communication system includes a terminal 11 and a network-side device 12. Terminal 11 can be a mobile phone, tablet computer, laptop computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), augmented reality (AR) / virtual reality (VR) device, robot, wearable device, vehicle-mounted device (VUE), pedestrian terminal (PUE), smart home (home devices with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), game console, personal computer (PC), ATM, or self-service machine, etc. Wearable devices include: smartwatches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart chains, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. It should be noted that the specific type of terminal 11 is not limited in this embodiment. Network-side equipment 12 may include access network equipment or core network equipment. Access network equipment 12 may also be referred to as radio access network equipment, radio access network (RAN), radio access network function, or radio access network unit. Access network equipment 12 may include base stations, WLAN access points, or WiFi nodes, etc. Base stations may be referred to as Node B, evolved Node B (eNB), access point, base transceiver station (BTS), radio base station, radio transceiver, Basic Service Set (BSS), Extended Service Set (ESS), home B node, home evolved B node, Transmitting Receiving Point (TRP), or any other suitable term in the field, as long as the same technical effect is achieved. The base station is not limited to specific technical terms. It should be noted that in this application embodiment, only a base station in an NR system is used as an example for description, and the specific type of base station is not limited.Core network equipment may include, but is not limited to, at least one of the following: core network node, core network function, Mobility Management Entity (MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function, Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized network configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (or L-NEF), Binding Support Function (BSF), Application Function (AF), etc. It should be noted that the embodiments in this application only use the core network equipment in the NR system as an example for introduction, and do not limit the specific type of core network equipment.

[0049] The following explains some concepts and / or terms involved in the service-oriented user plane registration method, user plane determination method, user plane service information subscription method, apparatus, communication equipment, system and storage medium provided in the embodiments of this application.

[0050] Currently in the 5G core network, user plane UPF network elements (including PDU session anchor (PSA) network elements and uplink classifier (UL CL) network elements, all collectively referred to as UPF network elements) are non-service-oriented. Service-oriented architecture is a new architecture introduced in the 5G core network architecture. In Service Based Architecture (SBA), the interaction between network functions is achieved through service calls. Each network function presents a common service interface to the outside world, which can be called by authorized network functions or services.

[0051] Traditional 2nd Generation (2G), 3rd Generation (3G), and 4th Generation (4G) core network architectures employ a point-to-point architecture. Interfaces between network elements need to be predefined and configured, and these defined interfaces can only be used between specific types of network elements, resulting in limited flexibility. The 3rd Generation Partnership Project (3GPP) has selected the following protocol implementation combination for the SBA interface in the current protocol: Transmission Control Protocol (TCP), Hypertext Transfer Protocol (HTTP), Hypertext Transfer Protocol (HTTP) / 2, JavaScript Object Notation (JSON), RESTful, and OpenAPI 3.0. This protocol design offers numerous advantages: facilitating the adoption of new internet technologies, enabling rapid deployment, supporting continuous integration and the release of new network services, and facilitating the development of operator-owned or third-party services.

[0052] Currently, most network elements and interfaces in the 5G core network have been service-oriented, but the User Plane (UPF) has not been service-oriented. Other network elements cannot call the services of the UPF network element, and the UPF network element can only be controlled by the SMF network element and cannot use the services of other 5GC network elements.

[0053] like Figure 2As shown, a 5G network includes User Equipment (UE), RAN equipment, and 5G core network equipment. The 5G core network equipment includes: Network Slice Selection Function (NSSF) network elements, NEF network elements, NRF network elements, PCF network elements, UDM network elements, AF network elements, NSSAAF network elements, Authentication Server Function (AUSF) network elements, AMF network elements, SMF network elements, Service Communication Proxy (SCP) network elements, NSACF network elements, UPF network elements, and Data Network (DN).

[0054] Specifically, the interface between the UE and the AMF network element is the N1 interface; the interface between the RAN and the AMF network element is the N2 interface; the interface between the RAN and the UPF network element is the N3 interface; the interface between the UPF network element and the SMF network element is the customized N4 interface; the interface between the UPF and the DN network element is the N6 interface; the interface of the NSSAAF network element is the Nnssaaf interface; the interface of the AUSF network element is the Nausf interface; the interface of the AMF network element is the Naamf interface; the interface of the SMF network element is the Nsmf interface; the interface of the NSACF network element is the Nnsacf interface; the interface of the NSSF network element is the Nnssf interface; the interface of the NEF network element is the Nnef interface; the interface of the NRF network element is the Npcf interface; the interface of the PCF network element is the Npcf interface; the interface of the UDM network element is the Nudm interface; the interface of the AF network element is the Naf interface; and the interface of the UPF network element is the N9 interface. Among the interfaces mentioned above, those such as N4 are customized point-to-point interfaces, while those such as Namf are service-oriented interfaces.

[0055] Currently, this non-service-oriented User Plane (UPF) network element has many drawbacks. For example, the UPF is a network element that performs data transmission and forwarding. It can detect a lot of useful Quality of Service (QoS) related measurement information, such as the uplink and downlink packet transmission rates, bandwidth, and uplink and downlink packet loss counts for a user. To obtain this QoS-related information, the UPF network element must report it to the SMF network element, which then shares it with other network elements. This information sharing method is not convenient enough; it cannot be directly shared from the data source and must be routed through the SMF network element. For example, if the AF network element wants to subscribe to QoS monitoring information, the UPF network element must report it to the SMF network element, the SMF network element must report it to the PCF network element, and the PCF network element must then send the QoS monitoring data to the AF network element via the NEF network element. This method is very complex and time-consuming. All user plane data collected or output by the UPF must be routed through the control plane before reaching the peer device. In addition, since the UPF network element is not service-oriented, all data plane information, such as QoS information, needs to be aggregated from the user plane UPF network element to the control plane SMF network element before it can be sent. This method seriously affects timeliness and is not convenient or flexible enough.

[0056] The following description, in conjunction with the accompanying drawings, details the service-oriented user plane registration method, user plane determination method, and user plane service information subscription method provided in this application embodiment through some embodiments and application scenarios.

[0057] Currently, for UPF network elements, other network elements cannot call the services of UPF network elements, and UPF network elements can only be controlled by SMF network elements and cannot use the services of other 5G network elements. Thus, (1) if UPF is a service-oriented network element, how to register with NRF network elements and be found by SMF network elements is an unsolved problem. (2) How other network elements (such as AF network elements or Network Data Analytics Function (NWDAF) network elements) can obtain the relevant services opened by UPF network elements from UPF network elements is an unsolved problem.

[0058] In this embodiment of the application, a service-oriented user plane is designed. This user plane can provide service-oriented interfaces to provide related services of the user plane to other 5GC network elements for direct invocation, or for other network elements to invoke related services of the user plane through the SMF network element. Furthermore, this service-oriented network element can also use the services of other network elements, such as the UPF network element using related services opened by the SMF network element.

[0059] Specifically, one approach is that UPF network elements can register with NRF network elements through registration requests or registration update requests, enabling / supporting other network elements to find UPF network elements through NRF network elements, thereby directly or indirectly calling the relevant services opened by UPF network elements.

[0060] Another approach is that SMF network elements can request NRF network elements to search for UPF network elements through query requests in order to find network elements that meet the requirements (network elements that satisfy the target conditions).

[0061] Another approach is that, when the SMF network element finds the UPF network element, the AF network element or NWDAF network element can subscribe to the relevant services of the UPF network element by sending a subscription request directly or indirectly to the UPF network element. That is, it can directly subscribe to the relevant services of the UPF network element, or indirectly subscribe to the relevant services of the UPF network element through the SMF network element.

[0062] This application provides a service-oriented user plane registration method. Figure 3 A flowchart illustrating a registration method for a service-oriented user plane provided in an embodiment of this application is shown. Figure 3 As shown, the service-oriented user plane registration method provided in this application embodiment may include the following steps 201 and 202.

[0063] Step 201: The first network element sends a target request to the second network element.

[0064] In this embodiment, the aforementioned target request is a registration request or a registration update request, which is used to request the registration of the first network element into the second network element. Wherein, when the first network element is registered into the second network element, other network elements can find the first network element through the second network element.

[0065] Step 202: The second network element receives the target request sent by the first network element.

[0066] Optionally, in this embodiment of the application, the first network element can be a UPF network element, a PSA network element, or a UL CL network element, and the second network element can be an NRF network element, which is a network element used for network element lookup within 5G.

[0067] Optionally, in this embodiment of the application, the UPF network element can send an Nnrf_NFManagement_NFRegister registration request to the NRF network element to request the UPF network element to be registered in the NRF network element.

[0068] Optionally, in this embodiment of the application, the target request includes at least one of the following: relevant information of the first network element and first target indication information. The first target indication information is used to indicate whether the first network element is a service-oriented user plane network element.

[0069] Optionally, in this embodiment of the application, the relevant information of the first network element mentioned above includes at least one of the following: the Internet Protocol IP address of the UE, the Subscription Permanent Identifier (SUPI) or Generic Public Subscription Identifier (GPSI) of the UE, the Data Network Name (DNN) of the UE, the Single Network Slice Selection Assistance Information (S-NSSAI) of the UE, the relevant services supported by the first network element, the relevant services of the first network element to be subscribed to, and the fourth indication information, which is used to instruct the first network element to request service to provide the relevant services of the first network element.

[0070] Optionally, in this embodiment, the services supported by the first network element are used during registration, i.e., which services the first network element supports; the services requested for subscription are used during subscription by the fourth network element, i.e., which services the fourth network element wants to obtain. Optionally, in this embodiment, the first target indication information includes at least one of the following: first indication information, second indication information, and third indication information. The first indication information indicates whether the first network element supports opening its relevant services to other network elements; the second indication information indicates whether the relevant services of the first network element can be directly or indirectly subscribed to by other network elements; and the third indication information indicates whether the first network element has the ability to obtain relevant services from other network elements.

[0071] Optionally, in the embodiments of this application, the other network elements mentioned above can be AMF network elements, SMF network elements, NEF network elements, AF network elements, NWDAF network elements, etc.

[0072] Optionally, in this embodiment of the application, if the subscriber directly subscribes to the relevant services of the first network element, the subscriber directly triggers: Nupf_EventExposure_Subscribe to UPF; if the subscriber cannot directly subscribe to the relevant services of the first network element, it is necessary to subscribe to a certain event of the UPF network element through the SMF network element.

[0073] Optionally, in this embodiment of the application, the above-mentioned indication of whether the first network element has the ability to obtain related services from other network elements can be to obtain related services provided by SMF network element, PCF network element or NWDAF network element.

[0074] Optionally, in this embodiment, the related services of the first network element include at least one of the following: the QoS stream bit rate of the first device, the QoS stream data packet latency of the first device, the number of data packets transmitted by the first device, the number of data packets retransmitted by the first device, the resource information of the first network element, the load information of the first network element, the traffic capacity of the first network element, the throughput of the first network element, the QoS monitoring report of the first network element, and the QoS monitoring indication information of the first network element. Wherein, the first device is either the first network element or the UE, and the QoS monitoring indication information is used to indicate whether the first network element supports providing QoS monitoring through service-based signaling.

[0075] For example, when a UPF network element registers with an NRF network element, an instruction can be added to the Nnrf_NFManagement_NFRegister registration request. This instruction indicates that the UPF network element supports providing QoS monitoring reports to NEF, AF, or NWDAF network elements via Nupf_EventExposure_Notify.

[0076] Optionally, in this embodiment of the application, the QoS flow bit rate of the first device is QoS flow BitRate (per UE or per UPF): the observed uplink or downlink bit rate of a certain UE; or, the bit rate of all uplink or downlink carried by this UPF.

[0077] Optionally, in this embodiment of the application, the QoS flow packet delay of the first device is QoS flow PacketDelay (per UE or per UPF): the observed uplink or downlink packet delay of a certain UE; or, the delay of all uplink or downlink packets carried by this UPF.

[0078] Optionally, in this embodiment of the application, the number of data packets transmitted by the first device is Packettransmission (per UE or per UPF): the number of data packets (uplink or downlink) transmitted by a certain UE as observed; or the data of the data packets (uplink or downlink) transmitted by this UPF.

[0079] Optionally, in the embodiments of this application, the number of data packets retransmitted by the first device is Packet retransmission (per UE or per UPF): the number of data packets retransmitted by a certain UE (uplink or downlink); or the data of the data packets retransmitted by this UPF (uplink or downlink).

[0080] Optionally, in this embodiment of the application, the resource information of the first network element is UPF resource: the resource status of the UPF, including the current available or total CPU load or computing power, storage space, and disk capacity of the UPF.

[0081] Optionally, in this embodiment of the application, the load information of the first network element is UPF load: the load status of the UPF within a certain time interval, such as the number of PDU sessions (UE's) carried by the current UPF, the number of forwarded data packets (forwarding capacity), etc.

[0082] Optionally, in this embodiment of the application, the traffic capacity of the first network element is the UPF traffic volume: the traffic capacity of the UPF, that is, the traffic situation of the UPF in a certain session or for a certain UE during a certain communication process within a certain time. It can be the peak traffic or the average traffic.

[0083] Optionally, in this embodiment of the application, the throughput of the first network element is the UPF throughput: uplink and downlink throughput. It represents the throughput over a certain time interval, either peak or average.

[0084] Optionally, in this embodiment, the QoS monitoring indication information of the first network element is QoS monitoring: whether the UPF can provide QoS monitoring. For example, QoS monitoring includes uplink, downlink, and loopback delay measurement. It can also measure the packet delay of the QoS flow.

[0085] Optionally, in this embodiment of the application, the first network element provides related services of the first network element through service-oriented signaling, which includes at least one of the following: Nupf_EventExposure_Notify.

[0086] Optionally, in this embodiment, each service in the related services of the first network element corresponds to an event ID. After step 202 above, the service-oriented user plane registration method provided in this embodiment further includes steps 203 and 204 as described below.

[0087] Step 203: The first network element receives subscription requests sent by other network elements.

[0088] In this embodiment of the application, the subscription request is used to request subscription to the relevant services of the first network element, and the subscription request includes at least one event identifier.

[0089] For example, an AF network element, or an NWDAF network element, or an SMF network element can trigger Nupf_EventExposure_Subscribe to the UPF network element to request subscription to the relevant services of the UPF network element.

[0090] Step 204: The first network element sends the relevant services of the first network element to other network elements via service-based signaling, which correspond to at least one event identifier.

[0091] Optionally, in the embodiments of this application, the first network element may indicate that it can use the services of the SMF network element. Then, the first network element may also indicate the type of SMF network element services that it can use or wants to obtain, identified by an event ID, such as obtaining the relevant services of the SMF network element from the SMF network element.

[0092] Optionally, in this embodiment of the application, the first network element provides related services of the first network element through service-oriented signaling, which includes notification information, at least one of the following: Nupf_EventExposure_Notify.

[0093] Optionally, in this embodiment, the first target indication information includes third indication information. For example, the first network element has the ability to obtain relevant services from the session management function (SMF) network element, and the relevant services of the SMF network element are services supported and opened by the SMF network element. That is, the UPF network element can subscribe to the relevant services of the SMF network element through Nsmf_EventExposure_Subscribe, and the SMF network element can also send the services of the SMF network element subscribed to by the UPF network element to the service-oriented UPF network element through Nsmf_EventExposure_Notify.

[0094] Optionally, in this embodiment of the application, the aforementioned SMF network element sends the relevant services of the SMF network element to the relevant services of the first network element in the form of a notification, such as Nsmf_EventExposure_Notify.

[0095] Optionally, in this embodiment of the application, the related services of the SMF network element include at least one of the following:

[0096] The UE's Internet Protocol IP address / prefix is ​​provided, or the UE's IP address / prefix change is notified (UE IP address / Prefix allocation / change);

[0097] Protocol Data Unit (PDU) session establishment and / or PDU session release notification;

[0098] User-facing UP path change notification service;

[0099] Notification service for changes in access type;

[0100] Notification service for changes in RAT type of wireless access technology;

[0101] Public Land Mobile Network (PLMN) Change Notification Service (PLMN change);

[0102] Quality of Service (QoS) flow identifier QFI configuration service (QFI allocation);

[0103] Information on PDU Session for WLAN;

[0104] User plane status information;

[0105] Session Management Congestion Control Experience for PDU Session;

[0106] UE session behavior trends;

[0107] UE behavior;

[0108] UE communications trends.

[0109] Optionally, in this embodiment of the application, the first target indication information mentioned above includes the third indication information. For example, the first network element has the ability to obtain relevant services from the network data analysis function (NWDAF) network element, and the relevant services of the NWDAF network element are the open analysis functions, data collection functions, or statistical functions supported by the NWDAF network element.

[0110] Optionally, in this embodiment of the application, the first network element may indicate that it can use the services of the NWDAF network element, or indicate the services of the NWDAF network element that it wishes to obtain or use. Then, the first network element may also indicate the type of service of the NWDAF network element that it wishes to use or obtain, using the (Analytics) analysis ID identifier, for example, obtaining the relevant services of the NWDAF network element from the NWDAF network element.

[0111] Optionally, in this embodiment of the application, the related services of the NWDAF network element include at least one of the following:

[0112] Load level information (Analytics ID: load level information);

[0113] Service experience information (Analytics ID: Service Experience);

[0114] Network element load information (Analytics ID: NF load information);

[0115] Network performance statistics or predictions (Analytics ID: Network Performance);

[0116] UE mobility statistics or prediction (Analytics ID: UE Communication);

[0117] UE communication analysis or prediction (Analytics ID: UE Mobility and / or UE Communication);

[0118] Analysis or prediction of abnormal terminal behavior (Analytics ID: Abnormal behaviour);

[0119] User data congestion analysis or prediction (Analytics ID: User Data Congestion);

[0120] QoS sustainability analysis or prediction (Analytics ID: QoS Sustainability);

[0121] Analysis or prediction of session management congestion control experience (Analytics ID: Session Management Congestion Control Experience);

[0122] Redundant Transmission Experience Analysis or Prediction (Analytics ID:Redundant TransmissionExperience);

[0123] Wireless LAN performance analysis or prediction (Analytics ID: WLAN performance);

[0124] UE Dispersion (Analytics ID: UE Dispersion);

[0125] Data network performance analysis or prediction (Analytics ID:DN Performance).

[0126] The capabilities of NWDAF network elements for related services.

[0127] Optionally, in this embodiment, an Analytics ID is used. The first network element requests the corresponding service by including the Analytics ID in the subscription request.

[0128] For example, a UPF network element can trigger the services of an NWDAF network element: Nnwdaf_AnalyticsSubscription_Subscribe or Nnwdaf_AnalyticsInfo_Request, to request to subscribe to or obtain the services provided by the NWDAF network element. Each signaling message contains an Event ID, which is used for identification.

[0129] Optionally, in the embodiments of this application, combined with Figure 3 ,like Figure 4 As shown, after step 202 above, the service-oriented user plane registration method provided in this application embodiment further includes steps 205 and 206 as described below.

[0130] Step 205: The second network element sends a target response to the first network element.

[0131] In this embodiment of the application, the target response is a registration response or a registration update response, which is used to instruct the first network element to complete registration or complete registration update.

[0132] Step 206: The first network element receives the target response sent by the second network element.

[0133] This application also provides a service-oriented user plane registration method. A first network element can register itself with a second network element through a registration response or a registration update response, so that other network elements can find the first network element through the second network element. This solves the problem of how a UPF network element can register with an NRF network element and be found by an SMF network element.

[0134] It should be noted that the service-oriented user plane registration method provided in this application embodiment can also be executed by a service-oriented user plane registration device, or by a control module in the service-oriented user plane registration device for executing the service-oriented user plane registration method.

[0135] This application also provides a method for determining the user plane. Figure 5 A flowchart illustrating a method for determining a user plane according to an embodiment of this application is shown. Figure 5 As shown, the method for determining the user face provided in this application embodiment may include the following steps 301 and 302.

[0136] Step 301: The third network element sends a query request to the second network element.

[0137] In this embodiment of the application, the above query request is used to request the second network element to find / discover the first network element. The query request includes second target indication information, which is used to indicate the first network element that meets the target conditions.

[0138] Step 302: The second network element receives the query request sent by the third network element.

[0139] Optionally, in this embodiment of the application, the third network element can be an SMF network element or other 5G core network elements, and this embodiment of the application does not impose any restrictions.

[0140] Optionally, in this embodiment of the application, the third network element triggers a query request for the first network element using Nnrf_NFDiscovery_Request.

[0141] Optionally, in this embodiment of the application, the query request includes at least one of the following: indicating whether to search for a service-oriented first network element; indicating to search for a first network element with a certain capability, i.e., providing the corresponding event ID. For example, when searching for a first network element, the third network element may indicate to search for a first network element that can provide Quality of Service (QoS) monitoring through a service-oriented interface; and indicate that the first network element can also use the service-oriented information of other 5G network elements.

[0142] For example, an SMF network element triggers a network element lookup request to an NRF network element: Nnrf_NFDiscovery_Request. The lookup request can request the NRF network element to look up a service-oriented UPF network element. This service-oriented UPF network element supports opening QoS monitoring to other network elements through Nupf_EventExposure_Notify.

[0143] For example, an NWDAF network element triggers a network element lookup request to an NRF network element: Nnrf_NFDiscovery_Request. The lookup request can request the NRF network element to look up a service-oriented UPF network element. The query request includes: EventID = QoS flow Packet Delay, that is, the service-oriented UPF network element supports opening the QoS flow Packet Delay to other network elements through Nupf_EventExposure_Notify.

[0144] Optionally, in the embodiments of this application, the first network element that satisfies the target condition includes at least one of the following: a service-oriented first network element, a first network element with target capabilities, and a first network element that supports the use of service-oriented information from other network elements.

[0145] Optionally, in this embodiment, the first network element with the target capability is a first network element that supports open related services. The related services of the first network element include at least one of the following: the QoS stream bit rate of the first device, the QoS stream data packet latency of the first device, the number of data packets transmitted by the first device, the number of data packets retransmitted by the first device, the resource information of the first network element, the load information of the first network element, the traffic capacity of the first network element, the throughput of the first network element, the QoS monitoring report of the first network element, and the QoS monitoring indication information of the first network element. Wherein, the first device is either a first network element or a user equipment (UE), and the QoS monitoring indication information is used to indicate whether the first network element supports providing QoS monitoring through service-based signaling.

[0146] Optionally, in this embodiment of the application, the first network element provides related services of the first network element through service-oriented signaling, which includes notification information, at least one of the following: Nupf_EventExposure_Notify.

[0147] It should be noted that the description of each service in the relevant services of the first network element can be found in the above embodiments, and will not be repeated here.

[0148] Optionally, in the embodiments of this application, combined with Figure 5 ,like Figure 6 As shown, after step 302 above, the method for determining the user plane provided in this application embodiment further includes steps 303 and 304 as described below.

[0149] Step 303: The second network element sends a query response to the third network element.

[0150] In this embodiment of the application, the query response includes the Internet Protocol IP address, port number, or fully qualified domain name (FQDN) of the user plane network element that meets the target conditions.

[0151] Step 304: The third network element receives the query response sent by the second network element.

[0152] This application embodiment also provides a method for determining the user plane. The third network element can request the second network element to search for the first network element through a query request. Since the query request includes second target indication information indicating the first network element that meets the target conditions, the second network element can quickly and accurately find the first network element that meets the target conditions (i.e., meets the requirements of the third network element).

[0153] It should be noted that the user plane determination method provided in this application embodiment can also be executed by a user plane determination device, or by a control module in the user plane determination device for executing the user plane determination method.

[0154] This application also provides a method for subscribing to user plane service information. Figure 7 A flowchart illustrating a user plane service information subscription method provided in an embodiment of this application is shown. Figure 7 As shown, the user plane service information subscription method provided in this application embodiment may include the following steps 401 to 403.

[0155] Step 401: The fourth network element sends a subscription request to the first network element.

[0156] In this embodiment of the application, the subscription request is used to request the subscription of the relevant services of the first network element, and the subscription request includes the relevant information of the first network element.

[0157] Optionally, in this embodiment of the application, the fourth network element can be an AF network element or an NWDAF network element.

[0158] For example, AF network elements or NWDAF network elements can subscribe to the relevant services of UPF network elements (i.e., the first network element) through Nupf_EventExposure_Subscribe.

[0159] Step 402: The first network element receives the subscription request sent by the fourth network element and sends a notification message to the fourth network element.

[0160] In this embodiment of the application, the notification information includes the relevant services of the first network element.

[0161] In this embodiment of the application, after the first network element receives the subscription request sent by the fourth network element and agrees to the subscription request, once the first network element obtains the relevant services of the first network element requested in the subscription request, it can send a notification message to the fourth network element to send the relevant services of the first network element to the fourth network element.

[0162] For example, an AF network element requests a UPF network element to collect a QoS monitoring report. After collecting the relevant information, the UPF network element uses Nupf_EventExposure_Notify to send the QoS monitoring report to the AF network element.

[0163] Step 403: The fourth network element receives the notification information sent by the first network element.

[0164] Optionally, in this embodiment of the application, the first network element provides related services of the first network element through service-oriented signaling, which includes notification information, at least one of the following: Nupf_EventExposure_Notify.

[0165] Optionally, in this embodiment of the application, the relevant information of the first network element mentioned above includes at least one of the following: the Internet Protocol IP address of the UE, the UE's Subscription Permanent Identifier (SUPI) or General Public Subscription Identifier (GPSI), the UE's Data Network Name (DNN), the UE's Single Network Slice Selection Assistance Information (S-NSSAI), the relevant services of the first network element to be subscribed to, the relevant services supported by the first network element, and fourth indication information, which is used to instruct the first network element to request service to provide the relevant services of the first network element.

[0166] Optionally, in this embodiment of the application, the first network element that requests service directly provides a notification to the fourth network element via a local NEF network element or NEF network element, rather than providing it from the control plane, requiring the user plane to directly provide the information.

[0167] Optionally, in this embodiment, the related services of the first network element include at least one of the following: the QoS stream bit rate of the first device, the QoS stream data packet latency of the first device, the number of data packets transmitted by the first device, the number of data packets retransmitted by the first device, the resource information of the first network element, the load information of the first network element, the traffic capacity of the first network element, the throughput of the first network element, the QoS monitoring report of the first network element, and the QoS monitoring indication information of the first network element. Wherein, the first device is either the first network element or the user equipment (UE), and the QoS monitoring indication information is used to indicate whether the first network element supports providing QoS monitoring through service-based signaling.

[0168] Optionally, in this embodiment of the application, the first network element provides related services of the first network element through service-oriented signaling, which includes notification information, at least one of the following: Nupf_EventExposure_Notify.

[0169] It should be noted that the description of each service in the relevant services of the first network element can be found in the above embodiments, and will not be repeated here.

[0170] Optionally, in the first embodiment of this application, the fourth network element is an AF network element, which indirectly subscribes to the relevant services of the UPF network element through the SMF network element. Combined with... Figure 7 ,like Figure 8 As shown, step 401 can be implemented by steps 401a to 401c; step 402 can be implemented by steps 402a to 402c, or step 402 can be implemented by step 402d; and step 403 can be implemented by steps 403a or 403b.

[0171] Step 401a: The fourth network element sends a subscription request to the NEF network element.

[0172] In this embodiment of the application, the subscription request is used by the third network element to determine the first network element.

[0173] For example, the AF network element sends a subscription request Nnef_EventExposure_Subscribe to the NEF network element. This subscription request is used to subscribe to the relevant services of the UPF network element (i.e., the first network element). At this time, there is a PDU session between the AF network element and the UE, but the AF network element does not know which UPF network element is serving the current UE, so it needs to determine the user plane network element first.

[0174] Step 401b: The NEF network element receives the subscription request sent by the fourth network element and sends a subscription request to the third network element.

[0175] For example, after receiving a subscription request from the AF network element, the NEF network element first needs to locate the SMF network element managing the PDU session between the AF network element and the UE. Then, the NEF network element can send a subscription request to the SMF network element: Nsmf_EventExposure_Subscribe. This subscription request is used to subscribe to the relevant services of the UPF network element that maintains the current PDU session between the AF network element and the UE. For example, Nsmf_EventExposure_Subscribe can carry Event ID = UPF throughput, indicating that it wants the UPF network element to provide throughput data.

[0176] Optionally, in this embodiment, the NEF network element triggers a subscription to a third network element, such as an Nsmf_EventExposure_Subscribe request. However, this request needs to be newly added, subscribing to the event of the first network element and including the event ID of the first network element.

[0177] Step 401c: The third network element receives the subscription request sent by the NEF network element, determines the first network element, and sends the subscription request to the first network element.

[0178] Optionally, in this embodiment of the application, after the third network element receives the request from the NEF, it can find the PDU session based on the UE IP address, SUPI, etc., and find the IP address of the UPF carrying the PDU session. Then, it triggers a subscription request to the UPF: Nupf_EventExposure_Subscribe. This subscription request is used to obtain the open information (i.e., the information corresponding to the event ID) of the first network element that the fourth network element wants to obtain. The main purpose is to send the event ID to the first network element.

[0179] It is understandable that the fourth network element sends a subscription request to the third network element via the NEF network element, and the fourth network element sends a subscription request to the first network element via the third network element.

[0180] Step 402a: The first network element receives the subscription request sent by the third network element and sends a notification message to the third network element.

[0181] For example, when a UPF network element sends Nupf_EventExposure_Notify to an SMF network element, this signaling includes information about the UPF network element (i.e., the first network element) that the AF network element has subscribed to.

[0182] Step 402b: The third network element receives the notification information sent by the first network element and sends the notification information to the NEF network element.

[0183] For example, when an SMF network element sends Nsmf_EventExposure_Notify to an NEF network element, this signaling includes information about the UPF network element (i.e., the first network element) that the AF network element has subscribed to.

[0184] Step 402c: The NEF network element receives the notification information sent by the third network element and sends the notification information to the fourth network element.

[0185] For example, when a NEF network element sends Nnef_EventExposure_Notify to an AF network element, this signaling includes information about the UPF network element (i.e., the first network element) that the AF network element has subscribed to.

[0186] It is understandable that the fourth network element receives notification information sent by the first network element via the third network element and the NEF network element.

[0187] Step 402d: The first network element directly sends a notification message to the fourth network element.

[0188] It is understandable that the first network element can directly send the service results it provides to the subscriber. For example, the UPF network element collects UPF throughput information based on the subscription request of the AF network element, and then the UPF network element directly sends this information to the AF network element.

[0189] For example, a UPF network element sends a Nupf_EventExposure_Notify message to a NEF network element. This signaling includes information about the UPF network element (i.e., the first network element) subscribed to by the AF network element. Then, the NEF network element triggers a Nnef_EventExposure_Notify message to the AF network element, which also includes information about the UPF network element subscribed to by the AF network element. Here, the NEF network element only performs forwarding functions and does not process the signaling. In this way, the UPF network element directly sends the collected information about the first network element to the AF network element, without being forwarded by other control plane network elements such as the SMF network element.

[0190] Step 403a: The fourth network element receives the notification information sent by the NEF network element.

[0191] Step 403b: The fourth network element directly receives the notification information sent by the first network element.

[0192] It is understood that if steps 402a to 402c are performed, step 403a is performed; if step 402d is performed, step 403b is performed.

[0193] It should be noted that the logical relationship between steps 402a to 402c and step 402d is an "OR" relationship, and the logical relationship between steps 403a and 403b is also an "OR" relationship. Figure 8 To illustrate this relationship, steps 402d and 403b are shown in dashed lines.

[0194] Optionally, in the second embodiment of this application, the fourth network element is an AF network element, which directly subscribes to the relevant services of the UPF network element. Combined with... Figure 7 ,like Figure 9As shown, step 401 can be implemented by steps 401d to 401g, step 402 can be implemented by steps 402e and 402f, and step 403 can be implemented by step 403c.

[0195] Step 401d: The fourth network element sends a subscription request to the NEF network element.

[0196] For example, the AF network element sends a subscription request Nnef_EventExposure_Subscribe to the NEF network element. This subscription request is used to subscribe to the relevant services of the UPF network element. At this time, there is a PDU session between the AF network element and the UE, but the AF network element does not know which UPF network element is serving the current UE, so it needs to determine the user plane network element first.

[0197] Step 401e: The NEF network element receives the subscription request sent by the fourth network element and sends a confirmation request to the third network element.

[0198] It should be noted that the prerequisite for a NEF network element to send a confirmation request to a third network element is that the NEF network element has found the third network element. The aforementioned confirmation request is used to determine the UPF network element currently serving the PDU session between the AF network element and the UE.

[0199] For example, after receiving a subscription request from the AF network element, the NEF network element first needs to locate the SMF network element managing the PDU session between the AF network element and the UE. Then, the NEF network element sends a request to the SMF network element: Nsmf_UPFInformation_Get. This signaling is used to request information about the UPF network element serving the current PDU session between the AF network element and the UE. The parameters included in this signaling are: the UE's IP address, the UE's SUPI or GPSI, the UE's DNN, the UE's S-NSSAI, the relevant services of the first network element requesting subscription, the relevant services supported by the first network element, and a fourth indication information. This fourth indication information instructs the first network element requesting service to provide the relevant services of the first network element.

[0200] In this embodiment of the application, the above-mentioned determination request is used by the third network element to determine the first network element, and the determination request includes the IP address, port number or FQDN of the first network element.

[0201] It is understood that in this embodiment of the application, after the NEF network element finds the third network element, the NEF needs to replace the fourth network element to find the first network element serving the current UE and the current PDU session.

[0202] Step 401f: The third network element receives the confirmation request sent by the NEF network element, determines the first network element, and sends the IP address, port number or FQDN of the first network element to the NEF network element.

[0203] Step 401g: The NEF network element receives the IP address, port number, or FQDN of the first network element sent by the third network element, and sends the subscription request to the first network element.

[0204] It is understood that the fourth network element sends the subscription request to the NEF network element, and through the NEF network element, sends a confirmation request to the third network element according to the subscription request to determine the address information of the first network element; and the fourth network element sends the IP address, port number or FQDN of the first network element to the NEF network element through the third network element, and sends the subscription request to the first network element through the NEF network element.

[0205] It is understandable that the NEF network element triggers the subscription of the first network element, which is done on behalf of the fourth network element.

[0206] Step 402e: The first network element receives the subscription request sent by the NEF network element and sends a notification message to the NEF network element.

[0207] For example, the NEF network element replaces the AF network element and sends a subscription request Nupf_EventExposure_Subscribe to the UPF network element. This subscription request is used to subscribe to the relevant services of the UPF network element (i.e., the first network element).

[0208] Step 402f: The NEF network element receives the notification information sent by the first network element and sends the notification information to the fourth network element.

[0209] For example, a UPF network element sends a Nupf_EventExposure_Notify message to a NEF network element. This signaling includes information about the UPF network element (i.e., the first network element) subscribed to by the AF network element. Then, the NEF network element triggers another Nnef_EventExposure_Notify message to the AF network element, also containing information about the UPF network element (i.e., the first network element) subscribed to by the AF network element. Here, the NEF network element only performs forwarding functions and does not process the signaling. In this way, the UPF network element directly sends the collected information about the first network element to the AF network element, without being forwarded by other control plane network elements such as the SMF network element.

[0210] Optionally, in this embodiment of the application, the NEF network element triggers a subscription request to the first network element: Nupf_EventExposure_Subscribe. This subscription request is used to obtain the open information of the first network element (i.e., the information corresponding to the event ID) that the fourth network element wants to obtain.

[0211] Step 403c: The fourth network element receives the notification information sent by the NEF network element.

[0212] For example, after receiving a notification from a UPF network element, the NEF network element triggers Nnef_EventExposure_Notify to the AF network element. This signaling includes relevant information about the UPF network element (i.e., the first network element) that the AF network element has subscribed to. Here, the NEF network element only acts as a forwarding function and does not process the signaling. In this way, the UPF network element directly sends the collected relevant information about the first network element to the AF network element, without being forwarded by other control plane network elements such as the SMF network element.

[0213] It is understandable that the fourth network element receives notification information sent by the first network element via the NEF network element.

[0214] Optionally, in this embodiment of the application, the first network element provides related services of the first network element through service-oriented signaling, which includes notification information, at least one of the following: Nupf_EventExposure_Notify.

[0215] Optionally, in embodiment three of this application, the fourth network element is an NWDAF network element, which indirectly subscribes to the relevant services of the UPF network element through the SMF network element. Combined with... Figure 7 ,like Figure 10 As shown, step 401 can be implemented by steps 401h and 401i; step 402 can be implemented by steps 402g and 402h, or step 402 can be implemented by step 402i; and step 403 can be implemented by steps 403d or 403e.

[0216] Step 401h: The fourth network element sends the subscription request to the third network element.

[0217] Optionally, in this embodiment, a network element (e.g., an SMF network element or an AMF network element) requests the analysis results of the fourth unit using the signaling of Nnwdaf_AnalyticsSubscription_Subscribe or Nnwdaf_AnalyticsInfo_Request. This signaling carries the following parameters: Analytics ID = UE communication (which can also be another Analytics ID of the NWDAF network element in the first embodiment), Target of Analytics Reporting = SUPI, Analytics Filter Information = (Application ID, Area of ​​Interest, etc.)).

[0218] Optionally, in this embodiment of the application, the fourth network element can directly find the third network element first and then trigger the subscription, without the help of the NEF network element.

[0219] Optionally, in this embodiment of the application, the fourth network element uses SUPI to find the third network element serving this UE (actually the third network element serving the PDU session of this UE) and obtain the third network element ID, the third network element IP address, etc.

[0220] In this embodiment of the application, the subscription request is used by the third network element to determine the first network element.

[0221] Optionally, in this embodiment, the fourth network element triggers a subscription request: Nsmf_EventExposure_Subscribe(Event ID,SUPI,Application ID), hoping that the third network element will provide relevant information about the first network element. Here, the event ID is the open information that the first network element can provide. At the same time, it can carry an indication, indicating that it is requesting the first network element to provide open information with the help of the third network element. The fourth network element can also indicate whether to allow the first network element with service capabilities to open the information.

[0222] For example, the fourth network element (e.g., the NWDAF network element) sends a subscription request to the SMF network element: Nsmf_EventExposure_Subscribe. This subscription request is used to subscribe to the relevant services of a specific UPF network element in the current UE's PDU session. For instance, Nsmf_EventExposure_Subscribe can carry Event ID = UPFthroughput, indicating that it requests the UPF network element to provide throughput data. It can also carry the UE IP address, DNN, S-NSSAI, SUPI, etc., all of which are used by the third network element to determine the UPF network element (the first network element).

[0223] Step 401i: The third network element receives the subscription request sent by the fourth network element, determines the first network element, and sends the subscription request to the first network element.

[0224] For example, after the SMF network element determines the IP address or port number of the UPF network element, it sends a subscription request to the UPF network element: Nupf_EventExposure_Subscribe. This subscription request is used to subscribe to the relevant information of the first network element. This relevant information is the open information corresponding to the Event ID that the NWDAF network element hopes the first network element can provide in step 401h above.

[0225] It is understood that the fourth network element sends the subscription request to the third network element, so that the third network element can send the subscription request to the first network element.

[0226] Step 402g: The first network element receives the subscription request sent by the third network element and sends a notification message to the third network element.

[0227] For example, when a UPF network element sends Nupf_EventExposure_Notify to an SMF network element, this signaling includes information about the UPF network element (i.e., the first network element) that the NWDAF network element has subscribed to.

[0228] Step 402h: The third network element receives the notification information sent by the first network element and sends the notification information to the fourth network element.

[0229] For example, when an SMF network element sends Nsmf_EventExposure_Notify to an NWDAF network element, this signaling includes information about the UPF network element (i.e., the first network element) that the NWDAF network element has subscribed to.

[0230] Step 402i: The first network element receives the subscription request sent by the third network element and directly sends notification information to the fourth network element.

[0231] For example, when a UPF network element sends Nupf_EventExposure_Notify to an NWDAF network element, this signaling includes information about the UPF network element (i.e., the first network element) that the NWDAF network element has subscribed to.

[0232] Optionally, in this embodiment of the application, the third network element finds the first network element and sets the rules for reporting through the N4 interface. When the first network element collects data and meets the reporting conditions, it can open the information to the fourth network element.

[0233] Step 403d: The fourth network element receives the notification information sent by the third network element.

[0234] It is understood that the fourth network element receives the notification information sent by the first network element via the third network element.

[0235] Step 403e: The fourth network element directly receives the notification information sent by the first network element.

[0236] Optionally, in this embodiment of the application, the first network element provides related services of the first network element through service-oriented signaling, which includes notification information, at least one of the following: Nupf_EventExposure_Notify.

[0237] Optionally, in this embodiment of the application, the notification information is sent by the first network element under the condition that the relevant services of the first network element are opened.

[0238] It is understood that if steps 402g and 402h are executed, step 403d is executed; if step 402i is executed, step 403e is executed.

[0239] It should be noted that the logical relationship between steps 402g and 402h and step 402i is an "OR" relationship, and the logical relationship between steps 403d and 403e is also an "OR" relationship. Figure 10 To illustrate this relationship, steps 402i and 403e are shown in dashed lines.

[0240] Optionally, in this embodiment of the application, the subscription request may further include at least one of the following: a fifth instruction information and a sixth instruction information, wherein the fifth instruction information is used to instruct the third network element to request the first network element to open the relevant services of the first network element, and the sixth instruction information is used to instruct whether to allow a user plane network element with service-oriented capabilities to open the relevant services.

[0241] Optionally, in embodiment four of this application, the fourth network element is an NWDAF network element, which directly subscribes to the relevant services of the UPF network element. Combined with... Figure 7 ,like Figure 11 As shown, step 401 can be implemented by steps 401j and 401l, step 402 can be implemented by step 402j, and step 403 can be implemented by step 403f.

[0242] Step 401j: The fourth network element sends the subscription request to the third network element.

[0243] Optionally, in this embodiment, a network element (e.g., an SMF network element or an AMF network element) requests the analysis results of the fourth unit using the signaling of Nnwdaf_AnalyticsSubscription_Subscribe or Nnwdaf_AnalyticsInfo_Request. This signaling carries the following parameters: Analytics ID = UE communication (which can also be another Analytics ID of the NWDAF network element in the first embodiment), Target of Analytics Reporting = SUPI, Analytics Filter Information = (Application ID, Area of ​​Interest, etc.)).

[0244] Optionally, in the embodiments of this application, the fourth network element uses SUPI, UE IP, DNN and / or S-NSSAI, etc., to find the third network element serving this UE (actually the third network element serving the PDU session of this UE), and obtain the third network element ID, third network element IP address, etc. (for example, obtaining the ID and IP address of the SMF network element).

[0245] In this embodiment of the application, the subscription request is used by the third network element to determine the first network element.

[0246] For example, the NWDAF network element requests the SMF network element to find the UPF information of the PDU session serving the current UE by sending SUPI, UE IP, DNN and / or S-NSSAI, such as UPF IP address and port number.

[0247] Optionally, in this embodiment of the application, the fourth network element triggers a request to obtain the IP address of the first network element, which is used to subscribe to and obtain information of the first network element.

[0248] For example, the fourth network element triggers a request to obtain relevant information about the first network element from the SMF. For instance, it may use Nsmf_UPFInformation_Get, with parameters including the UE's SUPI, DNN, S-NSSAI, etc. The information is used to obtain the IP address of the first network element serving the current UE.

[0249] The fourth network element can also instruct whether to allow the first network element with service capabilities to open up information.

[0250] Step 401k: The third network element receives the subscription request sent by the fourth network element, determines the first network element, and sends the IP address, port number, or FQDN of the first network element to the fourth network element.

[0251] For example, the third network element sends the IP address, port number, or FQDN of the first network element to the NWDAF network element through Nsmf_UPFInformation_Get response.

[0252] Step 4011: The fourth network element receives the IP address, port number, or FQDN of the first network element sent by the third network element, and sends the subscription request to the first network element.

[0253] For example, an NWDAF network element triggers Nupf_EventExposure_Subscribe to a UPF network element. This subscription request is used to subscribe to relevant information of the first network element. This relevant information is the open information corresponding to the Event ID that the NWDAF network element hopes the first network element can provide.

[0254] Step 402j: The first network element receives the subscription request sent by the fourth network element and directly sends notification information to the fourth network element.

[0255] Optionally, in this embodiment of the application, the fourth network element subscribes to the events of the first network element, Nupf_EventExposure_Subscribe, with parameters including: Event ID, UE IP, SUPI, DNN, S-NSSAI, etc.

[0256] Optionally, in this embodiment of the application, after the first network element collects the data desired by the first network element, it sends a notify to the fourth network element.

[0257] Step 403f: The fourth network element directly receives the notification information sent by the first network element.

[0258] Optionally, in this embodiment of the application, the first network element provides related services of the first network element through service-oriented signaling, which includes notification information, at least one of the following: Nupf_EventExposure_Notify.

[0259] This application provides a method for subscribing to user plane service information. When the third network element finds the first network element, the fourth network element can subscribe to the relevant services of the first network element by sending a subscription request directly or indirectly to the first network element. That is, it can directly subscribe to the relevant services of the first network element, or indirectly subscribe to the relevant services of the first network element through the third network element, so as to obtain the relevant services opened by the first network element.

[0260] It should be noted that the user plane service information subscription method provided in this application embodiment can also be executed by a user plane service information subscription device, or by a control module in the user plane service information subscription device for executing the user plane service information subscription method.

[0261] Optionally, in this embodiment, the execution relationship of steps 201 and 202, 301 and 302, and 401 to 403 can be as follows: first execute steps 201 and 202, then execute steps 301 and 302, and then execute steps 401 to 403; or, first execute steps 201 and 202, then execute steps 401 to 403, and execute steps 301 and 302 during the execution of steps 401 to 403. It can be understood that the first network element can send a target request to the second network element to request registration of the first network element with the second network element; when the first network element is registered with the second network element, the third network element can send a query request to the second network element to request the second network element to find the first network element; when the third network element finds the first network element through the second network element, the fourth network element can send a subscription request to the first network element to request subscription to the relevant services of the first network element.

[0262] The following detailed description of the interaction process of the service-oriented user plane registration method, user plane determination method, and user plane service information subscription method provided in this application embodiment, through specific implementation methods (i.e., implementation methods one to three), will be provided in detail.

[0263] Implementation Method 1: Service-Oriented User Face Registration Method / Process

[0264] like Figure 12 As shown, the service-oriented user plane registration method provided in this application embodiment includes the following steps 21 and 22.

[0265] Step 21: The UPF network element sends a registration request or registration update request to the NRF network element.

[0266] In this embodiment of the application, the UPF network element can trigger a registration request (Nnrf_NFManagement_NFRegister Request) or a registration update request ( / Nnrf_NFManagement_NFUpdate Request) to the NRF network element to request the NRF network element to register the relevant information of the UP network element into the NRF network element. The NRF network element is the network element used for network element lookup in the 5G core network.

[0267] The registration request or registration update request includes at least one of the following:

[0268] An indication message, which indicates whether this UPF network element is a service-oriented UPF, includes the following analyses:

[0269] (a) Indicates whether this user plane can open related services to other network elements, such as: AMF network elements, SMF network elements, NEF network elements, AF network elements, and NWDAF network elements. The services that a UPF network element can open include at least one of the following, and each openable information or service is identified using an event ID:

[0270] QoS flow Bit Rate (per UE or per UPF);

[0271] QoS flow packet delay (per UE or per UPF);

[0272] Packet transmission (per UE or per UPF);

[0273] Packet retransmission (per UE or per UPF);

[0274] UPF resource: The resource status of the UPF;

[0275] UPF load: The load status of the UPF within a certain time interval;

[0276] UPF traffic volume: The flow capacity of the UPF;

[0277] UPF throughput: Uplink and downlink throughput;

[0278] QoS monitoring: Whether the UPF can provide QoS monitoring.

[0279] (b) The UPF can indicate whether the information or capabilities mentioned in (a) above can be subscribed to directly, or whether it needs to be subscribed to indirectly through the SMF. If subscribed directly, the subscriber directly triggers: Nupf_EventExposure_Subscribe to the UPF; if not subscribed directly, it needs to subscribe to a specific event of the UPF through the SMF.

[0280] (c) The UPF can also indicate whether it can obtain services from other 5GC core networks. For example, the UPF can indicate whether it can obtain services from the SMF, PCF, or NWDAF.

[0281] Step 22: After NRF completes the UPF registration, NRF triggers / sends a registration response or registration update response to UPF to indicate that the registration or registration update is complete.

[0282] It should be noted that the relevant explanations and beneficial effects in steps 21 and 22 above can be found in the descriptions in the above embodiments, and will not be repeated here. Implementation Method Two: The method / process for determining the user plane, i.e., selecting UPF network elements based on whether they possess service-oriented or service-opening capabilities.

[0283] like Figure 13 As shown, the method for determining the user face provided in this application embodiment includes the following steps 31 and 32.

[0284] Step 31: The SMF network element triggers / sends a UPF query request.

[0285] In this embodiment of the application, the query request (Nnrf_NFDiscovery_Request) includes at least one of the following information:

[0286] An indication message indicating whether to look up the service-oriented UPF;

[0287] This is an instruction message indicating the search for a UPF with a specific capability, i.e., providing the corresponding event ID. For example, when searching for a UPF, the SMF can instruct the search to find a UPF that can provide QoS monitoring through a service-oriented interface.

[0288] The instruction information is used to indicate that the UPF can also use the service information of other 5GC network elements.

[0289] Step 32: After the NRF finds the UPF, the NRF network element triggers / sends a query response to the SMF network element.

[0290] In this embodiment of the application, the query response (Nnrf_NFDiscovery request) includes the IP address, UPF ID, or FQDN of the UPF network element that meets the criteria.

[0291] It should be noted that this second implementation method is illustrated using the example of SMF network element selecting / searching for UPF network element, but it is not limited to SMF network element. Other service-oriented network elements (such as AMF network element or PCF network element) can also complete the selection / search of UPF network element.

[0292] For the relevant explanations and beneficial effects of steps 31 and 32 above, please refer to the descriptions in the above embodiments, which will not be repeated here.

[0293] Implementation Method 3: Subscription method / process for user plane service information, i.e., AF network element or NWDAF network element subscribing to relevant services of UPF network element.

[0294] The following describes in detail the interaction process of the user plane service information subscription method provided in this application embodiment through four implementation methods (i.e., implementation methods 3.1 to 3.4) for implementation method 3.

[0295] Implementation method 3.1: AF indirectly subscribes to relevant services of UPF through SMF.

[0296] like Figure 14 As shown, the user plane service information subscription method provided in this application embodiment includes the following steps 41 to 50.

[0297] Step 41: PDU session establishment.

[0298] In this embodiment of the application, PDU Session Establishment is a session established between the UE and the UPF, and also between the UPF and the AF.

[0299] Step 42: AF triggers a UPF event subscription request, which is used to subscribe to related UPF services.

[0300] In this embodiment of the application, the subscription request includes at least one of the following:

[0301] UE IP address;

[0302] UE SUPI or GPSI;

[0303] DNN;

[0304] S-NSSAI;

[0305] The event or information of the UPF to be subscribed to is represented by the event ID;

[0306] The instruction information requests a service-oriented UPF and directly provides notification to the AF or NEF, rather than providing it from the control plane. The instruction information for the UPF must be provided directly from the user plane.

[0307] Steps 43 to 45 are the process of NEF searching for SMF, that is, finding an SMF that is the management network element of the PDU session mentioned above.

[0308] Step 46: NEF triggers a subscription request to SMF, such as an Nsmf_EventExposure_Subscribe request.

[0309] It should be noted that the subscription request subscribes to the UPF event and includes the UPF event ID.

[0310] Step 47: After receiving the subscription request from the NEF, the SMF can find the PDU session based on the UE IP address, SUPI, etc., and find the IP address of the UPF carrying the PDU session, and then trigger the subscription request (Nupf_EventExposure_Subscribe) to the UPF.

[0311] The subscription request is used to obtain the open information of the UPF (the information / service corresponding to the event ID) that AF / NWDAF expects to obtain. That is, the subscription request includes the event ID of the open information of the UPF that AF / NWDAF expects to obtain.

[0312] Step 48: UPF sends a notification to SMF, which includes UPF’s open information / related services.

[0313] Step 49: SMF sends a notification to NEF to send the UPF's open information to NEF.

[0314] Step 50: NEF sends the UPF's open information to AF.

[0315] It should be noted that the relevant explanations and beneficial effects of steps 41 to 50 above can be found in the descriptions in the above embodiments, and will not be repeated here.

[0316] Implementation method 3.2: AF network element directly subscribes to relevant services of UPF network element

[0317] like Figure 15As shown, the user plane service information subscription method provided in this application embodiment includes the following steps 51 to 59.

[0318] Steps 51 to 55 are the same as steps 41 to 45 above.

[0319] It should be noted that after NEF finds SMF, NEF can replace AF to find the UPF network element serving the current UE and the current PDUsession.

[0320] Therefore, in step 56, the NEF network element triggers a signaling message to look up the information of the UPF network element corresponding to the current UE IP network element, DNN network element, S-NSSAI network element, SUPI network element, and event ID (information exposed by the UPF network element) from the SMF network element. In one implementation, this signaling message is the event exposure service message of the SMF network element.

[0321] Alternatively, a new one could be designed: Nsmf_UPFInformation_Get.

[0322] SMF response: Send the UPF network element's IP address, UPF ID, UPF FQDN, etc., to the NEF network element. This UPF network element must be the one serving the current UE, serving the current PDU session, and capable of providing the capability openness information corresponding to the event ID.

[0323] Step 57: The NEF network element triggers the subscription to the UPF network element, which is done in place of the AF network element.

[0324] A subscription request is triggered to the UPF network element: Nupf_EventExposure_Subscribe. This subscription request is used to obtain the open information (information corresponding to the event ID) of the UPF network element that the AF network element wants to obtain. Step 58: The UPF network element sends a notification to the NEF network element, sending the open information.

[0325] Step 59: The NEF network element then sends the information to the AF.

[0326] It should be noted that the relevant explanations and beneficial effects of steps 51 to 59 above can be found in the descriptions in the above embodiments, and will not be repeated here.

[0327] Implementation method 3.3: The NWDAF network element indirectly subscribes to the relevant services of the UPF network element through the SMF network element.

[0328] like Figure 16As shown, the user plane service information subscription method provided in this network element application embodiment includes the following steps 61 to 65.

[0329] It should be noted that the process here is similar to the process mentioned above where the AF network element indirectly subscribes to the relevant services of the UPF through the SMF network element. The difference is that the NWDAF network element can directly find the SMF network element first (i.e., without the assistance of the NEF network element) and then trigger the subscription of the relevant services of the UPF network element.

[0330] Step 61: The NF network element requests the analysis results from the NWDAF network element using the signaling Nnwdaf_AnalyticsSubscription_Subscribe. This signaling carries the parameters: Analytics ID = UEcommunication (which can also be another Analytics ID of the NWDAF network element in Example 1), Target of Analytics Reporting = SUPI.

[0331] Analytics Filter Information=(Application ID, Area of ​​Interest, etc.).

[0332] Step 62: The NWDAF network element uses SUPI to find the SMF network element serving this UE (actually the SMF network element serving the PDU session of this UE) according to steps 4-5 of Example 3-1, and obtain the SMF ID, SMF IP address, etc.

[0333] Step 63: Nsmf_EventExposure_Subscribe(Event ID, SUPI, Application ID).

[0334] The NWDAF network element triggers a request, hoping that the SMF network element will provide relevant information about the UPF network element. Here, the event ID is the open information that the UPF network element can provide. It can also carry an indication, which indicates that it is requesting the UPF network element to provide open information with the help of the SMF network element.

[0335] At the same time, the NWDAF network element can also instruct whether to allow UPF network elements with service capabilities to open information.

[0336] Step 64: The SMF network element finds the UPF network element and sets the rules for N4 reporting. Once the UPF network element collects data and meets the reporting conditions, it can open the information to the NWDAF network element.

[0337] Step 65: The UPF network element notifies the NWDAF network element that the information corresponding to the event ID has been obtained and sent to the NWDAF network element.

[0338] It should be noted that the relevant explanations and beneficial effects of steps 61 to 65 above can be found in the descriptions in the above embodiments, and will not be repeated here. Implementation Method 3.4: NWDAF directly subscribes to UPF related services

[0339] like Figure 17 As shown, the user plane service information subscription method provided in this application embodiment includes the following steps 71 to 76.

[0340] Step 71: The NF network element requests the NWDAF analysis results using the signaling Nnwdaf_AnalyticsSubscription_Subscribe. This signaling carries the parameters: Analytics ID = UE communication (or other Analytics IDs from NWDAF in Example 1), Target of Analytics Reporting = SUPI.

[0341] Analytics Filter Information=(Application ID, Area of ​​Interest, etc.).

[0342] Step 72: The NWDAF network element uses SUPI to find the SMF network element serving this UE (actually the SMF of the PDU session serving this UE) according to steps 4-5 of Example 3-1, and obtain the SMF ID, SMF IP address, etc.

[0343] Step 73: The NWDAF network element triggers a request to obtain the IP address of the UPF network element, which is used to subscribe to and obtain information about the UPF network element.

[0344] NWDAF triggers a request to obtain relevant information about the UPF network element from the SMF network element. For example, it can use Nsmf_UPFInformation_Get, with parameters including the UE's SUPI, DNN, S-NSSAI, etc. The information is used to obtain the IP address of the UPF network element serving the current UE.

[0345] At the same time, the NWDAF network element can also instruct whether to allow UPF network elements with service capabilities to open information.

[0346] Step 74: The SMF network element finds the UPF network element and sends the UE's IP address, FQDN, etc. to the NWDAF network element.

[0347] Step 75: The NWDAF network element subscribes to the events of the UPF network element using Nupf_EventExposure_Subscribe. Parameters include: Event ID, UE IP, SUPI, DNN, S-NSSAI, etc.

[0348] Step 76: After the UPF network element collects the data desired by the NWDAF network element, it sends a notify to the NWDAF.

[0349] It should be noted that the relevant explanations and beneficial effects of steps 71 to 76 above can be found in the descriptions in the above embodiments, and will not be repeated here.

[0350] Figure 18 This illustration shows a possible structural diagram of a registration device for a service-oriented user plane involved in an embodiment of this application. For example... Figure 18 As shown, the registration device 80 for the service-oriented user plane may include: a sending module 81.

[0351] The sending module 81 is used to send a target request to the second network element. The target request is a registration request or a registration update request. The target request is used to request the first network element to be registered in the second network element. When the first network element is registered in the second network element, other network elements can find the first network element through the second network element.

[0352] This application provides a service-oriented user plane registration device. The service-oriented user plane registration device can register a first network element to a second network element through a registration response or a registration update response, so that other network elements can find the first network element through the second network element, thereby solving the problem of how a UPF network element can register to an NRF network element and be found by an SMF network element.

[0353] In one possible implementation, the aforementioned target request includes at least one of the following: relevant information of the first network element and first target indication information; wherein, the first target indication information is used to indicate whether the first network element is a service-oriented user plane network element; the relevant information of the first network element includes at least one of the following: the UE's IP address, the UE's SUPI or GPSI, the UE's DNN, the UE's S-NSSAI, the relevant services supported by the first network element, the relevant services of the first network element to be subscribed to, and fourth indication information, which is used to instruct the first network element to request service-oriented services to provide the relevant services of the first network element.

[0354] In one possible implementation, the aforementioned first target indication information includes at least one of the following: first indication information, second indication information, and third indication information; wherein, the first indication information is used to indicate whether the first network element supports opening the relevant services of the first network element to other network elements, the second indication information is used to indicate whether the relevant services of the first network element are allowed to be directly or indirectly subscribed to by other network elements, and the third indication information is used to indicate whether the first network element has the ability to obtain the relevant services of other network elements.

[0355] In one possible implementation, the related services of the first network element include at least one of the following: the QoS stream bit rate of the first device, the QoS stream data packet latency of the first device, the number of data packets transmitted by the first device, the number of data packets retransmitted by the first device, the resource information of the first network element, the load information of the first network element, the traffic capacity of the first network element, the throughput of the first network element, the QoS monitoring report of the first network element, and the QoS monitoring indication information of the first network element; wherein, the first device is the first network element or the UE, and the QoS monitoring indication information is used to indicate whether the first network element supports providing QoS monitoring through service-based signaling.

[0356] In one possible implementation, each service among the related services of the first network element corresponds to an event identifier. The service-oriented user plane registration device 80 provided in this application embodiment further includes a receiving module. The receiving module is configured to receive subscription requests sent by other network elements after the sending module 81 sends a target request to the second network element. These subscription requests are for subscribing to the related services of the first network element, and include at least one event identifier. The sending module 81 is also configured to send the service corresponding to the at least one event identifier among the related services of the first network element to other network elements via service-oriented signaling.

[0357] In one possible implementation, the aforementioned first target indication information includes third indication information; the first network element has the ability to obtain relevant services from the session management function (SMF) network element, and the relevant services of the SMF network element are services open to the SMF network element; the relevant services of the SMF network element include at least one of the following:

[0358] Provide the UE's IP address / prefix, or notify the UE of changes to its IP address / prefix;

[0359] PDU session establishment and / or PDU session release notification;

[0360] UP path change notification service;

[0361] Access type change notification service;

[0362] RAT type change notification service;

[0363] PLMN change notification service;

[0364] QFI configuration service;

[0365] PDU session information for wireless LAN;

[0366] User face status information;

[0367] PDU session management and congestion control capabilities;

[0368] UE session behavior trends;

[0369] UE behavior;

[0370] UE communication trends.

[0371] In one possible implementation, the aforementioned first target indication information includes third indication information; the first network element has the ability to obtain relevant services from the NWDAF network element, and the relevant services of the NWDAF network element are open analysis functions, data acquisition functions, or statistical functions supported by the NWDAF network element; the relevant services of the NWDAF network element include at least one of the following:

[0372] Load level information;

[0373] Service experience information;

[0374] Network element load information;

[0375] Network performance statistics or prediction;

[0376] UE mobility statistics or prediction;

[0377] UE communication analysis or prediction;

[0378] Analysis or prediction of abnormal terminal behavior;

[0379] User data congestion analysis or prediction;

[0380] QoS sustainability analysis or prediction;

[0381] Session management, congestion control, experience analysis, or prediction;

[0382] Redundant transmission experience analysis or prediction;

[0383] Wireless LAN performance analysis or prediction;

[0384] UE dispersion;

[0385] Data network performance analysis or prediction.

[0386] The capabilities of NWDAF network elements for related services.

[0387] In one possible implementation, the service-oriented user plane registration device 80 provided in this application embodiment further includes a receiving module. The receiving module is configured to receive a target response sent by the second network element after the sending module 81 sends a target request to the second network element. The target response is a registration response or a registration update response, and the target response is used to instruct the first network element to complete registration or registration update.

[0388] The service-oriented user plane registration device provided in this application embodiment can implement the various processes implemented by the first network element in the above method embodiment and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0389] Figure 19 A schematic diagram of a possible structure of the user plane determination device involved in an embodiment of this application is shown. For example... Figure 19 As shown, the user plane determination device 90 may include: a sending module 91.

[0390] The sending module 91 is used to send a query request to the second network element. The query request is used to request the second network element to find the first network element. The query request includes second target indication information, which is used to indicate the first network element that meets the target conditions.

[0391] This application provides a user plane determination device. The user plane determination device can request a second network element to search for a first network element through a query request. Since the query request includes second target indication information indicating a first network element that meets the target conditions, the second network element can quickly and accurately find the first network element that meets the target conditions (i.e., meets the requirements of a third network element).

[0392] In one possible implementation, the first network element that meets the target conditions includes at least one of the following: a service-oriented first network element, a first network element with target capabilities, and a first network element that supports the use of service-oriented information from other network elements.

[0393] In one possible implementation, the first network element with the target capability is a first network element that supports open related services; the related services of the first network element include at least one of the following: the QoS stream bit rate of the first device, the QoS stream data packet latency of the first device, the number of data packets transmitted by the first device, the number of data packets retransmitted by the first device, the resource information of the first network element, the load information of the first network element, the traffic capacity of the first network element, the throughput of the first network element, the QoS monitoring report of the first network element, and the QoS monitoring indication information of the first network element; wherein, the first device is the first network element or the UE, and the QoS monitoring indication information is used to indicate whether the first network element supports providing QoS monitoring through service-based signaling.

[0394] In one possible implementation, the user plane determination device 90 provided in this application embodiment further includes a receiving module. The receiving module is configured to receive a query response sent by the second network element after the sending module 91 sends a query request to the second network element. The query response includes the IP address, port number, or FQDN of the user plane network element that meets the target conditions.

[0395] The user plane determination device provided in this application embodiment can implement the various processes implemented by the third network element in the above method embodiment and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0396] Figure 20 A schematic diagram of a possible structure of a user plane service information subscription device involved in an embodiment of this application is shown. For example... Figure 20 As shown, the user plane service information subscription device 100 may include a sending module 101 and a receiving module 102.

[0397] The sending module 101 is used to send a subscription request to the first network element. The subscription request requests subscriptions to relevant services of the first network element and includes relevant information about the first network element. The receiving module 102 is used to receive notification information sent by the first network element, which includes relevant services of the first network element.

[0398] This application provides a user plane service information subscription device. When a third network element finds a first network element, the user plane service information subscription device can subscribe to the relevant services of the first network element by directly or indirectly sending a subscription request to the first network element. That is, it can directly subscribe to the relevant services of the first network element, or indirectly subscribe to the relevant services of the first network element through a third network element, so as to obtain the relevant services opened by the first network element.

[0399] In one possible implementation, the relevant information of the first network element mentioned above includes at least one of the following: the UE's IP address, the UE's SUPI or GPSI, the UE's DNN, the UE's S-NSSAI, the relevant services of the first network element to be subscribed to, the relevant services supported by the first network element, and fourth indication information, which is used to instruct the first network element to provide the relevant services of the first network element.

[0400] In one possible implementation, the related services of the first network element include at least one of the following: the QoS stream bit rate of the first device, the QoS stream data packet latency of the first device, the number of data packets transmitted by the first device, the number of data packets retransmitted by the first device, the resource information of the first network element, the load information of the first network element, the traffic capacity of the first network element, the throughput of the first network element, the QoS monitoring report of the first network element, and the QoS monitoring indication information of the first network element; wherein, the first device is the first network element or the UE, and the QoS monitoring indication information is used to indicate whether the first network element supports providing QoS monitoring through service-based signaling.

[0401] In one possible implementation, the fourth network element is an AF network element. The sending module 101 is specifically used to send a subscription request to the third network element via the NEF network element, the subscription request being used by the third network element to determine the first network element; and to send a subscription request to the first network element via the third network element. The receiving module 102 is specifically used to receive notification information sent by the first network element via the third network element and the NEF network element; or, to directly receive notification information sent by the first network element.

[0402] In one possible implementation, the fourth network element is an AF network element. The sending module 101 is specifically used to send a subscription request to the NEF network element, and through the NEF network element, send a confirmation request to the third network element based on the subscription request. This confirmation request is used by the third network element to determine the first network element, and includes relevant information about the first network element. The third network element then sends the IP address, port number, or FQDN of the first network element to the NEF network element, and through the NEF network element, sends a subscription request to the first network element. The receiving module 102 is specifically used to receive notification information sent by the first network element via the NEF network element.

[0403] In one possible implementation, the fourth network element is an NWDAF network element. The sending module 101 is specifically used to send a subscription request to the third network element, which is used by the third network element to determine the first network element; and through the third network element, sends the subscription request to the first network element. The receiving module 102 is specifically used to receive notification information sent by the first network element via the third network element; or, directly receive notification information sent by the first network element.

[0404] In one possible implementation, the subscription request may further include at least one of the following: a fifth instruction information and a sixth instruction information, wherein the fifth instruction information is used to instruct the third network element to request the first network element to open the relevant services of the first network element, and the sixth instruction information is used to instruct whether to allow the user plane network element with service capabilities to open the relevant services.

[0405] In one possible implementation, the fourth network element is an NWDAF network element. The sending module 101 is specifically used to send a subscription request to the third network element, which is used by the third network element to determine the first network element; and to receive the IP address, port number, or FQDN of the first network element sent by the third network element, and send a subscription request to the first network element. The receiving module 102 is specifically used to directly receive notification information sent by the first network element.

[0406] The user plane service information subscription device provided in this application embodiment can implement the various processes implemented by the fourth network element in the above method embodiment and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0407] Optionally, such as Figure 21 As shown, this application embodiment also provides a communication device 5000, including a processor 5001 and a memory 5002. The memory 5002 stores a program or instructions that can run on the processor 5001. For example, when the communication device 5000 is a network element, when the program or instructions are executed by the processor 5001, they implement the various steps of the first network element side method embodiment described above and achieve the same technical effect, or implement the various steps of the third network element side method embodiment described above and achieve the same technical effect, or implement the various steps of the fourth network element side method embodiment described above and achieve the same technical effect. To avoid repetition, further details are omitted here.

[0408] This application embodiment also provides a network element, including a processor and a communication interface. The communication interface is used to send a target request to a second network element. The target request is a registration request or a registration update request, and the target request is used to request the first network element to be registered in the second network element. Wherein, when the first network element is registered in the second network element, other network elements can find the first network element through the second network element. This network element embodiment corresponds to the above-described method embodiment on the first network element side. All implementation processes and methods of the above method embodiments can be applied to this network element embodiment and achieve the same technical effects.

[0409] This application embodiment also provides a network element, including a processor and a communication interface. The communication interface is used to send a query request to a second network element. The query request requests the second network element to find a first network element. The query request includes second target indication information, which indicates the first network element that meets the target conditions. This network element embodiment corresponds to the above-described third network element-side method embodiment. All implementation processes and methods of the above method embodiments can be applied to this network element embodiment and can achieve the same technical effect.

[0410] This application embodiment also provides a network element, including a processor and a communication interface. The communication interface is used to send a subscription request to a first network element, the subscription request being used to request subscription to relevant services of the first network element, the subscription request including relevant information of the first network element; and to receive notification information sent by the first network element, the notification information including relevant services of the first network element. This network element embodiment corresponds to the above-described fourth network element-side method embodiment. All implementation processes and methods of the above method embodiments can be applied to this network element embodiment and can achieve the same technical effects.

[0411] Specifically, Figure 22 To realize a hardware structure diagram of a network element in an embodiment of this application, the network element is a first network element, or the network element is a third network element, or the network element is a fourth network element.

[0412] like Figure 22 As shown, network element 1200 includes: processor 1201, network interface 1202, and memory 1203. The network interface 1202 is, for example, a general-purpose public wireless interface.

[0413] Specifically, the network element 1200 in this application embodiment further includes: instructions or programs stored in memory 1203 and executable on processor 1201. Processor 1201 calls the instructions or programs in memory 1203 to execute the methods executed by the above modules and achieve the same technical effect. To avoid repetition, it will not be described in detail here.

[0414] The network element provided in this application embodiment can implement the various processes implemented by the first network element, the third network element and the fourth network element in the above method embodiment, and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0415] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above method embodiments and achieve the same technical effect. To avoid repetition, they will not be described again here.

[0416] The processor is the processor in the communication device described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0417] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above method embodiments and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0418] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0419] This application also provides a computer program / program product, which is stored in a storage medium and executed by at least one processor to implement the various processes of the above method embodiments and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0420] This application embodiment also provides a communication system, including: a first network element, a third network element, and a fourth network element. The first network element can be used to perform the steps of the service-oriented user plane registration method described above, the third network element can be used to perform the steps of the user plane determination method described above, and the fourth network element can be used to perform the steps of the user plane service information subscription method described above.

[0421] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0422] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a computer software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0423] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

Claims

1. A registration method for a service-oriented user interface, characterized in that, include: The first network element sends a target request to the second network element. The target request is a registration request or a registration update request. The target request is used to request the first network element to register with the second network element. In the case where the first network element is registered to the second network element, other network elements can find the first network element through the second network element; The target request includes: relevant information of the first network element and first target indication information; the first target indication information is used to indicate whether the first network element is a service-oriented user plane network element; the first target indication information includes at least one of the following: second indication information and third indication information; The second indication information is used to indicate whether the relevant services of the first network element are allowed to be directly or indirectly subscribed to by other network elements, and the third indication information is used to indicate whether the first network element has the ability to obtain the relevant services of other network elements; The relevant information of the first network element includes at least one of the following: the UE's Internet Protocol IP address, the UE's Data Network Name (DNN), the UE's Single Network Slice Selection Assistance Information (S-NSSAI), and the relevant services supported by the first network element; The relevant services of the first network element include at least one of the following: the QoS stream bit rate of the first device, the QoS stream data packet latency of the first device, the throughput of the first network element, and the QoS monitoring report of the first network element.

2. The method according to claim 1, characterized in that, The relevant information of the first network element also includes at least one of the following: the UE's Subscription Permanent Identifier (SUPI) or General Public Subscription Identifier (GPSI), the relevant services of the first network element for which subscription is requested, and the fourth indication information; wherein, the fourth indication information is used to instruct the first network element requesting service to provide the relevant services of the first network element.

3. The method according to claim 1 or 2, characterized in that, The related services of the first network element also include at least one of the following: the number of data packets transmitted by the first device, the number of data packets retransmitted by the first device, the resource information of the first network element, the load information of the first network element, the traffic capacity of the first network element, and the QoS monitoring indication information of the first network element. Wherein, the first device is the first network element or user equipment (UE), and the QoS monitoring indication information is used to indicate whether the first network element supports providing QoS monitoring through service-based signaling.

4. The method according to claim 3, characterized in that, Each service in the related services of the first network element corresponds to an event identifier; After the first network element sends a target request to the second network element, the method further includes: The first network element receives a subscription request sent by another network element. The subscription request is used to request to subscribe to the relevant services of the first network element. The subscription request includes at least one event identifier. The first network element sends the service corresponding to the at least one event identifier from the relevant services of the first network element to the other network elements via service-based signaling.

5. The method according to claim 1, characterized in that, The first target indication information includes the third indication information; The first network element has the ability to obtain relevant services from the SMF network element with session management function, and the relevant services of the SMF network element are the services that the SMF network element supports and opens. The relevant services of the SMF network element include at least one of the following: Provide the UE's Internet Protocol IP address / prefix, or notify the UE of changes to its IP address / prefix; Protocol Data Unit (PDU) session establishment and / or PDU session release notification; User-facing UP path change notification service; Access type change notification service; Notification service for changes in RAT type of wireless access technology; Public Land Mobile Network (PLMN) Change Notification Service; Quality of Service (QFI) configuration service; PDU session information for wireless LAN; User face status information; PDU session management and congestion control capabilities; UE session behavior trends; UE behavior; UE communication trends.

6. The method according to claim 1, characterized in that, The first target indication information includes the third indication information; The first network element has the ability to obtain relevant services from the network data analysis function (NWDAF) network element. The relevant services of the NWDAF network element are open analysis functions, data collection functions, or statistical functions supported by the NWDAF network element. The relevant services of the NWDAF network element include at least one of the following: Load level information; Service experience information; Network element load information; Network performance statistics or prediction; UE mobility statistics or prediction; UE communication analysis or prediction; Analysis or prediction of abnormal terminal behavior; User data congestion analysis or prediction; QoS sustainability analysis or prediction; Session management, congestion control, experience analysis, or prediction; Redundant transmission experience analysis or prediction; Wireless LAN performance analysis or prediction; UE dispersion; Data network performance analysis or prediction; The capabilities of the NWDAF network element for related services.

7. The method according to claim 1, characterized in that, After the first network element sends a target request to the second network element, the method further includes: The first network element receives a target response sent by the second network element. The target response is a registration response or a registration update response, and the target response is used to instruct the first network element to complete registration or complete registration update.

8. A method for determining a user plane, characterized in that, include: The third network element sends a query request to the second network element. The query request is used to request the second network element to find the first network element. The query request includes second target indication information, which is used to indicate the first network element that meets the target conditions. The first network element is a network element that has been registered with the second network element. The second network element is a network element that registers with the first network element after receiving the target request sent by the first network element. The target request is either a registration request or a registration update request. The target request includes: relevant information of the first network element and first target indication information; the first target indication information is used to indicate whether the first network element is a service-oriented user plane network element; the first target indication information includes at least one of the following: second indication information and third indication information; The second indication information is used to indicate whether the relevant services of the first network element are allowed to be directly or indirectly subscribed to by other network elements, and the third indication information is used to indicate whether the first network element has the ability to obtain the relevant services of other network elements; The first network element that meets the aforementioned target conditions includes: a first network element that supports the opening of related services; The relevant services of the first network element include at least one of the following: the QoS stream bit rate of the first device, the QoS stream data packet latency of the first device, the throughput of the first network element, and the QoS monitoring report of the first network element.

9. The method according to claim 8, characterized in that, The first network element that satisfies the target conditions also includes at least one of the following: a service-oriented first network element and a first network element that supports the use of service-oriented information from other network elements.

10. The method according to claim 8, characterized in that, The related services of the first network element also include at least one of the following: the number of data packets transmitted by the first device, the number of data packets retransmitted by the first device, the resource information of the first network element, the load information of the first network element, the traffic capacity of the first network element, and the QoS monitoring indication information of the first network element. Wherein, the first device is the first network element or user equipment (UE), and the QoS monitoring indication information is used to indicate whether the first network element supports providing QoS monitoring through service-based signaling.

11. The method according to any one of claims 8 to 10, characterized in that, After the third network element sends a query request to the second network element, the method further includes: The third network element receives a query response sent by the second network element, the query response including the Internet Protocol IP address, port number or fully qualified domain name (FQDN) of the user plane network element that meets the target conditions.

12. A method for subscribing to user plane service information, characterized in that, include: When the third network element finds the first network element through the second network element, the fourth network element sends a subscription request to the first network element. The subscription request is used to request to subscribe to the relevant services of the first network element. The subscription request includes relevant information of the first network element, which includes at least one of the following: the UE's Internet Protocol IP address, the UE's Data Network Name (DNN), the UE's Single Network Slice Selection Assistance Information (S-NSSAI), and the relevant services supported by the first network element. The relevant services of the first network element include at least one of the following: the QoS stream bit rate of the first device, the QoS stream data packet latency of the first device, the throughput of the first network element, and the QoS monitoring report of the first network element; The fourth network element receives notification information sent by the first network element, and the notification information includes relevant services of the first network element; Wherein, the first network element is a network element that has been registered with the second network element, and the second network element is a network element that registers with the first network element after receiving the target request sent by the first network element; the target request is a registration request or a registration update request; The target request includes: relevant information of the first network element and first target indication information; the first target indication information is used to indicate whether the first network element is a service-oriented user plane network element; the first target indication information includes at least one of the following: second indication information and third indication information; The second indication information is used to indicate whether the relevant services of the first network element are allowed to be directly or indirectly subscribed to by other network elements, and the third indication information is used to indicate whether the first network element has the ability to obtain the relevant services of other network elements.

13. The method according to claim 12, characterized in that, The relevant information of the first network element also includes at least one of the following: the UE's Subscription Permanent Identifier (SUPI) or General Public Subscription Identifier (GPSI), the relevant services of the first network element for which subscription is requested, and the fourth indication information; wherein, the fourth indication information is used to instruct the first network element requesting service to provide the relevant services of the first network element.

14. The method according to claim 12, characterized in that, The related services of the first network element also include at least one of the following: the number of data packets transmitted by the first device, the number of data packets retransmitted by the first device, the resource information of the first network element, the load information of the first network element, the traffic capacity of the first network element, and the QoS monitoring indication information of the first network element. Wherein, the first device is the first network element or user equipment (UE), and the QoS monitoring indication information is used to indicate whether the first network element supports providing QoS monitoring through service-based signaling.

15. The method according to any one of claims 12 to 14, characterized in that, The fourth network element is an application function (AF) network element; The fourth network element sends a subscription request to the first network element, including: The fourth network element sends the subscription request to the third network element via the Network Open Function (NEF) network element, and the subscription request is used by the third network element to determine the first network element; The fourth network element sends the subscription request to the first network element through the third network element; The fourth network element receives notification information sent by the first network element, including: The fourth network element receives the notification information sent by the first network element via the third network element and the NEF network element; or, The fourth network element directly receives the notification information sent by the first network element.

16. The method according to any one of claims 12 to 14, characterized in that, The fourth network element is an AF network element; The fourth network element sends a subscription request to the first network element, including: The fourth network element sends the subscription request to the NEF network element, and the NEF network element sends a confirmation request to the third network element based on the subscription request. The confirmation request is used by the third network element to determine the first network element, and the confirmation request includes relevant information of the first network element. The fourth network element sends the IP address, port number, or fully qualified domain name (FQDN) of the first network element to the NEF network element through the third network element, and sends the subscription request to the first network element through the NEF network element. The fourth network element receives notification information sent by the first network element, including: The fourth network element receives the notification information sent by the first network element via the NEF network element.

17. The method according to any one of claims 12 to 14, characterized in that, The fourth network element is the Network Data Analysis Function (NWDAF) network element; The fourth network element sends a subscription request to the first network element, including: The fourth network element sends the subscription request to the third network element, and the subscription request is used by the third network element to determine the first network element; The fourth network element sends the subscription request to the first network element through the third network element; The fourth network element receives notification information sent by the first network element, including: The fourth network element receives the notification information sent by the first network element via the third network element; or, The fourth network element directly receives the notification information sent by the first network element.

18. The method according to claim 17, characterized in that, The subscription request also includes at least one of the following: a fifth instruction and a sixth instruction, wherein the fifth instruction is used to instruct the third network element to request the first network element to open the relevant services of the first network element, and the sixth instruction is used to instruct whether to allow a user plane network element with service capabilities to open the relevant services.

19. The method according to any one of claims 12 to 14, characterized in that, The fourth network element is the NWDAF network element; The fourth network element sends a subscription request to the first network element, including: The fourth network element sends the subscription request to the third network element, and the subscription request is used by the third network element to determine the first network element; The fourth network element receives the IP address, port number, or FQDN of the first network element sent by the third network element, and sends the subscription request to the first network element. The fourth network element receives notification information sent by the first network element, including: The fourth network element directly receives the notification information sent by the first network element.

20. A registration device for a service-oriented user interface, characterized in that, include: Sending module; The sending module is used to send a target request to the second network element. The target request is a registration request or a registration update request. The target request is used to request the first network element to be registered in the second network element. In the case where the first network element is registered to the second network element, other network elements can find the first network element through the second network element; The target request includes: relevant information of the first network element and first target indication information; the first target indication information is used to indicate whether the first network element is a service-oriented user plane network element; the first target indication information includes at least one of the following: first indication information, second indication information and third indication information; The first indication information is used to indicate whether the first network element supports opening the relevant services of the first network element to other network elements; the second indication information is used to indicate whether the relevant services of the first network element are allowed to be directly or indirectly subscribed to by other network elements; and the third indication information is used to indicate whether the first network element has the ability to obtain the relevant services of other network elements. The relevant information of the first network element includes at least one of the following: the UE's Internet Protocol IP address, the UE's Data Network Name (DNN), the UE's Single Network Slice Selection Assistance Information (S-NSSAI), and the relevant services supported by the first network element; The relevant services of the first network element include at least one of the following: the QoS stream bit rate of the first device, the QoS stream data packet latency of the first device, the throughput of the first network element, and the QoS monitoring report of the first network element.

21. A device for determining a user plane, characterized in that, include: Sending module; The sending module is used to send a query request to the second network element. The query request is used to request the second network element to find the first network element. The query request includes second target indication information, which is used to indicate the first network element that meets the target conditions. The first network element is a network element that has been registered with the second network element. The second network element is a network element that registers with the first network element after receiving the target request sent by the first network element. The target request is either a registration request or a registration update request. The target request includes: relevant information of the first network element and first target indication information; the first target indication information is used to indicate whether the first network element is a service-oriented user plane network element; the first target indication information includes at least one of the following: second indication information and third indication information; The second indication information is used to indicate whether the relevant services of the first network element are allowed to be directly or indirectly subscribed to by other network elements, and the third indication information is used to indicate whether the first network element has the ability to obtain the relevant services of other network elements; The first network element that meets the aforementioned target conditions includes: a first network element that supports the opening of related services; The relevant services of the first network element include at least one of the following: the QoS stream bit rate of the first device, the QoS stream data packet latency of the first device, the throughput of the first network element, and the QoS monitoring report of the first network element.

22. A user plane service information subscription device, characterized in that, include: Sending module and receiving module; The sending module is used to send a subscription request to the first network element when the third network element finds the first network element through the second network element. The subscription request is used to request to subscribe to the relevant services of the first network element. The subscription request includes relevant information of the first network element. The relevant information of the first network element includes at least one of the following: the UE's Internet Protocol IP address, the UE's Data Network Name (DNN), the UE's Single Network Slice Selection Assist Information (S-NSSAI), and the relevant services supported by the first network element. The first network element is a service-oriented user plane network element, and the first network element supports opening its related services to other network elements through service-oriented signaling; The relevant services of the first network element include at least one of the following: the QoS stream bit rate of the first device, the QoS stream data packet latency of the first device, the throughput of the first network element, and the QoS monitoring report of the first network element; The receiving module is used to receive notification information sent by the first network element, the notification information including relevant services of the first network element; Wherein, the first network element is a network element that has been registered with the second network element, and the second network element is a network element that registers with the first network element after receiving the target request sent by the first network element; the target request is a registration request or a registration update request; The target request includes: relevant information of the first network element and first target indication information; the first target indication information is used to indicate whether the first network element is a service-oriented user plane network element; the first target indication information includes at least one of the following: second indication information and third indication information; The second indication information is used to indicate whether the relevant services of the first network element are allowed to be directly or indirectly subscribed to by other network elements, and the third indication information is used to indicate whether the first network element has the ability to obtain the relevant services of other network elements.

23. A network element, characterized in that, It includes a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions being executed by the processor to implement the steps of the service-oriented user plane registration method as described in any one of claims 1 to 7.

24. A network element, characterized in that, It includes a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions being executed by the processor to implement the steps of the method for determining the user plane as claimed in any one of claims 8 to 11.

25. A network element, characterized in that, It includes a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions being executed by the processor to implement the steps of the user plane service information subscription method as described in any one of claims 12 to 19.

26. A communication system, characterized in that, The communication system includes a service-oriented user plane registration device as described in claim 20, a user plane determination device as described in claim 21, and a user plane service information subscription device as described in claim 22. or, The communication system includes the network element as described in claim 23, the network element as described in claim 24, and the network element as described in claim 25.

27. A readable storage medium, characterized in that, The readable storage medium stores a program or instructions that, when executed by a processor, implement the steps of the service-oriented user plane registration method as described in any one of claims 1 to 7, or the steps of the user plane determination method as described in any one of claims 8 to 11, or the steps of the user plane service information subscription method as described in any one of claims 12 to 19.

Images