A communication method, a communication device, and a communication system

Abstract

The application provides a communication method, a communication device and a communication system, relates to the technical field of communication, and is suitable for a network energy saving scene. In the method, when a first cell supports a network energy saving mode, a master information block received by a terminal device in the first cell carries a first index value, the first index value is used to determine first WUS configuration information from at least one set of preconfigured WUS configuration information. The terminal device receives an OD-SIB1 sent by a network device in the first cell after the terminal device sends a WUS to the network device according to the first WUS configuration information, so that the network device is woken up to send the OD-SIB1 to the terminal device. Thus, not only the data corresponding to the WUS configuration information sent by the network device to the terminal device is avoided, but also the problem that the terminal device depends on other cells to send the WUS is avoided, and the power consumption of the network device and the terminal device is saved by receiving the SIB1 on demand, and the signaling overhead is reduced.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a communication method, communication device and communication system. Background Technology

[0002] In communication systems, network devices typically broadcast System Information Block 1 (SIB1) periodically, allowing terminal devices to camp on the corresponding cell. To reduce network device power consumption and achieve energy saving, network devices corresponding to Network Energy Saving (NES) cells are currently allowed to stop periodically broadcasting SIB1. However, when network devices for NES cells do not broadcast SIB1, how a terminal device obtains the SIB1 of that NES cell when it needs to camp on that cell remains a problem to be solved. Summary of the Invention

[0003] This application provides a communication method, communication device, and communication system. After determining the WUS configuration information based on the index value of the wake-up signal (WUS) configuration information carried in the main information block, the terminal device sends the WUS to the network device according to the WUS configuration information to wake up the network device to send on-demand system information block 1 (OD-SIB1) to the terminal device. This not only saves the power consumption of the network device and the terminal device, but also reduces signaling overhead by only carrying the index value of the WUS configuration information.

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

[0005] The method includes: a terminal device receiving a master information block from a network device within a first cell. If the first cell supports a network power-saving mode, the master information block carries a first index value, which is used to determine the first WUS configuration information corresponding to the first index value from at least one pre-configured set of WUS configuration information. Therefore, the terminal device can determine the first WUS configuration information corresponding to the first index value based on the first index value carried in the master information block. This not only avoids the problem of the terminal device relying on other cells to send WUS information, but also avoids the network device sending data corresponding to the WUS configuration information to the terminal device, reducing signaling overhead.

[0006] According to the first WUS configuration information, the terminal device sends a WUS to the network device in the first cell to wake up the network device so that it can send OD-SIB1 to the terminal device, and then receives the OD-SIB1 sent by the network device in the first cell. Thus, the terminal device wakes up the network device to send OD-SIB1 without the network device continuously or periodically broadcasting SIB1, and the terminal device does not need to continuously listen for the SIB1 broadcast by the network device, achieving the goal of saving power consumption for both the network device and the terminal device.

[0007] In one possible implementation, the main information block also carries first indication information, which is used to indicate whether the first cell supports network power saving mode.

[0008] In this implementation, since the values ​​of the first indication information are different, the first indication information indicates whether the first cell supports the network power saving mode. This allows the terminal device to determine whether the first cell supports the network power saving mode based on the value of the first indication information carried in the main information block after receiving the main information block, thereby reducing signaling overhead.

[0009] In one possible implementation, the main information block includes a first field; if the first cell supports network power saving mode, the first field carries a first index value; if the first cell supports non-network power saving mode, the first field is used to configure the physical downlink control channel (PDCCH), which is used to schedule SIB1.

[0010] For example, the first field is the pdcch-ConfigSIB1 field in the main information block. When the first cell supports network energy-saving mode, the network device can send the first index value to the terminal device by reusing the pdcch-ConfigSIB1 field in the main information block without increasing signaling overhead. There is no need to send a large number of parameters included in the WUS configuration information in the air interface. The terminal device can determine the first WUS configuration information based on the first index value. The terminal device does not need to receive additional signaling, which not only avoids the increase of resource overhead, but also helps to reduce the power consumption of the terminal device.

[0011] In one possible implementation, at least one set of WUS configuration information belongs to the WUS configuration table, or at least one set of WUS configuration information is included in the WUS configuration table. Specifically, the WUS configuration table includes at least one record, each record corresponding to an index value and a set of WUS configuration information; or, each record corresponds to an index value range and a set of WUS configuration information. Different index values ​​within each index value range correspond to the same WUS configuration information.

[0012] In this implementation, at least one set of WUS configuration information is stored in a table, and each set of WUS configuration information is assigned a unique index value identifier. This allows the terminal device to query the first WUS configuration information corresponding to the first index value from the WUS configuration table after receiving the main information block, based on the first index value carried by the main information block, thereby reducing the complexity of managing at least one set of WUS configuration information.

[0013] In one possible implementation, WUS configuration information corresponding to different index value ranges is applicable to different communication scenarios, while WUS configuration information corresponding to different index values ​​within the same index value range is applicable to the same communication scenario.

[0014] In this implementation, WUS configuration information is configured at the communication scenario level, enabling the terminal device to send WUS to the network device based on WUS configuration information that is adaptive to the communication scenario, thereby improving the reliability of the terminal device sending WUS.

[0015] In one possible implementation, the method further includes: the terminal device receiving first configuration information from the network device. The first configuration information is used to configure the WUS configuration table.

[0016] In this implementation, the network device pre-configures the WUS configuration table for the terminal device, reducing the complexity of the terminal device looking up WUS configuration information based on the index value and improving the lookup efficiency.

[0017] In one possible implementation, each set of WUS configuration information includes at least: reference transmission resources for the physical random access channel (PRACH) used to transmit WUS, a preamble sequence set, the starting offset of the window, the preamble format, and second indication information. The reference transmission resources include reference frequency domain resources and / or reference time domain resources; the second indication information indicates whether the reduced capability (RedCap) device is allowed to transmit WUS to the network device.

[0018] In this implementation, the terminal device can select a preamble as WUS from the preamble sequence set included in the WUS configuration information and send it to the network device on the reference transmission resource of PRACH. This allows the network device to determine that the received preamble belongs to the preamble sequence set, thus determining that the received preamble is used to request the network device to send SIB1 on demand, thereby triggering the network device to send OD-SIB1.

[0019] Furthermore, if the second indication information included in the WUS configuration information indicates that RedCap devices are not allowed to send WUS to network devices, and if the terminal device is a RedCap device, the terminal device cannot send WUS to the network device. This avoids the problem of the first cell, which does not support RedCap devices, being frequently woken up by RedCap devices, resulting in resource waste, power consumption, and increased service latency for the terminal device.

[0020] In one possible implementation, sending WUS to the network device within the first cell includes: sending WUS to the network device within the first cell when the second indication information indicates that the RedCap device is allowed to send WUS to the network device, and the terminal device is a RedCap device, or when the terminal device is not a RedCap device.

[0021] In this implementation, when the terminal device is a RedCap device, the terminal device sends WUS to the network device only when the second indication information indicates that the RedCap device is allowed to send WUS to the network device. This avoids the problem of the first cell, which does not support RedCap devices, being frequently woken up by the RedCap device, resulting in resource waste, power consumption, and increased service latency for the terminal device.

[0022] When the terminal device is not a RedCap device, the terminal device can send WUS to the network device within the first cell, regardless of whether the second indication information indicates that the RedCap device is allowed to send WUS to the network device.

[0023] In one possible implementation, the method further includes: when the second indication information indicates that the RedCap device is not allowed to send WUS to the network device, and the terminal device is a RedCap device, the terminal device performs cell reselection, thereby avoiding the problem that the first cell that does not support the RedCap device is frequently woken up by the RedCap device, resulting in resource waste, power consumption, and increased service latency for the terminal device.

[0024] In one possible implementation, the method further includes: the terminal device, in response to sending WUS, starting a first timer, the duration of which is the duration corresponding to the initial offset of the window. Receiving OD-SIB1 from the network device within the first cell includes: the terminal device, in response to the expiration of the first timer, receiving OD-SIB1 within the SIB1 window.

[0025] In this implementation, the terminal device accurately knows when to start listening to OD-SIB1 based on the runtime of the first timer, and precisely controls the starting boundary of the SIB1 window without additional waiting or re-wake-up. This not only avoids the terminal device performing invalid blind detection and saves device power consumption, but also enables the terminal device to complete the random access process continuously and without overlap.

[0026] In one possible implementation, the frequency domain resources of PRACH are reference frequency domain resources, or the frequency domain resources of PRACH are determined based on a first index value, the physical cell identifier of the first cell, and the frequency domain bandwidth; wherein the frequency domain bandwidth is the product of the number of resource blocks occupied by the preamble format corresponding to the first index value, the subcarrier spacing, and the first value.

[0027] In this implementation, since the physical cell identifiers of different cells are unique, even if the terminal device receives master information blocks from network devices corresponding to different cells carrying the same index value, the terminal device can still determine different frequency domain resources based on the index value, the physical cell identifiers of different cells, and the frequency domain bandwidth. This avoids the problem of frequency domain resource interference caused by network devices configuring the same index value when the terminal device sends WUS.

[0028] In one possible implementation, the frequency domain resources of PRACH are determined based on a first index value, the physical cell identifier of the first cell, and the frequency domain bandwidth, including: the terminal device queries the WUS configuration table to obtain the reference frequency domain resources corresponding to the first index value; calculates the product of the remainder obtained by dividing the physical cell identifier of the first cell by the second value and the frequency domain bandwidth to obtain a third value; and determines the frequency domain resources of PRACH by the sum of the reference frequency domain resources corresponding to the first index value and the third value.

[0029] In this implementation, even if the terminal device receives master information blocks from network devices corresponding to different cells that carry the same index value, the terminal device can still calculate the frequency domain resources of different PRACHs, thus avoiding the problem of frequency domain resource interference when the terminal device sends WUS to network devices corresponding to different cells.

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

[0031] The method includes: the network device corresponding to the first cell sending a master information block to the terminal device. If the first cell supports a network power-saving mode, the master information block carries a first index value. This first index value is used to determine the first WUS configuration information corresponding to the first index value from at least one pre-configured set of WUS configuration information. Each set of WUS configuration information is used to configure the terminal device to send WUS. After receiving the WUS sent by the terminal device according to the first WUS configuration information for waking up the network device to send the On-Demand System Information Block (OD-SIB1) to the terminal device, the network device sends OD-SIB1 to the terminal device.

[0032] In this method, the network device does not need to send a large number of parameters included in the WUS configuration information to the terminal device. The terminal device can determine the first WUS configuration information corresponding to the first index value simply by carrying the first index value in the main information block. This not only enables the terminal device to obtain the first WUS configuration information, but also reduces signaling overhead.

[0033] The descriptions of the first index value and at least one set of WUS configuration information can be found in the introduction in the first aspect, and will not be repeated here.

[0034] In one possible implementation, the method further includes: the network device sending first configuration information to the terminal device. The first configuration information is used to configure the WUS configuration table.

[0035] In this implementation, the network device pre-configures the WUS configuration table for the terminal device, reducing the complexity of the terminal device looking up WUS configuration information based on the index value and improving the lookup efficiency.

[0036] In one possible implementation, the network device includes a low-power receiver and a main radio frequency transceiver module. The method further includes: the low-power receiver detecting a first preamble sent by the terminal device; wherein the first preamble is WUS; and when the low-power receiver determines that the first preamble belongs to a preamble sequence set, the low-power receiver sends a wake-up command to the main radio frequency transceiver module, the wake-up command being used to instruct the main radio frequency transceiver module to switch from a sleep state to an active state.

[0037] In this implementation, the low-power receiver determines that the first preamble belongs to the preamble sequence set, that is, it determines that the terminal device requests the network device to send OD-SIB1 to the terminal device. Only then does the low-power receiver wake up the main RF transceiver module, which avoids the problem of the main RF transceiver module being in a continuous active state and consuming a lot of power, thus helping to reduce the power consumption of the network device.

[0038] The second aspect is the implementation on the network device side, which corresponds to the first aspect. The explanations, supplements, and descriptions of the beneficial effects of the first aspect also apply to the second aspect, and will not be repeated here.

[0039] Thirdly, a communication device is provided, comprising a processing module and a transceiver module. The transceiver module is used to receive a master information block from a network device within a first cell; when the first cell supports a network power-saving mode, the master information block carries a first index value, the first index value being used to determine first WUS configuration information corresponding to the first index value from at least one pre-configured set of Wake-up Signal (WUS) configuration information.

[0040] The transceiver module is also used to send WUS to the network device in the first cell according to the first WUS configuration information; wherein, the WUS is used to wake up the network device to send the on-demand request system information block OD-SIB1 to the terminal device; The transceiver module is also used to receive OD-SIB1 from network devices within the first cell.

[0041] Fourthly, a communication device is provided, comprising a processing module and a transceiver module. The transceiver module is used to send a master information block to a terminal device within a first cell; wherein, when the first cell supports a network power-saving mode, the master information block carries a first index value, the first index value being used to determine first WUS configuration information corresponding to the first index value from at least one pre-configured set of Wake-up Signal (WUS) configuration information.

[0042] This transceiver module is used to receive the WUS sent by the terminal device according to the first WUS configuration information, and then send OD-SIB1 to the terminal device. The WUS is used to wake up the network device to send the On-Demand System Information Block (OD-SIB1) to the terminal device.

[0043] The third and fourth aspects are the implementation on the device side, which correspond to the first and second aspects. The explanations, supplements, and descriptions of the beneficial effects of the first and second aspects also apply to the third and fourth aspects, and will not be repeated here.

[0044] Fifthly, a communication device is provided, including a processor. The processor is coupled to a memory and can be used to execute instructions or data in the memory to implement the method in any possible implementation of the first aspect described above. Optionally, the communication device further includes a memory. Optionally, the communication device further includes a communication interface, and the processor is coupled to the communication interface.

[0045] In one implementation, the communication interface can be a transceiver, or an input / output interface.

[0046] In another implementation, the communication device is a chip configured in a terminal device. When the communication device is a chip configured in a terminal device, the communication interface can be an input / output interface.

[0047] In a sixth aspect, a communication device is provided, including a processor. The processor is coupled to a memory and can be used to execute instructions or data in the memory to implement the method in any possible implementation of the second aspect described above. Optionally, the communication device further includes a memory. Optionally, the communication device further includes a communication interface, and the processor is coupled to the communication interface.

[0048] In one implementation, the communication interface can be a transceiver, or an input / output interface.

[0049] In another implementation, the communication device is a chip configured in a satellite. When the communication device is a chip configured in a satellite, the communication interface can be an input / output interface.

[0050] In a seventh aspect, a processor is provided, comprising: an input circuit, an output circuit, and a processing circuit. The processing circuit is used to receive signals through the input circuit and to transmit signals through the output circuit, causing the processor to execute a method in any possible implementation of any aspect.

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

[0052] Eighthly, a communication device is provided, including a processor and a memory. The processor is used to read instructions stored in the memory, receive signals via a receiver, and transmit signals via a transmitter to execute the method in any possible implementation of any of the preceding aspects.

[0053] Optionally, there may be one or more processors and one or more memories.

[0054] Ninthly, a computer program product is provided, comprising: a computer program (also referred to as code or instructions) that, when executed, causes a computer to perform a method in any possible implementation of any of the above aspects.

[0055] In a tenth aspect, a computer-readable storage medium is provided that stores a computer program (also referred to as code or instructions) that, when executed on a computer, causes the computer to perform the methods in any possible implementation of any of the above aspects.

[0056] Eleventhly, a chip system is provided, comprising one or more processors for calling and executing instructions stored in memory, such that the methods in any of the foregoing aspects or any possible implementations of the foregoing aspects are executed. The chip system may be composed of chips or may include chips and other discrete devices.

[0057] The chip system may include input circuits or interfaces for transmitting information or data, and output circuits or interfaces for receiving information or data.

[0058] In a twelfth aspect, a communication system is provided, including the aforementioned terminal device and network device. Optionally, the communication system may further include other devices that communicate with the terminal device and / or network device. Attached Figure Description

[0059] Figure 1 A schematic diagram of a communication system provided in an embodiment of this application; Figure 2 This application provides a schematic diagram of an initial access process as illustrated in an embodiment. Figure 3 This is a schematic diagram of another initial access process provided in an embodiment of this application; Figure 4 A schematic diagram illustrating a communication method provided in an embodiment of this application; Figure 5 A schematic diagram illustrating another communication method provided in an embodiment of this application; Figure 6 A flowchart illustrating a communication method provided in an embodiment of this application; Figure 7 A flowchart illustrating another communication method provided in an embodiment of this application; Figure 8 A flowchart illustrating yet another communication method provided in an embodiment of this application; Figure 9 A flowchart illustrating a random access procedure provided in an embodiment of this application; Figure 10 A schematic block diagram of a communication device provided in an embodiment of this application; Figure 11 A schematic block diagram of another communication device provided in an embodiment of this application. Detailed Implementation

[0060] The technical solutions in the embodiments of this application will now be described with reference to the accompanying drawings.

[0061] The technical solutions provided in this application can be applied to various communication systems, such as: Global System for Mobile Communications (GSM) systems, General Packet Radio Service (GPRS), Wireless Local Area Network (WLAN), Long Term Evolution (LTE) systems, LTE Frequency Division Duplex (FDD) systems, LTE Time Division Duplex (TDD) systems, sidelink communication systems, Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication systems, non-terrestrial network (NTN) communication systems, 5th generation (5G) mobile communication systems, or new radio access technology (NR). Among these, 5G mobile communication systems can include non-standalone (NSA) and / or standalone (SA) networking. The technical solutions provided in this application can also be applied to future communication systems. This application does not limit the scope of these applications.

[0062] Figure 1 This is a schematic diagram of a communication system provided in an embodiment of this application. The communication system 100 may include a network device 110 and a terminal device 120. The network device 110 and the terminal device 120 can communicate via a wireless link, for example, through the communication method provided in this application. It should be understood that... Figure 1 An exemplary network device 110 and a terminal device 120 are shown. Optionally, the communication system 100 may also include multiple network devices and / or multiple terminal devices.

[0063] The network equipment in this application can be network-side equipment such as access network equipment, core network equipment, etc. Access network equipment is sometimes also called an access node. Access network equipment has wireless transceiver capabilities for communicating with terminal equipment. Access network equipment includes, but is not limited to, base stations, evolved NodeBs (eNodeBs), transmission reception points (TRPs) in the aforementioned communication systems, next-generation NodeBs (gNBs) in 5G mobile communication systems, access network equipment or modules of access network equipment in open RAN (ORAN) systems, satellites in NTN communication systems, base stations in future mobile communication systems, or access nodes in WiFi systems. Access network equipment can also be modules or units capable of implementing some of the functions of a base station. Access network equipment can be a macro base station, micro base station, or indoor station, a relay node or donor node, or a wireless controller in a cloud radio access network (CRAN) scenario. Optionally, access network equipment can also be a server, wearable device, or vehicle-mounted equipment, etc. For example, the access network equipment in vehicle-to-everything (V2X) technology can be a roadside unit (RSU). Multiple access network devices in a communication system can be base stations of the same type or different types. Base stations can communicate with terminals directly or via relay stations. Terminals can communicate with multiple base stations using different access technologies. The embodiments of this application do not limit the specific technology or device form used in the access network equipment. In this application, the access network equipment is referred to as a network device.

[0064] In this application, the means for implementing the functions of a network device can be a network device itself, or a means capable of supporting the network device in implementing those functions, such as a processor, circuit, chip, or chip system. This means can be installed in or connected to the network device. In the technical solutions provided in this application, the example of a network device being used to implement the functions of a network device is used to describe the technical solutions provided in this application.

[0065] The terminal device in this application can be a wireless terminal device capable of receiving network device scheduling and instruction information. The wireless terminal device can be a device providing voice and / or data connectivity to a user, a handheld device with wireless connectivity, or other processing devices connected to a wireless modem. For example, the terminal device can communicate with one or more core networks or the Internet via a radio access network (RAN). The terminal device can also be referred to as a terminal, user equipment (UE), mobile station, mobile terminal, etc. Terminal devices 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), ultra-reliable low-latency communication (URLLC), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, or satellite communication, etc. The terminal can be a mobile phone, tablet computer, computer with wireless transceiver capabilities, wearable device, vehicle, aircraft (such as drone, helicopter, airplane), hot air balloon, ship, robot, robotic arm, or smart home device, etc. The embodiments of this application do not limit the form of the terminal device.

[0066] In this application, the apparatus for implementing the functions of a terminal device can be the terminal device itself, or any apparatus capable of supporting the terminal device in implementing those functions, such as a processor, circuit, chip, or chip system. This apparatus can be installed in or connected to the terminal device. In the technical solutions provided in this application, the example of a terminal device being used to implement the functions of a terminal device is used to describe the technical solutions provided in this application.

[0067] Taking network devices as access network devices and terminal devices as terminals as an example, access network devices and / or terminals can be fixed or mobile. Access network devices and / or terminals 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 in the air on airplanes, balloons, and artificial satellites. This application does not limit the application scenarios of access network devices and terminals. Access network devices and terminal devices can be deployed in the same or different scenarios. For example, access network devices and terminal devices can be deployed simultaneously on land; or, access network devices can be deployed on land and terminal devices can be deployed on water, etc., and so on.

[0068] In practical applications, multiple network devices can collaborate to assist terminals in achieving wireless access, with different network devices each implementing a portion of the base station's functions. For example, network devices can be central units (CUs), distributed units (DUs), CUs (control planes, CPs), CUs (user planes, UPs), or radio units (RUs), etc. CUs and DUs can be set up separately 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).

[0069] 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 O-CU (Open CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules. CU (or CU-CP and CU-UP), DU, and RU can implement different protocol layer functions.

[0070] To facilitate understanding of the embodiments of this application, the terminology used in this application is first briefly explained. Optionally, the explanation of some terms can also refer to the explanations in the 3rd Generation Partnership Project (3GPP) standard protocol. It should be understood that the technical terms in this application are only examples and not limitations. For example, as technology evolves, technical terms may also change; where the technical meaning remains the same, other technical terms should also apply to this application.

[0071] 1. System Information System information (SI) is information sent by network devices to terminal devices. It may contain information required for the terminal device to access the network, as well as other functional / characteristic information. Network devices send SI when a terminal device accesses a cell or when broadcast messages sent by network devices change. This helps the terminal device to successfully camp on a cell that provides services and complete the corresponding communication services and physical processes.

[0072] In this embodiment, the system information consists of a master information block (MIB) and several system information blocks (SIBs). SIBs may include, but are not limited to, SIB1 and SIBx.

[0073] 2. MIB The MIB includes multiple fields, as shown in Table 1 below, including but not limited to the systemFrameNumber field, subCarrierSpacingCommon field, ssb-SubcarrierOffset field, dmrs-TypeA-Position field, pdcch-ConfigSIB1 field, cellBarred field, intraFreqReselection field, and two spare fields.

[0074] Table 1

[0075] The systemFrameNumber field refers to the system frame number, which occupies 6 bits and is used for synchronization and time management.

[0076] The subCarrierSpacingCommon field is used to provide the common subcarrier spacing, occupying 1 bit, and can be 15 kHz / 60 kHz or 30 kHz / 120 kHz.

[0077] The ssb-SubcarrierOffset field is used to indicate the subcarrier offset of the synchronization signal block (SSB).

[0078] The dmrs-TypeA-Position field is used to indicate the position of the first symbol of the uplink or downlink Type A demodulation reference signal (DMRS) within the time slot.

[0079] The `pdcch-ConfigSIB1` field is used to configure the PDCCH, which is used to schedule SIB1. Specifically, the `pdcch-ConfigSIB1` field indicates the transmission resources for the PDCCH that schedules SIB1, including time-domain and frequency-domain resources. In other words, the `pdcch-ConfigSIB1` field is used to configure the control-resource set (CORESET) 0 and the search space 0.

[0080] The `cellBarred` field indicates whether the current cell is blocked from access. When the `cellBarred` field is set to `Barred`, it indicates that the current cell is blocked from access, meaning the terminal device cannot select, reselect, or camp on that cell. Conversely, when the `cellBarred` field is set to `notBarred`, it indicates that the current cell is not blocked from access, meaning the terminal device can perform the normal initial access procedure on that cell.

[0081] The `intraFreqReselection` field indicates whether the terminal device is allowed to reselect another cell on the same frequency if access to the current cell is blocked. The `intraFreqReselection` field is only effective when the `cellBarred` field is set to `Barred`. When the `cellBarred` field is set to `notBarred`, the `intraFreqReselection` field can have any value.

[0082] 3.SIB1 SIB1 carries cell access control related information. Cell access control related information refers to control information indicating whether a terminal device is allowed to access network devices. This information may include access control parameters, security-related parameters, power control parameters, scheduling and resource allocation information, etc. SIBs may include cell configuration information, neighbor cell information, access control information, etc. Access control parameters may include cell selection and reselection parameters (e.g., signal quality, signal strength, coverage area, etc.).

[0083] In addition, SIB1 provides radio resource configuration information shared by all terminal devices and prohibition information required for unified access control. SIB1 is transmitted on the downlink-shared channel (DL-SCH) (or physical downlink shared channel (PDSCH)) at a period of 160 milliseconds (ms).

[0084] SIB1, also known as remaining minimum system information (RMSI), is broadcast periodically by network devices.

[0085] In this embodiment, the network device can periodically broadcast a MIB, and the terminal device can receive the periodically broadcast MIB. Then, in one approach, the network device periodically broadcasts a SIB1, and the terminal device can receive the periodically broadcast SIB1; this approach can be called broadcasting SIB1. Alternatively, in another approach, to reduce the power consumption of the terminal device, the terminal device can request SIB1 on demand, or this can be understood as the network device sending SIB1 on demand. In this approach, the network device sends SIB1 to the terminal device only after receiving a request message from the terminal device; this approach can be called sending SIB1 on demand. After receiving SIB1, the terminal initiates random access based on the received SIB1. In this application, sending SIB1 on demand can replace describing SIB1 based on a request.

[0086] For example, such as Figure 2 As shown, the initial access process for a terminal device to access the network via broadcasting SIB1 by the network device is as follows: S201, Network Equipment Broadcast SSB, Terminal Equipment Blind Detection SSB.

[0087] When a terminal device receives an SSB, it can obtain the MIB through the physical broadcast channel (PBCH) within the SSB. The MIB indicates information about control resource set 0 and search space 0. This search space 0 can be understood as the type 0 common search space (CSS). Specifically, the MIB may include parameters of the control resource set and parameters of the search space.

[0088] It is understandable that the parameters of the control resource set include the frequency domain start position, frequency domain bandwidth, time domain length (such as 1, 2, or 3 symbols), precoding granularity, etc.; the parameters of the search space include the control resource set ID, period and offset (in slots), duration (in slots), start symbol position, etc.

[0089] S202, the network device broadcasts SIB1. Correspondingly, the terminal device receives SIB1.

[0090] The terminal device detects the PDCCH in search space 0 based on the parameters of the search space. When the terminal device detects the PDCCH, it can further receive the PDSCH scheduled by the PDCCH, which carries SIB1. That is, the terminal device can obtain downlink control information (DCI) based on the PDCCH, and find the PDSCH carrying SIB1 based on the DCI, thereby obtaining SIB1.

[0091] After obtaining SIB1, the terminal device parses it to obtain the key information carried within. This key information includes: the random access preamble configuration (such as the PRACH configuration index and preamble format), upon which the terminal device can send PRACH. It can be understood that the key information carried in SIB1 may also include information related to the random access response (RAR) (such as the ra-Search Space, i.e., type 1 CSS) and information about the common PDCCH (such as the common Control Resource Set).

[0092] S203, the terminal device performs random access based on the received SIB1.

[0093] For example, after selecting a random access preamble sequence according to the configuration, the terminal device sends the random access preamble sequence (or message 1, MSG1) on the time and frequency domain resources of the PRACH, and waits to receive the RAR (or message 2, MSG2) in the designated PDCCH monitoring window. The RAR carries uplink resources. After receiving the RAR, the terminal device sends a connection request message (or message 3, MSG3) to the network device according to the uplink resources carried in the RAR, and receives a connection confirmation message (or message 4, MSG4) from the network device, thus completing the random access process.

[0094] Depend on Figure 2 As shown in the process, network devices periodically broadcast SIB1, and terminal devices continuously listen for SIB1, which wastes power for both network and terminal devices. Therefore, network devices should send SIB1 only as needed, based on requests from terminal devices.

[0095] like Figure 3 As shown below, the process of network devices sending SIB1 on demand is described in detail. Specifically, it includes S301 to S309 as described below.

[0096] S301, the network device corresponding to cell A sends WUS configuration information and measurement configuration information to the terminal device. Correspondingly, the terminal device receives the WUS configuration information and measurement configuration information from the network device corresponding to cell A.

[0097] The WUS configuration information supports obtaining OD-SIB1, meaning that the terminal device can use this WUS configuration information to wake up the network device corresponding to cell B to send OD-SIB1. This WUS configuration information may include: reference transmission resources for the PRACH used to send WUS, the preamble sequence set, the starting offset of the window, the preamble format, and the WUS triggering conditions, etc.

[0098] The transmission resources used for transmitting the PRACH of WUS include the time-domain resources and / or frequency-domain resources used by the terminal equipment to transmit WUS.

[0099] The preamble sequence set (OD-SIB1RequestPreambleSet) represents a set of RACH preamble sequences. These preamble sequences are used to request the network device to send SIB1 to the terminal device on demand. In other words, if the preamble received by the network device belongs to this preamble sequence set, the network device can determine that the received preamble is used to request the network device to send SIB1 on demand.

[0100] The window's starting offset (od-sib1-windowStartOffset) refers to the initial offset of the OD-SIB1 window relative to the end boundary of the RAR window. In other words, it determines the time slot in which the OD-SIB1 window begins after the RAR window ends. If this starting offset is too small, the OD-SIB1 window may overlap with the RAR window in the time domain, preventing the terminal device from simultaneously processing response messages and listening to OD-SIB1. If the starting offset is too large, it will result in a storage idle period between the OD-SIB1 window and the RAR window, increasing the latency for the terminal device to obtain OD-SIB1 and impacting the user experience. Therefore, the window's starting offset configured in the WUS configuration information ensures that the terminal device can continuously and non-overlappingly obtain OD-SIB1 within the OD-SIB1 window after the RAR window ends.

[0101] The preamble format indicates the type of preamble. Preamble types include long sequence formats and short sequence formats. Long sequence formats include Format0, Format1, Format2, and Format3. Short sequence formats include FormatA1, FormatB1, FormatA2, FormatB2, FormatA3, FormatB3, and FormatC0, etc.

[0102] It should be noted that different preamble formats are suitable for different scenarios. For example, long-sequence preambles are only applicable to the first frequency band (frequency range 1, FR1), which refers to the frequency band from 450MHz to 6GHz. Short-sequence preambles are applicable not only to FR1 but also to the second frequency band (frequency range 2, FR2), which refers to the frequency band from 24.25GHz to 52.6GHz.

[0103] WUS triggering conditions can be signal quality (e.g., RSRP or RSRQ) exceeding a preset threshold, or event triggering (e.g., A3 event, A4 event, or A5 event, etc.).

[0104] It is understood that cell B can be a network energy saving (NES) cell, and the network equipment corresponding to cell B only supports sending SIB1 on demand. The network equipment corresponding to cell A is a cell that supports periodically broadcasting SIB1. Since NES cell B does not support periodically broadcasting SIB1, the terminal device can request WUS configuration information from a neighboring cell (such as cell A). Then, based on the obtained WUS configuration information, the terminal device sends an uplink WUS to NES cell B to wake up NES cell B and send SIB1 to the terminal device.

[0105] The measurement configuration information received by the terminal device is used to configure some information related to the measurement of the terminal device, such as configuring the measurement object (e.g., the identification information, frequency point, and reference signal information of cell B to be measured), the measurement period, and information related to reporting the measurement report.

[0106] Information related to the reported measurement report includes the triggering conditions for the report and the content included in the report, such as the configuration of the report to include measurement results (e.g., measurement results of the serving cell and neighboring cells), measurement identifiers, etc. Measurement results include, but are not limited to, reference signal received power (RSRP), reference signal received quality (RSRQ), signal-to-interference plus noise ratio (SINR), or reference signal-to-interference plus noise ratio (RS-SINR).

[0107] S302, the terminal device measures the signal quality of cell B according to the measurement configuration information.

[0108] After receiving the measurement configuration information, the terminal device measures the signal quality of cell B according to the identification information of cell B indicated in the measurement configuration information, and obtains the measurement result of cell B.

[0109] S303, the terminal device determines whether the WUS trigger condition is met.

[0110] In one scenario, when the terminal device determines that the WUS triggering condition is not met, the terminal device continues to measure the signal quality of cell B.

[0111] In another case, when the terminal device determines that the WUS trigger condition is met, the terminal device executes the following S304.

[0112] S304, the terminal device sends a WUS to the network device corresponding to NES cell B. Correspondingly, the network device corresponding to NES cell B receives the WUS from the terminal device.

[0113] WUS is used to wake up the network device corresponding to cell B and send SIB1 to the terminal device as needed. The terminal device can send WUS to the network device corresponding to NES cell B according to the WUS configuration information.

[0114] S305, the network device corresponding to NES cell B sends a random access response. Correspondingly, the terminal device receives the random access response sent by the network device corresponding to NES cell B.

[0115] When the terminal device receives the random access response, it can determine that the network device corresponding to NES cell B has received WUS.

[0116] S306, the network device corresponding to NES cell B sends SIB1 as needed. Correspondingly, the terminal device receives SIB1 sent by the network device corresponding to NES cell B.

[0117] S307, the terminal device monitors and receives SIB1 through Type0 PDCCH.

[0118] It is understandable that the relevant description of SIB1 and the specific implementation principles of S306 and S307 are similar to the specific implementation principle of the terminal device obtaining SIB1 in S202 above. They can be referred to for mutual understanding, and will not be repeated here.

[0119] S308, the terminal device determines whether to reselect to cell B.

[0120] After the terminal device determines that it has been reselected to cell B, the terminal device executes the following S309; ​​otherwise, the terminal device continues to camp on cell A.

[0121] S309, the terminal device performs random access based on the received SIB1.

[0122] For the specific implementation of S309, please refer to the description of S203 above, which will not be repeated here.

[0123] The above Figure 3 The terminal device in the context is a device with NES capability, capable of sending request messages to network devices to obtain system information blocks. It should be understood that in an NES cell, devices that do not have the capability to send request messages to network devices to obtain system information blocks do not support sending request messages to obtain SIB1; such devices can be referred to as devices without NES capability and are not supported in residing in an NES cell.

[0124] In a network-based energy-saving scenario, a cell can be classified as either a network-based energy-saving cell or a non-network-based energy-saving cell. At any given time, a cell can be either a network-based energy-saving cell or a non-network-based energy-saving cell. That is, a cell cannot be both a network-based energy-saving cell and a non-network-based energy-saving cell simultaneously. For example, at time T1, the above... Figure 3 Cell A in the diagram is a non-energy-saving cell. At time T2, due to the smaller number of users or lower traffic volume in cell A, to conserve network power, the network equipment can switch from periodically broadcasting SIB1 to sending SIB1 on demand. Figure 3 Cell A is switched to a network energy-saving cell, that is, cell A is transformed from a regular cell to an NES cell.

[0125] From the above Figure 3 as well as Figure 4It is known that the WUS configuration information obtained by the terminal device is provided by the network device corresponding to the auxiliary cell (i.e., the network device corresponding to cell A). In this way, the terminal device can send WUS to NES cell B to obtain SIB1 based on the WUS configuration information. However, in scenarios without auxiliary cell coverage, such as rural wide-area coverage, private network deployment, or co-frequency networking, the above-mentioned scheme of relying on neighboring cells to obtain SIB1 on demand cannot be implemented.

[0126] For example, in such Figure 5 In the standalone network energy-saving scenario shown, the network device corresponding to NES cell C periodically broadcasts SSB to maintain basic signal coverage, but no longer periodically broadcasts SIB1 to achieve energy saving. However, because the network device corresponding to NES cell C no longer periodically broadcasts SIB1, the terminal device cannot obtain the WUS configuration information. Therefore, after parsing the MIB from the SSB, the terminal device cannot send uplink WUS to the network device corresponding to NES cell C, resulting in the terminal device being unable to obtain SIB1 and thus unable to access NES cell C.

[0127] In view of this, this application provides a communication method in which a terminal device receives a master information block from a network device in a first cell. When the first cell supports a network power-saving mode, the master information block carries a first index value, which is used to determine the first WUS configuration information corresponding to the first index value from at least one set of WUS configuration information. Based on the first WUS configuration information, the terminal device sends a WUS message to the network device in the first cell to wake up the network device and send OD-SIB1 to the terminal device, and then receives the OD-SIB1 message sent by the network device in the first cell. It is evident that the terminal device can determine the first WUS configuration information corresponding to the first index value based on the first index value carried in the master information block. This not only avoids the problem of the terminal device relying on other cells to send WUS messages, but also avoids the network device sending data corresponding to the WUS configuration information to the terminal device, reducing signaling overhead.

[0128] Furthermore, the terminal device wakes up the network device to send OD-SIB1, eliminating the need for the network device to continuously or periodically broadcast SIB1, and also eliminating the need for the terminal device to continuously listen for the SIB1 broadcast by the network device, thus achieving the goal of saving power consumption of both the network device and the terminal device.

[0129] The solution provided in this application will be described in detail below with reference to the corresponding flowcharts. It is understood that the illustrative flowcharts provided in this application primarily use different devices (e.g., terminal devices, network devices) as examples of the execution subjects of this interactive illustration to illustrate the method, but this application does not limit the execution subjects of the interactive illustrations. For example, the devices (e.g., terminal devices, network devices) in the illustrative flowcharts can also be chips, chip systems, or processors that support the implementation of this method on the device, or logic modules or software that can implement all or part of the functions of the device.

[0130] As a general statement, the message or signaling interactions involved in the interaction process of this application embodiment can be standard messages or signaling or newly introduced messages or signaling. This application embodiment does not make specific limitations on this.

[0131] Figure 6 This is a flowchart illustrating a communication method provided in an embodiment of this application. It can be understood that... Figure 6 The terminal device in the middle can be Figure 1 Any terminal device in the context of network equipment can refer to any component within that terminal device (such as a processor, chip, or chip system). Network equipment can be... Figure 1 Network equipment can also refer to devices within network equipment (such as processors, chips, or chip systems). For example... Figure 6 As shown, the method includes the following steps: S610, the network device corresponding to the first cell sends the main information block to the terminal device, and the terminal device receives the main information block in the first cell.

[0132] In the case where the first cell supports network power saving mode, the main information block carries a first index value. The main information block can be a MIB, and the first index value is used to determine the first WUS configuration information corresponding to the first index value from at least one pre-configured set of WUS configuration information. Each set of WUS configuration information contains all / complete information for configuring the terminal device to send WUS, that is, the content in a set of WUS configuration information supports the terminal device to send WUS to wake up the network device to initiate OD-SIB1.

[0133] The first cell supporting network energy-saving mode means that the first cell is an NES cell. That is, when the first cell is an NES cell, it supports network energy-saving mode. The first cell not supporting network energy-saving mode means that the first cell is a non-NES cell, i.e., a regular cell. When the first cell is a non-NES cell or a regular cell, it does not support network energy-saving mode. In this application, the first cell is the serving cell of the terminal device. The terminal device can initially connect to the first cell after power-on, or it can reselect to the first cell after cell reselection; there is no limitation on this.

[0134] Optionally, the main information block includes a first field. If the first cell supports network power saving mode, the first field carries a first index value. If the first cell does not support network power saving mode, the first field is used to configure the PDCCH. For example, the first field is the pdcch-ConfigSIB1 field. If the first cell supports network power saving mode, the pdcch-ConfigSIB1 field carries a first index value. If the first cell does not support network power saving mode, the pdcch-ConfigSIB1 field is used to configure the PDCCH.

[0135] It should be noted that when the first cell supports network power saving mode, the network device corresponding to the first cell no longer periodically broadcasts SIB1. In this case, the pdcch-ConfigSIB1 field in the main information block is no longer used to configure the PDCCH, but is reused to carry the first index value. For example, the pdcch-ConfigSIB1 field is defined as nesWusConfigIndex to carry the first index value. This reuse of the pdcch-ConfigSIB1 field allows the first index value to be sent to the terminal device without increasing signaling overhead. It eliminates the need to transmit a large number of parameters included in the WUS configuration information over the air interface. The terminal device can determine the first WUS configuration information based on the first index value, without receiving additional signaling. This not only avoids increased resource overhead but also helps reduce the power consumption of the terminal device.

[0136] In this embodiment of the application, when the first cell supports network power saving mode, the first field of the main information block sent by the network device to the terminal device carries a first index value. After the terminal device receives the main information block, it can parse the first index value from the main information block to determine the first WUS configuration information corresponding to the first index value. This not only improves the efficiency of network configuration of WUS configuration information, but also reduces signaling overhead.

[0137] Optionally, the main information block may also carry first indication information, which is used to indicate whether the first cell supports network power saving mode. For example, the first indication information may be used to indicate that the first cell supports network power saving mode, or the first indication information may also be used to indicate that the first cell does not support network power saving mode.

[0138] In one implementation, the spare bits of the main information block can be used to carry first indication information (e.g., nes-OperatingMode). The network device can assign different values ​​to the first indication information to indicate whether the first cell supports network power saving mode. If the first indication information indicates that the first cell supports network power saving mode, the first field of the main information block carries a first index value. If the first indication information indicates that the first cell does not support network power saving mode, the first field of the main information block is used to configure the PDCCH.

[0139] For example, when the first indication information is a first value, the first indication information is used to indicate that the first cell supports network power saving mode. When the first indication information is a second value, the first indication information is used to indicate that the first cell does not support network power saving mode. For instance, the terminal device can set the first indication information to a 1-bit binary number, and by assigning different binary numbers to the first indication information, the first indication information can indicate whether the first cell supports network power saving mode. When the value of the first indication information is 1, the first indication information is used to indicate that the first cell supports network power saving mode. When the value of the first indication information is 0, the first indication information is used to indicate that the first cell does not support network power saving mode.

[0140] It should be understood that the terminal device may also determine the first indication information as other types of values ​​or parameters, and there is no limitation on this. For example, when the first indication information is TRUE, it is used to indicate that the first cell supports network power saving mode. When the first information is FALSE, it is used to indicate that the first cell does not support network power saving mode.

[0141] For example, such as Figure 7As shown, taking the initial access of a terminal device to cell A as an example, after receiving the SSB periodically broadcast by the network device corresponding to cell A, the terminal device demodulates the PBCH to obtain the MIB. Further, the terminal device determines whether the first indication information carried in the MIB indicates that cell A supports network power saving mode. When the first indication information carried in the MIB indicates that cell A supports network power saving mode, the first field of the MIB carries a first index value. Thus, when the MIB sent by the network device to the terminal device carries the first indication information and the first index value, after receiving the MIB, the terminal device can parse the first indication information and the first index value from the MIB to determine whether the first cell supports network power saving mode based on the first indication information, and to determine the WUS configuration information corresponding to the first index value based on the first index value, thereby improving the efficiency of network configuration. When the first indication information carried in the MIB indicates that the first cell does not support network power saving mode, the first field of the MIB does not carry the first index value, but is used to configure the PDCCH. In this case, the network device of cell A periodically broadcasts SIB1, and the terminal device can obtain SIB1 according to the configured PDCCH. For the specific implementation details, please refer to S202 above, which will not be repeated here.

[0142] Optionally, the terminal device stores at least one set of WUS configuration information, and each set of WUS configuration information corresponds to an index value. After parsing the first index value from the main information block, the terminal device determines the first WUS configuration information corresponding to the first index value from the at least one set of WUS configuration information based on the first index value. Each set of WUS configuration information and its corresponding index value can be pre-configured to the terminal device by the network device.

[0143] Optionally, each set of WUS configuration information includes at least: a reference transmission resource for the PRACH used to send WUS, a preamble sequence set, the starting offset of the window, the preamble format, and second indication information.

[0144] The reference transmission resources used for transmitting the PRACH of WUS include reference time-domain resources and / or reference frequency-domain resources used by the terminal device to transmit WUS. For example, the reference time-domain resources included in the WUS configuration information may be actual frequency-domain resources, or they may include time offsets. The time offset is not an absolute time, but a time slot interval. The actual time-domain resources used for transmitting the PRACH of WUS refer to the sum of the end time the terminal device receives the SSB and the time offset. The reference frequency-domain resources included in the WUS configuration information may be actual frequency-domain resources or frequency-domain offsets. The actual frequency-domain resources used for transmitting the PRACH of WUS refer to the sum of the frequency-domain position where the terminal device finds the SSB and the frequency-domain offset.

[0145] The second indication information is used to indicate whether RedCap devices are allowed to send WUS to network devices. Network devices can assign different values ​​to the second indication information to indicate whether RedCap devices are allowed to send WUS to network devices. For example, when the second indication information is TRUE, it indicates that RedCap devices are allowed to send WUS to network devices. When the second indication information is FALSE, it indicates that RedCap devices are not allowed to send WUS to network devices.

[0146] For a detailed description of the preamble sequence set, the starting offset of the window, and the preamble format, please refer to the description in S301 above, which will not be repeated here.

[0147] In one possible implementation, at least one set of WUS configuration information is stored in tabular form. For example, the terminal device stores a WUS configuration table, which includes at least one record, each record corresponding to an index value and a set of WUS configuration information; or, each record corresponds to an index value range and a set of WUS configuration information, with different index values ​​within each index value range corresponding to the same WUS configuration information. Different index value ranges correspond to different communication scenarios.

[0148] Optionally, after parsing the first index value from the main information block, the terminal device retrieves the first WUS configuration information corresponding to the first index value from the WUS configuration table. Therefore, the network device does not need to transmit the large number of parameters included in the WUS configuration information over the air interface, and the terminal device does not need to receive additional signaling, which not only avoids increased resource overhead but also helps reduce the power consumption of the terminal device.

[0149] For example, the WUS configuration table includes 0-255 records, each corresponding to an index value and WUS configuration information. Records 0-255 correspond to index values ​​0-255 respectively. Alternatively, as shown in Table 2 below, the WUS configuration table includes five index value ranges divided from the 0-255 index values. These five index value ranges, in ascending order of index value, are applicable to the following communication scenarios: FR1, FR2, RedCap, high-coverage zone, and future expansion. Future expansion can refer to communication scenarios to be expanded in the future to adapt to future communication developments.

[0150] Table 2

[0151] In this context, the communication scenario FR1 refers to a frequency band ranging from 450MHz to 6GHz. For example, if a network device determines that its frequency band is between 450MHz and 6GHz, which is applicable to the FR1 scenario, the network device can select an index value from the index value range [0, 99] as the first index value. For example, the network device assigns the first index value to 50. The network device periodically sends SSBs. After receiving the SSB, the terminal device within its coverage area obtains the main information block through the PBCH in the SSB and parses the main information block to obtain the first index value of 50. The terminal device can determine the WUS configuration information corresponding to the first index value of 50 by querying Table 2 above. That is, the preamble format is Format0, the time offset is 2 slots, the frequency offset is 0, the preamble sequence set is SetA, the window start offset is sl1, and the second indication information is True. That is, the second indication information is used to indicate that the RedCap device is allowed to send WUS to the network device.

[0152] The communication scenario FR1 refers to a frequency band ranging from 24.25 GHz to 52.6 GHz. If the network device determines that its frequency band is within the 24.25 GHz to 52.6 GHz band, which is applicable to the FR2 scenario, the network device can select an index value from the index value range [100, 159] as the first index value. For example, the network device assigns the first index value to 150. The network device periodically sends SSB. After receiving the SSB, the terminal device within its coverage area obtains the main information block through the PBCH in the SSB and parses the main information block to obtain the first index value of 150. The terminal device can determine the WUS configuration information corresponding to the first index value 150 by querying Table 2 above. That is, the preamble format is Format0, the time offset is 5 slots, the frequency offset is 0, the preamble sequence set is SetB, the window start offset is sl2, and the second indication information is True. That is, the second indication information is used to indicate that the RedCap device is allowed to send WUS to the network device.

[0153] The communication scenario for RedCap refers to the communication scenario designed for RedCap devices. For example, a RedCap device might be an IoT device. If the network device determines that the current deployment environment is suitable for the RedCap communication scenario based on the communication scenario, the network device can select an index value from the index value range [160, 199] as the first index value. For example, the network device might assign the first index value to 180. The network device periodically sends SSBs. After receiving the SSB, the terminal device within its coverage area obtains the main information block through the PBCH in the SSB and parses the main information block to obtain the first index value of 180. The terminal device can then determine the WUS configuration information corresponding to the first index value of 180 by querying Table 2 above. This includes a preamble format of Format0, a time offset of 5 slots, a frequency offset of 0, a preamble sequence set of SetC, a window start offset of sl2, and the second indication information being True. This means the second indication information is used to indicate that the RedCap device is allowed to send WUS to the network device.

[0154] The communication scenario is a high-coverage zone, which refers to areas with poor signal propagation conditions where ordinary 5G coverage cannot reach or requires ultra-long-distance coverage. Examples include basements and rural areas with edge coverage. If the network device determines that the current deployment environment belongs to a high-coverage zone scenario based on the communication scenario, the network device can select an index value from the index value range [200, 239] as the first index value. For example, the network device assigns the first index value to 220. The network device periodically sends SSBs. After receiving the SSB, the terminal device within its coverage area obtains the main information block through the PBCH in the SSB and parses the main information block to obtain the first index value of 220. The terminal device can determine the WUS configuration information corresponding to the first index value 220 by querying Table 2 above. That is, the preamble format is FormatA1, the time offset is 2 slots, the frequency offset is 0, the preamble sequence set is SetD, and the second indication information is True, meaning the second indication information is used to indicate that RedCap devices are allowed to send WUS to the network device, and the starting offset of the window is sl1. In SetD, the preamble sequence is retransmitted twice by default. This ensures WUS transmission in weak coverage scenarios without adding extra signaling.

[0155] It should be noted that the values ​​of the second indication information corresponding to different index value ranges in Table 2 above are all True. This is only an example. In the case of communication scenarios such as FR1, FR2 or high coverage special zone, the second indication information indicates whether RedCap device is allowed to send WUS to network device, which is subject to the actual configuration in the WUS configuration table.

[0156] Optionally, the WUS configuration table stored in the terminal device is pre-configured by the network device. For example, the network device sends first configuration information to the terminal device, which is used to configure the WUS configuration table. After receiving the first configuration information, the terminal device stores the WUS configuration table configured by the first configuration information. Thus, the network device pre-configures the WUS configuration table for the terminal device, allowing the terminal device to determine the WUS configuration information corresponding to the first index value from the pre-configured WUS configuration table after parsing the first index value from the main information block. This eliminates the need for the network device to send WUS configuration information to the terminal device, reducing signaling overhead and lowering the complexity of the terminal device searching for WUS configuration information based on index values, while also improving search efficiency.

[0157] In S620, the terminal device sends a WUS within the first cell based on the first WUS configuration information. Correspondingly, the network device receives the WUS.

[0158] WUS is used to wake up network devices to send OD-SIB1 to terminal devices.

[0159] In this embodiment, when the first cell supports network power saving mode, it is described that the first cell is an NES cell, and the network device corresponding to the first cell does not periodically broadcast SIB1. In this case, the terminal device in the first cell sends WUS to the network device to wake up the network device to send OD-SIB1 to the terminal device.

[0160] Optionally, after determining the first WUS configuration information based on the first index value, the terminal device sends the WUS to the network device within the first cell according to the first WUS configuration information. Thus, upon receiving the WUS sent by the terminal device, the network device can allocate resources specifically based on the terminal device's request, reducing unnecessary network overhead and saving signaling overhead.

[0161] Specifically, the terminal device selects a preamble sequence as the WUS from the set of preamble sequences included in the first WUS configuration information, and then sends the WUS out on the actual transmission resources of the PRACH included in the first WUS configuration information.

[0162] In scenario one, the actual transmission resource for PRACH is the reference transmission resource for PRACH included in the first WUS configuration information. In this case, the terminal device transmits WUS on the reference transmission resource for PRACH.

[0163] In scenario two, the reference frequency domain resource for PRACH included in the first WUS configuration information is the base frequency domain offset. The frequency domain resource for PRACH is determined based on the first index value, the physical cell identifier of the first cell, and the frequency domain bandwidth. Optionally, the terminal device queries the WUS configuration table for the reference frequency domain resource corresponding to the first index value, and the terminal device calculates the product of the remainder obtained by dividing the physical cell identifier (PCI) of the first cell by the second value and the frequency domain bandwidth to obtain the third value. Further, the terminal device determines the frequency domain resource for PRACH as the sum of the reference frequency domain resource corresponding to the first index value and the third value.

[0164] For example, the terminal device determines the frequency domain resources of PRACH using the following formula (1).

[0165] Rel_Freq=Table_Freq_offset+(PCI mod3)*Bandwidth(1); Where Rel_Freq is the frequency domain resource of PRACH, Table_Freq_offset is the reference frequency domain resource corresponding to the first index value, PCI is the physical cell identifier of the first cell, PCI mod3 refers to the remainder obtained by dividing PCI by 3, and Bandwidth is the frequency domain bandwidth. ;in, This represents the number of resource blocks occupied by the preamble format corresponding to the first index value. For example, when the preamble format is Format0, it occupies 6 resource blocks. The subcarrier spacing.

[0166] In this second scenario, since the physical cell identifiers of different cells are unique, even if the terminal device receives master information blocks from network devices corresponding to different cells carrying the same index value, the terminal device can still determine different frequency domain resources based on the index value, the physical cell identifiers of different cells, and the frequency domain bandwidth. This avoids the problem of frequency domain resource interference caused by network devices configuring the same index value when the terminal device sends WUS.

[0167] Since the second indication information included in the first WUS configuration information is used to indicate whether RedCap devices are allowed to send WUS to network devices, before sending WUS to network devices, the terminal device also determines whether to send WUS to network devices based on whether it is a RedCap device and the content indicated by the second indication information. Specifically, this includes the following situations: In one scenario, if the terminal device is a RedCap device and the second indication information indicates that RedCap devices are not allowed to send WUS to the network device, the terminal device cannot send WUS to the network device within the first cell, and the terminal device performs cell reselection. In other words, if the terminal device is a RedCap device and is not allowed to send WUS to the network device, then the terminal device is prohibited from accessing the first cell. This avoids the problem of the first cell, which does not support RedCap devices, being frequently woken up by RedCap devices, leading to resource waste, power consumption, and increased service latency for the terminal device.

[0168] Cell reselection refers to the process by which the terminal device, based on the measured signal strength of the serving cell and neighboring cells, determines that a cell handover is required, then selects the target cell with the best signal from the candidate cells and completes the camping process.

[0169] In another scenario, if the terminal device is not a RedCap device, the terminal device may send WUS to the network device within the first cell, regardless of whether the second indication information indicates that the RedCap device is allowed to send WUS to the network device.

[0170] In another scenario, if the second instruction indicates that RedCap devices are not allowed to send WUS to network devices, and the terminal device is not a RedCap device, the terminal device may send WUS to the network device within the first cell. In other words, even if RedCap devices are not allowed to send WUS to network devices, if the terminal device is not a RedCap device, it may still send WUS to the network device.

[0171] For example, continue as follows Figure 7 As shown, assuming the terminal device is a RedCap device and the value of the second indication information is a preset value (e.g., True), the terminal device determines that the second indication information indicates that the RedCap device is allowed to send WUS to the network device, and the terminal device sends WUS to the network device within cell A. If the terminal device is a RedCap device and the value of the second indication information is not a preset value, for example, if the value of the second indication information is False, then the terminal device determines that the second indication information indicates that the RedCap device is not allowed to send WUS to the network device, and the terminal device cannot send WUS to the network device. If the terminal device is not a RedCap device, then there is no need to determine the value of the second indication information; the terminal device can send WUS to the network device within cell A.

[0172] Before the terminal device has determined the WUS configuration information, the terminal device parses the first indication information from the received main information block and determines whether the first cell supports network power saving mode based on the first indication information. This avoids the situation where the terminal device mistakenly regards the first cell as a non-network power saving cell when the first cell supports network power saving mode, and the terminal device directly performs cell reselection after continuously failing to search for SIB1. This ensures that the terminal device can successfully camp on the first cell.

[0173] S630, the network device corresponding to the first cell sends OD-SIB1 to the terminal device. The terminal device then receives this OD-SIB1.

[0174] In this embodiment, after the network device corresponding to the first cell receives the WUS sent by the terminal device, the network device is woken up and sends OD-SIB1 to the terminal device. After receiving the OD-SIB1 sent by the network device, the terminal device performs subsequent cell access and registration processes based on the system information included in the OD-SIB1.

[0175] Optionally, such as Figure 8 As shown, in response, the terminal device sends a WUS to the network device within the first cell and starts a first timer. The duration of the first timer is the duration corresponding to the starting offset of the window included in the first WUS configuration information. During the first timer's operation, the terminal device receives a RAR. Upon the first timer's expiration, the terminal device begins listening to the OD-SIB1 window. If the terminal device detects OD-SIB1 within the OD-SIB1 window, it parses OD-SIB1 to obtain the system message and then executes the subsequent random access procedure based on the system message. Therefore, the terminal device starts listening to OD-SIB1 at the end of the RAR window without additional waiting or re-wake-up, avoiding invalid blind detection, saving power consumption, and enabling continuous, non-overlapping random access procedures.

[0176] In summary, in this embodiment, when the first cell supports network power saving mode, the main information block received by the terminal device carries a first index value. This first index value is used to determine the first WUS configuration information corresponding to the first index value from at least one set of WUS configuration information. Further, based on the first WUS configuration information, the terminal device sends a WUS message to the network device within the first cell to wake up the network device and send OD-SIB1 to the terminal device, and then receives the OD-SIB1 sent by the network device within the first cell. It is evident that the terminal device can determine the first WUS configuration information corresponding to the first index value based on the first index value carried in the main information block without the assistance of other cells, avoiding the network device sending data corresponding to the WUS configuration information to the terminal device, thereby reducing air interface overhead. Furthermore, the terminal device waking up the network device to send OD-SIB1 does not require the network device to continuously or periodically broadcast SIB1, nor does it require the terminal device to continuously listen to the SIB1 broadcast by the network device. This not only avoids the problem of the terminal device relying on other cells to send WUS, but also achieves the purpose of saving power consumption of both the network device and the terminal device by receiving SIB1 on demand, and also reduces signaling overhead.

[0177] The following section, in conjunction with the method described above for the terminal device to determine the first WUS configuration information corresponding to the first index value based on the first index value carried in the main information block, provides a detailed introduction to the random access process of the terminal device accessing the network in the SIB1 scenario where the network device sends information on demand.

[0178] For example, Figure 9 This is a flowchart illustrating a random access procedure provided in an embodiment of this application. Figure 9 As shown, the process includes the following steps S900 to S908.

[0179] In S900, the network device corresponding to the first cell periodically sends SSBs to the terminal device. The terminal device then receives the SSBs.

[0180] Optionally, the terminal device initially accesses the first cell, or reselects to the first cell after cell reselection. The network device corresponding to the first cell periodically broadcasts an SSB. For example, the network device corresponding to the first cell can broadcast an SSB every 160 milliseconds (ms). After receiving the SSB, the terminal device obtains the MIB through the PBCH in the SSB.

[0181] S901, the terminal device parses the first instruction information from the MIB.

[0182] When the first indication information is used to indicate that the first cell does not support network power saving mode, the SIB1 broadcast by the network device is received.

[0183] If the first instruction information is used to instruct the first cell to support the network energy-saving module, the following S902 to S908 are executed.

[0184] S902, the terminal device parses the first index value from the MIB and determines the first WUS configuration information corresponding to the first index value based on the first index value.

[0185] Optionally, the specific implementation of the terminal device determining the first WUS configuration information corresponding to the first index value based on the first index value can be referred to in the description in S610 above, and will not be repeated here.

[0186] S903, the terminal device parses the second instruction information from the MIB and determines whether to allow the RedCap device to send WUS to the network device based on the second instruction information.

[0187] If the second instruction indicates that RedCap devices are not allowed to send WUS to network devices, and the terminal device is a RedCap device, the terminal device determines that it cannot send WUS to network devices in the first cell, and thus executes S904.

[0188] If the second instruction indicates that the RedCap device is not allowed to send WUS to the network device, and the terminal device is not a RedCap device, or if the second instruction indicates that the RedCap device is allowed to send WUS to the network device, the terminal device sends WUS to the network device within the first cell. That is, S905 is executed as described below.

[0189] S904, the terminal device performs cell reselection.

[0190] S905, the terminal device sends a first preamble (i.e., WUS) to the network device corresponding to the first cell according to the first WUS configuration information. Correspondingly, the low-power receiver of the network device corresponding to the first cell detects the first preamble sent by the terminal device.

[0191] Optionally, the terminal device selects a first preamble from the preamble sequence set included in the first WUS configuration information and sends it as WUS to the network device. Since the first preamble belongs to the preamble sequence set, the first preamble is used to request the network device to send SIB1 to the terminal device as needed.

[0192] When the network device is in deep power-saving mode, the main radio frequency transceiver module of the network device is turned off, and the low-power receiver of the network device is actually listening to the first preamble sent by the terminal device in the pre-configured PRACH.

[0193] S906: When the low-power receiver determines that the first preamble belongs to the preamble sequence set, it sends a wake-up command to the main RF transceiver module. Correspondingly, the main RF transceiver module receives the wake-up command.

[0194] The wake-up command is used to instruct the main radio frequency transceiver module to switch from sleep mode to active mode.

[0195] Optionally, when the low-power receiver detects the first preamble sent by the terminal device and determines that the first preamble belongs to the preamble sequence set, the low-power receiver determines that the first preamble is used to wake up the main RF transceiver module to send OD-SIB1 to the terminal device. Further, the low-power receiver sends a wake-up command to the main RF transceiver module to wake it up. This avoids the problem of the main RF transceiver module continuously being in an active state and consuming a large amount of power, which helps to reduce the power consumption of the network device. After the main RF transceiver module switches from sleep state to active state, it performs preheating and calibration to improve the reliability and accuracy of the SIB1 subsequently transmitted by the main RF transceiver module.

[0196] The warm-up and calibration process of the main RF transceiver module is as follows: After waking up, the main RF transceiver module powers on the device and warms up (e.g., for 5 minutes) to ensure the stability of the local oscillator and amplifier inside the main RF transceiver module. The main RF transceiver module calibrates the RF front-end parameters, such as the low-noise amplifier, filters, and the phase of each channel. Furthermore, the main RF transceiver module performs baseband synchronization and compensation to achieve alignment with the time and frequency domains of the terminal device.

[0197] S907, the main radio frequency transceiver module sends OD-SIB1 to the terminal device, and the corresponding terminal device receives OD-SIB1.

[0198] Optionally, the main RF transceiver module uses a PDCCH scrambled with a System Information Radio Network Temporary Identifier (SI-RNTI) to indicate the transmission resources (i.e., time domain resources and / or frequency domain resources) of the PDSCH carrying OD-SIB1. Within the agreed OD-SIB1 window, the main RF transceiver module sends OD-SIB1 to the terminal device on the transmission resources indicated by the PDCCH. Within the agreed OD-SIB1 window, the terminal device uses the SI-RNTI to listen to the PDCCH to detect the presence of scheduling information specific to itself. When the terminal device detects downlink control information scrambled with SI-RNTI within the OD-SIB1 window, it locates the PDSCH carrying SIB1 based on this DCI, thereby obtaining OD-SIB1.

[0199] S908, terminal devices perform random access based on OD-SIB1.

[0200] In the embodiments of this application, the implementation process of S808 can refer to the implementation process of S203 described above, and will not be repeated here.

[0201] It should be understood that Figures 1 to 9 The flowcharts or scene diagrams shown are for illustrative purposes only and are not intended to limit the embodiments of this application to the examples illustrated. In fact, those skilled in the art can interpret the embodiments based on... Figures 1 to 9 The examples in the document can be transformed into equivalent ways to obtain more implementations.

[0202] The above text combined Figures 1 to 9 This document describes in detail the communication method provided in the embodiments of this application. The following will combine... Figures 10 to 11 The device embodiments of this application are described in detail below. It should be understood that the communication device of this application embodiment can execute the various communication methods of the foregoing embodiments of this application, that is, the specific working processes of the various products below can be referred to the corresponding processes in the foregoing method embodiments.

[0203] In the embodiments described above, the terminal device may execute some or all of the steps in each embodiment; the network device may execute some or all of the steps in each embodiment. These steps or operations are merely examples, and the embodiments of this application may also perform other operations or variations thereof. Furthermore, the steps may be executed in different orders as presented in the embodiments, and it is not necessary to execute all the operations in the embodiments of this application. Moreover, the sequence number of each step does not imply the order of execution; the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0204] Figure 10 This is a schematic block diagram of a communication device provided in an embodiment of this application. Figure 10 As shown, the communication device may include a communication module 1020. The communication module 1020 can implement corresponding communication functions, which can be internal communication functions of the communication device or communication functions between the communication device and other devices. Optionally, the communication module 1020 may also be referred to as a communication interface or transceiver module. Optionally, the communication device further includes a processing module 1010. The processing module 1010 can implement corresponding processing functions.

[0205] Optionally, the communication device further includes a storage module, which can be used to store instructions and / or data; the processing module 1010 can read the instructions and / or data in the storage module so that the communication device can implement the aforementioned method embodiments.

[0206] In one possible design, the communication device may correspond to the terminal device in the above method embodiments, or to a component (such as a circuit, chip, or chip system) configured in the terminal device. The communication device can be used to execute the steps or processes performed by the terminal device in any of the above method embodiments.

[0207] For example, the communication module 1020 is used by the transceiver module to receive a master information block from a network device in a first cell; when the first cell supports a network power saving mode, the master information block carries a first index value, which is used to determine the first WUS configuration information corresponding to the first index value from at least one set of pre-configured wake-up signal WUS configuration information.

[0208] The communication module 1020 is also used to send a WUS to the network device in the first cell according to the first WUS configuration information, and then receive an OD-SIB1 from the network device in the first cell; wherein, the WUS is used to wake up the network device to send the on-demand request system information block OD-SIB1 to the terminal device.

[0209] The above are merely examples; for detailed steps or procedures, please refer to the descriptions in the foregoing embodiments.

[0210] In one possible design, the communication device may correspond to the network device in the above method embodiments, or to a component (such as a circuit, chip, or chip system) configured in the network device. The communication device can be used to perform the steps or processes executed by the network device in any of the above method embodiments.

[0211] For example, the communication module 1020 is used to send a main information block to a terminal device in a first cell; wherein, when the first cell supports a network power saving mode, the main information block carries a first index value, the first index value is used to determine the first WUS configuration information corresponding to the first index value from at least one set of pre-configured wake-up signal (WUS) configuration information.

[0212] The communication module 1020 is also used to receive the WUS sent by the terminal device according to the first WUS configuration information, and then send OD-SIB1 to the terminal device. The WUS is used to wake up the network device to send the on-demand system information block OD-SIB1 to the terminal device.

[0213] The above are merely examples; for detailed steps or procedures, please refer to the descriptions in the foregoing embodiments.

[0214] Figure 11 This is a schematic block diagram of another communication device provided in an embodiment of this application. The communication device may be a chip, chip system, or processor, etc., in a terminal device or network device that implements the above-described method. This communication device can be used to implement the methods described in the above-described method embodiments; for details, please refer to the descriptions in the above-described method embodiments.

[0215] like Figure 11 As shown, the communication device may include one or more processors 1110, which may also be referred to as processing units or processing modules, and can implement certain control functions. The processor 1110 can be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, while the central processing unit can be used to control the communication device (e.g., base station, baseband chip, user, user chip), execute software programs, and process data from the software programs.

[0216] In an alternative design, the processor 1110 may also store instructions and / or data, which can be executed by the processor 1110 to cause the communication device to perform the methods described in the above method embodiments.

[0217] In another alternative design, the communication device may include a communication interface 1120 for implementing receiving and transmitting functions. For example, the communication interface 1120 may be a transceiver circuit, interface, interface circuit, or transceiver. The transceiver circuit, interface, interface circuit, or transceiver for implementing receiving and transmitting functions may be separate or integrated. The aforementioned transceiver circuit, interface, interface circuit, or transceiver may be used for reading and writing code / data, or it may be used for transmitting or relaying signals.

[0218] Optionally, the communication device may include one or more memories 1130, which may store instructions that can be executed on the processor 1110, causing the communication device to perform the methods described in the above method embodiments. Optionally, the memories 1130 may also store data. Optionally, the processor 1110 may also store instructions and / or data. The processor 1110 and the memories 1130 may be provided separately or integrated together.

[0219] It should be understood that, in one possible design, the steps in the method embodiments provided in this application can be implemented by integrated logic circuits in the processor's hardware or by instructions in software form. The steps of the methods disclosed in the embodiments of this application can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules in the processor. The software modules can reside 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. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method. To avoid repetition, detailed descriptions are not provided here.

[0220] In one implementation, the communication device may correspond to the terminal device in the above method embodiments and may be used to execute the various steps and / or processes executed by the terminal device in the above method embodiments. The processor 1110 may be used to execute instructions stored in the memory 1130, and when the processor 1110 executes the instructions stored in the memory, the processor 1110 is used to execute the various steps and / or processes of the above method embodiments corresponding to the terminal device.

[0221] In another implementation, the communication device may correspond to the network device in the above method embodiments and may be used to execute the various steps and / or processes executed by the network device in the above method embodiments. The processor 1110 may be used to execute instructions stored in the memory 1130, and when the processor 1110 executes the instructions stored in the memory, the processor 1110 is used to execute the various steps and / or processes of the above method embodiments corresponding to the network device.

[0222] It should be understood that the aforementioned processing device can be one or more chips. For example, the processing device can be a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), a system-on-chip (SoC), a central processor unit (CPU), a network processor (NP), a digital signal processor (DSP), a microcontroller unit (MCU), a programmable logic device (PLD), or other integrated chips.

[0223] It is understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0224] According to the method provided in the embodiments of this application, this application also provides a chip system, which includes one or more processors for calling and executing instructions stored in memory, thereby causing the method described in the embodiments of this application to be executed. The chip system may be composed of chips or may include chips and other discrete devices.

[0225] The chip system may include input circuits or interfaces for transmitting information or data, and output circuits or interfaces for receiving information or data.

[0226] According to the method provided in the embodiments of this application, this application also provides a communication system, which includes the aforementioned network device and terminal device.

[0227] According to the method provided in the embodiments of this application, this application also provides a computer program product, which includes: computer program code, which, when run on a computer, causes the computer to execute the various steps or processes executed by the network device or terminal device in any of the foregoing method embodiments.

[0228] According to the method provided in the embodiments of this application, this application also provides a computer-readable storage medium storing program code, which, when run on a computer, causes the computer to execute the various steps or processes executed by the network device or terminal device in any of the foregoing method embodiments.

[0229] The computer-readable storage medium may be the aforementioned volatile memory or non-volatile memory, or it may include both volatile memory and non-volatile memory.

[0230] In the embodiments of this application, the terms and English abbreviations are exemplary examples given for ease of description and should not be construed as limiting the application in any way. This application does not preclude the possibility of defining other terms that can achieve the same or similar functions in existing or future agreements.

[0231] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions. When these computer instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated.

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

[0233] It should be understood that in the various embodiments of this application, the sequence number of each process does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0234] In summary, the above description is merely a preferred embodiment of the technical solution of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application.

Claims

1. A communication method, characterized in that, Applied to a terminal device, the method includes: Within the first cell, a master information block is received from a network device; if the first cell supports a network power saving mode, the master information block carries a first index value, which is used to determine the first WUS configuration information corresponding to the first index value from at least one pre-configured set of wake-up signal (WUS) configuration information. According to the first WUS configuration information, a WUS is sent to the network device in the first cell; wherein, the WUS is used to wake up the network device to send the on-demand request system information block OD-SIB1 to the terminal device; The OD-SIB1 is received from the network device within the first cell.

2. The method according to claim 1, characterized in that, The main information block also carries first indication information, which is used to indicate whether the first cell supports the network energy-saving mode.

3. The method according to claim 1 or 2, characterized in that, The main information block includes a first field; If the first cell supports the network energy-saving mode, the first field carries the first index value; When the first cell supports a non-network power saving mode, the first field is used to configure the Physical Downlink Control Channel (PDCCH), which is used to schedule SIB1.

4. The method according to claim 3, characterized in that, The first field is the pdcch-ConfigSIB1 field in the main information block.

5. The method according to claim 1 or 2, characterized in that, The at least one set of WUS configuration information belongs to the WUS configuration table; wherein, the WUS configuration table includes at least one record, each record corresponding to an index value and a set of WUS configuration information; or, each record corresponds to an index value range and a set of WUS configuration information.

6. The method according to claim 5, characterized in that, The method further includes: Receive first configuration information from the network device; the first configuration information is used to configure the WUS configuration table.

7. The method according to claim 1 or 2, characterized in that, Each set of WUS configuration information includes at least: reference transmission resources for the random access channel PRACH used to transmit the WUS, a set of preamble sequences, the starting offset of the window, the preamble format, and second indication information; The reference transmission resources include reference frequency domain resources and / or reference time domain resources; the second indication information is used to indicate whether the energy-saving terminal RedCap device is allowed to send the WUS to the network device.

8. The method according to claim 7, characterized in that, Sending WUS to the network device within the first cell includes: If the second indication information indicates that the RedCap device is allowed to send the WUS to the network device, and the terminal device is the RedCap device, or if the terminal device is not the RedCap device, the WUS is sent to the network device within the first cell.

9. The method according to claim 7, characterized in that, The method further includes: If the second indication information indicates that the RedCap device is not allowed to send the WUS to the network device, and the terminal device is the RedCap device, the terminal device performs cell reselection.

10. The method according to claim 7, characterized in that, The method further includes: In response to sending the WUS, a first timer is started, the duration of which is the duration corresponding to the starting offset of the window; Receiving the OD-SIB1 from the network device within the first cell includes: In response to the expiration of the first timer, the OD-SIB1 is received in the SIB1 window.

11. The method according to claim 7, characterized in that, The frequency domain resources of the PRACH are the reference frequency domain resources, or the frequency domain resources of the PRACH are determined based on the first index value, the physical cell identifier of the first cell, and the frequency domain bandwidth; wherein, the frequency domain bandwidth is the product of the number of resource blocks occupied by the preamble format corresponding to the first index value, the subcarrier spacing, and the first value.

12. The method according to claim 11, characterized in that, The frequency domain resources of the PRACH are determined based on the first index value, the physical cell identifier of the first cell, and the frequency domain bandwidth, including: The reference frequency domain resource corresponding to the first index value is obtained by querying the WUS configuration table; The third value is obtained by multiplying the remainder obtained by dividing the physical cell identifier of the first cell by the second value and the frequency domain bandwidth. The sum of the reference frequency domain resource corresponding to the first index value and the third value is determined as the frequency domain resource of the PRACH.

13. A communication method, characterized in that, Applied to network devices, the method includes: A master information block is sent to the terminal device in the first cell; wherein, if the first cell supports network power saving mode, the master information block carries a first index value, the first index value is used to determine the first WUS configuration information corresponding to the first index value from at least one set of wake-up signal WUS configuration information; each set of WUS configuration information is used to configure the terminal device to send WUS; The terminal device receives a WUS sent by the terminal device according to the first WUS configuration information; wherein the WUS is used to wake up the network device to send an On-Demand System Information Block (OD-SIB1) to the terminal device. Send the OD-SIB1 to the terminal device.

14. The method according to claim 13, characterized in that, The main information block also carries first indication information, which is used to indicate whether the first cell supports the network energy-saving mode.

15. The method according to claim 13 or 14, characterized in that, The main information block includes a first field; If the first cell supports the network energy-saving mode, the first field carries the first index value; When the first cell supports a non-network power saving mode, the first field is used to configure the Physical Downlink Control Channel (PDCCH), which is used to schedule SIB1.

16. The method according to claim 15, characterized in that, The first field is the pdcch-ConfigSIB1 field in the main information block.

17. The method according to claim 13 or 14, characterized in that, The at least one set of WUS configuration information belongs to the WUS configuration table; wherein, the WUS configuration table includes at least one record, each record corresponding to an index value and a set of WUS configuration information; or, each record corresponds to an index value range and a set of WUS configuration information.

18. The method according to claim 17, characterized in that, The method further includes: Send first configuration information to the terminal device; the first configuration information is used to configure the WUS configuration table.

19. The method according to claim 13 or 14, characterized in that, Each set of WUS configuration information includes at least: reference transmission resources for transmitting the PRACH of the WUS, a set of preamble sequences, the starting offset of the window, the preamble format, and second indication information; The reference transmission resources include reference frequency domain resources and / or reference time domain resources; the second indication information is used to indicate whether the energy-saving terminal RedCap device is allowed to send the WUS to the network device.

20. The method according to claim 19, characterized in that, Receiving the WUS sent by the terminal device in the first cell according to the WUS configuration information includes: If the second indication information indicates that the RedCap device is not allowed to send the WUS to the network device, and the terminal device is not the RedCap device, or if the second indication information indicates that the RedCap device is allowed to send the WUS to the network device, the terminal device shall receive the WUS sent by the terminal device in the first cell according to the WUS configuration information.

21. The method according to claim 19, characterized in that, The network device includes a low-power receiver and a main radio frequency transceiver module, and the method further includes: The low-power receiver detects a first preamble sent by the terminal device; wherein the first preamble is the WUS; When the low-power receiver determines that the first preamble belongs to the preamble sequence set, the low-power receiver sends a wake-up command to the main radio frequency transceiver module. The wake-up command is used to instruct the main radio frequency transceiver module to switch from a sleep state to an active state.

22. A communication device comprising one or more processors, a memory, and a computer program stored in the memory, characterized in that, The processor executes the computer program to implement the method of any one of claims 1-12; and / or, to implement the method of any one of claims 13-21.

23. A chip system comprising a memory and a processor, characterized in that, When the program / instructions stored in the memory are executed by the processor, they implement the method of any one of claims 1-12; and / or, implement the method of any one of claims 13-21.

24. A communication system, characterized in that, It includes a terminal device and a network device; wherein the terminal device is used to perform the method of any one of claims 1-12; and / or, the network device is used to perform the method of any one of claims 13-21.

25. A computer-readable storage medium having a computer program / instructions stored thereon, characterized in that, When the computer program / instructions are executed by the processor, they implement the method of any one of claims 1-12; and / or, implement the method of any one of claims 13-21.

26. A computer program product, characterized in that, The computer program product includes: a computer program or instructions that, when executed on a computer, cause the computer to perform the method of any one of claims 1-12; and / or to implement the method of any one of claims 13-21.

Images