Configuration for monitoring SIB1
Patent Information
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-02-07
- Publication Date
- 2026-08-13
Smart Images
Figure CN2025076339_13082026_PF_FP_ABST
Abstract
Description
CONFIGURATION FOR MONITORING SIB1FIELD
[0001] Various example embodiments relate to the field of communication and in particular, to a terminal device, a network device, methods, apparatuses and a computer readable storage medium for monitoring system information block 1 (SIB1) .BACKGROUND
[0002] A communication network can be seen as a facility that enables communications between two or more communication devices, or provides communication devices access to a data network. A mobile or wireless communication network is one example of a communication network.
[0003] Such communication networks operate in accordance with standards, such as those promulgated by 3GPP (Third Generation Partnership Project) or ETSI (European Telecommunications Standards Institute) . Examples of such standards include the so-called 5G (5th Generation) standard or other standards promulgated by 3GPP.SUMMARY
[0004] In general, exemplary embodiments of the present disclosure provide a solution for monitoring system information block 1 (SIB1) , for example, in case of switching between on-demand (OD) -system information block 1 (SIB1) and SIB1 broadcasting.
[0005] In a first aspect, there is provided a terminal device. The terminal device may include: at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the terminal device at least to: obtain first configuration information about system information block 1 (SIB1) from an uplink (UL) wake up signal (WUS) configuration; transmit an UL WUS to a network device based on the UL WUS configuration; based on receiving a synchronization signal block (SSB) in a first time window or a second time window, obtain second configuration information comprising at least SIB1 monitoring information; stop monitoring the SIB1 based on the first configuration information; and monitor the SIB1 based on the second configuration information.
[0006] In a second aspect, there is provided a network device. The network device may include: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the network device at least to: receive an uplink (UL) wake up signal (WUS) ; transmit an indication associated with a random access response (RAR) message, the indication being configured to indicate whether to fall back to broadcasted SIB1 monitoring; and transmit a synchronization signal block (SSB) in a first time window or a second time window.
[0007] In a third aspect, there is provided a method. The method may include: obtaining first configuration information about system information block 1 (SIB1) from an uplink (UL) wake up signal (WUS) configuration; transmitting an UL WUS to a network device based on the UL WUS configuration; based on receiving a synchronization signal block (SSB) in a first time window or a second time window, obtaining second configuration information comprising at least SIB1 monitoring information; stopping monitoring the SIB1 based on the first configuration information; and monitoring the SIB1 based on the second configuration information.
[0008] In a fourth aspect, there is provided a method. The method may include: receiving an uplink (UL) wake up signal (WUS) ; transmitting an indication associated with a random access response (RAR) message, the indication being configured to indicate whether to fall back to broadcasted SIB1 monitoring; and transmitting a synchronization signal block (SSB) in a first time window or a second time window.
[0009] In a fifth aspect, there is provided an apparatus. The apparatus may include: means for obtaining first configuration information about system information block 1 (SIB1) from an uplink (UL) wake up signal (WUS) configuration; means for transmitting an UL WUS to a network device based on the UL WUS configuration; means for based on receiving a synchronization signal block (SSB) in a first time window or a second time window, means for obtaining second configuration information comprising at least SIB1 monitoring information; means for stopping monitoring the SIB1 based on the first configuration information; and means for monitoring the SIB1 based on the second configuration information.
[0010] In a sixth aspect, there is provided an apparatus. The apparatus may include: means for receiving an uplink (UL) wake up signal (WUS) ; means for transmitting an indication associated with a random access response (RAR) message, the indication being configured to indicate whether to fall back to broadcasted SIB1 monitoring; and means for transmitting a synchronization signal block (SSB) in a first time window or a second time window.
[0011] In a seventh aspect, there is provided a non-transitory computer readable medium including program instructions for causing an apparatus to perform at least the method according to any of fourth or sixth aspects.
[0012] In an eighth aspect, there is provided a computer program including instructions, which, when executed by an apparatus, cause the apparatus at least to: obtain first configuration information about system information block 1 (SIB1) from an uplink (UL) wake up signal (WUS) configuration; transmit an UL WUS to a network device based on the UL WUS configuration; based on receiving a synchronization signal block (SSB) in a first time window or a second time window, obtain second configuration information comprising at least SIB1 monitoring information; stop monitoring the SIB1 based on the first configuration information; and monitor the SIB1 based on the second configuration information.
[0013] In a ninth aspect, there is provided a computer program including instructions, which, when executed by an apparatus, cause the apparatus at least to: receive an uplink (UL) wake up signal (WUS) ; transmit an indication associated with a random access response (RAR) message, the indication being configured to indicate whether to fall back to broadcasted SIB1 monitoring; and transmit a synchronization signal block (SSB) in a first time window or a second time window.
[0014] In an eleventh aspect, there is provided a terminal device. The terminal device may include: first obtaining circuitry configured to obtain first configuration information about system information block 1 (SIB1) from an uplink (UL) wake up signal (WUS) configuration; transmitting circuitry configured to transmit an UL WUS to a network device based on the UL WUS configuration; second obtaining circuitry configured to, based on receiving a synchronization signal block (SSB) in a first time window or a second time window, obtain second configuration information comprising at least SIB1 monitoring information; stopping circuitry configured to stop monitoring the SIB1 based on the first configuration information; and monitoring circuitry configured to monitor the SIB1 based on the second configuration information.
[0015] In a twelfth aspect, there is provided a network device. The network device may include: receiving circuitry configured to receive an uplink (UL) wake up signal (WUS) ; first transmitting circuitry configured to transmit an indication associated with a random access response (RAR) message, the indication being configured to indicate whether to fall back to broadcasted SIB1 monitoring; and second transmitting circuitry configured to transmit a synchronization signal block (SSB) in a first time window or a second time window.
[0016] It is to be understood that the summary section is not intended to identify key or essential features of embodiments of the present disclosure, nor is it intended to be used to limit the scope of the present disclosure. Other features of the present disclosure will become easily comprehensible through the following description.BRIEF DESCRIPTION OF THE DRAWINGS
[0017] Some exemplary embodiments will now be described with reference to the accompanying drawings, in which:
[0018] Fig. 1A illustrates a communication environment in which some embodiments of the present disclosure can be implemented;
[0019] Fig. 1B illustrates a schematic diagram illustrating normal UE monitoring PDCCH for SIB1;
[0020] Fig. 1C illustrates a schematic diagram illustrating UE receiving RAR and OD-SIB1 before SSB with updated PBCH / MIB;
[0021] Fig. 1D illustrates a schematic diagram illustrating UE receiving SSB with updated PBCH / MIB before or during OD-SIB1 reception;
[0022] Fig. 2 illustrates a signaling chart illustrating communication process in accordance with some embodiments of the present disclosure;
[0023] Fig. 3 illustrates an example of a signaling process of switching from OD-SIB1 monitoring to broadcasted SIB1 monitoring according to some embodiments of the present disclosure;
[0024] Fig. 4 illustrates another example of a signaling process of switching from OD-SIB1 monitoring to broadcasted SIB1 monitoring according to some embodiments of the present disclosure;
[0025] Fig. 5 illustrates a flowchart of a method implemented at a terminal device in accordance with some embodiments of the present disclosure;
[0026] Fig. 6 illustrates a flowchart of a method implemented at a network device in accordance with some embodiments of the present disclosure;
[0027] Fig. 7 illustrates a simplified block diagram of an apparatus that is suitable for implementing embodiments of the present disclosure; and
[0028] Fig. 8 illustrates a block diagram of an example computer readable medium in accordance with some embodiments of the present disclosure.
[0029] Throughout the drawings, the same or similar reference numerals represent the same or similar elements.DETAILED DESCRIPTION
[0030] Principles of the present disclosure will now be described with reference to some example embodiments. It is to be understood that these embodiments are described only for the purpose of illustration and help those skilled in the art to understand and implement the present disclosure, without suggesting any limitation as to the scope of the disclosure. The disclosure described herein can be implemented in various manners other than the ones described below.
[0031] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skills in the art to which this disclosure belongs.
[0032] References in the present disclosure to “one embodiment, ” “an embodiment, ” “an example embodiment, ” and the like indicate that the embodiment described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
[0033] It shall be understood that although the terms “first” and “second” etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and similarly, a second element could be termed a first element, without departing from the scope of example embodiments. As used herein, the term “and / or” includes any and all combinations of one or more of the listed terms.
[0034] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments. As used herein, the singular forms “a” , “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” , “comprising” , “has” , “having” , “includes” and / or “including” , when used herein, specify the presence of stated features, elements, and / or components etc., but do not preclude the presence or addition of one or more other features, elements, components and / or combinations thereof. As used herein, “at least one of the following: <a list of two or more elements>” and “at least one of <a list of two or more elements>” and similar wording, where the list of two or more elements are joined by “and” or “or” , mean at least any one of the elements, or at least any two or more of the elements, or at least all the elements.
[0035] As used in this application, the term “circuitry” may refer to one or more or all of the following: (a) hardware-only circuit implementations (such as implementations in only analog and / or digital circuitry) and (b) combinations of hardware circuits and software, such as (as applicable) : (i) a combination of analog and / or digital hardware circuit (s) with software / firmware and (ii) any portions of hardware processor (s) with software (including digital signal processor (s) ) , software, and memory (ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions) and (c) hardware circuit (s) and or processor (s) , such as a microprocessor (s) or a portion of a microprocessor (s) , that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation.
[0036] This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.
[0037] As used herein, the term “communication network” refers to a network following any suitable communication standards, such as Long Term Evolution (LTE) , LTE-Advanced (LTE-A) , Wideband Code Division Multiple Access (WCDMA) , High-Speed Packet Access (HSPA) , Narrow Band Internet of Things (NB-IoT) and so on. Furthermore, the communications between a terminal device and a network device in the communication network may be performed according to any suitable generation communication protocols, including, but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the future fifth generation (5G) communication protocols, and / or any other protocols either currently known or to be developed in the future. Embodiments of the present disclosure may be applied in various communication systems. Given the rapid development in communications, there will of course also be future type communication technologies and systems with which the present disclosure may be embodied. It should not be seen as limiting the scope of the present disclosure to only the aforementioned system.
[0038] As used herein, the term “network device” refers to a node in a communication network via which a terminal device accesses the network and receives services therefrom. The network device may refer to a base station (BS) or an access point (AP) , for example, a node B (NodeB or NB) , an evolved NodeB (eNodeB or eNB) , a NR NB (also referred to as a gNB) , a Remote Radio Unit (RRU) , a radio header (RH) , a remote radio head (RRH) , a relay, a low power node such as a femto, a pico, and so forth, depending on the applied terminology and technology.
[0039] The term “terminal device” refers to any end device that may be capable of wireless communication. By way of example rather than limitation, a terminal device may also be referred to as a communication device, user equipment (UE) , a Subscriber Station (SS) , a Portable Subscriber Station, a Mobile Station (MS) , or an Access Terminal (AT) . The terminal device may include, but not limited to, a mobile phone, a cellular phone, a smart phone, voice over IP (VoIP) phones, wireless local loop phones, a tablet, a wearable terminal device, a personal digital assistant (PDA) , portable computers, desktop computer, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback appliances, vehicle-mounted wireless terminal devices, wireless endpoints, mobile stations, laptop-embedded equipment (LEE) , laptop-mounted equipment (LME) , USB dongles, smart devices, wireless customer-premises equipment (CPE) , an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD) , a vehicle, a drone, a medical device and applications (e.g., remote surgery) , an industrial device and applications (e.g., a robot and / or other wireless devices operating in an industrial and / or an automated processing chain contexts) , a consumer electronics device, a device operating on commercial and / or industrial wireless networks, and the like. In the following description, the terms “terminal device” , “communication device” , “terminal” , “user equipment” and “UE” may be used interchangeably.
[0040] Fig. 1A illustrates an example of a network environment 100 in which some example embodiments of the present disclosure may be implemented. The system 100, for example, a communication network, includes at least one terminal device, such as a terminal device 110, and a plurality of network devices, such as a network device 120 and a network device 130. The network devices 120, 130 serve respective areas (also called as cells) . The terminal device 110 are capable of connecting and communicating in an UL and DL with either or both of the network devices 120, 130 as long as the terminal device 110 located within the corresponding cells. In addition to communicating the terminal device 110, the network devices 120, 130 may also communicate with each other. In some embodiments, the network device 120 may serve (or control or provide) a cell (e.g. a NES cell) , and the network device 130 may serve (or control or provide) a cell (e.g. an Cell A) . In some examples, the network device 130 may transmit configuration information of the network device 120, e.g. UL WUS configuration of NES Cell. After that, the terminal device 110 may transmit a UL WUS to the network device 120 providing the NES Cell. The network device 120 providing the NES Cell may transmit an SIB e.g. an on-demand SIB1 (OD-SIB1) to the terminal device 110.
[0041] It is to be understood that the particular number of various communication devices, the particular number of various communication links, the particular number of other elements, and the particular shape of the cells as shown in Fig. 1A is for illustration purpose only without suggesting any limitations. The communication system 100 may include any suitable number of communication devices, any suitable number of communication links, and any suitable number of other elements and any suitable shape of the cells adapted for implementing embodiments of the present disclosure. In addition, it should be appreciated that there may be various wireless as well as wireline communications (if needed) among all of the communication devices.
[0042] Communications in the communication system 100 may be implemented according to any proper communication protocol (s) , comprising, but not limited to, cellular communication protocols of the first generation (1G) , the second generation (2G) , the third generation (3G) , the fourth generation (4G) and the fifth generation (5G) and on the like, wireless local network communication protocols such as Institute for Electrical and Electronics Engineers (IEEE) 1002.11 and the like, and / or any other protocols currently known or to be developed in the future. Moreover, the communication may utilize any proper wireless communication technology, comprising but not limited to: Code Division Multiple Access (CDMA) , Frequency Division Multiple Access (FDMA) , Time Division Multiple Access (TDMA) , Frequency Division Duplex (FDD) , Time Division Duplex (TDD) , Multiple-Input Multiple-Output (MIMO) , Orthogonal Frequency Division Multiple (OFDM) , Discrete Fourier Transform spread OFDM (DFT-s-OFDM) and / or any other technologies currently known or to be developed in the future.
[0043] It is to be understood that the numbers of devices (i.e., the terminal device 110, the network device 120, and the network device 130) and their connection relationships and types shown in FIG. 1A are only for the purpose of illustration without suggesting any limitation. For example, the environment 100 may include any suitable numbers of devices adapted for implementing embodiments of the present disclosure. For example, while FIG. 1A depicts the terminal device 110 as a mobile phone; the terminal device 110 may be any type of user equipment.
[0044] Some embodiments of this disclosure relate to the Release 19 WID on NES enhancement. Based on the outcome of RAN#105, the release 19 work item on network energy saving (RP-242354) includes the following objective regarding on-demand SIB1 for idle / inactive mode UEs:
[0045] Specify support for on-demand SIB1 for UEs in idle / inactive mode [RAN1 / 2 / 3] - Specify procedures and signaling method (s) for Case 2 [RAN1 / 2] - Case 2: UE obtains UL WUS configuration from Cell A, UE transmits UL WUS on NES Cell, UE receives on-demand SIB1 from NES Cell - Triggering method by UL WUS using PRACH - Specify inter NG-RAN node signaling at least for the configuration of UL WUS [RAN3] - Note 1: No modification of SSB will be discussed under this objective - Note 2: - UL WUS: Uplink wake-up signal - Cell A: A cell that is periodically transmitting at least its own SIB1 - NES Cell: A cell that may transmit SIB1 transmission in response to UL WUS from a UE - Note 3: - RAN1 strives to minimize impact to legacy UE - RAN1 specification impact to support this feature should be minimized
[0046] The capacity cell referred in 3GPP as NES cell operating with OD-SIB1 mode will not periodically broadcast the SIB1. Instead, the SIB1 of the NES cell will be provided on-demand, i.e., based on the UE in RRC idle or RRC inactive mode requesting its transmission. As can be seen from the above objective, the UE will trigger the transmission by sending a wake-up signal (WUS) , which could e.g., be a Physical Random-Access Channel (PRACH) i.e. a preamble. This requires that the UE is configured with resources and information to transmit the WUS.
[0047] The following steps are assumed for OD-SIB1 operation for case 2: the terminal device 110 (such as the UE) obtains WUS configuration from the network device 130 providing the Cell A; the terminal device 110 sends UL WUS, i.e., RACH / Msg 1, to the network device 120 providing the NES Cell; the terminal device 110 monitors / receives a RAR response from the network device that receives the UL WUS; and the terminal device 110 receives OD-SIB1 from the NES Cell.
[0048] Some embodiments of this disclosure are applicable for case 2 and also applicable for all non-standalone cases and standalone case discussed in RAN1 / RAN2 during rel. 19 WUS.
[0049] Fig. 1B illustrates a schematic diagram illustrating normal UE monitoring PDCCH for SIB1. As specified in Clause 13 of TS38.213, a normal (for example, legacy) UE determines the slot index to monitor Type0-PDCCH based on the slot index of SS / PBCH block. The normal UE obtains the Type0-PDCCH configurations from PBCH / MIB carried by SS / PBCH block.
[0050] The following RAN2 #127 agreement has been made: A cell for which SIB1 request configuration is available, can periodically broadcast SIB1. If UE has SIB1 request configuration of a cell, UE needs to check if SIB1 is currently being broadcasted or provided on demand for that cell before requesting SIB1 of that cell.
[0051] A cell for which SIB1 request configuration is available may be included in the WUS configuration. A NES UE receiving the WUS configuration from cell A may assume that the NES cell is with on-demand SIB1 operation. Based on above RAN2 agreement, a NES cell for which SIB1 request is available has two statuses: status 1, the NES cell may periodically broadcast SIB1; status 2, the NES cell may provide SIB1 on demand.
[0052] To allow a NES UE which has SIB1 request configuration of a NES cell, to check if SIB1 is currently being broadcasted or provided on demand for that cell before requesting SIB1 of that cell, the UE needs to check the PBCH / MIB of the NES cell. The latest needs to be reflecting the SIB1 status (like in legacy) . A cell broadcasting SIB1 has a K_SSB <=23 for FR1 and K_SSB <=11 for FR2 if it is transmitted on sync raster. In addition, the PBCH / MIB payload contains a valid pdcch-ConfigSIB1 pointing to type0-PDCCH.
[0053] This means that a NES cell when switching to SIB1 broadcasting mode, switches from a non-cell defining (NCD) -Synchronization Signal / PBCH Block (SSB) (K_SSB > 23 for FR1 and K_SSB >11 for FR2) to a cell defining (CD) -SSB (K_SSB <= 23 for FR1 and K_SSB <=11 for FR2) .
[0054] For a NES cell switching from a NCD-SSB to a CD-SSB, the normal UEs may select / re-select the cell unless the normal UE has already barred this cell.
[0055] Whenever the cell is broadcasting the SIB1, it needs to be possible for the normal UEs to camp on such a cell. It would seem be suboptimal that the NW is broadcasting the SIB1 but the UEs cannot camp on the cell –especially as there are quite a big population of the normal UEs.
[0056] Hence for a cell providing the SIB1 on-demand and the UE requesting the OD-SIB1, the following procedure is expected:
[0057] Step 1: the UE camps on the cell A. Step 2: the UE obtains an UL WUS configuration from the cell A. The UL WUS configuration contains pdcch-ConfigSIB1 (searchSpaceZero and controlResourceSetZero) that allows the UE to monitor an OD-SIB1. Step 3: the UE re-selects the NES cell with the SSB / PBCH carrying an K_SSB >23 for FR1 and K_SSB > 11 for FR2. The pdcchConfigSIB1 in NES cell MIB does not carry any information about PDCCH for the OD-SIB1. The UE can refer to the UL WUS configuration to obtain the pdcchConfigSIB1. Step 4: the UE send an UL WUS towards the NES cell. Step 5: the UE receives a RAR response from the NES cell to acknowledge reception of the UL WUS. Step 6: the NW transmits OD-SIB1. The NES cell updates the SSB to carry the updated PBCH / MIB with new value for K_SSB (K_SSB < 24 for FR1 and K_SSB < 12 for FR2) to indicate that SIB1 is transmitted. The pdcchConfigSIB1 in the NES cell MIB associated to the updated K_SSB value may provide to the UE the PDCCH monitoring occasions for the SIB1. Step 7: the UE monitor the OD-SIB1 using the pdcch-ConfigSIB1 and the reference time point to determine the window starting time for on-demand SIB1 is based on the RAR window.
[0058] In this procedure, the problem is how the UE behaves because the UE receives two pdcchConfigSIB1, i.e., one from the UL WUS configuration (in step 2) , another from the updated PBCH / MIB (in step 6) . For example, Fig. 1C illustrates a schematic diagram illustrating UE receiving RAR and OD-SIB1 before SSB with updated PBCH / MIB, while Fig. 1D illustrates a schematic diagram illustrating UE receiving SSB with updated PBCH / MIB before or during OD-SIB1 reception. As shown in Figs. 1C and 1D, the discussed problem may not occur in the scenario of Fig. 1C, while the discussed problem will occur in the scenario of Fig. 1D because the UE receives SSB with the updated PBCH / MIB during the OD-SIB1 reception. It should be understood that even though the problem does not occur in the scenario of Fig. 1C, this scenario cannot be guaranteed because the SSB periodicity is typically 20ms while the type0 PDCCH monitoring window, is typically 20ms and the RAR window, typically 10ms.
[0059] In view of the above discussions and analysis, embodiments of the present disclosure provide a solution for monitoring system information block 1 (SIB1) . For example, in order to solve the problem about how the UE behaves when the network device switches from an OD-SIB1 mode to a SIB1 broadcasting mode, some embodiments of this disclosure provide a configuration for monitoring SIB1 in case the network device switches between OD-SIB1 and SIB1 broadcasting. In some embodiments, a terminal device obtains first configuration information about system information block 1 (SIB1) from an uplink (UL) wake up signal (WUS) configuration, the terminal device transmits an UL WUS to a network device based on the UL WUS configuration. The network device transmits a synchronization signal block (SSB) to the terminal device. Based on receiving a synchronization signal block (SSB) in a first time window or a second time window, the terminal device obtains second configuration information comprising at least SIB1 monitoring information. The terminal device stops monitoring the SIB1 based on the first configuration information, and monitors the SIB1 based on the second configuration information. Principles and some example embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings.
[0060] Hereinafter, the example method for providing a solution for a configuration for switching between OD-SIB1 and SIB1 broadcasting will be described with reference to Fig. 2 to Fig. 4. Reference is first made to Fig. 2, which illustrates an exemplary signaling chart illustrating communication process in accordance with some embodiments of the present disclosure.
[0061] As shown in Fig. 2, the terminal device 110 obtains 202 first configuration information about system information block 1 (SIB1) from an uplink (UL) wake up signal (WUS) configuration. Based on the UL WUS configuration, the terminal device 110 transmits 204 an UL WUS 206 to a network device 120, and accordingly, the network device 120 receives 208 the UL WUS 206. The network device 120 transmits 216 a synchronization signal block (SSB) 218 to the terminal device 110, and accordingly the terminal device 110 receives 220 the SSB 218. Based on receiving the SSB 218 within a first time window or a second time window, the terminal device 110 obtains 222 second configuration information comprising at least SIB1 monitoring information, and the terminal device 110 stops 224 monitoring the SIB1 based on the first configuration information and monitors 226 the SIB1 based on the second configuration information.
[0062] In some embodiments, the terminal device 110 may be a user equipment, and the network device 120 may be a NES cell.
[0063] In some embodiments, the network device 120 has two SIB1 modes, i.e., an OD-SIB1 mode and a SIB1 broadcasting mode. In the OD-SIB1 mode, the network device 120 may provide SIB1 on-demand, while in the SIB1 broadcasting mode, the network device 120 may periodically broadcast SIB1. When the network device 120 is operating in an OD-SIB1 mode, the network device 120 may transmit a NCD-SSB to the terminal device 110, and the NCD-SSB carries the K_SSB higher than 23 for frequency range (FR) 1 and the K_SSB higher than 11 for FR2. When the network device 120 switches to the SIB1 broadcasting mode from the OD-SIB1 mode, the network device 120 may transmit to the terminal device 110 a CD-SSB that indicates that network device 120 switches to the SIB1 broadcasting mode, and the CD-SSB carries an K_SSB less than 24 for frequency range 1 and K_SSB less than 12 for FR2.
[0064] In some embodiments, the terminal device 110 may receive the UL WUS configuration from another network device, such as a cell A. The terminal device 110 may obtain and store the first configuration information from the UL WUS configuration. For example, the first configuration information may be pdcchConfigSIB1 that allows the terminal device 110 to monitor the OD-SIB1 from the network device 120 based on the pdcchConfigSIB1.
[0065] In some embodiments, the terminal device 110 may re-select the network device 120, for example, may attempt to access the network device 120. The terminal device 110 may transmit the UL WUS to the network device 120, and the terminal device 110 may monitor the RAR message and the OD-SIB1 from the network device 120.
[0066] In some embodiments, when the network device 120 switches to the SIB1 broadcasting mode from the OD-SIB1 mode, the SSB carries the updated K_SSB may be transmitted to the terminal device 110 from the network device 120, and the value of the updated K_SSB is less than 24 for FR1 and less than 11 for FR2.
[0067] In some embodiments, the terminal device 110 may obtain second configuration information from the SSB carrying the updated K_SSB. For example, the second configuration may be pdcchConfigSIB1 obtained from the updated PBCH / MIB. The terminal device 110 may overwrite the pdcchConfigSIB1 obtained from the UL WUS configuration with the pdcchConfigSIB1 obtained from the updated PBCH / MIB.
[0068] In some embodiments, the terminal device 110 may receive the SSB within different time window, such as a first time window or a second time window. For example, the first time window may be an RAR window for the terminal device’s reception of an RAR message, and the second time window may an OD-SIB1 monitoring window after reception of an RAR message.
[0069] In some embodiments, based on receiving the SSB carrying an K_SSB less than 24 for frequency range 1 and K_SSB less than 12 for frequency range 2 within the first time window, the terminal device 110 may stop monitoring the OD-SIB1 based on the first configuration information, and terminal device 110 may fall back to monitor and acquire the broadcasted SIB1 based on the second configuration information. The terminal device 110 may also stop monitoring the RAR message.
[0070] In some embodiments, based on not receiving the SSB within the first time window, or based on receiving the SSB carrying an K_SSB higher than 23 for frequency range 1 and K_SSB higher than 11 for frequency range 2 within the first time window, the terminal device 110 may continue to monitor the RAR message.
[0071] In some embodiments, based on receiving the SSB carrying an K_SSB less than 24 for frequency range 1 and K_SSB less than 12 for frequency range 2 within the second time window, the terminal device 110 may stop monitoring the OD-SIB1 based on the first configuration information, and terminal device 110 may fall back to monitor and acquire the broadcasted SIB1 based on the second configuration information.
[0072] In some further embodiment, back to Fig. 2, the network device 120 may transmit 210 an indication associated with the RAR message 212 to the terminal device 110, and the terminal device 110 may obtain or receive 214 the indication associated with the RAR message 212, and the indication is configured to indicate whether to fall back to the broadcasting SIB1 monitoring. The indication may be explicitly or implicitly provided to the terminal device 110, and the indication may be provided by the network device 120 or otherwise predefined, for example by the standard, which is not limited herein. For example, the indication may be provided in an RAR payload, the indication may be provided in an RAR CORESET, or the indication may be implicitly provided based on interpretation of RAR CORESET parameters.
[0073] Based on receiving the SSB carrying an K_SSB less than 24 for frequency range 1 and K_SSB less than 12 for frequency range 2 within the second time window and based on the indication to fall back to broadcasted SIB1 monitoring, the terminal device 110 may stop monitoring the OD-SIB1 based on the first configuration information and fall back to monitor and acquire the broadcasted SIB1 based on the second configuration information. Based on receiving the SSB carrying an K_SSB less than 24 for frequency range 1 and K_SSB less than 12 for frequency range 2 within the second time window and based on the indication not to fall back to broadcasted SIB1 monitoring, the terminal device 110 may continue to monitor the OD-SIB1.
[0074] In some embodiments, based on not receiving the SSB in the second time window or based on receiving the SSB carrying an K_SSB higher than 23 for frequency range 1 and K_SSB higher than 11 for frequency range 2 in the second time window, the terminal device 110 may continue to monitor an OD-SIB1.
[0075] Fig. 3 illustrates an example of a signaling process of switching from OD-SIB1 monitoring to broadcasted SIB1 monitoring according to some embodiments of the present disclosure. The signaling process 400 may be a more specific example of the process 400 of Fig. 2 in the case that the terminal device receives the SSB within the RAR monitoring window. The terminal device 110 may be called as UE for short, and the network device 120 may be called as NES cell for short.
[0076] In step 0, the UE camps on the cell A 130. In steps 1 and 2, the cell A transmits the UL WUS configuration to the UE, and the UE stores the pdcchConfigSIB1 obtained from the UL WUS configuration. In step 3, the NES cell in the OD-SIB1 mode transmits a SSB with K_SSB higher than 23 for FR1 and K_SSB higher than 11 for FR2. In steps 4 and 5, the UE re-selects the NES cell and transmits the UL WUS towards the NES cell, and the UE starts monitoring NW response in the RAR window. The UE may be mandated to acquire SSB after sending the UL WUS. This allows the UE to detect if any PBCH update is signaled by the NW.
[0077] If the SSB occasion is present in the RAR window, i.e., the UE receives the SSB from the NES cell in the RAR window, the UE checks the update PBCH of the NES cell. If no SSB occasion is present in the RAR window, the UE keeps monitoring the RAR message.
[0078] If the NES cell is broadcasting SIB1, e.g. K_SSB is updated to CD-SSB, the NES cell switching to the SIB1 broadcasting SIB1 mode transmits to the UE a SSB with K_SSB less than 24 for FR1 and K_SSB less than 12 for FR2, as shown in step 6. In step 6.1, the UE obtains the updated pddcchConfigSIB1 from the PBCH / MIB, and the UE overwrites the pdcchConfigSIB1 obtained from WUS configuration with the updated one from the PBCH / MIB. In step 6.2, the UE stops monitoring the RAR and fall backs to acquire (for example, in the legacy way) the SIB1 based on the pdcchConfigSIB1 obtained from updated PBCH / MIB. In step 7, the NES cell transmits the SIB1 for example in the legacy way. Otherwise, i.e., if the NES cell is not broadcasting SIB1, the UE continues monitoring to detect the RAR message.
[0079] Fig. 4 illustrates another example of a signaling process of switching from OD-SIB1 monitoring to broadcasted SIB1 monitoring according to some embodiments of the present disclosure. The signaling process 400 may be a more specific example of the process 400 of Fig. 2 in the case that the terminal device receives the SSB within the OD-SIB1 monitoring window. The terminal device 110 may be called as UE for short, and the network device 120 may be called as NES cell for short.
[0080] In step 0, the UE camps on the cell A 130. In steps 1 and 2, the cell A transmits the UL WUS configuration to the UE, and the UE stores the pdcchConfigSIB1 obtained from the UL WUS configuration. In step 3, the NES cell in the OD-SIB1 mode transmits a SSB with K_SSB higher than 23 for FR1 and K_SSB higher than 11 for FR2. In steps 4 to 6, the UE re-selects the NES cell and transmits the UL WUS towards the NES cell, and NES cell transmits a RAR message with indication about fallback to the normal (for example, the legacy) SIB1 monitoring. After the RAR reception, the UE starts monitoring OD-SIB1.
[0081] If the SSB occasion is present in the RAR window, i.e., the UE receives the SSB from the NES cell in the RAR window, the UE checks the update PBCH of the NES cell. If no SSB occasion is present in the RAR window, the UE keeps monitoring the OD-SIB1. If the NES cell is broadcasting SIB1, e.g. K_SSB is updated to CD-SSB, the NES cell switching to the SIB1 broadcasting SIB1 mode transmits to the UE a SSB with K_SSB less than 24 for FR1 and K_SSB less than 12 for FR2, as shown in step 6. In step 6.1, the UE obtains the updated pddcchConfigSIB1 from the PBCH / MIB, and the UE overwrites the pdcchConfigSIB1 obtained from WUS configuration with the updated one from the PBCH / MIB. The NES cell allows the UE to select between the following options by sending one indication (as shown in step 6) to the UE in RAR message: option 1, the UE stops monitoring the OD-SIB1 and fall backs to acquire (for example, in the legacy way) the SIB1 based on the pdcchConfigSIB1 obtained from updated PBCH / MIB; option 2, the UE continues monitoring to detect the OD-SIB1.
[0082] Fig. 5 illustrates a flowchart of a method 500 implemented at a terminal device in accordance with some embodiments of the present disclosure. For the purpose of discussion, the method 500 will be described from the perspective of the terminal device 110 with reference to Fig. 1.
[0083] At block 510, the terminal device 110 obtains first configuration information about system information block 1 (SIB1) from an uplink (UL) wake up signal (WUS) configuration. At block 520, the terminal device 110 transmits an UL WUS to a network device based on the UL WUS configuration. At block 530, based on receiving a synchronization signal block (SSB) in a first time window or a second time window, the terminal device 110 obtains second configuration information comprising at least SIB1 monitoring information. At block 540, the terminal device 110 stops monitoring the SIB1 based on the first configuration information. At block 520, the terminal device 110 monitors the SIB1 based on the second configuration information.
[0084] In some embodiments, the SSB indicates that the network device switches to a SIB1 broadcasting mode from an on-demand (OD) -SIB1 mode.
[0085] In some embodiments, the SSB carries an K_SSB less than 24 for frequency range 1 and K_SSB less than 12 for frequency range 2.
[0086] In some embodiments, based on receiving the SSB in the first time window, the terminal device 110 stops monitoring a random access response (RAR) message; and the terminal device 110 fall backs to acquire a broadcasted SIB1 based on the second configuration information.
[0087] In some embodiments, based on not receiving the SSB in the first time window or based on receiving a SSB carrying an K_SSB higher than 23 for frequency range 1 and K_SSB higher than 11 for frequency range 2 in the first time window, the terminal device 110 continues to monitor an RAR message.
[0088] In some embodiments, the terminal device 110 receives an RAR message within the first time window.
[0089] In some embodiments, the terminal device 110 receives an indication associated with the RAR message, the indication being configured to indicate whether to fall back to broadcasted SIB1 monitoring.
[0090] In some embodiments, the indication is provided in an RAR payload; the indication is provided in an RAR control resource set (CORESET) ; or the indication is implicitly provided based on interpretation of RAR CORESET parameters.
[0091] In some embodiments, based on receiving the SSB in the second time window and based on the indication to fall back to broadcasted SIB1 monitoring, the terminal device 110 stops monitoring an OD-SIB1 and fall backs to acquire a broadcasted SIB1 based on the second configuration information.
[0092] In some embodiments, based on receiving the SSB in the second time window and based on the indication not to fall back to a broadcasted SIB1 monitoring, the terminal device 110 continues to monitor an OD-SIB1.
[0093] In some embodiments, based on not receiving the SSB in the second time window or based on receiving a SSB carrying an K_SSB higher than 23 for frequency range 1 and K_SSB higher than 11 for frequency range 2 in the second time window, the terminal device 110 continues to monitor an OD-SIB1.
[0094] In some embodiments, the first time window is an RAR window for reception of an RAR message; or the second time window is an OD-SIB1 monitoring window after reception of an RAR message.
[0095] In some embodiments, the first configuration information is an pdcchConfigSIB1 obtained from the UL WUS configuration; or the second configuration information is an pdcchConfigSIB1 obtained from the SSB.
[0096] Fig. 6 illustrates a flowchart of a method implemented at a network device according to some other embodiments of the present disclosure. For the purpose of discussion, the method 600 will be described from the perspective of the network device 120 with reference to Fig. 1.
[0097] At block 610, the network device 120 receives an uplink (UL) wake up signal (WUS) . At block 620, the network device 120 transmits an indication associated with a random access response (RAR) message, the indication being configured to indicate whether to fall back to broadcasted SIB1 monitoring. At block 630, the network device 120 transmits a synchronization signal block (SSB) in a first time window or a second time window.
[0098] In some embodiments, the network device 120 transmits the RAR message within the first time window.
[0099] In some embodiments, the indication is provided in an RAR payload; the indication is provided in an RAR control resource set (CORESET) ; or the indication is implicitly provided based on interpretation of RAR CORESET parameters.
[0100] In some embodiments, the SSB indicates that the network device switches to a SIB1 broadcasting mode from an on-demand (OD) -SIB1 mode.
[0101] In some embodiments, the SSB carries an K_SSB less than 24 for frequency range 1 and K_SSB less than 12 for frequency range 2.
[0102] In some embodiments, the first time window is an RAR window for reception of an RAR message; or the second time window is an OD-SIB1 monitoring window after reception of an RAR message.
[0103] In some embodiments, the first configuration information is an pdcchConfigSIB1 obtained from the UL WUS configuration; or the second configuration information is an pdcchConfigSIB1 obtained from the SSB.
[0104] In some embodiments, an apparatus (for example, the terminal device 110) capable of performing the method 500 may comprise means for performing the respective steps of the method 500. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module.
[0105] In some embodiments, the apparatus comprises means for obtaining first configuration information about system information block 1 (SIB1) from an uplink (UL) wake up signal (WUS) configuration. The apparatus further comprises means for transmitting an UL WUS to a network device based on the UL WUS configuration. The apparatus further comprises means for obtaining, based on receiving a synchronization signal block (SSB) in a first time window or a second time window, second configuration information comprising at least SIB1 monitoring information. The apparatus further comprises means for stopping monitoring the SIB1 based on the first configuration information. The apparatus further comprises means for monitoring the SIB1 based on the second configuration information.
[0106] In some embodiments, the SSB indicates that the network device switches to a SIB1 broadcasting mode from an on-demand (OD) -SIB1 mode.
[0107] In some embodiments, the SSB carries an K_SSB less than 24 for frequency range 1 and K_SSB less than 12 for frequency range 2.
[0108] In some embodiments, the apparatus comprises means for stopping, based on receiving the SSB in the first time window, monitoring a random access response (RAR) message; and the apparatus comprises means for fall backing to acquire a broadcasted SIB1 based on the second configuration information.
[0109] In some embodiments, the apparatus comprises means for continuing, based on not receiving the SSB in the first time window or based on receiving a SSB carrying an K_SSB higher than 23 for frequency range 1 and K_SSB higher than 11 for frequency range 2 in the first time window, to monitor an RAR message.
[0110] In some embodiments, the apparatus comprises means for receiving an RAR message within the first time window.
[0111] In some embodiments, the apparatus comprises means for receiving an indication associated with the RAR message, the indication being configured to indicate whether to fall back to broadcasted SIB1 monitoring.
[0112] In some embodiments, the indication is provided in an RAR payload; the indication is provided in an RAR control resource set (CORESET) ; or the indication is implicitly provided based on interpretation of RAR CORESET parameters.
[0113] In some embodiments, the apparatus comprises means for stopping, based on receiving the SSB in the second time window and based on the indication to fall back to broadcasted SIB1 monitoring, monitoring an OD-SIB1; and the apparatus comprises means for fall backing to acquire a broadcasted SIB1 based on the second configuration information.
[0114] In some embodiments, the apparatus comprises means for continuing, based on receiving the SSB in the second time window and based on the indication not to fall back to a broadcasted SIB1 monitoring, to monitor an OD-SIB1.
[0115] In some embodiments, the apparatus comprises means for continuing, based on not receiving the SSB in the second time window or based on receiving a SSB carrying an K_SSB higher than 23 for frequency range 1 and K_SSB higher than 11 for frequency range 2 in the second time window, to monitor an OD-SIB1.
[0116] In some embodiments, the first time window is an RAR window for reception of an RAR message; or the second time window is an OD-SIB1 monitoring window after reception of an RAR message.
[0117] In some embodiments, the first configuration information is an pdcchConfigSIB1 obtained from the UL WUS configuration; or the second configuration information is an pdcchConfigSIB1 obtained from the SSB.
[0118] In some embodiments, the apparatus further comprises means for performing other steps in some embodiments of the method 500. In some embodiments, the means comprises at least one processor and at least one memory including computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the performance of the apparatus.
[0119] In some embodiments, an apparatus (for example, the network device 120) capable of performing the method 600 may comprise means for performing the respective steps of the method 600. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module.
[0120] In some embodiments, the apparatus comprises means for receiving an uplink (UL) wake up signal (WUS) . The apparatus further comprises means for transmitting an indication associated with a random access response (RAR) message, the indication being configured to indicate whether to fall back to broadcasted SIB1 monitoring. The apparatus further comprises means for transmitting a synchronization signal block (SSB) in a first time window or a second time window.
[0121] In some embodiments, the apparatus further comprises means for transmitting the RAR message within the first time window.
[0122] In some embodiments, the indication is provided in an RAR payload; the indication is provided in an RAR control resource set (CORESET) ; or the indication is implicitly provided based on interpretation of RAR CORESET parameters.
[0123] In some embodiments, the SSB indicates that the network device switches to a SIB1 broadcasting mode from an on-demand (OD) -SIB1 mode.
[0124] In some embodiments, the SSB carries an K_SSB less than 24 for frequency range 1 and K_SSB less than 12 for frequency range 2.
[0125] In some embodiments, the first time window is an RAR window for reception of an RAR message; or the second time window is an OD-SIB1 monitoring window after reception of an RAR message.
[0126] In some embodiments, the first configuration information is an pdcchConfigSIB1 obtained from the UL WUS configuration; or the second configuration information is an pdcchConfigSIB1 obtained from the SSB.
[0127] In some embodiments, the apparatus further comprises means for performing other steps in some embodiments of the method 600. In some embodiments, the means comprises at least one processor and at least one memory including computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the performance of the apparatus.
[0128] Fig. 7 is a simplified block diagram of a device 700 that is suitable for implementing embodiments of the present disclosure. The device 700 may be provided to implement the communication device, for example the terminal device 110, and the network device 120 as shown in Fig. 1. As shown, the device 700 includes one or more processors 710, one or more memories 720 coupled to the processor 710, and one or more communication modules 740 coupled to the processor 710.
[0129] The communication module 740 is for bidirectional communications. The communication module 740 has at least one antenna to facilitate communication. The communication interface may represent any interface that is necessary for communication with other network devices.
[0130] The processor 710 may be of any type suitable to the local technical network and may include one or more of the following: general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples. The device 700 may have multiple processors, such as an application specific integrated circuit chip that is slaved in time to a clock which synchronizes the main processor.
[0131] The memory 720 may include one or more non-volatile memories and one or more volatile memories. Examples of the non-volatile memories include, but are not limited to, a read only memory (ROM) 724, an electrically programmable read only memory (EPROM) , a flash memory, a hard disk, a compact disc (CD) , a digital video disk (DVD) , and other magnetic storage and / or optical storage. Examples of the volatile memories include, but are not limited to, a random access memory (RAM) 722 and other volatile memories that may not last in the power-down duration.
[0132] A computer program 730 includes computer executable instructions that are executed by the associated processor 710. The program 730 may be stored in the ROM 724. The processor 710 may perform any suitable actions and processing by loading the program 730 into the RAM 722.
[0133] The embodiments of the present disclosure may be implemented by means of the program so that the device 700 may perform any process of the disclosure as discussed with reference to Figs. 2 to 4. The embodiments of the present disclosure may also be implemented by hardware or by a combination of software and hardware.
[0134] In some embodiments, the program 730 may be tangibly contained in a computer readable medium which may be included in the device 700 (such as in the memory 720) or other storage devices that are accessible by the device 700. The device 700 may load the program 730 from the computer readable medium to the RAM 722 for execution. The computer readable medium may include any types of tangible non-volatile storage, such as ROM, EPROM, a flash memory, a hard disk, CD, DVD, and the like.
[0135] Fig. 8 illustrates an example of the computer readable medium 1200 in form of CD or DVD in accordance with some embodiments of the present disclosure. The computer readable medium has the program 730 stored thereon. It is noted that although the computer-readable medium 800 is depicted in form of CD or DVD, the computer-readable medium 1200 may be in any other form suitable for carry or hold the program 730.
[0136] Generally, various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. While various aspects of embodiments of the present disclosure are illustrated and described as block diagrams, flowcharts, or using some other pictorial representations, it is to be understood that the block, apparatus, system, technique or method described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.
[0137] The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer readable storage medium. The computer program product includes computer-executable instructions, such as those included in program modules, being executed in a device on a target real or virtual processor, to carry out the methods 500 or 600 as described above with reference to Fig. 5 to Fig. 6. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types. The functionality of the program modules may be combined or split between program modules as desired in various embodiments. Machine-executable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.
[0138] Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.
[0139] In the context of the present disclosure, the computer program codes or related data may be carried by any suitable carrier to enable the device, apparatus or processor to perform various processes and operations as described above. Examples of the carrier include a signal, computer readable medium, and the like.
[0140] The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable medium may include but not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of the computer readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM) , a read-only memory (ROM) , an erasable programmable read-only memory (EPROM or Flash memory) , an optical fiber, a portable compact disc read-only memory (CD-ROM) , an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. The term “non-transitory, ” as used herein, is a limitation of the medium itself (i.e., tangible, not a signal) as opposed to a limitation on data storage persistency (e.g., RAM vs. ROM) .
[0141] Further, while operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Likewise, while several specific implementation details are contained in the above discussions, these should not be construed as limitations on the scope of the present disclosure, but rather as descriptions of features that may be specific to particular embodiments. Certain features that are described in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, various features that may be described in the context of a single embodiment may also be implemented in multiple embodiments separately or in any suitable sub-combination.
[0142] Although the present disclosure has been described in languages specific to structural features and / or methodological acts, it is to be understood that the present disclosure defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above may be disclosed as example forms of implementing the claims.
Claims
1.A terminal device, comprising:at least one processor; andat least one memory storing instructions that, when executed by the at least one processor, cause the terminal device at least to:obtain first configuration information about system information block 1 (SIB1) from an uplink (UL) wake up signal (WUS) configuration;transmit an UL WUS to a network device based on the UL WUS configuration;based on receiving a synchronization signal block (SSB) in a first time window or a second time window, obtain second configuration information comprising at least SIB1 monitoring information;stop monitoring the SIB1 based on the first configuration information; andmonitor the SIB1 based on the second configuration information.2.The terminal device of claim 1, wherein the SSB indicates that the network device switches to a SIB1 broadcasting mode from an on-demand (OD) -SIB1 mode.3.The terminal device of claim 1 or 2, wherein the SSB carries an K_SSB less than 24 for frequency range 1 and K_SSB less than 12 for frequency range 2.4.The terminal device of any one of claims 1 to 3, wherein the terminal device is further caused to:based on receiving the SSB in the first time window, stop monitoring a random access response (RAR) message; andfall back to acquire a broadcasted SIB1 based on the second configuration information.5.The terminal device of any one of claims 1 to 4, wherein the terminal device is further caused to:based on not receiving the SSB in the first time window or based on receiving a SSB carrying an K_SSB higher than 23 for frequency range 1 and K_SSB higher than 11 for frequency range 2 in the first time window, continue to monitor an RAR message.6.The terminal device of any one of claims 1 to 5, wherein the terminal device is further caused to:receive an RAR message within the first time window.7.The terminal device of claim 6, wherein the terminal device is further caused to:receive an indication associated with the RAR message, the indication being configured to indicate whether to fall back to broadcasted SIB1 monitoring.8.The terminal device of claim 7, wherein at least one of the following:the indication is provided in an RAR payload;the indication is provided in an RAR control resource set (CORESET) ; orthe indication is implicitly provided based on interpretation of RAR CORESET parameters.9.The terminal device of any one of claims 1 to 8, wherein the terminal device is further caused to:based on receiving the SSB in the second time window and based on the indication to fall back to broadcasted SIB1 monitoring, stop monitoring an OD-SIB1 and fall back to acquire a broadcasted SIB1 based on the second configuration information.10.The terminal device of any one of claims 1 to 9, wherein the terminal device is further caused to:based on receiving the SSB in the second time window and based on the indication not to fall back to a broadcasted SIB1 monitoring, continue to monitor an OD-SIB1.11.The terminal device of any one of claims 1 to 10, wherein the terminal device is further caused to:based on not receiving the SSB in the second time window or based on receiving a SSB carrying an K_SSB higher than 23 for frequency range 1 and K_SSB higher than 11 for frequency range 2 in the second time window, continue to monitor an OD-SIB1.12.The terminal device of any one of claims 1 to 11, wherein at least one of the following:the first time window is an RAR window for reception of an RAR message; orthe second time window is an OD-SIB1 monitoring window after reception of an RAR message.13.The terminal device of any one of claims 1 to 12, wherein at least one of the following:the first configuration information is an pdcchConfigSIB1 obtained from the UL WUS configuration; orthe second configuration information is an pdcchConfigSIB1 obtained from the SSB.14.A network device, comprising:at least one processor; andat least one memory storing instructions that, when executed by the at least one processor, cause the network device at least to:receive an uplink (UL) wake up signal (WUS) ;transmit an indication associated with a random access response (RAR) message, the indication being configured to indicate whether to fall back to broadcasted SIB1 monitoring; andtransmit a synchronization signal block (SSB) in a first time window or a second time window.15.The network device of claim 14, wherein the network device is further caused to:transmit the RAR message within the first time window.16.The network device of claim 15, wherein at least one of the following:the indication is provided in an RAR payload;the indication is provided in an RAR control resource set (CORESET) ; orthe indication is implicitly provided based on interpretation of RAR CORESET parameters.17.The network device of any one of claims 14 to 16, wherein the SSB indicates that the network device switches to a SIB1 broadcasting mode from an on-demand (OD) -SIB1 mode.18.The network device of claim any one of claims 14 to 17, wherein the SSB carries an K_SSB less than 24 for frequency range 1 and K_SSB less than 12 for frequency range 2.19.The network device of any one of claims 14 to 18, wherein at least one of the following:the first time window is an RAR window for the reception of the RAR message; orthe second time window is an OD-SIB1 monitoring window after the reception of the RAR message.20.The network device of any one of claims 14 to 19, wherein at least one of the following:the first configuration information is an pdcchConfigSIB1 obtained from the UL WUS configuration; orthe second configuration information is an pdcchConfigSIB1 obtained from the SSB.21.A method comprising:obtaining first configuration information about system information block 1 (SIB1) from an uplink (UL) wake up signal (WUS) configuration;transmitting an UL WUS to a network device based on the UL WUS configuration;based on receiving a synchronization signal block (SSB) in a first time window or a second time window, obtaining second configuration information comprising at least SIB1 monitoring information;stopping monitoring the SIB1 based on the first configuration information; andmonitoring the SIB1 based on the second configuration information.22.A method comprising:receiving an uplink (UL) wake up signal (WUS) ;transmitting an indication associated with a random access response (RAR) message, the indication being configured to indicate whether to fall back to broadcasted SIB1 monitoring; andtransmitting a synchronization signal block (SSB) in a first time window or a second time window.23.An apparatus comprising:means for obtaining first configuration information about system information block 1 (SIB1) from an uplink (UL) wake up signal (WUS) configuration;means for transmitting an UL WUS to a network device based on the UL WUS configuration;means for obtaining second configuration information comprising at least SIB1 monitoring information based on receiving a synchronization signal block (SSB) in a first time window or a second time window;means for stopping monitoring the SIB1 based on the first configuration information; andmeans for monitoring the SIB1 based on the second configuration information.24.An apparatus comprising:means for receiving an uplink (UL) wake up signal (WUS) ;means for transmitting an indication associated with a random access response (RAR) message, the indication being configured to indicate whether to fall back to broadcasted SIB1 monitoring; andmeans for transmitting a synchronization signal block (SSB) in a first time window or a second time window.25.A computer readable medium comprising program instructions that, when executed by an apparatus, cause the apparatus to perform at least one of the methods of claims 21 and 22.