Wireless communication method and apparatus for node

Abstract

Provided are a wireless communication method and apparatus for a node. The method comprises: a first node receiving first information, wherein the first information comprises a first parameter, a second parameter and a configuration parameter for second information; and sending the second information, wherein the second information is used for requesting third information, the second information is a wake-up signal, the third information is on-demand SIB1 information, the first parameter is used for identifying a cell type, the second parameter is used for indicating the length of a time window for reading the third information, the configuration parameter for the second information comes from a target cell of the first node or a cell on which the first node initially camps, the target cell is a serving cell or a network energy saving (NES) cell, and the cell on which the first node initially camps is a non-energy-saving cell.

Description

Methods and apparatus for wireless communication of nodes Technical Field

[0001] This application relates to the field of communication technology, and more specifically, to a method and apparatus for wireless communication for nodes. Background Technology

[0002] To achieve network energy saving (NES), network devices can send System Information Block (SIB) 1 only after receiving a request from a terminal device, thereby reducing unnecessary SIB 1 transmissions and associated monitoring. However, how the network device can transmit SIB 1 on demand after the terminal device requests it, and how the terminal device can receive SIB 1 on demand, are technical problems that urgently need to be solved. Summary of the Invention

[0003] This application provides a method and apparatus for wireless communication of nodes. The various aspects related to the embodiments of this application are described below.

[0004] In a first aspect, a method for wireless communication for a first node is provided, comprising: receiving first information, the first information including first parameters, second parameters, and configuration parameters of second information; sending the second information, the second information being used to request third information; wherein the second information is a wake-up signal, the third information is on-demand SIB1 information, the first parameter is used to identify a cell type, the second parameter is used to indicate the length of a time window for reading the third information; the configuration parameters of the second information are from a target cell or a cell where the first node first camps, the target cell being a serving cell or a network-efficient cell, and the cell where the first node first camps being a non-efficient cell.

[0005] In a second aspect, a method for wireless communication for a second node is provided, comprising: sending first information, the first information including first parameters, second parameters, and configuration parameters of the second information; receiving the second information, the second information being used to request third information; wherein the second information is a wake-up signal, the third information is on-demand SIB1 information, the first parameter is used to identify the cell type, the second parameter is used to indicate the length of the time window for reading the third information; the configuration parameters of the second information are from the target cell or the cell to which the first node first camps, the target cell being a serving cell or a network energy-saving (NES) cell, and the cell to which the first node first camps being a non-energy-saving cell.

[0006] Thirdly, a first node for wireless communication is provided, including a first transceiver module; the first transceiver module is used to receive first information, the first information including first parameters, second parameters, and configuration parameters of the second information; and to send the second information, the second information being used to request third information; wherein the second information is a wake-up signal, the third information is on-demand SIB1 information, the first parameter is used to identify the cell type, the second parameter is used to indicate the length of the time window for reading the third information; the configuration parameters of the second information come from the target cell or the cell to which the first node first camps, the target cell being a serving cell or a network energy-saving cell, and the cell to which the first node first camps being a non-energy-saving cell.

[0007] Fourthly, a second node for wireless communication is provided, including a second transceiver module for:

[0008] Send first information, which includes a first parameter, a second parameter, and configuration parameters for the second information; receive the second information, which is used to request third information; wherein the second information is a wake-up signal, the third information is on-demand SIB1 information, the first parameter is used to identify the cell type, the second parameter is used to indicate the length of the time window for reading the third information; the configuration parameters of the second information come from the target cell or the cell where the first node first camps, the target cell is a serving cell or a network energy-saving cell, and the cell where the first node first camps is a non-energy-saving cell.

[0009] Fifthly, a communication device is provided, including a memory and a processor, the memory for storing a program, and the processor for calling the program in the memory to perform the method as described in the first or second aspect.

[0010] In a sixth aspect, a first node for wireless communication is provided, comprising a transceiver, a memory, and a processor, wherein the memory stores a program, the processor invokes the program in the memory, and controls the transceiver to receive or transmit signals to cause the first node to perform the method as described in the first aspect.

[0011] In a seventh aspect, a second node for wireless communication is provided, comprising a transceiver, a memory, and a processor, wherein the memory stores a program, the processor invokes the program in the memory, and controls the transceiver to receive or transmit signals to cause the second node to perform the method as described in the second aspect.

[0012] Eighthly, embodiments of this application provide a communication system including the aforementioned first node and / or second node. In another possible design, the system may further include other devices that interact with the first node or second node as provided in the embodiments of this application.

[0013] Ninthly, embodiments of this application provide a computer-readable storage medium storing a computer program that causes a computer to perform some or all of the steps in the methods described above.

[0014] In a tenth aspect, embodiments of this application provide a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program operable to cause a computer to perform some or all of the steps of the methods described in the foregoing aspects. In some implementations, the computer program product may be a software installation package.

[0015] In one aspect, embodiments of this application provide a chip including a memory and a processor, the processor being able to call and run a computer program from the memory to implement some or all of the steps described in the methods of the foregoing aspects.

[0016] In this embodiment, the terminal device requests the network device to send SIB1 based on parameters from the first information received from the second node, using the second information. After receiving the parameters from the first information, the terminal device can determine the cell type to which the parameters apply, which helps to improve system performance while achieving network energy saving. Attached Figure Description

[0017] Figure 1 shows the wireless communication system used in an embodiment of this application.

[0018] Figure 2 is a schematic diagram of the network architecture used in the embodiments of this application.

[0019] Figures 3A and 3B are schematic diagrams of the structure of the wireless protocol stack used in the embodiments of this application.

[0020] Figure 4 is a schematic diagram of the reuse of SSB and CORESET#0 provided in an embodiment of this application.

[0021] Figure 5 is a schematic diagram of a CD-SSB pointing to cell A on an NES cell synchronization grating provided in an embodiment of this application.

[0022] Figure 6 is a flowchart illustrating a method for wireless communication provided in an embodiment of this application.

[0023] Figure 7 is a schematic diagram of WUS configuration of an NES cell SSB provided in an embodiment of this application.

[0024] Figure 8 is a schematic diagram of a cell transmitting SIB1 on demand based on a wake-up signal, according to an embodiment of this application.

[0025] Figure 9 is a schematic diagram of a device for wireless communication provided in an embodiment of this application.

[0026] Figure 10 is a schematic diagram of another device for wireless communication provided in an embodiment of this application.

[0027] Figure 11 is a schematic diagram of the structure of a communication device provided in an embodiment of this application.

[0028] Figure 12 is a schematic diagram of the hardware module of the communication device provided in the embodiment of this application. Detailed Implementation

[0029] The technical solutions of the embodiments of this application will be described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments.

[0030] The embodiments of this application can be applied to various communication systems. For example, the embodiments of this application can be applied to Global System for Mobile Communication (GSM), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), and General Packet Radio Service (GPRS). Furthermore, the embodiments of this application can be applied to Long Term Evolution (LTE) systems, Advanced Long Term Evolution (LTE-A) systems, 5th-generation (5G) communication systems or New Radio (NR) systems, evolution systems of NR systems, LTE-based access to unlicensed spectrum (LTE-U) systems, NR-based access to unlicensed spectrum (NR-U) systems, Universal Mobile Telecommunications System (UMTS), Wireless Local Area Networks (WLAN) systems, and Wireless Fidelity (WiFi) systems. The embodiments of this application can also be applied to other communication systems, such as 6th-generation (6G) communication systems, or future communication systems such as satellite communication systems.

[0031] Traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, communication systems can support not only traditional cellular communication but also one or more other types of communication. For example, a communication system can support one or more of the following communication methods: device-to-device (D2D) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), enhanced machine-type communication (eMTC), vehicle-to-vehicle (V2V) communication, and vehicle-to-everything (V2X) communication. The embodiments of this application can also be applied to communication systems that support the above-mentioned communication methods.

[0032] The communication system in this application embodiment can be applied to carrier aggregation (CA) scenarios, dual connectivity (DC) scenarios, and standalone (SA) network deployment scenarios.

[0033] The communication system in this application embodiment can be applied to unlicensed spectrum. This unlicensed spectrum can also be considered a shared spectrum. Alternatively, the communication system in this application embodiment can also be applied to licensed spectrum. This licensed spectrum can also be considered a dedicated spectrum.

[0034] The embodiments of this application can be applied to non-terrestrial network (NTN) systems. As an example, the NTN system can be a 4G-based NTN system, an NR-based NTN system, an Internet of Things (IoT)-based NTN system, or a narrowband Internet of Things (NB-IoT)-based NTN system.

[0035] A communication system may include one or more terminal devices. The terminal devices mentioned in the embodiments of this application may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent, or user device, etc.

[0036] In some embodiments, the terminal device may be a station (ST) in a WLAN. In some embodiments, the terminal device may be a cellular phone, cordless phone, session initiation protocol (SIP) phone, wireless local loop (WLL) station, personal digital assistant (PDA) device, handheld device with wireless communication capabilities, computing device or other processing device connected to a wireless modem, in-vehicle device, wearable device, terminal device in a next-generation communication system (e.g., NR system), or terminal device in a future public land mobile network (PLMN) network, etc.

[0037] In some embodiments, the terminal device may be a device that provides voice and / or data connectivity to a user. For example, the terminal device may be a handheld device, an in-vehicle device, etc., with wireless connectivity. As some specific examples, the terminal device may be a mobile phone, tablet, laptop, PDA, camera device, mobile internet device (MID), wearable device, virtual reality (VR) device, augmented reality (AR) device, wireless terminal in industrial control, wireless terminal in self-driving, wireless terminal in remote medical surgery, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, wireless terminal in smart home, etc.

[0038] In some embodiments, the terminal device may be deployed on land. For example, the terminal device may be deployed indoors or outdoors. In some embodiments, the terminal device may be deployed on water, such as on a ship. In some embodiments, the terminal device may be deployed in the air, such as on an airplane, balloon, or satellite.

[0039] In addition to terminal devices, the communication system may also include one or more network devices. In this embodiment, the network device can be a device for communicating with the terminal device; this network device may also be referred to as an access network device or a radio access network device. For example, the network device may be a base station. In this embodiment, the network device may refer to a radio access network (RAN) node (or device) that connects the terminal device to the wireless network. A base station can broadly encompass, or be replaced by, various names including: NodeB, evolved NodeB (eNB), next-generation NodeB (gNB), relay station, access point (AP), transmitting and receiving point (TRP), transmitting point (TP), master station (MeNB), secondary station (SeNB), multi-mode radio (MSR) node, home base station, network controller, access node, wireless node, transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. A base station can be a macro base station, micro base station, relay node, donor node, or a combination thereof. A base station can also refer to a communication module, modem, or chip installed within the aforementioned equipment or apparatus. Base stations can also be mobile switching centers, devices that perform base station functions in D2D, V2X, and M2M communications, network-side devices in 6G networks, and devices that perform base station functions in future communication systems. Base stations can support networks using the same or different access technologies. The embodiments of this application do not limit the specific technologies or device forms used in the network equipment.

[0040] Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move depending on the location of the mobile base station. In other examples, a helicopter or drone can be configured as a device to communicate with another base station.

[0041] In some deployments, the network device in this application embodiment may refer to a CU or a DU, or the network device may include both a CU and a DU. The gNB may also include an AAU.

[0042] By way of example and not limitation, in the embodiments of this application, the network device may have mobility characteristics; for example, the network device may be a mobile device. In some embodiments of this application, the network device may be a satellite or a balloon station. In some embodiments of this application, the network device may also be a base station located on land, water, or other similar locations.

[0043] In this embodiment, the network device can provide services to a cell. The terminal device communicates with the network device through the transmission resources (e.g., frequency domain resources, or spectrum resources) used by the cell. The cell can be the cell corresponding to the network device (e.g., a base station). The cell can belong to a macro base station or to a base station corresponding to a small cell. The small cell can include: metro cell, micro cell, pico cell, femto cell, etc. These small cells have the characteristics of small coverage area and low transmission power, and are suitable for providing high-speed data transmission services.

[0044] For example, FIG1 is a schematic diagram of the architecture of a wireless communication system provided in an embodiment of this application. The wireless communication system 100 shown in FIG1 includes a network device and multiple terminal devices. The network device 110 can provide communication coverage for a specific geographical area and can communicate with terminal devices located within the coverage area. The multiple terminal devices are, for example, terminal devices 120a to 120j in FIG1.

[0045] Optionally, the wireless communication system 100 shown in FIG1 may further include multiple network devices and each network device may include other number of terminal devices within its coverage area. This application embodiment does not limit this.

[0046] In the embodiments of this application, the communication system shown in FIG1 may also include various network entities, and the embodiments of this application do not limit this.

[0047] For example, Figure 2 is a schematic diagram of a network structure applying an embodiment of this application. The network architecture 200 in Figure 2 is the network architecture of a 5G NR / LTE / LTE-A system. The 5G NR / LTE / LTE-A network architecture can also be referred to as a 5G system (5GS) / evolved packet system (EPS) network architecture. This network architecture 200 includes at least one of network equipment 110, terminal equipment 120, 5G core network (5GC) / evolved packet core (EPC) 210, home subscriber server (HSS) / unified data management (UDM) 220, and Internet service 230. The network equipment and terminal equipment in Figure 2 are illustrated using RAN and UE as examples, respectively.

[0048] As shown in Figure 2, network device 110 provides user plane and control plane protocol termination to terminal device 120. Network device 110 is connected to 5GC / EPC 210 via an S1 / NG interface. 5GC / EPC 210 includes a mobility management entity (MME) / authentication management field (AMF) / session management function (SMF) 211, other MMEs / AMFs / SMFs 214, a service gateway (S-GW) / user plane function (UPF) 212, and a packet data network gateway (P-GW) / UPF 213. MME / AMF / SMF 211 is the control node that handles signaling between terminal device 120 and 5GC / EPC 210. Generally, MME / AMF / SMF 211 provides bearer and connection management. All user Internet Protocol (IP) packets are transmitted through the S-GW / UPF212, which is itself connected to the P-GW / UPF213. The P-GW provides UE IP address allocation and other functions. The P-GW / UPF213 is connected to Internet service 230. Internet service 230 includes operator-compliant Internet Protocol services, specifically including the Internet, intranet, IP multimedia subsystem (IMS), and packet-switched streaming services. It is evident that network architecture 200 provides packet-switched services; however, those skilled in the art will readily understand that the various concepts presented herein can be extended to networks providing circuit-switched services or other cellular networks.

[0049] Figures 3A and 3B respectively illustrate the structural diagrams of the wireless protocol stack using embodiments of this application. Figures 3A and 3B use the 5G wireless protocol stack as an example for illustration. The 5G wireless protocol stack is divided into two planes: the user plane (UP) protocol stack and the control plane (CP) protocol stack. The user plane protocol stack is the protocol suite used for user data transmission, and the control plane protocol stack is the protocol suite used for control signaling transmission in the 5G system. The specific names of each protocol stack layer are as follows:

[0050] As shown in Figure 3A, the user plane protocol stack includes, from top to bottom, the following layers: Service Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, Medium Access Control (MAC) layer, and Physical (PHY) layer.

[0051] As shown in Figure 3B, the control plane protocol stack includes, from top to bottom: non-access stratum (NAS); radio resource control (RRC) layer, PDCP layer, RLC layer, MAC layer, and PHY layer.

[0052] It should be understood that the different layers in the above protocol stack have different functions, and they work together through inter-layer interaction to achieve communication between terminal devices and network devices. With the development of artificial intelligence technology, AI-assisted computing has permeated the processing implementation methods of the above protocol stack. For example, the scheduling algorithm of the MAC layer and the encoding / decoding algorithm of the PHY layer can apply artificial intelligence algorithms to improve the performance of communication algorithms.

[0053] As an example, the wireless protocol architecture in Figures 3A and 3B is applicable to the terminal device in this application, such as a UE.

[0054] As an example, the wireless protocol architecture in Figures 3A and 3B is applicable to the network devices in this application, such as gNB.

[0055] It should be understood that devices with communication functions in the network / system of this application embodiment can be referred to as communication devices. The interpretation of terms in this application embodiment can refer to the TS36, TS37, and TS38 series of specifications from the 3rd Generation Partnership Project (3GPP), and also to the specifications from the Institute of Electrical and Electronics Engineers (IEEE).

[0056] To facilitate understanding, some related technical knowledge involved in the embodiments of this application is first introduced. The following related technologies are optional solutions and can be arbitrarily combined with the technical solutions of the embodiments of this application, all of which fall within the protection scope of the embodiments of this application. The embodiments of this application include at least some of the following contents.

[0057] With the development of mobile communication technology, next-generation wireless evolution systems (such as 5G systems) employ various technologies to improve data transmission rates to meet the data volume transmission demands of high-definition video, virtual reality, and other applications. These technologies include massive MIMO (multiple-input multiple-output) technology, non-orthogonal multiple access (NOMA), simultaneous full-duplex communication on the same frequency, novel modulation techniques, novel coding techniques, and higher-order modulation techniques. Through these technologies, peak data rates of up to Gbit / s can be achieved.

[0058] As an example, the latency level of the air interface needs to be around 1ms to meet the needs of real-time applications such as autonomous driving and telemedicine.

[0059] As an example, the massive network capacity can provide connectivity for hundreds of billions of devices, thereby meeting the communication needs of the Internet of Things.

[0060] As an example, the spectral efficiency of NR systems is more than 10 times higher than that of LTE systems. Based on continuous wide-area coverage and high mobility, user experience speeds can reach 100 Mbit / s. This demonstrates a significant increase in traffic density and connection density.

[0061] Furthermore, the improved system coordination and intelligence further enhance network flexibility. System coordination can manifest as collaborative networking involving multiple users, multiple points, multiple antennas, and multiple inputs. Based on coordination and intelligence, networks can flexibly and automatically adjust to each other.

[0062] However, in communication systems, network devices (e.g., base station equipment) typically consume a relatively high amount of power. To conserve the power of base station equipment, system messages need to be optimized. For ease of understanding, the following explanation uses NR system messages as an example.

[0063] NR system messages can be divided into Master Information Block (MIB) messages and some SIB messages. MIB messages are typically sent on the broadcast channel (BCH). The MIB transmission period is 80ms. MIBs can be retransmitted within this 80ms period. Additionally, MIB messages include parameters required by the terminal device to obtain SIB1 messages from the cell.

[0064] SIB1 messages can also be called SIB type 1 messages. SIB1 messages are transmitted on the downlink-shared channel (DL-SCH) with a period of 160ms. Within 160ms, SIBs can also be repeatedly transmitted with a variable transmission repetition period. The default transmission repetition period for SIB1 is 20ms, but the actual transmission repetition period depends on the network implementation. For example, for multiplexing mode 1 of synchronization signal block (SSB) and control resource set (CORESET), the transmission repetition period for SIB1 is 20ms. As another example, for multiplexing modes 2 / 3 of SSB and CORESET, the transmission repetition period for SIB1 is the same as the period for SSB.

[0065] In the embodiments of this application, SSB may also represent a synchronization signal and PBCH block.

[0066] SIB1 can carry key information required for terminal equipment to access the cell, such as random access parameters. SIB1 also includes information related to the availability and scheduling of other SIBs, such as the mapping of other SIBs to system information (SI) messages, their periodicity, and SI window size. SIB1 can also indicate whether one or more SIBs are provided only on demand. In this case, SIB1 can also provide the physical random access channel (PRACH) configuration required by the terminal equipment to request the necessary SIs. SIB1 also contains radio resource configuration information common to all terminal equipment and cell prohibition information applied to unified access control.

[0067] When SIB1 includes information related to other SIBs, the other SIB messages can be provided either periodically broadcast or on demand. If the other SIBs are provided on demand, SIB1 may also include information for the terminal device to execute the SI request.

[0068] SIB messages other than SIB1 (other SIBs) can be included in SI messages. These messages can also be transmitted on DL-SCH. Each SI message can be transmitted periodically within a time-domain window (called an SI window). For example, only SIBs with the same periodicity can be mapped to the same SI message. When each SI message is sent within a periodically occurring time-domain window, all SI messages can have SI windows of the same length. Each SI message is associated with one SI window, and the SI windows of different SI messages do not overlap. That is, only the corresponding SI message is sent within an SI window. In addition, the system can send SI messages multiple times within an SI window.

[0069] After downlink synchronization is completed, the UE needs to receive the SIB1 message to obtain the configuration related to uplink synchronization before performing the RACH process to complete uplink synchronization. The SIB1 message is carried by the PDSCH. To receive / decode SIB1, the scheduling information of the PDSCH needs to be known, which requires monitoring the corresponding PDCCH carrying the scheduling information. The pdcch-ConfigSIB1 parameter is part of the MIB in 5G NR, used to configure the Physical Downlink Control Channel (PDCCH) associated with SIB1 (System Information Block 1). The pdcch-ConfigSIB1 parameter defines the CORESET (Control Resource Set) and Search Space, which are key time-frequency resources for the terminal device to decode the SIB1 message. The Search Space of the PDCCH corresponding to SIB1 is type0-PDCCH CSS, and the bound CORESET is CORESET#0 (the frequency bandwidth is the same as the initial BWP).

[0070] In beam management scenarios, pdcch-ConfigSIB1 must ensure that the beam direction of the PDCCH and SSB are consistent to support wide coverage and mobility. The specific design is shown in the table below:

[0071] As can be seen from the table, there are three different multiplexing modes between SSB and CORESET 0. For Pattern 1, referring to Figure 4, it can be used in frequency bands FR1 and FR2. The frequency domain of CORESET 0 includes SSB, and the two are mapped to different symbols in the time domain. Patterns 2 and 3 are only applicable to frequency band FR2. In the frequency domain, because FR2 has a much larger bandwidth, it can cover both SSB and CORESET 0 simultaneously.

[0072] The following section uses the NR system as an example to introduce a method for configuring time-frequency resources such as WUS request information based on the control resource set (CORESET) and search space. CORESET primarily describes the distribution of frequency domain resources, while the search space primarily describes the distribution of time domain resources. Therefore, specific time-frequency domain resources can be determined by pairing CORESET and search space.

[0073] In NR, the network typically configures multiple CORESETs and multiple search spaces in the bandwidth part (BWP). By pairing CORESETs and search spaces, multiple blocks of time-frequency resources can be identified for different purposes.

[0074] For example, CORESET and search space can be in one-to-one correspondence. For instance, a pair of time-frequency domain resources determined by CORESET and search space can be used to transmit downlink control information (DCI) format 0_0 / 1_0 (i.e., DCI_format0_0 / 1_0); another pair of time-frequency domain resources determined by CORESET and search space can be used to transmit DCI_format 0_1 / 1_1.

[0075] For example, CORESET and search space can be one-to-many. For instance, one CORESET can correspond to multiple search spaces.

[0076] For example, Searchspace 0 is configured for the MIB. The time-frequency domain resources determined by Searchspace 0 and CORESET 0 can be used by the terminal device to receive the remaining minimum system information (RMSI). RMSI includes SIB1. That is, Searchspace 0 and CORESET 0 can be used to indicate scheduling information for SIB1.

[0077] For example, based on the search space configured at the network end and its associated CORESET, the terminal device can determine the time-frequency resource scheduling status of the physical downlink control channel (PDCCH). In cells that transmit SIB1 on demand, the PDCCH transmitted by the network device can be used to carry the scheduling information of SIB1, so that the terminal device can receive SIB1. For example, the monitoring timing of the PDCCH corresponding to SIB1 can be indicated by the parameters searchSpaceZero and controlResourceSetZero.

[0078] The previous section used NR system messages as an example to introduce various SIB messages. Network devices (e.g., gNBs) can periodically send SIB1 for initial access and schedule other SIBs for terminal devices in idle / inactive modes. Even if there is no demand from a terminal device, or no terminal device is camped on the cell, the network device will still transmit SIB1. Therefore, in some scenarios, the periodic transmission of SIB1 by network devices may result in significant energy waste.

[0079] To achieve network energy conservation, it is necessary to reduce unnecessary SIB1 transmissions and associated PRACH monitoring. Therefore, on-demand SIB1 transmission to idle / inactive terminal devices has become a research direction, providing network devices with more opportunities to enter sleep mode. For example, how to implement on-demand SIB1 (OD-SIB1) transmission to save network device energy is a question that needs to be considered.

[0080] When an NES cell transmits a Synchronization Signal Block (SSB) on the Synchronization Raster, the subcarrier offset (K_SSB) parameter configured in its PBCH (Physical Broadcast Channel) payload must meet the following conditions: FR1: K_SSB > 23; FR2 (millimeter wave): K_SSB > 11. This configuration indicates that the NES cell's SSB does not contain the control resource set (CORESET0) of the Type 0 PDCCH Common Search Space (CSS), and CORESET0 is a necessary resource for a traditional UE (non-R19 UE) to listen for and obtain SIB1. Therefore, if a traditional UE detects the NES cell's SSB first during the initial cell search process, it will ignore the NES cell and will not attempt to camp on it because it cannot resolve SIB1 through CORESET0. The traditional UE will continue to search for other cells that conform to the 3GPP standard configuration (i.e., cells where kSSB is within the normal range and contains CORESET0). As shown in Figure 5, the UE scans and detects the Cell-Defining SSB (CD-SSB) of Cell A at the Sync Raster Point, completes time-frequency synchronization, and camps on Cell A. Cell A sends WUS configuration to the UE via RRC signaling or system information (such as SIB), including parameters such as the listening timing and frequency range of the NES cell. According to the instructions in the WUS configuration, the UE activates the receiver in a specific time window and attempts to detect the NES Cell SSB. If the detection is successful, the UE synchronizes to the NES cell and obtains its system information (such as SIB1); if it fails, it remains in sleep mode to save power.

[0081] In this embodiment, NES cells supporting On-Demand SIB1 (OD-SIB1) can manage SIB1 transmission through the following three states and associate them with specific subcarrier offset (kSSB) parameters, as shown in the table below:

[0082] As shown in the table, after a UE camps on an NES cell, if the K_SSB indicator state is state 2 or 3, blind detection is initiated. The blind detection steps include: a) Setting a time window: attempting decoding within the TSIB1-DETECT window after camping (configurable, e.g., 100ms). b) Monitoring resources: monitoring PDCCH DCI scheduling information (Type 0 CSS) to check for the existence of SIB1 scheduling authorization; or, directly monitoring PDSCH resources (based on the SIB1 location indicated by the MIB) to verify CRC checksum. If the detection is successful: directly decoding SIB1 without sending UL WUS. If the detection fails: the base station sends UL WUS to trigger an OD-SIB1 request. It is evident that UL WUS is only sent when blind detection fails, avoiding unnecessary OD-SIB1 triggering and reducing cell signaling overhead.

[0083] However, when a UE receives a WUS configuration from a base station, it cannot distinguish whether the received WUS configuration applies to the serving cell, an NES cell, or other cells. Therefore, this application provides a method for wireless communication for nodes, which instructs the terminal device to specify configuration parameters applicable to the NES cell itself via the NES cell, thereby distinguishing the cell type to which the received WUS configuration applies.

[0084] For ease of understanding, the method for wireless communication for a node according to an embodiment of this application is described below with reference to FIG6. FIG6 is a schematic flowchart of the method for wireless communication in a first node according to an embodiment of this application. FIG6 is described from the perspective of the first node.

[0085] As an example, the first node can be a network-controlled repeater (NCR).

[0086] As an example, the first node can be a terminal device. For example, terminal devices 120a to 120j shown in Figure 1. The second node can be a network device. For example, the second node is an access network device or a core network device. Another example is a gNB. Yet another example is an LMF. The following embodiments are basically illustrated with the UE as the first node and the gNB as the second node.

[0087] As an example, the first node can be a relay, such as a relay terminal.

[0088] As an example, the first node can be any type of network device, such as network device 110 shown in Figure 1.

[0089] In some embodiments, the first node may be in a connected state.

[0090] The method shown in Figure 6 may include steps S610 to S620, which are described below.

[0091] In S610, the first node receives the first information.

[0092] The first information includes at least one of the following: a first parameter, a second parameter, and configuration parameters of the second information.

[0093] In one possible embodiment, the first parameter is used to identify the cell type, such as whether the cell is an energy-efficient cell or a non-energy-efficient cell. For example, the first parameter is the subcarrier offset (K_SSB). Specifically, for an NES cell supporting on-demand SIB1, a K_SSB greater than 23 and not equal to 30 for the first frequency band FR1, and a K_SSB greater than 11 and not equal to 14 for the second frequency band FR2, both indicate that SIB1 on the NES cell is transmitted on demand.

[0094] In one possible embodiment, the second parameter is used to indicate the timing of reading the third information, or to indicate the length of the time window for the third information, or to indicate the timing of transmitting the third information.

[0095] In one possible embodiment, the configuration parameters of the second information can be used to decode SIB1.

[0096] In one embodiment, the configuration parameters in the second information may indicate whether the configuration parameter applies to the serving cell or to other cells.

[0097] In S620, the first node sends the second information, which is used to request the third information;

[0098] In some embodiments, the cell that transmits SIB1 on demand is called an energy-saving cell, or a network energy-saving (NES) cell. For terminal devices in idle mode or inactive state, since the NES cell does not carry SIB1 information when transmitting SSB, the terminal device needs to send the second information to request the NES cell to send SIB1 information. The second information can be the on-demand SIB1 request information. Optionally, the second information, i.e., the on-demand SIB1 request information, can be an uplink (UL) wake-up signal (WUS), or other on-demand information / signaling requesting the transmission of SIB1. The uplink wake-up signal can be represented as UL-WUS. UL-WUS is any uplink signal that can trigger the transmission of on-demand SIB1. The third information can be the on-demand SIB1 information.

[0099] Alternatively, the terminal device may transmit on-demand SIB1 request information via a random access channel (RACH) or a separate signal or sequence. For example, the terminal device may transmit WUS via PRACH.

[0100] In some embodiments, the terminal device can directly request on-demand SIB1 from the serving cell or NES cell, or it can request on-demand SIB1 from the anchor cell associated with the serving cell or NES cell. For example, to obtain SIB1 information of an NES cell, the terminal device can send WUS to the NES cell or the anchor cell. That is, the SIB1 information obtained by the terminal device can come from the NES cell or the anchor cell, and the anchor cell can be the cell where the terminal device first camps (also known as the source cell). The cell where the terminal device first camps can be a non-network energy-saving cell. Optionally, the configuration parameters of the second information can come from the target cell or the cell where the first node first camps, and the target cell can be the serving cell or the NES cell.

[0101] The following section provides examples illustrating how to obtain the configuration parameters for the second piece of information, using different scenarios as examples.

[0102] Scenario 1: The cell where the UE needs to reside is the serving cell.

[0103] The UE receives system information from the serving cell (such as SIB1 or dedicated RRC signaling) and obtains the WUS configuration parameters from it. For example, the serving cell explicitly defines WUS configuration parameters, such as time and frequency resources, through the `rach-ConfigGeneric` or `prach-ConfigurationIndex` fields. Upon receiving this information, the UE applies these configuration parameters to the current serving cell by default. Furthermore, the serving cell's SIB1 may include PRACH configurations (such as time and frequency resources and preamble formats), and these parameters are directly related to the serving cell's WUS triggering mechanism.

[0104] Scenario 2: The cell where the UE needs to camp is an NES cell.

[0105] The WUS configuration parameters for an NES cell may be obtained in the following ways: a) Dedicated signaling: Before the UE hands over or reselects to an NES cell, NES cell-specific WUS parameters are sent via dedicated signaling similar to RRC reconfiguration messages (such as RRCReconfiguration). b) Implicit association: The existence of WUS configuration parameters is implicitly indicated by the extended k_SSB value in the NES cell's SSB (e.g., k_SSB = 24 in FR1). The UE then needs to resolve whether the WUS configuration parameters apply to the serving cell or the NES cell according to standard predefined rules.

[0106] In some possible embodiments, the configuration parameters of the second information include at least one of the following: Physical Cell Identifier List (IE PhysCellIdList), Global Synchronization Channel Number Offset (GSCN offset), Search Space Zero (SS0) and Control Resource Set Zero (CORESET0), Total Number of RA-Preambles available for NES cells (totalNumberOfRA-Preambles) and Random Access Preamble ID (RAPID) or reserved bits used to indicate the GSCN offset.

[0107] In some possible embodiments, if the configuration parameters of the second information contain a Physical Cell Identifier List (IE PhysCellIdList), it implicitly indicates that the configuration parameter applies to NES cells in the Physical Cell Identifier List. Conversely, if the IE PhysCellIdList does not exist, it implicitly indicates that the configuration parameter applies to the serving cell.

[0108] In some possible implementations, the configuration parameters are applied to the serving cell when the absolute radio-frequency channel number (NR-ARFCN or ValueNR) and physical cell identifier (PhysCellId, PCI) in PhysCellIdList match the serving cell. This is because the WUS configuration is only guaranteed to apply to the serving cell when both the PCI and ARFCN are identical, as the cell ID of the inter-frequency NES cell may overlap with the serving cell ID. Alternatively, when the WUS configuration is applied to the serving cell, at least the PhysCellId and ARFCN / ValueNR must be configured in the WUS configuration parameters.

[0109] In some possible embodiments, the second node adds `totalNumberOfRA-Preambles` and `RAPID` to the configuration parameters of the second information. Upon receiving the second information, the NES UE can distinguish between CFRA (Configure Random Access) and CBRA (Contentment Random Access), with the corresponding MAC sub-PDU size being 7 bytes. The UE can then execute the OD-SIB1 procedure to camp on the NES cell. The NES UE can also determine which RAPID is used for the OD-SIB1 request based on `RAPreambleIndex` and the number of SSBs in the configuration parameters. Clearly, the preambles other than CFRA / CBRA and OD-SIB1 are used for OSI. Based on this method, the NES UE can easily identify the format of the received MAC sub-PDU without decoding errors.

[0110] In some possible embodiments, if the configuration parameters of the second information do not include IE PhysCellIdList and totalNumberOfRA-Preambles, the first node needs to find other cells to obtain the valid configuration of the target cell, thereby camping on the NES cell through other cells. For example, a UE accesses cell A. Cell A broadcasts the NES cell list and related parameters via SIB15 / SIB16. After parsing SIB15 / SIB16, the UE obtains the UL-WUS configuration of the NES cell, listens for Type0CSS through the OD-SIB1 procedure, parses SIB1, and determines the camping conditions. If the conditions are met, the UE camps on the NES cell and establishes an RRC connection. The broadcast information of cell A is shown in the table below:

[0111] In some possible implementations, the GSCN is a number used in 5G NR to identify the center frequency of the Synchronization Signal Block (SSB), which can directly correspond to the SSB location. The UE infers the SSB location of cell A by scanning the GSCN frequency, avoiding blind search across the entire frequency band. For example, for FR1 (<6GHz), the UE can use a range of 24≤k_SSB≤29 to search for cell A; for FR2 (millimeter wave), the UE can use a range of 12≤k_SSB≤13 to search for cell A. Optionally, the UE determines the nearest GSCN corresponding to the SSB associated with Type 0CSS based on the GSCN offset of pdcch-ConfigSIB1. In scenario one, when the SSB of the nearest GSCN is an SSB sent by cell A, and cell A is a suitable cell for the UE to camp on, the UE can receive UL WUS configuration from cell A and subsequently perform the OD-SIB1 procedure to camp on the NES cell. In scenario two, the UE can receive the UL-WUS configuration from cell A. If the WUS configuration provides a totalNumberOfRA preamble for an NES cell, it means the NES UE can clearly identify which RAPID is used for CFRA / CBRA. If the SSB sent by cell A is appropriate (i.e., the UE is campable), the UE can receive the UL-WUS configuration from cell A. From the UL-WUS configuration, the UE obtains searchSpaceZero (SS0) and controlResourceSetZero (CORESET0). The UE can then execute the OD-SIB1 procedure to camp on the NES cell. It should be understood that if totalNumberOfRA-Preambles does not include resources for the NES cell, the UE needs to continue searching for other cells until a suitable cell is found.

[0112] In some possible embodiments, when the SSB of an NES cell is on a synchronization grating, and the NES cell uses reserved subcarrier offsets (FR1: KSSB = 30 KSSB = 30; FR2: KSSB = 14 KSSB = 14), the reserved bits of PDCCH-ConfigSIB1 indicate the GSCN offset: ΔGSCN = ±(768+N), N∈[1,128]. Therefore, the UE can use this offset to infer the possible location of cell A without blindly searching for all possible SSB locations. Furthermore, the frequency assistance information PDCCH-ConfigSIB1 also carries the search space (searchSpace Zero) and control resource set (controlResourceSet Zero) of OD-SIB1, assisting the UE in quickly listening to scheduling information. By providing more accurate frequency assistance information through PDCCH-ConfigSIB1, the UE can find cell A faster, which is more energy-efficient than the traditional blind search method. As shown in Figure 7, the UE completes initial synchronization by scanning the CD-SSB of cell A and camps on cell A. Cell A sends WUS configuration to the UE via RRC signaling or system information (such as SIB), which includes parameters such as the listening time, frequency range, and beam information of the NES cell. According to the instructions of the WUS configuration, the UE activates the receiver in a specific time window and attempts to detect the CD-SSB / NCD-SSB of the NES cell. If the detection is successful, the UE synchronizes to the NES cell and obtains its system information (such as SIB1); if it fails, it remains in sleep mode to save energy.

[0113] In some possible embodiments, the SSB of the NES cell is on a asynchronous grating. In this scenario, a traditional UE will not be able to detect the NES cell and will not camp on it because the SSB is an asynchronous grating, thus prohibiting these traditional UEs from entering the NES cell. The NES UE will also not be able to detect the NES cell and will not camp on it during its initial cell search. The NES UE will not camp on the NES cell during the initial search, so the UE needs to detect cell A first. Once cell A is detected, the UE camps on cell A and receives a WUS (Warnings Required). Since the WUS indicates that an NES cell may exist, it guides the UE to attempt to search for the NES cell's SSB within a specific time and frequency range. If the UE successfully detects the NES cell, it can further acquire the NES cell's system information. In this case, the NES cell can functionally be the PCell of an R19 UE. After the NES cell becomes the PCell, the UE can establish an RRC connection and begin normal communication. Therefore, even if the NES cell SSB is not in the synchronization grating, the Rel-19 UE can still indirectly discover the NES cell through cell A and eventually camp on or access the NES cell.

[0114] For ease of understanding, the following uses uplink WUS as an example to illustrate the on-demand SIB1 transmission in conjunction with Figure 8. In Figure 8, terminal device 810 is located in cell A (Cell#A), which is served by network device 820.

[0115] As shown in Figure 8, cell A periodically sends SSBs without SIB1, meaning cell A sends SIB1 on demand. When a terminal device sends WUS or other request information, it needs to obtain time-frequency resources for sending the request information. The network device sends a WUS configuration to the terminal device. This WUS configuration includes the relevant time-frequency resources and indicates whether the configuration parameters apply to the serving cell or another cell. Subsequently, when the terminal device attempts to access cell A, which sends SIB1 on demand, based on the WUS configuration, it can send an uplink WUS or on-demand SIB1 request to cell A, thereby triggering cell A to send SIB1. When cell A detects a WUS or on-demand SIB1 request, it can send on-demand SIB1 to the terminal device 810.

[0116] The above text, with reference to Figure 8, describes the method for sending on-demand SIB1 based on request information in the cell. How to design the PDCCH scheduling mechanism for OD-SIB1 for terminal devices in idle or inactive states to ensure reliable reception under different beam conditions while reducing network power consumption is also a problem that needs to be considered.

[0117] In some embodiments, it is assumed that the PDCCH of OD-SIB1 is transmitted during at least one PDCCH monitoring time corresponding to each transmitted SSB. During the OD-SIB1 window, the gNB transmits OD-SIB1 in all SSB beams, or transmits it on a designated subset of beams. After transmitting UL-WUS, the UE can receive OD-SIB1 using the optimal beam, which may be the same as or different from the SSB beam associated with UL-WUS.

[0118] In some embodiments, if the gNB has already transmitted SIB1 in all beams, and the UE still cannot receive SIB1, it can be determined that the channel conditions of the cell are very poor and unsuitable for access. For example, if the UE fails to receive SIB1 within the maximum number of retries (e.g., 3 times), the cell is marked as "barred". Furthermore, the UE adjusts the PDCCH monitoring timing according to the SSB. In the SSB or CORESET design, certain information is encoded to indicate when the UE monitors the PDCCH to receive SIB1. For example, the SSB frequency domain position can be mapped to the PDCCH monitoring timing as SSB_index + K_offset, where K_offset is indicated by the MIB or SIB1.

[0119] In some embodiments, the UE assumes that the PDCCH of the OD-SIB1 message is sent during at least one PDCCH monitoring time corresponding to the SSB indicated in the RAR. Therefore, sending OD-SIB1 during the PDCCH monitoring time corresponding to the SSB indicated in the RAR (Random Access Response) message of the UE random access procedure can reduce the power consumption of the gNB.

[0120] In some embodiments, the UE assumes that the PDCCH of the OD-SIB1 message is sent at least once during the PDCCH monitoring time corresponding to the SSB associated with the transmitted ULWUS preamble. Therefore, OD-SIB1 is sent during the PDCCH monitoring time corresponding to the SSB associated with the ULWUS transmitted by the UE. If the UE's optimal SSB beam changes, and SIB1 is only transmitted on the ULWUS-related SSB beam, SIB1 reception may fail.

[0121] In some embodiments, the PDCCH monitoring timing for dynamic beam selection allows the gNB to dynamically select the most suitable beam based on the UE's uplink signal measurements (e.g., UL-WUS, RA preamble, SR, etc.) and transmit OD-SIB1 within the PDCCH monitoring timing of that beam. For example, after transmitting UL-WUS, the UE sends an uplink measurement report to the gNB, indicating its current optimal beam. Based on this measurement result, the gNB transmits OD-SIB1 within the PDCCH monitoring timing corresponding to the optimal SSB beam indicated by the UE. This method improves the adaptability and robustness of SSB1 transmission, especially for rapidly changing channel environments. The gNB no longer needs to blindly select the SSB beam but instead optimizes it based on the UE's measurement feedback.

[0122] In some embodiments, the PDCCH monitoring timing of multiple SSB beams is combined with the SSB beam associated with UL-WUS and the best beam measured by the UE in the past to transmit OD-SIB1 on multiple possible beams. The gNB can select N best SSB beams (e.g., N=2~3) and transmit OD-SIB1 within the PDCCH monitoring timing of these beams. This balances energy efficiency and the success rate of UE SIB1 reception. Even if the best beam changes, the UE can still receive SIB1 from one of the N candidate beams, improving robustness. Furthermore, AI and ML beam management methods can be combined. For example, the UE transmits UL-WUS, associated with SSB beam A; the network transmits OD-SIB1 in beams A and B (historically best); the UE's current best beam is B, and it successfully receives SIB1. The advantage is that it combines multiple beams to cover the UE's movement path and avoids the failure of a single beam.

[0123] In some embodiments, the gNB may no longer be limited to sending SIB1 within a fixed time window, but instead adopt a dynamic time window, dynamically scheduling the PDCCH monitoring timing for SIB1 transmission based on the UE's request, UE capability information, or service mode. The dynamic time window is configured through at least one of the following configuration information: RRC Reconfiguration, or the onDemandSIB1-MonitoringConfig information in SystemInformationBlockType1 (SIB1), or the monitoring offset information in DCI, or an extended field in Msg2 (RAR, Random Access Response) indicating whether SIB1 transmission has been scheduled and indicating the PDCCH monitoring time offset, or adding a new control element (MAC CE) at the MAC layer indicating the applicable UE group and the PDCCH monitoring offset. After the UE sends UL-WUS, the gNB selects an appropriate PDCCH monitoring timing to send SIB1 within a flexible time slot (some time slots may be delayed). This avoids the problem of the UE being unable to receive SIB1 due to mismatched PDCCH monitoring timing, thus improving the reception success rate. In addition, the gNB can flexibly allocate resources, improving the overall energy efficiency of the cell.

[0124] The following table provides a comparative analysis of the different embodiments described above, in order to summarize the advantages of each approach.

[0125] In some embodiments, the gNB dynamically schedules PDCCH monitoring based on UE requests, rather than using a fixed time window. One design approach can be implemented through RRC signaling extensions, such as when the UE first accesses the network or when the connection is restored, the gNB configures the UE's PDCCH monitoring timing policy via RRC (RadioResourceControl). In RRCReconfiguration or SystemInformationBlockType1 (SIB1), a field is added, such as: onDemandSIB1-MonitoringConfig. This field can specifically include:

[0126] It should be understood that this field allows the UE to know how many time slots SIB1 might be delayed (e.g., 1-5ms, 5-10ms), and what mechanism will be used to notify the UE to monitor the PDCCH (e.g., DCI or RACH response). This is especially important when there are multiple UEs, allowing for parallel scheduling of PDCCH monitoring.

[0127] Alternatively, another design approach could be implemented via DCI signaling, where the gNB can dynamically notify a UE to monitor the PDCCH at specific times. This involves adding a new field to the PDCCH format (such as DCIFormat1_0 or 1_1), for example: DCIFormat 1_x Extension.

[0128] For example, if this field has 3 time slots, it means that the UE needs to start monitoring the PDCCH after 3 time slots to receive SIB1.

[0129] Alternatively, this can be implemented via RAR extension, where the UE requests SIB1 through the RACH procedure (Random Access Response). An extension field, such as RAR Extension, can be added to Msg2 (RAR, Random Access Response).

[0130] If this field represents 3 time slots, it means the UE needs to start monitoring the PDCCH after 5 time slots to receive SIB1. This is especially important for UEs accessing the network for the first time, ensuring that newly joined UEs correctly receive SIB1. It does not consume additional PDCCH resources, reducing signaling overhead.

[0131] Alternatively, another design approach could be implemented using MACCE, adding a new control element (MACCE) to the MAC layer: such as a MACCE Extension, specifically...

[0132] In some embodiments, the gNB sends a MACCE, instructing a group of UEs (such as UEs within the same beam) to monitor the PDCCH after the monitoring time. The gNB needs to notify multiple UEs to monitor the PDCCH, which can improve network flexibility, especially for eMBB and mMTC scenarios.

[0133] In some embodiments, the above different signaling methods may also be combined, such as combining RRC configuration and DCI signaling, to ensure long-term configurability while supporting dynamic scheduling and improving the robustness and flexibility of SIB1 transmission.

[0134] In some embodiments, when the terminal device is a Reduced Capability (RedCap) UE, RedCap UEs can only receive random access responses (RARs) within a 20MHz bandwidth, while non-RedCap UEs can receive RARs within a bandwidth exceeding 20MHz. Therefore, the network side needs to know the UE type in advance when sending RARs to optimize resource allocation. Optionally, the network side can use any one or more of the following embodiments to determine the UE type.

[0135] In Implementation Example A, the network side configures independent WUS resources for RedCapUEs, such as setting SIB1RequestResourceRedCap. Therefore, the gNB can distinguish between RedCapUEs and non-RedCapUEs in advance before responding to UL-WUS, based on the different WUS resources corresponding to different configurations.

[0136] In Example B, the network side configures independent PRACH resources for RedCapUE. For example, during the OD-SIB1 request phase, RedCapUE can be guided to use specific PRACH resources (such as different RACH resource pools or specific PRACH preambles) for access. In this way, RedCapUE and ordinary UE use different PRACH resources, so that gNB can distinguish the UE type after the PRACH process.

[0137] In Example C, the network side indicates the UE type through the PDCCH DCI Format. Before the RAR transmission triggered by WUS, the gNB can use specific bits of DCIFormat 1_0 / 1_1 to indicate whether the UE is a RedCap or a normal UE.

[0138] In Example D, the UE type is explicitly indicated in the OD-SIB1 request. The OD-SIB1 Request message itself may contain fields indicating the UE type. For example, different resource indices or HARQ feedback bits may be used in the OD-SIB1 request for PUCCH / PUSCH resources to indicate whether the UE is RedCap. The gNB can know the UE type in advance when it receives the OD-SIB1 request and adapt it during WUSRAR or OD-SIB1 transmission.

[0139] In Example E, by using MACCE (Control Element) to carry UE type information, before uplink data transmission, the gNB can request the UE to report whether it is a RedCap UE in the initial UL transmission or RRC connection request.

[0140] In Example F, different WUS codebooks are used, defining different WUS codebooks for RedCap UEs and ordinary UEs, allowing the gNB to determine the UE type simply through WUS detection. For example, RedCap UEs and ordinary UEs use different codewords in their WUS sequence design, enabling the gNB to distinguish the UE type upon receiving a WUS request. Optionally, the WUS codebook consists of specific sequences used for signal detection when the UE listens for WUS. Therefore, by designing different WUS codebooks for RedCap UEs and ordinary UEs, the gNB can immediately determine the UE type upon receiving a WUS request and then use different scheduling strategies for resource allocation. The gNB can know the UE's type in advance without waiting for the UE to send RAR or RRC messages, improving WUSRAR scheduling efficiency.

[0141] For embodiment F, at least one of the following schemes, such as index allocation, ZC root sequence, or orthogonal code, can be used to design different WUS codebooks for RedCapUE and ordinary UE.

[0142] As shown in the table above, in the index-based WUS codebook scheme, it is assumed that the WUS codebook set consists of 16 different sequences (numbered WUS_0 to WUS_15). Different WUS codebook indices can be pre-assigned to RedCapUE and non-RedCapUE; for example, RedCapUE can use only WUS_0 to WUS_7, while non-RedCapUE can use only WUS_8 to WUS_15. When the gNB detects a WUS codebook, it can directly determine its location based on the index range.

[0143] Optionally, in the WUS codebook scheme based on the Zadoff-Chu sequence, the WUS codebook can be generated based on the Zadoff-Chu (ZC) sequence. RedCapUE uses root sequences 25, 29, 34, and 38, while non-RedCapUE uses root sequences 63, 75, 91, and 97. The ZC sequence exhibits good autocorrelation and low cross-correlation properties, and different root sequences can clearly distinguish between RedCapUE and non-RedCapUE during detection.

[0144] Alternatively, in a WUS codebook scheme based on orthogonal sequence mapping, using different Walsh-Hadamard codes or Golay codes as WUS sequences for RedCap UE and non-RedCap UE can be adapted to systems that support more flexible signal processing.

[0145] In one embodiment, a RedCap UE searches for SSBs only on specific GSCN frequencies, and the network infers the UE type based on the SSB selection. For example, a RedCap UE may only perform cell searches on certain specific SSB resources, while a non-RedCap UE may have a wider range of SSB resources. Once the gNB discovers the SSB resources selected by the UE, it can infer whether the UE is RedCap, thereby adjusting subsequent OD-SIB1 transmission and RAR scheduling strategies.

[0146] In one embodiment, the UE type is indirectly determined by the difference in CSI-RS coverage (RedCap UEs cannot detect high-frequency CSI-RS). If UE type pre-classification is performed in conjunction with L1-Signal (such as CSI-RS), the gNB can use periodic CSI-RS (Channel State Information Reference Signal) to perform preliminary UE classification before the UE performs initial RACH or WUS: due to the limited RF capabilities of RedCap UEs, they may not be visible to certain high-frequency CSI-RS resources. The gNB can infer in advance whether the UE is RedCap based on whether the UE reports CSI-RS resource information, and differentiate them during RAR or OD-SIB1 scheduling.

[0147] In one embodiment, the gNB can carry UE capability information (such as bandwidth limitations) in RRCConnectionSetupRequest / Complete. For example, a non-RedCapUE report may include complete UE capability information, such as bandwidth support greater than 20MHz. A RedCapUE report may only support bandwidths below 20MHz.

[0148] The method embodiments of this application have been described in detail above with reference to Figures 1 to 8. The apparatus embodiments of this application will be described in detail below with reference to Figures 9 to 12. It should be understood that the descriptions of the method embodiments correspond to the descriptions of the apparatus embodiments; therefore, any parts not described in detail can be referred to the preceding method embodiments.

[0149] Figure 9 illustrates a first node for wireless communication provided in an embodiment of this application. The first node can be a terminal device or a network device. As shown in Figure 9, the first node 900 includes a first transceiver module 910.

[0150] The first transceiver module 910 is used as a first transceiver module to receive first information, the first information including first parameters, second parameters, and configuration parameters of the second information;

[0151] The first transceiver module 910 is also used to send the second information, which is used to request the third information;

[0152] Wherein, the second information is the wake-up signal WUS, the third information is the on-demand SIB1 information, the first parameter is used to identify the cell type, the second parameter is used to indicate the length of the time window for reading the third information; the configuration parameters of the second information come from the target cell or the cell to which the first node first camps, the target cell is the serving cell or the network energy-saving NES cell, and the cell to which the first node first camps is a non-energy-saving cell.

[0153] As one example, the first parameter is the subcarrier offset K_SSB;

[0154] Specifically, for NES cells that support on-demand SIB1, a K_SSB greater than 23 and not equal to 30 in the first frequency band FR1 and a K_SSB greater than 11 and not equal to 14 in the second frequency band FR2 both indicate that SIB1 on the NES cell is on-demand.

[0155] As one embodiment, the configuration parameters of the second information include at least one of the following:

[0156] Physical cell identifier list (IE PhysCellIdList) information;

[0157] The absolute radio frequency channel number ValueNR and physical cell identifier PhysCellId in PhysCellIdList;

[0158] Global Synchronization Channel Number Offset (GSCN)

[0159] Search space 0 and control resource set 0;

[0160] The total number of random access preambles available for NES cells is totalNumberOfRA-Preambles, and the random access preamble identifier is RAPID.

[0161] Alternatively, reserve bits.

[0162] As one embodiment, the first information is carried in the system information or RRC of the target cell; or

[0163] The first information is carried in the system information or RRC of the cell where the first cell is camped.

[0164] As one embodiment, the triggering condition for sending the second information includes at least one of the following:

[0165] The first node is camped in the NES cell, and the result of blind detection is that SIB1 is not detected; or

[0166] The target cell supports OD-SIB1, and OD-SIB1 is not broadcast.

[0167] As an example, a target cell supporting OD-SIB1 includes at least one of the following SIB1 transmission states:

[0168] A first transmission state, which indicates normal broadcast SIB1;

[0169] The second transmission state is used to indicate temporary broadcast SIB1;

[0170] The third transmission state is used to indicate that SIB1 is not broadcast.

[0171] As an example, the second information configuration parameters also include time-frequency resources and preamble information, wherein the preamble information corresponds to the format of the MAC sub-PDU.

[0172] As one embodiment, the first transceiver module 910 is further configured to:

[0173] Receive OD-SIB1 during one or more candidate SIB1 transmission opportunities;

[0174] Among them, one or more candidate SIB1 transmission opportunities include the first candidate SIB1 transmission opportunity;

[0175] The multiple candidate SIB1 transmission timings are PDCCH monitoring timings corresponding to all SSB beams; or...

[0176] The first candidate SIB1 transmission timing is the PDCCH monitoring timing corresponding to the SSB beam associated with the wake-up signal; or,

[0177] The first candidate SIB1 transmission timing is the PDCCH monitoring timing corresponding to the best SSB beam currently measured by the first node, or...

[0178] The first candidate SIB1 transmission timing is the PDCCH monitoring timing corresponding to the historical best SSB beam of the first node; or,

[0179] The first candidate SIB1 transmission timing is the PDCCH monitoring timing specified by the second node.

[0180] As one embodiment, the first transceiver module 910 is further configured to:

[0181] Send an uplink measurement report, which indicates the current optimal beam of the first node. The current optimal beam is used by the second node to send OD-SIB1 within the PDCCH monitoring time corresponding to the current optimal beam.

[0182] As one example, the time window for the third information is either a fixed time window or a dynamic time window.

[0183] As an example, the dynamic time window of the third information is determined based on the UE's capability information or service mode.

[0184] As an example, the dynamic time window of the third information is indicated by any one of RRC, DCI, SIB, or MAC CE.

[0185] As an example, the dynamic time window of the third information is configured through at least one of the following configuration information:

[0186] RRC reconfiguration information;

[0187] On-demand listening configuration information in SIB1;

[0188] Listening offset information in DCI;

[0189] The extended field in Msg2 indicates whether the SIB1 transmission has been scheduled and indicates the PDCCH monitoring time offset;

[0190] Alternatively, a control element in the MAC layer, which indicates the applicable UE group and the offset monitored by the PDCCH.

[0191] As one embodiment, the first transceiver module 910 is further configured to:

[0192] Receive configuration information, which indicates independent WUS resources or physical random access channel (PRACH) resources for lightweight RedCapUE configuration.

[0193] As one embodiment, the second information includes the type information of the first node.

[0194] As one embodiment, the first transceiver module 910 is further configured to:

[0195] Send a report message, which indicates whether the first node is a RedCapUE.

[0196] As an example, the codebook used by the wake-up signal is determined by whether the type of the first node is RedCapUE or not RedCapUE.

[0197] As one embodiment, the first transceiver module 910 can be a transceiver 1130. The first node 900 may also include a memory 1120 and a processor 1110, as shown in FIG11.

[0198] Figure 10 illustrates a second node for wireless communication according to an embodiment of this application. The second node can be a network-side device or entity used for positioning, such as a gNB. As shown in Figure 10, the second node 1000 includes a second transceiver module 1010.

[0199] The second transceiver module 1010 is used to send first information, the first information including first parameters, second parameters, and configuration parameters of the second information;

[0200] The second transceiver module is also used to receive the second information, which is used to request the third information;

[0201] Wherein, the second information is the wake-up signal WUS, the third information is the on-demand SIB1 information, the first parameter is used to identify the cell type, the second parameter is used to indicate the length of the time window for reading the third information; the configuration parameters of the second information come from the target cell or the cell to which the first node first camps, the target cell is the serving cell or the network energy-saving NES cell, and the cell to which the first node first camps is a non-energy-saving cell.

[0202] As one example, the first parameter is the subcarrier offset K_SSB;

[0203] Specifically, for NES cells that support on-demand SIB1, a K_SSB greater than 23 and not equal to 30 in the first frequency band FR1 and a K_SSB greater than 11 and not equal to 14 in the second frequency band FR2 both indicate that SIB1 on the NES cell is on-demand.

[0204] As one embodiment, the configuration parameters of the second information include at least one of the following:

[0205] Physical cell identifier list (IE PhysCellIdList) information;

[0206] The absolute radio frequency channel number ValueNR and physical cell identifier PhysCellId in PhysCellIdList;

[0207] Global Synchronization Channel Number Offset (GSCN)

[0208] Search space 0 and control resource set 0;

[0209] The total number of random access preambles available for NES cells is totalNumberOfRA-Preambles, and the random access preamble identifier is RAPID.

[0210] Alternatively, reserve bits.

[0211] As one embodiment, the first information is carried in the system information or RRC of the target cell; or

[0212] The first information is carried in the system information or RRC of the cell where the first cell is camped.

[0213] As one embodiment, the triggering condition for sending the second information includes at least one of the following:

[0214] The first node is camped in the NES cell, and the result of blind detection is that SIB1 is not detected; or

[0215] The target cell supports OD-SIB1, and OD-SIB1 is not broadcast.

[0216] As an example, a target cell supporting OD-SIB1 includes at least one of the following SIB1 transmission states:

[0217] A first transmission state, which indicates normal broadcast SIB1;

[0218] The second transmission state is used to indicate temporary broadcast SIB1;

[0219] The third transmission state is used to indicate that SIB1 is not broadcast.

[0220] As an example, the second information configuration parameters also include time-frequency resources and preamble information, wherein the preamble information corresponds to the format of the MAC sub-PDU.

[0221] As one embodiment, the second transceiver module 1010 is further configured to:

[0222] Send OD-SIB1 during one or more candidate SIB1 transmission opportunities;

[0223] Among them, one or more candidate SIB1 transmission opportunities include the first candidate SIB1 transmission opportunity;

[0224] The multiple candidate SIB1 transmission timings are PDCCH monitoring timings corresponding to all SSB beams; or...

[0225] The first candidate SIB1 transmission timing is the PDCCH monitoring timing corresponding to the SSB beam associated with the wake-up signal; or,

[0226] The first candidate SIB1 transmission timing is the PDCCH monitoring timing corresponding to the best SSB beam currently measured by the first node, or...

[0227] The first candidate SIB1 transmission timing is the PDCCH monitoring timing corresponding to the historical best SSB beam of the first node; or,

[0228] The first candidate SIB1 transmission timing is the PDCCH monitoring timing specified by the second node.

[0229] As one example, the time window for the third information is either a fixed time window or a dynamic time window.

[0230] As an example, the dynamic time window of the third information is determined based on the UE's capability information or service mode.

[0231] As an example, the dynamic time window of the third information is indicated by any one of RRC, DCI, SIB, or MAC CE.

[0232] As an example, the dynamic time window of the third information is configured through at least one of the following configuration information:

[0233] RRC reconfiguration information;

[0234] On-demand listening configuration information in SIB1;

[0235] Listening offset information in DCI;

[0236] The extended field in Msg2 indicates whether the SIB1 transmission has been scheduled and indicates the PDCCH monitoring time offset;

[0237] Alternatively, a control element in the MAC layer, which indicates the applicable UE group and the offset monitored by the PDCCH.

[0238] As one embodiment, the second transceiver module 1010 is further configured to:

[0239] Send configuration information, which indicates the independent WUS resource or physical random access channel (PRACH) resource for lightweight RedCapUE configuration.

[0240] As one embodiment, the second information includes the type information of the first node.

[0241] As one embodiment, the second transceiver module 1010 is further configured to:

[0242] Receive report information, which is used to indicate whether the first node is RedCapUE.

[0243] As an example, the codebook used by the wake-up signal is determined by whether the type of the first node is RedCapUE or not RedCapUE.

[0244] As one embodiment, the second transceiver module 1010 can be a transceiver 1030. The second node 1000 may also include a memory 1120 and a processor 1110, as shown in Figure 11.

[0245] Figure 11 is a schematic structural diagram of a communication device according to an embodiment of this application. The dashed lines in Figure 11 indicate that the unit or module is optional. This device 1100 can be used to implement the methods described in the above method embodiments. Device 1100 can be a chip, user equipment, or network device.

[0246] Apparatus 1100 may include one or more processors 1110. The processor 1110 may support apparatus 1100 in implementing the methods described in the preceding method embodiments. The processor 1110 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor may be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor.

[0247] The apparatus 1100 may further include one or more memories 1120. The memories 1120 store a program that can be executed by the processor 1110, causing the processor 1110 to perform the methods described in the preceding method embodiments. The memories 1120 may be independent of the processor 1110 or integrated within the processor 1110.

[0248] The device 1100 may also include a transceiver 1130. The processor 1110 can communicate with other devices or chips via the transceiver 1130. For example, the processor 1110 can send and receive data with other devices or chips via the transceiver 1130.

[0249] Figure 12 is a schematic diagram of the hardware modules of the communication device provided in this application embodiment. Specifically, Figure 12 shows a block diagram of a first communication device 1250 and a second communication device 1210 communicating with each other in the access network.

[0250] The first communication device 1250 includes a controller / processor 1259, a memory 1260, a data source 1267, a transmitter processor 1268, a receiver processor 1256, a multi-antenna transmitter processor 1257, a multi-antenna receiver processor 1258, a transmitter / receiver 1254, and an antenna 1452.

[0251] The second communication device 1410 includes a controller / processor 1475, a memory 1476, a data source 1477, a receiver processor 1470, a transmitter processor 1416, a multi-antenna receiver processor 1472, a multi-antenna transmitter processor 1471, a transmitter / receiver 1418, and an antenna 1420.

[0252] In the transmission from the second communication device 1410 to the first communication device 1450, at the second communication device 1410, upper-layer data packets from the core network or from the data source 1477 are provided to the controller / processor 1475. The core network and data source 1477 represent all protocol layers above the L2 layer. The controller / processor 1475 implements the functionality of the L2 layer. In the transmission from the second communication device 1410 to the first communication device 1450, the controller / processor 1475 provides header compression, encryption, packet segmentation and reordering, multiplexing between logical and transport channels, and radio resource allocation for the first communication device 1450 based on various priority metrics. The controller / processor 1475 is also responsible for retransmitting lost packets and signaling to the first communication device 1450. The transmit processor 1216 and the multi-antenna transmit processor 1271 implement various signal processing functions for the L1 layer (i.e., the physical layer). Transmit processor 1216 performs encoding and interleaving to facilitate forward error correction at the second communication device 1210, and mapping of signal clusters based on various modulation schemes (e.g., binary phase shift keying, quadrature phase shift keying, M-phase shift keying, M-quadrature amplitude modulation). Multi-antenna transmit processor 1271 performs digital spatial precoding on the encoded and modulated symbols, including codebook-based precoding and non-codebook-based precoding, and beamforming processing, generating one or more spatial streams. Transmit processor 1216 then maps each spatial stream to subcarriers, multiplexes it with a reference signal (e.g., a pilot) in the time and / or frequency domains, and subsequently uses inverse fast Fourier transform to generate a physical channel carrying the time-domain multicarrier symbol stream. Multi-antenna transmit processor 1271 then performs transmit analog precoding / beamforming operations on the time-domain multicarrier symbol stream. Each transmitter 1218 converts the baseband multicarrier symbol stream provided by the multi-antenna transmitter processor 1271 into an radio frequency stream, which is then provided to different antennas 1220.

[0253] In the transmission from the second communication device 1210 to the first communication device 1250, at the first communication device 1250, each receiver 1254 receives a signal through its corresponding antenna 1252. Each receiver 1254 recovers the information modulated onto the radio frequency carrier and converts the radio frequency stream into a baseband multicarrier symbol stream, which is then provided to the receiver processor 1256. The receiver processor 1256 and the multi-antenna receiver processor 1258 implement various signal processing functions of Layer 1. The multi-antenna receiver processor 1258 performs receive analog precoding / beamforming operations on the baseband multicarrier symbol stream from the receiver 1254. The receiver processor 1256 uses a fast Fourier transform to convert the baseband multicarrier symbol stream after the receive analog precoding / beamforming operations from the time domain to the frequency domain. In the frequency domain, the physical layer data signal and the reference signal are demultiplexed by the receiver processor 1256, where the reference signal is used for channel estimation, and the data signal is recovered in the multi-antenna receiver processor 1258 after multi-antenna detection to recover any spatial stream destined for the first communication device 1250. Symbols on each spatial stream are demodulated and recovered in the receive processor 1256, generating soft decisions. The receive processor 1256 then decodes and deinterleaves the soft decisions to recover the upper-layer data and control signals transmitted by the second communication device 1210 over the physical channel. The upper-layer data and control signals are then provided to the controller / processor 1259. The controller / processor 1259 implements the functions of Layer 2. The controller / processor 1259 may be associated with a memory 1260 storing program code and data. The memory 1260 may be referred to as computer-readable media. In the transmission from the second communication device 1210 to the first communication device 1250, the controller / processor 1259 provides multiplexing, packet reassembly, decryption, header decompression, and control signal processing between the transmission and logical channels to recover the upper-layer data packets from the second communication device 1210. The upper-layer data packets are then provided to all protocol layers above Layer 2. Various control signals may also be provided to Layer 3 for Layer 3 processing.

[0254] In the transmission from the first communication device 1250 to the second communication device 1210, at the first communication device 1250, upper-layer data packets are provided to the controller / processor 1259 using a data source 1267. The data source 1267 represents all protocol layers above the L2 layer. Similar to the transmission functions at the second communication device 1210 described in the transmission from the second communication device 1210 to the first communication device 1250, the controller / processor 1259 implements header compression, encryption, packet segmentation and reordering, and multiplexing between logic and transport channels, implementing L2 layer functions for the user plane and control plane. The controller / processor 1259 is also responsible for retransmitting lost packets and signaling to the second communication device 1210. Transmit processor 1268 performs modulation mapping and channel coding processing, while multi-antenna transmit processor 1257 performs digital multi-antenna spatial precoding, including codebook-based and non-codebook-based precoding, and beamforming processing. Subsequently, transmit processor 1268 modulates the generated spatial stream into a multi-carrier / single-carrier symbol stream. After analog precoding / beamforming operations in multi-antenna transmit processor 1257, the stream is provided to different antennas 1252 via transmitter 1254. Each transmitter 1454 first converts the baseband symbol stream provided by multi-antenna transmit processor 1457 into a radio frequency symbol stream before providing it to antenna 1452.

[0255] In the transmission from the first communication device 1450 to the second communication device 1410, the function at the second communication device 1410 is similar to the receiving function at the first communication device 1450 described in the transmission from the second communication device 1410 to the first communication device 1450. Each receiver 1418 receives radio frequency signals through its corresponding antenna 1420, converts the received radio frequency signals into baseband signals, and provides the baseband signals to the multi-antenna receiving processor 1472 and the receiving processor 1470. The receiving processor 1470 and the multi-antenna receiving processor 1472 jointly implement the L1 layer function. The controller / processor 1475 implements the L2 layer function. The controller / processor 1475 may be associated with a memory 1476 that stores program code and data. The memory 1476 may be referred to as computer-readable media. In the transmission from the first communication device 1450 to the second communication device 1410, the controller / processor 1475 provides multiplexing, packet reassembly, decryption, header decompression, and control signal processing between the transmission and logical channels to recover the upper-layer data packets from the first communication device 1250. The upper-layer data packets from the controller / processor 1275 can be provided to the core network or all protocol layers above Layer 2, and various control signals can also be provided to the core network or Layer 3 for Layer 3 processing.

[0256] As one embodiment, the first communication device 1250 includes: at least one processor and at least one memory, the at least one memory including computer program code; the at least one memory and the computer program code are configured to be used with the at least one processor.

[0257] As one embodiment, the first communication device 1250 includes: a memory storing a computer-readable instruction program that produces action when executed by at least one processor.

[0258] As an example, the first communication device 1250 corresponds to the first node in this application.

[0259] As one embodiment, the second communication device 1210 corresponds to the second node in this application.

[0260] As an example, the first communication device 1250 is a user equipment that can act as a relay node.

[0261] As an example, the first communication device 1250 is a network control relay (NCR).

[0262] As an example, the first communication device 1250 is a relay wireless repeater.

[0263] As an example, the first communication device 1250 is a relay.

[0264] As one embodiment, the second communication device 1210 is a Location Management Function (LMF).

[0265] As an example, the first communication device 1250 corresponds to the first node in this application, and the controller / processor 1159 is used to execute the above method.

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

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

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

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

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

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

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

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

[0274] In this application embodiment, the "protocol" may refer to a standard protocol in the field of communication, such as the LTE protocol, the NR protocol, and related protocols applied to future communication systems. This application does not limit this.

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

[0276] In the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

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

[0278] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0279] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

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

[0281] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for wireless communication of a first node, comprising: include: Receive first information, the first information including first parameter, second parameter, and configuration parameters of the second information; Send the second information, which is used to request the third information; Wherein, the second information is the wake-up signal WUS, the third information is the on-demand SIB1 information, the first parameter is used to identify the cell type, the second parameter is used to indicate the length of the time window for reading the third information; the configuration parameters of the second information come from the target cell or the cell to which the first node first camps, the target cell is the serving cell or the network energy-saving NES cell, and the cell to which the first node first camps is a non-energy-saving cell.

2. The method of claim 1, wherein, The first parameter is the subcarrier offset K_SSB; Specifically, for NES cells that support on-demand SIB1, a K_SSB greater than 23 and not equal to 30 in the first frequency band FR1 and a K_SSB greater than 11 and not equal to 14 in the second frequency band FR2 both indicate that SIB1 on the NES cell is on-demand.

3. The method according to claim 1 or 2, characterized in that, The configuration parameters for the second information include at least one of the following: Physical cell identifier list (IE PhysCellIdList) information; The absolute radio frequency channel number ValueNR and physical cell identifier PhysCellId in PhysCellIdList; Global Synchronization Channel Number Offset (GSCN) Search space 0 and control resource set 0; The total number of random access preambles available for NES cells is totalNumberOfRA-Preambles, and the random access preamble identifier is RAPID. Alternatively, reserve bits.

4. The method according to claim 1 or 2, characterized in that, The first information is carried in the system information or RRC of the target cell; or The first information is carried in the system information or RRC of the cell where the first cell is camped.

5. The method according to any one of claims 1 to 4, characterized in that, The triggering conditions for sending the second information include at least one of the following: The first node is camped in the NES cell, and the result of blind detection is that SIB1 is not detected; or The target cell supports OD-SIB1, and OD-SIB1 is not broadcast.

6. The method of claim 4, wherein, Target cells supporting OD-SIB1 include at least one of the following SIB1 transmission states: A first transmission state, which indicates normal broadcast SIB1; The second transmission state is used to indicate temporary broadcast SIB1; The third transmission state is used to indicate that SIB1 is not broadcast.

7. The method according to any one of claims 1 to 4, characterized in that, The second information configuration parameters also include time and frequency resources and preamble information, wherein the preamble information corresponds to the format of the MAC sub-PDU.

8. The method according to any one of claims 1 to 7, characterized in that, Also includes: Receive OD-SIB1 during one or more candidate SIB1 transmission opportunities; Among them, one or more candidate SIB1 transmission opportunities include the first candidate SIB1 transmission opportunity; The multiple candidate SIB1 transmission timings are PDCCH monitoring timings corresponding to all SSB beams; or... The first candidate SIB1 transmission timing is the PDCCH monitoring timing corresponding to the SSB beam associated with the wake-up signal; or, The first candidate SIB1 transmission timing is the PDCCH monitoring timing corresponding to the best SSB beam currently measured by the first node, or... The first candidate SIB1 transmission timing is the PDCCH monitoring timing corresponding to the historical best SSB beam of the first node; or, The first candidate SIB1 transmission timing is the PDCCH monitoring timing specified by the second node.

9. The method according to any one of claims 1 to 7, characterized in that, Also includes: Send an uplink measurement report, which indicates the current optimal beam of the first node. The current optimal beam is used by the second node to send OD-SIB1 within the PDCCH monitoring time corresponding to the current optimal beam.

10. The method according to any one of claims 1 to 7, characterized in that, The time window for the third information can be a fixed time window or a dynamic time window.

11. The method according to claim 10, characterized in that, The dynamic time window of the third information is determined based on the UE's capability information or service mode.

12. The method according to claim 10, characterized in that, The dynamic time window of the third information is indicated by any one of RRC, DCI, SIB, or MAC CE.

13. The method according to any one of claims 1 to 12, wherein the dynamic time window of the third information is configured through at least one of the following configuration information: RRC reconfiguration information; On-demand listening configuration information in SIB1; Listening offset information in DCI; The extended field in Msg2 indicates whether the SIB1 transmission has been scheduled and indicates the PDCCH monitoring time offset; Alternatively, a control element in the MAC layer, which indicates the applicable UE group and the offset monitored by the PDCCH.

14. The method according to any one of claims 1 to 13, characterized in that, Also includes: Receive configuration information, which indicates independent WUS resources or physical random access channel (PRACH) resources for lightweight RedCapUE configuration.

15. The method according to any one of claims 1 to 13, characterized in that, The second information includes the type information of the first node.

16. The method according to any one of claims 1 to 13, characterized in that, Also includes: Send a report message, which indicates whether the first node is a RedCapUE.

17. The method according to any one of claims 1 to 13, characterized in that, The codebook used for the wake-up signal is determined by whether the first node is of type RedCapUE or not RedCapUE.

18. A method for wireless communication for a second node, characterized in that, include: Send first information, which includes first parameters, second parameters, and configuration parameters of the second information; Receive the second information, which is used to request the third information; Wherein, the second information is the wake-up signal WUS, the third information is the on-demand SIB1 information, the first parameter is used to identify the cell type, the second parameter is used to indicate the length of the time window for reading the third information; the configuration parameters of the second information come from the target cell or the cell to which the first node first camps, the target cell is the serving cell or the network energy-saving NES cell, and the cell to which the first node first camps is a non-energy-saving cell.

19. The method according to claim 18, characterized in that, The first parameter is the subcarrier offset K_SSB; Specifically, for NES cells that support on-demand SIB1, a K_SSB greater than 23 and not equal to 30 in the first frequency band FR1 and a K_SSB greater than 11 and not equal to 14 in the second frequency band FR2 both indicate that SIB1 on the NES cell is on-demand.

20. The method according to claim 18 or 19, characterized in that, The configuration parameters for the second information include at least one of the following: Physical cell identifier list (IE PhysCellIdList) information; The absolute radio frequency channel number ValueNR and physical cell identifier PhysCellId in PhysCellIdList; Global Synchronization Channel Number Offset (GSCN) Search space 0 and control resource set 0; The total number of random access preambles available for NES cells is totalNumberOfRA-Preambles, and the random access preamble identifier is RAPID. Alternatively, reserve bits.

21. The method according to claim 18 or 19, characterized in that, The first information is carried in the system information or RRC of the target cell; or The first information is carried in the system information or RRC of the cell where the first cell is camped.

22. The method according to any one of claims 18 to 21, characterized in that, The triggering conditions for sending the second information include at least one of the following: The first node is camped in the NES cell, and the result of blind detection is that SIB1 is not detected; or The target cell supports OD-SIB1, and OD-SIB1 is not broadcast.

23. The method according to claim 22, characterized in that, Target cells supporting OD-SIB1 include at least one of the following SIB1 transmission states: A first transmission state, which indicates normal broadcast SIB1; The second transmission state is used to indicate temporary broadcast SIB1; The third transmission state is used to indicate that SIB1 is not broadcast.

24. The method according to any one of claims 18 to 21, characterized in that, The second information configuration parameters also include time and frequency resources and preamble information, wherein the preamble information corresponds to the format of the MAC sub-PDU.

25. The method according to any one of claims 18 to 24, characterized in that, Also includes: Send OD-SIB1 during one or more candidate SIB1 transmission opportunities; Among them, one or more candidate SIB1 transmission opportunities include the first candidate SIB1 transmission opportunity; The multiple candidate SIB1 transmission timings are PDCCH monitoring timings corresponding to all SSB beams; or... The first candidate SIB1 transmission timing is the PDCCH monitoring timing corresponding to the SSB beam associated with the wake-up signal; or, The first candidate SIB1 transmission timing is the PDCCH monitoring timing corresponding to the best SSB beam currently measured by the first node, or... The first candidate SIB1 transmission timing is the PDCCH monitoring timing corresponding to the historical best SSB beam of the first node; or, The first candidate SIB1 transmission timing is the PDCCH monitoring timing specified by the second node.

26. The method according to any one of claims 18 to 25, characterized in that, The time window for the third information can be a fixed time window or a dynamic time window.

27. The method according to claim 26, characterized in that, The dynamic time window of the third information is determined based on the UE's capability information or service mode.

28. The method according to claim 26, characterized in that, The dynamic time window of the third information is indicated by any one of RRC, DCI, SIB, or MAC CE.

29. The method according to any one of claims 18 to 28, wherein the dynamic time window of the third information is configured through at least one of the following configuration information: RRC reconfiguration information; On-demand listening configuration information in SIB1; Listening offset information in DCI; The extended field in Msg2 indicates whether the SIB1 transmission has been scheduled and indicates the PDCCH monitoring time offset; Alternatively, a control element in the MAC layer, which indicates the applicable UE group and the offset monitored by the PDCCH.

30. The method according to any one of claims 18 to 29, characterized in that, Also includes: Send configuration information, which indicates the independent WUS resource or physical random access channel (PRACH) resource for lightweight RedCapUE configuration.

31. The method according to any one of claims 18 to 30, characterized in that, The second information includes the type information of the first node.

32. The method according to any one of claims 18 to 30, characterized in that, Also includes: Receive report information, which is used to indicate whether the first node is RedCapUE.

33. The method according to any one of claims 18 to 30, characterized in that, The codebook used for the wake-up signal is determined by whether the first node is of type RedCapUE or not RedCapUE.

34. A first node for wireless communication, characterized in that, include: The first transceiver module is used to receive first information, the first information including first parameters, second parameters, and configuration parameters of the second information; The first transceiver module is also used to send the second information, which is used to request the third information; Wherein, the second information is the wake-up signal WUS, the third information is the on-demand SIB1 information, the first parameter is used to identify the cell type, the second parameter is used to indicate the length of the time window for reading the third information; the configuration parameters of the second information come from the target cell or the cell to which the first node first camps, the target cell is the serving cell or the network energy-saving NES cell, and the cell to which the first node first camps is a non-energy-saving cell.

35. The first node according to claim 34, characterized in that, The first parameter is the subcarrier offset K_SSB; Specifically, for NES cells that support on-demand SIB1, a K_SSB greater than 23 and not equal to 30 in the first frequency band FR1 and a K_SSB greater than 11 and not equal to 14 in the second frequency band FR2 both indicate that SIB1 on the NES cell is on-demand.

36. The first node according to claim 34 or 35, characterized in that, The configuration parameters for the second information include at least one of the following: Physical cell identifier list (IE PhysCellIdList) information; The absolute radio frequency channel number ValueNR and physical cell identifier PhysCellId in PhysCellIdList; Global Synchronization Channel Number Offset (GSCN) Search space 0 and control resource set 0; The total number of random access preambles available for NES cells is totalNumberOfRA-Preambles, and the random access preamble identifier is RAPID. Alternatively, reserve bits.

37. The first node according to claim 34 or 35, characterized in that, The first information is carried in the system information or RRC of the target cell; or The first information is carried in the system information or RRC of the cell where the first cell is camped.

38. The first node according to any one of claims 34 to 37, characterized in that, The triggering conditions for sending the second information include at least one of the following: The first node is camped in the NES cell, and the result of blind detection is that SIB1 is not detected; or The target cell supports OD-SIB1, and OD-SIB1 is not broadcast.

39. The first node according to claim 37, characterized in that, Target cells supporting OD-SIB1 include at least one of the following SIB1 transmission states: A first transmission state, which indicates normal broadcast SIB1; The second transmission state is used to indicate temporary broadcast SIB1; The third transmission state is used to indicate that SIB1 is not broadcast.

40. The first node according to any one of claims 34 to 37, characterized in that, The second information configuration parameters also include time and frequency resources and preamble information, wherein the preamble information corresponds to the format of the MAC sub-PDU.

41. The first node according to any one of claims 34 to 40, characterized in that, The first transceiver module is further configured to: Receive OD-SIB1 during one or more candidate SIB1 transmission opportunities; Among them, one or more candidate SIB1 transmission opportunities include the first candidate SIB1 transmission opportunity; The multiple candidate SIB1 transmission timings are PDCCH monitoring timings corresponding to all SSB beams; or... The first candidate SIB1 transmission timing is the PDCCH monitoring timing corresponding to the SSB beam associated with the wake-up signal; or, The first candidate SIB1 transmission timing is the PDCCH monitoring timing corresponding to the best SSB beam currently measured by the first node, or... The first candidate SIB1 transmission timing is the PDCCH monitoring timing corresponding to the historical best SSB beam of the first node; or, The first candidate SIB1 transmission timing is the PDCCH monitoring timing specified by the second node.

42. The first node according to any one of claims 34 to 40, characterized in that, The first transceiver module is further configured to: Send an uplink measurement report, which indicates the current optimal beam of the first node. The current optimal beam is used by the second node to send OD-SIB1 within the PDCCH monitoring time corresponding to the current optimal beam.

43. The first node according to any one of claims 34 to 40, characterized in that, The time window for the third information can be a fixed time window or a dynamic time window.

44. The first node according to claim 43, characterized in that, The dynamic time window of the third information is determined based on the UE's capability information or service mode.

45. The first node according to claim 43, characterized in that, The dynamic time window of the third information is indicated by any one of RRC, DCI, SIB, or MAC CE.

46. ​​The first node according to any one of claims 34 to 45, wherein the dynamic time window of the third information is configured through at least one of the following configuration information: RRC reconfiguration information; On-demand listening configuration information in SIB1; Listening offset information in DCI; The extended field in Msg2 indicates whether the SIB1 transmission has been scheduled and indicates the PDCCH monitoring time offset; Alternatively, a control element in the MAC layer, which indicates the applicable UE group and the offset monitored by the PDCCH.

47. The first node according to any one of claims 34 to 46, characterized in that, The first transceiver module is further configured to: Receive configuration information, which indicates independent WUS resources or physical random access channel (PRACH) resources for lightweight RedCapUE configuration.

48. The first node according to any one of claims 34 to 46, characterized in that, The second information includes the type information of the first node.

49. The first node according to any one of claims 34 to 46, characterized in that, The first transceiver module is further configured to: Send a report message, which indicates whether the first node is a RedCapUE.

50. The first node according to any one of claims 34 to 46, characterized in that, The codebook used for the wake-up signal is determined by whether the first node is of type RedCapUE or not RedCapUE.

51. A second node for wireless communication, characterized in that, include: The second transceiver module is used to send first information, the first information including first parameters, second parameters, and configuration parameters of the second information; The second transceiver module is also used to receive the second information, which is used to request the third information; Wherein, the second information is the wake-up signal WUS, the third information is the on-demand SIB1 information, the first parameter is used to identify the cell type, the second parameter is used to indicate the length of the time window for reading the third information; the configuration parameters of the second information come from the target cell or the cell to which the first node first camps, the target cell is the serving cell or the network energy-saving NES cell, and the cell to which the first node first camps is a non-energy-saving cell.

52. The second node according to claim 51, characterized in that, The first parameter is the subcarrier offset K_SSB; Specifically, for NES cells that support on-demand SIB1, a K_SSB greater than 23 and not equal to 30 in the first frequency band FR1 and a K_SSB greater than 11 and not equal to 14 in the second frequency band FR2 both indicate that SIB1 on the NES cell is on-demand.

53. The second node according to claim 51 or 52, characterized in that, The configuration parameters for the second information include at least one of the following: Physical cell identifier list (IE PhysCellIdList) information; The absolute radio frequency channel number ValueNR and physical cell identifier PhysCellId in PhysCellIdList; Global Synchronization Channel Number Offset (GSCN) Search space 0 and control resource set 0; The total number of random access preambles available for NES cells is totalNumberOfRA-Preambles, and the random access preamble identifier is RAPID. Alternatively, reserve bits.

54. The second node according to claim 51 or 52, characterized in that, The first information is carried in the system information or RRC of the target cell; or The first information is carried in the system information or RRC of the cell where the first cell is camped.

55. The second node according to any one of claims 51 to 54, characterized in that, The triggering conditions for sending the second information include at least one of the following: The first node is camped in the NES cell, and the result of blind detection is that SIB1 is not detected; or The target cell supports OD-SIB1, and OD-SIB1 is not broadcast.

56. The second node according to claim 55, characterized in that, Target cells supporting OD-SIB1 include at least one of the following SIB1 transmission states: A first transmission state, which indicates normal broadcast SIB1; The second transmission state is used to indicate temporary broadcast SIB1; The third transmission state is used to indicate that SIB1 is not broadcast.

57. The second node according to any one of claims 51 to 54, characterized in that, The second information configuration parameters also include time and frequency resources and preamble information, wherein the preamble information corresponds to the format of the MAC sub-PDU.

58. The second node according to any one of claims 51 to 57, characterized in that, The second transceiver module is also used for: Send OD-SIB1 during one or more candidate SIB1 transmission opportunities; Among them, one or more candidate SIB1 transmission opportunities include the first candidate SIB1 transmission opportunity; The multiple candidate SIB1 transmission timings are PDCCH monitoring timings corresponding to all SSB beams; or... The first candidate SIB1 transmission timing is the PDCCH monitoring timing corresponding to the SSB beam associated with the wake-up signal; or, The first candidate SIB1 transmission timing is the PDCCH monitoring timing corresponding to the best SSB beam currently measured by the first node, or... The first candidate SIB1 transmission timing is the PDCCH monitoring timing corresponding to the historical best SSB beam of the first node; or, The first candidate SIB1 transmission timing is the PDCCH monitoring timing specified by the second node.

59. The second node according to any one of claims 51 to 58, characterized in that, The time window for the third information can be a fixed time window or a dynamic time window.

60. The second node according to claim 59, characterized in that, The dynamic time window of the third information is determined based on the UE's capability information or service mode.

61. The second node according to claim 59, characterized in that, The dynamic time window of the third information is indicated by any one of RRC, DCI, SIB, or MAC CE.

62. The second node according to any one of claims 51 to 61, wherein the dynamic time window of the third information is configured through at least one of the following configuration information: RRC reconfiguration information; On-demand listening configuration information in SIB1; Listening offset information in DCI; The extended field in Msg2 indicates whether the SIB1 transmission has been scheduled and indicates the PDCCH monitoring time offset; Alternatively, a control element in the MAC layer, which indicates the applicable UE group and the offset monitored by the PDCCH.

63. The second node according to any one of claims 51 to 62, characterized in that, The second transceiver module is also used for: Send configuration information, which indicates the independent WUS resource or physical random access channel (PRACH) resource for lightweight RedCapUE configuration.

64. The second node according to any one of claims 51 to 63, characterized in that, The second information includes the type information of the first node.

65. The second node according to any one of claims 51 to 63, characterized in that, The second transceiver module is also used for: Receive report information, which is used to indicate whether the first node is RedCapUE.

66. The second node according to any one of claims 51 to 63, characterized in that, The codebook used for the wake-up signal is determined by whether the first node is of type RedCapUE or not RedCapUE.

67. A communication device, characterized in that, It includes a memory and a processor, the memory being used to store a program, and the processor being used to invoke the program in the memory to perform the method as described in any one of claims 1-33.

68. A communication device, characterized in that, Includes a processor for calling a program from memory to perform the method as described in any one of claims 1-33.

69. A chip, characterized in that, Includes a processor for calling a program from memory, causing a device on which the chip is mounted to perform the method as described in any one of claims 1-33.

70. A computer-readable storage medium, characterized in that, It contains a program that causes a computer to perform the method as described in any one of claims 1-33.

71. A computer program product, characterized in that, Includes a program that causes a computer to perform the method as described in any one of claims 1-33.

72. A computer program, characterized in that, The computer program causes the computer to perform the method as described in any one of claims 1-33.

Images