Direct subscription open to UPF events via user planes

Abstract

A direct subscription apparatus, method and program storage device open to UPF events via a user plane, the apparatus comprising: at least one processor; and at least one memory storing instructions that, when executed with the at least one processor, cause the apparatus to perform: sending a first message, where the first message includes at least one of: a direct subscription request to a user plane function service via the user plane interface, or a request for a direct callback subscription to the user plane function service via the user plane interface, wherein the direct callback subscription is used to initialize a tunnel with the application function; and receiving a second message based on sending the first message, wherein the second message includes information enabling the device to subscribe directly to the user plane function service via the user plane interface.

Description

Technical Field

[0001] Examples and non - limiting embodiments generally relate to communications, and more particularly, to subscriptions to application functions. Background Art

[0002] Indirect subscriptions to application functions are known. Summary of the Invention

[0003] The following summary of the invention is for illustrative purposes only. This summary of the invention is not intended to limit the scope of the claims.

[0004] According to one aspect, an example apparatus is provided, including: at least one processor; and at least one memory storing instructions that, when executed with the at least one processor, cause the apparatus to perform: sending a first message, where the first message includes at least one of the following: a direct subscription request for a user plane function service via a user plane interface, or a request for a direct callback subscription for a user plane function service via a user plane interface, where the direct callback subscription is used to initialize a tunnel with an application function; and receiving a second message based on sending the first message, where the second message includes information enabling the apparatus to directly subscribe to a user plane function service via the user plane interface.

[0005] According to one aspect, an example method is provided, including: sending a first message, where the first message includes at least one of the following: a direct subscription request for a user plane function service via a user plane interface, or a request for a direct callback subscription for a user plane function service via a user plane interface, where the direct callback subscription is used to initialize a tunnel with an application function; and receiving a second message based on sending the first message, where the second message includes information enabling the apparatus to directly subscribe to a user plane function service via the user plane interface.

[0006] According to one aspect, an example apparatus is provided, including: means for sending a first message, where the first message includes at least one of the following: a direct subscription request for a user plane function service via a user plane interface, or a request for a direct callback subscription for a user plane function service via a user plane interface, where the direct callback subscription is used to initialize a tunnel with an application function; and means for receiving a second message based on sending the first message, where the second message includes information enabling the apparatus to directly subscribe to a user plane function service via the user plane interface.

[0007] According to one aspect, an example apparatus is provided having a program storage device readable by the apparatus, tangibly embodying an instruction program executable by the apparatus for performing operations including: sending a first message, where the first message includes at least one of the following: a direct subscription request for a user plane function service via a user plane interface, or a request for a direct callback subscription for a user plane function service via the user plane interface, where the direct callback subscription is for initializing a tunnel with an application function; and receiving a second message based on sending the first message, where the second message includes information enabling the apparatus to directly subscribe to the user plane function service via the user plane interface.

[0008] According to one aspect, an example apparatus is provided, including: at least one processor; and at least one memory storing instructions that, when executed with the at least one processor, cause the apparatus to perform: receiving a first message from an application function, where the first message includes a request for a direct subscription to a user plane function service via a user plane interface; determining whether the user plane function supports a direct subscription to the user plane function service via the user plane interface; and sending a second message to the application function, the second message regarding whether the user plane function supports a direct subscription to the user plane function service via the user plane interface.

[0009] According to one aspect, an example method is provided, including: receiving a first message from an application function, where the first message includes a request for a direct subscription to a user plane function service via a user plane interface; determining whether the user plane function supports a direct subscription to the user plane function service via the user plane interface; and sending a second message to the application function, the second message regarding whether the user plane function supports a direct subscription to the user plane function service via the user plane interface.

[0010] According to one aspect, an example apparatus is provided, including: means for receiving a first message from an application function, where the first message includes a request for a direct subscription to a user plane function service via a user plane interface; means for determining whether the user plane function supports a direct subscription to the user plane function service via the user plane interface; and means for sending a second message to the application function, the second message regarding whether the user plane function supports a direct subscription to the user plane function service via the user plane interface.

[0011] According to one aspect, an example apparatus is provided having a program storage device readable by the apparatus tangibly embodying an instruction program executable by the apparatus to perform operations including: receiving a first message from an application function, wherein the first message includes a request for direct subscription to a user plane function service via a user plane interface; determining whether the user plane function supports direct subscription to the user plane function service via the user plane interface; and sending a second message to the application function, the second message regarding determining whether the user plane function supports direct subscription to the user plane function service via the user plane interface.

[0012] According to one aspect, an example apparatus is provided, comprising: at least one processor; and at least one memory storing instructions that, when executed in conjunction with the at least one processor, cause the apparatus to perform: sending a first message, wherein the first message includes a subscription request to a session management function regarding a protocol data unit session anchor user plane function; and receiving a second message based on sending the first message, wherein the second message includes a response having a user plane function identifier.

[0013] According to one aspect, an example method is provided, comprising: sending a first message, wherein the first message includes a subscription request to a session management function regarding a protocol data unit session anchor user plane function; and receiving a second message based on sending the first message, wherein the second message includes a response having a user plane function identifier.

[0014] According to one aspect, an example apparatus is provided, comprising: means for sending a first message, wherein the first message includes a subscription request to a session management function regarding a protocol data unit session anchor user plane function; and means for receiving a second message based on sending the first message, wherein the second message includes a response having a user plane function identifier.

[0015] According to one aspect, an example apparatus is provided having a program storage device readable by the apparatus tangibly embodying an instruction program executable by the apparatus to perform operations including: sending a first message, wherein the first message includes a subscription request to a session management function regarding a protocol data unit session anchor user plane function; and receiving a second message based on sending the first message, wherein the second message includes a response having a user plane function identifier.

[0016] According to one aspect, an example apparatus is provided, comprising: at least one processor; and at least one memory storing instructions that, when executed with the at least one processor, cause the apparatus to perform: sending a first message, wherein the first message includes a request for a user plane function profile with respect to a network repository function; and receiving a second message based on sending the first message, wherein the second message includes a response having a user plane function profile.

[0017] According to one aspect, an example method is provided, comprising: sending a first message, wherein the first message includes a request for a user plane function profile with respect to a network repository function; and receiving a second message based on sending the first message, wherein the second message includes a response having a user plane function profile.

[0018] According to one aspect, an example apparatus is provided, comprising: means for sending a first message, wherein the first message includes a request for a user plane function profile with respect to a network repository function; and means for receiving a second message based on sending the first message, wherein the second message includes a response having a user plane function profile.

[0019] According to one aspect, an example apparatus is provided having a program storage device readable by the apparatus tangibly embodying an instruction program executable by the apparatus to perform operations including: sending a first message, wherein the first message includes a request for a user plane function profile with respect to a network repository function; and receiving a second message based on sending the first message, wherein the second message includes a response having a user plane function profile.

[0020] According to one aspect, an example apparatus is provided, comprising: at least one processor; and at least one memory storing instructions that, when executed with the at least one processor, cause the apparatus to perform: receiving a first message from a network exposure function, the first message requesting information about whether the apparatus supports a protocol data unit session anchor; and sending a second message to the network exposure function having a response to the first message.

[0021] According to one aspect, an example method is provided, comprising: receiving a first message from a network exposure function, the first message requesting information about whether the apparatus supports a protocol data unit session anchor; and sending a second message to the network exposure function having a response to the first message.

[0022] According to one aspect, an example apparatus is provided, comprising: means for receiving a first message from a network exposure function, the first message requesting information about whether the apparatus supports a protocol data unit session anchor; and means for sending a second message to the network exposure function having a response to the first message.

[0023] According to one aspect, an example apparatus is provided having a program storage device readable by the apparatus tangibly embodying an instruction program executable by the apparatus to perform operations including: receiving a first message from a network exposure function, the first message requesting information on whether the apparatus supports a protocol data unit session anchor; and sending a second message to the network exposure function having a response to the first message.

[0024] According to one aspect, an example apparatus is provided including: at least one processor; and at least one memory storing instructions that when executed with the at least one processor cause the apparatus to perform: sending a first message to a network repository function, where the first message includes a request for a token for direct subscription by an application function to a user plane function service; and receiving a second message based on sending the first message, where the second message includes a token configured to be used for direct subscription by an application function to a user plane function service.

[0025] According to one aspect, an example method is provided including: sending a first message to a network repository function, where the first message includes a request for a token for direct subscription by an application function to a user plane function service; and receiving a second message based on sending the first message, where the second message includes a token configured to be used for direct subscription by an application function to a user plane function service.

[0026] According to one aspect, an example apparatus is provided including: means for sending a first message to a network repository function, where the first message includes a request for a token for direct subscription by an application function to a user plane function service; and means for receiving a second message based on sending the first message, where the second message includes a token configured to be used for direct subscription by an application function to a user plane function service.

[0027] According to one aspect, an example apparatus is provided having a program storage device readable by the apparatus tangibly embodying an instruction program executable by the apparatus to perform operations including: sending a first message to a network repository function, where the first message includes a request for a token for direct subscription by an application function to a user plane function service; and receiving a second message based on sending the first message, where the second message includes a token configured to be used for direct subscription by an application function to a user plane function service.

[0028] According to one aspect, an example apparatus is provided, including: at least one processor; and at least one memory storing instructions that, when executed with the at least one processor, cause the apparatus to perform: receiving a first message from a network exposure function, where the first message includes a request for a token for a direct subscription for an application function to serve a user plane function; and based on receiving the first message, sending a second message to the network exposure function having a response to the request.

[0029] According to one aspect, an example method is provided, including: receiving a first message from a network exposure function, where the first message includes a request for a token for a direct subscription for an application function to serve a user plane function; and based on receiving the first message, sending a second message to the network exposure function having a response to the request.

[0030] According to one aspect, an example apparatus is provided, including: means for receiving a first message from a network exposure function, where the first message includes a request for a token for a direct subscription for an application function to serve a user plane function; and means for sending, based on receiving the first message, a second message to the network exposure function having a response to the request.

[0031] According to one aspect, an example apparatus is provided having a program storage device readable by the apparatus tangibly embodying an instruction program executable by the apparatus for performing operations including: receiving a first message from a network exposure function, where the first message includes a request for a token for a direct subscription for an application function to serve a user plane function; and based on receiving the first message, sending a second message to the network exposure function having a response to the request.

[0032] According to one aspect, an example apparatus is provided, including: at least one processor; and at least one memory storing instructions that, when executed with the at least one processor, cause the apparatus to perform: receiving a first message from a network exposure function, where the first message includes a request regarding a user plane function service and a user plane endpoint; and based on receiving the first message, sending a second message to the network exposure function having a response to the request.

[0033] According to one aspect, an example method is provided, including: receiving a first message from a network exposure function, where the first message includes a request regarding a user plane function service and a user plane endpoint; and based on receiving the first message, sending a second message to the network exposure function having a response to the request.

[0034] According to one aspect, an example apparatus is provided, including: components for receiving a first message from a network exposure function, where the first message includes a request regarding a user plane function service and a user plane endpoint; and components for sending a second message with a response to the request to the network exposure function based on receiving the first message.

[0035] According to one aspect, an example apparatus is provided having a program storage device readable by the apparatus, tangibly embodying an instruction program executable by the apparatus for performing operations including: receiving a first message from a network exposure function, where the first message includes a request regarding a user plane function service and a user plane endpoint; and sending a second message with a response to the request to the network exposure function based on receiving the first message.

[0036] According to one aspect, an example apparatus is provided, including: at least one processor; and at least one memory storing instructions that, when executed with the at least one processor, cause the apparatus to perform: receiving, by a user plane function, a first message from a network exposure function, where the first message includes an endpoint for an application function and an authentication token; and establishing a tunnel between the application function and the user plane function using the received endpoint and authentication token for the application function.

[0037] According to one aspect, an example method is provided, including: receiving, by a user plane function, a first message from a network exposure function, where the first message includes an endpoint for an application function and an authentication token; and establishing a tunnel between the application function and the user plane function using the received endpoint and authentication token for the application function.

[0038] According to one aspect, an example apparatus is provided, including: components for receiving, by a user plane function, a first message from a network exposure function, where the first message includes an endpoint for an application function and an authentication token; and establishing a tunnel between the application function and the user plane function using the received endpoint and authentication token for the application function.

[0039] According to one aspect, an example apparatus is provided having a program storage device readable by the apparatus, tangibly embodying an instruction program executable by the apparatus for performing operations including: receiving, by a user plane function, a first message from a network exposure function, where the first message includes an endpoint for an application function and an authentication token; and establishing a tunnel between the application function and the user plane function using the received endpoint and authentication token for the application function.

[0040] According to one aspect, an example apparatus is provided, including: at least one processor; and at least one memory storing instructions that, when executed with the at least one processor, cause the apparatus to perform: sending, by a user plane function, a first message to an application function, where the first message includes a dynamic user plane function service endpoint based on a Uniform Resource Locator (URL); and receiving, by the user plane function, an authentication token from the application function, where the authentication token is at least partially based on the dynamic user plane function service endpoint based on a Uniform Resource Locator (URL).

[0041] According to one aspect, an example method is provided, including: sending, by a user plane function, a first message to an application function, where the first message includes a dynamic user plane function service endpoint based on a Uniform Resource Locator (URL); and receiving, by the user plane function, an authentication token from the application function, where the authentication token is at least partially based on the dynamic user plane function service endpoint based on a Uniform Resource Locator (URL).

[0042] According to one aspect, an example apparatus is provided, including: means for sending, by a user plane function, a first message to an application function, where the first message includes a dynamic user plane function service endpoint based on a Uniform Resource Locator (URL); and means for receiving, by the user plane function, an authentication token from the application function, where the authentication token is at least partially based on the dynamic user plane function service endpoint based on a Uniform Resource Locator (URL).

[0043] According to one aspect, an example apparatus is provided having a program storage device readable by the apparatus tangibly embodying an instruction program executable by the apparatus for performing operations including: sending, by a user plane function, a first message to an application function, where the first message includes a dynamic user plane function service endpoint based on a Uniform Resource Locator (URL); and receiving, by the user plane function, an authentication token from the application function, where the authentication token is at least partially based on the dynamic user plane function service endpoint based on a Uniform Resource Locator (URL).

[0044] According to one aspect, an example apparatus is provided, including: at least one processor; and at least one memory storing instructions that, when executed with the at least one processor, cause the apparatus to perform: receiving, from an application function, a first message, where the first message includes an authorization token and an indication of a data stream to be monitored using a direct subscription of the user plane function to the application function; and sending, based on receiving the first message, a second message from the user plane function to the application function.

[0045] According to one aspect, an example method is provided, including: receiving a first message from an application function, where the first message includes an authorization token and an indication of a data stream to be monitored using a direct subscription of the application function to a user plane function; and based on receiving the first message, sending a second message from the user plane function to the application function.

[0046] According to one aspect, an example apparatus is provided, including: means for receiving a first message from an application function, where the first message includes an authorization token and an indication of a data stream to be monitored using a direct subscription of the application function to a user plane function; and means for sending a second message from the user plane function to the application function based on receiving the first message.

[0047] According to one aspect, an example apparatus is provided having a program storage device readable by the apparatus, tangibly embodying an instruction program executable by the apparatus for performing operations including: receiving a first message from an application function, where the first message includes an authorization token and an indication of a data stream to be monitored using a direct subscription of the application function to a user plane function; and based on receiving the first message, sending a second message from the user plane function to the application function.

[0048] According to one aspect, an example apparatus is provided, including: at least one processor; and at least one memory storing instructions that, when executed with the at least one processor, cause the apparatus to perform: receiving a first message by the application function, where the first message includes a uniform resource locator (URL) for a dynamic user plane function service endpoint; and sending a second message from the application function to the user plane function at least in part based on receiving the first message.

[0049] According to one aspect, an example method is provided, including: receiving a first message by the application function, where the first message includes a uniform resource locator (URL) for a dynamic user plane function service endpoint; and sending a second message from the application function to the user plane function at least in part based on receiving the first message.

[0050] According to one aspect, an example apparatus is provided, including: means for receiving a first message by the application function, where the first message includes a uniform resource locator (URL) for a dynamic user plane function service endpoint; and means for sending a second message from the application function to the user plane function at least in part based on receiving the first message.

[0051] According to one aspect, an example apparatus is provided having a program storage device readable by the apparatus tangibly embodying an instruction program executable by the apparatus to perform operations including: receiving, by an application function, a first message, wherein the first message includes a uniform resource locator (URL) for a dynamic user plane function service endpoint; and sending, by the application function to the user plane function, a second message at least in part based on receiving the first message.

[0052] According to some aspects, the subject matter of the independent claims is provided. Some additional aspects are provided in the subject matter of the dependent claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] In the following description, the above aspects and other features are explained in conjunction with the accompanying drawings, in which:

[0054] Figure 1 is a block diagram of a possible and non-limiting example system in which the example embodiments may be practiced;

[0055] Figure 2 is a diagram showing example components in a control plane (CP) and a user plane (UP);

[0056] Figure 2A is a diagram showing a tunnel formed between a UPF and an AP;

[0057] Figure 3 is a diagram showing a modified AF session with required QoS procedures;

[0058] Figure 4 is a diagram showing an NEF function and associated messaging;

[0059] Figure 5 is a diagram showing an example method;

[0060] Figure 6 is a diagram showing an example method;

[0061] Figure 7 is a diagram showing an example method;

[0062] Figure 8 is a diagram showing an example method;

[0063] Figure 9 is a diagram showing an example method;

[0064] Figure 10 is a diagram showing an example method;

[0065] Figure 11 is a diagram showing an example method;

[0066] Figure 12 is a diagram showing an example method;

[0067] Figure 13 is a diagram showing an example method;

[0068] Figure 14 is a diagram showing an example method;

[0069] Figure 15 is a diagram showing an example method;

[0070] Figure 16 is a diagram showing an example method;

[0071] Figure 17 is a diagram showing an example method;

[0072] Figure 18 is a diagram showing an example method. Detailed implementation manners

[0073] The following abbreviations that may appear in the description and / or drawings are defined as follows:

[0074] 3GPP 3rd Generation Partnership Project

[0075] 5G 5th Generation

[0076] 5GC 5G Core Network

[0077] AF Application Function

[0078] AMF Access and Mobility Management Function ATSSS Access Service Steering, Switching and Splitting AUSF Authentication Server Function

[0079] CN Control Plane

[0080] CU Central Unit

[0081] DN Data Network

[0082] DNN Data Network Name

[0083] DU Distributed Unit

[0084] E2E End-to-End

[0085] EE Event Exposure

[0086] eNB (or eNodeB) evolved Node B (e.g., LTE base station)

[0087] EN-DC E-UTRA-NR Dual Connectivity

[0088] A node that provides NR user plane and control plane protocol termination to the UE, and acts as a secondary node in EN-DC

[0089] E-UTRA, evolved Universal Terrestrial Radio Access, i.e., LTE radio access technology

[0090] FAR, Forwarding Action Rule

[0091] gNB (or gNodeB), a base station for 5G / NR, i.e., a node that provides NR user plane and control plane protocol termination to the UE and is connected to the 5GC via the NG interface ID, Identification

[0092] IE, Information Element

[0093] I / F, Interface

[0094] LTE, Long Term Evolution

[0095] MAC, Media Access Control

[0096] MME, Mobility Management Entity

[0097] NAS, Non-Access Stratum

[0098] NEF, Network Exposure Function

[0099] NF, Network Function

[0100] ng or NG, New Generation

[0101] ng-eNB or NG-eNB, New Generation eNB

[0102] NR, New Radio

[0103] NRF, Network Repository Function

[0104] NSSF, Network Slice Selection Function

[0105] N / W or NW, Network

[0106] PCF, Policy Control Function

[0107] PDCP, Packet Data Convergence Protocol

[0108] PDU, Protocol Data Unit

[0109] PFCP, Packet Forwarding Control Protocol

[0110] PHY, Physical Layer

[0111] PSA, Protocol Data Unit Session Anchor

[0112] QFI Quality of Service Flow Identifier

[0113] QoS Quality of Service

[0114] QUIC Quick UDP Internet Connections

[0115] RAN Radio Access Network

[0116] Rel Release

[0117] RLC Radio Link Control

[0118] RRH Remote Radio Head

[0119] RRC Radio Resource Control

[0120] RU Radio Unit

[0121] Rx Receiver

[0122] S-NSSAI Single-Network Slice Selection Assistance Information

[0123] SBA Service-Based Architecture

[0124] SDAP Service Data Adaptation Protocol

[0125] SDF Service Data Flow

[0126] SID Study Item Description

[0127] SGW Serving Gateway

[0128] SMF Session Management Function

[0129] TCP Transmission Control Protocol

[0130] TS Technical Specification

[0131] TSCTSF Time-Sensitive Communication and Time Synchronization Function

[0132] Tx Transmitter

[0133] UDM Unified Data Management

[0134] UDP User Datagram Protocol

[0135] UDR Unified Data Repository

[0136] UE User Equipment (e.g., wireless, typically a mobile device)

[0137] UP User Plane

[0138] UPF User Plane Function

[0139] URL (Uniform Resource Locator)

[0140] Go to Figure 1 , which shows a block diagram of one possible and non - limiting example in which the example can be practiced. A user equipment (UE) 110, a radio access network (RAN) node 170, and (multiple) network elements 190 are shown. For example, examples of network devices, network apparatuses, or network entities can be understood to include at least a part of a transmission reception point or a cell or a gNB or a node. In Figure 1 the example of, the user equipment (UE) 110 communicates wirelessly with the wireless network 100. The UE is a wireless device that can access the wireless network 100. The UE 110 includes one or more processors 120, one or more memories 125, and one or more transceivers 130 interconnected by one or more buses 127. Each of the one or more transceivers 130 includes a receiver Rx 132 and a transmitter Tx 133. The one or more buses 127 can be an address, data, or control bus and can include any interconnect mechanism, such as a series of lines on a motherboard or integrated circuit, optical fibers, or other optical communication devices, etc. The one or more transceivers 130 are connected to one or more antennas 128. The one or more memories 125 include computer program code 123. The UE 110 includes a module 140, including one or both of parts 140 - 1 and / or 140 - 2, which can be implemented in a variety of ways. The module 140 can be implemented in hardware as module 140 - 1, such as as part of one or more processors 120. The module 140 - 1 can also be implemented as an integrated circuit or by other hardware (such as a programmable gate array). In another example, the module 140 can be implemented as module 140 - 2, which is implemented as computer program code 123 and executed by one or more processors 120. For example, the one or more memories 125 and the computer program code 123 can be configured to, together with one or more processors 120, cause the user equipment 110 to perform one or more operations described herein. The UE 110 communicates with the RAN node 170 via a wireless link 111.

[0141] The RAN node 170 in this example is a base station that provides access to the wireless network 100 by wireless devices such as the UE 110. The RAN node 170 can be, for example, a base station for 5G (also known as New Radio (NR)). In 5G, the RAN node 170 can be an NG-RAN node, which is defined as a gNB or an ng-eNB. A gNB is a node that provides NR user plane and control plane protocol termination to the UE and is connected to the 5GC (such as, for example, (one or more) network elements 190) via the NG interface. An ng-eNB is a node that provides E-UTRA user plane and control plane protocol termination to the UE and is connected to the 5GC via the NG interface. The NG-RAN node can include multiple gNBs, and they can also include a Central Unit (CU) (gNB-CU) 196 and (one or more) Distributed Units (DU) (gNB-DU), where the DU 195 is shown. Note that the DU can include or be coupled to and control a Radio Unit (RU). The gNB-CU is a logical node that hosts the RRC, SDAP, and PDCP protocols of the gNB or the RRC and PDCP protocols of the en-gNB, and controls the operation of one or more gNB-DUs. The gNB-CU terminates the F1 interface connected to the gNB-DU. The F1 interface is shown as reference 198, although reference 198 also shows the link between the remote element and the centralized element of the RAN node 170, such as the link between the gNB-CU 196 and the gNB-DU 195. The gNB-DU is a logical node that hosts the RLC, MAC, and PHY layers of the gNB or the en-gNB, and its operation is partially controlled by the gNB-CU. One gNB-CU supports one or more cells. One cell is supported by only one gNB-DU. The gNB-DU terminates the F1 interface 198 connected to the gNB-CU. Note that the DU 195 is considered to include the transceiver 160, for example, as part of the RU, but some examples of this case can have the transceiver 160 as part of a separate RU, for example, under the control of the DU 195 and connected to the DU 195. The RAN node 170 can also be an eNB (evolved NodeB) base station for LTE (Long Term Evolution), or any other suitable base station or node.

[0142] The RAN node 170 includes one or more processors 152, one or more memories 155, one or more network interfaces (N / W I / F) 161, and one or more transceivers 160 interconnected via one or more buses 157. Each of the one or more transceivers 160 includes a receiver Rx 162 and a transmitter Tx 163. The one or more transceivers 160 are connected to one or more antennas 158. The one or more memories 155 include computer program code 153. The CU 196 may include the (multiple) processors 152, the memory 155, and the network interface 161. Note that the DU 195 may also include its own one or more memories and (multiple) processors and / or other hardware, but these are not shown.

[0143] The RAN node 170 includes a module 150, the module 150 includes one or both of parts 150-1 and / or 150-2, and the module 150 can be implemented in a variety of ways. The module 150 can be implemented in hardware as the module 150-1, such as being implemented as part of one or more processors 152. The module 150-1 can also be implemented as an integrated circuit or via other hardware (such as a programmable gate array). In another example, the module 150 can be implemented as the module 150-2, and the module 150-2 is implemented as computer program code 153 and executed by one or more processors 152. For example, the one or more memories 155 and the computer program code 153 are configured to cause the RAN node 170 to perform one or more operations as described herein together with one or more processors 152. Note that the functions of the module 150 can be distributed, such as being distributed between the DU 195 and the CU 196, or being implemented only in the DU 195.

[0144] One or more network interfaces 161 communicate via a network, such as via links 176 and 131. Two or more gNBs 170 can communicate using, for example, the link 176. The link 176 can be wired or wireless or both, and can implement, for example, the Xn interface for 5G, the X2 interface for LTE, or other suitable interfaces for other standards.

[0145] One or more buses 157 may be an address, data, or control bus and may include any interconnection mechanism such as a series of lines on a motherboard or integrated circuit, fiber optic or other optical communication devices, wireless channels, etc. For example, one or more transceivers 160 may be implemented as a remote radio head (RRH) 195 for LTE or a distributed unit (DU) 195 for a gNB implementation for 5G, where other elements of the RAN node 170 may physically be located at a different location from the RRH / DU, and one or more buses 157 may be partially implemented as, for example, a fiber optic cable or other suitable network connection to connect other elements of the RAN node 170 (e.g., a central unit (CU), gNB-CU) to the RRH / DU 195. Reference 198 also indicates those suitable (plural) network links.

[0146] It should be noted that the description herein indicates that a "cell" performs functions, but it should be clear that the devices forming the cell will perform these functions. A cell forms part of a base station. That is, each base station may have multiple cells. For example, for a single carrier frequency and associated bandwidth, there may be three cells, each cell covering one-third of a 360-degree area such that the coverage area of a single base station covers an approximately elliptical or circular shape. Additionally, each cell may correspond to a single carrier, and a base station may use multiple carriers. Thus, if there are three 120-degree cells per carrier and there are two carriers, the base station has a total of six cells.

[0147] The wireless network 100 may include one or more network elements 190, which may include core network functions and provide connectivity to other networks (such as a telephone network and / or a data communication network (e.g., the Internet)) via one or more links 181. Such core network functions for 5G may include (a)ccess and (m)obility management functions ((a)MFs) and / or user plane functions ((u)PFs) and / or (s)ession management functions ((s)MFs). Such core network functions for LTE may include MME (Mobility Management Entity) / SGW (Serving Gateway) functions. These are merely example functions that may be supported by the (m)ultiple network elements 190, and note that both 5G and LTE functions may be supported. The RAN node 170 is coupled to the network element 190 via the link 131. The link 131 may be implemented as, for example, the NG interface for 5G, the S1 interface for LTE, or other suitable interfaces for other standards. The network element 190 includes one or more processors 175, one or more memories 171, and one or more network interfaces ((n)etwork (i)nterfaces) 180, which are interconnected by one or more buses 185. The one or more memories 171 include computer program code 173. The one or more memories 171 and the computer program code 173 are configured to cause the network element 190 to perform one or more operations in conjunction with the one or more processors 175.

[0148] The wireless network 100 may implement network virtualization, which is the process of combining hardware and software network resources with network functions into a single software-based management entity (virtual network). Network virtualization involves platform virtualization, typically combined with resource virtualization. Network virtualization is classified as external virtualization and internal virtualization. External virtualization combines many networks or parts of networks into virtual units, and internal virtualization provides network-like functions for software containers on a single system. Note that the virtualized entities resulting from network virtualization still use hardware (such as processors 152 or 175 and memories 155 and 171) to some extent for implementation, and such virtualized entities also produce technical effects.

[0149] The computer-readable memories 125, 155, and 171 can be of any type suitable for the local technical environment and can be implemented using any suitable data storage technology, such as semiconductor-based memory devices, flash memory, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. The computer-readable memories 125, 155, and 171 can be components for performing storage functions. The processors 120, 152, and 175 can be of any type suitable for the local technical environment and, by way of non-limiting example, can include one or more of the following: general-purpose computers, special-purpose computers, microprocessors, digital signal processors (DSPs), and processors based on multi-core processor architectures. The processors 120, 152, and 175 can be components for performing functions, such as controlling the UE 110, the RAN node 170, and other functions as described herein.

[0150] In general, various embodiments of the user equipment 110 can include, but are not limited to, cellular phones such as smart phones, tablet computers, personal digital assistants (PDAs) with wireless communication capabilities, portable computers with wireless communication capabilities, image capture devices such as digital cameras with wireless communication capabilities, game devices with wireless communication capabilities, music storage and playback devices with wireless communication capabilities, Internet devices that allow wireless Internet access and browsing, tablet computers with wireless communication capabilities, and portable units or terminals incorporating combinations of these functions.

[0151] Reference is also made to Figure 2 , an example control plane (CP) can include, for example, the following: NSSF, NEF, NRF, PCF, UDM, AF, AMF, AUSF, and SMF. Additionally, an example user plane (UP) can include the UE, RAN, UPF, and DN. The data network DN (e.g., an external data network) can also include one or more application functions AF. Note that this is merely an illustrative example showing some features and is not intended to be construed as limiting.

[0152] 3GPP Rel.18 has defined direct and indirect subscriptions for opening services for UPF events via the control plane. However, direct subscriptions for opening services for UPF events by the AF via the user plane are not defined and can be much faster than traditional control plane indirect subscriptions. Currently, the AF subscribes to UPF events via the PCF and SMF. To subscribe to UPF events, the AF needs to find the target PCF / SMF / UPF. Therefore, this is an indirect subscription process. With the features described herein, the subscription process can be enhanced to allow direct subscriptions for UPF events from applications via the user plane.

[0153] The features described herein can be used to allow direct subscriptions by an AF to UPF event exposure services via the user plane. This may correspond to a trusted (e.g., MNO-owned AF) or an untrusted AF. In either case, terms such as the N6 or N6 interface or the user plane interface refer to the reference point between the UPF and the data network (DN) where the trusted / untrusted AF is located. The N6 interface supports both user plane and control plane signaling (e.g., Radius / Diameter signaling). In this document, for reference, in the context of certain features described, the use of the user plane refers to via the N6 or N6 interface. The AF can request the 5GC to directly subscribe to UPF event exposure services, and there may be authorization for the direct subscription to UPF event exposure services. The AF can discover the attributes of the UPF event exposure services to be subscribed to, such as the relevant endpoints, the (multiple) versions of the exposure services, etc. When a subscription request arrives at the UPF from the AF, the UPF can know that the request has been correctly authorized by the 5GC. The AF can also be informed of changes to the PSA UPF, and thus change its subscription to the new PSA UPF.

[0154] Example aspect 1: Direct subscription by an AF to UPF N6 endpoints (static (NRF)) using N6 or the user plane

[0155] Using the features described herein, a direct subscription by an AF to QoS monitoring for a PDU session of a UE can be provided, for example, via N6 or the user plane. This may be similar to QoS monitoring as specified in 3GPP TS29.564. One example can include the following:

[0156] a) The UPF can expose its Nupf_EventExposure service via one or more N6 endpoints (in addition to the endpoints exposed within the 5GC). This can be, for example, via <IP address, port>-(multiple) pairs reachable via N6. The UPF can register the attributes of the N6 endpoints and (multiple) service instances at the NRF in its profile.

[0157] b) The AF can use existing services to request a session with QoS from the NEF / PCF. For example, the existing services may include the Nnef_AFsessionWithQoS_Create request and the Npcf_PolicyAuthorization_Create request. The AF can additionally request the possibility and authorization for direct subscription to the PSA UPF for QoS monitoring events.

[0158] c) The NEF / PCF may continue the authorization requested by the AF, including authorizing the AF to directly subscribe to the UPF event exposure service via the UP. An untrusted AF may interact with the NEF, which in turn interacts with the PCF. A trusted AF may directly interact with the PCF.

[0159] d) The NEF / PCF may identify the SMF serving the relevant PDU session based on the subscription information from the UDM.

[0160] e) The SMF may be configured to expose a new event: the UPF ID of the PSA UPF serving the PDU session.

[0161] f) The NEF / PCF may request the SMF to obtain the UPF ID of the PSA UPF serving the PDU session.

[0162] g) The NEF / PCF may obtain the UPF profile of the PSA UPF serving the PDU session from the NRF and check whether the UPF profile supports direct subscription via the user plane.

[0163] h) The NEF / PCF may return to the AF the attributes (N6 endpoint, version, http scheme, etc.) of the UPF event exposure service that can be used via the user plane. The NEF / PCF may also return an access token to be used by the AF when directly subscribing to the UPF event exposure service via the user plane.

[0164] i) The AF may utilize the information provided by the NEF / PCF and directly subscribe to the UPF event exposure service, such as via the N6 interface or the user plane, providing a description of the data flow to be monitored during the direct subscription to the UPF.

[0165] j) The UPF may check the authorization token and, if possible, accept the AF request.

[0166] k) The UPF may still need to identify the relevant QFI for which it monitors the request. For this purpose, the SMF may expose a new operation that maps QoS parameters / references to the relevant QFI. In one example alternative, the AF may provide QoS monitoring references to the NEF, which may be passed to the PCF, SMF, and UPF together with the QFI of the QoS flow. The AF may then directly subscribe to the UPF, providing the QoS monitoring references, enabling the UPF to derive the QoS flow or traffic flow subject to direct AF subscription.

[0167] It should be noted that due to various reasons, the PSA UPF of a PDU session may change. The following are examples of notifying the AF of the PSA UPF change:

[0168] l) The NEF open service can be provided such that it supports a new event: PSA UPF change.

[0169] m) The AF can subscribe to the above NEF events. The subscription can be either explicit or implicit. For example, when the AF requests the possibility of directly subscribing to the UPF, the subscription can be implicit.

[0170] n) The SMF open service can be provided such that it supports a new event: PSA UPF change.

[0171] o) The NEF can subscribe to the above SMF events. The subscription can be either explicit or implicit. For example, when the NEF requests to directly subscribe to the SMF for any new or existing event via which the UPF ID is provided, the subscription can be implicit.

[0172] p) When the PSA UPF changes, a notification can be sent, including the attributes of the UPF event open service of the new PSA UPF.

[0173] The features described herein can be used in conjunction with the static UPF endpoint open via N6. For example, the relevant endpoints may already be open via N6, and the corresponding information can be maintained at the NRF. However, for example, a new NEF<->UPF communication can be provided, via which the NEF, once it has received a request from the AF to directly subscribe to the UPF via the UPF, can talk to the UPF, such as asking the UPF if it can open some endpoints via N6, and informing the NEF of the contact information and the relevant access token.

[0174] In an alternative, the UPF can contact the AF (which provides access information for it in the subscription), so that the static port open of the UPF in N6 is not required; for example, the UPF can pick any port. In one example, a "token" can be used for authentication.

[0175] In another example, using the features described herein, the direct subscription by the AF via N6 or the user plane to the UPF event open service for future events is not limited to QoS monitoring as described above. In one type of example, a new NEF service may be defined, such as used by the AF to directly subscribe to the UPF event open service via the user plane and having at least some of the other features described above.

[0176] It should also be noted that although the above description relates to UPF event open services, the principles described herein can be extended to other UPF services. The features described herein can be extended to allow the AF to directly invoke other UPF services via the user plane. As an example, the UPF can support new UPF open services for direct subscription and / or notification via the user plane, which is different from the existing UPF event open services.

[0177] If the UPF supports direct subscription to its event open services via the user plane, it can advertise in its configuration file that the UPF is registered at the NRF. Dedicated open service instances can be used because these service instances are accessed via N6 and are thus open. In this example, general service instances that are subscribed via both the control plane and the user plane are not excluded.

[0178] The dedicated service instances for subscription via the user plane can be correspondingly marked in the UPF configuration file registered at the NRF. For example, an attribute (such as a boolean value) can be included in the relevant NFService IE. For example, an attribute upbasedSubscription with a default value can be included, and the default value indicates that "UP-based subscription is not supported (e.g., boolean false)".

[0179] The discovery query parameters can be correspondingly enhanced to support the new query parameter up-based-subscription to discover UPF service instances that support (or do not support) UP-based subscription. In this way, dedicated service instances for subscription via the user plane will not even be discovered for subscription via the control plane, and vice versa. If general service instances for subscription via both the control and user planes are used, these service instances in the UPF configuration file can newly support registering different endpoints / parameters for UP-based subscription (as opposed to subscription via the control plane / 5GC NF). The endpoints opened for subscription via the user plane can be correspondingly marked.

[0180] The dedicated service instances for subscription via the user plane can correspondingly set additional attributes, such as allowedNfTypes = AF, and optional attributes that are not applicable via N6 can be omitted.

[0181] Also refer to Figure 3 , the AF can utilize the "AF session with required QoS procedures" defined in clause 4.15.6.6 of 3GPP TS23.502, but with the following changes:

[0182] · At step 1, as shown by 301, the request for the Nnef_AFsessionWithQoS_Create request from AF to NEF may include a direct subscription for opening a service to UPF via the UP.

[0183] · At step 5, as shown by 305, the response for the Nnef_AFsessionWithQoS Create response from NEF to AF may include the UPF open service via the UP attribute authorization token.

[0184] Also refer to Figure 4 , Figure 4 which shows the new function and the related message passing completed in parallel between step 1 and step 5 in Figure 3 . In other words, Figure 3 steps 2 to 4b in Figure 4 and steps 2 to 5 in

[0185] Figure 3 · At step 1 (also shown as 301 in

[0186] ), NEF may determine to authorize the AF request; including additional requirements for authorizing (or not authorizing) a direct subscription for opening a service to UPF events via the UP. · At step 2, NEF may determine the SMF serving the UE / PDU session from the subscription information using the existing specification.

[0187] · At step 3a, NEF may subscribe to the Nsmf_EventExposure service that supports the new event "PSA UPF change" and input the PDU session ID of the PDU session for which QoS monitoring is required.

[0188] · At step 3b, after successful subscription, SMF may return the UPF ID of the current PSA UPF to NEF and further notify NEF when a PSA UPF change occurs.

[0189] · At steps 4a and 4b, NEF may obtain the UPF profile of the PSA UPF using the UPF ID and determine whether the UPF profile supports a direct subscription for opening a service to it via the user plane.

[0190] · If this is the case, then as shown by steps 5a and 5b, NEF may request an authorization token from the NRF on behalf of AF to be used for a direct subscription for opening a service to UPF events.

[0191] · NEF may return a response with the new required information to AF, as shown by step 6 (also shown as 305 in Figure 3 ).

[0192] AF can utilize Figure 3 the information in the response "Step 5" (corresponding to Figure 4 the response "Step 6" in

[0193] to directly subscribe to the UPF event opening service through the user plane. The UPF can check the authorization token and accept the request accordingly. The UPF may still need to determine the QFI for which it is requested to monitor. For this purpose, the UPF can utilize a new operation opened by the SMF, which maps QoS parameters / references to the relevant QFI.

[0194] In an alternative example (not shown in the figure), the AF can provide QoS monitoring references to the NEF, and these QoS monitoring references are passed to the PCF, SMF, and UPF together with the QFI of the QoS flow. Then, the AF can directly subscribe to the UPF that provides the QoS monitoring references, which enables the UPF to export the QoS flow or traffic flow subject to direct AF subscription.

[0195] As described above, the PSA UPF of a PDU session may change for various reasons. The following can be provided to notify the AF about the PSA UPF change:

[0196] 1. The NEF open service supports a new event: PSA UPF change.

[0197] 2. The AF subscribes to the above NEF event.

[0198] 3. The SMF open service supports a new event: PSA UPF change.

[0199] 4. The NEF subscribes to the above SMF event.

[0200] 5. When the PSA UPF changes, a notification is sent, and the notification includes the attributes of the UPF event opening service of the new PSA UPF.

[0201] 6. The AF subscribes to the new PSA UPF through the user plane and unsubscribes from the old PSA UPF.

[0202] In an alternative example, and / or as a generalization of the QoS monitoring case, a new NEF service can be defined instead of extending the existing Nnef_AFsessionWithQoS.

[0203] In an alternative example, the principles described herein can be extended to other UPF services, i.e., allowing the AF to directly invoke other UPF services through the user plane. For example, the UPF can support new UPF open services for direct subscription / notification via the user plane, which is different from the existing UPF event open services.

[0204] The features described herein can be used to achieve an effective subscription to the UPF event open service without the latency implied when the same request is sent via the control plane. The above features can be used for the direct subscription of the UPF event open service by the AF via the user plane. As described in further detail below, the features can be used to ensure that the UPF does not open via the N6 open service endpoint unless needed. In other words, if no service consumer subscribes to the event open service via N6, the features can be used to ensure that no additional UPF information is opened. This can be used to maximize security by not opening a new attack surface. Additionally, the features described herein can be used to provide direct subscriptions supported via N6 or the user plane without opening any new or additional information in the N6 of the DN.

[0205] Example aspect 2: Direct subscription by the AF using on-demand (NEF on request) UPF N6 endpoint opening via N6 or the user plane.

[0206] In this alternative example, it is not assumed that the UPF has pre-opened any of its N6 endpoints and registered them with the NRF. The above steps a to f for example aspect 1 are valid up to step "g". At step "g", the NEF cannot obtain the open endpoints of the UPF from the NRF because they do not exist. Using the features in this example aspect 2, the UPF can open its N6 endpoints when needed, and this need can be indicated by requesting the event opening of the UPF (via the UP N6 endpoint information). For this purpose, for example, the UPF can implement a new service, such as one called Nupf_GetN6EndpointInfo. The UPF can filter the consumers of its new service. For example, the UPF may not allow all NEFs to consume, but only some NEFs connected to a specific Af that has a certain relationship with the operator. To consume the Nupf_GetN6EndpointInfo service, the NEF can provide an authorization or access token and request the PSA UPF to provide the event open service via the UP endpoint. Once the NEF request is authorized, the PSA UPF can reply with the endpoint information to the NEF. Thereafter, the process can continue as described in step "h" above.

[0207] Also refer to Figure 5 and some features of this example aspect 2 are shown. Figure 5 Similar to Figure 4 but where Figure 4Steps 5a and 5b are affected, and the NEF <-> communication is replaced by NEF <-> UPF communication because the NEF needs information not available in the NRF, and the UPF is responsible for providing this information based on its internal actions, i.e., opening new endpoints.

[0208] Compared with Figure 4 the baseline example of Figure 5 the new / modified parts of

[0209] · The UPF service profile in the NRF does not contain open endpoint information because such information does not exist. Instead, the service profile of the UPF includes service names that can be used to query N6 endpoint information from the UPF.

[0210] · At step 5a, the NEF can send an HTTP GET request to the UPF to query N6 endpoint information and provide the authorization / access token with which the N6 endpoint will be associated.

[0211] · At step 5b, the UPF can check the available endpoints and select an existing endpoint or create a new endpoint, and associate the target endpoint with the provided token.

[0212] · At step 5c, the UPF can return the endpoint information to the NEF with an HTTP status of "200", indicating a successful service operation.

[0213] · At step 5d, the UPF can return the problem details to the NEF with an HTTP status (3xx / 4xx / 5xx) indicating an unsuccessful service status.

[0214] New Nupf_GetN6EndpointInfo service:

[0215] The Nupf_GetN6EndpointInfo service enables the UPF to provide its open N6 endpoint information, e.g., the N6 IP address and port number when queried by an NF service consumer (e.g., the NEF) for a given authorization / access token. The UPF can associate the given authorization / access token with the returned IP address and port number so that a new client can request connection establishment with the associated authorization / access token. Further information for this example is given in Tables 1 and 2 below:

[0216] Table 1: Service operations supported by the Nupf_GetN6EndpointInfo service.

[0217]

[0218] Table 2: Resource and method overview.

[0219]

[0220] Example aspect 3: Direct subscription by AF via N6 or the user plane without opening the UPF N6 endpoint.

[0221] In the above example aspects 1-2, the UPF needs to "statically" open its N6 attributes to the NRF or "non-statically" (i.e., on request) to the NEF. Then, the AF can directly connect to the endpoint opened by the PSA UPF. However, for example, another option is to avoid opening the UPF N6 endpoint, such as by having the UPF create a tunnel with the AF. An example of this case Figure 2A is shown. Then, this tunnel can be used by the AF for direct subscription. For example, this new alternative of using a tunnel can be called callback_subscription. One benefit of this solution is that the UPF does not need to use or open any static (<IP,port>) configuration, and it can "freely" pick them, thus making any potential attack vectors against the UPF via the N6 interface less imminent. This example aspect 3 may modify some of the key steps a to k mentioned above as follows: a) The UPF can use callback_subcscription to open its capabilities for the Nupf_EventExposure service via N6. This means it does not need to register any N6 endpoints in the NRF.

[0222] b) The AF uses existing services (e.g., Nnef_AFsessionWithQoS_Create request and Npcf_PolicyAuthorization_Create request) to request a session with QoS from the NEF / PCF. It can additionally request the possibility of directly callback_subscribing to the PSA UPF for QoS monitoring events. For callback_subscribe, the subscription from the AF is sent through a tunnel / connection first created and initiated by the UPF. For this, the AF opens an endpoint reachable from the UPF via N6. The opened endpoint and the authorization / access token are provided to the NEF / PCF.

[0223] c) The NEF / PCF continues the authorization requested by the AF, including authorizing the AF to directly callback_subscribe to UPF events via the UP to open the service

[0224] d) <Same - no change>

[0225] e) <Same - no change>

[0226] f) <Same - no change>

[0227] g) <Same - No change>

[0228] h) The NEF / PCF obtains the UPF configuration file of the PSA UPF serving the PDU session and checks whether it supports direct callback_subscription via the user plane:

[0229] · The NEF / PCF may pass the AF endpoint for tunnel establishment provided by the AF in step b), together with the authorization or access token provided by the AF, to the PSA UPF via a new service opened by the UPF or an extension of the service opened by the UPF event.

[0230] · The UPF can use this information to establish a tunnel with the AF.

[0231] · The AF can receive the tunnel establishment request and the authorization token. If so, the tunnel can be created.

[0232] · After the tunnel is established, the AF may require an authorization or access token to use the service opened by the UPF event via the UP. The NEF can provide such a token to the AF after receiving the token from the NRF. Alternatively, the NEF / PCF can act as an authorization server and create and provide an authorization or access token that will be used in both the AF and the UPF for this option.

[0233] · The NEF / PCF can return the attributes of the service opened by the UPF event to the AF (version, http scheme, etc.) using callback_subscription via the user plane.

[0234] i) The AF can use the information provided by the NEF / PCF and directly subscribe to the service opened by the UPF event via the tunnel, providing a description of the data stream to be monitored in the direct subscription to the UPF.

[0235] j) <Same – No change>

[0236] k) <Same – No change>

[0237] Also refer to Figure 6 where some features of this example aspect 3 are shown. Figure 6 Similar to Figure 4 but where steps 1 and 5 (5a and 5b) are affected and the NEF <-> NRF communication is replaced by NEF <-> UPF communication because the NEF provides information that is not available in the NRF in this example. Figure 5 The step 1 in Figure 6Step 1 therein includes a request for a direct callback subscription for services opened by the UPF via the user plane, where the AF endpoint and token are provided. Figure 5 Step 6 therein includes a response with a service profile, N6 endpoint, and token. On the other hand, Figure 6 Step 6 therein includes a response with a service profile and callback status and details for the required tunnel.

[0238] Figure 5 The new / modified part 6 is as follows compared to the Figure 4 baseline example:

[0239] · The service profile of the UPF is provided in the NRF

[0240] · The AF requests a direct callback_subscription via N6 and provides the relevant (N6) endpoint information (including its endpoint IP address, port number, and authorization / access token) to the NEF. The NEF performs AF authorization based on the callback_subscription preference.

[0241] · At step 5a, the NEF uses the new Nupf_Callback_service (POST) together with any authorization / access token provided by the AF to provide the AF endpoint information to the PSA UPF and requests the PSA UPF to perform a callback to the AF based on the provided information.

[0242] · At step 5b, the PSA UPF initializes the callback_subscription using the AF information, for example, initializes the tunnel creation with the AF.

[0243] · At step 5c, the UPF returns the success status of the service to the NEF.

[0244] · At step 5d, the UPF returns the problem details to the NEF, with an HTTP status (3xx / 4xx / 5xx) indicating an unsuccessful service status.

[0245] The new Nupf_Callback service:

[0246] · The Nupf_Callback service enables the UPF to receive AF (N6) endpoint information (ae-info: IP address, port number, authorization / access token) as part of a callback_subscription service request.

[0247] · When creating a tunnel with the AF, the UPF uses the provided authorization / access token along with the provided IP address and port number. The token is provided from the PSA UPF to the AF with the tunnel creation request, and then the AF can authorize the tunnel creation request.

[0248] Further information for this example is given in Tables 3 and 4 below:

[0249] Table 3: Service operations supported by the Nupf_Callback service.

[0250]

[0251] Table 4: Overview of resources and methods.

[0252]

[0253] The above features can be used to achieve an effective subscription to UPF events without the latency implied when the same request is sent via the control plane.

[0254] Example aspect 4: Direct subscription by the AF via N6 or the user plane, without UPF N6 endpoint opening and UPF URL access

[0255] In the above example aspect 3, the UPF needs to create an IP tunnel first before it can subscribe. However, for this example aspect 4, a URL based on a dynamic N6 endpoint can be created for a given PDU session. This example aspect 4 can modify some of the key steps a to o above (regarding example aspect 1) as follows:

[0256] a) The UPF can expose its Nupf_EventExposure service, and the Nupf_EventExposure callback URL can be provided to the AF (via the NEF / PCF), where the URL provides the required authentication mechanism. These dynamic URLs can be secure and reduce the DDoS attack vector in terms of the fixed port opening method.

[0257] b) <Same – no change>

[0258] c.) <Same – no change>

[0259] d.) <Same – no change>

[0260] e) <Same – no change>

[0261] f) <Same – no change>

[0262] g) The NEF / PCF can obtain the UPF profile of the PSA UPF serving the PDU session from the NRF and check whether it supports direct subscription via the user plane.

[0263] The NEF / PEF can obtain the dynamic URL for a given service with an AF identifier from the UPF. The dynamic URL may contain the PDU session ID, which can uniquely identify the given PDU session in the UPF when requested by the AF at a later time.

[0264] h) The NEF / PCF returns the attributes of the UPF event exposure service that can be used via the user plane (dynamic N6 endpoint, version, http scheme, authentication details, unique PDU session ID, etc.). The NEF / PCF can also return an access token to be used by the AF when directly subscribing to the UPF event exposure service via the user plane.

[0265] i) <Same - No change>

[0266] j) Based on the URL, the UPF performs internal authentication in the 5GC, and the UPF checks the authorization token and, if possible, accepts the AF request.

[0267] k) <Same - No change>

[0268] The PSA UPF of a PDU session may change for various reasons. The following innovations are proposed to notify the AF about the PSA UPF change:

[0269] l) <Same - No change> Same

[0270] m) <Same - No change> Same

[0271] n) <Same - No change> Same

[0272] o) After the PSA UPF changes, a notification can be sent, including the attributes of the UPF event exposure service of the new PSA UPF.

[0273] p) The new UPF URL and its corresponding authentication details can be provided.

[0274] According to an example embodiment, an apparatus is provided, comprising: at least one processor; and at least one memory storing instructions that, when executed with the at least one processor, cause the apparatus to perform: sending a first message, where the first message includes at least one of the following: a direct subscription request for a user plane function service via a user plane interface, or a request for a direct callback subscription for a user plane function service via a user plane interface, where the direct callback subscription is used to initialize a tunnel with an application function; and receiving a second message based on sending the first message, where the second message includes information enabling the apparatus to directly subscribe to the user plane function service via the user plane interface.

[0275] The user plane function service may include an event exposure service. A first message may be sent from an application function to a network exposure function, and a second message may be received by the application function from the network exposure function. The second message may include an authorization token that is configured to permit direct subscription to the user plane function service by the device via the user plane interface. The second message may include user plane function service information for direct subscription to the user plane function service by the device via the user plane interface. The user plane function service information may include at least one of the following: addressing information enabling access to the user plane service via the user plane interface, an HTTP or HTTPS scheme for direct subscription to the user plane function service, an HTTP version supported by the user plane service. The first message may include at least one of an Nnef_AFsessionWithQoS_Create request or an Npcf_PolicyAuthorization_Create request. The request may be configured to request the possibility and authorization regarding directly subscribing to a protocol data unit session anchor user plane function for user plane related events. At least one memory may store instructions that, when executed in conjunction with at least one processor, cause the device to perform directly subscribing to the user plane function service via the user plane interface using the information received in the second message by the application function of the device, and provide a description of at least one data flow to be monitored in the direct subscription to the user plane function. The device may directly subscribe to the user plane function service via the user plane interface by sending an HTTP or HTTPS request using the addressing information of the user plane function service and the HTTP version supported by the user plane function service, and including the received authorization token (if received) in the second message. At least one memory may store instructions that, when executed in conjunction with at least one processor, cause the device to perform providing a quality of service (QoS) monitoring reference to the network exposure function to be delivered together with at least one service quality flow identifier of a QoS flow. At least one memory may store instructions that, when executed in conjunction with at least one processor, cause the device to perform directly subscribing by the application function of the device to a user plane function that provides a QoS monitoring reference enabling the user plane function to derive Qos flows or traffic flows subject to the direct subscription. At least one memory may store instructions that, when executed in conjunction with at least one processor, cause the device to perform a direct subscription to the user plane function service via the user plane interface using a request or an additional request via a tunnel. At least one memory may store instructions that, when executed in conjunction with at least one processor, cause the device to perform the formation of a tunnel created by the device initiated by the user plane function.At least one memory may store instructions which, when executed with at least one processor, cause the device to perform the formation of the tunnel with the user plane function initiated by the application function. At least one memory may store instructions which, when executed with at least one processor, cause the device to perform opening an endpoint reachable via a user plane interface from the user plane function. At least one memory may store instructions which, when executed with at least one processor, cause the device to perform receiving a dynamic user plane function service endpoint at least partially based on a Uniform Resource Locator (URL) including an authentication mechanism before sending a first message. The first message may include an application function endpoint and an authorization token. The user plane interface may correspond to the user plane interface between the user plane function and the data network where the application function is located.

[0276] Also refer to Figure 7, according to an example embodiment, a method may be provided, including: as shown by block 702, sending a first message, where the first message includes at least one of the following items: a direct subscription request for a user plane function service via a user plane interface, or a request for a direct callback subscription for a user plane function service via a user plane interface, where the direct callback subscription is used to initialize a tunnel with an application function; and as shown by block 704, receiving a second message based on sending the first message, where the second message includes information enabling the device to directly subscribe to a user plane function service via the user plane interface. The user plane function service may include an event exposure service. The first message may be sent from an application function to a network exposure function, and the second message may be received by the application function from the network exposure function. The second message may include an authorization token configured to permit the device to directly subscribe to the user plane function service via the user plane interface. The second message may include user plane function service information for the device to directly subscribe to the user plane function service via the user plane interface. The user plane function service information may include at least one of the following items: addressing information enabling access to the user plane service via the user plane interface, an HTTP or HTTPS scheme for directly subscribing to the user plane function service, an HTTP version supported by the user plane service. The first message may include at least one of an Nnef_AFsessionWithQoS_Create request or an Npcf_PolicyAuthorization_Create request. The request may be configured to request the possibility and authorization regarding directly subscribing to a protocol data unit session anchor user plane function for user plane-related events. The method may include directly subscribing to the user plane function service via the user plane interface using the information received by the application function of the device in the second message and providing a description of at least one data stream to be monitored in the direct subscription to the user plane function. The method may include sending an HTTP or HTTPS request by using the addressing information of the user plane function service and the HTTP version supported by the user plane function service and directly subscribing to the user plane function service via the user plane interface by including the received authorization token (if received) in the second message. The method may include providing a quality of service (QoS) monitoring reference to the network exposure function to be passed together with at least one service quality flow identifier of a QoS flow. The method may include the application function of the device directly subscribing to the user plane function to provide a QoS monitoring reference that enables the user plane function to export Qos flows or traffic flows subject to the direct subscription. The method may include directly subscribing to the user plane function service via the user plane interface by using a request or an additional request via a tunnel. The method may include the formation of a tunnel created by the user plane function with the device.The method may include forming, by an application function, the tunnel with the user plane function. The method may include opening, from the user plane function, an endpoint reachable via a user plane interface. The method may include receiving, before sending a first message, a dynamic user plane function service endpoint based on a Uniform Resource Locator (URL) that at least partially includes an authentication mechanism. The first message may include an application function endpoint and an authorization token. The user plane interface may correspond to the user plane interface between the user plane function and the data network where the application function is located.

[0277] An example embodiment may provide an apparatus, including: means for sending a first message, where the first message includes at least one of the following: a direct subscription request for a user plane function service via a user plane interface, or a request for a direct callback subscription for a user plane function service via a user plane interface, where the direct callback subscription is for initializing a tunnel with an application function; and means for receiving a second message based on sending the first message, where the second message includes information enabling the apparatus to directly subscribe to the user plane function service via the user plane interface.

[0278] An example embodiment may provide a program storage device readable by a device, tangibly embodying an instruction program executable by the device to perform operations, the operations including: sending a first message, where the first message includes at least one of the following: a direct subscription request for a user plane function service via a user plane interface, or a request for a direct callback subscription for a user plane function service via a user plane interface, where the direct callback subscription is for initializing a tunnel with an application function; and receiving a second message based on sending the first message, where the second message includes information enabling the device to directly subscribe to the user plane function service via the user plane interface.

[0279] An example embodiment may provide an apparatus, including: at least one processor; and at least one memory storing instructions that, when executed with the at least one processor, cause the apparatus to perform: receiving, from an application function, a first message, where the first message includes a request for a direct subscription to a user plane function service via a user plane interface; determining whether the user plane function supports a direct subscription to the user plane function service via the user plane interface; and sending, to the application function, a second message regarding whether the user plane function supports a direct subscription to the user plane function service via the user plane interface.

[0280] The apparatus may include a network exposure function, and a first message is received from an application function. The user plane function service may include an event exposure service. A second message may include an authorization token configured to permit direct subscription to the user plane function service by the application function via a user plane interface. The second message may include user plane service information for direct subscription to the user plane function service by the application function via the user plane interface. The first message may include at least one of an Nnef_AFsessionWithQoS_Create request or an Npcf_PolicyAuthorization_Create request. The request may be configured to request the possibility and authorization regarding direct subscription to a protocol data unit session anchor user plane function for user plane related events. The first message may include a QoS monitoring reference to be passed together with at least one QoS flow identifier of a flow to be monitored for quality of service (QoS) with the network exposure function of the apparatus. At least one memory may store instructions that, when executed with at least one processor, cause the apparatus to perform determining a target session management function that supports direct subscription. At least one memory may store instructions that, when executed with at least one processor, cause the apparatus to perform sending a subscription request to the target session management function. The subscription request may be a subscription request for the event exposure service. At least one memory may store instructions that, when executed with at least one processor, cause the apparatus to perform receiving a subscription response from the target session management function, the subscription response having a user plane function identifier of a current protocol data unit session anchor user plane function. The determining may include use of the received subscription response having the user plane function identifier. At least one memory may store instructions that, when executed with at least one processor, cause the apparatus to perform sending a request for a user plane function profile from a network repository function. The request for the user plane function profile may include a request for a user plane function profile of a protocol data unit session anchor user plane function having a specified user plane function identifier. At least one memory may store instructions that, when executed with at least one processor, cause the apparatus to perform receiving a response having the user plane function profile from the network repository function. Determining whether the user plane function supports direct subscription to the user plane function service via the user plane interface may include using the response having the user plane function profile received from the network repository function. At least one memory may store instructions that, when executed with at least one processor, cause the apparatus to perform requesting a token from the network repository function by the network exposure function for direct subscription to the user plane function service. At least one memory may store instructions that, when executed with at least one processor, cause the apparatus to perform receiving the token from the network repository function and sending the token to the application function together with the second message.The at least one memory may store instructions which, when executed with the at least one processor, cause the device to perform sending a request to a user plane function to request user plane function service endpoint information that can be accessed via a user plane interface. The at least one memory may store instructions which, when executed with the at least one processor, cause the device to perform determining whether a target user plane function supports direct subscription to a user plane function service via the user plane interface. The determination may include use of a service name that is used to request user plane function service endpoint information from the user plane function. The at least one memory may store instructions which, when executed with the at least one processor, cause the device to perform receiving endpoint information from the user plane function. The at least one memory may store instructions which, when executed with the at least one processor, cause the device to perform receiving an authorization token configured for use with direct subscription from the user plane function. The at least one memory may store instructions which, when executed with the at least one processor, cause the device to perform sending application function endpoint information and the authorization token to the user plane function, the authorization token being configured to be used by the user plane function to initiate tunnel creation with the application function.

[0281] Reference is also made Figure 8 , an example embodiment may provide a method including: receiving, as shown by block 802, a first message from an application function, where the first message includes a request for direct subscription to a user plane function service via a user plane interface; determining whether the user plane function supports direct subscription to the user plane function service via the user plane interface, as shown by block 804; and sending, as shown by block 806, a second message to the application function regarding whether the user plane function supports direct subscription to the user plane function service via the user plane interface.

[0282] The method may include using a network exposure function, and a first message is received from an application function. The user plane function service may include an event exposure service. The second message may include an authorization token configured to permit direct subscription to the user plane function service by the application function via the user plane interface. The second message may include user plane service information for direct subscription to the user plane function service by the application function via the user plane interface. The first message may include at least one of an Nnef_AFsessionWithQoS_Create request or an Npcf_PolicyAuthorization_Create request. The request may be configured to request the possibility and authorization regarding direct subscription to the protocol data unit session anchor user plane function for user plane related events. The first message may include a QoS monitoring reference to be passed together with at least one QoS flow identifier of a flow to be monitored with quality of service (QoS) by the network exposure function of the device. The method may include determining a target session management function that supports direct subscription. The method may include sending a subscription request to the target session management function. The subscription request may be a subscription request for the event exposure service. The method may include receiving a subscription response from the target session management function, the subscription response having a user plane function identifier of the current protocol data unit session anchor user plane function. The determination may include the use of the received subscription response having the user plane function identifier. The method may include sending a request for a user plane function profile from a network repository function. The request for the user plane function profile may include a request for the user plane function profile of the protocol data unit session anchor user plane function having a specified user plane function identifier. The method may include receiving a response having the user plane function profile from the network repository function. Determining whether the user plane function supports direct subscription to the user plane function service via the user plane interface may include using the response having the user plane function profile received from the network repository function. The method may include the network exposure function requesting a token from the network repository function for direct subscription to the user plane function service. The method may include receiving the token from the network repository function and sending the token to the application function together with the second message. The method may include sending a request to the user plane function to request user plane function service endpoint information that can be accessed via the user plane interface. The method may include determining whether the target user plane function supports direct subscription to the user plane function service via the user plane interface. The determination may include the use of a service name used to request user plane function service endpoint information from the user plane function. The method may include receiving endpoint information from the user plane function. The method may include receiving an authorization token configured to be used with the direct subscription from the user plane function.The method may include sending application function endpoint information and an authorization token to a user plane function, the authorization token being configured to be used by the user plane function to initiate tunnel creation with the application function.

[0283] An example embodiment may provide an apparatus including: means for receiving a first message from an application function, where the first message includes a request for a direct subscription to a user plane function service via a user plane interface; means for determining whether the user plane function supports a direct subscription to the user plane function service via the user plane interface; and means for sending a second message to the application function, the second message regarding the determination of whether the user plane function supports a direct subscription to the user plane function service via the user plane interface.

[0284] An example embodiment may provide a program storage device readable by a device, tangibly embodying an instruction program executable by the device to perform operations including: receiving a first message from an application function, where the first message includes a request for a direct subscription to a user plane function service via a user plane interface; determining whether the user plane function supports a direct subscription to the user plane function service via the user plane interface; and sending a second message to the application function, the second message regarding the determination of whether the user plane function supports a direct subscription to the user plane function service via the user plane interface.

[0285] An example embodiment may provide an apparatus including: at least one processor; and at least one memory storing instructions that, when executed with the at least one processor, cause the apparatus to perform: sending a first message, where the first message includes a subscription request to a session management function regarding a protocol data unit session anchor user plane function; and based on sending the first message, receiving a second message, where the second message includes a response having a user plane function identifier.

[0286] The device may include a network exposure function, and at least one memory stores instructions which, when executed with at least one processor, cause the device to perform determining a session management function as a target session management function. A subscription request may be related to an event exposure service. At least one memory may store instructions which, when executed with at least one processor, cause the device to perform determining whether a target user plane function supports direct subscription to an event exposure service via a user plane interface using the received user plane function identifier. At least one memory may store instructions which, when executed with at least one processor, cause the device to perform sending a request for a user plane function profile from a network repository function, the request including a user plane function identifier. The request for the user plane function profile may include a request for a user plane function profile of a protocol data unit session anchor user plane function having a specified user plane function identifier. At least one memory may store instructions which, when executed with at least one processor, cause the device to perform receiving a response from a network repository function having a user plane function profile. Determining whether a user plane function supports direct subscription to a user plane function service via a user plane interface may include using the response received from a network repository function having a user plane function profile. At least one memory may store instructions which, when executed with at least one processor, cause the device to perform requesting a token regarding subscription from a network repository function by the network exposure function. At least one memory may store instructions which, when executed with at least one processor, cause the device to perform receiving a token from the network repository function and sending the token to an application function. At least one memory may store instructions which, when executed with at least one processor, cause the device to perform sending a request to a user plane function to request user plane function service endpoint information. At least one memory may store instructions which, when executed with at least one processor, cause the device to perform determining whether a target user plane function supports direct subscription to a user plane function service by an application function via a user plane interface. At least one memory may store instructions which, when executed with at least one processor, cause the device to perform requesting user plane function service endpoint information from a user plane function using a service name. At least one memory may store instructions which, when executed with at least one processor, cause the device to perform receiving endpoint information from a user plane function. At least one memory may store instructions which, when executed with at least one processor, cause the device to perform receiving an authorization token from a user plane function, the authorization token being configured to be used with a direct subscription by an application function.At least one memory may store instructions which, when executed with at least one processor, cause the device to perform sending application function endpoint information and an authorization token to a user plane function, the authorization token being configured to be used by the user plane function to initialize tunnel creation with the application function.

[0287] Reference is also made Figure 9 , an example embodiment may provide a method including: sending a first message, as shown by block 902, where the first message includes a subscription request to a session management function regarding a protocol data unit session anchor user plane function; and receiving a second message based on sending the first message, where the second message includes a response with a user plane function identifier, as shown by block 904. The method may include determining the session management function as a target session management function. The subscription request may be related to an event open service. The method may include using the received user plane function identifier to determine whether the target user plane function supports direct subscription to the event open service via a user plane interface. The method may include sending a request for a user plane function profile from a network repository function, the request including the user plane function identifier. The request for the user plane function profile may include a request for a user plane function profile of a protocol data unit session anchor user plane function with a specified user plane function identifier. The method may include receiving a response from the network repository function having the user plane function profile. Determining whether the user plane function supports direct subscription to a user plane function service via a user plane interface may include using the response received from the network repository function having the user plane function profile. The method may include the network exposure function requesting a token regarding the subscription from the network repository function. The method may include receiving the token from the network repository function and sending the token to the application function. The method may include sending a request to the user plane function to request user plane function service endpoint information. The method may include determining whether the target user plane function supports direct subscription to the user plane function service by the application function via a user plane interface. The method may include using the service name to request user plane function service endpoint information from the user plane function. The method may include receiving endpoint information from the user plane function. The method may include receiving an authorization token from the user plane function, the authorization token being configured to be used with the direct subscription by the application function. The method may include sending application function endpoint information and the authorization token to the user plane function, the authorization token being configured to be used by the user plane function to initialize tunnel creation with the application function.

[0288] An example embodiment may provide an apparatus including: components for sending a first message, where the first message includes a subscription request for a session management function regarding a protocol data unit session anchor user plane function; and components for receiving a second message based on sending the first message, where the second message includes a response with a user plane function identifier.

[0289] An example embodiment may provide a program storage device readable by a device, tangibly embodying an instruction program executable by the device to perform operations including: sending a first message, where the first message includes a subscription request for a session management function regarding a protocol data unit session anchor user plane function; and receiving a second message based on sending the first message, where the second message includes a response with a user plane function identifier.

[0290] An example embodiment may provide an apparatus including: at least one processor; and at least one memory storing instructions that, when executed with the at least one processor, cause the apparatus to perform: sending a first message, where the first message includes a request for a network repository function regarding a user plane function profile; and receiving a second message based on sending the first message, where the second message includes a response with a user plane function profile.

[0291] At least one memory may include instructions that, when executed with at least one processor, cause the device to perform at least one of the following: use the received user plane function profile to at least partially determine whether a target user plane function supports direct subscription of an application function to a user plane function service via the user profile, or use the received user plane function profile to at least partially determine whether a target user plane function supports direct callback subscription of an application function via a tunnel to a user plane function service. A request for the user plane function profile may be at least partially based on a user plane function identifier. The user plane function identifier may be related to a protocol data unit session anchor user plane function. At least one memory may store instructions that, when executed with at least one processor, cause the device to perform: send a subscription request regarding the protocol data unit session anchor user plane function to a session management function; and receive a response with a user plane function identifier from the session management function. The subscription request may be related to an event open service. At least one memory may store instructions that, when executed with at least one processor, cause the device to perform using the received user plane function identifier to determine whether the target user plane function supports direct subscription of an event open service via a user plane interface. The device may include a network exposure function, and wherein at least one memory stores instructions that, when executed with at least one processor, cause the device to perform determining a target session management function. At least one memory may store instructions that, when executed with at least one processor, cause the device to perform request, by the network exposure function, a token regarding direct subscription by an application function from a network repository function. At least one memory may store instructions that, when executed with at least one processor, cause the device to perform receive a token from the network repository function and send the token to the application function. At least one memory may store instructions that, when executed with at least one processor, cause the device to perform send a request to a user plane function to request user plane function service endpoint information. At least one memory may store instructions that, when executed with at least one processor, cause the device to perform determine whether the target user plane function supports direct subscription of a user plane function service by an application function via a user plane interface. At least one memory may store instructions that, when executed with at least one processor, cause the device to perform request user plane function service endpoint information from the user plane function using a service name. At least one memory may store instructions that, when executed with at least one processor, cause the device to perform receive endpoint information from the user plane function. At least one memory may store instructions that, when executed with at least one processor, cause the device to perform receive an authorization token from the user plane function, the authorization token being configured to be used with direct subscription by an application function.At least one memory may store instructions that, when executed with at least one processor, cause the device to perform sending application function endpoint information and an authorization token to a user plane function, the authorization token being configured to be used by the user plane function to initialize tunnel creation with the application function.

[0292] Reference is also made Figure 10 , and an example embodiment may provide a method including: sending a first message, as shown by block 1002, where the first message includes a request for a user plane function profile from a network repository function; and receiving a second message based on sending the first message, where the second message includes a response with the user plane function profile, as shown by block 1004. The method may include using the received user plane function profile to at least partially determine whether a target user plane function supports direct subscription of an application function to a user plane function service via the user profile, or using the received user plane function profile to at least partially determine whether the target user plane function supports direct callback subscription of an application function via a tunnel to the user plane function service. The request for the user plane function profile may be at least partially based on a user plane function identifier. The user plane function identifier may be related to a protocol data unit session anchor user plane function. The method may include: sending a subscription request for the protocol data unit session anchor user plane function to a session management function; and receiving a response with the user plane function identifier from the session management function. The subscription request may be related to an event open service. The method may include: using the received user plane function identifier to determine whether the target user plane function supports direct subscription of the event open service via a user plane interface. The method may include determining a target session management function. The method may include a network open function requesting a token for direct subscription by an application function from the network repository function. The method may include receiving the token from the network repository function and sending the token to the application function. The method may include sending a request to the user plane function to request user plane function service endpoint information. The method may include determining whether the target user plane function supports direct subscription of an application function to a user plane function service via a user plane interface. The method may include requesting user plane function service endpoint information from the user plane function using a service name. The method may include receiving endpoint information from the user plane function. The method may include receiving an authorization token from the user plane function, the authorization token being configured to be used with direct subscription by an application function. The method may include sending application function endpoint information and an authorization token to the user plane function, the authorization token being configured to be used by the user plane function to initialize tunnel creation with the application function.

[0293] An example embodiment may provide an apparatus including: means for sending a first message, wherein the first message includes a request for a user plane function profile with respect to a network repository function; and means for receiving a second message based on sending the first message, wherein the second message includes a response with a user plane function profile.

[0294] An example embodiment may provide a program storage device readable by a device, tangibly embodying an instruction program executable by the device to perform operations including: sending a first message, wherein the first message includes a request for a user plane function profile with respect to a network repository function; and receiving a second message based on sending the first message, wherein the second message includes a response with a user plane function profile.

[0295] An example embodiment may provide an apparatus including: at least one processor; and at least one memory storing instructions that, when executed with the at least one processor, cause the apparatus to perform: receiving, from a network exposure function, a first message requesting information on whether the apparatus supports a protocol data unit session anchor; and sending, to the network exposure function, a second message having a response to the first message.

[0296] The apparatus may include a session management function for receiving the first message. The requested information may include a user plane function identifier for a protocol data unit session anchor. The at least one memory may store instructions that, when executed with the at least one processor, cause the apparatus to perform sending another message to the network exposure function when a change occurs in the protocol data unit session anchor user plane function. The first message may include a request for a subscription notification when a change to the protocol data unit session anchor user plane function occurs using the session management function. The at least one memory may store instructions that, when executed with the at least one processor, cause the apparatus to perform receiving, from an application function, a quality of service monitoring reference having a quality of service flow identifier for a quality of service flow passed through the network exposure function.

[0297] Also refer to Figure 11, An example embodiment may provide a method, including: receiving a first message from a network exposure function, requesting information on whether the device supports a protocol data unit session anchor, as shown by block 1102; sending a second message with a response to the first message to the network exposure function, as shown by block 1104. A session management function may receive the first message. The requested information may include a user plane function identifier for the protocol data unit session anchor. The method may include sending another message to the network exposure function when a change occurs in the protocol data unit session anchor user plane function. The first message may include a request for a subscription notification when a change to the protocol data unit session anchor user plane function occurs using the session management function. The method may include receiving, from an application function, a quality of service monitoring reference having a quality of service flow identifier for a quality of service flow that is passed through the network exposure function.

[0298] An example embodiment may provide a device, including: means for receiving a first message from a network exposure function, requesting information on whether the device supports a protocol data unit session anchor; means for sending a second message with a response to the first message to the network exposure function.

[0299] An example embodiment may provide a program storage device readable by a device, tangibly embodying an instruction program executable by the device to perform operations, the operations including: receiving a first message from a network exposure function, requesting information on whether the device supports a protocol data unit session anchor; sending a second message with a response to the first message to the network exposure function.

[0300] An example embodiment may provide a device, including: at least one processor; and at least one memory storing instructions that, when executed with the at least one processor, cause the device to perform: sending a first message to a network repository function, where the first message includes a request for a token for a direct subscription for a user plane function served by an application function; receiving a second message based on sending the first message, where the second message includes a token configured to be used for a direct subscription for a user plane function served by an application function.

[0301] User plane function services may include event exposure services. The device may include a network exposure function that sends the first message. The at least one memory may store instructions that, when executed with the at least one processor, cause the device to send the received token to the application function. Sending the received token may further include sending user plane attribute information to the application function using the token, where the user plane attribute information includes information configured for the application function to form a direct subscription for user plane function services. The device may include a network exposure function that sends the request and receives the token.

[0302] Reference is also made to Figure 12 , an example embodiment may be provided with a method including: sending a first message to a network repository function, as shown by block 1202, where the first message includes a request for a token for direct subscription for an application function to serve a user plane function; receiving a second message based on the sending of the first message, where the second message includes a token configured to be used for direct subscription for an application function to serve a user plane function, as shown by block 1204. The user plane function service may include an event exposure service. The method may include a network exposure function that sends the first message. The method may include sending the received token to the application function. The sending of the received token may further include sending user plane attribute information to the application function using the token, where the user plane attribute information includes information configured for the application function to form a direct subscription to the user plane function service. The method may include a network exposure function that sends the request and receives the token.

[0303] An example embodiment may be provided with an apparatus including: means for sending a first message to a network repository function, where the first message includes a request for a token for direct subscription for an application function to serve a user plane function; means for receiving a second message based on the sending of the first message, where the second message includes a token configured to be used for direct subscription for an application function to serve a user plane function.

[0304] An example embodiment may be provided with a program storage device readable by a device, tangibly embodying an instruction program executable by the device to perform operations including: sending a first message to a network repository function, where the first message includes a request for a token for direct subscription for an application function to serve a user plane function; receiving a second message based on the sending of the first message, where the second message includes a token configured to be used for direct subscription for an application function to serve a user plane function.

[0305] An example embodiment may be provided with an apparatus including: at least one processor; and at least one memory storing instructions that, when executed with the at least one processor, cause the apparatus to perform: receiving a first message from a network exposure function, where the first message includes a request for a token for direct subscription for an application function to serve a user plane function; sending a second message with a response to the request to the network exposure function based on receiving the first message. The user plane function service may include an event exposure service. The apparatus may include a network repository function that receives the first message.

[0306] Reference is also made to Figure 13, an example embodiment may provide a method including: receiving a first message from a network exposure function, as shown by block 1302, where the first message includes a request for a token for direct subscription for an application function to serve a user plane function; and based on receiving the first message, sending a second message with a response to the request to the network exposure function, as shown by block 1304. The user plane function service may include an event exposure service. The network repository function may receive the first information.

[0307] An example embodiment may provide an apparatus including: means for receiving a first message from a network exposure function, where the first message includes a request for a token for direct subscription for an application function to serve a user plane function; and means for sending a second message with a response to the request to the network exposure function based on receiving the first message.

[0308] An example embodiment may provide a program storage device readable by a device, tangibly embodying an instruction program executable by the device to perform operations including: receiving a first message from a network exposure function, where the first message includes a request for a token for direct subscription for an application function to serve a user plane function; and based on receiving the first message, sending a second message with a response to the request to the network exposure function.

[0309] An example embodiment may provide an apparatus including: at least one processor; and at least one memory storing instructions that, when executed in conjunction with the at least one processor, cause the apparatus to perform: receiving a first message from a network exposure function, where the first message includes a request regarding a user plane function service and a user plane endpoint; and based on receiving the first message, sending a second message with a response to the request to the network exposure function. The apparatus may include a user plane function that receives the first message. The first message may include an authorization token for the apparatus to provide the user plane function service. The user plane function service may include an event exposure service. The response may include a user plane endpoint corresponding to the user plane function service. The at least one memory may store instructions that, when executed in conjunction with the at least one processor, cause the apparatus to perform an authentication process configured to authenticate the request.

[0310] Also refer to Figure 14, An example embodiment may provide a method, including: receiving a first message from a network exposure function, as shown by block 1402, wherein the first message includes a request regarding a user plane function service and a user plane endpoint; and based on receiving the first message, sending a second message having a response to the request to the network exposure function, as shown by block 1404. The method may include a user plane function that receives the first message. The first message may include an authorization token for the device to provide the user plane function service. The user plane function service may include an event exposure service. The response may include a user plane endpoint corresponding to the user plane function service. The method may include an authentication process configured to authenticate the request.

[0311] An example embodiment may provide a device, including: means for receiving a first message from a network exposure function, wherein the first message includes a request regarding a user plane function service and a user plane endpoint; and based on receiving the first message, sending a second message having a response to the request to the network exposure function.

[0312] An example embodiment may provide a program storage device readable by a device, tangibly embodying an instruction program executable by the device to perform operations, the operations including: receiving a first message from a network exposure function, wherein the first message includes a request regarding a user plane function service and a user plane endpoint; and based on receiving the first message, sending a second message having a response to the request to the network exposure function.

[0313] An example embodiment may provide a device, including: at least one processor; and at least one memory storing instructions that, when executed with the at least one processor, cause the device to perform: receiving, by a user plane function, a first message from a network exposure function, wherein the first message includes an endpoint for an application function and an authentication token; and establishing a tunnel between the application function and the user plane function using the received endpoint for the application function and the authentication token.

[0314] Also refer to Figure 15 , An example embodiment may provide a method, including: receiving, by a user plane function, a first message from a network exposure function, as shown by block 1502, wherein the first message includes an endpoint for an application function and an authentication token; and establishing a tunnel between the application function and the user plane function using the received endpoint for the application function and the authentication token, as shown by block 1504.

[0315] An example embodiment may provide an apparatus including: components for receiving, by a user plane function, a first message from a network exposure function, where the first message includes an endpoint for an application function and an authentication token; and components for establishing a tunnel between the application function and the user plane function using the received endpoint and authentication token for the application function.

[0316] An example embodiment may provide a program storage device readable by a device, tangibly embodying an instruction program executable by the device to perform operations including: receiving, by a user plane function, a first message from a network exposure function, where the first message includes an endpoint for an application function and an authentication token; and establishing a tunnel between the application function and the user plane function using the received endpoint and authentication token for the application function.

[0317] An example embodiment may provide an apparatus including: at least one processor; and at least one memory storing instructions that, when executed with the at least one processor, cause the apparatus to perform: sending, by a user plane function, a first message to an application function, where the first message includes a dynamic user plane function service endpoint based on a Uniform Resource Locator (URL); receiving, by the user plane function, an authentication token from the application function, where the authentication token is at least partially based on the dynamic user plane function service endpoint based on a Uniform Resource Locator (URL). The at least one memory may store instructions that, when executed with the at least one processor, cause the apparatus to perform an authentication process based on the received authentication token to determine whether to establish an IP tunnel between the application function and the user plane function.

[0318] Also refer to Figure 16 An example embodiment may provide a method including: sending, by a user plane function, a first message to an application function, as shown by block 1602, where the first message includes a dynamic user plane function service endpoint based on a Uniform Resource Locator (URL); receiving, by the user plane function, an authentication token from the application function, where the authentication token is at least partially based on the dynamic user plane function service endpoint based on a Uniform Resource Locator (URL), as shown by block 1604.

[0319] An example embodiment may provide an apparatus including: components for sending, by a user plane function, a first message to an application function, where the first message includes a dynamic user plane function service endpoint based on a Uniform Resource Locator (URL); components for receiving, by the user plane function, an authentication token from the application function, where the authentication token is at least partially based on the dynamic user plane function service endpoint based on a Uniform Resource Locator (URL).

[0320] An example embodiment may provide a program storage device readable by a device, tangibly embodying an instruction program executable by the device to perform operations, the operations including: sending, by a user plane function, a first message to an application function, wherein the first message includes a dynamic user plane function service endpoint based on a Uniform Resource Locator (URL); and receiving, by the user plane function, an authentication token from the application function, wherein the authentication token is at least partially based on the dynamic user plane function service endpoint based on a Uniform Resource Locator (URL).

[0321] An example embodiment may provide a device, including: at least one processor; and at least one memory storing instructions that, when executed with the at least one processor, cause the device to perform: receiving a first message from an application function, wherein the first message includes an authorization token and an indication of a data stream to be monitored using a direct subscription of the user plane function to the application function; and based on receiving the first message, sending a second message from the user plane function to the application function. The response may include information indicating acceptance of the direct subscription by the user plane function. The first message may be received by the user plane function via a user plane interface from the application function. The first message may be received by the user plane function via a tunnel with the application function. The second message may be sent by the user plane function via a tunnel with the application function.

[0322] Also referring to Figure 17 An example embodiment may provide a method, including: receiving a first message from an application function, as shown by block 1702, wherein the first message includes an authorization token and an indication of a data stream to be monitored using a direct subscription of the user plane function to the application function; and based on receiving the first message, sending a second message from the user plane function to the application function, as shown by block 1704. The response may include information indicating acceptance of the direct subscription by the user plane function. The first message may be received by the user plane function via a user plane interface from the application function. The first message may be received by the user plane function via a tunnel with the application function. The second message may be sent by the user plane function via a tunnel with the application function.

[0323] An example embodiment may provide a device, including: means for receiving a first message from an application function, wherein the first message includes an authorization token and an indication of a data stream to be monitored using a direct subscription of the user plane function to the application function; and means for sending a second message from the user plane function to the application function based on receiving the first message.

[0324] An example embodiment may provide a program storage device readable by a device, tangibly embodying an instruction program executable by the device to perform operations including: receiving a first message from an application function, where the first message includes an authorization token and an indication of a data stream to be monitored using a direct subscription of the user plane function by the application function; and based on receiving the first message, sending a second message from the user plane function to the application function.

[0325] An example embodiment may provide a device including: at least one processor; and at least one memory storing instructions that, when executed in conjunction with the at least one processor, cause the device to perform: receiving, by the application function, a first message, where the first message includes a uniform resource locator (URL) for a dynamic user plane function service endpoint; and at least partially based on receiving the first message, sending, by the application function, a second message to the user plane function. The second message may include the URL, and where the URL includes a part of an authentication mechanism for a direct subscription between the application function and the user plane function. The URL may include a protocol data unit session identifier that, when requested by the application function, identifies a protocol data unit session in the user plane function. The at least one memory may store instructions that, when executed in conjunction with the at least one processor, cause the device to perform: receiving, by the application function, attributes of a user plane function service from a network exposure function or a policy control function, the user plane function service being usable via a direct subscription between the application function and the user plane function. The at least one memory may store instructions that, when executed in conjunction with the at least one processor, cause the device to perform: receiving, by the application function, an access token or authorization information from a network exposure function or a policy control function, the access token or authorization information to be used by the application function when subscribing directly to the user plane function service via the user plane.

[0326] Also refer to Figure 18, an example embodiment may provide a method, including: receiving, by an application function, a first message, as shown by block 1802, where the first message includes a uniform resource locator (URL) for a dynamic user plane function service endpoint; and sending, by the application function to the user plane function, a second message at least partially based on receiving the first message, as shown by block 1802. The second message may include the URL, and where the URL includes a part of an authentication mechanism for direct subscription between the application function and the user plane function. The URL may include a protocol data unit session identifier that, when requested by the application function, identifies a protocol data unit session in the user plane function. The method may include: receiving, by the application function, attributes of a user plane function service from a network exposure function or a policy control function, where the user plane function service can be used via direct subscription between the application function and the user plane function. The method may include: receiving, by the application function, an access token or authorization information from a network exposure function or a policy control function, where the access token or authorization information will be used by the application function when directly subscribing to the user plane function service via the user plane.

[0327] An example embodiment may provide an apparatus, including: means for receiving, by an application function, a first message, where the first message includes a uniform resource locator (URL) for a dynamic user plane function service endpoint; and means for sending, by the application function to the user plane function, a second message at least partially based on receiving the first message.

[0328] An example embodiment may provide a program storage device readable by a device, tangibly embodying an instruction program executable by the device to perform operations, the operations including: receiving, by an application function, a first message, where the first message includes a uniform resource locator (URL) for a dynamic user plane function service endpoint; and sending, by the application function to the user plane function, a second message at least partially based on receiving the first message.

[0329] Utilizing the features described herein, the AF may initiate an example method where the UPF acts as a receiver of requests from the AF, and then the UPF may subsequently send a report to the AF based on the initial request from the AF. The UPF may receive a subscription request directly from the AF via the N6 interface. This may be, for example, via a tunnel.

[0330] As used herein, the term "non-transitory" is a limitation of the medium itself (i.e., tangible, rather than a signal), rather than a limitation of data storage persistence (e.g., RAM vs. ROM).

[0331] As used in this application, the term "circuitry" may refer to one or more or all of the following:

[0332] (a) Implementations solely in hardware circuitry (such as, solely in analog and / or digital circuitry) and

[0333] (b) Combinations of hardware circuitry and software, such as (where applicable):

[0334] (i) Combinations of (one or more) analog and / or digital hardware circuitry and software / firmware and

[0335] (ii) Any portion of (one or more) hardware processors (including (one or more) digital signal processors) with software, software, and (one or more) memories, which work together to enable a device (such as a mobile phone or a server) to perform various functions and

[0336] (iii) (One or more) hardware circuitry and / or (one or more) processors, such as (one or more) microprocessors or a portion of (one or more) microprocessors, which require software (e.g., firmware) to operate, but the software may be absent when operation does not require it.”

[0337] This definition of circuitry applies to all uses of the term in this application, including in any claims. As a further example, as used in this application, the term “circuitry” also encompasses implementations of solely hardware circuitry or a processor (or processors) or a portion of hardware circuitry or a processor and its (or their) attendant software and / or firmware. The term “circuitry” also encompasses, for example, if applicable to a particular claim element, a baseband integrated circuit or a processor integrated circuit for a mobile device or a server, a cellular network device, or a similar integrated circuit in other computing or network devices.

[0338] It should be understood that the above description is illustrative only. Various alternatives and modifications can be devised by those skilled in the art. For example, the features described in the respective dependent claims can be combined with each other in any suitable (one or more) combination. Additionally, the features in the above different embodiments can be selectively combined into new embodiments. Accordingly, this description is intended to cover all such alternatives, modifications, and variations that fall within the scope of the appended claims.

[0339] Example 1. A device for communication, comprising:

[0340] At least one processor; and

[0341] At least one memory storing instructions that, when executed with the at least one processor, cause the device to perform:

[0342] Transmit a first message, where the first message includes at least one of the following items:

[0343] A direct subscription request for user plane function services via a user plane interface, or

[0344] A request for a direct callback subscription to the user plane function service via the user plane interface, wherein the direct callback subscription is used to initialize a tunnel to an application function; and

[0345] Based on sending the first message, a second message is received, wherein the second message includes: information enabling the device to directly subscribe to the user plane function service via the user plane interface.

[0346] Example 2. The device according to Example 1, wherein the user plane function service includes an event exposure service.

[0347] Example 3. The device according to any one of Examples 1 to 2, wherein the first message is sent from an application function to a network exposure function, and the second message is received by the application function from the network exposure function.

[0348] Example 4. The device according to any one of Examples 1 to 3, wherein the second message includes an authorization token configured to: permit the device to directly subscribe to the user plane function service via the user plane interface.

[0349] Example 5. The device according to any one of Examples 1 to 4, wherein the second message includes user plane function service information for the device to directly subscribe to the user plane function service via the user plane interface.

[0350] Example 6. The device according to Example 5, wherein the user plane function service information includes at least one of the following items:

[0351] Addressing information enabling access to the user plane service via the user plane interface,

[0352] An HTTP or HTTPS scheme for directly subscribing to the user plane function service,

[0353] The HTTP version supported by the user plane service.

[0354] Example 7. The device according to any one of Examples 1 to 6, wherein the first message includes at least one of the following items: Nnef_AFsessionWithQoS_Create request or Npcf_PolicyAuthorization_Create request.

[0355] Example 8. The apparatus according to any one of Examples 1 to 7, wherein the request is configured to: request the possibility and authorization to directly subscribe to a protocol data unit session anchor user plane function for user plane related events.

[0356] Example 9. The apparatus according to any one of Examples 1 to 8, wherein the at least one memory stores instructions which, when executed in conjunction with the at least one processor, cause the apparatus to perform:

[0357] Use the information received by the application function of the apparatus in the second message to directly subscribe to the user plane function service via a user plane interface and provide a description of at least one data stream to be monitored in the direct subscription to the user plane function.

[0358] Example 10. The apparatus according to any one of Examples 1 to 9, wherein the apparatus sends an HTTP or HTTPS request by using the addressing information of the user plane function service and the HTTP version supported by the user plane function service, and directly subscribes to the user plane function service via the user plane interface by including the received authorization token (if any authorization token is received) in the second message.

[0359] Example 11. The apparatus according to Example 1, wherein the at least one memory stores instructions which, when executed in conjunction with the at least one processor, cause the apparatus to perform:

[0360] Provide a quality of service (QoS) monitoring reference to be passed to a network exposure function together with at least one service quality flow identifier of the QoS flow.

[0361] Example 12. The apparatus according to Example 11, wherein the at least one memory stores instructions which, when executed in conjunction with the at least one processor, cause the apparatus to perform:

[0362] The application function of the apparatus directly subscribes to the user plane function to provide the QoS monitoring reference, and the QoS monitoring reference enables the user plane function to derive the QoS flow or traffic flow subject to the direct subscription.

[0363] Example 13. The apparatus according to any one of Examples 1 to 12, wherein the at least one memory stores instructions which, when executed in conjunction with the at least one processor, cause the apparatus to perform:

[0364] The direct subscription to the user plane function service via the user plane interface via a tunnel by using the request or by using an additional request.

[0365] Example 14. The apparatus according to Example 13, wherein the at least one memory stores instructions that, when executed in conjunction with the at least one processor, cause the apparatus to perform:

[0366] The formation of a tunnel created by the apparatus, initiated by the user plane function.

[0367] Example 15. The apparatus according to Example 13, wherein the at least one memory stores instructions that, when executed in conjunction with the at least one processor, cause the apparatus to perform:

[0368] The formation of the tunnel with the user plane function, initiated by the application function.

[0369] Example 16. The apparatus according to Example 11, wherein the at least one memory stores instructions that, when executed in conjunction with the at least one processor, cause the apparatus to perform:

[0370] Exposing an endpoint reachable via a user plane interface from the user plane function.

[0371] Example 17. The apparatus according to Example 1, wherein the at least one memory stores instructions that, when executed in conjunction with the at least one processor, cause the apparatus to perform:

[0372] Receiving a dynamic user plane function service endpoint at least partially based on a Uniform Resource Locator (URL) including an authentication mechanism, before sending the first message.

[0373] Example 18. The apparatus according to Example 1, wherein the first message includes an application function endpoint and an authorization token.

[0374] Example 19. The apparatus according to any one of Examples 1 to 18, wherein the user plane interface corresponds to the user plane interface between the user plane function and the data network in which the application function is located.

[0375] Example 20. A method for communication, comprising:

[0376] Sending a first message, wherein the first message includes at least one of the following:

[0377] A direct subscription request for user plane function services via a user plane interface, or

[0378] A request for a direct callback subscription for user plane function services via the user plane interface, wherein the direct callback subscription is for initializing a tunnel with an application function; and

[0379] Based on sending the first message, a second message is received, where the second message includes: information enabling the device to directly subscribe to the user plane function service via the user plane interface.

[0380] Example 21. The method according to Example 20, wherein the user plane function service includes an event exposure service.

[0381] Example 22. The method according to any one of Examples 20 to 21, wherein the first message is sent from an application function to a network exposure function, and the second message is received by the application function from the network exposure function.

[0382] Example 23. The method according to any one of Examples 20 to 22, wherein the second message includes an authorization token, and the authorization token is configured to: allow the device to directly subscribe to the user plane function service via the user plane interface.

[0383] Example 24. The method according to any one of Examples 20 to 23, wherein the second message includes user plane function service information for the device to directly subscribe to the user plane function service via the user plane interface.

[0384] Example 25. The method according to Example 24, wherein the user plane function service information includes at least one of the following items:

[0385] Addressing information enabling access to the user plane service via the user plane interface,

[0386] HTTP or HTTPS scheme for directly subscribing to the user plane function service,

[0387] HTTP version supported by the user plane service.

[0388] Example 26. The method according to any one of Examples 20 to 25, wherein the first message includes at least one of the following items: Nnef_AFsessionWithQoS_Create request or Npcf_PolicyAuthorization_Create request.

[0389] Example 27. The method according to any one of Examples 20 to 26, wherein the request is configured to: request the possibility and authorization regarding directly subscribing to the protocol data unit session anchor user plane function for user plane-related events.

[0390] Example 28. The method according to any one of Examples 20 to 27, comprising: directly subscribing to the user plane function service via a user plane interface by using the information received in the second message by an application function of the device, and providing a description of at least one data stream to be monitored in the direct subscription to the user plane function.

[0391] Example 29. The method according to any one of Examples 20 to 28, wherein the device directly subscribes to the user plane function service via the user plane interface by sending an HTTP or HTTPS request by using the addressing information of the user plane function service and the HTTP version supported by the user plane function service, and by including the received authorization token (if any authorization token is received) in the second message.

[0392] Example 30. The method according to Example 20, comprising: providing a quality of service (QoS) monitoring reference to a network exposure function to be delivered together with at least one service quality flow identifier of the QoS flow.

[0393] Example 31. The method according to Example 30, comprising: directly subscribing by an application function of the device to the user plane function to provide the QoS monitoring reference, the QoS monitoring reference enabling the user plane function to derive the QoS flow or traffic flow subject to the direct subscription.

[0394] Example 32. The method according to any one of Examples 20 to 31, comprising: directly subscribing to the user plane function service via the user plane interface via a tunnel by using the request or by using an additional request.

[0395] Example 33. The method according to Example 32, comprising: forming a tunnel with the device initiated by the user plane function.

[0396] Example 34. The method according to Example 32, comprising: forming a tunnel with the user plane function initiated by the application function.

[0397] Example 35. The method according to Example 30, comprising: exposing an endpoint reachable via the user plane interface from the user plane function.

[0398] Example 36. The method according to Example 20, comprising: receiving a dynamic user plane function service endpoint at least partially based on a uniform resource locator (URL) including an authentication mechanism before sending the first message.

[0399] Example 37. The method according to Example 20, wherein the first message includes an application function endpoint and an authorization token.

[0400] Example 38. The method according to any one of Examples 20 to 37, wherein the user plane interface corresponds to the user plane interface between the user plane function and the data network where the application function is located.

[0401] Example 39. A device for communication, comprising:

[0402] a component for sending a first message, wherein the first message includes at least one of the following:

[0403] a direct subscription request for a user plane function service via a user plane interface, or

[0404] a request for a direct callback subscription for the user plane function service via the user plane interface, wherein the direct callback subscription is used to initialize a tunnel with an application function; and

[0405] a component for receiving a second message based on sending the first message, wherein the second message includes: information enabling the device to directly subscribe to the user plane function service via the user plane interface.

[0406] Example 40. A program storage device readable by a device, tangibly embodying an instruction program executable by the device for performing operations, the operations including:

[0407] sending a first message, wherein the first message includes at least one of the following:

[0408] a direct subscription request for a user plane function service via a user plane interface, or

[0409] a request for a direct callback subscription for the user plane function service via the user plane interface, wherein the direct callback subscription is used to initialize a tunnel with an application function; and

[0410] receiving a second message based on sending the first message, wherein the second message includes: information enabling the device to directly subscribe to the user plane function service via the user plane interface.

[0411] Example 41. A device for communication, comprising:

[0412] at least one processor; and

[0413] at least one memory storing instructions that, when executed with the at least one processor, cause the device to perform:

[0414] Receive a first message from an application function, where the first message includes: a request for direct subscription to a user plane function service via a user plane interface;

[0415] Determine whether the user plane function supports the direct subscription to the user plane function service via the user plane interface; and

[0416] Send a second message to the application function, the second message regarding whether the user plane function supports the direct subscription to the user plane function service via the user plane interface.

[0417] Example 42. The apparatus according to example 41, wherein the apparatus includes a network exposure function, and the first message is received from an application function.

[0418] Example 43. The apparatus according to any one of examples 41 to 42, wherein the user plane function service includes an event exposure service.

[0419] Example 44. The apparatus according to any one of examples 41 to 43, wherein the second message includes an authorization token, the authorization token being configured to: allow the direct subscription to the user plane function service by the application function via the user plane interface.

[0420] Example 45. The apparatus according to any one of examples 41 to 44, wherein the second message includes user plane service information, the user plane function service information being used for the direct subscription to the user plane function service by the application function via the user plane interface.

[0421] Example 46. The apparatus according to any one of examples 41 to 45, wherein the first message includes at least one of the following items: an Nnef_AFsessionWithQoS_Create request or an Npcf_PolicyAuthorization_Create request.

[0422] Example 47. The apparatus according to any one of examples 41 to 46, wherein the request is configured to: request the possibility and authorization for directly subscribing to a protocol data unit session anchor user plane function for user plane-related events.

[0423] Example 48. The apparatus according to any one of examples 41 to 47, wherein the first message includes: a QoS monitoring reference to be transmitted together with at least one QoS flow identifier of a flow with quality of service (QoS) to the network exposure function of the apparatus.

[0424] Example 49. The apparatus according to any one of Examples 41 to 48, wherein the at least one memory stores instructions that, when executed with the at least one processor, cause the apparatus to perform:

[0425] Determine a target session management function that supports the direct subscription.

[0426] Example 50. The apparatus according to Example 49, wherein the at least one memory stores instructions that, when executed with the at least one processor, cause the apparatus to perform:

[0427] Send a subscription request to the target session management function.

[0428] Example 51. The apparatus according to Example 50, wherein the subscription request is a subscription request for an event open service.

[0429] Example 52. The apparatus according to any one of Examples 50 to 51, wherein the at least one memory stores instructions that, when executed with the at least one processor, cause the apparatus to perform:

[0430] Receive a subscription response from the target session management function, the subscription response having a user plane function identifier of a current protocol data unit session anchor user plane function.

[0431] Example 53. The apparatus according to Example 52, wherein the determining includes: using the received subscription response having the user plane function identifier.

[0432] Example 54. The apparatus according to any one of Examples 41 to 53, wherein the at least one memory stores instructions that, when executed with the at least one processor, cause the apparatus to perform:

[0433] Send a request for a user plane function profile from a network repository function.

[0434] Example 55. The apparatus according to Example 54, wherein the request for the user plane function profile includes: a request for a user plane function profile of a protocol data unit session anchor user plane function having a specified user plane function identifier.

[0435] Example 56. The apparatus according to any one of Examples 54 to 55, wherein the at least one memory stores instructions that, when executed with the at least one processor, cause the apparatus to perform:

[0436] Receive a response having the user plane function profile from the network repository function.

[0437] Example 57. The apparatus according to Example 56, wherein determining whether the user plane function supports the direct subscription to the user plane function service via the user plane interface includes: using the response with the user plane function profile received from the network repository function.

[0438] Example 58. The apparatus according to any one of Examples 41 to 57, wherein the at least one memory stores instructions that, when executed with the at least one processor, cause the apparatus to perform:

[0439] Requesting, by a network exposure function, a token from a network repository function for the direct subscription to the user plane function service.

[0440] Example 59. The apparatus according to Example 58, wherein the at least one memory stores instructions that, when executed with the at least one processor, cause the apparatus to perform:

[0441] Receiving the token from the network repository function and sending the token and the second message to an application function.

[0442] Example 60. The apparatus according to Example 41, wherein the at least one memory stores instructions that, when executed with the at least one processor, cause the apparatus to perform:

[0443] Sending a request to a user plane function to request user plane function service endpoint information that can be accessed via a user plane interface.

[0444] Example 61. The apparatus according to any one of Examples 41 to 60, wherein the at least one memory stores instructions that, when executed with the at least one processor, cause the apparatus to perform: determining whether a target user plane function supports the direct subscription to the user plane function service via the user plane interface.

[0445] Example 62. The apparatus according to any one of Examples 41 to 61, wherein the determining includes: using a service name that is used to request user plane function service endpoint information from a user plane function.

[0446] Example 63. The apparatus according to any one of Examples 41 to 62, wherein the at least one memory stores instructions that, when executed with the at least one processor, cause the apparatus to perform:

[0447] Receiving endpoint information from a user plane function.

[0448] Example 64. The apparatus according to any one of Examples 41 to 63, wherein the at least one memory stores instructions which, when executed with the at least one processor, cause the apparatus to perform:

[0449] Receiving, from a user plane function, an authorization token configured to be used with the direct subscription.

[0450] Example 65. The apparatus according to any one of Examples 41 to 64, wherein the at least one memory stores instructions which, when executed with the at least one processor, cause the apparatus to perform:

[0451] Sending, to the user plane function, application function endpoint information and an authorization token, the authorization token being configured to be used by the user plane function to initiate tunnel creation with the application function.

[0452] Example 66. A method for communication, comprising:

[0453] Receiving, from an application function, a first message, wherein the first message comprises: a request for a direct subscription to a user plane function service via a user plane interface;

[0454] Determining whether the user plane function supports the direct subscription to the user plane function service via the user plane interface; and

[0455] Sending, to the application function, a second message regarding determining whether the user plane function supports the direct subscription to the user plane function service via the user plane interface.

[0456] Example 67. The method according to Example 66, wherein the method comprises: use of a network exposure function, and the first message is received from the application function.

[0457] Example 68. The apparatus according to any one of Examples 66 to 67, wherein the user plane function service comprises an event exposure service.

[0458] Example 69. The method according to any one of Examples 66 to 68, wherein the second message comprises an authorization token configured to: permit the direct subscription to the user plane function service by the application function via the user plane interface.

[0459] Example 70. The method according to any one of Examples 66 to 69, wherein the second message comprises user plane service information for the direct subscription to the user plane function service by the application function via the user plane interface.

[0460] Example 71. The method according to any one of Examples 66 to 70, wherein the first message includes at least one of the following items: an Nnef_AFsessionWithQoS_Create request or an Npcf_PolicyAuthorization_Create request.

[0461] Example 72. The method according to any one of Examples 66 to 71, wherein the request is configured to: request the possibility and authorization for directly subscribing to a protocol data unit session anchor user plane function for user plane related events.

[0462] Example 73. The method according to any one of Examples 66 to 72, wherein the first message includes: a QoS monitoring reference to be transmitted together with at least one QoS flow identifier of a flow of the network exposure function of the device together with quality of service (QoS).

[0463] Example 74. The method according to any one of Examples 66 to 73, including: determining a target session management function that supports the direct subscription.

[0464] Example 75. The method according to Example 74, including: sending a subscription request to the target session management function.

[0465] Example 76. The method according to Example 75, wherein the subscription request is a subscription request for an event exposure service.

[0466] Example 77. The method according to any one of Examples 75 to 76, including: receiving a subscription response from the target session management function, the subscription response having a user plane function identifier of a current protocol data unit session anchor user plane function.

[0467] Example 78. The method according to Example 77, wherein the determining includes: using the received subscription response having the user plane function identifier.

[0468] Example 79. The method according to any one of Examples 66 to 78, including: sending a request for a user plane function profile from a network repository function.

[0469] Example 80. The method according to Example 79, wherein the request for the user plane function profile includes: a request for a user plane function profile of a protocol data unit session anchor user plane function having a specified user plane function identifier.

[0470] Example 81. The method according to any one of Examples 79 to 80, including: receiving a response having the user plane function profile from the network repository function.

[0471] Example 82. The method according to Example 81, wherein determining whether the user plane function supports direct subscription to the user plane function service via the user plane interface includes: using the response with the user plane function profile received from the network repository function.

[0472] Example 83. The method according to any one of Examples 66 to 82, including: the network exposure function requesting a token from the network repository function for direct subscription to the user plane function service.

[0473] Example 84. The method according to Example 83, including: receiving the token from the network repository function and sending the token and the second message to the application function.

[0474] Example 85. The method according to Example 66, including: sending a request to the user plane function to request user plane function service endpoint information that can be accessed via the user plane interface.

[0475] Example 86. The method according to any one of Examples 66 to 85, including: determining whether a target user plane function supports direct subscription to the user plane function service via the user plane interface.

[0476] Example 87. The method according to any one of Examples 66 to 86, wherein the determining includes: using a service name that is used to request user plane function service endpoint information from the user plane function.

[0477] Example 88. The method according to any one of Examples 66 to 87, including: receiving endpoint information from the user plane function.

[0478] Example 89. The method according to any one of Examples 66 to 88, including: receiving an authorization token configured to be used with the direct subscription from the user plane function.

[0479] Example 90. The method according to any one of Examples 66 to 89, including: sending application function endpoint information and an authorization token to the user plane function, the authorization token being configured to be used by the user plane function to initialize tunnel creation with the application function.

[0480] Example 91. A device for communication, including:

[0481] a component for receiving a first message from an application function, wherein the first message includes: a request for direct subscription to a user plane function service via a user plane interface;

[0482] A component for determining whether a user plane function supports the direct subscription to the user plane function service via the user plane interface; and

[0483] A component for sending a second message to the application function, the second message regarding determining whether the user plane function supports the direct subscription to the user plane function service via the user plane interface.

[0484] Example 92. A program storage device readable by a device, tangibly embodying a program of instructions executable by the device for performing operations, the operations including:

[0485] Receiving a first message from an application function, where the first message includes: a request for a direct subscription to a user plane function service via a user plane interface;

[0486] Determining whether the user plane function supports the direct subscription to the user plane function service via the user plane interface; and

[0487] Sending a second message to the application function, the second message regarding determining whether the user plane function supports the direct subscription to the user plane function service via the user plane interface.

[0488] Example 93. A device for communication, including:

[0489] At least one processor; and

[0490] At least one memory storing instructions that, when executed with the at least one processor, cause the device to perform:

[0491] Sending a first message, where the first message includes: a subscription request to a session management function regarding a protocol data unit session anchor user plane function; and

[0492] Based on sending the first message, receiving a second message, where the second message includes a response with a user plane function identifier.

[0493] Example 94. The device according to Example 93, where the device includes a network exposure function, and where the at least one memory stores instructions that, when executed with the at least one processor, cause the device to perform:

[0494] Determining the session management function as a target session management function.

[0495] Example 95. The device according to any one of Examples 93 to 94, where the subscription request is related to an event exposure service.

[0496] Example 96. The apparatus according to Example 95, wherein the at least one memory stores instructions that, when executed with the at least one processor, cause the apparatus to perform:

[0497] Use the received user plane function identifier to determine whether the target user plane function supports direct subscription to event open services via the user plane interface.

[0498] Example 97. The apparatus according to any one of Examples 93 to 96, wherein the at least one memory stores instructions that, when executed with the at least one processor, cause the apparatus to perform:

[0499] Send a request for a user plane function profile from the network repository function, including the user plane function identifier.

[0500] Example 98. The apparatus according to Example 97, wherein the request for the user plane function profile includes: a request for a user plane function profile of a protocol data unit session anchor user plane function having the specified user plane function identifier.

[0501] Example 99. The apparatus according to any one of Examples 97 to 98, wherein the at least one memory stores instructions that, when executed with the at least one processor, cause the apparatus to perform:

[0502] Receive a response from the network repository function having the user plane function profile.

[0503] Example 100. The apparatus according to Example 99, wherein determining whether the user plane function supports the direct subscription to the user plane function service via the user plane interface includes: using the response received from the network repository function having the user plane function profile.

[0504] Example 101. The apparatus according to any one of Examples 93 to 100, wherein the at least one memory stores instructions that, when executed with the at least one processor, cause the apparatus to perform:

[0505] Request a token regarding the subscription from the network repository function by the network exposure function.

[0506] Example 102. The apparatus according to Example 101, wherein the at least one memory stores instructions that, when executed with the at least one processor, cause the apparatus to perform:

[0507] Receive the token from the network repository function and send the token to the application function.

[0508] Example 103. The apparatus according to Example 93, wherein the at least one memory stores instructions that, when executed with the at least one processor, cause the apparatus to perform:

[0509] Send a request to a user plane function to request user plane function service endpoint information.

[0510] Example 104. The apparatus according to any one of Examples 93 to 103, wherein the at least one memory stores instructions that, when executed with the at least one processor, cause the apparatus to perform:

[0511] Determine whether a target user plane function supports direct subscription to a user plane function service by an application function via a user plane interface.

[0512] Example 105. The apparatus according to any one of Examples 93 to 104, wherein the at least one memory stores instructions that, when executed with the at least one processor, cause the apparatus to perform:

[0513] Use a service name to request user plane function service endpoint information from a user plane function.

[0514] Example 106. The apparatus according to any one of Examples 93 to 105, wherein the at least one memory stores instructions that, when executed with the at least one processor, cause the apparatus to perform:

[0515] Receive endpoint information from a user plane function.

[0516] Example 107. The apparatus according to any one of Examples 93 to 106, wherein the at least one memory stores instructions that, when executed with the at least one processor, cause the apparatus to perform:

[0517] Receive an authorization token from a user plane function, the authorization token being configured to be used with a direct subscription by an application function.

[0518] Example 108. The apparatus according to any one of Examples 93 to 107, wherein the at least one memory stores instructions that, when executed with the at least one processor, cause the apparatus to perform:

[0519] Send application function endpoint information and an authorization token to a user plane function, the authorization token being configured to be used by the user plane function to initialize tunnel creation with the application function.

[0520] Example 109. A method for communication, comprising:

[0521] Send a first message, where the first message includes: a subscription request for a session management function regarding a protocol data unit session anchor user plane function; and

[0522] Based on sending the first message, receive a second message, where the second message includes a response with a user plane function identifier.

[0523] Example 110. The method according to Example 109 includes: determining the session management function as a target session management function.

[0524] Example 111. The method according to any one of Examples 109 to 110, where the subscription request is related to an event open service.

[0525] Example 112. The method according to Example 111 includes: using the received user plane function identifier to determine whether the target user plane function supports direct subscription to the event open service via a user plane interface.

[0526] Example 113. The method according to any one of Examples 109 to 112 includes: sending a request for a user plane function profile from a network repository function, including the user plane function identifier.

[0527] Example 114. The method according to Example 113, where the request for the user plane function profile includes: a request for a user plane function profile of a protocol data unit session anchor user plane function with the specified user plane function identifier.

[0528] Example 115. The method according to any one of Examples 113 to 114 includes: receiving a response from the network repository function with the user plane function profile.

[0529] Example 116. The method according to Example 115, where the determining whether the user plane function supports the direct subscription to the user plane function service via the user plane interface includes:

[0530] Using the received response from the network repository function with the user plane function profile.

[0531] Example 117. The method according to any one of Examples 109 to 116 includes: requesting a token regarding the subscription from a network repository function by a network exposure function.

[0532] Example 118. The method according to Example 117 includes: receiving the token from the network repository function and sending the token to an application function.

[0533] Example 119. The method according to Example 109 includes: sending a request to a user plane function to request user plane function service endpoint information.

[0534] Example 120. The method according to any one of Examples 109 to 119 includes: determining whether a target user plane function supports direct subscription to user plane function services by an application function via a user plane interface.

[0535] Example 121. The method according to any one of Examples 109 to 120 includes: using a service name to request user plane function service endpoint information from a user plane function.

[0536] Example 122. The method according to any one of Examples 109 to 121 includes: receiving endpoint information from a user plane function.

[0537] Example 123. The method according to any one of Examples 109 to 122 includes: receiving an authorization token from a user plane function, the authorization token being configured to be used in conjunction with direct subscription by an application function.

[0538] Example 124. The method according to any one of Examples 109 to 123 includes: sending application function endpoint information and an authorization token to a user plane function, the authorization token being configured to be used by the user plane function to initialize tunnel creation with the application function.

[0539] Example 125. A device for communication includes:

[0540] Components for sending a first message, where the first message includes: a subscription request to a session management function regarding a protocol data unit session anchor user plane function; and

[0541] Components for receiving a second message based on sending the first message, where the second message includes a response with a user plane function identifier.

[0542] Example 126. A program storage device readable by a device tangibly embodying an instruction program executable by the device for performing operations, the operations including:

[0543] Sending a first message, where the first message includes: a subscription request to a session management function regarding a protocol data unit session anchor user plane function; and

[0544] Receiving a second message based on sending the first message, where the second message includes a response with a user plane function identifier.

[0545] Example 127. A device for communication, comprising:

[0546] At least one processor; and

[0547] At least one memory storing instructions that, when executed with the at least one processor, cause the device to perform:

[0548] Send a first message, where the first message includes: a request for a user plane function profile regarding a network repository function; and

[0549] Based on sending the first message, receive a second message, where the second message includes a response with the user plane function profile.

[0550] Example 128. The device according to Example 127, wherein the at least one memory stores instructions that, when executed with the at least one processor, cause the device to perform at least one of the following:

[0551] Use the received user plane function profile to at least partially determine whether a target user plane function supports direct subscription of an application function to a user plane function service via a user profile, or

[0552] Use the received user plane function profile to at least partially determine whether a target user plane function supports direct callback subscription of an application function via a tunnel to a user plane function service.

[0553] Example 129. The device according to any one of Examples 127 to 128, wherein the request regarding the user plane function profile is at least partially based on a user plane function identifier.

[0554] Example 130. The device according to Example 129, wherein the user plane function identifier is related to a protocol data unit session anchor user plane function.

[0555] Example 131. The device according to any one of Examples 129 to 130, wherein the at least one memory stores instructions that, when executed with the at least one processor, cause the device to perform:

[0556] Send a subscription request regarding a protocol data unit session anchor user plane function to a session management function; and

[0557] Receive a response with the user plane function identifier from the session management function.

[0558] Example 132. The device according to Example 131, wherein the subscription request is related to an event open service.

[0559] Example 133. The apparatus according to Example 132, wherein the at least one memory stores instructions that, when executed with the at least one processor, cause the apparatus to perform:

[0560] Using the received user plane function identifier to determine whether the target user plane function supports direct subscription to the event open service via the user plane interface.

[0561] Example 134. The apparatus according to any one of Examples 127 to 133, wherein the apparatus includes a network exposure function, and wherein the at least one memory stores instructions that, when executed with the at least one processor, cause the apparatus to perform:

[0562] Determine a target session management function.

[0563] Example 135. The apparatus according to any one of Examples 127 to 134, wherein the at least one memory stores instructions that, when executed with the at least one processor, cause the apparatus to perform:

[0564] The network exposure function requests a token for direct subscription by the application function from the network repository function.

[0565] Example 136. The apparatus according to Example 135, wherein the at least one memory stores instructions that, when executed with the at least one processor, cause the apparatus to perform:

[0566] Receive the token from the network repository function and send the token to the application function.

[0567] Example 137. The apparatus according to Example 127, wherein the at least one memory stores instructions that, when executed with the at least one processor, cause the apparatus to perform:

[0568] Send a request to the user plane function to request user plane function service endpoint information.

[0569] Example 138. The apparatus according to any one of Examples 127 to 137, wherein the at least one memory stores instructions that, when executed with the at least one processor, cause the apparatus to perform:

[0570] Determine whether the target user plane function supports direct subscription to the user plane function service by the application function via the user plane interface.

[0571] Example 139. The apparatus according to any one of Examples 127 to 138, wherein the at least one memory stores instructions that, when executed with the at least one processor, cause the apparatus to perform:

[0572] Use a service name to request user plane function service endpoint information from a user plane function.

[0573] Example 140. The apparatus according to any one of Examples 127 to 139, wherein the at least one memory stores instructions that, when executed with the at least one processor, cause the apparatus to perform:

[0574] Receive endpoint information from a user plane function.

[0575] Example 141. The apparatus according to any one of Examples 127 to 140, wherein the at least one memory stores instructions that, when executed with the at least one processor, cause the apparatus to perform:

[0576] Receive an authorization token from a user plane function, the authorization token being configured to be used with a direct subscription of an application function.

[0577] Example 142. The apparatus according to any one of Examples 127 to 141, wherein the at least one memory stores instructions that, when executed with the at least one processor, cause the apparatus to perform:

[0578] Send application function endpoint information and an authorization token to a user plane function, the authorization token being configured to be used by the user plane function to initialize tunnel creation with the application function.

[0579] Example 143. A method for communication, comprising:

[0580] Send a first message, wherein the first message comprises: a request for a user plane function profile from a network repository function; and

[0581] Receive a second message based on sending the first message, wherein the second message comprises a response having the user plane function profile.

[0582] Example 144. The method according to Example 143, comprising:

[0583] Use the received user plane function profile to at least partially determine whether a target user plane function supports direct subscription of an application function to a user plane function service via a user profile, or

[0584] Use the received user plane function profile to at least partially determine whether a target user plane function supports direct callback subscription of an application function via a tunnel serving the user plane function.

[0585] Example 145. The method according to any one of Examples 143 to 144, wherein the request regarding the user plane function profile is at least partially based on a user plane function identifier.

[0586] Example 146. The method according to any one of Example 145, wherein the user plane function identifier is related to a protocol data unit session anchor user plane function.

[0587] Example 147. The method according to any one of Examples 145 to 146, comprising:

[0588] Sending a subscription request regarding the protocol data unit session anchor user plane function to a session management function; and

[0589] Receiving, from the session management function, a response having the user plane function identifier.

[0590] Example 148. The method according to any one of Example 147, wherein the subscription request is related to an event open service.

[0591] Example 149. The method according to Example 148, comprising: using the received user plane function identifier to determine whether the target user plane function supports direct subscription to the event open service via a user plane interface.

[0592] Example 150. The method according to any one of Examples 143 to 149, comprising a network exposure function, and comprising: determining a target session management function.

[0593] Example 151. The method according to any one of Examples 143 to 150, comprising: the network exposure function requesting a token regarding direct subscription by an application function from a network repository function.

[0594] Example 152. The method according to Example 151, comprising: receiving the token from the network repository function and sending the token to the application function.

[0595] Example 153. The method according to Example 143, comprising: sending a request to a user plane function to request user plane function service endpoint information.

[0596] Example 154. The method according to any one of Examples 143 to 153, comprising: determining whether the target user plane function supports direct subscription to a user plane function service by an application function via a user plane interface.

[0597] Example 155. The method according to any one of Examples 143 to 154, comprising: using a service name to request user plane function service endpoint information from a user plane function.

[0598] Example 156. The method according to any one of Examples 143 to 155, comprising: receiving endpoint information from a user plane function.

[0599] Example 157. The method according to any one of Examples 143 to 156, comprising receiving an authorization token from a user plane function, the authorization token being configured to be used with a direct subscription of an application function.

[0600] Example 158. The method according to any one of Examples 143 to 157, comprising sending application function endpoint information and an authorization token to a user plane function, the authorization token being configured to be used by the user plane function to initiate tunnel creation with the application function.

[0601] Example 159. An apparatus for communication, comprising:

[0602] means for sending a first message, wherein the first message comprises: a request for a user plane function profile from a network repository function; and

[0603] means for receiving a second message based on sending the first message, wherein the second message comprises a response having the user plane function profile.

[0604] Example 160. A program storage device readable by an apparatus, tangibly embodying a program of instructions executable by the apparatus for performing operations, the operations comprising:

[0605] sending a first message, wherein the first message comprises: a request for a user plane function profile from a network repository function; and

[0606] receiving a second message based on sending the first message, wherein the second message comprises a response having the user plane function profile.

[0607] Example 161. An apparatus for communication, comprising:

[0608] at least one processor; and

[0609] at least one memory storing instructions which, when executed in conjunction with the at least one processor, cause the apparatus to perform:

[0610] Receive a first message from a network exposure function, the first message requesting information on whether the device supports a protocol data unit session anchor;

[0611] Send a second message to the network exposure function having a response to the first message.

[0612] Example 162. The device according to example 161, wherein the device comprises: a session management function that receives the first message.

[0613] Example 163. The device according to example 161, wherein the requested information comprises: a user plane function identifier for the protocol data unit session anchor.

[0614] Example 164. The device according to any one of examples 161 to 163, wherein the at least one memory stores instructions that, when executed in conjunction with the at least one processor, cause the device to perform:

[0615] When a change occurs in a protocol data unit session anchor user plane function, send another message to the network exposure function.

[0616] Example 165. The device according to any one of examples 161 to 164, wherein the first message comprises: a request for a subscription notification when a change to a protocol data unit session anchor user plane function occurs using a session management function.

[0617] Example 166. The device according to any one of examples 161 to 165, wherein the at least one memory stores instructions that, when executed in conjunction with the at least one processor, cause the device to perform:

[0618] Receive, from an application function, a quality of service monitoring reference that is passed through a network exposure function and has a quality of service flow identifier for a quality of service flow.

[0619] Example 167. A method for communication, comprising:

[0620] Receive a first message from a network exposure function, the first message requesting information on whether the device supports a protocol data unit session anchor;

[0621] Send a second message to the network exposure function having a response to the first message.

[0622] Example 168. The method according to example 167, wherein a session management function receives the first message.

[0623] Example 169. The method according to Example 167, wherein the requested information includes: a user plane function identifier for the protocol data unit session anchor.

[0624] Example 170. The method according to any one of Examples 167 to 169, including: when a change occurs in the protocol data unit session anchor user plane function, sending another message to the network exposure function.

[0625] Example 171. The method according to any one of Examples 167 to 170, wherein the first message includes: a request for a subscription notification when a change to the protocol data unit session anchor user plane function occurs using a session management function.

[0626] Example 172. The method according to any one of Examples 167 to 171, including: receiving, from an application function, a quality of service monitoring reference that is passed through the network exposure function and has a quality of service flow identifier for a quality of service flow.

[0627] Example 173. An apparatus for communication, comprising:

[0628] means for receiving a first message from a network exposure function, the first message requesting information on whether the apparatus supports a protocol data unit session anchor;

[0629] means for sending a second message to the network exposure function having a response to the first message.

[0630] Example 174. A program storage device readable by an apparatus, tangibly embodying an instruction program executable by the apparatus for performing operations, the operations including:

[0631] receiving a first message from a network exposure function, the first message requesting information on whether the apparatus supports a protocol data unit session anchor;

[0632] sending a second message to the network exposure function having a response to the first message.

[0633] Example 175. An apparatus for communication, comprising:

[0634] at least one processor; and

[0635] at least one memory storing instructions that, when executed with the at least one processor, cause the apparatus to perform:

[0636] sending a first message to a network repository function, wherein the first message includes: a request for a token for a direct subscription to a user plane function served by an application function; and

[0637] Based on sending the first message, receiving a second message, where the second message includes: a token configured to be used for the direct subscription by the application function to the user plane function service.

[0638] Example 176. The apparatus according to example 175, wherein the user plane function service includes: an event open service.

[0639] Example 177. The apparatus according to any one of examples 175 to 176, wherein the apparatus includes: a network exposure function that sends the first message.

[0640] Example 178. The apparatus according to any one of examples 175 to 177, wherein the at least one memory stores instructions that, when executed with the at least one processor, cause the apparatus to perform:

[0641] Send the received token to the application function.

[0642] Example 179. The apparatus according to example 178, wherein sending the received token further includes: sending user plane attribute information and the token to the application function, where the user plane attribute information includes: information configured for the application function to form the direct subscription to the user plane function service.

[0643] Example 180. The apparatus according to any one of examples 175 to 179, wherein the apparatus includes: a network exposure function that sends the request and receives the token.

[0644] Example 181. A method for communication, including:

[0645] Sending a first message to a network repository function, where the first message includes: a request for a token for a direct subscription by an application function to a user plane function service;

[0646] Based on sending the first message, receiving a second message, where the second message includes: a token configured to be used for the direct subscription by the application function to the user plane function service.

[0647] Example 182. The method according to example 181, wherein the user plane function service includes: an event open service.

[0648] Example 183. The method according to any one of examples 181 to 182, including: a network exposure function that sends the first message.

[0649] Example 184. The method according to any one of Examples 181 to 183, comprising: sending the received token to the application function.

[0650] Example 185. The method according to Example 184, wherein sending the received token further comprises: sending user plane attribute information and the token to the application function, wherein the user plane attribute information comprises: information configured for the application function to form the direct subscription to the user plane function service.

[0651] Example 186. The method according to any one of Examples 181 to 185, comprising: a network exposure function that sends the request and receives the token.

[0652] Example 187. A device for communication, comprising:

[0653] a component for sending a first message to a network repository function, wherein the first message comprises: a request for a token for a direct subscription by an application function to a user plane function service; and

[0654] a component for receiving a second message based on sending the first message, wherein the second message comprises: the token configured to be used for the direct subscription by the application function to the user plane function service.

[0655] Example 188. A program storage device readable by a device, tangibly embodying an instruction program executable by the device for performing operations, the operations comprising:

[0656] sending a first message to a network repository function, wherein the first message comprises: a request for a token for a direct subscription by an application function to a user plane function service; and

[0657] receiving a second message based on sending the first message, wherein the second message comprises: the token configured to be used for the direct subscription by the application function to the user plane function service.

[0658] Example 189. A device for communication, comprising:

[0659] at least one processor; and

[0660] at least one memory storing instructions that, when executed with the at least one processor, cause the device to perform:

[0661] receiving a first message from a network exposure function, wherein the first message comprises: a request for a token for a direct subscription by an application function to a user plane function service; and

[0662] Based on receiving the first message, send a second message with a response to the request to the network exposure function.

[0663] Example 190. The apparatus according to Example 189, wherein the user plane function service includes: an event exposure service.

[0664] Example 191. The apparatus according to any one of Examples 189 to 190, wherein the apparatus includes: a network repository function that receives the first message.

[0665] Example 192. A method for communication, comprising:

[0666] Receiving a first message from a network exposure function, wherein the first message includes: a request for a token for direct subscription of a user plane function service by an application function;

[0667] Based on receiving the first message, send a second message with a response to the request to the network exposure function.

[0668] Example 193. The method according to Example 192, wherein the user plane function service includes: an event exposure service.

[0669] Example 194. The method according to any one of Examples 192 to 193, wherein a network repository function receives the first message.

[0670] Example 195. A device for communication, comprising:

[0671] A component for receiving a first message from a network exposure function, wherein the first message includes: a request for a token for direct subscription of a user plane function service by an application function;

[0672] A component for sending a second message with a response to the request to the network exposure function based on receiving the first message.

[0673] Example 196. A program storage device readable by a device, tangibly embodying an instruction program executable by the device for performing operations, the operations including:

[0674] Receiving a first message from a network exposure function, wherein the first message includes: a request for a token for direct subscription of a user plane function service by an application function; and

[0675] Based on receiving the first message, send a second message with a response to the request to the network exposure function.

[0676] Example 197. A device for communication, comprising:

[0677] At least one processor; and

[0678] At least one memory storing instructions which, when executed with the at least one processor, cause the device to perform:

[0679] Receiving a first message from a network exposure function, wherein the first message includes: a request regarding a user plane function service and a user plane endpoint; and

[0680] Based on receiving the first message, sending a second message to the network exposure function having a response to the request.

[0681] Example 198. The device according to example 197, wherein the device includes: a user plane function for receiving the first message.

[0682] Example 199. The device according to any one of examples 197 to 198, wherein the first message includes: an authorization token for the device to provide the user plane function service.

[0683] Example 200. The device according to any one of examples 197 to 199, wherein the user plane function service includes: an event exposure service.

[0684] Example 201. The device according to any one of examples 197 to 200, wherein the response includes: the user plane endpoint corresponding to the user plane function service.

[0685] Example 202. The device according to any one of examples 197 to 201, wherein the at least one memory stores instructions which, when executed with the at least one processor, cause the device to perform:

[0686] An authentication process configured to authenticate the request.

[0687] Example 203. A method for communication, comprising:

[0688] Receiving a first message from a network exposure function, wherein the first message includes: a request regarding a user plane function service and a user plane endpoint; and

[0689] Based on receiving the first message, sending a second message to the network exposure function having a response to the request.

[0690] Example 204. The method according to example 203, comprising: a user plane function for receiving the first message.

[0691] Example 205. The method according to any one of Examples 203 to 204, wherein the first message includes: an authorization token for the apparatus to provide the user plane function service.

[0692] Example 206. The method according to any one of Examples 203 to 205, wherein the user plane function service includes: an event open service.

[0693] Example 207. The method according to any one of Examples 203 to 206, wherein the response includes: the user plane endpoint corresponding to the user plane function service.

[0694] Example 208. The method according to any one of Examples 203 to 207, including: an authentication process configured to authenticate the request.

[0695] Example 209. An apparatus for communication, including:

[0696] a component for receiving a first message from a network exposure function, wherein the first message includes: a request regarding a user plane function service and a user plane endpoint; and

[0697] based on receiving the first message, sending a second message with a response to the request to the network exposure function.

[0698] Example 210. A program storage device readable by an apparatus, tangibly embodying an instruction program executable by the apparatus for performing operations, the operations including:

[0699] receiving a first message from a network exposure function, wherein the first message includes: a request regarding a user plane function service and a user plane endpoint; and

[0700] based on receiving the first message, sending a second message with a response to the request to the network exposure function.

[0701] Example 211. An apparatus for communication, including:

[0702] at least one processor; and

[0703] at least one memory storing instructions that, when executed with the at least one processor, cause the apparatus to perform:

[0704] receiving, by a user plane function, a first message from a network exposure function, wherein the first message includes: an endpoint for an application function and an authentication token; and

[0705] Establish a tunnel between the application function and the user plane function using the received endpoint for the application function and the authentication token.

[0706] Example 212. A method for communication, comprising:

[0707] Receiving, by a user plane function, a first message from a network exposure function, wherein the first message includes: an endpoint for an application function and an authentication token; and

[0708] Establishing a tunnel between the application function and the user plane function using the received endpoint for the application function and the authentication token.

[0709] Example 213. An apparatus for communication, comprising:

[0710] Means for receiving, by a user plane function, a first message from a network exposure function, wherein the first message includes: an endpoint for an application function and an authentication token; and

[0711] Means for establishing a tunnel between the application function and the user plane function using the received endpoint for the application function and the authentication token.

[0712] Example 214. A program storage device readable by a device, tangibly embodying an instruction program executable by the device for performing operations, the operations including:

[0713] Receiving, by a user plane function, a first message from a network exposure function, wherein the first message includes: an endpoint for an application function and an authentication token; and

[0714] Establishing a tunnel between the application function and the user plane function using the received endpoint for the application function and the authentication token.

[0715] Example 215. An apparatus for communication, comprising:

[0716] At least one processor; and

[0717] At least one memory storing instructions which, when executed in conjunction with the at least one processor, cause the apparatus to perform:

[0718] Sending, by a user plane function, a first message to an application function, wherein the first message includes: a dynamic user plane function service endpoint based on a Uniform Resource Locator (URL);

[0719] Receive, by the user plane function, an authentication token from the application function, where the authentication token is at least partially based on the dynamic user plane function service endpoint, and the dynamic user plane function service endpoint is based on a Uniform Resource Locator (URL).

[0720] Example 216. The apparatus according to Example 215, wherein the at least one memory stores instructions that, when executed with the at least one processor, cause the apparatus to perform:

[0721] Based on the received authentication token, perform an authentication process to determine whether to establish an IP tunnel between the application function and the user plane function.

[0722] Example 217. A method for communication, comprising:

[0723] Send, by a user plane function, a first message to an application function, where the first message includes: a dynamic user plane function service endpoint based on a Uniform Resource Locator (URL);

[0724] Receive, by the user plane function, an authentication token from the application function, where the authentication token is at least partially based on the dynamic user plane function service endpoint, and the dynamic user plane function service endpoint is based on a Uniform Resource Locator (URL).

[0725] Example 218. An apparatus for communication, comprising:

[0726] Components for sending, by a user plane function, a first message to an application function, where the first message includes: a dynamic user plane function service endpoint based on a Uniform Resource Locator (URL);

[0727] Components for receiving, by the user plane function, an authentication token from the application function, where the authentication token is at least partially based on the dynamic user plane function service endpoint, and the dynamic user plane function service endpoint is based on a Uniform Resource Locator (URL).

[0728] Example 219. A program storage device readable by a device, tangibly embodying an instruction program executable by the device for performing operations, the operations including:

[0729] Send, by a user plane function, a first message to an application function, where the first message includes a dynamic user plane function service endpoint based on a Uniform Resource Locator (URL);

[0730] Receive an authentication token from the application function by the user plane function, where the authentication token is at least partially based on the dynamic user plane function service endpoint, and the dynamic user plane function service endpoint is based on a Uniform Resource Locator (URL).

[0731] Example 220. A device for communication, comprising:

[0732] At least one processor; and

[0733] At least one memory storing instructions which, when executed with the at least one processor, cause the device to perform:

[0734] Receive a first message from an application function, where the first message includes: an authorization token, and an indication of a data stream to be monitored using a direct subscription of the user plane function to the application function; and

[0735] Based on receiving the first message, send a second message from the user plane function to the application function.

[0736] Example 221. The device according to Example 220, where the response includes: information indicating acceptance of the direct subscription by the user plane function.

[0737] Example 222. The device according to any one of Examples 220 to 221, where the first message is received by the user plane function from the application function via the user plane interface.

[0738] Example 223. The device according to any one of Examples 220 to 222, where the first message is received by the user plane function via a tunnel with the application function.

[0739] Example 224. The device according to any one of Examples 220 to 223, where the second message is sent by the user plane function via a tunnel with the application function.

[0740] Example 225. A method for communication, comprising:

[0741] Receive a first message from an application function, where the first message includes: an authorization token, and an indication of a data stream to be monitored using a direct subscription of the user plane function to the application function; and

[0742] Based on receiving the first message, send a second message from the user plane function to the application function.

[0743] Example 226. The method according to Example 225, where the response includes: information indicating acceptance of the direct subscription by the user plane function.

[0744] Example 227. The method according to any one of Examples 225 to 226, wherein the first message is received by the user plane function from the application function via the user plane interface.

[0745] Example 228. The method according to any one of Examples 225 to 227, wherein the first message is received by the user plane function via a tunnel with the application function.

[0746] Example 229. The method according to any one of Examples 225 to 228, wherein the second message is sent by the user plane function via a tunnel with the application function.

[0747] Example 230. An apparatus for communication, comprising:

[0748] means for receiving a first message from an application function, wherein the first message includes: an authorization token, and an indication of a data stream to be monitored using a direct subscription of the application function to the user plane function; and

[0749] means for sending a second message from the user plane function to the application function based on receiving the first message.

[0750] Example 231. A program storage device readable by a device, tangibly embodying a program of instructions executable by the device for performing operations, the operations including:

[0751] Receiving a first message from an application function, wherein the first message includes: an authorization token, and an indication of a data stream to be monitored using a direct subscription of the application function to the user plane function; and

[0752] Based on receiving the first message, sending a second message from the user plane function to the application function.

[0753] Example 232. An apparatus for communication, comprising:

[0754] At least one processor; and

[0755] At least one memory storing instructions which, when executed with the at least one processor, cause the apparatus to perform:

[0756] Receiving a first message from an application function, wherein the first message includes: a uniform resource locator (URL) for a dynamic user plane function service endpoint; and

[0757] Sending, by the application function, a second message to the user plane function at least in part based on receiving the first message.

[0758] Example 233. The apparatus according to Example 232, wherein the second message includes the URL, and wherein the URL includes: a part of an authentication mechanism for direct subscription between the application function and the user plane function.

[0759] Example 234. The apparatus according to any one of Examples 232 to 233, wherein the URL includes a protocol data unit session identifier that, when requested by the application function, identifies a protocol data unit session in the user plane function.

[0760] Example 235. The apparatus according to any one of Examples 232 to 234, wherein the at least one memory stores instructions that, when executed in conjunction with the at least one processor, cause the apparatus to perform:

[0761] Receiving, by the application function, attributes of a user plane function service from a network exposure function or a policy control function, the user plane function service being usable via a direct subscription between the application function and the user plane function.

[0762] Example 236. The apparatus according to any one of Examples 232 to 235, wherein the at least one memory stores instructions that, when executed in conjunction with the at least one processor, cause the apparatus to perform:

[0763] Receiving, by the application function, an access token or authorization information from a network exposure function or a policy control function, the access token or authorization information to be used by the application function when directly subscribing to the user plane function service via the user plane.

[0764] Example 237. A method for communication, comprising:

[0765] Receiving, by an application function, a first message, wherein the first message includes: a uniform resource locator (URL) for a dynamic user plane function service endpoint; and

[0766] Sending, by the application function, a second message to the user plane function at least in part based on receiving the first message.

[0767] Example 238. The method according to Example 237, wherein the second message includes: the URL, and wherein the URL includes: a part of an authentication mechanism for direct subscription between the application function and the user plane function.

[0768] Example 239. In the manner according to any one of Examples 237 to 238, wherein the URL includes a protocol data unit session identifier that, when requested by the application function, identifies a protocol data unit session in the user plane function.

[0769] Example 240. The method according to any one of Examples 237 to 239, comprising:

[0770] receiving, by the application function, attributes of a user plane function service from a network exposure function or a policy control function, the user plane function service being usable via a direct subscription between the application function and the user plane function.

[0771] Example 241. The method according to any one of Examples 237 to 240, comprising:

[0772] receiving, by the application function, an access token or authorization information from a network exposure function or a policy control function, the access token or authorization information being used by the application function when directly subscribing to the user plane function service via the user plane.

[0773] Example 242. An apparatus for communication, comprising:

[0774] means for receiving, by an application function, a first message, wherein the first message includes: a uniform resource locator (URL) for a dynamic user plane function service endpoint; and

[0775] means for sending, by the application function, a second message to a user plane function at least in part based on receiving the first message.

[0776] Example 243. A program storage device readable by a device, tangibly embodying an instruction program executable by the device for performing operations, the operations including:

[0777] receiving, by an application function, a first message, wherein the first message includes: a uniform resource locator (URL) for a dynamic user plane function service endpoint; and

[0778] sending, by the application function, a second message to a user plane function at least in part based on receiving the first message.

Claims

1. A device for communication, comprising: At least one processor; And At least one memory storing instructions which, when executed with the at least one processor, cause the device to perform: Send a first message, wherein the first message comprises at least one of the following: A direct subscription request for a user plane function service via a user plane interface, or A request for a direct callback subscription for the user plane function service via the user plane interface, wherein the direct callback subscription is for initializing a tunnel with an application function; And Based on sending the first message, receive a second message, wherein the second message comprises: information enabling the device to directly subscribe to the user plane function service via the user plane interface.

2. A device for communication, comprising: At least one processor; And At least one memory storing instructions which, when executed with the at least one processor, cause the device to perform: Receive a first message from an application function, wherein the first message comprises: a request for a direct subscription to a user plane function service via a user plane interface; Determine whether the user plane function supports the direct subscription to the user plane function service via the user plane interface; and Send a second message to the application function, the second message regarding the determination of whether the user plane function supports the direct subscription to the user plane function service via the user plane interface.

3. A device for communication, comprising: At least one processor; And At least one memory storing instructions which, when executed with the at least one processor, cause the device to perform: Send a first message, wherein the first message comprises: a subscription request for a session management function regarding a protocol data unit session anchor user plane function; And Based on sending the first message, receive a second message, wherein the second message comprises a response with a user plane function identifier.

4. A device for communication, comprising: At least one processor; And At least one memory storing instructions which, when executed with the at least one processor, cause the device to perform: Send a first message, wherein the first message comprises: a request for a user plane function profile from a network repository function; And Based on sending the first message, receive a second message, wherein the second message comprises a response with the user plane function profile.

5. A device for communication, comprising: At least one processor; And At least one memory storing instructions which, when executed with the at least one processor, cause the device to perform: Receive a first message from a network exposure function, the first message requesting information on whether the device supports a protocol data unit session anchor; Send a second message to the network exposure function with a response to the first message.

6. A device for communication, comprising: At least one processor; And at least one memory storing instructions which, when executed with the at least one processor, cause the device to perform: send a first message to a network repository function, wherein the first message includes: a request for a token for direct subscription for an application function to serve a user plane function; and receive a second message based on sending the first message, wherein the second message includes: the token configured to be used for the direct subscription for the application function to serve the user plane function.

7. A device for communication, comprising: at least one processor; and at least one memory storing instructions which, when executed with the at least one processor, cause the device to perform: receive a first message from a network exposure function, wherein the first message includes: a request for a token for direct subscription for an application function to serve a user plane function; and send a second message with a response to the request to the network exposure function based on receiving the first message.

8. A device for communication, comprising: at least one processor; and at least one memory storing instructions which, when executed with the at least one processor, cause the device to perform: receive a first message from a network exposure function, wherein the first message includes: a request regarding a user plane function service and a user plane endpoint; and send a second message with a response to the request to the network exposure function based on receiving the first message.

9. A device for communication, comprising: at least one processor; and at least one memory storing instructions which, when executed with at least one processor, cause the device to perform: receive a first message from an application function, wherein the first message includes: an authorization token, and an indication of a data stream to be monitored using the direct subscription of the application function to a user plane function; and send a second message from the user plane function to the application function based on receiving the first message.

10. A device for communication, comprising: at least one processor; and at least one memory storing instructions which, when executed with the at least one processor, cause the device to perform: receive a first message by an application function, wherein the first message includes: a uniform resource locator (URL) for a dynamic user plane function service endpoint; and send a second message from the application function to a user plane function at least partly based on receiving the first message.

Images