User-Plane Programmable Layer for Wireless Communication

Abstract

Methods, systems, and devices for wireless communication are described. A first wireless device can establish a User Plane Adaptive Protocol (UPAP) with a second wireless device. Thus, when generating a message to send to the second wireless device, the first wireless device can use UPAP layer entities to insert a main header and / or one or more service headers onto the network layer traffic. The main header may be common to multiple deployments, and the service headers may be unique for each deployment and / or each packet. One or more service headers may be used to perform Quality of Service (QoS) processing, to expose UPAP programmability to services and gateways, to perform on-pass header updates, to indicate instructions or rules, or any combination thereof.

Description

Technical Field

[0001] (Cross - Reference to Related Applications) This patent application claims priority to U.S. Patent Application No. 18 / 327,820, filed on June 1, 2023, by Elazzouni et al., titled "USER PLANE PROGRAMMABLE LAYER FOR RADIO COMMUNICATIONS", which has been assigned to the assignee of this specification and is hereby expressly incorporated herein by reference.

Background Art

[0002] The following relates to wireless communications including a user plane programmable layer.

[0003] Wireless communication systems are widely deployed to provide various types of communication content, including voice, video, packet data, messaging, and broadcast. These systems can 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), LTE-Advanced (LTE-A), or LTE-A Pro systems, as well as fifth-generation (5G) systems, sometimes referred to as New Radio (NR) systems. These systems may employ technologies 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 with a communication device that may be known as user equipment (UE). [Overview of the Initiative]

[0004] A method for wireless communication by a network entity is described. This method may include: sending a capability message from the network entity to a logical unit indicating that the network entity supports instructions for services associated with the radio layer for wireless communication with one or more UEs; establishing a data session with the logical unit and one of the UEs based on the transmission of the capability message; receiving instructions from the logical unit to perform radio functions associated with services with that UE based on the data session; and performing those instructions at the radio layer.

[0005] A network entity is described. The network entity may include one or more processors and one or more memories coupled to those one or more processors, which store processor executable code, and which, when the processor executable code is executed by one or more processors, cause the network entity to send a capability message from the network entity to a logical unit indicating that the network entity supports instructions for services associated with the radio layer for wireless communication with one or more UEs, and based on sending the capability message, cause the logical unit to establish a data session associated with one of the one or more UEs, and based on the data session, cause the logical unit to receive instructions for performing radio functions associated with services with that UE, and cause the instructions for performing those radio functions to be executed in the radio layer.

[0006] Another network entity is described. The network entity may include means for sending a capability message from the network entity to a logical unit indicating that the network entity supports instructions relating to a service associated with the radio layer for wireless communication with one or more UEs; means for establishing a data session associated with the logical unit and one of the UEs based on the transmission of the capability message; means for receiving instructions from the logical unit, based on the data session, for performing a radio function associated with the service with that UE; and means for performing the instructions for performing that radio function at the radio layer.

[0007] A non-temporary, computer-readable medium storing code for wireless communication by a network entity is described. This code may include instructions that can be executed by one or more processors to cause the network entity to send a capability message from the network entity to a logical unit indicating that the network entity supports instructions for services associated with the radio layer for wireless communication with one or more UEs; to establish a data session with the logical unit and one of the UEs based on the transmission of the capability message; to receive instructions from the logical unit to perform radio functions associated with the services with that UE based on the data session; and to execute instructions for performing those radio functions at the radio layer.

[0008] Some embodiments of the methods, network entities, and non-temporary computer-readable media described herein may further include operations, features, means, or instructions that receive a first message including instructions, packets, and headers, establish a data radio bearer with the UE based on a data session, transmit a second message including a first radio link control service data unit based on the establishment of the UE and the data radio bearer, receive a third message including a second radio link control service data unit based on the second message, the first radio link control service data unit including packets and headers, the second radio link control service data unit embeds the headers in a fourth message including a header and a response to a packet, transmit a fourth message based on an instruction, the fourth message including a response to a packet, and the instruction can be executed after receiving the third message.

[0009] In some embodiments of the methods, network entities, and non-temporary computer-readable media described herein, the fourth message includes a service header associated with the flow between the UE and the logical unit, the service header including instruction-based parameters.

[0010] Some embodiments of the methods, network entities, and non-temporary computer-readable media described herein may further include operations, features, means, or instructions which may receive a first message, including instructions and packets, and on the basis of the first message, execute the instructions; establish a data radio bearer with a UE on the basis of a data session; and transmit a second message, including packets, on the basis of establishing the data radio bearer with the UE and the instructions, and which may be executed before transmitting the second message.

[0011] In some embodiments of the methods, apparatus, and non-temporary computer-readable media described herein, the logical unit includes a second network entity.

[0012] A method for wireless communication by a network entity is described. This method may include: sending a capability message to a logical unit indicating the services supported by the network entity; establishing a data session with the logical unit and associated with a flow between the logical unit and the UE based on the transmission of the capability message; establishing a data radio bearer with the UE and associated with the flow based on the data session; receiving a first message associated with the flow from the logical unit, based on the data session with the logical unit, including a first header associated with a first layer; generating a radio link control service data unit including a second header associated with the first layer based on the first header and one or more radio functions of the network entity; and transmitting a second message including the radio link control service data unit via the data radio bearer.

[0013] A network entity is described. The network entity may include one or more processors and one or more memories coupled to those one or more processors, storing processor executable code, which, when the processor executable code is executed by one or more processors, cause a first UE to send a capability message to a logical unit indicating the services supported by the network entity, and, based on sending the capability message, cause the logical unit to establish a data session associated with a flow between the logical unit and the UE, and, based on the data session, cause the UE to establish a data radio bearer associated with the flow, and, based on the data session with the logical unit, cause the logical unit to receive a first message associated with the flow, including a first header associated with a first layer, and, based on the first header and one or more radio functions of the network entity, cause the UE to generate a radio link control service data unit including a second header associated with a first layer, and, via the data radio bearer, cause a second message including the radio link control service data unit to be sent.

[0014] Another network entity is described. The network entity may include means for sending capability messages to a logical unit indicating the services that the network entity supports; means for establishing a data session with the logical unit and associated with a flow between the logical unit and the UE based on sending capability messages; means for establishing a data radio bearer with the UE and associated with a flow based on the data session; means for receiving a first message associated with a flow from the logical unit, based on the data session with the logical unit, including a first header associated with a first layer; means for generating a radio link control service data unit including a second header associated with a first layer based on the first header and one or more radio functions of the network entity; and means for sending a second message including the radio link control service data unit via the data radio bearer.

[0015] A non-temporary computer-readable medium storing code for wireless communication by a network entity is described. This code may include instructions executable by one or more processors to cause the network entity to send a capability message to a logical unit indicating the services the network entity supports; to establish a data session with the logical unit and associated with a flow between the logical unit and the UE based on the transmission of the capability message; to establish a data radio bearer with the UE and associated with the flow based on the data session; to receive from the logical unit a first message associated with the flow, including a first header associated with a first layer, based on the data session with the logical unit; to generate a radio link control service data unit including a second header associated with a first layer, based on the first header and one or more radio functions of the network entity; and to send a second message containing the radio link control service data unit via the data radio bearer.

[0016] In some embodiments of the methods, network entities, and non-temporary computer-readable media described herein, a first message includes a main header and a first service header associated with a service, and a second message includes a main header, a first service header, and a second service header associated with the radio functionality of the network entity.

[0017] Some embodiments of the methods, network entities, and non-temporary computer-readable media described herein may further include operations, features, means, or instructions that, based on the prioritization, can receive a set of multiple messages from a logical unit, each of which includes a service header associated with a service, and that can perform prioritization on the set of multiple messages based on the corresponding service headers, and send a second message.

[0018] Some embodiments of the methods, network entities, and non-temporary computer-readable media described herein may further include operations, features, means, or instructions that modify a first service header based on instructions received from a second logical unit, and that a second message may be transmitted based on the modified first service header.

[0019] In some embodiments of the methods, network entities, and non-temporary computer-readable media described herein, a first message includes a set of service headers including a first service header, and the methods, apparatus, and non-temporary computer-readable media may include further operations, features, means, or instructions for adding a third service header to a second message based on instructions received from a second logical unit.

[0020] In some embodiments of the methods, network entities, and non-temporary computer-readable media described herein, a first message includes a set of service headers including a first service header, and a second message includes a subset of the set of service headers including the first service header, wherein the subset of the set of service headers does not include at least one service header from that set.

[0021] In some embodiments of the methods, network entities, and non-temporary computer-readable media described herein, a first header may include a directive indicating that a first message may be processed by the network entity before generating a radio link control service data unit, and a second header may be based on the directive indicating that the first message may be processed by the network entity.

[0022] In some embodiments of the methods, network entities, and non-temporary computer-readable media described herein, the first header includes an identifier of the network entity, instructions, measurements, information about a data session, or any combination thereof.

[0023] In some embodiments of the methods, network entities, and non-temporary computer-readable media described herein, the logical unit includes a second network entity, a user plane function, or both.

[0024] A method for wireless communication by a logic unit is described. The method includes receiving, by a network entity, a capability message indicating that the network entity supports instructions regarding services associated with a radio layer for wireless communication with a UE, establishing, based on the capability message, a data session associated with a flow between the logic unit and the UE, transmitting a first message including a main header, a service header associated with a first layer, an indication that the service header should be processed by the network entity, and instructions for performing radio functions associated with a service with the UE, and receiving a second message associated with the flow and including a main header based on the first message.

[0025] A logic unit is described. The logic unit includes one or more processors and one or more memories coupled to the one or more processors and storing processor-executable code, the processor-executable code being configured to cause the one or more processors to receive, from a first UE, a capability message indicating that a network entity supports instructions regarding services associated with a radio layer for wireless communication with the UE, establish, based on the capability message, a data session associated with a flow between the logic unit and the UE, transmit a first message including a main header, a service header associated with a first layer, an indication that the service header should be processed by the network entity, and instructions for performing radio functions associated with a service with the UE, and receive a second message associated with the flow and including a main header based on the first message.

[0026] Another logical unit is described. The logical unit may include means for receiving a capability message indicating that a network entity supports instructions for services associated with the radio layer for wireless communication with a UE; means for establishing a data session associated with a flow between the logical unit and the UE based on the capability message; means for sending a first message associated with the flow, including a main header, a service header associated with a first layer, an instruction that the service header should be processed by the network entity, and instructions for performing radio functions associated with the service with the UE; and means for receiving a second message associated with the flow, including a main header based on the first message.

[0027] A non-temporary computer-readable medium storing code for wireless communication by a logical unit is described. This code may include instructions, executable by one or more processors, to cause the logical unit to receive a capability message indicating that a network entity supports instructions for a service associated with the radio layer for wireless communication with a UE; to establish a data session associated with a flow between the logical unit and the UE based on the capability message; to send a first message associated with that flow, including a main header, a service header associated with a first layer, an instruction that the service header should be processed by a network entity, and instructions for performing radio functions associated with the service with the UE; and to receive a second message associated with that flow, including a main header based on the first message.

[0028] In some examples of the methods, logic units, and non-transitory computer-readable media described herein, the instruction that a service header may be processed by a network entity may include an instruction to perform that processing before generating a service data unit associated with a radio link control layer, an instruction to insert the service header within a first message, or both.

[0029] In some examples of the methods, logic units, and non-transitory computer-readable media described herein, the service header includes an identifier of a network entity, a second instruction, a measurement, or any combination thereof.

[0030] In some examples of the methods, logic units, and non-transitory computer-readable media described herein, the logic unit includes a second network entity, a user plane function, or both.

[0031] A method for wireless communication is described. The method may include generating a first service data unit associated with a radio link control layer, comprising a first packet, a first main header relating to the first packet, associated with a first layer above the radio link control layer, and a first service header relating to the first packet, associated with a service provided by one or more network entities in the network, wherein each of the first main header and the first service header is associated with a flow between a logical unit and a UE; generating a second service data unit associated with a radio link control layer, wherein the second service data unit comprises a second packet, a second main header relating to the first layer, and a second service header relating to the second packet, associated with a service, wherein each of the second main header and the second service header is associated with a flow between a logical unit and a UE, and the first service header and the second service header are different from each other; and outputting one or more messages comprising the first service data unit and the second service data unit.

[0032] The device is described. The device comprises one or more processors and one or more memories coupled to those one or more processors, which store processor executable code, and when the processor executable code is executed by one or more processors, causes a first UE to generate a first service data unit, which includes a first packet associated with the radio link control layer and associated with a first layer above the radio link control layer, and a first service header associated with the first packet and associated with a service provided by one or more network entities in the network, respectively However, it may include one or more memories configured to output one or more messages, each of the second main header and the second service header, which are associated with the flow between the logical unit and the UE and are associated with the radio link control layer, and each of the second main header and the second service header is associated with the flow between the logical unit and the UE, and the first service header and the second service header are different from each other, and the first service data unit and the second service data unit are included.

[0033] Another device is described. This device may include means for generating a first service data unit associated with a radio link control layer, comprising a first packet, a first main header relating to the first packet and associated with a first layer above the radio link control layer, and a first service header relating to the first packet and associated with a service provided by one or more network entities in the network, wherein each of the first main header and the first service header is associated with a flow between a logical unit and a UE; means for generating a second service data unit associated with a radio link control layer, wherein the second service data unit comprises a second packet, a second main header associated with the first layer, and a second service header relating to the second packet and associated with a service, wherein each of the second main header and the second service header is associated with a flow between a logical unit and a UE, and the first service header and the second service header are different from each other; and means for outputting one or more messages comprising the first service data unit and the second service data unit.

[0034] A non-temporary, computer-readable medium that stores codes for wireless communication by a device is described. The code may include instructions executable by one or more processors to cause a device to generate a first service data unit, which includes a first packet associated with a radio link control layer, a first main header relating to the first packet, which is associated with a first layer above the radio link control layer, and a first service header relating to a service provided by one or more network entities in the network; generate a second service data unit, which is associated with a radio link control layer, and each of the first main header and the first service header is associated with a flow between a logical unit and a UE; the second service data unit includes a second packet, a second main header associated with a first layer, and a second service header relating to a service, and each of the second main header and the second service header is associated with a flow between a logical unit and a UE; and output one or more messages, which include the first service data unit and the second service data unit, where the first service header and the second service header are different from each other.

[0035] Some embodiments of the methods, apparatus, and non-temporary computer-readable media described herein may further include operations, features, means, or instructions for establishing a data radio bearer with a UE, one or more messages which may be output by a network entity and may be based on establishing a data radio bearer with a UE.

[0036] Some embodiments of the methods, apparatus, and non-temporary computer-readable media described herein may further include operations, features, means, or instructions for establishing a network entity and a data radio bearer, one or more messages which may be output by the UE and based on establishing a network entity and a data radio bearer.

[0037] Some embodiments of the methods, apparatus, and non-temporary computer-readable media described herein further include operations, features, means, or instructions for obtaining a first message, which includes a first packet, a first main header, and a first service header, and modifying the first service header based on the first message, wherein a first service data unit can be generated based on the modified first service header.

[0038] Some embodiments of the methods, apparatus, and non-temporary computer-readable media described herein may further include operations, features, means, or instructions that modify a first service header, including updating a timestamp.

[0039] Some embodiments of the methods, apparatus, and non-temporary computer-readable media described herein may further include operations, features, means, or instructions for obtaining a first message comprising a first packet, a first main header, a first service header, and a third service header associated with a second service, and for removing the third service header in relation to the generation of the first service data unit such that the first service data unit does not include the third service header.

[0040] Some embodiments of the methods, apparatus, and non-temporary computer-readable media described herein may further include operations, features, means, or instructions for obtaining a first message comprising a first packet, a first main header, and a first service header, and adding a third service header in relation to the generation of a first service data unit such that the first service data unit includes a third service header, wherein the first message does not include a third service header.

[0041] In some embodiments of the methods, apparatus, and non-temporary computer-readable media described herein, the first service header, the second service header, or both, include instructions.

[0042] In some embodiments of the methods, apparatus, and non-temporary computer-readable media described herein, instructions may indicate that upon receipt of one or more messages, an acknowledgment should be sent; packets associated with one or more messages should be sorted according to the arrangement indicated by the instruction; packets associated with one or more messages should be discarded after a threshold time; packets associated with one or more messages should be timestamped; or any combination thereof.

[0043] In some embodiments of the methods, apparatus, and non-temporary computer-readable media described herein, the first service header includes a sorting timer, a sorting domain, an instruction to discard the first packet after the sorting timer has expired, an instruction to send acknowledgment feedback for the first packet, or any combination thereof.

[0044] In some embodiments of the methods, apparatus, and non-temporary computer-readable media described herein, the first main header and the second main header each include data control flags, header length, sequence number, information associated with extended fields, or any combination thereof.

[0045] A method for wireless communication is described. The method may include communicating a first message, which includes a first service data unit associated with a radio link control layer; deriving from the first service data unit a first packet, a first main header relating to the first packet, which is associated with a first layer above the radio link control layer, and a first service header relating to the first packet, which is associated with a service provided by one or more network entities in the network, wherein each of the first main header and the first service header is associated with a flow between a logical unit and a UE; generating a second service data unit, which is associated with a radio link control layer, and includes a second packet, a second main header, and a second service header relating to a service, wherein each of the second main header and the second service header is associated with a flow between a logical unit and a UE, and the second service header is based on the first service header and the second service header is different from the first service header; and communicating a second message, which includes the second service data unit.

[0046] A device is described. This device comprises one or more processors and one or more memories coupled to those one or more processors, which store processor executable code, and when the processor executable code is executed by one or more processors, causes a first UE to communicate a first message, which includes a first service data unit associated with the radio link control layer, and from the first service data unit, a first packet, a first main header relating to the first packet, which is associated with a first layer above the radio link control layer, and a first service relating to the first packet, which is associated with a service provided by one or more network entities in the network. It may include one or more memories that derive a service header and generate a second service data unit which includes a second packet, a second main header and a second service header associated with a service, each of which is associated with a flow between a logical unit and a UE, and is associated with the radio link control layer, and each of which is associated with a flow between a logical unit and a UE, and is configured to communicate a second message which includes a second service data unit which is based on the first service header and which is different from the first service header.

[0047] Another device is described. This device may include means for communicating a first message, which includes a first service data unit associated with a radio link control layer; means for deriving from the first service data unit a first packet, a first main header relating to the first packet, which is associated with a first layer above the radio link control layer, and a first service header relating to the first packet, which is associated with a service provided by one or more network entities in the network, wherein each of the first main header and the first service header is associated with a flow between a logical unit and a UE; means for generating a second service data unit, which is associated with a radio link control layer, and includes a second packet, a second main header and a second service header associated with a service, wherein each of the second main header and the second service header is associated with a flow between a logical unit and a UE, and the second service header is based on the first service header and the second service header is different from the first service header; and means for communicating a second message, which includes the second service data unit.

[0048] A non-temporary, computer-readable medium that stores codes for wireless communication by a device is described. This code may include instructions executable by one or more processors to cause a device to communicate a first message, which includes a first service data unit associated with a radio link control layer; from the first service data unit, a first packet, a first main header relating to the first packet, which is associated with a first layer above the radio link control layer, and a first service header relating to the first packet, which is associated with a service provided by one or more network entities in the network; each of the first main header and the first service header is associated with a flow between a logical unit and a UE, and generates a second service data unit, which includes a second packet, a second main header, and a second service header relating to a service; each of the second main header and the second service header is associated with a flow between a logical unit and a UE, and is associated with a radio link control layer; each of the second main header and the second service header is associated with a flow between a logical unit and a UE, and communicates a second message, which includes a second service data unit, the second service header being based on the first service header and the second service header being different from the first service header.

[0049] Some embodiments of the methods, apparatus, and non-temporary computer-readable media described herein may further include operations, features, means, or instructions for establishing a data radio bearer with a UE, wherein a first message may be communicated, and a second message may be output by a network entity, based on establishing a data radio bearer with a UE.

[0050] Some embodiments of the methods, apparatus, and non-temporary computer-readable media described herein may further include operations, features, means, or instructions for establishing a network entity and a data radio bearer, wherein a first message may be communicated and a second message may be output by the UE, based on establishing a network entity and a data radio bearer.

[0051] In some embodiments of the methods, apparatus, and non-temporary computer-readable media described herein, a first service header includes instructions, and the methods, apparatus, and non-temporary computer-readable media may include further operations, features, means, or instructions that perform the instructions, and the generation of a second service data unit may be based on the instructions.

[0052] In some embodiments of the methods, apparatus, and non-temporary computer-readable media described herein, the first service header includes information about the first packet, a sorting timer, a sorting domain, an instruction to discard the first packet after the sorting timer has expired, an instruction to send acknowledgment feedback for the first packet, or any combination thereof.

[0053] In some embodiments of the methods, apparatus, and non-temporary computer-readable media described herein, the first main header and the second main header each include data control flags, header length, sequence number, information associated with extended fields, or any combination thereof. [Brief explanation of the drawing]

[0054] [Figure 1] One embodiment of a wireless communication system supporting a user-plane programmable layer for wireless communication, according to one or more aspects of this disclosure, is shown. [Figure 2A] This disclosure provides an embodiment of a wireless communication system that supports a user-plane programmable layer for wireless communication, according to one or more aspects of this disclosure. [Figure 2B] This disclosure provides an embodiment of a wireless communication system that supports a user-plane programmable layer for wireless communication, according to one or more aspects of this disclosure. [Figure 2C] This disclosure provides an embodiment of a wireless communication system that supports a user-plane programmable layer for wireless communication, according to one or more aspects of this disclosure. [Figure 3A] One or more embodiments of the present disclosure illustrate an example of a higher-plane architecture supporting a user-plane programmable layer for wireless communication. [Figure 3B] One or more embodiments of the present disclosure illustrate an example of a higher-plane architecture supporting a user-plane programmable layer for wireless communication. [Figure 4A] This disclosure provides an embodiment of a wireless communication system that supports a user-plane programmable layer for wireless communication, according to one or more aspects of this disclosure. [Figure 4B] This disclosure provides an embodiment of a wireless communication system that supports a user-plane programmable layer for wireless communication, according to one or more aspects of this disclosure. [Figure 5] One or more embodiments of the present disclosure are shown, which illustrate an embodiment of a User Plane Adaptation Protocol (UPAP) Protocol Data Unit (PDU) supporting a user plane programmable layer for wireless communication. [Figure 6A] An embodiment of a UPAP header supporting a user-plane programmable layer for wireless communication, according to one or more aspects of this disclosure, is shown. [Figure 6B] An embodiment of a UPAP header supporting a user-plane programmable layer for wireless communication, according to one or more aspects of this disclosure, is shown. [Figure 6C]An embodiment of a UPAP header supporting a user-plane programmable layer for wireless communication, according to one or more aspects of this disclosure, is shown. [Figure 7A] One or more embodiments of this disclosure illustrate an example of a layer architecture supporting a user-plane programmable layer for wireless communication. [Figure 7B] One or more embodiments of this disclosure illustrate an example of a layer architecture supporting a user-plane programmable layer for wireless communication. [Figure 7C] One or more embodiments of this disclosure illustrate an example of a layer architecture supporting a user-plane programmable layer for wireless communication. [Figure 7D] One or more embodiments of this disclosure illustrate an example of a layer architecture supporting a user-plane programmable layer for wireless communication. [Figure 8] One embodiment of a process flow supporting a user-plane programmable layer for wireless communication, according to one or more aspects of this disclosure, is shown. [Figure 9] One embodiment of a service header timestamping scheme supporting a user-plane programmable layer for wireless communication, according to one or more aspects of this disclosure, is shown. [Figure 10] One embodiment of a reordering scheme supporting a user-plane programmable layer for wireless communication, according to one or more aspects of the present disclosure, is shown. [Figure 11] One embodiment of a layer architecture supporting a user-plane programmable layer for wireless communication, according to one or more aspects of this disclosure, is shown. [Figure 12] One embodiment of a process flow supporting a user-plane programmable layer for wireless communication, according to one or more aspects of this disclosure, is shown. [Figure 13]One embodiment of a user plane architecture supporting a user plane programmable layer for wireless communication, according to one or more aspects of this disclosure, is shown. [Figure 14] One embodiment of a layer architecture supporting a user-plane programmable layer for wireless communication, according to one or more aspects of this disclosure, is shown. [Figure 15] One embodiment of a process flow supporting a user-plane programmable layer for wireless communication, according to one or more aspects of this disclosure, is shown. [Figure 16] One embodiment of a process flow supporting a user-plane programmable layer for wireless communication, according to one or more aspects of this disclosure, is shown. [Figure 17] One embodiment of a process flow supporting a user-plane programmable layer for wireless communication, according to one or more aspects of this disclosure, is shown. [Figure 18] One embodiment of a process flow supporting a user-plane programmable layer for wireless communication, according to one or more aspects of this disclosure, is shown. [Figure 19] One embodiment of a process flow supporting a user-plane programmable layer for wireless communication, according to one or more aspects of this disclosure, is shown. [Figure 20] A block diagram of a device supporting a user-plane programmable layer for wireless communication, according to one or more aspects of this disclosure, is shown. [Figure 21] A block diagram of a device supporting a user-plane programmable layer for wireless communication, according to one or more aspects of this disclosure, is shown. [Figure 22] A block diagram of a communications manager supporting a user-plane programmable layer for wireless communication, according to one or more aspects of this disclosure, is shown. [Figure 23] The diagram shows a system including a device that supports a user-plane programmable layer for wireless communication, according to one or more aspects of this disclosure. [Figure 24] A block diagram of a device supporting a user-plane programmable layer for wireless communication, according to one or more aspects of this disclosure, is shown. [Figure 25] A block diagram of a device supporting a user-plane programmable layer for wireless communication, according to one or more aspects of this disclosure, is shown. [Figure 26] A block diagram of a communications manager supporting a user-plane programmable layer for wireless communication, according to one or more aspects of this disclosure, is shown. [Figure 27] The diagram shows a system including a device that supports a user-plane programmable layer for wireless communication, according to one or more aspects of this disclosure. [Figure 28] A flowchart illustrating a method for supporting a user-plane programmable layer for wireless communication according to one or more aspects of this disclosure is shown. [Figure 29] A flowchart illustrating a method for supporting a user-plane programmable layer for wireless communication according to one or more aspects of this disclosure is shown. [Figure 30] A flowchart illustrating a method for supporting a user-plane programmable layer for wireless communication according to one or more aspects of this disclosure is shown. [Figure 31] A flowchart illustrating a method for supporting a user-plane programmable layer for wireless communication according to one or more aspects of this disclosure is shown. [Figure 32] A flowchart illustrating a method for supporting a user-plane programmable layer for wireless communication according to one or more aspects of this disclosure is shown. [Modes for carrying out the invention]

[0055] In some embodiments, the network may include one or more logical units (e.g., a User Plane Function (UPF), a central unit (CU), and a distributed unit (DU)). A CU can be configured to communicate with the UPF and DU, and a DU can be configured to communicate with user equipment (UEs), other DUs, or both. The UPF can be configured to communicate with an external network for user traffic (e.g., data) and with the CU for network layer traffic (e.g., Internet Protocol (IP) packets). The CU may include a service data adaptation protocol (SDAP) layer entity that performs Quality of Service (QoS) flow processing. For example, an SDAP can map QoS flows associated with network layer traffic to a data radio bearer (DRB) and insert a header on each packet of network layer traffic. A flow may refer to the path between components associated with a data session (e.g., between a data network and a UE), and a data session may refer to the logical connection between a UE and a UPF or logical unit associated with a service. A data radio bearer may refer to a channel for the transfer of user data between a UE and a network entity. In some embodiments, an SDAP layer entity may perform flow-specific QoS processing. For example, each packet of network layer traffic (e.g., each IP packet) associated with the same QoS may have the same SDAP header. Having the same SDAP header can result in a lack of programmability and service adaptability.Furthermore, two packets associated with different deployments (for example, a first packet associated with an Internet of Things (IoT) deployment and a second packet associated with an extended reality (XR) deployment) may have the same SDAP header with the same fields (for example, the format of the SDAP header may be statically configured for any of several deployments). For example, both SDAP headers may have data / control fields and / or reserved fields. However, some information in the SDAP header used for one deployment may not be used for another. Therefore, the SDAP header may have unnecessary overhead for at least some deployments.

[0056] This disclosure describes a technology that can enable improved programmability and service adaptability and / or reduce at least some deployment overhead compared to other technologies. For example, a network entity (e.g., DU) may include radio layer entities, including User Plane Adaptive Protocol (UPAP) layer entities, radio link control (RLC) layer entities, medium access control (MAC) layer entities, and physical (PHY) layer entities. The UPAP layer entities can replace one or more functionalities of the SDAP layer entities and / or packet data convergence protocol (PDCP) layer entities of the CU, and the CU is configured to provide packets between the network entity and a logical unit (e.g., UPF). By replacing one or more of these functionalities and utilizing UPAP, the network entity may be able to communicate directly with the logical unit (e.g., directly with the UPF without going through the CU). Furthermore, UPAP layer entities may possess functionality that offers improved flexibility compared to SDAP layer entities and PDCP layer entities.

[0057] For example, some of the functionalities performed by UPAP layer entities may include performing QoS processing and inserting headers onto network layer traffic packets, such as a main header (common to multiple deployments and / or multiple packets, e.g., IoT and XR), and optionally one or more service headers (e.g., headers unique between deployments and / or between packets). For example, an IP packet associated with IoT may not have a service header inserted, while an IP packet associated with XR may. Therefore, the overhead associated with UPAP headers for IP packets associated with IoT can be reduced compared to XR. Furthermore, because service headers can differ between packets, those service headers may include unique fields, unique values ​​within the same field, executable instructions, or any combination thereof, which may allow different packets of network layer traffic to be processed in different ways (e.g., by any of the radio layer entities in the network entity).

[0058] In some embodiments, having a UPAP layer in a network entity (e.g., a DU) may allow a logical unit associated with a service to interact more directly with the radio layer (e.g., UPAP, RLC, MAC, PHY). A service may refer to an operation that an external network (e.g., an external network different from the network containing the network entity) can perform with the assistance of the UE and / or the network entity. In some embodiments, a logical unit associated with a service may use a service interface to program the network entity to perform the function. For example, the logical unit may send instructions to the network entity for performing a radio function. In some embodiments, these instructions may refer to executable code, a set of rules, parameter values, or any combination thereof that a wireless device can use to control its operation. A radio function can be defined as a function performed by a radio layer entity (e.g., a UPAP layer entity, an RLC layer entity, a MAC layer entity, or a PHY layer entity). Therefore, using the UPAP layer may enable a wider range of functionality that a network entity can perform.

[0059] In some embodiments, a logical unit (e.g., a UPF) may include some or all of the functionality of the UPAP layer. For example, a logical unit may include UPAP layer entities, in which case network entities may not include UPAP layer entities. Alternatively, a logical unit may include high UPAP layer entities, and network entities may include low UPAP layer entities, where high UPAP layer entities can perform tasks such as header compression and encryption, and low UPAP layer entities can be used to perform operations on high UPAP headers, such as correcting, modifying, or deleting high UPAP headers. In some embodiments, low UPAP layer entities can be programmed through an inter-UPAP interface between the logical unit and the network entity.

[0060] The aspects of this disclosure are first described in the context of wireless communication systems. Additional aspects of this disclosure are described in the context of upper-plane architecture, UPAP protocol data units (PDUs), UPAP headers, layer architecture, process flow, service header timestamping schemes, and sorting schemes. The aspects of this disclosure are further illustrated and described with reference to apparatus diagrams, system diagrams, and flowcharts relating to user-plane programmable layers for wireless communication.

[0061] Figure 1 shows one embodiment of a wireless communication system 100 supporting a user-plane programmable layer for wireless communication, according to one or more aspects of the present disclosure. 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 embodiments, the wireless communication system 100 may be a network operating according to an LTE network, an LTE-A network, an LTE-A Pro network, an NR network, or other systems and wireless technologies, including future systems and wireless technologies not expressly mentioned herein.

[0062] The network entity 105 can be distributed across a geographical area to form a wireless communication system 100 and may include devices of different forms or with different capabilities. In various embodiments, the network entity 105 may be referred to, among many technical terms, as a network element, mobility element, radio access network (RAN) node, or network equipment. In some embodiments, the network entity 105 and the UE 115 can communicate wirelessly via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, the network entity 105 can support a coverage area 110 (e.g., a geographical coverage area) in which the UE 115 and the network entity 105 can establish one or more communication links 125. The coverage area 110 can be an embodiment of a geographical area in which the network entity 105 and the UE 115 can support the communication of signals according to one or more radio access technologies (RATs).

[0063] The UE115 can be distributed across the entire coverage area 110 of the wireless communication system 100, and each UE115 can be fixed, mobile, or both at different times. The UE115 can be different forms of devices or devices with different capabilities. Several exemplary UE115 are shown in Figure 1. The UE115 described herein may be capable of supporting communication with various types of devices, such as other UE115 or network entities 105, as shown in Figure 1.

[0064] As described herein, a node of the wireless communication system 100, which may be referred to as a network node or wireless node, can be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, a node can be a UE 115. In another embodiment, a node can also be a network entity 105. In another embodiment, a first node can be configured to communicate with a second or third node. In one aspect of this embodiment, the first node can be a UE 115, the second node can be a network entity 105, and the third node can be a UE 115. In another aspect of this embodiment, the first node can be a UE 115, the second node can be a network entity 105, and the third node can be a network entity 105. In yet another embodiment of this embodiment, the first node, the second node, and the third node may differ from those of this embodiment. Similarly, references to UE115, network entity 105, apparatus, devices, computing systems, etc. may include disclosure that UE115, network entity 105, apparatus, devices, computing systems, etc. are nodes. For example, a disclosure that UE115 is configured to receive information from network entity 105 also discloses that the first node is configured to receive information from the second node.

[0065] In some embodiments, network entities 105 can communicate with the core network 130, communicate with each other, or communicate with both. For example, network entities 105 can 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 embodiments, network entities 105 can communicate with each other via the backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols) either directly (e.g., directly between network entities 105) or indirectly (e.g., via the core network 130). In some embodiments, network entities 105 can communicate with each other via a midhaul communication link 162 (e.g., according to a midhaul interface protocol), or via a fronthaul communication link 168 (e.g., according to a fronthaul interface protocol), or via any combination thereof. The backhaul communication link 120, the midhaul communication link 162, or the fronthaul communication link 168 may, in many embodiments or various combinations thereof, be one or more wired links (e.g., electrical links, fiber optic links), one or more wireless links (e.g., wireless links, wireless optical links), or may include such links. The UE 115 can communicate with the core network 130 via the communication link 155.

[0066] One or more of the network entities 105 described herein may include or be referred to as base station 140 (e.g., base transceiver station, radio base station, NR base station, access point, radio transceiver, node B, enode B (eNodeB, eNB), next-generation node B or giganode B (both sometimes referred to as gNB), 5G NB, next-generation eNB (next-generation eNB, ng-eNB), home node B, home enode B, or other preferred terminology). In some embodiments, the network entity 105 (e.g., base station 140) can be implemented in an aggregated (e.g., monolithic, standalone) base station architecture, which can be configured to utilize a protocol stack that is physically or logically integrated within a single network entity 105 (e.g., a single RAN node such as base station 140).

[0067] In some embodiments, the network entity 105 can be implemented in a decoupled architecture (e.g., a decoupled base station architecture, a decoupled RAN architecture) that can be configured to utilize a protocol stack that is physically or logically distributed among two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration supported by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, network entity 105 may include one or more of the following: CU160, DU165, radio unit (RU)170, RAN Intelligent Controller (RIC)175 (e.g., Near-RT RIC, Non-Real Time RIC), Service Management and Orchestration (SMO)180 system, or any combination thereof. RU170 may also be referred to as a radio head, smart radio head, remote radio head (RRH), remote radio unit (RRU), or transmission reception point (TRP). In a separate RAN architecture, one or more components of network entity 105 may be co-located, or one or more components of network entity 105 may be located in distributed locations (e.g., separate physical locations).In some embodiments, one or more network entities 105 of a separate RAN architecture can be implemented as virtual units (e.g., virtual CUs (VCUs), virtual DUs (VDUs), virtual RUs (VRUs)).

[0068] The functional division between CU160, DU165, and RU170 is flexible, and different functionalities can be supported depending on which function (e.g., network layer function, protocol layer function, baseband function, RF function, and any combination thereof) is performed in CU160, DU165, or RU170. For example, a functional division of the protocol stack may be adopted between CU160 and DU165, so that CU160 can support one or more layers of the protocol stack, and DU165 can support one or more different layers of the protocol stack. In some embodiments, CU160 can host higher protocol layer functionalities (e.g., layer 3 (L3), layer 2 (L2)) and signaling (e.g., Radio Resource Control (RRC), SDAP, PDCP). A CU160 can connect to one or more DU165s or RU170s, each of which can host lower protocol layers such as Layer 1 (L1) (e.g., PHY layer) or L2 (e.g., RLC layer, MAC layer) functionality and signaling, each of which can be controlled at least partially by the CU160. Alternatively, a functional partition of the protocol stack may be employed between the DU165 and RU170, so that the DU165 can support one or more layers of the protocol stack, and the RU170 can support one or more different layers of the protocol stack. The DU165 can support one or more different cells (e.g., via one or more RU170s).In some cases, the functional division between CU160 and DU165, or between DU165 and RU170, can be within the protocol layer (for example, some functions related to the protocol layer can be performed by one of CU160, DU165, or RU170, while other functions of the protocol layer can be performed by a different one of CU160, DU165, or RU170). CU160 can be further functionally divided into CU control plane (CU-CP) functions and CU user plane (CU-UP) functions. CU160 can be connected to one or more DU165s via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and DU165s can be connected to one or more RU170s via fronthaul communication links 168 (e.g., open fronthaul (FH) interfaces). In some embodiments, a midhaul communication link 162 or a fronthaul communication link 168 can be implemented according to an interface (e.g., a channel) between layers of the protocol stack, supported by a corresponding network entity 105 communicating over such a communication link.

[0069] In a wireless communication system (e.g., wireless communication system 100), the infrastructure and spectral resources for radio access can provide an IAB network architecture (e.g., to a core network 130) by supporting wireless backhaul link capabilities to complement wired backhaul connections. In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) can 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 DU 165 or one or more RU 170 can be partially controlled by one or more CU 160 associated with a donor network entity 105 (e.g., donor base station 140). One or more donor network entities 105 (e.g., IAB donors) can communicate with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access links and backhaul links (e.g., backhaul communication link 120). IAB node 104 may include an IAB mobile terminal (IAB mobile termination, IAB-MT) controlled (e.g., scheduled) by the DU165 of the coupled IAB donor. The IAB-MT may include a separate set of antennas for relaying communications with UE115, or it may share the same antennas of IAB node 104 (e.g., RU170) used for access to IAB node 104 via DU165 (e.g., a virtual IAB-MT (referred to as vIAB-MT)). In some embodiments, IAB node 104 may include a DU165 that supports communication links with additional entities (e.g., IAB node 104, UE115) in a relay chain or relay configuration of the access network (e.g., downstream).In such cases, one or more components of the isolated RAN architecture (for example, one or more IAB nodes 104, or components of IAB nodes 104) can be configured to operate in accordance with the techniques described herein.

[0070] For example, an access network (AN) or RAN may include communication between an access node (e.g., an IAB donor), an IAB node 104, and one or more UEs 115. The IAB donor can facilitate the connection between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, an IAB donor may refer to a RAN node having a wired or wireless connection to the core network 130. The IAB donor may include a CU 160 and at least one DU 165 (e.g., and RU 170), in which case the CU 160 can communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB donor and IAB node 104 can communicate via the F1 interface according to a protocol that defines signaling messages (e.g., the F1 AP protocol). Furthermore, or alternatively, the CU160 can communicate with the core network via an interface that may be an example of a backhaul link, and can communicate with other CU160s (e.g., CU160s associated with alternative IAB donors) via an Xn-C interface that may also be an example of a backhaul link.

[0071] IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access to UE 115, wireless self-backhaul capability). DU 165 may function as a distributed scheduling node directed to child nodes associated with IAB node 104, and IAB-MT may function as a scheduled node directed to a parent node associated with IAB node 104. That is, an IAB donor may be referred to as a parent node that communicates with one or more child nodes (e.g., an IAB donor can relay transmissions about the UE through one or more other IAB nodes 104). Furthermore, or alternatively, IAB node 104 may also be referred to as a parent or child node to other IAB nodes 104, depending on the relay chain or relay configuration of the AN. Therefore, the IAB-MT entity of IAB node 104 can provide a Uu interface for child IAB node 104 to receive signaling from parent IAB node 104, and the DU interface (e.g., DU165) can provide a Uu interface for parent IAB node 104 to signal to child IAB node 104 or UE115.

[0072] For example, IAB node 104 may be referred to as a parent node that supports communication with child IAB nodes, or as a child IAB node associated with an IAB donor, or both. An IAB donor may include a CU 160 having a wired or wireless connection (e.g., a backhaul communication link 120) to the core network 130 and may function as a parent node to IAB node 104. For example, the DU 165 of the IAB donor may relay transmissions to UE 115 via IAB node 104, or directly signal transmissions to UE 115, or both. The CU 160 of the IAB donor can signal the establishment of a communication link to IAB node 104 via the F1 interface, and IAB node 104 can schedule transmissions (e.g., transmissions to UE 115 relayed from the IAB donor) via the DU 165. In other words, data can be relayed to and from IAB node 104 via signaling through the NR Uu interface to the MT of IAB node 104. Communication with IAB node 104 can be scheduled by the DU165 of the IAB donor, and communication with IAB node 104 can also be scheduled by the DU165 of IAB node 104.

[0073] When the techniques described herein are applied in the context of a separate RAN architecture, one or more components of the separate RAN architecture can be configured to support a user-plane programmable layer for wireless communication, as described herein. For example, some operations described as being performed by UE115 or network entity 105 (e.g., base station 140) can be performed, or alternatively, by one or more components of the separate RAN architecture (e.g., IAB node 104, DU165, CU160, RU170, RIC175, SMO180).

[0074] UE115 may include, or may be referred to as, a mobile device, wireless device, remote device, handheld device, or subscriber device, or any other preferred term; “device” may also be referred to as, in many examples, a unit, station, terminal, or client. UE115 may also include, or may be referred to as, a personal electronic device such as a cellular phone, personal digital assistant (PDA), tablet computer, laptop computer, or personal computer. In some embodiments, UE115 may include, or may be referred to as, a wireless local loop (WLL) station, IoT device, Internet of Everything (IoE) device, or machine type communications (MTC) device, which can be implemented in various items such as home appliances, vehicles, meters, and so on.

[0075] The UE115 described herein may also function as a repeater, as shown in Figure 1, and may be capable of communicating with various types of devices, including, among many other examples, network entities 105 and network equipment, such as macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations.

[0076] UE 115 and network entity 105 can communicate wirelessly with each other over one or more communication links 125 (e.g., access links) using resources associated with one or more carriers. The term “carrier” may refer to a set of RF spectral resources having a defined physical layer structure for supporting communication links 125. For example, a carrier used with respect to communication link 125 may include a portion of the RF spectral band (e.g., a bandwidth part (BWP)) operating according to one or more physical layer channels with respect to a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquired signaling (e.g., synchronization signals, system information), control signaling that coordinates the operation of the carrier, user data, or other signaling. Wireless communication system 100 can support communication with UE 115 using carrier aggregation or multi-carrier operation. UE 115 may consist of multiple downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration. Carrier aggregation can be used with both frequency division duplexing (FDD) component carriers and time division duplexing (TDD) component carriers. Communication between network entity 105 and other devices may refer to communication between those devices and any part of network entity 105 (e.g., entity, sub-entity). For example, when referring to network entity 105, the terms “transmitting,” “receiving,” or “communicating” may refer to any part of network entity 105 in the RAN (e.g., base station 140, CU160, DU165, RU170) communicating with another device (e.g., directly or via one or more other network entities 105).

[0077] In some embodiments, such as in carrier aggregation configurations, a carrier may also have acquisition signaling or control signaling that coordinates the operation of other carriers. A carrier can be associated with a frequency channel (e.g., an evolved universal mobile telecommunication system terrestrial radio access (E-UTRA) absolute RF channel number (EARFCN)) and can be identified according to a channel raster for detection by the UE115. A carrier can operate in standalone mode, in which case initial acquisition and connection can be performed by the UE115 via that carrier, or a carrier can operate in non-standalone mode, in which case the connection is fixed using a different carrier (e.g., the same radio access technology or a different radio access technology).

[0078] The communication link 125 shown in the wireless communication system 100 may include, among many transmission configurations, a downlink transmission from the network entity 105 to the UE 115 (e.g., a forward link transmission), an uplink transmission from the UE 115 to the network entity 105 (e.g., a reverse link transmission), or both. The carrier can carry downlink communication or uplink communication (e.g., in FDD mode), or can be configured to carry both downlink communication and uplink communication (e.g., in TDD mode).

[0079] A carrier can be associated with a specific bandwidth in the RF spectrum, and in some embodiments, the carrier bandwidth may be referred to as the "system bandwidth" of that carrier or wireless communication system 100. For example, the carrier bandwidth may be one of a set of bandwidths (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz (MHz)) with respect to the carrier of a particular radio access technology. Devices of the wireless communication system 100 (e.g., network entity 105, UE 115, or both) may have a hardware configuration that supports communication using a specific carrier bandwidth, or may be configurable to support communication using one of the carrier bandwidths in a set of carrier bandwidths. In some embodiments, the wireless communication system 100 may include network entity 105 or UE 115 that support simultaneous communication using carriers associated with multiple carrier bandwidths. In some embodiments, each UE 115 provided may be configured to operate using a portion (e.g., subband, BWP) or all of the carrier bandwidth.

[0080] The signal waveform transmitted over the carrier can be composed of multiple subcarriers (for example, using multi-carrier modulation (MCM) techniques such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM). In systems employing MCM techniques, a resource element may refer to the resources of one symbol period (e.g., duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely proportional. The amount of bits carried by each resource element may depend on the modulation scheme (e.g., modulation order, modulation coding rate, or both) so that a relatively large number of resource elements (e.g., within the transmission duration) and a relatively high-order modulation scheme can accommodate a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectral resources, temporal resources, and spatial resources (e.g., spatial layers, beams), and the use of multiple spatial resources can improve the data rate or data integrity for communication with the UE115.

[0081] One or more numerologies relating to a carrier can be supported, and the numerology may include a subcarrier spacing (Δf) and a cyclic prefix. A carrier can be divided into one or more BWPs having the same or different numerologies. In some embodiments, UE115 can consist of multiple BWPs. In some embodiments, a single BWP relating to a carrier can be activated at a given time, and communication relating to UE115 can be restricted to one or more active BWPs.

[0082] The time interval relating to network entity 105 or UE115 is, for example, T s = 1 / (Δf max ·N f) can refer to a sampling period of seconds, which can be expressed as a multiple of the basic time unit, in this case Δf max This can represent the supported subcarrier intervals, and N f This can represent the supported Discrete Fourier Transform (DFT) size. The time interval of the communication resources can be organized according to radio frames, each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a system frame number (SFN) (e.g., in the range of 0 to 1023).

[0083] Each frame may contain multiple subframes or slots that are sequentially numbered, and each subframe or slot may have the same duration. In some embodiments, a frame can be divided into subframes (e.g., in the time domain), and each subframe can be further divided into a certain number of slots. Alternatively, each frame may contain a variable number of slots, the number of slots may depend on the subcarrier interval. Each slot may contain a certain number of symbol periods (e.g., depending on the length of the cyclic prefix added to the beginning of each symbol period). In some wireless communication systems 100, a slot can be further divided into a number of minislots associated with one or more symbols. Each symbol period, excluding the cyclic prefix, may be divided into one or more (e.g., N) f It can be associated with the sampling period of (individual). The duration of the symbol period may depend on the subcarrier interval or the frequency band of operation.

[0084] A subframe, slot, minislot, or symbol can 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 embodiments, the TTI duration (e.g., the amount of symbol duration within the TTI) can be variable. Furthermore, or alternatively, the smallest scheduling unit of the wireless communication system 100 can be dynamically selected (e.g., in bursts of shortened TTIs, sTTIs).

[0085] With respect to carrier-based communications, physical channels can be multiplexed according to various techniques. For example, one or more of the following can be used to multiplex physical control channels and physical data channels with respect to signaling over the downlink carrier: time division multiplexing (TDM), frequency division multiplexing (FDM), or hybrid TDM-FDM. A control domain (e.g., a control resource set, CORESET) relating to a physical control channel can be defined by a set of symbol periods and can be extended over the system bandwidth or a subset of the system bandwidth of that carrier. One or more control domains (e.g., CORESETs) can be configured with respect to a set of UE115s. For example, one or more of the UE115s can monitor or explore control domains with respect to control information according to one or more search space sets, each search space set may contain one or more control channel candidates at one or more aggregation levels, configured in a cascaded manner. The aggregation level for control channel candidates may refer to the amount of control channel resources (e.g., control channel elements, CCEs) associated with encoded information for a control information format with a given payload size. The search space set may include a common search space set configured to send control information to multiple UE115s, and a UE-specific search space set for sending control information to a specific UE115.

[0086] The network entity 105 may provide communication coverage through one or more cells, such as macrocells, small cells, hotspots, or other types of cells, or any combination thereof. The term “cell” may refer to a logical communication entity used in relation to communication with the network entity 105 (e.g., using a carrier), and may be associated with an identifier for distinguishing adjacent cells (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), etc.). In some embodiments, a cell may also refer to a coverage area 110, or a portion of the coverage area 110 (e.g., a sector), on which its logical communication entity operates. Such cells may range from smaller areas (e.g., structures, subsets of structures) to larger areas, depending on various factors, such as the capabilities of the network entity 105. For example, among many other possibilities, a cell may be, or may include, a building, a subset of a building, or the external space between coverage areas 110, or the external space overlapping with coverage area 110.

[0087] Macrocells generally cover relatively large geographical areas (e.g., a radius of several kilometers) and can enable unrestricted access by UE115 subscribed to the services of the network provider supporting the macrocell. Small cells can be associated with lower-power network entities 105 (e.g., lower-power base stations 140) compared to macrocells, and small cells can operate using the same or different (e.g., unlicensed, unauthorized) frequency bands as macrocells. Small cells can provide unrestricted access to UE115 subscribed to the network provider's services, or they can provide restricted access to UE115 associated with the small cell (e.g., UE115 within a closed subscriber group (CSG), or UE115 associated with users in a home or office). A network entity 105 can support one or more cells and can also support communication through one or more of those cells using one or more component carriers.

[0088] In some embodiments, a carrier can support multiple cells, and different cells can be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB)) which can provide access to different types of devices.

[0089] The electromagnetic spectrum is often subdivided into various classes, bands, and channels based on frequency / wavelength. In 5G NR, two initial operating bands are identified as frequency range designations FR1 (410 MHz to 7.125 GHz) and FR2 (24.25 GHz to 52.6 GHz). It should be understood that although a portion of FR1 is higher than 6 GHz, FR1 is often referred to as the "sub-6 GHz" band (for compatibility) in various documents and papers. A similar nomenclature issue can arise with FR2, which is often referred to as the "millimeter wave" band (for compatibility) in documents and papers, even though FR2 is different from the extremely high frequency (EHF) band (30 GHz to 300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0090] The frequencies between FR1 and FR2 are often referred to as intermediate band frequencies. In recent 5G NR research, the operating bands related to these intermediate band frequencies are identified as frequency range designation FR3 (7.125GHz~24.25GHz). The frequency bands within the FR3 range can inherit the characteristics of FR1 and / or FR2, and therefore, the features of FR1 and / or FR2 can be effectively extended to the intermediate band frequencies. Furthermore, higher frequency bands are currently being considered to extend 5G NR operation beyond 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6GHz~71GHz), FR4 (52.6GHz~114.25GHz), and FR5 (114.25GHz~300GHz). Each of these higher frequency bands is within the EHF band range.

[0091] With the above aspects in mind, please understand that, unless otherwise specified, terms such as "sub-6GHz" may broadly refer to frequencies that may be less than 6GHz, frequencies that may be within the FR1 range, or frequencies that may include intermediate band frequencies. Furthermore, please understand that, unless otherwise specified, terms such as "millimeter wave" may broadly refer to frequencies that may include intermediate band frequencies, frequencies that may be within the FR2, FR4, FR4-a or FR4-1, and / or FR5 ranges, or frequencies that may be within the EHF band.

[0092] In some embodiments, network entities 105 (e.g., base stations 140, RU 170) can be mobile and therefore can provide communication coverage for a moving coverage area 110. In some embodiments, different coverage areas 110 associated with different technologies may overlap, but these different coverage areas 110 can be supported by the same network entity 105. In some other embodiments, overlapping coverage areas 110 associated with different technologies can also 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.

[0093] The wireless communication system 100 can support synchronous or asynchronous operation. In synchronous operation, network entities 105 (e.g., base stations 140) may have similar frame timings, and transmissions from different network entities 105 can be approximately synchronized in time. In asynchronous operation, network entities 105 may have different frame timings, and transmissions from different network entities 105 may not be synchronized in time in some embodiments. The techniques described herein can be used with respect to either synchronous or asynchronous operation.

[0094] Some UE115s, such as MTC devices or IoT devices, can be low-cost or low-complexity devices that can provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC may refer to data communication technology that enables devices to communicate with each other or with a network entity 105 (e.g., base station 140) without human intervention. In some embodiments, M2M communication or MTC may include communication from a device that incorporates sensors or meters for measuring or capturing information, relaying such information to a central server or application program that uses the information, or presenting the information to a human interacting with the application program. Some UE115s can be designed to collect information or to enable automated behavior of machines or other devices. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, vehicle management and tracking, remote security sensing, physical access control, and transaction-based business billing.

[0095] Some UE115s can be configured to employ power-saving operating modes, such as half-duplex communication (e.g., a mode that supports one-way communication via transmit or receive, but does not support transmit and receive simultaneously). In some embodiments, half-duplex communication can be performed at a reduced peak rate. Other power-saving techniques for the UE115 include entering a power-saving deep sleep mode when not engaged in active communication, operating using a limited bandwidth (e.g., according to narrowband communication), or a combination of these techniques. For example, some UE115s can be configured to operate using narrowband protocol types associated with a defined portion or range (e.g., a subcarrier or a set of resource blocks, RBs) within, within, or outside the carrier's protected band.

[0096] The wireless communication system 100 can be configured to support ultra-reliable low-latency communications, low-latency communications, or various combinations thereof. For example, the wireless communication system 100 can be configured to support ultra-reliable low-latency communications (URLLC). The UE 115 can be designed to support ultra-reliable, low-latency, or criticality functions. Ultra-reliable communications may include private or group communications and may be supported by one or more services such as push-to-talk, video, or data. Support for ultra-reliable and low-latency functions may include service prioritization, 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 in this specification.

[0097] In some embodiments, a UE 115 can be configured to support direct communication with other UEs 115 via a device-to-device (D2D) communication link 135 (for example, according to a peer-to-peer (P2P) protocol, a D2D protocol, or a sidelink protocol). In some embodiments, one or more UEs 115 in a group performing D2D communication may reside within the coverage area 110 of a network entity 105 (e.g., base station 140, RU 170), and the various modes of such D2D communication can be configured (e.g., scheduled) by the network entity 105. In some embodiments, one or more UEs 115 in such a group may reside outside the coverage area 110 of the network entity 105, or may be unable to receive or not configured to receive transmissions from the network entity 105. In some embodiments, a group of UE115s communicating via D2D communication can support a one-to-many (1:M) system, where each UE115 transmits to each of the other UE115s in the group. In some embodiments, a network entity 105 can facilitate the scheduling of resources related to D2D communication. In some other embodiments, D2D communication can be performed between UE115s without the involvement of the network entity 105.

[0098] In some systems, the D2D communication link 135 can be an embodiment of a communication channel, such as a side-link communication channel, between vehicles (e.g., UE115). In some embodiments, vehicles can communicate using vehicle-to-everything (V2X) communication, vehicle-to-vehicle (V2V) communication, or any combination thereof. Vehicles can signal information related to traffic conditions, signal scheduling, weather, safety, emergencies, or any other information related to the V2X system. In some embodiments, vehicles in a V2X system can communicate with roadside infrastructure such as roadside units, or with the network via one or more network nodes (e.g., network entity 105, base station 140, RU170) using vehicle-to-network (V2N) communication, or both.

[0099] The core network 130 can provide user authentication, access authorization, tracking, IP connectivity, and other access, routing, or mobility functions. The core network 130 can 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)) that manages 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 UPF) that routes packets or interconnects to external networks. The control plane entity can manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management, for UE 115 serviced by a network entity 105 (e.g., base station 140) associated with the core network 130. User IP packets can be forwarded via a user plane entity that may provide IP address assignment and other functions. The user plane entity can connect to an IP service 150 relating to one or more network operators. The IP service 150 may include access to the Internet, one or more intranets, an IP Multimedia Subsystem (IMS), or a packet-switched streaming service.

[0100] The wireless communication system 100 can operate using one or more frequency bands, which may range from 300 megahertz (MHz) to 300 gigahertz (GHz). The 300 MHz to 3 GHz range is known as the ultra-high frequency (UHF) range or decimeter band, as its wavelengths range from approximately 1 decimeter to 1 meter. UHF waves may be blocked or redirected by buildings and environmental features, sometimes referred to as clusters, but these waves can penetrate structures well enough for a macrocell to serve a UE 115 located indoors. Communication using UHF waves can be associated with smaller antennas and shorter distances (e.g., less than 100 kilometers) compared to communication using lower frequencies and longer waves in the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0101] The wireless communication system 100 can also operate using the super high frequency (SHF) region, which may be in the range of 3 GHz to 30 GHz, also known as the centimeter band, or using the extremely high frequency (EHF) region of the spectrum (e.g., 30 GHz to 300 GHz), also known as the millimeter band. In some embodiments, the wireless communication system 100 can support millimeter wave (mmW) communication between the UE 115 and the network entity 105 (e.g., base station 140, RU 170), and the EHF antenna of the corresponding device can be smaller and more densely spaced than the UHF antenna. In some embodiments, such technology can facilitate the use of an antenna array within the device. However, the propagation of EHF transmissions may be more attenuated and shorter in range than that of SFH or UHF transmissions. The technology disclosed herein can be employed across transmissions using one or more different frequency domains, and the specified applications of the bands across these frequency domains may vary by country or regulatory body.

[0102] The wireless communication system 100 can utilize both licensed and unlicensed RF spectrum bands. For example, the wireless communication system 100 can employ NR technologies that use unlicensed bands such as License Assisted Access (LAA), LTE-Unlicensed (LTE-U) radio access technology, or the 5GHz industrial, scientific, and medical (ISM) band. While operating using unlicensed RF spectrum bands, devices such as network entities 105 and UE115 can employ carrier sensing for collision detection and avoidance. In some embodiments, operation using unlicensed bands may be based on a carrier aggregation configuration (e.g., LAA) that works in conjunction with component carriers operating using licensed bands. Among many examples, operation using unlicensed spectrum may include downlink transmission, uplink transmission, P2P transmission, or D2D transmission.

[0103] A network entity 105 (e.g., base station 140, RU170) or UE 115 may be equipped with multiple antennas that may be used to employ technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of the network entity 105 or UE 115 may be located in one or more antenna arrays or antenna panels that can transmit or receive MIMO operation or beamforming. For example, one or more base station antennas or antenna arrays may be co-located in an antenna assembly such as an antenna tower. In some embodiments, the antennas or antenna arrays associated with the network entity 105 may be located in diverse geographical locations. The network entity 105 may include an antenna array having a set of rows and columns of antenna ports that the network entity 105 can use to support beamforming for communication with the UE 115. Similarly, the UE 115 may include one or more antenna arrays that can support various MIMO or beamforming operations. Furthermore, or alternatively, the antenna panel can support RF beamforming with respect to signals transmitted through the antenna port.

[0104] Network entities 105 or UE115 may use MIMO communication to leverage multipath signal propagation and improve spectral efficiency by transmitting or receiving multiple signals through different spatial layers. Such techniques may be referred to as spatial multiplexing. Multiple signals can be transmitted by a transmitting device, for example, through different antennas or different combinations of antennas. Similarly, multiple signals can be received by a receiving device, for example, through different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and can carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers can be associated with different antenna ports used for channel measurement and reporting. MIMO techniques include single-user MIMO (SU-MIMO), where multiple spatial layers are transmitted to the same receiving device, and multiple-user MIMO (MU-MIMO), where multiple spatial layers are transmitted to multiple devices.

[0105] Beamforming, sometimes referred to as spatial filtering, directional transmission, or directional reception, is a signal processing technique that can be used in a transmitting or receiving device (e.g., network entity 105, UE115) to shape or steer an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals communicated through the antenna elements of an antenna array such that some signals propagating along a particular orientation relative to the antenna array undergo constructive interference, while other signals undergo destructive interference. The modulation of signals communicated through antenna elements may include the transmitting or receiving device applying amplitude offset, phase offset, or both to the signals carried through the antenna elements associated with that device. The modulation associated with each antenna element can be defined by a beamforming weight set associated with a particular orientation (e.g., relative to the antenna array of the transmitting or receiving device, or to some other orientation).

[0106] The network entity 105 or UE 115 can use beam sweeping techniques as part of its beamforming operation. For example, the network entity 105 (e.g., base station 140, RU 170) can use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with the UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) can be transmitted multiple times by the network entity 105 along different directions. For example, the network entity 105 can transmit signals according to different beamforming weight sets associated with different transmission directions. Transmissions along different beam directions can be used to identify the beam direction for subsequent transmission or reception by the network entity 105 (e.g., by a transmitting device such as the network entity 105, or by a receiving device such as the UE 115).

[0107] Some signals, such as data signals associated with a specific receiving device, can be transmitted by a transmitting device (e.g., transmitting network entity 105, transmitting UE 115) along a single beam direction (e.g., the direction associated with the receiving device, such as receiving network entity 105 or receiving UE 115). In some embodiments, the beam direction associated with transmission along a single beam direction can be determined based on signals transmitted along one or more beam directions. For example, UE 115 can receive one or more signals transmitted by network entity 105 along different directions and can report to network entity 105 an indication of the signal received by UE 115 that has the highest or acceptable signal quality.

[0108] In some embodiments, transmission by a device (e.g., by network entity 105 or UE115) can be performed using multiple beam directions, and the device can use a combination of digital precoding or beamforming to generate a combined beam for transmission (e.g., from network entity 105 to UE115). UE115 can report feedback indicating precoding weights for one or more beam directions, which may correspond to a configured set of beams across the system bandwidth or one or more subbands. Network entity 105 can transmit reference signals (e.g., cell-specific reference signal (CRS), channel state information reference signal (CSI-RS)) which may or may not be precoded. UE115 can provide feedback on beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-panel type codebook, a linear combination type codebook, a port selection type codebook). While these techniques are described with reference to signals transmitted by a network entity 105 (e.g., base station 140, RU170) along one or more directions, UE115 may employ similar techniques for transmitting signals multiple times along different directions (e.g., to identify beam directions for subsequent transmission or reception by UE115) or for transmitting signals along a single direction (e.g., to transmit data to a receiving device).

[0109] A receiving device (e.g., UE115) can perform receiving operations according to multiple receiving configurations (e.g., directional listening) when receiving various signals from another receiving device (e.g., network entity 105), such as synchronization signals, reference signals, beam selection signals, or other control signals. For example, a receiving device can perform receiving according to multiple receiving directions by receiving through different antenna subarrays, by processing received signals according to different antenna subarrays, by receiving according to different sets of receive beamforming weights (e.g., different directional listening weights) applied to signals received by multiple antenna elements of an antenna array, or by processing received signals according to different sets of receive beamforming weights applied to signals received by multiple antenna elements of an antenna array, any of which may be referred to as “listening” according to different receiving configurations or receiving directions. In some embodiments, a receiving device can use a single receiving configuration to receive along a single beam direction (e.g., when receiving data signals). A single receiving configuration can be matched along a beam direction determined based on listening according to various receiving configuration directions (for example, the beam direction determined to have the highest signal strength, the highest signal-to-noise ratio (SNR), or acceptable signal quality based on listening according to multiple beam directions).

[0110] The wireless communication system 100 can be a packet-based network operating according to a layered protocol stack. In the user plane, communication at the bearer or PDCP layer can be IP-based. To communicate over logical channels, the RLC layer can perform packet segmentation and reassembly. The MAC layer can perform priority processing and multiplexing of logical channels to transport channels. The MAC layer may also implement error detection techniques, error correction techniques, or both to support retransmission to improve link efficiency. In the control plane, the RRC layer can provide establishment, configuration, and maintenance of RRC connections between the UE 115 and the network entity 105 or core network 130 supporting the wireless bearer for user plane data. The PHY layer can map transport channels to physical channels.

[0111] UE115 and network entity 105 can support data retransmission to increase the likelihood of successful data reception. Hybrid automatic repeat request (HARQ) feedback is one technique to increase the likelihood of correct data reception over a communication link (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using cyclic redundancy check, CRC), forward error correction (FEC), and retransmission (e.g., automatic repeat request, ARQ). HARQ can improve throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise conditions). In some embodiments, the device can support same-slot HARQ feedback, in which case the device can provide HARQ feedback within a given slot for data received via a previous symbol within that slot. In some other embodiments, the device can provide HARQ feedback in a subsequent slot or according to some other time interval.

[0112] The technologies described herein can be implemented via additional or alternative wireless devices, including IAB nodes 104, DU165, CU160, and radio units (RUs) 170, in addition to being implemented between UE115 and network entity 105, or as an alternative thereto. For example, in some implementations, the embodiments described herein can be implemented in the context of a separated RAN architecture (e.g., an open RAN architecture). In a separated architecture, the RAN can be divided into three functional areas corresponding to CU160, DU165, and RU170. The functional division between CU160, DU165, and RU170 is flexible, and therefore, a number of substitutions of various functionalities occur depending on which function (e.g., MAC function, baseband function, radio frequency function, and any combination thereof) is performed in CU160, DU165, and RU170. For example, a functional partitioning of the protocol stack may be employed between the DU165 and RU170, so that the DU165 can support one or more layers of the protocol stack, and the RU170 can support one or more different layers of the protocol stack.

[0113] In some wireless communication systems (e.g., wireless communication system 100), the infrastructure and spectral resources for NR access can provide an IAB network architecture by further supporting wireless backhaul link capabilities to complement wired backhaul connections. One or more network entities 105 may include CU160, DU165, and RU170 and may be referred to as a donor network entity 105 or IAB donor. One or more DU165 (e.g., and / or RU170) associated with a donor network entity 105 can be partially controlled by a CU160 associated with the donor network entity 105. One or more donor network entities 105 (e.g., IAB donor) can communicate with one or more additional network entities 105 (e.g., IAB node 104) via supported access links and backhaul links. An IAB node 104 can support mobile terminal (MT) functionality controlled and / or scheduled by the DU165 of the coupled IAB donor. Furthermore, the IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115, etc.) in the relay chain or relay configuration of the access network (e.g., downstream). In such cases, one or more components of the isolated RAN architecture (e.g., one or more IAB nodes 104, or components of IAB node 104) can be configured to operate according to the techniques described herein.

[0114] In some embodiments, the wireless communication system 100 may include a core network 130 (e.g., a next-generation core network (NGC)), one or more IAB donors, IAB nodes 104, and UE 115, where the IAB nodes 104 can be partially controlled by each other and / or by the IAB donors. The IAB donors and IAB nodes 104 may be examples of various forms of the network entity 105. The IAB donors and one or more IAB nodes 104 may be configured as some relay chain (e.g., or communicate according to some relay chain).

[0115] For example, the Access Network (AN) or RAN may refer to communication between an access node (e.g., an IAB donor), an IAB node 104, and one or more UEs 115. The IAB donor can facilitate the connection between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, the IAB donor may refer to a RAN node having a wired or wireless connection to the core network 130. The IAB donor may include a CU 160 and at least one DU 165 (e.g., and RU 170), and the CU 160 can communicate with the core network 130 via an NG interface (e.g., some backhaul link). The CU 160 can host Layer 3 (L3) functionality and signaling (e.g., RRC, Service Data Adaptive Protocol (SDAP), PDCP, etc.). At least one DU165 and / or RU170 can host lower layers, such as Layer 1 (L1) and Layer 2 (L2) functionality and signaling (e.g., RLC, MAC, PHY, etc.), each of which can be at least partially controlled by a CU160. A DU165 can support one or more different cells. The IAB donor and IAB node 104 can communicate via the F1 interface according to some protocol (e.g., the F1 AP protocol) that defines signaling messages. Furthermore, a CU160 can communicate with the core network via the NG interface (which may be an example of a backhaul link) and with other CU160s (e.g., CU160s associated with alternative IAB donors) via the Xn-C interface (which may be an example of a backhaul link).

[0116] IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access to UE 115, wireless self-backhaul capability, etc.). IAB node 104 may include DU 165 and MT. DU 165 may function as a distributed scheduling node toward child nodes associated with IAB node 104, and MT may function as a scheduled node toward a parent node associated with IAB node 104. That is, an IAB donor may be referred to as a parent node that communicates with one or more child nodes (e.g., an IAB donor may relay transmissions concerning UEs through one or more other IAB nodes 104). Furthermore, IAB node 104 may also be referred to as a parent or child node toward other IAB nodes 104, depending on the relay chain or relay configuration of the AN. Therefore, the MT entity of IAB node 104 (e.g., MT) can provide a Uu interface for child nodes to receive signaling from parent IAB node 104, and the DU interface (e.g., DU165) can provide a Uu interface for parent nodes to signal to child IAB node 104 or UE115.

[0117] For example, IAB node 104 may be referred to as a parent node associated with an IAB node, and a child node associated with an IAB donor. An IAB donor may include a CU160 having a wired (e.g., fiber optic) or wireless connection to the core network and may function as a parent node to IAB node 104. For example, the DU165 of the IAB donor may relay transmissions to UE115 via IAB node 104, or it may directly signal transmissions to UE115. The CU160 of the IAB donor can signal the establishment of a communication link to IAB node 104 via the F1 interface, and IAB node 104 can schedule transmissions (e.g., transmissions to UE115 relayed from the IAB donor) via the DU165. That is, data can be relayed to and from IAB node 104 via signaling to MT via the NR Uu interface. Communication with IAB node 104 can be scheduled by the IAB donor DU165, and communication with IAB node 104 can also be scheduled by the DU165 of IAB node 104.

[0118] When the techniques described herein are applied in the context of a separate RAN architecture, one or more components of the separate RAN architecture (e.g., one or more IAB nodes 104, or components of IAB nodes 104) can be configured to support techniques for long round-trip times in random access channel procedures, as described herein. For example, some operations described as being performed by UE 115 or network entity 105 can, or alternatively, be performed by components of the separate RAN architecture (e.g., IAB nodes, DUs, CUs, etc.).

[0119] As described herein, a node, which may be referred to as a node, network node, network entity, or wireless node, can be a base station (e.g., any base station as described herein), a UE (e.g., any UE as described herein), a network controller, apparatus, device, computing system, one or more components, and / or another suitable processing entity configured to perform any of the technologies described herein. For example, a network node can be a UE. In another embodiment, a network node can be a base station. In another embodiment, a first network node can be configured to communicate with a second or third network node. In one aspect of this embodiment, the first network node can be a UE, the second network node can be a base station, and the third network node can be a UE. In another aspect of this embodiment, the first network node can be a UE, the second network node can be a base station, and the third network node can be a base station. In yet another embodiment of this embodiment, the first network node, the second network node, and the third network node may differ from those embodiments. Similarly, references to UEs, base stations, equipment, devices, computing systems, etc. may include disclosure that the UEs, base stations, equipment, devices, computing systems, etc. are network nodes. For example, a disclosure that a UE is configured to receive information from a base station also discloses that the first network node is configured to receive information from a second network node. If a particular embodiment is extended in accordance with this disclosure without contradiction to this disclosure (for example, the fact that a UE is configured to receive information from a base station also discloses that the first network node is configured to receive information from a second network node), then a broader embodiment of a narrower embodiment can be interpreted in a broad, open-ended manner, albeit in a reverse manner.It is also disclosed that a UE is configured to receive information from a base station, and that a first network node is configured to receive information from a second network node. In the above example, the first network node may refer to a first UE, a first base station, a first apparatus, a first device, a first computing system, one or more first components, a first processing entity, etc., configured to receive information, and the second network node may refer to a second UE, a second base station, a second apparatus, a second device, a second computing system, one or more second components, a second processing entity, etc.

[0120] As described herein, the communication of information (e.g., arbitrary information, signals, etc.) may be described in various ways using different terminology. Disclosure of one communication term includes disclosure of other communication terms. For example, a first network node may be described as configured to transmit information to a second network node. In this example, without inconsistency with the present disclosure, the disclosure that a first network node is configured to transmit information to a second network node includes the disclosure that a first network node is configured to provide, transmit, output, communicate, or transmit information to a second network node. Similarly, in this example, without inconsistency with the present disclosure, the disclosure that a first network node is configured to transmit information to a second network node includes the disclosure that a second network node is configured to receive, acquire, or decode information provided, transmitted, output, communicated, or transmitted by a first network node.

[0121] In some embodiments, the network may include one or more logical units 190 (e.g., UPF191, CU160, DU165). The CU can be configured to communicate with the UPF and DU, and the DU can be configured to communicate with the UE115, other DUs, or both. The UPF191 can be configured to communicate with an external network for user traffic (e.g., data) and with the CU for network layer traffic (e.g., IP packets). The CU may include an SDAP layer entity that performs QoS flow processing. For example, the SDAP can map QoS flows associated with network layer traffic to data radio bearers and can insert headers on each packet of network layer traffic. In some embodiments, the SDAP layer entity may perform flow-specific QoS processing. For example, each packet of network layer traffic (e.g., each IP packet) associated with the same QoS may have the same SDAP header. Having the same SDAP header may result in a lack of programmability and service adaptability. Furthermore, two packets associated with different deployments (for example, a first packet associated with IoT and a second packet associated with XR deployment) may have SDAP headers with the same fields. However, some information in the SDAP header used for one deployment may not be used for another. Therefore, the SDAP header may have unnecessary overhead for at least some deployments.

[0122] This disclosure describes a technology that can enable improved programmability and service adaptability and / or a reduction in at least some deployment overhead compared to other technologies. For example, a network entity 105 (e.g., a network entity having a DU) may include a radio layer entity 182, which includes a UPAP layer entity, an RLC layer entity, a MAC layer entity, and a PHY layer entity. The UPAP layer entity can replace one or more functionalities of a CU, an SDAP layer entity, and / or a PDCP layer entity, which is configured to provide packets between the network entity and a logical unit 190 (e.g., a UPF 191). By replacing one or more of these functionalities and utilizing UPAP, the network entity may be able to communicate directly with the logical unit (e.g., directly with the UPF without going through the CU). Furthermore, the UPAP layer entity may have functionality that offers improved flexibility compared to the SDAP layer entity and the PDCP layer entity.

[0123] For example, some of the functionalities performed by UPAP layer entities may include performing QoS processing and inserting headers onto network layer traffic packets, such as a main header (common to multiple deployments and / or multiple packets, e.g., IoT and XR), and optionally one or more service headers (e.g., headers unique between deployments and / or between packets). For example, an IP packet associated with IoT may not have a service header inserted, while an IP packet associated with XR may. Therefore, the overhead associated with UPAP headers for IP packets associated with IoT can be reduced compared to XR. Furthermore, because service headers can differ between packets, those service headers may include unique fields, unique values ​​within the same field, executable instructions, or any combination thereof, which may allow different packets of network layer traffic to be processed in different ways (e.g., by any of the radio layer entities in the network entity).

[0124] In some embodiments, having a UPAP layer in the network entity 105 (e.g., DU) may allow the logical unit 190 associated with the service to interact more directly with the radio link layer (e.g., UPAP, RLC, MAC, PHY). For example, the logical unit 190 associated with the service can use the service interface to program the network entity 105 to perform a function (e.g., via link 195). In some cases, the logical unit 190 can send commands to the network entity 105 to perform a radio function. Therefore, using the UPAP layer may enable a wider range of functionality that the network entity 105 can perform.

[0125] In some embodiments, UPF191 may include some or all of the functionality of the UPAP layer. For example, UPF191 may include UPAP layer entities, in which case network entity 105 may not include UPAP layer entities. Alternatively, UPF191 may include high UPAP layer entities, and network entity 105 may include low UPAP layer entities, where high UPAP layer entities can perform tasks such as header compression and encryption, and low UPAP layer entities can be used to perform operations on high UPAP headers, such as correcting, modifying, or deleting high UPAP headers. In some embodiments, low UPAP layer entities can be programmed through an inter-UPAP interface between UPF191 and network entity 105.

[0126] The UE communication manager 101 and / or base station communication manager 102 generate a first service data unit which includes a first packet associated with a first radio link control layer, a first main header relating to the first packet and associated with a first layer above the radio link control layer, and a first service header relating to the first packet and associated with a service provided by one or more network entities in the network, where each of the first main header and the first service header is associated with a flow between the logical unit 190 and the UE 115, and the radio link A second service data unit is generated associated with the control layer, and the second service data unit includes a second packet, a second main header associated with the first layer, and a second service header for the second packet associated with the service, each of which is associated with the flow between the logical unit and the UE, and the first service header and the second service header are different from each other, and the output can be configured to include one or more messages, including the first service data unit and the second service data unit.

[0127] Furthermore, or alternatively, the UE communication manager 101 and / or base station communication manager 102 communicate a first message including a first service data unit associated with the radio link control layer, derive from the first service data unit a first packet, a first main header relating to the first packet associated with a first layer above the radio link control layer, and a first service header relating to the first packet associated with a service provided by one or more network entities in the network, and each of the first main header and the first service header The system can be configured to generate a second service data unit which is associated with the flow between the logical unit 190 and the UE 115, is associated with the radio link control layer, and includes a second packet, a second main header, and a second service header associated with the service, wherein each of the second main header and the second service header is associated with the flow between the logical unit 190 and the UE 115, the second service header is based on the first service header, the second service header is different from the first service header, and a second message which includes the second service data unit can be communicated.

[0128] The base station communication manager 102 can be configured to send a capability message to the logical unit 190 indicating that the base station 140 supports commands related to services associated with the radio layer for wireless communication with one or more UEs 115, establish a data session with the logical unit 190 associated with one of the one or more UEs 115 based on the transmission of the capability message, receive commands from the logical unit 190 to perform radio functions associated with services with the UE based on the data session, and execute those commands at the radio layer.

[0129] Furthermore, or alternatively, the base station communication manager 102 may be configured to send a capability message to the logical unit 190 indicating the services supported by the base station 140, establish a data session with the logical unit 190 associated with the flow between the logical unit 190 and the UE 115 based on the transmission of the capability message, establish a data radio bearer with the UE 115 associated with the flow based on the data session, receive a first message associated with the flow from the logical unit 190, including a first header associated with a first layer based on the data session with the logical unit 190, generate a radio link control service data unit including a second header associated with the first layer based on the first header and one or more radio functions of the base station 140, and send a second message including the radio link control service data unit via the data radio bearer.

[0130] The logical unit communication manager 103 can be configured to receive a capability message indicating that the network entity 105 supports instructions regarding services associated with the radio layer for wireless communication with the UE 115, establish a data session associated with the flow between the logical unit 190 and the UE 115, send a first message associated with the flow and including a main header, a service header associated with the first layer, an instruction that the service header should be processed by the network entity 105, and instructions to perform radio functions associated with the UE 115, and receive a second message associated with the flow and including a main header based on the first message.

[0131] Figures 2A to 2C show embodiments 200-a, 200-b, and 200-c of a wireless communication system supporting a user-programmable layer for wireless communication according to one or more aspects of the present disclosure. In some embodiments, wireless communication systems 200-a, 200-b, and 200-c may implement one or more aspects of wireless communication system 100. For example, network entities 105-a, 105-b, and 105-c may each be an embodiment of network entity 105 and / or DU165 as described with reference to Figure 1, and UE115-a, 115-b, and 115-c may each be an embodiment of UE115 as described with reference to Figure 1. In some embodiments, logic units 205-a, 205-b, and 205-c may each be an embodiment of network entity 105 as described with reference to Figure 1. In some embodiments, logic units 205-a, 205-b, and 205-c may each be an embodiment of logic unit 190 (e.g., UPF) as described with reference to Figure 1, and / or an embodiment of DU165 as described with reference to Figure 1.

[0132] In the wireless communication system 200-a, the logical unit 205-a can be configured to communicate with the network entity 105-a, and the network entity 105-a can be configured to communicate with the UE 115-a. Furthermore, the network entity 105-a can establish a UPAP with the UE 115-a. For example, the network entity 105-a may have a UPAP layer entity 210-b, and the UE 115-a may have a UPAP layer entity 210-a. Furthermore, in some embodiments, the logical unit 205-a can establish a UPAP with the network entity 105-a. For example, the logical unit 205-a may have a UPAP layer entity 210-c. In some embodiments, the UPAP configuration may depend on the radio link, thereby allowing the radio protocols to be abstracted from the UPF service. In some embodiments, the UPAP can be used for packet forwarding (e.g., in architectures employing IAB, or similar architectures). In some embodiments, network entity 105-a may support the establishment of multiple UPAP layer entities for a single data session deployment, which can be described in more detail herein, for example with reference to Figures 4A and 4B. Additional details regarding embodiments in which network entity 105-a and UE115-a establish UPAP layer entities can be described herein, for example with reference to Figures 3A, 3B, 7A-7D, and 8.

[0133] In wireless communication system 200-b, logical unit 205-b can be configured to communicate with network entity 105-b, and network entity 105-b can be configured to communicate with UE 115-b. In some embodiments, logical unit 205-b may include some or all of the functionality of the UPAP layer. For example, logical unit 205-b (e.g., UPF, DU, network entity) can be configured to establish a corresponding UPAP layer entity with UE 115-b. For example, logical unit 205-b may have UPAP layer entity 210-e, and UE 115-b may have UPAP layer entity 210-d. In some embodiments, UPAP performs QoS processing and is not exposed to radio state and / or protocol. Therefore, a service header can be added a priori and propagated to the appropriate network entity (e.g., network entity 105-b). In some embodiments, network entity 105-b may handle MAC functionality and / or RLC functionality (for example, network entity 105-b may not handle UPAP functionality). Additional details regarding embodiments in which logical unit 205-b includes some or all of the functionality of the UPAP layer are described herein with reference to, for example, Figures 12 and 13.

[0134] In the wireless communication system 200-c, the logical unit 205-c can be configured to communicate with the network entity 105-c, and the network entity 105-c can be configured to communicate with the UE 115-c. In some embodiments, the functionality of the UPAP layer can be divided between the logical unit 205-c and the network entity 105-c. For example, the logical unit 205-c can establish a corresponding high UPAP layer entity with the UE 115-c, and the network entity 105-c can establish a corresponding low UPAP layer entity with the UE 115-c. For example, the logical unit 205-c may have a first high UPAP layer entity 215-a, the network entity 105-c may have a first low UPAP layer entity 220-a, and the UE 115-c may have a second high UPAP layer entity 215-b and a second low UPAP layer entity 220-b. In some embodiments, high UPAP layer entities 215-a and 215-b can be used to insert and delete high UPAP headers, and to perform tasks such as header compression, header decompression, encryption, decryption, or any combination thereof. Furthermore, low UPAP layer entities 220-a and 220-b can be used to perform operations on high UPAP headers, such as correcting, modifying, or removing high UPAP headers, and to insert or delete low UPAP headers. In some embodiments, the low UPAP layer entity 220-a can be programmed through an inter-UPAP interface between logical unit 205-c and network entity 105-c. In such embodiments, logical unit 205-c may have an inter-UPAP interface entity 225-a, and network entity 105-c may have an inter-UPAP interface entity 225-b.In some embodiments, non-wireless related functions can be performed in the high UPAP within the logical unit 205-c, and wireless related tasks can be performed in the low UPAP within the network entity 105-c having an inter-UPAP interface. Further details regarding the high and low UPAPs can be described herein with reference to, for example, Figures 14-16.

[0135] In some embodiments, UPAP layer entities can be used to perform data sessions (e.g., PDU sessions) for DRB mapping, QoS processing, and header insertion and extraction. For example, UPAP layer entities 210-a to 210-e, high UPAP layer entities 215-a and 215-b, low UPAP layer entities 220-a and 220-b, or any combination thereof, can be configured to perform QoS processing and insert a main header (e.g., a main header common to multiple deployments) onto network layer traffic packets. Furthermore, UPAP layer entities 210-a to 210-e, high UPAP layer entities 215-a and 215-b, low UPAP layer entities 220-a and 220-b, or any combination thereof, can be configured to insert one or more service headers (e.g., packet-dependent and / or deployment-dependent service headers, as well as potentially programmable service headers) onto network layer traffic packets. In some embodiments, the main header and / or service headers can be used to implement a QoS model. For example, network layer traffic packets may contain information available to the scheduler. By using service headers, the QoS model can be tailored to specific use cases and / or scheduler capabilities (for example, service headers may contain deadline information). In some embodiments, UPAP layer entities can determine UPAP interactions with user plane DU packet pipelines, as well as with other services and / or logical units such as UPFs.

[0136] Furthermore, the main header and / or service header can expose UPAP programmability to services and gateways (e.g., logical unit 205-a, logical unit 205-b) to constitute packet paths and / or RAN pipelines. For example, a service (e.g., a service associated with logical unit 205-a) can provide within the service header instructions that network entity 105-a can use to perform radio functions (e.g., the service can program the radio layer, or the service can provide programmability to the RAN). In some such embodiments, network entity 105-a can expose available service headers and associated functionality to the radio layer via an application programming interface (API). In some embodiments, a programmable packet header can encapsulate in-band instructions to an intermediate or destination node about how to process the packet, and / or information about the packet intended for use at the node, when processed by the UPAP layer entity at that node. In one embodiment (e.g., programmable and / or reconfigurable target packet reordering), the reordering can be fully enabled or disabled with respect to the DRB. When sorting is enabled, the baseline (e.g., the default) sorts each packet from the DRB as a whole. However, in certain deployments, complete sorting may not be necessary. For example, XR sorting can sort packets associated with the same application data unit (ADU). In general, sorting domains can be defined by grouping packets that should be sorted as a whole. UPAP layer entities can perform marking-based sorting, where packets with similar header marks in the sorting field are sorted separately from other packets that make up the sorting domain.Further details of this embodiment can be described herein, for example, with reference to Figure 11.

[0137] In some embodiments, UPAP layer entities 210-a to 210-e, high UPAP layer entities 215-a and 215-b, low UPAP layer entities 220-a and 220-b, or any combination thereof, can be used to perform on-pass header updates. For example, packet headers (e.g., service headers) can be added, deleted, or updated along the path (e.g., from logical unit 205-a to UE115-a). In some embodiments, service headers may indicate in-band packet rules for on-pass nodes. For example, service headers may indicate whether or not to send acknowledgment (ACK) feedback for a packet, how to perform sorting, whether to discard packets after a predetermined time (e.g., time T), whether to perform timestamping, whether to perform explicit congestion notification (ECN) marking, or any combination thereof. Further details regarding main headers and service headers can be described herein with reference to, for example, Figures 5, 6A, 6B, and 6C. Further details on how service headers can be used to perform on-pass header updates can be described herein, for example, with reference to Figure 9. Further details on how service headers can be used to indicate in-band packet rules can be described herein, for example, with reference to Figure 10.

[0138] In some embodiments, a network entity (e.g., network entities 105-a, 105-b, or 105-c) can send a capability message to a logical unit (e.g., logical units 205-a, 205-b, or 205-c) indicating that the network entity supports instructions for services associated with the radio layer for wireless communication with one or more UEs (e.g., UE115-a, UE115-b, UE115-c). Based on sending the capability message, the network entity can establish a data session with the logical unit associated with one of the UEs, and based on that data session, can receive instructions from the logical unit to perform radio functions associated with services with the UE. Furthermore, the network entity can execute instructions for performing those radio functions at the radio layer. Additional details can be described herein with reference to, for example, Figure 17.

[0139] In some embodiments, a network entity (e.g., network entities 105-a, 105-b, or 105-c) can send capability messages to a logical unit (e.g., logical units 205-a, 205-b, or 205-c) indicating the services that the network entity supports. The network entity can establish a data session with the logical unit associated with a flow between the logical unit and the UE (e.g., UE115-a, 115-b, UE115-c). Based on the data session, the network entity can establish a data radio bearer with the UE associated with the flow. The logical unit can send a first message associated with the flow to the network entity. The first message may include a first header associated with a first layer based on the data session with the logical unit. Furthermore, or alternatively, the first message may include a main header, a service header associated with the first layer, an instruction that the service header should be processed by the network entity, instructions to perform radio functions associated with the service with the UE, or any combination thereof. Further details can be described herein, for example, with reference to Figure 18.

[0140] In some embodiments, a wireless device (e.g., one of the logical units 205-a to 205-c, one of the network entities 105-a to 105-c, and one of the UEs 115-a to 115-c) can generate a first service data unit associated with the radio link control layer, which includes a first packet, a first main header relating to the first packet and associated with a first layer above the radio link control layer, and a first service header relating to the first packet and associated with a service provided by one or more network entities in the network. In such embodiments, the first main header and the first service header, respectively, can be associated with a flow between the logical unit and the UE. In some such embodiments, the wireless device can generate a second service data unit associated with the radio link control layer, which includes a second packet, a second main header relating to the first layer, and a second service header relating to the second packet and associated with a service. In some such embodiments, the second main header and the second service header can each be associated with a flow between the logical unit and the UE. Furthermore, the first service header and the second service header can be different from each other. In some embodiments, the wireless device can output one or more messages, including a first service data unit and a second service data unit. Additional details can be described herein with reference to, for example, Figure 19.

[0141] In some embodiments, a wireless device (e.g., one of the logical units 205-a to 205-c, one of the network entities 105-a to 105-c, and one of the UEs 115-a to 115-c) can be configured to communicate (e.g., receive) a first message, which includes a first service data unit associated with the radio link control layer. From the first service data unit, the wireless device can derive a first packet, a first main header (e.g., a UPAP main header) relating to the first packet and associated with a first layer above the radio link control layer, and a first service header relating to the first packet and associated with a service provided by one or more network entities in the network, each of which is associated with a flow between the logical unit and the UE. In some embodiments, a wireless device can generate a second service data unit associated with a radio link control layer, which includes a second packet, a second main header, and a second service header associated with a service, each of which can be associated with a flow between a logical unit and a UE, where the second service header is based on and different from the first service header. In some embodiments, the wireless device can communicate (e.g., transmit) a second message containing the second service data unit. Further details can be described herein with reference to, for example, Figure 20.

[0142] In some embodiments, the use of service headers can improve programmability and service adaptability. Furthermore, the techniques described herein may allow UPAP headers associated with some deployments to have reduced overhead compared to UPAP headers associated with other deployments. For example, a service header may not be inserted into an IP packet associated with IoT, while a service header may be inserted into an IP packet associated with XR. Therefore, the overhead associated with UPAP headers for IP packets associated with IoT can be reduced compared to XR. Moreover, since service headers can differ between packets, these service headers may contain unique fields, unique values ​​within the same field, executable instructions, or any combination thereof, which can enable different packets of network layer traffic to be processed in different ways (e.g., by RLC layer entities, MAC layer entities, PHY layer entities). In some embodiments, the use of UPAP layer entities may enable the merging of core services and RAN services, which can simplify protocols and reduce duplication between core and RAN. Merged services can be hosted based on the capabilities of each service in terms of deployment topology and constraints. In some such embodiments, real-time link management can be moved to the RAN edge, which may allow for the separation of performance-sensitive features, such as configuration (e.g., RRC) and activation (e.g., MAC). Adaptation in the RAN may enable more efficient feature activation and / or selection based on user experience constraints.

[0143] Figures 3A and 3B show embodiments 300-a and 300-b of a top-plane architecture supporting a user-programmable layer for wireless communication, according to one or more aspects of the present disclosure. In some embodiments, top-plane architectures 300-a and 300-b may implement one or more aspects of wireless communication systems 100 and / or 200-a to 200-c. For example, UPF320-a and 320-b may each be an embodiment of logic unit 205-a as described with reference to Figure 2A. Furthermore, or alternatively, DU330-a and 330-b may each be an embodiment of network entity 105-a as described with reference to Figure 2A, and / or network entity 105 and / or DU165 as described with reference to Figure 1. Furthermore, any of the UPAP layer entities 335-a, 335-c, or 335-d may be an embodiment of the UPAP layer entity 210-b as described with reference to Figure 2A, and / or the UPAP layer entity 335-b may be an embodiment of the UPAP layer entity 210-c as described with reference to Figure 2.

[0144] In the upper-plane architecture 300-a, the UPF320-a can communicate with the data network 305-a, the logical unit 310-a (e.g., via the service communication interface 315-a), and the DU330-a. The DU330-a can communicate with the logical unit 310-b (e.g., via the service communication interface 315-b). In some embodiments, the UPF320-a may be configured to have an IP layer entity 325-a, and the DU330-a may be configured to have a UPAP layer entity 335-a, an RLC layer entity 340-a, a MAC layer entity 345-a, and a PHY layer entity 350-a. In some embodiments, these UPAP layer, RLC layer, MAC layer, and PHY layer may be referred to as the radio layer 332.

[0145] In the upper-plane architecture 300-b, UPF320-b can communicate with the data network 305-b, the logical unit 310-c (e.g., via the service communication interface 315-c), and DU330-b. DU330-b can communicate with the logical unit 310-d (e.g., via the service communication interface 315-d). In some embodiments, UPF320-b can be configured to have an IP layer entity 325-b and a UPAP layer entity 335-b. Furthermore, DU330-b can be configured to have an RLC layer entity 340-b, a MAC layer entity 345-b, a PHY layer entity 350-b, a first UPAP layer entity 335-c, and a second UPAP layer entity 335-d. The first UPAP layer entity 335-c may function as a radio interface component (e.g., a UPAP layer entity that performs tasks related to a specific radio interface, such as a radio interface between DU330-b and UE), while the second UPAP layer entity 335-d may function as a capability-exposing component that can interface with services through an interface (e.g., a standardized interface).

[0146] A UPF (e.g., UPF320-a or 320-b) configured to communicate directly (e.g., without a CU) with a DU such as DU330-a or 330-b, and / or configured to have a UPAP layer entity, may be referred to as an enhanced UPF (e.g., eUPF). Similarly, a DU (e.g., DU330-a or 330-b) configured to communicate directly (e.g., without a CU) with a UPF such as UPF320-a or 320-b, and / or configured to have a UPAP layer entity, may be referred to as an enhanced DU (eDU). In some embodiments, an eUPF may function as a gateway to a data network (e.g., data network 305-a, data network 305-b) and may perform Layer 3 (L3) functionality (e.g., processing and policy) and / or one or more Layer 2 (L2) functions. In some embodiments, the eDU may perform wireless access functions and / or one or more non-wireless L2 functions (e.g., encryption).

[0147] In some embodiments, logical units 310-a and 310-c may be associated with a first type of service that uses an abstracted wireless link layer model. For example, logical units 310-a and 310-b may interact with the UPF (e.g., 320-a or 320-b) and therefore may not track wireless L2 details such as the type of RAT used for delivery. Furthermore, logical units 310-a and 310-c may be limited in the policies they can implement (e.g., billing, throttling to adapt the application layer). Examples of the first type of service include video streaming, web browsing, or file downloads.

[0148] In some embodiments, logical units 310-b and 310-d can be associated with a second type of service that directly interacts with the L2 radio layer of the corresponding DU (e.g., DU330-a and DU330-b, respectively). Logical units associated with the second type of service may operate with the identification of radio layer events. For example, positioning interfaces and the configuration of certain control plane signaling may be radio-dependent. Logical units associated with the second type of service may use the DU API to communicate information to the corresponding DU (e.g., with respect to programmability). In some embodiments, the second type of service may be local and / or radio-dependent (e.g., radio as a service), thus enabling non-data services and / or mixed data sensing services.

[0149] In some embodiments, user plane adaptation may function as the top layer in a DU (e.g., eDU). In some embodiments, user plane adaptation may interface with two or more types of entities. For example, user plane adaptation may interface with a UPF (e.g., eUPF), which may be a gateway to data networks (e.g., data networks 305-a, 305-b) and several services (e.g., the first type of services described herein). In such cases, UPAP can perform flow-to-DRB conversion according to the PDU configuration. Furthermore, UPAP may function as a local DU gateway to a second type of service described herein, which may be referred to as a user plane service, and which may be able to access the DU directly using an open API. Through the open DU API, the second type of service may establish a data session (e.g., a PDU session), which may create one or more UPAP layer entities within the DU.

[0150] Figures 4A and 4B show embodiments 400-a and 400-b of a wireless communication system supporting a user-programmable layer for wireless communication, according to one or more aspects of the present disclosure. In some embodiments, wireless communication systems 400-a and 400-b may implement one or more aspects of wireless communication system 100, wireless communication systems 200-a to 200-c, upper-plane architectures 300-a and 300-b, or any combination thereof. For example, network entities 405-a and 405-b may be an embodiment of network entity 105 and / or DU165 as described with reference to Figure 1, network entity 105-a as described with reference to Figure 2A, DU330-a as described with reference to Figure 3A, DU330-b as described with reference to Figure 3B, or any combination thereof. Furthermore, UE410-a and 410-b can each be an embodiment of UE115 as described with reference to Figure 1, and / or UE115-a as described with reference to Figure 2A. Furthermore, UPAP layer entities 415-a, 420-a, 425-a, and 430-a can each be an embodiment of UPAP layer entity 210-b as described with reference to Figure 2A, UPAP layer entity 335-a as described with reference to Figure 3A, UPAP layer entity 335-c or 335-d as described with reference to Figure 3B, or any combination thereof. Furthermore, UPAP layer entities 415-b, 420-b, 425-b, and 430-b can each be an embodiment of UPAP layer entity 210-a as described with reference to Figure 2A.

[0151] As described herein, a data session (e.g., a PDU session) can establish multiple UPAP layer entities within a network entity (e.g., a DU, eDU). For example, a single IP address can be mapped to multiple UPAP layer entities.

[0152] In a first embodiment shown in wireless communication system 400-a, a network entity 405-a (e.g., DU, eDU) can establish a first set of downlink UPAP layer entities (e.g., downlink UPAP layer entities 415-a and 415-b) with UE410-a. Similarly, a network entity 405-a can establish a second set of uplink UPAP layer entities (e.g., uplink UPAP layer entities 420-a and 420-b) with UE410-a. Downlink UPAP layer entities can be used with respect to downlink traffic, and uplink UPAP layer entities can be used with respect to uplink traffic. In some embodiments, having separate UPAP layer entities for uplink and downlink may allow traffic from UE410-a to have a shorter extension header (e.g., a shorter or fewer service header) than traffic from network entity 405-a (e.g., in embodiments where UE410-a has less capability in its scheduler). By having a shorter extension header, the UE410-a may consume less power and / or use fewer resources when transmitting uplink traffic. In some embodiments, the network entity 405-a may be configured to have uplink-only, downlink-only, or bidirectional UPAP layer entities.

[0153] In a second embodiment shown in wireless communication system 400-b, a network entity 405-b (e.g., DU, eDU) can establish a first set of UPAP layer entities (e.g., UPAP layer entities 425-a and 425-b) with UE 410-b, and a second set of UPAP layer entities (e.g., UPAP layer entities 430-a and 430-b) with UE 410-b. In some embodiments, the first set of UPAP layer entities and the second set of UPAP layer entities can be associated with a multipath transmission control protocol (MPTCP). Furthermore, the first set of UPAP layer entities can be associated with traffic in frequency range 1 (FR1), and the second set of UPAP layer entities can be associated with traffic in frequency range 2 (FR2). By using separate packet pipelines on FR1 and FR2, network entities 405-a and / or UE410-b can take into account different radio link variations associated with FR1 and FR2 (for example, in cases of overlap between FR1 and FR2).

[0154] Figure 5 shows one embodiment of the UPAP PDU500 supporting a user-programmable layer for wireless communication according to one or more aspects of the present disclosure. In some embodiments, the UPAP PDU500 can be implemented according to one or more aspects of Figures 1 to 4B. For example, UPAP PDU500 can be generated by one or more of the following: network entity 105 or UE115 as described with reference to Figure 1; UPAP layer entities 210-a to 210-e, high UPAP layer entities 215-a and 215-b, low UPAP layer entities 220-a and 220-b as described with reference to Figures 2A to 2C; UPAP layer entities 335-a to 335-d as described with reference to Figures 3A and 3B; UPAP layer entities 415-a, 415-b, 420-a, 420-b, 425-a, 425-b, 430-a, 430-b, or any combination thereof, or any combination thereof.

[0155] In some embodiments, a UPAP layer entity may insert a main header 505 and one or more service headers (e.g., service headers 510-a and 510-b) onto a payload 515 (e.g., a payload containing packets of network layer traffic, such as IP traffic). In such embodiments, the functionality of the UPAP layer can be divided into main functionality and service functionality, each reflected in the main header (e.g., main header 505) and one or more service headers (e.g., service headers 510-a and 510-b). In some embodiments, the main header 505 may be common for multiple deployments (e.g., arbitrary deployments), and the service headers (e.g., 510-a and 510-b) may be configured per data session (e.g., per PDU session). In some embodiments, depending on the configuration, multiple service headers may be sequentially appended to or stacked on a local header (e.g., service headers 510-a and 510-b may be stacked sequentially). In some embodiments, the service headers may function as extension headers.

[0156] In some embodiments, the main header 505 may contain one or more parameters, such as data / control (D / C) flags, header length information, information about extended fields, a sequence number, or any combination thereof. One or more service headers may be used to implement a QoS model, expose UPAP programmability to services and gateways, coordinate with on-pass header updates, or carry instructions (e.g., instructions for executing radio function 511) and / or parameters used by on-pass nodes. In some embodiments (e.g., IoT deployments), the main header 505 may be inserted, but one or more service headers may not be present. In other embodiments, service headers may be continuously extensible with respect to various applications and deployments (e.g., artificial intelligence (AI) service headers, XR service headers, energy efficiency service headers, sidelink service headers, time-sensitive network (TSN) service headers). In some embodiments, service headers and associated services are based on DU capabilities.

[0157] In some embodiments, the main header 505, service headers (e.g., 510-a and 510-b), and payload 515 can be an embodiment of an RLC service data unit (SDU) 520, or can be included within an RLC SDU 520. For example, an RLC entity of a wireless device (e.g., a network entity, UE, DU) can process the main header 505, service header, and payload 515 as an RLC SDU 520, and an RLC header can be added to the RLC SDU 520. In some embodiments, the resulting RLC SDU can be concatenated with another RLC SDU (e.g., containing another main header, one or more other service headers, and another payload) to form a larger RLC SDU with an added RLC header. Alternatively, the resulting RLC SDU can be divided into multiple segmented RLC SDUs, each with a corresponding RLC header inserted.

[0158] In some embodiments, the ability to remove or add service headers can lead to reduced overhead and simplified processing. Furthermore, service headers can enable adaptability to the application and transport layers, and full programmability through service interfaces with UPAP layer entities.

[0159] Figures 6A to 6C may be embodiments 600-a, 600-b, and 600-c of a UPAP header supporting a user-programmable layer for wireless communication, according to one or more embodiments of the present disclosure. In some embodiments, the UPAP headers 600-a, 600-b, and 600-c may be implemented according to one or more embodiments of Figures 1 to 5. For example, UPAP headers 600-a, 600-b, and 600-c can be generated by one or more of the following: network entity 105 or UE115 as described with reference to Figure 1; UPAP layer entities 210-a to 210-e, high UPAP layer entities 215-a and 215-b, and low UPAP layer entities 220-a and 220-b as described with reference to Figures 2A to 2C; UPAP layer entities 335-a to 335-d as described with reference to Figures 3A and 3B; UPAP layer entities 415-a, 415-b, 420-a, 420-b, 425-a, 425-b, 430-a, 430-b, or any combination thereof, or any combination thereof. Furthermore, or alternatively, the main headers 605-a, 605-b, 605-c, and 605-d can each be an embodiment of the main header 505 as described with reference to Figure 5, and the service headers 610-a, 610-b, and 610-c can each be an embodiment of the service header 510-a or 510-b as described with reference to Figure 5.

[0160] As described herein, QoS processing using service headers can be deployment-specific and / or packet-specific. For example, a service can indicate to the network the processing of a particular packet to a level of granularity as low as that of the individual packet (e.g., depending on the capabilities of the DU). In some embodiments, the complexity of the header (e.g., length of the service header, total number of service headers) can increase depending on constraints (e.g., deployment constraints, service level agreement (SLA) constraints). Furthermore, the packet header (e.g., the service header) can be tailored to the use case.

[0161] In the first embodiment, as shown in Figure 6A, the main header 605-a may be inserted on the payload, and the service header may not be inserted. In the second embodiment, as shown in Figure 6B, the main header 605-b and the service header 610-a may be inserted on the payload. In the third embodiment, the main header 605-c and the service header 610-b may be inserted on the first payload, and the main header 605-d and the service header 610-c may be inserted on the second payload. In some such embodiments, the service header 610-b may include a field corresponding to the value of a first parameter (e.g., a first deadline t1), and the service header 610-c may include a field corresponding to the value of a second parameter (e.g., a second deadline t2). In some embodiments, the main headers 605-c and 605-d may include the same value for each field.

[0162] In some embodiments, the first embodiment having a main header 605-a may have reduced overhead compared to the second and third embodiments (for example, when the payload contains IoT information). However, the second embodiment may enable the transmission of information used for a specific application (for example, when the payload contains XR information). Furthermore, the third embodiment may enable the processing of the first payload in a different manner than the second payload.

[0163] Figures 7A to 7D may be embodiments 700-a, 700-b, 700-c, and 700-d of a layer architecture supporting a user-programmable layer for wireless communication, according to one or more aspects of the present disclosure. In some embodiments, layer architectures 700-a, 700-b, 700-c, and 700-d may be implemented according to one or more aspects of Figures 1 to 4B. For example, UE701-a, 701-b, 701-c, and 701-d may be embodiments of UE115 as described with reference to Figure 1, UE115-a as described with reference to Figure 2A, UE410-a or 410-b as described with reference to Figures 4A and 4B, or any combination thereof. Furthermore, DU702-a, 702-b, 702-c, and 702-d can each be an embodiment of network entity 105 and / or DU165 as described with reference to Figure 1, network entity 105-a as described with reference to Figure 2A, DU330-a or 330-b as described with reference to Figures 3A and 3B, network entity 405-a or 405-b as described with reference to Figures 4A and 4B, or any combination thereof. Furthermore, UPF703-a and 703-b can each be an embodiment of logic unit 205-a as described with reference to Figure 2A, or UPF320-a or 320-b as described with reference to Figures 3A and 3B. Furthermore, each of the logical units 704-a, 704-b, 704-c, and 704-d can be an embodiment of the logical unit 205-a as described with reference to Figure 2A, the logical unit 310-a, the logical unit 310-b, the logical unit 310-c, the logical unit 310-d, the data network 305-a, or the data network 305-b, or any combination thereof, as described with reference to Figures 3A and 3B.

[0164] In layer architecture 700-a, UE701-a may include application layer entity 705-a, IP layer entity 710-a, UPAP layer entity 715-a, RLC layer entity 720-a, MAC layer entity 725-a, and PHY layer entity 730-a. DU702-a may include UPAP layer entity 715-b, RLC layer entity 720-b, MAC layer entity 725-b, and PHY layer entity 730-b. Furthermore, DU702-a may include backhaul interface entity 735-a and layer interface entity 740-a. UPF703-a may include IP layer entity 710-b, backhaul interface entity 735-b, and layer interface entity 740-b. Logical unit 704-a may include application layer entity 705-b and IP layer entity 710-c. Application layer entity 705-a can interface with application layer entity 705-b, IP layer entity 710-a can interface with IP layer entity 710-b, IP layer entity 710-b can interface with IP layer entity 710-c, UPAP layer entity 715-a can interface with UPAP layer entity 715-b, RLC layer entity 720-a can interface with RLC layer entity 720-b, MAC layer entity 725-a can interface with MAC layer entity 725-b, PHY layer entity 730-a can interface with PHY layer entity 730-b, backhaul interface entity 735-a can interface with backhaul interface entity 735-b, and layer interface entity 740-a can interface with layer interface entity 740-b.In some embodiments, the logical unit 704-a can be associated with a data network and / or a first type of service as described herein.

[0165] In layer architecture 700-b, UE701-b may include application layer entity 705-c, IP layer entity 710-d, UPAP layer entity 715-c, RLC layer entity 720-c, MAC layer entity 725-c, and PHY layer entity 730-c. DU702-b may include UPAP layer entity 715-d, RLC layer entity 720-d, MAC layer entity 725-d, and PHY layer entity 730-d. DU702-b may also include backhaul interface entity 735-c and layer interface entity 740-c. UPF703-b may include IP layer entity 710-e, UPAP layer entity 715-e, backhaul interface entity 735-d, and layer interface entity 740-d. Logical unit 704-b may include application layer entity 705-d and IP layer entity 710-f.Application layer entity 705-c can interface with application layer entity 705-d, IP layer entity 710-d can interface with IP layer entity 710-e, IP layer entity 710-e can interface with IP layer entity 710-f, UPAP layer entity 715-c can interface with UPAP layer entity 715-d, UPAP layer entity 715-d can interface with UPAP layer entity 715-e, RLC layer entity 720-c can interface with RLC layer entity 720-d, MAC layer entity 725-c can interface with MAC layer entity 725-d, PHY layer entity 730-c can interface with PHY layer entity 730-d, backhaul interface entity 735-c can interface with backhaul interface entity 735-d, and layer interface entity 740-c can interface with layer interface entity 740-d. In some embodiments, the logical unit 704-b can be associated with a data network and / or a first type of service as described herein.

[0166] In layer architecture 700-c, UE701-c may include application layer entity 705-e, IP layer entity 710-g, UPAP layer entity 715-f, RLC layer entity 720-e, MAC layer entity 725-e, and PHY layer entity 730-e. DU702-c may include UPAP layer entity 715-g, RLC layer entity 720-f, MAC layer entity 725-f, and PHY layer entity 730-f. Furthermore, DU702-c may include service interface entity 745-a and layer interface entity 740-e. Logical unit 704-c may include application layer entity 705-f, IP layer entity 710-h, service interface entity 745-b, and layer interface entity 740-f. Application layer entity 705-e can interface with application layer entity 705-f, IP layer entity 710-g can interface with IP layer entity 710-h, UPAP layer entity 715-f can interface with UPAP layer entity 715-g via a radio protocol interface, RLC layer entity 720-e can interface with RLC layer entity 720-f, MAC layer entity 725-e can interface with MAC layer entity 725-f, PHY layer entity 730-e can interface with PHY layer entity 730-f, service interface entity 745-a can interface with service interface entity 745-b, and layer interface entity 740-e can interface with layer interface entity 740-f. The service interface may enable programmability. In some embodiments, logical unit 704-c can be associated with a second type of service as described herein.

[0167] In layer architecture 700-d, UE701-d may include application layer entity 705-g, IP layer entity 710-i, UPAP layer entity 715-h, RLC layer entity 720-g, MAC layer entity 725-g, and PHY layer entity 730-g. DU702-d may include UPAP layer entity 715-i, RLC layer entity 720-h, MAC layer entity 725-h, and PHY layer entity 730-h. Furthermore, DU702-d may include service interface entity 745-c and layer interface entity 740-g. Logical unit 704-d may include application layer entity 705-h, IP layer entity 710-j, UPAP layer entity 715-j, service interface entity 745-d, and layer interface entity 740-h. Application layer entity 705-g can interface with application layer entity 705-h, IP layer entity 710-i can interface with IP layer entity 710-j, UPAP layer entity 715-h can interface with UPAP layer entity 715-i via the radio protocol interface, UPAP layer entity 715-i can interface with UPAP layer entity 715-j, RLC layer entity 720-g can interface with RLC layer entity 720-h, MAC layer entity 725-g can interface with MAC layer entity 725-h, PHY layer entity 730-g can interface with PHY layer entity 730-h, service interface entity 745-c can interface with service interface entity 745-d, and layer interface entity 740-g can interface with layer interface entity 740-h. The service interface can function as a direct header interface.It should be noted that these IP layer entities can be replaced with a different type of network protocol (e.g., an Ethernet layer entity) without departing from the scope of this disclosure. In some embodiments, the logical unit 704-d can be associated with a second type of service, as described herein.

[0168] Figure 8 shows one embodiment of process flow 800 supporting a user-programmable layer for wireless communication according to one or more aspects of the present disclosure. In some embodiments, process flow 800 can be implemented according to one or more aspects of Figures 1 to 7D. For example, logical unit 805 may be one embodiment of network entity 105 and / or DU165 as described with reference to Figure 1, logical unit 205-a or network entity 105-a as described with reference to Figure 2A, logical unit 310-b, logical unit 310-d, UPF320-a, UPF320-b, DU330-a, or DU330-b as described with reference to Figures 3A and 3B, network entity 405-a or 405-b as described with reference to Figures 4A and 4B, UPF703-a, UPF703-b, logical unit 704-c, or logical unit 704-d as described with reference to Figures 7A to 7D, or any combination thereof. The network entity 810 may be, in one embodiment, a wireless device 105 as described with reference to Figure 1, a network entity 105-a as described with reference to Figure 2A, a DU330-a or DU330-b as described with reference to Figures 3A and 3B, a network entity 405-a or 405-b as described with reference to Figures 4A and 4B, a DU702-a, DU702-b, DU702-c, or DU702-d as described with reference to Figures 7A to 7D, or any combination thereof. UE815 can be an embodiment of UE115 as described with reference to Figure 1, UE115-a as described with reference to Figure 2A, UE410-a or 410-b as described with reference to Figures 4A and 4B, UE701-a, UE701-b, UE701-c, or UE701-d as described with reference to Figures 7A to 7D, or any combination thereof.

[0169] At 820, UE815 can send a UE data session establishment request to network entity 810. At 825, UE815 can send a UE capability report to network entity 810. At 830, network entity 810 can send a data session establishment request to logical unit 805. At 835, logical unit 805 can send a capability query to network entity 810. At 840, network entity 810 can send a radio capability report to logical unit 805. At 845, logical unit 805 can establish one or more data sessions with network entity 810. At 850, network entity 810 can establish one or more DRBs and / or UPAPs with UE815. At 855, logical unit 805 can communicate with UE815 for data transmission via network entity 810.

[0170] In some embodiments, UPAP can interface directly with a logical unit associated with a second type of service to expose its radio capabilities (e.g., network entity 810). In such embodiments, the logical unit associated with the second type of service can program UPAP layer user plane functionality via an API to gain control over radio functionality and / or packet forwarding behavior. For example, in data session establishment (e.g., PDU session establishment), network entity 810 can communicate its capabilities with its programmable API (e.g., in 840). Logical unit 805 can, accordingly, establish a data session with the UPAP layer entities in network entity 810 and / or UE 815 (e.g., in 845 and 850). Such establishment may include information associated with a header to be attached to the packet, processing of various packet headers and metadata, and configuration of user plane on-pass behavior and associated DRB properties (e.g., QoS). In some embodiments, the capabilities supported by the network entity 810 may include instructions that the network entity 810 supports supported QoS models and / or instructions regarding services associated with the radio layer for wireless communication with the UE 815. In some embodiments, instructions for available radio APIs may include instructions for available headers that can be added by the UPAP layer and / or available actions for programming on-pass components.

[0171] Figure 9 shows one embodiment of a service header timestamping scheme 900 supporting a user-programmable layer for wireless communication, according to one or more aspects of the present disclosure. In some embodiments, the service header timestamping scheme 900 can be implemented in one or more aspects of Figures 1 to 8. For example, logical unit 905 can be one embodiment of network entity 105 and / or DU165 as described with reference to Figure 1, logical unit 205-a or network entity 105-a as described with reference to Figure 2A, logical unit 310-b, logical unit 310-d, UPF320-a, UPF320-b, DU330-a, or DU330-b as described with reference to Figures 3A and 3B, network entity 405-a or 405-b as described with reference to Figures 4A and 4B, UPF703-a, UPF703-b, logical unit 704-c, or logical unit 704-d as described with reference to Figures 7A to 7D, logical unit 805 as described with reference to Figure 8, or any combination thereof. Furthermore, DU910-a and 910-b can each be an embodiment of network entity 105 as described with reference to Figure 1, network entity 105-a as described with reference to Figure 2A, DU330-a or DU330-b as described with reference to Figures 3A and 3B, network entity 405-a or 405-b as described with reference to Figures 4A and 4B, DU702-a, DU702-b, DU702-c, or DU702-d as described with reference to Figures 7A to 7D, network entity 810 as described with reference to Figure 8, or any combination thereof. Furthermore, UE915 can be an embodiment of UE115 as described with reference to Figure 1, UE115-a as described with reference to Figure 2A, UE410-a or 410-b as described with reference to Figures 4A and 4B, UE701-a, UE701-b, UE701-c, or UE701-d as described with reference to Figures 7A to 7D, UE815 as described with reference to Figure 8, or any combination thereof.

[0172] In a TSN network, a precision time synchronization protocol (PTP) (e.g., generalized PTP, gPTP) may involve each node calculating the latency to the next node and adding a local timestamp to the packet header. This timestamp can be extracted and processed hop-by-hop to the destination node. A packet may contain a payload (e.g., a payload that transmits instructions to be executed) and the time until these instructions are executed. Therefore, maintaining more precise timing with respect to packets can lead to more accurate performance.

[0173] To implement the PTP protocol, logical unit 905 (for example, associated with a service for direct packet marking regarding TSN) can send TSN packet 920 to DU910-a. DU910-a can insert a main header 925 and a service header 930-a containing a first timestamp value. Thus, DU910-a can apply a timestamp to initiate the gPTP protocol. DU910-a can then send the main header 925, service header 930-a, and TSN packet 920 to DU910-b. DU910-b can extract the first timestamp value from service header 930-a, apply the gPTP protocol to account for latency, modify service header 930-a to account for dwell time, and apply a second timestamp value. For example, service header 930-a can be modified to create a service header 930-b that may contain a second timestamp value. DU910-b can send the main header 925, service header 930-b, and TSN packet to UE915. UE915 can extract the second timestamp value from service header 930-b along with other gPTP header information, calculate clock synchronization, and apply the TSN packet payload.

[0174] In this way, the service layer can program and / or configure the UPAP layer along the route to execute the PTP protocol by extracting existing service headers (for example, via service interface entities 745-a to 745-d), processing timing information, and adding new service headers with new timing information. By performing the procedure in this way, synchronization can be maintained along the route (for example, regardless of the number of nodes or DUs).

[0175] Figure 10 shows one embodiment of a sorting scheme 1000 supporting a user-programmable layer for wireless communication, according to one or more aspects of the present disclosure. In some embodiments, the sorting scheme 1000 can be implemented according to one or more aspects of Figures 1 to 7D. For example, UPAP layer entities 1005-a and 1005-b can be one or more of the UPAP layer entities 210-a to 210-e, high UPAP layer entities 215-a and 215-b, and low UPAP layer entities 220-a and 220-b as described with reference to Figures 2A to 2C, one or more of the UPAP layer entities 335-a to 335-d in Figures 3A and 3B, one or more of the UPAP layer entities 415-a, 415-b, 420-a, 420-b, 425-a, 425-b, 430-a, and 430-b as described with reference to Figures 4A and 4B, one or more of the UPAP layer entities 715-a to 715-j in Figures 7A to 7D, or any combination thereof, as one embodiment.

[0176] In some embodiments, head-of-line (HOL) flow blocking may occur when PDCP is used. For example, waiting for lost or delayed packets in PDCP for reordering may block other packets that have already been received from being forwarded. Furthermore, heterogeneous routes (FR1 routes and FR2 dual connectivity routes, and / or split bearers) can cause imbalances between routes, increasing the size of the reordering buffer.

[0177] To avoid inter-HOL flow blocking or delay due to heterogeneous paths in DU-based duplication, marking-based sorting can be performed using UPAP layer entities (e.g., UPAP layer entities 1005-a and 1005-b). In UPAP, different flows can be marked in different ways by using service headers and programmable packet markings, and sorting can be configured based on packet markings. In addition to the use of service headers for sorting markings, service headers may also include sorting timers and instructions to discard or forward (e.g., forward or discard the packet after time T if sorting is unsuccessful) by checking or inferring sorting domain fields, sorting timer fields, fields indicating whether to discard or forward when the sorting time expires, fields indicating whether to send an ACK or a NACK for a particular packet, or any combination thereof. Programmable sorting can be performed in the DU or UE based on whether uplink or downlink data is being transmitted.

[0178] In this embodiment, the UPAP layer entity 1005-a may represent a downlink UPAP layer entity relating to a network entity (e.g., a DU) or an uplink layer entity relating to a UE. In such an embodiment, the uplink flow 1010 can carry ACK feedback and the downlink flow 1015 can carry data. Alternatively, the UPAP layer entity 1005-a may represent an uplink UPAP layer entity relating to a UE or a downlink layer entity relating to a network entity (e.g., a DU). In such an embodiment, the uplink flow 1010 can carry data and the downlink flow 1015 can carry ACK feedback.

[0179] In one embodiment, UPAP layer entity 1005-b may be waiting to receive IP packet 1035-d (e.g., IP packet 10) over link 1020, and may have successfully received IP packets 1035-a, 1035-b, and 1035-c (e.g., IP packets 13, 12, and 11, respectively) over link 1020. The service header 1030 associated with IP packet 1035-d may indicate that the IP packet is part of a second flow, and the service headers associated with IP packets 1035-a, 1035-b, and 1035-c (e.g., service headers 1025-a, 1025-b, and 1025-c, respectively) may indicate that those IP packets are part of a first flow. Even if IP packets 1035-a, 1035-b, and 1035-c have a higher index than IP packet 1035-d, IP packet 1035-d is associated with a different flow than IP packets 1035-a, 1035-b, and 1035-c, so UPAP layer entity 1005-b can send ACK feedback for those IP packets while waiting to receive IP packet 1035-d.

[0180] Figure 11 shows one embodiment of a layer architecture 1100 supporting a user-programmable layer for wireless communication according to one or more aspects of the present disclosure. In some embodiments, the layer architecture 1100 may implement one or more aspects of Figures 1 to 10. For example, each component in Figure 11 may implement some or each of the aspects of the components with corresponding names in Figures 1 to 10. Furthermore, UPF1103 may be an embodiment of logic unit 205-b as described with reference to Figure 2B, DU1102 may be an embodiment of network entity 105 and / or DU165 as described with reference to Figure 1, and / or network entity 105-b as described with reference to Figure 2B, UE1101 may be an embodiment of UE115-b as described with reference to Figure 2B, and / or UE115 as described with reference to Figure 1, or any combination thereof.

[0181] In layer architecture 1100, UE1101 may include application layer entity 1105-a, IP layer entity 1110-a, UPAP layer entity 1115-a, RLC layer entity 1120-a, MAC layer entity 1125-a, and PHY layer entity 1130-a. DU1102 may include RLC layer entity 1120-b, MAC layer entity 1125-b, and PHY layer entity 1130-b. Furthermore, DU1102 may include backhaul interface entity 1135-a and layer interface entity 1140-a. UPF1103 may include IP layer entity 1110-b, UPAP layer entity 1115-b, backhaul interface entity 1135-b, and layer interface entity 1140-b. Logical unit 1104 may include application layer entity 1105-b. Application layer entity 1105-a can interface with application layer entity 1105-b, IP layer entity 1110-a can interface with IP layer entity 1110-b, UPAP layer entity 1115-a can interface with UPAP layer entity 1115-b, RLC layer entity 1120-a can interface with RLC layer entity 1120-b, MAC layer entity 1125-a can interface with MAC layer entity 1125-b, PHY layer entity 1130-a can interface with PHY layer entities, backhaul interface entity 1135-a can interface with backhaul interface entity 1135-b, and layer interface entity 1140-a can interface with layer interface entity 1140-b. In this embodiment, UPF 1103 (e.g., eUPF) can establish a UPAP based on data session constraints.Furthermore, the UE1101 and DU1102 (e.g., eDU) may have DRB and / or RLC channel connections between them.

[0182] In some embodiments, the layer architecture 1100 can be used to communicate messages between the UE 1101 and the logical unit 1104. For example, the UPF 1103 can establish corresponding UPAP layer entities (e.g., UPAP layer entities 1005-a and 1005-b) with the UE 1101. When the UPF 1103 receives an IP packet from the logical unit 1104, the UPF can use the UPAP layer entity 1115-b to generate a main header and / or service header, and provide those IP packets, main headers, and service headers to the UE 1101 via the DU 1102. Similarly, the UE 1101 can generate an IP packet and use the UPAP layer entity 1115-a to insert a main header and / or service header into that IP packet. If the scheduler is able to observe the UPAP service header, the layer architecture 1100 can enable the implementation of a QoS model. For example, a service header may include information (e.g., due date information) that is associated with a QoS flow, which the scheduler (e.g., DU1102) can use for one or more operations. In some embodiments, different service headers may be tailored to different QoS flows and may include parameter values ​​used to communicate information associated with those QoS flows. In some embodiments, the layer architecture 1100 may represent a more detailed diagram of a wireless communication system 200-b, as described with reference to Figure 2B.

[0183] Figure 12 shows one embodiment of process flow 1200 supporting a user-programmable layer for wireless communication according to one or more aspects of the present disclosure. In some embodiments, process flow 1200 may implement one or more aspects of Figures 1 to 11. For example, each component in Figure 12 may implement some or each of the aspects of the corresponding named components in Figures 1 to 11. Furthermore, logic unit 1205 may be an embodiment of logic unit 205-b as described with reference to Figure 2B, DU 1210 may be an embodiment of network entity 105 as described with reference to Figure 1 and / or network entity 105-b as described with reference to Figure 2B, UE 1215 may be an embodiment of UE 115-b as described with reference to Figure 2B and / or UE 115 as described with reference to Figure 1, or any combination thereof. In some embodiments, the process flow 1200 can be used when the layer architecture 1100 is employed and / or may represent a procedure performed by a device of the wireless communication system 200-b.

[0184] In some embodiments, process flow 1200 can be used to enable UE 1215 and logical unit 1205 to communicate a message including a main header and a service header, the service header can be used to carry instructions and / or parameters, or both, to implement a QoS model (for example, different service headers may be tailored to different QoS flows and may include parameter values ​​used to communicate information associated with those QoS flows). For example, at 1220, UE 1215 can send a UE data session establishment request to logical unit 1205 (for example, via DU 1210). At 1225, UE 1215 can send a UE capability report to logical unit 1205 (for example, via DU 1210). At 1230, logical unit 1205 can perform a data session constraint determination. At 1235, logical unit 1205 can establish one or more data sessions and corresponding UPAP layer entities with DU 1210. In 1240, DU1210 can establish one or more DRBs with UE1215.

[0185] In 1245, data transmission can be performed between logical unit 1205 and UE 1215 (for example, via DU 1210). For example, logical unit 1205 can identify an IP packet (for example, received from an external network) and insert a main header and a service header into that IP packet using UPAP layer entities established in logical unit 1205 (for example, UPAP layer entity 1115-b as described in Figure 11). Logical unit 1205 can provide DU 1210 with a message containing those main headers, service headers, and the IP packet. DU 1210 can perform radio functions using RLC layer entities, MAC layer entities, and PHY layer entities (for example, RLC layer entity 1120-b, MAC layer entity 1125-b, and PHY layer entity 1130-b as described with reference to Figure 11) and generate a second message to send to UE 1215 based on the message received from logical unit 1205. DU1210 can send a second message to UE1215, and UE1215 can use its radio capabilities to identify the main header, service header, and IP packet.

[0186] Figure 13 shows one embodiment of a top-plane architecture 1300 supporting a user-programmable layer for wireless communication, according to one or more aspects of the present disclosure. In some embodiments, the top-plane architecture may implement one or more aspects of Figures 1 to 12. For example, each component in Figure 13 may implement some or each of the aspects of the components with corresponding names in Figures 1 to 12. Furthermore, UPF1305 may be an embodiment of logic unit 205-c as described with reference to Figure 2C, and DU1310 may be a network entity 105 and / or DU165 as described with reference to Figure 1, and / or an embodiment of network entity 105-c as described with reference to Figure 2C.

[0187] In some embodiments, the UPAP can be split vertically between the UPF 1305 and the DU 1310 via an internal UPAP interface between the high UPAP layer entity 1320 and the low UPAP layer entity 1325. For example, the UPF 1305 (e.g., eUPF) may include the IP layer entity 1315 and the high UPAP layer entity 1320, while the DU 1310 (e.g., eDU) may include the low UPAP layer entity 1325, the RLC layer entity 1330, the MAC layer entity 1335, and the PHY layer entity 1340. In this setup, the UPAP configuration can distribute functionality between the low UPAP layer entity 1325 and the high UPAP layer entity 1320 in one or more ways. For example, one or more tasks relating to the high UPAP layer entity 1320 can operate on an end-to-end basis rather than as a function of radio conditions (e.g., header compression, encryption, sorting between routes). Furthermore, one or more tasks relating to the low UPAP layer entity 1325 may relate to the operation of a single DU (e.g., DU1310) and, in some embodiments, may depend on wireless conditions. In some embodiments, the UPAP may adjust (e.g., optimize) the arrangement of functionalities in response to wireless factors (e.g., deployment of FR1 and FR2, and / or scaling of independent functionalities).

[0188] Figure 14 shows one embodiment of a layer architecture 1400 supporting a user-programmable layer for wireless communication according to one or more aspects of the present disclosure. In some embodiments, the wireless communication system 1400 may implement one or more aspects of Figures 1 to 13. For example, each component in Figure 14 may implement some or each of the aspects of the corresponding named components in Figures 1 to 13. Furthermore, UPF 1403 may be an embodiment of logic unit 205-c as described with reference to Figure 2C, DU 1402 may be an embodiment of network entity 105 and / or DU 165 as described with reference to Figure 1, and / or network entity 105-c as described with reference to Figure 2C, UE 1401 may be an embodiment of UE 115-c as described with reference to Figure 2C, and / or UE 115 as described with reference to Figure 1, or any combination thereof.

[0189] In layer architecture 1400, UE1401 may include application layer entities 1405-a, IP layer entities 1410-a, high UPAP layer entities 1415-a, low UPAP layer entities 1420-a, RLC layer entities 1425-a, MAC layer entities 1430-a, and PHY layer entities 1435-a. DU1402 may include low UPAP layer entities 1420-b, RLC layer entities 1425-b, MAC layer entities 1430-b, and PHY layer entities 1435-b. Furthermore, DU1402 may include inter-UPAP interface entities 1440-a and layer interface entities 1445-a. UPF1403 may include IP layer entities 1410-b, high UPAP layer entities 1415-b, inter-UPAP interface entities 1440-b, and layer interface entities 1445-b. The logical unit 1404 may include application layer entities 1405-b and IP layer entities 1410-c.Application layer entity 1405-a can interface with application layer entity 1405-b, IP layer entity 1410-a can interface with IP layer entity 1410-b, IP layer entity 1410-b can interface with IP layer entity 115-c, high UPAP layer entity 1415-a can interface with high UPAP layer entity 1415-b, low UPAP layer entity 1420-a can interface with low UPAP layer entity 1420-b, RLC layer The ear entity 1425-a can interface with the RLC layer entity 1425-b, the MAC layer entity 1430-a can interface with the MAC layer entity 1430-b, the PHY layer entity 1435-a can interface with the PHY layer entity 1435-b, the UPAP inter-interface entity 1440-a can interface with the UPAP inter-interface entity 1440-b, and the layer interface entity 1445-a can interface with the layer interface entity 1445-b. In some embodiments, the high UPAP layer entity 1415-b can interface with the UPAP inter-interface entity 1440-b, and the low UPAP layer entity 1420-a can interface with the high UPAP layer entity 1415-a.

[0190] In some embodiments, an inter-UPAP interface can be used for communication between a high UPAP in UPF1403 and a low UPAP in DU1402 (or between two DUs). The inter-UPAP interface can carry the main UPAP header and / or one or more service headers. In some embodiments, the low UPAP can be programmed through the interface to parse the high UPAP header and correct, modify, or delete the header. Furthermore, or alternatively, the low UPAP can be programmed to parse the header and perform actions on them (e.g., prioritizing or scheduling). In some embodiments, the high UPAP can be used to perform end-to-end tasks, and the low UPAP can be used to perform tasks via a specific radio interface.

[0191] In one embodiment, a high UPAP layer entity 1415-b can provide a message to an inter-UPAP interface entity 1440-b, including a main header 1450, a high UPAP service header 1455, and a payload 1460. Upon receiving the message, the inter-UPAP interface entity 1440-b can insert an inter-UPAP header 1465 into the message and provide the message containing the inter-UPAP header 1465 to the inter-UPAP interface entity 1440-a. The inter-UPAP interface entity 1440-a can extract the inter-UPAP header 1465 and provide the message to a low UPAP layer entity 1420-b, which can then insert a low UPAP service header 1470 into the message. The low UPAP layer entity 1420-b can provide the message containing the low UPAP service header 1470 to the low UPAP layer entity 1420-a.

[0192] In some embodiments, the UPAP-to-UPAP header 1465 may include a node ID to enable DUs along the path to discover DU 1402, UPF 1403, and / or DUs along the path. Furthermore, or alternatively, the UPAP-to-UPAP header 1465 may encode instructions and / or measurements to and from DU 1402. In some embodiments, the UPAP-to-UPAP header 1465 may carry UPAP PDUs that have already been processed by a high UPAP, and these UPAP PDUs flow through the UPAP-to-UPAP interface. The UPAP-to-UPAP interface can distribute PDUs between a high UPAP and a low UPAP, or between two low UPAPs.

[0193] Figure 15 shows one embodiment of process flow 1500 supporting a user-programmable layer for wireless communication according to one or more aspects of the present disclosure. In some embodiments, process flow 1500 may implement one or more aspects of the present disclosure. In some embodiments, process flow 1500 may implement one or more aspects of Figures 1 to 14. For example, each component in Figure 15 may implement some or each of the aspects of the corresponding named components in Figures 1 to 14. Furthermore, logic unit 1505 may be an embodiment of logic unit 205-c as described with reference to Figure 2C, DU1510 may be an embodiment of network entity 105 and / or DU165 as described with reference to Figure 1, and / or network entity 105-c as described with reference to Figure 2C, UE1515 may be an embodiment of UE115-c as described with reference to Figure 2C, and / or UE115 as described with reference to Figure 1, or any combination thereof. In some embodiments, the process flow 1500 can be used when the layer architecture 1400 is employed and / or may represent a procedure performed by a device of the wireless communication system 200-c.

[0194] In some embodiments, process flow 1500 can be used to enable UE 1515 and logical unit 1505 to communicate messages including a main header and service headers (e.g., low UPAP service header and high UPAP service header), the service headers can be used to carry instructions and / or parameters, or both, to implement a QoS model (e.g., different service headers may be tailored to different QoS flows and may include parameter values ​​used to communicate information associated with those QoS flows). For example, in 1520, UE 1515 can send a UE data session establishment request to logical unit 1505 (e.g., via DU 1510). In 1525, UE 1515 can send a UE capability report to logical unit 1505. In 1530, DU 1530 can send a radio capability report to logical unit 1505. In some embodiments, the radio capability report can provide an indication of the capabilities of DU 1510, as well as its programmable API. At 1535, logical unit 1505 can perform the determination of data session constraints. At 1540, logical unit 1505 can establish one or more data sessions and UPAP with DU1510. At 1545, DU1510 can establish one or more DRBs with UE1515.

[0195] In 1550, data transmission can be performed between logical unit 1505 and UE 1515 (for example, via DU 1510). For example, logical unit 1505 can identify an IP packet (for example, received from an external network) and insert a main header and a high UPAP service header into that IP packet using a high UPAP layer entity established in logical unit 1505 (for example, high UPAP layer entity 1415-b as described in Figure 14). Logical unit 1505 can then provide DU 1510 with a message (for example, via an inter-UPAP interface as described herein) containing the main header, high UPAP service header, and IP packet. DU1510 can perform radio functions using low UPAP layer entities, RLC layer entities, MAC layer entities, and PHY layer entities (for example, low UPAP layer entities 1420-b, RLC layer entities 1425-b, MAC layer entities 1430-b, and PHY layer entities 1435-b, as described with reference to Figure 14), and can generate a second message to send to UE1515 based on a message received from logical unit 1505. DU1510 can send the second message to UE1515, and UE1515 can use the radio functions to identify the main header, service header, and IP packet.

[0196] Figure 16 shows one embodiment of process flow 1600 supporting a user-programmable layer for wireless communication according to one or more aspects of the present disclosure. In some embodiments, process flow 1600 may implement one or more aspects of the present disclosure. In some embodiments, process flow 1600 may implement one or more aspects of Figures 1 to 15. For example, each component in Figure 16 may implement some or each of the aspects of the components with corresponding names in Figures 1 to 15. Furthermore, the logical unit 1605 may be an embodiment of the logical units 205-a, 205-b, or 205-c as described with reference to Figures 2A to 2C; the network entity 1610 may be an embodiment of the network entity 105 and / or DU165 as described with reference to Figure 1, and / or an embodiment of the network entity 105-a, network entity 105-b, or network entity 105-c as described with reference to Figures 2A to 2C; the UE1615 may be an embodiment of the UE115-a, UE115-b, or UE115-c as described with reference to Figures 2A to 2C, and / or an embodiment of the UE115 as described with reference to Figure 1, or any combination thereof.

[0197] In 1620, the network entity 1610 may send a capability message to the logical unit 1605 indicating that the network entity 1610 supports instructions regarding services associated with the radio layer for wireless communication with one or more UEs (e.g., UE 1615). In some embodiments, the logical unit 1605 is a second network entity.

[0198] In 1625, the network entity 1610 can establish a data session with the logical unit 1605 associated with one of the UEs (e.g., UE1615) based on sending a capability message.

[0199] In 1630, the network entity 1610 can establish a data radio bearer with the UE 1615 based on the data session.

[0200] In 1635, the logical unit 1605 can send instructions to the network entity 1610 to perform radio functions associated with service with the UE, based on the data session.

[0201] In 1640, the network entity 1610 can execute commands at the wireless layer to perform its wireless functions.

[0202] In some embodiments, network entity 1610 may receive a first message (e.g., from logical unit 1605) including an instruction, a packet, and a header. Based on establishing a data radio bearer with UE 1615, network entity 1610 may send a second message including a first radio link control service data unit. In some such embodiments, the second radio link control service data unit may include a header and a response to the packet. Based on the second message, network entity 1610 may receive a third message (e.g., from UE 1615) including a second radio link control service data unit, the second radio link control service data unit including a header and a response to the packet. Network entity 1610 may embed a header in a fourth message, the fourth message including a response to the packet, and may send the fourth message (e.g., to logical unit 1605) based on an instruction. In some embodiments, this instruction may be executed after receiving the third message (e.g., and before sending the fourth message). In some embodiments, the fourth message includes a service header associated with the flow between UE1615 and logical unit 1605. In some such embodiments, the service header may include parameters based on the instruction.

[0203] In some embodiments, network entity 1610 may receive a first message (e.g., from logical unit 1605) containing instructions and packets. In some such embodiments, network entity 1610 may send a second message (e.g., to UE 1615) containing packets based on instructions to establish a data radio bearer with the UE. Furthermore, this instruction may be executed before sending the second message.

[0204] Figure 17 shows one embodiment of process flow 1700 supporting a user-programmable layer for wireless communication according to one or more aspects of the present disclosure. In some embodiments, process flow 1700 may implement one or more aspects of the present disclosure. In some embodiments, process flow 1700 may implement one or more aspects of Figures 1 to 16. For example, each component in Figure 17 may implement some or each of the aspects of the corresponding named components in Figures 1 to 16. Furthermore, the logical unit 1705 may be an embodiment of the logical units 205-a, 205-b, or 205-c as described with reference to Figures 2A to 2C; the network entity 1710 may be an embodiment of the network entity 105 and / or DU165 as described with reference to Figure 1, and / or an embodiment of the network entity 105-a, network entity 105-b, or network entity 105-c as described with reference to Figures 2A to 2C; the UE1715 may be an embodiment of the UE115-a, UE115-b, or UE115-c as described with reference to Figures 2A to 2C, and / or an embodiment of the UE115 as described with reference to Figure 1, or any combination thereof.

[0205] In 1720, the network entity 1710 can send capability messages to the logical unit 1705 indicating the services that the network entity 1710 supports.

[0206] In 1725, the network entity 1710 can establish a data session with the logical unit 1705 and associated with the flow between the logical unit 1705 and the UE 1715, based on sending a capability message.

[0207] In 1730, the network entity 1710 can establish a data radio bearer associated with the flow with the UE 1715 based on the data session.

[0208] In 1735, the logical unit 1705 can send a first message associated with a flow to the network entity 1710. In some embodiments, the first message may include a first header associated with a first layer based on a data session with the logical unit. In some embodiments, the first header may include an instruction that the first message should be processed by the network entity 1710 before generating a radio link control service data unit, and a second header may be based on the instruction that the first message should be processed by the network entity 1710. In some embodiments, the first header may include an identifier of the network entity 1710, instructions, measurements, information about the data session (e.g., instructions for a set of strategies or rules for performing energy saving), or any combination thereof. In some embodiments, the logical unit 1705 is a second network entity, a UPF, or both.

[0209] In some embodiments, the first message may include a main header and a first service header associated with a service. In some such embodiments, the second message may include a main header, a first service header, and a second service header associated with the radio functionality of the network entity. In some such embodiments, the logical unit 1705 may send a plurality of messages to the network entity 1710, each containing a first message and a service header associated with a service. The network entity 1710 may perform prioritization of the plurality of messages based on the corresponding service headers, and send the second message based on that prioritization. Furthermore, or alternatively, the network entity 1710 may modify the first service header based on instructions received from the second logical unit, and send the second message based on the modified first service header. Furthermore, or alternatively, the network entity 1710 may add a third service header to the second message based on instructions received from the second logical unit. In some embodiments, the first message includes a set of service headers, including a first service header, and the second message includes a subset of the set of service headers, including the first service header, where this subset of service headers does not include at least one service header from that set (for example, a service header may be removed).

[0210] In some embodiments, the first message may include a main header, a service header associated with the first layer, an instruction that the service header should be processed by the network entity 1710, an instruction to perform a radio function associated with the service with the UE 1715, or any combination thereof. In some embodiments, the instruction that the service header should be processed by the network entity 1710 may include an instruction to perform that processing before generating a service data unit associated with the radio link control layer, an instruction to insert the service header into the first message, or both. In some embodiments, the service header may include an identifier for the network entity 1710, a second instruction, a measurement, or any combination thereof.

[0211] In 1740, the network entity 1710 can generate an RLC SDU which includes a first header and a second header associated with the first layer based on one or more radio functions of the network entity.

[0212] In 1745, the network entity 1710 may transmit a second message via a data radio bearer, which includes a radio link control service data unit. In some embodiments, the second message may include a main header based on the first message.

[0213] At 1750, the network entity 1710 can send a third message to the logical unit 1705.

[0214] Figure 18 shows one embodiment of process flow 1800 supporting a user-plane programmable layer for wireless communication according to one or more aspects of the present disclosure. In some embodiments, process flow 1800 may implement one or more aspects of the present disclosure. In some embodiments, process flow 1800 may implement one or more aspects of Figures 1 to 17. For example, each component in Figure 18 may implement some or each of the aspects of the components with corresponding names in Figures 1 to 17. Furthermore, wireless devices 1805 and 1810 can each be an embodiment of a logic unit 205-a, 205-b, or 205-c as described with reference to Figures 2A to 2C, network entity 105 and / or DU165 as described with reference to Figure 1, and / or network entity 105-a, network entity 105-b, or network entity 105-c as described with reference to Figures 2A to 2C, UE115-a, UE115-b, or UE115-c as described with reference to Figures 2A to 2C, and / or UE115 as described with reference to Figure 1, or any combination thereof.

[0215] In 1815, the wireless device 1805 can generate a first service data unit which includes a first packet associated with the radio link control layer and a first main header relating to the first packet, which is associated with a first layer above the radio link control layer and a first service header relating to the first packet, which is associated with a service provided by one or more network entities in the network, where each of the first main header and the first service header is associated with a flow between the logical unit and the UE.

[0216] In 1820, the wireless device 1805 can generate a second service data unit associated with the radio link control layer, the second service data unit including a second packet, a second main header associated with the first layer, and a second service header relating to the second packet and associated with the service. In some embodiments, the second main header and the second service header, respectively, are associated with the flow between the logical unit and the UE. In some such embodiments, the first service header and the second service header are different from each other.

[0217] In 1825, the wireless device 1805 may output one or more messages, including a first service data unit and a second service data unit.

[0218] In embodiments where wireless device 1805 is a network entity and wireless device 1810 is a UE, wireless device 1805 can establish a data radio bearer with wireless device 1810. In some such embodiments, one or more messages are output by the network entity and are based on establishing a data radio bearer with wireless device 1810.

[0219] In some embodiments, the wireless device 1805 can obtain a first message (e.g., from a logical unit) including a first packet, a first main header, and a first service header, modify the first service header based on the first message, and generate a first service data unit based on the modified first header. In some embodiments, modifying the first service header may include updating a timestamp (e.g., a timestamp included by the first service header). In some embodiments, the wireless device 1805 can obtain a first message including a first packet, a first main header, a first service header, and a third service header associated with a second service. In such embodiments, the wireless device 1805 may remove the third service header when generating the first service data unit so that the first service data unit does not include the third service header. In some embodiments, the wireless device 1805 can obtain a first message including a first packet, a first main header, and a first service header. In such an embodiment, the wireless device 1805 may add a third service header when generating the first service data unit so that the first service data unit includes a third service header, and the first message does not include a third service header.

[0220] In some embodiments, the first service header, the second service header, or both may contain instructions. In some such embodiments, the instructions may indicate that an acknowledgment (e.g., ACK feedback) should be sent upon receipt of one or more messages, that packets associated with one or more messages should be sorted according to the arrangement indicated by the instructions, that packets associated with one or more messages should be discarded after a threshold time, that packets associated with one or more messages should be timestamped, or any combination thereof.

[0221] In some embodiments, the first service header includes a sorting timer, a sorting domain, an instruction to discard the first packet after the sorting timer expires, an instruction to send acknowledgment feedback for the first packet, or any combination thereof. In some embodiments, the first main header and the second main header each include data control flags, a header length, a sequence number, information associated with extended fields, or any combination thereof.

[0222] Figure 19 shows one embodiment of process flow 1900 supporting a user-plane programmable layer for wireless communication according to one or more aspects of the present disclosure. In some embodiments, process flow 1900 may implement one or more aspects of the present disclosure. In some embodiments, process flow 1900 may implement one or more aspects of Figures 1 to 18. For example, each component in Figure 19 may implement some or each of the aspects of the corresponding named components in Figures 1 to 18. Furthermore, wireless devices 1905 and 1910 can each be an embodiment of a logic unit 205-a, 205-b, or 205-c as described with reference to Figures 2A to 2C, a network entity 105 and / or DU165 as described with reference to Figure 1, and / or a network entity 105-a, network entity 105-b, or network entity 105-c as described with reference to Figures 2A to 2C, a UE115-a, UE115-b, or UE115-c as described with reference to Figures 2A to 2C, and / or a UE115 as described with reference to Figure 1, or any combination thereof.

[0223] In 1915, the wireless device 1910 can communicate with the wireless device 1905 and a first service data unit associated with the radio link control layer.

[0224] In 1920, the wireless device 1905 can derive from the first service data unit a first packet, a first main header relating to the first packet associated with a first layer above the radio link control layer, and a first service header relating to the first packet associated with a service provided by one or more network entities in the network. In some such embodiments, the first main header and the first service header, respectively, are associated with the flow between the logical unit and the UE.

[0225] In 1925, the wireless device 1905 may generate a second service data unit associated with the radio link control layer, which includes a second packet, a second main header, and a second service header associated with the service, each of which is associated with the flow between the logical unit and the UE. In some such embodiments, the second service header may be based on the first service header, and the second service header may be different from the first service header.

[0226] At 1930, the wireless device 1905 can communicate with the wireless device 1910 a second message, which includes a second service data unit.

[0227] In embodiments where wireless device 1905 is a network entity and wireless device 1910 is a UE, wireless device 1905 can establish a data radio bearer with wireless device 1910. In some such embodiments, one or more messages are output by the network entity and are based on establishing a data radio bearer with wireless device 1910.

[0228] In some embodiments, the first service header includes information about the first packet, a sorting timer, a sorting domain, an instruction to discard the first packet after the sorting timer expires, an instruction to send acknowledgment feedback for the first packet, or any combination thereof. In some embodiments, the first main header and the second main header may each include data control flags, a header length, a sequence number, information associated with extended fields, or any combination thereof.

[0229] Figure 20 shows a block diagram 2000 of device 2005 supporting a user-plane programmable layer for wireless communication according to one or more embodiments of the present disclosure. Device 2005 can be one embodiment of various forms of wireless devices as described herein. Device 2005 may include a receiver 2010, a transmitter 2015, and a communications manager 2020. Device 2005 may also include one or more processors. Each of these components can communicate with one another (for example, via one or more buses).

[0230] The receiver 2010 can provide means for acquiring (e.g., receiving, determining, identifying) information such as user data, control information, or any combination thereof, associated with various channels (e.g., control channels, data channels, information channels, channels associated with the protocol stack), including in-phase and quadrature (I / Q) samples, symbols, packets, protocol data units, and service data units. The information can be passed to other components of the device 2005. In some embodiments, the receiver 2010 may support acquiring information by receiving signals via one or more antennas. Furthermore, or alternatively, the receiver 2010 may support acquiring information by receiving signals via one or more wired (e.g., electrical, optical fiber) interfaces, wireless interfaces, or any combination thereof.

[0231] The transmitter 2015 can provide means for outputting (e.g., transmitting, providing, communicating, transmitting) information generated by other components of device 2005. For example, the transmitter 2015 can output information such as user data, control information, or any combination thereof, associated with various channels (e.g., control channel, data channel, information channel, channel associated with protocol stack) (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some embodiments, the transmitter 2015 may support outputting information by transmitting a signal via one or more antennas. Furthermore, or alternatively, the transmitter 2015 may support outputting information by transmitting a signal via one or more wired (e.g., electrical, optical fiber) interfaces, wireless interfaces, or any combination thereof. In some embodiments, the transmitter 2015 and receiver 2010 may be co-located in a transceiver that may include a modem or can be coupled to a modem.

[0232] The communication manager 2020, receiver 2010, transmitter 2015, or various combinations thereof, or various components thereof, can be embodiments of means for performing various aspects of a user-plane programmable layer for wireless communication, as described herein. For example, the communication manager 2020, receiver 2010, transmitter 2015, or various combinations thereof, or components thereof, can support methods for performing one or more of the functions described herein.

[0233] In some embodiments, the communications manager 2020, the receiver 2010, the transmitter 2015, or various combinations or components thereof may be implemented in hardware (e.g., in a communications management circuit). The hardware may include one or more processors, digital signal processors (DSPs), central processing units (CPUs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs) or other programmable logic devices, microcontrollers, individual gate or transistor logic, individual hardware components, or any combination thereof that are configured as means for performing or supporting the functions described herein. In some embodiments, one or more processors, and memory coupled to one or more processors, may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in memory by one or more processors).

[0234] Furthermore, or alternatively, in some embodiments, the communications manager 2020, receiver 2010, transmitter 2015, or various combinations or components thereof may be implemented in code executed by one or more processors (for example, as communications management software or firmware). When implemented in code executed by one or more processors, the functions of the communications manager 2020, receiver 2010, transmitter 2015, or various combinations or components thereof may be performed by a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices (for example, configured as means for performing or supporting means for performing the functions described in this disclosure).

[0235] In some embodiments, the communication manager 2020 can be configured to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting) using or in cooperation with the receiver 2010, the transmitter 2015, or both. For example, the communication manager 2020 can receive information from the receiver 2010 and transmit information to the transmitter 2015, or, by being integrated with the receiver 2010, the transmitter 2015, or both, can acquire information, output information, or perform various other operations as described herein.

[0236] The communications manager 2020 can support wireless communications in a network entity in accordance with embodiments such as those disclosed herein. For example, the communications manager 2020 can support, is configured to support, or can operate to support, means for a network entity to send a capability message from the network entity to a logical unit indicating that the network entity supports instructions for services associated with the radio layer for wireless communications with one or more UEs. The communications manager 2020 can support, is configured to support, or can operate to support, means for establishing a data session between the logical unit and one of the UEs based on the transmission of the capability message. The communications manager 2020 can support, is configured to support, or can operate to support, means for receiving instructions from the logical unit to perform radio functions associated with services with the UEs based on the data session. The communications manager 2020 can support, is configured to support, or can operate to support, means for performing instructions for performing radio functions at the radio layer.

[0237] Furthermore, or alternatively, the communications manager 2020 can support wireless communications in a network entity in accordance with embodiments such as those disclosed herein. For example, the communications manager 2020 can support, is configured to support, or is operable to support, means of sending capability messages to a logical unit indicating the services that the network entity supports. The communications manager 2020 can support, is configured to support, or is operable to support, means of establishing a data session with a logical unit and associated with a flow between the logical unit and the UE, based on sending capability messages. The communications manager 2020 can support, is configured to support, or is operable to support, means of establishing a data wireless bearer with the UE and associated with a flow, based on the data session with the logical unit. The communications manager 2020 can support, is configured to support, or is operable to support, means of receiving from a logical unit a first message associated with a flow, including a first header associated with a first layer, based on the data session with the logical unit. The communications manager 2020 is capable of supporting, configured to support, or operable to support, means for generating a radio link control service data unit, which includes a first header and a second header associated with a first layer based on one or more radio functions of a network entity. The communications manager 2020 is capable of supporting, configured to support, or operable to support, means for transmitting a second message, which includes the radio link control service data unit, via a data radio bearer.

[0238] Furthermore, or alternatively, the communications manager 2020 can support wireless communication in a logical unit in accordance with embodiments such as those disclosed herein. For example, the communications manager 2020 can support, is configured to support, or can operate to support, means for receiving capability messages indicating that a network entity supports instructions regarding services associated with the radio layer for wireless communication with the UE. The communications manager 2020 can support, is configured to support, or can operate to support, means for establishing a data session associated with a flow between the logical unit and the UE based on the capability message. The communications manager 2020 can support, is configured to support, or can operate to support, means for sending a first message associated with a flow, including a main header, a service header associated with a first layer, an instruction that the service header should be processed by a network entity, and instructions for performing radio functions associated with the service with the UE. Communication Manager 2020 is capable of supporting, configured to support, or operable to support, a means of receiving a second message that is associated with a flow and includes a main header based on the first message.

[0239] By including or configuring the communications manager 2020 in accordance with embodiments described herein, device 2005 (e.g., one or more processors controlling or coupled to receiver 2010, transmitter 2015, communications manager 2020, or a combination thereof) can support technologies for improved programmability and service adaptability, as well as for reducing at least some deployment overhead.

[0240] Figure 21 shows a block diagram 2100 of device 2105 supporting a user-plane programmable layer for wireless communication according to one or more embodiments of the present disclosure. Device 2105 may be an embodiment of device 2005 or any of the wireless device embodiments described herein. Device 2105 may include a receiver 2110, a transmitter 2115, and a communications manager 2120. Device 2105 may also include one or more processors. Each of these components can communicate with one another (for example, via one or more buses).

[0241] The receiver 2110 can provide means for acquiring (e.g., receiving, determining, identifying) information such as user data, control information, or any combination thereof, associated with various channels (e.g., control channels, data channels, information channels, channels associated with the protocol stack), including I / Q samples, symbols, packets, protocol data units, and service data units. The information can be passed to other components of device 2105. In some embodiments, the receiver 2110 may support acquiring information by receiving signals via one or more antennas. Furthermore, or alternatively, the receiver 2110 may support acquiring information by receiving signals via one or more wired (e.g., electrical, optical fiber) interfaces, wireless interfaces, or any combination thereof.

[0242] The transmitter 2115 can provide means for outputting (e.g., transmitting, providing, communicating, transmitting) information generated by other components of device 2105. For example, the transmitter 2115 can output information such as user data, control information, or any combination thereof, associated with various channels (e.g., control channel, data channel, information channel, channel associated with protocol stack) (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some embodiments, the transmitter 2115 may support outputting information by transmitting signals via one or more antennas. Furthermore, or alternatively, the transmitter 2115 may support outputting information by transmitting signals via one or more wired (e.g., electrical, optical fiber) interfaces, wireless interfaces, or any combination thereof. In some embodiments, the transmitter 2115 and receiver 2110 may be co-located in a transceiver that includes or can be coupled to a modem.

[0243] Device 2105, or its various components, can be an embodiment of means for performing various aspects of a user-plane programmable layer for wireless communication, as described herein. For example, the communication manager 2120 may include a capability message component 2125, an establishment component 2130, an instruction component 2135, a message component 2140, or any combination thereof. The communication manager 2120 can be an embodiment of various aspects of the communication manager 2020, as described herein. In some embodiments, the communication manager 2120, or its various components, can be configured to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting) using or in cooperation with the receiver 2110, the transmitter 2115, or both. For example, the communication manager 2120 can receive information from the receiver 2110 and transmit information to the transmitter 2115, or, by being integrated with the receiver 2110, the transmitter 2115, or both, it can acquire information, output information, or perform various other operations as described herein.

[0244] The communication manager 2120 can support wireless communication in a network entity in accordance with embodiments such as those disclosed herein. The capability message component 2125 can support, is configured to support, or is operable to support, means for a network entity to send a capability message from the network entity to a logical unit indicating that the network entity supports instructions for services associated with the radio layer for wireless communication with one or more UEs. The establishment component 2130 can support, is configured to support, or is operable to support, means for establishing a data session between the logical unit and one of the UEs based on sending a capability message. The instruction component 2135 can support, is configured to support, or is operable to support, means for receiving instructions from the logical unit to perform radio functions associated with services with the UE based on the data session. The instruction component 2135 can support, is configured to support, or is operable to support, means for performing instructions for performing radio functions at the radio layer.

[0245] Furthermore, or alternatively, the communication manager 2120 can support wireless communication in a network entity in accordance with embodiments such as those disclosed herein. The capability message component 2125 can support, is configured to support, or is operable to support, means for sending capability messages to a logical unit indicating the services that the network entity supports. The establishment component 2130 can support, is configured to support, or is operable to support, means for establishing a data session with a logical unit and associated with a flow between the logical unit and the UE, based on sending capability messages. The establishment component 2130 can support, is configured to support, or is operable to support, means for establishing a data wireless bearer with the UE and associated with a flow, based on the data session. The message component 2140 can support, is configured to support, or is operable to support, means for receiving a first message associated with a flow from a logical unit, including a first header associated with a first layer, based on the data session with the logical unit. The message component 2140 is capable of supporting, configured to support, or operable to support, means for generating a radio link control service data unit, which includes a first header and a second header associated with a first layer based on one or more radio functions of a network entity. The message component 2140 is capable of supporting, configured to support, or operable to support, means for transmitting a second message, which includes the radio link control service data unit, via a data radio bearer.

[0246] Furthermore, or alternatively, the communication manager 2120 can support wireless communication in the logical unit in accordance with embodiments such as those disclosed herein. The capability message component 2125 can support, is configured to support, or is operable to support, means for receiving capability messages indicating that a network entity supports instructions regarding services associated with the radio layer for wireless communication with the UE. The establishment component 2130 can support, is configured to support, or is operable to support, means for establishing a data session associated with a flow between the logical unit and the UE based on the capability message. The message component 2140 can support, is configured to support, or is operable to support, means for sending a first message associated with a flow, including a main header, a service header associated with a first layer, an instruction that the service header should be processed by a network entity, and instructions for performing radio functions associated with the service with the UE. The message component 2140 is associated with a flow and is capable of supporting, configured to support, or operable to support, a means of receiving a second message, which includes a main header based on the first message.

[0247] Figure 22 shows a block diagram 2200 of a communications manager 2220 supporting a user-plane programmable layer for wireless communication according to one or more embodiments of the present disclosure. The communications manager 2220 may be an embodiment of communications manager 2020, communications manager 2120, or any of both, as described herein. The communications manager 2220, or various components thereof, may be an embodiment of means for performing various embodiments of a user-plane programmable layer for wireless communication, as described herein. For example, the communications manager 2220 may include a capability message component 2225, an establishment component 2230, an instruction component 2235, a message component 2240, or any combination thereof. Each of these components may communicate with one another directly or indirectly (e.g., via one or more buses).

[0248] The communication manager 2220 can support wireless communication in a network entity according to embodiments such as those disclosed herein. The capability message component 2225 can support, is configured to support, or is operable to support, means for sending a capability message from the network entity to a logical unit indicating that the network entity supports instructions for services associated with the radio layer for wireless communication with one or more UEs. The establishment component 2230 can support, is configured to support, or is operable to support, means for establishing a data session between the logical unit and one of the UEs based on sending a capability message. The instruction component 2235 can support, is configured to support, or is operable to support, means for receiving instructions from the logical unit to perform radio functions associated with services with the UE based on the data session. In some embodiments, the instruction component 2235 can support, is configured to support, or is operable to support, means for performing instructions for performing radio functions at the radio layer.

[0249] In some embodiments, the message component 2240 is capable of supporting, configured to support, or operable to support, means for receiving a first message, which includes an instruction, a packet, and a header. In some embodiments, the establishment component 2230 is capable of supporting, configured to support, or operable to support, means for establishing a data radio bearer with the UE based on a data session. In some embodiments, the message component 2240 is capable of supporting, configured to support, or operable to support, means for transmitting a second message, which includes a first radio link control service data unit, based on establishing a data radio bearer with the UE, the first radio link control service data unit includes a packet and a header. In some embodiments, the message component 2240 is capable of supporting, configured to support, or operable to support, means for receiving a third message, which includes a second radio link control service data unit, based on the second message, the second radio link control service data unit includes a header and a response to the packet. In some embodiments, the message component 2240 is capable of supporting, configured to support, or operable to support, means for embedding a header in a fourth message, the fourth message including a response to a packet. In some embodiments, the message component 2240 is capable of supporting, configured to support, or operable to support, means for sending a fourth message based on an instruction, the instruction being executed after receiving a third message.

[0250] In some embodiments, the fourth message includes a service header associated with the flow between the UE and the logical unit. In some embodiments, this service header includes parameters based on the instruction.

[0251] In some embodiments, the message component 2240 is capable of supporting, configured to support, or operable to support, means for receiving a first message, including an instruction and a packet, and the execution of the instruction is based on the first message. In some embodiments, the establishment component 2230 is capable of supporting, configured to support, or operable to support, means for establishing a data radio bearer with the UE based on a data session. In some embodiments, the message component 2240 is capable of supporting, configured to support, or operable to support, means for sending a second message, including a packet, based on establishing a data radio bearer with the UE and an instruction, and the instruction is executed before sending the second message.

[0252] In some embodiments, the logical unit includes a second network entity.

[0253] Furthermore, or alternatively, the communication manager 2220 can support wireless communication in a network entity in accordance with embodiments such as those disclosed herein. In some embodiments, the capability message component 2225 can support, is configured to support, or is operable to support, means for sending capability messages to a logical unit indicating the services that the network entity supports. In some embodiments, the establishment component 2230 can support, is configured to support, or is operable to support, means for establishing a data session with a logical unit and associated with a flow between the logical unit and the UE, based on sending capability messages. In some embodiments, the establishment component 2230 can support, is configured to support, or is operable to support, means for establishing a data wireless bearer with the UE and associated with a flow, based on the data session. The message component 2240 can support, is configured to support, or is operable to support, means for receiving a first message associated with a flow from a logical unit, based on a data session with the logical unit, including a first header associated with a first layer. In some embodiments, the message component 2240 is capable of supporting, configured to support, or operable to support, means for generating a radio link control service data unit, which includes a first header and a second header associated with a first layer based on one or more radio functions of a network entity. In some embodiments, the message component 2240 is capable of supporting, configured to support, or operable to support, means for transmitting a second message, which includes the radio link control service data unit, via a data radio bearer.

[0254] In some embodiments, the first message includes a main header and a first service header associated with the service. In some embodiments, the second message includes a main header, a first service header, and a second service header associated with the wireless functionality of the network entity.

[0255] In some embodiments, the message component 2240 is capable of supporting, configured to support, or operable to support, means for receiving a set of multiple messages from a logical unit, each of which includes a service header associated with a service. In some embodiments, the message component 2240 is capable of supporting, configured to support, or operable to support, means for performing prioritization of the set of multiple messages based on corresponding service headers, and sending a second message is based on that prioritization.

[0256] In some embodiments, the message component 2240 is capable of supporting, configured to support, or operable to support means for modifying the first service header based on instructions received from a second logical unit, and the transmission of the second message is based on the modified first service header.

[0257] In some embodiments, the first message includes a set of service headers, including a first service header, and the message component 2240 is capable of supporting, configured to support, or operable to support, means of adding a third service header to the second message based on an instruction received from a second logical unit.

[0258] In some embodiments, the first message includes a set of service headers, which includes a first service header. In some embodiments, the second message includes a subset of the set of service headers, which includes the first service header. In some embodiments, the subset of the set of service headers does not include at least one service header from that set.

[0259] In some embodiments, the first header includes an instruction that the first message should be processed by a network entity before generating a wireless link control service data unit. In some embodiments, the second header is based on the instruction that the first message should be processed by a network entity.

[0260] In some embodiments, the first header includes an identifier for a network entity, instructions, measurements, information about a data session, or any combination thereof.

[0261] In some embodiments, the logical unit includes a second network entity, a user plane function, or both.

[0262] Furthermore, or alternatively, the communication manager 2220 can support wireless communication in the logical unit according to embodiments such as those disclosed herein. In some embodiments, the capability message component 2225 can support, is configured to support, or is operable to support, means for receiving capability messages indicating that a network entity supports instructions regarding services associated with the radio layer for wireless communication with the UE. In some embodiments, the establishment component 2230 can support, is configured to support, or is operable to support, means for establishing a data session associated with a flow between the logical unit and the UE based on the capability message. In some embodiments, the message component 2240 can support, is configured to support, or is operable to support, means for sending a first message associated with a flow, including a main header, a service header associated with a first layer, an instruction that the service header should be processed by a network entity, and instructions for performing radio functions associated with the service with the UE. In some embodiments, the message component 2240 is associated with a flow and is capable of, configured to, or operable to support, a means of receiving a second message, which includes a main header based on a first message.

[0263] In some embodiments, the instruction that a service header should be processed by a network entity includes an instruction to perform that processing before generating a service data unit associated with the radio link control layer, an instruction to insert a service header into a first message, or both.

[0264] In some embodiments, the service header includes a network entity identifier, a second instruction, a measurement, or any combination thereof.

[0265] In some embodiments, the logical unit includes a second network entity, a user plane function, or both.

[0266] Figure 23 shows a diagram of a system 2300 including a device 2305 that supports a user-plane programmable layer for wireless communication, according to one or more embodiments of the present disclosure. Device 2305 may be an embodiment of device 2005, device 2105, or a wireless device as described herein, or may include components thereof. Device 2305 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communications manager 2320, a transceiver 2310, an antenna 2315, a memory 2325, a code 2330, and a processor 2335. These components may communicate electronically or be coupled (e.g., operably, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 2340).

[0267] The transceiver 2310 can support bidirectional communication via a wired link, a wireless link, or both, as described herein. In some embodiments, the transceiver 2310 may include a wired transceiver and be able to communicate bidirectionally with another wired transceiver. Furthermore, or alternatively, in some embodiments, the transceiver 2310 may include a wireless transceiver and be able to communicate bidirectionally with another wireless transceiver. In some embodiments, the device 2305 may include one or more antennas 2315 that may be capable of transmitting or receiving wireless transmissions (e.g., simultaneously). The transceiver 2310 may also include a modem for modulating a signal, providing to transmit the modulated signal (e.g., by one or more antennas 2315, by a wired transmitter), receiving the modulated signal (e.g., from one or more antennas 2315, from a wired receiver), and demodulating the signal. In some implementations, the transceiver 2310 may include one or more interfaces coupled to one or more antennas 2315, configured to support various receiving or acquiring operations, or one or more interfaces coupled to one or more antennas 2315, configured to support various transmitting or output operations, or a combination thereof. In some implementations, the transceiver 2310 may include, or be configured to be coupled with, one or more processor or memory components capable of operating to perform or support operations based on received or acquired information or signals, or to generate information or other signals for transmission or other output, or for any combination thereof.In some implementations, the transceiver 2310, or the transceiver 2310 and one or more antennas 2315, or the transceiver 2310 and one or more antennas 2315 and one or more processor or memory components (e.g., processor 2335, or memory 2325, or both) can be included within a chip or chip assembly installed within the device 2305. In some examples, the transceiver can 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).

[0268] The memory 2325 can include RAM and ROM. When executed by the processor 2335, the memory 2325 can store computer-readable computer-executable code 2330 that includes instructions to cause the device 2305 to perform the various functions described herein. The code 2330 can be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. In some cases, the code 2330 may not be directly executable by the processor 2335 and can cause a computer to perform the functions described herein when (e.g., compiled and executed). In some cases, the memory 2325 can include a BIOS that can control basic hardware or software operations, such as interactions with peripheral components or peripheral devices, among other things.

[0269] The processor 2335 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, ASICs, CPUs, FPGAs, microcontrollers, programmable logic devices, individual gate or transistor logic, individual hardware components, or any combination thereof). In some cases, the processor 2335 may be configured to operate a memory array using a memory controller. In some other cases, a memory controller may be incorporated within the processor 2335. The processor 2335 may be configured to execute computer-readable instructions stored in memory (e.g., memory 2325) to cause device 2305 to perform various functions (e.g., functions or tasks supporting a user-plane programmable layer for wireless communication). For example, device 2305, or components of device 2305, may include the processor 2335 and memory 2325 coupled to the processor 2335, and the processor 2335 and memory 2325 are configured to perform various functions described herein. Processor 2335 can be an embodiment 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 the functions of device 2305 (e.g., by executing code 2330). Processor 2335 can be one or more of any suitable processors capable of executing scripts or instructions of one or more software programs stored within device 2305 (e.g., in memory 2325). In some implementations, processor 2335 can be a component of a processing system. A processing system may refer to a system or set of machines or components that receive inputs, process those inputs, and produce a set of outputs (which can be passed to other systems or components of device 2305, for example).For example, the processing system of device 2305 may refer to a system that includes various other components or sub-components of device 2305, such as processor 2335, or transceiver 2310, or communication manager 2320, or other combinations of components of device 2305. The processing system of device 2305 can interface with other components of device 2305 and process information (such as input or signals) received from other components, or output information to other components. For example, the chip or modem of device 2305 may include a processing system and one or more interfaces for outputting information, or for acquiring information, or for both. The one or more interfaces can be implemented, among other implementations, as a first interface configured to output information, and a second interface configured to acquire information, or as the same interface configured to output information and to acquire information, or may include such interfaces. In some implementations, the one or more interfaces may refer to an interface between the processing system of the chip or modem and the transmitter such that device 2305 can transmit information output from the chip or modem. Further, or alternatively, in some implementations, the one or more interfaces may refer to an interface between the processing system of the chip or modem and the receiver such that device 2305 can acquire an information or signal input and pass that information to the processing system. Those skilled in the art will readily recognize that the first interface can also acquire an information or signal input, and the second interface can also output an information or signal output.

[0270] In some embodiments, bus 2340 can support (e.g., internal) communications of the protocol layer of the protocol stack. In some embodiments, bus 2340 can support communications associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack), which may include communications performed within a component of device 2305 or between various components of device 2305, which may be located together or in different locations (for example, device 2305 may refer to a system in which one or more of the communications manager 2320, transceiver 2310, memory 2325, code 2330, and processor 2335 may be located within one of the various components or divided among the various components).

[0271] In some embodiments, the communications manager 2320 can manage various modes of communication with the core network 130 (for example, via one or more wired or wireless backhaul links). For example, the communications manager 2320 can manage the transfer of data communications relating to one or more client devices, such as UEs 115. In some embodiments, the communications manager 2320 can manage communication with other network entities 105 and may include a controller or scheduler for coordinating with other network entities 105 to control communication with the UEs 115. In some embodiments, the communications manager 2320 can support an X2 interface within the framework of LTE / LTE-A wireless communications network technology to provide communication between network entities 105.

[0272] The communication manager 2320 can support wireless communication in a network entity in accordance with embodiments such as those disclosed herein. For example, the communication manager 2320 can support, is configured to support, or can operate to support, means for the network entity to send a capability message from the network entity to a logical unit indicating that the network entity supports instructions for services associated with the radio layer for wireless communication with one or more UEs. The communication manager 2320 can support, is configured to support, or can operate to support, means for establishing a data session between the logical unit and one of the UEs based on the transmission of the capability message. The communication manager 2320 can support, is configured to support, or can operate to support, means for receiving instructions from the logical unit to perform radio functions associated with services with the UE based on the data session. The communication manager 2320 can support, is configured to support, or can operate to support, means for performing instructions for performing radio functions at the radio layer.

[0273] Furthermore, or alternatively, the communications manager 2320 can support wireless communications in a network entity in accordance with embodiments such as those disclosed herein. For example, the communications manager 2320 can support, is configured to support, or is operable to support, means of sending capability messages to a logical unit indicating the services that the network entity supports. The communications manager 2320 can support, is configured to support, or is operable to support, means of establishing a data session with a logical unit and associated with a flow between the logical unit and the UE, based on sending capability messages. The communications manager 2320 can support, is configured to support, or is operable to support, means of establishing a data wireless bearer with the UE and associated with a flow, based on the data session with the logical unit. The communications manager 2320 can support, is configured to support, or is operable to support, means of receiving from a logical unit a first message associated with a flow, including a first header associated with a first layer, based on the data session with the logical unit. The communications manager 2320 is capable of supporting, configured to support, or operable to support, means for generating a radio link control service data unit, which includes a first header and a second header associated with a first layer based on one or more radio functions of a network entity. The communications manager 2320 is capable of supporting, configured to support, or operable to support, means for transmitting a second message, which includes the radio link control service data unit, via a data radio bearer.

[0274] Furthermore, or alternatively, the communications manager 2320 can support wireless communication in a logical unit in accordance with embodiments such as those disclosed herein. For example, the communications manager 2320 can support, is configured to support, or is operable to support, means for receiving capability messages indicating that a network entity supports instructions regarding services associated with the radio layer for wireless communication with the UE. The communications manager 2320 can support, is configured to support, or is operable to support, means for establishing a data session associated with a flow between the logical unit and the UE based on the capability message. The communications manager 2320 can support, is configured to support, or is operable to support, means for sending a first message associated with a flow, including a main header, a service header associated with a first layer, an instruction that the service header should be processed by a network entity, and instructions for performing radio functions associated with the service with the UE. The communication manager 2320 is capable of supporting, configured to support, or operable to support, a means of receiving a second message associated with a flow, which includes a main header based on the first message.

[0275] By including or configuring the communications manager 2320 according to embodiments described herein, the device 2305 can support technologies for improved programmability and service adaptability, as well as for reducing at least some deployment overhead.

[0276] In some embodiments, the communication manager 2320 may be configured to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting) using or in cooperation with the transceiver 2310, one or more antennas 2315 (e.g., where applicable), or any combination thereof. Although the communication manager 2320 is shown as a separate component, in some embodiments, one or more functions described with reference to the communication manager 2320 may also be supported or performed by the transceiver 2310, processor 2335, memory 2325, code 2330, or any combination thereof. For example, code 2330 may include instructions executable by the processor 2335 to cause device 2305 to perform various aspects of the user-plane programmable layer for wireless communication, as described herein, or the processor 2335 and memory 2325 may be configured to perform or support such operations.

[0277] Figure 24 shows a block diagram 2400 of device 2405 supporting a user-plane programmable layer for wireless communication according to one or more embodiments of the present disclosure. Device 2405 may be one embodiment of various forms of wireless devices as described herein. Device 2405 may include a receiver 2410, a transmitter 2415, and a communications manager 2420. Device 2405 may also include one or more processors. Each of these components can communicate with one another (for example, via one or more buses).

[0278] The receiver 2410 can provide means for receiving information such as packets, user data, control information, or any combination thereof, associated with various information channels (e.g., control channels, data channels, information channels related to the user plane programmable layer for wireless communication). The information can be passed to other components of device 2405. The receiver 2410 can utilize a single antenna or a set of multiple antennas.

[0279] The transmitter 2415 can provide means for transmitting signals generated by other components of device 2405. For example, the transmitter 2415 can transmit information such as packets, user data, control information, or any combination thereof, associated with various information channels (e.g., control channels, data channels, information channels related to the user plane programmable layer for wireless communication). In some embodiments, the transmitter 2415 can be co-located with the receiver 2410 within the transceiver module. The transmitter 2415 can utilize a single antenna or a set of multiple antennas.

[0280] The communication manager 2420, receiver 2410, transmitter 2415, or various combinations thereof, or various components thereof, can be embodiments of means for performing various aspects of a user-plane programmable layer for wireless communication, as described herein. For example, the communication manager 2420, receiver 2410, transmitter 2415, or various combinations thereof, or components thereof, can support methods for performing one or more of the functions described herein.

[0281] In some embodiments, the communication manager 2420, the receiver 2410, the transmitter 2415, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include one or more processors, DSPs, CPUs, ASICs, FPGAs or other programmable logic devices, microcontrollers, individual gate or transistor logic, individual hardware components, or any combination thereof that are configured as means for performing or supporting the functions described herein. In some embodiments, one or more processors, and memory coupled to one or more processors, may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in memory by one or more processors).

[0282] Furthermore, or alternatively, in some embodiments, the communications manager 2420, receiver 2410, transmitter 2415, or various combinations or components thereof may be implemented in code executed by one or more processors (for example, as communications management software or firmware). When implemented in code executed by one or more processors, the functions of the communications manager 2420, receiver 2410, transmitter 2415, or various combinations or components thereof may be performed by a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices (for example, configured as means for performing or supporting means for performing the functions described herein).

[0283] In some embodiments, the communication manager 2420 can be configured to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting) using or in cooperation with the receiver 2410, the transmitter 2415, or both. For example, the communication manager 2420 can receive information from the receiver 2410 and transmit information to the transmitter 2415, or, by being integrated with the receiver 2410, the transmitter 2415, or both, can acquire information, output information, or perform various other operations as described herein.

[0284] The communication manager 2420 can support wireless communication in accordance with embodiments such as those disclosed herein. For example, the communication manager 2420 can support, is configured to support, or can operate to support, means for generating a first service data unit which includes a first packet associated with the wireless link control layer and a first main header relating to the first packet, which is associated with the first packet and which is associated with a service provided by one or more network entities in the network, with each of the first main header and the first service header being associated with a flow between the logical unit and the UE. The communication manager 2420 is capable of supporting, configured to support, or operable to support means for generating a second service data unit associated with the radio link control layer, the second service data unit comprising a second packet, a second main header associated with the first layer, and a second service header relating to the second packet associated with the service, the second main header and the second service header each associated with the flow between the logical unit and the UE, and the first service header and the second service header being distinct from each other. The communication manager 2420 is capable of supporting, configured to support, or operable to support means for outputting one or more messages comprising the first service data unit and the second service data unit.

[0285] Furthermore, or alternatively, the communications manager 2420 can support wireless communications in accordance with embodiments such as those disclosed herein. For example, the communications manager 2420 can support, is configured to support, or is operable to support, means for communicating a first message, including a first service data unit associated with a radio link control layer. The communications manager 2420 can support, is configured to support, or is operable to support, means for deriving from the first service data unit a first packet, a first main header relating to the first packet associated with a first layer above the radio link control layer, and a first service header relating to a service provided by one or more network entities in the network, each of which is associated with a flow between a logical unit and a UE. The communication manager 2420 is capable of supporting, configured to support, or operable to support means for generating a second service data unit associated with the radio link control layer, which includes a second packet, a second main header, and a second service header associated with the service, each of which is associated with a flow between a logical unit and the UE, and the second service header is based on and different from the first service header. The communication manager 2420 is capable of supporting, configured to support, or operable to support means for communicating a second message including the second service data unit.

[0286] By including or configuring the communications manager 2420 in accordance with embodiments such as those described herein, the device 2405 (e.g., one or more processors controlling or coupled to the receiver 2410, transmitter 2415, communications manager 2420, or a combination thereof) can support technologies for improved programmability and service adaptability, as well as for reducing at least some deployment overhead.

[0287] Figure 25 shows a block diagram 2500 of device 2505 supporting a user-plane programmable layer for wireless communication according to one or more embodiments of the present disclosure. Device 2505 may be an embodiment of device 2405 or any other embodiment of a wireless device as described herein. Device 2505 may include a receiver 2510, a transmitter 2515, and a communications manager 2520. Device 2505 may also include one or more processors. Each of these components can communicate with one another (for example, via one or more buses).

[0288] The receiver 2510 can provide means for receiving information such as packets, user data, control information, or any combination thereof, associated with various information channels (e.g., control channels, data channels, information channels related to the user plane programmable layer for wireless communication). The information can be passed to other components of device 2505. The receiver 2510 can utilize a single antenna or a set of multiple antennas.

[0289] The transmitter 2515 can provide means for transmitting signals generated by other components of the device 2505. For example, the transmitter 2515 can transmit information such as packets, user data, control information, or any combination thereof, associated with various information channels (e.g., control channels, data channels, information channels associated with the user plane programmable layer for wireless communication). In some embodiments, the transmitter 2515 can be co-located with the receiver 2510 within a transceiver module. The transmitter 2515 can utilize a single antenna or a set of multiple antennas.

[0290] The device 2505, or its various components, can be an example of means for performing various aspects of a user plane programmable layer for wireless communication as described herein. For example, the communication manager 2520 can include a service data unit generator 2525, a message component 2530, a derivation component 2535, or any combination thereof. The communication manager 2520 can be an example of the various aspects of the communication manager 2420 as described herein. In some embodiments, the communication manager 2520, or its various components, can be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or in cooperation with the receiver 2510, the transmitter 2515, or both. For example, the communication manager 2520 can receive information from the receiver 2510 and transmit information to the transmitter 2515, or can be integrated in combination with the receiver 2510, the transmitter 2515, or both to obtain information, output information, or perform various other operations as described herein.

[0291] The communications manager 2520 can support wireless communications according to embodiments such as those disclosed herein. The service data unit generator 2525 is capable of supporting, configured to support, or operable to support means for generating a first service data unit associated with a radio link control layer, which includes a first packet, a first main header relating to the first packet and associated with a first layer above the radio link control layer, and a first service header relating to the first packet and associated with a service provided by one or more network entities in the network, each of which is associated with a flow between a logical unit and a UE. The service data unit generator 2525 is capable of supporting, configured to support, or operable to support means for generating a second service data unit associated with the radio link control layer, the second service data unit comprising a second packet, a second main header associated with the first layer, and a second service header relating to the second packet associated with the service, the second main header and the second service header each associated with the flow between the logical unit and the UE, and the first service header and the second service header being distinct from each other. The message component 2530 is capable of supporting, configured to support, or operable to support means for outputting one or more messages comprising the first service data unit and the second service data unit.

[0292] Furthermore, or alternatively, the communications manager 2520 can support wireless communications in accordance with embodiments such as those disclosed herein. The message component 2530 is capable of supporting, configured to support, or operable to support, means for communicating a first message, including a first service data unit associated with a radio link control layer. The derivation component 2535 is capable of supporting, configured to support, or operable to support, means for deriving from the first service data unit a first packet, a first main header relating to the first packet associated with a first layer above the radio link control layer, and a first service header relating to a service provided by one or more network entities in the network, each of which is associated with a flow between a logical unit and a UE. The service data unit generator 2525 is associated with the radio link control layer and is capable of supporting, configured to support, or operable to support, means for generating a second service data unit, which includes a second packet, a second main header, and a second service header associated with a service, each of which is associated with a flow between a logical unit and a UE, the second service header being based on the first service header, and the second service header being different from the first service header. The message component 2530 is capable of supporting, configured to support, or operable to support, means for communicating a second message, which includes a second service data unit.

[0293] Figure 26 shows a block diagram 2600 of a communications manager 2620 supporting a user-plane programmable layer for wireless communication according to one or more embodiments of the present disclosure. The communications manager 2620 may be an embodiment of communications manager 2420, communications manager 2520, or any of both, as described herein. The communications manager 2620, or various components thereof, may be an embodiment of means for performing various embodiments of a user-plane programmable layer for wireless communication, as described herein. For example, the communications manager 2620 may include a service data unit generator 2625, a message component 2630, a derivation component 2635, an establishment component 2640, a message generator 2645, an instruction execution component 2650, or any combination thereof. Each of these components may communicate with one another directly or indirectly (e.g., via one or more buses).

[0294] The communications manager 2620 can support wireless communications according to embodiments such as those disclosed herein. The service data unit generator 2625 is capable of supporting, configured to support, or operable to support, means for generating a first service data unit associated with a radio link control layer, which includes a first packet, a first main header relating to the first packet and associated with a first layer above the radio link control layer, and a first service header relating to the first packet and associated with a service provided by one or more network entities in the network, each of which is associated with a flow between a logical unit and a UE. In some embodiments, the service data unit generator 2625 is capable of supporting, configured to support, or operable to support means for generating a second service data unit associated with the radio link control layer, the second service data unit comprising a second packet, a second main header associated with the first layer, and a second service header relating to the second packet associated with the service, the second main header and the second service header each associated with the flow between the logical unit and the UE, and the first service header and the second service header being distinct from each other. The message component 2630 is capable of supporting, configured to support, or operable to support means for outputting one or more messages comprising a first service data unit and a second service data unit.

[0295] In some embodiments, the establishment component 2640 is capable of supporting, configured to support, or operable to support means for establishing a data radio bearer with the UE, and one or more messages are output by the network entity based on establishing a data radio bearer with the UE.

[0296] In some embodiments, the establishment component 2640 is capable of supporting, configured to support, or operable to support means for establishing a network entity and a data radio bearer, and one or more messages are output by the UE based on establishing a network entity and a data radio bearer.

[0297] In some embodiments, the message component 2630 is capable of supporting, configured to support, or operable to support means for obtaining a first message, which includes a first packet, a first main header, and a first service header. In some embodiments, the message generator 2645 is capable of supporting, configured to support, or operable to support means for modifying a first service header based on the first message, and a first service data unit is generated based on the modified first service header.

[0298] In some embodiments, modifying the first service header includes updating the timestamp.

[0299] In some embodiments, the message component 2630 can, is configured to, or can operate to support means for obtaining a first message comprising a first packet, a first main header, a first service header, and a third service header associated with a second service. In some embodiments, the message generator 2645 can, is configured to, or can operate to support means for deleting a third service header when generating a first service data unit such that the first service data unit does not include the third service header.

[0300] In some embodiments, the message component 2630 can, is configured to, or is operable to support means for obtaining a first message, which includes a first packet, a first main header, and a first service header. In some embodiments, the message generator 2645 can, is configured to, or is operable to support means for adding a third service header when generating a first service data unit, such that the first service data unit includes a third service header, and the first message does not include a third service header.

[0301] In some embodiments, the first service header, the second service header, or both include instructions.

[0302] In some embodiments, the instructions indicate that an acknowledgment should be sent upon receipt of one or more messages, that packets associated with one or more messages should be sorted according to the arrangement indicated by the instructions, that packets associated with one or more messages should be discarded after a threshold time, that packets associated with one or more messages should be timestamped, or any combination thereof.

[0303] In some embodiments, the first service header includes a sorting timer, a sorting domain, an instruction to discard the first packet after the sorting timer has expired, an instruction to send acknowledgment feedback for the first packet, or any combination thereof.

[0304] In some embodiments, the first main header and the second main header each include data control flags, header length, sequence number, information associated with extended fields, or any combination thereof.

[0305] Furthermore, or alternatively, the communication manager 2620 can support wireless communication according to embodiments such as those disclosed herein. In some embodiments, the message component 2630 can support, is configured to support, or is operable to support, means for communicating a first message, which includes a first service data unit associated with a radio link control layer. The derivation component 2635 can support, is configured to support, or is operable to support, means for deriving from the first service data unit a first packet, a first main header relating to the first packet associated with a first layer above the radio link control layer, and a first service header relating to a service provided by one or more network entities in the network, each of which is associated with a flow between a logical unit and a UE. In some embodiments, the service data unit generator 2625 is capable of supporting, configured to support, or operable to support means for generating a second service data unit associated with the radio link control layer, which includes a second packet, a second main header, and a second service header associated with the service, each of which is associated with a flow between the logical unit and the UE, and the second service header is based on and different from the first service header. In some embodiments, the message component 2630 is capable of supporting, configured to support, or operable to support means for communicating a second message including the second service data unit.

[0306] In some embodiments, the establishment component 2640 is capable of supporting, configured to support, or operable to support means for establishing a data radio bearer with the UE, based on a first message being communicated and a second message being output by a network entity for establishing a data radio bearer with the UE.

[0307] In some embodiments, the establishment component 2640 is capable of supporting, configured to support, or operable to support means for establishing a network entity and a data radio bearer, based on a first message being communicated and a second message being output by the UE for establishing a network entity and a data radio bearer.

[0308] In some embodiments, the first service header includes instructions, and the instruction execution component 2650 is capable of supporting, configured to support, or operable to support means for executing instructions, and generating a second service data unit is based on the instructions.

[0309] In some embodiments, the first service header includes information about the first packet, a sorting timer, a sorting domain, an instruction to discard the first packet after the sorting timer has expired, an instruction to send acknowledgment feedback for the first packet, or any combination thereof.

[0310] Figure 27 shows a diagram of a system 2700 including a device 2705 that supports a user-plane programmable layer for wireless communication according to one or more embodiments of the present disclosure. Device 2705 may be an embodiment of device 2405, device 2505, or a wireless device as described herein, or may include components thereof. Device 2705 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communications manager 2720, an I / O controller 2710, a transceiver 2715, an antenna 2725, a memory 2730, a code 2735, and a processor 2740. These components may communicate electronically or be coupled (e.g., operably, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 2745).

[0311] The I / O controller 2710 can manage input and output signals related to device 2705. The I / O controller 2710 can also manage peripherals not integrated into device 2705. In some cases, the I / O controller 2710 may represent a physical connection or port to an external peripheral. In some cases, the I / O controller 2710 may utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or another known operating system. Furthermore, or alternatively, the I / O controller 2710 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller 2710 may be implemented as part of a processor, such as processor 2740. In some cases, the user can interact with the device 2705 via the I / O controller 2710 or via hardware components controlled by the I / O controller 2710.

[0312] In some cases, device 2705 may include a single antenna 2725. However, in some other cases, device 2705 may have two or more antennas 2725 that may be capable of simultaneously transmitting or receiving multiple wireless transmissions. Transceiver 2715 can communicate bidirectionally via one or more antennas 2725, a wired link, or a wireless link, as described herein. For example, transceiver 2715 may represent a wireless transceiver that can communicate bidirectionally with another wireless transceiver. Transceiver 2715 may also include a modem for modulating packets, providing those modulated packets to one or more antennas 2725 for transmission, and demodulating packets received from one or more antennas 2725. The transceiver 2715, or the transceiver 2715 and one or more antennas 2725, may be an embodiment of the transmitter 2415, transmitter 2515, receiver 2410, receiver 2510, or any combination thereof, or components thereof, as described herein.

[0313] Memory 2730 may include RAM and ROM. Memory 2730 can store computer-readable computer-executable code 2735, which, when executed by processor 2740, causes device 2705 to perform various functions described herein. Code 2735 may be stored in a non-temporary computer-readable medium, such as system memory or another type of memory. In some cases, code 2735 may not be directly executable by processor 2740, but (for example, when compiled and executed) can cause the computer to perform the functions described herein. In some cases, memory 2730 may include a BIOS that can control basic hardware or software operations, including, among many others, interactions with peripheral components or peripheral devices.

[0314] The processor 2740 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, individual gate or transistor logic components, individual hardware components, or any combination thereof). In some cases, the processor 2740 may be configured to operate a memory array using a memory controller. In some other cases, a memory controller may be incorporated within the processor 2740. The processor 2740 may be configured to execute computer-readable instructions stored in memory (e.g., memory 2730) to cause device 2705 to perform various functions (e.g., functions or tasks supporting a user-plane programmable layer for wireless communication). For example, device 2705, or components of device 2705, may include the processor 2740 and memory 2730 coupled to or to the processor 2740, and the processor 2740 and memory 2730 are configured to perform various functions described herein.

[0315] The communication manager 2720 can support wireless communication in accordance with embodiments such as those disclosed herein. For example, the communication manager 2720 can support, is configured to support, or can operate to support, means for generating a first service data unit which includes a first packet associated with the radio link control layer and a first main header relating to the first packet and which is associated with a first layer above the radio link control layer and which is associated with a service provided by one or more network entities in the network, respectively, where the first main header and the first service header are associated with a flow between the logical unit and the UE. The communication manager 2720 is capable of supporting, configured to support, or operable to support means for generating a second service data unit associated with the radio link control layer, the second service data unit comprising a second packet, a second main header associated with the first layer, and a second service header relating to the second packet associated with the service, the second main header and the second service header each associated with the flow between the logical unit and the UE, and the first service header and the second service header being distinct from each other. The communication manager 2720 is capable of supporting, configured to support, or operable to support means for outputting one or more messages comprising the first service data unit and the second service data unit.

[0316] Furthermore, or alternatively, the communications manager 2720 can support wireless communications in accordance with embodiments such as those disclosed herein. For example, the communications manager 2720 can support, is configured to support, or is operable to support, means for communicating a first message, including a first service data unit associated with a radio link control layer. The communications manager 2720 can support, is configured to support, or is operable to support, means for deriving from the first service data unit a first packet, a first main header relating to the first packet associated with a first layer above the radio link control layer, and a first service header relating to a service provided by one or more network entities in the network, each of which is associated with a flow between a logical unit and a UE. The communication manager 2720 is capable of supporting, configured to support, or operable to support means for generating a second service data unit associated with the radio link control layer, which includes a second packet, a second main header, and a second service header associated with the service, each of which is associated with a flow between a logical unit and a UE, and the second service header is based on and different from the first service header. The communication manager 2720 is capable of supporting, configured to support, or operable to support means for communicating a second message including the second service data unit.

[0317] By including or configuring the communications manager 2720 according to embodiments described herein, the device 2705 can support technologies for improved programmability and service adaptability, as well as for reducing at least some deployment overhead.

[0318] In some embodiments, the communication manager 2720 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or in cooperation with the transceiver 2715, one or more antennas 2725, or any combination thereof. Although the communication manager 2720 is shown as a separate component, in some embodiments, one or more functions described with reference to the communication manager 2720 may also be supported or performed by the processor 2740, memory 2730, code 2735, or any combination thereof. For example, code 2735 may include instructions executable by the processor 2740 for causing the device 2705 to perform various aspects of the user-plane programmable layer for wireless communication, as described herein, or the processor 2740 and memory 2730 may be configured to perform or support such operations.

[0319] Figure 28 shows a flowchart illustrating Method 2800, which supports a user-plane programmable layer for wireless communication according to various aspects of the present disclosure. The operation of Method 2800 can be carried out by a wireless device or its components, as described herein. For example, the operation of Method 2800 can be carried out by a wireless device, as described with reference to Figures 1 to 23. In some embodiments, the wireless device can execute a set of instructions for controlling the functional elements of the wireless device to perform the functions described. Furthermore, or alternatively, the wireless device can perform the functions described using dedicated hardware.

[0320] In 2805, the method may include sending a capability message from the network entity to a logical unit indicating that the network entity supports instructions relating to services associated with the radio layer for wireless communication with one or more UEs. The operation of 2805 can be performed according to embodiments such as those disclosed herein. In some embodiments, aspects of the operation of 2805 can be performed by a capability message component 2225, as described with reference to Figure 22.

[0321] In 2810, the method may include establishing a data session associated with a logical unit and one of the UEs, based on the transmission of a capability message. The operation of 2810 can be performed according to embodiments such as those disclosed herein. In some embodiments, aspects of the operation of 2810 can be performed by an establishment component 2230, as described with reference to Figure 22.

[0322] In 2815, the method may include receiving instructions from a logical unit, based on a data session, to perform a radio function associated with its service with the UE. The operation of 2815 can be performed according to embodiments such as those disclosed herein. In some embodiments, aspects of the operation of 2815 can be performed by instruction component 2235, as described with reference to Figure 22.

[0323] In 2820, the method may include executing instructions for performing wireless functions at the wireless layer. The operation of 2820 can be performed according to embodiments such as those disclosed herein. In some embodiments, various aspects of the operation of 2820 can be performed by instruction component 2235, as described with reference to Figure 22.

[0324] Figure 29 shows a flowchart illustrating Method 2900, which supports a user-plane programmable layer for wireless communication according to various aspects of the present disclosure. The operation of Method 2900 can be carried out by a wireless device or its components, as described herein. For example, the operation of Method 2900 can be carried out by a wireless device, as described with reference to Figures 1 to 23. In some embodiments, the wireless device can execute a set of instructions for controlling the functional elements of the wireless device to perform the functions described. Furthermore, or alternatively, the wireless device can perform the functions described using dedicated hardware.

[0325] In 2905, the method may include sending a capability message to a logical unit indicating the services supported by the network entity. The operation of 2905 can be performed according to embodiments such as those disclosed herein. In some embodiments, aspects of the operation of 2905 can be performed by a capability message component 2225, as described with reference to Figure 22.

[0326] In 2910, the method may include establishing a data session associated with a flow between the logical unit and the UE, based on the transmission of a capability message. The operation of 2910 can be performed according to embodiments such as those disclosed herein. In some embodiments, aspects of the operation of 2910 can be performed by an establishment component 2230, as described with reference to Figure 22.

[0327] In 2915, the method may include establishing a data wireless bearer associated with a flow with a UE based on a data session. The operation of 2915 can be performed according to embodiments such as those disclosed herein. In some embodiments, aspects of the operation of 2915 can be performed by an establishment component 2230, as described with reference to Figure 22.

[0328] In 2920, the method may include receiving a first message associated with a flow from a logical unit, based on a data session with the logical unit, including a first header associated with a first layer. The operation of 2920 can be performed according to embodiments such as those disclosed herein. In some embodiments, aspects of the operation of 2920 can be performed by a message component 2240, as described with reference to Figure 22.

[0329] In 2925, the method may include generating a radio link control service data unit, which includes a first header and a second header associated with a first layer based on one or more radio functions of a network entity. The operation of 2925 can be performed according to embodiments such as those disclosed herein. In some embodiments, aspects of the operation of 2925 can be performed by a message component 2240, as described with reference to Figure 22.

[0330] In 2930, the method may include transmitting a second message containing a radio link control service data unit via a data radio bearer. The operation of 2930 can be performed according to embodiments such as those disclosed herein. In some embodiments, aspects of the operation of 2930 can be performed by a message component 2240, as described with reference to Figure 22.

[0331] Figure 30 shows a flowchart illustrating Method 3000, which supports a user-plane programmable layer for wireless communication according to various aspects of the present disclosure. The operation of Method 3000 can be carried out by a wireless device or its components, as described herein. For example, the operation of Method 3000 can be carried out by a wireless device, as described with reference to Figures 1 to 23. In some embodiments, the wireless device can execute a set of instructions for controlling the functional elements of the wireless device to perform the functions described. Furthermore, or alternatively, the wireless device can perform the functions described using dedicated hardware.

[0332] In 3005, the method may include receiving a capability message indicating that the network entity supports instructions relating to services associated with the radio layer for wireless communication with the UE. The operation of 3005 can be performed according to embodiments such as those disclosed herein. In some embodiments, aspects of the operation of 3005 can be performed by a capability message component 2225, as described with reference to Figure 22.

[0333] In 3010, the method may include establishing a data session associated with a flow between a logical unit and a UE based on capability messages. The operation of 3010 can be performed according to embodiments such as those disclosed herein. In some embodiments, aspects of the operation of 3010 can be performed by an establishment component 2230, as described with reference to Figure 22.

[0334] In 3015, the method may include sending a first message associated with a flow, which includes a main header, a service header associated with a first layer, an instruction that the service header should be processed by a network entity, and an instruction to perform a radio function associated with a service with the UE. The operation of 3015 can be performed according to embodiments such as those disclosed herein. In some embodiments, aspects of the operation of 3015 can be performed by a message component 2240, as described with reference to Figure 22.

[0335] In 3020, the method may include receiving a second message associated with a flow, which includes a main header based on the first message. The operation of 3020 can be performed according to embodiments such as those disclosed herein. In some embodiments, various aspects of the operation of 3020 can be performed by a message component 2240, as described with reference to Figure 22.

[0336] Figure 31 shows a flowchart illustrating Method 3100, which supports a user-plane programmable layer for wireless communication according to various aspects of the present disclosure. The operation of Method 3100 can be carried out by a wireless device or its components, as described herein. For example, the operation of Method 3100 can be carried out by a wireless device, as described with reference to Figures 1 to 19 and Figures 24 to 27. In some embodiments, the wireless device can execute a set of instructions for controlling the functional elements of the wireless device to perform the functions described. Furthermore, or alternatively, the wireless device can perform the functions described using dedicated hardware.

[0337] In 3105, the method may include generating a first service data unit, which includes a first packet associated with a radio link control layer and associated with a first layer above the radio link control layer, and a first main header relating to the first packet and associated with a service provided by one or more network entities in the network, wherein each of the first main header and the first service header is associated with a flow between a logical unit and a UE. The operation of 3105 can be performed according to embodiments such as those disclosed herein. In some embodiments, aspects of the operation of 3105 can be performed by a service data unit generator 2625, as described with reference to Figure 26.

[0338] In 3110, the method may include generating a second service data unit associated with a wireless link control layer, wherein the second service data unit includes a second packet, a second main header associated with the first layer, and a second service header relating to the second packet associated with a service, each of which the second main header and the second service header are associated with a flow between a logical unit and a UE, and the first service header and the second service header are distinct from each other. The operation of 3110 can be performed according to embodiments such as those disclosed herein. In some embodiments, various aspects of the operation of 3110 can be performed by a service data unit generator 2625, as described with reference to Figure 26.

[0339] In 3115, the method may include outputting one or more messages, each containing a first service data unit and a second service data unit. The operation of 3115 can be performed according to embodiments such as those disclosed herein. In some embodiments, various aspects of the operation of 3115 can be performed by a message component 2630, as described with reference to Figure 26.

[0340] Figure 32 shows a flowchart illustrating Method 3200, which supports a user-plane programmable layer for wireless communication according to various aspects of the present disclosure. The operation of Method 3200 can be carried out by a wireless device or its components, as described herein. For example, the operation of Method 3200 can be carried out by a wireless device, as described with reference to Figures 1 to 19 and Figures 24 to 27. In some embodiments, the wireless device can execute a set of instructions for controlling the functional elements of the wireless device to perform the functions described. Furthermore, or alternatively, the wireless device can perform the functions described using dedicated hardware.

[0341] In 3205, the method may include communicating a first message, which includes a first service data unit associated with the radio link control layer. The operation of 3205 can be performed according to embodiments such as those disclosed herein. In some embodiments, aspects of the operation of 3205 can be performed by a message component 2630, as described with reference to Figure 26.

[0342] In 3210, the method may include deriving from a first service data unit a first packet, a first main header relating to the first packet associated with a first layer above the radio link control layer, and a first service header relating to the first packet associated with a service provided by one or more network entities in the network, wherein each of the first main header and the first service header is associated with a flow between a logical unit and a UE. The operation of 3210 can be performed according to embodiments such as those disclosed herein. In some embodiments, aspects of the operation of 3210 can be performed by a derivation component 2635, as described with reference to Figure 26.

[0343] In 3215, the method generates a second service data unit associated with a wireless link control layer, comprising a second packet, a second main header, and a second service header associated with a service, wherein each of the second main header and the second service header is associated with a flow between a logical unit and a UE, and the generation of the second service header is based on a first service header, while the second service header is different from the first service header. The operation of 3215 can be performed according to embodiments such as those disclosed herein. In some embodiments, various aspects of the operation of 3215 can be performed by a service data unit generator 2625, as described with reference to Figure 26.

[0344] In 3220, the method may include communicating a second message containing a second service data unit. The operation of 3220 can be performed according to embodiments such as those disclosed herein. In some embodiments, various aspects of the operation of 3220 can be performed by a message component 2630, as described with reference to Figure 26.

[0345] The following provides an overview of the various aspects of this disclosure.

[0346] Embodiment 1: A method for wireless communication by a network entity, comprising: sending a capability message from the network entity to a logical unit indicating that the network entity supports instructions relating to a service associated with the radio layer for wireless communication with one or more UEs; establishing a data session with the logical unit and associated with one of the one or more UEs, at least in part on sending the capability message; receiving instructions from the logical unit to perform a radio function associated with a service with the UE, at least in part on the data session; and performing the instructions to perform the radio function at the radio layer.

[0347] Embodiment 2: The method of Embodiment 1, further comprising receiving a first message including an instruction, a packet, and a header; establishing a data radio bearer with the UE at least in part on a data session; transmitting a second message including a first radio link control service data unit at least in part on establishing the data radio bearer with the UE, wherein the first radio link control service data unit transmits including a packet and a header; receiving a third message including a second radio link control service data unit at least in part on the second message, wherein the second radio link control service data unit receives including a header and a response to a packet; embedding the header in a fourth message, wherein the fourth message embeds the response to a packet; and transmitting a fourth message at least in part on an instruction, wherein the instruction transmits after receiving the third message.

[0348] Embodiment 3: The method of Embodiment 2, wherein a fourth message includes a service header associated with the flow between the UE and the logical unit, and this service header includes parameters that are at least partially based on the instruction.

[0349] Embodiment 4: Any method of Embodiments 1 to 3, further comprising receiving a first message, which includes an instruction and a packet, and executing the instruction, which is at least partially based on the first message; establishing a data radio bearer with the UE, which is at least partially based on a data session; and transmitting a second message, which includes a packet, which is at least partially based on establishing a data radio bearer with the UE and an instruction, which is performed before transmitting the second message.

[0350] Embodiment 5: Any method of Embodiments 1 to 4, wherein the logical unit includes a second network entity.

[0351] Embodiment 6: A method for wireless communication by a network entity, comprising: transmitting a capability message to a logical unit indicating a service supported by the network entity; establishing a data session with the logical unit associated with a flow between the logical unit and a UE, at least in part on transmitting the capability message; establishing a data radio bearer with the UE associated with the flow, at least in part on the data session; receiving a first message associated with a flow from the logical unit, at least in part on the data session with the logical unit, including a first header associated with a first layer; generating a radio link control service data unit, including a first header and a second header associated with a first layer, at least in part on one or more radio functions of the network entity; and transmitting a second message including the radio link control service data unit via the data radio bearer.

[0352] Embodiment 7: The method of Embodiment 6, wherein a first message includes a main header and a first service header associated with a service, and a second message includes a main header, a first service header and a second service header associated with the radio functionality of a network entity.

[0353] Embodiment 8: The method of Embodiment 7, further comprising receiving a plurality of messages from a logical unit, each of which includes a service header associated with a service, and performing prioritization of the plurality of messages at least in part on the corresponding service headers, wherein sending a second message is at least in part on the prioritization.

[0354] Embodiment 9: Any method of Embodiments 7, 8, further comprising modifying a first service header at least in part on an instruction received from a second logical unit, and sending a second message at least in part on the modified first service header.

[0355] Embodiment 10: Any of embodiments 7 to 9, wherein the first message includes a set of service headers including a first service header, and the method further includes adding a third service header to the second message based at least in part on an instruction received from a second logical unit.

[0356] Embodiment 11: Any method of Embodiments 7 to 10, wherein the first message includes a set of service headers including a first service header, and the second message includes a subset of the set of service headers including the first service header, and the subset of the set of service headers does not include at least one service header from the set of service headers.

[0357] Embodiment 12: Any method from Embodiments 6 to 11, wherein a first header includes an instruction that a first message should be processed by a network entity before generating a wireless link control service data unit, and a second header is at least partially based on the instruction that a first message should be processed by a network entity.

[0358] Embodiment 13: Any method from Embodiments 6 to 12, wherein the first header includes an identifier of a network entity, instructions, measurements, information about a data session, or any combination thereof.

[0359] Embodiment 14: Any method among Embodiments 6 to 13, wherein the logical unit includes a second network entity, a user plane function, or both.

[0360] Embodiment 15: A method for wireless communication by a logical unit, comprising: receiving a capability message indicating that a network entity supports instructions relating to a service associated with a radio layer for wireless communication with a UE; establishing a data session associated with a flow between the logical unit and the UE, at least based on the capability message; sending a first message associated with the flow, including a main header, a service header associated with a first layer, an instruction that the service header should be processed by the network entity, and instructions for performing a radio function associated with the service with the UE; and receiving a second message associated with the flow, including a main header at least based on the first message.

[0361] Embodiment 16: The method of Embodiment 15, wherein the instruction that a service header should be processed by a network entity includes an instruction to perform that processing before generating a service data unit associated wit...

Claims

1. Network entity, One or more processors, One or more memories connected to the one or more processors, storing processor-executable code, wherein when the processor-executable code is executed by the one or more processors, the network entity, The network entity causes the logical unit to send a capability message indicating that it supports instructions relating to services associated with the wireless layer for wireless communication with one or more UEs (UEs), Based at least in part on the fact that one or more processors are configured to send the capability messages, the logical unit establishes a data session associated with one of the one or more UEs. Based at least in part on the data session, the logical unit receives instructions to perform the radio function associated with the service with the UE, A network entity comprising one or more memories configured in the wireless layer to execute the instructions for performing the wireless function.

2. When the processor-executable code is executed by the one or more processors, the network entity will be: A first message, including the aforementioned instruction, packet, and header, is received. Based at least partially on the aforementioned data session, establish a data wireless bearer with the UE, Based at least in part on the fact that one or more of the processors are configured to establish the UE and the data radio bearer, a second message including a first radio link control service data unit is sent, the first radio link control service data unit including the packet and the header, Based at least in part on the second message, a third message is received which includes a second wireless link control service data unit, the second wireless link control service data unit includes the header and a response to the packet. A header is embedded in the fourth message, and the fourth message includes a response to the packet. The network entity according to claim 1, wherein a fourth message is sent based at least in part on the aforementioned instruction, and the instruction is further configured to be executed after the third message has been received.

3. The fourth message includes a service header associated with the flow between the UE and the logical unit, The service header includes parameters that are at least partially based on the instruction, The network entity according to claim 2.

4. When the processor-executable code is executed by the one or more processors, the network entity will be: A first message is received, including the aforementioned instruction and packet, and the instruction is executed at least in part based on the first message. Based at least partially on the aforementioned data session, establish a data wireless bearer with the UE, The network entity according to claim 1, wherein one or more processors are configured to establish the UE and the data radio bearer and cause the instruction to transmit a second message containing the packet, the instruction being further configured to be executed before the second message is transmitted.

5. The network entity according to claim 1, wherein the logical unit includes a second network entity.

6. Network entity, One or more processors, One or more memories connected to the one or more processors, storing processor-executable code, wherein when the processor-executable code is executed by the one or more processors, the network entity, The network entity causes the logical unit to send a capability message indicating the services it supports. Based at least in part on the fact that one or more of the processors are configured to send the capability messages, the logical unit establishes a data session associated with the flow between the logical unit and the user equipment (UE), Based at least partially on the aforementioned data session, establish the UE and the data wireless bearer associated with the flow. Based at least in part on the data session with the logical unit, a first message associated with the flow, including a first header associated with the first layer, is received from the logical unit. A wireless link control service data unit is generated, which includes a second header associated with the first layer, at least in part, based on the first header and one or more wireless functions of the network entity. A network entity comprising one or more memories configured to transmit a second message, including the wireless link control service data unit, via the data wireless bearer.

7. The first message includes a main header and a first service header associated with the service, The second message includes the main header, the first service header, and the second service header associated with the wireless functionality of the network entity. The network entity according to claim 6.

8. When the processor-executable code is executed by the one or more processors, the network entity will be: The logical unit receives a plurality of messages, each of which includes the first message, and each of the plurality of messages includes a service header associated with the service. The network entity according to claim 7, further configured to perform prioritization of the plurality of messages based at least partially on the corresponding service headers, and to transmit the second message based at least partially on the prioritization.

9. When the processor-executable code is executed by the one or more processors, the network entity will be: The network entity according to claim 7, further configured to modify the first service header based at least in part on an instruction received from a second logical unit, and to transmit the second message based at least in part on the modified first service header.

10. The first message includes a set of service headers, including the first service header, and when the processor executable code is executed by the one or more processors, the network entity receives The network entity according to claim 7, further configured to cause a third service header to be added to the second message, at least in part, based on an instruction received from a second logical unit.

11. The first message includes a set of service headers, which includes the first service header. The second message includes a subset of the set of service headers, which includes the first service header. The subset of the set of service headers does not include at least one service header from the set of service headers. The network entity according to claim 7.

12. The first header includes an instruction that the first message should be processed by the network entity before generating the wireless link control service data unit, The second header is at least partially based on the instruction that the first message should be processed by the network entity, The network entity according to claim 6.

13. The network entity according to claim 6, wherein the first header includes an identifier for the network entity, instructions, measurements, information about the data session, or any combination thereof.

14. The network entity according to claim 6, wherein the logical unit includes a second network entity, a user plane function, or both.

15. It is a logical unit, One or more processors, One or more memories connected to the one or more processors, storing processor-executable code, wherein when the processor-executable code is executed by the one or more processors, the network entity, The network entity receives a capability message indicating that it supports commands related to services associated with the wireless layer for wireless communication with user equipment (UE). Based at least in part on the capability message, establish a data session associated with the flow between the logical unit and the UE. A first message is sent, which is associated with the flow and includes a main header, a service header associated with a first layer, an instruction that the service header should be processed by the network entity, and an instruction to perform a radio function associated with the service with the UE. A logical unit comprising one or more memories associated with the flow and configured to receive a second message, which includes the main header at least partially based on the first message.

16. The logical unit according to claim 15, wherein the instruction that the service header should be processed by the network entity includes an instruction to perform the processing before the generation of a service data unit associated with the wireless link control layer, an instruction to insert the service header into the first message, or both.

17. The logical unit according to claim 16, wherein the service header includes an identifier for the network entity, a second instruction, a measurement value, or any combination thereof.

18. The logical unit according to claim 15, wherein the logical unit includes a second network entity, a user plane function, or both.

19. It is a device, One or more processors, One or more memories connected to the one or more processors, storing processor-executable code, wherein when the processor-executable code is executed by the one or more processors, the device, A first service data unit is generated, which includes a first packet associated with a wireless link control layer, a first main header relating to the first packet and associated with a first layer above the wireless link control layer, and a first service header relating to the first packet and associated with a service provided by one or more network entities in the network, wherein each of the first main header and the first service header is associated with a flow between a logical unit and a user device (UE). A second service data unit is generated associated with the wireless link control layer, the second service data unit comprising a second packet, a second main header associated with the first layer, and a second service header relating to the second packet and associated with the service, wherein each of the second main header and the second service header is associated with the flow between the logical unit and the UE, and the first service header and the second service header are different from each other. A device comprising: one or more memories configured to output one or more messages, including the first service data unit and the second service data unit.

20. When the processor-executable code is executed by the one or more processors, the device: The apparatus according to claim 19, further configured to establish a data radio bearer with the UE, wherein the one or more messages are output by a network entity, and the one or more processors are configured to establish a data radio bearer with the UE.

21. When the processor-executable code is executed by the one or more processors, the device: The apparatus according to claim 19, further configured to establish a data radio bearer with the network entity, and at least in part being configured that the one or more messages are output by the UE and that the one or more processors establish the data radio bearer with the network entity.

22. The system further comprises one or more transceivers configured to receive a first message, which includes the first packet, the first main header, and the first service header, the one or more processors further configured to modify the first service header based at least in part on the first message, and the first service data unit is generated based at least in part on the modified first service header. The apparatus according to claim 19.

23. The apparatus according to claim 22, wherein the processor executable code is further configured to cause the apparatus to update a timestamp when executed by the one or more processors in order to modify the first service header.

24. When the processor-executable code is executed by the one or more processors, the device: To obtain a first message including the first packet, the first main header, the first service header, and a third service header associated with the second service, The apparatus according to claim 19, further configured to remove the third service header in relation to the generation of the first service data unit so that the first service data unit does not include the third service header.

25. When the processor-executable code is executed by the one or more processors, the device: To obtain a first message including the first packet, the first main header, and the first service header, The apparatus according to claim 19, further configured to add the third service header in relation to the generation of the first service data unit such that the first service data unit includes a third service header, wherein the first message does not include the third service header.

26. The apparatus according to claim 19, wherein the first service header, the second service header, or both thereof include an instruction.

27. The apparatus according to claim 26, wherein the instruction indicates that an acknowledgment should be sent upon receipt of the one or more messages, that packets associated with the one or more messages should be sorted according to the arrangement indicated by the instruction, that packets associated with the one or more messages should be discarded after a threshold time, that packets associated with the one or more messages should be timestamped, or any combination thereof.

28. The apparatus according to claim 19, wherein the first service header includes a sorting timer, a sorting domain, an instruction to discard the first packet after the sorting timer has expired, an instruction to transmit acknowledgment feedback for the first packet, or any combination thereof.

29. The apparatus according to claim 19, wherein the first main header and the second main header each include a data control flag, a header length, a sequence number, information associated with an extended field, or any combination thereof.

30. It is a device, One or more processors, One or more memories connected to the one or more processors, storing processor-executable code, wherein when the processor-executable code is executed by the one or more processors, the device, A first message is transmitted, including a first service data unit associated with the wireless link control layer. From the first service data unit, a first packet, a first main header relating to the first packet associated with a first layer above the wireless link control layer, and a first service header relating to the first packet associated with a service provided by one or more network entities in the network, wherein each of the first main header and the first service header is associated with a flow between a logical unit and a user device (UE), The wireless link control layer generates a second service data unit which includes a second packet, a second main header, and a second service header associated with the service, wherein each of the second main header and the second service header is associated with the flow between the logical unit and the UE, and the second service header is at least partially based on the first service header, and the second service header is different from the first service header. A device comprising one or more memories configured to transmit a second message including the second service data unit.

31. When the processor-executable code is executed by the one or more processors, the device: The apparatus according to claim 30, further configured to establish a data radio bearer with the UE, and at least in part being configured that the first message is communicated, the second message is output by a network entity, and the one or more processors establish a data radio bearer with the UE.

32. When the processor-executable code is executed by the one or more processors, the device: The apparatus according to claim 30, further configured to establish a network entity and a data radio bearer, and at least in part being configured that the first message is communicated, the second message is output by the UE, and the one or more processors establish the network entity and the data radio bearer.

33. The first service header includes instructions, and when the processor-executable code is executed by the one or more processors, the device: The apparatus according to claim 30, further configured to execute the aforementioned instruction, wherein the generation of the second service data unit is at least partially based on the aforementioned instruction.

34. The apparatus according to claim 30, wherein the first service header includes information about the first packet, a sorting timer, a sorting domain, an instruction to discard the first packet after the sorting timer has expired, an expiration date for the first packet, an instruction to transmit acknowledgment feedback for the first packet, or any combination thereof.

35. The apparatus according to claim 30, wherein the first main header and the second main header each include a data control flag, a header length, a sequence number, information associated with an extended field, or any combination thereof.

Images