JP6896640B2 - Convenient access to millimeter-wave wireless access technology based on Edge Cloud Mobile Proxy - Google Patents

Description

Cross-reference to related applications This application is entitled "OPPORTUNISTIC ACCESS OF 5G MMWAVE RAT BASED ON EDGE CLOUD MOBILE PROXY" (convenient access to 5G MMWAV RAT based on Edge Cloud Mobile Proxy) filed on March 4, 2015. Claims priority over US Provisional Application No. 62 / 128,009, the entire disclosure of which is incorporated herein by reference for all purposes.

Embodiments of the present disclosure generally relate to the field of wireless communication, and more specifically to devices and methods for controlling expedient access to the spectrum of wireless air interfaces.

Next-generation wireless communication systems can be expected to utilize the wireless spectrum in the frequency band above 6 GHz (GHz). Channels in the frequency band above 6 GHz are commonly referred to as millimeter wave (mmWave) channels. The mmWave channel appears to be on and off due to the features of the mmWave channel, such as high-pass loss and quasi-optical propagation (but not limited). When the mmWave channel is on, communication links on the channel may observe high throughput rates. Communication links may be lost when the mmWave channel is off. In various scenarios, on / off dynamics may depend on the communication environment and the deployment of mmWave base stations. In many high-interest communication scenarios such as street canyons, city squares, offices, and shopping malls, channel on / off frequency and off time can be set in seconds.

The use of mmWave channels may increase the overall data rate supported by wireless communication systems, but improved mmWave channel integration may need to be improved to provide reliable communication. Absent.

The embodiments will be readily understood by the following detailed description in conjunction with the accompanying drawings. To facilitate this description, the same reference numbers refer to similar structural elements. Embodiments are shown as examples, but not limitations, in the drawings of the accompanying drawings.
It is a graph which shows the example of the channel dynamics of the mmWave channel which concerns on some embodiments. The network communication environment according to some embodiments is shown. An electronic device circuit according to some embodiments is shown. The wireless communication circuit which concerns on some embodiments is shown. The Ethernet controller according to some embodiments is shown. The computing device according to some embodiments is shown. The interaction of the modules of the communication protocol stacks of different devices according to some embodiments is shown. The schematic diagram of the traffic and feedback flow which concerns on some embodiments is shown. The reporting procedure according to some embodiments is shown. The convenience access operation according to some embodiments is shown. It is a flowchart which shows the TCP rate control operation which concerns on some Embodiments. The convenience access operation according to some embodiments is shown. The convenience access operation according to some embodiments is shown. The flowchart of the TCP management operation which concerns on some embodiments is shown. The convenience access operation according to some embodiments is shown. An exemplary computer readable storage medium according to some embodiments is shown.

The following detailed description will refer to the accompanying drawings that form part of this specification. In the figure, similar reference numbers indicate similar parts and are shown as exemplary embodiments that can be implemented. It should be understood that other embodiments may be utilized and structural or logical changes may be made without departing from the scope of the present disclosure.

Various actions may be described as multiple individual actions or actions in the most useful way to understand the subject matter described in the claims.

However, the order of description should not be construed as implying that their actions do not necessarily depend on the order. In particular, those actions do not have to be performed in the order presented. The operations described may be performed in a different order than the described embodiments. Various additional actions may be performed or the described actions may be omitted in the additional embodiments.

In the present disclosure, the phrase "A or B" means (A), (B) or (A and B). In the present disclosure, "A, B or C" means (A), (B), (C), (A and B), (A and C), (B and C), or (A, B and C). ) Means.

The description may use the expressions "in one embodiment" or "in a plurality of embodiments", each of which may refer to one or more of the same or different embodiments. Further, the terms "comprising", "including", "having" and the like used with respect to the embodiments of the present disclosure are synonyms.

FIG. 1 is a graph 100 showing an example of channel dynamics of a mmWave channel. In particular, Graph 100 shows the channel gain in decibels (dB) over the period in which the user equipment (UE) is moving.

Radio waves within the mmWave channel may have short wavelengths (eg, less than 500 mm) and may be associated with relatively high attenuation that can be caused by radio waves absorbed by the atmosphere, rain, and the like. The shorter the wavelength of such radio waves, the more diffuse reflections will occur, causing multipath propagation and causing fading problems. Moreover, such radio waves can be associated with significant frequency Doppler shifts, even at pedestrian speeds. The problem of radio wave propagation in such a mmWave channel can result in the channel dropping out periodically, as briefly introduced above. For example, Graph 100 shows that during a period that begins after 1 second and continues for about 6 seconds, the mmWave channel is on and can provide a significant channel gain that peaks at about -95 dB. However, immediately after the 6th second, the mmWave channel may be completely turned off and not turned back on until the 7th second is approached. At this time, the channel gain of the mmWave channel may increase to about −105 dB. Therefore, for a time close to 1 second, the mmWave channel is effectively turned off and any communication links established on the channel are dropped.

The channel on / off effect shown by Graph 100 suggests that different techniques may be used for connectivity and traffic management in the higher frequency bands compared to the lower frequency bands. The embodiments of the present disclosure are when the connection is maintained by radio access technology (RAT) operating in the low frequency band (eg, less than 6 GHz), while the RAT operating in the high frequency band (eg, above 6 GHz) is available. Provides access to the channel for convenience. Embodiments describe mobile proxies and traffic shaping that can be applied to turn unstable expedient access links into stable connections.

In the present disclosure, examples of expedient access and traffic shaping by components of a wireless communication system including, for example, a mobile proxy are described.

In some embodiments, expedient access and traffic shaping can be based on an anchor-booster architecture that provides a relatively stable connection by macroevolved node B (MeNB), while expedient communication links. A relatively unstable but large capacity connection is provided by the small cell eB (SeNB) to support.

Some embodiments may additionally / alternative include a traffic control mechanism implemented by a mobile proxy that may be present within the core network. Mobile proxies can manage expedient links and traffic buffering in the edge cloud. As used herein, an edge cloud is a core network entity that directly interfaces with a radio access network entity.

In various embodiments, the mobile proxy can terminate the transport layer that provides control of data transfer over the transport network. Mobile proxies can control data transfer over the transport network and buffer UE traffic in order to reduce or avoid fluctuations in radio channel capacity that adversely affect network traffic. A transport network refers to a network of devices connected by a transport layer (eg, a transmission control protocol (TCP) layer). The termination of the transport network may be a device that performs TCP layer operations, such as a mobile proxy or sending entity (eg, an application server). The transport network may traverse the core network to connect the terminations.

Mobile proxies can manipulate transport network traffic to accommodate the underlying radio access network capacity. Anchor eNBs, such as MeNBs, can maintain a radio resource control (RRC) connection with the UE. In various embodiments, the anchor eNB or mobile proxy may schedule expedient access to the mmWave booster cell in the user plane based on traffic size, traffic type, quality of service (QoS) requirements and mmWave wireless link quality. it can.

This high radio network data rate is always useful for transport networks, even if the average network capacity in the mmWave band is high, due to the dramatic fluctuations in the radio link rate due to the channel on / off effect described above. Not always. Thus, this disclosure describes expedient access procedures in edge clouds and radio access networks. Buffering and transport layer management in the edge cloud helps facilitate unstable expedient access links within radio access networks. Manipulating and scheduling traffic can turn unstable expedient access links into stable connections.

FIG. 2 shows a network communication environment 200 according to some embodiments. The network communication environment 200 (or simply "environment 200") includes a core network (CN) device 204 (which may include a mobile proxy 206), a macro evolution node B (MeNB) 208, and a small cell evolution node B (SeNB). Includes 212 and user equipment (UE) 216.

In some embodiments, the eNBs 208,212 are consistent with the specifications and protocols developed by the 3rd Generation Partnership Project (3GPP) (eg, but not limited to the Long Term Evolution (LTE) Technical Specification (TS)). It may be part of an advanced universal terrestrial radio access network (E-UTRAN) that provides wireless air interfaces.

As used herein, "LTE" may generally refer to releases related to the original LTE, LTE-Advanced (LTE-A), 5G, and the like. In other embodiments, the eNBs 208,212 are GSM® (Global System for Mobile Communication), General Packet Radio Service (GPRS), Universal Mobile Communication System (UMTS), High Speed Packet Access (HSPA), but not limited to. , Evolved HSPA (E-HSPA), and may be part of other cellular systems.

CN device 204 may be part of a core network (or Evolved Packet Core (EPC) of System Architecture Evolution (SAE)) responsible for overall control of the UE and establishment of bearers, with defined quality of service. It may be an IP packet flow having (QoS). In some embodiments, the CN device 204 can be considered to be at the edge of the core network and can therefore be referred to as an edge cloud device. The CN device 204 may include a serving gateway (S-GW) that acts as a local mobility anchor for the data bearer when the UE 216 is idle, with the CN mobility management entity (MME) reestablishing the bearer. The downlink data may be temporarily buffered while starting paging of the UE 216 for this purpose. The S-GW can also perform management functions on the visited network (eg, collect data usage statistics for billing purposes).

In some embodiments, the CN device 204 may additionally / optionally include one or more other logical nodes of the CN. For example, CN device 204 is responsible for IP address allocation for UE 216, quality of service (QoS) enforcement according to rules from the Policy and Billing Rule Function (PCRF), and flow-based billing. -GW) may be included. The CN device 204 may additionally / optionally include an MME, which is a control node that handles signaling between UE 216 and CN, such as signaling based on a non-access layer (NAS) protocol. Good. MME is a function related to bearer management (eg, establishment, maintenance, release of bearers processed by the session management layer of the NAS protocol), such as being processed by the connection or mobility management layer within the NAS protocol layer. , Connection between CN and UE 216 and establishment of security), or functions related to interworking with other networks.

As further detailed, the CN device 204 may include a mobile proxy 206 that manages the transport layer connection at the edge of the CN to facilitate reliable communication over the wireless air interface. In some embodiments, the mobile proxy 206 may employ buffering to manage transport layer functionality of the core network. For example, the mobile proxy 206 may receive traffic from the sending entity over a transport network connection that traverses the core network (where the CN device 204 is located). The mobile proxy 206 can buffer the traffic in the memory circuitry of the CN device 204 and cause the traffic to be sent to the radio access network eNB (eg MeNB 208 or SeNB 212) over a connection that traverses the radio access network. Can be done. The exact scheduling of one or more links to which traffic is transmitted may be determined by the scheduling logic in the mobile proxy 206 or MeNB 208.

The mobile proxy 206 may receive information about the capacity of links 220,224 and may control the data rate of the transport network in which the traffic is received. In this way, the mobile proxy 206, which acts as an edge cloud device, can effectively manage the transport network and at least participate in the effective transfer of data over the links of the air interface. Environment 200 can have a number of interfaces that specify signaling procedures and message types that can be transmitted between different entities. The eNB may communicate with the UE 216 via the Uu interface. The eNBs may communicate with each other via the X2 interface. The eNB may communicate with the mobile proxy via the SI interface. The SGW may communicate with the PGW via the S5 / S8 interface.

The MeNB 208 may be a relatively high power cellular base station that provides radio coverage for the UE over a relatively large coverage area. For example, in some embodiments, the MeNB 208 can provide radio coverage over a distance of 1 to 20 kilometers (km). In some embodiments, the MeNB 208 can have an output of tens of watts.

The SeNB 212 may be a relatively low power cellular base station that provides radio coverage for the UE over a relatively small coverage area as compared to the MeNB 208. For example, in some embodiments, the SeNB 212 can provide radio coverage over a distance of less than 1000 meters (m). In some embodiments, the SeNB 212 can have an output of less than a few watts. The SeNB 212 can be referred to as a microcell, picocell or femtocell eNB in various embodiments.

The MeNB 208 may implement a first RAT operating in a lower frequency band (eg, less than 6 GHz) to support a first communication link with the UE 216. The first communication link, also called an anchor link, can provide a baseline connection for signaling and data exchange between the UE 216 and the network.

The low frequency band is the evolutionary universal terrestrial radio access (E-UTRA) operating band used for frequency division duplex (FDD) 1-5, 7-14, 17-4, 65, 66, or time division duplex (TDD). ) May include the E-UTRA operating band 33-45. These E-UTRA operating bands can have a frequency band between about 700 MHz and 3700 MHz. In other embodiments, other frequency bands such as the GSM (Global System for Mobile Communications) frequency band and the Universal Mobile Communications (UMTS) frequency band can be used, which are high-speed downlink packet access (HSDPA) networks. , UMTS network, WiMAX (worldwide interoperability for microwave access) network, and other types of networks with or without RAT.

The SeNB 212 may implement a second RAT operating in a higher frequency band (eg, above 6 GHz) to support a second communication link with the UE 216. The second communication link, also called a booster link, can provide additional resources for exchanging data between the UE 216 and the network, if available.

The higher frequency band can have radio waves with wavelengths of about 500 mm to 1 mm. As used herein, this wavelength range is sometimes referred to as the "mmWave" wavelength. The higher frequency band, in some embodiments, is the milliband described by the International Telecommunication Union (IEEE) (having a frequency range of 110-300 GHz and a frequency range of 2.73 mm to 1 mm), International Telecommunication Union. The ITU radio band 10 (6-30 GHz) or the ITU radio band 11 (30-300 GHz) may be included.

Each of the communication links can include a number of different transmission layers (eg, used in multi-input, multi-output (MIMO) communication) or a number of different carriers (eg, used in a carrier aggregation environment). In addition, additional eNBs, transmit points or remote radio heads can be deployed in tuned multipoint scenarios. In general, the embodiments described can be incorporated into various cellular network deployments consistent with the description provided herein.

Communication within the environment 200 can distinguish between two different types of data flows. The first data flow (which can be called the user plane (U plane)) refers to data that is exchanged directly and transparently between users in an end-to-end connection, such as voice data or Internet Protocol (IP) packets. May include. The second data flow (which can be referred to as the control plane (C plane)) may include signaling information exchanged between the user and the network. Therefore, the C plane may be used for signaling information for exchanging a message for establishing a call or, for example, a message for updating a position.

The X2 interface between MeB208 and SeB212 can enable both C-plane and U-plane signaling. The SI interface between the MeNB 208 and the mobile proxy 206 can enable both C-plane and U-plane signaling. The SI interface between the SeNB 212 and the mobile proxy 206 can enable U-plane signaling.

In some embodiments, the C-plane connection of the SeNB 212 may be anchored to the MeNB 208 and the C-plane connection of the MeNB 208 may be anchored to the mobile proxy 206. Therefore, the SeNB 212 may exchange signaling information with the network via the MeNB 208, and the MeNB 208 may directly exchange signaling information with the network. In some embodiments, the U-plane connection of the SeNB 212 may be with the mobile proxy 206 of the MeNB 208 or CN device 204.

FIG. 3 shows an electronic device circuit 300 according to some embodiments. The electronic device circuit 300 may implement an eNB (eg, MeNB 208 or SeNB 212), CN device 204 or UE 216, may be incorporated, or may otherwise be part of it. In embodiments, the electronic device circuit 300 may include a communication circuit 304. The communication circuit 304 may include a control circuit 308, a transmission / reception circuit 312 including a transmission circuit 316 and a reception circuit 320, and a media interface circuit 324.

As used herein, the term "circuit" is an application specific integrated circuit (ASIC), electronic circuit, processor (shared, dedicated or group) or memory (shared, dedicated) that executes one or more software or firmware programs. Alternatively, it may refer to a group), a combination logic circuit, or any other suitable hardware component that provides the described functionality, which may be part of it, or may include them. In some embodiments, the electronic device circuit 300 may be implemented in one or more software or firmware modules, or the functions associated with the circuit may be implemented in one or more software or firmware modules. ..

The media interface circuit 324 may include circuit elements configured to communicatively couple the transmit and receive circuits 312 with a wired or wireless communication medium. In some embodiments, the media interface circuit 324 can include one or more antenna elements (for transmitting / receiving signals over the radio medium), amplifiers, filters, etc., as commonly indicated. It may include front-end components. In other embodiments, the media interface circuit 324 may include components for interfacing with other networks. For example, in some embodiments, the media interface circuit 324 may include an Ethernet® interface and may include a port or other media interface, such as a coaxial, twisted pair, fiber optic physical media interface.

The transmission / reception circuit 312 may combine the control circuit 308 with the media interface circuit 324. The transmission / reception circuit 312 may receive a signal from the control circuit 308, perform various signal processing functions, and prepare a signal for transmission via an appropriate communication medium by the media interface circuit 324. The transmission / reception circuit 312 may also receive a signal from the media interface circuit 324 and perform various signal processing functions to prepare the signal for transmission to the control circuit 308. In an embodiment in which the electronic device circuit 300 interfaces with, for example, a Uu interface wireless communication medium, the communication circuit 304 is a radio frequency portion that uses one or more digital signal processors (DSPs) and communication algorithm processing including a channel code. , A mixed signal portion and an analog portion, and a baseband portion may be included. This embodiment will be described in more detail with respect to FIG.

In an embodiment in which the electronic device circuit 300 interfaces with, for example, a wired communication medium of SI, X2 or S5 / S8 interface, the communication circuit 304 may provide signal processing according to an appropriate communication network protocol. For example, the communication circuit 304 may include an Ethernet controller that implements Ethernet protocols such as, for example, 10 Gigabit Ethernet, 1000BASE-T, 100BASE-TX, and 10BASE-T standards. This embodiment will be described in more detail with respect to FIG.

The control circuit 308 may include circuits that perform link layer (eg, media access control (MAC) layer) and upper layer operations to facilitate communication over a suitable network. In some embodiments, the digital physical layer (PHY) operation may also be performed by the control circuit 308 when the analog PHY operation is performed by the transmit and receive circuit 312.

As described in more detail herein, the control circuit 308 may operate to reduce fluctuations in radio channel capacitance in communication between the core network and the UE. The control circuit 308 is a method of reducing fluctuations in radio channel capacitance and providing highly reliable communication via a radio interface, and various accesses are made to enable convenient access of communication links in high frequency bands. Network control operations may be performed. In particular, access network control operations may include traffic reporting, scheduling, buffering / caching, traffic shaping, rate control, and the like. These operations will be described in more detail herein.

In some embodiments, the control circuit 308 may include various circuits, including, for example, a processing circuit and a memory circuit, in order to perform the operations described herein. In some embodiments, the control circuit 308 may implement a mobile proxy that provides access network control operations from a CN device, such as the CN device 204.

FIG. 4 shows a wireless communication circuit 400 according to some embodiments. The wireless communication circuit 400 can be implemented in the electronic device circuit 300 to provide a wireless connection. For example, the wireless communication circuit 400 may be used when the electronic device circuit 300 is adopted in the MeNB 208, SeNB 212 or UE 216 for communication via the Uu interface.

The radio communication circuit 400 may include at least a baseband circuit 404, an RF circuit 406, a front end circuit 408 and an antenna 410 coupled to each other as shown. In general, the baseband circuit 404 may be incorporated into the control circuit 308, the RF circuit 406 may be incorporated into the transmit and receive circuit 312, and the front end (FE) circuit 408 may be incorporated into the media interface circuit 324. However, it will be appreciated that in some embodiments, some features described for one component may be implemented in another component.

The baseband circuit 404 may include, but is not limited to, one or more circuits such as single-core or multi-core processors. The baseband circuit 404 is one or more baseband processors for processing the baseband signal received from the receive signal path of the RF circuit 406 and generating a baseband signal for the transmit signal path of the RF circuit 406. It may include control logic. The baseband processing circuit 404 may interface with the application circuit (on the platform hosting the communication circuit 400) for the generation and processing of the baseband signal and the control of the operation of the RF circuit 406. For example, in some embodiments, the baseband circuit 404 is a second generation (2G) baseband processor 404a, a third generation (3G) baseband processor 404b, a fourth generation (4G) baseband processor 404c, or a first. A 5th generation (5G) baseband processor 404d may be included. Other embodiments may have other baseband processors for other existing generations, generations under development, or generations to be developed in the future.

In some embodiments, the baseband circuit 404, RF circuit 406, FE circuit 408 and antenna 410 may have components dedicated to wireless communication in the low or high frequency bands. For example, in some embodiments, the 4G baseband processor 404c may be used for communication in the low frequency band and the 5G baseband processor 404d may be used for communication in the high frequency band.

The baseband circuit 404 (eg, one or more of the baseband processors 404a-d) may handle various radio control functions that allow communication with one or more radio networks via the RF circuit 406. Radio control functions may include, but are not limited to, signal modulation / demodulation, coding / decoding, radio frequency shifting, and the like. In some embodiments, the modulation / demodulation circuit of the baseband circuit 404 may include a Fast Fourier Transform (FFT), precoding or constellation mapping / demapping function. In some embodiments, the coding / decoding circuit of baseband circuit 404 may include convolution, tailbeat convolution, turbo, viterbi, or low density parity check (LDPC) encoder / decoder functions.

Embodiments of modulation / demodulation and encoder / decoder functions are not limited to these examples, and other embodiments may include other suitable functions.

In some embodiments, the baseband circuit 404 comprises elements of, for example, PHY, MAC, radio link control (RLC), packet data convergence protocol (PDCP), radio resource control (RRC), of the E-UTRAN protocol. It may contain elements of the protocol stack, such as elements. The central processing unit (CPU) 404e of the baseband circuit 404 may be configured to execute an element of the protocol stack for signaling in the PHY, MAC, RLC, PDCP or RRC layers. The layer of the protocol stack will be briefly described. The protocol stack discussion with respect to FIG. 4 is primarily based on the E-UTRA protocol stack, although some of the description may also accommodate non-E-UTRA protocol stacks.

The PHY layer can refer to hardware transmission techniques for networks, such as cabling, wiring, frequencies, pulses used to represent binary signals, and the like. The PHY layer can carry all information from the MAC transport channel via the air interface for link adaptation, power control, cell search (for initial synchronization and handover purposes) and other measurements of the RRC layer. Can be handled.

The MAC layer can provide an addressing and channel access control mechanism that allows a terminal to communicate within a multiple access network using a shared medium. The MAC layer can be connected to the physical layer via the transport channel and to the RLC layer via the logical channel. The MAC layer can perform multiplexing and demultiplexing between logical and transport channels and perform error correction via hybrid automatic repeat requests (HARQ), dynamic scheduling and channel prioritization. it can. Multiple access protocols that can be used in packet wireless wireless networks may include code division multiple access (CDMA) and orthogonal frequency division multiple access (OFDMA).

The RLC layer can communicate with the PDCP layer via a service access point (SAP) and with the MAC layer via a logical channel. The RLC layer can operate in one of three modes: transmission mode (TM), unacknowledged mode (UM) and acknowledged mode (AM). Depending on the mode, the RLC layer can perform various operations on the RLC service data unit (SDU) and protocol data unit (PDU), for example, error correction by automatic repeat request (ARQ), data transfer. And concatenated segmentation, RLC SDU reassembly, RLC PDU resegmentation, duplicate detection, protocol error detection, etc. can be performed.

The PDU layer includes header compression and decompression for user plane data, security functions (eg, encryption and decryption of user plane and control plane data, and integrity protection verification of control plane data), and handover support functions (eg, for example. Sequence distribution and rearrangement of the upper layer PDU, handover loss for the user plane data mapped to the RLC AM mode), and discarding of the user plane data due to the timeout can be performed.

The RRC layer may be the main layer that plays a role in controlling the functions within the access layer (AS). The RRC layer can establish a radio bear and form a lower layer using RRC signaling between the UE and the eNB. The RRC layer can provide broadcast of system information, RRC connection control, network controlled inter-RAT movement, measurement configuration reports, and the like.

In some embodiments, the baseband circuit may include one or more audio digital signal processors (DSPs) 404f. The audio DSP404f may include elements for compression / decompression and echo erasure, and in other embodiments may include other suitable processing elements.

The baseband circuit 404 may further include 404 g of memory / storage.

The memory / storage 404g may be used to load and store data or instructions for operations performed by the processor of baseband circuit 404. The memory / storage 404 g of one embodiment may include a computer-readable storage medium embodied in any combination of suitable volatile or non-volatile memory. Memory / storage 404g includes, but is not limited to, read-only memory (ROM) with embedded software instructions (eg, firmware), random access memory (eg, dynamic random access memory (DRAM)), cache, buffer, and the like. It may include any combination of various levels of memory / storage. The memory / storage 404g may be shared between various processors or may be dedicated to a particular processor.

In some embodiments, the components of the baseband circuit 404 may be properly combined on a single chip or a single chipset, or may be located on the same circuit board. In some embodiments, some or all of the components of the baseband circuit 404, RF circuit 406, or FE circuit 408 may be mounted together, for example, on a system on chip (SOC). In some embodiments, the baseband circuit 404 may provide communication compatible with one or more RATs. For example, in some embodiments, the baseband circuit 404 supports communication with an E-UTRAN or other wireless metropolitan area network (WMAN), wireless local area network (WLAN), wireless personal area network (WPAN). You can. In some embodiments, the baseband circuit 404 may support communication using both the high frequency band and the low frequency band. An embodiment in which the baseband circuit 404 is configured to support radio communication of two or more radio protocols can be referred to as a multimode baseband circuit.

The RF circuit 406 can use electromagnetic radiation modulated via a non-solid medium to enable communication with a wireless network. In various embodiments, the RF circuit 406 may include switches, filters, amplifiers, etc. to facilitate communication with the wireless network. The RF circuit 406 may include a received signal path that may include a circuit that downconverts the RF signal received from the FE circuit 408 and supplies the baseband signal to the baseband circuit 404. The RF circuit 406 may also include a transmit signal path that includes a circuit for upconverting the baseband signal provided by the baseband circuit 404 and providing the RF output signal to the FE circuit 408 for transmission.

In some embodiments, the RF circuit 406 may include a received signal path and a transmitted signal path. The received signal path of RF circuit 406 may include mixer circuit 406a, amplifier circuit 406b and filter circuit 406c. The transmission signal path of RF circuit 406 may include filter circuit 406c and mixer circuit 406a. The RF circuit 406 may also include a mixer circuit 406a for the received signal path and a composite circuit 406d for synthesizing the frequencies used by the transmitted signal path. In some embodiments, the mixer circuit 406a of the received signal path may be configured to downconvert the RF signal received from the FE circuit 408 based on the combined frequency provided by the combined circuit 406d. The amplifier circuit 406b may be configured to amplify the down-converted signal, and the filter circuit 406c may be configured to remove unwanted signals from the down-converted signal to generate an output baseband signal. It may be a low-pass filter (LPF) or a band-pass filter (BPF). The output baseband signal may be fed to the baseband circuit 404 for further processing. In some embodiments, the output baseband signal may be a zero frequency baseband signal, but this is not a requirement. In some embodiments, the mixer circuit 406a of the received signal path may include a passive mixer, but the scope of the embodiments is not limited to this point.

In some embodiments, the mixer circuit 406a of the transmit signal path upconverts the input baseband signal based on the combined frequency provided by the combined circuit 406d to generate the RF output signal of the FE circuit 408. It may be configured. The baseband signal may be provided by the baseband circuit 404 and filtered by the filter circuit 406c. The filter circuit 406c may include a low pass filter (LPF), but the scope of the embodiments is not limited to this point.

In some embodiments, the receiver circuit path mixer circuit 406a and the transmit signal path mixer circuit 406a may include two or more mixers, which may be arranged for orthogonal down-conversion or up-conversion, respectively. In some embodiments, the mixer circuit 406a of the received signal path and the mixer circuit 406a of the transmitted signal path may include two or more mixers and may be arranged for image rejection (eg, Hartley image rejection). In some embodiments, the mixer circuit 406a of the received signal path and the mixer circuit 406a of the transmitted signal path may be arranged for direct down-conversion or direct up-conversion, respectively. In some embodiments, the receive signal path mixer circuit 406a and the transmit signal path mixer circuit 406a may be configured for superheterodyne operation.

In some embodiments, the output baseband signal and the input baseband signal may be analog baseband signals, but the scope of the embodiments is not limited to this point. In some alternative embodiments, the output baseband signal and the input baseband signal may be digital baseband signals. In such an alternative embodiment, the RF circuit 406 may include an analog-to-digital converter (ADC) and a digital-to-analog converter (DAC) circuit, and the baseband circuit 404 is a digital base that communicates with the RF circuit 406. It may include a band interface.

In some dual-mode embodiments, separate wireless IC circuits may be provided to process the signals in each spectrum, but the scope of the embodiments is not limited to this.

In some embodiments, the synthesis circuit 406d may be a fractional N synthesizer or a fractional N / N + 1 synthesizer, but the scope of the embodiments is not limited to this when other types of frequency synthesizers are suitable. .. For example, the synthesis circuit 406d may be a synthesizer including a phase-locked loop including a delta-sigma synthesizer, a frequency multiplier, or a frequency divider.

The synthesis circuit 406d may be configured to synthesize the output frequencies used by the mixer circuit 406a of the RF circuit 406 based on the frequency input and the divider control input. In some embodiments, the synthesis circuit 406d may be a fractional N / N + 1 synthesizer.

In some embodiments, the frequency input may be provided by a voltage controlled oscillator (VCO), but this is not a requirement. The divider control input may be provided by either the baseband circuit 404 or the application processor, depending on the desired output frequency. In some embodiments, the divider control input (eg, N) may be determined from the lookup table based on the channel indicated by the application processor.

The stiffness circuit 406d of the RF circuit 406 may include a divider, a delay lock loop (DLL), a multiplexer and a phase accumulator. In some embodiments, the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to split the input signal by N or N + 1 (eg, based on carryout) to provide a fractional split ratio. In some exemplary embodiments, the DLL may include a set of series, adjustable delay elements, phase detectors, charge pumps and D-type flip-flops. In such an embodiment, the delay elements may be configured to divide the VCO period into Nd packets of equal phase, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback so that the total delay through the delay line is 1 VCO cycle.

In some embodiments, the synthesis circuit 406d may be configured to generate a carrier frequency as the output frequency. On the other hand, in another embodiment, the output frequency may be a multiple of the carrier frequency (for example, twice the carrier frequency and four times the carrier frequency), and carriers a plurality of signals having a plurality of different phases with respect to each other. It may be used with orthogonal generator and divider circuits to produce at frequency. In some embodiments, the output frequency may be the LO frequency (fLO). In some embodiments, the RF circuit 406 may include an IQ / polar converter.

The FE circuit 408 may include a received signal path, which operates on RF signals received from one or more antennas 410, amplifies the received signal, and further processes the amplified version of the received signal. May include circuits configured to provide for RF circuit 406. The FE circuit 408 may also include a transmit signal path, which amplifies the signal for transmission provided by RF circuit 406 for transmission by one or more of one or more antennas 410. It may include a circuit configured as such. In some embodiments, the FE circuit 408 may include a TX / RX switch for switching between transmit mode operation and receive mode operation. The FE circuit 408 may include a received signal path and a transmitted signal path. The received signal path of the FE circuit 408 may include a low noise amplifier (LNA) that amplifies the received RF signal and supplies the amplified received RF signal as an output (eg, to RF circuit 406). The transmit signal path of FE circuit 408 includes a power amplifier (PA) for amplifying an input RF signal (eg, provided by RF circuit 406) and (eg, by one or more of one or more antennas 410). It may include one or more filters that generate an RF signal for the next transmission.

FIG. 5 shows an Ethernet controller 500 according to some embodiments. The Ethernet controller 500 may be implemented in the electronic device circuit 300 to provide a wired connection. For example, when the electronic device circuit 300 is used in the CN device 204, MeNB 208 or SeNB 212 to communicate via the SI or X2 interface for communicating via the SI or S5 / S8 interface or the CN device 204, Ethernet. Controller 500 may be used.

The Ethernet controller 500 may include a host interface 512 for coupling the Ethernet controller 500 to the host platform. In some embodiments, the host interface 512 may be a bus interface for coupling with a serial expansion bus, such as a peripheral component interconnect express (PCIe) bus. In some embodiments, the host interface 512 is a PCIe endpoint with single route input / output virtualization (SR-IOV) that allows isolation of PCIe resources for manageability and performance reasons. Good. This allows different virtual machines in the virtual environment to share a single PCIe hardware interface. In other embodiments, the host interface 512 may be a PCIe endpoint with multiple route I / O virtualization that allows the PCIe bus to share resources between different virtual machines on different physical machines. ..

The Ethernet controller 500 may include a queue management and scheduling (QMS) circuit 516. The QMS circuit 516 (also called a network or packet scheduler) may employ a queuing / scheduling algorithm to control the transmission and reception of packets by the Ethernet controller 500. The QMS circuit 516 may manage the sequence of network packets in the transmit and receive queues of the Ethernet controller 500. In some embodiments, the QMS circuit 516 may include a plurality of different queues, each queue holding one flow of packets according to configured packet classification rules. For example, a packet may be divided into flows according to its source and destination IP addresses, quality of service requirements, and the like. In some embodiments, the QMS circuit 516 may be used by the Ethernet controller 500 to perform receiver scaling and spread incoming packets across the available processing cores of the host platform. The QMS circuit 516 is an intelligent offload that places incoming packets directly on the correct core to avoid directing the packet to the available processing core, even if another core is running the application that is the target of the packet. Further may provide flow direction functions, including.

The Ethernet controller 500 may further include a protocol acceleration / offload (A / O) circuit 520. The protocol A / O circuit 520 may offload processing of a particular protocol or function of a particular protocol from the host processor. For example, in some embodiments, protocol A / O circuit 520 may include a TCP offload engine that offloads TCP / IP stack processing from the host platform to the Ethernet controller 500. This can be particularly useful for high speed network interfaces such as Gigabit Ethernet and 10 Gigabit Ethernet. Offloaded processing includes operations related to TCP connection directivity, such as transport layer connection establishment, received packet acknowledgment, checksum and sequence number calculation, sliding window calculation, and transport layer connection termination. Good.

In some embodiments, the protocol A / O circuit 520 performs a mobile proxy transport layer operation to provide expedient access to the link in the high frequency band, as described in more detail herein. Can be facilitated.

The Ethernet controller 500 may further include a traffic classifier 524. The traffic classifier 524 can implement a process of classifying traffic into multiple traffic classes according to various parameters (eg, port number, protocol, etc.). Each traffic class may be treated differently to distinguish the services provided by the Ethernet controller 500.

The Ethernet controller 500 may further include a media access controller 528 that performs MAC layer operations for the Ethernet controller 500, for example using carrier sense multiple access (CSMA / CD) protocol. The media access controller 528 may include a plurality of full-duplex Ethernet MAC ports, which may be configured to operate at different speeds, for example 40 Gb / s, 10 Gb / s, 1 Gb / s.

The Ethernet controller 500 may further include a PHY 532 for performing Ethernet PHY layer operations. In some embodiments, the PHY 532 is considered an interface that is directly connected to a communication medium (eg, a backplane, a directly connected twin axial copper cable assembly), or an Ethernet® interface (possibly an external PHY). It may include an interface via). The PHY 532 may interface between the analog domain of Ethernet line modulation and the digital domain of link layer packet signaling performed by the media access controller 528. In some embodiments, the PHY circuit comprises a multi-rate medium attachment unit interface (MAUI) that can be considered for operation and multiple different link speeds (eg, 40 Gb / s, 10 Gb / s, 1 Gb / s or 100 Mb / s). It's fine.

The Ethernet controller 500 may further include an in-band management circuit 536 with a controller or processor performing various on-chip management functions. The in-band management circuit 536 may interface with the off-chip management controller via the system management bus (SMBus), interface with the network controller sideband interface (NC-SI), or, for example, the management component transport. It may interface with the connection of host interface 512 that communicates via PCIe using protocol (MCTP).

The in-band management circuit 536 may include a baseboard management controller or built-in management processor unit that handles management tasks that are performed by the Ethernet controller but not by other circuits (eg, Ethernet device drivers). In some embodiments, these missions perform part of a power-on sequence, process AQ commands, initialize ports, data center bridge function exchange (DCBX), and more. It may include participating in various fabric configuration protocols such as Link Layer Discovery Protocol (LLDP) and processing configuration requests received by the management interface.

In an embodiment in which the electronic device circuit 300 incorporates the Ethernet controller 500, the PHY 532 may be incorporated into the transmit and receive circuit 312 (and, if possible, the media interface circuit 324), with the other components of the Ethernet controller 500 being the control circuit 308. May be incorporated into.

FIG. 6 shows a computing device 600 according to some embodiments.

The computing device 600 may include a platform circuit 604 coupled with an electronic device circuit 608.

The electronic device circuit 608 may include circuits similar to or substantially interchangeable to the electronic device circuit 300.

Platform circuit 604 may include processing circuit 612 coupled with memory / storage 616. The processing circuit 604 is any type or set of configurable or non-configurable circuits designed to perform basic arithmetic, logical, control or input / output operations specified by computer program instructions. May include alignment. The processing circuit 604 may include one or more single-core or multi-core processors and may include any combination of general purpose and dedicated processors. In some embodiments, the processing circuit 604 is an application processor, communication processor, microprocessor, ASIC, reduced instruction set computer (RISC), DSP, coprocessor, combined logic circuit, controller (eg, memory, bridge, bus). Etc. may be included.

The processing circuit 604 may be coupled with memory / storage 616 and is configured to execute instructions stored in memory / storage 616 to enable various applications or operating systems running on device 600. Good.

The memory / storage circuit 616 holds digital contents (data, instructions, etc.) temporarily, temporarily, semi-permanently or permanently, and stores the digital contents when a predetermined event occurs. It may include any type or combination of configurable or non-configurable circuits that can be provided to another circuit component (eg, processing circuit 612). The memory / storage circuit 616 includes, but is not limited to, random access memory (RAM) (including, for example, static RAM (SRAM), dynamic RAM (RAM)), read-only memory (ROM) (eg, electrically erasable program). (Including possible ROM (EEPROM)), cache (LI, L2, etc.), buffer, etc. may be included.

The platform circuit 604 can generally perform upper layer functions related to the platform on which the device is mounted, and the electronic device circuit 608 generally performs lower layer functions related to communication over the appropriate network interface. can do.

Overall, platform circuits 604 and electronic device circuits 608 perform tasks or activities for users with an operating system 620 that manages computer hardware and software resources and provides various services to computer programs. One or more of providing an application 624 for, and a communication protocol stack 628 for communicably connecting a device module (eg, application 624) with a module implemented by another device over a network. You may implement the module.

The communication protocol stack 628 (or simply "stack 628") may include layers realized by the electronic device circuit 608 as described above, such as a PHY layer, a MAC layer, an RLC layer, a PDCP layer, and an RRC layer. The stack 628 may further include layers realized by the platform circuit 604, such as an internet layer, a transport layer, an application layer, and the like. The application layer may include communication protocols and interface methods used to handle communications transmitted over the IP network.

The transport layer can establish host-to-host data transfer channels and manage data exchange in a client-to-server or peer-to-peer networking model. The transport layer can include TCP or User Datagram Protocol (UDP). The TCP function, for example, establishes a connection using "3-way handshake" (SYNchronize; SYNchronize-ACKnowledge; ACKnowledge), acknowledges the packet when the packet is received at the far end, and eventually the message flow between endpoints. It may include the addition of a protocol load, the calculation of checksums and sequence numbers (again, the burden on the general-purpose CPU to execute), the sliding window calculation for packet acknowledgment and congestion control, and the termination of the connection.

The Internet layer can refer to the operations used to transport datagrams (packets) from outgoing hosts across network boundaries. The Internet layer may include, for example, an IP protocol (eg, IP version 4, IP version 6, etc.), an IP security protocol (eg, IPsec), and the like.

The control circuit used to perform the access network control operation is described above in FIG. 3 as being realized in an electronic device circuit. However, in some embodiments, some or all of the control circuitry may be implemented in the platform circuitry, eg platform circuitry 604. Further, the function of a particular layer is described as being realized by either the platform circuit 604 or the electronic device circuit 608, but in other embodiments, the function may be performed by the other circuit. For example, the transport layer function, including the function performed by the mobile proxy 206, may be performed by the platform circuit 604 or by the protocol A / O circuit of the electronic device circuit 608.

In an embodiment in which the computing device 600 is a CN device such as the CN device 204, the computing device 600 may implement a mobile proxy such as the mobile proxy 206. The mobile proxy may include modules of OS 620, application 624 or stack 628. In some embodiments, the mobile proxy may additionally / optionally include circuit elements of the platform circuit 604 or electronic device circuit 608 to perform the operations described herein.

In some embodiments, the computing device 600 may also include an input / output interface 632, a sensor 636 and a display (s) 640, especially if the computing device 600 is a UE (eg, UE 216). In various embodiments, the I / O interface 632 is designed to allow one or more user interfaces designed to allow user interaction with the system, or peripheral device interaction with the system. Peripheral device interface may be included. User interfaces may include, but are not limited to, physical keyboards or keypads, touchpads, speakers, microphones, and the like. Peripheral interface may include, but is not limited to, a non-volatile memory port, a universal serial bus (USB) port, an audio jack and a power interface.

In various embodiments, the sensor 636 may include one or more sensing devices that determine the environmental conditions and / or location information associated with the system. In some embodiments, the sensor may include, but is not limited to, a gyro sensor, an accelerometer, a proximity sensor, an ambient light sensor and a positioning unit. Also, the positioning unit may be part of a baseband circuit or RF circuit or interact with a baseband circuit or RF circuit to communicate with components of a positioning network (eg, a Global Positioning System (GPS) satellite). You can do it.

In various embodiments, the display 640 may include a display (eg, a liquid crystal display, a touch screen display, etc.).

FIG. 7 shows the interaction of modules in stacks of different devices, according to some embodiments. In particular, FIG. 7 shows a mobile proxy 206 in a CN device 204 coupled with an application server 708 and an eNB (eg MeNB 208 and SeNB 212). The eNB 208/212 may be further coupled with the UE 216.

Each component of FIG. 7 may include a module of a communication protocol stack, such as stack 628. In particular, the mobile proxy 206 may include a TCP module 720, an IP module 724, a transport IP network module 728 and a transport radio air interface module 732. The application server 708 may include an application layer module 736, a TCP module 740, an IP module 744 and a transport IP network module 748. The eNB 208/212 may include a transport radio air interface module 752. The UE 216 may include an application layer module 756 and a transport radio air interface module 760.

The component modules of FIG. 7 can be tuned to facilitate the transmission of data between the application layer module 736 of the application server 708 and the application layer module 756 of the UE 216.

In general, TCP modules 720 and 740 can perform transport layer operations and manage transport connections between the two modules. The IP modules 724 and 744 can perform Internet layer operations. The transport IP network modules 728,748 can perform L2 (link layer) and LI operations. The transport radio air interface module 732,752,760 can perform RRC-LI operation.

The mobile proxy 206 can use the TCP module 720 to maintain a TCP layer interface with the core network. The TCP operations performed by the TCP modules 720, 740 may include, but are not limited to, operations related to the management of transport layer connections, such as connection establishment, connection termination, resource usage, and data transfer. With respect to data transfer, TCP modules 720,740 provide ordered data transfer (the receiving module rearranges the packets according to the sequence number) and retransmitted lost packets (lack of response or negative response is the transmitting module). Can provide flow control (to limit and guarantee the speed at which the sender transfers data) and congestion control.

TCP rate control operations that can include flow or congestion control between TCP module 720 and TCP module 740 are as follows. The TCP module 720 can determine the data rate of the transport network between the TCP module 720 and the TCP module 740. The TCP module 720 can also determine the capacity of the radio access network, eg, the capacity of the connection between the transport radio air interface module 752 and the transport radio air interface module 760. If the data rate of the transport network is higher than the capacity of the wireless access network, the TCP module 720 notifies the TCP module 740 of the application server 708 to reduce the data rate of packets transmitted over the transport network. Therefore, feedback such as, for example, a transport layer data transfer management message can be generated, whereby the data rate of the transport network can be reduced to less than or equal to the capacity of the wireless access network.

In some embodiments, the transport layer data transfer management message may include a TCP message that includes a negative response (NACK). NACK may be included in the TCP message even if the IP packet is successfully received by the TCP module 720. In other embodiments, the mobile proxy negatively responds to a successfully received transmission in other ways, such as non-transmission of an acknowledgment (this occurrence can be interpreted as a negative response by the sending entity). You can do it.

Since the mobile proxy 206 can use various access network control operations such as buffering and traffic shaping, it is possible to avoid fluctuations in the radio access network capacity due to on / off of the mmWave link at the transport layer. In some embodiments, the access network control operation may be performed by the transport radio air interface module 732. The mobile proxy 206 can use the transport radio air interface module 732 to manage the connection between the mobile proxy 206 and the UE 216 (via the transport radio air interface module 760). Data can be transferred over this connection via the Uu and X2 interfaces according to the schedule developed by the mobile proxy or MeNB 208.

FIG. 8 is a schematic diagram of traffic and feedback flow via mobile proxy 206, MeNB 208 and UE 216 according to some embodiments. In particular, FIG. 8 shows the scheduling logic 804 coupled with the communication logic 806 in the mobile proxy 206 and the scheduling logic 808 coupled with the communication logic 810 in the MeNB 208.

The scheduling logic and communication logic may be logic that is at least partially implemented in the hardware of the control circuit to perform the scheduling and communication operations described herein. In some embodiments, the scheduling logic 804 and the communication logic 806 may include at least the components of the TCP module 720 and the transport radio air interface module 732. The scheduling logic 808 and the communication logic 810 may include at least the components of the transport radio air interface module 752.

In embodiments where the scheduling and communication logic is implemented in the wireless communication circuit 400, the scheduling logic is at least partially by a baseband processor (eg, 4G baseband processor 404c or 5G baseband processor 404d), memory / storage 404g or CPU404e. The communication logic may be implemented at least partially by the baseband processor 404, memory / storage 404g or RF circuit 406. In embodiments where the scheduling and communication logic is implemented on the Ethernet controller 500, the scheduling logic may be implemented at least partially by the QMS circuit 516 or protocol A / O circuit 520, and the communication logic may be implemented by the QMS circuit 516, protocol A. It may be implemented at least partially by the / O circuit 520, traffic classifier 524, media access controller 528 or PHY532. In other embodiments, the scheduling and communication logic may be implemented, at least partially, in other hardware such as processor 612 of platform circuit 604 or memory / storage 616.

Scheduling logic 804,808 can provide two levels of scheduling. In various embodiments, scheduling of traffic through the air interface may be performed by scheduling logic 804 or scheduling logic 808. The communication logic 806 can receive incoming traffic 812 from the network (eg, from the application server 708). Communication logic 806 can determine that the traffic 812 includes traffic associated with one or more QoS classes.

QoS classes can enable the ability to provide different priorities for different applications, users or data flows, or to guarantee a certain level of performance for a data flow. This makes it possible for QoS classes to guarantee specific performance characteristics such as bit rate, delay, jitter, packet dropping probability, and bit error rate.

The communication logic 806 can distinguish the traffic 812 based on each QoS class. In some embodiments, the communication logic 806 can determine the QoS class based on packet headers, source or destination addresses, and the like.

In some embodiments, the communication logic 806 can direct certain QoS class traffic to the associated buffer of buffer 814. Thus, each QoS class may have a corresponding buffer for buffering traffic prior to transmission to the eNB.

The buffer 814 can be implemented in the memory / storage of the communication or platform circuit.

Scheduling logic 804 can provide feedback 816 for each QoS class of traffic. Feedback 816 may be a transport layer data transfer management transmission used to regulate traffic over the core network using TCP rate control. In some embodiments, the feedback 816 may be intended for additional / alternative transport layer data transfer management.

The scheduling logic 804 may transmit control information 820 to the scheduling logic 808. The control information 820 may include a buffer state and QoS parameters associated with the QoS class.

Although FIG. 8 shows a message flowing directly to and from the scheduling logics 804 and 808, it will be appreciated that the connection may be a logical connection that can flow through the communication logics 806 and 810. Therefore, the scheduling logic may send and receive messages to and from other network components via the communication logic.

In an embodiment in which scheduling is performed by mobile proxy 206, control information 820 may include notification of scheduling decisions in scheduling logic 804.

Scheduling logic 808 may receive feedback from UE 216 or SeNB 212 that provides information about the capacity of the links provided by MeNB 208 and SeNB 212. Feedback 824 regarding the capacity of the second link provided by SeNB 212 may be received from UE 216 or SeNB 212.

Scheduling logic 808 may determine the link capacitance based on the information provided in feedback 824. In some embodiments, the link capacitance may include statistical information about the rate at which IP packets are successfully delivered to UE 216 over the first and second links. In some embodiments, this statistic may be based on tracking the acknowledgment and negative response of IP packets delivered to UE 216 at a given rate for a given channel state. The link capacitance may include predictive information based on the current channel state and operating characteristics of the first and second links (eg, average dropout frequency of the second link, average connection reestablishment time, etc.).

Scheduling logic 808 may send a link capacity report (which may include delivery rate statistics) to scheduling logic 804 in feedback 828. The link capacitance may be used by the scheduling logic 804 to determine the schedule (in embodiments where the mobile proxy 206 makes this determination) or for TCP rate control operations.

In an embodiment in which scheduling is performed on the MeNB 208, the scheduling logic 808 may transmit a notification of the scheduling decision of the scheduling logic 808 in the feedback 828.

In various embodiments, the scheduling decision performed by the scheduling logic 804 or 808 is that the traffic is delivered via the first link provided by MeNB 208 or via the second link provided by SeNB 212. You may decide whether or not to be directed to. In general, this decision can be made based on the QoS class of traffic and the capacity of the radio link.

In some embodiments, the scheduling logic 804 or 808 may predict the capacity of the first and second links based on the mobility of the UE 216.

In some embodiments, the scheduling logic 804 or 808 is based on the capacity of the links associated with one or more other UEs that are believed to be in close proximity to the UE 216, the capacity of the first and second links. May be predicted. For example, if the second UE is considered to be in close proximity to the UE 216, the scheduling logic 804 or 808 may determine that the UE's links are strongly correlated to the predetermined link capacitance of the second UE. Based on this, the link capacity of the UE 216 may be indicated.

In various embodiments, the links provided by SeNB 212 may utilize idle or active states. If the link is idle for an extended period of time, the link capacity measurements used by the scheduling logic can become outdated. Therefore, FIG. 9 shows an embodiment of reporting procedure 900 that can be used to provide updated link capacity measurements to the scheduling logic. The operations described in reporting procedure 900 may be performed by a control circuit implemented in each device, such as control circuit 308.

In 904, reporting procedure 900 may include the control circuit of UE 216 detecting a predetermined reporting event. In some embodiments, the predetermined reporting event may be the expiration of a timer set to facilitate periodic reporting. The reporting period may be chosen to balance the power consumption of the UE 216 with the accuracy of the channel state.

In some embodiments, the predetermined report event may be, for example, the reception of a report instruction from MeNB 208. The report instruction may be received by the UE 216 over the anchor connection when the UE 216 is active or when the mmWave connection is periodically activated.

In some embodiments, the given reporting event may or may be based on the detection of environmental conditions that may be associated with changes (or expected changes) in the state of the mmWave link. The presence or detection of certain environmental conditions may mean that the UE 216 needs to report the status of the mmWave link, or perhaps increase or decrease the frequency of reporting. Some environmental conditions include UE mobility, quality changes on another wireless communication link, UE location (eg, UE is located in a physically congested environment, eg surrounded by skyscrapers, and in line of sight. (If there is a possibility of breaking the mmWave link), or may include an increase or change in precipitation / pressure level. Such environmental conditions may be detected by a sensor or application on the UE 216.

At 908, reporting procedure 900 may further include invoking the mmWave interface and performing measurements. In an embodiment in which the mmWave interface is invoked, the operation at 908 may be to keep the mmWave interface active.

The measurements performed at 908 may include measuring signals transmitted by the SeNB, such as reference signals. The signal used as the basis of the measurement may include, for example, a reference signal such as a cell-specific reference signal (CRS) or a channel state information (CSI) reference signal. The CRS may be a pilot symbol inserted at both time and frequency in all downlink subframes and cells that support physical downlink shared channel (PDSCH) transmission. Such pilot symbols can provide estimates of the channel at a given position within the subframe. The UE 216 may interpolate the measurement results to estimate channels over any number of subframes.

The UE 216 may measure the parameters of the received signal, such as, for example, the reference signal reception power (RSRP) and the reference signal reception quality (RSRQ). RSRP can be defined as a linear average for the power contribution of the resource element for carrying the cell-specific reference signal within the measured frequency band considered. The RSRQ can be based on the RSRP and Received Signal Strength Indicator (RSSI) and the average total received power observed only in the OFDM symbol containing the reference signal for antenna port 0 within the measurement bandwidth over N resource blocks. Measure. RSRP can be defined as the ratio of NxRSRP / KSSI.

The UE 216 may transmit a report 912 containing the results of the measurements made in 908.

At 916, UE 216 may idle its mmWave interface.

Upon receiving the report 912, the MeB208 may estimate the link capacity of the links provided by the SeNB at 920. In some embodiments, the link capacitance estimation at 920 may further estimate the link capacitance of the primary link provided by MeNB 208 in the low frequency band. Estimates of primary link capacity may be based on measurement reports sent periodically to MeNB 208 over the primary link.

The reporting procedure 900 may further include detecting a predetermined reporting event by the MeNB 208 at 924. The predetermined report event 924 may be periodic or event driven, as described above for 904.

Upon detecting a predetermined report event (924), the MeNB 208 may send the report 928 to the mobile proxy 206.

FIG. 9 schematically shows a report 928 (also called a link capacity report message). Report 928 may include a data rate field 936 for communicating the link capacitance state of the wireless link (eg, link 220 or 224) to the user equipment (UE). The link capacity state may include statistical information about the rate at which IP packets are successfully delivered to the UE over each link.

Report 928 may further include a UE identifier field 932 for communicating the UE identifier. The identifier may be the IP address assigned to the UE, or another type of network identifier for the UE. In various embodiments, report 928 may include a dropout instruction field 940 for communicating information about the dropout frequency of the link (eg, link 220 or 224). The dropout instruction field 940 may be for communicating information about the average dropout frequency of the link.

In some embodiments, report 928 may further include a connection reestablishment time indicator field 944 for communicating information about the connection reestablishment time of the link (eg, link 220 or 224). The connection reestablishment time indicator field 944 may be for communicating information about the average connection reestablishment time of the first link.

In some embodiments, report 928 may further include a second data rate field 948 for communicating the link capacitance state of another radio link. For example, when the data rate field 936 communicates the link capacity state of the link 220, the second data rate field 948 may communicate the link capacity state of the link 224.

In some embodiments, report 928 may be a non-access layer message.

FIG. 10 shows a convenient access operation 1000 according to some embodiments. The expedient access operation 1000 may be a downlink-triggered mmWave link activation and access process with scheduling performed on the MeNB 208. In various embodiments, the operation of FIG. 10 may be performed, generated or controlled by the communication or platform circuit components of each device set forth in FIG.

The expedient access operation 1000 (hereinafter “operation 1000”) may begin with the mobile proxy 206 receiving UE traffic from the transmitting entity over the core network. For example, mobile proxy 206 may receive UE traffic from application server 708. The mobile proxy 206 may buffer UE traffic in memory circuits such as buffer 814, memory / storage 404g, and QMS circuit 516 at 1004.

The mobile proxy 206 may generate a transport layer data transfer management message transmission to the transmitting entity at 1004. The transport layer data transfer management message is for any of the TCP operations described above, such as ordered data transfer, loss packet retransmission, error-free data transfer, and flow / congestion control. Good. In some embodiments, the transport layer data transfer management message may include a TCP ACK / NACK message. For the purposes of this specification, the transmission of transport layer data transfer management messages, along with other transport layer data transfer management messages used for TCP rate control, is associated with successful or unsuccessful reception of IP packets. It may be for the purpose of doing so. However, in some embodiments, the transmission at 1004 may be used for TCP rate control.

The mobile proxy 206 may send a notification of UE traffic to the MeNB 208 in 1008. Notifications may include notifications of traffic type, size or QoS requirements.

Operation 1000 may include the MeNB 208 scheduling traffic at 1012. In particular, the MeNB 208 may schedule traffic via a first link provided by the MeNB 208 in the low frequency band or a second link provided by the SeNB 212 in the high frequency band. In some embodiments, the MeNB 208 may schedule a first portion of traffic on the first link and a second portion of traffic on the second link.

The MeNB 208 may schedule traffic over the first and second links based on the estimated link capacity. The estimation of link capacitance may be performed in the same manner as described above with respect to FIG. The MeNB 208 may further schedule traffic over the first and second links based on the type, size or QoS requirements of the traffic.

After creating the schedule at 1012, the MeNB 208 may send a notification of the scheduling decision to the mobile proxy 206 at 1016.

If the scheduling decision involves sending at least a portion of the traffic over the second link provided by the SeNB 212, the MeNB 208 will send an instruction to the UE 216 to wake up the MMWave air interface at 1020. Good. Instructions to wake up the mmWave interface may be transmitted via the first link provided by MeNB 208. The UE 216 may wake up its mmWave air interface and start synchronizing with the mmWave SeNB 212 at 1028.

If the scheduling decision involves sending at least a portion of the traffic over the second link provided by the SeNB 212, the mobile proxy 206 will download the first portion of the UE traffic to the SeNB 212 at 1024. You can do it.

If the scheduling decision involves sending at least a portion of the traffic over the first link provided by the MeNB 208, the mobile proxy 206 may download some of the UE traffic to the MeNB 208 at 1032. ..

Operation 1000 may include data transmission via the air interface at 1036.

Data transmission may be via a first or second link that matches the scheduling decision made by MeNB 208. Operation 1000 may further include at 1040 the UE 216 providing updates to the link capacity of the second link. The MeNB 208 may provide the mobile proxy 216 with updated link capacity for both the first and second links at 1044.

Upon receiving the updated UE link capacity, the mobile proxy 206 may perform a TCP rate control operation at 1048.

FIG. 11 is a flowchart showing the TCP rate control operation 1100 according to some embodiments.

The rate control operation 1100 (hereinafter "operation 1100") may be performed by components of the mobile proxy 206, including, for example, scheduling logic 804, communication logic 806 and TCP module 720.

At 1104, operation 1100 may include receiving UE link capacitance from MeNB 208. The UE link capacitance may be received in feedback transmitted from the MeNB 208 to the mobile proxy 206 via the control plane. The UE link capacity may include measurements or other parameters (eg, delivery rate statistics) related to the link capacity of the link provided to the UE 216 by MeNB 208 and SeNB 212.

At 1108, operation 1100 may include determining the transport network data rate and the RAN data rate.

The transport network data rate may correspond to the rate at which TCP traffic is delivered from TCP module 740 to TCP module 720. The transport network data rate may be determined by the mobile proxy 206 tracking the rate at which IP packets reach the mobile proxy 206.

The RAN data rate may correspond to the rate at which UE traffic is delivered from the transport radio air interface module 752 (of MeNB 208 and SeNB 212) to the transport radio air interface module 760. The RAN data rate may be determined based on the UE link capacity report provided in the feedback from MeNB 208.

Operation 1100 may include determining at 1112 whether the transport network data rate is greater than the RAN data rate.

If it is determined in 1112 that the transport network data rate is not greater than the RAN data rate, operation 1100 may loop back to 1104 to continue monitoring each data rate.

If in 1112 it is determined that the transport network data rate is greater than the RAN data rate, operation 1100 may include in 1116 that the mobile proxy reduces the transport network data rate. In some embodiments, the mobile proxy 206 may use TCP rate control procedures to reduce the transport network data rate. In various embodiments, the TCP rate control procedure may include procedures related to flow control or congestion control.

Flow control is typically used to prevent the sender from transmitting data faster than the TCP receiver can reliably receive and process the data. In this embodiment, the mobile proxy 206 may implement TCP flow control using a sliding window. Upon receiving traffic from the application server 708, mobile proxy 206 may determine the amount of additional data it wants to buffer for the connection. The mobile proxy 206 may then send a determined amount of instructions to the application server 708 in the receive window field. The application server 708 may only be allowed to send that amount of data before receiving the acknowledgment and receive window update from the mobile proxy 206. If the mobile proxy 206 wants to stop the data transmission of the application server 708, the mobile proxy 206 may transmit a zero value in the receive window field.

The mobile proxy 206 may, as an addition / alternative, use congestion control procedures to control the rate of data entering the transport network. In some embodiments, the mobile proxy 206 may send a negative response (or lack of an acknowledgment) to the application server 708. The application server 708 may receive such a negative response (or lack of an acknowledgment) and presume that the data rate of the transport network is too high. As a result, the application server 708 can reduce the rate at which packets are sent to the mobile proxy 206.

In various embodiments, the mobile proxy 206 may provide congestion control using any of a plurality of TCP congestion avoidance algorithms. Such TCP congestion avoidance algorithms may include TCP Tahoe and Reno, TCP Vegas, TCP New Reno, TCP Hybla, TCP BIC, TCP CUBIC, Agile-SD TCP, TCP Westwood +, or Compound TCP.

FIG. 12 shows the expedient access operation 1200 according to some embodiments. The expedient access operation 1200 may be a downlink-triggered mmWave link activation and access process with scheduling performed on the mobile proxy 206. Unless otherwise stated, the operation of FIG. 12 may be performed, generated or controlled by the communication or platform circuit components of each device described in FIG.

The expedient access operation 1200 (hereinafter "operation 1200") may start with the mobile proxy 206 receiving data from the transmitting entity over the core network. For example, mobile proxy 206 may receive traffic from application server 708.

At 1204, the mobile proxy 206 may buffer UE traffic within the memory circuit and send a transport layer data transfer management message to the transmitting entity, similar to the process described above for operation 1004 of FIG.

Operation 1200 may include, at 1208, the mobile proxy 206 scheduling UE traffic via a first link provided by MeNB 208 or a second link provided by SeNB 212. Scheduling UE traffic in 1208 may be similar to scheduling UE traffic in 1012, except that scheduling is performed in mobile proxy 206 instead of MeNB 208.

After creating the schedule in 1208, the mobile proxy 206 may send a notification of the scheduling decision to MeNB 208 at 1212.

If the scheduling decision involves sending at least a portion of the traffic over the second link provided by the SeNB 212, the MeNB 208 sends an instruction to the UE 216 to wake up the mmWave air interface at 1216. Good. Instructions to wake up the mmWave interface may be transmitted via the first link provided by MeNB 208.

The UE 216 may wake up its mmWave air interface and begin synchronization with the mmWave SeNB 212 at 1228.

If the scheduling decision involves sending at least a portion of the traffic over the second link provided by the SeNB 212, the mobile proxy 206 may download some of the UE traffic to the SeNB 212 at 1220. ..

If the scheduling decision involves sending at least a portion of the traffic over the first link provided by the MeNB 208, the mobile proxy 206 may download some of the UE traffic to the MeNB 208 at 1224. ..

Operation 1200 may include data transmission via an air interface at 1232. Data transmission may be via a first or second link that matches the scheduling decision made by mobile proxy 206.

Operation 1200 may further include at 1236 the UE 216 transmitting a link capacitance update for the second link provided by the SeNB 212. The MeNB 208 may provide the mobile proxy 216 with updated link capacity for both the first and second links at 1240.

Upon receiving the updated UE link capacity, the mobile proxy 206 may perform a TCP rate control operation at 1244. The performance of the TCP rate control operation may be similar to that described above.

FIG. 13 shows the expedient access operation 1300 according to some embodiments. The expedient access operation 1300 may be an uplink-triggered mmWave activation and access procedure involving a direct connection between the SeB212 and the mobile proxy 206. Unless otherwise stated, the operation of FIG. 13 may be performed, generated or controlled by components of the control circuitry of each device described in FIG.

The expedient access operation 1300 (hereinafter "operation 1300") may start with the UE 216 sending an uplink traffic report to the MeNB 208 at 1304. The uplink traffic report can provide an indication of the need for the UE 216 to send uplink traffic. Uplink traffic may be destined for another device on the core network, such as application server 708. The uplink traffic report may include instructions on the type, size or QoS requirements of the uploaded traffic.

Operation 1300 may include at 1308 the MeNB 208 scheduling traffic. The MeNB 208 may schedule traffic via the first link provided by the MeNB 208 or the second link provided by the SeNB 212. The MeNB 208 may schedule traffic over the first and second links based on the estimated link capacity. The estimation of link capacitance may be performed in the same manner as described above with respect to FIG. The MeNB 208 may further schedule uplink traffic on the first and second links based on the type, size or QoS requirements of the traffic.

Operation 1300 may include, at 1312, the MeNB 208 transmitting a notification of the scheduling decision to the UE 216.

If at least a portion of the uplink traffic is transmitted over the second link, the UE 216 may activate its mmWave interface and initiate synchronization and access with the SeNB 212 at 1316.

Operation 1300 may further include at 1320 the UE 216 transmitting an uplink data transmission. Uplink data may be transmitted via first and second links that match the scheduling decision of MeNB 208.

If at least a portion of the uplink traffic is transmitted over the second link, operation 1300 may include in 1324 the SeNB 212 uploading at least a portion of the UE traffic to the mobile proxy 206.

If at least a portion of the uplink traffic is transmitted over the first link, operation 1300 may include in 1328 the MeNB 208 uploading at least a portion of the UE traffic to the mobile proxy 206. Operation 1300 may further include at 1332 the mobile proxy 206 buffering uplink traffic and scheduling transmissions in the core network.

As mentioned above, the mobile proxy 206 may include a TCP module 720 that acts as a TCP endpoint to terminate the transport layer. Therefore, when scheduling transmissions in the core network, the TCP module 720 may need to manage TCP connections over the core network. FIG. 14 shows a flowchart of TCP management operation 1400 for managing a TCP connection for sending uplink traffic over a core network to a destination such as, for example, an application server 708. The TCP management operation 1400 may be executed by the TCP module 720.

The TCP management operation 1400 may start at 1404 when the TCP module 720 receives the uplink traffic. Uplink traffic may be received from MeB208 or SeB212.

The TCP management operation 1400 may include in 1408 that the TCP module 720 establishes a TCP connection. The TCP connection may be established with other endpoints of the TCP connection, such as the TCP module 740.

Establishing a TCP connection may include a multi-step handshake process. In some embodiments, the handshake process is sometimes referred to as a 3-way handshake. The 3-way handshake may include the TCP module 720 performing an active open by sending a synchronization request (SYN) to the TCP module 740. The TCP module 720 may set the sequence number included in the synchronization request to a random value A. Upon receiving the synchronization request, the TCP module 740 may respond with a synchronization acknowledgment (SYN-ACK) message. The synchronization confirmation message may include an acknowledgment number (eg, A + 1) set 1 higher than the synchronization request sequence number, and the TCP module 740 may generate another random number B for the sequence number included in the synchronization acknowledgment message. You may choose. Upon receiving the synchronization confirmation message, the TCP module 720 may return an acknowledgment (ACK) to the TCP module 740. The acknowledgment may include a sequence number set in the acknowledgment number (eg A + 1) and may include an ACK number (eg B + 1) set one higher than the sequence number of the synchronous acknowledgment message. Following the 3-way handshake, both TCP module 720 and TCP module 740 may receive an acknowledgment of the connection and full-duplex communication may be established.

Operation 1400 may further include, at 1412, the TCP module 720 transferring data over an established connection. As described above, the data transfer may be performed using TCP functions such as ordered data transfer, loss packet retransmission, error-free data transfer, flow control, congestion control and the like.

Operation 1400 may further include at 1416 the TCP module 720 terminating the TCP connection. In some embodiments, the TCP connection may be terminated using a 4-way handshake.

If TCP module 720 wants to stop half of the connections, TCP module 720 may send a completion (FIN) message to TCP module 740. The TCP module 740 may acknowledge a FIN message with an acknowledgment (ACK) message and may transmit another FIN message. When the TCP module 720 receives the ACK message and the FIN message from the TCP module 740, the TCP module 720 may transmit the final ACK message, wait for a predetermined time, and terminate the TCP connection. In this way, the TCP connection can be reliably closed by both TCP endpoints.

FIG. 15 shows the expedient access operation 1500 according to some embodiments. The expedient access operation 1500 may be an uplink-triggered mmWave activation and access procedure involving an indirect connection between the SeNB 212 and the mobile proxy 206. Unless otherwise stated, the operation of FIG. 15 may be performed, generated or controlled by the platform or communication circuit components of each device described in FIG.

The expedient access operation 1500 (hereinafter referred to as "operation 1500") may include procedures similar to those of similar names disclosed and discussed with respect to FIG. In particular, the UE may send an uplink traffic report to the MeNB 208 at 1504. The MeNB 208 may schedule traffic at 1508 and send a scheduling decision notification to UE 216 at 1512. The UE 216 may activate its mmWave interface, synchronize with the SeNB 212 at 1516, and upload data transmissions over the first or second link at 1520.

Unlike the operation 1300, in the operation 1500, the SeNB 212 may not be able to directly transmit the uplink data to the mobile proxy 206. Therefore, operation 1500 may include, at 1524, the SeNB 212 uploading at least a portion of the UE traffic to the MeNB 208. Then, at 1528, the MeNB 208 may upload all of the UE traffic to the mobile proxy 206. Operation 1500 may further include, at 1532, mobile proxy 206 buffering uplink traffic and scheduling transmissions in the core network. This may be performed in the same manner as described above for 1332.

FIG. 16 shows an exemplary computer-readable storage medium 1604 suitable for use in storing instructions that cause an apparatus to perform a selected embodiment of the present disclosure in response to execution of an instruction by the apparatus. In some embodiments, the computer-readable storage medium 1604 may be non-temporary. As shown, the computer-readable storage medium 1604 may include programming instructions 1608. Programming instruction 1608 makes a device (eg, CN device 204, MeNB 208, SeNB 212, UE 216, or similar computing device) in response to execution of programming instruction 1608 through the present disclosure in connection with the expedient access of the mmWave link. It may be configured to allow any of the methods or elements described to be implemented. In some embodiments, programming instruction 1608 relates to traffic reporting, scheduling, buffering, rate control, link measurement / reporting, etc. performed by a control circuit or corresponding module in response to execution of programming instruction 1608. It may be configured to allow any (aspect) of the methods or elements described throughout the disclosure to be realized. In some embodiments, programming instruction 1608 may be provided essentially on a temporary computer-readable storage medium such as a signal 1604.

Any combination of one or more computer-enabled or computer-readable storage media may be utilized. Computer-enabled or computer-readable storage media can be, but are not limited to, for example, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, devices, or propagation media. More specific examples (non-limiting list) of computer-readable storage media are electrical connections with one or more wires, portable computer diskettes, hard disks, random access memory (RAM), read-only memory (ROM), Erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage, transmission media such as those that support the Internet or intranet, magnetic storage Can include. The program can be electronically captured, for example, via optical scanning of paper or other medium, then processed by compilation, interpretation or other suitable method as needed, and then stored in computer memory. As such, the computer-enabled or computer-readable storage medium may be paper or other suitable medium on which the program is printed. In the context of this document, computer-enabled or computer-readable storage media includes, stores, and communicates programs that are used by or attached to instruction-execution systems, devices or devices. It can be any medium that can propagate or transport. The computer-enabled storage medium may include a propagated data signal that embodies the computer-enabled program code in baseband or as part of a carrier wave. Computer-enabled program code may be transmitted using any suitable medium, including but not limited to wireless, wired, fiber optic cables, RF, and the like.

The computer program code for performing the operations of the present disclosure includes object-oriented programming languages such as Java (registered trademark), Smalltalk, and C ++, and conventional procedural programming languages such as the "C" programming language and similar programming languages. It may be described in any combination of one or more programming languages, including. The program code is entirely on the user's computer, or partially on the user's computer, or as a stand-alone software package, or partly on the user's computer and partly on the remote computer, or completely. May be run on a remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer or connected to an external computer via any type of network, including local area networks (LANs) and wide area networks (WANs). Good (eg, over the internet with an internet service provider).

The present disclosure will be described with reference to the flow charts or block diagrams of the methods, devices (systems) and computer program products according to the embodiments of the present disclosure. It will be understood that the combination of each block of the flowchart or block diagram with the blocks of the flowchart or block diagram can be realized by computer program instructions. Such computer program instructions may be provided to the processor of a general purpose computer, special purpose computer or other programmable data processor to manufacture the machine, thereby providing the processor of the computer or other programmable data processor. The instruction executed through the program creates a means for realizing the function / operation specified by the block of the flowchart or the block diagram.

Such computer program instructions may be stored on a computer-readable storage medium capable of causing a computer or other programmable data processing device to function in a particular manner, whereby the instructions stored on the computer-readable storage medium may be stored. , Generates a manufactured product that includes a command means that realizes the function / operation specified by the block in the flowchart or block diagram. Computer program instructions may be loaded into a computer or other programmable data processor to perform a series of operating steps on the computer or other programmable device to generate a computer implementation process, thereby causing the computer or other programmable device. An instruction executed on a programmable device provides a process for realizing a function / operation specified by a block in a flowchart or a block diagram.

Some examples are shown below.

Example 1 includes a device comprising a memory circuit and a processing circuit coupled to the memory circuit. The processing circuit is configured to receive traffic from the sending entity through the transport network traversing the core network, buffer the traffic into the memory circuit, and control the data rate of the transport network. To cause traffic to be sent from the core network to a first eNB (eg macro eNB (MeNB)) or a second eNB (eg small cell eNB (SeNB)) for subsequent transmission to the user equipment (UE). It is composed of. In some examples, the SeNB is configured to communicate with the UE using frequencies above 6 GHz (GHz).

Example 2 includes the device of Example 1. The processing circuit is configured to send a transport layer data transfer management message to the sending entity to control the data rate of the transport network.

Example 3 includes the device of Example 2. The transport layer data transfer management message is a transmission control protocol (TCP) acknowledgment message or negative response message.

Example 4 includes any one of the devices of Examples 1 to 3. The processing circuit is configured to receive the link capacitance indication provided to the UE from the MeNB or SeNB and control the data rate of the transport network based on the link capacitance.

Example 5 includes the device of Example 4. The link capacity indication is included in the message along with the notification of the scheduling decision.

Example 6 includes the device of Example 4 or 5. The processing circuit is further configured to receive the updated link capacitance indication provided to the UE by the MeNB or SeNB.

Example 7 includes any one of the devices of Examples 2-6. The transport layer data transfer management message is a transport layer NACK message. The processing circuit is configured to send a transport layer NACK message to a transmitting entity to control the transmission rate of data from the transmitting entity, facilitating transport congestion control.

Example 8 includes the device of Example 7. The processing circuit is configured to result in the transmission of a transport layer NACK message regardless of whether the data has been successfully received.

Example 9 includes any one of the devices of Examples 1-8. The processing circuit is configured to cause the MeNB to send a notification of the traffic prior to the transmission of the traffic.

Example 10 includes the device of Example 9. Traffic notifications include notifications of traffic type, size or quality of service requirements.

Example 11 includes the device of Example 9 or 10. The processing circuit is further configured to receive a notification of the MeNB scheduling decision and transmit data to the MeNB or SeNB based on the notification.

Example 12 includes any one of the devices of Examples 1-11. The processing circuit is configured to generate a schedule for the transmission of traffic by the MeNB or SeNB and to send a notification of the schedule to the MeNB.

Example 13 includes the device of Example 12. The processing circuit is configured to generate a schedule based on the type, size or quality of service requirements of the traffic.

Example 14 includes the device of Example 13. The processing circuit is configured to receive a link capacity instruction provided by the MeNB or SeNB to the UE and schedule the transmission of traffic based on the link capacity instruction.

Example 15 includes any one of the devices of Examples 1-14. This device is installed in the core network.

Example 16 includes the device of Example 15. This device is a serving gateway.

Example 17 includes one or more computer-readable storage media with instructions. When the instruction is executed, the mobile proxy buffers the traffic received from the sending entity over the transport network that traverses the core network, controlling the data rate of the transport network, and subsequent user equipment. For the transmission of the (UE), a step of causing the macro eNB (MeNB) or the small cell eNB (SeNB) to transmit traffic from the core network is executed. The SeNB is configured to communicate with the UE using frequencies above gigahertz (GHz).

Example 18 includes one or more computer-readable storage media of Example 17. When the instruction is executed, it is further configured to send a transport layer data transfer management message to the sending entity to control the data rate of the transport network.

Example 19 includes one or more computer-readable storage media of any one of Examples 17-18. When the instruction is executed, it also causes the mobile proxy to perform a step of controlling the data rate of the transport network based on the link capacity of the wireless air interface.

Example 20 includes one or more computer-readable storage media of Example 19. When the instruction is executed, the mobile proxy is further made to perform a step of determining the link capacity based on the link capacity instruction received from the MeNB or SeNB.

Example 21 includes one or more computer-readable storage media of Example 20. The link capacity indication is included in the message along with the notification of the scheduling decision, and the message is received from the MeNB.

Example 22 includes one or more computer-readable storage media of any one of Examples 18-21. The transport layer data transfer management message is a transmission control protocol (TCP) message.

Example 23 includes one or more computer-readable storage media of any one of Examples 17-22. When the instruction is executed, it further causes the mobile proxy to perform a step of sending a traffic notification to the MeNB before sending the traffic. Traffic notifications include notifications of traffic type, size or quality of service requirements.

Example 24 includes one or more computer-readable storage media of any one of Examples 17-23. When the instruction is executed, it is further configured to receive a notification of the scheduling decision of MeNB and transmit data to the MeNB or SeNB based on the notification of the scheduling decision.

Example 25 includes one or more computer-readable storage media of any one of Examples 17-24. When the instruction is executed, it is configured to control the data rate by negatively responding to a normally received transmission.

Example 26 includes one or more computer-readable storage media with instructions. When the instruction is executed, the mobile proxy is in the process of processing the link capacity report received from the macro eNB (MeNB), and the link capacity report is provided to the user device (UE) by the small cell eNB (SeNB). The transport layer data transfer management message is sent to the sending entity based on the process and the link capacity report, including the link capacity of the first link to be used, the first link using frequencies greater than 6 gigahertz (GHz). The process of transmitting, the transport layer data transfer management message, executes a process, which is configured to control the data rate of the transport network.

Example 27 includes one or more computer-readable storage media of Example 26. The transport layer message is an acknowledgment / negative response (ACK / NACK) message.

Example 28 includes one or more computer-readable storage media of Example 26 or 27. The transport layer data transfer management message is a transmission control protocol (TCP) message.

Example 29 includes one or more computer-readable storage media of any one of Examples 26-28. Transport layer data transfer management messages are configured to provide congestion or flow control in the transport network.

Example 30 includes one or more computer-readable storage media of Example 29. When executed, the instruction further causes the mobile proxy to perform a step of generating a transport layer data transfer management message to provide congestion or flow control for each quality of service (QoS) class.

Example 31 includes one or more computer-readable storage media of any one of Examples 26-30. When executed, the instruction further causes the mobile proxy to perform a step of generating a schedule for sending data to the UE by MeNB or SeNB based on the link capacity report.

Example 32 includes one or more computer-readable storage media of Example 31. When executed, the instruction further causes the mobile proxy to perform a step of determining a quality of service (QoS) class of data and a step of generating a schedule based on the QoS class.

Example 33 includes a method of operating a mobile proxy. This method is a step of processing the link capacity report received from the macro eNB (MeNB), and the link capacity report is the first link provided to the user device (UE) by the small cell eNB (SeNB). A transport network that traverses the core network and terminates at the first end with a mobile proxy, based on steps and link capacity reports, including link capacity and the first link uses frequencies above 6 GHz (GHz). Includes steps to control the data rate of the.

Example 34 includes the method of Example 33. The step of controlling the data rate of the transport network includes sending a transport layer data transfer management message to the transmitting entity that terminates the transport network at the second end.

Example 35 includes the method of Example 34. The transport layer message is an acknowledgment / negative response (ACK / NACK) message.

Example 36 includes the method of Example 34 or 35. The transport layer data transfer management message is a transmission control protocol (TCP) message.

Example 37 includes any one of Examples 33-36. The steps of controlling the data rate include performing congestion or flow control in the transport network.

Example 38 includes any one of Examples 33-37. The steps of controlling the data rate include performing congestion or flow control for each quality of service (QoS) class.

Example 39 includes any one of Examples 33-38. Further, it includes a step of generating a schedule for transmitting data to the UE by MeNB or SeNB based on the link capacity report.

Example 40 includes the method of Example 39. Further, it includes a step of determining a quality of service (QoS) class of data and a step of generating a schedule based on the QoS class.

Example 41 includes a mobile proxy having means configured to perform any one of Examples 33-40.

Example 42 is a link capacity report including the link capacity status of the first link, which is implemented in hardware at least partially and is provided from the macro eNB (MeNB) to the user equipment (UE) by the small cell eNB (SeNB). Scheduling logic configured to receive, the first link uses frequencies above 6 GHz (GHz), based on the scheduling logic and at least partially hardware-implemented, link capacity reports. A device comprising communication logic configured to transmit a transport layer data transfer management message over a transport network.

Example 43 includes the device of Example 42. The transport layer data transfer management message is a transmission control protocol (TCP) message.

Example 44 includes any one of the devices of Examples 42-43. Transport layer data transfer management messages are configured to provide transport network congestion or flow control.

Example 45 includes the device of Example 44. The communication logic is configured to generate transport layer data transfer management messages to provide transport network congestion or flow control for individual quality of service (QoS) classes.

Example 46 includes any one of the devices of Examples 42-45. The scheduling logic is configured to generate a schedule for sending data to the UE by the MeNB or SeNB based on the link capacity report.

Example 47 includes the device of Example 46. Scheduling logic is further configured to determine a quality of service (QoS) class of data and generate a schedule based on the QoS class.

Example 48 includes a device comprising a memory circuit and a processing circuit coupled to the memory circuit. The processing circuit is configured to receive data from the user equipment (UE) via the macro eNB (MeNB) or small cell eNB (SeNB), and at least the first portion of the data is from 6 GHz (GHz). Data is transmitted from the UE to the SeNB using a large frequency, is configured to temporarily store the data in the memory circuit, terminates at the device, traverses the core network, and data via the core network. Is configured to send.

Example 49 includes the device of Example 48. The processing circuit is configured to schedule the transmission of data in the core network.

Example 50 includes the device of Example 48 or 49. The processing circuit is configured to receive data from the UE via both MeNB and SeNB.

Example 51 includes any one of Examples 48-50. The processing circuit is configured to receive data (including the first part of the data) from the MeNB.

Example 52 includes any one of the devices of Examples 48-51. The processing circuit is configured to send a transport layer data transfer management message to control the data rate of the transport network.

Example 53 includes one or more computer-readable storage media containing instructions. When executed, the instruction is a step of processing the data received from the user device (UE) from the user device (UE) via the macro eNB (MeNB) or the small cell eNB (SeNB) to the mobile proxy, and is a step of processing at least the first data. The portion is transmitted from the UE to the SeNB using a frequency greater than 6 GHz (GHz), via a process, a process of temporarily storing data in a memory circuit, and a transport network terminated by the device. , The process of transmitting data via the core network, and so on.

Example 54 includes one or more computer-readable storage media of Example 53. The instruction also causes the mobile proxy to perform the process of scheduling the transmission of data in the core network when executed.

Example 55 includes one or more computer-readable storage media of Example 53 or 54. Data is received from the UE via both MeNB and SeNB.

Example 56 includes one or more computer-readable storage media of any one of Examples 53-55. The data (including the first part of the data) is received from the MeNB.

Example 57 includes one or more computer-readable storage media of any one of Examples 53-56. When executed, the instruction further causes the mobile proxy to send a transport layer data transfer management message to perform the step of controlling the data rate of the transport network.

Example 58 includes one or more computer-readable storage media containing instructions. When executed, the instruction processes the data transmitted to the mobile proxy between the core network and the user equipment communicatively coupled to the mobile proxy via the radio access network, and the radio access network. The step of terminating the transmission control protocol (TCP) layer in order to reduce the fluctuation of the radio channel capacity in the above is executed.

Example 59 includes one or more computer-readable storage media of Example 58. The instruction, when executed, causes the mobile proxy to perform a step of manipulating the network traffic rate at the TCP layer based on the capacity of the radio access network.

Example 60 includes one or more computer-readable storage media of Example 59. Mobile proxies are configured to use TCP rate control procedures to manipulate network traffic.

Example 61 includes one or more computer-readable storage media of any one of Examples 59-60. When the instruction is executed, it is configured to process the link capacity report from the macro evolution node B (MeNB) to determine the capacity of the radio access network for the connection of the user equipment.

Example 62 includes one or more computer-readable storage media of any one of Examples 58-61. The instruction, when executed, also causes the mobile proxy to perform the process of processing traffic based on quality of service requirements.

Example 63 includes one or more computer-readable storage media of any one of Examples 58-62. Radio access networks include devices that provide one or more millimeter wave (mmWave) connections.

Example 64 includes a mobile proxy. Mobile proxies are a means of processing data that is communicated between the core network and user devices communicatively coupled to the mobile proxy over the radio access network and reduce fluctuations in radio channel capacity in the radio access network. A means of terminating the transmission control protocol (TCP) layer is provided.

Example 65 includes the mobile proxy of Example 64. Means for terminating the TCP layer are further configured to manipulate network traffic in the TCP layer based on the capacity of the radio access network.

Example 66 includes the mobile proxy of Example 65. The means for terminating the TCP layer is configured to manipulate network traffic using a TCP control mechanism.

Example 67 includes any one of the mobile proxies of Examples 64-66. Further, a means for processing a report from the macro evolution node B (MeNB) to determine the capacity of the radio access network is provided.

Example 68 includes any one of the mobile proxies of Examples 64-67. The means of processing data are configured to process traffic based on quality of service requirements.

Example 69 includes any one of the mobile proxies of Examples 64-68. Radio access networks include devices that provide one or more millimeter wave (mmWave) connections.

Example 70 includes a mobile proxy. A mobile proxy is data directed at a user device (UE) that is at least partially implemented in hardware and is communicably coupled from a transmitting entity over a first connection to a core network over a wireless access network. A Transmission Control Protocol (TCP) module that is configured to receive, and sends one or more transport layer messages to the sending entity over the first connection to control the data rate of the transport network. A TCP module configured to transmit and a transformer implemented in hardware, at least partially, configured to transmit data to the UE over a second connection between the UE and the core network. It is equipped with a port wireless air interface module.

Example 71 includes the mobile proxy of Example 70. The first connection traverses the Internet Protocol (IP) network and the second connection traverses the wireless air interface.

Example 72 includes the mobile proxy of Example 70 or 71. One or more transport layer messages include a transport layer data transfer management message for controlling the transmission rate of data from a transmitting entity.

Example 73 includes the mobile proxy of Example 72. The TCP module is configured to reduce the transmission rate by negatively responding to a successfully received transmission.

Example 74 includes the mobile proxy of Example 72 or 73. The TCP module is configured to control the data rate based on the link capacitance provided to the UE by the macro eNB (MeNB) or the small cell eNB (SeNB).

Example 75 includes any one of the mobile proxies of Examples 70-74. The mobile proxy is configured to receive a link capacity indication via a second connection.

Example 76 includes any one of the mobile proxies of Examples 70-75. The mobile proxy is configured to receive instructions from the macro eNB (MeNB) of the data transmission schedule to the UE by the MeNB or the small cell eNB (SeNB).

Example 77 includes any one of the mobile proxies of Examples 70-76. The mobile proxy is configured to send instructions to the macro eNB (MeNB) to schedule the transmission of data to the UE by the MeNB or small cell eNB (SeNB).

Example 78 includes the mobile proxy of Example 76 or 77. The schedule includes sending at least a portion of the data to the UE by the SeNB, which is configured to communicate with the UE using frequencies greater than 6 GHz.

Example 79 includes any one of the mobile proxies of Examples 70-78. The mobile proxy is configured to receive instructions for the data sent from the UE to the receiving entity, and the TCP module is configured to establish a first connection based on the instructions for the data sent from the UE. Ru.

Example 80 includes the mobile proxy of Example 79. The TCP module is configured to establish a first connection using a 3-way handshake.

Example 81 includes a macro eNB (MeNB). MeNB is a communication logic that is implemented in hardware at least partially and is configured to receive notification of data transmitted to a user device (UE) from a mobile proxy existing in a core network element. Is a first link or small cell eNB provided by MeNB based on communication logic, including data type, size or quality of service (QoS) requirements, and at least partly in hardware implementation and notification. It comprises scheduling logic configured to generate a schedule for transmitting data via a wireless air interface via a second link provided by SeNB). The communication logic is further configured to send schedule instructions to the mobile proxy.

Example 82 includes the MeNB of Example 81. The communication logic is configured to provide the mobile proxy with an indication of the link capacity provided by the MeNB or SeNB to the UE.

Example 83 includes the MeNB of Example 82. The communication logic is configured to send a message to the mobile proxy that contains both a link capacity instruction and a schedule instruction.

Example 84 includes any one MeNB of Examples 81-83. The communication logic is further configured to send an updated link capacity indication provided to the UE by the MeNB or SeNB.

Example 85 includes any one MeNB of Examples 81-84. The schedule for transmitting data over the air interface includes scheduling at least a first portion of the data to be provided to the UE by the SeNB. The SeNB is configured to transmit at least the first portion of the data using frequencies greater than 6 GHz.

Example 86 includes any one MeNB of Examples 81-85. The schedule for transmitting data over the air interface includes scheduling at least a first portion of the data to be provided to the UE by the MeNB. The communication logic is configured to receive at least the first portion of data from the core network and transmit at least the first portion to the UE using frequencies below 6 GHz.

Example 87 includes a macro eNB (MeNB). The MeNB is configured to determine the link capacity provided to the user equipment (UE) via the first link provided by the MeNB and the second link provided by the small cell eNB (SeNB). It includes a control circuit and a transmission / reception circuit coupled to the control circuit. The transmit / receive circuit is configured to transmit the link capacitance to the mobile proxy present in the core network element, and data is sent from the mobile proxy present in the core network element to the UE via the first link or the second link. It is configured to receive notification of the schedule for sending.

Example 88 includes the MeNB of Example 87. Scheduling the transmission of data includes scheduling at least a portion of the data over a second link.

Example 89 includes the MeNB of Example 88. The transmit / receive circuit is further configured to send a wakeup signal to the UE to instruct the UE to wake up the air interface associated with the second link.

Example 90 includes the MeNB of Example 89. The transmit / receive circuit is configured to transmit a wakeup signal via the first link.

Example 91 includes any one MeNB of Examples 87-90. Scheduling the transmission of data includes scheduling the first data over the first link. The communication circuit is further configured to receive the first data from the mobile proxy and transmit the first data to the UE over the first link.

Example 92 includes any one of Examples 87-91, MeNB. The communication circuit is further configured to transmit an updated link capacitance indication provided to the UE by the MeNB or SeNB.

Example 93 includes a macro eNB (MeNB). The MeNB comprises communication logic configured to provide a first link of a wireless air interface for communication with a user equipment (UE), and scheduling logic that is at least partially implemented in hardware. .. The scheduling logic is configured to receive the uplink traffic report from the UE via the communication logic and generate a schedule indicating the transmission of the first uplink data over the second link of the air interface. The second link is provided by the small cell eNB (SeNB) using a frequency greater than 6 GHz and is configured to transmit the schedule to the UE via the first link.

Example 94 includes the MeNB of Example 93. The communication logic is configured to communicate with a mobile proxy that resides in the core network element.

Example 95 comprises any one of Examples 93-94, MeNB. The communication logic is configured to receive the second uplink data over the first link and send the second uplink data to the mobile proxy.

Example 96 includes a method of operating a macro eNB (MeNB). The method is via a step of providing a first link of the wireless air interface for communication with the user equipment (UE), a step of receiving an uplink traffic report from the UE, and a second link of the air interface. A step of generating a schedule indicating the transmission of the first uplink data, the second link is a step and a schedule provided by the small cell eNB (SeNB) using a frequency greater than 6 GHz. A step of transmitting to the UE via the first link is included.

Example 97 includes the method of Example 96. In addition, it includes a step of communicating with a mobile proxy that resides in the core network element.

Example 98 includes any one of Examples 96-97. Further, it includes a step of receiving the second uplink data via the first link and a step of transmitting the second uplink data to the mobile proxy.

Example 99 includes a method of operating a mobile proxy. The method comprises receiving data from a transmitting entity via a first connection to a user device (UE) communicably coupled to a core network via a radio access network, and a transport network. It includes a step of controlling the data rate and a step of transmitting data to the UE via a second connection between the UE and the core network.

Example 100 includes the method of Example 99. The step of controlling the data rate of the transport network includes sending one or more transport layer messages to the sending entity over the first connection.

Example 101 includes the method of Example 100. One or more transport layer messages include a transport layer data transfer management message for controlling the transmission rate of data from a transmitting entity.

Example 102 includes any one of Examples 99-101. The first connection traverses the Internet Protocol (IP) network and the second connection traverses the wireless air interface.

Example 103 includes any one of Examples 99-101. The step of controlling the data rate includes a step of reducing the transmission rate by negatively responding to a normally received transmission.

Example 104 includes any one of Examples 99-103. The step of controlling the data rate is based on the link capacity provided to the UE by the macro eNB (MeNB) or the small cell eNB (SeNB).

Example 105 includes any one of Examples 99-104. Further, it includes a step of receiving an instruction of the link capacitance via the second connection.

Example 106 includes any one of Examples 99-105. Further, the step of receiving the instruction of the data transmission schedule to the UE by the MeNB or the small cell eNB (SeNB) from the macro eNB (MeNB) is included.

Example 107 includes any one of Examples 99-106. Further, the step of transmitting the instruction of the schedule of data transmission to the UE by the MeNB or the small cell eNB (SeNB) to the macro eNB (MeNB) is included.

Example 108 includes the method of Example 106 or 107. The SeNB is configured to communicate with the UE using frequencies greater than 6 GHz, including the transmission of at least a portion of the data to the UE by the SeNB.

Example 109 includes any one of Examples 99-108. The mobile proxy is configured to receive instructions for the data sent from the UE to the receiving entity, and the TCP module is configured to establish a first connection based on the instructions for the data sent from the UE. Ru.

Example 110 includes the method of Example 109. In addition, it includes the step of establishing a first connection using a 3-way handshake.

Example 111 includes a method of operating a macro eNB (MeNB). The method is the step of receiving a notification of data sent to a user device (UE) from a mobile proxy present in a core network element, where the notification sets the data type, size or quality of service (QoS) requirements. Including, based on steps and notifications, for transmitting data over a wireless air interface via a first link provided by MeNB or a second link provided by a small cell eNB (SeNB). It includes a step to generate a schedule and a step to send a schedule notification to a mobile proxy.

Example 112 includes the method of Example 111. Further, the mobile proxy includes a step of providing an instruction of the link capacity provided from the MeNB or SeNB to the UE.

Example 113 includes the method of Example 112. In addition, it includes sending a message to the mobile proxy that includes both link capacity instructions and schedule notifications.

Example 114 includes any one of the methods of Examples 111-113. Further, it includes a step of transmitting an updated link capacity indication provided to the UE by the MeNB or SeNB.

Example 115 includes any one of the methods of Examples 111-114. The schedule for transmitting data over the air interface includes scheduling at least a first portion of the data to be provided to the UE by the SeNB. The SeNB is configured to transmit at least the first portion of the data using frequencies greater than 6 GHz.

Example 116 includes any one of the methods of Examples 111-115. The schedule for transmitting data over the air interface includes scheduling at least a first portion of the data to be provided to the UE by the MeNB. The method further comprises the step of receiving at least the first portion of data from the core network and transmitting at least the first portion to the UE using frequencies below 6 GHz.

Example 117 includes a method of operating a macro eNB (MeNB). The method comprises a step of determining the link capacity provided to the user equipment (UE) via the first link provided by the MeNB and the second link provided by the small cell eNB (SeNB), and the link. Notification of the steps to send capacity to the mobile proxy present in the core network element and the schedule for sending data from the mobile proxy present in the core network element to the UE over the first or second link. Includes steps to receive and.

Example 118 includes the method of Example 117. Scheduling the transmission of data includes scheduling at least a portion of the data over a second link.

Example 119 includes the method of Example 118. Further, it includes a step of transmitting a wakeup signal to the UE to instruct the UE to wake up the air interface associated with the second link.

Example 120 includes the method of Example 119. Further, it includes a step of transmitting a wakeup signal via the first link.

Example 121 includes any one of Examples 117-120. Scheduling the transmission of data includes scheduling the first data over the first link. The method further includes the step of receiving the first data from the mobile proxy and transmitting the first data to the UE over the first link.

Example 122 includes any one of Examples 117-121. Further, it includes a step of transmitting an updated link capacity indication provided to the UE by the MeNB or SeNB.

Example 123 includes a method of operating a mobile proxy. The method buffers traffic received from a transmitting entity over a transport network that traverses the core network, controlling the data rate of the transport network, and subsequent transmissions to the user equipment (UE). For this purpose, it includes a step of transmitting traffic from the core network to the macro eNB (MeNB) or the small cell eNB (SeNB). The SeNB is configured to communicate with the UE using frequencies above 6 GHz (GHz).

Example 124 includes the method of Example 123. The step of controlling the data rate includes a step of sending a transport layer data transfer management message to the sending entity.

Example 125 includes the method of Example 123 or Example 124. The steps to control the data rate are based on the link capacity of the wireless air interface.

Example 126 includes the method of Example 125. Further, it includes a step of determining the link capacity based on the link capacity instruction received from the MeNB or SeNB.

Example 127 includes the method of Example 126. The link capacity indication is included in the message along with the notification of the scheduling decision, and the message is received from the MeNB.

Example 128 includes any one of Examples 124-127. The transport layer data transfer management message is a transmission control protocol (TCP) message.

Example 129 includes any one of the methods of Examples 123-128. Further, it includes a step of controlling the data rate by negatively responding to the normally received transmission.

Example 130 includes a device that performs any one of Examples 96-129 or any other example method.

Example 131 includes an apparatus comprising means for performing any one of Examples 96-129 and any other example.

Example 132 includes one or more computer-readable storage media (which may be non-temporary) containing instructions. The instruction, when executed, causes the device to perform any one of the methods of Examples 96-129 and other examples.

Example 133 is a means of receiving traffic from a transmitting entity via a transport network traversing the core network, a means of buffering the traffic in a memory circuit, a means of controlling the data rate of the transport network, and a user. A device comprising means for transmitting traffic from a core network to a macro eNB (MeNB) or a small cell eNB (SeNB) for subsequent transmission to a device (UE). In some examples, the SeNB is configured to communicate with the UE using frequencies above 6 GHz (GHz).

Example 134 includes the device of Example 133. Further, a means for controlling the data rate of the transport network by transmitting a transport layer data transfer management message to a transmitting entity is provided.

Example 135 includes the device of Example 134. The transport layer data transfer management message is a Transmission Control Protocol (TCP) acknowledgment message.

Example 136 includes any one of the devices of Examples 133-135. Further, it includes means for receiving the link capacity instruction provided from the MeNB or SeNB to the UE, and means for controlling the data rate of the transport network based on the link capacity.

Example 137 includes the device of Example 136. The link capacity indication is included in the message along with the notification of the scheduling decision.

Example 138 includes the device of Example 136 or 137. Further provided is means for receiving the updated link capacity indication provided to the UE by the MeNB or SeNB.

Example 139 includes any one of the devices of Examples 134-138. The transport layer data transfer management message is a transport layer NACK message. The present apparatus further includes means for transmitting a transport layer NACK message to a transmitting entity to control the transmission rate of data from the transmitting entity to facilitate transport congestion control.

Example 140 includes the device of Example 139. Further, a means for causing the transmission of the transport layer NACK message is provided regardless of whether or not the data is normally received.

Example 141 includes any one of the devices of Examples 133-140. Further, a means for causing the MeNB to send a notification of the traffic before the transmission of the traffic is provided.

Example 142 includes the device of Example 141. Traffic notifications include notifications of traffic type, size or quality of service requirements.

Example 143 includes the device of Example 141 or 142. Further, it includes a means for receiving the notification of the scheduling decision of the MeNB, and a means for transmitting data to the MeNB or the SeNB based on the notification.

Example 144 includes any one of the devices of Examples 141-143. Further, a means for generating a schedule for transmitting traffic by MeNB or SeNB and transmitting a notification of the schedule to MeNB is provided.

Example 145 includes the device of Example 144. In addition, it provides means for generating schedules based on traffic type, size or quality of service requirements.

Example 146 includes the device of Example 145. Further, it includes means for receiving the link capacity instruction provided to the UE by the MeNB or SeNB, and means for scheduling the transmission of traffic based on the link capacity instruction.

Example 147 includes any one of the devices of Examples 133-146. This device is installed in the core network.

Example 148 includes the apparatus of Example 147. This device is installed in the serving gateway.

Example 149 includes a device for operating a mobile proxy. This device is a means for processing the link capacity report received from the macro eNB (MeNB), and the link capacity report is the first link provided to the user device (UE) by the small cell eNB (SeNB). The first link comprises means of using a frequency greater than 6 GHz (GHz), including link capacitance, and means of controlling the data rate of the transport network based on the link capacitance report.

Example 150 includes the device of Example 149. Means for controlling the data rate of a transport network include means for sending a transport layer data transfer management message to a sending entity.

Example 151 includes the device of Example 150. The transport layer message is an acknowledgment / negative response (ACK / NACK) message.

Example 152 includes the device of Example 150 or 151. The transport layer data transfer management message is a transmission control protocol (TCP) message.

Example 153 includes any one of the devices of Examples 149-152. Means of controlling the data rate include means of performing congestion or flow control in the transport network.

Example 154 includes any one of the devices of Examples 149-153. Means of controlling data rates include means of performing congestion or flow control for individual quality of service (QoS) classes.

Example 155 includes any one of the devices of Examples 149-154. Further, it includes means for generating a schedule for transmitting data to the UE by MeNB or SeNB based on the link capacity report.

Example 156 includes the device of Example 155. Further, it includes means for determining a quality of service (QoS) class of data and means for generating a schedule based on the QoS class.

Example 157 is a means of receiving data from a user device (UE) via a macro eNB (MeNB) or a small cell eNB (SeNB), wherein at least the first portion of the data is from 6 GHz (GHz). Data is sent over the core network via means that are transmitted from the UE to the SeNB using a higher frequency, means that temporarily buffer the data in the memory circuit, and a transport network that terminates at the device. Includes a device comprising means of transmitting.

Example 158 includes the device of Example 157. Further, a means for scheduling the transmission of data in the core network is provided.

Example 159 includes the device of Example 157 or 158. Further, a means for receiving data from the UE via both MeNB and SeNB is provided.

Example 160 includes any one of the devices of Examples 157-159. Further, a means for receiving data (including the first part of the data) from the MeNB is provided.

Example 161 includes any one of the devices of Examples 157-160. Further, a means for transmitting a transport layer data transfer management message is provided in order to control the data rate of the transport network.

Example 162 includes a device in a mobile proxy. The device is a means of receiving data from a transmitting entity via a first connection to a user device (UE) communicably coupled to a core network via a radio access network and a transport network. It includes means for controlling the data rate and means for transmitting data to the UE via a second connection between the UE and the core network.

Example 163 includes the apparatus of Example 162. Means for controlling the data rate of a transport network include means for sending one or more transport layer messages to a transmitting entity over a first connection.

Example 164 includes the device of Example 163. One or more transport layer messages include a transport layer data transfer management message for controlling the transmission rate of data from a transmitting entity.

Example 165 includes any one of the devices of Examples 162-164. The first connection traverses the Internet Protocol (IP) network and the second connection traverses the wireless air interface.

Example 166 includes any one of the devices of Examples 162-164. Means for controlling the data rate include means for reducing the transmission rate by negatively responding to a successfully received transmission.

Example 167 includes any one of the devices of Examples 162-166. The means of controlling the data rate is based on the link capacity provided to the UE by the macro eNB (MeNB) or the small cell eNB (SeNB).

Example 168 includes any one of the devices of Examples 162-166. Further, a means for receiving the link capacity instruction via the second connection is provided.

Example 169 includes any one of the devices of Examples 162-168. Further, a means for receiving an instruction of a data transmission schedule to the UE by the MeNB or the small cell eNB (SeNB) from the macro eNB (MeNB) is provided.

Example 170 includes any one of the devices of Examples 162-169. Further, a means for transmitting an instruction of a schedule for transmitting data to the UE by the MeNB or the small cell eNB (SeNB) to the macro eNB (MeNB) is provided.

Example 171 includes the apparatus of Example 169 or 170. The schedule includes sending at least a portion of the data to the UE by the SeNB, which is configured to communicate with the UE using frequencies greater than 6 GHz.

Example 172 includes any one of the devices of Examples 162-171. The mobile proxy is configured to receive instructions for the data sent from the UE to the receiving entity, and the TCP module is configured to establish a first connection based on the instructions for the data sent from the UE. Ru.

Example 173 includes the apparatus of Example 172. Further provided is a means of establishing a first connection using a 3-way handshake.

Example 174 includes a device within a macro eNB (MeNB). The device is a means of receiving notifications of data sent to a user device (UE) from a mobile proxy that resides in a core network element, which provides data type, size or quality of service (QoS) requirements. For transmitting data via a wireless air interface, including, and based on notification, via a first link provided by MeNB or a second link provided by a small cell eNB (SeNB). It includes a means for generating a schedule and a means for sending a notification of the schedule to a mobile proxy.

Example 175 includes the device of Example 174. Further, the mobile proxy is provided with a means for providing an instruction of the link capacity provided from the MeNB or SeNB to the UE.

Example 176 includes the device of Example 175. In addition, the mobile proxy is provided with means for sending a message containing both a link capacity indication and a schedule notification.

Example 177 includes any one of the devices of Examples 174 to 176. Further provided is a means of transmitting an updated link capacity indication provided to the UE by the MeNB or SeNB.

Example 178 includes any one of the devices of Examples 174-177. The schedule for transmitting data over the air interface includes scheduling at least a first portion of the data to be provided to the UE by the SeNB. The SeNB is configured to transmit at least the first portion of the data using frequencies greater than 6 GHz.

Example 179 includes any one of the devices of Examples 174 to 178. The schedule for transmitting data over the air interface includes scheduling at least a first portion of the data to be provided to the UE by the MeNB. The apparatus further comprises means for receiving at least the first portion of data from the core network and transmitting at least the first portion to the UE using frequencies below 6 GHz.

Example 180 includes a device within a macro eNB (MeNB). The device provides a means and a link to determine the link capacity provided to the user equipment (UE) via the first link provided by the MeNB and the second link provided by the small cell eNB (SeNB). Means of transmitting capacity to the mobile proxy present in the core network element and notification of the schedule for transmitting data from the mobile proxy present in the core network element to the UE via the first link or the second link. It is provided with a means for receiving the data.

Example 181 includes the device of Example 180. Scheduling the transmission of data includes scheduling at least a portion of the data over a second link.

Example 182 includes the device of Example 180. Further, a means is provided for transmitting a wakeup signal to the UE to instruct the UE to wake up the air interface associated with the second link.

Example 183 includes the apparatus of Example 182. Further, a means for transmitting a wakeup signal via the first link is provided.

Example 184 includes any one of the devices of Examples 180-183. Scheduling the transmission of data includes scheduling the first data over the first link. The apparatus further comprises means for receiving the first data from the mobile proxy and transmitting the first data to the UE via the first link.

Example 185 includes any one of the devices of Examples 180-184. Further provided is a means of transmitting an updated link capacity indication provided to the UE by the MeNB or SeNB.

Example 186 includes a link capacity report message that includes a data rate field for communicating the link capacity status of the wireless link to the user equipment (UE) and a UE identifier field for communicating the UE identifier.

Example 187 includes the link capacity report message of Example 186. In addition, it includes a dropout instruction field for communicating information about the dropout frequency of the first link between the UE and the small cell eNB (SeNB).

Example 188 includes the link capacity report message of Example 187. The dropout instruction field is for communicating information about the average dropout frequency of the first link.

Example 189 includes a link capacity report message of any one of Examples 186-188. In addition, it includes a connection reestablishment time indicator field for communicating information about the connection reestablishment time of the first link between the UE and the small cell eNB (SeNB).

Example 190 includes the link capacity report message of Example 189. The connection reestablishment time indicator field is for communicating information about the average connection reestablishment time of the first link.

Example 191 includes a link capacity report message of any one of Examples 186-190. The wireless link is a link between the UE and the small cell eNB (SeNB).

Example 192 includes the link capacity report message of Example 191. The link capacity report message further includes a second data rate field for communicating the link capacity status of another radio link between the UE and the macrocell eNB (MeNB).

Example 193 includes a link capacity report message of any one of Examples 186-192. The link capacity status is statistical information regarding the rate at which IP packets are normally delivered to the user equipment (UE).

Example 194 includes a link capacity report message of any one of Examples 186 to 193. Link capacity report messages are non-access layer messages.

Example 195 includes a link capacity report message of any one of Examples 186-194. The UE identifier is the IP address assigned to the UE.

The description of the illustrated examples, including the content described in the abstract, is not intended to be exhaustive and does not limit the disclosure of the present invention to the exact form disclosed. Specific examples and examples are described herein for illustrative purposes, but as those skilled in the art will recognize, various calculations calculated to achieve the same object in the light of the above detailed description. Alternative or equivalent embodiments or examples may be made.

Claims (17)

Memory circuit and
The processing circuit coupled with the memory circuit and
It is a device equipped with
The processing circuit
Receives traffic from sending entities over a transport network that traverses the core network
The traffic is buffered in the memory circuit and
Control the data rate of the transport network
The traffic is transmitted from the core network to the first eNB or the second eNB for subsequent transmission to the user equipment (UE).
It is configured to generate a schedule for the transmission of traffic by the first eNB or the second eNB and to transmit a notification of the schedule to the first eNB.
apparatus. The processing circuit is configured to send a transport layer data transfer management message to the transmitting entity to control the data rate of the transport network.
The device according to claim 1. The transport layer data transfer management message is a transmission control protocol (TCP) acknowledgment message or negative response message.
The device according to claim 2. The processing circuit receives an instruction of the link capacity provided to the UE from the first eNB or the second eNB, and controls the data rate of the transport network based on the link capacity. Composed,
The device according to any one of claims 1 to 3. The processing circuit is further configured to receive a notification of the scheduling decision of the first eNB and transmit the traffic to the first eNB or the second eNB based on the notification.
The device according to any one of claims 1 to 3. The processing circuit is configured to generate the schedule based on the type, size or quality of service requirements of the traffic.
The device according to claim 1. The processing circuit receives an instruction of the link capacity provided to the UE by the first eNB or the second eNB, and schedules the transmission of the traffic based on the instruction of the link capacity. Composed,
The device according to claim 6. Macro eNB (MeNB)
Communication logic that is implemented at least partially in hardware and is configured to receive notifications of data transmitted to a user device (UE) from a mobile proxy present in a core network element. Communication logic, including said data type, size or quality of service (QoS) requirements.
Via a wireless air interface, at least partially implemented in hardware and based on the notification, via a first link provided by the MeNB or a second link provided by the small cell eNB (SeNB). And scheduling logic configured to generate a schedule for sending the data
With
The communication logic is further configured to send the schedule instructions to the mobile proxy.
MeNB. The communication logic is configured to provide the mobile proxy with an indication of the link capacity provided by the MeNB or SeNB to the UE.
The MeNB according to claim 8. The communication logic is configured to send a message to the mobile proxy that includes both said instructions for the link capacity and said instructions for the schedule.
The MeNB according to claim 9. The communication logic is further configured to send an indication of the updated link capacity provided to the UE by the MeNB or the SeNB.
The MeNB according to any one of claims 8 to 10. The schedule for transmitting the data via the radio air interface includes scheduling at least a first portion of the data to be provided to the UE by the SeNB.
The SeNB is configured to transmit at least the first portion of the data using frequencies greater than 6 GHz.
The MeNB according to any one of claims 8 to 10. The schedule for transmitting the data via the radio air interface includes scheduling at least a first portion of the data to be provided to the UE by the MeNB.
The communication logic is configured to receive at least the first portion of the data from the core network and transmit at least the first portion to the UE using frequencies below 6 GHz.
The MeNB according to any one of claims 8 to 10. Macro eNB (MeNB)
A control circuit configured to determine the link capacitance provided to the user equipment (UE) via the first link provided by the MeNB and the second link provided by the small cell eNB (SeNB). When,
The transmission / reception circuit coupled to the control circuit and
The transmission / reception circuit
The link capacity is configured to be sent to a mobile proxy that resides in the core network element.
A mobile proxy located on a core network element is configured to receive notification of a schedule for sending data to the UE via the first link or the second link.
MeNB. The schedule of data transmission includes that at least a portion of the data is scheduled via the second link.
The MeNB according to claim 14. The transmit / receive circuit is further configured to send a wakeup signal to the UE to instruct the UE to wake up the air interface associated with the second link.
The MeNB according to claim 15. The schedule of data transmission includes that the first data is scheduled via the first link.
The transmit / receive circuit is further configured to receive the first data from the mobile proxy and transmit the first data to the UE via the first link.
The MeNB according to any one of claims 14 to 16.

Images