Patent Grant
12177821
The evolution of wireless communication to fifth generation (5G) and sixth generation (6G) standards and technologies provides higher data rates and greater capacity, with improved reliability and lower latency, which enhances mobile broadband services. 5G and 6G technologies also provide new classes of services for vehicular, fixed wireless broadband, and the Internet of Things (IoT).
A unified air interface, which utilizes licensed, unlicensed, and shared license radio spectrum, in multiple frequency bands, is one aspect of enabling the capabilities of 5G and 6G systems. The 5G and 6G air interface utilizes radio spectrum in bands below 1 GHz (sub-gigahertz), below 6 GHz (sub-6 GHz), and above 6 GHz. Radio spectrum above 6 GHz includes millimeter wave (mmWave) frequency bands that provide wide channel bandwidths to support higher data rates for wireless broadband.
To increase data rates, throughput, and reliability for a user equipment, 5G and 6G systems support various forms of wireless connectivity that use multiple radio links between base stations and the user equipment. Techniques such as dual connectivity (DC) or coordinated multipoint (CoMP) communications, often coupled with beamformed signals, can improve data rates, throughput, and reliability, especially as received signal strengths decease for the user equipment near the edge of cells. The use of these radio link configurations increases the complexity of mobility management to maintain high data rates and reliability for the user equipment.
Conventional mobility management techniques are based on base station neighbor relationships and use handovers to maintain connectivity for the user equipment. However, conventional handover techniques do not account for internal conditions or states of the user equipment that require mitigation, such as a thermal condition in the user equipment or battery capacity of the user equipment.
This summary is provided to introduce simplified concepts of dynamic carrier subband operation for active coordination sets. The simplified concepts are further described below in the Detailed Description. This summary is not intended to identify essential features of the claimed subject matter, nor is it intended for use in determining the scope of the claimed subject matter.
In some aspects, a method for coordinating joint communication with a user equipment (UE) by a master base station of a first Active Coordination Set (ACS) is described in which the master base station selects a first carrier subband associated with the first ACS for joint communication with the UE, coordinates the joint communication for the UE with other base stations in the first ACS, and monitors the joint communication with the UE. Based on the monitoring the joint communication, the master base station selects a second carrier subband that is associated with a second ACS for the joint communication with the UE and coordinates with base stations associated with the second ACS to jointly communicate with the UE using the second carrier subband.
In another aspect, a network device is described that is configured for coordinating joint communication with a user equipment (UE) using one or more Active Coordination Sets. The network device includes a processor and memory system to implement a joint communication scheduler application. The joint communication scheduler application is configured to select a first carrier subband associated with the first ACS for joint communication with the UE, to coordinate, using the Xn interface, the joint communication for the UE with other base stations in the first ACS, and to monitor the joint communication with the UE. The joint communication scheduler application is configured to, based on the monitoring of the joint communication, select a second carrier subband that is associated with a second ACS for the joint communication with the UE and to coordinate, using the Xn interface, with base stations associated with the second ACS to jointly communicate with the UE using the second carrier subband.
In another aspect, a network device is described that is configured for performing any of the methods disclosed herein. In yet another aspect, processor-readable medium is described that comprises instructions which, when executed by one or more processors, cause a device including the one or more processors to perform any of the methods disclosed herein.
Aspects of dynamic carrier subband operation for active coordination sets are described with reference to the following drawings. The same numbers are used throughout the drawings to reference like features and components:
This document describes methods, devices, systems, and means for dynamic carrier subband operation for active coordination sets. A master base station selects a first carrier subband associated with a first Active Coordination Set (ACS) for joint communication with a user equipment (UE), coordinates the joint communication for the UE with other base stations in the first ACS, and monitors the joint communication with the UE. Based on the monitoring of the joint communication, the master base station selects a second carrier subband that is associated with a second ACS for the joint communication with the UE and coordinates with base stations associated with the second ACS to jointly communicate with the UE using the second carrier subband.
In aspects, an Active Coordination Set (ACS) is a user equipment-specific set of base stations (e.g., 5G and/or 6G base stations) usable for wireless communication by the user equipment. The ACS may be a component of, or used to implement, a user-centric no-cell (UCNC) network architecture. More specifically, the base stations that are included in the ACS are usable for joint communication (coordinated communication), which includes joint transmission, joint reception, or joint transmission and joint reception between the user equipment and one or more of the base stations in the ACS. The joint transmission and/or reception techniques include CoMP, Single Radio Access Technology (RAT) Dual Connectivity (single-RAT DC), and/or Multi-Radio Access Technology Dual Connectivity (MR-DC).
As channel conditions change for the user equipment, the user equipment, a master base station, and/or a core network function can add or remove base stations from the ACS while the user equipment concurrently communicates with base stations in the ACS that provide usable link quality. Based on these changes to the ACS, the master base station can add or remove base stations from the joint communication with the user equipment without performing a handover that interrupts data communication with the user equipment.
In aspects, a UE and/or an ACS Server can create multiple ACSs for that particular UE. The UE can operate using one or more ACSs. The UE can use the ACSs independently (e.g., use one ACS at a time) for communication with a Radio Access Network (RAN). The UE can operate using multiple ACSs concurrently, either by using each ACS for a separate communication link with the RAN or by using multiple ACSs cooperatively to support a single communication link with the RAN.
In further aspects, an ACS can be created, maintained, and used based on a variety of factors. A RAN may include radio spectrum from various radio bands (subbands), such as radio spectrum in a below 1 GHz (sub-gigahertz) band, a below 6 GHz (sub-6 GHz) band, and an above-6 GHz band that includes millimeter wave (mmWave) frequencies. For example, one factor for ACS creation and use is based on radio frequencies. A first ACS can include a carrier subband(s) in the sub-gigahertz band that provides coverage of relatively larger geographic areas than a second ACS for a carrier subband(s) at a higher radio frequency (RF). A carrier subband can be related to a portion of a radio band, such as a lower-frequency portion of a radio band that has different propagation characteristics than a higher-frequency portion of the same radio band.
In another aspect, an ACS can be created, maintained, and used based on the channel bandwidth supported in a carrier subband. For example, a first ACS can include a carrier subband(s) in mmWave RF spectrum that provides wide channel bandwidths to support higher data rates than a second ACS for a carrier subband(s) in the sub-gigahertz band that only supports relatively-narrower channel bandwidths with inherently lower data rates.
In further aspects, ACSs can be created, maintained, and used based on other factors, such as: a first ACS used for control-plane signaling and a second ACS(s) used for user-plane data communication, a first ACS used for uplink (UL) communication and a second ACS used for downlink (DL) communication, or a first ACS used when the UE is in a disengaged mode and a second ACS(s) used when the UE is in an engaged mode. For example, the first ACS may include lower-frequency carrier subbands to provide more-reliable control-plane signaling using narrower channels and lower-order modulation and coding schemes (MCS) and the second ACS may include a carrier subband(s) that provides wider channels and higher data rates for user-plane data communication.
In another example, the first ACS may include a carrier subband(s) with narrower channel bandwidths for uplink (UL) data communication and the second ACS may include a carrier subband(s) that provides wider channels and higher data rates for downlink (DL) communications. In a further example, the first ACS may include lower-frequency carrier subbands for use when the UE is in the disengaged mode to reduce UE power consumption by enabling the UE to operate at lower frequencies and the second ACS may include a carrier subband(s) that provides wider channels and higher data rates when the UE is in the engaged mode to support higher data-rate communication.
In one aspect, by providing support in the UE for multiple ACSs and dynamic switching between ACSs, the complexity of UE implementations can be reduced. For example, bandwidth switching decisions can be made by a master base station that monitors UE communications, such as DL data buffered in the RAN for the UE, and dynamically switches the UE from a lower-bandwidth ACS (e.g., an ACS with a carrier subband with a 1 MHz channel bandwidth) to a higher-bandwidth ACS (e.g., an ACS with a carrier subband with a 10 MHz or 100 MHz channel bandwidth).
In another aspect, by providing support in the UE for multiple ACSs and dynamic switching between ACSs, thermal and power constraints of the UE can be balanced against control-plane signaling and user-plane data communication. For example, if the UE determines that is constrained by power (e.g., low battery capacity) or thermal (e.g., an overheating condition in the UE) considerations, the master base station can dynamically switch the UE to an ACS that reduces power consumption or heat generation for the UE, such an ACS in a lower RF band, narrower channel bandwidths, and/or lower-order MCS.
In aspects, a carrier subband can be any portion of radio spectrum available in a RAN. The carrier subband can be an RF band (e.g., the sub-gigahertz band, the sub-6 GHz band, or the above-6 GHz band), a portion, subband, or bandwidth part of an RF band, a portion of an RF band that is allocated for channels of a specific bandwidth (e.g., 1 MHz, 10 MHz, or 100 MHz channel bandwidths), channels with a particular numerology in an RF band, and so forth.
In other aspects, a master base station (or an ACS Server acting as a controller for base stations in an ACS) can select and switch the ACS(s) for the UE based on one or more factors. For example, the master base station may select an ACS(s) based on one or more of: UE capability information received from the UE; DL data queued for the UE; a buffer status for UL data pending for transmission by the UE; a request from the UE based on a UE-related state, such as a thermal or power condition in the UE; network resource scheduling needs of the RAN; link quality measurements; or any other suitable factor(s).
In other aspects, the UE can switch from communicating using a single ACS to using another single ACS, switch from communicating using a single ACS to using multiple ACSs, or switch from communicating using multiple ACSs to using a single ACS. Switching between ACSs can be coordinated between master base stations for each of the ACSs using peer-to-peer communication (e.g., using an Xn interface), or a controller, such as an ACS Server, can coordinate with the master base stations in the ACSs to direct the switching of the UE between ACSs.
While features and concepts of the described systems and methods for dynamic carrier subband operation for active coordination sets can be implemented in any number of different environments, systems, devices, and/or various configurations, aspects of dynamic carrier subband operation for active coordination sets are described in the context of the following example devices, systems, and configurations.
The base stations 120 communicate with the user equipment 110 via the wireless links 131 and 132, which may be implemented as any suitable type of wireless link. The wireless links 131 and 132 can include a downlink of data and control information communicated from the base stations 120 to the user equipment 110, an uplink of other data and control information communicated from the user equipment 110 to the base stations 120, or both. The wireless links 130 may include one or more wireless links or bearers implemented using any suitable communication protocol or standard, or combination of communication protocols or standards such as 3rd Generation Partnership Project Long-Term Evolution (3GPP LTE), Fifth Generation New Radio (5G NR), 6G, and so forth. Multiple wireless links 130 may be aggregated in a carrier aggregation to provide a higher data rate for the user equipment 110. Multiple wireless links 130 from multiple base stations 120 may be configured for Coordinated Multipoint (CoMP) communication with the user equipment 110. Additionally, multiple wireless links 130 may be configured for single-radio access technology (RAT) (single-RAT) dual connectivity (single-RAT-DC) or multi-RAT dual connectivity (MR-DC).
The base stations 120 are collectively a Radio Access Network 140 (RAN, Evolved Universal Terrestrial Radio Access Network, E-UTRAN, 5G NR RAN or NR RAN). The base stations 121 and 122 in the RAN 140 are connected to a core network 150, such as a Fifth Generation Core (5GC) or 6G core network. The base stations 121 and 122 connect, at 102 and 104 respectively, to the core network 150 via an NG2 interface (or a similar 6G interface) for control-plane signaling and via an NG3 interface (or a similar 6G interface) for user-plane data communications. In addition to connections to core networks, base stations 120 may communicate with each other via an Xn Application Protocol (XnAP), at 112, to exchange user-plane and control-plane data. The user equipment 110 may also connect, via the core network 150, to public networks, such as the Internet 160 to interact with a remote service 170.
The user equipment 110 also includes processor(s) 212 and computer-readable storage media 214 (CRM 214). The processor 212 may be a single core processor or a multiple core processor composed of a variety of materials, such as silicon, polysilicon, high-K dielectric, copper, and so on. The computer-readable storage media described herein excludes propagating signals. CRM 214 may include any suitable memory or storage device such as random-access memory (RAM), static RAM (SRAM), dynamic RAM (DRAM), non-volatile RAM (NVRAM), read-only memory (ROM), or Flash memory useable to store device data 216 of the user equipment 110. The device data 216 includes user data, multimedia data, beamforming codebooks, applications, and/or an operating system of the user equipment 110, which are executable by processor(s) 212 to enable user-plane communication, control-plane signaling, and user interaction with the user equipment 110.
In some implementations, the CRM 214 may also include an active coordination set (ACS) manager 218. The ACS manager 218 can communicate with the antennas 202, the RF front end 204, the LTE transceiver 206, the 5G NR transceiver 208, and/or the 6G transceiver 210 to monitor the quality of the wireless communication links 130.
The device diagram for the base stations 120, shown in
The base stations 120 also include processor(s) 262 and computer-readable storage media 264 (CRM 264). The processor 262 may be a single core processor or a multiple core processor composed of a variety of materials, such as silicon, polysilicon, high-K dielectric, copper, and so on. CRM 264 may include any suitable memory or storage device such as random-access memory (RAM), static RAM (SRAM), dynamic RAM (DRAM), non-volatile RAM (NVRAM), read-only memory (ROM), or Flash memory useable to store device data 266 of the base stations 120. The device data 266 includes network scheduling data, radio resource management data, beamforming codebooks, applications, and/or an operating system of the base stations 120, which are executable by processor(s) 262 to enable communication with the user equipment 110.
CRM 264 also includes a joint communication scheduler 268. Alternately or additionally, the joint communication scheduler 268 may be implemented in whole or part as hardware logic or circuitry integrated with or separate from other components of the base stations 120. In at least some aspects, the joint communication scheduler 268 configures the LTE transceivers 256, the 5G NR transceivers 258, and the 6G transceiver(s) 260 for communication with the user equipment 110, as well as communication with a core network, such as the core network 150, and routing user-plane and control-plane data for joint communication. Additionally, the joint communication scheduler 268 may allocate air interface resources and schedule communications for the UE 110 and base stations 120 in the ACS when the base station 120 is acting as a master base station for the base stations 120 in the ACS.
The base stations 120 include an inter-base station interface 270, such as an Xn and/or X2 interface, which the joint communication scheduler 268 configures to exchange user-plane and control-plane data between other base stations 120, to manage the communication of the base stations 120 with the user equipment 110. The base stations 120 include a core network interface 272 that the joint communication scheduler 268 configures to exchange user-plane and control-plane data with core network functions and/or entities.
In example operations generally, the base stations 120 allocate portions (e.g., the resource units 304) of the air interface resource 302 for uplink and downlink communications. Each resource block 310 of network access resources may be allocated to support respective wireless communication links 130 of multiple user equipment 110. In the lower left corner of the grid, the resource block 311 may span, as defined by a given communication protocol, a specified frequency range 306 and comprise multiple subcarriers or frequency sub-bands. The resource block 311 may include any suitable number of subcarriers (e.g., 12) that each correspond to a respective portion (e.g., 15 kHz) of the specified frequency range 306 (e.g., 180 kHz). The resource block 311 may also span, as defined by the given communication protocol, a specified time interval 308 or time slot (e.g., lasting approximately one-half millisecond or 7 orthogonal frequency-division multiplexing (OFDM) symbols). The time interval 308 includes subintervals that may each correspond to a symbol, such as an OFDM symbol. As shown in
In example implementations, multiple user equipment 110 (one of which is shown) are communicating with the base stations 120 (one of which is shown) through access provided by portions of the air interface resource 302. The joint communication scheduler 268 (shown in
Additionally, or in the alternative to block-level resource grants, the joint communication scheduler 268 may allocate resource units at an element-level. Thus, the joint communication scheduler 268 may allocate one or more resource elements 320 or individual subcarriers to different user equipment 110. By so doing, one resource block 310 can be allocated to facilitate network access for multiple user equipment 110. Accordingly, the joint communication scheduler 268 may allocate, at various granularities, one or up to all subcarriers or resource elements 320 of a resource block 310 to one user equipment 110 or divided across multiple user equipment 110, thereby enabling higher network utilization or increased spectrum efficiency.
The joint communication scheduler 268 can therefore allocate air interface resource 302 by resource unit 304, resource block 310, frequency carrier, time interval, resource element 320, frequency subcarrier, time subinterval, symbol, spreading code, some combination thereof, and so forth. Based on respective allocations of resource units 304, the joint communication scheduler 268 can transmit respective messages to the multiple user equipment 110 indicating the respective allocation of resource units 304 to each user equipment 110. Each message may enable a respective user equipment 110 to queue the information or configure the LTE transceiver 206, the 5G NR transceiver 208, and/or the 6G transceiver 210 to communicate via the allocated resource units 304 of the air interface resource 302.
The UE 110 operates according to different resource control states 410. Different situations may occur that cause the UE 110 to transition between the different resource control states 410 as determined by the radio access technology. Examples of the resource control states 410 illustrated in
In establishing an RRC connection, the user equipment 110 may transition from the idle mode 414 to the connected mode 412. After establishing the connection, the user equipment 110 may transition (e.g., upon connection inactivation) from the connected mode 412 to an inactive mode 416 (e.g., RRC inactive mode, RRC INACTIVE state, NR-RRC INACTIVE state) and the user equipment 110 may transition (e.g., via an RRC connection resume procedure) from the inactive mode 416 to the connected mode 412. After establishing the connection, the user equipment 110 may transition between the connected mode 412 to an idle mode 414 (e.g., RRC idle mode, RRC_IDLE state, NR-RRC IDLE state, E-UTRA RRC IDLE state), for instance upon the network releasing the RRC connection. Further, the user equipment 110 may transition between the inactive mode 416 and the idle mode 414.
Further, the UE 110 may be in an engaged mode 422 or may be in a disengaged mode 424. As used herein, an engaged mode 422 is a connected mode (e.g., the connected mode 412) and a disengaged mode 424 is an idle, disconnected, connected-but-inactive, or connected-but-dormant mode (e.g., idle mode 414, inactive mode 416). In some cases, in the disengaged mode 424, the UE 110 may still be Network Access Stratum (NAS) registered with radio bearer active (e.g., inactive mode 416). In simple terms, an engaged mode may signify that an ongoing wireless connection has been established between the UE 110 and a base station 120, whereas a disengaged mode may signify a state in which there is no ongoing wireless connection between the UE 110 and a base station 120.
Each of the different resource control states 410 may have different quantities or types of resources available, which may affect power consumption within the UE 110. In general, the connected mode 412 represents the UE 110 actively connected to (engaged with) the base station 120. In the inactive mode 416, the UE 110 suspends connectivity with the base station 120 and retains information that enables connectivity with the base station 120 to be quickly re-established. In the idle mode 414 the UE 110 releases the connection with the base station 120.
Some of the resource control states 410 may be limited to certain radio access technologies. For example, the inactive mode 416 may be supported in LTE Release 15 (eLTE), 5G NR, and 6G, but not in 3G or previous generations of 4G standards. Other resource control states may be common or compatible across multiple radio access technologies, such as the connected mode 412 or the idle mode 414.
In aspects, dynamic carrier subband operation for active coordination sets is described with which the user equipment 110, while in the engaged mode 422, measures the link quality of candidate base stations 120 to determine which base stations 120 to include in the ACS.
For example, the user equipment 110 follows a path 502 through the RAN 140 while periodically measuring the link quality of base stations 120 that are currently in the ACS and candidate base stations 120 that the UE 110 may add to the ACS. For example, at position 504, the ACS at 506 includes the base stations 121, 122, and 123. As the UE 110 continues to move, at position 508, the UE 110 has deleted base station 121 and base station 122 from the ACS and added base stations 124, 125, and 126, as shown at 510. Continuing along the path 502, the UE 110, at position 512, has deleted the base stations 123 and 124 and added the base station 127, as shown in the ACS at 514.
The master base station schedules air interface resources for the joint communication between the UE 110 and the base stations 121, 122, and 123, based on the ACS associated with the UE 110. The master base station (base station 121) connects, via an N3 interface 601 (or a 6G equivalent interface) to the User Plane Function 610 (UPF 610) in the core network 150 for the communication of user-plane data to and from the user equipment 110. The master base station distributes the user-plane data to all the base stations in the joint communication via the Xn interfaces 112. The UPF 610 is further connected to a data network, such as the Internet 160 via the N6 interface 602. All of the base stations 120 in the ACS or any subset of the base stations 120 in the ACS can send downlink data to the UE 110. All of the base stations 120 in the ACS or any subset of the base stations 120 in the ACS can receive uplink data from the UE 110.
When the user equipment 110 creates or modifies an ACS, the user equipment 110 indirectly communicates the created ACS, or the ACS modification, to an ACS Server 620 that stores the ACS for each user equipment 110 operating in the RAN 140. Although shown in the core network 150, alternatively the ACS Server 620 may be an application server located outside the core network 150. The user equipment 110 communicates the ACS or ACS modification via the master base station (base station 121) which is connected to the ACS Server 620 via an N-ACS interface 603. Optionally or alternatively, the user equipment 110 communicates the created ACS or ACS modification to the ACS Server 620 via the Access and Mobility Function 630 (AMF 630) which is connected to the master base station (base station 121) via an N2 interface 604. The AMF 630 relays ACS-related communications to and from the ACS Server 620 via an ACS-AMF interface 605. ACS data between the user equipment 110 and the ACS Server 620 can be communicated via Radio Resource Control (RRC) communications, Non-Access Stratum (NAS) communications, or application-layer communications.
The ACS Server 620 may be implemented as a single network node (e.g., a server). Alternatively, the functionality of the ACS Server 620 may be distributed across multiple network nodes and/or devices and may be distributed in any fashion suitable to perform the functions described herein. The ACS Server 620 includes processor(s) and computer-readable storage media. The processor may be a single core processor, or a multiple core processor composed of a variety of materials, such as silicon, polysilicon, high-K dielectric, copper, and so on. CRM may include any suitable memory or storage device such as random-access memory (RAM), static RAM (SRAM), dynamic RAM (DRAM), non-volatile RAM (NVRAM), read-only memory (ROM), hard disk drives, or Flash memory useful to ACS and related data. The CRM includes applications and/or an operating system of the ACS Server 620, which are executable by the processor(s) to enable communication with the user equipment 110, the master base station 121, and the AMF 630. The ACS Server 620 includes one or more network interfaces for communication with the master base station 121, the AMF 630, and other devices in the core network 150, the user equipment 110, and/or devices in the RAN 140.
Whenever the ACS content changes for any particular user equipment 110, the ACS Server 620 sends a copy of the modified ACS to the master base station (base station 121) for that UE. The master base station uses the ACS to schedule air interface resources for joint communication with the user equipment 110. For example, when a new base station is added to the ACS or an existing base station in the ACS is deleted, the master base station allocates air interface resources for the new base station to participate in the joint communication or deallocates resources for the deleted base station. The master base station relays user-plane data based on the ACS received from the ACS Server 620. Continuing with the example, the master base station starts routing user-plane data to the new base station added to the ACS or terminates relaying data to the existing base station that was removed from the ACS.
In aspects, the initial ACS for the user equipment 110 can be established by the UE 110 during or after the UE 110 performs the attach procedure to connect to the RAN 140. For example, the UE 110 can initialize the ACS with the base stations 120 included in the neighbor relation table of the base station through which the UE 110 attaches to the RAN 140. In another example, the UE 110 considers the base stations 120 included in the neighbor relation table as candidates for the ACS and the measures the link quality of each candidate base station before adding a candidate base station to the ACS. In a further example, the user equipment 110 queries the ACS Server 620 for the last ACS used by the user equipment 110. The UE 110 then validates the entries in the last-used ACS to determine which, if any, entries of the last-used ACS are usable for communication and inclusion in the ACS. In another example, the UE 110, measures the link quality of any base stations 120 from the previous ACS that are within communication range and populates the ACS with one or more of the base stations 120 that exceed a threshold for inclusion (e.g., above a threshold for a Received Signal Strength Indicator (RSSI), a Reference Signal Received Power (RSRP), or a Reference Signal Received Quality (RSRQ)).
The user equipment 110 adds or deletes a base station 120 from the ACS by sending an ACS modification message to the ACS Server 620. The ACS modification message includes an identifier for a base station to add or delete from the ACS along with and indicator to either add or delete the identified base station. Optionally, or additionally, the ACS modification message may include identifiers of multiple base stations with corresponding add/delete indicators for each base station. Other information useful to the management of the ACS may be stored in or with the ACS, such as timestamps for entries in the ACS, geographic location information from the UE, a UE identifier, identification information for the current master base stations, and the like.
The ACS Server 620 receives the ACS modification message from the UE 110 (via the current master base station) and performs the requested modification to an ACS record for the UE 110 that is stored by the ACS Server 620. After receiving the ACS modification message, the ACS Server 620 sends a modified copy of the ACS for the UE 110 to the master base station (base station 121) via the N-ACS interface 603. Optionally or alternatively, the ACS Server 620 may send only the modification of the ACS to the master base station which causes the master base station to update its copy of the ACS. The joint communication scheduler 268 in the master base station uses the updated or modified ACS to modify the scheduling of resources and joint communications for the base stations 120 in the ACS. The master base station can perform real-time scheduling of resources within the ACS of the user equipment 110 to respond to changing channel conditions or communication requirements with low latency requirements.
In aspects, in addition to the UE 110 creating and maintaining an ACS based on link quality at the location of the UE 110 as described above with respect to
For example, the base stations 121, 122, and 126 operate in a first frequency band, such as the sub-gigahertz band or the sub-6 GHz band, and base stations 123, 124, and 125 operate in the above 6 GHz band, such as the mmWave frequency band. The UE 110 maintains two ACSs shown at 702. At the current location of the UE 110, the UE 110 has included the base stations 121, 122, and 126 in a “Band 1” ACS for communications between the UE 110 and the RAN 140 in the first frequency band, such as the sub-gigahertz band. The UE 110 has also included the base stations 123, 124, and 125 in a “Band 2” ACS for communications between the UE 110 and the RAN 140 in the second frequency band, such as the above 6 GHz band. Although two ACSs are illustrated in
For example, the base stations 121 and 127 operate in a first frequency band, such as the sub-gigahertz band, with radio propagation characteristics that support wireless communication over longer geographic distances between the UE 110 and the base stations 121 and 127. The base stations 122 and 126 operate in the sub-6 GHz band that supports higher data throughput than the sub-GHz band but over shorter distances. The base stations 123, 124, and 125 operate in the above 6 GHz band, such as the mmWave frequency band, with even higher data throughput but over even shorter distances.
Continuing with the example, the UE 110 has created four ACSs shown at 802. At the current location of the UE 110, the UE 110 has included the base stations 121 and 127 in a first (“Band 1 CP”) ACS for control-plane communications that require relatively lower bandwidths and benefit from the higher link budget in the sub-GHz band to improve reliability of control-plane communications for the UE 110. The UE 110 can use the first ACS for control-plane signaling related to user-plane communication in the sub-GHz band or in relation to user-plane communication in any combination of bands used by the UE 110.
The UE 110 has created the three remaining ACSs at 802 for user-plane communication. The UE 110 created the second (“Band 1 UP”) ACS for user-plane communication in the sub-GHz band, the third (“Band 2 UP”) ACS for user-plane communication in the sub-6 GHz band, the fourth, (“Band 3 UP”) ACS for user-plane communication in the above-GHz band. Although four ACSs are illustrated in
For example, the base stations 121 and 127 operate in a first frequency band, such as the sub-gigahertz band, with radio propagation characteristics that support wireless communication over longer geographic distances between the UE 110 and the base stations 121 and 127. The base stations 122 and 126 operate in the sub-6 GHz band that supports higher data throughput than the sub-GHz band but over shorter distances. The base stations 123, 124, and 125 operate in the above-6 GHz band, such as the mmWave frequency band, with even higher data throughput but over even shorter distances.
Continuing with the example, the UE 110 has created four ACSs shown at 902. At the current location of the UE 110, the UE 110 has included the base station 121 in a first (“Band 1 Disengaged”) ACS for communication when the UE 110 is the disengaged mode 424. The UE 110 can reduce power consumption in the disengaged mode 424 by communicating in the sub-GHz band. The UE 110 has created the three remaining ACSs at 902 for communication in the engaged mode 422. The UE 110 created the second (“Band 1 Engaged”) ACS for communication in the engaged mode 422 in the sub-GHz band, the third (“Band 2 Engaged”) ACS for communication in the engaged mode 422 in the sub-6 GHz band, the fourth, (“Band 3 Engaged”) ACS for communication in the engaged mode 422 in the above-6 GHz band. Although four ACSs are illustrated in
As discussed above with respect to
In another aspect, the master base station can coordinate carrier subband operation based on operational characteristics of current and/or historic communications with the UE. The master base station can determine a configuration for carrier subband operation based on an amount of data currently buffered for transmission to the UE 110, a buffer status of data pending at the UE 110 for transmission, a history of recent DL and/or UL data communicated between the UE 110 and the RAN 140, or the like. For example, the master base station 121 determines that there is an amount of data (e.g., an amount of data that exceeds a threshold value) for DL transmission to the UE 110. Based on the ACS associated with the UE 110, the master base station 121 can configure the base stations 120 in the ACS to transmit using a wider channel bandwidth that supports a higher data rate in a first frequency band, or the master base station 120 can configure the base stations 120 in the currently-used ACS or in a different ACS associated with the UE 110 to transmit in a different frequency band that supports higher data rates.
The master base station can also combine an operational characteristic with the UE capability information to coordinate carrier subband operation. For example, the master base station 121 determines from the UE capability information that the UE 110 supports wider channel bandwidths in the above-6 GHz band (e.g., a 100 MHz channel bandwidth) compared to a narrower channel bandwidth in a lower frequency band (e.g., a 1 MHz or a 10 MHz channel bandwidth). Based on the operational characteristic of a large amount of DL data to transmit to the UE 110 and the UE capability information, the master base station 121 determines to configure base stations in an above-6 GHz band ACS of the UE 110 to transmit the DL data to the UE 110.
In a further aspect, the master base station can coordinate carrier subband operation based on a request from the UE 110. The request from the UE 110 can be based on a status of the UE 110. For example, the UE 110 determines that a power status (e.g., a low battery capacity) or a thermal characteristic (e.g., an overheating condition) can be mitigated by changing the ACS(s) currently in use. The master base station coordinates with the base stations 120 to terminate communication in a frequency band (e.g., a band with higher power consumption), to reduce a channel bandwidth (e.g., to a bandwidth that has a lower power consumption for the UE), to change to a modulation and coding scheme (MCS) that reduces power consumption for the UE, or a combination of these. In a similar aspect, another request from the UE may indicate that another change in status of the UE (e.g., the UE is connected to a charger or the UE overheating condition has been mitigated) now enables the UE to operate using an ACS configuration that consumes more power and/or produces more heat. The master base station can then coordinate with the base stations 120 to configure subband operation based on the change in UE status.
As discussed above, the UE 110 can be associated with different ACSs that include different sets of base stations 120. In another aspect, the UE 110 can operate using different carrier subbands from different ACSs. The UE and the base stations can use the different carrier subbands independently or cooperatively for communication between the RAN and the UE. The different carrier subbands can be in the same band-class or different band-classes (e.g., the sub-gigahertz band-class, the sub-6 GHz band class, or the above 6 GHz band class). For example, a first carrier subband associated with a first ACS (e.g., an ACS in the sub-gigahertz band) is used to communicate control-plane signaling for a second carrier subband associated with a second ACS (e.g., an ACS used for user-plane communication in the sub-6 GHz or the above 6 GHz band). In another example, DL data is transmitted using a first carrier subband associated with a first ACS, and acknowledgements for the DL data are transmitted in a second carrier subband associated with a second ACS.
In another aspect, UL and DL communications can use different carrier subbands, each of which is associated with a different ACS. A master base station for UL communication coordinates with the master base station for the DL communication. The master base stations coordinate control-plane signaling, acknowledgements and negative-acknowledgements of communications, and/or ACS management.
In a further aspect, a first ACS (the base stations in the first ACS) can send a carrier-subband switching command to the UE to request that the UE switch to another set of carrier subbands associated with a different ACS(s). For example, the ACS can include the carrier-subband switching command in DL control-plane signaling of the first ACS. The carrier-subband switching command includes control information such as an identifier of the other set of carrier subbands associated with the other ACS, a carrier subband configuration, or a time at which the switch to the different ACS should occur.
In another aspect, the UE 110 can switch from communicating using a single ACS to using another single ACS, switch from communicating using a single ACS to using multiple ACSs, or switch from communicating using multiple ACSs to using a single ACS. Switching between ACSs can be coordinated between master base stations 120 for each of the ACSs using peer-to-peer communication (e.g., using an Xn interface), or a controller, such as an ACS Server 620, can coordinate with the master base stations 120 in the ACSs to direct the switching of the UE 110 between ACSs.
In another aspect, the master base station for a first ACS (or alternatively the ACS Server 620 acting as a controller for the first ACS) can send a request to the UE 110 to perform an update procedure for a second carrier subband associated with a second ACS. For example, the master base station for a sub-GHz ACS or the ACS Server 620 sends an update request to the UE 110 to provide link quality measurements of base stations 120 in a second ACS that is associated with the above-6 GHz band. The link quality measurements include the UE 110 measuring a Received Signal Strength Indicator (RSSI), a Reference Signal Received Power (RSRP), or a Reference Signal Received Quality (RSRQ). Alternatively or additionally, the update request directs the UE 110 to transmit UL sounding signals and/or beam sweeps for measurement by base stations 120 in the second ACS.
Example method 1000 is described with reference to
At block 1004, the master base station coordinates the joint communication for the UE with other base stations in the first ACS. For example, the master base station communicates with other base stations in the first ACS to allocate resources for the joint communication, and/or forward user-plane data, and/or forward control-plane signaling to the other base stations, or the like. The joint communication includes using the first carrier subband selected at block 1004 for communication (e.g., coordinated multipoint communication) between the UE and a plurality of base stations in the first ACS. The joint communication may include any of uplink communication, downlink communication, or both.
At block 1006, the master base station monitors the joint communication with the UE. For example, the master base station monitors data traffic between the base stations in the first ACS and the UE by evaluating parameters such as data throughput, UE buffer status, buffered downlink data for the UE, RRC signaling from the UE, or the like, to monitor the status of the joint communication.
At block 1008, based on monitoring the joint communication, the master base station determines whether to select a second carrier subband for joint communication with the UE. For example, the master base station evaluates monitored parameters to determine whether to select the second carrier subband, such as a monitored parameter exceeding a threshold value or receiving a request from the UE to select the second carrier subband. If the master base station determines not to select a second carrier subband for the UE, the master base station continues to monitor the joint communication at block 1006.
At block 1010, based on determining to select the second carrier subband at block 1008, the master base station coordinates the joint communication for the UE with other base stations in the second ACS. For example, the master base station communicates with other base stations in the second ACS to allocate resources for the joint communication, and/or forward user-plane data, and/or forward control-plane signaling to the other base stations, or the like. The joint communication includes using the second carrier subband selected at block 1008 for communication (e.g., coordinated multipoint communication) between the UE and a plurality of base stations in the second ACS. The joint communication may include any of uplink communication, downlink communication, or both. The UE may use the second carrier subband to communicate with the base stations in the second ACS at the same time as using the first carrier subband to communicate with base stations in the first ACS. Alternatively, the UE may terminate communication with base stations in the first ACS when using communicating with the base stations in the second ACS.
In the following text some examples are described:
Although aspects of dynamic carrier subband operation for active coordination sets have been described in language specific to features and/or methods, the subject of the appended claims is not necessarily limited to the specific features or methods described. Rather, the specific features and methods are disclosed as example implementations of dynamic carrier subband operation for active coordination sets, and other equivalent features and methods are intended to be within the scope of the appended claims. Further, various different aspects are described, and it is to be appreciated that each described aspect can be implemented independently or in connection with one or more other described aspects.
This application is a national stage entry of International Application No. PCT/US2020/014638, filed Jan. 22, 2020, which claims the benefit of U.S. Provisional Application No. 62/797,885, filed Jan. 28, 2019, the disclosures which are incorporated herein by reference in their entirety.
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/US2020/014638 | 1/22/2020 | WO |
| Publishing Document | Publishing Date | Country | Kind |
|---|---|---|---|
| WO2020/159773 | 8/6/2020 | WO | A |
| Number | Name | Date | Kind |
|---|---|---|---|
| 6038448 | Chheda et al. | Mar 2000 | A |
| 6665521 | Gorday et al. | Dec 2003 | B1 |
| 6898430 | Liberti et al. | May 2005 | B1 |
| 8023463 | Dick et al. | Sep 2011 | B2 |
| 8315629 | Pamp et al. | Nov 2012 | B2 |
| 8483184 | Yokoyama et al. | Jul 2013 | B2 |
| 8665806 | Wang et al. | Mar 2014 | B2 |
| 8706156 | Han et al. | Apr 2014 | B2 |
| 8989125 | Marupaduga et al. | Mar 2015 | B1 |
| 9008678 | Schoenerstedt | Apr 2015 | B2 |
| 9100095 | Mantri | Aug 2015 | B2 |
| 9210550 | Koc et al. | Dec 2015 | B2 |
| 9253783 | Wang et al. | Feb 2016 | B2 |
| 9344159 | Zhuang | May 2016 | B2 |
| 9374772 | Daoud | Jun 2016 | B2 |
| 9380533 | Chung et al. | Jun 2016 | B2 |
| 9674863 | Cheng et al. | Jun 2017 | B2 |
| 9743329 | Xiao et al. | Aug 2017 | B2 |
| 9780842 | Boudreau et al. | Oct 2017 | B2 |
| 9941939 | Parl et al. | Apr 2018 | B2 |
| 9985750 | Maaref et al. | May 2018 | B2 |
| 10045376 | Yang et al. | Aug 2018 | B2 |
| 10218422 | Raghavan et al. | Feb 2019 | B2 |
| 10412691 | Marupaduga et al. | Sep 2019 | B1 |
| 10476577 | Wang et al. | Nov 2019 | B1 |
| 10834645 | Wang et al. | Nov 2020 | B2 |
| 10893572 | Wang et al. | Jan 2021 | B2 |
| 11224081 | Wang et al. | Jan 2022 | B2 |
| 11375527 | Eyuboglu et al. | Jun 2022 | B1 |
| 11804877 | Wang et al. | Oct 2023 | B2 |
| 12114394 | Wang et al. | Oct 2024 | B2 |
| 20030002460 | English | Jan 2003 | A1 |
| 20040203973 | Khan | Oct 2004 | A1 |
| 20060013185 | Seo et al. | Jan 2006 | A1 |
| 20060116156 | Haseba et al. | Jun 2006 | A1 |
| 20060128312 | Declerck et al. | Jun 2006 | A1 |
| 20060203731 | Tiedemann et al. | Sep 2006 | A1 |
| 20100027487 | Ihm et al. | Feb 2010 | A1 |
| 20100103983 | Wang et al. | Apr 2010 | A1 |
| 20100142462 | Wang et al. | Jun 2010 | A1 |
| 20100173660 | Liu et al. | Jul 2010 | A1 |
| 20100210246 | Yang | Aug 2010 | A1 |
| 20110080893 | Fong et al. | Apr 2011 | A1 |
| 20110096751 | Ma et al. | Apr 2011 | A1 |
| 20110124294 | Dwyer et al. | May 2011 | A1 |
| 20110158117 | Ho et al. | Jun 2011 | A1 |
| 20110281585 | Kwon et al. | Nov 2011 | A1 |
| 20120033571 | Shimezawa et al. | Feb 2012 | A1 |
| 20120083309 | Kwon et al. | Apr 2012 | A1 |
| 20120087273 | Koo et al. | Apr 2012 | A1 |
| 20120120821 | Kazmi et al. | May 2012 | A1 |
| 20120157139 | Noh et al. | Jun 2012 | A1 |
| 20120178462 | Kim | Jul 2012 | A1 |
| 20120218968 | Kim et al. | Aug 2012 | A1 |
| 20120264443 | Ng et al. | Oct 2012 | A1 |
| 20130034136 | Park et al. | Feb 2013 | A1 |
| 20130053045 | Chuang | Feb 2013 | A1 |
| 20130053079 | Kwun et al. | Feb 2013 | A1 |
| 20130089058 | Yang et al. | Apr 2013 | A1 |
| 20130107848 | Kang et al. | May 2013 | A1 |
| 20130130684 | Gomes et al. | May 2013 | A1 |
| 20130150106 | Bucknell et al. | Jun 2013 | A1 |
| 20130182628 | Gholmieh et al. | Jul 2013 | A1 |
| 20130225184 | Liu et al. | Aug 2013 | A1 |
| 20130242787 | Sun et al. | Sep 2013 | A1 |
| 20130244682 | Schoenerstedt | Sep 2013 | A1 |
| 20140010131 | Gaal et al. | Jan 2014 | A1 |
| 20140112184 | Chai | Apr 2014 | A1 |
| 20140127991 | Lim et al. | May 2014 | A1 |
| 20140148168 | Aoyagi et al. | May 2014 | A1 |
| 20140169201 | Tamura et al. | Jun 2014 | A1 |
| 20140169261 | Ming et al. | Jun 2014 | A1 |
| 20140274081 | Comeau et al. | Sep 2014 | A1 |
| 20140287759 | Purohit | Sep 2014 | A1 |
| 20140348104 | Morita | Nov 2014 | A1 |
| 20140376478 | Morita | Dec 2014 | A1 |
| 20150098397 | Damnjanovic et al. | Apr 2015 | A1 |
| 20150139197 | He et al. | May 2015 | A1 |
| 20150139203 | Miryala et al. | May 2015 | A1 |
| 20150163822 | Guo et al. | Jun 2015 | A1 |
| 20150195795 | Loehr et al. | Jul 2015 | A1 |
| 20150244429 | Zhang et al. | Aug 2015 | A1 |
| 20150244489 | Wang | Aug 2015 | A1 |
| 20150288427 | Wang et al. | Oct 2015 | A1 |
| 20150326282 | Futaki | Nov 2015 | A1 |
| 20150373730 | Fujishiro et al. | Dec 2015 | A1 |
| 20160021526 | Niu et al. | Jan 2016 | A1 |
| 20160028448 | Park et al. | Jan 2016 | A1 |
| 20160037511 | Vincze et al. | Feb 2016 | A1 |
| 20160044634 | Seo et al. | Feb 2016 | A1 |
| 20160128123 | Li | May 2016 | A1 |
| 20160174278 | Gao et al. | Jun 2016 | A1 |
| 20160192420 | Kim et al. | Jun 2016 | A1 |
| 20160192433 | Deenoo et al. | Jun 2016 | A1 |
| 20160219475 | Kim | Jul 2016 | A1 |
| 20160323832 | Love et al. | Nov 2016 | A1 |
| 20170070931 | Huang et al. | Mar 2017 | A1 |
| 20170078333 | Tevlin | Mar 2017 | A1 |
| 20170105147 | Jiang et al. | Apr 2017 | A1 |
| 20170164252 | Chaudhuri et al. | Jun 2017 | A1 |
| 20170188406 | Baligh et al. | Jun 2017 | A1 |
| 20170230986 | Moon et al. | Aug 2017 | A1 |
| 20170238271 | Viorel et al. | Aug 2017 | A1 |
| 20170250786 | Better et al. | Aug 2017 | A1 |
| 20170148173 | Yang | Sep 2017 | A1 |
| 20170272345 | Viorel et al. | Sep 2017 | A1 |
| 20170289893 | Manna | Oct 2017 | A1 |
| 20170332389 | Sun et al. | Nov 2017 | A1 |
| 20170339530 | Maaref | Nov 2017 | A1 |
| 20170347277 | Zhang et al. | Nov 2017 | A1 |
| 20170359759 | Brown et al. | Dec 2017 | A1 |
| 20180152951 | Zhuang et al. | May 2018 | A1 |
| 20180213450 | Futaki | Jul 2018 | A1 |
| 20180219667 | Zhao et al. | Aug 2018 | A1 |
| 20180220403 | Wilson et al. | Aug 2018 | A1 |
| 20180235020 | Maaref | Aug 2018 | A1 |
| 20180270895 | Park et al. | Sep 2018 | A1 |
| 20180352511 | Martin et al. | Dec 2018 | A1 |
| 20190028348 | Chai | Jan 2019 | A1 |
| 20190053235 | Novlan et al. | Feb 2019 | A1 |
| 20190075604 | Wang et al. | Mar 2019 | A1 |
| 20190081657 | Zeng et al. | Mar 2019 | A1 |
| 20190082331 | Raghavan et al. | Mar 2019 | A1 |
| 20190165843 | Wu et al. | May 2019 | A1 |
| 20190174346 | Murray et al. | Jun 2019 | A1 |
| 20190174472 | Lee et al. | Jun 2019 | A1 |
| 20190253106 | Raghavan et al. | Aug 2019 | A1 |
| 20190312616 | Christoffersson et al. | Oct 2019 | A1 |
| 20200015192 | Chun | Jan 2020 | A1 |
| 20200145061 | Black | May 2020 | A1 |
| 20200154442 | Zhou | May 2020 | A1 |
| 20200178131 | Wang et al. | Jun 2020 | A1 |
| 20200187281 | Wang et al. | Jun 2020 | A1 |
| 20200196388 | Zhang et al. | Jun 2020 | A1 |
| 20200220603 | Hao et al. | Jul 2020 | A1 |
| 20200374970 | Wang et al. | Nov 2020 | A1 |
| 20210029516 | Wang et al. | Jan 2021 | A1 |
| 20210068123 | Zhu et al. | Mar 2021 | A1 |
| 20210385903 | Wang et al. | Dec 2021 | A1 |
| 20210391897 | Wang et al. | Dec 2021 | A1 |
| 20220030414 | Wang et al. | Jan 2022 | A1 |
| 20220038985 | Deeno et al. | Feb 2022 | A1 |
| 20220039160 | Wang et al. | Feb 2022 | A1 |
| 20220110181 | Miao | Apr 2022 | A1 |
| 20220311577 | Matsummura et al. | Sep 2022 | A1 |
| Number | Date | Country |
|---|---|---|
| 101764634 | Jun 2010 | CN |
| 101867451 | Oct 2010 | CN |
| 102474743 | May 2012 | CN |
| 103959672 | Jul 2014 | CN |
| 104067660 | Sep 2014 | CN |
| 105873124 | Aug 2016 | CN |
| 106879051 | Jun 2017 | CN |
| 107431962 | Dec 2017 | CN |
| 107736048 | Feb 2018 | CN |
| 107872889 | Apr 2018 | CN |
| 108140035 | Jun 2018 | CN |
| 2809104 | Dec 2014 | EP |
| 2953393 | Dec 2015 | EP |
| 3282786 | Feb 2018 | EP |
| 3701638 | Sep 2020 | EP |
| 0237771 | May 2002 | WO |
| 2008147654 | Dec 2008 | WO |
| 2012114151 | Aug 2012 | WO |
| 2013091229 | Jun 2013 | WO |
| 2014074919 | May 2014 | WO |
| 2014179958 | Nov 2014 | WO |
| 2015074270 | May 2015 | WO |
| 2015163798 | Oct 2015 | WO |
| 2016081375 | May 2016 | WO |
| 2016191091 | Dec 2016 | WO |
| 2017117340 | Jul 2017 | WO |
| 2017148173 | Sep 2017 | WO |
| 2018004278 | Jan 2018 | WO |
| 2018010818 | Jan 2018 | WO |
| 2018020015 | Feb 2018 | WO |
| 2018031770 | Feb 2018 | WO |
| 2018073485 | Apr 2018 | WO |
| 2018130115 | Jul 2018 | WO |
| 2018169343 | Sep 2018 | WO |
| 2018202797 | Nov 2018 | WO |
| 2018202798 | Nov 2018 | WO |
| 2019001039 | Jan 2019 | WO |
| 2019016141 | Jan 2019 | WO |
| 2019038700 | Feb 2019 | WO |
| 2018025789 | May 2019 | WO |
| 2020112680 | Jun 2020 | WO |
| 2020113010 | Jun 2020 | WO |
| 2020117558 | Jun 2020 | WO |
| 2020139811 | Jul 2020 | WO |
| 2020142532 | Jul 2020 | WO |
| 2020159773 | Aug 2020 | WO |
| 2020172022 | Aug 2020 | WO |
| 2020172372 | Aug 2020 | WO |
| 2020186097 | Sep 2020 | WO |
| 2020236429 | Nov 2020 | WO |
| 2021015774 | Jan 2021 | WO |
| 2021029879 | Feb 2021 | WO |
| 2021054963 | Mar 2021 | WO |
| 2021054964 | Mar 2021 | WO |
| Entry |
|---|
| “Foreign Office Action”, IN Application No. 202147024718, Feb. 28, 2022, 5 pages. |
| “Foreign Office Action”, IN Application No. 202147017729, Mar. 9, 2022, 6 pages. |
| “Foreign Office Action”, CN Application No. 201980069427.8, Oct. 18, 2021, 12 pages. |
| “International Preliminary Report on Patentability”, Application No. PCT/US2019/063620, May 25, 2021, 8 pages. |
| “Notice of Allowance”, U.S. Appl. No. 16/210,969, filed Oct. 26, 2021, 5 pages. |
| “Extended European Search Report”, EP Application No. 22194393.9, Jan. 26, 2023, 6 pages. |
| “Foreign Office Action”, EP Application No. 19845895.2, Dec. 13, 2022, 7 pages. |
| “International Preliminary Report on Patentability”, Application No. PCT/US2019/063081, May 25, 2021, 9 pages. |
| “International Preliminary Report on Patentability”, Application No. PCT/US2020/014638, Jul. 27, 2021, 7 pages. |
| “Non-Final Office Action”, U.S. Appl. No. 16/210,969, filed Jun. 24, 2021, 19 pages. |
| “3GPP TS 24.501 V16.3.0”, 3GPP TS 24.501 version 16.3.0, Dec. 2019, 645 pages. |
| 3GPP TSG RAN WG4 25.942 V2.0.0: “RF System Scenarios”, TSG RAN Working Group 4 (Radio) Meeting #8, Oct. 1999, 65 pages. |
| “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Security architecture and procedures for 5G system”, 3GPP TS 33.501 version 16.1.0 Release 16, Dec. 2019, 202 pages. |
| “5G; Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3”, 3GPP TS 24.501 version 15.1.0 Release 15, Oct. 2018, 406 pages. |
| “5G; Study on New Radio (NR) Access Technology”, ETSI TR 138 912; V14.0.0; Technical Report; 3GPP TR 38.912 version 14.0.0 Release 14, May 2017, 77 pages. |
| “Beam Management and Beam Reporting”, 3GPP TSG RAN WG1 Meeting #88bis, R1-1704488, Spokane, Washington, USA Apr. 3-7, 2017, Apr. 2017, 7 pages. |
| “Corrected Notice of Allowance”, U.S. Appl. No. 16/419,854, filed Dec. 16, 2020, 2 pages. |
| “Discussion on HARQ Management and HARQ-ACK Feedback”, 3GPP TSG RAN WG1 Meeting #91, R1-1720203, Reno, USA, Nov. 27-Dec. 1, 2017, 5 pages. |
| “Discussion on NR Beamforming with UE-Group-Specific Beam Sweeping”, 3GPP TSG-RAN WG1 Meeting #86 R1-166219 Gothenburg, Sweden, Aug. 22-26, 2016, 7 pages. |
| “Final Office Action”, U.S. Appl. No. 16/210,969, filed Jan. 7, 2021, 17 pages. |
| “International Preliminary Report on Patentability”, Application No. PCT/US2019/069129, Apr. 7, 2021, 14 pages. |
| “International Preliminary Report on Patentability”, PCT Application No. PCT/US2019/068265, Jan. 18, 2021, 31 pages. |
| “International Preliminary Report on Patentability”, Application No. PCT/US2019/068265, Jan. 18, 2021, 33 pages. |
| “International Preliminary Report on Patentability”, Application No. PCT/US2019/051980, Dec. 8, 2020, 7 pages. |
| “International Preliminary Report on Patentability”, Application No. PCT/US2019/063240, Feb. 18, 2021, 8 pages. |
| “International Search Report and Written Opinion”, Application No. PCT/US2019/051980, Jul. 27, 2020, 19 pages. |
| “International Search Report and Written Opinion”, PCT Application No. PCT/US2019/043355, Mar. 31, 2020, 12 pages. |
| “International Search Report and Written Opinion”, PCT Application No. PCT/US2020/014638, May 13, 2020, 12 pages. |
| “International Search Report and Written Opinion”, Application No. PCT/US2020/045777, Oct. 9, 2020, 13 pages. |
| “International Search Report and Written Opinion”, PCT Application No. PCT/US2019/069129, Mar. 31, 2020, 13 pages. |
| “International Search Report and Written Opinion”, PCT Application No. PCT/US2019/046374, Apr. 14, 2020, 13 pages. |
| “International Search Report and Written Opinion”, PCT Application No. PCT/US2020/022460, May 26, 2020, 13 pages. |
| “International Search Report and Written Opinion”, Application No. PCT/US2020/031716, Jul. 20, 2020, 14 pages. |
| “International Search Report and Written Opinion”, PCT Application No. PCT/US2019/063081, Feb. 21, 2020, 14 pages. |
| “International Search Report and Written Opinion”, PCT Application No. PCT/US2019/063620, Mar. 9, 2020, 14 pages. |
| “International Search Report and Written Opinion”, PCT Application No. PCT/US2019/052005, May 18, 2020, 14 pages. |
| “International Search Report and Written Opinion”, PCT Application No. PCT/US2020/017930, May 29, 2020, 14 pages. |
| “International Search Report and Written Opinion”, PCT Application No. PCT/US2019/063240, Feb. 13, 2020, 16 pages. |
| “International Search Report and Written Opinion”, PCT Application No. PCT/US2019/068265, Apr. 29, 2020, 29 pages. |
| “Invitation to Pay Additional Fees”, PCT Application No. PCT/US2019/051980, Jun. 4, 2020, 10 pages. |
| “Invitation to Pay Additional Fees”, PCT Application No. PCT/US2019/068265, Mar. 13, 2020, 13 pages. |
| “LTE; Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall Description; Stage 2 (3GPP TS 36.300 version 15.3.0 Release 15)”, ETSI TS 136 300 V15.3.0, Oct. 2018, 366 pages. |
| “LTE; Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification (3GPP TS 36.321 version 15.8.0 Release 15)”, ETSI TS 136 321 V15.8.0, Jan. 2020, 137 pages. |
| “Non-Final Office Action”, U.S. Appl. No. 16/210,969, filed Jul. 23, 2020, 15 Pages. |
| “Non-Final Office Action”, U.S. Appl. No. 16/206,579, filed Apr. 1, 2020, 23 Pages. |
| “Non-Final Office Action”, U.S. Appl. No. 16/419,854, filed Jun. 30, 2020, 29 Pages. |
| “Notice of Allowance”, U.S. Appl. No. 16/206,579, filed Jul. 8, 2020, 10 Pages. |
| “Notice of Allowance”, U.S. Appl. No. 16/419,854, filed Nov. 5, 2020, 11 pages. |
| “On the Need for More Flexible Configurations Related to CSI Reporting”, 3GPP TSG RAN WG1 Meeting #87, R1-1611237, Reno, USA, Nov. 14-18, 2016, 6 pages. |
| “Supplemental Notice of Allowance”, U.S. Appl. No. 16/206,579, filed Sep. 30, 2020, 3 pages. |
| “Third Generation Partnership Project; Technical Specification Group Services and System Aspects; Service requirements for the 5G system; Stage 1”, 3GPP TS 22.261 version 16.10.0 Release 16, Dec. 2019, 72 pages. |
| “U.S. Appl. No. 62/785,949”, filed Feb. 21, 2019. |
| “U.S. Appl. No. 62/785,949”, filed Dec. 28, 2018. |
| “UE Overheating for EN-DC”, 3GPP R2-1802414, UE overheating for EN-DC, in 3GPP TSG-RAN WG2 Meeting #101, Apple Inc., Mar. 2, 2018, 3 pages. |
| “Universal Mobile Telecommunications System (UMTS); Automatic Neighbour Relation (ANR) for UTRAN”, 3GPP TS 25.484 version 10.0.1 Release 10, Jan. 2012, 21 pages. |
| “Universal Mobile Telecommunications System (UMTS); Automatic Neighbour Relation (ANR) for UTRAN”, 3GPP TS 25.484 version 11.0.0 Release 11, Jan. 2012, 22 pages. |
| “Written Opinion”, Application No. PCT/US2019/063240, Oct. 27, 2020, 10 pages. |
| “Written Opinion”, Application No. PCT/US2019/068265, Sep. 25, 2020, 20 pages. |
| “Written Opinion”, Application No. PCT/US2020/014638, Nov. 26, 2020, 5 pages. |
| “Written Opinion”, PCT Application No. PCT/US2020/031716, Mar. 25, 2021, 6 pages. |
| “Written Opinion”, PCT Application No. PCT/US2019/069129, Dec. 14, 2020, 7 pages. |
| Aboba, B. et al., “Extensible Authentication Protocol (EAP)”, RFC Editor; Retrieved from https://www.rfc-editor.org/info/rfc3748, Jun. 2004, 67 pages. |
| Gorcin, Ali et al., “Hybrid Automatic Neighbor Relations for 5G Wireless Networks”, 2017, 6 pages. |
| Klingenbrunn, Thomas et al., “Power Backoff Mechanism for Intermodulation Distortion and Harmonic Distortion”, Technical Disclosure Commons; Retrieved from https://www.tdcommons.org/dpubs_series/3424, Jul. 13, 2020, 13 pages. |
| Lin, Roy et al., “Handling of Extensible Authentication Protocol Based Non-Access Stratum Authentication Failures”, Technical Disclosure Commons; Retrieved from https://www.tdcommons.org/dpubs_series/3191, Apr. 23, 2020, 11 pages. |
| Son, Harrison J. , “7 Deployment Scenarios of Private 5G Networks”, Netmanias; Retrieved from https://www.netmanias.com/en/post/blog/14500/5g-edge-kt-sk-telecom/7-deployment-scenarios-of-private-5g-networks, Oct. 21, 2019, 11 pages. |
| Wu, Chih-Hsiang , “Handling Overheating in a Wireless-Communication Device”, Technical Disclosure Commons; Retrieved from https://www.tdcommons.org/dpubs_series/2343, Jul. 12, 2019, 22 pages. |
| Zhang, Jinfang et al., “PoC of SCMA-Based Uplink Grant-Free Transmission in UCNC for 5G”, IEEE Journal on Selected Areas in Communications, vol. 35, No. 6, Jun. 2017, 10 pages. |
| Zhang, Jinyu et al., “Grant-less Uplink Transmission for LTE Operated in Unlicensed Spectrum”, Feb. 14, 2018, 6 pages. |
| “Foreign Office Action”, AU Application No. 20200216095, May 2, 2022, 7 pages. |
| “Foreign Office Action”, IN Application No. 202147026024, Jun. 3, 2022, 7 pages. |
| “Foreign Office Action”, IN Application No. 202247010266, Jul. 20, 2022, 7 pages. |
| “Foreign Office Action”, CN Application No. 201980083468.2, Sep. 21, 2023, 11 pages. |
| “Non-Final Office Action”, U.S. Appl. No. 17/295,815, filed Oct. 10, 2023, 10 pages. |
| “Notice of Allowance”, U.S. Appl. No. 17/275,632, filed Aug. 22, 2023, 7 pages. |
| “Report of e-mail discussion [95#30] Capability coordination for NR and LTE”, 3GPP TSG-RAN WG2 Meeting #95bis—R2-167065, Oct. 2016, 40 pages. |
| “Updates for M2AP baseline CR for MBMS congestion management”, 3GPP TSG RAN WG3 Meeting #87—R3-150291, Feb. 2015, 4 pages. |
| “Final Office Action”, U.S. Appl. No. 17/295,815, filed Jan. 3, 2024, 12 pages. |
| “Foreign Office Action”, AU Application No. 2023202260, Apr. 2, 2024, 6 pages. |
| “Non-Final Office Action”, U.S. Appl. No. 17/295,815, filed Apr. 1, 2024, 13 pages. |
| “Notice of Allowance”, U.S. Appl. No. 17/295,815, filed Jun. 28, 2024, 9 pages. |
| “Foreign Office Action”, EP Application No. 19845895.2, Oct. 18, 2024, 6 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20220007363 A1 | Jan 2022 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62797885 | Jan 2019 | US |
