Communication method and related apparatus
By having terminal devices receive or request SIB1 within a specified time window according to MIB instructions, the energy waste caused by network devices sending SIB1 on demand is solved, and efficient energy utilization is achieved.
Patent Information
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- HUAWEI TECH CO LTD
- Filing Date
- 2026-01-09
- Publication Date
- 2026-07-30
AI Technical Summary
In wireless communication systems, the way network devices send system message blocks (SIB1) on demand can lead to energy waste.
The terminal device determines whether to receive or request SIB1 based on the Master Information Block (MIB) instruction, and obtains SIB1 by receiving or sending the Physical Random Access Channel (PRACH) within a specified time window.
It reduces the energy consumption of terminal and network devices and improves energy utilization efficiency.
Smart Images

Figure CN2026071750_30072026_PF_FP_ABST
Abstract
Description
Communication methods and related devices
[0001] This application claims priority to Chinese Patent Application No. 202510121782.2, filed on January 24, 2025, 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 communications, and more particularly to a communication method and related apparatus. Background Technology
[0003] In wireless communication systems, network devices periodically broadcast System Information Block (SIB) 1 to provide critical information needed for terminal devices to access the network. To reduce the power consumption of network devices, terminal devices can send an SIB1 request to the network device when they need to obtain SIB1, allowing the network device to send SIB1 on demand. However, this method of sending SIB1 on demand still carries the potential for wasted energy. Summary of the Invention
[0004] This application provides a communication method and related apparatus to enable a terminal device to determine whether a first network device sends SIB1, and to obtain SIB1 by receiving SIB1 or requesting SIB1 depending on whether the first network device sends SIB1 or not, which helps to reduce the energy consumption of the first network device and the terminal device.
[0005] In a first aspect, embodiments of this application provide a communication method applied to a terminal-side device, such as a terminal device or a communication module in the terminal device, or a circuit or chip in the terminal device responsible for communication functions. Taking the application of this method to a terminal device as an example, the method includes: receiving a Master Information Block (MIB), where the MIB indicates whether to send a System Message Block (SIB1) or not to send SIB1; if the MIB indicates whether to send SIB1, receiving a first SIB1 within a first time window; or, if the MIB indicates whether to send SIB1, sending a Physical Random Access Channel (PRACH) and receiving the first SIB1 within a second time window, whereby the PRACH is used to request SIB1.
[0006] The terminal device can send SIB1 or not send SIB1 according to the MIB instruction. It can receive the first SIB1 in the first time window, or request SIB1 through PRACH and receive the first SIB1 in the second time window. This avoids directly sending PRACH to request SIB1, which helps to reduce the power consumption of the terminal device.
[0007] In some implementations, the length of the first time window is less than or equal to the length of the second time window.
[0008] The length of the first time window is less than or equal to the length of the second time window, which is beneficial for the terminal device to continuously receive the first SIB1 within the first time window.
[0009] In some implementations, the first time window is a preset time window; or, the method further includes: receiving first information from a second network device, the first information indicating at least one of the following: the length of the first time window, the start position of the first time window, or the end position of the first time window.
[0010] When the first time window is a preset time window, the overhead of indicating the first time window can be saved. Indicating the position of the first time window through the first information can improve the flexibility of the first time window setting.
[0011] In some implementations, the length of the second time window is a preset length; or, the method may further include: receiving second information from a second network device, the second information indicating the length of the second time window.
[0012] Similar to the first time window mentioned above, when the second time window is a preset time window, the overhead of indicating the second time window can be saved. Indicating the location of the second time window through second information improves the flexibility of its setting.
[0013] In some implementations, the MIB instructs whether to send system message block SIB1 or not, including: when the length of the second time window is greater than or equal to the first threshold, the MIB instructs whether to send SIB1 or not.
[0014] Wherein, the first threshold is a preset threshold; or, the method further includes: receiving third information from a second network device, wherein the third information indicates the first threshold.
[0015] In some implementations, the end position of the second time window is the same as the end position of the first time window.
[0016] The end position of the second time window is the same as the end position of the first time window, which allows the terminal device to continuously receive the first SIB1 within the first time period, avoiding wasting energy consumption of the terminal device and helping the terminal device save energy.
[0017] In some implementations, the first SIB1 corresponds to the first synchronization signal and physical broadcast channel block (SSB), and the first SSB is any SSB from the first network device.
[0018] The first SIB1 corresponds to the SIB1 in the direction of the first SSB. The terminal device can receive the first SIB1 in any direction corresponding to any SSB sent by the first network device, which can increase the probability of the terminal device receiving the first SIB1. This helps to avoid the terminal device wasting energy when it does not receive the first SIB1 and helps the terminal device save energy.
[0019] Secondly, embodiments of this application provide a communication method applied to a network-side device, such as a network device or a component (e.g., a chip, a chip system, etc.) within the network device, or it may be a logic module or software capable of implementing all or part of the functions of the network device. Taking the application of this method to a first network device as an example, the method includes: sending a MIB, wherein the MIB indicates whether to send SIB1 or not to send SIB1; if the MIB indicates that SIB1 should be sent, sending a first SIB1 within a first time window; or, if the MIB indicates that SIB1 should not be sent, receiving a PRACH and sending the first SIB1 within a second time window, wherein the PRACH is used to request SIB1.
[0020] The first network device may send SIB1 or not send SIB1 according to the MIB instruction. It can send the first SIB1 within the first time window, or receive the first SIB1 within the second time window according to the received PRACH for requesting SIB1. This avoids continuous reception of PRACH and helps reduce the power consumption of the first network device.
[0021] In some implementations, the length of the first time window is less than or equal to the length of the second time window.
[0022] In some implementations, the MIB indicates whether to send SIB1 or not, including: when the length of the second time window is greater than or equal to a first threshold, the MIB indicates whether to send SIB1 or not, where the first threshold is a preset threshold.
[0023] In some implementations, the first SIB1 includes the SIB1 corresponding to each of the multiple SSBs sent by the first network device within the first time window.
[0024] Within the first time window, each of the multiple SSBs sent by the first network device includes the first SIB1 in the direction corresponding to each SSB. This can be understood as the first network device sending the first SIB1 in the direction corresponding to each of the multiple SSBs, which is beneficial for the terminal device to receive the first SIB1 within the first time window and helps to reduce the power consumption of the terminal device.
[0025] In some implementations, the end position of the second time window is the same as the end position of the first time window.
[0026] Thirdly, embodiments of this application provide a communication method applied to a network-side device. Taking the application of this method to a second network device as an example, the method includes: sending first information to a terminal device, wherein the first information indicates at least one of the following: the length of a first time window, the start position of the first time window, or the end position of the first time window.
[0027] In some implementations, the method further includes sending a second message to the terminal device, the second message indicating the length of a second time window.
[0028] In some implementations, the method further includes sending third information to the terminal device, the third information indicating the first threshold.
[0029] The first, second, and third information can be included in the same information. The second network device can send the first, second, and third information simultaneously, which can save communication overhead.
[0030] Fourthly, embodiments of this application provide a communication method applied to a terminal-side device, such as a terminal device or a communication module in the terminal device, or a circuit or chip in the terminal device responsible for communication functions. Taking the application of this method to a terminal device as an example, the method includes: detecting a first physical downlink control channel (PDCCH) within a fourth time window, the first PDCCH including a PDCCH for scheduling SIB1; if the first PDCCH is detected within the fourth time window, receiving a first SIB1 according to the first PDCCH; or, if the first PDCCH is not detected within the fourth time window, sending a PRACH and receiving the first SIB1, the PRACH being used to request SIB1.
[0031] The terminal device detects the first PDCCH within the fourth time window. Depending on whether the first PDCCH is detected, it can receive the first SIB1 based on the first PDCCH, or request SIB1 through PRACH, thereby receiving the first SIB1. This avoids directly sending PRACH to request SIB1, which helps reduce the power consumption of the terminal device.
[0032] In some implementations, the first PDCCH includes a PDCCH scrambled with system information radio network temporary identifier (SI-RNTI) and a PDCCH scrambled with random access radio network temporary identifier (RA-RNTI).
[0033] When the first PDCCH includes both SI-RNTI scrambled PDCCH and RA-RNTI scrambled PDCCH, the probability of the terminal device detecting the first PDCCH within the fourth time window is increased, which is beneficial for the terminal device to receive the first SIB1 based on the first PDCCH and saves energy for the terminal device.
[0034] In some implementations, the length of the fourth time window is the same as the duration of the SIB1 transmission period.
[0035] The terminal device detects the first PDCCH within a time window of the same duration as the SIB1 transmission period. This allows the terminal device to detect the first PDCCH used for scheduling SIB1 in the shortest possible time, which helps save energy.
[0036] In some implementations, the fourth time window is a periodic time window, during which PRACH cannot be sent.
[0037] The terminal device does not send PRACH within the fourth time window; conversely, this can be understood as the first network device not receiving PRACH within the fourth time window. By not sending PRACH, the terminal device avoids frequent PRACH transmissions within the fourth time window, thus saving energy. Similarly, by not receiving PRACH within the fourth time window, the first network device avoids detecting PRACH within the fourth time window, thereby saving energy.
[0038] In some implementations, the method further includes receiving fourth information from a second network device, the fourth information indicating at least one of the following: the period of a fourth time window, the length of a fourth time window, the start position of a fourth time window, or the end position of a fourth time window.
[0039] Fifthly, embodiments of this application provide a communication method applied to a network-side device. Taking the application of this method to a second network device as an example, the method includes: sending fourth information to a terminal device, wherein the fourth information indicates at least one of the following: the period of a fourth time window, the length of the fourth time window, the start position of the fourth time window, or the end position of the fourth time window.
[0040] Sixthly, embodiments of this application provide a communication device, including modules or units for implementing the methods of the first to fifth aspects and any possible implementations of the first to fifth aspects. Each module or unit can implement its corresponding function by executing a computer program.
[0041] For example, the communication device in the sixth aspect is a terminal device or a component configured in a terminal device, such as a chip, chip system, processor, etc.; or, the communication device in the sixth aspect is a network device or a component configured in a network device, such as a chip, chip system, processor, etc.
[0042] In a seventh aspect, embodiments of this application provide a communication device, including a processor, which is configured to execute the communication methods in the first to fifth aspects and any possible implementations of the first to fifth aspects.
[0043] Optionally, the communication device includes a memory for storing instructions and data. The memory is coupled to a processor, which, when executing the instructions stored in the memory, can implement the methods described in the foregoing aspects.
[0044] Optionally, the communication device includes a communication interface for communicating with other communication devices. For example, the communication interface may be a transceiver, circuit, bus, module, pin, or other type of communication interface.
[0045] For example, the communication device provided in the seventh aspect is a chip or chip system, and may also be a terminal device or a first network device.
[0046] Eighthly, embodiments of this application provide a computer-readable storage medium including a computer program that, when run on a computer, causes the computer to implement the methods of the first to fifth aspects and any possible implementation of the first to fifth aspects.
[0047] Ninthly, embodiments of this application provide a computer program product, which includes a computer program (also referred to as code or instructions) that, when run, causes a computer to perform the methods of the first to fifth aspects and any possible implementation of the first to fifth aspects.
[0048] In a tenth aspect, embodiments of this application provide a communication system including the aforementioned terminal device, first network device, and second network device. The terminal device can be used to implement the methods in the first or fourth aspect and any possible implementation of the first or fourth aspect. The second network device can be used to implement the methods in the second aspect and any possible implementation of the second aspect. The second network device can also be used to implement the methods in the third or fifth aspect and any possible implementation of the third or fifth aspect.
[0049] The sixth to tenth aspects of this application correspond to the technical solutions of the first aspect of this application. The beneficial effects achieved by each aspect and the corresponding feasible implementation are similar, and will not be repeated here. Attached Figure Description
[0050] Figure 1 is a schematic diagram of the architecture of the communication system used in the embodiments of this application;
[0051] Figure 2 is a schematic diagram of the process by which network devices send SIB1 on demand;
[0052] Figure 3 is a flowchart illustrating a communication method provided in one embodiment of this application;
[0053] Figure 4 is a schematic diagram of the first network device sending the first SIB1;
[0054] Figure 5 is another schematic diagram of the first network device sending the first SIB1;
[0055] Figure 6 is a flowchart illustrating a communication method provided in another embodiment of this application;
[0056] Figure 7 is another schematic diagram of the first network device sending the first SIB1;
[0057] Figure 8 is a schematic diagram of the structure of a communication device provided in an embodiment of this application;
[0058] Figure 9 is a schematic diagram of the structure of a communication device provided in another embodiment of this application. Detailed Implementation
[0059] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.
[0060] It should be understood that in the embodiments of this application, "at least one" refers to one or more, and "more than one" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship, but it does not exclude the possibility of indicating that the preceding and following related objects are in an "and" relationship. The specific meaning can be understood in conjunction with the context. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c; a and b; a and c; b and c; or a and b and c. Here, a, b, and c can be single or multiple.
[0061] In this embodiment of the application, the use of prefixes such as "first" and "second" is merely for the purpose of distinguishing and describing different things belonging to the same name category, and does not constrain the order, size, or quantity of things. For example, "first parameter" and "second parameter" are simply different parameters, and there is no temporal or quantitative relationship between them.
[0062] This application will present various aspects, embodiments, or features relating to systems that may include multiple devices, components, modules, etc. It should be understood and appreciated that individual systems may include additional devices, components, modules, etc., and / or may not include all the devices, components, modules, etc. discussed in conjunction with the accompanying drawings. Furthermore, combinations of these approaches are also possible.
[0063] Furthermore, in the embodiments of this application, words such as "exemplarily" and "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design scheme described as an "example" in this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of the term "example" is intended to present concepts in a concrete manner. In the embodiments of this application, "of," "corresponding, relevant," and "corresponding" may sometimes be used interchangeably, and it should be noted that their intended meanings are consistent unless their distinction is emphasized.
[0064] "Instruction" can include direct instruction, indirect instruction, explicit instruction, and implicit instruction. When describing a certain instruction information to indicate A, it can be understood that the instruction information carries A, directly indicates A, or indirectly indicates A.
[0065] Figure 1 is a schematic diagram of the architecture of the communication system applied in the embodiments of this application. Figure 1 shows a schematic diagram of a possible, non-limiting system architecture. As shown in Figure 1, the communication system includes a radio access network (RAN) 100 and a core network (CN) 200. RAN 100 includes at least one RAN node (110a and 110b in Figure 1, collectively referred to as 110) and at least one terminal device (120a-120j in Figure 1, collectively referred to as 120). RAN 100 may also include other RAN nodes, such as wireless relay devices and / or wireless backhaul devices (not shown in Figure 1). Terminal device 120 is wirelessly connected to RAN node 110. RAN node 110 is wirelessly or wired connected to core network 200. The core network device in core network 200 and RAN node 110 in RAN 100 can be different physical devices, or they can be the same physical device integrating core network logical functions and radio access network logical functions.
[0066] RAN 100 can be a cellular system related to the 3rd Generation Partnership Project (3GPP), such as 4G, 5G mobile communication systems, or future-oriented evolution systems. RAN 100 can also be an open RAN (O-RAN or ORAN) or a cloud radio access network (CRAN). RAN 100 can also be a communication system that integrates two or more of the above systems.
[0067] RAN node 110, sometimes also referred to as access network equipment, RAN entity, or access node, is part of the communication system used to help terminal devices achieve wireless access. Multiple RAN nodes 110 in the communication system can be of the same type or different types. In some scenarios, the roles of RAN node 110 and terminal device 120 are relative. For example, network element 120i in Figure 1 can be a helicopter or drone, which can be configured as a mobile base station. For terminal devices 120j accessing RAN 100 through network element 120i, network element 120i is a base station; but for base station 110a, network element 120i is a terminal device. RAN node 110 and terminal device 120 are sometimes both referred to as communication devices. For example, network elements 110a and 110b in Figure 1 can be understood as communication devices with base station functions, and network elements 120a-120j can be understood as communication devices with terminal functions.
[0068] In one possible scenario, a RAN node can be a base station, an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP), a next-generation NodeB (gNB), or a base station in a future mobile communication system. A RAN node can be a macro base station (as shown in Figure 1, 110a), a micro base station or indoor station (as shown in Figure 1, 110b), a relay node or donor node, or a radio controller in a CRAN scenario. Optionally, a RAN node can also be a server, wearable device, vehicle, or in-vehicle equipment. For example, the access network equipment in vehicle-to-everything (V2X) technology can be a roadside unit (RSU).
[0069] In another possible scenario, multiple RAN nodes collaborate to assist the terminal in achieving wireless access, with different RAN nodes each implementing some of the base station's functions. For example, RAN nodes can be central units (CUs), distributed units (DUs), CU-control planes (CU-CPs), CU-user planes (CU-UPs), or radio units (RUs). CUs and DUs can be separate entities or included in the same network element, such as a baseband unit (BBU). RUs can be included in radio frequency equipment or radio frequency units, such as remote radio units (RRUs), active antenna units (AAUs), or remote radio heads (RRHs).
[0070] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an ORAN system, CU can also be called an open-CU (open-CU, O-CU), DU can also be called an open-DU (open-DU, O-DU), CU-CP can also be called an open-CU-CP (open-CU-CP, O-CU-CP), CU-UP can also be called an open-CU-UP (open-CU-UP, O-CU-UP), and RU can also be called an open-RU (open-RU, O-RU). For ease of description, the embodiments of this application use CU, CU-CP, CU-UP, DU, and RU as examples. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in the embodiments of this application can be implemented through software modules, hardware modules, or a combination of software modules and hardware modules.
[0071] Terminal equipment can also be called terminals, user equipment (UE), mobile stations, mobile terminals, etc. Terminal equipment can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IoT), virtual reality, augmented reality, point-of-sale (POS) machines, customer-premises equipment (CPE), light UE, reduced-capability UE (REDCAP UE), industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, etc. Terminals can be mobile phones, tablets, computers with wireless transceiver capabilities, wearable devices, vehicles, drones, helicopters, airplanes, ships, robots, robotic arms, smart home devices, etc.
[0072] Base stations and terminals can be fixed or mobile. They can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can be deployed on aircraft, balloons, and satellites. The embodiments of this application do not limit the application scenarios of the base stations and terminals.
[0073] The roles of base stations and terminals can be relative. For example, the helicopter or drone 120i in Figure 1 can be configured as a mobile base station. For terminals 120j that access the wireless access network 100 through 120i, terminal 120i is a base station; however, for base station 110a, 120i is a terminal, meaning that 110a and 120i communicate via a wireless air interface protocol. Of course, 110a and 120i can also communicate via a base station-to-base station interface protocol. In this case, relative to 110a, 120i is also a base station. Therefore, both base stations and terminals can be collectively referred to as communication devices. 110a and 110b in Figure 1 can be called communication devices with base station functions, and 120a-120j in Figure 1 can be called communication devices with terminal functions.
[0074] Communication between base stations and terminals, between base stations, and between terminals can be conducted using licensed spectrum, unlicensed spectrum, or both simultaneously. Communication can be conducted using spectrum below 6 GHz, spectrum above 6 GHz, or both simultaneously. The embodiments of this application do not limit the spectrum resources used for wireless communication.
[0075] In the embodiments of this application, the functions of the base station can be executed by modules (such as chips) within the base station, or by a control subsystem that includes base station functions. This control subsystem, including base station functions, can be a control center in the aforementioned application scenarios such as smart grids, industrial control, intelligent transportation, and smart cities. Similarly, the functions of the terminal can be executed by modules (such as chips or modems) within the terminal, or by a device that includes terminal functions.
[0076] In the communication system shown in Figure 1, after the network device is powered on, it periodically broadcasts a synchronization signal and a physical broadcast channel block (SSB) and SIB1 in the cell it controls. After receiving the SSB in the corresponding cell, the terminal device can further receive the SIB1 in that cell, and then initiate random access according to the configuration information of the physical random access channel (PRACH) indicated by the SIB1.
[0077] It is understandable that when a network device periodically broadcasts SIB1, it means that the network device needs to periodically consume a certain amount of energy to broadcast SIB1. To reduce the energy consumption of network devices, a feasible method is for the network device to stop periodically sending SIB1, and instead send SIB1 only when it receives a SIB1 request from a terminal device. Since this SIB1 is sent by the network device according to the needs of the terminal device, this type of SIB1 is referred to as on-demand SIB1 (OD-SIB1) in this embodiment.
[0078] Figure 2 illustrates the process of network devices transmitting SIB1 on demand. In this process, the first network device controls cell B, which is an energy-saving cell; therefore, the network device corresponding to cell B is the first network device. To reduce energy consumption in cell B, the first network device only periodically broadcasts SSB, not SIB1. The second network device controls cell A, which is a non-energy-saving cell; therefore, the network device corresponding to cell A is the second network device. The second network device periodically broadcasts both SSB and SIB1 in cell A.
[0079] For example, as shown in Figure 2, the process may include the following steps:
[0080] S201, the second network device sends a wake-up signal (WUS) configuration information to the terminal device. Correspondingly, the terminal device receives the WUS configuration information from the second network device.
[0081] It should be noted that before step S201, the first network device and the second network device have already exchanged WUS configuration information, that is, the first network device has sent the WUS configuration information to the second network device, and the second network device has obtained the WUS configuration information.
[0082] Considering that the first network device no longer periodically broadcasts SIB1, WUS configuration information can be sent to the terminal device via the second network device in this step. As an example, the second network device can send the WUS configuration information via broadcast, and the terminal device can receive the broadcast WUS configuration information. The WUS configuration information is used to configure information such as the time slot occupied by WUS on cell B, so that the terminal device can subsequently send WUS based on the WUS configuration information.
[0083] It should be noted that the WUS configuration information can be carried in a new SIB in cell A. Furthermore, the WUS configuration information can also be sent on demand; that is, the new SIB in cell A used to carry the WUS configuration information can also be sent as needed. This embodiment does not limit the method by which the second network device sends the WUS configuration information.
[0084] S202, the first network device sends an SSB to the terminal device. Correspondingly, the terminal device receives the SSB from the first network device.
[0085] For example, the first network device can send an SSB via broadcast, and correspondingly, the terminal device can receive the SSB broadcast by the first network device.
[0086] S203, the terminal device sends a PRACH to the first network device, the PRACH being used to request SIB1. Correspondingly, the first network device receives the PRACH from the terminal device.
[0087] In this step, when the terminal device needs SIB1, it can send a WUS to the first network device according to the WUS configuration information received in step S201. The WUS is used to request the first network device to send SIB1. Here, WUS can be understood as a PRACH signal, which is equivalent to the terminal device sending a PRACH to the first network device to request SIB1.
[0088] S204, the first network device sends a random access response to the terminal device. Correspondingly, the terminal device receives the random access response from the first network device.
[0089] In step S203, the terminal device sends a random access preamble on PRACH to indicate that the terminal device requests SIB1. Step S204 is optional; if resources permit, the first network device sends a random access response to the terminal device.
[0090] S205, the first network device sends a first SIB1 to the terminal device. Correspondingly, the terminal device receives the first SIB1 from the first network device.
[0091] To conserve energy in cell B, the first network device no longer broadcasts SIB1 periodically. Instead, it broadcasts SIB1 only upon receiving a SIB1 request, based on the needs of the terminal device. After receiving the PRACH from the terminal device in step S203, the first network device can determine that the terminal device needs to obtain SIB1. Therefore, the first network device sends the first SIB1 to the terminal device according to the PRACH.
[0092] For example, the first network device can broadcast the first SIB1, and the terminal device receives the first SIB1 broadcast by the first network device.
[0093] It is understandable that there are multiple terminal devices in cell B controlled by the first network device. Besides the terminal devices shown in Figure 2, other terminal devices in cell B may also send SIB1 requests to the first network device. Assuming that before step S203, that is, before the terminal device sends PRACH to the first network device, other terminal devices in cell B have already sent SIB1 requests to the first network device, then the first network device, after receiving the SIB1 request, will broadcast OD-SIB1.
[0094] In step S203, when the terminal device needs SIB1, it is unaware that the first network device is broadcasting OD-SIB1. Therefore, the terminal device does not receive the OD-SIB1 broadcast by the first network device, but instead expends energy to send a PRACH to the first network device to request SIB1, resulting in the terminal device failing to save energy. On the other hand, after receiving the PRACH from the terminal device, the first network device needs to broadcast OD-SIB1 again, causing the energy consumption of the first network device to increase.
[0095] To address the aforementioned technical problems, embodiments of this application provide a communication method and related apparatus. These embodiments enable a first network device to send an SIB1 via a broadcast SSB indication. If the terminal device determines that the first network device has sent an SIB1, it receives the SIB1 accordingly. Alternatively, if the terminal device determines that the first network device has not sent an SIB1 request, it sends an SIB1 request to the first network device to obtain the SIB1. This facilitates energy savings for both the terminal device and the first network device.
[0096] In the embodiments described below, the interaction between a terminal device and a network device is used as an example. It should be understood that the terminal device described above can be replaced by components configured in the terminal device (such as chips, chip systems, processors, etc.), or logical modules or software capable of implementing all or part of the functions of the terminal device; the network device described above can also be replaced by components configured in the network device (such as chips, chip systems, processors, etc.), or logical modules or software capable of implementing all or part of the functions of the network device.
[0097] Figure 3 is a flowchart illustrating a communication method according to an embodiment of this application. It is understood that Figure 3 is merely an example, and the communication method provided in this embodiment may include more or similar steps.
[0098] In this configuration, the first network device controls energy-saving cells, and the second network device controls non-energy-saving cells. Referring to step S201 in Figure 2, before step S301, the second network device sends WUS configuration information to the terminal device. Correspondingly, the terminal device receives the WUS configuration information from the second network device.
[0099] S301, the first network device sends a main information block (MIB) to the terminal device, which instructs the first network device to send SIB1 or not to send SIB1. Accordingly, the terminal device receives the MIB from the first network device.
[0100] As an example, a first network device broadcasts a Service Segmentation Block (SSB), and a terminal device receives the SSB broadcast by the first network device. It is understood that the SSB may include a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a physical broadcast channel (PBCH), where the PBCH carries a Meaningful Internet Block (MIB). This is equivalent to the first network device broadcasting the MIB, and the terminal device receiving the MIB broadcast by the first network device.
[0101] When a terminal device needs to obtain SIB1 (e.g., if SIB1 has expired), the terminal device can determine whether the MIB instructs the first network device to send SIB1 or not to send SIB1 by demodulating the PBCH, and obtain SIB1 according to the MIB instruction.
[0102] When the MIB instructs the first network device to send SIB1, as shown in step S302a of FIG3, the first network device sends the first SIB1 to the terminal device within a first time window. Accordingly, the terminal device receives the first SIB1 from the first network device within the first time window.
[0103] For example, the MIB can indicate "SIB1broadingcasting", meaning that the first network device is broadcasting SIB1. The first network device can broadcast the first SIB1 within a first time window, and correspondingly, the terminal device receives the first SIB1 broadcast by the first network device within the first time window. The "SIB1broadingcasting" and "SIB1notbroadingcasting" mentioned above, as signaling in the MIB indicating whether to send SIB1, can be reserved bits in the MIB or other indication fields in the MIB; this application embodiment does not limit this.
[0104] As described above, since the terminal device is unaware that the first network device is sending SIB1, it fails to receive SIB1 and instead sends an SIB1 request to the first network device. However, when the MIB indicates "SIB1 broadcasting," it is equivalent to the terminal device knowing that the first network device is sending SIB1. The first time window can be understood as the time window within which the terminal device is aware that the first network device is sending SIB1, and therefore the terminal device receives SIB1 within that first time period. Alternatively, the first time window can also be understood as the period within which the terminal device knows the first network device is sending SIB1, and therefore the terminal device receives SIB1 within that first time window.
[0105] Figure 4 is a schematic diagram of a first network device sending a first SIB1. In the diagram, the white matrix squares represent the SSBs broadcast by the first network device, and the black matrix squares represent the first SIB1s broadcast by the first network device. As an example, in Figure 4, the first network device broadcasts SSBs with a period of 20 milliseconds (ms), and the period of the first SIB1 is the same as that of the SSBs.
[0106] Taking the first SSB on the time axis from left to right as the first SSB in Figure 4, it can be seen from Figure 4 that the first network device broadcasts the first SIB1 during the time period corresponding to the sixth to thirteenth SSBs. The first time window includes the time period corresponding to the ninth to twelfth SSBs. That is, the time period during which the first network device broadcasts the first SIB1 covers the first time window, which is equivalent to the first network device sending the first SIB1 within the first time window.
[0107] It should be noted that the first network device controls the energy-saving cell, therefore, the first network device will only broadcast the first SIB1 upon receiving an SIB1 request. After the terminal device decodes the PBCH in the ninth SSB, the MIB instructs the first network device to send SIB1. In this case, the terminal device in the embodiment shown in Figure 3 did not subsequently request SIB1 from the first network device. Therefore, it can be understood that before the ninth SSB, there were other terminal devices in the cell controlled by the first network device that had already requested SIB1 from the first network device.
[0108] As shown in Figure 4, the first network device broadcasts the first SIB1 during the time period corresponding to the sixth SSB to the thirteenth SSB. The time when the first network device broadcasts the first SIB1 is earlier than the start time of the first time window. The first time window is the time window when the MIB indicates that the SIB1 is to be sent, or the first time window is the time window corresponding to the first network device sending the SIB1 as known to the terminal device. Therefore, the terminal device receives the first SIB1 within the first time window.
[0109] In some implementations, the first time window can be a preset time window. As an example, the first network device and the terminal device can agree on the length, start position, or end position of the first time window. The position of the first time window can be determined based on its start and end positions. Similarly, the position of the first time window can be determined based on its start and length. The position of the first time window can also be determined based on its end and length.
[0110] For example, taking Figure 4 as an example, the first network device and the terminal device can agree on a first time window length of 80ms. The starting position of the first time window is the time corresponding to the ninth SSB in Figure 4. Since the first network device sends SSBs with a period of 20ms, it can be determined that the first time window in Figure 4 includes the time period corresponding to the ninth to twelfth SSBs. Similarly, based on the starting and ending positions of the first time window, the ending position of the first time window, and the length of the first time window, the corresponding position of the first time window in Figure 4 can be determined. To avoid redundancy, this will not be elaborated further here.
[0111] Alternatively, the second network device may send first information to the terminal device, the first information indicating at least one of the following: the length of the first time window, the start position of the first time window, or the end position of the first time window. Accordingly, the terminal device receives the first information from the second network device.
[0112] It should be noted that both the first network device and the terminal device can obtain the position of the first time window. In the implementation method of the second network device sending the first information to the terminal device, the first network device and the second network device have already exchanged the first information in advance. That is, the first network device has sent the first information to the second network device, and the second network device can obtain the first information.
[0113] As an example, corresponding to step S201 in Figure 2, when the second network device sends WUS configuration information to the terminal device, the WUS configuration information may include the aforementioned first information. Alternatively, the second network device may also send the first information to the terminal device separately. By including the first information in the WUS configuration information, the overhead of the second network device can be saved.
[0114] Similar to the implementation of a preset time window, when the first information indicates the start and end positions of the first time window, the terminal device can determine the position of the first time window. When the first information indicates the length and start position of the first time window, or indicates the length and end position of the first time window, the terminal device can determine the position of the first time window.
[0115] It is understandable that the above implementation methods of indicating the first time window through the first information and the preset first time window can also be combined with each other. For example, the first network device and the terminal device can agree on the length of the first time window, and the first information can indicate the start position and / or end position of the first time window. Then, the terminal device can determine the position of the first time window based on the length of the first time window and the first information.
[0116] It should be noted that the first network device can broadcast SSBs via analog beams, and different analog beams correspond to different directions. This is equivalent to the first network device broadcasting SSBs in different directions. The first network device sending the first SIB1 to the terminal device within the first time window can be understood as the first network device broadcasting the first SIB1 in the direction corresponding to the first SSB within the first time window. The direction of the first SSB is the direction in which the terminal device is located, thus enabling the terminal device to receive the first SIB1 broadcast by the first network device within the first time window.
[0117] In one possible implementation, the first SIB1 may include the SIB1 corresponding to each of the multiple SSBs sent by the first network device within a first time window. Each SSB sent by the first network device corresponds to a different direction, and the first SIB1 includes the SIB1 corresponding to each of these multiple SSBs. This can be understood as the first network device broadcasting the first SIB1 in the directions corresponding to each SSB (i.e., on all SSBs) within the first time window, thereby enabling terminal devices in each direction corresponding to the multiple SSBs to receive the first SIB1 broadcast by the first network device.
[0118] Accordingly, in this implementation, the first SIB1 received by the terminal device within the first time window corresponds to the first SSB, and the first SSB can be any SSB from the first network device. Here, "first SIB1 corresponds to first SSB" indicates that the first SIB1 is the first SIB1 broadcast by the first network device in the direction corresponding to the first SSB. In this embodiment, the direction of the terminal device is not limited; therefore, the first SSB can be any SSB from the first network device. It can be understood that within the first time window, SIB1 corresponding to all SSBs has been sent, meaning the first network device has sent SIB1 in all SSB directions. The terminal device can receive the SIB1 corresponding to any SSB within the first time window. All SSBs mentioned above refer to the SSBs indicated for transmission in the WUS configuration information. For example, there are a total of 16 SSBs, namely SSB 0 to SSB 15. If the WUS configuration information indicates that SSB 0, SSB 2, SSB 3, and SSB 4 have been sent, then all SSBs here refer to SSB 0, SSB 2, SSB 3, and SSB 4.
[0119] If the MIB instructs the first network device not to send SIB1, as shown in steps S302b and S302c of FIG3, in step S302b, the terminal device sends a PRACH to the first network device, the PRACH being used to request SIB1. Accordingly, the first network device receives the PRACH from the terminal device.
[0120] For example, the MIB can indicate "SIB1 not broadcasting," meaning that the first network device is not broadcasting SIB1. When a terminal device needs to obtain SIB1, and the MIB indicates that the first network device has not sent SIB1, the terminal device can clearly know that the first network device has not sent SIB1. Corresponding to step S203 in Figure 2, the terminal device sends a WUS to the first network device, which requests the first network device to send SIB1.
[0121] In step S302c, the first network device sends the first SIB1 to the terminal device within a second time window. Correspondingly, the terminal device receives the first SIB1 from the first network device within the second time window.
[0122] As an example, the first network device may broadcast the first SIB1 within a second time window, and correspondingly, the terminal device may receive the first SIB1 from the first network device within the second time window.
[0123] Taking the aforementioned schematic diagram in Figure 4 as an example, after decoding the PBCH in the ninth SSB, the MIB instructs the first network device to send SIB1. In this case, it can be understood that the terminal device in the embodiment shown in Figure 3 did not subsequently request SIB1 from the first network device. As shown in Figure 4, assuming that after decoding the PBCH in the first SSB, the MIB instructs the first network device not to send SIB1, this is equivalent to the terminal device in the embodiment shown in Figure 3 subsequently sending a PRACH to the first network device to request SIB1.
[0124] Understandably, the first network device broadcasts the first SIB1 within the time period corresponding to the sixth to thirteenth SSBs, as shown in Figure 4, based on the PRACH from the terminal device. This is equivalent to the second time window including the time period corresponding to the sixth to thirteenth SSBs. Accordingly, after sending the PRACH to the first network device, the terminal device receives the first SIB1 from the first network device within the second time window.
[0125] In some implementations, the length of the second time window is a preset length. Alternatively, the second network device can send second information to the terminal device, indicating the length of the second time window. Accordingly, the terminal device receives the second information from the second network device.
[0126] It should be noted that both the first network device and the terminal device can obtain the length of the second time window. In the implementation where the second network device sends the second information to the terminal device, the first and second network devices have already exchanged the second information in advance; that is, the first network device has already sent the second information to the second network device, and the second network device can obtain the second information. As an example, corresponding to step S201 in Figure 2, when the second network device sends WUS configuration information to the terminal device, this WUS configuration information may include the aforementioned second information. Alternatively, the second network device may also send the second information to the terminal device independently.
[0127] For example, taking Figure 4 as an example, the first network device and the terminal device can agree on a second time window length of 160ms. Alternatively, when the second network device sends WUS configuration information to the terminal device, it can indicate in the WUS configuration information that the second time window length is 160ms.
[0128] In some implementations, the length of the first time window is less than or equal to the length of the second time window. The first time window can be understood as the transmission time window corresponding to the first SIB1 when the MIB instructs the first network device to transmit SIB1. Alternatively, the first time window can also be understood as the time window during which there is no SIB1 transmission when the MIB instructs the first network device not to transmit SIB1; that is, the first network device does not transmit SIB1 within the first time window. The second time window can be understood as the time window used to receive the first SIB1 after the terminal device sends a PRACH to the first network device; that is, the time window during which the first network device transmits the first SIB1 after receiving the PRACH.
[0129] If the length of the first time window is greater than the length of the second time window, it may result in the first network device not sending the first SIB1 for a certain period of time, but the terminal device still receiving the first SIB1, thus increasing the power consumption of the terminal device. In this implementation, when the length of the first time window is less than or equal to the length of the second time window, the terminal device can continuously receive the first SIB1 within the first time window, thereby saving power consumption.
[0130] As shown in Figure 4 above, the starting position of the second time window is before the starting position of the first time window, and the ending position of the second time window is after the ending position of the first time window. In other words, the second time window can completely cover the first time window.
[0131] In some implementations, the end position of the second time window is the same as the end position of the first time window. This can be understood as the end position of the second time window being the same as the end position of any first time window. The first time window can be understood as a recurring time window; for example, starting from radio frame 0, every 160ms constitutes a first time window. A radio frame is 10ms long, therefore radio frames 0 to 15 form a first time window, while radio frames 16 to 31 form another first time window. When the MIB instructs the first network device to send SIB1, the terminal device receives the first SIB1 within the first time window. Here, the first time window refers to the first time window that includes the SSB carrying the MIB. That is, the first time window contains the SSB, and the MIB in the SSB instructs the first network device to send SIB1.
[0132] Figure 5 is another schematic diagram of the first network device sending the first SIB1. In this diagram, the white matrix squares represent the SSBs broadcast by the first network device, and the black matrix squares represent the first SIB1s broadcast by the first network device. For example, similar to Figure 4, in Figure 5 (A) and (B), the first network device broadcasts SSBs with a period of 20ms, and the period of the first SIB1 is the same as that of the SSBs.
[0133] Taking the first SSB on the time axis from left to right as the first SSB in Figure 5 (A), it can be seen from Figure 5 (A) that the first network device broadcasts the first SIB1 during the time period corresponding to the sixth SSB to the sixteenth SSB. That is, the second time window includes the time period corresponding to the sixth SSB to the sixteenth SSB, and the end position of the second time window is the time corresponding to the sixteenth SSB.
[0134] The first time window includes the time period corresponding to the ninth SSB to the sixteenth SSB. The end position of the first time window is the time corresponding to the sixteenth SSB. The end position of the first time window is the same as the end position of the second time window.
[0135] It should be noted that, unlike the first time window in Figure 4, the first time window shown in Figure 5(A) has a length of 160ms. Assuming the first network device broadcasts the first SIB1 according to the length of the second time window shown in Figure 4, as indicated by the dotted line in Figure 5, the second time window includes the time period corresponding to the sixth SSB to the thirteenth SSB. As explained above, the length of the first time window is equivalent to the duration known to the terminal device as the first network device sending SIB1. If the second time window includes the time period corresponding to the sixth SSB to the thirteenth SSB, it means that during the time period corresponding to the fourteenth SSB to the sixteenth SSB, the first network device no longer sends the first SIB1, but the terminal device believes that the first network device is still sending the first SIB1 during that time period, causing the terminal device to continuously receive the first SIB1 during that time period, resulting in wasted energy for the terminal device.
[0136] Therefore, compared to Figure 4, it can be understood that in Figure 5(A), the first network device extends the length of the second time window for broadcasting the first SIB1 until the end position of the second time window is the same as the end position of the first time window. This is equivalent to the terminal device considering that the first network device also sent the first SIB1 during the time period between the end position of the second time window and the end position of the first time window, even if the end position of the second time window is different from the end position of the first time window. When the UE sends a PRACH request for SIB1 and receives the first SIB1 within the second time window, the first time window includes the end position of the second time window; that is, the end position of the second time window is located within the first time window.
[0137] Alternatively, as shown in Figure 5(B), the first SSB on the timeline from left to right is taken as the first SSB in Figure 5(A). The first network device broadcasts the first SIB1 during the time period corresponding to the ninth to the sixteenth SSB. That is, the second time window includes the time period corresponding to the ninth to the sixteenth SSB, and the end position of the second time window is the time corresponding to the sixteenth SSB. The first time window also includes the time period corresponding to the ninth to the sixteenth SSB, and the end position of the first time window is the same as the end position of the second time window.
[0138] As shown in Figure 5(B), compared to Figure 4, when the first network device broadcasts the first SIB1 in the second time window, it directly aligns the end position of the second time window with the end position of the first time window.
[0139] In this implementation, the end position of the second time window is the same as the end position of the first time window, which allows the terminal device to continuously receive the first SIB1 within the first time window, thus avoiding energy waste of the terminal device and saving energy.
[0140] As one possible implementation, if the length of the second time window is greater than or equal to the first threshold, the MIB indicates whether to send SIB1 or not. Alternatively, it can be understood that the MIB only contains the indication to send or not send SIB1 if the length of the second time window is greater than or equal to the first threshold. That is, if the length of the second time window is less than the first threshold, the MIB does not contain the indication to send or not send SIB1.
[0141] Taking Figures 4 and 5 as examples, the first network device broadcasts the SSB with a period of 20ms. Therefore, when the first network device broadcasts the first SIB1 within the second time window, the terminal device can decode the PBCH if the length of the second time window is greater than or equal to 20ms, allowing the MIB to switch between instructing the first network device to send SIB1 or not to send SIB1. If the length of the second time window is less than 20ms, the MIB cannot switch between the two indication states, which is equivalent to the first threshold being 20ms in the examples shown in Figures 4 and 5.
[0142] In this implementation, the first threshold can be a preset threshold, determined through a protocol or a method agreed upon between the first network device and the terminal device. Alternatively, the second network device can send third information to the terminal device, indicating the first threshold. Accordingly, the terminal device receives the third information from the second network device.
[0143] Similar to the first and second information mentioned above, both the first network device and the terminal device can obtain the first threshold. However, in the implementation where the second network device sends the third information to the terminal device, the first and second network devices have already exchanged the third information in advance; that is, the first network device has already sent the third information to the second network device, and the second network device can obtain the third information. As an example, corresponding to step S201 in Figure 2, when the second network device sends WUS configuration information to the terminal device, this WUS configuration information may include the aforementioned third information. Alternatively, the second network device may also send the third information to the terminal device independently.
[0144] It should be noted that the first, second, and third information mentioned above can all be carried through WUS configuration information, or can be sent separately by the second network device to the terminal device. This application embodiment does not limit this.
[0145] In this embodiment, the first network device can indicate whether to send SIB1 through MIB. If the terminal device determines that the first network device has sent SIB1, it can receive SIB1 accordingly. Alternatively, if the terminal device determines that the first network device has not sent a request for SIB1, it can send a request for SIB1 to the first network device to obtain SIB1. This is beneficial for both the terminal device and the first network device to save energy.
[0146] In the embodiment shown in Figure 3 above, the terminal device needs to decode the PBCH and, according to the MIB, instruct the first network device whether to send SIB1 to achieve the subsequent operation of obtaining SIB1. In some implementations, the communication method provided in this application embodiment can obtain SIB1 without decoding the PBCH.
[0147] Figure 6 is a flowchart illustrating a communication method according to another embodiment of this application. It is understood that Figure 6 is merely an example, and the communication method provided in this embodiment may include more or similar steps.
[0148] In this configuration, the first network device controls energy-saving cells, and the second network device controls non-energy-saving cells; details can be found in the preceding description and will not be repeated here. Referring to step S201 in Figure 2, before step S601, the second network device sends WUS configuration information to the terminal device. Correspondingly, the terminal device receives the WUS configuration information from the second network device. Furthermore, the first network device sends an SSB to the terminal device. Correspondingly, the terminal device receives the SSB from the first network device.
[0149] S601, the terminal device detects the first physical downlink control channel (PDCCH) within the fourth time window. The first PDCCH includes the PDCCH used for scheduling SIB1.
[0150] When a terminal device needs to obtain SIB1 (e.g., SIB1 has expired), the terminal device first performs a blind check of the first PDCCH within the fourth time window. For example, assuming the first network device broadcasts the first SIB1, the first network device can schedule the first physical downlink shared channel (PDSCH) using a PDCCH scrambled with the system information radio network temporary identifier (SI-RNTI). This first PDSCH carries the first SIB1; that is, the SI-RNTI scrambled PDCCH can be used to schedule SIB1. In this step, the first PDCCH may include a SI-RNTI scrambled PDCCH, which is equivalent to the PDCCH used to schedule SIB1.
[0151] In some implementations, the length of the fourth time window is the same as the duration of the SIB1 transmission period, i.e., the length of the fourth time window can be 160ms. It can be understood that when the first network device receives an SIB1 request, it broadcasts the first SIB1 according to the SIB1 transmission period. That is, the terminal device blindly detects SIB1 according to the SIB1 transmission period, and can detect the first PDCCH used for scheduling SIB1 within the duration of the SIB1 transmission period. The fact that the length of the fourth time window is the same as the duration of the SIB1 transmission period allows the terminal device to detect the first PDCCH used for scheduling SIB1 in the shortest possible time, which helps save energy for the terminal device.
[0152] If the terminal device detects the first PDCCH within the fourth time window, as shown in step S602a of Figure 6, the first network device sends the first SIB1 to the terminal device. Accordingly, the terminal device receives the first SIB1 based on the first PDCCH.
[0153] It is understandable that the first PDCHH includes the PDCCH used to schedule SIB1. When the terminal device detects the first PDCCH within the fourth time window, it is equivalent to the first network device sending the first SIB1. Therefore, the terminal device can receive the first SIB1 according to the first PDCCH.
[0154] In some implementations, the first PDCCH may include a PDCCH scrambled with SI-RNTI and a PDCCH scrambled with random access radio network temporary identifier (RA-RNTI).
[0155] In this configuration, the SI-RNTI scrambled PDCCH is used to schedule SIB1. When a terminal device detects the SI-RNTI scrambled PDCCH, it can schedule SIB1 according to the first PDSCH indicated by the SI-RNTI scrambled PDCCH. However, when a terminal device detects the RA-RNTI scrambled PDCCH, although RA-RNTI cannot be used to schedule SIB1, the RA-RNTI scrambled PDCCH is the PDCCH sent by the first network device during random access. If the terminal device detects RA-RNTI, it can be understood that another terminal device in the energy-saving cell controlled by the first network device is sending an SIB1 request to the first network device. Accordingly, the first network device broadcasts the first SIB1. That is, after detecting the RA-RNTI scrambled PDCCH, the terminal device can determine that the first network device has already sent the first SIB1, and then the terminal device continues to detect the SI-RNTI scrambled PDCCH and receives SIB1 according to it. Therefore, when the terminal device detects the RA-RNTI scrambled PDCCH, it can continue to receive the first SIB1 according to the SI-RNTI scrambled PDCCH, which is equivalent to the terminal device receiving the first SIB1 according to the first PDCCH.
[0156] In some other possible implementations, the first PDCCH may include a SI-RNTI scrambled PDCCH, and the second PDCCH may include a RA-RNTI scrambled PDCCH. The terminal device can detect both the first and second PDCCH within the fourth time window.
[0157] If the terminal device does not detect the first PDCCH within the fourth time window, as shown in steps S602b and S602c of Figure 6, in step S602b, the terminal device sends a PRACH to the first network device. The PRACH is used to request SIB1. Correspondingly, the first network device receives the PRACH from the terminal device.
[0158] If the terminal device needs to obtain SIB1 and no first PDCCH is detected within the fourth time window, the terminal device can determine that the first network device has not sent SIB1. Corresponding to step S203 in Figure 2, the terminal device sends a WUS to the first network device, which is used to request the first network device to send SIB1.
[0159] In step S602c, the first network device sends a first SIB1 to the terminal device. Correspondingly, the terminal device receives the first SIB1 from the first network device. As an example, the first network device broadcasts the first SIB1 according to the PRACH used to request the SIB1, and the terminal device receives the first SIB1 from the first network device.
[0160] Figure 7 is another schematic diagram of the first network device sending the first SIB1. In the figure, the shaded matrix squares represent the first PDCCH sent by the first network device, and the black matrix squares represent the first SIB1 broadcast by the first network device.
[0161] As shown in Figure 7, when the first terminal device needs to acquire SIB1, it detects the first PDCCH within the fourth time window. As shown in Figure 7, the first terminal device does not detect the first PDCCH within the fourth time window; therefore, the first terminal device sends a PRACH to the first network device to request SIB1. Correspondingly, after receiving the PRACH, the first network device broadcasts the first SIB1, and the terminal device can receive the first SIB1 broadcast by the first network device.
[0162] As shown in Figure 7, after the first terminal device sends a PRACH to the first network device, the second terminal device needs to obtain SIB1. This second terminal device can be understood as other terminal devices in the energy-saving cell controlled by the first network device, distinct from the first terminal device. Since the first network device broadcasts the first SIB1 based on the PRACH from the first terminal device, the second terminal device can detect the first PDCCH within the fourth time window, and thus receive the first SIB1 based on the first PDCCH.
[0163] It is understood that the first PDCCH detected by the second terminal device may include a SI-RNTI scrambled PDCCH broadcast by the first network device, which is used to schedule the first SIB1. The first PDCCH detected by the second terminal device may also include a RA-RNTI scrambled PDCCH broadcast by the first network device, which is equivalent to the PRACH sent by the first network device to the first terminal device during the random access process of the first terminal device. When the second terminal device detects the RA-RNTI scrambled PDCCH within the fourth time window, it can determine from this PDCCH that the first network device will broadcast SIB1 within the energy-saving cell it controls, and thus receive the first SIB1 based on the first PDCCH.
[0164] The first terminal device in Figure 7 above corresponds to the terminal device in the embodiment shown in Figure 6 where the first PDCCH is not detected in the fourth time window, and the second terminal device corresponds to the terminal device in the embodiment shown in Figure 6 where the first PDCCH is detected in the fourth time window.
[0165] As one possible implementation, the fourth time window can be a periodic time window, during which PRACH cannot be sent. Referring to Figure 7, the first network device broadcasts the first SIB1 request based on the first terminal device's SIB1 request. The second terminal device can detect the first PDCCH used to schedule the first SIB1 within the fourth time window and thus receive the first SIB1 based on the first PDCCH. If the first network device broadcasts the first PDCCH only after the fourth time window has ended, the second terminal device will not detect the first PDCCH within the fourth time window. Therefore, even if the first network device broadcasts the first SIB1, the second terminal device will still send a PRACH to the first network device to request the SIB1. Consequently, the first network device needs to receive a PRACH while broadcasting the first SIB1, leading to increased power consumption for the first network device.
[0166] In this implementation, the terminal device cannot send PRACH during the fourth time window, and the first network device does not receive PRACH during the fourth time window. That is, the first network device no longer detects PRACH during the fourth time window, thereby saving the energy consumed by the first network device for detecting PRACH during the fourth time window.
[0167] In some implementations, the second network device may send fourth information to the terminal device, the fourth information indicating at least one of the following: the period of the fourth time window, the length of the fourth time window, the start position of the fourth time window, or the end position of the fourth time window.
[0168] It should be noted that both the first network device and the terminal device can obtain the position of the fourth time window. However, in the implementation where the second network device sends the fourth information to the terminal device, the first network device and the second network device have already exchanged the fourth information in advance. For example, corresponding to step S201 in Figure 2, when the second network device sends WUS configuration information to the terminal device, the WUS configuration information may include the aforementioned fourth information. Alternatively, the second network device may also send the fourth information to the terminal device independently.
[0169] When the fourth information indicates the start and end positions of the fourth time window, the terminal device can determine the position of the fourth time window. When the fourth information indicates the length and start position of the fourth time window, or indicates the length and end position of the fourth time window, the terminal device can determine the position of the fourth time window.
[0170] It is understandable that any one of the following in the fourth information above—the period of the fourth time window, the length of the fourth time window, the start position of the fourth time window, or the end position of the fourth time window—can also be obtained through a preset method. The preset method and the fourth information can be combined with each other. For example, the first network device and the terminal device can agree on the length of the fourth time window, and the fourth information can indicate the start position and / or end position of the fourth time window. Then, the terminal device can determine the position of the fourth time window based on the length of the fourth time window and the fourth information.
[0171] In this embodiment, the terminal device blindly checks the first PDCCH within the fourth time window, which can be understood as an implementation method for the terminal device to determine whether the first network device has sent SIB1. Once the terminal device determines whether the first network device has sent SIB1, it can then proceed with the subsequent acquisition of SIB1, which helps avoid wasting energy on the terminal device and saves energy for both the terminal device and the first network device.
[0172] Figures 8 and 9 are schematic diagrams of possible communication devices provided in embodiments of this application. These communication devices can be used to implement the functions of terminal devices or network devices in the above method embodiments, and thus can also achieve the beneficial effects of the above method embodiments. In the embodiments of this application, the communication device can be the terminal device or the first network device in the method embodiments shown in Figure 3 or Figure 6, or it can be a component (such as a chip, chip system, processor, etc.) configured in the terminal device or the first network device, or it can be a logic module or software capable of implementing some or all of the functions of the terminal device or the first network device.
[0173] Figure 8 is a schematic diagram of the structure of a communication device provided in an embodiment of this application. As shown in Figure 8, the communication device 800 includes a processing module 810 and a transceiver module 820.
[0174] The transceiver module 820 can implement corresponding communication functions and can also be referred to as an input / output interface or communication unit. The processing module 810 can be used to perform processing operations. It should be understood that if the device 800 is a component configured in a network device or terminal device, such as a chip, the transceiver module 820 can be an input / output interface.
[0175] Optionally, the transceiver module 820 may include a sending module and a receiving module. The sending module is used to perform the sending operation of the first network device or terminal device in Figure 3 or Figure 6, and the receiving module is used to perform the receiving operation of the first network device or terminal device in Figure 3 or Figure 6.
[0176] It should be understood that when the device 800 is a component configured in a network device or terminal device, such as a chip, the transmitting module can be an output interface, and the transmitting operation involved in the embodiments of this application can be performed by the output interface; the receiving module can be an input interface, and the receiving operation involved in the embodiments of this application can be performed by the input interface.
[0177] Optionally, the device 800 may further include a storage module for storing instructions and / or data, and the processing module 810 may read the instructions and / or data from the storage module to enable the device to implement the method embodiment shown in FIG3 or FIG6.
[0178] In one possible design, the device 800 can be used to implement the functions of the terminal device in the method embodiment shown in FIG3 or FIG6. Alternatively, the device 800 can include a unit for implementing any function or operation of the terminal device in the method embodiment shown in FIG3 or FIG6. This unit can be implemented in whole or in part by software, hardware, firmware or any combination thereof.
[0179] When device 800 is used to implement the functions of the terminal device in the method embodiment shown in FIG3 or FIG6, transceiver module 820 (specifically, receiving module) can be used to execute step S301 in FIG3, receiving MIB from the first network device, the MIB instructing the first network device to send SIB1 or not to send SIB1, and can also be used to execute step S302a in FIG3, receiving the first SIB1 from the first network device in a first time window, or to execute step S302c in FIG3, receiving the second SIB1 from the first network device in a second time window; transceiver module 820 (specifically, sending module) can be used to execute step S302b in FIG3, sending PRACH to the first network device, the PRACH being used to request SIB1.
[0180] In another possible design, the device 800 can be used to implement the function of the first network device in the method embodiment shown in FIG3 or FIG6. Alternatively, the device 800 can include a unit for implementing any function or operation of the first network device in the method embodiment shown in FIG3 or FIG6. This unit can be implemented in whole or in part by software, hardware, firmware or any combination thereof.
[0181] When device 800 is used to implement the function of the first network device in the method embodiment shown in FIG3 or FIG6, transceiver module 820 (specifically, a sending module) can be used to execute step S301 in FIG3, sending MIB to terminal device, MIB instructing the first network device to send SIB1 or not send SIB1, and can also be used to execute step S302a in FIG3, sending the first SIB1 to terminal device in a first time window, or to execute step S302c in FIG3, sending the first SIB1 to terminal device in a second time window; transceiver module 820 (specifically, a receiving module) can be used to execute step S302b in FIG3, receiving PRACH from terminal device, which is used to request SIB1.
[0182] A more detailed description of the above-mentioned processing module 810 and transceiver module 820 can be obtained directly from the relevant descriptions in the method embodiments shown in Figure 3 or Figure 6, and will not be repeated here.
[0183] It should be noted that the transceiver module can also be called a transceiver unit, transceiver, transceiver machine, or transceiver device, etc. The processing module can also be called a processor, processing board, processing unit, or processing device, etc. Optionally, the transceiver module is used to perform the sending and receiving operations on the terminal device or network device side in the above method. The device in the communication module used to implement the receiving function can be considered as the receiving module, and the device in the communication module used to implement the sending function can be considered as the sending module; that is, the transceiver module includes both a receiving module and a sending module.
[0184] In another possible design, the aforementioned transceiver module and / or processing module can be implemented using virtual modules. For example, the processing module can be implemented using software functional modules or virtual devices, and the transceiver module can also be implemented using software functional modules or virtual devices. In another possible design, the processing module or transceiver module can also be implemented using physical devices. For example, if the device is implemented using a chip / chip circuit, the transceiver module can be an input / output circuit and / or a communication interface, performing input operations (corresponding to the aforementioned receiving operation) and output operations (corresponding to the aforementioned sending operation); the processing module is an integrated processor, microprocessor, or integrated circuit.
[0185] It should be understood that the module division in the embodiments of this application is illustrative and only represents a logical functional division. In actual implementation, there may be other division methods. Furthermore, the functional modules in the various embodiments of this application can be integrated into a single processor, exist as separate physical entities, or be integrated into a single module. The integrated modules described above can be implemented in hardware or as software functional modules.
[0186] Figure 9 is a schematic diagram of a communication device provided in another embodiment of this application. This device 900 can be a chip system, or it can be a device configured with a chip system to implement the above-described method embodiments. In this embodiment, the chip system can be composed of chips, or it can include chips and other discrete devices.
[0187] As shown in Figure 9, device 900 can be implemented using a processing system including one or more processors 901. Processor 901 includes microprocessors, microcontrollers, digital signal processors, field-programmable gate arrays, graphics processors, programmable logic devices, state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to various functions. That is, the processor used in device 900 can be used to implement any one or more of the embodiments described above.
[0188] The processing system in device 900 can be implemented using a bus architecture, typically represented by bus 902. Bus 902 may include any number of interconnect buses and bridges, depending on the specific application and overall design constraints of the processing system. The bus communicatively couples various circuits together, including one or more processors 901 (typically represented by a processor), memory 903, and computer-readable medium 904 (typically represented by a computer-readable medium). Bus 902 may also link various other circuits, such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and will therefore not be described further. Bus interface 905 provides an interface between bus 902 and transceivers, and between bus 902 and interfaces. Bus interface 905 may use, but is not limited to, transceivers to enable communication between device 900 and other devices or apparatuses.
[0189] A transceiver provides a communication interface or means for communicating with various other devices via a wireless transmission medium. The transceiver may be coupled to an antenna array, and the transceiver and antenna array may be used together for communication with a corresponding network type. At least one interface (e.g., a network interface and / or a user interface) provides a communication interface or means for communication via an internal bus or via an external transmission medium.
[0190] Processor 901 is responsible for managing bus 902 and general processing, including executing software stored on computer-readable medium 904. When executed by processor 901, the software causes the processing system to perform the various functions described below for any particular device.
[0191] The processor 901, memory 903, and computer-readable medium 904 can perform the following functions: encoding, decoding, rate matching, rate matching removal, scrambling, descrambling, modulation, demodulation, layer mapping, fast Fourier transform, inverse fast Fourier transform, inverse discrete Fourier transform, precoding, resource element (RE) mapping, channel equalization, RE demapping, digital beamforming (BF), adding cyclic prefix (CP), removing CP, etc.
[0192] The steps of the method disclosed in the embodiments of this application can be directly manifested as being executed by a hardware decoding processor, or being executed by a combination of hardware and software modules in the decoding processor. The software modules can be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art.
[0193] This application also provides a computer-readable storage medium storing computer instructions, which, when executed by a processor, implement the steps of the methods described above.
[0194] This application also provides a computer program product, including computer instructions that, when executed by a processor, implement the various steps in the methods described above.
[0195] This application also provides a communication system, which includes the aforementioned terminal device, first network device, and second network device.
[0196] It should be noted that the modules or components shown in the above embodiments can be one or more integrated circuits configured to implement the above methods, such as one or more application-specific integrated circuits (ASICs), one or more microprocessors, or one or more field-programmable gate arrays (FPGAs). Furthermore, when a module is implemented by a processing element calling program code, the processing element can be a general-purpose processor, such as a central processing unit (CPU) or other processor capable of calling program code, such as a controller. Additionally, these modules can be integrated together and implemented as a System-on-a-Chip (SoC).
[0197] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, software modules, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. A 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 flow or function according to the embodiments of this application is 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, 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, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state disk (SSD)).
[0198] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the disclosure herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and intent of this application are indicated by the following claims.
[0199] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.
Claims
1. A communication method, characterized in that, The method includes: Receive the master information block MIB, which indicates whether to send system message block SIB1 or not to send SIB1; If the MIB indicates that SIB1 should be sent, the first SIB1 should be received within the first time window; or, If the MIB indicates that SIB1 is not to be sent, a Physical Random Access Channel (PRACH) is sent, and the first SIB1 is received within a second time window, wherein the PRACH is used to request SIB1.
2. The method according to claim 1, characterized in that, The length of the first time window is less than or equal to the length of the second time window.
3. The method according to claim 2, characterized in that, The first time window is a preset time window; or, The method further includes: Receive first information from a second network device, the first information indicating at least one of the following: the length of the first time window, the start position of the first time window, or the end position of the first time window.
4. The method according to any one of claims 1 to 3, characterized in that, The length of the second time window is a preset length; or, The method further includes: Receive second information from a second network device, the second information indicating the length of the second time window.
5. The method according to any one of claims 1 to 4, characterized in that, The MIB instruction to send system message block SIB1 or not send SIB1 includes: If the length of the second time window is greater than or equal to the first threshold, the MIB indicates whether to send SIB1 or not. Wherein, the first threshold is a preset threshold; or, The method further includes: Receive third information from a second network device, the third information indicating the first threshold.
6. The method according to any one of claims 1 to 5, characterized in that, The end position of the second time window is the same as the end position of the first time window.
7. The method according to any one of claims 1 to 6, characterized in that, The first SIB1 corresponds to the first synchronization signal and the physical broadcast channel block (SSB), and the first SSB is any SSB from the first network device.
8. A communication method, characterized in that, The method includes: Send a MIB, which indicates whether to send SIB1 or not; If the MIB indicates that SIB1 should be sent, then the first SIB1 should be sent within the first time window; or, If the MIB indicates that SIB1 is not sent, a PRACH is received and the first SIB1 is sent within a second time window, the PRACH being used to request SIB1.
9. The method according to claim 8, characterized in that, The length of the first time window is less than or equal to the length of the second time window.
10. The method according to claim 8 or 9, characterized in that, The MIB instruction to send SIB1 or not send SIB1 includes: If the length of the second time window is greater than or equal to the first threshold, the MIB indicates whether to send SIB1 or not, where the first threshold is a preset threshold.
11. The method according to any one of claims 8 to 10, characterized in that, The first SIB1 includes SIB1 corresponding to each of the multiple SSBs sent by the first network device within the first time window.
12. The method according to any one of claims 8 to 11, characterized in that, The end position of the second time window is the same as the end position of the first time window.
13. A communication method, characterized in that, The method includes: The first physical downlink control channel (PDCCH) is detected within the fourth time window. The first PDCCH includes a PDCCH for scheduling SIB1. If the first PDCCH is detected within the fourth time window, the first SIB1 is received according to the first PDCCH; or, If the first PDCCH is not detected within the fourth time window, a PRACH is sent and the first SIB1 is received, wherein the PRACH is used to request SIB1.
14. The method according to claim 13, characterized in that, The first PDCCH includes the PDCCH scrambled with SI-RNTI and the PDCCH scrambled with Random Access Radio Network Temporary Identifier (RA-RANTI).
15. The method according to claim 13 or 14, characterized in that, The length of the fourth time window is the same as the duration of the SIB1 transmission period.
16. The method according to claim 13 or 14, characterized in that, The fourth time window is a periodic time window, during which PRACH cannot be sent.
17. The method according to claim 16, characterized in that, The method further includes: Receive fourth information from the second network device, the fourth information indicating at least one of the following: the period of the fourth time window, the length of the fourth time window, the start position of the fourth time window, or the end position of the fourth time window.
18. A communication device, characterized in that, The communication device includes a module for implementing the communication method as described in any one of claims 1 to 17.
19. A communication device, characterized in that, include: Processor, the processor being coupled to memory; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory, causing the communication device to perform the communication method as described in any one of claims 1 to 17.
20. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the communication method as described in any one of claims 1 to 17.
21. A computer program product, characterized in that, It includes a computer program that, when executed by a processor, implements the communication method as described in any one of claims 1 to 17.