SYSTEM AND METHOD TO CONFIGURE O-RAN FRONTHAUL TO SUPPORT 2ND-GENERATION (2G), 3RD-GENERATION (3G) AND NB-IOT

Abstract

There is provided, an open radio access network distributed unit (O-DU) having an electronic module that performs an FS-8 Radio Access Technology (RAT) functionality.

Claims

1. An open radio access network distributed unit (O-DU) comprising an electronic module that configured with structures to execute parameters to perform FS-8 Radio Access Technology (RAT), the parameters comprising: FS-8 frame structure parameters; Narrow Band-Internet of Things (NB-IOT) parameters; and automatic gain control (AGC) parameters.

2. The O-DU of claim 1 being further configured to send AGC parameters for a random access channel (RACH) AGC configuration to a 2G network radio unit (O-RU), the AGC parameters comprising: a Frame number where the RACH is expected; a Slot Number or Slot Numbers on the corresponding Frame number; and a Target dynamic Gain Range of the AGC.

3. The O-DU of claim 2, wherein the 2G radio unit can determine one or more of the AGC parameters based on the AGC parameter values.

4. The O-DU of claim 3, wherein the 2G O-RU is configured to determine where the RACH is expected on a frame and apply gain control based on the AGC parameter values.

5. The O-DU of claim 1, wherein the FS-8 frame structures comprise a maximum symbol size per millisecond capability for the O-RU.

6. The O-DU of claim 5, wherein the FS-8 frame structure further comprises extended symbol length parameter, a normal symbol length parameter, a sampling rate parameter, or a combination thereof.

7. The O-DU of claim 6, wherein the FS-8 frame structure further comprises an AGC-2G parameter, a 2G/3G RU frame format parameter, or both.

8. The O-DU of claim 6, wherein a sampling rate SR.sub.bandwidth (in Msps) for occupied bandwidth is used to determine a symbol length N.sub.symb and a cyclic prefix length CP.sub.bandwidth of fronthaul symbols.

9. The O-DU of claim 8, where the FH symbols are expressed as:
N.sub.symb=T.sub.symb×SR.sub.bandwidth
CP.sub.bandwidth=(T.sub.symb−66.66*e.sup.6)×SR.sub.bandwidth where T.sub.symb is in seconds.

10. The O-DU of claim 1, the AGC parameters comprising a parameter structure configured for the O-DU to inform an O-RU of AGC parameters other than RACH slots, the parameters comprising: a target dynamic range of the AGC, and AGC parameter sets.

11. The O-DU of claim 10, the AGC parameter sets comprising: an AGC integral gain parameter, an AGC proportional gain parameter, and a derivative gain parameter.

12. The O-DU of claim 1, wherein the O-DU is configured to support a 2G and 3G NB-IOT.

13. The O-DU of claim 12, wherein the O-DU is configured with a supported technology parameter configured for supporting GSM, UMTS and an NB-IOT, the supported technology parameter comprising a downlink parameter set, and uplink parameter set, or both.

14. The O-DU of claim 12, wherein the O-DU is configured to support 2G and 3G NB-IOT in a U-plane configuration, wherein the O-DU is configured with carrier parameters.

15. The O-DU of claim 14, wherein the carrier parameters comprise: tx-array carrier parameters, rx array carrier parameters, or both.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0030] FIG. 1 is a block diagram of a system of a single RAT radio access solution where an O-DU communicates with an O-RU over an O-RAN FH in an O-RAN.

[0031] FIG. 2 shows a 4G LTE subframe and slot structure.

[0032] FIG. 3 shows a 4G LTE subframe and slot structure.

DESCRIPTION OF THE DISCLOSURE

[0033] The system disclosed herein will allow FS-8 RATs (2G and 3G) to interface to O-RAN FH, and in general, any packet-based FH transport network standard. Reference is made to Third Generation Partnership Project (3GPP), the O-RAN Alliance, and the Internet Engineering Task Force (IETF) in accordance with embodiments of the present disclosure

[0034] FIG. 1 is a block diagram of a system 100 of a single RAT radio access solution where an O-DU 105 communicates with an O-RU 115 over an O-RAN FH 110 in an O-RAN 120. System 100 includes a 2G RAT 125 and a 3G RAT 130, which, in practice, are connected directly to O-DU 105.

[0035] System 100 can be configured for single carrier or multi-carrier systems. For example, for multi-carrier systems, the system can be configured to map the 2G signal to the any LTE bandwidth equivalent analog stream such as 5/10/15/20 MHz. Thus, system 100 allows an available 2G spectrum to be split across different antennas in multiples of LTE-equivalent bandwidths by using different RF frequencies for each of the antenna.

[0036] Implementations as described in this section with respect to a RAT system diagram in FIG. 1 where, O-RU system implement the C&M server 117. O-RU declares its capability and works with the C&M client 107 located in O-DU 105. M-Plane standard based message/information exchange 112 are carried out between O-RU and O-DU (between C&M server 117 and C&M client 105) over the FH 110 to handshake required non-real time system configuration and management for desired system operation.

[0037] Each of O-DU 105 and O-RU 115 includes electronic circuitry that performs operations to execute methods or processes described herein. The circuitry may be implemented with any or all of (a) discrete electronic components, (b) firmware, or (c) a programmable circuit that includes a processor and a memory. Such a processor is an electronic device configured of logic circuitry that responds to and executes instructions. Such a memory is a tangible, non-transitory, computer-readable storage device encoded with a computer program. In this regard, the memory stores data and instructions, i.e., program code, that are readable and executable by the processor for controlling operations of the processor. The memory may be implemented in a random-access memory (RAM), a hard drive, a read only memory (ROM), or a combination thereof.

[0038] Additionally, the program code may be configured on a storage device for subsequent loading into the memory. Such a storage device is a tangible, non-transitory, computer-readable storage device, and examples include (a) a compact disk, (b) a magnetic tape, (c) a read only memory, (d) an optical storage medium, (e) a hard drive, (f) a memory unit consisting of multiple parallel hard drives, (g) a universal serial bus (USB) flash drive, (h) a random-access memory, and (i) an electronic storage device coupled the components of system 100 via a network, e.g., the Internet.

[0039] The program code may be configured in one or more modules. The term “module” is used herein to denote a functional operation that may be embodied either as a stand-alone component or as an integrated configuration of a plurality of subordinate components. Thus, a module may be implemented as a single module or as a plurality of sub-ordinate modules that operate in cooperation with one another.

[0040] In an implementation, described is an O-RAN M-Plane Data-Structure Enhancement for 2G, 3G, NB-IoT RAT:

[0041] In an implementation, described is a YANG parameter structure for a DU to inform an RU of AGC parameters for a RACH Slot. AGC is a conditional feature, which can be implemented as a function of whether the O-RU supports 2G or not. The parameter is applicable for single carrier 2G or synchronized multi carrier 2G systems.

[0042] In an implementation, a 2G O-DU 107 sends following parameters to 2G O-RU for RACH AGC configuration:

[0043] a Frame number where a RACH is expected;

[0044] a Slot Number(s) on the corresponding Frame number;

[0045] a Target dynamic Gain Range of the AGC; and

[0046] AGC parameter sets (e.g.: agc-rach-nframe, agc-rach-slot, agc-rach-proportional-gain, agc-rach-integral-gain and agc-rach-differential-gainfactors). An implementation of an exemplary 2G PARCH AGC optional parameter structure includes: [0047] +—rw agc-configuration—rach {AGC-2G] [0048] +—agc-rach-nframe? unit 8 [0049] +—agc-rach-rach-slot? unit 8 [0050] +—agc-rach-proportional-gain? decimal64 [0051] +—agc-rach-integral-gain? decimal64 [0052] +—agc-rach-differential-gain? decimal64 [0053] +—rw agc-configuration—tch {AGC-2G] [0054] +—agc-tch-gain-range? decimal64 [0055] +—agc-tch-integral-gain? decimal64 [0056] +—agc-tch-differential-gain? decimal64 [0057] +—agc-tch-proportional-gain? decimal64 [0058] =

[0059] The 2G PARCH AGC optional parameter structure can be implemented under the O-RAR U-Plane configuration for rx array carriers (o-ran-uplane-conf.yang->rx-array-carriers).

[0060] Based on the parameter values, a 2G RU can be configured to determine the slots where the RACH is expected on each frame and can thus apply gain control.

[0061] In an implementation, described is a subframe and slot structure supporting multiple symbols in a frame. Over the FH multicarrier 2G and 3G radio access technology, IQ data flows can have following two alternative frame structures.

[0062] Option 1: Maintain 4G LTE subframe and slot structures and the corresponding 14 symbols per subframe as shown in the FIG. 2. Differences with 4G are total number of IQ data sample content per symbol is equal to the full size of the corresponding LTE symbol size for the corresponding bandwidth of operation. For example, for slot #0 or #7, a Symbol Size is the number of IQ samples Tsymb=71.9 μs at a sample rate corresponding to the system bandwidth e.g., Symbol Size=1104 Samples for a 10 MHz bandwidth multicarrier 2G/3G System. For slot #1, a Symbol Size is the number of IQ samples Tsymb=71.3 μs at a sample rate corresponding to the system bandwidth e.g., Symbol Size=1096 Samples for a 10 MHz bandwidth multicarrier 2G/3G System

[0063] Option 2: Maintain 4G LTE Subframe and slot structure and the corresponding 15 symbols per subframe as shown in FIG. 3. The difference for a 4G system is the number of IQ data sample content per symbol is equal to the full size of the corresponding LTE symbol size for the corresponding bandwidth of operation. For example, all slots have a Symbol Size that is the number of IQ samples Tsymb=66.67 us at a sample rate corresponding to the system bandwidth e.g., Symbol Size=1024 Samples for a 10 MHz bandwidth multicarrier 2G/3G System.

[0064] To support the above symbols in one millisecond, the O-RU can be configured to indicate the capability in YANG model under RU capability (e.g.: max-symbols-per-ms).

[0065] In an implementation, described is a FH sampling rate and symbol length structure and process. The O-DU can be configured to indicate the fronthaul sampling rate to O-RU. The sampling rate SR.sub.bandwidth (in Msps,) which is a function of occupied bandwidth, can be configured to determine the symbol length N.sub.symb and cyclic prefix length CP.sub.bandwidth of the fronthaul symbols. They could be expressed as following:

N.sub.symb=T.sub.symb×SR.sub.bandwidth

CP.sub.bandwidth=(T.sub.symb−66.66*e.sup.6)×SR.sub.bandwidth

Where T.sub.symb is in unit seconds.

[0066] An example of an implementation of FS-8 frame format parameters is shown below. Three additional parameters, “extended-symbol-length”, “normal-symbol-length” and “sampling-rate”, can be added under an O-RAN U-Plane configuration (o-ran-uplane-conf.yang), for example as follows:

[0067] +—rw fs8-frame-structure {FS8-Frame-Format}? [0068] +—rw max-symbols-per-ms [0069] +—rw extended-symbol-length [0070] +—rw normal-symbol-length [0071] +—rw sampling-rate
These parameters can be pushed from O-DU to O-RU via the M-plane as part of user plane configuration for 2G RUs 125 or 3G RUs 130. Optional features as shown in Table 1 can also be added.

TABLE-US-00001 TABLE 1 No Optional Feature Namespace Feature name 1 AGC for 2G RUs “urn:o-ran:uplane- AGC-2G conf:x.y” 2 Frame Format for “urn:o-ran:uplane- FS8-FRAME-FORMAT 2G/3G RUs conf:x.y”

[0072] In an implementation, described is a Yang parameter structure for an O-DU to inform an O-RU of AGC parameters for slots other than RACH slots. A 2G O-DU sends following parameters to 2G O-RU for AGC configuration for TCH and other slots: a Target dynamic Gain Range of the AGC and the AGC parameter sets {agc-tch-integral-gain, agc-tch-differential-gain, and agc-tch-proportional-gain} (proportional, integral and derivative parameters).

[0073] The 2G TCH slots (except RACH) AGC parameter structures are implemented under and an O-RAN U-Plane configuration for rx array carriers (o-ran-uplane-conf.yang->rx-array-carriers). Based on the above-referenced values, the 2G Radio unit can apply gain control for slots other than RACH slots.

[0074] In an implementation, a module is configured for a YANG model to support 2G, 3G and NB-IoT. The O-RU can be configured to report as a part of its capabilities whether it supports 2G, 3G, or NB-IOT. For example, an enhanced definition is added to the following two parameters in YANG model under RU capability:

TABLE-US-00002 .circle-solid. supportedtechnology-dl     ◯ enum range of type enhanced to support GSM, UMTS,     NBIoT  leaf-list supported-technology-dl {   type enumeration{    enum LTE {     description “LTE is supported in DL path.”;    }    enum NR {     description “NR is supported in DL path.”;    }    enum DSS_LTE_NR {     if-feature DSS_LTE_NR;     description      “DSS is supported in the DL, which implicitly means LTE      and NR are also BOTH supported in the DL.”;    }    enum GSM {     description “GSM is supported in DL path.”;    }    enum UMTS {     description “UMTS is supported in DL path.”;    }    enum NBIOT {     description “NBIOT StandAlone mode supported by RU”;    }    enum NBIOT-LTE {     description “NBIOT inband/guard band mode over LTE carrier supported by RU”;    }    enum NBIOT-NR {     description “NBIOT inband/guard band mode over NR carrier supported by RU”;    }   } .circle-solid. supportedtechnology-ul     ◯ enum range of type enhanced to support GSM, UMTS,     NBIoT  leaf-list supported-technology-ul {   type enumeration{    enum LTE {     description “LTE is supported in UL path.”;    }    enum NR {     description “NR is supported in UL path.”;    }    enum DSS_LTE_NR {     if-feature DSS_LTE_NR;     description      “DSS is supported in the UL, which implicitly means LTE      and NR are also BOTH supported in the UL.”;    }    enum GSM {     description “GSM is supported in UL path.”;    }    enum UMTS {     description “UMTS is supported in UL path.”;    }    enum NBIOT {     description “NBIOT StandAlone mode supported by RU”;    }    enum NBIOT-LTE {     description “NBIOT inband/guard band mode over LTE carrier supported by RU”;    }    enum NBIOT-NR {     description “NBIOT inband/guard band mode over NR carrier supported by RU”;    }   }

[0075] In an implementation, to support 2nd-Generation (2G), 3rd-Generation (3G) and NB-IoT in U-plane configurations, enum values for the parameter “type” are added under tx-array-carriers and rx-array-carriers present in the O-RAN U-Plane configuration (o-ran-uplane-conf.yang).

[0076] The present disclosure employs abbreviations, terms and technology defined in accord with Third Generation Partnership Project (3GPP) and/or Internet Engineering Task Force (IETF) technology standards and papers, including the following standards and definitions. 3GPP and IETF technical specifications (TS), standards (including proposed standards, technical reports (TR) and other papers are incorporated by reference in their entirety hereby, define the related terms and architecture reference models that follow.

Acronyms

[0077] 3GPP: 3rd Generation Partnership Project

[0078] AGC: Automatic gain control

[0079] BS: Base Station

[0080] C&M: Control and Management

[0081] CAPEX: Capital expenditures

[0082] CCH: Control channel

[0083] CPRI: Common Public Radio Interface

[0084] CUS-plane: Control, user, and synchronization plane

[0085] DL: Downlink

[0086] eCPRI: Enhanced Common Public Radio Interface

[0087] eNB: eNodeB (4G LTE base station)

[0088] FEC: Forward error correction

[0089] FH: Fronthaul

[0090] FS: Functional split

[0091] gNB: gNodeB (5G NR base station)

[0092] GPS: Global positioning system

[0093] HW: Hardware

[0094] M-plane: Management plane

[0095] NBIoT: Narrow Band Internet of Things

[0096] O-CU: O-RAN compliant Centralized Unit

[0097] O-DU: O-RAN compliant Distributed Unit

[0098] O-RU: O-RAN compliant Radio Unit

[0099] OPEX: Operating expenses

[0100] PRACH: Physical random access channel

[0101] PRB: Physical resource block

[0102] PTP: Precision time protocol

[0103] RACH: Random access channel

[0104] RAT: Radio access technology

[0105] RE: Resource element

[0106] RoE: Radio over Ethernet

[0107] SMO: Service Management and Orchestration

[0108] SW: Software

[0109] SyncE: Synchronous Ethernet

[0110] TCH: Traffic channel

[0111] UL: Uplink

Definitions

[0112] Channel: the contiguous frequency range between lower and upper frequency limits.

[0113] DL: DownLink: data flow towards the radiating antenna (generally on the LLS interface)

[0114] LLS: Lower Layer Split: logical interface between O-DU and O-RU when using a lower layer (intra-PHY based) functional split.

[0115] M-Plane: Management Plane: refers to non-real-time management operations between the O-DU and the O-RU.

[0116] Node-B: 3GGP defined access function for 3G RAT.

[0117] O-CU: O-RAN Control Unit—a logical node hosting PDCP, RRC, SDAP and other control functions

[0118] O-DU: O-RAN Distributed Unit: a logical node hosting RLC/MAC/High-PHY layers based on a lower layer functional split.

[0119] O-RU: O-RAN Radio Unit: a logical node hosting Low-PHY layer and RF processing based on a lower layer functional split. This is similar to 3GPP's “TRP” or “RRH” but more specific in including the Low-PHY layer (FFT/iFFT, PRACH extraction).

[0120] OTA: Over the Air

[0121] S-Plane: Synchronization Plane: refers to traffic between the O-RU or O-DU to a synchronization controller which is generally an IEEE 1588 Grand Master (however, Grand Master functionality may be embedded in the O-DU).

[0122] U-Plane: User Plane: refers to IQ sample data transferred between O-DU and O-RU

[0123] UL: UpLink: data flow away from the radiating antenna (generally on the LLS interface).

TABLE-US-00003 tx-array-carriers -- type     ◯ type enhanced to support GSM, UMTS, NBIoT    leaf type {     type enumeration {      enum NR {       description       “5G technology”;      }      enum LTE {       description       “LTE technology”;      }      enum DSS_LTE_NR {       if-feature mcap:DSS_LTE_NR;        description         “NR and LTE technologies in Dynamic Spectrum          Sharing mode”;      }      enum GSM {       description “GSM technology.”;      }      enum UMTS {       description “UMTS technology.”;      }      enum NBIOT {       description “NBIOT StandAlone mode       supported by RU”;      }      enum NBIOT-LTE {       description “NBIOT inband/guard band mode over      LTE carrier supported by RU”;      }      enum NBIOT-NR {       description “NBIOT inband/guard band mode over NR      carrier supported by RU”;      }     }     description      “Type of carrier. Indicates array-carrier      technology.”;  } rx-array-carriers    -- type     ◯ type enhanced to support GSM, UMTS, NBIoT    leaf type {     type enumeration {      enum NR {       description       “5G technology”;      }      enum LTE {       description        “LTE technology”;      }      enum DSS_LTE_NR {       if-feature mcap:DSS_LTE_NR;        description         “NR and LTE technologies in Dynamic Spectrum          Sharing mode”;      }      enum GSM {       description “GSM technology.”;      }      enum UMTS {       description “UMTS technology.”;      }      enum NBIOT {       description “NBIOT StandAlone mode supported by RU”;      }      enum NBIOT-LTE {       description “NBIOT inband/guard band mode over LTE     carrier supported by RU”;      }      enum NBIOT-NR {       description “NBIOT inband/guard band mode over NR      carrier supported by RU”;      }     }     description      “Type of carrier. Indicates array-carrier technology.; In an implementation, these additional value options are added to existing values of LTE, NR or DSS-LTE-N.

[0124] The techniques described herein are exemplary, and should not be construed as implying any particular limitation on the present disclosure. Various alternatives, combinations and modifications could be devised by those skilled in the art. For example, operations associated with the processes described herein can be performed in any order, unless otherwise specified or dictated by the operations themselves. The present disclosure is intended to embrace all such alternatives, modifications and variances that fall within the scope of the appended claims.

[0125] The term “comprises” or “comprising” are to be interpreted as specifying the presence of the stated features, integers, operations or components, but not precluding the presence of one or more other features, integers, operations or components or groups thereof. The terms “a” and “an” are indefinite articles, and as such, do not preclude embodiments having pluralities of articles.