Carrier aggregation method and device, terminal equipment and network equipment

Abstract

The embodiment of the invention provides a carrier aggregation method and device, terminal equipment and network equipment, and the method comprises the steps that the terminal equipment receives first configuration information sent by the network equipment, the first configuration information is used for configuring at least one cluster, and each cluster in the at least one cluster comprises at least one carrier or at least one cell.

Description

Carrier aggregation method and device, terminal equipment, and network equipment Technical Field

[0001] The embodiments of the present application relate to the field of mobile communication technology, and specifically to a carrier aggregation method and apparatus, terminal equipment, and network equipment. Background Art

[0002] In order to meet the demand for high speed, the fifth generation (5 th 5G systems support carrier aggregation (CA). CA enables the system to support larger bandwidth and achieve higher peak rates by jointly scheduling and utilizing resources on multiple component carriers (CCs).

[0003] In carrier aggregation (CA), carrier aggregation members are grouped at the cell level. Cells have distinct identities, such as the primary cell (PCell) and the secondary cell (SCell). Cells with different identities perform different functions, resulting in inequality between them. This leads to poor mobility robustness for mobile devices in these scenarios.

[0004] Summary of the Invention

[0005] Embodiments of the present application provide a carrier aggregation method and apparatus, terminal equipment, network equipment, chip, computer-readable storage medium, computer program product, and computer program.

[0006] The carrier aggregation method provided in the embodiment of the present application includes:

[0007] The terminal device receives first configuration information sent by the network device, where the first configuration information is used to configure at least one cluster, each of the at least one cluster including at least one carrier or at least one cell.

[0008] The carrier aggregation method provided in the embodiment of the present application includes:

[0009] The network device sends first configuration information to the terminal device, where the first configuration information is used to configure at least one cluster, each of the at least one cluster including at least one carrier or at least one cell.

[0010] The carrier aggregation apparatus provided in an embodiment of the present application is applied to a terminal device, and the apparatus includes:

[0011] The receiving unit is configured to receive first configuration information sent by a network device, where the first configuration information is used to configure at least one cluster, where each cluster in the at least one cluster includes at least one carrier or at least one cell.

[0012] The carrier aggregation apparatus provided in an embodiment of the present application is applied to a network device, and the apparatus includes:

[0013] A sending unit is used to send first configuration information to a terminal device, where the first configuration information is used to configure at least one cluster, each of the at least one cluster including at least one carrier or at least one cell.

[0014] The terminal device provided in an embodiment of the present application includes a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to perform the above-mentioned carrier aggregation method.

[0015] The network device provided in an embodiment of the present application includes a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to perform the above-mentioned carrier aggregation method.

[0016] The chip provided in the embodiment of the present application is used to implement the above-mentioned carrier aggregation method.

[0017] Specifically, the chip includes: a processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes the above-mentioned carrier aggregation method.

[0018] The computer-readable storage medium provided in an embodiment of the present application is used to store a computer program, which enables a computer to execute the above-mentioned carrier aggregation method.

[0019] The computer program product provided in an embodiment of the present application includes computer program instructions, which enable a computer to execute the above-mentioned carrier aggregation method.

[0020] The computer program provided in the embodiment of the present application, when executed on a computer, enables the computer to execute the above-mentioned carrier aggregation method.

[0021] Through the above technical solution, the network device configures at least one cluster for the terminal device through the first configuration information, each cluster includes at least one carrier or at least one cell, and carrier aggregation is realized in a cluster manner. The members participating in the carrier aggregation are based on the granularity of the carrier or cell, and the identities between the carriers or cells are equal. The terminal device can improve the mobility robustness when communicating in this scenario; in addition, when the members participating in the carrier aggregation are based on the granularity of the carrier, since there is no need to bind the uplink carrier and the downlink carrier together for aggregation (that is, the uplink carrier and the downlink carrier are decoupled during the aggregation process), the carrier aggregation is more flexible and can adapt to different business needs. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0023] FIG1 is a schematic diagram of an application scenario of an embodiment of the present application;

[0024] FIG2 is a schematic diagram of a flow chart of a carrier aggregation method provided in an embodiment of the present application;

[0025] FIG3 is a flowchart of a cluster configuration provided by an embodiment of the present application;

[0026] FIG4 is a first schematic diagram of a format of a MAC CE for activating and / or deactivating a cluster according to an embodiment of the present application;

[0027] FIG5 is a second schematic diagram of the format of a MAC CE for activating and / or deactivating a cluster provided in an embodiment of the present application;

[0028] FIG6 is a first schematic diagram of a format of a MAC CE for activating and / or deactivating a carrier according to an embodiment of the present application;

[0029] FIG7 is a second format of a MAC CE for activating and / or deactivating a carrier according to an embodiment of the present application;

[0030] FIG8 is a second flowchart of a cluster configuration provided by an embodiment of the present application;

[0031] FIG9 is a third schematic diagram of the format of a MAC CE for activating and / or deactivating a cluster according to an embodiment of the present application;

[0032] FIG10 is a fourth schematic diagram of a format of a MAC CE for activating and / or deactivating a cluster according to an embodiment of the present application;

[0033] FIG11 is a first embodiment of the present application provided by the MAC CE format for activating and / or deactivating a cell;

[0034] FIG12 is a second format of a MAC CE for activating and / or deactivating a cell according to an embodiment of the present application;

[0035] FIG13 is a schematic diagram of the deployment of a MAC entity and a HARQ entity provided in an embodiment of the present application;

[0036] FIG14-1 is a schematic diagram of a protocol stack deployed on the cloud provided in an embodiment of the present application;

[0037] FIG14-2 is a second schematic diagram of a protocol stack deployed on the cloud provided in an embodiment of the present application;

[0038] FIG14-3 is a third schematic diagram of a cloud-deployed protocol stack provided in an embodiment of the present application;

[0039] FIG15 is a flowchart of tight interworking provided in an embodiment of the present application;

[0040] FIG16 is a schematic diagram of the first structural composition of a carrier aggregation device provided in an embodiment of the present application;

[0041] FIG17 is a second schematic diagram of the structural composition of the carrier aggregation device provided in an embodiment of the present application;

[0042] FIG18 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0043] FIG19 is a schematic structural diagram of a chip according to an embodiment of the present application;

[0044] Figure 20 is a schematic block diagram of a communication system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0045] The following will describe the technical solutions in the embodiments of this application in conjunction with the drawings in the embodiments of this application. Obviously, the described embodiments are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0046] FIG1 is a schematic diagram of an application scenario of an embodiment of the present application.

[0047] As shown in Figure 1, a communication system 100 may include a terminal device 110 and a network device 120. The network device 120 may communicate with the terminal device 110 via an air interface. The terminal device 110 and the network device 120 support multi-service transmission.

[0048] It should be understood that the embodiments of the present application are only illustrative of the communication system 100, but the embodiments of the present application are not limited thereto. That is, the technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Long Term Evolution (LTE) system, LTE Time Division Duplex (TDD), Universal Mobile Telecommunication System (UMTS), Internet of Things (IoT) system, Narrow Band Internet of Things (NB-IoT) system, enhanced Machine-Type Communications (eMTC) system, 5G communication system (also known as New Radio (NR) communication system), or future communication systems.

[0049] In the communication system 100 shown in Figure 1, the network device 120 may be an access network device that communicates with the terminal device 110. The access network device may provide communication coverage for a specific geographical area and may communicate with the terminal device 110 (eg, UE) located within the coverage area.

[0050] The network device 120 may be an evolved Node B (eNB or eNodeB) in a Long Term Evolution (LTE) system, or a Next Generation Radio Access Network (NG RAN) device, or a gNB in ​​an NR system, or a wireless controller in a Cloud Radio Access Network (CRAN), or the network device 120 may be a relay station, an access point, an in-vehicle device, a wearable device, a hub, a switch, a bridge, a router, or a network device in a future evolved Public Land Mobile Network (PLMN), etc.

[0051] The terminal device 110 may be any terminal device, including but not limited to a terminal device connected to the network device 120 or other terminal devices by wire or wireless connection.

[0052] For example, the terminal device 110 may refer to an access terminal, user equipment (UE), a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or a user apparatus. An access terminal may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, an IoT device, a satellite handheld terminal, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal device in a 5G network, or a terminal device in a future evolution network, etc.

[0053] The terminal device 110 can be used for device-to-device (D2D) communication.

[0054] The wireless communication system 100 may further include a core network device 130 for communicating with the base station. The core network device 130 may be a 5G core network (5G Core, 5GC) device, such as an Access and Mobility Management Function (AMF), an Authentication Server Function (AUSF), a User Plane Function (UPF), or a Session Management Function (SMF). Optionally, the core network device 130 may also be an Evolved Packet Core (EPC) device of an LTE network, such as a Session Management Function + Core Packet Gateway (SMF+PGW-C) device. It should be understood that SMF+PGW-C can simultaneously implement the functions that can be implemented by SMF and PGW-C. During the network evolution process, the above-mentioned core network device may also be called other names, or a new network entity may be formed by dividing the functions of the core network, which is not limited in the embodiments of the present application.

[0055] The functional units in the communication system 100 may also establish connections and implement communication via next generation (NG) network interfaces.

[0056] For example, the terminal device establishes an air interface connection with the access network device through the NR interface for transmitting user plane data and control plane signaling; the terminal device can establish a control plane signaling connection with the AMF through the NG interface 1 (referred to as N1); the access network device, such as the next generation wireless access base station (gNB), can establish a user plane data connection with the UPF through the NG interface 3 (referred to as N3); the access network device can establish a control plane signaling connection with the AMF through the NG interface 2 (referred to as N2); the UPF can establish a control plane signaling connection with the SMF through the NG interface 4 (referred to as N4); the UPF can exchange user plane data with the data network through the NG interface 6 (referred to as N6); the AMF can establish a control plane signaling connection with the SMF through the NG interface 11 (referred to as N11); the SMF can establish a control plane signaling connection with the PCF through the NG interface 7 (referred to as N7).

[0057] Figure 1 exemplarily shows a base station, a core network device and two terminal devices. Optionally, the wireless communication system 100 may include multiple base station devices and each base station may include other numbers of terminal devices within its coverage area, which is not limited in this embodiment of the present application.

[0058] It should be noted that Figure 1 is merely an example of a system applicable to this application. Of course, the methods described in the embodiments of this application can also be applied to other systems. Furthermore, the terms "system" and "network" are often used interchangeably herein. The term "and / or" herein simply describes an association relationship between associated objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, the character " / " generally indicates that the associated objects are in an "or" relationship. It should also be understood that the "indication" mentioned in the embodiments of this application can be a direct indication, an indirect indication, or an indication of an association relationship. For example, "A indicates B" can mean that A directly indicates B, for example, B can obtain information through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can obtain information through C; or it can mean that A and B have an association relationship. It should also be understood that the "correspondence" mentioned in the embodiments of this application can mean that there is a direct or indirect correspondence between two objects, or that there is an association relationship between the two objects, or a relationship between an indicator and the indicated, a configuration and the configured, and so on. It should also be understood that the “predefined” or “predefined rules” mentioned in the embodiments of the present application can be implemented by pre-saving corresponding codes, tables or other methods that can be used to indicate relevant information in a device (for example, including a terminal device and a network device), and the present application does not limit its specific implementation method. For example, predefined can refer to a definition in a protocol. It should also be understood that in the embodiments of the present application, the “protocol” can refer to a standard protocol in the field of communications, such as an LTE protocol, an NR protocol, and related protocols used in future communication systems, and the present application does not limit this.

[0059] To facilitate understanding of the technical solutions of the embodiments of the present application, the relevant technologies of the embodiments of the present application are described below. The following relevant technologies can be arbitrarily combined with the technical solutions of the embodiments of the present application as optional solutions, and they all fall within the protection scope of the embodiments of the present application.

[0060] In 4G / 5G, the members participating in carrier aggregation are divided into PCell and SCell based on the granularity of cells. Among them, PCell is mainly responsible for system broadcast information, paging messages, Radio Resource Control (RRC) signaling, and mobility management, while the system broadcast information on SCell is configured through RRC dedicated signaling, and SCell is mainly responsible for data transmission. Each cell participating in carrier aggregation can have a physical downlink control channel (PDCCH). A cell can schedule its own physical downlink shared channel (PDSCH) through its own PDCCH. This scheduling method is called self-scheduling. Alternatively, a cell (i.e., the scheduling cell) can also schedule the PDSCH of other cells (i.e., the scheduled cell) through its own PDCCH. This scheduling method is called cross-carrier scheduling. In the cross-carrier scheduling method, the relationship between the scheduling cell and the scheduled cell can be configured through RRC signaling. There can be a Physical Uplink Control Channel (PUCCH) on the PCell. Optionally, there can be a PUCCH on at most one SCell. The PUCCH on a cell can realize uplink information transmission of all cells in the PUCCH group. Here, the PUCCH group refers to a cell group that can transmit uplink information through the same PUCCH, where the uplink information may include, for example, Hybrid Automatic Repeat-reQuest (HARQ) feedback information, Channel Status Information (CSI) report, etc.

[0061] For cells participating in carrier aggregation, each cell is associated with a cell index, which can be a serving cell index (Serving Cell index) or a secondary cell index (SCell index) or a carrier index (Carrier Index, CF). When configuring cells participating in carrier aggregation, the configuration information of a cell includes the configuration information of a downlink carrier. Optionally, the configuration information of an uplink carrier can be nested in the configuration information of a downlink carrier. Therefore, when configuring cells for carrier aggregation, only the downlink carrier can be configured, or the downlink carrier and the uplink carrier can be configured at the same time, so the number of downlink carriers must be greater than or equal to the number of uplink carriers. However, due to the diversity of current services, the uplink throughput of some services is greater than the downlink throughput, and the current carrier aggregation configuration method cannot meet the diverse business needs. Moreover, there is a one-to-one association between the downlink carrier and the uplink carrier, such as the association configured in SIB2. This makes the carrier management process inflexible and cannot meet the future business needs with high requirements for uplink data throughput.

[0062] During mobility, because the PCell has certain functional responsibilities, any change in the PCell will trigger a handover process (even if the target cell is the current SCell). Since the handover process involves a key change, it leads to a Media Access Control (MAC) reset, Packet Data Convergence Protocol (PDCP) reestablishment, and Radio Link Control (RLC) reestablishment, further causing service interruption and packet loss, impacting service performance. Furthermore, if a Radio Link Failure (RLF) occurs in the PCell, regardless of whether an RLF occurs in the SCell, a PCell RLF will be triggered, thereby triggering RRC connection reestablishment, which will also cause service interruption and packet loss, impacting service performance.

[0063] In future communication systems (such as 6G), when designing a "bandwidth-for-rate" mechanism, it is necessary to consider the flexibility, flexibility, and equality of carriers while meeting the needs of service diversity. To this end, the following technical solutions are proposed in the embodiments of this application.

[0064] To facilitate understanding of the technical solutions of the embodiments of the present application, the technical solutions of the present application are described in detail below through specific embodiments. The above related technologies can be combined arbitrarily with the technical solutions of the embodiments of the present application as optional solutions, and all of them fall within the scope of protection of the embodiments of the present application. The embodiments of the present application include at least part of the following contents.

[0065] The technical solution of the embodiment of the present application proposes the concept of "cluster", which can also be called "group". Clusters have different definitions depending on the granularity of members participating in carrier aggregation.

[0066] In one solution, the members participating in carrier aggregation are carriers, and a cluster can be defined as: a downlink cluster consisting of at least one downlink carrier, and / or an uplink cluster consisting of at least one uplink carrier. Specifically, when a terminal device enters the RRC connected state, the network device configures at least one downlink cluster and / or at least one uplink cluster for the terminal device, with each cluster associated with a cluster index. A downlink cluster may include at least one downlink carrier, each associated with a downlink carrier index; an uplink cluster may include at least one uplink carrier, each associated with an uplink carrier index. The association between downlink and uplink carriers is decoupled, meaning there is no fixed association. All downlink carriers within a downlink cluster are downlink synchronized, where downlink synchronization includes radio frame synchronization and / or subframe synchronization. All uplink carriers within an uplink cluster are uplink synchronized, where uplink synchronization can be understood as sharing a common uplink timing advance (TA). All downlink carriers within a downlink cluster have equal status, and similarly, all uplink carriers within an uplink cluster have equal status. Optionally, a downlink cluster may have a downlink carrier serving as a downlink cluster head. The downlink cluster head may be any downlink carrier in the downlink cluster, or a downlink carrier indicated by the network device, or a default downlink carrier. The downlink cluster head is used to achieve downlink synchronization for terminal devices. It should be noted that, since all downlink carriers in a downlink cluster are downlink synchronized, the downlink cluster head in a downlink cluster may be any downlink carrier in the downlink cluster, which also reflects that all downlink carriers in a downlink cluster have equal identities. Similarly, an uplink cluster may have an uplink carrier serving as an uplink cluster head. The uplink cluster head may be any uplink carrier in the uplink cluster, or an uplink carrier indicated by the network device, or a default uplink carrier. The uplink cluster head is used to achieve uplink synchronization for terminal devices. It should be noted that, since all uplink carriers in an uplink cluster are uplink synchronized, the uplink cluster head in an uplink cluster may be any uplink carrier in the uplink cluster, which also reflects that all uplink carriers in an uplink cluster have equal identities. In particular, the downlink carrier and uplink carrier of the cell where the terminal device initially enters the RRC connection state can serve as the downlink cluster head of a downlink cluster and the uplink cluster head of an uplink cluster, respectively. After the terminal device enters the RRC connection state, the network device can configure at least one downlink cluster and / or at least one uplink cluster for the terminal device. Here, the at least one downlink cluster needs to include the downlink cluster to which the downlink carrier of the cell where the terminal device initially enters the RRC connection state belongs. Similarly, the at least one uplink cluster needs to include the uplink cluster to which the uplink carrier of the cell where the terminal device initially enters the RRC connection state belongs. In addition to this, optionally, the network device can also configure a greater number of downlink clusters and / or uplink clusters for the terminal device.

[0067] As another solution, the members participating in carrier aggregation are cells, and the definition of a cluster can be: a cluster consisting of at least one cell. Specifically, when the terminal device enters the RRC connection state, the network device will configure at least one cluster for the terminal device, and each cluster is associated with a cluster index. Among them, a cluster can include at least one cell, and each cell is associated with a cell index. All cells in a cluster are downlink synchronized and / or uplink synchronized. Here, downlink synchronization includes wireless frame synchronization and / or subframe synchronization, and uplink synchronization can be understood as sharing a TA. The identities of all cells in a cluster are equal. Optionally, there will be a cell in a cluster as a cluster head. The cluster head can be any cell in the cluster or a cell indicated by the network device or a default cell. The cluster head is used for the terminal device to achieve downlink synchronization and / or uplink synchronization. It should be noted that since all cells in a cluster are downlink synchronized and / or uplink synchronized, the cluster head in a cluster can be any cell in the cluster, which also reflects that the identities of all cells in a cluster are equal. In particular, the cell where the terminal device initially enters the RRC connected state can serve as the cluster head of a cluster. After the terminal device enters the RRC connected state, the network device can configure at least one cluster for the terminal device. Here, the at least one cluster needs to include the cluster to which the cell where the terminal device initially enters the RRC connected state belongs. In addition, the network device can optionally configure a larger number of clusters for the terminal device.

[0068] At least one cluster configured on a network device can belong to the same site or different sites, which is transparent to the terminal device. Here, "site" can be a "base station." Since at least one cluster can belong to the same site or different sites, this effectively integrates carrier aggregation (CA) and dual connectivity (DC). In other words, DC and CA are transparent to the terminal device. This benefit reduces standardization, implementation, and testing efforts, and minimizes product feature differentiation in the market.

[0069] In addition, the RRC entity is not associated with a cell (whether logical or physical) and is an entity independent of the cell. This also reflects the equality of identity between all CCs (such as carriers or cells) in a cluster. The RRC entity can be associated with one or several sites, or with an area (such as the area defined by a cell list or the physical area governed by a cloud platform), or with one or more clusters.

[0070] FIG2 is a flow chart of a carrier aggregation method provided in an embodiment of the present application. As shown in FIG2 , the carrier aggregation method includes the following steps:

[0071] Step 201: A terminal device receives first configuration information sent by a network device, where the first configuration information is used to configure at least one cluster, each of the at least one cluster including at least one carrier or at least one cell.

[0072] In an embodiment of the present application, the network device sends first configuration information to the terminal device. Accordingly, the terminal device receives the first configuration information sent by the network device. The first configuration information is used to configure at least one cluster, and each cluster in the at least one cluster includes at least one carrier or at least one cell.

[0073] In some implementations, the network device is a network device corresponding to a current serving cell of the terminal device, for example, a first site corresponding to the current serving cell.

[0074] In some implementations, the first configuration information is carried in RRC signaling.

[0075] Solution 1: Members participating in carrier aggregation are based on carrier granularity

[0076] Cluster Configuration

[0077] In some embodiments, the first configuration information is used to configure at least one cluster, the at least one cluster including at least one downlink cluster (DL cluster) and / or at least one uplink cluster (UL cluster), each downlink cluster including at least one downlink carrier (DL carrier), and each uplink cluster including at least one uplink carrier (UL carrier).

[0078] Here, each cluster in the at least one downlink cluster and / or at least one uplink cluster is associated with a cluster index. The numbering of the cluster indexes satisfies the following constraints:

[0079] Constraint 1) The cluster indexes of the at least one downlink cluster are in the same numbering space (denoted as the first numbering space).

[0080] Constraint 2) The cluster indexes of the at least one upstream cluster are in the same numbering space (denoted as the second numbering space).

[0081] Constraint 3) Option 1) the cluster index of each cluster in the at least one downstream cluster and the cluster index of each cluster in the at least one upstream cluster are in independent numbering spaces (i.e., the first numbering space and the second numbering space are different numbering spaces); or, Option 2) the cluster index of each cluster in the at least one downstream cluster and the cluster index of each cluster in the at least one upstream cluster are in the same numbering space (i.e., the first numbering space and the second numbering space are the same numbering space).

[0082] It should be noted that cluster indexes in the same numbering space do not overlap. Cluster indexes in independent numbering spaces may overlap.

[0083] Here, each downlink carrier in the at least one downlink carrier is associated with a downlink carrier index; and / or each uplink carrier in the at least one uplink carrier is associated with an uplink carrier index. The numbering of the carrier indexes satisfies the following constraints:

[0084] Constraint 1) The downlink carrier indexes of each downlink carrier in at least one downlink carrier in the same downlink cluster are in the same numbering space.

[0085] Constraint 2) The uplink carrier indexes of each uplink carrier in at least one uplink carrier in the same uplink cluster are in the same numbering space.

[0086] Constraint 3) Option 1) The downlink carrier indexes of each downlink carrier in different downlink clusters are in independent numbering spaces; or Option 2) The downlink carrier indexes of each downlink carrier in different downlink clusters are in the same numbering space.

[0087] Constraint 4) Option 1) The uplink carrier indexes of each uplink carrier in different uplink clusters are in independent numbering spaces; or Option 2) The uplink carrier indexes of each uplink carrier in different uplink clusters are in the same numbering space.

[0088] In some implementations, the terminal device reports first capability information of the terminal device to the network device, and the network device receives the first capability information reported by the terminal device, where the first capability information includes at least one of the following:

[0089] First information, where the first information is used to indicate a capability of the terminal device to support a downlink cluster and / or a capability of the terminal device to support an uplink cluster;

[0090] Second information, where the second information is used to indicate a maximum number of downlink clusters and / or a maximum number of uplink clusters supported by the terminal device;

[0091] Third information, where the third information is used to indicate a maximum number of downlink carriers included in a downlink cluster and / or a maximum number of uplink carriers included in an uplink cluster supported by the terminal device;

[0092] Fourth information, the fourth information is used to indicate the frequency band combination of the downlink cluster and / or uplink cluster supported by the terminal device.

[0093] The network device may configure the at least one cluster for the terminal device according to the first capability information reported by the terminal device.

[0094] In the embodiment of the present application, downlink carriers within the same downlink cluster are downlink synchronized; and / or uplink carriers within the same uplink cluster are uplink synchronized.

[0095] For each downlink cluster, the terminal device performs downlink synchronization for the downlink cluster based on a first downlink carrier in the downlink cluster. Here, the first downlink carrier is any downlink carrier in the downlink cluster or a designated downlink carrier in the downlink cluster, and the designated downlink carrier is a downlink carrier indicated by a network device or a default downlink carrier.

[0096] For each uplink cluster, the terminal device performs uplink synchronization for the uplink cluster based on a first uplink carrier in the uplink cluster. Here, the first uplink carrier is any uplink carrier in the uplink cluster or a designated uplink carrier in the uplink cluster, and the designated uplink carrier is an uplink carrier indicated by a network device or a default uplink carrier.

[0097] In some embodiments, the terminal device uses a first random access resource to initiate a random access process to a first uplink carrier in the uplink cluster to achieve uplink synchronization; the first random access resource is a random access resource configured by the network device specifically for the uplink cluster.

[0098] FIG3 is a flow chart of a cluster configuration, which takes a terminal device as a UE and a network device including one or more sites (such as a base station) as an example. As shown in FIG3 , the process includes the following steps:

[0099] Step 301: The UE sends an RRC establishment request message to a network device.

[0100] Here, when a UE in an RRC idle state resides in a cell, the UE initiates an RRC connection establishment process due to a paging or uplink data arrival triggering the UE.

[0101] Here, optionally, the downlink carrier of the cell where the UE initiates the RRC connection establishment process can serve as the cluster head of a downlink cluster. The UE can complete downlink synchronization for the cell in the RRC idle state, and then obtain the configuration information of the cell, and perform a random access process for the cell based on the configuration information of the cell (for example, the associated uplink carrier configured through the system broadcast information of the cell), for example, sending MSG1 to the cell, receiving MSG2 sent by the cell, sending MSG3 (i.e., RRC establishment request message) to the cell, and receiving MSG4 (i.e., RRC establishment message) sent by the cell.

[0102] Step 302: The network device sends an RRC establishment message to the UE.

[0103] Step 303: After entering the RRC connected state, the UE sends an RRC setup complete message to the network device point.

[0104] Here, after the UE completes the random access process and the RRC connection establishment process, the UE enters the RRC connected state.

[0105] Step 304: The network device interacts with the core network to perform an initial context establishment process.

[0106] Step 305: The UE interacts with the network device to perform the UE capability reporting process.

[0107] Step 306: The UE interacts with the network device to perform the AS layer security activation process.

[0108] Step 307: The network device knows the UE's cluster-related capabilities.

[0109] Here, the network device learns the UE's cluster capability through the first capability information reported by the UE, where the first capability information includes at least one of the following:

[0110] First information, where the first information is used to indicate a capability of the terminal device to support a downlink cluster and / or a capability of the terminal device to support an uplink cluster;

[0111] Second information, where the second information is used to indicate a maximum number of downlink clusters and / or a maximum number of uplink clusters supported by the terminal device;

[0112] Third information, where the third information is used to indicate a maximum number of downlink carriers included in a downlink cluster and / or a maximum number of uplink carriers included in an uplink cluster supported by the terminal device;

[0113] Fourth information, the fourth information is used to indicate the frequency band combination of the downlink cluster and / or uplink cluster supported by the terminal device.

[0114] Step 308: The network device sends an RRC reconfiguration message to the UE, carrying configuration information of at least one downlink cluster and / or at least one uplink cluster (ie, first configuration information).

[0115] Here, after the UE capability reporting and AS layer security activation are completed between the UE and the access network, the network device completes the configuration of at least one downlink cluster and / or at least one uplink cluster, as well as the configuration of the carriers in each cluster through the RRC reconfiguration message.

[0116] Here, the network device may configure at least one downlink cluster and / or at least one uplink cluster for the UE according to the cluster capability of the UE.

[0117] Step 309: The UE sends an RRC reconfiguration completion message to the first site.

[0118] Step 310: The UE performs downlink synchronization with the downlink cluster.

[0119] Here, for the downlink cluster, the UE will randomly select a downlink carrier from the downlink cluster to perform downlink synchronization for the downlink cluster, or may also perform downlink synchronization for the downlink cluster according to the downlink carrier indicated by the network device, or may also perform downlink synchronization for the downlink cluster according to the default downlink carrier.

[0120] Step 311: The UE performs uplink synchronization with the uplink cluster.

[0121] Here, for the uplink cluster, the UE will randomly select an uplink carrier from the uplink cluster to perform uplink synchronization for the uplink cluster, or may also perform uplink synchronization for the uplink cluster according to the uplink carrier indicated by the network device, or may also perform uplink synchronization for the uplink cluster according to the default uplink carrier.

[0122] Here, the UE can achieve uplink synchronization through a random access process. The network device can configure a dedicated random access resource for the uplink cluster. The UE uses the dedicated random access resource to initiate a random access process to an uplink carrier in the uplink cluster, thereby quickly achieving uplink synchronization for the uplink cluster.

[0123] Step 312: The UE receives data via the downlink cluster and / or sends data via the uplink cluster.

[0124] Cluster Management

[0125] A) Add / Modify / Release Clusters

[0126] In some implementations, the network device sends second configuration information to the terminal device, and the terminal device receives the second configuration information sent by the network device, where the second configuration information is used to configure at least one of the following:

[0127] Add one or more downlink clusters and / or add one or more uplink clusters;

[0128] Modifying one or more downlink clusters and / or modifying one or more uplink clusters;

[0129] One or more downlink clusters are released and / or one or more uplink clusters are released.

[0130] In some implementations, the second configuration information is carried in RRC signaling.

[0131] Here, for the downlink cluster and / or uplink cluster, the network device may implement cluster management through RRC signaling, where the management includes at least one of the following: adding, modifying, and releasing.

[0132] B) Cluster status

[0133] In some embodiments, the first configuration information is further used to configure the initial state of each cluster in the at least one downlink cluster and / or the at least one uplink cluster; or, the initial state of each cluster in the at least one downlink cluster and / or the at least one uplink cluster defaults to an activated state or a deactivated state.

[0134] Here, the initial state of the downlink cluster and / or uplink cluster can be configured as an activated state or a deactivated state through RRC signaling. Alternatively, the initial state of the downlink cluster and / or uplink cluster is activated state or deactivated state by default.

[0135] In some embodiments, the network device sends a first command to the terminal device, and the terminal device receives the first command sent by the network device, where the first command is used to activate and / or deactivate at least some of the at least one downlink cluster and / or at least one uplink cluster. As an example, the first command includes at least one of the following: downlink control information (DCI) and a MAC control element (CE).

[0136] Here, the implementation of the first command may include but is not limited to the following:

[0137] Mode 1: The first command is used to activate and / or deactivate a cluster.

[0138] Mode 1-1) The first command carries a cluster index, first indication information, and second indication information, where the first indication information is used to indicate whether activation or deactivation is performed for the downlink or for the uplink, and the second indication information is used to indicate whether the cluster indicated by the cluster index is activated or deactivated, wherein the cluster index of the downlink cluster and the cluster index of the uplink cluster are in independent numbering spaces; or

[0139] Mode 1-2) The first command carries a cluster index and second indication information, where the second indication information is used to indicate whether to activate or deactivate the cluster indicated by the cluster index, wherein the cluster index of the downlink cluster and the cluster index of the uplink cluster are in the same numbering space; or

[0140] Mode 1-3) The first command carries a cluster index and second indication information, where the second indication information is used to indicate whether to activate or deactivate the cluster indicated by the cluster index, wherein the cluster index of the downlink cluster and the cluster index of the uplink cluster are in independent numbering spaces, and the association information of the first command is used to determine whether to activate or deactivate the downlink or uplink. Here, when the first command is a MAC CE, the association information of the first command is the logical channel identifier associated with the MAC CE.

[0141] Here, the network device may activate or deactivate a cluster through a layer 1 (L1) or layer 2 (L2) command, wherein the L1 command is, for example, a DCI, and the L2 command is, for example, a MAC CE.

[0142] Taking L2 commands as an example, the format of a MAC CE for activating and / or deactivating a cluster may refer to FIG4 , as shown in FIG4 :

[0143] In mode 1-1), the D / U field (corresponding to the first indication information) indicates whether the downlink cluster or the uplink cluster is to be activated or deactivated; the cluster index indicates the cluster to be activated or deactivated; and the A / D field (corresponding to the second indication information) indicates whether the cluster is to be activated or deactivated. The cluster index of the downlink cluster and the cluster index of the uplink cluster are in independent numbering spaces.

[0144] In mode 1-2), the cluster index is used to indicate the cluster to be activated or deactivated; the A / D field (corresponding to the second indication information) is used to indicate whether the cluster is to be activated or deactivated. The cluster index of the downlink cluster and the cluster index of the uplink cluster are in the same numbering space.

[0145] In method 1-3), the cluster index is used to indicate the cluster that needs to be activated or deactivated; the A / D field (corresponding to the second indication information) is used to indicate whether the cluster is activated or deactivated. The cluster index of the downlink cluster and the cluster index of the uplink cluster are in independent numbering spaces, and the logical channel identifier (LCID) associated with the MAC CE is used to indicate whether the activation or deactivation is for the downlink cluster or the uplink cluster. For example: LCID = x associated with the MAC CE is used to indicate that the MAC CE is for activation or deactivation of the downlink cluster. LCID = y associated with the MAC CE is used to indicate that the MAC CE is for activation or deactivation of the uplink cluster.

[0146] Mode 2: The first command is used to activate and / or deactivate one or more clusters.

[0147] Mode 2-1) The first command carries a first bitmap and first indication information, where each bit in the first bitmap corresponds to one or more cluster indexes, and the value of the bit is used to indicate whether one or more clusters indicated by the corresponding one or more cluster indexes are activated or deactivated, and the first indication information is used to indicate whether activation or deactivation is performed for the downlink or for the uplink, wherein the cluster index of the downlink cluster and the cluster index of the uplink cluster are in independent numbering spaces; or

[0148] Mode 2-2) The first command carries a first bitmap, where each bit in the first bitmap corresponds to one or more cluster indexes, and the value of the bit is used to indicate whether one or more clusters indicated by the corresponding one or more cluster indexes are activated or deactivated, wherein the cluster index of the downlink cluster and the cluster index of the uplink cluster are in the same numbering space; or

[0149] Mode 2-3) The first command carries a first bitmap, each bit in the first bitmap corresponds to one or more cluster indexes, and the value of the bit is used to indicate whether one or more clusters indicated by the corresponding one or more cluster indexes are activated or deactivated, wherein the cluster index of the downlink cluster and the cluster index of the uplink cluster are in independent numbering spaces, and the associated information of the first command is used to determine whether to activate or deactivate the downlink or the uplink. Here, when the first command is a MAC CE, the associated information of the first command is the logical channel identifier associated with the MAC CE.

[0150] Here, the network device can activate or deactivate one or more clusters through layer 1 (L1) or layer 2 (L2) commands, where the L1 command is, for example, a DCI, and the L2 command is, for example, a MAC CE.

[0151] Taking L2 commands as an example, the format of a MAC CE for activating and / or deactivating a cluster may refer to FIG5 , as shown in FIG5 :

[0152] In mode 2-1), the D / U field (corresponding to the first indication information) is used to indicate whether to activate or deactivate the downlink cluster or the uplink cluster; the bitmap, each bit in the bitmap corresponds to a cluster index, CLi indicates that the cluster index is i, and the bitmap in Figure 5 includes 7 bits. The number of bits occupied by the bitmap can be adjusted according to the number of clusters to be indicated. The value of each bit is used to indicate whether the cluster indicated by the corresponding cluster index is activated or deactivated. The cluster index of the downlink cluster and the cluster index of the uplink cluster are in independent numbering spaces.

[0153] In mode 2-2), a bitmap is used, where each bit corresponds to a cluster index, where CLi represents cluster index i. The bitmap in FIG5 includes 8 bits, but the present invention is not limited thereto. The number of bits occupied by the bitmap can be adjusted based on the number of clusters to be indicated. The value of each bit indicates whether the cluster indicated by the corresponding cluster index is activated or deactivated. The cluster index of the downlink cluster and the cluster index of the uplink cluster are in the same numbering space.

[0154] In method 2-3), the bitmap, each bit in the bitmap corresponds to a cluster index, CLi indicates that the cluster index is i, and the bitmap in Figure 5 includes 8 bits, but is not limited to this. The number of bits occupied by the bitmap can be adjusted according to the number of clusters that need to be indicated, and the value of each bit is used to indicate whether the cluster indicated by the corresponding cluster index is activated or deactivated. The cluster index of the downlink cluster and the cluster index of the uplink cluster are in independent numbering spaces, and the logical channel identifier (LCID) associated with the MAC CE is used to indicate whether the activation or deactivation is for the downlink cluster or the uplink cluster. For example: LCID associated with the MAC CE = x, is used to indicate that the MAC CE is for activation or deactivation of the downlink cluster. LCID associated with the MAC CE = y, is used to indicate that the MAC CE is for activation or deactivation of the uplink cluster.

[0155] Cluster membership management

[0156] A) Adding / modifying / releasing cluster members

[0157] In some implementations, the network device sends third configuration information to the terminal device, and the terminal device receives the third configuration information sent by the network device, where the third configuration information is used to configure at least one of the following:

[0158] Add one or more downlink carriers in a downlink cluster and / or add one or more uplink carriers in an uplink cluster;

[0159] Modifying one or more downlink carriers in a downlink cluster and / or modifying one or more uplink carriers in an uplink cluster;

[0160] One or more downlink carriers are released in the downlink cluster and / or one or more uplink carriers are released in the uplink cluster.

[0161] In some implementations, the third configuration information is carried in RRC signaling.

[0162] Here, for carriers in a downlink cluster and / or uplink cluster, the network device can manage the carriers in the cluster through RRC signaling. Management includes at least one of the following: adding, modifying, and releasing. It should be noted that if a cluster is released, all carriers in the cluster are also released. If a cluster is deactivated, all carriers in the cluster are also deactivated.

[0163] B) Status of cluster members

[0164] In some embodiments, the first configuration information is further used to configure the initial state of the carrier in each cluster of the at least one downlink cluster and / or the at least one uplink cluster; or, the initial state of the carrier in each cluster of the at least one downlink cluster and / or the at least one uplink cluster defaults to an activated state or a deactivated state.

[0165] Here, the initial state of the carriers in the cluster can be configured as an activated state or a deactivated state through RRC signaling. Alternatively, the initial state of the carriers in the cluster is defaulted to an activated state or a deactivated state.

[0166] In some embodiments, the network device sends a second command to the terminal device, and the terminal device receives the second command sent by the network device, where the second command is used to activate and / or deactivate at least some carriers in the at least one downlink cluster and / or at least one uplink cluster. As an example, the second command includes at least one of the following: DCI, MAC CE.

[0167] Here, the implementation of the second command may include but is not limited to the following:

[0168] Mode 1: The second command is used to activate and / or deactivate a carrier.

[0169] Mode 1-1) The second command carries a cluster index, a carrier index, third indication information, and fourth indication information, wherein the third indication information is used to indicate whether to activate or deactivate the downlink or the uplink, and the fourth indication information is used to indicate whether to activate or deactivate the carrier indicated by the carrier index, wherein the cluster index of the downlink cluster and the cluster index of the uplink cluster are in independent numbering spaces, and the carrier indexes in different clusters in the downlink cluster or uplink cluster are in independent numbering spaces; or,

[0170] Mode 1-2) The second command carries a cluster index, a carrier index, and fourth indication information, where the fourth indication information is used to indicate whether to activate or deactivate the carrier indicated by the carrier index, wherein the cluster index of the downlink cluster and the cluster index of the uplink cluster are in the same numbering space, and the carrier indexes in different clusters in the downlink cluster or uplink cluster are in independent numbering spaces; or

[0171] Mode 1-3) The second command carries a cluster index, a carrier index and fourth indication information, the fourth indication information is used to indicate whether to activate or deactivate the carrier indicated by the carrier index, wherein the cluster index of the downlink cluster and the cluster index of the uplink cluster are in independent numbering spaces, and the carrier indexes in different clusters in the downlink cluster or uplink cluster are in independent numbering spaces, and the associated information of the second command is used to determine whether to activate or deactivate the downlink or the uplink; here, when the second command is a MAC CE, the associated information of the second command is the logical channel identifier associated with the MAC CE. Or,

[0172] Mode 1-4) The second command carries a carrier index, third indication information, and fourth indication information, the third indication information being used to indicate whether to activate or deactivate the downlink or the uplink, and the fourth indication information being used to indicate whether to activate or deactivate the carrier indicated by the carrier index, wherein the carrier index within the downlink cluster and the carrier index within the uplink cluster are in independent numbering spaces, and the carrier indexes in different clusters in the downlink cluster or uplink cluster are in the same numbering space; or,

[0173] Mode 1-5) The second command carries a carrier index and fourth indication information, where the fourth indication information is used to indicate whether to activate or deactivate the carrier indicated by the carrier index, wherein the carrier index in the downlink cluster and the carrier index in the uplink cluster are in the same numbering space; or

[0174] Mode 1-6) The second command carries a carrier index and fourth indication information, the fourth indication information being used to indicate whether to activate or deactivate the carrier indicated by the carrier index, wherein the carrier index within the downlink cluster and the carrier index within the uplink cluster are in independent numbering spaces, and the carrier indexes within different clusters within the downlink cluster or uplink cluster are in the same numbering space, and the associated information of the second command is used to determine whether to activate or deactivate the downlink or the uplink. Here, when the second command is a MAC CE, the associated information of the second command is the logical channel identifier associated with the MAC CE.

[0175] Here, the network device may activate or deactivate a certain carrier through a layer 1 (L1) or layer 2 (L2) command, wherein the L1 command is, for example, a DCI, and the L2 command is, for example, a MAC CE.

[0176] Taking L2 commands as an example, the format of a MAC CE for activating and / or deactivating a carrier may refer to FIG6 , as shown in FIG6 :

[0177] In mode 1-1), the D / U field (corresponding to the third indication information) indicates whether activation / deactivation is performed for the downlink or uplink; the cluster index indicates the cluster index of the carrier to be activated / deactivated; the carrier index indicates the carrier to be activated / deactivated; and the A / D field (corresponding to the fourth indication information) indicates whether the carrier is activated or deactivated. The cluster index of the downlink cluster and the cluster index of the uplink cluster are in independent numbering spaces, and the carrier indices within different clusters within a downlink or uplink cluster are in independent numbering spaces.

[0178] In methods 1-2), the cluster index indicates the cluster index of the carrier to be activated or deactivated; the carrier index indicates the carrier to be activated or deactivated; and the A / D field (corresponding to the fourth indication information) indicates whether the carrier is to be activated or deactivated. The cluster index of the downlink cluster and the cluster index of the uplink cluster are in the same numbering space, and the carrier indices in different clusters within the downlink or uplink cluster are in independent numbering spaces.

[0179] In method 1-3), the cluster index is used to indicate the cluster index of the carrier that needs to be activated or deactivated; the carrier index is used to indicate the carrier that needs to be activated or deactivated; the A / D field (corresponding to the fourth indication information) is used to indicate whether the carrier is activated or deactivated. The cluster index of the downlink cluster and the cluster index of the uplink cluster are in independent numbering spaces, and the carrier indexes in different clusters in the downlink cluster or uplink cluster are in independent numbering spaces. The logical channel identifier (LCID) associated with the MAC CE is used to indicate whether the activation or deactivation is for the downlink or for the uplink. For example: LCID = x associated with the MAC CE is used to indicate that the MAC CE is activated or deactivated for the downlink. LCID = y associated with the MAC CE is used to indicate that the MAC CE is activated or deactivated for the uplink.

[0180] In methods 1-4), the D / U field (corresponding to the third indication information) indicates whether activation / deactivation is performed for the downlink or uplink; the carrier index indicates the carrier to be activated / deactivated; and the A / D field (corresponding to the fourth indication information) indicates whether the carrier is activated or deactivated. The carrier index within the downlink cluster and the carrier index within the uplink cluster are in independent numbering spaces, and the carrier indexes within different clusters within the downlink or uplink cluster are in the same numbering space.

[0181] In methods 1-5), the carrier index indicates the carrier to be activated or deactivated; the A / D field (corresponding to the fourth indication information) indicates whether the carrier is activated or deactivated. The carrier index within the downlink cluster and the carrier index within the uplink cluster are in the same numbering space.

[0182] In method 1-6), the carrier index is used to indicate the carrier that needs to be activated or deactivated; the A / D field (corresponding to the fourth indication information) is used to indicate whether the carrier is activated or deactivated. The carrier index in the downlink cluster and the carrier index in the uplink cluster are in independent numbering spaces, and the carrier indexes in different clusters in the downlink cluster or uplink cluster are in the same numbering space. The logical channel identifier (LCID) associated with the MAC CE is used to indicate whether the activation or deactivation is for the downlink or for the uplink. For example: LCID associated with the MAC CE = x is used to indicate that the MAC CE is for activation or deactivation for the downlink. LCID associated with the MAC CE = y is used to indicate that the MAC CE is for activation or deactivation for the uplink.

[0183] Mode 2: The second command is used to activate and / or deactivate one or more carriers.

[0184] Mode 2-1) The second command carries a cluster index, a second bitmap, and third indication information, where each bit in the second bitmap corresponds to one or more carrier indexes, and the value of the bit is used to indicate whether the one or more carriers indicated by the corresponding one or more carrier indexes are activated or deactivated, and the third indication information is used to indicate whether activation or deactivation is performed for the downlink or for the uplink, wherein the cluster index of the downlink cluster and the cluster index of the uplink cluster are in independent numbering spaces, and the carrier indexes in different clusters in the downlink cluster or uplink cluster are in independent numbering spaces; or,

[0185] Mode 2-2) The second command carries a cluster index and a second bitmap, each bit in the second bitmap corresponds to one or more carrier indexes, and the value of the bit is used to indicate whether the one or more carriers indicated by the corresponding one or more carrier indexes are activated or deactivated, wherein the cluster index of the downlink cluster and the cluster index of the uplink cluster are in the same numbering space, and the carrier indexes in different clusters in the downlink cluster or uplink cluster are in independent numbering spaces; or

[0186] Mode 2-3) The second command carries a cluster index and a second bitmap, each bit in the second bitmap corresponds to one or more carrier indices, and the value of the bit is used to indicate whether the one or more carriers indicated by the corresponding one or more carrier indices are activated or deactivated, wherein the cluster index of the downlink cluster and the cluster index of the uplink cluster are in independent numbering spaces, and the carrier indices in different clusters in the downlink cluster or uplink cluster are in independent numbering spaces, and the associated information of the second command is used to determine whether to activate or deactivate the downlink or the uplink; here, when the second command is a MAC CE, the associated information of the second command is the logical channel identifier associated with the MAC CE. Or,

[0187] Mode 2-4) The second command carries a second bitmap and third indication information, each bit in the second bitmap corresponds to one or more carrier indexes, and the value of the bit is used to indicate whether the one or more carriers indicated by the corresponding one or more carrier indexes are activated or deactivated, and the third indication information is used to indicate whether activation or deactivation is performed for the downlink or for the uplink, wherein the carrier index within the downlink cluster and the carrier index within the uplink cluster are in an independent numbering space, and the carrier indexes in different clusters in the downlink cluster or the uplink cluster are in the same numbering space; or,

[0188] Mode 2-5) The second command carries a second bitmap, where each bit in the second bitmap corresponds to one or more carrier indexes, and the value of the bit is used to indicate whether the one or more carriers indicated by the corresponding one or more carrier indexes are activated or deactivated, wherein the carrier index in the downlink cluster and the carrier index in the uplink cluster are in the same numbering space; or

[0189] Mode 2-6) The second command carries a second bitmap, each bit in the second bitmap corresponds to one or more carrier indexes, and the value of the bit is used to indicate whether the one or more carriers indicated by the corresponding one or more carrier indexes are activated or deactivated, wherein the carrier index within the downlink cluster and the carrier index within the uplink cluster are in independent numbering spaces, and the carrier indexes in different clusters in the downlink cluster or uplink cluster are in the same numbering space, and the associated information of the second command is used to determine whether to activate or deactivate the downlink or the uplink. Here, when the second command is a MAC CE, the associated information of the second command is the logical channel identifier associated with the MAC CE.

[0190] Here, the network device may activate or deactivate one or more carriers through a layer 1 (L1) or layer 2 (L2) command, wherein the L1 command is, for example, a DCI, and the L2 command is, for example, a MAC CE.

[0191] Taking L2 commands as an example, the format of a MAC CE for activating and / or deactivating a carrier may refer to FIG7 , as shown in FIG7 :

[0192] In mode 2-1), the D / U field (corresponding to the third indication information) is used to indicate whether activation or deactivation is performed for the downlink or for the uplink; the cluster index is used to indicate the cluster index of the carrier that needs to be activated or deactivated; the bit map, each bit in the bit map corresponds to a carrier index, Ci represents the carrier index is i, the number of bits occupied by the bit map in Figure 7 is only an example, the number of bits can be adjusted according to the number of carriers that need to be indicated, and the value of each bit is used to indicate whether the carrier indicated by the corresponding carrier index is activated or deactivated. The cluster index of the downlink cluster and the cluster index of the uplink cluster are in independent numbering spaces, and the carrier indexes in different clusters in the downlink cluster or uplink cluster are in independent numbering spaces.

[0193] In mode 2-2), the cluster index is used to indicate the cluster index of the carrier to be activated or deactivated; the bitmap, each bit in the bitmap corresponds to a carrier index, Ci represents the carrier index i, and the number of bits occupied by the bitmap in Figure 7 is only an example. The number of bits can be adjusted according to the number of carriers to be indicated. The value of each bit is used to indicate whether the carrier indicated by the corresponding carrier index is to be activated or deactivated. The cluster index of the downlink cluster and the cluster index of the uplink cluster are in the same numbering space, and the carrier indices in different clusters in the downlink cluster or uplink cluster are in independent numbering spaces.

[0194] In method 2-3), the cluster index is used to indicate the cluster index of the carrier that needs to be activated or deactivated; the bit map, each bit in the bit map corresponds to a carrier index, Ci represents the carrier index i, the number of bits occupied by the bit map in Figure 7 is only an example, and the number of bits can be adjusted according to the number of carriers that need to be indicated. The value of each bit is used to indicate whether the carrier indicated by the corresponding carrier index is activated or deactivated. The cluster index of the downlink cluster and the cluster index of the uplink cluster are in independent numbering spaces, and the carrier indexes in different clusters in the downlink cluster or uplink cluster are in independent numbering spaces. The logical channel identifier (LCID) associated with the MAC CE is used to indicate whether the activation or deactivation is for the downlink or for the uplink. For example: LCID associated with the MAC CE = x is used to indicate that the MAC CE is activated or deactivated for the downlink. LCID associated with the MAC CE = y is used to indicate that the MAC CE is activated or deactivated for the uplink.

[0195] In mode 2-4), the D / U field (corresponding to the third indication information) is used to indicate whether activation or deactivation is performed for the downlink or for the uplink; a bit map, each bit in the bit map corresponds to a carrier index, Ci represents the carrier index is i, the number of bits occupied by the bit map in Figure 7 is only an example, and the number of bits can be adjusted according to the number of carriers to be indicated, and the value of each bit is used to indicate whether the carrier indicated by the corresponding carrier index is activated or deactivated. The carrier index within the downlink cluster and the carrier index within the uplink cluster are in independent numbering spaces, and the carrier indexes in different clusters in the downlink cluster or uplink cluster are in the same numbering space.

[0196] In approach 2-5), each bit in the bitmap corresponds to a carrier index, where Ci represents carrier index i. The number of bits occupied by the bitmap in Figure 7 is only an example and can be adjusted based on the number of carriers to be indicated. The value of each bit indicates whether the carrier indicated by the corresponding carrier index is activated or deactivated. The carrier indices within the downlink cluster and the carrier indices within the uplink cluster are in the same numbering space.

[0197] In method 2-6), the bit map, each bit in the bit map corresponds to a carrier index, Ci represents the carrier index i, the number of bits occupied by the bit map in Figure 7 is only an example, and the number of bits can be adjusted according to the number of carriers that need to be indicated. The value of each bit is used to indicate whether the carrier indicated by the corresponding carrier index is activated or deactivated. The carrier index in the downlink cluster and the carrier index in the uplink cluster are in an independent numbering space, and the carrier indexes in different clusters in the downlink cluster or uplink cluster are in the same numbering space. The logical channel identifier (LCID) associated with the MAC CE is used to indicate whether the activation or deactivation is for the downlink or for the uplink. For example: LCID associated with the MAC CE = x, used to indicate that the MAC CE is activated or deactivated for the downlink. LCID associated with the MAC CE = y, used to indicate that the MAC CE is activated or deactivated for the uplink.

[0198] In some implementations, the downlink carrier and / or uplink carrier within the cluster has at least one of the following characteristics:

[0199] Feature 1: For a deactivated downlink carrier, the behavior of the terminal device on the downlink carrier includes at least one of the following: not monitoring PDCCH, not receiving PDSCH, performing CSI measurement, and performing beam measurement.

[0200] Feature 2: For a deactivated downlink carrier, whether the downlink carrier supports the sending and / or receiving of a first signal is determined based on the configuration of the network device, and the first signal includes at least one of the following: PDCCH, PDSCH, synchronization signal block (SS / PBCH Block, SSB), and channel state information reference signal (Channel State Information-Reference Signal, CSI-RS).

[0201] Feature 3: For a deactivated uplink carrier, the behavior of the terminal device on the uplink carrier includes at least one of the following: not sending PUSCH, not sending PUCCH, and not sending a sounding reference signal (SRS).

[0202] Feature 4: For a deactivated uplink carrier, whether the uplink carrier supports sending and / or receiving a second signal is determined based on the configuration of the network device, and the second signal includes at least one of the following: PUCCH, PUSCH, SRS, and Physical Random Access Channel (PRACH).

[0203] Here, after the downlink carrier is deactivated, the terminal device does not monitor the PDCCH or receive the PDSCH on the downlink carrier. Optionally, the terminal device can perform CSI measurements on the downlink carrier, or determine whether to perform CSI measurements on the downlink carrier based on the configuration of the network device. Optionally, the terminal device can perform beamforming measurements on the downlink carrier, or determine whether to perform beamforming measurements on the downlink carrier based on the configuration of the network device.

[0204] Here, after the uplink carrier is deactivated, the terminal device does not send PUSCH on the uplink carrier. Optionally, the terminal device does not send PUCCH on the uplink carrier, or determines whether to send PUCCH on the uplink carrier based on the configuration of the network device. Optionally, the terminal device does not send SRS on the uplink carrier, or determines whether to send SRS on the uplink carrier based on the configuration of the network device.

[0205] Scheduling of cluster members

[0206] In some implementations, for each configured downlink carrier, whether the downlink carrier contains PDCCH, PDSCH, SSB, CSI-RS, etc. can be determined based on the configuration of the network device. The downlink carrier can support self-scheduling, intra-cluster cross-carrier scheduling, and inter-cluster cross-carrier scheduling (i.e., cross-cluster cross-carrier scheduling).

[0207] In some implementations, for each configured uplink carrier, whether PUCCH, PUSCH, SRS, PRACH, etc. exist on the uplink carrier can be determined based on the configuration of the network device. The uplink carrier can support self-scheduling, intra-cluster cross-carrier scheduling, and inter-cluster cross-carrier scheduling (i.e., cross-cluster cross-carrier scheduling).

[0208] In some implementations, for a downlink carrier, the downlink carrier supports at least one of the following scheduling modes:

[0209] Same-carrier scheduling mode (also known as self-scheduling mode), wherein the same-carrier scheduling mode is that the DCI on the downlink carrier schedules the PDSCH on the downlink carrier;

[0210] A cross-carrier scheduling mode is that the DCI on the downlink carrier schedules the PDSCH on the second downlink carrier and / or schedules the PUSCH on the second uplink carrier.

[0211] In some embodiments, the cross-carrier scheduling mode includes a first type of cross-carrier scheduling mode and / or a second type of cross-carrier scheduling mode;

[0212] In the first type of cross-carrier scheduling mode (i.e., intra-cluster cross-carrier scheduling mode), the downlink carrier and the scheduled carrier belong to the same downlink cluster, and the scheduled carrier is the second downlink carrier;

[0213] In the second type of cross-carrier scheduling mode (ie, inter-cluster cross-carrier scheduling mode), the downlink carrier and the scheduled carrier belong to different downlink clusters, and the scheduled carrier includes the second downlink carrier and / or the second uplink carrier.

[0214] In some embodiments, for the first type of cross-carrier scheduling method, the DCI on the downlink carrier carries the carrier index of the scheduled carrier (or the identification information of the scheduled carrier); or, the relationship between the downlink carrier and the scheduled carrier is configured through RRC signaling.

[0215] In some embodiments, for the second type of cross-carrier scheduling mode, the DCI on the downlink carrier carries the cluster index of the cluster where the scheduled carrier is located (or the identification information of the cluster where the scheduled carrier is located) and the carrier index of the scheduled carrier (or the identification information of the scheduled carrier), wherein the carrier indexes in different clusters are in independent numbering spaces; or, the DCI on the downlink carrier carries the carrier index of the scheduled carrier, wherein the carrier indexes in different clusters are in the same numbering space; or, the relationship between the downlink carrier and the scheduled carrier is configured through RRC signaling.

[0216] In some implementations, in future communication systems (such as 6G), if the DCI format for scheduling a downlink carrier and a scheduling an uplink carrier is the same, the DCI also needs to carry an indication information to indicate whether the scheduled carrier is an uplink carrier or a downlink carrier.

[0217] In the above scheme, for the cross-carrier scheduling method, the relationship between the scheduling carrier and the scheduled carrier can be configured through RRC signaling, or the relationship between the scheduling carrier and the scheduled carrier is flexible and variable, and the scheduled carrier is dynamically indicated through DCI.

[0218] HARQ feedback on cluster members

[0219] In some implementations, for a third downlink carrier in the at least one downlink cluster, HARQ feedback information of a PDSCH on the third downlink carrier is transmitted via a PUCCH on a third uplink carrier.

[0220] Here, the third uplink carrier is configured through RRC signaling; or, the third uplink carrier is indicated through DCI that schedules the third downlink carrier.

[0221] In some embodiments, when the third uplink carrier is indicated by scheduling the DCI of the third downlink carrier, the DCI for scheduling the third downlink carrier carries the cluster index of the cluster in which the third uplink carrier is located and the carrier index of the third uplink carrier, wherein the carrier indexes in different clusters are in independent numbering spaces; or, the DCI for scheduling the third downlink carrier carries the carrier index of the third uplink carrier, wherein the carrier indexes in different clusters are in the same numbering space.

[0222] Here, for downlink feedback (i.e., HARQ feedback for PDSCH), PUCCH can be configured on one or more configured uplink carriers for HARQ feedback. Method 1: On which uplink carrier's PUCCH is the HARQ feedback information of the PDSCH of a downlink carrier transmitted? This can be configured through RRC signaling, for example: a PUCCH group is configured through RRC signaling, and the HARQ feedback information of all downlink carriers in the PUCCH group is transmitted through the same PUCCH. For the case of semi-persistent scheduling (SPS), it is also possible to configure through RRC signaling which uplink carrier's PUCCH is used for HARQ feedback. Method 2: On which uplink carrier's PUCCH is the HARQ feedback information of the PDSCH of a downlink carrier transmitted? This can be indicated by the DCI that schedules the PDSCH, for example, the DCI indicates the carrier index of the uplink carrier and / or the cluster index of the cluster where the uplink carrier is located.

[0223] TB transfer on cluster members

[0224] In current CA, members participating in carrier aggregation correspond to the same MAC entity, each member corresponds to a HARQ entity, and each HARQ entity has multiple HARQ processes. When a TB is initially transmitted on a member, if the transmission fails (i.e., a HARQ NACK occurs), the subsequent retransmission of the TB can only be performed on this member (even if the channel conditions of this member are very poor). This is because the data in a HARQ process in a HARQ entity must be associated for combined decoding. If the TB is retransmitted by changing the member, it is equivalent to retransmitting across HARQ entities, and the association between the initial and retransmitted data cannot be achieved.

[0225] To ensure that the TB can be effectively received by the receiving end, it is necessary to select members with better conditions to transmit the TB. The following implementation solutions can be used:

[0226] In some embodiments, the terminal device receives a first TB on a fourth downlink carrier, and if the number of retransmissions of the first TB exceeds a first threshold value, the terminal device receives the first TB on a fifth downlink carrier; and / or, the terminal device sends a second TB on a fourth uplink carrier, and if the number of retransmissions of the second TB exceeds a second threshold value, the terminal device sends the second TB on a fifth uplink carrier.

[0227] To ensure that TB can be effectively decoded by the receiving end, the following implementation solutions are available:

[0228] A) TB's new biography

[0229] In some implementations, the first TB on the fifth downlink carrier is new transmission data; and / or the second TB on the fifth uplink carrier is new transmission data.

[0230] In some implementations, the terminal device receives first DCI on the fourth downlink carrier, where the first DCI carries at least one of the following:

[0231] fifth information, where the fifth information is used to schedule the fifth downlink carrier to newly transmit the first TB;

[0232] The sixth information is used to instruct the network device to abandon retransmission of the first TB on the fourth downlink carrier and / or instruct the terminal device to clear the cache corresponding to the first HARQ process of the fourth downlink carrier, where the first HARQ process is the HARQ process corresponding to the first TB on the fourth downlink carrier.

[0233] In some implementations, the terminal device receives second DCI on a fourth downlink carrier, where the second DCI carries at least one of the following:

[0234] seventh information, where the seventh information is used to schedule the fifth uplink carrier to newly transmit the second TB;

[0235] The eighth information is used to instruct the terminal device to abandon retransmission of the second TB on the fourth uplink carrier and / or instruct the terminal device to clear the cache corresponding to the second HARQ process of the fourth uplink carrier, where the second HARQ process is the HARQ process corresponding to the second TB on the fourth uplink carrier.

[0236] For the above solution, different carriers correspond to different HARQ entities. Specifically, the fifth downlink carrier and the fourth downlink carrier correspond to different HARQ entities; and / or the fifth uplink carrier and the fourth uplink carrier correspond to different HARQ entities.

[0237] Here, if the number of retransmissions of a TB on a carrier exceeds a certain number, a new carrier may be selected to transmit the TB as new transmission data, and all transmissions of the TB on the previous carrier may be abandoned.

[0238] For the downlink, assuming that a certain TB1 is transmitted in HARQ process 1 of downlink carrier 1 and the number of retransmissions exceeds n without success, the network device abandons the transmission of TB1 in HARQ process 1 of downlink carrier 1 and schedules TB2 for transmission in HARQ process 1 of downlink carrier 1. Furthermore, the network device can perform cross-carrier scheduling on downlink carrier 1 and transmit TB1 as new data in downlink carrier 2. At the same time, the network device can send a PDCCH to the terminal device, instructing the network device to abandon the retransmission of TB1 in HARQ process 1 of downlink carrier 1 through the PDCCH, and the terminal device will clear the cache corresponding to HARQ process 1 of downlink carrier 1.

[0239] For the uplink, assuming that a certain TB2 is being transmitted in HARQ process 1 of uplink carrier 1 and the number of retransmissions exceeds n without success, the network device can send a PDCCH to the terminal device, instructing the terminal device through this PDCCH to abandon the retransmission of TB2 in HARQ process 1 of uplink carrier 1. The terminal device will clear the cache corresponding to HARQ process 1 of uplink carrier 1. Furthermore, the network device can perform cross-carrier scheduling through the PDCCH and transmit TB2 as new data in uplink carrier 2. Among them, the PDCCH can directly carry the cross-carrier scheduling information or instruct the terminal device to wait for the scheduling of other PDCCHs to perform the initial transmission of TB2.

[0240] B) TB retransmission

[0241] In some embodiments, the first TB on the fifth downlink carrier is retransmitted data of the first TB on the fourth downlink carrier; and / or the second TB on the fifth uplink carrier is retransmitted data of the second TB on the fourth uplink carrier.

[0242] B-1) For the above solution, the fifth downlink carrier and the fourth downlink carrier correspond to the same HARQ entity; and / or, the fifth uplink carrier and the fourth uplink carrier correspond to the same HARQ entity.

[0243] Here, each carrier group in the at least one downlink cluster and / or the at least one uplink cluster corresponds to a HARQ entity. The fifth downlink carrier and the fourth downlink carrier belong to the same carrier group, and / or the fifth uplink carrier and the fourth uplink carrier belong to the same carrier group. Therefore, the fifth downlink carrier and the fourth downlink carrier correspond to the same HARQ entity; and / or the fifth uplink carrier and the fourth uplink carrier correspond to the same HARQ entity.

[0244] In some embodiments, the terminal device receives fourth configuration information sent by the network device, where the fourth configuration information is used to configure one or more carrier groups, where each carrier group corresponds to a HARQ entity. Here, the fourth configuration information is carried in RRC signaling.

[0245] Here, since one carrier group corresponds to one HARQ entity, cross-carrier retransmission can be performed between carriers within one carrier group.

[0246] B-2) For the above solution, the fifth downlink carrier and the fourth downlink carrier correspond to different HARQ entities; and / or, the fifth uplink carrier and the fourth uplink carrier correspond to different HARQ entities. Here, the network device can indicate cross-carrier retransmission related information to the terminal device so that the terminal device can associate the initial transmission data with the retransmission data to achieve combined decoding gain. Specifically,

[0247] The terminal device receives a third DCI on a fourth downlink carrier, where the third DCI carries at least one of the following:

[0248] Ninth information, where the ninth information is used to schedule the fifth downlink carrier to retransmit the first TB;

[0249] Tenth information, where the tenth information is used to indicate a HARQ process identifier corresponding to the first TB on the fourth downlink carrier;

[0250] The eleventh information is used to indicate the HARQ process identifier corresponding to the first TB on the fifth downlink carrier.

[0251] The terminal device receives a fourth DCI on a fourth downlink carrier, where the fourth DCI carries at least one of the following:

[0252] Twelfth information, the twelfth information is used to schedule the fifth uplink carrier to retransmit the second TB;

[0253] Thirteenth information, the thirteenth information is used to indicate the HARQ process identifier corresponding to the second TB on the fourth uplink carrier;

[0254] Fourteenth information, the fourteenth information is used to indicate the HARQ process identifier corresponding to the second TB on the fifth uplink carrier.

[0255] Here, for downlink retransmission or uplink retransmission, the network device can carry indication information in the DCI for scheduling downlink retransmission or uplink retransmission, and use the indication information to indicate that the scheduling corresponding to the DCI is the retransmission scheduling of a certain carrier. For example, the DCI carries the relevant information of the scheduled carrier corresponding to the downlink retransmission and the HARQ corresponding to the retransmission data of the scheduled carrier for identification, and the scheduling carrier identifies the HARQ for this cross-carrier retransmission scheduling. The terminal device associates the initial transmission data and the retransmission data according to the information carried in the DCI, thereby achieving combined decoding gain. For example, the DCI carries the relevant information of the scheduled carrier corresponding to the uplink retransmission and the HARQ corresponding to the retransmission data of the scheduled carrier for identification, and the scheduling carrier identifies the HARQ for this cross-carrier retransmission scheduling. The terminal device performs cross-carrier retransmission according to the information carried in the DCI, and the network device can associate the initial transmission data and the retransmission data, thereby achieving combined decoding gain.

[0256] Random access on cluster members

[0257] In current Carrier Aggregation (CA), downlink and uplink carriers have a 1:1 binding relationship. When a terminal device performs random access on an SCell, it sends a first message (such as MSG1 / 3 / A) on the SCell's uplink carrier, but receives a second message (such as MSG2 / 4 / B) on the PCell's downlink carrier. The relationship between the downlink and uplink carriers during this random access process is clear. In cluster-based carrier aggregation, each carrier has an equal identity, with no distinction between PCell and SCell identities. There is no fixed association between downlink and uplink carriers. Therefore, during random access, it is necessary to clearly determine which uplink carrier sends the first message (such as MSG1 / 3 / A) and which downlink carrier receives the second message (such as MSG2 / 4 / B).

[0258] In some implementations, the terminal device sends a first message on a sixth uplink carrier and receives a second message on a sixth downlink carrier, where the first message and the second message are associated messages in a random access process.

[0259] In some embodiments, the first message is MSG1 and the second message is MSG2. Alternatively, the first message is MSG3 and the second message is MSG4. Alternatively, the first message is MSGA and the second message is MSGB.

[0260] In some implementations, the sixth uplink carrier is an uplink carrier in the at least one uplink cluster configured with PRACH resources and / or random access configuration information.

[0261] In some implementations, the sixth downlink carrier may be determined by, but is not limited to, the following methods:

[0262] Method 1: The carrier index or carrier number of the sixth downlink carrier is determined based on a random access sequence and a second parameter, where the second parameter is the number of downlink carriers configured by the first configuration information.

[0263] As an example, the downlink carrier for receiving the second message may be determined by the following formula:

[0264] preamble mod K1=DL carrier index;

[0265] Among them, DL carrier index is the carrier index or carrier number of the downlink carrier on which the terminal device receives the second message (the carrier number refers to the sequence number of all configured carriers from small to large), preamble is the random access series selected by the terminal device for initiating random access, and K1 is the number of all configured downlink carriers.

[0266] Method 2: The carrier index or carrier number of the sixth downlink carrier is determined based on the random access series and the fifth parameter, the fifth parameter is the number of downlink carriers in the first downlink carrier list, and the first downlink carrier list is a downlink carrier list configured by the network device for receiving the second message.

[0267] As an example, the downlink carrier for receiving the second message may be determined by the following formula:

[0268] preamble mod K2=DL carrier index;

[0269] Among them, DL carrier index is the carrier index or carrier number of the downlink carrier on which the terminal device receives the second message (the carrier number refers to the sequence number of all configured carriers from small to large), preamble is the random access series selected by the terminal device for initiating random access, and K2 is the number of downlink carriers in the downlink carrier list configured for receiving the second message.

[0270] Mode three: the sixth downlink carrier is a downlink carrier configured by a network device and associated with the sixth uplink carrier.

[0271] Here, the network device may configure a downlink carrier associated with the sixth uplink carrier, and the downlink carrier is used for the terminal device to receive the second message.

[0272] Mode 4: the sixth downlink carrier is a downlink carrier of at least one downlink carrier associated with a random access sequence and / or a PRACH resource.

[0273] Here, the network device may configure a random access series (ie, preamble code) and / or at least one downlink carrier associated with a PRACH resource, and the at least one associated downlink carrier is used for the terminal device to receive the second message.

[0274] In some embodiments, the terminal device uses RA-RNTI to receive a second message on a sixth downlink carrier, and the RA-RNTI is calculated based on a sixth parameter and / or a seventh parameter, the value of the sixth parameter is configured by a network device or is the carrier index of the sixth uplink carrier or is the carrier index of the sixth uplink carrier plus a first offset (such as 2), and the value of the seventh parameter is configured by a network device or is the cluster index of the uplink cluster where the sixth uplink carrier is located.

[0275] As an example: the second message is MSG2 or MSGB, the terminal device uses RA-RNTI to monitor the RA-RNTI-scrambled DCI on the sixth downlink carrier, and the RA-RNTI-scrambled DCI is used to schedule MSG2 or MSGB, and then the terminal device receives MSG2 or MSGB according to the RA-RNTI-scrambled DCI. When the carrier indexes in different clusters are in the same numbering space, the terminal device can calculate the RA-RNTI using the following formula:

[0276] RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id;

[0277] Where s_id is the index of the first OFDM symbol of the PRACH resource (0≤s_id<14);

[0278] t_id is the index of the first time slot of the PRACH resource in the system frame (0≤t_id<80);

[0279] f_id is the index of the PRACH opportunity in the frequency domain (0≤f_id<8);

[0280] ul_carrier_id is the carrier index of the uplink carrier used to transmit the first message.

[0281] To avoid RA-RNTI conflicts, the terminal device needs to consider the carrier index of the uplink carrier when calculating the RA-RNTI. If the concepts of normal uplink carrier (NUL) and supplementary uplink carrier (SUL) in NR are maintained in future communication systems (such as 6G) and the cell where the terminal device is located is a backward compatibility cell, the values ​​of ul_carrier_id need to be reserved as 0 and 1 to ensure that RA-RNTI conflicts do not occur during random access of terminal devices in the RRC idle state. At the same time, it is also necessary to consider the problem of RA-RNTI conflict when multiple terminal devices configured with a cluster initiate a random access process at the same time and receive the second message on the same downlink carrier. Therefore, for terminal devices configured with a cluster, after initiating random access on an uplink carrier, the value of ul_carrier_id used to calculate RA-RNTI is based on the value that can be configured based on the network device, or the value of ul_carrier_id is the carrier index of the uplink carrier, or the value of ul_carrier_id is the carrier index of the uplink carrier plus an offset (such as 2). At this time, the network device needs to coordinate the configuration of the carrier index of the uplink carrier to ensure that the RA-RNTI calculation between terminal devices does not conflict.

[0282] As an example: the second message is MSG2 or MSGB, the terminal device uses RA-RNTI to monitor the RA-RNTI-scrambled DCI on the sixth downlink carrier, and the RA-RNTI-scrambled DCI is used to schedule MSG2 or MSGB, and then the terminal device receives MSG2 or MSGB according to the RA-RNTI-scrambled DCI. When the carrier indexes in different clusters are in independent numbering spaces, the terminal device can calculate the RA-RNTI using the following formula:

[0283] RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id+14×80×8×max_ul_carrier_id×cluster_id;

[0284] Where s_id is the index of the first OFDM symbol of the PRACH resource (0≤s_id<14);

[0285] t_id is the index of the first time slot of the PRACH resource in the system frame (0≤t_id<80);

[0286] f_id is the index of the PRACH opportunity in the frequency domain (0≤f_id<8);

[0287] ul_carrier_id is the carrier index of the uplink carrier used to transmit the first message;

[0288] max_ul_carrier_id is the maximum number of uplink carriers in a cluster or the value of max_ul_carrier_id is configured by the network device;

[0289] cluster_id is the cluster index of the cluster where the uplink carrier used to transmit the first message belongs.

[0290] Solution 2: Members participating in carrier aggregation are based on the cell granularity

[0291] Cluster Configuration

[0292] In some embodiments, the first configuration information is used to configure at least one cluster, each of the at least one cluster including at least one cell.

[0293] Here, each cluster in the at least one cluster is associated with a cluster index. The numbering of the cluster indexes satisfies the following constraint: the cluster indexes of the clusters in the at least one cluster are in the same numbering space.

[0294] It should be noted that cluster indexes in the same numbering space do not overlap.

[0295] Here, each cell in the at least one cell is associated with a cell index. Here, the cell index can be a serving cell index, a secondary cell index, or a carrier index, etc. The numbering of the carrier index satisfies the following constraints:

[0296] Constraint 1) The cell indexes of at least one cell in the same cluster are in the same numbering space.

[0297] Constraint 2) Option 1) The cell indexes of cells in different clusters are in independent numbering spaces; or, Option 2) The cell indexes of cells in different clusters are in the same numbering space.

[0298] In some implementations, the terminal device reports first capability information of the terminal device to the network device, and the network device receives the first capability information reported by the terminal device, where the first capability information includes at least one of the following:

[0299] first information, where the first information is used to indicate a cluster-supporting capability of the terminal device;

[0300] second information, where the second information is used to indicate a maximum number of clusters supported by the terminal device;

[0301] third information, where the third information is used to indicate a maximum number of cells included in a cluster supported by the terminal device;

[0302] Fourth information, the fourth information is used to indicate the frequency band combination of the cluster supported by the terminal device.

[0303] The network device may configure the at least one cluster for the terminal device according to the first capability information reported by the terminal device.

[0304] In the embodiment of the present application, cells within the same cluster are downlink synchronized and / or uplink synchronized.

[0305] For each cluster, the terminal device performs downlink synchronization and / or uplink synchronization for the cluster based on a first cell in the cluster. Here, the first cell is any cell in the cluster or a designated cell in the cluster, and the designated cell is a cell indicated by a network device or a default cell.

[0306] In some implementations, the terminal device uses a first random access resource to initiate a random access process to a first cell in the cluster to achieve uplink synchronization; the first random access resource is a random access resource configured by the network device specifically for the cluster.

[0307] FIG8 is a flow chart of a cluster configuration, which takes a terminal device as a UE as an example and a network device including one or more sites (such as a base station) as an example. As shown in FIG8 , the process includes the following steps:

[0308] Step 801: The UE sends an RRC establishment request message to a network device.

[0309] Here, when a UE in an RRC idle state resides in a cell, the UE initiates an RRC connection establishment process due to a paging or uplink data arrival triggering the UE.

[0310] Here, optionally, the downlink carrier of the cell where the UE initiates the RRC connection establishment process can serve as the cluster head of a downlink cluster. The UE can complete downlink synchronization for the cell in the RRC idle state, and then obtain the configuration information of the cell, and perform a random access process for the cell based on the configuration information of the cell (for example, the associated uplink carrier configured through the system broadcast information of the cell), for example, sending MSG1 to the cell, receiving MSG2 sent by the cell, sending MSG3 (i.e., RRC establishment request message) to the cell, and receiving MSG4 (i.e., RRC establishment message) sent by the cell.

[0311] Step 802: The network device sends an RRC establishment message to the UE.

[0312] Step 803: After entering the RRC connected state, the UE sends an RRC setup complete message to the network device point.

[0313] Here, after the UE completes the random access process and the RRC connection establishment process, the UE enters the RRC connected state.

[0314] Step 804: The network device interacts with the core network to perform an initial context establishment process.

[0315] Step 805: The UE interacts with the network device to perform the UE capability reporting process.

[0316] Step 806: The UE interacts with the network device to perform the AS layer security activation process.

[0317] Step 807: The network device knows the UE's cluster-related capabilities.

[0318] Here, the network device learns the UE's cluster capability through the first capability information reported by the UE, where the first capability information includes at least one of the following:

[0319] first information, where the first information is used to indicate a cluster-supporting capability of the terminal device;

[0320] second information, where the second information is used to indicate a maximum number of clusters supported by the terminal device;

[0321] third information, where the third information is used to indicate a maximum number of cells included in a cluster supported by the terminal device;

[0322] Fourth information, the fourth information is used to indicate the frequency band combination of the cluster supported by the terminal device.

[0323] Step 808: The network device sends an RRC reconfiguration message to the UE, carrying configuration information of at least one cluster (ie, first configuration information).

[0324] Here, after the UE capability reporting and AS layer security activation are completed between the UE and the access network, the network device completes the configuration of at least one cluster and the configuration of the cells in each cluster through the RRC reconfiguration message.

[0325] Here, the network device may configure at least one cluster for the UE according to the UE's cluster-related capabilities.

[0326] Step 809: The UE sends an RRC reconfiguration completion message to the first site.

[0327] Step 810: The UE performs downlink synchronization and / or uplink synchronization with the cluster.

[0328] Here, the UE will randomly select a cell from the cluster to perform downlink synchronization and / or uplink synchronization for the cluster, or it may perform downlink synchronization and / or uplink synchronization for the cluster according to the cell indicated by the network device, or it may perform downlink synchronization and / or uplink synchronization for the cluster according to the default cell.

[0329] Here, the UE can achieve uplink synchronization through a random access process. The network device can configure dedicated random access resources for the cluster. The UE uses the dedicated random access resources to initiate a random access process to a cell in the cluster, thereby quickly achieving uplink synchronization for the cluster.

[0330] Step 811: The UE receives and / or sends data through the cluster.

[0331] Cluster Management

[0332] A) Add / Modify / Release Clusters

[0333] In some implementations, the network device sends second configuration information to the terminal device, and the terminal device receives the second configuration information sent by the network device, where the second configuration information is used to configure at least one of the following:

[0334] Add one or more clusters;

[0335] Modify one or more clusters;

[0336] Releases one or more clusters.

[0337] In some implementations, the second configuration information is carried in RRC signaling.

[0338] Here, for the cluster, the network device may implement cluster management through RRC signaling, where the management includes at least one of the following: adding, modifying, and releasing.

[0339] B) Cluster status

[0340] In some embodiments, the first configuration information is further used to configure an initial state of each cluster in the at least one cluster; or the initial state of each cluster in the at least one cluster is an activated state or a deactivated state by default.

[0341] Here, the initial state of the cluster can be configured as an activated state or a deactivated state through RRC signaling. Alternatively, the initial state of the cluster is defaulted to the activated state or the deactivated state.

[0342] In some implementations, the network device sends a first command to the terminal device, and the terminal device receives the first command sent by the network device, where the first command is used to activate and / or deactivate at least some of the at least one cluster. As an example, the first command includes at least one of the following: DCI, MAC CE.

[0343] Here, the implementation of the first command may include but is not limited to the following:

[0344] Mode 1: The first command is used to activate and / or deactivate a cluster.

[0345] The first command carries a cluster index and second indication information, where the second indication information is used to indicate whether to activate or deactivate the cluster indicated by the cluster index.

[0346] Here, the network device may activate or deactivate a cluster through a layer 1 (L1) or layer 2 (L2) command, wherein the L1 command is, for example, a DCI, and the L2 command is, for example, a MAC CE.

[0347] Taking the L2 command as an example, the format of the MAC CE used to activate and / or deactivate the cluster can refer to Figure 9, as shown in Figure 9: the cluster index is used to indicate the cluster that needs to be activated or deactivated; the A / D field (corresponding to the second indication information) is used to indicate whether the cluster is activated or deactivated.

[0348] Mode 2: The first command is used to activate and / or deactivate one or more clusters.

[0349] The first command carries a first bitmap, each bit in the first bitmap corresponds to one or more cluster indexes, and the value of the bit is used to indicate whether one or more clusters indicated by the corresponding one or more cluster indexes are activated or deactivated.

[0350] Here, the network device can activate or deactivate one or more clusters through layer 1 (L1) or layer 2 (L2) commands, where the L1 command is, for example, a DCI, and the L2 command is, for example, a MAC CE.

[0351] Taking the L2 command as an example, the format of the MAC CE used to activate and / or deactivate the cluster can refer to Figure 10, as shown in Figure 10: a bit map, each bit in the bit map corresponds to a cluster index, CLi indicates that the cluster index is i, and the bit map in Figure 10 includes 8 bits, but is not limited to this. The number of bits occupied by the bit map can be adjusted according to the number of clusters that need to be indicated, and the value of each bit is used to indicate whether the cluster indicated by the corresponding cluster index is activated or deactivated.

[0352] Cluster membership management

[0353] A) Adding / modifying / releasing cluster members

[0354] In some implementations, the network device sends third configuration information to the terminal device, and the terminal device receives the third configuration information sent by the network device, where the third configuration information is used to configure at least one of the following:

[0355] Add one or more cells to the cluster;

[0356] Modifying one or more cells in a cluster;

[0357] Release one or more cells in a cluster.

[0358] In some implementations, the third configuration information is carried in RRC signaling.

[0359] Here, for cells in a cluster, network devices can manage the cells in the cluster through RRC signaling. This management includes at least one of the following: adding, modifying, and releasing. It should be noted that if a cluster is released, all cells in the cluster are also released. If a cluster is deactivated, all cells in the cluster are also deactivated.

[0360] B) Status of cluster members

[0361] In some embodiments, the first configuration information is further used to configure an initial state of a cell in each of the at least one cluster; or the initial state of a cell in each of the at least one cluster is an activated state or a deactivated state by default.

[0362] Here, the initial state of the cells in the cluster can be configured as an activated state or a deactivated state through RRC signaling. Alternatively, the initial state of the cells in the cluster is defaulted to an activated state or a deactivated state.

[0363] In some embodiments, the network device sends a second command to the terminal device, and the terminal device receives the second command sent by the network device, where the second command is used to activate and / or deactivate at least some cells in the at least one cluster. As an example, the second command includes at least one of the following: DCI, MAC CE.

[0364] Here, the implementation of the second command may include but is not limited to the following:

[0365] Method 1: The second command is used to activate and / or deactivate a cell.

[0366] Mode 1-1) The second command carries a cluster index, a cell index, and fourth indication information, where the fourth indication information is used to indicate whether to activate or deactivate the cell indicated by the cell index, wherein the cell indexes in different clusters are in independent numbering spaces; or

[0367] Mode 1-2) The second command carries a cell index and fourth indication information, and the fourth indication information is used to indicate whether to activate or deactivate the cell indicated by the cell index, wherein the cell indexes in different clusters are in the same numbering space.

[0368] Here, the network device may activate or deactivate a cell through a layer 1 (L1) or layer 2 (L2) command, wherein the L1 command is, for example, a DCI, and the L2 command is, for example, a MAC CE.

[0369] Taking L2 commands as an example, the format of the MAC CE used to activate and / or deactivate a cell may refer to FIG11 , as shown in FIG11 :

[0370] In approach 1-1), the cluster index indicates the cluster index of the cell to be activated or deactivated; the cell index indicates the cell to be activated or deactivated; and the A / D field (corresponding to the fourth indication information) indicates whether the cell is to be activated or deactivated. Cell indexes in different clusters are in independent numbering spaces.

[0371] In mode 1-2), the cell index is used to indicate the cell to be activated or deactivated; the A / D field (corresponding to the fourth indication information) is used to indicate whether the cell is to be activated or deactivated. The cell indexes in different clusters are in the same numbering space.

[0372] Method 2: The second command is used to activate and / or deactivate one or more cells.

[0373] Mode 2-1) The second command carries a cluster index and a second bitmap, where each bit in the second bitmap corresponds to one or more cell indexes, and the value of the bit is used to indicate whether the one or more cells indicated by the corresponding one or more cell indexes are activated or deactivated, wherein the cell indexes in different clusters are in independent numbering spaces; or

[0374] Method 2-2) The second command carries a second bit map, each bit in the second bit map corresponds to one or more cell indexes, and the value of the bit is used to indicate whether one or more cells indicated by the corresponding one or more cell indexes are activated or deactivated, wherein the cell indexes in different clusters are in the same numbering space.

[0375] Here, the network device may activate or deactivate one or more cells through a layer 1 (L1) or layer 2 (L2) command, wherein the L1 command is, for example, a DCI, and the L2 command is, for example, a MAC CE.

[0376] Taking L2 commands as an example, the format of the MAC CE used to activate and / or deactivate a cell may refer to FIG12 , as shown in FIG12 :

[0377] In approach 2-1), the cluster index indicates the cluster index of the cell to be activated or deactivated; the bitmap corresponds to a cell index, where Ci represents cell index i. The number of bits in the bitmap in Figure 12 is only an example and can be adjusted based on the number of cells to be indicated. The value of each bit indicates whether the cell indicated by the corresponding cell index is to be activated or deactivated. Cell indexes in different clusters are in independent numbering spaces.

[0378] In approach 2-2), a bitmap is used, where each bit corresponds to a cell index, Ci represents cell index i. The number of bits occupied by the bitmap in FIG12 is only an example, and the number of bits may be adjusted based on the number of cells to be indicated. The value of each bit indicates whether the cell indicated by the corresponding cell index is activated or deactivated. Cell indexes in different clusters are in the same numbering space.

[0379] In some embodiments, cells within a cluster have at least one of the following characteristics:

[0380] Feature 1: For a deactivated cell, the behavior of the terminal device on the cell includes at least one of the following: not monitoring PDCCH, not receiving PDSCH, performing CSI measurement, performing beam measurement, not sending PUSCH, not sending PUCCH, and not sending SRS.

[0381] Feature 2: For a deactivated cell, whether the cell supports the sending and / or receiving of the first signal and / or the second signal is determined based on the configuration of the network device, and the first signal includes at least one of the following: PDCCH, PDSCH, SSB, CSI-RS, and the second signal includes at least one of the following: PUCCH, PUSCH, SRS, PRACH.

[0382] Here, after the cell is deactivated, the terminal device does not monitor PDCCH, does not receive PDSCH, and does not send PUSCH on the cell. Optionally, the terminal device can perform CSI measurement on the cell, or it depends on the configuration of the network device to determine whether to perform CSI measurement on the cell. Optionally, the terminal device can perform beam measurement on the cell, or it depends on the configuration of the network device to determine whether to perform beam measurement on the cell. Optionally, the terminal device does not send PUCCH on the cell, or it depends on the configuration of the network device to determine whether to send PUCCH on the cell. Optionally, the terminal device does not send SRS on the cell, or it depends on the configuration of the network device to determine whether to send SRS on the cell.

[0383] Scheduling of cluster members

[0384] In some implementations, for each configured cell, the presence of PDCCH, PDSCH, SSB, CSI-RS, PUCCH, PUSCH, SRS, PRACH, etc. may be determined based on the configuration of the network device. The cell may support self-scheduling, intra-cluster cross-carrier scheduling, or inter-cluster cross-carrier scheduling (i.e., cross-cluster and cross-carrier scheduling).

[0385] In some implementations, the cell supports at least one of the following scheduling modes:

[0386] Same-carrier scheduling mode (also known as self-scheduling mode), wherein the same-carrier scheduling mode is that the DCI on the cell schedules the PDSCH on the cell;

[0387] A cross-carrier scheduling method, where the cross-carrier scheduling method is that the DCI on the cell schedules the PDSCH and / or PUSCH on the second cell.

[0388] In some embodiments, the cross-carrier scheduling mode includes a first type of cross-carrier scheduling mode and / or a second type of cross-carrier scheduling mode;

[0389] In the first type of cross-carrier scheduling mode (i.e., intra-cluster cross-carrier scheduling mode), the cell and the scheduled cell belong to the same cluster, and the scheduled cell is the second cell;

[0390] In the second type of cross-carrier scheduling mode (ie, inter-cluster cross-carrier scheduling mode), the cell and the scheduled carrier belong to different clusters, and the scheduled carrier is the second cell.

[0391] In some embodiments, for the first type of cross-carrier scheduling method, the DCI on the cell carries the cell index of the scheduled cell (or the identification information of the scheduled cell); or, the relationship between the cell and the scheduled cell is configured through RRC signaling.

[0392] In some embodiments, for the second type of cross-carrier scheduling method, the DCI on the cell carries the cluster index of the cluster where the scheduled cell is located (or the identification information of the cluster where the scheduled cell is located) and the cell index of the scheduled cell (or the identification information of the scheduled cell), wherein the cell indexes in different clusters are in independent numbering spaces; or, the DCI on the cell carries the cell index of the scheduled cell, wherein the cell indexes in different clusters are in the same numbering space; or, the relationship between the cell and the scheduled cell is configured through RRC signaling.

[0393] In the above scheme, for the cross-carrier scheduling mode, the relationship between the scheduling cell and the scheduled cell can be configured through RRC signaling, or the relationship between the scheduling cell and the scheduled cell is flexible and variable, and the scheduled cell is dynamically indicated through DCI.

[0394] HARQ feedback on cluster members

[0395] In some embodiments, for a third cell in the at least one cluster, HARQ feedback information of a PDSCH on the third cell is transmitted via a PUCCH on a fourth cell.

[0396] Here, the fourth cell is configured through RRC signaling; or, the fourth cell is indicated by scheduling the DCI of the third cell.

[0397] In some embodiments, when the fourth cell is indicated by scheduling the DCI of the third cell, the DCI for scheduling the third cell carries the cluster index of the cluster where the fourth cell is located and the cell index of the fourth cell, wherein the cell indexes in different clusters are in independent numbering spaces; or, the DCI for scheduling the third cell carries the cell index of the fourth cell, wherein the cell indexes in different clusters are in the same numbering space.

[0398] Here, for downlink feedback (i.e., HARQ feedback for PDSCH), PUCCH can be configured on one or more configured cells for HARQ feedback. Method 1: On which cell's PUCCH the HARQ feedback information of the PDSCH of a cell is transmitted can be configured through RRC signaling, for example: a PUCCH group is configured through RRC signaling, and the HARQ feedback information of all cells in the PUCCH group is transmitted through the same PUCCH. For the case of semi-persistent scheduling (SPS), it is also possible to configure through RRC signaling which cell's PUCCH is used for HARQ feedback. Method 2: On which cell's PUCCH the HARQ feedback information of the PDSCH of a cell is transmitted can be indicated by the DCI that schedules the PDSCH, for example, the DCI indicates the cell index of the cell and / or the cluster index of the cluster where the cell is located.

[0399] TB transfer on cluster members

[0400] In current CA, members participating in carrier aggregation correspond to the same MAC entity, each member corresponds to a HARQ entity, and each HARQ entity has multiple HARQ processes. When a TB is initially transmitted on a member, if the transmission fails (i.e., a HARQ NACK occurs), the subsequent retransmission of the TB can only be performed on this member (even if the channel conditions of this member are very poor). This is because the data in a HARQ process in a HARQ entity must be associated for combined decoding. If the TB is retransmitted by changing the member, it is equivalent to retransmitting across HARQ entities, and the association between the initial and retransmitted data cannot be achieved.

[0401] To ensure that the TB can be effectively received by the receiving end, it is necessary to select members with better conditions to transmit the TB. The following implementation solutions can be used:

[0402] In some embodiments, the terminal device receives a first TB on the fifth cell, and if the number of retransmissions of the first TB exceeds a first threshold value, the terminal device receives the first TB on the sixth cell; and / or, the terminal device sends a second TB on the fifth cell, and if the number of retransmissions of the second TB exceeds a second threshold value, the terminal device sends the second TB on the sixth cell.

[0403] To ensure that TB can be effectively decoded by the receiving end, the following implementation solutions are available:

[0404] A) TB's new biography

[0405] In some embodiments, the first TB on the sixth cell is newly transmitted data; and / or the second TB on the sixth cell is newly transmitted data.

[0406] In some embodiments, the terminal device receives first DCI on the fifth cell, where the first DCI carries at least one of the following:

[0407] fifth information, where the fifth information is used to schedule the sixth cell to newly transmit the first TB;

[0408] The sixth information is used to instruct the network device to give up retransmitting the first TB on the fifth cell and / or instruct the terminal device to clear the cache corresponding to the first HARQ process of the fifth cell, where the first HARQ process is the HARQ process corresponding to the first TB on the fifth cell.

[0409] In some embodiments, the terminal device receives a second DCI on the fifth cell, where the second DCI carries at least one of the following:

[0410] Seventh information, where the seventh information is used to schedule the sixth cell to newly transmit the second TB;

[0411] The eighth information is used to instruct the terminal device to give up retransmitting the second TB on the fifth cell and / or instruct the terminal device to clear the cache corresponding to the second HARQ process of the fifth cell, where the second HARQ process is the HARQ process corresponding to the second TB on the fifth cell.

[0412] For the above solution, different cells correspond to different HARQ entities. Specifically, the sixth cell and the fifth cell correspond to different HARQ entities.

[0413] Here, if the number of retransmissions of a TB on a cell exceeds a certain number, a new cell may be selected to transmit the TB as new transmission data, and all transmissions of the TB on the previous cell may be abandoned.

[0414] For the downlink, assuming that a certain TB1 is transmitted in HARQ process 1 of cell 1 and the number of retransmissions exceeds n without success, the network device abandons the transmission of TB1 in HARQ process 1 of cell 1 and schedules TB2 for transmission in HARQ process 1 of cell 1. Furthermore, the network device can perform cross-carrier scheduling on cell 1 and transmit TB1 as new data in cell 2. At the same time, the network device can send a PDCCH to the terminal device, instructing the network device to abandon the retransmission of TB1 in HARQ process 1 of cell 1 through the PDCCH, and the terminal device will clear the corresponding cache of HARQ process 1 of cell 1.

[0415] For the uplink, assuming that a certain TB2 is being transmitted in HARQ process 1 of cell 1 and the number of retransmissions exceeds n without success, the network device can send a PDCCH to the terminal device, instructing the terminal device through this PDCCH to abandon the retransmission of TB2 in HARQ process 1 of cell 1. The terminal device will clear the cache corresponding to HARQ process 1 of cell 1. Furthermore, the network device can perform cross-carrier scheduling through the PDCCH and transmit TB2 as new data in cell 2. The PDCCH can directly carry the cross-carrier scheduling information or instruct the terminal device to wait for scheduling of other PDCCHs to perform the initial transmission of TB2.

[0416] B) TB retransmission

[0417] In some embodiments, the first TB on the sixth cell is retransmitted data of the first TB on the fifth cell; and / or the second TB on the sixth cell is retransmitted data of the second TB on the fifth cell.

[0418] B-1) For the above solution, the sixth cell and the fifth cell correspond to the same HARQ entity.

[0419] Here, each cell group in the at least one cluster corresponds to a HARQ entity; the sixth cell and the fifth cell belong to the same cell group, and therefore, the sixth cell and the fifth cell correspond to the same HARQ entity.

[0420] In some embodiments, the terminal device receives fourth configuration information sent by the network device, where the fourth configuration information is used to configure one or more cell groups, where each cell group corresponds to a HARQ entity.

[0421] Here, since one cell group corresponds to one HARQ entity, cross-carrier retransmission can be performed between cells in one cell group.

[0422] B-2) For the above solution, the sixth cell and the fifth cell correspond to different HARQ entities. Here, the network device can indicate cross-carrier retransmission related information to the terminal device so that the terminal device can associate the initial transmission data with the retransmission data to achieve combined decoding gain. Specifically,

[0423] The terminal device receives a third DCI on the fifth cell, where the third DCI carries at least one of the following:

[0424] Ninth information, where the ninth information is used to schedule the six cells to retransmit the first TB;

[0425] Tenth information, where the tenth information is used to indicate a HARQ process identifier corresponding to the first TB on the fifth cell;

[0426] The eleventh information is used to indicate the HARQ process identifier corresponding to the first TB in the six cells.

[0427] Here, for downlink retransmission or uplink retransmission, the network device can carry indication information in the DCI for scheduling downlink retransmission or uplink retransmission, and use the indication information to indicate that the scheduling corresponding to the DCI is the retransmission scheduling of a certain cell. For example, the DCI carries the relevant information of the scheduled cell corresponding to the downlink retransmission and the HARQ corresponding to the retransmission data of the scheduled cell to identify, and the scheduling cell identifies the HARQ for this cross-carrier retransmission scheduling. The terminal device associates the initial transmission data and the retransmission data according to the information carried in the DCI, thereby achieving combined decoding gain. For example, the DCI carries the relevant information of the scheduled cell corresponding to the uplink retransmission and the HARQ corresponding to the retransmission data of the scheduled cell to identify, and the scheduling cell identifies the HARQ for this cross-carrier retransmission scheduling. The terminal device performs cross-carrier retransmission according to the information carried in the DCI, and the network device can associate the initial transmission data and the retransmission data, thereby achieving combined decoding gain.

[0428] Random access on cluster members

[0429] In current Carrier Aggregation (CA), downlink and uplink carriers have a 1:1 binding relationship. When a terminal device performs random access on an SCell, it sends a first message (such as MSG1 / 3 / A) on the SCell's uplink carrier, but receives a second message (such as MSG2 / 4 / B) on the PCell's downlink carrier. The relationship between the downlink and uplink carriers during this random access process is clear. In cluster-based carrier aggregation, each cell has an equal identity, with no distinction between PCell and SCell identities. There is no fixed association between downlink and uplink carriers. Therefore, during random access, it is necessary to clearly determine on which cell's uplink carrier the first message (such as MSG1 / 3 / A) is sent, and on which cell's downlink carrier the second message (such as MSG2 / 4 / B) is received.

[0430] In some embodiments, the terminal device sends a first message on the seventh cell and receives a second message on the eighth cell, where the first message and the second message are associated messages in a random access process.

[0431] In some embodiments, the first message is MSG1 and the second message is MSG2. Alternatively, the first message is MSG3 and the second message is MSG4. Alternatively, the first message is MSGA and the second message is MSGB.

[0432] In some implementations, the seventh cell is a cell in the at least one cluster configured with PRACH resources and / or random access configuration information.

[0433] In some implementations, the eighth cell may be determined by, but is not limited to, the following methods:

[0434] Method 1: The cell index or cell number of the eighth cell is determined based on a random access series and a second parameter, where the second parameter is the number of cells configured by the first configuration information.

[0435] As an example, the cell for receiving the second message may be determined by the following formula:

[0436] preamble mod K3=Cell index;

[0437] Among them, Cell index is the cell index or cell number of the cell where the terminal device receives the second message (the cell number refers to the sequence number of all configured cells from small to large), preamble is the random access series selected by the terminal device for initiating random access, and K3 is the number of all configured cells.

[0438] Method 2: The cell index or cell number of the eighth cell is determined based on the random access series and the fifth parameter, where the fifth parameter is the number of cells in the first cell list, and the first cell list is a cell list configured by the network device for receiving the second message.

[0439] As an example, the cell for receiving the second message may be determined by the following formula:

[0440] preamble mod K4=Cell index;

[0441] Among them, Cell index is the cell index or cell number of the cell in which the terminal device receives the second message (the cell number refers to the sequential number of all configured cells from small to large), preamble is the random access series selected by the terminal device for initiating random access, and K4 is the number of cells in the cell list configured for receiving the second message.

[0442] Mode three: the eighth cell is a cell configured by the network device and associated with the seventh cell.

[0443] Here, the network device may configure a cell associated with the seventh cell, and the cell is used for the terminal device to receive the second message.

[0444] Mode 4: the eighth cell is one of at least one cell associated with the random access series and / or PRACH resources.

[0445] Here, the network device may configure at least one cell associated with a random access series (ie, preamble code) and / or a PRACH resource, and the at least one associated cell is used for the terminal device to receive the second message.

[0446] In some embodiments, the terminal device uses RA-RNTI to receive a second message on the eighth cell, and the RA-RNTI is calculated based on the sixth parameter and / or the seventh parameter, the value of the sixth parameter is configured by the network device or is the carrier index of the uplink carrier in the eighth cell or is the carrier index of the uplink carrier in the eighth cell plus a first bias (such as 2), and the seventh parameter is configured by the network device or is the cluster index of the cluster where the eighth cell is located.

[0447] As an example: the second message is MSG2 or MSGB, the terminal device uses RA-RNTI to monitor the RA-RNTI-scrambled DCI on the downlink carrier of the eighth cell, and the RA-RNTI-scrambled DCI is used to schedule MSG2 or MSGB, and then the terminal device receives MSG2 or MSGB according to the RA-RNTI-scrambled DCI. When the cell indexes in different clusters are in the same numbering space, the terminal device can calculate the RA-RNTI using the following formula:

[0448] RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id;

[0449] Where s_id is the index of the first OFDM symbol of the PRACH resource (0≤s_id<14);

[0450] t_id is the index of the first time slot of the PRACH resource in the system frame (0≤t_id<80);

[0451] f_id is the index of the PRACH opportunity in the frequency domain (0≤f_id<8);

[0452] ul_carrier_id is a carrier index of an uplink carrier in a cell used to transmit the first message.

[0453] To avoid RA-RNTI conflicts, the terminal device needs to consider the carrier index of the uplink carrier when calculating the RA-RNTI. If the concepts of normal uplink carrier (NUL) and supplementary uplink carrier (SUL) in NR are maintained in future communication systems (such as 6G) and the cell where the terminal device is located is a backward compatibility cell, the values ​​of ul_carrier_id need to be reserved as 0 and 1 to ensure that RA-RNTI conflicts do not occur during random access of terminal devices in the RRC idle state. At the same time, it is also necessary to consider the problem of RA-RNTI conflict when multiple terminal devices configured with a cluster initiate a random access process at the same time and receive the second message on the downlink carrier of the same cell. Therefore, after the terminal device configured with a cluster initiates random access on the uplink carrier of a cell, the value of ul_carrier_id used to calculate the RA-RNTI is based on the value that can be configured based on the network device, or the value of ul_carrier_id is the carrier index of the uplink carrier in the cell, or the value of ul_carrier_id is the carrier index of the uplink carrier in the cell plus an offset (such as 2). At this time, the network device needs to coordinate the carrier index of the uplink carrier in the cell to ensure that the RA-RNTI calculation between the terminal devices does not conflict.

[0454] As an example: the second message is MSG2 or MSGB, the terminal device uses RA-RNTI to monitor the RA-RNTI-scrambled DCI on the downlink carrier of the eighth cell, and the RA-RNTI-scrambled DCI is used to schedule MSG2 or MSGB, and then the terminal device receives MSG2 or MSGB according to the RA-RNTI-scrambled DCI. When the cell indexes in different clusters are in independent numbering spaces, the terminal device can calculate the RA-RNTI using the following formula:

[0455] RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id+14×80×8×

[0456] max_ul_cell_id×cluster_id;

[0457] Where s_id is the index of the first OFDM symbol of the PRACH resource (0≤s_id<14);

[0458] t_id is the index of the first time slot of the PRACH resource in the system frame (0≤t_id<80);

[0459] f_id is the index of the PRACH opportunity in the frequency domain (0≤f_id<8);

[0460] ul_carrier_id is the carrier index of the uplink carrier in the cell used to transmit the first message;

[0461] max_ul_cell_id is the maximum number of cells in a cluster or the value of max_ul_cell_id is configured by the network device;

[0462] cluster_id is the cluster index of the cluster where the cell used to transmit the first message belongs.

[0463] Solution 3: Deployment of a protocol stack associated with a cluster

[0464] In some embodiments, the correspondence between the at least one cluster and the MAC entity includes at least one of the following: one cluster corresponds to one MAC entity; multiple clusters correspond to one MAC entity. Furthermore, the MAC entity corresponds to one or more HARQ entities, each HARQ entity corresponding to a carrier group or cell group.

[0465] As an example: as shown in Figure 13, in case 1, one MAC entity corresponds to multiple HARQ entities, and one HARQ entity corresponds to one carrier group or cell group. In case 2, one MAC entity corresponds to multiple HARQ entities, and one HARQ entity corresponds to multiple carrier groups or cell groups.

[0466] In some embodiments, the MAC entity further includes an upper layer entity, and the upper layer entity includes at least one of the following: an RLC entity, a PDCP entity, an SDAP entity, an RRC entity, and a NAS entity; wherein,

[0467] The MAC entity and the upper layer entity are deployed in the cloud; or,

[0468] The MAC entity is deployed on the access network side, and the upper layer entity is deployed on the cloud side; or,

[0469] The MAC entity and the RLC entity are deployed on the access network side, and entities in the upper layer except the RLC entity are deployed on the cloud.

[0470] As an example: As shown in Figure 14-1, the NAS entity, RRC entity, SDAP entity, PDCP entity, RLC entity, and MAC entity are all deployed in the cloud.

[0471] As an example: As shown in Figure 14-2, the NAS entity, RRC entity, SDAP entity, PDCP entity, and RLC entity are deployed in the cloud.

[0472] As an example: As shown in Figure 14-3, the NAS entity, RRC entity, SDAP entity, and PDCP entity are deployed in the cloud.

[0473] In some embodiments, the RRC entity is associated with one or more sites; or, the RRC entity is associated with an area, where the area is an area defined by one or more cell lists or an area governed by a cloud platform.

[0474] In some implementations, the at least one cluster belongs to one or more sites. Different clusters may belong to the same site or to different sites, which is transparent to the terminal device.

[0475] Solution 4: Receiving system broadcast information

[0476] For the terminal device, the purpose of receiving the paging message is to receive the system broadcast change indication, and the purpose of receiving the system broadcast change indication is to receive updated system broadcast information.

[0477] When the system broadcast information is updated, the terminal device needs to obtain the updated system broadcast information. Here, the terminal device can obtain the updated system broadcast information in the following ways, but is not limited to:

[0478] Method 1: The terminal device receives a first RRC signaling, and the first RRC signaling is used to configure updated system broadcast information.

[0479] For this method, the terminal device does not monitor the P-RNTI-scrambled DCI and the SI-RNTI-scrambled DCI. The P-RNTI-scrambled DCI is used to schedule paging messages, the paging messages are used to carry system broadcast change indications, and the SI-RNTI-scrambled DCI is used to schedule updated system broadcast information.

[0480] Here, the P-RNTI is a UE temporary identifier used to scramble paging DCI (Paging DCI), which is used to schedule paging messages. The SI-RNTI is a UE temporary identifier used to scramble system broadcast information (DCI), which is used to schedule updated system broadcast information.

[0481] Here, for the terminal device in the RRC connection state, the updated system broadcast information can be configured to the terminal device through RRC dedicated signaling, so the terminal device in the RRC connection state does not need to receive paging messages, and naturally does not need to monitor the P-RNTI-encrypted DCI and SI-RNTI-encrypted DCI.

[0482] Method 2: The terminal device receives a second RRC signaling, and the second RRC signaling is used to configure at least one of the following: a system broadcast change indication, a target carrier or target cell where a system broadcast information change occurs, a target SIB received by the terminal device, a scheduling period of the target SIB, and a time range for the terminal device to receive the target SIB scheduling information; the terminal device monitors the SI-RNTI-encrypted DCI based on the second RRC signaling, and the SI-RNTI-encrypted DCI is used to schedule updated system broadcast information.

[0483] In this manner, the terminal device does not monitor the P-RNTI-scrambled DCI, which is used to schedule paging messages, and the paging messages are used to carry system broadcast change indications.

[0484] Here, for a terminal device in an RRC connection state, the terminal device does not monitor the P-RNTI-encrypted DCI, that is, the terminal device does not receive paging scheduling information and paging messages. The network device notifies the terminal device of the system broadcast change indication, the target carrier where the system broadcast information change occurs, or the relevant information of the target cell (such as carrier index, cell index, cluster index) through RRC dedicated signaling, and indicates the target SIB that the terminal device needs to receive, the scheduling period of the target SIB, and the time range for receiving the target SIB scheduling information, such as SFN, etc. The terminal device obtains the scheduling information of the updated system broadcast information by monitoring the SI-RNTI-encrypted DCI, and then obtains the updated system broadcast information based on the scheduling information.

[0485] Method three: The terminal device monitors the P-RNTI-scrambled DCI on the target carrier or target cell, and the P-RNTI-scrambled DCI is used to schedule paging messages. The P-RNTI-scrambled DCI and / or the paging message are used to notify at least one of the following: a system broadcast change indication, a target carrier or target cell where a system broadcast information change occurs, a target SIB received by the terminal device, a scheduling period of the target SIB, and a time range for the terminal device to receive the target SIB scheduling information; the terminal device monitors the SI-RNTI-scrambled DCI based on the P-RNTI-scrambled DCI and / or the paging message, and the SI-RNTI-scrambled DCI is used to schedule updated system broadcast information.

[0486] Here, for a terminal device in an RRC connection state, the terminal device monitors the P-RNTI-encrypted DCI on the target carrier or target cell, that is, the terminal device receives paging scheduling information and / or paging messages. The P-RNTI-encrypted DCI and / or the paging message can also notify the terminal device of a system broadcast change indication, relevant information of the target carrier or target cell where the system broadcast information change occurs (such as carrier index, cell index, cluster index), the target SIB received by the terminal device, the scheduling period of the target SIB, the time range for the terminal device to receive the target SIB scheduling information, such as SFN, etc. The terminal device obtains the scheduling information of the updated system broadcast information by monitoring the SI-RNTI-encrypted DCI, and then obtains the updated system broadcast information based on the scheduling information.

[0487] For this method, the terminal device needs to specify the target carrier or target cell. The terminal device can specify the target carrier or target cell in the following ways:

[0488] Mode I: The terminal device receives a third RRC signaling, where the third RRC signaling is used to configure:

[0489] The carrier index of the target carrier, wherein the carrier indexes in different clusters are in the same numbering space; or

[0490] The cluster index of the cluster where the target carrier is located and the carrier index of the target carrier, wherein the carrier indexes in different clusters are in independent numbering spaces; or

[0491] The cell index of the target cell, wherein the cell indexes in different clusters are in the same numbering space; or

[0492] The cluster index of the cluster where the target cell is located and the cell index of the target cell, wherein the cell indexes in different clusters are in independent numbering spaces.

[0493] Here, the network device configures relevant information of the target carrier (such as carrier index, cluster index) or relevant information of the target cell (such as cell index, cluster index) through RRC signaling.

[0494] Method II:

[0495] The target carrier can be determined as follows:

[0496] Method A-1) The terminal device determines the carrier index or carrier number of the target carrier based on a first parameter and a second parameter, wherein the first parameter is the identifier of the terminal device, and the second parameter is the number of downlink carriers configured by the first configuration information, wherein the carrier indexes in different clusters are in the same numbering space.

[0497] As an example, when the carrier indices in different clusters are in the same numbering space, a carrier can be uniquely identified by the carrier index. The target carrier for monitoring the paging DCI can be determined by the following formula:

[0498] DL carrier index=(UE ID mod N1);

[0499] Among them, DL carrier index is the carrier index or carrier number of the target carrier (the carrier number refers to the ascending order of all configured carriers), N1 is the number of all configured downlink carriers, and UE ID is the identifier of the terminal device (such as S-TMSI) or a value obtained by a certain calculation for the identifier of the terminal device (such as S-TMSI mod 1024).

[0500] Method A-2) The terminal device determines the carrier index or carrier number of the target carrier based on the first parameter and the third parameter, and determines the cluster index or cluster number of the cluster where the target carrier is located based on the first parameter and the fourth parameter, wherein the first parameter is the identifier of the terminal device, the third parameter is the number of downlink carriers in the cluster where the target carrier is located, and the fourth parameter is the number of downlink clusters configured by the first configuration information, wherein the carrier indexes in different clusters are in independent numbering spaces.

[0501] As an example, when the carrier indices in different clusters are in independent numbering spaces, a carrier needs to be uniquely identified by the carrier index and cluster index. The carrier index of the target carrier used to monitor the paging DCI and the cluster index of the cluster to which it belongs can be determined by the following formula:

[0502] DL carrier index=(UE ID mod N2);

[0503] cluster index=(UE ID mod M1);

[0504] Among them, DL carrier index is the carrier index or carrier number of the target carrier (the carrier number refers to the ascending order of all configured carriers), N2 is the number of downlink carriers configured in the cluster where the target carrier is located, UE ID is the terminal device identifier (such as S-TMSI) or a value obtained by a certain calculation of the terminal device identifier (such as S-TMSI mod 1024). Cluster index is the cluster index or cluster number of the cluster where the target carrier is located (the cluster number refers to the ascending order of all configured clusters), and M1 is the number of all configured downlink clusters.

[0505] The target cell can be determined as follows:

[0506] Method B-1) The terminal device determines the cell index or cell number of the target cell based on a first parameter and a second parameter, wherein the first parameter is the identifier of the terminal device, and the second parameter is the number of cells configured by the first configuration information, wherein the cell indexes in different clusters are in the same numbering space.

[0507] As an example, when cell indices in different clusters are in the same numbering space, a cell can be uniquely identified by the cell index. The target cell for monitoring paging DCI can be determined by the following formula:

[0508] DL cell index=(UE ID mod N3);

[0509] Among them, DL cell index is the cell index or cell number of the target cell (the cell number refers to the ascending order of all configured cells), N3 is the number of all configured cells, and UE ID is the identifier of the terminal device (such as S-TMSI) or a value obtained by a certain calculation of the identifier of the terminal device (such as S-TMSI mod 1024).

[0510] Mode B-2) The terminal device determines the cell index or cell number of the target cell based on the first parameter and the third parameter, and determines the cluster index or cluster number of the cluster where the target cell is located based on the first parameter and the fourth parameter, wherein the first parameter is the identifier of the terminal device, the third parameter is the number of cells in the cluster where the target cell is located, and the fourth parameter is the number of clusters configured by the first configuration information, wherein the cell indexes in different clusters are in independent numbering spaces.

[0511] As an example, when the cell indices in different clusters are in independent numbering spaces, a cell needs to be uniquely identified by the cell index and cluster index. The cell index of the target cell used to monitor the paging DCI and the cluster index of the cluster to which it belongs can be determined by the following formula:

[0512] DL cell index=(UE ID mod N4);

[0513] cluster index=(UE ID mod M2);

[0514] Among them, DL cell index is the cell index or cell number of the target cell (the cell number refers to the sequential number of all configured cells from small to large), N4 is the number of cells configured in the cluster where the target cell is located, UE ID is the identifier of the terminal device (such as S-TMSI) or a value obtained by a certain calculation of the identifier of the terminal device (such as S-TMSI mod 1024). Cluster index is the cluster index or cluster number of the cluster where the target cell is located (the cluster number refers to the sequential number of all configured clusters from small to large), and M2 is the number of all configured clusters.

[0515] Solution 5: Wireless Link Monitoring

[0516] In some embodiments, for a cluster configured by the first configuration information, if a radio link failure occurs in all carriers or cells in the cluster, the terminal device sends an uplink RRC signaling to the network device, and the uplink RRC signaling is used to notify the network device that a radio link failure occurs in the cluster.

[0517] In some embodiments, the terminal device receives fifth configuration information sent by the network device, and the fifth configuration information is used to configure the terminal device to trigger the terminal device to notify the target cluster of the radio link failure through uplink RRC signaling when a radio link failure occurs in the target cluster.

[0518] In some implementations, if radio link failure occurs in all clusters configured by the first configuration information, the terminal device initiates an RRC connection reestablishment process.

[0519] Here, for a cluster, if all carriers in the cluster have a radio link failure, the terminal device may be triggered to send an uplink RRC signaling to the network device, and the network device may be notified by the signaling that the cluster has an RLF. The signaling carries the cluster index of the cluster, and the network device may delete the cluster or replace it with a new cluster. Furthermore, the network device may use RRC signaling to configure which cluster has an RLF, which will trigger the terminal device to report the cluster RLF through uplink RRC signaling. Optionally, in this case, different clusters are generally located at different sites, but they are invisible to the terminal device, and the terminal device needs to report the cluster RLF to the network side. In addition, the RRC connection reestablishment process is triggered only when all clusters have an RLF.

[0520] Solution 6: Collaborative Cluster Configuration

[0521] In some embodiments, the terminal device receives first configuration information sent by a first site, where the first configuration information includes configuration information of a cluster on the first site side and configuration information of a cluster on the at least one second site side; wherein the configuration information of the cluster on the second site side is sent by the second site to the first site through a container.

[0522] In some implementations, the first site sends a cluster add request message to the second site; the first site receives a cluster add response message sent by the second site, where the cluster add response message carries a container, and the container is used to carry configuration information of the cluster on the second site side.

[0523] In some implementations, the cluster add request message carries at least one of the following:

[0524] fifth indication information, where the fifth indication information is used to indicate a bearer configuration that the second site needs to provide;

[0525] Sixth indication information, where the sixth indication information is used to indicate a protocol stack entity that the second site needs to provide.

[0526] The above solution is described below in conjunction with specific application scenarios.

[0527] In the early days of NR deployment, complete NR coverage was difficult to achieve, resulting in a typical network coverage model consisting of wide-area LTE coverage and NR island coverage. Furthermore, a large number of LTE deployments operate below 6 GHz, leaving limited spectrum available for 5G. Therefore, NR needs to explore spectrum applications above 6 GHz, as high-frequency bands have limited coverage and rapid signal fading. To protect mobile operators' initial investments in LTE and to accelerate 5G network deployment and commercial applications, a tight interworking model between LTE and NR has been proposed. With 6G deployment, high-frequency spectrum will also be used, even higher than that of 5G. Therefore, a tight interworking model between 6G and 4G can achieve rapid commercialization of 6G while minimizing the impact of high-frequency 6G on mobile communication performance. Some countries have not yet achieved full 4G coverage, while others have achieved full 5G coverage, so a tight interworking model between 5G and 6G is also needed. Whether it is tight interworking between 4G and 6G or tight interworking between 5G and 6G, if the terminal device originally resides or RRC is connected to the 4G / 5G network, in order to reduce the impact on the 4G / 5G protocol, especially the air interface protocol, you can choose to implement the network architecture based on EN-DC and NE-DC. If the terminal device resides or RRC is connected on the 6G network side, tight interworking between 6G and other RATs can be implemented based on the cluster mechanism. Here, other RATs can be 4G, 5G, 6G, or even WIFI nodes. Figure 15 shows a flowchart for implementing tight interworking between a first site and at least one second site based on a cluster mechanism. As an example, the first site can be a 6G base station, and the at least one second site includes at least one of the following: one or more 6G base stations, one or more 5G base stations, one or more 4G base stations, etc. As shown in Figure 15, the following steps are included:

[0528] Step 1501: A first station sends a cluster add request message to at least one second station.

[0529] In some implementations, the cluster add request message carries at least one of the following:

[0530] fifth indication information, where the fifth indication information is used to indicate a bearer configuration that the second site needs to provide;

[0531] Sixth indication information, where the sixth indication information is used to indicate a protocol stack entity that the second site needs to provide.

[0532] Step 1502: Each second station of the at least one second station sends a cluster addition response message to the first station.

[0533] Here, the cluster add response message carries the configuration information of at least one cluster on the second site side. To reduce the coupling between the first site and the second site, the cluster configuration information can be configured in the form of a container. That is, the first site does not need to understand the cluster configuration information from the second site and directly forwards the cluster configuration information of the second site to the terminal device.

[0534] Step 1503: The first site sends an RRC reconfiguration message to the UE, carrying cluster configuration information.

[0535] Step 1504: The UE sends an RRC reconfiguration completion message to the first site.

[0536] Step 1505: The UE performs uplink synchronization and / or downlink synchronization with the cluster on the first site side.

[0537] Here, when cluster members are based on carrier granularity, the clusters are divided into downlink clusters and uplink clusters. The UE needs to perform downlink synchronization with the downlink cluster on the first site side and / or perform uplink synchronization with the uplink cluster on the first site side. The specific implementation of synchronization can refer to the description of the related solutions above.

[0538] Here, when the cluster members are in cell granularity, the UE performs downlink synchronization and / or uplink synchronization with the cluster on the first site side. The specific implementation of synchronization can refer to the description of the above-mentioned related solutions.

[0539] Step 1506: The UE performs uplink synchronization and / or downlink synchronization with the cluster on the second site side.

[0540] Here, when cluster members are based on carrier granularity, the clusters are divided into downlink clusters and uplink clusters. The UE needs to perform downlink synchronization with the downlink cluster on the second site side and / or perform uplink synchronization with the uplink cluster on the second site side. The specific implementation of synchronization can refer to the description of the related solutions above.

[0541] Here, when the cluster members are based on the cell granularity, the UE performs downlink synchronization and / or uplink synchronization with the cluster on the second site side. The specific implementation of synchronization can refer to the description of the above-mentioned related solutions.

[0542] Step 1507: The UE receives and / or sends data through the cluster.

[0543] In the above scheme, the network device can configure the cluster and manage the cluster and cluster members (such as adding, deleting, modifying, etc.) through RRC dedicated signaling based on RRM measurement reporting. At the same time, the activation and deactivation of the cluster and cluster members can be achieved through L1 or L2 commands. In this process, there is basically no key change involved, and the frequency of MAC reset and L2 protocol entity reconstruction depends on the network side architecture and the deployment of the protocol entity. Under the network side architecture and protocol entity deployment architecture designed in the embodiment of the present application, the frequency of MAC reset and L2 protocol entity reconstruction can be reduced or even avoided, and the terminal device can improve the mobility robustness when communicating in this scenario.

[0544] It should be noted that the above-mentioned solutions 1 to 6 can be implemented independently or in any combination. For example, any one or more of the above-mentioned solutions 3 to 6 can be implemented in combination with the above-mentioned solution 1 or solution 2.

[0545] The technical solution of the embodiment of the present application realizes carrier aggregation in a cluster manner. The members participating in the carrier aggregation are based on the granularity of carriers or cells, and the identities between carriers or cells are equal. The terminal equipment can improve the mobility robustness when communicating in this scenario; in addition, when the members participating in the carrier aggregation are based on the granularity of carriers, since there is no need to bind the uplink carrier and the downlink carrier together for aggregation (that is, the uplink carrier and the downlink carrier are decoupled during the aggregation process), the carrier aggregation is more flexible and can adapt to different business needs.

[0546] The preferred embodiments of the present application are described in detail above in conjunction with the accompanying drawings. However, the present application is not limited to the specific details in the above embodiments. Within the technical concept of the present application, the technical solution of the present application can be subjected to a variety of simple modifications, and these simple modifications all fall within the scope of protection of the present application. For example, the various specific technical features described in the above specific embodiments can be combined in any suitable manner without contradiction. In order to avoid unnecessary repetition, the present application will no longer describe the various possible combinations separately. For another example, the various different embodiments of the present application can also be arbitrarily combined, as long as they do not violate the idea of ​​the present application, they should also be regarded as the contents disclosed in the present application. For another example, under the premise of no conflict, the various embodiments and / or the technical features in each embodiment described in the present application can be arbitrarily combined with the prior art, and the technical solution obtained after the combination should also fall within the scope of protection of the present application.

[0547] It should also be understood that in the various method embodiments of the present application, the sequence numbers of the above-mentioned processes do not imply a precedence in 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 embodiments of the present application. In addition, in the embodiments of the present application, the terms "downlink," "uplink," and "sidelink" are used to indicate the transmission direction of signals or data, where "downlink" is used to indicate the first direction of transmission of signals or data from a site to a user equipment in a cell, "uplink" is used to indicate the second direction of transmission of signals or data from a user equipment in a cell to a site, and "sidelink" is used to indicate the third direction of transmission of signals or data from user equipment 1 to user equipment 2. For example, "downlink signal" indicates that the transmission direction of the signal is the first direction. In addition, in the embodiments of the present application, the term "and / or" is merely a description of the association relationship between associated objects, indicating that three relationships can exist. Specifically, A and / or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone. In addition, the character " / " in this document generally indicates that the associated objects are in an "or" relationship.

[0548] FIG16 is a first schematic diagram of the structure of a carrier aggregation apparatus provided in an embodiment of the present application, which is applied to a terminal device. As shown in FIG16 , the carrier aggregation apparatus includes:

[0549] The receiving unit 1601 is configured to receive first configuration information sent by a network device, where the first configuration information is used to configure at least one cluster, where each cluster in the at least one cluster includes at least one carrier or at least one cell.

[0550] In some implementations, the at least one cluster includes at least one downlink cluster and / or at least one uplink cluster, each downlink cluster includes at least one downlink carrier, and each uplink cluster includes at least one uplink carrier.

[0551] In some implementations, the apparatus further includes: a sending unit 1602, configured to report first capability information of the terminal device to the network device, where the first capability information includes at least one of the following:

[0552] First information, where the first information is used to indicate a capability of the terminal device to support a downlink cluster and / or a capability of the terminal device to support an uplink cluster;

[0553] Second information, where the second information is used to indicate a maximum number of downlink clusters and / or a maximum number of uplink clusters supported by the terminal device;

[0554] Third information, where the third information is used to indicate a maximum number of downlink carriers included in a downlink cluster and / or a maximum number of uplink carriers included in an uplink cluster supported by the terminal device;

[0555] Fourth information, the fourth information is used to indicate the frequency band combination of the downlink cluster and / or uplink cluster supported by the terminal device.

[0556] In some embodiments, each cluster in the at least one downlink cluster and / or the at least one uplink cluster is associated with a cluster index.

[0557] In some implementations, each downlink carrier in the at least one downlink carrier is associated with a downlink carrier index; and / or each uplink carrier in the at least one uplink carrier is associated with an uplink carrier index.

[0558] In some implementations, downlink carriers within the same downlink cluster are downlink synchronized; and / or uplink carriers within the same uplink cluster are uplink synchronized.

[0559] In some embodiments, the device further includes: a synchronization unit configured to, for each downlink cluster, perform downlink synchronization for the downlink cluster based on the first downlink carrier in the downlink cluster; and / or, for each uplink cluster, perform uplink synchronization for the uplink cluster based on the first uplink carrier in the uplink cluster.

[0560] In some embodiments, the first downlink carrier is any one of the downlink carriers in the downlink cluster or a designated downlink carrier in the downlink cluster, and the designated downlink carrier is a downlink carrier indicated by a network device or a default downlink carrier; and / or, the first uplink carrier is any one of the uplink carriers in the uplink cluster or a designated uplink carrier in the uplink cluster, and the designated uplink carrier is an uplink carrier indicated by a network device or a default uplink carrier.

[0561] In some implementations, the sending unit 1602 is configured to initiate a random access process to a first uplink carrier in the uplink cluster using a first random access resource to achieve uplink synchronization; the first random access resource is a random access resource dedicated to the uplink cluster and configured by the network device.

[0562] In some implementations, the receiving unit 1601 is configured to receive second configuration information sent by the network device, where the second configuration information is used to configure at least one of the following:

[0563] Add one or more downlink clusters and / or add one or more uplink clusters;

[0564] Modifying one or more downlink clusters and / or modifying one or more uplink clusters;

[0565] One or more downlink clusters are released and / or one or more uplink clusters are released.

[0566] In some embodiments, the first configuration information is further used to configure the initial state of each cluster in the at least one downlink cluster and / or the at least one uplink cluster; or, the initial state of each cluster in the at least one downlink cluster and / or the at least one uplink cluster defaults to an activated state or a deactivated state.

[0567] In some implementations, the receiving unit 1601 is configured to receive a first command sent by the network device, where the first command is used to activate and / or deactivate at least part of the at least one downlink cluster and / or at least one uplink cluster.

[0568] In some embodiments, the first command includes at least one of the following: DCI, MAC CE.

[0569] In some embodiments, the first command carries a cluster index, first indication information, and second indication information, the first indication information being used to indicate whether activation or deactivation is performed for the downlink or for the uplink, and the second indication information being used to indicate whether activation or deactivation is performed for the cluster indicated by the cluster index, wherein the cluster index of the downlink cluster and the cluster index of the uplink cluster are in independent numbering spaces; or, the first command carries a cluster index and a second indication information, the second indication information being used to indicate whether activation or deactivation is performed for the cluster indicated by the cluster index, wherein the cluster index of the downlink cluster and the cluster index of the uplink cluster are in the same numbering space; or, the first command carries a cluster index and a second indication information, the second indication information being used to indicate whether activation or deactivation is performed for the cluster indicated by the cluster index, wherein the cluster index of the downlink cluster and the cluster index of the uplink cluster are in independent numbering spaces, and the associated information of the first command is used to determine whether activation or deactivation is performed for the downlink or for the uplink.

[0570] In some embodiments, the first command carries a first bit map and first indication information, each bit in the first bit map corresponds to one or more cluster indexes, the value of the bit is used to indicate whether one or more clusters indicated by the corresponding one or more cluster indexes are activated or deactivated, and the first indication information is used to indicate whether activation or deactivation is performed for the downlink or for the uplink, wherein the cluster index of the downlink cluster and the cluster index of the uplink cluster are in an independent numbering space; or, the first command carries a first bit map, each bit in the first bit map corresponds to one or more cluster indexes, the value of the bit is used to indicate whether one or more clusters indicated by the corresponding one or more cluster indexes are activated or deactivated, wherein the cluster index of the downlink cluster and the cluster index of the uplink cluster are in the same numbering space; or, the first command carries a first bit map, each bit in the first bit map corresponds to one or more cluster indexes, the value of the bit is used to indicate whether one or more clusters indicated by the corresponding one or more cluster indexes are activated or deactivated, wherein the cluster index of the downlink cluster and the cluster index of the uplink cluster are in an independent numbering space, and the associated information of the first command is used to determine whether activation or deactivation is performed for the downlink or for the uplink.

[0571] In some implementations, when the first command is a MAC CE, the associated information of the first command is a logical channel identifier associated with the MAC CE.

[0572] In some implementations, the receiving unit 1601 is configured to receive third configuration information sent by the network device, where the third configuration information is used to configure at least one of the following:

[0573] Add one or more downlink carriers in a downlink cluster and / or add one or more uplink carriers in an uplink cluster;

[0574] Modifying one or more downlink carriers in a downlink cluster and / or modifying one or more uplink carriers in an uplink cluster;

[0575] One or more downlink carriers are released in the downlink cluster and / or one or more uplink carriers are released in the uplink cluster.

[0576] In some embodiments, the first configuration information is further used to configure the initial state of the carrier in each cluster of the at least one downlink cluster and / or the at least one uplink cluster; or, the initial state of the carrier in each cluster of the at least one downlink cluster and / or the at least one uplink cluster defaults to an activated state or a deactivated state.

[0577] In some implementations, the receiving unit 1601 is configured to receive a second command sent by the network device, where the second command is used to activate and / or deactivate at least some carriers in the at least one downlink cluster and / or at least one uplink cluster.

[0578] In some implementations, the second command includes at least one of the following: DCI, MAC CE.

[0579] In some embodiments, the second command carries a cluster index, a carrier index, third indication information, and fourth indication information, the third indication information being used to indicate whether activation or deactivation is performed for the downlink or for the uplink, and the fourth indication information being used to indicate whether activation or deactivation is performed for the carrier indicated by the carrier index, wherein the cluster index of the downlink cluster and the cluster index of the uplink cluster are in independent numbering spaces, and the carrier indexes in different clusters in the downlink cluster or the uplink cluster are in independent numbering spaces; or, the second command carries a cluster index, a carrier index, and fourth indication information, and the fourth indication information is used to indicate activation or deactivation of the carrier The carrier indicated by the index is activated or deactivated, wherein the cluster index of the downlink cluster and the cluster index of the uplink cluster are in the same numbering space, and the carrier indexes in different clusters in the downlink cluster or the uplink cluster are in independent numbering spaces; or, the second command carries the cluster index, the carrier index and the fourth indication information, and the fourth indication information is used to indicate whether the carrier indicated by the carrier index is activated or deactivated, wherein the cluster index of the downlink cluster and the cluster index of the uplink cluster are in independent numbering spaces, and the carrier indexes in different clusters in the downlink cluster or the uplink cluster are in independent numbering spaces, and the associated information of the second command is used to determine whether to activate or deactivate the carrier indicated by the carrier index The carrier index within the downlink cluster and the carrier index within the uplink cluster are in independent numbering spaces, and the carrier indexes within different clusters in the downlink cluster or the uplink cluster are in the same numbering space; or, the second command carries the carrier index and the fourth indication information, and the fourth indication information is used to indicate whether the carrier indicated by the carrier index is activated or deactivated. Indicates whether to activate or deactivate the carrier indicated by the carrier index, wherein the carrier index in the downlink cluster and the carrier index in the uplink cluster are in the same numbering space; or, the second command carries the carrier index and fourth indication information, and the fourth indication information is used to indicate whether to activate or deactivate the carrier indicated by the carrier index, wherein the carrier index in the downlink cluster and the carrier index in the uplink cluster are in independent numbering spaces, and the carrier indexes in different clusters in the downlink cluster or uplink cluster are in the same numbering space, and the associated information of the second command is used to determine whether to activate or deactivate the downlink or the uplink.

[0580] In some embodiments, the second command carries a cluster index, a second bitmap, and third indication information, each bit in the second bitmap corresponds to one or more carrier indices, and the value of the bit is used to indicate whether the one or more carriers indicated by the corresponding one or more carrier indices are activated or deactivated, and the third indication information is used to indicate whether activation or deactivation is performed for the downlink or for the uplink, wherein the cluster index of the downlink cluster and the cluster index of the uplink cluster are in independent numbering spaces, and the carrier indices in different clusters in the downlink cluster or the uplink cluster are in independent numbering spaces; or, the second command carries a cluster index and a second bitmap, each bit in the second bitmap corresponds to one or more carrier indices, and the value of the bit is used to indicate whether the one or more carriers indicated by the corresponding one or more carrier indices are activated or deactivated, wherein the cluster index of the downlink cluster and the cluster index of the uplink cluster are in the same numbering space, and the carrier indices in different clusters in the downlink cluster or the uplink cluster are in independent numbering spaces; or, the second command carries a cluster index and a second bitmap, each bit in the second bitmap corresponds to one or more carrier indices, and the value of the bit is used to indicate whether the one or more carriers indicated by the corresponding one or more carrier indices are activated or deactivated. whether multiple carriers are activated or deactivated, wherein the cluster index of the downlink cluster and the cluster index of the uplink cluster are in an independent numbering space, and the carrier indexes in different clusters in the downlink cluster or the uplink cluster are in an independent numbering space, and the associated information of the second command is used to determine whether activation or deactivation is performed for the downlink or for the uplink; or, the second command carries a second bitmap and third indication information, each bit in the second bitmap corresponds to one or more carrier indexes, and the value of the bit is used to indicate whether the one or more carriers indicated by the corresponding one or more carrier indexes are activated or deactivated, and the third indication information is used to indicate whether activation or deactivation is performed for the downlink or for the uplink, wherein the carrier indexes in the downlink cluster and the carrier indexes in the uplink cluster are in an independent numbering space, and the carrier indexes in different clusters in the downlink cluster or the uplink cluster are in the same numbering space; or, the second command carries a second bitmap, each bit in the second bitmap corresponds to one or more carrier indexes, and the value of the bit is used to indicate whether the one or more carriers indicated by the corresponding one or more carrier indexes are activated or deactivated, wherein the carrier indexes in the downlink cluster and the carrier indexes in the uplink cluster are in the same numbering space;Alternatively, the second command carries a second bitmap, each bit in the second bitmap corresponds to one or more carrier indexes, and the value of the bit is used to indicate whether one or more carriers indicated by the corresponding one or more carrier indexes are activated or deactivated, wherein the carrier indexes within a downlink cluster and the carrier indexes within an uplink cluster are in independent numbering spaces, and the carrier indexes in different clusters within the downlink cluster or the uplink cluster are in the same numbering space, and the associated information of the second command is used to determine whether activation or deactivation is performed for the downlink or for the uplink.

[0581] In some implementations, when the second command is a MAC CE, the associated information of the second command is a logical channel identifier associated with the MAC CE.

[0582] In some embodiments, for a deactivated downlink carrier, the behavior of the terminal device on the downlink carrier includes at least one of the following: not monitoring PDCCH, not receiving PDSCH, performing CSI measurement, and performing beam measurement.

[0583] In some embodiments, for a deactivated uplink carrier, the behavior of the terminal device on the uplink carrier includes at least one of the following: not sending PUSCH, not sending PUCCH, and not sending SRS.

[0584] In some embodiments, for a deactivated downlink carrier, whether the downlink carrier supports sending and / or receiving a first signal is determined based on the configuration of a network device, where the first signal includes at least one of the following: PDCCH, PDSCH, SSB, CSI-RS.

[0585] In some embodiments, for a deactivated uplink carrier, whether the uplink carrier supports sending and / or receiving a second signal is determined based on the configuration of the network device, and the second signal includes at least one of the following: PUCCH, PUSCH, SRS, PRACH.

[0586] In some implementations, the downlink carrier supports at least one of the following scheduling modes:

[0587] Same-carrier scheduling mode, wherein the same-carrier scheduling mode is that the DCI on the downlink carrier schedules the PDSCH on the downlink carrier;

[0588] A cross-carrier scheduling mode is that the DCI on the downlink carrier schedules the PDSCH on the second downlink carrier and / or schedules the PUSCH on the second uplink carrier.

[0589] In some embodiments, the cross-carrier scheduling mode includes a first type of cross-carrier scheduling mode and / or a second type of cross-carrier scheduling mode;

[0590] In the first type of cross-carrier scheduling mode, the downlink carrier and the scheduled carrier belong to the same downlink cluster, and the scheduled carrier is the second downlink carrier;

[0591] In the second type of cross-carrier scheduling mode, the downlink carrier and the scheduled carrier belong to different downlink clusters, and the scheduled carrier includes the second downlink carrier and / or the second uplink carrier.

[0592] In some implementations, for the first type of cross-carrier scheduling,

[0593] The DCI on the downlink carrier carries the carrier index of the scheduled carrier; or,

[0594] The relationship between the downlink carrier and the scheduled carrier is configured through RRC signaling.

[0595] In some implementations, for the second type of cross-carrier scheduling,

[0596] The DCI on the downlink carrier carries the cluster index of the cluster where the scheduled carrier is located and the carrier index of the scheduled carrier, wherein the carrier indexes in different clusters are in independent numbering spaces; or,

[0597] The DCI on the downlink carrier carries the carrier index of the scheduled carrier, wherein the carrier indexes in different clusters are in the same numbering space; or

[0598] The relationship between the downlink carrier and the scheduled carrier is configured through RRC signaling.

[0599] In some embodiments, for a third downlink carrier in the at least one downlink cluster, HARQ feedback information of a PDSCH on the third downlink carrier is transmitted via a PUCCH on a third uplink carrier;

[0600] The third uplink carrier is configured through RRC signaling; or,

[0601] The third uplink carrier is indicated by a DCI that schedules the third downlink carrier.

[0602] In some embodiments, the DCI for scheduling the third downlink carrier carries the cluster index of the cluster in which the third uplink carrier is located and the carrier index of the third uplink carrier, wherein the carrier indexes in different clusters are in independent numbering spaces; or, the DCI for scheduling the third downlink carrier carries the carrier index of the third uplink carrier, wherein the carrier indexes in different clusters are in the same numbering space.

[0603] In some embodiments, the receiving unit 1601 is used to receive a first TB on a fourth downlink carrier, and if the number of retransmissions of the first TB exceeds a first threshold value, the terminal device receives the first TB on a fifth downlink carrier; and / or, the sending unit 1602 is used to send a second TB on a fourth uplink carrier, and if the number of retransmissions of the second TB exceeds a second threshold value, the terminal device sends the second TB on a fifth uplink carrier.

[0604] In some implementations, the first TB on the fifth downlink carrier is new transmission data; and / or the second TB on the fifth uplink carrier is new transmission data.

[0605] In some implementations, the receiving unit 1601 is configured to receive first DCI on the fourth downlink carrier, where the first DCI carries at least one of the following:

[0606] fifth information, where the fifth information is used to schedule the fifth downlink carrier to newly transmit the first TB;

[0607] The sixth information is used to instruct the network device to abandon retransmission of the first TB on the fourth downlink carrier and / or instruct the terminal device to clear the cache corresponding to the first HARQ process of the fourth downlink carrier, where the first HARQ process is the HARQ process corresponding to the first TB on the fourth downlink carrier.

[0608] In some implementations, the receiving unit 1601 is configured to receive a second DCI on a fourth downlink carrier, where the second DCI carries at least one of the following:

[0609] seventh information, where the seventh information is used to schedule the fifth uplink carrier to newly transmit the second TB;

[0610] The eighth information is used to instruct the terminal device to abandon retransmission of the second TB on the fourth uplink carrier and / or instruct the terminal device to clear the cache corresponding to the second HARQ process of the fourth uplink carrier, where the second HARQ process is the HARQ process corresponding to the second TB on the fourth uplink carrier.

[0611] In some implementations, the fifth downlink carrier and the fourth downlink carrier correspond to different HARQ entities; and / or the fifth uplink carrier and the fourth uplink carrier correspond to different HARQ entities.

[0612] In some embodiments, the first TB on the fifth downlink carrier is retransmitted data of the first TB on the fourth downlink carrier; and / or the second TB on the fifth uplink carrier is retransmitted data of the second TB on the fourth uplink carrier.

[0613] In some implementations, the fifth downlink carrier and the fourth downlink carrier correspond to the same HARQ entity; and / or the fifth uplink carrier and the fourth uplink carrier correspond to the same HARQ entity.

[0614] In some embodiments, each carrier group in the at least one downlink cluster and / or the at least one uplink cluster corresponds to a HARQ entity; the fifth downlink carrier and the fourth downlink carrier belong to the same carrier group, and / or the fifth uplink carrier and the fourth uplink carrier belong to the same carrier group.

[0615] In some implementations, the receiving unit 1601 is configured to receive fourth configuration information sent by a network device, where the fourth configuration information is used to configure one or more carrier groups, where each carrier group corresponds to one HARQ entity.

[0616] In some implementations, the fifth downlink carrier and the fourth downlink carrier correspond to different HARQ entities; and / or the fifth uplink carrier and the fourth uplink carrier correspond to different HARQ entities.

[0617] In some implementations, the receiving unit 1601 is configured to receive a third DCI on a fourth downlink carrier, where the third DCI carries at least one of the following:

[0618] Ninth information, where the ninth information is used to schedule the fifth downlink carrier to retransmit the first TB;

[0619] Tenth information, where the tenth information is used to indicate a HARQ process identifier corresponding to the first TB on the fourth downlink carrier;

[0620] The eleventh information is used to indicate the HARQ process identifier corresponding to the first TB on the fifth downlink carrier.

[0621] In some implementations, the receiving unit 1601 is configured to receive a fourth DCI on a fourth downlink carrier, where the fourth DCI carries at least one of the following:

[0622] Twelfth information, the twelfth information is used to schedule the fifth uplink carrier to retransmit the second TB;

[0623] Thirteenth information, the thirteenth information is used to indicate the HARQ process identifier corresponding to the second TB on the fourth uplink carrier;

[0624] Fourteenth information, the fourteenth information is used to indicate the HARQ process identifier corresponding to the second TB on the fifth uplink carrier.

[0625] In some implementations, the sending unit 1602 is configured to send a first message on a sixth uplink carrier, and the receiving unit 1601 is configured to receive a second message on a sixth downlink carrier, where the first message and the second message are associated messages in a random access process.

[0626] In some implementations, the sixth uplink carrier is an uplink carrier in the at least one uplink cluster configured with PRACH resources and / or random access configuration information.

[0627] In some embodiments, the carrier index or carrier number of the sixth downlink carrier is determined based on the random access series and a second parameter, and the second parameter is the number of downlink carriers configured by the first configuration information; or, the carrier index or carrier number of the sixth downlink carrier is determined based on the random access series and a fifth parameter, and the fifth parameter is the number of downlink carriers in the first downlink carrier list, and the first downlink carrier list is a downlink carrier list configured by the network device for receiving the second message; or, the sixth downlink carrier is a downlink carrier associated with the sixth uplink carrier configured by the network device; or, the sixth downlink carrier is one downlink carrier of at least one downlink carrier associated with the random access series and / or PRACH resources.

[0628] In some embodiments, the receiving unit 1601 is used to receive a second message on a sixth downlink carrier using an RA-RNTI, where the RA-RNTI is calculated based on a sixth parameter and / or a seventh parameter, where the value of the sixth parameter is configured by a network device or is the carrier index of the sixth uplink carrier or is the carrier index of the sixth uplink carrier plus a first offset, and the value of the seventh parameter is configured by a network device or is the cluster index of the uplink cluster in which the sixth uplink carrier is located.

[0629] In some embodiments, each of the at least one cluster includes at least one cell.

[0630] In some implementations, the sending unit 1602 is configured to report first capability information of the terminal device to the network device, where the first capability information includes at least one of the following:

[0631] first information, where the first information is used to indicate a cluster-supporting capability of the terminal device;

[0632] second information, where the second information is used to indicate a maximum number of clusters supported by the terminal device;

[0633] third information, where the third information is used to indicate a maximum number of cells included in a cluster supported by the terminal device;

[0634] Fourth information, the fourth information is used to indicate the frequency band combination of the cluster supported by the terminal device.

[0635] In some embodiments, each cluster in the at least one is associated with a cluster index.

[0636] In some embodiments, each cell of the at least one cell is associated with a cell index.

[0637] In some implementations, cells within the same cluster are downlink synchronized and / or uplink synchronized.

[0638] In some embodiments, the synchronization unit is configured to, for each cluster, enable the terminal device to perform downlink synchronization and / or uplink synchronization for the cluster based on the first cell in the cluster.

[0639] In some implementations, the first cell is any one cell in the cluster or a designated cell in the cluster, and the designated cell is a cell indicated by a network device or a default cell.

[0640] In some implementations, the sending unit 1602 is configured to initiate a random access process to a first cell in the cluster using a first random access resource to achieve uplink synchronization; the first random access resource is a random access resource dedicated to the cluster and configured by the network device.

[0641] In some implementations, the receiving unit 1601 is configured to receive second configuration information sent by the network device, where the second configuration information is used to configure at least one of the following:

[0642] Add one or more clusters;

[0643] Modify one or more clusters;

[0644] Releases one or more clusters.

[0645] In some embodiments, the first configuration information is further used to configure an initial state of each cluster in the at least one cluster; or the initial state of each cluster in the at least one cluster is an activated state or a deactivated state by default.

[0646] In some implementations, the receiving unit 1601 is configured to receive a first command sent by the network device, where the first command is used to activate and / or deactivate at least part of the at least one cluster.

[0647] In some embodiments, the first command includes at least one of the following: DCI, MAC CE.

[0648] In some embodiments, the first command carries a cluster index and second indication information, where the second indication information is used to indicate whether to activate or deactivate the cluster indicated by the cluster index.

[0649] In some embodiments, the first command carries a first bitmap, each bit in the first bitmap corresponds to one or more cluster indexes, and the value of the bit is used to indicate whether one or more clusters indicated by the corresponding one or more cluster indexes are activated or deactivated.

[0650] In some implementations, the receiving unit 1601 is configured to receive third configuration information sent by the network device, where the third configuration information is used to configure at least one of the following:

[0651] Add one or more cells to the cluster;

[0652] Modifying one or more cells in a cluster;

[0653] Release one or more cells in a cluster.

[0654] In some embodiments, the first configuration information is further used to configure an initial state of a cell in each of the at least one cluster; or the initial state of a cell in each of the at least one cluster is an activated state or a deactivated state by default.

[0655] In some implementations, the receiving unit 1601 is configured to receive a second command sent by the network device, where the second command is used to activate and / or deactivate at least some cells in the at least one cluster.

[0656] In some implementations, the second command includes at least one of the following: DCI, MAC CE.

[0657] In some embodiments, the second command carries a cluster index, a cell index and fourth indication information, and the fourth indication information is used to indicate whether to activate or deactivate the cell indicated by the cell index, wherein the cell indices in different clusters are in independent numbering spaces; or, the second command carries a cell index and fourth indication information, and the fourth indication information is used to indicate whether to activate or deactivate the cell indicated by the cell index, wherein the cell indices in different clusters are in the same numbering space.

[0658] In some embodiments, the second command carries a cluster index and a second bit map, each bit in the second bit map corresponds to one or more cell indices, and the value of the bit is used to indicate whether the one or more cells indicated by the corresponding one or more cell indices are activated or deactivated, wherein the cell indices in different clusters are in independent numbering spaces; or, the second command carries a second bit map, each bit in the second bit map corresponds to one or more cell indices, and the value of the bit is used to indicate whether the one or more cells indicated by the corresponding one or more cell indices are activated or deactivated, wherein the cell indices in different clusters are in the same numbering space.

[0659] In some embodiments, for a deactivated cell, the behavior of the terminal device on the cell includes at least one of the following: not monitoring PDCCH, not receiving PDSCH, performing CSI measurement, performing beam measurement, not sending PUSCH, not sending PUCCH, and not sending SRS.

[0660] In some embodiments, whether the cell supports the sending and / or receiving of the first signal and / or the second signal is determined based on the configuration of the network device, the first signal includes at least one of the following: PDCCH, PDSCH, SSB, CSI-RS, and the second signal includes at least one of the following: PUCCH, PUSCH, SRS, PRACH.

[0661] In some implementations, the cell supports at least one of the following scheduling modes:

[0662] Same-carrier scheduling mode, wherein the same-carrier scheduling mode is that the DCI on the cell schedules the PDSCH on the cell;

[0663] A cross-carrier scheduling method, where the cross-carrier scheduling method is that the DCI on the cell schedules the PDSCH and / or PUSCH on the second cell.

[0664] In some embodiments, the cross-carrier scheduling mode includes a first type of cross-carrier scheduling mode and / or a second type of cross-carrier scheduling mode;

[0665] In the first type of cross-carrier scheduling mode, the cell and the scheduled cell belong to the same cluster, and the scheduled cell is the second cell;

[0666] In the second type of cross-carrier scheduling mode, the cell and the scheduled carrier belong to different clusters, and the scheduled carrier is the second cell.

[0667] In some implementations, for the first type of cross-carrier scheduling,

[0668] The DCI on the cell carries the cell index of the scheduled cell; or,

[0669] The relationship between the cell and the scheduled cell is configured through RRC signaling.

[0670] In some implementations, for the second type of cross-carrier scheduling,

[0671] The DCI on the cell carries the cluster index of the cluster where the scheduled cell is located and the cell index of the scheduled cell, wherein the cell indexes in different clusters are in independent numbering spaces; or

[0672] The DCI on the cell carries the cell index of the scheduled cell, wherein the cell indexes in different clusters are in the same numbering space; or

[0673] The relationship between the cell and the scheduled cell is configured through RRC signaling.

[0674] In some embodiments, for a third cell in the at least one cluster, HARQ feedback information of a PDSCH on the third cell is transmitted via a PUCCH on a fourth cell;

[0675] The fourth cell is configured through RRC signaling; or,

[0676] The fourth cell is indicated by scheduling the DCI of the third cell.

[0677] In some embodiments, the DCI for scheduling the third cell carries the cluster index of the cluster where the fourth cell is located and the cell index of the fourth cell, wherein the cell indexes in different clusters are in independent numbering spaces; or, the DCI for scheduling the third cell carries the cell index of the fourth cell, wherein the cell indexes in different clusters are in the same numbering space.

[0678] In some embodiments, the receiving unit 1601 is used to receive the first TB on the fifth cell, and if the number of retransmissions of the first TB exceeds a first threshold value, the terminal device receives the first TB on the sixth cell; and / or, the sending unit 1602 is used to send the second TB on the fifth cell, and if the number of retransmissions of the second TB exceeds a second threshold value, the terminal device sends the second TB on the sixth cell.

[0679] In some embodiments, the first TB on the sixth cell is newly transmitted data; and / or the second TB on the sixth cell is newly transmitted data.

[0680] In some implementations, the receiving unit 1601 is configured to receive first DCI on the fifth cell, where the first DCI carries at least one of the following:

[0681] fifth information, where the fifth information is used to schedule the sixth cell to newly transmit the first TB;

[0682] The sixth information is used to instruct the network device to give up retransmitting the first TB on the fifth cell and / or instruct the terminal device to clear the cache corresponding to the first HARQ process of the fifth cell, where the first HARQ process is the HARQ process corresponding to the first TB on the fifth cell.

[0683] In some implementations, the receiving unit 1601 is configured to receive a second DCI on the fifth cell, where the second DCI carries at least one of the following:

[0684] Seventh information, where the seventh information is used to schedule the sixth cell to newly transmit the second TB;

[0685] The eighth information is used to instruct the terminal device to give up retransmitting the second TB on the fifth cell and / or instruct the terminal device to clear the cache corresponding to the second HARQ process of the fifth cell, where the second HARQ process is the HARQ process corresponding to the second TB on the fifth cell.

[0686] In some implementations, the sixth cell and the fifth cell correspond to different HARQ entities.

[0687] In some embodiments, the first TB on the sixth cell is retransmitted data of the first TB on the fifth cell; and / or the second TB on the sixth cell is retransmitted data of the second TB on the fifth cell.

[0688] In some implementations, the sixth cell and the fifth cell correspond to the same HARQ entity.

[0689] In some embodiments, each cell group in the at least one cluster corresponds to a HARQ entity;

[0690] The sixth cell and the fifth cell belong to the same cell group.

[0691] In some implementations, the receiving unit 1601 is configured to receive fourth configuration information sent by a network device, where the fourth configuration information is used to configure one or more cell groups, where each cell group corresponds to a HARQ entity.

[0692] In some implementations, the sixth cell and the fifth cell correspond to different HARQ entities.

[0693] In some implementations, the receiving unit 1601 is configured to receive a third DCI on the fifth cell, where the third DCI carries at least one of the following:

[0694] Ninth information, where the ninth information is used to schedule the six cells to retransmit the first TB;

[0695] Tenth information, where the tenth information is used to indicate a HARQ process identifier corresponding to the first TB on the fifth cell;

[0696] The eleventh information is used to indicate the HARQ process identifier corresponding to the first TB in the six cells.

[0697] In some implementations, the sending unit 1602 is configured to send a first message on a seventh cell, and the receiving unit 1601 is configured to receive a second message on an eighth cell, where the first message and the second message are associated messages in a random access process.

[0698] In some implementations, the seventh cell is a cell in the at least one cluster configured with PRACH resources and / or random access configuration information.

[0699] In some embodiments, the cell index or cell number of the eighth cell is determined based on a random access series and a second parameter, where the second parameter is the number of cells configured by the first configuration information; or, the cell index or cell number of the eighth cell is determined based on a random access series and a fifth parameter, where the fifth parameter is the number of cells in a first cell list, where the first cell list is a cell list configured by a network device for receiving the second message; or, the eighth cell is a cell associated with the seventh cell configured by a network device; or, the eighth cell is one of at least one cell associated with a random access series and / or PRACH resources.

[0700] In some embodiments, the receiving unit 1601 is used to receive a second message on the eighth cell using the RA-RNTI, where the RA-RNTI is calculated based on the sixth parameter and / or the seventh parameter, the value of the sixth parameter is configured by the network device or is the carrier index of the uplink carrier in the eighth cell or is the carrier index of the uplink carrier in the eighth cell plus a first offset, and the seventh parameter is configured by the network device or is the cluster index of the cluster in which the eighth cell is located.

[0701] In some implementations, the correspondence between the at least one cluster and the MAC entity includes at least one of the following:

[0702] One cluster corresponds to one MAC entity;

[0703] Multiple clusters correspond to one MAC entity.

[0704] In some embodiments, the MAC entity corresponds to one or more HARQ entities, and each HARQ entity corresponds to a carrier group or a cell group.

[0705] In some embodiments, the MAC entity further includes an upper layer entity, and the upper layer entity includes at least one of the following: an RLC entity, a PDCP entity, an SDAP entity, an RRC entity, and a NAS entity; wherein,

[0706] The MAC entity and the upper layer entity are deployed in the cloud; or,

[0707] The MAC entity is deployed on the access network side, and the upper layer entity is deployed on the cloud side; or,

[0708] The MAC entity and the RLC entity are deployed on the access network side, and entities in the upper layer except the RLC entity are deployed on the cloud.

[0709] In some embodiments, the RRC entity is associated with one or more sites; or, the RRC entity is associated with an area, where the area is an area defined by one or more cell lists or an area governed by a cloud platform.

[0710] In some embodiments, the receiving unit 1601 is configured to receive a first RRC signaling, where the first RRC signaling is used to configure updated system broadcast information. The terminal device does not monitor P-RNTI-scrambled DCI and SI-RNTI-scrambled DCI, where the P-RNTI-scrambled DCI is used to schedule a paging message, where the paging message is used to carry a system broadcast change indication, and the SI-RNTI-scrambled DCI is used to schedule updated system broadcast information.

[0711] In some embodiments, the receiving unit 1601 is used to receive a second RRC signaling, and the second RRC signaling is used to configure at least one of the following: a system broadcast change indication, a target carrier or target cell where a system broadcast information change occurs, a target SIB received by the terminal device, a scheduling period of the target SIB, and a time range for the terminal device to receive the target SIB scheduling information; based on the second RRC signaling, the SI-RNTI-scrambled DCI is monitored, and the SI-RNTI-scrambled DCI is used to schedule updated system broadcast information. The terminal device does not monitor the P-RNTI-scrambled DCI, and the P-RNTI-scrambled DCI is used to schedule paging messages, and the paging messages are used to carry system broadcast change indications.

[0712] In some embodiments, the receiving unit 1601 is used to monitor the P-RNTI-scrambled DCI on the target carrier or target cell, the P-RNTI-scrambled DCI is used to schedule paging messages, the P-RNTI-scrambled DCI and / or the paging message are used to notify at least one of the following: a system broadcast change indication, a target carrier or target cell where a system broadcast information change occurs, a target SIB received by the terminal device, a scheduling period of the target SIB, and a time range for the terminal device to receive the target SIB scheduling information; based on the P-RNTI-scrambled DCI and / or the paging message, monitor the SI-RNTI-scrambled DCI, the SI-RNTI-scrambled DCI is used to schedule updated system broadcast information.

[0713] In some implementations, the receiving unit 1601 is configured to receive a third RRC signaling, where the third RRC signaling is used to configure:

[0714] The carrier index of the target carrier, wherein the carrier indexes in different clusters are in the same numbering space; or

[0715] The cluster index of the cluster where the target carrier is located and the carrier index of the target carrier, wherein the carrier indexes in different clusters are in independent numbering spaces; or

[0716] The cell index of the target cell, wherein the cell indexes in different clusters are in the same numbering space; or

[0717] The cluster index of the cluster where the target cell is located and the cell index of the target cell, wherein the cell indexes in different clusters are in independent numbering spaces.

[0718] In some embodiments, the device further includes: a determination unit for determining the carrier index or carrier number of the target carrier based on a first parameter and a second parameter, the first parameter being the identifier of the terminal device, and the second parameter being the number of downlink carriers configured by the first configuration information, wherein the carrier indexes in different clusters are in the same numbering space; or, determining the carrier index or carrier number of the target carrier based on the first parameter and the third parameter, and determining the cluster index or cluster number of the cluster where the target carrier is located based on the first parameter and the fourth parameter, the first parameter being the identifier of the terminal device, the third parameter being the number of downlink carriers in the cluster where the target carrier is located, and the fourth parameter being the number of downlink clusters configured by the first configuration information, wherein the carrier indexes in different clusters are in the same numbering space. The carrier index is in an independent numbering space; or, the cell index or cell number of the target cell is determined based on a first parameter and a second parameter, the first parameter is the identifier of the terminal device, and the second parameter is the number of cells configured by the first configuration information, wherein the cell indexes in different clusters are in the same numbering space; or, the cell index or cell number of the target cell is determined based on the first parameter and the third parameter, and the cluster index or cluster number of the cluster where the target cell is located is determined based on the first parameter and the fourth parameter, the first parameter is the identifier of the terminal device, the third parameter is the number of cells in the cluster where the target cell is located, and the fourth parameter is the number of clusters configured by the first configuration information, wherein the cell indexes in different clusters are in independent numbering spaces.

[0719] In some embodiments, the sending unit 1602 is configured to send uplink RRC signaling to a network device for a cluster configured with the first configuration information, if a radio link failure occurs in all carriers or cells in the cluster, and the uplink RRC signaling is used to notify the network device that a radio link failure occurs in the cluster.

[0720] In some embodiments, the receiving unit 1601 is used to receive fifth configuration information sent by the network device, and the fifth configuration information is used to configure the terminal device to trigger the target cluster to notify the target cluster of the radio link failure through uplink RRC signaling when a radio link failure occurs in the target cluster.

[0721] In some embodiments, if radio link failure occurs in all clusters configured by the first configuration information, the terminal device initiates an RRC connection reestablishment process.

[0722] In some embodiments, the at least one cluster belongs to one or more sites.

[0723] In some embodiments, the receiving unit 1601 is used to receive first configuration information sent by a first site, where the first configuration information includes configuration information of a cluster on the first site side and configuration information of a cluster on the at least one second site side; wherein the configuration information of the cluster on the second site side is sent by the second site to the first site through a container.

[0724] In some embodiments, the sending unit 1602 is used to send a cluster add request message to the second site; the receiving unit 1601 is used to receive a cluster add response message sent by the second site, and the cluster add response message carries a container, and the container is used to carry the configuration information of the cluster on the second site side.

[0725] In some implementations, the cluster add request message carries at least one of the following:

[0726] fifth indication information, where the fifth indication information is used to indicate a bearer configuration that the second site needs to provide;

[0727] Sixth indication information, where the sixth indication information is used to indicate a protocol stack entity that the second site needs to provide.

[0728] Those skilled in the art should understand that the relevant description of the above-mentioned carrier aggregation device in the embodiment of the present application can be understood with reference to the relevant description of the carrier aggregation method in the embodiment of the present application.

[0729] FIG17 is a second schematic diagram of the structure of a carrier aggregation apparatus provided in an embodiment of the present application, which is applied to a network device. As shown in FIG17 , the carrier aggregation apparatus includes:

[0730] The sending unit 1701 is configured to send first configuration information to a terminal device, where the first configuration information is used to configure at least one cluster, where each cluster in the at least one cluster includes at least one carrier or at least one cell.

[0731] In some implementations, the at least one cluster includes at least one downlink cluster and / or at least one uplink cluster, each downlink cluster includes at least one downlink carrier, and each uplink cluster includes at least one uplink carrier.

[0732] In some implementations, the apparatus further includes: a receiving unit 1702, configured to receive first capability information of the terminal device reported by the terminal device, where the first capability information includes at least one of the following:

[0733] First information, where the first information is used to indicate a capability of the terminal device to support a downlink cluster and / or a capability of the terminal device to support an uplink cluster;

[0734] Second information, where the second information is used to indicate a maximum number of downlink clusters and / or a maximum number of uplink clusters supported by the terminal device;

[0735] Third information, where the third information is used to indicate a maximum number of downlink carriers included in a downlink cluster and / or a maximum number of uplink carriers included in an uplink cluster supported by the terminal device;

[0736] Fourth information, the fourth information is used to indicate the frequency band combination of the downlink cluster and / or uplink cluster supported by the terminal device.

[0737] In some embodiments, each cluster in the at least one downlink cluster and / or the at least one uplink cluster is associated with a cluster index.

[0738] In some implementations, each downlink carrier in the at least one downlink carrier is associated with a downlink carrier index; and / or each uplink carrier in the at least one uplink carrier is associated with an uplink carrier index.

[0739] In some implementations, downlink carriers within the same downlink cluster are downlink synchronized; and / or uplink carriers within the same uplink cluster are uplink synchronized.

[0740] In some implementations, the sending unit 1701 is configured to send second configuration information to the terminal device, where the second configuration information is used to configure at least one of the following:

[0741] Add one or more downlink clusters and / or add one or more uplink clusters;

[0742] Modifying one or more downlink clusters and / or modifying one or more uplink clusters;

[0743] One or more downlink clusters are released and / or one or more uplink clusters are released.

[0744] In some embodiments, the first configuration information is further used to configure the initial state of each cluster in the at least one downlink cluster and / or the at least one uplink cluster; or, the initial state of each cluster in the at least one downlink cluster and / or the at least one uplink cluster defaults to an activated state or a deactivated state.

[0745] In some embodiments, the sending unit 1701 is used to send a first command to the terminal device, where the first command is used to activate and / or deactivate at least part of the at least one downlink cluster and / or at least one uplink cluster.

[0746] In some embodiments, the first command includes at least one of the following: DCI, MAC CE.

[0747] In some embodiments, the first command carries a cluster index, first indication information, and second indication information, the first indication information being used to indicate whether activation or deactivation is performed for the downlink or for the uplink, and the second indication information being used to indicate whether activation or deactivation is performed for the cluster indicated by the cluster index, wherein the cluster index of the downlink cluster and the cluster index of the uplink cluster are in independent numbering spaces; or, the first command carries a cluster index and a second indication information, the second indication information being used to indicate whether activation or deactivation is performed for the cluster indicated by the cluster index, wherein the cluster index of the downlink cluster and the cluster index of the uplink cluster are in the same numbering space; or, the first command carries a cluster index and a second indication information, the second indication information being used to indicate whether activation or deactivation is performed for the cluster indicated by the cluster index, wherein the cluster index of the downlink cluster and the cluster index of the uplink cluster are in independent numbering spaces, and the associated information of the first command is used to determine whether activation or deactivation is performed for the downlink or for the uplink.

[0748] In some embodiments, the first command carries a first bit map and first indication information, each bit in the first bit map corresponds to one or more cluster indexes, the value of the bit is used to indicate whether one or more clusters indicated by the corresponding one or more cluster indexes are activated or deactivated, and the first indication information is used to indicate whether activation or deactivation is performed for the downlink or for the uplink, wherein the cluster index of the downlink cluster and the cluster index of the uplink cluster are in an independent numbering space; or, the first command carries a first bit map, each bit in the first bit map corresponds to one or more cluster indexes, the value of the bit is used to indicate whether one or more clusters indicated by the corresponding one or more cluster indexes are activated or deactivated, wherein the cluster index of the downlink cluster and the cluster index of the uplink cluster are in the same numbering space; or, the first command carries a first bit map, each bit in the first bit map corresponds to one or more cluster indexes, the value of the bit is used to indicate whether one or more clusters indicated by the corresponding one or more cluster indexes are activated or deactivated, wherein the cluster index of the downlink cluster and the cluster index of the uplink cluster are in an independent numbering space, and the associated information of the first command is used to determine whether activation or deactivation is performed for the downlink or for the uplink.

[0749] In some implementations, when the first command is a MAC CE, the associated information of the first command is a logical channel identifier associated with the MAC CE.

[0750] In some implementations, the sending unit 1701 is configured to send third configuration information to the terminal device, where the third configuration information is used to configure at least one of the following:

[0751] Add one or more downlink carriers in a downlink cluster and / or add one or more uplink carriers in an uplink cluster;

[0752] Modifying one or more downlink carriers in a downlink cluster and / or modifying one or more uplink carriers in an uplink cluster;

[0753] One or more downlink carriers are released in the downlink cluster and / or one or more uplink carriers are released in the uplink cluster.

[0754] In some embodiments, the first configuration information is further used to configure the initial state of the carrier in each cluster of the at least one downlink cluster and / or the at least one uplink cluster; or, the initial state of the carrier in each cluster of the at least one downlink cluster and / or the at least one uplink cluster defaults to an activated state or a deactivated state.

[0755] In some embodiments, the sending unit 1701 is used to send a second command to the terminal device, where the second command is used to activate and / or deactivate at least part of the carriers in the at least one downlink cluster and / or at least one uplink cluster.

[0756] In some implementations, the second command includes at least one of the following: DCI, MAC CE.

[0757] In some embodiments, the second command carries a cluster index, a carrier index, third indication information, and fourth indication information, the third indication information being used to indicate whether activation or deactivation is performed for the downlink or for the uplink, and the fourth indication information being used to indicate whether activation or deactivation is performed for the carrier indicated by the carrier index, wherein the cluster index of the downlink cluster and the cluster index of the uplink cluster are in independent numbering spaces, and the carrier indexes in different clusters in the downlink cluster or the uplink cluster are in independent numbering spaces; or, the second command carries a cluster index, a carrier index, and fourth indication information, and the fourth indication information is used to indicate activation or deactivation of the carrier The carrier indicated by the index is activated or deactivated, wherein the cluster index of the downlink cluster and the cluster index of the uplink cluster are in the same numbering space, and the carrier indexes in different clusters in the downlink cluster or the uplink cluster are in independent numbering spaces; or, the second command carries the cluster index, the carrier index and the fourth indication information, and the fourth indication information is used to indicate whether the carrier indicated by the carrier index is activated or deactivated, wherein the cluster index of the downlink cluster and the cluster index of the uplink cluster are in independent numbering spaces, and the carrier indexes in different clusters in the downlink cluster or the uplink cluster are in independent numbering spaces, and the associated information of the second command is used to determine whether to activate or deactivate the carrier indicated by the carrier index The carrier index within the downlink cluster and the carrier index within the uplink cluster are in independent numbering spaces, and the carrier indexes within different clusters in the downlink cluster or the uplink cluster are in the same numbering space; or, the second command carries the carrier index and the fourth indication information, and the fourth indication information is used to indicate whether the carrier indicated by the carrier index is activated or deactivated. Indicates whether to activate or deactivate the carrier indicated by the carrier index, wherein the carrier index in the downlink cluster and the carrier index in the uplink cluster are in the same numbering space; or, the second command carries the carrier index and fourth indication information, and the fourth indication information is used to indicate whether to activate or deactivate the carrier indicated by the carrier index, wherein the carrier index in the downlink cluster and the carrier index in the uplink cluster are in independent numbering spaces, and the carrier indexes in different clusters in the downlink cluster or uplink cluster are in the same numbering space, and the associated information of the second command is used to determine whether to activate or deactivate the downlink or the uplink.

[0758] In some embodiments, the second command carries a cluster index, a second bitmap, and third indication information, each bit in the second bitmap corresponds to one or more carrier indices, and the value of the bit is used to indicate whether the one or more carriers indicated by the corresponding one or more carrier indices are activated or deactivated, and the third indication information is used to indicate whether activation or deactivation is performed for the downlink or for the uplink, wherein the cluster index of the downlink cluster and the cluster index of the uplink cluster are in independent numbering spaces, and the carrier indices in different clusters in the downlink cluster or the uplink cluster are in independent numbering spaces; or, the second command carries a cluster index and a second bitmap, each bit in the second bitmap corresponds to one or more carrier indices, and the value of the bit is used to indicate whether the one or more carriers indicated by the corresponding one or more carrier indices are activated or deactivated, wherein the cluster index of the downlink cluster and the cluster index of the uplink cluster are in the same numbering space, and the carrier indices in different clusters in the downlink cluster or the uplink cluster are in independent numbering spaces; or, the second command carries a cluster index and a second bitmap, each bit in the second bitmap corresponds to one or more carrier indices, and the value of the bit is used to indicate whether the one or more carriers indicated by the corresponding one or more carrier indices are activated or deactivated. whether multiple carriers are activated or deactivated, wherein the cluster index of the downlink cluster and the cluster index of the uplink cluster are in an independent numbering space, and the carrier indexes in different clusters in the downlink cluster or the uplink cluster are in an independent numbering space, and the associated information of the second command is used to determine whether activation or deactivation is performed for the downlink or for the uplink; or, the second command carries a second bitmap and third indication information, each bit in the second bitmap corresponds to one or more carrier indexes, and the value of the bit is used to indicate whether the one or more carriers indicated by the corresponding one or more carrier indexes are activated or deactivated, and the third indication information is used to indicate whether activation or deactivation is performed for the downlink or for the uplink, wherein the carrier indexes in the downlink cluster and the carrier indexes in the uplink cluster are in an independent numbering space, and the carrier indexes in different clusters in the downlink cluster or the uplink cluster are in the same numbering space; or, the second command carries a second bitmap, each bit in the second bitmap corresponds to one or more carrier indexes, and the value of the bit is used to indicate whether the one or more carriers indicated by the corresponding one or more carrier indexes are activated or deactivated, wherein the carrier indexes in the downlink cluster and the carrier indexes in the uplink cluster are in the same numbering space;Alternatively, the second command carries a second bitmap, each bit in the second bitmap corresponds to one or more carrier indexes, and the value of the bit is used to indicate whether one or more carriers indicated by the corresponding one or more carrier indexes are activated or deactivated, wherein the carrier indexes within a downlink cluster and the carrier indexes within an uplink cluster are in independent numbering spaces, and the carrier indexes in different clusters within the downlink cluster or the uplink cluster are in the same numbering space, and the associated information of the second command is used to determine whether activation or deactivation is performed for the downlink or for the uplink.

[0759] In some implementations, when the second command is a MAC CE, the associated information of the second command is a logical channel identifier associated with the MAC CE.

[0760] In some embodiments, for a deactivated downlink carrier, whether the downlink carrier supports sending and / or receiving a first signal is determined based on the configuration of a network device, where the first signal includes at least one of the following: PDCCH, PDSCH, SSB, CSI-RS.

[0761] In some embodiments, for a deactivated uplink carrier, whether the uplink carrier supports sending and / or receiving a second signal is determined based on the configuration of the network device, and the second signal includes at least one of the following: PUCCH, PUSCH, SRS, PRACH.

[0762] In some implementations, the downlink carrier supports at least one of the following scheduling modes:

[0763] Same-carrier scheduling mode, wherein the same-carrier scheduling mode is that the DCI on the downlink carrier schedules the PDSCH on the downlink carrier;

[0764] A cross-carrier scheduling mode is that the DCI on the downlink carrier schedules the PDSCH on the second downlink carrier and / or schedules the PUSCH on the second uplink carrier.

[0765] In some embodiments, the cross-carrier scheduling mode includes a first type of cross-carrier scheduling mode and / or a second type of cross-carrier scheduling mode;

[0766] In the first type of cross-carrier scheduling mode, the downlink carrier and the scheduled carrier belong to the same downlink cluster, and the scheduled carrier is the second downlink carrier;

[0767] In the second type of cross-carrier scheduling mode, the downlink carrier and the scheduled carrier belong to different downlink clusters, and the scheduled carrier includes the second downlink carrier and / or the second uplink carrier.

[0768] In some implementations, for the first type of cross-carrier scheduling,

[0769] The DCI on the downlink carrier carries the carrier index of the scheduled carrier; or,

[0770] The relationship between the downlink carrier and the scheduled carrier is configured through RRC signaling.

[0771] In some implementations, for the second type of cross-carrier scheduling,

[0772] The DCI on the downlink carrier carries the cluster index of the cluster where the scheduled carrier is located and the carrier index of the scheduled carrier, wherein the carrier indexes in different clusters are in independent numbering spaces; or,

[0773] The DCI on the downlink carrier carries the carrier index of the scheduled carrier, wherein the carrier indexes in different clusters are in the same numbering space; or

[0774] The relationship between the downlink carrier and the scheduled carrier is configured through RRC signaling.

[0775] In some embodiments, for a third downlink carrier in the at least one downlink cluster, HARQ feedback information of a PDSCH on the third downlink carrier is transmitted via a PUCCH on a third uplink carrier;

[0776] The third uplink carrier is configured through RRC signaling; or,

[0777] The third uplink carrier is indicated by a DCI that schedules the third downlink carrier.

[0778] In some embodiments, the DCI for scheduling the third downlink carrier carries the cluster index of the cluster in which the third uplink carrier is located and the carrier index of the third uplink carrier, wherein the carrier indexes in different clusters are in independent numbering spaces; or, the DCI for scheduling the third downlink carrier carries the carrier index of the third uplink carrier, wherein the carrier indexes in different clusters are in the same numbering space.

[0779] In some embodiments, the sending unit 1701 is used to send the first TB on the fourth downlink carrier, and if the number of retransmissions of the first TB exceeds the first threshold value, the first TB is sent on the fifth downlink carrier; and / or the receiving unit 1702 is used to receive the second TB on the fourth uplink carrier, and if the number of retransmissions of the second TB exceeds the second threshold value, the second TB is received on the fifth uplink carrier.

[0780] In some implementations, the first TB on the fifth downlink carrier is new transmission data; and / or the second TB on the fifth uplink carrier is new transmission data.

[0781] In some implementations, the sending unit 1701 is configured to send a first DCI on the fourth downlink carrier, where the first DCI carries at least one of the following:

[0782] fifth information, where the fifth information is used to schedule the fifth downlink carrier to newly transmit the first TB;

[0783] The sixth information is used to instruct the network device to abandon retransmission of the first TB on the fourth downlink carrier and / or instruct the terminal device to clear the cache corresponding to the first HARQ process of the fourth downlink carrier, where the first HARQ process is the HARQ process corresponding to the first TB on the fourth downlink carrier.

[0784] In some implementations, the sending unit 1701 is configured to send a second DCI on a fourth downlink carrier, where the second DCI carries at least one of the following:

[0785] seventh information, where the seventh information is used to schedule the fifth uplink carrier to newly transmit the second TB;

[0786] The eighth information is used to instruct the terminal device to abandon retransmission of the second TB on the fourth uplink carrier and / or instruct the terminal device to clear the cache corresponding to the second HARQ process of the fourth uplink carrier, where the second HARQ process is the HARQ process corresponding to the second TB on the fourth uplink carrier.

[0787] In some implementations, the fifth downlink carrier and the fourth downlink carrier correspond to different HARQ entities; and / or the fifth uplink carrier and the fourth uplink carrier correspond to different HARQ entities.

[0788] In some embodiments, the first TB on the fifth downlink carrier is retransmitted data of the first TB on the fourth downlink carrier; and / or the second TB on the fifth uplink carrier is retransmitted data of the second TB on the fourth uplink carrier.

[0789] In some implementations, the fifth downlink carrier and the fourth downlink carrier correspond to the same HARQ entity; and / or the fifth uplink carrier and the fourth uplink carrier correspond to the same HARQ entity.

[0790] In some embodiments, each carrier group in the at least one downlink cluster and / or the at least one uplink cluster corresponds to a HARQ entity; the fifth downlink carrier and the fourth downlink carrier belong to the same carrier group, and / or the fifth uplink carrier and the fourth uplink carrier belong to the same carrier group.

[0791] In some embodiments, the sending unit 1701 is used to send fourth configuration information to the terminal device, where the fourth configuration information is used to configure one or more carrier groups, where each carrier group corresponds to a HARQ entity.

[0792] In some implementations, the fifth downlink carrier and the fourth downlink carrier correspond to different HARQ entities; and / or the fifth uplink carrier and the fourth uplink carrier correspond to different HARQ entities.

[0793] In some implementations, the sending unit 1701 is configured to send a third DCI on a fourth downlink carrier, where the third DCI carries at least one of the following:

[0794] Ninth information, where the ninth information is used to schedule the fifth downlink carrier to retransmit the first TB;

[0795] Tenth information, where the tenth information is used to indicate a HARQ process identifier corresponding to the first TB on the fourth downlink carrier;

[0796] The eleventh information is used to indicate the HARQ process identifier corresponding to the first TB on the fifth downlink carrier.

[0797] In some implementations, the sending unit 1701 is configured to receive a fourth DCI on a fourth downlink carrier, where the fourth DCI carries at least one of the following:

[0798] Twelfth information, the twelfth information is used to schedule the fifth uplink carrier to retransmit the second TB;

[0799] Thirteenth information, the thirteenth information is used to indicate the HARQ process identifier corresponding to the second TB on the fourth uplink carrier;

[0800] Fourteenth information, the fourteenth information is used to indicate the HARQ process identifier corresponding to the second TB on the fifth uplink carrier.

[0801] In some implementations, the receiving unit 1702 is configured to receive a first message on a sixth uplink carrier, and the sending unit 1701 is configured to send a second message on a sixth downlink carrier, where the first message and the second message are associated messages in a random access process.

[0802] In some implementations, the sixth uplink carrier is an uplink carrier in the at least one uplink cluster configured with PRACH resources and / or random access configuration information.

[0803] In some embodiments, the carrier index or carrier number of the sixth downlink carrier is determined based on the random access series and a second parameter, and the second parameter is the number of downlink carriers configured by the first configuration information; or, the carrier index or carrier number of the sixth downlink carrier is determined based on the random access series and a fifth parameter, and the fifth parameter is the number of downlink carriers in the first downlink carrier list, and the first downlink carrier list is a downlink carrier list configured by the network device for receiving the second message; or, the sixth downlink carrier is a downlink carrier associated with the sixth uplink carrier configured by the network device; or, the sixth downlink carrier is one downlink carrier of at least one downlink carrier associated with the random access series and / or PRACH resources.

[0804] In some embodiments, the sending unit 1701 is used to send a second message on a sixth downlink carrier using an RA-RNTI, where the RA-RNTI is calculated based on a sixth parameter and / or a seventh parameter, where the value of the sixth parameter is configured by a network device or is the carrier index of the sixth uplink carrier or is the carrier index of the sixth uplink carrier plus a first offset, and the value of the seventh parameter is configured by a network device or is the cluster index of the uplink cluster in which the sixth uplink carrier is located.

[0805] In some embodiments, each of the at least one cluster includes at least one cell.

[0806] In some implementations, the receiving unit 1702 is configured to receive first capability information of the terminal device reported by the terminal device, where the first capability information includes at least one of the following:

[0807] first information, where the first information is used to indicate a cluster-supporting capability of the terminal device;

[0808] second information, where the second information is used to indicate a maximum number of clusters supported by the terminal device;

[0809] third information, where the third information is used to indicate a maximum number of cells included in a cluster supported by the terminal device;

[0810] Fourth information, the fourth information is used to indicate the frequency band combination of the cluster supported by the terminal device.

[0811] In some embodiments, each cluster in the at least one is associated with a cluster index.

[0812] In some embodiments, each cell of the at least one cell is associated with a cell index.

[0813] In some implementations, cells within the same cluster are downlink synchronized and / or uplink synchronized.

[0814] In some implementations, the sending unit 1701 is configured to send second configuration information to the terminal device, where the second configuration information is used to configure at least one of the following:

[0815] Add one or more clusters;

[0816] Modify one or more clusters;

[0817] Releases one or more clusters.

[0818] In some embodiments, the first configuration information is further used to configure an initial state of each cluster in the at least one cluster; or the initial state of each cluster in the at least one cluster is an activated state or a deactivated state by default.

[0819] In some implementations, the sending unit 1701 is configured to send a first command to the terminal device, where the first command is used to activate and / or deactivate at least part of the at least one cluster.

[0820] In some embodiments, the first command includes at least one of the following: DCI, MAC CE.

[0821] In some embodiments, the first command carries a cluster index and second indication information, where the second indication information is used to indicate whether to activate or deactivate the cluster indicated by the cluster index.

[0822] In some embodiments, the first command carries a first bitmap, each bit in the first bitmap corresponds to one or more cluster indexes, and the value of the bit is used to indicate whether one or more clusters indicated by the corresponding one or more cluster indexes are activated or deactivated.

[0823] In some implementations, the sending unit 1701 is configured to send third configuration information to the terminal device, where the third configuration information is used to configure at least one of the following:

[0824] Add one or more cells to the cluster;

[0825] Modifying one or more cells in a cluster;

[0826] Release one or more cells in a cluster.

[0827] In some embodiments, the first configuration information is further used to configure an initial state of a cell in each of the at least one cluster; or the initial state of a cell in each of the at least one cluster is an activated state or a deactivated state by default.

[0828] In some embodiments, the sending unit 1701 is configured to send a second command to the terminal device, where the second command is used to activate and / or deactivate at least some cells in the at least one cluster.

[0829] In some implementations, the second command includes at least one of the following: DCI, MAC CE.

[0830] In some embodiments, the second command carries a cluster index, a cell index and fourth indication information, and the fourth indication information is used to indicate whether to activate or deactivate the cell indicated by the cell index, wherein the cell indices in different clusters are in independent numbering spaces; or, the second command carries a cell index and fourth indication information, and the fourth indication information is used to indicate whether to activate or deactivate the cell indicated by the cell index, wherein the cell indices in different clusters are in the same numbering space.

[0831] In some embodiments, the second command carries a cluster index and a second bit map, each bit in the second bit map corresponds to one or more cell indices, and the value of the bit is used to indicate whether the one or more cells indicated by the corresponding one or more cell indices are activated or deactivated, wherein the cell indices in different clusters are in independent numbering spaces; or, the second command carries a second bit map, each bit in the second bit map corresponds to one or more cell indices, and the value of the bit is used to indicate whether the one or more cells indicated by the corresponding one or more cell indices are activated or deactivated, wherein the cell indices in different clusters are in the same numbering space.

[0832] In some embodiments, whether the cell supports the sending and / or receiving of the first signal and / or the second signal is determined based on the configuration of the network device, the first signal includes at least one of the following: PDCCH, PDSCH, SSB, CSI-RS, and the second signal includes at least one of the following: PUCCH, PUSCH, SRS, PRACH.

[0833] In some implementations, the cell supports at least one of the following scheduling modes:

[0834] Same-carrier scheduling mode, wherein the same-carrier scheduling mode is that the DCI on the cell schedules the PDSCH on the cell;

[0835] A cross-carrier scheduling method, where the cross-carrier scheduling method is that the DCI on the cell schedules the PDSCH and / or PUSCH on the second cell.

[0836] In some embodiments, the cross-carrier scheduling mode includes a first type of cross-carrier scheduling mode and / or a second type of cross-carrier scheduling mode;

[0837] In the first type of cross-carrier scheduling mode, the cell and the scheduled cell belong to the same cluster, and the scheduled cell is the second cell;

[0838] In the second type of cross-carrier scheduling mode, the cell and the scheduled carrier belong to different clusters, and the scheduled carrier is the second cell.

[0839] In some implementations, for the first type of cross-carrier scheduling,

[0840] The DCI on the cell carries the cell index of the scheduled cell; or,

[0841] The relationship between the cell and the scheduled cell is configured through RRC signaling.

[0842] In some implementations, for the second type of cross-carrier scheduling,

[0843] The DCI on the cell carries the cluster index of the cluster where the scheduled cell is located and the cell index of the scheduled cell, wherein the cell indexes in different clusters are in independent numbering spaces; or,

[0844] The DCI on the cell carries the cell index of the scheduled cell, wherein the cell indexes in different clusters are in the same numbering space; or

[0845] The relationship between the cell and the scheduled cell is configured through RRC signaling.

[0846] In some embodiments, for a third cell in the at least one cluster, HARQ feedback information of a PDSCH on the third cell is transmitted via a PUCCH on a fourth cell;

[0847] The fourth cell is configured through RRC signaling; or,

[0848] The fourth cell is indicated by scheduling the DCI of the third cell.

[0849] In some embodiments, the DCI for scheduling the third cell carries the cluster index of the cluster where the fourth cell is located and the cell index of the fourth cell, wherein the cell indexes in different clusters are in independent numbering spaces; or, the DCI for scheduling the third cell carries the cell index of the fourth cell, wherein the cell indexes in different clusters are in the same numbering space.

[0850] In some embodiments, the sending unit 1701 is used to send the first TB on the fifth cell, and if the number of retransmissions of the first TB exceeds a first threshold value, the terminal device sends the first TB on the sixth cell; and / or, the receiving unit 1702 is used to receive the second TB on the fifth cell, and if the number of retransmissions of the second TB exceeds a second threshold value, the terminal device receives the second TB on the sixth cell.

[0851] In some embodiments, the first TB on the sixth cell is newly transmitted data; and / or the second TB on the sixth cell is newly transmitted data.

[0852] In some implementations, the sending unit 1701 is configured to send a first DCI on the fifth cell, where the first DCI carries at least one of the following:

[0853] fifth information, where the fifth information is used to schedule the sixth cell to newly transmit the first TB;

[0854] The sixth information is used to instruct the network device to give up retransmitting the first TB on the fifth cell and / or instruct the terminal device to clear the cache corresponding to the first HARQ process of the fifth cell, where the first HARQ process is the HARQ process corresponding to the first TB on the fifth cell.

[0855] In some implementations, the sending unit 1701 is configured to send a second DCI on the fifth cell, where the second DCI carries at least one of the following:

[0856] Seventh information, where the seventh information is used to schedule the sixth cell to newly transmit the second TB;

[0857] The eighth information is used to instruct the terminal device to give up retransmitting the second TB on the fifth cell and / or instruct the terminal device to clear the cache corresponding to the second HARQ process of the fifth cell, where the second HARQ process is the HARQ process corresponding to the second TB on the fifth cell.

[0858] In some implementations, the sixth cell and the fifth cell correspond to different HARQ entities.

[0859] In some embodiments, the first TB on the sixth cell is retransmitted data of the first TB on the fifth cell; and / or the second TB on the sixth cell is retransmitted data of the second TB on the fifth cell.

[0860] In some implementations, the sixth cell and the fifth cell correspond to the same HARQ entity.

[0861] In some embodiments, each cell group in the at least one cluster corresponds to a HARQ entity;

[0862] The sixth cell and the fifth cell belong to the same cell group.

[0863] In some embodiments, the sending unit 1701 is used to send fourth configuration information to the terminal device, where the fourth configuration information is used to configure one or more cell groups, where each cell group corresponds to a HARQ entity.

[0864] In some implementations, the sixth cell and the fifth cell correspond to different HARQ entities.

[0865] In some implementations, the sending unit 1701 is configured to send a third DCI on the fifth cell, where the third DCI carries at least one of the following:

[0866] Ninth information, where the ninth information is used to schedule the six cells to retransmit the first TB;

[0867] Tenth information, where the tenth information is used to indicate a HARQ process identifier corresponding to the first TB on the fifth cell;

[0868] The eleventh information is used to indicate the HARQ process identifier corresponding to the first TB in the six cells.

[0869] In some embodiments, the receiving unit 1702 is configured to receive a first message on a seventh cell, and the sending unit 1701 is configured to send a second message on an eighth cell, where the first message and the second message are associated messages in a random access process.

[0870] In some implementations, the seventh cell is a cell in the at least one cluster configured with PRACH resources and / or random access configuration information.

[0871] In some embodiments, the cell index or cell number of the eighth cell is determined based on a random access series and a second parameter, where the second parameter is the number of cells configured by the first configuration information; or, the cell index or cell number of the eighth cell is determined based on a random access series and a fifth parameter, where the fifth parameter is the number of cells in a first cell list, where the first cell list is a cell list configured by a network device for receiving the second message; or, the eighth cell is a cell associated with the seventh cell configured by a network device; or, the eighth cell is one of at least one cell associated with a random access series and / or PRACH resources.

[0872] In some embodiments, the sending unit 1701 is used to send a second message on the eighth cell using the RA-RNTI, where the RA-RNTI is calculated based on the sixth parameter and / or the seventh parameter, the value of the sixth parameter is configured by the network device or is the carrier index of the uplink carrier in the eighth cell or is the carrier index of the uplink carrier in the eighth cell plus a first offset, and the seventh parameter is configured by the network device or is the cluster index of the cluster in which the eighth cell is located.

[0873] In some implementations, the correspondence between the at least one cluster and the MAC entity includes at least one of the following:

[0874] One cluster corresponds to one MAC entity;

[0875] Multiple clusters correspond to one MAC entity.

[0876] In some embodiments, the MAC entity corresponds to one or more HARQ entities, and each HARQ entity corresponds to a carrier group or a cell group.

[0877] In some embodiments, the MAC entity further includes an upper layer entity, and the upper layer entity includes at least one of the following: an RLC entity, a PDCP entity, an SDAP entity, an RRC entity, and a NAS entity; wherein,

[0878] The MAC entity and the upper layer entity are deployed in the cloud; or,

[0879] The MAC entity is deployed on the access network side, and the upper layer entity is deployed on the cloud side; or,

[0880] The MAC entity and the RLC entity are deployed on the access network side, and entities in the upper layer except the RLC entity are deployed on the cloud.

[0881] In some embodiments, the RRC entity is associated with one or more sites; or, the RRC entity is associated with an area, where the area is an area defined by one or more cell lists or an area governed by a cloud platform.

[0882] In some embodiments, the sending unit 1701 is configured to send a first RRC signaling, where the first RRC signaling is used to configure updated system broadcast information. The terminal device does not monitor P-RNTI-scrambled DCI and SI-RNTI-scrambled DCI, where the P-RNTI-scrambled DCI is used to schedule a paging message, where the paging message is used to carry a system broadcast change indication, and the SI-RNTI-scrambled DCI is used to schedule updated system broadcast information.

[0883] In some embodiments, the sending unit 1701 is used to send a second RRC signaling, and the second RRC signaling is used to configure at least one of the following: a system broadcast change indication, a target carrier or target cell where a system broadcast information change occurs, a target SIB received by the terminal device, a scheduling period of the target SIB, and a time range for the terminal device to receive the target SIB scheduling information. The second RRC signaling is used for the terminal device to monitor the SI-RNTI-scrambled DCI, and the SI-RNTI-scrambled DCI is used to schedule updated system broadcast information. The terminal device does not monitor the P-RNTI-scrambled DCI, and the P-RNTI-scrambled DCI is used to schedule paging messages, and the paging messages are used to carry the system broadcast change indication.

[0884] In some embodiments, the sending unit 1701 is used to send P-RNTI-scrambled DCI on the target carrier or target cell, and the P-RNTI-scrambled DCI is used to schedule paging messages. The P-RNTI-scrambled DCI and / or the paging message are used to notify at least one of the following: a system broadcast change indication, a target carrier or target cell where a system broadcast information change occurs, a target SIB received by the terminal device, a scheduling period of the target SIB, and a time range for the terminal device to receive the target SIB scheduling information; the P-RNTI-scrambled DCI and / or the paging message are used for the terminal device to monitor SI-RNTI-scrambled DCI, and the SI-RNTI-scrambled DCI is used to schedule updated system broadcast information.

[0885] In some implementations, the sending unit 1701 is configured to send a third RRC signaling, where the third RRC signaling is used to configure:

[0886] The carrier index of the target carrier, wherein the carrier indexes in different clusters are in the same numbering space; or

[0887] The cluster index of the cluster where the target carrier is located and the carrier index of the target carrier, wherein the carrier indexes in different clusters are in independent numbering spaces; or

[0888] The cell index of the target cell, wherein the cell indexes in different clusters are in the same numbering space; or

[0889] The cluster index of the cluster where the target cell is located and the cell index of the target cell, wherein the cell indexes in different clusters are in independent numbering spaces.

[0890] In some embodiments, the device further includes: a determination unit for determining the carrier index or carrier number of the target carrier based on a first parameter and a second parameter, the first parameter being the identifier of the terminal device, and the second parameter being the number of downlink carriers configured by the first configuration information, wherein the carrier indexes in different clusters are in the same numbering space; or, determining the carrier index or carrier number of the target carrier based on the first parameter and the third parameter, and determining the cluster index or cluster number of the cluster where the target carrier is located based on the first parameter and the fourth parameter, the first parameter being the identifier of the terminal device, the third parameter being the number of downlink carriers in the cluster where the target carrier is located, and the fourth parameter being the number of downlink clusters configured by the first configuration information, wherein the carrier indexes in different clusters are in the same numbering space. The carrier index is in an independent numbering space; or, the cell index or cell number of the target cell is determined based on a first parameter and a second parameter, the first parameter is the identifier of the terminal device, and the second parameter is the number of cells configured by the first configuration information, wherein the cell indexes in different clusters are in the same numbering space; or, the cell index or cell number of the target cell is determined based on the first parameter and the third parameter, and the cluster index or cluster number of the cluster where the target cell is located is determined based on the first parameter and the fourth parameter, the first parameter is the identifier of the terminal device, the third parameter is the number of cells in the cluster where the target cell is located, and the fourth parameter is the number of clusters configured by the first configuration information, wherein the cell indexes in different clusters are in independent numbering spaces.

[0891] In some embodiments, the sending unit 1701 is used to send fifth configuration information to the terminal device, and the fifth configuration information is used to configure the terminal device to trigger the terminal device to notify the target cluster of the radio link failure through uplink RRC signaling when a radio link failure occurs in the target cluster.

[0892] In some embodiments, the at least one cluster belongs to one or more sites.

[0893] In some embodiments, the network device is a first site, and the sending unit 1701 is used to send first configuration information to the terminal device, where the first configuration information includes configuration information of the cluster on the first site side and configuration information of the cluster on the at least one second site side; wherein the configuration information of the cluster on the second site side is sent by the second site to the first site through a container.

[0894] In some embodiments, the sending unit 1701 is used to send a cluster add request message to the second site; the receiving unit 1702 is used to receive a cluster add response message sent by the second site, and the cluster add response message carries a container, and the container is used to carry the configuration information of the cluster on the second site side.

[0895] In some implementations, the cluster add request message carries at least one of the following:

[0896] fifth indication information, where the fifth indication information is used to indicate a bearer configuration that the second site needs to provide;

[0897] Sixth indication information, where the sixth indication information is used to indicate a protocol stack entity that the second site needs to provide.

[0898] Those skilled in the art should understand that the relevant description of the above-mentioned carrier aggregation device in the embodiment of the present application can be understood with reference to the relevant description of the carrier aggregation method in the embodiment of the present application.

[0899] Figure 18 is a schematic diagram of a communication device 1800 provided in an embodiment of the present application. The communication device can be a terminal device or a network device. The communication device 1800 shown in Figure 18 includes a processor 1810, which can call and execute a computer program from a memory to implement the method in the embodiment of the present application.

[0900] Optionally, as shown in FIG18 , the communication device 1800 may further include a memory 1820. The processor 1810 may call and execute a computer program from the memory 1820 to implement the method in the embodiment of the present application.

[0901] The memory 1820 may be a separate device independent of the processor 1810 , or may be integrated into the processor 1810 .

[0902] Optionally, as shown in FIG18 , the communication device 1800 may further include a transceiver 1830 , and the processor 1810 may control the transceiver 1830 to communicate with other devices, specifically, to send information or data to other devices, or to receive information or data sent by other devices.

[0903] The transceiver 1830 may include a transmitter and a receiver. The transceiver 1830 may further include an antenna, and the number of antennas may be one or more.

[0904] Optionally, the communication device 1800 may specifically be a network device in an embodiment of the present application, and the communication device 1800 may implement the corresponding processes implemented by the network device in each method in the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0905] Optionally, the communication device 1800 may specifically be a mobile terminal / terminal device of an embodiment of the present application, and the communication device 1800 may implement the corresponding processes implemented by the mobile terminal / terminal device in each method of the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0906] Figure 19 is a schematic structural diagram of a chip according to an embodiment of the present application. The chip 1900 shown in Figure 19 includes a processor 1910, which can call and run a computer program from a memory to implement the method according to the embodiment of the present application.

[0907] Optionally, as shown in FIG19 , the chip 1900 may further include a memory 1920. The processor 1910 may call and execute a computer program from the memory 1920 to implement the method in the embodiment of the present application.

[0908] The memory 1920 may be a separate device independent of the processor 1910 , or may be integrated into the processor 1910 .

[0909] Optionally, the chip 1900 may further include an input interface 1930. The processor 1910 may control the input interface 1930 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

[0910] Optionally, the chip 1900 may further include an output interface 1940. The processor 1910 may control the output interface 1940 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

[0911] Optionally, the chip can be applied to the network device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the network device in each method of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0912] Optionally, the chip can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0913] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0914] FIG20 is a schematic block diagram of a communication system 2000 provided in an embodiment of the present application. As shown in FIG20 , the communication system 2000 includes a terminal device 2010 and a network device 2020 .

[0915] Among them, the terminal device 2010 can be used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 2020 can be used to implement the corresponding functions implemented by the network device in the above method. For the sake of brevity, they are not repeated here.

[0916] It should be understood that the processor of the embodiments of the present application may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method embodiment can be completed by hardware integrated logic circuits in the processor or software instructions. The above processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. The various methods, steps, and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the embodiments of the present application can be directly embodied as being executed by a hardware decoding processor, or can be executed by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium mature in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0917] It is understood that the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0918] It should be understood that the above-mentioned memories are exemplary but not restrictive. For example, the memories in the embodiments of the present application may also be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM RAM (DR RAM), etc. In other words, the memories in the embodiments of the present application are intended to include, but are not limited to, these and any other suitable types of memories.

[0919] An embodiment of the present application also provides a computer-readable storage medium for storing a computer program.

[0920] Optionally, the computer-readable storage medium can be applied to the network device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0921] Optionally, the computer-readable storage medium can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0922] An embodiment of the present application also provides a computer program product, including computer program instructions.

[0923] Optionally, the computer program product can be applied to the network device in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0924] Optionally, the computer program product can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0925] The embodiment of the present application also provides a computer program.

[0926] Optionally, the computer program can be applied to the network device in the embodiments of the present application. When the computer program runs on a computer, the computer executes the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not described here.

[0927] Optionally, the computer program can be applied to the mobile terminal / terminal device in the embodiments of the present application. When the computer program runs on the computer, the computer executes the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0928] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0929] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0930] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0931] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0932] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0933] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0934] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present application should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. A carrier aggregation method, the method comprising: The terminal device receives first configuration information sent by the network device, where the first configuration information is used to configure at least one cluster, each of the at least one cluster including at least one carrier or at least one cell.

2. The method according to claim 1, wherein The at least one cluster includes at least one downlink cluster and / or at least one uplink cluster, each downlink cluster includes at least one downlink carrier, and each uplink cluster includes at least one uplink carrier.

3. The method according to claim 2, wherein: Before the terminal device receives the first configuration information, the method further includes: The terminal device reports first capability information of the terminal device to the network device, where the first capability information includes at least one of the following: First information, where the first information is used to indicate a capability of the terminal device to support a downlink cluster and / or a capability of the terminal device to support an uplink cluster; Second information, where the second information is used to indicate a maximum number of downlink clusters and / or a maximum number of uplink clusters supported by the terminal device; Third information, where the third information is used to indicate a maximum number of downlink carriers included in a downlink cluster and / or a maximum number of uplink carriers included in an uplink cluster supported by the terminal device; Fourth information, the fourth information is used to indicate the frequency band combination of the downlink cluster and / or uplink cluster supported by the terminal device.

4. The method according to claim 2 or 3, wherein: Each cluster in the at least one downlink cluster and / or the at least one uplink cluster is associated with a cluster index.

5. The method according to any one of claims 2 to 4, wherein Each downlink carrier in the at least one downlink carrier is associated with a downlink carrier index; and / or, Each uplink carrier in the at least one uplink carrier is associated with an uplink carrier index.

6. The method according to any one of claims 2 to 5, wherein Downlink carriers in the same downlink cluster are downlink synchronized; and / or, The uplink carriers in the same uplink cluster are uplink synchronized.

7. The method according to any one of claims 2 to 6, wherein The method further comprises: For each downlink cluster, the terminal device performs downlink synchronization for the downlink cluster based on a first downlink carrier in the downlink cluster; and / or, For each uplink cluster, the terminal device performs uplink synchronization for the uplink cluster based on a first uplink carrier in the uplink cluster.

8. The method according to claim 7, wherein: The first downlink carrier is any downlink carrier in the downlink cluster or a designated downlink carrier in the downlink cluster, and the designated downlink carrier is a downlink carrier indicated by a network device or a default downlink carrier; and / or, The first uplink carrier is any uplink carrier in the uplink cluster or a designated uplink carrier in the uplink cluster. The designated uplink carrier is an uplink carrier indicated by a network device or a default uplink carrier.

9. The method according to claim 7 or 8, wherein The terminal device performs uplink synchronization for the uplink cluster based on the first uplink carrier in the uplink cluster, including: The terminal device uses a first random access resource to initiate a random access process to a first uplink carrier in the uplink cluster to achieve uplink synchronization; the first random access resource is a random access resource configured by the network device specifically for the uplink cluster.

10. The method according to any one of claims 2 to 9, wherein The method further comprises: The terminal device receives second configuration information sent by the network device, where the second configuration information is used to configure at least one of the following: Add one or more downlink clusters and / or add one or more uplink clusters; Modifying one or more downlink clusters and / or modifying one or more uplink clusters; One or more downlink clusters are released and / or one or more uplink clusters are released.

11. The method according to any one of claims 2 to 10, wherein The first configuration information is further used to configure an initial state of each cluster in the at least one downlink cluster and / or the at least one uplink cluster; or, The initial state of each cluster in the at least one downlink cluster and / or the at least one uplink cluster is an activated state or a deactivated state by default.

12. The method according to any one of claims 2 to 11, wherein The method further comprises: The terminal device receives a first command sent by the network device, where the first command is used to activate and / or deactivate at least part of the at least one downlink cluster and / or at least one uplink cluster.

13. The method according to claim 12, wherein: The first command includes at least one of the following: downlink control information DCI, and a media access control MAC control element CE.

14. The method according to claim 12 or 13, wherein: The first command carries a cluster index, first indication information, and second indication information, wherein the first indication information is used to indicate whether to activate or deactivate the downlink or uplink, and the second indication information is used to indicate whether to activate or deactivate the cluster indicated by the cluster index, wherein the cluster index of the downlink cluster and the cluster index of the uplink cluster are in independent numbering spaces; or The first command carries a cluster index and second indication information, where the second indication information is used to indicate whether to activate or deactivate the cluster indicated by the cluster index, wherein the cluster index of the downlink cluster and the cluster index of the uplink cluster are in the same numbering space; or The first command carries a cluster index and second indication information, and the second indication information is used to indicate whether to activate or deactivate the cluster indicated by the cluster index, wherein the cluster index of the downlink cluster and the cluster index of the uplink cluster are in independent numbering spaces, and the associated information of the first command is used to determine whether to activate or deactivate the downlink or the uplink.

15. The method according to claim 12 or 13, wherein: The first command carries a first bitmap and first indication information, where each bit in the first bitmap corresponds to one or more cluster indexes, and the value of the bit is used to indicate whether one or more clusters indicated by the corresponding one or more cluster indexes are activated or deactivated, and the first indication information is used to indicate whether activation or deactivation is performed for the downlink or for the uplink, wherein the cluster index of the downlink cluster and the cluster index of the uplink cluster are in independent numbering spaces; or The first command carries a first bitmap, where each bit in the first bitmap corresponds to one or more cluster indexes, and the value of the bit is used to indicate whether one or more clusters indicated by the corresponding one or more cluster indexes are activated or deactivated, wherein the cluster index of the downlink cluster and the cluster index of the uplink cluster are in the same numbering space; or The first command carries a first bit map, each bit in the first bit map corresponds to one or more cluster indexes, and the value of the bit is used to indicate whether one or more clusters indicated by the corresponding one or more cluster indexes are activated or deactivated, wherein the cluster index of the downlink cluster and the cluster index of the uplink cluster are in independent numbering spaces, and the associated information of the first command is used to determine whether to activate or deactivate the downlink or the uplink.

16. The method according to claim 14 or 15, wherein: In the case where the first command is a MAC CE, the associated information of the first command is a logical channel identifier associated with the MAC CE.

17. The method according to any one of claims 2 to 16, wherein The method further comprises: The terminal device receives third configuration information sent by the network device, where the third configuration information is used to configure at least one of the following: Add one or more downlink carriers in a downlink cluster and / or add one or more uplink carriers in an uplink cluster; Modifying one or more downlink carriers in a downlink cluster and / or modifying one or more uplink carriers in an uplink cluster; One or more downlink carriers are released in the downlink cluster and / or one or more uplink carriers are released in the uplink cluster.

18. The method according to any one of claims 2 to 17, wherein The first configuration information is further used to configure an initial state of a carrier in each of the at least one downlink cluster and / or the at least one uplink cluster; or, The initial state of the carriers in each of the at least one downlink cluster and / or the at least one uplink cluster is an activated state or a deactivated state by default.

19. The method according to any one of claims 2 to 18, wherein The method further comprises: The terminal device receives a second command sent by the network device, where the second command is used to activate and / or deactivate at least some carriers in the at least one downlink cluster and / or at least one uplink cluster.

20. The method according to claim 19, wherein The second command includes at least one of the following: DCI, MAC CE.

21. The method according to claim 19 or 20, wherein The second command carries a cluster index, a carrier index, third indication information, and fourth indication information, the third indication information being used to indicate whether to activate or deactivate the downlink or the uplink, and the fourth indication information being used to indicate whether to activate or deactivate the carrier indicated by the carrier index, wherein the cluster index of the downlink cluster and the cluster index of the uplink cluster are in independent numbering spaces, and the carrier indexes in different clusters in the downlink cluster or the uplink cluster are in independent numbering spaces; or The second command carries a cluster index, a carrier index, and fourth indication information, where the fourth indication information is used to indicate whether to activate or deactivate the carrier indicated by the carrier index, wherein the cluster index of the downlink cluster and the cluster index of the uplink cluster are in the same numbering space, and the carrier indexes in different clusters in the downlink cluster or the uplink cluster are in independent numbering spaces; or The second command carries a cluster index, a carrier index, and fourth indication information, where the fourth indication information is used to indicate whether to activate or deactivate the carrier indicated by the carrier index, wherein the cluster index of the downlink cluster and the cluster index of the uplink cluster are in independent numbering spaces, and the carrier indexes in different clusters in the downlink cluster or the uplink cluster are in independent numbering spaces, and the associated information of the second command is used to determine whether to activate or deactivate the downlink or the uplink; or The second command carries a carrier index, third indication information, and fourth indication information, the third indication information being used to indicate whether to activate or deactivate the downlink or the uplink, and the fourth indication information being used to indicate whether to activate or deactivate the carrier indicated by the carrier index, wherein the carrier index within the downlink cluster and the carrier index within the uplink cluster are in independent numbering spaces, and the carrier indexes within different clusters in the downlink cluster or the uplink cluster are in the same numbering space; or The second command carries a carrier index and fourth indication information, where the fourth indication information is used to indicate whether to activate or deactivate the carrier indicated by the carrier index, wherein the carrier index in the downlink cluster and the carrier index in the uplink cluster are in the same numbering space; or The second command carries a carrier index and fourth indication information, where the fourth indication information is used to indicate whether to activate or deactivate the carrier indicated by the carrier index, wherein the carrier index within the downlink cluster and the carrier index within the uplink cluster are in independent numbering spaces, and the carrier indexes in different clusters in the downlink cluster or uplink cluster are in the same numbering space, and the associated information of the second command is used to determine whether to activate or deactivate the downlink or the uplink.

22. The method according to claim 19 or 20, wherein The second command carries a cluster index, a second bitmap, and third indication information, where each bit in the second bitmap corresponds to one or more carrier indexes, and the value of the bit is used to indicate whether one or more carriers indicated by the corresponding one or more carrier indexes are activated or deactivated, and the third indication information is used to indicate whether activation or deactivation is performed for the downlink or for the uplink, wherein the cluster index of the downlink cluster and the cluster index of the uplink cluster are in an independent numbering space, and the carrier indexes in different clusters in the downlink cluster or the uplink cluster are in an independent numbering space; or, The second command carries a cluster index and a second bitmap, each bit in the second bitmap corresponds to one or more carrier indexes, and the value of the bit is used to indicate whether one or more carriers indicated by the corresponding one or more carrier indexes are activated or deactivated, wherein the cluster index of the downlink cluster and the cluster index of the uplink cluster are in the same numbering space, and the carrier indexes in different clusters in the downlink cluster or the uplink cluster are in independent numbering spaces; or The second command carries a cluster index and a second bitmap, each bit in the second bitmap corresponds to one or more carrier indexes, and the value of the bit is used to indicate whether one or more carriers indicated by the corresponding one or more carrier indexes are activated or deactivated, wherein the cluster index of the downlink cluster and the cluster index of the uplink cluster are in an independent numbering space, and the carrier indexes in different clusters in the downlink cluster or uplink cluster are in an independent numbering space, and the associated information of the second command is used to determine whether to activate or deactivate the downlink or the uplink; or The second command carries a second bitmap and third indication information, where each bit in the second bitmap corresponds to one or more carrier indexes, and the value of the bit is used to indicate whether one or more carriers indicated by the corresponding one or more carrier indexes are activated or deactivated, and the third indication information is used to indicate whether activation or deactivation is performed for the downlink or for the uplink, wherein the carrier index within the downlink cluster and the carrier index within the uplink cluster are in an independent numbering space, and the carrier indexes in different clusters in the downlink cluster or the uplink cluster are in the same numbering space; or, The second command carries a second bitmap, each bit in the second bitmap corresponds to one or more carrier indexes, and the value of the bit is used to indicate whether one or more carriers indicated by the corresponding one or more carrier indexes are activated or deactivated, wherein the carrier indexes in the downlink cluster and the carrier indexes in the uplink cluster are in the same numbering space; or, The second command carries a second bit map, each bit in the second bit map corresponds to one or more carrier indexes, and the value of the bit is used to indicate whether one or more carriers indicated by the corresponding one or more carrier indexes are activated or deactivated, wherein the carrier index within the downlink cluster and the carrier index within the uplink cluster are in an independent numbering space, and the carrier indexes in different clusters in the downlink cluster or uplink cluster are in the same numbering space, and the associated information of the second command is used to determine whether to activate or deactivate the downlink or the uplink.

23. The method according to claim 21 or 22, wherein In the case where the second command is a MAC CE, the associated information of the second command is a logical channel identifier associated with the MAC CE.

24. The method according to any one of claims 19 to 23, wherein For a deactivated downlink carrier, the behavior of the terminal device on the downlink carrier includes at least one of the following: not monitoring the physical downlink control channel PDCCH, not receiving the physical downlink shared channel PDSCH, performing channel state information CSI measurement, and performing beam measurement.

25. The method according to any one of claims 19 to 24, wherein For a deactivated uplink carrier, the behavior of the terminal device on the uplink carrier includes at least one of the following: not sending a physical uplink shared channel PUSCH, not sending a physical uplink control channel PUCCH, and not sending a sounding reference signal SRS.

26. The method according to any one of claims 2 to 25, wherein For a deactivated downlink carrier, whether the downlink carrier supports sending and / or receiving a first signal is determined based on the configuration of the network device, where the first signal includes at least one of the following: PDCCH, PDSCH, synchronization signal block SSB, and channel state information reference signal CSI-RS.

27. The method according to any one of claims 2 to 26, wherein For a deactivated uplink carrier, whether the uplink carrier supports sending and / or receiving a second signal is determined based on the configuration of the network device, where the second signal includes at least one of the following: PUCCH, PUSCH, SRS, and physical random access channel PRACH.

28. The method according to any one of claims 2 to 27, wherein The downlink carrier supports at least one of the following scheduling modes: Same-carrier scheduling mode, wherein the same-carrier scheduling mode is that the DCI on the downlink carrier schedules the PDSCH on the downlink carrier; A cross-carrier scheduling mode is that the DCI on the downlink carrier schedules the PDSCH on the second downlink carrier and / or schedules the PUSCH on the second uplink carrier.

29. The method according to claim 28, wherein The cross-carrier scheduling mode includes a first type of cross-carrier scheduling mode and / or a second type of cross-carrier scheduling mode; In the first type of cross-carrier scheduling mode, the downlink carrier and the scheduled carrier belong to the same downlink cluster, and the scheduled carrier is the second downlink carrier; In the second type of cross-carrier scheduling mode, the downlink carrier and the scheduled carrier belong to different downlink clusters, and the scheduled carrier includes the second downlink carrier and / or the second uplink carrier.

30. The method according to claim 29, wherein For the first type of cross-carrier scheduling method, The DCI on the downlink carrier carries the carrier index of the scheduled carrier; or, The relationship between the downlink carrier and the scheduled carrier is configured through RRC signaling.

31. The method according to claim 29, wherein For the second type of cross-carrier scheduling method, The DCI on the downlink carrier carries the cluster index of the cluster where the scheduled carrier is located and the carrier index of the scheduled carrier, wherein the carrier indexes in different clusters are in independent numbering spaces; or, The DCI on the downlink carrier carries the carrier index of the scheduled carrier, wherein the carrier indexes in different clusters are in the same numbering space; or The relationship between the downlink carrier and the scheduled carrier is configured through RRC signaling.

32. The method according to any one of claims 2 to 31, wherein For a third downlink carrier in the at least one downlink cluster, hybrid automatic repeat request HARQ feedback information of the PDSCH on the third downlink carrier is transmitted through the PUCCH on the third uplink carrier; The third uplink carrier is configured through radio resource control RRC signaling; or, The third uplink carrier is indicated by a DCI that schedules the third downlink carrier.

33. The method according to claim 32, wherein The DCI for scheduling the third downlink carrier carries the cluster index of the cluster where the third uplink carrier is located and the carrier index of the third uplink carrier, wherein the carrier indexes in different clusters are in independent numbering spaces; or, The DCI for scheduling the third downlink carrier carries the carrier index of the third uplink carrier, wherein the carrier indexes in different clusters are in the same numbering space.

34. The method according to any one of claims 2 to 33, wherein The method further comprises: The terminal device receives a first transport block TB on a fourth downlink carrier, and if the number of retransmissions of the first TB exceeds a first threshold, the terminal device receives the first TB on a fifth downlink carrier; and / or, The terminal device sends the second TB on the fourth uplink carrier. If the number of retransmissions of the second TB exceeds a second threshold, the terminal device sends the second TB on the fifth uplink carrier.

35. The method according to claim 34, wherein The first TB on the fifth downlink carrier is new transmission data; and / or, The second TB on the fifth uplink carrier is new transmission data.

36. The method of claim 35, wherein: Before the terminal device receives the first TB on the fifth downlink carrier, the method further includes: The terminal device receives a first DCI on the fourth downlink carrier, where the first DCI carries at least one of the following: fifth information, where the fifth information is used to schedule the fifth downlink carrier to newly transmit the first TB; The sixth information is used to instruct the network device to abandon retransmission of the first TB on the fourth downlink carrier and / or instruct the terminal device to clear the cache corresponding to the first HARQ process of the fourth downlink carrier, where the first HARQ process is the HARQ process corresponding to the first TB on the fourth downlink carrier.

37. The method according to claim 35, wherein Before the terminal device sends the second TB on the fifth uplink carrier, the method further includes: The terminal device receives a second DCI on a fourth downlink carrier, where the second DCI carries at least one of the following: seventh information, where the seventh information is used to schedule the fifth uplink carrier to newly transmit the second TB; The eighth information is used to instruct the terminal device to abandon retransmission of the second TB on the fourth uplink carrier and / or instruct the terminal device to clear the cache corresponding to the second HARQ process of the fourth uplink carrier, where the second HARQ process is the HARQ process corresponding to the second TB on the fourth uplink carrier.

38. The method according to any one of claims 35 to 37, wherein The fifth downlink carrier and the fourth downlink carrier correspond to different HARQ entities; and / or, The fifth uplink carrier and the fourth uplink carrier correspond to different HARQ entities.

39. The method of claim 34, wherein: The first TB on the fifth downlink carrier is retransmitted data of the first TB on the fourth downlink carrier; and / or, The second TB on the fifth uplink carrier is retransmitted data of the second TB on the fourth uplink carrier.

40. The method of claim 39, wherein The fifth downlink carrier and the fourth downlink carrier correspond to the same HARQ entity; and / or, The fifth uplink carrier and the fourth uplink carrier correspond to the same HARQ entity.

41. The method according to claim 39 or 40, wherein Each carrier group in the at least one downlink cluster and / or the at least one uplink cluster corresponds to a HARQ entity; The fifth downlink carrier and the fourth downlink carrier belong to the same carrier group, and / or the fifth uplink carrier and the fourth uplink carrier belong to the same carrier group.

42. The method according to claim 41, wherein The method further comprises: The terminal device receives fourth configuration information sent by the network device, where the fourth configuration information is used to configure one or more carrier groups, where each carrier group corresponds to a HARQ entity.

43. The method of claim 39, wherein: The fifth downlink carrier and the fourth downlink carrier correspond to different HARQ entities; and / or, The fifth uplink carrier and the fourth uplink carrier correspond to different HARQ entities.

44. The method according to claim 43, wherein The method further comprises: The terminal device receives a third DCI on a fourth downlink carrier, where the third DCI carries at least one of the following: Ninth information, where the ninth information is used to schedule the fifth downlink carrier to retransmit the first TB; Tenth information, where the tenth information is used to indicate a HARQ process identifier corresponding to the first TB on the fourth downlink carrier; The eleventh information is used to indicate the HARQ process identifier corresponding to the first TB on the fifth downlink carrier.

45. The method of claim 43, wherein The method further comprises: The terminal device receives a fourth DCI on a fourth downlink carrier, where the fourth DCI carries at least one of the following: Twelfth information, the twelfth information is used to schedule the fifth uplink carrier to retransmit the second TB; Thirteenth information, the thirteenth information is used to indicate the HARQ process identifier corresponding to the second TB on the fourth uplink carrier; Fourteenth information, the fourteenth information is used to indicate the HARQ process identifier corresponding to the second TB on the fifth uplink carrier.

46. ​​The method according to any one of claims 2 to 45, wherein The method further comprises: The terminal device sends a first message on a sixth uplink carrier and receives a second message on a sixth downlink carrier, where the first message and the second message are associated messages in a random access process.

47. The method of claim 46, wherein The sixth uplink carrier is an uplink carrier in the at least one uplink cluster configured with PRACH resources and / or random access configuration information.

48. The method according to claim 46 or 47, wherein The carrier index or carrier number of the sixth downlink carrier is determined based on a random access sequence and a second parameter, where the second parameter is the number of downlink carriers configured by the first configuration information; or A carrier index or a carrier number of the sixth downlink carrier is determined based on a random access sequence and a fifth parameter, where the fifth parameter is the number of downlink carriers in a first downlink carrier list, where the first downlink carrier list is a downlink carrier list configured by the network device for receiving the second message; or, The sixth downlink carrier is a downlink carrier associated with the sixth uplink carrier configured by the network device; or, The sixth downlink carrier is a downlink carrier among at least one downlink carrier associated with a random access sequence and / or a PRACH resource.

49. The method according to any one of claims 46 to 48, wherein The receiving a second message on the sixth downlink carrier includes: The terminal device uses RA-RNTI to receive a second message on the sixth downlink carrier, and the RA-RNTI is calculated based on the sixth parameter and / or the seventh parameter. The value of the sixth parameter is configured by the network device or is the carrier index of the sixth uplink carrier or is the carrier index of the sixth uplink carrier plus the first offset. The value of the seventh parameter is configured by the network device or is the cluster index of the uplink cluster where the sixth uplink carrier is located.

50. The method of claim 1, wherein Each of the at least one cluster includes at least one cell.

51. The method of claim 50, wherein: Before the terminal device receives the first configuration information, the method further includes: The terminal device reports first capability information of the terminal device to the network device, where the first capability information includes at least one of the following: first information, where the first information is used to indicate a cluster-supporting capability of the terminal device; second information, where the second information is used to indicate a maximum number of clusters supported by the terminal device; third information, where the third information is used to indicate a maximum number of cells included in a cluster supported by the terminal device; Fourth information, the fourth information is used to indicate the frequency band combination of the cluster supported by the terminal device.

52. The method according to claim 50 or 51, wherein Each cluster in the at least one is associated with a cluster index.

53. The method according to any one of claims 50 to 52, wherein Each cell in the at least one cell is associated with a cell index.

54. The method according to any one of claims 50 to 53, wherein The cells in the same cluster are downlink synchronized and / or uplink synchronized.

55. The method according to any one of claims 50 to 54, wherein The method further comprises: For each cluster, the terminal device performs downlink synchronization and / or uplink synchronization for the cluster based on the first cell in the cluster.

56. The method of claim 55, wherein: The first cell is any one cell in the cluster or a designated cell in the cluster, and the designated cell is a cell indicated by a network device or a default cell.

57. The method according to claim 55 or 56, wherein The terminal device performs uplink synchronization for the cluster based on the first cell in the cluster, including: The terminal device uses a first random access resource to initiate a random access process to a first cell in the cluster to achieve uplink synchronization; the first random access resource is a random access resource configured by the network device specifically for the cluster.

58. The method according to any one of claims 50 to 57, wherein The method further comprises: The terminal device receives second configuration information sent by the network device, where the second configuration information is used to configure at least one of the following: Add one or more clusters; Modify one or more clusters; Releases one or more clusters.

59. The method according to any one of claims 50 to 58, wherein The first configuration information is further used to configure an initial state of each cluster in the at least one cluster; or, An initial state of each of the at least one cluster is an activated state or a deactivated state by default.

60. The method according to any one of claims 50 to 59, wherein The method further comprises: The terminal device receives a first command sent by the network device, where the first command is used to activate and / or deactivate at least part of the at least one cluster.

61. The method of claim 60, wherein: The first command includes at least one of the following: DCI, MAC CE.

62. The method according to claim 60 or 61, wherein The first command carries a cluster index and second indication information, where the second indication information is used to indicate whether to activate or deactivate the cluster indicated by the cluster index.

63. The method according to claim 60 or 61, wherein The first command carries a first bitmap, each bit in the first bitmap corresponds to one or more cluster indexes, and the value of the bit is used to indicate whether one or more clusters indicated by the corresponding one or more cluster indexes are activated or deactivated.

64. The method according to any one of claims 50 to 63, wherein The method further comprises: The terminal device receives third configuration information sent by the network device, where the third configuration information is used to configure at least one of the following: Add one or more cells to the cluster; Modifying one or more cells in a cluster; Release one or more cells in a cluster.

65. The method according to any one of claims 50 to 64, wherein The first configuration information is further used to configure an initial state of a cell in each of the at least one cluster; or, An initial state of a cell in each of the at least one cluster is an activated state or a deactivated state by default.

66. The method according to any one of claims 50 to 65, wherein The method further comprises: The terminal device receives a second command sent by the network device, where the second command is used to activate and / or deactivate at least some cells in the at least one cluster.

67. The method of claim 66, wherein The second command includes at least one of the following: DCI, MAC CE.

68. The method according to claim 66 or 67, wherein The second command carries a cluster index, a cell index, and fourth indication information, where the fourth indication information is used to indicate whether to activate or deactivate the cell indicated by the cell index, wherein the cell indexes in different clusters are in independent numbering spaces; or The second command carries a cell index and fourth indication information, where the fourth indication information is used to indicate whether to activate or deactivate the cell indicated by the cell index, wherein the cell indexes in different clusters are in the same numbering space.

69. The method according to claim 66 or 67, wherein The second command carries a cluster index and a second bitmap, each bit in the second bitmap corresponds to one or more cell indexes, and the value of the bit is used to indicate whether one or more cells indicated by the corresponding one or more cell indexes are activated or deactivated, wherein the cell indexes in different clusters are in independent numbering spaces; or The second command carries a second bit map, each bit in the second bit map corresponds to one or more cell indexes, and the value of the bit is used to indicate whether one or more cells indicated by the corresponding one or more cell indexes are activated or deactivated, wherein the cell indexes in different clusters are in the same numbering space.

70. The method according to any one of claims 66 to 69, wherein For a deactivated cell, the behavior of the terminal device on the cell includes at least one of the following: not monitoring PDCCH, not receiving PDSCH, performing CSI measurement, performing beam measurement, not sending PUSCH, not sending PUCCH, and not sending SRS.

71. The method of any one of claims 50 to 70, wherein Whether the cell supports sending and / or receiving the first signal and / or the second signal is determined based on the configuration of the network device, the first signal includes at least one of the following: PDCCH, PDSCH, SSB, CSI-RS, and the second signal includes at least one of the following: PUCCH, PUSCH, SRS, PRACH.

72. The method according to any one of claims 50 to 71, wherein The cell supports at least one of the following scheduling modes: Same-carrier scheduling mode, wherein the same-carrier scheduling mode is that the DCI on the cell schedules the PDSCH on the cell; A cross-carrier scheduling method, where the cross-carrier scheduling method is that the DCI on the cell schedules the PDSCH and / or PUSCH on the second cell.

73. The method of claim 72, wherein: The cross-carrier scheduling mode includes a first type of cross-carrier scheduling mode and / or a second type of cross-carrier scheduling mode; In the first type of cross-carrier scheduling mode, the cell and the scheduled cell belong to the same cluster, and the scheduled cell is the second cell; In the second type of cross-carrier scheduling mode, the cell and the scheduled carrier belong to different clusters, and the scheduled carrier is the second cell.

74. The method of claim 73, wherein For the first type of cross-carrier scheduling method, The DCI on the cell carries the cell index of the scheduled cell; or, The relationship between the cell and the scheduled cell is configured through RRC signaling.

75. The method of claim 73, wherein For the second type of cross-carrier scheduling method, The DCI on the cell carries the cluster index of the cluster where the scheduled cell is located and the cell index of the scheduled cell, wherein the cell indexes in different clusters are in independent numbering spaces; or The DCI on the cell carries the cell index of the scheduled cell, wherein the cell indexes in different clusters are in the same numbering space; or The relationship between the cell and the scheduled cell is configured through RRC signaling.

76. The method of any one of claims 50 to 75, wherein For a third cell in the at least one cluster, HARQ feedback information of the PDSCH on the third cell is transmitted through a PUCCH on a fourth cell; The fourth cell is configured through RRC signaling; or, The fourth cell is indicated by scheduling the DCI of the third cell.

77. The method of claim 76, wherein The DCI for scheduling the third cell carries the cluster index of the cluster where the fourth cell is located and the cell index of the fourth cell, wherein the cell indexes in different clusters are in independent numbering spaces; or The DCI for scheduling the third cell carries the cell index of the fourth cell, wherein the cell indexes in different clusters are in the same numbering space.

78. The method of any one of claims 50 to 77, wherein The method further comprises: The terminal device receives the first TB on the fifth cell. If the number of retransmissions of the first TB exceeds a first threshold, the terminal device receives the first TB on the sixth cell; and / or, The terminal device sends the second TB on the fifth cell. If the number of retransmissions of the second TB exceeds a second threshold, the terminal device sends the second TB on the sixth cell.

79. The method of claim 78, wherein The first TB on the sixth cell is new transmission data; and / or, The second TB on the sixth cell is new transmission data.

80. The method of claim 79, wherein Before the terminal device receives the first TB on the sixth cell, the method further includes: The terminal device receives a first DCI on the fifth cell, where the first DCI carries at least one of the following: fifth information, where the fifth information is used to schedule the sixth cell to newly transmit the first TB; The sixth information is used to instruct the network device to give up retransmitting the first TB on the fifth cell and / or instruct the terminal device to clear the cache corresponding to the first HARQ process of the fifth cell, where the first HARQ process is the HARQ process corresponding to the first TB on the fifth cell.

81. The method of claim 79, wherein Before the terminal device sends the second TB on the sixth cell, the method further includes: The terminal device receives a second DCI on the fifth cell, where the second DCI carries at least one of the following: Seventh information, where the seventh information is used to schedule the sixth cell to newly transmit the second TB; The eighth information is used to instruct the terminal device to give up retransmitting the second TB on the fifth cell and / or instruct the terminal device to clear the cache corresponding to the second HARQ process of the fifth cell, where the second HARQ process is the HARQ process corresponding to the second TB on the fifth cell.

82. The method according to any one of claims 79 to 81, wherein The sixth cell and the fifth cell correspond to different HARQ entities.

83. The method of claim 78, wherein The first TB on the sixth cell is retransmitted data of the first TB on the fifth cell; and / or, The second TB on the sixth cell is retransmitted data of the second TB on the fifth cell.

84. The method of claim 83, wherein The sixth cell and the fifth cell correspond to the same HARQ entity.

85. The method of claim 83 or 84, wherein Each cell group in the at least one cluster corresponds to a HARQ entity; The sixth cell and the fifth cell belong to the same cell group.

86. The method of claim 85, wherein The method further comprises: The terminal device receives fourth configuration information sent by the network device, where the fourth configuration information is used to configure one or more cell groups, where each cell group corresponds to a HARQ entity.

87. The method of claim 83, wherein The sixth cell and the fifth cell correspond to different HARQ entities.

88. The method of claim 87, wherein The method further comprises: The terminal device receives a third DCI on the fifth cell, where the third DCI carries at least one of the following: Ninth information, where the ninth information is used to schedule the six cells to retransmit the first TB; Tenth information, where the tenth information is used to indicate a HARQ process identifier corresponding to the first TB on the fifth cell; The eleventh information is used to indicate the HARQ process identifier corresponding to the first TB in the six cells.

89. The method according to any one of claims 50 to 88, wherein The method further comprises: The terminal device sends a first message on the seventh cell and receives a second message on the eighth cell, where the first message and the second message are associated messages in a random access process.

90. The method of claim 89, wherein The seventh cell is a cell in the at least one cluster configured with PRACH resources and / or random access configuration information.

91. The method according to claim 89 or 90, wherein The cell index or cell number of the eighth cell is determined based on a random access series and a second parameter, where the second parameter is the number of cells configured by the first configuration information; or The cell index or cell number of the eighth cell is determined based on a random access sequence and a fifth parameter, where the fifth parameter is the number of cells in a first cell list, where the first cell list is a cell list configured by the network device for receiving the second message; or, The eighth cell is a cell configured by the network device and associated with the seventh cell; or, The eighth cell is one of at least one cell associated with the random access sequence and / or PRACH resources.

92. The method according to any one of claims 89 to 91, wherein The receiving the second message on the eighth cell includes: The terminal device uses RA-RNTI to receive a second message on the eighth cell, and the RA-RNTI is calculated based on the sixth parameter and / or the seventh parameter. The value of the sixth parameter is configured by the network device or is the carrier index of the uplink carrier in the eighth cell or is the carrier index of the uplink carrier in the eighth cell plus the first offset. The seventh parameter is configured by the network device or is the cluster index of the cluster where the eighth cell is located.

93. The method according to any one of claims 1 to 92, wherein The correspondence between the at least one cluster and the MAC entity includes at least one of the following: One cluster corresponds to one MAC entity; Multiple clusters correspond to one MAC entity.

94. The method of claim 93, wherein The MAC entity corresponds to one or more HARQ entities, and each HARQ entity corresponds to a carrier group or cell group.

95. The method according to claim 93 or 94, wherein The MAC entity also includes an upper layer entity, and the upper layer entity includes at least one of the following: an RLC entity, a PDCP entity, an SDAP entity, an RRC entity, and a NAS entity; wherein, The MAC entity and the upper layer entity are deployed in the cloud; or, The MAC entity is deployed on the access network side, and the upper layer entity is deployed on the cloud side; or, The MAC entity and the RLC entity are deployed on the access network side, and entities in the upper layer except the RLC entity are deployed on the cloud.

96. The method of claim 95, wherein The RRC entity is associated with one or more sites; or, The RRC entity is associated with an area, which is an area defined by one or more cell lists or an area governed by a cloud platform.

97. The method according to any one of claims 1 to 96, wherein The method further comprises: The terminal device receives first RRC signaling, where the first RRC signaling is used to configure updated system broadcast information.

98. The method of claim 97, wherein The method further comprises: The terminal device does not monitor P-RNTI-scrambled DCI and SI-RNTI-scrambled DCI. The P-RNTI-scrambled DCI is used to schedule paging messages, the paging messages are used to carry system broadcast change indications, and the SI-RNTI-scrambled DCI is used to schedule updated system broadcast information.

99. The method according to any one of claims 1 to 96, wherein The method further comprises: The terminal device receives a second RRC signaling, where the second RRC signaling is used to configure at least one of the following: a system broadcast change indication, a target carrier or target cell where a system broadcast information change occurs, a target SIB received by the terminal device, a scheduling period of the target SIB, and a time range for the terminal device to receive the target SIB scheduling information; The terminal device monitors the SI-RNTI-scrambled DCI based on the second RRC signaling, where the SI-RNTI-scrambled DCI is used to schedule updated system broadcast information.

100. The method of claim 99, wherein The method further comprises: The terminal device does not monitor the P-RNTI-scrambled DCI, and the P-RNTI-scrambled DCI is used to schedule paging messages, and the paging messages are used to carry system broadcast change indications.

101. The method according to any one of claims 1 to 96, wherein The method further comprises: The terminal device monitors the P-RNTI-scrambled DCI on the target carrier or target cell, the P-RNTI-scrambled DCI is used to schedule a paging message, and the P-RNTI-scrambled DCI and / or the paging message is used to notify at least one of the following: a system broadcast change indication, a target carrier or target cell where a system broadcast information change occurs, a target SIB received by the terminal device, a scheduling period of the target SIB, and a time range for the terminal device to receive the target SIB scheduling information; The terminal device monitors the SI-RNTI-scrambled DCI based on the P-RNTI-scrambled DCI and / or the paging message, where the SI-RNTI-scrambled DCI is used to schedule updated system broadcast information.

102. The method according to claim 101, wherein The method further comprises: The terminal device receives a third RRC signaling, where the third RRC signaling is used to configure: The carrier index of the target carrier, wherein the carrier indexes in different clusters are in the same numbering space; or The cluster index of the cluster where the target carrier is located and the carrier index of the target carrier, wherein the carrier indexes in different clusters are in independent numbering spaces; or The cell index of the target cell, wherein the cell indexes in different clusters are in the same numbering space; or The cluster index of the cluster where the target cell is located and the cell index of the target cell, wherein the cell indexes in different clusters are in independent numbering spaces.

103. The method according to claim 101, wherein The method further comprises: The terminal device determines the carrier index or carrier number of the target carrier based on a first parameter and a second parameter, wherein the first parameter is an identifier of the terminal device and the second parameter is the number of downlink carriers configured by the first configuration information, wherein the carrier indexes in different clusters are in the same numbering space; or The terminal device determines the carrier index or carrier number of the target carrier based on the first parameter and the third parameter, and determines the cluster index or cluster number of the cluster where the target carrier is located based on the first parameter and the fourth parameter, wherein the first parameter is an identifier of the terminal device, the third parameter is the number of downlink carriers in the cluster where the target carrier is located, and the fourth parameter is the number of downlink clusters configured by the first configuration information, wherein the carrier indexes in different clusters are in independent numbering spaces; or, The terminal device determines a cell index or cell number of the target cell based on a first parameter and a second parameter, where the first parameter is an identifier of the terminal device and the second parameter is the number of cells configured by the first configuration information, wherein the cell indexes in different clusters are in the same numbering space; or The terminal device determines the cell index or cell number of the target cell based on the first parameter and the third parameter, and determines the cluster index or cluster number of the cluster where the target cell is located based on the first parameter and the fourth parameter, wherein the first parameter is the identifier of the terminal device, the third parameter is the number of cells in the cluster where the target cell is located, and the fourth parameter is the number of clusters configured by the first configuration information, wherein the cell indexes in different clusters are in independent numbering spaces.

104. The method according to any one of claims 1 to 103, wherein The method further comprises: For a cluster configured by the first configuration information, if radio link failure occurs in all carriers or cells in the cluster, the terminal device sends uplink RRC signaling to the network device, and the uplink RRC signaling is used to notify the network device that the radio link failure occurs in the cluster.

105. The method of claim 104, wherein The method further comprises: The terminal device receives fifth configuration information sent by the network device, and the fifth configuration information is used to configure that when a wireless link failure occurs in the target cluster, the terminal device is triggered to notify the target cluster of the wireless link failure through uplink RRC signaling.

106. The method according to any one of claims 1 to 105, wherein The method further comprises: If radio link failure occurs in all clusters configured by the first configuration information, the terminal device initiates an RRC connection reconstruction process.

107. The method according to any one of claims 1 to 106, wherein The at least one cluster belongs to one or more sites.

108. The method according to any one of claims 1 to 107, wherein The terminal device receives first configuration information sent by the network device, including: The terminal device receives first configuration information sent by a first site, where the first configuration information includes configuration information of a cluster on the first site side and configuration information of a cluster on the at least one second site side; wherein the configuration information of the cluster on the second site side is sent to the first site by the second site through a container.

109. The method of claim 108, wherein The method further comprises: The first site sends a cluster add request message to the second site; The first site receives a cluster addition response message sent by the second site, where the cluster addition response message carries a container, and the container is used to carry configuration information of the cluster on the second site side.

110. The method of claim 109, wherein: The cluster add request message carries at least one of the following: fifth indication information, where the fifth indication information is used to indicate a bearer configuration that the second site needs to provide; Sixth indication information, where the sixth indication information is used to indicate a protocol stack entity that the second site needs to provide.

111. A carrier aggregation method, the method comprising: The network device sends first configuration information to the terminal device, where the first configuration information is used to configure at least one cluster, each of the at least one cluster including at least one carrier or at least one cell.

112. The method according to claim 111, wherein The at least one cluster includes at least one downlink cluster and / or at least one uplink cluster, each downlink cluster includes at least one downlink carrier, and each uplink cluster includes at least one uplink carrier.

113. The method according to claim 111, wherein Each of the at least one cluster includes at least one cell.

114. A carrier aggregation apparatus, applied to a terminal device, the apparatus comprising: The receiving unit is configured to receive first configuration information sent by a network device, where the first configuration information is used to configure at least one cluster, where each cluster in the at least one cluster includes at least one carrier or at least one cell.

115. A carrier aggregation apparatus, applied to a network device, comprising: A sending unit is used to send first configuration information to a terminal device, where the first configuration information is used to configure at least one cluster, each of the at least one cluster including at least one carrier or at least one cell.

116. A terminal device comprising: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory to execute the method according to any one of claims 1 to 110.

117. A network device comprising: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory to execute the method as claimed in any one of claims 111 to 113.

118. A chip comprising: A processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes the method according to any one of claims 1 to 110, or the method according to any one of claims 111 to 113.

119. A computer-readable storage medium for storing a computer program, wherein the computer program causes a computer to execute the method according to any one of claims 1 to 110, or the method according to any one of claims 111 to 113.

120. A computer program product comprising computer program instructions, the computer program instructions causing a computer to perform the method of any one of claims 1 to 110, or any one of claims 111 to 113.

121. A computer program, the computer program causing a computer to perform the method of any one of claims 1 to 110, or any one of claims 111 to 113.

Images