Partitioning application data into application data units
By dividing application data into ADUs in network nodes in wireless communication systems and adding relevant instructions, the resource allocation problem is solved, efficient resource utilization and service quality improvement are achieved, and the key performance indicator requirements of ADUs are met.
Patent Information
- Application Number
- CN202380028275.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-03-25
- Filing Date
- 2023-01-25
- Publication Date
- 2024-11-05
AI Technical Summary
When processing application data, existing wireless communication systems are difficult to effectively manage and optimize resource allocation, resulting in waste of computing resources, power resources and network resources, especially in the face of increased communication error rates, which cannot meet the application data unit (ADU). ) associated key performance indicators (KPI) requirements.
By adding an indication to an application data unit (ADU) before receiving and providing application data in a network node, the network node can divide the data packet into ADUs and process communications based on the ADU-associated indications, saving resources to meet KPI requirements, or Try to meet these requirements under conservative conditions.
Through ADU division and related indications, network nodes can save computing resources, power resources and network resources under increased communication error rates, avoid resource waste, and meet ADU-related KPI requirements under conservative conditions, thereby improving system resource utilization Efficiency and service quality.
Smart Images

Figure CN118901215A_ABST
Abstract
Description
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This patent application claims priority to U.S. non-provisional patent application No. 17 / 656,565, entitled “APPLICATION DATA UNITS,” filed on March 25, 2022, which is hereby expressly incorporated herein by reference. Technical Field
[0003] Aspects of the present disclosure relate generally to wireless communications, and to techniques and apparatus for partitioning application data into application data units. Background Art
[0004] Wireless communication systems are widely deployed to provide various telecommunication services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).
[0005] A wireless network may include one or more base stations that support communications for a user equipment (UE) or multiple UEs. A UE may communicate with a base station via downlink communications and uplink communications. A "downlink" (or "DL") refers to the communication link from a base station to a UE, and an "uplink" (or "UL") refers to the communication link from a UE to a base station.
[0006] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region and / or global level. New Radio (NR), which may be referred to as 5G, is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better integrate with other open standards by improving spectrum efficiency, reducing costs, improving services, utilizing new spectrum, and using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with cyclic prefix (CP) on the downlink, using CP-OFDM and / or single carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink, as well as supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation, so as to better support mobile broadband Internet access. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR and other radio access technologies remain useful. Summary of the invention
[0007] Some aspects described herein relate to a method of wireless communication performed by a network node. The method may include receiving application data for transmission via an additional network node. The method may include providing the application data to the additional network node, the application data having one or more indications of division into application data units (ADUs) added before being provided to the additional network node.
[0008] Some aspects described herein relate to a network node for wireless communication. The network node may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive application data for transmission via an additional network node. The one or more processors may be configured to provide the application data to the additional network node, the application data having one or more indications added prior to being provided to the additional network node to be divided into application data units (ADUs).
[0009] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a network node. The instruction set, when executed by one or more processors of the network node, may cause the network node to receive application data for transmission via an additional network node. The instruction set, when executed by one or more processors of the network node, may cause the network node to provide the application data to the additional network node, the application data having one or more indications of division into ADUs added before being provided to the additional network node.
[0010] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving application data for transmission via an additional network node. The apparatus may include means for providing the application data to the additional network node, the application data having one or more indications of partitioning into ADUs added before being provided to the additional network node.
[0011] Aspects generally include methods, apparatus, systems, computer program products, non-transitory computer readable media, user equipment, base stations, wireless communication devices and / or processing systems as fully described herein with reference to and as illustrated by the accompanying drawings and description.
[0012] The features and technical advantages of examples according to the present disclosure have been outlined quite extensively above so that the following specific embodiments may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of protection of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the accompanying drawings is provided for the purpose of illustration and description, and not as a definition of the limitations of the claims.
[0013] Although various aspects are described in the present disclosure by illustrating some examples, it will be understood by those skilled in the art that such aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment, and / or artificial intelligence devices). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components and / or system-level components. The equipment incorporating the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals may include one or more components (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers) for analog and digital purposes. The various aspects described herein are intended to be practiced in various devices, components, systems, distributed arrangements, and / or end-user devices of various sizes, shapes and configurations. BRIEF DESCRIPTION OF THE DRAWINGS
[0014] In order to fully understand the above-mentioned features of the present disclosure, a more specific description of the invention briefly summarized above can be obtained by referring to various aspects (some of which are illustrated in the accompanying drawings). However, it should be noted that the accompanying drawings only illustrate certain typical aspects of the present disclosure and are therefore not to be considered as limiting the scope thereof, as the specification may admit of other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.
[0015] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure.
[0016] Figure 2 is a diagram illustrating an example of communication between a base station and a user equipment (UE) in a wireless network according to the present disclosure.
[0017] Figure 3 is a diagram illustrating an example decomposed base station architecture according to the present disclosure.
[0018] Figure 4 is a diagram illustrating an example of an application data unit according to the present disclosure.
[0019] Figure 5 and Figure 6 is a diagram illustrating an example associated with dividing application data into application data units according to the present disclosure.
[0020] Figure 7 is a diagram illustrating an example process associated with dividing application data into application data units according to the present disclosure.
[0021] Figure 8 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION
[0022] The various aspects of the disclosure are described more fully below with reference to the accompanying drawings. However, the disclosure can be embodied in many different forms, and should not be construed as being limited to any specific structure or function presented throughout the disclosure. Instead, these aspects are provided so that the disclosure will be thorough and complete, and the protection scope of the disclosure will be fully conveyed to those skilled in the art. It will be appreciated by those skilled in the art that the scope of the disclosure is intended to cover any aspect of the disclosure disclosed herein, whether it is implemented independently or in combination with any other aspect of the disclosure. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the disclosure is intended to cover such a device or method implemented using other structures, functions, or structures and functions other than the various aspects of the disclosure set forth herein or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the claims.
[0023] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using hardware, software, or a combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.
[0024] Although aspects may be described herein using terminology generally associated with 5G or new radio (NR) radio access technology (RAT), aspects of the present disclosure may be applied to other RATs, such as 3G RAT, 4G RAT, and / or post-5G RATs (e.g., 6G).
[0025] Figure 11 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be or may include elements of a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, etc. The wireless network 100 may include one or more base stations 110 (shown as BS110a, BS110b, BS110c, and BS110d), a user equipment (UE) 120 or multiple UEs 120 (shown as UE120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other network entities. The base station 110 is an entity that communicates with the UE 120. The base station 110 (sometimes referred to as a BS) may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, and / or a transmit receive point (TRP). Each base station 110 may provide communication coverage for a specific geographic area. In the 3rd Generation Partnership Project (3GPP), the term "cell" can refer to the coverage area of a base station 110 and / or a base station subsystem serving the coverage area, depending on the context in which the term is used.
[0026] The base station 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by a UE 120 with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by a UE 120 with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by a UE 120 that has an association with the femto cell (e.g., a UE 120 in a closed subscriber group (CSG)). A base station 110 for a macro cell may be referred to as a macro base station. A base station 110 for a pico cell may be referred to as a pico base station. A base station 110 for a femto cell may be referred to as a femto base station or a home base station. In Figure 1 In the example shown, BS 110a may be a macro base station for macrocell 102a, BS 110b may be a pico base station for picocell 102b, and BS 110c may be a femto base station for femtocell 102c. A base station may support one or more (eg, three) cells.
[0027] In some examples, the cells may not necessarily be stationary, and the geographic area of the cells may move depending on the location of the mobile base station 110 (e.g., a mobile base station). In some examples, the base stations 110 may be interconnected with each other and / or to one or more other base stations 110 or network nodes (not shown) in the wireless network 100 using any suitable transport network through various types of backhaul interfaces (such as direct physical connections or virtual networks).
[0028] The wireless network 100 may include one or more relay stations. A relay station is an entity that can receive transmissions of data from an upstream station (e.g., a base station 110 or a UE 120) and transmit transmissions of data to a downstream station (e.g., a UE 120 or a base station 110). A relay station may be a UE 120 that is capable of relaying transmissions for other UEs 120. Figure 1 In the example shown, BS 110d (eg, a relay base station) may communicate with BS 110a (eg, a macro base station) and UE 120d to facilitate communications between BS 110a and UE 120d. Base station 110 that relays communications may be referred to as a relay station, relay base station, relay, or the like.
[0029] The wireless network 100 may be a heterogeneous network that includes different types of base stations 110, such as macro base stations, pico base stations, femto base stations, relay base stations, etc. These different types of base stations 110 may have different transmit power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, a macro base station may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico base station, a femto base station, and a relay base station may have a lower transmit power level (e.g., 0.1 watt to 2 watts).
[0030] The network controller 130 may be coupled to or in communication with a set of base stations 110 and may provide coordination and control for the base stations. The network controller 130 may communicate with the base stations 110 via a backhaul communication link. The base stations 110 may communicate directly with each other or indirectly via a wireless backhaul communication link or a wired backhaul communication link.
[0031] UE 120 can be dispersed throughout the wireless network 100, and each UE 120 can be stationary or mobile. UE 120 can include, for example, access terminals, terminals, mobile stations, and / or subscriber units. UE 120 can be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, an industrial manufacturing equipment, a global positioning system device, and / or any other suitable device configured to communicate via a wireless medium.
[0032] Some UE 120 may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UE. MTC UE and / or eMTC UE may include, for example, a robot, a drone, a remote device, a sensor, a meter, a monitor and / or a location tag, which may communicate with a base station, another device (e.g., a remote device) or some other entity. Some UE 120 may be considered as an Internet of Things (IoT) device and / or may be implemented as a NB-IoT (narrowband IoT) device. Some UE 120 may be considered as client equipment. UE 120 may be included inside a housing that houses components of UE 120, such as a processor component and / or a memory component. In some examples, the processor component and the memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operationally coupled, communicatively coupled, electronically coupled, and / or electrically coupled.
[0033] In general, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a specific RAT and may operate on one or more frequencies. RAT may be referred to as a radio technology, air interface, etc. Frequency may be referred to as a carrier, frequency channel, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.
[0034] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly (e.g., without using base station 110 as an intermediary to communicate with each other) using one or more side link channels. For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), and / or mesh networks. In such examples, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by base station 110.
[0035] The devices of the wireless network 100 may communicate using an electromagnetic spectrum, which may be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, the devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency ranges designated FR1 (410 MHz–7.125 GHz) and FR2 (24.25 GHz–52.6 GHz). It should be understood that, although portions of FR1 are greater than 6 GHz, FR1 is often (interchangeably) referred to as the “below 6 GHz” band in various documents and articles. Similar naming issues sometimes occur with respect to FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz–300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU).
[0036] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz–24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and therefore the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6GHz-71GHz), FR4 (52.6GHz-114.25GHz) and FR5 (114.25GHz-300GHz). Each of these higher frequency bands falls within the EHF band.
[0037] Considering the above examples, unless otherwise explicitly stated, it should be understood that if the term "below 6 GHz" or the like is used herein, the term can be broadly referred to as a frequency that can be lower than 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise explicitly stated, it should be understood that if the term "millimeter wave" or the like is used herein, the term can be broadly referred to as a frequency that can include mid-band frequencies, can be within FR2, FR4, FR4-a or FR4-1, and / or FR5, or can be within the EHF band. It is expected that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) can be modified, and the techniques described herein are applicable to those modified frequency ranges.
[0038] In some aspects, the RAN network node may include a communications manager 150. As described in greater detail elsewhere herein, the communications manager 150 may receive application data from a network node (e.g., a user plane function (UPF) and / or a service layer entity, etc.) for transmission to a UE. The RAN network node may transmit the application data based at least in part on segmenting data packets (e.g., Internet Protocol (IP) packets) into ADUs, as directed by the network node. Additionally or alternatively, the communications manager 150 may perform one or more other operations described herein.
[0039] As indicated above, Figure 1 are provided as examples. Other examples can be found in the Figure 1 Different than described.
[0040] Figure 2 2 is a diagram illustrating an example 200 of base station 110 communicating with UE 120 in wireless network 100 according to the present disclosure. Base station 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≥1). UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1).
[0041] At the base station 110, the transmit processor 220 may receive data intended for the UE 120 (or a set of UEs 120) from the data source 212. The transmit processor 220 may select one or more modulation and coding schemes (MCS) for the UE 120 based at least in part on one or more channel quality indicators (CQI) received from the UE 120. The base station 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS selected for the UE 120, and provide data symbols for the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling), and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., pre-coding) on data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a to 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may further process (e.g., convert to analog, amplify, filter, and / or up-convert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a to 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a to 234t).
[0042] At the UE 120, a set of antennas 252 (shown as antennas 252a to 252r) may receive downlink signals from the base station 110 and / or other base stations 110 and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a to 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain input samples. Each modem 254 may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modem 254, may perform MIMO detection on the received symbols where applicable, and may provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to the data sink 260, and may provide decoded control information and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter, among other things. In some examples, one or more components of the UE 120 may be included in the housing 284.
[0043] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the base station 110 via the communication unit 294.
[0044] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or be included within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include one or more antenna elements (within a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, and / or coupled to one or more transmit and / or receive components (such as, Figure 2 One or more antenna elements of one or more components in.
[0045] On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information from a controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by the TX MIMO processor 266, where applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to the base station 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to perform the functions described herein (eg, with reference to Figures 5 to 8 ) or any aspect of any of the methods described herein.
[0046] At the base station 110, uplink signals from the UE 120 and / or other UEs may be received by the antenna 234, processed by the modem 232 (e.g., a demodulator component of the modem 232 shown as DEMOD), detected by the MIMO detector 236 (if applicable), and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and the decoded control information to the controller / processor 240. The base station 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The base station 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink and / or uplink communications. In some examples, the modem 232 of the base station 110 may include a modulator and a demodulator. In some examples, the base station 110 includes a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to execute the instructions described herein (e.g., reference 20). Figures 5 to 8 ) or any aspect of any of the methods described herein.
[0047] The controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2Any other components of the RAN network node may perform one or more techniques associated with dividing application data into application data units, as described in more detail elsewhere herein. In some aspects, the RAN network node described herein is Figure 2 The base station 110 shown is included in the base station 110, or includes one or more components of the base station 110. For example, the controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the Figure 7 700 and / or operations of other processes as described herein. Memory 242 and memory 282 may store data and program codes for base station 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed by one or more processors of base station 110 and / or UE 120 (e.g., directly, or after compilation, conversion and / or interpretation), may cause one or more processors, UE 120 and / or base station 110 to perform, direct or support, for example Figure 7 The process 700 and / or operations of other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.
[0048] In some aspects, the network node includes: means for receiving application data for transmission via an additional network node; and / or means for providing application data to the additional network node, the application data having one or more indications of partitioning into ADUs added before being provided to the additional network node. In some aspects, the means for the network node to perform the operations described herein may include, for example, Figure 8 One or more of the processor 820, memory 830, input component 840, output component 850, and / or communication component 860 shown in FIG.
[0049] Although Figure 2 The blocks in the 2000 and 2010 are illustrated as distinct components, but the functionality described above for these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described with respect to the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.
[0050] As indicated above, Figure 2 are provided as examples. Other examples can be found in the Figure 2 Different than described.
[0051] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or constituent parts in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element or a network equipment (such as a base station (BS, e.g., base station 110), or one or more units (or one or more components) performing base station functionality can be implemented in an aggregated or decomposed architecture. For example, a BS (such as a Node B (NB), an eNB, an NR BS, a 5G NB, an access node (AP), a TRP, a cell, etc.) can be implemented as an aggregated base station (also called a stand-alone BS or a monolithic BS) or a decomposed base station.
[0052] The aggregated base station can be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. The decomposed base station can be configured to utilize a protocol stack physically or logically distributed between two or more units, such as one or more central or centralized units (CU), one or more distributed units (DU), or one or more radio units (RU). In some aspects, the CU can be implemented within a RAN node, and one or more DUs can be co-located with the CU, or alternatively, can be geographically or virtually distributed in one or more other RAN nodes. The DU can be implemented to communicate with one or more RUs. Each of the CU, DU, and RU can also be implemented as a virtual unit, i.e., a virtual centralized unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).
[0053] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be used in an integrated access backhaul (IAB) network, an O-RAN (such as a network configuration sponsored by the O-RAN Alliance), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Individual units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.
[0054] Figure 3The disaggregated base station architecture shown may include one or more CUs 310 that may communicate directly with a core network 320 via a backhaul link, or indirectly with a core network 320 through one or more disaggregated base station units, such as a near real-time (near-RT) RAN intelligent controller (RIC) 325 via an E2 link, or a non-real-time (non-RT) RIC 315 associated with a service management and orchestration (SMO) framework 305, or both. The CU 310 may communicate with one or more DUs 330 via respective midhaul links, such as an F1 interface. The DU 330 may communicate with one or more RUs 340 via respective fronthaul links. The RU 340 may communicate with respective UEs 120 via one or more radio frequency (RF) access links. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.
[0055] Each of these units (e.g., CU 310, DU 330, RU 340) and near-RT RIC 325, non-RTRIC 315, and SMO framework 305 may include one or more interfaces, or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interface of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface that is configured to receive or send signals to one or more of the other units via a wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, a transmitter, or a transceiver (such as an RF transceiver) that is configured to receive or send signals or both to one or more of the other units on a wireless transmission medium.
[0056] In some aspects, CU 310 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented as having an interface configured to communicate signals with other control functions hosted by CU 310. CU310 may be configured to process user plane functions (e.g., central unit-user plane (CU-UP)), control plane functions (e.g., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 310 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 310 may be implemented to communicate with DU 330 for network control and signaling.
[0057] DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RU 340. In some aspects, DU 330 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) depending at least in part on a functional split such as defined by 3GPP. In some aspects, DU 330 may further host one or more low PHY layers. Each layer (or module) may be implemented with an interface that is configured to communicate signals with other layers (and modules) hosted by DU 330 or with control functions hosted by CU 310.
[0058] The lower layer functions may be implemented by one or more RUs 340. In some deployments, the RU 340 controlled by the DU 330 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on functional splitting (such as lower layer functional splitting). In such an architecture, the RU 340 may be implemented to handle over-the-air (OTA) communications with one or more UEs 120. In some specific implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable the implementation of the DU 330 and the CU 310 in a cloud-based RAN architecture (such as a vRAN architecture).
[0059] The SMO framework 305 may be configured to support RAN deployment and configuration of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 305 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 335) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, and near-RT RIC 325. In some specific implementations, the SMO framework 305 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 311) via the O1 interface. Additionally, in some specific implementations, the SMO framework 305 may communicate directly with one or more RUs 340 via the O1 interface. The SMO framework 305 may also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305 .
[0060] The non-RT RIC 315 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 325. The non-RT RIC 315 may be coupled to or in communication with the near-RT RIC 325 (such as via an A1 interface). The near-RT RIC 325 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 310, one or more DUs 330, or both, and the O-eNB with the near-RT RIC 325.
[0061] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 325, the non-RT RIC 315 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 325 and may be received from a non-network data source or from a network function at the SMO framework 305 or the non-RT RIC 315. In some examples, the non-RT RIC 315 or the near-RT RIC 325 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 315 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 305 (such as via reconfiguration of O1) or via creation of RAN management policies (such as A1 policies).
[0062] As indicated above, Figure 3 are provided as examples. Other examples can be found in the Figure 3 Different than described.
[0063] Figure 4 is a diagram illustrating an example 400 of an ADU according to the present disclosure. Figure 4 The structure of one or more communications including application data divided into ADUs is shown. A first device (eg, a network node, a RAN network node, or an application server, etc.) may provide application data to a second device (eg, a network node, a RAN network node, or a UE, etc.).
[0064] like Figure 4 As shown, the one or more communications include a plurality of data packets 405 (e.g., IP data packets). The first device may use different network resources and / or different timing resources to send the data packets 405. The data packets 405 may be divided into ADUs 410. For example, ADU1 may be associated with a first frame of a video stream (e.g., an extended reality video stream), and ADU2 may be associated with a second frame of the video stream, and so on.
[0065] The first device may send one or more ADUs in ADU 410 within a burst 415. For example, burst 1 may include ADU1 and ADU2; burst 2 may include ADU3, ADU4, and ADU5; and burst 3 may include ADU6. A burst of ADUs may include ADUs generated within a threshold amount of time. For example, the ADUs of burst 1 may be separated in time from the ADUs of burst 2 by a threshold amount of time.
[0066] Based at least in part on the division of the data packets 405 into the ADUs 410, application key performance indicators (KPIs) may be associated with the ADUs 410 (e.g., rather than being associated with each data packet 405 individually). The KPIs may include, among others, an ADU error rate (AER), an ADU delay budget (ADB), an ADU discard time (ADT), and / or an ADU content policy (ACP). The AER may refer to the allowed number of ADUs received in error on average. The ADB may refer to the maximum amount of delay that an ADU can tolerate. The ADT may refer to the maximum queue hold for an ADU. When an ADU is FEC protected (e.g., to support recovery of the ADU), the ACP may refer to the minimum portion (e.g., fraction or percentage) of the ADU bits to be delivered. The KPIs may be associated with requirements applied to the ADU to satisfy an ADU service flow template (A-TFT) for filtering services.
[0067] In one example, quality of service (QoS) control may be applied to the ADUs rather than equally across all data packets 405. In some examples, the data packets 405 divided into the ADUs 410 may be associated with a single video frame. In this manner, later received data packets 405 of the ADUs 410 may have a shorter packet delay budget than earlier received data packets 405 of the ADUs 410, such that all data packets 405 of the ADUs 410 arrive in time for joint processing and / or rendering at a receiving device (e.g., a UE).
[0068] In some networks, a network that is unaware of the ADU (e.g., a 5G network) may consume computing resources, power resources, network resources, and / or communication resources based at least in part on an increased communication error rate, which is based at least in part on a failure to meet a KPI associated with the ADU. For example, an offline conversion of applying an ADU requirement (e.g., AER or ADB) to a data packet-based requirement (e.g., packet error rate (PER) or packet delay budget (PDB)) for each data packet may not be feasible. A relaxed PER configuration (e.g., PER=AER) results in an actual AER that is higher than the PER. In these cases, there may be a loss of information during the conversion from the ADU to the data packet-based requirement. Additionally or alternatively, a network that is unaware of the ADU may consume network resources to conservatively attempt to meet the KPI associated with the ADU. For example, a conservative conversion may require a PER that is much smaller than the AER (e.g., PER=AER / N, where N is the average number of IP packets per ADU), resulting in ultra-low capacity.
[0069] As indicated above, Figure 4 are provided as examples. Other examples can be found in the Figure 4 Different than described.
[0070] In some aspects described herein, a network node (e.g., a UPF or a service layer entity) may receive application data for transmission via an additional network node (e.g., a RAN network node) and add an indication of an ADU to the application data before providing the application data to the additional network node. Based at least in part on the network node adding the indication of the ADU to the application data, the network may be aware of the ADU (e.g., dividing data packets of the application data into ADUs). In this manner, the network (e.g., a RAN network node) may process communications associated with the application data based at least in part on the ADU (e.g., using a KPI or other additional indication associated with the ADU), which may save computing resources, power resources, network resources, and / or communication resources that may otherwise have been consumed based at least in part on an increased communication error rate, so as not to fail to meet the KPI associated with the ADU. Additionally or alternatively, the network may save network resources that may otherwise have been consumed to conservatively attempt to meet the KPI associated with the ADU. In some aspects, signaling ADU-based QoS to 5G and 5G reporting back ADU-based QoS is helpful even without a scheduler utilizing knowledge of the ADU. For example, a source of application data (e.g., an application server) can use the reporting to manage subsequent communications via the network or outside the network.
[0071] A network node (e.g., UPF) may include a service layer (e.g., an ADU service layer). In some aspects, for each ADU delivered by an application server (e.g., an application on an application server), information related to the ADU (e.g., ADU metadata) may be delivered to the network and / or an associated UE (e.g., a receiving node). The service layer of the UPF identifies the ADU and signals the information related to the ADU (e.g., a tag indicating the ADU number) to the network together with the associated data packet. In some aspects, the application server may explicitly provide information related to the ADU, and / or the network node may identify information related to the ADU from the application data. For example, a service layer entity may learn to identify the ADU and / or information related to the ADU based at least in part on one or more metrics of the service of the application data. The service layer entity may train and / or use a machine learning (ML) model to identify the ADU and / or information related to the ADU. In some aspects, the network node may decouple information associated with the ADU received from the application server from information associated with the ADU provided to the RAN network node. For example, the network node may decouple (e.g., allow differentiation between) indications of ADU partitioning and information relating to the ADU from an application server from indications of ADUs and information relating to the ADU used within the network (e.g., a RAN network node) from the network node.
[0072] A network node (e.g., a service layer entity) may receive an ADU and ADU metadata (e.g., information related to the ADU) from an application server via a dedicated interface. The UPF may provide the ADU metadata to the RAN network node in a general packet radio system (GPRS) tunneling protocol user plane (GTP-U) header. In some aspects, the dedicated interface between the UPF and the application server may be based at least in part on a new protocol and / or a customized protocol. The ADU metadata may be carried in a protocol header or may be piggybacked in the payload of the ADU. In some aspects, some ADU metadata (e.g., an identifier of the ADU) is provided per data packet, while some ADU metadata (e.g., ADU length, the number of data packets, or application FEC parameters, etc.) is provided per ADU or is updated only when the value changes. The dedicated interface may be proprietary between the application server and the UPF in the domain of the network operator, or the dedicated interface may be standardized in the communication protocol.
[0073] A network node (e.g., a service layer entity) may perform ADU identification. For example, based at least in part on the failure of an application server to provide ADU metadata to a UPF (e.g., or otherwise to a network), a network node (e.g., a service layer entity and / or UPF) may use a technique for deriving ADU metadata from a received service. In some aspects, a network node may perform deep packet inspection (DPI) for a well-known application protocol to derive ADU metadata. For example, if a video frame is sent as several real-time transport protocol (RTP) packets, the packets will all carry the same timestamp in the RTP header. Packets with the same timestamp may be considered to be associated with the same ADU. In some aspects, a network node may use an ML algorithm to derive ADU metadata. For example, a network node or another device may train a neural network-based model to identify the application type of a received service. For example, a neural network-based model may use inputs such as timing, periodicity, number of packets, packet size mode, or packet size. In some aspects, different algorithms may be applied to derive ADU metadata based at least in part on the application type. For example, for flow packets arriving in periodic bursts, a clustering algorithm may be applied to partition the packets into ADUs.
[0074] The network node may map service flows and / or ADUs to data radio bearers (DRBs). The service received from the application server may include application data for one or more service flows. One or more service flows may be mapped only to the first QoS flow. Additionally or alternatively, one or more QoS flows may be mapped to a single DRB. In some aspects, ADU-aware flows and non-ADU-aware flows may be mapped to the same DRB. Since several service flows may be multiplexed on a DRB, ADUs on different flows may happen to have the same identifier during transmission. This may cause ambiguity when the RAN network node uses the relationship between ADUs on the same flow in scheduling. For example, the RAN network node may detect the late arrival of an ADU based on the inter-ADU delay.
[0075] In some aspects, the network node may identify the service flow for each ADU and include the service flow identification in the ADU metadata before providing the application data to the RAN network node. In some aspects, the service flow may be identified based on the source IP address and the destination IP address and / or port number of the ADU packet. In some aspects, the service flow identification may be allocated by a network node (e.g., a UPF and / or a service layer entity).
[0076] Figure 5 is a diagram of an example 500 associated with partitioning application data into ADUs according to the present disclosure. Figure 5 As shown in , a network node (e.g., a UPF, a server, and / or a service layer entity) may communicate with an application server and a RAN network node (e.g., a base station 110, a CU, a DU, and / or a RU). The RAN network node, the network node, and / or the application server may communicate with a UE (e.g., UE 120) via a communication link between the UE and the RAN network node. In some aspects, the RAN network node and the network node may be part of the same network domain. In some aspects, the RAN network node and the UE may be part of a wireless network (e.g., wireless network 100). The UE and the network node may be in a Figure 5 The operations shown are performed after a wireless connection has been established.
[0077] As indicated by reference numeral 505, the network node may receive application data from the application server. The application data may include data for joint processing at the UE, such as frames of a video stream and / or an extended reality application. In some aspects, the application data may be indicated for transmission via an additional network node, such as a RAN network node.
[0078] In some aspects, a network node may receive application data with one or more additional indications associated with an ADU and / or partitioning into ADUs. For example, the application data may indicate partitioning of data packets into ADUs, one or more ADU lengths, a number of data packets of application data per ADU, an indication of a data flow associated with the data packets of application data, one or more FEC parameters associated with the ADU, and / or one or more quality metrics associated with the ADU, etc. In some aspects, a first set of the one or more indications may be included in each data packet, a second set of the one or more indications may be included in each ADU, and / or a third set of the one or more indications may be included to indicate a change from a previous ADU, etc.
[0079] As shown by reference numeral 510, the network node may identify the partitioning of the application data into the ADUs. In some aspects, the network node may identify the partitioning of the application data into the ADUs based at least in part on an indication of the partitioning indicated by the application server (e.g., in an indication of the ADU partitioning from the application server). In some aspects, the network node may identify the partitioning independently of the indication of the partitioning from the application server (e.g., in the absence of an indication of the partitioning from the application server). For example, the network node may identify the partitioning based at least in part on deep packet inspection of data packets of the application data, timing of data packets of the application data, and / or ML, etc.
[0080] The network node may identify the partition based at least in part on training and / or using an ML model using inputs and results from previous application data. For example, the ML model may be based at least in part on parameters including one or more of the following: timing of data packets of the application data, periodicity of the data packets, number of data packets of the application data, size of the data packets, and / or characteristic patterns of the data packets, etc.
[0081] In some aspects, the network node may identify metadata associated with the ADU, the metadata including one or more additional indications associated with the ADU. For example, the network node may identify one or more additional indications associated with one or more of the following: one or more ADU lengths, a number of data packets of application data per ADU, an indication of a data flow associated with the data packets of application data, one or more FEC parameters associated with the ADU, and / or one or more quality metrics associated with the ADU, etc. In some aspects, a first set of the one or more additional indications may be included in each data packet, a second set of the one or more additional indications may be included in each ADU, and / or a third set of the one or more additional indications may be included to indicate a change from a previous ADU, etc.
[0082] As indicated by reference numeral 515, the network node may identify one or more data flows of data packets of the application data. In some aspects, the network node may identify the one or more data flows based at least in part on an indication from an application server, a source address of the data packets, a destination address of the data packets, and / or a port number of the data packets, etc. In some aspects, the network node may train and / or use an ML model to identify the one or more data flows based at least in part on a source address of the data packets, a destination address of the data packets, and / or a port number of the data packets, etc.
[0083] As shown by reference numeral 520, the network node may add one or more indications of the partitioning into ADUs and / or one or more additional indications associated with the ADUs. For example, as identified by reference numeral 510, the network node may add one or more indications of the partitioning into ADUs and / or one or more additional indications.
[0084] As indicated by reference numeral 525, the network node may provide the application data with one or more indications of the partition to the RAN network node. In some aspects, the network node may also provide one or more additional indications to the RAN network node. In some aspects, the one or more indications of the partition and / or the one or more additional indications may be carried in a protocol header of the application data or piggybacked with (e.g., attached to) the application data. In some aspects, the network node may provide the application data to the RAN network node indirectly (e.g., via one or more additional nodes, such as a core network node and / or a repeater or router).
[0085] In some aspects, the network node may send application data with one or more indications associated with the ADU. For example, the application data may indicate a division of data packets into ADUs, one or more ADU lengths, a number of data packets of application data per ADU, an indication of a data flow associated with the data packets of application data, one or more FEC parameters associated with the ADU, and / or one or more quality metrics associated with the ADU, etc. In some aspects, a first set of the one or more indications may be included in each data packet, a second set of the one or more indications may be included in each ADU, and / or a third set of the one or more indications may be included to indicate a change from a previous ADU, etc.
[0086] In some aspects, the one or more additional indications provided by the network node may be different from the one or more additional indications provided by the application server to the network node. For example, the one or more additional indications provided by the network node may be modified from one or more additional network nodes received by the network node from the application server. In some aspects, the network node may provide the one or more additional indications independently of receiving the one or more additional indications from the application server (e.g., in the absence of receiving the one or more additional indications from the application server).
[0087] As indicated by reference numeral 530, the RAN network node may schedule the ADUs for transmission to the UE. In some aspects, the RAN network node may schedule the ADUs based at least in part on the partitioning of the application data into the ADUs and / or based at least in part on the one or more additional indications. For example, the RAN network node may schedule the data packets for transmission to the UE based at least in part on the priorities of the data packets associated with the ADUs and based at least in part on one or more KPIs for the ADUs as indicated in the one or more additional indications.
[0088] As indicated by reference numeral 535, the RAN network node may send one or more downlink communications having one or more ADUs to the UE.
[0089] Based at least in part on the network node providing application data with an indication of partitioning of the application data into the ADU, the network (e.g., a RAN network node) may process communications associated with the application data based at least in part on the ADU (e.g., using a KPI or other additional indication associated with the ADU), which may conserve computing resources, power resources, network resources, and / or communication resources that may otherwise have been consumed to avoid failing to meet the KPI associated with the ADU based at least in part on the increased communication error rate. Additionally or alternatively, the network may conserve network resources that may otherwise have been consumed to conservatively attempt to meet the KPI associated with the ADU.
[0090] As indicated above, Figure 5 are provided as examples. Other examples can be found in the Figure 5 Different than described.
[0091] Figure 6 6 is a diagram of an example 600 associated with partitioning application data into ADUs according to the present disclosure. Figure 6As shown in , an application server, UPF, RAN network node (e.g., base station 110, CU, DU and / or RU) and / or UE (e.g., UE 120) can communicate application data. The RAN network node, the network node and / or the application server can communicate with the UE via a communication link between the UE and the RAN network node. In some aspects, the RAN network node and the network node can be part of the same network domain. In some aspects, the RAN network node and the UE can be part of a wireless network (e.g., wireless network 100). The UE and the network node can be in Figure 6 The operations shown are performed after a wireless connection has been established.
[0092] like Figure 6 As shown, application server 605 may include application 610. For example, application server 605 may host application 610 on one or more components of application server 605 (eg, on hardware and / or a combination of hardware and software of application server 605).
[0093] The application 610 may provide application data 615 to the UPF. The application data may include one or more data packets 615A and ADU metadata 615B. In some aspects, the ADU metadata 615B includes a first portion attached to or included in each data packet 615A. The ADU metadata 615B may include a second portion attached to or included in each ADU of the application data 615.
[0094] The UPF 620 may receive the application data 615 at a service layer entity 625 configured to manage ADU partitioning. For example, the service layer entity 625 may be configured to identify the ADU partitioning and / or one or more additional indications associated with the ADU, as indicated herein.
[0095] The UPF 620 provides the application data with metadata 630 to the RAN network node 635. The application data with metadata 630 may include one or more data packets 630A and ADU metadata 630B. In some aspects, the ADU metadata 630B includes a first portion appended to or included in each data packet 630A. The ADU metadata 630B may include a second portion appended to or included in each ADU of the application data with metadata 630. The application data with metadata 630 may include additional, modified, or new metadata when compared to the ADU metadata 615B.
[0096] The RAN network node 635 may receive the application data with the metadata 630. The RAN network node 635 may use the application data with the metadata 630 at an ADU scheduling control unit that identifies data packets associated with different ADUs. The ADU scheduling control unit may determine whether to schedule an ADU (e.g., if the ADU has not expired), a priority of the ADU for scheduling, and / or when to schedule the ADU based at least in part on the ADU metadata 630B.
[0097] The scheduler 645 may receive information associated with scheduling application data for downlink communications with the UE 655 from the ADU scheduling control unit 640. Based at least in part on the information from the ADU scheduling control unit 640, the scheduler may indicate to the UE 655 resources for one or more downlink communications including the application data with the metadata 650.
[0098] The RAN network node 635 may provide the application data with metadata 650 to the UE 655. The application data with metadata 650 may include one or more data packets 650A and ADU metadata 650B. In some aspects, the ADU metadata 650B includes a first portion appended to or included in each data packet 650A. The ADU metadata 650B may include a second portion appended to or included in each ADU of the application data with metadata 650. The application data with metadata 650 may include additional, modified, or new metadata when compared to the ADU metadata 615B and / or the ADU metadata 630B.
[0099] As indicated above, Figure 6 are provided as examples. Other examples can be found in the Figure 6 Different than described.
[0100] Figure 7 700 is a diagram illustrating an example process 700 performed, for example, by a network node according to the present disclosure. Example process 700 is an example in which a network node (e.g., a UPF, a service layer entity, and / or one or more devices or components used by the UPF and / or the service layer entity) performs operations associated with an ADU.
[0101] like Figure 7 As shown, in some aspects, process 700 may include receiving application data for transmission via an additional network node (block 710). For example, a network node (e.g., using Figure 8 The processor 820, memory 830, input component 840 and / or communication component 860 depicted in FIG. 8 may receive application data for transmission via an additional network node, as described above.
[0102] like Figure 7 As further shown in FIG. 7 , in some aspects, process 700 may include providing application data to an additional network node, the application data having one or more indications of partitioning into ADUs added prior to being provided to the additional network node (block 720). Figure 8 The processor 820, memory 830, output component 850 and / or communication component 860 depicted in FIG. 8 may provide application data to an additional network node, the application data having one or more indications of partitioning into ADUs added before being provided to the additional network node, as described above.
[0103] Process 700 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.
[0104] In a first aspect, process 700 includes adding one or more of: one or more indications of partitioning into ADUs, or one or more additional indications associated with the ADUs.
[0105] In a second aspect, either alone or in combination with the first aspect, the application data comprises one or more additional indications associated with the ADU, the one or more additional indications comprising one or more of: one or more ADU lengths, the number of data packets of the application data of each ADU, an indication of a data stream associated with the data packets of the application data, one or more forward error correction parameters associated with the ADU, or one or more quality metrics associated with the ADU.
[0106] In a third aspect, either alone or in combination with one or more of the first and second aspects, process 700 includes identifying a data stream associated with a data packet of application data based at least in part on one or more of the following: a source address of the data packet, a destination address of the data packet, or a port number of the data packet.
[0107] In a fourth aspect, alone or in combination with one or more of the first to third aspects, one or more additional indications are carried in a protocol header of the application data or are piggybacked with the application data.
[0108] In a fifth aspect, either alone or in combination with one or more of aspects 1 to 4, process 700 includes identifying the division as an ADU based at least in part on one or more of: an indication of the ADU division from an application server, deep packet inspection, timing of data packets of application data, or a machine learning model.
[0109] In a sixth aspect, either alone or in combination with one or more of aspects one to five, the machine learning model is based at least in part on parameters comprising one or more of: timing of data packets of application data, periodicity of data packets, number of data packets of application data, size of data packets, or characteristic patterns of data packets.
[0110] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, receiving application data includes: receiving application data with one or more additional indications of division into ADUs.
[0111] In an eighth aspect, providing application data to an additional network node, either alone or in combination with one or more of aspects one to seven, comprises one or more of: adding one or more additional indications associated with the ADU to the application data, or modifying one or more additional indications of the partition to generate one or more indications of the partition.
[0112] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, receiving the application data includes receiving one or more additional indications associated with the ADU.
[0113] In a tenth aspect, either alone or in combination with one or more of aspects one to nine, receiving one or more additional indications associated with the ADU comprises receiving one or more additional indications for each ADU, or receiving one or more additional indications based at least in part on a change in one or more values of the one or more additional indications.
[0114] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the network node comprises one or more of a service layer entity or a user plane function.
[0115] In a twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, the additional network node comprises a radio access network (RAN) network node.
[0116] although Figure 7 An example block diagram of process 700 is shown, but in some aspects, process 700 may include Figure 7 Additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 700. Additionally or alternatively, two or more of the blocks in the process 700 may be performed in parallel.
[0117] Figure 8 is a diagram of example components of an apparatus 800. The apparatus may correspond to a UE, a RAN network node, a network node, and / or an application server (e.g., as described in conjunction with Figure 5In some implementations, the UE, RAN network node, network node, and / or application server include one or more devices 800 and / or one or more components of the device 800. Figure 8 As shown, device 800 may include a bus 810 , a processor 820 , a memory 830 , an input component 840 , an output component 850 , and a communication component 860 .
[0118] The bus 810 includes one or more components that enable wired and / or wireless communication between components of the device 800. The bus 810 may be coupled to the device 800 via an operational coupling, a communicative coupling, an electronic coupling, and / or an electrical coupling. Figure 8 Two or more components of a computer system are coupled together. Processor 820 includes a central processing unit, a graphics processing unit, a microprocessor, a controller, a microcontroller, a digital signal processor, a field programmable gate array, an application specific integrated circuit, and / or another type of processing component. Processor 820 is implemented in hardware, firmware, or a combination of hardware and software. In some specific implementations, processor 820 includes one or more processors that can be programmed to perform one or more operations or processes described elsewhere herein.
[0119] The memory 830 includes volatile memory and / or non-volatile memory. For example, the memory 830 may include random access memory (RAM), read-only memory (ROM), a hard drive, and / or another type of memory (e.g., flash memory, magnetic memory, and / or optical memory). The memory 830 may include internal memory (e.g., RAM, ROM, or hard drive) and / or removable memory (e.g., movable via a universal serial bus connection). The memory 830 may be a non-transitory computer-readable medium. The memory 830 stores information, instructions, and / or software (e.g., one or more software applications) related to the operation of the device 800. In some specific implementations, the memory 830 includes one or more memories such as coupled to one or more processors (e.g., processor 820) via bus 810.
[0120] Input assembly 840 enables device 800 to receive input, such as user input and / or sensed input. For example, input assembly 840 may include a touch screen, keyboard, keypad, mouse, button, microphone, switch, sensor, global positioning system sensor, accelerometer, gyroscope and / or actuator. Output assembly 850 enables device 800 to provide output such as via display, speaker and / or light emitting diode. Communication assembly 860 enables device 800 to communicate with other devices via wired connection and / or wireless connection. For example, communication assembly 860 may include a receiver, a transmitter, a transceiver, a modem, a network interface card and / or an antenna.
[0121] The device 800 may perform one or more operations or processes described herein. For example, a non-transitory computer-readable medium (e.g., memory 830) may store an instruction set (e.g., one or more instructions or codes) for execution by the processor 820. The processor 820 may execute the instruction set to perform one or more operations or processes described herein. In some specific implementations, the execution of the instruction set by one or more processors 820 causes one or more processors 820 and / or the device 800 to perform one or more operations or processes described herein. In some specific implementations, hard-wired circuits may be used instead of instructions or in combination with instructions to perform one or more operations or processes described herein. Additionally or alternatively, the processor 820 may be configured to perform one or more operations or processes described herein. Therefore, the specific implementation described herein is not limited to any particular combination of hardware circuits and software.
[0122] Figure 8 The number and arrangement of components shown are provided as examples. Device 800 may include Figure 8 Those components shown may have additional components, fewer components, different components, or components arranged in a different manner than those shown. Additionally or alternatively, one (e.g., one or more) of the components of device 800 may perform one or more functions described as being performed by another set of components of device 800.
[0123] The following provides an overview of some aspects of the disclosure:
[0124] Aspect 1: A method of wireless communication performed by a network node, the method comprising: receiving application data for transmission via an additional network node; and providing the application data to the additional network node, the application data having one or more indications of division into application data units (ADUs) added before being provided to the additional network node.
[0125] Aspect 2: The method according to aspect 1 further comprises adding one or more of the following: the one or more indications of the division into ADUs, or one or more additional indications associated with the ADUs.
[0126] Aspect 3: A method according to any one of Aspects 1 or 2, wherein the application data includes one or more additional indications associated with the ADU, and the one or more additional indications include one or more of the following: one or more ADU lengths, the number of data packets of the application data of each ADU, an indication of a data stream associated with the data packets of the application data, one or more forward error correction parameters associated with the ADU, or one or more quality metrics associated with the ADU.
[0127] Aspect 4: According to the method described in Aspect 3, the method also includes: identifying the data flow associated with the data packet of the application data based at least in part on one or more of the following items: the source address of the data packet, the destination address of the data packet, or the port number of the data packet.
[0128] Aspect 5: The method according to any one of aspects 3 or 4, wherein the one or more additional indications are carried in a protocol header of the application data or are piggybacked with the application data.
[0129] Aspect 6: According to the method described in any one of Aspects 1 to 5, the method also includes: identifying the division into ADU based at least in part on one or more of the following: an indication of the ADU division from an application server, deep packet inspection, timing of data packets of the application data, or a machine learning model.
[0130] Aspect 7: A method according to Aspect 6, wherein the machine learning model is at least partially based on parameters including one or more of the following: the timing of the data packets of the application data, the periodicity of the data packets, the number of data packets of the application data, the size of the data packets, or a characteristic pattern of the data packets.
[0131] Aspect 8: The method according to any one of aspects 1 to 7, wherein receiving the application data comprises: receiving the application data with one or more additional indications of division into the ADUs.
[0132] Aspect 9: A method according to Aspect 8, wherein providing the application data to the additional network node includes one or more of the following: adding one or more additional indications associated with the ADU to the application data, or modifying the one or more additional indications of the partition to generate the one or more indications of the partition.
[0133] Aspect 10: The method according to any one of aspects 8 or 9, wherein receiving the application data comprises: receiving one or more additional indications associated with the ADU.
[0134] Aspect 11: A method according to Aspect 10, wherein receiving the one or more additional indications associated with the ADU includes: receiving the one or more additional indications for each ADU, or receiving the one or more additional indications based at least in part on a change in one or more values of the one or more additional indications.
[0135] Aspect 12: The method according to any one of aspects 1 to 11, wherein the network node comprises one or more of a service layer entity or a user plane function.
[0136] Aspect 13: The method according to any one of aspects 1 to 12, wherein the additional network node comprises a Radio Access Network (RAN) network node.
[0137] Aspect 14: An apparatus for performing wireless communications at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 1 to 13.
[0138] Aspect 15: A device for wireless communication, the device comprising: a memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more of aspects 1 to 13.
[0139] Aspect 16: An apparatus for wireless communication, the apparatus comprising at least one means for performing the method according to one or more of aspects 1 to 13.
[0140] Aspect 17: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 13.
[0141] Aspect 18: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 1 to 13.
[0142] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of these aspects.
[0143] As used herein, the term "component" is intended to be broadly interpreted as hardware, and / or a combination of hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, "software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, processes and / or functions and other examples. As used herein, "processor" is implemented in hardware and / or a combination of hardware and software. It will be clear that the system or method described herein can be implemented by a combination of hardware and / or hardware and software in different forms. The actual dedicated control hardware or software code for implementing these systems and / or methods does not limit various aspects. Therefore, the operation and behavior of the system and / or method are not described herein with reference to specific software codes, because it will be understood by those skilled in the art that software and hardware can be designed to implement the system and / or method based at least in part on the description herein.
[0144] As used herein, "satisfying a threshold" may mean, depending on the context, that a value is greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc.
[0145] Although specific combinations of features are set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features can be combined in a manner that is not specifically listed in the claims and / or is not disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, the phrase "at least one of" the list of items refers to any combination of these items (which includes a single member). As an example, "at least one of a, b or c" is intended to cover a, b, c, a+b, a+c, b+c and a+b+c, and any combination with multiple identical elements (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c and c+c+c, or any other ordering of a, b and c).
[0146] Any element, action or instruction used herein should not be interpreted as key or necessary unless clearly stated. In addition, as used herein, the article "one" is intended to include one or more items and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more items connected to the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items and can be used interchangeably with "one or more". If you only want to refer to an entry, the phrase "only one" or similar terms will be used. Moreover, as used herein, the term "having" etc. is intended to be an open term, which does not limit the elements they modify (for example, "having" A elements can also have B). In addition, the phrase "based on" is intended to mean "at least partially based on", unless explicitly stated otherwise. In addition, as used herein, the term "or" is intended to be open when used in a series, and can be used interchangeably with "and / or", unless otherwise explicitly stated (for example, if used in combination with "either" or "only one").
Claims
1. A method of wireless communication performed by a network node, the method comprising: receiving application data for transmission via the additional network node; as well as The application data is provided to the additional network node with one or more indications of division into application data units (ADUs) added prior to being provided to the additional network node.
2. The method according to claim 1, further comprising adding one or more of the following: said one or more indications of said division into ADUs, or One or more additional indications associated with the ADU.
3. The method of claim 1 , wherein the application data comprises one or more additional indications associated with the ADU, the one or more additional indications comprising one or more of the following: One or more ADU lengths, The number of data packets of the application data per ADU, an indication of a data flow associated with said data packets of said application data, one or more forward error correction parameters associated with the ADU, or One or more quality metrics associated with the ADU.
4. The method according to claim 3, further comprising: identifying the data flow associated with the data packet of the application data based at least in part on one or more of: the source address of the data packet, the destination address of the data packet, or The port number of the data packet.
5. The method of claim 3, wherein the one or more additional indications are carried in a protocol header of the application data or are piggybacked with the application data.
6. The method according to claim 1, further comprising: The division into ADUs is identified based at least in part on one or more of: an indication from an application server of the partitioning of the ADU, Deep Packet Inspection, the timing of data packets of the application data, or Machine learning models.
7. The method of claim 6, wherein the machine learning model is based at least in part on parameters comprising one or more of: said timing of said data packets of said application data, the periodicity of the data packets, the number of data packets of the application data, the size of the data packet, or A characteristic pattern of the data packets.
8. The method of claim 1 , wherein receiving the application data comprises: The application data is received with one or more additional indications of partitioning into the ADUs.
9. The method of claim 8, wherein providing the application data to the additional network node comprises one or more of: adding one or more additional indications associated with the ADU to the application data, or The one or more additional indications of a partition are modified to generate the one or more indications of a partition.
10. The method of claim 8, wherein receiving the application data comprises: One or more additional indications associated with the ADU are received.
11. The method of claim 10, wherein receiving the one or more additional indications associated with the ADU comprises: receiving the one or more additional indications for each ADU, or The one or more additional indications are received based at least in part on a change in one or more values of the one or more additional indications.
12. The method of claim 1, wherein the network node comprises one or more of the following: A service layer entity, or User plane function.
13. The method of claim 1, wherein the additional network node comprises a Radio Access Network (RAN) network node.
14. A network node for wireless communication, the network node comprising: Memory; and one or more processors coupled to the memory and configured to: receiving application data for transmission via the additional network node; as well as The application data is provided to the additional network node with one or more indications of division into application data units (ADUs) added prior to being provided to the additional network node.
15. The network node of claim 14, wherein the one or more processors are further configured to add one or more of the following: said one or more indications of said division into ADUs, or One or more additional indications associated with the ADU.
16. The network node of claim 14, wherein the application data comprises one or more additional indications associated with the ADU, the one or more additional indications comprising one or more of the following: One or more ADU lengths, The number of data packets of the application data per ADU, an indication of a data flow associated with said data packets of said application data, one or more forward error correction parameters associated with said ADU, or One or more quality metrics associated with the ADU.
17. The network node of claim 16, wherein the one or more processors are further configured to: identify the data flow associated with the data packets of the application data based at least in part on one or more of: the source address of the data packet, the destination address of the data packet, or The port number of the data packet.
18. The network node of claim 16, wherein the one or more additional indications are carried in a protocol header of the application data or are piggybacked with the application data.
19. The network node of claim 14, wherein the one or more processors are further configured to identify the partitioning into ADUs based at least in part on one or more of: an indication from an application server of the partitioning of the ADU, Deep Packet Inspection, the timing of data packets of the application data, or Machine learning models.
20. The network node of claim 19, wherein the machine learning model is based at least in part on parameters including one or more of: said timing of said data packets of said application data, the periodicity of the data packets, the number of data packets of the application data, the size of the data packet, or A characteristic pattern of the data packets.
21. The network node of claim 14, wherein to receive the application data, the one or more processors are configured to: receive the application data with one or more additional indications of partitioning into the ADUs.
22. The network node of claim 21, wherein to provide the application data to the additional network node, the one or more processors are configured to: adding one or more additional indications associated with the ADU to the application data, or The one or more additional indications of a partition are modified to generate the one or more indications of a partition.
23. The network node of claim 21, wherein the one or more processors are configured to: One or more additional indications associated with the ADU are received.
24. The network node of claim 23, wherein to receive the one or more additional indications associated with the ADU, the one or more processors are configured to: receiving the one or more additional indications for each ADU, or The one or more additional indications are received based at least in part on a change in one or more values of the one or more additional indications.
25. The network node of claim 14, wherein the network node comprises one or more of the following: A service layer entity, or User plane function.
26. The network node of claim 14, wherein the additional network node comprises a Radio Access Network (RAN) network node.
Citation Information
Patent Citations
Application data units
US20230308529A1
