WO2023055370A1

WO2023055370A1 - Multiple application functions influencing a protocol data unit session

Info

Publication number: WO2023055370A1
Application number: PCT/US2021/052814
Authority: WO
Inventors: Devaki Chandramouli; Colin Kahn
Original assignee: Nokia Technologies Oy; Nokia Of America Corporation
Priority date: 2021-09-30
Filing date: 2021-09-30
Publication date: 2023-04-06

Abstract

Systems, methods, apparatuses, and computer program products for coordinating and/or controlling multiple application functions (AFs) are provided. One method may include obtaining a sharing policy configured to define preferences for handling application function (AF) requests, receiving, from an application function (AF), a sharing option request that explicitly indicates a sharing option desired by the application function (AF), and determining whether the sharing option request by the application function (AF) is authorized for a user equipment (UE) and protocol data unit (PDU) session.

Description

MULTIPLE APPLICATION FUNCTIONS INFLUENCING A PROTOCOL DATA UNIT SESSION

FIELD:

[0001] Some example embodiments may generally relate to communications including mobile or wireless telecommunication systems, such as Long Term Evolution (LTE) or fifth generation (5G) radio access technology or new radio (NR) access technology, or other communications systems. For example, certain example embodiments may generally relate to systems and/or methods for coordinating between multiple application functions (AFs).

BACKGROUND:

[0002] Examples of mobile or wireless telecommunication systems may include the Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN), Long Term Evolution (LTE) Evolved UTRAN (E-UTRAN), LTE-Advanced (LTE-A), MulteFire, LTE- A Pro, and/or fifth generation (5G) radio access technology or new radio (NR) access technology. 5G wireless systems refer to the next generation (NG) of radio systems and network architecture. A 5G system is mostly built on a 5G new radio (NR), but a 5G (or NG) network can also build on the E-UTRA radio. It is estimated that NR provides bitrates on the order of 10-20 Gbit/s or higher, and can support at least service categories such as enhanced mobile broadband (eMBB) and ultra-reliable low-latency-communication (URLLC) as well as massive machine type communication (mMTC). NR is expected to deliver extreme broadband and ultra-robust, low latency connectivity and massive networking to support the Internet of Things (loT). With loT and machine-to-machine (M2M) communication becoming more widespread, there will be a growing need for networks that meet the needs of lower power, low data rate, and long battery life. The next generation radio access network (NG-RAN) represents the RAN for 5G, which can provide both NR and LTE (and LTE-Advanced) radio accesses. It is noted that, in 5G, the nodes that can provide radio access functionality to a user equipment (i.e., similar to the Node B, NB, in UTRAN or the evolved NB, eNB, in LTE) may be named next-generation NB (gNB) when built on NR radio and may be named next-generation eNB (NG-eNB) when built on E-UTRA radio.

SUMMARY:

[0003] An embodiment may be directed to an apparatus, which may include at least one processor and at least one memory comprising computer program code. The at least one memory and computer program code may be configured, with the at least one processor, to cause the apparatus at least to perform: obtaining a sharing policy configured to define preferences for handling application function (AF) requests, receiving, from an application function (AF), a sharing option request that explicitly indicates a sharing option desired by the application function (AF), and determining whether the sharing option request by the application function (AF) is authorized for a user equipment (UE) and protocol data unit (PDU) session.

[0004] An embodiment may be directed to an apparatus, which may include at least one processor and at least one memory comprising computer program code. The at least one memory and computer program code may be configured, with the at least one processor, to cause the apparatus at least to perform: transmitting a sharing option request to a network node, wherein the sharing option request indicates a sharing option desired by the apparatus, receiving, from the network node, an indication of an authorization for the sharing option, and performing procedures according to the authorized sharing option.

[0005] An embodiment may be directed to an apparatus, which may include at least one processor and at least one memory comprising computer program code. The at least one memory and computer program code may be configured, with the at least one processor, to cause the apparatus at least to perform: receiving configuration of policies comprising assistance information that specifies one or more of a sharing policy, currently active sharing options, or a sharing state for a protocol data unit (PDU) session, and setting up the protocol data unit (PDU) session using the assistance information. [0006] An embodiment may be directed to a method including obtaining a sharing policy configured to define preferences for handling application function (AF) requests, receiving, from an application function (AF), a sharing option request that explicitly indicates a sharing option desired by the application function (AF), and determining whether the sharing option request by the application function (AF) is authorized for a user equipment (UE) and protocol data unit (PDU) session.

[0007] An embodiment may be directed to a method including transmitting a sharing option request to a network node, wherein the sharing option request indicates a sharing option desired by the apparatus, receiving, from the network node, an indication of an authorization for the sharing option, and performing procedures according to the authorized sharing option.

[0008] An embodiment may be directed to a method including receiving configuration of policies comprising assistance information that specifies one or more of a sharing policy, currently active sharing options, or a sharing state for a protocol data unit (PDU) session, and setting up the protocol data unit (PDU) session using the assistance information.

[0009] An embodiment may be directed to an apparatus including means for obtaining a sharing policy configured to define preferences for handling application function (AF) requests, means for receiving, from an application function (AF), a sharing option request that explicitly indicates a sharing option desired by the application function (AF), and means for determining whether the sharing option request by the application function (AF) is authorized for a user equipment (UE) and protocol data unit (PDU) session.

[0010] In one variant, the apparatus may include means for establishing a sharing state by processing the sharing option request and prior sharing option requests, and in consideration of the sharing policy. In another variant, the apparatus may include means for updating or establishing the sharing state based on the sharing option(s) in an authorized application function (AF) sharing option request on a per user equipment (UE) or per protocol data unit (PDU) session basis. In a further variant, the apparatus may include means for authorizing a new application function (AF) request according to at least one of the sharing option request, the sharing policy, or the sharing state that results from a prior application function (AF) sharing option request for a same user equipment (UE) and protocol data unit (PDU) session. In another variant, the apparatus may include means for provisioning or updating user equipment policies containing sharing assistance information in the user equipment (UE), where the sharing assistance information specifies one or more of a sharing policy, currently active sharing options, or a sharing state for a protocol data unit (PDU) session.

[0011] An embodiment may be directed to an apparatus including means for transmitting a sharing option request to a network node, wherein the sharing option request indicates a sharing option desired by the apparatus, means for receiving, from the network node, an indication of an authorization for the sharing option, and means for performing procedures according to the authorized sharing option.

[0012] An embodiment may be directed to an apparatus including means for receiving configuration of policies comprising assistance information that specifies one or more of a sharing policy, currently active sharing options, or a sharing state for a protocol data unit (PDU) session, and means for setting up the protocol data unit (PDU) session using the assistance information.

BRIEF DESCRIPTION OF THE DRAWINGS:

[0013] For proper understanding of example embodiments, reference should be made to the accompanying drawings, wherein:

[0014] Fig. 1 illustrates an example system diagram;

[0015] Fig. 2 illustrates an example system diagram, according to one example embodiment;

[0016] Fig. 3 illustrates an example signaling diagram, according to an example embodiment;

[0017] Fig. 4A illustrates an example flow diagram of a method, according to an embodiment;

[0018] Fig. 4B illustrates an example flow diagram of a method, according to an embodiment;

[0019] Fig. 4C illustrates an example flow diagram of a method, according to an embodiment;

[0020] Fig. 5A illustrates an example block diagram of an apparatus, according to an embodiment;

[0021] Fig. 5B illustrates an example block diagram of an apparatus, according to an embodiment; and

[0022] Fig. 5C illustrates an example block diagram of an apparatus, according to an embodiment.

DETAIEED DESCRIPTION:

[0023] It will be readily understood that the components of certain example embodiments, as generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of some example embodiments of systems, methods, apparatuses, and computer program products for coordinating and/or controlling multiple application functions (AFs), is not intended to limit the scope of certain embodiments but is representative of selected example embodiments.

[0024] The features, structures, or characteristics of example embodiments described throughout this specification may be combined in any suitable manner in one or more example embodiments. For example, the usage of the phrases “certain embodiments,” “some embodiments,” or other similar language, throughout this specification refers to the fact that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment. Thus, appearances of the phrases “in certain embodiments,” “in some embodiments,” “in other embodiments,” or other similar language, throughout this specification do not necessarily all refer to the same group of embodiments, and the described features, structures, or characteristics may be combined in any suitable manner in one or more example embodiments.

[0025] Additionally, if desired, the different functions or procedures discussed below may be performed in a different order and/or concurrently with each other. Furthermore, if desired, one or more of the described functions or procedures may be optional or may be combined. As such, the following description should be considered as illustrative of the principles and teachings of certain example embodiments, and not in limitation thereof.

[0026] Certain example embodiments discussed herein may generally relate to 5G System (5GS) architecture, including the exposure framework of the 5GS. The role of the application function (AF) has grown considerably in 5G. For example, application functions (AFs) can request quality of service (QoS), influence traffic routing, request the sending of an application trigger to the UE, request location, request time synchronization, receive event reports, set a chargeable party, provide guidance for UE route selection polices, provision service parameters, request network status, request background data transfer, among other functions (e.g., see 3GPP technical specifications 23.501 and 23.502).

[0027] Currently, there is almost no coordination between AFs that may want to take advantage of the exposed functionality for a single PDU session. It is noted that a PDU session provides end- to-end user plane connectivity between the UE and a specific data network (DN) through the user plane function (UPF). A PDU session can support one or more QoS flows.

[0028] It would be desirable to be able to coordinate and control multiple AFs that may wish to influence or obtain services for a given PDU session so the AFs do not act in an uncoordinated manner. Fig. 1 illustrates an example system depicting the current situation in which there is no way to control or coordinate how multiple AFs interact with the 5GS. In this situation, conflicts are possible when multiple AFs affect the same PDU session without knowledge of each other. For example, one scenario or use case may include where AF1 might need just positioning and/or time synchronization information regarding a given UE, and AF2 might need to influence QoS/traffic routing for a given UE. In another example scenario, there might be many devices behind a single UE (acting as a (residential) gateway) and, in this case, each device might require different services or the same service (e.g., QoS) applied to different traffic but there is only one PDU session between the UE and the network. In yet another possible scenario, two AFs may request the same functionality for the same traffic flow where the request causes a conflict (e.g., request for QoS or a request to influence traffic routing). In this case, there is currently no mechanism to resolve the conflict. In a further scenario, two AFs may request the same functionality for the same traffic where the request does not cause a conflict, e.g., a request for event notification for the same event which may be associated with the same traffic flow. In this case, there is no mechanism to authorize the “allowed” requests from the two AFs.

[0029] Fig. 2 illustrates an example system diagram, according to one example embodiment. In particular, the example system of Fig. 2 can provide the ability to coordinate the AFs that influence any functionality for a given UE and a given PDU session. According to an example embodiment, a policy control function (PCF) 205 may obtain or receive, for example via provisioning or configuration, an operator sharing policy. In certain other embodiments, the control function 205 may be a different network function or a new network function. In certain example embodiments, the sharing policy may specify one or more of: (1) a default sharing option that may be applicable when the AF does not specify a sharing option in a request, (2) allowed sharing options, (3) orthogonal functionality lists or lists of functions that are not orthogonal, and/or (4) a non-conflicting functionality list. For example, the non-conflicting functionality list may indicate at least one functionality for which more than one AF can provide a request for the same traffic flow (alternatively or additionally, this could be a “conflicting” services list).

[0030] According to an example embodiment, an AF, such as untrusted AF-1 or untrusted AF-2 depicted in the example of Fig. 2, can request a sharing option. In one example embodiment, the request for a sharing option may include the ability for the AF to explicitly indicate that it needs exclusive access for a given UE and given PDU session. Additionally or alternatively, in a further example embodiment, the request for a sharing option may include the ability for the AF to explicitly indicate that it allows another AF to influence the PDU Session or same traffic flow (identified by traffic filter) for orthogonal functionality (e.g., AF-1 for time sync, AF-2 for QoS, traffic influencing, etc.). Additionally or alternatively, in a further example embodiment, the request for a sharing option may include the ability for the AF to explicitly indicate that it allows another AF to influence the PDU session for different traffic flows (identified by traffic filter). Additionally or alternatively, in a further example embodiment, the request for a sharing option may include the ability for the AF to explicitly indicate that it allows another AF to influence the PDU session for the same traffic and the same functionality (applicable for “non-conflicting” functionality such as event or location reporting). It is noted that an AF may simultaneously specify any combination of the above-noted sharing option requests in which case a logical “or” of the options applies. In an embodiment, for a PDU session, the 5GS may further establish a “sharing state” that results from processing all of the AF sharing option requests and consideration of the sharing policy.

[0031] In an example embodiment, the UE 210 may be configured with policies, such as UE route selection policies (URSP), that may include assistance information that specifies one or more of the sharing policy, the currently active sharing option(s) specified by an AF, and/or the sharing state for a PDU session. According to an embodiment, the UE may use this sharing assistance information to guide PDU session setup. For example, if the assistance information indicates a sharing policy or an AF requested sharing option is “exclusive access” for a PDU session, the UE may decide to setup separate PDU sessions for traffic flows associated with different applications.

[0032] Fig. 3 illustrates an example signaling diagram, according to certain embodiments. As illustrated in the example of Fig. 3, at 0, policies may be provisioned to define operator preferences for the handling of AF requests that contain “sharing options” and/or to establish default handling when an AF request does not include a sharing option. In an embodiment, the policies may also specify allowed sharing options and rules that define the same, and/or orthogonal functionality that can be used by multiple AFs simultaneously.

[0033] As further illustrated in the example of Fig. 3, at 1, the network exposure function (NEF) may expose an application programming interface (API) that enables the AF to explicitly indicate sharing option(s). For example, the sharing options as discussed above may include one or more of exclusive access, simultaneous influence on different services allowed, and/or simultaneous influence on different traffic allowed. As illustrated at 2, the NEF or PCF can authorize a new AF request according to at least one of: the AF request, operator “sharing policy”, and/or the “sharing state” that results from a prior AF request for the same UE / PDU Session. As illustrated at 3, the PCF may determine that the sharing option requested by the AF is authorized for the UE / PDU session. As illustrated at 4, the PCF may update or establish the “sharing state” based on the “sharing option(s)” in the authorized AF request (on a per UE or per PDU session basis). It is noted that, if a “sharing state” already exists due to a prior AF request, the updated “sharing state” may indicate what is allowed by the sharing options of both AFs. As illustrated at 5, URSP policies containing sharing assistance information may be provisioned and/or updated in the UE. As illustrated at 6, the AF may request that specific procedures are performed, such as QoS, event notification, traffic routing, etc.

[0034] Fig. 4A illustrates an example flow diagram of a method for coordinating between multiple AFs that may want to influence or obtain services for a given PDU session, according to one embodiment. In certain example embodiments, the flow diagram of Fig. 4A may be performed by a network entity or network node in a communications system, such as LTE or 5G NR. In some example embodiments, the network entity performing the method of Fig. 4A may include or be included in a 5G core (5GC) network node, or 5GC network functions, or the like. For example, according to certain embodiments, the entity performing the method of Fig. 4A may include a PCF or NEF, such as those illustrated in the examples of Figs. 1-3, or another entity or new network function. In some embodiments, the method of Fig. 4A may illustrate example operations of a PCF or NEF corresponding to apparatus 10 as illustrated in, and described with respect to, Fig. 5 A discussed below.

[0035] As illustrated in the example of Fig. 4A, the method may include, at 405, obtaining or receiving, e.g., via provisioning or configuration, a sharing policy that is configured to define preferences for handling AF requests. According to some embodiments, the sharing policy may specify or indicate one or more of: a default sharing option that is applicable when the application function (AF) does not specify a sharing option in a request, allowed sharing options, orthogonal functionality lists and/or lists of functionality that are not orthogonal, and/or a non-conflicting functionality list. In certain embodiments, the orthogonal functionality list may include two or more functionalities that can be (i.e., allowed to be) performed simultaneously, and the non-conflicting functionality list may include functionality that can be performed multiple times for different consumers (e.g., AF1, AF2, etc.). As one example, for an AF1 requesting location information and AF2 requesting QoS, the location request and QoS request may be considered orthogonal functionalities because they do not interfere with each other. In addition, the location request may be considered non-conflicting because it can be requested by more than one AF (e.g., AF1, AF2, AF3, etc.). While, for example, QoS for a traffic flow may be considered conflicting because two AFs cannot request different QoS for the same traffic flow.

[0036] As also illustrated in the example of Fig. 4A, the method may include, at 410, receiving, from an AF, a sharing option request that explicitly indicates a sharing option desired by the AF. For example, in some embodiments, the sharing option indicated in the request may include one or more of: an indication that the AF needs exclusive access for a the UE and PDU session, an indication that the AF allows another AF to influence the PDU session or same traffic flow for orthogonal functionality, an indication that the AF allows another AF to influence the PDU session for different traffic flows, and/or an indication that the AF allows another AF to influence the PDU session for the same traffic flow and same functionality.

[0037] As further illustrated in the example of Fig. 4A, the method may include, at 415, authorizing a new AF request according to at least one of the sharing option request, the sharing policy, or the sharing state that results from a prior AF sharing option request for the same UE and PDU session. In an embodiment, the method may also include, at 420, determining whether the sharing option request by the AF is authorized for a UE and PDU session and authorizing the sharing option request based on the determination. It should be noted that, in some embodiments, the order of procedure 415 and 520 may be switched, that is authorization of a new AF request according to at least one of the sharing option request, the sharing policy, or the sharing state that results from a prior AF sharing option request for the same UE and PDU session at 415 may occur after the authorization for a UE and PDU session shown at 420. [0038] In some embodiments, the method may include establishing a sharing state by processing the sharing option request from the AF and one or more prior sharing option requests from other AFs, and in consideration of the sharing policy. Additionally, in certain embodiments, the method may include updating or establishing the sharing state based on the sharing option(s) in an authorized AF sharing option request on a per UE or per PDU session basis. According to an embodiment, the method may include provisioning or updating policies containing sharing assistance information in the UE. For instance, the policies containing the sharing assistance information may include user equipment route selection policies (USRP). According to an embodiment, the sharing assistance information may specify one or more of a sharing policy, currently active sharing options, or a sharing state for a PDU session, for example. In some embodiments, the method may include performing AF request specific procedures, such as QoS, event notification, traffic routing, etc.

[0039] Fig. 4B illustrates an example flow diagram of a method for coordinating between multiple AFs that may want to influence or obtain services for a given PDU session, according to one embodiment. In certain example embodiments, the flow diagram of Fig. 4B may be performed by a network entity or network node in a communications system, such as LTE or 5G NR. In some example embodiments, the network entity performing the method of Fig. 4B may include or be included in a base station, access node, node B, eNB, gNB, gNB-DU, gNB-CU, NG-RAN node, transmission-reception points (TRPs), high altitude platform stations (HAPS), relay station, or 5GC network entities or functions or the like. For example, according to certain embodiments, the entity performing the method of Fig. 4B may include an AF, such as those illustrated in the examples of Figs. 1-3, or any other entity discussed herein. In some embodiments, the method of Fig. 4B may illustrate example operations of an AF corresponding to apparatus 20 as illustrated in, and described with respect to, Fig. 5B discussed below.

[0040] As illustrated in the example of Fig. 4B, the method may include, at 440, transmitting or otherwise providing a sharing option request to a network node, such as a PCF or NEF. In an embodiment, the sharing option request explicitly indicates a sharing option desired or needed by the AF. For example, the sharing option may include one or more of: an indication that the AF requires exclusive access for a respective UE and PDU session, an indication that the AF allows another AF to influence the PDU session or same traffic flow for orthogonal functionality, an indication that the AF allows another AF to influence the PDU session for different traffic flows, and/or an indication that the AF allows another AF to influence the PDU session for the same traffic flow and same functionality.

[0041] In certain embodiments, the method of Fig. 4B may also include, at 445, receiving, from the network node, an indication of the authorization for the sharing option requested by the AF. The method may then include, at 450, performing AF procedures according to the authorized sharing option. For instance, the AF procedures may include procedures relating to QoS, event notification, traffic routing, etc. [0042] Fig. 4C illustrates an example flow diagram of a method of coordinating between multiple AFs that may want to influence or obtain services for a given PDU session, according to an example embodiment. In certain example embodiments, the flow diagram of Fig. 4C may be performed by a communication device in a communications system, such as LTE or 5G NR. For instance, in some example embodiments, the communication device performing the method of Fig. 4C may include a UE, sidelink (SL) UE, wireless device, mobile station, loT device, UE type of roadside unit (RSU), other mobile or stationary device, or the like. For example, according to certain embodiments, the entity performing the method of Fig. 4C may include a UE, such as those illustrated in the examples of Figs. 1-3, or any other entity discussed herein. In some embodiments, the method of Fig. 4C may illustrate example operations of a UE corresponding to apparatus 30 as illustrated in, and described with respect to, Fig. 5C discussed below.

[0043] As illustrated in the example of Fig. 4C, the method may include, at 460, receiving configuration of policies including assistance information that may specify one or more of a sharing policy, currently active sharing options, and/or a sharing state for a PDU session. For example, the policies for which the configuration is received may include URSP. In certain embodiments, the sharing policy may be configured to define preferences for handling AF requests. According to some embodiments, the sharing policy may define or specify one or more of: a default sharing option that is applicable when the AF does not specify a sharing option in a request, allowed sharing options, orthogonal functionality lists and/or non-orthogonal functionality lists, and/or a conflicting functionality list and/or non-conflicting functionality list. In an embodiment, the method may then include, at 465, setting up the protocol data unit (PDU) session using the assistance information. As one example, if the assistance information indicates a sharing policy or an AF requested sharing option is “exclusive access” for a PDU session, the UE may decide to setup separate PDU sessions for traffic flows associated with different applications.

[0044] Fig. 5 A illustrates an example of an apparatus 10 according to an embodiment. In an embodiment, apparatus 10 may be a node, host, or server in a communications network or serving such a network. For example, apparatus 10 may be or may be included in a satellite, base station, a Node B, an evolved Node B (eNB), 5G Node B or access point, next generation Node B (NG-NB or gNB), transmission receive point (TRP), high altitude platform station (HAPS), integrated access and backhaul (IAB) node, and/or WLAN access point, associated with a radio access network, such as a LTE network, 5G or NR. According to further example embodiments, apparatus 10 may be a 5GC network node or 5GC network function. In one example embodiment, apparatus 10 may represent a PCF and/or NEF, such as those illustrated in Figs. 1-3.

[0045] It should be understood that, in some example embodiments, apparatus 10 may be comprised of an edge cloud server as a distributed computing system where the server and the radio node may be stand-alone apparatuses communicating with each other via a radio path or via a wired connection, or where they may be located in a same entity communicating via a wired connection. For instance, in certain example embodiments where apparatus 10 represents a gNB, it may be configured in a central unit (CU) and distributed unit (DU) architecture that divides the gNB functionality. In such an architecture, the CU may be a logical node that includes gNB functions such as transfer of user data, mobility control, radio access network sharing, positioning, and/or session management, etc. The CU may control the operation of DU(s) over a front-haul interface. The DU may be a logical node that includes a subset of the gNB functions, depending on the functional split option. It should be noted that one of ordinary skill in the art would understand that apparatus 10 may include components or features not shown in Fig. 5 A.

[0046] As illustrated in the example of Fig. 5 A, apparatus 10 may include a processor 12 for processing information and executing instructions or operations. Processor 12 may be any type of general or specific purpose processor. In fact, processor 12 may include one or more of general- purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), and processors based on a multi-core processor architecture, or any other processing means, as examples. [0047] While a single processor 12 is shown in Fig. 5 A, multiple processors may be utilized according to other example embodiments. For example, it should be understood that, in certain embodiments, apparatus 10 may include two or more processors that may form a multiprocessor system (e.g., in this case processor 12 may represent a multiprocessor) that may support multiprocessing. In some embodiments, the multiprocessor system may be tightly coupled or loosely coupled (e.g., to form a computer cluster).

[0048] Processor 12 may perform functions associated with the operation of apparatus 10, which may include, for example, precoding of antenna gain/phase parameters, encoding and decoding of individual bits forming a communication message, formatting of information, and overall control of the apparatus 10, including processes related to management of communication resources.

[0049] Apparatus 10 may further include or be coupled to a memory 14 (internal or external), which may be coupled to processor 12, for storing information and instructions that may be executed by processor 12. Memory 14 may be one or more memories and of any type suitable to the local application environment, and may be implemented using any suitable volatile or nonvolatile data storage technology such as a semiconductor-based memory device, a magnetic memory device and system, an optical memory device and system, fixed memory, and/or removable memory. For example, memory 14 can be comprised of any combination of random access memory (RAM), read only memory (ROM), static storage such as a magnetic or optical disk, hard disk drive (HDD), or any other type of non-transitory machine or computer readable media, or other appropriate storing means. The instructions stored in memory 14 may include program instructions or computer program code that, when executed by processor 12, enable the apparatus 10 to perform tasks as described herein. [0050] In an embodiment, apparatus 10 may further include or be coupled to (internal or external) a drive or port that is configured to accept and read an external computer readable storage medium, such as an optical disc, USB drive, flash drive, or any other storage medium. For example, the external computer readable storage medium may store a computer program or software for execution by processor 12 and/or apparatus 10.

[0051] In some embodiments, apparatus 10 may also include or be coupled to one or more antennas 15 for transmitting and receiving signals and/or data to and from apparatus 10. Apparatus 10 may further include or be coupled to a transceiver 18 configured to transmit and/or receive information. The transceiver 18 may include, for example, a plurality of radio interfaces that may be coupled to the antenna(s) 15, or may include any other appropriate transceiving means. In certain embodiments, the radio interfaces may correspond to a plurality of radio access technologies including one or more of GSM, NB-IoT, LTE, 5G, WLAN, Bluetooth, BT-LE, NFC, radio frequency identifier (RFID), ultrawideband (UWB), MulteFire, and/or the like. According to an example embodiment, the radio interface may include components, such as filters, converters (e.g., digital- to-analog converters and the like), mappers, a Fast Fourier Transform (FFT) module, and/or the like, e.g., to generate symbols or signals for transmission via one or more downlinks and to receive symbols (e.g., via an uplink).

[0052] As such, transceiver 18 may be configured to modulate information on to a carrier waveform for transmission by the antenna(s) 15 and to demodulate information received via the antenna(s) 15 for further processing by other elements of apparatus 10. In other example embodiments, transceiver 18 may be capable of transmitting and receiving signals or data directly. Additionally or alternatively, in some embodiments, apparatus 10 may include an input device and/or output device (I/O device), or an input/output means.

[0053] In an embodiment, memory 14 may store software modules that provide functionality when executed by processor 12. The modules may include, for example, an operating system that provides operating system functionality for apparatus 10. The memory may also store one or more functional modules, such as an application or program, to provide additional functionality for apparatus 10. The components of apparatus 10 may be implemented in hardware, or as any suitable combination of hardware and software.

[0054] According to some embodiments, processor 12 and memory 14 may be included in or may form a part of processing circuitry or control circuitry. In addition, in some embodiments, transceiver 18 may be included in or may form a part of transceiver circuitry.

[0055] As used herein, the term “circuitry” may refer to hardware-only circuitry implementations (e.g., analog and/or digital circuitry), combinations of hardware circuits and software, combinations of analog and/or digital hardware circuits with software/firmware, any portions of hardware processor(s) with software (including digital signal processors) that work together to cause an apparatus (e.g., apparatus 10) to perform various functions, and/or hardware circuit(s) and/or processor(s), or portions thereof, that use software for operation but where the software may not be present when it is not needed for operation. As a further example, as used herein, the term “circuitry” may also cover an implementation of merely a hardware circuit or processor (or multiple processors), or portion of a hardware circuit or processor, and its accompanying software and/or firmware. The term circuitry may also cover, for example, a baseband integrated circuit in a server, cellular network node or device, or other computing or network device.

[0056] As introduced above, in certain embodiments, apparatus 10 may be a network node or RAN node, such as a base station, access point, Node B, eNB, gNB, TRP, HAPS, IAB node, WLAN access point, 5GC network node, or 5GC network function, or the like. In some example embodiments, apparatus 10 may be or may be included in a PCF and/or NEF. For example, in some embodiments, apparatus 10 may be configured to perform one or more of the processes depicted in any of the flow charts or signaling diagrams described herein, such as those illustrated in any of Figs. 1-4. In some embodiments, as discussed herein, apparatus 10 may be configured to perform a procedure relating to coordinating between multiple AFs that may want to influence or obtain services for a given PDU session, for example.

[0057] Fig. 5B illustrates an example of an apparatus 20 according to another embodiment. In an embodiment, apparatus 20 may be a node or element in a communications network or associated with such a network, such as a satellite, base station, a Node B, an evolved Node B (eNB), 5G Node B or access point, next generation Node B (NG-NB or gNB), transmission receive point (TRP), high altitude platform station (HAPS), integrated access and backhaul (IAB) node, and/or WLAN access point, associated with a radio access network, such as a LTE network, 5G or NR. According to further example embodiments, apparatus 20 may be a 5GC network node, or 5GC network function. In one example embodiment, apparatus 20 may represent an AF, such as the AF illustrated in Figs. 1-3.

[0058] It should be understood that, in some example embodiments, apparatus 20 may be comprised of an edge cloud server as a distributed computing system where the server and the radio node may be stand-alone apparatuses communicating with each other via a radio path or via a wired connection, or they may be located in a same entity communicating via a wired connection. For instance, in certain example embodiments where apparatus 20 represents a gNB, it may be configured in a central unit (CU) and distributed unit (DU) architecture that divides the gNB functionality. In such an architecture, the CU may be a logical node that includes gNB functions such as transfer of user data, mobility control, radio access network sharing, positioning, and/or session management, etc. The CU may control the operation of DU(s) over a front-haul interface. The DU may be a logical node that includes a subset of the gNB functions, depending on the functional split option. It should be noted that one of ordinary skill in the art would understand that apparatus 20 may include components or features not shown in Fig. 5B. [0059] In some example embodiments, apparatus 20 may include one or more processors, one or more computer-readable storage medium (for example, memory, storage, or the like), one or more radio access components (for example, a modem, a transceiver, or the like), and/or a user interface. In some embodiments, apparatus 20 may be configured to operate using one or more radio access technologies, such as GSM, LTE, LTE-A, NR, 5G, WLAN, WiFi, NB-IoT, Bluetooth, NFC, MulteFire, and/or any other radio access technologies. It should be noted that one of ordinary skill in the art would understand that apparatus 20 may include components or features not shown in Fig. 5B.

[0060] As illustrated in the example of Fig. 5B, apparatus 20 may include or be coupled to a processor 22 for processing information and executing instructions or operations. Processor 22 may be any type of general or specific purpose processor. In fact, processor 22 may include one or more of general-purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), and processors based on a multi-core processor architecture, as examples. While a single processor 22 is shown in Fig. 5B, multiple processors may be utilized according to other embodiments. For example, it should be understood that, in certain embodiments, apparatus 20 may include two or more processors that may form a multiprocessor system (e.g., in this case processor 22 may represent a multiprocessor) that may support multiprocessing. In certain embodiments, the multiprocessor system may be tightly coupled or loosely coupled (e.g., to form a computer cluster).

[0061] Processor 22 may perform functions associated with the operation of apparatus 20 including, as some examples, precoding of antenna gain/phase parameters, encoding and decoding of individual bits forming a communication message, formatting of information, and overall control of the apparatus 20, including processes related to management of communication resources.

[0062] Apparatus 20 may further include or be coupled to a memory 24 (internal or external), which may be coupled to processor 22, for storing information and instructions that may be executed by processor 22. Memory 24 may be one or more memories and of any type suitable to the local application environment, and may be implemented using any suitable volatile or nonvolatile data storage technology such as a semiconductor-based memory device, a magnetic memory device and system, an optical memory device and system, fixed memory, and/or removable memory. For example, memory 24 can be comprised of any combination of random access memory (RAM), read only memory (ROM), static storage such as a magnetic or optical disk, hard disk drive (HDD), or any other type of non-transitory machine or computer readable media. The instructions stored in memory 24 may include program instructions or computer program code that, when executed by processor 22, enable the apparatus 20 to perform tasks as described herein.

[0063] In an embodiment, apparatus 20 may further include or be coupled to (internal or external) a drive or port that is configured to accept and read an external computer readable storage medium, such as an optical disc, USB drive, flash drive, or any other storage medium. For example, the external computer readable storage medium may store a computer program or software for execution by processor 22 and/or apparatus 20.

[0064] In some embodiments, apparatus 20 may also include or be coupled to one or more antennas 25 for receiving a downlink signal and for transmitting via an uplink from apparatus 20. Apparatus 20 may further include a transceiver 28 configured to transmit and receive information. The transceiver 28 may also include a radio interface (e.g., a modem) coupled to the antenna 25. The radio interface may correspond to a plurality of radio access technologies including one or more of GSM, LTE, LTE-A, 5G, NR, WLAN, NB-IoT, Bluetooth, BT-LE, NFC, RFID, UWB, and the like. The radio interface may include other components, such as filters, converters (for example, digital- to-analog converters and the like), symbol demappers, signal shaping components, an Inverse Fast Fourier Transform (IFFT) module, and the like, to process symbols, such as OFDMA symbols, carried by a downlink or an uplink.

[0065] For instance, transceiver 28 may be configured to modulate information on to a carrier waveform for transmission by the antenna(s) 25 and demodulate information received via the antenna(s) 25 for further processing by other elements of apparatus 20. In other embodiments, transceiver 28 may be capable of transmitting and receiving signals or data directly. Additionally or alternatively, in some embodiments, apparatus 20 may include an input and/or output device (I/O device). In certain embodiments, apparatus 20 may further include a user interface, such as a graphical user interface or touchscreen.

[0066] In an embodiment, memory 24 stores software modules that provide functionality when executed by processor 22. The modules may include, for example, an operating system that provides operating system functionality for apparatus 20. The memory may also store one or more functional modules, such as an application or program, to provide additional functionality for apparatus 20. The components of apparatus 20 may be implemented in hardware, or as any suitable combination of hardware and software. According to an example embodiment, apparatus 20 may optionally be configured to communicate with apparatus 10 or apparatus 30 via a wireless or wired communications link or interface 70 according to any radio access technology, such as NR.

[0067] According to some embodiments, processor 22 and memory 24 may be included in or may form a part of processing circuitry/means or control circuitry/means. In addition, in some embodiments, transceiver 28 may be included in or may form a part of transceiving circuitry or transceiving means.

[0068] As discussed above, according to some embodiments, apparatus 20 may be an AF, for example. According to certain embodiments, apparatus 20 may be controlled by memory 24 and processor 22 to perform the functions associated with example embodiments described herein. For example, in some embodiments, apparatus 20 may be configured to perform one or more of the processes depicted in any of the flow charts or signaling diagrams described herein, such as those illustrated in Figs. 1-4. Thus, according to an embodiment, apparatus 20 may be configured to perform a procedure relating to coordinating between multiple AFs that may want to influence or obtain services for a given PDU session, as discussed elsewhere herein.

[0069] Fig. 5C illustrates an example of an apparatus 30 according to another example embodiment. In an example embodiment, apparatus 30 may be a node or element in a communications network or associated with such a network, such as a UE, communication node, mobile equipment (ME), mobile station, mobile device, stationary device, loT device, or other device. As described herein, a UE may alternatively be referred to as, for example, a mobile station, mobile equipment, mobile unit, mobile device, user device, subscriber station, wireless terminal, tablet, smart phone, loT device, sensor or NB-IoT device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications thereof (e.g., remote surgery), an industrial device and applications thereof (e.g., a robot and/or other wireless devices operating in an industrial and/or an automated processing chain context), a consumer electonics device, a device operating on commercial and/or industrial wireless networks, or the like. As one example, apparatus 30 may be implemented in, for instance, a wireless handheld device, a wireless plug-in accessory, or the like. It should be noted that one of ordinary skill in the art would understand that apparatus 30 may include components or features not shown in Fig. 5C.

[0070] In some example embodiments, apparatus 30 may include one or more processors, one or more computer-readable storage medium (for example, memory, storage, or the like), one or more radio access components (for example, a modem, a transceiver, or the like), and/or a user interface. In some example embodiments, apparatus 30 may be configured to operate using one or more radio access technologies, such as GSM, LTE, LTE-A, NR, 5G, WLAN, WiFi, NB-IoT, MulteFire, and/or any other radio access technologies. It should be noted that one of ordinary skill in the art would understand that apparatus 30 may include components or features not shown in Fig. 5C.

[0071] As illustrated in the example of Fig. 5C, apparatus 30 may include or be coupled to a processor 32 for processing information and executing instructions or operations. Processor 32 may be any type of general or specific purpose processor. In fact, processor 32 may include one or more of general-purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), and processors based on a multi-core processor architecture, as examples. While a single processor 32 is shown in Fig. 5C, multiple processors may be utilized according to other example embodiments. For example, it should be understood that, in certain example embodiments, apparatus 30 may include two or more processors that may form a multiprocessor system (e.g., in this case processor 32 may represent a multiprocessor) that may support multiprocessing. In certain example embodiments, the multiprocessor system may be tightly coupled or loosely coupled (e.g., to form a computer cluster).

[0072] Processor 32 may perform functions associated with the operation of apparatus 30 including, as some examples, precoding of antenna gain/phase parameters, encoding and decoding of individual bits forming a communication message, formatting of information, and overall control of the apparatus 30, including processes related to management of communication resources.

[0073] Apparatus 30 may further include or be coupled to a memory 34 (internal or external), which may be coupled to processor 32, for storing information and instructions that may be executed by processor 32. Memory 34 may be one or more memories and of any type suitable to the local application environment, and may be implemented using any suitable volatile or nonvolatile data storage technology such as a semiconductor-based memory device, a magnetic memory device and system, an optical memory device and system, fixed memory, and/or removable memory. For example, memory 34 can be comprised of any combination of random access memory (RAM), read only memory (ROM), static storage such as a magnetic or optical disk, hard disk drive (HDD), or any other type of non-transitory machine or computer readable media. The instructions stored in memory 34 may include program instructions or computer program code that, when executed by processor 32, enable the apparatus 30 to perform tasks as described herein.

[0074] In an example embodiment, apparatus 30 may further include or be coupled to (internal or external) a drive or port that is configured to accept and read an external computer readable storage medium, such as an optical disc, USB drive, flash drive, or any other storage medium. For example, the external computer readable storage medium may store a computer program or software for execution by processor 32 and/or apparatus 30.

[0075] In some example embodiments, apparatus 30 may also include or be coupled to one or more antennas 35 for receiving a downlink signal and for transmitting via an uplink from apparatus 30. Apparatus 30 may further include a transceiver 38 configured to transmit and receive information. The transceiver 38 may also include a radio interface (e.g., a modem) coupled to the antenna 35. The radio interface may correspond to a plurality of radio access technologies including one or more of GSM, LTE, LTE-A, 5G, NR, WLAN, NB-IoT, BT-LE, RFID, UWB, and the like. The radio interface may include other components, such as filters, converters (for example, digital- to-analog converters and the like), symbol demappers, signal shaping components, an Inverse Fast Fourier Transform (IFFT) module, and the like, to process symbols, such as OFDMA symbols, carried by a downlink or an uplink.

[0076] For instance, transceiver 38 may be configured to modulate information on to a carrier waveform for transmission by the antenna(s) 35 and demodulate information received via the antenna(s) 35 for further processing by other elements of apparatus 30. In other example embodiments, transceiver 38 may be capable of transmitting and receiving signals or data directly. Additionally or alternatively, in some example embodiments, apparatus 30 may include an input and/or output device (I/O device). In certain example embodiments, apparatus 30 may further include a user interface, such as a graphical user interface or touchscreen.

[0077] In an example embodiment, memory 34 stores software modules that provide functionality when executed by processor 32. The modules may include, for example, an operating system that provides operating system functionality for apparatus 30. The memory may also store one or more functional modules, such as an application or program, to provide additional functionality for apparatus 30. The components of apparatus 30 may be implemented in hardware, or as any suitable combination of hardware and software. According to an example embodiment, apparatus 30 may optionally be configured to communicate with apparatus 10 via a wireless or wired communications link 71 and/or to communicate with apparatus 20 via a wireless or wired communications link 72, according to any radio access technology, such as NR.

[0078] According to some example embodiments, processor 32 and memory 34 may be included in or may form a part of processing circuitry or control circuitry. In addition, in some example embodiments, transceiver 38 may be included in or may form a part of transceiving circuitry.

[0079] As discussed above, according to some example embodiments, apparatus 30 may be a UE, communication node, mobile equipment (ME), mobile station, mobile device, stationary device, loT device, for example. According to certain example embodiments, apparatus 30 may be controlled by memory 34 and processor 32 to perform the functions associated with example embodiments described herein. For instance, in some example embodiments, apparatus 30 may be configured to perform one or more of the processes depicted in any of the diagrams or signaling flow diagrams described herein, such as those illustrated in Figs. 1-4. According to certain example embodiments, apparatus 30 may be configured to perform a procedure relating to coordinating between multiple AFs that may want to influence or obtain services for a given PDU session, for instance.

[0080] In some example embodiments, an apparatus (e.g., apparatus 10 and/or apparatus 20) may include means for performing a method, a process, or any of the variants discussed herein. Examples of the means may include one or more processors, memory, controllers, transmitters, receivers, sensors, and/or computer program code for causing the performance of any of the operations discussed herein.

[0081] In view of the foregoing, certain example embodiments provide several technological improvements, enhancements, and/or advantages over existing technological processes and constitute an improvement at least to the technological field of wireless network control and/or management. For example, as discussed in detail above, certain example embodiments are configured to provide methods and/or systems to coordinate or control multiple AFs that want to influence or obtain services for a given PDU session. Thus, some example embodiments allow for different AFs to act in a coordinated manner. Accordingly, the use of certain example embodiments results in improved functioning of communications networks and their nodes, such as base stations, eNBs, gNBs, and/or loT devices, UEs or mobile stations.

[0082] In some example embodiments, the functionality of any of the methods, processes, signaling diagrams, algorithms or flow charts described herein may be implemented by software and/or computer program code or portions of code stored in memory or other computer readable or tangible media, and may be executed by a processor. [0083] In some example embodiments, an apparatus may include or be associated with at least one software application, module, unit or entity configured as arithmetic operation(s), or as a program or portions of programs (including an added or updated software routine), which may be executed by at least one operation processor or controller. Programs, also called program products or computer programs, including software routines, applets and macros, may be stored in any apparatus-readable data storage medium and may include program instructions to perform particular tasks. A computer program product may include one or more computer-executable components which, when the program is run, are configured to carry out some example embodiments. The one or more computer-executable components may be at least one software code or portions of code. Modifications and configurations required for implementing the functionality of an example embodiment may be performed as routine(s), which may be implemented as added or updated software routine(s). In one example, software routine(s) may be downloaded into the apparatus.

[0084] As an example, software or computer program code or portions of code may be in source code form, object code form, or in some intermediate form, and may be stored in some sort of carrier, distribution medium, or computer readable medium, which may be any entity or device capable of carrying the program. Such carriers may include a record medium, computer memory, read-only memory, photoelectrical and/or electrical carrier signal, telecommunications signal, and/or software distribution package, for example. Depending on the processing power needed, the computer program may be executed in a single electronic digital computer or it may be distributed amongst a number of computers. The computer readable medium or computer readable storage medium may be a non-transitory medium.

[0085] In other example embodiments, the functionality of example embodiments may be performed by hardware or circuitry included in an apparatus, for example through the use of an application specific integrated circuit (ASIC), a programmable gate array (PGA), a field programmable gate array (FPGA), or any other combination of hardware and software. In yet another example embodiment, the functionality of example embodiments may be implemented as a signal, such as a non-tangible means, that can be carried by an electromagnetic signal downloaded from the Internet or other network.

[0086] According to an example embodiment, an apparatus, such as a node, device, or a corresponding component, may be configured as circuitry, a computer or a microprocessor, such as single-chip computer element, or as a chipset, which may include at least a memory for providing storage capacity used for arithmetic operation(s) and/or an operation processor for executing the arithmetic operation(s).

[0087] Example embodiments described herein may apply to both singular and plural implementations, regardless of whether singular or plural language is used in connection with describing certain embodiments. For example, an embodiment that describes operations of a single network node may also apply to example embodiments that include multiple instances of the network node, and vice versa.

[0088] One having ordinary skill in the art will readily understand that the example embodiments as discussed above may be practiced with procedures in a different order, and/or with hardware elements in configurations which are different than those which are disclosed. Therefore, although some embodiments have been described based upon these example embodiments, it would be apparent to those of skill in the art that certain modifications, variations, and alternative constructions would be apparent, while remaining within the spirit and scope of example embodiments.

Claims

We Claim:

1. An apparatus, comprising: at least one processor; and at least one memory comprising computer program code, the at least one memory and computer program code configured, with the at least one processor, to cause the apparatus at least to perform: obtaining a sharing policy configured to define preferences for handling application function (AF) requests; receiving, from an application function (AF), a sharing option request that explicitly indicates a sharing option desired by the application function (AF); and determining whether the sharing option request by the application function (AF) is authorized for a user equipment (UE) and protocol data unit (PDU) session.

2. The apparatus of claim 1, wherein the sharing policy specifies at least one of: a default sharing option that is applicable when the application function (AF) does not specify a sharing option in a request; allowed sharing options; orthogonal functionality lists and/or lists of functionality that are not orthogonal; or a non-conflicting functionality list.

3. The apparatus of claim 2, wherein the orthogonal functionality lists comprise two or more functionalities that can be performed simultaneously, and wherein the non-conflicting functionality list comprises functions that can be performed multiple times for different consumers.

4. The apparatus of any of claims 1-3, wherein the sharing option comprises at least one of: an indication that the application function (AF) needs exclusive access for the user equipment (UE) and protocol data unit (PDU) session; an indication that the application function (AF) allows another application function (AF) to influence the protocol data unit (PDU) session or same traffic flow for orthogonal functionality; an indication that the application function (AF) allows another application function (AF) to influence the protocol data unit (PDU) session for different traffic flows; or an indication that the application function (AF) allows another application function (AF) to influence the protocol data unit (PDU) session for the same traffic flow and same functionality.

5. The apparatus of any of claims 1-4, wherein the at least one memory and computer program code are configured, with the at least one processor, to cause the apparatus at least to perform: establishing a sharing state by processing the sharing option request and prior sharing option requests, and in consideration of the sharing policy.

6. The apparatus of claim 5, wherein the at least one memory and computer program code are configured, with the at least one processor, to cause the apparatus at least to perform: updating or establishing the sharing state based on the sharing option(s) in an authorized application function (AF) sharing option request on a per user equipment (UE) or per protocol data unit (PDU) session basis.

7. The apparatus of claim 5, wherein the at least one memory and computer program code are configured, with the at least one processor, to cause the apparatus at least to perform: authorizing a new application function (AF) request according to at least one of the sharing option request, the sharing policy, or the sharing state that results from a prior application function (AF) sharing option request for a same user equipment (UE) and protocol data unit (PDU) session.

8. The apparatus of any of claims 1-7, wherein the at least one memory and computer program code are configured, with the at least one processor, to cause the apparatus at least to perform: provisioning or updating user equipment policies containing sharing assistance information in the user equipment (UE), wherein the sharing assistance information indicates one or more of a sharing policy, currently active sharing options, or a sharing state for a protocol data unit (PDU) session.

9. The apparatus of claim 8, wherein the user equipment policies comprise user equipment route selection policies (URSP).

10. The apparatus of any of claims 1-9, wherein the apparatus comprises at least one of a 5^th generation core network (5GC) node, a policy control function (PCF), network exposure function (NEF), or a new network function.

11. An apparatus, comprising: at least one processor; and at least one memory comprising computer program code, the at least one memory and computer program code configured, with the at least one processor, to cause the apparatus at least to perform: transmitting a sharing option request to a network node, wherein the sharing option request indicates a sharing option desired by the apparatus; receiving, from the network node, an indication of an authorization for the sharing option; and performing procedures according to the authorized sharing option.

12. The apparatus of claim 11, wherein the sharing option comprises at least one of: an indication that the apparatus needs exclusive access for a user equipment (UE) and protocol data unit (PDU) session; an indication that the apparatus allows another application function (AF) to influence the protocol data unit (PDU) session or same traffic flow for orthogonal functionality; an indication that the apparatus allows another application function (AF) to influence the protocol data unit (PDU) session for different traffic flows; or an indication that the apparatus allows another application function (AF) to influence the protocol data unit (PDU) session for the same traffic flow and same functionality.

13. The apparatus of claims 11 or 12, wherein the apparatus comprises an application function, and wherein the network node comprises at least one of a 5^th generation core network (5GC) node, a policy control function (PCF), network exposure function (NEF), or a new network function.

14. An apparatus, comprising: at least one processor; and at least one memory comprising computer program code, the at least one memory and computer program code configured, with the at least one processor, to cause the apparatus at least to perform: receiving configuration of policies comprising assistance information that specifies one or more of a sharing policy, currently active sharing options, or a sharing state for a protocol data unit (PDU) session; and setting up the protocol data unit (PDU) session using the assistance information.

15. The apparatus of claim 14, wherein the policies comprise user equipment route selection policies (URSP).

16. The apparatus of claims 14 or 15, wherein the sharing policy is configured to define preferences for handling application function (AF) requests.

17. The apparatus of any of claims 14-16, wherein the sharing policy specifies at least one of: a default sharing option that is applicable when the application function (AF) does not specify a sharing option in a request; allowed sharing options; orthogonal functionality lists and/or lists of functionality that are not orthogonal; or a non-conflicting functionality list and/or a conflicting functionality list.

18. The apparatus of any of claims 14-17, wherein the apparatus comprises a user equipment.

19. A method, comprising: obtaining a sharing policy configured to define preferences for handling application function (AF) requests; receiving, from an application function (AF), a sharing option request that explicitly indicates a sharing option desired by the application function (AF); and determining whether the sharing option request by the application function (AF) is authorized for a user equipment (UE) and protocol data unit (PDU) session.

20. The method of claim 19, wherein the sharing policy specifies at least one of: a default sharing option that is applicable when the application function (AF) does not specify a sharing option in a request; allowed sharing options; orthogonal functionality lists and/or lists of functionality that are not orthogonal; or a non-conflicting functionality list and/or a conflicting functionality list.

21. The method of claim 20, wherein the orthogonal functionality lists comprise two or more functionalities that can be performed simultaneously, and wherein the non-conflicting functionality list comprises functions that can be performed multiple times for different consumers.

22. The method of any of claims 19-21, wherein the sharing option comprises at least one of: an indication that the application function (AF) needs exclusive access for the user equipment (UE) and protocol data unit (PDU) session; an indication that the application function (AF) allows another application function (AF) to influence the protocol data unit (PDU) session or same traffic flow for orthogonal functionality; an indication that the application function (AF) allows another application function (AF) to influence the protocol data unit (PDU) session for different traffic flows; or an indication that the application function (AF) allows another application function (AF) to influence the protocol data unit (PDU) session for the same traffic flow and same functionality.

23. The method of any of claims 19-22, comprising: establishing a sharing state by processing the sharing option request and prior sharing option requests, and in consideration of the sharing policy.

24. The method of claim 23, comprising: updating or establishing the sharing state based on the sharing option(s) in an authorized application function (AF) sharing option request on a per user equipment (UE) or per protocol data unit (PDU) session basis.

25. The apparatus of claim 23, comprising: authorizing a new application function (AF) request according to at least one of the sharing option request, the sharing policy, or the sharing state that results from a prior application function (AF) sharing option request for a same user equipment (UE) and protocol data unit (PDU) session.

26. The method of any of claims 19-25, comprising: provisioning or updating user equipment policies containing sharing assistance information in the user equipment (UE), wherein the sharing assistance information specifies one or more of a sharing policy, currently active sharing options, or a sharing state for a protocol data unit (PDU) session.

27. The method of claim 26, wherein the user equipment policies comprise user equipment route selection policies (URSP).

28. The method of any of claims 19-27, wherein the method is performed by at least one of a 5^th generation core network (5GC) node, a policy control function (PCF), network exposure function (NEF), or a new network function.

29. A method, comprising: transmitting a sharing option request to a network node, wherein the sharing option request indicates a sharing option desired by the apparatus; receiving, from the network node, an indication of an authorization for the sharing option; and performing procedures according to the authorized sharing option.

30. The method of claim 29, wherein the sharing option comprises at least one of: an indication that the apparatus needs exclusive access for a user equipment (UE) and protocol data unit (PDU) session; an indication that the apparatus allows another application function (AF) to influence the protocol data unit (PDU) session or same traffic flow for orthogonal functionality; an indication that the apparatus allows another application function (AF) to influence the protocol data unit (PDU) session for different traffic flows; or an indication that the apparatus allows another application function (AF) to influence the protocol data unit (PDU) session for the same traffic flow and same functionality.

31. The method of claims 29 or 30, wherein the method is performed by an application function, and wherein the network node comprises at least one of a 5^th generation core network (5GC) node, a policy control function (PCF), network exposure function (NEF), or a new network function.

32. A method, comprising: receiving configuration of policies comprising assistance information that specifies one or more of a sharing policy, currently active sharing options, or a sharing state for a protocol data unit (PDU) session; and setting up the protocol data unit (PDU) session using the assistance information.

33. The method of claim 32, wherein the policies comprise user equipment route selection policies (URSP).

34. The method of claims 32 or 33, wherein the sharing policy is configured to define preferences for handling application function (AF) requests.

35. The method of any of claims 32-34, wherein the sharing policy specifies at least one of: a default sharing option that is applicable when the application function (AF) does not specify a sharing option in a request; allowed sharing options; orthogonal functionality lists and/or lists of functionality that are not orthogonal; or a non-conflicting functionality list and/or a conflicting functionality list.

36. The method of any of claims 32-35, wherein the method is performed by a user equipment.

37. An apparatus, comprising: means for obtaining a sharing policy configured to define preferences for handling application function (AF) requests; means for receiving, from an application function (AF), a sharing option request that explicitly indicates a sharing option desired by the application function (AF); and means for determining whether the sharing option request by the application function (AF) is authorized for a user equipment (UE) and protocol data unit (PDU) session.

38. An apparatus, comprising: means for transmitting a sharing option request to a network node, wherein the sharing option request indicates a sharing option desired by the apparatus; means for receiving, from the network node, an indication of an authorization for the sharing option; and means for performing procedures according to the authorized sharing option.

39. An apparatus, comprising: means for receiving configuration of policies comprising assistance information that specifies one or more of a sharing policy, currently active sharing options, or a sharing state for a protocol data unit (PDU) session; and means for setting up the protocol data unit (PDU) session using the assistance information.