Wireless communication method, terminal equipment and network equipment

Abstract

The invention provides a wireless communication method, terminal equipment and network equipment. The method comprises the following steps: the terminal equipment receives first configuration information, wherein the first configuration information is related to a trigger request of a target SIB1; the terminal equipment sends a first request to network equipment, wherein the first request is used for requesting the target SIB1; the terminal equipment receives the target SIB1 sent by the network equipment; wherein the first configuration information is used for indicating a first lead code related to the first request and / or a transmission resource of the target SIB1.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and more specifically, to a wireless communication method, terminal equipment and network equipment. Background Art

[0002] In some communication systems, network devices periodically send system information blocks (SIBs) 1, which carry key information required for terminal devices to access the cell. In order to save energy, network devices can also trigger SIB1 transmission based on requests from terminal devices. However, how terminal devices send requests and how they receive SIB1 are issues that need to be resolved. Summary of the invention

[0003] The present application provides a wireless communication method, terminal device and network device. The following introduces various aspects involved in the embodiments of the present application.

[0004] In a first aspect, a method for wireless communication is provided, including: a terminal device receives first configuration information, wherein the first configuration information is related to a trigger request of a target SIB1; the terminal device sends a first request to a network device, wherein the first request is used to request the target SIB1; the terminal device receives the target SIB1 sent by the network device; wherein the first configuration information is used to indicate a first preamble code related to the first request and / or a transmission resource of the target SIB1.

[0005] In a second aspect, a method for wireless communication is provided, including: a network device sends first configuration information, wherein the first configuration information is related to a trigger request of a target SIB1; the network device receives a first request sent by a terminal device, wherein the first request is used to request the target SIB1; the network device sends the target SIB1 to the terminal device; wherein the first configuration information is used to indicate a first preamble code related to the first request and / or a transmission resource of the target SIB1.

[0006] According to a third aspect, a terminal device is provided, comprising: a transceiver unit for receiving first configuration information, wherein the first configuration information is related to a trigger request of a target SIB1; the transceiver unit is also used to send a first request to a network device, wherein the first request is used to request the target SIB1; the transceiver unit is also used to receive the target SIB1 sent by the network device; wherein the first configuration information is used to indicate a first preamble code related to the first request and / or a transmission resource of the target SIB1.

[0007] In a fourth aspect, a network device is provided, including: a transceiver unit, used to send first configuration information, the first configuration information is related to a trigger request of a target SIB1; the transceiver unit is also used to receive a first request sent by a terminal device, the first request is used to request the target SIB1; the transceiver unit is also used to send the target SIB1 to the terminal device; wherein the first configuration information is used to indicate a first preamble code related to the first request and / or a transmission resource of the target SIB1.

[0008] In a fifth aspect, a communication device is provided, comprising a memory and a processor, wherein the memory is used to store a program, and the processor is used to call the program in the memory to execute the method described in the first aspect or the second aspect.

[0009] In a sixth aspect, a device is provided, comprising a processor, configured to call a program from a memory to execute the method described in the first aspect or the second aspect.

[0010] In a seventh aspect, a chip is provided, comprising a processor for calling a program from a memory so that a device equipped with the chip executes the method described in the first aspect or the second aspect.

[0011] According to an eighth aspect, a computer-readable storage medium is provided, on which a program is stored, wherein the program enables a computer to execute the method as described in the first aspect or the second aspect.

[0012] According to a ninth aspect, a computer program product is provided, comprising a program, wherein the program enables a computer to execute the method described in the first aspect or the second aspect.

[0013] In a tenth aspect, a computer program is provided, wherein the computer program enables a computer to execute the method as described in the first aspect or the second aspect.

[0014] The terminal device in the embodiment of the present application can determine the first preamble code when the first request is sent based on random access according to the first configuration information, and can also determine the transmission resource of the target SIB1 according to the first configuration information. The target SIB1 is the SIB1 sent on demand. It can be seen that through the setting of the first configuration information, the terminal device can more conveniently request the target SIB1 from the network device and receive the target SIB1 in time, thereby improving resource utilization while achieving network energy saving. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figure 1 It is a wireless communication system applied in the embodiments of the present application.

[0016] Figure 2 It is a schematic diagram of a wireless communication scenario applied in an embodiment of the present application.

[0017] Figure 3 It is a flowchart of a wireless communication method provided in an embodiment of the present application.

[0018] Figure 4 yes Figure 3 A schematic diagram of a possible implementation of the method shown.

[0019] Figure 5 yes Figure 3 A possible flow diagram of the method shown.

[0020] Figure 6 It is a structural diagram of a terminal device provided in an embodiment of the present application.

[0021] Figure 7 It is a structural diagram of a network device provided in an embodiment of the present application.

[0022] Figure 8 It is a structural diagram of a wireless communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0023] The technical solutions in the embodiments of the present application are described below in conjunction with the accompanying drawings.

[0024] Figure 1 FIG. 1 is a schematic diagram of the architecture of a wireless communication system 100 used in an embodiment of the present application. Figure 1 As shown, the wireless communication system 100 may include a network device 110 and a terminal device 120. The network device 110 may be a device that communicates with the terminal device 120. The network device 110 may provide communication coverage for a specific geographical area and may communicate with terminal devices located in the coverage area.

[0025] Figure 1 One network device and two terminal devices are shown exemplarily. Optionally, the wireless communication system 100 may include multiple network devices and each network device may include another number of terminal devices within its coverage area, which is not limited.

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

[0027] It should be understood that the embodiments of the present application can be applied to various communication systems. For example, the embodiments of the present application can be applied to global system of mobile communication (GSM) system, code division multiple access (CDMA) system, wideband code division multiple access (WCDMA) system, general packet radio service (GPRS) system, long term evolution (LTE) system, advanced long term evolution (LTE-A) system, new radio (NR) system, NR system evolution system, LTE-based access to unlicensed spectrum (LTE-U) system, NR-based access to unlicensed spectrum (NR-U) system, universal mobile telecommunication system (UMTS), wireless local area network (WLAN) system, wireless fidelity (WiFi) system, fifth generation communication (5G) system. The embodiments of the present application can also be applied to other communication systems, such as the sixth-generation (6G) mobile communication system, or future communication systems such as satellite communication systems.

[0028] Traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, communication systems can not only support traditional cellular communications, but also support one or more other types of communications. For example, a communication system can support one or more of the following communications: 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, etc. The embodiments of the present application can also be applied to communication systems that support the above communication methods.

[0029] The communication system in the embodiment of the present application can be applied to a carrier aggregation (CA) scenario, a dual connectivity (DC) scenario, or a standalone (SA) networking scenario.

[0030] The communication system in the embodiment of the present application can be applied to an unlicensed spectrum. The unlicensed spectrum can also be considered as a shared spectrum. Alternatively, the communication system in the embodiment of the present application can also be applied to an authorized spectrum. The authorized spectrum can also be considered as a dedicated spectrum.

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

[0032] The terminal device in the embodiments of the present 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.

[0033] In some embodiments, the terminal device in the embodiment of the present application may be a device that provides voice and / or data connectivity to a user, and may be used to connect people, objects, and machines, such as a handheld device with wireless connection function, a vehicle-mounted device, etc. The terminal device in the embodiment of the present application may be a mobile phone, a tablet computer (Pad), a laptop computer, a PDA, a mobile internet device (MID), a wearable device, a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home, etc. Optionally, the UE may be used to act as a base station. For example, the UE may act as a scheduling entity that provides sidelink signals between UEs in V2X or D2D, etc. For example, a cellular phone and a car communicate with each other using sidelink signals. Cellular phones and smart home devices communicate with each other without relaying the communication signal through a base station.

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

[0035] The network device in the embodiment of the present application may be a device for communicating with a terminal device, and the network device may also be referred to as an access network device or a radio access network device. The network device may be, for example, a base station. The network device in the embodiment of the present application may refer to a radio access network (RAN) node (or device) that connects a terminal device to a wireless network. A base station may broadly cover various names as follows, or be replaced with the following names, such as: NodeB, evolved NodeB (eNB), next generation NodeB (gNB), relay station, access point, transmission point (TRP), transmission point (TP), master station (MeNB), secondary station (SeNB), multi-standard radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, base band 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 may be a macro base station, a micro base station, a relay node, a donor node, or the like, or a combination thereof. The base station may also refer to a communication module, modem or chip used to be set in the aforementioned equipment or device. The base station may also be a mobile switching center and a device that performs the base station function in D2D, V2X, and M2M communications, a network-side device in a 6G network, and a device that performs the base station function in a future communication system. The base station may support networks with the same or different access technologies. The embodiments of the present application do not limit the specific technology and specific device form used by the network equipment.

[0036] 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 based on the location of the mobile base station. In other examples, a helicopter or drone can be configured to act as a device that communicates with another base station.

[0037] In some deployments, the network device in the embodiments of the present application may refer to a CU or a DU, or the network device includes a CU and a DU. The gNB may also include an AAU.

[0038] The network equipment and terminal equipment can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on the water surface; they can also be deployed on aircraft, balloons and satellites in the air. The embodiments of the present application do not limit the scenarios in which the network equipment and terminal equipment are located.

[0039] It should be understood that all or part of the functions of the communication device in the present application may also be implemented by software functions running on hardware, or by virtualization functions instantiated on a platform (eg, a cloud platform).

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

[0041] It should be understood that the device with communication function in the network / system in the embodiment of the present application can be referred to as a communication device. Figure 1 Taking the wireless communication system 100 shown as an example, the communication equipment may include a network device 110 and a terminal device 120 with communication functions, and may also include other devices in the wireless communication system 100, such as a network controller, a mobile management entity and other network entities, which is not limited in the embodiments of the present application.

[0042] For ease of understanding, some relevant technical knowledge involved in the embodiments of the present application is first introduced. The following related technologies can be arbitrarily combined with the technical solutions of the embodiments of the present application as optional solutions, and they all belong to the protection scope of the embodiments of the present application. The embodiments of the present application include at least part of the following contents.

[0043] With the development of mobile communication technology, the new generation of wireless evolution systems (for example, 5G systems) use a variety of technologies to improve data transmission rates to meet the needs of different scenarios. Various technologies such as massive multiple-input multiple-output (MIMO) technology, non-orthogonal multiple access technology, simultaneous full-duplex communication technology, new modulation technology, new coding technology, and high-order modulation technology.

[0044] As an example, the peak rate can reach the Gbit / s standard to meet the transmission needs of large amounts of data such as high-definition video and virtual reality.

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

[0046] As an example, ultra-large network capacity can provide connectivity for hundreds of billions of devices, thus meeting the communication needs of the Internet of Things.

[0047] As an example, the spectrum efficiency of the NR system is more than 10 times higher than that of the LTE system. Based on continuous wide-area coverage and high mobility, the user experience rate can reach 100Mbit / s. It can be seen that the traffic density and connection density have been greatly improved.

[0048] In addition, the improvement of system coordination and intelligence has further improved the flexibility of the network. System coordination can be manifested as multi-user, multi-point, multi-antenna, and multi-input coordinated networking. Based on coordination and intelligence, networks can be flexibly and automatically adjusted.

[0049] However, in a communication system, the power consumption of network equipment (for example, base station equipment) is usually high. In order to save the power consumption of the base station equipment, it is necessary to optimize the system message. For ease of understanding, the following is an example of NR system message.

[0050] NR system messages can be divided into master information block (MIB) messages and some SIB messages. MIB messages are usually sent on the broadcast channel (BCH). The MIB transmission period is 80ms. MIB can be repeatedly transmitted within an 80ms period. In addition, the MIB message also includes the parameters required by the terminal device to obtain the SIB1 message from the cell.

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

[0052] In the embodiment of the present application, SSB may also represent a synchronization signal / physical broadcast channel block (synchronizationsignal and PBCH block).

[0053] SIB1 can carry key information required for terminal devices 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 mapping of other SIBs to system information (SI) messages, periodicity, SI window size, etc. SIB1 can also indicate whether one or more SIBs are provided only on demand, in which case SIB1 can also provide the physical random access channel (PRACH) configuration required by the terminal device to request the SI required by the terminal device. SIB1 also contains radio resource configuration information common to all terminal devices and cell barring information applied to unified access control.

[0054] When SIB1 includes relevant information about other SIBs, other SIB messages may be provided through periodic broadcast or on-demand. If other SIBs are provided on-demand, SIB1 may include information for terminal devices to perform system information (SI) requests.

[0055] 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 SI window). Only SIBs with the same period can be mapped to the same SI message. Each SI message is sent within a periodic 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 the SI window.

[0056] As mentioned above, in a traditional communication system, a network device (e.g., gNB) may periodically send SIB1 for initial access and schedule other SIBs for terminal devices in idle / inactive mode. The network device will always transmit even if there is no demand from the terminal device or no terminal device resides on the cell. In these scenarios, the periodic transmission of SIB1 by the network device may result in a large waste of energy. In other words, permanent SIB1 transmission will waste energy because continuous transmission of SIB1 may not be necessary in some cases.

[0057] In order to save power consumption of network-side equipment, network energy saving (NES) technology is introduced. NES technology can be applied to a variety of scenarios so that operators have the opportunity to reduce the operating costs of any potential deployment. Various scenarios include urban micro-scenarios, macro-scenarios, indoor hotspots (InH) scenarios, etc. For urban micro-scenarios and InH scenarios, the number of terminal devices residing on the cell may change significantly over time. In addition, once the overall traffic load is not so high, the network may decide to shut down some cells. Specifically, the access network equipment can shut down SIB1 transmission on the cell while maintaining basic operations on adjacent cells.

[0058] As an example, network devices can send SIB1 on demand to solve the energy waste problem caused by unnecessary SIB1 transmission. For example, energy is saved by reducing unnecessary SIB1 transmission and associated physical random access channel (PRACH) monitoring, and providing network devices with more opportunities to be in sleep mode. However, how to achieve on-demand SIB1 transmission and save network energy is a technical difficulty worth studying.

[0059] As an example, for a terminal device in idle / inactive mode, the cell that sends on-demand SIB1 is the NES cell. The NES cell does not carry SIB1 information when sending SSB. Therefore, the terminal device needs to send a SIB1 request to the NES cell to obtain the SIB1 information of the NES cell. The SIB1 request is, for example, an uplink wake-up signal (WUS) or on-demand information / signaling. The SIB1 information obtained by the terminal device can come from the NES cell, such as Figure 2 shown.

[0060] See also Figure 2 , the cell A (cell#A) in service (on) always periodically sends SSB (always on). However, SSB does not include SIB1. The communication system of cell A includes terminal device 210 and network device 220. When terminal device 220 attempts to access cell A that sends SIB1 on demand, terminal device 210 can send an uplink WUS to network device 220, that is, step S201. If network device 220 detects WUS, it sends SIB1 on demand, that is, step S202.

[0061] The above introduces the communication process of NES technology and NES cells. In this process, how the terminal device sends a SIB1 request and how the terminal device monitors the on-demand SIB1 sent by the network device are both problems that need to be solved.

[0062] For example, Figure 2 The SSB sent by cell A may not carry the resource configuration information requested by SIB1.

[0063] For another example, after the terminal device sends a SIB1 request according to the power ramp, it may immediately start decoding the indication search space of the physical downlink control channel (PDCCH) related to SIB1. However, the NES cell may have to wait until the next SI window to send SIB1. Because the window length and periodicity of SIB1 are usually longer. In this case, the terminal device may perform blind decoding that is impossible to succeed for a long time until a timer expires, thus consuming more power.

[0064] In response to the above problems, an embodiment of the present application proposes a method for wireless communication. Through this method, the terminal device can determine the sending mode and / or configuration parameters of the first request (SIB1 request) according to the first configuration information. After sending the first request, the terminal device can also detect and receive the target SIB1 according to the first time window indicated by the first configuration information. It can be seen that the target SIB1 is sent based on the trigger of the first request, and the monitoring of the terminal device is also performed within the indicated time window, so the power consumption of the terminal device and the network device can be saved.

[0065] For ease of understanding, the following Figure 3 The method proposed in the embodiment of the present application is described in detail. Figure 3 It is a schematic flowchart of the wireless communication method of an embodiment of the present application. Figure 3 The method shown includes steps S310 to S330. Figure 3 It is introduced from the perspective of the interaction between terminal devices and network devices.

[0066] The terminal device may be any communication device that requests the target SIB1, which is not limited here. In some embodiments, the terminal device may be a terminal device in an idle state or an inactive state. For example, the terminal device is a UE in an idle / inactive mode. In some embodiments, the terminal device is a communication terminal that supports the NES function.

[0067] In some implementations, a terminal device that supports request-based triggering of SIB1 is also referred to as a terminal device with NES capability.

[0068] In some implementations, a terminal device that does not support triggering of SIB1 based on a request of the terminal device is also referred to as a terminal device without NES capability or a legacy terminal device.

[0069] The network device may provide services for the cell where the terminal device is located. Optionally, the cell where the terminal device is located may be a cell where the terminal device is currently communicating, a cell that the terminal device is trying to access, or a cell determined by the terminal device after cell reselection or switching.

[0070] In some embodiments, the cell where the terminal device is located includes the first NES cell. That is, the cell where the terminal device is located may be the first NES cell, or may be a plurality of cells including the first NES cell.

[0071] The cell corresponding to the network device may be a cell in which the network device is providing services. The cell corresponding to the network device may be the same as the cell in which the terminal device is located, or may be a cell that communicates with the cell in which the terminal device is located.

[0072] In some embodiments, the cell corresponding to the network device is the first NES cell. That is, the network device provides communication services for the first NES cell. Therefore, the network device can provide services for the terminal device.

[0073] As an example, the first NES cell may be one of a plurality of NES cells. The plurality of NES cells may be indicated by a list of NES cell identifiers. If a list of NES cell identifiers is provided, the same configuration may be used for all of these cells.

[0074] In some embodiments, the cell corresponding to the network device is a non-NES cell that communicates with the first NES cell, for example Figure 4 The non-NES cell can be used as an anchor cell in the network. The non-NES cell can be used as a master cell, responsible for the first request configuration of multiple NES cells and the sending of the target SIB1. The non-NES cell can maintain information interaction with multiple NES cells. For example, the SSB sent by the non-NES cell will carry SIB1. For simplicity, the non-NES cell is used in the following text to represent a non-NES cell that can communicate with the first NES cell.

[0075] As an example, a non-NES cell corresponding to the network device may communicate with a plurality of NES cells including the first NES cell.

[0076] As an example, a non-NES cell may also be referred to as an anchor cell or an anchor point cell, that is, a non-NES cell may be an anchor point cell of multiple NES cells. A non-NES cell may receive configuration information of multiple NES cells.

[0077] As an example, the non-NES cell and the NES cell may communicate via an interface between base stations. For example, the non-NES cell may communicate with the first NES cell via an Xn interface.

[0078] In the above example, when the first request is sent based on contention free random access (CFRA), the non-NES cell can obtain all preamble code indexes and / or root sequences allocated by multiple NES cells based on CFRA through the Xn interface. For example, the non-NES cell sends a signaling request to one or more surrounding NES cells through the Xn interface to obtain the root sequence information currently used. The one or more NES cells can respond to the non-NES cell with configuration parameters such as the root sequence through the Xn interface.

[0079] In some scenarios, the root sequence of the NES cell may be dynamically adjusted according to the network status or interference between other cells. After adjusting the root sequence, the NES cell can notify the non-NES cell through the Xn interface to ensure that the configuration information of the non-NES cell is the latest.

[0080] In some scenarios, when the NES cell is reconfigured (for example, load balancing, interference avoidance strategy adjustment, etc.), new root sequence information is also sent to the non-NES cell through the Xn interface.

[0081] See also Figure 3 In step S310, the terminal device receives first configuration information. The first configuration information is related to the triggering request of the target SIB1, so the transmission of the target SIB1 helps to improve the utilization of energy and resources.

[0082] The target SIB1 is the SIB1 requested by the terminal device to the target cell. The transmission of the target SIB1 is triggered based on the request of the terminal device, so the target SIB1 is also the on-demand SIB1, namely "OD-SIB1 (on demand SIB1)".

[0083] When the target cell requested by the terminal device is the first NES cell, the target SIB1 is the SIB1 of the first NES cell. Optionally, the target SIB1 received by the terminal device may be from the first NES cell or from a non-NES cell communicating with the first NES cell.

[0084] The request of the terminal device to trigger the target SIB1 may be a first request. The first request may also be referred to as a SIB1 request. In the embodiment of the present application, the first request is not limited. For example, the first request may be a UL WUS, which is used to wake up the network device in the uplink so that it can send the target SIB1 at an appropriate time. For another example, the first request may be "on demand information or signaling".

[0085] In some embodiments, the first configuration information may include parameters related to the first request configuration. The parameters related to the first request configuration may include configuration parameters of the first NES cell and / or the non-NES cell. For example, the first NES cell may configure SSB transmission parameters related to the first request. For example, the non-NES cell may configure an identifier of the applied cell, such as a NES cell identifier list.

[0086] As an example, the parameters related to the first request configuration can come from the first NES cell or from the non-NES cell. For example, the terminal device can receive the configuration parameters sent by the first NES cell before it goes into sleep. As another example, the non-NES cell can provide the terminal device with the SSB parameters of the NES cell, such as ssb PositionsInBurst. In the relevant specifications, SIB1 will indicate ssb PositionsInBurst, and the terminal device can obtain the SSB index through ssb PositionsInBurst. In the present application, the SSB sent by the NES cell does not carry SIB1, so the non-NES cell can indicate the SSB number / index for the terminal device to determine the mapping between the SSB of the NES cell and the sending timing of the first request. Otherwise, the terminal device will not be able to select the appropriate first request sending timing corresponding to its optimal SSB index.

[0087] In the above example, when the terminal device sends the first request based on the random access procedure, the sending timing of the first request can share the random access channel occasion (random access channel occasion, RO).

[0088] As an example, the first configuration information may include resource configuration information of the first request. For example, the first request may be sent via PRACH resources to trigger the first NES cell to send the target SIB1. Figure 2 For example, if the SSB sent by cell A carries WUS / on demand information or signaling resource configuration information, when the terminal device 220 attempts to access the cell A that sends SIB1 on demand, the terminal device can send UL WUS to cell #A based on the configuration information. For example, the terminal device 220 can send a first request via a random access channel (RACH) or a separate signal or sequence to trigger cell A to send the target SIB1. If cell A detects the first request, the cell sends the on-demand SIB1.

[0089] As an example, the first configuration information may indicate a first preamble code associated with the first request, which will be described below in conjunction with step S320.

[0090] In some embodiments, the first configuration information may indicate one or more of the following configuration information: transmission of the first request; reception of the target SIB1 and reception of a first request-related response. When the terminal device sends the first request based on a random access procedure, the first request-related response may also be a random access response (RAR).

[0091] As an example, for transmission of the first request, the first configuration information may indicate that the first request is sent based on a random access procedure. For example, the first configuration information may include resources required to successfully complete the first request.

[0092] In the above example, when the first request is sent based on CFRA, the first configuration information may specify the relevant preamble index and its root sequence, and may also provide parameters required for UL power control. For example, the non-NES cell may carry the information of the preamble index and / or root sequence in the first configuration information. After the terminal device obtains the first configuration information (such as NES UE UL WUS configuration information) from the non-NES cell, it may initiate a random access process based on CFRA.

[0093] As an example, for receiving the target SIB1, the first configuration information may include resources of the PDCCH or physical downlink shared channel (PDSCH) for detecting SIB1 (or called SIB1 capture), so that the terminal device can detect and receive the target SIB1 in a timely manner.

[0094] As an example, for receiving the target SIB1, the first configuration information may indicate the transmission resources of the target SIB1. The transmission resources of the target SIB1 may include a first time window for receiving the target SIB1, or may include frequency domain resources, which will be described below in conjunction with step S330.

[0095] As an example, the first configuration information may also include resources for receiving a response related to the first request. Taking RAR as an example, the first configuration information may include resources for receiving RAR. RAR can serve as an explicit trigger for the terminal device to start monitoring resources for receiving the target SIB1. For example, when the terminal device sends the first request according to the power ramp parameter, it does not start monitoring SIB1 until RAR or PreambleTransMax is received. If RAR is not set, the terminal device may consume more power to receive the target SIB1. This is because the window of system information is much longer than the RAR response time.

[0096] As an implementation method, when the first request is WUS, the first configuration information may include one or more of the following parameters: NES-CellId; SIB1-RequestConfig; frequencyInfoUL; pdcch-ConfigSIB1; pdcch-ConfigOD-SIB1-RAR. Among them, the parameter NES-CellId is used to determine which cells the relevant configuration supports (To which cell does the config applies); the parameter SIB1-RequestConfig and the parameter frequencyInfoUL are used for WUS transmission (transmission); the parameter pdcch-ConfigSIB1 is used for target SIB1 reception (reception); the parameter pdcch-ConfigOD-SIB1-RAR is used for RAR reception. The details are shown in Table 1.

[0097] Table 1

[0098]

[0099]

[0100] As can be seen from Table 1, the first configuration information may include transmission parameters of the target SIB1 requested, and may also include transmission parameters of the target SIB1. For example, the first configuration information may include request parameters and transmission parameters for the non-NES cell to transmit the target SIB1.

[0101] The terminal device may receive the first configuration information in a variety of ways. As an example, the terminal device may directly receive the first configuration information sent by the network device. For example, when the trigger request of the target SIB1 is an uplink WUS, the terminal device may receive an uplink WUS configuration (UL WUS Config) sent by the network device. As an example, the terminal device may determine the first configuration information based on higher layer signaling.

[0102] Exemplarily, when the network device corresponds to a non-NES cell, the non-NES cell may send the first configuration information to terminal devices in a plurality of NES cells, wherein the plurality of NES cells include a first NES cell.

[0103] In step S320, the terminal device sends a first request to the network device, the first request being used to request the target SIB1. The network device may receive the first request sent by the terminal device and trigger the sending of the target SIB1. Exemplarily, when the network device corresponds to a non-NES cell, the terminal device may send an uplink WUS to the non-NES cell.

[0104] The target SIB1 corresponds to the first NES cell. In other words, the target SIB1 is the SIB1 triggered by the first request corresponding to the first NES cell, or in other words, the target SIB1 is the SIB1 of the first NES cell.

[0105] When the terminal device sends the first request based on the random access process, the first request may be sent based on the preamble. For example, the first request may include the first preamble, and the first preamble is used by the terminal device to request the target SIB1. For another example, the first request may correspond to the first preamble, or the first request is related to the first preamble.

[0106] The first preamble associated with the first request can reuse the preamble in the related communication system. Taking the preamble of NR random access as an example, the preamble can be divided into three parts: contention random access, non-contention random access (also called non-contention random access) and others. For CFRA, high-level parameters will indicate which preamble to use, thereby avoiding the situation where different terminal devices select the same preamble and cause interference. In CFRA, the network (through the radio resource control (RRC) layer) can directly specify the preamble for the terminal device. This process is implemented through high-level signaling, such as through the RRC Connection Reconfiguration message.

[0107] As can be seen from the foregoing, the terminal device can send a first request based on CFRA to ensure random access without contention and conflict. It is sufficient to send the first request using only the preamble of CFRA, because all terminal devices request the same message, namely the target SIB1. In addition, it is also a relatively effective way for the network device to satisfy the first request by sending the target SIB1 according to broadcast. The lack of dedicated transmission can reduce overhead. Compared with contention-based random access, CFRA can save the number of parameters required for the configuration of the first request.

[0108] In the embodiment of the present application, the sequence of the preamble is not limited. Exemplarily, the preamble may be generated by a Zadoff-Chu sequence, which has good correlation characteristics in time and frequency.

[0109] The first configuration information can be used to indicate the first preamble. When the first configuration information comes from a non-NES cell, the non-NES cell can indicate the first preamble according to the preamble sent by the first NES cell. When the first configuration information comes from the first NES cell, the first NES cell can directly allocate the first preamble to the terminal device. In other words, the terminal device can obtain the first preamble and the index of the first preamble from the non-NES cell, and can also obtain the first preamble and the index of the first preamble from the first NES cell.

[0110] Optionally, after obtaining the first configuration information, the terminal device may determine the first preamble code according to the first configuration information.

[0111] Optionally, the terminal device may obtain the preamble code index when sending the first request based on CFRA while obtaining the first configuration information from the non-NES cell or from the first NES cell.

[0112] In some embodiments, when multiple terminal devices including a terminal device send multiple first requests, the multiple first requests can be sent based on the same preamble. That is, the non-NES cell or the first NES cell can specify the same preamble index and root sequence for each terminal device. Exemplarily, when the first request sent by the terminal device includes the first preamble, the first preamble can be used for multiple terminal devices that send the first request.

[0113] In some embodiments, the non-NES cell or the first NES cell may specify a unique preamble index and root sequence for each terminal device. In CFRA, each terminal device is assigned a unique preamble index. The index is usually selected from the available preamble set. For example, the base station (gNB) may pre-assign one or more preamble indexes to each terminal device according to network planning or the specific needs of the terminal device.

[0114] As an example, when the first request includes the first preamble, the first preamble may be one of the first preamble group. The preambles in the first preamble group may be used for multiple terminal devices that send the first request. Exemplarily, all preambles in the first preamble group may be dedicated preambles for SIB1 requests.

[0115] As an example, the first preamble code group includes multiple preamble codes, and the multiple preamble codes correspond one-to-one to multiple terminal devices.

[0116] In the above example, the first preamble group may be one or more of the following: the first preamble group is one of at least two preamble groups used for CFRA; the preambles in the first preamble group are preambles reserved by the network device.

[0117] Exemplarily, the preambles used for CFRA may be divided into at least two preamble groups. The at least two preamble groups may include a first preamble group and a second preamble group, and the second preamble group is used for a random access procedure.

[0118] As can be seen from the foregoing, the first NES cell will maintain information exchange with the non-NES cell. The first NES cell can divide the preambles for non-contention access into two groups: Group A and Group B. Group A is used by users in this cell, such as the preambles assigned during switching; Group B is used by terminal devices that initiate the first request. The first NES cell will send the preambles and / or preamble indexes of Group B to the non-NES cell, so that the non-NES cell can assign preamble indexes and / or preambles to the terminal devices. Each terminal device assigned a CFRA preamble uses the network-specified preamble when initiating the first request in the NES cell, thereby ensuring non-contention access.

[0119] Exemplarily, the first NES cell may also allocate a reserved preamble to the terminal device that sends the first request. The reserved preamble is, for example, a preamble of other parts of the NR preamble described above.

[0120] Exemplarily, when the first preamble group includes a preamble group (eg, group B) for CFRA and a reserved preamble, it may be determined whether to use the preamble in group B or the reserved preamble according to the second condition.

[0121] As an implementation, the second condition is related to the location information of the terminal device. That is, when the first preamble group includes a preamble group for CFRA and a reserved preamble, the first preamble is determined according to the location information of the terminal device. For example, when the terminal device is at the edge of a non-NES cell / a first NES cell, the non-NES cell / the first NES cell can allocate a preamble in group B to the terminal device, and the terminal devices at other locations are allocated a reserved preamble, or vice versa.

[0122] Continue to see Figure 3 In step S330, the terminal device receives the target SIB1 sent by the network device. Accordingly, the network device sends the target SIB1. Exemplarily, when the network device corresponds to a non-NES cell, if the non-NES cell receives the first request, the target SIB1 can be sent to the terminal device in the first NES cell.

[0123] In some embodiments, the sending of the target SIB1 is determined based on the first condition. That is, even if the network device receives the first request, the sending of the target SIB1 requires other triggering conditions to reduce the power consumption of the terminal device and the network device. The power consumption cost of the terminal device and the network device is proportional to the rate of triggering events acquired by the target SIB1. For terminal devices with high mobility, cell reselection events may occur frequently, triggering excessive requests for the target SIB1, resulting in frequent sending of the target SIB1, which is not ideal for the power consumption and interference of the terminal device and the network. When determining whether to send the target SIB1 based on the first condition, the sending frequency of the target SIB1 can be avoided / minimized based on an effective mechanism to reduce power consumption.

[0124] In some embodiments, the first condition may include one or more of the following: whether the cell corresponding to the network device receives the first type of trigger event; the number of terminal devices sending the first request in the cell corresponding to the network device; and the measurement result of the terminal device.

[0125] As an example, the first type of triggering event may be an event other than the first request triggering that is used to trigger the sending of the target SIB1. For the first type of triggering event, the first NES cell may know the occurrence of the triggering event by presetting, thereby sending the target SIB1 to the terminal device without the first request. Exemplarily, the first type of triggering event may include receiving an indication that the system information has been changed, receiving a public warning system (PWS) notification, reconfiguration after synchronization is completed, and other events that can trigger the sending of SIB1. Exemplarily, the first type of triggering event may also include events such as cell reselection and cell switching initiated by traditional terminal devices. Exemplarily, the first type of triggering event may also include events such as the terminal device returning from out of coverage, the terminal device entering the network from another radio access technology (RAT), the terminal device receiving a request (e.g., a positioning request) from an upper layer, the terminal device having no stored SIB or the SIB valid version expired or requesting the SIB valid version, and the terminal device performing satellite switching with resynchronization.

[0126] In the embodiment of the present application, for the first type of triggering event, the traditional terminal device and the terminal device supporting NES will have different operations. Once the terminal device supporting NES resides in the first NES cell, after receiving the indication of SI change, the terminal device can also trigger the sending of the first request. The first NES cell / non-NES cell can send the target SIB1 in the next SI modification cycle. In other words, the terminal device residing in the first NES cell sends the first request, which can avoid frequently triggering the sending of the target SIB1 to the high-speed mobile terminal device. However, the terminal device supporting NES may frequently trigger the sending of the first request in a high-speed mobile environment. If the terminal device does not receive the target SIB1 after N (N is an integer) times of sending, or the terminal device does not receive the target SIB1 within a certain time T, the terminal device can assume that the SIB1 received last time has not changed, and will complete subsequent operations based on the stored last SIB1.

[0127] As an example, the first condition may be related to the number of terminal devices sending the first request in the cell corresponding to the network device. The number of terminal devices sending the first request may also be replaced by the number of terminal devices triggering the sending of the target SIB1.

[0128] In the above example, the number of terminal devices can also be used to determine the sending method of the target SIB1. When the number of terminal devices is greater than the first threshold, the target SIB1 can be sent through broadcast; when the number of terminal devices is less than or equal to the first threshold, the target SIB1 is sent through downlink control information (DCI). Vice versa.

[0129] As an implementation method, the first NES cell / non-NES cell can be in a very small statistical time [T min , T max ] within a certain period of time, the number of users who send the first request or the number of users of the triggering event that triggers the sending of SIB1 are counted. If the counted number is greater than a set value, the first NES cell / non-NES cell may send the target SIB1 immediately through a broadcast message after the counting time, instead of sending it through DCI. If the counted number is less than a set value, the first NES cell / non-NES cell may send the target SIB1 through DCI instead of a broadcast message after the counting time.

[0130] For ease of understanding, the following Figure 4 Take this as an example for introduction. Figure 4 The communication method shown is executed by a network device.

[0131] See also Figure 4In step S410, the network device determines whether the number of terminal devices sending the first request is greater than a first threshold, if yes, then execute step S420, if not, then execute step S430.

[0132] In step S420, the network device sends the target SIB1 by broadcasting.

[0133] In step S430, the network device sends the target SIB1 via downlink control information.

[0134] It should be understood that Figure 4 The determination of the sending mode of the target SIB1 based on the magnitude relationship between the number of terminal devices and the first threshold is only an example. In some scenarios, after the judgment is made in step S410, if yes, step S430 is executed, and if not, step S420 is executed.

[0135] As an implementation method, when the number of terminal devices is greater than the first threshold, the target SIB1 can be sent via DCI; when the number of terminal devices is less than or equal to the first threshold, the target SIB1 is sent via DCI. For the frequency range (FR) 2 scenario, the transmission of the broadcast message requires scanning each beam for transmission, which consumes more power than DCI transmission.

[0136] As an example, the measurement result of the terminal device includes a reference signal received power (RSRP) value measured by the terminal device. The RSRP value may be a result of measuring the received SSB. As an implementation, the RSRP value measured for the SSB is greater than a threshold RSRP target , the terminal device can trigger the sending of the target SIB1.

[0137] In some embodiments, in order to receive the target SIB1, the terminal device needs to be synchronized with the cell that sends the target SIB1. For example, when the non-NES cell is the first NES cell that sends the target SIB1, the terminal device needs to be synchronized with the time and frequency of the non-NES cell.

[0138] In some embodiments, in order to receive the target SIB1, the terminal device also needs to determine other information of the cell sending the target SIB1. For example, when the non-NES cell is the first NES cell sending the target SIB1, the terminal device needs to detect the physical layer cell identity (ID) of the non-NES cell.

[0139] As can be seen from the foregoing, the first configuration information may indicate the transmission resources of the target SIB1. Exemplarily, the transmission resources of the target SIB1 may include the first time window in which the terminal device receives the target SIB1. Exemplarily, the transmission resources of the target SIB1 may include the frequency domain resources corresponding to the first NES cell. Exemplarily, the transmission resources of the target SIB1 may be a physical resource block (PRB).

[0140] In some embodiments, the first time window may include a time domain position at which a network device sends a target SIB1 or a terminal device receives a target SIB1. The first configuration information is also used to indicate the first time window. Optionally, the first configuration information may indicate a position of the target SIB1 within the first time window. Optionally, the first configuration information may indicate how the terminal device determines the position of the target SIB1 within the first time window. For example, the first configuration information may indicate that the position of the target SIB1 within the first time window is determined according to the ID of the first NES cell.

[0141] As an example, the first time window may be related to the RAR time window mentioned above. Exemplarily, when the first request is sent based on a random access procedure, the first time window may be a time window for detecting a random access response.

[0142] As an example, the first time window may be related to the SI sending window. When the network device corresponds to a non-NES cell, since the non-NES cell may send the target SIB1 of multiple NES cells, the relevant SI acquisition process may be used for transmission. In other words, the non-NES cell may send the target SIB1 to the terminal devices in different NES cells by sending SI. Exemplarily, the first time window is the SI window, and the target SIB1 is sent through the SI window. The following text will provide an exemplary explanation in conjunction with the determination method of the first time window.

[0143] In some embodiments, when a network device of a non-NES cell provides services for multiple NES cells including a first NES cell, multiple SIB1s (ie, multiple target SIB1s or on-demand SIB1s) of the multiple NES cells are respectively sent on different frequency domain resources.

[0144] As an example, the frequency domain resource may be a bandwidth part (BWP), a frequency band, a frequency range or a carrier. For example, different frequency domain resources corresponding to multiple NES cells are different BWPs.

[0145] As an example, BWP is divided in non-NES cells, and different target SIB1 resources are allocated to different NES cells, thereby optimizing resource utilization and reducing interference. BWP is usually a continuous spectrum resource that can be independently configured and managed in NR. Non-NES cells can be configured with multiple BWPs at the same time, and each BWP can support different bandwidth and parameter configurations.

[0146] As an implementation method, a non-NES cell can divide multiple BWPs according to its own spectrum resources and the number of NES cells it serves, and different BWPs are allocated to different NES cells.

[0147] As an implementation method, in the divided BWP, a specific target SIB1 resource is allocated to each BWP. For example, the first NES cell corresponds to the first BWP, and the first BWP includes dedicated resources for the target SIB1. Each BWP corresponding to each NES cell may include dedicated resources corresponding to SIB1. The terminal equipment of each NES cell may receive the target SIB1 in the BWP corresponding to the cell. This configuration can avoid interference of SIB1 information generated between multiple different NES cells and improve resource utilization efficiency.

[0148] As an implementation method, a non-NES cell can send frequency domain resource allocation information to terminal devices in multiple NES cells. For example, a non-NES cell can broadcast the configuration information of the BWP and target SIB1 corresponding to each NES to the terminal devices in each NES cell through SIB or dedicated signaling. In this way, the terminal device knows in which BWP and frequency band to receive the target SIB1. The terminal device in each NES cell receives the target SIB1 on the BWP allocated to the NES cell where it is located according to the received configuration information.

[0149] As an implementation method, non-NES cells can dynamically adjust the BWP bandwidth and target SIB1 resource allocation of each NES cell according to the real-time network load and cell demand of multiple NES cells. For example, when the load of a certain NES cell increases, its BWP bandwidth can be expanded or more target SIB1 resources can be reallocated.

[0150] As an implementation, different NES cells may share some BWP resources under low load conditions. For example, multiple NES cells may reuse the first requested resources and / or target SIB1 resources by time division or frequency hopping to improve spectrum utilization.

[0151] In some embodiments, a non-NES cell may allocate different PRBs or the same PRBs to different NES cells. A PRB is usually composed of a subcarrier and a time slot, and is the minimum allocation unit of frequency domain and time domain resources. When different PRBs are allocated, interference between SIB1 information can be avoided. When the same PRB is allocated, spectrum utilization can be improved. Furthermore, PRB reuse and hopping techniques can be used to improve spectrum utilization. That is, based on hopping or the same PRB being reused, it can be ensured that the PRBs used to send the target SIB1 of multiple NES cells will not conflict, thereby avoiding signal conflicts between different cells.

[0152] As an example, the same PRB resources allocated to different NES cells may be referred to as first resources. Non-NES cells may allocate the same PRB resources to NES cells in an NES cell group (or referred to as an NES cell set). For example, when the first NES cell is one of the first NES cell group, multiple SIB1s corresponding to multiple NES cells in the first NES cell group may be sent by multiplexing the first resources.

[0153] In the above example, through frequency hopping technology, different NES cells can use the same PRB resources (first resources) on different frequencies, and the frequency can hop in time. In this way, even if two NES cells use the same PRB in a certain time slot, they will not interfere with each other due to their different frequencies. Frequency hopping can be performed according to a preset pattern (such as a pseudo-random sequence). The PRB of each cell will hop to different frequency positions in different time periods, which can reduce long-term frequency interference.

[0154] In the above example, in a cell with a MIMO antenna system, the PRBs can be reused in different spatial directions by beamforming technology. That is, the first resource can be reused based on the spatial direction. For example, two NES cells can use the same PRBs in different antenna beam directions without interfering with each other.

[0155] Combination of the above Figure 3 and Figure 4 The present invention introduces a method embodiment of a terminal device sending a first request and receiving a target SIB1 based on an instruction of a first configuration information. For ease of understanding, the following takes a non-NES cell sending a target SIB1 as an example. Figure 5 The system structure and process are illustrated. Figure 5 The cell served by the network device 502 is an anchor cell, that is, a non-NES cell. In the coverage area of ​​the anchor cell, the terminal device 501 and two NES cells, namely the first NES cell and the second NES cell, are schematically shown.

[0156] See also Figure 5 In step S510, the network device 502 sends UE UL WUS configuration information of the first NES cell and the second NES cell to the terminal device 501.

[0157] In step S520, the terminal device 501 sends an uplink WUS (first request) to the network device 502 to request the target SIB1 of the first NES cell or the second NES cell.

[0158] In step S530, after receiving the request signal from the terminal device, the network device 502 sends the target SIB1 to the terminal device that initiates the request in the first NES cell or the second NES cell.

[0159] exist Figures 3 to 5 In the method shown, the first configuration information may indicate the transmission resources of the target SIB1. Among them, the transmission resources of the target SIB1 may include a first time window for the terminal device to receive the target SIB1. The first time window may be related to the SI window. When a non-NES cell sends the target SIB1 of multiple NES cells based on the same SI window, there may be many SIB1 messages, and how to configure multiple SIB1s to reduce conflicts is a problem that needs to be considered. In addition, too many SIB1 messages may also cause the SI window period to be too long or cause interference. If the SI window period is too long, the delay of the network device sending SIB1 to the terminal device in the NES cell will increase.

[0160] Based on this, the embodiment of the present application also proposes a method for indicating the target SIB1 transmission resource. The method is a SI window offset strategy based on the cell ID, which determines the starting time or offset of the SI of each cell within the SI window by using the cell ID. Through this method, the network equipment can evenly distribute the SI broadcast time slots of multiple NES cells, thereby avoiding conflicts and optimizing resource utilization.

[0161] In some embodiments, the position of the target SIB1 within the first time window is determined according to the ID of the first NES cell. The ID of the first NES cell may be a physical cell identity (PCI).

[0162] Exemplarily, the ID of the first NES cell is used to determine the first offset of the target SIB1 within the first time window. That is, the ID of the first NES cell can be used to determine the starting time of the target SIB1 within the SI window. If an SI window consists of 10 subframes and the first offset of the first NES cell is 3, the target SIB1 information of the first NES cell will be broadcast starting from the 3rd subframe within the SI window. By generating different offsets through different cell IDs, it can be ensured that the terminal devices of multiple NES cells read the target SIB1 of their own cells at different times, thereby reducing signal conflicts and interference.

[0163] As an example, when the first time window is used to send multiple SIB1s including the target SIB1, the first offset SI offset for:

[0164] SI offset =(cell ID ×k)mod T;

[0165] Among them, cell ID is the ID of the first NES cell, k is an interval factor related to the interval of multiple SIB1s in the first time window, and T is the length of the first time window.

[0166] Optionally, cell ID It can be the PCI of the first NES cell.

[0167] Optionally, k may be the first spacing factor corresponding to the target SIB1. k may be a constant factor used to adjust the span of the offset to ensure that different NES cells are sufficiently separated within the SI window. By adjusting the k value, the distribution density of SI information and the spacing between different NES cells within the SI window may be controlled to meet the needs of different networks.

[0168] Optionally, T is the total length of the SI window. T may represent the number of time slots or subframes included in the first time window or SI window.

[0169] In some embodiments, the target SIB1 corresponds to a first NES cell, and the first NES cell is one of a plurality of NES cells served by the network device. When the network device corresponds to a non-NES cell communicating with a plurality of NES cells, the position of the target SIB1 within the first time window and / or the first interval factor corresponding to the target SIB1 may also be determined according to the load of the non-NES cell and / or the load of the first NES cell.

[0170] As an example, when the load of the first NES cell is high, the target SIB1 can be distributed more densely in the first time window. For example, when the load is high, the target SIB1 is distributed more densely in the time domain or frequency domain by increasing the offset parameter value / interval factor in the time domain or frequency domain. This means that SI information can be transmitted more frequently. When the load is low, the offset parameter value / interval factor can be reduced to reduce the broadcast frequency of SI information and save resources. That is, the interval factor is adjusted in real time according to the load of the first NES cell.

[0171] As an example, the load of a non-NES cell may include the load conditions of each NES cell within its coverage. A non-NES cell may continuously monitor its load conditions and the network load conditions of each NES cell within its coverage. Based on the real-time network load, a non-NES cell may dynamically adjust the k value in the above formula, or directly adjust the offset of a certain NES cell. For example, in a highly loaded NES cell, the offset of the SI window may be slightly adjusted to ensure that SI information can be transmitted more frequently.

[0172] As an example, the load of a non-NES cell is related to one or more of the following information: the number of NES cells communicating with the non-NES cells; the number of terminal devices sending SIB1 requests; the sending frequency of SIB1 requests; and the physical resource block (PRB) occupancy rate of uplink resources.

[0173] As an example, the load of the first NES cell is related to one or more of the following information: the number of terminal devices that send SIB1 requests; the frequency of sending SIB1 requests; the PRB occupancy rate of uplink resources. In other words, the network load can be measured by the following indicators: the number of terminals that send the first request in each NES cell within a period of time, and the frequency of the request; or the use of uplink frequency domain resources can be measured by the PRB occupancy rate.

[0174] As an implementation method, the non-NES cell can set one or more load thresholds for each NES cell within its coverage area. For example, when the PRB occupancy rate exceeds 80%, or the number of terminal device connections reaches a certain number, the SI window offset adjustment is triggered.

[0175] As an implementation, the first spacing factor can be adjusted according to the load of the first NES cell. The first spacing factor can be adjusted using a linear or nonlinear formula. For example, the second spacing factor k after the first spacing factor is adjusted is adjust for:

[0176]

[0177] Among them, k initialis the initial interval factor, Q is the real-time load value, Q adjust is the load intermediate value used to adjust the spacing factor, Q max is the maximum load value of the first NES cell.

[0178] As an example, the second interval factor adjusted in real time is not necessarily used to determine the new offset. In other words, the second interval factor can be used to determine the new offset based on certain conditions to reduce the amount of calculation.

[0179] As an implementation method, when the difference between the second interval factor and the first interval factor is greater than or equal to the second threshold, the second interval factor is used to determine the position of the target SIB1 within the first time window; when the difference between the second interval factor and the first interval factor is less than the second threshold, the first interval factor is used to determine the position of the target SIB1 within the first time window.

[0180] As an implementation, the second offset determined according to the second interval factor is:

[0181] SI offset =(cell ID ×k adjust )mod T.

[0182] As an implementation, after calculating the new offset, the system can immediately update the SI window so that SI information can be broadcast more frequently under high load conditions. It should be understood that after adjusting the offset, the non-NES cell should also continue to monitor the adjustment effect, including the transmission efficiency of SI information and the change of network load.

[0183] As an example, the first interval factor may also be adjusted according to one or more of the following information: the priority of the first NES cell; the location of the first NES cell within the coverage of the non-NES cell; and the level at which the ID of the first NES cell is located.

[0184] As an implementation method, non-NES cells divide cells into different priorities according to the importance of multiple NES cells, or implement differentiated interval factor adjustment strategies for NES cells of different priorities. For example, cells with high priorities can be allocated more time slots in the SI window, so that the SI information of these cells can be broadcast more frequently. The adjustment range of the SI window can be larger.

[0185] As an implementation method, non-NES cells can divide cells into different priorities according to the coverage areas of multiple NES cells, or implement differentiated interval factor adjustment strategies for NES cells in different areas. For example, NES cells in core locations can be set with smaller thresholds and larger adjustment ranges, while NES cells in edge locations are relatively conservative.

[0186] As an implementation method, for larger-scale networks, it is possible to divide the IDs of NES cells into different levels. Cells at each level use different offset calculation formulas or interval factor adjustment strategies or SI window lengths. For example, NES cells at level 1 use a shorter SI window, and NES cells at level 2 use a longer SI window. Through this multi-level offset strategy, a more uniform SI information distribution can be achieved in the network.

[0187] Combination of the above Figures 1 to 5 , describes in detail the method embodiment of the present application. Figures 6 to 8 , describes the device embodiment of the present application in detail. It should be understood that the description of the device embodiment corresponds to the description of the method embodiment, so the parts not described in detail can refer to the previous method embodiment.

[0188] Figure 6 600 is a schematic block diagram of a terminal device according to an embodiment of the present application. The terminal device 600 may be any of the terminal devices described above. Figure 6 The terminal device 600 shown includes a transceiver unit 610 .

[0189] The transceiver unit 610 can be used to receive first configuration information, which is related to the trigger request of the target SIB1; the transceiver unit 610 is also used to send a first request to the network device, and the first request is used to request the target SIB1; the transceiver unit 610 is also used to receive the target SIB1 sent by the network device; wherein the first configuration information is used to indicate the first preamble code related to the first request and / or the transmission resources of the target SIB1.

[0190] Optionally, the transceiver unit 610 is further configured to send a first request based on CFRA.

[0191] Optionally, the first request includes a first preamble code, and the first preamble code is used to send the first request to multiple terminal devices.

[0192] Optionally, the first request includes a first preamble code, the first preamble code is one of a first preamble code group, and the preamble codes in the first preamble code group are used to send the first request to multiple terminal devices.

[0193] Optionally, the first preamble code group is one or more of the following: the first preamble code group is one of at least two preamble code groups used for CFRA, the at least two preamble code groups also include a second preamble code group, and the second preamble code group is used for a random access process; the preamble codes in the first preamble code group are preamble codes reserved by the network device.

[0194] Optionally, when the first preamble code group includes a preamble code group for CFRA and a reserved preamble code, the first preamble code is determined according to the location information of the terminal device.

[0195] Optionally, the sending of the target SIB1 is determined according to a first condition, which includes one or more of the following: whether the cell corresponding to the network device receives a first type of trigger event; the number of terminal devices that send the first request in the cell corresponding to the network device; and the measurement results of the terminal devices.

[0196] Optionally, when the number of terminal devices is greater than a first threshold, the target SIB1 is sent via broadcast; when the number of terminal devices is less than or equal to the first threshold, the target SIB1 is sent via downlink control information.

[0197] Optionally, the first configuration information includes one or more of the following: NES-CellId; SIB1-RequestConfig; frequencyInfoUL; pdcch-ConfigSIB1; pdcch-ConfigOD-SIB1-RAR.

[0198] Optionally, the transmission resources of the target SIB1 include a first time window for the terminal device to receive the target SIB1, and the first configuration information is also used to indicate the position of the target SIB1 within the first time window, or the position of the target SIB1 within the first time window is determined according to the ID of the cell corresponding to the target SIB1.

[0199] Optionally, the target SIB1 corresponds to a first NES cell, and the ID of the first NES cell is used to determine a first offset of the target SIB1 within a first time window.

[0200] Optionally, the first time window is used to send multiple SIB1s including the target SIB1, and the first offset SI offset for:

[0201] SI offset =(cell ID ×k)mod T;

[0202] Among them, cell ID is the ID of the first NES cell, k is the interval factor related to the interval of multiple SIB1s in the first time window, and T is the length of the first time window.

[0203] Optionally, the target SIB1 corresponds to a first NES cell, the first NES cell is one of multiple NES cells served by the network device, the network device corresponds to a non-NES cell that communicates with multiple NES cells, and the position of the target SIB1 within the first time window and / or the first interval factor corresponding to the target SIB1 is determined according to the load of the first NES cell.

[0204] Optionally, the first interval factor is adjusted according to the load of the first NES cell, and the second interval factor k after the first interval factor is adjusted is adjust for:

[0205]

[0206] Among them, k initial is the initial interval factor, Q is the real-time load value, Q adjust is the load intermediate value used to adjust the spacing factor, Q max is the maximum load value of the first NES cell.

[0207] Optionally, when the difference between the second interval factor and the first interval factor is greater than or equal to a second threshold, the second interval factor is used to determine the position of the target SIB1 within the first time window; when the difference between the second interval factor and the first interval factor is less than the second threshold, the first interval factor is used to determine the position of the target SIB1 within the first time window.

[0208] Optionally, the first interval factor may also be adjusted according to one or more of the following information: the priority of the first NES cell; the location of the first NES cell within the coverage of the non-NES cell; and the level at which the ID of the first NES cell is located.

[0209] Optionally, the target SIB1 corresponds to a first NES cell, the transmission resources corresponding to the target SIB1 include frequency domain resources corresponding to the first NES cell, the first NES cell is one of multiple NES cells served by the network device, and multiple SIB1s of multiple NES cells are respectively sent on different frequency domain resources.

[0210] Optionally, different frequency domain resources are different BWPs, the first NES cell corresponds to a first BWP, and the first BWP includes dedicated resources for the target SIB1.

[0211] Optionally, the target SIB1 corresponds to a first NES cell, the first NES cell is one of a first NES cell group, and multiple SIB1s corresponding to multiple NES cells in the first NES cell group are sent by multiplexing the first resource.

[0212] Optionally, the target SIB1 corresponds to the first NES cell, the network device corresponds to the first NES cell, or the network device corresponds to a non-NES cell that communicates with the first NES cell.

[0213] Figure 7 700 is a schematic block diagram of a network device according to an embodiment of the present application. The network device 700 may be any of the network devices described above. Figure 7The network device 700 shown includes a transceiver unit 710 .

[0214] The transceiver unit 710 can be used to send first configuration information, which is related to the trigger request of the target SIB1; the transceiver unit 710 is also used to receive a first request sent by a terminal device, and the first request is used to request the target SIB1; the transceiver unit 710 is also used to send the target SIB1 to the terminal device; wherein the first configuration information is used to indicate the first preamble code related to the first request and / or the transmission resources of the target SIB1.

[0215] Optionally, the first request is sent based on CFRA.

[0216] Optionally, the first request includes a first preamble code, and the first preamble code is used to send the first request to multiple terminal devices.

[0217] Optionally, the first request includes a first preamble code, the first preamble code is one of a first preamble code group, and the preamble codes in the first preamble code group are used to send the first request to multiple terminal devices.

[0218] Optionally, the first preamble code group is one or more of the following: the first preamble code group is one of at least two preamble code groups used for CFRA, the at least two preamble code groups also include a second preamble code group, and the second preamble code group is used for a random access process; the preamble codes in the first preamble code group are preamble codes reserved by the network device.

[0219] Optionally, when the first preamble code group includes a preamble code group for CFRA and a reserved preamble code, the first preamble code is determined according to the location information of the terminal device.

[0220] Optionally, the sending of the target SIB1 is determined according to a first condition, which includes one or more of the following: whether the cell corresponding to the network device receives a first type of trigger event; the number of terminal devices that send the first request in the cell corresponding to the network device; and the measurement results of the terminal devices.

[0221] Optionally, when the number of terminal devices is greater than a first threshold, the target SIB1 is sent via broadcast; when the number of terminal devices is less than or equal to the first threshold, the target SIB1 is sent via downlink control information.

[0222] Optionally, the first configuration information includes one or more of the following: NES-CellId; SIB1-RequestConfig; frequencyInfoUL; pdcch-ConfigSIB1; pdcch-ConfigOD-SIB1-RAR.

[0223] Optionally, the transmission resources of the target SIB1 include a first time window for the terminal device to receive the target SIB1, and the first configuration information is also used to indicate the position of the target SIB1 within the first time window, or the position of the target SIB1 within the first time window is determined according to the identification ID of the cell corresponding to the target SIB1.

[0224] Optionally, the target SIB1 corresponds to a first NES cell, and the ID of the first NES cell is used to determine a first offset of the target SIB1 within a first time window.

[0225] Optionally, the first time window is used to send multiple SIB1s including the target SIB1, and the first offset SI offset for:

[0226] SI offset =(cell ID ×k)mod T;

[0227] Among them, cell ID is the ID of the first NES cell, k is the interval factor related to the interval of multiple SIB1s in the first time window, and T is the length of the first time window.

[0228] Optionally, the target SIB1 corresponds to a first NES cell, the first NES cell is one of multiple NES cells served by the network device, the network device corresponds to a non-NES cell that communicates with multiple NES cells, and the position of the target SIB1 within the first time window and / or the first interval factor corresponding to the target SIB1 is determined according to the load of the first NES cell.

[0229] Optionally, the first interval factor is adjusted according to the load of the first NES cell, and the second interval factor k after the first interval factor is adjusted is adjust for:

[0230]

[0231] Among them, k initial is the initial interval factor, Q is the real-time load value, Q adjust is the load intermediate value used to adjust the spacing factor, Q max is the maximum load value of the first NES cell.

[0232] Optionally, when the difference between the second interval factor and the first interval factor is greater than or equal to a second threshold, the second interval factor is used to determine the position of the target SIB1 within the first time window; when the difference between the second interval factor and the first interval factor is less than the second threshold, the first interval factor is used to determine the position of the target SIB1 within the first time window.

[0233] Optionally, the first interval factor may also be adjusted according to one or more of the following information: the priority of the first NES cell; the location of the first NES cell within the coverage of the non-NES cell; and the level at which the ID of the first NES cell is located.

[0234] Optionally, the target SIB1 corresponds to a first NES cell, the transmission resources corresponding to the target SIB1 include frequency domain resources corresponding to the first NES cell, the first NES cell is one of multiple NES cells served by the network device, and multiple SIB1s of multiple NES cells are respectively sent on different frequency domain resources.

[0235] Optionally, different frequency domain resources are different BWPs, the first NES cell corresponds to a first BWP, and the first BWP includes dedicated resources for the target SIB1.

[0236] Optionally, the target SIB1 corresponds to a first NES cell, the first NES cell is one of a first NES cell group, and multiple SIB1s corresponding to multiple NES cells in the first NES cell group are sent by multiplexing the first resource.

[0237] Optionally, the target SIB1 corresponds to the first NES cell, the network device corresponds to the first NES cell, or the network device corresponds to a non-NES cell that communicates with the first NES cell.

[0238] Figure 8 Shown is a schematic diagram of the structure of a communication device according to an embodiment of the present application. Figure 8 The dotted line in the figure indicates that the unit or module is optional. The device 800 can be used to implement the method described in the above method embodiment. The device 800 can be a chip, a terminal device or a network device.

[0239] The device 800 may include one or more processors 810. The processor 810 may support the device 800 to implement the method described in the foregoing method embodiment. The processor 810 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 also be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

[0240] The apparatus 800 may further include one or more memories 820. The memory 820 stores a program, which can be executed by the processor 810, so that the processor 810 executes the method described in the above method embodiment. The memory 820 may be independent of the processor 810 or integrated in the processor 810.

[0241] The apparatus 800 may further include a transceiver 830. The processor 810 may communicate with other devices or chips through the transceiver 830. For example, the processor 810 may transmit and receive data with other devices or chips through the transceiver 830.

[0242] The present application also provides a computer-readable storage medium for storing a program. The computer-readable storage medium can be applied to a terminal device or a network device provided in the present application, and the program enables a computer to execute the method performed by the terminal device or the network device in each embodiment of the present application.

[0243] The computer-readable storage medium may be any available medium that can be read by a computer or a data storage device such as a server or a data center that includes one or more available media. The available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a digital video disc (DVD)), or a semiconductor medium (e.g., a solid state disk (SSD)).

[0244] The embodiment of the present application also provides a computer program product. The computer program product includes a program. The computer program product can be applied to the terminal device or network device provided in the embodiment of the present application, and the program enables the computer to execute the method performed by the terminal device or network device in each embodiment of the present application.

[0245] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. 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 computer-readable storage medium, for example, the computer instructions can be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center.

[0246] The embodiment of the present application also provides a computer program. The computer program can be applied to the terminal device or network device provided in the embodiment of the present application, and the computer program enables a computer to execute the method executed by the terminal or network device in each embodiment of the present application.

[0247] The terms "system" and "network" in this application can be used interchangeably. In addition, the terms used in this application are only used to explain the specific embodiments of the present application, and are not intended to limit the present application. The terms "first", "second", "third" and "fourth" in the specification and claims of this application and the accompanying drawings are used to distinguish different objects, rather than to describe a specific order. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions.

[0248] In the embodiments of the present application, the "indication" mentioned can be a direct indication, an indirect indication, or an indication of an association relationship. For example, A indicates B, which can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association relationship between A and B.

[0249] In the embodiments of the present application, the term "corresponding" may indicate that there is a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship of indication and being indicated, configuration and being configured, etc.

[0250] In the embodiments of the present application, "pre-definition" or "pre-configuration" can be implemented by pre-saving corresponding codes, tables or other methods that can be used to indicate relevant information in a device (for example, including a terminal device and a network device), and the present application does not limit the specific implementation method. For example, pre-definition can refer to what is defined in the protocol.

[0251] In the embodiments of the present application, the “protocol” may refer to a standard protocol in the communication field, for example, it may include an LTE protocol, an NR protocol, and related protocols used in future communication systems, and the present application does not limit this.

[0252] In the embodiments of the present application, determining B based on A does not mean determining B only based on A. B can also be determined based on A and / or other information.

[0253] In the embodiments of the present application, the term "and / or" is only a description of the association relationship of the associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.

[0254] In the embodiments of the present application, the sequence numbers of the above processes do not mean the order of execution. The order of execution 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 the present application.

[0255] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

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

[0257] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0258] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A wireless communication method, characterized in that: include: The terminal device receives first configuration information, where the first configuration information is related to a trigger request of a target system information block SIB1; The terminal device sends a first request to the network device, where the first request is used to request the target SIB1; The terminal device receives the target SIB1 sent by the network device; The first configuration information is used to indicate the transmission resources of the first preamble code and / or the target SIB1 related to the first request.

2. The method according to claim 1, characterized in that The terminal device sending the first request to the network device further includes: The terminal device sends the first request based on contention-free random access CFRA.

3. The method according to claim 1 or 2, characterized in that: The first request includes the first preamble code, and the first preamble code is used for multiple terminal devices to send the first request.

4. The method according to claim 1 or 2, characterized in that: The first request includes the first preamble code, the first preamble code is one of a first preamble code group, and the preamble codes in the first preamble code group are used for multiple terminal devices to send the first request.

5. The method according to claim 4, characterized in that The first preamble code group is one or more of the following: The first preamble group is one of at least two preamble groups used for CFRA, the at least two preamble groups further comprising a second preamble group, the second preamble group being used for a random access procedure; The preamble codes in the first preamble code group are preamble codes reserved by the network device.

6. The method according to claim 5, characterized in that When the first preamble code group includes a preamble code group for CFRA and a reserved preamble code, the first preamble code is determined according to the location information of the terminal device.

7. The method according to any one of claims 1 to 6, characterized in that The sending of the target SIB1 is determined according to a first condition, where the first condition includes one or more of the following: whether the cell corresponding to the network device receives a first type of trigger event; The number of terminal devices sending the first request in the cell corresponding to the network device; The measurement result of the terminal device.

8. The method according to claim 7, characterized in that When the number of terminal devices is greater than a first threshold, the target SIB1 is sent via broadcast; when the number of terminal devices is less than or equal to the first threshold, the target SIB1 is sent via downlink control information.

9. The method according to any one of claims 1 to 8, characterized in that The first configuration information includes one or more of the following: NES-CellId; SIB1-RequestConfig; frequencyInfoUL; pdcch-ConfigSIB1; pdcch-ConfigOD-SIB1-RAR.

10. The method according to any one of claims 1 to 9, characterized in that The transmission resources of the target SIB1 include a first time window for the terminal device to receive the target SIB1, and the first configuration information is also used to indicate the position of the target SIB1 within the first time window, or the position of the target SIB1 within the first time window is determined according to the identification ID of the cell corresponding to the target SIB1.

11. The method according to claim 10, characterized in that The target SIB1 corresponds to a first network energy saving NES cell, and the ID of the first NES cell is used to determine a first offset of the target SIB1 within the first time window.

12. The method according to claim 11, characterized in that The first time window is used to send a plurality of SIB1s including the target SIB1, and the first offset SI offset for: SI offset =(cell ID ×k)mod T; Among them, cell ID is the ID of the first NES cell, k is the interval factor related to the interval of the multiple SIB1s in the first time window, and T is the length of the first time window.

13. The method according to any one of claims 10 to 12, characterized in that: The target SIB1 corresponds to a first NES cell, which is one of multiple NES cells served by the network device, and the network device corresponds to a non-NES cell that communicates with the multiple NES cells. The position of the target SIB1 within the first time window and / or the first interval factor corresponding to the target SIB1 is determined according to the load of the first NES cell.

14. The method according to claim 13, characterized in that The first spacing factor is adjusted according to the load of the first NES cell, and the second spacing factor k after the first spacing factor is adjusted is adjust for: Among them, k initial is the initial interval factor, Q is the real-time load value, Q adjust is the load intermediate value used to adjust the spacing factor, Q max is the maximum load value of the first NES cell.

15. The method according to claim 14, characterized in that When the difference between the second interval factor and the first interval factor is greater than or equal to a second threshold, the second interval factor is used to determine the position of the target SIB1 within the first time window; when the difference between the second interval factor and the first interval factor is less than the second threshold, the first interval factor is used to determine the position of the target SIB1 within the first time window.

16. The method according to any one of claims 13 to 15, characterized in that The first interval factor may also be adjusted according to one or more of the following information: the priority of the first NES cell; The location of the first NES cell within the coverage area of ​​the non-NES cell; The level at which the ID of the first NES cell is located.

17. The method according to any one of claims 1 to 16, characterized in that The target SIB1 corresponds to a first NES cell, and the transmission resources corresponding to the target SIB1 include frequency domain resources corresponding to the first NES cell. The first NES cell is one of multiple NES cells served by the network device, and multiple SIB1s of the multiple NES cells are respectively sent on different frequency domain resources.

18. The method according to claim 17, characterized in that The different frequency domain resources are different bandwidth parts BWP, the first NES cell corresponds to a first BWP, and the first BWP includes dedicated resources for the target SIB1.

19. The method according to any one of claims 1 to 18, characterized in that The target SIB1 corresponds to a first NES cell, the first NES cell is one of a first NES cell group, and multiple SIB1s corresponding to multiple NES cells in the first NES cell group are sent by multiplexing first resources.

20. The method according to any one of claims 1 to 19, characterized in that The target SIB1 corresponds to a first NES cell, the network device corresponds to the first NES cell, or the network device corresponds to a non-NES cell communicating with the first NES cell.

21. A wireless communication method, characterized in that: include: The network device sends first configuration information, where the first configuration information is related to a trigger request of a target system information block SIB1; The network device receives a first request sent by a terminal device, where the first request is used to request the target SIB1; The network device sends the target SIB1 to the terminal device; The first configuration information is used to indicate the transmission resources of the first preamble code and / or the target SIB1 related to the first request.

22. The method according to claim 21, characterized in that The first request is sent based on contention-free random access CFRA.

23. The method according to claim 21 or 22, characterized in that The first request includes the first preamble code, and the first preamble code is used for multiple terminal devices to send the first request.

24. The method according to claim 21 or 22, characterized in that The first request includes the first preamble code, the first preamble code is one of a first preamble code group, and the preamble codes in the first preamble code group are used for multiple terminal devices to send the first request.

25. The method according to claim 24, characterized in that The first preamble code group is one or more of the following: The first preamble group is one of at least two preamble groups used for CFRA, the at least two preamble groups further comprising a second preamble group, the second preamble group being used for a random access procedure; The preamble codes in the first preamble code group are preamble codes reserved by the network device.

26. The method according to claim 25, characterized in that When the first preamble code group includes a preamble code group for CFRA and a reserved preamble code, the first preamble code is determined according to the location information of the terminal device.

27. The method according to any one of claims 21 to 26, characterized in that The sending of the target SIB1 is determined according to a first condition, where the first condition includes one or more of the following: whether the cell corresponding to the network device receives a first type of trigger event; The number of terminal devices sending the first request in the cell corresponding to the network device; The measurement result of the terminal device.

28. The method according to claim 27, characterized in that When the number of terminal devices is greater than a first threshold, the target SIB1 is sent via broadcast; when the number of terminal devices is less than or equal to the first threshold, the target SIB1 is sent via downlink control information.

29. The method according to any one of claims 21 to 28, characterized in that The first configuration information includes one or more of the following: NES-CellId; SIB1-RequestConfig; frequencyInfoUL; pdcch-ConfigSIB1; pdcch-ConfigOD-SIB1-RAR.

30. The method according to any one of claims 21 to 29, characterized in that The transmission resources of the target SIB1 include a first time window for the terminal device to receive the target SIB1, and the first configuration information is also used to indicate the position of the target SIB1 within the first time window, or the position of the target SIB1 within the first time window is determined according to the identification ID of the cell corresponding to the target SIB1.

31. The method according to claim 30, characterized in that The target SIB1 corresponds to a first network energy saving NES cell, and the ID of the first NES cell is used to determine a first offset of the target SIB1 within the first time window.

32. The method according to claim 31, characterized in that The first time window is used to send a plurality of SIB1s including the target SIB1, and the first offset SI offset for: SI offset =(cell ID ×k)mod T; Among them, cell ID is the ID of the first NES cell, k is the interval factor related to the interval of the multiple SIB1s in the first time window, and T is the length of the first time window.

33. The method according to any one of claims 30 to 32, characterized in that The target SIB1 corresponds to a first NES cell, which is one of multiple NES cells served by the network device, and the network device corresponds to a non-NES cell that communicates with the multiple NES cells. The position of the target SIB1 within the first time window and / or the first interval factor corresponding to the target SIB1 is determined according to the load of the first NES cell.

34. The method according to claim 33, characterized in that The first spacing factor is adjusted according to the load of the first NES cell, and the second spacing factor k after the first spacing factor is adjusted is adjust for: Among them, k initial is the initial interval factor, Q is the real-time load value, Q adjust is the load intermediate value used to adjust the spacing factor, Q max is the maximum load value of the first NES cell.

35. The method according to claim 34, characterized in that When the difference between the second interval factor and the first interval factor is greater than or equal to a second threshold, the second interval factor is used to determine the position of the target SIB1 within the first time window; when the difference between the second interval factor and the first interval factor is less than the second threshold, the first interval factor is used to determine the position of the target SIB1 within the first time window.

36. The method according to any one of claims 33 to 35, characterized in that The first interval factor may also be adjusted according to one or more of the following information: the priority of the first NES cell; The location of the first NES cell within the coverage area of ​​the non-NES cell; The level at which the ID of the first NES cell is located.

37. The method according to any one of claims 21 to 36, characterized in that The target SIB1 corresponds to a first NES cell, and the transmission resources corresponding to the target SIB1 include frequency domain resources corresponding to the first NES cell. The first NES cell is one of multiple NES cells served by the network device, and multiple SIB1s of the multiple NES cells are respectively sent on different frequency domain resources.

38. The method according to claim 37, characterized in that The different frequency domain resources are different bandwidth parts BWP, the first NES cell corresponds to a first BWP, and the first BWP includes dedicated resources for the target SIB1.

39. The method according to any one of claims 21 to 38, characterized in that The target SIB1 corresponds to a first NES cell, the first NES cell is one of a first NES cell group, and multiple SIB1s corresponding to multiple NES cells in the first NES cell group are sent by multiplexing first resources.

40. The method according to any one of claims 21 to 39, characterized in that The target SIB1 corresponds to a first NES cell, the network device corresponds to the first NES cell, or the network device corresponds to a non-NES cell communicating with the first NES cell.

41. A terminal device, characterized in that: include: A transceiver unit, configured to receive first configuration information, where the first configuration information is related to a trigger request of a target system information block SIB1; The transceiver unit is further configured to send a first request to the network device, where the first request is configured to request the target SIB1; The transceiver unit is further configured to receive the target SIB1 sent by the network device; The first configuration information is used to indicate the transmission resources of the first preamble code and / or the target SIB1 related to the first request.

42. The terminal device according to claim 41, characterized in that: The transceiver unit is further configured to send the first request based on contention-free random access CFRA.

43. The terminal device according to claim 41 or 42, characterized in that: The first request includes the first preamble code, and the first preamble code is used for multiple terminal devices to send the first request.

44. The terminal device according to claim 41 or 42, characterized in that: The first request includes the first preamble code, the first preamble code is one of a first preamble code group, and the preamble codes in the first preamble code group are used for multiple terminal devices to send the first request.

45. The terminal device according to claim 44, characterized in that: The first preamble code group is one or more of the following: The first preamble group is one of at least two preamble groups used for CFRA, the at least two preamble groups further comprising a second preamble group, the second preamble group being used for a random access procedure; The preamble codes in the first preamble code group are preamble codes reserved by the network device.

46. ​​The terminal device according to claim 45, characterized in that: When the first preamble code group includes a preamble code group for CFRA and a reserved preamble code, the first preamble code is determined according to the location information of the terminal device.

47. The terminal device according to any one of claims 41 to 46, characterized in that: The sending of the target SIB1 is determined according to a first condition, where the first condition includes one or more of the following: whether the cell corresponding to the network device receives a first type of trigger event; The number of terminal devices sending the first request in the cell corresponding to the network device; The measurement result of the terminal device.

48. The terminal device according to claim 47, characterized in that: When the number of terminal devices is greater than a first threshold, the target SIB1 is sent via broadcast; when the number of terminal devices is less than or equal to the first threshold, the target SIB1 is sent via downlink control information.

49. The terminal device according to any one of claims 41 to 48, characterized in that: The first configuration information includes one or more of the following: NES-CellId; SIB1-RequestConfig; frequencyInfoUL; pdcch-ConfigSIB1; pdcch-ConfigOD-SIB1-RAR.

50. The terminal device according to any one of claims 41 to 49, characterized in that: The transmission resources of the target SIB1 include a first time window for the terminal device to receive the target SIB1, and the first configuration information is also used to indicate the position of the target SIB1 within the first time window, or the position of the target SIB1 within the first time window is determined according to the identification ID of the cell corresponding to the target SIB1.

51. The terminal device according to claim 50, characterized in that: The target SIB1 corresponds to a first network energy saving NES cell, and the ID of the first NES cell is used to determine a first offset of the target SIB1 within the first time window.

52. The terminal device according to claim 51, characterized in that: The first time window is used to send a plurality of SIB1s including the target SIB1, and the first offset SI offset for: SI offset =(cell ID ×k)mod T; Among them, cell ID is the ID of the first NES cell, k is the interval factor related to the interval of the multiple SIB1s in the first time window, and T is the length of the first time window.

53. The terminal device according to any one of claims 50-52, characterized in that: The target SIB1 corresponds to a first NES cell, which is one of multiple NES cells served by the network device, and the network device corresponds to a non-NES cell that communicates with the multiple NES cells. The position of the target SIB1 within the first time window and / or the first interval factor corresponding to the target SIB1 is determined according to the load of the first NES cell.

54. The terminal device according to claim 53, characterized in that: The first spacing factor is adjusted according to the load of the first NES cell, and the second spacing factor k after the first spacing factor is adjusted is adjust for: Among them, k initial is the initial interval factor, Q is the real-time load value, Q adjust is the load intermediate value used to adjust the spacing factor, Q max is the maximum load value of the first NES cell.

55. The terminal device according to claim 54, characterized in that: When the difference between the second interval factor and the first interval factor is greater than or equal to a second threshold, the second interval factor is used to determine the position of the target SIB1 within the first time window; when the difference between the second interval factor and the first interval factor is less than the second threshold, the first interval factor is used to determine the position of the target SIB1 within the first time window.

56. The terminal device according to any one of claims 53-55, characterized in that: The first interval factor may also be adjusted according to one or more of the following information: the priority of the first NES cell; The location of the first NES cell within the coverage area of ​​the non-NES cell; The level at which the ID of the first NES cell is located.

57. The terminal device according to any one of claims 41 to 56, characterized in that: The target SIB1 corresponds to a first NES cell, and the transmission resources corresponding to the target SIB1 include frequency domain resources corresponding to the first NES cell. The first NES cell is one of multiple NES cells served by the network device, and multiple SIB1s of the multiple NES cells are respectively sent on different frequency domain resources.

58. The terminal device according to claim 57, characterized in that: The different frequency domain resources are different bandwidth parts BWP, the first NES cell corresponds to a first BWP, and the first BWP includes dedicated resources for the target SIB1.

59. The terminal device according to any one of claims 41 to 58, characterized in that: The target SIB1 corresponds to a first NES cell, the first NES cell is one of a first NES cell group, and multiple SIB1s corresponding to multiple NES cells in the first NES cell group are sent by multiplexing first resources.

60. The terminal device according to any one of claims 41 to 59, characterized in that: The target SIB1 corresponds to a first NES cell, the network device corresponds to the first NES cell, or the network device corresponds to a non-NES cell communicating with the first NES cell.

61. A network device, characterized in that: include: A transceiver unit, configured to send first configuration information, where the first configuration information is related to a trigger request of a target system information block SIB1; The transceiver unit is further configured to receive a first request sent by a terminal device, where the first request is used to request the target SIB1; The transceiver unit is further configured to send the target SIB1 to the terminal device; The first configuration information is used to indicate the transmission resources of the first preamble code and / or the target SIB1 related to the first request.

62. The network device according to claim 61, characterized in that The first request is sent based on contention-free random access CFRA.

63. The network device according to claim 61 or 62, characterized in that: The first request includes the first preamble code, and the first preamble code is used for multiple terminal devices to send the first request.

64. The network device according to claim 61 or 62, characterized in that: The first request includes the first preamble code, the first preamble code is one of a first preamble code group, and the preamble codes in the first preamble code group are used for multiple terminal devices to send the first request.

65. The network device according to claim 64, characterized in that The first preamble code group is one or more of the following: The first preamble group is one of at least two preamble groups used for CFRA, the at least two preamble groups further comprising a second preamble group, the second preamble group being used for a random access procedure; The preamble codes in the first preamble code group are preamble codes reserved by the network device.

66. The network device according to claim 65, characterized in that When the first preamble code group includes a preamble code group for CFRA and a reserved preamble code, the first preamble code is determined according to the location information of the terminal device.

67. The network device according to any one of claims 61 to 66, characterized in that: The sending of the target SIB1 is determined according to a first condition, where the first condition includes one or more of the following: whether the cell corresponding to the network device receives a first type of trigger event; The number of terminal devices sending the first request in the cell corresponding to the network device; The measurement result of the terminal device.

68. The network device according to claim 67, characterized in that When the number of terminal devices is greater than a first threshold, the target SIB1 is sent via broadcast; when the number of terminal devices is less than or equal to the first threshold, the target SIB1 is sent via downlink control information.

69. The network device according to any one of claims 61 to 68, characterized in that: The first configuration information includes one or more of the following: NES-CellId; SIB1-RequestConfig; frequencyInfoUL; pdcch-ConfigSIB1; pdcch-ConfigOD-SIB1-RAR.

70. The network device according to any one of claims 61-69, characterized in that: The transmission resources of the target SIB1 include a first time window for the terminal device to receive the target SIB1, and the first configuration information is also used to indicate the position of the target SIB1 within the first time window, or the position of the target SIB1 within the first time window is determined according to the identification ID of the cell corresponding to the target SIB1.

71. The network device according to claim 70, characterized in that The target SIB1 corresponds to a first network energy saving NES cell, and the ID of the first NES cell is used to determine a first offset of the target SIB1 within the first time window.

72. The network device according to claim 71, characterized in that The first time window is used to send a plurality of SIB1s including the target SIB1, and the first offset SI offset for: SI offset =(cell ID ×k)mod T; Among them, cell ID is the ID of the first NES cell, k is the interval factor related to the interval of the multiple SIB1s in the first time window, and T is the length of the first time window.

73. The network device according to any one of claims 70 to 72, characterized in that: The target SIB1 corresponds to a first NES cell, which is one of multiple NES cells served by the network device, and the network device corresponds to a non-NES cell that communicates with the multiple NES cells. The position of the target SIB1 within the first time window and / or the first interval factor corresponding to the target SIB1 is determined according to the load of the first NES cell.

74. The network device according to claim 73, characterized in that The first spacing factor is adjusted according to the load of the first NES cell, and the second spacing factor k after the first spacing factor is adjusted is adjust for: Among them, k initial is the initial interval factor, Q is the real-time load value, Q adjust is the load intermediate value used to adjust the spacing factor, Q max is the maximum load value of the first NES cell.

75. The network device according to claim 74, characterized in that When the difference between the second interval factor and the first interval factor is greater than or equal to a second threshold, the second interval factor is used to determine the position of the target SIB1 within the first time window; when the difference between the second interval factor and the first interval factor is less than the second threshold, the first interval factor is used to determine the position of the target SIB1 within the first time window.

76. The network device according to any one of claims 73-75, characterized in that: The first interval factor may also be adjusted according to one or more of the following information: the priority of the first NES cell; The location of the first NES cell within the coverage area of ​​the non-NES cell; The level at which the ID of the first NES cell is located.

77. The network device according to any one of claims 61-76, characterized in that: The target SIB1 corresponds to a first NES cell, and the transmission resources corresponding to the target SIB1 include frequency domain resources corresponding to the first NES cell. The first NES cell is one of multiple NES cells served by the network device, and multiple SIB1s of the multiple NES cells are respectively sent on different frequency domain resources.

78. The network device according to claim 77, characterized in that The different frequency domain resources are different bandwidth parts BWP, the first NES cell corresponds to a first BWP, and the first BWP includes dedicated resources for the target SIB1.

79. The network device according to any one of claims 61 to 78, characterized in that: The target SIB1 corresponds to a first NES cell, the first NES cell is one of a first NES cell group, and multiple SIB1s corresponding to multiple NES cells in the first NES cell group are sent by multiplexing first resources.

80. The network device according to any one of claims 61-79, characterized in that: The target SIB1 corresponds to a first NES cell, the network device corresponds to the first NES cell, or the network device corresponds to a non-NES cell communicating with the first NES cell.

81. A communication device, characterized in that: The invention comprises a memory and a processor, wherein the memory is used to store a program, and the processor is used to call the program in the memory to execute the method according to any one of claims 1 to 40.

82. A device, characterized in that The invention comprises a processor, which is used to call a program from a memory to execute the method according to any one of claims 1 to 40.

83. A chip, characterized in that: It comprises a processor, which is used to call a program from a memory, so that a device equipped with the chip executes a method as claimed in any one of claims 1 to 40.

84. A computer-readable storage medium, characterized in that A program is stored thereon, the program causing a computer to execute the method according to any one of claims 1 to 40.

85. A computer program product, characterized in that The method comprises a program which causes a computer to execute the method according to any one of claims 1 to 40.

86. A computer program, characterized in that The computer program causes a computer to execute the method according to any one of claims 1 to 40.

Images