RRC signaling transmission method and communication device

Abstract

According to the RRC signaling transmission method and the communication device, in a carrier aggregation scene, if CSI-RS resource configuration of a first carrier (such as a PCC) is the same as CSI-RS resource configuration of other carriers (such as a plurality of SCCs), indication information (such as a CC list) can be added to a CSI-RS resource configuration part of the first carrier in an RRC signaling; 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, and the RRC may not include the configuration information of the CSI-RS resources on other carriers; or, the identifier of the first carrier can be added to the CSI-RS resource configuration part of other carriers in the RRC, and the RRC does not include specific configuration information of CSI-RS resources on other carriers, so that the length (overhead) of RRC signaling is reduced, and the consumption of communication resources by the RRC is reduced.

Description

Technical Field

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

[0002] In order to further increase the transmission rate, carrier aggregation (CA) technology is supported in the protocol, that is, multiple component carriers (CCs) are aggregated together for data transmission, thereby increasing the bandwidth of data transmission and the data transmission rate. For each CC accessed by the terminal device, the base station needs to use radio resource control (RRC) signaling to configure channel state information-reference signal (CSI-RS) resources for this CC. Since a terminal may access multiple CCs through CA, as the number of CCs and the bandwidth continue to increase, the RRC signaling needs to configure the CSI-RS resources corresponding to each of these multiple CCs respectively, resulting in an increase in the overhead (or length) of the RRC signaling, and more communication resources are required to transmit the RRC, increasing the consumption of communication resources. Summary of the Invention

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

[0004] In a first aspect, a method for RRC signaling transmission is provided. The execution subject of this method can be a network device, or a chip, a chip system, or a processor that supports the network device to implement this method, or a logical node, a logical module, or software that can implement all or part of the functions of the network device. The method includes: sending RRC signaling, where the RRC signaling includes the CSI-RS resource configuration corresponding to a first CC and indication information, 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 configurations corresponding to at least one CC, and both the first CC and the at least one CC are carriers serving the terminal device. Wherein, the RRC signaling does not include the CSI-RS resource configurations corresponding to the at least one CC respectively.

[0005] The method for RRC signaling transmission provided by the first aspect, in the scenario of carrier aggregation, if the CSI-RS resource configuration on a certain carrier (for example, the first CC) is the same as the CSI-RS resource configuration on another carrier (the second CC), the identifier of the first CC can be added to the part of the CSI-RS resource configuration on the second carrier 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. The specific configuration information of the CSI-RS resources on the second CC does not need to be included in the RRC, 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.

[0006] In a possible implementation manner of the first aspect, the indication information includes a CC list, and the CC list includes the identifiers corresponding to at least one CC respectively. In this implementation manner, it can more accurately indicate which CCs have the same NZP CSI-RS resource configuration as the NZP CSI-RS resource configuration corresponding to the first CC. The accuracy of the indication information is improved, it is easy to implement, and the overhead of the indication information can be reduced.

[0007] Exemplarily, the CSI-RS resource configuration includes at least one of the NZP CSI-RS resource configuration or the CSI-IM resource configuration. In this implementation manner, since the NZP CSI-RS resource configuration and the CSI-IM resource configuration include relatively many configurations, the gain in reducing the length of the RRC signaling is relatively obvious.

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

[0009] Exemplarily, the first CC is a PCC, and all at least one CCs are SCCs. In this implementation manner, by following the setting of the SCC LIST in the corresponding CSI-RS resource configuration part of the PCC, it is more in line with the actual scenario, improving the practicability of the method provided by this application, and the gain is relatively obvious.

[0010] Exemplarily, the first CC can also be an SCC, and each CC in the CC list is also an SCC.

[0011] Exemplarily, in the case where the configuration of the NZP CSI-RS resources corresponding to the first CC and the CC list are included in the RRC signaling, 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 the NZP CSI-RS resources for each CC in the CC list in the RRC signaling, that is, the configuration information of the NZP CSI-RS resources on each CC in the CC list is deleted in the RRC, achieving a zero-configuration effect.

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

[0013] Optionally, if it is the NZP CSI-RS resource configuration for mobility management, indication information (such as the above CC list) can be added to the "CSI-RS-ResourceConfigMobility" part corresponding to the first CC in the RRC signaling. If it is the resource configuration of ZP CSI-RS, indication information (such as the above 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 the RRC.

[0014] In a second aspect, a method for transmitting RRC signaling is provided. The execution subject of this method can be a network device, or a chip, chip system, or processor that supports the network device to implement this method, or a logical node, logical module, or software that can implement all or part of the functions of the network device. The method includes: sending RRC signaling, where 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. 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. Among them, 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.

[0015] The method for RRC signaling transmission provided by the second aspect, in the scenario of carrier aggregation, if the CSI-RS resource configuration on a certain carrier (for example, the first CC) is the same as the CSI-RS resource configuration on another carrier (the second CC), the identifier of the first CC can be added to the part of the CSI-RS resource configuration of the second carrier 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 the RRC, the specific configuration information of the CSI-RS resources on the second CC does not need to be included, 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.

[0016] Exemplarily, the first CC is a PCC or an SCC, and the second CC is an SCC. In this implementation manner, by adding the identifier of the PCC or another SCC to the part of the CSI-RS resource configuration corresponding to the SCC, it conforms to the actual scenario, improves the practicability of the method provided by this application, and the gain is obvious.

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

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

[0019] Exemplarily, 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 respectively. In other words, in the RRC signaling, it is no longer necessary to configure the NZP CSI-RS resources for each CC in the CC list, 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.

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

[0021] Optionally, if it is an NZP CSI-RS resource configuration for mobility management, the identifier of the first CC may be added to the "CSI-RS-ResourceConfigMobility" section corresponding to the second CC in the RRC signaling. If it is a resource configuration of ZP CSI-RS, the identifier of the first CC may be added to the "PDSCH-Config IE" section 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 resource configuration of ZP CSI-RS corresponding to the second CC, which 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 the RRC.

[0022] In a third aspect, a method for transmitting RRC signaling is provided. The execution subject of this method may be a terminal device, or a chip, a chip system, or a processor that supports the terminal device to implement this method. The method includes: receiving RRC signaling, where the RRC signaling includes the CSI-RS resource configuration corresponding to the first CC and indication information, 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 configurations corresponding to at least one CC, and both the first CC and the at least one CC are carriers serving the terminal device; determining the CSI-RS resource configurations corresponding to at least one CC according to the RRC signaling. Wherein, the RRC signaling does not include the CSI-RS resource configurations corresponding to at least one CC.

[0023] In the method for transmitting RRC signaling provided in the third aspect, in a carrier aggregation scenario, if the CSI-RS resource configuration on the first CC is the same as the CSI-RS resource configurations on other carriers, indication information (such as a CC list) may be added to the part of the RRC signaling that configures the CSI-RS resources on the first carrier, for indicating that the CSI-RS resource configuration on the first carrier is the same as the CSI-RS resource configurations on the CCs in the CC list. The configuration content of the CSI-RS resources on other carriers does not need to be included in the RRC signaling. The length (overhead) of the RRC signaling is reduced, the problem of the large length (large overhead) of the RRC signaling is solved, and the consumption of communication resources by the RRC is reduced.

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

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

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

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

[0028] For the technical effects corresponding to any possible implementation in the third aspect, reference may be made to the technical effects corresponding to any implementation in the first aspect above, which will not be elaborated here.

[0029] In a fourth aspect, a method for RRC signaling transmission is provided. The execution entity of this method can be a terminal device, or a chip, a chip system, or a processor that supports the terminal device to implement this method. The method includes: receiving an RRC signaling, where 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; determining the CSI-RS resource configuration corresponding to the second CC according to the RRC signaling. Wherein, 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.

[0030] In the method for RRC signaling transmission provided in the fourth aspect, in the scenario of carrier aggregation, if the CSI-RS resource configuration on a certain carrier (for example, the first CC) is the same as the CSI-RS resource configuration on another carrier (the second CC), the identifier of the first CC can be added to the part of the CSI-RS resource configuration on the second carrier in the RRC signaling, 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. The specific configuration information of the CSI-RS resources on the second CC does not need to be included in the RRC, 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.

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

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

[0033] In a possible implementation 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.

[0034] For the technical effects corresponding to any possible implementation in the fourth aspect, reference may be made to the technical effects corresponding to any implementation in the second aspect above, which will not be elaborated here.

[0035] In a fifth aspect, a communication device is provided. The device includes: a module for performing each step in the above first aspect or any possible implementation of the first aspect (for example, including a processing module and an interface module), or a module for performing each step in the above second aspect or any possible implementation of the second aspect (for example, including a processing module and an interface module). The device can be a network device, or a chip, chip system, or processor in a network device, etc., and can also be a logical node, logical module, or software that can implement all or part of the functions of a network device.

[0036] In a sixth aspect, a communication device is provided. The device includes at least one processor and a memory. The at least one processor is used to execute: the method in the above first aspect or any possible implementation of the first aspect, or the method in the above second aspect or any possible implementation of the second aspect. The device can be a network device, or a chip, chip system, or processor in a network device, etc., and can also be a logical node, logical module, or software that can implement all or part of the functions of a network device.

[0037] In a seventh aspect, a communication device is provided. The device includes at least one processor and an interface circuit. The at least one processor is used to execute: the method in the above first aspect or any possible implementation of the first aspect, or the method in the above second aspect or any possible implementation of the second aspect. The device can be a network device, or a chip, chip system, or processor in a network device, etc., and can also be a logical node, logical module, or software that can implement all or part of the functions of a network device.

[0038] In an eighth aspect, a communication device is provided. The device includes: a module for performing each step in the above third aspect or any possible implementation of the third aspect (for example, including a processing module and an interface module), or a module for performing each step in the above fourth aspect or any possible implementation of the fourth aspect (for example, including a processing module and an interface module). The device can be a terminal device, or a chip, chip system, or processor in a terminal device.

[0039] In a ninth aspect, a communication device is provided. The device includes at least one processor and a memory. The at least one processor is configured to execute: the method in the third aspect above or any possible implementation manner of the third aspect, or the method in the fourth aspect above or any possible implementation manner of the fourth aspect. The device may be a terminal device, or a chip, a chip system, or a processor in the terminal device, etc.

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

[0041] In an eleventh aspect, a network device is provided. The network device includes the communication device provided in the fifth aspect above, or the network device includes the communication device provided in the sixth aspect above, or the network device includes the communication device provided in the seventh aspect above.

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

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

[0044] In a fourteenth aspect, a computer-readable storage medium is provided. The computer-readable storage medium stores a computer program which, when executed, is configured to execute: the method in the first aspect above or any possible implementation manner of the first aspect, or the method in the second aspect above or any possible implementation manner of the second aspect, the method in the third aspect above or any possible implementation manner of the third aspect, or the method in the fourth aspect above or any possible implementation manner of the fourth aspect.

[0045] In a fifteenth aspect, a chip is provided, the chip including: a processor for calling and running a computer program from a memory, so that a communication device installed with the chip performs: the method in the first aspect above or any possible implementation manner of the first aspect, the method in the second aspect above or any possible implementation manner of the second aspect, the method in the third aspect above or any possible implementation manner of the third aspect, or the method in the fourth aspect above or any possible implementation manner of the fourth aspect. Description of the Drawings

[0046] Figure 1 FIG. is a schematic diagram of a communication scenario applicable to the method provided in this application example.

[0047] Figure 2 FIG. is a schematic diagram of another communication scenario applicable to the method provided in this application example.

[0048] Figure 3 FIG. is a schematic diagram of a gNB architecture provided in this application example.

[0049] Figure 4 FIG. is a schematic diagram of a radio access network device (i.e., network device) provided in this application example.

[0050] Figure 5 FIG. is a schematic diagram of a user plane protocol layer structure between a network device and a terminal device provided in this application example.

[0051] Figure 6 FIG. is a schematic diagram of a control plane (or also referred to as a signaling plane) protocol layer structure between a terminal device and a network device provided in this application example.

[0052] Figure 7 FIG. is a schematic flowchart of a method for RRC signaling transmission provided in this application example.

[0053] Figure 8 FIG. is a schematic diagram of a form of configuring NZP CSI-RS resources (NZP CSI-RS-Resource) of a first CC provided in this application example.

[0054] Figure 9 FIG. is a schematic diagram of a form of adding an SCC list (scc_List SEQUENCE) under NZP CSI-RS resources of a first CC provided in this application example.

[0055] Figure 10 FIG. is a schematic flowchart of another method for RRC signaling transmission provided in this application example.

[0056] Figure 11It is a schematic block diagram of a communication device provided by an embodiment of the present application.

[0057] Figure 12 It is a schematic block diagram of another communication device provided by an embodiment of the present application.

[0058] Figure 13 It is a schematic block diagram of a communication device provided by an embodiment of the present application.

[0059] Figure 14 It is a schematic block diagram of another communication device provided by an embodiment of the present application.

[0060] Figure 15 It is a schematic block diagram of a terminal device provided by an embodiment of the present application.

[0061] Figure 16 It is a schematic block diagram of a network device provided by an embodiment of the present application. Detailed implementation manners

[0062] Next, the technical solutions in the present application will be described with reference to the accompanying drawings.

[0063] In the description of the embodiments of the present application, unless otherwise specified, " / " means "or". For example, A / B may mean A or B. The "and / or" herein is only a description of the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B may mean: A exists alone, A and B exist simultaneously, and B exists alone. In addition, in the description of the embodiments of the present application, "a plurality of" means two or more than two.

[0064] Hereinafter, the terms "first" and "second" are only used for descriptive purposes and cannot be construed as indicating or implying relative importance or implicitly specifying the quantity of the indicated technical features. Thus, the features defined with "first" and "second" may explicitly or implicitly include one or more of such features. In the description of this embodiment, unless otherwise specified, the meaning of "a plurality of" is two or more.

[0065] In the embodiments of the present application, a terminal device or a network device includes a hardware layer, an operating system layer running on top of 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 a memory (also referred to as main memory). The operating system can be any one or more computer operating systems that implement service processing through processes. For example, the Linux operating system, the Unix operating system, the Android operating system, the iOS operating system, or the Windows operating system, etc. The application layer includes applications such as a browser, an address book, a word processing software, and an instant messaging software. Moreover, the embodiments of the present application do not particularly limit the specific structure of the execution subject of the method provided by the embodiments of the present application. As long as it can communicate according to the method provided by the embodiments of the present application by running a program recording the code of the method provided by the embodiments of the present application. For example, the execution subject of the method provided by the embodiments 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 and execute the program.

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

[0067] New Radio (NR) is a new radio access technology (RAT) developed by the 3rd Generation Partnership Project (3GPP) for the 5th generation mobile communication network (5G). It is the global common standard for the air interface of 5G networks. 3GPP specifications define the technical details for NR. The 5G communication system includes non-standalone (NSA) mode and standalone (SA) mode in the networking mode.

[0068] In the SA scenario, the NR protocol stipulates that the maximum packet data convergence protocol (PDCP) service data unit (PDCP SDU) is 9000 bytes. In the NSA scenario, the Long-Term Evolution (LTE) protocol stipulates that the maximum PDCP SDU is 8188 bytes.

[0069] Currently, in order to further increase the transmission rate, the CA technology is supported in the protocol, that is, multiple component carriers (CCs) are aggregated together for data transmission, thereby increasing the bandwidth of data transmission and the data transmission rate. The CA technology can include: in-band continuous CA, in-band discontinuous CA, and inter-band CA. Among them, in-band continuous CA and in-band discontinuous CA can be collectively referred to as intra-frequency CA, and inter-band CA can also be called multi-frequency CA.

[0070] Currently, 5G specifies two frequency bands, namely Frequency Range 1 (FR1) and Frequency Range 2 (FR2). FR1 refers to the sub-6 GHz frequency band, covering the range between 450 MHz and 7125 MHz. The operating frequency band of FR2 is between 24.25 GHz and 52.6 GHz, that is, the millimeter wave frequency band. In the protocol versions before and including R17, for FR2, the intra-frequency CA can reach 800 M. The multi-frequency CA of FR1 and FR2 can support a bandwidth greater than 800 M. For CA, the number of CCs included can be 9 CCs. In the protocol versions after R18, for CA, the number of CCs included can be 10 CCs.

[0071] The Channel State Information - Reference Signal (CSI - RS) is a very important reference signal in 5G. The CSI - RS is mainly used in the following aspects:

[0072] Obtaining channel state information: It is 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 the precoding matrix, channel quality information, etc.;

[0073] Beam management: It is used to obtain the shaping weights of the beams on the terminal device and base station sides, and support beam measurement during the beam management process;

[0074] Time - frequency tracking: It is used for accurate time - frequency synchronization tracking and obtaining Quasi Co - Location (QCL) parameters. In this case, the CSI - RS can also be called the Tracking Reference Signal (TRS);

[0075] Mobility management: It is used to complete measurements related to mobility management;

[0076] Interference measurement: The CSI - RS can also be used for Interference Measurement (IM). In this case, the CSI - RS can also be called CSI IM.

[0077] Rate matching: It is used for the Rate Matching of the Physical Downlink Share Channel (PDCCH).

[0078] 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-RSRP Computation (computing the reference signal receiving power of L1), L1-SINR Computation (computing the signal to interference plus noise ratio of L1), and Mobility management, etc. Among them, L1 RSRP and L1-SINR can be used for beam management. While ZP CSI-RS is mainly used for Rate Matching of the physical downlink share channel (PDCCH). The protocol defines the time-frequency resource sets of NZP CSI-RS and ZP CSI-RS.

[0079] For example, Table 1 shows a schematic table of the specific content and functions included in an example of CSI-RS.

[0080] Table 1

[0081]

[0082] At present, the terminal device can access multiple carriers by means of CA. The multiple carriers can be divided into a primary carrier component (PCC) and secondary carrier components (SCCs). Generally, the serving cell for the terminal can include a primary cell (PCell) and one or more secondary cells (Scells). The PCell can be determined during the initial connection establishment or reconnection process. The PCell operates on the PCC. The Scell is a cell added through RRC reconfiguration to provide additional frequency band resources. One Scell operates on one SCC. The terminal device only initiates the random access process on the PCC. The PCC is always in the active state, while the SCC can be added / modified / released through the RRC connection reconfiguration message (RRC ConnectionReconfiguration). Each CC corresponds to one cell.

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

[0084] For NZP CSI-RS, except for the NZP CSI-RS used for mobility management, the NZP CSI-RS used for time / frequency tracking, CSI computation, L1-RSRP computation, and L1-SINR computation, and the CSI-RS resources 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 (NZPCSI-RSResource), one or more CSI-IM resources (CSI-IM-Resource), or one or more system synchronization block (System Synchronization Block SSB) resources (CSI-SSB-Resource). Among them, the 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 NZPCSI-RS for the above purposes and the time-frequency resources of CSI-IM.

[0085] 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 CSI-IM on this CC for the terminal device through the CSI measurement configuration information element (CSI-MeasConfig IE) in the RRC signaling. Since a terminal may access multiple CCs through the CA method, with the continuous increase of CCs and bandwidths, the RRC signaling needs to configure the time-frequency resources of the NZP CSI-RS resources or CSI-IM corresponding to each of these multiple CCs respectively, resulting in an increase in the overhead (or length) of the RRC signaling and requiring more communication resources to transmit the RRC, increasing the consumption of communication resources.

[0086] Currently, a technique of RRC segmentation 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 (e.g., 9000 bytes or 8188 bytes), this RRC signaling can be segmented or fragmented into multiple segments at the RRC layer, and each segment is transmitted using a separate RRC PDU. The receiving device reassembles the received multiple segments to obtain the complete RRC signaling. All segments of an RRC signaling need to be sent before another RRC signaling is sent, and RRC segmentation supports both uplink and downlink.

[0087] However, the RRC segmentation technique cannot fundamentally solve the problem of large overhead of RRC signaling. For example, in a scenario where the base station configures the NZP CSI-RS resources and CSI-IM resources corresponding to each CC for a terminal device using RRC signaling, since the number of CCs that the terminal device accesses may be relatively large, the length of the RRC signaling is large. Even if the RRC segmentation technique is adopted, the number of segments needs to be continuously expanded, and the splitting, transmission, and reassembly of the RRC signaling will all bring problems such as performance and reliability. This reduces the reliability of RRC signaling transmission, and also cannot solve the problem of the large length (large overhead) of the RRC signaling.

[0088] In view of this, the present application provides a method and a communication device for RRC signaling transmission. In a carrier aggregation scenario, if the CSI-RS resource configuration of a certain carrier (e.g., the first carrier) is the same as the CSI-RS resource configurations 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 configurations corresponding to other CCs. Then, 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 can also be added to the CSI-RS resource configuration part of other carriers in the RRC, and then 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.

[0089] It can be understood that the method provided by the present application can be applied in a carrier aggregation scenario.

[0090] For example, Figure 1 The following shows a schematic diagram of a communication scenario applicable to the method provided by the present application, asFigure 1 As shown, communication is carried out between the terminal device and the network device. In the CA mode, the terminal device can communicate with the network device respectively on multiple CCs ( Figure 1 As shown, there are 3 CCs), and communicate with the network device respectively on multiple CCs. Among the multiple CCs, one is the PCC, and the others are all SCCs. The terminal device can communicate with the network device through these CCs (including PCC and SCC). When the network device configures NZP CSI-RS resources and CSI-IM resources for each CC by using RRC, the method of RRC signaling transmission provided in this application can be used.

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

[0092] For example, in the non-standalone networking Option 3 series architecture, the 4G base station serves as the control plane anchor point, which is called the Master Node, and the 5G base station is called the Secondary Node. Both the Master Node and the Secondary Node can perform carrier aggregation. Optionally, the primary carrier and the secondary carrier of the Master Node can also be called Pcell and Scell, and the primary carrier and the secondary carrier of the Secondary Node are called PScell and Scell. The Master Node and the Secondary Node with carrier aggregation can also be called MCG (Master Cell Group) and SCG (Secondary Cell Group). When the network device configures NZP CSI-RS resources and CSI-IM resources for each CC by using RRC, the method of RRC signaling transmission provided in this application can be used.

[0093] It should be understood that Figure 1 or Figure 2 The communication scenario (communication system) shown is only exemplary and should not impose any limitation on the communication scenarios applicable to the embodiments of this application. For example, Figure 1 or Figure 2The communication system shown may also include more or fewer network nodes, such as terminal devices or network devices. Or the number of aggregated CCs between the terminal device and the network device may also be more. It can be understood that the method provided in this application can be applied to any carrier aggregation scenario.

[0094] Exemplarily, Figure 1 Or Figure 2 The communication system shown may be a cellular system related to the 3rd 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 or 5G mobile communication system (including stand-alone and non-stand-alone networking), NR, or a future evolution system (such as a 6G mobile communication system). Or, it may also be an open radio access network (O-RAN), a cloud radio access network (CRAN), or a wireless fidelity (WiFi) system, or it may also be a communication system that is a fusion of two or more of the above systems. The embodiments of this application do not limit this here.

[0095] Optionally, in the embodiments of this application, the network device may also be referred to as: an access network device, a radio access network device, a radio access network (RAN) node, a RAN entity, or an access node, etc., which forms part of the communication system and is used to help the terminal device achieve wireless access.

[0096] In a possible scenario, the network device can be any device with wireless transceiver capabilities. For example, it includes: traditional macro base stations (evolved node B, eNB) in Universal Mobile Telecommunications System (UMTS) and LTE communication systems, micro base station eNBs in a Heterogeneous Network (HetNet) scenario, BaseBand Unit (BBU) and Remote Radio Unit (RRU) in a distributed base station scenario, BBU pool RRU in a Cloud Radio Access Network (CRAN) scenario, gNBs, base stations evolved by 3GPP in future wireless communication systems, access nodes in WiFi systems, wireless relay nodes, wireless backhaul nodes, etc. For example, the base station can be: macro base station, micro base station, pico base station, small station, relay station, or balloon station, etc.

[0097] In another possible scenario, the network device can be a base station, evolved NodeB (eNodeB), access point (AP), transmission reception point (TRP), next-generation base station in a 6th generation (6G) mobile communication system, base station in a future mobile communication system, etc. Optionally, the network device can also be a relay node or a host node, or a wireless controller in a CRAN scenario. Optionally, the network device can 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 can also be implemented by software functions running on hardware, or by virtualized functions instantiated on a platform (such as a cloud platform). The network device in this application can also be a logical node, logical module, or software that can implement all or part of the functions of a radio access network device.

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

[0099] If the control plane and user plane separation architecture is considered, the gNB-CU can be further divided into a Central Unit-Control Plane (CU-CP) entity (or also referred to as a CU-CP node) and a Central Unit-User Plane (CU-UP) entity (or also referred to as a CU-UP node). Among them, the gNB-CU-CP is a control plane entity for providing signaling control, and the gNB-CU-UP is a user plane entity for providing the transmission of terminal device data. The gNB-CU-CP and the gNB-CU-UP are connected through the E1 interface, the gNB-CU-CP and the gNB-DU are connected through the F1-C interface, and the gNB-CU-UP and the gNB-DU are connected through the F1-U interface. Its structure is as Figure 3 shown, Figure 3 which is a schematic diagram of the architecture with the separation of the gNB-CU-CP and the gNB-CU-UP.

[0100] For the architecture as Figure 3 shown, it also has the following characteristics:

[0101] One gNB will include one gNB-CU-CP, multiple gNB-CU-UPs, and multiple gNB-DUs;

[0102] One DU can only be connected to one gNB-CU-CP;

[0103] One CU-UP can only be connected to one gNB-CU-CP;

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

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

[0106] It should be understood that Figure 3 this is only exemplary and should not impose any limitations on the architecture of the gNB. For example, in the architecture with CU-DU separation and CP-UP separation, the gNB can include only one gNB-CU-UP, one gNB-CU-CP, and one gNB-DU, or it can also include more gNB-CU-UPs and gNB-DUs. This application does not limit this here.

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

[0108] In different systems, the 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, the CU may also be called an O-CU (Open CU), the DU may also be called an O-DU, the CU-CP may also be called an O-CU-CP, the CU-UP may also be called an O-CU-UP, and the RU may also be called an O-RU. For ease of description, the CU, CU-CP, CU-UP, DU, and RU are used as examples in this application. Any of the CU (or CU-CP, CU-UP), DU, and RU in this application may be implemented by a software module, a hardware module, or a combination of a software module and a hardware module.

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

[0110] Optionally, the CU and DU can 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 (such as the RRC layer and / or the service data adaptation protocol (SDAP) layer, etc.); the DU is configured to implement the protocol layers below the PDCP layer (such as the radio link control (RLC) layer, the media access control (MAC) layer, and / or the physical (PHY) layer, etc.). Another example is that the CU is configured to implement 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 protocol layers at and below the PDCP layer (such as the RLC layer, the MAC layer, and / or the PHY layer, etc.).

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

[0112] The CU-CP can interact with the network element in the core network that is used to implement the control plane function. The network element in the core network that is used to implement the control plane function can be an access and mobility management function network element. For example, the access and mobility management function network element in the 5G system (access and mobility management function, AMF). This access and mobility management function network element is responsible for mobility management in the mobile network, such as location updates of terminal devices, registration of terminal devices to the network, handovers of terminal devices, etc.

[0113] The CU-UP can interact with the network element in the core network that is used to implement the user plane function. The network element in the core network that is used to implement the user plane function, for example, the user plane function (UPF) in the 5G system, is responsible for forwarding and receiving data in the terminal device.

[0114] The above configurations of the CU and DU are merely examples, and the functions of the CU and DU can also be configured as needed. For example, the CU or DU can be configured to have more protocol layer functions, 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 protocol layers above the RLC layer are set in the CU, and the remaining functions of the RLC layer and the protocol layers below the RLC layer are set in the DU. Another example is that the functions of the CU or DU can be divided according to the service type or other system requirements. For example, divided by latency, the functions that require a small latency for processing are set in the DU, and the functions that do not need to meet this latency requirement are set in the CU.

[0115] The DU and RU can cooperate to jointly 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 baseband functions, and the RU is configured to implement mid-RF functions. Another example is that 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 implement the low-layer functions and RF functions. The high-layer functions in the physical layer can include a part of the functions of the physical layer, and this part of the functions is closer to the MAC layer. The low-layer functions in the physical layer can include another part of the functions of the physical layer, and this part of the functions is closer to the mid-RF side.

[0116] In the embodiments of this application, the terminal device can also be referred to as a terminal, user equipment (UE), mobile station, mobile terminal, etc. The terminal can be widely used in various scenarios. For example, D2D, V2X communication, machine-type communication (MTC), Internet of Things (IOT), virtual reality, augmented reality, industrial control, autonomous driving, remote medical treatment, smart grid, smart furniture, smart office, smart wearables, 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 this application do not limit the device form of the terminal.

[0117] The protocol stack structure between the terminal device and the network device is described below by way of example.

[0118] Figure 5 The following shows a schematic diagram of the user plane protocol layer structure between a network device and a terminal device. As Figure 5As shown, the user plane protocol layer structure may include functions of protocol layers such as the PDCP layer, RLC layer, MAC layer, and PHY layer. Among them, the physical layer is located at the lowest layer (layer one), the MAC layer, RLC, and PDCP belong to the second layer (layer two), and the RRC belongs to the third layer (layer three). Optionally, an SDAP layer may also be included above the PDCP layer.

[0119] Figure 6 As shown is a schematic diagram of the control plane (or also referred to as the signaling plane) protocol layer structure between a terminal device and a network device.

[0120] As Figure 6 As shown, the control plane protocol layer structure of the terminal device and the network device may include functions of 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, a non-access stratum (NAS) protocol may also exist in the terminal device. The NAS layer in the terminal device communicates with the NAS layer in the access and mobility management function (AMF) of the core network device through the network device. Exemplarily, the main functions of the NAS layer include: supporting general processes for terminal device mobility such as authentication, authorization, general terminal device configuration update, and security control mode processes; supporting session management processes to establish and maintain a data connection between the terminal device and the data network, etc.

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

[0122] The following uses specific examples to illustrate the RRC signaling transmission method provided by the present application.

[0123] It should be understood that in the embodiments of the present application, the network device and the terminal device are taken as an example of the execution subject of the method to illustrate the method. By way of example and not limitation, the terminal device in the present application may also be a chip, chip system, or processor that supports the terminal device to implement the method. The embodiments of the present application do not limit this here. The network device in the present application may also be a chip, chip system, or processor that supports the network device to implement the method, or may also be a logical node, logical module, or software that can implement all or part of the functions of the network device.

[0124] The following is a detailed description of the method provided by this application in conjunction with Figure 7 to describe in detail the method provided by this application. Figure 7 is a schematic flowchart of a method for RRC signaling transmission according to an embodiment of this application. The method 700 can be applied to Figure 1 or Figure 2 the scenarios or communication architectures shown, and of course, it can also be applied to other communication scenarios or communication architectures with carrier aggregation. The embodiments of this application do not limit this here.

[0125] As Figure 7 shown, Figure 7 the method 700 shown in Figure 7 may include S710 to S720. The following is a detailed description of each step in the method 700 in conjunction with

[0126] S710, the network device sends an RRC signaling to the terminal device. The RRC signaling includes the CSI-RS resource configuration corresponding to the first CC and indication information, 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 configurations corresponding to at least one CC. Wherein, the CSI-RS resource configuration includes at least one of the NZP CSI-RS resource configuration or the CSI-IM resource configuration.

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

[0128] Optionally, in the embodiments of this application, the NZP CSI-RS can be used for time / frequency tracking, CSI computation, L1-RSRP computation, L1-SINR computation, etc. For example, when the ZP CSI-RS is used for time / frequency tracking, the NZP CSI-RS can be a TRS.

[0129] Of course, in the embodiments of this application, the NZP CSI-RS can also be used for mobility management.

[0130] For ease of description, in the following examples, the NZP CSI-RS resource configuration for time / frequency tracking, CSI computation, L1-RSRP computation, and L1-SINR computation is used for illustration.

[0131] For ease of understanding, the following examples use the CC list to illustrate the indication information.

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

[0133] Exemplarily, in some possible implementation manners, in scenarios such as cell (a cell can also be referred to as a carrier) handover, cell reconfiguration, cell addition, cell reconstruction, and a cell waking up from the inactive state to the active state, the network device needs to configure the NZP CSI-RS resource for each CC or each cell through the RRC signaling. For example, the network device can configure the NZP CSI-RS resource for each CC through the "CSI-MeasConfig IE" in the RRC signaling.

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

[0135] Of course, in other implementation manners of the present application, the first CC may also be an SCC, and each CC in the CC list is also an SCC.

[0136] 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 to say, the terminal device can communicate with the network device on multiple CCs respectively. The multiple CCs include the first CC and the CCs included in the CC list, and the multiple CCs are all the CCs or cells served by the terminal device.

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

[0138] For example, assume that the terminal device communicates with the network device on M CCs respectively. The first CC among the M CCs can be a PCC, and the other CCs are all SCCs. If, among the M CCs, in addition to the first CC, there are N CCs whose configurations of the NZP CSI-RS resources respectively corresponding to them are the same as the configuration of the NZP CSI-RS resource corresponding to the first CC, the CC list includes the identifiers respectively corresponding to these N CCs.

[0139] It should also be understood that in the embodiments of the present application, when the configuration of the NZP CSI-RS resources corresponding to the first CC and the CC list are included in the RRC signaling, the RRC signaling does not need to include the configuration of the NZP CSI-RS resources corresponding to each CC in the CC list respectively. In other words, it is no longer necessary to configure the 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 an effect of configuration-free.

[0140] For example, assume that the CC list includes 5 CCs. If in the existing manner, it is necessary to configure the NZP CSI-RS resources for these 5 CCs respectively in the RRC signaling, the RRC signaling needs to include 5 groups of fields (or 5 parts), and each group of fields (or each part) configures the NZP CSI-RS resources of one CC respectively. According to the method provided in the embodiments of the present application, only the CC list needs to be added after the configuration of the NZP CSI-RS resources corresponding to the first CC. In this way, it is not necessary to configure the NZP CSI-RS resources for these 5 CCs respectively in the RRC signaling, and the RRC signaling does not need to include these 5 groups of fields (or 5 parts), that is, these 5 groups of fields (or 5 parts) are saved, the length (overhead) of the RRC signaling is reduced, the problem of the large length (large overhead) of the RRC signaling is solved, and the consumption of communication resources by the RRC is reduced.

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

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

[0143] (1), Resource type (resourceType): The NZP CSI-RS resources of the first CC may be configured as periodic, semi-persistent or aperiodic;

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

[0145] (3) Resource mapping: Defines the structure of NZP CSI-RS on the first CC, including the physical resource blocks (PRBs) occupied in the frequency domain.

[0146] (4) Power control offset relative to NZP CSI-RS RE: The power offset of the Physical Downlink Shared Channel Resource Element (PDSCH RE) on the first CC relative to the NZP CSI-RS RE. Exemplarily, the value range is [-8, 15] dB, and the step size is 1 dB.

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

[0148] (6) Scrambling ID: The scrambling ID of the NZP CSI-RS on the first CC.

[0149] (7) Periodicity and offset: The transmission period and slot offset of the periodic or semi-static NZP CSI-RS resource on the first CC.

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

[0151] Of course, the above NZP CSI-RS resource (NZP CSI-RS-Resource) configuration is only exemplary and should not impose any restrictions on the NZP CSI-RS resource configuration in the embodiments of the present application. In other implementation manners of the present application, the NZP CSI-RS resource configuration may further include other contents, which are not limited in the embodiments of the present application.

[0152] 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 above. For example, for the second CC in the CC list, the NZP CSI-RS resource configuration also includes the above items (1) to (8), and the second CC is any CC in the CC list.

[0153] The NZP CSI-RS resource configuration corresponding to each CC in the CC list also includes the above respective configurations, and each configuration of the NZP CSI-RS resource (NZP CSI-RS-Resource) of the second CC is the same as that of the first CC respectively. For example, assuming that the CC list includes the 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 corresponding respective configurations of the first CC.

[0154] For example, the "CSI-MeasConfig" part corresponding to the first CC in the RRC signaling includes: the resource type (resourceType), NZP CSI-RS-Resource identifier (NZP CSI-RS-ResourceId), resource mapping (resourceMapping), power control offset relative to the NZP CSI-RS RE (powerControlOffset), power offset control relative to the SSBRE (powerControlOffsetSS), scrambling ID (scramblingID), periodicity and time slot offset (periodicityAndOffset), reference to the TCI-State (qcl-InfoPeriodicCSI-RS), etc. In some possible implementation manners of the present application, the "CSI-MeasConfig" part corresponding to the first CC may further include a CC list.

[0155] Among them, the "CSI-MeasConfig" part corresponding to each CC in the CC list does not need to include configuration contents such as the resource type (resourceType), NZP CSI-RS-Resource identifier (NZP CSI-RS-ResourceId), resource mapping, power control offset relative to NZP CSI-RS RE, power offset control relative to SSBRE (powerControlOffsetSS), scrambling ID, periodicity and time slot offset, reference to TCI-State (qcl-InfoPeriodicCSI-RS), etc. corresponding to this CC.

[0156] Exemplarily, the form of the NZP CSI-RS resource (NZP CSI-RS-Resource) configuration of the first CC can be as Figure 8 shown.

[0157] Optionally, the CC list can be indicated under the NZP CSI-RS resource configuration of the first CC, that is, the CC list is added to the NZP CSI-RS resource configuration part ("CSI-MeasConfig" part) of the first CC. Exemplarily, the form of adding the SCC list (scc_List SEQUENCE) under the NZP CSI-RS resource of the first CC can be as Figure 9 shown. 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 can 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, improving the accuracy and efficiency of the indication information (i.e., the CC list).

[0158] It should also be understood that "the NZP CSI-RS resource configuration part of the first CC includes a CC list" can also implicitly indicate that the configuration of the NZP CSI-RS resource corresponding to each CC in the CC list is the same as the configuration of the NZP CSI-RS resource corresponding to the first CC. In other words, if the terminal device discovers that the NZP CSI-RS resource configuration of the first CC indicates or includes a CC list after receiving the RRC signaling, the terminal device can determine that the configuration of the NZP CSI-RS resource corresponding to each CC in the CC list is the same as the configuration of the NZP CSI-RS resource corresponding to the first CC. That is to say, the network device and the terminal device have the same understanding of "the NZP CSI-RS resource of the first CC indicates or includes a CC list".

[0159] S720, the terminal device determines the CSI-RS resource configuration information of the CC to which it is connected according to the RRC signaling.

[0160] 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 according to the CSI-RS resource configuration corresponding to the first CC (for example, the NZP CSI-RS resource configuration for time / frequency tracking, CSI computation, L1-RSRP computation, L1-SINR computation, or the 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 corresponding to the CC that needs to be accessed.

[0161] The method for RRC signaling transmission provided by the embodiments of this application, in the scenario of carrier aggregation, if the NZP CSI-RS resource configuration on a certain carrier (which can also be referred to as the corresponding NZP CSI-RS resource configuration on a certain carrier) is the same as the NZP CSI-RS resource configurations on other carriers, indication information (such as a CC list) can be configured in the RRC signaling for the part of the NZP CSI-RS resources on the first carrier, to indicate that the NZP CSI-RS resource configuration on the first carrier is the same as the NZP CSI-RS resource configurations of the CCs in the CC list. In this way, the RRC signaling does not need to include the configuration content of the NZP CSI-RS resources on other carriers. In other words, under the NZP resources corresponding to the first CC, a CC list that can be used is indicated. The NZP CSI-RS resource configurations in the CSI-MeaConfig on each CC included in the CC list can be set by following the CC list in the corresponding resource configuration of the first CC. In this way, 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), 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.

[0162] Of course, in method 700, the indication information is described by taking the CC list as an example. It should be understood that in other implementation manners of this application, the indication information can 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 configurations of certain CCs, and can also indicate which specific CCs these are. The embodiments of this application do not limit this here.

[0163] It should also be understood that taking the NZP CSI-RS resource configuration as an example above, in other implementation manners of this application, the NZP CSI-RS resource configuration in method 700 can also be replaced with the CSI-IM resource (CSI-IM-Resource) configuration. That is to say, the above method can also be used to configure CSI-IM resources for multiple CCs in the RRC. For example, the network device can configure CSI-IM resources for the CC in the "CSI-MeasConfig" in the RRC signaling.

[0164] It should also be understood that in other implementations of this application, the method provided in the embodiments of this application can also be used for the resource configuration of NZP CSI-RS for mobility management or the resource configuration of ZP CSI-RS. If it is for the resource configuration of NZP CSI-RS for mobility management, indication information (such as the above CC list) can be added to the "CSI-RS-ResourceConfigMobility" part corresponding to the first CC in the RRC signaling. If it is for the resource configuration of ZP CSI-RS, indication information (such as the above 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 resource configuration of NZP CSI-RS for mobility management or the resource configuration of ZP CSI-RS corresponding to each CC in the CC list, which 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 the RRC.

[0165] Figure 10 is a schematic flowchart of a method for RRC signaling transmission according to another embodiment of this application. As Figure 10 shown, Figure 10 the method 1000 shown in it may include S1010 to S1020. The following will describe each step in method 1000 in detail in combination with Figure 10 details.

[0166] S1010, the network device sends RRC signaling to the terminal device. The RRC signaling includes the CSI-RS resource configuration corresponding to the first CC. The CSI-RS resource configuration part of the second CC in the RRC signaling includes the 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. Among them, the CSI-RS resource configuration includes at least one of the NZP CSI-RS resource configuration or the CSI-IM resource configuration.

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

[0168] For the manner of the first CSI-RS resource configuration and the specific content included in the CSI-RS resource configuration of the first CC, reference can be made to the description of the corresponding part of the above method 700. For the sake of brevity, it will not be elaborated here.

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

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

[0171] For example, the network device can configure NZP CSI-RS resources or CSI-IM resources for the first CC through the "CSI-MeasConfig IE" in the RRC signaling.

[0172] 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, therefore, the identifier of the first CC can be added to the CSI-RS resource configuration part 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, in the RRC signaling, it is no longer necessary to configure the CSI-RS resources for the second CC, that is, the specific content of the CSI-RS resource configuration on the second CC in the RRC is deleted. An effect of avoiding the configuration of CSI-RS resources on the second CC is achieved. For example, the NZP CSI-RS resource configuration information or CSI-IM resource configuration information on the second CC can be deleted in the RRC.

[0173] Exemplarily, if configured in the existing manner, in the RRC signaling, it is necessary to configure CSI-RS resources for the first CC and the second CC respectively. The RRC signaling needs to include 2 groups of fields (or 2 parts), and each group of fields (or each part) configures the NZP CSI-RS resources of one CC (for example, configuring the above 8 items). According to the method provided in the embodiments 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 smaller than the length of the field used to indicate the "CSI-RS resource configuration corresponding to the second CC". In this way, in the RRC signaling, it is not necessary to configure the CSI-RS resources for the second CC, that is, the CSI-RS resource configuration part corresponding to the second CC in the RRC signaling does not need to include this 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 the large length (large overhead) of the RRC signaling, and reducing the consumption of communication resources by the RRC.

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

[0175] 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 configuration contents such as the resource type (resourceType) corresponding to the second CC, the NZP CSI-RS-Resource identifier (NZP CSI-RS-ResourceId), resource mapping (resourceMapping), power control offset (powerControlOffset) relative to the NZP CSI-RS RE, power offset control (powerControlOffsetSS) relative to the SSB RE, scrambling ID (scramblingID), periodicity and slot offset (periodicityAndOffset), and reference to the TCI-State (qcl-InfoPeriodicCSI-RS).

[0176] It should also be understood that "the CSI-RS resource configuration part 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 determines, after receiving the RRC, that the CSI-RS resource configuration part of the second CC includes the identifier of the first CC, the terminal device may 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. That is to say, 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".

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

[0178] 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 may determine the CSI-RS resource configuration corresponding to the second CC according to the CSI-RS resource configuration corresponding to the first CC (such as the NZP CSI-RS resource configuration for time / frequency tracking, CSI computation, L1-RSRP computation, L1-SINR computation, or the 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.

[0179] In the method for RRC signaling transmission provided by the embodiments of the present application, in the scenario of carrier aggregation, if the CSI-RS resource configuration on a certain carrier (for example, the first CC) is the same as the CSI-RS resource configuration on another carrier (the second CC), the identifier of the first CC may be added to the part of the CSI-RS resources of the second carrier configured 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. The specific configuration information of the CSI-RS resources on the second CC does not need to be included in the RRC, 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.

[0180] It should also be understood that taking the NZP CSI-RS resource configuration as an example above, in other implementation manners of the present application, the NZP CSI-RS resource configuration in method 1000 may also be replaced by the CSI-IM resource (CSI-IM-Resource) configuration. That is, the above method may also be used to configure CSI-IM resources for multiple CCs in the RRC. For example, the network device may configure CSI-IM resources for the CC in the "CSI-MeasConfig" in the RRC signaling.

[0181] It should also be understood that in other implementation manners of this application, the method provided by the embodiments of this application can also be used for the resource configuration of NZP CSI-RS for mobility management or the resource configuration of ZP CSI-RS. If it is for the resource configuration of NZP CSI-RS 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 for the resource configuration of ZP CSI-RS, 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 resource configuration of NZP CSI-RS for mobility management or the resource configuration of ZP CSI-RS corresponding to the second CC, which 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 the RRC.

[0182] It should be understood that the above is only to help those skilled in the art better understand the embodiments of this application, rather than to limit the scope of the embodiments of this application. Those skilled in the art can obviously make various equivalent modifications or changes according to the above examples. For example, some steps in the above method embodiments may not be necessary, or some steps may be newly added, etc. Or any combination of any two or any more of the above embodiments. The solutions after such modifications, changes or combinations also fall within the scope of the embodiments of this application.

[0183] It should also be understood that the manners, situations, categories, and the division of embodiments in the embodiments of this application are only for the convenience of description and should not constitute a special limitation. The features in various manners, categories, situations, and embodiments can be combined without conflict.

[0184] It should also be understood that the various digital numbers involved in the embodiments of this application are only for the convenience of description and are not used to limit the scope of the embodiments of this application. The magnitudes of the serial numbers of the above processes do not mean the order of execution. The order of execution of each process should be determined by its function and internal logic and should not constitute any limitation to the implementation process of the embodiments of this application.

[0185] It should also be understood that the above description of the embodiments of this application emphasizes the differences between the various embodiments. The same or similar parts not mentioned can be referred to each other. For the sake of brevity, they will not be elaborated here.

[0186] The above combination Figures 1 to 10 has made a detailed description of the method of the embodiments of this application. Next, in combination with Figures 11 to 16 a detailed description of the communication device of the embodiments of this application will be given.

[0187] In this embodiment, the functional modules of the terminal device and the network device can be divided according to the above method. For example, each function can correspond to a respective functional module, or two or more functions can be integrated into one processing module. The above integrated module can be implemented in the form of hardware. It should be noted that the division of modules in this embodiment is illustrative and is only a logical function division. There can be other division methods in actual implementation.

[0188] It should be noted that the relevant content of each step involved in the above method embodiment can be cited in the function description of the corresponding functional module, and will not be elaborated here.

[0189] The terminal device and the network device provided in the embodiment of the present application are used to execute any one of the RRC signaling transmission methods provided in the above method embodiment, and thus can achieve the same effect as the above implementation method. In the case of adopting an integrated unit, the terminal device or the network device may include a processing module, and optionally a 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 the network device. For example, it can be used to support the terminal device or the network device to execute the steps performed by the processing unit. The storage module can be used to support the storage of program codes and data, etc. The communication module can be used to support the communication between the terminal device or the network device and other devices.

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

[0191] Exemplarily, Figure 11 FIG. shows a schematic block diagram of a communication device 1100 according to an embodiment of the present application. The communication device 1100 can correspond to the network device described in the above method 700 or method 1000, or can 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 method 700 or method 1000.

[0192] Such as Figure 11As shown, the device 1100 may include a processing unit 1110 and a transceiver unit 1120. The transceiver unit 1120 is configured to perform specific signal transceiver 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 a communication module.

[0193] In some embodiments:

[0194] The processing unit 1110 is configured to: generate RRC signaling, the RRC signaling includes CSI-RS resource configuration corresponding to the 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 configurations 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 configurations corresponding to the at least one CC respectively.

[0195] The transceiver unit 1120 is configured to: transmit the RRC signaling.

[0196] For the communication device provided in this application, in the scenario of carrier aggregation, if the CSI-RS resource configuration on the first CC is the same as the CSI-RS resource configurations on other carriers, indication information (such as a CC list) may be added to the part of the CSI-RS resources configuration on the first carrier in the RRC signaling, which is used to indicate that the CSI-RS resource configuration on the first carrier is the same as the CSI-RS resource configurations on the CCs in the CC list. Then 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 the large length (large overhead) of the RRC signaling, and reduces the consumption of communication resources by the RRC.

[0197] In some possible implementation manners, the indication information includes a CC list, and the CC list includes identifiers corresponding to at least one CC respectively.

[0198] In some possible implementation manners, the CSI-RS resource configuration includes at least one of NZP CSI-RS resource configuration or CSI-IM resource configuration.

[0199] In some possible implementation manners, the first CC is a PCC, and the at least one CCs are all SCCs.

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

[0201] In some other embodiments:

[0202] The processing unit 1110 is configured to: generate RRC signaling, where the RRC signaling includes CSI-RS resource configuration corresponding to a first CC, and the CSI-RS resource configuration part 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 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.

[0203] The transceiver unit 1120 is configured to: transmit the RRC signaling.

[0204] In the communication device provided in this application, in a carrier aggregation scenario, if the CSI-RS resource configuration on a certain carrier (for example, the first CC) is the same as the CSI-RS resource configuration on another carrier (the second CC), an identifier of the first CC may be added to the part of the CSI-RS resource configuration of the second carrier in the RRC signaling, 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. The specific configuration information of the CSI-RS resources on the second CC does not need to be included in the RRC, 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.

[0205] In some possible implementation manners, the CSI-RS resource configuration includes at least one of NZP CSI-RS resource configuration or CSI-IM resource configuration.

[0206] In some possible implementation manners, the first CC is a PCC or an SCC, and the second CC is an SCC.

[0207] In some possible implementation manners, 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.

[0208] It should be understood that for the specific processes of each unit in the communication device 1100 to execute the above corresponding steps, please refer to the descriptions related to the network device in the relevant embodiments of method 700 or method 1000 in the foregoing. For the sake of brevity, details are not described here.

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

[0210] Further, the communication device 1100 may further include a storage unit. The transceiver unit 1120 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 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 by the storage unit, and the transceiver unit 1120 is configured to perform specific signal transceiver under the control of the processing unit 1110.

[0211] 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 Figure 12 shown, the communication device 1200 may include a processor 1210, a memory 1220, and a transceiver 1230.

[0212] Figure 11 the communication device 1100 shown or Figure 12 the communication device 1200 shown is capable of implementing the steps performed by the network device in the foregoing method 700 or method 1000. Similar descriptions may refer to the descriptions in the foregoing corresponding methods. To avoid repetition, they are not elaborated here.

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

[0214] Exemplarily, Figure 13 shows a schematic block diagram of a communication device 1300 according to an embodiment of the present application. The communication device 1300 may correspond to the terminal device described in the foregoing 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 configured to perform each action or processing procedure performed by the terminal device in any one of the foregoing method 700 or method 1000.

[0215] As Figure 13 shown, the communication device 1300 includes a transceiver unit 1310 and a processing unit 1320. The transceiver unit 1310 is configured to perform specific signal transceiver under the control of the processing unit 1320.

[0216] In some embodiments:

[0217] The transceiver unit 1310 is configured to: receive RRC signaling, where the RRC signaling includes the CSI-RS resource configuration and indication information corresponding to a 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 configurations corresponding to at least one CC, both the first CC and the at least one CC are carriers serving the terminal device, and the RRC signaling does not include the CSI-RS resource configurations corresponding to the at least one CC respectively.

[0218] The processing unit 1320 is configured to: determine the CSI-RS resource configurations corresponding to the at least one CC respectively according to the RRC signaling.

[0219] In the communication device provided in this application, in the scenario of carrier aggregation, if the CSI-RS resource configuration on the first CC is the same as the CSI-RS resource configurations of other carriers, indication information (such as a CC list) can be added to a part of the CSI-RS resource configuration on the first carrier in the RRC signaling, which is used to indicate that the CSI-RS resource configuration on the first carrier is the same as the CSI-RS resource configurations of the CCs in the CC list. Then, 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 the large length (large overhead) of the RRC signaling, and reduces the consumption of communication resources by the RRC.

[0220] In some possible implementation manners, the indication information includes a CC list, and the CC list includes the identifiers corresponding to the at least one CC respectively.

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

[0222] In some possible implementation manners, the first CC is a PCC, and the at least one CC are all SCCs.

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

[0224] In some other embodiments: The transceiver unit 1310 is configured to: receive RRC signaling, where 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.

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

[0226] In the communication device provided in this application, in the scenario of carrier aggregation, if the CSI-RS resource configuration on a certain carrier (for example, the first CC) is the same as the CSI-RS resource configuration on another carrier (the second CC), the identifier of the first CC can be added to the part of the CSI-RS resource configuration of the second carrier in the RRC signaling, 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. The specific configuration information of the CSI-RS resources on the second CC does not need to be included in the RRC, 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.

[0227] In some possible implementation manners, the CSI-RS resource configuration includes at least one of NZP CSI-RS resource configuration or CSI-IM resource configuration.

[0228] In some possible implementation manners, the first CC is a PCC or an SCC, and the second CC is an SCC.

[0229] In some possible implementation manners, 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.

[0230] Furthermore, the communication device 1300 may further 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 the 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 mutually coupled, the storage unit stores instructions, the processing unit 1320 is used to execute the instructions stored by the storage unit, and the transceiver unit 1310 is used to perform specific signal transceiver under the control of the processing unit 1320.

[0231] It should be understood that for the specific processes of each unit in the communication device 1300 to execute the above corresponding steps, please refer to the descriptions related to the terminal device in the relevant embodiments in the foregoing method 700 or method 1000. For the sake of brevity, no further elaboration will be provided here.

[0232] 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.

[0233] Exemplarily, as Figure 14 shown, the communication device 1400 may include a processor 1410, a memory 1420, a transceiver 1430, and a bus system 1440. Each component of the communication device 1400 is coupled together through the bus system 1440. In addition to the data bus, the bus system 1440 may further include a power bus, a control bus, a status signal bus, etc. However, for the sake of clear illustration, in Figure 14 all kinds of buses are labeled as the bus system 1440. For the convenience of representation, Figure 14 only a schematic diagram is shown in

[0234] Figure 13 The communication device 1300 shown in Figure 14 or the communication device 1400 shown in

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

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

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

[0238] Figure 15 FIG. 1500 is a schematic structural diagram of a terminal device provided in the present application. The above communication device 1300 or communication device 1400 can be configured in the terminal device 1500. Or, the communication device 1300 or communication device 1400 itself can be the terminal device 1500. Or rather, the terminal device 1500 can execute the actions performed by the terminal device in the above method 700 or method 1000. Optionally, for ease of explanation, Figure 15 only the main components of the terminal device are shown. As Figure 15 shown, the terminal device 1500 includes a processor, a memory, a control circuit, an antenna, and an input / output device.

[0239] The processor is mainly used to process communication protocols and communication data, control the entire terminal device, execute software programs, and process the data of software programs. For example, it is used to support the terminal device to perform the actions described in the method embodiments of the above RRC signaling transmission. The memory is mainly used to store software programs and data. For example, it stores the configuration of CSI-RS resources corresponding to each CC described in the above embodiments. The control circuit is mainly used for the conversion between baseband signals and radio frequency signals and the processing of radio frequency signals. The control circuit and the 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 embodiments. The input / output device, such as a touch screen, a display screen, a keyboard, etc., is mainly used to receive data input by the user and output data to the user.

[0240] After the terminal device is powered 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 wirelessly transmitted, the processor performs baseband processing on the data to be transmitted and then outputs a baseband signal to the radio frequency circuit. The radio frequency circuit performs radio frequency processing on the baseband signal and then transmits the radio frequency signal outward in the form of electromagnetic waves through the antenna. When a signaling (such as the above RRC signaling) is sent to the terminal device, the radio frequency circuit receives the radio frequency signal through the antenna, converts the radio frequency 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.

[0241] Those skilled in the art can understand that, for the sake of convenience of description, Figure 15 only one memory and one processor are shown. In an actual terminal device, there may be multiple processors and memories. The memory can also be referred to as a storage medium or a storage device, etc. The embodiments of the present application do not limit this.

[0242] For example, the processor may include a baseband processor and a central processor. The baseband processor is mainly used to process communication protocols and communication data, and the central processor is mainly used to control the entire terminal device, execute software programs, and process the data of software programs. Figure 15The processor therein integrates the functions of a baseband processor and a central processor. Those skilled in the art can understand that the baseband processor and the central processor can also be separate processors interconnected through technologies such as a bus. Those skilled in the art can understand that the terminal device can include multiple baseband processors to adapt to different network modes, and the terminal device can include multiple central processors to enhance its processing capacity. Each component of the terminal device can be connected through various buses. The baseband processor can also be referred to as a baseband processing circuit or a baseband processing chip. The central processor can also be referred to as a central processing circuit or a central processing chip. The function of processing communication protocols and communication data can be built into the processor or stored in the storage unit in the form of a software program, and the processor executes the software program to implement the baseband processing function.

[0243] Exemplarily, in the embodiments of the present application, an antenna and a control circuit with transceiver functions can be regarded as the transceiver unit 1501 of the terminal device 1500, and a processor with processing functions can be regarded as the processing unit 1502 of the terminal device 1500. As Figure 15 shown, the terminal device 1500 includes a transceiver unit 1501 and a processing unit 1502. The transceiver unit can also be referred to as a transceiver, a transceiver machine, a transceiver device, etc. Optionally, the device in the transceiver unit 1501 for implementing the receiving function can be regarded as the receiving unit, and the device in the transceiver unit 1501 for implementing the sending function can be regarded as the sending unit, that is, the transceiver unit 1501 includes a receiving unit and a sending unit. Exemplarily, the receiving unit can also be referred to as a receiver, a receiver circuit, etc., and the sending unit can be referred to as a transmitter, a transmitter circuit, etc.

[0244] Figure 16 It is a schematic structural diagram of a network device 1600 provided in the embodiments 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) (which can also be referred to as a digital unit, DU) 1602. The RRU 1601 can be referred to as a transceiver unit, a transceiver machine, a transceiver circuit, or a transceiver, etc., and it can include at least one antenna 16011 and a radio frequency unit 16012. The RRU 1601 part is mainly used for the transceiver of radio frequency signals and the conversion between radio frequency signals and baseband signals, for example, for sending multiple groups of data streams and indication information in the above embodiments to the terminal device. The BBU 1602 part is mainly used for baseband processing and controlling the base station, etc. The RRU1601 and the BBU 1602 can be physically set together or physically separated, that is, a distributed base station.

[0245] The BBU 1602 is the control center of the base station, and can also be referred to as a processing unit, mainly used to complete baseband processing functions such as channel coding, multiplexing, modulation, spreading, 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 embodiments.

[0246] In one example, the BBU 1602 can be composed of one or more single boards. The multiple single boards can jointly support a radio access network of a single access mode (such as an LTE system or a 5G system), or can separately support radio access networks of different access modes. 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 the first DCI in the above embodiments and information such as the uplink precoding matrix corresponding to the uplink resources with sub-band granularity. The processor 16022 is used to control the base station to perform necessary actions, for example, to control the base station to execute the operation process of the network device in the above method embodiments. The memory 16021 and the processor 16022 can serve one or more single boards. That is to say, a memory and a processor can be separately set on each single board. It is also possible that multiple single boards share the same memory and processor. In addition, necessary circuits can be provided on each single board.

[0247] In a possible implementation manner, with the development of system-on-chip (SoC) technology, all or part of the functions of the 1602 part and the 1601 part can be implemented by SoC technology. For example, it can be implemented by a base station function chip, which integrates devices such as a processor, a memory, and an antenna interface. The programs related to the base station functions are stored in the memory, and the processor executes the programs to implement the related functions of the base station. Optionally, the base station function chip can also read the external memory of the chip to implement the related functions of the base station.

[0248] It should be understood that Figure 16 The structure of the exemplary network device 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.

[0249] 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 (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

[0250] It should also be understood that the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an EPROM, an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example 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), synchlink DRAM (SLDRAM), and direct rambus RAM (DR RAM).

[0251] The embodiments of the present application further provide a communication system, which includes the above-mentioned terminal device and network device.

[0252] The above embodiments can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. 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 programs are loaded or executed on a computer, the processes or functions according to the embodiments of the present application are 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. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wired (such as infrared, wireless, microwave, etc.) means.

[0253] The embodiments of the present application also provide a computer-readable medium for storing computer program code. The computer program includes instructions for executing any of the methods for RRC signaling transmission provided in the embodiments of the present application. The readable medium can be the memory in the above examples, and the embodiments of the present application do not limit this.

[0254] The present application also provides a computer program product. The computer program product includes instructions that, when executed, cause the terminal device to perform operations corresponding to those of the terminal device in the above method, or cause the network device to perform operations corresponding to those of the network device in the above method.

[0255] The embodiments of the present application also provide a chip, which includes a processing unit and a communication unit. The processing unit can be, for example, a processor, and the communication unit can be, for example, an input / output interface, a pin, or a circuit. The processing unit can execute computer instructions to cause the chip in the communication device to execute any of the methods for RRC signaling transmission provided in the embodiments of the present application.

[0256] Optionally, any of the communication devices provided in the embodiments of the present application can include this chip.

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

[0258] Optionally, the storage unit is a storage unit within the chip, such as a register, cache, etc., or the storage unit can also be a storage unit outside the chip within the communication device, such as a ROM or other types of static storage devices that can store static information and instructions, a RAM, etc. Among them, the processor mentioned anywhere above can be a CPU, a microprocessor, an ASIC, or an integrated circuit for executing one or more programs for controlling the above-mentioned RRC signaling transmission method. The processing unit and the storage unit can be decoupled and separately arranged on different physical devices, and are 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 various functions in the above embodiments. Alternatively, the processing unit and the memory can also be coupled on the same device.

[0259] The terms "system" and "network" are often used interchangeably in this document. The term "and / or" in this document is merely a description of the association relationship between associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone. In addition, the character " / " in this document generally represents an "or" relationship between the associated objects before and after.

[0260] In this application, names may be assigned to various objects such as various messages / information / devices / systems / devices / actions / operations / processes, etc. It can be understood that these specific names do not constitute a limitation on the relevant objects, and the assigned names can be changed according to factors such as the scenario, 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 reflected / executed in the technical solution.

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

[0262] In 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 illustrative. For example, the division of the unit is only a logical function division, and there can be other division methods in actual implementation. For example, 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 displayed or discussed coupling or direct coupling or communication connection to each other can be through some interfaces, and the indirect coupling or communication connection of the device or unit can be in an electrical, mechanical, or other form.

[0263] The unit described as a separation component may or may not be physically separated. The component shown as a unit may or may not be a physical unit, that is, it may be located in one place or distributed over multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0264] In addition, each functional unit in various embodiments of the present application may be integrated into one processing unit, may exist separately as individual physical units, or two or more units may be integrated into one unit.

[0265] As mentioned above, the above are only specific embodiments of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art within the technical scope disclosed by the present application can easily think of changes or substitutions, which should all be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A method for RRC signaling transmission, characterized in that, the method includes: sending an RRC signaling, where the RRC signaling includes a CSI-RS resource configuration corresponding to a first CC and indication information, 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 configurations corresponding to at least one CC, and both the first CC and the at least one CC are carriers serving a terminal device.

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

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

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 are all SCCs.

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 includes: sending an RRC signaling, where the RRC signaling includes a CSI-RS resource configuration corresponding to a first CC, and the CSI-RS resource configuration part of a 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 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 includes: Receive an RRC signaling, where the RRC signaling includes a CSI-RS resource configuration corresponding to a first CC and indication information, 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 configurations corresponding to at least one CC, and both the first CC and the at least one CC are carriers serving a terminal device; Determine the CSI-RS resource configurations corresponding to the at least one CC according to the RRC signaling.

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

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

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

16. The method according to any one of claims 12 to 15, wherein, the first CC is a PCC, and the at least one CC are all SCCs.

17. The method according to any one of claims 12 to 16, wherein, 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, wherein, the method includes: Receive an RRC signaling, where the RRC signaling includes a CSI-RS resource configuration corresponding to a first CC, and the CSI-RS resource configuration part 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 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; Determine the CSI-RS resource configuration corresponding to the second CC according to the RRC signaling.

19. The method according to claim 18, wherein, 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, wherein, the CSI-RS resource configuration includes at least one of: a NZP CSI-RS resource configuration or a CSI-IM resource configuration.

21. The method according to any one of claims 18 to 20, wherein, 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, wherein, 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, wherein, includes: A unit for performing each step of the method according to any one of claims 1 to 11, or a unit for performing each step of the method according to any one of claims 12 to 22.

24. A communication device, characterized in that it comprises at least one processor and an interface circuit, and the at least one processor is configured 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 it comprises: a processor, the processor being coupled to a memory for storing programs or instructions, and when the programs or instructions are executed by the processor, the device is caused 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.

26. A computer-readable storage medium, characterized in that a computer program is stored in the computer-readable storage medium, the computer program comprising program instructions which, when executed by a processor, cause the processor 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.

27. A chip, characterized in that it comprises: a processor for calling and running a computer program from a memory, such that a communication device installed with the chip executes: the method according to any one of claims 1 to 11, or the method according to any one of claims 12 to 22.

Images