Method and apparatus for wireless communication

Abstract

Provided are a method and device for wireless communication. The method comprises: a first terminal device sending a first request, the first request being used to request a first SIB of a first cell; and the first terminal device receiving the first SIB and / or configuration information of the first SIB; wherein the first cell is a serving cell corresponding to the first terminal device, and the first SIB comprises a SIB1 of the first cell.

Description

Technical Field

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

[0002] To serve terminal devices, network devices typically send system information blocks (SIBs) periodically. However, in scenarios where terminal devices have no demand or no terminal devices are present in the cell, the periodic sending of SIBs by network devices results in significant energy waste. Therefore, how to implement on-demand sending of SIBs to achieve network energy saving has become an urgent technical problem to be solved. Summary of the Invention

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

[0004] In a first aspect, a method for wireless communication is provided, comprising: a first terminal device sending a first request, the first request being used to request a first SIB of a first cell; the first terminal device receiving the first SIB and / or configuration information of the first SIB; wherein the first cell is a serving cell corresponding to the first terminal device, and the first SIB includes SIB1 of the first cell.

[0005] In a second aspect, a method for wireless communication is provided, comprising: a first network device corresponding to a first cell receiving a first request sent by a first terminal device, or receiving a second request sent by a second network device corresponding to a second cell, wherein the first request is used to request a first SIB of the first cell, and the second request is determined according to the first request; the first network device sending the first SIB and / or configuration information of the first SIB to the first terminal device; wherein the first cell is a serving cell corresponding to the first terminal device, and the first SIB includes SIB1 of the first cell.

[0006] Thirdly, a method for wireless communication is provided, comprising: a second network device corresponding to a second cell receiving a first request sent by a first terminal device, the first request being used to request a first SIB of the first cell; the second network device sending configuration information of the first SIB to the first terminal device; wherein the first cell is a serving cell corresponding to the first terminal device, and the first SIB includes SIB1 of the first cell.

[0007] Fourthly, a method for wireless communication is provided, comprising: a second terminal device receiving a first request sent by a first terminal device, the first request being used to request a first SIB of a first cell; the second terminal device sending configuration information of the first SIB to the first terminal device; wherein the first cell is a serving cell corresponding to the first terminal device, and the first SIB includes SIB1 of the first cell.

[0008] Fifthly, an apparatus for wireless communication is provided, the apparatus being a first terminal device, the apparatus comprising: a transmitting unit for transmitting a first request, the first request being for requesting a first SIB of a first cell; and a receiving unit for receiving the first SIB and / or configuration information of the first SIB; wherein the first cell is a serving cell corresponding to the first terminal device, and the first SIB includes SIB1 of the first cell.

[0009] A sixth aspect provides an apparatus for wireless communication, the apparatus being a first network device corresponding to a first cell, the apparatus comprising: a receiving unit, configured to receive a first request sent by a first terminal device, or to receive a second request sent by a second network device corresponding to a second cell, wherein the first request is used to request a first SIB of the first cell, and the second request is determined based on the first request; and a sending unit, configured to send the first SIB and / or configuration information of the first SIB to the first terminal device; wherein the first cell is a serving cell corresponding to the first terminal device, and the first SIB includes SIB1 of the first cell.

[0010] A seventh aspect provides an apparatus for wireless communication, the apparatus being a second network device corresponding to a second cell, the apparatus comprising: a receiving unit for receiving a first request sent by a first terminal device, the first request being for requesting a first SIB of the first cell; and a sending unit for sending configuration information of the first SIB to the first terminal device; wherein the first cell is a serving cell corresponding to the first terminal device, and the first SIB includes SIB1 of the first cell.

[0011] Eighthly, an apparatus for wireless communication is provided, the apparatus being a second terminal device, the apparatus comprising: a receiving unit configured to receive a first request sent by a first terminal device, the first request being for requesting a first SIB of a first cell; and a sending unit configured to send configuration information of the first SIB to the first terminal device; wherein the first cell is a serving cell corresponding to the first terminal device, and the first SIB includes SIB1 of the first cell.

[0012] A ninth aspect provides a communication device 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 any one of the first to fourth aspects.

[0013] A tenth aspect provides an apparatus including a processor for calling a program from memory to perform the method as described in any one of the first to fourth aspects.

[0014] Eleventh aspect: A chip is provided, including 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 the first to fourth aspects.

[0015] In a twelfth aspect, a computer-readable storage medium is provided having a program stored thereon that causes a computer to perform the method described in any one of the first to fourth aspects.

[0016] In a thirteenth aspect, a computer program product is provided, comprising a program that causes a computer to perform the method as described in any one of the first to fourth aspects.

[0017] Fourteenth aspect, a computer program is provided that causes a computer to perform the method as described in any one of the first to fourth aspects.

[0018] In this embodiment, the first terminal device receives the first SIB of the first cell only after sending a first request for the first SIB. The first SIB includes SIB1. Therefore, the SIB1 received by the first terminal device is not sent periodically, but only upon request from the first terminal device. Consequently, the network device corresponding to the first cell can send SIB1 on demand, thereby achieving network energy saving. Attached Figure Description

[0019] Figure 1 This is the wireless communication system used in the embodiments of this application.

[0020] Figure 2 This is a flowchart illustrating a method for wireless communication provided in an embodiment of this application.

[0021] Figure 3 yes Figure 2 The diagram illustrates a possible application of the method in a single-cell scenario.

[0022] Figure 4 yes Figure 3 A possible flowchart for the scenario shown.

[0023] Figure 5 yes Figure 3The diagram illustrates another possible process for the scenario shown.

[0024] Figure 6 yes Figure 2 The diagram illustrates a possible application of the method in a multi-cell scenario.

[0025] Figure 7 yes Figure 6 A possible flowchart for the scenario shown.

[0026] Figure 8 yes Figure 2 A schematic diagram of one possible implementation of the method shown.

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

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

[0029] Figure 11 This is a schematic diagram of another device for wireless communication provided in the embodiments of this application.

[0030] Figure 12 This is a schematic diagram of another device for wireless communication provided in the embodiments of this application.

[0031] Figure 13 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application. Detailed Implementation

[0032] The technical solutions of the embodiments of this application will now be described with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. All other embodiments obtained by those skilled in the art without creative effort regarding the embodiments of this application are within the scope of protection of this application.

[0033] 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), General Packet Radio Service (GPRS), Long Term Evolution (LTE), Advanced Long Term Evolution (LTE-A), New Radio (NR), evolution systems of NR, LTE-based access to unlicensed spectrum (LTE-U), NR-based access to unlicensed spectrum (NR-U), Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (WiFi), and 5th-generation (5G) systems. The embodiments of this application can also be applied to other communication systems, such as 6th-generation (6G) mobile communication systems, or future communication systems such as satellite communication systems.

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

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

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

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

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

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

[0040] 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, 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.

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

[0042] 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, 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, radio node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. A base station can be a macro base station, micro base station, relay node, donor node, or similar entities, or combinations thereof. A base station can also refer to a communication module, modem, or chip installed within the aforementioned equipment or apparatus. A base station can also be a mobile switching center, a device that performs base station functions in D2D, V2X, and M2M communications, a network-side device in a 6G network, or a device that performs base station functions in future communication systems. A base station 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.

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

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

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

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

[0047] For example, Figure 1 This is a schematic diagram of the architecture of a communication system provided in an embodiment of this application. Figure 1 As shown, the communication system 100 may include a network device 110, which may be a device that communicates with a terminal device 120 (or a communication terminal, terminal). The network device 110 can provide communication coverage for a specific geographical area and can communicate with terminal devices located within that coverage area.

[0048] Figure 1 An exemplary network device and two terminal devices are shown. In some embodiments of this application, the communication system 100 may include multiple network devices and each network device may include other numbers of terminal devices within its coverage area, without limitation.

[0049] In the embodiments of this application, Figure 1 The communication system shown may also include other network entities such as a mobility management entity (MME) and an access and mobility management function (AMF), but this application does not limit this.

[0050] It should be understood that devices with communication functions in the network / system of this application embodiment can be referred to as communication devices. Figure 1Taking the communication system 100 shown as an example, the communication equipment may include a network device 110 and a terminal device 120 with communication functions. The network device 110 and the terminal device 120 may be the specific devices described above, which will not be repeated here. The communication equipment may also include other devices in the communication system 100, such as network controllers, mobility management entities and other network entities. This application embodiment does not limit this.

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

[0052] 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, novel modulation techniques, novel coding techniques, and higher-order modulation techniques. Through these technologies, peak data rates reaching Gbit / s can be achieved.

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

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

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

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

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

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

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

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

[0061] SIB1 can carry key information required for terminal equipment to access the cell, such as random access parameters. SIB1 can also carry 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.

[0062] 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 can include information for the terminal device to perform a system information (SI) request.

[0063] 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 the SI window). Only SIBs with the same period can be mapped to the same SI message. 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 an 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.

[0064] 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. Therefore, in some scenarios, the periodic transmission of SIB1 by network devices may result in significant energy waste.

[0065] To achieve network energy efficiency, it is necessary to reduce unnecessary SIB1 transmissions and associated PRACH monitoring. Therefore, it is necessary to study on-demand SIB1 transmissions of terminal devices in idle / inactive states, thereby providing network devices with more opportunities to enter sleep mode.

[0066] However, how to achieve on-demand SIB1 transmission to save network equipment energy is a technical challenge worth studying.

[0067] It should be noted that the energy waste caused by the periodic transmission of SIB1 by network devices mentioned above is only an example. The embodiments of this application can be applied to any type of communication scenario where communication devices waste energy due to the periodic transmission of messages.

[0068] To address the aforementioned issues, this application proposes a method for wireless communication. Using this method, a first terminal device receives the first SIB only after sending a first request to request a first SIB, thereby accessing the first cell. On the network side, network devices do not need to periodically send the first SIB; instead, they send it on demand based on the request from the first terminal device. Therefore, relevant network-side devices can remain in sleep or inactive modes for longer periods, thus achieving effective energy savings on the network side.

[0069] To facilitate understanding, the following will be combined with... Figure 2The methods proposed in the embodiments of this application will be described in detail. Figure 2 This is presented from the perspective of the interaction between the first terminal device and the second device. The dashed line indicates that the second device is not a specific device, but rather an optional communication device.

[0070] See Figure 2 In step S210, the first terminal device sends a first request.

[0071] The first terminal device can be any type of terminal device requesting the first SIB, and there is no limitation herein. In some embodiments, the first terminal device can be a terminal device in an idle state or an inactive state. For example, the first terminal device is a UE in an idle / inactive mode.

[0072] In some embodiments, the first terminal device is a device that supports network energy saving (NES) functionality.

[0073] The serving cell corresponding to the first terminal device is the first cell. In other words, the cell where the first terminal device is located is the first cell, or the network device corresponding to the first cell can provide services to the first terminal device.

[0074] In some embodiments, the area where the first terminal device is located is only near the first cell, that is, the first terminal device is in a single-cell scenario. Figure 3 For example, terminal device 310 is the first terminal device in a single-cell scenario, and the first cell is... Figure 3 Cell A (Cell#A) in the middle. Figure 3 In the first cell, the network device 320 can provide services to the terminal device 310.

[0075] In some embodiments, the area where the first terminal device is located includes multiple cells, and these multiple cells include the first cell. That is, multiple cells including the first cell are associated with the first terminal device; therefore, the first terminal device is in a multi-cell scenario. In this scenario, at least some of the multiple cells can provide services to the first terminal device through their respective network devices. For example, the first terminal device can receive information broadcast by at least some of the network devices corresponding to each of these at least some cells.

[0076] As an example, multiple cells associated with a first terminal device exist within a region. This region, for example, is a specific geographical area.

[0077] As an example, multiple cells associated with the first terminal device are located within a tracking area (TA). These multiple cells may correspond to the same tracking area code (TAC) or tracking area identity (TAI).

[0078] The following is based on Figure 6 This example illustrates a multi-cell scenario. See [link / reference] Figure 6 Terminal device 610 is the first terminal device in a multi-cell scenario. The multiple cells associated with the first terminal device are cell A, cell B (Cell#B), cell C (Cell#C), and cell D (Cell#D). Among them, cell B, where the first terminal device is located, is the first cell.

[0079] The network device corresponding to the first cell is the first network device. The first cell can provide services to the first terminal device through the corresponding first network device. The first network device can be any of the network devices mentioned above, and is not limited here.

[0080] In the embodiments of this application, the transmission / reception performed by any cell can be represented as the transmission / reception performed by the network device corresponding to the cell, or the transmission / reception performed by the cell through the corresponding network device.

[0081] In some embodiments, the first cell can be a cell where energy saving needs to be achieved on the network side. This cell can be any of the cell sizes described above. Energy saving needs to be achieved on the network side can include energy saving of network equipment or energy saving of the core network. Optionally, the first cell can be an NES cell or a network energy-saving cell with similar functions.

[0082] As an example, the PBCH or MIB in an SSB typically provides the parameter set for SIB1 transmission, the search space, and the corresponding SIB1 scheduling core. Within this core, the terminal device can listen for SIB1 scheduling based on the indication of a special system message, the Radio Network Temporary Identifier (SI-RNTI). However, in on-demand SIB1 (first cell) related technical solutions, the PBCH / MIB will not provide the parameter set for SIB1 transmission and / or SIB1 configuration, nor will it provide the search space and the corresponding SIB1 scheduling core, thereby enabling energy saving on the network side.

[0083] For example, for the first terminal device in idle / inactive mode, the cell that transmits SIB1 on demand can be an NES cell.

[0084] As an example, in a multi-cell scenario, the multiple cells may include one or more NES cells and at least one non-NES cell. The one or more NES cells include a first cell. Compared to NES cells, non-NES cells have relatively lower energy-saving requirements. Optionally, non-NES cells can also be considered conventional cells.

[0085] As an example, a non-NES cell can assist a first terminal device in obtaining the relevant SIB of the first cell. When a non-NES cell is used by the first terminal device to obtain the first SIB, the non-NES cell can also be called an auxiliary cell or anchor cell.

[0086] For example, the plurality of cells may include one anchor cell and multiple non-anchor cells (i.e., NES cells). For example, in Figure 6 The multiple cells shown include one anchor cell (cell A) and multiple non-anchor cells (cell B, cell C, and cell D).

[0087] Optionally, the second cell can be any other cell within the same tracking area as the first cell.

[0088] Optionally, the second cell may be a non-NES cell (anchor cell) among multiple cells associated with the first terminal device.

[0089] Optionally, when the second cell serves as an auxiliary cell, the second cell can be a neighboring cell of the first cell or an auxiliary cell that may perform carrier aggregation. As an example, in a multi-cell scenario, the first terminal device can utilize an auxiliary cell to request the first SIB.

[0090] As an example, the second cell can provide idle / inactive terminal devices with information related to the first SIB. This information is typically provided in the system information of the first cell or in proprietary signaling to facilitate reception by the idle / inactive terminal device. In embodiments of this application, the system information sent by the second cell may include information required by the first cell (NES cell) to request the first SIB.

[0091] In some embodiments, the first terminal device may send a first request to the second device, such as... Figure 2 As shown. The second device is any one of a variety of devices capable of communicating with the first terminal device.

[0092] As an example, the second device could be the first network device corresponding to the first cell. The first terminal device can communicate with the first network device through the resources of the first cell. For example, the second device could be... Figure 3 Network device 320 or Figure 6Network device 630.

[0093] Optionally, the first terminal device may directly send the first request to the first network device. For example, Figure 3 Terminal device 310 (first terminal device) can send a first request to network device 320 (first network device) via uplink 301. For example, Figure 6 The terminal device 610 can send a first request to the network device 630 through the uplink 604.

[0094] As an example, the first network device can send periodic SSBs that do not contain SIB1 configuration information.

[0095] As an example, the first network device can also monitor the first request and respond promptly. That is, even if the first cell is in sleep mode, it will still monitor the first request sent by the terminal device.

[0096] As an example, the first network device can receive a first request sent by the first terminal device. This will be discussed later. Figure 4 and Figure 5 An exemplary description is provided for the communication between the first terminal device and the first network device.

[0097] As an example, the second device can be a network device corresponding to another cell associated with the first cell. The other cells associated with the first cell include the second cell. The first terminal device can communicate with the second network device corresponding to the second cell through the resources of the second cell. The second network device can be any of the network devices described above. For example, the second device could be... Figure 6 Network device 620.

[0098] Optionally, the first terminal device may send a first request to the second network device to request the second cell to assist it in acquiring the first SIB. For example, in Figure 6 In the process, terminal device 610 can send a first request to network device 620 through uplink 602.

[0099] Optionally, the second network device may send a second request to the first network device to trigger a response from the first cell to the first terminal device's first request. The second request can be determined based on the first request. For example, the second request may include the first request, or it may be the first request itself.

[0100] As an example, the first network device can send the configuration information of the first SIB to the second network device. The configuration information of the first SIB will be explained in detail below in conjunction with step S220.

[0101] For example, the configuration information of the first SIB can be used by the second network device to respond to the first request from the first terminal device, or it can be used by the second network device to determine the resource configuration information of the first request. For instance, the second network device can directly send the configuration information of the first SIB to the first terminal device after receiving the first request. Alternatively, after receiving the configuration information of the first SIB, the second network device can configure the transmission resources of the first request so that terminal devices in the first cell that are in an idle or inactive state can send the first request upon access.

[0102] For example, when the first cell determines that there are non-NES cells in the vicinity, the first network device can send the configuration information of the first SIB to the network device corresponding to the non-NES cell, so that the non-NES cell can assist the first terminal device in requesting the first SIB.

[0103] As an example, the second device may include a first network device and a second network device. The first terminal device may send a first request with the assistance of the second network device and receive configuration information of a first SIB / first SIB sent by either the first or second network device. This will be discussed in conjunction with... Figure 7 An example is provided to illustrate the communication between the first terminal device and the two cells.

[0104] As an example, the second device can also be a terminal device other than the first terminal device, such as a second terminal device. The second terminal device can be any type of terminal device surrounding the first terminal device. For example, for the first request sent by the first terminal device to trigger the transmission of on-demand SIBs in the first cell, other terminal devices can also undertake the auxiliary function of transmitting the first SIB.

[0105] Taking a UE as an example, there are always many UEs around a single UE, thus providing the potential for UE collaboration. In other words, multiple UEs can help activate one UE to more reliably receive / send data from the network, thereby improving overall spectrum efficiency, system capacity, and UE experience. The network can assist UE collaboration and provide more possible transmission paths from the network to the target UE, resulting in better coverage. In very dense networks, the access network can also schedule users who benefit from UE collaboration, taking into account factors such as the creation of cooperation groups, signaling transmission and sharing, privacy restrictions, battery consumption, and collaboration incentives. For example, multiple UEs in close proximity can be grouped into a UE cooperation group (CG), which will be discussed later. Figure 8 An example is provided.

[0106] In some implementations, the first terminal device can form a UE cooperation group with multiple terminal devices. The UE cooperation group may include at least one cooperating UE (CUE) and a target UE (TUE). Optionally, the CUE can be a second terminal device in a non-NES cell, and the TUE can be the first terminal device.

[0107] Optionally, the cell where the second terminal device is located is a non-NES cell, so that the second terminal device can assist the first terminal device in obtaining the first SIB or the configuration information of the first SIB. When the second terminal device is in a non-NES cell, the second terminal device can store or receive SIB-related information from adjacent NES cells, and the first terminal device can obtain the SIB information within the NES cell from the second terminal device.

[0108] As an example, after receiving the first request, the second terminal device can send the configuration information of the first SIB to the first terminal device. After obtaining the configuration information of the first SIB, the first terminal device can also send the information to the third terminal device in the first cell.

[0109] As an example, the second terminal device can also send the resource configuration information requested in the first request to the first terminal device. The resource configuration information requested in the first request is, for example, the transmission time / frequency resources requested in the first request.

[0110] As an example, the second terminal device can also act as a relay for the first terminal device to communicate with network devices. That is, the CUE in the cooperation group can effectively act as a relay for UE-to-Network communication towards the TUE.

[0111] As an example, within a collaboration group, a second terminal device of the CUE can expand the collaboration group based on sensing results. For instance, the CUE can select from a group of active or idle devices near the TUE, and can add these devices to the collaboration group to expand the collaboration group, provided that these devices are willing to collaborate or can sense other terminal devices through sensing.

[0112] As an example, the second terminal device can forward cooperation information to the first terminal device to help the first terminal device receive data. For instance, the CUE can forward cooperation information to the TUE to help the TUE decode data packets received during the multicast phase.

[0113] As an example, the association information or resource configuration information sent by the second terminal device to the first terminal device depends on the cooperation strategy. That is, during the cooperation phase, the information sent by the second terminal device depends on the cooperation strategy. These cooperation strategies include amplification and forwarding, decoding and forwarding, compression and forwarding, (frequency-selective) soft forwarding, joint reception, etc., of information related to the first SIB.

[0114] As an example, during sidelink communication (including licensed spectrum or shared spectrum), the first terminal device can also obtain relevant information about the first SIB from the second terminal device.

[0115] In some embodiments, the first terminal device may send a first request to multiple second devices simultaneously. For example, since the first terminal device is in an idle or inactive state, when the first terminal device confirms the resource configuration information of the first cell and the second cell in the first terminal device, the first terminal device may send the first request to the first cell and the second cell simultaneously, and both the first cell and the second cell will respond.

[0116] The above describes how the first terminal device sends a first request to various second devices, and the first request is used to request the first SIB of the first cell.

[0117] In some embodiments, the first SIB is one or more SIBs sent by the first network device according to the needs of the terminal device. Therefore, the first network device does not need to send the first SIB periodically, but rather sends it on demand to achieve energy saving. For example, the first network device does not need to send SIB1 according to a 160ms period and a transmission repetition period within 160ms, but instead sends it according to a first request.

[0118] The first SIB includes SIB1 of the first cell. Network devices can send SIB1 upon request from terminal devices, thereby reducing unnecessary SIB1 transmissions. As an example, the first SIB can be SIB1 of the first cell, all SIBs of the first cell, or a subset of SIBs in the first cell that includes SIB1.

[0119] In some implementations, when the first cell is an NES cell, the sent SSB may not contain the parameter set of SIB1, thereby reducing transmission overhead. However, part of the cell random access configuration is provided in SIB1. When the first terminal device discovers the first cell and wishes to access it, it needs to request the first SIB because the received SSB does not contain the parameters of SIB1.

[0120] In some embodiments, the first SIB is the SIB required by the first terminal device, and may also be referred to as an on-demand SIB. Accordingly, SIB1 included in the first SIB may also be referred to as on-demand SIB1, and the first request may also be referred to as an on-demand SIB1 request.

[0121] In some embodiments, the first cell may periodically transmit SSBs but not periodically transmit SIB1. Compared to the first cell, which is a non-anchor cell, the second cell, which is the anchor cell, can be the cell that transmits both SSBs and SIB1 and provides information related to the on-demand SIB1 process. For example, in... Figure 3 In this context, cell A, which is in service (on), periodically sends SSBs (always on). However, the SSBs do not include SIB1. For example, in... Figure 6 In the process, cells B, C, and D, which are in service, only send SSB (SSB only), but cell A sends both SSB and SIB1.

[0122] In some embodiments, when the first cell periodically transmits an SSB, the transmission period of the SSB can be fixed or variable. For example, in an NES cell, SSB transmission can support both periodic transmission with a fixed period length and transmission with a variable period length.

[0123] As an example, the SSB transmission period can be dynamically adjusted based on cell load. That is, if there are differences in the SSB transmission period, the SSB can be dynamically transmitted according to the cell load. For example, if the cell load is relatively light, the SSB transmission period can be relatively longer; if the cell load is relatively heavy, the SSB transmission period can be relatively shorter.

[0124] As an example, the transmission period of an SSB can be a combination of long and short periods. For instance, an SSB can be transmitted with alternating long and short periods: long period, short period, long period, short period. In this scenario, the first cell can choose to transmit SIB information during the long SSB period and only transmit SSB information during the short SSB period. Therefore, the first cell does not carry SIB1 information in every SSB, but rather transmits SIB1 information intermittently or at relatively fixed intervals, thus achieving energy savings to some extent.

[0125] It should be noted that in the first cell, SSB transmission also supports on-demand transmission. For example, if the SSB transmission cycle remains unchanged, when transmitting an SSB on demand, the SSB will always carry SIB information. In this scenario, the first terminal device requesting the SSB of the first cell can also be considered equivalent to the first terminal device requesting the first SIB of the first cell.

[0126] The first request can be implemented in multiple ways. That is, the first terminal device can send information for requesting the first SIB in multiple ways. Optionally, the first request may include one or more of the following: a wake uplink signal (WUS), a request information / request signaling for requesting the first SIB, a first sequence for requesting the first SIB; and a preamble index associated with the first SIB.

[0127] In some embodiments, the first request may be a WUS, also known as an UL WUS. The WUS can be used to wake up the first cell and the first network device in sleep mode, or it can request the first network device not in sleep mode to send a first SIB. For example, when the first cell detects the WUS sent by the first terminal device, the first network device can send an on-demand SIB1.

[0128] As an example, in a single-cell scenario, since the first cell does not carry SIB1 information when sending SSB, the first terminal device needs to send WUS to trigger the first cell to send the first SIB. The first SIB may include SIB1 information.

[0129] As an example, in a multi-cell scenario, it's necessary to consider whether the first cell where the first terminal device is located is an NES cell or a non-NES cell. If the first cell is an NES cell, after reading the cell's SSB, the first terminal device can send WUS to the NES cells and / or non-NES cells among the multiple cells. If the first cell is a non-NES cell, the first terminal device can receive SIB information.

[0130] Optionally, in a multi-cell scenario, if the first cell sends WUS to both NES and non-NES cells, the design of the WUS for the NES and non-NES cells can be different or the same.

[0131] In some embodiments, the first request may be on-demand information / demand signaling for requesting the first SIB. This on-demand information / demand signaling may also be used to wake up the first cell and the first network device, or to request the first SIB from the first cell. For example, when the first cell detects the on-demand information / demand signaling sent by the first terminal device, the first network device may send on-demand SIB1.

[0132] As an example, demand signaling can be either control signaling or data signaling, without limitation.

[0133] As an example, in a single-cell scenario, since the first cell does not carry SIB1 information when sending SSB, the first terminal device needs to send demand information / demand signaling to trigger the first cell to send SIB1 or SIB1 configuration information.

[0134] As an example, in a multi-cell scenario, if the first cell where the first terminal device is located is an NES cell, after reading the SSB of the cell, the first terminal device can send demand information / demand signaling to the NES cells and / or non-NES cells among the multiple cells.

[0135] In some embodiments, the first request may be a first sequence for requesting a first SIB. The first sequence may be a separate sequence or a separate signal. That is, the first terminal device does not need to share resources of other communication processes when sending the first sequence. For example, when the first cell detects the first sequence sent by the first terminal device, the first network device may send an on-demand SIB1.

[0136] In some embodiments, the first request may be a preamble index associated with the first SIB. As an example, when the first terminal device performs random access, the preamble index sent may be a configured specified index. When the first terminal device selects this specified index, it indicates that the first terminal device is requesting the network device to send the first SIB. As one implementation, when the first terminal device requests the base station to send SIB1 based on the specified preamble index, the base station can respond to the first terminal device by sending a response message for the random access procedure. For example, message 2 (Msg2) used by the base station to respond to random access includes a random access preamble identifier (RAPID). When the RAPID matches the preamble index sent by the first terminal device, it can be considered that the base station has received the first terminal device's request for the first SIB.

[0137] In some embodiments, the first request may include at least two of the above implementation methods to wake up the first cell in a timely manner. For example, the first request may include an uplink wake-up signal and demand signaling for requesting the first SIB. Alternatively, when the first request is a wake-up signal, this signal may also be a known sequence.

[0138] In some embodiments, the first terminal device may send the first request in multiple ways. These multiple ways may include various uplink resources. Optionally, the first terminal device may send the first request alone or together with other uplink channels / messages.

[0139] As an example, the first request can be sent via the uplink channel of the first terminal device, and / or via resources indicated by the resource configuration information of the first request. Exemplarily, when the first request is sent alone, corresponding transmission resources need to be configured or pre-configured for the first request. The first terminal device can send the first request based on the resource configuration information after receiving it.

[0140] As an example, the resource configuration information for the first request refers to the information used to configure the transport resources for the first request. This resource configuration information can be pre-configured information for the transport resources or dynamically configured information for the transport resources.

[0141] In some implementations, the resource configuration information requested in the first request can be determined based on auxiliary information sent by the first cell and / or the second cell. This auxiliary information is used by the first terminal device to request a first SIB including SIB1, and can also be referred to as SIB1 information. Therefore, when the first terminal device is located in an NES cell, it can receive auxiliary information not only sent by the NES cell but also by non-NES cells. For example, in... Figure 6 In the middle, terminal device 610 can receive auxiliary information through downlink 601 or 603.

[0142] As an example, when the first terminal device detects auxiliary information from the second cell, the first terminal device does not need to access the second cell. This auxiliary information can provide the first terminal device with information related to the first SIB request procedure of the first cell (including resource configuration information for the first request). The first request sent by the first terminal device is configured to be sent on both the first and second cells.

[0143] As an example, the auxiliary information sent by the first cell and / or the second cell may include the resource configuration information of the first request, and the first terminal device can determine the transmission resources of the first request based on the auxiliary information.

[0144] As an example, the auxiliary information sent by the first cell and / or the second cell may include the configuration information of the first SIB, which can be used to determine the resource configuration information of the first request.

[0145] As an example, the second cell can determine the resource configuration information for the first request based on the configuration information of the first SIB sent by the first cell. In other words, the configuration information of the first SIB is used by the second network device to determine the resource configuration information for the first request. For instance, after receiving the configuration information of the first SIB, the second network device can determine the time-frequency resources for transmitting the first request and notify the first terminal device.

[0146] As an example, the first network device may send the resource configuration information and / or the configuration information of the first SIB to the second network device in order to enable the second cell to determine auxiliary information.

[0147] As an example, the auxiliary information for the second cell can be configured with one NES cell or multiple NES cells.

[0148] In some embodiments, when the auxiliary information is sent by a second cell acting as an anchor cell, the second cell can provide auxiliary information for multiple SIBs of multiple surrounding NES cells to assist terminal devices within the multiple NES cells in requesting SIB1. In this scenario, multiple network devices corresponding to multiple NES cells can send SIB configuration information to the second network device. For example, the second network device can receive the configuration information of the first SIB sent by the first network device and determine the auxiliary information for the first terminal device to send the first request based on this information.

[0149] As an example, in a multi-cell scenario, the second cell can integrate the configuration information of multiple SIBs and send it to the first terminal device via broadcast or dedicated signaling. The first terminal device can then send a first request to the first cell based on the configuration information of the multiple SIBs.

[0150] For example, the SIB1 of the first cell can be multiplexed with the SIB1 of the second cell and / or other non-NES cells.

[0151] For example, configuration information for multiple SIBs of multiple NES cells can be multiplexed using signaling transmitted by the second cell, or the configuration information for multiple SIBs can be carried on different downlink channels. For instance, when the second cell transmits configuration information for one or more SIBs of one or more NES cells, the SIBs from different NES cells can be multiplexed together and transmitted via common signaling (such as SSB). Terminal devices in different cells can distinguish the configuration information required by their respective cells using index numbers. Alternatively, when the second cell transmits configuration information for one or more SIBs of one or more NES cells, the configuration information for each SIB can be carried via a separate physical downlink shared channel (PDSCH).

[0152] As an example, the second network device can receive resource configuration information and SIB configuration information from multiple first requests sent by multiple network devices. The multiple cells corresponding to the multiple network devices are NES cells, and the multiple network devices include the first network device. The resource configuration information and SIB configuration information from the multiple first requests are used by the second network device to determine auxiliary information for each of the multiple network devices.

[0153] For example, multiple NES cells can send the configured resource configuration information of the first request to a second cell. If the configuration resources of any NES cell change, the second cell must also be notified promptly. For instance, if the resources configured by the first cell for the first terminal device in the first request change, the base station of the first cell can notify the base station of the second cell that the resources requested in the first request have changed. The base station of the second cell can store this change, and the resource configuration sent to the first terminal device next time will be the new resource configuration.

[0154] As an example, the auxiliary information transmitted by the second cell as the anchor cell may include some or all of the following: a list of selectable non-anchor cells (non-anchored cells) and cell indexes and / or physical cell identifiers (PCIs); power control parameters when the first request (e.g., WUS) is transmitted on the NES cell; whether the anchor cell transmits SIB1 information for non-anchor cells; PRACH configuration; CORESET / UE's search space set configuration for receiving random access responses (RARs) or SIB1s from non-anchor cells; and the transmission time / frequency resources for the first request.

[0155] For example, based on the auxiliary information of the second cell, the first terminal device already knows the list of anchor cells and non-anchor cells in the vicinity (e.g., within the coverage area of ​​the same TAC) during initial access, or the list of anchor cells near its own non-anchor cell. For example, the first terminal device can receive auxiliary information provided by the anchor cell through SSB information or other public or private signaling from the anchor cell. Generally, the configuration and resources of the first cell and the second cell regarding the first request are the same. However, when the configuration information of the two cells differs, the first terminal device needs to make a reasonable selection for cell access.

[0156] As one implementation, the resource configuration information in the first request may include first configuration information sent by the first cell and second configuration information sent by the second cell. When the first configuration information differs from the second configuration information, the first terminal device can send the first request based on the first configuration information. In other words, if there is a difference in resource configuration, the first terminal device will use the configuration of its own first cell as the standard.

[0157] As another implementation, the resource configuration information in the first request may include first configuration information sent by the first cell and second configuration information sent by the second cell. When the first configuration information differs from the second configuration information, the first terminal device can choose to send the configuration information for the first request from the first configuration information and the second configuration information. That is, the first terminal device can choose to send the first request using either the first configuration information or the second configuration information.

[0158] For example, the first terminal device can select appropriate configuration information based on the service type. The service type may include the service priority, urgency, etc., which are not limited here. For instance, if the first terminal device's service is urgent and the service time is short, the first terminal device can directly access the first cell based on the configuration information of the second cell.

[0159] In some embodiments, the first request carries a relatively small amount of information and occupies very few resources. In multi-cell scenarios, the resources configured for the first request in different NES cells can be the same. For example, within a cell area covered by the same TAC, all NES cells configure or reserve the same resources for the first request. For instance, multiple first requests from multiple NES cells may be located at the same time-frequency resource location.

[0160] In some embodiments, multiple terminal devices may send a first request, and the system can configure a resource pool (first resource pool) for multiple terminal devices or network devices to select configurable resources for the first request. In this case, the resource configuration information of the first request is determined based on the first resource pool. Optionally, as long as there are resources in the first resource pool, the first requests from different terminal devices will be received.

[0161] In some embodiments, different terminal devices may send the first request simultaneously. Although the resources for the first request are pre-configured, the network device's resources are limited. Therefore, the first or second network device can set up a buffer to receive on-demand SIB requests from multiple terminal devices. As an example, the buffer can store the first requests from different terminal devices according to a first-come, first-served principle.

[0162] In some embodiments, the resource configuration information of the first request is also related to the type or sending method of the first request.

[0163] As an example, when the first request is a standalone WUS (Warranty Request), the WUS can be a sequence. In this scenario, the sender and receiver can agree in advance on the content and timing of the sequence to facilitate wake-up.

[0164] As an example, the resource configuration information in the first request can also be carried in the SSBs sent by different cells. These different cells can include the first cell, the anchor cell among the multiple cells mentioned above, or any cell among multiple cells. For example, when the first request is for WUS, the WUS configuration information can be carried and sent by the SSB of the second cell.

[0165] As one implementation method, in a single-cell scenario, the first terminal device can determine the sending method of the first request based on whether the SSB sent by the first cell carries the resource configuration information of the first request.

[0166] For example, the first terminal device may receive a first SSB sent by the first cell. When the first SSB does not contain resource configuration information for the first request, the first terminal device sends the first request via PRACH; or, when the first SSB contains resource configuration information for the first request, the first terminal device sends the first request via PRACH or the resource indicated by the resource configuration information. For example, when sending the first request based on resource configuration information, the first terminal device may send a separate signal or sequence on the resource indicated by the resource configuration information.

[0167] In some embodiments, when the first terminal device sends a first request via uplink resources, multiple uplink (UL) channels can be considered. Optionally, the first request can be sent via one or more of PRACH, physical uplink control channel (PUCCH), and physical uplink shared channel (PUSCH). For example, the first request can be carried on these uplink channels. Alternatively, the first request can share the same resources with these uplink channels for transmission.

[0168] As an example, the first request can be sent along with messages in the random access procedure. For instance, when the first request is sent via PRACH, it can be carried in an uplink message of the random access procedure. Considering different types of random access procedures, this uplink message can include one or more of the following: message 1 (Msg1), message A (MsgA), and message 3 (Msg3). For example, when the first terminal device sends a WUS to the base station, the WUS can be sent alone or together with Msg1 / MsgA. This will be discussed later in conjunction with... Figure 4 and Figure 5 The following are examples illustrating the process of requesting the first SIB based on message 1 and message 3 respectively.

[0169] As an example, when the first terminal device sends a first request via PRACH, this PRACH can be specifically designed for the first request from the first terminal device in idle / inactive mode. For instance, this PRACH may not perform uplink synchronization. That is, this PRACH may not establish synchronization with the uplink.

[0170] As an example, the PRACH used for the first request can be configured on the first cell (non-anchor cell) and / or the second cell (anchor cell). That is, the resource configuration information of the first request can indicate the random access resources of the first cell and / or the second cell.

[0171] Optionally, when the resource configuration information of the first request indicates the resources of the second cell, the first request may be monitored by the second cell alone, or it may be monitored by both cells together if the first cell and the second cell are synchronized.

[0172] In some embodiments, whether the first request is sent alone or sent together with other messages, the procedures related to the first request can share the first resource with the random access procedure. That is, the first request can be sent through the common resources of the random access procedure.

[0173] Optionally, the process related to the first request may include the transmission of UL / DL (downlink, DL) signals associated with the request of the first SIB. The transmission resources for these UL / DL signals need to be configured.

[0174] Optionally, the common resources for the random access procedure may include the common resources within the first cell used by the terminal equipment to perform the random access procedure, or the common resources of the multiple cells mentioned above used by the terminal equipment to perform the random access procedure.

[0175] As an example, public resources may include public random access channel (RACH) resources. That is, resources used to transmit the DL / UL signal associated with the first request and resources configured to share the public RACH at least partially.

[0176] As an example, considering that the first request is sent along with RACH, at least the public resources of RACH can be shared.

[0177] As an example, the first request is sent through the common resources of the random access procedure of the first cell. The common resources of the random access procedure of the first cell may include all or some of the resources of the first cell used for random access.

[0178] As an example, the first request is sent via the common resources of the random access procedure of the second cell (anchor cell) among multiple cells. The common resources of the random access procedure of the second cell may include all or some of the resources used by the second cell for random access.

[0179] As an example, in a multi-cell scenario, when the PRACH of the second cell (anchor cell) is associated with multiple non-anchor cells, different indexes can be created for these non-anchor cells to help the terminal device determine which cell it is accessing via the PRACH configuration. As mentioned earlier, the auxiliary information provided by the second cell can include a list of multiple non-anchor cells and their indexes.

[0180] As an example, based on the resource configuration information of the first request, the first request can be sent through one or more random access channel occasions (ROs). RO can also represent a PRACH occasion. That is, the resource configuration information of the first request can indicate one or more ROs for sending the first request. For example, the first request can be sent through the first RO indicated by the resource configuration information.

[0181] In some implementations, one or more Remote Access Registries (ROs) used for the first request can be additionally configured ROs. That is, these ROs are distinct from the ROs used for random access. ROs configured for traditional terminal devices can be called default ROs, while additional ROs configured for terminal devices supporting NES functionality can be called NES ROs, to simultaneously meet the requirements of random access and network energy saving. For example, a base station in an anchor cell can configure a default RO for traditional UEs and additional NES ROs for UEs supporting NES functionality. Therefore, the one or more ROs used by the first terminal device to send the first request are NES ROs.

[0182] As an example, the default RO can be a relatively sparse RO, while the NES RO can be a relatively dense RO. For instance, the NES RO can be configured to have a different RO cycle than the default RO through configuration parameters.

[0183] As an example, one or more ROs can be configured by reusing some parameters from the traditional PRACH configuration, or they can be configured through a separate PRACH configuration. In other words, a dedicated PRACH configuration can be set for NES ROs.

[0184] As an example, one or more ROs can be used by the first terminal device to send the first request. For instance, in scenarios with short RO cycles, a sufficient number of ROs can be configured to meet the transmission requirements of the first request and the random access channel.

[0185] As an example, the configuration of one or more ROs can be indicated by downlink control information (DCI) or a medium access control (MAC) control element (CE). The DCI can be a configured grant-DCI (CG-DCI). Therefore, the resource configuration information requested initially can include indications from DCI or MAC-CE. When the configuration of one or more ROs is indicated by DCI or MAC-CE, alignment is required between the first terminal device and the network device to meet the adjustment requirements of the RO configuration starting point.

[0186] Optionally, the time-domain location of one or more ROs can be determined based on the reception time of the configuration indication information. That is, the time-domain location of one or more ROs is determined based on the reception time of the resource configuration information.

[0187] Optionally, the time-domain location of one or more ROs is determined based on the reception time of the indication information configured therein and a first time parameter. That is, the time-domain location of one or more ROs is determined based on the reception time of the resource configuration information and a first time parameter.

[0188] As an example, the first time parameter can be a time period T. This time period T can be a predefined time period or can be directly indicated among multiple pre-configured candidates. For example, the time domain location of one or more ROs can be located after the time period T that starts from the reception time of the (CG-)DCI or MAC-CE indicating the NES RO.

[0189] As an example, the first time parameter can be a time period associated with a pattern or service type. For instance, the time domain location of one or more ROs can be located after an associated time period starting from the reception time of (CG-)DCI or MAC-CE.

[0190] As an example, once one or more configured Remote Access Roots (ROs) are exhausted, all terminal devices will be limited to using the default RO. These terminal devices can include both traditional devices and those supporting NES functionality. In cases of high access latency or congestion, the number of default ROs may be insufficient. In such situations, the base station can provide additional NES ROs for NES-enabled terminal devices. Alternatively, NES-enabled terminal devices can send requests to the base station as needed.

[0191] See also Figure 2 In step S220, the first terminal device receives the first SIB and / or the configuration information of the first SIB.

[0192] In some embodiments, the first SIB can be a system information block directly received by the first terminal device, and the configuration information of the first SIB can be used by the first terminal device to receive the first SIB. That is, the first terminal device can receive the first SIB and its configuration information.

[0193] As an example, the first terminal device can receive the first SIB sent by the first network device. For example, in Figure 3 In this context, terminal device 310 can receive the first SIB (e.g., on-demand SIB1) sent by network device 320 via downlink 302. For example, in... Figure 6 In this process, terminal device 610 can receive the first SIB sent by network device 630 through downlink 603.

[0194] As an example, the first terminal device can receive configuration information of the first SIB sent by the first network device. For example, in Figure 6 In this process, terminal device 610 can receive configuration information of the first SIB sent by network device 620 through downlink 601.

[0195] As an example, the first terminal device can receive configuration information of the first SIB sent by the second terminal device. For example, in Figure 8 In this process, terminal device 820 can receive the configuration information of the first SIB sent by terminal device 810 through a cooperative group or a side link.

[0196] In some embodiments, when a first terminal device sends a first request to multiple devices simultaneously, the first terminal device may receive configuration information of a first SIB from each of the multiple devices. In this scenario, the first terminal device can select the configuration information of the SIB based on the first information. For example, when the first terminal device receives the configuration information of a first SIB sent by a first cell and the configuration information of a second SIB sent by a second cell, the first terminal device selects the configuration information of the first SIB used for accessing the first cell based on the first information.

[0197] As an example, the first information may include one or more of the following: the service level of the first terminal device; the service time of the first terminal device; and the measurement results of the first terminal device.

[0198] Optionally, the service level is related to the service type and service priority of the first terminal device.

[0199] Optionally, the service time is related to the urgency of the business, business needs, or user needs of the first terminal device.

[0200] Optionally, the measurement results may include parameters such as reference signal received power (RSRP).

[0201] In some embodiments, the configuration information of the first SIB may include the parameter set for SIB1 transmission, the search space, and the corresponding SIB1 scheduling CORESET. For example, the first terminal device may receive a PBCH / MIB containing configuration information and thus receive the first SIB.

[0202] In some embodiments, the configuration information of the first SIB can be used to determine relevant information about the first request from the first cell. The relevant information about the first request may include information related to the request process of the first SIB. The first SIB includes SIB1, and this information may also include information related to the on-demand SIB1 process, i.e., information related to the process of the first terminal device requesting on-demand SIB1. For example, the information related to the on-demand SIB1 process may include RACH configuration that triggers on-demand SIB1.

[0203] As an example, in a multi-cell scenario, the configuration information of the first SIB can be sent by the first network device, the second network device, or the second terminal device; no limitation is made here. For example, in Figure 6 In this process, the terminal device can receive the configuration information of the first SIB sent by the network device 630 through the downlink 603, or it can receive the configuration information of the first SIB sent by the network device 620 through the downlink 601.

[0204] Optionally, when the second device is the first network device, if the first network device receives a first request from the first terminal device, it can send the first SIB or its configuration information. For example, after receiving an uplink wake-up signal from the first terminal device, the base station can send the first SIB or its configuration information via a broadcast message. The configuration information of the first SIB includes the configuration information of SIB1.

[0205] As an example, the configuration information of SIB1 received by the first terminal device can come from an NES cell or a non-NES cell.

[0206] In some embodiments, the first SIB broadcast by the first network device needs to be sent within the SSB cycle. In this scenario, if the first terminal device misses an SSB cycle, it needs to wait for access. The first terminal device can receive the first SIB in the next SSB cycle. For example, if the first SIB is SIB1, the first terminal device can wait for the PBCH / MIB to be sent in the next SSB cycle. As mentioned above, this PBCH / MIB can provide the parameter set, search space, and corresponding SIB1 scheduling CORESET for SIB1 transmission.

[0207] As an example, if the first request from the first terminal device is sent together with the random access procedure, the first network device can send its unique SIB1 information, which is the configuration information of the first SIB, to the first terminal device via broadcast information or proprietary information.

[0208] In some embodiments, the first terminal device may monitor the first SIB and / or its configuration information within a first time window. For example, the first terminal device may receive the first SIB and / or its configuration information sent by the first network device within the first time window. Alternatively, the first terminal device may receive the configuration information of the first SIB sent by the second network device within the first time window.

[0209] Taking SIB1 as an example, the time parameter of the first time window can be determined based on the sending time of the first request. For example, the first terminal device may expect to receive SIB1 during a SIB1 monitoring period of L milliseconds (or L time slots) after sending the first request. That is, the transmission time of SIB1 is a first time window (detection window) with a duration of L milliseconds.

[0210] Taking SIB1 as an example again, the time parameter of the first time window can be determined based on the length of the buffer (T1). For example, the first terminal device may expect to receive SIB1 during a SIB1 monitoring period of length T1 after sending the first request. Alternatively, the first terminal device may expect to receive SIB1 during a SIB1 monitoring period of length L+T1 after sending the first request. In other words, the transmission time of SIB1 is a first time window (detection window) of length L+T1.

[0211] As an example, the network device can explicitly notify the first terminal device of the time parameters of the first time window, so that the first terminal device can detect the first SIB and / or the configuration information of the first SIB at an appropriate time.

[0212] The above text combined Figure 2-3 and Figure 6 This paper introduces a method for a first terminal device to send a first request to request a first SIB, and the application of this method in single-cell and multi-cell scenarios.

[0213] exist Figure 3 In the single-cell scenario shown, terminal device 310 is the first terminal device, and cell A is the first cell. In the scenario where cell A is served, network device 320 of cell A will always periodically send SSB, and will only send on-demand SIB after receiving a request from terminal device 310.

[0214] exist Figure 6 In the multi-cell scenario shown, terminal device 610 is the first terminal device, cell B where the terminal device is located is the first cell, and cell A is the second cell. In this scenario, terminal device 610 can obtain ULWUS and SIB1 configurations from cells other than cell B.

[0215] like Figure 6 As shown, there are two types of cells in this area. One is the anchor cell (anchored cell), such as cell A; the other is the non-anchor cell (NES cell or on-demand SIB1 cell), such as cells B / C / D. The anchor cell periodically sends SSB and SIB1, while the non-anchor cell only sends SIB1 upon request from the terminal device.

[0216] To facilitate understanding, the following will be combined with... Figure 4-5 and Figure 7 The processes for single-cell and multi-cell scenarios are illustrated with examples respectively.

[0217] Figure 4 and Figure 5 This is a flowchart illustrating the process in a single-cell scenario. Figure 4 Taking the on-demand SIB1 request based on message 1 as an example, Figure 5 Take, for example, an on-demand SIB1 request based on message 3. It should be noted that... Figure 4 and Figure 5 The method shown can also be applied to multi-cell scenarios. Figure 4 and Figure 5 In this context, the first terminal device can be a UE, and the first network device can be the gNB corresponding to the first cell.

[0218] See Figure 4In step S410, the first terminal device receives the SSB sent by the first network device. The SSB does not contain configuration information for SIB1.

[0219] In step S420, the first terminal device sends a message 1 (Msg1 torequest SIB1) to the first network device requesting SIB1. That is, message 1 sent to the first network device carries a first request to request the first network device to send the SIB1 message. The first terminal device may also carry the first request in message A it sends.

[0220] In step S430, after receiving the first request, the first network device carries SIB1-related configuration information in message 2. The RAR of message 2 contains at least RAPID.

[0221] In step S440, the first network device can broadcast relevant information about SIB1.

[0222] See Figure 5 In step S510, the first terminal device receives the SSB sent by the first network device. The SSB does not contain configuration information for SIB1.

[0223] In step S520, the first terminal device sends message 1 to the first network device.

[0224] In step S530, the first network device sends message 2 to the first terminal device.

[0225] In step S540, the first terminal device sends message 3 to the first network device. The first terminal device may include a first request (RRCSib1Request) in message 3 to request the first network device to send SIB1.

[0226] In step S550, after receiving the first request, the first network device carries the configuration information of the first SIB in message 4.

[0227] In step S560, the first network device can broadcast relevant information about SIB1.

[0228] It should be understood that in some scenarios, both message 1 and message 3 can carry the first request. Regardless of the scenario, before initiating the SIB1 request process, the system needs to provide the first terminal device with the required information (e.g., sending UL-WUS resources and configurations).

[0229] Figure 7 This is a flowchart illustrating the process of requesting on-demand SIB1 in a multi-cell scenario. Figure 7The first terminal device can be a UE in an idle / inactive state, the first cell can be an NES cell, and the second cell can be an anchor cell. The dashed line indicates that this procedure is optional.

[0230] See Figure 7 In step S710, the second cell sends assistance information to the first terminal device through the second network device.

[0231] In step S720, the first cell sends a periodic SSB and performs a first request for monitoring (such as WUS monitoring).

[0232] In step S730, the first cell sends auxiliary information or configuration information (config info) to the first terminal device through the first network device.

[0233] In step S740, the first terminal device sends a first request (WUS requesting SIB1) to the first network device.

[0234] In step S750, the first network device sends an acknowledgment (ACK) to the first terminal device.

[0235] In step S760, the first network device sends a triggered SIB1 or possibly other SIBs.

[0236] As mentioned above, the first terminal device can also obtain the configuration information of the first SIB with the assistance of other terminal devices. For ease of understanding, the following section will combine... Figure 8 An example is provided.

[0237] Figure 8 The scenario shown includes two cells: cell A, which transmits periodic SIB1, and cell B, which transmits on-demand SIB1. Therefore, cell B is an NES cell, i.e., the first cell; while cell A is a non-NES cell (traditional cell). Cell A contains terminal device 810, while cell B contains terminal devices 820 and 830.

[0238] like Figure 8As shown, terminal devices 810, 820, and 830 can form a cooperative group. In this cooperative group, terminal device 820, located in cell B, is the first terminal device (target UE), and terminal device 830 is the third terminal device; terminal device 810, located in cell A, is the second terminal device (cooperating UE). Terminal device 810 in cell A stores SIB information or receives SIB1-related information from the neighboring NES cell (cell B). Terminal device 820 can obtain the SIB1 information within the NES cell from terminal device 810, and terminal device 820 can also send the received SIB1-related information to terminal device 830.

[0239] The above text combined Figures 3 to 8 This document describes application examples of the embodiments of this application in various scenarios. Regardless of whether it is a single-cell scenario, a multi-cell scenario, or a cooperative group scenario, the first terminal device needs to determine whether the first cell it is in is an NES cell. Optionally, the first terminal device can determine whether the first cell is an NES cell based on second information. When the first cell is an NES cell, the first terminal device can send a first request to the first cell and / or the second cell.

[0240] In some embodiments, the second information may include one or more of the following: whether the SSB sent by the first cell contains an identifier that the first cell is an NES cell; whether the MIB sent by the first cell contains an identifier that the first cell is an NES cell; whether the SSB or MIB sent by the first cell contains configuration information of the first SIB; and the load of the first cell.

[0241] As an example, the first terminal device can determine whether the first cell is an NES cell by using the SSB or other DL signals (such as PDCCH scheduling SIB1) sent by the first cell. For example, the PBCH of the SSB can contain an identifier of the NES cell. When the first terminal device receives this identifier information, it can clearly know that the cell it has accessed (i.e., the cell it is currently in) is an NES cell.

[0242] As an example, a first terminal device can determine whether a first cell is an NES cell by using the MIS (Mean Information Base) sent by the first cell. For instance, the MIS can contain an identifier for an NES cell. When the first terminal device receives this identifier, it can clearly know that the cell it is accessing (i.e., the cell it is currently in) is an NES cell.

[0243] As an example, when the SSB periodically sent by the first cell does not contain the configuration information of the first SIB, the first terminal device can consider the cell it accesses to be an NES cell.

[0244] As an example, whether the first cell is an NES cell is related to its load. For instance, to save energy, the network can support on-demand SIB transmission, but cell load must be considered. On-demand SIB transmission is suitable for medium-load scenarios. When the number of access terminal devices increases, if the network schedules SIB1 based on a longer period, it may limit access latency and the size of the reserved resource pool, negatively impacting performance. Therefore, when the load reaches high levels, the network can resume SIB1 transmission.

[0245] As an example, when the load of the first cell exceeds a first threshold, the first cell switches from an NES cell to a non-NES cell.

[0246] Furthermore, in multi-cell scenarios, the first terminal device also needs to determine whether its current cell is an NES cell (on-demand SIB1 cell) or an anchor cell. As mentioned earlier, an anchor cell can provide the first request and the configuration of the first SIB to terminal devices in adjacent NES cells. In order to access an NES cell, the first terminal device needs to detect at least one anchor cell to obtain the relevant configuration of the NES cell.

[0247] In some embodiments, the second cell may provide the anchor cell and non-anchor cell identifiers in the PBCH or MIB of the SSB. As mentioned above, the auxiliary information provided by the second cell may include the PCIs of multiple NES cells. After receiving this information, the first terminal device can clearly know whether the cell it is accessing is an anchor cell or a non-anchor cell. If the first terminal device is in an NES cell, the first terminal device may send a first request to the network device of the NES cell or the network device of the anchor cell to obtain the first SIB.

[0248] As an example, in a multi-cell scenario including a second cell, the first terminal device can receive third information sent by the second cell. The third information may include identification information of multiple cells. The first terminal device can perform cell access and cell reselection based on this identification information. Optionally, auxiliary information provided by the second cell may include the third information.

[0249] For example, when the first terminal device is in an idle or inactive state, it needs to re-enter the connection state.

[0250] For example, when the first terminal device is in a connected state, it may need to perform cell handover or cell reselection. For instance, if the first cell runs out of resources, cell reselection and handover will be triggered. The first terminal device can directly reselect to the second cell based on the configuration information of the second cell. Therefore, the resources of the first cell can also be used as a condition for cell reselection or handover.

[0251] As an example, when the first terminal device needs to re-enter the connected state, it can perform cell measurement and cell reselection based on the strength of the received signal. For instance, the first terminal device can select a cell to camp on based on the RSRP of multiple currently received cells (including anchor cells and non-anchor cells). Therefore, the first terminal device can access both NES and non-NES cells.

[0252] As an example, the first terminal device can choose which cell it will continue to camp on based on the results of cell measurement and reselection.

[0253] Optionally, when the first terminal device receives resource configuration requests from some of the multiple cells for the first request, if it chooses to camp on the current NES cell based on the cell measurement and reselection results, the first terminal device sends a first request for the first SIB to the NES cell or the anchor cell; if it chooses to camp on the anchor cell, the first terminal device sends a random access request to the anchor cell.

[0254] Optionally, if the first terminal device is in a connected state, the network equipment (e.g., a base station) in the cell can also send the resource configuration information of the first request via other signals to facilitate cell handover or reselection by the first terminal device. Other signals include, for example, the DCI on CORESET#0 carrying the resource configuration information of the first request for the target cell.

[0255] The above text combined Figures 1 to 8 The method embodiments of this application are described in detail below. Figures 9 to 13 The present application provides a detailed description of the apparatus embodiments. It should be understood that the descriptions of the apparatus embodiments correspond to the descriptions of the method embodiments; therefore, any parts not described in detail can be found in the foregoing method embodiments.

[0256] Figure 9 This is a schematic block diagram of a device for wireless communication according to an embodiment of this application. The device 900 can be any of the terminal devices described above. Figure 9 The apparatus 900 shown includes a transmitting unit 910 and a receiving unit 920.

[0257] The sending unit 910 can be used to send a first request, which is used to request the first SIB of the first cell; wherein, the first cell is the serving cell corresponding to the first terminal device, and the first SIB includes the SIB1 of the first cell.

[0258] The receiving unit 920 can be used to receive the first SIB and / or the configuration information of the first SIB.

[0259] Optionally, the first request may include one or more of the following: an uplink wake-up signal; demand information / demand signaling for requesting the first SIB; a first sequence for requesting the first SIB; and a preamble index associated with the first SIB.

[0260] Optionally, the device 900 further includes a first determining unit, which can be used to determine that the first cell is an NES cell; the sending unit 910 is also used to send a first request to the first cell.

[0261] Optionally, the first cell is one of a plurality of cells, and the plurality of cells also includes a second cell. The sending unit is further configured to send a first request to the second cell; the receiving unit is further configured to receive configuration information of the first SIB sent by the first cell and / or the second cell.

[0262] Optionally, the multiple cells include multiple NES cells and at least one non-NES cell, the second cell is a non-NES cell, the multiple NES cells include the first cell, the multiple NES cells correspond to the configuration information of multiple SIBs respectively, the configuration information of the multiple SIBs reuses the signaling sent by the second cell, or the configuration information of the multiple SIBs is carried on different downlink channels respectively.

[0263] Optionally, the device 900 further includes a processing unit, which can be used to select the configuration information of the first SIB for accessing the first cell based on the first information when the first terminal device receives the configuration information of the first SIB sent by the first cell and the configuration information of the first SIB sent by the second cell.

[0264] Optionally, the first information includes one or more of the following: the service level of the first terminal device; the service time of the first terminal device; and the measurement results of the first terminal device.

[0265] Optionally, the receiving unit 920 is further configured to receive third information sent by the second cell; wherein the third information includes identification information of multiple cells, and the identification information of multiple cells is used by the first terminal device for cell access and / or cell reselection.

[0266] Optionally, the sending unit 910 is further configured to send a first request to the second terminal device; the receiving unit is further configured to receive configuration information of the first SIB sent by the second terminal device; wherein the cell where the second terminal device is located is a non-NES cell.

[0267] Optionally, the sending unit 910 is also used to send configuration information of the first SIB to a third terminal device located in the first cell.

[0268] Optionally, the device 900 further includes a second determining unit, which can be used to determine whether the first cell is an NES cell based on the second information; the sending unit 910 is also used to send a first request when the first cell is an NES cell.

[0269] Optionally, the second information includes one or more of the following: whether the SSB sent by the first cell contains an identifier that the first cell is an NES cell; whether the MIB sent by the first cell contains an identifier that the first cell is an NES cell; whether the SSB or MIB sent by the first cell contains configuration information of the first SIB; and the load of the first cell.

[0270] Optionally, the first request may be sent via the uplink channel of the first terminal device, and / or via the resource indicated by the resource configuration information of the first request.

[0271] Optionally, the receiving unit 920 is further configured to receive a first SSB sent by the first cell; the sending unit 910 is further configured to: send a first request via PRACH when the first SSB does not contain resource configuration information; or, send a first request via PRACH or the resource indicated by the resource configuration information when the first SSB contains resource configuration information.

[0272] Optionally, when the first request is sent via a public resource of the random access procedure, the resource configuration information indicates one or more Resource Entities (ROs) for sending the first request.

[0273] Optionally, the first cell is one of multiple cells, which may also include a second cell. The resource configuration information is determined based on the auxiliary information sent by the first cell and / or the second cell.

[0274] Optionally, the resource configuration information includes first configuration information sent by the first cell and second configuration information sent by the second cell. The sending unit 910 is further configured to: send a first request according to the first configuration information when the first configuration information is different from the second configuration information; or, when the first configuration information is different from the second configuration information, select the configuration information to send the first request according to the first configuration information and the second configuration information based on the service type.

[0275] Optionally, the receiving unit 920 is further configured to monitor the first SIB and / or the configuration information of the first SIB within a first time window; wherein the time parameter of the first time window is determined according to the sending time of the first request.

[0276] Optionally, the first terminal device is in an idle state or an inactive state.

[0277] Figure 10 This is a schematic block diagram of another device for wireless communication according to an embodiment of this application. The device 1000 can be any of the first network devices corresponding to the first cell described above. Figure 10 The apparatus 1000 shown includes a receiving unit 1010 and a transmitting unit 1020.

[0278] The receiving unit 1010 can be used to receive a first request sent by the first terminal device, or to receive a second request sent by the second network device corresponding to the second cell. The first request is used to request the first SIB of the first cell, and the second request is determined according to the first request. The first cell is the serving cell corresponding to the first terminal device, and the first SIB includes the SIB1 of the first cell.

[0279] The sending unit 1020 can be used to send the first SIB and / or the configuration information of the first SIB to the first terminal device.

[0280] Optionally, the first request may include one or more of the following: an uplink wake-up signal; demand information / demand signaling for requesting the first SIB; a first sequence for requesting the first SIB; and a preamble index associated with the first SIB.

[0281] Optionally, whether the first cell is an NES cell is determined based on second information, which includes one or more of the following: whether the SSB sent by the first cell contains an identifier that the first cell is an NES cell; whether the MIB sent by the first cell contains an identifier that the first cell is an NES cell; whether the SSB or MIB sent by the first cell contains configuration information of the first SIB; and the load of the first cell.

[0282] Optionally, the first request may be sent via the uplink channel of the first terminal device, and / or via the resource indicated by the resource configuration information of the first request.

[0283] Optionally, the sending unit 1020 is further configured to send a first SSB; the receiving unit 1010 is further configured to receive a first request via the PRACH of the first terminal device when the first SSB does not contain resource configuration information of the first request; or, when the first SSB contains resource configuration information of the first request, receive the first request via the PRACH of the first terminal device or the resource indicated by the resource configuration information.

[0284] Optionally, when the first request is sent via a public resource of the random access procedure, the resource configuration information indicates one or more Resource Entities (ROs) for sending the first request.

[0285] Optionally, the device sending unit 1020 is further configured to send resource configuration information and / or configuration information of the first SIB to the second network device; wherein the resource configuration information and / or configuration information of the first SIB are used for second cell determination auxiliary information.

[0286] Optionally, the first cell is one of multiple cells, which include multiple NES cells and at least one non-NES cell. The second cell is a non-NES cell, which includes the first cell. The multiple NES cells correspond to the configuration information of multiple SIBs respectively. The configuration information of the multiple SIBs reuses the signaling sent by the second cell. Alternatively, the configuration information of the multiple SIBs is carried on different downlink channels.

[0287] Optionally, the sending unit 1020 is further configured to send the first SIB and / or the configuration information of the first SIB within a first time window; wherein the time parameter of the first time window is determined according to the sending time of the first request.

[0288] Optionally, the first terminal device is in an idle state or an inactive state.

[0289] Figure 11 This is a schematic block diagram of another device for wireless communication according to an embodiment of this application. The device 1100 can be any of the second network devices corresponding to the second cell described above. Figure 11 The device 1100 shown includes a receiving unit 1110 and a transmitting unit 1120.

[0290] The receiving unit 1110 can be used to receive a first request sent by the first terminal device, the first request being used to request the first SIB of the first cell; wherein, the first cell is the serving cell corresponding to the first terminal device, and the first SIB includes SIB1 of the first cell.

[0291] The sending unit 1120 can be used to send configuration information of the first SIB to the first terminal device.

[0292] Optionally, the first request may include one or more of the following: an uplink wake-up signal; demand information / demand signaling for requesting the first SIB; a first sequence for requesting the first SIB; and a preamble index associated with the first SIB.

[0293] Optionally, the sending unit 1120 is further configured to send a second request to the first network device corresponding to the first cell, wherein the second request is determined based on the first request.

[0294] Optionally, the receiving unit 1110 is further configured to receive resource configuration information and configuration information of multiple SIBs for multiple first requests sent by multiple network devices; wherein, the multiple cells corresponding to the multiple network devices are network energy-saving NES cells, the second cell is a non-NES cell, the multiple network devices include the first network device corresponding to the first cell, and the resource configuration information and configuration information of the multiple first requests are used by the second network device to determine the auxiliary information of the multiple network devices respectively.

[0295] Optionally, whether the first cell is an NES cell is determined based on second information, which includes one or more of the following: whether the SSB sent by the first cell contains an identifier that the first cell is an NES cell; whether the MIB sent by the first cell contains an identifier that the first cell is an NES cell; whether the SSB or MIB sent by the first cell contains configuration information of the first SIB; and the load of the first cell.

[0296] Optionally, the configuration information of multiple SIBs may be multiplexed using the signaling transmitted by the second cell, or the configuration information of multiple SIBs may be carried on different downlink channels.

[0297] Optionally, the first cell is one of multiple cells, the second cell is a non-NES cell, and the sending unit is also used to send third information to the first terminal device; wherein, the third information includes the identification information of multiple cells, and the identification information of multiple cells is used by the first terminal device to perform cell access and / or cell reselection.

[0298] Optionally, the first request may be sent via the uplink channel of the first terminal device, and / or via the resource indicated by the resource configuration information of the first request.

[0299] Optionally, when the first request is sent via a public resource of the random access procedure, the resource configuration information indicates one or more Resource Entities (ROs) for sending the first request.

[0300] Optionally, the resource configuration information is determined based on auxiliary information sent by the first cell and / or the second cell.

[0301] Optionally, the sending unit is further configured to send configuration information of the first SIB within a first time window; wherein the time parameter of the first time window is determined according to the sending time of the first request.

[0302] Optionally, the first terminal device is in an idle state or an inactive state.

[0303] Figure 12 This is a schematic block diagram of another device for wireless communication according to an embodiment of this application. The device 1200 can be any of the second terminal devices described above. Figure 12 The apparatus 1200 shown includes a receiving unit 1210 and a transmitting unit 1220.

[0304] The receiving unit 1210 can be used to receive a first request sent by the first terminal device, the first request being used to request the first SIB of the first cell; wherein, the first cell is the serving cell corresponding to the first terminal device, and the first SIB includes SIB1 of the first cell.

[0305] The sending unit 1220 can be used to send configuration information of the first SIB to the first terminal device.

[0306] Optionally, the first request may include one or more of the following methods: requesting demand information / demand signaling for the first SIB; or requesting a first sequence for the first SIB.

[0307] Optionally, the first cell is an NES cell, and the cell where the second terminal device is located is a non-NES cell.

[0308] Optionally, whether the first cell is an NES cell is determined based on second information, which includes one or more of the following: whether the SSB sent by the first cell contains an identifier that the first cell is an NES cell; whether the MIB sent by the first cell contains an identifier that the first cell is an NES cell; whether the SSB or MIB sent by the first cell contains configuration information of the first SIB; and the load of the first cell.

[0309] Optionally, the sending unit is further configured to send configuration information of the first SIB within a first time window; wherein the time parameter of the first time window is determined according to the sending time of the first request.

[0310] Optionally, the first terminal device is in an idle state or an inactive state.

[0311] Figure 13 The diagram shown is a structural schematic of a communication device according to an embodiment of this application. Figure 13 The dashed lines indicate that the unit or module is optional. The device 1300 can be used to implement the methods described in the above method embodiments. The device 1300 can be a chip, a terminal device, or a network device.

[0312] Apparatus 1300 may include one or more processors 1310. The processor 1310 may support apparatus 1300 in implementing the methods described in the preceding method embodiments. The processor 1310 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.

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

[0314] The device 1300 may also include a transceiver 1330. The processor 1310 can communicate with other devices or chips via the transceiver 1330. For example, the processor 1310 can send and receive data with other devices or chips via the transceiver 1330.

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

[0316] 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 medium can 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.

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

[0318] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions. When 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 via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means.

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

[0320] In this application, the terms "system" and "network" are 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.

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

[0322] In the embodiments of this application, the term "correspondence" may 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.

[0323] In the embodiments of this application, "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 terminal devices and network devices). This application does not limit the specific implementation method. For example, predefined can refer to what is defined in the protocol.

[0324] In the embodiments of this application, the term "protocol" may refer to standard protocols in the field of communications, such as LTE protocols, NR protocols, and related protocols applied in future communication systems. This application does not limit the scope of these protocols.

[0325] In the embodiments of this application, determining B based on A does not mean determining B solely based on A; B can also be determined based on A and / or other information.

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

[0327] In the embodiments of this application, the order of the above-mentioned process numbers 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.

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

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

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

[0331] 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, characterized in that, include: The first terminal device receives resource configuration information for the first request, the resource configuration information comes from the second cell, and the resource configuration information is used to indicate the Physical Random Access Channel (PRACH) configured on the first cell for the first request; The first terminal device sends a first request to the first cell via the PRACH, the first request being used to request the system information block SIB1 of the first cell; The first terminal device receives SIB1 and / or the configuration information of SIB1; Wherein, the first cell is the serving cell corresponding to the first terminal device, the first cell is a network energy-saving NES cell, and the second cell is a non-NES cell; the PRACH is a dedicated PRACH designed for the first request, and the PRACH does not perform uplink synchronization; the first request includes a preamble index related to the SIB1, and the preamble index is used to instruct the first terminal device to request the first network device corresponding to the first cell to send the SIB1.

2. The method according to claim 1, characterized in that, The first request also includes one or more of the following methods: Uplink wake-up signal; Used to request the demand information / demand signaling of SIB1; Used to request the first sequence of SIB1.

3. The method according to claim 1 or 2, characterized in that, The method further includes: The first terminal device determines that the first cell is an NES cell; The first terminal device sends the first request to the first cell.

4. The method according to claim 1 or 2, characterized in that, The first cell is one of a plurality of cells, the plurality of cells also including the second cell, and the method further includes: The first terminal device also sends the first request to the second cell; The first terminal device receives the configuration information of SIB1 sent by the first cell and / or the second cell.

5. The method according to claim 4, characterized in that, The plurality of cells include a plurality of NES cells and at least one non-NES cell. The plurality of NES cells correspond to the configuration information of a plurality of SIBs. The configuration information of the plurality of SIBs reuses the signaling sent by the second cell, or the configuration information of the plurality of SIBs is carried on different downlink channels.

6. The method according to claim 4, characterized in that, The method further includes: When the first terminal device receives the SIB1 configuration information sent by the first cell and the SIB1 configuration information sent by the second cell, the first terminal device selects the SIB1 configuration information for accessing the first cell based on the first information.

7. The method according to claim 6, characterized in that, The first information includes one or more of the following: The service level of the first terminal device; The service time of the first terminal device; and The results of the measurement performed by the first terminal device.

8. The method according to claim 4, characterized in that, The method further includes: The first terminal device receives the third information sent by the second cell; The third information includes the identification information of the plurality of cells, which is used by the first terminal device for cell access and / or cell reselection.

9. The method according to claim 1 or 2, characterized in that, The method further includes: The first terminal device determines whether the first cell is an NES cell based on the second information; When the first cell is an NES cell, the first terminal device sends the first request.

10. The method according to claim 9, characterized in that, The second information includes one or more of the following: Does the synchronization signal block SSB sent by the first cell contain an identifier that the first cell is an NES cell? Does the main information block (MIB) sent by the first cell contain an identifier that the first cell is an NES cell? Does the SSB or MIB sent by the first cell contain the configuration information of SIB1? The load of the first cell.

11. The method according to claim 1 or 2, characterized in that, The method further includes: The first terminal device receives the first SSB sent by the first cell; When the first SSB does not contain the resource configuration information, the first terminal device sends the first request via the Physical Random Access Channel (PRACH); or... When the first SSB contains the resource configuration information, the first terminal device sends the first request via PRACH or the resource indicated by the resource configuration information.

12. The method according to claim 1 or 2, characterized in that, The first cell is one of a plurality of cells, which also includes the second cell. The resource configuration information is determined based on auxiliary information sent by the first cell and / or the second cell.

13. The method according to claim 12, characterized in that, The resource configuration information also includes first configuration information sent by the first cell and second configuration information sent by the second cell, and the method further includes: When the first configuration information differs from the second configuration information, the first terminal device sends the first request based on the first configuration information; or... When the first configuration information is different from the second configuration information, the first terminal device selects the configuration information for sending the first request from the first configuration information and the second configuration information according to the service type.

14. The method according to claim 1 or 2, characterized in that, The method further includes: The first terminal device monitors SIB1 and / or the configuration information of SIB1 within a first time window; The time parameter of the first time window is determined based on the sending time of the first request.

15. The method according to claim 1 or 2, characterized in that, The first terminal device is in an idle or inactive state.

16. A method for wireless communication, characterized in that, include: The first network device corresponding to the first cell receives a first request sent by the first terminal device, or receives a second request sent by the second network device corresponding to the second cell. The first request is used to request the system information block SIB1 of the first cell, and the second request is determined according to the first request. The first network device sends the SIB1 and / or the configuration information of the SIB1 to the first terminal device; Wherein, the first cell is the serving cell corresponding to the first terminal device, the first request is sent through the Physical Random Access Channel (PRACH) configured on the first cell, the PRACH is indicated according to the resource configuration information of the first request from the second cell, the first cell is a network energy-saving NES cell, and the second cell is a non-NES cell; the PRACH is a dedicated PRACH designed for the first request, and the PRACH does not perform uplink synchronization; the first request includes a preamble index related to the SIB1, and the preamble index is used to instruct the first terminal device to request the first network device to send the SIB1.

17. The method according to claim 16, characterized in that, The first request also includes one or more of the following methods: Uplink wake-up signal; Used to request the demand information / demand signaling of SIB1; Used to request the first sequence of SIB1.

18. The method according to claim 16 or 17, characterized in that, Whether the first cell is an NES cell is determined based on second information, which includes one or more of the following: Does the synchronization signal block SSB sent by the first cell contain an identifier that the first cell is an NES cell? Does the main information block (MIB) sent by the first cell contain an identifier that the first cell is an NES cell? Does the SSB or MIB sent by the first cell contain the configuration information of SIB1? The load of the first cell.

19. The method according to claim 16 or 17, characterized in that, The method further includes: The first network device sends the first SSB; When the first SSB does not contain the resource configuration information requested in the first request, the first network device receives the first request through the physical random access channel (PRACH) of the first terminal device; or... When the first SSB contains the resource configuration information of the first request, the first network device receives the first request through the PRACH of the first terminal device or the resource indicated by the resource configuration information.

20. The method according to claim 16 or 17, characterized in that, The method further includes: The first network device sends the resource configuration information and / or the SIB1 configuration information to the second network device; The resource configuration information and / or the configuration information of SIB1 are used for the second cell determination auxiliary information.

21. The method according to claim 16 or 17, characterized in that, The first cell is one of a plurality of cells, which include a plurality of NES cells and at least one non-NES cell. The plurality of NES cells correspond to the configuration information of a plurality of SIBs. The configuration information of the plurality of SIBs reuses the signaling sent by the second cell, or the configuration information of the plurality of SIBs is carried on different downlink channels.

22. The method according to claim 16 or 17, characterized in that, The method further includes: The first network device sends SIB1 and / or the configuration information of SIB1 within a first time window; The time parameter of the first time window is determined based on the sending time of the first request.

23. The method according to claim 16 or 17, characterized in that, The first terminal device is in an idle or inactive state.

24. A method for wireless communication, characterized in that, include: The second network device corresponding to the second cell sends resource configuration information for the first request to the first terminal device. The resource configuration information is used to indicate the physical random access channel (PRACH) configured on the first cell for the first request. The second network device receives a first request sent by the first terminal device, the first request being used to request the system information block SIB1 of the first cell; The second network device sends the configuration information of SIB1 to the first terminal device; Wherein, the first cell is the serving cell corresponding to the first terminal device, the first request is sent through the PRACH, the first cell is a network energy-saving NES cell, and the second cell is a non-NES cell; the PRACH is a dedicated PRACH designed for the first request, and the PRACH does not perform uplink synchronization; the first request includes a preamble index related to the SIB1, and the preamble index is used to instruct the first terminal device to request the first network device corresponding to the first cell to send the SIB1.

25. The method according to claim 24, characterized in that, The first request also includes one or more of the following methods: Uplink wake-up signal; Used to request the demand information / demand signaling of SIB1; Used to request the first sequence of SIB1.

26. The method according to claim 24 or 25, characterized in that, The method further includes: The second network device sends a second request to the first network device, wherein the second request is determined based on the first request.

27. The method according to claim 24 or 25, characterized in that, The method further includes: The second network device receives resource configuration information and configuration information of multiple SIBs from multiple first requests sent by multiple network devices; Wherein, the multiple cells corresponding to the multiple network devices are NES cells, the multiple network devices include the first network device, and the resource configuration information of the multiple first requests and / or the configuration information of the multiple SIBs are used by the second network device to determine the auxiliary information of the multiple network devices respectively.

28. The method according to claim 27, characterized in that, Whether the first cell is an NES cell is determined based on second information, which includes one or more of the following: Does the synchronization signal block SSB sent by the first cell contain an identifier that the first cell is an NES cell? Does the main information block (MIB) sent by the first cell contain an identifier that the first cell is an NES cell? Does the SSB or MIB sent by the first cell contain the configuration information of SIB1? The load of the first cell.

29. The method according to claim 27, characterized in that, The configuration information of the multiple SIBs may reuse the signaling sent by the second cell, or the configuration information of the multiple SIBs may be carried on different downlink channels.

30. The method according to claim 24 or 25, characterized in that, The first cell is one of multiple cells, and the method further includes: The second network device sends third information to the first terminal device; The third information includes the identification information of the plurality of cells, which is used by the first terminal device for cell access and / or cell reselection.

31. The method according to claim 24 or 25, characterized in that, The resource configuration information is determined based on the auxiliary information sent by the first cell and / or the second cell.

32. The method according to claim 24 or 25, characterized in that, The method further includes: The second network device sends the configuration information of SIB1 within the first time window; The time parameter of the first time window is determined based on the sending time of the first request.

33. The method according to claim 24 or 25, characterized in that, The first terminal device is in an idle or inactive state.

34. A device for wireless communication, characterized in that, The device is a first terminal device, and the device includes: A receiving unit is configured to receive resource configuration information for a first request, the resource configuration information being from a second cell, and the resource configuration information being used to indicate the Physical Random Access Channel (PRACH) configured on a first cell for the first request. The transmitting unit is configured to send a first request to the first cell via the PRACH, wherein the first request is used to request the system information block SIB1 of the first cell. The receiving unit is also configured to receive SIB1 and / or the configuration information of SIB1; Wherein, the first cell is the serving cell corresponding to the first terminal device, the first cell is a network energy-saving NES cell, and the second cell is a non-NES cell; the PRACH is a dedicated PRACH designed for the first request, and the PRACH does not perform uplink synchronization; the first request includes a preamble index related to the SIB1, and the preamble index is used to instruct the first terminal device to request the first network device corresponding to the first cell to send the SIB1.

35. The apparatus according to claim 34, characterized in that, The first request also includes one or more of the following methods: Uplink wake-up signal; Used to request the demand information / demand signaling of SIB1; Used to request the first sequence of SIB1.

36. The apparatus according to claim 34 or 35, characterized in that, The device further includes: The first determining unit is used to determine that the first cell is an NES cell; The sending unit is also used to send the first request to the first cell.

37. The apparatus according to claim 34 or 35, characterized in that, The first cell is one of a plurality of cells, the plurality of cells including the second cell, the sending unit is further configured to send the first request to the second cell; the receiving unit is further configured to receive the configuration information of SIB1 sent by the first cell and / or the second cell.

38. The apparatus according to claim 37, characterized in that, The plurality of cells include a plurality of NES cells and at least one non-NES cell. The plurality of NES cells correspond to the configuration information of a plurality of SIBs. The configuration information of the plurality of SIBs reuses the signaling sent by the second cell, or the configuration information of the plurality of SIBs is carried on different downlink channels.

39. The apparatus according to claim 37, characterized in that, The device further includes: The processing unit is configured to, when the first terminal device receives the configuration information of SIB1 sent by the first cell and the configuration information of SIB1 sent by the second cell, select the configuration information of SIB1 for accessing the first cell based on the first information.

40. The apparatus according to claim 39, characterized in that, The first information includes one or more of the following: The service level of the first terminal device; The service time of the first terminal device; and The results of the measurement performed by the first terminal device.

41. The apparatus according to claim 37, characterized in that, The receiving unit is further configured to receive third information sent by the second cell; wherein the third information includes the identification information of the plurality of cells, and the identification information of the plurality of cells is used by the first terminal device to perform cell access and / or cell reselection.

42. The apparatus according to claim 34 or 35, characterized in that, The device further includes: The second determining unit is used to determine whether the first cell is an NES cell based on the second information; The sending unit is further configured to send the first request when the first cell is an NES cell.

43. The apparatus according to claim 42, characterized in that, The second information includes one or more of the following: Does the synchronization signal block SSB sent by the first cell contain an identifier that the first cell is an NES cell? Does the main information block (MIB) sent by the first cell contain an identifier that the first cell is an NES cell? Does the SSB or MIB sent by the first cell contain the configuration information of SIB1? The load of the first cell.

44. The apparatus according to claim 34 or 35, characterized in that, The receiving unit is further configured to receive the first SSB transmitted by the first cell; the transmitting unit is further configured to: When the first SSB does not contain the resource configuration information, the first request is sent via the Physical Random Access Channel (PRACH); or... When the first SSB contains the resource configuration information, the first request is sent via PRACH or the resource indicated by the resource configuration information.

45. The apparatus according to claim 34 or 35, characterized in that, The first cell is one of a plurality of cells, which also includes a second cell. The resource configuration information is determined based on auxiliary information sent by the first cell and / or the second cell.

46. ​​The apparatus according to claim 45, characterized in that, The resource configuration information includes first configuration information sent by the first cell and second configuration information sent by the second cell. The sending unit is further configured to: When the first configuration information differs from the second configuration information, the first request is sent according to the first configuration information; or... When the first configuration information is different from the second configuration information, the configuration information for sending the first request is selected from the first configuration information and the second configuration information according to the service type.

47. The apparatus according to claim 34 or 35, characterized in that, The receiving unit is further configured to monitor SIB1 and / or the configuration information of SIB1 within a first time window; wherein the time parameter of the first time window is determined according to the sending time of the first request.

48. The apparatus according to claim 34 or 35, characterized in that, The first terminal device is in an idle or inactive state.

49. A device for wireless communication, characterized in that, The device is a first network device corresponding to the first cell, and the device includes: The receiving unit is configured to receive a first request sent by a first terminal device, or to receive a second request sent by a second network device corresponding to a second cell, wherein the first request is used to request the system information block SIB1 of the first cell, and the second request is determined according to the first request. A sending unit is configured to send the SIB1 and / or the configuration information of the SIB1 to the first terminal device; Wherein, the first cell is the serving cell corresponding to the first terminal device, the first request is sent through the Physical Random Access Channel (PRACH) configured on the first cell, the PRACH is indicated according to the resource configuration information of the first request from the second cell, the first cell is a network energy-saving NES cell, and the second cell is a non-NES cell; the PRACH is a dedicated PRACH designed for the first request, and the PRACH does not perform uplink synchronization; the first request includes a preamble index related to the SIB1, and the preamble index is used to instruct the first terminal device to request the first network device to send the SIB1.

50. The apparatus according to claim 49, characterized in that, The first request also includes one or more of the following methods: Uplink wake-up signal; Used to request the demand information / demand signaling of SIB1; Used to request the first sequence of SIB1.

51. The apparatus according to claim 49 or 50, characterized in that, Whether the first cell is an NES cell is determined based on second information, which includes one or more of the following: Does the synchronization signal block SSB sent by the first cell contain an identifier that the first cell is an NES cell? Does the main information block (MIB) sent by the first cell contain an identifier that the first cell is an NES cell? Does the SSB or MIB sent by the first cell contain the configuration information of SIB1? The load of the first cell.

52. The apparatus according to claim 49 or 50, characterized in that, The transmitting unit is also used to transmit a first SSB; The receiving unit is also used for: When the first SSB does not contain the resource configuration information requested in the first request, the first request is received via the Physical Random Access Channel (PRACH) of the first terminal device; or... When the first SSB contains the resource configuration information of the first request, the first request is received through the PRACH of the first terminal device or the resource indicated by the resource configuration information.

53. The apparatus according to claim 49 or 50, characterized in that, The sending unit is further configured to send the resource configuration information and / or the configuration information of SIB1 to the second network device; wherein the resource configuration information and / or the configuration information of SIB1 are used for the second cell determination auxiliary information.

54. The apparatus according to claim 49 or 50, characterized in that, The first cell is one of a plurality of cells, which include a plurality of NES cells and at least one non-NES cell. The plurality of NES cells correspond to the configuration information of a plurality of SIBs. The configuration information of the plurality of SIBs reuses the signaling sent by the second cell, or the configuration information of the plurality of SIBs is carried on different downlink channels.

55. The apparatus according to claim 49 or 50, characterized in that, The sending unit is further configured to send SIB1 and / or the configuration information of SIB1 within a first time window; wherein the time parameter of the first time window is determined according to the sending time of the first request.

56. The apparatus according to claim 49 or 50, characterized in that, The first terminal device is in an idle or inactive state.

57. A device for wireless communication, characterized in that, The device is a second network device corresponding to the second cell, and the device includes: The sending unit is configured to send resource configuration information for a first request to a first terminal device, wherein the resource configuration information is used to indicate the physical random access channel (PRACH) configured on the first cell for the first request; The receiving unit is configured to receive a first request sent by the first terminal device, wherein the first request is used to request the system information block SIB1 of the first cell; The sending unit is also used to send the configuration information of SIB1 to the first terminal device; Wherein, the first cell is the serving cell corresponding to the first terminal device, the first request is sent through the PRACH, the first cell is a network energy-saving NES cell, and the second cell is a non-NES cell; the PRACH is a dedicated PRACH designed for the first request, and the PRACH does not perform uplink synchronization; the first request includes a preamble index related to the SIB1, and the preamble index is used to instruct the first terminal device to request the first network device corresponding to the first cell to send the SIB1.

58. The apparatus according to claim 57, characterized in that, The first request also includes one or more of the following methods: Uplink wake-up signal; Used to request the demand information / demand signaling of SIB1; Used to request the first sequence of SIB1.

59. The apparatus according to claim 57 or 58, characterized in that, The sending unit is further configured to send a second request to the first network device, wherein the second request is determined based on the first request.

60. The apparatus according to claim 57 or 58, characterized in that, The receiving unit is further configured to receive resource configuration information and configuration information of multiple SIBs for multiple first requests sent by multiple network devices; wherein, the multiple cells corresponding to the multiple network devices are NES cells, the multiple network devices include the first network device, and the resource configuration information and / or the configuration information of the multiple first requests are used by the second network device to determine the auxiliary information of the multiple network devices respectively.

61. The apparatus according to claim 60, characterized in that, Whether the first cell is an NES cell is determined based on second information, which includes one or more of the following: Does the synchronization signal block SSB sent by the first cell contain an identifier that the first cell is an NES cell? Does the main information block (MIB) sent by the first cell contain an identifier that the first cell is an NES cell? Does the SSB or MIB sent by the first cell contain the configuration information of SIB1? The load of the first cell.

62. The apparatus according to claim 60, characterized in that, The configuration information of the multiple SIBs may reuse the signaling sent by the second cell, or the configuration information of the multiple SIBs may be carried on different downlink channels.

63. The apparatus according to claim 57 or 58, characterized in that, The first cell is one of a plurality of cells, and the sending unit is further configured to send third information to the first terminal device; wherein, the third information includes the identification information of the plurality of cells, and the identification information of the plurality of cells is used by the first terminal device to perform cell access and / or cell reselection.

64. The apparatus according to claim 57 or 58, characterized in that, The resource configuration information is determined based on the auxiliary information sent by the first cell and / or the second cell.

65. The apparatus according to claim 57 or 58, characterized in that, The sending unit is also used to send the configuration information of SIB1 within a first time window; wherein the time parameter of the first time window is determined according to the sending time of the first request.

66. The apparatus according to claim 57 or 58, characterized in that, The first terminal device is in an idle or inactive state.

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.

Images