SIB1 transmission
Patent Information
- Application Number
- PCT/CN2024/075044
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2024-01-31
- Publication Date
- 2024-11-21
Smart Images

Figure CN2024075044_21112024_PF_FP_ABST
Abstract
Description
SIB1 TRANSMISSION
[0001] The present disclosure relates to wireless communications, and more specifically to system information block 1 (SIB1) transmission, in particular, for network energy saving.BACKGROUND
[0002] A wireless communications system may include one or multiple network communication devices, such as base stations, which may be otherwise known as an eNodeB (eNB) , a next-generation NodeB (gNB) , or other suitable terminology. Each network communication devices, such as a base station may support wireless communications for one or multiple user communication devices, which may be otherwise known as user equipment (UE) , or other suitable terminology. The wireless communications system may support wireless communications with one or multiple user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers) . Additionally, the wireless communications system may support wireless communications across various radio access technologies including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, among other suitable radio access technologies beyond 5G (e.g., sixth generation (6G) ) .
[0003] In 5G new radio (NR) , system information (SI) can be delivered to the UE and the SI may be necessary for the UE to operate in NR system. There can be three types of SI:master information block (MIB) , SIB1, and other SI (OSI) . The SIB1 may contain information relevant for the UE to access the cell and information about other SI available in the cell. However, there are still some issues for SIB1 transmission to be addressed.SUMMARY
[0004] The present disclosure relates to methods, apparatuses, and systems that support SIB1 transmission, especially, for network energy saving.
[0005] Some implementations of the method and devices described herein include, receiving, via the transceiver from a base station, synchronization signal and physical broadcast channel (PBCH) blocks (SSBs) ; determining whether a system information block 1 (SIB1) is broadcasted based on information elements of a master information block (MIB) in the SSBs; and in the case that the SIB1 is not broadcasted, starting one of a physical random access channel (PRACH) procedure for system information block (SIB) requesting or a PRACH procedure for SIB1 requesting and cell accessing. In this way, the power consumption on SIB1 transmission is reduced.
[0006] Some implementations of the method and apparatuses described herein may further include: in the case that the first information element indicates that a cell is not barred and the second information element indicates that the SIB1 is transmitted, determining that the SIB1 is broadcasted by the cell; in the case that the first information element indicates that a cell is barred and the second information element indicates that the SIB1 is transmitted, determining that the SIB1 is not broadcasted by the cell and is on-demand triggered; and in the case that the second information element indicates that the SIB1 is not transmitted, determining that the SIB1 is not transmitted by the cell.
[0007] Some implementations of the method and apparatuses described herein may further include: in the case that a contention resolution fails, restarting a PRACH procedure without SIB1 requesting.
[0008] Some implementations of the method and apparatuses described herein may further include in the case that the Msg2 comprises the DL grant, determining that the SIB1 is scheduled by the DL grant; and in the case that the Msg2 comprises the preamble for acknowledging the requesting of SIB1 transmission, determining that the SIB1 is transmitted periodically.
[0009] Some implementations of the method and apparatuses described herein may further include obtaining a set of preambles for the Msg1 transmission associated with one of SIB1 requesting and cell accessing, or SIB requesting; and performing the Msg1 transmission with a preamble among the set of preambles.
[0010] Some implementations of the method and apparatuses described herein may further include determining, based on the PUCCH indicator, a PUCCH resource for hybrid automatic repeat request acknowledgement (HARQ-ACK) for the SIB1 reception.
[0011] Some implementations of the method and apparatuses described herein may further include starting a timer for a SIB1 retransmission in the case that a SIB1 reception is failed; transmitting, to the base station, a second DCI format for scheduling the SIB1 retransmission; and monitoring the SIB1 from the base station before the timer expires.
[0012] Some implementations of the method and apparatuses described herein may further include determining that a PRACH procedure is failed in the case that the SIB1 reception is failed; and restarting the PRACH procedure.
[0013] In some implementations of the method and apparatuses described herein, the information elements may comprise a first information element indicative of cell barring and a second information element indicative of a SSB subcarrier offset, wherein the SSB subcarrier offset is associated with whether the SIB1 is transmitted.
[0014] In some implementations of the method and apparatuses described herein, the PRACH procedure for SIB1 requesting and cell accessing may comprise one of the following: Msg1 transmission, Msg2 reception, SIB1 reception, Msg3 transmission or Msg4 reception.
[0015] In some implementations of the method and apparatuses described herein, an initial Msg3 transmission may be scheduled by a first downlink control information (DCI) format.
[0016] In some implementations of the method and apparatuses described herein, the PRACH procedure for SIB requesting may comprise a PRACH procedure for SIB1 requesting and a PRACH procedure for other SIB requesting.
[0017] In some implementations of the method and apparatuses described herein, the PRACH procedure for SIB1 requesting may comprise Msg1 transmission, Msg2 reception and SIB1 reception.
[0018] In some implementations of the method and apparatuses described herein, the PRACH procedure for other SIB requesting may comprise Msg1 transmission, Msg2 reception, SIB1 reception, and other SIB reception.
[0019] In some implementations of the method and apparatuses described herein, the Msg2 may comprise one of a downlink (DL) grant for scheduling the SIB1 or a preamble for acknowledging the requesting of SIB1 transmission.
[0020] In some implementations of the method and apparatuses described herein, the set of preambles may be obtained from a configuration either from the anchored cell or from a non-anchored cell.
[0021] In some implementations of the method and apparatuses described herein, the DL grant may comprise at least one of following: allocation for time domain resource, allocation for frequency domain resource, a modulation and coding scheme (MCS) and a physical uplink control channel (PUCCH) indicator.
[0022] Some implementations of the method and devices described herein include, transmitting, via the transceiver to a user equipment, synchronization signal and physical broadcast channel (PBCH) blocks (SSBs) , wherein whether a system information block 1 (SIB1) is broadcasted is indicated based on information elements of a master information block (MIB) in the SSBs; and starting, for a user equipment, one of a physical random access channel (PRACH) procedure for system information block (SIB) requesting or a PRACH procedure for SIB1 requesting and cell accessing. In this way, the power consumption on SIB1 transmission is reduced.
[0023] Some implementations of the method and apparatuses described herein may further include receiving, from the user equipment, a request for restarting a PRACH procedure without SIB1 requesting in the case that a contention resolution fails.
[0024] Some implementations of the method and apparatuses described herein may further include: in the case that the Msg1 reception comprises a first preamble associated with the SIB1 requesting and the cell accessing, starting the PRACH procedure for SIB1 requesting and cell accessing; in the case that the Msg1 reception comprises a second preamble associated with the SIB1 requesting, starting a PRACH procedure for the SIB1 requesting; and in the case that the Msg1 reception comprises a third preamble associated with the other SIB requesting, starting a PRACH procedure for the other SIBrequesting.
[0025] Some implementations of the method and apparatuses described herein may further include receiving, from the user equipment, a second DCI format for scheduling a SIB1 retransmission in the case that a SIB1 transmission is failed; and performing the SIB1 retransmission to the user equipment.
[0026] Some implementations of the method and apparatuses described herein may further include receiving a request for restarting a PRACH procedure in the case that the SIB1 transmission is failed.
[0027] In some implementations of the method and apparatuses described herein, the information elements may comprise a first information element indicative of cell barring and a second information element indicative of a SSB subcarrier offset, wherein the SSB subcarrier offset is associated with whether the SIB1 is transmitted.
[0028] In some implementations of the method and apparatuses described herein, in the case that the SIB1 is broadcasted by the cell, the first information element may indicate that a cell is not barred and the second information element indicates that the SIB1 is transmitted; in the case that the SIB1 is not broadcasted by the cell and is on-demand triggered, the first information element indicates that a cell is barred and the second information element may indicate that the SIB1 is transmitted; or in the case that the SIB1 is not transmitted by the cell, the second information element may indicate that the SIB1 is not transmitted.
[0029] In some implementations of the method and apparatuses described herein, the PRACH procedure for SIB1 requesting and cell accessing may comprise one of the following: Msg1 reception, Msg2 transmission, SIB1 transmission, Msg3 reception or Msg4 transmission.
[0030] In some implementations of the method and apparatuses described herein, an initial Msg3 reception may be scheduled by a first downlink control information (DCI) format.
[0031] In some implementations of the method and apparatuses described herein, the PRACH procedure for SIB requesting may comprise one of the following: a PRACH procedure for SIB1 requesting and a PRACH procedure for other SIB requesting.
[0032] In some implementations of the method and apparatuses described herein, the PRACH procedure for SIB1 requesting may comprise: Msg1 reception, Msg2 transmission and SIB1 transmission.
[0033] In some implementations of the method and apparatuses described herein, the PRACH procedure for other SIB requesting may comprise one of the following: Msg1 reception, Msg2 transmission, SIB1 transmission, and other SIB transmission.
[0034] In some implementations of the method and apparatuses described herein, the Msg2 may comprise one of a downlink (DL) grant for scheduling the SIB1 or a preamble for acknowledging the requesting of SIB1 transmission.
[0035] In some implementations of the method and apparatuses described herein, the DL grant may comprise at least one of following: an allocation for time domain resource, an allocation for frequency domain resource, a modulation and coding scheme (MCS) and a physical uplink control channel (PUCCH) indicator.BRIEF DESCRIPTION OF THE DRAWINGS
[0036] FIG. 1A illustrates an example of a wireless communications system that supports SIB1 transmission for network energy saving in accordance with aspects of the present disclosure.
[0037] FIG. 1B illustrates an example procedure of Msg1 based mechanism associated with aspects of the present disclosure.
[0038] FIG. 1C illustrates an example of a sub-protocol data unit (sub-PDU) associated with aspects of the present disclosure.
[0039] FIG. 1D illustrates an example procedure of Msg3 based mechanism associated with aspects of the present disclosure.
[0040] FIG. 1E illustrates an example of separate random access channel (RACH) procedures for SIB1 requesting and cell accessing associated with aspects of the present disclosure.
[0041] FIG. 2 illustrates an example signaling chart illustrating an example process that supports SIB1 transmission for network energy saving in accordance with aspects of the present disclosure.
[0042] FIG. 3 illustrates an example of a random access response (RAR) sub-PDU format.
[0043] FIG. 4 illustrates an example of an RAR sub-PDU format in accordance with aspects of the present disclosure.
[0044] FIG. 5 illustrates an example procedure for both SIB1 requesting and cell accessing in accordance with aspects of the present disclosure.
[0045] FIG. 6 illustrates an example procedure for other SIB requesting in accordance with aspects of the present disclosure.
[0046] FIGS. 7 and 8 illustrate examples of devices that support SIB1 transmission for network energy saving in accordance with aspects of the present disclosure.
[0047] FIGS. 9 and 10 illustrate examples of processors that support SIB1 transmission for network energy saving in accordance with aspects of the present disclosure.
[0048] FIG. 11 illustrates a flowchart of a method that supports SIB1 transmission for network energy saving in accordance with aspects of the present disclosure.
[0049] FIG. 12 illustrates a flowchart of a method that supports SIB1 transmission for network energy saving in accordance with aspects of the present disclosure.
[0050] Throughout the drawings, the same or similar reference numerals represent the same or similar elements.DETAILED DESCRIPTION
[0051] Principles of the present disclosure will now be described with reference to some 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 may be implemented in various manners other than the ones described below.
[0052] 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.
[0053] References in the present disclosure to “one embodiment, ” “an example embodiment, ” “an embodiment, ” “some embodiments, ” and the like indicate that the embodiment (s) 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 do not necessarily refer to the same embodiment (s) . 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.
[0054] It shall be understood that although the terms “first” and “second” or the like 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 element. For example, a first element could also be termed as a second element, and similarly, a second element could also be termed as a first element, without departing from the scope of embodiments. As used herein, the term “and / or” includes any and all combinations of one or more of the listed terms.
[0055] 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.
[0056] As used herein, the term “communication network” refers to a network following any suitable communication standards, such as, 5G new radio (NR) , 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. Further, the communications between a user equipment 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 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 also be future type communication technologies and systems in which the present disclosure may be embodied. It should not be seen as limiting the scope of the present disclosure to only the aforementioned systems.
[0057] As used herein, the term “network device” generally refers to a node in a communication network via which a user equipment can access the communication network and receive 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) , a radio access network (RAN) node, an evolved NodeB (eNodeB or eNB) , a NR NB (also referred to as a gNB) , a Remote Radio Unit (RRU) , a radio header (RH) , an infrastructure device for a V2X (vehicle-to-everything) communication, a transmission and reception point (TRP) , a reception point (RP) , a remote radio head (RRH) , a relay, an integrated access and backhaul (IAB) node, a low power node such as a femto BS, a pico BS, and so forth, depending on the applied terminology and technology. The network device may further refer to a network function (NF) in the core network, for example, a SMF, an AMF, a PCF, a UPF or devices with same function in future network architectures, and so forth.
[0058] As used herein, the term “user equipment (UE) ” generally refers to any end device that may be capable of wireless communications. By way of example rather than a limitation, a user equipment may also be referred to as a communication device, a terminal device, an end user device, a subscriber station (SS) , an unmanned aerial vehicle (UAV) , a portable subscriber station, a mobile station (MS) , or an access terminal (AT) . The user equipment may include, but is not limited to, a mobile phone, a cellular phone, a smart phone, a voice over IP (VoIP) phone, a wireless local loop phone, a tablet, a wearable user equipment, a personal digital assistant (PDA) , a portable computer, a desktop computer, an image capture user equipment such as a digital camera, a gaming user equipment, a music storage and playback appliance, a vehicle-mounted wireless user equipment, a wireless endpoint, a mobile station, laptop-embedded equipment (LEE) , laptop-mounted equipment (LME) , a USB dongle, a smart device, 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 (for example, a remote surgery device) , an industrial device (for example, 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: “user equipment, ” “communication device, ” “terminal, ” “user equipment” and “UE, ” may be used interchangeably.
[0059] FIG. 1A illustrates an example of a wireless communications system 100A that supports store and forward operations in accordance with aspects of the present disclosure. The wireless communications system 100A may include one or more network entities 102 (also referred to as network equipment (NE) ) , one or more UEs 104, a core network 106, and a packet data network 108. The wireless communications system 100A may support various radio access technologies. In some implementations, the wireless communications system 100A may be a 4G network, such as an LTE network or an LTE-Advanced (LTE-A) network. In some other implementations, the wireless communications system 100A may be a 5G network, such as an NR network. In other implementations, the wireless communications system 100A may be a combination of a 4G network and a 5G network, or other suitable radio access technology including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , IEEE 802.20. The wireless communications system 100A may support radio access technologies beyond 5G. Additionally, the wireless communications system 100A may support technologies, such as time division multiple access (TDMA) , frequency division multiple access (FDMA) , or code division multiple access (CDMA) , etc.
[0060] The one or more network entities 102 may be dispersed throughout a geographic region to form the wireless communications system 100A. One or more of the network entities 102 described herein may be or include or may be referred to as a network node, a base station, a network element, a radio access network (RAN) , a base transceiver station, an access point, a NodeB, an eNodeB (eNB) , a next-generation NodeB (gNB) , or other suitable terminology. A network entity 102 and a UE 104 may communicate via a communication link 110, which may be a wireless or wired connection. For example, a network entity 102 and a UE 104 may perform wireless communication (e.g., receive signaling, transmit signaling) over a Uu interface.
[0061] A network entity 102 may provide a geographic coverage area 112 for which the network entity 102 may support services (e.g., voice, video, packet data, messaging, broadcast, etc. ) for one or more UEs 104 within the geographic coverage area 112. For example, a network entity 102 and a UE 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc. ) according to one or multiple radio access technologies. In some implementations, a network entity 102 may be moveable, for example, a satellite associated with a non-terrestrial network. In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies may overlap, but the different geographic coverage areas 112 may be associated with different network entities 102. Information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
[0062] The one or more UEs 104 may be dispersed throughout a geographic region of the wireless communications system 100A. A UE 104 may include or may be referred to as a mobile device, a wireless device, a remote device, a remote unit, a handheld device, or a subscriber device, or some other suitable terminology. In some implementations, the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples. Additionally, or alternatively, the UE 104 may be referred to as an Internet-of-Things (IoT) device, an Internet-of-Everything (IoE) device, or machine-type communication (MTC) device, among other examples. In some implementations, a UE 104 may be stationary in the wireless communications system 100A. In some other implementations, a UE 104 may be mobile in the wireless communications system 100A.
[0063] The one or more UEs 104 may be devices in different forms or having different capabilities. Some examples of UEs 104 are illustrated in FIG. 1A. A UE 104 may be capable of communicating with various types of devices, such as the network entities 102, other UEs 104, or network equipment (e.g., the core network 106, the packet data network 108, a relay device, an integrated access and backhaul (IAB) node, or another network equipment) , as shown in FIG. 1A. Additionally, or alternatively, a UE 104 may support communication with other network entities 102 or UEs 104, which may act as relays in the wireless communications system 100A.
[0064] A UE 104 may also be able to support wireless communication directly with other UEs 104 over a communication link 114. For example, a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular-V2X deployments, the communication link 114 may be referred to as a sidelink. For example, a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface.
[0065] A network entity 102 may support communications with the core network 106, or with another network entity 102, or both. For example, a network entity 102 may interface with the core network 106 through one or more backhaul links 116 (e.g., via an S1, N2, N2, or another network interface) . The network entities 102 may communicate with each other over the backhaul links 116 (e.g., via an X2, Xn, or another network interface) . In some implementations, the network entities 102 may communicate with each other directly (e.g., between the network entities 102) . In some other implementations, the network entities 102 may communicate with each other or indirectly (e.g., via the core network 106) . In some implementations, one or more network entities 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC) . An ANC may communicate with the one or more UEs 104 through one or more other access network transmission entities, which may be referred to as a radio heads, smart radio heads, or transmission-reception points (TRPs) .
[0066] In some implementations, a network entity 102 may be configured in a disaggregated architecture, which may be configured to utilize a protocol stack physically or logically distributed among two or more network entities 102, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance) , or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN) ) . For example, a network entity 102 may include one or more of a central unit (CU) , a distributed unit (DU) , a radio unit (RU) , a RAN Intelligent Controller (RIC) (e.g., a Near-Real Time RIC (Near-RT RIC) , a Non-Real Time RIC (Non-RT RIC) ) , a Service Management and Orchestration (SMO) system, or any combination thereof.
[0067] An RU may also be referred to as a radio head, a smart radio head, a remote radio head (RRH) , a remote radio unit (RRU) , or a transmission reception point (TRP) . One or more components of the network entities 102 in a disaggregated RAN architecture may be co-located, or one or more components of the network entities 102 may be located in distributed locations (e.g., separate physical locations) . In some implementations, one or more network entities 102 of a disaggregated RAN architecture may be implemented as virtual units (e.g., a virtual CU (VCU) , a virtual DU (VDU) , a virtual RU (VRU) ) .
[0068] Split of functionality between a CU, a DU, and an RU may be flexible and may support different functionalities depending upon which functions (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combinations thereof) are performed at a CU, a DU, or an RU. For example, a functional split of a protocol stack may be employed between a CU and a DU such that the CU may support one or more layers of the protocol stack and the DU may support one or more different layers of the protocol stack. In some implementations, the CU may host upper protocol layer (e.g., a layer 3 (L3) , a layer 2 (L2) ) functionality and signaling (e.g., Radio Resource Control (RRC) , service data adaption protocol (SDAP) , Packet Data Convergence Protocol (PDCP) ) . The CU may be connected to one or more DUs or RUs, and the one or more DUs or RUs may host lower protocol layers, such as a layer 1 (L1) (e.g., physical (PHY) layer) or an L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160.
[0069] Additionally, or alternatively, a functional split of the protocol stack may be employed between a DU and an RU such that the DU may support one or more layers of the protocol stack and the RU may support one or more different layers of the protocol stack. The DU may support one or multiple different cells (e.g., via one or more RUs) . In some implementations, a functional split between a CU and a DU, or between a DU and an RU may be within a protocol layer (e.g., some functions for a protocol layer may be performed by one of a CU, a DU, or an RU, while other functions of the protocol layer are performed by a different one of the CU, the DU, or the RU) .
[0070] A CU may be functionally split further into CU control plane (CU-CP) and CU user plane (CU-UP) functions. A CU may be connected to one or more DUs via a midhaul communication link (e.g., F1, F1-c, F1-u) , and a DU may be connected to one or more RUs via a fronthaul communication link (e.g., open fronthaul (FH) interface) . In some implementations, a midhaul communication link or a fronthaul communication link may be implemented in accordance with an interface (e.g., a channel) between layers of a protocol stack supported by respective network entities 102 that are in communication via such communication links.
[0071] The core network 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The core network 106 may be an evolved packet core (EPC) , or a 5G core (5GC) , which may include a control plane entity that manages access and mobility (e.g., a mobility management entity (MME) , an access and mobility management functions (AMF) ) and a user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW) , a Packet Data Network (PDN) gateway (P-GW) , or a user plane function (UPF) ) . In some implementations, the control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc. ) for the one or more UEs 104 served by the one or more network entities 102 associated with the core network 106.
[0072] The core network 106 may communicate with the packet data network 108 over one or more backhaul links 116 (e.g., via an S1, N2, N2, or another network interface) . The packet data network 108 may include an application server 118. In some implementations, one or more UEs 104 may communicate with the application server 118. A UE 104 may establish a session (e.g., a protocol data unit (PDU) session, or the like) with the core network 106 via a network entity 102. The core network 106 may route traffic (e.g., control information, data, and the like) between the UE 104 and the application server 118 using the established session (e.g., the established PDU session) . The PDU session may be an example of a logical connection between the UE 104 and the core network 106 (e.g., one or more network functions of the core network 106) .
[0073] In the wireless communications system 100A, the network entities 102 and the UEs 104 may use resources of the wireless communications system 100A (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers) ) to perform various operations (e.g., wireless communications) . In some implementations, the network entities 102 and the UEs 104 may support different resource structures. For example, the network entities 102 and the UEs 104 may support different frame structures. In some implementations, such as in 4G, the network entities 102 and the UEs 104 may support a single frame structure. In some other implementations, such as in 5G and among other suitable radio access technologies, the network entities 102 and the UEs 104 may support various frame structures (i.e., multiple frame structures) . The network entities 102 and the UEs 104 may support various frame structures based on one or more numerologies.
[0074] One or more numerologies may be supported in the wireless communications system 100A, and a numerology may include a subcarrier spacing and a cyclic prefix. A first numerology (e.g., μ=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first numerology (e.g., μ=0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe. A second numerology (e.g., μ=1) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., μ=2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth numerology (e.g., μ=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth numerology (e.g., μ=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.
[0075] A time interval of a resource (e.g., a communication resource) may be organized according to frames (also referred to as radio frames) . Each frame may have a duration, for example, a 10 millisecond (ms) duration. In some implementations, each frame may include multiple subframes. For example, each frame may include 10 subframes, and each subframe may have a duration, for example, a 1 ms duration. In some implementations, each frame may have the same duration. In some implementations, each subframe of a frame may have the same duration.
[0076] Additionally or alternatively, a time interval of a resource (e.g., a communication resource) may be organized according to slots. For example, a subframe may include a number (e.g., quantity) of slots. The number of slots in each subframe may also depend on the one or more numerologies supported in the wireless communications system 100A. For instance, the first, second, third, fourth, and fifth numerologies (i.e., μ=0, μ=1, μ=2, μ=3, μ=4) associated with respective subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may utilize a single slot per subframe, two slots per subframe, four slots per subframe, eight slots per subframe, and 16 slots per subframe, respectively. Each slot may include a number (e.g., quantity) of symbols (e.g., OFDM symbols) . In some implementations, the number (e.g., quantity) of slots for a subframe may depend on a numerology. For a normal cyclic prefix, a slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable for 60 kHz subcarrier spacing) , a slot may include 12 symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for a normal cyclic prefix and an extended cyclic prefix may depend on a numerology. It should be understood that reference to a first numerology (e.g., μ=0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.
[0077] In the wireless communications system 100A, an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc. By way of example, the wireless communications system 100A may support one or multiple operating frequency bands, such as frequency range designations FR1 (410 MHz –7.125 GHz) , FR2 (24.25 GHz –52.6 GHz) , FR3 (7.125 GHz –24.25 GHz) , FR4 (52.6 GHz –114.25 GHz) , FR4a or FR4-1 (52.6 GHz –71 GHz) , and FR5 (114.25 GHz –300 GHz) . In some implementations, the network entities 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands. In some implementations, FR1 may be used by the network entities 102 and the UEs 104, among other equipment or devices for cellular communications traffic (e.g., control information, data) . In some implementations, FR2 may be used by the network entities 102 and the UEs 104, among other equipment or devices for short-range, high data rate capabilities.
[0078] FR1 may be associated with one or multiple numerologies (e.g., at least three numerologies) . For example, FR1 may be associated with a first numerology (e.g., μ=0) , which includes 15 kHz subcarrier spacing; a second numerology (e.g., μ=1) , which includes 30 kHz subcarrier spacing; and a third numerology (e.g., μ=2) , which includes 60 kHz subcarrier spacing. FR2 may be associated with one or multiple numerologies (e.g., at least 2 numerologies) . For example, FR2 may be associated with a third numerology (e.g., μ=2) , which includes 60 kHz subcarrier spacing; and a fourth numerology (e.g., μ=3) , which includes 120 kHz subcarrier spacing.
[0079] In 5G NR, SI is delivered to the UE and the SI is necessary for the UE to operate in NR system. There are three types of SI: master information block (MIB) , SIB1, and other SI (OSI) . The MIB contains basic cell configurations and information required for the UE to acquire SIB1. The MIB is transmitted in physical broadcast channel (PBCH) of synchronization signal and PBCH blocks (SSBs) and broadcasted to the UEs in the cell. The SIB1 contains information relevant for the UE to access the cell and information about other SI available in the cell. SIB1 is broadcasted to the UEs in the cell. OSI includes all other SIBs (SIBx) except SIB1. Each SIBx may correspond to configurations for specific features. An OSI can be either broadcasted or unicast to the UE.
[0080] If a SIBx is indicated to be available in the cell, and the related configuration si-BroadcastStatus is set to “broadcasting” , the UE determines that the SIBx is broadcasted by the network, and the UE could acquire the SIBx in one of the configured time occasions based on scheduling. If si-BroadcastStatus is set to “notBroadcasting” , the UE may request the SI message via an on-demand SI mechanism.
[0081] Two on-demand SI mechanisms have been specified for requesting the SI message based on gNB configuration. An on-demand SI mechanism is Msg1 based mechanism and the other on-demand SI mechanism is Msg3 based mechanism.
[0082] FIG. 1B illustrates an example procedure 100B of Msg1 based mechanism associated with aspects of the present disclosure. As shown in FIG. 1B, the UE requests SI via dedicated preambles in Msg1. The UE may be provided with dedicated ROs and dedicated preambles in SIB1 to request the SI. Upon sending dedicated Msg1 preamble in a dedicated RO, the UE may receive RAR comprising an acknowledgement for the SI request. As shown in FIG. 1C, the RAR sub-PDU contains a preamble identity (ID) .
[0083] FIG. 1D illustrates an example procedure 100D of Msg3 based mechanism associated with aspects of the present disclosure. As shown in FIG. 1D, the UE requests SI through RRCSystemInfoRequest in Msg3. The UE may receive acknowledgement of the SI request in Msg4.
[0084] In Rel-19, not only OSI, but SIB1 might be on-demand transmitted instead of always broadcasted. With this way, the gNB does not need to periodically broadcast SIB1 and the gNB may transmit the SIB1 based on UE requesting. This is beneficial in terms of network energy saving, which is an objective of NR Rel-19 to achieve. Based on this objective, if a Rel-19 UE needs SIB1, it might send a wake-up signal (WUS) to gNB to request the SIB1 transmission. From gNB point of view, SIB1 might not be transmitted unless requested by a UE. This reduces power consumption on SIB1 transmission in gNB especially in low system load scenario.
[0085] To reduce standard impact, it could be considered to reuse on-demand SI mechanisms (Msg1 based or Msg3 based mechanism) for on-demand SIB1 as much as possible.
[0086] FIG. 1E illustrates an example of separate RACH procedures 100E for SIB1 requesting and cell accessing associated with aspects of the present disclosure. As shown in FIG. 1E, with Msg1 based SIB1 requesting, when a UE accesses the cell, the UE may firstly start a RACH procedure for requesting SIB1. After acquiring SIB1, the UE may start another RACH procedure for cell accessing. It should be noted that here SIB1 is assumed to be periodically transmitted upon requested (e.g., with a 20ms periodicity) , leading to long gNB active time and high power consumption.
[0087] It could be observed that due to so many involved steps, using two RACH procedures for SIB1 requesting and cell accessing may cause relatively large signalling overhead and high gNB power consumption. Besides, periodically transmitted SIB1 in the procedure is another factor contributing high gNB power consumption, as mentioned above.
[0088] In addition, when a Rel-19 UE needs to decode SIB1 of a cell, e.g., when the UE is in RRC INACTIVE / IDLE and decides to switch to RRC CONNECTED, or the UE is power on and looks for SSB and SIB1 in each predefined synchronization raster, the UE should be provided whether current SIB1 is broadcasted or not. If SIB1 is broadcasted, the UE could decode SIB1 and does not need to send the WUS. Otherwise, the WUS needs to be transmitted to trigger the gNB to send SIB1 for the UE. Therefore, the UE need to determine the status of SIB1 transmission in the cell, based on which to determine whether to send WUS for obtaining SIB1.
[0089] In view of the above discussions, some embodiments of the present disclosure provide a solution for SIB1 transmission, for example, for network energy saving. In one aspect of the solution of the present disclosure, a user equipment receives synchronization signal and physical broadcast channel (PBCH) blocks (SSBs) from a base station. The UE may first determine whether SIB1 is currently broadcasted in the network. The determination could be based on information elements of a master information block (MIB) in the SSBs. . In the case that the SIB1 is not broadcasted, the user equipment starts one of a physical random access channel (PRACH) procedure for system information block (SIB) requesting or a PRACH procedure for SIB1 requesting and cell accessing. In this way, the user equipment may determine the status of SIB1 transmission and request the SIB1 based on the status of SIB1 transmission. Therefore, the power consumption on SIB1 transmission is reduced. Principles and implementations of embodiments of the present disclosure will be described in detail below with reference to FIGS. 2-12.
[0090] FIG. 2 illustrates a signaling chart illustrating an example process 200 in accordance with aspects of the present disclosure. The process 200 may involve the user equipment 201 and the base station 202. It would be appreciated that although the process 200 is applied in the communication environment 100A of FIG. 1A, this process may be likewise applied to other communication scenarios with similar issues.
[0091] In the process 200, the base station 202 transmits 210 SSBs 215 to the user equipment 201, and whether a SIB1 is broadcasted is indicated based on information elements of a MIB in the SSBs. On the other side of the communication, the user equipment 201 receives 220 the SSBs 215 from the base station 202.
[0092] With on-demand SIB1, the user equipment 201 may identify up to three cases of SSB and SIB1 transmission in the cell. In the first case, cell defining SSBs are transmitted and SIB1 is broadcasted in the cell. In the second case, cell defining SSBs are transmitted and SIB1 is not broadcasted but may be on-demand triggered. In the third case, non-cell defining SSBs or SSBs for measurement are transmitted and SIB1 is not transmitted. Here cell defining SSBs carries information regarding the scheduling of SIB1 while non-cell defining SSB does not carry such information.
[0093] For a cell supporting on-demand SIB1, the base station 202 may broadcast SIB1 in one period (e.g., in case medium or high load) and transmit SIB1 based on triggering in another period (e.g., in case low load) . The former case can allow UEs not supporting on-demand SSB to access the cell, while in the latter case, it may avoid a RRC IDLE / INACTIVE UE not supporting on-demand SIB1 to access the cell since in this case the UE keeps detecting SIB1 but SIB1 is not actually transmitted.
[0094] Based on information elements of a MIB in the SSBs, the user equipment 201 determines 225 whether a SIB1 is broadcasted. For example, the user equipment 201 may determine the status of SIB1 transmission in its serving cell to determine whether to send a WUS for obtaining SIB1.
[0095] Alternatively or additionally, the information elements may comprise a first information element indicative of cell barring and a second information element indicative of a SSB subcarrier offset, and the SSB subcarrier offset is associated with whether the SIB1 is transmitted.
[0096] An information element in MIB, ssb-SubcarrierOffset (named also as kssb) , have been used in NR to indicate whether SIB1 is provided by the cell. For FR1, if 0≤k_ssb≤23, the user equipment 201 assumes that SIB1 is provided by the cell. If 24≤k_ssb≤31, the user equipment 201 assumes that SIB1 is not provided. For FR2, if 0≤k_ssb≤11, the user equipment 201 assumes that SIB1 is provided by the cell. If 12≤k_ssb≤15, the user equipment 201 assumes that SIB1 is not provided.
[0097] In order not to impact UEs not supporting on-demand SSB, the user equipment 201 may determine the status of SIB1 transmission (i.e., the above three cases) based on information elements comprising cellBarred and ssb-SubcarrierOffset in MIB.
[0098] In some embodiments, if the first information element indicates that a cell is not barred and the second information element indicates that the SIB1 is transmitted, the user equipment 201 may determine that the SIB1 is broadcasted by the cell. For example, if cellBarred in MIB indicates “notBarred” and ssb-SubcarrierOffset indicates that SIB1 is transmitted, the user equipment 201 may assume that SIB1 is broadcasted when accessing the cell.
[0099] In some embodiments, if the first information element indicates that a cell is barred and the second information element indicates that the SIB1 is transmitted, the user equipment 201 may determine the SIB1 is not broadcasted by the cell and is on-demand triggered. For example, if cellBarred in MIB indicates “barred” and ssb-SubcarrierOffset indicates SIB1 is transmitted, the user equipment 201 may assume that SIB1 is not broadcasted and can be on-demand triggered.
[0100] In some embodiments, if the second information element indicates that the SIB1 is not transmitted, the user equipment 201 may determine that the SIB1 is not transmitted by the cell. For example, if ssb-SubcarrierOffset indicates SIB1 is not transmitted, the user equipment 201 may assume that SIB1 is not transmitted by the cell.
[0101] The UEs not supporting on-demand SIB1 cannot access the cell when on-demand SIB1 is used. CellBarred is indicated as “barred” may avoid the legacy UEs and UEs not supporting on-demand SIB1 from keeping detecting SIB1, which may not be transmitted by the base station 202.
[0102] Continuing with reference to FIG. 2, in the case that the SIB1 is not broadcasted, the user equipment 201 starts 230 one of a PRACH procedure for SIB requesting or a PRACH procedure for SIB1 requesting and cell accessing. On the other side of the communication, for the user equipment 201, the base station 202 starts 235 one of a PRACH procedure for SIB requesting or a PRACH procedure for SIB1 requesting and cell accessing. In other words, the user equipment 201 may request SIB1 from the base station 202 when the SIB1 is not broadcasted and the SIB1 can be on-demand triggered.
[0103] In some embodiments, the PRACH procedure for SIB1 requesting and cell accessing may comprise Msg1 transmission, Msg2 reception, SIB1 reception, Msg3 transmission and Msg4 reception. To reduce signalling overhead and reduce power consumption for on-demand SIB1, one RACH procedure may be used for both SIB1 requesting and cell accessing. From the point of the base station 202, the PRACH procedure for SIB1 requesting and cell accessing may comprise Msg1 reception, Msg2 transmission, SIB1 transmission, Msg3 reception and Msg4 transmission.
[0104] In some embodiments, the PRACH procedure for SIB requesting may comprise: a PRACH procedure for SIB1 requesting or a PRACH procedure for other SIB requesting. In other words, the user equipment 201 may request SIB1 transmission, but not accessing the cell.
[0105] In some implementations, the PRACH procedure for SIB1 requesting may comprise Msg1 transmission, Msg2 reception and SIB1 reception. From the point of the base station 202, the PRACH procedure for SIB1 requesting may comprise: Msg1 reception, Msg2 transmission and SIB1 transmission.
[0106] In an example, the user equipment 201 may need to detect a SIBx to obtain specific configurations. Before that, the user equipment 201 needs to detect SIB1 to obtain the configurations of SIBx. To identify such cases to the base station 202, the user equipment 201 may be provided with separate preambles. If a preamble is received from the separate preambles, the base station 202 will send RAR to the user equipment 201 to acknowledge the request. The contention resolution procedure, i.e., Msg3 and Msg4 transmission / reception, is not needed. The base station 202 will sends SIB1 to the user equipment 201 and then terminates the procedure.
[0107] In some embodiments, the PRACH procedure for other SIB requesting may comprise Msg1 transmission, Msg2 reception, SIB1 reception, and other SIB reception. From the point of the base station 202, the PRACH procedure for SIBx requesting may comprise Msg1 reception, Msg2 transmission, SIB1 transmission, and other SIB transmission.
[0108] In an example, when the user equipment 201 requests SIBx transmission while SIB1 is currently not transmitted by the base station 202, and the user equipment 201 is already provided with dedicated preambles for the requesting, the user equipment 201 does not need to firstly request SIB1 then request SIBx. The user equipment 201 may request SIBx and assume that SIB1 is transmitted before SIBx transmission, i.e., UE needs to detect SIB1 before SIBx detection. This reduces the steps on the SI requesting and is beneficial for network power saving. Upon sending the Msg1 requesting a SIBx transmission, the user equipment 201 may be provided with RAR to acknowledge the requesting.
[0109] In addition, the user equipment 201 may obtain a set of preambles for the Msg1 transmission associated with one of SIB1 requesting and cell accessing, or SIB requesting, then the user equipment 201 may perform the Msg1 transmission with a preamble among the set of preambles. In some embodiments, the set of preambles may be obtained from a configuration either from the anchored cell or from a non-anchored cell. For instance, the set of preambles might be obtained from a configuration from another cell or another carrier, or obtained from an RRC message from the anchor cell or anchor carrier.
[0110] Correspondingly, if the Msg1 reception comprises a first preamble associated with the SIB1 requesting and the cell accessing, the base station 202 may start the PRACH procedure for SIB1 requesting and cell accessing. If the Msg1 reception comprises a second preamble associated with the SIB1 requesting, the base station 202 may start a PRACH procedure for the SIB1 requesting. If the Msg1 reception comprises a third preamble associated with the other SIB requesting, the base station 202 may start a PRACH procedure for the other SIB requesting.
[0111] Alternatively or additionally, the Msg2 may comprise one of a DL grant for scheduling the SIB1 or a preamble for acknowledging the requesting of SIB1 transmission. With the DL grant, the SIB1 physical downlink shared channel (PDSCH) does not need to be periodically scheduled and transmitted in the preconfigured time occasions. This reduces the long activation of SIB1 transmission and is beneficial for network power saving. Alternatively, the UE may assume that SIB1 is still scheduled according to the configurations obtained from MIB, i.e., the configurations of control resource set and search space set related with SIB1 scheduling.
[0112] FIGS. 3 and 4 illustrate examples of an RAR sub-PDU format and the proposed RAR format, respectively. It can be seen that the structure is not changed and the difference between the RAR sub-PDU format in FIG. 3 and the proposed RAR format in FIG. 4 is that the UL grant in RAR sub-PDU (for Msg3 scheduling) of FIG. 3 is replaced with DL grant (for SIB1 PDSCH scheduling) . The timing advanced command, which is used for obtaining the UL transmission timing, and the temporary cell radio network temporary identifier (TC-RNTI) , which is used for scrambling the DCIs for DL and UL scheduling in the random access procedure, are not changed.
[0113] In some embodiments, if the Msg2 comprises the DL grant, the user equipment 201 may determine that the SIB1 is scheduled by the DL grant. In some embodiments, if the Msg2 comprises the preamble for acknowledging the requesting of SIB1 transmission, the user equipment 201 may determine that the SIB1 is transmitted according to the scheduling in the search space set configured in the MIB.
[0114] In an example, the user equipment 201 may determine whether SIB1 is scheduled by RAR, i.e., the Msg2, or is scheduled by a DCI in the search space set zero based on the format of the received RAR. For example, if the user equipment 201 receives an RAR sub-PDU containing the transmitted preamble, the user equipment 201 may assume that SIB1 will be scheduled periodically in the search space set zero configured in MIB. While if the user equipment 201 receives an RAR sub-PDU with the DL grant, the user equipment 201 may assume that SIB1 is scheduled by the DL grant.
[0115] As an alternative, the RAR sub-PDU may contain the transmitted preamble for acknowledging the requesting of SIB1 transmission, the user equipment 201 may detect SIB1 assuming SIB1 is broadcasted (i.e., scheduled based on DCI in the configured search space set 0) firstly and then detect SIBx after getting SIBx configurations from SIB1.
[0116] As another alternative, the RAR sub-PDU may contain DL grant, the user equipment 201 may detect SIB1 according to the DL grant firstly and then detect SIBx.
[0117] Additionally, the DL grant may comprise allocation for time domain resource, allocation for frequency domain resource, a MCS and a PUCCH indicator. For instance, the DL grant in the RAR contains at least time and frequency allocations for SIB1 PDSCH transmission, the MCS and the redundancy version. It may also contain a PUCCH resource indicator, which is used for HARQ-ACK feedback for SIB PDSCH. Table 1 shows an example on RAR DL format field.
[0118] Table 1. RAR DL format field
[0119] In some embodiments, if a SIB1 reception is failed, the user equipment 201 may start a timer for a SIB1 retransmission. Then the user equipment 201 may transmit a second DCI format for scheduling the SIB1 retransmission to the base station. Before the timer expires, the user equipment 201 may monitor the SIB1 from the base station 202.
[0120] Correspondingly, if a SIB1 transmission is failed, the user equipment 201 may receive a second DCI format for scheduling a SIB1 retransmission from the user equipment. The user equipment 201 may then perform the SIB1 retransmission to the user equipment.
[0121] Alternatively or additionally, if the SIB1 reception is failed, the user equipment 201 may determine that a PRACH procedure is failed, the user equipment 201 may then restart the PRACH procedure. Correspondingly, if the SIB1 transmission is failed, the base station 202 may receive a request for restarting a PRACH procedure. Alternatively or additionally, based on the PUCCH indicator, the user equipment 201 may determine a PUCCH resource for HARQ-ACK for the SIB1 reception.
[0122] In an example, if RAR is not received within the configured RAR window, the user equipment 201 may determine that the RACH procedure is failed and may restart a proposed RACH procedure.
[0123] In another example, if RAR is received and the SIB1 PDSCH is successfully received, the user equipment 201 may obtain the common PUCCH resource configurations for HARQ-ACK feedback for DL messages transmitted in the RACH procedure (including Msg4 PDSCH and SIB1 PDSCH) . The user equipment 201 may determine a PUCCH resource from the common PUCCH resources based on the PUCCH resource indicator in the DL grant for HARQ-ACK feedback for SIB1 PDSCH. UE starts Msg3 transmission after sending HARQ-ACK.
[0124] In yet another example, if RAR is received while SIB1 PDSCH is not received by the user equipment 201, common PUCCH resources cannot be obtained, so the user equipment 201 will not provide HARQ-ACK feedback for SIB1 PDSCH. Alternatively or additionally, the user equipment 201 and the base station 202 may start a SIB1 PDSCH retransmission timer, within which the user equipment 201 needs to receive the retransmitted SIB1 PDSCH. The retransmitted SIB1 PDSCH can be scheduled using DCI format 1_0. Upon the time expires and SIB1 PDSCH is not received, the UE may determine that the RACH procedure is failed Alternatively or additionally, SIB1 PDSCH will never be retransmitted, and the user equipment 201may determine that the RACH procedure is failed if SIB1 PDSCH is not received.
[0125] In addition, an initial Msg3 transmission may be scheduled by a first DCI format. Since the UL grant for Msg3 scheduling is replaced with DL grant for SIB1 scheduling in RAR, both Msg3 first transmission and retransmissions (if happens) may be scheduled by DCI format 0_0. This is different with some other schemes where Msg3 first transmission is scheduled by UL grant in RAR, and the retransmission is scheduled by DCI format 0_0.
[0126] Additionally, if a contention resolution fails, the user equipment 201 may restart a PRACH procedure without SIB1 requesting. On the other side of the communication, if a contention resolution fails, the base station 202 may receive a request for restarting a PRACH procedure without SIB1 requesting from the user equipment.
[0127] For example, a contention resolution timer is started upon Msg3 scheduling starts. If the contention resolution fails, which means either Msg4 is not received or the ID of the user equipment 201 in the Msg4 does not match the one transmitted in Msg3, the user equipment 201 may restart the RACH procedure using a 4-step RACH procedure instead of the proposed RACH procedure, since SIB1 has already obtained by the user equipment 201 and no need to request it.
[0128] FIG. 5 illustrates an example procedure 500 for both SIB1 requesting and cell accessing in accordance with aspects of the present disclosure. The procedure 500 may involve a UE 501, a gNB 502. It is understood that the procedure 500 can be considered as a more specific example of the process 200 in FIG. 2. Thus, the UE 501 in FIG. 5 may be an example of the user equipment 201 in FIG. 2, the gNB 502 in FIG. 5 may be an example of the base station 202 in FIG. 2.
[0129] As shown in FIG. 5, at 505, the UE 501 performs the Msg1 transmission to the gNB 502. The Msg1 at 501 serves not only a WUS for requesting SIB1, but also requesting for accessing the cell. To meet this requirement, the UE may be provided with a set of preambles, which are dedicated for SIB1 requesting and cell accessing. From gNB point of view, if the gNB 502 receives a preamble from the set of preambles, the proposed PRACH procedure is used for SIB1 requesting and cell accessing.
[0130] At 510, the UE 501 receives RAR comprising an acknowledgement from the gNB 502. contains a DL grant, which is used to schedule SIB1 transmission. At 515, the UE 501 receives the requested SIB1 from the gNB 502. At 520, the UE 501 transmits the Msg3 to the gNB 502. At 550, the gNB 502 transmits the Msg4 to the UE 501.
[0131] FIG. 6 illustrates an example procedure 600 for SIBx requesting in accordance with aspects of the present disclosure. The procedure 600 may involve a UE 601, a gNB 602. It is understood that the procedure 600 can be considered as a more specific example of the process 200 in FIG. 2. Thus, the UE 601 in FIG. 6 may be an example of the user equipment 201 in FIG. 2, the gNB 602 in FIG. 6 may be an example of the base station 202 in FIG. 2.
[0132] As shown in FIG. 6, at 605, the UE 601 transmits Msg1 for requesting SIBx to the gNB 602. At 610, the gNB 602 transmits an RAR comprising an acknowledgement to the UE 601. If SIB1 is not broadcasted currently, the gNB 602 may use the DL grant in the RAR. At 615, the UE 601 receives the SIB1 from the gNB 602. At 620, the UE 601 receives the requested SIBx from the gNB 602.
[0133] In general, a PRACH procedure is used for both SIB1 requesting and cell accessing. For the PRACH procedure, a dedicated Msg1 preamble is provided to the UE for both SIB1 requesting and cell accessing. A new RAR format is used for SIB1 scheduling, and a DL grant is contained in the response RAR. Whether SIB1 is periodically transmitted or scheduled by RAR DL grant is determined based on RAR format. A PUCCH resource indicator is included in the RAR DL grant for HARQ-ACK feedback for SIB1 PDSCH. Msg3 initial transmission is scheduled by DCI format 0_0. If a contention resolution fails, the UE restarts a 4-step RACH procedure.
[0134] In addition, a new PRACH procedure is used for UE to request SIB1 or request SIBx when SIB1 is not broadcasted. For the PRACH procedure, dedicated preambles are provided for the UE to request SIB1 or request SIBx when SIB1 is not broadcasted. After sending the requests for SIBx, the UE may receive SIB1 before receive SIBx. How to receive SIB1 (either based on scheduling or based on DL grant in RAR) is determined based on RAR format. Furthermore, the status of SIB1 transmission is determined based on information elements comprising cellBarred, and ssb-SubcarrierOffset in MIB.
[0135] FIG. 7 illustrates an example of a device 700 that supports SIB1 transmission for network energy saving in accordance with aspects of the present disclosure. The device 700 may be an example of a UE 104 as described herein. The device 700 may support wireless communication with one or more network entities 102, UEs 104, or any combination thereof. The device 700 may include components for bi-directional communications including components for transmitting and receiving communications, such as a processor 702, a memory 704, a transceiver 706, and, optionally, an I / O controller 708. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses) .
[0136] The processor 702, the memory 704, the transceiver 706, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. For example, the processor 702, the memory 704, the transceiver 706, or various combinations or components thereof may support a method for performing one or more of the operations described herein.
[0137] In some implementations, the processor 702, the memory 704, the transceiver 706, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry) . The hardware may include a processor, a digital signal processor (DSP) , an application-specific integrated circuit (ASIC) , a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure. In some implementations, the processor 702 and the memory 704 coupled with the processor 702 may be configured to perform one or more of the functions described herein (e.g., executing, by the processor 702, instructions stored in the memory 704) .
[0138] For example, the processor 702 may support wireless communication at the device 700 in accordance with examples as disclosed herein. The processor 702 may be configured to operable to support a means for receiving, via the transceiver from a base station, synchronization signal and physical broadcast channel (PBCH) blocks (SSBs) ; a means for determining whether a system information block 1 (SIB1) is broadcasted based on information elements of a master information block (MIB) in the SSBs; and a means for in the case that the SIB1 is not broadcasted, starting one of a physical random access channel (PRACH) procedure for system information block (SIB) requesting or a PRACH procedure for SIB1 requesting and cell accessing. The processor 702 may be configured to operable to support other means for other implementations of method 1100.
[0139] The processor 702 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof) . In some implementations, the processor 702 may be configured to operate a memory array using a memory controller. In some other implementations, a memory controller may be integrated into the processor 702. The processor 702 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 704) to cause the device 700 to perform various functions of the present disclosure.
[0140] The memory 704 may include random access memory (RAM) and read-only memory (ROM) . The memory 704 may store computer-readable, computer-executable code including instructions that, when executed by the processor 702 cause the device 700 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some implementations, the code may not be directly executable by the processor 702 but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some implementations, the memory 704 may include, among other things, a basic I / O system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.
[0141] The I / O controller 708 may manage input and output signals for the device 700. The I / O controller 708 may also manage peripherals not integrated into the device M02. In some implementations, the I / O controller 708 may represent a physical connection or port to an external peripheral. In some implementations, the I / O controller 708 may utilize an operating system such as or another known operating system. In some implementations, the I / O controller 708 may be implemented as part of a processor, such as the processor 706. In some implementations, a user may interact with the device 700 via the I / O controller 708 or via hardware components controlled by the I / O controller 708.
[0142] In some implementations, the device 700 may include a single antenna 710. However, in some other implementations, the device 700 may have more than one antenna 710 (i.e., multiple antennas) , including multiple antenna panels or antenna arrays, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 706 may communicate bi-directionally, via the one or more antennas 710, wired, or wireless links as described herein. For example, the transceiver 706 may represent a wireless transceiver and may communicate bi- directionally with another wireless transceiver. The transceiver 706 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 710 for transmission, and to demodulate packets received from the one or more antennas 710. The transceiver 706 may include one or more transmit chains, one or more receive chains, or a combination thereof.
[0143] A transmit chain may be configured to generate and transmit signals (e.g., control information, data, packets) . The transmit chain may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM) , frequency modulation (FM) , or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM) . The transmit chain may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmit chain may also include one or more antennas 710 for transmitting the amplified signal into the air or wireless medium.
[0144] A receive chain may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receive chain may include one or more antennas 710 for receive the signal over the air or wireless medium. The receive chain may include at least one amplifier (e.g., a low-noise amplifier (LNA) ) configured to amplify the received signal. The receive chain may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal. The receive chain may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.
[0145] FIG. 8 illustrates an example of a device 800 that supports SIB1 transmission for network energy saving in accordance with aspects of the present disclosure. The device 800 may be an example of a network entity 102 as described herein. The device 800 may support wireless communication with one or more network entities 102, UEs 104, or any combination thereof. The device 800 may include components for bi-directional communications including components for transmitting and receiving communications, such as a processor 802, a memory 804, a transceiver 806, and, optionally, an I / O controller 808. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses) .
[0146] The processor 802, the memory 804, the transceiver 806, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. For example, the processor 802, the memory 804, the transceiver 806, or various combinations or components thereof may support a method for performing one or more of the operations described herein.
[0147] In some implementations, the processor 802, the memory 804, the transceiver 806, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry) . The hardware may include a processor, a digital signal processor (DSP) , an application-specific integrated circuit (ASIC) , a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure. In some implementations, the processor 802 and the memory 804 coupled with the processor 802 may be configured to perform one or more of the functions described herein (e.g., executing, by the processor 802, instructions stored in the memory 804) .
[0148] For example, the processor 802 may support wireless communication at the device 800 in accordance with examples as disclosed herein. The processor 802 may be configured to operable to support a means for transmitting, via the transceiver to a user equipment, synchronization signal and physical broadcast channel (PBCH) blocks (SSBs) , wherein whether a system information block 1 (SIB1) is broadcasted is indicated based on information elements of a master information block (MIB) in the SSBs; and a means for starting, for a user equipment, one of a physical random access channel (PRACH) procedure for system information block (SIB) requesting or a PRACH procedure for SIB1 requesting and cell accessing. The processor 802 may be configured to operable to support other means for other implementations of method 1200.
[0149] The processor 802 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof) . In some implementations, the processor 802 may be configured to operate a memory array using a memory controller. In some other implementations, a memory controller may be integrated into the processor 802. The processor 802 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 804) to cause the device 800 to perform various functions of the present disclosure.
[0150] The memory 804 may include random access memory (RAM) and read-only memory (ROM) . The memory 804 may store computer-readable, computer-executable code including instructions that, when executed by the processor 802 cause the device 800 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some implementations, the code may not be directly executable by the processor 802 but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some implementations, the memory 804 may include, among other things, a basic I / O system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.
[0151] The I / O controller 808 may manage input and output signals for the device 800. The I / O controller 808 may also manage peripherals not integrated into the device M02. In some implementations, the I / O controller 808 may represent a physical connection or port to an external peripheral. In some implementations, the I / O controller 808 may utilize an operating system such as or another known operating system. In some implementations, the I / O controller 808 may be implemented as part of a processor, such as the processor 806. In some implementations, a user may interact with the device 800 via the I / O controller 808 or via hardware components controlled by the I / O controller 808.
[0152] In some implementations, the device 800 may include a single antenna 810. However, in some other implementations, the device 800 may have more than one antenna 810 (i.e., multiple antennas) , including multiple antenna panels or antenna arrays, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 806 may communicate bi-directionally, via the one or more antennas 810, wired, or wireless links as described herein. For example, the transceiver 806 may represent a wireless transceiver and may communicate bi- directionally with another wireless transceiver. The transceiver 806 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 810 for transmission, and to demodulate packets received from the one or more antennas 810. The transceiver 806 may include one or more transmit chains, one or more receive chains, or a combination thereof.
[0153] A transmit chain may be configured to generate and transmit signals (e.g., control information, data, packets) . The transmit chain may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM) , frequency modulation (FM) , or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM) . The transmit chain may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmit chain may also include one or more antennas 810 for transmitting the amplified signal into the air or wireless medium.
[0154] A receive chain may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receive chain may include one or more antennas 810 for receive the signal over the air or wireless medium. The receive chain may include at least one amplifier (e.g., a low-noise amplifier (LNA) ) configured to amplify the received signal. The receive chain may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal. The receive chain may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.
[0155] FIG. 9 illustrates an example of a processor 900 that supports SIB1 transmission for network energy saving in accordance with aspects of the present disclosure. The processor 900 may be an example of a processor configured to perform various operations in accordance with examples as described herein. The processor 900 may include a controller 902 configured to perform various operations in accordance with examples as described herein. The processor 900 may optionally include at least one memory 904. Additionally, or alternatively, the processor 900 may optionally include one or more arithmetic-logic units (ALUs) 900. One or more of these components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses) .
[0156] The processor 900 may be a processor chipset and include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) in accordance with examples as described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to or included in the processor chipset (e.g., the processor 900) or other memory (e.g., random access memory (RAM) , read-only memory (ROM) , dynamic RAM (DRAM) , synchronous dynamic RAM (SDRAM) , static RAM (SRAM) , ferroelectric RAM (FeRAM) , magnetic RAM (MRAM) , resistive RAM (RRAM) , flash memory, phase change memory (PCM) , and others) .
[0157] The controller 902 may be configured to manage and coordinate various operations (e.g., signaling, receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) of the processor 900 to cause the processor 900 to support various operations in accordance with examples as described herein. For example, the controller 902 may operate as a control unit of the processor 900, generating control signals that manage the operation of various components of the processor 900. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.
[0158] The controller 902 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 904 and determine subsequent instruction (s) to be executed to cause the processor 900 to support various operations in accordance with examples as described herein. The controller 902 may be configured to track memory address of instructions associated with the memory 904. The controller 902 may be configured to decode instructions to determine the operation to be performed and the operands involved. For example, the controller 902 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 900 to cause the processor 900 to support various operations in accordance with examples as described herein. Additionally, or alternatively, the controller 902 may be configured to manage flow of data within the processor 900. The controller 902 may be configured to control transfer of data between registers, arithmetic logic units (ALUs) , and other functional units of the processor 900.
[0159] The memory 904 may include one or more caches (e.g., memory local to or included in the processor 900 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementation, the memory 904 may reside within or on a processor chipset (e.g., local to the processor 900) . In some other implementations, the memory 904 may reside external to the processor chipset (e.g., remote to the processor 900) .
[0160] The memory 904 may store computer-readable, computer-executable code including instructions that, when executed by the processor 900, cause the processor 900 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. The controller 902 and / or the processor 900 may be configured to execute computer-readable instructions stored in the memory 904 to cause the processor 900 to perform various functions (e.g., functions or tasks supporting transmit power prioritization) . For example, the processor 900 and / or the controller 902 may be coupled with or to the memory 904, the processor 900, the controller 902, and the memory 904 may be configured to perform various functions described herein. In some examples, the processor 900 may include multiple processors and the memory 904 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein.
[0161] The one or more ALUs 900 may be configured to support various operations in accordance with examples as described herein. In some implementation, the one or more ALUs 900 may reside within or on a processor chipset (e.g., the processor 900) . In some other implementations, the one or more ALUs 900 may reside external to the processor chipset (e.g., the processor 900) . One or more ALUs 900 may perform one or more computations such as addition, subtraction, multiplication, and division on data. For example, one or more ALUs 900 may receive input operands and an operation code, which determines an operation to be executed. One or more ALUs 900 be configured with a variety of logical and arithmetic circuits, including adders, subtractors, shifters, and logic gates, to process and manipulate the data according to the operation. Additionally, or alternatively, the one or more ALUs 900 may support logical operations such as AND, OR, exclusive-OR (XOR) , not-OR (NOR) , and not-AND (NAND) , enabling the one or more ALUs 900 to handle conditional operations, comparisons, and bitwise operations.
[0162] The processor 900 may support wireless communication in accordance with examples as disclosed herein. The processor 900 may be configured to or operable to support a means for receiving, from a base station, synchronization signal and physical broadcast channel (PBCH) blocks (SSBs) ; a means for determining whether a system information block 1 (SIB1) is broadcasted based on information elements of a master information block (MIB) in the SSBs; and a means for in the case that the SIB1 is not broadcasted, starting one of a physical random access channel (PRACH) procedure for system information block (SIB) requesting or a PRACH procedure for SIB1 requesting and cell accessing. The processor 900 may be configured to operable to support other means for other implementations of method 1100.
[0163] FIG. 10 illustrates an example of a processor 1000 that supports SIB1 transmission for network energy saving in accordance with aspects of the present disclosure. The processor 1000 may be an example of a processor configured to perform various operations in accordance with examples as described herein. The processor 1000 may include a controller 1002 configured to perform various operations in accordance with examples as described herein. The processor 1000 may optionally include at least one memory 1004. Additionally, or alternatively, the processor 1000 may optionally include one or more arithmetic-logic units (ALUs) 1000. One or more of these components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses) .
[0164] The processor 1000 may be a processor chipset and include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) in accordance with examples as described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to or included in the processor chipset (e.g., the processor 1000) or other memory (e.g., random access memory (RAM) , read-only memory (ROM) , dynamic RAM (DRAM) , synchronous dynamic RAM (SDRAM) , static RAM (SRAM) , ferroelectric RAM (FeRAM) , magnetic RAM (MRAM) , resistive RAM (RRAM) , flash memory, phase change memory (PCM) , and others) .
[0165] The controller 1002 may be configured to manage and coordinate various operations (e.g., signaling, receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) of the processor 1000 to cause the processor 1000 to support various operations in accordance with examples as described herein. For example, the controller 1002 may operate as a control unit of the processor 1000, generating control signals that manage the operation of various components of the processor 1000. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.
[0166] The controller 1002 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 1004 and determine subsequent instruction (s) to be executed to cause the processor 1000 to support various operations in accordance with examples as described herein. The controller 1002 may be configured to track memory address of instructions associated with the memory 1004. The controller 1002 may be configured to decode instructions to determine the operation to be performed and the operands involved. For example, the controller 1002 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 1000 to cause the processor 1000 to support various operations in accordance with examples as described herein. Additionally, or alternatively, the controller 1002 may be configured to manage flow of data within the processor 1000. The controller 1002 may be configured to control transfer of data between registers, arithmetic logic units (ALUs) , and other functional units of the processor 1000.
[0167] The memory 1004 may include one or more caches (e.g., memory local to or included in the processor 1000 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementation, the memory 1004 may reside within or on a processor chipset (e.g., local to the processor 1000) . In some other implementations, the memory 1004 may reside external to the processor chipset (e.g., remote to the processor 1000) .
[0168] The memory 1004 may store computer-readable, computer-executable code including instructions that, when executed by the processor 1000, cause the processor 1000 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. The controller 1002 and / or the processor 1000 may be configured to execute computer-readable instructions stored in the memory 1004 to cause the processor 1000 to perform various functions (e.g., functions or tasks supporting transmit power prioritization) . For example, the processor 1000 and / or the controller 1002 may be coupled with or to the memory 1004, the processor 1000, the controller 1002, and the memory 1004 may be configured to perform various functions described herein. In some examples, the processor 1000 may include multiple processors and the memory 1004 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein.
[0169] The one or more ALUs 1000 may be configured to support various operations in accordance with examples as described herein. In some implementation, the one or more ALUs 1000 may reside within or on a processor chipset (e.g., the processor 1000) . In some other implementations, the one or more ALUs 1000 may reside external to the processor chipset (e.g., the processor 1000) . One or more ALUs 1000 may perform one or more computations such as addition, subtraction, multiplication, and division on data. For example, one or more ALUs 1000 may receive input operands and an operation code, which determines an operation to be executed. One or more ALUs 1000 be configured with a variety of logical and arithmetic circuits, including adders, subtractors, shifters, and logic gates, to process and manipulate the data according to the operation. Additionally, or alternatively, the one or more ALUs 1000 may support logical operations such as AND, OR, exclusive-OR (XOR) , not-OR (NOR) , and not-AND (NAND) , enabling the one or more ALUs 1000 to handle conditional operations, comparisons, and bitwise operations.
[0170] The processor 1000 may support wireless communication in accordance with examples as disclosed herein. The processor 1002 may be configured to or operable to support a means for transmitting, to a user equipment, synchronization signal and physical broadcast channel (PBCH) blocks (SSBs) , wherein whether a system information block 1 (SIB1) is broadcasted is indicated based on information elements of a master information block (MIB) in the SSBs; and a means for starting, for a user equipment, one of a physical random access channel (PRACH) procedure for system information block (SIB) requesting or a PRACH procedure for SIB1 requesting and cell accessing. The processor 1000 may be configured to operable to support other means for other implementations of method 1200.
[0171] FIG. 11 illustrates a flowchart of a method 1100 that supports SIB1 transmission for network energy saving in accordance with aspects of the present disclosure. The operations of the method 1100 may be implemented by a device or its components as described herein. For example, the operations of the method 1100 may be performed by a network entity 102 as described herein. In some implementations, the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.
[0172] At 1105, the method may include receiving, from a base station, synchronization signal and physical broadcast channel (PBCH) blocks (SSBs) . The operations of 1105 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1105 may be performed by a device as described with reference to FIG. 1A.
[0173] At 1110, the method may include determining whether a system information block 1 (SIB1) is broadcasted based on information elements of a master information block (MIB) in the SSBs. The operations of 1110 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 110 may be performed by a device as described with reference to FIG. 1A.
[0174] At 1115, the method may include in the case that the SIB1 is not broadcasted, starting one of a physical random access channel (PRACH) procedure for system information block (SIB) requesting or a PRACH procedure for SIB1 requesting and cell accessing. The operations of 1115 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1115 may be performed by a device as described with reference to FIG. 1A.
[0175] In some embodiments, the information elements may comprise a first information element indicative of cell barring and a second information element indicative of a SSB subcarrier offset, wherein the SSB subcarrier offset is associated with whether the SIB1 is transmitted.
[0176] In some embodiments, the method may further include in the case that the first information element indicates that a cell is not barred and the second information element indicates that the SIB1 is transmitted, determining that the SIB1 is broadcasted by the cell; in the case that the first information element indicates that a cell is barred and the second information element indicates that the SIB1 is transmitted, determining that the SIB1 is not broadcasted by the cell and is on-demand triggered; and in the case that the second information element indicates that the SIB1 is not transmitted, determining that the SIB1 is not transmitted by the cell.
[0177] In some embodiments, the PRACH procedure for SIB1 requesting and cell accessing may comprise: Msg1 transmission, Msg2 reception, SIB1 reception, Msg3 transmission or Msg4 reception. In some embodiments, an initial Msg3 transmission may be scheduled by a first downlink control information (DCI) format. In some embodiments, the method may further include in the case that a contention resolution fails, restarting a PRACH procedure without SIB1 requesting.
[0178] In some embodiments, the PRACH procedure for SIB requesting may comprise: a PRACH procedure for SIB1 requesting or a PRACH procedure for other SIB requesting. In some embodiments, the PRACH procedure for SIB1 requesting may comprise: Msg1 transmission, Msg2 reception or SIB1 reception.
[0179] In some embodiments, the PRACH procedure for other SIB requesting may comprise: Msg1 transmission, Msg2 reception, SIB1 reception, and other SIB reception. In some embodiments, the Msg2 may comprise one of a downlink (DL) grant for scheduling the SIB1 or a preamble for acknowledging the requesting of SIB1 transmission.
[0180] In some embodiments, the method may further include in the case that the Msg2 comprises the DL grant, determining that the SIB1 is scheduled by the DL grant; and in the case that the Msg2 comprises the preamble for acknowledging the requesting of SIB1 transmission, determining that the SIB1 is transmitted periodically.
[0181] In some embodiments, the method may further include obtaining a set of preambles for the Msg1 transmission associated with one of SIB1 requesting and cell accessing, or SIB requesting; and performing the Msg1 transmission with a preamble among the set of preambles.
[0182] In some embodiments, the set of preambles may be obtained from a configuration either from the anchored cell or from a non-anchored cell.
[0183] In some embodiments, the DL grant may comprise at least one of following: allocation for time domain resource, allocation for frequency domain resource, a modulation and coding scheme (MCS) and a physical uplink control channel (PUCCH) indicator.
[0184] In some embodiments, the method may further include determining, based on the PUCCH indicator, a PUCCH resource for hybrid automatic repeat request acknowledgement (HARQ-ACK) for the SIB1 reception.
[0185] In some embodiments, the method may further include starting a timer for a SIB1 retransmission in the case that a SIB1 reception is failed; transmitting, to the base station, a second DCI format for scheduling the SIB1 retransmission; and monitoring the SIB1 from the base station before the timer expires.
[0186] In some embodiments, the method may further include determining that a PRACH procedure is failed in the case that the SIB1 reception is failed; and restarting the PRACH procedure.
[0187] FIG. 12 illustrates a flowchart of a method 1200 that supports SIB1 transmission for network energy saving in accordance with aspects of the present disclosure. The operations of the method 1200 may be implemented by a device or its components as described herein. For example, the operations of the method 1200 may be performed by a network entity 102 as described herein. In some implementations, the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.
[0188] At 1205, the method may include transmitting, to a user equipment, synchronization signal and physical broadcast channel (PBCH) blocks (SSBs) , wherein whether a system information block 1 (SIB1) is broadcasted is indicated based on information elements of a master information block (MIB) in the SSBs. The operations of 1205 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1205 may be performed by a device as described with reference to FIG. 1A.
[0189] At 1210, the method may include starting, for a user equipment, one of a physical random access channel (PRACH) procedure for system information block (SIB) requesting or a PRACH procedure for SIB1 requesting and cell accessing. The operations of 1210 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1210 may be performed by a device as described with reference to FIG. 1A.
[0190] In some embodiments, the information elements may comprise a first information element indicative of cell barring and a second information element indicative of a SSB subcarrier offset, wherein the SSB subcarrier offset is associated with whether the SIB1 is transmitted.
[0191] In some embodiments, in the case that the SIB1 is broadcasted by the cell, the first information element may indicate that a cell is not barred and the second information element indicates that the SIB1 is transmitted; in the case that the SIB1 is not broadcasted by the cell and is on-demand triggered, the first information element indicates that a cell is barred and the second information element may indicate that the SIB1 is transmitted; or in the case that the SIB1 is not transmitted by the cell, the second information element may indicate that the SIB1 is not transmitted.
[0192] In some embodiments, the PRACH procedure for SIB1 requesting and cell accessing may comprise one of the following: Msg1 reception, Msg2 transmission, SIB1 transmission, Msg3 reception or Msg4 transmission. In some embodiments, an initial Msg3 reception may be scheduled by a first downlink control information (DCI) format.
[0193] In some embodiments, the method may further include receiving, from the user equipment, a request for restarting a PRACH procedure without SIB1 requesting in the case that a contention resolution fails.
[0194] In some embodiments, the PRACH procedure for SIB requesting may comprise a PRACH procedure for SIB1 requesting or a PRACH procedure for other SIB requesting. In some embodiments, the PRACH procedure for SIB1 requesting may comprise Msg1 reception, Msg2 transmission and SIB1 transmission. In some embodiments, the PRACH procedure for other SIB requesting may comprise Msg1 reception, Msg2 transmission, SIB1 transmission, and other SIB transmission.
[0195] In some embodiments, the method may further include in the case that the Msg1 reception comprises a first preamble associated with the SIB1 requesting and the cell accessing, starting the PRACH procedure for SIB1 requesting and cell accessing; in the case that the Msg1 reception comprises a second preamble associated with the SIB1 requesting, starting a PRACH procedure for the SIB1 requesting; and in the case that the Msg1 reception comprises a third preamble associated with the other SIB requesting, starting a PRACH procedure for the other SIB requesting.
[0196] In some embodiments, the Msg2 may comprise one of a downlink (DL) grant for scheduling the SIB1 or a preamble for acknowledging the requesting of SIB1 transmission. In some embodiments, the DL grant may comprise at least one of following: an allocation for time domain resource, an allocation for frequency domain resource, a modulation and coding scheme (MCS) and a physical uplink control channel (PUCCH) indicator.
[0197] In some embodiments, the method may further include receiving, from the user equipment, a second DCI format for scheduling a SIB1 retransmission in the case that a SIB1 transmission is failed; and performing the SIB1 retransmission to the user equipment. In some embodiments, the method may further include receiving a request for restarting a PRACH procedure in the case that the SIB1 transmission is failed.
[0198] It should be noted that the methods described herein describes possible implementations, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible. Further, aspects from two or more of the methods may be combined.
[0199] The various illustrative blocks and components described in connection with the disclosure herein may be implemented or performed with a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
[0200] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.
[0201] Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer. By way of example, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM) , flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.
[0202] As used herein, including in the claims, an article “a” before an element is unrestricted and understood to refer to “at least one” of those elements or “one or more” of those elements. The terms “a, ” “at least one, ” “one or more, ” and “at least one of one or more” may be interchangeable. As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of” or “one or more of” or “one or both of” ) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C) . Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on”shall be construed in the same manner as the phrase “based at least in part on. Further, as used herein, including in the claims, a “set” may include one or more elements.
[0203] The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.
Claims
1.A user equipment comprising:a processor; anda transceiver coupled to the processor,wherein the processor is configured to:receive, via the transceiver from a base station, synchronization signal and physical broadcast channel (PBCH) blocks (SSBs) ;determine whether a system information block 1 (SIB1) is broadcasted based on information elements of a master information block (MIB) in the SSBs; andin the case that the SIB1 is not broadcasted, start one of a physical random access channel (PRACH) procedure for system information block (SIB) requesting or a PRACH procedure for SIB1 requesting and cell accessing.2.The user equipment of claim 1, wherein the information elements comprise a first information element indicative of cell barring and a second information element indicative of a SSB subcarrier offset, wherein the SSB subcarrier offset is associated with whether the SIB1 is transmitted.3.The user equipment of claim 2, wherein the processor is further configured to at least one of the following:in the case that the first information element indicates that a cell is not barred and the second information element indicates that the SIB1 is transmitted, determine that the SIB1 is broadcasted by the cell;in the case that the first information element indicates that a cell is barred and the second information element indicates that the SIB1 is transmitted, determine that the SIB1 is not broadcasted by the cell and is on-demand triggered; andin the case that the second information element indicates that the SIB1 is not transmitted, determine that the SIB1 is not transmitted by the cell.4.The user equipment of claim 1, wherein the PRACH procedure for SIB1 requesting and cell accessing comprises one of the following: Msg1 transmission, Msg2 reception, SIB1 reception, Msg3 transmission or Msg4 reception.5.The user equipment of claim 4, wherein an initial Msg3 transmission is scheduled by a first downlink control information (DCI) format.6.The user equipment of claim 4, wherein the processor is further configured to:in the case that a contention resolution fails, restart a PRACH procedure without SIB1 requesting.7.The user equipment of claim 1, wherein the PRACH procedure for SIB requesting comprises: a PRACH procedure for SIB1 requesting and a PRACH procedure for other SIB requesting.8.The user equipment of claim 7, wherein the PRACH procedure for SIB1 requesting comprises: Msg1 transmission, Msg2 reception and SIB1 reception.9.The user equipment of claim 7, wherein the PRACH procedure for other SIB requesting comprises: Msg1 transmission, Msg2 reception, SIB1 reception, and other SIB reception.10.The user equipment of claim 4, wherein the Msg2 comprises one of a downlink (DL) grant for scheduling the SIB1 or a preamble for acknowledging the requesting of SIB1 transmission.11.The user equipment of claim 10, wherein the processor is further configured to:in the case that the Msg2 comprises the DL grant, determine that the SIB1 is scheduled by the DL grant; andin the case that the Msg2 comprises the preamble for acknowledging the requesting of SIB1 transmission, determine that the SIB1 is transmitted periodically.12.The user equipment of claim 4, wherein the processor is further configured to:obtain a set of preambles for the Msg1 transmission associated with one of SIB1 requesting and cell accessing, or SIB requesting; andperform the Msg1 transmission with a preamble among the set of preambles.13.The user equipment of claim 12, wherein the set of preambles are obtained from a configuration either from the anchored cell or from a non-anchored cell.14.The user equipment of claim 10, wherein the DL grant comprises at least one of following: allocation for time domain resource, allocation for frequency domain resource, a modulation and coding scheme (MCS) and a physical uplink control channel (PUCCH) indicator.15.The user equipment of claim 14, wherein the processor is further configured to:determine, based on the PUCCH indicator, a PUCCH resource for hybrid automatic repeat request acknowledgement (HARQ-ACK) for the SIB1 reception.16.The user equipment of claim 1, wherein the processor is further configured to:start a timer for a SIB1 retransmission in the case that a SIB1 reception is failed;transmit, to the base station, a second DCI format for scheduling the SIB1 retransmission; andmonitor the SIB1 from the base station before the timer expires.17.The user equipment of any of claims 1-16, wherein the processor is further configured to:determine that a PRACH procedure is failed in the case that a SIB1 reception is failed; andrestart the PRACH procedure.18.A base station comprising:a processor; anda transceiver coupled to the processor,wherein the processor is configured to:transmit, via the transceiver, synchronization signal and physical broadcast channel (PBCH) blocks (SSBs) , wherein whether a system information block 1 (SIB1) is broadcasted is indicated based on information elements of a master information block (MIB) in the SSBs; andstart, for a user equipment, one of a physical random access channel (PRACH) procedure for system information block (SIB) requesting or a PRACH procedure for SIB1 requesting and cell accessing.19.A processor for wireless communication, comprising:at least one memory; anda controller coupled with the at least one memory and configured to cause the controller to:receive, from a base station, synchronization signal and physical broadcast channel (PBCH) blocks (SSBs) ;determine whether a system information block 1 (SIB1) is broadcasted based on information elements of a master information block (MIB) in the SSBs; andin the case that the SIB1 is not broadcasted, start one of a physical random access channel (PRACH) procedure for system information block (SIB) requesting or a PRACH procedure for SIB1 requesting and cell accessing.20.A method performed by a user equipment, comprising:receiving, from a base station, synchronization signal and physical broadcast channel (PBCH) blocks (SSBs) ;determining whether a system information block 1 (SIB1) is broadcasted based on information elements of a master information block (MIB) in the SSBs; andin the case that the SIB1 is not broadcasted, start one of a physical random access channel (PRACH) procedure for system information block (SIB) requesting or a PRACH procedure for SIB1 requesting and cell accessing.
Citation Information
Patent Citations
Method and apparatus for handling system information request in wireless communication system
US20210185758A1
System information block transmission method and communication apparatus
US20230318791A1
Wireless communication method and user equipment for handling random access operations
WO2021155853A1
Method and apparatus for using on-demand reference signal or system information block for network energy saving
WO2023151463A1
Information transmission method and communication apparatus
WO2023207589A1
Cited By
Determination method, communication device and storage medium
WO2025153118A3
Method executed by user equipment, and user equipment
WO2026138797A1
Communication method
WO2026153048A1
