Method and apparatus for optimizing configuration of extension header for protocol data unit of communication system

Abstract

Techniques are provided for removal of header extensions to mitigate packet fragmentation. In the context of an application function, based on determining a protocol description indicating protocol data unit (PDU) set information related to augmented reality data, transmission of a processing request for a PDU set is caused, the processing request including at least a request for removing a header extension related to the PDU set. In addition, transmission of at least one PDU of the set of PDUs containing the header extension is caused based on an indication that the header extension is removable by a user plane function of the core network. Corresponding methods, apparatuses, and computer-readable storage media for the core network, the user plane function, and the user equipment are also provided.

Description

Technical Field

[0001] Various example embodiments described in the subject disclosure relate generally to wireless communications techniques and, more particularly, to techniques for configuring protocol data units for wireless communications. Background Art

[0002] A communication system can be viewed as a facility that enables communication sessions between two or more entities (such as user equipment (UE), base stations / access points, network functions (NFs) and / or other nodes) by providing connectivity between the various entities involved in the communication path. For example, a communication system may be provided with a communication network and one or more compatible communication devices. Communication systems continue to evolve to extend the flexibility of network use, provide improved security and / or provide improved network services to users. For example, the fourth generation (4G) wireless mobile telecommunication technology (also known as long-term evolution (LTE) technology) is designed to provide high-capacity mobile multimedia with high data rates, in particular for human-machine interaction. The next generation or fifth generation (5G) technology is intended to be used not only for human-machine interaction, but also for machine-type communications in so-called Internet of Things (IoT) networks.

[0003] The Third Generation Partnership Project (3GPP) has developed standards for 5G technology, including standards for next-generation radio access networks and 5G network architectures that can provide ultra-wideband, ultra-strong, low-latency connectivity, and high data rate low-latency connectivity for interactive media services. 5G technology improves the various telecommunication services provided to end users and helps support large-scale broadband that can deliver gigabytes of bandwidth per second on demand for both uplink and downlink transmissions. Next-generation networks based on 5G network architecture use radio access network (RAN) functions and core network functions to send data, such as extended reality data, via protocol data units (PDUs). These PDUs can be grouped into PDU sets, which include one or more PDUs that carry a payload of an information unit generated at the application level (e.g., a video frame or video slice for an extended reality service). However, in some scenarios under current network protocols, PDUs may be inefficiently configured and / or sent via the network. Summary of the invention

[0004] Various example embodiments are generally directed to techniques for removing header extensions. In example embodiments, the method, apparatus, and computer program product are configured to control removal of header extensions, thereby allowing for mitigation of packet fragmentation.

[0005] In an example embodiment, a method is provided, comprising: based on determining a protocol description indicating a protocol data unit (PDU) set information related to extended reality, causing transmission of a processing request for the PDU set, the processing request comprising at least a request to remove a header extension related to the PDU set. The method further comprises: based on an indication that the header extension is removable by a user plane function of a core network, causing transmission of at least one PDU in the PDU set including the header extension.

[0006] The method of an example embodiment includes a header extension, wherein the header extension is a real-time protocol (RTP) header extension. In an example embodiment, the protocol description includes information about the header extension. In an example embodiment, the protocol description includes information about at least one of: an application protocol, a header type, and / or a payload type. In an example embodiment, causing transmission of a processing request includes causing transmission of a processing request to a policy control function of a core network.

[0007] The method of an example embodiment, causing transmission of the at least one PDU comprises causing transmission of the at least one PDU including the header extension to a user plane function to facilitate removal of the header extension from the at least one PDU via the user plane function.

[0008] The method of an example embodiment, causing transmission of at least one PDU includes causing transmission of at least one PDU including a header extension to a user plane function to facilitate providing the at least one PDU without the header extension to a user equipment. In an example embodiment, the processing request also includes a protocol description for the PDU set.

[0009] In another example embodiment, an apparatus is provided that includes at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to: based on determining a protocol description indicating a protocol data unit (PDU) set information related to extended reality data, cause transmission of a processing request for the PDU set, the processing request including at least a request to remove a header extension related to the PDU set. The apparatus is also caused to cause transmission of at least one PDU of the PDU set including the header extension based on an indication that the header extension is removable by a user plane function of a core network.

[0010] The apparatus of the example embodiment includes a header extension, wherein the header extension is a real-time protocol (RTP) header extension. In an example embodiment, the protocol description includes information about the header extension. In an example embodiment, the protocol description includes information about at least one of: an application protocol, a header type, and / or a payload type. In an example embodiment, causing transmission of the processing request includes causing transmission of the processing request to a policy control function of the core network.

[0011] The apparatus of the example embodiment, causing transmission of the at least one PDU comprises causing transmission of the at least one PDU including the header extension to a user plane function to facilitate removal of the header extension from the at least one PDU via the user plane function.

[0012] The apparatus of an example embodiment, causing transmission of at least one PDU includes causing transmission of at least one PDU including a header extension to a user plane function to facilitate providing the at least one PDU without the header extension to a user equipment. In an example embodiment, the processing request also includes a protocol description for the PDU set.

[0013] In another example embodiment, a non-transitory computer-readable storage medium is provided, including program instructions stored thereon, the program instructions being used to: based on determining a protocol description indicating a protocol data unit (PDU) set information related to extended reality data, cause transmission of a processing request for the PDU set, the processing request comprising at least a request to remove a header extension related to the PDU set. The program instructions are also used to: based on an indication that the header extension is removable by a user plane function of a core network, cause transmission of at least one PDU of the PDU set including the header extension.

[0014] In an example embodiment, the header extension is a real-time protocol (RTP) header extension. In an example embodiment, the protocol description includes information about the header extension. In an example embodiment, the protocol description includes information about at least one of: an application protocol, a header type, and / or a payload type. The program instructions for causing transmission of the processing request include causing transmission of the processing request to a policy control function of the core network.

[0015] The program instructions for causing transmission of at least one PDU include causing transmission of the at least one PDU including a header extension to a user plane function to facilitate removal of the header extension from the at least one PDU via the user plane function.

[0016] The program instructions for causing transmission of at least one PDU include causing transmission of the at least one PDU including a header extension to a user plane function to facilitate providing the at least one PDU without the header extension to a user equipment. In an example embodiment, the processing request also includes a protocol description for the PDU set.

[0017] In yet another example embodiment, an apparatus is provided, comprising: means for causing transmission of a processing request for a protocol data unit (PDU) set based on determining a protocol description indicating information of a PDU set related to extended reality data, the processing request comprising at least a request for removing a header extension related to the PDU set. The apparatus further comprises: means for causing transmission of at least one PDU of the PDU set including the header extension based on an indication that the header extension is removable by a user plane function of a core network.

[0018] In an example embodiment, the header extension is a real-time protocol (RTP) header extension. In an example embodiment, the protocol description includes information about the header extension. In an example embodiment, the protocol description includes information about at least one of: an application protocol, a header type, and / or a payload type. In an example embodiment, the apparatus for causing transmission of the processing request includes causing transmission of the processing request to a policy control function of the core network.

[0019] The apparatus of an example embodiment, means for causing transmission of at least one PDU comprises causing transmission of the at least one PDU including a header extension to a user plane function to facilitate removal of the header extension from the at least one PDU via the user plane function.

[0020] The apparatus of an example embodiment, the means for causing transmission of at least one PDU includes causing transmission of at least one PDU including a header extension to a user plane function to facilitate providing the at least one PDU without the header extension to a user equipment. In an example embodiment, the processing request also includes a protocol description for the PDU set.

[0021] In an example embodiment, a method is provided, comprising: receiving a processing request for a set of protocol data units (PDUs) from an application function of a core network, the processing request comprising a protocol description and a request for removing a header extension associated with the set of PDUs. The method further comprises determining, based on the protocol description, that a user plane function of the core network is capable of removing the header extension for the set of PDUs. The method further comprises causing a rule indication to be provided to the user plane function for removing the header extension associated with the set of PDUs.

[0022] In an example embodiment, the header extension is a real-time protocol (RTP) header extension. The method of the example embodiment also includes: based on determining that the user plane function can remove the header extension associated with the PDU set, sending a response to the application function. In an example embodiment, the protocol description includes information about the header extension. In an example embodiment, the protocol description includes information about at least one of: an application protocol, a header type, and / or a payload type.

[0023] In another example embodiment, an apparatus is provided, comprising at least one processor and at least one memory storing instructions, the instructions, when executed by the at least one processor, causing the apparatus to: receive a processing request for a protocol data unit (PDU) set from an application function of a core network, the processing request comprising a protocol description and a request for removing a header extension associated with the PDU set. The apparatus is also caused to: determine, based on the protocol description, that a user plane function of the core network is capable of removing a header extension for the PDU set. The apparatus is also caused to: cause a rule indication to be provided to the user plane function for removing the header extension associated with the PDU set.

[0024] In an example embodiment, the header extension is a real-time protocol (RTP) header extension. The apparatus of an example embodiment, the instructions when executed by at least one processor further cause the apparatus to: send a response to an application function based on determining that the user plane function is capable of removing the header extension associated with the PDU set. In an example embodiment, the protocol description includes information about the header extension. In an example embodiment, the protocol description includes information about at least one of: an application protocol, a header type, and / or a payload type.

[0025] In another embodiment, a non-transitory computer-readable storage medium is provided, comprising program instructions stored thereon, the program instructions being used to: receive a processing request for a protocol data unit (PDU) set from an application function of a core network, the processing request comprising a protocol description and a request for removing a header extension associated with the PDU set. The program instructions are also used to: determine, based on the protocol description, that a user plane function of the core network is capable of removing a header extension for the PDU set. The instructions are also used to: cause a rule indication to be provided to the user plane function for removing a header extension associated with the PDU set.

[0026] In an example embodiment, the header extension is a real-time protocol (RTP) header extension. The program instructions of the example embodiment are further configured to: based on determining that the user plane function can remove the header extension associated with the PDU set, send a response to the application function. In an example embodiment, the protocol description includes information about the header extension. In an example embodiment, the protocol description includes information about at least one of: an application protocol, a header type, and / or a payload type.

[0027] In yet another example embodiment, an apparatus is provided that includes means for receiving a processing request for a set of protocol data units (PDUs) from an application function of a core network, the processing request including a protocol description and a request for removing header extensions associated with the set of PDUs. The apparatus also includes means for determining, based on the protocol description, that a user plane function of the core network is capable of removing header extensions for the set of PDUs. The apparatus also includes means for causing a rule indication to be provided to the user plane function for removing header extensions associated with the set of PDUs.

[0028] In an example embodiment, the header extension is a real-time protocol (RTP) header extension. The apparatus of the example embodiment further comprises: means for sending a response to the application function based on determining that the user plane function is capable of removing the header extension associated with the PDU set. In an example embodiment, the protocol description comprises information about the header extension. In an example embodiment, the protocol description comprises information about at least one of: an application protocol, a header type, and / or a payload type.

[0029] In an example embodiment, a method is provided that includes: receiving an indication from a policy control function of a core network to remove a header extension for a set of protocol data units (PDUs). The method also includes: receiving from an application function at least one PDU of the set of PDUs that includes the header extension. The method also includes: in response to receiving the at least one PDU, causing removal of the header extension from the at least one PDU and adjusting one or more parameters for the at least one PDU.

[0030] In an example embodiment, the header extension is a real-time protocol (RTP) header extension. The method of the example embodiment further comprises: determining at least one PDU set parameter for a PDU set based on the header extension, and causing removal of the header extension from the PDU based on the at least one PDU set parameter. In the example embodiment, the method further comprises: adding a GPRS tunneling protocol-user plane header extension including the at least one PDU set parameter to a GPRS tunneling protocol-user plane header of the PDU. In the example embodiment, the method further comprises: sending at least one PDU to at least one radio access network.

[0031] In another example embodiment, an apparatus is provided that includes at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to: receive an indication from a policy control function of a core network to remove a header extension for a set of protocol data units (PDUs). The apparatus is also caused to: receive at least one PDU of the set of PDUs including the header extension from an application function. The apparatus is also caused to: in response to receiving the at least one PDU, cause the removal of the header extension from the at least one PDU and adjust one or more parameters for the at least one PDU.

[0032] In an example embodiment, the header extension is a real-time protocol (RTP) header extension. The apparatus of the example embodiment, when executed by at least one processor, further causes the apparatus to: determine at least one PDU set parameter for a PDU set based on the header extension, and cause removal of the header extension from the PDU based on the at least one PDU set parameter. The apparatus of the example embodiment, when executed by at least one processor, further causes the apparatus to: add a GPRS tunneling protocol-user plane header extension including the at least one PDU set parameter to a GPRS tunneling protocol-user plane header of the PDU. The apparatus of the example embodiment, when executed by at least one processor, further causes the apparatus to: send at least one PDU to at least one radio access network.

[0033] In another example embodiment, a non-transitory computer-readable storage medium is provided, comprising program instructions stored thereon, the program instructions for: receiving an indication from a policy control function of a core network for removing a header extension for a set of protocol data units (PDUs). The program instructions are also for: receiving at least one PDU of the set of PDUs including a header extension from an application function. The program instructions are also for: in response to receiving the at least one PDU, causing the removal of the header extension from the at least one PDU and adjusting one or more parameters for the at least one PDU.

[0034] In an example embodiment, the header extension is a real-time protocol (RTP) header extension. The instructions of the example embodiment are further configured to: determine at least one PDU set parameter for a PDU set based on the header extension, and cause the removal of the header extension from the PDU based on the at least one PDU set parameter. In this example embodiment, the instructions are further configured to: add a GPRS tunneling protocol-user plane header extension including the at least one PDU set parameter to a GPRS tunneling protocol-user plane header of the PDU. In this example embodiment, the instructions are further configured to: send at least one PDU to at least one radio access network.

[0035] In yet another example embodiment, an apparatus is provided that includes: means for receiving an indication for removing a header extension for a set of protocol data units (PDUs) from a policy control function of a core network. The apparatus also includes: means for receiving at least one PDU of the set of PDUs including the header extension from an application function. The apparatus also includes: means for causing removal of the header extension from the at least one PDU in response to receiving the at least one PDU, and means for adjusting one or more parameters for the at least one PDU.

[0036] In an example embodiment, the header extension is a real-time protocol (RTP) header extension. The apparatus of the example embodiment further comprises: means for determining at least one PDU set parameter for a PDU set based on the header extension, and means for causing removal of the header extension from the PDU based on the at least one PDU set parameter. In the example embodiment, the apparatus further comprises: means for adding a GPRS Tunneling Protocol-User Plane header extension including the at least one PDU set parameter to a GPRS Tunneling Protocol-User Plane header of the PDU. In the example embodiment, the apparatus further comprises: means for sending at least one PDU to at least one radio access network.

[0037] In an example embodiment, a method is provided, comprising: receiving a quality of service (QoS) rule from a system management function of a core network, the quality of service (QoS) rule comprising an indication for removing a header extension for a set of protocol data units (PDUs). The method further comprises: receiving at least one PDU of the set of PDUs including the header extension from an application. The method further comprises: in response to receiving the at least one PDU, causing removal of the header extension from the at least one PDU and adjusting one or more parameters for the at least one PDU. The method further comprises: causing transmission of the at least one PDU without the header extension to at least one radio access network.

[0038] In an example embodiment, the header extension is a real time protocol (RTP) header extension.In an example embodiment, causing transmission of the at least one PDU comprises causing transmission of the at least one PDU without the header extension to a user plane function via the radio access network.

[0039] In another example embodiment, a device is provided, comprising at least one processor and at least one memory storing instructions, which instructions, when executed by the at least one processor, cause the device to: receive a quality of service (QoS) rule from a system management function of a core network, the quality of service (QoS) rule including an indication for removing a header extension for a set of protocol data units (PDUs). The device is also configured to: receive at least one PDU of the set of PDUs including a header extension from an application. The device is also configured to: in response to receiving the at least one PDU, cause removal of the header extension from the at least one PDU and adjust one or more parameters for the at least one PDU. The device is also caused to: cause transmission of the at least one PDU without the header extension to at least one radio access network.

[0040] In an example embodiment, the header extension is a real time protocol (RTP) header extension.In an example embodiment, causing transmission of the at least one PDU comprises causing transmission of the at least one PDU without the header extension to a user plane function via the radio access network.

[0041] In another example embodiment, a non-transitory computer-readable storage medium is provided, comprising program instructions stored thereon, the program instructions for receiving a quality of service (QoS) rule from a system management function of a core network, the quality of service (QoS) rule comprising an indication for removing a header extension for a set of protocol data units (PDUs). The program instructions are also used to: receive at least one PDU of the set of PDUs including a header extension from an application. The instructions are also used to: in response to receiving the at least one PDU, cause the removal of the header extension from the at least one PDU, and adjust one or more parameters for the at least one PDU. The device is also used to: cause transmission of the at least one PDU without the header extension to at least one radio access network.

[0042] In an example embodiment, the header extension is a real time protocol (RTP) header extension.In an example embodiment, causing transmission of the at least one PDU comprises causing transmission of the at least one PDU without the header extension to a user plane function via the radio access network.

[0043] In yet another example embodiment, an apparatus is provided that includes means for receiving a quality of service (QoS) rule from a system management function of a core network, the quality of service (QoS) rule including an indication for removing a header extension for a set of protocol data units (PDUs). The apparatus also includes means for receiving at least one PDU of the set of PDUs including the header extension from an application. The apparatus also includes means for causing removal of the header extension from the at least one PDU in response to receiving the at least one PDU, and means for adjusting one or more parameters for the at least one PDU. The apparatus also includes means for causing transmission of the at least one PDU without the header extension to at least one radio access network.

[0044] In an example embodiment, the header extension is a real time protocol (RTP) header extension.In an example embodiment, causing transmission of the at least one PDU comprises causing transmission of the at least one PDU without the header extension to a user plane function via the radio access network.

[0045] The above content of the invention is provided only for the purpose of summarizing some example embodiments, in order to provide a basic understanding of some aspects of the present subject disclosure. Therefore, it will be understood that the above example embodiments are merely examples and should not be interpreted as narrowing the scope or spirit of the present subject disclosure in any way. It will be understood that, in addition to the embodiments summarized here, the scope of the present subject disclosure also covers many potential example embodiments, some of which will be further described below. Other features, aspects and advantages of the present subject disclosure will become apparent from the description, drawings and / or claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0046] Having generally described certain example embodiments of the subject disclosure, reference will now be made to the accompanying drawings which are not drawn to scale, and in which:

[0047] Figure 1 An example of a communication system according to an example embodiment of the subject disclosure is shown;

[0048] Figure 2 shows a block diagram of an apparatus that may be configured according to an example embodiment of the subject disclosure;

[0049] Figure 3 A block diagram illustrating an example architecture for protocol data unit set processing for extended reality according to various example embodiments of the subject disclosure;

[0050] Figure 4A A signal diagram in a downlink configuration illustrating operation according to an example embodiment of the subject disclosure;

[0051] Figure 4B A signal diagram in a downlink configuration illustrating operation according to an example embodiment of the subject disclosure;

[0052] Figure 5A A signal diagram in an uplink configuration illustrating operation according to an example embodiment of the subject disclosure;

[0053] Figure 5B A signal diagram in an uplink configuration illustrating operation according to an example embodiment of the subject disclosure;

[0054] Figure 6 An example workflow implemented by application functions according to an example embodiment of the subject disclosure is shown;

[0055] Figure 7 An example workflow implemented by a core network including a policy control function according to an example embodiment of the subject disclosure is shown;

[0056] Figure 8 shows an example workflow implemented by a user plane function according to an example embodiment of the subject disclosure; and

[0057] Fig. 9 An example workflow implemented by a user device according to an example embodiment of the subject disclosure is shown. DETAILED DESCRIPTION

[0058] Some example embodiments of the subject disclosure will now be described more fully with reference to the accompanying drawings, in which some, but not all, example embodiments are shown. In fact, the various example embodiments of the subject disclosure may be embodied in many different forms and should not be construed as limited to the example embodiments described herein; on the contrary, these example embodiments are provided so that the subject disclosure will satisfy applicable legal requirements. The same reference numerals always refer to the same elements. As used herein, the terms "data," "content," "information," and similar terms may be used interchangeably to refer to data that can be sent, received, and / or stored according to the example embodiments of the subject disclosure. Therefore, the use of any such terms should not be considered to limit the spirit and scope of the example embodiments of the subject disclosure.

[0059] Additionally, as used herein, the term "circuitry" refers to (a) a hardware circuit implementation only (e.g., an implementation in analog circuitry and / or digital circuitry); (b) a combination of circuitry and (multiple) computer program products, including software and / or firmware instructions stored on one or more computer-readable memories, that work together to cause the device to perform one or more functions described herein; and (c) circuitry, such as, for example, (multiple) microprocessors or a portion of (multiple) microprocessors, that requires software or firmware to operate even if the software or firmware is not physically present. This definition of "circuitry" applies to all uses of the term herein, including in any claims. As a further example, the term "circuitry" as used herein also includes an implementation including one or more processors and / or (multiple) portions thereof and accompanying software and / or firmware. As another example, the term "circuitry" as used herein also includes, for example, a baseband integrated circuit or application processor integrated circuit for a mobile phone or a similar integrated circuit in a server, cellular network equipment, other network equipment (such as a core network device), a field programmable gate array, and / or other computing devices.

[0060] The term "comprising" means including, but not limited to, and should be interpreted in the manner commonly used in the patent context. The use of broader terms such as comprises, includes, and having should be understood to provide support for narrower terms such as consisting of, consisting essentially of, and consisting essentially of. In addition, to the extent that the terms "includes" and "including" and variations thereof are used in the detailed description or claims, these terms are intended to be inclusive in a manner similar to the term "comprising."

[0061] The phrases "in one embodiment," "in an example embodiment," "according to one embodiment," "according to an example embodiment," "in some embodiments," "in some example embodiments," "in various embodiments," "in various example embodiments," and the like generally refer to that a particular feature, structure, or characteristic following the phrase may be included in at least one example embodiment of the subject disclosure, but not necessarily in all example embodiments of the subject disclosure. Thus, a particular feature, structure, or characteristic may be included in more than one example embodiment of the subject disclosure, such that these phrases are not necessarily referring to the same example embodiment.

[0062] As used herein, the terms "example," "exemplary," and the like are used to mean "serving as an example, instance, or illustration." Any implementation, aspect, or design described herein as "example" or "exemplary" is not necessarily to be construed as preferred or advantageous over other implementations, aspects, or designs. Rather, the use of the terms "example," "exemplary," and the like are intended to present concepts in a concrete manner.

[0063] If the specification states that "may", "can", "could", "should", "will", "preferably", "possibly", "usually", "optionally", "for example", "often" or "might" (or other such language) are included or have a certain characteristic, then that particular component or feature need not be included or have that characteristic. In some example embodiments, such components or features may be optionally included, or may be excluded.

[0064] As used herein, the term "computer-readable medium" refers to non-transient storage hardware, non-transient storage devices, or non-transient computer system memory, which can be accessed by a controller, a microcontroller, a computing system, or a module of a computing system to encode computer executable instructions or software programs thereon. Non-transient "computer-readable medium" can be accessed by a computing system or a module of a computing system to obtain and / or execute computer executable instructions or software programs encoded on the medium. Examples of non-transient computer-readable media may include, but are not limited to, one or more types of hardware memory, non-transient tangible media (e.g., one or more magnetic storage disks, one or more optical disks, one or more USB flash drives), computer system memory, or random access memory (such as DRAM, SRAM, EDO RAM), etc. The term "non-transient" used herein is a limitation of the medium itself (e.g., tangible, not a signal), rather than a limitation on data storage persistence (e.g., RAM vs. ROM).

[0065] As used herein, “at least one of: ” and “at least one of ” and similar expressions, where a list of two or more elements is connected by “and” or “or”, mean at least any one element, or at least any two or more elements, or at least all elements.

[0066] This article will illustrate example embodiments in conjunction with example communication systems and associated technologies to optimize the configuration of extended headers for protocol data units of communication systems. However, it should be understood that the scope of the claims is not limited to the specific type of communication system and / or process disclosed. The example embodiments can be implemented using one or more processes and operations in a network (e.g., a core network) or a terminal device (e.g., a user device) of a communication system. For example, although described in the context of a wireless cellular system utilizing 3GPP system elements (such as a 3GPP next-generation core network), the disclosed example embodiments can be adapted to various other types of communication systems in a straightforward manner. In addition, although the present subject disclosure can describe various example embodiments in conjunction with a fifth-generation (5G) communication system, the present subject disclosure is also applicable to and includes other networks and network technologies, such as 3G, 4G, long-term evolution (LTE), sixth generation (6G), etc., but is not limited thereto.

[0067] According to the exemplary example embodiments implemented in the 5G communication system environment, one or more 3GPP technical specifications (TS) and technical reports (TR) further explain the user equipment and core network elements / entities / functions and / or the operations performed by the user equipment and core network elements / entities / functions, such as 3GPP TS23.700-60, 3GPP TS23.501, 3GPP TS23.502 and / or 3GPP TS23.503. Other 3GPP TS / TR documents provide other conventional details that will be appreciated by those of ordinary skill in the art. However, while the example embodiments are well suited for implementations associated with the above-mentioned 5G 3GPP standards, the alternative embodiments are not necessarily intended to be limited to any particular standard.

[0068] like Figure 1 As shown, a communication system 100 is provided according to various example embodiments disclosed in the subject matter. In one or more example embodiments, the communication system 100 may include one or more terminal devices (e.g., user devices) and one or more networks (e.g., one or more communication networks). In various example embodiments, the communication system 100 is an environment that includes or corresponds to a 5G communication system (e.g., a 5G communication network) associated with one or more terminal devices (e.g., user devices) and / or one or more networks (e.g., one or more communication networks) that support 5G communication. However, Figure 1The description of the communication system 100 in the description is not intended to limit or otherwise restrict the example embodiments described and contemplated herein to any particular component or network configuration, nor is it intended to exclude any alternative configurations or systems for the collection of configurations and systems that may be used in conjunction with the embodiments of the subject disclosure. Instead, Figure 1 The communication system 100 disclosed therein is presented merely to provide an example basis and context to facilitate describing some features, aspects, and uses of the methods, apparatus, and computer program products disclosed and contemplated herein. It will be understood that although Figure 1 Many of the aspects and components presented in are shown as discrete, separate elements, but other configurations may be used in conjunction with the methods, apparatus, and computer programs described herein, including configurations that combine, omit, and / or add aspects and / or components.

[0069] In some example embodiments, the communication system 100 may include at least one user equipment (UE) 110 and at least one network component 111, which are capable of communicating with each other and receiving uplink (UL) and / or downlink (DL) transmissions. The at least one network component 111 may be a radio access network (RAN) component, a core network (CN) component, a data network (DN) component, an application server component, an application function, and / or another type of network component. In one or more example embodiments, the at least one network component 111 may be a network element and may be embodied by any of a variety of access points, including, for example, a NodeB, e.g., a gNB, etc. The UE 110 may be configured to operate in two or more frequency bands, such as three or four frequency bands in some example embodiments. For at least some (but not necessarily all) frequency bands, the UE 110 and / or the at least one network component 111 may be configured to remove header extensions (e.g., real-time protocol (RTP) header extensions) associated with a protocol data unit (PDU). Typically, RTP header extensions can be utilized for XR, and when the RTP header is to be utilized between an endpoint and a 5GS, it can be included between an application client and an application server (e2e). However, including an RTP header extension in a PDU and / or PDU set may waste resources (especially on the air interface) and may further cause fragmentation of the PDU on N6 because the additional overhead causes the PDU to exceed the maximum packet size (typically 1500 bytes for Ethernet). In addition, RTP has traditionally been utilized for the e2e protocol. Therefore, in various example embodiments disclosed herein, including an RTP header extension in a PDU and / or PDU set can be negotiated between an endpoint and a 5GS. In addition, in various example embodiments disclosed herein, the RTP header extension is not sent e2e, but is removed by the 5GS (UE or user plane function (UPF)) when the PDU containing the header extension is received. By negotiating the inclusion of RTP header extensions in PDUs and / or PDU sets, utilization of network resources (e.g., air interface resources) can be optimized and / or fragmentation of PDUs on N6 can be mitigated. For example, RTP header extension removal can be utilized to remove information not required by an application and / or to avoid packet fragmentation in a tunnel between the RAN and the UPF.

[0070] As described below, the apparatus, methods, and computer program products of the example embodiments are configured to implement removal of header extensions to reduce bandwidth of data sent via the communication system 100, remove unneeded bits for transmissions associated with the communication system 100, and / or mitigate packet fragmentation during data transmissions via the communication system 100.

[0071] By way of example, the communication system 100 may be deployed within a radio access architecture based on Long Term Evolution Advanced (LTE Advanced, LTE-A) and / or New Radio (NR, 5G). However, the system may be deployed within other network architectures, including other communication networks, for example, other communication networks developed in the future, such as 6G networks, and any of a number of existing networks, including Universal Mobile Telecommunications System (UMTS) Radio Access Network (UTRAN or E-UTRAN), Wireless Local Area Network (WLAN or Wi-Fi), Worldwide Interoperability for Microwave Access (WiMAX), Personal Communications Service (PCS), Wideband Code Division Multiple Access (WCDMA), systems using Ultra-Wideband (UWB) technology, sensor networks, mobile ad hoc networks (MANETs), and Internet Protocol Multimedia Subsystem (IMS), or any combination thereof.

[0072] UE 110 may be any type of user terminal, terminal device, etc. to which resources on the air interface are allocated and assigned. For example, UE may be a portable computing device, such as a wireless mobile communication device, including but not limited to the following types of devices: mobile station (mobile phone), smart phone, virtual reality device, augmented reality device, personal digital assistant (PDA), mobile phone, device using wireless modem (alarm or measurement device, etc.), laptop and / or touch screen computer, tablet computer, game console, notebook and multimedia device. User equipment may also be referred to as a subscriber unit, mobile station, remote terminal, access terminal or user terminal, to name just a few names or devices.

[0073] In some example embodiments, at least one network component 111 may be associated with one or more cellular access points. In some example embodiments, at least one network component 111 may define and / or serve one or more cells. In one or more example embodiments, one or more access points may communicate with a network (such as a core network) via a gateway, such that the one or more access points establish a cellular wireless access network through which UE 102 may communicate with at least one network component 111.

[0074] Although not shown, the communication system 100 may also include a controller associated with one or more access points (such as base stations), for example, to facilitate operation of the access points and management of the UEs 102 communicating therewith. Figure 1As shown, the communication system 100 may also include one or more wireless local area networks (WLANs), each of which may be served by a WLAN access point configured to establish wireless communications with the UE 102. Thus, the UE 102 may communicate with at least one network component 111 via the WLAN access point. In various example embodiments, the at least one network component 111 may include additional network elements, such as routers, switches, servers, gateways, and / or controllers, to facilitate communications with the UE 102.

[0075] In some example embodiments, the communication system 100 or its components (e.g., base stations, towers, etc.) may be configured to communicate with communication devices (e.g., UE 102), such as mobile phones, etc., over multiple different frequency bands (e.g., FR1 (below 6 GHz), FR2 (millimeter wave), other suitable frequency bands, sub-bands thereof, etc.). In some example embodiments, the communication network 100 may include or employ massive multiple-input multiple-output (massive MIMO) antennas. In some example embodiments, the communication system 100 may include multi-user MIMO (MU-MIMO) antennas. In some example embodiments, the communication system 100 may employ edge computing, whereby computing servers are closer to communication devices (e.g., UE 102) in communication, physical, computational, and / or temporal terms to reduce latency and data traffic congestion. In some example embodiments, the communication system 100 may employ other technologies, devices, or methods, such as small cells, low-power RAN, beamforming of radio waves, WIFI-cellular convergence, non-orthogonal multiple access (NOMA), channel coding, etc.

[0076] Reference now Figure 2 , an example apparatus 200 is provided. The apparatus 200 may be an embodiment of a UE 110, a RAN component 120, an application function (AF) 130, a user plane function (UPF) 140, a policy control function (PCF) 150A, and / or a session management function (SMF) 150B, such as Figure 3 In one or more example embodiments, AF 130, UPF 140, and / or PCF 150A may be integrated in a core network that communicates with or is otherwise associated with UE 110. Alternatively, apparatus 200 may be an embodiment of another type of network element, or may be embodied by or otherwise associated with another type of network element, such as, for example, an access point.

[0077] The apparatus 200 includes a processor 202, a memory 204, and / or a network interface 206. The apparatus 200 may be configured to perform one or more operations described herein. Although these components are described with respect to the execution of various functions, it should be understood that a particular implementation necessarily includes the use of specific hardware. It should also be understood that some of these components may include similar or common hardware. For example, two sets of circuit systems may utilize the same processor, network interface, storage medium, etc. to perform their associated functions, so that each set of circuit systems does not require duplicate hardware.

[0078] In some example embodiments, the processor 202 (and / or a coprocessor or any processing circuitry assisting or otherwise associated with the processor) may communicate with the memory 204 via a bus to transfer information between components of the apparatus 200. The memory 204 is non-transitory and may include, for example, one or more volatile and / or non-volatile memories. In other words, for example, the memory 204 may be an electronic storage device (e.g., a computer-readable storage medium). The memory 204 may be configured to store information, data, content, applications, instructions, etc. to enable the apparatus 200 to perform various functions according to the example embodiments disclosed herein.

[0079] The processor 202 may be embodied in a variety of different ways, and may include, for example, one or more processing devices configured to execute independently. In some non-limiting embodiments, the processor 202 may include one or more processors configured in series via a bus to enable independent execution of instructions, pipelining, and / or multithreading. The use of the term "processor" may be understood to include a single-core processor, a multi-core processor, multiple processors within the device 200, and / or a remote or "cloud" processor.

[0080] In some example embodiments, the processor 202 may be configured to execute instructions stored in the memory 204 and / or the circuit system accessible to the processor 202. In some example embodiments, the processor 202 may be configured to perform hard-coded functions. Therefore, whether configured by hardware or software methods, or by a combination of the two, the processor 202 may represent an entity (e.g., physically embodied in a circuit system) that is capable of performing operations in accordance with the embodiments disclosed herein while being correspondingly configured. Alternatively, as another example, when the processor 202 is embodied as an executor of software instructions, the instructions may specifically configure the processor 202 to perform the algorithms and / or operations described herein when the instructions are executed.

[0081] In some example embodiments, the apparatus 200 may optionally include an input / output circuit system that may communicate with the processor 202 in turn to provide output to a user and / or other entity, and in some example embodiments receive an indication of an input. The input / output circuit system may include a user interface and may include a display, and may include a web user interface, a mobile application, a query initiating computing device, an information kiosk, etc. In some example embodiments, the input / output circuit system may also include a keyboard, a mouse, a joystick, a touch screen, a touch area, a soft key, a microphone, a speaker, or other input / output mechanisms. The processor and / or the user interface circuit system including the processor may be configured to control one or more functions of one or more user interface units by computer program instructions (e.g., software and / or firmware) stored on a memory accessible to the processor (e.g., memory 204, etc.).

[0082] The network interface 206 can be any component, such as a device or circuit system embodied in hardware or a combination of hardware and software, which is configured to receive and / or send data from / to a network, for example, one or more of the RAN components 120 and / or any other device, circuit system, or module in communication with the apparatus 200. In this regard, the network interface 206 may include, for example, a network interface for enabling communication with a wired or wireless communication network. For example, the network interface 206 may include one or more network interface cards, antennas, buses, switches, routers, modems, and supporting hardware and / or software, or any other device suitable for enabling communication via a network. Additionally or alternatively, the network interface 206 may include a circuit system for interacting with an antenna to cause transmission of a signal via the antenna(s) or to process reception of a signal received via the antenna(s).

[0083] It should be understood that the embodiments described herein are not limited to the systems given as examples, such as 5G systems, and those skilled in the art may apply the solutions to other communication systems, including 6G or other communication systems being developed or to be developed in the future. In addition, although some embodiments are described herein in the context of a base station, the method may be performed by other types of network entities according to other example embodiments.

[0084] Figure 3An example architecture for PDU set processing for extended reality (XR) in a 5G device according to an example embodiment of the subject disclosure is shown. In various example embodiments, a PDU set may include one or more PDUs configured to carry a payload of an information unit generated at the application level (e.g., a video frame, a video slice for an XR service, etc.). As shown, the architecture may include a UE 110, a RAN 120, an AF 130, a UPF 140, a PCF 150A, and / or an SMF 150B.

[0085] In one or more example embodiments, UE 102 is in operable communication with RAN 120, such as through a transmission tower, base station, access point, network node, etc. In some example embodiments, RAN 120 may communicate with UPF 140, SMF 150B, or components or entities thereof. In some example embodiments, AF 130, UPF 140, PCF 150A, and / or SMF 150B may be included in a core network that facilitates communication with UE 102, such as for sending data, messages, requests, etc. In some example embodiments, UE 102 may connect to RAN 120, which may then relay communications between UE 102 and one or more portions of the core network (e.g., AF 130, UPF 140, PCF 150A, and / or SMF 150B). In other example embodiments, the core network may also include a network exposure function (NEF) and / or one or more additional network functions (e.g., a network slice selection function (NSSF), a unified data repository (UDR), etc.), which may assist in the communication between the application and the user device. For example, in some example embodiments, the core network may additionally or alternatively include one or more of the following network functions: NEF, NSSF, UDR, authentication server function (AUSF), access and mobility management function (AMF), data network (DN), such as operator services, Internet access or third-party services, unstructured data storage function (UDSF), network repository function (NRF), unified data management (UDM), user plane function (UPF), UE radio capability management function (UCMF), network data analysis function (NWDAF), and / or charging function (CHF). The system environment may also include the following network entities: service communication agent (SCP) and security edge protection agent (SEPP). In some example embodiments, SMF 150B may communicate directly with UPF 140.

[0086] In some example embodiments, UE 102 may include a single mode or dual mode device such that UE 102 may connect to RAN 120. In some example embodiments, RAN 120 may be configured to implement one or more radio access technologies (RATs), such as Bluetooth, Wi-Fi, Global System for Mobile Communications (GSM), Universal Mobile Telecommunications Service (UMTS), LTE, or 5GNR, etc., which may be used to connect UE 102 to a core network. In some example embodiments, RAN 120 may include or be implemented using a chip (such as a silicon chip) in UE 102 that may be paired with or otherwise recognized by a similar chip in the core network, such that RAN 120 may establish a connection or line of communication between UE 102 and the core network by identifying and pairing the chip within UE 102 with the chip in the core network. In some example embodiments, RAN 120 may implement one or more base stations, towers, etc., to communicate between UE 102 and AF 130, UPF 140, PCF 150A, and / or SMF 150B of the core network.

[0087] In some example embodiments, UE 102 may be configured to communicate with RAN 120 in an N1 interface, e.g., according to a non-access stratum (NAS) protocol. In some example embodiments, RAN 120 may be configured to communicate with AF 130, PCF 150A, and / or SMF 150B of the core network in an N2 interface (e.g., in a control plane between a base station of RAN 120 and AF 130, PCF 150A, and / or SMF 150B of the core network). In some example embodiments, RAN 120 may be configured to communicate with UPF 140 in an N3 interface, e.g., in a user plane. In some example embodiments, AF 130, UPF 140, PCF 150A, and / or SMF 150B of the core network may be configured to communicate with other services or network entities within the core network in a variety of different interfaces and / or according to a variety of different protocols. In one or more example embodiments, SMF 150B may be configured to communicate with UPF 140 in an N4 interface, which may act as a bridge between the control plane and the user plane, such as acting as a conduit for a PDU session during which one or more PDUs and / or one or more PDU sets are sent between UE 102, RAN 120, AF 130, UPF 140, PCF 150A, SMF 150B, and / or components / services thereof.

[0088] In one or more example embodiments, the AF 130 may be configured to send one or more processing requests to at least one PCF 150A. In various example embodiments, the processing request may include the initiation of a PDU session, which may be used to provide end-to-end user plane connectivity between a UE and a specific data network (DN) through a user plane function (UPF). The PDU session may support one or more quality of service (QoS) flows. In various example embodiments, a one-to-one mapping is provided between a QoS flow and a quality of service profile. In various example embodiments, a PDU set includes one or more PDUs that transmit a payload of an information unit generated at an application level (e.g., a frame, a video slice, etc. for an XRM service, as used in 3GPP TS23.501). In various example embodiments, the PDU QoS set may also include parameters, which are defined in 3GPP 23.201v 18.1.0 section 5.7. In various example embodiments, the PDU QoS set may include one or more parameters, which may be used to support a PDU set based on QoS processing within a radio access network. The PDU set may include at least one of the following QoS characteristics: PDU set delay budget (PSDB), PDU set error (PSER), and / or PDU set integrated processing information (PSIHI). In one or more example embodiments, the processing request provides one or more values ​​associated with the PDU set QoS parameters and / or protocol description information to the PCF 150A. The protocol description information may include information about the application protocol, header (e.g., real-time protocol, secure real-time protocol, etc.) and / or payload type (e.g., H.264). In various example embodiments, the AF 130 may also send a real-time protocol (RTP) / secure real-time protocol (SRTP) PDU header extension and / or payload type information to the UPF 140. In one or more example embodiments, the information sent to the UPF 140 is sent on a downlink (DL). In various example embodiments, the communication between the AF 130 and at least the UE 110 and / or the UPF 140 may require an RTP header extension.

[0089] Further references Figure 3In various example embodiments, the PCF 150A may authorize a request received from an application function (AF) 130. In the event that the PCF authorizes the request from the AF, the PCF 150A may incorporate the information received from the AF 130 into a policy and charging control (PCC) rule. In one or more example embodiments, the PCF 150A sends the PCC rule to a session management function (SMF) 150B. In the event that the PCF does not authorize the request from the AF, the PDU set QoS parameters and the protocol description information may be statically configured in the 5GS. In various example embodiments, the SMF 150B determines a QoS flow for an extended reality (XR) traffic service data flow. The SMF 150B may send new PDU set QoS parameters to a next generation radio access network (NG RAN) component 120 simultaneously and / or separately, and the protocol description information and / or the PDU set information includes information about marking an indication to a PDU session anchor (PSA) user plane function (UPF) 140. The PSA UPF 140 determines and implements specific rules configured to detect one or more RTP / SRTP headers, detect the payload of the DL PDU, determine the PDU set, and / or extract the PDU set information. In one or more example embodiments, the specific rules are based at least in part on the received protocol description. In other embodiments, the PSA UPF 140 may alternatively be configured to implement one or more specific processes to identify the PDU set, such as when the PSAUPF 140 does not receive specific protocol description information from the SMF 150B (e.g., for proprietary application protocols other than RTP).

[0090] Further references Figure 3In various example embodiments, a PDU Session Anchor (PSA) User Plane Function (UPF) 140 is configured to support detection of PDU sets and / or marking of PDU sets by sending one or more General Packet Radio Service (GPRS) Tunneling Protocol-User Plane (GTP-U) packets (e.g., header extensions) to at least one Next Generation Radio Access Network (NG RAN) component 120. In various example embodiments, the GTP-U header includes information about the PDU set. The information may include at least one of: a PDU set sequence number, an indication of an end PDU of the PDU set, a PDU sequence number within the PDU set, a PDU set size (in bytes), a PDU set importance for identifying the importance of the PDU set with a Quality of Service (QoS) flow, and the like. In various example embodiments, the PDU set importance may be a unique GTP-U parameter provided by the UPF that may distinguish PDU sets based on the type of application / media layer payload / attribute. The RAN component 120 is configured to integrate and / or differentiate processing of one or more PDU sets based at least in part on new QoS parameters applicable to the PDU group of the PDU set received from the session management function (SMF) 150B. The new QoS parameter may be at least one of: a PDU set error rate (PSER), a PDU set delay budget (PSDB), and / or a PDU set integrated processing indicator (PSIHI). In various example embodiments, the PSIHI may be used by the RAN component 120 to indicate whether all PDUs in the PDU set are required for an application to process application layer information.

[0091] It will be appreciated that certain example embodiments described herein occur in the context of telecommunications networks, including but not limited to telecommunications networks that conform to and / or otherwise incorporate aspects of fifth generation (5G) architecture. Figures 1 to 3 While various configurations and / or components of example architectures of communication networks are shown, numerous other systems, system configurations, networks, network entities, and paths / protocols for communications therein are contemplated and considered within the scope of the subject disclosure.

[0092] Although the methods, devices / apparatuses and computer program products / codes described herein are described in the context of a fifth generation core network (5GC) and system, such as Figures 1 to 3 Although shown and described above, the described methods, apparatuses and computer program products can still be applied in a broader context in any suitable telecommunication system, network, standard and / or protocol. It will be understood that the described methods, apparatuses and computer program products can also be applied to future networks and systems that have not yet been developed, which will be apparent to those skilled in the art based on the subject disclosure.

[0093] According to one or more embodiments, one or more of the following figures illustrate example transmissions between UE 110, RAN 120, AF 130, UPF 140, PCF 150A and / or SMF 150B to optimize configuration of extended headers of protocol data units for a communication system.

[0094] Figures 4A to 4B An example downlink (DL) implementation of a signal flow according to an example embodiment is shown, wherein a user plane function (UPF) is configured to remove one or more real-time protocol (RTP) header extensions from one or more protocol data units (PDUs) it receives. Figure 4A At operation 1, the application function (AF) 130 may send a request to the core network 150 for extended reality (XR) PDU set processing. In one or more example embodiments, the core network 150 may include at least NEF, SMF150B and / or PCF 150A. The request may include an XR protocol description and / or a request for removal of a real-time protocol (RTP) header extension. In one or more example embodiments, the XR protocol description includes a header extension containing PDU set information for 5GS, such as, for example, a 3GPP Service and System Aspect 4 (SA4) header extension for an XR PDU set identifier associated with a codec. In various example embodiments, the SA4 header extension for the XR PDU set identifier may be used for the PDU set identifier. In various example embodiments, the SA4 header extension for the XR PDU set identifier may be specifically designed to carry information to the 5GS instead of to the application client / server. Additionally or alternatively, the SA4 header extension for the XR PDU set identifier may explicitly transmit the PDU set information. As shown in operation 2 , the core network 150 determines that the user plane function is able to remove the RTP header extension and sends a response to the AF 130 .

[0095] As shown in operation 3a, the core network 150 is configured to send a rule including an indication for the removal of a header extension (e.g., an RTP header extension) to a user plane function (UPF) 140. In one or more example embodiments, a session management function (SMF) is configured to send the rule. In one or more example embodiments, the rule is a forwarding action rule, a quality enforcement rule, a packet detection rule, or another type of rule. In some cases, prior to the transmission of the rule, a policy control function (PCF) within the core network 150 is configured to send a policy and charging control (PCC) rule to the SMF. In one or more example embodiments, the PCC rule includes a "header extension removal" request. The SMF can determine the quality of service (QoS) flow before sending the rule to the UPF. As shown in operation 3b, the UPF 140 sends a header extension removal response to the core network 150 in response to receiving the forwarding action rule.

[0096] As shown in operation 4, application function (AF) 130 may send one or more PDUs including header extensions (such as SA4 header extensions) to user plane function (UPF) 140. As shown in operation 5, UPF may determine one or more PDU sets and / or one or more PDU set parameters based at least in part on the SA4 header extensions received from AF 130. As shown in operation 6, UPF 140 may be configured to determine and / or remove one or more real-time protocol (RTP) header extensions. UPF 140 may remove RTP header extensions from one or more packets and / or adjust one or more parameters associated with the packets as needed (e.g., adjust packet size, etc.). In various example embodiments, the removal of header extensions (e.g., RTP header extensions) may be configured to reduce unnecessary bits of header packets, reduce air interference usage, reduce transmission network resources, and / or reduce packet fragmentation.

[0097] like Figure 4B As shown in operation 7 of , the user plane function (UPF) 140 is configured to add a new PDU set parameter to a general packet radio service (GPRS) tunneling protocol-user plane (GTP-U) header. As shown in operation 8, the UPF 140 can send the PDU to the next generation radio access network (NG RAN) component 120 for PDU set processing. As shown in operation 9, the RAN component 120 performs PDU set differentiation and integrated packet processing. As shown in operation 10, the RAN component 120 can send the PDU to the UE 110. The sent PDU may not have a header extension (e.g., a real-time protocol header extension).

[0098] Figures 5A to 5BAn example uplink (UL) implementation of a signal flow according to an example embodiment is shown, in which a UE 110 is configured to remove one or more header extensions, such as a real-time protocol (RTP) header extension, from one or more protocol data units (PDUs) received by it. Figure 5A At operation 1, AF 130 may send a request to the core network 150 for extended reality (XR) PDU set processing. In one or more example embodiments, the core network 150 may include at least NEF, SMF 150B and / or PCF 150A. The request may include an XR protocol description and / or a request for removal of a header extension (e.g., a real-time protocol (RTP) header extension). In one or more example embodiments, the XR protocol description includes an SA4 header extension for XR PDU set identification. As shown in operation 2, the PCF of the core network 150 may determine that at least one UE 110 is capable of removing a header extension (e.g., an RTP header extension). The PCF may be further configured to send a response to the AF 130 simultaneously and / or individually when it is determined that at least one UE 110 is capable of removing the (RTP) header extension.

[0099] As shown in operation 3, in various example embodiments, the core network 150 is configured to send a rule including an indication for header extension removal (e.g., RTP header extension removal) to the UE 110. In one or more example embodiments, the session management function (SMF) is configured to send the rule. In one or more example embodiments, the rule is a QoS rule or another type of rule. In some cases, prior to the transmission of the action rule, a policy control function (PCF) within the core network 150 is configured to send a policy and charging control (PCC) rule to the SMF. In one or more example embodiments, the PCF may trigger a PDU session modification procedure to update the UE to remove the header extension. In one or more example embodiments, the PCC rule includes a "header extension removal" request. The SMF determines a quality of service (QoS) flow before sending the rule to at least one UE 110. As shown in operation 4, the application function (AF) 130 may send one or more PDUs including a header extension (such as an SA4 header extension) to at least one UE 110. As shown in operation 5, UE 110 may determine one or more PDU sets and / or one or more PDU set parameters based at least in part on the SA4 header extension received from AF 130. In various example embodiments, the parameters may include at least one of: a PDU set sequence number, an indication of an end PDU of the PDU set, a PDU sequence number within the PDU set, a PDU set size (in bytes), and / or a PDU set importance.

[0100] like Figure 5BAs shown in operation 6 of , UE 110 may be configured to determine and / or remove one or more header extensions (e.g., real-time protocol header extensions). In various example embodiments, the removal of header extensions (e.g., RTP header extensions) may be configured to reduce unnecessary bits of header packets, reduce air interference usage, reduce transmission network resources, and / or reduce packet fragmentation. UE 110 may remove header extensions (e.g., RTP header extensions) from one or more packets and / or adjust one or more parameters associated with the packets as needed (e.g., adjust packet size, etc.). As shown in operation 7, UE 110 is configured to send a PDU without header extensions to a next generation radio access network (NG RAN) component 120 on an uplink (UL) transmission. As shown in operation 8, RAN component 120 is configured to send a PDU without header extensions to at least one user plane function (UPF) 140 and / or at least one application function (AF) 130. In various example embodiments, the AF that exchanges signaling with one or more 5GSs may be an application server that exchanges user plane packets with at least one UE.

[0101] Reference now Figures 6 to 9 , by means of a device (e.g. Figure 2 The example flowchart of the operations performed by the device 200) is correspondingly embodied by an application function, a network exposure function, a user plane function and at least one user device.

[0102] Reference now Figure 6 , a method 600 is shown, which can be performed by an apparatus embodied by an application function (e.g., AF 130), wherein the apparatus 200 includes components, such as a processor 202, a memory 204, a network interface 206, etc., for causing the transmission of a processing request for a PDU set based on (e.g., in response to) determining a protocol description indicating PDU set information related to extended reality data, the processing request comprising at least a request to remove a header extension related to the PDU set information. See box 602. The request may also include a protocol description for an XR media stream indicating the PDU set information. In some example embodiments, the header extension may be a real-time protocol (RTP) header extension. In various example embodiments, the protocol description may include information about the header extension. The information may include at least one of: an application protocol, a header type, and / or a payload type.

[0103] The apparatus 200 also includes components, such as a processor 202, a memory 204, a network interface 206, etc., for causing transmission of at least one PDU in the PDU set including a header extension based on (e.g., in response to) an indication that the header extension is removable by a user plane function of the core network. See block 604. The application function may be configured to send at least one PDU in the PDU set after receiving an indication that the header extension is removable by a UPF (e.g., UPF 140) of the core network from a PCF (e.g., PCF 150A) of the core network. In some example embodiments, the PCF and / or the UPF may be located within the same core network. The transmission of at least one PDU may also include causing transmission of at least one PDU including a header extension to the UPF to facilitate removal of the header extension from the at least one PDU via the UPF. In other embodiments, the transmission of at least one PDU may include causing transmission of at least one PDU including a header extension to the UPF to facilitate providing at least one PDU without the header extension to a UE (e.g., UE 102).

[0104] Reference now Figure 7 , the example flow chart shows that Figure 2 The operations performed by the device 200 shown in the figure are shown in the figure, and the device 200 is embodied as a PCF (e.g., PFC 150A) of the core network. In one or more example embodiments, the core network includes at least a session management function, a policy control function, and / or a network exposure function. Now refer to Figure 7 , a method 700 is shown, which can be performed by an apparatus embodied by a PCF (e.g., PFC 150A), the apparatus including at least a session management function, a policy control function, and / or a network exposure function, wherein the apparatus 200 includes components, such as a processor 202, a memory 204, a network interface 206, etc., for receiving a processing request for an XR media stream indicating PDU set information from an application function of a core network, the processing request including a protocol description and a request for removal of a header extension associated with the PDU set. See block 702. The processing request may be sent from one or more application functions (e.g., AF 130) within the core network. In one or more example embodiments, the processing request may include a protocol description applicable to the PDU set. In various example embodiments, the processing request may also include a request for removal of a header extension associated with the PDU. The header extension may be a real-time protocol (RTP) header extension. In various example embodiments, the received protocol description includes information about the header extension. The protocol description is configured to include information about at least one of the following: an application protocol, a header type, and / or a payload type.

[0105] The device 200 also includes components, such as a processor 202, a memory 204, and a network interface 206, for determining, based on the protocol description, that a user plane function of the core network is capable of removing header extensions for a PDU set. See box 704. The UPF can indicate its ability to remove header extensions (e.g., RTP header extensions) via a response to a policy control function. After determining that the UPF is capable of removing the header extension, the policy control function (PCF) within the core network can also be configured to send a response to an application function based at least in part on the determination made by the UPF. In various example embodiments, the PCF can send a response to a network exposure function (NEF). In one or more example embodiments, the NEF then sends a response to the application function. In other embodiments, the PCF can send a response directly to the application function.

[0106] The apparatus 200 also includes components, such as a processor 202, a memory 204, a network interface 206, etc., for causing a rule indication to be provided to a user plane function for removing a header extension associated with a PDU set. See block 706. The rule indication may be provided to a user plane function (UPF) via a session management function within the core network. In various example embodiments, the header extension may be a real-time protocol (RTP) header extension.

[0107] Reference now Figure 8 , the example flow chart shows that Figure 2 The operations performed by the apparatus 200 shown and embodied as a UPF (e.g., UPF 140). Figure 8 , a method 800 is shown that may be performed by an apparatus as embodied by a UPF (e.g., UPF 140), wherein the apparatus 200 includes components, such as a processor 202, a memory 204, a network interface 206, etc., for receiving an indication from a policy control function (PCF) of a core network to remove a header extension for a PDU set. See block 802. In various example embodiments, the header extension may be a real-time protocol (RTP) header extension for extended reality (XR).

[0108] The apparatus 200 also includes components, such as a processor 202, a memory 204, a network interface, etc., for receiving at least one PDU of the PDU set including a header extension from an application function. See block 804. In various example embodiments, the application function may be configured to send at least one PDU of the PDU set to a user plane function (UPF). In some example embodiments, the at least one PDU may include a SA4 header extension. In one or more example embodiments, the SA4 header extension may be a SA4 real-time protocol (RTP) header extension.

[0109] The apparatus 200 also includes components, such as a processor 202, a memory 204, a network interface, etc., for causing the removal of a header extension from at least one PDU and / or adjusting one or more parameters for at least one PDU in response to receiving at least one PDU. See block 806. The user plane function (UPF) may also be configured to determine at least one PDU set parameter for the PDU set. In one or more example embodiments, the determination of the parameter is based at least in part on the header extension. The UPF may also cause the removal of a header extension (e.g., a real-time protocol (RTP) header extension) based at least in part on at least one determined PDU set parameter. In various example embodiments, the UPF removes the header extension (e.g., RTP header extension) from the packet and adjusts the parameters (e.g., packet size, etc.) as needed. In various example embodiments, the UPF may also be configured to add a general packet radio service (GPRS) tunneling protocol-user plane (GTP-U) header extension. In one or more example embodiments, the GTP-U header extension may include at least one PDU set parameter. The UPF may also be configured to send the GTP-U header extension to at least one radio access network (RAN) component.

[0110] Reference now Fig. 9 , the example flow chart shows that Figure 2 The operations shown in FIG. 1 and embodied in the apparatus 200 of the UE 110 are performed. Now referring to Fig. 9 , a method 900 that may be performed by an apparatus embodied by at least one user device (e.g., UE 110) is shown, wherein the apparatus 200 includes components, such as a processor 202, a memory 204, a network interface 206, etc., for receiving a QoS rule from a system management function of a core network, the QoS rule including an indication for removal of a header extension for a PDU set. See block 902. The QoS rule may include an indication for removal of a header extension for a PDU set (e.g., a real-time protocol (RTP) header extension). In various example embodiments, the QoS rule may also be configured to instruct the user device to remove a header extension for at least one PDU set in an uplink (UL) configuration.

[0111] The apparatus 200 also includes components, such as a processor 202, a memory 204, a network interface, etc., for receiving at least one PDU in the PDU set including a header extension from an application. See box 904. The application can be an application client, an application on a UE, or another type of application. The user device can receive at least one PDU in the PDU set including a header extension from the application. In various example embodiments, the application can be an application function external to the UE. In other embodiments, the application can be a UE application (e.g., an application client). In various example embodiments, the header extension can be an SA4 header extension, which includes information about the removal of the header extension.

[0112] The apparatus 200 also includes components, such as a processor 202, a memory 204, a network interface, etc., for causing removal of a header extension from at least one PDU and / or adjusting one or more parameters for at least one PDU in response to receiving at least one PDU. See block 906. In various example embodiments, the UE may remove a header extension (e.g., a real-time protocol (RTP) header extension) based at least in part on a received PDU that includes a header extension (e.g., an SA4 header extension). The UE may also adjust one or more parameters (e.g., packet size, etc.) based at least in part on a received PDU that includes an SA4 header extension. Removal of a header extension (e.g., an RTP header extension) may be configured to reduce unnecessary bits of a header packet, reduce air interference usage, reduce transmission network resources, and / or reduce packet fragmentation.

[0113] The apparatus 200 also includes components, such as a processor 202, a memory 204, a network interface, etc., for causing transmission of at least one PDU without a header extension to at least one radio access network. See block 908. The transmission of at least one PDU may be configured to be without a real-time protocol (RTP) header extension. In various example embodiments, the UE 110 may send a PDU without a header extension (e.g., an RTP header extension) to one or more radio access networks. In one or more example embodiments, the transmission is performed on an uplink transmission. In one or more example embodiments, causing transmission of at least one PDU includes causing transmission of at least one PDU without a header extension to a user plane function and / or an application function via a radio access network.

[0114] The method, apparatus, and computer program product provide numerous advantages, including, in an example embodiment, improved interaction of a 5G device (e.g., a user device, a user plane function, etc.) with an application to coordinate the removal of a header extension for at least one PDU (e.g., a real-time protocol (RTP) header extension removal). In addition, the method, apparatus, and computer program product of the example embodiments provide a reduction in unnecessary bits of header packets, a reduction in air interference, a reduction in transmission network resources, and / or a reduction in packet fragmentation.

[0115] The following example embodiments relate to further aspects of the subject disclosure.

[0116] Example embodiment 1 is a method comprising: based on determining a protocol description indicating a protocol data unit (PDU) set information related to extended reality data, causing the transmission of a processing request for the PDU set, the processing request including at least a request for removing a header extension related to the PDU set; and based on an indication that the header extension is removable by a user plane function of a core network, causing the transmission of at least one PDU in the PDU set including a header extension.

[0117] In Example Embodiment 2, the subject matter of Example Embodiment 1 may optionally include: the header extension is a Real Time Protocol (RTP) header extension.

[0118] In Example Embodiment 3, the subject matter of Example Embodiment 1 may optionally include: the protocol description includes information about header extension.

[0119] In Example Embodiment 4, the subject matter of Example Embodiment 1 may optionally include: the protocol description includes information about at least one of: an application protocol, a header type, and / or a payload type.

[0120] In Example Embodiment 5, the subject matter of Example Embodiment 1 may optionally include causing transmission of the processing request including causing transmission of the processing request to a policy control function of the core network.

[0121] In Example Embodiment 6, the subject matter of Example Embodiment 1 may optionally include causing transmission of at least one PDU including causing transmission of at least one PDU including a header extension to a user plane function to facilitate removal of the header extension from the at least one PDU via the user plane function.

[0122] In Example Embodiment 7, the subject matter of Example Embodiment 1 may optionally include causing transmission of at least one PDU including causing transmission of at least one PDU including a header extension to a user plane function to facilitate providing at least one PDU without a header extension to a user equipment.

[0123] In Example Embodiment 8, the subject matter of Example Embodiment 1 may optionally include that the processing request further includes a protocol description for the PDU set.

[0124] Example embodiment 9 is a device comprising at least one processor and at least one memory storing instructions, which instructions, when executed by the at least one processor, cause the device to: based on determining a protocol description indicating a protocol data unit (PDU) set information related to extended reality data, cause the transmission of a processing request for the PDU set, the processing request including at least a request for removing a header extension related to the PDU set; and based on an indication that the header extension is removable by a user plane function of a core network, cause the transmission of at least one PDU in the PDU set that includes a header extension.

[0125] In Example Embodiment 10, the subject matter of Example Embodiment 9 may optionally include that the header extension is a Real Time Protocol (RTP) header extension.

[0126] In Example Embodiment 11, the subject matter of Example Embodiment 9 may optionally include: the protocol description including information about header extension.

[0127] In Example Embodiment 12, the subject matter of Example Embodiment 9 may optionally include: the protocol description includes information about at least one of: an application protocol, a header type, and / or a payload type.

[0128] In Example Embodiment 13, the subject matter of Example Embodiment 9 may optionally include causing transmission of the processing request including causing transmission of the processing request to a policy control function of the core network.

[0129] In Example Embodiment 14, the subject matter of Example Embodiment 9 may optionally include causing transmission of at least one PDU including causing transmission of at least one PDU including a header extension to a user plane function to facilitate removal of the header extension from the at least one PDU via the user plane function.

[0130] In Example Embodiment 15, the subject matter of Example Embodiment 9 may optionally include causing transmission of at least one PDU including causing transmission of at least one PDU including a header extension to a user plane function to facilitate providing at least one PDU without the header extension to a user equipment.

[0131] In Example Embodiment 16, the subject matter of Example Embodiment 9 can optionally include that the processing request further includes a protocol description for the PDU set.

[0132] Example embodiment 17 is a non-transitory computer-readable storage medium comprising program instructions stored thereon, the program instructions being configured to perform at least the following: based on determining a protocol description indicating a protocol data unit (PDU) set information related to extended reality data, causing the transmission of a processing request for the PDU set, the processing request comprising at least a request for removing a header extension associated with the PDU set; and based on an indication that the header extension is removable by a user plane function of a core network, causing the transmission of at least one PDU in the PDU set that includes a header extension.

[0133] In Example Embodiment 18, the subject matter of Example Embodiment 17 may optionally include: the header extension is a Real Time Protocol (RTP) header extension.

[0134] In Example Embodiment 19, the subject matter of Example Embodiment 17 may optionally include: the protocol description including information about header extension.

[0135] In example embodiment 20, the subject matter of example embodiment 17 may optionally include: the protocol description includes information about at least one of: an application protocol, a header type, and / or a payload type.

[0136] In Example Embodiment 21, the subject matter of Example Embodiment 17 may optionally include causing transmission of the processing request including causing transmission of the processing request to a policy control function of the core network.

[0137] In Example Embodiment 22, the subject matter of Example Embodiment 17 may optionally include causing transmission of at least one PDU including causing transmission of at least one PDU including a header extension to a user plane function to facilitate removal of the header extension from the at least one PDU via the user plane function.

[0138] In Example Embodiment 23, the subject matter of Example Embodiment 17 may optionally include causing transmission of at least one PDU including causing transmission of at least one PDU including a header extension to a user plane function to facilitate providing at least one PDU without the header extension to a user equipment.

[0139] In Example Embodiment 24, the subject matter of Example Embodiment 17 can optionally include the processing request further comprising a protocol description for the PDU set.

[0140] Example embodiment 25 is a device comprising: a component for causing the transmission of a processing request for a protocol data unit (PDU) set based on determining a protocol description indicating information of a PDU set related to extended reality data, the processing request comprising at least a request for removing a header extension related to the PDU set; and a component for causing the transmission of at least one PDU in the PDU set including a header extension based on the header extension being removable by a user plane function of a core network.

[0141] In Example Embodiment 26, the subject matter of Example Embodiment 25 may optionally include: the header extension is a real-time protocol (RTP) header extension.

[0142] In Example Embodiment 27, the subject matter of Example Embodiment 25 may optionally include: the protocol description including information about header extension.

[0143] In Example Embodiment 28, the subject matter of Example Embodiment 25 may optionally include: the protocol description includes information about at least one of: an application protocol, a header type, and / or a payload type.

[0144] In Example Embodiment 29, the subject matter of Example Embodiment 25 may optionally include causing transmission of the processing request including causing transmission of the processing request to a policy control function of the core network.

[0145] In example embodiment 30, the subject matter of example embodiment 25 may optionally include: the means for causing transmission of at least one PDU includes means for causing transmission of at least one PDU including a header extension to a user plane function to facilitate removal of the header extension from the at least one PDU via the user plane function.

[0146] In example embodiment 31, the subject matter of example embodiment 25 may optionally include: the components for causing transmission of at least one PDU include components for causing transmission of at least one PDU including a header extension to a user plane function to facilitate providing at least one PDU without a header extension to a user equipment.

[0147] In example embodiment 32, the subject matter of example embodiment 25 can optionally include the processing request further comprising a protocol description for the PDU set.

[0148] Example embodiment 33 is a method comprising: receiving a processing request for a protocol data unit (PDU) set from an application function of a core network, the processing request comprising a protocol description and a request for removing header extensions associated with the PDU set; based on the protocol description, determining that a user plane function of the core network is capable of removing header extensions for the PDU set; and causing a rule indication to be provided to the user plane function for removing header extensions associated with the PDU set.

[0149] In Example Embodiment 34, the subject matter of Example Embodiment 33 may optionally include that the header extension is a Real Time Protocol (RTP) header extension.

[0150] In Example Embodiment 35, the subject matter of Example Embodiment 33 may optionally include sending a response to the application function based on determining that the user plane function is capable of removing the header extension associated with the PDU set.

[0151] In Example Embodiment 36, the subject matter of Example Embodiment 33 can optionally include: the protocol description including information about header extensions.

[0152] In Example Embodiment 37, the subject matter of Example Embodiment 33 may optionally include: the protocol description includes information about at least one of: an application protocol, a header type, and / or a payload type.

[0153] Example embodiment 38 is a device comprising: at least one processor and at least one memory storing instructions, which instructions, when executed by the at least one processor, cause the device to at least perform: receiving a processing request for a protocol data unit (PDU) set from an application function of a core network, the processing request including a protocol description and a request for removing a header extension associated with the PDU set; based on the protocol description, determining that a user plane function of the core network is capable of removing the header extension for the PDU set; and causing a rule indication to be provided to the user plane function for removing the header extension associated with the PDU set.

[0154] In Example Embodiment 39, the subject matter of Example Embodiment 38 may optionally include: the header extension is a Real Time Protocol (RTP) header extension.

[0155] In example embodiment 40, the subject matter of example embodiment 38 may optionally include the instructions, when executed by at least one processor, further causing the apparatus to send a response to the application function based on determining that the user plane function is capable of removing header extensions associated with the PDU set.

[0156] In example embodiment 41, the subject matter of example embodiment 38 can optionally include: the protocol description including information about header extensions.

[0157] In example embodiment 42, the subject matter of example embodiment 38 can optionally include: the protocol description includes information about at least one of: an application protocol, a header type, and / or a payload type.

[0158] Example embodiment 43 is a non-transitory computer-readable storage medium comprising program instructions stored thereon, the program instructions being configured to perform at least the following: receiving a processing request for a protocol data unit (PDU) set from an application function of a core network, the processing request comprising a protocol description and a request for removing header extensions associated with the PDU set; based on the protocol description, determining that a user plane function of the core network is capable of removing header extensions for the PDU set; and causing a rule indication to be provided to the user plane function for removing header extensions associated with the PDU set.

[0159] In example embodiment 44, the subject matter of example embodiment 43 may optionally include that the header extension is a real-time protocol (RTP) header extension.

[0160] In Example Embodiment 45, the subject matter of Example Embodiment 43 can optionally include the instructions being further configured to send a response to the application function based on determining that the user plane function is capable of removing the header extension associated with the PDU set.

[0161] In Example Embodiment 46, the subject matter of Example Embodiment 43 can optionally include: the protocol description including information about header extensions.

[0162] In Example Embodiment 47, the subject matter of Example Embodiment 43 may optionally include: the protocol description includes information about at least one of: an application protocol, a header type, and / or a payload type.

[0163] Example embodiment 48 is a device comprising: a component for receiving a processing request for a protocol data unit (PDU) set from an application function of a core network, the processing request including a protocol description and a request for removing header extensions associated with the PDU set; a component for determining, based on the protocol description, that a user plane function of the core network is capable of removing header extensions for the PDU set; and a component for causing a rule indication to be provided to the user plane function for removing header extensions associated with the PDU set.

[0164] In Example Embodiment 49, the subject matter of Example Embodiment 48 can optionally include: the header extension is a Real Time Protocol (RTP) header extension.

[0165] In example embodiment 50, the subject matter of example embodiment 48 may optionally include means for sending a response to the application function based on determining that the user plane function is capable of removing the header extension associated with the PDU set.

[0166] In example embodiment 51, the subject matter of example embodiment 48 can optionally include the protocol description including information about header extensions.

[0167] In example embodiment 52, the subject matter of example embodiment 48 can optionally include that the protocol description includes information about at least one of: an application protocol, a header type, and / or a payload type.

[0168] Example embodiment 53 is a method comprising: receiving an indication from a policy control function of a core network for removing a header extension for a protocol data unit (PDU) set; receiving at least one PDU of the PDU set including a header extension from an application function; and in response to receiving at least one PDU, causing removal of the header extension from at least one PDU; and adjusting one or more parameters for at least one PDU.

[0169] In example embodiment 54, the subject matter of example embodiment 53 may optionally include: the header extension is a real-time protocol (RTP) header extension.

[0170] In Example Embodiment 55, the subject matter of Example Embodiment 53 may optionally include: determining at least one PDU set parameter for the PDU set based on the header extension; and causing removal of the header extension from the PDU based on the at least one PDU set parameter.

[0171] In Example Embodiment 56, the subject matter of Example Embodiment 55 may optionally include adding a GPRS Tunneling Protocol-User Plane header extension including at least one PDU set parameter to a GPRS Tunneling Protocol-User Plane header of the PDU.

[0172] In Example Embodiment 57, the subject matter of Example Embodiment 55 can optionally include sending at least one PDU to at least one radio access network.

[0173] Example embodiment 58 is a device comprising at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the device to at least perform: receive an indication from a policy control function of a core network to remove a header extension for a set of protocol data units (PDUs); receive at least one PDU of the set of PDUs including the header extension from an application function; and in response to receiving the at least one PDU, cause removal of the header extension from the at least one PDU; and adjust one or more parameters for the at least one PDU.

[0174] In Example Embodiment 59, the subject matter of Example Embodiment 58 can optionally include: the header extension is a Real Time Protocol (RTP) header extension.

[0175] In example embodiment 60, the subject matter of example embodiment 58 may optionally include: the instructions, when executed by at least one processor, further cause the apparatus to: determine at least one PDU set parameter for the PDU set based on the header extension; and cause removal of the header extension from the PDU based on the at least one PDU set parameter.

[0176] In example embodiment 61, the subject matter of example embodiment 60 may optionally include: the instructions, when executed by at least one processor, further cause the apparatus to: add a GPRS Tunneling Protocol-User Plane header extension including at least one PDU set parameter to a GPRS Tunneling Protocol-User Plane header of the PDU.

[0177] In Example Embodiment 62, the subject matter of Example Embodiment 60 may optionally include the instructions, when executed by at least one processor, further causing the apparatus to transmit at least one PDU to at least one radio access network.

[0178] In an example embodiment 63 is a non-transitory computer-readable storage medium comprising program instructions stored thereon, the program instructions being configured to perform at least one of the following: receiving an indication from a policy control function of a core network for removing a header extension for a protocol data unit (PDU) set; receiving at least one PDU of the PDU set including a header extension from an application function; in response to receiving at least one PDU, causing removal of the header extension from at least one PDU; and adjusting one or more parameters for at least one PDU.

[0179] In Example Embodiment 64, the subject matter of Example Embodiment 63 may optionally include that the header extension is a Real Time Protocol (RTP) header extension.

[0180] In Example Embodiment 65, the subject matter of Example Embodiment 63 may optionally include: the instructions are further configured to: determine at least one PDU set parameter for the PDU set based on the header extension; and cause removal of the header extension from the PDU based on the at least one PDU set parameter.

[0181] In Example Embodiment 66, the subject matter of Example Embodiment 65 can optionally include: the instructions are further configured to: add a GPRS Tunneling Protocol-User Plane header extension including at least one PDU set parameter to a GPRS Tunneling Protocol-User Plane header of the PDU.

[0182] In Example Embodiment 67, the subject matter of Example Embodiment 65 can optionally include the instructions being further configured to send at least one PDU to at least one radio access network.

[0183] Example embodiment 68 is a device comprising: a component for receiving an indication from a policy control function of a core network to remove a header extension for a set of protocol data units (PDUs); a component for receiving at least one PDU of the PDU set including a header extension from an application function; and a component for causing removal of the header extension from at least one PDU in response to receiving at least one PDU; and a component for adjusting one or more parameters for at least one PDU.

[0184] In Example Embodiment 69, the subject matter of Example Embodiment 68 can optionally include that the header extension is a Real Time Protocol (RTP) header extension.

[0185] In example embodiment 70, the subject matter of example embodiment 68 may optionally include means for determining at least one PDU set parameter for the PDU set based on the header extension; and means for causing removal of the header extension from the PDU based on the at least one PDU set parameter.

[0186] In Example Embodiment 71, the subject matter of Example Embodiment 70 may optionally include means for adding a GPRS Tunneling Protocol-User Plane header extension including at least one PDU set parameter to a GPRS Tunneling Protocol-User Plane header of the PDU.

[0187] In example embodiment 72, the subject matter of example embodiment 70 can optionally include means for transmitting at least one PDU to at least one radio access network.

[0188] Example embodiment 73 is a method comprising: receiving a quality of service (QoS) rule from a system management function of a core network, the quality of service (QoS) rule including an indication for removing a header extension of a protocol data unit (PDU) set; receiving at least one PDU in the PDU set including a header extension from an application; and in response to receiving the at least one PDU, causing removal of the header extension from the at least one PDU; and adjusting one or more parameters for the at least one PDU; and causing transmission of the at least one PDU without the header extension to at least one wireless access network.

[0189] In example embodiment 74, the subject matter of example embodiment 73 can optionally include: the header extension is a real-time protocol (RTP) header extension.

[0190] In Example Embodiment 75, the subject matter of Example Embodiment 73 can optionally include causing transmission of the at least one PDU comprising causing transmission of the at least one PDU without a header extension to a user plane function via the radio access network.

[0191] Example embodiment 76 is a device comprising: at least one processor and at least one memory storing instructions, which instructions, when executed by the at least one processor, cause the device to at least perform: receiving quality of service (QoS) rules from a system management function of a core network, the quality of service (QoS) rules including an indication for removing header extensions for a protocol data unit (PDU) set; receiving at least one PDU in the PDU set including a header extension from an application; and in response to receiving the at least one PDU, causing removal of the header extension from the at least one PDU; and adjusting one or more parameters for the at least one PDU; and causing transmission of at least one PDU without the header extension to at least one wireless access network.

[0192] In Example Embodiment 77, the subject matter of Example Embodiment 76 can optionally include: the header extension is a real-time protocol (RTP) header extension.

[0193] In Example Embodiment 78, the subject matter of Example Embodiment 76 can optionally include causing transmission of the at least one PDU comprising causing transmission of the at least one PDU without a header extension to a user plane function via the radio access network.

[0194] Example embodiment 79 is a non-transitory computer-readable storage medium comprising program instructions stored thereon, the program instructions being configured to perform at least the following: receiving a quality of service (QoS) rule from a system management function of a core network, the quality of service (QoS) rule comprising an indication for removing a header extension for a protocol data unit (PDU) set; receiving at least one PDU in the PDU set including a header extension from an application; and in response to receiving the at least one PDU, causing removal of the header extension from the at least one PDU; and adjusting one or more parameters for the at least one PDU; and causing transmission of at least one PDU without the header extension to at least one wireless access network.

[0195] In example embodiment 80, the subject matter of example embodiment 79 can optionally include that the header extension is a real-time protocol (RTP) header extension.

[0196] In Example Embodiment 81, the subject matter of Example Embodiment 79 can optionally include causing transmission of the at least one PDU comprising causing transmission of the at least one PDU without a header extension to a user plane function via a radio access network.

[0197] Example embodiment 82 is an apparatus comprising: a component for receiving a quality of service (QoS) rule from a system management function of a core network, the quality of service (QoS) rule including an indication for removing a header extension for a set of protocol data units (PDUs); a component for receiving at least one PDU in the PDU set including a header extension from an application; and a component for causing removal of the header extension from at least one PDU in response to receiving the at least one PDU; and a component for adjusting one or more parameters for at least one PDU; and a component for causing transmission of at least one PDU without the header extension to at least one wireless access network.

[0198] In Example Embodiment 83, the subject matter of Example Embodiment 82 may optionally include that the header extension is a Real Time Protocol (RTP) header extension.

[0199] In Example Embodiment 84, the subject matter of Example Embodiment 82 can optionally include causing transmission of the at least one PDU comprising causing transmission of the at least one PDU without a header extension to a user plane function via the radio access network.

[0200] In addition, implementations of the various techniques described herein may be implemented in digital electronic circuit systems, or in computer hardware, firmware, software, or a combination thereof. Implementations may be implemented as computer program products, for example, computer programs tangibly embodied in information carriers, for example, in machine-readable storage devices or in propagated signals, for execution by a data processing device (e.g., a programmable processor, a computer, or multiple computers) or for controlling the operation of a data processing device. Implementations may also be provided on a computer-readable medium or a computer-readable storage medium, which may be a non-transitory medium. Implementations of the various techniques may also include implementations provided via transient signals or media, and / or downloadable programs and / or software implementations via the Internet or (multiple) other networks (wired networks and / or wireless networks).

[0201] A computer program may be in source code form, object code form, or some intermediate form, and may be stored in some carrier, distribution medium, or computer-readable medium, which may be any entity or device capable of carrying the program. For example, such carriers include recording media, computer memory, read-only memory, optical and / or electrical carrier signals, telecommunication signals, and software distribution packages. Depending on the processing power required, a computer program may be executed in a single electronic digital computer or distributed among multiple computers.

[0202] Computer programs (such as the computer programs (multiple) described herein) can be written in any form of programming language, including compiled or interpreted languages, and can be deployed in any form, including as stand-alone programs or as modules, components, subroutines or other units or parts thereof suitable for use in a computing environment. Computer programs can be deployed for execution on one computer or multiple computers at one site, or distributed across multiple sites and interconnected by a communication network.

[0203] The operations of the method may be performed by one or more programmable processors executing a computer program or computer program portion to perform functions by operating on input data and generating output. The operations of the method may also be performed by a dedicated logic circuit system, and the apparatus may be implemented as a dedicated logic circuit system, such as an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit).

[0204] It will be understood that each block of the flowchart(s) and combinations of blocks in the flowchart(s) may be implemented by various components, such as hardware, firmware, processors, circuit systems, and / or other communication devices associated with executing software including one or more computer program instructions. For example, one or more of the programs described herein may be implemented by computer program instructions. In this regard, the computer program instructions embodying the programs described herein may be stored in, for example, a memory 204 of a device 200 associated with a user device 110 or other device employing an embodiment of the subject disclosure, and executed by a processor 202. It will be understood that any such computer program instructions may be loaded onto a computer or other programmable device (e.g., hardware) to produce a machine, such that the resulting computer or other programmable device implements the functions specified in the blocks of the flowchart(s). These computer program instructions may also be stored in a computer-readable memory, which may direct a computer or other programmable device to operate in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture, the execution of which implements the functions specified in the blocks of the flowchart(s). The computer program instructions may also be loaded onto a computer or other programmable apparatus to cause a series of operations to be executed on the computer or other programmable apparatus to produce a computer-implemented process, such that the instructions executed on the computer or other programmable apparatus provide operations for implementing the functions specified in the blocks of the flowchart.

[0205] Therefore, the blocks of the (multiple) flow charts support the combination of components for performing the specified functions and the combination of operations for performing the specified functions for performing the specified functions. It will also be understood that one or more blocks of the (multiple) flow charts and the combination of blocks in the (multiple) flow charts can be implemented by a special-purpose hardware computer system that performs the specified functions or a combination of special-purpose hardware and computer instructions.

[0206] Numerous modifications and other embodiments will occur to those skilled in the art having the benefit of the teachings presented in the foregoing description and the associated drawings. Therefore, it should be understood that the present disclosure is not limited to the specific embodiments disclosed, and modifications and other embodiments are intended to be included within the scope of the appended claims. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.

Claims

1. A communication method, the method comprising: Based on determining a protocol description indicating a set of protocol data unit (PDU) information related to extended reality data, causing transmission of a processing request for the set of PDUs, the processing request comprising at least a request to remove a header extension related to the set of PDUs; as well as Based on an indication that the header extension is removable by a user plane function of a core network, transmission of at least one PDU of the PDU set including the header extension is caused.

2. The method of claim 1, wherein the header extension is a Real Time Protocol (RTP) header extension. The method according to claim 1 , wherein the protocol description includes information about the header extension. 4 . The method of claim 1 , wherein the protocol description comprises information about at least one of: an application protocol, a header type, and / or a payload type.

5. The method of claim 1 , wherein causing the transmission of the processing request comprises: causing transmission of the processing request to a policy control function of the core network.

6. The method of claim 1 , wherein causing transmission of the at least one PDU comprises: causing transmission of the at least one PDU including the header extension to the user plane function to facilitate removal of the header extension from the at least one PDU via the user plane function.

7. The method of claim 1 , wherein causing transmission of the at least one PDU comprises: causing transmission of the at least one PDU including the header extension to the user plane function to facilitate providing the at least one PDU without the header extension to a user equipment.

8. The method of claim 1, wherein the processing request further comprises the protocol description for the PDU set.

9. A communication method, the method comprising: receiving, from an application function of a core network, a processing request for a set of protocol data units (PDUs), the processing request comprising a protocol description and a request to remove a header extension associated with the set of PDUs; Based on the protocol description, determining that a user plane function of the core network is capable of removing the header extension for the PDU set; as well as causing a rule indication to be provided to the user plane function for removing the header extension associated with the set of PDUs.

10. The method of claim 9, wherein the header extension is a Real Time Protocol (RTP) header extension.

11. The method according to claim 9, further comprising: Based on determining that the user plane function is capable of removing the header extension associated with the PDU set, a response is sent to the application function.

12. The method of claim 9, wherein the protocol description includes information about the header extension.

13. The method of claim 9, wherein the protocol description comprises information about at least one of: an application protocol, a header type, and / or a payload type.

14. A communication method, the method comprising: receiving an indication from a policy control function of a core network to remove a header extension for a set of protocol data units (PDUs); receiving, from an application function, at least one PDU of the PDU set including the header extension; as well as In response to receiving the at least one PDU, causing removal of the header extension from the at least one PDU; and One or more parameters for the at least one PDU are adjusted.

15. The method of claim 14, wherein the header extension is a Real Time Protocol (RTP) header extension.

16. The method according to claim 14, further comprising: determining at least one PDU set parameter for the PDU set based on the header extension; as well as The removing of the header extension from the PDU is caused based on the at least one PDU set parameter.

17. The method according to claim 16, further comprising: A GPRS tunneling protocol-user plane header extension including the at least one PDU set parameter is added to the GPRS tunneling protocol-user plane header of the PDU.

18. The method according to claim 16, further comprising: The at least one PDU is sent to at least one radio access network.

19. A communication method, the method comprising: receiving a quality of service (QoS) rule from a system management function of a core network, the QoS rule comprising an indication to remove a header extension for a set of protocol data units (PDUs); receiving, from an application, at least one PDU of the PDU set including a header extension; as well as In response to receiving the at least one PDU, causing removal of the header extension from the at least one PDU; as well as adjusting one or more parameters for the at least one PDU; as well as causing transmission of the at least one PDU without the header extension to at least one radio access network.

20. The method of claim 19, wherein the header extension is a Real Time Protocol (RTP) header extension.

21. The method of claim 19, wherein causing transmission of the at least one PDU comprises: causing transmission of the at least one PDU without the header extension to a user plane function via the radio access network.

22. A communications device comprising means for performing the method of any one of claims 1 to 8, 9 to 13, 14 to 18, or 19 to 21.

23. A computer program comprising instructions which, when executed by an apparatus, cause the apparatus to perform the method according to any one of claims 1 to 8, 9 to 13, 14 to 18, or 19 to 21.

Images