Communication method and related apparatus

Abstract

The present application provides a communication method and a related apparatus. A network device configures and sends information, the information indicating that a first cell supports or does not support requesting a system information block (SIB1). When a terminal device has a capability of requesting SIB1 and the information indicates that the first cell supports requesting SIB1, the terminal device accesses the first cell. The terminal device accesses the first cell on the basis of the received information and its own capability of requesting SIB1. Therefore, a terminal device that does not have the capability of requesting SIB1 is prevented from attempting to acquire SIB1 multiple times, saving the energy consumption of the terminal device that does not have the capability of requesting SIB1.

Description

Communication methods and related devices

[0001] This application claims priority to Chinese Patent Application No. 2024119979347, filed with the Chinese Patent Office on December 31, 2024, entitled "Communication Method and Related Apparatus", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of mobile communication technology, and in particular to a communication method and related apparatus. Background Technology

[0003] With the development of mobile communications, how to achieve network energy savings (NES) is an issue that needs to be considered.

[0004] To achieve network energy conservation, the on-demand (OD) system information block (SIB) 1 was proposed. On-demand SIB 1 can be understood as network devices no longer broadcasting SIB 1; terminal devices request SIB 1 from network devices only when needed, thereby reducing the energy consumption of network devices. Because NES cells no longer broadcast SIB 1, some information, such as synchronization signals and physical broadcast channel blocks (SSBs), no longer indicate available SIB 1 Physical Downlink Control Channel (PDCCH) resources.

[0005] Some terminal devices lack the ability to request SIB1, and because NES cells do not indicate the availability of valid SIB1 PDCCH resources, these terminal devices cannot access NES cells due to their inability to obtain SIB1. Consequently, they will repeatedly attempt to receive SIB1 in NES cells, resulting in high power consumption for these terminal devices. Summary of the Invention

[0006] This application provides a communication method to solve the problem of excessive power consumption caused by repeated attempts to receive SIB1 by terminal devices that do not have the ability to request SIB1. The disclosed technical solution is as follows:

[0007] The first aspect of this application provides a communication method, which can be executed by a network device, or by a component (such as a circuit, chip, or chip system) configured in the network device, or by a logic module or software capable of implementing all or part of the functions of the network device. This application does not limit the scope of the method. The following description uses a network device as an example.

[0008] Network device configuration information, the information indicating whether the first cell supports or does not support requesting system information block SIB1, and the network device sends the information.

[0009] Because the network device configures and sends information indicating whether the first cell supports or does not support requesting SIB1, it lays the foundation for the terminal device to determine whether to access the first cell based on its own capabilities and whether the first cell supports or does not support requesting SIB1. If the terminal does not have the ability to request SIB1 and the first cell does not support requesting SIB1, the terminal device will not access the first cell. Therefore, it can avoid terminal devices that do not have the ability to request SIB1 from repeatedly trying to obtain SIB1 in the first cell, thereby reducing the power consumption of terminal devices that do not have the ability to request SIB1.

[0010] In some implementations, the information includes: first information and SIB1 request configuration information; the information indicates whether the first cell supports or does not support requesting System Information Block SIB1, including: the first information indicating the information of the first cell, the SIB1 request configuration information indicating the information of the cell supporting requesting SIB1, the information of the first cell being included in the information of the cell supporting requesting SIB1 indicating that the first cell supports requesting SIB1, and the information of the first cell not being included in the information of the cell supporting requesting SIB1 indicating that the first cell does not support requesting SIB1, so that the terminal device can determine whether the first cell supports requesting SIB1 based on the received information.

[0011] In some implementations, the information includes: first information and second information; the information indicates whether the first cell supports or does not support requesting System Information Block (SIB1), including: the first information indicating the information of the first cell, and the second information including the Master Information Block (MIB) or Physical Broadcast Channel (PBCH) payload, whereby the MIB or PBCH payload indicates whether the first cell supports or does not support requesting SIB1. In this implementation, the first cell directly indicates whether it supports or does not support requesting SIB1 based on the MIB or PBCH payload, eliminating the need for the terminal device to determine whether the first cell supports or does not support requesting SIB1. Therefore, this not only avoids terminal devices lacking the ability to request SIB1 repeatedly attempting to acquire resources for transmitting SIB1 in the first cell, thereby reducing the energy consumption of terminal devices lacking the ability to request SIB1, but also reduces the energy consumption of the terminal device receiving the information.

[0012] In some implementations, the information includes: first information and second information; the information indicates whether the first cell supports or does not support the requested System Information Block (SIB1), including: the first information indicating information about the first cell; the second information including the MIB and PBCH loads, the MIB and PBCH loads indicating k SSB The value; or, the second information includes the MIB, which indicates k. SSB The value of k; SSB The value of k is the first value, indicating that the first cell supports the request for SIB1,k SSB The value of the second value indicates that the first cell does not support requesting SIB1. This is indicated by the MIB, or by the load of the MIB and PBCH. SSB The value of MIB and PBCH lays the foundation for terminal devices to determine whether to access the first cell. Furthermore, the MIB and PBCH payloads are information broadcast by the cell in the existing protocol, so this approach is conducive to compatibility with the existing protocol and is easy to implement.

[0013] The second aspect of this application provides a communication method that can be executed by a network device, or by a component (such as a circuit, chip, or chip system) configured in the network device, or by a logic module or software capable of implementing all or part of the functions of the network device. This application does not limit the scope of this method. The following description uses a network device as an example.

[0014] The network device configuration information indicates that terminal devices or target terminal devices that do not have the capability to request SIB1 are prohibited from accessing the first cell. Target terminal devices include terminal devices that have the capability to request SIB1 and terminal devices that do not have the capability to request SIB1. The network device sends the information.

[0015] The network device configures and sends information indicating that terminal devices or target terminal devices that do not have the ability to request SIB1 are prohibited from accessing the first cell. This allows terminal devices to determine whether to access the first cell based on the information and their own ability to request SIB1. If the terminal does not have the ability to request SIB1 and the first cell does not support requesting SIB1, the terminal device will not access the first cell. Therefore, it can avoid terminal devices that do not have the ability to request SIB1 from repeatedly trying to obtain resources for transmitting SIB1 in the first cell, thereby reducing the energy consumption of terminal devices that do not have the ability to request SIB1.

[0016] In some implementations, the information includes first information and second information; the information indicates that terminal devices or target terminal devices that do not have the capability to request SIB1 are prohibited from accessing the first cell, including: the first information indicating information about the first cell; the second information including a first field and a second field, where the first field indicates prohibition and the second field has a third value, indicating that terminal devices that do not have the capability to request SIB1 are prohibited from accessing the first cell; or, the first field indicates prohibition and the second field has a fourth value, indicating that target terminal devices are prohibited from accessing the first cell. Using two fields to jointly indicate prohibition of terminal devices or target terminal devices that do not have the capability to request SIB1 from accessing the first cell provides greater flexibility.

[0017] In some implementations, the second information includes the MIB; or, the second information includes both the MIB and the third information, with the first field contained in the MIB and the second field contained in the third information. In other words, the two fields can be contained in the same information or in different information, further increasing flexibility.

[0018] In some implementations, the third piece of information includes the PBCH payload.

[0019] In some implementations, the information includes: first information and second information; the information indicates that the target terminal device is prohibited from accessing the first cell, including: the first information indicates information about the first cell, and the second information includes the MIB, the MIB indicating that the target terminal device is prohibited from accessing the first cell.

[0020] In some implementations, the information includes: first information and second information; the information indicating that the target terminal device is prohibited from accessing the first cell includes: the first information indicating information about the first cell, and the second information including an indication k SSB The value of the MIB and PBCH load, or, the second information includes an indication of the k SSB The value of the MIB; the MIB indicates that it is disabled, and k SSB The value is the first value, indicating that the target terminal device is prohibited from accessing the first cell. Prohibiting the target terminal from accessing the first cell is convenient in certain situations, such as when the first cell is only used for testing, to prevent the terminal device from accessing the first cell and being unable to communicate normally.

[0021] A third aspect of this application provides a communication method that can be executed by a terminal device, or by a component (such as a circuit, chip, or chip system) configured in the terminal device, or by a logic module or software capable of implementing all or part of the functions of the terminal device. This application does not limit the scope of the method. The following description uses a terminal device as an example.

[0022] The terminal device receives information indicating whether the first cell supports or does not support requesting System Information Block (SIB1). If the terminal device has the capability to request SIB1 and the information indicates that the first cell supports SIB1, the terminal device accesses the first cell. Because the terminal device accesses the first cell based on the received information and its own capability to request SIB1, terminal devices without the capability to request SIB1 are prevented from accessing the first cell that supports SIB1, thus avoiding multiple attempts by terminal devices without this capability to acquire SIB1 transmission resources and saving energy for them.

[0023] In some implementations, the information includes first information and SIB1 request configuration information. The first information indicates information about a first cell, and the SIB1 request configuration information indicates information about cells that support SIB1 requests. The information indicating that the first cell supports SIB1 requests includes: the information about the first cell being included in the information about cells that support SIB1 requests. Since the information about the first cell is included in the information about cells that support SIB1 requests, it indicates that the first cell supports SIB1 requests. The terminal device then determines whether to access the first cell based on its own capabilities. If it does not have the capability to request SIB1, it will not access the first cell, thus saving energy.

[0024] In some implementations, the information includes: first information and second information; the information indicates whether the first cell supports or does not support requesting System Information Block (SIB1), including: the first information indicating the information of the first cell, and the second information including MIB or PBCH payload, the MIB or PBCH payload indicating whether the first cell supports or does not support requesting SIB1. Based on the information indicating whether the first cell supports or does not support requesting SIB1, the terminal device does not need to further determine whether the first cell supports requesting SIB1, thus further saving the terminal device's energy consumption.

[0025] In some implementations, the information includes: first information and second information; the information indicates whether the first cell supports or does not support the requested System Information Block (SIB1), including: the first information indicating information about the first cell; the second information including the MIB and PBCH loads, the MIB and PBCH loads indicating k SSB The value; or, the second information includes the MIB, which indicates k. SSB The value; the information indicates that the first cell supports request SIB1, including: k SSB The first value indicates that the first cell supports request SIB1.

[0026] The fourth aspect of this application provides a communication method, which can be executed by a terminal device, or by a component (such as a circuit, chip, or chip system) configured in the terminal device, or by a logic module or software capable of implementing all or part of the functions of the terminal device. This application does not limit the scope of the method. The following description uses a terminal device as an example.

[0027] The terminal device receives information indicating that terminal devices lacking the capability to request SIB1, or target terminal devices, are prohibited from accessing the first cell. Target terminal devices include both those capable of requesting SIB1 and those not. If a terminal device possesses the capability to request SIB1, and the information indicates that terminal devices lacking this capability are prohibited from accessing the first cell, then the terminal device accesses the first cell. This method prevents terminal devices lacking the capability to request SIB1 from accessing the first cell, thus saving energy for these devices.

[0028] In some implementations, the information includes first information and second information; the information indicates that terminal devices or target terminal devices that do not have the capability to request SIB1 are prohibited from accessing the first cell, including: the first information indicating information about the first cell; the second information including a first field and a second field, where the first field indicates prohibition and the second field has a third value, indicating that terminal devices that do not have the capability to request SIB1 are prohibited from accessing the first cell; or, the first field indicates prohibition and the second field has a fourth value, indicating that target terminal devices are prohibited from accessing the first cell. Using two fields to jointly indicate prohibition of terminal devices or target terminal devices that do not have the capability to request SIB1 from accessing the first cell provides greater flexibility.

[0029] In some implementations, the second information includes: MIB; or, the second information includes: MIB and third information, where the first field is contained in the MIB and the second field is contained in the third information.

[0030] In some implementations, the third piece of information includes the PBCH payload.

[0031] In some implementations, the information includes: first information and second information; the information indicates that the target terminal device is prohibited from accessing the first cell, including: the first information indicates information about the first cell, and the second information includes the MIB, the MIB indicating that the target terminal device is prohibited from accessing the first cell.

[0032] In some implementations, the information includes: first information and second information; the information indicating that the target terminal device is prohibited from accessing the first cell includes: the first information indicating information about the first cell, and the second information including an indication k SSB The values ​​of the MIB and PBCH loads, or, the second information includes an indication of k.SSB The value of the MIB; the MIB indicates that it is disabled, and k SSB The value is the first value, indicating that the target terminal device is prohibited from accessing the first cell.

[0033] A fifth aspect of this application provides an electronic device comprising: one or more processors, a memory, and a touchscreen; the memory is used to store program code; and the processor is used to run the program code, thereby enabling the electronic device to implement the communication methods provided in the first, second, third, and fourth aspects of this application.

[0034] A sixth aspect of this application provides a computer-readable storage medium having instructions stored thereon that, when executed on an electronic device, cause the electronic device to perform the communication methods provided in the first, second, third, and fourth aspects of this application.

[0035] The seventh aspect of this application provides a computer program product having stored thereon that, when executed on an electronic device, causes the electronic device to implement the communication methods provided in the first, second, third, and fourth aspects of this application.

[0036] An eighth aspect of this application provides a chip system comprising: at least one processor and an interface, the interface being configured to receive code instructions and transmit them to the at least one processor; the at least one processor executing the code instructions to implement the communication methods provided in the first, second, third, and fourth aspects of this application. Attached Figure Description

[0037] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0038] Figure 1 is an example flowchart of On-Demand SIB1;

[0039] Figure 2 is a flowchart of a communication method provided in an embodiment of this application;

[0040] Figure 3 is a flowchart of another communication method provided in an embodiment of this application;

[0041] Figure 4 is a flowchart of another communication method provided in an embodiment of this application;

[0042] Figure 5 is a flowchart of another communication method provided in an embodiment of this application;

[0043] Figure 6 is a flowchart of another communication method provided in an embodiment of this application;

[0044] Figure 7 is a flowchart of another communication method provided in an embodiment of this application;

[0045] Figure 8 is a flowchart of another communication method provided in an embodiment of this application;

[0046] Figure 9 is a schematic diagram illustrating the composition of a communication device provided in an embodiment of this application;

[0047] Figure 10 is a schematic diagram illustrating the composition of another communication device provided in an embodiment of this application;

[0048] Figure 11 is a schematic diagram of another communication device provided in an embodiment of this application. Detailed Implementation

[0049] The terms "first," "second," and "third," etc., used in this application specification, claims, and drawings are used to distinguish different objects, not to limit a specific order.

[0050] In the embodiments of this application, the words "in some implementations" or "for example" are used to indicate examples, illustrations or descriptions, and should not be construed as being more preferred or more advantageous than other embodiments or designs.

[0051] The communication systems applicable to the embodiments of this application can be second-generation (2G) communication systems, third-generation (3G) communication systems, long-term evolution (LTE) systems, fifth-generation (5G) communication systems, LTE and 5G hybrid architectures, 5G new radio (5G NR) systems, and new communication systems that will emerge in the future development of communication.

[0052] A communication system includes terminal equipment and network equipment. Network equipment includes access network equipment and core network equipment.

[0053] Terminal devices can take various forms, such as mobile phones, tablets, computers with wireless transceiver capabilities, virtual reality (VR) terminal devices, augmented reality (AR) terminal devices, wireless terminal devices in industrial control, vehicle-mounted terminal devices, wireless terminal devices in self-driving technology, wireless terminal devices in remote medical care, wireless terminal devices in smart grids, wireless terminal devices in transportation safety, wireless terminal devices in smart cities, wireless terminal devices in smart homes, wearable terminal devices, and so on. Terminal devices are sometimes also referred to as user equipment (UE), access terminal devices, vehicle-mounted terminal devices, industrial control terminal devices, UE units, UE stations, mobile stations, mobile terminals, remote stations, remote terminal devices, mobile devices, UE terminal devices, wireless communication devices, UE agents, or UE devices. Terminal devices can also be fixed terminal devices or mobile terminal devices.

[0054] Access network equipment can be terrestrial base stations or non-terrestrial network (NTN) equipment. NTN equipment can also be called base stations and / or satellite access nodes (SAN).

[0055] A base station is any device located on the network side with wireless transceiver capabilities, including but not limited to: evolved Node Bs (NodeBs, eNBs, or e-NodeBs) in LTE, base stations (gNodeBs or gNBs) or transmission receiving points / transmission reception points (TRPs) in new radio (NR), base stations evolved later in 3GPP, access nodes, wireless relay nodes, and wireless backhaul nodes in Wi-Fi systems. Base stations can be macro base stations, micro base stations, pico base stations, small cells, relay stations, or balloon stations, etc. A base station can contain one or more co-located or non-co-located TRPs. A base station can also be a radio controller, centralized unit (CU), and / or distributed unit (DU) in a cloud radio access network (CRAN) scenario. Base stations can communicate with terminal devices, or they can communicate with terminal devices through relay stations.

[0056] A base station supports at least one cell. In the embodiments of this application, a cell with NES capability is referred to as an NES cell. In the following embodiments of this application, a cell sending or broadcasting a message (or information) means that the base station supporting that cell sends or broadcasts a message (or information) under that cell.

[0057] NES cells can also be referred to as cells that support SIB1 requests, cells that support SIB1 requests, cells that support on-demand SIB1 requests, etc.

[0058] An example of On-Demand SIB1 is shown in Figure 1:

[0059] Step 0: Cells that support SIB1 requests exchange information with neighboring cells of the NES cell (referred to as cell A in Figure 1) through the Xn interface.

[0060] The information exchange associated with the embodiments of this application is that the NES cell sends information to cell A, and the information sent includes information related to SIB1 on demand.

[0061] Step 1: Cell A sends an SIB1 request for configuration information, and the corresponding terminal device receives the SIB1 request for configuration information.

[0062] SIB1 request configuration information is configured based on relevant information about the SIB1 request.

[0063] Step 2: The terminal device sends SIB1 request information to the NES cell based on the SIB1 request configuration information, and the NES cell receives the SIB1 request information accordingly.

[0064] Step 3: The NES cell sends SIB1 to the terminal device, and the terminal device receives SIB1 accordingly.

[0065] It is evident that network devices do not broadcast SIB1, but send SIB1 to the requesting terminal device when the terminal device requests it.

[0066] The process shown in Figure 1 is only an example. In other implementations, the SIB1 request configuration information is sent by the cell that supports the SIB1 request (i.e., the NES cell), or the terminal device sends the SIB1 request information to cell A, and correspondingly, SIB1 is sent from cell A to the terminal device.

[0067] In the embodiments of this application, a terminal device that has the ability to request SIB1 is referred to as a terminal device with the ability to request SIB1, or a terminal device that supports SIB1 requests, or a terminal device that supports requesting SIB1, etc.

[0068] For some terminal devices, such as those implemented before Rel-19 (version 19), and those implemented after Rel-19 that lack the ability to request SIB1, these devices are unable to request SIB1. Cells that support SIB1 requests no longer broadcast SIB1. This lack of broadcasting means that when network devices send synchronization signals and physical broadcast channel blocks (SSBs) on the GSCN, the MIBs contained in the SSBs do not indicate valid time-frequency domain resources for the Physical Downlink Control Channel (PDCCH). Terminal devices cannot obtain SIB1 when they receive such SSBs. SSBs that do not carry valid time-frequency domain resources for the SIB1 PDCCH can be called non-cell-defined SSBs, or NCD-SSBs for short. Because cells that support SIB1 requests no longer broadcast SIB1, these types of terminal devices cannot obtain SIB1 in cells that do not broadcast SIB1, and therefore cannot successfully access cells that support SIB1 requests. Based on the protocol, these terminal devices will attempt to receive the cell-defined SSB (CD-SSB) multiple times on one or more synchronization grids GSCN. This attempt will lead to excessive power consumption of the terminal devices. The CD-SSB refers to the SSB in which the MIB carries the time-frequency domain resource indication of the valid SIB1 PDCCH.

[0069] The embodiments of this application provide a communication method to solve the problem of excessive power consumption of terminal devices that do not have the ability to request SIB1 in cells that support SIB1 requests.

[0070] An embodiment of this application provides a communication method that can be applied to a network device. Unless otherwise specified, the "network device" in the embodiments of this application can refer to the network device itself, or a component in the network device (e.g., a processor, chip, or chip system), or a logical module or software that can implement all or part of the functions of the network device. The method includes: configuring information, wherein the information indicates whether a first cell supports or does not support requesting system information block SIB1, and sending information.

[0071] Accordingly, the embodiments of this application provide a communication method that can be applied to a terminal device. Unless otherwise specified, the "terminal device" in the embodiments of this application can refer to the terminal device itself, or a component in the terminal device (e.g., a processor, chip, or chip system), or a logic module or software that can implement all or part of the functions of the terminal device. The method includes: receiving information indicating whether a first cell supports or does not support requesting System Information Block SIB1; and accessing the first cell when the terminal device has the ability to request SIB1 and the information indicates that the first cell supports requesting System Information Block SIB1.

[0072] Because the terminal device can access the first cell if it supports requesting SIB1 based on its capabilities and information indications, it will not access a cell that supports SIB1 if it does not have the capability to request SIB1. This reduces the possibility of increased power consumption caused by the terminal device repeatedly detecting CD-SSB to receive SIB1, thereby reducing the power consumption of the terminal device.

[0073] The following will provide a detailed description with reference to Figures 2-5. In the embodiments corresponding to Figures 2-5, the information configured and transmitted by the network device includes first information and second information. The first information is used to indicate information about the first cell. An example of the first information is the primary synchronization signal (PSS) and the secondary synchronization signal (SSS). The second information is used to indicate whether request SIB1 is supported or not. An example of the second information will be described with reference to the steps in the embodiments corresponding to Figures 2-5.

[0074] Figure 2 is a flowchart of a communication method provided by an embodiment of this application. In the following steps, the first cell is a cell that supports SIB1 request. Figure 2 includes the following steps:

[0075] S11. The first cell configures and broadcasts an SSB. Correspondingly, terminal devices that do not have the ability to request SIB1 receive the SSB.

[0076] The SSB contains the primary synchronization signal (PSS), the secondary synchronization signal (SSS), and the physical broadcast channel (PBCH) information.

[0077] The PBCH message contains the master information block (MIB) and the PBCH payload.

[0078] In some cases, SSB is also called synchronization signal (SS) / PBCH; therefore, SS / PBCH and SSB are understood as equivalent. As mentioned above, in the embodiments of this application, the SSB transmitted by the first cell of the NES cell is NCD-SSB, which does not indicate the transmission resources of a valid SIB1 PDCCH.

[0079] S12. Terminal devices that do not have the ability to request SIB1 obtain the physical cell identifier (PCI) of the first cell and the MIB indication information in the SSB based on the SSB.

[0080] In some implementations, the terminal device obtains the PCI of the first cell based on PSS and SSS.

[0081] The MIB contains multiple fields, one of which indicates whether access is denied or permitted. For example, the MIB may contain a `cellBarred` field. A value of `barred` indicates denial, while a value of `notbarred` indicates permission. Combined with the PSS and SSS, this indicates the first cell. The denial or permission statement means that access to the first cell is denied or permitted. In this embodiment, the value of the `cellBarred` field is exemplified by `barred`.

[0082] For terminal devices implemented before Rel-19, after resolving the PCI and cellBarred fields of the first cell to have a value of "barred," the device will not access the first cell because the value of the cellBarred field is effective. For some terminal devices implemented after Rel-19 that can recognize SIB1 request configuration information, after resolving the PCI and cellBarred fields of the first cell to have a value of "barred," the device will not access the first cell because the value of the cellBarred field is effective. However, for other terminal devices implemented before and after Rel-19, the cellBarred field is ineffective. For example, the terminal device may not parse the cellBarred field or may ignore the value after parsing it. In other words, a cellBarred value of "barred" cannot prevent such terminal devices from accessing the first cell that supports SIB1 requests. Examples of such terminal devices include lightweight (RedCap) terminal devices or non-terrestrial network (NTN) terminal devices implemented after Rel-19. These terminal devices need to combine the following steps to determine whether to access the first cell.

[0083] In the embodiments of this application, terminal devices that do not have the ability to request SIB1 and terminal devices that have the ability to request SIB1 refer to terminal devices where the cellBarred field is not effective. Of course, they can also refer to terminal devices where the cellBarred field is effective. The embodiments of this application do not limit this.

[0084] S13. Cell A broadcasts SIB1 request configuration information. Correspondingly, terminal devices that do not have the ability to request SIB1 receive the SIB1 request configuration information.

[0085] The SIB1 request configuration information contains the PCI of the cell that supports the SIB1 request. In this embodiment, the SIB1 request configuration information is used as an example of the second information.

[0086] The execution order of S11 and S13 is not a limitation.

[0087] S14. Terminal devices that do not have the ability to request SIB1 determine whether the PCI of the first cell is included in the PCI of the cell that supports requesting SIB1. If so, the access process to the first cell is not executed (as indicated by the cross in Figure 2).

[0088] The PCI of the first cell is included in the PCI of the cell that supports SIB1 request, indicating that the first cell supports SIB1 request. For terminal devices that do not have the capability to request SIB1, they cannot obtain SIB1 from the cell that supports SIB1 request, and therefore, they do not access the first cell. It is understood that the process for accessing the first cell is only an example and not a limitation. If the information of the first cell is not included in the information of the cell that supports SIB1 request, terminal devices that do not have the capability to request SIB1 will not execute the process or steps for the first cell.

[0089] PCI is just one example of information about a cell.

[0090] As can be seen from the process in Figure 2, the network device implicitly indicates whether the first cell supports requesting SIB1 through the PSS and SSS in the SSB and the SIB1 request configuration information. If the terminal device does not have the ability to request SIB1 determines that the first cell does not support requesting SIB1 based on the SSB and SIB1 request configuration information, it will not access the first cell. This avoids the increased energy consumption caused by repeatedly trying to receive CD-SSB in the first cell because it does not have the ability to request SIB1 and therefore cannot obtain SIB1.

[0091] In Figure 2, based on Figure 1, we take cell A sending an SIB1 request for configuration information as an example, but this is not intended to be limiting. Furthermore, the information sent by the first cell can be sent by other cells, and this is not considered a limitation in the embodiments of this application.

[0092] Figure 3 is a flowchart of another communication method provided by an embodiment of this application. The difference between the flowchart shown in Figure 2 and the flowchart is that the terminal device with SIB request capability executes the corresponding process based on the received information. Figure 3 includes the following steps:

[0093] S21. The first cell configures and broadcasts an SSB, and correspondingly, terminal devices with the ability to request SIB1 receive the SSB.

[0094] For details regarding SSB, please refer to S11.

[0095] S22. Terminal devices with the capability to request SIB1 obtain PCI and MIB indication information of the first cell based on SSB.

[0096] S23. Cell A broadcasts SIB1 request configuration information, and correspondingly, terminal devices capable of requesting SIB1 receive the SIB1 request configuration information.

[0097] For details on the implementation, please refer to S13.

[0098] S24. The terminal device with the capability to request SIB1 determines whether the PCI of the first cell is included in the PCI of the cell that supports requesting SIB1.

[0099] For details on the implementation of S24, please refer to S14.

[0100] The PCI of the first cell is included in the PCI of the cell that supports SIB1 request, indicating that the first cell is a cell that supports SIB1 request. Therefore, terminal devices with SIB1 request capability can access the first cell, i.e., execute S25.

[0101] S25. Terminal devices with the capability to request SIB1 execute the process of accessing the first cell.

[0102] Referring to Figure 1, if the judgment result of S24 is yes, the terminal device with the ability to request SIB1 executes steps 2 and 3, and after step 3, executes S25.

[0103] The process shown in Figure 3 ensures that a terminal device can only access a cell that supports SIB1 request if it has the capability to request SIB1. This avoids terminal devices that do not have the capability to request SIB1 making multiple meaningless attempts to receive CD-SSB in cells that support SIB1 request, thus reducing the energy consumption of terminal devices that do not have the capability to request SIB1 request.

[0104] Understandably, in order to fully utilize the energy-saving characteristics of terminal devices capable of requesting SIB1 and reduce the energy consumption of mobile communication systems, if the first cell is not a cell that supports requesting SIB1, then terminal devices capable of requesting SIB1 will not access the first cell. This increases the likelihood that terminal devices capable of requesting SIB1 will access cells that support requesting SIB1. Furthermore, network devices use information such as MIB, SIB1 request configuration information, and PBCH load to indicate whether the first cell supports or does not support requesting SIB1, which helps terminal devices to know as early as possible whether to access the first cell, further reducing the energy consumption of terminal devices.

[0105] Figure 4 shows a flowchart of another communication method provided by an embodiment of this application. The difference between Figures 2 and 3 is that the network device uses a display method to indicate whether the first cell supports or does not support request SIB1. Figure 4 includes the following steps:

[0106] S31. The first cell configures and broadcasts the SSB, and the corresponding terminal equipment receives the SSB.

[0107] Terminal devices include terminal devices that have the ability to request SIB1 and terminal devices that do not have the ability to request SIB1.

[0108] In this embodiment, for example, the second information is the MIB or PBCH load in the SSB.

[0109] In the SSB, the PSS and SSS indicate the first cell, and the MIB or PBCH payload indicates that the first cell supports SIB1 request. In some implementations, the reserved field in the MIB or PBCH payload indicates that the first cell supports SIB1 request; in other implementations, a new field is added to the MIB or PBCH payload (compared to the existing protocol), and this new field indicates that the first cell supports SIB1 request. The size of the reserved field or the new field can be 1 bit or greater than 1 bit.

[0110] Taking the MIB as an example, the spare field is a 1-bit reserved field in the MIB. Using the value pre-configured for the spare field, it indicates whether the first cell supports or does not support request SIB1. In this embodiment, since it is assumed that the first cell supports request SIB1, the value of the spare field in S31 indicates that the first cell supports request SIB1.

[0111] S32. Terminal devices with the capability to request SIB1 execute the access to the first cell procedure based on the MIB or PBCH load.

[0112] Terminal devices that lack the capability to request SIB1 do not execute the access procedure to the first cell. The process shown in Figure 4, by instructing the first cell to support SIB1 requests via MIB or PBCH load, prevents terminal devices lacking the capability to request SIB1 from executing the access procedure to the first cell. This avoids multiple attempts to acquire resources for SIB1 transmission, such as multiple attempts to receive CD-SSB, thus reducing energy consumption. Furthermore, by explicitly indicating whether the first cell supports or does not support SIB1 requests, the terminal device does not need to make a judgment, which also helps reduce its energy consumption.

[0113] It is understandable that the "terminal device with SIB1 request capability" and "terminal device without SIB1 request capability" shown in Figure 4 are intended to compare the differences between the two types of terminal devices when the MIB or PBCH load indicates that the first cell supports SIB1 request, and are not intended to limit the two types of terminal devices to receiving the SSB together, or to ensure that the SSB is sent to both types of terminal devices, nor to limit the information sent by the network device to be received by both types of terminal devices.

[0114] Figure 5 shows a flowchart of another communication method provided by an embodiment of this application, including the following steps:

[0115] S41. The first cell configures and broadcasts the SSB, and the corresponding terminal equipment receives the SSB.

[0116] The SSB includes the MIB and PBCH payloads. The cellBarred field in the MIB has a value of barred. The MIB also contains the ssb-SubcarrierOffset field, which represents the subcarrier frequency offset between the SSB and the resource block.

[0117] The PBCH payload contains reserved or newly added fields that can be used in conjunction with the ssb-SubcarrierOffset field to indicate k. SSB The size of a reserved or newly added field can be 1 bit.

[0118] In this embodiment, for example, the second information is the MIB and PBCH load, or the second information is the MIB.

[0119] S42. The terminal device obtains k based on SSB. SSB .

[0120] Subcarrier 0 of the SSB is not necessarily aligned to the position of subcarrier 0 of the resource block, k SSB This represents the number of subcarriers between subcarrier 0 of the SSB and subcarrier 0 of the resource block. Because this embodiment assumes that the first cell supports requesting SIB1, and that the k of the cell supporting requesting SIB1... SSB Since it is the first value, the terminal device obtains k. SSB Then, based on k SSB The value and its own capabilities can determine whether to connect to the first cell.

[0121] In some implementations, the frequency range (FR) of the carrier used for communication between the terminal device and the first cell is FR1, and k is obtained based on the ssb-SubcarrierOffset field in the MIB and 1 bit in the PBCH payload. SSB The obtained k SSB The first value is defined as any value that is not less than 24 and not greater than 31, or 30 or 31. All other values ​​are referred to as the second value.

[0122] In other implementations, the carrier frequency range used for communication between the terminal device and the first cell is FR2, and k is obtained based on the ssb-SubcarrierOffset field in the MIB. SSB The obtained k SSB The first value is defined as any value that is not less than 12 and not greater than 15, or 14 or 15. All other values ​​are referred to as the second value.

[0123] S43. Terminal devices capable of requesting SIB1 are based on k SSBIf the first value is selected, the process of accessing the first cell is executed.

[0124] Terminal devices that do not have the ability to request SIB1 are based on k SSB If the value is the first value, the process of accessing the first cell will not be executed.

[0125] The process shown in Figure 5 involves the terminal device obtaining k based on the SSB. SSB The value of the SIB1 request and whether the device itself has the capability to request SIB1 determine whether to access a cell that supports SIB1 requests. This prevents terminal devices that do not have the capability to request SIB1 from accessing cells that support SIB1 requests, which helps reduce the energy consumption of such terminal devices.

[0126] It is understandable that, in the process shown in Figures 4 and 5, for terminal devices where the cellBarred field is effective (i.e., the value of the cellBarred field is not ignored), access to the first cell can be prohibited based on the value of the cellBarred field being Barred. However, for terminal devices where the cellBarred field is not effective (such as RedCap terminal devices or NTN terminal devices before and after the implementation of Rel-19), access is prohibited based on k. SSB Based on the first value and its own capabilities, it decides whether to connect to the first cell.

[0127] In Figures 2-5, the value of the cellBarred field in the MIB is "barred" as an example. However, in the processes shown in Figures 2-5, the value of the cellBarred field can be replaced with "notbarred". In this case, for terminal devices that are not active after Rel-19 implementation, access to the first cell can still be prohibited based on the processes shown in Figures 2-5, even if the cellBarred field is not active. For terminal devices that are active after Rel-19 implementation, access to the first cell can still be prohibited based on Figures 2-5, even if the cellBarred field is active. For terminal devices that were active before Rel-19 implementation, access to the first cell is attempted based on the value of "notbarred". However, because the first cell supports requesting SIB1 but does not broadcast SIB1, terminal devices that are not active are prohibited from accessing the first cell because they cannot obtain SIB1. Therefore, when the value of the cellBarred field is notbarred, the process shown in Figures 2-5 can reduce the power consumption of terminal devices that do not have the ability to request SIB1.

[0128] In the embodiments of this application, a communication method is also provided. This method can be applied to a network device. Unless otherwise specified, the "network device" in the embodiments of this application can refer to the network device itself, or a component in the network device (e.g., a processor, chip, or chip system), or a logic module or software that can implement all or part of the functions of the network device. The method includes: configuring information, wherein the information indicates that terminal devices or target terminal devices that do not have the ability to request SIB1 are prohibited from accessing a first cell, wherein the target terminal devices include terminal devices that have the ability to request SIB1 and terminal devices that do not have the ability to request SIB1, and sending the information.

[0129] Correspondingly, a communication method is also provided. This method can be applied to a terminal device. Unless otherwise specified, the "terminal device" in the embodiments of this application can refer to the terminal device itself, or a component in the terminal device (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the functions of the terminal device. The method includes: receiving information indicating that a terminal device or a target terminal device that does not have the capability to request SIB1 is prohibited from accessing the cell. The target terminal device includes terminal devices that have the capability to request SIB1 and terminal devices that do not have the capability to request SIB1. When the terminal device has the capability to request SIB1 and the information indicates that a terminal device that does not have the capability to request SIB1 is prohibited from accessing the first cell, the terminal device accesses the first cell.

[0130] The network device indicates to the terminal device whether the cell supports or does not support requesting SIB1. Based on the network's indication and its own capabilities, the terminal device accesses the first cell. This can prevent terminal devices that do not have the ability to request SIB1 from accessing cells that support requesting SIB1, thereby reducing the energy consumption caused by terminal devices that do not have the ability to request SIB1 repeatedly trying to receive CD-SSB.

[0131] The following will provide a detailed explanation with reference to Figures 6 and 7. In the embodiments corresponding to Figures 6 and 7, the information configured and sent by the network device includes first information and second information. The first information is used to indicate information about the first cell, and an example of the first information is PSS and SSS. The second information is used to indicate whether SIB1 request is supported or not. The second information includes a first field and a second field. The first field indicates prohibition and the second field has a third value, indicating that terminal devices that do not have the ability to request SIB1 are prohibited from accessing the first cell; or, the first field indicates prohibition and the second field has a fourth value, indicating that the target terminal device is prohibited from accessing the first cell. The specific steps will be explained with reference to the embodiments corresponding to Figures 6 and 7.

[0132] The target terminal devices that have the ability to request SIB1 are those implemented after Rel-19. The target terminal devices that do not have the ability to request SIB1 are those implemented before Rel-19 and those implemented after Rel-19 that do not have the ability to request SIB1.

[0133] Figure 6 is a flowchart of another communication method provided by an embodiment of this application, including the following steps:

[0134] S51. The first cell configures and broadcasts the SSB, and the corresponding terminal equipment receives the SSB.

[0135] Terminal devices include terminal devices that have the ability to request SIB1 and terminal devices that do not have the ability to request SIB1.

[0136] In this embodiment, the SSB includes the MIB.

[0137] In some implementations, the first field is the cellBarred field in the MIB, and the second field can be a reserved field in the MIB, such as the spare field, or it can be a newly added field in the MIB. The size of the newly added field can be 1 bit.

[0138] In some implementations, both the first and second fields are enumeration types. For example, if the value of the cellBarred field is barred, terminal devices that were not implemented before Rel-19 can be prohibited from accessing the first cell. If the value of the second field is notbarred, terminal devices that have the ability to request SIB1 are allowed to access the first cell, while terminal devices that do not have the ability to request SIB1 are prohibited from accessing the first cell. If the value of the second field is barred, all terminal devices are prohibited from accessing the first cell.

[0139] In other implementations, the cellBarred field is an enumeration type, and the second field is a numeric type. For example, if the value of the cellBarred field is barred, it can prevent terminal devices that were not implemented before Rel-19 from accessing the first cell. If the value of the second field is 0, terminal devices with the ability to request SIB1 are allowed to access the first cell, while terminal devices without the ability to request SIB1 are prohibited from accessing the first cell. If the value of the second field is 1, all terminal devices are prohibited from accessing the first cell.

[0140] It is also possible that the cellBarred field is a numeric type, meaning that the first and second fields, through numerical values, indicate that terminal devices that do not have the ability to request SIB1 or all terminal devices are prohibited from accessing the first cell.

[0141] In this embodiment, it is assumed that the first cell supports SIB1 request, the value of the cellBarred field is barred, and the value of the second field is 0.

[0142] S52. A terminal device capable of requesting SIB1 executes the process of accessing the first cell based on the first field and the second field being the third value.

[0143] Terminal devices that do not have the ability to request SIB1 will not execute the access to the first cell procedure if the first and second fields have the third value.

[0144] The process shown in Figure 6 indicates whether access to the cell is prohibited or allowed through the first and second fields in the MIB. Therefore, the terminal device can decide whether to attempt to access the cell based on the first and second fields and its own capabilities. This can avoid excessive energy consumption caused by terminal devices that do not have the ability to request SIB1 repeatedly attempting to access cells that support SIB1 requests.

[0145] Figure 7 is a flowchart of another access method provided by an embodiment of this application. The difference from Figure 6 is that the second field is included in the PBCH payload. Figure 7 includes the following steps:

[0146] S61. The first cell configures and broadcasts the SSB, and the corresponding terminal equipment receives the SSB.

[0147] In this embodiment, the SSB includes the MIB and PBCH loads.

[0148] In some implementations, the first field is the cellBarred field in the MIB, and the second field is the newly added or reserved field in the PBCH payload. The size of the newly added or reserved field can be 1 bit.

[0149] For the types and values ​​of the first and second fields, please refer to S51.

[0150] S62. A terminal device capable of requesting SIB1 executes the access to the first cell procedure based on the first field and the second field.

[0151] Terminal devices that do not have the ability to request SIB1 will not execute the access to the first cell procedure based on the first and second fields.

[0152] It is understandable that the method of jointly indicating whether access to the cell is allowed through two fields in Figures 5 and 6, compared with the aforementioned embodiments, not only reduces the energy consumption of terminal devices, but also has greater flexibility. One manifestation of this greater flexibility is that, based on the joint indication of the first and second fields, it is possible to prohibit all terminal devices after Rel-19 from accessing the cell.

[0153] In some cases, a cell may not allow all terminal devices to access it. For example, the first cell supports SIB1 requests but is in the debugging phase, so it does not allow all terminal devices to access the cell.

[0154] In light of this situation, embodiments of this application provide yet another communication method, as shown in FIG8, including the following steps:

[0155] S71. The first cell configures and broadcasts the SSB, and the corresponding terminal equipment receives the SSB.

[0156] In this embodiment, for example, the first information is the PSS and SSS in the SSB. The second information is the MIB and PBCH load in the SSB, or the second information is the MIB in the SSB.

[0157] The value of the cellBarred field in the MIB is barred. The MIB also contains the ssb-SubcarrierOffset field.

[0158] If the frequency range of the carrier used by the first cell is FR1, then k is jointly indicated by the ssb-SubcarrierOffset field of the MIB and the 1 bit reserved or added in the PBCH payload. SSB If the frequency range of the carrier used by the first cell is FR2, then k is indicated by the ssb-SubcarrierOffset field of the MIB. SSB .

[0159] If the first cell supports requesting SIB1, then the indicated k SSB The first value is indicated by k if the first cell does not support requesting SIB1. SSB For examples of the first and second values, see S42.

[0160] S72, The terminal device obtains k based on SSB. SSB .

[0161] For details, please refer to S42.

[0162] In this embodiment, it is assumed that the first cell supports SIB1 request, and the terminal device obtains k. SSB This is the first value. In this case, both terminal devices with the ability to request SIB1 after the Rel-19 implementation and terminal devices without the ability to request SIB1 after the Rel-19 implementation are based on k. SSBIf the first value and the cellBarred field value are both "barred", the access procedure for the first cell will not be executed. For terminal devices that were active before Rel-19 implementation and whose cellBarred field was active, the access procedure for the first cell will not be executed if the cellBarred field value is "barred".

[0163] Under the mechanism of prohibiting access to the first cell provided in this embodiment, if the terminal device obtains k SSB If the second value is used, then both terminal devices with the ability to request SIB1 after the implementation of Rel-19 and terminal devices without the ability to request SIB1 after the implementation of Rel-19 are based on k. SSB If the second value and the cellBarred field value are both "barred", the procedure for accessing the first cell will be executed. For terminal devices that were in use before Rel-19 implementation and whose cellBarred field was active, the procedure for accessing the first cell will not be executed if the cellBarred field value is "barred".

[0164] In addition to the process shown in Figure 8, the terminal device can also skip the access to the first cell process based solely on the value of the cellBarred field being "barred," meaning it doesn't consider k. SSB When the value of the cellBarred field is barred, terminal devices implemented after Rel-19, as well as terminal devices implemented before Rel-19 and whose cellBarred field is active, will no longer access the first cell.

[0165] It is understandable that if a network device uses the value of the cellBarred field to prohibit terminal devices after the implementation of Rel-19, as well as terminal devices before the implementation of Rel-19 whose cellBarred field is in effect, from accessing the first cell, and if it is necessary to only prohibit terminal devices that do not have the ability to request SIB1 from accessing the first cell, then the value of the cellBarred field is set to notbarred, and this is combined with the methods shown in Figures 2-5 to indicate whether the first cell supports or does not support requesting SIB1.

[0166] Figure 9 is an example of the composition of a communication device provided in an embodiment of this application. The communication device can be a terminal device, including but not limited to mobile phones, smart wearable devices (such as smartwatches), and other electronic devices. Taking a mobile phone as an example, the communication device may include a processor 110, internal memory 120, display screen 130, antenna 1, antenna 2, mobile communication module 140, and wireless communication module 150, etc.

[0167] It is understood that the structure illustrated in this embodiment does not constitute a specific limitation on the communication device. In other embodiments, the communication device may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0168] The processor 110 may include one or more processing units, such as an application processor (AP), a modem processor, a digital signal processor (DSP), and / or a baseband processor.

[0169] Internal memory 120 can be used to store executable program code, which includes instructions. Processor 110 performs various functions of the electronic device by executing the instructions stored in internal memory 120.

[0170] The wireless communication function of the electronic device can be realized through antenna 1, antenna 2, mobile communication module 140, wireless communication module 150, modem processor and baseband processor, etc.

[0171] Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals.

[0172] The mobile communication module 140 can provide solutions for wireless communication applications, including 2G / 3G / 4G / 5G, in electronic devices.

[0173] In some embodiments, the mobile communication module 140 includes a communication interface coupled to the processor 110. This communication interface may be a transceiver or an input / output interface. In some embodiments, when the communication device is a chip configured in a terminal, the communication interface may be an input / output interface.

[0174] The wireless communication module 150 can provide solutions for wireless communication applications in electronic devices, including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), and infrared (IR) technologies.

[0175] In addition, an operating system runs on top of the aforementioned components. Examples include iOS, Android, and Windows. Applications can be installed and run on this operating system.

[0176] Figure 10 illustrates another example of the composition of a communication device provided in an embodiment of this application. This communication device can be a network device, such as a satellite. Figure 10 shows a simplified schematic diagram of a network device. The network device includes: at least one processor 210, at least one memory 220, at least one transceiver 230, at least one network interface 240, and one or more antennas 250. The processor 210, memory 220, transceiver 230, and network interface 240 are connected, for example, via a bus. In this embodiment, the connection may include various interfaces, transmission lines, or buses, etc., and this embodiment is not limited in this respect. The antenna 250 is connected to the transceiver 230. The network interface 240 is used to enable a network element to connect to other communication devices through a communication link. For example, the network interface 240 may include a network interface between a network element and network elements in the core network, such as an S1 interface. The network interface may also include a network interface between a network element and other network elements, such as an X2 or Xn interface.

[0177] The processor 210 shown in Figure 10 can specifically perform the network device processing actions in the above communication method, the memory 220 can perform the storage actions in the above communication method, the transceiver 230 and the antenna 250 can perform the transmission and reception actions in the above communication method, and the network interface 240 can perform the interaction actions between the network device and the terminal in the above method.

[0178] Processor 210 may include, but is not limited to, at least one of the following: a central processing unit (CPU), a microprocessor, a digital signal processor (DSP), a microcontroller unit (MCU), or an artificial intelligence processor, etc., which are various computing devices that run software. Each computing device may include one or more cores for executing software instructions to perform calculations or processing. The processor may be a standalone semiconductor chip or integrated with other circuits into a single semiconductor chip. For example, it may form a System-on-a-Chip (SoC) with other circuits (such as encoding / decoding circuits, hardware acceleration circuits, or various bus and interface circuits), or it may be integrated as a built-in processor within an ASIC. The ASIC with the integrated processor may be packaged separately or together with other circuits. In addition to the cores for executing software instructions to perform calculations or processing, the processor may further include necessary hardware accelerators, such as field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), or logic circuits that implement dedicated logic operations.

[0179] The memory 220 may include at least one of the following types, but is not limited to: read-only memory (ROM) or other types of static storage devices that can store static information and instructions, random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, or electrically erasable programmable-only memory (EEPROM).

[0180] Transceiver 230 can be used to support the reception or transmission of radio frequency (RF) signals between network elements and other devices. Transceiver 230 can be connected to antenna 250. Transceiver 230 includes a transmitter Tx and a receiver Rx. Specifically, one or more antennas 250 can receive RF signals. The receiver Rx of transceiver 230 is used to receive RF signals from the antennas, convert the RF signals into digital baseband signals or digital intermediate frequency (IF) signals, and provide the digital baseband signals or IF signals to processor 210 so that processor 210 can perform further processing on the digital baseband signals or IF signals, such as demodulation and decoding. In addition, the transmitter Tx in transceiver 230 is also used to receive modulated digital baseband signals or IF signals from processor 210, convert the modulated digital baseband signals or IF signals into RF signals, and transmit the RF signals through one or more antennas 250. Specifically, the receiver Rx can selectively perform one or more stages of downmixing and analog-to-digital conversion on the radio frequency signal to obtain a digital baseband signal or a digital intermediate frequency (IF) signal. The order of the downmixing and IF processing is adjustable. The transmitter Tx can selectively perform one or more stages of upmixing and digital-to-analog conversion on the modulated digital baseband or digital IF signal to obtain a radio frequency signal. The order of the upmixing and IF processing is also adjustable. Digital baseband signals and digital IF signals can be collectively referred to as digital signals.

[0181] The transceiver 230 can also be referred to as an input / output interface or a communication interface, etc. In some embodiments, when the above-mentioned communication device is a chip configured in a satellite, the transceiver 230 can be an input / output interface.

[0182] It should be understood that Figure 10 is merely an example and not a limitation, and the network devices described above, including processors, memory, and transceivers, may not depend on the structure shown in Figure 10.

[0183] This application also provides a communication device.

[0184] As shown in Figure 11, the communication device 300 can correspondingly implement the functions or steps implemented by the network device in the various method embodiments described above. The communication device 300 includes a processing module 301 and a transceiver module 302. In some embodiments, the communication device may further include a storage module 303, which can be used to store instructions (code or program) and / or data. The processing module 301 and the transceiver module 302 can be coupled to the storage module 303. For example, the processing module 301 can read instructions (code or program) and / or data from the storage module to implement the corresponding method. The various modules described above can be set independently, or partially or completely integrated.

[0185] In some embodiments, the processing module 301 is used to configure information indicating whether the first cell supports or does not support Request System Information Block (SIB1), and the transceiver module 302 is used to send the information.

[0186] In other embodiments, the processing module 301 is used to configure information indicating that terminal devices or target terminal devices that do not have the capability to request SIB1 are prohibited from accessing the first cell. The target terminal devices include terminal devices that have the capability to request SIB1 and terminal devices that do not have the capability to request SIB1. The transceiver module 302 is used to send the information.

[0187] The specific implementation of the functions of the transceiver module 302 and the processing module 301 can be found in the embodiments shown in Figures 2-8, and will not be repeated here.

[0188] The communication device 300 shown in Figure 11 can also correspondingly implement the functions or steps implemented by the terminal device in the above-described method embodiments. The communication device 300 includes a processing module 301 and a transceiver module 302. In some embodiments, the communication device 300 may not include the processing module 301. In some embodiments, the communication device may also include a storage module 303, which can be used to store instructions (code or program) and / or data. The processing module 301 and the transceiver module 302 can be coupled to the storage module 303. For example, the processing module 301 can read instructions (code or program) and / or data from the storage module to implement the corresponding method. The above modules can be set independently, or partially or completely integrated.

[0189] In some embodiments, the transceiver module 302 is used to receive information indicating whether the first cell supports or does not support requesting System Information Block (SIB1), and the processing module 301 is used to access the first cell when the terminal device has the ability to request SIB1 and the information indicates that the first cell supports requesting SIB1.

[0190] In other embodiments, the transceiver module 302 is used to receive information indicating that a terminal device or a target terminal device that does not have the capability to request SIB1 is prohibited from accessing the first cell. The target terminal device includes a terminal device that has the capability to request SIB1 and the terminal device that does not have the capability to request SIB1. The processing module 301 is used to access the first cell when the terminal device has the capability to request SIB1 and the information indicates that the terminal device that does not have the capability to request SIB1 is prohibited from accessing the first cell.

[0191] The specific implementation of the functions of the transceiver module 302 and the processing module 301 can be found in the embodiments shown in Figures 2-8, and will not be repeated here.

[0192] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the explanations and beneficial effects of the relevant content in any of the communication devices provided above can be referred to the corresponding method embodiments provided above, and will not be repeated here.

[0193] This application also provides a processor, including: an input circuit, an output circuit, and a processing circuit. The processing circuit receives signals through the input circuit and transmits signals through the output circuit, causing the processor to execute the communication method described in the above embodiments.

[0194] In specific implementation, the processor can be one or more chips, the input circuit can be input pins, the output circuit can be output pins, and the processing circuit can be transistors, gate circuits, flip-flops, and various logic circuits. The input signal received by the input circuit can be received and input by, for example, but not limited to, a receiver, and the signal output by the output circuit can be output to, for example, but not limited to, a transmitter and transmitted by the transmitter. Furthermore, the input circuit and the output circuit can be the same circuit, which is used as the input circuit and the output circuit at different times. This application does not limit the specific implementation of the processor and various circuits.

[0195] This application also provides a chip system including one or more processors for calling and executing instructions stored in memory, thereby executing the communication method described in the above embodiments. The chip system may be composed of a chip or may include chips and other discrete devices. The chip system may include input circuitry or interfaces for transmitting information or data, and output circuitry or interfaces for receiving information or data.

[0196] This application also provides a computer-readable storage medium storing instructions that, when executed on one or more computing devices, cause the one or more computing devices to perform the communication method described in the above embodiments.

[0197] Computer-readable storage media can be non-transitory computer-readable storage media, such as read-only memory (ROM), random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage devices.

[0198] This application also provides a computer program product. When executed by one or more computing devices, the computer program product allows the computing devices to execute any of the aforementioned communication methods. The computer program product can be a software installation package. When any of the aforementioned communication methods is required, the computer program product can be downloaded and executed on a computer.

[0199] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit it. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

Claims

1. A communication method, characterized in that, include: Configuration information, which indicates whether the first cell supports or does not support requesting System Information Block (SIB1); Send the aforementioned information.

2. The method according to claim 1, characterized in that, The information includes: first information and SIB1 request configuration information; The information indicating whether the first cell supports or does not support the request system information block SIB1 includes: The first information indicates the information of the first cell, and the SIB1 request configuration information indicates the information of the cell that supports the SIB1 request. If the information of the first cell is included in the information of the cell that supports the SIB1 request, it indicates that the first cell supports the SIB1 request. If the information of the first cell is not included in the information of the cell that supports the SIB1 request, it indicates that the first cell does not support the SIB1 request.

3. The method according to claim 1, characterized in that, The information includes: first information and second information; The information indicating whether the first cell supports or does not support requesting System Information Block SIB1 includes: The first information indicates information about the first cell, and the second information includes the Master Information Block (MIB) or the Physical Broadcast Channel (PBCH) payload, wherein the MIB or the PBCH payload indicates whether the first cell supports or does not support Request SIB1.

4. The method according to claim 1, characterized in that, The information includes: first information and second information; The information indicating whether the first cell supports or does not support requesting System Information Block SIB1 includes: The first information indicates information about the first cell; The second information includes the MIB and PBCH loads, the MIB and PBCH loads indicating k SSB The value; or, the second information includes a MIB, the MIB indicating the value of k. SSB The value; The k SSB The value of k is the first value indicating that the first cell supports request SIB1. SSB The value of the second value indicates that the first cell does not support requesting SIB1.

5. A communication method, characterized in that, include: Configuration information, the information indicating that terminal devices or target terminal devices that do not have the ability to request SIB1 are prohibited from accessing the first cell, the target terminal devices including terminal devices that have the ability to request SIB1 and terminal devices that do not have the ability to request SIB1; Send the aforementioned information.

6. The method according to claim 5, characterized in that, The information includes first information and second information; The information indication prohibits terminal devices or target terminal devices that do not have the capability to request SIB1 from accessing the first cell, including: The first information indicates information about the first cell; The second information includes a first field and a second field, wherein the first field indicates prohibition and the second field is a third value, indicating that the terminal device that does not have the ability to request SIB1 is prohibited from accessing the first cell; or, the first field indicates prohibition and the second field is a fourth value, indicating that the target terminal device is prohibited from accessing the first cell.

7. The method according to claim 6, characterized in that, The second information includes: MIB; or, the second information includes: the MIB and third information, wherein the first field is contained in the MIB and the second field is contained in the third information.

8. The method according to claim 7, characterized in that, The third piece of information includes: PBCH load.

9. The method according to claim 5, characterized in that, The information includes: first information and second information; The information indicating that the target terminal device is prohibited from accessing the first cell includes: The first information indicates information about the first cell, and the second information includes a MIB, wherein the MIB indicates that the target terminal device is prohibited from accessing the first cell.

10. The method according to claim 5, characterized in that, The information includes: first information and second information; The information indicating that the target terminal device is prohibited from accessing the first cell includes: The first information indicates information about the first cell, and the second information includes an indication of k. SSB The value of the MIB and PBCH load, or, the second information includes an indication of the k SSB The value of the MIB; The MIB instruction is prohibited, and the k SSB The value is the first value, indicating that the target terminal device is prohibited from accessing the first cell.

11. A communication method, characterized in that, include: Received information, the information indicating whether the first cell supports or does not support requesting system information block SIB1; If the terminal device has the capability to request SIB1, and the information indicates that the first cell supports requesting SIB1, then the device can access the first cell.

12. The method according to claim 11, characterized in that, The information includes first information and SIB1 request configuration information, wherein the first information indicates information about the first cell, and the SIB1 request configuration information indicates information about cells that support SIB1 requests; The information indicating that the first cell supports SIB1 includes: The information of the first cell is included in the information of the cell that supports the SIB1 request.

13. The method according to claim 11, characterized in that, The information includes: first information and second information; The information indicating whether the first cell supports or does not support requesting System Information Block SIB1 includes: The first information indicates information about the first cell, and the second information includes the MIB or PBCH load, wherein the MIB or PBCH load indicates whether the first cell supports or does not support request SIB1.

14. The method according to claim 11, characterized in that, The information includes: first information and second information; The information indicating whether the first cell supports or does not support requesting System Information Block SIB1 includes: The first information indicates information about the first cell; The second information includes the MIB and PBCH loads, the MIB and PBCH loads indicating k SSB The value; or, the second information includes a MIB, the MIB indicating the value of k. SSB The value; the information indicating that the first cell supports request SIB1 includes: The k SSB The first value indicates that the first cell supports request SIB1.

15. An access method, characterized in that, include: Receive information indicating that terminal devices or target terminal devices that do not have the capability to request SIB1 are prohibited from accessing the first cell, wherein the target terminal devices include terminal devices that have the capability to request SIB1 and terminal devices that do not have the capability to request SIB1. If the terminal device has the capability to request SIB1, and the information indicates that the terminal device without the capability to request SIB1 is prohibited from accessing the first cell, then the terminal device can access the first cell.

16. The method according to claim 15, characterized in that, The information includes first information and second information; The information indication prohibits terminal devices or target terminal devices that do not have the capability to request SIB1 from accessing the first cell, including: The first information indicates information about the first cell; The second information includes a first field and a second field, wherein the first field indicates prohibition and the second field is a third value, indicating that the terminal device that does not have the ability to request SIB1 is prohibited from accessing the first cell; or, the first field indicates prohibition and the second field is a fourth value, indicating that the target terminal device is prohibited from accessing the first cell.

17. The method according to claim 16, characterized in that, The second information includes: MIB; or, the second information includes: the MIB and third information, wherein the first field is contained in the MIB and the second field is contained in the third information.

18. The method according to claim 17, characterized in that, The third piece of information includes: PBCH load.

19. The method according to claim 15, characterized in that, The information includes: first information and second information; The information indicating that the target terminal device is prohibited from accessing the first cell includes: The first information indicates information about the first cell, and the second information includes a MIB, wherein the MIB indicates that the target terminal device is prohibited from accessing the first cell.

20. The method according to claim 15, characterized in that, The information includes: first information and second information; The information indicating that the target terminal device is prohibited from accessing the first cell includes: The first information indicates information about the first cell, and the second information includes an indication of k. SSB The value of the MIB and PBCH load, or, the second information includes an indication of the k SSB The value of the MIB; The MIB instruction is prohibited, and the k SSB The value is the first value, indicating that the target terminal device is prohibited from accessing the first cell.

21. An electronic device, characterized in that, The electronic device includes: one or more processors, a memory, and a touch screen; the memory is used to store program code; the processor is used to run the program code, causing the electronic device to implement the communication method as described in any one of claims 1 to 20.

22. A computer-readable storage medium, characterized in that, It stores instructions that, when executed on an electronic device, cause the electronic device to perform the communication method as described in any one of claims 1 to 20.

23. A computer program product, characterized in that, It stores an execution method that, when the computer program product is run on the electronic device, causes the electronic device to implement the communication method as described in any one of claims 1 to 20.

24. A chip system, characterized in that, include: At least one processor and an interface, the interface being used to receive code instructions and transmit them to the at least one processor; The at least one processor executes the code instructions to implement the communication method according to any one of claims 1 to 20.

Images