Communication method and communication device

Abstract

Provided are a communication method and a communication device. The method comprises: a first terminal device executes cell selection or reselection, wherein the cell selection or reselection is associated with a first event, and the first event comprises one or more of the following: the first terminal device detects a radio link failure; the first terminal device executes RRC reestablishment, and the first terminal device enters an RRC idle state.

Description

Communication methods and communication equipment Technical Field

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

[0002] Terminal devices can perform cell selection or reselection to choose a suitable cell for communication. With the development of technology, network energy saving (NES) technology has become a research hotspot; however, related technologies have not considered the impact of NES technology on the cell selection or reselection process. Summary of the Invention

[0003] This application provides a communication method and a communication device. The various aspects covered by this application are described below.

[0004] In a first aspect, a communication method is provided, comprising: a first terminal device performing cell selection or reselection; wherein the cell selection or reselection is associated with a first event, the first event including one or more of the following: the first terminal device detects a radio link failure; the first terminal device performs radio resource control (RRC) reconstruction; the first terminal device transitions from an RRC connected state to an RRC idle state; the first terminal device enters an RRC idle state.

[0005] In a second aspect, a communication method is provided, comprising: a first terminal device receiving one or more of the following: first wake-up signal (WUS) configuration information; a first system information block (SIB), wherein the first SIB is used to carry the first WUS configuration information; and SIB1 of a first cell.

[0006] Thirdly, a communication method is provided, comprising: a network device sending one or more of the following: first WUS configuration information; a first SIB, wherein the first SIB is used to carry the first WUS configuration information; and SIB1 of a first cell.

[0007] Fourthly, a communication device is provided, the communication device being a first terminal device, the first terminal device comprising: a processing unit configured to perform cell selection or reselection; wherein the cell selection or reselection is associated with a first event, the first event including one or more of the following: the first terminal device detects a radio link failure; the first terminal device performs RRC reconstruction; the first terminal device transitions from an RRC connected state to an RRC idle state; the first terminal device enters an RRC idle state.

[0008] Fifthly, a communication device is provided, the communication device being a first terminal device, the first terminal device comprising: a communication unit for receiving one or more of the following: first WUS configuration information; a first SIB, the first SIB being used to carry the first WUS configuration information; and SIB1 of a first cell.

[0009] In a sixth aspect, a communication device is provided, the communication device being a network device, the network device comprising: a communication unit for transmitting one or more of the following: first WUS configuration information; a first SIB, the first SIB being used to carry the first WUS configuration information; and an SIB1 of a first cell.

[0010] A seventh aspect provides a communication device including a transceiver, a memory, and a processor, wherein the memory is used to store a program, the processor is used to invoke the program in the memory, and to control the transceiver to receive or transmit signals so that the communication device performs the method as described in the first aspect, the second aspect, or the third aspect.

[0011] Eighth aspect, an apparatus is provided, including a processor for calling a program from a memory to cause the apparatus to perform the method as described in the first, second, or third aspect.

[0012] A ninth aspect provides a chip including a processor for calling a program from memory, causing a device having the chip mounted to perform the method as described in the first, second, or third aspect.

[0013] A tenth aspect provides a computer-readable storage medium having a program stored thereon that causes a computer to perform the methods described in the first, second, or third aspects.

[0014] Eleventhly, a computer program product is provided, including a program that causes a computer to perform the methods described in the first, second, or third aspects.

[0015] In a twelfth aspect, a computer program is provided that causes a computer to perform the methods described in the first, second, or third aspects. Attached Figure Description

[0016] Figure 1 is an example architecture diagram of a wireless communication system to which embodiments of this application can be applied.

[0017] Figure 2 is a flowchart illustrating a communication method provided in one embodiment of this application.

[0018] Figure 3 is a flowchart illustrating a communication method provided in another embodiment of this application.

[0019] Figure 4 is a flowchart illustrating a communication method provided in another embodiment of this application.

[0020] Figure 5 is a flowchart illustrating a communication method provided in another embodiment of this application.

[0021] Figure 6 is a schematic diagram of the structure of a communication device provided in one embodiment of this application.

[0022] Figure 7 is a schematic diagram of the structure of a communication device provided in another embodiment of this application.

[0023] Figure 8 is a schematic diagram of the structure of a communication device provided in another embodiment of this application.

[0024] Figure 9 is a schematic diagram of a device applicable to embodiments of this application. Detailed Implementation

[0025] The technical solutions in this application will now be described with reference to the accompanying drawings. For ease of understanding, the communication terms and processes that may be involved in the embodiments of this application will first be introduced with reference to Figures 1 to 9.

[0026] Communication system

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

[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 support not only traditional cellular communication but also one or more other types of communication. For example, a communication system can support one or more of the following communication methods: device-to-device (D2D) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), enhanced machine-type communication (eMTC), vehicle-to-vehicle (V2V) communication, and vehicle-to-everything (V2X) communication. The embodiments of this application can also be applied to communication systems that support the above-mentioned communication methods.

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

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

[0031] The technical solutions of this application embodiment can be applied to various Internet of Things (IoT) communication systems. For example, this technical solution can be applied to narrowband Internet of Things (NB-IoT) communication systems. As another example, this technical solution can be applied to ambient IoT (AIoT) communication systems.

[0032] Figure 1 illustrates an example system architecture of a communication system 100 applicable to embodiments of this application. The 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 can provide network coverage for a specific geographical area and can communicate with the terminal device 120 located within that coverage area. The terminal device 120 can access a network (such as a wireless network) through the network device 110. Optionally, the wireless communication system 100 may also include other network entities such as a network controller and a mobility management entity; this embodiment of the application does not limit this.

[0033] The terminal device in this application embodiment can 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 device, user agent, or user device. The terminal device in this application embodiment can be a device that provides voice and / or data connectivity to a user, and can be used to connect people, objects, and machines, such as a handheld device with wireless connectivity, vehicle-mounted device, etc. The terminal devices in the embodiments of this application can be mobile phones, tablets, laptops, PDAs, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, self-driving, remote medical surgery, smart grids, transportation safety, smart cities, and smart homes, etc. Optionally, the terminal device can act as a base station. For example, the terminal device can act as a scheduling entity, providing sidelink signals between terminal devices in vehicle-to-everything (V2X) or device-to-device (D2D) systems. For instance, cellular phones and cars communicate with each other using sidelink signals. Cellular phones and smart home devices communicate without relaying communication signals through base stations.

[0034] In some embodiments, the terminal device may also be a device in AIoT (such as a reader) to meet the needs of certain scenarios.

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

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

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

[0038] Network devices and terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can also be deployed in the air on airplanes, balloons, and satellites. This application does not limit the scenario in which the network devices and terminal devices are located.

[0039] It should be understood that all or part of the functions of the communication device in this application can also be implemented by software functions running on hardware, or by virtualization functions instantiated on a platform such as a cloud platform.

[0040] Figure 1 illustrates an exemplary network device 110 and two terminal devices 120. Optionally, the communication system 100 may include multiple network devices 110, and the communication system 100 may also include other numbers of terminal devices 120.

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

[0042] The preceding text has provided a detailed introduction to communication systems. Currently, the main application scenarios of communication systems (such as 5G) can include enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), and massive machine-type communication (mMTC).

[0043] eMBB can be applied to scenarios where users access multimedia content, services, and data, and its demand is growing rapidly. Furthermore, because eMBB may be deployed in different environments, such as indoors, urban areas, and rural areas, the capabilities and requirements for eMBB vary significantly across these environments.

[0044] URLLC can be applied to scenarios such as industrial automation, power automation, remote medical operations (surgery), and traffic safety assurance. Typical characteristics of mMTC include: high connection density, small data volume, latency-insensitive services, low module cost, and long service life.

[0045] Terminal devices in a communication system may have different radio resource control (RRC) states, and the communication system can perform mobility management on the terminal devices based on their RRC states. The following section introduces the RRC states of terminal devices and their mobility management methods.

[0046] Currently, the protocol defines three RRC states for terminal devices: RRC connected, RRC idle, and RRC inactive.

[0047] The RRC connected state refers to the state a terminal device is in after completing a random access procedure but before releasing the RRC. An RRC connection exists between the terminal device and a network device (e.g., an access network device). In the RRC connected state, the terminal device can transmit data with the network device, such as downlink and / or uplink data transmission. Alternatively, the terminal device can also transmit terminal-specific data and / or control channels with the network device to transmit specific information or unicast information.

[0048] In RRC connected mode, network devices can determine the cell-level location information of terminal devices, meaning they can identify the cell to which the terminal device belongs. When a terminal device moves in RRC connected mode, such as from one cell to another, the network device can control the terminal device to perform a cell handover. Therefore, mobility management for terminal devices in RRC connected mode can include cell handover. Furthermore, mobility management for terminal devices in RRC connected mode can be controlled by the network device, allowing the terminal device to handover to a designated cell according to instructions issued by the network device.

[0049] RRC idle state refers to the state of a terminal device when it is camped in a cell but has not yet performed random access. The terminal device typically enters the RRC idle state after powering on or after RRC release. In the RRC idle state, there is no RRC connection between the terminal device and network devices (e.g., the camped network device), the network device does not store the terminal device's context, and no connection has been established between the network device and the core network for that terminal device. If the terminal device needs to transition from the RRC idle state to the RRC connected state, it must initiate an RRC connection establishment process.

[0050] In RRC idle state, the core network (CN) can send paging messages to the terminal device; that is, the paging process can be triggered by the CN. Optionally, the paging area can also be configured by the CN. In some cases, for a terminal device in RRC idle state, when the terminal device moves its location (e.g., from one cell to another), the terminal device can initiate a cell reselection process. In other cases, for a terminal device in RRC idle state, when the terminal device needs to access a cell, the terminal device can initiate a cell selection process. In other words, mobility management of a terminal device in RRC idle state can include cell reselection and / or cell selection.

[0051] The RRC inactive state is a state defined to reduce air interface signaling, quickly restore radio connectivity, and quickly restore data services. The RRC inactive state is a state between the connected state and the idle state. The terminal device had previously entered the RRC connected state and then released the RRC connection with the network device, but the network device retained the terminal device's context. Furthermore, the connection established between the network device and the core network for this terminal device was not released; that is, the user plane bearer and control plane bearer between the RAN and CN are still maintained, i.e., a CN-NR connection exists.

[0052] In the RRC inactive state, the RAN can send paging messages to the terminal device, meaning the paging process can be triggered by the RAN. RAN-based paging areas are managed by the RAN, and network devices can determine the location of the terminal device at the RAN paging area level.

[0053] In some cases, for a terminal device in RRC inactive state, when the terminal device moves its location (e.g., from one cell to another), the terminal device can initiate a cell reselection procedure. In other cases, for a terminal device in RRC inactive state, when the terminal device needs to access a cell, the terminal device can initiate a cell selection procedure. In other words, mobility management of a terminal device in RRC inactive state can include cell reselection and / or cell selection.

[0054] With the rapid development of technology, energy consumption has become a significant component of operators' operating costs. According to a report by the Global System for Mobile Communications Association (GSMA), energy costs for mobile networks account for approximately 23% of operators' total costs. The majority of energy consumption comes from radio access networks, particularly active antenna units (AAUs), while data centers and fiber optic transmission account for only a smaller share.

[0055] Energy consumption includes two types: dynamic components, such as energy consumption during data transmission / reception; and static components, such as energy consumption to maintain the operation of necessary wireless access devices (even when there is no continuous data transmission / reception).

[0056] Therefore, related technologies propose network energy saving (NES) projects. These projects should not only assess potential network energy consumption but also evaluate and balance the impact on network and user performance. For example, the project should not have a particularly large impact on certain key performance indicators (KPIs). These KPIs include spectral efficiency, capacity, user-perceived throughput (UPT), latency, terminal device power consumption, complexity, handover performance, call drop rate, and initial access performance.

[0057] Potential research directions for this project include defining procedures and signaling methods for terminal devices in connected mode and configured with carrier aggregation (CA), including intra-frequency / inter-frequency CA, to support on-demand SSB secondary scell (SCell) operation. For example, defining triggering methods for SSB transmission (selected from uplink wake-up signal (WUS), backhaul cell on / off indication, and secondary cell activation / deactivation signaling).

[0058] Furthermore, potential research directions for this project may include researching processes and signaling methods for idle / inactive terminal devices to support on-demand transmission of system information block 1 (SIB1). Specifically, this could include one or more of the following: a method for triggering an uplink wake-up signal; configuration information for the wake-up signal provided to the terminal device; and information exchange between network devices (at least exchanging configuration information for the wake-up signal).

[0059] Potential research directions for this project include: defining adaptive techniques for general signal / channel transmission. For example, time-domain adaptation of the physical random access channel (PRACH); spatial-domain adaptation of PRACH; and adaptation of paging timing.

[0060] Related technologies propose that terminal devices can request SIB1 from on-demand SIB1 cells based on WUS configuration information. The application of these technologies may affect the cell selection process, especially the cell selection process triggered by radio link failure (RLF). However, these technologies do not address this point, which may lead to difficulties in the cell selection process or reduce its efficiency.

[0061] To address the aforementioned issues, the embodiments of this application will be described in detail below.

[0062] Figure 2 is a flowchart illustrating a communication method provided in one embodiment of this application. The method in Figure 2 can be executed by a first terminal device, which can be any type of terminal device mentioned in Figure 1.

[0063] Referring to Figure 2, in step S210, the first terminal device performs cell selection or reselection. Before or during the cell selection or reselection, the first terminal device may be in RRC connected state. The cell selection or reselection may be triggered by or associated with a first event. The first event mentioned here may include one or more of the following: the first terminal device detects a radio link failure, the first terminal device performs RRC reconstruction, the first terminal device transitions from RRC connected state to RRC idle state, and the first terminal device enters RRC idle state.

[0064] For example, the cell selection or reselection mentioned in step S210 can be a cell selection or reselection in the following scenario: the first terminal device in the RRC connected state detects or experiences an RLF, and the first terminal device performs RRC reconstruction or sends an RRC connection establishment request. During the above RRC reconstruction process, the first terminal device may be in one of the following states: access stratum (AS) security is active; or, AS security is active and signalalling radio bearer (SRB) 2 and at least one data radio bearer (DRB) have been established.

[0065] For example, the cell selection or reselection mentioned in step S210 can be a cell selection or reselection in the following scenario: the first terminal device in the RRC connected state transitions to the RRC idle state, or the first terminal device enters the RRC idle state. In this RRC idle state, the AS security of the first terminal device is not activated; or, the AS security is activated, but SRB2 and at least one DRB are not established.

[0066] During cell selection or reselection, the first terminal device may select or reselect a cell according to cell selection rules (such as the S criterion) provided by relevant technologies. Alternatively, in some implementations, the first terminal device may also perform cell selection or reselection based on first information. The first information may include one or more of the following: first WUS configuration information (which may refer to WUS configuration information previously acquired by the first terminal device and / or WUS configuration information currently stored by the first terminal device), channel quality information of the cell, and cell type (such as whether it is an NES cell).

[0067] For example, the first terminal device may preferentially select or search for the cell corresponding to the first WUS configuration information. The cell corresponding to the first WUS configuration information may refer to a cell that can use the first WUS configuration information. For example, if the first terminal device can request SIB1 of a certain cell based on the first WUS configuration information, then that cell can be understood as the cell corresponding to the first WUS configuration information. The first terminal device mentioned here may be a terminal device that satisfies one or more of the following: supports requesting common signals or channels, supports NES, and has WUS configuration information. That is, if the first terminal device is a terminal device that supports requesting common signals or channels, and / or a terminal device that supports NES, and / or a terminal device that has WUS configuration information, then the first terminal device may preferentially select or search for the cell corresponding to the first WUS configuration information.

[0068] For example, the first terminal device can perform cell selection or reselection based on a first priority. This first priority is the priority of cell selection, cell reselection, or cell search, and is determined based on the first WUS configuration information. For instance, if a cell corresponds to the cell specified in the first WUS configuration information, the priority of cell selection, cell reselection, or cell search for that cell can be increased. The first terminal device mentioned here can be, for example, a terminal device that satisfies one or more of the following: supports requesting a common signal or channel, supports NES, and has WUS configuration information. That is, if the first terminal device is a terminal device that supports requesting a common signal or channel, and / or a terminal device that supports NES, and / or a terminal device that has WUS configuration information, then the first terminal device can perform cell selection or reselection based on the first priority.

[0069] For example, the first terminal device may preferentially select or search for cells of a first type. This first type of cell may include one or more of the following: normal cells, cells periodically transmitting SIB1, cells periodically transmitting SSB, cells that do not support NES, NES cells broadcasting SIB1, and NES cells broadcasting SSB. The first terminal device mentioned here may, for example, be a terminal device that meets one or more of the following criteria: does not support requesting a common signal or channel, does not support NES, and does not have WUS configuration information. That is, if the first terminal device is a terminal device that does not support requesting a common signal or channel, and / or, does not support NES, and / or, does not have WUS configuration information, then the first terminal device may preferentially select or search for cells of the first type.

[0070] For example, the first terminal device can select a group of cells based on the channel quality information of the cells, and then select a cell from that group of cells based on the first WUS configuration information. This cell could be, for example, an NES cell, a cell supporting on-demand SIB1 requests, or a cell corresponding to the first WUS configuration information. By comprehensively considering the channel quality and WUS configuration information of the cells, the first terminal device can perform cell selection or reselection more rationally, thereby improving the efficiency of cell selection or reselection.

[0071] For example, the first terminal device can select a group of cells based on the first WUS configuration information. This group of cells consists entirely of NES cells, supporting on-demand requests for SIB1 cells or cells corresponding to the first WUS configuration information. Then, the first terminal device can select a cell from the cell's channel quality information. This cell could, for example, be the one with the best channel quality in the group. By comprehensively considering the cell's channel quality and WUS configuration information, the first terminal device can perform cell selection or reselection more rationally, thereby improving the efficiency of cell selection or reselection.

[0072] During or after the cell selection or reselection process, the first terminal device may request, not request, or determine whether to request the first cell to send SIB1. The first cell mentioned here may be a cell involved in the cell selection or reselection process, such as a cell selected by the first terminal device based on the cell selection or reselection process, or a cell that the first terminal device expects to select during the cell selection or reselection process.

[0073] For example, while the first terminal device is performing cell selection or reselection, the first terminal device requests, does not request, or determines whether to request the first cell to send SIB1.

[0074] For example, when the first terminal device selects the first cell based on cell selection or reselection, the first terminal device requests, does not request, or determines whether to request the first cell to send SIB1.

[0075] For example, if the first terminal device expects to select the first cell based on cell selection or reselection, the first terminal device may request, not request, or determine whether to request the first cell to send SIB1.

[0076] The decision to request, not request, or request the first cell to send SIB1, mentioned above, can be determined based on certain information (hereinafter referred to as the second information). This second information may include one or more of the following: the type of the first cell, and whether the first terminal device has first WUS configuration information (which may or may not include the WUS configuration information corresponding to the first cell).

[0077] For example, if the first cell is a first type of cell, the first terminal device may not request or is certain not to request the first cell to send SIB1; or, the first terminal device may consider that it has already obtained SIB1 (such as the SIB1 of the first cell). The first type of cell includes one or more of the following: a normal cell (or cell A), a cell that periodically sends SIB1, a cell that periodically sends SSB, a cell that does not support NES, an NES cell that is broadcasting SIB1, and an NES cell that is broadcasting SSB. Further, in one embodiment, the first terminal device can obtain SIB1 from the broadcast message of the first cell.

[0078] For example, if the first cell is an NES cell (or a cell that requests SIB1 on demand, or a cell that does not periodically send SIB1), and the first terminal device does not have the first WUS configuration information, then the first terminal device does not request or determines not to request the first cell to send SIB1. Further, in one embodiment, the first terminal device may perform one or more of the following operations: continue performing cell selection or reselection, determine that the stored WUS configuration information is valid, and continue using the stored WUS configuration information.

[0079] For example, if the first cell is an NES cell (or a cell that requests SIB1 on demand, or a cell that does not periodically send SIB1), and the first terminal device does not contain WUS configuration information corresponding to the first cell, then the first terminal device does not request or determines not to request the first cell to send SIB1. Further, in one embodiment, the first terminal device may perform one or more of the following operations: continue performing cell selection or reselection, determine that the stored WUS configuration information is valid, and continue using the stored WUS configuration information.

[0080] For example, if the first cell is an NES cell (or a cell that requests SIB1 on demand, or a cell that does not periodically send SIB1), and the first terminal device has the first WUS configuration information, then the first terminal device requests or confirms that the first cell sends SIB1.

[0081] For example, if the first cell is an NES cell (or a cell that requests SIB1 on demand, or a cell that does not periodically send SIB1), and the first terminal device does not contain the WUS configuration information corresponding to the first cell, then the first terminal device requests or confirms that the first cell sends SIB1.

[0082] During cell selection or reselection, in some implementations, the first terminal device may perform one or more of the following actions: the first terminal device deletes previously received or saved first WUS configuration information; the first terminal device releases previously received or saved first WUS configuration information; the first terminal device determines that previously received or saved first WUS configuration information is invalid; the first terminal device deletes previously received or saved first SIB; the first terminal device releases previously received or saved first SIB; the first terminal device determines that previously received or saved first SIB is invalid. Here, the first SIB mentioned above can refer to the SIB used to carry the WUS configuration information. This first SIB can be any SIB other than SIB1; in some implementations, the first SIB can be referred to as SIB-X.

[0083] Furthermore, in one embodiment, the above operation may be performed under certain conditions (hereinafter referred to as the first condition). That is, when the first condition is met, the first terminal device performs the above deletion or release operation. The first condition may include one or more of the following: the first terminal device camps on a cell based on cell selection or reselection; the first terminal device determines (or considers) a cell as an available cell based on cell selection or reselection; the cell selection or reselection is not the first cell selection or reselection performed by the first terminal device after obtaining the first WUS configuration information; the cell selection or reselection is not the first cell selection or reselection performed by the first terminal device after obtaining the first WUS configuration information from the camped cell; the cell selection or reselection is triggered based on RRC reconstruction; the first timer of the first terminal device (the first timer is used for RRC reconstruction and is triggered based on the first terminal device detecting a radio link failure, and the first timer may be, for example, a T311 timer) times out or stops; the second timer of the first terminal device (the second timer is used for the RRC reconstruction process and is triggered based on the RRC connection reconstruction request sent by the first terminal device, and the timer may be, for example, a T301 timer) times out or stops; the third timer of the first terminal device (the third timer is used for RRC connection establishment and is triggered based on the RRC connection establishment request sent by the first terminal device, and the timer may be, for example, a T300 timer) times out or stops.

[0084] For example, if the first terminal device camps on a cell based on cell selection or reselection, or if the first terminal device determines (or considers) a cell to be an available cell based on cell selection or reselection, then the first terminal device deletes the previously received or saved first WUS configuration information, or releases the previously received or saved first WUS configuration information, or determines that the previously received or saved first WUS configuration information is invalid, or deletes the previously received or saved first SIB, or releases the previously received or saved first SIB, or determines that the previously received or saved first SIB is invalid.

[0085] For example, if the cell selection or reselection is not the first cell selection or reselection performed after the first terminal device obtains the first WUS configuration information, or if the cell selection or reselection is not the first cell selection or reselection performed after the first terminal device obtains the first WUS configuration information from the camped cell, then the first terminal device deletes the previously received or saved first WUS configuration information, or releases the previously received or saved first WUS configuration information, or determines that the previously received or saved first WUS configuration information is invalid, or deletes the previously received or saved first SIB, or releases the previously received or saved first SIB, or determines that the previously received or saved first SIB is invalid. In other words, the first terminal device considers the WUS configuration information to be valid only in the first cell selection or reselection process after the first terminal device obtains the WUS configuration information.

[0086] For example, if the first terminal device is performing an RRC rebuild and / or the first timer (such as T311) is running, the first terminal device determines (or believes) that if the first timer times out or stops, the previously received or saved first WUS configuration information is invalid.

[0087] For example, if the first terminal device is performing an RRC rebuild and / or the second timer (such as T301) is running, the first terminal device determines (or believes) that if the second timer times out or stops, the previously received or saved first WUS configuration information is invalid.

[0088] For example, if the first terminal device is performing RRC establishment and / or the third timer (such as T300) is running, the first terminal device determines (or believes) that if the third timer times out or stops, the first WUS configuration information previously received or saved is invalid.

[0089] During the cell selection or reselection process, in some implementations, the first terminal device may perform one or more of the following: determine that the first WUS configuration information previously received or stored by the first terminal device is valid, or not release the first WUS configuration information.

[0090] Furthermore, in one embodiment, the above operation may be performed under certain conditions (hereinafter referred to as the second condition). That is, when the second condition is met, the first terminal device determines that the previously received or stored first WUS configuration information is valid, or does not release the first WUS configuration information. The second condition may include one or more of the following: the cell selection or reselection is the first cell selection or reselection performed after the first terminal device obtains the first WUS configuration information; the WUS configuration is obtained or saved before the current cell selection or reselection process is performed by the first terminal device; the first timer of the first terminal device (the first timer is used for RRC reconstruction and is triggered based on the first terminal device detecting a radio link failure, and the first timer may be, for example, a T311 timer) has not timed out or stopped; the second timer of the first terminal device (the second timer is used for the RRC reconstruction process and is triggered based on the RRC connection reconstruction request sent by the first terminal device, and the timer may be, for example, a T301 timer) has not timed out or stopped; the third timer of the first terminal device (the third timer is used for RRC connection establishment and is triggered based on the RRC connection establishment request sent by the first terminal device, and the timer may be, for example, a T300 timer) has not timed out or stopped.

[0091] For example, if the cell selection or reselection is the first cell selection or reselection performed by the first terminal device after acquiring the first WUS configuration information, or if the cell selection or reselection is the first cell selection or reselection performed by the first terminal device after acquiring the first WUS configuration information from the camped cell, then the first terminal device may perform one or more of the following: determine that the first WUS configuration information previously received or stored by the first terminal device is valid, or not release the first WUS configuration information. In other words, the first terminal device considers the WUS configuration information to be valid only in the first cell selection or reselection process after the first terminal device acquires the WUS configuration information.

[0092] For example, if the first terminal device is performing an RRC rebuild and / or the first timer (such as T311) is running, the first terminal device determines (or considers) that the first WUS configuration information previously received or saved is valid before the first timer expires or stops.

[0093] For example, if the first terminal device is performing an RRC rebuild and / or the second timer (such as T301) is running, the first terminal device determines (or considers) that the first WUS configuration information previously received or saved is valid before the second timer expires or stops.

[0094] For example, if the first terminal device is performing RRC establishment and / or the third timer (such as T300) is running, the first terminal device determines (or considers) that the first WUS configuration information previously received or saved is valid before the third timer expires or stops.

[0095] As mentioned earlier, the cell selection or reselection mentioned in Figure 2 can be the cell selection or reselection associated with the RRC reconstruction process. In some implementations, if RRC reconstruction fails, the first terminal device can obtain a second SIB (the second SIB can be used to carry WUS configuration information, and this second SIB can be any SIB other than SIB1; in some cases, the second SIB can be referred to as SIB-X) according to the first process. This first process can correspond to the terminal device in the RRC disconnected state (RRC idle state and / or RRC inactive state).

[0096] In some implementations, if RRC reconstruction is successful, the first terminal device obtains the second SIB according to either the second process or the first process. The first process mentioned here can be found in the description above. The second process mentioned here can correspond to the terminal device in the RRC connected state.

[0097] In some implementations, without conflict, the first terminal device mentioned in the preceding embodiments can be in RRC connected state before performing cell selection or reselection, or when performing cell selection or reselection. That is, the embodiment corresponding to Figure 2 can be applied to the cell selection or reselection process of a terminal device in connected state.

[0098] In some implementations, without conflict, the first terminal device mentioned in the preceding embodiments has valid first WUS configuration information or a first SIB before performing cell selection or reselection; or, the first terminal device receives updated first WUS configuration information or a first SIB before performing cell selection or reselection; or, the first terminal device obtains the first WUS configuration information or a first SIB for the first time before performing cell selection or reselection. The first SIB mentioned here can be used to carry WUS configuration information, such as the first WUS configuration information mentioned above.

[0099] The embodiments of this application are described in more detail below with specific examples. In the examples below, the first terminal device mentioned above is referred to as UE, and the SIB used to carry WUS configuration information is referred to as SIB-X. It should be noted that the examples below are only for the purpose of helping those skilled in the art to understand the embodiments of this application, and are not intended to limit the embodiments of this application to the specific values ​​or specific scenarios illustrated. Those skilled in the art can obviously make various equivalent modifications or changes based on the examples given, and such modifications or changes also fall within the scope of the embodiments of this application.

[0100] Example 1

[0101] Related technologies mention that on-demand SIB1 cells (or NES cells) do not send SIB1; idle-state UEs need to send a UL WUS request to obtain the SIB1 of the NES cell. However, connected-state UEs use WUS configuration information, and the details of requesting SIB1 are unclear. The following, with reference to Example 1, describes how connected-state UEs use WUS configuration information to request SIB1 during cell selection or reselection.

[0102] The UE performs cell selection or reselection. Optionally, at least one of the following may be included:

[0103] 1) Scenarios involving cell selection or reselection may include at least one of the following:

[0104] • When a connected UE detects or a radio link failure occurs, it performs an RRC reconstruction (e.g., in the case of AS security activation, or in the case of AS security activation and SRB2 and at least one DRB established), or sends an RRC connection establishment request.

[0105] • Connected UE transitions to RRC idle state. For example, if AS security is not activated, or if AS security is activated but SRB2 and at least one DRB are not established, the connected UE transitions to RRC idle state.

[0106] 2) The UE performs cell selection or reselection. For example, this may include the following optional aspects:

[0107] a) Preferred selection of communities

[0108] i. Method 1: Select cells according to the cell selection rules provided by relevant technologies;

[0109] ii. Method 2: Select cells based on WUS configuration information and / or channel quality.

[0110] For example, the UE prioritizes selecting or searching for cells corresponding to the WUS configuration information. Alternatively, the UE increases the priority of cell selection, cell reselection, or cell search for cells corresponding to the WUS configuration information. Furthermore, the above operations are performed when the UE is an NES UE, or when the UE has WUS configuration information.

[0111] For example, the UE may prioritize selecting a normal cell, or a cell that transmits SIB1 / SSB periodically, or a non-energy-saving cell. Furthermore, the above operations are performed when the UE is a non-NES UE, or when the UE does not have WUS configuration information.

[0112] b) Should SIB1 be requested?

[0113] i. If the cell selected by the UE is Cell A (i.e., a normal cell, or a cell that preferentially selects SIB1 / SSB periodically), or is an NES cell that is broadcasting SIB1 / SSB, then the UE does not need to request SIB1, and can directly obtain the SIB1 broadcast by that cell.

[0114] Optionally, if the UE camps on the cell, or the UE considers the cell to be an available cell, the UE deletes the previously acquired or saved WUS configuration information, or the UE deletes the SIB-X corresponding to the previously acquired or saved WUS, or the UE considers the previously acquired or saved WUS configuration information invalid, or the UE considers the previously acquired or saved SIB-X corresponding to the previously acquired or saved WUS to be invalid.

[0115] Optionally, the UE considers the WUS configuration information to be valid only in the first cell selection or reselection after the UE acquired the WUS configuration.

[0116] Optionally, if the UE is performing an RRC reconstruction process and / or T311 is running, the WUS configuration information is valid before the UE considers T311 to have timed out or stopped, or before it considers T301 to have timed out or stopped.

[0117] Optionally, if the UE performs an RRC reconstruction procedure and / or T311 is enabled, the UE releases the WUS configuration information. For example, the UE releases the WUS configuration information in one of the following situations: T311 times out or stops, or T301 times out or stops.

[0118] Optionally, if the UE performs the RRC establishment procedure and / or T300 is enabled, the UE considers the WUS configuration information invalid.

[0119] ii. If the cell selected by the UE is an NES cell and the UE does not have WUS configuration information, or the UE does not have WUS configuration information for the cell, then the UE continues the cell selection or reselection process.

[0120] Optionally, if the UE camps on a cell based on the cell selection or reselection process, or if the UE considers a cell to be an available cell, then the UE deletes the previously acquired or saved WUS configuration information, or deletes the SIB-X corresponding to the previously acquired or saved WUS, or considers the previously acquired or saved WUS configuration information invalid, or considers the previously acquired or saved SIB-X corresponding to the previously acquired or saved WUS to be invalid.

[0121] Optionally, the UE considers the WUS configuration information to be valid only in the first cell selection or reselection after the UE acquired the WUS configuration.

[0122] Optionally, if the UE is performing an RRC reconstruction process and / or T311 is running, the WUS configuration information is valid before the UE considers T311 to have timed out or stopped, or before it considers T301 to have timed out or stopped.

[0123] Optionally, if the UE performs an RRC reconstruction procedure and / or T311 is enabled, the UE releases the WUS configuration information. For example, the UE releases the WUS configuration information in one of the following situations: T311 times out or stops, or T301 times out or stops.

[0124] Optionally, if the UE performs the RRC establishment procedure and / or T300 is enabled, the UE considers the WUS configuration information invalid.

[0125] iii. If the cell selected by the UE is an NES cell (i.e., OD-SIB1 cell, or the cell does not periodically send SIB1), and the UE has WUS configuration information, or the UE has WUS configuration information for the cell, then the UE sends an OD-SIB1 request to obtain SIB1.

[0126] Optionally, if the UE camps on a cell based on the cell selection or reselection process, or if the UE considers a cell to be an available cell, then the UE deletes the previously acquired or saved WUS configuration information, or deletes the SIB-X corresponding to the previously acquired or saved WUS, or considers the previously acquired or saved WUS configuration information invalid, or considers the previously acquired or saved SIB-X corresponding to the previously acquired or saved WUS to be invalid.

[0127] Optionally, the UE considers the WUS configuration information to be valid only in the first cell selection or reselection after the UE acquired the WUS configuration.

[0128] Optionally, if the UE is performing an RRC reconstruction process and / or T311 is running, the WUS configuration information is valid before the UE considers T311 to have timed out or stopped, or before it considers T301 to have timed out or stopped.

[0129] Optionally, if the UE performs an RRC reconstruction procedure and / or T311 is enabled, the UE releases the WUS configuration information. For example, the UE releases the WUS configuration information in one of the following situations: T311 times out or stops, or T301 times out or stops.

[0130] Optionally, if the UE performs the RRC establishment procedure and / or T300 is enabled, the UE considers the WUS configuration information invalid.

[0131] In some implementations, the UE is a connected UE before or during cell selection or reselection.

[0132] In some implementations, the UE has WUS configuration information before performing cell selection or reselection, or when the UE is performing cell selection or reselection, or the UE has SIB-X carrying WUS configuration information.

[0133] For example, the UE obtains new WUS configuration information before cell selection or reselection, or the UE obtains a new SIB-X including WUS configuration information.

[0134] For example, the UE has valid WUS configuration information, or the UE has a valid new SIB-X that includes WUS configuration information.

[0135] Optionally, in the event of RRC reconstruction failure, the UE obtains SIB-X according to the RRC idle state / RRC inactive state procedure.

[0136] Optionally, if RRC reconstruction is successful, the UE obtains SIB-X according to the RRC connection state procedure.

[0137] Figure 3 is a schematic flowchart of a communication method provided in another embodiment of this application. The method in Figure 3 is described from the perspective of the interaction between a first terminal device and a network device, which can be any type of terminal device and network device mentioned in Figure 1. The first terminal device can be, for example, a terminal device that supports on-demand request SIB1.

[0138] This application does not specifically limit the RRC state of the first terminal device in its embodiments. For example, the first terminal device is located in the first cell and is in an RRC connected state. Or, the first terminal device is a terminal device connected to the first cell. Another example is that the first terminal device resides in the first cell and is in an RRC disconnected state (such as an RRC idle state or an RRC inactive state). The first cell mentioned here can be a first type of cell or a second type of cell. A first type of cell includes one or more of the following: a normal cell, a cell that periodically sends SIB1, a cell that periodically sends SSB, a cell that does not support NES, an NES cell that is broadcasting SIB1, and an NES cell that is broadcasting SSB. A second type of cell includes one or more of the following: an NES cell, a cell that requests SIB1 on demand, a cell that does not periodically send SIB1, and a cell that does not periodically send SSB.

[0139] Referring to Figure 3, in step S310, the first terminal device receives the first WUS configuration information and / or the first SIB (used to carry the first WUS configuration information).

[0140] This application does not specifically limit the timing or method of receiving the first WUS configuration information or the first SIB.

[0141] In some implementations, the aforementioned first WUS configuration information or first SIB can be carried in a handover command for cell handover. For example, if the first terminal device is in RRC connected state and the first terminal device is handovering from the second cell to the first cell, the first terminal device can receive a cell handover command, and the cell handover command carries the first WUS configuration information or first SIB.

[0142] In some implementations, the aforementioned first WUS configuration information or first SIB can be carried in the cell's broadcast message.

[0143] Upon receiving the first WUS configuration information or the first SIB, in some implementations, the first terminal device can determine the validity of the first WUS configuration information or the first SIB. In one implementation, the first terminal device can determine the validity of the first SIB or the first WUS configuration information based on the SIB1 of the first cell. For example, the SIB1 of the first cell may include a first parameter for determining the validity of the first SIB (assuming the first SIB is represented by SIB-X, the first parameter may be called the validity parameter of SIB-X). Exemplarily, the first parameter may include one or more of the following: value tag, area scope, area value, public land mobile network (PLMN) identifier, and cell identifier.

[0144] After determining the validity of the first WUS configuration information or the first SIB, in some implementations, the first terminal device may perform different operations based on different check results of the validity of the first WUS configuration information or the first SIB. For example, if the first SIB is valid, the first terminal device continues to save or use the first SIB or the first WUS configuration information; and / or, if the first SIB is valid, the first terminal device determines that it is not necessary to update the first SIB or the first WUS configuration information.

[0145] The determination of the validity of the first WUS configuration information or the first SIB by the first terminal device can be triggered under certain conditions (hereinafter referred to as the fourth condition). This fourth condition may include one or more of the following: the first terminal device needs to request the SIB used to carry the WUS configuration information; the first terminal device needs to obtain the WUS configuration information; the first terminal device receives a system information change instruction; the first terminal device selects the first cell based on the cell selection process; the first terminal device selects the first cell based on the cell reselection process; the first terminal device connects to the first cell (i.e., is located in the first cell and enters the RRC connected state); the first terminal device camps in the first cell; the first terminal device switches from the second cell to the first cell; the first terminal device receives the SIB1 of the first cell; the first terminal device receives the SIB1 of the first cell for the first time; the first cell where the first terminal device is currently located is broadcasting SIB1.

[0146] For example, if the first terminal device selects a first cell based on the cell selection process, the first terminal device determines the validity of the previously acquired or stored first WUS configuration information or first SIB. If the first WUS configuration information or first SIB is valid, the first terminal device can continue to use the first WUS configuration information or first SIB in the first cell; and / or, if the first WUS configuration information or first SIB is invalid, the first terminal device can acquire new second WUS configuration information or second SIB (used to carry the second WUS configuration information, which will not be described again below) in the first cell.

[0147] For example, if the first terminal device connects to the first cell based on the RRC connection establishment procedure, the first terminal device determines the validity of the first WUS configuration information or the first SIB that was previously acquired or stored. If the first WUS configuration information or the first SIB is valid, the first terminal device can continue to use the first WUS configuration information or the first SIB in the first cell; and / or, if the first WUS configuration information or the first SIB is invalid, the first terminal device can acquire new second WUS configuration information or a second SIB in the first cell.

[0148] For example, if the first terminal device reselects to the first cell based on the cell reselection process, the first terminal device determines the validity of the previously acquired or stored first WUS configuration information or first SIB. If the first WUS configuration information or first SIB is valid, the first terminal device can continue to use the first WUS configuration information or first SIB in the first cell; and / or, if the first WUS configuration information or first SIB is invalid, the first terminal device can acquire new second WUS configuration information or second SIB in the first cell.

[0149] For example, if the first terminal device moves from outside the coverage area to the first cell, the first terminal device determines the validity of the first WUS configuration information or the first SIB that was previously acquired or stored. If the first WUS configuration information or the first SIB is valid, the first terminal device can continue to use the first WUS configuration information or the first SIB in the first cell; and / or, if the first WUS configuration information or the first SIB is invalid, the first terminal device can acquire new second WUS configuration information or a second SIB in the first cell.

[0150] For example, if the first terminal device switches to the first cell based on a cell handover process, the first terminal device determines the validity of the previously acquired or stored first WUS configuration information or first SIB. If the first WUS configuration information or first SIB is valid, the first terminal device can continue to use the first WUS configuration information or first SIB in the first cell; and / or, if the first WUS configuration information or first SIB is invalid, the first terminal device can acquire new second WUS configuration information or second SIB in the first cell.

[0151] For example, if the first terminal device receives a system information change instruction, the first terminal device determines the validity of the previously acquired or stored first WUS configuration information or first SIB (the first terminal device may first acquire SIB1 and determine the validity of the first WUS configuration information or first SIB based on SIB1). If the first WUS configuration information or first SIB is valid, the first terminal device can continue to use the first WUS configuration information or first SIB in the first cell; and / or, if the first WUS configuration information or first SIB is invalid, the first terminal device can acquire new second WUS configuration information or second SIB in the first cell.

[0152] For example, if the first terminal device receives SIB1 from the first cell, the first terminal device determines the validity of the previously acquired or stored first WUS configuration information or first SIB. If the first WUS configuration information or first SIB is valid, the first terminal device can continue to use the first WUS configuration information or first SIB in the first cell; and / or, if the first WUS configuration information or first SIB is invalid, the first terminal device can acquire new second WUS configuration information or second SIB in the first cell.

[0153] For example, if the first terminal device receives SIB1 from the first cell for the first time, the first terminal device determines the validity of the previously acquired or stored first WUS configuration information or first SIB. If the first WUS configuration information or first SIB is valid, the first terminal device can continue to use the first WUS configuration information or first SIB in the first cell; and / or, if the first WUS configuration information or first SIB is invalid, the first terminal device can acquire new second WUS configuration information or second SIB in the first cell. Further, in some implementations, if the first cell can be a cell that requests SIB1 on demand, the first terminal device performs the above actions.

[0154] For example, if the first cell is broadcasting SIB1, the first terminal device determines the validity of the first WUS configuration information or the first SIB that was previously acquired or stored. If the first WUS configuration information or the first SIB is valid, the first terminal device can continue to use the first WUS configuration information or the first SIB in the first cell; and / or, if the first WUS configuration information or the first SIB is invalid, the first terminal device can acquire new second WUS configuration information or a second SIB in the first cell.

[0155] Figure 4 is a flowchart illustrating a communication method provided in another embodiment of this application. The method in Figure 4 is described from the perspective of the interaction between a first terminal device and a network device, which can be any type of terminal device and network device mentioned in Figure 1. The first terminal device can be, for example, a terminal device that supports on-demand request SIB1.

[0156] This application does not specifically limit the RRC state of the first terminal device in its embodiments. For example, the first terminal device may be located in a first cell and be in an RRC connected state. Alternatively, the first terminal device may be a terminal device connected to the first cell. Another example is that the first terminal device may reside in the first cell and be in an RRC disconnected state (such as an RRC idle state or an RRC inactive state). The first cell mentioned here may be a first type of cell or a second type of cell. A first type of cell includes one or more of the following: a normal cell, a cell that periodically sends SIB1, a cell that periodically sends SSB, a cell that does not support NES, an NES cell that is broadcasting SIB1, and an NES cell that is broadcasting SSB. A second type of cell includes one or more of the following: an NES cell, a cell that requests SIB1 on demand, a cell that does not periodically send SIB1, and a cell that does not periodically send SSB.

[0157] Referring to Figure 4, in step S410, the first terminal device receives SIB1 from the first cell. It should be understood that the embodiments in Figure 4 and Figure 3 can be implemented independently or in combination. For example, the first terminal device can first execute step S310 in Figure 3 in the second cell, i.e., receive the first WUS configuration information and / or the first SIB. After entering the first cell (which can be based on cell handover, cell selection, or cell reselection), the first terminal device receives SIB1 from the first cell. Of course, the first WUS configuration information, the first SIB, and SIB1 can all be information received in the first cell. For example, the first terminal device receives the first WUS configuration information and / or the first SIB in the first cell, then receives SIB1 in the first cell, and determines the validity of the first WUS configuration information and / or the first SIB based on SIB1. If the first WUS configuration information and / or the first SIB is valid, the first terminal device may continue to use the first WUS configuration information and / or the first SIB; and / or, if the first WUS configuration information and / or the first SIB is invalid, the first terminal device may receive new second WUS configuration information and / or the second SIB (for carrying the second WUS configuration information) in the first cell.

[0158] The embodiments of this application do not specifically limit the receiving method of SIB1 of the first cell.

[0159] In some implementations, when the first cell sends SIB1 via a broadcast message, the SIB1 of the first cell is carried within the broadcast message. Accordingly, the first terminal device can receive the SIB1 of the first cell through this broadcast message. It should be noted that the first cell sending SIB1 via a broadcast message includes one of the following: the first cell periodically broadcasts SIB1; the first cell is a cell that requests SIB1 on demand, and the first cell is currently broadcasting SIB1.

[0160] In some implementations, the first terminal device can receive the SIB1 of the first cell via dedicated signaling. This dedicated signaling can be an RRC-specific message, such as an RRC reconfiguration message. For example, the first terminal device receives an RRC-specific message that includes dedicated SIB1 delivery information, which includes the SIB1 of the first cell. Further, in one implementation, if the first cell is a cell that requests SIB1 on demand (or an NES cell), the SIB1 of the first cell is carried in the RRC-specific message of the first terminal device. Further, in some implementations, the dedicated System Information Delivery (si-BroadcastStatus) field description can indicate that the IE can carry SIB-X, i.e., the SIB used to carry WUS configuration information; and / or, the network device can notify the first terminal device of the SIB-X via system information broadcast (optionally, the system information broadcast status (si-BroadcastStatus) can be set to broadcasting).

[0161] In some implementations, if the first cell does not periodically broadcast SIB1, or if the first cell is a cell that requests SIB1 on demand, then the network device does not configure the search space corresponding to SIB1. For example, the network device may not broadcast the configuration information of the search space corresponding to SIB1; and / or, the handover command sent by the network device to the first terminal device may not carry the configuration information of the search space corresponding to SIB1. Whether the network device needs to carry the configuration information of the search space corresponding to SIB1 in the handover command can be determined based on the capabilities of the first terminal device. For example, if the first terminal device has the capability to request SIB1 on demand, then the handover command may not carry the configuration information of the search space corresponding to SIB1. The capabilities of the first terminal device can be determined based on the interaction between the source network device and the target network device.

[0162] In some implementations, if the first cell is a cell that requests SIB1 on demand (or the first cell does not periodically broadcast SIB1), and the fifth condition is met, the first terminal device will perform cell reselection or determine that it cannot obtain SIB1. The fifth condition mentioned here may include one or more of the following: after the first terminal device camps on the first cell, it fails to determine (or authenticate) the validity of the stored SIB used to carry WUS configuration information; after the first terminal device camps on the first cell, it does not receive the SIB used to carry WUS configuration information; after the first terminal device camps on the first cell, it does not store a valid SIB used to carry WUS configuration information.

[0163] In some implementations, if the first terminal device is in RRC connected state, the acquisition method of the first cell's SIB1 can be determined based on whether the first terminal device has configured a common search space (such as a common search space for SIB1).

[0164] For example, if the first terminal device is in RRC connected state and the first terminal device has not configured a common search space (such as a common search space for SIB1), the SIB1 of the first cell can be obtained based on network device-specific RRC messages. Optionally, the first terminal device is a terminal device whose T311 timer is not running, or a terminal device that is not in the process of RRC reconstruction. Optionally, the first terminal device does not need to obtain or re-obtain the MIB before obtaining SIB1.

[0165] For example, when the first terminal device is in RRC connected state and the first terminal device is configured with a common search space (such as a common search space for SIB1), the first terminal device satisfies one of the following: obtains the SIB1 broadcast by the network device; obtains the SIB1 of the first cell based on a network device-specific RRC message; requests or obtains the SIB1 of the first cell based on a RACH procedure (such as a RACH procedure triggered by an RRC system information request, or a RACH procedure executed using RACH resources associated with SIB1 (such as a physical uplink shared channel occasion (PO) and / or preamble)); requests or obtains the SIB1 of the first cell based on a dedicated RRC message (such as a dedicated SIB request) sent by the first terminal device; or obtains other system information (OSI) of the first cell when it is not necessary to obtain the SIB1 of the first cell (i.e., the first terminal device does not need to obtain SIB1 first and then obtain OSI, but can directly obtain OSI). Optionally, the first terminal device is a terminal device whose T311 timer is not running, or a terminal device that is not in the process of RRC reconstruction. Optionally, the first terminal device does not need to acquire or reacquire the MIB before acquiring SIB1. Further, the first terminal device acquires SIB1 if one of the following requests is met: receiving a system information change instruction; the first terminal device does not store a valid target SIB (the SIB required by the first terminal device) and has not acquired SIB1 in the current change cycle; or the first terminal device does not store a valid target SIB (the SIB required by the first terminal device) and the SIB1 acquired in the current change cycle indicates that the broadcast status of the target SIB is nonBroadcasting.

[0166] For example, when the first terminal device is in RRC connected state and the first terminal is a UE running T311, or a UE performing RRC reconstruction, the UE obtains the MIB of the first cell, and / or the UE obtains the SIB1 of the first cell. In obtaining SIB1, the UE obtains SIB1 via broadcast information, or obtains SIB1 using a method similar to an idle / inactive UE, or the UE requests and obtains SIB1 from the first cell.

[0167] Figure 5 is a schematic flowchart of a communication method provided in another embodiment of this application. The method in Figure 5 is described from the perspective of the interaction between a first terminal device and a network device, which can be any type of terminal device and network device mentioned in Figure 1.

[0168] This application does not specifically limit the RRC state of the first terminal device in its embodiments. For example, the first terminal device may be located in a first cell and be in an RRC connected state. Alternatively, the first terminal device may be a terminal device connected to the first cell. Another example is that the first terminal device may reside in the first cell and be in an RRC disconnected state (such as an RRC idle state or an RRC inactive state). The first cell mentioned here may be a first type of cell or a second type of cell. A first type of cell includes one or more of the following: a normal cell, a cell that periodically sends SIB1, a cell that periodically sends SSB, a cell that does not support NES, an NES cell that is broadcasting SIB1, and an NES cell that is broadcasting SSB. A second type of cell includes one or more of the following: an NES cell, a cell that requests SIB1 on demand, a cell that does not periodically send SIB1, and a cell that does not periodically send SSB.

[0169] Referring to Figure 5, in step S510, the first terminal device performs a first operation. The first operation may include one or more of the following: receiving a second SIB (used to carry second WUS configuration information) sent by the first cell; receiving the second WUS configuration information sent by the first cell; determining that the first WUS configuration information previously received or saved by the first terminal device is invalid; re-acquiring the WUS configuration information; the first terminal device acquiring the SIB1 of the first cell; and the first terminal device requesting the second SIB from the first cell.

[0170] It should be understood that the embodiments in Figure 5 can be implemented independently of or in combination with the embodiments in Figure 3 or Figure 4. For example, the first terminal device can first receive the first SIB or first WUS configuration information mentioned in the embodiment of Figure 3. Then, after connecting to or camping on the first cell, the first terminal device can continue to execute step S510. Further, in some implementations, before executing step S510, step S410 in Figure 4 can be executed first, that is, receiving the SIB1 of the first cell, and if it is determined that the first SIB or first WUS configuration information is invalid based on the SIB1 of the first cell, then step S510 is executed. Of course, the first terminal device can also directly execute step S510 after connecting to or camping on the first cell.

[0171] Step S510 in Figure 5 can be executed under certain circumstances (hereinafter referred to as the first circumstance). This first circumstance may include one or more of the following: the first SIB is invalid; the first WUS configuration information is invalid; the first terminal device switches to the first cell; the first terminal device reselects to the first cell; the first terminal device selects to the first cell based on the cell selection process; the first terminal device enters the first cell from outside the coverage area; the first terminal device receives a system information change instruction; the first terminal device receives the SIB1 of the first cell; the first terminal device receives the SIB1 of the first cell for the first time; the first terminal device connects to the first cell; the first terminal device receives a system information change instruction; the first terminal device receives the SIB1 of the first cell; the first terminal device receives the SIB1 of the first cell for the first time; the first cell where the first terminal device is currently located is broadcasting SIB1. For example, the first operation can be executed whenever the first terminal device switches, reselects, or selects the first cell, or whenever the first terminal device moves or camps in a different cell.

[0172] As can be seen from the above description, whether to perform the first operation can be divided into two cases. In the first case, it is necessary to first determine the validity of the first SIB or first WUS configuration information (e.g., authenticating the validity of the first SIB or first WUS configuration information based on the validity parameters in SIB1). If the first SIB or first WUS configuration information is invalid, the second SIB or second WUS configuration information is obtained or re-obtained in the first cell. In the second case, the first terminal device does not need to determine the validity of the first SIB or first WUS configuration information, but can directly obtain the second SIB or second WUS configuration information. Some specific examples are given below.

[0173] In one implementation, if the first SIB is invalid, the first terminal device receives a second SIB or second WUS configuration information sent by the first cell. The first SIB mentioned here may be an SIB previously received or stored by the first terminal device. The acquisition and validity verification of the first SIB can be performed as described in the embodiments of Figures 3 and 4, and will not be repeated here. For example, after the first terminal device receives SIB1 being broadcast by the first cell, it can determine whether the first SIB is valid based on SIB1. If the first SIB is invalid, the first terminal device receives a second SIB or second WUS configuration information sent by the first cell. As a more specific example, SIB-X (including the SIB used to carry WUS configuration information) can be added to the system information scheduling information (si-SchedulingInfo) or SIB type information (SIB-TypeInfo) in the SIB1 sent by the first cell. The first terminal device can determine the validity of the first SIB based on the system information scheduling information or SIB type information, and / or receive the second SIB or second WUS configuration information.

[0174] In another implementation, if the first WUS configuration information is invalid, the first terminal device can receive the second SIB or second WUS configuration information sent by the first cell. The first WUS configuration information mentioned here can be WUS configuration information previously received or saved by the first terminal device. The acquisition and validity verification of the first WUS configuration information can be performed as described in the embodiments of Figures 3 and 4, and will not be repeated here.

[0175] In another implementation, if the first terminal device switches to the first cell, the first terminal device receives the second SIB or second WUS configuration information sent by the first cell. For example, assuming the first terminal device acquired or stored WUS configuration information (such as the first WUS configuration information mentioned above) before the cell switch, the first terminal device, upon switching to the first cell, can determine (or believe) that the previously stored WUS configuration information is no longer valid, or determine (or believe) that it needs to reacquire the second WUS configuration information, or determine (or believe) that it needs to delete the previously stored WUS configuration information. Alternatively, assuming the first terminal device did not acquire or store WUS configuration information before the cell switch, the first terminal device, upon switching to the first cell, can receive the second SIB or second WUS configuration information sent by the first cell.

[0176] In another implementation, if the first terminal device reselects to the first cell, the first terminal device receives the second SIB or second WUS configuration information sent by the first cell. For example, assuming the first terminal device acquired or stored WUS configuration information (such as the first WUS configuration information mentioned above) before cell reselection, the first terminal device, upon reselecting to the first cell, can determine (or consider) that the previously stored WUS configuration information is no longer valid, or determine (or consider) that it needs to reacquire the second WUS configuration information, or determine (or consider) that it needs to delete the previously stored WUS configuration information. Alternatively, assuming the first terminal device did not acquire or store WUS configuration information before cell reselection, the first terminal device, upon reselecting to the first cell, can receive the second SIB or second WUS configuration information sent by the first cell.

[0177] In another implementation, if the first terminal device selects a first cell based on the cell selection process, the first terminal device receives the second SIB or second WUS configuration information sent by the first cell. For example, assuming the first terminal device acquired or stored WUS configuration information (such as the first WUS configuration information mentioned above) before cell reselection, the first terminal device, upon reselecting to the first cell, can determine (or consider) that the previously stored WUS configuration information is no longer valid, or determine (or consider) that it needs to reacquire the second WUS configuration information, or determine (or consider) that it needs to delete the previously stored WUS configuration information. Alternatively, assuming the first terminal device did not acquire or store WUS configuration information before cell selection, the first terminal device, upon selecting the first cell, can receive the second SIB or second WUS configuration information sent by the first cell.

[0178] In another implementation, if the first terminal device enters the first cell from outside the coverage area, the first terminal device receives the second SIB or second WUS configuration information sent by the first cell. For example, assuming the first terminal device stored WUS configuration information (such as the first WUS configuration information mentioned above) before entering the first cell, the first terminal device can determine (or consider) that the previously stored WUS configuration information is no longer valid, or determine (or consider) that it needs to re-acquire the second WUS configuration information, or determine (or consider) that it needs to delete the previously stored WUS configuration information. Alternatively, assuming the first terminal device did not acquire or store WUS configuration information before entering the first cell, the first terminal device can receive the second SIB or second WUS configuration information sent by the first cell upon entering the first cell.

[0179] In another implementation, if the first terminal device receives a system information change instruction, then the first terminal device receives the second SIB or second WUS configuration information sent by the first cell. For example, the first terminal device receives the first WUS configuration information from the first cell, and then receives the system information change instruction. After receiving the system change instruction, the first terminal device can determine, based on the instruction of SIB1, whether the stored first WUS configuration information is still valid, or whether it is necessary to reacquire the second SIB or second WUS configuration information. If the first WUS configuration information is invalid or it is determined that the second SIB or second WUS configuration information needs to be reacquired, then the first terminal device receives the second SIB or second WUS configuration information sent by the first cell.

[0180] In another embodiment, if the first terminal device receives SIB1 from the first cell, the first terminal device receives (or immediately receives) the second SIB or second WUS configuration information sent by the first cell.

[0181] In another embodiment, if the first terminal device receives the SIB1 of the first cell for the first time, the first terminal device receives (or immediately receives) the second SIB or second WUS configuration information sent by the first cell.

[0182] As mentioned earlier, the first terminal device receives a second SIB sent by the first cell. This second SIB can be triggered based on a first message. The first message can satisfy one or more of the following: the first message is a message sent by the first terminal device; and / or, the first message is used to request the first cell to send the second SIB. The first message can be carried in uplink resources, which can be, for example, dedicated uplink resources.

[0183] This application does not specifically limit the type of the first message in the embodiments. Several possible options for the first message are given below.

[0184] In some implementations, the first message is a DedicatedSIBRequest message. For example, if the first terminal device is in RRC connected state, the first message is a DedicatedSIBRequest message. Alternatively, the first message can also be any other message used to implement the SIB request function.

[0185] In some implementations, the first message is an RRC System Info Request message, used to trigger the RACH process, or a message transmitted through the RACH process. For example, if the first terminal device is in an RRC disconnected state (such as an RRC idle state or an RRC inactive state), then the first message is an RRC System Info Request message, used to trigger the RACH process, or a message transmitted through the RACH process.

[0186] It should be understood that the first message may be sent under certain conditions (hereinafter referred to as the first condition). This first condition may be associated with one or more of the following: whether the first terminal device stores a valid SIB-X (an SIB for carrying WUS configuration information); whether the first terminal device stores valid WUS configuration information; whether the first terminal device has configured a search space for the second SIB; whether the first terminal device has configured a search space for the OSI; whether the first cell's SIB1 contains the second SIB; whether the system information scheduling information in the first cell's SIB1 contains the second SIB; the system information broadcast status of the second SIB in the first cell's SIB1; the system information broadcast status of the second SIB in the system information scheduling information; whether the first terminal device has configured on-demand SIB requests; whether the first terminal device has the capability to make on-demand SIB requests; whether the first timer is running, and whether the first timer is associated with on-demand SIB requests. Furthermore, in some implementations, the aforementioned first condition can be associated with the RRC connection state. In other words, if the first condition is met when the first terminal device is in the RRC connection state, the first terminal device sends a first message (such as a dedicated SIB request message).

[0187] In one implementation, the first condition includes one or more of the following: the first terminal device does not store a valid SIB-X (an SIB for carrying WUS configuration information); the first terminal device does not store valid WUS configuration information; the first terminal device does not configure a search space for the second SIB; the first terminal device does not configure a search space for OSI; SIB1 of the first cell contains the second SIB; system information scheduling information contains the second SIB; the first terminal device configures an onDemandSIB-request; the first terminal device has the capability to make onDemandSIB-requests; and a third timer (such as the T350 timer) is not running. For example, if the first terminal device does not configure a search space for OSI and does not store a valid SIB (an SIB for carrying WUS configuration information), if the system information scheduling information contains the second SIB, and the first terminal device configures an onDemandSIB-request, and the T350 timer is not running, then the first terminal device triggers the transmission of a dedicated SIB request, and the information element (IE) corresponding to the dedicated SIB request carries indication information of the second SIB.

[0188] In another implementation, the first condition includes one or more of the following: the first terminal device does not store a valid SIB-X (an SIB used to carry WUS configuration information); the first terminal device does not store valid WUS configuration information; the first terminal device has configured a search space for the second SIB; the first terminal device has configured a search space for OSI; the SIB1 of the first cell contains the second SIB; the system information scheduling information contains the second SIB; the system information broadcast status indicates that the second SIB is not transmitted using broadcast mode; the first terminal device has configured an onDemandSIB-request; the first terminal device has the capability to make onDemandSIB-requests; and the third timer (such as the T350 timer) is not in running state. For example, if the first terminal device is configured with an OSI search space and does not store a valid SIB-X (an SIB used to carry WUS configuration information), if the system information scheduling information contains SIB-X and the system information broadcast status corresponding to SIB-X is set to non-broadcasting, the first terminal device is configured with onDemandSIB-request, and the T350 timer is not running, then the first terminal device triggers the transmission of a dedicated SIB request, and the IE corresponding to the dedicated SIB request carries the indication information of the second SIB.

[0189] It should be understood that the second SIB can be carried within dedicated System Information Delivery (DID). For example, the domain description of the DID can indicate that the IE can carry SIB-X (an SIB used to carry WUS configuration information). Alternatively, the second SIB can be an SIB-X broadcast by the network device via system messages (in which case the network device can set the system information broadcast status to broadcasting).

[0190] In addition to the first condition mentioned above, in some implementations, the first message can also be triggered when the second condition is met. This second condition can be associated with one or more of the following: whether the SIB1 of the first cell contains system information scheduling information; whether the SIB1 of the first cell contains system information request configuration; whether the system information scheduling information contains system information request configuration; whether the SIB1 of the first cell contains a second SIB; whether the system information scheduling information contains a second SIB; the system information broadcast status of the second SIB in the SIB1 of the first cell; the system information broadcast status of the second SIB in the system scheduling information. Furthermore, in some implementations, this second condition can be associated with the RRC disconnected state. That is, if the first terminal device is in the RRC disconnected state and the second condition is met, the first terminal device can send the first message (such as the RRC system information request message mentioned above, a message used to trigger the RACH procedure, or a message transmitted through the RACH procedure).

[0191] In one implementation, the second condition includes one or more of the following: the SIB1 of the first cell contains system information scheduling information (si-SchedulingInfo); the SIB1 of the first cell contains system information request configuration; the system information scheduling information contains system information request configuration (si-RequestConfig); the SIB1 of the first cell contains a second SIB; the system information scheduling information contains a second SIB; and the system information broadcast status (si-BroadcastStatus) indicates that the second SIB does not use broadcast transmission. If the second condition is met, the first terminal device may, for example, send a first message of the following type: a message for triggering a RACH procedure or a message transmitted through a RACH procedure. For example, if the SIB1 of the first cell includes si-SchedulingInfo, si-SchedulingInfo includes si-RequestConfig, and the SchedulingInfo in si-SchedulingInfo includes SIB-X (the SIB for carrying WUS configuration information), and if the si-BroadcastStatus corresponding to SIB-X is set to notBroadcasting, then the first terminal device triggers a RACH procedure to request SIB-X.

[0192] In another implementation, the second condition includes one or more of the following: the SIB1 of the first cell contains system information scheduling information; the SIB1 of the first cell does not contain system information request configuration; the system information scheduling information does not contain system information request configuration; the SIB1 of the first cell contains a second SIB; the system information scheduling information contains a second SIB; and the system information broadcast status indicates that the second SIB is not transmitted using broadcast mode. If the second condition is met, the first terminal device may, for example, send a first message of the following type: an RRC system information request message.

[0193] For example, if the SIB1 of the first cell includes si-SchedulingInfo, si-SchedulingInfo does not include si-RequestConfig, and the SchedulingInfo in si-SchedulingInfo includes SIB-X (the SIB used to carry WUS configuration information), and if the si-BroadcastStatus corresponding to SIB-X is set to notBroadcasting, then the first terminal device sends an RRCSystemInfoRequest to request SIB-X. For example, this RRCSystemInfoRequest may carry a requested-SI-list, and this requested-SI-list may contain SIB-X.

[0194] Furthermore, in some implementations, after sending the RRC system information request message, the first terminal device can acquire or listen to (or immediately acquire or listen to) the broadcast second SIB. For example, if it receives a system information request confirmation message from a lower layer (or receives an RRC system information request confirmation message), the first terminal device acquires or listens to (or immediately acquires or listens to) the broadcast second SIB.

[0195] Besides obtaining the second SIB based on the first message as described above, in other implementations, the first terminal device can also directly obtain or listen to the second SIB broadcast by the first cell.

[0196] The "first terminal device acquiring or listening to the second SIB broadcast by the first cell" mentioned here can also be performed under certain conditions (hereinafter referred to as the third condition). The third condition is associated with one or more of the following: whether the first terminal device stores valid WUS configuration information; whether the first terminal device stores valid SIB-X (used to carry WUS configuration information); whether the first terminal device has configured a search space for the second SIB; whether the first terminal device has configured a search space for OSI; whether the first cell's SIB1 contains the second SIB; whether the system information scheduling information (si-schedulinginfo) in the first cell's SIB1 contains the second SIB; the system information broadcast status (si-BroadcastStatus) of the second SIB in the first cell's SIB1; and the system information broadcast status of the second SIB in the system information scheduling information.

[0197] In one implementation, the third condition includes one or more of the following: the first terminal device is configured with a search space for the second SIB; the first terminal device is configured with a search space for OSI; the second SIB is contained in SIB1 of the first cell; the system information scheduling information contains the second SIB; and the system information broadcast status indicates that the second SIB is transmitted using broadcast. For example, if the first terminal device is configured with a search space for OSI and the first terminal device does not store a valid SIB-X (the SIB used to carry WUS configuration information), and if si-schedulinginfo contains SIB-X and the si-BroadcastStatus corresponding to SIB-X is set to Broadcasting, then the first terminal device can obtain SIB-X based on broadcast.

[0198] The embodiments of this application are described in more detail below with specific examples. In the examples below, the first terminal device mentioned above is called UE, the SIB used to carry WUS configuration information is called SIB-X, and the first cell mentioned above is cell 1. It should be noted that the examples below are only for helping those skilled in the art to understand the embodiments of this application, and are not intended to limit the embodiments of this application to the specific values ​​or specific scenarios illustrated. Those skilled in the art can obviously make various equivalent modifications or changes based on the examples given, and such modifications or changes also fall within the scope of the embodiments of this application.

[0199] Example 2

[0200] In related technologies, it is unclear how a Cell A (i.e., a normal cell) or an NES cell (a cell requesting SIB1 on demand) obtains WUS configuration information or carries SIB-X information for RRC connected state. Example 2 provides a solution to this problem.

[0201] First, the UE is in RRC connected state and is currently connected to cell 1.

[0202] 1) Cell 1 can be a normal cell, or a cell that transmits SIB1 / SSB periodically, or an energy-saving cell (e.g., a cell that transmits SSB / SIB1 on demand).

[0203] 2) The UE obtains SIB1 through dedicated signaling (such as RRC reconfiguration messages) or by broadcast.

[0204] 3) The UE is a UE that supports OD-SIB1.

[0205] 4) If the UE is a UE that has been switched to cell 1, the SIB-X or WUS configuration information can be sent to the UE through the handover command.

[0206] If the UE needs to request SIB-X, or the UE needs to obtain WUS configuration information, or the UE receives a system information change indication, the UE shall perform at least one of the following actions:

[0207] 1) Determine whether SIB-X is valid based on the SIB-X validity parameters in SIB1;

[0208] 2) If the UE has a valid SIB-X stored, the UE uses or saves the WUS configuration information carried in the SIB-X;

[0209] 3) If the UE does not have a valid SIB-X stored, the UE needs to obtain a new SIB-X.

[0210] The UE can obtain the new SIB-X in the following ways:

[0211] a) If the UE is not configured with a search space for OSI and does not store a valid SIB-X, and if the si-schedulinginfo contains the SIB-X, and the UE is configured with onDemandSIB-request and the T350 timer is not running, then the UE triggers the DedicatedSIBRequest transmission and carries the SIB-X in the IE.

[0212] b) If the UE is configured with an OSI-based search space and the UE does not store a valid SIB-X, and if the si-schedulinginfo contains the SIB-X and the si-BroadcastStatus corresponding to the SIB-X is set to Broadcasting, then the UE obtains the SIB-X based on broadcast.

[0213] c) If the UE is configured with an OSI search space and the UE does not store a valid SIB-X, if the si-schedulinginfo contains the SIB-X, the si-BroadcastStatus corresponding to the SIB-X is set to notBroadcasting, the UE is configured with onDemandSIB-request, and timer T350 is not running, then the UE triggers the DedicatedSIBRequest transmission and carries the SIB-X in the IE.

[0214] 4) The domain description of dedicatedSystemInformationDelivery specifies that the IE can carry SIB-X; and / or, the network notifies the UE of SIB-X via system information broadcast so that the UE can obtain WUS. Optionally, si-BroadcastStatus can be set to Broadcasting before broadcasting SIB-X.

[0215] Before the UE obtains SIB-X, it can first obtain SIB1. The following is an example illustrating how to obtain SIB1.

[0216] 1) If SIB1 is an on-demand requested SIB1 and SIB1 is being broadcast, or if SIB1 is a periodically broadcast SIB1, then the UE can obtain SIB1 according to the procedures provided by the relevant technology.

[0217] 2) If SIB1 is not a periodically broadcast SIB1, or if SIB1 is an on-demand requested SIB1, then network devices (such as base stations) may be required not to configure a search space for SIB1 (e.g., on-demand SIB1 cells do not broadcast configuration information for the SIB1 search space, or the handover command of a UE supporting on-demand SIB1 requests does not carry configuration information for the SIB1 search space (the source network device (such as S-gNB) and the target network device (such as T-gNB) can obtain UE capabilities based on interaction)), and / or, the UE obtains SIB1 based on a dedicated RRC message (optionally, the network device can notify the UE SIB through dedicatedSIB1-Delivery. For example, the domain description of dedicatedSystemInformationDelivery can indicate that the IE can carry SIB-X; and / or, the network device can notify the UE SIB-X through system information broadcast so that the UE can obtain SIB1. Optionally, si-BroadcastStatus can be set to Broadcasting).

[0218] The following provides detailed examples illustrating the sources of WUS configuration information. The sources of WUS configuration information can be categorized into the following three situations.

[0219] Case 0: The UE obtains WUS configuration information from cell 1. That is, the UE did not obtain WUS configuration before camping, selecting, or reselecting to cell 1, or the obtained WUS configuration has expired.

[0220] Case 1: Assume that the UE has obtained WUS configuration information before connecting to cell 1, and assume that the WUS configuration information may be available WUS configuration information.

[0221] Case 2: Assume that the UE has obtained the WUS configuration information before connecting to cell 1, and assume that the WUS configuration information is definitely unavailable.

[0222] For Case 1:

[0223] Based on the SIB-X validity parameters indicated by the network device, it can be determined whether the stored WUS is still valid, or whether it is necessary to reacquire the SIB-X.

[0224] 1) Basic principle: After cell selection, or after RRC connection establishment, or after cell handover, or when selecting or reselecting a new cell, or when receiving system information change instructions, the UE can use a valid SIB-X.

[0225] 2) Optionally, once the UE connects to the cell, or once the UE acquires SIB1 (or acquires SIB1 for the first time), the UE authenticates whether the stored SIB-X is valid. Optionally, if SIB-X is invalid, the UE immediately reacquires SIB-X; otherwise, the UE considers SIB-X valid. Optionally, this behavior applies to cell 1 as an on-demand SIB1 cell, meaning that if cell 1 is an on-demand SIB1 cell, the UE can authenticate whether the stored SIB-X is valid in the manner described in point 2).

[0226] 3) Optionally, once the UE connects to the cell, or once the UE obtains SIB1 (or obtains SIB1 for the first time), based on the indication of SIB-X validity parameters carried in SIB1 (including but not limited to valueTag, areaScope, etc.), the UE determines or authenticates whether the stored WUS configuration information or SIB-X is valid. Optionally, this authentication can be performed if the UE requires SIB-X, or it can be performed as soon as SIB1 is obtained. Optionally, this behavior applies to cell 1 as an on-demand SIB1 cell, that is, if cell 1 is an on-demand SIB1 cell, the UE can authenticate whether the stored SIB-X is valid in the manner described in point 3).

[0227] 4) Optionally, if a system information change indication is received and the UE obtains SIB1, the UE can determine, based on SIB1, whether the stored WUS configuration information is valid, or whether it needs to re-obtain SIB-X. Optionally, the above actions of the UE are performed in a cell if the UE is camped on a cell.

[0228] 5) Optionally, if the current cell is broadcasting SIB1, the UE verifies whether SIB-X is valid. Optionally, the above actions are performed in a cell where the UE is camped.

[0229] 6) For example, SIB-X information can be added to the si-SchedulingInfo of SIB1 or to the SIB-TypeInfo so that the UE can authenticate the validity of SIB-X. For example, SIB-X information can be added to the SIB that supports scheduling or to the SIB type information, such as adding the valueTag and / or areaScope corresponding to SIB-X.

[0230] For Case 2:

[0231] It can be assumed that the WUS configuration information stored by the UE is no longer valid, or that it is necessary to reacquire SIB-X, or that the previously stored WUS configuration information needs to be deleted.

[0232] 1) Basic principle: After cell selection, or after RRC connection establishment, or after cell handover, or after selecting or reselecting a new cell, or after receiving a system information change instruction, the UE needs to reacquire SIB-X, and / or considers the previously acquired SIB-X invalid.

[0233] 2) Optionally, once the UE is camped in cell 1, or once the UE obtains SIB1 (or obtains SIB1 for the first time), the UE immediately obtains SIB-X. That is, the UE does not need to perform SIB-X validity verification, or, without considering the validity verification parameters in SIB1, directly or re-obtains SIB-X. This cell can be a normal cell or an on-demand SIB-1 cell. Optionally, this behavior applies to cell 1 as an on-demand SIB-1 cell; that is, if cell 1 is an on-demand SIB-1 cell, the UE can authenticate the validity of the stored SIB-X in the manner described in point 2).

[0234] 3) Optionally, if a system information change indication is received and the UE obtains SIB1, the UE can determine, based on SIB1, whether the stored WUS configuration information is valid, or whether it needs to re-obtain SIB-X. Optionally, the above actions are performed in a cell if the UE is camped in that cell.

[0235] 4) Optionally, if the current cell is broadcasting SIB1, the UE verifies whether SIB-X is valid. Optionally, the above actions are performed in a cell where the UE is camped.

[0236] 5) For example, SIB-X information can be added to the si-SchedulingInfo of SIB1 or to the SIB-TypeInfo so that the UE can authenticate the validity of SIB-X. For example, SIB-X information can be added to the SIB that supports scheduling or to the SIB type information, such as adding the valueTag and / or areaScope corresponding to SIB-X.

[0237] 6) Optionally, if a system information change indication is received, or if a system information change indication is received and the system information change indication indicates an update to SIB-X, the UE needs to reacquire SIB-X. Optionally, the above actions are performed in a cell where the UE is camped.

[0238] 7) Optionally, if the current cell is broadcasting SIB1, the UE needs to reacquire SIB-X. Optionally, the above actions are performed in a cell where the UE is camped.

[0239] Furthermore, in some implementations, for UEs in RRC connected state (either UEs in an RRF scenario and in RRC connected state, or UEs in connected state that wish to request OSI), SIB1 can be obtained as follows:

[0240] If a public search space is not configured, SIB1 is delivered based on network device-specific RRCs; and / or

[0241] If no common search space is configured, the UE requests or obtains SIB1 based on a dedicated RRC message from the network device, or requests or obtains SIB1 based on a RACH procedure (such as a RACH procedure triggered by an RRC system information request, or a RACH procedure executed using RACH resources (PO and / or preamble) associated with SIB1), or requests or obtains SIB1 based on a dedicated RRC message sent by the UE (such as a dedicated SIB request), or, if it is not necessary to obtain SIB1, obtains the OSI of the first cell (i.e., the first terminal device does not need to obtain SIB1 before obtaining the OSI).

[0242] Example 3

[0243] In related technologies, it is unclear how WUS configuration information is obtained or how SIB-X carrying WUS configuration information is used in the RRC disconnected state, either in Cell A (i.e., normal cell) or NES cell (cell requesting SIB1 on demand). Example 3 provides a solution to this problem.

[0244] The UE is stationed in cell 1.

[0245] 1) Cell 1 can be a normal cell, or a cell that transmits SIB1 / SSB periodically, or an energy-saving cell (e.g., a cell that transmits SSB / SIB1 on demand).

[0246] 2) The UE is a UE that supports OD-SIB1.

[0247] If the UE needs to request SIB-X, or the UE needs to obtain WUS configuration information, or the UE receives a system information change indication, the UE shall perform at least one of the following actions:

[0248] 1) Determine whether SIB-X is valid based on the SIB-X validity parameters in SIB1;

[0249] 2) If the UE has a valid SIB-X stored, the UE uses or saves the WUS configuration information carried in the SIB-X;

[0250] 3) If the UE does not have a valid SIB-X stored, the UE needs to obtain a new SIB-X.

[0251] The UE can obtain the new SIB-X in the following ways:

[0252] a) For example, if SIB1 includes si-SchedulingInfo, si-SchedulingInfo includes si-RequestConfig, and the SchedulingInfo included in si-SchedulingInfo includes SIB-X, and if the si-BroadcastStatus corresponding to SIB-X is set to notBroadcasting, the UE triggers the RACH procedure to request SIB-X.

[0253] b) For example, if SIB1 includes si-SchedulingInfo, si-SchedulingInfo does not include si-RequestConfig, and the SchedulingInfo included in si-SchedulingInfo includes SIB-X, and if the si-BroadcastStatus corresponding to SIB-X is set to notBroadcasting, the UE sends an RRCSystemInfoRequest to request SIB-X. Note: The RRCSystemInfoRequest carries a requested-SI-list, which includes SIB-X.

[0254] Before the UE obtains SIB-X, it can first obtain SIB1. The following is an example illustrating how to obtain SIB1.

[0255] 1) If SIB1 is an on-demand requested SIB1 and SIB1 is being broadcast, or if SIB1 is a periodically broadcast SIB1, then the UE can obtain SIB1 according to the procedures provided by the relevant technology.

[0256] 2) If SIB1 is not periodically broadcast, or if SIB1 is requested on demand, if the UE camps on a cell and has not authenticated whether the stored SIB-X is valid, or has not obtained SIB-X, or the UE has not stored a valid SIB-X, the UE believes that it cannot obtain SIB-1, or the UE believes that the stored SIB-X is invalid, or the UE performs cell reselection.

[0257] The following provides detailed examples illustrating the sources of WUS configuration information. The sources of WUS configuration information can be categorized into the following three situations.

[0258] Case 0: The UE obtains WUS configuration information from cell 1.

[0259] Case 1: Assume that the UE has obtained WUS configuration information before camping on cell 1 (e.g., through cell selection or reselection), and assume that the WUS configuration information may be available WUS configuration information.

[0260] Case 2: Assume that the UE has obtained the WUS configuration information before camping on cell 1 (e.g., through cell selection or reselection), and assume that the WUS configuration information is definitely unavailable.

[0261] For Case 1:

[0262] Based on the SIB-X validity parameters indicated by the network device, it can be determined whether the stored WUS is still valid, or whether it is necessary to reacquire the SIB-X.

[0263] 1) Basic principle: The UE can use a valid SIB-X after cell selection, cell reselection, moving from outside the coverage area to the coverage area, or receiving a system information change instruction.

[0264] 2) Optionally, once the UE is camped in the cell, or once the UE obtains SIB1 (or obtains SIB1 for the first time), the UE authenticates whether the stored SIB-X is valid.

[0265] 3) Optionally, once the UE is camped on the cell, or once the UE obtains SIB1 (or obtains SIB1 for the first time), based on the indication of the SIB-X validity parameters carried in SIB1 (including but not limited to valueTag, areaScope, etc.), the UE determines whether the stored WUS configuration information or SIB-X is valid.

[0266] 4) Optionally, if a system information change instruction is received and the UE obtains SIB1, the UE can determine whether the stored WUS configuration information is valid or whether it is necessary to re-obtain SIB-X based on SIB1.

[0267] 5) Optionally, if the current cell is broadcasting SIB1, then the UE verifies whether SIB-X is valid.

[0268] 6) For example, SIB-X information can be added to the si-SchedulingInfo of SIB1 or to the SIB-TypeInfo so that the UE can authenticate the validity of SIB-X. For example, SIB-X information can be added to the SIB that supports scheduling or to the SIB type information, such as adding the valueTag and / or areaScope corresponding to SIB-X.

[0269] For Case 2:

[0270] If the UE selects or reselects to cell 1, the stored WUS configuration information may be considered invalid, or it may be considered necessary to reacquire SIB-X, or the previously stored WUS configuration information may be deleted.

[0271] 1) Basic principle: After cell selection, cell reselection, or moving from outside the coverage area to within the coverage area, or receiving a system information change instruction, the UE may consider that the stored WUS configuration information is no longer valid, or that it needs to reacquire SIB-X, or that it needs to delete the previously stored WUS configuration information.

[0272] 2) Optionally, once the UE is camped in cell 1, or once the UE obtains SIB1 (or obtains SIB1 for the first time), the UE immediately obtains SIB-X.

[0273] 3) Optionally, if a system information change instruction is received and the UE obtains SIB1, the UE can determine whether the stored WUS configuration information is valid or whether it is necessary to re-obtain SIB-X based on SIB1.

[0274] 4) Optionally, if the current cell is broadcasting SIB1, then the UE verifies whether SIB-X is valid.

[0275] 5) For example, SIB-X information can be added to the si-SchedulingInfo of SIB1 or to the SIB-TypeInfo so that the UE can authenticate the validity of SIB-X. For example, SIB-X information can be added to the SIB that supports scheduling or to the SIB type information, such as adding the valueTag and / or areaScope corresponding to SIB-X.

[0276] In addition to the content described above, the embodiments of this application may also include the following solutions.

[0277] To support RLF, the simplest approach is to extend the following scheme to the cell selection process: If the UE's RRC connection re-establishment fails, the UE is advised to follow the procedures in the RRC idle / RRC inactive state to obtain SIB-X. The UE considers the WUS configuration information to be valid only in the first cell reselection after the UE obtains the WUS configuration information.

[0278] Therefore, for a UE in RRC connected state (such as an R19 NES UE), if the UE triggers RLF, the UE considers the WUS configuration information obtained from the serving cell to be valid only in the next cell selection. In the event of RRC reconstruction failure, the UE follows the procedure in RRC idle state / RRC inactive state to obtain SIB-X.

[0279] Another scenario where a connected UE needs SIB1 is when it needs to obtain OSI. In related technologies, if searchSpaceSIB1 is not configured, the UE delivers SIB1 based on the network device's dedicated RRC. If searchSpaceSIB1 is configured, the UE can monitor the broadcast SIB1. For UEs in RRC connected state (such as R19 NES UEs), the above rules can continue to be used. However, when searchSpaceSIB1 is configured, how to obtain on-demand SIB1 is a problem that needs to be considered. To address this problem, this application proposes Scheme A, that is, the UE can obtain SIB1 through the message-1 based on-demand SIB1 procedure. UEs in all RRC states can use Scheme A. In addition, this application also proposes Scheme B and Scheme C. Scheme B includes: the UE can obtain SIB1 through a dedicated RRC request. Scheme C includes: delivering SIB1 based on the network device's dedicated RRC.

[0280] In summary, for UEs in RRC connected state (such as R19 NES UEs), if the T311 timer is not running and if searchSpaceSIB1 is not configured, SIB1 is delivered based on the network device's dedicated RRC; otherwise, the UE obtains SIB1 through the Msg-1 based on-demand SIB1 procedure.

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

[0282] Figure 6 is a schematic diagram of the structure of a communication device provided in an embodiment of this application. The communication device 600 shown in Figure 6 is the first terminal device in the embodiment of Figure 2 mentioned above. The communication device 600 includes a processing unit 610. The processing unit 610 is used to perform cell selection or reselection; wherein the cell selection or reselection is associated with a first event, the first event including one or more of the following: the first terminal device detects a radio link failure; the first terminal device performs RRC reconstruction; the first terminal device transitions from an RRC connected state to an RRC idle state; the first terminal device enters an RRC idle state.

[0283] In some implementations, the processing unit 610 is configured to: perform cell selection or reselection based on first information; wherein the first information includes one or more of the following: first wake-up signal (WUS) configuration information, cell channel quality information, and cell type.

[0284] In some implementations, the processing unit 610 is used to: preferentially select or search for the cell corresponding to the first WUS configuration information; or, perform the cell selection or reselection according to a first priority, wherein the first priority is the priority of cell selection, cell reselection or cell search, and the first priority is determined based on the first WUS configuration information.

[0285] In some implementations, the first terminal device satisfies one or more of the following: supports request for common signals or channels; supports NES; and has WUS configuration information.

[0286] In some implementations, the processing unit 610 is used to: preferentially select or search for cells of a first type; wherein the cells of the first type include one or more of the following: normal cells, cells that periodically transmit System Information Block (SIB1), cells that periodically transmit Synchronization Signal Block (SSB), cells that do not support NES, NES cells that are broadcasting SIB1, and NES cells that are broadcasting SSB.

[0287] In some implementations, the first terminal device satisfies one or more of the following: does not support requesting common signals or channels; does not support NES; and does not have WUS configuration information.

[0288] In some implementations, the first terminal device is in RRC connected state before or during the cell selection or reselection process.

[0289] In some implementations, the processing unit 610 is further configured to: request, not request, or determine whether to request the first cell to send SIB1.

[0290] In some implementations, the processing unit 610 is configured to: in a first case, request, not request, or determine whether to request the first cell to send SIB1; wherein the first case includes one of the following: the first terminal device is performing the cell selection or reselection process; the first terminal device selects the first cell based on the cell selection or reselection; the first terminal device expects to select the first cell based on the cell selection or reselection.

[0291] In some implementations, the processing unit 610 is configured to: based on a second information request, not request or determine whether to request the first cell to send SIB1; wherein the second information includes one or more of the following: the type of the first cell; whether the first terminal device has first WUS configuration information.

[0292] In some implementations, the first WUS configuration information includes the WUS configuration information of the first cell.

[0293] In some implementations, the processing unit 610 is configured to: if the first cell is a first type of cell, then not request or determine not to request the first cell to send SIB1, or the first terminal device considers that it has already obtained SIB1; wherein, the first type of cell includes one or more of the following: normal cell, cell that periodically sends SIB1, cell that periodically sends SSB, cell that does not support NES, NES cell that is broadcasting SIB1, and NES cell that is broadcasting SSB.

[0294] In some implementations, the processing unit 610 is configured to: if the first cell is an NES cell and the first terminal device does not have the first WUS configuration information, then not request or determine not to request the first cell to send SIB1.

[0295] In some implementations, the processing unit 610 is further configured to perform one or more of the following: continue performing the cell selection or reselection; determine that the stored WUS configuration information is valid; and continue using the stored WUS configuration information.

[0296] In some implementations, the processing unit 610 is configured to: if the first cell is an NES cell and the first terminal device has the first WUS configuration information, request or determine to request the first cell to send SIB1.

[0297] In some implementations, the processing unit 610 is further configured to: during the cell selection or reselection process, if a first condition is met, perform one or more of the following: the first terminal device deletes previously received or saved first WUS configuration information; the first terminal device releases previously received or saved first WUS configuration information; the first terminal device determines that the previously received or saved first WUS configuration information is invalid; the first terminal device deletes previously received or saved first SIB; the first terminal device releases previously received or saved first SIB; the first terminal device determines that the previously received or saved first SIB is invalid; wherein, the first SIB is used to carry WUS configuration information.

[0298] In some implementations, the first condition includes one or more of the following: the first terminal device camps on a cell based on the cell selection or reselection; the first terminal device determines a cell as an available cell based on the cell selection or reselection; the cell selection or reselection is not the first cell selection or reselection performed by the first terminal device after obtaining the first WUS configuration information; the cell selection or reselection is not the first cell selection or reselection performed by the first terminal device after obtaining the first WUS configuration information from the camped cell; the cell selection or reselection is triggered based on RRC reconstruction; a first timer of the first terminal device times out or stops, the first timer is used for RRC reconstruction, and the first timer is triggered based on the first terminal device detecting a radio link failure; a second timer of the first terminal device times out or stops, the second timer is used for the RRC reconstruction process, and the second timer is triggered based on an RRC connection reconstruction request sent by the first terminal device; a third timer of the first terminal device times out or stops, the third timer is used for RRC connection establishment, and the third timer is triggered based on an RRC connection establishment request sent by the first terminal device.

[0299] In some implementations, the processing unit 610 is further configured to: during the cell selection or reselection process, if the second condition is met, determine that the first WUS configuration information previously received or saved by the first terminal device is valid, or not release the first WUS configuration information.

[0300] In some implementations, the second condition includes one or more of the following: the cell selection or reselection is the first cell selection or reselection performed by the first terminal device after obtaining the first WUS configuration information; during the cell selection or reselection process performed by the first terminal device, the WUS configuration is obtained or saved before the current cell selection or reselection process is performed; the first timer of the first terminal device has not timed out or stopped, the first timer is used for the RRC reconstruction process, and the first timer is triggered based on the first terminal device detecting a radio link failure; the second timer of the first terminal device has not timed out or stopped, the second timer is used for the RRC reconstruction process, and the second timer is triggered based on the RRC connection reconstruction request sent by the first terminal device; the third timer of the first terminal device has not timed out or stopped, the third timer is used for RRC connection establishment, and the third timer is triggered based on the RRC connection establishment request sent by the first terminal device.

[0301] In some implementations, the communication device 600 further includes: a communication unit, configured to: if the RRC reconstruction fails, obtain a second SIB according to a first process; and / or, if the RRC reconstruction succeeds, obtain a second SIB according to a second process, or obtain a second SIB according to a first process; wherein the second SIB is used to carry WUS configuration information, the first process corresponds to the terminal device in the RRC disconnected state, and the second process corresponds to the terminal device in the RRC connected state.

[0302] In some implementations, the first terminal device has valid first WUS configuration information or a first SIB before performing the cell selection or reselection; or, the first terminal device receives updated first WUS configuration information or a first SIB before performing the cell selection or reselection; or, the first terminal device acquires the first WUS configuration information or a first SIB for the first time before performing the cell selection or reselection; wherein, the first SIB is used to carry the first WUS configuration information.

[0303] Figure 7 is a schematic diagram of the structure of a communication device provided in another embodiment of this application. The communication device 700 shown in Figure 7 can be the first terminal device in the embodiments of Figures 3 to 6 above. The communication device 700 may include a communication unit 710. The communication unit 710 is used to receive one or more of the following: first WUS configuration information; a first SIB, wherein the first SIB is used to carry the first WUS configuration information; and SIB1 of a first cell.

[0304] In some implementations, the first WUS configuration information or the first SIB is carried in a handover command for cell handover; and / or, the first WUS configuration information or the first SIB is carried in a cell broadcast message.

[0305] In some implementations, the communication device 700 further includes a first processing unit for determining the validity of the first SIB or the first WUS configuration information.

[0306] In some implementations, the validity of the first SIB is determined based on the SIB1 of the first cell.

[0307] In some implementations, the SIB1 of the first cell includes a first parameter for determining the validity of the first SIB.

[0308] In some implementations, the first parameter includes one or more of the following: value label, area range, area value, public land mobile network (PLMN) identifier, and cell identifier.

[0309] In some implementations, the communication device 700 further includes: a second processing unit, configured to continue saving or using the first SIB or the first WUS configuration information if the first SIB is valid; and / or, if the first SIB is valid, determine that it is not necessary to update the first SIB or the first WUS configuration information.

[0310] In some implementations, the communication device 700 further includes: an execution unit for performing a first operation, the first operation including one or more of the following: receiving a second SIB sent by the first cell, the second SIB being used to carry second WUS configuration information; receiving the second WUS configuration information sent by the first cell; determining that the first WUS configuration information previously received or saved by the first terminal device is invalid; re-acquiring the WUS configuration information; the first terminal device acquiring the SIB1 of the first cell; the first terminal device requesting the second SIB from the first cell.

[0311] In some implementations, the execution unit is configured to: perform the first operation in a first case; wherein the first case includes one or more of the following: the first SIB is invalid; the first WUS configuration information is invalid; the first terminal device switches to the first cell; the first terminal device reselects to the first cell; the first terminal device connects to the first cell; the first terminal device selects to the first cell based on a cell selection process; the first terminal device resides in the first cell; the first terminal device receives an indication of a system information change; the first terminal device receives SIB1 of the first cell; the first terminal device receives SIB1 of the first cell for the first time; the first cell where the first terminal device is currently located is broadcasting SIB1.

[0312] In some implementations, the transmission of the second SIB is triggered by a first message, which satisfies one or more of the following: the first message is a message sent by the first terminal device; and / or, the first message is used to request the first cell to transmit the second SIB.

[0313] In some implementations, the first message is a dedicated SIB request message.

[0314] In some implementations, the first message is sent if a first condition is met, and the first condition is associated with one or more of the following: whether the first terminal device is configured with a search space for the second SIB; whether the first terminal device is configured with a search space for other system information OSIs; whether the first cell's SIB1 contains the second SIB; whether the system information scheduling information in the first cell's SIB1 contains the second SIB; the system information broadcast status of the second SIB in the first cell's SIB1; the system information broadcast status of the second SIB in the system information scheduling information; whether the first terminal device is configured with on-demand SIB requests; whether the first terminal device has the capability to make on-demand SIB requests; and whether a first timer is running, and the first timer is associated with the on-demand SIB request.

[0315] In some implementations, the first condition includes one or more of the following: the first terminal device is not configured with a search space for the second SIB; the first terminal device is not configured with a search space for OSI; SIB1 of the first cell contains the second SIB; the system information scheduling information contains the second SIB; the first terminal device is configured with on-demand SIB requests; the first terminal device has the capability to make on-demand SIB requests; and the third timer is not running.

[0316] In some implementations, the first condition includes one or more of the following: the first terminal device is configured with a search space for the second SIB; the first terminal device is configured with a search space for OSI; SIB1 of the first cell contains the second SIB; the system information scheduling information contains the second SIB; the system information broadcast status indicates that the second SIB is not transmitted using broadcast mode; the first terminal device is configured with on-demand SIB requests; the first terminal device has the capability of on-demand SIB requests; and the third timer is not in running state.

[0317] In some implementations, the second SIB is carried in dedicated system information delivery information.

[0318] In some implementations, the first message satisfies one of the following: the first message is an RRC system information request message; the first message is a message used to trigger the RACH procedure; the first message is a message transmitted through the RACH procedure.

[0319] In some implementations, the first message is sent if a second condition is met, the second condition being associated with one or more of the following: whether the SIB1 of the first cell contains system information scheduling information; whether the SIB1 of the first cell contains system information request configuration; whether the system information scheduling information contains system information request configuration; whether the SIB1 of the first cell contains the second SIB; whether the system information scheduling information contains the second SIB; the system information broadcast status of the second SIB in the SIB1 of the first cell; and the system information broadcast status of the second SIB in the system scheduling information.

[0320] In some implementations, the first message is a message used to trigger the RACH procedure or a message transmitted through the RACH procedure, and the second condition includes one or more of the following: the SIB1 of the first cell contains the system information scheduling information; the SIB1 of the first cell contains the system information request configuration; the system information scheduling information contains the system information request configuration; the SIB1 of the first cell contains the second SIB; the system information scheduling information contains the second SIB; the system information broadcast status indicates that the second SIB does not use broadcast mode for transmission.

[0321] In some implementations, the first message is an RRC system information request message, and the second condition includes one or more of the following: the SIB1 of the first cell contains the system information scheduling information; the SIB1 of the first cell does not contain the system information request configuration; the system information scheduling information does not contain the system information request configuration; the SIB1 of the first cell contains the second SIB; the system information scheduling information contains the second SIB; the system information broadcast status indicates that the second SIB is not transmitted using broadcast mode.

[0322] In some implementations, the communication unit 710 is further configured to: acquire or listen to the broadcast second SIB after sending the RRC system information request message.

[0323] In some implementations, the communication unit 710 is used to: if a system information request confirmation message is received from a lower layer, acquire or listen to the broadcast second SIB.

[0324] In some implementations, the execution unit is used to: acquire or listen to the second SIB broadcast by the first cell.

[0325] In some implementations, the execution unit is configured to: acquire or listen to the second SIB broadcast by the first cell when a third condition is met; wherein the third condition is associated with one or more of the following: whether the first terminal device has configured a search space for the second SIB; whether the first terminal device has configured a search space for OSI; whether the second SIB is included in SIB1 of the first cell; whether the system information scheduling information in SIB1 of the first cell includes the second SIB; the system information broadcast status of the second SIB in SIB1 of the first cell; and the system information broadcast status of the second SIB in the system information scheduling information.

[0326] In some implementations, the third condition includes one or more of the following: the first terminal device is configured with a search space for the second SIB; the first terminal device is configured with a search space for OSI; the second SIB is included in SIB1 of the first cell; the system information scheduling information includes the second SIB; the system information broadcast status indicates that the second SIB is transmitted using broadcast mode.

[0327] In some implementations, the first processing unit is configured to: determine the validity of the first SIB or the first WUS configuration information if a fourth condition is met; wherein the fourth condition includes one or more of the following: the first terminal device selects a first cell based on a cell selection process; the first terminal device selects a first cell based on a cell reselection process; the first terminal device connects to the first cell; the first terminal device camps on the first cell; the first terminal device switches from a second cell to the first cell; the first terminal device receives an indication of a system information change; the first terminal device receives SIB1 of the first cell; the first terminal device receives SIB1 of the first cell for the first time; the first cell where the first terminal device is currently located is broadcasting SIB1.

[0328] In some implementations, when the first cell sends SIB1 via a broadcast message, the SIB1 of the first cell is carried in the broadcast message of the first cell.

[0329] In some implementations, the first cell sends SIB1 via a broadcast message, including one of the following: the first cell periodically broadcasts SIB1; the first cell is a cell that requests SIB1 on demand, and the first cell is currently broadcasting SIB1.

[0330] In some implementations, when the first cell is a cell that requests SIB1 on demand, the SIB1 of the first cell is carried in the RRC dedicated message of the first terminal device.

[0331] In some implementations, the RRC dedicated message includes dedicated SIB1 delivery information, which includes the SIB1 of the first cell.

[0332] In some implementations, if the first cell is a cell that requests SIB1 on demand, the network device does not configure the search space corresponding to SIB1.

[0333] In some implementations, the network device does not configure the search space corresponding to SIB1, including one or more of the following: the network device does not broadcast the configuration information of the search space corresponding to SIB1; the handover command sent by the network device to the first terminal device does not carry the configuration information of the search space corresponding to SIB1.

[0334] In some implementations, when the first terminal device is in RRC connected state and the first terminal device is not configured with a common search space, the SIB1 of the first cell is obtained based on network device-specific RRC messages.

[0335] In some implementations, when the first terminal device is in RRC connected state and the first terminal device is configured with a common search space, the first terminal device satisfies one of the following: obtains the SIB1 of the first cell based on a network device dedicated RRC message; requests or obtains the SIB1 of the first cell based on a RACH procedure; requests or obtains the SIB1 of the first cell based on a dedicated RRC message sent by the first terminal device; or obtains the OSI of the first cell when it is not necessary to obtain the SIB1 of the first cell.

[0336] In some implementations, the communication device 710 further includes a processing unit, configured to perform cell reselection or determine that SIB1 cannot be obtained if the fifth condition is met, in the case that the first cell is a cell requesting SIB1 on demand.

[0337] In some implementations, the fifth condition includes one or more of the following: after the first terminal device camps on the first cell, the validity of the stored SIB for carrying WUS configuration information is not determined; after the first terminal device camps on the first cell, the SIB for carrying WUS configuration information is not received; after the first terminal device camps on the first cell, the valid SIB for carrying WUS configuration information is not stored.

[0338] In some implementations, the first terminal device is located in the first cell and is in an RRC connected state; or, the first terminal device is camped in the first cell and is in an RRC disconnected state.

[0339] Figure 8 is a schematic diagram of the structure of a communication device provided in another embodiment of this application. The communication device 800 shown in Figure 8 can be the network device mentioned in the embodiments of Figures 3 to 5 above. The communication device 800 may include a communication unit 810. The communication unit 810 is used to send one or more of the following: a first wake-up signal WUS configuration information; a first SIB, the first SIB being used to carry the first WUS configuration information; and SIB1 of a first cell.

[0340] In some implementations, the first WUS configuration information or the first SIB is carried in a handover command for cell handover; and / or, the first WUS configuration information or the first SIB is carried in a cell broadcast message.

[0341] In some implementations, the validity of the first SIB is determined based on the SIB1 of the first cell.

[0342] In some implementations, the SIB1 of the first cell includes a first parameter for determining the validity of the first SIB.

[0343] In some implementations, the first parameter includes one or more of the following: value label, area range, area value, PLMN identifier, and cell identifier.

[0344] In some implementations, the communication unit 810 is further configured to: send the second SIB or the second WUS configuration information of the first cell, wherein the second SIB is used to carry the second WUS configuration information.

[0345] In some implementations, the transmission of the second SIB is triggered by a first message, which satisfies one or more of the following: the first message is a message sent by a first terminal device; and / or, the first message is used to request the first cell to transmit the second SIB.

[0346] In some implementations, the first message is a dedicated SIB request message.

[0347] In some implementations, the first message is sent if a first condition is met, which is associated with one or more of the following: whether the first terminal device has configured a search space for the second SIB; whether the first terminal device has configured a search space for OSI; whether the first cell's SIB1 contains the second SIB; whether the system information scheduling information in the first cell's SIB1 contains the second SIB; the system information broadcast status of the second SIB in the first cell's SIB1; the system information broadcast status of the second SIB in the system information scheduling information; whether the first terminal device has configured on-demand SIB requests; whether the first terminal device has the capability to make on-demand SIB requests; and whether a first timer is running, and the first timer is associated with the on-demand SIB request.

[0348] In some implementations, the first condition includes one or more of the following: the first terminal device is not configured with a search space for the second SIB; the first terminal device is not configured with a search space for OSI; SIB1 of the first cell contains the second SIB; the system information scheduling information contains the second SIB; the first terminal device is configured with on-demand SIB requests; the first terminal device has the capability to make on-demand SIB requests; and the third timer is not running.

[0349] In some implementations, the first condition includes one or more of the following: the first terminal device is configured with a search space for the second SIB; the first terminal device is configured with a search space for OSI; SIB1 of the first cell contains the second SIB; the system information scheduling information contains the second SIB; the system information broadcast status indicates that the second SIB is not transmitted using broadcast mode; the first terminal device is configured with on-demand SIB requests; the first terminal device has the capability of on-demand SIB requests; and the third timer is not in running state.

[0350] In some implementations, the second SIB is carried in dedicated system information delivery information.

[0351] In some implementations, the first message satisfies one of the following: the first message is an RRC system information request message; the first message is a message used to trigger the RACH procedure; the first message is a message transmitted through the RACH procedure.

[0352] In some implementations, the first message is sent if a second condition is met, the second condition being associated with one or more of the following: whether the SIB1 of the first cell contains system information scheduling information; whether the SIB1 of the first cell contains system information request configuration; whether the system information scheduling information contains system information request configuration; whether the SIB1 of the first cell contains the second SIB; whether the system information scheduling information contains the second SIB; the system information broadcast status of the second SIB in the SIB1 of the first cell; and the system information broadcast status of the second SIB in the system scheduling information.

[0353] In some implementations, the first message is a message used to trigger the RACH procedure or a message transmitted through the RACH procedure, and the second condition includes one or more of the following: the SIB1 of the first cell contains the system information scheduling information; the SIB1 of the first cell contains the system information request configuration; the system information scheduling information contains the system information request configuration; the SIB1 of the first cell contains the second SIB; the system information scheduling information contains the second SIB; the system information broadcast status indicates that the second SIB does not use broadcast mode for transmission.

[0354] In some implementations, the first message is an RRC system information request message, and the second condition includes one or more of the following: the SIB1 of the first cell contains the system information scheduling information; the SIB1 of the first cell does not contain the system information request configuration; the system information scheduling information does not contain the system information request configuration; the SIB1 of the first cell contains the second SIB; the system information scheduling information contains the second SIB; the system information broadcast status indicates that the second SIB is not transmitted using broadcast mode.

[0355] In some implementations, the communication unit is further configured to: broadcast the second SIB after receiving the RRC system information request message;

[0356] In some implementations, the communication unit is further configured to send a system information request confirmation message to the first terminal device.

[0357] In some implementations, when the first cell sends SIB1 via a broadcast message, the SIB1 of the first cell is carried in the broadcast message of the first cell.

[0358] In some implementations, the first cell sends SIB1 via a broadcast message, including one of the following: the first cell periodically broadcasts SIB1; the first cell is a cell that requests SIB1 on demand, and the first cell is currently broadcasting SIB1.

[0359] In some implementations, when the first cell is a cell that requests SIB1 on demand, the SIB1 of the first cell is carried in the RRC dedicated message of the first terminal device.

[0360] In some implementations, the RRC dedicated message includes dedicated SIB1 delivery information, which includes the SIB1 of the first cell.

[0361] In some implementations, if the first cell is a cell that requests SIB1 on demand, the network device does not configure the search space corresponding to SIB1.

[0362] In some implementations, the network device does not configure the search space corresponding to SIB1, including one or more of the following: the network device does not broadcast the configuration information of the search space corresponding to SIB1; the handover command sent by the network device to the first terminal device does not carry the configuration information of the search space corresponding to SIB1.

[0363] In some implementations, when the first terminal device is in RRC connected state and the first terminal device is not configured with a common search space, the SIB1 of the first cell is obtained by the first terminal device based on network device-specific RRC messages.

[0364] In some implementations, when the first terminal device is in RRC connected state and the first terminal device is configured with a common search space, the first cell satisfies one of the following: the SIB1 of the first cell is obtained based on a network device-specific RRC message; the SIB1 of the first cell is obtained based on a RACH procedure; the SIB1 of the first cell is obtained based on a dedicated RRC message sent by the first terminal device; the OSI of the first cell is obtained without needing to obtain the SIB1 of the first cell.

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

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

[0367] The apparatus 900 may further include one or more memories 920. The memories 920 store a program that can be executed by the processor 910, causing the processor 910 to perform the methods described in the preceding method embodiments. The memories 920 may be independent of the processor 910 or integrated into the processor 9910.

[0368] The device 900 may also include a transceiver 930. The processor 910 can communicate with other devices or chips via the transceiver 930. For example, the processor 910 can send and receive data with other devices or chips via the transceiver 930.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Claims

1. A communication method, characterized in that, include: The first terminal device performs cell selection or reselection; The cell selection or reselection is associated with a first event, which includes one or more of the following: The first terminal device detected a wireless link failure; The first terminal device performs Radio Resource Control (RRC) reconstruction; The first terminal device enters the RRC idle state.

2. The method according to claim 1, characterized in that, The first terminal device performs cell selection or reselection, including: The first terminal device performs cell selection or reselection based on the first information; The first information includes one or more of the following: first wake-up signal (WUS) configuration information, cell type.

3. The method according to claim 2, characterized in that, The first terminal device performs cell selection or reselection based on the first information, including: The first terminal device preferentially selects or searches for the cell corresponding to the first WUS configuration information; or... The first terminal device performs cell selection or reselection according to a first priority, where the first priority is the priority of cell selection, cell reselection or cell search, and the first priority is determined based on the first WUS configuration information.

4. The method according to claim 2 or 3, characterized in that, The first terminal device satisfies one or more of the following: Support requests for public signals or channels; Supports network energy-saving NES; It contains WUS configuration information.

5. The method according to claim 2, characterized in that, The first terminal device performs cell selection or reselection based on the first information, including: The first terminal device preferentially selects or searches for cells of the first type; The first type of cell includes one or more of the following: normal cell, cell that periodically transmits System Information Block (SIB1), cell that periodically transmits Synchronization Signal Block (SSB), cell that does not support NES, NES cell that is broadcasting SIB1, and NES cell that is broadcasting SSB.

6. The method according to claim 5, characterized in that, The first terminal device satisfies one or more of the following: Requests for public signals or channels are not supported. NES is not supported. WUS configuration information is not available.

7. The method according to any one of claims 1 to 6, characterized in that, Before or during the cell selection or reselection, the first terminal device is in RRC connected state.

8. The method according to any one of claims 1 to 7, characterized in that, The method further includes: The first terminal device requests, does not request, or determines whether to request the first cell to send SIB1.

9. The method according to claim 8, characterized in that, The first terminal device requests, whether to request or determine whether to request the first cell to send SIB1, including: In the first case, the first terminal device requests, does not request, or determines whether to request the first cell to send SIB1; The first situation includes one of the following: The first terminal device is performing the cell selection or reselection process; The first terminal device selects the first cell based on the cell selection or reselection; The first terminal device selects the first cell based on the cell selection or reselection expectation.

10. The method according to claim 8 or 9, characterized in that, The first terminal device requests, or does not request or determines whether to request the first cell to send SIB1, including: The first terminal device, based on the second information request, decides whether to request the first cell to send SIB1 or not. The second information includes one or more of the following: The type of the first cell; Does the first terminal device have the first WUS configuration information? 11. The method according to claim 10, characterized in that, The first WUS configuration information includes the WUS configuration information of the first cell.

12. The method according to claim 10 or 11, characterized in that, The first terminal device, based on the second information request, decides whether to request or determine whether to request the first cell to send SIB1, including: If the first cell is a first type of cell, then the first terminal device does not request or is certain not to request the first cell to send SIB1, or the first terminal device believes that it has already obtained SIB1; The first type of cell includes one or more of the following: normal cell, cell that periodically transmits SIB1, cell that periodically transmits SSB, cell that does not support NES, NES cell that is broadcasting SIB1, and NES cell that is broadcasting SSB.

13. The method according to claim 10 or 11, characterized in that, The first terminal device, based on the second information request, decides whether to request or determine whether to request the first cell to send SIB1, including: If the first cell is an NES cell and the first terminal device does not have the first WUS configuration information, then the first terminal device does not request or determines not to request the first cell to send SIB1.

14. The method according to claim 13, characterized in that, The method further includes one or more of the following: The first terminal device continues to perform the cell selection or reselection; The first terminal device determines that the stored WUS configuration information is valid; The first terminal device continues to use the stored WUS configuration information.

15. The method according to claim 10 or 11, characterized in that, The first terminal device, based on the second information request, decides whether to request or determine whether to request the first cell to send SIB1, including: If the first cell is an NES cell and the first terminal device has the first WUS configuration information, then the first terminal device requests or confirms that the first cell sends SIB1.

16. The method according to any one of claims 1 to 15, characterized in that, The method further includes: During the cell selection or reselection process, if the first condition is met, the first terminal device performs one or more of the following: The first terminal device deletes the first WUS configuration information that was previously received or saved. The first terminal device releases the first WUS configuration information received or saved before the release; The first terminal device determines that the previously received or saved first WUS configuration information is invalid; The first terminal device deletes the first SIB that was previously received or saved. The first SIB received or stored before the first terminal device releases; The first terminal device determines that the first SIB received or stored previously is invalid; The first SIB is used to carry WUS configuration information.

17. The method according to claim 16, characterized in that, The first condition includes one or more of the following: The first terminal device chooses or reselects to camp on a cell based on the cell selection; The first terminal device determines a cell as an available cell based on the cell selection or reselection. The cell selection or reselection is not the first cell selection or reselection performed by the first terminal device after obtaining the first WUS configuration information; The cell selection or reselection is not the first cell selection or reselection performed by the first terminal device after obtaining the first WUS configuration information from the camped cell; The cell selection or reselection is based on RRC reconstruction triggering; The first timer of the first terminal device times out or stops. The first timer is used for RRC reconstruction and is triggered based on the first terminal device detecting a wireless link failure. The second timer of the first terminal device times out or stops. The second timer is used for the RRC reconstruction process and is triggered based on the RRC connection reconstruction request sent by the first terminal device. The third timer of the first terminal device times out or stops. The third timer is used for RRC connection establishment and is triggered based on the RRC connection establishment request sent by the first terminal device.

18. The method according to any one of claims 1 to 17, characterized in that, The method further includes: During the cell selection or reselection process, if the second condition is met, the first terminal device determines that the first WUS configuration information previously received or saved by the first terminal device is valid, or does not release the first WUS configuration information.

19. The method according to claim 18, characterized in that, The second condition includes one or more of the following: The cell selection or reselection is the first cell selection or reselection performed by the first terminal device after obtaining the first WUS configuration information; During the cell selection or reselection process performed by the first terminal device, the WUS configuration is acquired or saved before the current cell selection or reselection process is performed; The first timer of the first terminal device did not time out or stop. The first timer is used for the RRC reconstruction process and is triggered based on the first terminal device detecting a wireless link failure. The second timer of the first terminal device did not time out or stop. The second timer is used for the RRC reconstruction process and is triggered based on the RRC connection reconstruction request sent by the first terminal device. The third timer of the first terminal device did not time out or stop. The third timer is used for RRC connection establishment and is triggered based on the RRC connection establishment request sent by the first terminal device.

20. The method according to any one of claims 1 to 6, characterized in that, The method further includes: If the RRC reconstruction fails, the first terminal device obtains the second SIB according to the first process; and / or, If the RRC reconstruction is successful, the first terminal device obtains the second SIB according to the second process, or obtains the second SIB according to the first process; The second SIB is used to carry WUS configuration information. The first process corresponds to the terminal device in the RRC non-connected state, and the second process corresponds to the terminal device in the RRC connected state.

21. The method according to any one of claims 1 to 20, characterized in that: The first terminal device has valid first WUS configuration information or a first SIB before performing the cell selection or reselection; or, The first terminal device received updated first WUS configuration information or first SIB before performing the cell selection or reselection; or, The first terminal device obtains the first WUS configuration information or the first SIB for the first time before performing the cell selection or reselection; The first SIB is used to carry the first WUS configuration information.

22. A communication method, characterized in that, include: The first terminal device receives one or more of the following: First wake-up signal WUS configuration information; The first system information block (SIB) is used to carry the first WUS configuration information. SIB1 of the first community.

23. The method according to claim 22, characterized in that: The first WUS configuration information or the first SIB is carried in a handover command for cell handover; and / or, The first WUS configuration information or the first SIB is carried in the cell's broadcast message.

24. The method according to claim 22 or 23, characterized in that, The method further includes: The first terminal device determines the validity of the first SIB or the first WUS configuration information.

25. The method according to claim 24, characterized in that, The validity of the first SIB is determined based on the SIB1 of the first cell.

26. The method according to claim 25, characterized in that: The SIB1 of the first cell includes a first parameter for determining the validity of the first SIB.

27. The method according to claim 26, characterized in that, The first parameter includes one or more of the following: value label, area range, area value, public land mobile network (PLMN) identifier, and cell identifier.

28. The method according to any one of claims 24 to 27, characterized in that, The method further includes: If the first SIB is valid, the first terminal device continues to save or use the first SIB or the first WUS configuration information; and / or, If the first SIB is valid, the first terminal device determines that it does not need to update the first SIB or the first WUS configuration information.

29. The method according to any one of claims 22 to 28, characterized in that, The method further includes: The first terminal device performs a first operation, which includes one or more of the following: Receive the second SIB sent by the first cell, the second SIB being used to carry the second WUS configuration information; Receive the second WUS configuration information sent by the first cell; It is determined that the first WUS configuration information previously received or saved by the first terminal device is invalid; Reacquire WUS configuration information; The first terminal device obtains the SIB1 of the first cell; The first terminal device requests a second SIB from the first cell.

30. The method according to claim 29, characterized in that, The first terminal device performs a first operation, including: In the first case, the first terminal device performs the first operation; The first situation includes one or more of the following: The first SIB is invalid; The first WUS configuration information is invalid; The first terminal device switches to the first cell; The first terminal device reselects to the first cell; The first terminal device is connected to the first cell; The first terminal device selects the first cell based on the cell selection process; The first terminal device resides in the first cell; The first terminal device receives an indication of a system information change; The first terminal device receives SIB1 from the first cell; The first terminal device receives SIB1 of the first cell for the first time; The first cell where the first terminal device is currently located is broadcasting SIB1.

31. The method according to claim 29 or 30, characterized in that, The transmission of the second SIB is triggered by a first message, which satisfies one or more of the following: The first message is a message sent by the first terminal device; and / or, The first message is used to request the first cell to send the second SIB.

32. The method according to claim 31, characterized in that... ； The first message is a dedicated SIB request message.

33. The method according to claim 31 or 32, characterized in that, The first message is sent if a first condition is met, and the first condition is associated with one or more of the following: Whether the first terminal device is configured with a search space for the second SIB; Does the first terminal device have an OSI search space for other system information? Does the first cell's SIB1 contain the second SIB? Does the system information scheduling information in SIB1 of the first cell include the second SIB? The system information broadcast status of the second SIB in SIB1 of the first cell; The system information broadcast status of the second SIB in the system information scheduling information; Whether the first terminal device is configured with on-demand SIB requests; Does the first terminal device have the capability to request SIBs on demand? Whether the first timer is in running state, and whether the first timer is associated with the on-demand SIB request.

34. The method according to claim 33, characterized in that, The first condition includes one or more of the following: The first terminal device is not configured with a search space for the second SIB; The first terminal device is not configured with an OSI search space; The first cell's SIB1 includes the second SIB; The system information scheduling information includes the second SIB; The first terminal device is configured with on-demand SIB requests; The first terminal device has the ability to request SIBs on demand; The third timer is not running.

35. The method according to claim 33, characterized in that, The first condition includes one or more of the following: The first terminal device is configured with a search space for the second SIB; The first terminal device is configured with an OSI search space; The first cell's SIB1 includes the second SIB; The system information scheduling information includes the second SIB; The system information broadcast status indicates that the second SIB is not using broadcast transmission; The first terminal device is configured with on-demand SIB requests; The first terminal device has the ability to request SIBs on demand; The third timer is not running.

36. The method according to any one of claims 33 to 35, characterized in that, The second SIB is carried in dedicated system information delivery information.

37. The method according to claim 31, characterized in that, The first message satisfies one of the following: The first message is an RRC system information request message; The first message is a message used to trigger the Random Access Channel (RACH) procedure; The first message is a message transmitted via the RACH process.

38. The method according to claim 31 or 37, characterized in that, The first message is sent if a second condition is met, and the second condition is associated with one or more of the following: Does the SIB1 of the first cell contain system information and scheduling information? Does the SIB1 of the first cell contain a system information request configuration? Does the system information scheduling information include system information request configuration? Does the first cell's SIB1 contain the second SIB? Does the system information scheduling information include the second SIB? The system information broadcast status of the second SIB in SIB1 of the first cell; The system information broadcast status of the second SIB in the system scheduling information.

39. The method according to claim 38, characterized in that, The first message is a message used to trigger the RACH process or a message transmitted through the RACH process, and the second condition includes one or more of the following: The SIB1 of the first cell contains the system information scheduling information; The SIB1 of the first cell contains the system information request configuration; The system information scheduling information includes system information request configuration; The first cell's SIB1 includes the second SIB; The system information scheduling information includes the second SIB; The system information broadcast status indicates that the second SIB does not use broadcast transmission.

40. The method according to claim 38, characterized in that, The first message is an RRC system information request message, and the second condition includes one or more of the following: The SIB1 of the first cell contains the system information scheduling information; The SIB1 of the first cell does not contain system information request configuration; The system information scheduling information does not include system information request configuration; The first cell's SIB1 includes the second SIB; The system information scheduling information includes the second SIB; The system information broadcast status indicates that the second SIB does not use broadcast transmission.

41. The method according to claim 37 or 38, characterized in that, The method further includes: After sending the RRC system information request message, the first terminal device acquires or listens to the broadcast of the second SIB.

42. The method according to claim 41, characterized in that, The first terminal device acquires or listens to the broadcast of the second SIB, including: If a system information request confirmation message is received from a lower layer, the first terminal device acquires or listens to the broadcast of the second SIB.

43. The method according to claim 29, characterized in that, The first terminal device performs a first operation, including: The first terminal device acquires or listens to the second SIB broadcast by the first cell.

44. The method according to claim 43, characterized in that, The first terminal device acquires or listens to the second SIB broadcast by the first cell, including: If the third condition is met, the first terminal device acquires or listens to the second SIB broadcast by the first cell. The third condition is associated with one or more of the following: Whether the first terminal device is configured with a search space for the second SIB; Does the first terminal device have an OSI search space configured? Does the first cell's SIB1 contain the second SIB? Does the system information scheduling information in SIB1 of the first cell include the second SIB? The system information broadcast status of the second SIB in SIB1 of the first cell; The system information broadcast status of the second SIB in the system information scheduling information.

45. The method according to claim 44, characterized in that, The third condition includes one or more of the following: The first terminal device is configured with a search space for the second SIB; The first terminal device is configured with an OSI search space; The first cell's SIB1 includes the second SIB; The system information scheduling information includes the second SIB; The system information broadcast status indicates that the second SIB uses broadcast mode for transmission.

46. ​​The method according to any one of claims 24 to 28, characterized in that, The first terminal device determines the validity of the first SIB or the first WUS configuration information, including: If the fourth condition is met, the first terminal device determines the validity of the first SIB or the first WUS configuration information. The fourth condition includes one or more of the following: The first terminal device selected the first cell based on the cell selection process; The first terminal device selected the first cell based on the cell reselection process; The first terminal device is connected to the first cell; The first terminal device is hosted in the first cell; The first terminal device switches from the second cell to the first cell; The first terminal device receives an indication of a system information change; The first terminal device receives SIB1 from the first cell; The first terminal device receives SIB1 of the first cell for the first time; The first cell where the first terminal device is currently located is broadcasting SIB1.

47. The method according to any one of claims 22 to 46, characterized in that, When the first cell sends SIB1 via a broadcast message, the SIB1 of the first cell is carried in the broadcast message of the first cell.

48. The method according to claim 47, characterized in that, The first cell sends SIB1 via broadcast message, including one of the following: The first cell periodically broadcasts SIB1; The first cell is a cell that requests SIB1 on demand, and the first cell is broadcasting SIB1.

49. The method according to any one of claims 22 to 46, characterized in that, In the case that the first cell is a cell that requests SIB1 on demand, the SIB1 of the first cell is carried in the RRC dedicated message of the first terminal device.

50. The method according to claim 49, characterized in that, The RRC dedicated message includes dedicated SIB1 delivery information, which includes the SIB1 of the first cell.

51. The method according to any one of claims 42 to 50, characterized in that, If the first cell is a cell that requests SIB1 on demand, then the network device does not configure the search space corresponding to SIB1.

52. The method according to claim 51, characterized in that, The network device does not configure a search space corresponding to SIB1, including one or more of the following: The network device does not broadcast the configuration information of the search space corresponding to SIB1; The switching command sent by the network device to the first terminal device does not carry the configuration information of the search space corresponding to SIB1.

53. The method according to claim 22, characterized in that, When the first terminal device is in RRC connected state and the first terminal device is not configured with a common search space, the SIB1 of the first cell is obtained based on network device dedicated RRC messages.

54. The method according to claim 22, characterized in that, When the first terminal device is in RRC connected state and the first terminal device is configured with a common search space, the first terminal device satisfies one of the following: The SIB1 of the first cell is obtained based on the network device-specific RRC message; The SIB1 of the first cell is requested or obtained based on the RACH procedure; Based on the dedicated RRC message sent by the first terminal device, request or obtain the SIB1 of the first cell; Obtain the OSI of the first cell without needing to obtain the SIB1 of the first cell.

55. The method according to claim 22, characterized in that, The method further includes: If the first cell is a cell that requests SIB1 on demand, and the fifth condition is met, the first terminal device will perform cell reselection or determine that it cannot obtain SIB1.

56. The method according to claim 55, characterized in that, The fifth condition includes one or more of the following: After the first terminal device camps on the first cell, the validity of the SIB stored to carry WUS configuration information is not determined; After the first terminal device camped on the first cell, it did not receive the SIB used to carry WUS configuration information; After the first terminal device is stationed in the first cell, it does not store a valid SIB for carrying WUS configuration information.

57. The method according to any one of claims 22 to 56, characterized in that: The first terminal device is located in the first cell, and the first terminal device is in RRC connection state; or, The first terminal device is camped in the first cell and is in an RRC non-connected state.

58. A communication method, characterized in that, include: The network device sends one or more of the following: First wake-up signal WUS configuration information; The first system information block (SIB) is used to carry the first WUS configuration information. SIB1 of the first community.

59. The method according to claim 58, characterized in that: The first WUS configuration information or the first SIB is carried in a handover command for cell handover; and / or, The first WUS configuration information or the first SIB is carried in the cell's broadcast message.

60. The method according to claim 58 or 59, characterized in that, The validity of the first SIB is determined based on the SIB1 of the first cell.

61. The method according to claim 60, characterized in that: The SIB1 of the first cell includes a first parameter for determining the validity of the first SIB.

62. The method according to claim 61, characterized in that, The first parameter includes one or more of the following: value label, area range, area value, public land mobile network (PLMN) identifier, and cell identifier.

63. The method according to any one of claims 58 to 62, characterized in that, The method further includes: The network device sends the second SIB or the second WUS configuration information of the first cell, wherein the second SIB is used to carry the second WUS configuration information.

64. The method according to claim 63, characterized in that, The transmission of the second SIB is triggered by a first message, which satisfies one or more of the following: The first message is a message sent by the first terminal device; and / or, The first message is used to request the first cell to send the second SIB.

65. The method according to claim 64, characterized in that... ； The first message is a dedicated SIB request message.

66. The method according to claim 64 or 65, characterized in that, The first message is sent if a first condition is met, and the first condition is associated with one or more of the following: Whether the first terminal device is configured with a search space for the second SIB; Does the first terminal device have an OSI search space for other system information? Does the first cell's SIB1 contain the second SIB? Does the system information scheduling information in SIB1 of the first cell include the second SIB? The system information broadcast status of the second SIB in SIB1 of the first cell; The system information broadcast status of the second SIB in the system information scheduling information; Whether the first terminal device is configured with on-demand SIB requests; Does the first terminal device have the capability to request SIBs on demand? Whether the first timer is in running state, and whether the first timer is associated with the on-demand SIB request.

67. The method according to claim 66, characterized in that, The first condition includes one or more of the following: The first terminal device is not configured with a search space for the second SIB; The first terminal device is not configured with an OSI search space; The first cell's SIB1 includes the second SIB; The system information scheduling information includes the second SIB; The first terminal device is configured with on-demand SIB requests; The first terminal device has the ability to request SIBs on demand; The third timer is not running.

68. The method according to claim 66, characterized in that, The first condition includes one or more of the following: The first terminal device is configured with a search space for the second SIB; The first terminal device is configured with an OSI search space; The first cell's SIB1 includes the second SIB; The system information scheduling information includes the second SIB; The system information broadcast status indicates that the second SIB is not using broadcast transmission; The first terminal device is configured with on-demand SIB requests; The first terminal device has the ability to request SIBs on demand; The third timer is not running.

69. The method according to any one of claims 65 to 68, characterized in that, The second SIB is carried in dedicated system information delivery information.

70. The method according to claim 64, characterized in that, The first message satisfies one of the following: The first message is an RRC system information request message; The first message is a message used to trigger the Random Access Channel (RACH) procedure; The first message is a message transmitted via the RACH process.

71. The method according to claim 64 or 70, characterized in that, The first message is sent if a second condition is met, and the second condition is associated with one or more of the following: Does the SIB1 of the first cell contain system information and scheduling information? Does the SIB1 of the first cell contain a system information request configuration? Does the system information scheduling information include system information request configuration? Does the first cell's SIB1 contain the second SIB? Does the system information scheduling information include the second SIB? The system information broadcast status of the second SIB in SIB1 of the first cell; The system information broadcast status of the second SIB in the system scheduling information.

72. The method according to claim 71, characterized in that, The first message is a message used to trigger the RACH process or a message transmitted through the RACH process, and the second condition includes one or more of the following: The SIB1 of the first cell contains the system information scheduling information; The SIB1 of the first cell contains the system information request configuration; The system information scheduling information includes system information request configuration; The first cell's SIB1 includes the second SIB; The system information scheduling information includes the second SIB; The system information broadcast status indicates that the second SIB does not use broadcast transmission.

73. The method according to claim 71, characterized in that, The first message is an RRC system information request message, and the second condition includes one or more of the following: The SIB1 of the first cell contains the system information scheduling information; The SIB1 of the first cell does not contain system information request configuration; The system information scheduling information does not include system information request configuration; The first cell's SIB1 includes the second SIB; The system information scheduling information includes the second SIB; The system information broadcast status indicates that the second SIB does not use broadcast transmission.

74. [Amended according to Rule 26, 21.02.2025] The method according to claim 70 or 71, characterized in that, The method further includes: After receiving the RRC system information request message, the network device broadcasts the second SIB.

75. The method according to claim 74, characterized in that, The method further includes: The network device sends a system information request confirmation message to the first terminal device.

76. The method according to any one of claims 58 to 75, characterized in that, When the first cell sends SIB1 via a broadcast message, the SIB1 of the first cell is carried in the broadcast message of the first cell.

77. The method according to claim 76, characterized in that, The first cell sends SIB1 via broadcast message, including one of the following: The first cell periodically broadcasts SIB1; The first cell is a cell that requests SIB1 on demand, and the first cell is broadcasting SIB1.

78. The method according to any one of claims 58 to 75, characterized in that, In the case that the first cell is a cell that requests SIB1 on demand, the SIB1 of the first cell is carried in the RRC dedicated message of the first terminal device.

79. The method according to claim 78, characterized in that, The RRC dedicated message includes dedicated SIB1 delivery information, which includes the SIB1 of the first cell.

80. The method according to any one of claims 58 to 79, characterized in that, If the first cell is a cell that requests SIB1 on demand, then the network device does not configure the search space corresponding to SIB1.

81. The method according to claim 80, characterized in that, The network device does not configure a search space corresponding to SIB1, including one or more of the following: The network device does not broadcast the configuration information of the search space corresponding to SIB1; The switching command sent by the network device to the first terminal device does not carry the configuration information of the search space corresponding to SIB1.

82. The method according to claim 58, characterized in that, When the first terminal device is in RRC connected state and the first terminal device has not configured a common search space, the SIB1 of the first cell is obtained by the first terminal device based on the network device dedicated RRC message.

83. The method according to claim 58, characterized in that, When the first terminal device is in RRC connected state and the first terminal device is configured with a common search space, the first cell satisfies one of the following: The SIB1 of the first cell is obtained based on network device-specific RRC messages; The SIB1 of the first cell is obtained based on the RACH procedure; The SIB1 of the first cell is obtained based on the dedicated RRC message sent by the first terminal device; The OSI of the first cell is obtained without needing to obtain the SIB1 of the first cell.

84. A communication device, characterized in that, The communication device is a first terminal device, which includes: The processing unit is used to perform cell selection or reselection; The cell selection or reselection is associated with a first event, which includes one or more of the following: The first terminal device detected a wireless link failure; The first terminal device performs Radio Resource Control (RRC) reconstruction; The first terminal device enters the RRC idle state.

85. The communication device according to claim 84, characterized in that, The processing unit is used for: The cell selection or reselection is performed based on the first information; The first information includes one or more of the following: first wake-up signal (WUS) configuration information, cell type.

86. The communication device according to claim 85, characterized in that, The processing unit is used for: Prioritize selecting or searching for the cell corresponding to the first WUS configuration information; or, The cell selection or reselection is performed according to a first priority, where the first priority is the priority of cell selection, cell reselection, or cell search, and the first priority is determined based on the first WUS configuration information.

87. The communication device according to claim 85 or 86, characterized in that, The first terminal device satisfies one or more of the following: Support requests for public signals or channels; Supports network energy-saving NES; It contains WUS configuration information.

88. The communication device according to claim 85, characterized in that, The processing unit is used for: Prioritize or search for the first type of community; The first type of cell includes one or more of the following: normal cell, cell that periodically transmits System Information Block (SIB1), cell that periodically transmits Synchronization Signal Block (SSB), cell that does not support NES, NES cell that is broadcasting SIB1, and NES cell that is broadcasting SSB.

89. The communication device according to claim 88, characterized in that, The first terminal device satisfies one or more of the following: Requests for common signals or channels are not supported. NES is not supported. WUS configuration information is not available.

90. The communication device according to any one of claims 84 to 89, characterized in that, Before or during the cell selection or reselection process, the first terminal device is in RRC connected state.

91. The communication device according to any one of claims 84 to 90, characterized in that, The processing unit is also used for: Request, do not request, or determine whether to request the first cell to send SIB1.

92. The communication device according to claim 91, characterized in that, The processing unit is used for: In the first case, request, do not request, or determine whether to request the first cell to send SIB1; The first situation includes one of the following: The first terminal device is performing the cell selection or reselection process; The first terminal device selects the first cell based on the cell selection or reselection; The first terminal device selects the first cell based on the cell selection or reselection expectation.

93. The communication device according to claim 91 or 92, characterized in that, The processing unit is used for: Based on the second information request, it is determined whether to request the first cell to send SIB1 or not. The second information includes one or more of the following: The type of the first cell; Does the first terminal device have the first WUS configuration information? 94. The communication device according to claim 93, characterized in that, The first WUS configuration information includes the WUS configuration information of the first cell.

95. The communication device according to claim 93 or 94, characterized in that, The processing unit is used for: If the first cell is a first type of cell, then the first terminal device does not request or determines that it does not request the first cell to send SIB1, or the first terminal device believes that it has already obtained SIB1; The first type of cell includes one or more of the following: normal cell, cell that periodically transmits SIB1, cell that periodically transmits SSB, cell that does not support NES, NES cell that is broadcasting SIB1, and NES cell that is broadcasting SSB.

96. The communication device according to claim 93 or 94, characterized in that, The processing unit is used for: If the first cell is an NES cell and the first terminal device does not have the first WUS configuration information, then it does not request or determines that it will not request the first cell to send SIB1.

97. The communication device according to claim 96, characterized in that, The processing unit is also configured to perform one or more of the following: Continue with the cell selection or reselection process. Confirm that the stored WUS configuration information is valid; Continue using the stored WUS configuration information.

98. The communication device according to claim 93 or 94, characterized in that, The processing unit is used for: If the first cell is an NES cell and the first terminal device has the first WUS configuration information, then request or confirm request the first cell to send SIB1.

99. The communication device according to any one of claims 84 to 98, characterized in that, The processing unit is also used for: During the cell selection or reselection process, if the first condition is met, one or more of the following actions are performed: The first terminal device deletes the first WUS configuration information that was previously received or saved. The first terminal device releases the first WUS configuration information received or saved before the release; The first terminal device determines that the previously received or saved first WUS configuration information is invalid; The first terminal device deletes the first SIB that was previously received or saved. The first SIB received or stored before the first terminal device releases; The first terminal device determines that the first SIB received or stored previously is invalid; The first SIB is used to carry WUS configuration information.

100. The communication device according to claim 99, characterized in that, The first condition includes one or more of the following: The first terminal device chooses or reselects to camp on a cell based on the cell selection; The first terminal device determines a cell as an available cell based on the cell selection or reselection. The cell selection or reselection is not the first cell selection or reselection performed by the first terminal device after obtaining the first WUS configuration information; The cell selection or reselection is not the first cell selection or reselection performed by the first terminal device after obtaining the first WUS configuration information from the camped cell; The cell selection or reselection is based on RRC reconstruction triggering; The first timer of the first terminal device times out or stops. The first timer is used for RRC reconstruction and is triggered based on the first terminal device detecting a wireless link failure. The second timer of the first terminal device times out or stops. The second timer is used for the RRC reconstruction process and is triggered based on the RRC connection reconstruction request sent by the first terminal device. The third timer of the first terminal device times out or stops. The third timer is used for RRC connection establishment and is triggered based on the RRC connection establishment request sent by the first terminal device.

101. The communication device according to any one of claims 84 to 100, characterized in that, The processing unit is also used for: During the cell selection or reselection process, if the second condition is met, the first WUS configuration information previously received or saved by the first terminal device is determined to be valid, or the first WUS configuration information is not released.

102. The communication device according to claim 101, characterized in that, The second condition includes one or more of the following: The cell selection or reselection is the first cell selection or reselection performed by the first terminal device after obtaining the first WUS configuration information; During the cell selection or reselection process performed by the first terminal device, the WUS configuration is acquired or saved before the current cell selection or reselection process is performed; The first timer of the first terminal device did not time out or stop. The first timer is used for the RRC reconstruction process and is triggered based on the first terminal device detecting a wireless link failure. The second timer of the first terminal device did not time out or stop. The second timer is used for the RRC reconstruction process and is triggered based on the RRC connection reconstruction request sent by the first terminal device. The third timer of the first terminal device did not time out or stop. The third timer is used for RRC connection establishment and is triggered based on the RRC connection establishment request sent by the first terminal device.

103. The communication device according to any one of claims 84 to 89, characterized in that, The communication device also includes: Communication unit, used for: If the RRC reconstruction fails, a second SIB is obtained according to the first procedure; and / or, If the RRC reconstruction is successful, the second SIB is obtained according to the second process, or the second SIB is obtained according to the first process; The second SIB is used to carry WUS configuration information. The first process corresponds to the terminal device in the RRC non-connected state, and the second process corresponds to the terminal device in the RRC connected state.

104. The communication device according to any one of claims 84 to 103, characterized in that: The first terminal device has valid first WUS configuration information or a first SIB before performing the cell selection or reselection; or, The first terminal device received updated first WUS configuration information or first SIB before performing the cell selection or reselection; or, The first terminal device obtains the first WUS configuration information or the first SIB for the first time before performing the cell selection or reselection; The first SIB is used to carry the first WUS configuration information.

105. A communication device, characterized in that, The communication device is a first terminal device, which includes: A communication unit for receiving one or more of the following: First wake-up signal WUS configuration information; The first system information block (SIB) is used to carry the first WUS configuration information. SIB1 of the first community.

106. The communication device according to claim 105, characterized in that: The first WUS configuration information or the first SIB is carried in a handover command for cell handover; and / or, The first WUS configuration information or the first SIB is carried in the cell's broadcast message.

107. The communication device according to claim 105 or 106, characterized in that, The communication device also includes: The first processing unit is used to determine the validity of the first SIB or the first WUS configuration information.

108. The communication device according to claim 107, characterized in that, The validity of the first SIB is determined based on the SIB1 of the first cell.

109. The communication device according to claim 108, characterized in that: The SIB1 of the first cell includes a first parameter for determining the validity of the first SIB.

110. The communication device according to claim 109, characterized in that, The first parameter includes one or more of the following: value label, area range, area value, public land mobile network (PLMN) identifier, and cell identifier.

111. The communication device according to any one of claims 107 to 110, characterized in that, The communication device also includes: The second processing unit is configured to, if the first SIB is valid, continue to save or use the first SIB or the first WUS configuration information; and / or, If the first SIB is valid, then it is determined that there is no need to update the first SIB or the first WUS configuration information.

112. The communication device according to any one of claims 105 to 111, characterized in that, The communication device also includes: An execution unit is configured to perform a first operation, the first operation including one or more of the following: Receive the second SIB sent by the first cell, the second SIB being used to carry the second WUS configuration information; Receive the second WUS configuration information sent by the first cell; It is determined that the first WUS configuration information previously received or saved by the first terminal device is invalid; Reacquire WUS configuration information; The first terminal device obtains the SIB1 of the first cell; The first terminal device requests a second SIB from the first cell.

113. The communication device according to claim 112, characterized in that, The execution unit is used for: In the first case, perform the first operation; The first situation includes one or more of the following: The first SIB is invalid; The first WUS configuration information is invalid; The first terminal device switches to the first cell; The first terminal device reselects to the first cell; The first terminal device is connected to the first cell; The first terminal device selects the first cell based on the cell selection process; The first terminal device resides in the first cell; The first terminal device receives an indication of a system information change; The first terminal device receives SIB1 from the first cell; The first terminal device receives SIB1 of the first cell for the first time; The first cell where the first terminal device is currently located is broadcasting SIB1.

114. The communication device according to claim 112 or 113, characterized in that, The transmission of the second SIB is triggered by a first message, which satisfies one or more of the following: The first message is a message sent by the first terminal device; and / or, The first message is used to request the first cell to send the second SIB.

115. The communication device according to claim 114, characterized in that... ； The first message is a dedicated SIB request message.

116. The communication device according to claim 114 or 115, characterized in that, The first message is sent if a first condition is met, and the first condition is associated with one or more of the following: Whether the first terminal device is configured with a search space for the second SIB; Does the first terminal device have an OSI search space for other system information? Does the first cell's SIB1 contain the second SIB? Does the system information scheduling information in SIB1 of the first cell include the second SIB? The system information broadcast status of the second SIB in SIB1 of the first cell; The system information broadcast status of the second SIB in the system information scheduling information; Whether the first terminal device is configured with on-demand SIB requests; Does the first terminal device have the capability to request SIBs on demand? Whether the first timer is in running state, and whether the first timer is associated with the on-demand SIB request.

117. The communication device according to claim 116, characterized in that, The first condition includes one or more of the following: The first terminal device is not configured with a search space for the second SIB; The first terminal device is not configured with an OSI search space; The first cell's SIB1 includes the second SIB; The system information scheduling information includes the second SIB; The first terminal device is configured with on-demand SIB requests; The first terminal device has the ability to request SIBs on demand; The third timer is not running.

118. The communication device according to claim 116, characterized in that, The first condition includes one or more of the following: The first terminal device is configured with a search space for the second SIB; The first terminal device is configured with an OSI search space; The first cell's SIB1 includes the second SIB; The system information scheduling information includes the second SIB; The system information broadcast status indicates that the second SIB is not using broadcast transmission; The first terminal device is configured with on-demand SIB requests; The first terminal device has the ability to request SIBs on demand; The third timer is not running.

119. The communication device according to any one of claims 115 to 118, characterized in that, The second SIB is carried in dedicated system information delivery information.

120. The communication device according to claim 114, characterized in that, The first message satisfies one of the following: The first message is an RRC system information request message; The first message is a message used to trigger the Random Access Channel (RACH) procedure; The first message is a message transmitted via the RACH process.

121. The communication device according to claim 114 or 120, characterized in that, The first message is sent if a second condition is met, and the second condition is associated with one or more of the following: Does the SIB1 of the first cell contain system information and scheduling information? Does the SIB1 of the first cell contain a system information request configuration? Does the system information scheduling information include system information request configuration? Does the first cell's SIB1 contain the second SIB? Does the system information scheduling information include the second SIB? The system information broadcast status of the second SIB in SIB1 of the first cell; The system information broadcast status of the second SIB in the system scheduling information.

122. The communication device according to claim 121, characterized in that, The first message is a message used to trigger the RACH process or a message transmitted through the RACH process, and the second condition includes one or more of the following: The SIB1 of the first cell contains the system information scheduling information; The SIB1 of the first cell contains the system information request configuration; The system information scheduling information includes system information request configuration; The first cell's SIB1 includes the second SIB; The system information scheduling information includes the second SIB; The system information broadcast status indicates that the second SIB does not use broadcast transmission.

123. The communication device according to claim 121, characterized in that, The first message is an RRC system information request message, and the second condition includes one or more of the following: The SIB1 of the first cell contains the system information scheduling information; The SIB1 of the first cell does not contain system information request configuration; The system information scheduling information does not include system information request configuration; The first cell's SIB1 includes the second SIB; The system information scheduling information includes the second SIB; The system information broadcast status indicates that the second SIB does not use broadcast transmission.

124. The communication device according to claim 120 or 121, characterized in that, The communication unit is also used for: After sending the RRC system information request message, acquire or listen for the second SIB broadcast.

125. The communication device according to claim 124, characterized in that, The communication unit is used for: If a system information request confirmation message is received from a lower layer, the second SIB broadcast is acquired or listened to.

126. The communication device according to claim 112, characterized in that, The execution unit is used for: Acquire or listen to the second SIB broadcast by the first cell.

127. The communication device according to claim 126, characterized in that, The execution unit is used for: If the third condition is met, acquire or listen to the second SIB broadcast by the first cell; The third condition is associated with one or more of the following: Whether the first terminal device is configured with a search space for the second SIB; Does the first terminal device have an OSI search space configured? Does the first cell's SIB1 contain the second SIB? Does the system information scheduling information in SIB1 of the first cell include the second SIB? The system information broadcast status of the second SIB in SIB1 of the first cell; The system information broadcast status of the second SIB in the system information scheduling information.

128. The communication device according to claim 127, characterized in that, The third condition includes one or more of the following: The first terminal device is configured with a search space for the second SIB; The first terminal device is configured with an OSI search space; The first cell's SIB1 includes the second SIB; The system information scheduling information includes the second SIB; The system information broadcast status indicates that the second SIB uses broadcast mode for transmission.

129. The communication device according to any one of claims 107 to 111, characterized in that, The first processing unit is used for: If the fourth condition is met, the validity of the first SIB or the first WUS configuration information is determined. The fourth condition includes one or more of the following: The first terminal device selected the first cell based on the cell selection process; The first terminal device selected the first cell based on the cell reselection process; The first terminal device is connected to the first cell; The first terminal device is hosted in the first cell; The first terminal device switches from the second cell to the first cell; The first terminal device receives an indication of a system information change; The first terminal device receives SIB1 from the first cell; The first terminal device receives SIB1 of the first cell for the first time; The first cell where the first terminal device is currently located is broadcasting SIB1.

130. The communication device according to any one of claims 105 to 129, characterized in that, When the first cell sends SIB1 via a broadcast message, the SIB1 of the first cell is carried in the broadcast message of the first cell.

131. The communication device according to claim 130, characterized in that, The first cell sends SIB1 via broadcast message, including one of the following: The first cell periodically broadcasts SIB1; The first cell is a cell that requests SIB1 on demand, and the first cell is broadcasting SIB1.

132. The communication device according to any one of claims 105 to 129, characterized in that, In the case that the first cell is a cell that requests SIB1 on demand, the SIB1 of the first cell is carried in the RRC dedicated message of the first terminal device.

133. The communication device according to claim 132, characterized in that, The RRC dedicated message includes dedicated SIB1 delivery information, which includes the SIB1 of the first cell.

134. The communication device according to any one of claims 105 to 133, characterized in that, If the first cell is a cell that requests SIB1 on demand, then the network device does not configure the search space corresponding to SIB1.

135. The communication device according to claim 134, characterized in that, The network device does not configure a search space corresponding to SIB1, including one or more of the following: The network device does not broadcast the configuration information of the search space corresponding to SIB1; The switching command sent by the network device to the first terminal device does not carry the configuration information of the search space corresponding to SIB1.

136. The communication device according to claim 105, characterized in that, When the first terminal device is in RRC connected state and the first terminal device is not configured with a common search space, the SIB1 of the first cell is obtained based on network device dedicated RRC messages.

137. The communication device according to claim 105, characterized in that, When the first terminal device is in RRC connected state and the first terminal device is configured with a common search space, the first terminal device satisfies one of the following: The SIB1 of the first cell is obtained based on the network device-specific RRC message; The SIB1 of the first cell is requested or obtained based on the RACH procedure; Based on the dedicated RRC message sent by the first terminal device, request or obtain the SIB1 of the first cell; Obtain the OSI of the first cell without needing to obtain the SIB1 of the first cell.

138. The communication device according to claim 105, characterized in that, The communication device also includes: The processing unit is configured to, if the fifth condition is met, perform cell reselection or determine that SIB1 cannot be obtained when the first cell is a cell that requests SIB1 on demand.

139. The communication device according to claim 138, characterized in that, The fifth condition includes one or more of the following: After the first terminal device camps on the first cell, the validity of the SIB stored to carry WUS configuration information is not determined; After the first terminal device camped on the first cell, it did not receive the SIB used to carry WUS configuration information; After the first terminal device is stationed in the first cell, it does not store a valid SIB for carrying WUS configuration information.

140. The communication device according to any one of claims 105 to 139, characterized in that: The first terminal device is located in the first cell, and the first terminal device is in RRC connection state; or, The first terminal device is camped in the first cell and is in an RRC non-connected state.

141. A communication device, characterized in that, The communication device is a network device, and the network device includes: A communication unit for transmitting one or more of the following: First wake-up signal WUS configuration information; The first system information block (SIB) is used to carry the first WUS configuration information. SIB1 of the first community.

142. The communication device according to claim 141, characterized in that: The first WUS configuration information or the first SIB is carried in a handover command for cell handover; and / or, The first WUS configuration information or the first SIB is carried in the cell's broadcast message.

143. The communication device according to claim 141 or 142, characterized in that, The validity of the first SIB is determined based on the SIB1 of the first cell.

144. The communication device according to claim 143, characterized in that: The SIB1 of the first cell includes a first parameter for determining the validity of the first SIB.

145. The communication device according to claim 144, characterized in that, The first parameter includes one or more of the following: value label, area range, area value, public land mobile network (PLMN) identifier, and cell identifier.

146. The communication device according to any one of claims 141 to 145, characterized in that, The communication unit is also used for: Send the second SIB or second WUS configuration information of the first cell, wherein the second SIB is used to carry the second WUS configuration information.

147. The communication device according to claim 146, characterized in that, The transmission of the second SIB is triggered by a first message, which satisfies one or more of the following: The first message is a message sent by the first terminal device; and / or, The first message is used to request the first cell to send the second SIB.

148. The communication device according to claim 147, characterized in that... ； The first message is a dedicated SIB request message.

149. The communication device according to claim 147 or 148, characterized in that, The first message is sent if a first condition is met, and the first condition is associated with one or more of the following: Whether the first terminal device is configured with a search space for the second SIB; Does the first terminal device have an OSI search space for other system information? Does the first cell's SIB1 contain the second SIB? Does the system information scheduling information in SIB1 of the first cell include the second SIB? The system information broadcast status of the second SIB in SIB1 of the first cell; The system information broadcast status of the second SIB in the system information scheduling information; Whether the first terminal device is configured with on-demand SIB requests; Does the first terminal device have the capability to request SIBs on demand? Whether the first timer is in running state, and whether the first timer is associated with the on-demand SIB request.

150. The communication device according to claim 149, characterized in that, The first condition includes one or more of the following: The first terminal device is not configured with a search space for the second SIB; The first terminal device is not configured with an OSI search space; The first cell's SIB1 includes the second SIB; The system information scheduling information includes the second SIB; The first terminal device is configured with on-demand SIB requests; The first terminal device has the ability to request SIBs on demand; The third timer is not running.

151. The communication device according to claim 149, characterized in that, The first condition includes one or more of the following: The first terminal device is configured with a search space for the second SIB; The first terminal device is configured with an OSI search space; The first cell's SIB1 includes the second SIB; The system information scheduling information includes the second SIB; The system information broadcast status indicates that the second SIB is not using broadcast transmission; The first terminal device is configured with on-demand SIB requests; The first terminal device has the ability to request SIBs on demand; The third timer is not running.

152. The communication device according to any one of claims 148 to 151, characterized in that, The second SIB is carried in dedicated system information delivery information.

153. The communication device according to claim 147, characterized in that, The first message satisfies one of the following: The first message is an RRC system information request message; The first message is a message used to trigger the Random Access Channel (RACH) procedure; The first message is a message transmitted via the RACH process.

154. The communication device according to claim 147 or 153, characterized in that, The first message is sent if a second condition is met, and the second condition is associated with one or more of the following: Does the SIB1 of the first cell contain system information and scheduling information? Does the SIB1 of the first cell contain a system information request configuration? Does the system information scheduling information include system information request configuration? Does the first cell's SIB1 contain the second SIB? Does the system information scheduling information include the second SIB? The system information broadcast status of the second SIB in SIB1 of the first cell; The system information broadcast status of the second SIB in the system scheduling information.

155. The communication device according to claim 154, characterized in that, The first message is a message used to trigger the RACH process or a message transmitted through the RACH process, and the second condition includes one or more of the following: The SIB1 of the first cell contains the system information scheduling information; The SIB1 of the first cell contains the system information request configuration; The system information scheduling information includes system information request configuration; The first cell's SIB1 includes the second SIB; The system information scheduling information includes the second SIB; The system information broadcast status indicates that the second SIB does not use broadcast transmission.

156. The communication device according to claim 154, characterized in that, The first message is an RRC system information request message, and the second condition includes one or more of the following: The SIB1 of the first cell contains the system information scheduling information; The SIB1 of the first cell does not contain system information request configuration; The system information scheduling information does not include system information request configuration; The first cell's SIB1 includes the second SIB; The system information scheduling information includes the second SIB; The system information broadcast status indicates that the second SIB does not use broadcast transmission.

157. [Amended according to Rule 26, 21.02.2025] The communication device according to claim 153 or 154 is characterized in that, The communication unit is also used for: After receiving the RRC system information request message, the second SIB is broadcast.

158. The communication device according to claim 157, characterized in that, The communication unit is also used for: Send a system information request confirmation message to the first terminal device.

159. The communication device according to any one of claims 151 to 158, characterized in that, When the first cell sends SIB1 via a broadcast message, the SIB1 of the first cell is carried in the broadcast message of the first cell.

160. The communication device according to claim 159, characterized in that, The first cell sends SIB1 via broadcast message, including one of the following: The first cell periodically broadcasts SIB1; The first cell is a cell that requests SIB1 on demand, and the first cell is broadcasting SIB1.

161. The communication device according to any one of claims 141 to 158, characterized in that, In the case that the first cell is a cell that requests SIB1 on demand, the SIB1 of the first cell is carried in the RRC dedicated message of the first terminal device.

162. The communication device according to claim 161, characterized in that, The RRC dedicated message includes dedicated SIB1 delivery information, which includes the SIB1 of the first cell.

163. The communication device according to any one of claims 141 to 162, characterized in that, If the first cell is a cell that requests SIB1 on demand, then the network device does not configure the search space corresponding to SIB1.

164. The communication device according to claim 163, characterized in that, The network device does not configure a search space corresponding to SIB1, including one or more of the following: The network device does not broadcast the configuration information of the search space corresponding to SIB1; The switching command sent by the network device to the first terminal device does not carry the configuration information of the search space corresponding to SIB1.

165. The communication device according to claim 141, characterized in that, When the first terminal device is in RRC connected state and the first terminal device has not configured a common search space, the SIB1 of the first cell is obtained by the first terminal device based on the network device dedicated RRC message.

166. The communication device according to claim 141, characterized in that, When the first terminal device is in RRC connected state and the first terminal device is configured with a common search space, the first cell satisfies one of the following: The SIB1 of the first cell is obtained based on network device-specific RRC messages; The SIB1 of the first cell is obtained based on the RACH procedure; The SIB1 of the first cell is obtained based on the dedicated RRC message sent by the first terminal device; The OSI of the first cell is obtained without needing to obtain the SIB1 of the first cell.

167. A communication device, characterized in that, The device includes a transceiver, a memory, and a processor. The memory stores a program, and the processor invokes the program in the memory and controls the transceiver to receive or transmit signals so that the communication device performs the method as described in any one of claims 1 to 21, 22 to 57, or 58 to 83.

168. An apparatus, characterized in that, Includes a processor for calling a program from memory to cause the apparatus to perform the method as described in any one of claims 1 to 21, 22 to 57, or 58 to 83.

169. A chip, characterized in that, Includes a processor for calling a program from memory, causing a device on which the chip is mounted to perform the method as described in any one of claims 1 to 21, 22 to 57, or 58 to 83.

170. A computer-readable storage medium, characterized in that, It contains a program that causes a computer to perform the method as described in any one of claims 1 to 21, 22 to 57, or 58 to 83.

171. A computer program product, characterized in that, Includes a program that causes a computer to perform the method as described in any one of claims 1 to 21, 22 to 57, or 58 to 83.

172. A computer program, characterized in that, The computer program causes the computer to perform the method as described in any one of claims 1 to 21, 22 to 57, or 58 to 83.

Images