Communication method and apparatus

Abstract

A communication method and apparatus, belonging to the technical field of communications. The method comprises: receiving first information, the first information being used for indicating that a first synchronization signal block (SSB) and at least one second SSB are quasi-colocated (QCL), and the type of the first SSB being different from the type of the second SSB. On the basis of the above-described solution, the first information can indicate that the first SSB and the at least one second SSB are QCL. In this way, a terminal side can simply measure one SSB among the first SSB or the at least one second SSB, and determine channel characteristics of the unmeasured SSB on the basis of the QCL relationship. In the above-described solution, the terminal side does not need to measure both the first SSB and the at least one second SSB, thereby reducing energy consumption of the terminal side.

Description

Communication methods and devices

[0001] This application claims priority to Chinese Patent Application No. 202411603945.2, filed on November 8, 2024, entitled "Communication Method and Apparatus", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communication technology, and more specifically, to a communication method and apparatus. Background Technology

[0003] When a terminal device is in motion, it can continuously perform cell search and measurement based on a synchronization signal block (SSB), select an appropriate SSB beam, and thus achieve initial access and mobility management. This SSB can also be called an always-on (AO) SSB.

[0004] Furthermore, if there is no demand from the terminal equipment and / or network equipment, the network equipment may not transmit another SSB within the cell (e.g., a secondary cell). If there is demand from the terminal equipment and / or network equipment, the network equipment may transmit the aforementioned SSB within the cell. The aforementioned SSB can also be referred to as an on-demand (OD) SSB.

[0005] However, terminal devices need to measure both SSBs separately, which increases their energy consumption. Therefore, reducing the energy consumption of terminal devices is an urgent problem to be solved. Summary of the Invention

[0006] This application provides a communication method and apparatus that configures quasi-colocation (QCL) relationships of different types of SSBs on the network side, so that the terminal side does not need to measure both types of SSBs, thereby reducing the power consumption on the terminal side.

[0007] Firstly, a communication method is provided. The method provided in this application can be executed by a terminal side. Unless otherwise specified, the terminal side in this application can be the terminal device itself, a component within the terminal device (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the terminal device's functions. For ease of description, the following description will use the terminal side as the executing entity.

[0008] The method includes: receiving first information, wherein the first information is used to indicate that there is a quasi-co-located QCL between a first synchronization signal block (SSB) and at least one second SSB, the type of the first SSB being different from the type of the second SSB.

[0009] Based on the above scheme, the first information can indicate that there is a QCL between the first SSB and at least one second SSB. In this way, the terminal can measure only one of the first SSB or at least one second SSB and determine the channel characteristics of the unmeasured SSB based on the QCL relationship. In this scheme, the terminal does not need to measure both the first SSB and at least one second SSB, thereby reducing the terminal's power consumption.

[0010] In some implementations, the first SSB is an on-demand SSB, and the second SSB is a continuously sent SSB.

[0011] In some implementations, the index of the first SSB is different from the index of the second SSB.

[0012] Based on the above scheme, the QCL relationship between the first SSB and the second SSB can be decoupled from whether the indexes are the same. Compared to a scheme that assumes that only SSBs with the same index can have a QCL relationship, the above scheme can specify that SSBs with different indexes have a QCL relationship, thereby achieving flexible configuration of the QCL relationship.

[0013] In some implementations, the frequency corresponding to the first SSB is different from the frequency corresponding to the second SSB.

[0014] Based on the above scheme, the QCL relationship between the first SSB and the second SSB can be decoupled from whether their frequencies are the same. Compared to a scheme that assumes only SSBs with the same frequency can have a QCL relationship, the above scheme can specify a QCL relationship between SSBs corresponding to different frequencies, thereby achieving a flexible configuration of QCL management.

[0015] In some implementations, the method further includes receiving second information, which indicates that the QCL relationship between the first SSB and the second SSB is of a first type.

[0016] Based on the above scheme, the terminal side can determine the type of QCL relationship between the first SSB and the second SSB through the second information, thereby determining that the first SSB and the second SSB correspond to the same channel characteristics. The terminal side does not need to measure both the first SSB and the second SSB, but can reuse the measured same channel characteristics, thereby reducing the power consumption of the terminal side.

[0017] In some implementations, before receiving the first information, the method further includes: receiving third information, the third information indicating that there is a QCL between the first SSB and at least one third SSB, and that the at least one third SSB is different from the at least one second SSB; wherein, after receiving the first information, the method further includes: determining, based on the first information, the SSB that satisfies the QCL relationship with the first SSB as the at least one second SSB.

[0018] Based on the above scheme, the network side can update the SSBs that satisfy the QCL relationship with the first SSB, thereby ensuring the effectiveness of the QCL mapping relationship on the terminal side.

[0019] In some implementations, the first information is carried in a radio resource control (RRC) message, a media access control (MAC) control element (CE), or downlink control information (DCI).

[0020] Based on the above scheme, the first information can be carried in an RRC message, which is easy to implement. Alternatively, the first information can be carried in a MAC CE or DCI, achieving dynamic indication of the QCL mapping relationship with a shorter latency.

[0021] Secondly, a communication method is provided. The method provided in this application can be executed by the network side. Unless otherwise specified, the terminal side in this application can be the network device itself, a component within the network device (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the functions of the network device. For ease of description, the following description will use the network side as the executing entity.

[0022] The method includes: sending first information, wherein the first information is used to indicate that there is a quasi-co-addressable (QCL) between a first synchronization signal block (SSB) and at least one second SSB, the type of the first SSB being different from the type of the second SSB.

[0023] In some implementations, the method further includes sending a second message indicating that the QCL relationship between the first SSB and the second SSB is of a first type.

[0024] In some implementations, before sending the first information, the method further includes sending a third information, which indicates that there is a QCL between the first SSB and at least one third SSB, and that the at least one third SSB is different from the at least one second SSB.

[0025] Other possible implementations of the second aspect mentioned above can be found in the various possible implementations of the first aspect mentioned above, and will not be repeated here.

[0026] Thirdly, a communication device is provided, including processing circuitry (or a processor) and an input / output interface (also referred to as an interface circuit), the input / output interface being used for inputting and / or outputting signals, the processing circuitry being used to perform the first aspect and any possible method of the first aspect, or the processing circuitry being used to perform the second aspect and any possible method of the second aspect.

[0027] In some implementations, the processing circuitry is used to communicate with other devices via an interface circuitry and to perform the first aspect and any possible method of the first aspect, or to perform the second aspect and any possible method of the second aspect.

[0028] Fourthly, a communication device is provided. This communication device may include units or modules for performing the functions of the communication device.

[0029] In some implementations, the communication device may include modules, units, or means for performing the methods / operations / steps / actions described in the first aspect and any possible implementation of the first aspect. These modules, units, or means may be hardware circuits, software, or a combination of hardware circuits and software.

[0030] The device includes a transceiver unit. The transceiver unit is used to receive first information, which indicates that a quasi-co-located QCL exists between a first synchronization signal block (SSB) and at least one second SSB, wherein the type of the first SSB is different from the type of the second SSB.

[0031] In some implementations, the transceiver unit is also used to receive second information, which indicates that the QCL relationship between the first SSB and the second SSB is of the first type.

[0032] In some implementations, the transceiver unit is further configured to: receive third information indicating that there is a QCL between the first SSB and at least one third SSB, and that the at least one third SSB is different from the at least one second SSB; wherein the apparatus further includes a processing unit. The processing unit is configured to: determine, based on the first information, that the SSB that satisfies the QCL relationship with the first SSB is the at least one second SSB.

[0033] In some implementations, the communication device may include modules, units, or means for performing the methods / operations / steps / actions described in the second aspect and any possible implementation of the second aspect. These modules, units, or means may be hardware circuits, software, or a combination of hardware circuits and software.

[0034] The device includes a transceiver unit. The transceiver unit is used to transmit first information, which indicates that a quasi-co-located QCL exists between a first synchronization signal block (SSB) and at least one second SSB, wherein the type of the first SSB is different from the type of the second SSB.

[0035] In some implementations, the transceiver unit is also used to: send second information, which indicates that the QCL relationship between the first SSB and the second SSB is of a first type.

[0036] In some implementations, the transceiver unit is further configured to: send third information indicating that there is a QCL between the first SSB and at least one third SSB, wherein the at least one third SSB is different from the at least one second SSB.

[0037] Fifthly, a computer-readable storage medium is provided that stores a computer program or instructions that, when executed, cause the first aspect and any possible method of the first aspect to be performed (or implemented), or cause the second aspect and any possible method of the second aspect to be performed (or implemented).

[0038] In a sixth aspect, a computer program product is provided, comprising a computer program or instructions that, when executed, cause the first aspect and any possible method of the first aspect to be performed (or implemented), or cause the second aspect and any possible method of the second aspect to be performed (or implemented).

[0039] A seventh aspect provides a communication device, including a processor for executing (or implementing) any of the possible methods of the first aspect above, or for executing (or implementing) any of the possible methods of the second aspect above, by executing a computer program (or computer-executable instructions) stored in a memory, and / or by logic circuitry.

[0040] In one possible implementation, the device also includes a memory. In another possible implementation, the processor and memory are integrated together. In yet another possible implementation, the memory is located outside the communication device. The processor may include one or more processors.

[0041] In one possible implementation, the communication device further includes a communication interface for communicating with other devices, such as transmitting or receiving data and / or signals. Exemplarily, the communication interface may be a transceiver, circuit, bus, module, or other type of communication interface.

[0042] In one implementation, the communication device of the third, fourth, or seventh aspect mentioned above can be a chip or a chip system.

[0043] Eighthly, a chip is provided, including a processor for calling a computer program or computer instructions in memory to cause any of the implementations of the first aspect to be executed (or implemented), or to cause any of the implementations of the second aspect to be executed (or implemented).

[0044] In some implementations, the processor is coupled to the memory via an interface.

[0045] A ninth aspect provides a communication system including a terminal side and a network side, wherein the terminal side is configured to perform the first aspect and any possible implementation thereof, and the network side is configured to perform the second aspect and any possible implementation thereof.

[0046] The description of the beneficial effects of any implementation of any of the second to ninth aspects can be referred to the description of the beneficial effects of the first aspect. Attached Figure Description

[0047] Figure 1 is a schematic diagram of a communication system.

[0048] Figure 2 is a schematic block diagram of another communication system.

[0049] Figure 3 is a schematic flowchart of a communication method provided in an embodiment of this application.

[0050] Figure 4 is a schematic diagram of beam scanning provided in an embodiment of this application.

[0051] Figure 5 is another schematic diagram of beam scanning provided in an embodiment of this application.

[0052] Figure 6 is another schematic diagram of beam scanning provided in an embodiment of this application.

[0053] Figure 7 is a schematic block diagram of a communication device provided in an embodiment of this application.

[0054] Figure 8 is a schematic diagram of another communication device provided in an embodiment of this application.

[0055] Figure 9 is a schematic diagram of a chip system provided in an embodiment of this application.

[0056] Figure 10 is a schematic diagram of another chip system provided in an embodiment of this application. Detailed Implementation

[0057] In this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of different embodiments are consistent and can be referenced by each other. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0058] I. In this application, "at least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, or B exists alone, where A and B can be singular or plural. In the textual description of this application, the character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, and c can mean: a, or, b, or, c, or, a and b, or, a and c, or, b and c, or, a, b, and c. Here, a, b, and c can each be single or multiple.

[0059] II. In this application, the terms "first," "second," and various numerical designations (e.g., #1, #2, etc.) indicate distinctions made for ease of description and are not intended to limit the scope of the embodiments of this application. For example, they may distinguish different messages, rather than describing a specific order or sequence. It should be understood that such descriptions can be interchanged where appropriate to describe solutions other than those in the embodiments of this application.

[0060] Third, in this application, descriptions such as "when," "under the circumstances," and "if" all refer to the device making corresponding processing under certain objective circumstances, and are not time-limited, nor do they require the device to make a judgment action when implementing it, nor do they imply any other limitations.

[0061] IV. In this application, "instruction" or "for instruction" can include both direct (or explicit) and indirect (or implicit) instruction. When describing instruction information as indicating A, it can include whether the instruction information directly or indirectly indicates A, but does not necessarily mean that the instruction information carries A. For example, in the case of indirect (or implicit) instruction, the receiving end of the instruction information can obtain A based on the parameters indicated by the instruction information, combined with other rules or parameters, or through deduction.

[0062] V. The indication methods involved in the embodiments of this application should be understood to cover various methods that enable the party to be indicated to obtain the information to be indicated. The information to be indicated can be sent as a whole or divided into multiple sub-information and sent separately. Moreover, the sending period and / or sending time of these sub-information can be the same or different. This application does not limit the sending method, for example.

[0063] VI. In this application, "protocol" can refer to standard protocols in the field of communications, such as 5G protocols, new radio (NR) protocols, and related protocols applied to future communication systems; this application does not limit this term. "Predefined" can include predefined terms, such as protocol definitions. "Preconfiguration" can be implemented by pre-storing corresponding codes, tables, or other means that can be used to indicate relevant information in the device; this application does not limit the implementation method.

[0064] VII. In this application, "communication" can also be described as "data transmission," "information transmission," "data processing," etc. "Transmission" includes "sending" and / or "receiving." For example, transmission can be uplink transmission, such as a terminal device sending a signal to a network device; transmission can also be downlink transmission, such as a network device sending a signal to a terminal device; transmission can also be sidelink transmission, such as a terminal device sending a signal to another terminal device. For example, "transmission" can be air interface level transmission, or it can be signal transmission from a chip input (I) / output (O) port, rather than air interface level transmission.

[0065] 8. In this application, terms such as “message”, “information”, “signal” or “information element (IE)” can be used interchangeably. There are no restrictions on the name of the message or information, as long as it can achieve the corresponding function.

[0066] 9. "Sending information to XX (device)" can be understood as the destination of the information being that device. This can include sending information directly or indirectly to that device. "Receiving information from XX (device), or receiving information from XX (device)" can be understood as the source of the information being that device. This can include receiving information directly or indirectly from that device. Information may undergo necessary processing between the source and destination, such as format changes, but the destination can understand the valid information from the source. Similar expressions in this application can be understood in a similar way, and will not be repeated here. Furthermore, "sending" can also be understood as the "output" of the chip interface, and "receiving" can also be understood as the "input" of the chip interface. In other words, "sending" or "receiving" can occur between devices, for example, between network devices and terminal devices via an air interface. "Sending" or "receiving" can also occur within a device, for example, between components, modules, chips, software modules, or hardware modules within the device via a bus, wiring, or interface.

[0067] 10. In this application, terms such as "exemplarily" and "for example" are used to indicate examples, illustrations, or descriptions to present concepts in a specific manner. Any embodiment or design described as an "example" in this application should not be construed as being more preferred or advantageous than other embodiments or designs. In the embodiments of this application, the terms "of," "corresponding (relevant)," "corresponding," and "associated" may sometimes be used interchangeably, and it should be noted that their intended meanings are consistent unless their distinctions are emphasized.

[0068] XI. In this application, configuration can be signaling configuration or can be described as configuring signaling. For example, signaling configuration includes configuration using signaling sent by network devices, which can be radio resource control (RRC) messages, downlink control information (DCI) messages, or system information blocks (SIBs). Another example is signaling configuration between network devices. These network devices can include access network devices, core network devices, or management plane devices, etc. Optionally, signaling configuration can also be configured to terminal devices or network devices using pre-configured signaling, or configured to terminal devices or network devices through pre-configuration. Here, pre-configuration means defining or configuring the values ​​of corresponding parameters in advance using a protocol, and storing them in the terminal device or network device during communication. Pre-configured messages can be modified or updated when the terminal device or network device is connected to the network.

[0069] 12. This application will present various aspects, embodiments, or features relating to systems that may include multiple devices, components, modules, etc. Each system may include devices, components, modules, etc., other than those illustrated, and / or may not include all and all of the devices, components, modules, etc. discussed in conjunction with the accompanying drawings.

[0070] Thirteen, the business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0071] XIV. In the various embodiments of this application, the sequence number of each process does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application. The terms "comprising," "including," "having," and their variations all mean "including but not limited to," unless otherwise specifically emphasized.

[0072] To facilitate understanding of the embodiments of this application, the following is a brief, exemplary description of the concepts that may be involved in the embodiments.

[0073] Carrier aggregation (CA):

[0074] CA (Carrier Aggregator) technology can be used to increase the transmission bandwidth for individual users. For example, CA technology can integrate multi-frequency resources, aggregating spectrum resources in the same or different frequency bands for use by the terminal side, thereby improving overall network resource utilization and enhancing user experience. In some possible implementations, CA can aggregate two or more component carriers (CCs) together to support greater transmission bandwidth.

[0075] In a CA (Connectivity in Context) scenario, the primary cell (PCell) can be the cell where the terminal initiates the initial connection establishment, the cell where radio resource control (RRC) connection reconstruction is performed, or the primary cell designated during handover. For example, the PCell can be responsible for RRC communication between the terminal and the network.

[0076] For example, a secondary cell (SCell) can be added during RRC reconfiguration to provide additional radio resources. In some possible implementations, there may be no RRC communication between the SCell and the terminal side.

[0077] Time-domain resources:

[0078] Taking 5G NR technology as an example, time-domain resources can include other resources such as frames, subframes, slots, symbols, seconds, and milliseconds.

[0079] For example, a frame can also be called a wireless frame. The length of a frame can be 10 ms. The frame number can range from 0 to 1023.

[0080] For example, the length of a subframe can be 1 ms. The subframe number can range from 0 to 9.

[0081] For example, in the case of a normal cyclic prefix (CP), one time slot can include 14 symbols.

[0082] The symbol length can be variable and can be related to the subcarrier spacing (SCS). Thus, although the number of symbols in a time slot can be fixed, the time slot length is also related to the SCS because the symbol length is related to the SCS. For example, with an SCS of 15 kHz, one subframe (which can be 1 ms long) includes one time slot. As another example, with an SCS of 120 kHz, one subframe (which can be 1 ms long) includes eight time slots.

[0083] Synchronization signal block (SSB):

[0084] SSB can also be called synchronization signal / physical broadcast channel block, SSB signal, SSB beam, or other names.

[0085] For example, an SSB may include a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a physical broadcast channel (PBCH). When a terminal device is moving, it can continuously perform cell search and measurement based on the SSB, selecting an appropriate SSB beam to achieve initial access and mobility management. For example, each SSB may occupy four consecutive symbols in the time domain and 20 resource blocks (RBs) in the frequency domain. The 20 RBs may include 240 subcarriers.

[0086] The PSS and SSS can occupy the first and third symbols of the SSB, respectively. Both the PSS and SSS can occupy 127 subcarriers. The PBCH can include the demodulation reference signal (DMRS). The PBCH can occupy the second and fourth symbols of the entire SSB, as well as the third symbol and 48 subcarriers at each end of the frequency domain resources.

[0087] In some possible implementations, the terminal device can obtain the master information block (MIB) information based on the PBCH, thereby obtaining basic information about the cell, such as whether access is prohibited, as well as the location information of system information block type 1 (SIB1). After obtaining the location information of SIB1 according to the MIB information, the terminal device can obtain SIB1 at the location corresponding to that location information, thereby obtaining the remaining basic information required for cell selection during initial network access and the scheduling information of other system information blocks (SIBs). SIB1 can also be referred to as the remaining minimum system information (RMSI).

[0088] In wireless communication systems such as NR, SSBs can be transmitted in the form of beam scanning. For example, a network device can transmit an SSB beam in one direction at a certain moment. Thus, by transmitting SSB beams in different directions at multiple moments, the network device can cover the required directions for the entire cell. For example, assuming that multiple SSB beams are transmitted in different directions in a single beam scan, the entire set of SSB beams transmitted in this round can be called an SSB burst. This SSB burst can also be called an SSB burst set, an SSB burst group, or other names, which are not limited in this application. For ease of understanding, it will be referred to as an SSB burst set below.

[0089] For example, when a terminal device makes its initial access, the default transmission period for the SSB burst set can be 20ms. The transmission window for the SSB burst set can be in units of half frames (e.g., 5ms in length). For example, within the aforementioned 20ms transmission period, the SSB burst set can always be limited to a 5ms time interval, with no SSB beams transmitted for the remaining 15ms.

[0090] In some possible implementations, the SSB burst set will be continuously transmitted according to the configured transmission period, regardless of whether there is a demand from network devices and / or terminal devices. The aforementioned continuously transmitted SSB beam may be called an always-on (AO) SSB, a continuously transmitted SSB, or other names, which are not limited in this application.

[0091] On-demand (OD) SSB:

[0092] In some possible implementations, the network device may not transmit SSBs within the cell (e.g., a secondary cell) if there is no demand from the terminal device and / or network device. If there is a demand from the terminal device and / or network device, the network device may transmit SSBs within the cell. Furthermore, the network device may send signaling to the terminal device instructing it to receive the aforementioned SSBs.

[0093] For example, the aforementioned requirements may include the need to use SSB for cell measurement, time-frequency synchronization, or secondary cell activation. In this way, network devices can dynamically decide whether to transmit SSB within a cell based on whether there is a need. Compared to a strategy of always transmitting SSB (AO SSB), this can save energy consumption for terminal devices and / or network devices.

[0094] The aforementioned on-demand SSB can be called an on-demand (OD) SSB, intermittent SSB, or other names, which are not limited in this application. Similarly, the cell configured with the OD SSB can be called a network energy saving (NES) cell or other names, which are not limited in this application.

[0095] In some possible implementations, after the terminal device establishes a radio resource control (RRC) connection with the network device through the primary cell, the network device can provide the terminal device with the configuration information of the OD SSB on the secondary cell via RRC messages. For example, the configuration information may include the period of the OD SSB, or the number of OD SSB beams, etc. When required, the network device can instruct the terminal device to receive a specifically configured OD SSB after a certain time interval via signaling. For example, the signaling may be carried on RRC messages, MAC CE, or DCI.

[0096] Quasi-colocation (QCL):

[0097] For example, if the channel characteristics (or wireless channel characteristics) of one antenna port can be derived from those of another antenna port, then the two antenna ports can be considered to have a QCL relationship. In other words, for two antenna ports with a QCL relationship, the channel estimation (or measurement) obtained from one antenna port can be applied to the other port.

[0098] The aforementioned antenna port may also be referred to as a port, antenna, or other name, and this application does not limit this. Furthermore, since the channel characteristics at the antenna port can be obtained by channel estimation (or measurement) of a reference signal, the aforementioned antenna port can also be understood as a reference signal. For example, the reference signal may include a channel state information reference signal (CSI-RS), an SSB, a sounding reference signal (SRS), or other signals.

[0099] For example, the aforementioned channel characteristics may include Doppler spread, Doppler frequency shift, average delay, delay spread, or spatial receiver parameters, etc.

[0100] Those skilled in the art will understand that two signals transmitted from the same antenna port can theoretically traverse the same wireless channel. Channel estimation (or measurement) of these two signals will yield the same channel characteristics. Conversely, two signals transmitted from different antenna ports will theoretically traverse different wireless channels. Channel estimation (or measurement) of these two signals may yield different channel characteristics. However, in some cases, two signals transmitted from different antenna ports may traverse similar wireless channels; such antenna ports can be referred to as QCL (Qualitable Channel Closure). In other words, these two antenna ports are QCL.

[0101] QCL can also be called quasi-common position, quasi-co-position, or other names, which are not limited in this application.

[0102] For example, QCL can include four types. These are described below.

[0103] QCL-Type A: Antenna ports with QCL-Type A can have the same Doppler shift, Doppler spread, average delay, and delay spread L. Alternatively, it can be understood that antenna ports with QCL-Type A have the same channel characteristics except for the space receiver parameters.

[0104] QCL-Type B: Antenna ports with QCL-Type B can have the same Doppler shift and Doppler spread. For example, QCL-Type B can be primarily designed for low-frequency applications.

[0105] QCL-Type C: Antenna ports with QCL-Type C can have the same Doppler shift and average delay. For example, QCL-Type B can be used only when the SSB is used as the reference signal for the QCL. Due to the limited resources and density occupied by the SSB, some coarse channel characteristics can be obtained from the SSB, while other channel characteristics can be obtained from other reference signals.

[0106] QCL-Type D: Antenna ports with QCL-Type D can have the same spatial receiver parameters. For example, if two antenna ports are QCL-Type D, then beams in the same direction can be used to receive signals on both ports.

[0107] The types of QCLs may also include other types, which are not limited in this application.

[0108] The technical solutions of this application embodiment can be applied to various communication systems, including but not limited to: Long Term Evolution (LTE) systems, NR systems, and 5G (5G) systems.th This includes various mobile communication systems such as 5G, narrowband Internet of Things (NB-IoT), enhanced machine-type communication (eMTC), enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), satellite communication systems, LTE-machine-to-machine (LTE-M) systems, and other systems that evolve after 5G, such as future mobile communication systems.

[0109] Figure 1 is a schematic diagram of a communication system 100. As shown in Figure 1, the communication system 100 includes a wireless access network 110 and a core network 120. Optionally, the communication system 100 may also include an Internet 130. The wireless access network 110 may include at least one access network device (111a and 111b in Figure 1) and at least one terminal device (112a-112j in Figure 1). The terminal device is connected to the access network device wirelessly. The access network device is connected to the core network 120 wirelessly or via a wired connection. The core network 120 may include one or more core network devices. The core network device and the access network device may be independent physical devices, or the functions of the core network device and the logical functions of the access network device may be integrated on the same physical device, or a single physical device may integrate some of the functions of the core network device and some of the functions of the access network device. Terminal devices and access network devices may be interconnected via wired or wireless connections. Wireless communication can occur between terminal devices, between access network devices, and between terminal devices and access network devices via air interface resources. For example, air interface resources may include at least one of time-domain resources, frequency-domain resources, code resources, and spatial resources. Figure 1 is a schematic diagram; the communication system 100 may also include other access network devices, such as wireless relay devices and wireless backhaul devices, which are not shown in Figure 1.

[0110] Access network equipment can be any device with wireless transceiver capabilities. For example, access network equipment can be a base station used to connect terminal devices to a radio access network (RAN). Access network equipment is sometimes also referred to as an access network element, access network node, RAN node, or RAN. It is understood that the names of devices with access network functionality may differ in systems employing different wireless access technologies. For ease of description, devices providing wireless communication access functionality to terminal devices can be collectively referred to as base stations or RANs. Exemplarily, access network equipment includes, but is not limited to: various forms of macro base stations (as shown in Figure 1, 111a), micro base stations or indoor stations (as shown in Figure 1, 111b), pico base stations, small cells, balloon stations, relay stations, access points, etc. Access network equipment can include evolved node Bs (eNBs or eNodeBs) in LTE, access points (APs), wireless relay nodes, wireless backhaul nodes, transmission points (TRPs or TPs), or transmission reception points (TRPs) in Wi-Fi systems. It can also include next-generation NodeBs (gNBs) or transmission points (TRPs or TPs) in 5G systems, one or a group of antenna panels (including multiple antenna panels) of a base station in a 5G system, and network nodes constituting a gNB or transmission point, such as baseband units (BBUs) or distributed units (DUs). Furthermore, it can include access network equipment, servers, or vehicle-mounted equipment in networks evolving after 5G. Access network equipment can also be modules or units that perform some of the functions of a base station; for example, it can be a central unit (CU) or a DU.

[0111] In this embodiment, the apparatus for implementing the functions of the access network device can be the access network device itself, or it can be an apparatus capable of supporting the access network device in implementing the functions, such as a chip system, which can be installed in the access network device. The chip system can be composed of chips, or it can include chips and other discrete components.

[0112] In another possible scenario, multiple access network devices collaborate to assist the terminal in achieving wireless access, with each device performing a portion of the base station's functions. For example, the access network devices could be a CU, DU, CU (control plane, CP), CU (user plane, UP), or a radio unit (RU). The CU and DU can be separate entities or included in the same network element, such as a BBU. The RU can be included in radio equipment or radio units, such as a remote radio unit (RRU), an active antenna unit (AAU), or a remote radio head (RRH).

[0113] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an open radio access network (O-RAN) system, CU can also be called O-CU (open CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. For ease of description, this application uses CU, CU-CP, CU-UP, DU, and RU as examples. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software modules and hardware modules. The embodiments of this application do not limit the specific technology or specific device form used in the access network equipment.

[0114] Terminal equipment can be a device that provides voice and / or data connectivity to users. Terminal equipment can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; it can also be deployed on water (such as ships); and it can be deployed in the air (such as airplanes, balloons, and satellites). Terminal equipment can also be referred to as user equipment (UE), access terminal, terminal, subscriber unit, user station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, wireless network equipment, user agent, or user device. In this application embodiment, terminal devices include, but are not limited to: cellular phones, mobile phones, wireless data cards, wireless modems, tablets, laptop computers, notebook computers, handheld computers, mobile internet devices (MIDs), computers with wireless transceiver capabilities, cordless phones, session initiation protocol (SIP) phones, smartphones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handsets with wireless communication capabilities, computing devices or other devices connected to wireless modems, in-vehicle devices (e.g., cars, bicycles, electric vehicles, airplanes, ships, trains, high-speed trains, etc.), wearable devices (e.g., smartwatches, smart bracelets, pedometers, smart glasses, etc.), satellite terminals, terminal devices in the Internet of Things or the Internet of Vehicles, as well as any form of terminal in future networks, relay user equipment, or terminals in future evolved public land mobile networks (PLMNs), etc.Terminal devices can also be virtual reality (VR) devices, augmented reality (AR) devices, smart point-of-sale (POS) machines, customer-premises equipment (CPE), light UE, reduced capability UE (REDCAP UE), machine-type communication (MTC) terminals, terminal devices in industrial control, terminal devices in self-driving, terminal devices in telemedicine, terminal devices in smart grids, wireless terminals in transportation safety, terminal devices in smart cities, terminal devices in smart homes, tactile terminal devices, smart home devices (e.g., refrigerators, televisions, air conditioners, electricity meters, etc.), smart robots, robotic arms, workshop equipment, wireless terminals in self-driving, or flying devices (e.g., smart robots, hot air balloons, drones, airplanes), etc. The terminal device can also be a vehicle device, such as a complete vehicle device, an in-vehicle module, an in-vehicle chip, an on-board unit (OBU), or a telematics box (T-BOX). The terminal device can also be other devices with terminal functions; for example, it can be a device that functions as a terminal in device-to-device (D2D) communication. This application does not limit the scope of the embodiments in this regard.

[0115] In this application embodiment, the device for implementing the functions of the terminal device can be the terminal device itself, or it can be any device capable of supporting the terminal device in implementing the functions, such as a chip or chip system. This device can be installed in the terminal device. The chip system can consist of chips or include chips and other discrete components. In the technical solution of this application embodiment, the device for implementing the functions of the terminal device is referred to as the terminal device, which can also be called a terminal. The following description may use a UE (User Equipment) as an example to illustrate the technical solution provided in this application embodiment.

[0116] The roles of base stations and terminals can be relative. For example, the helicopter or drone 112i in Figure 1 can be configured as a mobile base station. For terminals 112j that access the wireless access network 110 via 112i, terminal 112i is a base station; however, for base station 111a, 112i is a terminal, meaning that 111a and 112i communicate via a wireless air interface protocol. Of course, 111a and 112i can also communicate via a base station-to-base station interface protocol. In this case, relative to 111a, 112i is also a base station. Therefore, both base stations and terminals can be collectively referred to as communication devices. 111a and 111b in Figure 1 can be called communication devices with base station functions, and 112a-112j in Figure 1 can be called communication devices with terminal functions.

[0117] Access network devices and terminal devices can communicate via wireless links. The transmission link from the access network device to the terminal device can be called a downlink (DL) or downlink channel, used for transmitting downlink signals. The transmission link from the terminal device to the access network device can be called an uplink (UL) or uplink channel, used for transmitting uplink signals. The transmission link from one terminal device to another can be called a sidelink (SL) or sidelink channel, used for transmitting sidelink signals.

[0118] Figure 2 is a schematic block diagram of another communication system. This communication system may also be referred to as an O-RAN system or other names. The communication system may include a core network, access network equipment (represented as RAN in Figure 2), and a UE. As an example, the communication system may also include other components besides those shown in Figure 2; specific details are not limited in this application.

[0119] Access network devices can communicate with the core network (CN) via a backhaul link. For example, a BBU in an access network device communicates with the core network via a backhaul link. Access network devices can also communicate with UEs via an air interface. For example, an RU in an access network device communicates with at least one UE via an air interface. The BBU communicates with at least one RU via a fronthaul link. The BBU and RU may or may not be co-located; this application does not limit this. The BBU may include at least one CU and at least one DU, and the CU and DU can communicate with each other via at least one midhaul link.

[0120] For example, the CU can be used to perform functions of the upper layer. For instance, the upper layer may include layer 2 (L2) and / or layer 3 (L3). The DU can be used to perform functions of layer 1 (L1) and / or part of L2. The RU can be used to perform computational and digital radio frequency (RF) functions of L1. In some possible implementations, the DU can be deployed as a single unit, i.e., the DU can perform the functions of the DU and RU described above.

[0121] For example, the CU and / or DU may include a chassis platform, motherboard, peripheral devices or cooling devices, etc. The motherboard may include processing units, memory, internal I / O interfaces or external connection ports, etc.

[0122] The processing unit can be a processor, such as one or more of the following: a central processing unit (CPU), an application-specific integrated circuit (ASIC), a digital signal processor (DSP), a microprocessor unit (MPU), a microcontroller unit (MCU), a graphics processing unit (GPU), a field-programmable gate array (FPGA), an artificial intelligence processor (AI processor), a multi-core processor, or a neural processing unit (NPU). Exemplarily, the processor can also be an x86 processor, a non-x86 processor, an advanced instruction set computer (RISC) machine (ARM processor), or other processors.

[0123] In some possible implementations, the processor may connect to one or more hardware accelerators. For example, the hardware accelerator may be an FPGA, GPU, or other accelerator. Exemplarily, the processor and the hardware accelerator may have a peripheral component interconnect (PCI) express (PCIe) interface and communicate through this PCIe interface. Exemplarily, the hardware accelerator may communicate with the outside world via a gigabit Ethernet (GbE) interface.

[0124] For example, components of a hardware accelerator may include: software, hardware or memory for system debugging interfaces, or a single-board management controller.

[0125] For example, a DU system can be implemented using a processor (e.g., a multi-core processor) and one or more hardware accelerators. For instance, portions of the DU protocol stack can be implemented in software running on the processor, while computationally intensive L1 and L2 functions can be offloaded to FPGA- and / or GPU-based hardware accelerators. Alternatively, all L1 functions can be offloaded to FPGA- and / or GPU-based hardware accelerators, while other protocol stack components are implemented in software running on the processor. Yet another example is that the entire protocol stack is implemented in software running on the processor.

[0126] For example, the RU may include an O-RAN processing unit (OPU). The OPU may be used to receive enhanced common public radio interface (eCPRI) frames from the O-RAN fronthaul, and / or to perform fronthaul interface, lowest-level L1 operations (e.g., encoding, scrambling, modulation, layer mapping, or precoding), synchronization, beamforming, or resource element mapping, etc.

[0127] In some possible implementations, the OPU may include a digital processing unit (DPU), a RAN fronthaul link processing unit, and an RF processing unit.

[0128] The DPU can be used to perform synchronization, digital downconversion (DDC), digital upconversion (DUC), crest factor reduction (CFR), or digital pre-distortion (DPD), etc. In this way, the DPU can reduce the peak-to-average power ratio (PAPR) and / or adjacent channel leakage ratio (ACLR) of the RF front end. For example, the DPU may include an FPGA and / or an ASIC. The DPU can also be implemented in other ways.

[0129] The RF processing unit may include a transceiver module, an up-converter, a down-converter, a power amplifier (PA), a low noise amplifier (LNA), a transmit (Tx) filter, a receive (Rx) filter, or other devices.

[0130] For example, the transceiver module can be used to perform operations such as analog-to-digital conversion, digital-to-analog conversion, RF sampling, and frequency conversion using RF signals, intermediate frequency (IF) signals, and local oscillator (LO) signals in up-conversion and down-conversion.

[0131] The aforementioned physical device can also be a logic module, and the aforementioned logic module can also be a physical device; this application does not impose any limitations.

[0132] Some protocols (e.g., the NR protocol) stipulate that the UE assumes that SSBs transmitted using the same index at the same center frequency location are QCL (Quadrature Classless) with respect to Doppler spread, Doppler shift, average delay, delay spread, and spatial receiver parameters. For example, there exists an SSB burst set on a cell. This SSB burst set is transmitted at regular intervals. For SSBs transmitted in any two rounds of this burst set, the UE assumes that the two SSBs with the same index are QCL. It is clear that the above stipulation only specifies that SSBs with the same frequency and index are QCL, without discussing the relationships between different indices, different frequencies, and various types of SSBs.

[0133] According to the above regulations, for two types of SSBs with different frequencies and / or different indices, the terminal side will measure these SSBs separately, resulting in greater energy consumption.

[0134] Therefore, how to reduce the energy consumption of terminal devices is an urgent problem to be solved.

[0135] Figure 3 is a schematic flowchart of a communication method 300 provided in an embodiment of this application. This method 300 configures the QCL relationship of different types of SSBs on the network side, eliminating the need for the terminal side to measure both types of SSBs, thereby reducing power consumption on the terminal side. Optional operations in method 300 are shown in dashed lines in Figure 3. The various operations of method 300 are described below with reference to Figure 3.

[0136] S320, the terminal receives first information from the network side. Optionally, the first information is used to indicate that there is a QCL between the first SSB and at least one second SSB. Optionally, the first information is used to indicate the QCL relationship between the first SSB and at least one second SSB.

[0137] Correspondingly, the network side sends the first information to the terminal side.

[0138] For example, the first information may include the index of a first SSB and the index of at least one second SSB, thereby indicating that there is a QCL between the first SSB and at least one second SSB.

[0139] For example, the first information can be specific indication information (e.g., 1 bit). This indication information can be used to indicate that there is a QCL between the first SSB and at least one second SSB. For example, a value of 1 indicates that there is a QCL between the first SSB and at least one second SSB; a value of 0 indicates that there is no QCL between the first SSB and at least one second SSB. Alternatively, a value of 0 indicates that there is a QCL between the first SSB and at least one second SSB; a value of 1 indicates that there is no QCL between the first SSB and at least one second SSB.

[0140] The first information can also indicate the QCL relationship between the first SSB and at least one second SSB in other ways, which will not be enumerated further.

[0141] The first information can be information in a table or in the form of key-value pairs. This application does not limit the specific data form in which the first information indicates the QCL relationship.

[0142] In some examples, the first information can be used to indicate whether some or all of the SSBs of the first type have a QCL relationship with the SSBs of the second type. For example, each SSB of the second type can correspond to an indication message that indicates which SSB of the first type is the QCL source of that SSB (e.g., the indication message indicates the index of the SSB of the first type). For example, the first information can be used to indicate that: the QCL source of SSB#1 of the second type is SSB#1 of the first type; the QCL source of SSB#2 of the second type is SSB#2 of the first type; the QCL source of SSB#3 of the second type is SSB#3 of the first type; and the QCL source of SSB#4 of the second type is SSB#4 of the first type.

[0143] For example, the first information may be carried in an RRC message (e.g., an RRC reconfiguration message), a MAC CE, or a DCI. The first information may also be carried in other messages, and this application does not limit this.

[0144] The first SSB and at least one second SSB can be configured on the same cell, for example, on a secondary cell on the terminal side.

[0145] Unless otherwise specified, SSB can also be understood as or replaced by SSB signal, SSB beam, or SSB resource. For example, first SSB can be replaced by first SSB signal, first SSB beam, or first SSB resource.

[0146] The frequency of the first SSB may be the same as or different from the frequency of any of the at least one second SSB. The above frequency may be understood as or replaced by frequency position, subcarrier, CC, center frequency position, occupied resource element (RE) or other frequency-related terms, which are not limited in this application.

[0147] The index of the first SSB can be the same as or different from the index of any of the at least one second SSB. The index of an SSB can be its index within the SSB burst set to which it belongs. However, this application does not limit this, and the index of an SSB can also be other indices. The aforementioned SSB index can be understood as or replaced by the SSB's identity (ID) or other information corresponding to the SSB; this application does not limit this.

[0148] Unless otherwise specified, "second SSB" refers to any one of the "at least one second SSB" in S320 above.

[0149] The type of the first SSB can be different from the type of the second SSB. For example, the type of the first SSB can be different from the type of each of the at least one second SSBs mentioned above.

[0150] The SSB type can represent the SSB transmission method (e.g., transmission interval), SSB resources, SSB pattern, or other aspects. For example, different SSB types can represent at least one difference in the following: SSB transmission method, SSB resources, SSB pattern, or other aspects.

[0151] For ease of description, the type of the first SSB will be referred to as Type 1, and the type of the second SSB will be referred to as Type 2. Thus, the first SSB can be understood as an SSB of Type 1. At least one second SSB can be understood as at least one SSB of Type 2. The Type 1 and Type 2 can be different.

[0152] As an example, the first type can be a continuously transmitting type; in other words, the first SSB can be a continuously transmitting SSB. In this context, a "continuously transmitting SSB" can also be called an always-on SSB (AO SSB). The description of the AO SSB above can be found above and will not be repeated here.

[0153] As an example, the second type can be an on-demand sending type; in other words, the second SSB can be an on-demand sending SSB. Here, "on-demand sending SSB" can also be called an on-demand SSB (OD SSB). In this way, the second SSB can be sent at a specific time. The description of the OD SSB mentioned above can be found in the previous text and will not be repeated here.

[0154] The first type can also be any type other than continuous transmission; the second type can also be any type other than on-demand transmission. For example, the resources used to transmit the second SSB are different from the resources used to transmit the first SSB. Another example is that the pattern of the second SSB is different from the pattern of the first SSB.

[0155] For example, the first SSB can be an SSB. The second SSB can be an SSB. Thus, there is a QCL between the first SSB and at least one second SSB, which can be understood as a QCL between an SSB of the first type and one or more SSBs of the second type. The description of QCL can be found above and will not be repeated here.

[0156] In some possible implementations, prior to S320, method 300 also includes: generating first information on the network side.

[0157] In some possible implementations, after S320, method 300 further includes: the terminal side determining, based on the first information, that there is a QCL between the first SSB and at least one second SSB.

[0158] In some examples, the first information can also be used to indicate the QCL relationship between other SSBs of the first type (i.e., SSBs other than the first SSB) and other SSBs of the second type (i.e., SSBs other than at least one second SSB). See below for details, which will not be elaborated here.

[0159] Based on the above scheme, the first information can indicate that there is a QCL between the first SSB and at least one second SSB. In this way, the terminal can measure only one of the first SSB or at least one second SSB and determine the channel characteristics of the unmeasured SSB based on the QCL relationship. In this scheme, the terminal does not need to measure both the first SSB and at least one second SSB, thereby reducing the terminal's power consumption.

[0160] Furthermore, the above scheme introduces two types of SSBs, which helps improve network efficiency and save energy consumption on the network side. For example, in processes such as secondary cell activation, L1 measurement, or time-frequency synchronization, the above scheme can improve network efficiency and save energy consumption on the network side.

[0161] Figure 4 is a schematic diagram of beam scanning provided in an embodiment of this application. For ease of description and understanding, the following description uses the first type (i.e., the type of the first SSB) as the AO type and the second type (i.e., the type of the second SSB) as the OD type. However, those skilled in the art will understand that the type of the first SSB and / or the type of the second SSB can also be other types.

[0162] As a specific example, the network side can configure a certain cell as a secondary cell for the terminal side. This secondary cell may be inactive. The network side can transmit a first type of SSB (e.g., AO SSB) on this inactive secondary cell. For example, Figure 4(a) shows three first type SSBs, namely SSB#1, SSB#2, and SSB#3. Here, "#1", "#2", and "#3" can represent the indices of the first type of SSB. The first type of SSB is not limited to the three SSBs shown in Figure 4; other SSBs may also be used, which is not limited in this application.

[0163] The terminal can measure the first type of SSB mentioned above and periodically report the measurement results. The network can obtain the strong beam direction of the terminal based on the measurement results. For example, the strong beam direction can be the beam direction with a relatively strong reference signal receiving power (RSRP).

[0164] For example, assuming a sudden data transmission demand exists at a certain moment, the network side can activate the aforementioned secondary cell for the terminal side. For instance, the network side can send a second type of SSB (e.g., OD SSB) to the terminal side. This second type of SSB can be used to activate the secondary cell. Considering that the network side has already obtained prior information (the strong beam direction between the terminal side and the network side) through measurements of the first type of SSB, the second type of SSB does not need to scan the beam direction across the entire spatial domain, but rather scans within a specific beam direction (e.g., the aforementioned strong beam direction). Therefore, during the scanning process of the second type of SSB, the network side sends fewer beams, thereby saving network side energy consumption.

[0165] In some examples, the beamwidth of a second type of SSB (e.g., a second SSB) can be smaller than the beamwidth of a first type of SSB (e.g., a first SSB). For example, the beam of the second SSB can be narrower than that of the first SSB. This allows the network side to perform beam scanning based on at least one second type of SSB within a specific beam direction (e.g., the strong beam direction between the terminal side and the network side determined according to the first type of SSB). For example, Figure 4(b) shows three second type SSBs, namely SSB#1, SSB#2, and SSB#3. Here, "#1", "#2", and "#3" can represent the indices of the second type of SSB.

[0166] Compared to transmitting a second SSB beam across the entire airspace beam direction, the above scheme reduces the number of second SSBs transmitted by the network side. Furthermore, the second SSB beam is narrower, allowing for more precise scanning of the terminal side. This scheme enables the terminal side to further improve the airspace beam synchronization quality.

[0167] Furthermore, according to the current protocol, SSB#1 of type 1 in Figure 4(a) and SSB#1 of type 2 in Figure 4(b) are QCL; SSB#2 of type 1 in Figure 4(a) and SSB#2 of type 2 in Figure 4(b) are QCL; and SSB#3 of type 1 in Figure 4(a) and SSB#3 of type 2 in Figure 4(b) are QCL. In other words, the SSB index and frequency are bound to the QCL relationship. However, there is not necessarily a one-to-one QCL relationship between SSB#1 to SSB#3 of type 2 and SSB#1 to SSB#3 of type 1. Thus, the terminal side may incorrectly apply the channel characteristics of type 1 SSBs to type 2 SSBs, leading to a fault. Alternatively, the terminal side may perform measurements on both type 1 to SSB#3 and type 2 SSB#1 to SSB#3, resulting in high power consumption on the terminal side.

[0168] Method 300 in this embodiment can decouple the index and frequency of SSB from the QCL relationship, thereby improving the flexibility of configuration.

[0169] For example, suppose the first SSB is SSB#2 of type 1; the second type of SSBs with QCL relationships to the first SSB includes three second SSBs, namely SSB#1, SSB#2, and SSB#3 of type 2. First information can indicate that SSB#2 of type 1 and SSB#1 to SSB#3 of type 2 are QCL. In this way, the terminal side does not need to measure SSB#1 to SSB#3 of type 2, but can apply the channel characteristics of SSB#2 of type 1 to SSB#3 of type 2, thereby reducing power consumption on the terminal side.

[0170] In some scenarios, decoupling the indexes of QCL and SSB can achieve a gain in reducing latency.

[0171] For example, if the SSB of the first type is indicated to be transmitted in the latter half of the SSB pattern in the time domain (e.g., within the last 2.5 ms), no SSB signal needs to be transmitted in the first half of the SSB pattern (e.g., within the first 2.5 ms). If the QCL is bound to the SSB index, when a second type SSB with a QCL between it and the first type SSB needs to be transmitted, it is necessary to wait in the time domain until the latter half of the SSB pattern to transmit the second type SSB, resulting in a large delay.

[0172] As a specific example, assume that 64 Type 1 SSBs are configured on the cell, denoted as SSB#1 to SSB#64. The network side has determined, based on the measurement results of the Type 1 SSBs, that the strong beam directions correspond to Type 1 SSBs#61 to #64. Assume the pattern of Type 2 and Type 1 SSBs is example D (case D). In the pattern of case D, the time-domain resources of SSB#1 to SSB#64 are distributed at unequal intervals within a 5ms time window, with SSB#61 to SSB#64 distributed in the last 1ms. In this case, if the terminal side, according to the current protocol scheme, determines that the SSBs#61 to SSB#64 of Type 1 have a QCL relationship with Type 1 SSBs#61 to SSB#64 as Type 2 SSBs#61 to SSB#64. In this way, the terminal side cannot send the second type of SSB within the first 4ms, but can only send the second type of SSB#61 to SSB#64, which have QCL relationship with the first type of SSB#61 to SSB#64, in the last 1ms of the above time window.

[0173] Through the method 300 provided in this application embodiment, the QCL relationship can be decoupled from the index. For example, SSB#1 to SSB#4 of the second type can have QCL relationships with SSB#61 to SSB#64 of the first type, respectively. Thus, the terminal can send SSB#1 to SSB#4 of the second type, which have QCL relationships with SSB#61 to SSB#64 of the first type, in the 1st ms of a 5ms time window. Therefore, the above scheme can advance the time of SSB transmission, thereby achieving a gain in latency reduction.

[0174] For ease of description and understanding, the following description uses the first type (i.e., the type of the first SSB) as the AO type and the second type (i.e., the type of the second SSB) as the OD type. However, those skilled in the art will understand that the type of the first SSB and / or the type of the second SSB can also be other types.

[0175] The following is an example of a first SSB corresponding to multiple second SSBs, denoted as Mapping Example 1.

[0176] In some mapping example 1, the first information can be used to indicate that there is a QCL between the first SSB and multiple second SSBs.

[0177] Optionally, the first information is used to indicate the QCL relationship between a first type of SSB and a second type of SSB. Specifically, there is a QCL between one SSB in the first type of SSB and multiple SSBs in the second type of SSB.

[0178] For example, suppose that M SSBs of the first type are configured, and N SSBs of the second type are configured. M and N can be positive integers. M can be greater than or equal to N, or less than or equal to N.

[0179] Among M SSBs of type I, there can be m SSBs of type I that have QCL relationships with multiple SSBs of type II. Here, m can be a positive integer less than or equal to M.

[0180] In some examples, each of the m first-type SSBs mentioned above has a QCL with the same number of second-type SSBs.

[0181] For example, suppose M = 4, m = 4, and N = 16. That is, 4 SSBs of type 1 are configured, and 16 SSBs of type 2 are configured. Each SSB of type 1 can have a QCL relationship with 4 SSBs of type 2.

[0182] As a specific example, there is a QCL relationship between SSB#1 of type 1 and SSB#1 to SSB#4 of type 2; there is a QCL relationship between SSB#2 of type 1 and SSB#5 to SSB#8 of type 2; there is a QCL relationship between SSB#3 of type 1 and SSB#9 to SSB#12 of type 2; and there is a QCL relationship between SSB#4 of type 1 and SSB#13 to SSB#16 of type 2.

[0183] Figure 5 is another schematic diagram of beam scanning provided in an embodiment of this application.

[0184] As another concrete example, Figure 5(a) shows two Type I SSBs (m=2). Figure 5(b) shows four Type II SSBs. There is a QCL between Type I SSB#1 and Type II SSB#1 and SSB#2. There is also a QCL between Type I SSB#2 and Type II SSB#3 and SSB#4. That is, each of the m=2 Type I SSBs corresponds to the same number of Type II SSBs.

[0185] In other examples, each of the m first-type SSBs mentioned above may be QCL with the same or different number of second-type SSBs.

[0186] For example, suppose M = 8, m = 2, and N = 8. That is, 8 SSBs of type 1 and 8 SSBs of type 2 are configured. Among them, two SSBs of type 1 have QCL relationships with multiple SSBs of type 2. The number of SSBs of type 2 corresponding to the two SSBs of type 1 can be the same or different.

[0187] As a specific example of different quantities, SSB#1 of the first type can have a QCL relationship with SSB#1 to SSB#6 of the second type; SSB#2 of the first type can have a QCL relationship with SSB#7 to SSB#8 of the second type.

[0188] As another concrete example, Figure 5(c) shows three Type I SSBs, where two Type I SSBs have a QCL relationship with Type II SSBs (m=2). Figure 5(d) shows three Type II SSBs. Type I SSB#2 has a QCL relationship with Type II SSBs#1 and#2. Type I SSB#3 has a QCL relationship with Type II SSBs#3 through#5. That is, the number of Type II SSBs corresponding to each of the m=2 Type I SSBs can be different.

[0189] In some further examples, some of the m SSBs of type 1 may correspond to the same number of SSBs of type 2. This application does not limit whether the number of SSBs of type 2 corresponding to another portion of the SSBs of type 1 is the same.

[0190] The following is an example of a first SSB corresponding to a second SSB, denoted as Mapping Example 2.

[0191] In some mapping example 2, the first information can be used to indicate that there is a QCL between the first SSB and a second SSB.

[0192] Optionally, the first information is used to indicate the QCL relationship between a first type of SSB and a second type of SSB. Here, the relationship between an SSB of the first type of SSB and an SSB of the second type of SSB is QCL. In other words, the QCL relationship can be injective.

[0193] For example, suppose that M SSBs of the first type are configured, and N SSBs of the second type are configured. M and N can be positive integers. M can be greater than or equal to N.

[0194] For ease of description, assume that there are M SSBs of the first type, namely SSB#1 to SSB#M, and N SSBs of the second type, namely SSB#1 to SSB#N.

[0195] For a first-type SSB with index m, there exists a QCL relationship between a second-type SSB with index n and the first-type SSB with index m. In other words, there is a QCL relationship between SSB#m of the first type and SSB#n of the second type.

[0196] Where m is a positive integer less than or equal to M, and n is a positive integer less than or equal to N. m and n may or may not be equal; this application does not impose any restrictions. In other words, the indices of the first type of SSB with QCL relations and the indices of the second type of SSB may be the same or different; this application does not impose any restrictions.

[0197] Figure 6 is another schematic diagram of beam scanning provided in an embodiment of this application.

[0198] As a concrete example, Figure 6(a) shows three Type 1 SSBs. Figure 5(b) shows three Type 2 SSBs. There is a QCL between Type 1 SSB#1 and Type 2 SSB#2. There is a QCL between Type 1 SSB#2 and Type 2 SSB#3. There is a QCL between Type 1 SSB#3 and Type 2 SSB#1.

[0199] The beamwidth of the second type of SSB can be less than or equal to the beamwidth of the first type of SSB, or it can be greater than the beamwidth of the first type of SSB. This application does not impose any limitation on this.

[0200] In some examples, there exists a natural number k such that there is a QCL relationship between a first-type SSB with index m and a second-type SSB with index (n+k)mod N. Here, mod can represent modulo.

[0201] When k=0, the index of an SSB of type 1 with a QCL relationship can be the same as the index of an SSB of type 2.

[0202] With k≠0, as a concrete example, M=4 SSBs of type 1 are configured, and N=4 SSBs of type 2 are configured. Assuming k=2, then there is a QCL relationship between SSB#1 of type 1 and SSB#3 of type 2, a QCL relationship between SSB#2 of type 1 and SSB#4 of type 2, a QCL relationship between SSB#3 of type 1 and SSB#1 of type 2, and a QCL relationship between SSB#4 of type 1 and SSB#2 of type 2.

[0203] In some possible implementations, the index of the first SSB is different from the index of the second SSB.

[0204] The description of the index is as described above and will not be repeated here.

[0205] Based on the above scheme, the QCL relationship between the first SSB and the second SSB can be decoupled from whether the indexes are the same. Compared to a scheme that assumes that only SSBs with the same index can have a QCL relationship, the above scheme can specify that SSBs with different indexes have a QCL relationship, thereby achieving flexible configuration of the QCL relationship.

[0206] Those skilled in the art will understand that, in some possible implementations, whether the index of the first SSB is the same as the index of the second SSB is not limited in this application. Furthermore, SSBs of the first type and SSBs of the second type with the same index may or may not have a QCL relationship.

[0207] In some possible implementations, the frequency corresponding to the first SSB is different from the frequency corresponding to the second SSB.

[0208] The frequency corresponding to an SSB can be used to transmit and / or receive that SSB. For example, a terminal can receive a first SSB on the frequency corresponding to a first SSB and a second SSB on the frequency corresponding to a second SSB. Similarly, the network can transmit a first SSB on the frequency corresponding to a first SSB and transmit a second SSB on the frequency corresponding to a second SSB.

[0209] In some examples, a first-type SSB and a second-type SSB are configured on the same cell. The first-type SSB and the second-type SSB may use the same or different frequencies.

[0210] If the first type of SSB and the second type of SSB have the same frequency, the terminal side can follow the protocol's provisions and assume that the SSBs with the same index in the first type of SSB and the second type of SSB are both QCL.

[0211] If the frequencies of the first type of SSB and the second type of SSB are different, for example, the frequencies of the first SSB and the second SSB are different, the terminal side can determine that there is a QCL relationship between the first SSB and the second SSB based on the first information.

[0212] In other examples, regardless of whether the frequency corresponding to the first type of SSB and the frequency corresponding to the second type of SSB are the same, the terminal side can determine the QCL relationship between the first type of SSB and the second type of SSB based on the network side's indication (e.g., first information).

[0213] Based on the above scheme, the QCL relationship between the first SSB and the second SSB can be decoupled from whether their frequencies are the same. Compared to a scheme that assumes only SSBs with the same frequency can have a QCL relationship, the above scheme can specify a QCL relationship between SSBs corresponding to different frequencies, thereby achieving a flexible configuration of QCL management.

[0214] Those skilled in the art will understand that, in some possible implementations, whether the frequency corresponding to the first SSB is the same as the frequency corresponding to the second SSB is not limited in this application. Furthermore, among the first type of SSB and the second type of SSB, SSBs corresponding to the same frequency may or may not have a QCL relationship.

[0215] In some possible implementations, method 300 also includes: S325.

[0216] S325, the terminal receives second information from the network side. Optionally, the second information can be used to indicate that the QCL relationship between the first SSB and the second SSB is of a first type.

[0217] Correspondingly, the network side can send this second information to the terminal side.

[0218] The second information can be carried in an RRC message, MAC CE, DCI, or other message; this application does not impose any limitations on this. The second information can be carried in the same message as the first information, or it can be carried in different messages. The second information can be sent simultaneously with the first information, or it can be sent at different times.

[0219] The second information may include indication information of the first type, thereby indicating the first type.

[0220] For example, the first type can be QCL-TypeA, QCL-TypeB, QCL-TypeC, QCL-TypeD, or other types. For example, other QCL types that have emerged as the standard has evolved.

[0221] Optionally, the second information is used to indicate the type of QCL relationship between the first type of SSB and the second type of SSB.

[0222] In some examples, the first and second information can jointly indicate that among the SSBs of the first type, a portion of the SSBs have a QCL relationship with a portion of the SSBs of the second type, and this relationship is of type C; another portion of the SSBs of the first type have a QCL relationship with another portion of the SSBs of the second type, and this relationship is of type D; and yet another portion of the SSBs of the first type do not have a QCL relationship with yet another portion of the SSBs of the second type.

[0223] As a specific example, the network side is configured with four second-type SSBs, denoted as SSB#1 to SSB#4. The first and second information can be carried in the RRC message. The first and second information can jointly indicate that: the QCL source of second-type SSB#1 is first-type SSB#1, and the QCL type is TypeD; the QCL source of second-type SSB#2 is first-type SSB#1, and the QCL type is TypeD; the RRC message does not configure (or in other words, the first and second information do not explicitly indicate) the QCL source and QCL type of second-type SSB#3 and SSB#4, indicating that there is no QCL relationship between these two second-type SSBs and the first-type SSBs.

[0224] Based on the above scheme, the terminal side can determine the type of QCL relationship between the first SSB and the second SSB through the second information, thereby determining that the first SSB and the second SSB correspond to the same channel characteristics. The terminal side does not need to measure both the first SSB and the second SSB, but can reuse the measured same channel characteristics, thereby reducing the power consumption of the terminal side.

[0225] In some possible implementations, the method 300 may further include S310 before S320 (or S325).

[0226] S310, the terminal receives third information from the network side, the third information being used to indicate that there is a QCL between the first SSB and at least one third SSB.

[0227] The aforementioned at least one third SSB can be a second type of SSB or another type of SSB.

[0228] In this case, at least one third SSB differs from at least one second SSB. For example, some or all of the SSBs in at least one third SSB do not belong to the aforementioned at least one second SSB. Similarly, some or all of the SSBs in at least one second SSB do not belong to the aforementioned at least one third SSB.

[0229] The other descriptions of the third SSB are similar to those of the second SSB, as detailed above, and will not be repeated here.

[0230] The third information can be carried in an RRC message, MAC CE, DCI, or other messages; this application does not impose any limitations on this. The third information and the first information can be carried in different messages. For example, the third information can be carried in an RRC message, and the first information can be carried in an RRC reconfiguration message. The third information and the first information can also be carried in other messages; this application does not impose any limitations on this.

[0231] The terminal may receive multiple indications of QCL relationship. The terminal can use the last received indication to determine the SSB that satisfies the QCL relationship with the first SSB.

[0232] In some possible implementations, after S320, method 300 also includes: S330.

[0233] S330, the terminal side determines, based on the first information, that the SSB that satisfies the QCL relationship with the first SSB is at least one second SSB.

[0234] As an example, the network side can send an RRC message to the terminal side, which may include third information. In this way, the terminal side can know that the SSB that satisfies the QCL relationship with the first SSB can be at least one third SSB.

[0235] The first SSB and at least one third SSB satisfy a QCL relationship, which can be understood as a mapping relationship (or QCL mapping relationship). For ease of understanding, the above mapping relationship can be denoted as the first mapping relationship.

[0236] In the event of terminal-side movement or other events, the QCL relationship between SSBs may change. In other words, the QCL mapping relationship may change. For example, the SSBs that satisfy the QCL relationship with the first SSB may change. The network side can determine from the measurement results of the first SSB that the strong beam direction of the terminal side has changed, thus requiring a change in the SSBs that satisfy the QCL relationship with the first SSB. In other words, the network side needs to update the first mapping relationship. For example, the network side determines to change the QCL relationship between the first SSB and at least one third SSB to a QCL relationship between the first SSB and at least one second SSB (denoted as the second mapping relationship).

[0237] Based on the above scheme, the network side can update the SSBs that satisfy the QCL relationship with the first SSB, thereby ensuring the effectiveness of the QCL mapping relationship on the terminal side.

[0238] In some possible implementations, the network side can execute S320. For example, the network side can send an RRC reconfiguration message to the terminal side, which may include first information. Optionally, the RRC reconfiguration message may also include second information.

[0239] In this way, the network side can update the QCL mapping relationship. The terminal side can execute S330 based on the first information, that is, determine the updated second mapping relationship.

[0240] Based on the above scheme, the first information can be carried in an RRC message, which is easy to implement.

[0241] Furthermore, in some other possible implementations, the network side can execute S320. For example, the network side can send a MAC CE or DCI to the terminal side, which may include first information. Optionally, the MAC CE or DCI may also include second information.

[0242] MAC CE or DCI has shorter latency and can achieve dynamic updates of QCL mapping relationships.

[0243] For example, after establishing an RRC connection between the terminal and the cell where the network resides, the network can send an RRC message to the terminal. This RRC message can indicate the QCL mapping relationship (e.g., the aforementioned first mapping relationship). If the QCL mapping relationship changes, the network can indicate the updated QCL mapping relationship (e.g., the aforementioned second mapping relationship) to the terminal through a field in the MAC CE or a field in the DCI. For example, the aforementioned field can be used to carry first information.

[0244] Based on the above scheme, the first information can be carried in MAC CE or DCI, and the dynamic indication of QCL mapping relationship can be achieved with a shorter latency.

[0245] The communication device provided in the embodiments of this application will be described in detail below with reference to Figures 7 to 10. The description of the device embodiments corresponds to the description of the method embodiments. Therefore, for content not described in detail, please refer to the method embodiments above. For the sake of brevity, some content will not be repeated.

[0246] This application embodiment can divide the communication device into functional modules according to the above method example. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into one processing module. The integrated modules can be implemented in hardware, software, or a combination of both. The module division in this application embodiment is illustrative and only represents one logical functional division; other division methods may be used in actual implementation. The following description uses the division of functional modules according to each function as an example.

[0247] Figure 7 is an exemplary block diagram of the communication device 1000 provided in an embodiment of this application.

[0248] As shown in Figure 7, for example, the communication device 1000 may include a chip system 1010, a memory 1020, a bus 1030, a power management module 1040, or a transceiver 1050, etc.

[0249] The chip system 1010 can be an integrated circuit chip with signal processing capabilities. In implementation, each step of the above method can be completed through integrated logic circuits in the hardware of the chip system 1010 or through software instructions.

[0250] As an example and not a limitation, the chip system 1010 may include circuitry or chips responsible for signal processing (such as a modem chip, also known as a baseband chip, or a system-on-chip (SoC) chip or system-in-package (SIP) chip containing a modem core).

[0251] Optionally, the chip system 1010 may also include a memory (such as a cache) for storing instructions and data. In some embodiments, the memory in the chip system 1010 is a cache memory. This memory can store instructions or data that the chip system 1010 has just used or that are used repeatedly. If the chip system 1010 needs to use the instruction or data again, it can directly retrieve it from the memory. This avoids repeated accesses, reduces the waiting time of the chip system 1010, and thus improves the efficiency of the system.

[0252] In some embodiments, the chip system 1010 may include one or more interfaces. Interfaces may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a subscriber identity module (SIM) interface, and / or a universal serial bus (USB) interface, etc.

[0253] The memory 1020 may include random access memory (RAM) and read-only memory (ROM). The memory 1020 may store computer-readable, computer-executable code, including instructions that, when executed, cause the processor to perform the various functions described in this application.

[0254] Optionally, the code may include instructions for implementing various aspects of the embodiments of this application, such as instructions for receiving first information. The code may be stored in a non-transitory computer-readable medium such as system memory or other types of memory. In some cases, the code may not be directly executable by the chip system 1010, but may enable a computer (e.g., at compile and execution time) to perform the functions described in this application. In some cases, memory 1020 may contain a basic I / O system that can control basic hardware or software operations, such as interaction with peripheral components or devices.

[0255] For example, the chip system 1010 executes various functional applications and data processing of the communication device 1000 by running instructions stored in the memory 1020. For instance, when the communication device 1000 transfers files with other devices (which may also be terminals or access network devices), the chip system 1010 of the communication device 1000 can call the computer-executable program code stored in the memory 1020 to implement the communication method provided in the embodiments of this application.

[0256] In addition, the memory 1020 can be integrated into the chip system 1010 or independent of the chip system 1010.

[0257] For example, bus 1030 may be USB for supporting communication between various parts of communication device 1000.

[0258] The power management module 1040 is used to receive charging input from the charger. Optionally, the power management module 1040 can also supply power to the communication device 1000 while charging it (e.g., the battery module of the communication device 1000). By way of example and not limitation, the power management module 1040 can also supply power to other devices besides the communication device 1000.

[0259] Transceiver 1050 can communicate bidirectionally via one or more antennas, a wired link, or a wireless link. For example, transceiver 1050 can represent a wireless transceiver and can communicate bidirectionally with another wireless transceiver. Transceiver 1050 may also include a modem for modulating packets and providing the modulated packets to the antenna for transmission, and for demodulating packets received from the antenna. Transceiver 1050 may include a receiver and a transmitter, the receiver performing the function of receiving information and the transmitter performing the function of transmitting information.

[0260] In some cases, a wireless device may include a single antenna. However, in other cases, the device may have more than one antenna, such as antenna 1 and antenna 2 shown in FIG. 7, which may be capable of simultaneously transmitting or receiving multiple wireless transmissions. Exemplarily, antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in the communication device 1000 can be used to cover one or more communication frequency bands. Different antennas can also be multiplexed to improve antenna utilization. For example, antenna 1 can be multiplexed as a diversity antenna for a wireless local area network. In other embodiments, the antennas can be used in conjunction with a tuning switch. The communication device 1000 can transfer files to other devices via wireless communication functions.

[0261] In one design, the communication device 1000 may correspond to the terminal side in the above method embodiments.

[0262] The device 1000 can implement the steps or processes executed on the terminal side corresponding to the above method embodiments. The transceiver 1050 can be used to perform the terminal-side transmission and reception related operations in the above method embodiments, such as executing step S320 in the above method embodiments. The chip system 1010 can be used to perform the terminal-side processing related operations in the above method embodiments.

[0263] In another design, the communication device 1000 may correspond to the network side in the above method embodiment.

[0264] The device 1000 can implement the steps or processes executed on the network side corresponding to the method embodiments above. The transceiver 1050 can be used to perform network-side transmission and reception related operations in the method embodiments above, such as executing step S320 in the method embodiments above. The chip system 1010 can be used to perform network-side processing related operations in the method embodiments above.

[0265] In the design of the communication device 1000 corresponding to the terminal device, the communication device 1000 may include modules such as the short-range communication module 1064, sensor 1061, display 1062, or camera 1063 as shown in FIG7.

[0266] The short-range communication module 1064 may include modules that support short-range communication, such as Wi-Fi and Bluetooth.

[0267] For example, sensor 1061 may include pressure sensor, gyroscope sensor, barometric pressure sensor, magnetic sensor, accelerometer, distance sensor, proximity sensor, fingerprint sensor, temperature sensor, touch sensor, ambient light sensor, bone conduction sensor, etc.

[0268] For example, the display 1062 is used to display images, videos, etc. The display includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a mini light-emitting diode (LED), a micro LED, a micro OLED, a quantum dot light-emitting diode (QLED), etc. For example, in this embodiment, the display can be used to display the interface required by the communication device 1000. For example, the communication device 1000 implements the display function through a graphics processing unit (GPU), a display, and an application processor. The GPU is a microprocessor for image processing, connected to the display and the application processor. The GPU is used to perform mathematical and geometric calculations and for graphics rendering. The chip system 1010 may include one or more GPUs that execute program instructions to generate or change display information.

[0269] For example, camera 1063 is used to acquire images, videos, etc.

[0270] It is understood that the structure shown in Figure 7 does not constitute a specific limitation on the communication device 1000, and the specific structure of the terminal device and / or access network device can be referred to Figure 7. In some embodiments, the communication device 1000 may also include more or fewer components than shown in Figure 7, or combine some components, or split some components, or have different component arrangements, etc. Alternatively, some components shown in Figure 7 may be implemented in hardware, software, or a combination of software and hardware, and the terminal device and / or access network device may add or reduce components based on the structure given in Figure 7.

[0271] Figure 8 is a schematic block diagram of a communication device 2000 provided in an embodiment of this application.

[0272] As shown in Figure 8, the communication device 2000 may include a baseband unit 2010, which can communicate with external devices via a cellular radio frequency (RF) transceiver 2020 (e.g., if the communication device 2000 is a terminal device, the baseband unit 2010 can communicate with access network devices via the cellular RF transceiver 2020; or, if the communication device 2000 is an access network device, the baseband unit 2010 can communicate with terminal devices and / or core network devices via the cellular RF transceiver 2020).

[0273] By way of example, baseband unit 2010 may include computer-readable medium / memory. Baseband unit 2010 may be responsible for general processing, including the execution of software stored on computer-readable medium / memory. When executed by baseband unit 2010, the software causes baseband unit 2010 to perform the various functions described above. Computer-readable medium / memory may also be used to store data manipulated by baseband unit 2010 when executing the software.

[0274] Optionally, the baseband unit 2010 further includes a receiving unit 2011, a management unit 2012, and a transmitting unit 2013. When the communication device 2000 is applied to the terminal side, the management unit 2012 may include one or more of the sub-units shown in FIG8. For example, a QCL determination sub-unit, wherein the QCL determination sub-unit can be used to perform the operation of determining the QCL relationship between a first type of SSB and a second type of SSB in the above method embodiments. The units within the management unit 2011 may be stored in a computer-readable medium / memory and / or configured as hardware within the baseband unit 2010. The receiving unit 2011 and the transmitting unit 2013 may be referred to as transceiver units.

[0275] When the communication device 2000 is used to implement the terminal side functions in the above method embodiments, the receiving unit 2011 is used to perform the receiving step on the terminal side, the sending unit 2013 is used to perform the sending step on the terminal side, and the management unit 2012 is used to perform the processing step on the terminal side.

[0276] For example, when the communication device 2000 is used to implement the terminal side functions in the above method embodiments, the receiving unit 2011 receives first information, wherein the first information is used to indicate that there is a quasi-co-addressable QCL between the first synchronization signal block SSB and at least one second SSB, and the type of the first SSB is different from the type of the second SSB.

[0277] For example, when the device 2000 is used to perform the method in FIG3, the receiving unit 2011 can be used to perform the step of receiving information in the method; the management unit 2012 can be used to perform the processing step in the method; and the sending unit 2013 can be used to perform the step of sending information in the method.

[0278] When the communication device 2000 is used to implement the network side functions in the above method embodiments, the receiving unit 2011 is used to perform the receiving steps on the network side, the sending unit 2013 is used to perform the sending steps on the network side, and the management unit 2012 is used to perform the processing steps on the network side.

[0279] For example, when the communication device 2000 is used to implement the network side functions in the above method embodiments, the sending unit 2013 is used to send first information, wherein the first information is used to indicate that there is a quasi-co-addressable QCL between the first synchronization signal block SSB and at least one second SSB, and the type of the first SSB is different from the type of the second SSB.

[0280] For example, when the device 2000 is used to perform the method in FIG3, the receiving unit 2011 can be used to perform the step of receiving information in the method; the management unit 2012 can be used to perform the processing step in the method; and the sending unit 2013 can be used to perform the step of sending information in the method.

[0281] When the communication device 2000 is used to implement the terminal side functions in the above method embodiments, the receiving unit 2011 is used to perform the receiving step on the terminal side, the sending unit 2013 is used to perform the sending step on the terminal side, and the management unit 2012 is used to perform the processing step on the terminal side.

[0282] For a more detailed description of the receiving unit 2011, the management unit 2012, and the sending unit 2013, please refer to the relevant descriptions in the above method embodiments, which will not be repeated here.

[0283] By way of example and not limitation, the chip system in this application is shown in Figure 9, which is a schematic block diagram of the chip system 3000 provided in an embodiment of this application. The chip system includes, but is not limited to, a modem chip, also known as a baseband chip, or a system-on-chip (SoC) chip or a system-in-package (SIP) chip containing a modem core.

[0284] As can be seen from Figure 9, the chip system (or processing system) includes a processor 3010, a memory 3020, and an input / output interface 3030.

[0285] The processor 3010 can be a processing circuit in the chip system (including at least one processor, such as processor 1 and processor 2 as shown in FIG. 9). The processor 3010 can be coupled to the memory 3020, and call the instructions in the memory 3020, so that the chip system can implement the methods and functions of the various embodiments of this application. The input / output interface 3030 can be an input / output circuit in the chip system, which outputs the information processed by the chip system, or inputs the data or signaling information to be processed into the chip system for processing.

[0286] As one approach, the chip system is used to implement operations performed by the terminal side or the network side in the various method embodiments described above.

[0287] For example, processor 3010 is used to implement processing-related operations performed by the terminal side or network side in the above method embodiments, as described in the foregoing embodiments; input / output interface 3030 is used to implement sending and / or receiving-related operations performed by the terminal side or network side in the above method embodiments, as described in the foregoing embodiments.

[0288] As an example and not a limitation, the chip system in this application is shown in Figure 10, which is a schematic block diagram of the chip system 4000 provided in an embodiment of this application.

[0289] As shown in Figure 10, the chip system (or processing system) includes an input / output interface 4010 and logic circuitry 4020. The input / output interface 4010 can be an input / output circuit within the chip system, outputting processed information or inputting data or signaling information to be processed. For details, please refer to the description in the preceding embodiments, such as the embodiment shown in Figure 3. The logic circuitry 4020 is used to execute the aforementioned communication method, and for details, please refer to the description in the preceding embodiments.

[0290] As one approach, the chip system is used to implement operations performed by the terminal side or the network side in the various method embodiments described above.

[0291] For example, logic circuit 4020 is used to implement processing-related operations performed by the terminal side or network side in the above method embodiments; input / output interface 4010 is used to implement sending and / or receiving-related operations performed by the terminal side or network side in the above method embodiments.

[0292] This application also provides a computer-readable storage medium storing computer instructions for implementing the methods executed by the device in the above-described method embodiments.

[0293] For example, when the computer program is executed by the computer, it enables the computer to implement the methods executed by the terminal side or the network side in the various embodiments of the above methods.

[0294] This application also provides a computer program product comprising instructions which, when executed by a computer, implement the methods executed by the terminal side or the network side in the above-described method embodiments.

[0295] This application also provides a communication system, including the aforementioned network side and terminal side.

[0296] The explanations and beneficial effects of the relevant contents in any of the devices provided above can be found in the corresponding method embodiments provided above, and will not be repeated here.

[0297] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0298] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0299] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

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

[0301] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0302] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0303] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A communication method, characterized in that, include: Receive first information, wherein the first information is used to indicate that there is a quasi-co-addressable QCL between a first synchronization signal block (SSB) and at least one second SSB, and the type of the first SSB is different from the type of the second SSB.

2. The method according to claim 1, characterized in that, The first SSB is an SSB sent on demand, and the second SSB is an SSB sent continuously.

3. The method according to claim 1 or 2, characterized in that, The index of the first SSB is different from the index of the second SSB.

4. The method according to any one of claims 1 to 3, characterized in that, The frequency corresponding to the first SSB is different from the frequency corresponding to the second SSB.

5. The method according to any one of claims 1 to 4, characterized in that, The method further includes: Receive second information, which indicates that the QCL relationship between the first SSB and the second SSB is of the first type.

6. The method according to any one of claims 1 to 5, characterized in that, Before receiving the first information, the method further includes: Receive third information, the third information being used to indicate that there is a QCL between the first SSB and at least one third SSB, the at least one third SSB being different from the at least one second SSB; The method further includes, after receiving the first information: Based on the first information, the SSB that satisfies the QCL relationship with the first SSB is determined to be the at least one second SSB.

7. The method according to any one of claims 1 to 6, characterized in that, The first information is carried in a Radio Resource Control (RRC) message, a Media Access Control (MAC) control unit (CE) message, or a Downlink Control Information (DCI) message.

8. A communication method, characterized in that, include: Send a first message, wherein the first message is used to indicate that there is a quasi-co-addressable QCL between a first synchronization signal block (SSB) and at least one second SSB, and the type of the first SSB is different from the type of the second SSB.

9. The method according to claim 8, characterized in that, The first SSB is an SSB sent on demand, and the second SSB is an SSB sent continuously.

10. The method according to claim 8 or 9, characterized in that, The index of the first SSB is different from the index of the second SSB.

11. The method according to any one of claims 8 to 10, characterized in that, The frequency corresponding to the first SSB is different from the frequency corresponding to the second SSB.

12. The method according to any one of claims 8 to 11, characterized in that, The method further includes: Send a second message, which indicates that the QCL relationship between the first SSB and the second SSB is of the first type.

13. The method according to any one of claims 8 to 12, characterized in that, Before sending the first information, the method further includes: A third message is sent, which indicates that there is a QCL between the first SSB and at least one third SSB, and that the at least one third SSB is different from the at least one second SSB.

14. The method according to any one of claims 8 to 13, characterized in that, The first information is carried in a Radio Resource Control (RRC) message, a Media Access Control (MAC) control unit (CE) message, or a Downlink Control Information (DCI) message.

15. A communication device, characterized in that, It includes at least one module or at least one unit, said at least one module or said at least one unit being used to perform the method of any one of claims 1 to 14.

16. A communication device, characterized in that, include: At least one processor, the at least one processor being configured to execute a computer program or instructions to cause the method of any one of claims 1 to 14 to be performed.

17. The communication device according to claim 16, characterized in that, The communication device further includes a memory for storing the computer program or the instructions.

18. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program or instructions that, when executed, cause the method of any one of claims 1 to 14 to be performed.

19. A computer program product, characterized in that, Includes a computer program or instructions, which, when executed, implement the method as described in any one of claims 1 to 14.

20. A communication system, characterized in that, It includes a terminal side and a network side, wherein the terminal side is used to perform the method as described in any one of claims 1 to 7, and the network side is used to perform the method as described in any one of claims 8 to 14.

Images