WO2024127124A1

WO2024127124A1 - Sub-band reporting in wireless communication systems

Info

Publication number: WO2024127124A1
Application number: PCT/IB2023/061751
Authority: WO
Inventors: Hiromasa Umeda; Tero Henttonen
Original assignee: Nokia Technologies Oy
Priority date: 2022-12-13
Filing date: 2023-11-21
Publication date: 2024-06-20

Abstract

Systems, methods, apparatuses, and computer program products for the smooth migration of regionally-defined sub-bands and other methods of sub-band reporting and handling in wireless communication systems are provided. For example, a method can include generating, by a device, a frequency band list comprising a plurality of frequency bands in reverse chronological order of definition. The method can also include providing, by the device, the frequency band list to a user equipment.

Description

TITLE:

SUB-BAND REPORTING IN WIRELESS COMMUNICATION SYSTEMS

CROSS-REFERENCE TO RELATED APPLICATION

[0001] This application claims priority from, and the benefit of US Provisional Application No. 63/432242, filed December 13, 2022, the contents of which are hereby included by reference in their entirety.

FIELD:

[0002] Some example embodiments may generally relate to communications including mobile or wireless telecommunication systems, such as Long Term Evolution (LTE) or fifth generation (5G) radio access technology or new radio (NR) access technology, or other communications systems including subsequent generations of the same or similar standards. For example, certain example embodiments may generally relate to the smooth migration of regionally-defined sub-bands and other methods of sub-band reporting and handling in wireless communication systems.

BACKGROUND:

[0003] Examples of mobile or wireless telecommunication systems may include the Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN), Long Term Evolution (LTE) Evolved UTRAN (E-UTRAN), LTE-Advanced (LTE-A), MulteFire, LTE-A Pro, and/or fifth generation (5G) radio access technology or new radio (NR) access technology. 5G wireless systems refer to the next generation (NG) of radio systems and network architecture. A 5G system is mostly built on a 5G new radio (NR), but a 5G (or NG) network can also build on the E-UTRA radio. From release 18 (Rel-18) onward, 5G is referred to as 5G advanced. It is estimated that NR provides bitrates on the order of 10-20 Gbit/s or higher, and can support at least service categories such as enhanced mobile broadband (eMBB) and ultra-reliable low-latency-communication (URLLC) as well as massive machine type communication (mMTC). NR is expected to deliver extreme broadband and ultra-robust, low latency connectivity and massive networking to support the Internet of Things (loT). With loT and machine-to- machine (M2M) communication becoming more widespread, there will be a growing need for networks that meet the needs of lower power, low data rate, and long battery life. The next generation radio access network (NG-RAN) represents the RAN for 5G, which can provide both NR and LTE (and LTE-Advanced) radio accesses. It is noted that, in 5G, the nodes that can provide radio access functionality to a user equipment (i.e., similar to the Node B, NB, in UTRAN or the evolved NB, eNB, in LTE) may be named next-generation NB (gNB) when built on NR radio and may be named next-generation eNB (NG-eNB) when built on E-UTRA radio. 6G is currently under development and may replace 5G and 5G advanced.

SUMMARY:

[0004] An embodiment may be directed to an apparatus. The apparatus may include at least one processor and at least memory storing instructions. The instructions, when executed by the at least one processor, may cause the apparatus at least to perform generating a frequency band list comprising a plurality of frequency bands in reverse chronological order of definition. The instructions, when executed by the at least one processor, may also cause the apparatus at least to perform providing the frequency band list to a user equipment.

[0005] An embodiment may be directed to a method. The method can include generating, by a device, a frequency band list comprising a plurality of frequency bands in reverse chronological order of definition. The method can also include providing, by the device, the frequency band list to a user equipment.

[0006] An embodiment can be directed to an apparatus. The apparatus can include means for generating a frequency band list comprising a plurality of frequency bands in reverse chronological order of definition. The apparatus can also include means for providing the frequency band list to a user equipment.

BRIEF DESCRIPTION OF THE DRAWINGS:

[0007] For proper understanding of example embodiments, reference should be made to the accompanying drawings, wherein:

[0008] FIG. 1 illustrates a solution for single carrier operation; [0009] FIG. 2 illustrates intra-band non-contiguous uplink carrier aggregation operation;

[00010] FIG. 3 illustrates single band operation with new band numbering;

[0010] FIG. 4 illustrates new band numbering definition, according to certain embodiments;

[0011] FIG. 5 illustrates a method according to certain embodiments; and

[0012] FIG. 6 illustrates an example block diagram of a system, according to an embodiment.

DETAILED DESCRIPTION:

[0013] It will be readily understood that the components of certain example embodiments, as generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of some example embodiments of systems, methods, apparatuses, and computer program products for providing the smooth migration of regionally-defined sub-bands and other methods of sub-band reporting and handling in wireless communication systems, is not intended to limit the scope of certain embodiments but is representative of selected example embodiments.

[0014] The features, structures, or characteristics of example embodiments described throughout this specification may be combined in any suitable manner in one or more example embodiments. For example, the usage of the phrases “certain embodiments,” “some embodiments,” or other similar language, throughout this specification refers to the fact that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment. Thus, appearances of the phrases “in certain embodiments,” “in some embodiments,” “in other embodiments,” or other similar language, throughout this specification do not necessarily all refer to the same group of embodiments, and the described features, structures, or characteristics may be combined in any suitable manner in one or more example embodiments.

[0015] Certain embodiments may have various aspects and features. These aspects and features may be applied alone or in any desired combination with one another. Other features, procedures, and elements may also be applied in combination with some or all of the aspects and features disclosed herein.

[0016] Additionally, if desired, the different functions or procedures discussed below may be performed in a different order and/or concurrently with each other. Furthermore, if desired, one or more of the described functions or procedures may be optional or may be combined. As such, the following description should be considered as illustrative of the principles and teachings of certain example embodiments, and not in limitation thereof.

[0017] In the third generation partnership project (3GPP), there may be a definition of a band. In some countries only part of the band, a sub-band, may be released and available with a regulation at a given time. Thus, 3GPP can have defined the band in a global manner that encompasses frequency allocation that are larger than a specific country may allow. Accordingly, only part of the band may be available in some countries. Even if the part is contained in the band and a UE that supports the band is compliant to 3GPP specifications, regulations may not allow the UE to camp on a cell of the sub-band of the band without a corresponding local certification. For example, band n77 experienced this issue in the USA and Canada.

[0018] 3GPP addressed this issue with new network signaling (NS). Other approaches to this issue may include defining new UE capabilities indicating “subband portions” or defining new band numbers that are used for the “extended” part of the band. Certain embodiments overcome challenges in such approaches by defining a new band with a new NS-value as was done for the band n77.

[0019] To better understand the challenges that certain embodiments overcome, consider that band n77, namely 3300 - 4200 MHz, was defined as a globally available band. When the requirements for n77 were specified, the availability of full spectrum of n77 in USA was not clear. Later, a sub-band of 3700-3980MHz within n77 became available in USA, but it was requested that a UE not camp on any other carriers outside the sub-band in the USA. In order to overcome this restriction, 3GPP introduced a note to n77. It was noted that it was considered that no introduction of a new band is the only way not to increase the number of band combinations. The note specifically indicated that in the USA this band, namely n77, was restricted to 3700 - 3980 MHz, but the details of how UE ensured this was left unspecified.

[0020] It’s noted that the way in which UEs are restricted to camp on a cell of 3700 - 3980 MHz, which can be referred to as sub-band A for convenience, in n77 in USA was not specified at that time and no issue had been identified for a while. Later, an additional sub-block of 3450 - 3550 MHz, which can be referred to as subband B for convenience, was released in USA. There may be some advantage to disabling the legacy UEs not to camp on a cell of sub-block B. 3GPP defined a new NS_55 as well as CA_NC_NS_55/CA_NS_55 as illustrated in FIGs. 1 and 2 respectively, and defined a new UE capability of extendedBand-n77-rl6 to indicate that a new UE supports both sub-band A and sub-band B in USA.

[0021] FIG. 1 illustrates a solution for single carrier operation. In the example of FIG. 1, a legacy UE that does not understand the network signaling, NS_55, may consider a cell of sub-band B cell-barred. Thus, such a legacy UE may consider itself restricted from camping on the cell. The legacy UE also cannot understand NS_55 in the sub-band A, but the legacy UE can read NS_01, and consequently can still camp on the cell of sub-band A. By contrast, a relatively new UE, which understands NS_55, can camp on the cell of sub-band A or B without any problem. [0022] FIG. 2 illustrates intra-band non-contiguous uplink (UL) carrier aggregation (CA) operation. In the example of FIG. 2, a network can know that a legacy UE, which does not report extendedBand-n77-rl6, but reports, for example, CA_n77(2A), cannot conduct intra band non-contiguous UL CA between carriers in sub-band A and those in sub-band B. Additionally, the network can know that a relatively new UE, which reports extendedBand-n77-rl6 as well as CA_n77(2A) can conduct intra band non-contiguous UL CA across sub-band A and B. This approach, however, may rely on having many standardized exceptions and relevant notes or similar texts in the specifications. For instance, before this approach was used, it was a rule that all the NS value for UL CA shall be the same. Furthermore, if additional sub-band on top of A and B was introduced, the specifications as well as operational conditions like which NS should be indicated in each cell, the order in which multiple NS(s) are indicated, and the like, become even more complex. [0023] Hence, rather than reusing an existing band or introducing a new band, a new band numbering can be used, together with a premise that if a new band numbering within an existing band is supported by a UE, then it can be considered that the UE can also support all the band combinations including the existing band. For example, if an (example) band number nX was defined for band n77, then UE indicating support for band nX would also always support band n77. Such UE would also support any band combinations where n77 is replaced by nX, or vice versa. This approach may prevent an increase in the number of band combinations due to a new band and can be referred to as a new band numbering.

[0024] This approach may be clean and clear when it comes to single band operation or inter band combinations as can be seen in FIG. 3. Specifically, FIG. 3 illustrates single band operation with new band numbering. In this example, the “nX” part was the original “n77” in the USA, while the “nY” was the newly allocated block for the US. If new band numbering had been taken into use, “nX” would have been just “n77” with or without a new capability like extendedBand-n77-rl6, or just some other band number, for example “nX” = “nl59”, and “nY” would have been some other band number, for example “nY” = “nl60”.

[0025] Under this approach, a legacy UE indicates only nX support and a new UE indicates both nX and nY. In this way, a network can clearly know a given UE’s ability so that resource management, such as handover (HO), can be properly handled. Such an approach also frees the network from the concern for NS handling for single carrier operation as well as CA. This solution, however, may add complexity when it comes to intra band non-contiguous CA, or even contiguous CA if a new sub-band is released in a way that it is adjacent to one or more existing sub- band(s). In particular, while a given UE may support nX and nY, supporting these bands individually does not necessarily imply that the UE can support every arbitrary combination of those bands. As the number of sub-bands increases, recently developed UEs may need to indicate more and more band numberings, which may get cumbersome to signal and even cause inter-operability device testing (IODT) issues.

[0026] For example, CA_nX-nY is not intra-band non-contiguous UL CA. CA_nX- nY can be considered as inter-band CA with nX and nY. While the performance requirements may follow CA_n77(2A), strictly speaking, the network may not be able to handle CA_nX-nY exactly as CA_n77(2A). Hence, the introduction of a new band numbering based on the existing band definition may create additional complexities.

[0027] In certain embodiments, a “sub-band” allocation can include an entire frequency band allocation that is supported at the time the new sub-band is created. Thus, a new sub-band can be defined such that all previously defined sub-band(s) are confined within the new sub-band, even if the sub-bands are not contiguous. In other words, each new sub-band can contain the previous sub-bands. Thus, the subbands can be free of principle in continuity of frequency. In other words, there may be neither requirement nor prohibition that the sub-bands be continuous in frequency. Additionally, a rule can be defined for setting the order of the sub-bands listed in a frequencyBandList in each cell. The rule can be that the order of the subbands listed in a frequencyBandList in each cell can be listed in reverse chronological order. More particularly, the rule can indicate that this sub-band numbering can be followed when the frequencies of the newer sub-band overlap with the older sub-band. Thus, UEs supporting newer versions can choose the largest sub-band first).

[0028] This approach may avoid the complexity due to the introduction of new band numbering. UEs may always support the largest sub-band allocation available at the time of certification, and the network can signal which sub-bands are allowed for camping on a cell. As a result, UEs that only support older sub-bands may only camp on the cell if the network indicates the older sub-band numbers.

[0029] A new band definition free of principle in continuity of frequency may be applied not only to a new band numbering, but also to a normal band definition. For example, there is no need to define in a way that a frequency division duplex (FDD) band is one UL block paired with one downlink (DL) block or a time division duplex (TDD) band is one UL/DL block. Instead, a band may be defined with multiple frequency blocks to reduce the complexity.

[0030] FIG. 4 illustrates new band numbering definition, according to certain embodiments. FIG. 4 illustrates an example implementation that may work with n77 in the USA, showing three sub-band allocations for the band n77. More specifically, a new sub-band may be defined to confine a sub-band(s) defined before in a way free of principle in continuity of frequency as illustrated in Figure 4.

[0031] In this example, the first-created sub-band A is defined as nX. A first cell may operate at sub-band A. Sub-band A and later created sub-band B are defined jointly as nY which is one band, but with non-continuity. A second cell may operate at sub-band B. In order to show that the same approach can be used with more than two sub-bands, nZ is included as a third created sub-band, including sub-band A and B as well as a third sub-band, which following the same convention might be designated sub-band C. A third cell may operate at sub-band C. Instead of designating each of the newly added sub-blocks as a separate sub-band, in certain embodiments, the sub-bands are designated as a non-continuous collection of the already-included sub-blocks and the newly added sub-block.

[0032] Additionally, a rule can be defined for setting the order of the sub-bands listed in a frequencyBandList in each cell in reverse chronological order whenever their frequencies overlap each other. In frequencyBandList within SIB1 of a cell, the leftmost cell (for example, a cell using the leftmost frequencies in the Figure 4, such as the third cell in the previous discussion) can indicate nZ only since there is no overlap with other band numberings. Indication of only nZ may prevent all the legacy UEs that support nX, nY and/or n77 from camping on this cell. The middle cell (for example, a cell using the middle frequencies in FIG. 4, such as the second cell in the previous discussion) can indicate band numberings in the order of nZ and nY. It is noted that nY may not be listed before nZ. If a UE supports both nY and nZ, the UE may camp on the middle cell as nY. If the UE also supports for example, CA_nZ(2A), the UE may not be able to utilize that feature because the UE may not support CA_nYA-nZA. Thus, band numbering may be defined per sub-band, such that, for example nZ and nY do not overlap each other. The rightmost cell (for example, a cell using the rightmost frequencies in FIG. 4, namely the first cell in the previous discussion) can indicate band numberings in the order of nZ, nY, and nX, which may allow all UEs to camp on the cell, indicating that frequency allocation is supported by all UEs supporting nZ, nY, or nX.

[0033] For single carrier operation, a UE that supports nX can just camp on the rightmost cell. A UE that supports nY can camp on the middle cell or rightmost cell. [0034] A UE that supports nZ can camp on the leftmost, middle or rightmost cell. [0035] A UE that supports a recently defined new band numbering is not necessarily required to report the legacy band numberings or related band combinations. More specifically, in Fig. 3, a recently developed UE needs to report nX as well as nY to use both sub-bands, but with certain embodiments, only reporting of the latest band numbering is needed.

[0036] For intra-band UL non-contiguous and/or contiguous CA operation, a UE that supports nX can use CA within nX. A UE that supports nY can use CA across the middle and/or rightmost cells simultaneously if the UE wants. A UE supports nZ can use CA across the leftmost, middle and/or rightmost cells simultaneously if the UE wants.

[0037] The network can handle each of the UEs as normal CA UE, avoiding the need for special care as in the new numbering illustrated in FIGs. 1-3.

[0038] Third generation partnership project (3GPP) technical specification (TS) 38.331 v.17.2.0, clause 5.2.2.4.2, indicates that UE is to select the first available frequency band in the list. For example, if the UE supports one or more of the frequency bands indicated in the frequencyBandList for downlink for TDD, or one or more of the frequency bands indicated in the frequencyBandList for uplink for FDD, the UE can select the first frequency band in the frequencyBandList, for FDD from frequencyBandList for uplink, or for TDD from frequencyBandList for downlink.

[0039] FIG. 5 illustrates a method according to certain embodiments. As shown in FIG. 5, a method can include, at 510, generating, by a device, a frequency band list comprising a plurality of frequency bands in chronological order of definition. The device may be a base station, such a next generation Node B (gNB) or the like. The method can also include, at 520, providing, by the device, the frequency band list to a user equipment. For example, the frequency band list may be provided to the UE via radio resource control (RRC) signalling either via system information (for example via system information block (SIB) such as SIB1) or via dedicated signalling (for example, via RRCReconfiguration message). The signalling in SIB1 can indicate the supported frequencies in a cell, via the field frequencyBandList, to the user equipment, and the UE can select the first supported frequency from the list when camping on the cell.

[0040] The plurality of frequency bands can include an earlier-defined band and a later-defined band. The chronological order in the list can involve the later-defined band being listed before the earlier-defined band in the list. This may also be known as reverse chronological order. The definition here can refer to the definition within standards organization(s) or by the authorities for a region.

[0041] The later-defined band can include a first sub-band and a second sub-band. The earlier-defined band can include the first sub-band but not the second sub-band. For example, the earlier-defined band may be only the first-sub-band. An example of this is shown in FIG. 4, in which nY includes one band that is not part of nX and also includes nX. The first sub-band and the second sub-band may be noncontiguous as illustrated in FIG. 4, but may alternatively be contiguous.

[0042] The later-defined band can include the earlier-defined band and a further subband. In other words, the later-defined band can strictly be a super-set of the earlier- defined band, as illustrated in the examples in FIG. 4.

[0043] As shown in FIG. 5, the method can further include, at 530, receiving, at the device from the user equipment, an indication of a supported band from frequency band list. The indication may be explicit or implicit. For example, if the UE supports nY and nX but not nZ, then the UE may indicate nY to the NW, because nY is the first supported band in the list. The method can further include, at 540, determining, by the device, a level of support of sub-bands based on the indication. The method can additionally include taking further network control operations based on such determination. For example, at 550, the network can hand over, by the device, the user equipment based on the determined level of support.

[0044] For example, if a UE supports nY and nX, but not nZ, no matter what the content of the list is, the UE may be unable to indicate a capability of nZ band support and may be unable to camp on the cell as nZ. The network can list bands in an order of priority. The UE can use the first supported band in the list among supported bands, if multiple bands are supported to be available for the cell. Thus, in this example, the UE may use nY in the cell. Optionally, the UE may indicate both nY and nX to the network. In this example, because the UE does not support nZ, the UE may not indicate nZ to the network. In this way, the network may be able to determine the level of support of which the UE is capable.

[0045] FIG. 6 illustrates an example of a system that includes an apparatus 10, according to an embodiment. In an embodiment, apparatus 10 may be a node, host, or server in a communications network or serving such a network. For example, apparatus 10 may be a network node, satellite, base station, a Node B, an evolved Node B (eNB), 5G Node B or access point, next generation Node B (NG-NB or gNB), TRP, HAPS, integrated access and backhaul (IAB) node, and/or a WLAN access point, associated with a radio access network, such as an LTE network, 5G or NR. In some example embodiments, apparatus 10 may be gNB or other similar radio node, for instance.

[0046] It should be understood that, in some example embodiments, apparatus 10 may include an edge cloud server as a distributed computing system where the server and the radio node may be stand-alone apparatuses communicating with each other via a radio path or via a wired connection, or they may be located in a same entity communicating via a wired connection. For instance, in certain example embodiments where apparatus 10 represents a gNB, it may be configured in a central unit (CU) and distributed unit (DU) architecture that divides the gNB functionality. In such an architecture, the CU may be a logical node that includes gNB functions such as transfer of user data, mobility control, radio access network sharing, positioning, and/or session management, etc. The CU may control the operation of DU(s) over a mid-haul interface, referred to as an Fl interface, and the DU(s) may have one or more radio unit (RU) connected with the DU(s) over a front-haul interface. The DU may be a logical node that includes a subset of the gNB functions, depending on the functional split option. It should be noted that one of ordinary skill in the art would understand that apparatus 10 may include components or features not shown in FIG. 6.

[0047] As illustrated in the example of FIG. 6, apparatus 10 may include a processor 12 for processing information and executing instructions or operations. Processor 12 may be any type of general or specific purpose processor. In fact, processor 12 may include one or more of general-purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), and processors based on a multi-core processor architecture, or any other processing means, as examples. While a single processor 12 is shown in FIG. 6, multiple processors may be utilized according to other embodiments. For example, it should be understood that, in certain embodiments, apparatus 10 may include two or more processors that may form a multiprocessor system (e.g., in this case processor 12 may represent a multiprocessor) that may support multiprocessing. In certain embodiments, the multiprocessor system may be tightly coupled or loosely coupled (e.g., to form a computer cluster).

[0048] Processor 12 may perform functions associated with the operation of apparatus 10, which may include, for example, precoding of antenna gain/phase parameters, encoding and decoding of individual bits forming a communication message, formatting of information, and overall control of the apparatus 10, including processes related to the smooth migration of regionally-defined sub-bands and other methods of sub-band reporting and handling in wireless communication systems.

[0049] Apparatus 10 may further include or be coupled to a memory 14 (internal or external), which may be coupled to processor 12, for storing information and instructions that may be executed by processor 12. Memory 14 may be one or more memories and of any type suitable to the local application environment, and may be implemented using any suitable volatile or nonvolatile data storage technology such as a semiconductor-based memory device, a magnetic memory device and system, an optical memory device and system, fixed memory, and/or removable memory. For example, memory 14 can be include any combination of random access memory (RAM), read only memory (ROM), static storage such as a magnetic or optical disk, hard disk drive (HDD), or any other type of non-transitory machine or computer readable media, or other appropriate storing means. The instructions stored in memory 14 may include program instructions or computer program code that, when executed by processor 12, enable the apparatus 10 to perform tasks as described herein.

[0050] In an embodiment, apparatus 10 may further include or be coupled to (internal or external) a drive or port that is configured to accept and read an external computer readable storage medium, such as an optical disc, USB drive, flash drive, or any other storage medium. For example, the external computer readable storage medium may store a computer program or software for execution by processor 12 and/or apparatus 10.

[0051] In some embodiments, apparatus 10 may also include or be coupled to one or more antennas 15 for transmitting and receiving signals and/or data to and from apparatus 10. Apparatus 10 may further include or be coupled to a transceiver 18 configured to transmit and receive information. The transceiver 18 may include, for example, a plurality of radio interfaces that may be coupled to the antenna(s) 15, or may include any other appropriate transceiving means. The radio interfaces may correspond to a plurality of radio access technologies including one or more of global system for mobile communications (GSM), narrow band Internet of Things (NB-IoT), LTE, 5G, WLAN, Bluetooth (BT), Bluetooth Low Energy (BT-LE), nearfield communication (NFC), radio frequency identifier (RFID), ultrawideband (UWB), MulteFire, and the like. The radio interface may include components, such as filters, converters (for example, digital-to-analog converters and the like), mappers, a Fast Fourier Transform (FFT) module, and the like, to generate symbols for a transmission via one or more downlinks and to receive symbols (via an uplink, for example).

[0052] As such, transceiver 18 may be configured to modulate information on to a carrier waveform for transmission by the antenna(s) 15 and demodulate information received via the antenna(s) 15 for further processing by other elements of apparatus 10. In other embodiments, transceiver 18 may be capable of transmitting and receiving signals or data directly. Additionally or alternatively, in some embodiments, apparatus 10 may include an input and/or output device (I/O device), or an input/output means.

[0053] In an embodiment, memory 14 may store software modules that provide functionality when executed by processor 12. The modules may include, for example, an operating system that provides operating system functionality for apparatus 10. The memory may also store one or more functional modules, such as an application or program, to provide additional functionality for apparatus 10. The components of apparatus 10 may be implemented in hardware, or as any suitable combination of hardware and software.

[0054] According to some embodiments, processor 12 and memory 14 may be included in or may form a part of processing circuitry/means or control circuitry/means. In addition, in some embodiments, transceiver 18 may be included in or may form a part of transceiver circuitry/means.

[0055] As used herein, the term “circuitry” may refer to hardware-only circuitry implementations (e.g., analog and/or digital circuitry), combinations of hardware circuits and software, combinations of analog and/or digital hardware circuits with software/firmware, any portions of hardware processor(s) with software (including digital signal processors) that work together to cause an apparatus (e.g., apparatus 10) to perform various functions, and/or hardware circuit(s) and/or processor(s), or portions thereof, that use software for operation but where the software may not be present when it is not needed for operation. As a further example, as used herein, the term “circuitry” may also cover an implementation of merely a hardware circuit or processor (or multiple processors), or portion of a hardware circuit or processor, and its accompanying software and/or firmware. The term circuitry may also cover, for example, a baseband integrated circuit in a server, cellular network node or device, or other computing or network device.

[0056] As introduced above, in certain embodiments, apparatus 10 may be or may be a part of a network element or RAN node, such as a base station, access point, Node B, eNB, gNB, TRP, HAPS, IAB node, relay node, WLAN access point, satellite, or the like. In one example embodiment, apparatus 10 may be a gNB or other radio node, or may be a CU and/or DU of a gNB. According to certain embodiments, apparatus 10 may be controlled by memory 14 and processor 12 to perform the functions associated with any of the embodiments described herein. For example, in some embodiments, apparatus 10 may be configured to perform one or more of the processes depicted in any of the flow charts or signaling diagrams described herein, such as those illustrated in FIGs. 4 and 5, or any other method described herein. In some embodiments, as discussed herein, apparatus 10 may be configured to perform a procedure relating to providing the smooth migration of regionally-defined sub-bands and other methods of sub-band reporting and handling in wireless communication systems, for example.

[0057] FIG. 6 further illustrates an example of an apparatus 20, according to an embodiment. In an embodiment, apparatus 20 may be a node or element in a communications network or associated with such a network, such as a UE, communication node, mobile equipment (ME), mobile station, mobile device, stationary device, loT device, or other device. As described herein, a UE may alternatively be referred to as, for example, a mobile station, mobile equipment, mobile unit, mobile device, user device, subscriber station, wireless terminal, tablet, smart phone, loT device, sensor or NB-IoT device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications thereof (e.g., remote surgery), an industrial device and applications thereof (e.g., a robot and/or other wireless devices operating in an industrial and/or an automated processing chain context), a consumer electronics device, a device operating on commercial and/or industrial wireless networks, or the like. As one example, apparatus 20 may be implemented in, for instance, a wireless handheld device, a wireless plug-in accessory, or the like.

[0058] In some example embodiments, apparatus 20 may include one or more processors, one or more computer-readable storage medium (for example, memory, storage, or the like), one or more radio access components (for example, a modem, a transceiver, or the like), and/or a user interface. In some embodiments, apparatus 20 may be configured to operate using one or more radio access technologies, such as GSM, LTE, LTE-A, NR, 5G, WLAN, WiFi, NB-IoT, Bluetooth, NFC, MulteFire, and/or any other radio access technologies. It should be noted that one of ordinary skill in the art would understand that apparatus 20 may include components or features not shown in FIG. 6.

[0059] As illustrated in the example of FIG. 6, apparatus 20 may include or be coupled to a processor 22 for processing information and executing instructions or operations. Processor 22 may be any type of general or specific purpose processor. In fact, processor 22 may include one or more of general-purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs), field- programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), and processors based on a multi-core processor architecture, as examples. While a single processor 22 is shown in FIG. 6, multiple processors may be utilized according to other embodiments. For example, it should be understood that, in certain embodiments, apparatus 20 may include two or more processors that may form a multiprocessor system (e.g., in this case processor 22 may represent a multiprocessor) that may support multiprocessing. In certain embodiments, the multiprocessor system may be tightly coupled or loosely coupled (e.g., to form a computer cluster).

[0060] Processor 22 may perform functions associated with the operation of apparatus 20 including, as some examples, precoding of antenna gain/phase parameters, encoding and decoding of individual bits forming a communication message, formatting of information, and overall control of the apparatus 20, including processes related to management of communication resources.

[0061] Apparatus 20 may further include or be coupled to a memory 24 (internal or external), which may be coupled to processor 22, for storing information and instructions that may be executed by processor 22. Memory 24 may be one or more memories and of any type suitable to the local application environment, and may be implemented using any suitable volatile or nonvolatile data storage technology such as a semiconductor-based memory device, a magnetic memory device and system, an optical memory device and system, fixed memory, and/or removable memory. For example, memory 24 can include any combination of random access memory (RAM), read only memory (ROM), static storage such as a magnetic or optical disk, hard disk drive (HDD), or any other type of non-transitory machine or computer readable media. The instructions stored in memory 24 may include program instructions or computer program code that, when executed by processor 22, enable the apparatus 20 to perform tasks as described herein.

[0062] In an embodiment, apparatus 20 may further include or be coupled to (internal or external) a drive or port that is configured to accept and read an external computer readable storage medium, such as an optical disc, USB drive, flash drive, or any other storage medium. For example, the external computer readable storage medium may store a computer program or software for execution by processor 22 and/or apparatus 20. [0063] In some embodiments, apparatus 20 may also include or be coupled to one or more antennas 25 for receiving a downlink signal and for transmitting via an uplink from apparatus 20. Apparatus 20 may further include a transceiver 28 configured to transmit and receive information. The transceiver 28 may also include a radio interface (e.g., a modem) coupled to the antenna 25. The radio interface may correspond to a plurality of radio access technologies including one or more of GSM, LTE, LTE-A, 5G, NR, WLAN, NB-IoT, Bluetooth, BT-LE, NFC, RFID, UWB, and the like. The radio interface may include other components, such as filters, converters (for example, digital-to-analog converters and the like), symbol demappers, signal shaping components, an Inverse Fast Fourier Transform (IFFT) module, and the like, to process symbols, such as OFDM symbols, carried by a downlink or an uplink.

[0064] For instance, transceiver 28 may be configured to modulate information on to a carrier waveform for transmission by the antenna(s) 25 and demodulate information received via the antenna(s) 25 for further processing by other elements of apparatus 20. In other embodiments, transceiver 28 may be capable of transmitting and receiving signals or data directly. Additionally or alternatively, in some embodiments, apparatus 20 may include an input and/or output device (I/O device). In certain embodiments, apparatus 20 may further include a user interface, such as a graphical user interface or touchscreen.

[0065] In an embodiment, memory 24 stores software modules that provide functionality when executed by processor 22. The modules may include, for example, an operating system that provides operating system functionality for apparatus 20. The memory may also store one or more functional modules, such as an application or program, to provide additional functionality for apparatus 20. The components of apparatus 20 may be implemented in hardware, or as any suitable combination of hardware and software. According to an example embodiment, apparatus 20 may optionally be configured to communicate with apparatus 10 via a wireless or wired communications link 70 according to any radio access technology, such as NR.

[0066] According to some embodiments, processor 22 and memory 24 may be included in or may form a part of processing circuitry or control circuitry. In addition, in some embodiments, transceiver 28 may be included in or may form a part of transceiving circuitry.

[0067] As discussed above, according to some embodiments, apparatus 20 may be a UE, SL UE, relay UE, mobile device, mobile station, ME, loT device and/or NB- loT device, or the like, for example. According to certain embodiments, apparatus 20 may be controlled by memory 24 and processor 22 to perform the functions associated with any of the embodiments described herein, such as one or more of the operations illustrated in, or described with respect to, FIGs. 4 and 5, or any other method described herein. For example, in an embodiment, apparatus 20 may be controlled to perform a process relating to providing the smooth migration of regionally-defined sub-bands and other methods of sub-band reporting and handling in wireless communication systems, as described in detail elsewhere herein.

[0068] In some embodiments, an apparatus (e.g., apparatus 10 and/or apparatus 20) may include means for performing a method, a process, or any of the variants discussed herein. Examples of the means may include one or more processors, memory, controllers, transmitters, receivers, and/or computer program code for causing the performance of any of the operations discussed herein.

[0069] In view of the foregoing, certain example embodiments provide several technological improvements, enhancements, and/or advantages over existing technological processes and constitute an improvement at least to the technological field of wireless network control and/or management. Certain embodiments may have various benefits and/or advantages. For example, certain embodiments may allow a reduction in the complexity of handling changing levels of support by various generations of UEs in a network (for example as a result of the Federal Communications Commission making an additional frequency block available for mobile communications). Such handling may be performed in a way that may reduce network signaling and simplify communications between UEs and the network. Certain embodiments may decrease workloads for specifications as well as development of UEs and networks since certain embodiments may stabilize or automate the relevant considerations for them.

[0070] In some example embodiments, the functionality of any of the methods, processes, signaling diagrams, algorithms or flow charts described herein may be implemented by software and/or computer program code or portions of code stored in memory or other computer readable or tangible media, and may be executed by a processor.

[0071] In some example embodiments, an apparatus may include or be associated with at least one software application, module, unit or entity configured as arithmetic operation(s), or as a program or portions of programs (including an added or updated software routine), which may be executed by at least one operation processor or controller. Programs, also called program products or computer programs, including software routines, applets and macros, may be stored in any apparatus-readable data storage medium and may include program instructions to perform particular tasks. A computer program product may include one or more computer-executable components which, when the program is run, are configured to carry out some example embodiments. The one or more computer-executable components may be at least one software code or portions of code. Modifications and configurations required for implementing the functionality of an example embodiment may be performed as routine(s), which may be implemented as added or updated software routine(s). In one example, software routine(s) may be downloaded into the apparatus.

[0072] As an example, software or computer program code or portions of code may be in source code form, object code form, or in some intermediate form, and may be stored in some sort of carrier, distribution medium, or computer readable medium, which may be any entity or device capable of carrying the program. Such carriers may include a record medium, computer memory, read-only memory, photoelectrical and/or electrical carrier signal, telecommunications signal, and/or software distribution package, for example. Depending on the processing power needed, the computer program may be executed in a single electronic digital computer or it may be distributed amongst a number of computers. The computer readable medium or computer readable storage medium may be a non-transitory medium. The term “non-transitory” as used herein, is a limitation of the medium itself (i.e. tangible, not a signal) as opposed to a limitation on data storage persistency (e.g. RAM vs. ROM). [0073] In other example embodiments, the functionality of example embodiments may be performed by hardware or circuitry included in an apparatus, for example through the use of an application specific integrated circuit (ASIC), a programmable gate array (PGA), a field programmable gate array (FPGA), or any other combination of hardware and software. In yet another example embodiment, the functionality of example embodiments may be implemented as a signal, such as a non-tangible means, that can be carried by an electromagnetic signal downloaded from the Internet or other network.

[0074] According to an example embodiment, an apparatus, such as a node, device, or a corresponding component, may be configured as circuitry, a computer or a microprocessor, such as single-chip computer element, or as a chipset, which may include at least a memory for providing storage capacity used for arithmetic operation(s) and/or an operation processor for executing the arithmetic operation(s). [0075] Example embodiments described herein may apply to both singular and plural implementations, regardless of whether singular or plural language is used in connection with describing certain embodiments. For example, an embodiment that describes operations of a single network node may also apply to example embodiments that include multiple instances of the network node, and vice versa.

[0076] One having ordinary skill in the art will readily understand that the example embodiments as discussed above may be practiced with procedures in a different order, and/or with hardware elements in configurations which are different than those which are disclosed. Therefore, although some embodiments have been described based upon these example embodiments, it would be apparent to those of skill in the art that certain modifications, variations, and alternative constructions would be apparent, while remaining within the spirit and scope of example embodiments.

[0077] PARTIAE GEOSSARY:

[0078] BC Band Combination

[0079] CA Carrier Aggregation

[0080] DL Downlink

[0081] FDD Frequency Division Duplex

[0082] gNB 5G Node-B [0083] IODT Inter Operability Device Testing

[0084] NC Non Contiguous

[0085] NS Network Signalling

[0086] TDD Time Division Duplexing

[0087] UE User Equipment

[0088] UL Uplink

Claims

We Claim:

1. An apparatus, comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to perform generating a frequency band list comprising a plurality of frequency bands in reverse chronological order of definition; and providing the frequency band list to a user equipment.

2. The apparatus of claim 1, wherein the plurality of frequency bands comprise an earlier-defined band and a later-defined band, wherein the reverse chronological order comprises the later-defined band being listed before the earlier- defined band.

3. The apparatus of claim 2, wherein the later-defined band comprises a first sub-band and a second sub-band, and wherein the earlier-defined band consists of the first sub-band.

4. The apparatus of claim 3, wherein the first sub-band and the second subband are non-contiguous with one another.

5. The apparatus of claim 3, wherein the first sub-band and the second subband are contiguous with each other.

6. The apparatus of any of claims 2 to 5, wherein the later-defined band comprises the earlier-defined band and a further sub-band.

7. The apparatus of any of claims 1 to 6, wherein the instructions, when executed by the at least one processor, further cause the apparatus at least to perform receiving, from the user equipment, an indication of a supported band from the frequency band list; and determining a level of support of sub-bands based on the indication.

8. The apparatus of claim 7, wherein the instructions, when executed by the at least one processor, further cause the apparatus at least to perform handing over the user equipment based on the determined level of support.

9. A method, comprising: generating, by a device, a frequency band list comprising a plurality of frequency bands in reverse chronological order of definition; and providing, by the device, the frequency band list to a user equipment.

10. The method of claim 9, wherein the plurality of frequency bands comprise an earlier-defined band and a later-defined band, wherein the reverse chronological order comprises the later-defined band being listed before the earlier- defined band.

11. The method of claim 10, wherein the later-defined band comprises a first sub-band and a second sub-band, and wherein the earlier-defined band consists of the first sub-band.

12. The method of claim 11, wherein the first sub-band and the second subband are non-contiguous with one another.

13. The method of claim 11, wherein the first sub-band and the second subband are contiguous with each other.

14. The method of any of claims 10 to 13, wherein the later-defined band comprises the earlier-defined band and a further sub-band.

15. The method of any of claims 9 to 14, further comprising: receiving, at the device from the user equipment, an indication of a supported band from the frequency band list; and determining, by the device, a level of support of sub-bands based on the indication.

16. The method of claim 15, further comprising: handing over, by the device, the user equipment based on the determined level of support.

17. An apparatus, comprising: means for generating a frequency band list comprising a plurality of frequency bands in reverse chronological order of definition; and means for providing the frequency band list to a user equipment.

18. The apparatus of claim 17, wherein the plurality of frequency bands comprise an earlier-defined band and a later-defined band, wherein the reverse chronological order comprises the later-defined band being listed before the earlier- defined band.

19. The apparatus of claim 18, wherein the later-defined band comprises a first sub-band and a second sub-band, and wherein the earlier-defined band consists of the first sub-band.

20. The apparatus of claim 19, wherein the first sub-band and the second subband are non-contiguous with one another.

21. The apparatus of claim 19, wherein the first sub-band and the second subband are contiguous with each other.

22. The apparatus of any of claims 18 to 21, wherein the later-defined band comprises the earlier-defined band and a further sub-band.

23. The apparatus of any of claims 17 to 22, further comprising: means for receiving, from the user equipment, an indication of a supported band from the frequency band list; and means for determining a level of support of sub-bands based on the indication.

24. The apparatus of claim 23, further comprising: means for handing over the user equipment based on the determined level of support.

25. A computer program product encoding instructions for performing the method of any of claims 9-16.

26. A non-transitory computer-readable medium encoded with instructions that, when executed in hardware, perform the method of any of claims 9-16.