JP7043506B2 - Multi-technology aggregation architecture for long-term evolution communication systems - Google Patents

Description

Cross-reference to related applications.
This application was filed on February 6, 2017 and has priority under US Patent Application No. 62/455327 to Lee entitled "Multi-Technology Aggregation Architecture for Long Term Evolution Communication Systems". The disclosure of the provisional application is incorporated herein by reference in its entirety.

In some embodiments, the current subject matter is about remote communication systems, and more specifically about multi-technology aggregation architectures for long-term evolution communication systems. Here, the radio communication system may include a long term evolution system and a new 5G radio (“NR”) communication system.

In today's world, cellular networks provide individuals and businesses with on-demand communication capabilities. Typically, a cellular network is a wireless network that can be distributed throughout a terrestrial area called a cell. Each such cell is serviced by at least one fixed point transceiver called a cell site or base station. Each cell can use a different set of frequencies from neighboring cells to avoid interference with each other within each cell and provide improved service. When multiple cells are connected to each other, they provide wireless reach over a large geographic area, with multiple mobile phones and / or other wireless devices or portable transceivers anywhere in the network. Allows you to communicate and communicate with fixed transceivers and telephones. Such communication is done over the base station and is achieved even if the mobile transceiver travels through multiple cells during transmission. The main wireless communication providers have deployed such cell sites worldwide, and therefore this communication requires multiple telephones and multiple mobile computing devices to be connected to the public switched telephone network and the public Internet. Is possible.

The mobile phone may receive and / or create a telephone and / or data call via a cell site or transmission tower by using a radio wave that transmits a signal to the mobile phone and a signal from the mobile phone. A possible, portable phone. From the perspective of a large number of mobile phone users, current mobile phone networks provide limited and shared resources. In that regard, multiple cell sites and handsets change frequencies and use low power transmitters to allow multiple callers to use the network simultaneously with less interference. The reach by the cell site may depend on the number of users who may use a particular geographic location and / or network. For example, in a city, cell sites have a range of up to about half a mile, while in rural areas the range can be as high as 5 miles. In some areas, users may also receive signals from cell sites 25 miles away.

The following are some examples of digital cellular technologies currently in use by telecommunications providers. That is, for Global System for Mobile Communication ("GSM") (Registered Trademark), General Packet Radio System ("GPRS"), cdmaOne, CDMA2000, Evolution-Data Optimization ("EV-DO"), GSM Evolution. Enhanced Data Rate (“EDGE”), Universal Mobile Communication System (“UMTS”), Digital Enhanced Cordless Remote Communication (“DECT”), Digital AMPS (“IS-136 / CDMA”), and Integrated Digital Expansion Network. ("IDEN") and the like. Long Term Evolution, or 4G LTE, is a standard for high-speed wireless data communication for mobile phones and data terminals. The 5G LTE standard is currently under development. LTE is based on GSM / EDGE and UMTS / HSPA digital cellular technologies, allowing for increased capacity and speed by using different wireless interfaces along with improvements to the core network.

Portable devices include, for example, voice data (eg phone calls), emails, text messages, internet browsing, video data (eg video, video calls, augmented reality / virtual reality, etc.), audio data (eg song streaming), etc. It is used to receive and transmit various types of data. Different types of data may require different transmit bandwidth. For example, reproducing high quality video on a high quality mobile device may require higher bandwidth compared to sending an email or text message to the mobile device.

In some embodiments, the current subject matter relates to a method of computer implementation. The method is a step of transmitting the first downlink data to the user equipment using the first downlink frequency and receiving the first uplink data from the user equipment using the first uplink frequency. A step, a step of transmitting the second downlink data to the user equipment using the second downlink frequency, and a step of receiving the second uplink data using the first uplink frequency. include.

In some embodiments, the current subject matter may include one or more of the following optional features. The first downlink data may be transmitted using the first base station of the wireless communication system, and the first uplink data may be received using the first base station. Similarly, the second downlink data may be transmitted from the second base station of the wireless communication system, and the second uplink data may be transmitted from the second base station to the first base station.

In some embodiments, the first and second base stations may include at least one of an eNodeB base station, a gNodeB base station, and any combination thereof. At least one of the first base station and the second base station may include at least one of a radio transmitter, a radio receiver, and any combination thereof. The first and second base stations may operate in at least one of a long-term evolution communication system and a new wireless communication system.

In some embodiments, at least one of the first and second base stations provides at least one of the first and second base stations with at least packet data convergence protocol control information. It may be communicably coupled with at least one centralized unit configured to do so. At least one of the first and second uplink data may include user control information.

In some embodiments, the method uses a centralized unit to generate a packet data convergence protocol packet data unit based on the information provided by at least one of the first and second base stations. It may include a step and a step of transmitting the generated packet data unit to at least one of the first and second base stations. Further, the method may include a step of independently generating scheduling information by the first and second base stations, and a step of sharing the generated scheduling information between the first and second base stations.

A non-temporary computer program product (ie, physical) that stores instructions that, when executed by one or more data processors in one or more computing systems, cause the one or more data processors to perform the operations described herein. Computer program products implemented in the same way) are also explained. Similarly, a computer system including one or more data processors and memory coupled to the one or more data processors is also described. The memory may temporarily or permanently store instructions that cause at least one processor to perform one or more of the operations described herein. In addition, the method may be implemented by one or more data processors distributed within a single computational system or within two or more computational systems. Such a computing system
Through one or more connections including, but not limited to, connections on networks (eg, the Internet, wireless wide area networks, local area networks, wide area networks, wired networks, etc.), or (2) of multiple computing systems. Connected through a direct connection between one or more of, data and / or commands or other commands can be exchanged.

Details of one or more variations of the subject matter described herein are described in the accompanying drawings and in the description below. Other features and advantages of the subject matter described herein will be apparent from the description and drawings, as well as from the claims.

The accompanying drawings, which are incorporated and in part thereof, together with description, show a particular aspect of the subject matter disclosed herein and are some of the concepts associated with the disclosed embodiments. Assist the explanation.

The figure which shows the example of the conventional long term evolution (“LTE”) communication system. A diagram showing further details of the example LTE system shown in FIG. 1a. The figure which shows the addition detail of the advanced packet core of the example of the LTE system shown in FIG. 1a. The figure which shows the example of the evolved NodeB of the example of the LTE system shown in FIG. 1a. Diagrams showing further details of the evolved NodeB shown in FIGS. 1a-1d. Diagram showing an example of an intelligent long-term evolution radio access network for some embodiments of the current subject. Diagram showing an example of an intelligent long-term evolution radio access network that implements carrier aggregation features according to some embodiments of the current subject. A diagram showing an example of a communication system capable of implementing 5G technology and providing users with the use of higher frequency bands. Diagram showing an existing long-term evolution communication network The figure which shows the example of the long term evolution communication network which concerns on some embodiments of the present subject. Diagram showing an example of a multi-technology aggregation system according to some embodiments of the current subject. Diagram showing an example of a communication system according to some embodiments of the current subject. Diagram showing an example of a communication system according to some embodiments of the current subject. The figure which shows the example of the communication system which can carry out the centralized high baseband unit (“BBU”) structure. Diagram showing an example of LTE-NR internetworking architecture The figure which shows the example of the architecture which can implement the Xx interface between LTEeNodeB and NR gNodeB. Diagram showing an example of a multi-technology aggregation centralized virtual RAN architecture for some embodiments of the current subject. Diagram illustrating examples of processes that can be performed by the system shown in FIG. 14a, according to some embodiments of the current subject. Diagram showing an example of a multi-technology aggregation flow control architecture for some embodiments of the current subject. A diagram illustrating an example of a flow control algorithm that can be performed by the architecture shown in FIG. 15 for some embodiments of the current subject. A diagram illustrating an example of a flow control algorithm that can be performed by the architecture shown in FIG. 15 for some embodiments of the current subject. Diagram showing an example of a multi-technology aggregation load balancing process for some embodiments of the current subject. Diagram showing an example of a system according to some embodiments of the current subject. Diagram showing examples of methods according to some embodiments of the current subject

Current themes can provide feasible systems and methods in multi-technology aggregation wireless communication systems. Such systems may include long-term evolution radio communication systems and / or new radio communication systems. One or more aspects of the current subject matter may be incorporated into the transmitter and / or receiver components of a base station in such a communication system. An example of a long term evolution communication system is described below.

I. Long term evolution communication system.
FIGS. 1a-1c and 2 are diagrams showing an example of a conventional long-term evolution (“LTE”) communication system 100, together with its various components. LTE systems or 4G LTE, as is commercially known, are controlled by standards for high speed data wireless communication for mobile phones and data terminals. This standard provides GSM / EDGE ("Global System for Mobile Communications" / "Enhanced Data Rate for GSM Evolution" in addition to UMTS / HSPA ("Universal Mobile Remote Communication System" / "High Speed Packet Access") network technology. ")based on. This standard was developed by 3GPP ("3rd Generation Partnership Project").

As shown in FIG. 1A, the system 100 may include an evolved universal terrestrial radio access network 102 (“EUTRAN”), an evolved packet core 108 (“EPC”), and a packet data network 101 (“PDN”). EUTRAN 102 and EPC 108 provide communication between user equipment 104 and PDN 101. The EUTRAN 102 is a plurality of "evolved NodeBs" ("eNodeB", "ENODEB", "enodeb" or "eNB") or bases that provide communication functions to a plurality of user devices 104a-104c (as shown in FIG. 1b). It may include stations 106a-106c. The user device 104 can be a mobile phone, a smartphone, a tablet, a personal computer, a mobile information terminal (“PDA”), a server, a data terminal, and / or any kind of user device, and / or any combination thereof. .. The user device 104 can be connected to the EPC 108 and then to the PDN 101 via any eNoteB106. Typically, the user equipment 104 may connect to the closest eNote B106 in terms of distance. In the LTE system 100, EUTRAN 102 and EPC 108 work together to provide connectivity, mobility and services to user equipment 104.

FIG. 1b is a diagram showing further details of the network 100 of FIG. 1a. As mentioned above, EUTRAN 102 includes a plurality of eNodeB 106, also known as cell sites. The eNodeB 106 provides radio functions and performs key control functions, including airlink resource scheduling or radio resource management, active mode mobility or handover, and service admission control. The eNodeB 106 is in charge of selecting a mobility management entity (such as MME shown in FIG. 1c) that provides services to the user equipment 104, and protocol functions such as header compression and encryption. The eNodeB 106s constituting the EUTRAN 102 cooperate with each other for radio resource management and handover.

Communication between the user equipment 104 and the eNodeB 106 occurs via the air interface 122 (also known as the "LTE-Uu" interface). As shown in FIG. 1b, the air interface 122 provides communication between the user equipment 104b and the eNodeB 106. Air interface 122 uses orthogonal frequency division multiple access (“OFDMA”) and single carrier frequency division multiple access (“SC-FDMA”), which is a variant of OFDMA, for downlink and uplink, respectively. OFDMA allows the use of multiple known antenna techniques, such as, for example, multiple inputs and multiple outputs (“MIMO”).

The air interface 122 provides radio resource control (“RRC”) for signal communication between the user equipment 104 and the eNodeB 106 and signal communication between the user equipment 104 and the MME (as shown in FIG. 1c). Various protocols are used, including with the non-access layer (“NAS”). In addition to signal communication, user traffic is transmitted between the user equipment 104 and the eNodeB 106. Both signal communication and traffic within the system 100 are transmitted via physical layer (“PHY”) channels.

The plurality of eNodeB 106s can be interconnected with each other using the X2 interfaces 130a to 130c. As shown in FIG. 1a, the X2 interface 130a provides the interconnection between the eNodeB 106a and the eNodeB 106b, the X2 interface 130b provides the interconnection between the eNodeB 106a and the eNodeB 106b, and the X2 interface 130c provides the interconnection between the eNodeB 106b and the eNodeB 106c. Provides interconnection between. The X2 interface can be established between the two eNodeB 106s to provide signal exchange. The exchange of signals may include load-related information, interference-related information, and handover-related information. The eNodeB 106 communicates with the evolved packet core 108 via the S1 interfaces 124a-124c. The S1 interface 124 can be divided into two interfaces. That is, a control plane (in FIG. 1c, the control plane interface (S1-MME interface) 128 is shown) and a user plane (in FIG. 1c, the user plane interface (S1-U interface) 125 is shown).

The EPC 108 establishes and implements quality of service (“QoS”) for user services, allowing the user equipment 104 to maintain a constant Internet Protocol (“IP”) address while on the move. It should be noted that each node in network 100 has its own IP address. The EPC 108 is designed to work with legacy wireless networks. The EPC 108 is also designed to separate the control plane (ie, signal communication) and the user plane (ie, traffic) in the core network architecture. This increases implementation flexibility and provides independent extensibility of control and user data functions.

The EPC108 architecture is dedicated to packet data and is shown in detail in FIG. 1c. The EPC 108 includes a serving gateway (S-GW) 110, a PDN gateway (P-GW) 112, a mobility management entity (“MME”) 114, and a home subscriber server (“HSS”) 116 (EPC 108 subscribers). Database) and policy control and billing rule function (“PCRF”) 118. Some of these (S-GW, P-GW, MME, HSS, etc.) can often be combined into multiple nodes according to the manufacturer's implementation.

The S-GW 110 functions as an IP packet data router and is a bearer path anchor of the user equipment in the EPC 108. Therefore, when the user equipment moves from one eNodeB 106 to another during the mobility operation, the S-GW 110 remains the same and goes to the EUTRAN 102 to communicate with the new eNodeB 106 servicing the user equipment 104. The bearer pass is switched. When the user equipment 104 moves to the area of another S-GW 110, the MME 114 transfers all of the bearer paths of the user equipment to the new S-GW. The S-GW 110 establishes a bearer path to one or more P-GW 112s for the user equipment. When downstream data is received for the standby user device, the S-GW 110 buffers the downstream packet and requests the MME 114 to find and reestablish the bearer path to and through EUTRAN 102.

P-GW 112 is a gateway between EPC108 (and user equipment 104 and EUTRAN102) and PDN101 (shown in FIG. 1a). The P-GW 112 functions as a router for user traffic and performs functions on behalf of user equipment. This feature includes assigning IP addresses to user equipment, filtering downstream user traffic packets to ensure that they are located in the appropriate bearer path, and performing downstream QoS, including data rates. included. Depending on the service used by the subscriber, there may be a plurality of user data bearer paths between the user equipment 104 and the P-GW 112. Subscribers can use the service on PDNs provided by different P-GWs. In this case, the user equipment has at least one bearer pass established for each P-GW 112. If the S-GW 110 is also changing during the handover of the user equipment from one eNodeB to another, the bearer path from the P-GW is switched to the new S-GW.

The MME 114 manages the user equipment 104 in the EPC 108. Management is to manage authentication, to maintain the context of the authenticated user equipment 104, to establish a data bearer path in the network for user traffic, and to be idle and not disconnected from the network. Includes tracking the location of mobile phones. For user equipment 104 that needs to reconnect to the access network to receive downstream data, MME 114 initiates paging to locate the user equipment and finds bearer paths to and through EUTRAN102. Request to be reestablished. The MME 114 of the particular user equipment 104 is selected by the eNodeB 106 at which the user equipment 104 initiates system access. The MME is typically part of a set of MMEs within the EPC 108 for load sharing and redundancy purposes. In establishing the user's data bearer path, the MME 114 is responsible for selecting the P-GW 112 and the S-GW 110 and constitutes the end of the data path through the EPC 108.

The PCRF 118 not only controls the flow-based billing function in the policy control execution function (“PCEF”) existing in the P-GW 110, but is also in charge of policy control decision making. PCRF 118 provides QoS approval (QoS class identifier (“QCI”) and bit rate) that determines how a particular data flow is processed by the PCEF and ensures that it follows the user's enrollment profile. ..

As mentioned above, IP service 119 is provided by PDN101 (as shown in FIG. 1a).

II. eNodeB.
FIG. 1d shows a configuration example of eNodeB 106. The eNodeB 106 may include at least one remote radio head (“RRH”) 132 (usually three RRH 132s may be present) and one baseband unit (“BBU”) 134. The RRH 132 can be connected to the antenna 136. The RRH132 and BBU134 can be connected using an optical interface that complies with the Common Public Radio Interface (“CPRI”) 142 standard specification. The behavior of the eNodeB 106 can be characterized using the following standard parameters (and specifications):
-Radio frequency band (Band4, Band9, Band17)
-Bandwidth (5MHz, 10MHz, 15MHz, 20MHz)
-Access method (downlink: OFDMA, uplink: SC-OFDMA)
-Antenna technology (downlink: 2x2 MIMO, uplink: 1x2 single input, multiple outputs ("SIMO"))
・ Number of sectors (maximum 6)
・ Maximum transmission power (60W)
-Maximum transmission speed (downlink: 150Mb / s, uplink: 50Mb / s)
-S1 / X2 interface (1000Base-SX, 1000Base-T)
・ Mobile environment (350km / h)
The BBU 134 can be in charge of digital baseband signal processing, S1 line termination, X2 line termination, call processing, and monitoring control processing. An IP packet received from EPC108 (not shown in FIG. 1d) can be modulated into a digital baseband signal and transmitted to RRH132. Conversely, the digital baseband signal received from RRH132 can be demodulated into IP packets for transmission to EPC108.

The RRH 132 can transmit and receive radio signals using the antenna 136. The RRH 132 can convert the digital baseband signal from the BBU 134 (using a converter (“CONV”) 140) to a radio frequency (“RF”) signal to the user equipment 104 (not shown in FIG. 1d). Power is amplified (using an amplifier (“AMP”) 138) for transmission. Conversely, the RF signal received from the user equipment 104 is amplified (using AMP138) and converted (using CONV140) into a digital baseband signal for transmission to BBU134.

FIG. 2 shows additional details of the example of eNodeB 106. The eNodeB 106 includes a plurality of layers. That is, it includes LTE layer 1 (202), LTE layer 2 (204), and LTE layer 3 (206). The LTE layer 1 includes a physical layer (“PHY”). LTE layer 2 includes medium access control (“MAC”), radio link control (“RLC”), and packet data convergence protocol (“PDCP”). LTE layer 3 includes radio resource control (“RRC”), dynamic resource allocation, configuration and provision of eNodeB measurements, radio admission control, connection mobility control, and radio resource management (“RRM”). Includes various functions and protocols, including. The RLC protocol is an automatic repeat request (“ARQ”) fragmentation protocol specified in cellular radio interfaces. The RRC protocol handles LTE Layer 3 control plane signaling between the user equipment and EUTRAN. The RRC includes functions for establishing and opening connections, broadcasting system information, establishing / reconfiguring and releasing radio bearers, RRC connection mobility procedures, paging notifications and releases, and external loop power control. PDCP performs compression and decompression of IP headers, transfer of user data, and maintenance of wireless bearer sequence numbers. The BBU 134 shown in FIG. 1d may include LTE layers L1 to L3.

One of the main functions of the eNodeB 106 is radio resource management, which schedules both uplink and downlink air interface resources for user equipment 104, controls bearer resources, and controls admissions. And include. As an agent of the EPC 108, the eNodeB 106 is in charge of transferring a paging message used to locate the mobile phone when the mobile phone is idle. The eNodeB 106 also wirelessly communicates common control channel information to establish header compression, encryption and decryption of wirelessly transmitted user data, as well as handover reporting and trigger criteria. As mentioned above, the eNodeB 106 can cooperate with other eNodeB 106s via the X2 interface for the purpose of handover and interference management. The eNodeB 106 selects an MME from a group of MMEs so that the load can be shared by a plurality of MMEs in order to avoid congestion.

III. Intelligent LTE radio access network.
FIG. 3 shows an example of a system 300 according to some embodiments of the current subject. The system 300 may be implemented as a centralized cloud radio access network (“C-RAN”) or a virtual radio access network (“V-RAN”). The system 300 may include at least one intelligent remote radiohead (“iRRH”) unit 302 and one intelligent baseband unit (“iBBU”) 304. The iRRH302 and iBBU304 may be connected using Ethernet® fronthaul (“FH”) communication 306 and the iBBU304 may be connected to EPC108 using backhaul (“BH”) communication 308. User equipment 104 (not shown in FIG. 3) can communicate with iRRH302.

In some embodiments, the iRRH 302 comprises a power amplifier (“PA”) module 312, a radio frequency (“RF”) module 314, an LTE layer L1 (or physical layer) 316, and a portion 318 of the LTE layer L2. May include. Part 318 of LTE layer L2 can include a MAC layer and may further include some functions / protocols for RLC and PDCP as described below. The iBBU 304 may be a centralized unit, capable of communicating with a plurality of iRRHs, including LTE layer L3 (322) (eg, RRC, RRM, etc.) and may also include a portion 320 of LTE layer L2. Like part 318, part 320 may include various functions / protocols for PDCP. Therefore, the system 300 may be configured to divide functions / protocols relating to PDCP between the iRRH302 and the iBBU304.

The system (eg, LTE communication) 300 can implement the features of carrier aggregation (“CA”) and collaborative multipoint (“CoMP”) transmission. CA and CoMP features are described in 4GLTE Advanced 3GPP Standards, Leases 10 and 11, respectively. Both features are designed to improve the data throughput rate and work with 4GLTE Advanced. The following is a brief summary of each of these features.

A. Carrier aggregation.
CA or channel aggregation makes it possible to use multiple LTE carriers together to provide the high data rates required for 4G LTE Advanced. These channels or carriers may be present in contiguous elements of the spectrum or in different bands. Carriers can be aggregated using continuous intraband carrier aggregation, discontinuous intraband carrier aggregation, and interband discontinuous carrier aggregation. In continuous intraband carrier aggregation, carriers are adjacent to each other and the aggregated channel is considered by the user equipment as a single expanded channel in terms of radio frequency (“RF”) (usually a channel). If they are not adjacent, more transceivers will be needed). Discontinuous intraband carrier aggregation typically requires two transceivers and the multicarrier signal is not treated as a single signal. Interband discontinuous carrier aggregation requires multiple transceivers within a single user device, which can impact cost, performance, and power. In addition, this aggregation technique requires reduction of intermodulation and intermodulation from the two transceivers. When carriers are aggregated, each carrier may be referred to as a component carrier. There are two categories of component carriers. That is, the primary component carrier (ie, the main carrier in any group, and the uplink primary component carrier associated with the primary downlink carrier), and the secondary component carrier (one or more secondary). There is a component carrier). The association between the downlink primary component carrier and the corresponding uplink primary component carrier is cell-specific.

When LTE carrier aggregation is used, it is necessary to be able to schedule data across carriers and notify terminals of DCI rates for different component carriers. Cross-carrier scheduling can be achieved individually via RRC signaling, per component carrier or per user device. When cross-carrier scheduling is not in place, downlink scheduling assignments can be achieved on a carrier-by-carrier basis. For uplinks, allocations may be generated between one downlink component carrier and one uplink component carrier. When cross-carrier scheduling is active, the physical downlink shared channel (“PDSCH”) in the downlink or the physical uplink shared channel (“PUSCH”) in the uplink is other than the physical downlink control channel (“PDCCH”). Related component carriers are sent. The carrier indicator in the PDCCH provides information about the component carriers used in the PDSCH or PUSCH. The PDSCH is the main data having a channel dynamically assigned to the user and carries the data in the transport block (“TB”) corresponding to the MAC packet data unit (“PDU”). The PDSCH is passed from the MAC layer to the PHY layer once every transmission time interval (“TTI”) (ie, 1 ms). The PDCCH is a channel for transmitting the resource allocation of the user equipment included in the downlink control information (“DCI”) message.

There are five deployment scenarios for CA. In the first scenario, cells (eg, F1 and F2 cells, etc.) can be co-located and overlaid to provide much the same coverage. Both layers provide sufficient coverage and mobility is supported at both layers. In the second scenario, cells F1 and F2 can be co-located and overlaid, but the cell in F2 has smaller coverage due to the larger path loss. Here, only the F1 cell provides sufficient coverage and the F2 cell is used to improve the throughput. Here, mobility is performed based on the coverage of the F1 cell. In the third scenario, the F1 cell and the F2 cell are arranged in the same place and overlaid, but the coverage of the F2 cell is small because the path loss of the F2 cell is large. Here only the F1 cell provides sufficient coverage and the F2 cell is used to improve the throughput. Here, mobility is based on F1 cell coverage. In the fourth scenario, the F1 cell provides macro coverage and the remote radiohead of the F2 cell is used to improve the throughput at the hotspot. In a fifth scenario, similar to the second scenario, a frequency selection repeater is deployed to extend coverage for one of the carrier frequencies. It is assumed that F1 cells and F2 cells of the same eNodeB can be aggregated in places where coverage overlaps.

B. Cooperative multipoint transmission.
As mentioned above, the CoMP transmission feature is used to transmit / receive data to / from the user equipment from several points, thereby achieving improved performance at the edge of the cell as well. Guarantee that. CoMP enables dynamic coordination of transmission and reception at various different base stations, improving the overall quality of the user and improving the usability of the network. CoMP requires close communication between multiple geographically separated eNodeBs to provide co-scheduling and co-processing of transmitted and received signals. This allows two or more eNodeBs to support user equipment at the edge of the cell in order to improve signal transmission and reception and improve throughput.

There are four deployment scenarios for CoMP. The first scenario involves a similar network with an intrasite CoMP. The second scenario also includes a homologous network, but with a higher transmit power RRH. A third scenario includes a heterogeneous network with low power RRH within macrocell coverage. Here, the transmit / receive points created by RRH have different cell identifiers as macrocells. A fourth scenario involves a heterogeneous network with low power RRH within macrocell coverage.

Combined reception and processing, and coordinated scheduling can be realized by uplink CoMP. Combined reception and processing formats can form a virtual antenna array by using antennas at different sites and coordinating between different base stations. The signals received by the base station are combined and processed to generate the final output signal. The combined reception and processing format also reduces errors when receiving low intensity signals or signals masked by interference. The co-scheduling format coordinates scheduling decisions among multiple base stations in order to reduce or minimize interference. Since only scheduling data is transmitted between different coordinating base stations, this format allows for backhaul load reduction.

C. Ethernet-based front hole in Intelligent LTE RAN.
FIG. 4 shows an example of a system 400 according to some embodiments of the current subject. An example of System 400, entitled "Long Term Evolution Radio Access Network," is disclosed in co-owned and co-pending U.S. Patent Application No. 14/179421, filed in December 2014, and the entire disclosure thereof. Is incorporated herein by reference. The system 400 may be configured to implement 4G LTE Advanced features, including carrier aggregation capabilities. The system 400 includes an integral baseband unit (“iBBU”) 402, a primary cell (“P cell”) intelligent remote radiohead 404, and one or more secondary cells (“S cell”) intelligent remote radiohead 406. May include. In LTE CA, the P cell is a serving cell that has an RRC connection with the UE radio access network. The P cell can only be modified by successfully performing the handover procedure. The S cell is a secondary cell that can be added / removed from the list of configured cells when the UE enters and exits the coverage area. The configuration of the S cell is performed by the RRC based on the mobility measurement event triggered by the UE and transmitted to the RRC.

As shown in FIG. 4, both iRRH404,406 include LTE layer 1 (ie, PHY layer), both LTE layer 2 (ie, MAC, PDCP, RLC), and like iBBU402, their own. It has LTE layer 2 (ie MAC, PDCP, RLC) divided within. The iRRH404 may include a PHY layer 412, a MAC layer 414, a scheduler P cell component 416, a master RLC component 418, an RLC status component 420, a PDCP security component 422, and a BSR component 424. Similarly, the iRRH406 may include a PHY layer 411, a MAC layer 413, a scheduler S cell component 415, a slave RLC component 419, an RLC status component 421, a PDCP security component 423, and a BSR component 425. The iBBU 402 may include a buffer management component 432, a PDCP-SN component 434, a PDCP-RoHC component 436, a VAS component 438, an RRC component 440, and a GTP component 442.

The buffer management component 432 can implement the use of the buffer occupancy report. The buffer occupancy report is received from the iRRH and controls the flow of user data to cells P and / or S, enabling sequence delivery of data to user equipment. The PDCP-SN component 434 can perform sequence numbering of the PDCP service data unit (“PDCPSDU”). The PDCP Robust Header Compression (“PDCP-RoHC”) component 436 can perform IP header compression for voice over LTE service flows. The value-added service (“VAS”) component 438 may provide application intelligence to eNodeB by performing shallow and deep packet inspection of the data flow. This component can determine how a particular data flow is treated. Inspection of shallow packets (“SPI”) can be performed by inspecting one or more headers of a data packet to determine the information associated with the data packet. For example, shallow packet inspection can inspect the IP header of a data packet to identify the source IP address of the data packet. In some embodiments, deep packet inspection (“DPI”) can be performed by examining other layers of data packets based on the results of shallow packet inspection. In some embodiments, the payload of the data packet can be inspected to determine the resource blocks to allocate to the data packet.

The iRRH404 and iRRH406 may be connected differently via an iRRH-to-iRR interface that may be a sharable connection with a direct connection 452 or a fronthaul connection 458. The iRRH404 can communicate with the iBBU402 using the front hole (“FH”) connection 458, and the iRRH406 can communicate with the iBBU using the FH connection 464.

In some embodiments, the iBBU 402 can provide centralized remote radio resource control (“RRC”) with RRC component 440. This eliminates the need for long delay RRC coordination and provides the ability to set LTE layers 2 on iRRH404s and 406s. This function may be implemented as part of a coordinated multipoint transmission function, as described below.

As shown in FIG. 4, the functions related to the PDCP protocol can be divided among iBBU402, iRRH404, and iRRH406. PDCP-RPHC436 (ROHC refers to the robust header compression protocol used to compress packets) and PDCP-SN434 (SN refers to the sequence number), as well as the buffer management component 432 in the iBBU402 are referred to as the PDPC-upper. The PDCP-security 422 and 423 in iRRH404 and 406, respectively, are called PDCP-lowers. By having the iBBU402 have a PDCP-upper and the iRRH404 and 406 have a PDCP-lower, the PDCP function is centralized, the iBBU402 has a ROHC and sequence numbering function, and the iRRH encryption function (see known PDPC technology). Can be processed. In some embodiments, the PDCP-upper in the iBBU402 can also handle the coordination of the data flow to the scheduler in the iRRH.

In addition, PDCP-upper and PDCP-lower can be used to provide flow control between iBBU402 and iRRH406. Flow control depends on the bearer's estimated data rate. For example, in downlink 462, depending on the buffer occupancy level and the estimated data rate from the report provided by the PDCP-lower, the PDCP-upper can send compressed and numbered packets to the P-cell iRRH404 and S-cell iRRH406. In some embodiments, the PDCP-lower can generate a report of buffer occupancy levels. This report can be generated on a regular basis, automatically, manually, and / or at any time on request. Based on this report, the PDCP top can estimate the buffer outflow rate based on consecutive buffer occupancy reports (such as two reports), elapsed time between reports, and additional data sent to the buffer between reports. ..

By including the buffer management function 432, the iBBU 402 can support the sequential distribution of PDCP packet data units (“PDCPPDU”) and can support the implementation of the default bearer value-added service (“VAS”) multi-queue. The buffer management function 432 can detect the buffer stall in the S cell 406 and trigger the redirection of the stall PDCPPU packet to the P cell 404. The PDCP-lower can detect old packets and drop them. In-sequence delivery of PDCPDU can refer to the requirements of the data flow transmitted in RLC confirmed mode and non-confirmed mode. The implementation of VAS multi-queues allows for data flow prioritization within the default bearer. In some embodiments, buffer stall detection is based on an estimated buffer drain rate that can be derived from the buffer occupancy report received from the PDCP-lower.

In some embodiments, the PDCP-upper may tag each packet data unit with lifetime information (referring to the time until the data packet expires) in order to perform packet redirection. can. The PDCP-lower can then delete the packet from its buffer and notify the PDCP-upper of the number of the deleted packet when the viability timer for that packet expires. The PDCP-upper can decide whether to retransmit the deleted packet to the same PDCP-lower or to redirection the deleted packet to another iRRH's PDCP-lower. Dropping of a packet can be performed in cells P and / or S, and the packet can be redirected to cell P and / or S.

In some embodiments, the RLC protocol processing can be divided into iRRH404 and iRRH406. Here, the iRRH404 may include a master RLC component 418 and the iRRH406 may include a slave RLC component 419. The master RLC component 418 can assign the RLC PDU sequence number to the slave RLC component 419, thereby centralizing the RLC PDU sequence numbering process. In the current subject system, each RLC entity can maintain a list of unconfirmed PDUs sent, so it can process ARQ procedures only for unconfirmed PDUs sent. This is because the RLC entity may not be aware of other PDUs that can be transmitted by other entities or may not have the original data to handle the retransmission of unidentified PDUs. In some embodiments, the RLCARQ status PDU can be transmitted from the user equipment at a rate of only a few tens of milliseconds, via a connection shared between iRRH interfaces, i.e., a direct connection 452 and / or a front hole 458. It can be shared between two RLC entities. In some embodiments, the iRRH-to-iRR interface can utilize industry standard stream control transport protocol (“SCTP”) via IP. Information exchange at the application layer may be based on the interprocess communication protocol.

The channel state information (“CSI”), confirmed / unconfirmed (“ACK / NACK”) signaling, precoding matrix indicator (“PMI”), and rank indicator (“RI”) received by the P-cell iRRH404 are: It may be transferred via the iRRH interface 452 for sharing with the S cell scheduler 415 via a front hole or a direct Gigabit Ethernet (“GE”) connection. This information is available to the S-cell scheduler in the same subframe as the transmitted subframe so that it does not affect the H-ARQRTT targeting 8 ms.

In some embodiments, the iRRH interface 452 is used in the S cell iRRH406 to inform the P cell iRRH404 which PUCCH resource expects the arrival of H-ARQACK / NACK feedback for packets transmitted in the S cell. (PUCCH resource allocation is defined by the 3GPP standard for 4G LTE). As a non-limiting example, the scheduler may be designed to determine on which user equipment to schedule 2 milliseconds before the data is transmitted wirelessly. H-ARQACK / NACK can be transmitted from the user device 4 ms after receiving the data. Therefore, in order to notify the P cell iRRH404 of the use of the RUCCH resource before the downlink H-ARQACK / NACK information arrives from the user equipment, the one-way delay of the iRRH-to-interface 452 is, for example, 4 mm. No more than a second. As can be understood, the above is provided as an exemplary and non-limiting example of the system of the current subject. Further, it is also understood that current subject systems are not limited to specific data scheduling parameters and / or specific delays with respect to data transmission, but can be designed with arbitrary scheduling, delays, and / or other parameters. Should be.

In some embodiments, the iRRH inter-transport 456 is shared with the front hall and can be switched by a physical direct connection 452 between the iRRH404, 406 using the iBBU402 and / or Gigabit Ethernet interface. When the iRRH interface is configured as a switched connection 456 across the front hall, for example when the iBBU402 and iRRH404 and / or iRRH406 are connected and / or arranged, and / or MW, mmWave, FSO, etc. When based on the LOS wireless transport, fronthaul delays may be based on a very low delay transport, such as when the iRRH are geographically separated.

IV. New wireless multi-technology aggregation communication network.
In some embodiments, the current subject matter relates to a 5G new radio (“NR”) communication system. 5G NR is a next-generation telecommunications standard that goes beyond the current 4G / IMT advanced standard. 5G networks will be offered at higher capacities than current 4G, increasing the number of mobile broadband users per area unit and allowing them to consume more or unlimited amount of data per month and in gigabytes per user. It is planned. This allows users to stream high resolution media for hours using their mobile devices, even if they are not on a Wi-Fi network. 5G networks are planned to have improved inter-device communication support, lower cost, lower latency, lower battery consumption, etc. than 4G equipment. Such networks have a data rate of tens of megabits per second for a large number of users, a data rate of 100 Mb / s for metropolitan areas, and users in a limited area (office floor, etc.). Simultaneously 1 Gb / s, multiple simultaneous connections of wireless sensor networks, improved spectral efficiency, improved coverage, improved signaling efficiency, reduced delay of 1-10 ms compared to existing systems. It is planned to have.

FIG. 5 shows an example of a communication system 500 capable of implementing 5G technology and providing users with the use of higher frequency bands (eg, above 10 GHz). The system 500 may include a macro cell 502 and a small cell 504,506.

The mobile device 508 may be configured to communicate with one or more of the small cells 504,506. The system 500 enables division of the control plane (C plane) and the user plane (U plane) between the macro plane 502 and the small cells 504 and 506. Here, the C plane and the U plane use different frequency bands. In particular, the small cells 502,504 may be configured to utilize a higher frequency band when communicating with the mobile device 508. The macrocell 502 can utilize the existing cellular band for C-plane communication. The mobile device 508 can be communicably coupled via the U-plane 512, and the small cell (eg, small cell 506) can provide higher data rates and more flexible / cost efficient / energy efficient operation. .. The macrocell 502 can maintain good connectivity and mobility via the C plane 510. Furthermore, depending on the location, LTE PUCCH and NR PUCCH can be transmitted at the same frequency.

FIG. 6 shows an existing long-term evolution communication network 600. The network 600 includes elements similar to those shown and described above for FIGS. 1a-1d. As shown in FIG. 6, the system 600 may include an evolved packet core (“EPC”) 602 communicatively coupled to a radio access network (“cRAN”) 604. The cRAN604 is communicably coupled to one or more master eNodeBs (“MeNB”) 606. As described above, the system 600 can implement carrier aggregation (“CA”) technology to provide communicability to user equipment communicating with the system 600.

The MeNB 606 can communically couple 614 with one or more serving eNodeBs (“SeNB”) 608s (using dual connection technology (“DC”)). The MeNB 606 may also include various networking components including PDCP, RLC, MAC, PHY layers. RF component 612 can be coupled to MeNB 606 using the CPRI interface. The SeNB 608 may include a corresponding component that can enable communication with any other third party eNodeB 610 that may be communicable with the MeNB 606 and / or the system 600. RF component 612 can be integrated into SeNB 608. The eNodeB can provide a service (“service”) 616 to its network user with respect to the above discussion.

FIG. 7 shows an example of the long-term evolution communication network 700. In contrast to the network 600, the PDCP component 718 may be removed from the MeNB 706 and replaced by a radio access network (“cRAN”) 704. In addition, the RF component 712 can be integrated into the MeNB 706. In a multi-technology aggregation communication system that may include LTE and NR functionality, the iRRH component is replaced by the dBBU component, the iBBU component is replaced by the cBBU component, and communication between the dBBU and cBBU takes place over the mid-hole link (LTE). In the system, the front hole link is used for communication between iRRH and iBBU). Also, all dBBU components are communicably coupled to cBBU.

FIG. 8 shows an example of a multi-technology aggregation system 800 according to some embodiments of the current subject. Currently, multi-technology aggregation based on the LTE Dual Connectivity (“DC”) architecture is supported. Multi-technology aggregation systems can support the transmission of LTE UL and new wireless uplinks (“NR UL”) at the same carrier frequency for reliable uplink (“UL”) operations. For uplink multiplexing purposes, multicast broadcast single frequency network (“MBSFN”) subframes and / or minislots and / or simultaneous transmission at the same frequency may be implemented. However, this may require two uplinks.

In some embodiments, to solve the shortcomings of a conventional system, the system 800 allows the transmission of new radio (NR) uplink control information (“UCI”) while reusing the LTE PUCCH. , Can provide multi-technology aggregation architectures and interfaces for the implementation of centralized and distributed RAN. In addition, if LTE UL data is present, PUCI can transmit UCI. As shown in FIG. 8, the system 800 may include an LTE base station (eg, eNodeB) 802, an NR base station (eg, gNodeB) 804, and an LTE base station (eg, eNodeB) 806. The eNodeB 806 can be the same as the eNodeB 802. The eNodeB 802 and gNodeB 804 can be used for downlink transmission to one or more user devices (CCTV, virtual reality devices, smartphones, mobile phones, etc.). The eNodeB 802 can transmit PDCCH and PDSCH data on the downlink and may have a transmission rate of up to about 1 Gb / s. The gNodeB 804 can transmit NR-PDCCH, NR-PDSCH data on the downlink and may have a transmission rate of more than 1 Gb / s (eg, up to 5 Gb / s). Nodes 802 and 804 may be communicably coupled using a multi-technology aggregation network. The eNodeB 806 (which may be the same as or different from the eNodeB 802) may be used to transmit the uplink data. The user equipment can transmit the PUCCH and the PUSCH to the eNodeB 806 together with other uplink data.

FIG. 9 is a diagram illustrating an example of a communication system 900 according to some embodiments of the current subject. The system 900 may include a base station (eg, eNodeB) 902 and an NR base station (eg, gNodeB) 904. Base station 902 can provide coverage of the area under its umbrella, in which base station 904 may be located. Base station 904 can provide a peak throughput of several Gb / s in a small area. Base station 904 can generate signals / beams specific to user equipment that can provide high area spectral efficiency. In some user equipment of the NR cell edge (ie, the cell edge of the area covered by the base station 904), the radio state may be degraded, causing frequent handovers and degradation of control channel reception performance.

FIG. 10 shows an example of a communication system 1000 according to some embodiments of the current subject. The system 1000 may resemble the system 900 shown in FIG. 9 and may include a base station (eg, eNodeB) 1002 and an NR base station (eg, gNodeB) 1004. Repeatedly, base station 1002 can provide coverage of its umbrella area. Base station 1004 may be located in the cell area of base station 1002. Base station 1002 can function as a mobility anchor and provide downlink (PDCCH, PDSCH) and uplink (PUCCH, PUSCH) transmissions to user equipment in its cell area. Further, the base station 1002 can also receive the uplink control information from the base station 1002, which may be transmitted to the base station 1002 by the uplink (PUCCH) of the base station 1002.

In some embodiments, base station 1004 may only be used for downlink transmission (capacity / throughput). Base station 1004 may implement an active antenna system (“AAS”) and beam forming (“BF”) tracking algorithm and transmit to user equipment within its coverage area. Beam formation can be used to transmit downlink NR-PDCCH and NR-PDSCH information / data. Base station 1004 can generate transmitted beams on demand based on capacity needs and / or other parameters. Base station 1004 can also perform various advanced multi-site processing functions.

FIG. 11 shows an example of a communication system 1100 capable of implementing a centralized high baseband unit (“BBU”) structure. The system 1100 may include a higher BBU (“H-BBU”) component 1102 and a lower BBU (“L-BBU”) component 1104-1108. The H-BBU component 1102 may include RRC, flow control, VAS, and PDCP function. The L-BBU component 1104-1108 may include RCL / MAC, PHY and RF layer / components. The L-BBU components 1104 and 1106 may be configured as LTE components and the L-BBU component 1108 may be configured as NR components. Information from the eNodeB and gNodeB (ie, their respective L-BBU components) can be transmitted to the H-BBU component 1102. This can be achieved using the Xx-C (control) interface and the Xx-U interface.

In some embodiments, downlink scheduling can be performed as follows: The eNodeB may transmit uplink control information (“UCI”) to the gNodeB. This may include downlink ACK / NACK, channel state information (“CSI”), precoding matrix indicator (“PMI”), and rank indicator (“RI”). The gNodeB may transmit downlink control information (“DCI”) to the eNodeB. This may include modulation coding schemes (“MCS”) and resource indications (“RIV”). As part of the flow control of the system 1100, buffer state information (eNodeB / gNodeB), average throughput (eNodeB / gNodeB), cell loading (eNodeB / gNodeB), and channel quality (eNodeB / gNodeB) can be provided. Reference signal reception power (“RSRP”) and reference signal reception quality (“RSRQ”) (eNodeB / gNodeB) can be used with activation / deactivation information for the purpose of activating / deactivating gNodeB. .. The eNodeB / gNodeB can also configure a discontinuous reception parameter (“DRX”) by configuring various RRC parameters. Further, configuration and measurement of gNodeB radio resources and mobility control information can also be used in the system 1100.

FIG. 12 shows an example of the LTE-NR internetworking architecture 1200. As shown in FIG. 12, the LTE eNodeB 1202 can be communicably coupled to the MME 1204 of the EPC via the S1-MME interface 1201 and to the gNodeB 1206 via the Xx-C interface 1203. Further, the LTE eNodeB 1202 may be communicably coupled to the S-GW 1208 of the EPC via the S1-U interface 1205 and to the gNodeB 1206 via the Xx-U interface 1207. The gNodeB 1206 may be communicably coupled to the S-GW 1208 using the S1-U interface 1209. In particular, the PDCP component 1211 of the LTE eNodeB 122 may be communicably coupled to the new radio (NR) RLC component 1213 of the gNodeB 1206 via the Xx interface 1215.

FIG. 13 shows an example of architecture 1300 capable of implementing the Xx interface 1301 between LTE eNodeB 1302 and NR gNodeB 1304. The Xx interface 1301 may include a control interface (Xx-C) and a user interface (Xx-u). In some embodiments, the eNodeB 1302 may perform down-scheduling by transmitting uplink control information (“UCI”) to the gNodeB. Here, the uplink control information may include downlink ACK / NACK, channel state information (“CSI”), precoding matrix indicator (“PMI”), and rank indicator (“RI”). The gNodeB may transmit downlink control information (“DCI”) to the gNodeB. Here, the downlink control information may include a modulation coding scheme (“MCS”) and a resource indicator (“RIV”). Flow control may provide buffer status information (eNodeB / gNodeB), average throughput (eNodeB / gNodeB), cell load (eNodeB / gNodeB), and channel quality (eNodeB / gNodeB). Reference signal reception power (“RSRP”) and reference signal reception quality (“RSRQ”) (eNodeB / gNodeB) can be provided along with various activation / deactivation information to activate / deactivate gNodeB. .. The eNodeB / gNodeB can also configure a discontinuous reception parameter (“DRX”). The configuration and immediate mobility control information of the gNodeB radio resource can also be used in the system 1300.

FIG. 14a shows a multi-technology aggregation centralized virtual RAN architecture 1400 according to some embodiments of the current subject. Architecture 1400 may include a centralized unit 1402, a master eNodeB (“MeNB”) unit 1404, and a gNodeB (“gNB”) unit 1406. The centralized unit 1402 may include at least the following components: That is, it may include RRC, GPRS tunneling protocol (“GTP”), VAS, PDCP-RoHC, PDCP-SN, PDCP security, and flow control. The MeNB unit 1404 may be communicably coupled to the centralized unit 1402 via a midhaul (which may include a backhaul link from a small cell to a master cell or from a lower BBU to a higher BBU). The MeNB unit 1404 may include at least the following components: That is, it may include BSR, RLC (with ARQ), scheduler MeNB, and MAC / PHY layer (with H-ARQ). The gNB unit 1406 may be communicably coupled to the MeNB unit 1404 using an Xx (direct) interface. The gNB unit 1406 may include at least the following components: That is, BSR, RLC (with ARQ), scheduler gNB, and MAC / PHY layer (with H-ARQ).

In some embodiments, the RRC component of centralized unit 1402 can be used to add / drop cells (eg gNB, eNodeB, etc.). PDCP components can be used to secure the U-plane. The flow control component within the centralized unit 1402 can provide activation / deactivation of the gNB unit 1406, and buffer status management and RSRP / RSRQ updates for the DRX configuration. In the gNB unit 1406, the signal-to-noise ratio (“SNR”) can be used to generate an adaptive RLC service data unit (“SDU”). The scheduler gNB component of unit 1406 may communicate with the scheduler MeNB component of unit 1404 via the Xx interface. The scheduler can share various scheduling information, CSI, PMI, RI, HARQ feedback information, and / or other information.

In some embodiments, the system 1400 can use the frequency F1_DL for the purpose of transmitting LTE downlink information for the purpose of multiplexing and transmitting UCI. In the case of uplink LTE transmission, the frequency F1_DL can be used. Frequency F2 can be used for transmission of NR uplink livelihood information. For example, the information may include NR downlink transmission, NR CSI feedback estimated based on NR DL CSI RS, or DM RS measurement from the user equipment. These may include at least one of the CQI, PMI, CQI, RI, and PMI in the form of an approach angle (“AOA”) and intensity estimate from RS. Further, the NR uplink control information may include a scheduling request (“SR”). In addition, the NR UCI can be mapped to LTE PUCCH and transmitted at frequency F1_UL.

FIG. 14b shows an example of process 1410 that can be performed by system 1400 of FIG. 14a. In step 1412, the centralized RRC component of centralized unit 1402 may perform add / drop cells. At step 1414, the various PDCP components of centralized unit 1402 can perform anchoring of the user plane. In step 1416, buffer status management and / or RSRP / RSRQ updates for enable / disable DRX settings may be communicated between the centralized unit 1402 and NR gNB1406. In step 1416, the adaptive RLC SDU can be generated based on signal-to-noise ratio (SNR) information from both eNB 1404 and gNB 1406. The schedulers of eNB 1404 and gNB 1406 (“Scheduler MeNB” and “Scheduler gNB”) may execute an independent scheduling process in step 1418. The Xx direct interface between eNB 1404 and gNB 1406 can then be used to share scheduling, CSI / PMI / RI, and / or HRQ feedback information.

FIG. 15 shows an example of a multi-technology aggregation flow control architecture 1500 for some embodiments of the current subject. Architecture 1500 may include a centralized unit (“CU”) 1502, an eNB unit 1504, and a gNB unit 1506. Unit 1502 may include at least PDCP components and multi-connectivity (“MC”) traffic forming capabilities. Units 1504, 1506 may include at least the respective RLC, MAC, PHY components / layers.

FIG. 16 shows an example of a flow control algorithm 1600 according to some embodiments of the current subject, and FIG. 17 shows an example of a flow control algorithm that can be executed by the architecture 1500.

As shown in FIG. 16, an example of the Flow Seigyo algorithm 1600 can be performed between PDCP and RLC in CU1502 (eg, shown in FIG. 15). During the initial setup during cell setup, the maximum RLC buffer size may be sent from RLC to PDCP. It may include a Qmin parameter that can be a parameter of the traffic forming function. The RLC can send a data transfer request along with the RLC buffer state information (eg, RLC_buffer_drain_rate and avg_RLC_buffer_size). Upon receiving the data transfer request, the traffic forming function of the CU 1502 may determine the size of the PDCP PDU and transfer the PDCP PDU to the RLC. The traffic formation function can be expressed as follows.

f (Qmax, Qmin, RLC_buffer_drain_rate, avg_RLC_buffer_size)

As shown in FIG. 17, the example of the flow control algorithm 1700 can be similar to the flow control algorithm 1700. However, in this case, the traffic forming function can estimate the required packet size based on the maximum / minimum RLC buffer size and the packet round trip time. The PDCP can then send the PDCP PDU to RLC. In this case, the traffic formation function can be expressed as follows.

f (Qmax, Qmin, RTT)

FIG. 18 shows an example of a multi-technology aggregation load balancing process 1800 that can be performed using eNB 1802 and / or gNB 1804 according to some embodiments of the current subject. During process 1800, incoming data 1801 is received and processed by each RLC component (ie, each RLC component of eNB and gNB) and sends a data transfer request to the PDCP of the CU (eg, unit 1502 shown in FIG. 15). can. One or more gNB1804s can also send their RLC buffer status 1820 information to the PDCP (which can also be provided for traffic formation functions within the CU). One or more gNB1804s can also send their RLC buffer state 1821 information to the PDCP (which can also be provided for traffic shaping functionality within the CU). Upon receiving the data transfer request, the traffic shaping function 1805 divides the bearer into a plurality of packet data units (“PDUs”) 1805 and divides the data into eNB 1802 (RLC SDU for P cell 1807 and segmented RLC PDU 1811). And can be transmitted to the RLC of gNB1804 (RLC SDU and RLC PDU1813 for S cell 1809). The channel recognition MAC SDU1815, 1817 can provide a resource allocation size for the RLC components in the eNB 1802 and gNB 1804 respectively.

In some embodiments, the current subject matter is a variety of average buffer sizes as well as buffer occupancy rates in the distributed unit gNB (gNB-DU) for the transmission of data associated with a particular data radio bearer to the user equipment. May contain information. This information can be provided as part of the F1 user plane protocol service (F1 is the logical interface between the centralized unit gNB (gNB-CU) and the distributed gNB (gNB-DU)). The average buffer size of the data radio bearer may represent the average buffer size for the associated data radio bearer. This average buffer size may be reported by gNB-DU to gNB-CU as part of a feedback process for controlling the downlink user data flow for a particular data radio bearer. The average buffer size can be averaged over the time between consecutive status reports. The average buffer occupancy rate can be reported in multiple RLC SDUs acquired by the MAC layer of a particular bearer between consecutive reports. As an example, the average buffer size of the data radio bearer is a 4-octet status report frame (eg, having a value range of 0 ... 2 ^32-1 ), and the average buffer occupancy rate is also a 4-octet status report frame. (For example, it can be in the range of 0 ... 2 ³² -1).

In some embodiments, the current subject may be configured to be implemented, for example, in the system 1900 shown in FIG. The system 1900 may include one or more of a processor 1910, a memory 1920, a storage device 1930, and an input / output device 1940. Each of the components 1910, 1920, 1930, 1940 can be interconnected using the system bus 1950. Processor 1910 may be configured to process instructions for execution within system 600. In some embodiments, the processor 1910 can be a single-threaded processor. In an alternative embodiment, the processor 1910 can be a multithreaded processor. Processor 1910 may be further configured to process instructions stored in memory 1920 or storage device 1930, including sending and receiving information via input / output devices 1940. The memory 1920 can store information in the system 1900. In some embodiments, the memory 1920 may be a computer readable medium. Further in some embodiments, the memory 1920 may be a non-volatile memory unit. The storage device 1930 may provide the system 1900 with a large capacity storage device. In some embodiments, the storage device 1930 can be a computer readable medium. In an alternative embodiment, the storage device 1930 can be a floppy disk device, a hard disk device, an optical disk device, a tape device, a non-volatile solid state memory, or any other type of storage device. The input / output device 1940 may be configured to provide input / output operations to the system 1900. In some embodiments, the input / output device 1940 may include a keyboard and / or a Ponting device. In an alternative embodiment, the input / output device 1940 may include a display unit for displaying a graphical user interface.

FIG. 20 shows an example of Method 2000 with respect to some embodiments of the current subject. In step 2002, the first base station (eg LTE eNodeB) can transmit the downlink data to the user equipment. The transmission can utilize the first downlink frequency. In step 2004, the first base station can use the first uplink frequency to receive uplink data from the user equipment. In step 2006, the second base station (eg, NR gNodeB, etc.) may transmit downlink data to the user equipment. A second downlink frequency may be utilized in this transmission. In step 2008, the second base station can transmit uplink data to the first base station using the first uplink frequency.

In some embodiments, the current subject matter may include one or more of the following optional features. The first downlink data may be transmitted using the first base station of the wireless communication system, and the first uplink data may be received using the first base station. Similarly, the second downlink data can be transmitted from the second base station of the wireless communication system, and the second uplink data can be transmitted from the second base station to the first base station.

In some embodiments, the first and second base stations may include at least one of an eNodeB base station, a gNodeB base station, and any combination thereof. At least one of the first base station and the second base station may include at least one of a radio transmitter, a radio receiver, and any combination thereof. The first and second base stations can be base stations operating in at least one of a long-term evolution communication system and a new wireless communication system.

In some embodiments, at least one of the first and second base stations is configured to provide at least one of the first and second base stations with at least packet data convergence protocol control information. It can be communicably coupled to at least one centralized unit. At least one of the first and second uplink data may include user control information.

In some embodiments, Method 2000 uses a centralized unit to generate a packet data convergence protocol packet data unit based on information provided by at least one of the first and second base stations. And the step of transmitting the generated packet data unit to at least one of the first and second base stations. The method may include a step of individually generating scheduling information by the first and second base stations and a step of sharing the generated scheduling information between the first and second base stations.

The systems and methods disclosed herein can be implemented in various forms, including, for example, data processors such as computers including databases, digital electronic circuits, firmware, software and the like. Moreover, the features and other aspects and concepts mentioned above in the embodiments of the present disclosure may be implemented in a variety of environments. These environments and related applications may be specially constructed to perform various processes and operations according to the disclosed embodiments, or they may be coded to provide essential functionality. It may include a general purpose computer or computing platform that has been selectively enabled or reconfigured. The processes disclosed herein are not inherently relevant to any particular computer, network, architecture, environment or other device and may be performed with the appropriate combination of hardware, software and / or firmware. .. For example, various general purpose machines can be used with programs written in connection with the teachings of the disclosed embodiments. It may also be convenient to build specialized equipment or systems to carry out the requested methods and techniques.

The systems and methods disclosed herein are for execution by computer program products, ie, data processing devices such as programmable processors, computers or multiple computers, or to control the operation of those data processing devices. Can be implemented as a computer program explicitly implemented as an information carrier, such as a machine readable storage medium or a transmitted signal. Computer programs may be written in any form of programming language, including compiled or translated languages, and may be in the form of a stand-alone program or as a module, component, subroutine or other unit suitable for use in a computing environment. Can be deployed in any form, including. The computer program may be deployed on one computer, a plurality of computers at one point, and a plurality of computers distributed at a plurality of points and interconnected by a communication network.

As used herein, the term "user" can refer to any entity, including a person or computer.

In some cases, sequence numbers such as "first", "second", etc. may be associated with an sequence, but as used herein, sequence numbers do not necessarily imply an sequence. is not it. For example, sequence numbers can only be used to distinguish one object from another. For example, to distinguish the first event from the second event, it does not necessarily suggest a chronological order or a fixed reference system (eg, the first event in one paragraph of the specification is. It can be different from the first event in another paragraph of the specification).

The above description is intended to illustrate, but not to limit, the scope of protection of the invention defined in the claims that follow. Other embodiments are included in the scope of protection of the following claims.

These computer programs, also called programs, software, software applications, applications, components, or codes, include machine instructions for programmable processors, high-level procedural programming languages and / or object-oriented programming languages, and / or assemblies /. It can be implemented in a machine language. As used herein, a "machine-readable medium" includes a machine-readable medium that receives machine instructions as a machine-readable signal and is any program product such as a magnetic disk, optical disk, memory, programmable logic device (PLD), etc. , A device and / or a device. The term "machine readable signal" refers to any signal used to provide machine instructions and / or data to a programmable processor. Machine-readable media can store these machine instructions non-temporarily, as do, for example, non-temporary solid-state memory or magnetic hard drives, or any storage medium equivalent thereto. Machine-readable media are alternative or additional, such as processor caches, or other random access memory associated with one or more physical processor cores, in a temporary manner with those machine instructions. May be stored.

To provide interaction with the user, the subject matter described herein is a display device, such as a brown tube (CRT) monitor or liquid crystal display (LCD) monitor, for displaying information to the user, and the user computer. It can be implemented on a computer having a keyboard and a pointing device such as a mouse or trackball capable of providing input to the computer. Other types of devices may be used to provide interaction with the user. For example, the feedback provided to the user may be any form of sensory feedback, such as visual feedback, auditory feedback, or tactile feedback, and the input from the user may be acoustic input, audio input, or tactile input. Can be received in any form, including but not limited to them.

The subject matter described herein is
(1) include back-end components such as, for example, one or more data servers, or (2) includes middleware components, such as, for example, one or more application servers, or (3), for example, as described herein by the user. Includes front-end components such as one or more client computers with a graphical user interface or web browser capable of interacting with embodiments of the subject, or (4) these back-end, middleware, or front-end components. It can be performed on a computational system that includes any combination of. The components of the system may be interconnected by any form or intermediary of digital data communication, such as communication networks. The communication network includes, but is not limited to, a local area network (“LAN”), a wide area network (“WAN”), the Internet, and the like.

Computational systems can include clients and servers. Generally, but non-exclusively, clients and servers interact remotely with each other, typically over a communication network. The client-server relationship is generated by a computer program that is executed on each computer and has a client-server relationship with each other.

The embodiments described above do not represent all embodiments relating to the subject matter described herein. Rather, those embodiments are only a few examples of aspects relating to the described subject matter. Some variants have been described above, but other changes or additions are possible. In particular, in addition to the features and / or variants described herein, additional features and / or variants may be provided. For example, it can be various combinations and partial combinations of disclosed features, and / or combinations and partial combinations of some additional features disclosed above. In addition, the logic flows shown in the accompanying figures and / or described herein do not necessarily require the particular order shown to obtain favorable results. Other embodiments may be included in the scope of protection of the following claims.

Claims (9)

The step of transmitting the first downlink data to the user equipment using the first downlink frequency,
A step of receiving the first uplink data from the user device using the first uplink frequency, and
A step of transmitting the second downlink data to the user equipment using the second downlink frequency, and
Including the step of receiving the second uplink data using the first uplink frequency.
The first downlink data is transmitted using the first base station in the wireless communication system, and the first uplink data is received using the first base station.
The second uplink data is transmitted from the second base station in the wireless communication system using the second downlink frequency, and the second uplink data is the first uplink frequency. Is transmitted from the second base station to the first base station, and then received by the first base station.
At least one of the first and second base stations is configured to provide at least packet data convergence protocol control information to at least one of the first base station and the second base station. Communicably coupled to at least one centralized unit,
The centralized unit generates a packet data convergence protocol packet data unit based on the information provided by at least one of the first and second base stations, and the generated packet data unit. Configured to transmit to at least one of the first and second base stations.
Computer implementation method. The first and second base stations include at least one of an eNodeB base station, a gNodeB base station, and any combination thereof.
The method according to claim 1. At least one of the first base station and the second base station includes a radio transmitter and a radio receiver .
The method according to claim 2. The first and second base stations are base stations that operate in at least one of a long-term evolution communication system and a new wireless communication system.
The method according to any one of claims 1-3. The at least one centralized unit is configured to include a multi-connectivity traffic forming function.
The method according to any one of claims 1-4. At least one of the first and second uplink data includes uplink control information.
The method according to any one of claims 1-5. A step of independently generating scheduling information by the first and second base stations,
The first and second base stations further include a step of sharing the generated scheduling information.
The method according to claim 6 . With at least one programmable processor,
A non-transitory machine-readable medium that stores an instruction, wherein the instruction performs the operation according to any one of claims 1-7 when executed by the at least one programmable processor . system. Any of claims 1-7 for a computer program product comprising a non-temporary machine-readable medium containing an instruction and executed by at least one programmable processor for the at least one programmable processor. To execute the operation described in one,
Computer program product.

Images