RRC signaling transmission method and communication apparatus

Abstract

An RRC signaling transmission method and a communication apparatus. In a carrier aggregation scenario, if a CSI-RS resource configuration on a first carrier (e.g., a PCC) are the same as CSI-RS resource configurations on the other carriers (e.g., a plurality of SCCs), in RRC signaling, indication information (e.g., a CC list) can be added to the CSI-RS resource configuration part of the first carrier, the indication information indicates that the CSI-RS resource configuration on the first carrier is the same as the CSI-RS resource configurations corresponding to the other CCs, and RRC may not comprise configuration information of CSI-RS resources on the other carriers; alternatively, an identifier of the first carrier can also be added to the CSI-RS resource configuration parts of the other carriers in the RRC, and the RRC may not comprise the specific configuration information of the CSI-RS resources on the other carriers, thus reducing the length (overhead) of the RRC signaling and the consumption of communication resources by the RRC.

Description

RRC signaling transmission method and communication device

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office on November 27, 2023, with application number 202311597718.9 and application name “RRC signaling transmission method and communication device”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communications, and more specifically, to a method and a communication device for RRC signaling transmission. Background Art

[0003] To further increase the transmission rate, the protocol supports carrier aggregation (CA) technology, which aggregates multiple component carriers (CCs) for data transmission, thereby increasing the bandwidth of data transmission and the data transmission rate. For each CC accessed by a terminal device, the base station is required to use radio resource control (RRC) signaling to configure channel state information-reference signal (CSI-RS) resources for that CC. Since a terminal may access multiple CCs through CA, as the number of CCs and bandwidth continue to increase, RRC signaling needs to configure the CSI-RS resources corresponding to each of these multiple CCs. As a result, the overhead (or length) of RRC signaling will increase, requiring more communication resources to transmit RRC, which increases the consumption of communication resources.

[0004] Summary of the Invention

[0005] The present application provides a method and a communication device for RRC signaling transmission, which can reduce the length (overhead) of RRC signaling and reduce the consumption of communication resources by RRC.

[0006] In a first aspect, a method for transmitting RRC signaling is provided. The execution subject of the method may be a network device, or a chip, chip system, or processor that supports the network device in implementing the method, or a logical node, logic module, or software that can implement all or part of the network device functions. The method includes: sending RRC signaling, the RRC signaling including a CSI-RS resource configuration and indication information corresponding to a first CC, the indication information being used to indicate that the CSI-RS resource configuration corresponding to the first CC is the same as the CSI-RS resource configuration corresponding to at least one CC, and that the first CC and the at least one CC are both carriers serving a terminal device. The RRC signaling does not include the CSI-RS resource configuration corresponding to the at least one CC.

[0007] In the first aspect, the RRC signaling transmission method provided herein, in a carrier aggregation scenario, if the CSI-RS resource configuration on a carrier (e.g., a first CC) is identical to the CSI-RS resource configuration on another carrier (a second CC), the identifier of the first CC can be added to the portion of the RRC signaling that configures the CSI-RS resources on the second carrier. The identifier of the first CC is used to indicate that the CSI-RS resource configuration corresponding to the second CC is identical to the CSI-RS resource configuration corresponding to the first CC. The RRC signaling then need not include specific configuration information for the CSI-RS resources on the second CC, thereby reducing the length (overhead) of the RRC signaling, addressing the issue of large RRC signaling length (high overhead), and reducing the RRC's consumption of communication resources.

[0008] In a possible implementation of the first aspect, the indication information includes a CC list, where the CC list includes an identifier corresponding to at least one CC. In this implementation, it is possible to more accurately indicate which CCs correspond to the same NZP CSI-RS resource configuration as the NZP CSI-RS resource configuration corresponding to the first CC. This improves the accuracy of the indication information, facilitates implementation, and reduces the overhead of the indication information.

[0009] Exemplarily, the CSI-RS resource configuration includes at least one of an NZP CSI-RS resource configuration or a CSI-IM resource configuration. In this implementation, since the NZP CSI-RS resource configuration and the CSI-IM resource configuration include more configurations, the gain in reducing the length of the RRC signaling is more significant.

[0010] For example, the NZP CSI-RS can be used for time / frequency tracking, CSI computation, L1-RSRP calculation, L1-SINR calculation, etc. For example, when the ZP CSI-RS is used for time / frequency tracking, the NZP CSI-RS can be a TRS. Optionally, the NZP CSI-RS can also be used for mobility management.

[0011] Exemplarily, the first CC is a PCC, and at least one CC is an SCC. In this implementation, the PCC follows the setting of the SCC LIST in the corresponding CSI-RS resource configuration part, which is consistent with the actual scenario, improves the practicality of the method provided in this application, and the gain is quite obvious.

[0012] Exemplarily, the first CC may also be an SCC, and each CC in the CC list may also be an SCC.

[0013] For example, when the RRC signaling includes the configuration of the NZP CSI-RS resources corresponding to the first CC and the CC list, the RRC signaling does not need to include the configuration of the NZP CSI-RS resources corresponding to each CC in the CC list. In other words, it is no longer necessary to configure NZP CSI-RS resources for each CC in the CC list in the RRC signaling, that is, the NZP CSI-RS resource configuration information on each CC in the CC list is deleted in the RRC, achieving a configuration-free effect.

[0014] For example, NZP CSI-RS resources or CSI-IM resources can be configured for each CC in the "CSI-MeasConfig" in the RRC signaling, and the indication information is located in the NZP CSI-RS resource configuration part or the CSI-IM resource part in the "CSI-MeasConfig" field corresponding to the first CC.

[0015] Optionally, if it is an NZP CSI-RS resource configuration for mobility management, indication information (for example, the above-mentioned CC list) can be added to the "CSI-RS-ResourceConfigMobility" part corresponding to the first CC in the RRC signaling. If it is a ZP CSI-RS resource configuration, indication information (for example, the above-mentioned CC list) can be added to the "PDSCH-Config IE" part corresponding to the first CC in the RRC signaling. In this way, the RRC signaling does not need to include the NZP CSI-RS resource configuration or ZP CSI-RS resource configuration for mobility management corresponding to each CC in the CC list, and can also reduce the length (overhead) of the RRC signaling, solve the problem of the large length (large overhead) of the RRC signaling, and reduce the consumption of communication resources by RRC.

[0016] In the second aspect, a method for RRC signaling transmission is provided, wherein the execution subject of the method may be a network device, or a chip, chip system, or processor that supports the network device to implement the method, or a logical node, logic module, or software that can implement all or part of the network device functions. The method comprises: sending RRC signaling, wherein the RRC signaling includes the CSI-RS resource configuration corresponding to the first CC, and the CSI-RS resource configuration part of the second CC in the RRC signaling includes the identifier of the first CC, and the identifier of the first CC is used to indicate that the CSI-RS resource configuration corresponding to the second CC is the same as the CSI-RS resource configuration corresponding to the first CC, and both the first CC and the second CC are carriers serving the terminal device. The CSI-RS resource configuration part of the second CC in the RRC signaling does not include the CSI-RS resource configuration corresponding to the second CC.

[0017] The second aspect provides a method for RRC signaling transmission. In a carrier aggregation scenario, if the CSI-RS resource configuration on a carrier (e.g., a first CC) is the same as the CSI-RS resource configuration on another carrier (a second CC), the identifier of the first CC can be added to the portion of the RRC signaling that configures the CSI-RS resources for the second carrier. The identifier of the first CC is used to indicate that the CSI-RS resource configuration corresponding to the second CC is the same as the CSI-RS resource configuration corresponding to the first CC. The RRC does not need to include specific configuration information for the CSI-RS resources on the second CC, thereby reducing the length (overhead) of the RRC signaling, resolving the problem of large RRC signaling length (high overhead), and reducing the consumption of communication resources by the RRC.

[0018] Exemplarily, the first CC is a PCC or an SCC, and the second CC is an SCC. In this implementation, by adding the identifier of the PCC or another SCC to the CSI-RS resource configuration part corresponding to the SCC, it is more consistent with the actual scenario, thereby improving the practicality of the method provided in this application, and the gain is more obvious.

[0019] Exemplarily, the CSI-RS resource configuration includes at least one of an NZP CSI-RS resource configuration or a CSI-IM resource configuration. In this implementation, since the NZP CSI-RS resource configuration and the CSI-IM resource configuration include more configurations, the gain in reducing the length of the RRC signaling is more significant.

[0020] Exemplarily, the first CC is a PCC or an SCC, and the second CC is an SCC.

[0021] For example, when the RRC signaling includes the configuration of the NZP CSI-RS resources corresponding to the first CC and the CC list, the RRC signaling does not need to include the configuration of the NZP CSI-RS resources corresponding to each CC in the CC list. In other words, it is no longer necessary to configure NZP CSI-RS resources for each CC in the CC list in the RRC signaling, that is, the NZP CSI-RS resource configuration information on each CC in the CC list is deleted in the RRC, achieving a configuration-free effect.

[0022] For example, NZP CSI-RS resources or CSI-IM resources can be configured for each CC in the "CSI-MeasConfig" in the RRC signaling, and the identifier of the first CC is located in the NZP CSI-RS resource configuration part or CSI-IM resource part in the "CSI-MeasConfig" field corresponding to the second CC.

[0023] Optionally, if it is an NZP CSI-RS resource configuration for mobility management, the identifier of the first CC can be added to the "CSI-RS-ResourceConfigMobility" part corresponding to the second CC in the RRC signaling. If it is a ZP CSI-RS resource configuration, the identifier of the first CC can be added to the "PDSCH-Config IE" part corresponding to the second CC in the RRC signaling. In this way, the RRC signaling does not need to include the NZP CSI-RS resource configuration or ZP CSI-RS resource configuration for mobility management corresponding to the second CC, and can also reduce the length (overhead) of the RRC signaling, solve the problem of the large length (large overhead) of the RRC signaling, and reduce the consumption of communication resources by RRC.

[0024] In a third aspect, a method for transmitting RRC signaling is provided. The execution subject of the method may be a terminal device, or a chip, chip system, or processor that supports the terminal device to implement the method. The method includes: receiving RRC signaling, the RRC signaling including a CSI-RS resource configuration corresponding to a first CC and indication information, the indication information being used to indicate that the CSI-RS resource configuration corresponding to the first CC is the same as the CSI-RS resource configuration corresponding to at least one CC, and that the first CC and the at least one CC are both carriers serving the terminal device; and determining, based on the RRC signaling, the CSI-RS resource configuration corresponding to the at least one CC. The RRC signaling does not include the CSI-RS resource configuration corresponding to the at least one CC.

[0025] The third aspect provides a method for transmitting RRC signaling. In a carrier aggregation scenario, if the CSI-RS resource configuration on the first CC is the same as the CSI-RS resource configuration of other carriers, indication information (e.g., a CC list) can be added to the portion of the CSI-RS resource configuration on the first carrier in the RRC signaling to indicate that the CSI-RS resource configuration of the first carrier is the same as the CSI-RS resource configuration of the CC in the CC list. In this way, the RRC signaling does not need to include the configuration content of the CSI-RS resources on other carriers. This reduces the length (overhead) of the RRC signaling, solves the problem of large length (large overhead) of the RRC signaling, and reduces the consumption of communication resources by RRC.

[0026] In a possible implementation manner of the third aspect, the indication information includes a CC list, and the CC list includes an identifier corresponding to at least one CC.

[0027] In a possible implementation manner of the third aspect, the CSI-RS resource configuration includes: at least one of: NZP CSI-RS resource configuration or CSI-IM resource configuration.

[0028] In a possible implementation of the third aspect, the first CC is a PCC, and the at least one CC is an SCC.

[0029] In a possible implementation manner of the third aspect, the indication information is located in the NZP CSI-RS resource configuration part in the "CSI-MeasConfig" field corresponding to the first CC.

[0030] The technical effects corresponding to any possible implementation method in the third aspect can be referred to the technical effects corresponding to any possible implementation method in the first aspect mentioned above, and will not be repeated here.

[0031] In a fourth aspect, a method for RRC signaling transmission is provided. The execution subject of the method can be a terminal device, or a chip, chip system, or processor that supports the terminal device to implement the method. The method includes: receiving RRC signaling, the RRC signaling includes a CSI-RS resource configuration corresponding to a first CC, and the CSI-RS resource configuration portion of the second CC in the RRC signaling includes an identifier of the first CC, and the identifier of the first CC is used to indicate that the CSI-RS resource configuration corresponding to the second CC is the same as the CSI-RS resource configuration corresponding to the first CC; determining the CSI-RS resource configuration corresponding to the second CC according to the RRC signaling. The CSI-RS resource configuration portion of the second CC in the RRC signaling does not include the CSI-RS resource configuration corresponding to the second CC.

[0032] The fourth aspect provides a method for transmitting RRC signaling. In a carrier aggregation scenario, if the CSI-RS resource configuration on a certain carrier (e.g., a first CC) is the same as the CSI-RS resource configuration on another carrier (a second CC), the identifier of the first CC can be added to the portion of the RRC signaling that configures the CSI-RS resources on the second carrier. The identifier of the first CC is used to indicate that the CSI-RS resource configuration corresponding to the second CC is the same as the CSI-RS resource configuration corresponding to the first CC. The RRC does not need to include specific configuration information for the CSI-RS resources on the second CC, thereby reducing the length (overhead) of the RRC signaling, solving the problem of large RRC signaling length (large overhead), and reducing the consumption of communication resources by the RRC.

[0033] In a possible implementation manner of the fourth aspect, the CSI-RS resource configuration includes: at least one of: NZP CSI-RS resource configuration or CSI-IM resource configuration.

[0034] In a possible implementation of the fourth aspect, the first CC is a PCC or an SCC, and the second CC is an SCC.

[0035] In a possible implementation manner of the fourth aspect, the identifier of the first CC is located in the NZP CSI-RS resource configuration part of the "CSI-MeasConfig" field corresponding to the second CC.

[0036] The technical effects corresponding to any possible implementation method in the fourth aspect can be referred to the technical effects corresponding to any possible implementation method in the above-mentioned second aspect, and will not be repeated here.

[0037] In a fifth aspect, a communication device is provided, comprising: a module (e.g., a processing module and an interface module) for performing each step in the first aspect or any possible implementation of the first aspect, or a module (e.g., a processing module and an interface module) for performing each step in the second aspect or any possible implementation of the second aspect. The device may be a network device, a chip, a chip system, or a processor in a network device, or a logical node, logic module, or software that implements all or part of the network device's functions.

[0038] In a sixth aspect, a communication device is provided, comprising at least one processor and memory, wherein the at least one processor is configured to execute: the method of the first aspect or any possible implementation of the first aspect, or the method of the second aspect or any possible implementation of the second aspect. The device may be a network device, a chip, a chip system, or a processor in a network device, or a logical node, a logical module, or software that implements all or part of the network device's functions.

[0039] In a seventh aspect, a communication device is provided, comprising at least one processor and an interface circuit, wherein the at least one processor is configured to execute: the method of the first aspect or any possible implementation of the first aspect, or the method of the second aspect or any possible implementation of the second aspect. The device may be a network device, a chip, a chip system, or a processor in a network device, or a logical node, a logical module, or software capable of implementing all or part of the network device's functions.

[0040] In an eighth aspect, a communication device is provided, comprising: a module (e.g., a processing module and an interface module) for performing each step in the third aspect or any possible implementation of the third aspect, or a module (e.g., a processing module and an interface module) for performing each step in the fourth aspect or any possible implementation of the fourth aspect. The device may be a terminal device, or a chip, a chip system, or a processor in the terminal device.

[0041] In a ninth aspect, a communications device is provided, comprising at least one processor and memory, wherein the at least one processor is configured to execute: the method in the third aspect or any possible implementation of the third aspect, or the method in the fourth aspect or any possible implementation of the fourth aspect. The device may be a terminal device, or may be a chip, chip system, or processor in the terminal device.

[0042] In a tenth aspect, a communication device is provided, comprising at least one processor and an interface circuit, wherein the at least one processor is configured to execute: the method in the third aspect or any possible implementation of the third aspect, or the method in the fourth aspect or any possible implementation of the fourth aspect. The device may be a terminal device, or may be a chip, chip system, or processor in the terminal device.

[0043] In the eleventh aspect, a network device is provided, which includes the communication device provided in the fifth aspect, or the network device includes the communication device provided in the sixth aspect, or the network device includes the communication device provided in the seventh aspect.

[0044] In the twelfth aspect, a terminal device is provided, which includes the communication device provided in the eighth aspect, or the terminal device includes the communication device provided in the ninth aspect, or the terminal device includes the communication device provided in the tenth aspect.

[0045] In the thirteenth aspect, a computer program product is provided, which includes a computer program, which, when executed by a processor, is used to execute: the method in the first aspect or any possible implementation of the first aspect, the method in the second aspect or any possible implementation of the second aspect, the method in the third aspect or any possible implementation of the third aspect, or the method in the fourth aspect or any possible implementation of the fourth aspect.

[0046] In the fourteenth aspect, a computer-readable storage medium is provided, which stores a computer program. When the computer program is executed, it is used to execute: the method in the first aspect or any possible implementation of the first aspect, or the method in the second aspect or any possible implementation of the second aspect, the method in the third aspect or any possible implementation of the third aspect, or the method in the fourth aspect or any possible implementation of the fourth aspect.

[0047] In the fifteenth aspect, a chip is provided, which includes: a processor for calling and running a computer program from a memory, so that a communication device equipped with the chip executes: the method in the first aspect or any possible implementation of the first aspect, the method in the second aspect or any possible implementation of the second aspect, the method in the third aspect or any possible implementation of the third aspect, or the method in the fourth aspect or any possible implementation of the fourth aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0048] FIG1 is a schematic diagram of an example of a communication scenario applicable to the method provided in the present application, provided in an embodiment of the present application.

[0049] FIG2 is a schematic diagram of another communication scenario applicable to the method provided in the present application, provided in an embodiment of the present application.

[0050] Figure 3 is a schematic diagram of a gNB architecture provided in an embodiment of the present application.

[0051] FIG4 is a schematic diagram of a wireless access network device (ie, a network device) provided in an embodiment of the present application.

[0052] FIG5 is a schematic diagram of a user plane protocol layer structure between a network device and a terminal device provided in an embodiment of the present application.

[0053] Figure 6 is a schematic diagram of the control plane (or signaling plane) protocol layer structure between a terminal device and a network device provided in an embodiment of the present application.

[0054] Figure 7 is a schematic flowchart of an example of an RRC signaling transmission method provided in an embodiment of the present application.

[0055] FIG8 is a schematic diagram of an example of NZP CSI-RS resource (NZP CSI-RS-Resource) configuration of a first CC provided in an embodiment of the present application.

[0056] FIG9 is a schematic diagram of an example of adding an SCC list (scc_List SEQUENCE) under the NZP CSI-RS resource of the first CC provided by an embodiment of the present application.

[0057] Figure 10 is a schematic flowchart of another example of an RRC signaling transmission method provided in an embodiment of the present application.

[0058] FIG11 is a schematic block diagram of a communication device according to an embodiment of the present application.

[0059] FIG12 is a schematic block diagram of another communication device provided in an embodiment of the present application.

[0060] FIG13 is a schematic block diagram of a communication device provided in an embodiment of the present application.

[0061] FIG14 is a schematic block diagram of another communication device provided in an embodiment of the present application.

[0062] Figure 15 is a schematic block diagram of a terminal device provided in an embodiment of the present application.

[0063] Figure 16 is a schematic block diagram of a network device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0064] The technical solution in this application will be described below with reference to the accompanying drawings.

[0065] In the description of the embodiments of this application, unless otherwise specified, " / " represents or. For example, A / B can represent A or B. "And / or" in this article is simply a description of the association relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, in the description of the embodiments of this application, "plurality" means two or more than two.

[0066] In the following, the terms "first" and "second" are used for descriptive purposes only and should not be understood to indicate or imply relative importance or implicitly specify the number of the technical features indicated. Therefore, a feature defined as "first" or "second" may explicitly or implicitly include one or more of the features. In the description of this embodiment, unless otherwise specified, "plurality" means two or more.

[0067] In an embodiment of the present application, a terminal device or a network device includes a hardware layer, an operating system layer running on the hardware layer, and an application layer running on the operating system layer. The hardware layer includes hardware such as a central processing unit (CPU), a memory management unit (MMU), and memory (also called main memory). The operating system can be any one or more computer operating systems that implement business processing through processes, such as a Linux operating system, a Unix operating system, an Android operating system, an iOS operating system, or a Windows operating system. The application layer includes applications such as browsers, address books, word processing software, and instant messaging software. In addition, the embodiment of the present application does not specifically limit the specific structure of the execution subject of the method provided in the embodiment of the present application. As long as it is possible to communicate according to the method provided in the embodiment of the present application by running a program that records the code of the method provided in the embodiment of the present application, for example, the execution subject of the method provided in the embodiment of the present application can be a terminal device or a network device, or a functional module in the terminal device or the network device that can call a program and execute the program.

[0068] In addition, various aspects or features of the present application can be implemented as methods, devices or products using standard programming and / or engineering techniques. The term "product" as used in this application covers computer programs that can be accessed from any computer-readable device, carrier or medium. For example, computer-readable media may include, but are not limited to: magnetic storage devices (e.g., hard disks, floppy disks or magnetic tapes, etc.), optical disks (e.g., compact discs (CDs), digital versatile discs (DVDs), etc.), smart cards and flash memory devices (e.g., erasable programmable read-only memories (EPROMs), cards, sticks or key drives, etc.). In addition, the various storage media described herein may represent one or more devices and / or other machine-readable media for storing information. The term "machine-readable medium" may include, but is not limited to, wireless channels and various other media capable of storing, containing and / or carrying instructions and / or data.

[0069] New Radio (NR) is a new radio access technology (RAT) developed by the 3rd Generation Partnership Project (3GPP) for fifth-generation mobile communication networks (5G). It is the global standard for the air interface of 5G networks. 3GPP specifications define the technical details of NR. 5G communication systems operate in two networking modes: non-standalone (NSA) and standalone (SA).

[0070] In SA scenarios, the NR protocol specifies that the maximum size of a packet data convergence protocol (PDCP) service data unit (PDCP SDU) is 9000 bytes. In NSA scenarios, the Long Term Evolution (LTE) protocol specifies that the maximum size of a PDCP SDU is 8188 bytes.

[0071] To further increase transmission rates, the protocol currently supports CA technology, which aggregates multiple CCs for data transmission, thereby increasing bandwidth and data rates. CA technologies include intra-band continuous CA, intra-band discontinuous CA, and inter-band CA. Intra-band continuous CA and intra-band discontinuous CA are collectively referred to as intra-band CA, while inter-band CA is also referred to as multi-band CA.

[0072] Currently, 5G specifies two frequency bands: Frequency range 1 (FR1) and Frequency range 2 (FR2). FR1 refers to the sub-6 GHz frequency band, covering the range of 450 MHz to 7125 MHz. The FR2 operating frequency band is between 24.25 GHz and 52.6 GHz, which is the millimeter wave band. In R17 and earlier protocol versions, for FR2, same-frequency CA can reach 800 MHz. Multi-frequency CA in FR1 and FR2 can support bandwidth greater than 800 MHz. For CA, the number of CCs included can be 9 CCs. In R18 and later protocol versions, the number of CCs included for CA can be 10 CCs.

[0073] The channel state information-reference signal (CSI-RS) is a very important reference signal in 5G. CSI-RS is mainly used in the following aspects:

[0074] Acquiring channel state information: used to measure the channel between the base station and the terminal device and obtain the channel state information required for scheduling and link adaptation, such as precoding matrix and channel quality information;

[0075] Beam management: used to obtain the shaping weights of the beams on the terminal device and base station side, and supports beam measurement during the beam management process;

[0076] Time-frequency tracking: Used for accurate time-frequency synchronization tracking and obtaining Quasi Co-Location (QCL) parameters. In this context, CSI-RS can also be called Tracking Reference Signal (TRS).

[0077] Mobility management: used to complete mobility management related measurements;

[0078] Interference measurement: CSI-RS can also be used for interference measurement (IM). In this case, CSI-RS can also be called CSI IM.

[0079] Rate matching: used for rate matching of the physical downlink share channel (PDCCH).

[0080] CSI-RS can be divided into non-zero power CSI-RS (NZP CSI-RS) and zero-power CSI-RS (ZP CSI-RS). NZP CSI-RS is mainly used for time / frequency tracking, CSI computation, L1 reference signal receiving power (L1 RSRP) calculation (L1-RSRP calculation), L1 signal to interference plus noise ratio (L1 SINR calculation), and mobility management. L1 RSRP and L1-SINR can be used for beam management. ZP CSI-RS is mainly used for rate matching of the physical downlink shared channel (PDCCH). The protocol defines the time-frequency resource sets for NZP CSI-RS and ZP CSI-RS.

[0081] For example, Table 1 is a schematic table showing the specific contents and functions of a CSI-RS.

[0082] Table 1

[0083] Currently, terminal devices can access multiple carriers using CA, and multiple carriers can be divided into primary carrier component (PCC) and secondary carrier component (SCC). Generally, the cell serving the terminal (serving cell) may include a primary cell (PCell) and one or more secondary cells (Scell). The PCell may be determined during the initial connection establishment (connection establishment) or reconnection process. The PCell works on the PCC. The Scell ​​is a cell added through RRC reconfiguration, providing additional frequency band resources, and one Scell ​​works on one SCC. The terminal device will only initiate a random access process on the PCC, and the PCC is always in an activated state, while the SCC can be added / modified / released through the RRC connection reconfiguration message (RRC ConnectionReconfiguration). Each CC corresponds to a cell.

[0084] For each CC (including a PCC and one or more SCCs) accessed by a terminal device, the base station is required to configure CSI-RS resources and CSI-RS time domain behavior for that CC using RRC signaling. For example, CSI-RS time domain behavior includes periodic, semi-static, and aperiodic.

[0085] For NZP CSI-RS, in addition to the NZP CSI-RS used for mobility management, the NZP CSI-RS used for time / frequency tracking, CSI computation, L1-RSRP calculation, and L1-SINR calculation, as well as the CSI-RS resources used for CSI-IM, are all configured through the CSI measurement configuration information element (CSI-MeasConfig IE) in RRC. Each CSI measurement configuration information element (CSI-MeasConfig IE) includes: one or more NZP CSI-RS resources (NZP CSI-RS Resource), one or more CSI-IM resources (CSI-IM-Resource), or one or more System Synchronization Signal Block (SSB) resources (CSI-SSB-Resource). Among them, SSB is used for beam management. In other words, the CSI measurement configuration information element (CSI-MeasConfig IE) indicates the time-frequency resources of the NZP CSI-RS and the time-frequency resources of the CSI-IM for the above purposes.

[0086] In summary, for each CC, the network device (such as a base station) needs to configure at least one of the time-frequency resources of the NZP CSI-RS or the time-frequency resources of the CSI-IM on the CC to the terminal device through the CSI measurement configuration information unit (CSI-MeasConfig IE) in the RRC signaling. Since a terminal may access multiple CCs through CA, as the number of CCs and bandwidth continues to increase, the RRC signaling needs to configure the NZP CSI-RS resources or CSI-IM time-frequency resources corresponding to each CC in these multiple CCs, resulting in an increase in the overhead (or length) of the RRC signaling, requiring more communication resources to transmit the RRC, and increasing the consumption of communication resources.

[0087] Currently, RRC segmentation technology has been proposed to reduce the length of RRC signaling. For example, when the length of an RRC signaling exceeds the maximum limit of the PDCP SDU (for example, 9000 bytes or 8188 bytes), the RRC signaling can be divided into multiple segments or multiple fragments at the RRC layer, and each segment is transmitted using a separate RRC PDU. The receiving device reassembles the multiple segments received to obtain the complete RRC signaling. All segments of an RRC signaling need to be sent before another RRC signaling is sent. RRC segmentation supports both uplink and downlink.

[0088] However, RRC segmentation technology cannot fundamentally solve the problem of high RRC signaling overhead. For example, in a scenario where a base station uses RRC signaling to configure NZP CSI-RS resources and CSI-IM resources corresponding to each of multiple CCs for a terminal device, since the terminal device may access many CCs, the length of the RRC signaling is relatively long. Even if RRC segmentation technology is used, the number of fragments needs to be continuously expanded, and the splitting, transmission, and reassembly of the RRC signaling will bring performance and reliability issues. This reduces the reliability of RRC signaling transmission and cannot solve the problem of large RRC signaling length (high overhead).

[0089] In view of this, the present application provides a method and communication device for RRC signaling transmission. In a carrier aggregation scenario, if the CSI-RS resource configuration of a carrier (for example, a first carrier) is the same as the CSI-RS resource configuration of other carriers, in the RRC signaling, indication information can be added to the CSI-RS resource configuration part of the first carrier, and the indication information indicates that the CSI-RS resource configuration of the first carrier is the same as the CSI-RS resource configuration corresponding to other CCs. The RRC may not include the configuration information of the CSI-RS resources on other carriers (corresponding to other carriers); alternatively, the identifier of the first carrier may be added to the CSI-RS resource configuration part of other carriers in the RRC, and the RRC may not include the specific configuration information of the CSI-RS resources on other carriers, thereby reducing the length (overhead) of the RRC signaling, solving the problem of the large length (large overhead) of the RRC signaling, and reducing the consumption of communication resources by the RRC.

[0090] It can be understood that the method provided in this application can be applied in the scenario of carrier aggregation.

[0091] For example, Figure 1 shows a schematic diagram of a communication scenario applicable to the method provided in this application. As shown in Figure 1, communication is performed between a terminal device and a network device. Through CA, the terminal device can communicate with the network device separately on multiple CCs (3 CCs shown in Figure 1). Among the multiple CCs, one is a PCC and the others are SCCs. The terminal device can communicate with the network device through these CCs (including PCC and SCC). When the network device uses RRC to configure NZP CSI-RS resources and CSI-IM resources for each CC, the RRC signaling transmission method provided in this application can be used.

[0092] For another example, Figure 2 shows a schematic diagram of another communication scenario applicable to the method provided in this application. As shown in Figure 2, communication is performed between a terminal device and two network devices. The two network devices can be network devices of different standards (for example, a 4G base station and a 5G base station). Both the 4G base station and the 5G base station are connected to the 4G core network. The communication scenario shown in Figure 2 is a dual connection (DC) communication scenario under the NSA architecture. On the basis of the dual connection, the 4G part and the 5G part can each perform carrier aggregation within them. Under dual connection, the mobile phone simultaneously accesses the 4G base station and the 5G base station.

[0093] For example, in the Option 3 series architecture of non-independent networking, the 4G base station serves as the control plane anchor point, referred to as the master node (Master Node), and the 5G base station is referred to as the secondary node (Secondary Node). Both the master node and the secondary node can perform carrier aggregation. Optionally, the main carrier and the secondary carrier of the master node can also be referred to as Pcell and Scell, and the main carrier and the secondary carrier of the secondary node can be referred to as PScell ​​and Scell. The master node and the secondary node with carrier aggregation can also be referred to as MCG (Master Cell Group) and SCG (Secondary Cell Group). When the network device uses RRC to configure NZP CSI-RS resources and CSI-IM resources for each CC, the RRC signaling transmission method provided in this application can be used.

[0094] It should be understood that the communication scenarios (communication systems) shown in Figures 1 or 2 are merely exemplary and should not impose any limitations on the communication scenarios applicable to the embodiments of the present application. For example, the communication system shown in Figures 1 or 2 may also include more or smaller network nodes, such as terminal devices or network devices. Or the number of aggregated CCs between the terminal device and the network device may be greater. It is understood that the method provided in the present application can be applied to any carrier aggregation scenario.

[0095] Exemplarily, the communication system shown in Figure 1 or Figure 2 can be a cellular system related to the Third Generation Partnership Project (3GPP), such as an LTE system, an LTE frequency division duplex (FDD) system, an LTE time division duplex (TDD), a Universal Mobile Telecommunication System (UMTS), a Worldwide Interoperability for Microwave Access (WiMAX) communication system, a 4G, 5G mobile communication system (including independent networking and non-independent networking), NR, or a future-oriented evolution system (such as a 6G mobile communication system), or an open access network (open RAN, O-RAN or ORAN), a cloud radio access network (CRAN), or a wireless fidelity (WiFi) system, or a communication system that integrates two or more of the above systems. The embodiments of the present application are not limited here.

[0096] Optionally, in an embodiment of the present application, the network device may also be referred to as: access network device, wireless access network device, wireless access network (RAN) node, RAN entity or access node, etc., constituting a part of the communication system to help terminal devices achieve wireless access.

[0097] In one possible scenario, a network device can be any device with wireless transceiver capabilities. Examples include: traditional macro base stations (evolved node B, eNBs) in traditional Universal Mobile Telecommunications Systems (UMTS) and LTE communication systems; micro base stations (eNBs) in heterogeneous networks (HetNets); baseband processing units (BBUs) and remote radio units (RRUs) in distributed base station scenarios; baseband pool (BBU pool) RRUs in cloud radio access networks (CRANs); gNBs in future wireless communication systems, 3GPP-derived base stations, access nodes in WiFi systems, wireless relay nodes, wireless backhaul nodes, etc. For example, a base station can be: a macro base station, a micro base station, a pico base station, a small cell, a relay station, or a balloon station.

[0098] In another possible scenario, the network device may be a base station, an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP), a next-generation base station in a sixth-generation (6G) mobile communication system, a base station in a future mobile communication system, etc. Optionally, the network device may also be a relay node or a host node, or a wireless controller in a CRAN scenario. Optionally, the network device may also be an access network device in V2X technology, such as a road side unit (RSU). All or part of the functions of the network device in this application may also be implemented by software functions running on hardware, or by virtualization functions instantiated on a platform (such as a cloud platform). The network device in this application may also be a logical node, logical module or software that can implement all or part of the functions of a wireless access network device.

[0099] In NR technology, a network device (e.g., gNB) can consist of a gNB Centralized Unit (CU) and one or more gNB Distributed Units (DU). The gNB-CU and gNB-DU are different logical nodes and can be deployed on different physical devices or on the same physical device.

[0100] Considering a separate control plane and user plane architecture, the gNB-CU can be further divided into a Centralized Unit-Control Plane (CU-CP) entity (also known as a CU-CP node) and a Centralized Unit-User Plane (CU-UP) entity (also known as a CU-UP node). The gNB-CU-CP is a control plane entity responsible for signaling control, while the gNB-CU-UP is a user plane entity responsible for data transmission for terminal devices. The gNB-CU-CP and gNB-CU-UP are connected via the E1 interface, the gNB-CU-CP and gNB-DU are connected via the F1-C interface, and the gNB-CU-UP and gNB-DU are connected via the F1-U interface. Figure 3 shows the architecture with separate gNB-CU-CP and gNB-CU-UP.

[0101] The architecture shown in Figure 3 also has the following characteristics:

[0102] A gNB consists of one gNB-CU-CP, multiple gNB-CU-UPs, and multiple gNB-DUs.

[0103] A DU can only connect to one gNB-CU-CP;

[0104] A CU-UP can only connect to one gNB-CU-CP;

[0105] A DU can be connected to multiple gNB-CU-UPs under the control of the same CU-CP;

[0106] A CU-UP can be connected to multiple gNB-DUs under the control of the same CU-CP.

[0107] It should be understood that Figure 3 is merely illustrative and does not limit the gNB architecture. For example, in a CU-DU separation or CP-UP separation architecture, a gNB may include only one gNB-CU-UP, one gNB-CU-CP, and one gNB-DU, or may include more gNB-CU-UPs and gNB-DUs. This application does not impose any limitations on this.

[0108] For example, Figure 4 shows another schematic diagram of a wireless access network device (i.e., a network device). As shown in Figure 4, the wireless access network device includes one or more CUs, one or more DUs, and one or more radio units (RUs). For clarity, Figure 4 shows only one CU, DU, and RU. The CU is used to connect to the core network and one or more DUs. Optionally, the CU can have some of the functions of the core network. The CU can include a CU-CP and a CU-UP.

[0109] In different systems, CU (or CU-CP and CU-UP), DU or RU may also have different names, but those skilled in the art can understand their meanings. For example, in the ORAN system, CU may also be called O-CU (Open CU), DU may also be called O-DU, CU-CP may also be called O-CU-CP, CU-UP may also be called O-CU-UP, and RU may also be called O-RU. For the convenience of description, this application uses CU, CU-CP, CU-UP, DU and RU as examples for description. Any unit of CU (or CU-CP, CU-UP), DU and RU in this application can be implemented by a software module, a hardware module, or a combination of a software module and a hardware module.

[0110] In one possible scenario, for example, the network device may be the aforementioned CU, DU, CU-CP, or CU-UP. The CU and DU may be configured separately or included in the same network element, such as a BBU. The RU may be included in a radio frequency device or radio frequency unit, such as an RRU, an active antenna unit (AAU), or a remote radio head (RRH).

[0111] Optionally, the CU and DU may be configured according to the protocol layer functions of the wireless network they implement: for example, the CU is configured to implement the functions of the packet data convergence protocol (PDCP) layer and the protocol layers above it (for example, the RRC layer and / or the service data adaptation protocol (SDAP) layer, etc.); the DU is configured to implement the functions of the protocol layers below the PDCP layer (for example, the radio link control (RLC) layer, the media access control (MAC) layer, and / or the physical (PHY) layer, etc.). For another example, the CU is configured to implement the functions of the protocol layers above the PDCP layer (such as the RRC layer and / or the SDAP layer), and the DU is configured to implement the functions of the PDCP layer and the protocol layers below it (for example, the RLC layer, the MAC layer, and / or the PHY layer, etc.).

[0112] When a CU includes a CU-CP and a CU-UP, the CU-CP is used to implement the control plane functions of the CU, and the CU-UP is used to implement the user plane functions of the CU. For example, when the CU is configured to implement the functions of the PDCP layer, RRC layer, and SDAP layer, the CU-CP is used to implement the RRC layer functions and the control plane functions of the PDCP layer, and the CU-UP is used to implement the SDAP layer functions and the user plane functions of the PDCP layer.

[0113] The CU-CP can interact with network elements in the core network that implement control plane functions. The network elements in the core network that implement control plane functions can be access and mobility function network elements, such as the access and mobility management function (AMF) network element in the 5G system. The access and mobility function network element is responsible for mobility management in the mobile network, such as location update of terminal devices, registration network of terminal devices, and switching of terminal devices.

[0114] The CU-UP can interact with network elements in the core network that implement user plane functions. Network elements in the core network that implement user plane functions, such as the user plane function (UPF) in the 5G system, are responsible for forwarding and receiving data in terminal devices.

[0115] The above configuration of CU and DU is only an example, and the functions of CU and DU can also be configured as needed. For example, the CU or DU can be configured to have the functions of more protocol layers, or the CU or DU can be configured to have partial processing functions of the protocol layer. For example, some functions of the RLC layer and the functions of the protocol layers above the RLC layer are set in the CU, and the remaining functions of the RLC layer and the functions of the protocol layers below the RLC layer are set in the DU. For another example, the functions of the CU or DU can be divided according to the service type or other system requirements, such as by delay, and the functions whose processing time needs to meet the smaller delay requirement are set in the DU, and the functions that do not need to meet the delay requirement are set in the CU.

[0116] The DU and RU can work together to implement the functions of the PHY layer. A DU can be connected to one or more RUs. The functions of the DU and RU can be configured in various ways according to the design. For example, the DU is configured to implement the baseband function, and the RU is configured to implement the mid-RF function. For another example, the DU is configured to implement the high-layer functions in the PHY layer, and the RU is configured to implement the low-layer functions in the PHY layer or to implement the low-layer functions and the RF functions. The high-layer functions in the physical layer may include a part of the functions of the physical layer, which is closer to the MAC layer, and the low-layer functions in the physical layer may include another part of the functions of the physical layer, which is closer to the mid-RF side.

[0117] In the embodiments of the present application, the terminal device may also be referred to as a terminal, user equipment (UE), mobile station, mobile terminal, etc. The terminal can be widely used in various scenarios, such as D2D, V2X communication, machine-type communication (MTC), Internet of Things (IOT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grid, smart furniture, smart office, smart wearable, smart transportation, smart city, etc. The terminal can be a mobile phone, tablet computer, computer with wireless transceiver function, wearable device, vehicle, drone, helicopter, airplane, ship, robot, robotic arm, smart home device, etc. The embodiments of the present application do not limit the device form of the terminal.

[0118] The following is an exemplary description of the protocol stack structure between the terminal device and the network device.

[0119] Figure 5 shows a schematic diagram of the user plane protocol layer structure between a network device and a terminal device. As shown in Figure 5, the user plane protocol layer structure may include protocol layer functions such as the PDCP layer, RLC layer, MAC layer, and PHY layer. The physical layer is located at the lowest layer (Layer 1), the MAC layer, RLC, and PDCP belong to the second layer (Layer 2), and RRC belongs to the third layer (Layer 3). Optionally, an SDAP layer may also be included above the PDCP layer.

[0120] FIG6 is a schematic diagram showing an example of a control plane (or signaling plane) protocol layer structure between a terminal device and a network device.

[0121] As shown in Figure 6, the control plane protocol layer structure of the terminal device and the network device may include the functions of the protocol layers such as the RRC layer, PDCP layer, RLC layer, MAC layer and PHY layer. Among them, the RRC layer, PDCP layer, RLC layer, MAC layer and PHY layer can be collectively referred to as the access stratum (AS). Above the RRC layer, the non-access stratum (NAS) protocol may also exist in the terminal device. The NAS layer in the terminal device and the NAS layer in the access and mobility management function (AMF) of the core network device communicate through the network device. Exemplarily, the main functions of the NAS layer include: supporting general processes of terminal device mobility such as authentication, authorization, general terminal device configuration update and security control mode process; supporting session management processes to establish and maintain data connections between terminal devices and data networks, etc.

[0122] It should be understood that the structure of the protocol stack shown in Figures 5 and 6 is merely exemplary, and the functions or roles of each protocol layer are also exemplary descriptions and should not impose any restrictions on the functions of the protocol stack or protocol layer of the terminal device and network device provided in the embodiments of the present application.

[0123] The following describes the RRC signaling transmission method provided by this application with reference to specific examples.

[0124] It should be understood that in the embodiments of the present application, the method is described by taking a network device and a terminal device as the execution subject of the execution method as an example. As an example and not a limitation, the terminal device in the present application may also be a chip, a chip system, or a processor that supports the terminal device to implement the method. The embodiments of the present application are not limited here. The network device in the present application may also be a chip, a chip system, or a processor that supports the network device to implement the method, or it may also be a logical node, a logical module, or software that can implement all or part of the network device functions.

[0125] The method provided in the present application is described in detail below in conjunction with Figure 7. Figure 7 is a schematic flowchart of a method for RRC signaling transmission in an embodiment of the present application. This method 700 can be applied to the scenarios or communication architectures shown in Figure 1 or Figure 2, and of course can also be applied to other carrier aggregation communication scenarios or communication architectures. The embodiments of the present application are not limited here.

[0126] As shown in Figure 7 , the method 700 shown in Figure 7 may include steps S710 to S720 . The following describes each step in the method 700 in detail with reference to Figure 7 .

[0127] S710. A network device sends RRC signaling to a terminal device. The RRC signaling includes a CSI-RS resource configuration corresponding to a first CC and indication information. The indication information is used to indicate that the CSI-RS resource configuration corresponding to the first CC is the same as the CSI-RS resource configuration corresponding to at least one CC. The CSI-RS resource configuration includes at least one of an NZP CSI-RS resource configuration or a CSI-IM resource configuration.

[0128] Correspondingly, the terminal device receives the RRC signaling.

[0129] Optionally, in an embodiment of the present application, the NZP CSI-RS may be used for time / frequency tracking, CSI computation, L1-RSRP calculation, L1-SINR calculation, etc. For example, when the ZP CSI-RS is used for time / frequency tracking, the NZP CSI-RS may be a TRS.

[0130] Of course, in the embodiment of the present application, NZP CSI-RS can also be used for mobility management.

[0131] For ease of explanation, the following examples are based on NZP CSI-RS resource configuration for time / frequency tracking, CSI computation, L1-RSRP calculation, and L1-SINR calculation.

[0132] For ease of understanding, the following examples use the CC list as an example to illustrate the indication information.

[0133] In an embodiment of the present application, the CC list includes an identifier of at least one CC, and the configuration of the NZP CSI-RS resources corresponding to each CC in the CC list is the same as the configuration of the NZP CSI-RS resources corresponding to the first CC (or on the first CC). By indicating the CC list in RRC signaling, it is possible to more accurately indicate which CCs have the same NZP CSI-RS resource configuration as the first CC. This improves the accuracy of the indication information, facilitates implementation, and reduces the overhead of the indication information.

[0134] For example, in some possible implementations, in scenarios such as cell (cell may also be referred to as carrier) switching, cell reconfiguration, cell addition, cell reconstruction, and cell awakening from an inactive state to an active state, the network device needs to configure NZP CSI-RS resources for each CC or each cell through RRC signaling. For example, the network device may configure NZP CSI-RS resources for each CC through the "CSI-MeasConfig IE" in the RRC signaling.

[0135] Optionally, the first CC may be a PCC, and each CC in the CC list may be an SCC.

[0136] Of course, in other implementations of the present application, the first CC may also be an SCC, and each CC in the CC list may also be an SCC.

[0137] It should be understood that in an embodiment of the present application, the terminal device communicates with the network device through carrier aggregation, that is, the terminal device can communicate with the network device separately on multiple CCs, and the multiple CCs include the first CC and the CCs included in the CC list, and the multiple CCs are CCs or cells serving the terminal device.

[0138] In an embodiment of the present application, if the configuration of the NZP CSI-RS resources corresponding to at least some of the multiple CCs is the same as the configuration of the NZP CSI-RS resources corresponding to the first CC, the identifiers of these at least some CCs can be combined into a CC list.

[0139] For example, assume that a terminal device communicates with a network device on M CCs, where the first CC can be a PCC and the other CCs are SCCs. If the configuration of the NZP CSI-RS resources corresponding to the remaining N CCs, excluding the first CC, is the same as the configuration of the NZP CSI-RS resources corresponding to the first CC, the CC list includes the identifiers corresponding to these N CCs.

[0140] It should also be understood that in the embodiment of the present application, when the RRC signaling includes the configuration of the NZP CSI-RS resource corresponding to the first CC and the CC list, the RRC signaling does not need to include the configuration of the NZP CSI-RS resource corresponding to each CC in the CC list. In other words, it is no longer necessary to configure the NZP CSI-RS resource for each CC in the CC list in the RRC signaling, that is, the NZP CSI-RS resource configuration information on each CC in the CC list is deleted in the RRC, achieving a configuration-free effect.

[0141] For example, assuming that the CC list includes 5 CCs, if according to the existing method, NZP CSI-RS resources need to be configured for these 5 CCs separately in RRC signaling, the RRC signaling needs to include 5 groups of fields (or 5 parts), and each group of fields (or each part) is configured with the NZP CSI-RS resources of one CC. According to the method provided in the embodiment of the present application, it is only necessary to add the CC list after the configuration of the NZP CSI-RS resources corresponding to the first CC. In this way, NZP CSI-RS resources do not need to be configured for these 5 CCs separately in RRC signaling, and these 5 groups of fields (or 5 parts) do not need to be included in the RRC signaling. That is, these 5 groups of fields (or 5 parts) are saved, the length (overhead) of RRC signaling is reduced, the problem of large length (large overhead) of RRC signaling is solved, and the consumption of communication resources by RRC is reduced.

[0142] As a possible implementation, the network device may configure NZP CSI-RS resources for each CC in the "CSI-MeasConfig" in the RRC signaling.

[0143] Exemplarily, the NZP CSI-RS resource (NZP CSI-RS-Resource) configuration of the first CC may include the following eight items (denoted as (1) to (8)):

[0144] (1) Resource Type: The NZP CSI-RS resource of the first CC can be configured as periodic, semi-persistent, or aperiodic.

[0145] (2) NZP CSI-RS-Resource identifier (NZP CSI-RS-ResourceId) of the first CC: indicates the identifier (Identity, ID) of the NZP CSI-RS-Resource;

[0146] (3) Resource Mapping: defines the structure of the NZP CSI-RS on the first CC, including the physical resource blocks (PRBs) occupied in the frequency domain;

[0147] (4) Power Control Offset relative to NZP CSI-RS RE (powerControlOffset): The power offset of the Physical Downlink Shared Channel Resource Element (PDSCH RE) on the first CC relative to the NZP CSI-RS RE. For example, the value range is [-8, 15] dB, with a step size of 1 dB;

[0148] (5) Power offset control relative to SSB RE (powerControlOffsetSS): The power offset of NZP CSI-RS RE on the first CC relative to SSB RE. For example, the value range is {-3dB, 0dB, 3dB, 6dB};

[0149] (6) Scrambling ID: the scrambling ID of the NZP CSI-RS on the first CC;

[0150] (7) Periodicity and slot offset (periodicityAndOffset): The transmission period and slot offset of the periodic or semi-static NZP CSI-RS resources on the first CC;

[0151] (8) Reference to TCI-State (qcl-InfoPeriodicCSI-RS): A reference to the NZP CSI-RS TCI-State on the first CC, indicating the QCL source reference signal (referenceSignal) and the QCL type (qcl-Type).

[0152] Of course, the above-mentioned NZP CSI-RS resource (NZP CSI-RS-Resource) configuration is merely exemplary and should not impose any limitations on the NZP CSI-RS resource configuration in the embodiments of the present application. In other implementations of the present application, the NZP CSI-RS resource configuration may also include other content, which is not limited in the embodiments of the present application.

[0153] It should be understood that for each CC, the specific content of the corresponding NZP CSI-RS resource configuration is the same as the content of the NZP CSI-RS resource configuration of the first CC mentioned above. For example, for the second CC in the CC list, the NZP CSI-RS resource configuration also includes the above-mentioned items (1) to (8), and the second CC is any CC in the CC list.

[0154] The NZP CSI-RS resource configuration corresponding to each CC in the CC list also includes the above configurations and is the same as the various configurations of the NZP CSI-RS resource (NZP CSI-RS-Resource) of the first CC. For example, assuming that the CC list includes a second CC, the resourceType, NZP CSI-RS-ResourceId, resourceMapping, powerControlOffset, powerControlOffsetSS, scramblingID, periodicityAndOffset, qcl-InfoPeriodicCSI-RS, etc. of the second CC are the same as the various configurations corresponding to the first CC.

[0155] For example, the "CSI-MeasConfig" part corresponding to the first CC in the RRC signaling includes: the resource type (resourceType) corresponding to the first CC, the NZP CSI-RS-Resource identifier (NZP CSI-RS-ResourceId), resource mapping (resourceMapping), the power control offset (powerControlOffset) relative to the NZP CSI-RS RE, the power offset control (powerControlOffsetSS) relative to the SSB RE, the scrambling code ID (scrambling ID), the periodicity and time slot offset (periodicity And Offset), and the reference to the TCI-State (qcl-InfoPeriodic CSI-RS). In some possible implementations of the present application, the "CSI-MeasConfig" part corresponding to the first CC may also include a CC list.

[0156] Among them, the "CSI-MeasConfig" part corresponding to each CC in the CC list does not need to include: the resource type (resourceType) corresponding to the CC, NZP CSI-RS-Resource identifier (NZP CSI-RS-ResourceId), resource mapping (resourceMapping), power control offset (powerControlOffset) relative to NZP CSI-RS RE, power offset control relative to SSB RE (powerControlOffsetSS), scrambling code ID (scramblingID), period and time slot offset (periodicityAndOffset), reference to TCI-State (qcl-InfoPeriodicCSI-RS) and other configuration contents.

[0157] Exemplarily, the NZP CSI-RS resource (NZP CSI-RS-Resource) configuration of the first CC may be in the form shown in FIG8 .

[0158] Optionally, a CC list may be indicated under the NZP CSI-RS resource configuration of the first CC, that is, a CC list may be added to the NZP CSI-RS resource configuration part ("CSI-MeasConfig" part) of the first CC. Exemplarily, the form of adding an SCC list (scc_List SEQUENCE) under the NZP CSI-RS resource of the first CC may be as shown in FIG9 . By indicating the CC list under the NZP CSI-RS resource configuration of the first CC (or the NZP CSI-RS resource configuration part), it may be more clearly and accurately indicated that the NZP CSI-RS resource configuration corresponding to each CC in the CC list is the same as the NZP CSI-RS resource configuration of the first CC, thereby improving the accuracy and efficiency of the indication information (i.e., the CC list).

[0159] It should also be understood that “the NZP CSI-RS resource configuration part of the first CC includes a CC list” may also implicitly indicate that the configuration of the NZP CSI-RS resources corresponding to each CC in the CC list is the same as the configuration of the NZP CSI-RS resources corresponding to the first CC. In other words, if the terminal device receives RRC signaling and finds that the NZP CSI-RS resource configuration of the first CC indicates or includes a CC list, the terminal device can determine that the configuration of the NZP CSI-RS resources corresponding to each CC in the CC list is the same as the configuration of the NZP CSI-RS resources corresponding to the first CC. In other words, the network device and the terminal device have the same understanding of “the NZP CSI-RS resources of the first CC indicate or include a CC list”.

[0160] S720: The terminal device determines the CSI-RS resource configuration information of the accessed CC according to the RRC signaling.

[0161] After the terminal device receives the RRC signaling, if the CC that the terminal device needs to access is included in the CC list, the terminal device can determine the CSI-RS resource configuration corresponding to the CC that needs to be accessed (for example, NZP CSI-RS resource configuration for time / frequency tracking (Time / Frequency Tracking), CSI calculation (CSI computation), L1-RSRP calculation, L1-SINR calculation, or CSI-IM resource configuration, etc.) based on the CSI-RS resource configuration corresponding to the first CC. That is, the CSI-RS resource configuration corresponding to the first CC is used as the CSI-RS resource configuration corresponding to the CC that needs to be accessed.

[0162] The RRC signaling transmission method provided in the embodiment of the present application, in the scenario of carrier aggregation, if the NZP CSI-RS resource configuration on a certain carrier (also referred to as the NZP CSI-RS resource configuration corresponding to a certain carrier) is the same as the NZP CSI-RS resource configuration on other carriers, partial indication information (for example, a CC list) of the NZP CSI-RS resource on the first carrier can be configured in the RRC signaling to indicate that the NZP CSI-RS resource configuration on the first carrier is the same as the NZP CSI-RS resource configuration of the CC in the CC list, and the configuration content of the NZP CSI-RS resources on other carriers does not need to be included in the RRC signaling. In other words, the available CC list is indicated under the corresponding NZP resource on the first CC, and the NZP CSI-RS resource configuration in the CSI-MeaConfig on each CC included in the CC list can be set by the first CC on the corresponding resource configuration of the follow CC list. The RRC does not need to include the configuration information of the NZP CSI-RS resources on other carriers (each CC included in the CC list), thereby reducing the length (overhead) of the RRC signaling, solving the problem of the large length (large overhead) of the RRC signaling, and reducing the consumption of communication resources by the RRC.

[0163] Of course, in method 700, the indication information is described using a CC list as an example. It should be understood that in other implementations of the present application, the indication information may also be implemented in other ways, as long as the indication information can be used to indicate that the NZP CSI-RS resource configuration on the first carrier is the same as the NZP CSI-RS resource configuration of certain CCs, and can also indicate the specific CCs. This embodiment of the present application is not limited thereto.

[0164] It should also be understood that while the NZP CSI-RS resource configuration is used as an example above, in other implementations of the present application, the NZP CSI-RS resource configuration in method 700 may also be replaced with CSI-IM resource (CSI-IM-Resource) configuration. In other words, the above-described approach may also be used to configure CSI-IM resources for multiple CCs in RRC. For example, the network device may configure CSI-IM resources for a CC using "CSI-MeasConfig" in RRC signaling.

[0165] It should also be understood that in other implementations of the present application, the method provided in the embodiments of the present application can also be used for NZP CSI-RS resource configuration or ZP CSI-RS resource configuration for mobility management. If it is NZP CSI-RS resource configuration for mobility management, indication information (for example, the above-mentioned CC list) can be added to the "CSI-RS-ResourceConfigMobility" part corresponding to the first CC in the RRC signaling. If it is ZP CSI-RS resource configuration, indication information (for example, the above-mentioned CC list) can be added to the "PDSCH-Config IE" part corresponding to the first CC in the RRC signaling. In this way, the RRC signaling does not need to include the NZP CSI-RS resource configuration or ZP CSI-RS resource configuration for mobility management corresponding to each CC in the CC list, and can also reduce the length (overhead) of the RRC signaling, solve the problem of large length (large overhead) of the RRC signaling, and reduce the consumption of communication resources by RRC.

[0166] FIG10 is a schematic flow chart of a method for RRC signaling transmission according to another embodiment of the present application. As shown in FIG10 , the method 1000 shown in FIG10 may include S1010 to S1020. Each step in the method 1000 will be described in detail below with reference to FIG10 .

[0167] S1010. A network device sends RRC signaling to a terminal device. The RRC signaling includes a CSI-RS resource configuration corresponding to a first CC. The CSI-RS resource configuration portion of the second CC in the RRC signaling includes an identifier of the first CC. The identifier of the first CC is used to indicate that the CSI-RS resource configuration corresponding to the second CC is the same as the CSI-RS resource configuration corresponding to the first CC. The CSI-RS resource configuration includes at least one of an NZP CSI-RS resource configuration or a CSI-IM resource configuration.

[0168] Correspondingly, the terminal device receives the RRC signaling.

[0169] For the manner of configuring the first CSI-RS resource and the specific contents of the CSI-RS resource configuration of the first CC, reference may be made to the description of the corresponding part of the above method 700 , which will not be repeated here for the sake of brevity.

[0170] For example, the CSI-RS resource configuration of the first CC may also include the above 8 items.

[0171] In method 1000, both the first CC and the second CC are CCs serving the terminal device. For example, the first CC may be a PCC or an SCC, and the second CC may be an SCC. Of course, both the first CC and the second CC may also be SCCs.

[0172] For example, the network device may configure NZP CSI-RS resources or CSI-IM resources for the first CC through the “CSI-MeasConfig IE” in the RRC signaling.

[0173] It should be understood that in method 1000, since the CSI-RS resource configuration corresponding to the second CC is the same as the CSI-RS resource configuration corresponding to the first CC, and the RRC includes the CSI-RS resource configuration information corresponding to the first CC, the identifier of the first CC can be added to the CSI-RS resource configuration portion of the second CC in the RRC signaling. The identifier of the first CC is used to indicate that the CSI-RS resource configuration corresponding to the second CC is the same as the CSI-RS resource configuration corresponding to the first CC. In this way, the RRC signaling does not need to include the specific content of the CSI-RS resource configuration corresponding to the second CC. In other words, it is no longer necessary to configure CSI-RS resources for the second CC in the RRC signaling, that is, the specific content of the CSI-RS resource configuration for the second CC is deleted from the CSI-RS resource configuration portion of the second CC in the RRC. This achieves the effect of eliminating the need to configure CSI-RS resources for the second CC. For example, the NZP CSI-RS resource configuration information or CSI-IM resource configuration information for the second CC can be deleted in the RRC.

[0174] For example, if, according to existing methods, CSI-RS resources need to be configured for the first CC and the second CC separately in RRC signaling, the RRC signaling needs to include two groups of fields (or two parts), with each group of fields (or each part) configuring the NZP CSI-RS resources of one CC (for example, configuring the eight items described above). According to the method provided in an embodiment of the present application, only the identifier of the first CC needs to be added to the CSI-RS resource configuration part corresponding to the second CC, and the length of the field used to indicate the "identifier of the first CC" is much shorter than the length of the field used to indicate the "CSI-RS resource configuration corresponding to the second CC". In this way, there is no need to configure CSI-RS resources for the second CC in the RRC signaling, that is, the CSI-RS resource configuration part corresponding to the second CC in the RRC signaling does not need to include the group of fields (or this part) corresponding to the second CC, that is, this group of fields (or this part) is saved, thereby reducing the length (overhead) of the RRC signaling, solving the problem of large RRC signaling length (large overhead), and reducing the consumption of communication resources by RRC.

[0175] For example, the "CSI-MeasConfig" part corresponding to the first CC in the RRC signaling includes: the resource type (resourceType) corresponding to the first CC, the NZP CSI-RS-Resource identifier (NZP CSI-RS-ResourceId), resource mapping (resourceMapping), the power control offset (powerControlOffset) relative to the NZP CSI-RS RE, the power offset control relative to the SSB RE (powerControlOffsetSS), the scrambling code ID (scramblingID), the period and time slot offset (periodicityAndOffset), the reference to the TCI-State (qcl-InfoPeriodicCSI-RS) and other configuration contents.

[0176] The "CSI-MeasConfig" part corresponding to the second CC in the RRC signaling may only include the identifier of the first CC, and does not need to include: the resource type (resourceType) corresponding to the second CC, the NZP CSI-RS-Resource identifier (NZP CSI-RS-ResourceId), resource mapping (resourceMapping), the power control offset (powerControlOffset) relative to the NZP CSI-RS RE, the power offset control (powerControlOffsetSS) relative to the SSB RE, the scrambling code ID (scramblingID), the period and time slot offset (periodicityAndOffset), the reference to the TCI-State (qcl-InfoPeriodicCSI-RS) and other configuration contents.

[0177] It should also be understood that “the CSI-RS resource configuration portion of the second CC includes the identifier of the first CC” may also implicitly indicate that the CSI-RS resource configuration corresponding to the second CC is the same as the CSI-RS resource configuration corresponding to the first CC. In other words, if the terminal device receives the RRC and finds that the CSI-RS resource configuration portion of the second CC includes the identifier of the first CC, the terminal device can determine that the CSI-RS resource configuration corresponding to the second CC is the same as the CSI-RS resource configuration corresponding to the first CC. In other words, the network device and the terminal device have the same understanding of “the CSI-RS resource configuration corresponding to the second CC is the same as the CSI-RS resource configuration corresponding to the first CC.”

[0178] S1020. The terminal device determines the CSI-RS resource configuration information of the second CC according to the RRC signaling.

[0179] After the terminal device receives the RRC signaling, if the CSI-RS resource configuration part of the second CC includes the identifier of the first CC, the terminal device can determine the CSI-RS resource configuration corresponding to the second CC based on the CSI-RS resource configuration corresponding to the first CC (for example, NZP CSI-RS resource configuration for time / frequency tracking, CSI computation, L1-RSRP calculation, L1-SINR calculation, or CSI-IM resource configuration, etc.). That is, the CSI-RS resource configuration corresponding to the first CC is used as the CSI-RS resource configuration required for the second CC.

[0180] In the RRC signaling transmission method provided in an embodiment of the present application, in a carrier aggregation scenario, if the CSI-RS resource configuration on a certain carrier (e.g., a first CC) is the same as the CSI-RS resource configuration on another carrier (a second CC), the identifier of the first CC can be added to the portion of the RRC signaling that configures the CSI-RS resources of the second carrier. The identifier of the first CC is used to indicate that the CSI-RS resource configuration corresponding to the second CC is the same as the CSI-RS resource configuration corresponding to the first CC. The RRC does not need to include specific configuration information for the CSI-RS resources on the second CC, thereby reducing the length (overhead) of the RRC signaling, solving the problem of large RRC signaling length (large overhead), and reducing the consumption of communication resources by the RRC.

[0181] It should also be understood that the above uses NZP CSI-RS resource configuration as an example. In other implementations of the present application, the NZP CSI-RS resource configuration in method 1000 may also be replaced with CSI-IM resource (CSI-IM-Resource) configuration. In other words, the above approach may also be used to configure CSI-IM resources for multiple CCs in RRC. For example, the network device may configure CSI-IM resources for a CC using "CSI-MeasConfig" in RRC signaling.

[0182] It should also be understood that in other implementations of the present application, the method provided in the embodiments of the present application can also be used for NZP CSI-RS resource configuration for mobility management or resource configuration of ZP CSI-RS. If it is NZP CSI-RS resource configuration for mobility management, the identifier of the first CC can be added to the "CSI-RS-ResourceConfigMobility" part corresponding to the second CC in the RRC signaling. If it is ZP CSI-RS resource configuration, the identifier of the first CC can be added to the "PDSCH-Config IE" part corresponding to the second CC in the RRC signaling. In this way, the RRC signaling does not need to include the NZP CSI-RS resource configuration for mobility management or the ZP CSI-RS resource configuration corresponding to the second CC, and can also reduce the length (overhead) of the RRC signaling, solve the problem of large length (large overhead) of the RRC signaling, and reduce the consumption of communication resources by the RRC.

[0183] It should be understood that the above is only intended to help those skilled in the art better understand the embodiments of the present application, and is not intended to limit the scope of the embodiments of the present application. Based on the above examples given, those skilled in the art can obviously make various equivalent modifications or changes. For example, some steps in the above method embodiments may not be necessary, or some new steps may be added. Or a combination of any two or any multiple embodiments described above. Such modifications, changes, or combined solutions also fall within the scope of the embodiments of the present application.

[0184] It should also be understood that the division of the modes, situations, categories and embodiments in the embodiments of the present application is only for the convenience of description and should not constitute a special limitation. The features of various modes, categories, situations and embodiments can be combined without contradiction.

[0185] It should also be understood that the various numerical numbers involved in the embodiments of this application are only for the convenience of description and are not intended to limit the scope of the embodiments of this application. The order of the sequence numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0186] It should also be understood that the above description of the embodiments of the present application focuses on emphasizing the differences between the various embodiments. The same or similar points that are not mentioned can be referenced with each other. For the sake of brevity, they will not be repeated here.

[0187] The method of the embodiment of the present application is described in detail above with reference to Figures 1 to 10. The communication device of the embodiment of the present application is described in detail below with reference to Figures 11 to 16.

[0188] In this embodiment, terminal devices and network devices can be divided into functional modules according to the above method. For example, each function can be divided into separate functional modules, or two or more functions can be integrated into a single processing module. The integrated modules can be implemented in hardware. It should be noted that the module division in this embodiment is illustrative and represents only a logical functional division. In actual implementation, other division methods may be used.

[0189] It should be noted that the relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module, and will not be repeated here.

[0190] The terminal device and network device provided in the embodiments of the present application are used to perform any of the RRC signaling transmission methods provided in the above method embodiments, and thus can achieve the same effect as the above implementation method. In the case of an integrated unit, the terminal device or network device may include a processing module, as well as an optional storage module and a communication module. Among them, the processing module can be used to control and manage the actions of the terminal device or network device. For example, it can be used to support the terminal device or network device to execute the steps performed by the processing unit. The storage module can be used to support the storage of program code and data, etc. The communication module can be used to support communication between the terminal device or network device and other devices.

[0191] The processing module may be a processor or a controller. It may implement or execute the various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. The processor may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of digital signal processing (DSP) and a microprocessor, and so on. The storage module may be a memory. The communication module may specifically be a device that interacts with other electronic devices, such as a radio frequency circuit, a Bluetooth chip, or a Wi-Fi chip.

[0192] For example, Figure 11 shows a schematic block diagram of a communication device 1100 of an embodiment of the present application. The communication device 1100 may correspond to the network device described in the above-mentioned method 700 or method 1000, or may be a chip or component applied to the network device. Moreover, each module or unit in the communication device 1100 is respectively used to execute each action or processing process performed by any one of the network devices in the above-mentioned method 700 or method 1000.

[0193] As shown in Figure 11, the device 1100 may include a processing unit 1110 and a transceiver unit 1120. The transceiver unit 1120 is configured to perform specific signal transmission and reception under the control of the processing unit 1110. The processing unit may also be referred to as a processing module, and the transceiver unit may also be referred to as a communication unit or communication module.

[0194] In some embodiments:

[0195] Processing unit 1110 is used to: generate RRC signaling, the RRC signaling including the CSI-RS resource configuration and indication information corresponding to the first CC, the indication information being used to indicate that: the CSI-RS resource configuration corresponding to the first CC is the same as the CSI-RS resource configuration corresponding to at least one CC, the first CC and the at least one CC are both carriers serving the terminal device, and the RRC signaling does not include the CSI-RS resource configuration corresponding to the at least one CC.

[0196] The transceiver unit 1120 is used to send the RRC signaling.

[0197] The communication device provided in the present application, in a carrier aggregation scenario, if the CSI-RS resource configuration on the first CC is the same as the CSI-RS resource configuration of other carriers, indication information (e.g., a CC list) can be added to the portion of the CSI-RS resource configuration on the first carrier in the RRC signaling to indicate that the CSI-RS resource configuration of the first carrier is the same as the CSI-RS resource configuration of the CCs in the CC list. In this way, the RRC signaling does not need to include the configuration content of the CSI-RS resources on other carriers. This reduces the length (overhead) of the RRC signaling, solves the problem of large length (large overhead) of the RRC signaling, and reduces the consumption of communication resources by RRC.

[0198] In some possible implementations, the indication information includes a CC list, where the CC list includes an identifier corresponding to at least one CC.

[0199] In some possible implementations, the CSI-RS resource configuration includes at least one of: NZP CSI-RS resource configuration or CSI-IM resource configuration.

[0200] In some possible implementations, the first CC is a PCC, and at least one CC is an SCC.

[0201] In some possible implementations, the indication information is located in the NZP CSI-RS resource configuration part of the "CSI-MeasConfig" field corresponding to the first CC.

[0202] In other embodiments:

[0203] Processing unit 1110 is configured to generate RRC signaling, where the RRC signaling includes a CSI-RS resource configuration corresponding to the first CC, where a portion of the CSI-RS resource configuration for the second CC in the RRC signaling includes an identifier of the first CC, where the identifier of the first CC is used to indicate that the CSI-RS resource configuration corresponding to the second CC is the same as the CSI-RS resource configuration corresponding to the first CC, and that both the first CC and the second CC are carriers serving a terminal device. The portion of the CSI-RS resource configuration for the second CC in the RRC signaling does not include the CSI-RS resource configuration corresponding to the second CC.

[0204] The transceiver unit 1120 is used to send the RRC signaling.

[0205] In the communication device provided herein, in a carrier aggregation scenario, if the CSI-RS resource configuration on a carrier (e.g., a first CC) is identical to the CSI-RS resource configuration on another carrier (a second CC), the identifier of the first CC can be added to the portion of the RRC signaling that configures the CSI-RS resources on the second carrier. The identifier of the first CC is used to indicate that the CSI-RS resource configuration corresponding to the second CC is identical to the CSI-RS resource configuration corresponding to the first CC. The RRC signaling does not need to include specific configuration information for the CSI-RS resources on the second CC, thereby reducing the length (overhead) of the RRC signaling, addressing the issue of large RRC signaling length (high overhead), and reducing the consumption of communication resources by the RRC signaling.

[0206] In some possible implementations, the CSI-RS resource configuration includes at least one of: NZP CSI-RS resource configuration or CSI-IM resource configuration.

[0207] In some possible implementations, the first CC is a PCC or an SCC, and the second CC is an SCC.

[0208] In some possible implementations, the identifier of the first CC is located in the NZP CSI-RS resource configuration portion of the "CSI-MeasConfig" field corresponding to the second CC.

[0209] It should be understood that the specific process of each unit in the communication device 1100 executing the above corresponding steps can be referred to the description of the network device in conjunction with the relevant embodiments of method 700 or method 1000 in the previous text. For the sake of brevity, it is not repeated here.

[0210] Optionally, the transceiver unit 1120 may include a receiving unit (module) and a sending unit (module), configured to execute the steps of the network device receiving information and sending information in the embodiment of the aforementioned method 500.

[0211] Furthermore, the communication device 1100 may also include a storage unit. The transceiver unit 1120 may be a transceiver, an input / output interface, or an interface circuit. The storage unit is configured to store instructions executed by the transceiver unit 1120 and the processing unit 1110. The transceiver unit 1120, the processing unit 1110, and the storage unit are coupled to each other. The storage unit stores instructions, the processing unit 1110 is configured to execute the instructions stored in the storage unit, and the transceiver unit 1120 is configured to perform specific signal transmission and reception under the control of the processing unit 1110.

[0212] It should be understood that the transceiver unit 1120 may be a transceiver, an input / output interface, or an interface circuit. The storage unit may be a memory. The processing unit 1110 may be implemented by a processor. As shown in FIG12 , the communication device 1200 may include a processor 1210, a memory 1220, and a transceiver 1230.

[0213] The communication device 1100 shown in FIG11 or the communication device 1200 shown in FIG12 can implement the steps performed by the network device in the aforementioned method 700 or method 1000. Similar descriptions can refer to the descriptions of the aforementioned corresponding methods. To avoid repetition, they are not repeated here.

[0214] It should also be understood that the communication device 1100 shown in FIG. 11 or the communication device 1200 shown in FIG. 12 may be a network device, or a network device may include the communication device 1100 shown in FIG. 11 or the communication device 1200 shown in FIG. 12 .

[0215] Exemplarily, Figure 13 shows a schematic block diagram of a communication device 1300 of an embodiment of the present application. The communication device 1300 may correspond to the terminal device described in the above-mentioned method 700 or method 1000, or may be a chip or component applied to the terminal device. Moreover, each module or unit in the communication device 1300 is respectively used to execute each action or processing process performed by the terminal device in any one of the above-mentioned methods 700 or method 1000.

[0216] As shown in FIG13 , the communication device 1300 includes a transceiver unit 1310 and a processing unit 1320. The transceiver unit 1310 is configured to perform specific signal transmission and reception under the control of the processing unit 1320.

[0217] In some embodiments:

[0218] The transceiver unit 1310 is used to: receive RRC signaling, which includes the CSI-RS resource configuration and indication information corresponding to the first CC, and the indication information is used to indicate that: the CSI-RS resource configuration corresponding to the first CC is the same as the CSI-RS resource configuration corresponding to at least one CC, and the first CC and the at least one CC are both carriers serving the terminal device, and the RRC signaling does not include the CSI-RS resource configuration corresponding to the at least one CC.

[0219] The processing unit 1320 is configured to determine, according to the RRC signaling, a CSI-RS resource configuration corresponding to at least one CC.

[0220] The communication device provided in the present application, in a carrier aggregation scenario, if the CSI-RS resource configuration on the first CC is the same as the CSI-RS resource configuration of other carriers, indication information (e.g., a CC list) can be added to the portion of the CSI-RS resource configuration on the first carrier in the RRC signaling to indicate that the CSI-RS resource configuration of the first carrier is the same as the CSI-RS resource configuration of the CCs in the CC list. In this way, the RRC signaling does not need to include the configuration content of the CSI-RS resources on other carriers. This reduces the length (overhead) of the RRC signaling, solves the problem of large length (large overhead) of the RRC signaling, and reduces the consumption of communication resources by RRC.

[0221] In some possible implementations, the indication information includes a CC list, where the CC list includes an identifier corresponding to at least one CC.

[0222] In some possible implementations, the CSI-RS resource configuration includes at least one of: NZP CSI-RS resource configuration or CSI-IM resource configuration.

[0223] In some possible implementations, the first CC is a PCC, and at least one CC is an SCC.

[0224] In some possible implementations, the indication information is located in the NZP CSI-RS resource configuration part of the "CSI-MeasConfig" field corresponding to the first CC.

[0225] In some other embodiments: the transceiver unit 1310 is configured to: receive RRC signaling, where the RRC signaling includes a CSI-RS resource configuration corresponding to a first CC, where a portion of the CSI-RS resource configuration for a second CC in the RRC signaling includes an identifier of the first CC, where the identifier of the first CC is used to indicate that the CSI-RS resource configuration corresponding to the second CC is the same as the CSI-RS resource configuration corresponding to the first CC, and that both the first CC and the second CC are carriers serving a terminal device. The portion of the CSI-RS resource configuration for the second CC in the RRC signaling does not include the CSI-RS resource configuration corresponding to the second CC.

[0226] The processing unit 1320 is configured to determine, according to the RRC signaling, the CSI-RS resource configuration corresponding to the second CC.

[0227] In the communication device provided in the present application, in a carrier aggregation scenario, if the CSI-RS resource configuration on a certain carrier (e.g., a first CC) is the same as the CSI-RS resource configuration on another carrier (a second CC), the identifier of the first CC can be added to the portion of the RRC signaling that configures the CSI-RS resources on the second carrier. The identifier of the first CC is used to indicate that the CSI-RS resource configuration corresponding to the second CC is the same as the CSI-RS resource configuration corresponding to the first CC. The RRC does not need to include specific configuration information for the CSI-RS resources on the second CC, thereby reducing the length (overhead) of the RRC signaling, resolving the problem of large RRC signaling length (large overhead), and reducing the consumption of communication resources by the RRC.

[0228] In some possible implementations, the CSI-RS resource configuration includes at least one of an NZP CSI-RS resource configuration or a CSI-IM resource configuration.

[0229] In some possible implementations, the first CC is a PCC or an SCC, and the second CC is an SCC.

[0230] In some possible implementations, the identifier of the first CC is located in the NZP CSI-RS resource configuration portion of the "CSI-MeasConfig" field corresponding to the second CC.

[0231] Furthermore, the communication device 1300 may also include a storage unit, and the transceiver unit 1310 may be a transceiver, an input / output interface, or an interface circuit. The storage unit is used to store instructions executed by the transceiver unit 1310 and the processing unit 1320. The transceiver unit 1310, the processing unit 1320, and the storage unit are coupled to each other. The storage unit stores instructions, the processing unit 1320 is used to execute the instructions stored in the storage unit, and the transceiver unit 1310 is used to perform specific signal transmission and reception under the control of the processing unit 1320.

[0232] It should be understood that the specific process of each unit in the communication device 1300 executing the above corresponding steps can be referred to the description of the terminal device in the above text in combination with the relevant embodiments in method 700 or method 1000. For the sake of brevity, it is not repeated here.

[0233] It should be understood that the transceiver unit 1310 may be a transceiver, an input / output interface, or an interface circuit. The storage unit may be a memory. The processing unit 1320 may be implemented by a processor.

[0234] For example, as shown in FIG14 , communication device 1400 may include a processor 1410, a memory 1420, a transceiver 1430, and a bus system 1440. The various components of communication device 1400 are coupled together via bus system 1440. Bus system 1440, in addition to a data bus, may also include a power bus, a control bus, and a status signal bus. However, for clarity, various buses are labeled as bus system 1440 in FIG14 . For ease of illustration, FIG14 is only schematically illustrated.

[0235] The communication device 1300 shown in FIG13 or the communication device 1400 shown in FIG14 can implement the steps performed by the terminal device in the aforementioned method 700 or method 1000. Similar descriptions can refer to the descriptions of the aforementioned corresponding methods. To avoid repetition, they are not repeated here.

[0236] It should also be understood that the communication device 1300 shown in Figure 13 or the communication device 1400 shown in Figure 14 can be a terminal device, or the terminal device can include the communication device 1300 shown in Figure 13 or the communication device 1400 shown in Figure 14.

[0237] It should also be understood that the division of units in the above device is merely a division of logical functions. In actual implementation, they can be fully or partially integrated into one physical entity, or they can be physically separated. Moreover, the units in the device can all be implemented in the form of software called through processing elements; or all be implemented in the form of hardware; or some units can be implemented in the form of software called through processing elements, and some units can be implemented in the form of hardware. For example, each unit can be a separately established processing element, or it can be integrated into a certain chip of the device. In addition, it can also be stored in a memory in the form of a program, and called by a certain processing element of the device to execute the function of the unit. Here, the processing element 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 unit above can be implemented by the integrated logic circuit of the hardware in the processor element or in the form of software called through the processing element.

[0238] In one example, the unit in any of the above devices may be one or more integrated circuits configured to implement the above method, such as one or more application specific integrated circuits (ASICs), one or more DSPs, one or more field programmable gate arrays (FPGAs), or a combination of at least two of these integrated circuit forms. For another example, when the unit in the device can be implemented in the form of a processing element scheduler, the processing element may be a general-purpose processor, such as a central processing unit (CPU) or other processor that can call a program. For another example, these units can be integrated together and implemented in the form of a system-on-a-chip (SOC).

[0239] Figure 15 is a schematic diagram of the structure of a terminal device 1500 provided in this application. The aforementioned communication device 1300 or communication device 1400 can be configured in the terminal device 1500. Alternatively, the communication device 1300 or communication device 1400 itself can be the terminal device 1500. In other words, the terminal device 1500 can perform the actions performed by the terminal device in the aforementioned method 700 or method 1000. Optionally, for ease of illustration, Figure 15 only shows the main components of the terminal device. As shown in Figure 15, the terminal device 1500 includes a processor, memory, control circuitry, an antenna, and input / output devices.

[0240] The processor is mainly used to process communication protocols and communication data, as well as to control the entire terminal device, execute software programs, and process data of software programs, such as supporting the terminal device to perform the actions described in the above-mentioned RRC signaling transmission method embodiment. The memory is mainly used to store software programs and data, such as storing the configuration of CSI-RS resources corresponding to each CC described in the above-mentioned embodiment. The control circuit is mainly used to convert baseband signals into radio frequency signals and process radio frequency signals. The control circuit and antenna together can also be called a transceiver, which is mainly used to transmit and receive radio frequency signals in the form of electromagnetic waves. For example, it receives the RRC signaling described in the above-mentioned embodiment. Input and output devices, such as touch screens, displays, keyboards, etc., are mainly used to receive data input by users and output data to users.

[0241] When the terminal device is turned on, the processor can read the software program in the storage unit, interpret and execute the instructions of the software program, and process the data of the software program. When data needs to be sent wirelessly, the processor performs baseband processing on the data to be sent and outputs the baseband signal to the RF circuit. The RF circuit performs RF processing on the baseband signal and then sends the RF signal outward in the form of electromagnetic waves through the antenna. When a signaling (such as the above-mentioned RRC signaling, etc.) is sent to the terminal device, the RF circuit receives the RF signal through the antenna, converts the RF signal into a baseband signal, and outputs the baseband signal to the processor. The processor converts the baseband signal into data and processes the data.

[0242] Those skilled in the art will appreciate that, for ease of explanation, FIG15 shows only one memory and processor. In an actual terminal device, multiple processors and memories may exist. The memory may also be referred to as a storage medium or storage device, etc., which is not limited in the present embodiment.

[0243] For example, a processor may include a baseband processor and a central processing unit (CPU). The baseband processor is primarily responsible for processing communication protocols and communication data, while the CPU is primarily responsible for controlling the entire terminal device, executing software programs, and processing data from software programs. The processor in Figure 15 integrates the functions of both the baseband processor and the CPU. Those skilled in the art will appreciate that the baseband processor and the CPU may also be independent processors interconnected via a bus or other technology. Those skilled in the art will appreciate that a terminal device may include multiple baseband processors to accommodate different network standards, multiple CPUs to enhance its processing capabilities, and that the various components of the terminal device may be connected via various buses. The baseband processor may also be referred to as a baseband processing circuit or a baseband processing chip. The CPU may also be referred to as a central processing circuit or a central processing chip. The functionality for processing communication protocols and communication data may be built into the processor or stored as a software program in a storage unit, with the processor executing the software program to implement the baseband processing functionality.

[0244] By way of example, in an embodiment of the present application, an antenna and a control circuit having transceiver functions may be regarded as a transceiver unit 1501 of the terminal device 1500, and a processor having a processing function may be regarded as a processing unit 1502 of the terminal device 1500. As shown in FIG15 , the terminal device 1500 includes a transceiver unit 1501 and a processing unit 1502. The transceiver unit may also be referred to as a transceiver, a transceiver, a transceiver device, etc. Optionally, the device for implementing the receiving function in the transceiver unit 1501 may be regarded as a receiving unit, and the device for implementing the transmitting function in the transceiver unit 1501 may be regarded as a transmitting unit, that is, the transceiver unit 1501 includes a receiving unit and a transmitting unit. By way of example, the receiving unit may also be referred to as a receiver, a receiver, a receiving circuit, etc., and the transmitting unit may be referred to as a transmitter, a transmitter, or a transmitting circuit, etc.

[0245] Figure 16 is a structural diagram of a network device 1600 provided in an embodiment of the present application, which can be used to implement the functions of the network device in the above method. The network device 1600 includes one or more radio frequency units, such as a remote radio unit (RRU) 1601 and one or more baseband units (BBU) (also known as digital units, DU) 1602. The RRU 1601 can be called a transceiver unit, a transceiver, a transceiver circuit, or a transceiver, etc., and may include at least one antenna 16011 and a radio frequency unit 16012. The RRU 1601 part is mainly used for receiving and transmitting radio frequency signals and converting radio frequency signals into baseband signals, for example, for sending multiple groups of data streams and indication information in the above embodiment to terminal devices. The BBU 1602 part is mainly used for baseband processing, controlling the base station, etc. The RRU 1601 and BBU 1602 can be physically set together or physically separated, that is, a distributed base station.

[0246] The BBU 1602 is the control center of the base station, which can also be called a processing unit. It is mainly used to perform baseband processing functions such as channel coding, multiplexing, modulation, spread spectrum, etc. For example, the BBU (processing unit) 1602 can be used to control the base station to execute the operation process of the network device in the above method embodiment.

[0247] In one example, the BBU 1602 can be composed of one or more boards. Multiple boards can jointly support a wireless access network with a single access standard (such as an LTE system or a 5G system), or can separately support wireless access networks with different access standards. The BBU 1602 also includes a memory 16021 and a processor 16022. The memory 16021 is used to store necessary instructions and data. For example, the memory 16021 stores information such as the first DCI in the above embodiment and the uplink precoding matrix corresponding to the uplink resources with subband granularity. The processor 16022 is used to control the base station to perform necessary actions, such as controlling the base station to execute the operation process of the network device in the above method embodiment. The memory 16021 and the processor 16022 can serve one or more boards. That is, a separate memory and processor can be set on each board. Alternatively, multiple boards can share the same memory and processor. In addition, necessary circuits can be set on each board.

[0248] In one possible implementation, with the development of system-on-chip (SoC) technology, all or part of the functions of parts 1602 and 1601 can be implemented using SoC technology. For example, they can be implemented using a base station function chip that integrates a processor, memory, antenna interface, and other components. Programs for base station-related functions are stored in the memory, and the processor executes the programs to implement the base station-related functions. Optionally, the base station function chip can also read memory external to the chip to implement the base station-related functions.

[0249] It should be understood that the structure of the network device illustrated in FIG16 is only one possible form and should not constitute any limitation to the embodiments of the present application. The present application does not exclude the possibility of other forms of base station structures that may appear in the future.

[0250] It should be understood that in the embodiments of the present application, the processor may be a central processing unit (CPU), and the processor may also be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor, etc.

[0251] It should also be understood that the memory in the embodiments of the present application can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an EPROM, an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0252] An embodiment of the present application also provides a communication system, which includes: the above-mentioned terminal device and network device.

[0253] The above embodiments can be implemented in whole or in part by software, hardware, firmware or any other combination. When implemented using software, the above embodiments can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer program are loaded or executed on a computer, the process or function according to the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website, computer, server or data center to another website, computer, server or data center by wired (e.g., infrared, wireless, microwave, etc.) means.

[0254] The present application also provides a computer-readable medium for storing computer program code, wherein the computer program includes instructions for executing any of the RRC signaling transmission methods provided in the above embodiments of the present application. The computer-readable medium may be the memory in the above examples, and the present application is not limited thereto.

[0255] The present application also provides a computer program product, which includes instructions. When the instructions are executed, the terminal device performs the terminal device operation corresponding to the above method, or the network device performs the network device operation corresponding to the above method.

[0256] An embodiment of the present application further provides a chip, comprising: a processing unit and a communication unit. The processing unit may be, for example, a processor, and the communication unit may be, for example, an input / output interface, a pin, or a circuit. The processing unit may execute computer instructions to cause the chip within the communication device to perform any of the RRC signaling transmission methods provided in the embodiments of the present application.

[0257] Optionally, any one of the communication devices provided in the above embodiments of the present application may include this chip.

[0258] Optionally, the computer instructions are stored in a storage unit.

[0259] Optionally, the storage unit is a storage unit within the chip, such as a register, a cache, etc. The storage unit may also be a storage unit located outside the chip within the communication device, such as a ROM or other type of static storage device that can store static information and instructions, RAM, etc. The processor mentioned in any of the above may be a CPU, a microprocessor, an ASIC, or one or more integrated circuits for controlling the execution of the program of the above-mentioned RRC signaling transmission method. The processing unit and the storage unit may be decoupled and respectively provided on different physical devices, and connected by wired or wireless means to implement the respective functions of the processing unit and the storage unit, so as to support the chip to implement the various functions in the above-mentioned embodiments. Alternatively, the processing unit and the memory may also be coupled on the same device.

[0260] The terms "system" and "network" are often used interchangeably in this document. The term "and / or" is simply a description of an association between related objects, indicating that three possible relationships exist. For example, "A and / or B" can mean: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, the character " / " generally indicates an "or" relationship between the related objects.

[0261] Various objects such as various messages / information / equipment / systems / devices / actions / operations / processes that may appear in this application are named. It is understandable that these specific names do not constitute a limitation on the relevant objects. The names assigned may change with factors such as the scene, context or usage habits. The understanding of the technical meaning of the technical terms in this application should be mainly determined from the functions and technical effects embodied / executed in the technical solution.

[0262] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0263] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the unit is only a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0264] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0265] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0266] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. A method for RRC signaling transmission, characterized in that: The method comprises: RRC signaling is sent, wherein the RRC signaling includes a CSI-RS resource configuration and indication information corresponding to a first CC, wherein the indication information is used to indicate that: the CSI-RS resource configuration corresponding to the first CC is the same as the CSI-RS resource configuration corresponding to at least one CC, and the first CC and the at least one CC are both carriers serving the terminal device.

2. The method according to claim 1, characterized in that The RRC signaling does not include the CSI-RS resource configuration corresponding to the at least one CC.

3. The method according to claim 1 or 2, characterized in that: The indication information includes a CC list, and the CC list includes identifiers corresponding to the at least one CC.

4. The method according to any one of claims 1 to 3, characterized in that The CSI-RS resource configuration includes: at least one of NZP CSI-RS resource configuration or CSI-IM resource configuration.

5. The method according to any one of claims 1 to 4, characterized in that The first CC is a PCC, and the at least one CC is an SCC.

6. The method according to any one of claims 1 to 5, characterized in that The indication information is located in the NZP CSI-RS resource configuration part of the "CSI-MeasConfig" field corresponding to the first CC.

7. A method for RRC signaling transmission, characterized in that: The method comprises: RRC signaling is sent, wherein the RRC signaling includes a CSI-RS resource configuration corresponding to a first CC, wherein a CSI-RS resource configuration part of a second CC in the RRC signaling includes an identifier of the first CC, wherein the identifier of the first CC is used to indicate that the CSI-RS resource configuration corresponding to the second CC is the same as the CSI-RS resource configuration corresponding to the first CC, and both the first CC and the second CC are carriers serving a terminal device.

8. The method according to claim 7, characterized in that The CSI-RS resource configuration part of the second CC in the RRC signaling does not include the CSI-RS resource configuration corresponding to the second CC.

9. The method according to claim 7 or 8, characterized in that: The CSI-RS resource configuration includes: at least one of NZP CSI-RS resource configuration or CSI-IM resource configuration.

10. The method according to any one of claims 7 to 9, characterized in that The first CC is a PCC or an SCC, and the second CC is an SCC.

11. The method according to any one of claims 7 to 10, characterized in that The identifier of the first CC is located in the NZP CSI-RS resource configuration part of the "CSI-MeasConfig" field corresponding to the second CC.

12. A method for RRC signaling transmission, characterized in that: The method comprises: receiving RRC signaling, where the RRC signaling includes a CSI-RS resource configuration and indication information corresponding to a first CC, where the indication information is used to indicate that: the CSI-RS resource configuration corresponding to the first CC is the same as the CSI-RS resource configuration corresponding to at least one CC, and the first CC and the at least one CC are both carriers serving a terminal device; Determine, according to the RRC signaling, a CSI-RS resource configuration corresponding to each of the at least one CC.

13. The method according to claim 12, characterized in that The RRC signaling does not include the CSI-RS resource configuration corresponding to the at least one CC.

14. The method according to claim 12 or 13, characterized in that The indication information includes a CC list, and the CC list includes identifiers corresponding to the at least one CC.

15. The method according to any one of claims 12 to 14, characterized in that The CSI-RS resource configuration includes: at least one of NZP CSI-RS resource configuration or CSI-IM resource configuration.

16. The method according to any one of claims 12 to 15, characterized in that The first CC is a PCC, and the at least one CC is an SCC.

17. The method according to any one of claims 12 to 16, characterized in that The indication information is located in the NZP CSI-RS resource configuration part of the "CSI-MeasConfig" field corresponding to the first CC.

18. A method for RRC signaling transmission, characterized in that: The method comprises: receiving an RRC signaling, wherein the RRC signaling includes a CSI-RS resource configuration corresponding to a first CC, wherein a CSI-RS resource configuration portion of a second CC in the RRC signaling includes an identifier of the first CC, and the identifier of the first CC is used to indicate: The CSI-RS resource configuration corresponding to the second CC is the same as the CSI-RS resource configuration corresponding to the first CC; Determine, according to the RRC signaling, a CSI-RS resource configuration corresponding to the second CC.

19. The method according to claim 18, characterized in that The CSI-RS resource configuration part of the second CC in the RRC signaling does not include the CSI-RS resource configuration corresponding to the second CC.

20. The method according to claim 18 or 19, characterized in that The CSI-RS resource configuration includes: at least one of NZP CSI-RS resource configuration or CSI-IM resource configuration.

21. The method according to any one of claims 18 to 20, characterized in that The first CC is a PCC or an SCC, and the second CC is an SCC.

22. The method according to any one of claims 18 to 21, characterized in that The identifier of the first CC is located in the NZP CSI-RS resource configuration part of the "CSI-MeasConfig" field corresponding to the second CC.

23. A communication device, characterized in that: include: A unit for executing the respective steps of the method according to any one of claims 1 to 11, or a unit for executing the respective steps of the method according to any one of claims 12 to 22.

24. A communication device, characterized in that: The method comprises at least one processor and an interface circuit, wherein the at least one processor is used to execute: the method according to any one of claims 1 to 11, or the method according to any one of claims 12 to 22.

25. A communication device, characterized in that: include: A processor, the processor is coupled to a memory, the memory is used to store programs or instructions, when the program or instructions are executed by the processor, the device executes: the method according to any one of claims 1 to 11, or the method according to any one of claims 12 to 22.

26. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, wherein the computer program includes program instructions, and when the program instructions are executed by a processor, the processor executes: the method as claimed in any one of claims 1 to 11, or the method as claimed in any one of claims 12 to 22.

27. A chip, characterized in that: It comprises: a processor, configured to call and run a computer program from a memory, so that a communication device equipped with the chip executes: a method as claimed in any one of claims 1 to 11, or a method as claimed in any one of claims 12 to 22.

28. A computer program product, comprising a computer program, wherein when the computer program is executed by a processor, the computer program is configured to perform the method according to any one of claims 1 to 11 or the method according to any one of claims 12 to 22.

29. A system, characterized in that: The method comprises at least one communication device, wherein the communication device is configured to execute the method according to any one of claims 1 to 11.

Images