WO2023214088A1

WO2023214088A1 - Automation for application-based qos in a 5g vn group

Info

Publication number: WO2023214088A1
Application number: PCT/EP2023/062081
Authority: WO
Inventors: Ping Chen; Maria Cruz Bartolome Rodrigo; Susana Fernandez Alonso; Emiliano MERANO
Original assignee: Telefonaktiebolaget Lm Ericsson (Publ)
Priority date: 2022-05-06
Filing date: 2023-05-08
Publication date: 2023-11-09

Abstract

Methods and apparatuses for UE session management are provided. A method performed by a core network node comprises creating a UE group and adding at least one UE to the UE group, wherein UE group information comprises at least one traffic descriptor. The method further comprises indicating, in the UE group information for the at least one traffic descriptor, an application identifier (AppID) and a Quality of Service (QoS) profile. The method further comprises, in response to the establishment of a Protocol Data Unit (PDU) session by the at least one UE, generating an Application Detection Control (ADC) event using the AppID to detect traffic associated with the AppID. The method also comprises, when traffic associated with the AppID is detected using the ADC event, generating a QoS flow using the QoS profile.

Description

AUTOMATION FOR APPLICATION-BASED QOS IN A 5G VN GROUP

Technical Field

[0001] Embodiments of the present disclosure relate to methods, core network nodes, Policy Control Function (PCF) network nodes, Application Function (AF) network nodes and user equipments (UEs), and particularly methods, core network nodes, PCF network nodes, AF network nodes and UEs for UE session management.

[0002] Embodiments are related to the 3rd Generation Partnership Project (3GPP) 5th Generation (5G) Core, and in particular to 5G Virtual Network (VN) Group of UEs Exposure functionality that is available in Unified Data Management (UDM). A 5G VN Group of UEs may be identified by an External Identifier which may be used by Applications to manage a group of users/devices (an example of an external identifier is a Generic Public Subscription Identifier, GPSI) in an easy and consistent manner to steer the user's connectivity to, e.g. a corporate/private data network.

Background

[0003] A 5G VN group is a group of UEs, typically created by an Application Function (AF). If allowed, the AF may add UE members to the newly created group, and application descriptors associated to the group. These application descriptors are typically delivered to the UE in the form of UE Route Selection Policy (URSP) rules. The URSP provide information on which Protocol Data Unit (PDU) session on a network slice a given service or application should use when it is activated. Using the URSP the UE, when matching an Application initiated by the end user (for example, a corporate application, such as Microsoft Teams or Zoom), establishes a new PDU session (establishing new data connectivity) to an specific Data Network Name (DNN) and slice (identified by Single Network Slice Selection Assistance Information, S-NSSAI).

[0004] There currently exist certain challenge(s). If the end users (UE members of a group, such as a 5G VN group) require a special Quality of Service (QoS) treatment (for example, to support video calls in Microsoft Teams), the AF (continuing with the example, the Microsoft Teams AF) will typically initiate an AF session with QoS for the related UE Internet Protocol (IP) address starting to send/receive video IP packets. This requires that for each UE the AF, Network Exposure Function (NEF) and Policy Control Function (PCF) are required to create and maintain a QoS session for each UE member joining (for example) the Microsoft Teams video call. If the number of UE members grows, a consequence is a large amount of resources being used in one or more of the AF/NEF/PCF, when eventually the QoS for the Application is the same no matter the UE member initiating the App.

[0005] Essentially, existing systems lack an automated procedure to enable QoS treatment on a per Application basis for all UE group members.

[0006] Figure 1 is a signaling diagram that depicts an example of a challenge as discussed above. In Figure 1 , the SMF is a Session Management Function and the AMF is an Access and Mobility Management Function. The AMF, PCF, SMF, Unified Data Repository (UDR), UDM, NEF and AF are examples of network node functions which may be provided by one or more network nodes, which may be core network nodes. As shown by Figure 1 , each member of the 5G VN group requires an AF session with a suitable QoS created by the AF, for each application (traffic descriptor) associated to the group. In some scenarios, this can lead to hundreds or even thousands of sessions/resources being created and/or maintained in one or more of the AF/NEF/PCF; one session is typically required for each combination of UE group member and application.

[0007] 3GPP TS 23.501 version 17.2.0: System architecture for the 5G System (5GS), available at https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx? specificationld=3144 as of 4 May 2022 defines the Stage 2 system architecture for the 5G System, which provides data connectivity and services.

[0008] 3GPP TS 23.502 version 17.2.1 : Procedures for the 5G System (5GS), available at https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails. aspx?specificationld=3145 as of 4 May 2022, defines the Stage 2 procedures and Network Function Services for the 5G system architecture and for the policy and charging control framework.

Summary

[0009] Embodiments of the disclosure aim to provide methods and apparatus that alleviate some or all of the challenges identified herein.

[0010] According to embodiments, a parameter provisioning service in NEF may be enhanced to offer the possibility for the AF to indicate an Application Identifier (Appld) and a QoS profile (QoS reference). In embodiments, the NEF may send the new information towards the UDM, and the UDM may store the new information in a UDR as part of the UE group information (for example, 5G VN group data). Subsequently, a PCF may read the new UE group information from the UDR and apply new business logic based on the Appid/QoS profile to be applied, that is, the PCF may configure an Application Detection Control (ADC) event for those Applds belonging to the UE group. When traffic for the application (s) is detected, for example, by the UPF, the PCF may use the QoS reference associated with the Appld to install new PCC rules with the appropriate (typically upgraded) QoS.

[0011] An embodiment of the disclosure provides a method performed by a core network node for UE session management. The method comprises creating a UE group and adding at least one UE to the UE group, wherein UE group information comprises at least one traffic descriptor. The method further comprises indicating, in the UE group information for the at least one traffic descriptor, an AppID and a QoS profile. The method also comprises, in response to the establishment of a PDU session by the at least one UE, generating an ADC event using the AppID to detect traffic associated with the AppID. The method further comprises, when traffic associated with the AppID is detected using the ADC event, generating a QoS flow using the QoS profile.

[0012] A further embodiment of the disclosure provides a method performed by a PCF for UE session management. The method comprises, in response to a UE establishing a PDU session, retrieving from a UDR UE group information for the UE, wherein the UE group information comprises at least one traffic descriptor and further comprises an AppID and QoS profile for the traffic descriptor. The method also comprises generating an ADC event using the AppID to detect traffic associated with the AppID. The method further comprises utilizing the QoS profile to create one or more PCC rules associated with the AppID, and in response to the detection of traffic associated with the AppID, generating a QoS flow using the one or more PCC rules associated with the AppID. [0013] A further embodiment of the disclosure provides a method performed by an AF for UE session management. The method comprises creating a UE group and adding at least one UE to the UE group, wherein UE group information comprises at least one traffic descriptor. The method further comprises indicating in the UE group information for the at least one traffic descriptor, an AppID and a QoS profile. The method further comprises sending the UE group information comprising the at least one traffic descriptor, AppID and QoS profile information to be stored.

[0014] Additional embodiments are discussed in the application and in the claims. The scope of the disclosure is defined by the claims.

[0015] Certain embodiments may provide one or more of the following technical advantage(s). In embodiments, during the creation of a group of UEs (such as a 5G VN group), an automated mechanism may be provided so that the AF does not need to individually create an AF session with QoS for each UE member using the 5G VN Group App. The automated mechanism may release one or more of AF, NEF and PCF from the burden of maintaining QoS sessions per UE member, and may therefore reduce processing load and increase overall efficiency.

Brief Description of the Drawings

[0016] For a better understanding of the embodiments of the present disclosure, and to show how it may be put into effect, reference will now be made, by way of example only, to the accompanying drawings, in which:

Figure 1 is a signaling diagram that depicts an example of a challenge as discussed in the application;

Figure W1 is a flowchart of a method in accordance with some embodiments;

Figure VV2 is a flowchart of a further method in accordance with some embodiments;

Figure VV3 is a flowchart of a further method in accordance with some embodiments;

Figure VV4 is a flowchart of a further method in accordance with some embodiments;

Figure 2 is a signaling diagram showing methods in accordance with embodiments;

Figure QQ1 shows an example of a communication system in accordance with some embodiments;

Figure QQ2 shows a UE in accordance with some embodiments;

Figure QQ3 shows a network node in accordance with some embodiments;

Figure QQ4 is a block diagram of a host in accordance with embodiments;

Figure QQ5 is a block diagram illustrating a virtualization environment in accordance with embodiments;

Figure QQ6 shows a communication diagram of a host communicating via a network node with a UE over a partially wireless connection in accordance with some embodiments.

Detailed Description [0017] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0018] Figure W1 depicts a method in accordance with particular embodiments. The method W1 may be performed by a UE or wireless device (e.g. the UE QQ112 or UE QQ200 as described later with reference to Figures QQ1 and QQ2 respectively). The method begins at step W102 with the UE activating an application having an AppID that a core network node has used to generate an ADC event. The method continues at step W104 with the UE establishing a PDU session for use by the application. The method then proceeds to step W106 with the UE receiving notification of a QoS flow generated by the core network node for use in transmitting and receiving traffic associated with the application.

[0019] Figure W2 depicts a method in accordance with particular embodiments. The method W2 may be performed by a core network node (e.g. the core network node QQ106 as described later with reference to Figure QQ1). The method begins at step W202 with the core network node creating a UE group and adding at least one UE to the UE group, wherein UE group information comprises at least one traffic descriptor. The method continues at step W204 with the core network node indicating, in the UE group information for the at least one traffic descriptor, an AppID and a QoS profile. At step W206 the core network node, in response to the establishment of a PDU session by the at least one UE, generates an ADC event using the AppID to detect traffic associated with the AppID. At step W208 the core network node, when traffic associated with the AppID is detected using the ADC event, generates a QoS flow using the QoS profile.

[0020] Figure W3 depicts a method in accordance with particular embodiments. The method W3 may be performed by a PCF (which may be hosted, for example, in the core network node QQ106 as described later with reference to Figure QQ1). The method begins at step W302 with the PCF, in response to a UE establishing a PDU session, retrieving from a UDR UE group information for the UE, wherein the UE group information comprises at least one traffic descriptor and further comprises an AppID and QoS profile for the traffic descriptor. The method continues at step W304 with the PCF generating an ADC event using the AppID to detect traffic associated with the AppID. At step W306 the PCF utilizes the QoS profile to create one or more Policy and Charging Control, PCC, rules associated with the AppID. At step W308 the PCF, in response to the detection of traffic associated with the AppID, generating a QoS flow using the one or more PCC rules associated with the AppID .

[0021] Figure W4 depicts a method in accordance with particular embodiments. The method W4 may be performed by a network node (e.g. network node QQ110 or core network node QQ106, both as described later with reference to Figure QQ1). The method begins at step W402 with the AF creating a UE group and adding at least one UE to the UE group, wherein UE group information comprises at least one traffic descriptor. The method continues at step W404 with the AF indicating in the UE group information for the at least one traffic descriptor, an AppID and a QoS profile. At step W406 the AF sends the UE group information comprising the at least one traffic descriptor, AppID and QoS profile information to be stored.

[0022] Figure 2 is a signaling diagram showing methods in accordance with embodiments. In step 1 of Figure 2, the AF creates a 5G VN group of UEs and adds UE members to the group. The AF also includes traffic descriptors for the PCF to generate URSP rules. In embodiments, the AF also includes (on a per traffic descriptor level), an application identifier (Appld) and a QoS profile (QoS) to be applied for the application associated with the traffic descriptor (see step 2). The AppID and/or QoS profile information may be provided for all traffic descriptors, or some of the traffic descriptors. The UE group information is then propagated from the AF to the NEF and UDM, before being stored (including the Appld and QoS) in the UDR, as shown in steps 3-5 (one or more of the AF, NEF, UDM and UDR may form part of the same or different core network nodes or non-core network nodes).

[0023] In step 6-8, a new PDU session is established. At step 9, the PCF retrieves the UE group info. As this group info includes Appld and QoS for the traffic descriptors, the PCF can configure an ADC event to detect application traffic. The PCF may also generate one or more PCC rules. This information is passed to the SMF, which instructs the UPF to report application traffic detection (see steps 10 and 11).

[0024] In steps 12 to 15, a UE policy control session is established and the rules are delivered to the UE; alternatively the policy control session may be established earlier, for example at steps 5 and 6. Subsequently, when the UE opens an application matching a traffic descriptor associated with the UE group, a new PDU session towards the DNN/S-NSSAI associated with the group is established, and a SM policy control session is established for the PDU session (see steps 16 and 17). When traffic associated with the AppID is sent/received by the UE, this is detected using the ADC event and the PCF is informed (see steps 18 to 20). The PCF can then provide PCC Rules so that the SMF generates a QoS flow using the QoS profile for the application (see steps 21 to 23). Accordingly, as set out in step 24), there is no need for an AF session with QoS to be initiated by the AF, as the PCF has orchestrated the creation of a dedicated QoS flow in an automated manner when the user of the UE opened the application.

[0025] Figure QQ1 shows an example of a communication system QQ100 in accordance with some embodiments. [0026] In the example, the communication system QQ100 includes a telecommunication network QQ102 that includes an access network QQ104, such as a radio access network (RAN), and a core network QQ106, which includes one or more core network nodes QQ108. The access network QQ104 includes one or more access network nodes, such as network nodes QQ110a and QQ110b (one or more of which may be generally referred to as network nodes QQ110), or any other similar 3^rd Generation Partnership Project (3GPP) access node or non- 3GPP access point. The network nodes QQ110 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs QQ112a, QQ112b, QQ112c, and QQ112d (one or more of which may be generally referred to as UEs QQ112) to the core network QQ106 over one or more wireless connections.

[0027] Example wireless communications over a wireless connection include transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system QQ100 may include any number of wired or wireless networks, network nodes, UEs, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections. The communication system QQ100 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system. [0028] The UEs QQ112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and/or operable to communicate wirelessly with the network nodes QQ110 and other communication devices. Similarly, the network nodes QQ110 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs QQ112 and/or with other network nodes or equipment in the telecommunication network QQ102 to enable and/or provide network access, such as wireless network access, and/or to perform other functions, such as administration in the telecommunication network QQ102.

[0029] In the depicted example, the core network QQ106 connects the network nodes QQ110 to one or more hosts, such as host QQ116. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network QQ106 includes one more core network nodes (e.g., core network node QQ108) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and/or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node QQ108. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and/or a User Plane Function (UPF).

[0030] The host QQ116 may be under the ownership or control of a service provider other than an operator or provider of the access network QQ104 and/or the telecommunication network QQ102, and may be operated by the service provider or on behalf of the service provider. The host QQ116 may host a variety of applications to provide one or more services. Examples of such applications include the provision of live and/or pre-recorded audio/video content, data collection services, for example, retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0031] As a whole, the communication system QQ100 of Figure QQ1 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WIMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LIFI, and/or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.

[0032] In some examples, the telecommunication network QQ102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network QQ102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network QQ102. For example, the telecommunications network QQ102 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and/or Massive Machine Type Communication (mMTC)ZMassive loT services to yet further UEs.

[0033] In some examples, the UEs QQ112 are configured to transmit and/or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network QQ104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network QQ104. Additionally, a UE may be configured for operating in single- or multi-RAT or multistandard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

[0034] In the example illustrated in Figure QQ1 , the hub QQ114 communicates with the access network QQ104 to facilitate indirect communication between one or more UEs (e.g., UE QQ112c and/or QQ112d) and network nodes (e.g., network node QQ110b). In some examples, the hub QQ114 may be a controller, router, a content source and analytics node, or any of the other communication devices described herein regarding UEs. For example, the hub QQ114 may be a broadband router enabling access to the core network QQ106 for the UEs. As another example, the hub QQ114 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes QQ110, or by executable code, script, process, or other instructions in the hub QQ114. As another example, the hub QQ114 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub QQ114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub QQ114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub QQ114 then provides to the UE either directly, after performing local processing, and/or after adding additional local content. In still another example, the hub QQ114 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy loT devices.

[0035] The hub QQ114 may have a constant/persistent or intermittent connection to the network node QQ110b. The hub QQ114 may also allow for a different communication scheme and/or schedule between the hub QQ114 and UEs (e.g., UE QQ112c and/or QQ112d), and between the hub QQ114 and the core network QQ106. In other examples, the hub QQ114 is connected to the core network QQ106 and/or one or more UEs via a wired connection. Moreover, the hub QQ114 may be configured to connect to an M2M service provider over the access network QQ104 and/or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes QQ110 while still connected via the hub QQ114 via a wired or wireless connection. In some embodiments, the hub QQ114 may be a dedicated hub - that is, a hub whose primary function is to route communications to/from the UEs from/to the network node QQ110b. In other embodiments, the hub QQ114 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node QQ110b, but which is additionally capable of operating as a communication start and/or end point for certain data channels. [0036] Figure QQ2 shows a UE QQ200 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless camera, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle-mounted or vehicle embedded/! ntegrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-loT) UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.

[0037] A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to- infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0038] The UE QQ200 includes processing circuitry QQ202 that is operatively coupled via a bus QQ204 to an input/output interface QQ206, a power source QQ208, a memory QQ210, a communication interface QQ212, and/or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure QQ2. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0039] The processing circuitry QQ202 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory QQ210. The processing circuitry QQ202 may be implemented as one or more hardware- implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry QQ202 may include multiple central processing units (CPUs). The processing circuitry QQ202 may be operable to provide, either alone or in conjunction with other UE QQ200 components, such as the memory QQ210, UE QQ200 functionality. For example, the processing circuitry QQ202 may be configured to cause the UE QQ202 to perform the methods as described with reference to Figure W1.

[0040] In the example, the input/output interface QQ206 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and/or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE QQ200. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

[0041] In some embodiments, the power source QQ208 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source QQ208 may further include power circuitry for delivering power from the power source QQ208 itself, and/or an external power source, to the various parts of the UE QQ200 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source QQ208. Power circuitry may perform any formatting, converting, or other modification to the power from the power source QQ208 to make the power suitable for the respective components of the UE QQ200 to which power is supplied.

[0042] The memory QQ210 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory QQ210 includes one or more application programs QQ214, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data QQ216. The memory QQ210 may store, for use by the UE QQ200, any of a variety of various operating systems or combinations of operating systems.

[0043] The memory QQ210 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and/or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUlCC), integrated UICC (IUICC) or a removable UICC commonly known as ‘SIM card.' The memory QQ210 may allow the UE QQ200 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory QQ210, which may be or comprise a device-readable storage medium. [0044] The processing circuitry QQ202 may be configured to communicate with an access network or other network using the communication interface QQ212. The communication interface QQ212 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna QQ222. The communication interface QQ212 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter QQ218 and/or a receiver QQ220 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter QQ218 and receiver QQ220 may be coupled to one or more antennas (e.g., antenna QQ222) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0045] In some embodiments, communication functions of the communication interface QQ212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and/or standards, such as IEEE 802.11 , Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol/internet protocol (TCP/IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0046] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface QQ212, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient). [0047] As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or controls a robotic arm performing a medical procedure according to the received input.

[0048] A UE, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are devices which are or which are embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door/window sensor, a flood/moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and/or software in dependence on the intended application of the loT device in addition to other components as described in relation to the UE QQ200 shown in Figure QQ2.

[0049] As yet another specific example, in an loT scenario, a UE may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another UE and/or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-loT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.

[0050] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone's speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone's speed. The first and/or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0051] Figure QQ3 shows a network node QQ300 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a UE and/or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)).

[0052] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0053] Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multistandard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and/or Minimization of Drive Tests (MDTs).

[0054] The network node QQ300 includes processing circuitry QQ302, a memory QQ304, a communication interface QQ306, and a power source QQ308, and/or any other component, or any combination thereof. The network node QQ300 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node QQ300 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node QQ300 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory QQ304 for different RATs) and some components may be reused (e.g., a same antenna QQ310 may be shared by different RATs). The network node QQ300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node QQ300, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node QQ300. [0055] The processing circuitry QQ302 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node QQ300 components, such as the memory QQ304, network node QQ300 functionality.

[0056] In some embodiments, the processing circuitry QQ302 includes a system on a chip (SOC). In some embodiments, the processing circuitry QQ302 includes one or more of radio frequency (RF) transceiver circuitry QQ312 and baseband processing circuitry QQ314. In some embodiments, the radio frequency (RF) transceiver circuitry QQ312 and the baseband processing circuitry QQ314 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry QQ312 and baseband processing circuitry QQ314 may be on the same chip or set of chips, boards, or units.

[0057] The memory QQ304 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device-readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by the processing circuitry GG302. The memory GG304 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and/or other instructions capable of being executed by the processing circuitry QQ302 and utilized by the network node QQ300. The memory QQ304 may be used to store any calculations made by the processing circuitry QQ302 and/or any data received via the communication interface QQ306. In some embodiments, the processing circuitry QQ302 and memory QQ304 is integrated.

[0058] The communication interface QQ306 is used in wired or wireless communication of signaling and/or data between a network node, access network, and/or UE. As illustrated, the communication interface QQ306 comprises port(s)/terminal(s) QQ316 to send and receive data, for example to and from a network over a wired connection. The communication interface QQ306 also includes radio front-end circuitry QQ318 that may be coupled to, or in certain embodiments a part of, the antenna QQ310. Radio front-end circuitry QQ318 comprises filters QQ320 and amplifiers QQ322. The radio front-end circuitry QQ318 may be connected to an antenna QQ310 and processing circuitry QQ302. The radio front-end circuitry may be configured to condition signals communicated between antenna QQ310 and processing circuitry QQ302. The radio front-end circuitry QQ318 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry QQ318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters QQ320 and/or amplifiers QQ322. The radio signal may then be transmitted via the antenna QQ310. Similarly, when receiving data, the antenna QQ310 may collect radio signals which are then converted into digital data by the radio front-end circuitry QQ318. The digital data may be passed to the processing circuitry QQ302. In other embodiments, the communication interface may comprise different components and/or different combinations of components.

[0059] In certain alternative embodiments, the network node QQ300 does not include separate radio front-end circuitry QQ318, instead, the processing circuitry QQ302 includes radio front-end circuitry and is connected to the antenna QQ310. Similarly, in some embodiments, all or some of the RF transceiver circuitry QQ312 is part of the communication interface QQ306. In still other embodiments, the communication interface QQ306 includes one or more ports or terminals QQ316, the radio front-end circuitry QQ318, and the RF transceiver circuitry QQ312, as part of a radio unit (not shown), and the communication interface QQ306 communicates with the baseband processing circuitry QQ314, which is part of a digital unit (not shown).

[0060] The antenna QQ310 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. The antenna QQ310 may be coupled to the radio front-end circuitry QQ318 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In certain embodiments, the antenna QQ310 is separate from the network node QQ300 and connectable to the network node QQ300 through an interface or port.

[0061] The antenna QQ310, communication interface QQ306, and/or the processing circuitry QQ302 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node. Any information, data and/or signals may be received from a UE, another network node and/or any other network equipment. Similarly, the antenna QQ310, the communication interface QQ306, and/or the processing circuitry QQ302 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and/or signals may be transmitted to a U E, another network node and/or any other network equipment.

[0062] The power source QQ308 provides power to the various components of network node QQ300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source QQ308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node QQ300 with power for performing the functionality described herein. For example, the network node QQ300 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source QQ308. As a further example, the power source QQ308 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0063] Embodiments of the network node QQ300 may include additional components beyond those shown in Figure QQ3 for providing certain aspects of the network node's functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein. For example, the network node QQ300 may include user interface equipment to allow input of information into the network node QQ300 and to allow output of information from the network node QQ300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node QQ300.

[0064] Figure QQ4 is a block diagram of a host QQ400, which may be an embodiment of the host QQ116 of Figure QQ1 , in accordance with various aspects described herein. As used herein, the host QQ400 may be or comprise various combinations hardware and/or software, including a standalone server, a blade server, a cloud- implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. The host QQ400 may provide one or more services to one or more UEs.

[0065] The host QQ400 includes processing circuitry QQ402 that is operatively coupled via a bus QQ404 to an input/output interface QQ406, a network interface QQ408, a power source QQ410, and a memory QQ412. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures QQ2 and QQ3, such that the descriptions thereof are generally applicable to the corresponding components of host QQ400.

[0066] The memory QQ412 may include one or more computer programs including one or more host application programs QQ414 and data QQ416, which may include user data, e.g., data generated by a UE for the host QQ400 or data generated by the host QQ400 for a UE. Embodiments of the host QQ400 may utilize only a subset or all of the components shown. The host application programs QQ414 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (WC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAG, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). The host application programs QQ414 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host QQ400 may select and/or indicate a different host for over-the-top services for a UE. The host application programs QQ414 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.

[0067] Figure QQ5 is a block diagram illustrating a virtualization environment QQ500 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments QQ500 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized.

[0068] Applications QQ502 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein. For example, the methods as described with reference to Figure VV2 may be implemented.

[0069] Hardware QQ504 includes processing circuitry, memory that stores software and/or instructions executable by hardware processing circuitry, and/or other hardware devices as described herein, such as a network interface, input/output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers QQ506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs QQ508a and QQ508b (one or more of which may be generally referred to as VMs QQ508), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein. The virtualization layer QQ506 may present a virtual operating platform that appears like networking hardware to the VMs QQ508.

[0070] The VMs QQ508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer QQ506. Different embodiments of the instance of a virtual appliance QQ502 may be implemented on one or more of VMs QQ508, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

[0071] In the context of NFV, a VM QQ508 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs QQ508, and that part of hardware QQ504 that executes that VM, be it hardware dedicated to that VM and/or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs QQ508 on top of the hardware QQ504 and corresponds to the application QQ502.

[0072] Hardware QQ504 may be implemented in a standalone network node with generic or specific components. Hardware QQ504 may implement some functions via virtualization. Alternatively, hardware QQ504 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration QQ510, which, among others, oversees lifecycle management of applications QQ502. In some embodiments, hardware QQ504 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system QQ512 which may alternatively be used for communication between hardware nodes and radio units.

[0073] Figure QQ6 shows a communication diagram of a host QQ602 communicating via a network node QQ604 with a UE QQ606 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE QQ112a of Figure QQ1 and/or UE QQ200 of Figure QQ2), network node (such as network node QQ110a of Figure QQ1 and/or network node QQ300 of Figure QQ3), and host (such as host QQ116 of Figure QQ1 and/or host QQ400 of Figure QQ4) discussed in the preceding paragraphs will now be described with reference to Figure QQ6.

[0074] Like host QQ400, embodiments of host QQ602 include hardware, such as a communication interface, processing circuitry, and memory. The host QQ602 also includes software, which is stored in or accessible by the host QQ602 and executable by the processing circuitry. The software includes a host application that may be operable to provide a service to a remote user, such as the UE QQ606 connecting via an over-the-top (OTT) connection QQ650 extending between the UE QQ606 and host QQ602. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection QQ650.

[0075] The network node QQ604 includes hardware enabling it to communicate with the host QQ602 and UE QQ606. The connection QQ660 may be direct or pass through a core network (like core network QQ106 of Figure QQ1) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet.

[0076] The UE QQ606 includes hardware and software, which is stored in or accessible by UE QQ606 and executable by the UE's processing circuitry. The software includes a client application, such as a web browser or operator-specific "app” that may be operable to provide a service to a human or non-human user via UE QQ606 with the support of the host QQ602. In the host QQ602, an executing host application may communicate with the executing client application via the OTT connection QQ650 terminating at the UE QQ606 and host QQ602. In providing the service to the user, the UE's client application may receive request data from the host's host application and provide user data in response to the request data. The OTT connection QQ650 may transfer both the request data and the user data. The UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT connection QQ650.

[0077] The OTT connection QQ650 may extend via a connection QQ660 between the host QQ602 and the network node QQ604 and via a wireless connection QQ670 between the network node QQ604 and the UE QQ606 to provide the connection between the host QQ602 and the UE QQ606. The connection QQ660 and wireless connection QQ670, over which the OTT connection QQ650 may be provided, have been drawn abstractly to illustrate the communication between the host QQ602 and the UE QQ606 via the network node QQ604, without explicit reference to any intermediary devices and the precise routing of messages via these devices.

[0078] As an example of transmitting data via the OTT connection QQ650, in step QQ608, the host QQ602 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE QQ606. In other embodiments, the user data is associated with a UE QQ606 that shares data with the host QQ602 without explicit human interaction. In step QQ610, the host QQ602 initiates a transmission carrying the user data towards the UE QQ606. The host QQ602 may initiate the transmission responsive to a request transmitted by the UE QQ606. The request may be caused by human interaction with the UE QQ606 or by operation of the client application executing on the UE QQ606. The transmission may pass via the network node QQ604, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step QQ612, the network node QQ604 transmits to the UE QQ606 the user data that was carried in the transmission that the host QQ602 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step QQ614, the UE QQ606 receives the user data carried in the transmission, which may be performed by a client application executed on the UE QQ606 associated with the host application executed by the host QQ602.

[0079] In some examples, the UE QQ606 executes a client application which provides user data to the host QQ602. The user data may be provided in reaction or response to the data received from the host QQ602. Accordingly, in step QQ616, the UE QQ606 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input/output interface of the UE QQ606. Regardless of the specific manner in which the user data was provided, the UE QQ606 initiates, in step QQ618, transmission of the user data towards the host QQ602 via the network node QQ604. In step QQ620, in accordance with the teachings of the embodiments described throughout this disclosure, the network node QQ604 receives user data from the UE QQ606 and initiates transmission of the received user data towards the host QQ602. In step QQ622, the host QQ602 receives the user data carried in the transmission initiated by the UE QQ606.

[0080] One or more of the various embodiments improve the performance of OTT services provided to the UE QQ606 using the OTT connection QQ650, in which the wireless connection QQ670 forms the last segment. More precisely, the teachings of these embodiments may improve the capability for automation of dedicated QoS flows for applications and thereby provide benefits such as improved utilization of processing resources and reduced AF workload. [0081] In an example scenario, factory status information may be collected and analyzed by the host QQ602. As another example, the host QQ602 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host QQ602 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host QQ602 may store surveillance video uploaded by a UE. As another example, the host QQ602 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs. As other examples, the host QQ602 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and/or transmitting data.

[0082] In some examples, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection QQ650 between the host QQ602 and UE QQ606, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host QQ602 and/or UE QQ606. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection QQ650 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities. The reconfiguring of the OTT connection QQ650 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node QQ604. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host QQ602. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or 'dummy' messages, using the OTT connection QQ650 while monitoring propagation times, errors, etc.

[0083] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and/or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0084] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and/or by end users and a wireless network generally.

ABBREVIATIONS

At least some of the following abbreviations may be used in this disclosure. If there is an inconsistency between abbreviations, preference should be given to how it is used above. If listed multiple times below, the first listing should be preferred over any subsequent listing(s).

1x RTT CDMA2000 1x Radio Transmission Technology

3GPP 3rd Generation Partnership Project

5G 5th Generation

6G 6th Generation

ABS Almost Blank Subframe

ARQ Automatic Repeat Request

AWGN Additive White Gaussian Noise

BCCH Broadcast Control Channel

BCH Broadcast Channel

CA Carrier Aggregation

CC Carrier Component

CCCH SDU Common Control Channel SDU

CDMA Code Division Multiplexing Access

CGI Cell Global Identifier

CIR Channel Impulse Response

CP Cyclic Prefix

CPICH Common Pilot Channel

CPICH Ec/No CPICH Received energy per chip divided by the power density in the band

CQI Channel Quality information

C-RNTI Cell RNTI

CSI Channel State Information

DCCH Dedicated Control Channel

DL Downlink

DM Demodulation

DMRS Demodulation Reference Signal

DRX Discontinuous Reception

DTX Discontinuous Transmission

DTCH Dedicated Traffic Channel

DUT Device Under Test

E-CID Enhanced Cell-ID (positioning method) eMBMS evolved Multimedia Broadcast Multicast Services

E-SMLC Evolved-Serving Mobile Location Centre

ECGI Evolved CGI eNB E-UTRAN NodeB ePDCCH Enhanced Physical Downlink Control Channel

E-SMLC Evolved Serving Mobile Location Center

E-UTRA Evolved UTRA

E-UTRAN Evolved UTRAN

FDD Frequency Division Duplex FFS For Further Study gNB Base station in NR GNSS Global Navigation Satellite System HARQ Hybrid Automatic Repeat Request

HO Handover

HSPA High Speed Packet Access

HRPD High Rate Packet Data

LOS Line of Sight

LPP LTE Positioning Protocol

LTE Long-Term Evolution

MAC Medium Access Control

MAC Message Authentication Code MBSFN Multimedia Broadcast multicast service Single Frequency Network MBSFN ABS MBSFN Almost Blank Subframe MDT Minimization of Drive Tests

MIB Master Information Block

MME Mobility Management Entity

MSC Mobile Switching Center

NPDCCH Narrowband Physical Downlink Control Channel NR New Radio

OCNG OFDMA Channel Noise Generator OFDM Orthogonal Frequency Division Multiplexing

OFDMA Orthogonal Frequency Division Multiple Access OSS Operations Support System

OTDOA Observed Time Difference of Arrival O&M Operation and Maintenance

PBCH Physical Broadcast Channel

P-CCPCH Primary Common Control Physical Channel

PCell Primary Cell

PCFICH Physical Control Format Indicator Channel

PDCCH Physical Downlink Control Channel PDCP Packet Data Convergence Protocol

PDP Profile Delay Profile

PDSCH Physical Downlink Shared Channel

PGW Packet Gateway

PHICH Physical Hybrid-ARQ Indicator Channel

PLMN Public Land Mobile Network

PMI Precoder Matrix Indicator

PRACH Physical Random Access Channel

PRS Positioning Reference Signal

PSS Primary Synchronization Signal

PUCCH Physical Uplink Control Channel

PUSCH Physical Uplink Shared Channel

RACH Random Access Channel

QAM Quadrature Amplitude Modulation

RAN Radio Access Network

RAT Radio Access Technology

RLC Radio Link Control

RLM Radio Link Management

RNC Radio Network Controller

RNTI Radio Network Temporary Identifier

RRC Radio Resource Control

RRM Radio Resource Management

RS Reference Signal

RSCP Received Signal Code Power

RSRP Reference Symbol Received Power OR Reference Signal Received Power

RSRQ Reference Signal Received Quality OR Reference Symbol Received Quality

RSSI Received Signal Strength Indicator

RSTD Reference Signal Time Difference

SCH Synchronization Channel

SCell Secondary Cell

SDAP Service Data Adaptation Protocol

SDU Service Data Unit

SFN System Frame Number

SGW Serving Gateway

SI System Information

SIB System Information Block

SNR Signal to Noise Ratio SON Self Optimized Network

SS Synchronization Signal

SSS Secondary Synchronization Signal

TDD Time Division Duplex

TDOA Time Difference of Arrival

TOA Time of Arrival

TSS Tertiary Synchronization Signal

TTI Transmission Time Interval

UE User Equipment

UL Uplink

USIM Universal Subscriber Identity Module

UTDOA Uplink Time Difference of Arrival

WCDMA Wide CDMA

WLAN Wide Local Area Network

The following numbered statements provide additional information on the disclosure.

1. A method performed by a user equipment, UE, for session management, the method comprising: activating an application having an application identifier, AppID, that a core network node has used to generate an Application Detection Control, ADC, event; establishing a Protocol Data Unit, PDU, session for use by the application; and receiving notification of a Quality of Service, QoS, flow generated by the core network node for use in transmitting and receiving traffic associated with the application.

2. The method of statement 1 further comprising the step of: utilizing the QoS flow to transmit and receive traffic associated with the application.

3. The method of any preceding statement further comprising, prior to activating the application, receiving from the core network node UE route selection policy, URSP, rules.

4. The method of any preceding statement, wherein the UE is a 3^rd Generation Partnership Project, 3GPP, 5^th Generation, 5G UE.

5. The method of statement 4, wherein the UE forms part of a 5G Virtual Network, VN, UE group managed by the core network node.

6. The method of any preceding statement, further comprising: providing user data; and forwarding the user data to a host via the transmission to the network node.

7. A method performed by a core network node for user equipment, UE, session management, the method comprising: creating a UE group and adding at least one UE to the UE group, wherein UE group information comprises at least one traffic descriptor; indicating, in the UE group information for the at least one traffic descriptor, an application identifier, AppID, and a Quality of Service, QoS, profile; in response to the establishment of a Protocol Data Unit, PDU, session by the at least one UE, generating an Application Detection Control, ADC, event using the AppID to detect traffic associated with the AppID; and when traffic associated with the AppID is detected using the ADC event, generating a QoS flow using the QoS profile.

8. The method of statement 7, further comprising detecting traffic using the ADC event, wherein the detection of the traffic is performed by a User Plane Function, UPF, and/or wherein the detection of the traffic is instructed by a Session Management Function, SMF.

9. The method of any of statements 7 and 8, wherein the generation of the ADC event is performed by a Policy Control Function, PCF, of the core network node.

10. The method of statement 9, further comprising storing the UE group information in a Unified Data Repository, UDR, by a Unified Data Manager, UDM, of the core network node.

11. The method of statement 10 further comprising, prior to generating the ADC event, retrieving the UE group information from the UDR by the PCF.

12. The method of any of statements 9 to 11 , wherein the PCF utilizes the QoS profile to create one or more Policy and Charging Control, PCC, rules to be applied by a Session Management Function, SMF, to generate the QoS flow.

13. The method of any of statements 7 to 12, wherein the creation of the UE group and addition of the at least one UE to the UE group is performed by an Application Function, AF.

14. The method of statement 13 further comprising, by the AF, including in the UE group information a notification Uniform Resource Indicator, URI, requesting notification if QoS failure occurs.

15. The method of statement 14 further comprising, if a failure occurs during the generation of the QoS flow, sending a notification of the failure to the AF.

16. The method of any of statements 7 to 15, wherein the core network node is a 3rd Generation Partnership Project, 3GPP, 5th Generation, 5G core network node.

17. The method of statement 16, wherein the UE group is a 5G Virtual Network, VN, UE group managed by the core network node.

18. The method of any of statements 7 to 17, wherein the UE group comprises a plurality of UEs.

19. The method of any of statements 7 to 18, wherein the UE group information comprises a plurality of traffic descriptors.

20. The method of any of statements 7 to 19, further comprising: obtaining user data; and forwarding the user data to a host or a user equipment.

21. A method performed by a Policy Control Function, PCF, for user equipment, UE, session management, the method comprising: in response to a UE establishing a Protocol Data Unit, PDU, session, retrieving from a Unified Data Repository, UDR, UE group information for the UE, wherein the UE group information comprises at least one traffic descriptor and further comprises an application identifier, AppID, and Quality of Service, QoS, profile for the traffic descriptor; generating an Application Detection Control, ADC, event using the AppID to detect traffic associated with the AppID; utilizing the QoS profile to create one or more Policy and Charging Control, PCC, rules associated with the AppID; and in response to the detection of traffic associated with the AppID, generating a QoS flow using the one or more PCC rules associated with the AppID.

22. A method performed by an Application Function, AF, for user equipment, UE, session management, the method comprising: creating a UE group and adding at least one UE to the UE group, wherein UE group information comprises at least one traffic descriptor; indicating in the UE group information for the at least one traffic descriptor, an application identifier, AppID, and a Quality of Service, QoS, profile; and sending the UE group information comprising the at least one traffic descriptor, AppID and QoS profile information to be stored.

23. A user equipment, UE, for session management, comprising: processing circuitry configured to cause the user equipment to: activate an application having an application identifier, AppID, that a core network node has used to generate an Application Detection Control, ADC, event; establish a Protocol Data Unit, PDU, session for use by the application; and receive notification of a Quality of Service, QoS, flow generated by the core network node for use in transmitting and receiving traffic associated with the application; and power supply circuitry configured to supply power to the processing circuitry.

24. A core network node for user equipment, UE, session management, the core network node comprising: processing circuitry configured to cause the core network node to: create a UE group and add at least one UE to the UE group, wherein UE group information comprises at least one traffic descriptor; indicate, in the UE group information for the at least one traffic descriptor, an application identifier, AppID, and a Quality of Service, QoS, profile; in response to the establishment of a Protocol Data Unit, PDU, session by the at least one UE, generate an Application Detection Control, ADC, event using the AppID to detect traffic associated with the AppID; and when traffic associated with the AppID is detected using the ADC event, generate a QoS flow using the QoS profile; and power supply circuitry configured to supply power to the processing circuitry.

25. A Policy Control Function, PCF, network node for user equipment, UE, session management, the PCF network node comprising: processing circuitry configured to cause the PCF network node to: in response to a UE establishing a Protocol Data Unit, PDU, session, retrieve from a Unified Data Repository, UDR, UE group information for the UE, wherein the UE group information comprises at least one traffic descriptor and further comprises an application identifier, AppID, and Quality of Service, QoS, profile for the traffic descriptor; generate an Application Detection Control, ADC, event using the AppID to detect traffic associated with the AppID; utilize the QoS profile to create one or more Policy and Charging Control, PCC, rules associated with the AppID; and in response to the detection of traffic associated with the AppID, generate a QoS flow using the one or more PCC rules associated with the AppID; and power supply circuitry configured to supply power to the processing circuitry.

26. An Application Function, AF, network node for user equipment, UE, session management, the AF network node comprising: processing circuitry configured to cause the AF network node to: create a UE group and add at least one UE to the UE group, wherein UE group information comprises at least one traffic descriptor; indicate in the UE group information for the at least one traffic descriptor, an application identifier, AppID, and a Quality of Service, QoS, profile; and send the UE group information comprising the at least one traffic descriptor, AppID and QoS profile information to be stored; and power supply circuitry configured to supply power to the processing circuitry.

27. A user equipment, UE, for user equipment, UE, session management, the UE comprising: an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; the processing circuitry being configured to perform any of the steps of any of statements 1 to 6; an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the UE.

28. A host configured to operate in a communication system to provide an over-the-top, OTT, service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment, UE, wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform any of the steps of any of statements 1 to 6 to receive the user data from the host.

29. The host of statement 28, wherein the cellular network further includes a network node configured to communicate with the UE to transmit the user data to the UE from the host.

30. The host of any of statements 28 and 29, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.

31. A method implemented by a host operating in a communication system that further includes a network node and a user equipment (UE), the method comprising: providing user data for the UE; and initiating a transmission carrying the user data to the UE via a cellular network comprising the network node, wherein the UE performs any of the operations of any of statements 1 to 6 to receive the user data from the host.

32. The method of statement 31 , further comprising: at the host, executing a host application associated with a client application executing on the UE to receive the user data from the UE.

33. The method of statement 32, further comprising: at the host, transmitting input data to the client application executing on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application. 34. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform any of the steps of any of statements 1 to 6 to transmit the user data to the host.

35. The host of statement 34, wherein the cellular network further includes a network node configured to communicate with the UE to transmit the user data from the UE to the host.

36. The host of any of statements 34 and 35, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.

37. A method implemented by a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: at the host, receiving user data transmitted to the host via the network node by the UE, wherein the UE performs any of the steps of any of statements 1 to 6 to transmit the user data to the host.

38. The method of statement 37, further comprising: at the host, executing a host application associated with a client application executing on the UE to receive the user data from the UE.

39. The method of statement 38, further comprising: at the host, transmitting input data to the client application executing on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application.

40. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a core network node in a cellular network for transmission to a user equipment (UE), the core network node having a communication interface and processing circuitry, the processing circuitry of the core network node configured to perform any of the operations of any of statements 7 to 22 to transmit the user data from the host to the UE.

41 . The host of statement 40, wherein: the processing circuitry of the host is configured to execute a host application that provides the user data; and the UE comprises processing circuitry configured to execute a client application associated with the host application to receive the transmission of user data from the host.

42. A method implemented in a host configured to operate in a communication system that further includes a core network node and a user equipment (UE), the method comprising: providing user data for the UE; and initiating a transmission carrying the user data to the UE via a cellular network comprising the core network node, wherein the core network node performs any of the operations of any of statements 7 to 22 to transmit the user data from the host to the UE.

43. The method of statement 42, further comprising, at the core network node, transmitting the user data provided by the host for the UE.

44. The method of any of statements 42 and 43, wherein the user data is provided at the host by executing a host application that interacts with a client application executing on the UE, the client application being associated with the host application.

45. A communication system configured to provide an over-the-top service, the communication system comprising: a host comprising: processing circuitry configured to provide user data for a user equipment (UE), the user data being associated with the over-the-top service; and a network interface configured to initiate transmission of the user data toward a network node for transmission to the UE, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of statements 7 to 22 to transmit the user data from the host to the UE.

46. The communication system of statement 45, further comprising: the network node; and/or the user equipment.

47. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to initiate receipt of user data; and a network interface configured to receive the user data from a network node in a cellular network, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of statements 7 to 22 to receive the user data from a user equipment (UE) for the host.

48. The host of statement 47, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.

49. The host of the any of statements 47 and 48, wherein the initiating receipt of the user data comprises requesting the user data.

50. A method implemented by a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: at the host, initiating receipt of user data from the UE, the user data originating from a transmission which the network node has received from the UE, wherein the network node performs any of the steps of any of statements 7 to 22 to receive the user data from the UE for the host.

51 . The method of statement 50, further comprising at the network node, transmitting the received user data to the host.

Claims

1. A method performed by a core network node for user equipment, UE, session management, the method comprising: creating a UE group and adding at least one UE to the UE group, wherein UE group information comprises at least one traffic descriptor; indicating, in the UE group information for the at least one traffic descriptor, an application identifier, AppID, and a Quality of Service, QoS, profile; in response to the establishment of a Protocol Data Unit, PDU, session by the at least one UE, generating an Application Detection Control, ADC, event using the AppID to detect traffic associated with the AppID; and when traffic associated with the AppID is detected using the ADC event, generating a QoS flow using the QoS profile.

2. The method of claim 1, further comprising detecting traffic using the ADC event, wherein the detection of the traffic is performed by a User Plane Function, UPF, and/or wherein the detection of the traffic is instructed by a Session Management Function, SMF.

3. The method of any of claims 1 and 2, wherein the generation of the ADC event is performed by a Policy Control Function, PCF, of the core network node.

4. The method of claim 3, further comprising storing the UE group information in a Unified Data Repository, UDR, by a Unified Data Manager, UDM, of the core network node.

5. The method of claim 4 further comprising, prior to generating the ADC event, retrieving the UE group information from the UDR by the PCF.

6. The method of any of claims 3 to 5, wherein the PCF utilizes the QoS profile to create one or more Policy and Charging Control, PCC, rules to be applied by a Session Management Function, SMF, to generate the QoS flow.

7. The method of any of claims 1 to 6, wherein the creation of the UE group and addition of the at least one UE to the UE group is performed by an Application Function, AF.

8. The method of claim 7 further comprising, by the AF, including in the UE group information a notification Uniform Resource Indicator, URI, requesting notification if QoS failure occurs.

9. The method of claim 8 further comprising, if a failure occurs during the generation of the QoS flow, sending a notification of the failure to the AF.

10. The method of any of claims 1 to 9, wherein the core network node is a 3rd Generation Partnership Project, 3GPP, 5th Generation, 5G core network node.

11. The method of claim 10, wherein the UE group is a 5G Virtual Network, VN, UE group managed by the core network node.

12. The method of any of claims 1 to 11, wherein the UE group comprises a plurality of UEs.

13. The method of any of claims 1 to 12, wherein the UE group information comprises a plurality of traffic descriptors.

14. A method performed by a user equipment, UE, for session management, the method comprising: activating an application having an application identifier, AppID, that a core network node has used to generate an Application Detection Control, ADC, event; establishing a Protocol Data Unit, PDU, session for use by the application; and receiving notification of a Quality of Service, QoS, flow generated by the core network node for use in transmitting and receiving traffic associated with the application.

15. The method of claim 14 further comprising the step of: utilizing the QoS flow to transmit and receive traffic associated with the application.

16. The method of any of claims 14 and 15 further comprising, prior to activating the application, receiving from the core network node UE route selection policy, URSP, rules.

17. The method of any of claims 14 to 16, wherein the UE is a 3^rd Generation Partnership Project, 3GPP, 5^th Generation, 5G UE.

18. The method of claim 17, wherein the UE forms part of a 5G Virtual Network, VN, UE group managed by the core network node.

19. A method performed by a Policy Control Function, PCF, for user equipment, UE, session management, the method comprising: in response to a UE establishing a Protocol Data Unit, PDU, session, retrieving from a Unified Data Repository, UDR, UE group information for the U E, wherein the UE group information comprises at least one traffic descriptor and further comprises an application identifier, AppID, and Quality of Service, QoS, profile for the traffic descriptor; generating an Application Detection Control, ADC, event using the AppID to detect traffic associated with the AppID; utilizing the QoS profile to create one or more Policy and Charging Control, PCC, rules associated with the AppID; and in response to the detection of traffic associated with the AppID, generating a QoS flow using the one or more PCC rules associated with the AppID.

20. A method performed by an Application Function, AF, for user equipment, UE, session management, the method comprising: creating a UE group and adding at least one UE to the UE group, wherein UE group information comprises at least one traffic descriptor; indicating in the UE group information for the at least one traffic descriptor, an application identifier, AppID, and a Quality of Service, QoS, profile; and sending the UE group information comprising the at least one traffic descriptor, AppID and QoS profile information to be stored.

21 . A user equipment, UE, for session management, comprising: processing circuitry configured to cause the user equipment to: activate an application having an application identifier, AppID, that a core network node has used to generate an Application Detection Control, ADC, event; establish a Protocol Data Unit, PDU, session for use by the application; and receive notification of a Quality of Service, QoS, flow generated by the core network node for use in transmitting and receiving traffic associated with the application; and power supply circuitry configured to supply power to the processing circuitry.

22. A core network node for user equipment, UE, session management, the core network node comprising: processing circuitry configured to cause the core network node to: create a UE group and add at least one UE to the UE group, wherein UE group information comprises at least one traffic descriptor; indicate, in the UE group information for the at least one traffic descriptor, an application identifier, AppID, and a Quality of Service, QoS, profile; in response to the establishment of a Protocol Data Unit, PDU, session by the at least one UE, generate an Application Detection Control, ADC, event using the AppID to detect traffic associated with the AppID; and when traffic associated with the AppID is detected using the ADC event, generate a QoS flow using the QoS profile; and power supply circuitry configured to supply power to the processing circuitry.

23. A Policy Control Function, PCF, network node for user equipment, UE, session management, the PCF network node comprising: processing circuitry configured to cause the PCF network node to: in response to a UE establishing a Protocol Data Unit, PDU, session, retrieve from a Unified Data Repository, UDR, UE group information for the UE, wherein the UE group information comprises at least one traffic descriptor and further comprises an application identifier, AppID, and Quality of Service, QoS, profile for the traffic descriptor; generate an Application Detection Control, ADC, event using the AppID to detect traffic associated with the AppID; utilize the QoS profile to create one or more Policy and Charging Control, PCC, rules associated with the AppID; and in response to the detection of traffic associated with the AppID, generate a QoS flow using the one or more PCC rules associated with the AppID; and power supply circuitry configured to supply power to the processing circuitry.

24. An Application Function, AF, network node for user equipment, UE, session management, the AF network node comprising: processing circuitry configured to cause the AF network node to: create a UE group and add at least one UE to the UE group, wherein UE group information comprises at least one traffic descriptor; indicate in the UE group information for the at least one traffic descriptor, an application identifier, AppID, and a Quality of Service, QoS, profile; and send the UE group information comprising the at least one traffic descriptor, AppID and QoS profile information to be stored; and power supply circuitry configured to supply power to the processing circuitry.

25. A communication system comprising at least one of: the UE of claim 21 ; the core network node of claim 22; the PCF network node of claim 23; and the AF network node of claim 24.