Application servers, network elements, and user equipment

Abstract

A network can provision a user equipment (UE) with charging rules for the UE to host sidelink (SL) communications with other UEs. An application server can receive information indicating that a group of user equipment (UEs) has been formed, the group of UEs including a first UE connected to a radio access network (RAN) and at least one additional UE connected to the first UE via a sidelink (SL), select SL parameters including session management parameters and charging parameters for a SL session of the group of UEs, and provision the selected SL parameters to a policy control function (PCF) of a core network (CN).

Description

BACKGROUND

[0001] A user equipment (UE) can be configured with multiple communication links. For example, a UE can receive signals from a cell of a corresponding network over a downlink and can transmit signals to a cell of a corresponding network over an uplink. The UE can also be configured to communicate with another UE via a sidelink (SL). The term "sidelink" refers to a communication link that can be used for device-to-device (D2D) communication. Thus, the SL can facilitate communication between a UE and another UE without involving a network cell.

[0002] During an interactive service that includes multiple UEs (e.g., a network-controlled interactive service (NCIS) for an interactive game), the UEs can include different roles within the service. For example, one or more UEs can be a session leader (or "primary UE") that utilizes network resources to perform the service, while other UEs in a group of UEs, e.g., "secondary UEs," can be connected to the primary UE over a SL and can not be directly connected to the network. The primary UE can incur data usage and / or utilize network resources that the secondary UEs can avoid. A mobile network operator (MNO) can wish to establish charging / billing rules for allocating the cost of the service among the group of UEs. SUMMARY

[0003] Some example embodiments relate to an application server having one or more processors configured to perform operations. The operations include receiving information indicating that a group of user equipments (UEs) has been formed, the group of UEs including a first UE connected to a radio access network (RAN) and at least one additional UE connected to the first UE via a sidelink (SL); selecting SL parameters including session management parameters and charging parameters for a SL session of the group of UEs; and provisioning the selected SL parameters to a policy control function (PCF) of a core network (CN).

[0004] Other example embodiments relate to a network component having one or more processors configured to perform operations. The operations include receiving, from an application server (AS), a provisioning of sidelink (SL) parameters for an interactive service of a group of user equipments (UEs), the group of UEs including a first UE and at least one additional UE connected to the first UE via a SL, the SL parameters including session management parameters and charging parameters for a SL session of the group of UEs; converting at least a portion of the SL parameters to policy rules including session management rules and charging rules; and provisioning the policy rules for the SL session for the first UE.

[0005] Other exemplary embodiments relate to a network component having one or more processors configured to perform operations. These operations include: establishing a first Protocol Data Unit (PDU) session for communication between a core network (CN) and a user equipment (UE); receiving from a Policy Control Function (PCF) a supply of policy rules for a group of UEs, the group including a UE and at least one other UE connected to the UE via a side link (SL), wherein the policy rules include session management rules and charging rules for interactive services; establishing a second PDU session for the UE group based on the policy rules; and determining the duration of the second PDU session according to the policy rules at the end of the group PDU session.

[0006] Another exemplary embodiment relates to a user equipment (UE) having one or more processors configured to perform operations. The operations include: establishing a UE group comprising the UE for interaction services and at least one other UE, wherein the at least one other UE is connected to the UE via a side link (SL); receiving a provision of policy rules for the interaction services, wherein the policy rules include session management rules and charging rules for the interaction services; establishing a Protocol Data Unit (PDU) session with Session Management Function (SMF) for the interaction services based on the policy rules; performing the interaction services with the at least one other UE via the SL; and reporting the duration of the PDU session to the SMF at the end of the interaction services. Attached Figure Description

[0007] Figure 1 Exemplary network arrangements according to various exemplary implementations are shown.

[0008] Figure 2 Exemplary UEs according to various exemplary implementations are shown.

[0009] Figure 3 An exemplary network arrangement is shown, which includes a first UE (UE1) with a connection to the NG-RAN and two other UEs (UE2 and U3) with sidelink connections to UE1.

[0010] Figure 4 The call flow is shown for providing path selection and charging rule parameters for the network and user equipment (UE) involving side link (SL) group communications of the UE. Detailed Implementation

[0011] The exemplary embodiments can be further understood with reference to the following description and related figures, wherein similar elements have the same reference numerals. The exemplary embodiments relate to a network that tracks the duration of sidelink (SL) sessions (e.g., group interaction services) according to billing rules for user equipment (UEs) connected to the network.

[0012] The exemplary embodiments are described with respect to the UE. However, the use of the UE is provided for illustrative purposes only. The exemplary embodiments can be used with any electronic component configured with hardware, software, and / or firmware for exchanging information (e.g., control information) and / or data with a network. Therefore, the UE described herein is used to represent any suitable electronic device.

[0013] Exemplary implementations are also described with reference to sidelinks (SLs). The term "sidelink" generally refers to a communication link between a UE and another UE. An SL provides direct device-to-device (D2D) communication, where information and / or data exchanged between a UE and another UE via a sidelink does not traverse the cell. In some configurations, a single SL provides bidirectional data communication between a UE and another UE. In other configurations, a single SL provides unidirectional data communication between a UE and another UE, but signaling can be transmitted in both directions. The term "unicast" refers to one-to-one (i.e., D2D) device communication and can generally refer to either bidirectional or unidirectional communication. Various implementations may be applied to one or both of the communication forms indicated below.

[0014] Both the Long Term Evolution (LTE) and 5G New Radio (NR) standards support SL communication. In some configurations, the network can provide the UE with information instructing it on how to establish, maintain, and / or utilize the SL. Therefore, when information and / or data exchanged via the SL does not traverse the cell, the UE and network can exchange SL-related information via the network cell. In other configurations, the SL is not controlled by the network. In any configuration, the first and second UEs can still perform synchronization and discovery procedures and exchange control information corresponding to the SL.

[0015] Network Control Interaction Service (NCIS) involves the exchange of data between users involved in the same NCIS session, such as for interactive gaming. User Equipment (UE) in the same NCIS session is grouped together as an NCIS group and shares certain information. NCIS groups can include users in the local area or users geographically distant from each other, as well as users from the same mobile network operator (MNO) or different MNOs.

[0016] NCIS allows UEs from the same or different MNOs to perform side-link (SL) communication. Some interactive services may require low-latency SL bearers, such as PC5 bearers, meaning that SL communication for services is conducted via network-managed PDU sessions. At least one UE in an NCIS group must be connected to the network to act as the primary UE, while secondary UEs in the NCIS group may have SLs to the primary UE but no connection to the network.

[0017] Figure 1 An exemplary network arrangement 100 according to various exemplary embodiments is shown. The exemplary network arrangement 100 includes UEs 110 and 112. Those skilled in the art will understand that UEs 110 and 112 can be any type of electronic component configured to communicate via a network, such as components of connected cars, mobile phones, tablet computers, smartphones, phablets, embedded devices, wearable devices, Internet of Things (IoT) devices, etc.

[0018] Throughout this specification, the terms "UE 110," "UE," and "transmitting device" are used interchangeably. Additionally, the terms "UE 112," "another UE," and "receiving device" are also used interchangeably. It should also be understood that a real network setup can include any number of UEs used by any number of users. Therefore, the example with two UEs, 110 and 112, is provided for illustrative purposes only.

[0019] UEs 110 and 112 can communicate directly with one or more networks. In the example of network configuration 100, the networks with which UEs 110 and 112 can communicate wirelessly are 5G NR Radio Access Network (5G NR-RAN) 120, LTE Radio Access Network (LTE-RAN) 122, and Wireless Local Area Network (WLAN) 124. These types of networks support Vehicle-to-Everything (V2X) and / or Side Link (SL) communication. In the exemplary network arrangement 100, UEs 110 and 112 are connected via SL. However, UE 110 can also communicate with other types of networks, and UE 110 can also communicate with networks via wired connections. Therefore, UEs 110 and 112 may include a 5G NR chipset communicating with 5G NR-RAN 120, an LTE chipset communicating with LTE-RAN 122, and an ISM chipset communicating with WLAN 124.

[0020] 5G NR-RAN 120 and LTE-RAN 122 may be portions of a cellular network that can be deployed by a cellular provider (e.g., Verizon, AT&T, T-Mobile, etc.). These networks 120, 122 may include, for example, cells or base stations (NodeB, eNodeB, HeNB, eNBS, gNB, gNodeB, macrocell base stations, microcell base stations, small cell base stations, femtocell base stations, etc.) configured to send and receive traffic from UEs equipped with appropriate cellular chipsets. WLAN 124 may include any type of wireless local area network (WiFi, hotspot, IEEE 802.11x network, etc.).

[0021] UEs 110 and 112 can connect to the 5G NR-RAN via gNB 120A. The reference to a single gNB 120A is for illustrative purposes only. Exemplary implementations can be applied to any suitable number of gNBs. UEs 110 and 112 can also connect to LTE-RAN 122 via eNB 122A.

[0022] Those skilled in the art will understand that any associated procedures can be performed for UEs 110 and 112 to connect to 5G NR-RAN 120 and LTE-RAN 122. For example, as discussed above, 5G NR-RAN 120 and LTE-RAN 122 can be associated with a specific cellular provider where UEs 110, 112, and / or their users have contract and credential information (e.g., stored on a SIM card). Upon detecting the presence of 5G NR-RAN 120, UEs 110 and 112 can transmit the corresponding credential information to associate with 5G NR-RAN 120. More specifically, UEs 110 and 112 can be associated with a specific base station (e.g., gNB 120A of 5G NR-RAN 120 and eNB 122A of LTE-RAN 122).

[0023] UEs 110 and 112 can also communicate directly with each other using a sidelink. This sidelink is a direct D2D communication link. Therefore, information and / or data transmitted directly to another endpoint (e.g., UE 110 or UE 112) does not traverse the cell (e.g., gNB120A, eNB 122A). In some implementations, UEs 110 and 112 can receive information from the cell regarding how to establish, maintain, and / or utilize the sidelink. Therefore, the network (e.g., 5G NR-RAN 120, LTE-RAN 122) can control the sidelink. In other implementations, UEs 110 and 112 can control the sidelink. Regardless of how the sidelink is controlled, UEs 110 and 112 can simultaneously maintain downlink / uplink to the currently pre-occupied cell (e.g., gNB 120A, eNB 122A) and a sidelink to another UE.

[0024] In addition to networks 120, 122, and 124, network deployment 100 also includes a cellular core network 130, an Internet 140, an IP Multimedia Subsystem (IMS) 150, and a network service backbone 160. The cellular core network 130 can be viewed as an interconnected set of components that manage the operation and traffic of a cellular network (e.g., a 5GC in NR). The cellular core network 130 also manages traffic flowing between the cellular network and the Internet 140. Network entities associated with the 5GC include Access and Mobility Management Functions (AMF), Session Management Functions (SMF), Network Exposure Functions (NEF), and Policy Control Functions (PCF). Application Functions (AFs) may also exist, which can be part of the cellular core network 130 or entities external to the cellular core network 130. AFs external to the cellular core network 130 can be, for example, interactive service servers, game application servers, etc. External AFs can interact with network entities within the cellular core network 130 to influence communication to / from the network and to other UEs via sidelinks.

[0025] The AMF (Application Management Provider) is responsible for registration management (e.g., registering the UE with the network) and connection management. The AMF provides transport for Session Management (SM) messages between the UE and the SMF (Service Management Provider) and acts as a transparent broker for routing SM messages. The AMF also handles N2 signaling from the SMF and AMF for PDU sessions and QoS. The UE needs to register with the AMF to receive network services. Registration Management (RM) is used to register or deregister the UE with the network (e.g., the AMF) and to establish the UE context within the network.

[0026] The SMF can be responsible for Session Management (SM) (e.g., session establishment, modification, and release). SM can refer to the management of PDU sessions, and a PDU session or "session" can refer to the PDU connectivity service that provides or enables PDU exchange between UE 801 and a Data Network (DN) identified by a Data Network Name (DNN). A PDU session can be established upon UE request, modified upon UE or 5GC request, and released upon UE or 5GC request. Upon request from an Application Server (AS), the 5GC can trigger a specific application in the UE. In response to receiving a trigger message, the UE can pass the trigger message (or relevant portions / information of the trigger message) to one or more identified applications in the UE. The identified applications in the UE can establish a PDU session to a specific DNN. The SMF can check whether the UE request conforms to the user subscription information associated with the UE. In this regard, the SMF can retrieve and / or request updates from the Unified Data Management (UDM) regarding SMF level subscription data. The SMF can support interaction with external DNs to transmit signaling for PDU session authorization / authentication via external DNs.

[0027] The NEF can provide means for securely exposing services and capabilities provided by 3GPP network functions to third parties, internal exposure / re-exposure, application functions (AFs), edge computing, or fog computing systems. In such implementations, the NEF can authenticate, authorize, and / or restrict AFs. The NEF can also translate information exchanged with AFs as well as information exchanged with internal network functions.

[0028] PCF provides policy rules for control plane functions to enforce these functions and also supports a unified policy framework for managing network behavior. PCF can communicate with AMF, SMF, and AF.

[0029] The Application Controller (AF) can provide information about the impact of applications on traffic routing and interacts with the policy framework for policy control. The AF acts as a quality controller for specific applications residing on the network and interconnects with the PCF. The AF can exchange information with the 5GC via the NEF, which can be used for edge computing implementations.

[0030] IMS150 can generally be described as an architecture for delivering multimedia services to UE 110 using the IP protocol. IMS150 can communicate with cellular core network 130 and Internet 140 to provide multimedia services to UE 110. Network service backbone 160 communicates directly or indirectly with Internet 140 and cellular core network 130. Network service backbone 160 can generally be described as a set of components (e.g., servers, network storage deployments, etc.) that implement a set of services that can be used to extend the functionality of UE 110 to communicate with various networks.

[0031] Figure 2 An exemplary UE 110 according to various exemplary embodiments is shown. Reference will be made to... Figure 1 The network layout 100 is used to describe UE 110. UE 110 may include a processor 205, a memory layout 210, a display device 215, an input / output (I / O) device 220, a transceiver 225, and other components 230. Other components 230 may include, for example, a SIM card, an embedded SIM (eSIM), an audio input device, an audio output device, a power source, a data acquisition device, and ports for electrically connecting UE 110 to other electronic devices. Figure 2 The UE 110 shown can also represent UE 112.

[0032] Processor 205 can be configured to execute multiple engines of UE 110. For example, an engine may include interaction service engine 235. Interaction service engine 235 can perform operations including establishing PDU sessions for application-specific group communications. In addition, interaction service engine 235 can report certain parameters of group communications, such as session duration, to the SMF, which will be described in further detail below.

[0033] The engines described above, each acting as an application (e.g., a program) executed by processor 205, are merely exemplary. The functionality associated with the engines may also be represented as a separate integrated component of UE 110, or as a modular component coupled to UE 110, such as an integrated circuit with or without firmware. For example, the integrated circuit may include input circuitry for receiving signals and processing circuitry for processing signals and other information. Engines may also be embodied as a single application or multiple separate applications. Furthermore, in some UEs, the functionality described for processor 205 is distributed among two or more processors, such as a baseband processor and an application processor. Exemplary implementations can be implemented according to any of these or other configurations of the UE.

[0034] Memory arrangement 210 may be a hardware component configured to store data related to operations performed by UE 110. Display device 215 may be a hardware component configured to display data to a user, while I / O device 220 may be a hardware component enabling user input. Display device 215 and I / O device 220 may be separate components or may be integrated together (such as a touchscreen). Transceiver 225 may be a hardware component configured to establish connections with 5G NR-RAN 120, WLAN 122, etc. Therefore, transceiver 225 may operate on multiple different frequencies or channels (e.g., consecutive frequency groups).

[0035] Figure 3An exemplary network arrangement 300 is illustrated, comprising a first UE (UE1) with a connection to the NG-RAN and two other UEs (UE2 and UE3) with sidelink connections to UE1. The primary UE (UE1 in this example) may cause data usage and / or utilize network resources that the secondary UEs (UE2 and UE3) connected to the primary UE only via SL might avoid. Therefore, the MNO can establish billing / accounting rules for allocating NCIS costs among the UEs. Billing may be based on, for example, data volume.

[0036] According to the various exemplary embodiments described herein, the network can track the duration of SL sessions (e.g., group interaction services) based on charging rules for user equipment (UEs) connected to the network. The session duration can be determined by the SMF (or received from the UE at the SMF) based on session management (SM) and / or charging rules provided by the Policy Control Function (PCF) and configured for the UE by the Session Management Function (SMF). The PCF communicates with the Application Server (AS) and receives SL session management parameters (e.g., path selection information / traffic routing rules) and charging parameters for interaction services, which the PCF uses to supply the SMF for the SL sessions.

[0037] The PCF further supplies the UE with UE policy rules for SL, including, for example, session management rules and charging rules. In some implementations, based on the charging rules, the SMF identifies the start and end of the SL session to determine the session duration. In an alternative implementation, the UE is supplied with SL usage-related information to report to the SMF.

[0038] Figure 4 Call flow 400 is illustrated for providing path selection and charging rules for network and user equipment (UE) communications involving side-link (SL) groups of UEs. End-to-end operation relies in part on existing procedures defined for 5GS.

[0039] The entities involved in call flow 400 include three UEs, such as UE1, UE2, and UE3 communicating in the interactive service. These three UEs can be similarly configured as described above. Figure 3 The aforementioned UEs will be described in detail below. However, in other embodiments, a number of other UEs may participate in interactive services, such as NCIS sessions. Call flow 400 also includes NR RAN, AMF, SMF, PCF, and an application server (AS) acting as an AF.

[0040] In 402, UE1 is registered and has a PDU session established for communication with the NR RAN via the Uu interface. As discussed above, the PDU session can be managed by the SMF via the AMF.

[0041] In 404, UE1 performs a discovery procedure for UEs interested in performing application-specific group communications and discovers UE2 and UE3. The discovery procedure can be performed using parameters previously provided by the application server (AS) or pre-configured in the UE. In this example, a group including UE1, UE2, and UE3 can be considered to have been established, with UE1 acting as the primary role and UE2 and UE3 acting as secondary roles via a SL to UE1. UE1 can notify the AS, which can act as an AF (AF of the 3GPP network to which UE1 is a subscriber), that the group has been established. In other exemplary embodiments, if deployed by an MNO, the AS can obtain information about the formed group from the 5G Direct Discovery Name Management Function (DDNMF) (not shown).

[0042] In 406, the AS is triggered (based on group establishment) to supply session management and charging parameters to the PCF, either directly or via the NEF, such as parameters for sidelink group communication and charging. Session management and charging parameters may also be associated with validity periods (e.g., the duration for which parameters remain valid). These parameters may be influenced by the corresponding capabilities of the group member UEs provided to the AS in 404 (e.g., the role of the UE in the group).

[0043] In section 408, the PCF converts information provided by the AF into UE policy rules and supplies them to UE1. These rules may include traffic routing rules for PC5 path selection, and these traffic routing rules are then supplied to the UE using existing methods (such as those defined in section 4.2.4.3 of TS23.502). The PC5 interface is designated for one-to-many group communication, such as SL communication, and has an associated bearer-level security mechanism (PC5 bearer). If UE-based reporting used by the SL for communication is used by the network, these rules are also configured by the PCF as part of this supply. For example, the UE may be supplied with reporting the duration of SL sessions.

[0044] In section 410, the PCF further supplies the SMF with session management rules and billing rules. For example, billing rules may include rules in which the duration of an SL session is used as a parameter for billing.

[0045] In 412, the UE initiates PDU session establishment (for example, for a sidelink-specific DNN) or modification of an existing PDU session (e.g., to add an SL PC5 bearer) based on the supplied application traffic routing rules. The PDU session is established or modified according to the SM rules provided from the PCF to the SMF. If a PDU session modification is initiated, it can be triggered by the SMF. For an SL bearer, the SMF requests the NR RAN (via the AMF) to allocate resources. In another implementation, the SMF may request the NR RAN to report the SL frequency for which resources are allocated. The NR RAN confirms the allocation of resources for the new or modified PDU session. If requested by the SMF, the NR RAN may additionally include the configured SL frequency in its confirmation to the SMF.

[0046] In step 414, upon confirmation from the NR RAN, the SMF marks the start of the SL session. This step allows the SMF to track the session duration of interactive services used for billing purposes based on the billing rules provided by the PCF. In an alternative implementation, the duration of the SL session can also be reported by the UE. In this implementation, in step 508, rules for reporting the duration of the SL session are provided to the UE.

[0047] In 416, UE1, UE2, and UE3 perform interactive services via SL communication. It should be noted that in some implementations, similar to UE1, UE2 and UE3 may also have network connectivity and be provided with billing rules.

[0048] In 418, SL communication ends. The end of sidelink communication can be triggered by the application, UE1 and / or another UE near the mobile network, or the expiration of the validity period of the supplied session management rules and charging rules.

[0049] In 420, the end of SL communication triggers the release of the PDU session (if established only for SL communication) or the modification of the PDU session (e.g., to remove the PC5 bearer).

[0050] In section 422, when a PDU session is released or modified, the SMF marks the SL session as ended according to the charging rules. If configured to report SL usage-related information, the UE sends this information to the SMF during this phase.

[0051] Those skilled in the art will understand that the exemplary embodiments described above can be implemented with any suitable software or hardware configuration or combination thereof. Exemplary hardware platforms for implementing the exemplary embodiments may include, for example, Intel x86-based platforms with compatible operating systems, Windows OS, Mac platforms and MAC OS, and mobile devices with operating systems such as iOS, Android, etc. In other examples, exemplary embodiments of the methods described above may be embodied as programs comprising lines of code stored on a non-transitory computer-readable storage medium, which, at compile time, can be executed on a processor or microprocessor.

[0052] Although this patent application describes various combinations of various embodiments, each with different features, those skilled in the art will understand that any feature of an embodiment can be combined with features of other embodiments or features that are not functionally or logically inconsistent with the operation or function of the device of the disclosed embodiment of the invention in any manner not explicitly denied.

[0053] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly explained to users.

[0054] It will be apparent to those skilled in the art that various modifications can be made to this disclosure without departing from its spirit or scope. Therefore, this disclosure is intended to cover all modifications and variations thereof, provided that such modifications and variations are within the scope of the appended claims and their equivalents.

Claims

1. An application server, comprising: one or more processors configured to perform operations comprising: receiving information indicating that a group of user equipment, UEs, has been formed, the group of UEs including a first UE connected to a radio access network, RAN, and at least one further UE connected to the first UE via a sidelink, SL; selecting SL parameters, the SL parameters including session management parameters and charging parameters for a SL session of the group of UEs; and provisioning the selected SL parameters to a policy control function, PCF, of a core network, CN, to facilitate the PCF converting at least a portion of the SL parameters to policy rules including session management rules and charging rules.

2. The application server of claim 1, wherein the information is received from the first UE.

3. The application server of claim 1, wherein the information is received from a direct discovery name management function, DDNMF, of a network operator.

4. The application server of claim 1, wherein the application server acts in a role of an application function, AF, of a cellular network to which the first UE subscribes.

5. The application server of claim 1, wherein the SL parameters are valid for a predetermined time period.

6. The application server of claim 1, wherein the information includes capability information of one or more of the UEs in the group of UEs.

7. The application server of claim 6, wherein the selecting the SL parameters is based at least on the capability information of the one or more of the UEs.

8. A network component, comprising: one or more processors configured to perform operations comprising: receiving, from an application server, AS, a provisioning of sidelink, SL, parameters for an interactive service of a group of user equipment, UEs, the group of UEs including a first UE and at least one further UE connected to the first UE via a SL, the SL parameters including session management parameters and charging parameters for a SL session of the group of UEs; converting at least a portion of the SL parameters to policy rules including session management rules and charging rules; and providing the policy rules for the SL session for the first UE.

9. The network component of claim 8, wherein the operations further comprise: providing the policy rules to a session management function, SMF, of a core network, CN, to enable the SMF to determine a duration of the SL session according to the charging rules.

10. The network component of claim 8, wherein the policy rules include a rule indicating that the first UE is to report SL usage.

11. The network component of claim 8, wherein the policy rules include a rule indicating that the first UE is to report a duration of the SL session.

12. The network component of claim 8, wherein the network component comprises a policy control function, PCF, of a core network.

13. A network component, comprising: one or more processors configured to perform operations comprising: establishing a first protocol data unit, PDU, session for communication between a core network, CN, and a user equipment, UE; receiving, from a policy control function, PCF, provisioning of policy rules for a group of UEs including the UE and at least one further UE connected to the UE via a sidelink, SL, wherein the policy rules include session management rules and charging rules for an interactive service and are based on SL parameters from an application server, AS, including session management parameters and charging parameters for the group of UEs; establishing a second PDU session for the group of UEs based on the policy rules; and determining a duration of the second PDU session at an end of the group PDU session in accordance with the policy rules.

14. The network element of claim 13, wherein determining the duration of the second PDU session comprises: identifying a start time of the second PDU session and an end time of the second PDU session.

15. The network component of claim 14, wherein the operations further comprise: receiving, from a radio access network, RAN, to which the UE is connected, a confirmation of a resource allocation for the interactive service; and identifying the start time of the second PDU session when the confirmation is received.

16. The network component of claim 15, wherein the operations further comprise: requesting the RAN to provide SL frequency parameters configured for the interactive service.

17. The network component of claim 13, wherein the duration of the second PDU session is determined from a report received from the UE.

18. The network component of claim 13, wherein the second PDU session is one of a new PDU session or a modification of the first PDU session.

19. The network component of claim 18, wherein modifying the first PDU session includes adding a SL bearer to the first PDU session.

20. A user equipment, UE, comprising: one or more processors configured to perform operations comprising: establishing a group of UEs including the UE and at least one further UE for an interactive service, wherein the at least one further UE is connected to the UE via a sidelink, SL; receiving provisioning of policy rules for the interactive service, wherein the policy rules include session management rules and charging rules for the interactive service and are based on SL parameters from an application server, AS, including session management parameters and charging parameters for the group of UEs; establishing, with a session management function, SMF, for the interactive service, a protocol data unit, PDU, session based on the policy rules; performing the interactive service with the at least one further UE via the SL; and reporting, to the SMF, a duration of the PDU session at an end of the interactive service.

Images