WO2025209230A1 - Cell bandwidth part setting method and apparatus - Google Patents

Abstract

A cell bandwidth part (BWP) setting method and an apparatus. The cell BWP setting method comprises: receiving downlink control information (DCI) of a first cell. The DCI may comprise a first field used for indicating a first BWP of a third cell, and a second field used for indicating a second BWP of a second cell. The first BWP is different from an activated BWP of the third cell. A BWP of the second cell is set as the second BWP on the basis of a first bit length and/or a second bit length. The first bit length of the second field is different from a second bit length of a second field of the first BWP. According to the present application, when the DCI indicates that a BWP of the third cell is switched to the first BWP, the second BWP is accurately set for the second cell on the basis of different bit lengths of the second fields under different BWPs, thereby improving the communication efficiency.

Description

Method and device for setting cell bandwidth part

This application claims priority to the Chinese patent application filed with the State Intellectual Property Office on April 3, 2024, with application number "202410409089.0" and invention name "Method and Device for Setting Partial Cell Bandwidth", the entire contents of which are incorporated by reference into this application.

Technical Field

The embodiments of the present application relate to the field of wireless communications, and in particular to a method and device for setting a cell bandwidth part (BWP).

Background Art

With the continuous emergence of services such as high-definition video, augmented reality (AR), and virtual reality (VR), wireless data traffic is rapidly increasing, driving the continuous evolution of wireless communication technology. Exploiting frequency and spatial resources for wireless communication is a crucial dimension of this evolution.

To support future network capacity and transmission rate requirements, carrier aggregation (CA) has been introduced to address the limited bandwidth of a single carrier. In CA scenarios, a terminal can be served by multiple cells, meaning that the terminal has multiple serving cells. For example, these multiple serving cells can include a primary cell (PCell) and one or more secondary cells (SCells).

In a CA scenario, when the BWP of the serving cell configured by the network device for the terminal needs to be changed, it is currently unclear how to configure the BWP of one or more SCells.

Summary of the Invention

The present application provides a method and apparatus for setting a cell BWP, which can accurately set a second BWP for a second cell according to different bit lengths of a second field in different BWPs when the BWP of a third cell is switched to a first BWP, thereby improving communication efficiency.

To achieve the above objectives, this application adopts the following technical solutions:

In a first aspect, a method for setting a cell BWP is provided. The method can be applied to a terminal, for example, a terminal or a communication module within the terminal, or a circuit or chip responsible for communication functions within the terminal. Taking the method applied to a terminal as an example, the method includes: receiving DCI from a first cell. The DCI may include a first field and a second field. The first field may be used to indicate a first BWP for a third cell. This first BWP is different from the activated BWP for the third cell. The third cell may be the cell with the smallest cell identifier among N cells corresponding to N FDRA fields. The values of the N FDRA fields may be invalid values. N is an integer greater than 1. The second field may be used to indicate a second BWP for the second cell. In some examples, the first cell may be a PCell and the second cell may be an SCell. The terminal may set the BWP for the second cell to the second BWP based on a first bit length and/or a second bit length. The first bit length of the second field may be different from the second bit length of the second field of the first BWP. The first bit length of the second field may be understood as the second bit length of the second field of the activated BWP. In some examples, the third cell may be either a PCell or an SCell.

It can be understood that the activation of BWP in the present application can be understood as activating the downlink BWP, and can also be understood as activating the uplink BWP.

This application can accurately set the second BWP for the second cell according to the different bit lengths of the second field in different BWPs when the BWP of the third cell is switched to the first BWP, thereby improving communication efficiency.

In one possible design, the format of the DCI may be a DCI format for scheduling multiple cells. The DCI includes M FDRA fields. The M FDRA fields may include N FDRA fields with invalid values. M is an integer greater than 1, and M is greater than or equal to N. The second field may be a field corresponding to the third cell. In some examples, the DCI format may be DCI format 1_1, DCI format 1_2, or DCI format 1_3.

In one possible design, the format of the DCI may be a DCI format for scheduling multiple cells. The first field is used to indicate the first BWP of each scheduled cell in the multiple scheduled cells indicated by the DCI. For example, for any of the multiple scheduled cells, when the activated BWP of the cell is different from the first BWP, the terminal device parses the fields in the DCI according to the RRC parameters configured by the first BWP. For another example, for any of the multiple scheduled cells, when the activated BWP of the cell is the same as the first BWP, the terminal device parses the fields in the DCI according to the RRC parameters configured by the activated BWP or the RRC parameters configured by the first BWP. In another possible design, the format of the DCI may be a DCI format for scheduling one cell. When the terminal device receives the DCI on the first cell, the DCI is used to schedule the physical downlink shared channel of the first cell. Wherein, the carrier indicator field (CIF) contained in the DCI takes a value of 0, or the DCI does not contain the CIF field, then the first field contained in the DCI is used to indicate the first BWP of the first cell.

In one possible design, setting the BWP of the second cell to the second BWP according to the first bit length and/or the second bit length may include: setting the BWP of the second cell to the second BWP according to the first bit length.

In one possible design, when the first bit length is less than the second bit length, setting the BWP of the second cell to the second BWP based on the first bit length and/or the second bit length may include setting the BWP of the second cell to the second BWP based on a first number of LSBs in a second field of the first BWP, where the first number is the same as the first bit length.

In one possible design, where the first bit length is greater than the second bit length, setting the BWP of the second cell to a second BWP based on the first bit length and/or the second bit length may include setting the BWP of the second cell to the second BWP based on a second number of LSBs in the second field, where the second number is the same as the second bit length.

In one possible design, the second field includes at least one of the following fields: an MCS field; an NDI field; an RV field; an HPN field; or an AP field, wherein the RRC parameters configure the AP field to be type 2.

In one possible design, the value of the FDRA field is an invalid value, which can be defined in the following way: the RA type is configured as type 0, and the FDRA field indicates all 0s; or, the RA type is configured as type 1, and the FDRA field indicates all 1s; or, the RA type is configured as a dynamic switching resource allocation type, and the FDRA field indicates all 0s or all 1s.

In a second aspect, a method for setting a cell BWP is provided. The method can be applied to a network side, for example, an access network device on the network side, a module (such as a circuit, chip, or chip system) within the access network device, or a logical node, logic module, or software that implements all or part of the access network device's functions. Taking the method applied to the access network device as an example, the method includes: configuring a second BWP for a second cell and sending DCI of the first cell. The DCI may include a first field and a second field. The first field may be used to indicate a first BWP for a third cell. The first BWP is different from the activated BWP of the third cell. The third cell may be the cell with the smallest cell identifier among N cells corresponding to N FDRA fields. The values of the N FDRA fields may be invalid values. N is an integer greater than 1. The second field may be used to indicate the second BWP of the second cell. In some examples, the first cell may be a PCell and the second cell may be an SCell. The first bit length of the second field is different from the second bit length of the second field of the first BWP. The first bit length of the second field can be understood as the second bit length of the second field of the activated BWP. The BWP of the second cell may be determined based on the second BWP and the first bit length and/or the second bit length. In some examples, the third cell may be a PCell or a SCell.

In one possible design, the format of the DCI may be a DCI format for scheduling multiple cells. The DCI includes M FDRA fields. The M FDRA fields may include N FDRA fields with invalid values. M is an integer greater than 1, and M is greater than or equal to N. The second field may be a field corresponding to the third cell. In some examples, the DCI format may be DCI format 1_1, DCI format 1_2, or DCI format 1_3.

In one possible design, the format of the DCI may be a DCI format for scheduling multiple cells. The first field is used to indicate the first BWP of each scheduled cell in the multiple scheduled cells indicated by the DCI. For example, for any of the multiple scheduled cells, when the activated BWP of the cell is different from the first BWP, the terminal device parses the fields in the DCI according to the RRC parameters configured by the first BWP. For another example, for any of the multiple scheduled cells, when the activated BWP of the cell is the same as the first BWP, the terminal device parses the fields in the DCI according to the RRC parameters configured by the activated BWP or the RRC parameters configured by the first BWP. In another possible design, the format of the DCI may be a DCI format for scheduling one cell. When the terminal device receives the DCI on the first cell, the DCI is used to schedule the physical downlink shared channel of the first cell. Wherein, if the CIF contained in the DCI has a value of 0 or the DCI does not contain a CIF, the first field contained in the DCI is used to indicate the first BWP of the first cell.

In one possible design, the second field includes at least one of the following fields: an MCS field; an NDI field; an RV field; an HPN field; or an AP field, wherein the RRC parameters configure the AP field to be type 2.

In one possible design, the value of the FDRA field is an invalid value, which can be defined in the following way: the RA type is configured as type 0, and the FDRA field indicates all 0s; or, the RA type is configured as type 1, and the FDRA field indicates all 1s; or, the RA type is configured as a dynamic switching resource allocation type, and the FDRA field indicates all 0s or all 1s.

In a third aspect, a communication device is provided, which has the functions of implementing the first or second aspect mentioned above. For example, the communication device includes a module or unit or means corresponding to executing the operations involved in the first or second aspect mentioned above. The module or unit or means can be implemented through software, or through hardware, or through a combination of software and hardware.

In a fourth aspect, a communication device is provided, comprising an interface circuit and one or more processors. The one or more processors are coupled to a memory. The memory is used to store part or all of the necessary computer programs or instructions for implementing the functions described in the first or second aspect. The one or more processors can execute the computer programs or instructions. When executed, the computer programs or instructions enable the communication device to implement the method of any possible design or implementation of the first or second aspect. The interface circuit is used to implement communication functions within the communication device and/or communication functions between the communication device and other devices or components.

In one possible design, the processor is configured to communicate with other devices or components through the interface circuit.

In one possible design, the communication device may also include the memory.

In some examples, the communication device may be a terminal, or a communication module in a terminal, or a chip in the terminal responsible for communication functions such as a modem chip (also known as a baseband chip) or a SoC or SIP chip including a modem module.

In some examples, the above-mentioned communication device can be an access network device, or a module in the access network device (such as a circuit, chip or chip system, etc.), or a logical node, logical module or software that can implement all or part of the functions of the access network device.

In a fifth aspect, a communication system is provided, which includes a terminal that executes any method of the first aspect and a network device that executes any method of the second aspect.

In a sixth aspect, a computer-readable storage medium is provided. The computer-readable storage medium stores computer instructions, which, when executed on a computer, cause the computer to execute the communication method according to any of the above aspects.

In a seventh aspect, a computer program product is provided, which includes a computer program or instructions, and when the computer program or instructions are run on a computer, causes the computer to execute any communication method designed in any of the above aspects.

The beneficial effects corresponding to the methods in any of the above-mentioned second to seventh aspects can be referred to the description of the beneficial effects of each method in the first aspect, and this application will not repeat them here.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG1 is a schematic diagram of the architecture of a mobile communication system used in an embodiment of the present application;

FIG2 is a schematic diagram of self-carrier scheduling;

FIG3 is a schematic diagram of cross-carrier scheduling;

FIG4 is a schematic diagram of a single DCI scheduling;

FIG5 is a schematic diagram of a BWP switching;

FIG6 is a schematic diagram of a method for setting a cell BWP according to an embodiment of the present application;

FIG7 is a schematic diagram of a correspondence between a second field and an SCell provided in an embodiment of the present application;

FIG8 is a schematic diagram of DCI changes under different BWPs provided by an embodiment of the present application;

FIG9 is another schematic diagram of DCI changes under different BWPs provided by an embodiment of the present application;

FIG10 is a schematic diagram of the relationship between the second field and the second cell under different BWPs provided by an embodiment of the present application;

FIG11 is a schematic diagram of a second cell BWP configuration provided by an embodiment of the present application;

FIG12 is a schematic diagram of another second cell BWP configuration provided by an embodiment of the present application;

FIG13 is a schematic diagram of another second cell BWP configuration provided by an embodiment of the present application;

FIG14 is a schematic diagram of a communication device provided in an embodiment of the present application;

FIG15 is a schematic diagram of another communication device provided in an embodiment of the present application.

DETAILED DESCRIPTION

FIG1 is a schematic diagram of the architecture of a communication system 1000 provided in an embodiment of the present application. As shown in FIG1 , the communication system 1000 includes a radio access network (RAN) 100, wherein the RAN 100 includes at least one RAN node (such as 110a and 110b in FIG1 , collectively referred to as 110), and may also include at least one terminal (such as 120a-120j in FIG1 , collectively referred to as 120). The RAN 100 may also include other RAN nodes, such as wireless relay devices and/or wireless backhaul devices (not shown in FIG1 ). The terminal 120 is connected to the RAN node 110 wirelessly. Terminals and RAN nodes may be connected to each other via wired or wireless means. The communication system 1000 may also include a core network 200. The RAN node 110 is connected to the core network 200 wirelessly or via wired means. The core network devices in the core network 200 and the RAN nodes 110 in the RAN 100 may be independent and different physical devices, or may be the same physical device that integrates the logical functions of the core network devices and the logical functions of the RAN nodes.

The RAN 100 may be an evolved universal terrestrial radio access (E-UTRA) system, a new radio (NR) system, a sixth generation (6G) radio access system, or future radio access systems defined in the 3rd Generation Partnership Project (3GPP). The RAN 100 may also include two or more of the aforementioned different radio access systems. The RAN 100 may also be an open RAN (O-RAN).

A RAN node, also known as a radio access network device, RAN entity, or access node, facilitates wireless access to a communication system. In one application scenario, a RAN node can be a base station (BS), an evolved NodeB (eNodeB), a transmission reception point (TRP), a next-generation NodeB (gNB) in a fifth-generation (5G) mobile communication system, a next-generation NodeB in a 6G mobile communication system, or a base station in future mobile communication systems. A RAN node can be a macro base station (such as 110a in Figure 1), a micro base station, an indoor station (such as 110b in Figure 1), a relay node, or a donor node.

In another application scenario, multiple RAN nodes can collaborate to help terminals achieve wireless access, with different RAN nodes implementing portions of the base station's functions. For example, a RAN node can be a centralized unit (CU), a distributed unit (DU), or a radio unit (RU). The CU implements the base station's radio resource control protocol and packet data convergence protocol (PDCP) functions, as well as the service data adaptation protocol (SDAP) functions. The DU implements the base station's radio link control layer and medium access control (MAC) layer functions, as well as some or all of the physical layer functions. For detailed descriptions of each of these protocol layers, please refer to the relevant 3GPP technical specifications. The RU is responsible for transmitting and receiving RF signals. The CU and DU can be two independent RAN nodes, or they can be integrated into the same RAN node, such as in the baseband unit (BBU). The RU can be included in radio equipment, such as a remote radio unit (RRU) or an active antenna unit (AAU). The CU can be further divided into two types of RAN nodes: the CU-control plane and the CU-user plane.

In different systems, RAN nodes may have different names. For example, in an O-RAN system, a CU may be called an open CU (O-CU), a DU may be called an open DU (O-DU), and a RU may be called an open RU (O-RU). The RAN nodes in the embodiments of the present application may be implemented using software modules, hardware modules, or a combination of software and hardware modules. For example, a RAN node may be a server loaded with the corresponding software modules. The embodiments of the present application do not limit the specific technologies and specific device forms used by the RAN nodes. For ease of description, the following description uses a base station as an example of a RAN node.

A terminal is a device with wireless transceiver capabilities that can send signals to or receive signals from a base station. A terminal may also be referred to as a terminal device, user equipment (UE), mobile station, mobile terminal, etc. Terminals can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grid, smart furniture, smart office, smart wearable, smart transportation, smart city, etc. A terminal can be a mobile phone, tablet computer, computer with wireless transceiver capabilities, wearable device, vehicle, aircraft, ship, robot, robotic arm, smart home appliance, etc. The embodiments of this application do not limit the specific technology and specific device form used by the terminal.

Base stations and terminals can be fixed or mobile. They can be deployed on land, indoors or outdoors, handheld or vehicle-mounted; on water; or on aircraft, balloons, and satellites. The embodiments of this application do not limit the application scenarios of base stations and terminals.

The roles of base stations and terminals can be relative. For example, the helicopter or drone 120i in Figure 1 can be configured as a mobile base station. To terminals 120j accessing the wireless access network 100 via 120i, terminal 120i is a base station. However, to base station 110a, 120i is a terminal, meaning that communication between 110a and 120i occurs via a wireless air interface protocol. Of course, communication between 110a and 120i can also occur via a base station-to-base station interface protocol. In this case, 120i is also a base station relative to 110a. Therefore, base stations and terminals can be collectively referred to as communication devices. 110a and 110b in Figure 1 can be referred to as communication devices with base station functionality, while 120a-120j in Figure 1 can be referred to as communication devices with terminal functionality.

Communication between base stations and terminals, between base stations, and between terminals can be carried out through authorized spectrum, unauthorized spectrum, or both; communication can be carried out through spectrum below 6 gigahertz (GHz), spectrum above 6 GHz, or spectrum below 6 GHz and spectrum above 6 GHz. The embodiments of the present application do not limit the spectrum resources used for wireless communication.

In the embodiments of the present application, the functions of the base station may also be performed by a module (such as a chip) in the base station, or by a control subsystem that includes the base station functions. The control subsystem that includes the base station functions here may be a control center in the above-mentioned application scenarios such as smart grid, industrial control, smart transportation, and smart city. The functions of the terminal may also be performed by a module (such as a chip or modem) in the terminal, or by a device that includes the terminal functions.

In a CA scenario, two or more component carriers (CCs) are aggregated to support a larger transmission bandwidth. A CC can also be called a component carrier or component carrier. A carrier is a radio signal or electromagnetic wave with a specific frequency, bandwidth, and format, emitted by a base station's main equipment. A carrier can be considered the main body used to carry information. In this application, "carrier," "cell," or "carrier frequency" can be used interchangeably.

In related technologies, if a base station wants to schedule terminals on multiple carriers for simultaneous physical downlink shared channel (PDSCH) or physical uplink shared channel (PUSCH) transmissions, it needs to send multiple downlink control information (DCI) messages for scheduling. Each carrier requires one DCI message for scheduling. Scheduling can be categorized as either self-carrier scheduling or cross-carrier scheduling, depending on the carrier on which the DCI is sent.

It can be understood that in each embodiment of the present application, PDSCH and PUSCH are merely examples of downlink data channels and uplink data channels, respectively. In different systems and different scenarios, data channels may have different names, and the embodiments of the present application do not limit this.

In the case of self-carrier scheduling, DCI scheduled for PDSCH or PUSCH transmission on a carrier is also sent on that carrier. For example, as shown in Figure 2 , DCI 1 scheduled for PDSCH 1 transmission on CC 1 is sent on CC 1, and DCI 2 scheduled for PDSCH 2 transmission on CC 2 is sent on CC 2. In the case of cross-carrier scheduling, DCI scheduled for PDSCH or PUSCH transmission on a carrier can be sent on another carrier. This allows multiple DCIs to be sent on a single carrier. For example, as shown in Figure 3 , DCI 1 scheduled for PDSCH 1 transmission on CC 1 and DCI 2 scheduled for PDSCH 2 transmission on CC 2 can both be sent on CC 1.

It can be understood that FIG2 and FIG3 are only described by taking PDSCH as an example, and the same is applicable to the scheduling of PUSCH.

As can be seen, for both self-carrier and cross-carrier scheduling, the number of DCIs required is proportional to the number of carriers used. This multi-DCI scheduling approach increases control channel overhead. For the terminal, blind detection (BD) requires multiple DCIs, so the terminal's blind detection budget increases with the number of carriers, increasing the complexity of terminal blind detection.

Other related technologies propose using a single DCI to schedule PDSCH or PUSCH on multiple frequency bands or carriers. This reduces the control channel overhead caused by using multiple DCIs to schedule multiple carriers and avoids configuring a physical downlink control channel (PDCCH) on each carrier.

In some examples, the DCI that schedules multiple carriers is referred to as a single DCI. As shown in Figure 4, in a discrete multi-carrier scenario, a single DCI is used to schedule multiple carriers. This can significantly reduce control channel overhead and free up more downlink resources for PDSCH transmission, thereby increasing downlink capacity.

Corresponding to the single DCI is the traditional DCI, which is used to schedule data for one cell, such as the DCI shown in Figures 2 and 3, i.e., the traditional DCI.

The BWP in NR can be defined as a contiguous common resource block (CRB) within a given subcarrier spacing. As shown in Figure 5 , a terminal can communicate within BWP 1. The network device can instruct the terminal to switch BWPs using the BWP indicator field in the DCI. After switching, the terminal can communicate within BWP 2. When the BWP indicated by the BWP indicator field is different from the terminal's currently active BWP, the network device instructs the terminal to switch BWPs. However, if the BWP indicated by the BWP indicator field is the same as the terminal's currently active BWP, the terminal does not need to switch BWPs. The terminal can continue to communicate on the currently active BWP. The activated BWP can be a downlink (DL) BWP or an uplink (UL) BWP. The BWP indicator field can indicate a BWP index or a BWP identity (ID). In other examples, the BWP indication field may also indicate a row index of a table, or a value of a bit state associated with the BWP.

However, there is currently no consensus on how to set the BWP for the SCell when the network device instructs the terminal to switch BWPs. Setting the active downlink BWP of the SCell to a specific BWP by the terminal device can be understood as switching the active downlink BWP to the specific BWP on the SCell. The network device can instruct the terminal device to set the active downlink BWP to the specific BWP via DCI.

Therefore, an embodiment of the present application provides a cell BWP setting method. When the BWP of the cell with the smallest cell identifier in the invalid FDRA field is switched to the first BWP, the second BWP is accurately set for the SCell according to the different bit lengths of the second field in the DCI under different BWPs, thereby improving communication efficiency.

The communication method and communication device are further described below in conjunction with the accompanying drawings. It is understandable that the present application uses a network device and a terminal as an example to illustrate the execution subject of the interaction diagram, but the present application does not limit the execution subject of the interaction diagram. For example, the method executed by the network device in the present application can also be implemented by a module in the network device (such as a circuit, chip or chip system, etc.), or a logical node, logic module or software that can realize all or part of the network device function; the method executed by the terminal in the present application can also be implemented by a communication module in the terminal or a circuit or chip in the terminal responsible for the communication function (such as a modem chip (also known as a baseband chip), or a SoC chip containing a modem core, or a SIP chip).

It can be understood that the network devices in the following embodiments may also be referred to as access network devices or base stations.

In the embodiments of the present application, the term "wireless communication" may also be referred to as "communication", and the term "communication" may also be described as "data transmission", "information transmission" or "transmission".

FIG6 is a schematic diagram of a method for setting a cell BWP according to an embodiment of the present application.

The communication process is applicable to but not limited to the communication scenario shown in Figure 1. The method may include the following steps:

S101: A network device configures a second BWP for a second cell.

In some embodiments, the network device may configure the corresponding second BWP for one or more second cells. For example, the second cell may be an SCell. In some examples, the second BWP may be any BWP used for communication, or the second BWP may be a BWP for which the terminal does not need to monitor the PDCCH. Among them, the BWP for which the terminal does not need to monitor the PDCCH may also be referred to as a dormant BWP. For the dormant BWP, the network device may configure the dormant BWP for the terminal device through RRC parameters or signaling, and the parameter RRC parameter or signaling may be a dormant BWP configuration (DormantBWP-Config). The index of the dormant BWP is configured through RRC parameters, such as a dormant BWP identifier (dormantBWP-Id). The network device configuring the second BWP for the second cell here can also be understood as the network device sending RRC signaling to the terminal to configure the second BWP for the second cell.

In other examples, the network device may further configure a first BWP for the third cell. The first BWP for the third cell may be a BWP different from the currently activated BWP of the third cell. For example, the first BWP may be referred to as a target BWP.

The third cell may be a cell with the smallest cell identifier among cells corresponding to each invalid FDRA field among multiple invalid frequency domain resource assignment (FDRA) fields. The invalid FDRA field may also be considered as an FDRA field having an invalid value. The number of invalid FDRA fields may be N, where N is an integer greater than 1.

In other examples, the network device may generate DCI for the first cell, where the DCI may include a first field and a second field. The first field may be used to indicate a first BWP for the third cell, and the second field may be used to indicate a second BWP for the second cell. For example, the first cell may be a PCell.

In each embodiment of the present application, "field" can also be understood as "information field" or "field", for example, the first field can be a BWP indication field.

In some examples, the first BWP indicated by the first field may be an identifier indicating the BWP. For example, the first field may directly indicate the index of the first BWP. In another example, the first field may indicate a sequence number or a value, where the sequence number corresponds to the index of the first BWP, or the value corresponds to the index of the first BWP. The first field may indirectly indicate the first BWP via the sequence number or the value.

For different BWPs, the network device can configure parameters related to the second field using radio resource control (RRC) parameters. These parameters can indicate the bit length of the second field. Therefore, the bit length of the second field can vary for different BWPs. In other words, the bit length of the second field can be determined based on the BWP-level RRC parameters.

S102: The network device sends the DCI of the first cell to the terminal.

Correspondingly, the terminal receives the DCI of the first cell sent by the network device.

S103: The terminal sets the BWP of one or more second cells as the second BWP according to the first bit length and/or the second bit length.

In some embodiments, the terminal may determine, based on the DCI received in S102, that the third cell requires BWP switching, i.e., that the currently active BWP of the third cell needs to be switched to the first BWP. In this case, considering that the second field may have different bit lengths depending on the BWP-level RRC parameter configuration, the terminal may parse the second field based on the first bit length and/or the second bit length to determine the second BWP corresponding to one or more second cells. For each second cell, the terminal sets the BWP of the second cell to the second BWP corresponding to the second cell.

The first bit length can be considered to be the bit length corresponding to the second field of the activated BWP of the third cell. The second bit length can be considered to be the length corresponding to the second field of the first BWP of the third cell. For RRC parameters of different BWP levels, the bit length of the second field determined based on the corresponding RRC parameters is generally different. Therefore, it can be considered that the first bit length is different from the second bit length. It is understandable that some second fields have the same bit length determined based on the RRC parameters configured for different BWP levels, while some second fields have different bit lengths determined based on the RRC parameters configured for different BWP levels. Of course, if the bit length of the second field is configured to be the same for RRC parameters of different BWP levels, the first bit length can be considered to be the same as the second bit length. The terminal can then directly parse the second field based on this same bit length to determine the second BWP corresponding to the second cell.

In some examples, the second field indicates the second BWP of the second cell, which can be indicated by different values. For example, "0" can be used to indicate that the second BWP of the second cell is set to a dormant BWP. In another example, "1" can be used to indicate that the second BWP of the second cell is set to a BWP used for communication, i.e., a non-dormant BWP. When the terminal is communicating within the non-dormant BWP of the second cell, i.e., the active downlink BWP of the second cell is not a dormant BWP, such as BWP#1, a bit of "1" in the second field can indicate that the terminal continues to communicate within the current active downlink BWP in the second cell, or it can be considered that the terminal does not switch BWPs in the second cell. When the active BWP of the second cell of the terminal is a dormant BWP, a bit of "1" in the second field can indicate that the active downlink BWP of the terminal in the second cell is the BWP configured by the first BWP identifier (firstWithinActiveTimeBWP-Id) within the activation time, indicating that the terminal switches from the dormant BWP to the BWP configured by firstWithinActiveTimeBWP-Id. FirstWithinActiveTimeBWP-Id can be an RRC parameter. The BWP configured with firstWithinActiveTimeBWP-Id can be considered the BWP used when the terminal switches from a dormant BWP to a communication BWP. Of course, the above is only an example of a possible relationship between a value and a second BWP. Any possible value can be used to establish a relationship with the second BWP based on actual circumstances, and this embodiment of the present application is not limited thereto. It should be understood that the following embodiments of this application will use the above relationship between the value and the second BWP as an example.

In some examples, if the terminal determines through analysis that the second BWP of the second cell is different from the current BWP of the second cell, the terminal switches the BWP of the second cell to the second BWP. Several situations may exist. In one case, the current BWP of the second cell is a BWP used for communication, which is not a dormant BWP, and the second field indicates that the second cell is "0." This means that the terminal will switch the current BWP of the second cell to a dormant BWP. In another case, the current BWP of the second cell is a dormant BWP, and the second field indicates that the second cell is "1." This means that the terminal will switch the current dormant BWP of the second cell to a BWP used for communication. This BWP used for communication may be the BWP configured by firstWithinActiveTimeBWP-Id.

In some examples, dormantBWP-Id and firstWithinActiveTimeBWP-Id can be configured through RRC parameters. If the terminal determines to switch the current active downlink BWP of the second cell to a dormant BWP, the terminal can set the dormant BWP corresponding to the identifier of the dormant BWP as the activated downlink BWP of the second cell. In this case, the terminal will not monitor the PDCCH of the second cell. Among them, the dormant BWP can be configured by the dormant BWP identifier (dormantBWP-Id). The dormantBWP-Id can be considered as an RRC parameter. If the terminal determines to switch the current dormant BWP of the second cell to a BWP used for communication, the terminal can set the BWP configured by firstWithinActiveTimeBWP-Id as the activated downlink BWP of the second cell.

For another example, if the terminal determines through analysis that the second BWP of the second cell is the same as the currently activated downlink BWP of the second cell, the terminal does not need to switch the activated downlink BWP of the second cell. There may be the following situations: in one case, the current BWP of the second cell is a BWP used for communication, and the BWP used for communication is not a dormant BWP, while the second field indicates that the second cell is "1." This means that the second cell is not dormant, and the terminal does not need to switch the current BWP of the second cell. In another case, the current BWP of the second cell is a dormant BWP, while the second field indicates that the second cell is "0." This means that the second cell needs to go to sleep, but since the current activated downlink BWP of the second cell is a dormant BWP, there is no need to switch the current activated downlink BWP of the second cell.

As can be seen, the second field can be considered to indicate whether the SCell is dormant. Switching between dormant and non-dormancy SCell behavior is achieved through the BWP switching described in the above example. For example, if the second field in the DCI indicates that a certain SCell is dormant, the terminal in that SCell needs to switch the currently active downlink BWP to the dormant BWP. After that, the terminal will no longer monitor the PDCCH in that SCell.

It is understood that the implementation process of each embodiment of the present application is implemented when the terminal is in the RRC connected state. It can also be considered that the terminal is implemented within the active time of the PCell.

It is worth noting that in each embodiment of the present application, the DCI indicates the BWP switching of a certain cell (or scheduled cell) or several cells (or scheduled cells), which means that the network device instructs the terminal to perform BWP switching on the certain cell (or scheduled cell) or several cells (or scheduled cells), but does not mean that the terminal has performed BWP switching. In other words, whether the terminal actually performs BWP switching may also refer to any other possible factors. For example, if the value of the FDRA field corresponding to the certain (scheduled) cell or several (scheduled) cells indicated by the DCI is an invalid value, then the BWP will not be switched from the activated BWP to the BWP indicated by the BWP indication field field in the DCI. The embodiments of the present application do not limit this.

In an embodiment of the present application, when the DCI indicates that the BWP of the third cell is switched to the first BWP indicated by the BWP indication domain field in the DCI, the second BWP can be accurately set for the second cell according to the different bit lengths of the second field under different BWPs, thereby improving communication efficiency.

In the cell BWP setting method provided in an embodiment of the present application, the DCI format is a DCI format for scheduling multiple cells. The DCI includes M FDRA fields. The FDRA field may also be referred to as a third field. The M FDRA fields may include N FDRA fields with invalid values. The second field is a field corresponding to the third cell. M is an integer greater than 1, and M is greater than or equal to N.

In some embodiments, the format of the DCI can also be a DCI format for scheduling one cell, for example, the DCI format is DCI format (format) 1_1 or the DCI format is DCI format 1_2. This type of DCI includes one FDRA field. The DCI is sent on the PCell, and the terminal device can detect the DCI on the PCell. The DCI does not contain a CIF field or the value of the included CIF field is 0, then the bit length corresponding to the field included in the DCI is determined according to the activation BWP of the PCell. When the value of the one FDRA field is an invalid value, the PCell can be considered to be the third cell, that is, the first cell is the third cell. The second field contained in the DCI is the field corresponding to the third cell, that is, the second field corresponding to the PCell.

In some embodiments, the DCI format is a DCI format used to schedule multiple cells. For example, the DCI format may be DCI format 1_3. That is, the DCI of the first cell may be DCI format 1_3. It will be understood that DCI format 1_3 is used to simultaneously schedule physical downlink shared channels of multiple cells. In other examples, the DCI format may be DCI format 1_1 or DCI format 1_2. That is, the DCI of the first cell may be used to schedule the physical downlink shared channel of one cell.

In some examples, the DCI may include M third fields. Among the M third fields, N third fields may have invalid values. That is, the value of at least one third field among the M third fields included in the DCI is an invalid value. It can be understood that one second field corresponds to one third field. Correspondingly, one second field corresponds to one cell, and one third field also corresponds to one cell, and the second field and the third field can be associated through the corresponding cells. For example, the third field is associated with SCell 1, and the second field is associated with SCell 1, then it can be considered that the third field has a corresponding relationship with the second field, or that the third field is associated with the second field.

For example, when M is 1, it means that there is one third field in the DCI, and the value of the third field can be an invalid value. The second field can be a field corresponding to the invalid third field. The terminal can directly set the BWP of the second cell based on the second field.

For another example, when M is greater than 1, it means that there are multiple third fields in the DCI, i.e., M third fields. Among the M third fields, N third fields may have invalid values. The terminal can then determine the cell identifier of the cell corresponding to each third field in the N third fields. The third cell is determined based on the multiple cell identifiers. For example, the third cell may be the cell with the smallest cell identifier among the multiple cell identifiers. The terminal can configure the BWP for the second cell based on the second field corresponding to the third cell. In some examples, the cell identifier may be, for example, a cell ID or a cell index.

The embodiment of the present application can be applied to a case where there are multiple invalid third fields, and accurately set the second BWP for the second cell to improve communication efficiency.

In the cell BWP setting method provided in the embodiment of the present application, the invalid value of the FDRA field can be defined as follows:

Method 1:

The resource allocation (RA) type is configured as type 0, and the FDRA field indicates all 0s.

In some examples, the third field can be considered to be the FDRA field. Then when the RA type is configured as type 0, the FDRA field indicates all 0s, which means that the cell corresponding to the third field is not allocated any frequency domain resources. Then the value of the third field can be considered to be an invalid value. Among them, the RA type of type 0 indicates that frequency domain resources are allocated with physical resource blocks as the granularity, which can indicate discrete frequency domain resources. In some examples, the RA type can be statically configured through the resource allocation (resourceAllocation) parameter. The resourceAllocation parameter can be considered as an RRC parameter. For example, the RA type configuration of type 0 can be indicated by resourceAllocationType0.

Method 2:

The RA type is configured as type 1, and the FDRA field indicates all 1s.

In some examples, the FDRA field indicates all 1s, which means that complete frequency domain resources are allocated to the cell corresponding to the third field. Considering that complete frequency domain resources usually exceed the frequency domain resources of the BWP of the cell in the third field, when the RA type is configured as type 1 and the FDRA field indicates all 1s, the value of the third field can also be considered to be invalid. Among them, the RA type of type 1 indicates that continuous resources are allocated. For example, the RA type configuration of type 1 can be indicated by resourceAllocationType1.

Method 3:

The RA type is configured as the dynamic resource allocation type, and the FDRA field indicates all 0s or all 1s.

In some examples, the RA type configuration may be a dynamic switching resource allocation type. For example, the RA type may be statically configured as dynamic through the dynamic switching (dynamicSwitch) parameter. The dynamicSwitch parameter may be considered as an RRC parameter. In this case, the RA type in this DCI scheduling may be indicated as type 0 or type 1 based on the third field in the DCI, that is, the highest bit of the FDRA field. Then, when the FDRA field indicates all 0s, it may be considered similar to method 1; when the FDRA field indicates all 1s, it may be considered similar to method 2. That is to say, when the RA type is configured as a dynamic switching resource allocation type, and the FDRA field indicates all 0s or all 1s, the value of the third field may be considered to be an invalid value.

This application provides multiple ways to define the value of the third field as an invalid value, which can be applied to different scenarios, so that the invalid third field can be accurately known, and the BWP can be configured for the second cell according to the second field corresponding to the invalid third field.

In the cell BWP setting method provided in an embodiment of the present application, the second field includes at least one of the following fields: a modulation and coding scheme (MCS) field; a new data indicator (NDI) field; a redundancy version (RV) field; a hybrid automatic repeat request process number (HPN) field; or an antenna port (AP) field. It can also be understood that the second field is a field formed by concatenating a bit sequence of at least one of the above fields.

In some examples, the MCS field may be the MCS of transport block (TB) 1. The NDI field may be the NDI field of TB 1. The RV field may be the RV field of TB 1.

In some examples, the second field may include an MCS field. For another example, the second field may include an MCS field and an RV field. For another example, the second field may include an MCS field, an NDI field, and an RV field. For another example, the second field may include an MCS field, an NDI field, an RV field, and an AP field. For another example, the second field may include an MCS field, an NDI field, an RV field, an HPN field, and an AP field. It is understood that the second field may include any two, three, or four of the above fields, and the embodiments of the present application are not limited thereto.

In some examples, when the second field includes an AP field, the AP field is configured as type 2 (type 2) through antenna port DCI1_3 (antennaPortsDCI1-3) or antenna port DCI0_3 (antennaPortsDCI0-3). Among them, antennaPortsDCI1-3 and antennaPortsDCI0-3 can be considered as RRC parameters. This is because, when the RRC parameter configures the AP field as type 2, it means that the AP field is only used for the cell corresponding to the second field. For example, if the RRC parameter configures the AP field as type 1a, it means that the AP field may be shared by multiple cells. If the AP field is used to indicate the sleep status of the SCell, it will affect the data transmission of other cells.

It can be understood that the various second fields provided above are valid when the third field is valid, that is, when the value of the third field is not satisfied as an invalid value, the second field can be used to set the data transmission in the cell corresponding to the second field. When the value of the third field is an invalid value, the terminal does not monitor the PDCCH in the corresponding cell, which means that the terminal does not perform data transmission on the corresponding cell, or that the cell has no data scheduling. Then the second field used to set data transmission can be used for reinterpretation, such as for setting the sleep status of one or more SCells. Therefore, the second field in the above embodiments can also be called a reinterpretation field, a reinterpretation domain, a specific domain, etc.

It can be understood that the above-mentioned second field for reinterpretation can be used to indicate whether the SCell is dormant when the value of the third field is an invalid value. For example, a bit in the second field can be used to set the dormant status of an SCell. For example, if the bit is "0", it can indicate that the SCell is dormant. For another example, if the bit is "1", it can indicate that the SCell is not dormant. The process of the terminal setting the BWP of the corresponding SCell according to the bit can refer to the above-mentioned related embodiments, and the embodiments of the present application will not be repeated here.

In some examples, the second field can be mapped to the SCell identifier from the smallest to the largest, in descending order. That is, the mapping is performed sequentially from the most significant bit (MSB) to the least significant bit (LSB) in the second field, from the smallest SCell identifier to the largest SCell identifier. For example, as shown in FIG7 , assume there are five second fields, namely, second field 1 to second field 5. These five second fields are arranged in sequence. It can be seen that the MSB of these five second fields corresponds to an SCell identifier of 0, that is, the MSB is used to indicate an SCell with an SCell identifier of 0. The adjacent bit of the MSB of the second field corresponds to an SCell identifier of 1, that is, the bit is used to indicate an SCell with an SCell identifier of 1. This continues in this manner until the LSB of the second field corresponds to an SCell identifier of X, that is, the LSB is used to indicate an SCell with an SCell identifier of X. X is the maximum value in the SCell identifier. X is a positive integer greater than or equal to 0.

In other embodiments, considering that the second field is a field for reinterpretation, and these second fields may be reinterpreted for other purposes in other scenarios, to prevent these fields from being interpreted as multiple meanings at the same time, in the embodiment of the present application, when the second field is used to indicate the second BWP of the second cell, the first condition must also be met.

The first condition may be that a one-shot hybrid automatic repeat request acknowledgment (HARQ-ACK) request field does not exist in the DCI, or the field is set to 0. It is understood that when the field exists in the DCI or is not 0, the second field in the above embodiment may be reinterpreted to have other meanings.

In some embodiments, the bit length of the various possible second fields mentioned above can be determined according to the RRC parameters at the BWP level. For example, the RV field can be divided into 0 bits, 1 bits, or 2 bits according to the influence of the RRC parameter numberOfBitsForRV-DCI-1-3 at the BWP level. For another example, the HPN field can be divided into 0 bits, 1 bits, 2 bits, 3 bits, 4 bits, or 5 bits according to the influence of the RRC parameter harq-ProcessNumberSizeDCI-1-3 at the BWP level. For another example, the AP field can be divided into 4 bits, 5 bits, or 6 bits according to the influence of the RRC parameters dmrs-Type and maxLength at the BWP level. For different BWPs, refer to Table 1 for the situations in which the second fields in the above 5 may vary with different BWPs.

Table 1

It can be seen that, for example, the number of bits of the MCS field and the NDI field may not change with different BWPs, that is, may be fixed.

The embodiment of the present application provides multiple fields that can be used to indicate the second BWP, so that one or more of the multiple fields can be used to set the BWP of the second cell in different scenarios, thereby improving universality.

In the cell BWP setting method provided in the embodiment of the present application, considering that the bit length of the second field may vary with different BWPs, in the scenario where the network device instructs the terminal to switch the BWP of the first cell, the bit length of the second field corresponding to different BWPs may be different, which will cause the terminal to have different understandings of the second field during the BWP switching process.

In some embodiments, as shown in Figure 8 , if a cell needs to switch from an active BWP to a target BWP indicated by the BWP indication field, the bit length of the DCI for the active BWP may be shorter than the bit length of the DCI for the target BWP. To do so, the bit length of the DCI received in the active BWP can be aligned with the corresponding bit length of the DCI in the target BWP by prepending zeros to the upper bits, and the terminal then parses the DCI. As shown in Figure 9 , if a cell needs to switch from an active BWP to a target BWP, the bit length of the DCI received in the active BWP may be longer than the corresponding bit length of the DCI in the target BWP. To do so, the DCI can be parsed by parsing one or more LSBs. The number of LSBs to be parsed can be determined by reference to the bit length of the DCI in the target BWP. The target BWP can be understood as the indicated BWP indicated by the BWP indication field in the DCI, when the BWP indicated by the BWP indication field in the DCI is different from the current active BWP. The BWP indicated by the BWP indication field may be an indicated activated downlink BWP or an indicated activated uplink BWP.

If the second field in the DCI is parsed according to the bit length of the second field in the target BWP indicated by the BWP indication field, the network device may not want some cells to be put into sleep mode. However, due to changes in the bit length of the second field, such as when padding with "0s," the padded "0" bits will indicate that the BWP of the corresponding cell has switched to the sleep BWP, thereby indicating that the cell is in sleep mode. As shown in Figure 10, under an activated BWP, each bit in the five second fields corresponds to an SCell. This means that the sleep status of the corresponding SCell can be indicated by each bit. However, under a target BWP, the bit length of some second fields may change due to the RRC parameter configuration of the target BWP. For example, the bit length of second fields 3, 4, and 5 may change. In this case, the terminal can pad the second field with "0s" to complete the bit length. As can be seen, after the second field is padded with "0s," the bits corresponding to the SCell identifier, from the lowest bit to the lowest bit, are aligned. The bits corresponding to SCells 6 through 12 are obviously different from those corresponding to the activated BWP. In particular, the SCells corresponding to the bits padded with "0" may have been originally configured by the network device to not sleep. However, due to the bit length of the second field under the target BWP, these SCells are forced to sleep, thus affecting data communication. The target BWP mentioned above can be the first BWP mentioned above, that is, the BWP indicated by the BWP indication field in the DCI.

It should be noted that in each embodiment of the present application, the bit length of the second field of a certain BWP can be understood as the bit length of the second field in the received DCI when the BWP is communicating. Then, the first bit length mentioned in each embodiment of the present application can be understood as the bit length of the second field in the received DCI in the activated BWP of the third cell. The second bit length mentioned in each embodiment of the present application can be understood as the bit length of the second field in the received DCI in the first BWP of the third cell.

In some embodiments, the terminal may set the BWP of the second cell to the second BWP based on the first bit length. For example, when the terminal receives DCI from the first cell indicating that the BWP of the third cell needs to be switched to the first BWP, the terminal may determine the second BWP of the second cell indicated by the second field based on the bit length of the second field in the DCI received in the third cell's currently active BWP. The terminal then configures the BWP of the second cell to the second BWP corresponding to the second cell. The bit length of the second field in the DCI received in the active BWP of the third cell is the first bit length. It is understood that the terminal determines the second BWP of the second cell indicated by the second field based on the first bit length. It can be considered that the terminal does not consider the case where the second field is padded with "0" after the BWP is switched to the BWP indicated by the BWP indication field in the DCI.

Referring to FIG. 11 , it is assumed that the first cell is a PCell and the second cell is an SCell. The terminal receives DCI on the PCell. The DCI format may be DCI format 1_3. The first field in the DCI, such as the BWP indication field, indicates the first BWP of the third cell. The first BWP of one or more scheduled cells indicated by the DCI can be considered to indicate that the activated BWP of the indicated one or more scheduled cells has been switched to the first BWP. If the activated BWP of one of the indicated one or more scheduled cells is the same as the first BWP, the cell does not need to perform BWP switching and continues to communicate or sleep on the current activated BWP of the cell. If the activated BWP of a scheduled cell is different from the first BWP, the terminal device parses the field corresponding to the cell in the DCI based on the RRC parameter configuration of the first BWP of the cell. The DCI includes at least one FDRA field with an invalid value. Among the cells corresponding to the at least one invalid FDRA field, the cell with the smallest cell index is the third cell. For example, the DCI indicates four scheduled cells: PCell, SCell#1, SCell#2, and SCell#3. The FDRA fields corresponding to SCell#2 and SCell#3 are invalid, while the FDRA fields corresponding to PCell and SCell#1 are valid. Of the two, SCell#2 and SCell#3 have the smallest cell index, making SCell#2 the third cell.

If the BWP indicated by the BWP indication field is different from the currently activated BWP of the third cell, the terminal can determine the second BWP of the second cell indicated by the second field according to the bit length corresponding to the second field under the activated BWP before the BWP of SCell#2 is switched. For example, the terminal can determine the bitmap according to the first bit length of the second field of the activated BWP. It can be seen that when the terminal parses the second field in the DCI, it parses it according to the second field of the activated BWP. There is no "0" padding. That is to say, when the BWP indicated by the BWP indication field in the DCI is different from the activated BWP of the third cell, the terminal's parsing method for the second field in the DCI remains unchanged.

Among them, the bit map can represent the correspondence or mapping relationship between each bit in the second field and the SCell. The terminal determines the bit length corresponding to each second field based on the RRC parameters of the activated BWP of the third cell. Assume that the second field 1 is the MCS field, the second field 2 is the NDI field, the second field 3 is the RV field, the second field 4 is the HPN field, and the second field 5 is the AP field. Assume that in the DCI sent by the network device, the second field indicates 11 SCells. When the terminal communicates on the activated BWP of the third cell, the correspondence between each bit in the MCS field, NDI field, RV field, HPN field and AP field and the SCell can refer to the correspondence before the BWP switching in Figure 11. When the first field indicates that the first BWP of the third cell is different from the activated BWP of the third cell, it indicates that the activated BWP of the third cell needs to be switched to the first BWP.

In this case, the terminal can still parse the second field of the activated BWP to determine the correspondence between each bit of the second field and the SCell, thereby determining whether the corresponding SCell is dormant. As shown in Figure 11, the parsing method of the second field of the target BWP indicated by the BWP indication field in the DCI is the same as the parsing method of the second field of the activated BWP. Based on this correspondence, the terminal can determine the second BWP corresponding to each SCell indicated by the second field, and set the activated BWP of each SCell to the second BWP. For example, set the corresponding SCell to a dormant state or a non-dormant state. Among them, the dormant state indicates that the BWP of the SCell is a dormant BWP; the non-dormant state indicates that the activated BWP of the SCell is a non-dormant BWP, such as the BWP of any possible terminal monitoring PDCCH.

Referring to Figure 12 , which is similar to Figure 11 , the difference is that in Figure 12 , the terminal parses the second field of the DCI according to the bit length of the target BWP's DCI. However, the terminal still interprets the second field of the DCI according to the bit length of the second field of the activated BWP. In other words, although the terminal parses the DCI according to the DCI length of the target BWP indicated by the BWP indicator field in the DCI, it interprets the second field according to the first bit length of the activated BWP. Zero padding introduced during the DCI parsing process is not considered.

For example, the terminal can determine the bitmap based on the first bit length of the second field of the activation BWP. The terminal determines the bit length corresponding to each second field based on the RRC parameters of the activation BWP of the third cell. When the first BWP indicated by the first field is different from the activation BWP of the third cell, that is, when the activation BWP of the third cell is switched to the first BWP, the terminal can still determine whether the corresponding SCell is dormant based on the correspondence between the bits of the second field and the SCell before the BWP switch. As shown in Figure 12, the correspondence between the bits of the second field corresponding to the target BWP and the SCell is the same as before the BWP switch. Zero padding introduced during DCI parsing is not considered. Based on this correspondence, the terminal can determine the second BWP corresponding to each SCell indicated by the second field and set the activation BWP of each SCell to the second BWP. For example, this can set the corresponding SCell to a dormant or non-dormant state.

11 and 12, the terminal still parses the second field according to the bit length of the second field of the activated BWP before the BWP switching. The terminal does not consider whether "0" is added before and after the BWP switching.

Of course, Figure 12 only illustrates the case where the second field length changes from a shorter length to a longer length after a BWP switch. In other examples, the second field length changes from a longer length to a shorter length after a BWP switch. The terminal can parse the second field according to the bit length of the second field before the BWP switch. It will be appreciated that when a terminal receives the DCI within the PCell, the terminal device is communicating or sleeping within the activated BWP of each scheduled cell indicated by the DCI. Therefore, the actual length of the second field corresponding to the third cell in the DCI is still the bit length of the second field determined based on the activated BWP of the third cell.

The embodiment of the present application allows the terminal and the network device to uniformly parse the second field according to the bit length of the second field before the BWP switching, thereby avoiding the situation where the network device and the terminal misunderstand the second BWP set for the second cell, thereby improving communication efficiency.

In other embodiments, when the terminal parses the second field according to the first bit length, if the second field changes from more to less after the BWP is switched, the terminal can also set the BWP of the second cell to the second BWP based on the second number of LSBs in the second field. The second number is the same as the second bit length. It should be noted that the second field involved in each embodiment of the present application changes from more to less, or from less to more. This can be understood as the number of bits (or bit length, number of bits, etc.) of the second field changing from more to less, or the number of bits (or bit length, number of bits, etc.) of the second field changing from less to more. Of course, in some examples, some second fields can be indicated as 0 bits through the RRC parameters at the BWP level. In this case, the second field can also be considered non-existent. In this case, it can also be considered that the number of second fields changes from more to less, or the number of second fields changes from less to more.

For example, assuming the first bit length of the second field is 5 bits and the second bit length of the second field is 3 bits, if the terminal parses the second field according to the first bit length, it can parse the second field based on the three least significant bits (LSBs) of the five bits to determine the second BWP of the SCell indicated by each of the three LSBs. The terminal then sets the BWP of the corresponding SCell to the second BWP based on the parsing result of the second field.

The embodiment of the present application can also be applicable to the case where the first bit length is greater than the second bit length. In this case, the terminal can accurately determine the second BWP of the second cell based on the second number of LSBs in the first bit length to improve communication efficiency.

In some further embodiments, when the first bit length is less than the second bit length, the terminal may set the BWP of the second cell to the second BWP based on the first number of LSBs in the second field of the first BWP. The first number is the same as the first bit length. For example, if the terminal receives DCI in the first cell indicating that the BWP of the third cell needs to be switched to the first BWP, the terminal may determine the second BWP of the second cell indicated by the second field based on the second bit length. The second bit length is the bit length of the second field of the DCI in the first BWP of the third cell. The terminal sets the BWP of the second cell to the second BWP corresponding to the second cell. If the first bit length is less than the second bit length, the terminal may determine the BWP of the second cell indicated by the second field based on the first number of LSBs in the second bit length.

It can be considered that in this example, the terminal considers the case where the second field is padded with "0" after indicating the BWP switching of the third cell, and parses it according to the target BWP. It can be understood that in this case, it only means that the DCI indicates that the third cell is to perform BWP switching, but the third cell may not actually switch to the BWP indicated by the BWP indication domain field in the DCI. Of course, whether the third cell actually performs BWP switching can also refer to any other conditions that may need to be considered, and the embodiments of the present application are not limited here. In this case, the terminal can parse the second field based on the LSB of the first number, and the first number is the same as the first bit length. Therefore, when the first bit length is less than the second bit length, it can be considered that although the terminal parses according to the second bit length, it will ignore (ignore) or skip (skip) the "0" bit in the second field.

Referring to Figure 13, the scenario is similar to that shown in Figure 12, except that after the terminal determines that the indicated first BWP is different from the activated BWP, the terminal determines the second BWP of the second cell indicated by the second field based on the bit length corresponding to the second field under the target BWP. If the first bit length is less than the second bit length, the terminal will also consider the first bit length as the first number and select the LSB of the first number in the second field for parsing to determine the BWP of the second cell indicated by the second field.

For example, the terminal may determine the bitmap according to the first bit length of the second field of the activated BWP and the second bit length of the second field of the first BWP.

The terminal determines the bit length corresponding to each second field, i.e., the first bit length, based on the RRC parameters of the activated BWP of the third cell. The terminal may use the first bit length as the first quantity. The terminal may also determine the bit length corresponding to each second field, i.e., the second bit length, based on the RRC parameters of the first BWP of the third cell. Similar to Figure 12 , the second field in the DCI sent by the network device in Figure 13 indicates 11 SCells. The second fields are similar to those in Figure 12 and will not be described in detail in this embodiment of the present application. When the first field indicates that the first BWP of the third cell is different from the activated BWP of the third cell, that is, when the first field indicates that the activated BWP of the third cell needs to be switched to the first BWP, the correspondence between the bits of the second fields in the activated BWP and the SCells can refer to the correspondence before the BWP switching in Figure 13 . In this case, the terminal can determine whether the corresponding SCell is dormant based on the correspondence between the bits of the second field and the SCell after the BWP switching. If the first bit length is less than the second bit length, the correspondence between the bits of the second field corresponding to the target BWP and the SCell is as shown in Figure 13 . As can be seen, the terminal parses the first number of LSBs in the second bit length of the second field according to the first bit length. For example, if the first bit length of second field 3 is 1 bit and the second bit length of second field 3 is 2 bits, the terminal parses one LSB of the two bits. Referring to second field 5 in Figure 13 , the first bit length of second field 5 is 4 bits, and the second bit length of second field 5 is also 4 bits. Before BWP switching, the first three bits (or three MSBs) of second field 5 are actually used to indicate three SCells. In this solution, the terminal parses the second field according to the second bit length and parses the three LSBs in second field 5 to determine the second BWP of the corresponding SCell. Based on the determined second BWP, the terminal can configure each SCell, namely, configure the corresponding SCell to a dormant or non-dormant state.

It can be seen that in this case, although part of the second field needs to be padded with "0" bits, the terminal still ignores or skips the bits padded with "0".

Of course, Figure 13 only shows the situation where the second field changes from less to more after the BWP is switched. In other examples, for the situation where the second field changes from more to less after the BWP is switched. The terminal can parse the second field according to the bit length of the second field after the BWP is switched. In this case, when configuring the second field to indicate the SCell, the network device will avoid configuring the number of SCells to exceed the second bit length of the second field, so as to avoid the situation where some SCells cannot be indicated due to the reduction of the bit length of the second field. In this scenario, the terminal can directly configure the second BWP for the second cell based on the second bit length. It can also be considered that the terminal does not expect (does not expect) the situation where some SCells cannot be indicated due to the DCI indicating BWP switching, that is, the terminal does not expect the situation where some SCells do not correspond to the bits of the second field. In each embodiment of the present application, DCI indicating BWP switching can be understood as that the BWP indicated by the BWP indication field in the DCI is different from the activated BWP of the third cell.

This embodiment of the present application allows the terminal and network device to uniformly parse the second field of the BWP indicated by the BWP indication field in the DCI according to the bit length of the second field. If the first bit length is less than the second bit length, the terminal can accurately determine the second BWP of the second cell based on the first number of LSBs in the second bit length. This can avoid misunderstandings between the network device and the terminal regarding the second BWP set for the second cell, thereby improving communication efficiency.

In other embodiments, when the first bit length is less than the second bit length, the BWP of the second cell may be set to the second BWP according to the first bit length. When the first bit length is greater than the second bit length, the BWP of the second cell may be set to the second BWP according to the second bit length. For the specific implementation process, please refer to the description of the relevant embodiments of Figures 10, 11, and 12, and the embodiments of this application will not be repeated here.

In the cell BWP setting method provided in the embodiment of the present application, the DCI may further include at least one third field as a valid field. For example, when the third field is an FDRA field, the DCI may include at least one valid FDRA field.

In the above embodiments of the present application, the DCI that can be sent by the network device can ensure that one cell will not be instructed to sleep at the same time, or scheduled to receive PDSCH and/or send PUSCH.

In the cell BWP setting method provided in an embodiment of the present application, if the first field in the DCI sent by the network device indicates the first BWP of the first cell, or the first field indicates the first BWP of the third cell. In this case, the terminal can ignore the second BWP of the second cell indicated by the second field in the DCI. For example, the terminal can ignore the SCell dormancy indication when the PCell switching activation BWP is indicated as the first BWP, or when the first field of the DCI indicates that the DCI indicates the first BWP of all scheduled cells. The terminal can ignore the invalid third field and ignore the second field corresponding to the third cell.

Another possible implementation method is that in the DCI sent by the network device, the first field indicates the first BWP of the first cell, or the first field indicates the first BWP of the third cell. In this case, the terminal can ignore the first BWP indicated by the first field in the DCI. That is to say, when the terminal receives the DCI, if the value of the FDRA field corresponding to one or more scheduled cells indicated by the DCI is an invalid value, the terminal can ignore the first field. It can be understood that in this case, the terminal sets the second BWP of the second cell according to the second field in the DCI. The terminal does not switch from the activated BWP to the BWP indicated by the first field on the scheduled cell or multiple scheduled cells indicated by the DCI based on the first field of the DCI. In other words, the terminal may not perform BWP switching of the third cell, but perform setting of the BWP of the second cell.

Another possible implementation is that the network device indicates SCell sleep through the second field of the DCI, and the network device indicates BWP switching through the first field of the DCI cannot exist at the same time. The terminal does not expect to receive a DCI, the first field of which indicates the first BWP, and the value of the FDRA field corresponding to the scheduled cell or multiple scheduled cells indicated by the DCI is an invalid value. In some examples, if the terminal receives this type of DCI, the terminal may not process the DCI, or the terminal may discard (drop or discard) the DCI, or the terminal may consider the DCI to be an erroneous (false or error) DCI. In other words, the DCI sent by the network device does not consider indicating SCell sleep and indicating BWP switching of one or more cells at the same time. Of course, for the terminal, it does not expect to receive this type of DCI.

It can be understood that the above-described embodiments of this application solve the problem of different interpretations of bits in the reinterpretation field between terminals and network devices, which leads to data transmission failures and inability to reduce terminal power consumption. This improves data communication efficiency, reduces terminal power consumption, and enhances the robustness of downlink communications. It also clarifies the parsing method for the reinterpretation field used to indicate SCell dormancy in the PCell BWP switching scenario, as well as the mapping relationship between each bit in the reinterpretation field and the SCell.

It is understood that, in order to implement the functions in the above embodiments, the base station and the terminal include hardware structures and/or software modules corresponding to the execution of each function. Those skilled in the art should readily appreciate that, in conjunction with the units and method steps of the various examples described in the embodiments disclosed in this application, this application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in hardware or in a computer software-driven hardware manner depends on the specific application scenario and design constraints of the technical solution.

Figures 14 and 15 are schematic diagrams of the structures of possible communication devices provided in embodiments of the present application. These communication devices can be used to implement the functions of the terminal or base station in the above method embodiments, and thus can also achieve the beneficial effects possessed by the above method embodiments. In the embodiments of the present application, the communication device can be the terminal 120 as shown in Figure 1, or the base station 110 as shown in Figure 1, or a module (such as a chip) applied to a terminal or base station.

As shown in Figure 14, a communication device 1400 includes a processing unit 1410 and a transceiver unit 1420. The communication device 1400 is used to implement the functions of a terminal or a base station in the method embodiment shown in Figure 6 above.

When the communication device 1400 is used to implement the functions of the terminal in the method embodiment shown in Figure 6: the transceiver unit 1420 is used to receive the DCI of the first cell; the processing unit 1410 is used to set the BWP of the second cell to the second BWP according to the first bit length and/or the second bit length.

When the communication device 1400 is used to implement the function of the base station in the method embodiment shown in FIG6 : the processing unit 1410 is used to configure the second BWP for the second cell; and the transceiver unit 1420 is used to send the DCI of the first cell.

For a more detailed description of the processing unit 1410 and the transceiver unit 1420 , reference may be made to the method embodiment shown in FIG6 and the related descriptions of the embodiments in FIG7 to FIG13 .

As shown in Figure 15, communication device 1500 includes a processor 1510 and an interface circuit 1520. Processor 1510 and interface circuit 1520 are coupled to each other. It is understood that interface circuit 1520 can be a transceiver or an input/output interface. Optionally, communication device 1500 may also include a memory 1530 for storing instructions executed by processor 1510, or storing input data required by processor 1510 to execute instructions, or storing data generated after processor 1510 executes instructions. Sometimes, interface circuit 1520 can also be understood as part of processor 1510, in which case communication device 1500 includes processor 1510.

When the communication device 1500 is used to implement the method shown in FIG6 , the processor 1510 is used to implement the functions of the processing unit 1410 , and the interface circuit 1520 is used to implement the functions of the transceiver unit 1420 .

When the above-mentioned communication device is a chip applied to a terminal, the terminal chip implements the functions of the terminal in the above-mentioned method embodiment. When the terminal chip receives information from the base station, it can be understood that the information is first received by other modules in the terminal (such as a radio frequency module or antenna) and then sent to the terminal chip by these modules. When the terminal chip sends information to the base station, it can be understood that the information is first sent to other modules in the terminal (such as a radio frequency module or antenna) and then sent to the base station by these modules.

When the above-mentioned communication device is a chip applied to a base station, the base station chip implements the functions of the base station in the above-mentioned method embodiment. When the base station chip receives information from the terminal, it can be understood that the information is first received by other modules in the base station (such as a radio frequency module or antenna) and then sent to the base station chip by these modules. When the base station chip sends information to the terminal, it can be understood that the information is sent to other modules in the base station (such as a radio frequency module or antenna) and then sent to the terminal by these modules.

In this application, when entity A sends information to entity B, it can be done directly from A to B or indirectly through another entity. Similarly, when entity B receives information from entity A, it can be done directly from entity B or indirectly through another entity. Entities A and B herein can be RAN nodes or terminals, or modules within a RAN node or terminal. The sending and receiving of information can be information exchange between a RAN node and a terminal, for example, between a base station and a terminal; the sending and receiving of information can also be information exchange between two RAN nodes, for example, between a CU and a DU; the sending and receiving of information can also be information exchange between different modules within a device, for example, between a terminal chip and other modules in the terminal, or between a base station chip and other modules within the base station.

It is understood that the processor in the embodiments of the present application may be a central processing unit, or may be other general-purpose processors, digital signal processors, application-specific integrated circuits, field programmable gate arrays or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. The general-purpose processor may be a microprocessor or any conventional processor.

The method steps in the embodiments of the present application can be implemented in hardware or in software instructions that can be executed by a processor. The software instructions can be composed of corresponding software modules, and the software modules can be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, registers, hard disk, mobile hard disk, CD-ROM or any other form of storage medium well known in the art. An exemplary storage medium is coupled to the processor so that the processor can read information from the storage medium and write information to the storage medium. The storage medium can also be an integral part of the processor. The processor and storage medium can be located in an ASIC. In addition, the ASIC can be located in a base station or a terminal. The processor and storage medium can also exist in a base station or a terminal as discrete components.

In the above embodiments, all or part of the embodiments may be implemented using software, hardware, firmware, or any combination thereof. When implemented using software, all or part of the embodiments may be implemented in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are performed in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user device, or other programmable device. The computer program or instructions may be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program or instructions may be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or data center that integrates one or more available media. The available medium may be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; an optical medium, such as a digital video disk; or a semiconductor medium, such as a solid-state drive. The computer-readable storage medium may be a volatile or nonvolatile storage medium, or may include both volatile and nonvolatile types of storage media.

In the various embodiments of the present application, unless otherwise specified or there is a logical conflict, the terms and/or descriptions between different embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

In this application, "at least one" means one or more, and "more" means two or more. "And/or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and/or B can mean: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. In the text description of this application, the character "/" generally indicates that the previous and next associated objects are in an "or" relationship; in the formula of this application, the character "/" indicates that the previous and next associated objects are in a "division" relationship. "Including at least one of A, B and C" can mean: including A; including B; including C; including A and B; including A and C; including B and C; including A, B and C.

It is understood that the various numbers used in the embodiments of this application are merely for ease of description and are not intended to limit the scope of the embodiments of this application. The order of the sequence numbers of the above-mentioned processes does not necessarily imply a specific order of execution; the order of execution of the processes should be determined by their functions and inherent logic.

In this application, a base station sends downlink signals or downlink information to a terminal, and the downlink information is carried on a downlink channel; the terminal sends uplink signals or uplink information to the base station, and the uplink information is carried on an uplink channel. In order to communicate with the base station, the terminal needs to establish a wireless connection in the cell controlled by the base station. The cell with which the terminal has established a wireless connection is called the serving cell of the terminal. When the terminal communicates with the serving cell, it will also be interfered with by signals from neighboring cells.

The network architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Ordinary technicians in this field will know that with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

The terms "first" and "second" in the description and drawings of the embodiments of the present application are used to distinguish different objects, or to distinguish different treatments of the same object. Words such as "first" and "second" can distinguish between identical or similar items with substantially the same functions and effects. For example, the first device and the second device are merely used to distinguish different devices and do not limit their order. Those skilled in the art will understand that words such as "first" and "second" do not limit the quantity and execution order, and words such as "first" and "second" do not necessarily limit differences.

Furthermore, the terms "including," "having," and any variations thereof, mentioned in the description of the embodiments of the present application are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or apparatus comprising a series of steps or units is not limited to the listed steps or units, but may optionally include other steps or units not listed, or may optionally include other steps or units inherent to the process, method, product, or apparatus.

In the embodiments of this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of this application should not be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner to facilitate understanding.

It will be understood that the “embodiment” mentioned throughout the specification means that the specific features, structures or characteristics related to the embodiment are included in at least one embodiment of the embodiment of the present application. Therefore, the various embodiments in the entire specification do not necessarily refer to the same embodiment. In addition, these specific features, structures or characteristics can be combined in one or more embodiments in any suitable manner. It will be understood that in the various embodiments of the embodiment of the present application, the size of the sequence number of each process does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present application.

It can be understood that in the embodiments of the present application, "when" and "if" both mean that corresponding processing will be performed under certain objective circumstances, and do not limit the time, nor do they require any judgment action when implementing, nor do they mean that there are other limitations.

It is understood that some optional features in the embodiments of the present application may, in certain scenarios, be implemented independently of other features, such as the solution on which they are currently based, to solve corresponding technical problems and achieve corresponding effects. In certain scenarios, they may also be combined with other features as needed. Accordingly, the devices provided in the embodiments of the present application may also implement these features or functions accordingly, which will not be described in detail here.

In the embodiments of the present application, unless otherwise specified, the same or similar parts between the various embodiments can refer to each other. In the various embodiments of the present application, and the various implementation methods/implementation methods/implementation methods in the various embodiments, if there is no special explanation and logical conflict, the terms and/or descriptions between different embodiments and the various implementation methods/implementation methods/implementation methods in the various embodiments are consistent and can be referenced to each other. The technical features in different embodiments and the various implementation methods/implementation methods/implementation methods in the various embodiments can be combined to form new embodiments, implementation methods, implementation methods, or implementation methods according to their inherent logical relationships. The implementation methods of the embodiments of the present application described below do not constitute a limitation on the scope of protection of the embodiments of the present application.

Claims (15)

A method for setting a portion of a cell bandwidth, characterized in that the method comprises: Receive downlink control information DCI of a first cell, where the DCI includes a first field and a second field, where the first field is used to indicate a first bandwidth part BWP of a third cell, and the second field is used to indicate a second BWP of the second cell, where the first BWP is different from an activated BWP of the third cell, a first bit length of the second field is different from a second bit length of the second field of the first BWP, and the third cell is a cell with a smallest cell identifier among N cells corresponding to N frequency domain resource allocation FDRA fields, values of the N FDRA fields are invalid values, and N is an integer greater than 1; The BWP of the second cell is set to the second BWP according to the first bit length and/or the second bit length. The method according to claim 1 is characterized in that the format of the DCI is a DCI format for scheduling multiple cells, and the DCI includes M FDRA fields, wherein the M FDRA fields include the N FDRA fields whose values are invalid values, and the second field is a field corresponding to the third cell, wherein M is an integer greater than or equal to N. The method according to claim 1 or 2, wherein the first bit length is less than the second bit length, and setting the BWP of the second cell to the second BWP according to the first bit length and/or the second bit length includes: The BWP of the second cell is set to the second BWP according to a first number of least significant bits in a second field of the first BWP, the first number being the same as the first bit length. The method according to claim 1 or 2, wherein the first bit length is greater than the second bit length, and setting the BWP of the second cell to the second BWP according to the first bit length and/or the second bit length includes: The BWP of the second cell is set to the second BWP according to a second number of least significant bits in the second field, wherein the second number is the same as the second bit length. The method according to any one of claims 1 to 4, wherein the second field includes at least one of the following fields: Modulation and coding scheme MCS field; New data indication NDI field; Redundancy version RV field; Hybrid Automatic Repeat Request Process Number HPN field; or Antenna port AP field, wherein the radio resource control RRC parameter configuration said AP field is type 2. The method according to any one of claims 1 to 5, wherein the value of the FDRA field is defined as an invalid value in the following manner: The resource allocation RA type is configured as type 0, and the FDRA field indicates all 0s; or, The RA type is configured as type 1, and the FDRA field indicates all 1s; or The RA type is configured as a dynamic switching resource allocation type, and the FDRA field indicates all 0s or all 1s. A method for setting a portion of a cell bandwidth, characterized in that the method comprises: Configuring a second BWP for the second cell; Send downlink control information DCI of the first cell, the DCI including a first field and a second field, the first field is used to indicate the first BWP of the third cell, the second field is used to indicate the second BWP of the second cell, the first BWP is different from the activation BWP of the third cell, the first bit length of the second field is different from the second bit length of the second field of the first BWP, the third cell is the cell with the smallest cell identifier among the N cells corresponding to the N frequency domain resource allocation FDRA fields, the values of the N FDRA fields are invalid values, and N is an integer greater than 1. The method according to claim 7 is characterized in that the format of the DCI is a DCI format for scheduling multiple cells, and the DCI includes M FDRA fields, wherein the M FDRA fields include the N FDRA fields whose values are invalid values, and the second field is a field corresponding to the third cell, wherein the M is an integer greater than 1, and the M is greater than or equal to the N. The method according to claim 7 or 8, wherein the second field includes at least one of the following fields: Modulation and coding scheme MCS field; New data indication NDI field; Redundancy version RV field; Hybrid Automatic Repeat Request Process Number HPN field; or Antenna port AP field, wherein the radio resource control RRC parameter configuration said AP field is type 2. The method according to any one of claims 7 to 9, wherein the value of the FDRA field is defined as an invalid value by: The resource allocation RA type is configured as type 0, and the FDRA field indicates all 0s; or, The RA type is configured as type 1, and the FDRA field indicates all 1s; or The RA type is configured as a dynamic switching resource allocation type, and the FDRA field indicates all 0s or all 1s. A communication device, characterized by comprising a module for executing the method according to any one of claims 1 to 6, or a module for executing the method according to any one of claims 7 to 10. A communication device, characterized in that it includes a processor and an interface circuit, the interface circuit is used to receive signals from other communication devices and transmit them to the processor or send signals from the processor to other communication devices, the processor is used to implement the method according to any one of claims 1 to 6 through a logic circuit or execute code instructions, or to implement the method according to any one of claims 7 to 10. A communication system, characterized in that the system comprises: a communication device for executing the method according to any one of claims 1 to 6, and a communication device for executing the method according to any one of claims 7 to 10. A computer-readable storage medium, characterized in that a computer program or instruction is stored in the storage medium, and when the computer program or instruction is executed by a communication device, the method according to any one of claims 1 to 6 or the method according to any one of claims 7 to 10 is implemented. A computer program product, comprising a computer program or instructions, wherein when the computer program or instructions are executed by a communication device, the method according to any one of claims 1 to 6 is implemented, or the method according to any one of claims 7 to 10 is implemented.