US20220361089A1 - Systems and methods for supporting evolving band regulations - Google Patents
Systems and methods for supporting evolving band regulations Download PDFInfo
- Publication number
- US20220361089A1 US20220361089A1 US17/512,462 US202117512462A US2022361089A1 US 20220361089 A1 US20220361089 A1 US 20220361089A1 US 202117512462 A US202117512462 A US 202117512462A US 2022361089 A1 US2022361089 A1 US 2022361089A1
- Authority
- US
- United States
- Prior art keywords
- user equipment
- base station
- band
- indication
- ghz
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims description 53
- 230000033228 biological regulation Effects 0.000 title description 10
- 230000001105 regulatory effect Effects 0.000 claims abstract description 71
- 230000011664 signaling Effects 0.000 claims abstract description 65
- 230000007613 environmental effect Effects 0.000 claims abstract description 18
- 238000001228 spectrum Methods 0.000 claims abstract description 9
- 238000004891 communication Methods 0.000 claims description 33
- 238000012545 processing Methods 0.000 claims description 16
- 230000009467 reduction Effects 0.000 claims description 4
- 230000006399 behavior Effects 0.000 description 15
- 238000010586 diagram Methods 0.000 description 11
- 238000003860 storage Methods 0.000 description 9
- 230000001413 cellular effect Effects 0.000 description 8
- 230000005540 biological transmission Effects 0.000 description 7
- 230000002776 aggregation Effects 0.000 description 6
- 238000004220 aggregation Methods 0.000 description 6
- 230000006870 function Effects 0.000 description 4
- 238000004519 manufacturing process Methods 0.000 description 4
- 230000003247 decreasing effect Effects 0.000 description 3
- 230000001419 dependent effect Effects 0.000 description 3
- 238000013461 design Methods 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 229920001621 AMOLED Polymers 0.000 description 2
- 230000008901 benefit Effects 0.000 description 2
- 230000000903 blocking effect Effects 0.000 description 2
- 230000010267 cellular communication Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 230000007774 longterm Effects 0.000 description 2
- 101150012579 ADSL gene Proteins 0.000 description 1
- 102100020775 Adenylosuccinate lyase Human genes 0.000 description 1
- 108700040193 Adenylosuccinate lyases Proteins 0.000 description 1
- 101100127285 Drosophila melanogaster unc-104 gene Proteins 0.000 description 1
- WHXSMMKQMYFTQS-UHFFFAOYSA-N Lithium Chemical compound [Li] WHXSMMKQMYFTQS-UHFFFAOYSA-N 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 229910052744 lithium Inorganic materials 0.000 description 1
- 239000000463 material Substances 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 229920000642 polymer Polymers 0.000 description 1
- 238000003825 pressing Methods 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 238000009877 rendering Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
- H04W8/24—Transfer of terminal data
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/08—Reselecting an access point
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
- H04W52/02—Power saving arrangements
- H04W52/0209—Power saving arrangements in terminal devices
- H04W52/0212—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/04—Wireless resource allocation
- H04W72/044—Wireless resource allocation based on the type of the allocated resource
- H04W72/0453—Resources in frequency domain, e.g. a carrier in FDMA
-
- H04W72/048—
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/50—Allocation or scheduling criteria for wireless resources
- H04W72/51—Allocation or scheduling criteria for wireless resources based on terminal or device properties
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
- H04W16/14—Spectrum sharing arrangements between different networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
- H04W48/12—Access restriction or access information delivery, e.g. discovery data delivery using downlink control channel
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
- H04W52/04—TPC
- H04W52/30—TPC using constraints in the total amount of available transmission power
- H04W52/36—TPC using constraints in the total amount of available transmission power with a discrete range or set of values, e.g. step size, ramping or offsets
- H04W52/367—Power values between minimum and maximum limits, e.g. dynamic range
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/20—Control channels or signalling for resource management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
- H04W84/04—Large scale networks; Deep hierarchical networks
- H04W84/042—Public Land Mobile systems, e.g. cellular systems
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D30/00—Reducing energy consumption in communication networks
- Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks
Definitions
- the present disclosure relates generally to wireless communication, and more specifically to evolving and expanded regulations relating to radio frequency bands.
- user equipment In cellular communication, user equipment (e.g., a cell phone) may communicate (e.g., with a base station) under guidelines or rules that may be set and enforced by regulatory and/or standards bodies, such as the Federal Communications Commission (FCC), the Third Generation Partnership Project (3GPP), European Telecommunications Standards Institute (ETSI), and so on.
- FCC Federal Communications Commission
- 3GPP Third Generation Partnership Project
- ETSI European Telecommunications Standards Institute
- user equipment configured to operate in accordance with the guidelines or rules prior to the update may not be properly or efficiently operate under the updated guidelines or rules.
- a method for operating user equipment may include detecting a base station via the user equipment, synchronizing the user equipment to the base station, and receiving, at the user equipment, system information from the base station.
- the system information may include one or more network signaling flags, the network signaling flags indicating frequency ranges supported by the base station.
- the method may also include receiving, by the user equipment, one or more of the frequency ranges supported by the user equipment corresponding to the one or more network signaling flags.
- the method may further include sending an indication of the one or more frequency ranges supported by the user equipment from the user equipment to the base station.
- a system may include a base station supporting a non-federal network in a coverage area, user equipment in the coverage area communicatively coupled to the base station, environmental sensing capability sensors that determine whether additional non-federal networks are deployed in neighboring coverage areas with respect to the coverage area, and a Spectrum Access System communicatively coupled to the base station and the environmental sensing capability sensors.
- the Spectrum Access System may receive indications from the environmental sensing capability sensors as to whether the additional non-federal networks are deployed in the neighboring coverage areas.
- the Spectrum Access System may further, based on receiving the indications that indicate that the additional non-federal networks are deployed in the neighboring coverage areas, send an indication to the base station that the user equipment is permitted to operate using a default power mode.
- a method for operating user equipment may include receiving, at a receiver of the user equipment, a system information block from a base station.
- the system information block may include a network signaling value of multiple network signaling values corresponding to multiple regulatory requirements of multiple geographical regions.
- the method may also include receiving, using processing circuitry of the user equipment, a regulatory requirement of the multiple regulatory requirements of a geographical region of the multiple geographical regions corresponding to the network signaling value.
- the method may further include configuring, using processing circuitry of the user equipment, a transmitter or the receiver of the user equipment to comply with the regulatory requirement.
- a method for operating user equipment in a geographical region includes receiving, at a receiver of the user equipment, a system information block from a base station.
- the system information block includes a network signaling value of multiple network signaling values corresponding to multiple regulatory requirements of the geographical region.
- the method also includes receiving, using processing circuitry of the user equipment, the geographical region that the user equipment is located, and receiving, using the processing circuitry of the user equipment, a regulatory requirement of the multiple regulatory requirements corresponding to the network signaling value and based on the geographical region.
- the method further includes configuring, using processing circuitry of the user equipment, a transmitter or the receiver of the user equipment to comply with the regulatory requirement.
- FIG. 1 is a block diagram of an electronic device, according to embodiments of the present disclosure
- FIG. 2 is a functional block diagram of the electronic device of FIG. 1 , according to embodiments of the present disclosure
- FIG. 3 is a frequency chart illustrating a frequency band and subranges of the frequency band, according to embodiment of the present disclosure
- FIG. 4 is a diagram of a wireless communication network, according to embodiments of the present disclosure.
- FIG. 5 is a flowchart of a method for configuring the transceiver of the user equipment to communicate with the wireless communication network of FIG. 4 using one or more frequency subranges, according to embodiments of the present disclosure
- FIG. 6 is diagram of network coverage provided by a wireless communication network, according to embodiments of the present disclosure.
- FIG. 7 is a flowchart of a method for determining whether user equipment may operate without restriction on a restricted frequency band, according to embodiments of the present disclosure
- FIG. 8 is a frequency diagram of frequency-delineated regulatory requirements for different countries, according to embodiments of the present disclosure.
- FIG. 9 is a flowchart of a method for receiving or determining the frequency-delineated regulatory requirements of FIG. 8 for a country based on having greater than eight network signaling values, according to embodiments of the present disclosure.
- FIG. 10 is a flowchart of a method for determining the frequency-delineated regulatory requirements of FIG. 8 for a country based on region-dependent network signaling values, according to embodiments of the present disclosure.
- a target e.g., design, value, amount
- a margin of any suitable or contemplatable error e.g., within 0.1% of a target, within 1% of a target, within 5% of a target, within 10% of a target, within 25% of a target, and so on.
- user equipment In wireless (e.g., cellular) communication, user equipment (e.g., a cell phone, a smartphone, a tablet, a wearable device, a laptop, and so on) may communicate on a channel of a frequency band (e.g., the n77 or 3.7 gigahertz (GHz) frequency band) with a network (e.g., a wireless communication network) through one or more communication nodes (e.g., base stations).
- a frequency band e.g., the n77 or 3.7 gigahertz (GHz) frequency band
- a network e.g., a wireless communication network
- 3GPP Third Generation Partnership Project
- the network may allocate the channel to the user equipment, noting that the user equipment supports a frequency band (e.g., the n77 band) that includes the frequency of the channel.
- a frequency band e.g., the n77 band
- the base station may indicate (e.g., to the other base station or the network) that the user equipment supports the frequency band based on the user equipment indicating that it supports the frequency of the channel.
- the frequency band is updated (e.g., to include additional or remove a frequency subrange), and the user equipment is not updated in kind, then communication with the user equipment may become less efficient or fail altogether.
- U.S. United States
- GHz gigahertz
- user equipment may communicate using the n77 band if it complies with the Federal Communications Commission (FCC) rules governing the 3.7-3.98 GHz range.
- FCC Federal Communications Commission
- user equipment may be tested to confirm compliance with the FCC rules related to operate the 3.7-3.98 GHz range.
- the 3GPP updates the n77 band to allow an additional range of frequencies, such as the 3.5 GHz subrange (e.g., 3.45-3.55 GHz) in the U.S., at least at the time of that update, currently operating user equipment may not comply with the newly added 3.5 GHz band, as the user equipment may not have been tested, and thus not comply, with the 3.5 GHz subrange.
- the 3.5 GHz subrange e.g., 3.45-3.55 GHz
- the base station may indicate (e.g., to another base station or the network) that the user equipment supports the n77 band—and not the subrange of the n77 band that the user equipment complies with (e.g., 3.7-3.98 GHz)—to perform a handover event or request a secondary cell for carrier aggregation, the other base station may allocate a channel or the base station may allocate the secondary cell in the 3.5 GHz band for which the user equipment is not compliant. Accordingly, the handover event may fail, in which the user equipment may disconnect from the network, or the secondary cell may not be used by the user equipment, in which the user equipment may not be able to use the full bandwidth allocated to it for communication.
- the handover event may fail, in which the user equipment may disconnect from the network, or the secondary cell may not be used by the user equipment, in which the user equipment may not be able to use the full bandwidth allocated to it for communication.
- the presently disclosed embodiments enable the user equipment to indicate supported ranges of frequencies to the base station.
- the system information may include one or more network signaling values indicative of one or more frequency ranges supported by the base station.
- the one or more network signaling values may include the original 3.7-3.98 GHz frequency subrange of the n77 band, as well as the newly added 3.45-3.55 GHz frequency subrange of the n77 band.
- the user equipment may respond to the base station by indicating, using one or more modified maximum power reduction (MPR) behavior bits, which of the one or more frequency ranges are supported by the user equipment.
- MPR modified maximum power reduction
- the user equipment may indicate that it supports the 3.7-3.98 GHz frequency subrange, but not the 3.45-3.55 GHz frequency subrange. Accordingly, when performing a handover event or requesting a secondary cell for carrier aggregation, the other base station may allocate a channel or the base station may allocate the secondary cell in a frequency range supported by the user equipment. That is, in the above example, the other base station may allocate a channel or the base station may allocate the secondary cell in the 3.7-3.98 GHz frequency subrange.
- frequency bands may be updated (e.g., by the 3GPP) such that transmission and/or reception specification or requirements may change.
- the n77 band includes the 3.45-3.55 GHz frequency subrange (the “3.5 GHz subrange”), which initially was used by federal incumbent users and was protected by the FCC by blocking any non-federal communications from occurring on the frequency subrange.
- the FCC further protected the 3.5 GHz subrange blocking any non-federal communications from occurring on the neighboring subrange of 3.55-3.7 GHz frequency subrange, also known as the citizens Broadband Radio Service (CBRS) band, if the non-federal communications occurred in the same coverage area as those of the federal users.
- CBRS citizens Broadband Radio Service
- CBRS power backoff a power backoff of user equipment on the CBRS band (referred to herein as a “CBRS power backoff”) that is greater or “stricter” than a power backoff of the user equipment when not using the CBRS band. This was implemented by setting a network signaling value in a system information block sent from a base station to the user equipment per the 3GPP standard.
- the FCC recently allowed non-federal networks and users to use the 3.5 GHz subrange in coverage areas where federal users are not using the subrange. That is, the non-federal networks may be deployed using the 3.5 GHz subrange in coverage areas where there are no federal users utilizing the 3.5 GHz subrange. Accordingly, in the case where user equipment is using the CBRS band, and the user equipment is not located in or adjacent to a coverage area where there are federal users using the 3.5 GHz subrange, then the user equipment may not operate to its full communication potential or efficiency, as the FCC regulations may force it to operate with a greater power backoff (e.g., under the assumption that there are only federal users in the 3.5 GHz subrange).
- the presently disclosed embodiments enable a Spectrum Access System (SAS) controller that allocates spectrum resources in the CBRS band to determine, using Environmental Sensing Capability (ESC) sensors, whether there are non-federal networks in coverage areas.
- SAS Spectrum Access System
- ESC Environmental Sensing Capability
- the SAS controller may cause base stations in the coverage area to indicate (e.g., disable a network signaling value corresponding to the CBRS power backoff) to user equipment that it may operate using use the CBRS band with a default power backoff (e.g., less than the CBRS power backoff). In this manner, user equipment using the CBRS band may operate to its full communication potential or efficiency.
- a frequency band may have different regional regulatory specifications or requirements for the same or overlapping frequency subranges in the frequency band.
- Korea has a low power indoor (LPI) regulatory specification in the 6.425-7.125 GHz subrange
- Brazil has a LPI and very low port (VLP) regulatory specification in the overlapping 5.925-7.125 GHz subrange.
- Networks may indicate this regulatory specification to user equipment in system information sent by a base station (e.g., via network signaling values). Upon receiving this indication, the user equipment may configure its transceiver to operate using the regulatory specification.
- the 3GPP has only allocated eight network signaling values, and the number of permutations of geographical regions and their regulatory specifications may be much greater than eight. As such, the eight network signaling values may be insufficient to provide the proper regional regulatory specification to the user equipment.
- the eight network signaling values may correspond to regional regulatory specifications of the region that the user equipment and/or the base stations is located.
- the user equipment may determine its location (e.g., as determined using a location sensor of the user equipment) or the location of the base station (e.g., as received from the base station, and so on), and determine the regulatory specification based on the network signaling value and the location of the user equipment. In this manner, the user equipment may configure its transceiver to operate using the appropriate regulatory specification.
- FIG. 1 is a block diagram of an electronic device 10 .
- the electronic device 10 may include, among other things, one or more processors 12 (collectively referred to herein as a single processor for convenience, which may be implemented in any suitable form of processing circuitry), memory 14 , nonvolatile storage 16 , a display 18 , input structures 22 , an input/output (I/O) interface 24 , a network interface 26 , and a power source 29 .
- the various functional blocks shown in FIG. 1 may include hardware elements (including circuitry), software elements (including computer code stored on a computer-readable medium) or a combination of both hardware and software elements.
- the processor 12 , memory 14 , the nonvolatile storage 16 , the display 18 , the input structures 22 , the input/output (I/O) interface 24 , the network interface 26 , and/or the power source 29 may each be communicatively coupled directly or indirectly (e.g., through or via another component, a communication bus, a network) to one another to transmit and/or receive data between one another.
- FIG. 1 is merely one example of a particular implementation and is intended to illustrate the types of components that may be present in electronic device 10 .
- the electronic device 10 may represent a block diagram of any suitable computing device, including a desktop or notebook computer (e.g., in the form of a MacBook®, MacBook® Pro, MacBook Air®, iMac®, Mac® mini, or Mac Pro® available from Apple Inc. of Cupertino, Calif.), a portable electronic or handheld electronic device such as a wireless electronic device or smartphone (e.g., in the form of a model of an iPhone® available from Apple Inc. of Cupertino, Calif.), a tablet (e.g., in the form of a model of an iPad® available from Apple Inc. of Cupertino, Calif.), a wearable electronic device (e.g., in the form of an Apple Watch® by Apple Inc.
- a desktop or notebook computer e.g., in the form of a MacBook®, MacBook® Pro, MacBook Air®, iMac®, Mac® mini, or Mac Pro® available from Apple Inc. of Cupertino, Calif.
- a portable electronic or handheld electronic device such as a
- processor 12 and other related items in FIG. 1 may be generally referred to herein as “data processing circuitry.” Such data processing circuitry may be embodied wholly or in part as software, software, hardware, or any combination thereof. Furthermore, the processor 12 and other related items in FIG. 1 may be a single contained processing module or may be incorporated wholly or partially within any of the other elements within the electronic device 10 .
- the processor 12 may be implemented with any combination of general-purpose microprocessors, microcontrollers, digital signal processors (DSPs), field programmable gate array (FPGAs), programmable logic devices (PLDs), controllers, state machines, gated logic, discrete hardware components, dedicated hardware finite state machines, or any other suitable entities that may perform calculations or other manipulations of information.
- DSPs digital signal processors
- FPGAs field programmable gate array
- PLDs programmable logic devices
- controllers state machines, gated logic, discrete hardware components, dedicated hardware finite state machines, or any other suitable entities that may perform calculations or other manipulations of information.
- the processors 12 may perform the various functions described herein and below.
- the processor 12 may be operably coupled with a memory 14 and a nonvolatile storage 16 to perform various algorithms.
- Such programs or instructions executed by the processor 12 may be stored in any suitable article of manufacture that includes one or more tangible, computer-readable media.
- the tangible, computer-readable media may include the memory 14 and/or the nonvolatile storage 16 , individually or collectively, to store the instructions or routines.
- the memory 14 and the nonvolatile storage 16 may include any suitable articles of manufacture for storing data and executable instructions, such as random-access memory, read-only memory, rewritable flash memory, hard drives, and optical discs.
- programs e.g., an operating system
- encoded on such a computer program product may also include instructions that may be executed by the processor 12 to enable the electronic device 10 to provide various functionalities.
- the display 18 may facilitate users to view images generated on the electronic device 10 .
- the display 18 may include a touch screen, which may facilitate user interaction with a user interface of the electronic device 10 .
- the display 18 may include one or more liquid crystal displays (LCDs), light-emitting diode (LED) displays, organic light-emitting diode (OLED) displays, active-matrix organic light-emitting diode (AMOLED) displays, or some combination of these and/or other display technologies.
- LCDs liquid crystal displays
- LED light-emitting diode
- OLED organic light-emitting diode
- AMOLED active-matrix organic light-emitting diode
- the input structures 22 of the electronic device 10 may enable a user to interact with the electronic device 10 (e.g., pressing a button to increase or decrease a volume level).
- the I/O interface 24 may enable electronic device 10 to interface with various other electronic devices, as may the network interface 26 .
- the I/O interface 24 may include an I/O port for a hardwired connection for charging and/or content manipulation using a standard connector and protocol, such as the Lightning connector provided by Apple Inc. of Cupertino, Calif., a universal serial bus (USB), or other similar connector and protocol.
- the network interface 26 may include, for example, one or more interfaces for a personal area network (PAN), such as a BLUETOOTH® network, for a local area network (LAN) or wireless local area network (WLAN), such as a network employing one of the IEEE 802.11x family of protocols (e.g., WI-FI®), and/or for a wide area network (WAN), such as any standards related to the Third Generation Partnership Project (3GPP), including, for example, a 3 rd generation (3G) cellular network, universal mobile telecommunication system (UMTS), 4 th generation (4G) cellular network, long term evolution (LTE®) cellular network, long term evolution license assisted access (LTE-LAA) cellular network, 5th generation (5G) cellular network, and/or New Radio (NR) cellular network, a satellite network, and so on.
- PAN personal area network
- LAN local area network
- WLAN wireless local area network
- WAN wide area network
- 3GPP Third Generation Partnership Project
- 3GPP Third
- the network interface 26 may include, for example, one or more interfaces for using a Release-15 cellular communication standard of the 5G specifications that include the millimeter wave (mmWave) frequency range (e.g., 24.25-300 gigahertz (GHz)).
- the network interface 26 of the electronic device 10 may allow communication over the aforementioned networks (e.g., 5G, Wi-Fi, LTE-LAA, and so forth).
- the network interface 26 may also include one or more interfaces for, for example, broadband fixed wireless access networks (e.g., WIMAX®), mobile broadband Wireless networks (mobile WIMAX®), asynchronous digital subscriber lines (e.g., ADSL, VDSL), digital video broadcasting-terrestrial (DVB-T®) network and its extension DVB Handheld (DVB-H®) network, ultra-wideband (UWB) network, alternating current (AC) power lines, and so forth.
- broadband fixed wireless access networks e.g., WIMAX®
- mobile broadband Wireless networks e.g., mobile broadband Wireless networks (mobile WIMAX®)
- asynchronous digital subscriber lines e.g., ADSL, VDSL
- DVD-T® digital video broadcasting-terrestrial
- DVD-H® extension DVB Handheld
- UWB ultra-wideband
- AC alternating current
- the network interface 26 may include a transceiver 30 .
- the transceiver 30 may be disposed within the processor 12 .
- the transceiver 30 may support transmission and receipt of various wireless signals via one or more antennas.
- the power source 29 of the electronic device 10 may include any suitable source of power, such as a rechargeable lithium polymer (Li-poly) battery and/or an alternating current (AC) power converter.
- the electronic device 10 may take the form of a computer, a portable electronic device, a wearable electronic device, or other type of electronic device.
- FIG. 2 is a functional block diagram of the electronic device 10 that may implement the components shown in FIG. 1 and/or the circuitry and/or components described in the following figures.
- the processor 12 , the memory 14 , the transceiver 30 , the transmitter 40 , the receiver 44 , and/or the antennas 45 may be communicatively coupled directly or indirectly (e.g., through or via another component, a communication bus, a network) to one another to transmit and/or receive data between one another.
- the electronic device 10 may include the transmitter 40 and/or the receiver 44 that respectively enable transmission and reception of data between the electronic device 10 and a remote location via, for example, a network or direction connection associated with the electronic device 10 and an external transceiver (e.g., in the form of a cell, eNB (E-UTRAN Node B or Evolved Node B), base stations, and the like. As illustrated, the transmitter 40 and the receiver 44 may be combined into the transceiver 30 .
- the electronic device 10 may also have one or more antennas 45 a through 45 n electrically coupled to the transceiver 30 .
- the antennas 45 a - 45 n may be configured in an omnidirectional or directional configuration, in a single-beam, dual-beam, or multi-beam arrangement, and so on. Each antenna 45 may be associated with a one or more beams and various configurations. In some embodiments, each beam, when implement as multi-beam antennas, may correspond to a respective transceiver 30 .
- the electronic device 10 may include multiple transmitters, multiple receivers, multiple transceivers, and/or multiple antennas as suitable for various communication standards.
- the transmitter 40 may wirelessly transmit packets having different packet types or functions. For example, the transmitter 40 may transmit packets of different types generated by the processor 12 .
- the receiver 44 may wirelessly receive packets having different packet types. In some examples, the receiver 44 may detect a type of a packet used and process the packet accordingly. In some embodiments, the transmitter 40 and the receiver 44 may transmit and receive information via other wired or wireline systems or devices.
- the various components of the electronic device 10 may be coupled together by a bus system 46 .
- the bus system 46 may include a data bus, for example, as well as a power bus, a control signal bus, and a status signal bus, in addition to the data bus.
- the components of the electronic device 10 may be coupled together or accept or provide inputs to each other using some other mechanism.
- FIG. 3 is a frequency chart of a frequency band 50 (e.g., the n77 band) and subranges of the frequency band, according to embodiments of the present disclosure.
- the n77 band includes a subrange 52 between 3.55 GHz and 3.65 GHz (also referred to as the Citizens Broadband Radio Service (CBRS) band), a subrange 54 between 3.45 GHz and 3.55 GHz (also referred to as the 3.5 GHz subrange), and a subrange 56 between 3.7 GHz and 3.98 GHz (also referred to as the C-band), among others.
- CBRS citizens Broadband Radio Service
- the FCC recently released new rules for the 3.5 GHz subrange 54 within the n77 band to allow for utilization of the subrange 54 in network communication, while current radio frequency requirements from the 3GPP restrict usage of the subrange 54 and limit the U.S. to the C-band 56 .
- these user equipment may not been tested for compliance with the new FCC rules for the 3.5 GHz subrange 54 , and thus are not permitted to use the 3.5 GHz subrange 54 .
- a network enabling communication on the n77 band may only assume that user equipment is operable on an entire frequency band (e.g., the n77 band) and not respective subranges of the frequency band (e.g., the C-band 56 vs.
- the network not be able to distinguish between these two types of user equipment and would only realize that the user equipment does not support 3.5 GHz subrange 54 when performing a handover event (e.g., transferring network coverage of the user equipment from one base station to another base station) or requesting a secondary cell for carrier aggregation fails.
- a handover event e.g., transferring network coverage of the user equipment from one base station to another base station
- requesting a secondary cell for carrier aggregation fails.
- FIG. 4 is a diagram of a network 60 (e.g., a wireless communication network), according to embodiments of the present disclosure.
- the network 60 may provide network coverage to user equipment 62 over a channel in a supported frequency range or band (e.g., the n77 band) via one or more base stations 64 A, 64 B (collectively 64 ) within a coverage area 66 .
- the frequency band may include one or more frequency subranges (e.g. the CBRS band 52 , the 3.5 GHz subrange 54 , the C-band 56 , and so on).
- the base station 64 may broadcast a message on one or more supported frequency ranges or channels (e.g. in the n77 band) that are available to establish the connection to the user equipment 62 in the coverage area or cell 66 . If the user equipment 62 also supports the one or more supported frequency ranges or channels (e.g., in the C-band 56 of the n77 band), then the user equipment 62 may respond, and the base station 64 may establish the connection to the user equipment 62 using a channel of the one or more supported frequency ranges or channels. As illustrated, the base station 64 may establish the connection to the user equipment 62 using a channel in the C-band 56 .
- the base station 64 may establish the connection to the user equipment 62 using a channel in the C-band 56 .
- the base station 64 may perform a handover event or request a secondary cell for carrier aggregation based on the entire frequency band, instead of the subrange supported by the user equipment 62 .
- the user equipment 62 only supports the subrange (e.g., the C-band 56 ) of the frequency band (e.g., the n77 band) and not another subrange (e.g., the 3.5 GHz subrange 54 ) of the frequency band, then, if the handover event is performed or the secondary cell is implemented using the other subrange that is not supported by the user equipment 62 , the handover event or the implementation of the secondary cell may fail. In such cases, the user equipment 62 may disconnect from the network 60 , or the secondary cell may not be used by the user equipment 62 , in which the user equipment 62 may not be able to use the full bandwidth allocated to it for communication.
- the subrange e.g., the C-band 56
- the secondary cell may not be used by the user equipment 62 , in which the user equipment 62 may not be able to use the full bandwidth allocated to it for communication.
- the presently disclosed embodiments include enabling the base station 64 to send a system information block to the user equipment 62 having one or more network signaling (NS) flags/values to communicate the frequency subranges supported by the base station 64 .
- the system information block is sent to all user equipment 62 in the coverage area 66
- the NS flags (which include eight integer value per frequency band) may indicate to the user equipment 62 the regional regulatory requirements apply the user equipment 62 in the coverage area 66 .
- the user equipment 62 specification may define additional requirements which become applicable based on the NS flags.
- the user equipment 62 may establish communication with the base station 64 if the user equipment 62 supports the frequency band and the applicable NS flags.
- the NS flags may be used to indicate to the user equipment 62 the available frequency subranges (e.g., the C-band 56 , the 3.5 GHz band 54 , and so on) supported by the base station 64 .
- the base station 64 A may support both the C-band 56 and the 3.5 GHz band 54 . Accordingly, the base station 64 A may send a system information block with NS flags indicating that it supports the C-band 56 and the 3.5 GHz band 54 to the user equipment 62 in its coverage area 66 .
- the presently disclosed embodiments also include enabling the user equipment 62 to indicate to the base station 64 the frequency subranges indicated by the NS flags of the receive system information block that are in turn supported by the user equipment 62 .
- the user equipment 62 may utilize one or more modified maximum power reduction (MPR) behavior bits to indicate the frequency subranges supported by the user equipment 62 .
- MPR modified maximum power reduction
- the 3GPP specification provides that the MPR bits may specify an allowed decrease in maximum power transmitted by the user equipment 62 to enable the user equipment 62 to fulfill regional regulatory requirements (e.g., transmitter adjacent channel leakage ratio requirements).
- the modified MPR behavior bits may distinguish applicability of different A-MPR (Additional MPR) requirements for different types of user equipment 62 in particular frequency bands (e.g., n257 n260, and n261).
- the user equipment 62 may set the modified MPR behavior bits corresponding to a frequency subrange (e.g., the C-band 56 , the 3.5 GHz band 54 , and so on) that the user equipment 62 supports to indicate to the base station 64 that the user equipment 62 supports the frequency subrange.
- a frequency subrange e.g., the C-band 56 , the 3.5 GHz band 54 , and so on
- the base station 64 may be aware of and/or store the frequency subrange(s) supported by the user equipment 62 , and perform a handover event or allocate a secondary cell based on the supported frequency subrange, instead of the entire frequency band (e.g., the n77 band), which may not be supported by the user equipment 62 in whole, thus preventing disconnection from the network 60 or a drop in bandwidth usage.
- the entire frequency band e.g., the n77 band
- the user equipment 62 may receive the system information block from the base station 64 A indicating that the base station 64 A supports both the C-band 56 and the 3.5 GHz band 54 . However, the user equipment 62 may only support the C-band 56 . As such, the user equipment 62 may set modified MPR behavior bits corresponding to the C-band 56 , but not the 3.5 GHz band 54 , and send the modified MPR behavior bits (e.g., in a message) to the base station 64 A. Upon receipt of the modified MPR behavior bits, the base station 64 A may establish a primary cell 68 with the user equipment 62 on the supported C-band 56 .
- the base station 64 A may not establish a secondary cell 70 using the 3.5 GHz band 54 , as the user equipment 62 has indicated that it does not support the 3.5 GHz band 54 . Instead, the base station 64 A may establish a secondary cell 72 using the C-band 56 . Similarly, if the user equipment 62 moves to another coverage area 74 , the base station 64 A may perform a handover event 76 with a base station 64 B that provides support to the other coverage area 74 . In particular, the base station 64 A may send an indication to the base station 64 B of the frequency subrange(s) supported by the user equipment 62 (e.g., the C-band 56 ).
- the base station 64 B may not establish connection 78 with the user equipment 62 using the 3.5 GHz band 54 , as the user equipment 62 has indicated that it does not support the 3.5 GHz band 54 . Instead, the base station 64 B may establish connection 80 with the user equipment 62 using the C-band 56 . Without this indication of user equipment-supported frequency subranges, the network 60 and base stations 64 may have attempted to establish the secondary cell 70 or performed the handover event 76 by establishing the connection 78 with the user equipment 62 using the unsupported 3.5 GHz band 54 , resulting in decreased bandwidth usage or disconnection from the network 60 .
- FIG. 5 is a flowchart of a method 90 for configuring the transceiver 30 of the user equipment 62 to communicate with the wireless communication network 60 (e.g. including the base station 64 A and/or the base station 64 B) using one or more frequency subranges, according to embodiments of the present disclosure.
- Any suitable device e.g., a controller
- the method 90 may be implemented by executing instructions stored in a tangible, non-transitory, computer-readable medium, such as the memory 14 or storage 16 , using the processor 12 .
- the method 90 may be performed at least in part by one or more software components, such as an operating systems, one or more software applications, and the like, of the user equipment 62 , the base station 64 A and/or the base station 64 B, and the terrestrial network. While the method 90 is described using steps in a specific sequence, it should be understood that the present disclosure contemplates that the described steps may be performed in different sequences than the sequence illustrated, and certain described steps may be skipped or not performed altogether.
- software components such as an operating systems, one or more software applications, and the like
- the user equipment 62 detects the base station 64 .
- the user equipment 62 may detect the base station by receiving a radio frequency (RF) signal when the user equipment 62 enters the coverage area 66 of the base station 64 .
- the RF signal may include timing alignment information, among other information.
- the user equipment 62 synchronizes to the base station 64 by aligning its timing with the timing alignment information of the base station 64 .
- the base station 64 broadcasts system information indicative of frequency subranges supported by the base station 64 .
- the base station 64 may indicate the frequency subranges in the NS flags that are used to indicate the capabilities of the base station 64 .
- the base station 64 may indicate the C-band 56 and the 3.5 GHz band 54 in one or more NS flags of the broadcasted system information.
- the user equipment 62 reads the system information, including the NS flags, received from the base station 64 .
- the system information may additionally include timing specification, power specifications, Global Positioning System (GPS) coordinates, and/or any other applicable information.
- GPS Global Positioning System
- the user equipment 62 may store the system information in the memory 14 for future usage.
- the user equipment 62 determines or receives the frequency subranges supported by the base station 64 from the system information block.
- the one or more NS flags may include the C-band 56 and the 3.5 GHz band 54 of the n77 band.
- the user equipment 62 indicates the frequency subranges supported by the base station 64 that are also supported by the user equipment 62 .
- the user equipment 62 may set one or more indicator bits corresponding to one or more frequency subranges that are supported by the user equipment 62 .
- the indicator bits may include modified MPR behavior bits.
- the NS flags for the n77 band may include a new NS flag (“NS_X”) corresponding to the 3.5 GHz subrange 54 .
- NS_X a new NS flag
- the value for the A-MPR may be set to 0 decibels (thus rendering the NS flag irrelevant for purposes of MPR operation).
- a modified MPR behavior bit corresponding to the new NS flag may be defined, such that setting the modified MPR behavior bit indicates that the user equipment 62 supports the 3.5 GHz subrange 54 . If the user equipment 62 does not set the modified MPR behavior bit, then the user equipment 62 is indicating that it does not support the 3.5 GHz subrange 54 .
- the modified MPR behavior bit may correspond directly to 3.5 GHz subrange 54 .
- the 3GPP may define the modified MPR behavior bit to correspond directly to the n77 band, such that if the user equipment 62 sets the modified MPR behavior bit, then it implies that the user equipment 62 supports the 3.5 GHz subrange 54 . If the user equipment 62 does not set the modified MPR behavior bit, then it implies that the user equipment 62 does not support the 3.5 GHz subrange 54 (e.g. the user equipment 62 only supports the 3.7-3.98 GHz subrange). In such embodiments, the user equipment 62 may not receive a corresponding NS flag and/or setting the A-MPR to 0 decibels to indicate support for the 3.5 GHz subrange 54 may be avoided. While this embodiment refers to the 3.5 GHz subrange 54 , it should be understood that any suitable frequency subrange of a frequency band, and particularly newly introduced subranges to existing frequency bands, are contemplated.
- the base station 64 configures its resources to the user equipment 62 within the frequency subranges supported by the user equipment 62 and the base station 64 . Once the resources are configured and a connection is established between the user equipment 62 and the base station 64 , the user equipment 62 and the base station 64 may send and receive user data 106 over the frequency subrange. In this manner, the method 90 may enable the user equipment to configure the transceiver 30 to conform to one or more applicable subrange of frequencies and communicate with a terrestrial network (e.g., including the base station 64 and/or the base station 64 B).
- a terrestrial network e.g., including the base station 64 and/or the base station 64 B.
- the 3.5 GHz band 54 was utilized by federal incumbent users.
- the 3.5 GHz band 54 is situated adjacent to the CBRS band 52 (3.55-3.7 GHz).
- stricter requirements were introduced for the CBRS band 52 by the FCC.
- the FCC currently enforces a power backoff of the user equipment 62 using the CBRS band 52 (the “CBRS power backoff”) that is greater or “stricter” than a power backoff of the user equipment 62 when not using the CBRS band 52 (a “default power backoff”).
- the 3GPP has defined the power backoff as a maximum power by which the user equipment 62 is to back off (e.g., when approaching a power threshold, to meet out-of-band emission levels, and so on), while an actual power backoff value may be smaller and/or may depend on an implementation of the user equipment 62 .
- the CBRS power backoff may be referred to as a lower power mode, while the default power backoff may be referred to as a default power mode.
- the lower power mode refers to a greater power backoff than the default power backoff
- the lower power mode in other applications, may refer to any suitable power characteristics that cause the user equipment 62 to operate at less power than the default power mode, include decreased transmission power, decreased reception power, less maximum transmission power, less maximum reception power, and so on.
- Table 1 below provided by 3GPP Technical Specification (TS) 38.101-1, illustrates different CBRS power backoff values (e.g., depending on, there are different cases A1-A8) that may be applied by the user equipment 62 .
- the numbers below are described in decibels (dB) as an amount of power that the user equipment 62 may backoff to meet regulatory requirements.
- Table 1 is specific to the CBRS band requirements.
- Table 2 below illustrates different default power backoff values that may be applied by the user equipment 62 .
- the default power backoff values in Table 2 are applicable when there are no conditions that exist to operate under the CBRS band requirements, and have lower power backoff values that that of the CBRS power backoff values. That is, the user equipment 62 may still be allowed to backoff its power, but not to the same degree as the CBRS power backoff values, and, in some cases, not at all. Accordingly, the lower default power backoff values enable the user equipment 62 to operate at higher transmission and/or reception power, and thus with better performance, then when operating using the higher CBRS power backoff values.
- Edge RB Outer RB Inner RB Modulation allocations allocations DFT-s- Pi/2 BPSK ⁇ 3.5 ⁇ 1.2 ⁇ 0.2 OFDM ⁇ 0.5 ⁇ 0.5 0 Pi/2 BPSK w ⁇ 0.5 ⁇ 0 0 Pi/2 BPSK DMRS QPSK ⁇ 1 0 16QAM ⁇ 2 ⁇ 1 64QAM ⁇ 2.5 256QAM ⁇ 4.5 CP-OFDM QPSK ⁇ 3 ⁇ 1.5 16QAM ⁇ 3 ⁇ 2 64QAM ⁇ 3.5 256QAM ⁇ 6.5
- the FCC recently allowed non-federal networks and users to use the 3.5 GHz subrange 54 in coverage areas where federal users are not using the subrange. That is, the non-federal networks may be deployed using the 3.5 GHz subrange 54 in coverage areas where there are no federal users utilizing the 3.5 GHz subrange 54 .
- the user equipment 62 may not operate to its full communication potential or efficiency, as the FCC regulations may force it to operate with a greater power backoff (e.g., under the assumption that there are only federal users in the 3.5 GHz subrange 54 ).
- FIG. 6 is a diagram of network coverage provided by a wireless communication network 110 , according to embodiments of the present disclosure.
- Coverage Area A 112 may include federal users 114 using the 3.5 GHz band 54 .
- non-federal networks 116 e.g., a cellular network as provided by a network operator to users other than federal users 114 via one or more base stations
- the federal users 114 may be those defined as “federal incumbent users” by the FCC and/or 47 C.F.R. ⁇ 96.15.
- Coverage Area B 118 and Coverage Areas C 120 may include non-federal users connecting to a non-federal network 116 operating on the 3.5 GHz band and/or the CBRS band 52 .
- user equipment 62 may operate under the lower or CBRS power mode (e.g., employing the CBRS power backoff) due to both coverage areas neighboring Coverage Area A 112 .
- Coverage Area D 122 may also include non-federal users connecting to a non-federal network 116 operating on the 3.5 GHz band and/or the CBRS band 52 .
- Coverage Area D 122 borders only two coverage areas (e.g., Coverage Area B 118 and Coverage Area C 120 ), and each neighboring coverage area has a non-federal network 116 operating in the 3.5 GHz band 54 or the CBRS band 52 , there is no need for the user equipment 62 to operate on the CBRS band 52 under the lower or CBRS power mode (e.g., employing the CBRS power backoff) since it may be safely assumed that Coverage Area D 122 does not border a coverage area with federal users 114 .
- CBRS power mode e.g., employing the CBRS power backoff
- a Spectrum Access System (SAS) controller 124 may utilize one or more environmental sensing capability sensors (ESC) 126 to identify the presence and coverage area of non-federal networks (e.g., non-federal network deployments) 116 operating in the 3.5 GHz band 54 or the CBRS band 52 to determine the presence and coverage areas of federal users 114 operating on the 3.5 GHz band 54 .
- SAS Spectrum Access System
- ESC environmental sensing capability sensors
- the SAS controller 124 may include an automated frequency coordinator that manages radio frequency wave sharing on a dynamic, as-needed basis across multiple tiers of access (e.g., federal incumbent users, priority access license users, and general authorized access users).
- the environmental sensing capability sensors 126 may include a network of sensors utilized to detect non-federal or federal frequency use in particular frequency subranges (e.g. 3.5 GHz to 3.65 GHz).
- the SAS controller 124 may assume that there are federal users 114 in the coverage area. Accordingly, the SAS controller 124 may prevent or block non-federal networks 116 and user equipment 62 attempting to use the non-federal networks 116 from operating on the 3.5 GHz band 54 and the CBRS band 52 in the coverage area.
- the SAS controller 124 may determine that there are no federal users 114 within that coverage area. Moreover, if the environmental sensing capability sensors 126 detect that there are no non-federal networks 116 using the 3.5 GHz band 54 or the CBRS band 52 within a neighboring coverage area (e.g., Coverage Area A 114 ) of the coverage area, the SAS controller 124 may assume that there are federal users 114 in the neighboring coverage area.
- the SAS controller 124 may communicate to the non-federal network 116 within the coverage area to indicate to user equipment 62 that operating on the CBRS band 52 is permissible if using the CBRS power backoff.
- the 3.5 GHz band 54 currently has no such restriction imposed on it by standards and/or regulation bodies.
- a coverage area e.g., Coverage Area D 122
- the SAS controller 124 may communicate to the non-federal network 116 within the coverage area to indicate to user equipment 62 that operating on the CBRS band 52 using the default power mode is permissible (e.g., the user equipment 62 may use the default power backoff, and need not operate under the CBRS power mode and use the CBRS power backoff).
- default power mode may refer to applying the default power backoff as specified by regulatory or standards bodies when operating outside of the CBRS band 52 , such as that shown above in Table 2.
- the 3.5 GHz band 54 currently has no such restriction imposed on it by standards and/or regulation bodies. In this manner, the user equipment 62 using the CBRS band 52 may operate to its full communication potential or efficiency.
- FIG. 7 is a flowchart of a method 140 for determining whether the user equipment 62 may operate without restriction (e.g., operate under the default power mode with the default power backoff) on a restricted frequency band (e.g., the CBRS band 52 ), according to embodiments of the present disclosure.
- Any suitable device e.g., a controller
- Any suitable device may control components of the user equipment 62 , the base station 64 , the non-federal networks 116 , the SAS controller 124 , and/or the environmental sensing capability sensors 126 , such as the processor 12 of each of these devices or systems, may perform the method 140 .
- the method 140 may be implemented by executing instructions stored in a tangible, non-transitory, computer-readable medium, such as the memory 14 or storage 16 , using the processor 12 .
- the method 140 may be performed at least in part by one or more software components, such as an operating systems, one or more software applications, and the like, of the user equipment 62 , the base station 64 , the non-federal networks 116 , the SAS controller 124 , and/or the environmental sensing capability sensors 126 . While the method 140 is described using steps in a specific sequence, it should be understood that the present disclosure contemplates that the described steps may be performed in different sequences than the sequence illustrated, and certain described steps may be skipped or not performed altogether.
- the SAS controller 124 determines whether there are non-federal networks 116 using the 3.5 GHz band 54 or the CBRS band 52 in a coverage area of the base station 64 and in each neighboring coverage areas adjacent to the coverage area.
- the SAS controller 124 may utilize the environmental sensing capability sensors 126 to detect if there are non-federal networks 116 using the 3.5 GHz band 54 or the CBRS band 52 in the coverage area and the neighboring coverage areas. If the environmental sensing capability sensors 126 detect non-federal networks 116 using the 3.5 GHz band 54 or the CBRS band 52 in a coverage area, the SAS controller 124 may determine that there are no federal users 114 in the coverage area.
- the SAS controller 124 may determine that there are federal users 114 in the coverage area. As described above, there may not be any non-federal networks 116 on either the 3.5 GHz band 54 or the CBRS band 52 when federal users 114 are present within a coverage area.
- the SAS controller 124 determines there are non-federal networks 116 using the 3.5 GHz band 54 or the CBRS band 52 in the coverage area of the base station 64 and in the neighboring coverage areas adjacent to the coverage area, then, at block 144 , the SAS controller 124 sends an indication to the base station 64 that user equipment 62 connected to the base station 64 may use the default power mode.
- the SAS controller 124 may send an indication to the non-federal network 116 in Coverage Area D that the user equipment 62 connected to the non-federal network 116 may use the default power mode.
- the base station 64 determines if the indication that the user equipment 62 may use the default power mode has been received. For example, the SAS controller 124 may determine that there are no non-federal networks 116 using the 3.5 GHz band 54 or the CBRS band 52 in Coverage Area A 112 of FIG. 6 .
- the base station 64 sends an indication to the user equipment 62 to transmit using the lower or CBRS power mode when using the CBRS band 52 .
- the base station may set a network signaling value (e.g., network signaling value 27 or NS27 per the 3GPP standard) corresponding to operating using the lower or CBRS power mode that is sent to the user equipment 62 in a system information block.
- the user equipment 62 transmits data using the CBRS power mode on the CBRS band 52 . That is, the user equipment 62 may configure its transmitter 40 to use the CBRS power backoff when transmitting data on the CBRS band 52 .
- the base station 64 sends an indication to the user equipment 62 to transmit with the default power mode on the CBRS band 52 .
- the indication may include a lack of setting a network signaling value (e.g., the NS27 value) corresponding to operating using the CBRS power mode in a system information block sent to the user equipment 62 .
- the lack of setting the network signal value removal of the restrictions flag may lead to improved network performance through the allowance of less power backoff as offered by the default power mode when operating on the CBRS band 52 .
- the user equipment 62 transmits data using the default power mode on the CBRS band 52 . That is, the user equipment 62 may configure its transmitter 40 to use the default power mode when transmitting data on the CBRS band 52 .
- a new 6 GHz band has recently been allocated by different countries for network operation. Almost all countries have allocated the new 6 GHZ band (or parts thereof), for unlicensed network operation. As a result, most countries have slightly different regulatory requirements for the new 6 GHz band which may need to be addressed when initializing network communication.
- FIG. 8 is a frequency diagram of frequency-delineated regulatory requirements for different countries, according to embodiments of the present disclosure.
- different countries may have different regulatory requirements for different subranges of a frequency band 160 (e.g., the 6 GHz frequency band).
- these subranges corresponding to different regulatory requirements in different countries may overlap.
- Korea Korean
- LPI Low-Power Indoor
- VLP Very Low Power
- Brazil has a regulatory requirement 166 for the entire frequency range between 5.925 GHz and 7.125 GHz to operate on the LPI mode or the VLP mode.
- a regulatory requirement in one country may be different than the same regulatory requirement in another country. That is, the LPI mode in Korea may limit maximum transmission power to a power value that is different than that of the LPI mode in Brazil.
- a base station 64 may send the user equipment 62 a network signaling value corresponding to the appropriate regulatory requirement.
- the user equipment 62 may then receive or determine the regulatory requirement based on the network signal value, and operate under the regulatory requirement.
- networks signaling values are specific to each frequency band (e.g., 160 )
- each frequency band 160 is typically allotted only eight network signaling values. Because each country has different regulatory requirements, and even the same regulatory requirements are different in different countries, eight network signaling values may not be sufficient to cover all the different possible regulatory requirements.
- FIG. 9 is a flowchart of a method 170 for receiving or determining the frequency-delineated regulatory requirements of FIG. 8 for a country based on having greater than eight network signaling values, according to embodiments of the present disclosure.
- Any suitable device e.g., a controller
- the method 170 may be implemented by executing instructions stored in a tangible, non-transitory, computer-readable medium, such as the memory 14 or storage 16 , using the processor 12 .
- the method 170 may be performed at least in part by one or more software components, such as an operating systems, one or more software applications, and the like, of the user equipment 62 . While the method 170 is described using steps in a specific sequence, it should be understood that the present disclosure contemplates that the described steps may be performed in different sequences than the sequence illustrated, and certain described steps may be skipped or not performed altogether.
- the network signaling values are increased greater than eight values.
- the number of network signaling values may be at least the number of different regulatory requirements for the different countries.
- the user equipment 62 receives or determines a network signaling value of multiple network signaling values each corresponding to a regulatory requirement of a geographical region. As described above, there may be at least more than eight network signaling values for the frequency band on which the user equipment 62 may be operating (e.g., the 6 GHz frequency band 160 ).
- the user equipment 62 receives or determines a regulatory requirement based on the network signaling value.
- the user equipment 62 may store a table of different regulatory requirements and the associated network signaling value corresponding to each regulatory requirement.
- each network signaling value may correspond to a regulatory requirement for a subrange of the designated frequency band (e.g. VLP/LPI for 5.945 GHz to 6.425 GHz in Korea).
- the user equipment 62 applies the regulation requirement determined from the network signaling value. In this manner, the method 170 may enable the user equipment 62 to determine the frequency-delineated regulatory requirements for a country based on having greater than eight network signaling value.
- FIG. 10 is a flowchart of a method 180 for determining the frequency-delineated regulatory requirements of FIG. 8 for a country based on region-dependent network signaling values, according to embodiments of the present disclosure.
- Any suitable device e.g., a controller
- the method 170 may be implemented by executing instructions stored in a tangible, non-transitory, computer-readable medium, such as the memory 14 or storage 16 , using the processor 12 .
- the method 180 may be performed at least in part by one or more software components, such as an operating systems, one or more software applications, and the like, of the user equipment 62 . While the method 180 is described using steps in a specific sequence, it should be understood that the present disclosure contemplates that the described steps may be performed in different sequences than the sequence illustrated, and certain described steps may be skipped or not performed altogether.
- the user equipment 62 receives a network signaling value (e.g., out of eight possible network signaling values).
- the user equipment 62 receives or determines a geographical region of the user equipment 62 .
- the user equipment 62 may use a location sensor (e.g., a Global Navigation Satellite System (GNSS) sensor such as a Global Positioning System (GPS) Sensor) to receive or determine the geographical region.
- GNSS Global Navigation Satellite System
- GPS Global Positioning System
- the user equipment 62 may utilize a network operator's Public Land Mobile Network (PLMN) value to receive or determine the geographical region. That is, the PLMN may be a combination of mobile communication services offered by a network operator in a specific country.
- PLMN Public Land Mobile Network
- the user equipment 62 may store a table that correlates geographical regions to PLMN values.
- the user equipment 62 may receive a PLMN value associated with the network operator. By referencing the table using the PLMN value, the user equipment 62 may identify the geographical region where the base station 64 (and thus the user equipment 62 ) is located.
- the user equipment 62 receives or determines a regulatory requirement based on the network signaling value and the geographical region.
- the user equipment 62 may store a table of different regulatory requirements for each geographical region, and the associated network signaling value corresponding to each regulatory requirement of a respective geographical region. In particular, the same network signaling values may be used to correspond to different regulatory requirements in different regions.
- the user equipment 62 applies the regulatory requirement determined from the network signaling value and the geographical region. In this manner, the method 180 may enable the user equipment 62 to determine the frequency-delineated regulatory requirements for a country based on region-dependent network signaling values.
- personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users.
- personally identifiable information data should be managed and handled so as to minimize risks of unintentional or unauthorized access or use, and the nature of authorized use should be clearly indicated to users.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Databases & Information Systems (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
- This application claims the benefit of U.S. Provisional Application No. 63/185,115, entitled “Systems and Methods for Supporting Evolving Band Regulations”, filed May 6, 2021, which is hereby incorporated by reference in its entirety for all purposes.
- The present disclosure relates generally to wireless communication, and more specifically to evolving and expanded regulations relating to radio frequency bands.
- In cellular communication, user equipment (e.g., a cell phone) may communicate (e.g., with a base station) under guidelines or rules that may be set and enforced by regulatory and/or standards bodies, such as the Federal Communications Commission (FCC), the Third Generation Partnership Project (3GPP), European Telecommunications Standards Institute (ETSI), and so on. However, when the guidelines or rules are updated, user equipment configured to operate in accordance with the guidelines or rules prior to the update may not be properly or efficiently operate under the updated guidelines or rules.
- A summary of certain embodiments disclosed herein is set forth below. It should be understood that these aspects are presented merely to provide the reader with a brief summary of these certain embodiments and that these aspects are not intended to limit the scope of this disclosure. Indeed, this disclosure may encompass a variety of aspects that may not be set forth below.
- In one embodiment, a method for operating user equipment may include detecting a base station via the user equipment, synchronizing the user equipment to the base station, and receiving, at the user equipment, system information from the base station. The system information may include one or more network signaling flags, the network signaling flags indicating frequency ranges supported by the base station. The method may also include receiving, by the user equipment, one or more of the frequency ranges supported by the user equipment corresponding to the one or more network signaling flags. The method may further include sending an indication of the one or more frequency ranges supported by the user equipment from the user equipment to the base station.
- In another embodiment, a system may include a base station supporting a non-federal network in a coverage area, user equipment in the coverage area communicatively coupled to the base station, environmental sensing capability sensors that determine whether additional non-federal networks are deployed in neighboring coverage areas with respect to the coverage area, and a Spectrum Access System communicatively coupled to the base station and the environmental sensing capability sensors. The Spectrum Access System may receive indications from the environmental sensing capability sensors as to whether the additional non-federal networks are deployed in the neighboring coverage areas. The Spectrum Access System may further, based on receiving the indications that indicate that the additional non-federal networks are deployed in the neighboring coverage areas, send an indication to the base station that the user equipment is permitted to operate using a default power mode.
- In yet another embodiment, a method for operating user equipment may include receiving, at a receiver of the user equipment, a system information block from a base station. The system information block may include a network signaling value of multiple network signaling values corresponding to multiple regulatory requirements of multiple geographical regions. The method may also include receiving, using processing circuitry of the user equipment, a regulatory requirement of the multiple regulatory requirements of a geographical region of the multiple geographical regions corresponding to the network signaling value. The method may further include configuring, using processing circuitry of the user equipment, a transmitter or the receiver of the user equipment to comply with the regulatory requirement.
- In another embodiment, a method for operating user equipment in a geographical region includes receiving, at a receiver of the user equipment, a system information block from a base station. The system information block includes a network signaling value of multiple network signaling values corresponding to multiple regulatory requirements of the geographical region. The method also includes receiving, using processing circuitry of the user equipment, the geographical region that the user equipment is located, and receiving, using the processing circuitry of the user equipment, a regulatory requirement of the multiple regulatory requirements corresponding to the network signaling value and based on the geographical region. The method further includes configuring, using processing circuitry of the user equipment, a transmitter or the receiver of the user equipment to comply with the regulatory requirement.
- Various refinements of the features noted above may exist in relation to various aspects of the present disclosure. Further features may also be incorporated in these various aspects as well. These refinements and additional features may exist individually or in any combination. For instance, various features discussed below in relation to one or more of the illustrated embodiments may be incorporated into any of the above-described aspects of the present disclosure alone or in any combination. The brief summary presented above is intended only to familiarize the reader with certain aspects and contexts of embodiments of the present disclosure without limitation to the claimed subject matter.
- Various aspects of this disclosure may be better understood upon reading the following detailed description and upon reference to the drawings described below in which like numerals refer to like parts.
-
FIG. 1 is a block diagram of an electronic device, according to embodiments of the present disclosure; -
FIG. 2 is a functional block diagram of the electronic device ofFIG. 1 , according to embodiments of the present disclosure; -
FIG. 3 is a frequency chart illustrating a frequency band and subranges of the frequency band, according to embodiment of the present disclosure; -
FIG. 4 is a diagram of a wireless communication network, according to embodiments of the present disclosure; -
FIG. 5 is a flowchart of a method for configuring the transceiver of the user equipment to communicate with the wireless communication network ofFIG. 4 using one or more frequency subranges, according to embodiments of the present disclosure; -
FIG. 6 is diagram of network coverage provided by a wireless communication network, according to embodiments of the present disclosure; -
FIG. 7 is a flowchart of a method for determining whether user equipment may operate without restriction on a restricted frequency band, according to embodiments of the present disclosure; -
FIG. 8 is a frequency diagram of frequency-delineated regulatory requirements for different countries, according to embodiments of the present disclosure; -
FIG. 9 is a flowchart of a method for receiving or determining the frequency-delineated regulatory requirements ofFIG. 8 for a country based on having greater than eight network signaling values, according to embodiments of the present disclosure; and -
FIG. 10 is a flowchart of a method for determining the frequency-delineated regulatory requirements ofFIG. 8 for a country based on region-dependent network signaling values, according to embodiments of the present disclosure. - One or more specific embodiments will be described below. In an effort to provide a concise description of these embodiments, not all features of an actual implementation are described in the specification. It should be appreciated that in the development of any such actual implementation, as in any engineering or design project, numerous implementation-specific decisions must be made to achieve the developers' specific goals, such as compliance with system-related and business-related constraints, which may vary from one implementation to another. Moreover, it should be appreciated that such a development effort might be complex and time consuming, but would nevertheless be a routine undertaking of design, fabrication, and manufacture for those of ordinary skill having the benefit of this disclosure.
- When introducing elements of various embodiments of the present disclosure, the articles “a,” “an,” and “the” are intended to mean that there are one or more of the elements. The terms “comprising,” “including,” and “having” are intended to be inclusive and mean that there may be additional elements other than the listed elements. Additionally, it should be understood that references to “one embodiment” or “an embodiment” of the present disclosure are not intended to be interpreted as excluding the existence of additional embodiments that also incorporate the recited features. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. Use of the term “approximately,” “near,” “about”, and/or “substantially” should be understood to mean including close to a target (e.g., design, value, amount), such as within a margin of any suitable or contemplatable error (e.g., within 0.1% of a target, within 1% of a target, within 5% of a target, within 10% of a target, within 25% of a target, and so on).
- In wireless (e.g., cellular) communication, user equipment (e.g., a cell phone, a smartphone, a tablet, a wearable device, a laptop, and so on) may communicate on a channel of a frequency band (e.g., the n77 or 3.7 gigahertz (GHz) frequency band) with a network (e.g., a wireless communication network) through one or more communication nodes (e.g., base stations). In particular, according to the current Third Generation Partnership Project (3GPP) standard, when establishing communication with the network via base station, the user equipment may detect network coverage (e.g., at a cell supported by the base station) and receive system information including a frequency of a channel from the base station. If the user equipment supports the frequency, the user equipment indicates as such to the base station, the network may allocate the channel to the user equipment, noting that the user equipment supports a frequency band (e.g., the n77 band) that includes the frequency of the channel. When performing a handover event (e.g., transferring network coverage of the user equipment from the base station to another base station) or requesting a secondary cell for carrier aggregation, the base station may indicate (e.g., to the other base station or the network) that the user equipment supports the frequency band based on the user equipment indicating that it supports the frequency of the channel.
- However, if the frequency band is updated (e.g., to include additional or remove a frequency subrange), and the user equipment is not updated in kind, then communication with the user equipment may become less efficient or fail altogether. For example, the 3GPP currently restricts United States (U.S.) operation of the n77 band to the range of 3.7-3.98 gigahertz (GHz). Thus, user equipment may communicate using the n77 band if it complies with the Federal Communications Commission (FCC) rules governing the 3.7-3.98 GHz range. In particular, user equipment may be tested to confirm compliance with the FCC rules related to operate the 3.7-3.98 GHz range. However, if the 3GPP updates the n77 band to allow an additional range of frequencies, such as the 3.5 GHz subrange (e.g., 3.45-3.55 GHz) in the U.S., at least at the time of that update, currently operating user equipment may not comply with the newly added 3.5 GHz band, as the user equipment may not have been tested, and thus not comply, with the 3.5 GHz subrange.
- While this may not cause a problem when the user equipment is initially connecting to the network, because the base station may indicate (e.g., to another base station or the network) that the user equipment supports the n77 band—and not the subrange of the n77 band that the user equipment complies with (e.g., 3.7-3.98 GHz)—to perform a handover event or request a secondary cell for carrier aggregation, the other base station may allocate a channel or the base station may allocate the secondary cell in the 3.5 GHz band for which the user equipment is not compliant. Accordingly, the handover event may fail, in which the user equipment may disconnect from the network, or the secondary cell may not be used by the user equipment, in which the user equipment may not be able to use the full bandwidth allocated to it for communication.
- The presently disclosed embodiments enable the user equipment to indicate supported ranges of frequencies to the base station. In particular, when the base station sends system information to the user equipment based on the user equipment detecting network coverage provided by the base station, the system information may include one or more network signaling values indicative of one or more frequency ranges supported by the base station. For example, the one or more network signaling values may include the original 3.7-3.98 GHz frequency subrange of the n77 band, as well as the newly added 3.45-3.55 GHz frequency subrange of the n77 band. The user equipment may respond to the base station by indicating, using one or more modified maximum power reduction (MPR) behavior bits, which of the one or more frequency ranges are supported by the user equipment. For example, the user equipment may indicate that it supports the 3.7-3.98 GHz frequency subrange, but not the 3.45-3.55 GHz frequency subrange. Accordingly, when performing a handover event or requesting a secondary cell for carrier aggregation, the other base station may allocate a channel or the base station may allocate the secondary cell in a frequency range supported by the user equipment. That is, in the above example, the other base station may allocate a channel or the base station may allocate the secondary cell in the 3.7-3.98 GHz frequency subrange.
- Additionally, frequency bands may be updated (e.g., by the 3GPP) such that transmission and/or reception specification or requirements may change. For example, the n77 band includes the 3.45-3.55 GHz frequency subrange (the “3.5 GHz subrange”), which initially was used by federal incumbent users and was protected by the FCC by blocking any non-federal communications from occurring on the frequency subrange. The FCC further protected the 3.5 GHz subrange blocking any non-federal communications from occurring on the neighboring subrange of 3.55-3.7 GHz frequency subrange, also known as the Citizens Broadband Radio Service (CBRS) band, if the non-federal communications occurred in the same coverage area as those of the federal users. Moreover, if the non-federal communications occurred in a different coverage area as those of the federal users, then the FCC enforced a power backoff of user equipment on the CBRS band (referred to herein as a “CBRS power backoff”) that is greater or “stricter” than a power backoff of the user equipment when not using the CBRS band. This was implemented by setting a network signaling value in a system information block sent from a base station to the user equipment per the 3GPP standard.
- However, the FCC recently allowed non-federal networks and users to use the 3.5 GHz subrange in coverage areas where federal users are not using the subrange. That is, the non-federal networks may be deployed using the 3.5 GHz subrange in coverage areas where there are no federal users utilizing the 3.5 GHz subrange. Accordingly, in the case where user equipment is using the CBRS band, and the user equipment is not located in or adjacent to a coverage area where there are federal users using the 3.5 GHz subrange, then the user equipment may not operate to its full communication potential or efficiency, as the FCC regulations may force it to operate with a greater power backoff (e.g., under the assumption that there are only federal users in the 3.5 GHz subrange).
- The presently disclosed embodiments enable a Spectrum Access System (SAS) controller that allocates spectrum resources in the CBRS band to determine, using Environmental Sensing Capability (ESC) sensors, whether there are non-federal networks in coverage areas. For a coverage area that has non-federal networks (and thus may not have federal users) and are adjacent to coverage areas that have non-federal networks, the SAS controller may cause base stations in the coverage area to indicate (e.g., disable a network signaling value corresponding to the CBRS power backoff) to user equipment that it may operate using use the CBRS band with a default power backoff (e.g., less than the CBRS power backoff). In this manner, user equipment using the CBRS band may operate to its full communication potential or efficiency.
- Moreover, a frequency band may have different regional regulatory specifications or requirements for the same or overlapping frequency subranges in the frequency band. For example, in the newly allocated 6 GHz frequency band, Korea has a low power indoor (LPI) regulatory specification in the 6.425-7.125 GHz subrange, while Brazil has a LPI and very low port (VLP) regulatory specification in the overlapping 5.925-7.125 GHz subrange. Networks may indicate this regulatory specification to user equipment in system information sent by a base station (e.g., via network signaling values). Upon receiving this indication, the user equipment may configure its transceiver to operate using the regulatory specification. However, the 3GPP has only allocated eight network signaling values, and the number of permutations of geographical regions and their regulatory specifications may be much greater than eight. As such, the eight network signaling values may be insufficient to provide the proper regional regulatory specification to the user equipment.
- Some of the presently disclosed embodiments enable expanding the number of network signaling values beyond eight to accommodate for the full number of possible regulatory specifications for each geographical region. In additional or alternative embodiments, the eight network signaling values may correspond to regional regulatory specifications of the region that the user equipment and/or the base stations is located. As such, the user equipment may determine its location (e.g., as determined using a location sensor of the user equipment) or the location of the base station (e.g., as received from the base station, and so on), and determine the regulatory specification based on the network signaling value and the location of the user equipment. In this manner, the user equipment may configure its transceiver to operate using the appropriate regulatory specification.
-
FIG. 1 is a block diagram of anelectronic device 10. Theelectronic device 10 may include, among other things, one or more processors 12 (collectively referred to herein as a single processor for convenience, which may be implemented in any suitable form of processing circuitry),memory 14,nonvolatile storage 16, adisplay 18,input structures 22, an input/output (I/O)interface 24, anetwork interface 26, and apower source 29. The various functional blocks shown inFIG. 1 may include hardware elements (including circuitry), software elements (including computer code stored on a computer-readable medium) or a combination of both hardware and software elements. Theprocessor 12,memory 14, thenonvolatile storage 16, thedisplay 18, theinput structures 22, the input/output (I/O)interface 24, thenetwork interface 26, and/or thepower source 29 may each be communicatively coupled directly or indirectly (e.g., through or via another component, a communication bus, a network) to one another to transmit and/or receive data between one another. It should be noted thatFIG. 1 is merely one example of a particular implementation and is intended to illustrate the types of components that may be present inelectronic device 10. - By way of example, the
electronic device 10 may represent a block diagram of any suitable computing device, including a desktop or notebook computer (e.g., in the form of a MacBook®, MacBook® Pro, MacBook Air®, iMac®, Mac® mini, or Mac Pro® available from Apple Inc. of Cupertino, Calif.), a portable electronic or handheld electronic device such as a wireless electronic device or smartphone (e.g., in the form of a model of an iPhone® available from Apple Inc. of Cupertino, Calif.), a tablet (e.g., in the form of a model of an iPad® available from Apple Inc. of Cupertino, Calif.), a wearable electronic device (e.g., in the form of an Apple Watch® by Apple Inc. of Cupertino, Calif.), and other similar devices. It should be noted that theprocessor 12 and other related items inFIG. 1 may be generally referred to herein as “data processing circuitry.” Such data processing circuitry may be embodied wholly or in part as software, software, hardware, or any combination thereof. Furthermore, theprocessor 12 and other related items inFIG. 1 may be a single contained processing module or may be incorporated wholly or partially within any of the other elements within theelectronic device 10. Theprocessor 12 may be implemented with any combination of general-purpose microprocessors, microcontrollers, digital signal processors (DSPs), field programmable gate array (FPGAs), programmable logic devices (PLDs), controllers, state machines, gated logic, discrete hardware components, dedicated hardware finite state machines, or any other suitable entities that may perform calculations or other manipulations of information. Theprocessors 12 may perform the various functions described herein and below. - In the
electronic device 10 ofFIG. 1 , theprocessor 12 may be operably coupled with amemory 14 and anonvolatile storage 16 to perform various algorithms. Such programs or instructions executed by theprocessor 12 may be stored in any suitable article of manufacture that includes one or more tangible, computer-readable media. The tangible, computer-readable media may include thememory 14 and/or thenonvolatile storage 16, individually or collectively, to store the instructions or routines. Thememory 14 and thenonvolatile storage 16 may include any suitable articles of manufacture for storing data and executable instructions, such as random-access memory, read-only memory, rewritable flash memory, hard drives, and optical discs. In addition, programs (e.g., an operating system) encoded on such a computer program product may also include instructions that may be executed by theprocessor 12 to enable theelectronic device 10 to provide various functionalities. - In certain embodiments, the
display 18 may facilitate users to view images generated on theelectronic device 10. In some embodiments, thedisplay 18 may include a touch screen, which may facilitate user interaction with a user interface of theelectronic device 10. Furthermore, it should be appreciated that, in some embodiments, thedisplay 18 may include one or more liquid crystal displays (LCDs), light-emitting diode (LED) displays, organic light-emitting diode (OLED) displays, active-matrix organic light-emitting diode (AMOLED) displays, or some combination of these and/or other display technologies. - The
input structures 22 of theelectronic device 10 may enable a user to interact with the electronic device 10 (e.g., pressing a button to increase or decrease a volume level). The I/O interface 24 may enableelectronic device 10 to interface with various other electronic devices, as may thenetwork interface 26. In some embodiments, the I/O interface 24 may include an I/O port for a hardwired connection for charging and/or content manipulation using a standard connector and protocol, such as the Lightning connector provided by Apple Inc. of Cupertino, Calif., a universal serial bus (USB), or other similar connector and protocol. Thenetwork interface 26 may include, for example, one or more interfaces for a personal area network (PAN), such as a BLUETOOTH® network, for a local area network (LAN) or wireless local area network (WLAN), such as a network employing one of the IEEE 802.11x family of protocols (e.g., WI-FI®), and/or for a wide area network (WAN), such as any standards related to the Third Generation Partnership Project (3GPP), including, for example, a 3rd generation (3G) cellular network, universal mobile telecommunication system (UMTS), 4th generation (4G) cellular network, long term evolution (LTE®) cellular network, long term evolution license assisted access (LTE-LAA) cellular network, 5th generation (5G) cellular network, and/or New Radio (NR) cellular network, a satellite network, and so on. In particular, thenetwork interface 26 may include, for example, one or more interfaces for using a Release-15 cellular communication standard of the 5G specifications that include the millimeter wave (mmWave) frequency range (e.g., 24.25-300 gigahertz (GHz)). Thenetwork interface 26 of theelectronic device 10 may allow communication over the aforementioned networks (e.g., 5G, Wi-Fi, LTE-LAA, and so forth). - The
network interface 26 may also include one or more interfaces for, for example, broadband fixed wireless access networks (e.g., WIMAX®), mobile broadband Wireless networks (mobile WIMAX®), asynchronous digital subscriber lines (e.g., ADSL, VDSL), digital video broadcasting-terrestrial (DVB-T®) network and its extension DVB Handheld (DVB-H®) network, ultra-wideband (UWB) network, alternating current (AC) power lines, and so forth. - As illustrated, the
network interface 26 may include atransceiver 30. In some embodiments, all or portions of thetransceiver 30 may be disposed within theprocessor 12. Thetransceiver 30 may support transmission and receipt of various wireless signals via one or more antennas. - The
power source 29 of theelectronic device 10 may include any suitable source of power, such as a rechargeable lithium polymer (Li-poly) battery and/or an alternating current (AC) power converter. In certain embodiments, theelectronic device 10 may take the form of a computer, a portable electronic device, a wearable electronic device, or other type of electronic device. -
FIG. 2 is a functional block diagram of theelectronic device 10 that may implement the components shown inFIG. 1 and/or the circuitry and/or components described in the following figures. As illustrated, theprocessor 12, thememory 14, thetransceiver 30, thetransmitter 40, thereceiver 44, and/or the antennas 45 (illustrated as 45 a-45 n) may be communicatively coupled directly or indirectly (e.g., through or via another component, a communication bus, a network) to one another to transmit and/or receive data between one another. - The
electronic device 10 may include thetransmitter 40 and/or thereceiver 44 that respectively enable transmission and reception of data between theelectronic device 10 and a remote location via, for example, a network or direction connection associated with theelectronic device 10 and an external transceiver (e.g., in the form of a cell, eNB (E-UTRAN Node B or Evolved Node B), base stations, and the like. As illustrated, thetransmitter 40 and thereceiver 44 may be combined into thetransceiver 30. Theelectronic device 10 may also have one or more antennas 45 a through 45 n electrically coupled to thetransceiver 30. The antennas 45 a-45 n may be configured in an omnidirectional or directional configuration, in a single-beam, dual-beam, or multi-beam arrangement, and so on. Each antenna 45 may be associated with a one or more beams and various configurations. In some embodiments, each beam, when implement as multi-beam antennas, may correspond to arespective transceiver 30. Theelectronic device 10 may include multiple transmitters, multiple receivers, multiple transceivers, and/or multiple antennas as suitable for various communication standards. - The
transmitter 40 may wirelessly transmit packets having different packet types or functions. For example, thetransmitter 40 may transmit packets of different types generated by theprocessor 12. Thereceiver 44 may wirelessly receive packets having different packet types. In some examples, thereceiver 44 may detect a type of a packet used and process the packet accordingly. In some embodiments, thetransmitter 40 and thereceiver 44 may transmit and receive information via other wired or wireline systems or devices. - As illustrated, the various components of the
electronic device 10 may be coupled together by a bus system 46. The bus system 46 may include a data bus, for example, as well as a power bus, a control signal bus, and a status signal bus, in addition to the data bus. The components of theelectronic device 10 may be coupled together or accept or provide inputs to each other using some other mechanism. - As previously noted, the 3GPP may update frequency bands by expanding the frequency range covered by a frequency band, how a frequency band may be used, and so on.
FIG. 3 is a frequency chart of a frequency band 50 (e.g., the n77 band) and subranges of the frequency band, according to embodiments of the present disclosure. In particular, the n77 band includes asubrange 52 between 3.55 GHz and 3.65 GHz (also referred to as the Citizens Broadband Radio Service (CBRS) band), asubrange 54 between 3.45 GHz and 3.55 GHz (also referred to as the 3.5 GHz subrange), and asubrange 56 between 3.7 GHz and 3.98 GHz (also referred to as the C-band), among others. - In the United States (U.S.), the FCC recently released new rules for the 3.5
GHz subrange 54 within the n77 band to allow for utilization of thesubrange 54 in network communication, while current radio frequency requirements from the 3GPP restrict usage of thesubrange 54 and limit the U.S. to the C-band 56. As such, while user equipment that is currently in use have been tested for compliance with the FCC rules with respect to the C-band 56, these user equipment may not been tested for compliance with the new FCC rules for the 3.5GHz subrange 54, and thus are not permitted to use the 3.5GHz subrange 54. A potential change of the 3GPP specification to permit usage of the 3.5GHz subrange 54 in the n77 band for U.S. operation may lead to two different types of user equipment that support the n77 band in the U.S., those which also support the 3.5 GHz subrange 54 (e.g., because such user equipment has been tested for compliance with the new FCC rules for the 3.5 GHz subrange 54), and those that do not support the 3.5GHz subrange 54. Because a network enabling communication on the n77 band may only assume that user equipment is operable on an entire frequency band (e.g., the n77 band) and not respective subranges of the frequency band (e.g., the C-band 56 vs. the 3.5 GHz subrange 54), the network not be able to distinguish between these two types of user equipment and would only realize that the user equipment does not support 3.5GHz subrange 54 when performing a handover event (e.g., transferring network coverage of the user equipment from one base station to another base station) or requesting a secondary cell for carrier aggregation fails. - With the foregoing in mind,
FIG. 4 is a diagram of a network 60 (e.g., a wireless communication network), according to embodiments of the present disclosure. In particular, thenetwork 60 may provide network coverage touser equipment 62 over a channel in a supported frequency range or band (e.g., the n77 band) via one ormore base stations coverage area 66. As shown inFIG. 3 , the frequency band may include one or more frequency subranges (e.g. theCBRS band 52, the 3.5GHz subrange 54, the C-band 56, and so on). - In particular, the
base station 64 may broadcast a message on one or more supported frequency ranges or channels (e.g. in the n77 band) that are available to establish the connection to theuser equipment 62 in the coverage area orcell 66. If theuser equipment 62 also supports the one or more supported frequency ranges or channels (e.g., in the C-band 56 of the n77 band), then theuser equipment 62 may respond, and thebase station 64 may establish the connection to theuser equipment 62 using a channel of the one or more supported frequency ranges or channels. As illustrated, thebase station 64 may establish the connection to theuser equipment 62 using a channel in the C-band 56. However, if thebase station 64 is not aware of the subranges supported by theuser equipment 62, and only associates the channel that theuser equipment 62 operates on with the entire frequency band (e.g., the n77 band), then thebase station 64 may perform a handover event or request a secondary cell for carrier aggregation based on the entire frequency band, instead of the subrange supported by theuser equipment 62. If theuser equipment 62 only supports the subrange (e.g., the C-band 56) of the frequency band (e.g., the n77 band) and not another subrange (e.g., the 3.5 GHz subrange 54) of the frequency band, then, if the handover event is performed or the secondary cell is implemented using the other subrange that is not supported by theuser equipment 62, the handover event or the implementation of the secondary cell may fail. In such cases, theuser equipment 62 may disconnect from thenetwork 60, or the secondary cell may not be used by theuser equipment 62, in which theuser equipment 62 may not be able to use the full bandwidth allocated to it for communication. - The presently disclosed embodiments include enabling the
base station 64 to send a system information block to theuser equipment 62 having one or more network signaling (NS) flags/values to communicate the frequency subranges supported by thebase station 64. According the 3GPP specification, the system information block is sent to alluser equipment 62 in thecoverage area 66, and the NS flags (which include eight integer value per frequency band) may indicate to theuser equipment 62 the regional regulatory requirements apply theuser equipment 62 in thecoverage area 66. Theuser equipment 62 specification may define additional requirements which become applicable based on the NS flags. Theuser equipment 62 may establish communication with thebase station 64 if theuser equipment 62 supports the frequency band and the applicable NS flags. As such, in some embodiments, the NS flags may be used to indicate to theuser equipment 62 the available frequency subranges (e.g., the C-band 56, the 3.5GHz band 54, and so on) supported by thebase station 64. In theexample network 60 ofFIG. 4 , thebase station 64A may support both the C-band 56 and the 3.5GHz band 54. Accordingly, thebase station 64A may send a system information block with NS flags indicating that it supports the C-band 56 and the 3.5GHz band 54 to theuser equipment 62 in itscoverage area 66. - The presently disclosed embodiments also include enabling the
user equipment 62 to indicate to thebase station 64 the frequency subranges indicated by the NS flags of the receive system information block that are in turn supported by theuser equipment 62. In particular, theuser equipment 62 may utilize one or more modified maximum power reduction (MPR) behavior bits to indicate the frequency subranges supported by theuser equipment 62. The 3GPP specification provides that the MPR bits may specify an allowed decrease in maximum power transmitted by theuser equipment 62 to enable theuser equipment 62 to fulfill regional regulatory requirements (e.g., transmitter adjacent channel leakage ratio requirements). The 3GPP specification also provides that the modified MPR behavior bits may distinguish applicability of different A-MPR (Additional MPR) requirements for different types ofuser equipment 62 in particular frequency bands (e.g., n257 n260, and n261). In the disclosure embodiments, theuser equipment 62 may set the modified MPR behavior bits corresponding to a frequency subrange (e.g., the C-band 56, the 3.5GHz band 54, and so on) that theuser equipment 62 supports to indicate to thebase station 64 that theuser equipment 62 supports the frequency subrange. In this manner, thebase station 64 may be aware of and/or store the frequency subrange(s) supported by theuser equipment 62, and perform a handover event or allocate a secondary cell based on the supported frequency subrange, instead of the entire frequency band (e.g., the n77 band), which may not be supported by theuser equipment 62 in whole, thus preventing disconnection from thenetwork 60 or a drop in bandwidth usage. - In the
example network 60 ofFIG. 4 , theuser equipment 62 may receive the system information block from thebase station 64A indicating that thebase station 64A supports both the C-band 56 and the 3.5GHz band 54. However, theuser equipment 62 may only support the C-band 56. As such, theuser equipment 62 may set modified MPR behavior bits corresponding to the C-band 56, but not the 3.5GHz band 54, and send the modified MPR behavior bits (e.g., in a message) to thebase station 64A. Upon receipt of the modified MPR behavior bits, thebase station 64A may establish aprimary cell 68 with theuser equipment 62 on the supported C-band 56. If thenetwork 60 desires to perform carrier aggregation by establishing a secondary cell, thebase station 64A may not establish asecondary cell 70 using the 3.5GHz band 54, as theuser equipment 62 has indicated that it does not support the 3.5GHz band 54. Instead, thebase station 64A may establish asecondary cell 72 using the C-band 56. Similarly, if theuser equipment 62 moves to anothercoverage area 74, thebase station 64A may perform ahandover event 76 with abase station 64B that provides support to theother coverage area 74. In particular, thebase station 64A may send an indication to thebase station 64B of the frequency subrange(s) supported by the user equipment 62 (e.g., the C-band 56). Accordingly, thebase station 64B may not establishconnection 78 with theuser equipment 62 using the 3.5GHz band 54, as theuser equipment 62 has indicated that it does not support the 3.5GHz band 54. Instead, thebase station 64B may establishconnection 80 with theuser equipment 62 using the C-band 56. Without this indication of user equipment-supported frequency subranges, thenetwork 60 andbase stations 64 may have attempted to establish thesecondary cell 70 or performed thehandover event 76 by establishing theconnection 78 with theuser equipment 62 using the unsupported 3.5GHz band 54, resulting in decreased bandwidth usage or disconnection from thenetwork 60. -
FIG. 5 is a flowchart of amethod 90 for configuring thetransceiver 30 of theuser equipment 62 to communicate with the wireless communication network 60 (e.g. including thebase station 64A and/or thebase station 64B) using one or more frequency subranges, according to embodiments of the present disclosure. Any suitable device (e.g., a controller) that may control components of theuser equipment 62, thebase station 64A and/or thebase station 64B, and the terrestrial network, such as theprocessor 12 of each of these devices or systems, may perform themethod 90. In some embodiments, themethod 90 may be implemented by executing instructions stored in a tangible, non-transitory, computer-readable medium, such as thememory 14 orstorage 16, using theprocessor 12. For example, themethod 90 may be performed at least in part by one or more software components, such as an operating systems, one or more software applications, and the like, of theuser equipment 62, thebase station 64A and/or thebase station 64B, and the terrestrial network. While themethod 90 is described using steps in a specific sequence, it should be understood that the present disclosure contemplates that the described steps may be performed in different sequences than the sequence illustrated, and certain described steps may be skipped or not performed altogether. - At
block 92, theuser equipment 62 detects thebase station 64. In particular, theuser equipment 62 may detect the base station by receiving a radio frequency (RF) signal when theuser equipment 62 enters thecoverage area 66 of thebase station 64. The RF signal may include timing alignment information, among other information. Atblock 94, theuser equipment 62 synchronizes to thebase station 64 by aligning its timing with the timing alignment information of thebase station 64. - At
block 96, thebase station 64 broadcasts system information indicative of frequency subranges supported by thebase station 64. In particular, thebase station 64 may indicate the frequency subranges in the NS flags that are used to indicate the capabilities of thebase station 64. For example, as illustrated inFIG. 4 , thebase station 64 may indicate the C-band 56 and the 3.5GHz band 54 in one or more NS flags of the broadcasted system information. - At
block 98, theuser equipment 62 reads the system information, including the NS flags, received from thebase station 64. The system information may additionally include timing specification, power specifications, Global Positioning System (GPS) coordinates, and/or any other applicable information. In some embodiments, theuser equipment 62 may store the system information in thememory 14 for future usage. - At
block 100, theuser equipment 62 determines or receives the frequency subranges supported by thebase station 64 from the system information block. By way of example, the one or more NS flags may include the C-band 56 and the 3.5GHz band 54 of the n77 band. Atblock 102, theuser equipment 62 indicates the frequency subranges supported by thebase station 64 that are also supported by theuser equipment 62. In particular, theuser equipment 62 may set one or more indicator bits corresponding to one or more frequency subranges that are supported by theuser equipment 62. In some embodiments, the indicator bits may include modified MPR behavior bits. - In one embodiment, the NS flags for the n77 band may include a new NS flag (“NS_X”) corresponding to the 3.5
GHz subrange 54. For the new NS flag, the value for the A-MPR may be set to 0 decibels (thus rendering the NS flag irrelevant for purposes of MPR operation). A modified MPR behavior bit corresponding to the new NS flag may be defined, such that setting the modified MPR behavior bit indicates that theuser equipment 62 supports the 3.5GHz subrange 54. If theuser equipment 62 does not set the modified MPR behavior bit, then theuser equipment 62 is indicating that it does not support the 3.5GHz subrange 54. In some embodiments, the modified MPR behavior bit may correspond directly to 3.5GHz subrange 54. That is the 3GPP may define the modified MPR behavior bit to correspond directly to the n77 band, such that if theuser equipment 62 sets the modified MPR behavior bit, then it implies that theuser equipment 62 supports the 3.5GHz subrange 54. If theuser equipment 62 does not set the modified MPR behavior bit, then it implies that theuser equipment 62 does not support the 3.5 GHz subrange 54 (e.g. theuser equipment 62 only supports the 3.7-3.98 GHz subrange). In such embodiments, theuser equipment 62 may not receive a corresponding NS flag and/or setting the A-MPR to 0 decibels to indicate support for the 3.5GHz subrange 54 may be avoided. While this embodiment refers to the 3.5GHz subrange 54, it should be understood that any suitable frequency subrange of a frequency band, and particularly newly introduced subranges to existing frequency bands, are contemplated. - At
block 104, thebase station 64 configures its resources to theuser equipment 62 within the frequency subranges supported by theuser equipment 62 and thebase station 64. Once the resources are configured and a connection is established between theuser equipment 62 and thebase station 64, theuser equipment 62 and thebase station 64 may send and receiveuser data 106 over the frequency subrange. In this manner, themethod 90 may enable the user equipment to configure thetransceiver 30 to conform to one or more applicable subrange of frequencies and communicate with a terrestrial network (e.g., including thebase station 64 and/or thebase station 64B). - As discussed above, modifications and/or updates to the standards or regulations regarding non-federal networks and frequency bands may lead to inefficiencies. Initially, the 3.5
GHz band 54 was utilized by federal incumbent users. The 3.5GHz band 54 is situated adjacent to the CBRS band 52 (3.55-3.7 GHz). To avoid interfering with the federal users, stricter requirements were introduced for theCBRS band 52 by the FCC. In particular, the FCC currently enforces a power backoff of theuser equipment 62 using the CBRS band 52 (the “CBRS power backoff”) that is greater or “stricter” than a power backoff of theuser equipment 62 when not using the CBRS band 52 (a “default power backoff”). The 3GPP has defined the power backoff as a maximum power by which theuser equipment 62 is to back off (e.g., when approaching a power threshold, to meet out-of-band emission levels, and so on), while an actual power backoff value may be smaller and/or may depend on an implementation of theuser equipment 62. The CBRS power backoff may be referred to as a lower power mode, while the default power backoff may be referred to as a default power mode. Moreover, while the lower power mode refers to a greater power backoff than the default power backoff, it should be understood that the lower power mode, in other applications, may refer to any suitable power characteristics that cause theuser equipment 62 to operate at less power than the default power mode, include decreased transmission power, decreased reception power, less maximum transmission power, less maximum reception power, and so on. - Table 1 below, provided by 3GPP Technical Specification (TS) 38.101-1, illustrates different CBRS power backoff values (e.g., depending on, there are different cases A1-A8) that may be applied by the
user equipment 62. The numbers below are described in decibels (dB) as an amount of power that theuser equipment 62 may backoff to meet regulatory requirements. Table 1 is specific to the CBRS band requirements. -
TABLE 1 A3 A4 A5 A6 A7 A8 A1 A2 Outer/ Outer/ Outer/ Outer/ Outer/ Outer/ Modulation/Waveform Outer Outer Inner Inner Inner Inner Inner Inner DFT-s- PI/2 BPSK [4.5] [6] 4 4 4 4 10.5 4 OFDM QPSK [4.5] [6] 4 4 4 4 10.5 4 16QAM [4.5] [6] 5 4 5 4 11 4 64QAM [4.5] [6] 5 4 5 4 11 4 256QAM [6] 11 CP-OFDM QPSK [5.5] [7] 6 4 6 4 11.5 4 16QAM [5.5] [7] 6 4 6 4 11.5 4 64QAM [5.5] [7] 6 4 6 4 11.5 4 256QAM [7] 11.5 - By comparison, Table 2 below, also provided by 3GPP TS 38.101-1, illustrates different default power backoff values that may be applied by the
user equipment 62. In particular, the default power backoff values in Table 2 are applicable when there are no conditions that exist to operate under the CBRS band requirements, and have lower power backoff values that that of the CBRS power backoff values. That is, theuser equipment 62 may still be allowed to backoff its power, but not to the same degree as the CBRS power backoff values, and, in some cases, not at all. Accordingly, the lower default power backoff values enable theuser equipment 62 to operate at higher transmission and/or reception power, and thus with better performance, then when operating using the higher CBRS power backoff values. -
TABLE 2 MPR (dB) Edge RB Outer RB Inner RB Modulation allocations allocations allocations DFT-s- Pi/2 BPSK ≤3.5 ≤1.2 ≤0.2 OFDM ≤0.5 ≤0.5 0 Pi/2 BPSK w ≤0.5 ≤0 0 Pi/2 BPSK DMRS QPSK ≤1 0 16QAM ≤2 ≤1 64QAM ≤2.5 256QAM ≤4.5 CP-OFDM QPSK ≤3 ≤1.5 16QAM ≤3 ≤2 64QAM ≤3.5 256QAM ≤6.5 - As discussed above, the FCC recently allowed non-federal networks and users to use the 3.5
GHz subrange 54 in coverage areas where federal users are not using the subrange. That is, the non-federal networks may be deployed using the 3.5GHz subrange 54 in coverage areas where there are no federal users utilizing the 3.5GHz subrange 54. Accordingly, in the case whereuser equipment 62 is using theCBRS band 52, and theuser equipment 62 is not located in or adjacent to a coverage area where there are federal users using the 3.5GHz subrange 54, then theuser equipment 62 may not operate to its full communication potential or efficiency, as the FCC regulations may force it to operate with a greater power backoff (e.g., under the assumption that there are only federal users in the 3.5 GHz subrange 54). - With the foregoing in mind,
FIG. 6 is a diagram of network coverage provided by awireless communication network 110, according to embodiments of the present disclosure.Coverage Area A 112 may includefederal users 114 using the 3.5GHz band 54. As such, per FCC regulations, there may be no deployment of non-federal networks 116 (e.g., a cellular network as provided by a network operator to users other thanfederal users 114 via one or more base stations) operating on the 3.5 GHz band and/or theCBRS band 52 withinCoverage Area A 112. Thefederal users 114 may be those defined as “federal incumbent users” by the FCC and/or 47 C.F.R. § 96.15.Coverage Area B 118 andCoverage Areas C 120 may include non-federal users connecting to anon-federal network 116 operating on the 3.5 GHz band and/or theCBRS band 52. To operate on theCBRS band 52 inCoverage Area B 118 andCoverage Area C 120,user equipment 62 may operate under the lower or CBRS power mode (e.g., employing the CBRS power backoff) due to both coverage areas neighboringCoverage Area A 112.Coverage Area D 122 may also include non-federal users connecting to anon-federal network 116 operating on the 3.5 GHz band and/or theCBRS band 52. - Since
Coverage Area D 122 borders only two coverage areas (e.g.,Coverage Area B 118 and Coverage Area C 120), and each neighboring coverage area has anon-federal network 116 operating in the 3.5GHz band 54 or theCBRS band 52, there is no need for theuser equipment 62 to operate on theCBRS band 52 under the lower or CBRS power mode (e.g., employing the CBRS power backoff) since it may be safely assumed thatCoverage Area D 122 does not border a coverage area withfederal users 114. Thus, to determine ifuser equipment 62 in a coverage area may operate under the default power mode (e.g., employing the default power backoff) on theCBRS band 52, a Spectrum Access System (SAS)controller 124 may utilize one or more environmental sensing capability sensors (ESC) 126 to identify the presence and coverage area of non-federal networks (e.g., non-federal network deployments) 116 operating in the 3.5GHz band 54 or theCBRS band 52 to determine the presence and coverage areas offederal users 114 operating on the 3.5GHz band 54. TheSAS controller 124 may include an automated frequency coordinator that manages radio frequency wave sharing on a dynamic, as-needed basis across multiple tiers of access (e.g., federal incumbent users, priority access license users, and general authorized access users). The environmentalsensing capability sensors 126 may include a network of sensors utilized to detect non-federal or federal frequency use in particular frequency subranges (e.g. 3.5 GHz to 3.65 GHz). - In particular, if the environmental
sensing capability sensors 126 do not detect anynon-federal networks 116 using the 3.5GHz band 54 or theCBRS band 52 within the coverage area (e.g., Coverage Area A 114), theSAS controller 124 may assume that there arefederal users 114 in the coverage area. Accordingly, theSAS controller 124 may prevent or blocknon-federal networks 116 anduser equipment 62 attempting to use thenon-federal networks 116 from operating on the 3.5GHz band 54 and theCBRS band 52 in the coverage area. On the other hand, if the environmentalsensing capability sensors 126 detectnon-federal networks 116 using the 3.5GHz band 54 or theCBRS band 52 within a coverage area (e.g., Coverage Area B 118), theSAS controller 124 may determine that there are nofederal users 114 within that coverage area. Moreover, if the environmentalsensing capability sensors 126 detect that there are nonon-federal networks 116 using the 3.5GHz band 54 or theCBRS band 52 within a neighboring coverage area (e.g., Coverage Area A 114) of the coverage area, theSAS controller 124 may assume that there arefederal users 114 in the neighboring coverage area. Accordingly, theSAS controller 124 may communicate to thenon-federal network 116 within the coverage area to indicate touser equipment 62 that operating on theCBRS band 52 is permissible if using the CBRS power backoff. The 3.5GHz band 54 currently has no such restriction imposed on it by standards and/or regulation bodies. - Additionally, if a coverage area (e.g., Coverage Area D 122) has
non-federal networks 116 using the 3.5GHz band 54 or theCBRS band 52 and is bordered only by coverage areas having non-federal networks 116 (e.g.,Coverage Area B 118 and Coverage Area C 120) using the 3.5GHz band 54 or theCBRS band 52, then theSAS controller 124 may communicate to thenon-federal network 116 within the coverage area to indicate touser equipment 62 that operating on theCBRS band 52 using the default power mode is permissible (e.g., theuser equipment 62 may use the default power backoff, and need not operate under the CBRS power mode and use the CBRS power backoff). It should be understood that default power mode may refer to applying the default power backoff as specified by regulatory or standards bodies when operating outside of theCBRS band 52, such as that shown above in Table 2. Again, the 3.5GHz band 54 currently has no such restriction imposed on it by standards and/or regulation bodies. In this manner, theuser equipment 62 using theCBRS band 52 may operate to its full communication potential or efficiency. - With the foregoing in mind,
FIG. 7 is a flowchart of amethod 140 for determining whether theuser equipment 62 may operate without restriction (e.g., operate under the default power mode with the default power backoff) on a restricted frequency band (e.g., the CBRS band 52), according to embodiments of the present disclosure. Any suitable device (e.g., a controller) that may control components of theuser equipment 62, thebase station 64, thenon-federal networks 116, theSAS controller 124, and/or the environmentalsensing capability sensors 126, such as theprocessor 12 of each of these devices or systems, may perform themethod 140. In some embodiments, themethod 140 may be implemented by executing instructions stored in a tangible, non-transitory, computer-readable medium, such as thememory 14 orstorage 16, using theprocessor 12. For example, themethod 140 may be performed at least in part by one or more software components, such as an operating systems, one or more software applications, and the like, of theuser equipment 62, thebase station 64, thenon-federal networks 116, theSAS controller 124, and/or the environmentalsensing capability sensors 126. While themethod 140 is described using steps in a specific sequence, it should be understood that the present disclosure contemplates that the described steps may be performed in different sequences than the sequence illustrated, and certain described steps may be skipped or not performed altogether. - At
block 142, theSAS controller 124 determines whether there arenon-federal networks 116 using the 3.5GHz band 54 or theCBRS band 52 in a coverage area of thebase station 64 and in each neighboring coverage areas adjacent to the coverage area. In particular, theSAS controller 124 may utilize the environmentalsensing capability sensors 126 to detect if there arenon-federal networks 116 using the 3.5GHz band 54 or theCBRS band 52 in the coverage area and the neighboring coverage areas. If the environmentalsensing capability sensors 126 detectnon-federal networks 116 using the 3.5GHz band 54 or theCBRS band 52 in a coverage area, theSAS controller 124 may determine that there are nofederal users 114 in the coverage area. On the other hand, if the environmentalsensing capability sensors 126 do not detect anynon-federal networks 116 using the 3.5GHz band 54 or theCBRS band 52 in a coverage area, theSAS controller 124 may determine that there arefederal users 114 in the coverage area. As described above, there may not be anynon-federal networks 116 on either the 3.5GHz band 54 or theCBRS band 52 whenfederal users 114 are present within a coverage area. - If the
SAS controller 124 determines there arenon-federal networks 116 using the 3.5GHz band 54 or theCBRS band 52 in the coverage area of thebase station 64 and in the neighboring coverage areas adjacent to the coverage area, then, atblock 144, theSAS controller 124 sends an indication to thebase station 64 thatuser equipment 62 connected to thebase station 64 may use the default power mode. For example, inFIG. 6 , there arenon-federal networks 116 inCoverage Area D 122 and its neighboring coverage areas (e.g.,Coverage Area B 118 and Coverage Area C 120). As such, theSAS controller 124 may send an indication to thenon-federal network 116 in Coverage Area D that theuser equipment 62 connected to thenon-federal network 116 may use the default power mode. - After the
SAS controller 124 sends the indication to thebase station 64 that theuser equipment 62 connected to thebase station 64 may use the default power mode inblock 144, or if theSAS controller 124 determines there arenon-federal networks 116 using the 3.5GHz band 54 or theCBRS band 52 in the coverage area of thebase station 64 and in the neighboring coverage areas adjacent to the coverage area inblock 142, then, atblock 146, the base station determines if the indication that theuser equipment 62 may use the default power mode has been received. For example, theSAS controller 124 may determine that there are nonon-federal networks 116 using the 3.5GHz band 54 or theCBRS band 52 inCoverage Area A 112 ofFIG. 6 . - At
block 148, if thebase station 64 has not received the indication thatuser equipment 62 may use the default power mode, then thebase station 64 sends an indication to theuser equipment 62 to transmit using the lower or CBRS power mode when using theCBRS band 52. For example, the base station may set a network signaling value (e.g., network signaling value 27 or NS27 per the 3GPP standard) corresponding to operating using the lower or CBRS power mode that is sent to theuser equipment 62 in a system information block. Atblock 150, theuser equipment 62 transmits data using the CBRS power mode on theCBRS band 52. That is, theuser equipment 62 may configure itstransmitter 40 to use the CBRS power backoff when transmitting data on theCBRS band 52. - At
block 152, if thebase station 64 received the indication thatuser equipment 62 may use default power, then thebase station 64 sends an indication to theuser equipment 62 to transmit with the default power mode on theCBRS band 52. In some embodiments, the indication may include a lack of setting a network signaling value (e.g., the NS27 value) corresponding to operating using the CBRS power mode in a system information block sent to theuser equipment 62. The lack of setting the network signal value removal of the restrictions flag may lead to improved network performance through the allowance of less power backoff as offered by the default power mode when operating on theCBRS band 52. Atblock 154, theuser equipment 62 transmits data using the default power mode on theCBRS band 52. That is, theuser equipment 62 may configure itstransmitter 40 to use the default power mode when transmitting data on theCBRS band 52. - Additionally, a new 6 GHz band has recently been allocated by different countries for network operation. Almost all countries have allocated the new 6 GHZ band (or parts thereof), for unlicensed network operation. As a result, most countries have slightly different regulatory requirements for the new 6 GHz band which may need to be addressed when initializing network communication.
- With the foregoing in mind,
FIG. 8 is a frequency diagram of frequency-delineated regulatory requirements for different countries, according to embodiments of the present disclosure. As illustrated, different countries may have different regulatory requirements for different subranges of a frequency band 160 (e.g., the 6 GHz frequency band). In some cases, these subranges corresponding to different regulatory requirements in different countries may overlap. By way of example, Korea (KR) has a firstregulatory requirement 162 for the frequency range between 5.925 GHz and 6.425 GHz to operate on a Low-Power Indoor (LPI) mode or Very Low Power (VLP) mode, and a secondregulatory requirement 164 for the frequency range between 6.425 GHz and 7.125 GHz to operate on the LPI mode. However, Brazil (BR) has aregulatory requirement 166 for the entire frequency range between 5.925 GHz and 7.125 GHz to operate on the LPI mode or the VLP mode. Moreover, a regulatory requirement in one country may be different than the same regulatory requirement in another country. That is, the LPI mode in Korea may limit maximum transmission power to a power value that is different than that of the LPI mode in Brazil. - To enable
user equipment 62 to operate under the appropriate regulatory requirement, abase station 64 may send the user equipment 62 a network signaling value corresponding to the appropriate regulatory requirement. Theuser equipment 62 may then receive or determine the regulatory requirement based on the network signal value, and operate under the regulatory requirement. However, even though networks signaling values are specific to each frequency band (e.g., 160), eachfrequency band 160 is typically allotted only eight network signaling values. Because each country has different regulatory requirements, and even the same regulatory requirements are different in different countries, eight network signaling values may not be sufficient to cover all the different possible regulatory requirements. - With the foregoing in mind,
FIG. 9 is a flowchart of amethod 170 for receiving or determining the frequency-delineated regulatory requirements ofFIG. 8 for a country based on having greater than eight network signaling values, according to embodiments of the present disclosure. Any suitable device (e.g., a controller) that may control components of theuser equipment 62, such as theprocessor 12 of each of these devices or systems, may perform themethod 170. In some embodiments, themethod 170 may be implemented by executing instructions stored in a tangible, non-transitory, computer-readable medium, such as thememory 14 orstorage 16, using theprocessor 12. For example, themethod 170 may be performed at least in part by one or more software components, such as an operating systems, one or more software applications, and the like, of theuser equipment 62. While themethod 170 is described using steps in a specific sequence, it should be understood that the present disclosure contemplates that the described steps may be performed in different sequences than the sequence illustrated, and certain described steps may be skipped or not performed altogether. - In some embodiments, the network signaling values are increased greater than eight values. In particular, the number of network signaling values may be at least the number of different regulatory requirements for the different countries. With this in mind, at
block 172, theuser equipment 62 receives or determines a network signaling value of multiple network signaling values each corresponding to a regulatory requirement of a geographical region. As described above, there may be at least more than eight network signaling values for the frequency band on which theuser equipment 62 may be operating (e.g., the 6 GHz frequency band 160). Atblock 174, theuser equipment 62 receives or determines a regulatory requirement based on the network signaling value. Theuser equipment 62 may store a table of different regulatory requirements and the associated network signaling value corresponding to each regulatory requirement. In some embodiments, each network signaling value may correspond to a regulatory requirement for a subrange of the designated frequency band (e.g. VLP/LPI for 5.945 GHz to 6.425 GHz in Korea). Atblock 176, theuser equipment 62 applies the regulation requirement determined from the network signaling value. In this manner, themethod 170 may enable theuser equipment 62 to determine the frequency-delineated regulatory requirements for a country based on having greater than eight network signaling value. - Additionally or alternatively, the regulatory requirement may be based on the network signaling value and an indication of a geographical region (e.g., a country).
FIG. 10 is a flowchart of a method 180 for determining the frequency-delineated regulatory requirements ofFIG. 8 for a country based on region-dependent network signaling values, according to embodiments of the present disclosure. Any suitable device (e.g., a controller) that may control components of theuser equipment 62, such as theprocessor 12 of each of these devices or systems, may perform the method 180. In some embodiments, themethod 170 may be implemented by executing instructions stored in a tangible, non-transitory, computer-readable medium, such as thememory 14 orstorage 16, using theprocessor 12. For example, the method 180 may be performed at least in part by one or more software components, such as an operating systems, one or more software applications, and the like, of theuser equipment 62. While the method 180 is described using steps in a specific sequence, it should be understood that the present disclosure contemplates that the described steps may be performed in different sequences than the sequence illustrated, and certain described steps may be skipped or not performed altogether. - At
block 182, theuser equipment 62 receives a network signaling value (e.g., out of eight possible network signaling values). Atblock 184, theuser equipment 62 receives or determines a geographical region of theuser equipment 62. In some embodiments, theuser equipment 62 may use a location sensor (e.g., a Global Navigation Satellite System (GNSS) sensor such as a Global Positioning System (GPS) Sensor) to receive or determine the geographical region. In additional or alternative embodiments, theuser equipment 62 may utilize a network operator's Public Land Mobile Network (PLMN) value to receive or determine the geographical region. That is, the PLMN may be a combination of mobile communication services offered by a network operator in a specific country. Theuser equipment 62 may store a table that correlates geographical regions to PLMN values. When theuser equipment 62 connects to abase station 64, theuser equipment 62 may receive a PLMN value associated with the network operator. By referencing the table using the PLMN value, theuser equipment 62 may identify the geographical region where the base station 64 (and thus the user equipment 62) is located. - At
block 186, theuser equipment 62 receives or determines a regulatory requirement based on the network signaling value and the geographical region. Theuser equipment 62 may store a table of different regulatory requirements for each geographical region, and the associated network signaling value corresponding to each regulatory requirement of a respective geographical region. In particular, the same network signaling values may be used to correspond to different regulatory requirements in different regions. Atblock 188, theuser equipment 62 applies the regulatory requirement determined from the network signaling value and the geographical region. In this manner, the method 180 may enable theuser equipment 62 to determine the frequency-delineated regulatory requirements for a country based on region-dependent network signaling values. - The specific embodiments described above have been shown by way of example, and it should be understood that these embodiments may be susceptible to various modifications and alternative forms. It should be further understood that the claims are not intended to be limited to the particular forms disclosed, but rather to cover all modifications, equivalents, and alternatives falling within the spirit and scope of this disclosure.
- The techniques presented and claimed herein are referenced and applied to material objects and concrete examples of a practical nature that demonstrably improve the present technical field and, as such, are not abstract, intangible or purely theoretical. Further, if any claims appended to the end of this specification contain one or more elements designated as “means for [perform]ing [a function] . . . ” or “step for [perform]ing [a function] . . . ,” it is intended that such elements are to be interpreted under 35 U.S.C. 112(f). However, for any claims containing elements designated in any other manner, it is intended that such elements are not to be interpreted under 35 U.S.C. 112(f).
- It is well understood that the use of personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users. In particular, personally identifiable information data should be managed and handled so as to minimize risks of unintentional or unauthorized access or use, and the nature of authorized use should be clearly indicated to users.
Claims (23)
Priority Applications (7)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US17/512,462 US20220361089A1 (en) | 2021-05-06 | 2021-10-27 | Systems and methods for supporting evolving band regulations |
EP22166004.6A EP4087297A1 (en) | 2021-05-06 | 2022-03-31 | Systems and methods for supporting evolving band regulations |
EP22197576.6A EP4142324A1 (en) | 2021-05-06 | 2022-03-31 | Systems and methods for supporting evolving band regulations |
CN202210454230.XA CN115314983A (en) | 2021-05-06 | 2022-04-27 | System and method for supporting evolved band policing |
CN202211101657.8A CN115442797A (en) | 2021-05-06 | 2022-04-27 | System and method for supporting evolved band policing |
US17/902,526 US20230007570A1 (en) | 2021-05-06 | 2022-09-02 | Systems and methods for supporting evolving band regulations |
US18/464,954 US20230422152A1 (en) | 2021-05-06 | 2023-09-11 | Systems and methods for supporting evolving band regulations |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US202163185115P | 2021-05-06 | 2021-05-06 | |
US17/512,462 US20220361089A1 (en) | 2021-05-06 | 2021-10-27 | Systems and methods for supporting evolving band regulations |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US17/902,526 Continuation US20230007570A1 (en) | 2021-05-06 | 2022-09-02 | Systems and methods for supporting evolving band regulations |
Publications (1)
Publication Number | Publication Date |
---|---|
US20220361089A1 true US20220361089A1 (en) | 2022-11-10 |
Family
ID=81325871
Family Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US17/512,462 Pending US20220361089A1 (en) | 2021-05-06 | 2021-10-27 | Systems and methods for supporting evolving band regulations |
US17/902,526 Pending US20230007570A1 (en) | 2021-05-06 | 2022-09-02 | Systems and methods for supporting evolving band regulations |
US18/464,954 Pending US20230422152A1 (en) | 2021-05-06 | 2023-09-11 | Systems and methods for supporting evolving band regulations |
Family Applications After (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US17/902,526 Pending US20230007570A1 (en) | 2021-05-06 | 2022-09-02 | Systems and methods for supporting evolving band regulations |
US18/464,954 Pending US20230422152A1 (en) | 2021-05-06 | 2023-09-11 | Systems and methods for supporting evolving band regulations |
Country Status (3)
Country | Link |
---|---|
US (3) | US20220361089A1 (en) |
EP (2) | EP4142324A1 (en) |
CN (2) | CN115442797A (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20230199507A1 (en) * | 2021-12-16 | 2023-06-22 | Dell Products, L.P. | Low-latency network edge spectrum-as-a-service controller |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20190281543A1 (en) * | 2016-11-11 | 2019-09-12 | Beijing Xiaomi Mobile Software Co., Ltd. | Communication method and device |
US11159302B2 (en) * | 2018-11-01 | 2021-10-26 | Samsung Electronics Co., Ltd. | Method and apparatus for performing communication in mobile communication system |
Family Cites Families (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11019655B2 (en) * | 2017-01-19 | 2021-05-25 | Apple Inc. | Advertisement of NR capability to user equipment |
JP2021016010A (en) * | 2017-10-06 | 2021-02-12 | 株式会社Nttドコモ | User equipment and base station apparatus |
JP2021504994A (en) * | 2017-11-24 | 2021-02-15 | オッポ広東移動通信有限公司Guangdong Oppo Mobile Telecommunications Corp., Ltd. | Random access methods, frequency spectrum reporting methods, terminals and network devices |
KR102598542B1 (en) * | 2018-03-08 | 2023-11-06 | 삼성전자주식회사 | Method for transmitting carrier combination for carrier aggregation and electronic device therefor |
EP4192121A1 (en) * | 2018-06-21 | 2023-06-07 | Fg Innovation Company Limited | Method and apparatus for performing cell (re)selection in wireless communication system |
WO2020069174A1 (en) * | 2018-09-27 | 2020-04-02 | Intel Corporation | Ue capability indication for multi-connectivity handover |
US12048042B2 (en) * | 2019-03-29 | 2024-07-23 | Huawei Technologies Co., Ltd. | Reconfiguration method, terminal device, and communications system |
CN113748745A (en) * | 2020-03-31 | 2021-12-03 | Oppo广东移动通信有限公司 | Information indication method, device, equipment and storage medium |
-
2021
- 2021-10-27 US US17/512,462 patent/US20220361089A1/en active Pending
-
2022
- 2022-03-31 EP EP22197576.6A patent/EP4142324A1/en active Pending
- 2022-03-31 EP EP22166004.6A patent/EP4087297A1/en active Pending
- 2022-04-27 CN CN202211101657.8A patent/CN115442797A/en active Pending
- 2022-04-27 CN CN202210454230.XA patent/CN115314983A/en active Pending
- 2022-09-02 US US17/902,526 patent/US20230007570A1/en active Pending
-
2023
- 2023-09-11 US US18/464,954 patent/US20230422152A1/en active Pending
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20190281543A1 (en) * | 2016-11-11 | 2019-09-12 | Beijing Xiaomi Mobile Software Co., Ltd. | Communication method and device |
US11159302B2 (en) * | 2018-11-01 | 2021-10-26 | Samsung Electronics Co., Ltd. | Method and apparatus for performing communication in mobile communication system |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20230199507A1 (en) * | 2021-12-16 | 2023-06-22 | Dell Products, L.P. | Low-latency network edge spectrum-as-a-service controller |
Also Published As
Publication number | Publication date |
---|---|
US20230007570A1 (en) | 2023-01-05 |
CN115442797A (en) | 2022-12-06 |
US20230422152A1 (en) | 2023-12-28 |
CN115314983A (en) | 2022-11-08 |
EP4142324A1 (en) | 2023-03-01 |
EP4087297A1 (en) | 2022-11-09 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20160242186A1 (en) | Dynamic Carrier Selection Via Auxiliary Carriers In Unlicensed Band | |
EP3776997B1 (en) | Synchronization signal design for unlicensed spectrum access using cellular communications | |
US12035367B2 (en) | Channel sensing indication when COT sharing in NR systems operating in unlicensed spectrum | |
CN103947272B (en) | The method and computer-readable medium implemented at terminal device, terminal device | |
US12063598B2 (en) | Reduced power consumption by obtaining time domain resource allocation patterns in advance via additional signaling | |
US11778516B2 (en) | Device category in 3GPP communications | |
US11540276B2 (en) | Wideband transmission with narrowband monitoring for new radio unlicensed spectrum (NRU) | |
US12127176B2 (en) | Uplink transmission support for reduced capability devices in wireless communications | |
US20230422152A1 (en) | Systems and methods for supporting evolving band regulations | |
US11395282B2 (en) | Cellular burst detection in unlicensed spectrum | |
EP4266722A1 (en) | Systems and methods for supporting evolving band regulations | |
CN115397000A (en) | System and method for compliance with indoor/outdoor unlicensed band regulations | |
EP2849472A1 (en) | Mobile communication method, wireless base station, and mobile station | |
US12063645B2 (en) | Scheduling restriction enhancements for LTE and 5G NR dynamic spectrum sharing | |
US20230199744A1 (en) | Regional classification of resource block allocation during power boost for shaped transmission | |
US20230199743A1 (en) | Regional classification of resource block allocation during power boost for shaped transmission | |
CN116939582A (en) | System and method for supporting evolved band policing | |
CN113875275A (en) | Method and device for signal transmission |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: APPLE INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:IOFFE, ANATOLIY SERGEY;POPP, DANIEL;WAGNER, ELMAR;AND OTHERS;SIGNING DATES FROM 20211018 TO 20211022;REEL/FRAME:057998/0117 |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: FINAL REJECTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE AFTER FINAL ACTION FORWARDED TO EXAMINER |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |