Communication methods, devices and systems
By establishing synchronization information association between primary and secondary carriers and multi-carrier scheduling in carrier aggregation scenarios, the problem of communication overhead between terminal devices and network devices is solved, enabling rapid activation of secondary cells and improving communication efficiency.
Patent Information
- Application Number
- CN202211661802.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2020-04-30
- Publication Date
- 2026-11-17
- Estimated Expiration
- 2040-04-30
AI Technical Summary
In carrier aggregation scenarios, how can we optimize the communication overhead between terminal devices and network devices to reduce signaling interaction and the time required to activate secondary cells?
By establishing a correlation between synchronization information and CSI values between the downlink primary carrier and secondary carrier, the terminal device can directly activate the secondary cell based on the synchronization information of the primary carrier, reducing channel measurement steps; at the same time, multi-carrier scheduling and group scheduling schemes are adopted to reduce the use of DCI.
It enables rapid activation of secondary cells, reduces communication overhead between terminal devices and network devices, and improves communication efficiency.
Smart Images

Figure CN116156646B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of communication technology, and in particular to communication methods, devices and systems. Background Technology
[0002] The continuous growth of smart terminal users, along with the increasing volume of user services and data throughput, has placed higher demands on communication speeds. To meet the requirements of higher downlink and uplink peak rates, greater transmission bandwidth is needed. Due to the scarcity of continuous spectrum with large bandwidth, carrier aggregation (CA) has been proposed as a solution. Carrier aggregation combines two or more component carriers (CCs) to support greater transmission bandwidth. Specifically, carrier aggregation includes carrier aggregation between different cells under a single base station and carrier aggregation between different cells under different base stations in dual connectivity (DC) scenarios.
[0003] Currently, when configuring multiple cells for a terminal device, how to further optimize the configuration to reduce the communication overhead between the terminal device and network devices is a problem that needs to be solved. Summary of the Invention
[0004] This application provides communication methods, apparatus, and systems to reduce communication overhead between terminal devices and network devices in carrier aggregation scenarios.
[0005] In a first aspect, embodiments of this application provide a communication method, comprising: a network device sending a first signaling message to a terminal device on a downlink primary carrier, the first signaling message including configuration information of a secondary cell, the configuration information of the secondary cell including downlink secondary carrier information, or including downlink secondary carrier information and uplink secondary carrier information; the network device sending a second signaling message to the terminal device, the second signaling message being used by the terminal device to activate the secondary cell; the network device determining, based on a Channel State Information (CSI) report and / or feedback signaling received from the terminal device, that the terminal device has successfully activated the secondary cell, the feedback signaling being used to indicate feedback information of the second signaling message; wherein, the time-frequency domain synchronization information of the downlink primary carrier is the same as the time-frequency domain synchronization information of the downlink secondary carrier, or the difference between the time-frequency domain synchronization information of the downlink primary carrier and the time-frequency domain synchronization information of the downlink secondary carrier is less than a first threshold; the CSI value of the downlink primary carrier is the same as the CSI value of the downlink secondary carrier, or the difference between the CSI value of the downlink primary carrier and the CSI value of the downlink secondary carrier is less than a second threshold.
[0006] Based on the above scheme, since the synchronization information of the downlink secondary carrier is the same as or similar to that of the downlink primary carrier, the terminal device can activate the secondary cell without receiving relevant information from the network device for performing channel measurements. In other words, the terminal device can perform downlink synchronization with the downlink secondary carrier based on the synchronization information of the downlink primary carrier. This scheme reduces the steps required for the network device to activate the secondary cell for the terminal device, and drastically reduces the time for the secondary cell to transition from deactivated to activated state. Therefore, while achieving rapid cell activation, it also reduces the communication overhead between the terminal device and the network device.
[0007] In one possible implementation, the network device determines that the terminal device has successfully activated the secondary cell based on a CSI report and / or feedback signaling received from the terminal device, including: if the network device receives the CSI report from the terminal device and the CSI report is a valid CSI report, then the network device determines that the terminal device has successfully activated the secondary cell; or, the network device determines that the terminal device has successfully activated the secondary cell at a first moment, wherein the time interval between the first moment and receiving the feedback signaling is greater than or equal to a first preset duration; or, the network device determines that the terminal device has successfully activated the secondary cell at a second moment, wherein the time interval between the second moment and receiving the feedback signaling is greater than or equal to a second preset duration.
[0008] In one possible implementation, the first set duration is equal to (the number of time slots in a subframe corresponding to the subcarrier interval + 1) * the duration of a time slot; wherein the subcarrier interval is the subcarrier interval corresponding to the Physical Uplink Control Channel (PUCCH), and the PUCCH is used to carry feedback information of the second signaling.
[0009] In one possible implementation, the second set duration is equal to (the number of time slots in a subframe corresponding to the subcarrier interval + 1) * the duration of a time slot; wherein the subcarrier interval is the subcarrier interval corresponding to the PUCCH, and the PUCCH is used to carry feedback information of the second signaling.
[0010] Secondly, embodiments of this application provide a communication method, comprising: a terminal device receiving a first signaling from a network device on a downlink primary carrier, the first signaling including configuration information of a secondary cell, the configuration information of the secondary cell including downlink secondary carrier information, or including downlink secondary carrier information and uplink secondary carrier information; the terminal device receiving a second signaling from the network device, the second signaling being used to activate the secondary cell for the terminal device; the terminal device sending a Channel State Information (CSI) report and / or feedback signaling to the network device, the feedback signaling being used to indicate feedback information of the second signaling. Wherein, the time-frequency domain synchronization information of the downlink primary carrier is the same as the time-frequency domain synchronization information of the downlink secondary carrier, or the difference between the time-frequency domain synchronization information of the downlink primary carrier and the time-frequency domain synchronization information of the downlink secondary carrier is less than a first threshold; the CSI value of the downlink primary carrier is the same as the CSI value of the downlink secondary carrier, or the difference between the CSI value of the downlink primary carrier and the CSI value of the downlink secondary carrier is less than a second threshold.
[0011] The terminal device can perform downlink synchronization with the downlink secondary carrier based on the time-frequency domain synchronization information of the downlink primary carrier and the configuration information of the downlink secondary carrier.
[0012] Based on the above scheme, since the synchronization information of the downlink secondary carrier is the same as or similar to that of the downlink primary carrier, the terminal device can activate the secondary cell without receiving relevant information from the network device for performing channel measurements. In other words, the terminal device can perform downlink synchronization with the downlink secondary carrier based on the synchronization information of the downlink primary carrier. This scheme reduces the steps required for the network device to activate the secondary cell for the terminal device, and drastically reduces the time for the secondary cell to transition from deactivated to activated state. Therefore, while achieving rapid activation of the cell carrier, it also reduces the communication overhead between the terminal device and the network device.
[0013] Based on the first aspect, or any implementation of the first aspect, or the second aspect, or any implementation of the second aspect:
[0014] In one possible implementation, the first signaling is Media Access Control (MAC) CE signaling, Radio Resource Control (RRC) signaling, or Downlink Control Information (DCI) signaling.
[0015] In one possible implementation, the second signaling is MAC CE signaling, Radio Resource Control (RRC) signaling, or Downlink Control Information (DCI) signaling.
[0016] Thirdly, embodiments of this application provide a communication method, comprising: a network device determining a first downlink control information (DCI), the first DCI being used to schedule M data channels, the M data channels being mapped onto N carriers, the N carriers being used for data transmission of the M data channels, and one of the M data channels being mapped onto at least one of the N carriers, where M is a positive integer and N is an integer greater than 1; the network device sending the first DCI to a terminal device. Based on the above scheme, since one DCI can schedule multiple carriers, compared to one DCI being used to schedule only one carrier, when the same number of carriers need to be scheduled, the method of this application requires fewer DCIs, thereby reducing the signaling overhead between the terminal device and the network device. That is, the multi-carrier scheduling scheme of this application, compared to the single-carrier scheduling scheme, can reduce the signaling overhead between the terminal device and the network device.
[0017] In one possible implementation, the network device determines a second DCI, which is used to schedule K data channels, the K data channels being mapped onto one carrier, and the one carrier being used for data transmission of the K data channels, where K is a positive integer; the network device sends the second DCI to the terminal device; wherein the scrambling identifier corresponding to the first DCI is different from the scrambling identifier corresponding to the second DCI.
[0018] In one possible implementation, the first DCI includes a first identification field, which indicates that the first DCI is used for scheduling the N carriers.
[0019] In one possible implementation, the network device sends Radio Resource Control (RRC) signaling to the terminal device, the RRC signaling being used to instruct the first DCI to be used for scheduling the N carriers.
[0020] Fourthly, embodiments of this application provide a communication method, comprising: a terminal device receiving first downlink control information (DCI) from a network device, the first DCI being used to schedule M data channels, the M data channels being mapped onto N carriers, the N carriers being used for data transmission of the M data channels, one of the M data channels being mapped onto at least one carrier among the N carriers, M being a positive integer and N being an integer greater than 1; the terminal device communicating with the network device on at least two carriers among the N carriers according to the first DCI.
[0021] Based on the above scheme, since one DCI can schedule multiple carriers, compared to one DCI being used to schedule only one carrier, the method of this application requires fewer DCIs when scheduling the same number of carriers, thereby reducing the signaling overhead between the terminal device and the network device. In other words, the multi-carrier scheduling scheme of this application can reduce the signaling overhead between the terminal device and the network device compared to the single-carrier scheduling scheme.
[0022] In one possible implementation, the terminal device receives a second DCI from the network device. The second DCI is used to schedule K data channels, which are mapped onto one carrier. The one carrier is used for data transmission across the K data channels, where K is a positive integer. The terminal device communicates with the network device on the one carrier according to the second DCI. The scrambling identifier corresponding to the first DCI is different from the scrambling identifier corresponding to the second DCI. This method distinguishes between the second DCI used for single-carrier scheduling and the first DCI used for multi-carrier scheduling using different scrambling identifiers, without requiring modification of the DCI, thus simplifying implementation.
[0023] In one possible implementation, the first DCI includes a first identifier field, which indicates that the first DCI is used for scheduling the N carriers. This scheme is simple and flexible to implement by adding a first identifier field to indicate that the first DCI is used for scheduling the N carriers.
[0024] In one possible implementation, the terminal device receives Radio Resource Control (RRC) signaling from the network device. The RRC signaling is used to indicate that the first DCI is used for scheduling the N carriers. This scheme uses RRC signaling to indicate that the first DCI is used for scheduling the N carriers, eliminating the need to add an indication field to the first DCI to indicate that it is used for scheduling the N carriers, thus reducing DCI overhead.
[0025] Based on the third aspect, or any implementation method of the third aspect, or the fourth aspect, or any implementation method of the fourth aspect:
[0026] In one possible implementation, the N carriers include a carrier for transmitting the first DCI and N-1 other carriers, the other N-1 carriers being configured via RRC signaling; or, the N carriers being configured via RRC signaling; or, the first DCI includes N-1 carrier indication fields, the N carriers including a carrier for transmitting the first DCI and N-1 other carriers, the N-1 carrier indication fields being used to indicate the other N-1 carriers; or, the first DCI includes a carrier indication field, the carrier indication field being used to indicate an index of a carrier group, the carrier group including the N carriers, the carrier group being configured via RRC signaling.
[0027] In one possible implementation, the first DCI includes a BWP indication field for indicating N BWPs with the same index on the N carriers; or, the first DCI includes a BWP group indication field for indicating the index of a BWP group, the BWP group including at least one BWP on each of the N carriers; or, the first DCI includes N BWP indication fields for indicating N BWPs on the N carriers.
[0028] Fifthly, embodiments of this application provide a communication device, which may be a network device or a chip for a network device. The device has the function of implementing the method of the first aspect, or the method of the third aspect, or various implementations of the first aspect, or various implementations of the third aspect. This function can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-described functions.
[0029] Sixthly, embodiments of this application provide a communication device, which can be a terminal device or a chip for a terminal device. The device has the function of implementing the method of the second aspect, or the method of the fourth aspect, or various implementations of the second aspect, or various implementations of the fourth aspect. This function can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-described functions.
[0030] In a seventh aspect, embodiments of this application provide a communication device, including a processor and a memory; the memory is used to store computer execution instructions, and when the device is running, the processor executes the computer execution instructions stored in the memory to cause the device to perform any of the methods described in the first to fourth aspects and the implementation methods of the first to fourth aspects above.
[0031] Eighthly, embodiments of this application provide a communication device, including a processor and an interface circuit. The processor is configured to communicate with other devices via the interface circuit and execute any of the methods described in the first to fourth aspects and their respective implementations. The processor may include one or more devices.
[0032] Ninthly, embodiments of this application provide a communication device including a processor for connection to a memory, for calling a program stored in the memory to execute any of the methods described in the first to fourth aspects and their respective implementations. The memory may be located within or outside the device. The processor may include one or more processors.
[0033] In a tenth aspect, embodiments of this application also provide a computer-readable storage medium storing instructions that, when executed on a computer, cause a processor to perform any of the methods described in the first to fourth aspects and the implementation methods of the first to fourth aspects.
[0034] Eleventhly, embodiments of this application also provide a computer program product, which includes a computer program that, when the computer program is run, causes any one of the methods in the first to fourth aspects and the implementation methods of the first to fourth aspects to be executed.
[0035] In a twelfth aspect, embodiments of this application also provide a chip system, including: a processor, configured to execute any of the methods described in the first to fourth aspects and the implementation methods of the first to fourth aspects.
[0036] In a thirteenth aspect, embodiments of this application also provide a communication system, including a network device for performing the first aspect or any implementation of the first aspect described above, and a terminal device for performing the second aspect or any implementation of the second aspect described above.
[0037] In a fourteenth aspect, embodiments of this application also provide a communication system, including a network device for performing the third aspect or any implementation of the third aspect described above, and a terminal device for performing the fourth aspect or any implementation of the fourth aspect described above. Attached Figure Description
[0038] Figure 1 This is a schematic diagram of a network architecture applicable to the embodiments of this application;
[0039] Figure 2 This is a schematic diagram of a communication method provided in an embodiment of this application;
[0040] Figure 3 This is a schematic diagram of a communication method provided in an embodiment of this application;
[0041] Figure 4 This is a schematic diagram of another communication method provided in an embodiment of this application;
[0042] Figure 5 A schematic diagram of a communication device provided in an embodiment of this application;
[0043] Figure 6 A schematic diagram of another communication device provided in the embodiments of this application;
[0044] Figure 7 A schematic diagram of a terminal device provided in an embodiment of this application;
[0045] Figure 8 This is a schematic diagram of a network device provided in an embodiment of this application. Detailed Implementation
[0046] The technical solutions provided in this application can be applied to various communication systems, such as 5G communication systems, future evolution systems, or multiple communication convergence systems. The technical solutions provided in this application can be applied to various application scenarios, such as machine-to-machine (M2M), macro-micro communication, enhanced mobile broadband (eMBB), ultra-reliable and low-latency communication (uRLLC), and massive machine-type communication (mMTC). These scenarios may include, but are not limited to, communication between communication devices, communication between network devices, and communication between network devices. The following description uses the communication scenario between network devices and terminals as an example.
[0047] Furthermore, the network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.
[0048] like Figure 1 The diagram shown illustrates a network architecture applicable to an embodiment of this application, including a terminal device and a network device. The terminal device communicates with the network device via a wireless interface.
[0049] A terminal device is a device with wireless transceiver capabilities that can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; it can also be deployed on water (such as on ships); and it can be deployed in the air (such as on airplanes, balloons, and satellites). Terminal devices can include mobile phones, tablets, computers with wireless transceiver capabilities, virtual reality (VR) terminals, augmented reality (AR) terminals, wireless terminals in industrial control, wireless terminals in self-driving vehicles, wireless terminals in remote medical care, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, user equipment (UE), etc.
[0050] Network equipment is a device that provides wireless communication functions for terminal devices. Network equipment includes, but is not limited to: next-generation base stations (g node B, gNB) in the 5th generation (5G), evolved node B (eNB), radio network controller (RNC), node B (NB), base station controller (BSC), base transceiver station (BTS), home base station (e.g., home evolved node B, or home node B, HNB), baseband unit (BBU), transmitting and receiving point (TRP), transmitting point (TP), mobile switching center, etc.
[0051] When deploying 5G standalone, the logical architecture of network equipment can adopt a separation mode of centralized unit (CU) and distributed unit (DU). Based on the configuration of protocol stack functions, the CU-DU logical architecture can be divided into two types: CU-DU separation architecture and CU-DU converged architecture. For the CU-DU separation architecture, the functions of the protocol stack can be dynamically configured and divided, with some functions implemented in the CU and the remaining functions in the DU. To meet the needs of different division options, it is necessary to support both ideal and non-ideal transmission networks. The interface between the CU and DU should comply with the requirements of the 3rd Generation Partnership Project (3GPP) specifications. For the CU-DU converged architecture, the logical functions of the CU and DU are integrated into the same network device to realize all the functions of the protocol stack.
[0052] The continuous growth of smart terminal users, along with the increasing volume of user services and data throughput, has placed higher demands on communication speeds. To meet the requirements of higher downlink and uplink peak rates, greater transmission bandwidth is needed. Due to the scarcity of continuous spectrum with large bandwidth, carrier aggregation (CA) has been proposed as a solution. Carrier aggregation combines two or more component carriers (CCs) together to support greater transmission bandwidth.
[0053] In single-link scenarios, carrier aggregation configures one cell in the network device as the primary cell for the terminal device, and other cells in the network device as secondary cells for the terminal device. The primary cell (Pcell) is the cell established during the initial connection of the terminal device, the cell used for Radio Resource Control (RRC) connection reconstruction, or the primary cell designated during handover. The primary cell is responsible for RRC communication with the terminal device. The carrier element corresponding to the primary cell is called the Primary Component Carrier (PCC). Specifically, the downlink carrier of the primary cell is called the Downlink Primary Carrier (DL PCC), and the uplink carrier is called the Uplink Primary Carrier (UL PCC). Secondary cells (Scell) are added during RRC reconfiguration to provide additional radio resources; there is no RRC communication between the secondary cell and the terminal device. The carrier element corresponding to the secondary cell is called the Secondary Component Carrier (SCC). The downlink carrier of the secondary cell is called the downlink secondary carrier (DLSCC), and the uplink carrier of the secondary cell is called the uplink secondary carrier (UL SCC).
[0054] Carrier aggregation in dual-link scenarios involves configuring one cell from the primary network device as the primary cell of the terminal device (i.e., the primary cell in the Master Cell Group (MCG)), configuring one cell from the secondary network device as the Primary Secondary Cell (Primary Scell) of the terminal device (i.e., the primary cell in the Secondary Cell Group (SCG)), and configuring other cells under the primary or secondary network devices, excluding the primary and primary / secondary cells, as secondary cells of the terminal device. The primary cell is the cell established during the initial connection of the terminal device, the cell used for RRC connection reconstruction, or the primary cell designated during handover. The primary cell is responsible for RRC communication with the terminal device. The carrier element corresponding to the primary cell is called the primary carrier element. The downlink carrier of the primary cell is called the downlink primary carrier (DL PCC), and the uplink carrier is called the uplink primary carrier (UL PCC). The primary and secondary cells are added during RRC reconfiguration to provide additional radio resources; there is no RRC communication between the primary and secondary cells and the terminal device. The carrier units corresponding to the primary and secondary cells are called secondary carrier units. Among them, the downlink carrier of the primary and secondary cells is called the downlink secondary carrier (DL SCC), and the uplink carrier of the primary and secondary cells is called the uplink secondary carrier (UL SCC).
[0055] The primary cell is determined during connection establishment, while the secondary cell is added / modified / released via RRC connection reconfiguration messages after initial access is completed.
[0056] The relationship between a cell and a carrier is as follows: A cell has no physical entity; it is merely a logical concept. It is the smallest logical unit in a mobile communication network that provides users with a complete set of services (calling, being called, mobility, internet access, etc.). A carrier is a radio signal (electromagnetic wave) with a specific frequency, bandwidth, and standard emitted by network equipment. It is the main component used to carry information. A cell can have one or more downlink carriers and / or one or more uplink carriers. A single cell can include one downlink carrier, one uplink carrier, and one supplementary uplink (SUL) carrier, where an SUL carrier refers to a carrier whose uplink resources are used solely for transmission within the current communication standard.
[0057] Currently, when configuring multiple cells for a terminal device, how to further optimize the configuration to reduce the communication overhead between the terminal device and network devices is a problem that needs to be solved.
[0058] This application's embodiments optimize communication between terminal devices and network devices in carrier aggregation scenarios from three aspects, thereby reducing communication overhead between terminal devices and network devices.
[0059] The first aspect involves simplifying the activation process and reducing signaling interactions during the process of network equipment instructing terminal equipment to activate secondary cells. This achieves rapid activation of secondary cells while reducing communication overhead between terminal equipment and network equipment. A secondary cell includes downlink carriers, or downlink and uplink carriers, or uplink carriers. When a cell is activated, all uplink and downlink carriers within that cell are also activated. Optionally, the downlink and uplink carriers in a secondary cell can be activated independently.
[0060] Secondly, when scheduling carriers using Downlink Control Information (DCI), this application enables a single DCI to schedule multiple carriers (referred to as carrier joint scheduling or multi-carrier scheduling). Compared to a single DCI scheduling only one carrier (referred to as single-carrier scheduling), this application's embodiments improve DCI scheduling efficiency. When scheduling the same number of carriers, this application's embodiments require fewer DCIs, thereby reducing communication overhead between the terminal device and the network device.
[0061] The third aspect is to group multiple carriers into multiple carrier groups, and the carriers in each carrier group satisfy certain characteristics, thereby reducing the communication overhead between terminal devices and network devices.
[0062] It should be noted that in the embodiments of this application, the above three aspects are independent of each other. That is, only the first aspect, or the second aspect, or the third aspect can be implemented, or any two aspects can be combined (such as implementing the fast activation scheme of the first aspect and the joint scheduling scheme of the second aspect), or the three aspects can be combined.
[0063] The solutions for the above three aspects will be explained separately below.
[0064] The first aspect of the solution (i.e., quick activation) will be explained below.
[0065] like Figure 2 As shown, this is a communication method provided in an embodiment of the present application, which is used by a network device to configure a carrier for a terminal device.
[0066] The method includes the following steps:
[0067] Step 201: The terminal device receives the synchronization signal / broadcast channel block (SS / PBCH Block, SSB) and system message sent by the network device on the downlink primary carrier.
[0068] The terminal device achieves downlink synchronization with the downlink primary carrier based on the SSB. The system message includes information such as the primary carrier configuration.
[0069] Step 202: The terminal device sends the Physical Random Access Channel (PRACH) to the network device to achieve uplink synchronization with the uplink primary carrier.
[0070] Through steps 201 and 202, the terminal device achieves access to the main carrier.
[0071] Step 203: The terminal device receives RRC signaling sent by the network device on the downlink primary carrier. This RRC signaling configures the configuration information of the terminal device's secondary cell. The configuration information of the secondary cell includes downlink secondary carrier information, or includes both downlink secondary carrier information and uplink secondary carrier information. A secondary cell contains at least one downlink carrier and K uplink carriers, where K is an integer greater than or equal to zero.
[0072] Step 204: The terminal device receives the medium access control element (MAC CE) signaling sent by the network device on the downlink primary carrier, which is used to activate the secondary cell.
[0073] Before the secondary cell is activated, it is in a deactivated state.
[0074] Step 205: The terminal device sends a feedback signaling message to the network device to indicate the feedback information of the MAC CE signaling message.
[0075] Step 206: The terminal device receives the SSB sent by the network device on the downlink secondary carrier and performs downlink synchronization with the downlink secondary carrier.
[0076] Step 207: The terminal device receives the Channel Status Information Reference Signal (CSI-RS) sent by the network device on the downlink secondary carrier.
[0077] Step 208: The terminal device performs channel measurements according to CSI-RS, obtains a Channel Status Information (CSI) report, and reports the CSI report to the network device.
[0078] The CSI report includes, but is not limited to, one or more of the following information: Channel Quality Indicator (CQI), Precoding Matrix Indicator (PMI), Rank Indicator (RI), Delay Information, Angle Information, and Beam Information.
[0079] Step 209: If the network device receives a valid CSI report, it is confirmed that the terminal device has successfully activated the secondary cell.
[0080] Step 210: The terminal device sends a PRACH to the network device on the uplink secondary carrier.
[0081] This step is optional.
[0082] Through steps 201 to 210 above, this application embodiment provides a scheme for activating secondary cells.
[0083] like Figure 3 The diagram illustrates a communication method provided in an embodiment of this application, which is different from... Figure 2 In a corresponding embodiment, the secondary cell can be activated quickly, thereby reducing the communication overhead between the terminal device and the network device. That is, the... Figure 3 The corresponding secondary cell activation scheme in the embodiment is for Figure 2 An improvement to the secondary cell activation scheme in the corresponding embodiment.
[0084] The method includes the following steps:
[0085] Steps 301 to 302 are the same as steps 201 to 202 above, and can be referred to the foregoing description.
[0086] Step 303: The terminal device receives a first signaling message (such as MAC CE signaling, RRC signaling, or DCI signaling) sent by the network device on the downlink primary carrier. The first signaling message configures the secondary cell of the terminal device, that is, the first signaling message contains the configuration information of the secondary cell.
[0087] The configuration information of the secondary cell includes downlink secondary carrier information, or includes both downlink secondary carrier information and uplink secondary carrier information.
[0088] Step 304: The terminal device receives a second signaling message (such as MAC CE signaling, RRC signaling, or DCI signaling) sent by the network device on the downlink primary carrier. The second signaling message is used by the terminal device to activate the secondary cell.
[0089] Before the secondary cell is activated, it is in a deactivated state.
[0090] Step 305: The terminal device sends a feedback signaling message to the network device to indicate the feedback information of the second signaling message.
[0091] This step is optional.
[0092] Step 306: The terminal device sends a CSI report to the network device.
[0093] This step is optional.
[0094] Steps 305 and 306 above can be performed by executing only one of them, or by executing both of them.
[0095] Step 307: The network device determines that the terminal device has successfully activated the secondary cell based on the received CSI report and / or feedback signaling.
[0096] As one implementation method, the time-domain synchronization information of the downlink primary carrier is the same as the time-domain synchronization information of the downlink secondary carrier, and / or the frequency-domain synchronization information of the downlink primary carrier is the same as the frequency-domain synchronization information of the downlink secondary carrier. Alternatively, the difference between the time-domain synchronization information of the downlink primary carrier and the time-domain synchronization information of the downlink secondary carrier is less than a preset threshold, and / or the difference between the frequency-domain synchronization information of the downlink primary carrier and the frequency-domain synchronization information of the downlink secondary carrier is less than a preset threshold. Furthermore, the CSI value of the downlink primary carrier is the same as the CSI value of the downlink secondary carrier, or the difference between the CSI value of the downlink primary carrier and the CSI value of the downlink secondary carrier is less than a preset threshold.
[0097] As another implementation method, the time-domain synchronization information of the downlink secondary carrier (which may be referred to as the first downlink secondary carrier) configured in step 303 above is the same as the time-domain synchronization information of the downlink secondary carrier (which may be referred to as the second downlink secondary carrier) in a secondary cell indicated by a network device, and / or the frequency-domain synchronization information of the first downlink secondary carrier is the same as the frequency-domain synchronization information of the second downlink secondary carrier. Alternatively, the difference between the time-domain synchronization information of the first downlink secondary carrier and the time-domain synchronization information of the second downlink secondary carrier is less than a preset threshold, and / or the difference between the frequency-domain synchronization information of the first downlink secondary carrier and the frequency-domain synchronization information of the second downlink secondary carrier is less than a preset threshold. Furthermore, the CSI value of the first downlink secondary carrier is the same as the CSI value of the second downlink secondary carrier, or the difference between the CSI value of the first downlink secondary carrier and the CSI value of the second downlink secondary carrier is less than a preset threshold.
[0098] Optionally, the second signaling may carry at least one of a cell index, an uplink carrier index, and a downlink carrier index.
[0099] Optionally, network devices configure the correlation between different carriers or the correlation between reference signals on different carriers in the secondary cell configuration, hereinafter referred to as QCL (Quas i co-location)-X. For example, if the CSI-RS on the downlink secondary carrier and the CSI-RS on the downlink primary carrier satisfy QCL-X, then the CSI value of the downlink primary carrier is the same as the CSI value of the downlink secondary carrier, or the difference between the CSI value of the downlink primary carrier and the CSI value of the downlink secondary carrier is less than a preset threshold. If the SSB on the downlink secondary carrier and the SSB on the primary carrier satisfy QCL-X, then the time-domain synchronization information of the downlink primary carrier is the same as the time-domain synchronization information of the downlink secondary carrier, and / or the frequency-domain synchronization information of the downlink primary carrier is the same as the frequency-domain synchronization information of the downlink secondary carrier. Alternatively, the difference between the time-domain synchronization information of the downlink primary carrier and the time-domain synchronization information of the downlink secondary carrier is less than a preset threshold, and / or the difference between the frequency-domain synchronization information of the downlink primary carrier and the frequency-domain synchronization information of the downlink secondary carrier is less than a preset threshold.
[0100] For example, the downlink secondary carrier and the downlink primary carrier satisfy the QCL-X relationship, and the time-domain synchronization information of the downlink primary carrier is the same as that of the downlink secondary carrier, and / or the frequency-domain synchronization information of the downlink primary carrier is the same as that of the downlink secondary carrier. Alternatively, the difference between the time-domain synchronization information of the downlink primary carrier and the time-domain synchronization information of the downlink secondary carrier is less than a preset threshold, and / or the difference between the frequency-domain synchronization information of the downlink primary carrier and the frequency-domain synchronization information of the downlink secondary carrier is less than a preset threshold. Furthermore, the CSI value of the downlink primary carrier is the same as that of the downlink secondary carrier, or the difference between the CSI value of the downlink primary carrier and the CSI value of the downlink secondary carrier is less than a preset threshold.
[0101] For example, the relationship between the downlink secondary carrier and a carrier QCL-X indicated by a network device.
[0102] Based on the above scheme, since the synchronization information of the downlink secondary carrier is the same as or similar to the synchronization information of the downlink primary carrier (or the downlink secondary carrier in a secondary cell indicated by a network device), the terminal device can activate the secondary cell without receiving relevant information from the network device for performing channel measurements. That is, the terminal device can perform downlink synchronization with the downlink secondary carrier based on the synchronization information of the downlink primary carrier (or the downlink secondary carrier in a secondary cell indicated by a network device) and the configuration information of the secondary cell. Compared to... Figure 2 The secondary cell activation scheme in the corresponding embodiment can reduce the number of steps required for the network device to activate the secondary cell for the terminal device (at least reduce the number of steps required for the network device to activate the secondary cell). Figure 2 In the corresponding embodiments, steps 206 and 207 are implemented, and the time for the secondary cell to go from deactivated to activated is greatly reduced, thereby achieving rapid activation of the secondary cell while also reducing the communication overhead between the terminal device and the network device.
[0103] As one implementation method, step 307 above can be implemented in ways including but not limited to the following three methods:
[0104] Method 1: If the network device receives a CSI report from the terminal device and the CSI report is a valid CSI report, then the terminal device has successfully activated the secondary cell.
[0105] The definition of a valid CSI report can be: the information in the CSI report meets predefined conditions, such as the CQI value not being 0.
[0106] Based on this implementation method, step 306 above needs to be executed, but step 305 above can be executed or not.
[0107] When a network device receives a valid CSI report from a terminal device, it determines that the terminal device has successfully activated the secondary cell. Specifically, the terminal device performs downlink synchronization with the downlink secondary carrier based on the synchronization information of the downlink primary carrier or the downlink secondary carrier in a secondary cell indicated by a network device.
[0108] Method 2: The network device determines that the terminal device has successfully activated the secondary cell at the first moment, and the time interval between the first moment and receiving the feedback signaling is greater than or equal to the first set duration.
[0109] Based on this implementation method, step 305 above needs to be executed, but step 306 above can be executed or not.
[0110] For example, if a network device receives feedback signaling at time T1, it determines that the terminal device has successfully activated the secondary cell at time T2 (also known as the first time). The difference between T2 and T1 is greater than or equal to a first preset duration. Alternatively, it can be understood that the terminal device has successfully activated the secondary cell at least after receiving feedback signaling for at least the first preset duration.
[0111] Optionally, the first set duration is equal to (the number of time slots in a subframe corresponding to the subcarrier interval + 1) * the duration of a time slot, wherein the subcarrier interval is the subcarrier interval corresponding to the Physical Uplink Shared Channel (PUCCH), and the PUCCH is used to carry the feedback information of the second signaling.
[0112] Optionally, the first set duration is associated with the subcarrier spacing of the first active bandwidth portion in the downlink secondary carrier. For example, the first set duration is 5ms for 15kHz and 4ms for 30kHz. The first active bandwidth portion is configured by higher layers.
[0113] Method 3: If the network device receives a valid CSI report at the second moment, it is determined that the terminal device has successfully activated the secondary cell. The time interval between the second moment and receiving the feedback signaling is greater than or equal to the second set duration.
[0114] Based on this implementation method, steps 305 and 306 above need to be executed.
[0115] For example, if a network device receives feedback signaling at time T3 and a valid CSI report at time T4 (also known as the second time), and the difference between T4 and T3 is greater than or equal to a second preset duration, then the network device determines that the terminal device has successfully activated the secondary cell. Alternatively, it can be understood that if the network device receives a valid CSI report at least after receiving feedback signaling for at least the second preset duration, then it determines that the terminal device has successfully activated the secondary cell.
[0116] Optionally, the second set duration is equal to (the number of time slots in a subframe corresponding to the subcarrier interval + 1) * the duration of a time slot, wherein the subcarrier interval is the subcarrier interval corresponding to the PUCCH, and the PUCCH is used to carry the feedback information of the second signaling.
[0117] Optionally, the second set duration is associated with the subcarrier spacing of the first active bandwidth portion in the downlink secondary carrier. For example, the first set duration is 5ms for 15kHz and 4ms for 30kHz. The first active bandwidth portion is configured by higher layers.
[0118] The second aspect of the above scheme (i.e., carrier joint scheduling or multi-carrier scheduling) will be explained below.
[0119] In the first implementation, one DCI is used to schedule one or more data channels (such as PDSCH or PUSCH), each data channel carrying a Transport Block (TB), and each data channel is mapped to one carrier. Therefore, one DCI is used to schedule only one carrier. Alternatively, this can be understood as the DCI in this implementation being used only for single-carrier scheduling.
[0120] In the second implementation method, the embodiments of this application can also achieve joint scheduling and transmission among the active downlink carriers. Specifically, one DCI can schedule M data channels (such as Physical Downlink Shared Channel (PDSCH) or Physical Uplink Shared Channel (PUSCH)), which are mapped to N carriers, where M is a positive integer and N is an integer greater than 1. Therefore, this implementation method can enable one DCI to schedule multiple carriers. Alternatively, it can be understood that the DCI in this implementation method can be used for multi-carrier scheduling or joint carrier scheduling.
[0121] like Figure 4 As shown, this is another communication method provided in an embodiment of this application, which can realize the scheduling of multiple carriers by one DCI. Figure 4 In corresponding embodiments, a DCI can schedule multiple carriers, or a DCI can be used for multi-carrier scheduling, or a DCI can be used for joint carrier scheduling.
[0122] The method includes the following steps:
[0123] Step 401: The network device determines the first DCI.
[0124] The first DCI is used to schedule M data channels, which are mapped onto N carriers. One of the M data channels is mapped onto at least one of the N carriers. M is a positive integer and N is an integer greater than 1.
[0125] In this context, M data channels are mapped onto N carriers, which can also be understood as N carriers being used for data transmission of M data channels.
[0126] Here, "mapping" means that there is a correspondence between M data channels and N carriers. When there is data to be transmitted in the M data channels or some of the M data channels, this data is transmitted through the corresponding N carriers or some of the N carriers. That is, the information on the M data channels can be carried on physical resource blocks on the N carriers.
[0127] Step 402: The network device sends the first DCI to the terminal device. Accordingly, the terminal device can receive the first DCI.
[0128] Step 403: The terminal device communicates with the network device on at least two of the N carriers scheduled by the first DCI, according to the first DCI.
[0129] Based on the above scheme, since one DCI can schedule multiple carriers, compared to one DCI being used to schedule only one carrier, when the same number of carriers need to be scheduled, the method described in this application requires fewer DCIs, thereby reducing the signaling overhead between the terminal device and the network device. In other words, the multi-carrier scheduling scheme of this application can reduce the signaling overhead between the terminal device and the network device compared to the single-carrier scheduling scheme.
[0130] As one implementation method, in the embodiments of this application, the carrier used to transmit DCI that schedules multiple carriers can be predefined, configured through MAC CE signaling, RRC signaling, or DCI signaling, or the downlink carrier for transmitting DCI can be determined by the terminal device through blind detection and receiving joint carrier scheduling DCI.
[0131] As one implementation method, in this embodiment of the application, the maximum number of carriers in a DCI scheduling can be predefined or configured via MAC CE signaling, RRC signaling, or DCI signaling. For example, the maximum number of carriers in a DCI scheduling can be predefined as 2 or 3, etc. Alternatively, the maximum number of carriers in a DCI scheduling can be semi-statically configured to 2 or 3, etc., via RRC signaling. The carriers include uplink carriers or downlink carriers.
[0132] As one implementation method, in this embodiment, the actual number of carriers in a DCI scheduling can be predefined or configured via MAC CE signaling, RRC signaling, or DCI signaling. For example, the predefined actual number of carriers in a DCI scheduling is the same as the maximum number of carriers in that DCI scheduling. Another example is that the actual number of carriers in a DCI scheduling can be semi-statically configured to be 2 or 3 via RRC signaling. The carriers include uplink carriers or downlink carriers.
[0133] Regarding the scheduling method of the aforementioned DCI (such as the first DCI described above), the design of the DCI in this application embodiment is as follows.
[0134] I. Indication Method of DCI Scheduling Mode
[0135] For DCIs of the same size but different formats used for single-carrier scheduling, they can be distinguished by the DCI format identifier field. That is, different information is added to the DCI format identifier field to indicate different DCI formats, but these DCIs are all the same size. As an example, the DCI format may include DCI format 1_1.
[0136] In order to indicate that the DCI is used for multi-carrier scheduling in the embodiments of this application, the following two different methods can be used.
[0137] In the first implementation method, the size of the DCI used for scheduling multiple carriers (which can be called the multi-carrier scheduling DCI or the first DCI) in this application embodiment is the same as the size of the DCI used for single-carrier scheduling (which can also be called the single-carrier scheduling DCI or the second DCI).
[0138] For example, the single-carrier scheduling process is as follows: The network device can also determine a second DCI, which is used to schedule K data channels. These K data channels are mapped onto one carrier, and this one carrier is used for the data transmission of the K data channels, where K is a positive integer. The network device sends the second DCI to the terminal device.
[0139] This implementation method has one approach. Since the DCI used for multi-carrier scheduling and the DCI used for single-carrier scheduling have the same DCI size, in order to distinguish between the DCI used for multi-carrier scheduling and the DCI used for single-carrier scheduling in the embodiments of this application, three different design schemes are given below:
[0140] 1) Use different scrambling identifiers for scrambling.
[0141] As an example, DCI used for single-carrier scheduling uses Cell Radio Network Temporary Identifier (C-RNTI) scrambling, while DCI used for multi-carrier scheduling uses a new RNTI scrambling. Thus, terminal devices can distinguish between single-carrier scheduling and multi-carrier scheduling by using different RNTI scrambling.
[0142] 2) Use an additional 1 bit of information to distinguish whether the DCI is used for single-carrier scheduling or multi-carrier scheduling.
[0143] For example, a first identifier field or a multi-carrier identifier field can be introduced in DCI. A value of 0 in the first identifier field or multi-carrier identifier field indicates single-carrier scheduling, and a value of 1 indicates multi-carrier scheduling. Alternatively, a value of 1 indicates single-carrier scheduling, and a value of 0 indicates multi-carrier scheduling.
[0144] 3) Configure the DCI scheduling mode via RRC signaling.
[0145] For example, a network device sends an RRC signaling message to a terminal device to instruct the first DCI to be used for scheduling N carriers, where N is an integer greater than 1. Alternatively, the RRC signaling message can be understood as instructing the first DCI to be used for multi-carrier scheduling.
[0146] For example, a network device sends an RRC signaling message to a terminal device to instruct the second DCI to be used for scheduling one carrier. Alternatively, the RRC signaling message can be understood as instructing the second DCI to be used for single-carrier scheduling.
[0147] For example, a terminal device defines a joint multi-carrier scheduling capability and reports this capability. If the terminal device supports joint multi-carrier scheduling, the network device can configure whether the terminal device's multi-carrier capability is enabled through higher-layer signaling. If the capability is enabled, the second DCI is used for multi-carrier scheduling; otherwise, if the network device configures the capability to be disabled or not configured, the second DCI is used for single-carrier scheduling.
[0148] In the second implementation method, the size of the DCI used for multi-carrier scheduling (i.e., the first DCI) in this embodiment is different from the size of the DCI used for single-carrier scheduling (i.e., the second DCI). Therefore, the new DCI format does not need the DCI format identifier field. That is, the scheduling mode of the DCI can be directly distinguished by the size of the DCI.
[0149] II. Design of the Carrier Indicator Field in DCI
[0150] In this application embodiment, the design method for the carrier indication field of the DCI (i.e., the first DCI) used for multi-carrier scheduling includes, but is not limited to:
[0151] The following example illustrates how a DCI can schedule N carriers.
[0152] 1) The carrier indication field is not included in DCI.
[0153] For example, the N carriers scheduled in a DCI include the scheduled carrier itself, and the other N-1 carriers are configured to the terminal device via RRC signaling. Alternatively, the N carriers scheduled in a DCI include the carrier used to transmit the DCI and the other N-1 carriers, which are configured to the terminal device via RRC signaling. The scheduling order of the N carriers in the frequency domain (scheduling frequency domain resources) can be clockwise or counterclockwise according to the cell index, or the carrier transmitting the DCI can be at the beginning or end of the scheduling order, with the other carriers ordered clockwise or counterclockwise according to the cell index. Alternatively, the carrier transmitting the DCI can be at the beginning or end of the scheduling order, with the other carriers ordered according to the order configured by the RRC signaling.
[0154] For example, if all N carriers scheduled by DCI are configured in RRC signaling, then the scheduling order of these N carriers in the frequency domain can be sorted clockwise or counterclockwise according to the cell index, or sorted according to the order configured in the RRC signaling.
[0155] 2) DCI includes N-1 carrier indication fields. The N carriers scheduled by DCI include the carrier used to transmit DCI and the other N-1 carriers, which are indicated by the N-1 carrier indication fields.
[0156] Alternatively, it can be understood that the N-1 carrier indication fields in the DCI indicate N-1 carriers out of the N carriers scheduled by the DCI. Each carrier indication field indicates one carrier, and the other carrier among the N carriers scheduled by the DCI is the carrier that transmits the DCI signal. The scheduling order of the N carriers in the frequency domain (scheduling frequency domain resources) can be clockwise or counterclockwise according to the cell index, or the carrier transmitting the DCI can be at the beginning or end of the scheduling order, with the other carriers ordered clockwise or counterclockwise according to the cell index. Alternatively, the carrier transmitting the DCI can be at the beginning or end of the scheduling order, with the other carriers ordered according to the DCI signaling configuration order.
[0157] 3) The DCI includes a carrier indication field, which is used to indicate the index of a carrier group rather than a single carrier. This carrier group is configured via RRC signaling and includes N carriers.
[0158] That is, the carrier indication field of the DCI indicates a carrier group containing N carriers, thereby achieving the purpose of indicating N carriers. The scheduling order of the N carriers in the frequency domain can be sorted clockwise or counterclockwise according to the cell index or according to the order of RRC signaling configuration.
[0159] Optionally, for the scheduling of the uplink data channel, the N carriers cannot be carriers transmitting DCI, therefore all N carriers need to have explicit indications.
[0160] III. Design of the Bandwidth Part Indicator Field in DCI
[0161] In this application embodiment, the design method for the BWP indication field of the DCI (i.e., the first DCI) used for multi-carrier scheduling includes, but is not limited to:
[0162] 1) The DCI includes a BWP indicator field, and the BWP index of all scheduled carriers is the same, that is, the active BWP index of N carriers scheduled by a DCI is the same.
[0163] In one implementation, the number of BWPs configured on N carriers of a DCI schedule is the same.
[0164] In another implementation, the BWPs configured on the N carriers of a DCI schedule are completely identical. That is, not only is the number of BWPs configured on each carrier the same, but other configurations (such as BWP size, subcarrier spacing, etc.) are also the same.
[0165] As one implementation method, the size of the BWP indicator field in a DCI is determined based on the minimum number of BWPs configured among N scheduled carriers.
[0166] For example, the first DCI schedules two downlink PDSCHs, mapped to two downlink carriers C1 and C2. Downlink BWP1 and BWP2 are configured on C1 and C2, respectively. The DCI indicates BWP index 2. Therefore, the active downlink BWP on both C1 and C2 is BWP2. The first PDSCH is mapped to BWP2 on C1, and the second PDSCH is mapped to BWP2 on C2. As another example, the first DCI schedules one downlink PDSCH, mapped to two downlink carriers C3 and C4. Downlink BWP1 and BWP2 are configured on C3 and C4, respectively. The DCI indicates BWP index 1. Therefore, the active downlink BWP on both C3 and C4 is BWP1, and the PDSCH is mapped to BWP1 on both C3 and C4.
[0167] 2) The DCI includes a BWP group indicator field, which indicates the index of a BWP group, rather than the index of a single BWP.
[0168] The BWP group can be configured via RRC signaling. The BWP group includes at least one BWP in each scheduled carrier, and the number of BWPs in a carrier is less than or equal to the maximum number of active BWPs.
[0169] For example, the first DCI schedules two downlink PDSCHs, mapped to two downlink carriers C1 and C2. Downlink BWP1 and BWP2 are configured on C1 and C2, respectively. The network device configures BWP group 0 {C1 BWP1, C2 BWP1}, BWP group 1 {C1 BWP1, C2 BWP2}, and BWP group 2 {C1 BWP2, C2 BWP1} via RRC signaling. The DCI indicates BWP group index 0. Therefore, the active downlink BWP on C1 and C2 is BWP1. The first PDSCH is mapped to BWP1 on C1, and the second PDSCH is mapped to BWP1 on C2.
[0170] 3) The DCI includes N BWP indication fields, each of which is used to indicate a BWP on a carrier.
[0171] 4) The DCI does not include the BWP indication field. The terminal device believes that the PDSCH is mapped to the currently active BWP. That is, the DCI does not support dynamic switching of BWP. The network device can switch BWP through existing single-carrier scheduling signaling or RRC signaling.
[0172] 5) The DCI includes a BWP indication field, which is used to indicate the active BWP on the primary or secondary carrier. The other carrier uses the currently active BWP. This method is applicable to the joint scheduling of up to two carriers.
[0173] Optionally, if the terminal device supports the simultaneous activation of multiple BWPs on a single carrier, then the above indication method needs to indicate each of the multiple activated BWPs on each carrier separately.
[0174] It should be noted that the indication methods for DCI scheduling, the design of the carrier indication domain in DCI, and the design of the bandwidth indication domain in DCI can be designed independently of each other. However, in practical applications, once the indication method for DCI scheduling is selected, the design methods for the carrier indication domain and the bandwidth indication domain in DCI must also be compatible with the DCI scheduling method. Alternatively, once the design method for the carrier indication domain in DCI is selected, the design methods for the scheduling method and the bandwidth indication domain in DCI must also be compatible with the design method for the carrier indication domain. In other words, the three aspects of the DCI design described above need to be implemented jointly and are mutually compatible.
[0175] The third aspect of the above scheme (i.e., setting up a carrier group) will be explained below.
[0176] To reduce communication overhead between terminal devices and network devices, and to improve communication quality and efficiency, embodiments of this application provide a method for setting up carrier groups.
[0177] In this embodiment of the application, the network device defines a frequency band group, cell group, or carrier group.
[0178] A frequency band group comprises one or more frequency bands, a frequency band comprises one or more cells, and a cell comprises one or more carriers. These carriers include uplink carriers and / or downlink carriers.
[0179] A cell group comprises one or more cells, and a cell comprises one or more carriers. These carriers include uplink carriers and / or downlink carriers.
[0180] A carrier group comprises one or more carriers. These carriers include uplink carriers and / or downlink carriers.
[0181] The following example illustrates this. For instance, cell 1 and cell 2 are configured on frequency band 1. Cell 1 contains one uplink carrier (UL CA-1) and one downlink carrier (DL CA-1), while cell 2 contains two uplink carriers (UL CA-2 and UL CA-3) and one downlink carrier (DL CA-2). Cell 3 is also configured on frequency band 2, containing one uplink carrier (UL CA-4) and one downlink carrier (DL CA-3).
[0182] If a network device defines a frequency band group {frequency band 1, frequency band 2}, then the carriers corresponding to this frequency band group include: ULCA-1, UL CA-2, UL CA-3, UL CA-4, DL CA-1, DL CA-2, and DL CA-3.
[0183] If a network device defines a cell group {cell 1, cell 2}, then the carriers corresponding to this cell group include: ULCA-1, UL CA-2, UL CA-3, DL CA-1, and DL CA-2.
[0184] If a network device defines a carrier group {UL CA-1,UL-CA4,DL-CA1,DL-CA3}, then the carriers in this carrier group include: UL CA-1,UL-CA4,DL-CA1,DL-CA3.
[0185] Optionally, the network device can also define an uplink carrier group and a downlink carrier group. For example, if the network device defines an uplink carrier group {UL CA-1, UL CA-2, UL-CA3, UL-CA4}, then the carriers within this group include: ULCA-1, UL CA-2, UL-CA3, and UL-CA4. As another example, if the network device defines a downlink carrier group {DL-CA1, DL-CA2, DL-CA3}, then the carriers within this group include: DL-CA1, DL-CA2, and DL-CA3.
[0186] Therefore, network devices can specify a group of carriers by defining frequency band groups, cell groups, or carrier groups.
[0187] In the following embodiments of this application, a carrier group is defined as an example, and the carrier group may include uplink carriers and downlink carriers. In the embodiments of this application, the carriers within a carrier group need to satisfy certain relationships. For example, the uplink carriers within a carrier group need to satisfy certain relationships. As another example, the downlink carriers within a carrier group need to satisfy certain relationships.
[0188] As one implementation method, the relationships satisfied between uplink carriers within a carrier group include, but are not limited to, one or more of the following relationships:
[0189] A1: The uplink carriers within a carrier group have the same timing advance, or the difference in timing advance between different uplink carriers is less than a threshold value, which is a predefined value. Therefore, the timing advance between uplink carriers within this carrier group can be used interchangeably.
[0190] A2: The terminal device transmits PRACH only on the uplink primary carrier, or only on a predefined uplink carrier, or only on an uplink carrier within the carrier group configured by RRC signaling, and receives the random access response on the downlink carrier corresponding to that uplink carrier.
[0191] A3: The terminal device transmits the Physical Uplink Shared Channel (PUCCH) only on the uplink primary carrier, or only on a predefined uplink carrier, or only on one uplink carrier within the carrier group configured by the RRC signaling.
[0192] A4: The terminal device only transmits a Sounding Reference Signal (SRS) on a specific uplink carrier. This uplink carrier can be a predefined uplink carrier or an uplink carrier within a carrier group configured by RRC signaling.
[0193] A5: The terminal device transmits the Phase Tracking Reference Signal (PTRS) only on a specific uplink carrier. This uplink carrier can be a predefined uplink carrier or an uplink carrier within a carrier group configured by RRC signaling.
[0194] A6: Joint scheduling transmission can be performed between active uplink carriers within a carrier group. That is, for an uplink carrier, a downlink control information (DCI) can be used to schedule the uplink carrier bandwidth part (BWP) on multiple uplink carriers.
[0195] A7: All terminal devices use the same uplink primary carrier.
[0196] The advantage of satisfying A1 or A2 above is that network devices can configure PRACH resources on only one carrier within a carrier group. This carrier is predefined as the primary carrier, or the carrier with the largest / smallest carrier index, or a carrier configured by higher-layer signaling, thereby saving uplink resources. Optionally, when a terminal device needs uplink timing advance adjustment on a carrier, if there are no PRACH resources on that carrier and the carrier is configured within a carrier group, then the terminal device only needs to report a timing adjustment request, and the network device can use DCI to trigger PRACH transmission on a carrier with PRACH resources.
[0197] The advantage of meeting the above A3, A4, or A5 requirements is that it can save uplink resources.
[0198] The advantage of meeting the above A6 requirement is that it can save downlink control resources.
[0199] As one implementation method, the relationships satisfied between downlink carriers within a carrier group include, but are not limited to, one or more of the following relationships:
[0200] B1: The time-domain synchronization information of different downlink carriers is the same, or the difference in time-domain synchronization information between different downlink carriers is less than a threshold value, which is a predefined value, indicating that the time-domain synchronization information between downlink carriers in the carrier group can be used interchangeably.
[0201] B2: The frequency domain synchronization information of different downlink carriers is the same, or the difference in frequency domain synchronization information between different downlink carriers is less than a threshold value, which is a predefined value, indicating that the frequency domain synchronization information between downlink carriers in the carrier group can be used by each other.
[0202] B3: The measured values of different downlink carriers are the same, or the difference between the measured values of different downlink carriers is less than a threshold value, which is a predefined value. The measured values include reference signal receiving power (RSRP), reference signal receiving quality (RSRQ), path loss, coupling loss, etc.
[0203] B4: The CSI values of different downlink carriers are the same, or the difference between the CSI values of different downlink carriers is less than a threshold value, which is a predefined value. The CSI includes, but is not limited to, one or more of the following: CQI, PMI, RI, delay information, angle information, beam information, etc.
[0204] B5: Joint scheduling transmission can be performed between active downlink carriers within a carrier group. That is, for a downlink carrier, a single downlink control information (DCI) can schedule the downlink carrier bandwidth portion (BWP) on multiple downlink carriers.
[0205] B6: The network device transmits SSB on only one downlink carrier, which is predefined as the primary carrier, or the carrier with the largest / smallest carrier index in the carrier group, or a carrier configured by higher-layer signaling.
[0206] B7: Network devices transmit CSI-RS only on a specific downlink carrier, which can be a primary downlink carrier or a secondary downlink carrier. This downlink carrier can be configured through predefined or higher-layer signaling.
[0207] B8: Network devices only transmit PDCCH on the downlink primary carrier, and terminal devices only listen to PDCCH on the downlink primary carrier.
[0208] B9: Network devices transmit phase tracking reference signals only on a specific downlink carrier, which can be a primary downlink carrier or a secondary downlink carrier. This downlink carrier can be configured through predefined or higher-layer signaling.
[0209] B10: Network devices transmit cross-carrier scheduled DCIs or jointly scheduled DCIs only on a specific downlink carrier. This downlink carrier can be a primary downlink carrier or a secondary downlink carrier, and the downlink carrier can be configured through predefined or higher-layer signaling.
[0210] The advantage of satisfying B1, B2, B3, or B4 is that it enables rapid activation of terminal devices and saves reference signal resources for time-frequency synchronization.
[0211] The advantage of meeting the above B5 requirement is that it can save downlink control resources.
[0212] The advantage of meeting the above B6 or B7 requirements is that it can save network equipment resources.
[0213] The advantage of meeting the above B8 or B10 requirements is that it can save control channel resources.
[0214] The advantage of meeting the above B9 requirement is that it can save downlink resources.
[0215] As one implementation method, in this embodiment of the application, the maximum number of carriers within a carrier group can be predefined or determined based on the capabilities reported by the terminal device. Optionally, the terminal device can also report different maximum carrier count capabilities under different frequency bands to the network device.
[0216] As one implementation method, in this embodiment, the network device may not configure a carrier group. Instead, the network device configures one or more associated carriers for each carrier. Specific association relationships include: association of reference signals and association of parameters. For example, the CSI-RS of carrier 1 is associated with the CSI-RS of carrier 2, and the CSI of carrier 1 is associated with the CSI of carrier 2. The associated carrier parameters indicate that they can be used interchangeably, exhibiting the same characteristics as within the aforementioned carrier group. The parameters and reference signals represent another configuration method for the aforementioned carrier group. For instance, the network device configures association relationships between different carriers, or association relationships between reference signals on different carriers, or association relationships between one or more parameters on different carriers in the secondary cell configuration. This relationship is hereinafter represented by QCL (Quasi co-location)-X. For example, if the CSI-RS on downlink carrier 1 and the CSI-RS on downlink carrier 2 satisfy QCL-X, then B3 and / or B4 are satisfied. If the SSB on downlink secondary carrier 1 and the SSB on downlink carrier 2 satisfy QCL-X, then B1 and / or B2 are satisfied.
[0217] The following describes an implementation method that combines the carrier group configuration scheme of the third aspect with the fast activation scheme of the first aspect.
[0218] As one implementation method, if the downlink primary carrier and the downlink secondary carrier come from the same carrier group, and the different downlink carriers within that carrier group satisfy the aforementioned relationships B1 and / or B2, that is: the time-domain synchronization information and / or frequency-domain synchronization information of different downlink carriers are the same, or the difference between the time-domain synchronization information and / or frequency-domain synchronization information of different downlink carriers is less than a threshold, then the terminal device can use the time-domain synchronization information and / or frequency-domain synchronization information of the downlink primary carrier as the time-domain synchronization information and / or frequency-domain synchronization information of the downlink secondary carrier. Therefore, during the activation of the downlink secondary carrier, it is not necessary to perform [further steps]. Figure 2Step 206 in the corresponding embodiment can save communication overhead between the terminal device and the network device.
[0219] As another implementation method, if the downlink primary carrier and the downlink secondary carrier come from the same carrier group, and the different downlink carriers within that carrier group satisfy the above relationships B3 and / or B4, that is: the CSI values of different downlink carriers are the same, or the difference in CSI values between different downlink carriers is less than a threshold, then the terminal device can use the CSI value of the downlink primary carrier, thus eliminating the need for further execution. Figure 2 In step 207 of the corresponding embodiment, the terminal device does not need to perform channel measurement, which can save communication overhead between the terminal device and the network device.
[0220] As another implementation method, if the downlink primary carrier and the downlink secondary carrier come from the same carrier group, and different downlink carriers within that carrier group satisfy the above-mentioned relationships B1 and / or B2, and B3 and / or B4, then the following can be obtained: Figure 3 The corresponding implementation scheme.
[0221] The following describes an implementation method that combines the carrier group configuration scheme of the third aspect with the carrier joint scheduling scheme of the second aspect.
[0222] As one implementation method, in this embodiment of the application, the carrier transmitting PDCCH among the N carriers scheduled by DCI can be predefined or configured via MAC CE signaling, RRC signaling, or DCI signaling. These N carriers can come from the same carrier group, and the carriers within this carrier group satisfy the conditions B5 and / or B6 described above.
[0223] It should be noted that, in the embodiments of this application, the carrier group configuration scheme of the third aspect can also be combined with the fast activation scheme of the first aspect and the carrier joint scheduling scheme of the second aspect.
[0224] For example, a carrier group can be predefined, in which the carriers within the carrier group satisfy at least the following 1) to 3):
[0225] 1) B1 and / or B2 as defined above;
[0226] 2) B3 and / or B4 as defined above;
[0227] 3) B5 and / or B6 as defined above.
[0228] In this combined scheme, rapid carrier activation and joint carrier scheduling can be achieved, thereby saving communication overhead between terminal devices and network devices at different stages and greatly improving the communication efficiency between terminal devices and network devices.
[0229] The above mainly describes the solution provided in this application from the perspective of interaction between various network elements. It is understood that, in order to achieve the above functions, each network element includes corresponding hardware structures and / or software modules for executing each function. Those skilled in the art should readily recognize that, based on the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein, this invention can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art 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 invention.
[0230] It is understood that, in the above method embodiments, the steps or operations corresponding to those implemented by the terminal device can also be implemented by components (e.g., chips or circuits) configured on the terminal device. Similarly, the steps or operations corresponding to those implemented by the network device can also be implemented by components (e.g., chips or circuits) configured on the network device.
[0231] This application also provides apparatus for implementing any of the above methods. For example, an apparatus is provided that includes units (or means) for implementing the various steps performed by the terminal device in any of the above methods. For example, an apparatus is provided that includes units (or means) for implementing the various steps performed by the network device in any of the above methods.
[0232] refer to Figure 5 This is a schematic diagram of a communication device provided in an embodiment of this application. The device is used to implement the above-described... Figure 3 or Figure 4 In the method embodiments, the various steps performed by the corresponding network device are as follows: Figure 5 As shown, the device 500 includes a transceiver unit 510 and a determination unit 520.
[0233] In the first embodiment:
[0234] Transceiver unit 510 is configured to send a first signaling message to a terminal device on a downlink primary carrier, the first signaling message containing configuration information of a secondary cell, the configuration information of the secondary cell including downlink secondary carrier information, or including downlink secondary carrier information and uplink secondary carrier information; and send a second signaling message to the terminal device, the second signaling message being used by the terminal device to activate the secondary cell; and determining unit 520 is configured to determine, based on a Channel State Information (CSI) report and / or feedback signaling received from the terminal device, that the terminal device has successfully activated the secondary cell, the feedback signaling being used to indicate feedback information of the second signaling message; wherein, the time-frequency domain synchronization information of the downlink primary carrier is the same as the time-frequency domain synchronization information of the downlink secondary carrier, or the difference between the time-frequency domain synchronization information of the downlink primary carrier and the time-frequency domain synchronization information of the downlink secondary carrier is less than a first threshold; and the CSI value of the downlink primary carrier is the same as the CSI value of the downlink secondary carrier, or the difference between the CSI value of the downlink primary carrier and the CSI value of the downlink secondary carrier is less than a second threshold.
[0235] In one possible implementation, the determining unit 520 is specifically configured to determine that the terminal device has successfully activated the secondary cell if the transceiver unit 510 receives the CSI report from the terminal device and the CSI report is a valid CSI report; or, determine that the terminal device has successfully activated the secondary cell at a first moment, wherein the time interval between the first moment and receiving the feedback signaling is greater than or equal to a first preset duration; or, determine that the terminal device has successfully activated the secondary cell if the transceiver unit 510 receives the CSI report at a second moment and the CSI report is a valid CSI report, wherein the time interval between the second moment and receiving the feedback signaling is greater than or equal to a second preset duration.
[0236] In one possible implementation, the first set duration is equal to (the number of time slots in a subframe corresponding to the subcarrier interval + 1) * the duration of one time slot; wherein, the subcarrier interval is the subcarrier interval corresponding to the PUCCH, and the PUCCH is used to carry feedback information of the second signaling.
[0237] In one possible implementation, the second set duration is equal to (the number of time slots in a subframe corresponding to the subcarrier interval + 1) * the duration of a time slot; wherein the subcarrier interval is the subcarrier interval corresponding to the PUCCH, and the PUCCH is used to carry feedback information of the second signaling.
[0238] In one possible implementation, the first signaling is Media Access Control (MAC) CE signaling, Radio Resource Control (RRC) signaling, or Downlink Control Information (DCI) signaling.
[0239] In one possible implementation, the second signaling is MAC CE signaling, Radio Resource Control (RRC) signaling, or Downlink Control Information (DCI) signaling.
[0240] In the second embodiment:
[0241] The determining unit 520 is used to determine a first downlink control information (DCI), which is used to schedule M data channels, the M data channels are mapped onto N carriers, the N carriers are used for data transmission of the M data channels, and one of the M data channels is mapped onto at least one of the N carriers, where M is a positive integer and N is an integer greater than 1; the transceiver unit 510 is used to send the first DCI to the terminal device.
[0242] In one possible implementation, the determining unit 520 is further configured to determine a second DCI, the second DCI being used to schedule K data channels, the K data channels being mapped onto one carrier, the one carrier being used for data transmission of the K data channels, where K is a positive integer; the transceiver unit 510 is further configured to send the second DCI to the terminal device; wherein the scrambling identifier corresponding to the first DCI is different from the scrambling identifier corresponding to the second DCI.
[0243] In one possible implementation, the first DCI includes a first identification field, which indicates that the first DCI is used for scheduling the N carriers.
[0244] In one possible implementation, the transceiver unit 510 is further configured to send Radio Resource Control (RRC) signaling to the terminal device, the RRC signaling being used to instruct the first DCI to be used for scheduling the N carriers.
[0245] In one possible implementation, the N carriers include a carrier for transmitting the first DCI and N-1 other carriers, the other N-1 carriers being configured via RRC signaling; or, the N carriers being configured via RRC signaling; or, the first DCI includes N-1 carrier indication fields, the N carriers including a carrier for transmitting the first DCI and N-1 other carriers, the N-1 carrier indication fields being used to indicate the other N-1 carriers; or, the first DCI includes a carrier indication field, the carrier indication field being used to indicate an index of a carrier group, the carrier group including the N carriers, the carrier group being configured via RRC signaling.
[0246] In one possible implementation, the first DCI includes a BWP indication field for indicating N BWPs with the same index on the N carriers; or, the first DCI includes a BWP group indication field for indicating the index of a BWP group, the BWP group including at least one BWP on each of the N carriers; or, the first DCI includes N BWP indication fields for indicating N BWPs on the N carriers.
[0247] It is understood that the above-mentioned units can also be referred to as modules or circuits, and the above-mentioned units can be set up independently or integrated in whole or in part. The above-mentioned transceiver unit 510 can also be referred to as a communication interface.
[0248] Optionally, the communication device 500 may further include a storage unit for storing data or instructions (also referred to as code or programs). The various units described above can interact with or be coupled to the storage unit to implement corresponding methods or functions. For example, the processing unit can read data or instructions from the storage unit, enabling the communication device to implement the methods described in the above embodiments.
[0249] refer to Figure 6 This is a schematic diagram of a communication device provided in an embodiment of this application. The device is used to implement the above-described... Figure 3 or Figure 4 In the method embodiments, the steps executed by the corresponding terminal device are as follows: Figure 6 As shown, the device 600 includes a transceiver unit 610 and a processing unit 620.
[0250] In the first embodiment:
[0251] Transceiver unit 610 is configured to receive first signaling from a network device on a downlink primary carrier, the first signaling containing configuration information of a secondary cell, the configuration information of the secondary cell including downlink secondary carrier information, or including downlink secondary carrier information and uplink secondary carrier information; receive second signaling from the network device, the second signaling being used to activate the secondary cell for the terminal device; and send a Channel State Information (CSI) report and / or feedback signaling to the network device, the feedback signaling being used to indicate feedback information of the second signaling. Processing unit 620 is configured to perform downlink synchronization with the downlink secondary carrier based on the time-frequency domain synchronization information of the downlink primary carrier and the configuration information of the downlink secondary carrier; wherein the time-frequency domain synchronization information of the downlink primary carrier is the same as the time-frequency domain synchronization information of the downlink secondary carrier, or the difference between the time-frequency domain synchronization information of the downlink primary carrier and the time-frequency domain synchronization information of the downlink secondary carrier is less than a first threshold; the CSI value of the downlink primary carrier is the same as the CSI value of the downlink secondary carrier, or the difference between the CSI value of the downlink primary carrier and the CSI value of the downlink secondary carrier is less than a second threshold.
[0252] In one possible implementation, the first signaling is Media Access Control (MAC) CE signaling, Radio Resource Control (RRC) signaling, or Downlink Control Information (DCI) signaling.
[0253] In one possible implementation, the second signaling is MAC CE signaling.
[0254] In the second embodiment:
[0255] Transceiver unit 610 is configured to receive first downlink control information (DCI) from a network device. The first DCI is used to schedule M data channels, which are mapped onto N carriers. The N carriers are used for data transmission on the M data channels. One of the M data channels is mapped onto at least one of the N carriers. M is a positive integer and N is an integer greater than 1. Processing unit 620 is configured to communicate with the network device on at least one of the N carriers according to the first DCI.
[0256] In one possible implementation, the transceiver unit 610 is further configured to receive a second DCI from the network device, the second DCI being used to schedule K data channels, the K data channels being mapped onto one carrier, the one carrier being used for data transmission of the K data channels, where K is a positive integer; the processing unit 620 is further configured to communicate with the network device on the one carrier according to the second DCI; wherein the scrambling identifier corresponding to the first DCI is different from the scrambling identifier corresponding to the second DCI.
[0257] In one possible implementation, the first DCI includes a first identification field, which indicates that the first DCI is used for scheduling the N carriers.
[0258] In one possible implementation, the transceiver unit 610 is further configured to receive Radio Resource Control (RRC) signaling from the network device, the RRC signaling being used to instruct the first DCI to be used for scheduling the N carriers.
[0259] In one possible implementation, the N carriers include a carrier for transmitting the first DCI and N-1 other carriers, the other N-1 carriers being configured via RRC signaling; or, the N carriers being configured via RRC signaling; or, the first DCI includes N-1 carrier indication fields, the N carriers including a carrier for transmitting the first DCI and N-1 other carriers, the N-1 carrier indication fields being used to indicate the other N-1 carriers; or, the first DCI includes a carrier indication field, the carrier indication field being used to indicate an index of a carrier group, the carrier group including the N carriers, the carrier group being configured via RRC signaling.
[0260] In one possible implementation, the first DCI includes a BWP indication field for indicating N BWPs with the same index on the N carriers; or, the first DCI includes a BWP group indication field for indicating the index of a BWP group, the BWP group including at least one BWP on each of the N carriers; or, the first DCI includes N BWP indication fields for indicating N BWPs on the N carriers.
[0261] It is understood that the aforementioned units can also be referred to as modules or circuits, and the aforementioned units can be set up independently or integrated in whole or in part. The aforementioned transceiver unit 610 can also be referred to as a communication interface, and the aforementioned processing unit 620 can also be referred to as a processor.
[0262] Optionally, the communication device 600 may further include a storage unit for storing data or instructions (also referred to as code or programs). The various units described above can interact with or be coupled to the storage unit to implement corresponding methods or functions. For example, the processing unit can read data or instructions from the storage unit, enabling the communication device to implement the methods described in the above embodiments.
[0263] It should be understood that the division of units in the above device is merely a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, all units in the device can be implemented entirely through software calls from processing elements; all units can be implemented entirely in hardware; or some units can be implemented through software calls from processing elements, and others in hardware. For example, each unit can be a separate processing element, or it can be integrated into a chip within the device. Alternatively, it can be stored as a program in memory, called and executed by a processing element of the device. Moreover, these units can be fully or partially integrated together, or implemented independently. The processing element mentioned here can also be called a processor, which can be an integrated circuit with signal processing capabilities. In the implementation process, each step of the above method or each of the above units can be implemented through integrated logic circuits in the processor element or through software calls from processing elements.
[0264] In one example, a unit in any of the above devices can be one or more integrated circuits configured to implement the methods described above, such as: one or more Application Specific Integrated Circuits (ASICs), or one or more digital signal processors (DSPs), or one or more Field Programmable Gate Arrays (FPGAs), or a combination of at least two of these forms of integrated circuits. As another example, when a unit in the device can be implemented in the form of a processing element scheduler, the processing element can be a general-purpose processor, such as a Central Processing Unit (CPU) or other processor capable of calling programs. Furthermore, these units can be integrated together to implement a system-on-a-chip (SOC).
[0265] The receiving unit described above (e.g., a receiving unit) is an interface circuit of the device used to receive signals from other devices. For example, when the device is implemented as a chip, the receiving unit is an interface circuit for the chip to receive signals from other chips or devices. The transmitting unit described above (e.g., a transmitting unit) is an interface circuit of the device used to transmit signals to other devices. For example, when the device is implemented as a chip, the transmitting unit is an interface circuit for the chip to transmit signals to other chips or devices.
[0266] refer to Figure 7This is a schematic diagram of a terminal device provided in an embodiment of this application. The terminal device is used to achieve the above... Figure 3 or Figure 4 The operation of the terminal device in the corresponding embodiment. For example... Figure 7 As shown, the terminal device includes an antenna 710, a radio frequency (RF) device 720, and a signal processing unit 730. The antenna 710 is connected to the RF device 720. In the downlink direction, the RF device 720 receives information sent by the network device through the antenna 710 and sends the information to the signal processing unit 730 for processing. In the uplink direction, the signal processing unit 730 processes the information from the terminal device and sends it to the RF device 720. The RF device 720 processes the information from the terminal device and then sends it to the network device through the antenna 710.
[0267] The signal processing section 730 is used to process data at various communication protocol layers. The signal processing section 730 can be a subsystem of the terminal device. The terminal device may also include other subsystems, such as a central processing subsystem for processing the terminal device's operating system and application layers; or a peripheral subsystem for connecting to other devices. The signal processing section 730 can be a separately configured chip. Optionally, the above-mentioned devices can be located within the signal processing section 730.
[0268] The signal processing section 730 may include one or more processing elements 731, such as a main control CPU and other integrated circuits, and an interface circuit 733. Furthermore, the signal processing section 730 may also include a storage element 732. The storage element 732 is used to store data and programs. The program for executing the method performed by the terminal device in the above methods may or may not be stored in the storage element 732, for example, it may be stored in a memory outside the signal processing section 730. When needed, the signal processing section 730 loads the program into a cache for use. The interface circuit 733 is used to communicate with other devices. The above devices may be located in the signal processing section 730, which can be implemented by a chip. The chip includes at least one processing element and an interface circuit, wherein the processing element is used to execute the various steps of any of the methods executed by the terminal device, and the interface circuit is used to communicate with other devices. In one implementation, the unit implementing the various steps of the above methods can be implemented in the form of a processing element scheduler. For example, the device includes a processing element and a storage element, and the processing element calls the program stored in the storage element to execute the method executed by the terminal device in the above method embodiments. Storage elements can be storage elements located on the same chip as processing elements, i.e., on-chip storage elements.
[0269] In another implementation, the program used to execute the method performed by the terminal device in the above method can be located on a storage element on a different chip than the processing element, i.e., an off-chip storage element. In this case, the processing element calls or loads the program from the off-chip storage element onto the on-chip storage element to call and execute the method executed by the terminal device in the above method embodiments.
[0270] In another implementation, the unit in the terminal device that implements each step of the above method can be configured as one or more processing elements, which are disposed on the signal processing section 730. These processing elements can be integrated circuits, such as one or more ASICs, one or more DSPs, one or more FPGAs, or combinations of these types of integrated circuits. These integrated circuits can be integrated together to form a chip.
[0271] The units implementing each step of the above method can be integrated together as a system-on-a-chip (SOC). This SOC chip is used to implement the above method. This chip can integrate at least one processing element and a storage element, with the processing element calling a stored program in the storage element to implement the method executed by the terminal device; alternatively, this chip can integrate at least one integrated circuit to implement the method executed by the terminal device; or, a combination of the above implementation methods can be used, with the function of some units implemented by the processing element calling a program, and the function of some units implemented by the integrated circuit.
[0272] As can be seen, the above apparatus may include at least one processing element and an interface circuit, wherein the at least one processing element is used to execute the method provided by any of the terminal devices in the above method embodiments. The processing element may execute part or all of the steps executed by the terminal device in a first manner: that is, by calling a program stored in a storage element; or in a second manner: that is, by combining instructions with the integrated logic circuits of the hardware in the processor element; of course, it may also combine the first and second methods to execute part or all of the steps executed by the terminal device.
[0273] The processing element here, as described above, can be a general-purpose processor, such as a CPU, or one or more integrated circuits configured to implement the above methods, such as one or more ASICs, or one or more microprocessors (DSPs), or one or more FPGAs, or a combination of at least two of these integrated circuit forms. The storage element can be a single memory or a collective term for multiple storage elements.
[0274] refer to Figure 8 This is a schematic diagram of a network device provided in an embodiment of this application. This network device is used to achieve the above... Figure 3 or Figure 4 The operation of the network device in the corresponding embodiment. For example... Figure 8 As shown, the network device includes: an antenna 810, a radio frequency (RF) device 820, and a baseband device 830. The antenna 810 is connected to the RF device 820. In the uplink direction, the RF device 820 receives information sent by the terminal device through the antenna 810 and transmits the information to the baseband device 830 for processing. In the downlink direction, the baseband device 830 processes the information from the terminal device and transmits it to the RF device 820, which then processes the information and transmits it to the terminal device through the antenna 810.
[0275] The baseband device 830 may include one or more processing elements 831, such as a main control CPU and other integrated circuits, and also includes an interface 833. Furthermore, the baseband device 830 may also include a storage element 832 for storing programs and data; the interface 833 is used to interact with the radio frequency device 820, such as a Common Public Radio Interface (CPRI). The above-described means for the network device may be located in the baseband device 830. For example, the above-described means for the network device may be a chip on the baseband device 830, which includes at least one processing element and interface circuitry. The processing element is used to execute the various steps of any of the methods executed by the network device, and the interface circuitry is used to communicate with other devices. In one implementation, the unit of the network device that implements the various steps of the above methods can be implemented in the form of a processing element scheduler. For example, the means for the network device includes a processing element and a storage element, and the processing element calls the program stored in the storage element to execute the method executed by the network device in the above method embodiments. Storage elements can be storage elements located on the same chip as the processing elements, i.e., on-chip storage elements, or storage elements located on different chips than the processing elements, i.e., off-chip storage elements.
[0276] In another implementation, the units in the network device that implement the steps of the above methods can be configured as one or more processing elements located on the baseband device. These processing elements can be integrated circuits, such as one or more ASICs, one or more DSPs, one or more FPGAs, or combinations of these types of integrated circuits. These integrated circuits can be integrated together to form a chip.
[0277] The units implementing the various steps of the above methods in a network device can be integrated together as a system-on-a-chip (SOC). For example, a baseband device includes this SOC chip to implement the above methods. This chip can integrate at least one processing element and a storage element, with the processing element calling a stored program from the storage element to implement the methods executed by the network device. Alternatively, the chip can integrate at least one integrated circuit to implement the methods executed by the network device. Or, a combination of the above implementation methods can be used, where the functions of some units are implemented by the processing element calling a program, and the functions of other units are implemented by integrated circuits.
[0278] As can be seen, the above-described apparatus for a network device may include at least one processing element and an interface circuit, wherein the at least one processing element is used to execute any of the methods provided by the network device in the above method embodiments. The processing element may execute part or all of the steps executed by the network device in a first manner: that is, by calling a program stored in a storage element; or in a second manner: that is, by combining instructions with the integrated logic circuits of the hardware in the processor element; of course, it may also combine the first and second methods to execute part or all of the steps executed by the network device.
[0279] The processing element here, as described above, can be a general-purpose processor, such as a CPU, or one or more integrated circuits configured to implement the above methods, such as one or more ASICs, or one or more microprocessors (DSPs), or one or more FPGAs, or a combination of at least two of these integrated circuit forms. The storage element can be a single memory or a collective term for multiple storage elements.
[0280] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state disk (SSD)).
[0281] Those skilled in the art will understand that the various numerical designations used in this application, such as "first," "second," "third," and "fourth," are merely for descriptive convenience and are not intended to limit the scope of the embodiments of this application, nor do they indicate a sequential order. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one" refers to one or more. "At least two" refers to two or more. "At least one," "any one," or similar expressions refer to any combination of these items, including any combination of single or multiple items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple. "Multiple" refers to two or more, and other quantifiers are similar.
[0282] The various illustrative logic units and circuits described in the embodiments of this application can be implemented or operate the described functions using a general-purpose processor, digital signal processor, application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof. The general-purpose processor can be a microprocessor; alternatively, it can also be any conventional processor, controller, microcontroller, or state machine. The processor can also be implemented using a combination of computing devices, such as a digital signal processor and a microprocessor, multiple microprocessors, one or more microprocessors combined with a digital signal processor core, or any other similar configuration.
[0283] In one or more exemplary designs, the functions described herein can be implemented in hardware, software, firmware, or any combination of these three. If implemented in software, these functions can be stored on a computer-readable medium or transmitted on a computer-readable medium in the form of one or more instructions or code. Computer-readable media includes computer storage media and communication media that facilitate the transfer of computer programs from one location to another. Storage media can be any available media accessible to a general-purpose or special-purpose computer. For example, such computer-readable media can include, but is not limited to, RAM, ROM, EEPROM, CD-ROM or other optical disc storage, disk storage or other magnetic storage devices, or any other medium that can be used to carry or store program code in the form of instructions or data structures and other formats readable by a general-purpose or special-purpose computer or processor. Furthermore, any connection can be suitably defined as a computer-readable medium, for example, if the software is transmitted from a website, server, or other remote resource via a coaxial cable, fiber optic computer, twisted pair, digital subscriber line (DSL), or wirelessly, such as infrared, wireless, and microwave, it is also included in the definition of a computer-readable medium. The disks and discs mentioned include compressed disks, laser discs, optical discs, Digital Versatile Discs (DVDs), floppy disks, and Blu-ray discs. Disks typically copy data magnetically, while discs typically copy data optically using lasers. Combinations of these can also be contained in computer-readable media.
[0284] Those skilled in the art will recognize that, in one or more of the examples above, the functions described in this application can be implemented using hardware, software, firmware, or any combination thereof. When implemented in software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or code on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any medium that facilitates the transfer of a computer program from one place to another. Storage media can be any available medium accessible to a general-purpose or special-purpose computer.
[0285] The specific embodiments described above further illustrate the purpose, technical solution, and beneficial effects of this application. It should be understood that the above descriptions are merely specific embodiments of this application and are not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, or improvements made based on the technical solution of this application should be included within the scope of protection of this application. The above description in this application specification allows for the utilization or implementation of the content of this application by anyone skilled in the art. Any modifications based on the disclosed content should be considered obvious in the art. The basic principles described in this application can be applied to other variations without departing from the inventive nature and scope of this application. Therefore, the content disclosed in this application is not limited to the described embodiments and designs but can be extended to the maximum extent consistent with the principles and novel features disclosed in this application.
[0286] Although this application has been described in conjunction with specific features and embodiments, it is obvious that various modifications and combinations can be made thereto without departing from the spirit and scope of this application. Accordingly, this specification and drawings are merely illustrative descriptions of the application as defined by the appended claims, and are considered to cover any and all modifications, variations, combinations, or equivalents within the scope of this application. Clearly, those skilled in the art can make various alterations and modifications to this application without departing from its scope. Thus, if such modifications and modifications fall within the scope of the claims and their equivalents, this application is also intended to include such modifications and modifications.
Claims
1. A communication method characterized by comprising: include: A first downlink control information (DCI) is determined. The first DCI is used to schedule M data channels, which are mapped to N carriers. One of the M data channels is mapped to at least one of the N carriers. M is a positive integer and N is an integer greater than 1. Send the first DCI to the terminal device; The first DCI includes a carrier indication field, which is used to indicate the index of a carrier group, the carrier group including the N carriers, and the carrier group is configured by Radio Resource Control (RRC) signaling. The first DCI also includes a partial bandwidth BWP indication field, which is used to indicate N BWPs with the same index on the N carriers.
2. The method of claim 1, wherein, The method further includes: Multiple carrier groups are sent to the terminal device, wherein the carrier groups belong to the multiple carrier groups.
3. The method according to claim 1 or 2, characterized in that, The maximum number of carriers scheduled in the first DCI is predefined.
4. The method according to claim 1 or 2, characterized in that, The M data channels include the Physical Downlink Shared Channel (PDSCH) or the Physical Uplink Shared Channel (PUSCH).
5. The method according to claim 1 or 2, characterized in that, The first DCI further includes a first identifier field, which is used to indicate that the first DCI is used for scheduling the N carriers; or, The terminal device is sent an RRC signaling message, which is used to instruct the first DCI to be used for scheduling the N carriers.
6. A communication method characterized by comprising: include: The network device receives a first DCI, which is used to schedule M data channels, the M data channels are mapped to N carriers, and one of the M data channels is mapped to at least one of the N carriers, where M is a positive integer and N is an integer greater than 1. According to the first DCI, communication is made with the network device on at least two of the N carriers; The first DCI includes a carrier indication field, which is used to indicate the index of a carrier group, the carrier group including the N carriers, and the carrier group is configured via RRC signaling; The first DCI also includes a partial bandwidth BWP indication field, which is used to indicate N BWPs with the same index on the N carriers.
7. The method of claim 6, wherein, The method further includes: The network device receives multiple carrier groups, wherein the carrier groups belong to the multiple carrier groups.
8. The method of claim 7, wherein, The method further includes: transmitting a Physical Uplink Control Channel (PUCCH) on an uplink primary carrier within a carrier group indicated by the carrier indication field, or transmitting a PUCCH on a predefined uplink carrier, or transmitting a PUCCH on an uplink carrier within a carrier group configured by RRC signaling.
9. The method according to claim 7 or 8, characterized in that, The relationships that the downlink carriers within the carrier group indicated by the carrier indication field satisfy include one or more of the following: The time-domain synchronization information of different downlink carriers is the same, or the difference in time-domain synchronization information between different downlink carriers is less than a first threshold, wherein the first threshold is a predefined value, indicating that the time-domain synchronization information between downlink carriers within a carrier group can be used interchangeably; The frequency domain synchronization information of different downlink carriers is the same, or the difference in frequency domain synchronization information between different downlink carriers is less than a second threshold, wherein the second threshold is a predefined value, indicating that the frequency domain synchronization information between downlink carriers within a carrier group can be used interchangeably.
10. The method according to claim 6 or 7, characterized in that, in, The first DCI includes a first identifier field, which indicates that the first DCI is used for scheduling the N carriers; or, Receive RRC signaling from the network device, the RRC signaling being used to instruct the first DCI to be used for scheduling the N carriers.
11. A communications device, characterized by Includes a processor, the processor being configured to cause the communication device to perform the method of any one of claims 1-5 by executing a computer program or instructions, or by using logic circuitry.
12. The communication apparatus according to claim 11, wherein The communication device further includes a memory for storing the computer program or instructions.
13. A communications device, characterized by Includes a processor, the processor being configured to cause the communication device to perform the method of any one of claims 6-10 by executing a computer program or instructions, or by using logic circuitry.
14. The communication apparatus according to claim 13, wherein The communication device further includes a memory for storing the computer program or instructions.
15. A computer readable storage medium characterized by: Includes a computer program that, when run on a computer, causes the computer to perform the method as described in any one of claims 1-10.
