Communication method, and terminal device and network device

Abstract

Provided are a communication method, and a terminal device and a network device. The communication method comprises: a terminal device receiving an SSB sent by a network device, wherein the SSB comprises MIB information, the MIB information is used for indicating that access to a cell is prohibited, and the SSB is used by the terminal device to access the cell. When MIB information indicates that access to a cell is prohibited, a terminal device supporting a lower protocol version does not access the cell, and a terminal device supporting a higher protocol version can further determine, by means of related content in the MIB information, whether to access the cell, and access the cell by means of an SSB when determining that the access to the cell is allowed, thereby implementing cell access control over terminal devices of different protocol versions.

Description

Communication methods, terminal equipment and network equipment Technical Field

[0001] This application relates to the field of communication technology, and more specifically, to a communication method, terminal equipment, and network equipment. Background Technology

[0002] When terminal devices with different protocol versions exist in a communication system, a synchronization signal block / physical broadcast channel block (SS / PBCH block, SSB) sent to a terminal device of one version may be received by a terminal device of another version and incorrectly used for cell access and measurement. Therefore, how to perform cell access control for terminal devices with different protocol versions becomes a problem that needs to be solved.

[0003] Summary of the Invention

[0004] This application provides a communication method, a terminal device, and a network device. The various aspects covered by this application are described below.

[0005] In a first aspect, a communication method is provided, comprising: a terminal device receiving an SSB sent by a network device, the SSB including MIB information, the MIB information being used to indicate that access to a cell is prohibited, and the SSB being used by the terminal device to access the cell.

[0006] In a second aspect, a communication method is provided, comprising: a network device sending a synchronization signal broadcast channel block (SSB) to a terminal device, the SSB including MIB information, the MIB information being used to indicate that access to the cell is prohibited, and the SSB being used by the terminal device to access the cell.

[0007] Thirdly, a terminal device is provided, comprising: a receiving unit for receiving an SSB sent by a network device, the SSB including MIB information, the MIB information being used to indicate that access to the cell is prohibited, and the SSB being used by the terminal device to access the cell.

[0008] Fourthly, a network device is provided, comprising: a transmitting unit, configured to transmit a synchronization signal broadcast channel block (SSB) to a terminal device, the SSB including MIB information, the MIB information being used to indicate that access to the cell is prohibited, and the SSB being used by the terminal device to access the cell.

[0009] Fifthly, a terminal device is provided, including a processor, a memory, and a transceiver. The memory is used to store one or more computer programs, and the processor is used to invoke the computer programs in the memory and control the transceiver to receive or send signals, so that the terminal device performs some or all of the steps in the method described in the first aspect.

[0010] In a sixth aspect, a network device is provided, including a processor, a memory, and a transceiver, wherein the memory is used to store one or more computer programs, the processor is used to invoke the computer programs in the memory, and control the transceiver to receive or send signals, causing the terminal device to perform some or all of the steps in the method described in the second aspect.

[0011] In a seventh aspect, a communication system is provided, comprising the aforementioned terminal device and network device. Optionally, the communication system further includes other devices that interact with the terminal device and network device.

[0012] Eighthly, a computer-readable storage medium is provided, the computer-readable storage medium storing a computer program that causes a terminal device and a network device to perform some or all of the steps of the methods described in the preceding aspects.

[0013] A ninth aspect provides a computer program product comprising a non-transitory computer-readable storage medium storing a computer program operable to cause terminal devices and network devices to perform some or all of the steps of the methods described in the preceding aspects. Optionally, the computer program product includes a software installation package.

[0014] In a tenth aspect, a chip is provided, the chip including a memory and a processor, the processor being able to call and run a computer program from the memory to implement some or all of the steps described in the methods of the foregoing aspects.

[0015] In this embodiment, when the MIB information in the SBB indicates that cell access is prohibited, terminal devices supporting lower protocol versions will not access the cell. However, for terminal devices supporting higher protocol versions, access to the cell can be further determined through the relevant content in the MIB information. If cell access is permitted, access is granted through the SSB. This achieves cell access control for terminal devices with different protocol versions. Therefore, when a terminal device supporting a lower protocol version detects an SSB sent to a terminal device supporting a higher protocol version, it will not mistakenly use an SSB that does not belong to it for access and measurement, thus avoiding subsequent communication quality degradation or even connection interruption. Attached Figure Description

[0016] Figure 1 is a schematic diagram of a wireless communication system that may be applied in the embodiments of this application.

[0017] Figure 2 is a schematic flowchart of a communication method according to an embodiment of this application.

[0018] Figure 3 is a schematic block diagram of a terminal device according to an embodiment of this application.

[0019] Figure 4 is a schematic block diagram of a network device according to an embodiment of this application.

[0020] Figure 5 is a schematic block diagram of a communication apparatus according to an embodiment of this application. Detailed Implementation

[0021] The technical solutions in this application will now be described with reference to the accompanying drawings. For ease of understanding, the communication terms and processes that may be involved in the embodiments of this application will be introduced first with reference to Figure 1.

[0022] Wireless communication system

[0023] Figure 1 is a system architecture example diagram of a wireless communication system 100 applicable to embodiments of this application. The wireless communication system 100 may include a network device 110 and a terminal device 120. The network device 110 may be a device that communicates with the terminal device 120. The network device 110 can provide network coverage for a specific geographical area and can communicate with the terminal device 120 located within that coverage area. The terminal device 120 can access a network (such as a wireless network) through the network device 110. Optionally, the wireless communication system 100 may also include other network entities such as a network controller and a mobility management entity, which are not limited in this embodiment.

[0024] It should be understood that the technical solutions of the embodiments of this application can be applied to various communication systems, such as: fifth generation (5G) systems or new radio (NR), long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, etc. The technical solutions provided in this application can also be applied to future communication systems, such as sixth generation mobile communication systems, satellite communication systems, etc.

[0025] The terminal device in this application embodiment can also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device. The terminal device in this application embodiment can be a device that provides voice and / or data connectivity to a user, and can be used to connect people, objects, and machines, such as a handheld device with wireless connectivity, vehicle-mounted device, etc. The terminal devices in the embodiments of this application can be mobile phones, tablets, laptops, PDAs, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, self-driving, remote medical surgery, smart grids, transportation safety, smart cities, and smart homes, etc. Optionally, the terminal device can act as a base station. For example, the terminal device can act as a scheduling entity, providing sidelink signals between terminal devices in vehicle-to-everything (V2X) or device-to-device (D2D) systems. For instance, cellular phones and cars communicate with each other using sidelink signals. Cellular phones and smart home devices communicate without relaying communication signals through base stations.

[0026] The network device in this application embodiment can be a device for communicating with terminal devices. This network device can be, for example, an access network device or a wireless access network device. For instance, the network device can be a base station. The term "base station" can broadly encompass various names such as, or be replaced by, the following: NodeB, evolved NodeB (eNB), next-generation NodeB (gNB), relay station, access point, transmitting and receiving point (TRP), transmitting point (TP), 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. A base station can be a macro base station, micro base station, relay node, donor node, or the like, or a combination thereof.

[0027] Radio resource control (RRC) status and mobility management

[0028] Currently, the protocol defines three RRC states for terminal devices: RRC connected, RRC idle, and RRC inactive.

[0029] The RRC connected state refers to the state a terminal device is in after completing a random access procedure but before releasing the RRC. An RRC connection exists between the terminal device and a network device (e.g., an access network device). In the RRC connected state, the terminal device can transmit data with the network device, such as downlink and / or uplink data transmission. Alternatively, the terminal device can also transmit terminal-specific data and / or control channels with the network device to transmit specific information or unicast information.

[0030] In RRC connected mode, network devices can determine the cell-level location information of terminal devices, meaning they can identify the cell to which the terminal device belongs. When a terminal device moves in RRC connected mode, such as from one cell to another, the network device can control the terminal device to perform a cell handover. Therefore, mobility management for terminal devices in RRC connected mode can include cell handover. Furthermore, mobility management for terminal devices in RRC connected mode can be controlled by the network device, allowing the terminal device to handover to a designated cell according to instructions issued by the network device.

[0031] RRC idle state refers to the state of a terminal device when it is camped in a cell but has not yet performed random access. The terminal device typically enters the RRC idle state after powering on or after RRC release. In the RRC idle state, there is no RRC connection between the terminal device and network devices (e.g., the camped network device), the network device does not store the terminal device's context, and no connection has been established between the network device and the core network for that terminal device. If the terminal device needs to transition from the RRC idle state to the RRC connected state, it must initiate an RRC connection establishment process.

[0032] In RRC idle state, the core network (CN) can send paging messages to the terminal device; that is, the paging process can be triggered by the CN. Optionally, the paging area can also be configured by the CN. In some cases, for a terminal device in RRC idle state, when the terminal device moves its location (e.g., from one cell to another), the terminal device can initiate a cell reselection process. In other cases, for a terminal device in RRC idle state, when the terminal device needs to access a cell, the terminal device can initiate a cell selection process. In other words, mobility management of a terminal device in RRC idle state can include cell reselection and / or cell selection.

[0033] The RRC inactive state is a state defined to reduce air interface signaling, quickly restore radio connectivity, and quickly restore data services. The RRC inactive state is a state between the connected state and the idle state. The terminal device had previously entered the RRC connected state and then released the RRC connection with the network device, but the network device retained the terminal device's context. Furthermore, the connection established between the network device and the core network for this terminal device was not released; that is, the user plane bearer and control plane bearer between the RAN and CN are still maintained, i.e., a CN-NR connection exists.

[0034] In the RRC inactive state, the RAN can send paging messages to the terminal device, meaning the paging process can be triggered by the RAN. RAN-based paging areas are managed by the RAN, and network devices can determine the location of the terminal device at the RAN paging area level.

[0035] In some cases, for a terminal device in RRC inactive state, when the terminal device moves its location (e.g., from one cell to another), the terminal device can initiate a cell reselection procedure. In other cases, for a terminal device in RRC inactive state, when the terminal device needs to access a cell, the terminal device can initiate a cell selection procedure. In other words, mobility management of a terminal device in RRC inactive state can include cell reselection and / or cell selection.

[0036] SSB

[0037] SSB plays a crucial role in the initial access, synchronization, and acquisition of cell broadcast information for terminal devices. For example, it carries the cell identity (ID), performs time-frequency synchronization, indicates symbol-level / timeslot-level / frame timing, measures beam strength / signal quality, and measures cell signal strength / signal quality. Cell signal strength / signal quality measurements may include radio resource management (RRM) measurements and channel state information (CSI) measurements. Beam strength / signal quality measurements can be used for beam selection, beam fault detection, and beam fault recovery.

[0038] The Support Bus (SB) comprises the primary synchronization signal (PSS), secondary synchronization signal (SSS), physical broadcast channel (PBCH), and demodulation reference signal (DMRS). The PBCH carries the master information block (MIB) information. MIB information is transmitted through the PBCH. Synchronization signals in the SSB, such as the PSS and SSS, along with the PBCH and DMRS, ensure that terminal devices effectively receive MIB information in different propagation environments. MIB information is crucial broadcast information that ensures successful network access and use by terminal devices. It provides basic system configuration parameters and synchronization information, forming one of the foundations of network operation. Through MIB information, terminal devices can obtain basic system information and perform subsequent connection and communication operations.

[0039] Typically, the MIB information includes the control resource set (CORESET) and search space information of the physical downlink control channel (PDCCH). This PDCCH is in Type-0 format and is used to carry system information blocks (SIBs), such as SIB 1. The terminal device can determine the PDCCH based on the MIB information, and then obtain SIB1 on the corresponding physical downlink shared channel (PDSCH) based on the PDCCH.

[0040] In this context, CORESET can be understood as a set of resources used to transmit downlink control information (DCI), also known as a control resource area or a physical downlink control channel (PDCCH) resource set. PDCCH carries downlink control information (DCI) and is transmitted by network devices to terminal devices. Depending on the format of the DCI carried by the PDCCH, the DCI can indicate different control information to the terminal device, such as downlink scheduling information, uplink scheduling information, and timeslot format indication information. Currently, PDCCH resources are defined through CORESET and a search space. In some implementations, information such as the frequency band occupied by the PDCCH in the frequency domain and the number of symbols occupied by the PDCCH in the time domain can be encapsulated in the CORESET. Correspondingly, information such as the starting symbol number occupied by the PDCCH and the monitoring period of the PDCCH can be encapsulated in the search space.

[0041] In addition, MIB information may also include the following: system frame number (SFN), used to indicate the sequence number of the current system frame for frame synchronization; carrier frequency and bandwidth information, used to provide spectrum usage information to help terminal devices connect to the frequency resources currently used; subcarrier spacing (SCS) configuration, used to indicate the subcarrier spacing in the frequency domain, such as supporting different subcarrier spacings such as 15kHz, 30kHz, 60kHz, 120kHz, and 240kHz; SSB period information, used to help terminal devices perform synchronization signal detection within a specific time window; and parameters such as wireless port configuration and power control.

[0042] MIB information includes the basic configuration parameters required by the RAN. MIB information is the first step for terminal equipment to access the network. After receiving and decoding the MIB information, the terminal equipment can obtain the system information described above, thereby correctly accessing the network and communicating. SFN and other physical layer parameters in the MIB information can be used by the terminal equipment for time and frequency synchronization and for decoding other more detailed system information blocks, such as SIB1. SIB1 provides the key information required by the terminal equipment during initial access and normal operation, ensuring correct synchronization, selection of a suitable cell, random access, and acquisition of basic network configuration parameters. Through SIB1, the terminal equipment can communicate efficiently with network equipment, ensuring a stable and reliable connection. SIB1 includes key system information required for terminal equipment to access the network, such as Public Land Mobile Network (PLMN) information, cell selection information, time and frequency information, access parameters, power control information, cell broadcast information, public alarm information, and other information. Other information includes cell access restrictions, registration area information, etc. It is evident that MIB information is the foundation of system information broadcasting, enabling terminal devices to obtain the most critical system configuration and physical layer information in the initial stage.

[0043] MIB information can be encoded using, for example, 24 bits. These 24 bits carry information used by the terminal device for initial network access and configuration. These 24 bits include, for example, the SFN field, subcarrier spacing (subCarrierSpacingCommon) field, SSB subcarrier offset (ssb-SubcarrierOffset) field, PDCCH SIB1 configuration (pdcch-ConfigSIB1) field, CellBarred field, Intra-frequency Reselection field, DMSR position (dmrs-TypeA-Position) field, and Reserved Bits. The contents of the main fields in the MIB bit field can be seen in Table 1.

[0044] Table 1

[0045] The primary function of the `cellBarred` field in the MIB information is to control and manage cell access permissions. By setting this field, the network can effectively guide the behavior of terminal devices, optimize resource management, and perform cell-level maintenance or load control when necessary. This mechanism plays a crucial role in ensuring network stability and quality of service.

[0046] As shown in Table 1, the CellBarred field is used to indicate whether the cell blocks terminal devices from accessing it. For example, when the field is set to barred, it means that the cell is blocked from access; when the field is set to notbarred, it means that the cell is not blocked from access.

[0047] When a cell is blocked from access, all terminal devices receiving the MIB information will know that access to that cell is not permitted, thus avoiding attempts to connect to it. This is typically used for network maintenance, load control, or temporarily shutting down a cell. By broadcasting cell access blocking information, network devices can guide terminal devices to find other available cells. For terminal devices, if the current cell is blocked, they can automatically search for and attempt to connect to other unblocked cells. By explicitly informing terminal devices that a cell is blocked, the ineffective behavior of repeated attempts to access that cell can be reduced, thereby saving power and improving access efficiency.

[0048] During cell-level network maintenance or software upgrades, operators can temporarily set the CellBarred field to "barred" to prevent terminal devices from accessing the cell, ensuring the smooth progress of maintenance work. In some cases, a cell may be overloaded and require temporary blocking of new terminal device access. By setting the CellBarred field to "barred," network devices can guide newly arriving terminal devices to other cells with lower load. For certain emergency situations or disaster recovery periods, operators may temporarily shut down certain cells to manage resources or optimize network performance.

[0049] In 5G NR systems, the CellBarred field can typically be set and broadcast through the Network Management System (NMS) or other configuration tools. Operators can dynamically adjust the value of the CellBarred field based on real-time network conditions and needs to achieve flexible network management and optimization.

[0050] MIB information is periodically broadcast in the PBCH to ensure that all terminal devices can receive this critical system information in a timely manner. After a terminal device is powered on, it needs to access the network and be able to receive and send data. This process requires an initial access procedure. During the access procedure, the terminal device needs to scan the synchronization signal, decode the PBCH and SIB1, and perform cell search and selection.

[0051] After startup, the terminal device first scans different frequency bands to find synchronization signals such as PSS and SSS. It then decodes these synchronization signals to obtain the cell's physical layer identifier (PCI) and frame structure information, performing time and frequency synchronization. Based on the synchronization signal information, the terminal device determines the time and frequency resource location of the PBCH, receives and decodes the PBCH. After decoding the PBCH, it obtains the MIB information and extracts the SFN, SSB subcarrier spacing, higher-layer parameters, and other configuration information from the 24 bits in the MIB information. Decoding SIB1 allows the terminal device to obtain more detailed system information, such as cell configuration information and random access channel (RACH) configuration. Next, the terminal device performs a random access procedure (RACH) to obtain uplink synchronization and exchange its identifier with the network device. This identifier might include the cell-radio network temporary identifier (C-RNTI) provided by the network device and the terminal device's own identifier, such as the SAE-temporary mobile subscriber identity (S-TMSI) or international mobile subscriber identity (IMSI). The network device then sends an RRC connection establishment message to the terminal device, instructing it to enter the radio resource control (RRC) connection state. Through this initial access procedure, the terminal device successfully accesses the network and enables reliable data transmission.

[0052] In every mobile communication system, the standards implemented are constantly evolving and improving, resulting in new versions. This leads to situations where terminal devices using multiple protocol versions are operating simultaneously. Higher protocol versions of the wireless system are improvements over older versions. When a serving cell supports a higher protocol version, and a terminal device using a lower protocol version accesses that cell, problems may arise at certain stages of communication. For example, a higher protocol version might have improved or adjusted the Service Shield (SSB), and a terminal device using a lower protocol version might not be able to recognize or utilize the new SSB.

[0053] In carrier aggregation (CA) scenarios, in addition to the primary cell (PCell), the system also configures one or more secondary cells (SCells). These cells collectively provide users with higher data rates and better coverage. SCells may not transmit SSBs; such SCells are called SSB-less cells, provided they are co-located with a special cell (SPcell) or other secondary cells on the same frequency. If the terminal device is already synchronized with another cell, and that cell is co-located with an SSB-less cell, the terminal device can communicate on the SSB-less cell. Typically, the terminal device can perform synchronization and initial access on the SCell using SSBs transmitted on the PCell. When the terminal device completes synchronization and initial access on the SCell via SSBs on the PCell, the SCell can be configured and activated using RRC signaling or medium access control (MAC) control elements (CE), thus providing flexible CA and cell management. For example, SCells can be added, modified, or released via RRC connection reconfiguration; or SCells can be activated or deactivated via MAC CE. In this way, when spectrum resources are limited, unnecessary SSB transmissions can be reduced, thereby improving spectrum efficiency and reducing the power consumption of network and terminal devices, especially the power consumption of network devices.

[0054] Although SSB transmission is not required on SCells, it may be necessary in certain scenarios. For example, in some standalone deployments, SCells may need to transmit SSBs to support the synchronization and access of terminal devices; or, in some complex handover scenarios, transmitting SSBs on SCells can help terminal devices complete inter-cell handovers more smoothly.

[0055] SSBs can be periodic; network devices can periodically send SSBs to help terminal devices synchronize with network devices or the serving cell, or to perform cell measurements. However, for terminal devices, since it cannot be guaranteed that every SSB transmitted on the SCell will be effectively utilized, this can lead to wasted resources.

[0056] Therefore, higher protocol versions introduced on-demand SSB transmission, also known as on-demand SSB. On-demand SSBs are not sent continuously, but only for a specific period. For example, on-demand SSBs can include two scenarios: one where the network device sends an SSB for a period of time for terminal devices to detect it, and the network device can indicate this information to the terminal device via control signaling such as RRC signaling or MAC CE; the other scenario where the terminal device requests an SSB from the network device on demand, and the network device sends the SSB based on the terminal device's request. This reduces resource waste.

[0057] In older protocol versions, SSBs are sent periodically. When SSB parameters, such as the period, are modified, the network device notifies the terminal device via a broadcast signal. Terminal devices using older protocol versions do not support on-demand SSBs. Because on-demand SSBs require transmission over a period of time, when on-demand SSB transmission stops or transmission parameters, such as the transmission period, are modified, the terminal device using an older protocol version will perceive the SSB as continuously transmitting. Even if signaling indicates that the SSB transmission will terminate after a certain period, the terminal device using an older protocol version cannot recognize or interpret the information about the SSB transmission period. After the SSB transmission stops, the terminal device using an older protocol version may still use the SSB for incorrect operations, such as measurement and synchronization, which may cause problems in subsequent communication. Specifically, the following two scenarios may occur.

[0058] First, for terminal devices supporting lower protocol versions, if the terminal device's SCell is configured not to transmit SSBs, and the terminal device is in the RRC_CONNECTED state while the SCell is transmitting on-demand SSBs for other terminal devices supporting higher protocol versions, the terminal device supporting the lower protocol version will not detect the on-demand SSBs. In this case, when the terminal device receives the physical layer PDSCH and physical downlink shared channel (PUSCH), it cannot puncture the SSBs during rate matching, resulting in decoding errors.

[0059] Secondly, for terminal devices supporting lower protocol versions, if the terminal device's SCell is configured to support SSB transmission, when in the RRC_IDLE or RRC_INACTIVE state, if the terminal device attempts to search for SCell cells during periods without SSB transmission or when an SSB is not triggered, it will be unable to identify the cell because there is no available SSB to provide the necessary synchronization and system information. However, if the terminal device detects an on-demand SSB after it is triggered, it may identify the cell and initiate access. This is because after an on-demand SSB is triggered, the terminal device may access the cell based on the synchronization signal and system information in the on-demand SSB. Once the terminal device enters the RRC_CONNECTED state based on the on-demand SSB, and the network device stops transmitting the on-demand SSB, the terminal device may not be aware that the on-demand SSB has stopped, thus incorrectly using the on-demand SSB for measurement, leading to inaccurate measurement results. One possible solution is that once the terminal device enters the RRC_CONNECTED state, the network device can switch the terminal device to another cell before the on-demand SSB transmission stops, so as to ensure that the terminal device maintains its connection and continues to receive services, thus being unaffected by the lack of on-demand SSB.

[0060] However, when terminal devices supporting lower protocol versions access the network via on-demand SSB, the network devices switch the terminal devices to other cells before the on-demand SSB transmission ends, which also brings the following problems. First, when on-demand SSB transmission stops, the network devices need to schedule the terminal devices, release resources, and integrate uplink, downlink, and control resources among the terminal devices, increasing the scheduling burden on the network devices. Second, before on-demand SSB stops, the terminal devices accessing via on-demand SSB need to be able to switch to the correct cell, which increases the latency of on-demand SSB shutdown, and the cell handover process also introduces a certain latency. Finally, when the terminal device switches to a neighboring cell, measurement and reporting are required. During measurement, the terminal device's communication may be paused, affecting the user's communication quality. Furthermore, frequent measurement and handover will consume the terminal device's power, especially in NR systems, where the terminal device needs to scan in all directions, which is both time-consuming and energy-intensive.

[0061] In view of this, in the embodiments of this application, after the higher version protocol makes adjustments to the SSB relative to the lower version protocol, the cell access prohibited field in the MIB information is used to prohibit certain terminal devices from accessing the cell, and to allow the desired terminal devices to access the cell.

[0062] As shown in Table 1 above, the basic function of the CellBarred field in the MIB information is to control whether terminal devices are allowed to access the cell. Currently, this field can only globally allow or prohibit access for all terminal devices. This embodiment of the application can use the CellBarred field in conjunction with finer-grained control to restrict access for only certain terminal devices, i.e., only prohibit specific terminal devices, such as those supporting lower protocol versions.

[0063] When the MIB information in the SSB indicates that cell access is prohibited, terminal devices supporting lower protocol versions will not access the cell through that SSB. However, terminal devices supporting higher protocol versions can further determine whether to access the cell based on the relevant information in the MIB information, and will access the cell through that SSB if access is permitted. This achieves cell access control for terminal devices with different protocol versions. Therefore, when a terminal device supporting a lower protocol version detects an SSB sent to a terminal device supporting a higher protocol version, it will not use an SSB that does not belong to it for incorrect access and measurement, thus avoiding subsequent communication quality degradation or even connection interruption.

[0064] Figure 2 is a schematic flowchart of a communication method according to an embodiment of this application. The method 200 shown in Figure 2 can be executed by a terminal device and a network device. The terminal device is, for example, a terminal device that supports a predetermined protocol version, or a terminal device that supports on-demand SSB. The predetermined protocol version can be, for example, a higher protocol version, such as Release 19 or later in NR; correspondingly, the terminal device that supports a lower protocol version is, for example, a terminal device in Release 18 or earlier in NR.

[0065] As shown in Figure 2, method 200 includes some or all of the following steps.

[0066] In step 210, the network device sends an SSB to the terminal device.

[0067] Accordingly, in step 220, the terminal device receives the SSB sent by the network device.

[0068] The SSB includes MIB information, which is used to indicate that access to the cell is prohibited. Here, the field in the MIB information used to indicate that access to the cell is prohibited can be, for example, the cell access prohibited (cellBarred) field shown in Table 1 above.

[0069] In this embodiment of the application, for terminal devices that support lower protocol versions, if the MIB information in the SSB indicates that the cell is prohibited from access, they will not access the cell; for terminal devices that support higher protocol versions, if they receive the MIB information in the SSB indicating that the cell is prohibited from access, they may also access the cell through the SSB. That is, it is possible that the MIB information is used to indicate that the cell is prohibited from access and the SSB is used by the terminal device to access the cell.

[0070] For example, when the MIB information indicates that access to the cell is prohibited, other fields in the MIB information, or a combination of other fields in the MIB information, can be used to indicate whether a terminal device supporting a higher protocol version is allowed to access the cell. These fields in the MIB information can be fields that are typically not used by terminal devices when the cell indicates that access is prohibited, or fields that are used with a very low probability. These fields are used to indicate to terminal devices with higher protocol versions whether access to the cell is permitted.

[0071] The following describes in detail how a terminal device supporting a higher protocol version determines whether to access the cell via an SSB carrying the MIB information when the MIB information is used to indicate that access is prohibited by the cell. The terminal device referred to below is one that supports a higher protocol version.

[0072] Example 1

[0073] In some embodiments, the MIB information includes a first field, which indicates whether the SSB is a cell-defined SSB (CD SSB) or a non-cell-defined SSB (NCD SSB). The terminal device can determine whether to access the cell based on the first field.

[0074] The first field, for example, is the SSB subcarrier offset field (ssb-SubcarrierOffset) in the MIB information. The ssb-SubcarrierOffset field can be used to indicate whether the SSB is a CD SSB or an NCD SSB. As an example, a value of 0 to 14 in the ssb-SubcarrierOffset field indicates that the SSB is a CD SSB; a value of 15 in the SubcarrierOffset field indicates that the SSB is an NCD SSB.

[0075] CD SSB and NCD SSB are two types of SSBs in the NR system. One difference between CD SSB and NCD SSB lies in whether they are used to acquire system information, such as SIB1. CD SSB is typically used to acquire system information. The PBCH of a CD SSB includes MIB information, which carries the CORESET and search space information of the PDCCH used to acquire SIB1. Therefore, terminal devices can acquire SIB1 based on CD SSB. However, the MIB information in the PBCH of an NCD SSB does not carry the PDCCH information carrying SIB1, so terminal devices cannot acquire system information through NCD SSB. The main function of NCD SSB is interference cancellation and robustness enhancement. For example, the strength of interference signals can be obtained by measuring PSS and SSS. NCD SSB can also provide timing and synchronization references so that terminal devices can correctly receive and demodulate signals from network devices. NCD SSB is not used to transmit system information. CD SSBs need to be transmitted on a sync raster, while NCD SSBs do not. In other words, NCD SSBs can be transmitted on or off a sync raster.

[0076] Here, the terminal device can determine whether to access the cell based on the first field using the following three methods. These are described in detail below.

[0077] Example 1-1

[0078] In some embodiments, whether to access a cell can be determined based on whether the SSB is a CD SSB or an NCD SSB, indicated by a first field. For example, if the first field indicates that the SSB is an NCD SSB, the terminal device does not access the cell; if the first field indicates that the SSB is a CD SSB, the terminal device accesses the cell.

[0079] Typically, when the cellBarred field in the MIB information indicates that cell access is prohibited (i.e., the cellBarred field is set to barred), the MIB information may not carry SIB1 information because the terminal device is not allowed to access the cell. This is equivalent to the SSB being an NCD SSB. In other words, it is unlikely that the cellBarred field will be set to barred and the SSB will be a CD SSB. Therefore, this embodiment considers utilizing this situation to indicate to terminal devices with higher protocol versions whether they are allowed to access the cell. Specifically, for lower version terminal devices or terminal devices already connected to the cell, if the cellBarred field in the MIB information is set to barred, it will be assumed that the MIB information does not carry SIB1, and access to the cell via the SSB will not be permitted. For higher version terminal devices, if the cellBarred field is set to barred, access to the cell can be determined based on a first field. For example, if the first information indicates that the SSB is a CD SSB, access to the cell is permitted; if the first information indicates that the SSB is an NCD SSB, access to the cell is prohibited.

[0080] For example, the first field is the ssb-SubcarrierOffset field in the MIB information. When the cellBarred field is set to barred, the terminal device determines whether to allow cell access based on the ssb-SubcarrierOffset field. Specifically, a value between 0 and 14 indicates that the SSB is a CD SSB, in which case the terminal device is allowed to access the cell; a value of 15 indicates that the SSB is an NCD SSB, in which case the terminal device is prohibited from accessing the cell.

[0081] Examples 1-2

[0082] In some embodiments, the terminal device may determine whether to access the cell based on the value of the first field. For example, if the value of the first field is a preset value, or if the value of the first field is within a preset range, the terminal device may access the cell; otherwise, the terminal device may not access the cell.

[0083] The first field can be the ssb-SubcarrierOffset field in the MIB information. In this case, the preset value or preset range is, for example, a portion of the values ​​in the ssb-SubcarrierOffset field that correspond to the CD SSB. This preset value and preset range can be agreed upon by the protocol or sent by the network device.

[0084] As an example, considering that the value of the ssb-SubcarrierOffset field ranges from 0 to 15, and that a value of 15 indicates that the SSB is an NCD SSB, the values ​​from 0 to 14 can be divided into two parts to indicate whether access is allowed or denied. For instance, if the value of the ssb-SubcarrierOffset field in the MIB information received by the terminal device from the SSB is between 0 and 13, it indicates that access to the cell is allowed, and the terminal device can access the cell; if the value of the ssb-SubcarrierOffset field is equal to 14, it indicates that access to the cell is denied, and the terminal device will not access the cell.

[0085] Examples 1-3

[0086] In some embodiments, the terminal device determines whether to access the cell based on the first field and other fields. For example, if the first field indicates that the SSB is NCD SSB, the terminal device does not access the cell; if the first field indicates that the SSB is CD SSB, the terminal device further determines whether to access the cell based on other fields in the MIB information.

[0087] For example, the MIB information also includes a second field. When the first field indicates that the SSB is a CD SSB, the second field indicates whether the terminal device can access the cell. Specifically, if the second field indicates that the terminal device is allowed to access the cell, the terminal device can access the cell via the SSB; if the second field indicates that the terminal device is prohibited from accessing the cell, the terminal device cannot access the cell.

[0088] Details regarding the second field will be described later.

[0089] Example 2

[0090] In Embodiment 2, the terminal device can determine whether to access the cell via the SSB based on whether the SSB is transmitted on a synchronization grid. For example, if the SSB is transmitted on an asynchronous grid, the terminal device does not access the cell; if the SSB is transmitted on a synchronization grid, the terminal device accesses the cell via the SSB.

[0091] In some embodiments, when the SSB is transmitted in an out-of-synchronization grid, the terminal device does not access the cell; when the SSB is transmitted in a synchronous grid, the terminal device continues to determine whether it can access the cell based on the first field in the MIB information. For example, if the SSB is transmitted in a synchronous grid and the first field indicates that the SSB is an NCD SSB, the terminal device does not access the cell; if the first field indicates that the SSB is a CD SSB, the terminal device accesses the cell. As another example, when the SSB is transmitted in a synchronous grid, the terminal device determines whether to access the cell based on the value of the first field. If the value of the first field is a preset value or within a preset range, the terminal device can access the cell; otherwise, the terminal device does not access the cell. Here, the specific process of how the terminal device determines whether to access the cell based on the first field when the SSB is transmitted in a synchronous grid can be referred to the relevant description of the first field in the aforementioned Embodiment 1, and will not be detailed here.

[0092] Furthermore, in Embodiments 1 and 2 above, when the SSB is an NCD SSB or the SSB is transmitted over an asynchronous grid, it indicates that the cell prohibits access for the terminal device. In other embodiments, when the SSB is a CD SSB or the SSB is transmitted over a synchronous grid, the terminal device can further determine whether the cell allows the terminal device to access by combining the second field in the MIB information.

[0093] Below are several possible implementations of the second field.

[0094] In some embodiments, the second field includes other fields in the MIB information besides the Intra-frequency Reselection field, such as one or more of the following fields: SFN field, subcarrierSpacingCommon field, SSB-SubcarrierOffset field, PDCCH SIB1 configuration field, CellBarred field, Intra-frequency Reselection field, DMSR position field, and Reserved Bits.

[0095] It is understandable that when the cellbarred field is set to barred, the terminal device can determine whether to access the cell based on any one of the fields in the MIB information other than the Intra-frequency Reselection field, or it can determine whether to access the cell by combining multiple fields.

[0096] As shown in Table 1 above, the Intra-frequency Reselection field can be used to indicate whether the terminal device is allowed to perform intra-frequency reselection. For example, if the cellbarred field is set to barred, setting the Intra-frequency Reselection field to allowed means that the terminal device is allowed to perform intra-frequency reselection; setting the Intra-frequency Reselection field to not allowed means that the terminal device is not allowed to perform intra-frequency reselection.

[0097] Typically, when the cellBarred field in the MIB information indicates that cell access is prohibited (i.e., the cellBarred field is set to barred), terminal devices with lower protocol versions or those already connected to the cell can determine whether intra-frequency reselection is possible based on the Intra-frequency Reselection field in the MIB information. Other fields in the MIB information besides the Intra-frequency Reselection field are useless to these terminal devices. Therefore, this embodiment considers using other fields besides the Intra-frequency Reselection field, such as a second field, when cell access is prohibited to indicate to terminal devices with higher protocol versions whether cell access is permitted.

[0098] As an example, in some embodiments, the second field includes the pdcch-ConfigSIB1 field from the MIB information, which indicates whether access by the terminal device is allowed.

[0099] As shown in Table 1 above, the pdcch-ConfigSIB1 field can be used to indicate a predetermined resource configuration, such as the bandwidth of PDCCH / SIB1, CORESET information, search space, and necessary PDCCH parameters. Here, the pdcch-ConfigSIB1 field can be reused to indicate whether a terminal device is allowed to access the cell. For example, if the pdcch-ConfigSIB1 field indicates a predetermined resource configuration, it means that the terminal device is allowed to access the cell. This predetermined resource configuration can be agreed upon by the protocol or sent by the network device.

[0100] As an example, in some embodiments, the second field includes a reserved field from the MIB information, which indicates whether access by the terminal device is permitted. This reduces the impact on the functionality of other fields.

[0101] For example, a reserved field value of 1 indicates that terminal device access is allowed, and a reserved field value of 0 indicates that terminal device access is prohibited; or, a reserved field value of 0 indicates that terminal device access is allowed, and a reserved field value of 1 indicates that terminal device access is prohibited.

[0102] Example 3

[0103] When the cellbarred field is set to barred, terminal device access can be determined not by the fields in the MIB information, but by the information associated with the MIB information.

[0104] For example, MIB information is also used to obtain SIB1, which is used to indicate whether a terminal device is allowed to access the cell. In other words, SIB1 information is used to indicate whether a terminal device is allowed to access the cell.

[0105] The method embodiments of this application have been described in detail above with reference to FIG2. The apparatus embodiments of this application will be described in detail below with reference to FIGS. 3 to 5. It should be understood that the descriptions of the method embodiments correspond to the descriptions of the apparatus embodiments. Therefore, any parts not described in detail can be referred to the foregoing method embodiments.

[0106] Figure 3 is a schematic diagram of a terminal device according to an embodiment of this application. The terminal device 300 shown in Figure 3 may include a receiving unit 310. The receiving unit 310 is used to receive an SSB sent by a network device. The SSB includes MIB information, which is used to indicate that access to the cell is prohibited. The SSB is used by the terminal device to access the cell.

[0107] In some embodiments, the MIB information includes a first field, which indicates that the SSB is a cell-defined SSB.

[0108] In some embodiments, the first field is the SSB subcarrier bias field in the MIB information, and the value of the first field is a preset value, or the value of the first field is within a preset range.

[0109] In some embodiments, the SSB is transmitted on a synchronization grid.

[0110] In some embodiments, the MIB information includes an SSB subcarrier bias field, which is used to indicate that the terminal device accesses the cell.

[0111] In some embodiments, the MIB information includes a second field, which is used to indicate that the terminal device accesses the cell.

[0112] In some embodiments, the second field is any field in the MIB information other than the inter-frequency reselection field.

[0113] In some embodiments, the fields in the MIB information other than the inter-frequency reselection field include one or more of the following fields: SFN field; PDCCH SIB1 configuration field; subcarrier spacing field; DMSR location field; reserved field.

[0114] In some embodiments, the second field is the PDCCH SIB1 configuration field in the MIB information, which indicates a predetermined resource configuration.

[0115] In some embodiments, the second field is a reserved field in the MIB information, and the reserved field indicates a preset value.

[0116] In some embodiments, the MIB information is further used to obtain SIB1, which is used to indicate that the terminal device accesses the cell.

[0117] In some embodiments, the terminal device is a terminal device that supports a predetermined protocol version and / or supports on-demand SSB.

[0118] In some embodiments, the predetermined protocol version is Release 19 of the new wireless NR communication protocol.

[0119] It is understood that the receiving unit 310 may be, for example, a transceiver 530. Additionally, the terminal device 300 may optionally include a processor 510 and a memory 520, as detailed in Figure 5.

[0120] Figure 4 is a schematic diagram of a network device according to an embodiment of this application. The network device 400 shown in Figure 4 includes a sending unit 410. The sending unit 410 is used to send an SSB to a terminal device. The SSB includes MIB information, which is used to indicate that access to the cell is prohibited. The SSB is used by the terminal device to access the cell.

[0121] In some embodiments, the MIB information includes a first field, which indicates that the SSB is a cell-defined SSB.

[0122] In some embodiments, the first field is the SSB subcarrier bias field in the MIB information, and the value of the first field is a preset value, or the value of the first field is within a preset range.

[0123] In some embodiments, the SSB is transmitted on a synchronization grid.

[0124] In some embodiments, the MIB information includes an SSB subcarrier bias field, which is used to indicate that the terminal device accesses the cell.

[0125] In some embodiments, the MIB information includes a second field, which is used to indicate that the terminal device accesses the cell.

[0126] In some embodiments, the second field is any field in the MIB information other than the inter-frequency reselection field.

[0127] In some embodiments, the fields in the MIB information other than the inter-frequency reselection field include one or more of the following fields: SFN field; PDCCH SIB1 configuration field; subcarrier spacing field; DMSR location field; reserved field.

[0128] In some embodiments, the second field is the PDCCH SIB1 configuration field in the MIB information, which indicates a predetermined resource configuration.

[0129] In some embodiments, the second field is a reserved field in the MIB information, and the reserved field indicates a preset value.

[0130] In some embodiments, the MIB information is further used to obtain SIB1, which is used to indicate that the terminal device accesses the cell.

[0131] In some embodiments, the terminal device is a terminal device that supports a predetermined protocol version and / or supports on-demand SSB.

[0132] In some embodiments, the predetermined protocol version is Release 19 of the new wireless NR communication protocol.

[0133] It is understood that the transmitting unit 410 may be, for example, a transceiver 530. Additionally, the network device 400 may optionally include a processor 510 and a memory 520, as detailed in Figure 5.

[0134] Figure 5 is a schematic structural diagram of a communication apparatus according to an embodiment of this application. The dashed lines in Figure 5 indicate that the unit or module is optional. This apparatus can be used to implement the methods described in the above method embodiments. The apparatus may be, for example, a chip, a terminal device, or a network device.

[0135] As shown in Figure 5, the device 500 may include one or more processors 510. The processors 510 can support the device 500 in implementing the methods described in the above-described method embodiments. The processor 510 may be a general-purpose processor or a special-purpose processor. For example, the processor 510 may be a central processing unit (CPU). Alternatively, the processor 510 may also be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor.

[0136] The apparatus 500 may also include one or more memories 520. The memories 520 store a program that can be executed by the processor 510, causing the processor 510 to perform the methods described in the preceding method embodiments. The memories 520 may be independent of the processor 510 or integrated within the processor 510.

[0137] The device 500 may also include a transceiver 530. The processor 510 can communicate with other devices or chips via the transceiver 530. For example, the processor 510 can send and receive data with other devices or chips via the transceiver 530.

[0138] This application provides a communication system. The system includes the aforementioned terminal device and / or network device. In some implementations, the system further includes other devices that interact with the terminal device and / or network device.

[0139] This application also provides a computer-readable storage medium for storing a program. This computer-readable storage medium can be applied to a terminal device or network device provided in this application, and the program causes a computer to execute the methods performed by the terminal device or network device in various embodiments of this application.

[0140] This application also provides a computer program product. The computer program product includes a program. This computer program product can be applied to a terminal device or network device provided in this application embodiment, and the program causes a computer to execute the methods performed by the terminal device or network device in the various embodiments of this application.

[0141] This application also provides a computer program. This computer program can be applied to the terminal or network device provided in this application, and the computer program causes the computer to execute the methods performed by the terminal device or network device in various embodiments of this application.

[0142] It should be understood that the terms "system" and "network" in this application can be used interchangeably. Furthermore, the terminology used in this application is only for explaining specific embodiments of the application and is not intended to limit the application. The terms "first," "second," "third," and "fourth," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish different objects, not to describe a specific order. In addition, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion.

[0143] In the embodiments of this application, the term "instruction" can be a direct instruction, an indirect instruction, or an indication of a relationship. For example, A instructing B can mean that A directly instructs B, such as B being able to obtain information through A; it can also mean that A indirectly instructs B, such as A instructing C, so B can obtain information through C; or it can mean that there is a relationship between A and B.

[0144] In the embodiments of this application, "B corresponding to A" means that B is associated with A, and B can be determined based on A. However, it should be understood that determining B based on A does not mean that B is determined solely based on A; B can also be determined based on A and / or other information.

[0145] In the embodiments of this application, the term "correspondence" can indicate a direct or indirect correspondence between two things, or an association between two things, or a relationship of instruction and being instructed, configuration and being configured, etc.

[0146] In this application embodiment, "predefined" or "preconfigured" can be implemented by pre-storing corresponding codes, tables, or other means that can be used to indicate relevant information in the device, including terminal devices and network devices. This application does not limit the specific implementation method. For example, predefined can refer to what is defined in the protocol.

[0147] In the embodiments of this application, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship.

[0148] In the embodiments of this application, "comprising" can refer to direct inclusion or indirect inclusion. Optionally, "comprising" mentioned in the embodiments of this application can be replaced with "indicating" or "used to determine". For example, "A includes B" can be replaced with "A indicates B" or "A is used to determine B".

[0149] In the various embodiments of this application, the order of the above-mentioned processes 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.

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

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

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

[0153] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave) means. The computer-readable storage medium can be any available medium that a computer can read or a data storage device such as a server or data center that integrates one or more available media. The available media can be magnetic media such as floppy disks, hard disks, magnetic tapes, etc., or optical media such as digital video discs (DVDs) or semiconductor media such as solid-state disks (SSDs).

[0154] 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

A communication method, characterized in that, The method includes: The terminal device receives a synchronization signal broadcast channel block (SSB) sent by the network device. The SSB includes master information block (MIB) information, which is used to indicate that access to the cell is prohibited. The SSB is used by the terminal device to access the cell. The method according to claim 1, characterized in that, The MIB information includes a first field, which indicates that the SSB is a cell-defined SSB. The method according to claim 2, characterized in that, The first field is the SSB subcarrier bias field in the MIB information, and the value of the first field is a preset value or the value of the first field is within a preset range. The method according to claim 1, characterized in that, The SSB is transmitted on the synchronization grid. The method according to claim 4, characterized in that, The MIB information includes an SSB subcarrier offset field, which is used to indicate that the terminal device accesses the cell. The method according to any one of claims 2 to 4, characterized in that, The MIB information includes a second field, which is used to indicate that the terminal device accesses the cell. The method according to claim 6, characterized in that, The second field is any field in the MIB information other than the inter-frequency reselection field. The method according to claim 7, characterized in that, The fields in the MIB information other than the inter-frequency reselection field include one or more of the following fields: System frame number field; Physical Downlink Control Channel (PDCCH) System Information Block SIB1 Configuration Field; Subcarrier spacing field; DMSR location field; Reserved fields. The method according to any one of claims 6 to 8, characterized in that, The second field is the PDCCH SIB1 configuration field in the MIB information, which indicates the predetermined resource configuration. The method according to any one of claims 6 to 8, characterized in that, The second field is a reserved field in the MIB information, and the reserved field indicates a preset value. The method according to any one of claims 1 to 10, characterized in that, The MIB information is also used to obtain SIB1, which is used to indicate that the terminal device accesses the cell. The method according to any one of claims 1 to 11, characterized in that, The terminal device is a terminal device that supports a predetermined protocol version and / or supports on-demand SSB. The method according to claim 12, characterized in that, The predetermined protocol version is Release 19 of the new wireless NR communication protocol. A communication method, characterized in that, The method includes: The network device sends a synchronization signal broadcast channel block (SSB) to the terminal device. The SSB includes master information block (MIB) information, which is used to indicate that access to the cell is prohibited. The SSB is used by the terminal device to access the cell. The method according to claim 14, characterized in that, The MIB information includes a first field, which indicates that the SSB is a cell-defined SSB. The method according to claim 15, characterized in that, The first field is the SSB subcarrier bias field in the MIB information, and the value of the first field is a preset value or the value of the first field is within a preset range. The method according to claim 14, characterized in that, The SSB is transmitted on the synchronization grid. The method according to claim 17, characterized in that, The MIB information includes an SSB subcarrier offset field, which is used to indicate that the terminal device accesses the cell. The method according to any one of claims 15 to 17, characterized in that, The MIB information includes a second field, which is used to indicate that the terminal device accesses the cell. The method according to claim 19, characterized in that, The second field is any field in the MIB information other than the inter-frequency reselection field. The method according to claim 20, characterized in that, The fields in the MIB information other than the inter-frequency reselection field include one or more of the following fields: System frame number field; Physical Downlink Control Channel (PDCCH) System Information Block SIB1 Configuration Field; Subcarrier spacing field; DMSR location field; Reserved fields. The method according to any one of claims 19 to 21 is characterized in that, The second field is the PDCCH SIB1 configuration field in the MIB information, which indicates the predetermined resource configuration. The method according to any one of claims 19 to 21 is characterized in that, The second field is a reserved field in the MIB information, and the reserved field indicates a preset value. The method according to any one of claims 19 to 23 is characterized in that, The MIB information is also used to obtain SIB1, which is used to indicate that the terminal device accesses the cell. The method according to any one of claims 19 to 24, characterized in that, The terminal device is a terminal device that supports a predetermined protocol version and / or supports on-demand SSB. The method according to claim 25, characterized in that, The predetermined protocol version is Release 19 of the new wireless NR communication protocol. A communication method, characterized in that, The method includes: The terminal device receives a synchronization signal broadcast channel block (SSB) sent by the network device. The SSB includes master information block (MIB) information, which is used to indicate that access to the cell is prohibited. The SSB is used by the terminal device to access the cell. The method according to claim 27, characterized in that, The MIB information includes a first field, which indicates that the SSB is a cell-defined SSB. The method according to claim 28, characterized in that, The first field is the SSB subcarrier bias field in the MIB information, and the value of the first field is a preset value or the value of the first field is within a preset range. The method according to claim 27, characterized in that, The SSB is transmitted on the synchronization grid. The method according to claim 30, characterized in that, The MIB information includes an SSB subcarrier offset field, which is used to indicate that the terminal device accesses the cell. The method according to any one of claims 28 to 30, characterized in that, The MIB information includes a second field, which is used to indicate that the terminal device accesses the cell. The method according to claim 32, characterized in that, The second field is any field in the MIB information other than the inter-frequency reselection field. The method according to claim 33 is characterized in that, In addition to the frequency reselection field, the MIB information also includes Other fields, including one or more of the following fields: System frame number field; Physical Downlink Control Channel (PDCCH) System Information Block SIB1 Configuration Field; Subcarrier spacing field; DMSR location field; Reserved fields. The method according to any one of claims 32 to 34, characterized in that, The second field is the PDCCH SIB1 configuration field in the MIB information, which indicates the predetermined resource configuration. The method according to any one of claims 32 to 34, characterized in that, The second field is a reserved field in the MIB information, and the reserved field indicates a preset value. The method according to any one of claims 27 to 36, characterized in that, The MIB information is also used to obtain SIB1, which is used to indicate that the terminal device accesses the cell. The method according to any one of claims 27 to 37, characterized in that, The terminal device is a terminal device that supports a predetermined protocol version and / or supports on-demand SSB. The method according to claim 38, characterized in that, The predetermined protocol version is Release 19 of the new wireless NR communication protocol. A communication method, characterized in that, The method includes: The network device sends a synchronization signal broadcast channel block (SSB) to the terminal device. The SSB includes master information block (MIB) information, which is used to indicate that access to the cell is prohibited. The SSB is used by the terminal device to access the cell. The method according to claim 40, characterized in that, The MIB information includes a first field, which indicates that the SSB is a cell-defined SSB. The method according to claim 41, characterized in that, The first field is the SSB subcarrier bias field in the MIB information, and the value of the first field is a preset value or the value of the first field is within a preset range. The method according to claim 40, characterized in that, The SSB is transmitted on the synchronization grid. The method according to claim 43, characterized in that, The MIB information includes an SSB subcarrier offset field, which is used to indicate that the terminal device accesses the cell. The method according to any one of claims 41 to 43 is characterized in that, The MIB information includes a second field, which is used to indicate that the terminal device accesses the cell. The method according to claim 45, characterized in that, The second field is any field in the MIB information other than the inter-frequency reselection field. The method according to claim 46, characterized in that, The fields in the MIB information other than the inter-frequency reselection field include one or more of the following fields: System frame number field; Physical Downlink Control Channel (PDCCH) System Information Block SIB1 Configuration Field; Subcarrier spacing field; DMSR location field; Reserved fields. The method according to any one of claims 45 to 47, characterized in that, The second field is the PDCCH SIB1 configuration field in the MIB information, which indicates the predetermined resource configuration. The method according to any one of claims 45 to 48, characterized in that, The second field is a reserved field in the MIB information, and the reserved field indicates a preset value. The method according to any one of claims 45 to 49, characterized in that, The MIB information is also used to obtain SIB1, which is used to indicate that the terminal device accesses the cell. The method according to any one of claims 45 to 50, characterized in that, The terminal device is a terminal device that supports a predetermined protocol version and / or supports on-demand SSB. The method according to claim 51, characterized in that, The predetermined protocol version is Release 19 of the new wireless NR communication protocol. A terminal device, characterized in that, The device includes a transceiver, a memory, and a processor. The memory stores a program, and the processor invokes the program in the memory and controls the transceiver to receive or send signals so that the terminal device performs the method according to any one of claims 1 to 13. A network device, characterized in that, The device includes a transceiver, a memory, and a processor. The memory stores a program, and the processor invokes the program in the memory and controls the transceiver to receive or transmit signals so that the wireless access device performs the method according to any one of claims 14 to 26. An apparatus characterized in that, Includes a processor for calling a program from memory to cause the apparatus to perform the method according to any one of claims 1 to 13, or the method according to any one of claims 14 to 26. A chip characterized in that, Includes a processor for calling a program from memory to cause the chip to perform the method according to any one of claims 1 to 13, or the method according to any one of claims 14 to 26. A computer-readable storage medium, characterized in that, It contains a program that causes a computer to perform the method according to any one of claims 1 to 13, or the method according to any one of claims 14 to 26. A computer program product, characterized in that, Includes a program that causes a computer to perform the method according to any one of claims 1 to 13, or the method according to any one of claims 14 to 26. A computer program, characterized in that, The computer program causes the computer to perform the method according to any one of claims 1 to 13, or the method according to any one of claims 14 to 26.

Images