Per-application authentication and / or authorization
By passing tokens between 5GMS AA and 5GMS clients, the dynamic policy authorization problem in the 5G media streaming architecture is solved, and effective authentication and resource management of UE applications are realized, ensuring that resource usage complies with SLA and preventing unauthorized use.
Patent Information
- Application Number
- CN202280094171.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-01-31
- Filing Date
- 2022-12-21
- Publication Date
- 2024-11-12
AI Technical Summary
In the prior art, it is difficult to determine and authorize the activation of dynamic policies used in 5G media streaming architecture, resulting in authorization problems when UE applications use communication network resources, affecting the effective management and use of resources.
By passing tokens between 5GMS AA and 5GMS clients, authorization and activation of dynamic policies is achieved, ensuring that only authorized policies are activated and preventing unauthorized resources from being used.
It effectively promotes the authentication and authorization of UE applications, ensures that resource use complies with the Service Level Agreement (SLA), prevents unauthorized resource use, and improves the management and control efficiency of network resources.
Smart Images

Figure CN118947088A_ABST
Abstract
Description
Technical Field
[0001] The present application generally relates to the field of communication networks, and more specifically to techniques for authenticating and / or authorizing a separate application (e.g., hosted by a user equipment UE) that wants to use communication network resources. The present application relates to a method performed at a 5G media stream aware application 5GMS AA, a method performed at a 5G media stream 5GMS client, a method performed at a 5GMS application function 5GMSAF, and a method performed at an application service provider ASP. In addition, corresponding entities, user equipment UE, non-transitory computer-readable storage media, and computer program products are provided. Background Art
[0002] At a high level, the 5G system (5GS) includes an access network (AN) and a core network (CN). The AN provides a connection to the CN to the UE via a base station (such as a gNB or ng-eNB described below). The CN includes various network functions (NFs) that provide a variety of different functions, such as session management, connection management, billing, authentication, etc.
[0003] Figure 1 A high-level view of an exemplary 5G network architecture including a Next Generation Radio Access Network (NG-RAN) 199 and a 5G Core (5GC) 198 is shown. The NG-RAN 199 may include one or more gNodeBs (gNBs) connected to the 5GC via one or more NG interfaces, such as gNBs 100, 150 connected via interfaces 102, 152, respectively. More specifically, the gNBs 100, 150 may be connected to one or more access and mobility management functions (AMFs) in the 5GC 198 via respective NG-C interfaces. Similarly, the gNBs 100, 150 may be connected to one or more user plane functions (UPFs) in the 5GC 198 via respective NG-U interfaces. Various other network functions (NFs) may be included in the 5GC 198, as described in more detail below.
[0004] In addition, the gNBs may be connected to each other via one or more Xn interfaces (e.g., Xn interface 140 between gNBs 100 and 150). The radio technology of NG-RAN is generally referred to as "New Radio" (NR). With respect to the NR interface to the UE, each gNB may support frequency division duplex (FDD), time division duplex (TDD), or a combination thereof. Each gNB may serve a geographic coverage area including one or more cells, and in some cases, may also use various directional beams to provide coverage in the corresponding cells.
[0005] NG-RAN 199 is layered into a radio network layer (RNL) and a transport network layer (TNL). The NG-RAN architecture (i.e., NG-RAN logical nodes and the interfaces between them) is defined as part of the RNL. For each NG-RAN interface (NG, Xn, F1), the relevant TNL protocols and functions are specified. TNL provides services for user plane transport and signaling transport. In some exemplary configurations, each gNB is connected to all 5GC nodes within an "AMF area", where the term "AMF" will be described in more detail below.
[0006] Figure 1 The NG RAN logical nodes shown in the figure include a central unit (CU or gNB-CU) and one or more distributed units (DU or gNB-DU). For example, gNB 100 includes gNB-CU 110 and gNB-DUs 120 and 130. CU (e.g., gNB-CU 110) is a logical node that hosts high-level protocols and performs various gNB functions (e.g., controls the operation of DUs). DUs (e.g., gNB-DUs 120, 130) are decentralized logical nodes that host low-level protocols and may include various subsets of gNB functions depending on the functional partitioning options. Therefore, each of the CU and DU may include various circuits required to perform their respective functions, including processing circuits, transceiver circuits (e.g., for communication), and power supply circuits.
[0007] gNB-CU through the corresponding F1 logical interface (e.g. Figure 1 The F1 interface is connected to one or more gNB-DUs (see interfaces 122 and 132 shown in FIG. 1 ). However, a gNB-DU may be connected to only a single gNB-CU. The gNB-CU and the connected gNB-DU are visible only as a gNB to other gNBs and the 5GC. In other words, the F1 interface is not visible outside the gNB-CU.
[0008] Another change in 5G networks (e.g., in 5GC) is that the traditional peer-to-peer interfaces and protocols found in previous generations of networks are modified and / or replaced by a service-based architecture (SBA), in which a network function (NF) provides one or more services to one or more service consumers. This can be done, for example, through a hypertext transfer protocol / representational state transfer (HTTP / REST) application programming interface (API). In general, various services are self-contained functions that can be changed and modified in an independent manner without affecting other services.
[0009] In addition, services include various "service operations", which are finer-grained divisions of the overall service functionality. The interaction between service consumers and producers can be of "request / response" or "subscription / notification" type. In 5G SBA, the network repository function (NRF) allows each network function to discover services provided by other network functions, while the data storage function (DSF) allows each network function to store its context. This 5G SBA model is based on the principles of modularity, reusability, and self-containment including NFs, which can enable network deployments to take advantage of the latest virtualization and software technologies.
[0010] OAUTH 2.0 is commonly used to provide security to HTTP REST APIs used, for example, in 5GC SBA. OAUTH separates the authorization server from the resource server. This generally simplifies deployment because not every resource server (e.g., HTTP server) needs to also provide authorization functionality. In addition, the separation of the authorization server from the resource server allows access credentials to be reused for different services or between different parties.
[0011] Within 3GPP Release 16 (Rel-16), the 5G media streaming architecture is defined as an evolution of packet-switched streaming defined in 3GPP TS26.234 (v15.1.0). The 5G Media Streaming (5GMS) architecture focuses on content delivery using Dynamic Adaptive Streaming over HTTP (DASH) or HTTP Live Streaming (HLS). 5GMS also defines additional media control-related processes that utilize and / or use the 5G User Plane (UP). 5GMS supports both uplink (UL, i.e., UE to network) and downlink (DL, i.e., network to UE) flows. Multiple features are specific to UL or DL (e.g., content hosting), but other features (e.g., dynamic policies) are used in common for both UL flow use cases and DL flow use cases.
[0012] 5GMS application providers use 5GMS functions to provide application services, such as video or audio streaming services. 5GMS application providers control (and provide) 5GMS-aware applications (5GMS AA) on UEs that are enabled to use 5GMS functions. For example, a UE may include a 5GMS client, which is a type of application enabler client (e.g., OS-level functions) that supports 5G MS-defined protocols and processes. UE application clients can access 5GMS functions via the 5GMS client. Summary of the invention
[0013] The dynamic policy (or dynamic policy invocation) procedure enables a UE application (i.e., associated with an application service provider) to activate a new 3GPP system policy, such as a Quality of Service (QoS) policy or a charging-related policy. However, it is currently unclear how to determine whether a requesting UE application is authorized to activate a particular dynamic policy. For example, it is unclear how to determine whether a requesting UE application is attempting to reuse a policy of another application service provider. This may lead to various problems, issues, and / or difficulties.
[0014] Embodiments of the present disclosure address these and other challenges, problems and / or difficulties, thereby facilitating authentication and / or authorization of UE applications attempting to invoke dynamic policies.
[0015] The above problems are solved by the features of the independent claims, the dependent claims describe further embodiments.
[0016] Some embodiments include example methods (e.g., processes) for 5GMS AA hosted by a UE operating in a communication network (e.g., NG-RAN, 5GC).
[0017] These exemplary methods may include obtaining a token from an application service provider ASP associated with the 5GMS AA, the token indicating that the 5GMS AA is authorized to invoke or activate a dynamic policy for resources of the communication network, wherein the dynamic policy is associated with the ASP. These exemplary methods may also include sending the token to a 5GMS client hosted by the UE. The 5GMS client is associated with a 5GMS application function AF of the communication network.
[0018] Other embodiments include methods (e.g., processes) for a 5G MS client hosted by a UE operating in a communications network (e.g., NG-RAN, 5GC).
[0019] These exemplary methods may include: receiving a token from a 5GMS AA hosted by the UE, the token indicating that the 5GMS AA is authorized to invoke or activate a dynamic policy for resources of the communication network. The dynamic policy is associated with an ASP, and the ASP is associated with the 5GMS AA. These exemplary methods may also include: sending the token to a 5GMS AF of the communication network in a request to activate the dynamic policy for the 5GMS AA. These exemplary methods may also include: receiving a response from the 5GMS AF, the response indicating that the dynamic policy is activated for the 5GMS AA based on the token.
[0020] Other embodiments include methods (e.g., processes) for a 5GMS AF associated with a communications network (e.g., NG-RAN, 5GC).
[0021] These example methods may include receiving a token from a 5GMS client hosted by a UE operating in the communication network, the token indicating that the 5GMS AA hosted by the UE is authorized to invoke or activate a dynamic policy for resources of the communication network. The dynamic policy is associated with an ASP, the ASP is associated with the 5GMS AA, and the token is received in a request to activate the dynamic policy for the 5GMS AA. These example methods may also include sending a response to the 5GMS client indicating that the dynamic policy is activated based on determining that the token is valid.
[0022] Other embodiments include methods (e.g., processes) for an ASP associated with a 5G MSAA hosted by a UE operating in a communications network (e.g., NG-RAN, 5GC).
[0023] These exemplary methods may include providing a token to the 5GMS AA, the token indicating that the 5GMS AA is authorized to invoke or activate a dynamic policy for resources of the communication network, wherein the dynamic policy is associated with the ASP.
[0024] Other embodiments include 5GMS AA, 5GMS client, 5GMS AF and ASP, and UE, network node or computing device hosting 5GMS AA, 5GMS client, 5GMS AF and ASP, which are configured to perform operations corresponding to any exemplary method described herein. Other embodiments also include a non-transitory computer-readable medium storing computer-executable instructions, which configure such 5GMS AA, 5GMS client, 5GMS AF and ASP to perform operations corresponding to any exemplary method described herein when executed by a processing circuit.
[0025] These and other disclosed embodiments can facilitate authentication and / or authorization of UE applications that attempt to invoke dynamic policies related to resource usage in a communication network (e.g., QoS policies or billing-related policies). Embodiments can facilitate compliance with a service level agreement (SLA) between an MNO and an ASP such that the ASP authorizes application resource usage within the scope of the SLA and prevents resource usage outside of these scopes. For example, an embodiment prevents other applications that are not covered by the SLA from using network resources paid for by the ASP. In this way, embodiments provide improved control by the MNO and / or ASP over network resource usage by applications.
[0026] These and other objects, features and advantages of the present disclosure will become apparent upon reading the following “Detailed Description” based on the “Brief Description of the Drawings” briefly described below. BRIEF DESCRIPTION OF THE DRAWINGS
[0027] Figure 1-2 Various aspects of an exemplary 5G network architecture are shown;
[0028] Figure 3 is a block diagram of a 5GMS downlink (DL) architecture with a network level interface;
[0029] Figure 4 shows the application layer view of the 5GMSDL architecture;
[0030] Figure 5-6 Various aspects of an exemplary dynamic policy invocation process are shown;
[0031] Figure 7 is an example arrangement illustrating certain issues associated with authorizing UE applications to invoke or activate dynamic policies;
[0032] Figure 8 A signal flow chart of an authorization process based on a callback mechanism according to some embodiments of the present disclosure is shown;
[0033] Fig. 9 A signal flow diagram showing an authorization process based on a pre-provisioned authorization token according to other embodiments of the present disclosure;
[0034] Fig.10 An exemplary method (e.g., process) for 5GMS AA hosted by a UE operating in a communication network according to various embodiments of the present disclosure is illustrated;
[0035] Fig.11 An exemplary method (e.g., process) for a 5GMS client hosted by a UE operating in a communication network according to various embodiments of the present disclosure is shown;
[0036] Fig.12 An exemplary method (e.g., process) for a 5GMS AF associated with a communication network according to various embodiments of the present disclosure is shown;
[0037] Fig.13 An exemplary method (e.g., process) for an ASP associated with a 5GMS AA hosted by a UE operating in a communication network according to various embodiments of the present disclosure is illustrated;
[0038] Fig.14 A communication system according to various embodiments of the present disclosure is shown;
[0039] Fig.15 A UE according to various embodiments of the present disclosure is shown;
[0040] Fig.16shows a network node according to various embodiments of the present disclosure;
[0041] Fig.17 A host computing system according to various embodiments of the present disclosure is shown;
[0042] Fig.18 is a block diagram of a virtualization environment in which the functions implemented by some embodiments of the present disclosure may be virtualized;
[0043] Fig.19 Communications between a host computing system, a network node, and a UE via multiple connections are shown according to various embodiments of the present disclosure. DETAILED DESCRIPTION
[0044] The embodiments briefly summarized above will now be described more fully with reference to the accompanying drawings. These descriptions are provided by way of example to explain the subject matter to those skilled in the art, and these descriptions should not be construed as limiting the scope of the subject matter to only the embodiments described herein. More specifically, the examples provided below illustrate the operation of various embodiments according to the advantages discussed above.
[0045] Generally, all terms used herein should be interpreted according to their common meaning in the relevant technical field, unless different meanings are clearly given and / or different meanings are implied from the context of its use. Unless clearly stated, all references to one / an / the element, device, assembly, part, step, etc. should be publicly interpreted as referring to at least one instance of the element, device, assembly, part, step, etc. The steps of any method and / or process disclosed herein do not have to be performed in the exact order disclosed, unless a step is clearly described as after or before another step and / or it is implied that a step must be after or before another step. Where appropriate, any feature of any embodiment disclosed herein may be applied to any other embodiment. Similarly, any advantage of any embodiment may be applicable to any other embodiment, and vice versa. Other purposes, features and advantages of the attached embodiments will be apparent from the following description.
[0046] Furthermore, the following terms are used throughout the description given below:
[0047] Core network node: As used herein, a "core network node" is any type of node in a core network. Some examples of core network nodes include, for example, a mobility management entity (MME), a serving gateway (SGW), a packet data network gateway (P-GW), etc. A core network node may also be a node that implements a specific core network function (NF), such as an access and mobility management function (AMF), a session management function (AMF), a user plane function (UPF), a service capability exposure function (SCEF), etc.
[0048] Network node: As used herein, a "network node" is any node that is part of a core network of a telecommunications network (e.g., the core network nodes discussed above). Functionally, a network node is a device that is capable of, configured to, arranged to, and / or operable to communicate directly or indirectly with wireless or wired devices and / or with other network nodes or devices in a telecommunications network to enable and / or provide wireless or wired access to telecommunications devices, and / or to perform other functions (e.g., management) in a telecommunications network.
[0049] Node: As used herein, the term “node” (without any prefix) may be any type of node capable of operating in or with a telecommunication network (including the RAN and / or the core network), including a radio access node (or equivalent terms), a core network node, or a telecommunication device.
[0050] Service: As used herein, the term "service" generally refers to a set of data associated with one or more applications.
[0051] This data will be transmitted over a network and needs to meet certain specific delivery requirements in order for the application to be successful.
[0052] Component: As used herein, the term "component" generally refers to any component required to deliver a service. Examples of components are RAN (e.g., E-UTRAN, NG-RAN, or parts thereof, such as eNB, gNB, base station (BS), etc.), CN (e.g., EPC, 5GC, or parts thereof, including all types of links between RAN and CN entities), and cloud infrastructure with associated resources such as computing, storage, etc. In general, each component may have a "manager", which is an entity (e.g., a RAN manager) that can collect historical information about resource utilization and provide information about the current and predicted future availability of resources associated with the component.
[0053] Note that the description given herein focuses on 3GPP telecommunication systems, and therefore, 3GPP terminology or terms similar to 3GPP terminology are generally used. However, the concepts disclosed herein are not limited to 3GPP systems. Other wireless systems (including but not limited to Wideband Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMax), Ultra Mobile Broadband (UMB), and Global System for Mobile Communications (GSM)) may also benefit from the concepts, principles, and / or embodiments described herein.
[0054] Furthermore, functions and / or operations described herein as being performed by a telecommunication device or a network node may be distributed across multiple telecommunication devices and / or network nodes.
[0055] Figure 2An exemplary non-roaming 5G reference architecture is shown, with service-based interfaces and various NFs defined by 3GPP within the control plane (CP). They include the following NFs, and additional details are provided for the NFs most relevant to the present disclosure:
[0056] Application Function (AF, with Naf interface), which interacts with 5GC to supply information to the network operator, and to subscribe to specific events occurring in the operator's network. The AF provides applications for which services are delivered in a different layer (i.e., transport layer) than the layer where the service has been requested (i.e., signaling layer), controlling flow resources according to what is negotiated with the network. The AF delivers dynamic session information to the PCF (via the N5 interface), including a description of the media to be delivered by the transport layer.
[0057] Policy Control Function (PCF, with Npcf interface), which supports a unified policy framework to manage network behavior by providing PCC rules (e.g., regarding the processing of each service data flow under PCC control) to SMF via N7 reference point. PCF provides policy control decisions and flow-based charging control to SMF, including service data flow detection, gating, QoS, and flow-based charging (except credit management). PCF receives session and media related information from AF, and notifies AF of service (or user) plane events.
[0058] User Plane Function (UPF) - supports the processing of user plane services based on rules received from SMF, including packet inspection and different implementation actions (such as event detection and reporting). UPF communicates with RAN (such as NG-RAN) via N3 reference point
[0059] The N9 reference point is used for communication between two UPFs.
[0060] Session Management Function (SMF, with Nsmf interface), which interacts with the separate service (or user) plane, including creating, updating, and deleting protocol data unit (PDU) sessions, and managing session contexts with the user plane function (UPF), such as for event reporting. For example, SMF performs data flow detection (based on filter definitions included in PCC rules), online and offline charging interactions, and policy enforcement.
[0061] Charging Function (CHF, with Nchf interface), which is responsible for converged online and offline charging functions. It provides quota management (for online charging), re-authorization triggers, rating conditions, etc., and receives notifications about usage reports from the SMF. Quota management involves granting a specific number of units (e.g. bytes, seconds) for a service. The CHF also interacts with the charging system.
[0062] Access and Mobility Management Function (AMF, with Namf interface), which terminates the RAN CP interface and handles all mobility and connection management of the UE (similar to the MME in EPC). AMF communicates with the UE via the N1 reference point,
[0063] And communicate with a RAN (e.g., NG-RAN) via the N2 reference point.
[0064] Network Exposure Function (NEF) with Nnef interface - acts as an entry point into the operator network by securely exposing network capabilities and events provided by 3GPP NFs to the AF, and by providing a way for the AF to securely provide information to the 3GPP network. For example, the NEF provides a service that allows the AF to provision specific subscription data (such as expected UE behavior) for various UEs.
[0065] • Network Repository Function (NRF) with Nnrf interface - provides service registration and discovery, enabling NFs to identify appropriate services provided from other NFs.
[0066] Network Slice Selection Function (NSSF) with Nnssf interface - A "network slice" is a logical partition of a 5G network that provides specific network capabilities and features, e.g. to support a specific service. A network slice instance is a set of NF instances and required network resources (e.g. compute, storage, communication) that provide the capabilities and features of a network slice. NSSF enables other NFs (e.g. AMF) to identify a network slice instance that is suitable for a UE's desired service.
[0067] Authentication Server Function (AUSF) with Nausf interface - Based on the user's home network (HPLMN), it performs user authentication and computes security key material for various purposes.
[0068] • Network Data Analysis Function (NWDAF) with Nnwdaf interface, which is described in more detail above and below.
[0069] · Location Management Function (LMF) with Nlmf interface - supports various functions related to UE location determination, including location determination of the UE and obtaining any of the following: DL location measurements or position estimates from the UE; UL location measurements from the NG RAN; and non-UE associated assistance data from the NG RAN.
[0070] The Unified Data Management (UDM) function supports the generation of 3GPP authentication credentials, user identity handling, access authorization based on subscription data, and other subscriber-related functions. To provide this functionality, UDM uses subscription data (including authentication data) stored in the 5GC Unified Data Repository (UDR). In addition to UDM, UDR supports the storage and retrieval of policy data by the PCF and the storage and retrieval of application data by the NEF. The terms "UDM" and "UDM function" are used interchangeably in this article.
[0071] NRF allows each NF to discover services provided by other NFs, while Data Storage Function (DSF) allows each NF to store its context. In addition, NEF provides exposure of 5GC capabilities and events to AFs inside and outside 5GC. For example, NEF provides a service that allows AF to provision specific subscription data (such as expected UE behavior) for various UEs.
[0072] The communication link between the UE and the 5G network (AN and CN) can be grouped into two different layers. The UE communicates with the CN through the non-access stratum (NAS) and with the AN through the access stratum (AS). All NAS communications are carried out via the NAS protocol ( Figure 2 The N1 interface in the UE takes place between the UE and the AMF. The security of the communication through these layers is provided by the NAS protocol (for NAS) and the PDCP protocol (for AS).
[0073] As mentioned above, within 3GPP Rel-16, the 5G media streaming architecture is defined as an evolution of the packet-switched stream defined in 3GPP TS26.234 (v15.1.0). The 5GMS architecture focuses on content delivery using dynamic adaptive streaming over HTTP (DASH) or HTTP real-time streaming (HLS). 5GMS also defines additional media control-related processes that utilize and / or use 5G UP. 5GMS supports both UL and DL streams. Multiple functions are specific to UL or DL (e.g., content hosting), but other functions (e.g., dynamic policies) are used in common for both UL and DL streaming use cases.
[0074] The 5GMS architecture defines three main functions. The 5GMS client is a type of application enabler client (e.g., OS-level functions) that supports the protocols and procedures defined by the 5G MS. More specifically, the 5GMS client is a 5GMS DL (5GMSd) client or a 5GMS UL (5GMSu) client, depending on the stream direction they support. In a simple case, the 5GMSd client contains a media player capable of retrieving and rendering 3GP-DASH (specified in 3GPP TS26.247), MPEG-DASH (specified in ISO / IES23009-1), or Apple HLS (specified in IETF RFC 8216). In more advanced cases, the 5GMS client contains a media session handler (MSH) that calls the API of the 5GMS AF.
[0075] Additionally, the 5GMS AF includes media control functions such as dynamic policies, consumption reports, metric reports, network assistance, etc. The 5GMS client interacts with the 5GMS AF to invoke dynamic policies or retrieve information (such as network assistance or QoS related information). In addition, the 5GMS application server (AS) includes media-related functions such as content hosting (such as storage or caching of media content), URL signing, server certificates, etc.
[0076] 5GMS application providers (also known as application service providers or ASPs) use 5GMS capabilities to provide application services, such as video or audio streaming services. 5GMS application providers control (and provide) 5GMS-aware applications (5GMS AA) on UEs that are enabled to use 5GMS capabilities. The 5GMS architecture allows the above functions to be placed within a trusted data network (DN) controlled by a mobile network operator (MNO) serving the UE (i.e., hosting the 5GMS client) or within an external DN (e.g., for over-the-top or OTT applications).
[0077] Figure 3 is a block diagram of a 5GMS downlink architecture with corresponding network level interfaces. In this example, a 5GMS client 300 is located in a UE 1500 together with a 5GMS aware application 200 (which is a downstream (d) application case in this case). Note that Figure 3 The above two options are shown, that is, the 5GMS AF 500 and the 5GMS AS 600 are in a trusted DN or in an external DN (where a 5GMS application provider (ASP) 700 is provided). In addition, the UE 1500 is connected to the RAN 50 and the UPF 60 (via the RAN 50). The ASP is connected to the NEF 80, and the 5GMS AF 500 is connected to the PCF 70.
[0078] Figure 4 Figure 2 shows an application layer view of the 5GMSDL architecture. Figure 4 In the example, for clarity, specific 5GC NFs (such as UPF) that do not directly interact in the communication have been removed. Additionally, whether the 5GMS function is deployed in a trusted DN or in an external DN is not visible at the application layer, so these two options are not visible at the application layer. Figure 4 5GMS AF 500 and 5GMS AS 600 may be perceived through configuration (e.g., via NEF API instead of PCF API).
[0079] like Figure 4 As shown, the 5GMS architecture defines the following set reference points between different functions.
[0080] M1, provisioning reference point. M1d contains specific provisioning functions for DL flows.
[0081] M2, media reference point. For DL flows (M2d), 5GMS application providers can ingest media data into the system. Both push and pull ingestion are supported. For UL flows (M2u), 5GMS application providers receive data from the system.
[0082] • M3, reference point between control functions (eg provisioning) and media plane functions (eg content hosting). Not defined by 3GPP.
[0083] M4, media reference point. For DL stream (M4d), the media player retrieves the content. M4d can use 3GP-DASH as the stream format. For UL stream (M4u), the format is not currently defined, but the FLUS format (e.g., defined in 3GPP TS 26.238, 3GPP TR 26.939) can be supported.
[0084] M5, Media Session Handling (MSH) reference point. For example, this API can be used for dynamic policy invocation, metrics reporting, or other 5GMS functions.
[0085] M6 and M7. These are UE internal APIs between 5GMS AA and 5GMS functions. One API is used to control a media player (e.g. a DASH player) and the other is used to interact with MSH.
[0086] M8 (M8d, M8u), provisioning reference point. Not defined by 3GPP, but used to provision 5GMS features.
[0087] The Dynamic Policy (or Dynamic Policy Invocation) procedure via the M5 reference point enables UE applications to activate new 3GPP system policies, such as QoS policies or charging related policies. Figure 5 An example dynamic policy invocation process for a QoS policy is shown. Figure 5 The upper part of shows the initial setup: multiple application flows 41 and 42 from two services (1 and 2) use the same protocol data unit (PDU) session with a single QoS flow identifier (e.g. 5QI=8). However, it is desired to allocate the application flows from service 2 to different QoS flows. This can be triggered by the UE application as needed, for example. Figure 5 The bottom portion of shows the resulting arrangement, where priority traffic flow 43 from service 2 is assigned a different QoS flow identifier than flow 44 (ie 5QI=5).
[0088] A similar example can be implemented based on charging differentiation. The UPF should associate the data of service 2 to a different rating group than the data from service 1. However, in the case of charging separation, only different rating groups are required, not different QoS flows.
[0089] Figure 6 An exemplary information flow of a dynamic policy invocation process is shown. In this example, a UE 1500 (which may be in a vehicle) may include a 5GMS client 300 and an application client 200. The 5GMS client 300 (or an MSH in a 5GMS client) uses an M5 API to trigger a dynamic policy invocation process and provide the required information, including which policy should be applied and how to identify the application service.
[0090] The 5GMS application provider 700 uses the M1 API to provision policy templates within the 5GMS system. Each policy template is associated with an identifier (ID) and contains policy information, such as an API server URL (e.g., including the address of an NEF or PCF) and an API key (e.g., authorization information for an NEF or PCF API). The policy template may also contain additional information, such as a QoS reference string, a data network name (DNN), an ASP identifier, a network slice identifier, etc.
[0091] When the UE application client 200 calls the new dynamic policy API, the MSH provides the relevant policy template ID and service detection information in the form of a service data flow (SDF) description. The SDF specifies the application service to be supervised, for example, as a 5-tuple IP packet filter set or by using other identifiers (such as the service type (ToS) field).
[0092] The 5GMS AF 500 combines the information received from the UE application with the previously provisioned policy template and triggers dynamic policy and charging control (PCC) rule creation via PCF (using the N5 interface) or via NEF (using the N33 interface). When using NEF, the 5GMS AF can use the Nnef_AFsessionWithQoS or NnefChargeableParty API call, depending on the relevant policy.
[0093] One issue is UE application authorization, specifically whether the UE application providing the SDF description is actually authorized to activate dynamic policies. For example, UE application 1 (e.g., a video streaming application from ASP 1) should not be allowed to reuse a policy that the UE application previously obtained from a different ASP 2. As a more specific example, when an ASP subsidizes policy usage or when a specific QoS should be used, it should be verified that the UE application is actually authorized to activate the policy it identifies. In other words, it should be verified that the ASP to which the UE application is associated is the same policy that the UE application is attempting to invoke.
[0094] Figure 7 is an example arrangement illustrating such authorization issues in a downstream environment. In this arrangement, the UE includes a 5GMS client 300 (which in the present case is 5GMSd (d means downstream)) and two 5GMS-aware applications 200a, 200b, namely, application #1 associated with 5GMS ASP#1 700a and 5GMS AS 600a and application #2 associated with 5GMS ASP#2 700b and 5GMS AS600b. In this example, ASP#1 has negotiated with the MNO for the use of a QoS policy, for example to provide a 4K video streaming service with high reliability and high quality. The negotiated QoS policy may be specified in a service level agreement (SLA) between ASP#1 and the MNO. Thus, the MNO is referred to as the "resource owner", application #1 is referred to as the "resource user", and ASP#1 is referred to as the "resource usage owner". It should be understood that the concepts described in this application may also be used in an upstream environment, where the entities shown in the figure with a "d" at the end will be replaced by corresponding entities with a "u" at the end for the uplink. When no suffix is used in the text, both uplink and downlink cases shall be covered. The present application can be used for both uplink and downlink cases.
[0095] In this arrangement, only applications associated with ASP#1 700a should be able to invoke policies subject to the SLA. For example, application #2 from ASP#2 700b should be prevented from invoking policies subject to the SLA because ASP#2 may already have other policies specified in another SLA with the MNO. In the case of OAUTH 2.0, the resource owner is the user of the UE application who is using the network resources under the overall application service subscription. Therefore, the OAUTH 2.0 model cannot be directly applied to Figure 7 The scene shown in .
[0096] Accordingly, embodiments of the present disclosure address these and other challenges, problems and / or difficulties by enabling the 5GMS AF 500 to perform certain authorization checks with the ASP. To facilitate such checks, the 5GMS client 300 provides an authorization token (e.g., via M5), which can be verified by the 5GMS AF 500 itself, or by the 5GMS AF 500 using an immediate callback with the ASP 700a / 700b (e.g., via M1). In essence, this technology introduces a resource usage owner role in an OAUTH-like authentication and authorization architecture. When the ASP 700a / 700b has an SLA with the MNO, the ASP needs to authorize resource usage by the UE application only within the scope of the SLA. The ASP may want to ensure that the UE application uses network resources only in accordance with the application service subscription.
[0097] Embodiments are described below in the context of two different use cases referred to as QoS Flow and Zero Rating. In the QoS Flow use case, the ASP 700a / 700b offers subscriptions at different quality levels, such as 4K video quality subscription, HD video quality, and SD video quality. The ASP has established SLAs with one or more MNOs to provide appropriate network-level QoS to support the application subscription quality level. QoS-related connection usage fees are part of the subscription provided by the ASP and are therefore paid by the ASP.
[0098] In the zero rating use case, the ASP 700a / 700b has a zero rating agreement with the MNO. When the video quality remains below a certain threshold (e.g., SD), the end user is not charged for network data usage. The UE application ensures that the media player does not select a higher quality representation that is not covered by the zero rating agreement between the MNO and the ASP.
[0099] The overall assumption is that the user has an application (e.g., video) service subscription to the ASP. Therefore, the user authorizes itself (and the UE application client) to the ASP backend. Even if there is no network-level resource usage, the ASP needs to authorize the user / UE for consuming content at a specific quality level (e.g., 4K). The embodiments described below enhance this authorization process to include authorization for network-level resources. Two specific techniques are described below, namely, a callback mechanism and token pre-provisioning.
[0100] Figure 8 A signal flow diagram of an authorization process based on a callback mechanism according to some embodiments of the present disclosure is shown. The process is based on an authorization token (e.g., a random number or a random string) provided by ASP 700 to 5GMS AA 200 (via M8) and from 5GMS AA 200 to 5GMS client (MSH) 300 (via M6). When MSH wants to activate a dynamic policy, MSH passes the authorization token to 5GMS AF 500 (via M5). Upon receiving the authorization token, 5GMS AF performs a callback to ASP 700 to verify whether the authorization token is valid. When the token is valid, the UE application is authorized to activate the policy.
[0101] The authorization token may be provided during the login process (eg, with the login response), or may be requested and provided after login (eg, with other application service-specific metadata). Figure 8 The signaling in assumes that the authorization token is provided along with the login response. The 5GMS AA may provide some mobile network information (e.g., Public Land Mobile Network (PLMN) identifier) along with the authorization token request, which may facilitate MNO-specific tokens.
[0102] The following explains in more detail Figure 8 message flow.
[0103] When a user wants to consume video content using 5GMS AA 200, the user needs to authenticate himself to 5GMS AA 200 and to ASP 700. In some cases, the authorization can be cached / stored by 5GMS AA so that the user does not always have to bother entering login credentials. User authentication can be based on a username and password or other credential information sent to ASP 700 in step S81. 5GMS AA 200 can be a native application, such as an Android or iOS application. Alternatively, 5GMS AA can be a browser application, such as a web page.
[0104] The 5GMS application provider (ie, ASP) determines the policy permissions for the application service subscription in step S82. For example, the user may have subscribed to SD quality video service, HD quality video service, or 4K quality video service. The ASP creates an authorization token according to the subscription level (S83) and passes the token to the application 5GMS AA 200 together with the login response (S84).
[0105] When the 5GMS AA then (immediately or later) activates the network service from the 5GMS AF 500 using the 5GMS client 300 (S85), the 5GMS AA 200 passes the authorization token to the MSH in the 5GMS client 300 (S86). Here, the authorization token is provided together with the user ID (uid) to separate the authorization from the user identification. In some cases, the authorization token may also include the uid, for example in encrypted form.
[0106] In S87, when the MSH activates the dynamic policy, the MSH provides the uid and authorization token to the 5GMS AF 500, for example as query line parameters. The 5GMS AF 500 uses a callback function to verify the authorization token to the ASP. The callback function can be implemented as an HTTP REST service, and the ASP may have stored the callback URL with the policy template parameters. In step S88, a request is sent to the ASP 700 to verify the token, and in step S89, the ASP 700 confirms the requested access rights. In S90, the ASP supplies one or more policy templates during the provisioning process (via M1). In addition to the authorization token, the M5 dynamic policy invocation call includes the SDF and the policy template ID.
[0107] When the 5GMS AF 500 has verified that the UE 5GMS AA 200 is authorized to activate the dynamic policy based on the received authentication token (S91), the 5GMS AF performs the corresponding process (S92 and S93) towards the NEF or PCF 400. For example, the 5GMS AF 500 uses the Nnef_AFsessionWithQoS API towards the NEF to trigger the addition of the QoS flow. In step S94, a policy confirmation is sent back in response to step S87.
[0108] Fig. 9A signal flow diagram of an authorization process based on a pre-provisioned authorization token according to other embodiments of the present disclosure is shown. In these embodiments, an authorization token (e.g., a random number or a random string) can be used by the 5GMS AF 500 for multiple authorization processes (even for different users) within a certain validity period. During a provisioning operation or a provisioning update operation, the authorization token (with a validity period) is provisioned to the 5GMS AF 500. Alternatively, the 5GMS AF can be configured to automatically update the authorization token so that the 5GMS AF 500 periodically contacts the 5GMS application provider (i.e., ASP) 700 to obtain a new token.
[0109] and Figure 8 As in the illustrated embodiment, the MSH of the 5GMS client 300 passes the authorization token along with any M5 call to the 5GMS AF 500, which authorizes the MSH based on the token. At or before the end (or expiration) of the limited validity period of the token, the ASP 700 must somehow update the token at the UE 5GMS AA 200. For example, when a user authorizes himself as an application service consumer, a new token may be passed to the 5GMS AA 200. Alternatively, the 5GMS AA 200 may be configured to automatically retrieve new tokens periodically.
[0110] exist Fig. 9 In the illustrated embodiment, the ASP is required to provision an authorization token before any UE 5GMS AA 200 attempts to activate the corresponding network service. The token is generated by the ASP 700 in step S100 and is sent to the 5GMS AF 500 in step S101 along with the validity of the token. This token provisioning (or pre-provisioning) can be done together with other 5GMS provisions (e.g., provisions defined by a policy template). When the user (and associated 5GMS AA 200) identifies itself and authorizes itself towards the ASP 700 in steps S102 and S103 similar to steps S81 and S84, the 5GMS AA receives the authorization token. The UE can store the token, as in another alternative. Steps S104 to S110 correspond to steps S85 to S87 and S91 to S94.
[0111] and Figure 8One difference of the illustrated embodiment is that the 5GMS AF 500 uses an authentication token. When the 5GMS AA 200 attempts to activate a network service (e.g., dynamic policy), the 5GMS AA 200 (via the 5GMS Client 300) provides the 5GMS AF 500 with an authorization token. The 5GMS AF 500 then performs a validity check procedure based on the previously provisioned authorization token. One benefit of this approach is that the 5GMS AF 500 does not need to contact the ASP 700 for every policy activation request from the 5GMS AA (via the 5GMS Client).
[0112] You can refer to Figure 10-13 To further illustrate the above described embodiment, Figure 10-13 Exemplary methods (eg, processes) for 5GMSAA 200, 5GMS Client 300, 5GMS AF 500, and ASP 700 are shown, respectively. In other words, various features of the operations described below correspond to the various embodiments described above. Figure 6-8 The exemplary methods shown in the can be used in conjunction (e.g., in conjunction with each other and with other processes described herein) to provide benefits, advantages, and / or solutions to the problems described herein. Figure 6-8 The exemplary method is shown by specific blocks in a specific order, but the operations corresponding to the blocks can be performed in a different order than shown, and can be combined and / or divided into blocks and / or operations with functions different from those shown. Optional blocks and / or operations are indicated by dotted lines.
[0113] In particular, Fig.10 An exemplary method (e.g., process) for a 5GMS-aware application (AA) 200 hosted by a UE operating in a communication network (e.g., NG-RAN, 5GC, etc.) according to various embodiments of the present disclosure is shown. For example, Fig.10 The exemplary method shown in can be performed by, for example, a 5GMS AA (or a UE hosting a 5GMS AA) as described elsewhere in this document.
[0114] The exemplary method may include the operation of block 1010, wherein the 5GMS AA 200 may obtain a token from an application service provider (ASP) 700 associated with the 5GMS AA, the token indicating that the 5GMS AA is authorized to invoke or activate a dynamic policy for resources of a communication network, wherein the dynamic policy is associated with the ASP. The exemplary method may also include the operation of block 1020, wherein the 5GMS AA 200 may send the token to a 5GMS client 300 hosted by the UE. The 5GMS client is associated with a 5GMS application function (AF) 500 of the communication network.
[0115] In some embodiments, the dynamic policy is a QoS policy. In other embodiments, the dynamic policy is a zero rating policy. In some embodiments, the token is sent (e.g., in block 1020) to a media session handler (MSH) of a 5G MS client.
[0116] In some embodiments, obtaining the token in block 1010 may include operations in sub-block 1011, where the 5GMSAA may send a login request to the ASP 700, and receive a login response from the ASP, wherein the token is received in the login response. In some of these embodiments, the login request includes a username and password associated with a user of the 5GMS AA, and the login response also includes a user identifier (uid) corresponding to the username. In this case, the uid is sent to the 5GMS client together with the token.
[0117] In some embodiments, the token is associated with a validity period, and the exemplary method may further include the operation of block 1040, wherein associated with the expiration of the validity period, the 5GMS AA 200 may obtain from the ASP 700 an updated token indicating that the 5GMS AA is authorized to invoke or activate the dynamic policy. In this case, the updated token is associated with the updated validity period. In some of these embodiments, the exemplary method may further include the operation of block 1050, wherein the 5GMS AA 200 may send the updated token to the 5GMS client 300.
[0118] In some embodiments, the exemplary method may also include the operation of block 1060, wherein the 5GMS AA 200 may send or receive data via the communication network according to the dynamic policy during the media session between the 5GMS AA and the ASP. This may be done, for example, after the dynamic policy has been activated. In some embodiments, the data is received via Dynamic Adaptive Streaming over HTTP (DASH) or HTTP Live Streaming (HLS).
[0119] also, Fig.11 An exemplary method (e.g., process) for a 5GMS client 300 hosted by a UE operating in a communication network (e.g., NG-RAN, 5GC, etc.) according to various embodiments of the present disclosure is shown. For example, Fig.11 The exemplary method shown in can be performed by a 5GMS client (or a UE hosting a 5GMS client), for example, as described elsewhere in this document.
[0120] The exemplary method may include the operation of block 1110, wherein the 5GMS client 300 may receive a token from a 5GMS AA 200 hosted by a UE, the token indicating that the 5GMS AA is authorized to invoke or activate a dynamic policy for resources of a communication network. The dynamic policy is associated with an ASP 700, which is associated with the 5GMS AA 200. The exemplary method may also include the operation of block 1120, wherein the 5GMS client 300 may send the token to a 5GMS AF 500 of the communication network in a request to activate the dynamic policy for the 5GMS AA. The exemplary method may also include the operation of block 1130, wherein the 5GMS client 300 may receive a response from the 5GMS AF 500, the response indicating that the dynamic policy is activated for the 5GMS AA according to the token.
[0121] In some embodiments, the dynamic policy is a QoS policy. In other embodiments, the dynamic policy is a zero rating policy. In some embodiments, the token is received from the 5GMS AA (e.g., in block 1110) and sent by the MSH of the 5GMS client to the 5GMS AF (e.g., in block 1120).
[0122] In some embodiments, the token is received along with a user identifier (uid) corresponding to a username associated with a user of the 5GMS AA (e.g., in block 1110), and the uid is sent along with the token to the 5GMS AF 500 (e.g., in block 1120).
[0123] In some embodiments, the token is associated with a validity period, and the exemplary method may further include the operation of block 1150, wherein associated with the expiration of the validity period, the 5GMS client 300 may receive from the 5GMS AA 200 an updated token indicating that the 5GMS AA 200 is authorized to invoke or activate the dynamic policy. The updated token is associated with the updated validity period. In some of these embodiments, the exemplary method may further include the operations of blocks 1160-1170, wherein the 5GMS client 300 may send the updated token to the 5GMS AF 500 in a request to activate the dynamic policy for the 5GMS AA, and receive a response from the 5GMS AF indicating that the dynamic policy is activated for the 5GMS AA 200 according to the updated token.
[0124] In some embodiments, the exemplary method may also include the operation of block 1140, wherein the 5GMS client may send or receive data with a 5GMS application server (AS) via a communication network according to a dynamic policy. The data is associated with a media session between the 5GMS AA and the ASP. This may be done, for example, after the dynamic policy has been activated. In some embodiments, the data may be received via DASH or HLS.
[0125] also, Fig.12 An exemplary method (e.g., process) for a 5GMS AF 500 associated with a communication network (e.g., 5GC, etc.) according to various embodiments of the present disclosure is shown. For example, Fig.12 The exemplary method shown in can be performed by, for example, a 5GMS AF (or a network node or computing platform hosting a 5GMS AF) as described elsewhere in this document.
[0126] The exemplary method may include the operation of box 1220, wherein the 5GMS AF 500 may receive a token from a 5GMS client 300 hosted by a UE operating in a communication network, the token indicating that the 5GMS AA 200 hosted by the UE is authorized to invoke or activate a dynamic policy for resources of the communication network. The dynamic policy is associated with an ASP 700, which is associated with the 5GMS AA, and the token is received in a request to activate the dynamic policy for the 5GMS AA. The exemplary method may include the operation of box 1230, wherein the 5GMS AF 500 may send a response to the 5GMS client indicating that the dynamic policy is activated based on determining that the token is valid.
[0127] In some embodiments, the dynamic policy is a QoS policy. In other embodiments, the dynamic policy is a zero-rating policy.
[0128] In some embodiments, the exemplary method may further include the operation of block 1210, wherein the 5GMS AF 500 may receive another token from the ASP 700 indicating that the 5GMS AA is authorized to invoke or activate the dynamic policy. In this case, determining that the token is valid in block 1230 includes the operation of sub-block 1231, wherein the 5GMS AF 500 may verify that the token received from the 5GMS AA 200 matches the other token received from the ASP. In some of these embodiments, the other token includes a validity period, and determining that the token is valid in block 1230 includes the operation of sub-block 1232, wherein the 5GMS AF may verify that the token was received from the 5GMS AA before the validity period expired. Figure 8 Examples of these embodiments are shown.
[0129] In some variations, the exemplary method may also include the operation of box 1270, wherein the 5GMS AF 500 may receive another updated token from the ASP 700 indicating that the 5GMS is authorized to invoke or activate the dynamic policy. The updated another token is associated with the updated validity period. In some other variations, the exemplary method may also include the operations of boxes 1280-1290, wherein the 5GMS AF 500 may then receive the updated token from the 5GMS client in a request to activate the dynamic policy for the 5GMS AA, and based on determining that the updated token is valid, send a response to the 5GMS client indicating that the dynamic policy is activated. The updated token is associated with the updated validity period.
[0130] In other embodiments, determining that the token is valid in block 1230 includes operations of sub-blocks 1233-1234, where the 5GMS AF 500 may send the token to the ASP 700, and receive a response from the ASP indicating that the 5GMS AA 200 is authorized to activate the dynamic policy. In some embodiments, the token is received from the 5GMS client 300 (e.g., in block 1220) along with a user identifier (uid) corresponding to a user name associated with a user of the 5GMS AA, and the token is sent to the ASP along with the uid (e.g., in sub-block 1233). Fig. 9 Examples of these embodiments are shown.
[0131] In some embodiments, the exemplary method may further include operations of blocks 1240-1250, where, based on determining (e.g., in block 1230) that the token is valid, the 5GMS AF may send a request to activate the dynamic policy to the PCF of the communication network, and receive a response indicating that the dynamic policy is activated from the PCF 400. The response is sent to the 5GMS client based on the response from the PCF 400 (e.g., in block 1260).
[0132] also, Fig.13 An exemplary method (e.g., process) for an ASP 700 associated with a 5GMS AA hosted by a UE operating in a communication network according to various embodiments of the present disclosure is shown. For example, Fig.13 The exemplary methods shown in can be performed by an ASP (or a network node or computing platform hosting an ASP) such as described elsewhere herein.
[0133] The exemplary method may include the operation of block 1310, wherein the ASP 700 may provide a token to the 5GMS AA 200, the token indicating that the 5GMS AA 200 is authorized to invoke or activate a dynamic policy for resources of the communication network, wherein the dynamic policy is associated with the ASP 700. In some embodiments, the dynamic policy is a QoS policy. In other embodiments, the dynamic policy is a zero-rating policy.
[0134] In some embodiments, providing the token in block 1310 includes operations of sub-block 1311, wherein ASP 700 may receive a login request from 5GMS AA 200, and send a login response to 5GMS AA, wherein the token is sent in the login response. In some of these embodiments, the login request includes a username and password associated with a user of the 5GMS AA, the login response also includes a user identifier (uid) corresponding to the username, and the uid is sent to the 5GMS client together with the token.
[0135] In some embodiments, the token is associated with a validity period, and the exemplary method may also include the operation of block 1380, wherein, associated with the expiration of the validity period, the ASP 700 may provide an updated token indicating that the 5GMS AA 200 is authorized to invoke or activate the dynamic policy to the 5GMS AA 200. The updated token is associated with an updated validity period.
[0136] In some embodiments, the exemplary method may also include the operations of blocks 1320-1330 and 1350. In block 1320, the ASP 700 may receive another token from a 5GMS AF 500 associated with the communication network indicating that the 5GMS AA 200 is authorized to invoke or activate the dynamic policy, thereby sending the token to the ASP. In block 1330, the ASP 700 may verify that the other token received from the 5GMS AF 500 matches the token provided to the 5GMS AA. In block 1350, the ASP may send a response to the 5GMS AF indicating that the 5GMS AA 200 is authorized to activate the dynamic policy. Figure 8 Examples of these embodiments are shown.
[0137] In some of these embodiments, the token is associated with a validity period, and the exemplary method may also include the operation of block 1340, wherein the ASP 700 may verify that another token is received from the 5GMS AF before the validity period expires. In other words, sending the response in block 1350 may also be based on the verification in block 1340.
[0138] In other embodiments, the exemplary method may also include the operation of box 1360, wherein the ASP 700 may send a token to a 5GMS AF 500 associated with the communication network. Fig. 9 Examples of these embodiments are shown. In some of these embodiments, the token is associated with a validity period, and the exemplary method may also include the operation of block 1390, wherein associated with the expiration of the validity period, the ASP 700 may send an updated token to the 5GMS AF indicating that the 5GMS is authorized to invoke or activate the dynamic policy. The updated token is associated with an updated validity period.
[0139] In some embodiments, the exemplary method may also include the operation of box 1370, wherein ASP 700 may send or receive data via the communication network according to the dynamic policy during the media session between 5GMS AA 200 and ASP 700.
[0140] Although various embodiments are described above in terms of methods, apparatuses, devices, computer-readable media, and receivers, those skilled in the art will readily appreciate that such methods may be embodied in various combinations of hardware and software in various systems, communication devices, computing devices, control devices, apparatuses, non-transitory computer-readable media, and the like.
[0141] Fig.14 An example of a communication system 1400 according to some embodiments is shown. In this example, the communication system 1400 includes a telecommunications network 1402, which includes an access network 1404 (e.g., a radio access network (RAN)) and a core network 1406 (which includes one or more core network nodes 1408). The access network 1404 includes one or more access network nodes, such as network nodes 1410a and 1410b (one or more of which may be generally referred to as network nodes 1410), or any other similar third generation partnership project (3GPP) access node or non-3GPP access point. The network node 1410 facilitates direct or indirect connection of user equipment (UE), such as connecting UE 1412a, 1412b, 1412c, and 1412d (one or more of which may be generally referred to as UE 1412) to the core network 1406 via one or more wireless connections.
[0142] Example wireless communications over wireless connections include sending and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for transmitting information without the use of wires, cables, or other material conductors. In addition, in different embodiments, the communication system 1400 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that can facilitate or participate in the communication of data and / or signals (whether via a wired connection or a wireless connection). The communication system 1400 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar types of systems.
[0143] UE 1412 may be any of a variety of communication devices, including wireless devices that are arranged, configured and / or operable to wirelessly communicate with network node 1410 and other communication devices. Similarly, network node 1410 is arranged, capable, configured and / or operable to communicate directly or indirectly with UE 1412 and / or other network nodes or devices in telecommunication network 1402 to enable and / or provide network access (e.g., wireless network access) and / or perform other functions (e.g., management) in telecommunication network 1402.
[0144] In the depicted example, the core network 1406 connects the network node 1410 to one or more hosts, such as the host 1416. These connections may be direct connections, or indirect connections via one or more intermediate networks or devices. In other examples, the network node may be directly coupled to the host. The core network 1406 includes one or more core network nodes (e.g., core network node 1408) composed of hardware and software components. The features of these components may be substantially similar to those described for the UE, network node, and / or host, so that their description is generally applicable to the corresponding components of the core network node 1408. The example core network node includes one or more functions of: a mobile switching center (MSC), a mobility management entity (MME), a home subscriber server (HSS), an access and mobility management function (AMF), a session management function (SMF), an authentication server function (AUSF), a subscription identifier de-hiding function (SIDF), a unified data management (UDM), a security edge protection agent (SEPP), a network open function (NEF), and / or a user plane function (UPF).
[0145] The host 1416 may be under the ownership or control of a service provider other than the operator or provider of the access network 1404 and / or the telecommunications network 1402, and may be operated by or on behalf of the service provider. The host 1416 may host various applications to provide one or more services. Examples of such applications include real-time and pre-recorded audio / video content, data collection services (e.g., obtaining and compiling data of various environmental conditions detected by multiple UEs), analysis functions, social media, functions for controlling or otherwise interacting with remote devices, functions for alarm and monitoring centers, or any other such functions performed by a server.
[0146] Overall, Fig.14 The communication system 1400 enables connections between UEs, network nodes, and hosts. In this sense, the communication system can be configured to operate according to predefined rules or procedures, such as specific standards, including but 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 standards (e.g., 6G); Wireless Local Area Network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard (WiFi); and / or any other suitable wireless communication standards, such as 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.
[0147] In some examples, telecommunication network 1402 is a cellular network implementing 3GPP standardized features. Thus, telecommunication network 1402 can support network slicing to provide different logical networks to different devices connected to telecommunication network 1402. For example, telecommunication network 1402 can provide ultra-reliable low-latency communication (URLLC) services to some UEs while providing enhanced mobile broadband (eMBB) services to other UEs, and / or provide massive machine type communication (mMTC) / massive IoT services to other UEs.
[0148] In some examples, UE 1412 is configured to send and / or receive information without direct human interaction. For example, the UE may be designed to send information to access network 1404 on a predetermined schedule when triggered by an internal or external event or in response to a request from access network 1404. Additionally, the UE may be configured to operate in a single RAT or multi-RAT or multi-standard mode. For example, the UE may operate using any one or a combination of Wi-Fi, NR (New Radio), and LTE, i.e., configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved UMTS Terrestrial Radio Access Network) New Radio-Dual Connectivity (EN-DC).
[0149] In this example, the hub 1414 communicates with the access network 1404 to facilitate indirect communication between one or more UEs (e.g., UE 1412c and / or 1412d) and a network node (e.g., network node 1410b). In some examples, the hub 1414 may be a controller, a router, a content source and analysis, or any other communication device described herein with respect to the UE. For example, the hub 1414 may be a broadband router that enables the UE to access the core network 1406. As another example, the hub 1414 may be a controller that sends commands or instructions to one or more actuators in the UE. The commands or instructions may be received from the UE, the network node 1410, or received by an executable code, a script, a process, or other instructions in the hub 1414. As another example, the hub 1414 may be a data collector that acts as a temporary storage device for UE data, and in some embodiments, analysis or other processing of the data may be performed. As another example, the hub 1414 may be a content source. For example, for a UE that is a VR headset, display, speaker, or other media delivery device, the hub 1414 can obtain VR assets, video, audio, or other media or data related to the sensory information via the network node, and then the hub 1414 provides it to the UE directly, after performing local processing, and / or after adding additional local content. In another example, the hub 1414 acts as a proxy server or orchestrator for the UE, especially when one or more UEs are low-energy IoT devices.
[0150] Hub 1414 can have constant / persistent or intermittent connection with network node 1410b. Hub 1414 can also allow different communication schemes and / or scheduling between hub 1414 and UE (e.g., UE 1412c and / or 1412d) and hub 1414 and core network 1406. In other examples, hub 1414 is connected to core network 1406 and / or one or more UE via wired connection. In addition, hub 1414 can be configured to be connected to M2M service provider and / or connected to another UE via direct connection through access network 1404. In some scenarios, UE can establish wireless connection with network node 1410, while still connected via hub 1414 by wired or wireless connection. In some embodiments, hub 1414 can be a dedicated hub, that is, its main function is to route communication from network node 1410b to UE / from UE to network node 1410b. In other embodiments, the hub 1414 may be a non-dedicated hub, that is, a device that is operable to route communications between UEs and the network node 1410b, but is also capable of operating as a communications origin and / or endpoint for a particular data channel.
[0151] In various embodiments, the host 1416 or core network node 1408 may implement an application function (AF) or application server (AS) associated with the communication system or network 1400. In other words, the AF or AS may be located in or coupled to the core network 1406. Such an AF or AS may be configured to perform operations corresponding to the specific exemplary methods described above. Additionally, the UE 1412 may be configured to perform the operations described above as being performed by a 5GMS client (uplink or downlink) and a 5GMS-aware application (AA).
[0152] Fig.15 UE 1500 according to some embodiments is shown. Fig.14 The UEs 1412a and 1412b discussed may be implemented in conjunction with Figures 3 to 9 The functions of the UE 1500 discussed herein may correspond to those in conjunction with Fig.15UE 1500 discussed. As used herein, UE refers to a device capable of, configured, arranged and / or operable to wirelessly communicate with a network node and / or other UEs. Examples of UEs include, but are not limited to, smart phones, mobile phones, cellular phones, voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, game consoles or devices, music storage devices, playback devices, wearable terminal devices, wireless endpoints, mobile stations, tablet computers, laptop computers, laptop embedded devices (LEEs), laptop mounted devices (LMEs), smart devices, wireless client equipment (CPEs), vehicle-mounted or vehicle-mounted embedded / integrated wireless devices, etc. Other examples include any UE identified by the Third Generation Partnership Project (3GPP), including narrowband Internet of Things (NB-IoT) UEs, machine type communications (MTC) UEs, and / or enhanced MTC (eMTC) UEs.
[0153] The UE may support device-to-device (D2D) communications, for example, by implementing 3GPP standards for sidelink communications, dedicated short-range communications (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 associated device. Rather, a UE may represent a device that is intended to be sold to or operated by a human user but may not be, or may not initially be, associated with a particular human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended to be sold to or operated by an end user but may be associated with or operated for the benefit of a user (e.g., a smart power meter).
[0154] UE 1500 includes a processing circuit 1502, which is operatively coupled to an input / output interface 1506, a power supply 1508, a memory 1510, a communication interface 1512, and / or any other components or any combination thereof via a bus 1504. Some UEs may utilize Fig.15 All or a subset of the components shown in . The level of integration between components may vary depending on the UE. In addition, some UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.
[0155] The processing circuit 1502 is configured to process instructions and data, and may be configured to implement any sequential state machine operable to execute instructions stored as a machine-readable computer program in the memory 1510. The processing circuit 1502 may be implemented as one or more hardware-implemented state machines (e.g., using discrete logic, field programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), etc.); programmable logic and appropriate firmware; one or more stored computer programs, general-purpose processors (e.g., microprocessors or digital signal processors (DSPs)) and appropriate software; or any combination of the above. For example, the processing circuit 1502 may include multiple central processing units (CPUs).
[0156] In this example, the input / output interface 1506 can be configured to provide one or more interfaces to an input device, an output device, or one or more input and / or output devices. Examples of output devices include speakers, sound cards, video cards, displays, monitors, printers, actuators, transmitters, smart cards, another output device, or any combination thereof. An input device can allow a user to capture information into the UE 1500. Examples of input devices include touch-sensitive displays or presence-sensitive displays, cameras (e.g., digital cameras, digital video cameras, web cameras, etc.), microphones, sensors, mice, trackballs, direction pads, trackpads, rollers, smart cards, etc. The presence-sensitive display can include a capacitive or resistive touch sensor to sense input from a user. The sensor can be, for example, 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 can use an interface port of the same type as an input device. For example, a universal serial bus (USB) port can be used to provide input devices and output devices.
[0157] In some embodiments, the power supply 1508 is configured as a battery or a battery pack. Other types of power supplies may be used, such as an external power supply (e.g., a power outlet), a photovoltaic device, or a battery. The power supply 1508 may also include a power supply circuit for transmitting power from the power supply 1508 itself and / or an external power supply to various parts of the UE 1500 via an input circuit or interface (e.g., a power cord). The transmitted power may be used, for example, to charge the power supply 1508. The power supply circuit may perform any formatting, conversion, or other modification of the power from the power supply 1508 to make the power suitable for the corresponding components of the UE 1500 to which the power is provided.
[0158] The memory 1510 may be or be configured to include a memory such as a random access memory (RAM), a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a magnetic disk, an optical disk, a hard disk, a removable cassette, a flash drive, etc. In one example, the memory 1510 includes one or more application programs 1514 (e.g., an operating system, a web browser application, a widget, a widget engine, or other application) and corresponding data 1516. The memory 1510 may store any one of a variety of operating systems or a combination of operating systems for use by the UE 1500.
[0159] The memory 1510 may be configured to include a plurality of physical drive units, such as a redundant array of independent disks (RAID), a flash memory, a USB flash drive, an external hard drive, a thumb drive, a pen drive, a key drive, a high-density digital versatile disc (HD-DVD) optical drive, an internal hard drive, a Blu-ray optical drive, a holographic digital data storage (HDDS) optical drive, an external mini dual in-line memory module (DIMM), a synchronous dynamic random access memory (SDRAM), an external micro-DIMM SDRAM, a smart card memory (e.g., a tamper-proof module in the form of a universal integrated circuit card (UICC), including one or more subscriber identity modules (SIMs), such as USIM and / or ISIM), other memories, or any combination thereof. The UICC may be, for example, an embedded UICC (eUICC), an integrated UICC (iUICC), or a removable UICC, commonly referred to as a “SIM card”. The memory 1510 may allow the UE 1500 to access instructions, applications, etc. stored on a temporary or non-temporary storage medium to offload data or upload data. An article of manufacture, such as utilizing a communication system, may be tangibly embodied as or in memory 1510, which may be or include a device-readable storage medium.
[0160] The processing circuit 1502 may be configured to communicate with an access network or other network using a communication interface 1512. The communication interface 1512 may include one or more communication subsystems and may include an antenna 1522 or be communicatively coupled to the antenna 1522. The communication interface 1512 may include one or more transceivers for communication (e.g., 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 1518 and / or a receiver 1520 suitable for providing network communications (e.g., optical, electrical, frequency allocation, etc.). In addition, the transmitter 1518 and the receiver 1520 may be coupled to one or more antennas (e.g., antenna 1522), and may share circuit components, software, or firmware, or may be implemented separately instead.
[0161] In the illustrated embodiment, the communication functionality of the communication interface 1512 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communication such as Bluetooth, near field communication, location-based communication such as using a global positioning system (GPS) to determine location, another similar communication functionality, or any combination thereof. Communication may be implemented according to one or more communication protocols and / or standards, such as IEEE 802.11, code division multiple 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 network (SONET), asynchronous transfer mode (ATM), QUIC, hypertext transfer protocol (HTTP), etc.
[0162] Regardless of the type of sensor, the UE may provide an output of the data captured by its sensor via a wireless connection to a network node through its communication interface 1512. The data captured by the UE's sensor may be transmitted via another UE via a wireless connection to a network node. The output may be periodic (e.g., every 15 minutes if it reports the sensed temperature), random (e.g., to balance the reporting load from multiple sensors), in response to a trigger event (e.g., sending an alarm when humidity is detected), in response to a request (e.g., a user-initiated request), or a continuous stream (e.g., a live video feed of a patient).
[0163] As another example, the UE includes an actuator, motor, or switch associated with a communication interface that is configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input, the state of the actuator, motor, or switch can change. For example, the UE can include a motor that adjusts a control surface or rotor of a drone in flight based on the received input, or controls a robotic arm performing a medical procedure based on the received input.
[0164] When in the form of an Internet of Things (IoT) device, a UE may be a device for one or more application areas including, but not limited to, urban wearable technology, extended industry applications, and healthcare. Non-limiting examples of such IoT devices are devices that are or are embedded in: a connected refrigerator or freezer, a television, connected lighting, an electric meter, a robotic 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 / humidity sensor, an electric door lock, a connected doorbell, an air conditioning system such as 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 device for tactile enhancement or sensory enhancement, a sprinkler, an animal or item tracking device, a sensor for monitoring plants or animals, an industrial robot, an unmanned aerial vehicle (UAV), and any kind of medical device such as a heart rate monitor or a teleoperated surgical robot. A UE in the form of an IoT device includes circuits and / or software related to the intended application of the IoT device and, for example, software for Fig.15 Other components described with respect to UE 1500 shown in FIG.
[0165] As yet another specific example, in an IoT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements and sends the results of such monitoring and / or measurements to another UE and / or a network node. In this case, the UE may be an M2M device, which may be referred to as an MTC device in the 3GPP context. As a specific example, a UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle (e.g., a car, bus, truck), a ship, and an airplane, or other device that is capable of monitoring and / or reporting its operating status or other functions associated with its operation.
[0166] In practice, any number of UEs may be used together for a single use case. For example, a first UE may be or be integrated into a drone and provide the drone's speed information (obtained via a speed sensor) to a second UE that is a remote controller for 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 speed of the drone. The first UE and / or the second UE may also include multiple of the functions described above. For example, a UE may include a sensor and an actuator and handle data communications for both the speed sensor and the actuator.
[0167] In various embodiments, UE 1500 may be configured to perform the operations described above as being performed by a 5GMS client (uplink or downlink) and a 5GMS Aware Application (AA). UE 1500 may particularly implement the Figures 3 to 9 Functionality of the UE discussed.
[0168] Fig.16 A network node 1600 according to some embodiments is shown. As used herein, a network node refers to a device capable of, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or other network nodes or devices in a telecommunications 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 Node Bs (gNBs)).
[0169] Base stations may be classified based on the amount of coverage they provide (or in other words, their transmit power class), and may therefore be referred to as femto base stations, pico base stations, micro base stations, or macro base stations, depending on the amount of coverage provided. A base station may be a relay node or a relay donor node that controls a relay. A network node may also include one or more (or all) parts of a distributed radio base station (e.g., a centralized digital unit and / or a remote radio unit (RRU), sometimes referred to as a remote radio head (RRH)). Such a remote radio unit may or may not be integrated with an antenna as an antenna-integrated radio. Portions of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).
[0170] Other examples of network nodes include a multi-transmission point (multi-TRP) 5G access node, a multi-standard radio MSR device (such as an MSR BS), a network controller such as a radio network controller (RNC) or a base station controller (BSC), a base transceiver station (BTS), a transmission point, a transmission node, a multi-cell / multicast coordination entity (MCE), an operation and maintenance (O&M) node, an operation support system (OSS) node, a self-organizing network (SON) node, a positioning node (e.g., an evolved serving mobile positioning center (E-SMLC)) and / or a minimization of drive tests (MDT).
[0171] The network node 1600 includes a processing circuit 1602, a memory 1604, a communication interface 1606, and a power supply 1608. The network node 1600 may include multiple physically separated components (e.g., a node B component and an RNC component, or a BTS component and a BSC component, etc.), each of which may have its own corresponding components. In certain scenarios where the network node 1600 includes multiple separate components (e.g., BTS and BSC components), one or more separate components may be shared between multiple network nodes. For example, a single RNC may control multiple node Bs. In such a scenario, in some cases, each unique node B and RNC pair may be considered as a single separate network node. In some embodiments, the network node 1600 may be configured to support multiple radio access technologies (RATs). In such an embodiment, some components may be repeated (e.g., separate memories 1604 for different RATs), while some components may be reused (e.g., the same antenna 1610 may be shared by different RATs). The network node 1600 may also include various sets of example components for different wireless technologies (e.g., GSM, WCDMA, LTE, NR, Wi-Fi, Zigbee, Z-wave, LoRaWAN, radio frequency identification (RFID), or Bluetooth wireless technologies) integrated into the network node 1600. These wireless technologies may be integrated into the same or different chips or chipsets and other components within the network node 1600.
[0172] The processing circuit 1602 may include a combination of one or more of the following operable to provide network node 1600 functionality, alone or in combination with other network node 1600 components (e.g., memory 1604): a microprocessor, a controller, a microcontroller, a central processing unit, a digital signal processor, an application specific integrated circuit, a field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic.
[0173] In some embodiments, processing circuitry 1602 includes a system on a chip (SOC). In some embodiments, processing circuitry 1602 includes one or more of radio frequency (RF) transceiver circuitry 1612 and baseband processing circuitry 1614. In some embodiments, radio frequency (RF) transceiver circuitry 1612 and baseband processing circuitry 1614 may be on separate chips (or chipsets), boards, or units (e.g., a radio unit and a digital unit). In alternative embodiments, some or all of RF transceiver circuitry 1612 and baseband processing circuitry 1614 may be on the same chip or chipset, board, or unit.
[0174] Memory 1604 may include any form of volatile or non-volatile computer-readable memory, including, but not limited to, permanent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (e.g., hard disk), removable storage media (e.g., flash drive, compact disk (CD) or digital video disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable storage device that stores information, data and / or instructions that can be used by processing circuit 1602. Memory 1604 may store any suitable instructions, data or information, including computer programs, software, applications (including one or more of logic, rules, code, tables, etc.) and / or other instructions that can be executed by processing circuit 1602 and utilized by network node 1600. Memory 1604 may be used to store any calculations performed by processing circuit 1602 and / or any data received via communication interface 1606. In some embodiments, processing circuit 1602 and memory 1604 are integrated.
[0175] The communication interface 1606 is used for the wired or wireless communication of signaling and / or data between network nodes, access networks and / or UEs. As shown, the communication interface 1606 includes a port / terminal 1616 to send and receive data from the network, for example, via a wired connection. The communication interface 1606 also includes a radio front-end circuit 1618 that can be coupled to an antenna 1610 or as a part of an antenna 1610 in some embodiments. The radio front-end circuit 1618 includes a filter 1620 and an amplifier 1622. The radio front-end circuit 1618 can be connected to the antenna 1610 and the processing circuit 1602. The radio front-end circuit 1618 can be configured to adjust the signal transmitted between the antenna 1610 and the processing circuit 1602. The radio front-end circuit 1618 can receive digital data that will be sent to other network nodes or UEs via a wireless connection. The radio front-end circuit 1618 can use a combination of a filter 1620 and / or an amplifier 1622 to convert digital data into a radio signal with appropriate channel and bandwidth parameters. The radio signal can then be transmitted via the antenna 1610. Similarly, when receiving data, antenna 1610 may collect radio signals, which may then be converted into digital data by radio front end circuitry 1618. The digital data may be passed to processing circuitry 1602. In other embodiments, the communication interface may include different components and / or different combinations of components.
[0176] In some alternative embodiments, the network node 1600 does not include a separate radio front end circuit 1618, but rather, the processing circuit 1602 includes the radio front end circuit and is connected to the antenna 1610. Similarly, in some embodiments, all or part of the RF transceiver circuit 1612 is part of the communication interface 1606. In other embodiments, the communication interface 1606 includes one or more ports or terminals 1616, the radio front end circuit 1618, and the RF transceiver circuit 1612 as part of a radio unit (not shown), and the communication interface 1606 communicates with the baseband processing circuit 1614, which is part of the digital unit (not shown).
[0177] Antenna 1610 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals. Antenna 1610 may be coupled to radio front end circuit 1618 and may be any type of antenna capable of wirelessly sending and receiving data and / or signals. In some embodiments, antenna 1610 is separate from network node 1600 and may be connected to network node 1600 via an interface or port.
[0178] Antenna 1610, communication interface 1606 and / or processing circuit 1602 may be configured to perform any receiving operation and / or certain obtaining operations described herein as being performed by a network node. Any information, data and / or signal may be received from a UE, another network node and / or any other network device. Similarly, antenna 1610, communication interface 1606 and / or processing circuit 1602 may be configured to perform any sending operation described herein as being performed by a network node. Any information, data and / or signal may be sent to a UE, another network node and / or any other network device.
[0179] The power supply 1608 provides power to the various components of the network node 1600 in a form suitable for the respective components (e.g., at the voltage and current levels required by each respective component). The power supply 1608 may also include or be coupled to a power management circuit to provide power to the components of the network node 1600 for performing the functions described herein. For example, the network node 1600 may be connected to an external power source (e.g., a power grid, a power outlet) via an input circuit or interface (e.g., a cable), whereby the external power source provides power to the power circuit of the power supply 1608. As yet another example, the power supply 1608 may include a power source in the form of a battery or battery pack connected to or integrated into the power circuit. If the external power source fails, the battery may provide backup power.
[0180] An embodiment of the network node 1600 may include Fig.16 Additional components beyond those shown that are used to provide certain aspects of the functionality of the network node, including any functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 1600 may include a user interface device to allow information to be input into the network node 1600 and to allow information to be output from the network node 1600. This may allow a user to perform diagnostics, maintenance, repair, and other management functions for the network node 1600.
[0181] In various embodiments, the network node 1600 may be configured to perform operations performed by the network node, network function (NF), application function (AF), and application server (AS) in the exemplary methods or processes described above.
[0182] Fig.17 is a block diagram of a host 1700 according to various aspects described herein, and the host 1700 may be Fig.14 1416 of the embodiment of the host. As used herein, the host 1700 can be or include various combinations of hardware and / or software, including processing resources in a stand-alone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, a container, or a server farm. The host 1700 can provide one or more services to one or more UEs.
[0183] Host 1700 includes processing circuitry 1702, which is operatively coupled to input / output interface 1706, network interface 1708, power supply 1710, and memory 1712 via bus 1704. Other components may be included in other embodiments. The features of these components may be substantially similar to those described with respect to previous figures (e.g., Fig.15 and 16 ) so that its description is generally applicable to corresponding components of host 1700.
[0184] The memory 1712 may include one or more computer programs, including one or more host applications 1714 and data 1716, which may include user data, such as data generated by the UE for the host 1700 or data generated by the host 1700 for the UE. An embodiment of the host 1700 may use only a subset or all of the components shown. The host application 1714 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding of multiple different classes, types or implementations of UEs (e.g., mobile phones, desktop computers, wearable display systems, head-up display systems). The host application 1714 may also provide user authentication and authorization checks, and may periodically report health status, routing, and content availability to a central node (e.g., a device in a core network or on the edge). Thus, the host 1700 can select and / or indicate to the UE a different host for the over-the-top service. The host application 1714 can support various protocols, such as HTTP Live Streaming (HLS) protocol, Real-time Messaging Protocol (RTMP), Real-time Streaming Protocol (RTSP), HTTP Dynamic Adaptive Streaming (MPEG-DASH), etc.
[0185] In various embodiments, host 1700 may implement an application function (AF) or an application server (AS) associated with a communication system or network. Such an AF or AS may be configured to perform operations corresponding to the specific exemplary methods described above.
[0186] Fig.18It is a block diagram showing a virtualized environment 1800 in which the functions implemented by some embodiments can be virtualized. In the current context, virtualization means creating a virtual version of a device or equipment, which may include a virtualized hardware platform, storage device, and networking resources. As used herein, virtualization can be applied to any device or component thereof described herein, and relates to an implementation in which at least a portion of the functions are implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components performed by one or more virtual machines (VMs), which are implemented in one or more virtual environments 1800 hosted by one or more hardware nodes (e.g., hardware computing devices operated as network nodes, UEs, core network nodes, or hosts). In addition, in embodiments in which a virtual node does not require a radio connection (e.g., a core network node or host), the node may be fully virtualized.
[0187] Application 1802 (which may alternatively be referred to as a software instance, a virtual appliance, a network function, a virtual node, a virtual network function, etc.) runs in a virtualized environment 1800 to implement certain features, functions and / or benefits of some embodiments disclosed herein.
[0188] The hardware 1804 includes processing circuitry, memory storing software and / or instructions executable by the hardware processing circuitry, and / or other hardware devices as described herein, such as network interfaces, input / output interfaces, etc. The software may be executed by the processing circuitry to instantiate one or more virtualization layers 1806 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide virtual machines 1808a and 1808b (one or more of which may be generally referred to as virtual machines 1808), and / or perform any of the functions, features, and / or benefits described for some embodiments described herein. The virtualization layer 1806 may present a virtual operating platform that appears to be networked hardware to the virtual machines 1808.
[0189] The virtual machine 1808 includes virtual processing, virtual memory, virtual network or interface, and virtual storage, and can be run by a corresponding virtualization layer 1806. Different embodiments of instances of virtual devices 1802 can be implemented on one or more virtual machines 1808 and can be implemented in different ways. In some contexts, the virtualization of hardware is referred to as network function virtualization (NFV). NFV can be used to integrate many network device types onto industry-standard high-volume server hardware, physical switches, and physical storage that can be located in data centers and customer premises equipment.
[0190] In the context of NFV, a virtual machine 1808 may be a software implementation of a physical machine that runs a program as if the program were executed on a physical, non-virtualized machine. Each virtual machine 1808 and the portion of the hardware 1804 that executes the virtual machine (hardware dedicated to the virtual machine and / or hardware shared by the virtual machine with other virtual machines) form a separate virtual network element. Still in the context of NFV, a virtual network function is responsible for handling a specific network function running in one or more virtual machines 1808 on the hardware 1804 and corresponds to an application 1802.
[0191] Hardware 1804 can be implemented in a stand-alone network node with general or specific components. Hardware 1804 can implement some functions via virtualization. Alternatively, hardware 1804 can be part of a larger hardware cluster (e.g., such as in a data center or CPE), where many hardware nodes work together and are managed via management and orchestration 1810, which, among other items, oversees the life cycle management of application 1802. In some embodiments, hardware 1804 is coupled to one or more radio units, each of which includes one or more transmitters and one or more receivers that can be coupled to one or more antennas. The radio unit can communicate directly with other hardware nodes via one or more appropriate network interfaces, and can be used in combination with virtual components to provide a virtual node with radio capabilities, such as a radio access node or base station. In some embodiments, a control system 1812 can be used to provide some signaling, which can be used alternatively for communication between hardware nodes and radio units.
[0192] In various embodiments, the virtualization environment 1800 may be configured to host the various network functions (NFs), application functions (AFs), and application servers (ASs) described above. In other words, these NFs, AFs, and ASs may be implemented in corresponding virtual nodes 1802 based on the underlying hardware 1804. These corresponding virtual nodes 1802 may be configured to perform the various exemplary methods or processes described above.
[0193] Fig.19 A communication diagram is shown in which a host 1902 communicates with a UE 1906 via a network node 1904 over a partially wireless connection according to some embodiments. Fig.19 To describe the UE (eg, Fig.14 UE 1412a and / or Fig.15 UE 1500), network node (e.g. Fig.14 The network node 1410a and / or Fig.16 network nodes 1600) and hosts (e.g. Fig.14 Host 1416 and / or Fig.17 An example implementation of host 1700).
[0194] Similar to the host 1700, an embodiment of the host 1902 includes hardware, such as a communication interface, a processing circuit, and a memory. The host 1902 also includes software that is stored in the host 1902 or accessible by the host 1902 and can be executed by the processing circuit. The software includes a host application that can operate to provide services to a remote user (e.g., a UE 1906 connected via an over-the-top (OTT) connection 1950 extending between the UE 1906 and the host 1902). When providing services to the remote user, the host application can provide user data sent using the OTT connection 1950.
[0195] The network node 1904 includes hardware that enables it to communicate with the host 1902 and the UE 1906. The connection 1960 can be direct or through a core network (such as Fig.14 The core network 1406 of the present invention) and / or one or more other intermediate networks, such as one or more public, private or managed networks. For example, the intermediate network can be a backbone network or the Internet.
[0196] UE 1906 includes hardware and software, which is stored in UE 1906 or accessible by UE 1906 and can be executed by the processing circuit of UE. The software includes a client application, such as a web browser or an operator-specific "application", which is operable to provide services to human or non-human users via UE 1906 with the support of host 1902. In host 1902, the executing host application can communicate with the executing client application via an OTT connection 1950 terminated at UE 1906 and host 1902. When providing services to users, the client application of UE can receive request data from the host application of the host and provide user data in response to the request data. OTT connection 1950 can transmit both request data and user data. The client application of UE can interact with the user to generate user data provided to the host application via OTT connection 1950.
[0197] The OTT connection 1950 may extend via a connection 1960 between the host 1902 and the network node 1904 and via a wireless connection 1970 between the network node 1904 and the UE 1906 to provide connectivity between the host 1902 and the UE 1906. The connection 1960 and the wireless connection 1970 through which the OTT connection 1950 may be provided have been drawn abstractly to illustrate communications between the host 1902 and the UE 1906 via the network node 1904 without explicit reference to any intermediate devices and the precise routing of messages via those devices.
[0198] As an example of sending data via the OTT connection 1950, in step 1908, the host 1902 provides user data, which can be performed by executing a host application. In some embodiments, the user data is associated with a specific human user who interacts with the UE 1906. In other embodiments, the user data is associated with the UE 1906, and the UE 1906 shares the data with the host 1902 without explicit human interaction. In step 1910, the host 1902 initiates a transmission carrying the user data toward the UE 1906. The host 1902 may initiate the transmission in response to a request sent by the UE 1906. The request may be caused by human interaction with the UE 1906 or by the operation of a client application executed on the UE 1906. According to the teachings of the embodiments described throughout the present disclosure, the transmission may be through the network node 1904. Therefore, in step 1912, according to the teachings of the embodiments described throughout the present disclosure, the network node 1904 sends the user data carried in the transmission initiated by the host 1902 to the UE 1906. In step 1914 , UE 1906 receives user data carried in the transmission, which may be performed by a client application executing on UE 1906 that is associated with a host application executed by host 1902 .
[0199] In some examples, UE 1906 executes a client application that provides user data to host 1902. The user data may be provided in response to data received from host 1902. Thus, in step 1916, UE 1906 may provide user data, which may be performed by executing a client application. In providing the user data, the client application may further consider user input received from a user via an input / output interface of UE 1906. Regardless of the specific manner in which the user data is provided, UE 1906 initiates transmission of the user data toward host 1902 via network node 1904 in step 1918. In step 1920, in accordance with the teachings of the embodiments described throughout the present disclosure, network node 1904 receives user data from UE 1906 and initiates transmission of the received user data toward host 1902. In step 1922, host 1902 receives the user data carried in the transmission initiated by UE 1906.
[0200] One or more of the various embodiments improves the performance of OTT services provided to UE 1906 using OTT connection 1950 (wherein wireless connection 1970 forms the final segment). More precisely, embodiments can facilitate authentication and / or authorization of UE applications that attempt to invoke dynamic policies related to resource usage in a communication network (e.g., quality of service (QoS) policies or billing-related policies). Thus, embodiments facilitate enhancing a service level agreement (SLA) between a network operation (e.g., an MNO) and an application service provider (ASP) so that the ASP authorizes application resource usage within the scope of the SLA and prevents resource usage outside of these scopes. For example, embodiments prevent other applications that are not covered by the SLA from using network resources paid for by the ASP, which increases the value of the SLA to the ASP. For example, the ASP may be an OTT service provider.
[0201] In an example scenario, host 1902 may collect and analyze plant status information. As another example, host 1902 may process audio and video data that may have been obtained from UE for creating a map. As another example, host 1902 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, host 1902 may store surveillance videos uploaded by UE. As another example, host 1902 may store or control access to media content such as video, audio, VR, or AR, and host 1902 may broadcast, multicast, or unicast the media content to UE. As other examples, host 1902 may be used for energy pricing, remote control of non-time-critical power loads to balance power generation demand, positioning services, presentation services (e.g., compiling a map based on data collected from a remote device, etc.), or any other function of collecting, obtaining, storing, analyzing, and / or sending data.
[0202] In some examples, a measurement process may be provided for the purpose of monitoring data rates, delays, and other factors on which one or more embodiments are improved. In response to changes in the measurement results, there may also be an optional network function for reconfiguring the OTT connection 1950 between the host 1902 and the UE 1906. The measurement process and / or network function for reconfiguring the OTT connection may be implemented in the software and hardware of the host 1902 and / or the UE 1906. In some embodiments, sensors (not shown) may be deployed in other devices through which the OTT connection 1950 passes or associated with such other devices; the sensors may participate in the measurement process by providing the values of the monitored quantities of the above examples or providing the values of other physical quantities from which the software can calculate or estimate the monitored quantities. The reconfiguration of the OTT connection 1950 may include message formats, retransmission settings, preferred routes, etc.; the reconfiguration does not require direct changes to the operation of the network node 1904. Such processes and functions may be known and practiced in the art. In some embodiments, the measurement may involve proprietary UE signaling, which facilitates the host 1902 to measure throughput, propagation time, delay, etc. The measurement can be achieved because the software causes the OTT connection 1950 to be used to send messages, particularly empty or "dummy" messages, during which it monitors propagation times, errors, etc.
[0203] Some general conclusions can be drawn from the above discussion.
[0204] As far as 5GMS AA is concerned, the following points need to be noted:
[0205] In some embodiments, the dynamic policy is a QoS policy. In other embodiments, the dynamic policy is a zero rating policy. In some embodiments, the token is sent to the media session handler (MSH) of the 5G MS client.
[0206] In some embodiments, obtaining the token may include sending a login request to an ASP, and receiving a login response from the ASP, wherein the token is received in the login response. In some of these embodiments, the login request includes a username and password associated with a user of the 5GMS AA, and the login response also includes a user identifier (uid) corresponding to the username. In this case, the uid is sent to the 5GMS client together with the token.
[0207] In some embodiments, the token is associated with a validity period, and these exemplary methods may further include: in association with the expiration of the validity period, obtaining from the ASP an updated token indicating that the 5GMS AA is authorized to invoke or activate the dynamic policy. In this case, the updated token is associated with the updated validity period. In some of these embodiments, these exemplary methods may further include: sending the updated token to the 5GMS client.
[0208] In some embodiments, these exemplary methods may also include: during the media session between the 5GMS AA and the ASP, sending or receiving data via the communication network according to the dynamic policy. This can be done, for example, after the dynamic policy has been activated. In some embodiments, the data is received via Dynamic Adaptive Streaming over HTTP (DASH) or HTTP Live Streaming (HLS). In addition, the token may be sent to the media session handler MSH of the 5GMS client.
[0209] In some embodiments, the token is an identifier indicating that the UE is authorized to invoke or activate a dynamic policy.
[0210] As far as 5GMS client is concerned, the following points need to be noted:
[0211] In some embodiments, the dynamic policy is a QoS policy. In other embodiments, the dynamic policy is a zero rating policy. In some embodiments, the token is received from the 5GMS AA and sent by the MSH of the 5GMS client to the 5GMS AF. In some embodiments, the token is received with a user identifier (uid) corresponding to a user name associated with a user of the 5GMS AA, and the uid is sent to the 5GMS AF together with the token.
[0212] In some embodiments, the token is associated with a validity period, and these exemplary methods may further include: in association with the expiration of the validity period, receiving from the 5GMS AA an updated token indicating that the 5GMS AA is authorized to invoke or activate the dynamic policy. The updated token is associated with the updated validity period. In some of these embodiments, these exemplary methods may further include: in a request to activate the dynamic policy for the 5GMS AA, sending the updated token to the 5GMS AF, and receiving a response from the 5GMS AF indicating that the dynamic policy is activated for the 5GMS AA according to the updated token.
[0213] In some embodiments, these exemplary methods may further include: sending or receiving data with a 5GMS application server (AS) via a communication network according to a dynamic policy. The data is associated with a media session between the 5GMS AA and the ASP. This may be done, for example, after the dynamic policy has been activated. In some embodiments, the data may be received via HTTP DASH or HLS.
[0214] In some embodiments, the token is received from the 5GMS AA and sent by the media session handler MSH of the 5GMS client to the 5GMS AF.
[0215] As far as 5GMS AF is concerned, the following points need to be noted:
[0216] In some embodiments, the dynamic policy is a QoS policy. In other embodiments, the dynamic policy is a zero-rating policy.
[0217] In some embodiments, these exemplary methods may further include: receiving another token from the ASP indicating that the 5GMS AA is authorized to invoke or activate the dynamic policy. In this case, determining that the token is valid includes: verifying that the token received from the 5GMS AA matches the other token received from the ASP. In some of these embodiments, the other token includes a validity period, and determining that the token is valid also includes: verifying that the token is received from the 5GMS AA before the validity period expires.
[0218] In some variations, these exemplary methods may further include: receiving from the ASP another token indicating that the 5GMS is authorized to invoke or activate an update of the dynamic policy. The updated another token is associated with the updated validity period. In some other variations, these exemplary methods may further include: subsequently receiving the updated token from the 5GMS client in a request to activate the dynamic policy for the 5GMS AA, and based on determining that the updated token is valid, sending a response to the 5GMS client indicating that the dynamic policy is activated. The updated token is associated with the updated validity period.
[0219] In other embodiments, determining that the token is valid includes: sending the token to the ASP, and receiving a response from the ASP indicating that the 5GMSAA is authorized to activate the dynamic policy. In some of these embodiments, the token is received from the 5GMS client together with a user identifier (uid) corresponding to a user name associated with a user of the 5GMSAA, and the token is sent to the ASP together with the uid.
[0220] In some embodiments, these exemplary methods may further include: based on determining that the token is valid, sending a request to activate the dynamic policy to a PCF of the communication network, and receiving a response from the PCF indicating that the dynamic policy is activated. The response is sent to the 5GMS client based on the response from the PCF.
[0221] With regard to APS, the following points need to be noted:
[0222] In some embodiments, the dynamic policy is a QoS policy. In other embodiments, the dynamic policy is a zero-rating policy.
[0223] In some embodiments, providing the token may include: receiving a login request from the 5GMS AA, and sending a login response to the 5GMS AA, wherein the token is sent in the login response. In some of these embodiments, the login request includes a username and password associated with a user of the 5GMS AA, the login response also includes a user identifier (uid) corresponding to the username, and the uid is sent to the 5GMS client together with the token.
[0224] In some embodiments, the token is associated with a validity duration, and these exemplary methods may also include: in association with expiration of the validity duration, providing to the 5GMS AA an updated token indicating that the 5GMS AA is authorized to invoke or activate the dynamic policy. The updated token is associated with an updated validity duration.
[0225] In some embodiments, these exemplary methods may further include the following: receiving another token from a 5GMS AF associated with the communication network indicating that the 5GMS AA is authorized to invoke or activate the dynamic policy, thereby sending the token to the ASP; verifying that the other token received from the 5GMS AF matches the token provided to the 5GMS AA; and sending a response to the 5GMS AF indicating that the 5GMS AA is authorized to activate the dynamic policy. In some of these embodiments, the token is associated with a validity period, and these exemplary methods may further include: verifying that the other token is received from the 5GMS AF before the validity period expires.
[0226] In other embodiments, these exemplary methods may further include: sending a token to a 5GMS AF associated with the communication network. In some of these embodiments, the token is associated with a validity period, and these exemplary methods may further include: in association with the expiration of the validity period, sending an updated token to the 5GMS AF indicating that the 5GMS is authorized to invoke or activate the dynamic policy. The updated token is associated with an updated validity period.
[0227] In some embodiments, these exemplary methods may also include: during the media session between the 5GMS AA and the ASP, sending or receiving data via the communication network according to the dynamic policy. This can be done, for example, after the dynamic policy has been activated. In some embodiments, the data can be sent via HTTP DASH or HLS.
[0228] The above merely illustrates the principles of the present disclosure. In view of the teachings herein, various modifications and changes to the described embodiments will be apparent to those skilled in the art. It should therefore be understood that those skilled in the art will be able to design a variety of systems, arrangements, and processes that, although not explicitly shown or described herein, embody the principles of the present disclosure and are therefore within the spirit and scope of the present disclosure. As will be appreciated by those of ordinary skill in the art, the various embodiments may be used together with each other, and may be used interchangeably with each other.
[0229] As used herein, the term "unit" may have its conventional meaning in the field of electronic devices, electrical equipment and / or electronic equipment, and may include, for example, electrical and / or electronic circuits, devices, modules, processors, memories, logical solid-state and / or discrete devices, computer programs or instructions for performing corresponding tasks, processes, calculations, output and / or display functions, etc. as described herein.
[0230] Any appropriate steps, methods, features, functions or benefits disclosed herein may be performed by one or more functional units or modules of one or more virtual devices. Each virtual device may include multiple such functional units. These functional units may be implemented via a processing circuit, which may include one or more microprocessors or microcontrollers, and other digital hardware that may include a digital signal processor (DSP), dedicated digital logic, etc. The processing circuit may be configured to execute program codes stored in a memory, which may include one or more types of memory, such as a read-only memory (ROM), a random access memory (RAM), a cache memory, a flash memory device, an optical storage device, etc. The program code stored in the memory includes program instructions for executing one or more telecommunications and / or data communication protocols and instructions for executing one or more technologies described herein. In some implementations, a processing circuit may be used to cause a corresponding functional unit to perform a corresponding function according to one or more embodiments of the present disclosure.
[0231] As described herein, the device and / or apparatus may be represented by a semiconductor chip, a chipset, or a (hardware) module including such a chip or chipset; however, this does not exclude the possibility that the function of the device or apparatus is not implemented by hardware but is implemented as a software module (e.g., a computer program or computer program product including an executable software code portion for execution or operation on a processor). In addition, the functions of the device or apparatus may be implemented by any combination of hardware and software. The device or apparatus may also be viewed as an assembly of multiple devices and / or apparatuses, whether they are functionally cooperative or independent of each other. In addition, as long as the functions of the device or apparatus are retained, the device and apparatus may be implemented in a distributed manner throughout the system. Such and similar principles are considered to be known to those skilled in the art.
[0232] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as those commonly understood by those of ordinary skill in the art to which the present disclosure belongs. It will be further understood that the terms used herein should be interpreted as having a meaning consistent with their meaning in the context of this specification and the relevant art, and should not be interpreted as an idealized or overly formal meaning, unless explicitly defined as such herein.
[0233] In addition, certain terms used in this disclosure (including the specification and drawings) may be used synonymously in certain circumstances (e.g., "data" and "information"). It should be understood that although these terms (and / or other terms that may be synonymous with each other) may be used synonymously herein, there may be situations where such words may not be intended to be used synonymously. If prior art knowledge is not explicitly incorporated herein by reference above, its entirety is explicitly incorporated herein. All publications cited are incorporated herein by reference in their entirety.
[0234] Examples of the techniques and devices described herein include, but are not limited to, the following examples:
[0235] A1. A method for a 5G Media Stream (5GMS) Aware Application (AA) hosted by a User Equipment (UE) operating in a communication network, the method comprising:
[0236] obtaining a token from an application service provider (ASP) associated with the 5GMS AA, the token indicating that the 5GMS AA is authorized to invoke or activate a dynamic policy for resources of the communication network, wherein the dynamic policy is associated with the ASP; and
[0237] A token is sent to a 5GMS client hosted by the UE, where the 5GMS client is associated with a 5GMS Application Function (AF) of the communication network.
[0238] A2. The method of embodiment A1, wherein the dynamic policy is one of: a quality of service (QoS) policy, or a zero rating policy.
[0239] A3. A method according to any one of embodiments A1-A2, wherein obtaining the token comprises: sending a login request to an ASP, and receiving a login response from the ASP, and wherein the token is received in the login response.
[0240] A4. The method according to embodiment A3, wherein:
[0241] The login request includes a username and password associated with a user of the 5GMS AA;
[0242] The login response also includes a user identifier (uid) corresponding to the username; and
[0243] The uid is sent along with the token to the 5GMS client.
[0244] A5. The method of any one of embodiments A1-A4, wherein:
[0245] The token is associated with a validity period;
[0246] The method further includes: in association with expiration of the validity period, obtaining from the ASP an updated token indicating that the 5GMS AA is authorized to invoke or activate the dynamic policy; and
[0247] The updated token is associated with an updated validity period.
[0248] A6. The method according to embodiment A5 also includes: sending an updated token to the 5GMS client.
[0249] A7. The method according to any one of embodiments A1-A6 also includes: during the media session between the 5GMS AA and the ASP, sending or receiving data via the communication network according to a dynamic strategy.
[0250] A8. The method of embodiment A7, wherein the data is received via Dynamic Adaptive Streaming over HTTP (DASH) or HTTP Live Streaming (HLS).
[0251] A9. A method according to any one of embodiments A1-A8, wherein the token is sent to the media session handler (MSH) of the 5GMS client.
[0252] B1. A method for a 5G Media Stream (5GMS) client hosted by a user equipment (UE) operating in a communication network, the method comprising:
[0253] receiving a token from a 5G Media Stream (5GMS) aware application (AA) hosted by the UE, the token indicating that the 5GMS AA is authorized to invoke or activate a dynamic policy for resources of a communication network, wherein the dynamic policy is associated with an application service provider (ASP) and the ASP is associated with the 5GMS AA;
[0254] sending a token to a 5GMS Application Function (AF) of the communication network in a request to activate a dynamic policy for 5GMS AA; and
[0255] A response is received from the 5GMS AF indicating that the dynamic policy is activated for the 5GMS AA based on the token.
[0256] B2. The method of embodiment B1, wherein the dynamic policy is one of: a quality of service (QoS) policy, or a zero rating policy.
[0257] B3. The method according to any one of embodiments B1-B2, wherein:
[0258] The token is received together with a user identifier (uid) corresponding to a username associated with a user of the 5GMS AA; and
[0259] The uid is sent to the 5GMS AF together with the token.
[0260] B4. The method of any one of embodiments B1-B3, wherein:
[0261] The token is associated with a validity period;
[0262] The method further includes: in association with expiration of the validity time period, receiving from the 5GMS AA an updated token indicating that the 5GMS AA is authorized to invoke or activate the dynamic policy; and
[0263] The updated token is associated with an updated validity period.
[0264] B5. The method according to embodiment B4, further comprising:
[0265] sending the updated token to the 5GMS AF in a request to activate dynamic policy for the 5GMS AA; and
[0266] A response is received from the 5GMS AF indicating that the dynamic policy is activated for the 5GMS AA based on the updated token.
[0267] B6. The method according to any one of embodiments B1-B5 further includes: sending or receiving data with a 5GMS application server (AS) via a communication network according to a dynamic strategy, wherein the data is associated with a media session between the 5GMS AA and the ASP.
[0268] B7. The method of embodiment B6, wherein the data is received via Dynamic Adaptive Streaming over HTTP (DASH) or HTTP Live Streaming (HLS).
[0269] B8. A method according to any one of embodiments B1-B7, wherein the token is received by a media session handler (MSH) of a 5GMS client from a 5GMS AA and sent to the 5GMS AF.
[0270] C1. A method for a 5G Media Stream (5GMS) application function (AF) associated with a communication network, the method comprising:
[0271] Receiving a token from a 5GMS client hosted by a user equipment (UE) operating in a communication network, the token indicating that a 5GMS-aware application (AA) hosted by the UE is authorized to invoke or activate a dynamic policy for resources of the communication network, wherein:
[0272] Dynamic policies are associated with the Application Service Provider (ASP), which is associated with the 5GMS AA, and
[0273] The token is received in a request to activate dynamic policy for 5GMS AA; and
[0274] Based on determining that the token is valid, a response is sent to the 5GMS client indicating that the dynamic policy is activated.
[0275] C2. The method of embodiment C1, wherein the dynamic policy is one of: a quality of service (QoS) policy, or a zero rating policy.
[0276] C3. The method of any one of embodiments C1-C2, wherein:
[0277] The method further includes: receiving from the ASP another token indicating that the 5GMS AA is authorized to invoke or activate the dynamic policy;
[0278] Determining that the token is valid includes verifying that a token received from the 5GMS AA matches another token received from the ASP.
[0279] C4. The method according to embodiment C3, wherein:
[0280] Another token is associated with a validity period; and
[0281] Determining that the token is valid includes: verifying that the token is received from the 5GMS AA before the validity period expires.
[0282] C5. The method according to embodiment C4 also includes: receiving another updated token from the ASP indicating that the 5GMS is authorized to call or activate the dynamic policy, wherein the updated another token is associated with the updated validity period.
[0283] C6. The method according to embodiment C5, further comprising:
[0284] subsequently receiving an updated token from the 5GMS client in a request to activate a dynamic policy for the 5GMS AA, wherein the updated token is associated with an updated validity period; and
[0285] Based on determining that the updated token is valid, a response is sent to the 5GMS client indicating that the dynamic policy is activated.
[0286] C7. The method of any one of embodiments C1-C2, wherein determining that the token is valid comprises:
[0287] Sending a token to the ASP; and
[0288] A response is received from the ASP indicating that the 5GMS AA is authorized to activate the dynamic policy.
[0289] C8. The method of embodiment C7, wherein:
[0290] The token is received from the 5GMS client together with a user identifier (uid) corresponding to a username associated with a user of the 5GMS AA; and
[0291] The token is sent along with the uid to the ASP.
[0292] C9. The method according to any one of embodiments C1-C8, further comprising:
[0293] Based on determining that the token is valid, sending a request to activate the dynamic policy to a policy control function (PCF) of the communication network; and
[0294] receiving a response from the PCF indicating that the dynamic policy is activated,
[0295] Among them, the response is sent to the 5GMS client based on the response from the PCF.
[0296] D1. A method for an application service provider (ASP) of a 5G media stream (5GMS) aware application (AA) hosted by a user equipment (UE) operating in a communication network, the method comprising:
[0297] A token is provided to the 5GMS AA, the token indicating that the 5GMS AA is authorized to invoke or activate a dynamic policy for resources of the communication network, wherein the dynamic policy is associated with the ASP.
[0298] D2. The method of embodiment D1, wherein the dynamic policy is one of: a quality of service (QoS) policy, or a zero rating policy.
[0299] D3. A method according to any one of embodiments D1-D2, wherein providing a token comprises: receiving a login request from a 5GMS AA, and sending a login response to the 5GMS AA, and wherein the token is sent in the login response.
[0300] D4. The method according to embodiment D3, wherein:
[0301] The login request includes a username and password associated with a user of the 5GMS AA;
[0302] The login response also includes a user identifier (uid) corresponding to the username; and
[0303] The uid is sent along with the token to the 5GMS client.
[0304] D5. The method of any one of embodiments D1-D4, wherein:
[0305] The token is associated with a validity period;
[0306] The method further includes: in association with expiration of the validity time period, providing to the 5GMS AA an updated token indicating that the 5GMS AA is authorized to invoke or activate the dynamic policy; and
[0307] The updated token is associated with an updated validity period.
[0308] D6. The method according to any one of embodiments D1-D5, further comprising:
[0309] receiving another token from a 5GMS Application Function (AF) associated with the communication network indicating that the 5GMS AA is authorized to invoke or activate the dynamic policy, thereby sending the token to the ASP;
[0310] verifying that another token received from the 5GMS AF matches the token provided to the 5GMS AA; and
[0311] A response is sent to the 5GMS AF indicating that the 5GMS AA is authorized to activate the dynamic policy.
[0312] D7. The method according to embodiment D6, wherein:
[0313] The token is associated with a validity period;
[0314] The method also includes verifying that another token is received from the 5GMS AF before expiration of the validity period.
[0315] D8. The method according to any one of embodiments D1-D5 also includes: sending a token to a 5GMS application function (AF) associated with the communication network.
[0316] D9. The method according to embodiment D8, wherein:
[0317] The token is associated with a validity period; and
[0318] The method also includes: in association with the expiration of the validity period, sending an updated token to the 5GMS AF indicating that the 5GMS is authorized to invoke or activate the dynamic policy, wherein the updated token is associated with the updated validity period.
[0319] D10. The method according to any one of embodiments D1-D9 further includes: during a media session between the 5GMS AA and the ASP, sending or receiving data via a communication network according to a dynamic strategy.
[0320] D11. The method of embodiment D10, wherein the data is sent via Dynamic Adaptive Streaming over HTTP (DASH) or HTTP Live Streaming (HLS).
[0321] E1. A user equipment (UE) configured to operate in a communication network, wherein:
[0322] The UE includes a communication interface circuit and a processing circuit, which are operatively coupled and configured to implement a 5G Media Stream (5GMS) Aware Application (AA); and
[0323] The processing circuit and the interface circuit are further configured to perform operations corresponding to the method according to any one of embodiments A1-A9.
[0324] E2. A user equipment (UE) configured to operate in a communication network, the UE being further configured to host a 5G media stream (5GMS) aware application (AA), the 5GMS AA being arranged to perform operations corresponding to the method described in any one of embodiments A1-A9.
[0325] E3. A non-temporary computer-readable medium storing computer-executable instructions, which, when executed by a processing circuit of a user equipment (UE) configured to host a 5G media stream (5GMS) aware application (AA), configure the 5GMS AA to perform operations corresponding to the method described in any one of embodiments A1-A9.
[0326] E4. A computer program product comprising computer executable instructions which, when executed by a processing circuit of a user equipment (UE) configured to host a 5G media stream (5GMS) aware application (AA), configure the 5GMS AA to perform operations corresponding to the method described in any one of embodiments A1-A9.
[0327] F1. A user equipment (UE) configured to operate in a communication network, wherein:
[0328] The UE includes communication interface circuitry and processing circuitry operatively coupled and configured to implement a 5G Media Streaming (5GMS) client; and
[0329] The processing circuit and the interface circuit are further configured to perform operations corresponding to the method according to any one of embodiments B1-B8.
[0330] F2. A user equipment (UE) configured to operate in a communication network, the UE being further configured to host a 5G media stream (5GMS) client, the 5GMS client being arranged to perform operations corresponding to the method described in any one of embodiments B1-B8.
[0331] F3. A non-temporary computer-readable medium storing computer-executable instructions, which, when executed by a processing circuit of a user equipment (UE) configured to host a 5G media stream (5GMS) client, configure the 5GMS client to perform operations corresponding to the method described in any one of embodiments B1-B8.
[0332] F4. A computer program product comprising computer executable instructions which, when executed by a processing circuit of a user equipment (UE) configured to host a 5G media stream (5GMS) client, configure the 5GMS client to perform operations corresponding to the method described in any one of embodiments B1-B8.
[0333] G1. A media stream (5GMS) application function (AF) associated with a communication network, wherein:
[0334] The 5GMS AF is implemented by operatively coupled processing circuitry and communication interface circuitry; and
[0335] The processing circuit and the communication interface circuit are configured to perform operations corresponding to the method according to any one of embodiments C1-C9.
[0336] G2. A media stream (5GMS) application function (AF) associated with a communication network, wherein the 5GMS AF is configured to perform operations corresponding to the method described in any one of embodiments C1-C9.
[0337] G3. A non-temporary computer-readable medium storing computer-executable instructions, which, when executed by a processing circuit associated with a 5G media stream (5GMS) application function (AF) associated with a communication network, configures the 5GMS AF to perform operations corresponding to the method described in any one of embodiments C1-C9.
[0338] G4. A computer program product comprising computer executable instructions which, when executed by a processing circuit associated with a 5G media stream (5GMS) application function (AF) associated with a communication network, configure the 5GMS AF to perform operations corresponding to the method described in any one of embodiments C1-C9.
[0339] H1. An application service provider (ASP) for a 5G media stream (5GMS) aware application (AA) hosted by a user equipment (UE) operating in a communication network, wherein:
[0340] The ASP is implemented by operatively coupled processing circuitry and communication interface circuitry; and
[0341] The processing circuit and the communication interface circuit are configured to perform operations corresponding to the method according to any one of embodiments D1-D11.
[0342] H2. An application service provider (ASP) for a 5G media stream (5GMS) aware application (AA) hosted by a user equipment (UE) operating in a communication network, wherein the ASP is configured to perform operations corresponding to the method described in any one of embodiments D1-D11.
[0343] H3. A non-temporary computer-readable medium storing computer-executable instructions that, when executed by a processing circuit associated with an application service provider (ASP) for a 5G media stream (5GMS) aware application (AA) hosted by a user equipment (UE) operating in a communication network, configure the ASP to perform operations corresponding to the method described in any one of embodiments D1-D11.
[0344] H4. A computer program product comprising computer executable instructions which, when executed by a processing circuit associated with an application service provider (ASP) for a 5G media stream (5GMS) aware application (AA) hosted by a user equipment (UE) operating in a communication network, configure the ASP to perform operations corresponding to the method described in any one of embodiments D1-D11.
Claims
1. A method for a 5G media stream 5GMS-aware application AA (200) hosted by a user equipment UE operating in a communication network, the method comprising: obtaining (S84, S103, 1010) a token from an application service provider ASP (700) associated with the 5GMS AA (200), the token indicating that the 5GMS AA (200) is authorized to invoke or activate a dynamic policy for resources of the communication network, wherein the dynamic policy is associated with the ASP (700); and The token is sent (S86, S105, 1020) to a 5GMS client (300) hosted by the UE, wherein the 5GMS client (300) is associated with a 5GMS application function AF (500) of the communication network.
2. The method according to claim 1, wherein: The dynamic policy is one of the following: a Quality of Service (QoS) policy, or a zero rating policy.
3. The method according to any one of claims 1 to 2, wherein: Obtaining the token includes sending (S81, S102, S1011) a login request to the ASP (700), and receiving a login response (S84, S103, 1011) from the ASP (700), and wherein the token is received in the login response.
4. The method according to claim 3, wherein: The login request includes a username and a password associated with a user of the 5GMS AA (200); The login response also includes a user identifier uid corresponding to the user name; and The uid is sent to the 5GMS client together with the token.
5. The method according to any one of claims 1 to 4, wherein: The token is associated with a validity period; The method further comprises: in association with the expiry of the validity period, obtaining (1040) from the ASP (700) a token indicating that the 5GMS AA (200) is authorized to invoke or activate an update of the dynamic policy; and The updated token is associated with an updated validity period.
6. The method according to claim 5, further comprising: The updated token is sent (1050) to the 5GMS client (300).
7. The method according to any one of claims 1 to 6, further comprising: During a media session between the 5GMS AA (200) and the ASP (700), data (1030) is sent or received via the communication network according to the dynamic policy.
8. The method according to claim 7, wherein: The data is received via dynamic adaptive streaming over HTTP (DASH) or HTTP live streaming (HLS).
9. The method according to any one of claims 1 to 8, wherein: The token is sent (S86, S105, 1020) to the media session handler MSH of the 5GMS client (300).
10. The method according to any one of claims 1 to 9, wherein: The token is an identifier indicating that the UE is authorized to invoke or activate the dynamic policy.
11. A method for a 5G media stream 5G MS client (300) hosted by a user equipment UE operating in a communication network, the method comprising: receiving (S86, S105, 1110) a token from a 5G media stream 5GMS-aware application AA (200) hosted by the UE, the token indicating that the 5GMS AA (200) is authorized to invoke or activate a dynamic policy for resources of the communication network, wherein the dynamic policy is associated with an application service provider ASP (700), the ASP (700) being associated with the 5GMS AA (200); sending (S87, S106, 1120) the token to a 5GMS Application Function AF (500) of the communication network in a request to activate the dynamic policy for the 5GMS AA (200); and A response is received (S94, S110, 1130) from the 5GMS AF (500), the response indicating that the dynamic policy is activated for the 5GMS AA (200) according to the token.
12. The method according to claim 11, wherein: The dynamic policy is one of the following: a Quality of Service (QoS) policy, or a zero rating policy.
13. The method according to any one of claims 11 to 12, wherein: The token is received together with a user identifier uid corresponding to a username associated with a user of the 5GMS AA (200); and The uid is sent together with the token to the 5GMS AF (500).
14. A method according to any one of claims 11 to 13, wherein: The token is associated with a validity period; The method further comprises: in association with the expiration of the validity period (1150), receiving a token from the 5GMS AA (200) indicating that the 5GMS AA (200) is authorized to invoke or activate an update of the dynamic policy; and The updated token is associated with an updated validity period.
15. The method according to claim 14, further comprising: sending (1160) the updated token to the 5GMS AF (500) in a request to activate the dynamic policy for the 5GMS AA (200); as well as A response is received (1170) from the 5GMS AF (500), the response indicating that the dynamic policy is activated for the 5GMS AA (200) based on the updated token.
16. The method according to any one of claims 11 to 15, further comprising: According to the dynamic strategy, data (1140) is sent or received with the 5GMS application server AS (600) via the communication network, wherein the data is associated with a media session between the 5GMSAA (200) and the ASP (700).
17. The method according to claim 16, wherein: The data is received via dynamic adaptive streaming over HTTP (DASH) or HTTP live streaming (HLS).
18. The method according to any one of claims 11 to 17, wherein: The token is received by the media session handler MSH of the 5GMS client (300) from the 5GMS AA (200) and sent to the 5GMS AF (500).
19. A method for a 5G media stream 5GMS application function AF (500) associated with a communication network, the method comprising: A token is received (S87, S106, 1220) from a 5GMS client (300) hosted by a user equipment UE operating in the communication network, the token indicating that a 5GMS-aware application AA (200) hosted by the UE is authorized to invoke or activate a dynamic policy for resources of the communication network, wherein: The dynamic policy is associated with an application service provider ASP (700), the ASP (700) is associated with the 5GMSAA (200), and The token is received in a request to activate the dynamic policy for the 5GMS AA (200); and based on determining (1230) that the token is valid, sending (S94, S110, 1260) a response to the 5GMS client (300) indicating that the dynamic policy is activated.
20. The method according to claim 19, wherein: The dynamic policy is one of the following: a Quality of Service (QoS) policy, or a zero rating policy.
21. The method according to any one of claims 19 or 20, wherein: The method further comprises: receiving (1210) from the ASP (700) another token indicating that the 5GMS AA (200) is authorized to invoke or activate the dynamic policy; and Determining that the token is valid includes verifying (1231) that the token received from the 5GMS AA (200) matches the other token received from the ASP (700).
22. The method of claim 21, wherein: The further token is associated with a validity period; as well as Determining that the token is valid includes verifying (1232) that the token is received from the 5GMS AA (200) before expiration of the validity period.
23. The method according to claim 22, further comprising: Receiving (1210) another token from the ASP (700) indicating that the 5GMSAA (200) is authorized to invoke or activate an update of the dynamic policy, wherein the updated another token is associated with an updated validity period.
24. The method according to claim 23, further comprising: subsequently receiving (1280) an updated token from the 5GMS client (300) in a request to activate the dynamic policy for the 5GMS AA (200), wherein the updated token is associated with the updated validity period; and Based on determining that the updated token is valid, sending (1290) a response to the 5GMS client (300) indicating that the dynamic policy is activated.
25. The method according to any one of claims 19 to 20, wherein: Determining that the token is valid includes: sending (S88, 1233) the token to the ASP (700); and A response is received (S90, 1234) from the ASP (700) indicating that the 5GMS AA (200) is authorized to activate the dynamic policy.
26. The method of claim 25, wherein: The token is received from the 5GMS Client (300) together with a user identifier uid corresponding to a username associated with a user of the 5GMS AA (200); and The token is sent to the ASP (700) along with the uid.
27. The method according to any one of claims 19 to 26, further comprising: Based on determining that the token is valid, sending (S92, S108, 1240) a request to activate the dynamic policy to a policy control function PCF (400) of the communication network; as well as receiving (S93, S109, 1250) a response from the PCF (400) indicating that the dynamic policy is activated, Wherein, the response is sent to the 5GMS client (300) based on the response from the PCF (400).
28. A method for an application service provider ASP (700) of a 5G media stream 5GMS-aware application AA (200) hosted by a user equipment UE operating in a communication network, the method comprising: A token is provided (S84, S103, 1310) to the 5GMS AA (200), the token indicating that the 5GMS AA (200) is authorized to invoke or activate a dynamic policy for resources of the communication network, wherein the dynamic policy is associated with the ASP (700).
29. The method according to claim 28, wherein: The dynamic policy is one of the following: a Quality of Service (QoS) policy, or a zero rating policy.
30. The method according to any one of claims 28 to 29, wherein: Providing the token includes: receiving (S81, S102, 1311) a login request from the 5GMSAA (200), and sending (S84, S103, 1311) a login response to the 5GMS AA (200), and wherein the token is sent in the login response.
31. The method of claim 30, wherein: The login request includes a username and a password associated with a user of the 5GMS AA (200); The login response also includes a user identifier uid corresponding to the user name; and The uid is sent together with the token to the 5GMS AA (200).
32. A method according to any one of claims 28 to 31, wherein: The token is associated with a validity period; The method further comprises: in association with expiration of the validity period, providing to the 5GMS AA (200) a token indicating that the 5GMS AA (200) is authorized to invoke or activate an update of the dynamic policy; and The updated token is associated with an updated validity period.
33. The method according to any one of claims 28 to 32, further comprising: receiving (S88, 1320) from a 5GMS Application Function AF (500) associated with the communication network another token indicating that the 5GMS AA (200) is authorized to invoke or activate the dynamic policy; verifying (S89, 1330) that the further token received from the 5GMS AF (500) matches the token provided to the 5GMS AA (200); and A response is sent (S90, 1350) to the 5GMS AF (500) indicating that the 5GMS AA (200) is authorized to activate the dynamic policy.
34. The method of claim 33, wherein: The token is associated with a validity period; as well as The method further comprises verifying (1340) that the further token is received from the 5GMS AF (500) before expiry of the validity period.
35. The method according to any one of claims 28 to 34, further comprising: The token is sent to a 5GMS Application Function AF (500) associated with the communication network.
36. The method of claim 35, wherein: The token is associated with a validity period; as well as The method further comprises, in association with the expiry of the validity period (1390), sending to the 5GMS AF (500) an updated token indicating that the 5GMS AA (200) is authorized to invoke or activate the dynamic policy, wherein the updated token is associated with the updated validity period.
37. The method according to any one of claims 28 to 36, further comprising: During a media session between the 5GMS AA (200) and the ASP (700), data (1370) is sent or received via the communication network according to the dynamic policy.
38. The method of claim 37, wherein: The data is sent via dynamic adaptive streaming over HTTP (DASH) or HTTP live streaming (HLS).
39. A user equipment UE (1500) configured to operate in a communication network, wherein: The UE (1500) comprises a communication interface circuit (1506) and a processing circuit (1502) which are operatively coupled and configured to implement a 5G media stream 5GMS-aware application AA (200); and The processing circuit (1502) and the interface circuit (1506) are further configured to perform operations corresponding to the method according to any one of claims 1 to 10.
40. A user equipment UE configured to operate in a communication network, the UE being further configured to host a 5G media stream 5GMS aware application AA (200), the 5GMS AA (200) being arranged to perform operations corresponding to the method according to any one of claims 1 to 10.
41. A non-transitory computer-readable medium storing computer-executable instructions, which, when executed by a processing circuit of a user equipment UE (1500) configured to host a 5G media stream 5GMS Awareness Application AA (200), configures the 5GMS AA (200) to perform operations corresponding to the method according to any one of claims 1 to 10.
42. A computer program product comprising computer executable instructions, which, when executed by a processing circuit (1502) of a user equipment UE (1500) configured to host a 5G media stream 5GMS Awareness Application AA (200), configures the 5GMS AA (200) to perform operations corresponding to the method according to any one of claims 1 to 10.
43. A user equipment UE (1500) configured to operate in a communication network, wherein: The UE comprises a communication interface circuit (1506) and a processing circuit (1502) which are operatively coupled and configured to implement a 5G media stream 5G MS client (300); and The processing circuit (1502) and the interface circuit (1506) are further configured to perform operations corresponding to the method according to any one of claims 11 to 18.
44. A user equipment UE configured to operate in a communication network, the UE being further configured to host a 5G media stream 5GMS client (300), the 5GMS client (300) being arranged to perform operations corresponding to the method according to any one of claims 11 to 18.
45. A non-transitory computer-readable medium storing computer-executable instructions, which, when executed by a processing circuit (1502) of a user equipment UE (1500) configured to host a 5G media stream 5GMS client (300), configures the 5GMS client (300) to perform operations corresponding to the method according to any one of claims 11 to 18.
46. A computer program product comprising computer executable instructions, which, when executed by a processing circuit (1502) of a user equipment UE (1500) configured to host a 5G media stream 5GMS client (300), configures the 5GMS client (300) to perform operations corresponding to the method according to any one of claims 11 to 18.
47. A 5G media stream 5GMS application function AF (500, 1600) associated with a communication network, wherein: The 5GMS AF (500, 1600) is implemented by a processing circuit (1602) and a communication interface circuit (1606) that are operatively coupled; and The processing circuit (1602) and the communication interface circuit (1606) are configured to perform operations corresponding to the method according to any one of claims 19 to 27.
48. A media stream 5GMS application function AF (500) associated with a communication network, wherein: The 5GMS AF (500) is configured to perform operations corresponding to the method according to any one of claims 19 to 27.
49. A non-transitory computer-readable medium storing computer-executable instructions, which, when executed by a processing circuit (1602) associated with a 5G media stream 5GMS application function AF (500, 1600) associated with a communication network, configures the 5GMS AF (500, 1600) to perform operations corresponding to the method according to any one of claims 19 to 27.
50. A computer program product comprising computer executable instructions which, when executed by a processing circuit (1602) associated with a 5G media stream 5GMS application function AF (500, 1600) associated with a communication network, configure the 5GMS AF (500, 1600) to perform operations corresponding to the method according to any one of claims 19 to 27.
51. An application service provider ASP (700, 1600) for a 5G media stream 5GMS-aware application AA (200) hosted by a user equipment UE operating in a communication network, wherein: The ASP (700, 1600) is implemented by a processing circuit (1602) and a communication interface circuit (1606) operatively coupled; and The processing circuit (1602) and the communication interface circuit (1606) are configured to perform operations corresponding to the method according to any one of claims 28 to 38.
52. An application service provider ASP (700) for a 5G media stream 5GMS-aware application AA (200) hosted by a user equipment UE operating in a communication network, wherein: The ASP (700) is configured to perform operations corresponding to the method according to any one of claims 28 to 38.
53. A non-transitory computer-readable medium storing computer-executable instructions, which, when executed by a processing circuit (1602) associated with an application service provider ASP (700, 1600) for a 5G media stream 5GMS-aware application AA (200) hosted by a user equipment UE operating in a communication network, configure the ASP (700, 1600) to perform operations corresponding to the method described in any one of claims 28 to 38.
54. A computer program product comprising computer executable instructions which, when executed by a processing circuit (1602) associated with an application service provider ASP (700, 1600) for a 5G media stream 5GMS-aware application AA (200) hosted by a user equipment UE operating in a communication network, configure the ASP (700, 1600) to perform operations corresponding to a method according to any one of claims 28 to 38.
