A guard band indication method and device

Abstract

An embodiment of the present application discloses a method for indicating a guardband in an unlicensed spectrum, characterized in that it includes: a network device generates one or any combination of the following four types of information in the unlicensed spectrum: an indication of configured bandwidth information, an indication of available bandwidth information, an indication of unavailable bandwidth information, or an indication of guardband information; the network device sends one or any combination of the four types of information generated above; wherein one or any combination of the four types of information is used to determine a guardband based on a listen-before-talk (LBT) result.

Description

Technical Field

[0001] The present application relates to the field of wireless communication technology, and in particular to a guard band indication method, related equipment and system. Background Art

[0002] The rapid development of wireless communication technology has led to an increasing shortage of spectrum resources, which has promoted the exploration of unlicensed frequency bands. For unlicensed frequency bands, broadband transmission greater than 20MHz is supported. In addition, communication systems deployed on unlicensed spectrum usually use or share wireless resources in a competitive manner. Generally, before sending a signal, the site will first listen to whether the unlicensed spectrum is idle. For example, the busy or idle state is judged by the size of the received power on the unlicensed spectrum. If the received power is less than a certain threshold, the unlicensed spectrum is considered to be idle, and the signal can be sent on the unlicensed spectrum, otherwise the signal is not sent. This mechanism of listening before sending is called Listen Before Talk (LBT for short). Due to the uncertainty of the results of LBT, for a certain broadband carrier, there may be narrowband interference on part of the bandwidth, that is, only part of the bandwidth is idle, so the device can only transmit on the idle part of the bandwidth ( Figure 1 The transmission is performed on the medium gray subband. Figure 1 In the blank sub-band, the transmission of other devices forms narrowband interference. There is a potential signal leakage and mutual interference risk between the device and the narrowband interference device in the broadband. Summary of the invention

[0003] The technical problem to be solved by the present application is to reduce channel interference on unlicensed spectrum, such as narrowband interference.

[0004] On the one hand, a method for indicating a guardband in an unlicensed spectrum is provided, comprising: a network device generates one or any combination of the following four types of information in the unlicensed spectrum: an indication of configured bandwidth information, an indication of available bandwidth information, an indication of unavailable bandwidth information, or an indication of guardband information; the network device sends one or any combination of the four types of information generated above; wherein the one or any combination of the four types of information is used to determine a guardband based on a listen-before-talk (LBT) result. Furthermore, data transmission may also be performed within the available bandwidth in the bandwidth and within the actual resource location range outside the guardband.

[0005] In another aspect, a method for determining a guardband in an unlicensed spectrum includes: a terminal receives one or any combination of the following four types of information in the unlicensed spectrum: an indication of configured bandwidth information, an indication of available bandwidth information, an indication of unavailable bandwidth information, or an indication of guardband information; the terminal determines a guardband based on a listen-before-talk (LBT) result according to one or any combination of the four types of information. Furthermore, data reception may also be performed within the available bandwidth in the bandwidth and within the actual resource location range outside the guardband.

[0006] Optionally, one or more of the indication of the configured bandwidth information, the indication of the available bandwidth information, the indication of the unavailable bandwidth information or the guardband information are carried in a system message or RRC or DCI.

[0007] In addition, the standard may specify the size and position of the available bandwidth or the unavailable bandwidth based on the result of the listen-before-talk LBT, or the size and position of the available bandwidth or the unavailable bandwidth guardband, and predefine the resources corresponding to different values ​​of the indication of the configured bandwidth information, the indication of the available bandwidth information, the indication of the unavailable bandwidth information, or the indication of the guardband information. Through the above definition, the complexity of the related indication or indication can be reduced to a certain extent, thereby saving the overhead of communication resources.

[0008] In other aspects, the present application also provides devices, computer-readable storage media, etc. that can execute the aforementioned methods.

[0009] By implementing the embodiments of the present application, for the use of unlicensed frequency bands, the flexibility of uplink resource scheduling can be improved on the basis of meeting the OCB requirements of ESTI. Furthermore, resource utilization can be improved. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the background technology, the drawings required for use in the embodiments of the present application or the background technology will be described below.

[0011] Figure 1 It is a schematic diagram of an existing resource allocation method involved in this application;

[0012] Figure 2 It is a schematic diagram of the architecture of a wireless communication system involved in the present application;

[0013] Figure 3 is a schematic diagram of the hardware architecture of a terminal provided by an embodiment of the present application;

[0014] Figure 4 is a schematic diagram of the hardware architecture of a base station provided by an embodiment of the present application;

[0015] Figure 5 is a schematic diagram of the architecture of a wireless communication system provided by an embodiment of the present application;

[0016] Figure 6 It is a simple schematic diagram of a guardband position involved in this application;

[0017] Figure 7-12 They are schematic diagrams of resources with a bandwidth of 80 MHz provided by an embodiment of the present application;

[0018] Fig.13 is a schematic diagram of an in-band guard band provided by an embodiment of the present application;

[0019] Fig.14 is a schematic diagram of an in-band guard band provided by another embodiment of the present application;

[0020] Fig.15 is a schematic diagram of an inner guard band provided by another embodiment of the present application;

[0021] Fig.16 This is a schematic diagram of an in-band guard band provided by another embodiment of the present application;. DETAILED DESCRIPTION

[0022] The terms used in the implementation section of this application are only used to explain the specific embodiments of this application and are not intended to limit this application.

[0023] For the convenience of subsequent description, the abbreviations and key terms in this article can be referred to in the following table:

[0024]

[0025]

[0026]

[0027] In order to facilitate understanding of the implementation of the present application, the wireless communication system involved in the embodiments of the present application is first introduced.

[0028] refer to Figure 2 , Figure 2 2 shows a wireless communication system 200 involved in the present application. The wireless communication system 200 can operate in a licensed frequency band or an unlicensed frequency band. It can be understood that the use of the unlicensed frequency band can improve the system capacity of the wireless communication system 200. Figure 2 As shown, the wireless communication system 200 includes: one or more network devices 201, such as base stations, NodeBs, eNodeBs or WLAN access points, wireless relay nodes, wireless backhaul nodes, one or more terminals 203, and a core network 215. Among them:

[0029] The network device 201 may be used to communicate with the terminal 203 under the control of a base station controller (not shown). In some embodiments, the base station controller may be a part of the core network 230 or may be integrated into the base station 201.

[0030] The network device 201 may be used to transmit control information or user data to a core network 215 via a blackhaul interface (eg, S1 interface) 213 .

[0031] The network device 201 can wirelessly communicate with the terminal 203 through one or more base station antennas. Each base station 201 can provide communication coverage for its corresponding coverage area 207. The coverage area 207 corresponding to the access point can be divided into multiple sectors, where one sector corresponds to a part of the coverage area (not shown).

[0032] The network device 201 and the base station 201 may also communicate with each other directly or indirectly via a backhaul link 211. Here, the backhaul link 211 may be a wired communication connection or a wireless communication connection.

[0033] The network device 201 may also be a wireless controller in a cloud radio access network (CRAN) scenario. The network device 201 may also be a network device in a 5G network or a network device in a future evolution network; it may also be a wearable device or an in-vehicle device, etc. The network device 201 may also be a small station, a transmission reference point (TRP), etc. Of course, the application is not limited to this.

[0034] In some embodiments of the present application, the network device 201 may include: a base transceiver station, a wireless transceiver, a basic service set (BSS), an extended service set (ESS), NodeB, eNodeB, etc. The wireless communication system 200 may include several different types of base stations 201, such as a macro base station, a micro base station, etc. The base station 201 may apply different wireless technologies, such as a cell wireless access technology or a WLAN wireless access technology.

[0035] The terminal 203 can be distributed throughout the wireless communication system 200, and can be stationary or mobile. It can be deployed on land, including indoors or outdoors, handheld, wearable or vehicle-mounted; it can also be deployed on the water surface (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons and satellites, etc.). The terminal device can be a mobile phone, a tablet computer (Pad), a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home, etc. The embodiments of the present application do not limit the application scenarios. The terminal device may also be sometimes referred to as user equipment (UE), access terminal equipment, UE unit, UE station, mobile station, mobile station, remote station, remote terminal equipment, mobile device, UE terminal equipment, terminal equipment, wireless communication equipment, UE agent or UE device, etc. In some embodiments of the present application, the terminal 203 may include: a mobile device, a mobile station, a mobile unit, a wireless unit, a remote unit, a user agent, a mobile client, etc.

[0036] In an embodiment of the present application, the wireless communication system 200 may be an LTE communication system capable of operating in an unlicensed frequency band, such as LTE-U, or may be a 5G communication system capable of operating in an unlicensed frequency band and future new air interfaces and other communication systems. The wireless communication system 200 may adopt a licensed assisted access (LAA) scheme to handle terminal access in an unlicensed frequency band. In the LAA scheme, the primary cell (Primary Cell) operates in an authorized frequency band to transmit critical messages and services that require quality of service assurance; the secondary cell (Secondary Cell) operates in an unlicensed frequency band to achieve improved data plane performance.

[0037] In the embodiment of the present application, the wireless communication system 200 can support multi-carrier (waveform signals of different frequencies) operation. A multi-carrier transmitter can transmit modulated signals on multiple carriers simultaneously. For example, each communication connection 205 can carry multi-carrier signals modulated using different wireless technologies. Each modulated signal can be sent on a different carrier and can also carry control information (such as reference signals, control channels, etc.), overhead information, data, etc.

[0038] In addition, the wireless communication system 200 may also include a WiFi network. In order to achieve harmonious coexistence between the operator network and the WiFi network (operating in the unlicensed spectrum), the wireless communication system 200 may adopt a Listen before Talk (LBT) mechanism. For example, in the wireless communication system 200, some terminals 203 may use unlicensed spectrum resources by connecting to the WiFi access point 209 via the WiFi communication connection 217, and some terminals 203 may also use unlicensed spectrum resources by connecting to the base station 201 via the mobile communication connection 205. When using an unlicensed frequency band, any device must first listen to see if the frequency band is occupied. If the frequency band is not busy, it can occupy and transmit data.

[0039] refer to Figure 3 , Figure 3 FIG. 3 shows a terminal 300 provided in some embodiments of the present application. Figure 3 As shown, the terminal 300 may include: an input and output module (including an audio input and output module 318, a key input module 316, and a display 320, etc.), a user interface 302, one or more terminal processors 304, a transmitter 306, a receiver 308, a coupler 310, an antenna 314, and a memory 312. These components may be connected via a bus or other means. Figure 3 Take bus connection as an example.

[0040] The communication interface 301 can be used for the terminal 300 to communicate with other communication devices, such as a base station. Figure 4 The base station 400 shown. Specifically, the communication interface 301 may include: a global system for mobile communication (GlobalSystem for Mobile Communication, GSM) (2G) communication interface, a wideband code division multiple access (Wideband Code Division Multiple Access, WCDMA) (3G) communication interface, and a long-term evolution (Long Term Evolution, LTE) (4G) communication interface, etc. One or more of the above, can also be a communication interface of 4.5G, 5G or a future new air interface. Not limited to a wireless communication interface, the terminal 300 can also be configured with a wired communication interface 301, such as a local access network (Local Access Network, LAN) interface.

[0041] The antenna 314 can be used to convert electromagnetic energy in the transmission line into electromagnetic waves in free space, or convert electromagnetic waves in free space into electromagnetic energy in the transmission line. The coupler 310 is used to divide the mobile communication signal received by the antenna 314 into multiple paths and distribute them to multiple receivers 308.

[0042] The transmitter 306 may be used to perform transmission processing on the signal output by the terminal processor 304, for example, modulating the signal into a signal in an authorized frequency band, or modulating the signal into a signal in an unauthorized frequency band. In some embodiments of the present application, the transmitter 206 may include an unauthorized spectrum transmitter 3061 and an authorized spectrum transmitter 3063. The unauthorized spectrum transmitter 3061 may support the terminal 300 to transmit signals on one or more unauthorized spectrums, and the authorized spectrum transmitter 3063 may support the terminal 300 to transmit signals on one or more authorized spectrums.

[0043] The receiver 308 may be used to receive and process the mobile communication signal received by the antenna 314. For example, the receiver 308 may demodulate the received signal modulated on the unlicensed frequency band, and may also demodulate the received signal modulated on the licensed frequency band. In some embodiments of the present application, the receiver 308 may include an unlicensed spectrum receiver 3081 and an authorized spectrum receiver 3083. The unlicensed spectrum receiver 3081 may support the terminal 300 to receive the signal modulated on the unlicensed spectrum, and the authorized spectrum receiver 3083 may support the terminal 300 to receive the signal modulated on the authorized spectrum.

[0044] In some embodiments of the present application, the transmitter 306 and the receiver 308 can be regarded as a wireless modem. In the terminal 300, the number of the transmitter 306 and the number of the receiver 308 can be one or more.

[0045] Apart from Figure 3 In addition to the transmitter 306 and the receiver 308 shown, the terminal 300 may also include other communication components, such as a GPS module, a Bluetooth module, a wireless high-fidelity (Wireless Fidelity, Wi-Fi) module, etc. Not limited to the wireless communication signals described above, the terminal 300 may also support other wireless communication signals, such as satellite signals, shortwave signals, etc. Not limited to wireless communication, the terminal 300 may also be configured with a wired network interface (such as a LAN interface) to support wired communication.

[0046] The input and output modules can be used to realize the interaction between the terminal 300 and the user or the external environment, and can mainly include an audio input and output module 318, a key input module 316, and a display 320. Specifically, the input and output modules can also include: a camera, a touch screen, and a sensor. Among them, the input and output modules communicate with the terminal processor 304 through the user interface 302.

[0047] The memory 312 is coupled to the terminal processor 304 and is used to store various software programs and or multiple groups of instructions. Specifically, the memory 312 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more disk storage devices, flash memory devices or other non-volatile solid-state storage devices. The memory 312 can store an operating system (hereinafter referred to as the system), such as an embedded operating system such as ANDROID, IOS, WINDOWS, or LINUX. The memory 312 can also store a network communication program, which can be used to communicate with one or more additional devices, one or more terminal devices, and one or more network devices. The memory 312 can also store a user interface program, which can display the content of the application program vividly through a graphical operation interface, and receive user control operations on the application program through input controls such as menus, dialog boxes, and buttons.

[0048] In some embodiments of the present application, the memory 312 may be used to store an implementation program of the resource allocation method provided by one or more embodiments of the present application on the terminal 300 side. For the implementation of the resource allocation method provided by one or more embodiments of the present application, please refer to the subsequent embodiments.

[0049] The terminal processor 304 can be used to read and execute computer-readable instructions. Specifically, the terminal processor 304 can be used to call a program stored in the memory 312, such as an implementation program of the resource allocation method provided in one or more embodiments of the present application on the terminal 300 side, and execute the instructions contained in the program.

[0050] It is understandable that the terminal 300 may be Figure 2 The terminal 203 in the wireless communication system 200 shown may be implemented as a mobile device, a mobile station, a mobile unit, a wireless unit, a remote unit, a user agent, a mobile client, and the like.

[0051] Need to explain, Figure 3 The terminal 300 shown is only one implementation of the embodiment of the present application. In actual applications, the terminal 300 may also include more or fewer components, which is not limited here.

[0052] refer to Figure 4 , Figure 4 4 shows a base station 400 provided in some embodiments of the present application. Figure 4 As shown, the base station 400 may include: a communication interface 403, one or more base station processors 401, a transmitter 407, a receiver 409, a coupler 411, an antenna 413 and a memory 405. These components may be connected via a bus or other means. Figure 4 Take bus connection as an example.

[0053] The communication interface 403 can be used for the base station 400 to communicate with other communication devices, such as terminal devices or other base stations. Specifically, the terminal device can be Figure 3 The terminal 300 shown. Specifically, the communication interface 403 may include: one or more of the global system for mobile communications (GSM) (2G) communication interface, wideband code division multiple access (WCDMA) (3G) communication interface, and long-term evolution (LTE) (4G) communication interface, etc., and may also be a communication interface of 4.5G, 5G or future new air interfaces. Not limited to wireless communication interfaces, the base station 400 may also be configured with a wired communication interface 403 to support wired communication, for example, the backhaul link between a base station 400 and other base stations 400 may be a wired communication connection.

[0054] The antenna 413 can be used to convert electromagnetic energy in the transmission line into electromagnetic waves in free space, or convert electromagnetic waves in free space into electromagnetic energy in the transmission line. The coupler 411 can be used to divide the mobile communication signal into multiple paths and distribute them to multiple receivers 409.

[0055] The transmitter 407 may be used to perform transmission processing on the signal output by the base station processor 401, for example, modulating the signal into a signal in an authorized frequency band, or modulating the signal into a signal in an unauthorized frequency band. In some embodiments of the present application, the transmitter 407 may include an unauthorized spectrum transmitter 4071 and an authorized spectrum transmitter 4073. The unauthorized spectrum transmitter 4071 may support the base station 400 to transmit signals on one or more unauthorized spectrums, and the authorized spectrum transmitter 4073 may support the base station 400 to transmit signals on one or more authorized spectrums.

[0056] The receiver 409 may be used to receive and process the mobile communication signal received by the antenna 413. For example, the receiver 409 may demodulate the received signal modulated on the unlicensed frequency band, and may also demodulate the received signal modulated on the licensed frequency band. In some embodiments of the present application, the receiver 409 may include an unlicensed spectrum receiver 4091 and an authorized spectrum receiver 4093. The unlicensed spectrum receiver 4091 may support the base station 400 to receive the signal modulated on the unlicensed spectrum, and the authorized spectrum receiver 4093 may support the base station 400 to receive the signal modulated on the authorized spectrum.

[0057] In some embodiments of the present application, the transmitter 407 and the receiver 409 can be regarded as a wireless modem. In the base station 400, the number of the transmitter 407 and the number of the receiver 409 can be one or more.

[0058] The memory 405 is coupled to the base station processor 401 and is used to store various software programs and or multiple groups of instructions. Specifically, the memory 405 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more disk storage devices, flash memory devices or other non-volatile solid-state storage devices. The memory 405 can store an operating system (hereinafter referred to as system), such as uCOS, VxWorks, RTLinux and other embedded operating systems. The memory 405 can also store a network communication program, which can be used to communicate with one or more additional devices, one or more terminal devices, and one or more network devices.

[0059] The base station processor 401 can be used to manage wireless channels, establish and remove calls and communication links, and control the handover of user equipment in the control area. Specifically, the base station processor 401 may include: an administration module or a communication module (AM or CM) (a center for voice exchange and information exchange), a basic module (BM) (for completing call processing, signaling processing, wireless resource management, wireless link management and circuit maintenance functions), a transcoder and submultiplexer (TCSM) (for completing multiplexing, demultiplexing and code conversion functions), and the like.

[0060] In the embodiment of the present application, the base station processor 401 can be used to read and execute computer-readable instructions. Specifically, the base station processor 401 can be used to call a program stored in the memory 405, such as an implementation program of the resource allocation method provided in one or more embodiments of the present application on the base station 400 side, and execute the instructions contained in the program.

[0061] It is understandable that the base station 400 may be Figure 2 The base station 201 in the wireless communication system 200 shown can be implemented as a base transceiver station, a wireless transceiver, a basic service set (BSS), an extended service set (ESS), NodeB, eNodeB, etc. The base station 400 can be implemented as several different types of base stations, such as a macro base station, a micro base station, etc. The base station 400 can apply different wireless technologies, such as a cell wireless access technology, or a WLAN wireless access technology.

[0062] Need to explain, Figure 4 The base station 400 shown is only one implementation of the embodiment of the present application. In actual applications, the base station 400 may also include more or fewer components, which is not limited here.

[0063] The present invention can be applied to the aforementioned 5G NR system, and the present invention can also be applied to other communication systems, in which one entity preconfigures or sends guardband indication information, another entity presets a value or receives the indication information, and determines the available transmission bandwidth within the broadband based on the indication information.

[0064] like Figure 5As shown, the base station and UE1 to UE6 form a communication system. In this communication system, UE1 to UE6 can send uplink data to the base station, and the base station needs to receive the uplink data sent by UE1 to UE6 and give it to UE1 to UE6. In addition, UE4 to UE6 can also form a communication system. In this communication system, the BS can send downlink information to UE1, UE2, UE5, etc.; UE5 can also send downlink information to UE4 and UE6.

[0065] In one embodiment of the present invention, a method for guardband indication is provided. The base station indicates the guardband configuration in different bandwidth scenarios through radio resource control RRC signaling. For a certain broadband carrier / channel / BWP, different available bandwidth scenarios correspond to different results of LBT, and different guardbands are configured for the different available bandwidth scenarios. It can be understood that available bandwidth and unavailable bandwidth are relative concepts, and the configuration of guardband can also be configured based on unavailable bandwidth, and the two can be equivalent. The base station indicates the different guardband configuration information to the UE through RRC signaling. According to the guardband configuration information, the UE can obtain the bandwidth or resource information actually used for transmission in different available bandwidth scenarios. It can be understood that the schemes for guardband indication in broadband carriers, channels or BWPs in various implementations are similar. For the sake of ease of description, only BWP is taken as an example below. However, the relevant embodiments are also applicable to guardband indication in broadband channels and guardband indication in broadband carriers, and do not constitute a limitation.

[0066] In a possible implementation, the indication of the guardband is pre-set in the system, and the base station can notify the UE of the guardband information through system messages and / or radio resource control signaling. In addition, the base station will also indicate the bandwidth information configured for the UE (hereinafter referred to as the configured bandwidth information) in the system message. Specifically, such as BWP information. Optionally, the BWP information includes uplink BWP information and downlink BWP information, and according to the BWP information, the UE can obtain the corresponding uplink and downlink configured bandwidth information. For unlicensed frequency bands, since LBT is required, for a certain BWP, the bandwidth actually available for transmission (hereinafter referred to as the available bandwidth) depends on the result of LBT, so the base station needs to indicate the corresponding guardband for all possible available bandwidth situations caused by the uncertainty of LBT. The UE can obtain the corresponding guardband information in all possible available bandwidth scenarios according to the corresponding guardband indication information. In some embodiments, the available bandwidth corresponds to the partial bandwidth through which LBT passes, and the unavailable bandwidth corresponds to the partial bandwidth that LBT fails. In some other embodiments, the available bandwidth may be less than the partial bandwidth through which LBT passes.

[0067] When LBT is required before data transmission, it is understandable that due to the uncertainty of LBT, the available bandwidth may be less than or equal to the configured bandwidth. At this time, the sending device needs to notify the receiving device of the available bandwidth. For the receiving device, according to the indicated configured bandwidth information, available bandwidth information, and then according to the guardband indication information, the resource location corresponding to the corresponding guardband in the current available bandwidth scenario can be obtained, and finally it can be known on which resources the data needs to be received.

[0068] Specifically, taking downlink transmission as an example, assuming that the downlink BWP configured by the base station is 80MHz, the base station needs to indicate the guardband information corresponding to all possible available bandwidth scenarios through system messages or RRC signaling. Exemplarily, assuming that the basic bandwidth of LBT is 20MHz, that is, LBT is performed on 4 20MHz subbands, then according to different results of LBT, the available bandwidth of the 80MHz BWP has the following possible combinations: subband1 or subband2 or subband3 or subband4 or subband1+2 or subband1+3 or subband1+4 or subband2+3 or subband2+4 or subband3+4 or subband1+2+3 or subband1+2+4 or subband1+3+4 or subband2+3+4 (such as Figure 6As shown in the figure, the available bandwidth is subband1+2+4, and the unavailable bandwidth is subband3. The indication of the guardband can be based on the available bandwidth, or optionally based on the unavailable bandwidth. Specifically, if the indication is based on the available bandwidth, the resources actually used for transmission are less than or equal to the resources corresponding to the available bandwidth minus the resources corresponding to the guardband, and when the indication is based on the unavailable bandwidth, the resources actually not used for transmission should be greater than or equal to the resources corresponding to the unavailable bandwidth plus the resources corresponding to the guardband. Optionally, in subsequent specific implementation plans, these two methods may be equivalent to each other). At this time, the base station needs to carry the guardband information corresponding to all the above possible combinations in the system message / RRC signaling for indication. It can be understood that for the transmission of system messages or RRC signaling on unlicensed frequency bands, LBT must also be performed first. Only after LBT is successful can the base station send the above message.

[0069] It can be seen that in the implementation manner of the present invention, one of the following four types of indications or any combination thereof is included: indication of configured bandwidth information, indication of available bandwidth information, indication of unavailable bandwidth information or indication of Guardband information.

[0070] Implementation of an indication for configuring bandwidth information

[0071] The base station can indicate the configured bandwidth information through system message / RRC. Specifically, the configured bandwidth information includes the location information of the configured bandwidth and / or the subcarrier spacing, etc. Referring to the description of BWP in 3GPP 38.331, such as the definition of BWP information element, the location information of the configured bandwidth can directly define one or more of the subcarrier spacing, starting RB, ending RB, and the number of RBs corresponding to the configured bandwidth, etc. The UE can obtain the actual frequency domain position of the configured bandwidth according to the indication information, such as the subcarrier spacing, the starting RB, and the corresponding total number of RBs. Further optionally, the configured bandwidth information can also include the subband information corresponding to the BWP. For example, the configured bandwidth indication information also includes the number of subbands divided by the BWP, such as NrofSubband, and the frequency domain position corresponding to each subband. The frequency domain position information of the subband can be absolute frequency domain position information, or can also be indicated by the starting RB and / or the number of RBs, that is, the UE can obtain the frequency domain position corresponding to the subband according to the starting RB corresponding to the subband and the number of RBs contained. Optionally, the indication may also be performed by indicating a starting RB and / or an ending RB.

[0072] In addition, in a possible manner, the configured bandwidth information includes multiple configured bandwidth information, and the multiple configured bandwidth information can be carried in the same indication information, or in multiple indication information. That is, for the same UE, the base station can configure multiple different configured bandwidth information for it, and each information corresponding to the configured bandwidth can be implemented in any of the above methods.

[0073] The following is further explained with examples, such as Figure 7 As shown, assuming that the base station configures a 80MHz downlink BWP for a certain UE, and the subcarrier spacing is 60KHz, the base station can indicate that the subcarrier spacing of the 80MHz BWP is 60KHz, and the frequency domain position is RB#0 to RB#106, with a total of 107 RBs by configuring bandwidth information. Specifically, the base station can indicate the starting RB#0 (the first one) and the number of RBs is 107; or the base station can indicate that the starting RB is RB#0 (the first one) and the ending RB is RB#106 (the last one), and the UE can obtain the frequency domain position of the configured 80MHz BWP according to the indication information. Further, the base station may also configure bandwidth information of multiple subbands within the 80MHz BWP, exemplarily indicating that the number of subbands included is 4, further indicating that the bandwidth information corresponding to subband1 is the starting RB#0 and the number of RBs is 26, indicating that the bandwidth information corresponding to subband2 is the starting RB is RB#26 and the number of RBs is 27, indicating that the bandwidth information corresponding to subband3 is the starting RB is RB#53 and the number of RBs is 27, indicating that the bandwidth information corresponding to subband3 is the starting RB is RB#80 and the number of RBs is 27; or optionally, indicating that the bandwidth information corresponding to subband1 is the starting RB is RB#0 and the ending RB is RB#25, indicating that the bandwidth information corresponding to subband2 is the starting RB is RB#26 and the ending RB is RB#52, indicating that the bandwidth information corresponding to subband3 is the starting RB is RB#53 and the ending RB is RB#79, and indicating that the bandwidth information corresponding to subband4 is the starting RB is RB#80 and the ending RB is RB#106. It should be noted that the number of RBs and the division of subbands here are only used for scheme description and do not constitute a limitation. Other schemes may also be adopted. For example, the number of RBs corresponding to 80MHz is 108, and each subband contains 27 RBs, etc. The corresponding RBs can be arranged in ascending or descending order.

[0074] In addition, the base station can also configure multiple BWPs for the UE at the same time. Optionally, the base station can include information of multiple BWPs in one bandwidth configuration information, or the base station sends multiple bandwidth configuration information, each bandwidth configuration information includes information of one BWP. Figure 8As shown, the base station configures 80 MHz BWP for the UE and also configures four 20 MHz BWPs. For 80MHz BWP, the starting RB can be indicated as RB#0 and the number of RBs is 107; or the starting RB can be indicated as RB#0 and the ending RB is RB#106; for 20MHz BWP1, the starting RB can be indicated as RB#0 and the number of RBs is 26; or the starting RB can be indicated as RB#0 and the ending RB is RB#25; for 20MHz BWP2, the starting RB can be indicated as RB#27 and the number of RBs is 26; or the starting RB can be indicated as RB#27 and the ending RB is RB#52; for 20MHz BWP3, the starting RB can be indicated as RB#54 and the number of RBs is 26; or the starting RB can be indicated as RB#54 and the ending RB is RB#79; for 20MHzBWP4, the starting RB can be indicated as RB#81 and the number of RBs is 26; or the starting RB can be indicated as RB#81 and the ending RB is RB#106; the information can be included in the same configuration bandwidth information for indication, or optionally, it can also be indicated in multiple configuration bandwidth information respectively. It should also be noted that here, for the 60KHz subcarrier spacing scenario, the bandwidth size of the BWP is not limited, and can also be other values, such as 40MHz, 60MHz, 100MHz, etc.; the number of RBs corresponding to the 80MHz BWP and the number of RBs corresponding to each narrowband 20MHz BWP are only used for scheme description and do not constitute a limitation. They can also be other values, such as each 20MHz BWP corresponds to 24 RBs, such as Figure 8 As shown in FIG. 1 , other corresponding solutions may also be used for the number of RBs corresponding to each BWP.

[0075] Of course, in other implementations, the indication of the above-mentioned configuration bandwidth information may be implicit. For example, in some implementation schemes, the configuration bandwidth information may default to the bandwidth of initial access, such as initial active BWP.

[0076] After receiving the indication of the configured bandwidth information, the UE can obtain the range of the actual resource location corresponding to the downlink transmission according to the result of the LBT and in combination with the indication of the available bandwidth or the indication of the guardband information, and then complete the data reception within the available bandwidth in the bandwidth and outside the guardband. Specifically, the data reception is completed on the allocated resources, which is not involved in the embodiments of the present invention and will not be described in detail.

[0077] Implementation of indication of available bandwidth\indication of unavailable bandwidth information

[0078] Taking downlink transmission as an example, the scheme for uplink transmission can be analogous, and will not be elaborated here. When there is downlink data transmission, the base station first performs LBT, and then performs data transmission on the available bandwidth where LBT succeeds. The base station can indicate the information of the available bandwidth to facilitate the UE to correctly receive the data.

[0079] In one possible approach, the available bandwidth information is directly indicated in the downlink control information DCI. Figure 5 For example, the available bandwidth is subband1, subband2 and subband4, and the base station indicates the information of 1, 2 and 4 in the DCI. Alternatively, a bitmap is used in the DCI to indicate the information of the available bandwidth. For example, for four subbands, a 4-bit bitmap is used; each bit corresponds to a subband, and when the value of the bit is "1", it means that the subband corresponding to the bit is available. For example, when the available bandwidth is subband1, subband2 and subband4, "1101" can be used for indication.

[0080] In another example, the indication of available bandwidth may be optionally indicated in combination with RRC signaling. For example, the base station may index all possible available bandwidth combinations by number in advance through RRC signaling. Exemplarily, the index of available bandwidth is identified by AvailableBW_ID, and for all available bandwidth combinations, one or more indications included in the following configuration information may be used:

[0081] AvailableBWConfig::=Sequence(size(1..MaxNrofAvailableBW)ofAvailableBW)

[0082] AvailableBW::=sequence{

[0083] AvailableBW_ID indicates the index ID of the available bandwidth

[0084] Subcarrierspacing indicates the subcarrier spacing corresponding to the available bandwidth corresponding to the ID

[0085] BandwidthInfo indicates the available bandwidth information corresponding to the ID.

[0086] MaxNrofAvailableBW indicates the maximum number of all available bandwidth combinations supported.

[0087] It is not difficult to understand that the above indication method corresponds to a list indication method, that is, each available bandwidth ID corresponds to a detailed bandwidth information. For example, taking 80MHz BWP, 60KHz subcarrier spacing, and 4 subbands as an example, the corresponding MaxNrofAvailableBW=15, assuming that the BandwidthInfo corresponding to AvailableBW_ID=1 is subband1, that is, the available bandwidth with ID 1 corresponds to subband1. Optionally, the base station can also directly indicate the detailed resource information of the available bandwidth corresponding to the current available bandwidth ID in BandwidthInfo, such as through one or more of the starting resource position, the ending resource position, the number of resources, the absolute resource position, the resource index, etc. The resource can be RB / subcarrier / subcarrier set, etc. At this time, even if the UE does not obtain information about the subband by configuring the bandwidth information, it can still accurately obtain the resource information corresponding to each available bandwidth. It should be noted that the above format is only used to describe the scheme and does not constitute a limitation. All list-based indication methods are included in the scope of the present invention.

[0088] It can be understood that the above solution is indicated based on the subband method. When the base station is configured with multiple narrowband BWPs at the same time, a similar solution can also be indicated based on the narrowband BWP. Fig. 9 Taking the situation described in as an example, the corresponding available bandwidths are 20MHz BWP1, 20MHz BWP2 and 20MHz BWP4, and the base station indicates information 1, 2, and 4 in the DCI; or optionally, a bitmap is used in the DCI to indicate the information of the available bandwidth. For example, for four 20MHz BWPs, a 4-bit bitmap is used, and each bit corresponds to a 20MHz BWP, where the value of the bit is "1", indicating that the BWP corresponding to the bit is available. For example, when the available bandwidth is 20MHz BWP1, 20MHz BWP2 and 20MHzBWP4, "1101" can be used for indication; further optionally, the indication of the available bandwidth needs to be combined with RRC signaling. For example, the base station pre-numbers and indexes all possible available bandwidth combinations through RRC signaling, and the specific scheme is the same as before.

[0089] It should be noted that, for the configuration of narrowband BWP, in some implementations, the resources corresponding to multiple adjacent narrowband BWPs may not be continuous. Fig. 9As shown, the RBs corresponding to BWP1 are RB#0-RB#25, and the RBs corresponding to BWP2 are RB#27-RB#52, with one RB in between. In other implementation schemes, the number of RBs in between may also be other values. At this time, the indication of the available bandwidth has the following possible implementations: Optionally, the available bandwidth is the union of the resources corresponding to the indicated multiple available BWPs. For example, when the base station indicates that the available bandwidth is BWP1, BWP2, and BWP4, the resources corresponding to the available bandwidth are RB#0-RB#25, RB#27-RB#52, and RB#81-RB#106. Optionally, according to the indication of the indicated available BWP, the unavailable BWP information can be obtained, and the available bandwidth corresponds to the remaining resources after the total resources are removed from the resources corresponding to the unavailable BWP. For example, when the base station indicates that the available bandwidth is BWP1, BWP2, and BWP4, the resources corresponding to the available bandwidth are all resources except the resources RB#54-RB#79 corresponding to the unavailable BWP3. Based on the above RRC signaling, when indicating available bandwidth, the base station can indicate the index ID corresponding to the actual transmission bandwidth in the DCI, and the UE can obtain the corresponding available bandwidth information based on the index ID and the information indicated in the RRC signaling.

[0090] After the UE obtains the available bandwidth information through the aforementioned method (DCI direct indication, or RRC combined with DCI indication), it can be combined with the indication of the guardband information or the guardband determination principle specified in the standard, and the UE can obtain the corresponding guardband information under the current available bandwidth scenario. Combined with the available bandwidth information and the guardband information, the UE can know the range of the actual resource location corresponding to the downlink transmission, and then complete the data reception within the available bandwidth in the bandwidth and outside the guardband. (Specifically, completing data reception on the allocated resources is not involved in the implementation of the present invention and will not be repeated)

[0091] Implementation of the indication of guardband information

[0092] In one possible way, the base station directly displays the information indicating the guardband in the system message or RRC signaling. Exemplarily, the displayed guardband information can be implemented by indicating the size of the guardband, for example, X RBs or subcarriers or subcarrier sets. Another example is to directly indicate that the bandwidth occupied by the guardband is XHz or XMHz, etc., and another example is to indicate that the guardband is a percentage of a certain bandwidth or a certain frequency domain unit size, etc. Under this scheme, the UE can determine the resource location of the guardband based on the configured bandwidth information and the available bandwidth information, combined with the size of the guardband. That is, the UE can determine the resource location of the guardband at one or more boundaries of the available bandwidth based on the aforementioned information received.

[0093] For example, reference Fig.10 , also taking 80MHz BWP and 60KHz subcarrier spacing as an example, assuming that LBT is performed on 4 20MHz subbands, the available bandwidth is subband1+3+4. Continuing with the previous assumptions, according to the bandwidth configuration information and the indication of the available bandwidth, it can be known that the resources corresponding to the available bandwidth are the frequency domain resources corresponding to subband1, subband3, and subband4, namely RB#0~RB#25, and RB#53~RB#106. At this time, exemplarily, the base station can directly display the size of the guardband as 2 RBs. After receiving this information, the UE can know that the two RBs located at the two available bandwidth boundaries (the two RB#24 and RB#25 at the first boundary, and the two RB#53 and RB#54 at the second boundary) are guardbands. It can be understood that when the guardband information only includes the size of the guardband, the criterion for further confirming the position of the guardband based on the available bandwidth should be a default or standard pre-defined criterion, such as stipulating that the guardband corresponds to one or more boundaries of the available bandwidth, X consecutive RBs or subcarriers or subcarrier sets along the direction of decreasing bandwidth, or in ascending and / or descending order. It can be understood that other pre-defined rules may also be used, and the embodiments of the present invention are not limited thereto.

[0094] Alternatively, optionally, the explicit guardband information can be implemented by directly indicating the resource location corresponding to the guardband. In this case, the base station needs to indicate the resource location of the corresponding guardband for all possible available bandwidths. The resource location information can be in the form of start and end resource indexes, and / or the starting resource and the number of resources, and / or directly indicating the resource index, and the resource can be a resource block RB / subcarrier / subcarrier set, etc.

[0095] Exemplarily, the index of the available bandwidth is identified by AvailableBW_ID, and the guardband corresponding to all the available bandwidths may be indicated by one or more of the following configuration information:

[0096] GuardbandConfig::=Sequence(size(1..MaxNrofAvailableBW)of Guardband)

[0097] Guardband::=sequence{

[0098] AvailableBW_ID indicates the index ID of the available bandwidth

[0099] Subcarrierspacing indicates the subcarrier spacing corresponding to the available bandwidth corresponding to the ID

[0100] GuardbandInfo indicates the guardband information corresponding to the available bandwidth corresponding to the ID.

[0101] MaxNrofAvailableBW indicates the maximum number of all available bandwidth combinations supported.

[0102] Specifically, for example, using the previous example, assuming that the available bandwidth AvailableBW_ID=13 corresponds to the available bandwidth subband1+3+4, the corresponding GuardbandInfo is RB#24 and RB#25, and RB#53 and RB#54.

[0103] Optionally, the guardband information may also be included in the available bandwidth configuration information, such as by adding a column of information to the available bandwidth configuration information, such as by one or more instructions included in the following configuration information:

[0104] AvailableBWConfig::=Sequence(size(1..MaxNrofAvailableBW)ofAvailableBW)

[0105] AvailableBW::=sequence{

[0106] AvailableBW_ID indicates the index ID of the available bandwidth

[0107] BandwidthInfo indicates the available bandwidth information corresponding to the ID

[0108] Subcarrierspacing indicates the subcarrier spacing corresponding to the available bandwidth corresponding to the ID

[0109] GuardbandInfo indicates the guardband information corresponding to the available bandwidth corresponding to the ID.

[0110] Where MaxNrofAvailableBW indicates the maximum number of all available bandwidth combinations supported;

[0111] It is not difficult to understand that the above configuration information corresponds to the content contained in Table 1 (the values ​​in Table 1 are only used to illustrate the solution and do not constitute a limitation)

[0112] Table 1

[0113]

[0114]

[0115] In another possible implementation, the base station indirectly indicates the guardband information corresponding to the available bandwidth through RRC signaling, and optionally indicates the resource information that can be actually used for transmission in various available bandwidth scenarios. It can be understood that the resources that can actually be used for transmission should be equal to the total resources included in the available bandwidth excluding the resources used for the guardband; for example, it can be achieved by one or more indications included in the following configuration information:

[0116] AvailableBWConfig::=Sequence(size(1..MaxNrofAvailableBW)ofAvailableBW)

[0117] AvailableBW::=sequence{

[0118] AvailableBW_ID indicates the index ID of the available bandwidth

[0119] Subcarrierspacing indicates the subcarrier spacing corresponding to the available bandwidth corresponding to the ID

[0120] BandwidthInfo indicates available bandwidth information

[0121] ResourceInfo indicates the actual available resources of the available bandwidth corresponding to the ID (implicitly indicating guardband information)}

[0122] Where MaxNrofAvailableBW indicates the maximum number of all available bandwidth combinations supported;

[0123] It is understandable that ResourceInfo implicitly includes guardband information.

[0124] Similarly, it is not difficult to understand that the above configuration information corresponds to the content contained in Table 2 (the values ​​in Table 2 are only used to illustrate the solution and do not constitute a limitation)

[0125] Table 2

[0126]

[0127]

[0128] In another example, optionally, indirectly indicating guardband information corresponding to available bandwidth can also be implemented by indicating resource information that is not available for transmission under various available bandwidth situations. It can be understood that the resources that are not available for transmission should be equal to the union of the total number of resources included in the unavailable bandwidth and the guardband resources.

[0129] For example, this is achieved by one or more instructions included in the following configuration information:

[0130] AvailableBWConfig::=Sequence(size(1..MaxNrofAvailableBW)ofAvailableBW)

[0131] AvailableBW::=sequence{

[0132] AvailableBW_ID indicates the index ID of the available bandwidth

[0133] Subcarrierspacing indicates the subcarrier spacing corresponding to the available bandwidth corresponding to the ID

[0134] UnavailableBandwidthInfo indicates unavailable bandwidth information

[0135] UnavailableResourceInfo indicates that the resource corresponding to the ID is unavailable under the available bandwidth (implicitly indicating guardband information)}

[0136] Where MaxNrofAvailableBW indicates the maximum number of all available bandwidth combinations supported;

[0137] Similarly, it is not difficult to understand that the above configuration information corresponds to the content contained in the following Table 3 (the values ​​in Table 3 are only used to illustrate the solution and do not constitute a limitation)

[0138] Table 3

[0139]

[0140]

[0141] It can be understood that for different bandwidths BWP, the number of RBs corresponding to different subcarrier spacing scenarios can be other values, the position relationship between the RBs corresponding to each subband and the RBs corresponding to the broadband BWP can be other methods, and the size of the guardband may also be other values ​​according to different requirements for signal energy leakage, and for devices with different capabilities, the size of the guardband may also be different. The numerical values ​​used in any of the above implementation schemes are for illustrative purposes only and do not constitute a limitation.

[0142] For other subcarrier spacing scenarios, such as 30KHz subcarrier and 15KHz subcarrier scenarios, any of the above indication schemes can be used. Fig.11 , assuming a BWP with 80MHz bandwidth and 30KHz subcarrier spacing, corresponding to 217 RBs, for the indication of the configured bandwidth, the base station can configure the location information of the bandwidth through system messages or RRC signaling, and directly define one or more of the subcarrier spacing, starting RB, ending RB, and number of RBs corresponding to the configured bandwidth. The UE can obtain the actual frequency domain position of the configured bandwidth based on the indication information, such as the subcarrier spacing, starting RB, and the corresponding total number of RBs. Furthermore, the multiple subbands divided by the BWP can also be indicated by indicating the number of subbands, the starting RB, ending RB, number of RBs, etc. corresponding to each subband. According to the indication information, the UE can accurately obtain the frequency domain position corresponding to the BWP, the corresponding resource block position, and the frequency domain position of each subband, and the corresponding resource block position. Fig.11 , the 30KHz subcarrier spacing and the 80MHz bandwidth BWP corresponding RBs are RB#0-RB#216 through system message / RRC signaling, and subband1 corresponds to RB#0-RB#54 for a total of 55 RBs, subband2 corresponds to RB#56-RB#108 for a total of 54 RBs, subband3 corresponds to RB#109-RB#162 for a total of 54 RBs, and subband4 corresponds to RB#163-RB#216 for a total of 54 RBs. The division of subbands can also be other ways, without limitation. The detailed indication method can refer to the previous implementation method, which will not be repeated here.

[0143] Furthermore, one or more BWPs may be configured on this basis. Optionally, the RBs corresponding to any two adjacent BWPs may be continuous or non-continuous. Fig.12As shown, one or more BWPs can be configured on the basis of the configured 80MHz BWP, such as configuring one or more 20MHz BWPs and / or one or more 40MHz BWPs, wherein the four 20MHz BWPs correspond to RB#0-RB#50, RB#55-RB#105, RB#111-RB#161, RB#166-RB#216, respectively, and each 20MHz BWP corresponds to 51 RBs; two 40MHz BWPs correspond to 106 RBs, namely RB#0-RB#105, RB#111-RB#216; it can be understood that the number of RBs corresponding to each BWP may also be other values, and the specific distribution may also be by other schemes, which is not limited to the embodiments of the present invention.

[0144] Accordingly, the indication of available bandwidth and the indication of guardband information can adopt a similar solution as in the aforementioned 60KHz subcarrier scenario, which will not be described in detail here. Similarly, the indication of 15KHz subcarrier is similar.

[0145] Optionally, for any of the above implementation schemes, the resource indication may be based on an RB as a basic unit, and optionally, may also be based on an RB group (RBG), a subcarrier, a subcarrier set, etc. as a basic unit.

[0146] In another possible implementation, the guardband information is predefined in the standard protocol, that is, no signaling is required. However, it is necessary to clearly specify the guardband information, such as size, location, etc., in the standard protocol such as 38.101 or 38.104. Optionally, the corresponding guardband information can be specified based on one or any combination of different configured bandwidths, different subcarrier spacings, different device capabilities, or different available bandwidth scenarios. Exemplarily, as shown in Table 4. Optionally, unified guardband information can also be specified, that is, the same guardband principle is adopted in all scenarios. Exemplarily, the following conditions need to be met to specify the in-band guardband: when the available bandwidth consists of one or more sub-bands, the in-band guardband at each sub-band is equal to X% of the sub-band bandwidth, such as X=10 or other values; or optionally, the absolute size of the in-band guardband is specified, such as X MHz. In addition, as mentioned above, guardband can also be configured based on unavailable bandwidth. Guardband can also be part of bandwidth other than unavailable bandwidth that is continuous with unavailable bandwidth, and its size can be, for example, N% of unavailable bandwidth, such as N=5 or 10 or other values.

[0147] Among them, multiple continuous subbands can be regarded as a larger subband, or optionally, as multiple independent subbands. In particular, different X values ​​can be defined for devices with different capabilities. For example, for devices with higher capabilities, the in-band guardband at each subband is equal to 5% of the bandwidth of the subband, while for devices with slightly lower capabilities, the in-band guardband is equal to 10% of the bandwidth of the subband, so as to maximize resource utilization while reducing interference. At this time, the base station only needs to notify the UE of the configured bandwidth information and available bandwidth information. The UE can obtain the resource location corresponding to the guardband according to the provisions in the standard protocol, and then know which resources need to be used to receive data. Optionally, when determining the guardband resource location, it is necessary to calculate based on the subcarrier spacing; for example, continue with Figure 6 For example, for a certain 80MHz BWP, after LBT, the available bandwidth corresponds to subbands 1, 2, and 4. Optionally, subbands 1 and 2 can be regarded as a continuous 40MHz subband, and the guardband at the corresponding subband boundary must meet 10% of the subband, that is, 4MHz. For a 60KHz subcarrier spacing, the resources corresponding to the guardband should be 4 / 0.72 rounded down or up, that is, 5 or 6 RBs. Then, according to the subband division indication, the actual RB corresponding to the guardband can be determined. Furthermore, optionally, subbands 1 and 2 can also be regarded as two independent subbands. Since subbands 1 and 2 are continuous, there is no need for a guardband between subbands 1 and 2. For the boundary between subbands 2 and 3, the guardband needs to meet 10% of subband 2, that is, 2MHz. At this time, for 60KHz subcarrier spacing, the resources corresponding to the guardband should be 2 / 0.72 rounded down or up, that is, 2 or 3 RBs. Then, according to the subband division indication, the actual RB corresponding to the guardband can be determined. For other bandwidths and other subcarrier spacing scenarios, the solution is similar and will not be repeated.

[0148] In the above embodiment, based on the predefined resource block distribution diagrams under different bandwidths, for example Figure 7-12 The transmitting end may not send the guardband indication, and the receiving end (such as the terminal) may determine the specific position and size of the guardband (for this communication) or the bandwidth to be used according to the received indication of the available bandwidth and the specified guardband information (the above X). The above resource block distribution diagram includes the size and position of one or more resource blocks included in each subband or BWP under a certain bandwidth. For details, please refer to Figure 7-12The resource block distribution diagram of any one or its variants, this implementation only takes 80MHz as an example, and the resource block distribution when the bandwidth is 20MHz, 40MHz, 160MHz or 320MHz can also be specified. For example, the resource block distribution for the bandwidth of 40MHz can be the first half or the second half of the aforementioned 80MHz bandwidth.

[0149] Table 4

[0150]

[0151] In another implementation manner, the base station may also dynamically indicate the guardband information through DCI information. Optionally, a direct indication method may be used to add a new field in the DCI or design a new DCI for guardband indication. Specifically, the resource location corresponding to the guardband may be directly indicated in the DCI, such as indicating one or more information in the starting resource index, ending resource index, number of resources, all resource indexes, etc. corresponding to the guardband. Optionally, an implicit indication method may also be used in the DCI. For example, by indicating the resource information actually used for transmission in the DCI, it can be understood that the resources actually available for transmission should be equal to the remaining resources after the available bandwidth is deducted from the resources corresponding to the guardband. Specifically, one or more information in the starting resource index, ending resource index, number of resources, all resource indexes, etc. corresponding to the resources actually used for transmission may be indicated. Optionally, the implicit indication method may also indicate the resource information actually not used for transmission. It can be understood that the resource information actually not transmitted should be equal to the union of the resources corresponding to the actual unavailable bandwidth and the guardband resources. Specifically, one or more information in the starting resource index, ending resource index, number of resources, all resource indexes, etc. corresponding to the resources actually used for transmission may be indicated.

[0152] Implementation of an indication for configuring an intra carrier guard band

[0153] In one possible manner, the base station configures one or more LBT bandwidths for the UE and configures one or more in-band guard bands. The base station carries an indication in the system message or RRC signaling for indicating the resource location information of the one or more in-band guard bands. In other words, the base station can also explicitly indicate the resource location information of the one or more in-band guard bands. The LBT bandwidth can be understood as a subband, or can also be expressed as a sub-band. The base station can perform LBT on the one or more LBT bandwidths, determine whether to send or receive data on the one or more in-band guard bands based on the LBT results, and indicate that the UE receives downlink data or sends uplink data on the one or more in-band guard bands through a displayed indication (e.g., dynamic signaling) or an implicit indication (e.g., a preset rule). The results of LBT may include LBT success (also referred to as LBT pass) and LBT failure. In different implementations, the LBT bandwidth can also be an RB range, that is, the base station configures one or more RB ranges for the UE, or the LBT bandwidth can be an RB set, that is, the base station configures one or more RB sets for the UE.

[0154] The resource location information of the in-band guard band may be represented by a starting resource index and an ending resource index, and / or a starting resource and a resource number, and / or a resource index is directly indicated. The resource may be a resource block RB, a subcarrier or a subcarrier set, etc. For example, the base station may indicate the starting RB index (index) and the ending RB index of the in-band guard band to the UE, or the base station may indicate the starting RB index and the number of occupied RBs of the in-band guard band to the UE.

[0155] For example, reference Fig.13 and Fig.14, the base station configures a carrier or BWP for the UE, in which 4 LBT bandwidths are divided. For the convenience of explanation, "LBT bandwidth#0~#3" is used to represent it. An in-band guard band is configured between two adjacent LBT bandwidths, and 3 in-band guard bands are configured between the 4 LBT bandwidths. For the convenience of explanation, "in-band guardband#1~#3" is used to represent it. The in-band guard band can be configured by the number of RBs, the number of subcarriers or the absolute bandwidth. Taking the BWP of 80MHz and the subcarrier spacing of 60kHz as an example, there are a total of 107 RBs, numbered #0~#106 respectively. Exemplarily, the frequency domain resources corresponding to the three in-band guard bands are: guard band#1 is RB#24~RB#27, guardband#2 is RB#51~#54, and guard band#3 is RB#78~#81, which is not limited in this application.

[0156] In the case where the UE has one or more serving cells, the base station configures an in-band guard band for some or all of the serving cells (per cell) of the UE, for example, the above-mentioned in-band guard band resource indication information is configured for one serving cell. Exemplarily, the signaling for configuring the in-band guard band for a serving cell can be carried in the serving cell configuration (ServingCellConfig) or the serving cell common configuration (ServingCellConfigCommon), that is, the above-mentioned in-band guard band resource indication information is configured in ServingCellConfig or ServingCellConfigCommon. Exemplarily, a set of parameters (parameters) or a parameter (parameter) can be added to servingcellconfig or ServingCellConfigCommon to indicate the above-mentioned resource location information, or a sequence (sequence) method can be used. For the same serving cell, the in-band guard bands of the uplink and downlink can be the same or different. In the case where the UE is configured with one or more BWPs, the base station configures an in-band guard band for some or all of the BWPs (per BWP) of the UE, for example, the above-mentioned in-band guard band resource indication information is configured for one BWP. Exemplarily, the signaling for configuring the in-band guard band may be carried in the information element (IE) BWP, BWP-DownlinkCommon, BWP-DownlinkDedicated, BWP-UplinkCommon or BWP-UplinkDedicated. For the same BWP, the in-band guard bands of uplink and downlink may be the same or different.

[0157] For the downlink, the base station performs LBT on each LBT bandwidth before sending the downlink signal. Fig.13, the base station successfully listens in LBT bandwidth #1~#3 and can send downlink signals. The base station fails to listen in LBT bandwidth #0 and cannot send downlink signals. The base station can send downlink data on in-band guard band #2 and #3, but cannot send downlink signals on in-band guard band #1. For the uplink, if the UE is scheduled to send PUSCH on LBT bandwidth #1~#3, the UE can send uplink data on in-band guard band #2 and guard band #3. However, it cannot send uplink data on in-band guard band #1. In different implementations, the subbands that failed LBT or were not scheduled can be at the edge of the carrier or BWP (such as Fig.13 ), or in the middle of the carrier or BWP (such as Fig.14 ).

[0158] During downlink transmission, the base station can configure the rate matching pattern (RMP) for the corresponding dynamically schedulable in-band guard band through PDSCH-Config in the RRC signaling, which can indicate the rate matching pattern corresponding to the in-band guard band. For example, RMP is used to configure the RB on the corresponding in-band guard band without mapping PDSCH. The dynamically schedulable in-band guard band can be all the in-band guard bands configured in the carrier or BWP, or it can be part of the in-band guard bands configured in the carrier or BWP. For example, refer to Fig.15 , configure rate matching mode #1 (RMP#1) for in-band guard band #1, and configure rate matching mode #2 (RMP#2) for in-band guard band #2.

[0159] In some implementations, a rate matching pattern group (RMPG) may also be configured for the rate matching pattern of the guard band in the band. Fig.15 , RMP#1 corresponding to the in-band guard band#1 is added to RMPG#1, and RMP#2 corresponding to the in-band guard band#2 is added to RMPG#2.

[0160] Furthermore, the base station indicates whether to map the PDSCH to the in-band guard band through the RMI in the downlink control information (DCI). For example, RMI is used to indicate whether the base station uses RMPG. When RMPG is used, the base station does not map PDSCH to the RB on the guard band corresponding to the RMP in the RMPG; when RMPG is not used, the base station maps PDSCH to the RB on the guard band corresponding to the RMP in the RMPG. The UE determines whether to receive the PDSCH based on the RMI. Exemplarily, the RMI can be 2 bits in DCI format 1-1. The most significant bit (MSB) in the RMI is used to indicate whether the base station uses RMPG#1, and the least significant bit (LSB) in the RMI is used to indicate whether the base station uses RMPG#2. Determine whether the RB in the in-band guard band corresponding to the RMP contained in the RMPG is mapped to PDSCH based on the indication of the downlink control information. For example, a bit value of "0" indicates that the corresponding in-band guard band resource can be mapped to PDSCH, and a bit value of "1" indicates that the corresponding in-band guard band resource is not mapped to PDSCH. RMI="00" means that the in-band guard band resources corresponding to the set of RMPG#1 and RMPG#2 can be mapped to PDSCH, that is, both in-band guard band#1 and in-band guard band#2 can be mapped to PDSCH; RMI="10" means that the in-band guard band resource corresponding to RMPG#1 is not mapped to PDSCH, and the in-band guard band resource corresponding to RMPG#2 can be mapped to PDSCH, that is, in-band guard band#1 is not mapped to PDSCH, and in-band guard band#2 can be mapped to PDSCH; RMI="01" means that the in-band guard band resource corresponding to RMPG#1 can be mapped to PDSCH, and the in-band guardband resource corresponding to RMPG#2 is not mapped to PDSCH, that is, in-band guard band#1 can be mapped to PDSCH, and in-band guard Band#2 is not mapped to PDSCH; RMI = "11", indicating that the in-band guard band resource set corresponding to RMPG#1 and RMPG#2 cannot be mapped to PDSCH, that is, in-band guard band#1 and guard band#2 are not mapped to PDSCH.In other implementations, a bit value of "1" may indicate that the corresponding in-band guard band resource cannot be mapped to PDSCH, and a bit value of "0" may indicate that the corresponding in-band guard band resource can be mapped to PDSCH.

[0161] The UE determines whether the base station has mapped the PDSCH in the in-band guard band by reading the RMI in the DCI of the PDSCH. Fig.15 The PDSCH scheduled by DCI occupies 2 LBT bandwidths (LBT bandwidths #1 and #2) and 2 in-band guardbands (in-band guard band #1 and #2). The UE learns through RMI that the base station has mapped the PDSCH on the in-band guard band #2 (box A shown in the figure) and has not mapped the PDSCH on the in-band guard band #1 (box B shown in the figure), and rate matching is required.

[0162] It is understandable that in other implementations, the number of RMPGs may be other values, and the RMP contained in the RMPG may be other values. Accordingly, the base station may increase the number of RMPGs configured in the high-level signaling, that is, increase the number of bits of the RMI carried in the DCI, and each bit corresponds to an RMPG. This solves the problem in the prior art that the number of guard bands in the rate matching indication method is limited, and improves communication efficiency.

[0163] In some other embodiments, the DCI may carry an intra-carrier guard band indicator (GBI) to indicate whether the intra-band guard band is mapped to PDSCH. For example, the GBI is carried in DCI format 1-1. For different UEs, the base station can configure whether to carry the GBI in DCI format 1-1. The GBI occupies X bits in the DCI, each corresponding to an intra-band gard band, where each bit corresponds to an intra-band guard band configured by a higher layer. Exemplarily, if the bit is 0, it means that the frequency domain resources corresponding to the intra-band guard band are not mapped to PDSCH, and if the bit is 1, it means that the frequency domain resources corresponding to the intra-band guard band are mapped to PDSCH; or if the bit is 1, it means that the frequency domain resources corresponding to the intra-band guard band are mapped to PDSCH, and if the bit is 0, it means that the frequency domain resources corresponding to the intra-band guard band are mapped to PDSCH. In the case where the UE is scheduled with frequency domain resources overlapping with the intra-band guard band, rate matching is performed for the overlapping frequency domain resources. Exemplarily, the number of bits of the GBI can be adjusted according to the number of in-band guard bands, or the number of bits of the GBI can be the maximum number of in-band guard bands configurable by the system, and N LSBs or N MSBs in X bits are used as indication bits for indicating the in-band guard band (N<=X).

[0164] by Fig.13 For example, the base station configures 3 in-band guard bands, and uses "1" to indicate that the corresponding in-band guard band cannot map PDSCH, and "0" to indicate that the corresponding in-band guard band can map PDSCH. GBI="100" can be indicated in the DCI, where the 1st to 3rd bits correspond to in-band guard band #1 to 3, respectively. Then the UE can know that guard band #1 cannot map PDSCH. Similarly, the base station can indicate GBI="110" in the DCI, corresponding to Fig.14 It can be understood that, when it is necessary to increase / decrease the number of guard bands indicated by the GBI, the number of bits of the GBI can be increased / decreased.

[0165] In another embodiment, the base station and the UE may agree on a default rule through a protocol. When the UE is configured to receive a GC-PDCCH carrying an indication of available LBT bandwidth, after the UE detects valid available bandwidth, the UE can determine whether the gNB has mapped the PDSCH on the in-band guard band based on the available LBT bandwidth. For example, if the LBT bandwidths on both sides of the in-band guard band are available bandwidths, the base station maps the PDSCH on the in-band guard band, otherwise, the base station does not map the PDSCH on the in-band guard band. Please refer to Fig.15 , the UE detects that the available LBT bandwidth indicated by the base station is LBT bandwidth#1 and LBT bandwidth#2. When the UE receives the DCI-scheduled PDSCH occupying LBT bandwidth#1 and #2, and LBT bandwidth#1 and #2 are available bandwidths, it is determined that PDSCH is mapped on the in-band guard band#2 between LBT bandwidth#1 and #2; and the in-band guard band#1, because the LBT bandwidth#0 on one side is a non-available bandwidth, the base station does not map PDSCH on guard band#1. In an exemplary embodiment, when the base station sends a GC-PDCCH at the start of a downlink burst, and the available bandwidth indication carried therein is all "0" or all "1", indicating that the currently sent available bandwidth indication is invalid, when the UE receives the bandwidth indication value, it can be considered that PDSCH is not mapped on the in-band guard band.

[0166] In another example, based on the fallback DCI (DCI format 1-0) in NR, it is assumed by default that all configured in-band guard bands are unavailable. When the terminal detects a PDSCH scheduled using the fallback DCI, it can also be considered that the base station has not mapped the PDSCH on the in-band guard band. The use of a simplified signaling design can reduce system overhead.

[0167] The transmission and reception of downlink PDSCH are described in the previous text. For the transmission and reception of uplink PUSCH, a method similar to the transmission and reception of downlink PDSCH can also be adopted. For example, the base station configures RMI or GBI in the DCI for scheduling PUSCH to indicate whether the UE maps PUSCH on the in-band guard band overlapping with the allocated frequency domain resources. In some embodiments, the UE can only send if the LBT on all LBT bandwidths overlapping with the scheduled PUSCH is successful. Then the DCI (DCI format 0-1) carries 1 bit to indicate whether the UE maps PUSCH on the in-band guardband that can map PUSCH. For example, the 1 bit can be RMI or GBI. It can be understood that although both are called RMI / GBI, there may be differences in the RMI / GBI mechanism in the uplink and the RMI / GBI mechanism in the downlink. Exemplarily, the base station can configure whether to carry the 1 bit in (DCI format 0-1), for example, according to the capability configuration of the UE. Furthermore, the UE can determine in which specific guard bands the PUSCH can be mapped through the frequency domain scheduling information carried by the base station in the uplink scheduling DCI. For example, please refer to Fig.16 , DCI schedules the UE to send PUSCH on LBT bandwidth #1, #2 and #3 and in-band guardband #2 and #3 (dummy boxes A and C), and does not send PUSCH on guard band #1 (box B). Therefore, the UE maps PUSCH on guard band #2 and guard band #3. Since the LBT result of LBT bandwidth #0 is unknown, the UE cannot map PUSCH on guard band #1. The UE can determine whether to map PUSCH on guard band #2 and guard band #3 based on the dynamic indication of the base station. In an example, the base station can use fallback DCI (DCI format 0-0) to schedule PUSCH, and the UE may not map PUSCH in the in-band guard band that overlaps with the uplink frequency domain scheduling.

[0168] The relevant features of this embodiment can be referenced or combined with the above embodiments or the following embodiments, so the repeated parts are not repeated. In addition, the network device or terminal (or related modules, chips, systems, computer programs, storage media) involved in the subordinate device embodiment or system embodiment can also be used to execute the method provided in the embodiment of this application.

[0169] In the aforementioned implementation modes, information such as configured bandwidth, available bandwidth or guardband is carried by RRC or standard preset or DCI indication, so as to indicate the in-band guardband information in the broadband scenario to the UE.

[0170] In addition, on the receiving side, the terminal or UE can determine the guardband based on the indication of the configured bandwidth, available bandwidth and / or guardband. In this way, interference caused by signal leakage can be avoided, and the decoding probability can be increased, thereby improving system performance.

[0171] The specific implementation methods illustrated above further explain the purpose and technical solutions of this application in detail. It should be understood that the above description is only the specific implementation methods of this application and is not intended to limit the scope of protection of this application. Any modification, equivalent replacement, improvement, etc. made on the basis of the technical solution of this application shall be included in the scope of protection of this application.

[0172] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented by software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present invention is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website site, computer, server or data center to another website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state hard disk Solid State Disk (SSD)), etc.

Claims

1. A method for indicating a guard band in an unlicensed spectrum, characterized in that: include: The communication device generates an indication of guardband information within a partial bandwidth BWP, where the guardband information indicates a starting resource block (RB) and the number of RBs corresponding to the guardband within the BWP, the BWP including multiple RB sets, and the guardband being located between two adjacent RB sets; The communication device sends an indication of the guard band information.

2. The method according to claim 1, characterized in that Data is transmitted within the available bandwidth in the BWP and within a range of resource locations outside the guardband.

3. The method according to claim 1 or 2, characterized in that The guardband information is carried in the RRC.

4. The method according to claim 1 or 2, characterized in that Different configured bandwidths and different subcarrier spacings correspond to the guardband sizes and positions predefined by the standard.

5. A method for determining a guard band in an unlicensed spectrum, characterized in that: include: The communication device receives an indication of guard band information within a partial bandwidth BWP, where the guard band information indicates a starting resource block (RB) and the number of RBs corresponding to the guard band within the BWP, the BWP including multiple RB sets, and the guard band is located between two adjacent RB sets; The communication device determines the guardband according to an instruction of the guardband information.

6. The method according to claim 5, characterized in that Data reception is performed within the available bandwidth in the BWP and within a range of resource locations outside the guardband.

7. The method according to claim 5 or 6, characterized in that The guardband information is carried in the RRC.

8. The method according to claim 5 or 6, characterized in that Different configured bandwidths and different subcarrier spacings correspond to the guardband sizes and positions predefined by the standard.

9. A communication device, characterized in that: include: The first module is configured to generate an indication of guardband information within a partial bandwidth BWP, where the guardband information indicates a starting resource block (RB) and the number of RBs corresponding to the guardband within the BWP, where the BWP includes multiple RB sets, and the guardband is located between two adjacent RB sets; The second module is configured to send an indication of the guardband information.

10. The device according to claim 9, characterized in that The second module is further configured to send data within the available bandwidth in the BWP and within a resource location range outside the guardband.

11. The device according to claim 9 or 10, characterized in that The guardband information is carried in the RRC.

12. The device according to claim 9 or 10, characterized in that Different configured bandwidths and different subcarrier spacings correspond to the guardband sizes and positions predefined by the standard.

13. A communication device, characterized in that: include: The first module is configured to receive an indication of guardband information within a partial bandwidth BWP, where the guardband information indicates a starting resource block (RB) and the number of RBs corresponding to the guardband within the BWP, where the BWP includes multiple RB sets, and the guardband is located between two adjacent RB sets; The second module is configured to determine the guardband according to an indication of the guardband information.

14. The device according to claim 13, characterized in that The second module is further configured to receive data within the available bandwidth in the BWP and within a resource location range outside the guardband.

15. The device according to claim 13 or 14, characterized in that The guardband information is carried in the RRC.

16. The device according to claim 13 or 14, characterized in that Different configured bandwidths and different subcarrier spacings correspond to the guardband sizes and positions predefined by the standard.

17. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the method according to any one of claims 1 to 4 or 5 to 8 is implemented.

18. A communication device, characterized in that: include: processor, memory, and communication interfaces; The processor controls the sending and receiving actions of the communication interface; The memory stores a program; The processor calls the program stored in the memory to execute the method according to any one of claims 1 to 4 or 5 to 8.

Images