Patent Application
20250212182
Aspects pertain to wireless communications. Some aspects relate to slice and other resource allocation for paired processing between user devices.
Users sometimes wish to connect to another computer remotely. Remote desktop protocols and related technologies permit this connection and access. However, these technologies can be cumbersome. Furthermore, these technologies do not give the user the native feel of using the remote computer and inputs and operations can be limited.
In the figures, which are not necessarily drawn to scale, like numerals may describe similar components in different views. Like numerals having different letter suffixes may represent different instances of similar components. The figures illustrate generally, by way of example, but not by way of limitation, various aspects discussed in the present document.
The following description and the drawings sufficiently illustrate aspects to enable those skilled in the art to practice them. Other aspects may incorporate structural, logical, electrical, process, and other changes. Portions and features of some aspects may be included in or substituted for, those of other aspects. Aspects outlined in the claims encompass all available equivalents of those claims.
Referring now to
The management portion/side of the architecture 300 includes the SMO Framework 302 containing the non-RT RIC 312 and may include the O-Cloud 306. The O-Cloud 306 is a cloud computing platform including a collection of physical infrastructure nodes to host the relevant O-RAN functions (e.g., the near-RT RIC 314, O-RAN Central Unit-Control Plane (O-CU-CP) 321, O-RAN Central Unit-User Plane (O-CU-UP) 322, and the O-RAN Distributed Unit (O-DU) 315), supporting software components (e.g., OSs, VMs, container runtime engines, ML engines, etc.), and appropriate management and orchestration functions.
The radio portion/side of the logical architecture 300 includes the near-RT RIC 314, the O-RAN Distributed Unit (O-DU) 315, the O-RU 316, the O-RAN Central Unit-Control Plane (O-CU-CP) 321, and the O-RAN Central Unit-User Plane (O-CU-UP) 322 functions. The radio portion/side of the logical architecture 300 may also include the O-e/gNB 310.
The O-DU 315 is a logical node hosting RLC, MAC, and higher PHY layer entities/elements (High-PHY layers) based on a lower-layer functional split. The O-RU 316 is a logical node hosting lower PHY layer entities/elements (Low-PHY layer) (e.g., FFT/iFFT, PRACH extraction, etc.) and RF processing elements based on a lower layer functional split. The O-CU-CP 321 is a logical node hosting the RRC and the control plane (CP) part of the PDCP protocol. The O O-CU-UP 322 is a logical node hosting the user-plane part of the PDCP protocol and the SDAP protocol.
In any of the system architectures and networks described with respect to
As described earlier herein, users may wish to use an application (e.g., a gaming application or other processing-intensive application) on a low- or medium-end device 402 while leveraging the processing power of a different user device 404 or device 406. Device/s 404, 406 may be remote from device 402 (e.g., in a separate room or separate building from device 402, although aspects of the disclosure are not limited thereto). In examples, the device/s 404, 406 can have enhanced or improved processing power relative to device 402.
There are currently technologies available to for enabling the above interaction. For example, remote desktop protocols and related technologies permit connection and access from one device to another, but remote desktop technologies do not give the user the native feel of using the remote computer and inputs and operations can be limited. Aspects of the disclosure address these and other concerns by providing a low-end or medium-end device (e.g., device 402) methodologies to use processing capabilities of device/s 404, 406 in real-time.
Systems and methods according to aspects of the disclosure can improve stability and reduce the latency of communication between device 402 and device 404 or device 406. Data can be exchanged in real-time and with little or no lag or jitter. The device 402 can specify or request a latency for which communications should occur and the device 402 and device/s 404, 406 can negotiate a latency number for the communications to take place according to various aspects of the disclosure.
Packet processing can proceed according to negotiated latency requirements between device 402 and device 404. Device 402 can transmit packets to be processed by device/s 404, 406 at signal 403. The device 402 can uplink packets and O-DU 414 (e.g., at layer 2) can assign the packets an identifier or identification (e.g., unique latency number) and then provide these packets to O-DU 414 layer 1. O-DU 414 layer 1 can access the negotiated latency requirement and process the packets to match the negotiated latency requirement. The unique latency number can be a unique identifier to identify the source of the data packets (e.g., device 402 in the example illustrated).
Device 404 (or device 406, depending on which device is to be requested or used by device 402) can access downlink packets at O-DU 416 layer 1, access the unique latency number, match the unique latency number with the number provided on the uplink by device 402, and process the downlink packets 405 to match the negotiated latency requirement. O-DU 416 layer 2 can obtain packets from layer 1 and match the end-to-end latency requirement between device 402 and device 404. The device/s 404, 406 can then implement the desired device 402 application and return data or other user information.
O-DU 414 and O-DU 416 can provide resources (e.g., resource elements or other types of resources that can vary based on RAT) to maintain consistent uplink/downlink latency within the negotiated limits. As such, the O-DU 414, 416 can configure communication resources based on the latency requirement. Such configuration can include, as an example, carrier aggregation, although embodiments are not limited to carrier aggregation implementation or to any particular RAT.
Furthermore, a consistent stream of packets should be provided between device 402 and device/s 404, 406. Such consistency can be provided with resource allocation and also by layer 1 reserving a number of CPU cores for subsequent transmission interval packet processing at layer 1. If at any time a lag or unbalance is noticed (e.g., if latency increases) further resources can be allocated/adjusted. If further resources are not available (either to device 402 or to device 404, 406) or there is otherwise a mismatch between resources, then resources can be de-allocated from the other side (e.g., from either device 402 or device 404, 406) to maintain balance in resources.
The O-DU 414, 416 can implement synchronization of packets from device 402 and device 404, 406 so that they are processed within acceptable latency. Depending on the negotiated latency requirement appropriate O-DU 414, 416, layer 1 CPU resource slices can be allocated so that processing happens within an acceptable transmission time interval.
There can be a dependency or attachment between resources (e.g., over-the-air resources) and computing slices/computing resources of O-DU 414, 416 layer 1. In this regard, if for example sufficient over-the-air resource elements are available to maintain latency but slices are not available at O-DU 414, 416 layer 1, then resource elements can be de-allocated to match available slices. If sufficient slices are available at O-DU 414, 416 layer 1, but over-the-air resource elements are not available, then slices can be de-allocated to match available over-the-air resources. Furthermore, if future capacity can be predicted or detected, then O-DU 414, 416 can reserve CPU slices for a number of transmission time intervals or other time period.
Referring still to
The O-RAN Radio Unit (O-RU) 420, 422, 424 may have limited functionality including an antenna and circuitry for transmitting wireless signals converting signals from digital to analog, beamforming, etc. External IP network 426 can be provided and similar to external network 131A described with reference to
Procedures, operations, and apparatuses described herein allow implementation of an algorithm on a protocol's physical layer (e.g., Layer 1) to provide low latency processing at a network-side device (e.g., O-DU). Messaging can occur using, for example, with L1-L2 application programming interface (API) from the O-DU to O-CU, wherein details regarding O-DU and O-CU are provided with reference to
The method 500 can begin with operation 502 with receiving communications from a first user device 402 (
The method 500 can continue with operation 504 with determining a latency requirement for the user application. The latency requirement can be provided within a parameter or request of the first user device 402 and/or negotiated between the first user device 402 and the second user device 404.
The method 500 can continue with operation 506 with configuring communication resources based on the latency requirement. The resources can include any over-the-air resources such as resource elements, cell carrier aggregation, etc. but aspects of the disclosure are not limited to any particular communication standard, RAT, or resource type.
The method 500 can continue with operation 508 with configuring communication of user application data based on the latency requirement and using the configured communication resources. At this point, a user can be executing an application on the first user device 402 while leveraging resources of the second user device 404.
LTE and LTE-Advanced are standards for wireless communications of high-speed data for UE such as mobile telephones. In LTE-Advanced and various wireless systems, carrier aggregation is a technology according to which multiple carrier signals operating on different frequencies may be used to carry communications for a single UE, thus increasing the bandwidth available to a single device. In some aspects, carrier aggregation may be used where one or more component carriers operate on unlicensed frequencies.
Aspects described herein can be used in the context of any spectrum management scheme including, for example, dedicated licensed spectrum, unlicensed spectrum, (licensed) shared spectrum (such as Licensed Shared Access (LSA) in 2.3-2.4 GHz, 3.4-3.6 GHZ, 3.6-3.8 GHz, and further frequencies and Spectrum Access System (SAS) in 3.55-3.7 GHz and further frequencies).
Aspects described herein can also be applied to different Single Carrier or OFDM flavors (CP-OFDM, SC-FDMA, SC-OFDM, filter bank-based multicarrier (FBMC), OFDMA, etc.) and in particular 3GPP NR (New Radio) by allocating the OFDM carrier data bit vectors to the corresponding symbol resources.
Referring again to
In an aspect, the UEs 101 and 102 may further directly exchange communication data via a ProSe interface 105. The ProSe interface 105 may alternatively be referred to as a sidelink interface comprising one or more logical channels, including but not limited to a Physical Sidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Discovery Channel (PSDCH), and a Physical Sidelink Broadcast Channel (PSBCH).
The UE 102 is shown to be configured to access an access point (AP) 106 via connection 107. The connection 107 can comprise a local wireless connection, such as, for example, a connection consistent with any IEEE 802.11 protocol, according to which the AP 106 can comprise a wireless fidelity (WiFi®) router. In this example, the AP 106 is shown to be connected to the Internet without connecting to the core network of the wireless system (described in further detail below).
The RAN 110 can include one or more access nodes that enable connections 103 and 104. These access nodes (ANs) can be referred to as base stations (BSs), NodeBs, evolved NodeBs (eNBs), Next Generation NodeBs (gNBs), RAN network nodes, and the like, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell). In some aspects, communication nodes 111 and 112 can be transmission/reception points (TRPs). In instances when the communication nodes 111 and 112 are NodeBs (e.g., eNBs or gNBs), one or more TRPs can function within the communication cell of the NodeBs. The RAN 110 may include one or more RAN nodes for providing macrocells, e.g., macro RAN node 111, and one or more RAN nodes for providing femtocells or picocells (e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells), e.g., low power (LP) RAN node 112 or an unlicensed spectrum based secondary RAN node 112.
Any of the RAN nodes 111 and 112 can terminate the air interface protocol and can be the first point of contact for the UEs 101 and 102. In some aspects, any of the RAN nodes 111 and 112 can fulfill various logical functions for the RAN 110 including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling, and mobility management. In an example, any of the nodes 111 and/or 112 can be a new generation Node-B (gNB), an evolved node-B (eNB), or another type of RAN node.
The RAN 110 is shown to be communicatively coupled to a core network (CN) 120 via an S1 interface 113. In aspects, the CN 120 may be an evolved packet core (EPC) network, a NextGen Packet Core (NPC) network, or some other type of CN (e.g., as illustrated in reference to
In this aspect, the CN 120 comprises the MMEs 121, the S-GW 122, the Packet Data Network (PDN) Gateway (P-GW) 123, and a home subscriber server (HSS) 124. The MMEs 121 may be similar in function to the control plane of legacy Serving General Packet Radio Service (GPRS) Support Nodes (SGSN). The MMEs 121 may manage mobility aspects in access such as gateway selection and tracking area list management. The HSS 124 may comprise a database for network users, including subscription-related information to support the network entities' handling of communication sessions. The CN 120 may comprise one or several HSSs 124, depending on the number of mobile subscribers, the capacity of the equipment, the organization of the network, etc. For example, the HSS 124 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc.
The S-GW 122 may terminate the S1 interface 113 towards the RAN 110, and route data packets between the RAN 110 and the CN 120. In addition, the S-GW 122 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities of the S-GW 122 may include a lawful intercept, charging, and some policy enforcement.
The P-GW 123 may terminate an SGi interface toward a PDN. The P-GW 123 may route data packets between the EPC network 120 and external networks such as a network including the application server 184 (alternatively referred to as application function (AF)) via an Internet Protocol (IP) interface 125. The P-GW 123 can also communicate data to other external networks 131A, which can include the Internet, IP multimedia subsystem (IPS) network, and other networks. Generally, the application server 184 may be an element offering applications that use IP bearer resources with the core network (e.g., UMTS Packet Services (PS) domain, LTE PS data services, etc.). In this aspect, the P-GW 123 is shown to be communicatively coupled to an application server 184 via an IP interface 125. The application server 184 can also be configured to support one or more communication services (e.g., Voice-over-Internet Protocol (VOIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UEs 101 and 102 via the CN 120.
The P-GW 123 may further be a node for policy enforcement and charging data collection. Policy and Charging Rules Function (PCRF) 126 is the policy and charging control element of the CN 120. In a non-roaming scenario, in some aspects, there may be a single PCRF in the Home Public Land Mobile Network (HPLMN) associated with a UE's Internet Protocol Connectivity Access Network (IP-CAN) session. In a roaming scenario with a local breakout of traffic, there may be two PCRFs associated with a UE's IP-CAN session: a Home PCRF (H-PCRF) within an HPLMN and a Visited PCRF (V-PCRF) within a Visited Public Land Mobile Network (VPLMN). The PCRF 126 may be communicatively coupled to the application server 184 via the P-GW 123.
An NG system architecture can include the RAN 110 and a 5G network core (5GC) 120. The NG-RAN 110 can include a plurality of nodes, such as gNBs and NG-eNBs. The core network 120 (e.g., a 5G core network or 5GC) can include an access and mobility function (AMF) and/or a user plane function (UPF). The AMF and the UPF can be communicatively coupled to the gNBs and the NG-eNBs via NG interfaces. More specifically, in some aspects, the gNBs and the NG-eNBs can be connected to the AMF by NG-C interfaces, and the UPF by NG-U interfaces. The gNBs and the NG-eNBs can be coupled to each other via Xn interfaces.
In some aspects, the NG system architecture can use reference points between various nodes as provided by 3GPP Technical Specification (TS) 23.501 (e.g., V15.4.0, 2018-12). In some aspects, each of the gNBs and the NG-eNBs can be implemented as a base station, a mobile edge server, a small cell, a home eNB, a RAN network node, and so forth. In some aspects, a gNB can be a master node (MN) and NG-eNB can be a secondary node (SN) in a 5G architecture. In some aspects, the master/primary node may operate in a licensed band and the secondary node may operate in an unlicensed band.
In some aspects, the 5G system architecture 140B includes an IP multimedia subsystem (IMS) 168B as well as a plurality of IP multimedia core network subsystem entities, such as call session control functions (CSCFs). More specifically, the IMS 168B includes a CSCF, which can act as a proxy CSCF (P-CSCF) 162BE, a serving CSCF (S-CSCF) 164B, an emergency CSCF (E-CSCF) (not illustrated in
In some aspects, the UDM/HSS 146 can be coupled to an application server 160B, which can include a telephony application server (TAS) or another application server (AS). The AS 160B can be coupled to the IMS 168B via the S-CSCF 164B or the I-CSCF 166B.
A reference point representation shows that interaction can exist between corresponding NF services. For example,
Referring again to
The Open Fronthaul (OF) interface(s) is/are between O-DU 315 and O-RU 316 functions. The OF interface(s) includes the Control User Synchronization (CUS) Plane and Management (M) Plane.
The F1-c interface connects the O-CU-CP 321 with the O-DU 315. As defined by 3GPP, the F1-c interface is between the gNB-CU-CP and gNB-DU nodes. However, for purposes of O-RAN, the F1-c interface is adopted between the O-CU-CP 321 with the O-DU 315 functions while reusing the principles and protocol stack defined by 3GPP and the definition of interoperability profile specifications.
The F1-u interface connects the O-CU-UP 322 with the O-DU 315. As defined by 3GPP, the F1-u interface is between the gNB-CU-UP and gNB-DU nodes. However, for purposes of O-RAN, the F1-u interface is adopted between the O-CU-UP 322 with the O-DU 315 functions while reusing the principles and protocol stack defined by 3GPP and the definition of interoperability profile specifications.
The NG-c interface is defined by 3GPP as an interface between the gNB-CU-CP and the AMF in the 5GC. The NG-c is also referred to as the N2 interface (see [O06]). The NG-u interface is defined by 3GPP, as an interface between the gNB-CU-UP and the UPF in the 5GC. The NG-u interface is referred to as the N3 interface. In O-RAN, NG-c and NG-u protocol stacks defined by 3GPP are reused and may be adapted for O-RAN purposes.
The X2-c interface is defined in 3GPP for transmitting control plane information between eNBs or between eNB and en-gNB in EN-DC. The X2-u interface is defined in 3GPP for transmitting user plane information between eNBs or between eNB and en-gNB in EN-DC. In O-RAN, X2-c and X2-u protocol stacks defined by 3GPP are reused and may be adapted for O-RAN purposes.
The Xn-c interface is defined in 3GPP for transmitting control plane information between gNBs, ng-eNBs, or between an ng-eNB and gNB. The Xn-u interface is defined in 3GPP for transmitting user plane information between gNBs, ng-eNBs, or between ng-eNB and gNB. In O-RAN, Xn-c and Xn-u protocol stacks defined by 3GPP are reused and may be adapted for O-RAN purposes.
The E1 interface is defined by 3GPP as being an interface between the gNB-CU-CP (e.g., gNB-CU-CP 3728) and gNB-CU-UP (see e.g., [O07], [O09]). In O-RAN, E1 protocol stacks defined by 3GPP are reused and adapted as an interface between the O-CU-CP 621 and the O-CU-UP 622 functions.
The O-RAN Non-Real Time (RT) RAN Intelligent Controller (RIC) 312 is a logical function within the SMO framework 202, 302 that enables non-real-time control and optimization of RAN elements and resources; AI/machine learning (ML) workflow(s) including model training, inferences, and updates; and policy-based guidance of applications/features in the Near-RT RIC 314.
In some embodiments, the non-RT RIC 312 is a function that sits within the SMO platform (or SMO framework) 302 in the O-RAN architecture. The primary goal of non-RT RIC is to support intelligent radio resource management for a non-real-time interval (i.e., greater than 500 ms), policy optimization in RAN, and insertion of AI/ML models to near-RT RIC and other RAN functions. The non-RT RIC terminates the A1 interface to the near-RT RIC. It will also collect OAM data over the O1 interface from the O-RAN nodes.
The O-RAN near-RT RIC 314 is a logical function that enables near-real-time control and optimization of RAN elements and resources via fine-grained data collection and actions over the E2 interface. The near-RT RIC 314 may include one or more AI/ML workflows including model training, inferences, and updates.
The non-RT RIC 312 can be an ML training host to host the training of one or more ML models. ML training can be performed offline using data collected from the RIC, O-DU 315, and O-RU 316. For supervised learning, non-RT RIC 312 is part of the SMO 302, and the ML training host and/or ML model host/actor can be part of the non-RT RIC 312 and/or the near-RT RIC 314. For unsupervised learning, the ML training host and ML model host/actor can be part of the non-RT RIC 312 and/or the near-RT RIC 314. For reinforcement learning, the ML training host and ML model host/actor may be co-located as part of the non-RT RIC 312 and/or the near-RT RIC 314. In some implementations, the non-RT RIC 312 may request or trigger ML model training in the training hosts regardless of where the model is deployed and executed. ML models may be trained and not currently deployed.
The A1 interface is between the non-RT RIC 312 (within or outside the SMO 302) and the near-RT RIC 314. The A1 interface supports three types of services, including a Policy Management Service, an Enrichment Information Service, and an ML Model Management Service.
In some embodiments, an O-RAN network node can include a disaggregated node with at least one O-RAN Radio Unit (O-RU), at least one O-DU coupled via an F1 interface to at least one O-CU coupled via an E2 interface to a RIC (e.g., RIC 312 and/or RIC 314).
As illustrated in
As illustrated in
As illustrated in
As illustrated in
As illustrated in
As illustrated in
In example embodiments, any of the UEs or RAN network nodes discussed in connection with
The communication device may include a hardware processor 602 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory 604, a static memory 606, and mass storage 607 (e.g., hard drive, tape drive, flash storage, or other block or storage devices), some or all of which may communicate with each other via an interlink (e.g., bus) 608.
The communication device 600 may further include a display device 610, an alphanumeric input device 612 (e.g., a keyboard), and a user interface (UI) navigation device 614 (e.g., a mouse). In an example, the display device 60, input device 612, and UI navigation device 614 may be a touchscreen display. The communication device 600 may additionally include a signal generation device 618 (e.g., a speaker), a network interface device 620, and one or more sensors 621, such as a global positioning system (GPS) sensor, compass, accelerometer, or another sensor. The communication device 600 may include an output controller 628, such as a serial (e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate or control one or more peripheral devices (e.g., a printer, card reader, etc.).
The mass storage 607 may include a communication device-readable medium 622, on which is stored one or more sets of data structures or instructions 624 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein. In some aspects, registers of the processor 602, the main memory 604, the static memory 606, and/or the mass storage 607 may be, or include (completely or at least partially), the device-readable medium 622, on which is stored the one or more sets of data structures or instructions 624, embodying or utilized by any one or more of the techniques or functions described herein. In an example, one or any combination of the hardware processor 602, the main memory 604, the static memory 606, or the mass storage 607 may constitute the device-readable medium 622.
As used herein, the term “device-readable medium” is interchangeable with “computer-readable medium” or “machine-readable medium.” While the communication device-readable medium 622 is illustrated as a single medium, the term “communication device-readable medium” may include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) configured to store the one or more instructions 624. The term “communication device-readable medium” is inclusive of the terms “machine-readable medium” or “computer-readable medium”, and may include any medium that is capable of storing, encoding, or carrying instructions (e.g., instructions 624) for execution by the communication device 600 and that causes the communication device 600 to perform any one or more of the techniques of the present disclosure, or that is capable of storing, encoding or carrying data structures used by or associated with such instructions. Non-limiting communication device-readable medium examples may include solid-state memories and optical and magnetic media. Specific examples of communication device-readable media may include non-volatile memory, such as semiconductor memory devices (e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; Random Access Memory (RAM); and CD-ROM and DVD-ROM disks. In some examples, communication device-readable media may include non-transitory communication device-readable media. In some examples, communication device-readable media may include communication device-readable media that is not a transitory propagating signal.
Instructions 624 may further be transmitted or received over a communications network 626 using a transmission medium via the network interface device 620 utilizing any one of several transfer protocols. In an example, the network interface device 620 may include one or more physical jacks (e.g., Ethernet, coaxial, or phone jacks) or one or more antennas to connect to the communications network 626. In an example, the network interface device 620 may include a plurality of antennas to wirelessly communicate using at least one single-input-multiple-output (SIMO), MIMO, or multiple-input-single-output (MISO) techniques. In some examples, the network interface device 620 may wirelessly communicate using Multiple User MIMO techniques.
The term “transmission medium” shall be taken to include any intangible medium that is capable of storing, encoding, or carrying instructions for execution by the communication device 600, and includes digital or analog communications signals or another intangible medium to facilitate communication of such software. In this regard, a transmission medium in the context of this disclosure is a device-readable medium.
Example aspects of the present disclosure are further disclosed hereinbelow.
Example 1 is a network device comprising: communication circuitry configured to receive communications from a first user device for running a user application on a second user device; and processing circuitry coupled to the communication circuitry configured to: determine a latency requirement for the user application; configure communication resources based on the latency requirement; and configure communication of user application data based on the latency requirement and using the configured communication resources.
In Example 2, the subject matter of Example 1 can optionally include wherein the processing circuitry includes multiple processing slices and wherein the processing circuitry is further configured to allocate processing slices based on the latency requirement.
In Example 3, the subject matter of any of Examples 1-2 can optionally include wherein user application data includes identification information for the first user device.
In Example 4, the subject matter of Example 3 can optionally include wherein the identification information includes an indication of a latency requirement for the first user device or for the user application.
In Example 5, the subject matter of any of Examples 1-4 can optionally include wherein configuring communication resources includes performing carrier aggregation.
In Example 6, the subject matter of any of Examples 1-5 can optionally include wherein the processing circuitry is configured to reduce communication resources for either the first user device or the second user device if a mismatch is detected between communication resources of the first user device or the second user device.
In Example 7, the subject matter of any of Examples 1-6 can optionally include wherein the processing circuitry is configured to adjust communication resources upon detecting a change in resource allocation for either or both of the first user device or the second user device.
Example 8 is an apparatus for use in an Open Radio Access Network (O-RAN) base station, the apparatus comprising: processing circuitry, wherein to configure the O-RAN base station for signal processing in an O-RAN network, the processing circuitry is to: determine a latency requirement for a user application; configure communication resources based on the latency requirement; and configure communication of user application data based on the latency requirement and using the configured communication resources; and a memory coupled to the processing circuitry and configured to store latency information and identification information for user devices associated with the user application.
In Example 9, the subject matter of Example 8 can optionally include wherein the processing circuitry is to: allocate processing slices based on the latency requirement.
In Example 10, the subject matter of any of Examples 8-9 can optionally include wherein user application data includes identification information for a first user device.
In Example 11, the subject matter of Example 10 can optionally include wherein the identification information includes an indication of a latency requirement for the first user device or for the user application.
In Example 12, the subject matter of any of Examples 8-11 can optionally include wherein configuring communication resources includes performing carrier aggregation.
In Example 13, the subject matter of any of Examples 8-12 can optionally include wherein the processing circuitry is configured to reduce communication resources for either a first user device or a second user device if a mismatch is detected between communication resources of the first user device or the second user device.
In Example 14, the subject matter of any of Examples 8-13 can optionally include wherein the processing circuitry is configured to adjust communication resources upon detecting a change in resource allocation for either or both of a first user device or a second user device.
Example 15 is a method for communicating application data from a first user device to a second user device, the method comprising: receiving communications from a first user device for running a user application on a second user device; determining a latency requirement for the user application; configuring communication resources based on the latency requirement; and configuring communication of user application data based on the latency requirement and using the configured communication resources.
In Example 16, the subject matter of Example 15 can optionally include allocating processing slices based on the latency requirement.
In Example 17, the subject matter of any of Examples 15-16 can optionally include wherein user application data includes identification information for the first user device.
In Example 18, the subject matter of Example 17 can optionally include wherein the identification information includes an indication of a latency requirement for the first user device or for the user application.
In Example 19, the subject matter of any of Examples 15-18 can optionally include wherein configuring communication resources includes performing carrier aggregation.
In Example 20, the subject matter of any of Examples 15-19 can optionally include reducing communication resources for either the first user device or the second user device if a mismatch is detected between communication resources of the first user device or the second user device.
Example 21 is a system including means for performing any of Examples 1-20.
Although example aspects have been described herein, it will be evident that various modifications and changes may be made to these aspects without departing from the broader scope of the present disclosure. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense. This Detailed Description, therefore, is not to be taken in a limiting sense, and the scope of various aspects is defined only by the appended claims, along with the full range of equivalents to which such claims are entitled.
