Wireless communication method, terminal device, and network device

Abstract

Provided are a wireless communication method, a terminal device, and a network device. The method comprises: a terminal device receiving first information which is sent by a network device and is associated with a target SSB, wherein the first information is used for indicating that the target SSB is not used by the terminal device to access a first cell associated with the target SSB, the target SSB is a non-cell-defining SSB or a cell-defining SSB, and the transmission of the target SSB is triggered on the basis of a request from the terminal device. In the embodiments of the present application, a network device sends first information to a terminal device, so as to indicate that a target SSB involved in on-demand transmission is not used by the terminal device to access a first cell associated with the target SSB. On the basis of the first information, the present application may help to reduce access errors of a terminal device that does not support an on-demand SSB, thereby improving the communication efficiency.

Description

Method, terminal device and network device for wireless communication TECHNICAL FIELD

[0001] The present application relates to the technical field of communication, and more particularly, to a method, a terminal device and a network device for wireless communication. BACKGROUND

[0002] In a communication system, a terminal device can perform initial access based on a target synchronization signal broadcast channel block (SS / PBCH block, SSB) (e.g., a cell-defining SSB). However, when the target SSB is an on-demand SSB, a terminal device that does not support the on-demand SSB may fail to perform initial access based on the target SSB, which can result in access errors.

[0003] SUMMARY

[0004] The present application provides a method, a terminal device and a network device for wireless communication. The various aspects of the present application are described below.

[0005] In a first aspect, a method for wireless communication is provided, comprising: receiving, by a terminal device, first information associated with a target SSB and transmitted by a network device, the first information being used to indicate that the target SSB is not used for the terminal device to access a first cell associated with the target SSB, wherein the target SSB is a non-cell-defining SSB or a cell-defining SSB, and transmission of the target SSB is triggered based on a request of the terminal device.

[0006] In a second aspect, a method for wireless communication is provided, comprising: in response to a first event, receiving, by a terminal device, fourth information transmitted by a network device, the fourth information being used to indicate that a target SSB is activated in a secondary cell, and transmission of the target SSB is triggered based on a request of the terminal device; wherein the first event comprises one or more of the following: the secondary cell is configured; the secondary cell is activated; the network device indicates to activate the secondary cell.

[0007] In a third aspect, a method for wireless communication is provided, comprising: transmitting, by a network device, first information associated with a target SSB to a terminal device, the first information being used to indicate that the target SSB is not used for the terminal device to access a first cell associated with the target SSB, wherein the target SSB is a non-cell-defining SSB or a cell-defining SSB, and transmission of the target SSB is triggered based on a request of the terminal device.

[0008] In a fourth aspect, a method of wireless communication is provided, including: in response to a first event, sending, by a network device, fourth information to a terminal device, the fourth information being used to indicate that a target SSB is activated in a secondary cell, transmission of the target SSB being triggered based on a request of the terminal device; wherein the first event includes one or more of: the secondary cell being configured; the secondary cell being activated; the network device indicating to activate the secondary cell.

[0009] In a fifth aspect, a terminal device is provided, including: a receiving unit configured to receive first information associated with a target SSB sent by a network device, the first information being used to indicate that the target SSB is not used for the terminal device to access a first cell associated with the target SSB, wherein the target SSB is a non-cell-defining SSB or a cell-defining SSB, and transmission of the target SSB is triggered based on a request of the terminal device.

[0010] In a sixth aspect, a terminal device is provided, including: in response to a first event, a receiving unit configured to receive fourth information sent by a network device, the fourth information being used to indicate that a target SSB is activated in a secondary cell, transmission of the target SSB being triggered based on a request of the terminal device; wherein the first event includes one or more of: the secondary cell being configured; the secondary cell being activated; the network device indicating to activate the secondary cell.

[0011] In a seventh aspect, a network device is provided, including: a sending unit configured to send, to a terminal device, first information associated with a target SSB, the first information being used to indicate that the target SSB is not used for the terminal device to access a first cell associated with the target SSB, wherein the target SSB is a non-cell-defining SSB or a cell-defining SSB, and transmission of the target SSB is triggered based on a request of the terminal device.

[0012] In an eighth aspect, a network device is provided, including: in response to a first event, a sending unit configured to send, to a terminal device, fourth information, the fourth information being used to indicate that a target SSB is activated in a secondary cell, transmission of the target SSB being triggered based on a request of the terminal device; wherein the first event includes one or more of: the secondary cell being configured; the secondary cell being activated; the network device indicating to activate the secondary cell.

[0013] In a ninth aspect, a terminal device is provided, including a processor, a memory, and a communication interface, the memory being configured to store one or more computer programs, and the processor being configured to invoke the computer programs in the memory, so that the terminal device performs some or all steps in the method of the first aspect and / or the second aspect.

[0014] In a tenth aspect, a network device is provided, which includes a processor, a memory, and a transceiver. The memory is configured to store one or more computer programs. The processor is configured to invoke the computer programs in the memory, so that the network device performs some or all of the steps in the methods of the third aspect and / or the fourth aspect.

[0015] In an eleventh aspect, a communication system is provided, which includes the terminal device and / or the network device described above. In another possible design, the system can further include other devices interacting with the terminal device or the network device in the solutions provided by the embodiments.

[0016] In a twelfth aspect, a computer-readable storage medium is provided, which stores a computer program. The computer program causes a communication device (e.g., a terminal device or a network device) to perform some or all of the steps in the methods of the various aspects described above.

[0017] In a thirteenth aspect, a computer program product is provided, which includes a non-transitory computer-readable storage medium storing a computer program. The computer program is operable to cause a communication device (e.g., a terminal device or a network device) to perform some or all of the steps in the methods of the various aspects described above. In some implementations, the computer program product can be a software installation package.

[0018] In a fourteenth aspect, a chip is provided, which includes a memory and a processor. The processor can invoke and run a computer program from the memory, to implement some or all of the steps described in the methods of the various aspects described above.

[0019] In the embodiments, the network device sends the first information to the terminal device, to indicate that the target SSB for on-demand transmission is not used for the terminal device to access the first cell associated with the target SSB. Based on the first information, it can help to reduce the access error of the terminal device that does not support on-demand SSB, to improve the communication efficiency. BRIEF DESCRIPTION OF DRAWINGS

[0020] FIG. 1 is a wireless communication system 100 to which embodiments of the present disclosure are applied.

[0021] FIG. 2 is a schematic flowchart of a method of wireless communication according to an embodiment of the present disclosure.

[0022] FIG. 3 is a schematic flowchart of a method of wireless communication according to another embodiment of the present disclosure.

[0023] FIG. 4 is a schematic diagram of a first event according to an embodiment of the present disclosure.

[0024] FIG. 5 is a schematic diagram of a terminal device according to an embodiment of the present application.

[0025] FIG. 6 is a schematic diagram of a terminal device according to another embodiment of the present application.

[0026] FIG. 7 is a schematic diagram of a network device according to an embodiment of the present application.

[0027] FIG. 8 is a schematic diagram of a network device according to another embodiment of the present application.

[0028] FIG. 9 is a schematic structural diagram of a communication apparatus according to an embodiment of the present application. DETAILED DESCRIPTION

[0029] The technical solutions in the present application will be described below with reference to the accompanying drawings.

[0030] FIG. 1 is a wireless communication system 100 to which embodiments of the present application are applied. The wireless communication system 100 can include a network device 110 and a terminal device 120. The network device 110 can be a device that communicates with the terminal device 120. The network device 110 can provide communication coverage for a specific geographic area and can communicate with the terminal device 120 located in the coverage area.

[0031] FIG. 1 exemplarily shows one network device and two terminals. Optionally, the wireless communication system 100 can include multiple network devices and each network device can include other numbers of terminal devices within its coverage, which is not limited in the embodiments of the present application.

[0032] Optionally, the wireless communication system 100 can further include a network controller, a mobile management entity, and other network entities, which are not limited in the embodiments of the present application.

[0033] It should be understood that the technical solutions in the embodiments of the present application can be applied to various communication systems, for example, a 5th generation (5G) system or new radio (NR), a long term evolution (LTE) system, an LTE frequency division duplex (FDD) system, an LTE time division duplex (TDD), and the like. The technical solutions provided in the present application can also be applied to future communication systems, such as a 6th generation mobile communication system, a satellite communication system, and the like.

[0034] The terminal device in the embodiments of the present application can also be referred to as a user equipment (UE), an access terminal, a user unit, a user station, a mobile station, a mobile station (MS), a mobile terminal (MT), a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent or a user apparatus. The terminal device in the embodiments of the present application can refer to a device that provides voice and / or data connectivity for a user, and can be used to connect people, things and machines, such as handheld devices with wireless connection functions, vehicle-mounted devices, etc. The terminal device in the embodiments of the present application can be a mobile phone, a tablet computer (Pad), a notebook computer, a palm computer, a mobile internet device (MID), a wearable device, a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control, a wireless terminal in self driving, a wireless terminal in remote medical surgery, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home, etc. Optionally, the UE can be used to act as a base station. For example, the UE can act as a scheduling entity, which provides sidelink signals between UEs in V2X or D2D, etc. For example, a cellular phone and a car communicate with each other using sidelink signals. The cellular phone and the smart home device communicate with each other without relaying the communication signals through the base station.

[0035] The network device in the embodiments of the present application can be a device for communicating with a terminal device, which can also be referred to as an access network device or a radio access network device, such as a network device, which can be a base station. The network device in the embodiments of the present application can refer to a radio access network (RAN) node (or device) that accesses a terminal device to a wireless network. The base station can broadly cover various names in the following or be replaced by the following names, such as: Node B (NodeB), evolved Node B (eNB), next generation Node B (gNB), relay station, access point, transmitting and receiving point (TRP), transmitting point (TP), master station MeNB, auxiliary station SeNB, multi-standard radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. The base station can be a macro base station, a micro base station, a relay node, a donor node or the like, or a combination thereof. The base station can also refer to a communication module, modem or chip for being arranged in the foregoing device or apparatus. The base station can also be a mobile switching center and a device that undertakes a base station function in device-to-device (D2D), vehicle-to-everything (V2X), machine-to-machine (M2M) communication, network side device in 6G network, device that undertakes a base station function in future communication system, etc. The base station can support networks of the same or different access technologies. The embodiments of the present application do not limit the specific technology and specific device form adopted by the network device.

[0036] The base station can be fixed or mobile. For example, a helicopter or a drone can be configured to act as a mobile base station, and one or more cells can move according to the location of the mobile base station. In other examples, a helicopter or a drone can be configured to act as a device that communicates with another base station.

[0037] In some deployments, the network device in the embodiments of the present application can refer to a CU or a DU, or the network device includes a CU and a DU. The gNB can also include an AAU.

[0038] The network device and the terminal device can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; can also be deployed on water surface; can also be deployed on aircraft, balloons and satellites in the air. The scenarios in which the network device and the terminal device are located are not limited in the embodiments of the present application.

[0039] It should be understood that all or part of the functions of the communication device in the present application can also be implemented by software functions running on hardware, or by virtualized functions instantiated on a platform (such as a cloud platform).

[0040] Secondary cell (SCell)

[0041] Carrier aggregation (CA) refers to aggregating two or more carriers (component carriers, CCs) into a wider bandwidth resource to transmit data. In the scenario of carrier aggregation, in addition to the primary cell (PCell), the system will also configure one or more SCells. These cells collectively provide users with higher data rates and better coverage, so that the system can support more users and higher throughput, and effectively utilize scattered spectrum resources to improve the utilization rate of spectrum resources. In some scenarios, by aggregating carriers of different frequency bands, the coverage performance of the network can be improved.

[0042] Before carrying communication data, an SCell needs to be configured and activated. The configuration of an SCell is mainly completed through radio resource control (RRC) signaling, including RRCConnectionReconfiguration, which is used to add, modify or release an SCell, and medium access control control element (MAC CE) is used to activate or deactivate an SCell. A system allocates a unique cell identity number for an SCell. After activation, an SCell starts to bear part of user data transmission, and a network device dynamically allocates resources, performs scheduling and management according to network load and user demand. An SCell registers with a core network (such as an evolved packet core (EPC)) to obtain necessary network resources and permissions. A network device (for example, a base station) and a network management system continuously monitor the performance of an SCell, and perform optimization adjustment through measurement reporting and network device feedback to ensure the best performance of an SCell.

[0043] A terminal device (for example, a UE) first connects to a primary cell (PCell) to establish an initial RRC connection. A network device (for example, a NodeB) configures the terminal device to perform signal measurement on a neighbor cell (including an SCell). The specific measurement configuration is issued through RRC signaling, including a measurement object, an event type (such as A1, A2, A3, A4, A5), a measurement quantity (such as reference signal received power (RSRP) and reference signal received quality (RSRQ)), and the like.

[0044] The terminal device performs signal measurement on the neighbor cell according to the configuration, and reports a measurement report to the network device (for example, a base station) when a trigger condition is met. The measurement report includes signal strength and quality information of the neighbor cell (including an SCell).

[0045] The network device decides whether to add an SCell according to the measurement report. If it is decided to add, an indication of adding an SCell is issued to the terminal device through an RRCConnectionReconfiguration message. The RRCConnectionReconfiguration message includes configuration parameters of the SCell, such as a physical cell ID, a frequency band, a transmission power, synchronization information and the like. These parameters are used to guide the terminal device to connect and use the SCell.

[0046] When the SCell is added, the network device further issues an activation indication. The activation indication contains the activation time and related scheduling information. After receiving the activation indication, the terminal device activates the SCell according to the configuration and sends a RRC connection reconfiguration completion message (RRCConnectionReconfigurationComplete) to the network device for confirmation.

[0047] In a communication system (for example, NR), the configuration and activation of an SCell involve multiple steps, from discovery and measurement to configuration and activation, from the configuration instruction of the network device to the specific operation of the terminal device.

[0048] Before configuring the SCell, the terminal device first needs to discover and measure the neighboring cell. The terminal device receives a measurement object (MO) sent by the network device to the terminal device through RRC signaling, which specifies the frequency band and cell to be measured. The SSB measurement timing configuration (SMTC) information contained in the MO guides the terminal device to perform SSB measurement on the neighboring cell within a specific time window. The following is an example of a measurement configuration message.

[0049] The terminal device measures the SSB of the neighboring cell according to the MO and SMTC, collects information such as signal strength (such as RSRP) and quality (such as RSRQ, signal interference noise ratio (SINR)), and reports the measurement results to the network device for the network device to make configuration decisions based on the results. The measurement reporting message is as follows.

[0050] UE->eNodeB:MeasurementReport

[0051] Report:

[0052] -EventId:A3

[0053] -MeasuredObjectId:1

[0054] -MeasurementResult:-105dBm

[0055] The network device sends a RRC connection reconfiguration message to the terminal device, which contains the configuration information of the SCell, including the frequency band and bandwidth of the SCell, the physical cell identifier (PCI) of the SCell, and the downlink and uplink link configuration of the SCell. The following is an example of a RRC connection reconfiguration message.

[0056] eNodeB->UE: RRCConnectionReconfiguration

[0057] ScellToAddModList:

[0058] - ScellIndex: 1

[0059] - ServingCellId: 2

[0060] - DownlinkFrequency: <frequency>

[0061] -UplinkFrequency: <frequency>

[0062] - CellIndividualOffset: 0 dB

[0063] After receiving the RRC connection reconfiguration message, the terminal device sends confirmation information to the network device (for example, the base station), and configures the related parameters of the SCell according to the information in the message.

[0064] UE->eNodeB: RRC ConnectionReconfigurationComplete

[0065] After the SCell configuration is completed, the network device can dynamically activate or deactivate the SCell as needed to optimize resource utilization and user experience. The activation and deactivation process is implemented through MAC CE. MAC CE is a special control signaling used to deliver control information of the MAC layer. The processing delay of MAC CE is smaller than that of the control information signaling of the RRC layer, and the SCell can be activated faster. The following is an example of activation through RRC signaling.

[0066] eNodeB->UE: RRCConnectionReconfiguration

[0067] ScellToActivateList:

[0068] -ScellIndex: 1

[0069] -ActivationTime: <time>

[0070] After the terminal device receives the activation command, it begins data transmission on the SCell. This includes starting physical layer processing and resource scheduling for the SCell.

[0071] Through the above steps, the SCell is successfully configured and activated, and the terminal device can use the SCell for data transmission, thereby improving network capacity and user experience. This process relies on the precise configuration and management of RRC signaling to ensure the effective addition and activation of the SCell. When the network device decides that the SCell is no longer needed, it sends a deactivation command to the terminal device through MAC CE. After the terminal device receives the deactivation command, it stops data transmission on the SCell and releases the related resources.

[0072] In a wireless communication system, in the scenario of carrier aggregation and multi-cell deployment, the SSB of the SCell can help the terminal device with synchronization, connection, inter-cell handover, and measurement, etc. SSB includes synchronization signals (SS) and physical broadcast channel (PBCH). It is used for initial access of the terminal device, synchronization, and acquisition of cell broadcast information.

[0073] In a wireless communication system, SCell usually does not transmit SSB. SSB is mainly used for PCell, while SCell usually does not need to transmit SSB. Carrier aggregation allows multiple carriers to be used for data transmission at the same time. PCell is responsible for control signals and most management functions, while SCell is mainly used to enhance data throughput. Therefore, SCell does not need to transmit SSB because synchronization and broadcast information has already been transmitted by PCell. In addition, initial access and synchronization functions are usually handled by PCell, and SCell is mainly used to increase the bandwidth and capacity of data transmission. Therefore, SCell does not need to transmit SSB to provide synchronization information, as the terminal device has already acquired the necessary synchronization information through PCell. In addition, SCell is usually used in dense areas or hotspot areas to provide additional bandwidth. Terminal devices in these areas have already synchronized and accessed the network through PCell, and SCell only needs to be responsible for additional data transmission. Since transmitting SSB consumes additional power and resources, not transmitting SSB in SCell helps to save energy and reduce interference. SCell can be activated and used when needed without the need to transmit SSB, thereby improving the overall efficiency of the network. SCell can be located in higher frequency bands, which are mainly used for high-throughput data transmission rather than signal coverage and synchronization. Therefore, SSB transmission is not necessary in these frequency bands.

[0074] The SCell does not transmit SSB mainly because of its secondary role in the wireless communication system, mainly responsible for data transmission rather than synchronization and control functions, as the terminal device has been synchronized and initially accessed through the PCell. When the terminal device has completed synchronization and initial access through the SSB of the PCell, the SCell only needs to be configured and activated through RRC signaling. In the case of limited spectrum resources, reducing unnecessary SSB transmission can improve spectrum efficiency and reduce the power consumption of network devices and terminal devices, especially the power consumption on the network device side.

[0075] However, in some specific scenarios, the SCell may need to transmit SSB, for example, in some standalone deployment scenarios, the SCell may need to transmit SSB to support synchronization and access of terminal devices. In some complex handover scenarios, SSB transmission on the SCell can help terminal devices complete inter-cell handover more smoothly. In order to reduce the power consumption of network devices and terminal devices, in some implementations, on-demand SSB can be configured in the SCell, or in other words, SSB can be configured in the SCell, and the transmission of SSB is triggered based on the request of the terminal device.

[0076] When the SCell is configured but the terminal device does not receive the SCell activation, the SCell is a serving cell of the terminal device, and the SSB in the SCell can be configured to the terminal device through ServingCellConfigCommon, the content of ServingCellConfigCommon is as shown below.

[0077] Cell defining SSB (CD-SSB) and non-cell defining SSB (NCD-SSB) are two different types of SSBs. The SSB contains a broadcast information master information block (MIB), and part of the information in the MIB can indicate whether the SSB is a cell defining SSB. For NCD-SSB, the main use is for the broadcast and synchronization of a specific cell, so part of the information in the MIB indicates SIB1 related information, and the terminal device can detect SIB1 based on the SIB1 related information, and then perform initial access. For NCD-SSB, the main use is to broadcast system information and global radio resource management, so part of the information in the MIB does not indicate SIB1 related information, but SSB related information, so the terminal device cannot use NCD-SSB for initial access.

[0078] As described above, in a communication system, a terminal device can perform initial access based on a target SSB (e.g., a cell-defining SSB). However, when the target SSB is an on-demand SSB, a terminal device that does not support the on-demand SSB can perform initial access based on the target SSB, which can result in access errors.

[0079] For example, in a mixed deployment scenario, a low-version terminal device does not support an on-demand SSB, and a high-version terminal device supports the on-demand SSB. If the terminal device does not receive signaling of SSB modification, the terminal device can consider that the SSB has always existed and still performs periodic transmission. When the target on-demand SSB stops transmitting, the network device does not notify the target SSB of stopping transmitting in a traditional manner (i.e., periodic transmission of the SSB), but in a new manner (i.e., on-demand transmission of the SSB). The low-version terminal device does not receive the message of the new manner of notification and considers that the target SSB still performs periodic transmission. In this case, the low-version terminal device can receive a target SSB requested by the high-version terminal device on demand, and the target SSB can be a cell-defining SSB. The low-version terminal device performs access based on the target SSB, which can result in access errors.

[0080] To address the above issues, embodiments of the present disclosure provide a method of wireless communication. A network device sends first information to a terminal device to indicate that a target SSB transmitted on demand is not used by the terminal device to access a first cell associated with the target SSB. Based on the first information, access errors of terminal devices that do not support on-demand SSBs can be reduced, and communication efficiency can be improved.

[0081] A method of wireless communication according to embodiments of the present disclosure is described below in conjunction with FIG. 2. FIG. 2 is a schematic flowchart of a method of wireless communication according to embodiments of the present disclosure. The method shown in FIG. 2 includes step S210.

[0082] In step S210, a network device sends first information to a terminal device.

[0083] In some implementations, the first information is used to indicate that a target SSB is not used by the terminal device to access a first cell associated with the target SSB, and transmission of the target SSB is triggered based on a request of the terminal device, that is, based on the first information, it can be determined that the target SSB transmitted on demand is not used by the terminal device to access the first cell.

[0084] In embodiments of the present disclosure, the first cell is not limited. For example, the first cell can be an SCell. For another example, the first cell can be a PCell.

[0085] In some implementations, the first cell is associated with the target SSB, which can be understood as that the target SSB is transmitted in the first cell. For example, the first cell is an SCell, and the target SSB is configured to be transmitted in the SCell by ServingCellConfigCommon.

[0086] In some other implementations, the first cell is associated with the target SSB, which can be understood as that the target SSB carries or indicates information of the first cell.

[0087] In some implementations, the target SSB is a cell-defining SSB, which can be understood as that initial access can be performed based on the target SSB.

[0088] In some other implementations, the target SSB is a non-cell-defining SSB, which can be understood as that initial access cannot be performed based on the target SSB.

[0089] In some implementations, the first information is used to indicate that the target SSB is not used by the terminal device to access the first cell associated with the target SSB, which can be understood as that the first information is used to indicate that the target SSB is a non-cell-defining SSB.

[0090] In some implementations, if the target SSB is a cell-defining SSB, the first information is used to indicate that the target SSB is a non-cell-defining SSB, or in other words, the first information is used to indicate that the cell-defining SSB is a non-cell-defining SSB.

[0091] In some other implementations, if the target SSB is a non-cell-defining SSB, the first information is used to indicate that the target SSB is a non-cell-defining SSB, or in other words, the first information is used to indicate that the non-cell-defining SSB is a non-cell-defining SSB.

[0092] In some implementations, the first information is carried in the MIB of the target SSB. For example, the first information is carried in a field in the MIB, and the field takes a first value to indicate that the target SSB is a non-cell-defining SSB. For another example, the first value can be 0 or 1. Carrying the first information in the MIB helps to reduce the overhead of transmitting the first information.

[0093] In some other implementations, the first information is carried in the first signal, which is transmitted before the target SSB, which helps to increase the flexibility of transmitting the first information.

[0094] In some implementations, if the target SSB is a cell-defining SSB, one or more fields in the MIB are used to carry information associated with the target SSB.

[0095] In some other implementations, if the target SSB is a non-cell-defining SSB, one or more fields in the MIB are used to carry information associated with the target SSB.

[0096] In some implementations, one or more fields of the MIB can be referred to as "field A", in which information associated with the target SSB is carried, which helps the terminal device that does not support on-demand SSB to obtain accurate information.

[0097] In some implementations, the information associated with the target SSB carried in field A can be understood as the content of field A of the traditional non-cell-defined SSB.

[0098] In some implementations, the network device sends second information to the terminal device, and the second information is used to indicate whether the first cell supports triggering transmission of the SSB based on a request of the terminal device, or in other words, the second information is used to indicate whether the first cell supports on-demand SSB. Accordingly, the terminal device can determine whether the first cell supports transmitting on-demand SSB after receiving the second information.

[0099] In some implementations, the second information is carried in a field. For example, if the field takes a first value, it indicates that the first cell supports on-demand SSB. If the field takes a second value, it indicates that the first cell does not support on-demand SSB. The first value is different from the second value. For example, the first value can be 0, and the second value can be 1. For another example, the first value can be 1, and the second value can be 0.

[0100] In some implementations, the terminal device receives the target SSB transmitted by the network device in the first cell, and detects the SIB1 associated with the target SSB to determine whether the target SSB is a cell-defined SSB or a non-cell-defined SSB.

[0101] In some implementations, if the terminal device detects the SIB1 associated with the target SSB, the target SSB is a cell-defined SSB. For example, when the terminal device detects the SIB1 associated with the target SSB (for example, completes the cyclic redundancy check (CRC) of the SIB1), it can be determined that the target SSB is a cell-defined SSB.

[0102] In some implementations, if the terminal device does not detect the SIB1 associated with the target SSB, the target SSB is a non-cell-defined SSB.

[0103] In some implementations, if the first cell and the terminal device both support triggering transmission of the SSB based on a request of the terminal device, the terminal device detects the SIB1 associated with the target SSB, that is, if the target SSB is an on-demand SSB, the terminal device that supports on-demand SSB detects the SIB1 associated with the target SSB.

[0104] In some implementations, if the target SSB is a cell-defining SSB, the information associated with the target SSB is carried in the configuration information of the first cell.

[0105] In some implementations, the configuration information of the first cell includes downlinkConfigCommon. For example, assuming that the first cell is an SCell, the information associated with the SSB can be notified to the terminal device in the downlinkConfigCommon signaling of the SCell configuration.

[0106] In some implementations, the information associated with the target SSB includes time domain resources and / or frequency domain resources for detecting a SIB1 associated with the target SSB. For example, the information associated with the target SSB includes Kssb and pdcch-ConfigSIB1, based on which information of a control-resource set (CORESET) of common control information can be determined, and the terminal device can blind detect the SIB1 associated with the target SSB in the common CORESET. It should be noted that Kssb and pdcch-ConfigSIB1 are contents in the MIB of a traditional cell-defining SSB. For another example, the information associated with the target SSB includes time domain resources and / or frequency domain resources for transmitting a SIB1 associated with the target SSB, the time domain resources can include symbols, slots, subframes, frames, etc., and the frequency domain resources can include subcarriers, frequency bands, bandwidths, etc., and the SIB1 associated with the target SSB can be detected on the time domain resources and / or the frequency domain resources for transmitting the SIB1 associated with the target SSB.

[0107] When the target SSB is a non-cell-defining SSB, the above method of detecting a SIB1 associated with the target SSB to determine whether the target SSB is a cell-defining SSB increases the processing of the terminal device for decoding the SIB1. In order to reduce unnecessary decoding, in some implementations, the network device sends third information to the terminal device, the third information being used to indicate whether an SSB transmitted in the first cell is a cell-defining SSB or a non-cell-defining SSB, and the SSB transmitted in the first cell includes the target SSB.

[0108] In some implementations, the third information is carried in the configuration information of the first cell. For example, the configuration information of the first cell includes a first field, and when the first field takes a first value, it indicates that the SSB transmitted in the first cell is a cell-defining SSB. When the first field takes a second value, it indicates that the SSB transmitted in the first cell is a non-cell-defining SSB. The first value and the second value are different. For example, the first value can be 0, and the second value can be 1. For another example, the first value can be 1, and the second value can be 0.

[0109] In some implementations, the third information is carried in an SMTC window of the first cell. For example, the first cell is a SCell, and the third information is carried in smtc in SCellConfig below.

[0110] In some other implementations, the third information is carried in high layer signaling of the first cell. For example, the first cell is a SCell, and the third information is carried in SCellConfigCommon in SCellConfig above.

[0111] It should be noted that when the third information is used to indicate that the SSB transmitted in the first cell is a cell-defining SSB or a non-cell-defining SSB, the information associated with the target SSB in the above-mentioned scheme using the second information can also be used to detect the SIB1 associated with the target SSB. The interpretation of the information associated with the target SSB is described above and will not be repeated here.

[0112] From the above, it can be seen that the network device can configure the transmission of the SSB in the SCell, but after the SCell is configured for the terminal device, how to activate the transmission of the on-demand SSB is a problem to be solved urgently.

[0113] To solve the above problem, the embodiment of the present application proposes a method of wireless communication. When the secondary cell state is about to change or has changed (for example, the secondary cell is activated or the network device instructs to activate the secondary cell), the network device sends fourth information to the terminal device to indicate the activation of the on-demand SSB.

[0114] The method of wireless communication of the embodiment of the present application is described below in combination with FIG. 3. FIG. 3 is a schematic flowchart of the method of wireless communication of the embodiment of the present application. The method shown in FIG. 3 includes step S310.

[0115] In step S310, in response to a first event, the network device sends fourth information to the terminal device.

[0116] In some implementations, the fourth information is used to indicate the activation of a target SSB in the secondary cell, and the transmission of the target SSB is triggered based on the request of the terminal device, that is, the fourth information is used to indicate the activation of the on-demand SSB in the secondary cell. Accordingly, the terminal device receiving the fourth information can send a request to request the network device to send the on-demand SSB.

[0117] In some embodiments, the first event comprises one or more of the following: the secondary cell is configured, the secondary cell is activated, and the network device indicates to activate the secondary cell. For example, referring to FIG. 4, the secondary cell is configured occurs at time T1, the network device indicates to activate the secondary cell occurs at time T2, and the secondary cell is activated occurs at time T3. The network device can send the fourth information to the terminal device at a time between T1 and T2, at a time between T2 and T3, and after time T3, that is, the on-demand SSB can be activated at different stages after the SCell is configured.

[0118] In some embodiments, the network device indicates to activate the secondary cell can be understood as that the terminal device receives a command sent by the network device to activate the secondary cell.

[0119] In some embodiments, the fourth information is carried in a serving cell common configuration associated with the secondary cell. For example, the fourth information is carried in the ServingCellConfigCommon described above. For another example, the fourth information is carried in a field in the ServingCellConfigCommon, and the field takes a first value, which indicates to activate the on-demand SSB in the secondary cell. For another example, the first value can be 0 or 1.

[0120] The method embodiments of the present application are described in detail above in combination with FIGs. 1 to 4, and the device embodiments of the present application are described in detail below in combination with FIGs. 5 to 9. It should be understood that the description of the method embodiments corresponds to the description of the device embodiments, and therefore, the parts not described in detail can be referred to the method embodiments.

[0121] FIG. 5 is a schematic diagram of a terminal device according to an embodiment of the present application. The terminal device 500 comprises a receiving unit 510.

[0122] The receiving unit 510 is configured to receive first information associated with a target SSB sent by a network device, the first information being used to indicate that the target SSB is not used for the terminal device to access a first cell associated with the target SSB, wherein the target SSB is a non-cell-defined SSB or a cell-defined SSB, and transmission of the target SSB is triggered based on a request of the terminal device.

[0123] In some embodiments, the first information is used to indicate that the target SSB is a non-cell-defined SSB.

[0124] In some embodiments, the first information is carried in a MIB of the target SSB.

[0125] In some embodiments, if the target SSB is a cell-defined SSB, one or more fields in the MIB are used to carry information associated with the target SSB.

[0126] In some embodiments, the terminal device further includes: the receiving unit is further configured to receive second information sent by the network device, the second information being used to indicate whether the first cell supports triggering SSB transmission based on a request of the terminal device.

[0127] In some embodiments, the terminal device further includes: the receiving unit is further configured to receive the target SSB sent by the network device in the first cell; and a detecting unit is configured to detect a SIB1 associated with the target SSB to determine whether the target SSB is a cell-defining SSB or a non-cell-defining SSB.

[0128] In some embodiments, the terminal device detects the SIB1 associated with the target SSB, including: if both the first cell and the terminal device support triggering SSB transmission based on a request of the terminal device, the terminal device detects the SIB1 associated with the target SSB.

[0129] In some embodiments, the terminal device further includes: the receiving unit is further configured to receive third information sent by the network device, the third information being used to indicate whether a SSB transmitted in the first cell is a cell-defining SSB or a non-cell-defining SSB, the SSB transmitted in the first cell including the target SSB.

[0130] In some embodiments, the third information is carried in one or more of the following: configuration information of the first cell; SMTC of the first cell; and SCellConfigCommon of the first cell.

[0131] In some embodiments, if the target SSB is a cell-defining SSB, information associated with the target SSB is carried in the configuration information of the first cell.

[0132] In some embodiments, the configuration information of the first cell includes downlinkConfigCommon.

[0133] In some embodiments, the information associated with the target SSB includes time domain resources and / or frequency domain resources used to detect the SIB1 associated with the SSB.

[0134] FIG. 6 is a schematic diagram of a terminal device according to an embodiment of the present application. The terminal device 600 includes a sending unit 610.

[0135] In some embodiments, in response to a first event, the receiving unit 610 is configured to receive fourth information sent by the network device, the fourth information being used to indicate that a target SSB is activated in a secondary cell, and transmission of the target SSB is triggered based on a request of the terminal device; wherein the first event includes one or more of the following: the secondary cell is configured; the secondary cell is activated; the network device indicates to activate the secondary cell.

[0136] In some embodiments, the fourth information is carried in a service cell common configuration associated with the secondary cell.

[0137] FIG. 7 is a schematic diagram of a network device according to an embodiment of the present application. The network device 700 includes a sending unit 710.

[0138] The sending unit 710 is configured to send, to a terminal device, first information associated with a target SSB, the first information being used to indicate that the target SSB is not used by the terminal device to access a first cell associated with the target SSB, wherein the target SSB is a non-cell-defining SSB or a cell-defining SSB, and transmission of the target SSB is triggered based on a request of the terminal device.

[0139] In some embodiments, the first information is used to indicate that the target SSB is a non-cell-defining SSB.

[0140] In some embodiments, the first information is carried in a MIB of the target SSB.

[0141] In some embodiments, if the target SSB is a cell-defining SSB, one or more fields in the MIB are used to carry information associated with the target SSB.

[0142] In some embodiments, the network device further includes that the sending unit is further configured to send, to the terminal device, second information, the second information being used to indicate whether the first cell supports triggering SSB transmission based on a request of the terminal device.

[0143] In some embodiments, the network device further includes that the sending unit is configured to send, to the terminal device, third information, the third information being used to indicate that an SSB transmitted in the first cell is a cell-defining SSB or a non-cell-defining SSB, and the SSB transmitted in the first cell includes the target SSB.

[0144] In some embodiments, the third information is carried in one or more of the following: configuration information of the first cell; SMTC of the first cell; SCellConfigCommon of the first cell.

[0145] In some embodiments, if the target SSB is a cell-defining SSB, the information associated with the target SSB is carried in configuration information of the first cell.

[0146] In some embodiments, the configuration information of the first cell includes downlinkConfigCommon.

[0147] In some embodiments, the information associated with the target SSB includes time domain resources and / or frequency domain resources for detecting a SIB1 associated with the target SSB.

[0148] FIG. 8 is a schematic diagram of a network device according to an embodiment of the present application. The network device 800 includes a sending unit 810.

[0149] In response to a first event, the sending unit 810 is configured to send fourth information to a terminal device, the fourth information being used to indicate that a target SSB is activated in a secondary cell, and transmission of the target SSB is triggered based on a request of the terminal device; wherein the first event includes one or more of the following: the secondary cell is configured; the secondary cell is activated; the network device indicates to activate the secondary cell.

[0150] In some embodiments, the fourth information is carried in a serving cell common configuration associated with the secondary cell.

[0151] In optional embodiments, the receiving unit 510 can be a transceiver 930. The terminal device 500 can further include a processor 910 and a memory 920, as shown in FIG. 9.

[0152] In optional embodiments, the receiving unit 610 can be a transceiver 930. The terminal device 600 can further include a processor 910 and a memory 920, as shown in FIG. 9.

[0153] In optional embodiments, the sending unit 710 can be a transceiver 930. The network device 700 can further include a processor 910 and a memory 920, as shown in FIG. 9.

[0154] In optional embodiments, the sending unit 810 can be a transceiver 930. The network device 800 can further include a processor 910 and a memory 920, as shown in FIG. 9.

[0155] FIG. 9 is a schematic structural diagram of a communication apparatus according to an embodiment of the present application. The dashed line in FIG. 9 indicates that the unit or module is optional. The apparatus 900 can be used to implement the method described in the above method embodiments. The apparatus 900 can be a chip, a terminal device or a network device.

[0156] The apparatus 900 can include one or more processors 910. The processor 910 can support the apparatus 900 to implement the methods described in the foregoing method embodiments. The processor 910 can be a general purpose processor or a special purpose processor. For example, the processor can be a central processing unit (CPU). Alternatively, the processor can also be other general purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gates or transistor logic, discrete hardware components, etc. The general purpose processor can be a microprocessor or the processor can also be any conventional processor.

[0157] The apparatus 900 can also include one or more memories 920. The memory 920 stores a program that can be executed by the processor 910, so that the processor 910 executes the methods described in the foregoing method embodiments. The memory 920 can be independent of the processor 910 or integrated in the processor 910.

[0158] The apparatus 900 can also include a transceiver 930. The processor 910 can communicate with other devices or chips through the transceiver 930. For example, the processor 910 can perform data transceiving with other devices or chips through the transceiver 930.

[0159] The embodiments of the present application also provide a computer readable storage medium for storing a program. The computer readable storage medium can be applied to the terminal or network device provided by the embodiments of the present application, and the program causes the computer to execute the method performed by the terminal or network device in the various embodiments of the present application.

[0160] The embodiments of the present application also provide a computer program product. The computer program product includes a program. The computer program product can be applied to the terminal or network device provided by the embodiments of the present application, and the program causes the computer to execute the method performed by the terminal or network device in the various embodiments of the present application.

[0161] The embodiments of the present application also provide a computer program. The computer program can be applied to the terminal or network device provided by the embodiments of the present application, and the computer program causes the computer to execute the method performed by the terminal or network device in the various embodiments of the present application.

[0162] It should be understood that the terms "system" and "network" can be used interchangeably in this application. In addition, the terms used in this application are only used to explain the specific embodiments of the application, and are not intended to limit the application. The terms "first", "second", "third", and "fourth" and the like in the specification and claims of the application and the drawings are used to distinguish different objects, and are not used to describe a particular order. In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusion.

[0163] In embodiments of the present application, the term "indicate" can be direct indication or indirect indication, or can represent an associated relationship. For example, A indicates B, which can mean that B can be obtained directly through A; or A indirectly indicates B, for example, A indicates C, and B can be obtained through C; or A and B have an associated relationship.

[0164] In embodiments of the present application, the term "corresponding" can represent a direct or indirect corresponding relationship between the two, or can represent an associated relationship between the two, or can represent an indication and being indicated, configuration and being configured, etc.

[0165] In embodiments of the present application, the term "and / or" is only used to describe the associated relationship between the associated objects, which means that there can be three relationships, for example, A and / or B, which can mean that A exists alone, A and B exist together, and B exists alone. In addition, the character " / " in this paper generally represents a "or" relationship between the associated objects before and after.

[0166] In several embodiments provided by the present application, it should be understood that the disclosed system, device and method can be implemented by other means. For example, the above-described device embodiments are only illustrative, for example, the division of the units is only a logical function division, and actual implementation can have another division manner, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the displayed or discussed objects can be indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0167] The units described as separate components can or can not be physically separated, and the components shown as units can or can not be physical units, that is, they can be located in one place, or can be distributed on a plurality of network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the embodiment scheme.

[0168] In addition, each function unit in each embodiment of the present application can be integrated in one processing unit, or each unit can be physically present separately, or two or more units can be integrated in one unit.

[0169] In the above embodiments, all or part of the embodiments can be implemented by software, hardware, firmware or any combination thereof. When implemented by software, all or part of the embodiments can be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center through wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) mode. The computer readable storage medium can be any available medium that can be read by a computer or a data storage device such as a server, data center, etc. integrated with one or more available media. The available media can be magnetic media (for example, floppy disk, hard disk, magnetic tape), optical media (for example, digital video disc (DVD)) or semiconductor media (for example, solid state disk (SSD)) and the like.

[0170] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art can easily think of changes or replacements within the technical range disclosed in the present application, which should be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.< / time> < / frequency> < / frequency>

Claims

1. A method of wireless communication, comprising: Comprising: receiving, by a terminal device, first information associated with a target synchronization signal block (SSB) from a network device, the first information indicating that the target SSB is not used for the terminal device to access a first cell associated with the target SSB, wherein the target SSB is a non-cell-defining SSB or a cell-defining SSB, and transmission of the target SSB is triggered based on a request from the terminal device.

2. The method of claim 1, wherein, The first information indicates that the target SSB is a non-cell-defining SSB.

3. The method of claim 1 or 2, wherein, The first information is carried in a master information block (MIB) of the target SSB.

4. The method of claim 3, wherein, If the target SSB is a cell-defining SSB, one or more fields in the MIB are used to carry information associated with the target SSB.

5. The method of any one of claims 1-4, wherein, The method further comprises: receiving, by the terminal device, second information from the network device, the second information indicating whether the first cell supports triggering SSB transmission based on a request from the terminal device.

6. The method of any one of claims 1-5, wherein, The method further comprises: receiving, by the terminal device, the target SSB from the network device in the first cell; detecting, by the terminal device, a system information block (SIB1) associated with the target SSB to determine whether the target SSB is a cell-defining SSB or a non-cell-defining SSB.

7. The method of claim 6, wherein, The detecting, by the terminal device, the SIB1 associated with the target SSB comprises: If the first cell and the terminal device both support triggering SSB transmission based on a request from the terminal device, detecting, by the terminal device, the SIB1 associated with the target SSB.

8. The method of any one of claims 1-7, wherein, The method further comprises: receiving, by the terminal device, third information from the network device, the third information indicating whether SSBs transmitted in the first cell are cell-defining SSBs or non-cell-defining SSBs, the SSBs transmitted in the first cell including the target SSB.

9. The method of claim 8, wherein, The third information is carried in one or more of: configuration information of the first cell; SSB measurement timing configuration (SMTC) of the first cell; SCellConfigCommon of the first cell.

10. The method of any one of claims 1-9, wherein, If the target SSB is a cell-defining SSB, information associated with the target SSB is carried in the configuration information of the first cell.

11. The method of claim 10, wherein, The configuration information of the first cell includes downlinkConfigCommon.

12. The method of claim 10 or 11, wherein, The information associated with the target SSB includes time domain resources and / or frequency domain resources for detecting the SIB1 associated with the SSB.

13. A method of wireless communication, comprising: Comprising: receiving, by a terminal device, fourth information from a network device in response to a first event, the fourth information indicating that a target synchronization signal block (SSB) is activated in a secondary cell, and transmission of the target SSB is triggered based on a request from the terminal device; wherein the first event comprises one or more of: the secondary cell is configured; the secondary cell is activated; the network device indicates to activate the secondary cell.

14. The method of claim 13, wherein, The fourth information is carried in a serving cell common configuration associated with the secondary cell.

15. A method of wireless communication, comprising: Comprising: The network device sends first information associated with the target SSB to the terminal device, the first information being used to indicate that the target SSB is not used for the terminal device to access a first cell associated with the target SSB, wherein the target SSB is a non-cell-defining SSB or a cell-defining SSB, and transmission of the target SSB is triggered based on a request of the terminal device.

16. The method of claim 15, wherein, The first information is used to indicate that the target SSB is a non-cell-defining SSB.

17. The method of claim 15 or 16, wherein, The first information is carried in a MIB of the target SSB.

18. The method of claim 17, wherein, If the target SSB is a cell-defining SSB, one or more fields in the MIB are used to carry information associated with the target SSB.

19. The method of any one of claims 15-18, wherein, The method further comprises: The network device sends second information to the terminal device, the second information being used to indicate whether the first cell supports triggering SSB transmission based on a request of the terminal device.

20. The method of any one of claims 15-19, wherein, The method further comprises: The network device sends third information to the terminal device, the third information being used to indicate that SSBs transmitted in the first cell include a cell-defining SSB or a non-cell-defining SSB, the SSBs transmitted in the first cell including the target SSB.

21. The method of claim 20, wherein, The third information is carried in one or more of the following: configuration information of the first cell; SMTC of the first cell; SCellConfigCommon of the first cell.

22. The method of any one of claims 15-21, wherein, If the target SSB is a cell-defining SSB, the information associated with the target SSB is carried in the configuration information of the first cell.

23. The method of claim 22, wherein, The configuration information of the first cell includes downlinkConfigCommon.

24. The method of claim 22 or 23, wherein, The information associated with the target SSB includes time domain resources and / or frequency domain resources used to detect a SIB1 associated with the SSB.

25. A method of wireless communication, comprising: Comprise: In response to a first event, the network device sends fourth information to the terminal device, the fourth information being used to indicate that a target SSB is activated in a secondary cell, and transmission of the target SSB is triggered based on a request of the terminal device; wherein the first event includes one or more of the following: The secondary cell is configured; The secondary cell is activated; The network device indicates to activate the secondary cell.

26. The method of claim 25, wherein, The fourth information is carried in a serving cell common configuration associated with the secondary cell.

27. A terminal device, comprising: Comprise: A receiving unit is configured to receive first information associated with a target SSB sent by a network device, the first information being used to indicate that the target SSB is not used for a terminal device to access a first cell associated with the target SSB, wherein the target SSB is a non-cell-defining SSB or a cell-defining SSB, and transmission of the target SSB is triggered based on a request of the terminal device.

28. The terminal device of claim 27, wherein, The first information is used to indicate that the target SSB is a non-cell-defining SSB.

29. The terminal device according to claim 27 or 28, characterized by The first information is carried in a MIB of the target SSB.

30. The terminal device of claim 29, wherein, If the target SSB is a cell-defining SSB, one or more fields in the MIB are used to carry information associated with the target SSB.

31. The terminal device of any one of claims 27-30, wherein, The terminal device further comprises: The receiving unit is further configured to receive second information sent by the network device, the second information being used to indicate whether the first cell supports triggering SSB transmission based on a request of the terminal device.

32. The terminal device of any one of claims 27-31, wherein, The terminal device further includes: The receiving unit is further configured to receive the target SSB sent by the network device in the first cell. The detecting unit is configured to detect SIB1 associated with the target SSB to determine whether the target SSB is a cell-defined SSB or a non-cell-defined SSB.

33. The terminal device of claim 32, wherein, The terminal device detects SIB1 associated with the target SSB, including: If the first cell and the terminal device both support triggering SSB transmission based on a request of the terminal device, the terminal device detects SIB1 associated with the target SSB.

34. The terminal device of any one of claims 27-33, wherein, The terminal device further includes: The receiving unit is further configured to receive third information sent by the network device, the third information being used to indicate whether SSB transmitted in the first cell is a cell-defined SSB or a non-cell-defined SSB, the SSB transmitted in the first cell including the target SSB.

35. The terminal device of claim 34, wherein, The third information is carried in one or more of the following: configuration information of the first cell; SMTC of the first cell; SCellConfigCommon of the first cell.

36. The terminal device of any one of claims 27-35, wherein, If the target SSB is a cell-defined SSB, information associated with the target SSB is carried in the configuration information of the first cell.

37. The terminal device of claim 36, wherein, The configuration information of the first cell includes downlinkConfigCommon.

38. The terminal device according to claim 36 or 37, characterized by The information associated with the target SSB includes time domain resources and / or frequency domain resources for detecting SIB1 associated with the SSB.

39. A terminal device, comprising: including: In response to a first event, the receiving unit is configured to receive fourth information sent by the network device, the fourth information being used to indicate that a target SSB is activated in a secondary cell, transmission of the target SSB being triggered based on a request of the terminal device. The first event includes one or more of the following: The secondary cell is configured; The secondary cell is activated; The network device indicates to activate the secondary cell.

40. The terminal device of claim 39, wherein, The fourth information is carried in a serving cell common configuration associated with the secondary cell.

41. A network device, comprising: including: The sending unit is configured to send first information associated with a target SSB to a terminal device, the first information being used to indicate that the target SSB is not used for the terminal device to access a first cell associated with the target SSB, The target SSB is a non-cell-defined SSB or a cell-defined SSB, and transmission of the target SSB is triggered based on a request of the terminal device.

42. The network device of claim 41, wherein, The first information is used to indicate that the target SSB is a non-cell-defined SSB.

43. The network device of claim 41 or 42, wherein, The first information is carried in MIB of the target SSB.

44. The network device of claim 43, wherein, If the target SSB is a cell-defined SSB, one or more fields in the MIB are used to carry information associated with the target SSB.

45. The network device of any of claims 41-44, wherein, The network device further includes: The sending unit is further configured to send second information to the terminal device, the second information being used to indicate whether the first cell supports triggering SSB transmission based on a request of the terminal device.

46. The network device of any of claims 41-45, wherein, The network device further includes: The sending unit is further configured to send third information to the terminal device, the third information being used to indicate whether a SSB transmitted in the first cell is a cell-defined SSB or a non-cell-defined SSB, the SSB transmitted in the first cell including the target SSB.

47. The network device of claim 46, wherein, The third information is carried in one or more of the following: configuration information of the first cell; SMTC of the first cell; SCellConfigCommon of the first cell.

48. The network device of any of claims 41-47, wherein, If the target SSB is a cell-defined SSB, information associated with the target SSB is carried in the configuration information of the first cell.

49. The network device of claim 48, wherein, The configuration information of the first cell includes downlinkConfigCommon.

50. The network device of claim 48 or 49, wherein, The information associated with the target SSB includes time domain resources and / or frequency domain resources used to detect a SIB1 associated with the SSB. 51.A network device for wireless communication, comprising: including: In response to a first event, the sending unit is configured to send fourth information to the terminal device, the fourth information being used to indicate that a target SSB is activated in a secondary cell, transmission of the target SSB being triggered based on a request of the terminal device; The first event includes one or more of the following: The secondary cell is configured; The secondary cell is activated; The network device indicates to activate the secondary cell.

52. The network device of claim 51, wherein, The fourth information is carried in a serving cell common configuration associated with the secondary cell.

53. A terminal device, comprising: A terminal device includes a transceiver, a memory, and a processor, the memory being used to store a program, the processor being used to invoke the program in the memory and control the transceiver to receive or send signals, so that the terminal device performs the method in any one of claims 1-14.

54. A network device, comprising: A network device includes a transceiver, a memory, and a processor, the memory being used to store a program, the processor being used to invoke the program in the memory and control the transceiver to receive or send signals, so that the network device performs the method in any one of claims 15-26.

55. An apparatus comprising: A device includes a processor configured to invoke a program from a memory, so that the device performs the method in any one of claims 1-26.

56. A chip, comprising: A chip includes a processor configured to invoke a program from a memory, so that a device in which the chip is installed performs the method in any one of claims 1-26.

57. A computer-readable storage medium, characterized in that, A computer program product has a program stored thereon, the program causing a computer to perform the method in any one of claims 1-26.

58. A computer program product, characterised in that, A computer program product has a program stored thereon, the program causing a computer to perform the method in any one of claims 1-26.

59. A computer program characterised in that, The computer program product causes a computer to perform the method in any one of claims 1-26.

Images