Negotiation and notification of protocol data unit (PDU) set or data burst tagging mechanism

Abstract

Methods, systems, and devices for wireless communication are described. In some systems, one or more network entities or functionalities may participate in a two-step procedure, according to which the one or more network entities or functionalities negotiate a set of available labeling mechanisms for identifying packets belonging to the same set of protocol data units (PDUs) or data bursts, and according to which the one or more network entities or functionalities may participate in the two-step procedure, the one or more network entities or functionalities negotiate a set of available labeling mechanisms for identifying packets belonging to the same set of protocol data units (PDUs) or data bursts. An application function (AF) may receive a notification of one or more selected marking mechanisms to be used for a traffic flow. The AF may negotiate the set of available tagging mechanisms with a network exposure function (NEF), and may receive an indication of the one or more selected tagging mechanisms from a session management function (SMF).

Description

[0001] Cross-references

[0002] This patent application claims the benefit of U.S. Provisional Patent Application No. 63 / 339,171, filed by TONESI et al. on May 6, 2022, entitled “NEGOTIATION AND NOTIFICATION OF PROTOCOL DATA UNIT (PDU) SET OR DATA BURST MARKING MECHANISMS” and U.S. Patent Application No. 18 / 312,551, filed by TONESI et al. on May 4, 2023, entitled “NEGOTIATION AND NOTIFICATION OF PROTOCOL DATA UNIT (PDU) SET OR DATA BURSTMARKING MECHANISMS”, each of which is assigned to the assignee of this application. Background Art

[0003] The following relates to wireless communications, including negotiation and notification of protocol data unit (PDU) aggregation or data burst marking mechanisms.

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, etc. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems (such as long term evolution (LTE) systems, advanced LTE (LTE-A) systems, or LTE-A Pro systems) and fifth generation (5G) systems (which may be referred to as new radio (NR) systems). These systems may employ techniques such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each of which supports wireless communication of communication devices, which may be referred to as user equipment (UE). Summary of the invention

[0005] The described techniques relate to improved methods, systems, devices, and apparatuses that support negotiation and notification of protocol data unit (PDU) set or data burst marking mechanisms. For example, the described techniques provide mutually understood procedures to support synchronization between one or more network entities or functionalities regarding which specific marking mechanism is to be used for a service flow involving one or both of a PDU set or a data burst. In some specific implementations, for example, one or more network entities or functionalities may select, identify, or otherwise determine which specific marking mechanism is to be used for a service flow according to a two-step procedure, which may involve a first step associated with network negotiation between an application function (AF) and a network exposure function (NEF) and a second step associated with notification between a session management function (SMF) and the AF.

[0006] A method of wireless communication performed by a network entity is described. The method may include: outputting to a core network entity a request to send information indicating a set of available marking mechanisms for identifying packets belonging to a set of PDUs or a same data burst; obtaining from the core network entity information indicating the set of available marking mechanisms in response to the request; and outputting to the core network entity an indication of a subset of one or more marking mechanisms from the set of available marking mechanisms, wherein at least one marking mechanism in the subset of one or more marking mechanisms corresponds to a policy control rule update for the core network entity.

[0007] A first network node for wireless communication is described. The first network node may include: a memory; and at least one processor coupled to the memory, the at least one processor configured to: output a request to a core network entity to send information indicating a set of available marking mechanisms for identifying packets belonging to a set of PDUs or a same data burst; obtain information indicating the set of available marking mechanisms from the core network entity in response to the request; and output an indication of a subset of one or more marking mechanisms from the set of available marking mechanisms to the core network entity, wherein at least one marking mechanism in the subset of one or more marking mechanisms corresponds to a policy control rule update for the core network entity.

[0008] An apparatus for wireless communication at a network entity is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: output to a core network entity a request to send information indicating a set of available marking mechanisms for identifying packets belonging to the same PDU set or the same data burst; obtain from the core network entity information indicating the set of available marking mechanisms in response to the request; and output to the core network entity an indication of a subset of one or more marking mechanisms from the set of available marking mechanisms, wherein at least one marking mechanism in the subset of one or more marking mechanisms corresponds to a policy control rule update for the core network entity.

[0009] Another apparatus for wireless communication at a network entity is described. The apparatus may include: means for outputting to a core network entity a request to send information indicating a set of available marking mechanisms for identifying packets belonging to a set of PDUs or a same data burst; means for obtaining, in response to the request, from the core network entity information indicating the set of available marking mechanisms; and means for outputting to the core network entity an indication of a subset of one or more marking mechanisms from the set of available marking mechanisms, wherein at least one marking mechanism in the subset of one or more marking mechanisms corresponds to a policy control rule update for the core network entity.

[0010] A non-transitory computer-readable medium having stored thereon code for wireless communication is described. The code, when executed by a network entity, may cause the network entity to: output to a core network entity a request to send information indicating a set of available marking mechanisms for identifying packets belonging to the same PDU set or the same data burst; obtain from the core network entity information indicating the set of available marking mechanisms in response to the request; and output to the core network entity an indication of a subset of one or more marking mechanisms from the set of available marking mechanisms, wherein at least one marking mechanism in the subset of one or more marking mechanisms corresponds to a policy control rule update for the core network entity.

[0011] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, outputting the request may include operations, features, means, or instructions for outputting the request to a NEF via a subscription request message, wherein the core network entity includes the NEF.

[0012] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the subscription request message includes an event indicating that the request corresponds to one or both of a PDU set flag or a data burst flag.

[0013] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the subscription request message may be an event exposure subscription request message.

[0014] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, obtaining information may include operations, features, means, or instructions for obtaining information from a NEF via an event exposure notification message, wherein the core network entity includes the NEF.

[0015] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the core network entity may include a NEF, and the information indicating the set of available marking mechanisms may be associated with the NEF.

[0016] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, obtaining information may include operations, features, components, or instructions for obtaining capability information associated with a core network entity, wherein the capability information indicates a set of available marking mechanisms, and wherein obtaining the information is associated with exposure of the set of available marking mechanisms to the network entity.

[0017] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, outputting an indication may include operations, features, components, or instructions for outputting an indication to a policy control function (PCF), wherein the core network entity includes the PCF.

[0018] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the core network entity may include a PCF, and the policy control rule update for the core network entity may be associated with the PCF.

[0019] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, each respective marking mechanism in the subset of the one or more marking mechanisms may be compatible with the network entity.

[0020] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, outputting the indication may include operations, features, means, or instructions for outputting the indication to the PCF via the NEF.

[0021] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a set of available marking mechanisms may be associated with a network configuration.

[0022] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a set of available marking mechanisms may be stored in one or more of: a memory accessible by the NEF; a unified data repository; or an operations, management, and maintenance entity, depending on the network configuration.

[0023] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, obtaining information may include operations, features, components, or instructions for obtaining information from one or more of the following based on a network configuration: a memory accessible by the NEF; a unified data repository; or an operations, management, and maintenance entity.

[0024] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the network entity may be an AF, and the core network entity includes one or both of a NEF or a PCF.

[0025] A method of wireless communication performed by a first network entity is described. The method may include: obtaining a request from a second network entity to send information indicating a set of available marking mechanisms for identifying packets belonging to the same PDU set or the same data burst; obtaining information indicating the set of available marking mechanisms according to a network configuration; and outputting the information indicating the set of available marking mechanisms to the second network entity in response to the request.

[0026] A first network node for wireless communication is described. The first network node may include a memory and at least one processor coupled to the memory, the at least one processor configured to: obtain a request from a second network entity to send information indicating a set of available marking mechanisms for identifying packets belonging to the same PDU set or the same data burst; obtain information indicating the set of available marking mechanisms according to a network configuration; and output the information indicating the set of available marking mechanisms to the second network entity in response to the request.

[0027] An apparatus for wireless communication at a first network entity is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: obtain from a second network entity a request to send information indicating a set of available marking mechanisms for identifying packets belonging to the same PDU set or the same data burst; obtain information indicating the set of available marking mechanisms according to a network configuration; and output, to the second network entity in response to the request, information indicating the set of available marking mechanisms.

[0028] Another apparatus for wireless communication at a first network entity is described. The apparatus may include: means for obtaining a request from a second network entity to send information indicating a set of available marking mechanisms for identifying packets belonging to the same PDU set or the same data burst; means for obtaining information indicating the set of available marking mechanisms according to a network configuration; and means for outputting information indicating the set of available marking mechanisms to the second network entity in response to the request.

[0029] A non-transitory computer-readable medium having stored thereon code for wireless communication is described. The code, when executed by a first network entity, may cause the first network entity to: obtain from a second network entity a request to send information indicating a set of available marking mechanisms for identifying packets belonging to the same PDU set or the same data burst; obtain information indicating the set of available marking mechanisms according to a network configuration; and output, to the second network entity in response to the request, information indicating the set of available marking mechanisms.

[0030] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, obtaining the request may include operations, features, means, or instructions for obtaining the request from the AF via a subscription request message, where the second network entity may be the AF.

[0031] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the subscription request message includes an event indicating that the request corresponds to one or both of a PDU set flag or a data burst flag.

[0032] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the subscription request message may be an event exposure subscription request message.

[0033] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, outputting information may include operations, features, components, or instructions for outputting information to the AF via an event exposure notification message, where the second network entity may be the AF.

[0034] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for obtaining information indicating a subset of one or more marking mechanisms from a set of available marking mechanisms from a second network entity and outputting an indication of the subset of one or more marking mechanisms to a PCF, wherein at least one marking mechanism in the subset of one or more marking mechanisms corresponds to a policy control rule update for the PCF.

[0035] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, each respective marking mechanism in a subset of the one or more marking mechanisms may be compatible with the second network entity.

[0036] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a set of available marking mechanisms may be stored in one or more of: a memory accessible by the NEF; a unified data repository; or an operations, management, and maintenance entity, depending on the network configuration.

[0037] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, obtaining information may include operations, features, components, or instructions for obtaining information from one or more of the following based on a network configuration: a memory accessible by the NEF; a unified data repository; or an operations, management, and maintenance entity.

[0038] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the first network entity may be a NEF and the second network entity may be an AF.

[0039] A method of wireless communication performed by a first network entity is described. The method may include: obtaining from a second network entity information indicating at least one marking mechanism from a set of available marking mechanisms, wherein the set of available marking mechanisms enables identification of packets belonging to the same PDU set or the same data burst; and updating a policy control rule associated with one or both of the PDU set marking or the data burst marking according to the at least one marking mechanism.

[0040] A first network node for wireless communication is described. The first network node may include a memory and at least one processor coupled to the memory, the at least one processor configured to: obtain from a second network entity information indicating at least one marking mechanism from a set of available marking mechanisms, wherein the set of available marking mechanisms enables identification of packets belonging to the same PDU set or the same data burst; and update a policy control rule associated with one or both of the PDU set marking or the data burst marking according to the at least one marking mechanism.

[0041] An apparatus for wireless communication at a first network entity is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: obtain information indicating at least one marking mechanism from a set of available marking mechanisms from a second network entity, wherein the set of available marking mechanisms enables identification of packets belonging to the same PDU set or the same data burst; and update a policy control rule associated with one or both of the PDU set marking or the data burst marking according to the at least one marking mechanism.

[0042] Another apparatus for wireless communication at a first network entity is described. The apparatus may include: means for obtaining, from a second network entity, information indicating at least one marking mechanism from a set of available marking mechanisms, wherein the set of available marking mechanisms enables identification of packets belonging to the same PDU set or the same data burst; and means for updating a policy control rule associated with one or both of the PDU set marking or the data burst marking according to the at least one marking mechanism.

[0043] A non-transitory computer-readable medium having stored thereon code for wireless communication is described. The code, when executed by a first network entity, may cause the first network entity to: obtain from a second network entity information indicating at least one marking mechanism from a set of available marking mechanisms, wherein the set of available marking mechanisms enables identification of packets belonging to the same PDU set or the same data burst; and update a policy control rule associated with one or both of a PDU set marking or a data burst marking according to the at least one marking mechanism.

[0044] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, updating policy control rules may include operations, features, components, or instructions for permitting a first network entity to modify marking options for one or both of PDU aggregate marking or data burst marking for dynamic policy control rules used by an SMF.

[0045] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, obtaining the information may include operations, features, means, or instructions for obtaining the information from the AF via the NEF, where the second network entity may be the AF.

[0046] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, each respective marking mechanism of at least one marking mechanism may be compatible with AF.

[0047] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a set of available marking mechanisms may be associated with a network configuration.

[0048] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a set of available marking mechanisms may be stored in one or more of: a memory accessible by the NEF; a unified data repository; or an operations, management, and maintenance entity, depending on the network configuration.

[0049] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for obtaining information from one or more of the following based on the network configuration: a memory accessible by the NEF; a unified data repository; or an operations, management, and maintenance entity.

[0050] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first network entity may be a PCF and the second network entity may be an AF.

[0051] A method of wireless communication performed by a first network entity is described. The method may include: outputting a request to a core network entity to send information indicating a marking mechanism, wherein the marking mechanism enables identification of packets belonging to the same PDU set or the same data burst; obtaining information indicating the marking mechanism from the core network entity according to the request; and outputting an indication of the marking mechanism to a second network entity, wherein the indication of the marking mechanism to the second network entity is associated with establishment of a traffic flow according to the marking mechanism.

[0052] A first network node for wireless communication is described. The first network node may include a memory and at least one processor coupled to the memory, the at least one processor being configured to: output a request to a core network entity to send information indicating a marking mechanism, wherein the marking mechanism enables identification of packets belonging to the same PDU set or the same data burst; obtain information indicating the marking mechanism from the core network entity according to the request; and output an indication of the marking mechanism to a second network entity, wherein the indication of the marking mechanism to the second network entity is associated with establishment of a service flow according to the marking mechanism.

[0053] An apparatus for wireless communication at a first network entity is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: output a request to a core network entity to send information indicating a marking mechanism, wherein the marking mechanism enables identification of packets belonging to the same PDU set or the same data burst; obtain information indicating the marking mechanism from the core network entity in accordance with the request; and output an indication of the marking mechanism to a second network entity, wherein the indication of the marking mechanism to the second network entity is associated with establishment of a service flow according to the marking mechanism.

[0054] Another apparatus for wireless communication at a first network entity is described. The apparatus may include: means for outputting a request to a core network entity to send information indicating a marking mechanism, wherein the marking mechanism enables identification of packets belonging to the same PDU set or the same data burst; means for obtaining information indicating the marking mechanism from the core network entity in accordance with the request; and means for outputting an indication of the marking mechanism to a second network entity, wherein the indication of the marking mechanism to the second network entity is associated with establishment of a traffic flow according to the marking mechanism.

[0055] A non-transitory computer-readable medium having stored thereon code for wireless communication is described. The code, when executed by a first network entity, may cause the first network entity to: output a request to a core network entity for sending information indicating a marking mechanism, wherein the marking mechanism enables identification of packets belonging to the same PDU set or the same data burst; obtain information indicating the marking mechanism from the core network entity in accordance with the request; and output an indication of the marking mechanism to a second network entity, wherein the indication of the marking mechanism to the second network entity is associated with establishment of a service flow according to the marking mechanism.

[0056] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, outputting a request may include operations, features, components, or instructions for outputting a request to an SMF via a subscription request message, wherein the core network entity includes the SMF.

[0057] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the subscription request message includes an event indicating that the request corresponds to one or both of a PDU set flag or a data burst flag.

[0058] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the output request may include operations, features, components, or instructions for outputting the request to the SMF via the NEF and the unified data management function, wherein the core network entity also includes the NEF and the unified data management function.

[0059] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the subscription request message may be an event exposure subscription request message.

[0060] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a marking mechanism may be associated with dynamically retrieving one or more policy control rules from the PCF during PDU session establishment or modification, and the one or more policy control rules may be based on one or more marking mechanisms that are compatible with the first network entity.

[0061] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a marking mechanism may be associated with one or more policy control rules that may be predefined for a core network entity, and the one or more policy control rules may be based on one or more marking mechanisms that may be compatible with the first network entity.

[0062] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, obtaining information may include operations, features, components, or instructions for obtaining information from an SMF via an event exposure notification message, wherein the core network entity includes the SMF.

[0063] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the marking mechanism enables identification of a set of PDUs or a burst of data transmitted by an application server to a user plane function.

[0064] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first network entity may be an AF, the core network entity may be an SMF, and the second network entity may be an application server.

[0065] A method of wireless communication performed by a first network entity is described. The method may include: obtaining a request from a second network entity to send information indicating a marking mechanism, wherein the marking mechanism enables identification of packets belonging to the same PDU set or the same data burst; obtaining information indicating the marking mechanism according to one or more policy control rules; and outputting information indicating the marking mechanism to the second network entity according to the request, wherein the information indicating the marking mechanism is associated with establishment of a traffic flow according to the marking mechanism.

[0066] A first network node for wireless communication is described. The first network node may include a memory and at least one processor coupled to the memory, the at least one processor being configured to: obtain a request for sending information indicating a marking mechanism from a second network entity, wherein the marking mechanism enables identification of packets belonging to the same PDU set or the same data burst; obtain the information indicating the marking mechanism according to one or more policy control rules; and output the information indicating the marking mechanism to the second network entity according to the request, wherein the information indicating the marking mechanism is associated with establishment of a traffic flow according to the marking mechanism.

[0067] An apparatus for wireless communication at a first network entity is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: obtain a request for sending information indicating a marking mechanism from a second network entity, wherein the marking mechanism enables identification of packets belonging to the same PDU set or the same data burst; obtain information indicating the marking mechanism according to one or more policy control rules; and output information indicating the marking mechanism to the second network entity according to the request, wherein the information indicating the marking mechanism is associated with establishment of a service flow according to the marking mechanism.

[0068] Another apparatus for wireless communication at a first network entity is described. The apparatus may include: means for obtaining a request from a second network entity to send information indicating a marking mechanism, wherein the marking mechanism enables identification of packets belonging to the same PDU set or the same data burst; means for obtaining information indicating the marking mechanism in accordance with one or more policy control rules; and means for outputting information indicating the marking mechanism to the second network entity in accordance with the request, wherein the information indicating the marking mechanism is associated with establishment of a traffic flow in accordance with the marking mechanism.

[0069] A non-transitory computer-readable medium having stored thereon code for wireless communication is described. The code, when executed by a first network entity, may cause the first network entity to: obtain a request from a second network entity to send information indicating a marking mechanism, wherein the marking mechanism enables identification of packets belonging to the same PDU set or the same data burst; obtain information indicating the marking mechanism according to one or more policy control rules; and output information indicating the marking mechanism to the second network entity according to the request, wherein the information indicating the marking mechanism is associated with establishment of a service flow according to the marking mechanism.

[0070] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, obtaining the request may include operations, features, means, or instructions for obtaining the request from the AF via a subscription request message, where the second network entity may be the AF.

[0071] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the subscription request message includes an event indicating that the request corresponds to one or both of a PDU set flag or a data burst flag.

[0072] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for monitoring subscription request messages based on an event.

[0073] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, obtaining the request may include operations, features, means, or instructions for obtaining the request from the AF via the NEF and the unified data management function.

[0074] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the subscription request message may be an event exposure subscription request message.

[0075] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for dynamically obtaining one or more policy control rules from the PCF during PDU session establishment or modification, wherein the one or more policy control rules may be based on one or more marking mechanisms that are compatible with the first network entity.

[0076] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the one or more policy control rules may be predefined at the first network entity, and the one or more policy control rules may be based on one or more marking mechanisms that are compatible with the first network entity.

[0077] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for selecting a user plane function based on a marking mechanism and configuring the user plane function based on the marking mechanism, wherein the configuration of the user plane function based on the marking mechanism may be associated with the establishment of a service flow according to the marking mechanism.

[0078] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for obtaining, from a user plane function, information indicating capabilities of the user plane function that may be associated with a marking mechanism, wherein the user plane function may be selected based on the capabilities of the user plane function.

[0079] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for searching a set of marking mechanism options based on one or more marking mechanisms compatible with a second network entity and identifying a user plane function based on the search of the set of marking mechanism options, wherein the user plane function may be identified based on being able to perform at least one of the one or more marking mechanisms compatible with the second network entity.

[0080] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, outputting information may include operations, features, components, or instructions for outputting information to the AF via an event exposure notification message, where the second network entity may be the AF.

[0081] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the marking mechanism enables identification of a set of PDUs or a burst of data transmitted by an application server to a user plane function.

[0082] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the first network entity may be a SMF and the second network entity may be an AF.

[0083] A method of wireless communication performed by a network entity is described. The method may include: obtaining from a core network entity information indicating a set of available marking mechanisms for identifying packets belonging to the same PDU set or the same data burst; and outputting to the core network entity an indication of at least one marking mechanism from the set of available marking mechanisms corresponding to a policy control rule update for the core network entity.

[0084] A first network node for wireless communication is described. The first network node may include a memory and at least one processor coupled to the memory, the at least one processor configured to: obtain from a core network entity information indicating a set of available marking mechanisms for identifying packets belonging to the same PDU set or the same data burst; and output to the core network entity an indication of at least one marking mechanism from the set of available marking mechanisms corresponding to a policy control rule update for the core network entity.

[0085] An apparatus for wireless communication at a network entity is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: obtain from a core network entity information indicating a set of available marking mechanisms for identifying packets belonging to the same PDU set or the same data burst; and output to the core network entity an indication of at least one marking mechanism from the set of available marking mechanisms corresponding to a policy control rule update for the core network entity.

[0086] Another apparatus for wireless communication at a network entity is described. The apparatus may include: means for obtaining, from a core network entity, information indicating a set of available marking mechanisms for identifying packets belonging to the same PDU set or the same data burst; and means for outputting to the core network entity an indication of at least one marking mechanism from the set of available marking mechanisms corresponding to a policy control rule update for the core network entity.

[0087] A non-transitory computer-readable medium having stored thereon code for wireless communication is described. The code, when executed by a network entity, may cause the network entity to: obtain from a core network entity information indicating a set of available marking mechanisms for identifying packets belonging to the same PDU set or the same data burst; and output to the core network entity an indication of at least one marking mechanism from the set of available marking mechanisms corresponding to a policy control rule update for the core network entity.

[0088] A method of wireless communication performed by a first network entity is described. The method may include: outputting to a second network entity information indicating a set of available marking mechanisms for identifying packets belonging to the same PDU set or the same data burst; and obtaining from the second network entity an indication of at least one marking mechanism from the set of available marking mechanisms.

[0089] A first network node for wireless communication is described. The first network node may include a memory and at least one processor coupled to the memory, the at least one processor configured to: output to a second network node information indicating a set of available marking mechanisms for identifying packets belonging to the same PDU set or the same data burst; and obtain from the second network node an indication of at least one marking mechanism from the set of available marking mechanisms.

[0090] An apparatus for wireless communication at a first network entity is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: output to a second network entity information indicating a set of available marking mechanisms for identifying packets belonging to the same PDU set or the same data burst; and obtain from the second network entity an indication of at least one marking mechanism from the set of available marking mechanisms.

[0091] Another apparatus for wireless communication at a first network entity is described. The apparatus may include: means for outputting to a second network entity information indicating a set of available marking mechanisms for identifying packets belonging to the same PDU set or the same data burst; and means for obtaining from the second network entity an indication of at least one marking mechanism from the set of available marking mechanisms.

[0092] A non-transitory computer-readable medium having stored thereon code for wireless communication is described. The code, when executed by a first network entity, may cause the network entity to: output to a second network entity information indicating a set of available marking mechanisms for identifying packets belonging to the same PDU set or the same data burst; and obtain from the second network entity an indication of at least one marking mechanism from the set of available marking mechanisms. BRIEF DESCRIPTION OF THE DRAWINGS

[0093] Figure 1 An example of a wireless communication system supporting negotiation and notification of a protocol data unit (PDU) aggregation or data burst marking mechanism in accordance with one or more aspects of the present disclosure is shown.

[0094] Figure 2 An example of a network architecture supporting negotiation and notification of a PDU aggregation or data burst marking mechanism according to one or more aspects of the present disclosure is shown.

[0095] Figure 3 An example of a network diagram supporting negotiation and notification of a PDU aggregation or data burst marking mechanism in accordance with one or more aspects of the present disclosure is shown.

[0096] Figures 4 to 6An example of a process flow to support negotiation and notification of a PDU aggregation or data burst marking mechanism in accordance with one or more aspects of the present disclosure is shown.

[0097] Figure 7 An example of a header format that supports negotiation and notification of a PDU aggregation or data burst marking mechanism according to one or more aspects of the present disclosure is shown.

[0098] Figure 8 and Fig. 9 A block diagram of a device supporting negotiation and notification of a PDU aggregation or data burst marking mechanism according to one or more aspects of the present disclosure is shown.

[0099] Fig.10 A block diagram of a communications manager supporting negotiation and notification of a PDU aggregation or data burst marking mechanism in accordance with one or more aspects of the present disclosure is shown.

[0100] Fig.11 A diagram of a system including devices supporting negotiation and notification of PDU aggregation or data burst marking mechanisms in accordance with one or more aspects of the present disclosure is shown.

[0101] Figures 12 to 16 A flow chart illustrating a method for supporting negotiation and notification of a PDU aggregation or data burst marking mechanism according to one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0102] In some wireless communication systems, one or more network entities or functionalities may support extended reality and media (XRM) applications, according to which one or more network entities or functionalities may process and prepare one or more data packets such as protocol data units (PDUs) for transmission to user equipment (UE). In some cases, one or more network entities or functionalities may process and prepare one or more data packets on a packet-by-packet basis. In other words, one or more network entities or functionalities may process and prepare each data packet separately. For example, an application server (AS) entity may transmit a single packet to a user plane function (UPF), which may transmit a single packet to a radio access network (RAN), which may send a single packet to a UE, or vice versa. In some other cases, one or more network entities or functionalities may extend the data packet processing and preparation framework to handle a collection or burst of multiple packets together (so that a collection of multiple packets is transmitted together, simultaneously, approximately simultaneously, or in a short period of time). By handling multiple packets together, where the multiple packets may collectively indicate one or more information units, the RAN may gain a more complete insight into the data traffic between the AS and the UE, which may enable the RAN to more efficiently allocate resources for packet transmission between the RAN and the UE.

[0103] In order to support such handling of multiple packets that may be grouped together by one or both of a PDU set or a data burst (e.g., a PDU burst), one or more network entities or functionalities may use a marking mechanism according to which packets may be marked to identify that they belong to a specific PDU set or data burst. In some deployments, various types of marking mechanisms may be used. However, in some systems, one or more network entities or functionalities may lack a signaling or configuration-based mechanism to ensure that one or more network entities or functionalities use or expect the same marking mechanism. As a result, different network entities or functionalities may potentially use or expect different marking mechanisms, which may lead to interoperability issues, for example, between a 5G system (5GS) and an application function (AF) or AS.

[0104] In some embodiments of the present disclosure, one or more network entities or functionalities may support mutually understood procedures to support synchronization between one or more network entities or functionalities regarding which specific marking mechanism is to be used for a service flow involving one or both of a PDU set or a data burst. In some embodiments, for example, one or more network entities or functionalities may select, identify, or otherwise determine which specific marking mechanism is to be used for a service flow according to a two-step procedure. In some aspects, the two-step procedure may include a first step associated with negotiation of a PDU set or data burst marking mechanism between an AF and a core network and a second step associated with notification of the selected PDU set or data burst marking mechanism from a session management function (SMF) to the AF. According to the first step, the AF may subscribe to the core network to obtain a set of marking mechanisms available for the service flow, the AF may indicate a subset of one or more marking mechanisms (e.g., a set of one or more marking mechanisms suitable for the AF or otherwise preferred by the AF) to a policy control function (PCF), and the PCF may update one or more policy control rules based on at least one marking mechanism in the subset of one or more marking mechanisms. According to the second step, the AF may subscribe to the SMF for notifications of the selected marking mechanism, the SMF may retrieve and select a marking mechanism (and select a UPF based on the selected marking mechanism), the SMF may indicate the selected marking mechanism to the AF, and the AF may forward the indication of the selected marking mechanism to the AS. In some aspects, the SMF may indicate multiple selected marking mechanisms. For example, the SMF may indicate to the AF and the AS a first marking mechanism for identifying packets belonging to the same PDU burst and a second marking mechanism for identifying packets belonging to the same data burst.

[0105] Specific implementations of the subject matter described in the present disclosure may be implemented to achieve one or more of the following potential advantages. For example, as a result of implementing the described procedures, the AF and the system such as the 5GS may negotiate and use multiple different options to mark the PDU sets or data bursts transmitted between the AS and the UPF. In addition, the 5GS and the AF or AS may avoid or prevent interoperability issues between the 5GS and the AF or AS by maintaining synchronization between the 5GS and the AF or AS, on which various network entities or functionalities use a marking mechanism to exchange PDU sets or data burst-related metadata between the AS and the UPF, which may increase the likelihood of successfully communicating data packets between network entities or functionalities (and ultimately between the UE and the AS). As a result, the UE and the system may achieve higher data rates, greater spectral efficiency, lower latency, and greater system capacity, among other things.

[0106] First, various aspects of the present disclosure are described in the context of a wireless communication system. Various aspects of the present disclosure are additionally illustrated and described with reference to network diagrams, process flows, and header formats. Various aspects of the present disclosure are further illustrated and described with reference to apparatus diagrams, system diagrams, and flow charts related to the negotiation and notification of PDU sets or data burst marking mechanisms.

[0107] Figure 1 An example of a wireless communication system 100 that supports negotiation and notification of a PDU set or data burst marking mechanism according to one or more aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a long term evolution (LTE) network, an advanced LTE (LTE-A) network, an LTE-A Pro network, a new radio (NR) network, or a network operating according to other systems and radio technologies (including future systems and radio technologies not explicitly mentioned herein).

[0108] The network entities 105 may be dispersed throughout a geographic area to form the wireless communication system 100, and may include devices in different forms or with different capabilities. In various examples, the network entities 105 may be referred to as network elements, mobility elements, radio access network (RAN) nodes, or network equipment, etc. In some examples, the network entities 105 and the UE 115 may communicate wirelessly via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, the network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) within which the UE 115 and the network entity 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area within which the network entity 105 and the UE 115 may support signal communications according to one or more radio access technologies (RATs).

[0109] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile, or both stationary and mobile at different times. The UEs 115 may be devices in different forms or with different capabilities. Figure 1 Some example UEs 115 are illustrated in FIG. 1. The UEs 115 described herein may be capable of communicating with various types of devices such as Figure 1 Communicating with other UEs 115 or network entities 105 as shown.

[0110] As described herein, a node (which may be referred to as a node, a network node, a network entity, or a wireless node) may include, may be, or may be included in (e.g., as a component of) a base station (e.g., any base station described herein), a UE (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, an integrated access and backhaul (IAB) node, a distributed unit (DU), a central unit (CU), a remote / radio unit (RU) (which may also be referred to as a remote radio unit (RRU)), and / or another processing entity configured to perform any of the techniques described herein. For example, the network node may be a UE. As another example, the network node may be a base station or a network entity. As another example, a first network node may be configured to communicate with a second network node or a third network node. In one aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a UE. In another aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a base station. In further aspects of this example, the first network node, the second network node, and the third network node may be different relative to these examples. Similarly, references to UE, base station, device, equipment, computing system, etc. may include disclosure of UE, base station, device, equipment, computing system, etc. as a network node. For example, a disclosure that a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node. Consistent with the present disclosure, once a specific example is expanded according to the present disclosure (e.g., a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node), a broader example of a narrower example may be interpreted in reverse, but in a broad, open-ended manner. In the above example where a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node, the first network node may refer to a first UE configured to receive information, a first base station, a first device, a first device, a first computing system, a first set of one or more components, a first processing entity, etc.; and the second network node may refer to a second UE, a second base station, a second device, a second device, a second computing system, a second set of one or more components, a second processing entity, etc.

[0111] As described herein, different terms may be used in various aspects to describe the communication of information (e.g., any information, signal, etc.). The disclosure of one communication term includes the disclosure of other communication terms. For example, a first network node may be described as being configured to send information to a second network node. In this example and consistent with the present disclosure, the disclosure that the first network node is configured to send information to the second network node includes the disclosure that the first network node is configured to provide, transmit, output, communicate, or send information to the second network node. Similarly, in this example and consistent with the present disclosure, the disclosure that the first network node is configured to send information to the second network node includes the disclosure that the second network node is configured to receive, obtain, or decode information provided, transmitted, output, communicated, or sent by the first network node.

[0112] In some examples, the network entities 105 may communicate with the core network 130, or with each other, or both. For example, the network entities 105 may communicate with the core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, the network entities 105 may communicate with each other directly (e.g., directly between each network entity 105) or indirectly (e.g., via the core network 130) via the backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, the network entities 105 may communicate with each other via midhaul communication links 162 (e.g., according to a midhaul interface protocol) or fronthaul communication links 168 (e.g., according to a fronthaul interface protocol) or any combination thereof. The backhaul communication links 120, midhaul communication links 162, or fronthaul communication links 168 may be or include one or more wired links (e.g., electrical links, optical fiber links), one or more wireless links (e.g., radio links, wireless optical links), etc. or various combinations thereof. UE 115 may communicate with core network 130 via communication link 155 .

[0113] One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., a transceiver base station, a radio base station, an NR base station, an access point, a radio transceiver, a Node B, an evolved Node B (eNB), a next generation Node B, or a Gigabit Node B (any of which may be referred to as a gNB), a 5G NB, a next generation eNB (ng-eNB), a home Node B, a home evolved Node B, or other suitable terms). In some examples, the network entity 105 (e.g., a base station 140) may be implemented in an aggregated (e.g., monolithic, stand-alone) base station architecture, which may be configured to utilize a protocol stack physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as a base station 140).

[0114] In some examples, the network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that may be configured to utilize a protocol stack that is physically or logically distributed between two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entity 105 may include one or more of the following: a central unit (CU) 160, a distributed unit (DU) 165, a RU 170, a RAN intelligent controller (RIC) 175 (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) 180 system, or any combination thereof. The RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), an RRU, or a transmit receive point (TRP). One or more components of the network entity 105 in the decomposed RAN architecture may be co-located, or one or more components of the network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of the decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0115] The functional split between CU 160, DU 165, and RU 170 is flexible and may support different functionalities, depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, and RU 170. For example, a functional split of a protocol stack may be employed between CU 160 and DU 165, such that CU 160 may support one or more layers of a protocol stack and DU 165 may support one or more different layers of a protocol stack. In some examples, CU 160 may host higher protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functionality and signaling (e.g., radio resource control (RRC), service data adaptation protocol (SDAP), packet data convergence protocol (PDCP)). The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160. Additionally or alternatively, a functional split of the protocol stack may be employed between the DUs 165 and RUs 170, such that the DUs 165 may support one or more layers of the protocol stack, and the RUs 170 may support one or more different layers of the protocol stack. The DUs 165 may support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional split between CU 160 and DU 165 or between DU 165 and RU 170 may be within the protocol layer (e.g., some functions of the protocol layer may be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer are performed by different ones of CU 160, DU 165, or RU 170). CU 160 may be further functionally split into CU control plane (CU-CP) and CU user plane (CU-UP) functions. CU 160 may be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and DU 165 may be connected to one or more RUs 170 via fronthaul communication links 168 (e.g., open fronthaul (FH) interface). In some examples, midhaul communication link 162 or fronthaul communication link 168 may be implemented according to an interface (eg, channel) between layers of a protocol stack supported by the respective network entities 105 communicating over those communication links.

[0116] In some wireless communication systems (e.g., wireless communication system 100), infrastructure and spectrum resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DUs 165 or one or more RUs 170 may be controlled in part by one or more CUs 160 associated with a donor network entity 105 (e.g., a donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120). The IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a coupled IAB donor's DU 165. The IAB-MT may include an independent set of antennas for relaying communications with the UE 115, or may share the same antennas of the IAB node 104 (e.g., of the RU 170) for access via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, the IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of the IAB node 104) may be configured to operate according to the techniques described herein.

[0117] In the case where the techniques described herein are applied to the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture may be configured to support negotiation and notification of PDU sets or data burst marking mechanisms as described herein. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., IAB node 104, DU 165, CU 160, RU 170, RIC 175, SMO 180).

[0118] UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable term, where a "device" may also be referred to as a unit, a station, a terminal, or a client, etc. UE 115 may also include or may be referred to as a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, UE 115 may include or may be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, etc., which may be implemented in various objects such as appliances or vehicles, meters, etc.

[0119] The UE 115 described herein may be capable of communicating with various types of devices, such as other UEs 115, which may sometimes act as relays, as well as network entities 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 shown.

[0120] The UE 115 and the network entity 105 may communicate with each other wirelessly via one or more communication links 125 (e.g., access links) via one or more carriers. The term "carrier" may refer to a collection of RF spectrum resources having a physical layer structure defined for supporting the communication link 125. For example, a carrier for the communication link 125 may include a portion of an RF spectrum band (e.g., a bandwidth portion (BWP)) that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling for coordinating carrier operations, user data, or other signaling. The wireless communication system 100 may support communications with the UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, the UE 115 may be configured to have multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation may be used for both frequency division duplex (FDD) and time division duplex (TDD) component carriers. Communication between the network entity 105 and other devices may refer to communication between these devices and any portion (e.g., entity, sub-entity) of the network entity 105. For example, the terms "send," "receive," or "communicate" when referring to the network entity 105 may refer to any portion of the network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) of the RAN communicating with another device (e.g., directly or via one or more other network entities 105).

[0121] The signal waveform transmitted through the carrier may be composed of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system employing MCM techniques, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and the subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both), such that the more resource elements a device receives and the higher the order of the modulation scheme, the higher the data rate of the device may be. Wireless communication resources may refer to a combination of RF spectrum resources, time resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0122] The time interval of the network entity 105 or the UE 115 may be expressed as a multiple of a basic time unit, which may be, for example, a sampling period T s =1 / (Δf max ·N f ) seconds, where Δf max It can represent the maximum supported subcarrier spacing, and N f The maximum supported discrete Fourier transform (DFT) size may be indicated. Time intervals of the communication resources may be organized according to radio frames, each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0123] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, the frame may be divided into subframes (e.g., in the time domain), and each subframe may be further divided into a certain number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a certain number of symbol periods (e.g., depending on the length of the cyclic prefix appended in front of each symbol period). In some wireless communication systems 100, the time slot may be further divided into multiple micro time slots containing one or more symbols. Excluding the cyclic prefix, each symbol period may include one or more (e.g., N f The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.

[0124] A subframe, a time slot, a mini-time slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100 and may be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., the number of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in a burst of a shortened TTI (sTTI)).

[0125] Physical channels may be multiplexed on a carrier according to various techniques. Physical control channels and physical data channels may be multiplexed on a downlink carrier using, for example, one or more of a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique. A control region (e.g., a control resource set (CORESET)) of a physical control channel may be defined by a set of symbol periods and may extend across a system bandwidth of a carrier or a subset of that system bandwidth. One or more control regions (e.g., CORESETs) may be configured for a set of UEs 115. For example, one or more of the UEs 115 may monitor or search a control region for control information according to one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level of a control channel candidate may refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space sets may include a common search space set configured for transmitting control information to multiple UEs 115 , and a UE-specific search space set for transmitting control information to a specific UE 115 .

[0126] In some examples, the network entities 105 (e.g., base stations 140, RUs 170) may be mobile and thus provide communication coverage for mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 provide coverage for various coverage areas 110 using the same or different radio access technologies.

[0127] The wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication or various combinations thereof. For example, the wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable or low-latency or critical functions. Ultra-reliable communication may include private communication or group communication, and may be supported by one or more services (such as push-to-talk, video, or data). Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, and ultra-reliable low-latency may be used interchangeably herein.

[0128] In some examples, a UE 115 may be able to communicate directly with other UEs 115 via a device-to-device (D2D) communication link 135 (e.g., according to a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 in a group that are performing D2D communication may be within a coverage area 110 of a network entity 105 (e.g., a base station 140, a RU 170), and the one or more UEs may support aspects of such D2D communication configured or scheduled by the network entity 105. In some examples, one or more UEs 115 in this group may be outside the coverage area 110 of the network entity 105, or may otherwise be unable or not configured to receive transmissions from the network entity 105. In some examples, a group of UEs 115 communicating via D2D communication may support a one-to-many (1:M) system, in which each UE 115 transmits to each other UE 115 in the group. In some examples, the network entity 105 may facilitate scheduling of resources for D2D communication. In some other examples, D2D communications may be performed between UEs 115 without involving network entity 105 .

[0129] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) for managing access and mobility and at least one user plane entity (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)) for routing packets or interconnecting to an external network. The control plane entity may manage non-access layer (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by a network entity 105 (e.g., a base station 140) associated with the core network 130. User IP packets may be delivered through the user plane entity, which may provide IP address allocation and other functions. The user plane entity may be connected to the IP service 150 of one or more network operators. IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0130] The wireless communication system 100 may operate using one or more frequency bands that may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). The region from 300 MHz to 3 GHz may be referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelengths are in the range of from about one decimeter to one meter long. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves may be sufficient to penetrate structures so that macro cells provide services to UEs 115 located indoors. Transmission of UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) than transmission using smaller frequencies and longer wavelengths of the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0131] The wireless communication system 100 may utilize licensed and unlicensed RF spectrum bands. For example, the wireless communication system 100 may use license assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology in unlicensed bands such as the 5 GHz industrial, scientific, and medical (ISM) band. When operating in an unlicensed RF spectrum band, devices such as the network entity 105 and the UE 115 may employ carrier sensing for conflict detection and avoidance. In some examples, operations in an unlicensed band may be based on a carrier aggregation configuration in conjunction with a component carrier (e.g., LAA) operating in a licensed band. Operations in an unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, and the like.

[0132] The network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of the network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, antennas or antenna arrays associated with the network entity 105 may be located in different geographic locations. The network entity 105 may have an antenna array having a set of multiple rows and columns of antenna ports that the network entity 105 can use to support beamforming for communications with the UE 115. Similarly, the UE 115 may have one or more antenna arrays that may support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals sent via the antenna ports.

[0133] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or direct an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining signals conveyed via antenna elements of an antenna array so that some signals propagating in a particular direction relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals conveyed via antenna elements may include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to signals carried via antenna elements associated with the device. Adjustments associated with each of these antenna elements may be defined by a set of beamforming weights associated with a particular direction (e.g., relative to the antenna array of the transmitting device or the receiving device or relative to some other direction).

[0134] The wireless communication system 100 may be a packet-based network that operates according to a layered protocol stack. In the user plane, the communication at the bearer layer or the PDCP layer may be IP-based. The RLC layer may perform packet segmentation and reassembly to communicate on a logical channel. The MAC layer may perform priority processing and multiplexing of logical channels to transport channels. The MAC layer may also use error detection technology, error correction technology, or both to support retransmission at the MAC layer to improve link efficiency. In the control plane, the RRC protocol layer may provide the establishment, configuration, and maintenance of an RRC connection that supports a radio bearer for user plane data between the UE 115 and the network entity 105 or the core network 130. At the PHY layer, a transport channel may be mapped to a physical channel.

[0135] In some systems, such as the wireless communication system 100, one or more network entities 105 or functionalities may extend the data packet processing and preparation framework to handle a collection or burst of multiple packets together (so that a collection of multiple packets are transmitted together, simultaneously, approximately simultaneously, in a short period of time). According to handling multiple packets together, where the multiple packets may collectively indicate one or more information units, the RAN may obtain a more complete view of the data traffic between the AS and the UE 115, which may enable the RAN to more efficiently allocate resources for packet transmission between the RAN and the UE 115.

[0136] In order to support such handling of multiple packets that may be grouped together by one or both of a PDU set or a data burst (e.g., a PDU burst or a burst of PDU data packets), one or more network entities 105 or functionalities may use a marking mechanism according to which packets may be marked to identify that they belong to a specific PDU set or data burst. In some deployments, various types of marking mechanisms may be used. However, in some systems, one or more network entities 105 or functionalities may lack a signaling or configuration-based mechanism to ensure that one or more network entities or functionalities use or expect the same marking mechanism. As a result, different network entities 105 or functionalities may use or expect different marking mechanisms, which may lead to interoperability issues, such as between a 5GS and an AF or AS.

[0137] In some implementations, one or more network entities 105 or functionalities may support mutually understood procedures to support synchronization between one or more network entities 105 or functionalities regarding which specific marking mechanism is to be used for a service flow involving one or both of a PDU set or a data burst. In some implementations, for example, one or more network entities 105 or functionalities may select, identify, or otherwise determine which specific marking mechanism is to be used for a service flow according to a two-step procedure. In some aspects, the two-step procedure may include a first step associated with negotiation of a PDU set or data burst marking mechanism between the AF and the core network and a second step associated with notification of the selected PDU set or data burst marking mechanism from the SMF to the AF.

[0138] According to the first step, the AF may subscribe to the core network to obtain a set of marking mechanisms that can be used for the service flow, the AF may indicate the set of one or more marking mechanisms (e.g., a set of one or more marking mechanisms suitable for the AF) to the policy control function (PCF), and the PCF may update one or more policy control rules based on the set of one or more marking mechanisms. According to the second step, the AF may subscribe to the selected marking mechanism (e.g., one or more selected marking mechanisms) to the SMF, the SMF may retrieve the selected marking mechanism and select the UPF based on the selected marking mechanism, the SMF may indicate the selected marking mechanism to the AF, and the AF may forward the indication of the selected marking mechanism to the AS. Thus, the AS may exchange a set or burst of PDUs with the UE 115 via the UPF and the RAN according to the selected marking mechanism, wherein each of the AS, the UPF, and the RAN may be expected to use the selected marking mechanism according to the two-step procedure.

[0139] Figure 2 An example of a network architecture 200 (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) supporting negotiation and notification of a PDU set or data burst marking mechanism according to one or more aspects of the present disclosure is illustrated. The network architecture 200 may illustrate an example for implementing one or more aspects of the wireless communication system 100. The network architecture 200 may include one or more CUs 160-a, which may communicate directly with a core network 130-a via a backhaul link 120-a, or indirectly with a core network 130-a through one or more disaggregated network entities 105 (e.g., a near-RT RIC 175-b via an E2 link, or a non-RT RIC 175-a associated with an SMO 180-a (e.g., an SMO framework), or both. The CU 160-a may communicate with one or more DUs 165-a via a corresponding midhaul communication link 162-a (e.g., an F1 interface). The DU 165-a may communicate with one or more RUs 170-a via a corresponding fronthaul communication link 168-a. The RUs 170-a may be associated with respective coverage areas 110-a and may communicate with the UEs 115-a via one or more communication links 125-a. In some implementations, a UE 115-a may be simultaneously served by multiple RUs 170-a.

[0140] Each of the network entities 105 of the network architecture 200 (e.g., CU 160-a, DU 165-a, RU 170-a, non-RT RIC 175-a, near-RT RIC 175-b, SMO 180-a, open cloud (O-Cloud) 205, open eNB (O-eNB) 210) may include one or more interfaces or may be coupled to one or more interfaces configured to receive or send signals (e.g., data, information) via a wired or wireless transmission medium. Each network entity 105 or an associated processor (e.g., a controller) that provides instructions to an interface of the network entity 105 may be configured to communicate with one or more of the other network entities 105 via a transmission medium. For example, these network entities 105 may include a wired interface that is configured to receive signals on a wired transmission medium or to send signals to one or more of the other network entities 105 on a wired transmission medium. Additionally or alternatively, the network entity 105 may include a wireless interface, which may include a receiver, a transmitter, or a transceiver (e.g., an RF transceiver) configured to receive signals on a wireless transmission medium, or to send signals to one or more of the other network entities 105 on a wireless transmission medium, or both.

[0141] In some examples, CU 160-a may host one or more higher layer control functions. Such control functions may include RRC, PDCP, SDAP, etc. Each control function may be implemented with an interface configured to communicate signals with other control functions hosted by CU 160-a. CU 160-a may be configured to handle user plane functionality (e.g., CU-UP), control plane functionality (e.g., CU-CP), or a combination thereof. In some examples, CU 160-a may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 160-a may be implemented to communicate with DU 165-a for network control and signaling.

[0142] DU 165-a may correspond to a logical unit that includes one or more functions (e.g., base station functions, RAN functions) for controlling the operation of one or more RUs 170-a. In some examples, DU 165-a may host one or more of the RLC layer, MAC layer, and one or more aspects of the PHY layer (e.g., high PHY layers, such as modules for FEC encoding and decoding, scrambling, modulation and demodulation, etc.) based at least in part on functional divisions such as those defined by the Third Generation Partnership Project (3GPP). In some examples, DU 165-a may also host one or more low PHY layers. Each layer may be implemented with an interface that is configured to communicate signals with other layers hosted by DU 165-a or with control functions hosted by CU 160-a.

[0143] In some examples, lower layer functionality may be implemented by one or more RUs 170-a. For example, a RU 170-a controlled by a DU 165-a may correspond to a logical node that hosts RF processing functions or low PHY layer functions (e.g., performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.) or both based on functional splitting such as lower layer functional splitting. In this architecture, RU 170-a may be implemented to handle air (OTA) communications with one or more UEs 115-a. In some specific implementations, real-time and non-real-time aspects of control plane and user plane communications with RU 170-a may be controlled by corresponding DU 165-a. In some examples, this configuration may enable DU 165-a and CU 160-a to be implemented in a cloud-based RAN architecture such as a vRAN architecture.

[0144] The SMO 180-a may be configured to support RAN deployment and configuration of non-virtualized and virtualized network entities 105. For non-virtualized network entities 105, the SMO 180-a may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (e.g., an O1 interface). For virtualized network entities 105, the SMO 180-a may be configured to interact with a cloud computing platform (e.g., O-Cloud 205) via a cloud computing platform interface (e.g., an O2 interface) to perform network entity lifecycle management (e.g., to instantiate virtualized network entities 105). Such virtualized network entities 105 may include, but are not limited to, CU 160-a, DU 165-a, RU 170-a, and near-RT RIC 175-b. In some specific implementations, the SMO 180-a may communicate with components configured according to a 4G RAN (e.g., via an O1 interface). Additionally or alternatively, in some implementations, the SMO 180-a may communicate directly with one or more RUs 170-a via an O1 interface. The SMO 180-a may also include a non-RT RIC 175-a configured to support the functionality of the SMO 180-a.

[0145] The non-RT RIC 175-a may be configured to include logic functions that implement non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) or machine learning (ML) workflows (including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 175-b). The non-RT RIC 175-a may be coupled to or communicate with the near-RT RIC 175-b (e.g., via an A1 interface). The near-RT RIC 175-b may be configured to include logic functions that implement near real-time control and optimization of RAN elements and resources via data collection and actions on an interface connecting one or more CUs 160-a, one or more DUs 165-a, or both, and the O-eNB 210 to the near-RT RIC 175-b (e.g., via an E2 interface).

[0146] In some examples, in order to generate an AI / ML model to be deployed in the near-RT RIC 175-b, the non-RT RIC 175-a may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 175-b and may be received from a non-network data source or from a network function at the SMO 180-a or the non-RT RIC 175. In some examples, the non-RT RIC 175-a or the near-RT RIC 175-b may be configured to tune RAN behavior or performance. For example, the non-RT RIC 175-a may monitor long-term trends and patterns of performance and employ an AI model or ML model to perform corrective actions through the SMO 180-a (e.g., via reconfiguration of O1) or via the generation of a RAN management policy (such as an A1 policy).

[0147] According to the specific implementations described herein, one or more network entities 105 or functionalities may support negotiation and notification signaling mechanisms to achieve the same understanding of the marking mechanism to be used for a set or burst of PDUs (e.g., data or data packets). In some specific implementations, one or more network entities 105 or functionalities may support such negotiation and notification based on an architecture-level configuration or signaling design. For example, according to the specific implementations described herein, as a result of synchronizing on a specific or specific marking mechanism to be used to identify packets (e.g., PDUs) as belonging to the same set of PDUs or the same burst of data, the AS-UPF interface may provide greater data rates and experience higher communication efficiency.

[0148] Figure 3 An example of a network diagram 300 that supports negotiation and notification of a PDU set or data burst marking mechanism according to one or more aspects of the present disclosure is illustrated. The network diagram 300 can implement or be implemented to implement aspects of the wireless communication system 100 or the network architecture 200. For example, the network diagram 300 illustrates communications between various network entities 105 or network functionalities and UE 115, which can be as described herein, including references Figure 1 and Figure 2In some implementations, the various network entities 105 or functionalities may support a two-step procedure according to which one or more of the network entities 105 or functionalities may maintain synchronization regarding which marking mechanism in a set of multiple marking mechanisms is to be used for a traffic flow between the AS 310 and the UE 115. The various network entities 105 or functionalities illustrated by the network diagram 300 include AF 305, AS 310, core network 315 (which may be an example of a 5G core network), PCF 320, network exposure function (NEF) 325, SMF 330, access and mobility function (AMF) 335, UPF 340, RAN 345 ​​(which may be an example of a base station 140 or located at the base station), and UE 115.

[0149] In some aspects, the network diagram 300 may support or otherwise implement per PDU set or per data burst integrated packet handling. For example, AS 310 and UPF 340 may exchange (e.g., send or receive) a set of one or more PDUs 355 (e.g., data packets) together or as a group for simultaneous (or approximately simultaneous) processing or handling. In some examples, for example, AS 310 may send a set of one or more PDUs 355 together, simultaneously, approximately simultaneously, or in a short period of time, and the set of one or more PDUs 355 may jointly indicate or convey one or more information units. AS 310 may send a set of one or more PDUs 355 to UPF 340 via an N6 interface. As used herein, a "short period of time" may refer to a period of time less than N milliseconds, where N is a positive number. In some aspects, N may be less than or equal to, for example, 5, 2.5, 1, 0.5, 0.1, 0.05, or 0.01.

[0150] The UPF 340 may generate another set of one or more PDUs 350 (e.g., data packets) together or as a group for simultaneous (or near-simultaneous) processing or handling for exchange with the RAN 345 ​​and the UE 115. In some aspects, the UPF 340 may mark a set of one or more PDUs 355 independently of how the AS 310 marks the set of one or more PDUs 350. For example, a set of one or more PDUs 355 may be associated with a first marking mechanism, and a set of one or more PDUs 350 may be associated with a second marking mechanism, wherein the first marking mechanism may be different from or the same as the second marking mechanism (even if the set of one or more PDUs 355 may be associated with the first marking mechanism, and the set of one or more PDUs 350 includes the same data or information). In other words, the metadata provided by the AS and the metadata provided by the UPF may be independent. For example, the metadata provided by the AS and the metadata provided by the UPF may be consistent or inconsistent. Furthermore, a set of one or more PDUs 355 is described herein as generally referring to one or more PDUs, and thus, a PDU in the set of one or more PDUs 355 may belong to one or both of a PDU set or a data burst.

[0151] In addition, the network diagram 300 (specifically the AS 310 and the UPF 340) may support different options for how to indicate metadata related to the marking (e.g., grouping) of a set of one or more PDUs 355 by the AS 310 and the UPF 340. The different marking options may include no marking mechanism, a marking mechanism based on a real-time transport protocol (RTP) header, a marking mechanism based on a secure real-time transport protocol (SRTP) header, a marking mechanism based on a web real-time communication (WebRTC) or a marking mechanism based on a hypertext transfer protocol (HTTP) dynamic adaptive streaming (DASH), a specific implementation-dependent marking mechanism, etc. In some aspects, both the AS 310 and the UPF 340 may use the marking mechanism when sending or receiving a set of one or more PDUs 355.

[0152] As an example for PDU set marking, for RTP (which may be associated with an unencrypted header and payload), a parameter set may be configured to indicate information associated with a PDU set (e.g., a classification or marking of a PDU set). For example, if the NAL I flag is set to 1, the PDU priority marking (PPM) may be equal to or associated with a relatively high importance. For another example, a NAL priority field value set for an enhancement layer may be mapped to a PPM based on an application preference for motion or quality. If no configuration applies, the PPM may default to being equal to or associated with a relatively low importance. By Figure 7Additional details related to the RTP header format used to mark PDUs are illustrated and described with reference to this figure.

[0153] As another example for PDU set marking, for SRTP associated with an unencrypted extended experimental header and an encrypted payload, a parameter set may be configured to indicate information associated with a PDU set (e.g., a classification or marking of a PDU set). In some aspects, the configured parameters may be based on the RTP extension header. For example, if the I flag is set to 1, the PPM may be equal to or associated with a relatively high importance, and if the D flag is set to 1, the PPM may be equal to or associated with a relatively low importance. In addition, a temporal ID (TID), layer ID (LID), or temporal layer 0 picture index (TL0PICIDX) value may be mapped to a PPM based on an application preference for motion or quality. If no configuration is applicable, the PPM may default to being equal to or associated with a relatively low importance.

[0154] As another example for PDU set marking, for SRTP associated with an unencrypted header and an encrypted payload, a parameter set may be configured to indicate information associated with a PDU set (e.g., a classification or marking of a PDU set). The configured parameters may include one or more of the following: an Internet Protocol version 6 (IPv6) flow label value corresponding to an application preference for importance of the PDU, a Differentiated Services Code Point (DSCP) corresponding to an application preference for importance of the PDU (e.g., if DSCP=d1, then PPM may be equal to or associated with relatively high importance, or a corresponding importance in a transmit Internet Protocol (IP) port and PPM (e.g., if transmit port=p1, then PPM may be equal to or associated with medium importance). If no configuration is applicable, the PPM may default to being equal to or associated with relatively low importance.

[0155] As another example for PDU set marking, the AF 305 and the core network 315 may negotiate not to apply marking. In such an example, the UPF 340 may generate markings (e.g., packets) for a set of one or more PDUs 355 based on a local mechanism such as deep packet inspection or machine learning without using markings from the AS 310. Thus, while the UPF 340 marks packets for the RAN 345, marking between the AF 305 or AS 310 and the UPF 340 may be optional.

[0156] For data burst marking, a set of one or more burst-aware fields may be updated or set to a specific value to indicate that the DPU belongs to or is part of a specific burst. In some aspects, the set of burst-aware fields may include a burst service flow flag and a last PDU of the burst flag. In some other aspects, the set of burst-aware fields may include a burst service flow flag, a burst sequence number, a last PDU of the burst flag or the number of IP packets in the burst, and an IP sequence number in the burst.

[0157] The network diagram 300 may use a marking mechanism to group a set of one or more PDUs 355 according to a PDU set or a data burst. A PDU set may include one or more PDUs carrying a payload of an information unit (e.g., a frame or video slice for an XRM service) generated at the application layer. One or more PDUs in a data burst may be associated with the same importance (e.g., the same importance constraint) at the application layer. Thus, in some aspects, the application layer may use all PDUs in the PDU set to use the corresponding information unit (and if at least one PDU in the PDU set is lost, the corresponding information unit may not be used). In some other aspects, if some PDUs in the PDU set are lost, the application layer may still recover portions of the corresponding information unit. A data burst may be a set of multiple PDUs that may be larger than a single PDU set. Thus, a data burst may include more than one PDU set and, accordingly, convey more than one information unit. In other words, a (data) burst may represent a group of packets generated by an application at approximately the same time, and the packets constituting the burst may not be associated with a notion of "importance", and may not be associated with constraints involving receiving all of the data in the burst for successful processing (which may be specific to a PDU set). In some aspects, (data) burst information may be implicitly conveyed or supported by one or more network entities 105 or functionalities according to signaling or configuration of information associated with the parameters defined in Table 1 shown below.

[0158]

[0159] Table 1: TSC auxiliary information

[0160] In order to prevent interoperability issues between the system (e.g., 5GS) and the AF 305 or AS 310, the AF 305 or AS 310 and the system, metadata related to which protocol or details are used to exchange PDU sets or data bursts between the AS 310 and the UPF 340 can be synchronized. This synchronization between the AF 305 or AS 310 and the system can be associated with a setting policy in the system (e.g., 5GS) for which protocol (e.g., which marking mechanism) is to be used for PDU sets or data burst information between the AS 310 and the system in which the application is supported. Such a policy can be arranged offline (e.g., via a service level agreement (SLA)) or via explicit signaling. Additionally or alternatively, this synchronization between the AF 305 or AS 310 and the system can be associated with a PDU session establishment update that takes into account the selected protocol (e.g., the selected marking mechanism) for the PDU set or data burst information. Additionally or alternatively, such synchronization between the AF 305 or AS 310 and the system may be associated with system exposure or confirmation to the AF 305, or both, that a given protocol (e.g., a given marking mechanism) is available for a business flow (e.g., an XRM business flow).

[0161] According to a specific implementation described herein, one or more network entities 105 or functionalities of the network diagram 300 may employ a two-step procedure according to which the AF 305 and the core network 315 may negotiate a set of available or suitable marking mechanisms for one or both of a PDU set or a data burst, and according to which the SMF 330 may inform the AF 305 of the selected marking mechanism for one or both of a PDU set or a data burst. Figure 4 and Figure 5 Additional details related to the negotiation of a set of available or suitable marking mechanisms between the AF 305 and the core network 315 are illustrated and described with reference to these figures. Figure 6 Additional details of notification of the selected marking mechanism from the SMF 330 to the AF 305 are illustrated and described with reference to the figure. In some aspects, the SMF 330 may indicate multiple selected marking mechanisms. For example, the SMF 330 may indicate to the AF 305 and the AS 310 a first marking mechanism for identifying packets belonging to the same PDU burst and a second marking mechanism for identifying packets belonging to the same data burst. In such aspects, the AS 310 and the UPF 340 may use a single corresponding marking mechanism for PDU aggregate marking and a single corresponding marking mechanism for data burst marking, and the SMF 330 may indicate two corresponding marking mechanisms to the AF 305.

[0162] In some systems, one or more network entities 105 or functionalities may use a packet flow description (PFD) as the basis for communication from the AF 305 to the unified data repository (UDR). For example, the SMF 330 may subscribe to the PFDManagement service from the NEF 325 to retrieve the configuration, and the SMF 330 may use the N4 PFD management procedure to configure one or more PDFs in the UPF 340. Thus, details of the PDU set marking transmitted on the AS-UPF interface may be provided with the PFD to map different PDU set services on different quality of service (QoS) flows. In some specific implementations, the identification of the start or end of each PDU set or burst and the mapping of the PDU set or burst service on the QoS flow may be associated with a separate signaling mechanism or a separate rule or procedure. In addition, in some specific implementations, the use of PDU set markings may be authorized by policy control rules, and the actual marking options to be used may be part of the PFD. In such implementations, the network diagram 300 may still support routing from the AF 305 to the NEF 325 to the UDR, and the AF 305 may use the routing to request one or more PDU aggregation or burst marking options.

[0163] Furthermore, as described herein, the term "output" may generally refer to any method or means for outputting information, including, for example, sending, signaling, messaging, conveying, indicating, etc. Furthermore, outputting may include outputting via wireless signaling, via wired signaling, or via a combination of wired and wireless signaling. Similarly, as described herein, the term "obtaining" may generally refer to any method or means for obtaining information, including, for example, receiving, sensing, extracting, measuring, etc. Furthermore, obtaining may include obtaining via wireless signaling, via wired signaling, or via a combination of wired and wireless signaling.

[0164] Figure 4 An example of a process flow 400 that supports negotiation and notification of a PDU set or data burst marking mechanism in accordance with one or more aspects of the present disclosure is shown. The process flow 400 can implement aspects of the wireless communication system 100, the network architecture 200, and the network diagram 300. For example, the process flow 400 illustrates communications between the AF 305, the NEF 325, and the UDR 405. In some implementations, the AF 305, the NEF 325, and the UDR 405 can communicate to negotiate a set of available or suitable marking mechanisms between the AF 305 and the core network 315 (which can include one or both of the NEF 325 and the UDR 405). In other words, the process flow 400 illustrates an AF 305-NEF 325 interaction.

[0165] In the following description of the process flow 400, operations (such as reporting or providing) may be performed in a different order than shown, or operations performed by the example device may be performed in a different order or at a different time. Some operations may also be excluded from the process flow 400, or other operations may be added to the process flow 400. In addition, although some operations or signaling are shown as occurring at different times for discussion purposes, these operations may actually occur simultaneously.

[0166] At 410, the AF 305 may output to the NEF 325 a request for notification of a set of available marking mechanisms associated with marking one or both of the PDUs in the PDU set (e.g., PDU set marking) or the PDUs in the data burst (e.g., data burst marking). In some aspects, each respective marking mechanism in the set of available marking mechanisms corresponds to a respective way of identifying a set of one or more PDUs that jointly convey one or more information units. In some implementations, the AF 305 may output the request via a subscription request message, such as an event exposure subscription request message. For example, the AF 305 may output the request via an Nnef_EventExposure_Subscribe request message.

[0167] In some specific implementations, the AF 305 may include an event (e.g., an event identifier, an event filter, or an event field) in the subscription request message, and may set the value of the event based on the subscription request message including a request for notification of a set of available marking mechanisms. For example, the event included by the AF 305 in the subscription request message may be associated with one or both of a PDU set marking or a data burst marking. In other words, the AF 305 may set the event so that the event = 'PDU set marking mechanism' or 'burst marking mechanism' or 'PDU set and burst marking mechanism'. Based on outputting the subscription request message to the NEF 325, the AF 305 may effectively subscribe to the core network 315 (e.g., a 5G core network) to obtain a list of options supported by the system (e.g., 5GS).

[0168] At 415, the NEF 325 may output a subscription response message to the AF 305. In some examples, the subscription response message may confirm or acknowledge the subscription of the AF 305 to the NEF 325 or the core network 315. In some aspects, the subscription response message may be an example of an Nnef_EventExposure_Subscribe response message.

[0169] At 420, the NEF 325 can obtain a set of available marking mechanisms based on the network configuration. In some implementations, the NEF 325 can obtain the set of available marking mechanisms from one or more of a memory of the NEF 325 or the core network 315, the UDR 405, or an operations, administration, and maintenance (OAM) entity. For example, the NEF 325 can store or retrieve a set of available marking mechanisms for PDU aggregate marking (e.g., RTP, SRTP, etc.) or a set of available marking mechanisms for burst marking (e.g., different mechanisms or techniques for setting a burst awareness field).

[0170] At 425, the NEF 325 may output an indication of the set of available marking mechanisms according to the request to the AF 305. In other words, the NEF 325 may store or retrieve a set of available marking mechanisms for PDU aggregation marking or for burst marking, and may expose the set of available marking mechanisms to the AF 305. In some implementations, the NEF 325 may output the indication of the set of available marking mechanisms to the AF 305 via a notification message, such as an event exposure notification message. For example, the NEF 325 may output the indication of the set of available marking mechanisms to the AF 305 via an Nnef_EventExposure_Notify message.

[0171] Thus, the AF 305 can obtain information associated with marking mechanism options supported by the system (e.g., 5GS). In some implementations, the AF 305 can use this information to select or identify one or more marking mechanisms suitable for the AF 305 or the traffic flow to be communicated from the AS 310 to the core network 315 and to the UE 115 from the set of available marking mechanisms. Figure 5 Additional details related to the selection of one or more marking mechanisms from a set of available marking mechanisms by the AF 305 and notification of the selected one or more marking mechanisms from the AF 305 to one or more other network entities 105 or functionalities are illustrated and described with reference to this figure.

[0172] In addition, and as also through Figure 5 As illustrated and described in more detail with reference to the figure, the AF 305 may obtain information generally indicating marking mechanism options from the core network 315 without sending a request to the core network 315. For example, the core network 315 may provide (such as send or otherwise expose or indicate) core network capabilities to the AF 305, and the AF 305 may identify, select, ascertain, or otherwise determine which one or more marking mechanisms may be used based on the core network capabilities.

[0173] Figure 5An example of a process flow 500 for supporting negotiation and notification of a PDU set or data burst marking mechanism in accordance with one or more aspects of the present disclosure is shown. The process flow 500 may implement aspects of the wireless communication system 100, the network architecture 200, the network diagram 300, or the process flow 400. For example, the process flow 500 illustrates communications between the AF 305, the NEF 325, and the PCF 320. In some implementations, the AF 305, the NEF 325, and the PCF 320 may communicate notification of one or more preferred marking mechanisms selected by the AF 305 (e.g., suitable for the AF 305) from a set of available marking mechanisms. In other words, the process flow 500 illustrates an AF 305 to PCF 320 interaction for notifying the PCF 320 of one or more marking mechanisms preferred by the AF 305. In some aspects, the process flow 500 may be associated with establishing an AF session with a specific QoS procedure.

[0174] In the following description of the process flow 500, operations (such as reporting or providing) may be performed in a different order than shown, or operations performed by the example device may be performed in a different order or at a different time. Some operations may also be excluded from the process flow 500, or other operations may be added to the process flow 500. In addition, although some operations or signaling are shown as occurring at different times for discussion purposes, these operations may actually occur simultaneously.

[0175] At 505, the NEF 325 (or another entity of the core network 315) may output information indicating the set of available marking mechanisms to the AF 305. In some aspects, such information may include capability information associated with the core network 315. In such aspects, the capability information may explicitly indicate the set of available marking mechanisms (via one or more dedicated fields), or may implicitly indicate the set of available marking mechanisms (such as via a general indication of core network capabilities). In some specific implementations, the NEF 325 (or another entity of the core network 315) may provide information indicating the set of available marking mechanisms without receiving a request for the information from the AF 305. For example, the NEF 325 (or another entity of the core network 315) and the AF 305 may support a capability exposure procedure, via which the AF 305 may receive, obtain, identify, ascertain, or otherwise determine the capabilities of the core network 315 (which may explicitly or implicitly indicate the set of available marking mechanisms).

[0176] At 510, the AF 305 may output an indication of a set of one or more marking mechanisms (such as at least one marking mechanism) from the set of available marking mechanisms to the NEF 325 (e.g., a function, entity, or component of the core network 315). In some aspects, the indication of the set of one or more marking mechanisms may be associated with (e.g., correspond to or imply) a policy control rule update at the PCF 320 (e.g., at the core network 315).

[0177] At 515, the NEF 325 may perform authorization. In some aspects, the authorization may be associated with authorizing the AF 305 or communications between the core network 315 and the AF 305.

[0178] At 520, the NEF 325 may output an indication of the one or more marking mechanisms to the PCF 320 (e.g., another function, entity, or component of the core network 315). Thus, the NEF 325 may relay the indication of the set of one or more marking mechanisms from the AF 305 to the PCF 320. In other words, the AF 305 may output the indication of the set of one or more marking mechanisms to the PCF via the NEF 325, wherein the NEF 325 relays the indication of the set of one or more marking mechanisms to the PCF 320.

[0179] At 525, the PCF 320 may output a create response message to the NEF 325. In some aspects, the create response message may be an example of an Npcf_PolicyAuthorization_Create response message.

[0180] At 530, the NEF 325 may output a create response message to the AF 305. In some aspects, the create response message may be an example of a Nnef_AFsessionWithQoS_Create response message.

[0181] At 535, the NEF 325 may output a subscribe message to the PCF 320. In some aspects, the subscribe message may be an example of a Npcf_PolicyAuthorization_Subscribe message.

[0182] At 540, the PCF 320 may update a policy control rule associated with PDU set marking or data burst marking according to at least one marking mechanism in a set of one or more marking mechanisms indicated from the NEF 325 (and originally indicated from the AF 305). For example, the AF 305 may indicate to the PCF 320 that the AF 305 desires one or more marking mechanism options appropriate for the AF 305 (or appropriate for a service flow to be communicated from the AS 310 to the core network 315 and to the UE 115), and the PCF 320 may update the one or more policy control rules accordingly. For example, the PCF 320 may update one or more policy and / or charging control (PCC) rules, where a PCC rule may refer to or include a set of information that enables detection of service data flows and provides parameters for policy control or charging control or both.

[0183] In some implementations, the PCF 320 may include a PCC rule associated with an information name of a PDU set marking mechanism or a burst marking mechanism or both in a set of PCC rules supported by the PCF 320, and a description associated with the PCC rule may indicate that the PCC rule is for a PDU set marking mechanism or a burst marking mechanism that the AF 305 has indicated to the PCF 320. Thus, the PCF 320 may be permitted to modify the PCC rule for a dynamic PCC rule (e.g., a dynamic PCC rule in the SMF 330). Additional details associated with various PCC rules that the PCF 320 may support are illustrated by Table 2 shown below. Thus, the PCF 320 may populate the PCC rule based on the PDU set or burst marking option preferred by the AF according to the configured behavior.

[0184]

[0185] Table 2: PCC rule information in 5G core network

[0186] At 545, the PCF 320 may output an authorization notification message to the NEF 325. In some aspects, the authorization notification message may be an example of an Npcf_PolicyAuthorization_Notify message.

[0187] At 550, the NEF 325 may output a notification message to the AF 305. In some aspects, the notification message may be an example of a Nnef_AFsessionWithQoS_Notify message.

[0188] Thus, the AF 305 may indicate to the PCF 320 a set of one or more marking mechanisms suitable for the AF 305, and the PCF 320 may update the one or more PCC rules accordingly. In addition to or in lieu of the AF 305 subscribing to obtain options for PDU set or burst marking and indicating the selected option to the PCF 320, one or more PDU set or burst marking settings may be preconfigured or pre-agreed at one or more network entities 105 or functionalities. For example, one or more PCC rules describing options for how to mark PDU sets or bursts between the AS 310 and the UPF 340 may be preconfigured in the PCF 320, and thereby, the AF 305 and the PCF 320 may avoid exchanging signaling associated with the one or more marking mechanisms selected by the AF 305. In such examples, the one or more PCC rules may be preconfigured in the PCF 320 by data network name (DNN), by single network slice selection assistance information (S-NSSAI), by AF ID, based on flow description, etc.

[0189] Based on obtaining PCC rules associated with available, supported or suitable marking mechanisms at PCF 320 (based on the signaling mechanism of process flow 400 and process flow 500 or based on pre-configuration), SMF 330 may select a specific marking mechanism to use when marking PDUs transmitted from AS 310 to UPF 340 (and ultimately to UE 115). In order to achieve synchronization between core network 315 (of which SMF 330 may be a function, entity or component) and AF 305 and AS 310, AF 305 may request notification of which marking mechanism SMF 330 has selected. Figure 6 Additional details related to such notification of a selected marking mechanism (eg, a selected marking option or method) are illustrated and described with reference to this figure.

[0190] Figure 6 An example of a process flow 600 that supports negotiation and notification of a PDU set or data burst marking mechanism in accordance with one or more aspects of the present disclosure is shown. The process flow 600 may implement aspects of the wireless communication system 100, the network architecture 200, the network diagram 300, the process flow 400, or the process flow 500. For example, the process flow 600 illustrates communications between the AF 305, the NEF 325, the unified data management (UDM) function 605, the SMF 330, the UPF 340, and the PCF 320. In some implementations, one or more of these network entities 105 or functionalities may communicate notification of a selected marking mechanism to be used to identify packets belonging to the same PDU set or data burst. In some aspects, the process flow 600 may illustrate communications at or during session establishment or modification.

[0191] In the following description of process flow 600, operations (such as reporting or providing) may be performed in a different order than shown, or operations performed by the example device may be performed in a different order or at a different time. Some operations may also be excluded from process flow 600, or other operations may be added to process flow 600. In addition, although some operations or signaling are shown as occurring at different times for discussion purposes, these operations may actually occur simultaneously.

[0192] At 610 , SMF 330 may select and configure UPF 340 for forwarding packets (eg, PDUs) to SMF 330 .

[0193] At 615, the AF 305 may output to the NEF 325 a request for notification of a selected marking mechanism to be used to identify packets belonging to the same PDU set or data burst (e.g., a request for information indicating the selected marking mechanism). In some implementations, the AF 305 may output the request to the NEF 325 via a subscription request message, such as an event exposure subscription request message. For example, the AF 305 may output the request via an Nnef_EventExposure_Subscribe request message. In some implementations, the AF 305 may include in the subscription request message an event (e.g., an event identifier, event filter, or event field) indicating that the request is for one or both of a PDU set marking or a data burst marking. For example, the AF 305 may set the event to be equal to or otherwise indicate 'PDU set marking' or 'burst marking' or 'PDU set and burst marking'.

[0194] At 620, the NEF 325 may output (e.g., forward or relay) the AF 305's request for notification of the selected marking mechanism to the UDM function 605. In some implementations, the NEF 325 may output, forward or relay the request via a subscription request message, such as an event exposure subscription request message. For example, the NEF 325 may output the request via a Nudm_EventExposure_Subscribe request message. In some implementations, the NEF 325 may include in the subscription request message an event indicating that the request is for one or both of a PDU aggregate marking or a data burst marking. For example, the NEF 325 may set the event equal to or otherwise indicate 'PDU aggregate marking' or 'burst marking' or 'PDU aggregate and burst marking'.

[0195] At 625, the UDM function 605 may output (e.g., send, forward, or relay) the AF 305 request for notification of the selected marking mechanism to the SMF 330. In some implementations, the UDM function 605 may output, forward, or relay the request via a subscription request message, such as an event exposure subscription request message. For example, the UDM function 605 may output the request via an Nsmf_EventExposure_Subscribe request message. In some implementations, the UDM function 605 may include in the subscription request message an event indicating that the request is for one or both of a PDU aggregate marking or a data burst marking. For example, the UDM function 605 may set the event to be equal to or otherwise indicate 'PDU aggregate marking' or 'burst marking' or 'PDU aggregate and burst marking'. Thus, the AF 305 may effectively output a request for notification of the selected marking mechanism to the SMF 330 via the NEF 325 and the UDM function 605.

[0196] In some specific implementations, SMF 330 may monitor the request based on an event indicating that the request is for one or both of PDU aggregate marking or data burst marking. For example, SMF 330 may select a specific monitoring opportunity or a specific monitoring identifier or both so that SMF 330 can obtain a request for notification of the selected marking mechanism. In other words, SMF 330 (and / or UPF 340) may support monitoring events specifically associated with a request for notification of the selected marking mechanism. In some aspects, SMF 330 and UPF 340 may support logic based on monitoring events associated with a request for notification of the selected marking mechanism (e.g., a decision to obtain or not obtain a given message, or to make a specific decision or to activate a specific signaling mechanism).

[0197] At 630, the SMF 330 may output a subscription response message to the UDM function 605. In some aspects, the subscription response message may be an example of an Nsmf_EventExposure_Subscribe response message.

[0198] At 635, the UDM function 605 may output a subscription response message to the NEF 325. In some aspects, the subscription response message may be an example of a Nudm_EventExposure_Subscribe response message.

[0199] At 640, the NEF 325 may output a subscription response message to the AF 305. In some aspects, the subscription response message may be an example of a Nnef_EventExposure_Subscribe response message. Thus, the SMF 330 may effectively confirm or acknowledge the subscription of the AF 305 to notifications of the selected marking mechanism. In other words, the AF 305 may use the Nnef / udm / smf_EventExposure_Subscribe message to request to be notified of the selected option for marking one or both of the PDU set or the data burst.

[0200] At 645, the SMF 330 may retrieve or otherwise obtain a set of one or more policy control rules (e.g., PCC rules). In some implementations, the SMF 330 may dynamically retrieve the policy control rules from the PCF 320 during PDU session establishment or modification. In such implementations, the policy control rules stored or maintained at the PCF 320 may include details or information associated with one or more marking mechanism options preferred by the AF 305 (for either or both of PDU set marking or data burst marking). Thus, in such implementations, the SMF 330 may output a request for the policy control rules to the PCF 320, and the PCF 320 may output an indication of the policy control rules (e.g., information indicating the policy control rules) to the SMF 330. In some aspects, the PCF 320 may provide the policy control rules to the SMF 330 without a request from the SMF 330.

[0201] In some other implementations, the SMF 330 may obtain the policy control rules without interacting with the PCF 320. In such implementations, the SMF 330 may use one or more policy control rules predefined or preconfigured at the SMF 330. Furthermore, in such implementations, the SMF 330 may expect that the one or more policy control rules predefined or preconfigured at the SMF 330 include details or information associated with one or more marking mechanism options (for either or both of PDU aggregate marking or data burst marking) preferred by the AF 305. For example, at least one of the policy control rules predefined or preconfigured at the SMF 330 may include or be based on one or more marking mechanism options preferred by the AF 305.

[0202] In some aspects, one or more policy control rules retrieved or obtained by SMF 330 may indicate a specific marking mechanism to be used to identify packets belonging to the same PDU set or data burst. Thus, SMF 330 may select the indicated marking mechanism (which may be referred to as the selected marking mechanism in this article). In some specific implementations, SMF 330 may further select UPF 340 (from a set of potential multiple UPFs) based on the selected marking mechanism, and may configure UPF 340 based on the selected marking mechanism. For example, the configuration of UPF 340 may be associated with the establishment of a business flow to be communicated according to the selected marking mechanism. Thus, UPF selection logic may be based on a PDU set or burst marking option preferred or supported by one or both of SMF 330 and AF 305.

[0203] As part of the selection and configuration of the UPF 340 by the SMF 330, the SMF 330 may select the UPF 340 based on the marking mechanism indicated in one or more policy control rules and according to information associated with the capabilities of the UPF 340 for the selected marking mechanism. Thus, in some specific implementations, the UPF 340 may perform a network function (NF) registration with a network repository function (NRF) by indicating the capabilities of the UPF 340 for PDU aggregation or burst marking. Therefore, the SMF 330 may perform NF discovery with the NRF by searching or querying the selected marking mechanism to determine or identify which one or more UPFs are capable of using the selected marking mechanism. Based on the SMF 330's search or query of the NRF for the selected marking mechanism, the SMF 330 may identify that the UPF 340 is capable of the selected marking mechanism.

[0204] At 650, SMF 330 and UPF 340 may detect a change in delivery status event.

[0205] At 655, SMF 330 may output an indication of the selected marking mechanism to NEF 325. In some implementations, SMF 330 may output the indication of the selected marking mechanism to NEF 325 via a notification message, such as an event exposure notification message. For example, SMF 330 may output the indication via an Nsmf_EventExposure_Notify message.

[0206] At 660, the NEF 325 may output an indication of the selected marking mechanism to the AF 305. In some implementations, the NEF 325 may output the indication of the selected marking mechanism to the AF 305 via a notification message, such as an event exposure notification message. For example, the NEF 325 may output the indication via an Nnef_EventExposure_Notify message.

[0207] Thus, the SMF 330 can effectively reuse event exposure signaling via the NEF 325 to notify the AF 305 of the selected marking mechanism (e.g., the selected method for marking) by using the Nsmf / nef_EventExposure_Notify message. In some implementations, the SMF 330 can indicate the selected marking mechanism to the AF 305 based on the actual capabilities of the UPF 340. For example, based on selecting the UPF 340 based on the selected marking mechanism, in some implementations, the SMF 330 can update or adjust the selected marking mechanism to meet the actual capabilities of the UPF 340. In such implementations, the SMF 330 can indicate the updated or adjusted selected marking mechanism to the AF 305.

[0208] Figure 7 An example of a header format 700 that supports negotiation and notification of a PDU set or data burst marking mechanism according to one or more aspects of the present disclosure is shown. The header format 700 may implement or be implemented to implement aspects of the wireless communication system 100, the network architecture 200, the network diagram 300, the process flow 400, the process flow 500, or the process flow 600. In some scenarios, the AS 310 and the UPF 340 may use the header format 700 to mark packets as belonging to a PDU set according to the RTP marking mechanism. Figure 7 As illustrated, the example header not including the field 705 may be an example of an RTP header format, and the example header including the field 705 may be an example of an RTP header extension format.

[0209] In the RTP header, the marker "M" bit is set for the last packet of the frame indicated by the RTP timestamp. Therefore, the UPF 340 can identify the beginning and end of a PDU set or frame based on the "M" bit (wherein a PDU set can be equivalently referred to as a PDU frame). According to the options associated with the identification based on the RTP header extension, the "S" bit and the "E" bit in the frame marker RTP header extension respectively represent the beginning and end of a frame (e.g., a video frame). Thus, the UPF 340 can identify the beginning and end of a PDU set or frame based on the "S" and "E" bits. In some aspects, the identification of video frames based on the "S" and "E" bits in the RTP header extension can also be applied to scalable video streams.

[0210] Alternatively, UPF 340 may use the periodicity information as a frame traffic pattern to identify a PDU set or frame. The traffic pattern may also be detected by UPF 340. For example, the downlink media traffic may be 60 PDU sets per second (e.g., 60 frames per second (FPS)) and UPF 340 may determine that it receives one PDU set (e.g., a complete PDU set) every 16.67 milliseconds.

[0211] Figure 8 A block diagram 800 of a device 805 supporting negotiation and notification of a PDU set or data burst marking mechanism according to one or more aspects of the present disclosure is shown. The device 805 may be an example of aspects of a network entity 105 as described herein. The device 805 may include a receiver 810, a transmitter 815, and a communication manager 820. The device 805 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0212] The receiver 810 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be passed to other components of the device 805. In some examples, the receiver 810 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 810 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0213] The transmitter 815 may provide a means for outputting (e.g., sending, providing, conveying, transmitting) information generated by other components of the device 805. For example, the transmitter 815 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 815 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 815 may support outputting information by sending signals via one or more wired (e.g., electrical, optical fiber) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 815 and the receiver 810 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0214] The communication manager 820, the receiver 810, the transmitter 815, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the negotiation and notification of PDU sets or data burst marking mechanisms as described herein. For example, the communication manager 820, the receiver 810, the transmitter 815, or various combinations thereof or components thereof may support methods for performing one or more of the functions described herein.

[0215] In some examples, the communication manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microprocessor, discrete gate or transistor logic, discrete hardware components, or any combination thereof that is configured as or otherwise supports means for performing the functions described herein. In some examples, a processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0216] Additionally or alternatively, in some examples, the communication manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be performed by a general purpose processor (e.g., configured as or otherwise supporting means for performing the functionality described in the present disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.

[0217] In some examples, the communication manager 820 can be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with the receiver 810, the transmitter 815, or both. For example, the communication manager 820 can receive information from the receiver 810, transmit information to the transmitter 815, or be integrated with the receiver 810, the transmitter 815, or both to obtain information, output information, or perform various other operations as described herein.

[0218] According to examples as disclosed herein, the communication manager 820 may support wireless communications at a network entity. For example, the communication manager 820 may be configured to or otherwise support a component for outputting a request to send information indicating a set of available marking mechanisms for identifying packets belonging to the same PDU set or the same data burst to a core network entity. The communication manager 820 may be configured to or otherwise support a component for obtaining information indicating a set of available marking mechanisms from the core network entity in response to the request. The communication manager 820 may be configured to or otherwise support a component for outputting an indication of a subset of one or more marking mechanisms from the set of available marking mechanisms to the core network entity, wherein at least one marking mechanism in the subset of one or more marking mechanisms corresponds to a policy control rule update for the core network entity.

[0219] Additionally or alternatively, according to examples as disclosed herein, the communication manager 820 may support wireless communication at a network entity. For example, the communication manager 820 may be configured to or otherwise support means for: obtaining from a core network entity information indicating a set of available marking mechanisms for identifying packets belonging to the same PDU set or the same data burst; and outputting to the core network entity an indication of at least one marking mechanism from the set of available marking mechanisms corresponding to a policy control rule update for the core network entity.

[0220] Additionally or alternatively, according to examples as disclosed herein, the communication manager 820 may support wireless communications at the first network entity. For example, the communication manager 820 may be configured as or otherwise support a means for obtaining, from the second network entity, a request to send information indicating a set of available marking mechanisms for identifying packets belonging to the same PDU set or the same data burst. The communication manager 820 may be configured as or otherwise support a means for obtaining information indicating a set of available marking mechanisms according to a network configuration. The communication manager 820 may be configured as or otherwise support a means for outputting, in response to the request, information indicating a set of available marking mechanisms to the second network entity.

[0221] Additionally or alternatively, according to examples as disclosed herein, the communication manager 820 may support wireless communication at the first network entity. For example, the communication manager 820 may be configured to or otherwise support means for: outputting information indicating a set of available marking mechanisms for identifying packets belonging to the same PDU set or the same data burst to the second network entity; and obtaining an indication of at least one marking mechanism from the set of available marking mechanisms from the second network entity.

[0222] Additionally or alternatively, according to examples as disclosed herein, the communication manager 820 may support wireless communications at the first network entity. For example, the communication manager 820 may be configured as or otherwise support means for obtaining, from the second network entity, information indicating a subset of one or more marking mechanisms from a set of available marking mechanisms, wherein the set of available marking mechanisms enables identification of packets belonging to the same PDU set or the same data burst. The communication manager 820 may be configured as or otherwise support means for updating a policy control rule associated with one or both of the PDU set marking or the data burst marking according to at least one marking mechanism from the subset of one or more marking mechanisms.

[0223] Additionally or alternatively, according to examples as disclosed herein, the communication manager 820 may support wireless communication at the first network entity. For example, the communication manager 820 may be configured to or otherwise support means for: obtaining, from the second network entity, information indicating at least one marking mechanism from a set of available marking mechanisms, wherein the set of available marking mechanisms enables identification of packets belonging to the same PDU set or the same data burst; and updating a policy control rule associated with one or both of the PDU set marking or the data burst marking according to the at least one marking mechanism.

[0224] Additionally or alternatively, according to examples as disclosed herein, the communication manager 820 may support wireless communications at the first network entity. For example, the communication manager 820 may be configured to or otherwise support a component for outputting a request to send information indicating a marking mechanism to a core network entity, wherein the marking mechanism enables identification of packets belonging to the same PDU set or the same data burst. The communication manager 820 may be configured to or otherwise support a component for obtaining information indicating a marking mechanism from the core network entity in accordance with the request. The communication manager 820 may be configured to or otherwise support a component for outputting an indication of a marking mechanism to a second network entity, wherein the indication of the marking mechanism to the second network entity is associated with the establishment of a service flow according to the marking mechanism.

[0225] Additionally or alternatively, according to examples as disclosed herein, the communication manager 820 may support wireless communications at the first network entity. For example, the communication manager 820 may be configured as or otherwise support a component for obtaining a request to send information indicating a marking mechanism from a second network entity, wherein the marking mechanism enables identification of packets belonging to the same PDU set or the same data burst. The communication manager 820 may be configured as or otherwise support a component for obtaining information indicating a marking mechanism according to one or more policy control rules. The communication manager 820 may be configured as or otherwise support a component for outputting information indicating a marking mechanism to the second network entity according to the request, wherein the information indicating the marking mechanism is associated with the establishment of a service flow according to the marking mechanism.

[0226] By including or configuring a communications manager 820 according to examples as described herein, a device 805 (e.g., a processor controlling or otherwise coupled to a receiver 810, a transmitter 815, a communications manager 820, or a combination thereof) may support techniques for reducing processing, reducing power consumption, and more efficiently utilizing communications resources.

[0227] Fig. 9A block diagram 900 of a device 905 supporting negotiation and notification of a PDU set or data burst marking mechanism according to one or more aspects of the present disclosure is shown. The device 905 may be an example of aspects of the device 805 or network entity 105 as described herein. The device 905 may include a receiver 910, a transmitter 915, and a communication manager 920. The device 905 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0228] The receiver 910 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be passed to other components of the device 905. In some examples, the receiver 910 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 910 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0229] The transmitter 915 may provide a means for outputting (e.g., sending, providing, conveying, transmitting) information generated by other components of the device 905. For example, the transmitter 915 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 915 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 915 may support outputting information by sending signals via one or more wired (e.g., electrical, optical fiber) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 915 and the receiver 910 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0230] The device 905 or its various components may be examples of components for performing various aspects of the negotiation and notification of the PDU set or data burst marking mechanism as described herein. For example, the communication manager 920 may include a subscription request component 925, a notification component 930, a policy control rule update component 935, a network configuration component 940, a marking mechanism component 945, a service flow marking component 950, a policy control rule component 955, or any combination thereof. The communication manager 920 may be an example of various aspects of the communication manager 820 as described herein. In some examples, the communication manager 920 or its various components may be configured to use or otherwise cooperate with the receiver 910, the transmitter 915, or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, the communication manager 920 may receive information from the receiver 910, transmit information to the transmitter 915, or be integrated with the receiver 910, the transmitter 915, or both to obtain information, output information, or perform various other operations as described herein.

[0231] According to an example as disclosed herein, the communication manager 920 may support wireless communications at a network entity. The subscription request component 925 may be configured as or otherwise support a component for outputting a request to send information indicating a set of available marking mechanisms for identifying packets belonging to the same PDU set or the same data burst to a core network entity. The notification component 930 may be configured as or otherwise support a component for obtaining information indicating a set of available marking mechanisms from the core network entity in response to the request. The policy control rule update component 935 may be configured as or otherwise support a component for outputting an indication of a subset of one or more marking mechanisms from the set of available marking mechanisms to the core network entity, wherein at least one marking mechanism in the subset of one or more marking mechanisms corresponds to a policy control rule update for the core network entity.

[0232] Additionally or alternatively, according to examples as disclosed herein, the communication manager 920 may support wireless communications at a network entity. The notification component 930 may be configured as or otherwise support means for obtaining, from a core network entity, information indicating a set of available marking mechanisms for identifying packets belonging to the same PDU set or the same data burst. The policy control rule update component 935 may be configured as or otherwise support means for outputting to the core network entity an indication of at least one marking mechanism from the set of available marking mechanisms corresponding to a policy control rule update for the core network entity.

[0233] Additionally or alternatively, according to examples as disclosed herein, the communication manager 920 may support wireless communications at the first network entity. The subscription request component 925 may be configured as or otherwise support a means for obtaining, from the second network entity, a request to send information indicating a set of available marking mechanisms for identifying packets belonging to the same PDU set or the same data burst. The network configuration component 940 may be configured as or otherwise support a means for obtaining information indicating a set of available marking mechanisms according to a network configuration. The notification component 930 may be configured as or otherwise support a means for outputting, in response to the request, information indicating a set of available marking mechanisms to the second network entity.

[0234] Additionally or alternatively, according to examples as disclosed herein, the communication manager 920 can support wireless communication at the first network entity. The notification component 930 can be configured as or otherwise support means for outputting information indicating a set of available marking mechanisms for identifying packets belonging to the same PDU set or the same data burst to the second network entity. The policy control rule update component 935 can be configured as or otherwise support means for obtaining, from the second network entity, an indication of at least one marking mechanism from the set of available marking mechanisms.

[0235] Additionally or alternatively, according to examples as disclosed herein, the communication manager 920 may support wireless communications at the first network entity. The marking mechanism component 945 may be configured as or otherwise support means for obtaining, from the second network entity, information indicating a subset of one or more marking mechanisms from a set of available marking mechanisms, wherein the set of available marking mechanisms enables identification of packets belonging to the same PDU set or the same data burst. The policy control rule updating component 935 may be configured as or otherwise support means for updating a policy control rule associated with one or both of a PDU set marking or a data burst marking according to at least one marking mechanism from the subset of one or more marking mechanisms.

[0236] Additionally or alternatively, according to examples as disclosed herein, the communication manager 920 can support wireless communications at the first network entity. The marking mechanism component 945 can be configured to or otherwise support means for obtaining, from the second network entity, information indicating at least one marking mechanism from a set of available marking mechanisms, wherein the set of available marking mechanisms enables identification of packets belonging to the same PDU set or the same data burst. The policy control rule updating component 935 can be configured to or otherwise support means for updating a policy control rule associated with one or both of a PDU set marking or a data burst marking according to at least one marking mechanism.

[0237] Additionally or alternatively, according to examples as disclosed herein, the communication manager 920 may support wireless communications at the first network entity. The subscription request component 925 may be configured to or otherwise support a component for outputting a request to send information indicating a marking mechanism to a core network entity, wherein the marking mechanism enables identification of packets belonging to the same PDU set or the same data burst. The notification component 930 may be configured to or otherwise support a component for obtaining information indicating a marking mechanism from the core network entity in accordance with the request. The service flow marking component 950 may be configured to or otherwise support a component for outputting an indication of a marking mechanism to a second network entity, wherein the indication of the marking mechanism to the second network entity is associated with the establishment of a service flow according to the marking mechanism.

[0238] Additionally or alternatively, according to examples as disclosed herein, the communication manager 920 may support wireless communications at the first network entity. The subscription request component 925 may be configured as or otherwise support a means for obtaining a request from the second network entity to send information indicating a marking mechanism, wherein the marking mechanism enables identification of packets belonging to the same PDU set or the same data burst. The policy control rule component 955 may be configured as or otherwise support a means for obtaining information indicating a marking mechanism according to one or more policy control rules. The notification component 930 may be configured as or otherwise support a means for outputting information indicating a marking mechanism to the second network entity according to the request, wherein the information indicating the marking mechanism is associated with establishment of a traffic flow according to the marking mechanism.

[0239] Fig.10A block diagram 1000 of a communication manager 1020 supporting negotiation and notification of PDU sets or data burst marking mechanisms according to one or more aspects of the present disclosure is shown. The communication manager 1020 can be an example of aspects of the communication manager 820, the communication manager 920, or both as described herein. The communication manager 1020 or its various components can be examples of components for performing various aspects of the negotiation and notification of PDU sets or data burst marking mechanisms as described herein. For example, the communication manager 1020 can include a subscription request component 1025, a notification component 1030, a policy control rule update component 1035, a network configuration component 1040, a marking mechanism component 1045, a traffic flow marking component 1050, a policy control rule component 1055, an AF to PCF relay component 1060, a network link component 1065, a monitoring component 1070, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses), which communication may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with the network entity 105, between devices, components, or virtualized components associated with the network entity 105), or any combination thereof.

[0240] According to examples as disclosed herein, the communication manager 1020 may support wireless communications at a network entity. The subscription request component 1025 may be configured to or otherwise support a component for outputting a request to send information indicating a set of available marking mechanisms for identifying packets belonging to the same PDU set or the same data burst to a core network entity. The notification component 1030 may be configured to or otherwise support a component for obtaining information indicating a set of available marking mechanisms from the core network entity in response to the request. The policy control rule update component 1035 may be configured to or otherwise support a component for outputting an indication of a subset of one or more marking mechanisms from the set of available marking mechanisms to the core network entity, wherein at least one marking mechanism in the subset of one or more marking mechanisms corresponds to a policy control rule update for the core network entity.

[0241] In some examples, to support outbound requests, subscription request component 1025 may be configured or otherwise support means for outbound requests to a network exposure function via a subscription request message, wherein the core network entity includes the network exposure function.

[0242] In some examples, the subscription request message includes an event indicating that the request corresponds to one or both of a PDU set flag or a data burst flag.

[0243] In some examples, the subscription request message is an event exposure subscription request message.

[0244] In some examples, to support obtaining information, notification component 1030 can be configured or otherwise support means for obtaining information from a network exposure function via an event exposure notification message, wherein the core network entity includes the network exposure function.

[0245] In some examples, the core network entity includes a NEF, and the information indicating the set of available marking mechanisms is associated with the NEF.

[0246] In some examples, to support obtaining this information, notification component 1030 may be configured as or otherwise support a component for obtaining capability information associated with a core network entity, wherein the capability information indicates a set of available marking mechanisms, and wherein obtaining the information is associated with exposure of the set of available marking mechanisms to the network entity.

[0247] In some examples, to support outputting the indication, the policy control rule updating component 1035 can be configured or otherwise support means for outputting the indication to a policy control function, wherein the core network entity includes the policy control function.

[0248] In some examples, the core network entity may include a PCF, and policy control rule updates for the core network entity may be associated with the PCF.

[0249] In some examples, each respective marking mechanism in a subset of the one or more marking mechanisms is compatible with the network entity.

[0250] In some examples, to support outputting the indication, network link component 1065 may be configured or otherwise support means for outputting the indication to the policy control function via the network exposure function.

[0251] In some examples, the set of available marking mechanisms is associated with a network configuration.

[0252] In some examples, the set of available tagging mechanisms is stored in one or more of: a memory accessible by the network exposure function; a unified data repository; or an operations, management, and maintenance entity depending on the network configuration.

[0253] In some examples, to support obtaining this information, network configuration component 1040 may be configured as or otherwise support components for obtaining information based on the network configuration from one or more of: a memory accessible by the network exposure function; a unified data repository; or an operations, management, and maintenance entity.

[0254] In some examples, the network entity is an application function and the core network entity includes one or both of a network exposure function or a policy control function.

[0255] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1020 can support wireless communications at the first network entity. In some examples, the subscription request component 1025 can be configured as or otherwise support a means for obtaining, from the second network entity, a request to send information indicating a set of available marking mechanisms for identifying packets belonging to the same PDU set or the same data burst. The network configuration component 1040 can be configured as or otherwise support a means for obtaining information indicating a set of available marking mechanisms according to a network configuration. In some examples, the notification component 1030 can be configured as or otherwise support a means for outputting, in response to the request, information indicating a set of available marking mechanisms to the second network entity.

[0256] In some examples, to support obtaining the request, subscription request component 1025 can be configured or otherwise support means for obtaining the request from an application function via a subscription request message, where the second network entity is the application function.

[0257] In some examples, the subscription request message includes an event indicating that the request corresponds to one or both of a PDU set flag or a data burst flag.

[0258] In some examples, the subscription request message is an event exposure subscription request message.

[0259] In some examples, to support outputting this information, notification component 1030 can be configured or otherwise support means for outputting the information to an application function via an event exposure notification message, where the second network entity is the application function.

[0260] In some examples, AF to PCF relay component 1060 can be configured as or otherwise support means for obtaining, from the second network entity, information indicating a subset of one or more marking mechanisms from the set of available marking mechanisms. In some examples, AF to PCF relay component 1060 can be configured as or otherwise support means for outputting an indication of the subset of one or more marking mechanisms to a policy control function, wherein at least one marking mechanism in the subset of one or more marking mechanisms corresponds to a policy control rule update for the policy control function.

[0261] In some examples, each respective marking mechanism in the subset of the one or more marking mechanisms is compatible with the second network entity.

[0262] In some examples, the set of available tagging mechanisms is stored in one or more of: a memory accessible by the network exposure function; a unified data repository; or an operations, management, and maintenance entity depending on the network configuration.

[0263] In some examples, to support obtaining this information, network configuration component 1040 may be configured as or otherwise support components for obtaining information based on the network configuration from one or more of: a memory accessible by the network exposure function; a unified data repository; or an operations, management, and maintenance entity.

[0264] In some examples, the first network entity is a network exposed function and the second network entity is an application function.

[0265] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1020 can support wireless communications at the first network entity. The marking mechanism component 1045 can be configured as or otherwise support means for obtaining, from the second network entity, information indicating a subset of one or more marking mechanisms from a set of available marking mechanisms, wherein the set of available marking mechanisms enables identification of packets belonging to the same PDU set or the same data burst. In some examples, the policy control rule updating component 1035 can be configured as or otherwise support means for updating a policy control rule associated with one or both of a PDU set marking or a data burst marking according to at least one marking mechanism from the subset of one or more marking mechanisms.

[0266] In some examples, to support updating policy control rules, the policy control rule updating component 1035 may be configured as or otherwise support components for permitting the first network entity to modify marking options for one or both of PDU set marking or data burst marking for dynamic policy control rules used by a session management function.

[0267] In some examples, to support obtaining this information, AF to PCF relay component 1060 can be configured or otherwise support means for obtaining information from an application function via a network exposure function, where the second network entity is the application function.

[0268] In some examples, each respective marking mechanism in a subset of one or more marking mechanisms is compatible with the application functionality.

[0269] In some examples, the set of available marking mechanisms is associated with a network configuration.

[0270] In some examples, the set of available tagging mechanisms is stored in one or more of: a memory accessible by the network exposure function; a unified data repository; or an operations, management, and maintenance entity depending on the network configuration.

[0271] In some examples, network configuration component 1040 may be configured as or otherwise support means for obtaining information based on the network configuration from one or more of: a memory accessible by a network exposure function; a unified data repository; or an operations, management, and maintenance entity.

[0272] In some examples, the first network entity is a policy control function and the second network entity is an application function.

[0273] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1020 may support wireless communications at the first network entity. In some examples, the subscription request component 1025 may be configured to or otherwise support a component for outputting a request to send information indicating a marking mechanism to a core network entity, wherein the marking mechanism enables identification of packets belonging to the same PDU set or the same data burst. In some examples, the notification component 1030 may be configured to or otherwise support a component for obtaining information indicating a marking mechanism from the core network entity in accordance with the request. The service flow marking component 1050 may be configured to or otherwise support a component for outputting an indication of a marking mechanism to a second network entity, wherein the indication of the marking mechanism to the second network entity is associated with the establishment of a service flow according to the marking mechanism.

[0274] In some examples, to support outbound requests, subscription request component 1025 may be configured or otherwise support means for outbound requests to a session management function via a subscription request message, wherein the core network entity includes the session management function.

[0275] In some examples, the subscription request message includes an event indicating that the request corresponds to one or both of a PDU set flag or a data burst flag.

[0276] In some examples, to support outputting the request, subscription request component 1025 may be configured as or otherwise support components for outputting the request to a session management function via a network exposure function and a unified data management function, wherein the core network entity also includes the network exposure function and the unified data management function.

[0277] In some examples, the subscription request message is an event exposure subscription request message.

[0278] In some examples, the marking mechanism is associated with dynamically retrieving one or more policy control rules from a policy control function during PDU session establishment or modification. In some examples, the one or more policy control rules are based on one or more marking mechanisms compatible with the first network entity.

[0279] In some examples, the marking mechanism is associated with one or more policy control rules predefined for the core network entity. In some examples, the one or more policy control rules are based on one or more marking mechanisms compatible with the first network entity.

[0280] In some examples, to support obtaining information, notification component 1030 can be configured or otherwise support means for obtaining information from a session management function via an event exposure notification message, wherein the core network entity includes the session management function.

[0281] In some examples, a marking mechanism enables identification of sets of PDUs or data bursts transmitted by an application server to a user plane function.

[0282] In some examples, the first network entity is an application function and the core network entity is a session management function. In some examples, the second network entity is an application server.

[0283] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1020 may support wireless communications at the first network entity. In some examples, the subscription request component 1025 may be configured as or otherwise support a component for obtaining a request from the second network entity to send information indicating a marking mechanism, wherein the marking mechanism enables identification of packets belonging to the same PDU set or the same data burst. The policy control rule component 1055 may be configured as or otherwise support a component for obtaining information indicating a marking mechanism according to one or more policy control rules. In some examples, the notification component 1030 may be configured as or otherwise support a component for outputting information indicating a marking mechanism to the second network entity according to the request, wherein the information indicating the marking mechanism is associated with the establishment of a service flow according to the marking mechanism.

[0284] In some examples, to support obtaining the request, subscription request component 1025 can be configured or otherwise support means for obtaining the request from an application function via a subscription request message, where the second network entity is the application function.

[0285] In some examples, the subscription request message includes an event indicating that the request corresponds to one or both of a PDU set flag or a data burst flag.

[0286] In some examples, monitoring component 1070 can be configured or otherwise support means for monitoring subscription request messages based on events.

[0287] In some examples, to support obtaining the request, subscription request component 1025 can be configured as or otherwise support means for obtaining the request from the application function via the network exposure function and the unified data management function.

[0288] In some examples, the subscription request message is an event exposure subscription request message.

[0289] In some examples, the policy control rules component 1055 may be configured to or otherwise support components for dynamically obtaining one or more policy control rules from a policy control function during PDU session establishment or modification, wherein the one or more policy control rules are based on one or more marking mechanisms compatible with the first network entity.

[0290] In some examples, the one or more policy control rules are predefined at the first network entity. In some examples, the one or more policy control rules are based on one or more marking mechanisms compatible with the first network entity.

[0291] In some examples, the network configuration component 1040 may be configured to or otherwise support means for selecting a user plane function based on a marking mechanism. In some examples, the network configuration component 1040 may be configured to or otherwise support means for configuring a user plane function based on a marking mechanism, wherein configuration of the user plane function based on the marking mechanism is associated with establishment of a traffic flow according to the marking mechanism.

[0292] In some examples, network configuration component 1040 may be configured as or otherwise support means for obtaining, from a user plane function, information indicating capabilities of the user plane function associated with a marking mechanism, wherein the user plane function is selected based on the capabilities of the user plane function.

[0293] In some examples, network configuration component 1040 may be configured or otherwise support means for searching a set of marking mechanism options based on one or more marking mechanisms compatible with the second network entity. In some examples, network configuration component 1040 may be configured or otherwise support means for identifying a user plane function based on searching a set of marking mechanism options, wherein the user plane function is identified based on enabling at least one of the one or more marking mechanisms compatible with the second network entity.

[0294] In some examples, to support outputting this information, notification component 1030 can be configured or otherwise support means for outputting the information to an application function via an event exposure notification message, where the second network entity is the application function.

[0295] In some examples, a marking mechanism enables identification of sets of PDUs or data bursts transmitted by an application server to a user plane function.

[0296] In some examples, the first network entity is a session management function and the second network entity is an application function.

[0297] Fig.11 A diagram of a system 1100 including a device 1105 supporting negotiation and notification of a PDU set or data burst marking mechanism according to one or more aspects of the present disclosure is shown. The device 1105 may be an example of a device 805, a device 905, or a network entity 105 as described herein, or include components thereof. The device 1105 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which communication may include communication through one or more wired interfaces, through one or more wireless interfaces, or any combination thereof. The device 1105 may include components that support output and acquisition communications, such as a communication manager 1120, a transceiver 1110, an antenna 1115, a memory 1125, a code 1130, and a processor 1135. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1140).

[0298] The transceiver 1110 may support bidirectional communication via a wired link, a wireless link, or both, as described herein. In some examples, the transceiver 1110 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1110 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1105 may include one or more antennas 1115 that may be capable of (e.g., concurrently) sending or receiving wireless transmissions. The transceiver 1110 may also include a modem for modulating a signal, providing the modulated signal for transmission (e.g., through one or more antennas 1115, through a wired transmitter), receiving the modulated signal (e.g., from one or more antennas 1115, from a wired receiver), and demodulating the signal. The transceiver 1110 or the transceiver 1110 and one or more antennas 1115 or a wired interface (where applicable) may be an example of a transmitter 815, a transmitter 915, a receiver 810, a receiver 910, or any combination thereof or any component thereof as described herein. In some examples, the transceiver may be operable to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).

[0299] The memory 1125 may include RAM and ROM. The memory 1125 may store computer-readable, computer-executable code 1130 including instructions that, when executed by the processor 1135, cause the device 1105 to perform various functions described herein. The code 1130 may be stored in a non-transitory computer-readable medium such as a system memory or another type of memory. In some cases, the code 1130 may not be directly executable by the processor 1135, but may (e.g., when compiled and executed) cause the computer to perform the functions described herein. In some cases, the memory 1125 may also include, among other things, a BIOS that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0300] The processor 1135 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, a discrete gate or transistor logic, a discrete hardware component, or any combination thereof). In some cases, the processor 1135 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 1135. The processor 1135 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 1125) to enable the device 1105 to perform various functions (e.g., functions or tasks that support negotiation and notification of a PDU set or data burst marking mechanism). For example, the device 1105 or a component of the device 1105 may include a processor 1135 and a memory 1125 coupled to the processor 1135, and the processor 1135 and the memory 1125 are configured to perform the various functions described herein. Processor 1135 can be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that can host functionality for performing functions of device 1105 (e.g., by executing code 1130).

[0301] In some examples, bus 1140 may support communications of a protocol layer (e.g., within a protocol layer) of a protocol stack. In some examples, bus 1140 may support communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within a component of device 1105, or communications performed between different components of device 1105 that may be co-located or located in different locations (e.g., where device 1105 may refer to a system in which one or more of communication manager 1120, transceiver 1110, memory 1125, code 1130, and processor 1135 may be located in one of these different components or divided between different components).

[0302] In some examples, the communication manager 1120 may manage aspects of communications with the core network 130 (e.g., via one or more wired or wireless backhaul links). For example, the communication manager 1120 may manage the delivery of data communications for client devices such as one or more UEs 115. In some examples, the communication manager 1120 may manage communications with other network entities 105 and may include a controller or scheduler for controlling communications with the UE 115 in coordination with the other network entities 105. In some examples, the communication manager 1120 may support an X2 interface within an LTE / LTE-A wireless communication network technology to provide communications between network entities 105.

[0303] According to examples as disclosed herein, the communication manager 1120 may support wireless communications at a network entity. For example, the communication manager 1120 may be configured to or otherwise support a component for outputting a request to send information indicating a set of available marking mechanisms for identifying packets belonging to the same PDU set or the same data burst to a core network entity. The communication manager 1120 may be configured to or otherwise support a component for obtaining information indicating a set of available marking mechanisms from the core network entity in response to the request. The communication manager 1120 may be configured to or otherwise support a component for outputting an indication of a subset of one or more marking mechanisms from the set of available marking mechanisms to the core network entity, wherein at least one marking mechanism in the subset of one or more marking mechanisms corresponds to a policy control rule update for the core network entity.

[0304] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1120 may support wireless communications at the first network entity. For example, the communication manager 1120 may be configured as or otherwise support a means for obtaining, from the second network entity, a request to send information indicating a set of available marking mechanisms for identifying packets belonging to the same PDU set or the same data burst. The communication manager 1120 may be configured as or otherwise support a means for obtaining information indicating a set of available marking mechanisms according to a network configuration. The communication manager 1120 may be configured as or otherwise support a means for outputting, in response to the request, information indicating a set of available marking mechanisms to the second network entity.

[0305] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1120 may support wireless communications at the first network entity. For example, the communication manager 1120 may be configured as or otherwise support means for obtaining, from the second network entity, information indicating a subset of one or more marking mechanisms from a set of available marking mechanisms, wherein the set of available marking mechanisms enables identification of packets belonging to the same PDU set or the same data burst. The communication manager 1120 may be configured as or otherwise support means for updating a policy control rule associated with one or both of the PDU set marking or the data burst marking according to at least one marking mechanism from the subset of one or more marking mechanisms.

[0306] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1120 may support wireless communications at the first network entity. For example, the communication manager 1120 may be configured as or otherwise support a component for outputting a request to send information indicating a marking mechanism to a core network entity, wherein the marking mechanism enables identification of packets belonging to the same PDU set or the same data burst. The communication manager 1120 may be configured as or otherwise support a component for obtaining information indicating a marking mechanism from the core network entity in accordance with the request. The communication manager 1120 may be configured as or otherwise support a component for outputting an indication of a marking mechanism to a second network entity, wherein the indication of the marking mechanism to the second network entity is associated with the establishment of a service flow according to the marking mechanism.

[0307] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1120 may support wireless communications at the first network entity. For example, the communication manager 1120 may be configured as or otherwise support a component for obtaining a request to send information indicating a marking mechanism from a second network entity, wherein the marking mechanism enables identification of packets belonging to the same PDU set or the same data burst. The communication manager 1120 may be configured as or otherwise support a component for obtaining information indicating a marking mechanism according to one or more policy control rules. The communication manager 1120 may be configured as or otherwise support a component for outputting information indicating a marking mechanism to the second network entity according to the request, wherein the information indicating the marking mechanism is associated with the establishment of a service flow according to the marking mechanism.

[0308] By including or configuring a communications manager 1120 according to the examples described herein, the device 1105 may support techniques for improved communications reliability, reduced latency, an improved user experience associated with reduced processing, reduced power consumption, more efficient use of communications resources, improved coordination between devices, longer battery life, and improved use of processing power.

[0309] In some examples, the communication manager 1120 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the transceiver 1110, one or more antennas 1115 (e.g., where applicable), or any combination thereof. Although the communication manager 1120 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1120 may be supported or performed by the processor 1135, the memory 1125, the code 1130, the transceiver 1110, or any combination thereof. For example, the code 1130 may include instructions that are executable by the processor 1135 to cause the device 1105 to perform various aspects of the negotiation and notification of PDU sets or data burst marking mechanisms as described herein, or the processor 1135 and the memory 1125 may be otherwise configured to perform or support such operations.

[0310] Fig.12 A flow chart illustrating a method 1200 for supporting negotiation and notification of a PDU set or data burst marking mechanism according to one or more aspects of the present disclosure is shown. The operations of the method 1200 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1200 may be implemented by a network entity or a component thereof as described herein. Figures 1 to 11 In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0311] At 1205, the method may include obtaining information indicating a set of available marking mechanisms for identifying packets belonging to the same PDU set or the same data burst from a core network entity. The operations of 1205 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1205 may be performed as described in reference to Fig.10 The notification component 1030 is used to execute.

[0312] At 1210, the method may include: outputting to the core network entity an indication of at least one marking mechanism from the set of available marking mechanisms corresponding to a policy control rule update for the core network entity. The operations of 1210 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1210 may be performed as described in reference to Fig.10 The policy control rule update component 1035 is used to execute.

[0313] Fig.13A flow chart illustrating a method 1300 for supporting negotiation and notification of a PDU set or data burst marking mechanism according to one or more aspects of the present disclosure is shown. The operations of the method 1300 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1300 may be implemented by a network entity or a component thereof as described herein. Figures 1 to 11 In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0314] At 1305, the method may include: outputting to the second network entity information indicating a set of available marking mechanisms for identifying packets belonging to the same PDU set or the same data burst. The operations of 1305 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1305 may be performed as described in reference to Fig.10 The notification component 1030 is used to execute.

[0315] At 1310, the method may include obtaining, from a second network entity, an indication of at least one marking mechanism from a set of available marking mechanisms. The operations of 1310 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1310 may be performed as described in reference to Fig.10 The policy control rule update component 1035 is used to execute.

[0316] Fig.14 A flow chart illustrating a method 1400 for supporting negotiation and notification of a PDU set or data burst marking mechanism according to one or more aspects of the present disclosure is shown. The operations of the method 1400 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1400 may be implemented by a network entity or a component thereof as described herein. Figures 1 to 11 In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0317] At 1405, the method may include obtaining, from a second network entity, information indicating at least one marking mechanism from a set of available marking mechanisms, wherein the set of available marking mechanisms enables identification of packets belonging to the same PDU set or the same data burst. The operations of 1405 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1405 may be performed as described in reference to Fig.10 The marking mechanism component 1045 is executed.

[0318] At 1410, the method may include updating a policy control rule associated with one or both of a PDU set tag or a data burst tag according to at least one tagging mechanism. The operations of 1410 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1410 may be performed as described in reference to Fig.10 The policy control rule update component 1035 is used to execute.

[0319] Fig.15 A flow chart illustrating a method 1500 for supporting negotiation and notification of a PDU set or data burst marking mechanism according to one or more aspects of the present disclosure is shown. The operations of the method 1500 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1500 may be implemented by a network entity or a component thereof as described herein. Figures 1 to 11 In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0320] At 1505, the method may include: outputting to a core network entity a request to send information indicating a marking mechanism, wherein the marking mechanism enables identification of packets belonging to the same PDU set or the same data burst. The operations of 1505 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1505 may be performed as described in reference to Fig.10 The subscription request component 1025 is used to execute.

[0321] At 1510, the method may include: obtaining information indicating a marking mechanism from a core network entity according to the request. The operations of 1510 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1510 may be performed as described in reference to Fig.10 The notification component 1030 is used to execute.

[0322] At 1515, the method may include: outputting an indication of the marking mechanism to the second network entity, wherein the indication of the marking mechanism to the second network entity is associated with the establishment of a traffic flow according to the marking mechanism. The operations of 1515 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1515 may be performed as described in reference to Fig.10 The business flow marking component 1050 is used to execute.

[0323] Fig.16 A flow chart illustrating a method 1600 for supporting negotiation and notification of a PDU set or data burst marking mechanism according to one or more aspects of the present disclosure is shown. The operations of the method 1600 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1600 may be implemented by a network entity or a component thereof as described in reference to Figures 1 to 11 In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0324] At 1605, the method may include obtaining, from a second network entity, a request to send information indicating a marking mechanism, wherein the marking mechanism enables identification of packets belonging to the same PDU set or the same data burst. The operations of 1605 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1605 may be performed as described in reference to Fig.10 The subscription request component 1025 is used to execute.

[0325] At 1610, the method may include obtaining information indicating a marking mechanism according to one or more policy control rules. The operations of 1610 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1610 may be performed as described in reference to Fig.10 The policy control rule component 1055 is used for execution.

[0326] At 1615, the method may include: outputting information indicating a marking mechanism to the second network entity according to the request, wherein the information indicating the marking mechanism is associated with establishing a service flow according to the marking mechanism. The operations of 1615 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1615 may be performed as described in reference to Fig.10 The notification component 1030 is used to execute.

[0327] The following provides an overview of various aspects of the disclosure:

[0328] Aspect 1: A method of wireless communication performed by a network entity, comprising: outputting a request to a core network entity for sending information indicating a set of available marking mechanisms for identifying packets belonging to the same PDU set or the same data burst; obtaining the information indicating the set of available marking mechanisms from the core network entity in response to the request; and outputting an indication of a subset of one or more marking mechanisms from the set of available marking mechanisms to the core network entity, wherein at least one marking mechanism in the subset of one or more marking mechanisms corresponds to a policy control rule update for the core network entity.

[0329] Aspect 2: The method according to aspect 1, wherein outputting the request comprises: outputting the request to a NEF via a subscription request message, wherein the core network entity comprises the NEF.

[0330] Aspect 3: The method according to aspect 2, wherein the subscription request message includes an event indicating that the request corresponds to one or both of a PDU set flag or a data burst flag.

[0331] Aspect 4: The method according to any one of Aspects 2 to 3, wherein the subscription request message is an event exposure subscription request message.

[0332] Aspect 5: The method according to any one of aspects 1 to 4, wherein obtaining the information comprises: obtaining the information from a NEF via an event exposure notification message, wherein the core network entity comprises the NEF.

[0333] Aspect 6: The method according to any one of aspects 1 to 4, wherein the core network entity comprises a NEF, and wherein the information indicating the set of available marking mechanisms is associated with the NEF.

[0334] Aspect 7: A method according to any one of Aspects 1 to 6, wherein obtaining the information comprises: obtaining capability information associated with the core network entity, wherein the capability information indicates the set of available marking mechanisms, and wherein obtaining the information is associated with exposure of the set of available marking mechanisms to the network entity.

[0335] Aspect 8: The method according to any one of Aspects 1 to 7, wherein outputting the indication comprises: outputting the indication to a PCF, wherein the core network entity comprises the PCF.

[0336] Aspect 9: The method according to any one of aspects 1 to 7, wherein the core network entity comprises a PCF, and wherein the policy control rule update for the core network entity is associated with the PCF.

[0337] Aspect 10: The method according to any one of aspects 8 or 9, wherein each corresponding marking mechanism in the subset of one or more marking mechanisms is compatible with the network entity.

[0338] Aspect 11: The method according to any one of aspects 8 to 10, wherein outputting the indication comprises: outputting the indication to the PCF via the NEF.

[0339] Aspect 12: The method according to any one of aspects 1 to 11, wherein the set of available marking mechanisms is associated with a network configuration.

[0340] Aspect 13: A method according to Aspect 12, wherein the set of available marking mechanisms is stored in one or more of the following according to the network configuration: a memory accessible by the NEF; a unified data repository; or an operation, management and maintenance entity.

[0341] Aspect 14: A method according to any one of Aspects 12 to 13, wherein obtaining the information comprises: obtaining the information from one or more of the following according to the network configuration: a memory accessible by the NEF; a unified data repository; or an operation, management and maintenance entity.

[0342] Aspect 15: The method according to any one of aspects 1 to 14, wherein the network entity is an AF, and the core network entity includes one or both of a NEF or a PCF.

[0343] Aspect 16: A method of wireless communication performed by a first network entity, comprising: obtaining a request from a second network entity to send information indicating a set of available marking mechanisms for identifying packets belonging to the same PDU set or the same data burst; obtaining the information indicating the set of available marking mechanisms based on a network configuration; and outputting the information indicating the set of available marking mechanisms to the second network entity in response to the request.

[0344] Aspect 17: The method according to aspect 16, wherein obtaining the request comprises: obtaining the request from an AF via a subscription request message, wherein the second network entity is the AF.

[0345] Aspect 18: The method according to aspect 17, wherein the subscription request message includes an event indicating that the request corresponds to one or both of a PDU set flag or a data burst flag.

[0346] Aspect 19: The method according to any one of Aspects 17 to 18, wherein the subscription request message is an event exposure subscription request message.

[0347] Aspect 20: The method according to any one of aspects 16 to 19, wherein outputting the information comprises: outputting the information to an AF via an event exposure notification message, wherein the second network entity is the AF.

[0348] Aspect 21: The method according to any one of Aspects 16 to 20 further includes: obtaining information indicating a subset of one or more marking mechanisms from the set of available marking mechanisms from the second network entity; and outputting an indication of the subset of one or more marking mechanisms to the PCF, wherein at least one marking mechanism in the subset of one or more marking mechanisms corresponds to a policy control rule update for the PCF.

[0349] Aspect 22: The method according to aspect 21, wherein each corresponding marking mechanism in the subset of one or more marking mechanisms is compatible with the second network entity.

[0350] Aspect 23: A method according to any one of Aspects 16 to 22, wherein the set of available marking mechanisms is stored in one or more of the following according to the network configuration: a memory accessible by the NEF; a unified data repository; or an operation, management and maintenance entity.

[0351] Aspect 24: A method according to any one of Aspects 16 to 23, wherein obtaining the information comprises: obtaining the information from one or more of the following according to the network configuration: a memory accessible by the NEF; a unified data repository; or an operation, management and maintenance entity.

[0352] Aspect 25: The method according to any one of aspects 16 to 24, wherein the first network entity is a NEF and the second network entity is an AF.

[0353] Aspect 26: A method of wireless communication performed by a first network entity, comprising: obtaining information indicating a subset of one or more marking mechanisms from a set of available marking mechanisms from a second network entity, wherein the set of available marking mechanisms enables identification of packets belonging to the same PDU set or the same data burst; and updating a policy control rule associated with one or both of a PDU set marking or a data burst marking according to at least one marking mechanism in the subset of one or more marking mechanisms.

[0354] Aspect 27: The method according to aspect 26, wherein updating the policy control rules includes: allowing the first network entity to modify the marking options used for one or both of the PDU aggregation marking or the data burst marking for the dynamic policy control rules used by the SMF.

[0355] Aspect 28: The method according to any one of aspects 26 to 27, wherein obtaining the information comprises: obtaining the information from an AF via a NEF, wherein the second network entity is the AF.

[0356] Aspect 29: The method according to Aspect 28, wherein each corresponding marking mechanism in the subset of one or more marking mechanisms is compatible with the AF.

[0357] Aspect 30: The method according to any one of Aspects 26 to 29, wherein the set of available marking mechanisms is associated with a network configuration.

[0358] Aspect 31: A method according to Aspect 30, wherein the set of available marking mechanisms is stored in one or more of the following according to the network configuration: a memory accessible by the NEF; a unified data repository; or an operation, management and maintenance entity.

[0359] Aspect 32: The method according to any one of Aspects 30 to 31 further includes: obtaining the information from one or more of the following based on the network configuration: a memory accessible by the NEF; a unified data repository; or an operation, management and maintenance entity.

[0360] Aspect 33: The method according to any one of aspects 26 to 32, wherein the first network entity is a PCF and the second network entity is an AF.

[0361] Aspect 34: A method of wireless communication performed by a first network entity, comprising: outputting a request for sending information indicating a marking mechanism to a core network entity, wherein the marking mechanism enables identification of packets belonging to the same PDU set or the same data burst; obtaining the information indicating the marking mechanism from the core network entity based on the request; and outputting an indication of the marking mechanism to a second network entity, wherein the indication of the marking mechanism to the second network entity is associated with the establishment of a service flow based on the marking mechanism.

[0362] Aspect 35: The method according to aspect 34, wherein outputting the request comprises: outputting the request to an SMF via a subscription request message, wherein the core network entity comprises the SMF.

[0363] Aspect 36: The method according to aspect 35, wherein the subscription request message includes an event indicating that the request corresponds to one or both of a PDU aggregation flag or a data burst flag.

[0364] Aspect 37: The method according to any one of Aspects 35 to 36, wherein outputting the request comprises: outputting the request to the SMF via the NEF and the unified data management function, wherein the core network entity also includes the NEF and the unified data management function.

[0365] Aspect 38: A method according to any one of Aspects 35 to 37, wherein the subscription request message is an event exposure subscription request message.

[0366] Aspect 39: A method according to any one of Aspects 34 to 38, wherein the marking mechanism is associated with dynamically retrieving one or more policy control rules from the PCF during PDU session establishment or modification, and the one or more policy control rules are based on one or more marking mechanisms compatible with the first network entity.

[0367] Aspect 40: A method according to any one of Aspects 34 to 39, wherein the marking mechanism is associated with one or more policy control rules predefined for the core network entity, and the one or more policy control rules are based on one or more marking mechanisms compatible with the first network entity.

[0368] Aspect 41: The method according to any one of Aspects 34 to 40, wherein obtaining the information comprises: obtaining the information from an SMF via an event exposure notification message, wherein the core network entity comprises the SMF.

[0369] Aspect 42: The method according to any one of aspects 34 to 41, wherein the marking mechanism enables identification of a set of PDUs or a data burst transmitted by the AS to a user plane function.

[0370] Aspect 43: The method according to any one of aspects 34 to 42, wherein the first network entity is an AF, the core network entity is an SMF, and the second network entity is an AS.

[0371] Aspect 44: A method of wireless communication performed by a first network entity, comprising: obtaining a request for sending information indicating a marking mechanism from a second network entity, wherein the marking mechanism enables identification of packets belonging to the same PDU set or the same data burst; obtaining the information indicating the marking mechanism according to one or more policy control rules; and outputting the information indicating the marking mechanism to the second network entity according to the request, wherein the information indicating the marking mechanism is associated with the establishment of a service flow according to the marking mechanism.

[0372] Aspect 45: The method according to aspect 44, wherein obtaining the request comprises: obtaining the request from an AF via a subscription request message, wherein the second network entity is the AF.

[0373] Aspect 46: The method according to aspect 45, wherein the subscription request message includes an event indicating that the request corresponds to one or both of a PDU aggregation flag or a data burst flag.

[0374] Aspect 47: The method according to Aspect 46 further includes: monitoring the subscription request message based on the event.

[0375] Aspect 48: The method according to any one of aspects 45 to 47, wherein obtaining the request comprises: obtaining the request from the AF via the NEF and the unified data management function.

[0376] Aspect 49: A method according to any one of Aspects 45 to 48, wherein the subscription request message is an event exposure subscription request message.

[0377] Aspect 50: The method according to any one of Aspects 44 to 49 further includes: dynamically obtaining the one or more policy control rules from the PCF during PDU session establishment or modification, wherein the one or more policy control rules are based on one or more marking mechanisms compatible with the first network entity.

[0378] Aspect 51: The method according to any one of aspects 44 to 50, wherein the one or more policy control rules are predefined at the first network entity, and the one or more policy control rules are based on one or more marking mechanisms compatible with the first network entity.

[0379] Aspect 52: The method according to any one of Aspects 44 to 51 further includes: selecting a user plane function based on the marking mechanism; and configuring the user plane function based on the marking mechanism, wherein the configuration of the user plane function based on the marking mechanism is associated with the establishment of the service flow according to the marking mechanism.

[0380] Aspect 53: The method according to Aspect 52 further includes: obtaining, from the user plane function, information indicating capabilities of the user plane function associated with the marking mechanism, wherein the user plane function is selected based on the capabilities of the user plane function.

[0381] Aspect 54: The method according to any one of Aspects 52 to 53 further includes: searching for a set of marking mechanism options based on one or more marking mechanisms compatible with the second network entity; and identifying the user plane function based on the search for the set of marking mechanism options, wherein the user plane function is identified based on at least one marking mechanism of the one or more marking mechanisms that is compatible with the second network entity.

[0382] Aspect 55: The method according to any one of aspects 44 to 54, wherein outputting the information comprises: outputting the information to an AF via an event exposure notification message, wherein the second network entity is the AF.

[0383] Aspect 56: A method according to any one of aspects 44 to 55, wherein the marking mechanism enables identification of a set of PDUs or a data burst transmitted by the AS to a user plane function.

[0384] Aspect 57: The method according to any one of aspects 44 to 56, wherein the first network entity is a SMF and the second network entity is an AF.

[0385] Aspect 58: An apparatus for wireless communication at a network entity, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 1 to 15.

[0386] Aspect 59: An apparatus for wireless communication at a network entity, comprising: at least one means for performing the method according to any one of aspects 1 to 15.

[0387] Aspect 60: A non-transitory computer-readable medium storing code for wireless communication at a network entity, the code comprising instructions executable by a processor to perform the method according to any one of aspects 1 to 15.

[0388] Aspect 61: An apparatus for wireless communication at a first network entity, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 16 to 25.

[0389] Aspect 62: An apparatus for wireless communication at a first network entity, comprising: at least one means for performing a method according to any one of aspects 16 to 25.

[0390] Aspect 63: A non-transitory computer-readable medium storing code for wireless communication at a first network entity, the code comprising instructions executable by a processor to perform the method according to any one of aspects 16 to 25.

[0391] Aspect 64: An apparatus for wireless communication at a first network entity, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 26 to 33.

[0392] Aspect 65: An apparatus for wireless communication at a first network entity, comprising: at least one means for performing a method according to any one of aspects 26 to 33.

[0393] Aspect 66: A non-transitory computer-readable medium storing code for wireless communication at a first network entity, the code comprising instructions executable by a processor to perform the method according to any one of aspects 26 to 33.

[0394] Aspect 67: An apparatus for wireless communication at a first network entity, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 34 to 43.

[0395] Aspect 68: An apparatus for wireless communication at a first network entity, comprising: at least one means for performing a method according to any one of aspects 34 to 43.

[0396] Aspect 69: A non-transitory computer-readable medium storing code for wireless communication at a first network entity, the code comprising instructions executable by a processor to perform the method according to any one of aspects 34 to 43.

[0397] Aspect 70: An apparatus for wireless communication at a first network entity, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 44 to 57.

[0398] Aspect 71: An apparatus for wireless communication at a first network entity, comprising: at least one means for performing a method according to any one of aspects 44 to 57.

[0399] Aspect 72: A non-transitory computer-readable medium storing code for wireless communication at a first network entity, the code comprising instructions executable by a processor to perform the method according to any one of aspects 44 to 57.

[0400] The above methods describe possible implementations, and the operations and steps may be rearranged or otherwise modified, and other implementations are possible. In addition, aspects from two or more methods may be combined.

[0401] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for example purposes, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein may also be applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the described techniques may be applicable to various other wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0402] The information and signals described herein may be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the specification may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0403] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or performed with a general purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0404] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. When implemented in software executed by a processor, the functions may be stored on or sent via a computer-readable medium as one or more instructions or codes. Other examples and specific implementations are within the scope of the present disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hard wiring, or a combination of any of these items. Features that implement the functions may also be physically located at different locations, including being distributed so that various parts of the functions are implemented at different physical locations.

[0405] Computer-readable medium includes both non-transient computer storage medium and communication medium, and it includes any medium that promotes the transfer of computer program from one place to another place.Non-transient storage medium can be any available medium that can be accessed by general or special-purpose computer.By way of example and not limitation, non-transient computer-readable medium can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage device, disk storage device or other magnetic storage device, or can be used for carrying or storing desired program code member and can be accessed by general or special-purpose computer or general or special-purpose processor in the form of instruction or data structure Any other non-transient medium.In addition, any connection is appropriately referred to as computer-readable medium.For example, if software is sent from website, server or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are included in the definition of computer-readable medium. As used herein, disk and disc include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc, where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

[0406] As used herein, the term "or" is an inclusive "or" unless restrictive language is used with respect to the listed alternatives. For example, references to "X is based on A or B" should be interpreted as including within its scope X based on A, X based on B, and X based on A and B. In this regard, references to "X is based on A or B" refer to "at least one of A or B" or "one or more of A or B" because "or" is inclusive. Similarly, references to "X is based on A, B, or C" should be interpreted as including within its scope X based on A, X based on B, X based on C, X based on A and B, X based on A and C, X based on B and C, and X based on A, B, and C. In this regard, references to "X is based on A, B, or C" refer to "at least one of A, B, or C" or "one or more of A, B, or C" because "or" is inclusive. As an example of restrictive language, a reference to "X is based on only one of A or B" should be interpreted to include within its scope X being based on A and X being based on B, but not including X being based on both A and B. Additionally, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase "based on A" (where "A" can be information, a condition, a factor, etc.) should be interpreted as "based on at least A," unless specifically stated differently. Additionally, as used herein, the phrase "set" should be understood to include the possibility of a set having one member. That is, the phrase "set" should be understood in the same manner as "one or more" or "at least one."

[0407] The term "determining" encompasses a wide variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, database or other data structure), ascertaining, etc. Additionally, "determining" may include receiving (such as receiving information), accessing (such as accessing data in a memory), etc. Additionally, "determining" may include resolving, obtaining, selecting, choosing, establishing, and other such similar actions.

[0408] In the drawings, similar components or features may have the same reference label. In addition, various components of the same type may be distinguished by following the reference label with a dash and a second label to distinguish between the similar components. If only the first reference label is used in the specification, the description may apply to any of the similar components having the same first reference label, regardless of the second or other subsequent reference labels.

[0409] The descriptions set forth herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration," rather than "preferred" or "having advantages over other examples." The specific embodiments include specific details to provide an understanding of the described techniques. However, these techniques may be practiced without these specific details. In some instances, structures and devices are shown in block diagram form to avoid obscuring the concepts of the examples.

[0410] The description herein is provided to enable one of ordinary skill in the art to implement or use the present disclosure. Various modifications to the present disclosure will be apparent to one of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Thus, the present disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A network entity for wireless communication, comprising: Memory; and at least one processor coupled to the memory, wherein the at least one processor is configured to: obtaining, from a core network entity, information indicating a set of available marking mechanisms for identifying packets belonging to the same set of protocol data units (PDUs) or the same data burst; as well as An indication of at least one marking mechanism from the set of available marking mechanisms corresponding to a policy control rule update for the core network entity is output to the core network entity. 2 . The network entity of claim 1 , wherein the core network entity comprises a policy control function, and wherein the policy control rule update for the core network entity is associated with the policy control function. 3 . The network entity of claim 2 , wherein each respective marking mechanism of the at least one marking mechanism is compatible with the network entity.

4. The network entity according to claim 2, wherein, in order to output the indication, the at least one processor is configured to: The indication is output to the policy control function via a network exposure function.

5. The network entity of claim 1 , wherein to obtain the information, the at least one processor is configured to: Capability information associated with the core network entity is obtained, wherein the capability information indicates the set of available marking mechanisms, and wherein obtaining of the information is associated with exposing the set of available marking mechanisms to the network entity. The network entity of claim 1 , wherein the set of available marking mechanisms is associated with a network configuration.

7. The network entity of claim 6, wherein the set of available marking mechanisms is stored in one or more of: a memory accessible by a network exposure function; a unified data repository; or an operations, management, and maintenance entity based on the network configuration.

8. The network entity according to claim 6, wherein, in order to obtain the information, the at least one processor is configured to: The information is obtained from one or more of: a memory accessible by a network exposed function; a unified data repository; or an operations, administration, and maintenance entity according to the network configuration.

9. The network entity of claim 1, wherein the core network entity comprises a network exposure function, and wherein the information indicative of the set of available marking mechanisms is associated with the network exposure function.

10. The network entity of claim 1, wherein the network entity is an application function, and the core network entity comprises one or both of a network exposure function or a policy control function.

11. A first network entity for wireless communication, comprising: Memory; and at least one processor coupled to the memory, wherein the at least one processor is configured to: outputting, to the second network entity, information indicating a set of available marking mechanisms for identifying packets belonging to the same set of protocol data units (PDUs) or the same data burst; as well as An indication of at least one marking mechanism from the set of available marking mechanisms is obtained from the second network entity.

12. The first network entity according to claim 11, wherein, in order to output the information, the at least one processor is configured to: The information is output to an application function via an event exposure notification message, wherein the second network entity is the application function.

13. The first network entity of claim 11 , wherein the at least one processor is configured to: An indication of the at least one marking mechanism is output to a policy control function, wherein the at least one marking mechanism corresponds to a policy control rule update for the policy control function.

14. The first network entity of claim 13, wherein each respective marking mechanism of the at least one marking mechanism is compatible with the second network entity.

15. The first network entity of claim 11 , wherein the at least one processor is configured to: Said information indicative of said set of available marking mechanisms is obtained according to a network configuration.

16. The first network entity of claim 15, wherein the set of available marking mechanisms is stored in one or more of: a memory accessible by a network exposure function; a unified data repository; or an operations, administration, and maintenance entity according to the network configuration.

17. The first network entity of claim 15, wherein the at least one processor is further configured to: The information is obtained from one or more of: a memory accessible by a network exposed function; a unified data repository; or an operations, administration, and maintenance entity according to the network configuration.

18. The first network entity of claim 11, wherein the first network entity is a network exposure function and the second network entity is an application function.

19. A first network entity for wireless communication, comprising: Memory; and at least one processor coupled to the memory, wherein the at least one processor is configured to: obtaining, from the second network entity, information indicative of at least one marking mechanism from a set of available marking mechanisms, wherein said set of available marking mechanisms enables identification of packets belonging to the same set of protocol data units (PDUs) or the same burst of data; and Policy control rules associated with one or both of PDU aggregate marking or data burst marking are updated according to the at least one marking mechanism.

20. The first network entity of claim 19, wherein to update the policy control rules, the at least one processor is configured to: The first network entity is permitted to modify marking options for one or both of the PDU aggregate marking or the data burst marking for dynamic policy control rules used by a session management function.

21. The first network entity of claim 19, wherein to obtain the information, the at least one processor is configured to: The information is obtained from an application function via a network exposure function, wherein the second network entity is the application function.

22. The first network entity of claim 21, wherein each respective marking mechanism of the at least one marking mechanism is compatible with the application function.

23. The first network entity of claim 19, wherein the set of available marking mechanisms is associated with a network configuration.

24. The first network entity of claim 23, wherein the set of available marking mechanisms is stored in one or more of: a memory accessible by a network exposure function; a unified data repository; or an operations, administration, and maintenance entity according to the network configuration.

25. The first network entity of claim 23, wherein the at least one processor is configured to: The information is obtained from one or more of: a memory accessible by a network exposed function; a unified data repository; or an operations, administration, and maintenance entity according to the network configuration.

26. The first network entity of claim 19, wherein the first network entity is a policy control function and the second network entity is an application function.

27. A method of wireless communication performed by a network entity, comprising: obtaining, from a core network entity, information indicating a set of available marking mechanisms for identifying packets belonging to the same set of protocol data units (PDUs) or the same data burst; as well as An indication of at least one marking mechanism from the set of available marking mechanisms corresponding to a policy control rule update for the core network entity is output to the core network entity.

28. The method of claim 27, wherein the core network entity comprises a network exposure function, and wherein the information indicative of the set of available marking mechanisms is associated with the network exposure function.

29. The method of claim 27, wherein the core network entity comprises a policy control function, and wherein the policy control rule update for the core network entity is associated with the policy control function.

30. The method of claim 29, wherein outputting the indication comprises: The indication is output to the policy control function via a network exposure function.

Images