Techniques for data transport in service-based wireless systems - Patent Application 20070122963
A service-based wireless network architecture with distributed units and transport services optimizes resource allocation and flexibility by enabling UEs to establish transport radio bearers, addressing inefficiencies and enhancing system performance and flexibility.
Patent Information
- Application Number
- JP2025514861
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2022-09-19
- Filing Date
- 2023-09-08
- Publication Date
- 2025-10-01
AI Technical Summary
Existing wireless communication systems, particularly those with a vertical hierarchical architecture, face inefficiencies in resource utilization and power consumption due to duplicated processing across multiple devices, and lack flexibility in integrating customized services and functionalities for user equipment (UEs).
Implementing a service-based wireless network architecture with distributed units (DUs) and transport services that enable UEs to establish transport radio bearers through signaling, configuring logical channels based on Quality of Service (QoS) parameters, and performing dynamic updates to optimize resource allocation and communication.
Enhances resource efficiency, reduces power consumption, and allows UEs to selectively subscribe to network services tailored to their needs, improving overall system performance and flexibility in service provision.
Smart Images

Figure 2025532548000001_ABST
Abstract
Description
[Technical Field]
[0001] cross reference
[0001] This patent application claims priority to U.S. patent application Ser. No. 17 / 948,125, entitled "TECHNIQUES FOR DATA TRANSPORT IN A SERVICE-BASED WIRELESS SYSTEM," by GHOLMIEH et al., filed Sep. 19, 2022, assigned to the assignee of this patent application, and expressly incorporated by reference in its entirety herein.
[0002] The following relates to wireless communications, including techniques for data transport in service-based wireless systems. [Background technology]
[0003]
[0003] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcasts, and so on. These systems may be capable of supporting 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, and fifth-generation (5G) systems, sometimes referred to as New Radio (NR) systems. These systems may employ techniques such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), or Discrete Fourier Transform Spread Orthogonal Frequency Division Multiplexing (DFT-S-OFDM), etc. A wireless multiple-access communication system may include one or more base stations that each support wireless communication for communication devices, which may be known as User Equipment (UE). Summary of the Invention
[0004]
[0004] Techniques described relate to improved methods, systems, devices, and apparatuses supporting techniques for data transport in service-based wireless systems. According to various aspects of the present disclosure, signaling and other mechanisms are provided that enable a user equipment (UE) to establish wireless connectivity in a service-based network, such as a sixth-generation (6G) network. In particular, aspects of the present disclosure may support signaling between a UE, network entities (e.g., distributed units (DUs)), and network services (e.g., core network services, radio access network (RAN) services, or both) of a service-based network architecture that enable the UE to establish transport channels for wireless connectivity in a service-based cloud network (e.g., a 6G network).
[0005] According to various aspects, signaling may be provided between a UE, a DU, and one or more transport services of a service-based cloud network architecture that enables the UE to establish radio bearers (e.g., transport radio bearers), where the one or more transport radio bearers are mapped to logical channels for communication between the UE and the DU. For example, the UE may establish a connection with the DU and receive control signaling indicating that a transport service is provided by the network. The UE may send a service request (e.g., via the DU) based on data to be transmitted, which may include Quality of Service (QoS) parameters (e.g., latency, reliability, timing of first packet, etc.). The transport service may communicate with the DU to configure scheduling, resources, and QoS requirements for the transport radio bearers. The DU may determine the radio configuration based on information received from the transport service, such as physical (PHY) layer parameters (e.g., number of carriers, logical channel mapping to service layer transport radio bearers, uplink grants / downlink grants, etc.) and Layer 2 (L2) parameters (e.g., Medium Access Control (MAC) and Radio Link Control (RLC) parameters, security parameters, Packet Data Convergence Protocol (PDCP) parameters, or any combination thereof). The UE may communicate with the transport service via the DU based on the radio configuration. Dynamic updates may be performed based on updated conditions in the UE, the network, or both.
[0006] A method for wireless communication in a UE is described, which may include: communicating, via a distributed unit, a first service message to establish a first transport radio bearer with a first transport service provided by a service-based network, the first service message indicating one or more attributes associated with information to be transported via the first transport radio bearer; receiving, in response to the first service message, from the distributed unit a physical resource configuration for communication associated with the first transport service and a mapping of the first transport radio bearer to a first channel between the UE and the distributed unit; and communicating, via the distributed unit, the information to be transported via the first transport service based on the physical resource configuration.
[0007] An apparatus for wireless communication in a UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to communicate, via a distributed unit, a first service message to establish a first transport radio bearer with a first transport service provided by a service-based network, the first service message indicating one or more attributes associated with information to be transported via the first transport radio bearer, receive, from the distributed unit in response to the first service message, a physical resource configuration for communication associated with the first transport service and a mapping of the first transport radio bearer to a first channel between the UE and the distributed unit, and communicate, via the distributed unit, the information to be transported via the first transport service based on the physical resource configuration.
[0008] Another apparatus for wireless communication in a UE is described, which may include: means for communicating, via a distributed unit, a first service message indicating one or more attributes associated with information to be transported via the first transport radio bearer to establish a first transport radio bearer with a first transport service provided by a service-based network; means for receiving, in response to the first service message, from the distributed unit a physical resource configuration for communication associated with the first transport service and a mapping of the first transport radio bearer to a first channel between the UE and the distributed unit; and means for communicating, via the distributed unit, the information to be transported via the first transport service based on the physical resource configuration.
[0009] A non-transitory computer-readable medium storing code for wireless communication in a UE is described, wherein the code may include instructions executable by a processor to: communicate, via a distributed unit, a first service message to establish a first transport radio bearer with a first transport service provided by a service-based network, the first service message indicating one or more attributes associated with information to be transported via the first transport radio bearer; receive, in response to the first service message, from the distributed unit a physical resource configuration for communication associated with the first transport service and a mapping of the first transport radio bearer to a first channel between the UE and the distributed unit; and communicate, via the distributed unit, the information to be transported via the first transport service based on the physical resource configuration.
[0010]
[0010] Some examples of the methods, apparatus, and non-transitory computer-readable media described in this specification may further include operations, features, means, or instructions for mapping one or more transport radio bearers to the first channel, each of the transport radio bearers having an associated transport service.
[0011] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, information to be transported via a first transport service may be split across two or more channels between the UE and the distributed unit, including a separate channel for signaling information. In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the split across the two or more channels may be based on one or more of a traffic priority of the information to be transported via the first transport service, a delay tolerance of the traffic of the information to be transported via the first transport service, a tolerable error rate of the traffic of the information to be transported via the first transport service, or any combination thereof.
[0012] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, two or more transport radio bearers from a first transport service may be mapped to the first channel, one transport radio bearer may be mapped to the first channel, or multiple transport radio bearers may be mapped to each of two or more channels. In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first service message includes one or more quality of service targets associated with information to be transported via the first transport service, and different quality of service targets are associated with different channels between the UE and the distributed unit. In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the information to be transported via the first transport service may be transmitted using a set of multiple packets, each packet of the set of multiple packets including an indication of the first transport radio bearer. In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first transport radio bearer provides communication for both signaling information and data associated with the first transport service.
[0013] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, communicating the first service message may include an operation, feature, means, or instruction for communicating one or more attributes associated with the information to be transported via the first transport service as one or more quality of service parameters including a latency target, a throughput target, a security level, or any combination thereof. Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include an operation, feature, means, or instruction for communicating one or more buffer status reports to the first transport service via the distributed unit to maintain an active state in the first transport service.
[0014] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for receiving an indication to suppress information to be transported via the first transport service and for suppressing information communicated via the first transport service regardless of the amount of information communicated via one or more other transport services different from the first transport service. Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for communicating, via the distributed unit, a second service message indicating deactivation of a first transport radio bearer associated with the first transport service. Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for obtaining further information to be transported via the first transport radio bearer and for activating the first transport radio bearer following deactivation of the first transport service.
[0015] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the third service message includes one or more indications of a buffer status report associated with the first transport radio bearer, a target delivery time for a first packet of data of the further information to be transported via the first transport radio bearer, or any combination thereof. Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for communicating, via the distributed unit, a second service message indicating to release the first transport radio bearer associated with the first transport service, wherein the second service message may be communicated in response to a lack of information to be transported via the first transport radio bearer, expiration of data associated with the first transport radio bearer, or any combination thereof.
[0016] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for receiving, from the distributed unit, an updated physical resource configuration in response to an updated configuration associated with the first transport service, and for communicating, via the distributed unit, information to be transported via the first transport service based on the updated physical resource configuration. In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first transport service may be provided at a protocol layer associated with the first transport radio bearer, which may be an Internet Protocol (IP) layer or a Packet Data Convergence Protocol (PDCP) layer.
[0017] A method for wireless communication in a distributed unit is described. The method may include communicating a first service message between a UE and a first transport service provided by a service-based network, the first service message establishing the first transport service and indicating one or more attributes associated with information to be transported via the first transport service, receiving a radio access network configuration from the first transport service indicating a first transport radio bearer and traffic flow information associated with the first transport radio bearer, sending to the UE, in response to the radio access network configuration, a physical resource configuration for communication associated with the first transport service and a mapping of the first transport radio bearer to a first channel between the UE and the distributed unit, and communicating the information to be transported via the first transport service between the UE and the first transport service based on the physical resource configuration.
[0018] An apparatus for wireless communication in a distributed unit is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to communicate a first service message between a UE and a first transport service provided by a service-based network, the first service message establishing the first transport service and indicating one or more attributes associated with information to be transported via the first transport service, receive from the first transport service a radio access network configuration indicating a first transport radio bearer and traffic flow information associated with the first transport radio bearer, transmit to the UE, in response to the radio access network configuration, a physical resource configuration for communication associated with the first transport service and a mapping of the first transport radio bearer to a first channel between the UE and the distributed unit, and communicate the information to be transported via the first transport service between the UE and the first transport service based on the physical resource configuration.
[0019] Another apparatus for wireless communication in a distributed unit is described, which may include: means for communicating a first service message between a UE and a first transport service provided by a service-based network, the first service message establishing the first transport service and indicating one or more attributes associated with information to be transported via the first transport service; means for receiving from the first transport service a radio access network configuration indicating a first transport radio bearer and traffic flow information associated with the first transport radio bearer; means for transmitting, in response to the radio access network configuration, to the UE a physical resource configuration for communication associated with the first transport service and a mapping of the first transport radio bearer to a first channel between the UE and the distributed unit; and means for communicating the information to be transported via the first transport service between the UE and the first transport service based on the physical resource configuration.
[0020] A non-transitory computer-readable medium storing code for wireless communication in a distributed unit is described, wherein the code may include instructions executable by a processor to communicate a first service message between a UE and a first transport service provided by a service-based network, the first service message establishing the first transport service and indicating one or more attributes associated with information to be transported via the first transport service, receive from the first transport service a radio access network configuration indicating a first transport radio bearer and traffic flow information associated with the first transport radio bearer, send to the UE, in response to the radio access network configuration, a physical resource configuration for communication associated with the first transport service and a mapping of the first transport radio bearer to a first channel between the UE and the distributed unit, and communicate the information to be transported via the first transport service between the UE and the first transport service based on the physical resource configuration.
[0021] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for mapping a first transport radio bearer and at least one other transport radio bearer to a first channel, where each transport radio bearer has an associated transport service. In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first service message includes one or more quality of service targets associated with information to be transported via the first transport service. In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the information to be transported via the first transport service may be transmitted using a set of multiple packets, where each packet in the set of multiple packets includes an indication of the first transport radio bearer.
[0022] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first transport radio bearer provides communication for both signaling information and data associated with the first transport service. Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for aggregating traffic flow information across the first transport service and one or more other transport services and for configuring one or more carriers and one or more resource grants of a physical resource configuration based on the aggregated traffic flow information. Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for providing an indication of the first transport radio bearer for each of a set of multiple packets associated with the first transport radio bearer and communicating with the first transport service based on a communication protocol that provides an indication of the traffic flow information associated with the first transport radio bearer. [Brief explanation of the drawings]
[0023] [Figure 1] 1 illustrates an example of a wireless communication system that supports techniques for data transport in a service-based wireless system in accordance with one or more aspects of the present disclosure. [Figure 2]
[0024] 1 illustrates an example of a wireless communication system that supports techniques for data transport in a service-based wireless system in accordance with one or more aspects of the present disclosure. [Figure 3]
[0025] 1 illustrates an example of a network architecture that supports techniques for data transport in a service-based wireless system in accordance with one or more aspects of the present disclosure. [Figure 4]
[0026] 1 illustrates an example of a transport channel structure that supports techniques for data transport in a service-based wireless system in accordance with one or more aspects of the present disclosure. [Figure 5]
[0027] 1 illustrates an example of a process flow supporting techniques for data transport in a service-based wireless system in accordance with one or more aspects of the present disclosure. [Figure 6]
[0028] 1 illustrates a block diagram of a device that supports techniques for data transport in a service-based wireless system in accordance with one or more aspects of the present disclosure. [Figure 7] 1 illustrates a block diagram of a device that supports techniques for data transport in a service-based wireless system in accordance with one or more aspects of the present disclosure. [Figure 8]
[0029] 1 illustrates a block diagram of a communications manager that supports techniques for data transport in a service-based wireless system in accordance with one or more aspects of the present disclosure. [Figure 9]
[0030] 1 illustrates a diagram of a system including devices that support techniques for data transport in a service-based wireless system in accordance with one or more aspects of the present disclosure. [Figure 10]
[0031] 1 illustrates a block diagram of a device that supports techniques for data transport in a service-based wireless system in accordance with one or more aspects of the present disclosure. [Figure 11] 1 illustrates a block diagram of a device that supports techniques for data transport in a service-based wireless system in accordance with one or more aspects of the present disclosure. [Figure 12]
[0032] 1 illustrates a block diagram of a communications manager that supports techniques for data transport in a service-based wireless system in accordance with one or more aspects of the present disclosure. [Figure 13]
[0033] 1 illustrates a diagram of a system including devices that support techniques for data transport in a service-based wireless system in accordance with one or more aspects of the present disclosure. [Figure 14]
[0034] 1 shows a flowchart illustrating a method supporting techniques for data transport in a service-based wireless system in accordance with one or more aspects of the present disclosure. [Figure 15] 1 shows a flowchart illustrating a method supporting techniques for data transport in a service-based wireless system in accordance with one or more aspects of the present disclosure. [Figure 16] 1 shows a flowchart illustrating a method supporting techniques for data transport in a service-based wireless system in accordance with one or more aspects of the present disclosure. [Figure 17] 1 shows a flowchart illustrating a method supporting techniques for data transport in a service-based wireless system in accordance with one or more aspects of the present disclosure. [Figure 18] 1 shows a flowchart illustrating a method supporting techniques for data transport in a service-based wireless system in accordance with one or more aspects of the present disclosure. [Figure 19] 1 shows a flowchart illustrating a method supporting techniques for data transport in a service-based wireless system in accordance with one or more aspects of the present disclosure. [Figure 20] 1 shows a flowchart illustrating a method supporting techniques for data transport in a service-based wireless system in accordance with one or more aspects of the present disclosure. [Figure 21] 1 shows a flowchart illustrating a method supporting techniques for data transport in a service-based wireless system in accordance with one or more aspects of the present disclosure. [Figure 22]1 shows a flowchart illustrating a method supporting techniques for data transport in a service-based wireless system in accordance with one or more aspects of the present disclosure. [Figure 23] 1 shows a flowchart illustrating a method supporting techniques for data transport in a service-based wireless system in accordance with one or more aspects of the present disclosure. [Figure 24] 1 shows a flowchart illustrating a method supporting techniques for data transport in a service-based wireless system in accordance with one or more aspects of the present disclosure. [Figure 25] 1 shows a flowchart illustrating a method supporting techniques for data transport in a service-based wireless system in accordance with one or more aspects of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION
[0024]
[0035] Some wireless systems may exhibit a relatively vertical hierarchical architecture, including many “layers” of different devices that perform functions for the system. For example, a wireless system may include user equipment (UEs), base stations / network entities, and numerous back-end (e.g., core network) devices associated with one or more functions for the system. Such a hierarchical structure may result in processing and other functions being performed in multiple devices (e.g., duplicated processing or capabilities across multiple back-end devices), thereby leading to wasted resources and excessive power consumption. Additionally, the back-end architecture of some wireless systems may be owned and maintained by a few operators, which may make it difficult for other parties / entities to integrate with the system and may complicate the system's ability to provide customized services and functionality to wireless devices.
[0025]
[0036] In comparison, some wireless systems, such as sixth-generation (6G) systems, may exhibit a flatter service-based architecture in which a radio access network (RAN) (e.g., a network entity) interfaces with a service-based network to connect UEs to network services maintained at various network addresses within the service-based network. In the context of a service-based system, operations and functions that might otherwise be performed by a few centralized back-end components (e.g., in some systems) may be distributed across several network services that may be hosted at different network addresses, such as in a cloud-based architecture. As a result, a UE in a service-based system may be able to establish and maintain connections with (e.g., "subscribe") to different network services or groups thereof on an à la carte basis, where each network service provides or delivers a respective network functionality or service. For example, a service-based system may include mobility services, security services, privacy services, location services, etc. In this regard, each UE in a service-based system may be able to select which network services it subscribes to based on the respective UE's individualized characteristics or needs.
[0026]
[0037] Aspects of the present disclosure relate to signaling and other mechanisms that enable a UE to establish a wireless connection in a service-based network. Described techniques relate to signaling between a UE, distributed units (DUs), and a transport service of the service-based network that obtains information related to data to be exchanged in communications with the UE and configures one or more transport channels for such communications. According to various aspects, signaling may be provided between the UE, the DU, and one or more transport services of a service-based cloud network architecture that enable the UE to establish radio bearers (e.g., transport radio bearers), where the one or more transport radio bearers are mapped to logical channels for communications between the UE and the DU. For example, a UE may establish a connection with a DU and receive control signaling indicating that a transport service is provided by the network. The UE may transmit a service request (e.g., via the DU) based on data to be transmitted, which may include quality of service (QoS) parameters (e.g., latency, reliability, timing of the first packet, etc.). The transport service may communicate with the DU to configure scheduling, resources, and QoS requirements for transport radio bearers. The DU may determine the radio configuration based on information received from the transport service, such as physical (PHY) layer parameters (e.g., number of carriers, logical channel mapping for service layer transport radio bearers, uplink grants / downlink grants, etc.) and Layer 2 (L2) parameters (e.g., medium access control (MAC) and radio link control (RLC) parameters, security parameters, packet data convergence protocol (PDCP) parameters, or any combination thereof). The UE may communicate with the transport service via the DU based on the radio configuration. Dynamic updates may be performed based on updated conditions in the UE, the network, or both.
[0027]
[0038] Aspects of the present disclosure are initially described in the context of a wireless communication system. Additional aspects of the present disclosure are described in the context of example network architectures and example process flows. Aspects of the present disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts relating to techniques for data transport in a service-based wireless system.
[0028]
[0039] 1 illustrates an example of a wireless communication system 100 that supports techniques for data transport in a service-based wireless system in accordance with 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 service-based network 130. In some examples, the wireless communication system 100 may implement aspects of a network that operates in accordance with a 6G network, a 5G network (e.g., a New Radio (NR) network), a 4G network (e.g., a Long Term Evolution (LTE) network, an LTE-Advanced (LTE-A) network, an LTE-A Pro network), or other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.
[0029]
[0040] The network entities 105 may be dispersed throughout a geographic area to form the wireless communication system 100 and may include devices of different forms or with different capabilities. In various examples, the network entities 105 may be referred to as network elements, mobility elements, radio access network (RAN) nodes, access points, or network equipment, among other nomenclature. In some examples, the network entities 105 and the UEs 115 may communicate wirelessly via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, each network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) over which the UEs 115 and the network entities 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area over which the network entities 105 and the UEs 115 may support communication of signals via one or more radio access technologies (RATs).
[0030]
[0041] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile or both at different times. The UEs 115 may be devices of different types or with different capabilities. Some example UEs 115 are illustrated in FIG. 1. The UEs 115 described herein may be capable of supporting communication with various types of devices, such as other UEs 115 or network entities 105, as shown in FIG. 1.
[0031]
[0042] As described herein, a node of the wireless communication system 100, which may be referred to as a network node or a wireless node, may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, an apparatus, 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 may be a UE 115. As another example, a node may be a network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be the UE 115, the second node may be a network entity 105, and the third node may be the UE 115. In another aspect of this example, the first node may be the UE 115, the second node may be a network entity 105, and the third node may be a network entity 105. In yet other aspects of this example, the first node, second node, and third node may differ with respect to these examples. Similarly, reference to a UE 115, a network entity 105, an apparatus, a device, a computing system, etc. may include disclosure of the UE 115, the network entity 105, the apparatus, the device, the computing system, etc. being a node. For example, disclosure that a UE 115 is configured to receive information from a network entity 105 also discloses that a first node is configured to receive information from a second node.
[0032]
[0043] In some examples, the network entities 105 may communicate with the service-based network 130, with each other, or both. For example, the network entities 105 may communicate with the service-based network 130 via one or more backhaul communication links 120 (e.g., according to an S1, N2, N3, or other interface protocol). Similarly, the UE 115 may communicate with the service-based network 130 via one or more communication links 155. In some examples, the network entities 105 may communicate with each other either via the backhaul communication links 120 (e.g., according to an X2, Xn, or other interface protocol), directly (e.g., directly between the network entities 105), or indirectly (e.g., via the service-based network 130). In some examples, the network entities 105 may communicate with each other via one or more communication links, such as a fronthaul communication link 168 (e.g., between the radio unit 170 and the distributed unit 165). The backhaul communication link 120, fronthaul communication link 168, or other communication link between network entities 105 may be or include one or more wired links (e.g., electrical links, optical fiber links), one or more wireless links (e.g., radio links, wireless optical links), among other embodiments or various combinations thereof.
[0033]
[0044] In some examples, the network entity 105 may communicate with a service platform 150 (e.g., a cloud platform) that provides one or more core network services (CN services), one or more radio access network services (RAN services), or any combination thereof (CN / RAN services 185). The CN / RAN services 185 may be provided over the service-based network 130 using one or more APIs. For example, one or more DU service APIs 175 may provide an interface for one or more services in the UE 115. The services in the UE 115 may correspond to one or more CN / RAN services 185 in the service platform 150. For example, a network service API 180 in the service-based network 130 may interface with a corresponding DU service API 175 in the DU 165, which in turn interfaces with a corresponding API in the UE 115 to provide service connectivity between the one or more UE 115 services and the corresponding CN / RAN services 185.
[0034]
[0045] One or more of the network entities 105 described herein may include a base station 140 (e.g., base transceiver station, radio base station, access point, radio transceiver, NodeB, eNodeB (eNB), Next Generation NodeB or Giga NodeB (all may be referred to as gNB), 5G NB, Next Generation eNB (ng-eNB), Home NodeB, Home eNodeB, 6G NB, or other suitable terminology) or may be referred to as a base station 140. In some examples, the network entities 105 (e.g., base stations 140) may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture that may be configured to utilize a service-based architecture and provide wireless access within a single network entity 105 (e.g., a single RAN node such as a base station 140 may include an RU 170, a DU 165, and a DU API 175 for CN / RAN services 185). The RU 170 may also be called a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmission reception point (TRP).
[0035]
[0046] Additionally, in some examples, one or more network entities 105 may be implemented in a disaggregated architecture (e.g., disaggregated base station architecture, disaggregated RAN architecture), which may be configured to utilize a protocol stack that is physically or logically distributed between two or more network entities 105, such as an Integrated Access Backhaul (IAB) network, an Open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., Cloud RAN (C-RAN)). For example, the network entities 105 may include one or more of a Central Unit (CU), a DU 165, an RU 170, a RAN Intelligent Controller (RIC) (e.g., a near-real-time RIC (near-RT RIC), a non-real-time RIC (non-RT RIC)), a Service Management and Orchestration (SMO) system, or any combination thereof. One or more components of the network entity 105 in a disaggregated RAN architecture may be co-located, or one or more components of the network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 in a disaggregated RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).
[0036]
[0047] The division of functionality among components (e.g., CU, DU, and RU) is flexible and may support different functionality depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF (radio frequency) functions, and any combination thereof) are performed in the components. For example, a functional division of a protocol stack may be adopted between the CU and DU 165 such that the CU can support one or more layers of the protocol stack and the DU 165 can support one or more different layers of the protocol stack. In some examples, the CU may host upper protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionality and signaling (e.g., RRC, SDAP, PDCP). In some examples, the CU may host one or more service APIs for one or more CN / RAN services 185 via corresponding network service APIs 180 of the service-based network 130. A CU may be connected to one or more DUs 165 or RUs 170, which may host lower protocol layers such as Layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., RLC (Radio Link Control) layer, MAC (Medium Access Control) layer) functionality and signaling, each of which may be at least partially controlled by a CU. Additionally or alternatively, functional division of the protocol stack may be employed between the DU 165 and the RU 170, such that the DU 165 can support one or more layers of the protocol stack, and the RU 170 can support one or more different layers of the protocol stack. The DU 165 may support one or more different cells (e.g., via one or more RUs 170). In some cases, the division of functions between the CU and the DU165, or between the DU165 and the RU170, may be within a protocol layer (e.g., some functions for a protocol layer may be performed by one of the CU, the DU165, or the RU170, while other functions of the protocol layer are performed by a different one of the CU, the DU165, or the RU170).The DUs 165 may be connected to one or more RUs 170 via fronthaul communication links 168 (e.g., open fronthaul (FH) interfaces). In some examples, the fronthaul communication links 168 may be implemented according to interfaces (e.g., channels) between layers of protocol stacks supported by the respective network entities 105 communicating over such communication links.
[0037]
[0048] In a wireless communication system (e.g., wireless communication system 100), infrastructure and spectrum resources for radio access may supplement wired backhaul connections to support wireless backhaul link capabilities and provide an IAB network architecture (e.g., for service-based network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DUs 165 or one or more RUs 170 may be partially controlled by a donor network entity 105 (e.g., donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access links and backhaul links (e.g., backhaul communication link 120). An IAB node 104 may include an IAB Mobile Termination (IAB-MT) controlled (e.g., scheduled) by the DU 165 of the associated IAB donor. The IAB-MT may include an independent set of antennas for relaying communications with the UE 115, or may share the same antenna (e.g., of the RU 170) of the IAB node 104 used for access via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, the IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., the IAB node 104, the UE 115) in an access network (e.g., downstream) relay chain or configuration. In such cases, one or more components of the disaggregated RAN architecture (e.g., one or more IAB nodes 104 or components of the IAB node 104) may be configured to operate in accordance with the techniques described herein.
[0038]
[0049] For the techniques described herein applied in the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture may be configured to support the techniques for capability indication for multiple services in a service-based wireless system described herein. For example, some operations described as being performed by the UE 115 or a network entity 105 (e.g., a base station 140) may additionally or alternatively be performed by one or more components of the disaggregated RAN architecture (e.g., an IAB node 104, a DU 165, a CU, a RU 170, a RIC, a SMO).
[0039]
[0050] The UE 115 may include or be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable terminology, and a "device" may also be referred to as a unit, a station, a terminal, or a client, among other examples. The UE 115 may also include or be referred to as a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, the UE 115 may include or be referred to as a Wireless Local Loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a Machine Type Communications (MTC) device, among other examples, which may be implemented in various items such as an appliance, a vehicle, a meter, or the like.
[0040]
[0051] The UEs 115 described herein may be capable of communicating with various types of devices, such as other UEs 115, which may act as relays, as shown in FIG. 1, as well as network entities 105 and network equipment, including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, among various examples.
[0041]
[0052] The UE 115 and the network entity 105 may wirelessly communicate 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 spectrum resources having a defined physical layer structure for supporting the communication link 125. For example, a carrier used for the communication link 125 may include a portion (e.g., a bandwidth part (BWP)) of an RF spectrum band operated according to one or more physical layer channels for a given radio access technique (e.g., 4G, 5G, 6G radio access technique). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling to coordinate operation on the carrier, user data, or other signaling. The wireless communication system 100 may support communication with the UE 115 using carrier aggregation or multi-carrier operation. The UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration. Carrier aggregation may be used with both frequency division duplexing (FDD) and time division duplexing (TDD) component carriers. Communication between the network entity 105 and other devices may refer to communication between a device and any part (e.g., entity, sub-entity) of the network entity 105. For example, when referring to the network entity 105, the terms "transmitting," "receiving," or "communicating" may refer to any part of the network entity 105 (e.g., base station 140, CU, DU 165, RU 170) of the RAN that communicates with another device (e.g., directly or via one or more other network entities 105).
[0042]
[0053] In some examples, such as carrier aggregation configurations, a carrier may also have acquisition or control signaling to coordinate operation with other carriers. A carrier may 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 may be identified according to a channel raster for discovery by the UE 115. A carrier may be operated in a standalone mode, where initial acquisition and connection may be made by the UE 115 via the carrier, or the carrier may be operated in a non-standalone mode, where connection is anchored using a different carrier (e.g., of the same or different radio access technology).
[0043]
[0054] The communication links 125 shown in the wireless communication system 100 may include, among other transmission configurations, downlink transmissions (e.g., forward link transmissions) from the network entity 105 to the UE 115, uplink transmissions (e.g., reverse link transmissions) from the UE 115 to the network entity 105, or both. A carrier may carry downlink or uplink communications (e.g., in FDD mode) or may be configured to carry downlink and uplink communications (e.g., in TDD mode).
[0044]
[0055] A carrier may be associated with a particular bandwidth of the RF spectrum, although in some examples, the carrier bandwidth may be referred to as the carrier or the “system bandwidth” of the wireless communication system 100. For example, the carrier bandwidth may be one of a set of bandwidths of a carrier of a particular radio access technology (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz (MHz)). Devices of the wireless communication system 100 (e.g., the network entity 105, the UE 115, or both) may have a hardware configuration that supports communication using a particular carrier bandwidth or may be configurable to support communication using one of the set of carrier bandwidths. In some examples, the wireless communication system 100 may include a network entity 105 or a UE 115 that supports simultaneous communication using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate using a portion (e.g., a sub-band, BWP) or all of the carrier bandwidth.
[0045]
[0056] A signal waveform transmitted over a carrier may be composed of multiple subcarriers (e.g., using a multi-carrier modulation (MCM) technique such as orthogonal frequency division multiplexing (OFDM) or discrete fourier transform spread OFDM (DFT-S-OFDM)). In a system employing MCM techniques, a resource element may relate to one symbol period (e.g., the time length of one modulation symbol) and one subcarrier, although the symbol period and subcarrier spacing may be inversely proportional. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both), such that a relatively large number of resource elements (e.g., during a transmission duration) and a relatively high order of the modulation scheme may correspond to a relatively higher communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, time resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may further increase data rates or data integrity for communications with UE 115.
[0046]
[0057] One or more numerologies for a carrier may be supported, which may include a subcarrier spacing (Δf) and a cyclic prefix. A carrier may be divided into one or more BWPs with the same or different numerologies. In some examples, a UE 115 may be configured with multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time, and communication for the UE 115 may be limited to one or more active BWPs.
[0047]
[0058] The time interval for the network entity 105 or the UE 115 is, for example, T S =1 / (Δf 最大 N f) seconds, where Δf 最大 may represent the supported subcarrier spacing, and N f may represent the supported Discrete Fourier Transform (DFT) size. The communication resource time intervals may be organized according to radio frames, each having a specified time length (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a System Frame Number (SFN) (e.g., ranging from 0 to 1023).
[0048]
[0059] Each frame may include multiple consecutively numbered subframes or slots, but each subframe or slot may have the same time length. In some examples, a frame may be divided (e.g., in the time domain) into subframes, but each subframe may be further divided into a certain amount of slots. Alternatively, each frame may include a variable number of slots, but the number of slots may depend on the subcarrier spacing. Each slot may include a certain number of symbol periods (e.g., depending on the length of a cyclic prefix prepended to each symbol period). In some wireless communication systems 100, a slot may be further divided into multiple minislots, which are associated with one or more symbols. Excluding the cyclic prefix, each symbol period may include one or more (e.g., N f The duration of a symbol period may depend on the subcarrier spacing or the frequency band of operation.
[0049]
[0060] A subframe, slot, minislot, or symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100, sometimes referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., the number of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., among bursts of shortened TTIs (sTTIs)).
[0050]
[0061] Physical channels may be multiplexed for communication using carriers according to various techniques. Physical control channels and physical data channels may be multiplexed for signaling over downlink carriers using, for example, one or more of a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique. A control region (e.g., a control resource set (CORESET)) for a physical control channel may be defined by a set of symbol periods and may span the system bandwidth of the carrier or a subset of the system bandwidth. One or more control regions (e.g., CORESETs) may be configured for a set of UEs 115. For example, one or more of the UEs 115 may monitor or search the control region for control information according to one or more search space sets, where each search space set may include one or more control channel candidates at one or more aggregation levels arranged in a cascaded manner. The aggregation level for a control channel candidate may refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space sets may include a common search space set configured for sending control information to multiple UEs 115 and a UE-specific search space set for sending control information to a specific UE 115.
[0051]
[0062] The network entity 105 may provide communication coverage via 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 for communication with the network entity 105 (e.g., using a carrier) and may be associated with an identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or other) for distinguishing neighboring cells. In some examples, a cell may also refer to a coverage area 110 or a portion (e.g., a sector) of a coverage area 110 in which the logical communication entity operates. Such a cell may range from a smaller area (e.g., a structure, a subset of a structure) to a larger area, depending on various factors such as the capabilities of the network entity 105. For example, a cell may be or include, among other things, a building, a subset of a building, or an outside space between or overlapping with the coverage area 110.
[0052]
[0063] A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs 115 that subscribe to service with the network provider that supports the macro cell. A small cell may be associated with a lower-power network entity 105 (e.g., a lower-power base station 140) compared to a macro cell, and the small cell may operate using the same or a different (e.g., licensed, unlicensed) frequency band as the macro cell. A small cell may provide unrestricted access to UEs 115 that subscribe to service with the network provider, or may provide restricted access to UEs 115 that have an association with the small cell (e.g., UEs 115 in a Closed Subscriber Group (CSG), UEs 115 associated with users in their homes or offices). A network entity 105 may support one or more cells and may also support communication via one or more cells using one or more component carriers.
[0053]
[0064] In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB)) that may provide access to different types of devices.
[0054]
[0065] In some examples, the network entities 105 (e.g., base stations 140, RUs 170) may be mobile and thus may provide communication coverage for moving coverage areas 110. In some examples, different coverage areas 110 associated with different techniques may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different techniques may be supported by different network entities 105. The wireless communication system 100 may include a heterogeneous network, for example, where different types of network entities 105 provide coverage to various coverage areas 110 using the same or different radio access techniques.
[0055]
[0066] Some UEs 115, such as MTC or IoT devices, may be low-cost or low-complexity devices and may provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC may refer to data communication techniques that allow devices to communicate with each other or with a network entity 105 (e.g., a base station 140) without human intervention. In some examples, M2M communication or MTC may include communication from devices that incorporate sensors or meters to measure or capture information and relay that information to a central server or application program that uses such information or presents it to a human who interacts with the application program. Some UEs 115 may be designed to collect information or 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, fleet management and tracking, remote security sensing, physical access control, and transaction-based business billing.
[0056]
[0067] The wireless communication system 100 may be configured to support ultra-reliable or low-latency communications, or various combinations thereof. For example, the wireless communication system 100 may be configured to support Ultra-Reliable Low-Latency Communication (URLLC). The UE 115 may be designed to support ultra-reliable, low-latency, or critical functionality. Ultra-reliable communications may include private or group communications, and may be supported by one or more services such as push-to-talk, video, data, etc. Support for ultra-reliable, low-latency functionality 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 herein.
[0057]
[0068] In some examples, the UEs 115 may be configured to support direct communication with other UEs 115 via device-to-device (D2D) communication links 135 (e.g., according to a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 of a group performing D2D communication may be within a coverage area 110 of a network entity 105 (e.g., a base station 140, an RU 170), which may support aspects of such D2D communication configured (e.g., scheduled) by the network entity 105. In some examples, one or more UEs 115 of such a group may be outside the coverage area 110 of the network entity 105, or may otherwise be unable or not configured to receive transmissions from the network entity 105. In some examples, a group of UEs 115 communicating via D2D communication may support a one-to-many (1:M) system in which each UE 115 transmits to each of the other UEs 115 in the group. In some examples, the network entity 105 may facilitate scheduling of resources for D2D communication. In some other examples, D2D communication may be performed between UEs 115 without the involvement of the network entity 105.
[0058]
[0069] In some systems, the D2D communication link 135 may be an example of a communication channel between vehicles (e.g., UEs 115), such as a sidelink communication channel. In some examples, the vehicles may communicate using vehicle-to-everything (V2X) communication, vehicle-to-vehicle (V2V) communication, or some combination thereof. The vehicles may signal information associated with traffic conditions, signal scheduling, weather, safety, emergencies, or any other information relevant to the V2X system. In some examples, the V2X system may communicate with roadside infrastructure, such as roadside units, or with a network via one or more network nodes (e.g., network entity 105, base station 140, RU 170) using vehicle-to-network (V2N) communication, or both.
[0059]
[0070] In some deployments, multiple RANs may be accessed by one or more UEs 115 or network entities 105, such as, for example, a 6G RAT and a 5G RAT. In some examples, the 6G RAT may be associated with the service-based network 130, while the 5G RAT may be associated with the 5G Core 190. The 5G Core 190 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The 5G Core 190 may be an Evolved Packet Core (EPC), 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 User Plane Function (UPF)) that routes packets or interconnects to external networks. The control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management for UEs 115 served by network entities 105 (e.g., base stations 140) associated with the 5G Core 190. User IP packets may be forwarded through a user plane entity, which may provide IP address allocation as well as other functions. The user plane entity may be connected to IP services 195 for one or more network operators.IP services 195 may include access to the Internet, intranet(s), IP Multimedia Subsystem (IMS), or packet-switched streaming services.
[0060]
[0071] The wireless communication system 100 may operate using one or more frequency bands, which may range from 300 megahertz (MHz) to 300 gigahertz (GHz). The 300 MHz to 3 GHz region is commonly known as the ultra-high frequency (UHF) region or decimeter band because wavelengths range in length from approximately 1 decimeter to 1 meter. Although UHF waves may be blocked or redirected by buildings and environmental features, sometimes referred to as clusters, the waves can penetrate structures sufficiently for a macrocell to provide service to UEs 115 located indoors. Communications using UHF waves may be associated with smaller antennas and shorter distances (e.g., less than 100 kilometers) compared to communications using lower frequencies and longer waves in the shortwave (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.
[0061]
[0072] The wireless communication system 100 may also operate using the Super High Frequency (SHF) region, also known as the centimeter band, which may range from 3 GHz to 30 GHz, or the Extremely High Frequency (EHF) region of the spectrum, also known as the millimeter band (e.g., 30 GHz to 300 GHz). In some examples, the wireless communication system 100 may support millimeter wave (mmW) communications between the UE 115 and the network entity 105 (e.g., base station 140, RU 170), although the EHF antennas on each device may be smaller and more closely spaced than UHF antennas. In some examples, such techniques may facilitate the use of antenna arrays within the device. However, propagation of EHF transmissions may experience greater attenuation and shorter distances than SHF or UHF transmissions. The techniques disclosed herein may be employed across transmissions using one or more different frequency ranges, and the designated use of bands across these frequency ranges may vary by country or regulatory body.
[0062]
[0073] The wireless communication system 100 may use both licensed and unlicensed RF spectrum bands. For example, the wireless communication system 100 may employ License Assisted Access (LAA), LTE-Unlicensed (LTE-U) radio access techniques, or NR techniques in an unlicensed band, such as the 5 GHz industrial, scientific, and medical (ISM) band. While operating using the unlicensed RF spectrum band, devices such as the network entity 105 and the UE 115 may employ carrier sensing for collision detection and avoidance. In some examples, operations using the unlicensed band may be based on a carrier aggregation configuration in conjunction with component carriers operating using a licensed band (e.g., LAA). Operations using the unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among other examples.
[0063]
[0074] A network entity 105 (e.g., base station 140, RU 170) or a UE 115 may be equipped with multiple antennas that can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of the network entity 105 or UE 115 may be located in one or more antenna arrays or antenna panels that can support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be collocated in an antenna assembly such as an antenna tower. In some examples, antennas or antenna arrays associated with the network entity 105 may be located at various geographic 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 of communications with the UE 115. Similarly, the UE 115 may include one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals transmitted through the antenna ports.
[0064]
[0075] The network entity 105 or the UE 115 may use MIMO communications to exploit multipath signal propagation and increase spectral efficiency by transmitting or receiving multiple signals via different spatial layers. Such techniques are sometimes referred to as spatial multiplexing. Multiple signals may be transmitted by a transmitting device, for example, via different antennas or different combinations of antennas. Similarly, multiple signals may be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports used for channel measurement and reporting. MIMO techniques include single-user MIMO (SU-MIMO), in which multiple spatial layers are transmitted to the same receiving device, and multiple-user MIMO (MU-MIMO), in which multiple spatial layers are transmitted to multiple devices.
[0065]
[0076] Beamforming, sometimes referred to as spatial filtering, directional transmission, or directional reception, is a signal processing technique that may be used at a transmitting or receiving device (e.g., network entity 105, UE 115) 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 may be achieved by combining signals communicated through antenna elements of an antenna array such that some signals propagating along a particular orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjusting signals communicated through antenna elements may include the transmitting or receiving device applying an amplitude offset, a phase offset, or both to signals carried through the antenna elements associated with the device. The adjustment associated with each of the antenna elements may 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).
[0066]
[0077] The network entity 105 or the UE 115 may use beam sweeping techniques as part of a beamforming operation. For example, the network entity 105 (e.g., base station 140, RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to perform a beamforming operation for directional communication with the UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted multiple times by the network entity 105 along different directions. For example, the network entity 105 may transmit signals according to different beamforming weight sets associated with different directions of transmission. The transmissions along different beam directions may be used to identify beam directions (e.g., by a transmitting device such as the network entity 105 or by a receiving device such as the UE 115) for subsequent transmission or reception by the network entity 105.
[0067]
[0078] Some signals, such as data signals associated with a particular receiving device, may be transmitted by a transmitting device (e.g., transmitting network entity 105, transmitting UE 115) along a single beam direction (e.g., a direction associated with a receiving device, such as receiving network entity 105 or receiving UE 115). In some examples, the beam direction associated with a transmission along a single beam direction may be determined based on signals transmitted along one or more beam directions. For example, UE 115 may receive one or more of the signals transmitted by network entity 105 along different directions, but may report to network entity 105 an indication of the signal that UE 115 received with the highest signal quality or otherwise acceptable signal quality.
[0068]
[0079] In some examples, transmission by a device (e.g., by the network entity 105 or the UE 115) may be performed using multiple beam directions, but the device may use a combination of digital precoding or beamforming to generate a composite beam for transmission (e.g., from the network entity 105 to the UE 115). The UE 115 may report feedback indicating precoding weights for one or more beam directions, but the feedback may correspond to a configured set of beams across the system bandwidth or one or more subbands. The network entity 105 may transmit reference signals (e.g., cell-specific reference signals (CRS), channel state information reference signals (CSI-RS)) that may or may not be precoded. The UE 115 may provide feedback for 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). Although these techniques are described with reference to signals transmitted along one or more directions by the network entity 105 (e.g., base station 140, RU 170), the UE 115 may employ similar techniques to transmit a signal multiple times along different directions (e.g., to identify a beam direction for subsequent transmission or reception by the UE 115) or to transmit a signal along a single direction (e.g., to transmit data to a receiving device).
[0069]
[0080] A receiving device (e.g., UE 115) may perform receiving operations according to multiple receiving configurations (e.g., directional intercept) when receiving various signals from the receiving device (e.g., network entity 105), such as synchronization signals, reference signals, beam selection signals, or other control signals. For example, the receiving device may perform receiving according to multiple receiving directions by receiving via different antenna subarrays, by processing received signals according to different antenna subarrays, by receiving according to different receive beamforming weight sets (e.g., different directional intercept weight sets) applied to signals received at multiple antenna elements of the antenna array, or by processing received signals according to different receive beamforming weight sets applied to signals received at multiple antenna elements of the antenna array, any of which may be referred to as “listening” according to different receiving configurations or receiving directions. In some examples, the receiving device may use a single receiving configuration to receive along a single beam direction (e.g., when receiving a data signal). A single receive configuration may be aligned along a beam direction determined based on interception from different receive configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or otherwise acceptable signal quality based on interception from multiple beam directions).
[0070]
[0081] In some examples, the wireless communication system 100 may include a packet-based network operating using a cloud platform, such as the service platform 150, that provides CN / RAN services 185. The CN / RAN services 185 may, in some examples, be hosted based on the deployment topology and capabilities with respect to service parameters associated with each service. Providing the CN / RAN services 185 enables separation of specific services (e.g., mobility, connection state management, security, paging, radio access services, quality of service (QoS) configuration and data services, UE capability management, location, messaging, among others) from transport functions (e.g., data radio bearer (DRB) management and logical channel (LC) management, data service configuration, among others). Service-based functionality (e.g., a message broker decouples radio network procedures from network delivery mechanisms) may allow the flexibility of some functions (e.g., L2 functions) to be hosted somewhere in the cloud, but may enable enhanced scalability, resilience, elasticity, agility, reuse, visibility, automation, failover, or any combination thereof (e.g., each service across the RAN and core network may be scaled independently by increasing or decreasing resources allocated independently across functions). Additionally, efficiency may be improved through providing real-time link management to the RAN edge, enabling adaptation in the DU 165 for more efficient activation, deactivation, or selection of features based on UE state.
[0071]
[0082] In some examples, the wireless communication system 100 supports signaling and other mechanisms that enable the UE 115 to establish a wireless connection with a service-based network 130 (e.g., a 6G network). In particular, aspects of the present disclosure relate to signaling between the UE 115, network entities 105 (e.g., DUs 165) of a service-based network architecture, and core network services (e.g., CN / RAN services 185) that enable the UE 115 to establish and maintain connections with different network entities 105, different core network services (e.g., CN / RAN services 185) provided by the network, or any combination thereof, based on the UE's capabilities communicated via capability services in the service-based network 130. Accordingly, the techniques described herein may enable the UE 115 to obtain a capability service context for the capability service and provide a capability indication of the UE 115 to the capability service. The capability service may receive the capability indication of the UE 115 and provide the information of the UE capabilities to one or more other services, to one or more network entities 105, or any combination thereof. One or more other services or one or more network entities 105 may use the indication of the capabilities of the UE 115 to determine various communication parameters.
[0072]
[0083] For example, a UE 115 of the wireless communication system 100 may establish a connection with a DU 165 of a network entity 105, but may receive control signaling indicating a capability service provided by the network (e.g., as part of a CN / RAN service 185). In some cases, the UE 115 may also receive a network address for the provided network service. The UE 115 may then send a capability service request to the network address of the capability service (via relaying by the DU 165), but may receive a capability service context for communicating with the capability service (via relaying by the DU 165). The UE 115 may then provide an indication of the UE 115's capabilities to the capability service, which may manage capability information for multiple UEs 115 and provide related capabilities to one or more other services or network entities 105. Thus, rather than each service having to separately request an indication of capabilities from the UE 115, the capability service may obtain the UE 115 capabilities and provide the relevant information to other services or entities.
[0073]
[0084] In some aspects, the UE 115 may be able to provide capability updates to a capability service. For example, the capabilities of the UE 115 may change from a previous UE 115 capability indication (e.g., due to RF emission limitations at the UE 115, thermal conditions at the UE 115, power conditions at the UE 115, etc.), and the updated capability indication may be provided to the capability service. In some examples, the UE 115 may also provide a time period for which the updated capability is a value (e.g., a time period for which the RF emission limitations change to allow the UE 115 to transmit using one or more frequency bands associated with the RF emission limitations). The capability service may receive the updated capability indication and, in response, provide the associated UE 115 capabilities to other services or network entities 105. In some examples, one or more other services or network entities 105 may provide subscription requests to the capability service, but may be informed of the updated capabilities based on the updated capability indication received at the capability service.
[0074]
[0085] The techniques described herein may enable a UE 115 to efficiently establish and maintain (e.g., subscribe to) a connection with a core network service provided by a service-based network, such as in a 6G system, based on the capabilities of the UE 115. In particular, the techniques described herein may enable the UE 115 to provide a capability indication to a capability service, where the capability service may coordinate with other CN / RAN services 185, other network entities 105, or any combination thereof, to provide communications using parameters according to the UE 115 capabilities. By enabling the UE 115 to provide a capability indication to a capability service, aspects of the present disclosure may enable the UE 115 to establish a connection with a wide variety of core network or RAN services that may be provided by different operators or entities without providing a separate capability indication for each service. Thus, the techniques described herein may enable the UE 115 to subscribe to different core network services on an a la carte basis according to the needs or requirements of each UE 115, thereby improving dedication and the overall user experience at the UE 115. Furthermore, by enabling the UE 115 to provide capability indications to capability services, the techniques described herein may enable the UE 115 to avoid communicating unnecessary or unwanted capability indications to multiple different core network services, thereby reducing control signaling within the network, improving resource utilization, and reducing power consumption at the UE 115.
[0075]
[0086] 2 illustrates an example wireless communication system 200 that supports techniques for capability indication for multiple services in a service-based wireless system in accordance with one or more aspects of the present disclosure. Aspects of wireless communication system 200 may implement or be implemented by aspects of wireless communication system 100. In some implementations, wireless communication system 200 illustrates an example architecture of a service-based wireless communication system, such as the 6G network described with reference to FIG. 1.
[0076]
[0087] The wireless communication system 200 may include one or more UEs 115 (e.g., UE 115-a), one or more network entities (e.g., network entity 105-a), and a service-based network 205. In some aspects, the service-based network 205 may be configured to communicate with or interface with a RAN 210 of the wireless communication system 200, where the RAN 210 includes one or more network entities (e.g., network entity 105-a). The service-based network 205 may support or provide a set of core network services 215 (e.g., core network services 215-a, 215-b, 215-c, 215-d, 215-d, 215-e). In some implementations, the service-based network 205 may include or be associated with a cloud platform, where each core network service 215 is hosted at a respective network address within the cloud platform.
[0077]
[0088] The UE 115-a may communicate with the network entity 105-a using one or more communication links 220, which may include an example of an access link (e.g., a Uu link). The communication link 220 may include a bidirectional link that may include both uplink and downlink communications. Similarly, the network entity 105-a of the RAN 210 may be configured to communicate (e.g., interface) with the service-based network 205 via one or more communication links (e.g., communication link 225), where the communication link 225 may be configured to facilitate bidirectional communications between the network entity 105-a and each of the respective core network services 215 of the service-based network 205.
[0078]
[0089] 2, the wireless communication system 200 may exhibit a service-based architecture in which entities of the RAN 210 (e.g., network entity 105-a) are configured to connect the UE 115-a to core network services 215 of the service-based network 205. In particular, the RAN 210 (e.g., network entity 105-a) may be configured to relay communications between the UE 115-a and various core network services 215 of the service-based network to enable the UE 115-a to establish and maintain a wireless connection with each core network service 215 for exchanging communications associated with various network functionalities supported by the respective core network service 215. In other words, the wireless communication system 200 may enable the UE 115-a to “subscribe” to each core network service 215 on an a la carte basis, depending on the needs or requirements of the UE 115-a. In this regard, different UEs 115 within the wireless communication system 200 may be able to subscribe to different subsets of the core network services 215 depending on the capabilities of the UE 115, the applications running on the UE 115, the mobility of the UE 115, etc.
[0079]
[0090] Each core network service 215 may be associated with a respective network address within the service-based network 205. Stated another way, each core network service 215 may be hosted in one or more components of a cloud-based network, where each component of the core network service 215 may be associated with a respective network address. Each core network service 215 may be provided by a network provider, a third-party entity, etc., where each core network service 215 is configured to support a respective service or functionality provided to components of the wireless communication system 200 (e.g., UE 115-a, network entity 105-a).
[0080]
[0091] Different services, functionalities, and core network functions that may be supported or provided by each core network service 215 may include, but are not limited to, capability services, mobility services, security services, privacy services, location services, etc. For example, a first core network service 215-a may include a core network mobility service that hosts information and provides signaling to facilitate geographic movement of the UE 115-a throughout the wireless communication system. As another example, a second core network service 215-b may include a security service that provides security and encryption services to subscribing UEs 115 within the wireless communication system 200.
[0081]
[0092] In some aspects, each core network service 215 may include a respective API configured to facilitate wireless communication with the network entity 105-a and the UE 115-a, such as the network service API 180 illustrated in FIG. 1. The API in each core network service 215 may include a routing API, a configuration API, or both. The routing API may be configured for service data unit communication between the UE 115-a and the respective core network service 215. In comparison, the configuration API may be configured to facilitate communication between the network entity 105-a and the respective core network service 215 to negotiate service requirements and service-specific behaviors.
[0082]
[0093] In some aspects, the network entity 105-a (e.g., eDU) may facilitate traffic routing (e.g., service data unit routing) from the UE 115-a to the core network services 215 (or vice versa). The network entity 105-a may facilitate traffic routing between respective devices directly, via other network entities 105-a, via a proxy, or any combination thereof. Further, in some cases, the UE 115-a may be communicatively coupled to multiple network entities 105 (e.g., dual connectivity), where the multiple network entities 105 facilitate traffic routing with the same or different sets of core network services 215. Additionally, the network entity 105-a may support service configurations or service contexts associated with communication parameters within the system, such as QoS flows, security, and UE 115 service contexts. In some aspects, the communication link 220 between the network entity 105-a and the UE 115-a may be associated with an access stratum configuration that facilitates over-the-air service awareness. The access stratum configuration may include logical channels, access stratum security, access stratum context, etc. For example, the access stratum configuration may be associated with service-specific configuration (e.g., logical channels corresponding to QoS flows for each respective core network service 215) and service-independent configuration (e.g., parameters common to all core network services 215).
[0083]
[0094] The service-based wireless communications system 200 (e.g., a 6G network) illustrated in FIG. 2 may exhibit several differences and advantages compared to some other types of wireless systems, such as networks that instead exhibit a relatively more vertically hierarchical architecture that includes many “layers” of different devices that perform functions for the network. A more hierarchical structure may result in processing and other functions being performed in multiple devices (e.g., the network entity 105 and one or more back-end devices), thereby leading to inefficient use of resources and high power consumption. Additionally, the back-end architecture of a network with a more vertically hierarchical architecture may be owned and maintained by a few operators, which may make it difficult for other parties / entities to integrate with such a system, and the services provided to UEs 115 and other devices may be difficult to customize within such a system.
[0084]
[0095] In comparison, the service-based wireless communications system 200 illustrated in Figure 2 exhibits a flatter, horizontal architecture that allows each function of the wireless communications system to be distributed across different components (e.g., core network services 215) of the system. For example, such functions and protocols may be divided and distributed across a set of core network services 215, such that each core network service 215 may support or enable a subset of the capabilities and functionality of a traditional wireless communications system. In other words, a service-based architecture may allow functions and protocols to be divided into self-contained services (e.g., core network services 215) as compared to components that provide all-encompassing network functions and protocols (e.g., modularization of network services / functionality across multiple core network services 215).
[0085]
[0096] In this regard, the wireless communications system 200 may represent an example of a cloud-native platform configured to host mergers of CORE and RAN services, which may simplify protocols and reduce duplication of processing operations across the CORE and RAN (e.g., redistribution of CORE and RAN 210 services). In other words, convergence of RAN 210 and CN functions may reduce repeated operations and functionality to serve one UE at different layers.
[0086]
[0097] The wireless communications system 200 may extend benefits associated with the service-based architecture of the service-based network 205 to the RAN 210, including the benefits of increased scalability, resilience, elasticity, agility, reuse, visibility, automation, and failover. Additionally, the service-based architecture may enable each core network service 215 across the RAN 210 and CORE to scale independently by increasing or decreasing the resources allocated across each core network service 215 independently.
[0087]
[0098] In some implementations, as described in further detail herein, the wireless communication system 200 may support signaling that enables the UE 115-a to establish and maintain communication with a core network service 215 of a service-based network 205, such as a 6G network, over transport channels configured by the transport services. In particular, aspects of the present disclosure relate to signaling that enables the UE 115-a to provide (e.g., via the network entity 105-a) to the transport services QoS metrics (e.g., latency, reliability, timing of first packet, etc.), a Buffer Status Report (BSR), a requested service type (e.g., best effort with security, high throughput without security, low latency data, etc.), or any combination thereof. The transport service may communicate with the network entity 105-a (e.g., DU) to configure scheduling, resources, and QoS requirements for the transport radio bearers, and the network entity 105-a may determine the radio configuration based on information received from the transport service, such as physical (PHY) layer parameters (e.g., number of carriers, logical channel mapping to service layer transport radio bearers, uplink / downlink grants, etc.) and L2 parameters (e.g., MAC and RLC parameters, security parameters, Packet Data Convergence Protocol (PDCP) parameters, or any combination thereof). The UE 115-a may communicate, via the network entity 105-a, information to be transported via the transport service based at least in part on the physical resource configuration.
[0088]
[0099] 3 illustrates an example of a network architecture 300 (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that supports techniques for capability indication for multiple services in a service-based wireless system according to one or more aspects of the present disclosure. The network architecture 300 may represent an example for implementing one or more aspects of the wireless communication system 100. The network architecture 300 may include a service-based network 305, which may be an example of the service-based network 130 or 205 that communicates with the DU 165-a via the link 120-b. In this example, the DU 165 may communicate directly with the 5G core 190-a via the backhaul communication link 120-a, or may also communicate with one or more DUs 310, which may communicate indirectly with the 5G core 190-a via one or more disaggregated network entities 105 (e.g., a quasi-RT RIC 330-a via an E2 link, or a non-RT RIC 330-b associated with the SMO 335 (e.g., an SMO framework), or both). The DUs 310 may communicate with one or more DUs 165-a via respective midhaul communication links 315 (e.g., F1 interfaces). The DUs 165-a may communicate with one or more RUs 170-a via respective fronthaul communication links 168-a. The RUs 170-a may be associated with respective coverage areas 110-a, but may communicate with the UEs 115-b via one or more communication links 125-a. In some implementations, the UE 115-b may be served by multiple RUs 170-a simultaneously.
[0089]
[0100] Each of the network entities 105 (e.g., CU 310, DU 165-a, RU 170-a, non-RT RIC 330-a, quasi-RT RIC 330-b, SMO 335, Open Cloud (O-Cloud) 320, Open eNBs (O-eNBs) 325) of network architecture 300 may include one or more interfaces or may be coupled with one or more interfaces configured to receive or transmit signals (e.g., data, information) over a wired or wireless transmission medium. Each network entity 105, or an associated processor (e.g., controller) that provides instructions to the interfaces of the network entity 105, may be configured to communicate with one or more of the other network entities 105 over a transmission medium. For example, a network entity 105 may include a wired interface configured to receive or transmit signals to one or more of the other network entities 105 over a wired transmission medium. Additionally or alternatively, the network entity 105 may include a wireless interface, which may include a receiver, a transmitter, or a transceiver (such as an RF transceiver), configured to receive and / or transmit signals to one or more of the other network entities 105 via a wireless transmission medium.
[0090]
[0101] In some examples, the CU 310 may host one or more upper layer control functions. Such control functions may include RRC, PDCP, SDAP, etc. Each control function may be implemented with an interface configured to communicate signals with other control functions hosted by the CU 310. The CU 310 may be configured to handle user plane functionality (e.g., CU-UP), control plane functionality (e.g., CU-CP), or a combination thereof. In some examples, the CU 310 may be logically divided into one or more CU-UP units and one or more CU-CP units. The CU-UP units, when implemented in an O-RAN configuration, may communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 310 may be implemented to communicate with the DU 165-a, as needed, for network control and signaling.
[0091]
[0102] Each DU 165-a may correspond to a logical unit including one or more functions (e.g., base station function, RAN function) for controlling the operation of one or more RUs 170-a. In some examples, when interfacing with the service-based network 305, the DU 165-a may host one or more APIs for one or more services of the service-based network 305 and one or more corresponding services in one or more UEs 115-b. In some examples, when interfacing with the DU 310, the DU 165-a may at least partially host one or more of an RLC layer, a MAC layer, and one or more aspects of a PHY layer (e.g., upper PHY layers, such as modules for FEC encoding and decoding, scrambling, modulation and demodulation, etc.), at least in part according to a functional division such as that defined by the 3rd Generation Partnership Project (3GPP). In some examples, the DU 165-a may further host one or more lower PHY layers. Each layer may be implemented with an interface configured to communicate signals with other layers hosted by the DU 165-a or with control functions hosted by the CU 310.
[0092]
[0103] In some examples, lower layer functionality may be implemented by one or more RUs 170-a. For example, an RU 170-a controlled by a DU 165-a may correspond to a logical node hosting RF processing functions, or lower PHY layer functions (e.g., performing Fast Fourier Transforms (FFTs), inverse FFTs (iFFTs), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on a functional division, such as a lower layer functional division. In such an architecture, an RU 170-a may be implemented to handle over-the-air (OTA) communications with one or more UEs 115-b. In some implementations, real-time and non-real-time aspects of control and user plane communications with the RU(s) 170-a may be controlled by the corresponding DU 165-a. In some examples, such a configuration may enable the DU 165-a and CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.
[0093]
[0104] The SMO 335 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network entities 105. For non-virtualized network entities 105, the SMO 335 may be configured to support deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operations and maintenance interface (e.g., an O1 interface). For virtualized network entities 105, the SMO 335 may be configured to interact with a cloud computing platform (e.g., O-Cloud 320) to perform network entity lifecycle management (e.g., instantiate virtualized network entities 105) via a cloud computing platform interface (e.g., an O2 interface). Such virtualized network entities 105 may include, but are not limited to, the DU 310, DU 165-a, RU 170-a, and quasi-RT RIC 330-a. In some implementations, the SMO 335 may communicate with components configured according to a 4G RAN (e.g., via the O1 interface). Additionally or alternatively, in some implementations, the SMO 335 may communicate directly with one or more RUs 170-a via an O1 interface. The SMO 335 may also include a non-RT RIC 330-b configured to support the functionality of the SMO 335.
[0094]
[0105] The non-RT RIC 330-b may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) or machine learning (ML) workflows, including model training and updates, or policy-based guidance of applications / features in the quasi-RT RIC 330-a. The non-RT RIC 330-b may be coupled to or communicate with the quasi-RT RIC 330-a (e.g., via an A1 interface). The quasi-RT RIC 330-a may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources through data collection and action via interfaces (e.g., via an E2 interface) connecting one or more CUs 310, one or more DUs 165-a, or both, and the O-eNB 325 with the quasi-RT RIC 330-a.
[0095]
[0106] In some examples, the non-RT RIC 330-b may receive parameters or external enrichment information from an external server to generate AI / ML models deployed to the quasi-RT RIC 330-b. Such information may be utilized by the quasi-RT RIC 330-a, but may be received at the SMO 335 or the non-RT RIC 330-b from non-network data sources or from network functions. In some examples, the non-RT RIC 330-b or the quasi-RT RIC 330-a may be configured to adjust RAN behavior or performance. For example, the non-RT RIC 330-b may employ AI / ML models to monitor long-term trends and patterns in performance and implement corrective actions through the SMO 335 (e.g., reconfiguration via O1) or by creating RAN management policies (e.g., A1 policies).
[0096]
[0107] In some implementations, as described in further detail herein, the network architecture 300 may support signaling that enables the UE 115 to establish and maintain communications with core network services of a service-based network, such as a 6G network. In particular, aspects of the present disclosure relate to signaling between the UE 115, the DU 165, and the core network services that enables the UE 115 to provide transport parameters to transport services that comprise one or more radio bearers that are mapped to one or more logical channels, where two or more radio bearers may be mapped to a single logical channel.
[0097]
[0108] 4 illustrates an example transport channel structure 400 that supports techniques for data transport in a service-based wireless system in accordance with one or more aspects of the present disclosure. The transport channel structure 400 may be implemented by aspects of the wireless communication system 100, the wireless communication system 200, the network architecture 300, or some combination thereof. For example, a UE (e.g., the UE 115 described with reference to FIGS. 1-3) and a network entity (e.g., the network entity 105, such as the DU 165 described with reference to FIGS. 1-3) may implement the channel transport structure 400.
[0098]
[0109] According to various aspects, the transport protocol structure with transport channel structure 400 may enable cloud-native protocol design for the core network, the RAN, and the UE. In some aspects, the physical layer 405 may provide PHY functionality (e.g., RF processing functionality, performing FFT, iFFT, digital beamforming, PRACH extraction and filtering, etc.). The physical layer 405 may be coupled with the L2 410, which may provide RLC processing, SDAP processing, PDCP processing, MAC processing, or any combination thereof. As described herein, one or more different services 415 may provide higher layer processing (e.g., L3 and higher layer processing, and optionally one or more L2 functions). 4 illustrates three services 415, including a first service 415-a, a second service 415-b, and a third service 415-c, each of which may have an associated transport radio bearer 420 (e.g., a first transport radio bearer 420-a, a second transport radio bearer 420-b, and a third transport radio bearer 420-c). Although three services 415 and associated transport radio bearers 420 are illustrated in FIG. 4, other examples may have more or fewer services 415.
[0099]
[0110] According to some aspects, one or more transport radio bearers (e.g., which may transport information associated with signaling radio bearers and data radio bearers, such as those used in 5G networks) may be mapped to a single channel (e.g., logical channel) between a UE and a network entity. In some cases, a network entity, such as a DU, may accumulate requests from different services (e.g., performing CU and AMF functions). In some cases, transport radio bearers may be service-specific, but QoS targets are provided per service 415, per transport radio bearer 420. In some cases, packets transported over the transport radio bearer 420 may include an indication of the associated service. In some cases, the mapping between the transport radio bearer 420 and the logical channel may be provided by the transport service. In some cases, such mapping may be a one-to-one mapping (e.g., one logical channel to one transport radio bearer 420), a many-to-one mapping (e.g., one logical channel to multiple transport radio bearers 420, which may be a default mode of operation if no mapping is requested from the transport service), or a many-to-many mapping (e.g., multiple logical channels to multiple transport radio bearers 420, which may be associated with the same or different services, but may be provided across services if in the same public IP or private IP subnet). Thus, each service 415 may divide its traffic across multiple channels (e.g., multiple logical channels for signaling information, low priority data, and high priority data, etc.). In some cases, a many-to-many mapping within a service 415 may enable traffic differentiation within an application (e.g., audio vs. video, camera position vs. virtual reality streaming, etc.), which may enable a scheduler to identify traffic types based on the channel and schedule accordingly.
[0100]
[0111] As described herein, services 415 may include a transport service, where a transport service API in the UE may initiate a request with an associated transport service in the network to establish a transport radio bearer. In some cases, one or more QoS targets may be provided (e.g., from the UE sending the request), in which case the transport service may configure the serving DU to enable correct delivery of the service, including the QoS targets, for the connection. The transport service may negotiate QoS requirements and manage end-to-end bearers / flows with the UE. If the transported data is for best-effort service, the associated bearer or flow may operate on an existing IP service (e.g., a previously established IP service). Another service may perform admission control similar to the 5G CU-CP function. In some cases, an API may be used for the interface between the UE and the transport service, which may provide configuration of traffic flow information (e.g., QoS requirements, buffer status reports, etc.) and traffic patterns (e.g., uplink / downlink traffic patterns). In some cases, APIs in the network may expose scheduler loading and constraints, expose discontinuous reception (DRX), configuration options, expose real-time QoS measurements at the UE and network, or any combination thereof.
[0101]
[0112] A UE operating in such a system may establish a context with one or more transport services in the network (e.g., contexts for best-effort mobility with security, high throughput without security, low latency data, etc.). The UE may maintain an active transport state, such as by sending a BSR report to the transport service, when the service is in use and the UE is connected to a network device (e.g., a DU or other RAN node). In some cases, the UE may perform throughput throttling for the downlink and uplink directions. In some cases, the UE may request the transport service to throttle downlink traffic. Additionally or alternatively, the UE may throttle uplink traffic based on a request from the service 415. In some cases, the UE may determine that a transport service has become inactive through data inactivity, in-band or out-of-band data indications, explicit signaling from the service 415, the UE disconnecting from a network entity, or any combination thereof, a local protocol error (e.g., if signaling to the service repeatedly fails), or the like.
[0102]
[0113] In some cases, the UE may determine the need to use one or more transport services for which the UE has established a context and which are currently inactive. In some cases, the UE may send an activation request to a network entity (e.g., a DU), which includes one or more services to activate, including routing information, optionally additional service protocol messages to be delivered for the services, and additional information such as an initial buffer status deport per transport radio bearer, a deadline for delivering the first packet, etc. In some cases, the network entity may provide the UE with a confirmation in the activation response of which services are activated and, if confirmed, may move the transport service(s) to active. In some cases, for each requested service that was not activated, the UE may receive a cause of activation failure (e.g., a cause code) either directly in local signaling or in one or more service protocol messages. In such cases, the UE may delete the context for the service based on the failure cause, but the UE may re-establish a context with the service or attempt to establish a context with another service based on the failure. In some cases, optionally, in the case of a UE-controlled connection, if the UE determines that no more services are active or that a UE buffer associated with a service is empty (e.g., in the case of a transport service, the UE may have transmitted all data or the data has expired locally), the UE may send a request to the network entity to release the connection. The request may include further signaling to one or more services, if they are active.
[0103]
[0114] In some cases, a network entity (e.g., a DU) may perform operations associated with a transport service. For example, the network entity may establish a connection with a UE, which may include configuring the UE with physical resources (PHY / L2) to support the transport service, dynamically updating the configuration as service requirements change, activating carriers, and providing uplink and downlink grants. In some cases, based on a UE request, the network entity may send an activation request to one or more services that may provide logical channel mapping to service layer transport radio bearers. The network entity may communicate with the transport service via a communication protocol that provides other transport services such as packet delimitation and flow control. In some cases, the network entity may receive a request from one or more services to maintain a context for the service. The network entity may at a later stage receive an indication from one or more services (or UEs) that the service has become inactive, or may determine that the UE has no active service, and may release the local connection for the UE based on that determination. If any services were still active, the network entity may indicate to those services that the connection is to be released (eg, further including a service protocol message if provided by the UE).
[0104]
[0115] In some cases, a transport service may perform various operations related to data transport. For example, the transport service may establish a context with a UE connected to a network entity (e.g., a DU) and determine that the UE is active. In some cases, the transport service may be provided at a defined layer (e.g., the IP layer or the PDCP layer). In some cases, the transport service may require the network entity to maintain an active context for the UE, which may help provide an expected quality of service for each transport radio bearer. In some cases, the transport service may also maintain a context with the network entity (e.g., a DU) to which the UE is connected (e.g., addressing behavior at the network entity while the service is active, service-related configurations), which may include updating the requirements over time, such as dynamically or periodically providing expected throughput requirements, providing feedback on received quality of service, or any combination thereof. In some cases, the transport service may initiate a transition to an inactive mode. For example, it may be determined that a service is no longer active (e.g., based on closing / unlocking an end-to-end protocol or a lack of transmission for a certain period of time), and the transport service may notify the network entity that the service is no longer active. In other cases, the network entity may initiate the transition to the inactive mode through an indication that the transport service has been deactivated at the network entity (e.g., due to a local disconnection or failure) or an indication that the transport service is inactive for the UE.When a UE is moved to an inactive state in a service, in some cases the transport service may retain the UE context or may not retain the latest information associated with the network entities to which the UE is connected (e.g., if the UE reconnects on the same DU, it either releases the network entity information or retains only the "last connected DU" set of information).
[0105]
[0116] 5 illustrates an example process flow 500 supporting a technique for data transport in a service-based wireless system according to one or more aspects of the present disclosure. Process flow 500 may include a UE 115-c, which may be an example of a UE 115 described herein, and a network entity 105-b (e.g., a DU 165) described herein. Process flow 500 may include a transport service 505, which may be an example of a transport service described herein. In the following description of process flow 500, operations between the UE 115-c, the network entity 105-b, and the transport service 505 may be transmitted in an order different from the example order shown, or operations performed by the UE 115-c, the network entity 105-b, and the transport service 505 may be performed in a different order or at different times. Some operations may also be omitted from process flow 500, while other operations may be added to process flow 500.
[0106]
[0117] At 510, the UE 115-c and the network entity 105-b may perform connection establishment according to a network connection establishment technique (e.g., an RRC connection establishment procedure). Possibly, as part of or subsequent to the connection establishment, the UE 115-c may receive control information from the network entity 105-b indicating routing information for transport services 505 for a set of core network services provided by a service-based network configured to interface with a RAN associated with the network entity 105-b.
[0107]
[0118] At 515, the UE 115-c and the network entity 105-b may perform a transport service establishment procedure to establish a context for the transport service 505 and the UE 115-c. For example, the UE 115-c may send a request including routing information for the transport service 505 (which may be provided by another network service, such as a discovery service) to the network entity 105-b. The network entity 105-b may communicate the request to the transport service 505 based on the routing information. For example, the request may be sent to the network entity 105-b for relaying to a network address associated with the transport service 505, where the network address is based on the routing information. Based on the request, the transport service 505 may communicate a response to the network entity 105-b, which may include service context information and logical channel mappings to one or more transport specific bearers. The network entity 105-b may send the service context information to the UE 115-c.
[0108]
[0119] At 520, the transport service 505 may exchange information with the network entity 105-b for transport configuration. For example, the transport service 505 may provide information regarding one or more transport radio bearers, one or more logical channels, and a mapping of one or more transport radio bearers to one or more logical channels.
[0109]
[0120] At 525, the network entity 105-b and the UE 115-c may exchange information related to wireless channel configuration for wireless communication (e.g., RAN communication). For example, the network entity 105-b and the UE 115-c may communicate parameters for one or more logical channels and one or more transport radio bearers.
[0110]
[0121] At 530, the UE 115-c and the transport service 505 may communicate a transport service configuration. For example, the transport service configuration may include configuration of traffic flow information (e.g., QoS targets), configuration of traffic patterns, etc. At 535, the UE 115-c and the transport service 505 may exchange data in accordance with the transport service configuration.
[0111]
[0122] 6 shows a block diagram 600 of a device 605 supporting techniques for data transport in a service-based wireless system in accordance with one or more aspects of the present disclosure. The device 605 may be an example of an aspect of a UE 115 as described herein. The device 605 may include a receiver 610, a transmitter 615, and a communications manager 620. The device 605 may also include a processor. Each of these components may communicate with one another (e.g., via one or more buses).
[0112]
[0123] The receiver 610 may provide a 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 techniques for data transport in a service-based wireless system). The information may be passed to other components of the device 605. The receiver 610 may utilize a single antenna or a set of multiple antennas.
[0113]
[0124] The transmitter 615 may provide a means for transmitting signals generated by other components of the device 605. For example, the transmitter 615 may 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 techniques for data transport in a service-based wireless system). In some examples, the transmitter 615 may be collocated with the receiver 610 within a transceiver module. The transmitter 615 may utilize a single antenna or a set of multiple antennas.
[0114]
[0125] The communications manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof may be examples of means for implementing various aspects of the techniques for data transport in service-based wireless systems described herein. For example, the communications manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof may support a method for implementing one or more of the functions described herein.
[0115]
[0126] In some examples, the communications manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry). The hardware may include a processor, a digital signal processor (DSP), a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting means for performing the functions described in this disclosure. In some examples, the processor and memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by the processor executing instructions stored in the memory).
[0116]
[0127] Additionally or alternatively, in some examples, the communications manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communications management software or firmware). When implemented in code executed by a processor, the functionality of the communications manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., that may be configured as or otherwise support a means for performing the functions described in this disclosure).
[0117]
[0128] In some examples, the communications manager 620 may be configured to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting) using or otherwise cooperating with the receiver 610, the transmitter 615, or both. For example, the communications manager 620 may receive information from the receiver 610, send information to the transmitter 615, or be integrated in combination with the receiver 610, the transmitter 615, or both to acquire information, output information, or perform various other operations described herein.
[0118]
[0129] The communications manager 620 may support wireless communications in the UE according to examples disclosed herein. For example, the communications manager 620 may be configured as or otherwise support a means for communicating a first service message via the distributed unit to establish a first transport radio bearer with a first transport service provided by the service-based network, the first service message indicating one or more attributes associated with information to be transported via the first transport radio bearer. The communications manager 620 may be configured as or otherwise support a means for receiving, from the distributed unit in response to the first service message, a physical resource configuration for communications associated with the first transport service and a mapping of the first transport radio bearer to a first channel (e.g., a first logical channel) between the UE and the distributed unit. The communications manager 620 may be configured as or otherwise support a means for communicating information to be transported via the first transport service via the distributed unit based on the physical resource configuration.
[0119]
[0130] By including or configuring a communications manager 620 according to the examples described herein, the device 605 (e.g., a processor controlling or otherwise coupled to the receiver 610, the transmitter 615, the communications manager 620, or a combination thereof) may support techniques for reduced processing, reduced power consumption, and more efficient utilization of communications resources.
[0120]
[0131] 7 shows a block diagram 700 of a device 705 supporting techniques for data transport in a service-based wireless system in accordance with one or more aspects of the present disclosure. The device 705 may be an example of an aspect of the device 605 or UE 115 described herein. The device 705 may include a receiver 710, a transmitter 715, and a communications manager 720. The device 705 may also include a processor. Each of these components may communicate with one another (e.g., via one or more buses).
[0121]
[0132] The receiver 710 may provide a 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 techniques for data transport in a service-based wireless system). The information may be passed to other components of the device 705. The receiver 710 may utilize a single antenna or a set of multiple antennas.
[0122]
[0133] The transmitter 715 may provide a means for transmitting signals generated by other components of the device 705. For example, the transmitter 715 may 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 techniques for data transport in a service-based wireless system). In some examples, the transmitter 715 may be collocated with the receiver 710 within a transceiver module. The transmitter 715 may utilize a single antenna or a set of multiple antennas.
[0123]
[0134] Device 705, or its various components, may be an example of a means for implementing various aspects of the techniques for data transport in a service-based wireless system described herein. For example, communications manager 720 may include transport services manager 725, transport radio bearer manager 730, or any combination thereof. Communications manager 720 may be an example of an aspect of communications manager 620 described herein. In some examples, communications manager 720, or its various components, may be configured to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting) using or otherwise cooperating with receiver 710, transmitter 715, or both. For example, communications manager 720 may receive information from receiver 710, transmit information to transmitter 715, or be integrated in combination with receiver 710, transmitter 715, or both to acquire information, output information, or perform various other operations described herein.
[0124]
[0135] The communications manager 720 may support wireless communications in the UE according to examples disclosed herein. The transport service manager 725 may be configured as or otherwise support a means for communicating a first service message via the distributed unit to establish a first transport radio bearer with a first transport service provided by the service-based network, the first service message indicating one or more attributes associated with information to be transported via the first transport radio bearer. The transport radio bearer manager 730 may be configured as or otherwise support a means for receiving, from the distributed unit in response to the first service message, a physical resource configuration for communications associated with the first transport service and a mapping of the first transport radio bearer to a first channel between the UE and the distributed unit. The transport radio bearer manager 730 may be configured as or otherwise support a means for communicating information to be transported via the first transport service via the distributed unit based on the physical resource configuration.
[0125]
[0136] 8 shows a block diagram 800 of a communications manager 820 supporting techniques for data transport in a service-based wireless system according to one or more aspects of the present disclosure. Communications manager 820 may be an example of aspects of communications manager 620, communications manager 720, or both, described herein. Communications manager 820, or its various components, may be an example of a means for implementing various aspects of the techniques for data transport in a service-based wireless system described herein. For example, communications manager 820 may include a transport services manager 825, a transport radio bearer manager 830, a radio bearer mapping manager 835, a packet attribute manager 840, a BSR manager 845, a data throughput manager 850, or any combination thereof. Each of these components may communicate directly or indirectly with one another (e.g., via one or more buses).
[0126]
[0137] The communications manager 820 may support wireless communications in the UE according to examples disclosed herein. The transport service manager 825 may be configured as or otherwise support a means for communicating a first service message via the distributed unit to establish a first transport radio bearer with a first transport service provided by the service-based network, the first service message indicating one or more attributes associated with information to be transported via the first transport radio bearer. The transport radio bearer manager 830 may be configured as or otherwise support a means for receiving, from the distributed unit in response to the first service message, a physical resource configuration for communications associated with the first transport service and a mapping of the first transport radio bearer to a first channel between the UE and the distributed unit. In some examples, the transport radio bearer manager 830 may be configured as or otherwise support a means for communicating information to be transported via the first transport service via the distributed unit based on the physical resource configuration.
[0127]
[0138] In some examples, the radio bearer mapping manager 835 may be configured as or otherwise support a means for mapping one or more transport radio bearers to a first logical channel, each of the transport radio bearers having an associated transport service. In some examples, the first service message includes one or more quality of service targets associated with information to be transported via the first transport service. In some examples, the information to be transported via the first transport service is transmitted using a set of multiple packets, each packet of the set of multiple packets including an indication of the first transport radio bearer. In some examples, the first transport radio bearer provides communication for both signaling information and data associated with the first transport service.
[0128]
[0139] In some examples, to support communicating the first service message, packet attribute manager 840 may be configured as or otherwise support a means for communicating one or more attributes associated with information to be transported via the first transport service, such as one or more quality of service parameters including a latency target, a throughput target, a security level, or any combination thereof.
[0129]
[0140] In some examples, the BSR manager 845 may be configured as or otherwise support a means for communicating one or more buffer status reports to the first transport service via the distributed unit in order to maintain an active state in the first transport service.
[0130]
[0141] In some examples, data throughput manager 850 may be configured as or otherwise support a means for receiving an indication to throttle information to be transported via a first transport service. In some examples, data throughput manager 850 may be configured as or otherwise support a means for throttling information communicated via a first transport service, regardless of the amount of information communicated via one or more other transport services different from the first transport service.
[0131]
[0142] In some examples, the transport service manager 825 may be configured as or otherwise support a means for communicating, via the distributed unit, a second service message indicating deactivation of a first transport radio bearer associated with the first transport service. In some examples, the transport service manager 825 may be configured as or otherwise support a means for obtaining further information to be transported via the first transport radio bearer following deactivation of the first transport service. In some examples, the transport service manager 825 may be configured as or otherwise support a means for communicating, via the distributed unit, a third service message for activating the first transport radio bearer. In some examples, the third service message includes one or more indications of a buffer status report associated with the first transport radio bearer, a target delivery time for a first packet of data of the further information to be transported via the first transport radio bearer, or any combination thereof.
[0132]
[0143] In some examples, the transport service manager 825 may be configured as or otherwise support a means for communicating, via the distributed unit, a second service message indicating release of a first transport radio bearer associated with the first transport service, where the second service message is communicated in response to a lack of information to be transported over the first transport radio bearer, expiration of data associated with the first transport radio bearer, or any combination thereof.
[0133]
[0144] In some examples, the transport radio bearer manager 830 may be configured or otherwise support a means for receiving an updated physical resource configuration from the distributed unit in response to an updated configuration associated with the first transport service. In some examples, the transport radio bearer manager 830 may be configured or otherwise support a means for communicating information to be transported via the first transport service via the distributed unit based on the updated physical resource configuration.
[0134]
[0145] In some examples, the first transport service is provided at a protocol layer associated with the first transport radio bearer, where the protocol layer is an Internet Protocol (IP) layer or a Packet Data Convergence Protocol (PDCP) layer.
[0135]
[0146] 9 shows a diagram of a system 900 including a device 905 supporting techniques for data transport in a service-based wireless system according to one or more aspects of the present disclosure. The device 905 may be an example of or include components of a device 605, a device 705, or a UE 115 as described herein. The device 905 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 905 may include components for two-way voice and data communication, including components for transmitting and receiving communications, such as a communications manager 920, an input / output (I / O) controller 910, a transceiver 915, an antenna 925, a memory 930, code 935, and a processor 940. These components may electronically communicate or otherwise be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 945).
[0136]
[0147] The I / O controller 910 may manage input and output signals for the device 905. The I / O controller 910 may also manage peripheral devices not integrated with the device 905. In some cases, the I / O controller 910 may represent a physical connection or port to an external peripheral device. In some cases, the I / O controller 910 may utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or another well-known operating system. Additionally or alternatively, the I / O controller 910 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller 910 may be implemented as part of a processor, such as the processor 940. In some cases, a user may interact with the device 905 through the I / O controller 910 or through hardware components controlled by the I / O controller 910.
[0137]
[0148] In some cases, the device 905 may include a single antenna 925. However, in some other cases, the device 905 may have two or more antennas 925 that may be capable of simultaneously transmitting or receiving multiple wireless transmissions. The transceiver 915 may communicate bidirectionally via one or more antennas 925, wired links, or wireless links described herein. For example, the transceiver 915 may represent a wireless transceiver, but may communicate bidirectionally with another wireless transceiver. The transceiver 915 may also include a modem for modulating packets, providing the modulated packets to one or more antennas 925 for transmission, and demodulating packets received from the one or more antennas 925. The transceiver 915, or the transceiver 915 and one or more antennas 925, may be an example of the transmitter 615, transmitter 715, receiver 610, receiver 710, or any combination or component thereof described herein.
[0138]
[0149] Memory 930 may include random access memory (RAM) and read-only memory (ROM). Memory 930 may store computer-readable computer-executable code 935, which includes instructions that, when executed by processor 940, cause device 905 to perform various functions described herein. Code 935 may be stored on a non-transitory computer-readable medium, such as system memory or another type of memory. In some cases, code 935 may not be directly executable by processor 940 but may cause a computer (e.g., when compiled or executed) to perform functions described herein. In some cases, memory 930 may include a basic I / O system (BIOS), which may control basic hardware or software operations, such as interaction with peripheral components or devices, among other things.
[0139]
[0150] The processor 940 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 940 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 940. The processor 940 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 930) to cause the device 905 to perform various functions (e.g., functions or tasks supporting techniques for data transport in a service-based wireless system). For example, the device 905 or a component of the device 905 may include the processor 940 and the memory 930 coupled to or associated with the processor 940, where the processor 940 and the memory 930 may be configured to perform various functions described herein.
[0140]
[0151] The communications manager 920 may support wireless communications in the UE according to examples disclosed herein. For example, the communications manager 920 may be configured as or otherwise support a means for communicating a first service message via the distributed unit to establish a first transport radio bearer with a first transport service provided by the service-based network, the first service message indicating one or more attributes associated with information to be transported via the first transport radio bearer. The communications manager 920 may be configured as or otherwise support a means for receiving, from the distributed unit in response to the first service message, a physical resource configuration for communications associated with the first transport service and a mapping of the first transport radio bearer to a first channel between the UE and the distributed unit. The communications manager 920 may be configured as or otherwise support a means for communicating, via the distributed unit based on the physical resource configuration, the information to be transported via the first transport service.
[0141]
[0152] By including or configuring a communications manager 920 according to examples as described herein, the device 905 may support techniques for reducing processing, reducing power consumption, and more efficient utilization of communications resources.
[0142]
[0153] In some examples, communications manager 920 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with transceiver 915, one or more antennas 925, or any combination thereof. Although communications manager 920 is shown as a separate component, in some examples, one or more functions described with reference to communications manager 920 may be supported or performed by processor 940, memory 930, code 935, or any combination thereof. For example, code 935 may include instructions executable by processor 940 to cause device 905 to perform various aspects of the techniques for data transport in services-based wireless systems described herein, or processor 940 and memory 930 may be otherwise configured to perform or support such operations.
[0143]
[0154] 10 shows a block diagram 1000 of a device 1005 supporting techniques for data transport in a service-based wireless system in accordance with one or more aspects of the present disclosure. The device 1005 may be an example of an aspect of a network entity 105 as described herein. The device 1005 may include a receiver 1010, a transmitter 1015, and a communications manager 1020. The device 1005 may also include a processor. Each of these components may communicate with one another (e.g., via one or more buses).
[0144]
[0155] The receiver 1010 may provide a means for obtaining (e.g., receiving, determining, identifying) information such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with protocol stacks). The information may be passed to other components of the device 1005. In some examples, the receiver 1010 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 1010 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical fiber) interfaces, wireless interfaces, or any combination thereof.
[0145]
[0156] The transmitter 1015 may provide a means for outputting (e.g., transmitting, providing, conveying, sending) information generated by other components of the device 1005. For example, the transmitter 1015 may output information such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with protocol stacks). In some examples, the transmitter 1015 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, the transmitter 1015 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 examples, the transmitter 1015 and receiver 1010 may be co-located within a transceiver that may include or be coupled to a modem.
[0146]
[0157] The communications manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be examples of means for implementing various aspects of the techniques for data transport in service-based wireless systems described herein. For example, the communications manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may support a method for implementing one or more of the functions described herein.
[0147]
[0158] In some examples, the communications manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry). The hardware may include a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof that may be configured as or otherwise support means for performing the functions described in this disclosure. In some examples, the processor and memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by the processor executing instructions stored in the memory).
[0148]
[0159] Additionally or alternatively, in some examples, the communications manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communications management software or firmware). When implemented in code executed by a processor, the functionality of the communications manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., that may be configured as or otherwise support a means for performing the functions described in this disclosure).
[0149]
[0160] In some examples, the communications manager 1020 may be configured to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting) using or otherwise cooperating with the receiver 1010, the transmitter 1015, or both. For example, the communications manager 1020 may receive information from the receiver 1010, transmit information to the transmitter 1015, or be integrated in combination with the receiver 1010, the transmitter 1015, or both to acquire information, output information, or perform various other operations described herein.
[0150]
[0161] The communications manager 1020 may support wireless communications in the distributed unit according to examples disclosed herein. For example, the communications manager 1020 may be configured as or otherwise support a means for communicating a first service message between a UE and a first transport service provided by a service-based network, where the first service message establishes the first transport service and indicates one or more attributes associated with information to be transported via the first transport service. The communications manager 1020 may be configured as or otherwise support a means for receiving, from the first transport service, a radio access network configuration indicating a first transport radio bearer and traffic flow information associated with the first transport radio bearer. The communications manager 1020 may be configured as or otherwise support a means for transmitting, in response to the radio access network configuration, to the UE a physical resource configuration for communications associated with the first transport service and a mapping of the first transport radio bearer to a first channel between the UE and the distributed unit. The communications manager 1020 may be configured as or otherwise support a means for communicating information to be transported via the first transport service between the UE and the first transport service based on the physical resource configuration.
[0151]
[0162] Additionally or alternatively, the communications manager 1020 may support wireless communications in core network services provided by the service-based network according to examples disclosed herein. For example, the communications manager 1020 may be configured as or otherwise support a means for communicating a first service message with a UE via a distributed unit to establish a first transport radio bearer with a first transport service provided by the service-based network, the first service message indicating one or more attributes associated with information to be transported via the first transport radio bearer. The communications manager 1020 may be configured as or otherwise support a means for outputting a second service message to the distributed unit indicating a radio access network configuration for the first transport radio bearer and traffic flow information associated with the first transport radio bearer. The communications manager 1020 may be configured as or otherwise support a means for communicating, via the distributed unit, information to be transported via the first transport service using the first transport radio bearer.
[0152]
[0163] By including or configuring a communications manager 1020 according to the examples described herein, the device 1005 (e.g., a processor controlling or otherwise coupled to the receiver 1010, the transmitter 1015, the communications manager 1020, or a combination thereof) may support techniques for reduced processing, reduced power consumption, and more efficient utilization of communications resources.
[0153]
[0164] 11 shows a block diagram 1100 of a device 1105 supporting techniques for data transport in a service-based wireless system in accordance with one or more aspects of the present disclosure. The device 1105 may be an example of an aspect of a device 1005 or a network entity 105 as described herein. The device 1105 may include a receiver 1110, a transmitter 1115, and a communications manager 1120. The device 1105 may also include a processor. Each of these components may communicate with one another (e.g., via one or more buses).
[0154]
[0165] The receiver 1110 may provide a means for obtaining (e.g., receiving, determining, identifying) information such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with protocol stacks). The information may be passed to other components of the device 1105. In some examples, the receiver 1110 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 1110 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical fiber) interfaces, wireless interfaces, or any combination thereof.
[0155]
[0166] The transmitter 1115 may provide a means for outputting (e.g., transmitting, providing, conveying, sending) information generated by other components of the device 1105. For example, the transmitter 1115 may output information such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, traffic channels, channels associated with protocol stacks). In some examples, the transmitter 1115 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, the transmitter 1115 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 examples, the transmitter 1115 and the receiver 1110 may be co-located within a transceiver that may include or be coupled to a modem.
[0156]
[0167] The device 1105, or its various components, may be an example of a means for implementing various aspects of the techniques for data transport in a service-based wireless system described herein. For example, the communications manager 1120 may include a transport services manager 1125, a RAN configuration manager 1130, a radio bearer mapping manager 1135, a transport radio bearer manager 1140, or any combination thereof. The communications manager 1120 may be an example of an aspect of the communications manager 1020 described herein. In some examples, the communications manager 1120, or its various components, may be configured to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting) using or otherwise cooperating with the receiver 1110, the transmitter 1115, or both. For example, the communications manager 1120 may receive information from the receiver 1110, transmit information to the transmitter 1115, or be integrated in combination with the receiver 1110, the transmitter 1115, or both to acquire information, output information, or perform various other operations described herein.
[0157]
[0168] The communications manager 1120 may support wireless communications in the distributed unit according to examples disclosed herein. The transport service manager 1125 may be configured as or otherwise support a means for communicating a first service message between the UE and a first transport service provided by the service-based network, where the first service message establishes the first transport service and indicates one or more attributes associated with information to be transported via the first transport service. The RAN configuration manager 1130 may be configured as or otherwise support a means for receiving a radio access network configuration from the first transport service indicating a first transport radio bearer and traffic flow information associated with the first transport radio bearer. The radio bearer mapping manager 1135 may be configured as or otherwise support a means for transmitting to the UE, in response to the radio access network configuration, a physical resource configuration for communications associated with the first transport service and a mapping of the first transport radio bearer to a first channel between the UE and the distributed unit. The transport radio bearer manager 1140 may be configured as or otherwise support a means for communicating information to be transported via the first transport service between the UE and the first transport service based on the physical resource configuration.
[0158]
[0169] Additionally or alternatively, the communications manager 1120 may support wireless communications in core network services provided by the service-based network according to examples disclosed herein. The transport service manager 1125 may be configured as or otherwise support a means for communicating a first service message with a UE via a distributed unit to establish a first transport radio bearer with a first transport service provided by the service-based network, the first service message indicating one or more attributes associated with information to be transported via the first transport radio bearer. The RAN configuration manager 1130 may be configured as or otherwise support a means for outputting a second service message to the distributed unit indicating a radio access network configuration for the first transport radio bearer and traffic flow information associated with the first transport radio bearer. The transport radio bearer manager 1140 may be configured as or otherwise support a means for communicating, via the distributed unit, information to be transported via the first transport service using the first transport radio bearer.
[0159]
[0170] 12 shows a block diagram 1200 of a communications manager 1220 supporting techniques for data transport in a service-based wireless system in accordance with one or more aspects of the present disclosure. Communications manager 1220 may be an example of aspects of communications manager 1020, communications manager 1120, or both, as described herein. Communications manager 1220, or various components thereof, may be an example of a means for implementing various aspects of the techniques for data transport in a service-based wireless system described herein. For example, communications manager 1220 may include a transport services manager 1225, a RAN configuration manager 1230, a radio bearer mapping manager 1235, a transport radio bearer manager 1240, a packet attribute manager 1245, a data throughput manager 1250, or any combination thereof. Each of these components may communicate directly or indirectly with one another (e.g., via one or more buses), which may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualization component associated with network entity 105, between devices, components, or virtualization components associated with network entity 105), or any combination thereof.
[0160]
[0171] The communications manager 1220 may support wireless communications in the distributed unit according to examples disclosed herein. The transport service manager 1225 may be configured as or otherwise support a means for communicating a first service message between the UE and a first transport service provided by the service-based network, where the first service message establishes the first transport service and indicates one or more attributes associated with information to be transported via the first transport service. The RAN configuration manager 1230 may be configured as or otherwise support a means for receiving a radio access network configuration from the first transport service indicating a first transport radio bearer and traffic flow information associated with the first transport radio bearer. The radio bearer mapping manager 1235 may be configured as or otherwise support a means for transmitting to the UE, in response to the radio access network configuration, a physical resource configuration for communications associated with the first transport service and a mapping of the first transport radio bearer to a first channel between the UE and the distributed unit. The transport radio bearer manager 1240 may be configured as or otherwise support a means for communicating information to be transported via the first transport service between the UE and the first transport service based on the physical resource configuration.
[0161]
[0172] In some examples, the radio bearer mapping manager 1235 may be configured as or otherwise support a means for mapping the first transport radio bearer and at least one other transport radio bearer to a first logical channel, each transport radio bearer having an associated transport service. In some examples, the first service message includes one or more quality of service targets associated with information to be transported via the first transport service. In some examples, the information to be transported via the first transport service is transmitted using a set of multiple packets, each packet of the set of multiple packets including an indication of the first transport radio bearer. In some examples, the first transport radio bearer provides communication for both signaling information and data associated with the first transport service.
[0162]
[0173] In some examples, the RAN configuration manager 1230 may be configured or otherwise support a means for receiving, from the first transport service, an updated radio access network configuration indicating updated traffic flow information associated with the first transport radio bearer, and in some examples, the radio bearer mapping manager 1235 may be configured or otherwise support a means for transmitting, to the UE, an updated physical resource configuration for communications associated with the first transport service in response to the updated radio access network configuration.
[0163]
[0174] In some examples, the data throughput manager 1250 may be configured as or otherwise support a means for aggregating traffic flow information across the first transport service and one or more other transport services, and the RAN configuration manager 1230 may be configured as or otherwise support a means for configuring one or more carriers and one or more resource grants of a physical resource configuration based on the aggregated traffic flow information.
[0164]
[0175] In some examples, the transport service manager 1225 may be configured as or otherwise support a means for communicating with a first transport service based on a communication protocol that provides an indication of a first transport radio bearer for each of a set of multiple packets associated with the first transport radio bearer and that provides an indication of traffic flow information associated with the first transport radio bearer.
[0165]
[0176] Additionally or alternatively, the communications manager 1220 may support wireless communications in core network services provided by the service-based network according to examples disclosed herein. In some examples, the transport service manager 1225 may be configured as or otherwise support a means for communicating a first service message with a UE via a distributed unit to establish a first transport radio bearer with a first transport service provided by the service-based network, the first service message indicating one or more attributes associated with information to be transported via the first transport radio bearer. In some examples, the RAN configuration manager 1230 may be configured as or otherwise support a means for outputting a second service message to the distributed unit indicating a radio access network configuration for the first transport radio bearer and traffic flow information associated with the first transport radio bearer. In some examples, the transport radio bearer manager 1240 may be configured as or otherwise support a means for communicating, via the distributed unit, information to be transported via the first transport service using the first transport radio bearer.
[0166]
[0177] In some examples, the first service message includes one or more quality of service targets associated with information to be transported via the first transport service. In some examples, the information to be transported via the first transport service is transmitted using a set of multiple packets, each packet of the set of multiple packets including an indication of the first transport radio bearer.
[0167]
[0178] In some examples, the RAN configuration manager 1230 may be configured or otherwise support a means for providing an updated radio access network configuration to the distributed unit indicating updated traffic flow information associated with the first transport radio bearer, and in some examples, the radio bearer mapping manager 1235 may be configured or otherwise support a means for communicating with the UE via the distributed unit using the first transport radio bearer based on the updated radio access network configuration.
[0168]
[0179] In some examples, the transport services manager 1225 may be configured as or otherwise support a means for communicating with a distributed unit based on a communication protocol that provides an indication of a first transport radio bearer for each of a set of multiple packets associated with the first transport radio bearer and that provides an indication of traffic flow information associated with the first transport radio bearer.
[0169]
[0180] 13 shows a diagram of a system 1300 including a device 1305 supporting techniques for data transport in a service-based wireless system according to one or more aspects of the present disclosure. The device 1305 may be an example of or include components of a device 1005, a device 1105, or a network entity 105 as described herein. The device 1305 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which may include communication via one or more wired interfaces, one or more wireless interfaces, or a combination thereof. The device 1305 may include components supporting outputting and obtaining communications, such as a communications manager 1320, a transceiver 1310, an antenna 1315, a memory 1325, code 1330, and a processor 1335. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1340).
[0170]
[0181] The transceiver 1310 may support bidirectional communication via a wired link, a wireless link, or both, as described herein. In some examples, the transceiver 1310 may include a wired transceiver but may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1310 may include a wireless transceiver but may communicate bidirectionally with another wireless transceiver. In some examples, the device 1305 may include one or more antennas 1315, which may be capable of transmitting or receiving (e.g., simultaneously) wireless transmissions. The transceiver 1310 may also include a modem for modulating signals, providing the modulated signals for transmission (e.g., by one or more antennas 1315 or by a wired transmitter), receiving the modulated signals (e.g., from one or more antennas 1315 or from a wired receiver), and demodulating the signals. In some implementations, the transceiver 1310 may include one or more interfaces, such as one or more interfaces coupled with one or more antennas 1315 configured to support various receive or acquisition operations, or one or more interfaces coupled with one or more antennas 1315 configured to support various transmit or output operations, or a combination thereof. In some implementations, the transceiver 1310 may include or be configured to couple to one or more processors or memory components operable 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 any combination thereof. In some implementations, the transceiver 1310, or the transceiver 1310 and one or more antennas 1315, or the transceiver 1310 and one or more antennas 1315 and one or more processors or memory components (e.g., the processor 1335, or the memory 1325, or both), may be included on a chip or chip assembly installed in the device 1305.The transceiver 1310, or the transceiver 1310 and one or more antennas 1315, or the wired interface, may be an example of the transmitter 1015, the transmitter 1115, the receiver 1010, the receiver 1110, or any combination or component thereof, as described herein, where applicable. In some examples, the transceiver may be operable to support communication over one or more communication links (e.g., the communication link 125, the backhaul communication link 120, the midhaul communication link, the fronthaul communication link 168).
[0171]
[0182] The memory 1325 may include RAM and ROM. The memory 1325 may store computer-readable computer-executable code 1330 including instructions that, when executed by the processor 1335, cause the device 1305 to perform various functions described herein. The code 1330 may be stored on a non-transitory computer-readable medium, such as system memory or another type of memory. In some cases, the code 1330 may not be directly executable by the processor 1335 but may cause the computer to perform (e.g., when compiled or executed) the functions described herein. In some cases, the memory 1325 may include a BIOS, which may control basic hardware or software operations, such as interaction with peripheral components or devices, among other things.
[0172]
[0183] The processor 1335 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof). In some cases, the processor 1335 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 1335. The processor 1335 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1325) to cause the device 1305 to perform various functions (e.g., functions or tasks supporting techniques for data transport in a service-based wireless system). For example, the device 1305 or a component of the device 1305 may include the processor 1335 and the memory 1325 coupled to the processor 1335, where the processor 1335 and the memory 1325 are configured to perform the various functions described herein. Processor 1335 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that may host functionality (e.g., by executing code 1330) to perform the functions of device 1305. Processor 1335 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored on device 1305 (e.g., in memory 1325). In some implementations, processor 1335 may be a component of a processing system. A processing system may generally refer to a system or set of machines or components that receives input, processes the input, and generates a set of output (e.g., that may be passed to other systems or components of device 1305).For example, the processing system of device 1305 may refer to a system that includes various other components or subcomponents of device 1305, such as processor 1335, or transceiver 1310, or communications manager 1320, or other components or combinations of components of device 1305. The processing system of device 1305 may interface with other components of device 1305, process information (e.g., input or signals) received from the other components, or output information to the other components. For example, a chip or modem of device 1305 may include a processing system and an interface for outputting information, an interface for acquiring information, or both. The interfaces may be implemented as, or may otherwise include, a first interface configured to output information and a second interface configured to acquire information. In some implementations, the first interface may refer to an interface between the processing system and a transmitter of the chip or modem, by which device 1305 may transmit information output from the chip or modem. In some implementations, the second interface may refer to an interface between a processing system and a receiver of a chip or modem, whereby the device 1305 may receive information or signal input, but that information may be passed to the processing system. Those skilled in the art will readily recognize that the first interface may also obtain information or signal input, but the second interface may also output information or signal output.
[0173]
[0184] In some examples, bus 1340 may support communication of (e.g., within) protocol layers of a protocol stack. In some examples, bus 1340 may support communication associated with logical channels of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communication performed within a component of device 1305 or between different components of device 1305, which may be collocated or located in different locations (e.g., device 1305 may refer to a system in which one or more of communications manager 1320, transceiver 1310, memory 1325, code 1330, and processor 1335 may be located in one of or split among different components).
[0174]
[0185] In some examples, the communications manager 1320 may manage aspects of communications with the core network 130 (e.g., over one or more wired or wireless backhaul links). For example, the communications manager 1320 may manage the forwarding of data communications for client devices, such as one or more UEs 115. In some examples, the communications manager 1320 may manage communications with other network entities 105, but may include a controller or scheduler for cooperating with the other network entities 105 to control communications with the UE 115. In some examples, the communications manager 1320 may support an X2 interface within the LTE / LTE-A wireless communications network technology to provide communications between network entities 105.
[0175]
[0186] The communications manager 1320 may support wireless communications in the distributed unit according to examples disclosed herein. For example, the communications manager 1320 may be configured as or otherwise support a means for communicating a first service message between a UE and a first transport service provided by a service-based network, where the first service message establishes the first transport service and indicates one or more attributes associated with information to be transported via the first transport service. The communications manager 1320 may be configured as or otherwise support a means for receiving, from the first transport service, a radio access network configuration indicating a first transport radio bearer and traffic flow information associated with the first transport radio bearer. The communications manager 1320 may be configured as or otherwise support a means for transmitting, to the UE, a physical resource configuration for communications associated with the first transport service and a mapping of the first transport radio bearer to a first channel between the UE and the distributed unit, in response to the radio access network configuration. The communications manager 1320 may be configured as or otherwise support a means for communicating information to be transported via the first transport service between the UE and the first transport service based on the physical resource configuration.
[0176]
[0187] Additionally or alternatively, the communications manager 1320 may support wireless communications in core network services provided by the service-based network according to examples disclosed herein. For example, the communications manager 1320 may be configured as or otherwise support a means for communicating a first service message with a UE via a distributed unit to establish a first transport radio bearer with a first transport service provided by the service-based network, the first service message indicating one or more attributes associated with information to be transported via the first transport radio bearer. The communications manager 1320 may be configured as or otherwise support a means for outputting a second service message to the distributed unit indicating a radio access network configuration for the first transport radio bearer and traffic flow information associated with the first transport radio bearer. The communications manager 1320 may be configured as or otherwise support a means for communicating, via the distributed unit, information to be transported via the first transport service using the first transport radio bearer.
[0177]
[0188] By including or configuring a communications manager 1320 according to examples as described herein, the device 1305 may support techniques for reducing processing, reducing power consumption, and more efficient utilization of communications resources.
[0178]
[0189] In some examples, communications manager 1320 may be configured to perform various operations (e.g., receive, acquire, monitor, output, transmit) using or otherwise in cooperation with transceiver 1310, one or more antennas 1315 (e.g., if applicable), or any combination thereof. Although communications manager 1320 is shown as a separate component, in some examples, one or more functions described with reference to communications manager 1320 may be supported or implemented by processor 1335, memory 1325, code 1330, transceiver 1310, or any combination thereof. For example, code 1330 may include instructions executable by processor 1335 to cause device 1305 to perform various aspects of the techniques for data transport in services-based wireless systems described herein, or processor 1335 and memory 1325 may be otherwise configured to perform or support such operations.
[0179]
[0190] 14 shows a flowchart illustrating a method 1400 supporting techniques for data transport in a service-based wireless system according to one or more aspects of the present disclosure. The operations of method 1400 may be performed by a UE or components thereof as described herein. For example, the operations of method 1400 may be performed by the UE 115 described with reference to FIGS. 1-9. In some examples, the UE may execute a set of instructions to control functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may implement aspects of the described functions using dedicated hardware.
[0180]
[0191] At 1405, the method may include communicating a first service message via the distributed unit to establish a first transport radio bearer with a first transport service provided by the service-based network, the first service message indicating one or more attributes associated with information to be transported via the first transport radio bearer. The operations of 1405 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 1405 may be performed by a transport service manager 825, as described with reference to FIG. 8.
[0181]
[0192] At 1410, the method may include receiving, from the distributed unit in response to the first service message, a physical resource configuration for communication associated with the first transport service and a mapping of the first transport radio bearer to a first channel (e.g., a first logical channel) between the UE and the distributed unit. The operations of 1410 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 1410 may be performed by a transport radio bearer manager 830, as described with reference to FIG. 8.
[0182]
[0193] At 1415, the method may include communicating, via the distributed unit based on the physical resource configuration, information to be transported via the first transport service. The operation of 1415 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operation of 1415 may be performed by a transport radio bearer manager 830, as described with reference to FIG. 8.
[0183]
[0194] 15 shows a flowchart illustrating a method 1500 supporting techniques for data transport in a service-based wireless system according to one or more aspects of the present disclosure. The operations of method 1500 may be performed by a UE or components thereof as described herein. For example, the operations of method 1500 may be performed by the UE 115 described with reference to FIGS. 1-9. In some examples, the UE may execute a set of instructions to control functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may implement aspects of the described functions using dedicated hardware.
[0184]
[0195] At 1505, the method may include communicating a first service message via the distributed unit to establish a first transport radio bearer with a first transport service provided by the service-based network, the first service message indicating one or more attributes associated with information to be transported via the first transport radio bearer. The operations of 1505 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 1505 may be performed by a transport service manager 825, as described with reference to FIG. 8.
[0185]
[0196] At 1510, the method may include receiving, from the distributed unit in response to the first service message, a physical resource configuration for communication associated with the first transport service and a mapping of the first transport radio bearer to the first channel between the UE and the distributed unit. The operations of 1510 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 1510 may be performed by a transport radio bearer manager 830, as described with reference to FIG. 8.
[0186]
[0197] At 1515, the method may include mapping one or more transport radio bearers to the first logical channel, each of the transport radio bearers having an associated transport service. The operations of 1515 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 1515 may be performed by the radio bearer mapping manager 835 described with reference to FIG. 8.
[0187]
[0198] At 1520, the method may include communicating, via the distributed unit based on the physical resource configuration, information to be transported via the first transport service. The operations of 1520 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 1520 may be performed by a transport radio bearer manager 830, as described with reference to FIG. 8.
[0188]
[0199] 16 shows a flowchart illustrating a method 1600 supporting techniques for data transport in a service-based wireless system according to one or more aspects of the present disclosure. The operations of method 1600 may be performed by a UE or components thereof as described herein. For example, the operations of method 1600 may be performed by the UE 115 described with reference to FIGS. 1-9. In some examples, the UE may execute a set of instructions to control functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may implement aspects of the described functions using dedicated hardware.
[0189]
[0200] At 1605, the method may include communicating a first service message via the distributed unit to establish a first transport radio bearer with a first transport service provided by the service-based network, the first service message indicating one or more attributes associated with information to be transported via the first transport radio bearer. The operations of 1605 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 1605 may be performed by a transport service manager 825, as described with reference to FIG. 8.
[0190]
[0201] At 1610, the method may include communicating one or more attributes associated with the information to be transported via the first transport service as one or more quality of service parameters including a latency target, a throughput target, a security level, or any combination thereof. The operations of 1610 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 1610 may be performed by a packet attribute manager 840 described with reference to FIG. 8.
[0191]
[0202] At 1615, the method may include communicating one or more buffer status reports to the first transport service via the distributed unit to maintain an active state in the first transport service. The operations of 1615 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 1615 may be performed by the BSR manager 845 described with reference to FIG. 8.
[0192]
[0203] At 1620, the method may include receiving, from the distributed unit in response to the first service message, a physical resource configuration for communication associated with the first transport service and a mapping of the first transport radio bearer to the first channel between the UE and the distributed unit. The operations of 1620 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 1620 may be performed by a transport radio bearer manager 830, as described with reference to FIG. 8.
[0193]
[0204] At 1625, the method may include communicating, via the distributed unit based on the physical resource configuration, information to be transported via the first transport service. The operations of 1625 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 1625 may be performed by a transport radio bearer manager 830, as described with reference to FIG. 8.
[0194]
[0205] 17 shows a flowchart illustrating a method 1700 supporting techniques for data transport in a service-based wireless system according to one or more aspects of the present disclosure. The operations of method 1700 may be performed by a UE or components thereof as described herein. For example, the operations of method 1700 may be performed by the UE 115 described with reference to FIGS. 1-9. In some examples, the UE may execute a set of instructions to control functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may implement aspects of the described functions using dedicated hardware.
[0195]
[0206] At 1705, the method may include communicating a first service message via the distributed unit to establish a first transport radio bearer with a first transport service provided by the service-based network, the first service message indicating one or more attributes associated with information to be transported via the first transport radio bearer. The operations of 1705 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 1705 may be performed by a transport service manager 825, as described with reference to FIG. 8.
[0196]
[0207] At 1710, the method may include receiving, from the distributed unit in response to the first service message, a physical resource configuration for communication associated with the first transport service and a mapping of the first transport radio bearer to the first channel between the UE and the distributed unit. The operations of 1710 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 1710 may be performed by a transport radio bearer manager 830, as described with reference to FIG. 8.
[0197]
[0208] At 1715, the method may include communicating, via the distributed unit based on the physical resource configuration, information to be transported via the first transport service. The operation of 1715 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operation of 1715 may be performed by a transport radio bearer manager 830, as described with reference to FIG. 8.
[0198]
[0209] At 1720, the method may include receiving an indication to suppress information to be transported via the first transport service. The operations of 1720 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 1720 may be performed by data throughput manager 850 described with reference to FIG. 8.
[0199]
[0210] At 1725, the method may include throttling information communicated via the first transport service regardless of an amount of information communicated via one or more other transport services different from the first transport service. The operations of 1725 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 1725 may be performed by data throughput manager 850 described with reference to FIG. 8.
[0200]
[0211] 18 shows a flowchart illustrating a method 1800 supporting techniques for data transport in a service-based wireless system according to one or more aspects of the present disclosure. The operations of method 1800 may be performed by a UE or components thereof as described herein. For example, the operations of method 1800 may be performed by the UE 115 described with reference to FIGS. 1-9. In some examples, the UE may execute a set of instructions to control functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may implement aspects of the described functions using dedicated hardware.
[0201]
[0212] At 1805, the method may include communicating a first service message via the distributed unit to establish a first transport radio bearer with a first transport service provided by the service-based network, the first service message indicating one or more attributes associated with information to be transported via the first transport radio bearer. The operations of 1805 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 1805 may be performed by a transport service manager 825, as described with reference to FIG. 8.
[0202]
[0213] At 1810, the method may include receiving, from the distributed unit in response to the first service message, a physical resource configuration for communication associated with the first transport service and a mapping of the first transport radio bearer to the first channel between the UE and the distributed unit. The operations of 1810 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 1810 may be performed by a transport radio bearer manager 830, as described with reference to FIG. 8.
[0203]
[0214] At 1815, the method may include communicating, via the distributed unit based on the physical resource configuration, information to be transported via the first transport service. The operation of 1815 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operation of 1815 may be performed by a transport radio bearer manager 830, as described with reference to FIG. 8.
[0204]
[0215] At 1820, the method may include communicating, via the distributed unit, a second service message indicating deactivating a first transport radio bearer associated with the first transport service. The operation of 1820 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operation of 1820 may be performed by a transport service manager 825, as described with reference to FIG. 8.
[0205]
[0216] At 1825, the method may include obtaining further information to be transported over the first transport radio bearer following deactivation of the first transport service. The operations of 1825 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 1825 may be performed by a transport service manager 825, as described with reference to FIG. 8.
[0206]
[0217] At 1830, the method may include communicating, via the distributed unit, a third service message for activating the first transport radio bearer. The operation of 1830 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operation of 1830 may be performed by the transport service manager 825, as described with reference to FIG. 8.
[0207]
[0218] 19 shows a flowchart illustrating a method 1900 supporting techniques for data transport in a service-based wireless system according to one or more aspects of the present disclosure. The operations of method 1900 may be performed by a UE or components thereof as described herein. For example, the operations of method 1900 may be performed by the UE 115 described with reference to FIGS. 1-9. In some examples, the UE may execute a set of instructions to control functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may implement aspects of the described functions using dedicated hardware.
[0208]
[0219] At 1905, the method may include communicating a first service message via the distributed unit to establish a first transport radio bearer with a first transport service provided by the service-based network, the first service message indicating one or more attributes associated with information to be transported via the first transport radio bearer. The operations of 1905 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 1905 may be performed by a transport service manager 825, as described with reference to FIG. 8.
[0209]
[0220] At 1910, the method may include receiving, from the distributed unit in response to the first service message, a physical resource configuration for communication associated with the first transport service and a mapping of the first transport radio bearer to the first channel between the UE and the distributed unit. The operations of 1910 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 1910 may be performed by a transport radio bearer manager 830, as described with reference to FIG. 8.
[0210]
[0221] At 1915, the method may include communicating, via the distributed unit based on the physical resource configuration, information to be transported via the first transport service. The operation of 1915 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operation of 1915 may be performed by a transport radio bearer manager 830, as described with reference to FIG. 8.
[0211]
[0222] At 1920, the method may include receiving an updated physical resource configuration from the distributed unit in response to the updated configuration associated with the first transport service. The operation of 1920 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operation of 1920 may be performed by a transport radio bearer manager 830, as described with reference to FIG. 8.
[0212]
[0223] At 1925, the method may include communicating, via the distributed unit, information to be transported via the first transport service based on the updated physical resource configuration. The operation of 1925 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operation of 1925 may be performed by a transport radio bearer manager 830, as described with reference to FIG. 8.
[0213]
[0224] FIG. 20 shows a flowchart illustrating a method 2000 supporting techniques for data transport in a service-based wireless system according to one or more aspects of the present disclosure. The operations of method 2000 may be implemented by a network entity or components thereof as described herein. For example, the operations of method 2000 may be performed by a network entity as described with reference to FIGS. 1-5 and 10-13. In some examples, the network entity may execute a set of instructions to control functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may perform aspects of the described functions using dedicated hardware.
[0214]
[0225] At 2005, the method may include communicating a first service message between the UE and a first transport service provided by the service-based network, where the first service message establishes the first transport service and indicates one or more attributes associated with information to be transported via the first transport service. The operations of 2005 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 2005 may be performed by a transport service manager 1225, as described with reference to FIG. 12.
[0215]
[0226] At 2010, the method may include receiving a radio access network configuration from a first transport service indicating a first transport radio bearer and traffic flow information associated with the first transport radio bearer. The operations of 2010 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 2010 may be performed by a RAN configuration manager 1230 such as described with reference to FIG. 12.
[0216]
[0227] At 2015, the method may include transmitting, in response to the radio access network configuration, to the UE a physical resource configuration for communication associated with the first transport service and a mapping of the first transport radio bearer to the first channel between the UE and the distributed unit. The operations of 2015 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 2015 may be performed by the radio bearer mapping manager 1235 described with reference to FIG. 12.
[0217]
[0228] At 2020, the method may include communicating information to be transported via the first transport service between the UE and the first transport service based on the physical resource configuration. The operations of 2020 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 2020 may be performed by a transport radio bearer manager 1240, as described with reference to FIG. 12.
[0218]
[0229] FIG. 21 shows a flowchart illustrating a method 2100 supporting techniques for data transport in a service-based wireless system according to one or more aspects of the present disclosure. The operations of method 2100 may be implemented by a network entity or components thereof as described herein. For example, the operations of method 2100 may be performed by a network entity as described with reference to FIGS. 1-5 and 10-13. In some examples, the network entity may execute a set of instructions to control functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may perform aspects of the described functions using dedicated hardware.
[0219]
[0230] At 2105, the method may include communicating a first service message between the UE and a first transport service provided by the service-based network, where the first service message establishes the first transport service and indicates one or more attributes associated with information to be transported via the first transport service. The operations of 2105 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 2105 may be performed by a transport service manager 1225, as described with reference to FIG. 12.
[0220]
[0231] At 2110, the method may include receiving a radio access network configuration from the first transport service indicating a first transport radio bearer and traffic flow information associated with the first transport radio bearer. The operations of 2110 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 2110 may be performed by a RAN configuration manager 1230 such as described with reference to FIG. 12.
[0221]
[0232] At 2115, the method may include mapping the first transport radio bearer and at least one other transport radio bearer to the first channel, each transport radio bearer having an associated transport service. The operations of 2115 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 2115 may be performed by the radio bearer mapping manager 1235 described with reference to FIG. 12.
[0222]
[0233] At 2120, the method may include transmitting, in response to the radio access network configuration, to the UE a physical resource configuration for communication associated with the first transport service and a mapping of the first transport radio bearer to the first channel between the UE and the distributed unit. The operations of 2120 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 2120 may be performed by the radio bearer mapping manager 1235 described with reference to FIG. 12.
[0223]
[0234] At 2125, the method may include communicating information to be transported via the first transport service between the UE and the first transport service based on the physical resource configuration. The operations of 2125 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 2125 may be performed by a transport radio bearer manager 1240, as described with reference to FIG. 12.
[0224]
[0235] FIG. 22 shows a flowchart illustrating a method 2200 supporting techniques for data transport in a service-based wireless system according to one or more aspects of the present disclosure. The operations of method 2200 may be implemented by a network entity or components thereof as described herein. For example, the operations of method 2200 may be performed by a network entity as described with reference to FIGS. 1-5 and 10-13. In some examples, the network entity may execute a set of instructions to control functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may perform aspects of the described functions using dedicated hardware.
[0225]
[0236] At 2205, the method may include communicating a first service message between the UE and a first transport service provided by the service-based network, where the first service message establishes the first transport service and indicates one or more attributes associated with information to be transported via the first transport service. The operations of 2205 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 2205 may be performed by a transport service manager 1225, as described with reference to FIG. 12.
[0226]
[0237] At 2210, the method may include receiving a radio access network configuration from the first transport service indicating a first transport radio bearer and traffic flow information associated with the first transport radio bearer. The operations of 2210 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 2210 may be performed by a RAN configuration manager 1230 as described with reference to FIG. 12.
[0227]
[0238] At 2215, the method may include transmitting, in response to the radio access network configuration, to the UE a physical resource configuration for communication associated with the first transport service and a mapping of the first transport radio bearer to the first channel between the UE and the distributed unit. The operations of 2215 may be implemented in accordance with examples disclosed herein. In some examples, aspects of the operations of 2215 may be performed by the radio bearer mapping manager 1235 described with reference to FIG. 12.
[0228]
[0239] At 2220, the method may include communicating information to be transported via the first transport service between the UE and the first transport service based on the physical resource configuration. The operations of 2220 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 2220 may be performed by a transport radio bearer manager 1240, as described with reference to FIG. 12.
[0229]
[0240] At 2225, the method may include receiving, from the first transport service, an updated radio access network configuration indicating updated traffic flow information associated with the first transport radio bearer. The operations of 2225 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 2225 may be performed by a RAN configuration manager 1230 as described with reference to FIG. 12.
[0230]
[0241] At 2230, the method may include transmitting, to the UE, an updated physical resource configuration for communications associated with the first transport service in response to the updated radio access network configuration. The operations of 2230 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 2230 may be performed by the radio bearer mapping manager 1235 described with reference to FIG. 12.
[0231]
[0242] FIG. 23 shows a flowchart illustrating a method 2300 supporting techniques for data transport in a service-based wireless system according to one or more aspects of the present disclosure. The operations of method 2300 may be implemented by a network entity or components thereof as described herein. For example, the operations of method 2300 may be performed by a network entity as described with reference to FIGS. 1-5 and 10-13. In some examples, the network entity may execute a set of instructions to control functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may perform aspects of the described functions using dedicated hardware.
[0232]
[0243] At 2305, the method may include communicating a first service message between the UE and a first transport service provided by the service-based network, where the first service message establishes the first transport service and indicates one or more attributes associated with information to be transported via the first transport service. The operations of 2305 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 2305 may be performed by a transport service manager 1225, as described with reference to FIG. 12.
[0233]
[0244] At 2310, the method may include receiving a radio access network configuration from the first transport service indicating a first transport radio bearer and traffic flow information associated with the first transport radio bearer. The operations of 2310 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 2310 may be performed by a RAN configuration manager 1230 as described with reference to FIG. 12.
[0234]
[0245] At 2315, the method may include transmitting, in response to the radio access network configuration, to the UE a physical resource configuration for communication associated with the first transport service and a mapping of the first transport radio bearer to the first channel between the UE and the distributed unit. The operations of 2315 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 2315 may be performed by the radio bearer mapping manager 1235 described with reference to FIG. 12.
[0235]
[0246] At 2320, the method may include communicating information to be transported via the first transport service between the UE and the first transport service based on the physical resource configuration. The operations of 2320 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 2320 may be performed by a transport radio bearer manager 1240, as described with reference to FIG. 12.
[0236]
[0247] At 2325, the method may include aggregating traffic flow information across the first transport service and one or more other transport services. The operations of 2325 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 2325 may be performed by data throughput manager 1250 described with reference to FIG. 12.
[0237]
[0248] At 2330, the method may include configuring one or more carriers and one or more resource grants of a physical resource configuration based on the aggregated traffic flow information. The operations of 2330 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 2330 may be performed by a RAN configuration manager 1230 as described with reference to FIG. 12.
[0238]
[0249] FIG. 24 shows a flowchart illustrating a method 2400 supporting techniques for data transport in a service-based wireless system according to one or more aspects of the present disclosure. The operations of method 2400 may be implemented by a network entity or components thereof as described herein. For example, the operations of method 2400 may be performed by a network entity as described with reference to FIGS. 1-5 and 10-13. In some examples, the network entity may execute a set of instructions to control functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may perform aspects of the described functions using dedicated hardware.
[0239]
[0250] At 2405, the method may include communicating a first service message with the UE via the distributed unit to establish a first transport radio bearer with a first transport service provided by the service-based network, the first service message indicating one or more attributes associated with information to be transported via the first transport radio bearer. The operations of 2405 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 2405 may be performed by a transport service manager 1225, as described with reference to FIG. 12.
[0240]
[0251] At 2410, the method may include outputting a second service message to the distributed unit indicating a radio access network configuration for the first transport radio bearer and traffic flow information associated with the first transport radio bearer. The operations of 2410 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 2410 may be performed by a RAN configuration manager 1230 as described with reference to FIG. 12.
[0241]
[0252] At 2415, the method may include communicating, via the distributed unit, information to be transported via the first transport service using the first transport radio bearer. The operations of 2415 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 2415 may be performed by a transport radio bearer manager 1240, as described with reference to FIG. 12.
[0242]
[0253] FIG. 25 shows a flowchart illustrating a method 2500 supporting techniques for data transport in a service-based wireless system according to one or more aspects of the present disclosure. The operations of method 2500 may be implemented by a network entity or components thereof as described herein. For example, the operations of method 2500 may be performed by a network entity as described with reference to FIGS. 1-5 and 10-13. In some examples, the network entity may execute a set of instructions to control functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may perform aspects of the described functions using dedicated hardware.
[0243]
[0254] At 2505, the method may include communicating a first service message with the UE via the distributed unit to establish a first transport radio bearer with a first transport service provided by the service-based network, the first service message indicating one or more attributes associated with information to be transported via the first transport radio bearer. The operations of 2505 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 2505 may be performed by a transport service manager 1225, as described with reference to FIG. 12.
[0244]
[0255] At 2510, the method may include outputting a second service message to the distributed unit indicating a radio access network configuration for the first transport radio bearer and traffic flow information associated with the first transport radio bearer. The operations of 2510 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 2510 may be performed by a RAN configuration manager 1230 as described with reference to FIG. 12.
[0245]
[0256] At 2515, the method may include communicating, via the distributed unit, information to be transported via the first transport service using the first transport radio bearer. The operations of 2515 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 2515 may be performed by the transport radio bearer manager 1240, as described with reference to FIG. 12.
[0246]
[0257] At 2520, the method may include providing an updated radio access network configuration to the distributed unit indicating updated traffic flow information associated with the first transport radio bearer. The operations of 2520 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 2520 may be performed by a RAN configuration manager 1230 as described with reference to FIG. 12.
[0247]
[0258] At 2525, the method may include communicating with the UE via the distributed unit using the first transport radio bearer based on the updated radio access network configuration. The operations of 2525 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 2525 may be performed by the radio bearer mapping manager 1235 described with reference to FIG. 12.
[0248]
[0259] The following provides a summary of aspects of the present disclosure.
[0249]
[0260] Aspect 1: A method for wireless communication in a UE, comprising: communicating a first service message via a distributed unit to establish a first transport radio bearer with a first transport service provided by a service-based network, the first service message indicating one or more attributes associated with information to be transported via the first transport radio bearer; receiving from the distributed unit in response to the first service message a physical resource configuration for communication associated with the first transport service and a mapping of the first transport radio bearer to a first channel between the UE and the distributed unit; and communicating, via the distributed unit, the information to be transported via the first transport service based at least in part on the physical resource configuration.
[0250]
[0261] Aspect 2: The method of aspect 1, further comprising mapping one or more transport radio bearers to the first channel, each of the transport radio bearers having an associated transport service.
[0251]
[0262] Aspect 3: A method as described in any of aspects 1 or 2, wherein information to be transported via the first transport service is split across two or more channels between the UE and the distributed unit, including a separate channel for signaling information.
[0252]
[0263] Aspect 4: The method of aspect 3, wherein the division across two or more channels is based at least in part on one or more of a traffic priority of information to be transported via the first transport service, a delay tolerance of traffic of information to be transported via the first transport service, a traffic tolerance error rate of information to be transported via the first transport service, or any combination thereof.
[0253]
[0264] Aspect 5: A method according to any one of aspects 1 to 4, wherein two or more transport radio bearers from a first transport service are mapped to the first channel, one transport radio bearer is mapped to the first channel, or multiple transport radio bearers are mapped to each of two or more channels.
[0254]
[0265] Aspect 6: A method according to any of aspects 1 to 5, wherein the first service message includes one or more quality of service targets associated with information to be transported via the first transport service, and different quality of service targets are associated with different channels between the UE and the distributed unit.
[0255]
[0266] Aspect 7: A method according to any one of aspects 1 to 6, wherein information to be transported via the first transport service is transmitted using a plurality of packets, each packet of the plurality of packets including an indication of the first transport radio bearer.
[0256]
[0267] Aspect 8: The method of any of aspects 1 to 7, wherein the first transport radio bearer provides communication for both signaling information and data associated with the first transport service.
[0257]
[0268] Aspect 9: A method described in any of aspects 1 to 8, wherein communicating the first service message includes communicating one or more attributes associated with the information to be transported via the first transport service as one or more quality of service parameters including a latency target, a throughput target, a security level, or any combination thereof.
[0258]
[0269] Aspect 10: The method of any of aspects 1 to 9, further comprising communicating, via the distributed unit, one or more buffer status reports to the first transport service to maintain an active state in the first transport service.
[0259]
[0270] Aspect 11: A method described in any of aspects 1 to 10, further comprising receiving an indication to suppress information to be transported via a first transport service, and suppressing the information communicated via the first transport service regardless of the amount of information communicated via one or more other transport services different from the first transport service.
[0260]
[0271] Aspect 12: The method of any of aspects 1 to 11, further comprising: communicating, via the distributed unit, a second service message indicating deactivation of a first transport radio bearer associated with the first transport service.
[0261]
[0272] Aspect 13: The method of aspect 12, further comprising, following deactivation of the first transport service, obtaining further information to be transported via the first transport radio bearer, and communicating via the distributed unit a third service message for activating the first transport radio bearer.
[0262]
[0273] Aspect 14: The method of aspect 13, wherein the third service message includes one or more indications of a buffer status report associated with the first transport radio bearer, a target delivery time for a first packet of further information data to be transported via the first transport radio bearer, or any combination thereof.
[0263]
[0274] Aspect 15: The method of any of aspects 1 to 14, further comprising communicating, via the distributed unit, a second service message indicating release of a first transport radio bearer associated with the first transport service, wherein the second service message is communicated in response to a lack of information to be transported via the first transport radio bearer, expiration of data associated with the first transport radio bearer, or any combination thereof.
[0264]
[0275] Aspect 16: The method of any of Aspects 1 to 15, further including: receiving an updated physical resource configuration from the distributed unit in response to an updated configuration associated with the first transport service; and communicating, via the distributed unit, information to be transported via the first transport service based at least in part on the updated physical resource configuration.
[0265]
[0276] Aspect 17: A method according to any one of aspects 1 to 16, wherein the first transport service is provided in a protocol layer associated with the first transport radio bearer, and the protocol layer is an Internet Protocol (IP) layer or a Packet Data Convergence Protocol (PDCP) layer.
[0266]
[0277] Aspect 18: A method for wireless communication in a distributed unit, the method including: communicating a first service message between a UE and a first transport service provided by a service-based network, the first service message establishing the first transport service and indicating one or more attributes associated with information to be transported via the first transport service; receiving a radio access network configuration from the first transport service indicating a first transport radio bearer and traffic flow information associated with the first transport radio bearer; in response to the radio access network configuration, sending to the UE a physical resource configuration for communication associated with the first transport service and a mapping of the first transport radio bearer to a first channel between the UE and the distributed unit; and communicating the information to be transported via the first transport service between the UE and the first transport service based at least in part on the physical resource configuration.
[0267]
[0278] Aspect 19: The method of aspect 18, further comprising mapping the first transport radio bearer and at least one other transport radio bearer to the first channel, each transport radio bearer having an associated transport service.
[0268]
[0279] Aspect 20: The method of any of aspects 18 to 19, wherein the first service message includes one or more quality of service targets associated with the information to be transported via the first transport service.
[0269]
[0280] Aspect 21: A method according to any of aspects 18 to 20, wherein information to be transported via the first transport service is transmitted using a plurality of packets, each packet of the plurality of packets including an indication of the first transport radio bearer.
[0270]
[0281] Aspect 22: The method of any of aspects 18 to 21, wherein the first transport radio bearer provides communication for both signaling information and data associated with the first transport service.
[0271]
[0282] Aspect 23: The method of any of aspects 18 to 22, further including: aggregating traffic flow information across the first transport service and one or more other transport services; and configuring one or more carriers and one or more resource grants of a physical resource configuration based at least in part on the aggregated traffic flow information.
[0272]
[0283] Aspect 24: The method of any of aspects 18 to 23, further including communicating with the first transport service based at least in part on a communication protocol that provides an indication of the first transport radio bearer for each of a plurality of packets associated with the first transport radio bearer and that provides an indication of traffic flow information associated with the first transport radio bearer.
[0273]
[0284] Aspect 25: An apparatus for wireless communication in a UE, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor, the instructions causing the apparatus to perform a method according to any of aspects 1 to 17.
[0274]
[0285] Aspect 26: An apparatus for wireless communication in a UE, the apparatus comprising at least one means for performing the method of any of aspects 1-17.
[0275]
[0286] Aspect 27: A non-transitory computer-readable medium storing code for wireless communication in a UE, the code including instructions executable by a processor for performing the method of any of aspects 1-17.
[0276]
[0287] Aspect 28: An apparatus for wireless communication in a distributed unit, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor, the instructions causing the apparatus to perform a method according to any one of aspects 18 to 24.
[0277]
[0288] Aspect 29: An apparatus for wireless communication in a distributed unit, comprising at least one means for performing the method of any of aspects 18-24.
[0278]
[0289] Aspect 30: A non-transitory computer-readable medium storing code for wireless communication in a distributed unit, the code including instructions executable by a processor for performing any of the methods of aspects 18-24.
[0279]
[0290] It should be noted that the methods described herein describe possible implementations, that operations and steps may be rearranged or otherwise modified, and that other implementations are possible. Furthermore, aspects from two or more of these methods may be combined.
[0280]
[0291] Although aspects of an LTE, LTE-A, LTE-A Pro, or NR system may be described as examples, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used throughout much of the description, the techniques described herein may be applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR. For example, the described techniques may be applicable to various other wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio techniques not explicitly mentioned herein.
[0281]
[0292] The information and signals described herein may be represented using any of a wide variety of techniques and technologies. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
[0282]
[0293] The various example blocks and components described in connection with the disclosure herein may be implemented or performed using a general purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but alternatively, the processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).
[0283]
[0294] The functions described herein may be implemented using hardware, software executed by a processor, firmware, or any combination thereof. If implemented using software executed by a processor, the functions may be stored on or transmitted using one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination thereof. The features implementing the functions may also be physically located in various locations, including being distributed so that portions of the functions are performed at different physical locations.
[0284]
[0295] Computer-readable media includes both non-transitory computer storage media and communication media, including any medium that facilitates transfer of a computer program from one place to another. Non-transitory storage media may be any available medium that can be accessed by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, Electrically Erasable Programmable ROM (EEPROM), flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code means in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer or processor. Also, any connection is properly termed a computer-readable medium. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL), or wireless techniques such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless techniques such as infrared, radio, and microwave are included within the definition of computer-readable media. As used herein, disk and disc include CDs, laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs. While a disk may reproduce data magnetically, a disc may reproduce data optically using a laser. Combinations of the above are also included within the scope of computer-readable media.
[0285]
[0296] As used herein, including in the claims, "or" as used in a list of items (e.g., a list of items followed by a phrase such as "at least one of" or "one or more of") indicates an inclusive list, such as, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also, as used herein, the phrase "based on" should not be construed as referring to a closed set of conditions. For example, an example step described as "based on condition A" could be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" is to be interpreted the same as the phrase "based at least in part on."
[0286]
[0297] The terms "determine" or "determining" encompass various actions, and thus "determining" may include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, database, or other data structure), ascertaining, and the like. "Determining" may also include receiving (e.g., receiving information), accessing (e.g., accessing data stored in a memory), and the like. "Determining" may also include resolving, obtaining, selecting, choosing, establishing, and other similar acts.
[0287]
[0298] In the accompanying figures, similar components or features may have the same reference label. Furthermore, various components of the same type may be distinguished by following the reference label with a dash and a second label that distinguishes between the similar components. If only a first reference label is used herein, the description is applicable to any of the similar components having the same first reference label, regardless of a second reference label, or any other subsequent reference label.
[0288]
[0299] The descriptions set forth herein with reference to the accompanying drawings illustrate example configurations and do not necessarily represent every example that may be implemented or fall within the scope of the claims. As used herein, the term "example" means "serving as an example, instance, or illustration," and does not mean "preferred" or "advantageous over other examples." The detailed description includes specific details for the purpose of providing an understanding of the described techniques. However, these techniques may be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described examples.
[0289]
[0300] The description herein is provided to enable any person skilled in the art to make or use the disclosure. Various modifications of the disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not intended to be limited to the examples and designs described herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims
1. 1. A method for wireless communication in a user equipment (UE), comprising: communicating a first service message via a distributed unit to establish a first transport radio bearer with a first transport service provided by a service-based network, the first service message indicating one or more attributes associated with information to be transported via the first transport radio bearer; receiving from the distributed unit in response to the first service message a physical resource configuration for communication associated with the first transport service and a mapping of the first transport radio bearer to a first channel between the UE and the distributed unit; communicating, via the distributed unit, the information to be transported via the first transport service based at least in part on the physical resource configuration; A method comprising:
2. 10. The method of claim 1, further comprising: mapping one or more transport radio bearers to the first channel, each of the transport radio bearers having an associated transport service.
3. 2. The method of claim 1, wherein the information to be transported via the first transport service is split across two or more channels between the UE and the distributed unit, including a separate channel for signaling information.
4. 4. The method of claim 3, wherein the division across the two or more channels is based at least in part on one or more of a traffic priority of the information to be transported via the first transport service, a delay tolerance of the traffic of the information to be transported via the first transport service, a traffic tolerance error rate of the information to be transported via the first transport service, or any combination thereof.
5. 2. The method of claim 1, wherein two or more transport radio bearers from the first transport service are mapped to the first channel, or one transport radio bearer is mapped to the first channel, or multiple transport radio bearers are mapped to each of two or more channels.
6. 2. The method of claim 1, wherein the first service message includes one or more quality of service targets associated with the information to be transported via the first transport service, and different quality of service targets are associated with different channels between the UE and the distributed unit.
7. 2. The method of claim 1, wherein the information to be transported over the first transport service is transmitted using a plurality of packets, each packet of the plurality of packets including an indication of the first transport radio bearer.
8. 10. The method of claim 1, wherein the first transport radio bearer provides communication for both signaling information and data associated with the first transport service.
9. The communicating the first service message comprises:
2. The method of claim 1, comprising communicating the one or more attributes associated with information to be transported via the first transport service as one or more quality of service parameters including a latency target, a throughput target, a security level, or any combination thereof.
10. 10. The method of claim 1, further comprising: communicating, via the distribution unit, one or more buffer status reports to the first transport service to maintain an active state in the first transport service.
11. receiving an indication to suppress information to be transported via the first transport service; Throttling the information communicated via the first transport service regardless of the amount of information communicated via one or more other transport services different from the first transport service; The method of claim 1 further comprising:
12. 2. The method of claim 1, further comprising: communicating, via the distributed unit, a second service message indicating deactivation of the first transport radio bearer associated with the first transport service.
13. obtaining further information to be transported via the first transport radio bearer following deactivation of the first transport service; communicating, via the distributed unit, a third service message for activating the first transport radio bearer; and The method of claim 12 further comprising:
14. 14. The method of claim 13, wherein the third service message comprises an indication of one or more of a buffer status report associated with the first transport radio bearer, a target delivery time for a first packet of the further information data to be transported over the first transport radio bearer, or any combination thereof.
15. 2. The method of claim 1, further comprising: communicating, via the distributed unit, a second service message indicating release of the first transport radio bearer associated with the first transport service, wherein the second service message is communicated in response to a lack of information to be transported over the first transport radio bearer, expiration of data associated with the first transport radio bearer, or any combination thereof.
16. receiving an updated physical resource configuration from the distributed unit in response to the updated configuration associated with the first transport service; communicating, via the distributed unit, the information to be transported via the first transport service based at least in part on the updated physical resource configuration; The method of claim 1 further comprising:
17. 2. The method of claim 1, wherein the first transport service is provided in a protocol layer associated with the first transport radio bearer, the protocol layer being an Internet Protocol (IP) layer or a Packet Data Convergence Protocol (PDCP) layer.
18. 1. A method for wireless communication in distributed units, comprising: communicating a first service message between a user equipment (UE) and a first transport service provided by a service-based network, the first service message establishing the first transport service and indicating one or more attributes associated with information to be transported via the first transport service; receiving a radio access network configuration from the first transport service indicating a first transport radio bearer and traffic flow information associated with the first transport radio bearer; transmitting to the UE, in response to the radio access network configuration, a physical resource configuration for communication associated with the first transport service and a mapping of the first transport radio bearer to a first channel between the UE and the distributed unit; communicating the information to be transported via the first transport service between the UE and the first transport service based at least in part on the physical resource configuration; A method comprising:
19. Mapping the first transport radio bearer and at least one other transport radio bearer to the first channel, each transport radio bearer having an associated transport service.
20. The method of claim 18, further comprising:
20. 20. The method of claim 18, wherein the first service message includes one or more quality of service targets associated with the information to be transported via the first transport service.
21. 20. The method of claim 18, wherein the information to be transported over the first transport service is transmitted using a plurality of packets, each packet of the plurality of packets including an indication of the first transport radio bearer.
22. 20. The method of claim 18, wherein the first transport radio bearer provides communication for both signaling information and data associated with the first transport service.
23. aggregating traffic flow information across the first transport service and one or more other transport services; configuring one or more carriers and one or more resource grants of the physical resource configuration based at least in part on the aggregated traffic flow information; 20. The method of claim 18, further comprising:
24. providing an indication of the first transport radio bearer for each of a plurality of packets associated with the first transport radio bearer, and communicating with the first transport service based at least in part on a communications protocol that provides an indication of traffic flow information associated with the first transport radio bearer.
20. The method of claim 18, further comprising:
25. 1. A method for wireless communication in a core network service provided by a service-based network, comprising: communicating a first service message to a user equipment (UE) via a distributed unit to establish a first transport radio bearer with a first transport service provided by the service-based network, the first service message indicating one or more attributes associated with information to be transported via the first transport radio bearer; outputting a second service message to the distributed unit indicating a radio access network configuration for the first transport radio bearer and traffic flow information associated with the first transport radio bearer; communicating, via the distributed unit, the information to be transported via the first transport service using the first transport radio bearer; A method comprising:
26. 26. The method of claim 25, wherein the first service message includes one or more quality of service targets associated with the information to be transported via the first transport service.
27. 26. The method of claim 25, wherein the information to be transported over the first transport service is transmitted using a plurality of packets, each packet of the plurality of packets including an indication of the first transport radio bearer.
28. providing an updated radio access network configuration to the distributed unit indicating updated traffic flow information associated with the first transport radio bearer; communicating with the UE via the distributed unit using the first transport radio bearer based at least in part on the updated radio access network configuration; 26. The method of claim 25, further comprising:
29. 1. An apparatus for wireless communication in a user equipment (UE), comprising: a processor; a memory coupled to the processor; Instructions stored in the memory and executable by the processor, causing the device to: communicating a first service message via a distributed unit to establish a first transport radio bearer with a first transport service provided by a service-based network, the first service message indicating one or more attributes associated with information to be transported via the first transport radio bearer; receiving from the distributed unit in response to the first service message a physical resource configuration for communication associated with the first transport service and a mapping of the first transport radio bearer to a first logical channel between the UE and the distributed unit; communicating, via the distributed unit, the information to be transported via the first transport service based at least in part on the physical resource configuration; Commands and An apparatus comprising:
30. The instructions are further executable by the processor to cause the device to:
30. The apparatus of claim 29, wherein one or more transport radio bearers are mapped to the first channel, each of the transport radio bearers having an associated transport service.