Media assistance data in telecommunication network

Abstract

Examples techniques to provide media assistance data in a telecommunication network (TCN) are described. The media assistance data is received by at least one of a User Plane Function (UPF) entity of the TCN and a User Equipment (UE) connected to the TCN. The media assistance data comprises application layer information. The UPF entity or the UE detects PDU set and determines PDU set information corresponding to the session, based on the media assistance data.

Description

MEDIA ASSISTANCE DATA IN TELECOMMUNICATION NETWORKFIELD

[0001] The field relates generally to wireless communication systems, and more particularly, to managing media services in a telecommunication network system, such as a fifth generation (5G) network system (5GS), a sixth generation (6G) network system, or beyond.BACKGROUND

[0002] A telecommunication network, such as a 5G telecommunication network, offers technical solutions related to data connectivity and network services, allowing greater throughput, lower latency, higher reliability, higher connectivity and higher mobility range. Additionally, 5G networks also extend the flexibility in network usage.

[0003] The 3rdGeneration Partnership Project (3GPP) is a standard organization which develops protocols for mobile telephony and is known for the development and maintenance of various standards including second generation (2G), third generation (3G), fourth generation (4G), Long Term Evolution (LTE), fifth generation (5G) standards, sixth generation (6G) standards, and beyond.

[0004] In a 5G network, for example, extended Reality and Media Services (XRM) contribute large amount of traffic to the 5G network, extended reality (XR) includes augmented reality (AR), virtual reality (VR), and mixed reality (MR) based applications. These applications may include, for example, cloud AR / VR, cloud gaming, video-based tele-control for machines or drones. Traffic of XR based services and other media services includes time sensitive data and has the characteristics of high throughput, low latency, and high reliability requirement. Time synchronization is also an important aspect to be considered while developing a framework for the transport of data related to XRM based services.

[0005] One or more 3GPP technical specifications (TS), e.g., 3GPP TS 23.501 , and technical reports (TR) provide explanations of network elements / functions and / or operations in 5G or other similar communication environments. 3GPP release 18 specifies mechanisms for the XRM services.SUMMARY

[0006] Various embodiments of present invention are described herein.

[0007] The details of some embodiments of the subject matter described in this specification are set forth in the accompanying drawings and the description below. Other features, aspects, and advantages of the subject matter will become apparent from the description, the drawings, and the claims.

[0008] According to an embodiment of the present invention, a method of providing media assistance data in a telecommunication network is provided. The Telecommunication Network (TCN) may be a 5-Generation Core Network (5GC) in one example.

[0009] The method comprises providing media assistance data from an application function (AF) of the TCN to a network entity of the TCN. The network entity may be a policy control function (PCF) entity or a Network Exposure Function (NEF) entity. The media assistance data comprises application layer information.

[0010] In an example the media assistance data further comprises parameter values to be used for a session as negotiated between endpoints of the session. The session may comprise a transport layer session or an application layer session. For example, the media assistance data comprises one of a session description protocol (SDR) session information, a Real-time Transport Protocol (RTP) session information, a DynamicAdaptive Streaming over HTTP (HTTP / DASH) session information, or a Quick UDP Internet Connections (QUIC) related session information.

[0011] The network entity that receives the media assistance data from the AF determines at least one of a parameter for transmission of service data over a session and a protocol description, which comprises media characteristics, based at least in part on the media assistance data.

[0012] In an example, the parameter for transmission of the service data comprises one or more of at least one quality of service (QoS) parameter or traffic assistance information. The at least one QoS parameter may comprise Packet Delay Budget (PDB), Packet Error Rate (PER), PDU Set Error Rate (PSER), PDU Set Delay Budget (PSDB), or PDU Set Integrated Handling Indicator (PSI H I) in an example.

[0013] The network entity then provides at least one of the parameter for transmission of the service data, the media assistance data and the protocol description to at least one of a User Plane Function (UPF) entity of the TCN, a Radio Access Network (RAN) of the TCN and a User equipment (UE) connected to the TCN via a Session Management Function (SMF) entity of the TCN. In one example implementation, one or more of the parameter for transmission of the service data, the media assistance data and the protocol description received at the UPF or UE cause the UPF entity or the UE to determine a media type of data received over the session. Further, in an example, determining the media type of the data comprises determining protocol data unit (PDU) sets or PDU set information corresponding to the session. In an example, at least one of the parameter for transmission of the service data, the media assistance data and the protocol description is configured to cause the UPF entity or the UE to determine protocol data unit (PDU) sets or PDU set information corresponding to the session.

[0014] For instance, in an example, the PCF entity may receive the media assistance data from the AF. The PCF entity may generate a PolicyCharging and Control (PCC) rule based at least in part on the media assistance data. The PCC rule may comprise a parameter for transmission of service data over a session and a protocol description, which includes media characteristics of the service data. The PCF entity transmits the PCC rule to the Session Management Function (SMF) entity of the TCN. Since the PCC rule based at least in part on the media assistance data, it enables the SMF entity to provide the parameter for transmission of the service data and the protocol description to a User Plane Function (UPF) entity of the TCN, a Radio Access Network (RAN) of the TCN and / or a User equipment (UE) connected to the TCN.

[0015] According to an embodiment of the present invention, another method of providing media assistance data in a telecommunication network, for example, without intervention of the network entities, is provided.

[0016] The method, in an example, comprises receiving media assistance data at an UPF entity of the TCN or an UE connected thereto. The media assistance data comprising application layer information. In an example, the media assistance information is provided by an Application Function (AF) entity to a Session Management Function (SMF) entity by a Policy Control Function (PCF) entity of the TCN directly or via a Network Exposure (NEF) Entity of the TCN. The at least one of the UPF entity or the UE receives the media assistance information from the Session Management Function (SMF) entity. In an example embodiment, the media assistance data can also include parameter values to be used for a session as negotiated between endpoints of a session. As mentioned previously, the media assistance data comprises one of a session description protocol (SDP), a Real-time Transport Protocol (RTP) session information, a Dynamic Adaptive Streaming over HTTP (HTTP / DASH) session information, or a Quick UDP Internet Connections (QUIC) related session information. Based on the media assistance data, the UPF or UE is enabled to detect PDU set and determine PDU set information corresponding to thesession. For example, the PDU set information may comprise PDU set importance value.

[0017] Also, in an example, the method further comprises detecting Data Burst and determining Data Burst parameters comprising End of Data Burst Indicator corresponding to the session.

[0018] In an example, the UPF or UE may additionally receive a parameter for transmission of service data over the session and protocol description determined by the PCF entity or the NEF entity of the TCN. The parameter for transmission of service data over the session and protocol description may in turn be based on the media assistance data. In an example, the parameter for transmission of the service data comprises a QoS parameter and traffic assistance information (e.g., Time Sensitive Communication Assistance Information TSCAI).

[0019] In an example, the method further comprises detecting PDU set and determining PDU set information corresponding to the session, by the UPF entity or the UE, based on at least one of the media assistance, the parameter for transmission of service data and the protocol description.BRIEF DESCRIPTION OF FIGURES

[0020] The following detailed description references the drawings, wherein:

[0021] Figure 1 illustrates a network system, in accordance with an example implementation of the present subject matter;

[0022] Figure 2a illustrates a method of providing media assistance data in a telecommunication network, in accordance with an example implementation of the present subject matter;

[0023] Figure 2b illustrates a signal flow diagram corresponding to the method illustrated in Figure 3a, in accordance with an example implementation of the present subject matter;

[0024] Figure 3a illustrates a method of providing media assistance data in a telecommunication network, in accordance with an example implementation of the present subject matter; and

[0025] Figure 3b illustrates a signal flow diagram corresponding to the method illustrated in Figure 3a, in accordance with another example implementation of the present subject matter.DETAILED DESCRIPTION

[0026] A network system (e.g., 5GS) comprises components, i.e., a access network (e.g., a 5G-AN) or next generation radio access network (NG-RAN), a core network (e.g., 5G Core Network 5GC) and a user equipment (UE). An access network may be a radio access network (RAN), e.g., a base station or access point connecting the user equipment to a core network (e.g., a 5G core network), which provides access for the UE to other UEs and / or a data network (DN), such as a packet data network (e.g., Internet). As mentioned above, 5G network access procedures are described in 3GPP technical specifications (TS) and technical reports (TR), e.g., Technical Specification (TS) 23.502, titled “Technical Specification Group Services and System Aspects; Procedures for the 5G System”, the disclosure of which is incorporated by reference herein in its entirety.

[0027] A 5G system is based on a service-based architecture, where a Control Plane (CP) which carries signaling traffic is separated from a User Plane which carries data or content to be communicated over the network. This makes the 5GS, a scalable network and the network may be adapted as per the requirements.

[0028] 5GC offers numerous network functions (NF) or network function entities providing capabilities such as mobility management, routing, security, policy control, charging, and subscriber data management. Each NF or network function entity offers one or more services to and may interact with other NFs or network function entities via applicationprogramming interface. Some of the NFs are Authentication Server Function (AUSF), Core Access and Mobility Management Function (AMF), Network Exposure Function (NEF), NF Repository Function (NRF), Policy Control function (PCF), Session Management Function (SMF), User plane Function (UPF), Application Function (AF). AF is a control plane function which provides designated application services to the end users. If an AF is trusted, the AF can interact directly with 5GC network functions, or if it is a 3rd party AF, then the AF can interact with an NEF. The NEF facilitates secure, robust, developer-friendly access to the exposed network services and capabilities of 5GC. The PCF provides policy rules to Control Plane function(s), and accesses subscription information relevant for policy decisions from a Unified Data Repository (UDR). The AMF, as used herein, is the element or function (i.e. , entity) in the core network (CN) that manages or participates in, among other network operations, access and mobility (including authentication / authorization) operations with the UE (through the access point). The SMF supports session management, e.g., session establishment, modification, release and other functions, such as UE IP address allocation & management. AUSF is an authentication server.

[0029] The UPF is the data plane in the 5G core. After an Access Gateway Function (AGF) authenticates a subscriber and establishes a protocol data unit (PDU) session, the SMF selects the UPF for the subscriber. The UPF provides the interconnect point between the mobile infrastructure and the Data Network. The UPF also supports packet routing and forwarding, packet inspection, Quality of Service (QoS) handling, acts as an external PDU session point of interconnecting to Data Network, and is an anchor point for intra- and inter-RAT (Radio access technology) mobility.

[0030] Further typical operations and functions of such network elements are not described here and may be found in appropriate 3GPP documentation.

[0031] To enable interaction of an UE with an AF, a session is established between the UE and the AF. For this purpose, the AF provides the Policy Control Function (PCF) with the application layer service requirements. The application layer service requirements, for example, for IP (Internet Protocol) type packets, may comprise source address, destination address, source port number, destination port number, and the protocol type above IP layer. Application layer service requirements also include QoS-related requirements, such as bandwidth requirements, service types, etc. If the AF is a trusted AF, the AF can provide information to the PCF directly, and if the AF is a third-party AF that is not trusted, the AF can provide information to the PCF through the NEF. The NEF authenticates the AF. As mentioned above, the application layer service requirements include QoS parameters and other information. Other information may include the service protocol used by the data flow in that particular service.

[0032] To support extended reality and media services in 3GPP networks, Service and System Aspects 2 (SA2) for Release 18 specifies mechanisms for integrated and differentiated PDU set handling. A Protocol Data Unit (PDU) may be understood as the basic unit of exchange between entities that communicate using a specified networking protocol. As specified in TS 23.501 , a PDU set is one or more PDUs carrying the payload of one unit of information generated at the application level, e.g., a video frame or video slice for XR services.

[0033] In case of time sensitive XRM applications, service requirements of different types of traffic steams with coordinated QoS selection and packet processing, guaranteed latency and reliability, time synchronization of parallel information, need to be addressed in order to ensure best service experience. Based on the service specific requirements and other information available at the PCF, PCF makes Policy Control and Charging (PCC ) rules and sends the PCC rules to the SMF. The SMF then maps the PCC to a corresponding QoS flow and determines a QoS profilecomprising QoS parameters; QoS rules comprising flow description information and QoS Flow Identifier (QFI); and packet detection rules (FDR) and corresponding QoS enforcement rules (QER), including the flow description information for service data flow (SDF) detection and the QFI of QoS Flow used to transmit the SDF.

[0034] Multiple PCC rules may be bound to the same QoS flow. This implies multiple service data flows or PDUs can be transmitted using the same QoS flow. The SMF then distributes these QoS profile / QoS rule / packet detection rule (PDR) to NG-RAN, UPF, and / or UE and instructs the UPF to detect PDU sets during the PDU Session Establishment / Modification procedures. After receiving the QoS parameters or profile, the NG-RAN maps the QoS Flow to an appropriate radio bearer according to the QoS parameters of the QoS Flow, and allocates the corresponding radio resources. The NG-RAN also sends the mapping relationship between QoS Flow and radio bearer to the UE. After the QoS Flow and radio resources are ready, the transmission of the service data starts.

[0035] The UPF uses the PDR received from the SMF to match the downlink data, marks the QFI to the matched packet header according to the corresponding QER, and then sends the packets to the NG-RAN through the PDU session level GPRS tunneling protocol-user plane (GTP- U) tunnel between the UPF and the NG-RAN. The GTP-U protocol entity provides packet transmission and reception services to user plane entities. The GTP-U protocol entity receives traffic from a number of GTP-U tunnel endpoints and transmits traffic to a number of GTP-U tunnel endpoints.

[0036] Thus, for downlink XR traffic, 3GPP specifies to support the detection of PDU sets by the PDU session anchor (PSA) UPF or UPF and subsequent marking of the PDU set information by the UPF in downlink GTP-U packets sent to the NG-RAN. Integrated and differentiated PDU set handling is performed in the NG-RAN according to QoS parameters that are applicable to the group of PDUs that form a PDU set. These QoSparameters include PDU Set Error Rate (PSER), PDU Set Delay Budget (PSDB) and a PDU Set Integrated Handling Indicator (PSIHI). The PSIHI indicates whether all PDUs in a PDU set are needed by the application for it to process the application layer information at all.

[0037] In 3GPP Release 18, XRM related specifications, there is only limited information about the traffic flows provided to the 5GC or UPF. The AF may send a request to the NEF, when the AF is a third party non-trusted entity or directly to the PCF, when the AF is a trusted entity, providing a protocol description indicating the application protocol, header (e.g., RTP / SRTP), extension header and / or payload type (e.g., H.264) used by the application for downlink traffic sent to the UPF. The protocol description is in addition to the IP and transport (UDP or TCP) layer service data flow identification information, and optionally QoS requirements and PDU Set QoS requirements for PDU Set QoS parameters as part of the service specific requirements, i.e., the above-described application layer service requirements. If the PCF authorizes the AF request, the PCF incorporates the AF information in a PCC rule sent to the SMF. Alternatively, the protocol description and optionally PDU Set QoS parameters may be more statically configured in the 5GC.

[0038] Protocol description indicates protocol and payload type used by the service data flow. As per TS 23.501 Rel-18, the SMF sends the protocol description to the UPF which may use it to help identify the PDU Sets to which PDUs received from the application belong. In addition, the UPF derives PDU Set Information for DL traffic and sends it to NG-RAN via DL GTP-U header of each PDU identified as belonging to a PDU Set. AF provided PDU Set QoS Parameters and protocol description may also be used by the SMF in determining the QoS Profile sent to the RAN and QoS rules sent to the UE. The PSA UPF can identify the PDU Set information using the protocol description and the received protocol headers (e.g., RTP / SRTP, SDP) as described above, or using implementation specific means. In Release 18, the protocol description is sent to the UPF to aid it indetecting DL PDU association with PDU Sets. It is not sent to the UE to aid a similar process for UL PDUs.

[0039] Applications, in general, can use different protocols for media / content transport, such as session description protocol (SDP), Realtime Transport Protocol (RTP), Dynamic Adaptive Streaming over HTTP (HTTP / DASH), and Quick UDP Internet Connections (QUIC) and different means to negotiate the media / content transport session parameters beyond UDP port numbers, such as codecs. The protocol description just refers to a specific protocol, e.g., session description protocol (SDP) header extension (HE) or payload type. However, both HE and payload type IDs are dynamically negotiated per session. Accordingly, the endpoints, e.g., AF and UE know the values of protocol description, for example, the negotiated HE and payload type IDs, but the UPF and other NFs of the 5GC, e.g., NEF, PCF, SMF are not aware of the same. The currently provided information in protocol description assumes AF intervention to identify PDU set(s) correctly at the UPF.

[0040] Further, the AF provides only the PDU set level QoS requirements (i.e., PSDB, PSER, PSIHI) and the Flow description (e.g., source and destination IP address and port numbers, etc.) for the target media service data flow to the UPF. AF does not provide any hint to 5GC regarding the content type of the media, information regarding type of frame, e.g., I frame / P frame, codecs to be used. However, such information also plays a critical role in the detection of PDU set and setting of the QoS parameters.

[0041] According to example implementations of the present subject matter, techniques to provide media assistance data of a session to entities of a telecommunication network, such as entities of a 5G core network (5GC) of a 5G communication network or UE or RAN to enable the telecommunication network to efficiently handle XRM based services are described.

[0042] In an example implementation, a PCF entity or a NEF entity of a telecommunication network (TCN) such as a 5GS receives the media assistance data from an application function (AF) entity of the TCN. The media assistance data comprises application layer information. The media assistance data may be information describing the session. It may comprise a description of a protocol to be used for service data flow over the session, content type of the data service data flow to be transmitted over the session, codec format to be used for XRM related data or start / stop of service / session. The media assistance data is received from an AF of the TCN. In an example, the media assistance data comprises parameter values to be used for the session as negotiated between endpoints of the session. The PCF entity or the NEF entity, as the case may be, determines at least one of a parameter for transmission of service data over a session and a protocol description based at least in part on the media assistance data. The protocol description comprises media characteristics such as type of media. The PCF entity or the NEF entity provides at least one of the parameter for transmission of the service data, the media assistance data and the protocol description to at least one of a User Plane Function (UPF) entity of the TCN, a Radio Access Network (RAN) and a User equipment (UE) connected to the TCN via a Session Management Function (SMF) entity of the TCN.

[0043] In an example, the parameter for transmission of the service data is a QoS parameter comprising Packet Delay Budget (PDB), Packet Error Rate (PER), PDU Set Error Rate (PSER), PDU Set Delay Budget (PSDB) and PDU Set Integrated Handling Indicator (PSIHI). The PSIHI indicates whether all PDUs in a PDU Set are needed by the application for it to process the application layer information at all. The parameter for transmission of the service data may also comprise traffic assistance information (e.g., Time Sensitive Communication Assistance Information (TSCAI)). The traffic assistance information may include attributes that can be used by the UE or UPF to detect PDU sets.

[0044] The parameter for transmission of the service data and the protocol description as derived using the media assistance data that comprises session specific details conveyed by the AF and the media assistance data itself are provided to the network entities, rather than AF providing the specific and limited set of parameters for transmission of the service data. Thus, the techniques described by the present invention make the network entities aware of the dynamically updated session parameters or requirements that may be negotiated between endpoints of the session. Since, the network entities, such as UPF, UE or RAN are aware of the session specific details, these entities can use the same for various functions. In an example, based on the parameters made available to the network entities, the QoS parameters can be set more appropriately and the UPF or UE may be enabled to detect the PDU sets, to determine PDU set parameters correctly and efficiently.

[0045] The above techniques are further described with reference to Figure 1 to Figure 3b. It should be noted that the description and the Figures merely illustrate the principles of the present subject matter along with examples described herein and should not be construed as a limitation to the present subject matter. It is thus understood that various arrangements may be devised that, although not explicitly described or shown herein, embody the principles of the present subject matter. Moreover, all statements herein reciting principles, aspects, and implementations of the present subject matter, as well as specific examples thereof, are intended to encompass equivalents thereof.

[0046] Figure 1 illustrates a telecommunication network, for example, a 5G system (5GS) 100, in accordance with an example implementation of the present subject matter. The 5G system (5GS) 100 comprises a 5G access network (5G-AN) 102 or next generation radio access network (NG- RAN), a 5G core network (5GC) 104 and a user equipment (UE) 106. The UE 106 may be a mobile station, and such a mobile station may comprise, by way of example, a mobile telephone, a computer, or any other type ofcommunication device. The term “user equipment” as used herein is therefore intended to be construed broadly, so as to encompass a variety of different types of mobile stations, subscriber stations or, more generally, communication devices, including examples such as a combination of a data card inserted in a laptop or other equipment such as a smart phone. Such communication devices are also intended to encompass devices commonly referred to as access terminals. As mentioned above, an access network, e.g., a base station connects the UE to the 5GC network, which provides access for the UE to other UEs and / or a data network (DN) 108.

[0047] Various Network Functions (NFs) or network function entities offered by the 5GC provide network capabilities. Some of the NFs or network function entities of 5GC are AUSF, AMF, NEF, NRF, PCF, SMF, UPF, and AF. Operations performed by these NFs or network function entities are the same described above. Further, one or more 3GPP technical specifications (TS) and technical reports (TR) may provide further explanation of network elements / functions and / or operations that may interact with parts of the inventive solutions, e.g., the above-referenced 3GPP TS 23.501 , 23.502. Other 3GPP TS / TR documents may provide other conventional details that one of ordinary skill in the art will realize. However, while well-suited for 5G-related 3GPP standards, embodiments are not necessarily intended to be limited to any particular standards.

[0048] Also, 5G network access procedures are described in 3GPP technical specifications (TS) and technical reports (TR), e.g., Technical Specification (TS) 23.502, titled “Technical Specification Group Services and System Aspects; Procedures for the 5G System” and TS 23.501 , the disclosure of which are incorporated by reference herein in its entirety.

[0049] According to an example of the present invention, for a session between two end points such as an application function (AF) and the UE, a media assistance data of the session that comprises parameter values to be used for the session as negotiated between the endpoints of the session and an application layer information is made available to thenetwork entities such as UPF of 5GC, RAN or UE. The network entities may use these parameter values for various purposes, for example, setting of QoS parameter for transmission of data over the session or for PDU set identification.

[0050] Figure 2a illustrates a method 200 of providing media assistance data in a telecommunication network (TCN) and Figure 2b illustrates corresponding signal flow, according to an example of the present subject matter. For the sake of ease of explanation, Figures 2a and 2b are explained in conjunction with each other.

[0051] The method 200 may be implemented by a processor(s) or computing device(s) through any suitable hardware, non-transitory machine-readable instructions, or combination thereof. It may be understood that blocks of the method 200 may be performed by computing devices programmed to perform the operations of a telecommunication network. However, for the ease of explanation, the present description of the example method 200 is provided in reference to a 5G system. Thus, in an example implementation, the method 200 may be performed by computing devices programmed to perform the operations of a 5G Core Network (5GC) and implemented in a 5G system such as above-described 5GS 100. The blocks of the method 200 may be executed based on instructions stored in a non-transitory computer readable medium, as will be readily understood. The non-transitory computer readable medium may include, for example, digital memories, magnetic storage media, such as magnetic disks and magnetic tapes, hard drives, or optically readable digital data storage media.

[0052] Referring to Figure 2a, at block 202, a Policy Control Function (PCF) entity 312 of the TCN, such as a PCF of the 5GC 104, receives media assistance data from an application function (AF) entity 302 of the TCN. The media assistance data 304 comprises application layer information. In an example, the application layer information may comprise a content type of service data to be transmitted over the session and the data or otherinformation related to the application layer data. The media assistance data further comprises parameter values to be used for the session as negotiated between endpoints of the session. The endpoints may be the AF entity 302 and a UE 326, such as a mobile device or a server. The session may be a transport layer session or an application layer session. Parameter values to be used for the session may comprise, address of receivers, port number, session information of a protocol to be used for the transmission of service data, codec format to be used for XRM related data and start / stop of service / session, bandwidth requirements, flow rate.

[0053] In an example, the media assistance data comprises one of a session description protocol (SDP), a Real-time Transport Protocol (RTP) session information, a Dynamic Adaptive Streaming over HTTP (HTTP / DASH) session information, or a Quick UDP Internet Connections (QUIC) related session information. In an example, the parameter values to be used for the session may be the values specified using the Session Description Protocol (SDP). As mentioned above, SDP is a format for describing multimedia communication sessions for the purposes of announcement and invitation. SDP supports streaming media applications, such as voice over IP (VoIP) and video conferencing. SDP does not deliver any media streams itself but is used between endpoints for negotiation of network metrics, media types, and other associated properties.

[0054] In an example, if the AF entity 302 entity is a third-party AF which is not trusted, the media assistance data 304 is provided in a request to the Network Exposure Function (NEF) entity 308 by the AF entity 302 as represented by the signal 306. The NEF entity 308 authenticates the AF entity 302 and after authenticating, provides the media assistance data 304 to the PCF 312 as represented by the signal 310.

[0055] At block 204, the PCF entity determines at least a parameter for transmission of service data over a session or a protocol description based at least in part on the media assistance data. The PCF entity 312 generates a Policy Charging and Control (PCC) rule 314 based at least inpart on the determined parameter for transmission of service data over a session and the protocol description. The parameters for transmission of the service data comprises a QoS parameter or traffic assistance information . The service data may be a single Protocol Data Unit (PDU) that is a basic unit of information exchanged between the end points or a PDU set which is one or more PDUs carrying the payload of one unit of information generated at the application level, e.g., a video frame or video slice for XR services.

[0056] The QoS parameter may comprise Packet Delay Budget (PDB), Packet Error Rate (PER), PDU Set Error Rate (PSER), PDU Set Delay Budget (PSDB) and PDU Set Integrated Handling Indicator (PSIHI). The traffic assistance information may include PDU set specific information that can be used by the UE or UPF to detect PDU sets for uplink or downlink transmission of the service data over the session. The PDU set specific information may comprise start / stop timing of a PDU set. The protocol description comprises media characteristics. Media characteristics may include the type of media or type frame, e.g., I frame or P frame.

[0057] In an example embodiment, the NEF may map the media assistance data to the parameters for transmission of the service data that includes the QoS parameters and the traffic assistance information; and protocol description. Instead of providing the media assistance data to the PCF, the NEF may provide the parameters for transmission of the service data and the protocol description to the PCF. The PCF may generate the PCC rule based at least in part on the parameters for transmission of the service data and the protocol description as received from the NEF.

[0058] At block 206, the PCF entity 312 provides at least one of the parameter for transmission of the service data and the protocol description to at least one of a User Plane Function (UPF) entity of the TCN, a Radio Access Network (RAN) of the TCN such as the RAN of the 5GS 100 and a User equipment (UE) connected to the TCN via a Session Management Function (SMF) entity of the TCN. In an example, in addition to theparameter for transmission of the service data and the protocol description included in the PCC rule, the PCF may also provide the media assistance data to at least one of the UPF entity of the TCN, the RAN and the UE by enclosing it as an object in the PCC rule or separately. At least one of the parameter for transmission of the service data, the media assistance data and the protocol description is configured to cause the UPF entity or the UE to determine media type of data received over the session. PCF interfaces with the SMF, SMF interfaces with the UPF and the SMF interfaces with the RAN / UE via a Access and Mobility Management Function (AMF) entity of the TCN.

[0059] The UPF may determine protocol data unit (PDU) sets or PDU set information corresponding to the session based on the information received from the SMF. The PDU set information may comprise PDU Set Sequence Number, indication of End PDU of the PDU Set, PDU Sequence Number within a PDU Set, PDU Set Size, PDU Set Importance value, which identifies the relative importance of a PDU Set compared to other PDU Sets within a QoS Flow. In an example, the UPF or UE may detect Data Burst and determine Data Burst parameters comprising End of Data Burst Indicator corresponding to the session. The PCF may provide the PCC rules 314 to a session management Function (SMF) entity 318 of the TCN as represented by the signal 316. The SMF entity 318 may provide the parameters for transmission of the service data and the protocol description (as indicated through data block 322 in Figure 2b) included in the PCC rules 314 to a User Plane Function (UPF) entity 324 of the TCN as represented by the signal 320 or to the UE 326 connected to the TCN or to the RAN.

[0060] In an example, the SMF entity 318 may also provide the media assistance data as received from the PCF entity 312 to at least one of the UPF entity 324, the UE 326, and the RAN. In an example, the SMF entity 318 maps the parameters for transmission of the service data, the protocol description and the media assistance information to a corresponding QoS flow which is used to transmit the service data or service data flow (SDF).Each QoS Flow is represented by a QoS Flow Identifier (QFI) and belongs to a PDU session. A QoS flow can be used to transmit multiple SDF entities having similar QoS requirements. The SMF entity 318 also determines the QoS profile comprising the QoS parameters, QoS rules to be sent to UE 326 comprising flow description information and QFI. The flow description information may comprise traffic assistance information (e.g., TSCAI) and the protocol description. The SMF entity 318 further determines packet detection rules (FDR) and corresponding QoS enforcement rules (QER). The PDR may include the flow description information that may comprise traffic assistance information (e.g., TSCAI) and protocol description for service data flow (SDF or PDU set) detection and the QFI of QoS Flow used to transmit the SDF. The SMF entity 318 sends the QoS profile to the NG- RAN, QoS rules to the UE 326 as represented through signal 328, and PDR and corresponding QER to the UPF entity 324 as represented through signal 320. The NG-RAN maps the QoS Flow to the appropriate radio bearer according to the QoS parameters of the QoS Flow, and allocates the corresponding radio resources. The transmission of the service data may then be started.

[0061] For downlink (DL) traffic, as described above, using the PDR, the UPF matches the downlink data, marks the QFI to the matched packet header according to the corresponding QER, and then sends the packets to the RAN through the PDU session level GPRS tunneling protocol-user plane (GTP-U) tunnel between the UPF entity 324 and the RAN. The UPF may use the protocol description included in the PDR to identity PDU sets and to derive PDU set information for identifying a PDU in the downlink data as belonging to a PDU set. The UPF entity 324 may send the PDU set information to RAN via DL GTP-U header of each PDU identified as belonging to a PDU Set. The GTP-U protocol entity provides packet transmission and reception services to user plane entities. The RAN receives packets from the GTP tunnel, identifies different QoS Flowsaccording to the QFI in the packet header, and then sends the packets to the UE 326 through the corresponding radio bearer.

[0062] In another embodiment, as mentioned above the SMF entity 318 provides the parameters 322 for transmission of the service data and the protocol description included in the PCC rules 314 to the UE 326 connected to the TCN. This embodiment is depicted using dotted lines in the signal flow illustrated in Figure 2b. Accordingly, the signal 328, represented by a dotted line, depicts the parameters 322 and protocol description included in the PCC rules 314 that the SMF entity 318 provides to the UE 326.

[0063] For uplink (UL) traffic, the UE 326 detects and matches the UL data with the flow description information containing traffic assistance information and protocol description in the QoS rule in order to determine the QoS Flow used to transmit the UL data. The UE 326 then marks the QFI to the matched packet header. The UE 326 then determines the corresponding radio bearer according to the QoS Flow, and sends the uplink PDU to the NG-RAN through the corresponding radio bearer. The NG-RAN sends the uplink data to the UPF entity 324 through the GTP tunnel of the PDU session.

[0064] Figure 3a illustrates a method 400 of providing media assistance data in a telecommunication network and Figure 3b illustrates corresponding signal flow, according to another example of the present subject matter. For the sake of ease of explanation, Figures 3a and 3b are explained in conjunction with each other.

[0065] The method 400 may be implemented by a processor(s) or computing device(s) through any suitable hardware, non-transitory machine-readable instructions, or combination thereof. It may be understood that blocks of the method 400 may be performed by computing devices programmed to perform the operations of a telecommunication network or a user equipment (UE). However, for ease of explanation, the present description of the example method 400 is provided in reference toa 5G system. Thus, in an example implementation, the method 400 may be performed by computing devices programmed to perform the operations of 5G Core Network (5GC) or the UE 106 and implemented in a 5G system such as the above-described 5GS system 100. The blocks of the method 400 may be executed based on instructions stored in a non-transitory computer readable medium, as will be readily understood. The non- transitory computer readable medium may include, for example, digital memories, magnetic storage media, such as magnetic disks and magnetic tapes, hard drives, or optically readable digital data storage media.

[0066] Referring to Figure 3a, at block 402, at least one of a User Plane Function (UPF) entity of a Telecommunication Core Network (TCN) or a User equipment (UE) connected to the TCN receives, media assistance data. The media assistance data may comprise application layer information. In an example, the media assistance data may also comprise parameter values to be used for a session as negotiated between endpoints of the session. In an example, the media assistance data comprises one of a session description protocol (SDP), a Real-time Transport Protocol (RTP) session information, a Dynamic Adaptive Streaming over HTTP (HTTP / DASH), session information or a Quick UDP Internet Connections (QUIC) related session information.

[0067] Further, as described above with reference to blocks 202, 204, and 206, the AF entity 302 may provide the media assistance data directly to the PCF entity 312, if it is an authorized PCF entity 312, or through the NEF entity 308 which authorizes the PCF entity 312 if the PCF entity 312 is a third party entity as indicated through the signals 504 and 506 in Figure 3b. The media assistance data may be provided in a container to the PCF entity 312. The container may be understood as an object to hold the parameter values to be used for the session as negotiated between endpoints of the session and application layer information. The object may hold information corresponding to SDP or corresponding to one of a Realtime Transport Protocol (RTP) session information, a Dynamic AdaptiveStreaming over HTTP (HTTP / DASH) session information, or a Quick UDP Internet Connections (QUIC) related session information. The PCF may enclose the container comprising media assistance data or a reference to the container comprising media assistance data in PCC rules. The media assistance information as included in the PCC rules may be forwarded, by the PCF entity 312 to the SMF entity 318 as indicated through signal 508. The SMF entity 318 may provide the media assistance data included in the PCC rules to the UPF entity 324 as represented by the signal 510 in Figure 3b or the UE 326 as represented by the signal 512 in Figure 3b. The SMF entity 318 may provide the media assistance data in the QoS rules to the UE 326. Further, the SMF entity 318 may provide the media assistance in the PDR to the UPF entity 324.

[0068] In an example embodiment, the UPF entity 324 or the UE 326 may also receive parameters for transmission of service data over the session and protocol description as determined by the PCF entity 312 or the NEF entity 308 of the TCN based at least in part on the media assistance data through the SMF entity 318. The parameter for transmission of the service data comprising QoS parameters and traffic assistance information (e.g., Time Sensitive Communication Assistance Information (TSCAI)).

[0069] At block 404, the UPF entity 324 or the UE 326 may detect PDU set and determine PDU set information corresponding to the session, based on the media assistance data. In an example, the UPF entity 324 or the UE 326 may detect a data burst and determine one or more data burst parameters comprising an end of data burst indicator corresponding to the session. In an embodiment, as mentioned above, for downlink (DL) traffic, using the media assistance information included in the PDR as received from the SMF entity 318, the UPF entity 324 may detect PDU set and determine PDU set information corresponding to the session. More specifically, the UPF entity 324 may use the media assistance information included in the PDR to detect PDU sets and to derive PDU set information for identifying a PDU in the downlink data as belonging to a PDU set. TheUPF entity 324 may send the PDU set information to RAN via DL GTP-U header of each PDU identified as belonging to a PDU Set. The UPF entity 324 matches the downlink data, marks the QFI to the matched packet or PDU header according to the corresponding QER, and then sends the PDUs to the RAN through the PDU session level GPRS tunneling protocoluser plane (GTP-U) tunnel between the UPF entity 324 and the RAN.

[0070] In another embodiment, the SMF entity 318 provides the media assistance data to the UE 326 as represented by the signal 512. This embodiment is depicted using dotted lines in the signal flow illustrated in Figure 3b. Accordingly, the signal 512, represented by a dotted line, depicts the media assistance data 502 that the SMF entity 318 provides to the UE 326. The SMF entity 318 may provide the media assistance data 502 in QoS rules sent to the UE 326.

[0071] For uplink (UL) traffic, the UE 326 detects and matches the UL data with the media assistance information that may be contained in the flow description information of the QoS rules in order to determine the QoS Flow used to transmit the UL data. The UE 326 then marks the QFI to the matched PDU header. The UE 326 then determines the corresponding radio bearer according to the QoS Flow, and sends the uplink packets to the RAN through the corresponding radio bearer. The RAN sends the uplink data to the UPF entity 324 through the GTP tunnel of the PDU session.

Claims

I / We Claim:1 . A method comprising: receiving, by a policy control function (PCF) entity or a Network Exposure Function (NEF) entity of a Telecommunication Network (TCN), media assistance data from an application function (AF) of the TCN, the media assistance data comprising application layer information; determining, by the PCF entity or the NEF entity, at least one of a parameter for transmission of service data over a session and a protocol description based at least in part on the media assistance data, the protocol description comprising media characteristics; providing, by the PCF entity or the NEF entity, at least one of the parameter for transmission of the service data, the media assistance data and the protocol description to at least one of a User Plane Function (UPF) entity of the TCN, a Radio Access Network (RAN) of the TCN, and a User equipment (UE) connected to the TCN via a Session Management Function (SMF) entity of the TCN.

2. The method as claimed in claim 1 , wherein at least one of the parameter for transmission of the service data, the media assistance data, and the protocol description is configured to cause the UPF entity or the UE to determine a media type of data received over the session, wherein determining the media type of the data comprises determining protocol data unit (PDU) sets or PDU set information corresponding to the session.

3. The method as claimed in claim 1 , wherein at least one of the parameter for transmission of the service data, the media assistance data, and the protocol description is configured to cause the UPF entity or the UE to determine protocol data unit (PDU) sets or PDU set information corresponding to the session.

4. The method as claimed in claim 1 , wherein the TCN is a 5- Generation Core Network (5GC).

5. The method as claimed in claim 1 , wherein the media assistance data further comprises one or more parameter values to be used for the session as negotiated between endpoints of the session, the session comprising one of a transport layer session or an application layer session.

6. The method as claimed in claim 5, wherein the media assistance data comprises one of a session description protocol (SDP) session information, a Real-time Transport Protocol (RTP) session information, a Dynamic Adaptive Streaming over HTTP (HTTP / DASH) session information, or a Quick UDP Internet Connections (QUIC) related session information.

7. The method as claimed in claim 1 , wherein the parameter for transmission of the service data comprises one or more of at least one quality of service (QoS) parameter or traffic assistance information.

8. The method as claimed in claim 7, wherein the at least one QoS parameter comprises Packet Delay Budget (PDB), Packet Error Rate (PER), PDU Set Error Rate (PSER), PDU Set Delay Budget (PSDB), or PDU Set Integrated Handling Indicator (PSIHI).

9. A method comprising: receiving, by a policy control function (PCF) entity of a Telecommunication Core Network (TCN), media assistance data from an application function (AF) of the TCN, the media assistance data comprising application layer information; generating, by the PCF entity, a Policy Charging and Control (PCC) rule based at least in part on the media assistance data, the PCC rulecomprising a parameter for transmission of service data over a session and a protocol description, the protocol description comprising media characteristics of the service data; providing, by the PCF entity, the PCC rule to a Session Management Function (SMF) entity of the TCN to cause the SMF entity to provide the parameter for transmission of the service data and the protocol description included in the PCC rule to at least one of a User Plane Function (UPF) entity of the TCN, a Radio Access Network of the TCN, and a User equipment (UE) connected to the TCN.

10. The method as claimed in claim 9, wherein at least one of the parameter for transmission of the service data and the protocol description is configured to cause the UPF entity or the UE to determine a media type of data received over the session, where to determine the media type of the data comprises to determine protocol data unit (PDU) sets or PDU set information corresponding to the session.11 . The method as claimed in claim 9, wherein the media assistance data further comprises parameter values to be used for the session as negotiated between endpoints of the session, the session comprising one of a transport layer session or an application layer session.

12. The method as claimed in claim 11 , wherein the media assistance data comprises one of a session description protocol (SDP), a Real-time Transport Protocol (RTP) session information, a Dynamic Adaptive Streaming over HTTP (HTTP / DASH) session information, or a Quick UDP Internet Connections (QUIC) related session information.

13. The method as claimed in claim 9, wherein the parameter for transmission of the service data comprises one or more of at least one quality of service (QoS) parameter or traffic assistance information, the atleast one QoS parameter comprising Packet Delay Budget (PDB), Packet Error Rate (PER), PDU Set Error Rate (PSER), PDU Set Delay Budget (PSDB), or PDU Set Integrated Handling Indicator (PS I HI) .

14. A method comprising: receiving, by at least one of a User Plane Function (UPF) entity of a Telecommunication Core Network (TCN) or a User equipment (UE) connected to the TCN, media assistance data, wherein the media assistance data comprises application layer information; and detecting, by the UPF entity or the UE, a PDU set and determining PDU set information corresponding to the session based on the media assistance data.

15. The method as claimed in claim 14, wherein the method further comprises receiving, by the UPF entity or the UE, a parameter for transmission of service data over the session and protocol description determined by a policy control function (PCF) entity or a Network Exposure Function (NEF) entity of the TCN based at least in part on the media assistance data, the parameter for transmission of the service data comprising a QoS parameter and traffic assistance information.

16. The method as claimed in claim 15, wherein the method further comprises detecting the PDU set and determining PDU set information corresponding to the session, by the UPF entity or the UE, based on at least one of the media assistance data, the parameter for transmission of service data and the protocol description.

17. The method as claimed in any one of claim 14, wherein the PDU set information comprises PDU set importance value.

18. The method as claimed in claim 14, wherein the method further comprises detecting a data burst and determining one or more data burst parameters comprising an end of data burst indicator corresponding to the session.

19. The method as claimed in claim 14, wherein the media assistance data comprises one of a session description protocol (SDP) session information, a Real-time Transport Protocol (RTP) session information, a Dynamic Adaptive Streaming over HTTP (HTTP / DASH) session information, or a Quick UDP Internet Connections (QUIC) related session information.

20. The method as claimed in claim 15, wherein the QoS parameter comprises Packet Delay Budget (PDB), Packet Error Rate (PER), PDU Set Error Rate (PSER), PDU Set Delay Budget (PSDB), or PDU Set Integrated Handling Indicator (PSIHI).21 . The method as claimed in claim 14, wherein the media assistance information is provided by an Application Function (AF) entity to a Session Management Function (SMF) entity, by the Policy Control Function (PCF) entity either directly or via the Network Exposure Function (NEF) entity of the TCN, and wherein the at least one of the UPF entity or the UE receives the media assistance information from the Session Management Function (SMF) entity.

Images