Wireless system wider bandwidth carrier indication

Abstract

Methods and apparatuses for indicating carriers are disclosed. One method includes sending a candidate carrier configuration, where the candidate carrier configuration includes at least one of a frequency location, a frequency offset, an operation mode, NRS information, CRS information, a power offset, and a EUTRA system bandwidth of at least one candidate carrier.

Description

Technical Field

[0001] The topics disclosed here generally relate to wireless communication, and more specifically to indicator carriers. Background Technology

[0002] The following abbreviations are defined herein, and at least some of them are referenced in the following description: 3rd Generation Partnership Project (3GPP), European Telecommunications Standards Institute (ETSI), Frequency Division Duplex (FDD), Frequency Division Multiple Access (FDMA), Long Term Evolution (LTE), New Radio (NR), Very Large Scale Integration (VLSI), Random Access Memory (RAM), Read-Only Memory (ROM), Erasable Programmable Read-Only Memory (EPROM or Flash Memory), Compact Disc Read-Only Memory (CD-ROM), Local Area Network (LAN), Wide Area Network (WAN), Personal Digital Assistant (PDA), User Equipment (UE), Uplink (UL), Evolved Node B (eNB), Next Generation Node B (gNB), New Radio (NR), Downlink (DL), Central Processing Unit (CPU), Graphics Processing Unit (GPU), Field Programmable Gate Array (FPGA), Dynamic RAM (DRAM), Synchronous Dynamic RAM (SDRAM), Static RAM (SRAM), Liquid Crystal Display (LCD), Light Emitting Diode (LED), Organic LED (OLED), Next Generation Node B (gNB), Orthogonal Frequency Division Multiplexing (OFDM), Radio Resource Control (RRC), Reference Signal (RS), Single Carrier Frequency Division Multiple Access (SC-FDMA), Time Division Duplex (TDD), Time Division Multiplexing (TDM), User Entity / Equipment (Mobile Terminal) (UE), Uplink (UL), Universal Mobile Telecommunications System (UMTS), Global Microwave Access Interoperability (WiMAX), Internet of Things (IoT), Narrowband Internet of Things (NB-IoT or NBIoT), Long Term Evolution (LTE), Narrowband (NB), Narrowband Primary Synchronization Signal (NPSS), Narrowband Secondary Synchronization Signal (NSSS), Narrowband Physical Broadcast Channel (NPBCH or NB-PBCH), System Information (SI), System Information Block (SIB), System Information Block Type 1-NB (NB-SIB1), Physical Downlink Shared Channel (PDSCH), Physical Uplink Shared Channel (PUSCH), Downlink Control Information (DCI), Physical Resource Block (PRB), Universal Mobile Telecommunications System (UMTS), Evolved UMTS Terrestrial Radio Access (E-UTRA or EUTRA).

[0003] An anchored carrier is a carrier that carries at least synchronization and broadcast signals. In NB-IoT, the anchored carrier is the carrier that the UE assumes will transmit the Narrowband Primary Synchronization Signal (NPSS), the Narrowband Secondary Synchronization Signal (NSSS), and the Narrowband Physical Broadcast Channel (NPBCH), where NPSS and NSSS are synchronization signals and NPBCH contains broadcast signals. On the other hand, a non-anchored carrier is a carrier that the UE does not assume will transmit NPSS, NSSS, and NPBCH.

[0004] In version 14, unanchored carriers can be configured as paging and random access carriers. Without any restrictions, unanchored carriers can be configured on any frequency carrier. For example, an unanchored carrier does not have to be an adjacent carrier to an anchor carrier. Furthermore, an unanchored carrier can be configured as a carrier independent of anchor carriers with different operating modes, and so on.

[0005] In version 17, non-anchored carriers can be configured for PDSCH and PUSCH transmissions. The frequency (location) of the non-anchored carrier needs to be indicated to the UE. Furthermore, there is a requirement to support data transmission on more than one carrier—for example, two or three carriers—(which can be anchored carriers, non-anchored carriers, or both). Therefore, it is necessary to indicate the location (frequency) of multiple carriers to the UE. Summary of the Invention

[0006] Methods and apparatus for indicating carrier waves are disclosed.

[0007] In one embodiment, a method includes transmitting a candidate carrier configuration, wherein the candidate carrier configuration includes at least one of the following: frequency location, frequency offset, operating mode, NRS information, CRS information, power offset, and EUTRA system bandwidth of at least one candidate carrier.

[0008] In one embodiment, each candidate carrier is associated with a frequency index. The method further includes transmitting a bitmap indicator that indicates whether each candidate carrier can be used for data transmission.

[0009] In another embodiment, a candidate carrier is a reference carrier of a carrier set. The method further includes transmitting the number of carriers in the carrier set.

[0010] In some embodiments, the frequency offset is a relative frequency offset to the frequency of the anchor carrier. Furthermore, the frequency offset is measured in units of basic resource blocks. The frequency location can be determined by at least one of the following: frequency offset, the frequency of the anchor carrier, the number of carriers in the carrier set, the operating mode of the anchor carrier, and the EUTRA system bandwidth.

[0011] In some embodiments, the candidate carrier is a neighboring carrier of the anchor carrier. The method further includes transmitting a number of carriers adjacent to the anchor carrier on each side. Alternatively, the number of carriers adjacent to the anchor carrier on each side may be 1 or 2.

[0012] In one embodiment, the base station unit includes a transmitter that transmits a candidate carrier configuration, wherein the candidate carrier configuration includes at least one of the following: frequency position, frequency offset, operating mode, NRS information, CRS information, power offset, and EUTRA system bandwidth of at least one candidate carrier.

[0013] In another embodiment, a method includes receiving a candidate carrier configuration, wherein the candidate carrier configuration includes at least one of the following: frequency position, frequency offset, operating mode, NRS information, CRS information, power offset, and EUTRA system bandwidth of at least one candidate carrier.

[0014] In another embodiment, the remote unit includes a receiver that receives a candidate carrier configuration, wherein the candidate carrier configuration includes at least one of the following: frequency position, frequency offset, operating mode, NRS information, CRS information, power offset, and EUTRA system bandwidth of at least one candidate carrier. Attached Figure Description

[0015] A more specific description of the embodiments briefly described above will be presented with reference to the specific embodiments illustrated in the accompanying drawings. It should be understood that these drawings depict only some embodiments and are therefore not to be considered limiting. The embodiments will be described and illustrated with additional specificity and detail using the drawings, in which:

[0016] Figure 1 This is a schematic diagram illustrating a carrier indication according to a first embodiment and a second embodiment of the first embodiment;

[0017] Figure 2 This is a schematic diagram illustrating a carrier indication according to a third embodiment of the first embodiment;

[0018] Figure 3 This is a schematic diagram illustrating a carrier indication according to a fourth embodiment of the first embodiment;

[0019] Figure 4 This is a schematic diagram illustrating a carrier indication according to the first embodiment of the second embodiment;

[0020] Figure 5 Describe an example of NB-IoT anchored carrier deployment for band protection;

[0021] Figure 6 This is a schematic diagram illustrating a carrier indication according to a second embodiment of the second embodiment;

[0022] Figure 7 This is a schematic diagram illustrating a carrier indication according to a third embodiment of the second embodiment;

[0023] Figure 8 This is a schematic flowchart illustrating an embodiment of a method for indicating a carrier wave;

[0024] Figure 9 This is a schematic flowchart illustrating yet another embodiment of a method for indicating a carrier wave; and

[0025] Figure 10 This is a schematic block diagram illustrating an apparatus according to one embodiment. Detailed Implementation

[0026] As will be appreciated by those skilled in the art, aspects of the embodiments can be embodied as a system, apparatus, method, or program product. Therefore, embodiments can take the form of a completely hardware embodiment, a completely software embodiment (including firmware, resident software, microcode, etc.), or an embodiment combining software and hardware aspects, which may generally be referred to herein as “circuit,” “module,” or “system.” Furthermore, embodiments can take the form of a program product embodied in one or more computer-readable storage devices, referred to hereinafter as code, storing machine-readable code, computer-readable code, and / or program code. The storage device can be a tangible, non-transitory, and / or non-transferable storage device. The storage device may not embody signals. In one embodiment, the storage device uses only signals for accessing the code.

[0027] Some functional units described in this specification may be labeled "modules" to give more specific emphasis to their independent implementation. For example, a module may be implemented as a hardware circuit that includes custom very large-scale integration (VLSI) circuitry or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. Modules may also be implemented using programmable hardware devices such as field-programmable gate arrays, programmable array logic, programmable logic devices, etc.

[0028] Modules can also be implemented in code and / or software to be executed by various types of processors. Identified code modules may, for example, comprise one or more physical or logical blocks of executable code, which may be organized, for example, as objects, procedures, or functions. However, the executables of identified modules do not necessarily have to be physically located together, but may include fundamentally different instructions stored in different locations that, when logically joined together, comprise the module and achieve the stated purpose of the module.

[0029] In practice, a code module can contain a single instruction or many instructions, and can even be distributed across several different code segments, across different programs, and across several memory devices. Similarly, operational data can be identified and illustrated within the module, and can be represented in any suitable form and organized within any suitable type of data structure. This operational data can be collected as a single dataset or can be distributed across different locations, including different computer-readable storage devices. Where the module or part of a module is implemented in software, the software portion is stored on one or more computer-readable storage devices.

[0030] Any combination of one or more computer-readable media may be used. A computer-readable medium may be a computer-readable storage medium. A computer-readable storage medium may be a storage device for storing code. A storage device may be, for example, but not necessarily, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.

[0031] A non-exhaustive list of more specific examples of storage devices will include the following: electrical connections having one or more wires, portable computer floppy disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), portable compact disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing. In the context of this document, a computer-readable storage medium can be any tangible medium capable of containing or storing a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0032] The code used to perform the operations of the embodiments may include any number of lines and may be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Python, Ruby, Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" programming language, and / or machine languages ​​such as assembly language. The code may execute entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or may make a connection to an external computer (e.g., via the Internet using an Internet service provider).

[0033] Throughout this specification, references to "an embodiment," "embodiment," or similar language mean that a particular feature, structure, or characteristic described in conjunction with that embodiment is included in at least one embodiment. Therefore, unless otherwise expressly specified, the phrases "in an embodiment," "in an embodiment," and similar language appearing throughout this specification may, but not necessarily all, refer to the same embodiment, but rather mean "one or more, but not all, embodiments." Unless otherwise expressly specified, the terms "comprising," "including," "having," and variations thereof mean "including, but not limited to,". Unless otherwise expressly specified, the enumerated list of items does not imply that any or all of these items are mutually exclusive. Unless otherwise expressly specified, the terms "a," "an," and "the" also mean "one or more".

[0034] Furthermore, the features, structures, or characteristics of the various embodiments described can be combined in any suitable manner. Numerous specific details, such as examples of programming, software modules, user selection, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., are provided in the following description to provide a thorough understanding of the embodiments. However, those skilled in the art will recognize that the embodiments can be practiced without one or more of the specific details or with other methods, components, materials, etc. In other instances, well-known structures, materials, or operations have not been shown or described in detail to avoid obscuring aspects of the embodiments.

[0035] Various aspects of different embodiments are described below with reference to schematic flowcharts and / or schematic block diagrams of methods, apparatus, systems, and program products according to embodiments. It should be understood that each block in the schematic flowcharts and / or schematic block diagrams, as well as combinations of blocks in the schematic flowcharts and / or schematic block diagrams, can be implemented by code. This code can be provided to a processor of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus to produce a machine, such that instructions executed via the processor of the computer or other programmable data processing apparatus create means for implementing the functions specified in the schematic flowcharts and / or schematic block diagrams for blocks or blocks.

[0036] Alternatively, code may be stored in a storage device that can instruct a computer, other programmable data processing device, or other device to function in a particular manner, causing the instructions stored in the storage device to produce an article of art, the article of art including instructions that implement the functions specified in blocks or blocks of schematic flowcharts and / or schematic block diagrams.

[0037] Code may also be loaded onto a computer, other programmable data processing apparatus or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer-implemented process, such that the code executing on the computer or other programmable apparatus provides a process for implementing the functions specified in blocks or blocks of flowcharts and / or block diagrams.

[0038] The schematic flowcharts and / or block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of apparatus, systems, methods, and program products according to various embodiments. In this regard, each block in the schematic flowcharts and / or block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions for implementing the specified logical function.

[0039] It should also be noted that in some alternative implementations, the functions annotated in the blocks may occur in a different order than those annotated in the figures. For example, depending on the functions involved, two blocks shown successively may be executed substantially simultaneously, or sometimes in reverse order. One or more blocks or portions thereof that are functionally, logically, or effectively equivalent to those in the illustrated figures are conceivable.

[0040] While various arrow and line types may be used in flowcharts and / or block diagrams, they are not intended to limit the scope of the corresponding embodiments. In practice, some arrows or other connectors may be used only to indicate the logical flow of the depicted embodiment. For example, an arrow may indicate a wait or monitoring period of unspecified duration between enumeration steps in a depicted embodiment. It should also be noted that each block in a block diagram and / or flowchart, and combinations of blocks in block diagrams and / or flowcharts, can be implemented by a system based on dedicated hardware, or a combination of dedicated hardware and code, performing the specified function or behavior.

[0041] The description of the elements in each figure can be referenced to the elements in the preceding figures. In all figures, similar numerals refer to similar elements, including alternative embodiments of similar elements.

[0042] In the first embodiment, the non-anchored carriers used for data transmission—that is, for PDSCH and PUSCH transmission—are indicated to the UE. Basically, there are two alternative ways to indicate non-anchored carriers to the UE. The first way is to first indicate all potential non-anchored carriers to the UE, and then indicate the actual non-anchored carriers used. For example, all potential non-anchored carriers can be indicated by SI (System Information), while the actual non-anchored carriers used can be indicated by RRC signaling. Alternatively, all potential non-anchored carriers can be indicated by RRC signaling, while the actual non-anchored carriers used can be indicated by DCI. The second way is to directly indicate the actual non-anchored carriers used to the UE. For example, the actual non-anchored carriers used can be indicated by RRC signaling.

[0043] In the first embodiment, each non-anchored carrier is associated with a candidate carrier configuration. The candidate carrier configuration may include at least one of the following parameters: frequency location, operating mode, NRS information, CRS information, and power offset to the anchored carrier.

[0044] For example, the carrier of NB-IoT occupies 180 kHz. Frequency positions can be the lowest and highest frequencies of the carrier, or the center frequency of the carrier (i.e., the intermediate frequency between the lowest and highest frequencies). For example, assuming a non-anchored carrier occupies frequencies from 6982.5 kHz to 7162.5 kHz, the frequency position of the non-anchored carrier can be represented as "lowest frequency 6982.5 kHz and highest frequency 7162.5 kHz" or "center frequency 7072.5 kHz". Frequency positions can also be represented as frequency indices, such as those defined in RAN4. For example, frequency index 0 can refer to a frequency range of 6982.5 kHz to 7162.5 kHz; frequency index 1 can refer to a frequency range of 6000 kHz to 6180 kHz.

[0045] NB-IoT supports three operating modes: Standalone, Guard Band, and In-Band. In In-Band mode, a physical resource block within the LTE carrier is used as the NB-IoT carrier. In Guard Band mode, a resource block used for the edge guard band of LTE is used as the NB-IoT carrier. In Standalone mode, a GSM band with 180kHz wide spectrum realignment is used as the NB-IoT carrier. The UE behaves differently in different operating modes. For example, a UE in In-Band mode should punch CRS resource elements for PDSCH resource mapping. Therefore, for non-anchored carrier PDSCH and PUSCH transmissions, the operating mode of the non-anchored carrier is preferably indicated to the UE.

[0046] The NRS (NB-IoT RS) is a reference signal used in NB-IoT. NRS information may include NRS frequency location information and NRS sequence information with the NB-IoT carrier. Both the NRS frequency location information and the NRS sequence information are determined by the "cell ID" of the NB-IoT carrier, even for non-anchored carriers. NRS information may optionally, but preferably, be included in the candidate carrier configuration. If NRS information is not included in the candidate carrier configuration, some restrictions should be placed on the UE's ability to assume the NRS frequency location and the NRS sequence to be the same as those of the anchored carrier.

[0047] CRS is a reference signal used in LTE. CRS information can include the CRS frequency location and CRS sequence information within the PRB. The CRS frequency location within the PRB is determined by the LTE cell ID, and the CRS sequence is determined by the LTE system-in-band CRS frequency location and the LTE cell ID. When LTE and NB-IoT are deployed in-band, the NB-IoT cell ID can be deployed the same as the LTE cell ID. If the NB-IoT cell ID is the same as the LTE cell ID, the LTE CRS can be used in conjunction with NRS to assist in channel estimation and measurement, which will improve channel estimation performance. CRS information is optionally, but preferably, included in the candidate carrier configuration.

[0048] As mentioned above, it is necessary to identify the operating mode when indicating NRS and CRS information. If the operating mode of the candidate carrier is not in-band, the CRS information is not included in the candidate carrier configuration.

[0049] Because the anchor carrier power is already indicated by higher-layer signaling, the power of the non-anchor carrier can be indicated as a power offset from the anchor carrier. This power offset from the anchor carrier can optionally be included in the candidate carrier configuration, as the UE can assume that the power of the non-anchor carrier is the same as the power of the anchor carrier.

[0050] According to a first implementation of the first embodiment, the potential non-anchored carrier is configured by the SI, for example, configured in SIB1. Additionally, the actual non-anchored carrier used is configured by RRC signaling.

[0051] SI is a broadcast message that can be received by all UEs in the cell, while RRC signaling can be UE-specific, that is, only received by a specific UE.

[0052] When configuring potential non-anchored carriers, each candidate carrier configuration can be associated with a frequency index. Accordingly, when RRC signaling configures the actual non-anchored carriers used, the frequency index can be used to indicate whether the corresponding candidate carrier is used by (other UEs). The frequency index can be implemented as a bitmap. For example, if SI configures 8 carriers, an 8-bit bitmap indicator can be used to indicate which carriers are used by the UE and which are not. Bit "0" can be used to indicate that the corresponding carrier is used by the UE, while "1" is used to indicate that the corresponding carrier is not used by any UE. For example, "01001111" can indicate that the first, third, and fourth corresponding carriers are used, but the second, fifth, sixth, seventh, and eighth corresponding carriers are not used. Figure 1 As shown, the SI configuration has eight unanchored carriers with frequency indices 1-8. RRC signaling can indicate a bitmap indicator "11100000" to a specific UE to indicate that carriers with indices 1-3 are unused carriers, i.e., unanchored carriers that can be used by the specific UE. These unanchored carriers with indices 1-3 can be used by the specific UE for PDSCH and / or PUSCH transmissions. According to the first embodiment, each unanchored carrier is indicated individually. Therefore, the unanchored carriers used by a specific UE can be consecutive or discontinuous.

[0053] The advantage of the first implementation is that the non-anchored carrier configuration is similar to the non-anchored carrier configuration of version 14.

[0054] In the second embodiment of the first embodiment, UE-specific RRC signaling directly configures the actual non-anchored carrier used for PDSCH and PUSCH transmissions. Still referring to... Figure 1 RRC signaling can indicate to a specific UE the non-anchored carriers with indices 1-3 used for PDSCH and PUSCH transmission. Each non-anchored carrier is indicated by its candidate carrier configuration. Similar to the first embodiment, according to the second embodiment, the non-anchored carriers for a specific UE can be continuous or discontinuous. According to the second embodiment, it is not necessary for the gNB to use SI to configure potential non-anchored carriers.

[0055] According to the first and second embodiments, each non-anchored carrier is indicated individually. Therefore, the indicated non-anchored carriers can be continuous or discontinuous. When the indicated non-anchored carriers are continuous, these continuous non-anchored carriers can be referred to as a carrier set.

[0056] According to the third embodiment, a carrier set of multiple consecutive unanchored carriers is indicated. Specifically, the SI configures the potential unanchored carriers. RRC signaling is used to indicate the first unanchored carrier (an example of a reference carrier) from the potential unanchored carriers (e.g., by its frequency index) of the carrier set, and further indicates the number of consecutive carriers included in the carrier set. Incidentally, the number of consecutive carriers may depend on the UR RF bandwidth capability. For example, if the UE Rf bandwidth capability is 600 kHz, the maximum number of consecutive carriers can be 3, because the bandwidth of 3 carriers is 540 kHz, which is less than 600 kHz.

[0057] Figure 2 The illustration shows a third implementation of the first embodiment. SI configures carriers with indices 1-3 as potential unanchored carriers. RRC signaling can indicate from the potential unanchored carriers 1-3 that a particular potential unanchored carrier (such as carrier #1) is the first unanchored carrier of the carrier set (referencing an example carrier), and further indicate that the number of carriers in the carrier set starting with the particular potential unanchored carrier (carrier #1) is 3. Therefore, carrier set #1 consisting of 3 carriers is configured, where the first carrier is carrier #1.

[0058] In the above description, the first non-anchored carrier of the carrier set is designated as the reference carrier of the carrier set. Alternatively, any non-anchored carrier in the carrier set can be designated as the reference carrier. For example, the last carrier in the carrier set, or the middle carrier in the carrier set if the carrier set consists of three carriers, can be designated as the reference carrier.

[0059] According to the third implementation of the first embodiment, the bandwidth (i.e., the number of non-anchored carriers) can be flexibly configured via RRC signaling for different UE capabilities.

[0060] Incidentally, the reference carrier of the carrier set and the consecutive number of carriers contained in the carrier set can be directly indicated by RRC signaling, rather than by SI indicating potential non-anchored carriers.

[0061] According to the fourth embodiment of the first embodiment, a carrier set of multiple consecutive non-anchored carriers is indicated. Unlike the third embodiment, in the fourth embodiment, the carrier set is directly configured by SI or RRC signaling.

[0062] like Figure 3 As illustrated, carrier sets are directly indicated by SI or RRC signaling. Each carrier set can be associated with a candidate carrier configuration. The number of non-anchored carriers included in a carrier set can be predetermined. For example, a carrier set can default to including 3 non-master carriers.

[0063] According to the first embodiment, the non-anchored carrier configuration is complex because each potential non-anchored carrier (or the carrier set in the fourth embodiment) has a candidate carrier configuration that includes at least one parameter. For example, the operating mode can be indicated individually for each potential non-anchored carrier. In the case of PDSCH transmission in in-band operating mode, it is always advantageous to use CRS for channel estimation. Therefore, for each potential non-anchored carrier in in-band operating mode, CRS information must be included in the non-anchored carrier configuration.

[0064] The UE is always able to identify the anchor carrier. In other words, the frequency position of the anchor carrier is derived by the UE after initial access. Therefore, it is advantageous to configure the frequency positions of potential non-anchor carriers by referencing the frequency position of the anchor carrier.

[0065] A second embodiment for indicating carrier frequency is described, wherein the frequency position of the anchor carrier is taken into account. It is sufficient to indicate the non-anchor carrier by indicating a frequency offset from the frequency position of the anchor carrier.

[0066] According to the first implementation of the second embodiment, only carriers adjacent to the anchor carrier can be configured as potential non-anchor carriers. The number of non-anchor carriers adjacent to both sides of the anchor carrier is indicated by RRC signaling.

[0067] Figure 4 The illustration shows an example of the first implementation of the second embodiment in in-band operation mode. Non-anchored carrier B is the lower adjacent carrier relative to the anchored carrier. Non-anchored carrier C is the upper adjacent carrier relative to the anchored carrier. Non-anchored carrier A is a consecutive carrier of adjacent carrier B. Both carriers A and B can be considered as adjacent non-anchored carriers on the lower side of the anchored carrier. RRC signaling indicates to the UE that the number of potential non-anchored carriers on the lower side of the anchored carrier is 2, and the number of potential non-anchored carriers on the upper side of the anchored carrier is 1. Under this condition, carriers A, B, C, and the anchored carrier form a carrier set with a bandwidth of 180 × 4 = 720 kHz.

[0068] By default, the number of potential non-anchored carriers below the anchored carrier and the number of potential non-anchored carriers above the anchored carrier are both set to 1. Figure 4 In this configuration, carriers B and C are the default potential non-anchored carriers. Under these conditions, carriers B and C, together with the anchored carrier, form a carrier set with a bandwidth of 540 kHz, where the center frequency of the carrier set remains the center frequency of the anchored carrier. In other words, there is no need to retune the center frequency for wider bandwidth transmission.

[0069] According to the first embodiment of the second embodiment, all potential or actually used non-anchored carriers are adjacent to the anchored carrier. It can be assumed that the channel quality of the non-anchored carriers is the same as that of the anchored carrier. No additional measurements are required for the non-anchored carriers. In the second embodiment, the frequency position of the non-anchored carrier is determined by its frequency offset from the anchored carrier. In the first embodiment of the second embodiment, the frequency offset is represented by the number of consecutive non-anchored carriers on both sides (below and above) of the anchored carrier.

[0070] Figure 4 An example is shown where the operating mode is in-band for the anchor carrier. When the operating mode is in the guard band for the anchor carrier, further configuration is necessary.

[0071] Figure 5 This describes an example of a guard band NB-IoT anchor carrier deployment. Guard band NB-IoT deployments may vary depending on the operator or vendor. The guard band, in particular... Figure 5 The detailed number of frequencies shown is for illustrative purposes only.

[0072] like Figure 5 As shown, for 10MHz and 20MHz LTE system bandwidths, the anchor carrier is potentially placed on the first PRB in the guard band, counting from the in-band edge. Considering the 100kHz channel grating requirement, only one potential anchor carrier is available on each side of the guard band.

[0073] The 100kHz channel grating requirement means that the center frequency of the anchor carrier should be a multiple of 100kHz. In guard band operation mode, the center frequency of the anchor carrier cannot be exactly a multiple of 100kHz. Instead, there may be an offset between the center frequency of the anchor carrier and the 100kHz channel grating. According to the NB-IoT standard, the maximum offset is 7.5kHz. In practice, the offset is either 2.5kHz or 7.5kHz.

[0074] For example, for a 10MHz LTE system bandwidth, there are two carriers in the guard band on each side of the in-band. The center frequencies are 4597.5kHz and 4777.5kHz or -4597.5kHz and -4777.5kHz to the LTE carrier center (e.g., assuming the LTE carrier center is 0Hz). Based on the center frequencies of the anchor carriers that meet the 100kHz channel grating requirements, and given a maximum offset of 7.5kHz, only carriers with center frequencies of 4597.5kHz and -4597.5kHz to the LTE carrier center can be used as potential anchor carriers. The other two carriers with center frequencies of 4777.5kHz and -4777.5kHz can be used as potential non-anchor carriers. Incidentally, in-band carriers can also be used as potential non-anchor carriers.

[0075] Similarly, for a 20MHz LTE system bandwidth, only carriers with center frequencies of 9097.5kHz and -9097.5kHz are eligible as potential anchor carriers. The other eight carriers in the guard band can be used as potential non-anchor carriers.

[0076] For 15MHz and 5MHz LTE system bandwidths, to meet the 100kHz channel grating requirement, three empty subcarriers (each with a 15kHz bandwidth) should be added as gaps between the in-band PRB grid and the guard band PRB grid. Only one potential anchor carrier is available on each side of the guard band. For the 15MHz LTE system bandwidth, the center frequencies of the available potential anchor carriers are 6892.5kHz and -6892.5kHz. For the 5MHz LTE system bandwidth, the center frequencies of the available potential anchor carriers are 2392.5kHz and -2392.5kHz. The other carriers in the guard band are potential non-anchor carriers. Note that for the 5MHz LTE system bandwidth, since the only carrier in any guard band is an anchor carrier, there are no potential non-anchor carriers in the guard band.

[0077] SI or RRC signaling can further indicate the EUTRA system bandwidth (e.g., 5MHz, 10MHz, 15MHz, or 20MHz).

[0078] If the EUTRA system bandwidth is 5MHz, and the frequency offset due to the 5MHz EUTRA system bandwidth is 1 PRB with a gap of 45kHz, then the frequency position of the non-anchored carriers (carriers A and D) to the anchored carrier is determined to be 180kHz + 45kHz = 225kHz. If the frequency offset is 2 PRBs, then the frequency position of the non-anchored carriers (carriers B and C) to the anchored carrier is determined to be 225kHz + 180kHz = 405kHz.

[0079] If the EUTRA system bandwidth is 15MHz, and if the frequency offset is 1PRB and the gap is 45kHz due to the 15MHz EUTRA system bandwidth, then the frequency position of the in-band non-anchored carriers (carriers B and C) to the anchored carrier is determined to be 180kHz + 45kHz = 225kHz. If the frequency offset is 1PRB and there is no gap, then the frequency position of the in-band non-anchored carriers (carriers A and D) to the anchored carrier is determined to be 180kHz.

[0080] If the EUTRA system bandwidth is 10MHz, and if the frequency offset is 1 and there is no gap, the frequency position of the non-anchored carrier to the anchored carrier in the in-band and guard band (carriers A, B, C and D) is determined to be 180KHz PRB.

[0081] If the EUTRA system bandwidth is 20MHz, and if the frequency offset is 1PRB and there is no gap, the frequency position of the in-band and guard band non-anchored carriers (carriers A, B, C, and D) to the anchored carrier is determined to be 180KHz.

[0082] Assuming the carrier set consists of 3 carriers (1 anchored carrier and 2 non-anchored carriers), the composition and bandwidth of the carrier set will vary depending on the EUTRA system bandwidth.

[0083] If the EUTRA system bandwidth is 5MHz, the carrier set can consist of an anchor carrier and two lower non-anchor carriers A and B, with a total bandwidth of 180KHz + 180KHz + 225KHz = 585KHz.

[0084] If the EUTRA system bandwidth is 15MHz, the carrier set can consist of an anchored carrier, an upper non-anchored carrier A, and a lower non-anchored carrier B, with a total bandwidth of 180KHz + 225KHz + 180KHz = 585KHz.

[0085] If the EUTRA system bandwidth is 10MHz, the carrier set can consist of an anchored carrier, an upper non-anchored carrier A, and a lower non-anchored carrier B, with a total bandwidth of 180KHz + 180KHz + 180KHz = 540KHz.

[0086] If the EUTRA system bandwidth is 20MHz, then the carrier set can consist of an anchored carrier, an upper non-anchored carrier A, and a lower non-anchored carrier B, with a total bandwidth of 180KHz + 180KHz + 180KHz = 540KHz.

[0087] According to a second embodiment of the second embodiment, the potential non-anchored carrier need not be a carrier adjacent to the anchored carrier. A carrier set consisting of multiple consecutive non-anchored carriers is indicated. Specifically, the frequency offset of the first non-anchored carrier in the carrier set to the anchored carrier can be indicated in PRBs using SI or RRC. Furthermore, the number of consecutive carriers included in the carrier set can also be further indicated.

[0088] Figure 6The illustration shows an example of a second implementation of the second embodiment. RRC signaling can indicate, in PRB units, the frequency offset of the non-anchored carrier 1 to the anchored carrier as N1 (e.g., N1 = -10), and the number of consecutive carriers as 3 (i.e., carrier set 1 consists of 3 consecutive non-anchored carriers). Incidentally, the number of consecutive carriers can be preset to a default value, such as 3. Therefore, carrier set 1, consisting of three consecutive carriers of the first carrier with an offset of -10 to the anchored carrier, is used for PDSCH and / or PUSCH transmission. To reduce the overhead of frequency offset indication, N1 can be defined as N1 = N0 * K, where K is the number of carriers in the carrier set, and N0 is a positive or negative integer satisfying that "the absolute value N0 * K is less than half the LTE bandwidth".

[0089] In the second embodiment of the second example, if the PCID of the LTE system is the same as the PCID of the anchor carrier of NB-IoT, then the CRS information of the carrier set consisting of non-anchor carriers can be derived from the cell ID of NB-IoT and the frequency location of the anchor carrier within the LTE system. For example... Figure 6 As shown, the anchor carrier is located within the LTE carrier and has a reference n. PRB = -16 at the PRB. The non-anchored carrier to the left of the anchored carrier is located within the LTE carrier with reference n. PRB = -17 at the PRB. The non-anchored carrier to the right of the anchored carrier is located within the LTE carrier and has a reference n. PRB At the PRB with a frequency offset of N1 = -15. Similarly, a non-anchored carrier 1 with a frequency offset of N1 = -10 is located within an LTE carrier with a reference n. PRB = -26 at the PRB. Therefore, the CRS information of the non-anchored carrier 1 is within the LTE carrier with reference n. PRB CRS information for PRB of -26.

[0090] Figure 6 The diagram also shows that the offset of carrier 2 (N2) is 3 (in PRBs), and the number of consecutive carriers contained in carrier set 2 is also 3. Needless to say, the CRS information of the non-anchored carrier 2 wave is within the LTE carrier with a reference n. PRB CRS information for PRB of -13.

[0091] In a second embodiment of the second embodiment, in order to ensure that the carrier set consisting of potential non-anchored carriers does not overlap, the minimum interval between adjacent offsets should be equal to or greater than the number of consecutive carriers contained in the carrier set.

[0092] Incidentally, in the second embodiment of the second embodiment, the first carrier of the carrier set is designated as the reference carrier. Alternatively, any carrier in the carrier set can be designated as the reference carrier.

[0093] According to the third implementation of the second embodiment, the offset of the carrier set of multiple consecutive non-anchored carriers is directly indicated by SI or RRC signaling in units of PRB.

[0094] By default, the carrier set consists of three adjacent carriers. The center frequency of the carrier set is the center frequency of the middle carrier among the three adjacent carriers. For standalone and in-band operation modes, even for some EUTRA bandwidths in guard band operation mode, the frequency offset of the non-anchored carrier from the anchored carrier is N*180kHz, where N is an integer greater than or equal to 1.

[0095] Figure 7 An example of a third embodiment of the second embodiment is illustrated. Figure 7 In , carrier set 1 and carrier set 2 are the same as Figure 6 The components shown are the same. However, Figure 7 The center frequency of carrier set 1 and in Figure 6 The second carrier contained in carrier set 1 is the same. Therefore, the offset from carrier set 1 to the anchor carrier is N1 in PRB units (e.g., N1 = -9). Similarly, the offset from carrier set 2 to the anchor carrier is N2 in PRB units (e.g., N2 = 4).

[0096] exist Figure 6 and Figure 7 In the diagram, all carriers are shown as adjacent to each other. In the case of anchored and / or non-anchored carriers in the guard band, there may be three empty subcarriers (total bandwidth 45 kHz) between the last in-band carrier and the first guard band carrier (see, for example, in...). Figure 5 (Carrier A and anchor carrier in the 5MHz case). Because this 45kHz gap is predetermined (exists only in the 5MHz or 15MHz EUTRA system bandwidth), the UE can identify the 45kHz gap if it is indicated as part of the EUTRA system bandwidth. In summary, the frequency location is determined by at least one of the following: frequency offset, anchor carrier frequency, number of carriers in the carrier set, anchor carrier operating mode, and EUTRA system bandwidth.

[0097] In the second embodiment, a frequency offset to the anchor carrier frequency is used to indicate the non-anchor carrier. Therefore, the frequency offset is included in the candidate carrier configuration. The frequency position is determined at least based on the frequency offset. As described above, when the anchor carrier's operating mode is a guard band, the frequency position is calculated given the EUTRA system bandwidth.

[0098] Figure 8This is a schematic flowchart illustrating an embodiment of a method 800 for indicating a carrier. In some embodiments, method 800 is performed by a device such as a base station unit. In some embodiments, method 800 may be performed by a processor that executes program code—e.g., a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0099] Method 800 may include 802 transmitting candidate carrier configuration, wherein the candidate carrier configuration includes at least one of the following: frequency position, frequency offset, operating mode, NRS information, CRS information, power offset, and EUTRA system bandwidth of at least one candidate carrier.

[0100] Figure 9 This is a schematic flowchart illustrating yet another embodiment of a method 900 for indicating a carrier wave. In some embodiments, method 900 is performed by a device such as a remote unit. In some embodiments, method 900 may be performed by a processor that executes program code—e.g., a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0101] Method 900 may include 902 receiving candidate carrier configuration, wherein the candidate carrier configuration includes at least one of the following: frequency position, frequency offset, operating mode, NRS information, CRS information, power offset, and EUTRA system bandwidth of at least one candidate carrier.

[0102] Figure 10 This is a schematic block diagram illustrating an apparatus according to one embodiment.

[0103] refer to Figure 10 The UE (i.e., remote unit) includes a processor, memory, and transceiver. The processor is implemented in... Figure 9 The functions, processes, and / or methods proposed in [the document]. The gNB (i.e., base station unit) includes a processor, memory, and transceiver. The processor is implemented in [the document]. Figure 8 The functions, processes, and / or methods proposed herein. The layers of the radio interface protocol can be implemented by a processor. A memory is connected to the processor to store information used to drive the processor. A transceiver is connected to the processor to transmit and / or receive radio signals. Needless to say, a transceiver can be implemented as a transmitter that transmits radio signals and a receiver that receives radio signals.

[0104] Memory can be located inside or outside the processor and connected to the processor via various known devices.

[0105] In the above embodiments, components and features of the embodiments are combined in a predetermined form. Unless otherwise expressly stated, each component or feature should be considered optional. Each component or feature may be implemented without being associated with other components or features. Additionally, embodiments may be configured by associating some components and / or features. The order of operations described in the embodiments may be changed. Some components or features of any embodiment may be included in another embodiment or replaced with components and features corresponding to another embodiment. It is apparent that claims not expressly recited in the claims are combined to form embodiments or included in new claims.

[0106] The embodiments can be implemented by hardware, firmware, software, or a combination thereof. In the case of hardware implementation, the exemplary embodiments described herein can be implemented by using one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, etc., according to the hardware implementation method.

[0107] The embodiments may be practiced in other specific forms. The described embodiments are to be considered in all respects as illustrative only and not restrictive. Therefore, the scope of the invention is indicated by the appended claims, and not by the foregoing description. All variations within the equivalent meaning and scope of the claims are to be included within their scope.

Claims

1. A method performed by a base station, the method comprising: Transmit candidate carrier configuration, the candidate carrier configuration indicating at least one of the following: frequency position, frequency offset, operating mode, narrowband reference signal (NRS) information, cell-specific reference signal (CRS) information, power offset, and Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (EUTRA) system bandwidth; and Send an indication of whether the candidate carriers configured based on the candidate carriers can be used for data transmission. Each candidate carrier is associated with a frequency index that is combined with its corresponding frequency position, and the indication includes a multi-bit bitmap indicator that corresponds one-to-one with the frequency index, where each bit in the bitmap indicator corresponds to a frequency index, to indicate the availability status of multiple candidate carriers in batches.

2. The method according to claim 1, wherein, The candidate carrier is the reference carrier of the carrier set.

3. The method according to claim 2, further comprising: The number of carriers in the carrier set to be transmitted.

4. The method according to claim 1, wherein, The frequency offset is a relative frequency offset with respect to the anchor carrier frequency.

5. The method according to claim 1, wherein, The frequency offset is measured in units of basic resource blocks.

6. The method according to claim 1, wherein, The frequency position is determined by the frequency offset, the frequency of the anchor carrier, the number of carriers in the carrier set, the operating mode of the anchor carrier, the EUTRA system bandwidth, or some combination thereof.

7. The method according to claim 6, wherein, The candidate carrier is a carrier adjacent to the anchor carrier.

8. The method of claim 7, further comprising: The number of carriers adjacent to the anchor carrier on each side are transmitted.

9. The method according to claim 7, wherein, The number of carriers adjacent to the anchor carrier on each side is 1 or 2.

10. A base station, comprising: At least one memory; as well as At least one processor, coupled to the at least one memory and configured such that the base station: Send candidate carrier configuration, the candidate carrier configuration indicating at least one of the following: frequency position, frequency offset, operating mode, NRS information, CRS information, power offset, and EUTRA system bandwidth of at least one candidate carrier; as well as Send an indication of whether the candidate carriers configured based on the candidate carriers can be used for data transmission. Each candidate carrier is associated with a frequency index that is combined with its corresponding frequency position, and the indication includes a multi-bit bitmap indicator that corresponds one-to-one with the frequency index, where each bit in the bitmap indicator corresponds to a frequency index, to indicate the availability status of multiple candidate carriers in batches.

11. The base station according to claim 10, wherein, The candidate carrier is the reference carrier of the carrier set.

12. The base station according to claim 11, wherein, The at least one processor is further configured to cause the base station to transmit the number of carriers in the carrier set.

13. The base station according to claim 10, wherein, The frequency offset is a relative frequency offset with respect to the anchor carrier frequency.

14. The base station according to claim 10, wherein, The frequency offset is measured in units of basic resource blocks.

15. The base station according to claim 10, wherein, The frequency position is determined by the frequency offset, the frequency of the anchor carrier, the number of carriers in the carrier set, the operating mode of the anchor carrier, the EUTRA system bandwidth, or some combination thereof.

16. The base station according to claim 15, wherein, The candidate carrier is a carrier adjacent to the anchor carrier.

17. The base station according to claim 16, wherein, The at least one processor is further configured to cause the base station to transmit a number of carriers adjacent to the anchor carrier on each side.

18. The base station according to claim 16, wherein, The number of carriers adjacent to the anchor carrier on each side is 1 or 2.

19. A method performed by a user equipment (UE), the method comprising: Receive candidate carrier configuration, the candidate carrier configuration indicating at least one of the following: frequency position, frequency offset, operating mode, NRS information, CRS information, power offset, and EUTRA system bandwidth of at least one candidate carrier; as well as Receive an indication of whether the candidate carriers configured based on the candidate carriers can be used for data transmission. Each candidate carrier is associated with a frequency index that is combined with its corresponding frequency position, and the indication includes a multi-bit bitmap indicator that corresponds one-to-one with the frequency index, where each bit in the bitmap indicator corresponds to a frequency index, to indicate the availability status of multiple candidate carriers in batches.

20. The method according to claim 19, wherein, The candidate carrier is the reference carrier of the carrier set.

21. The method of claim 20, further comprising: The number of carriers received from the carrier set.

22. The method according to claim 19, wherein, The frequency offset is a relative frequency offset with respect to the anchor carrier frequency.

23. The method according to claim 19, wherein, The frequency offset is measured in units of basic resource blocks.

24. The method according to claim 19, wherein, The frequency position is determined by the frequency offset, the frequency of the anchor carrier, the number of carriers in the carrier set, the operating mode of the anchor carrier, the EUTRA system bandwidth, or some combination thereof.

25. The method according to claim 24, wherein, The candidate carrier is a carrier adjacent to the anchor carrier.

26. The method of claim 25, further comprising: The number of carriers received adjacent to the anchored carrier on each side.

27. The method according to claim 25, wherein, The number of carriers adjacent to the anchor carrier on each side is 1 or 2.

28. A user equipment (UE), comprising: At least one memory; as well as At least one processor, coupled to the at least one memory and configured such that the UE: Receive candidate carrier configuration, the candidate carrier configuration indicating at least one of the following: frequency position, frequency offset, operating mode, NRS information, CRS information, power offset, and EUTRA system bandwidth of at least one candidate carrier; as well as Receive an indication of whether the candidate carriers configured based on the candidate carriers can be used for data transmission. Each candidate carrier is associated with a frequency index that is combined with its corresponding frequency position, and the indication includes a multi-bit bitmap indicator that corresponds one-to-one with the frequency index, where each bit in the bitmap indicator corresponds to a frequency index, to indicate the availability status of multiple candidate carriers in batches.

29. The UE according to claim 28, wherein, The candidate carrier is the reference carrier of the carrier set.

30. The UE according to claim 29, wherein, The at least one processor is further configured to cause the UE to receive a number of carriers in the carrier set.

31. The UE according to claim 28, wherein, The frequency offset is a relative frequency offset with respect to the anchor carrier frequency.

32. The UE according to claim 28, wherein, The frequency offset is measured in units of basic resource blocks.

33. The UE according to claim 28, wherein, The frequency position is determined by the frequency offset, the frequency of the anchor carrier, the number of carriers in the carrier set, the operating mode of the anchor carrier, the EUTRA system bandwidth, or some combination thereof.

34. The UE according to claim 33, wherein, The candidate carrier is a carrier adjacent to the anchor carrier.

35. The UE according to claim 34, wherein, The receiver further receives the number of carriers adjacent to the anchor carrier on each side.

36. The UE according to claim 34, wherein, The number of carriers adjacent to the anchor carrier on each side is 1 or 2.

Images