WO2021191873A1 - Demande d'un élément d'information d'un bloc d'informations système - Google Patents

Demande d'un élément d'information d'un bloc d'informations système Download PDF

Info

Publication number
WO2021191873A1
WO2021191873A1 PCT/IB2021/052545 IB2021052545W WO2021191873A1 WO 2021191873 A1 WO2021191873 A1 WO 2021191873A1 IB 2021052545 W IB2021052545 W IB 2021052545W WO 2021191873 A1 WO2021191873 A1 WO 2021191873A1
Authority
WO
WIPO (PCT)
Prior art keywords
bwp
sib
system information
request message
ran
Prior art date
Application number
PCT/IB2021/052545
Other languages
English (en)
Inventor
Prateek Basu Mallick
Hyung-Nam Choi
Joachim Löhr
Ravi Kuchibhotla
Original Assignee
Lenovo (Singapore) Pte. Ltd.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Lenovo (Singapore) Pte. Ltd. filed Critical Lenovo (Singapore) Pte. Ltd.
Publication of WO2021191873A1 publication Critical patent/WO2021191873A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H04W48/14—Access restriction or access information delivery, e.g. discovery data delivery using user query or user detection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H04W48/12—Access restriction or access information delivery, e.g. discovery data delivery using downlink control channel

Definitions

  • the subject matter disclosed herein relates generally to wireless communications and more particularly relates to optimizing on-demand system information (“SI”) request and provisioning, e.g., of a UE in the RRC_CONNECTED state.
  • SI system information
  • SIBs System Information Blocks
  • Rel-15 3GPP Release 15
  • SIB1 is used to deliver information for Cell Selection, Cell Access, SI Scheduling.
  • SIB2 is used to deliver information for RACH, Access Barring, UL frequency Information, MBSFN Config.
  • SIB3 is used to deliver information for Intra Frequency Cell Reselection.
  • SIB4 is used to deliver information for Intra Frequency Neighbor Cell.
  • SIB5 is used to deliver information for Inter Frequency Neighbor Cell.
  • SIB6 is used to deliver information for UTRAN Neighbor Cell.
  • SIB7 is used to deliver information for GERAN Neighbor Cell.
  • SIB8 is used to deliver information for CDMA Neighbor Cell.
  • SIB9 is used to deliver information for Home eNB Name for femtocell application.
  • SIB 10 is used to deliver information for ETWS (i.e., Primary Channel).
  • SIB11 is used to deliver information for ETWS (i.e., Secondary Channel).
  • SIB 12 is used to deliver information for CMAS.
  • SIB 14 is used to deliver information for Extended Access Barring.
  • SIB 13, SIB 15, and SIB20 are used to deliver information for MBMS.
  • SIB 16 is used to deliver information for GPS.
  • SIB 17 is used to deliver information for WLAN.
  • SIB 18, SIB 19, and SIB21 are used to deliver information for Sidelink.
  • SIB24 is used to deliver information for NR Neighbor Cell.
  • One method of a User Equipment device includes activating a first bandwidth part (“BWP”), where the first BWP is not configured with a Common Search Space (“CSS”) used to receive a system information block (“SIB”).
  • the first method includes sending a system information request message for at least one information element (“IE”) of a first SIB and monitoring for a response during a window of time.
  • IE information element
  • Another method of a UE includes determining that a first active BWP is not configured with a CSS used to receive a SIB and sending a first indication of autonomous BWP switching to a radio access network (“RAN”).
  • the first active BWP comprises a first uplink (“UL”) BWP and a first downlink (“DL”) BWP.
  • the second method includes switching the first DL BWP to a second DL BWP for which a CSS is configured and acquiring a first SIB using the second DL BWP.
  • Figure 1 is a schematic block diagram illustrating one embodiment of a wireless communication system for on-demand system information provisioning
  • Figure 2 is a block diagram illustrating one embodiment of a 5G New Radio (“NR”) protocol stack
  • Figure 3 is a diagram illustrating one embodiment of a procedure for on-demand System Information provisioning
  • Figure 4 is a diagram illustrating one embodiment of bandwidth parts in an overall carrier bandwidth
  • Figure 5 is a diagram illustrating one embodiment of ANS.l code for an RRC DedicatedSIBRequest message
  • Figure 6 is a diagram illustrating one embodiment of a user equipment apparatus that may be used for on-demand system information provisioning
  • Figure 7 is a diagram illustrating one embodiment of a network equipment apparatus that may be used for on-demand system information provisioning
  • Figure 8 is a flowchart diagram illustrating one embodiment of a first method for on-demand system information provisioning.
  • Figure 9 is a flowchart diagram illustrating one embodiment of a second method for on-demand system information provisioning.
  • embodiments may be embodied as a system, apparatus, method, or program product. Accordingly, embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects.
  • the disclosed embodiments may be implemented as a hardware circuit comprising custom very-large-scale integration (“VLSI”) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components.
  • VLSI very-large-scale integration
  • the disclosed embodiments may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices, or the like.
  • the disclosed embodiments may include one or more physical or logical blocks of executable code which may, for instance, be organized as an object, procedure, or function.
  • embodiments may take the form of a program product embodied in one or more computer readable storage devices storing machine readable code, computer readable code, and/or program code, referred hereafter as code.
  • the storage devices may be tangible, non- transitory, and/or non-transmission.
  • the storage devices may not embody signals. In a certain embodiment, the storage devices only employ signals for accessing code.
  • the computer readable medium may be a computer readable storage medium.
  • the computer readable storage medium may be a storage device storing the code.
  • the storage device may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.
  • a storage device More specific examples (a non-exhaustive list) of the storage device would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random-access memory (“RAM”), a read-only memory (“ROM”), an erasable programmable read-only memory (“EPROM” or Flash memory), a portable compact disc read only memory (“CD-ROM”), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
  • a computer readable storage medium may be any tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device.
  • Code for carrying out operations for embodiments may be any number of lines and may be written in any combination of one or more programming languages including an object- oriented programming language such as Python, Ruby, Java, Smalltalk, C++, or the like, and conventional procedural programming languages, such as the "C" programming language, or the like, and/or machine languages such as assembly languages.
  • the code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server.
  • the remote computer may be connected to the user's computer through any type of network, including a local area network (“LAN”), wireless LAN (“WLAN”), or a wide area network (“WAN”), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider (“ISP”)).
  • LAN local area network
  • WLAN wireless LAN
  • WAN wide area network
  • ISP Internet Service Provider
  • a list with a conjunction of “and/or” includes any single item in the list or a combination of items in the list.
  • a list of A, B and/or C includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C or a combination of A, B and C.
  • a list using the terminology “one or more of’ includes any single item in the list or a combination of items in the list.
  • one or more of A, B and C includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C or a combination of A, B and C.
  • a list using the terminology “one of’ includes one and only one of any single item in the list.
  • “one of A, B and C” includes only A, only B or only C and excludes combinations of A, B and C.
  • a member selected from the group consisting of A, B, and C includes one and only one of A, B, or C, and excludes combinations of A, B, and C.”
  • “a member selected from the group consisting of A, B, and C and combinations thereof’ includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C or a combination of A, B and C.
  • the code may also be stored in a storage device that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the storage device produce an article of manufacture including instructions which implement the function/act specified in the flowchart diagrams and/or block diagrams.
  • the code may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the code which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart diagrams and/or block diagrams.
  • each block in the flowchart diagrams and/or block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions of the code for implementing the specified logical function(s).
  • SI System Information
  • NR New Radio
  • SI messages can be requested by UEs through RRCSystemlnfoRequest message if “si-BroadcastStatus” (in Sl-Schedulinglnfo in SIB1) is set to “notBroadcasting” for the respective SI message(s).
  • Random access procedure in UL is initiated using the Physical Random Access Channel (“PRACH”) preamble(s) and PRACH resource(s) in “si-RequestConfig” corresponding to the SI message(s) that the UE requires to operate within the cell.
  • PRACH Physical Random Access Channel
  • the UE uses Msg3 to request SI- messages for which “si-BroadcastStatus” is set to “notBroadcasting”. If a UE receives acknowledgement for the RRCSystemlnfoRequest message, it acquires the requested SI message(s) immediately.
  • the on-demand SI request procedure is applicable for UEs in RRC IDLE and RRC INACTIVE modes only.
  • RRC CONNECTED is supported for use by features in NR, e.g., NR positioning, NR Vehicle-to- Everything (“V2X”), NR Industrial Intemet-of-Things (“IoT”), etc.
  • NR positioning e.g., NR positioning, NR Vehicle-to- Everything (“V2X”), NR Industrial Intemet-of-Things (“IoT”), etc.
  • CSS common search space
  • BWP active bandwidth part
  • a UE in RRC CONNECTED mode checks whether the required on-demand SI is being broadcasted by a network node (e.g., gNB or another RAN node). The UE does this by reading SIB1 before transmitting any SI request and transmits a dedicated SI request only when the required on-demand SI is not being broadcasted.
  • a network node e.g., gNB or another RAN node
  • the network node processes the dedicated SI request and decide which of the requested SIB(s) to send.
  • the network node may send a SIBs either in dedicated messaging (e.g., RRCReconfiguration message) or by broadcast (e.g., in system information).
  • the UE 205 is not permitted to request on-demand delivery of certain SIBs, such as any of SIB 1 -SIB9.
  • the list of requested SIBs provided by the UE contains only SIBs that are allowed to be requested on-demand.
  • the UE may send an uplink dedicated control channel (“UL-DCCH”) message for SI request in RRC CONNECTED mode.
  • the SI Request is per SIB.
  • a single UL-DCCH message can request multiple SIBs.
  • the on-demand SI provisioning for UEs in RRC CONNECTED state is not RACH-based and supports multiple BWPs. If a CSS used to receive the system information is configured on the active BWP, then the UE tries to receive the on-demand SI through broadcast, e.g., after transmitting the SI request as in RRC_IDLE/INACTIVE state.
  • the network may provide all the SIBs, which the network thinks the UE may need. However, this would result in waste of radio resources when SIBs are provided to the UE which it does not need. Overall, it is ineffective for the network to “guess” which of all SIBs, not even supported or provided by the cell, the UE may actually request.
  • lack of CSS is a trigger for UE to change its BWP autonomously. The UE may autonomously move to another BWP (activate it) that has a CSS; however, this will lead to some inefficiency and latency until network finds out the BWP change because the network does not know about the UE-autonomous BWP change.
  • Figure 1 depicts a wireless communication system 100 for on-demand system information provisioning, according to embodiments of the disclosure.
  • the wireless communication system 100 includes at least one remote unit 105, a radio access network (“RAN”) 120, and a mobile core network 140.
  • the RAN 120 and the mobile core network 140 form a mobile communication network.
  • the RAN 120 may be composed of a base unit 121 with which the remote unit 105 communicates using wireless communication links 123.
  • remote units 105 Even though a specific number of remote units 105, base units 121, wireless communication links 123, RANs 120, and mobile core networks 140 are depicted in Figure 1, one of skill in the art will recognize that any number of remote units 105, base units 121, wireless communication links 123, RANs 120, and mobile core networks 140 may be included in the wireless communication system 100.
  • the RAN 120 is compliant with the 5G system specified in the 3GPP specifications.
  • the RAN 120 may be aNG-RAN, implementing NR RAT and/or LTE RAT.
  • the RAN 120 may include non-3GPP RAT (e.g., Wi-Fi® or Institute of Electrical and Electronics Engineers (“IEEE”) 802.11 -family compliant WLAN).
  • the RAN 120 is compliant with the LTE system specified in the 3GPP specifications.
  • the wireless communication system 100 may implement some other open or proprietary communication network, for example Worldwide Interoperability for Microwave Access (“WiMAX”) or IEEE 802.16-family standards, among other networks.
  • WiMAX Worldwide Interoperability for Microwave Access
  • IEEE 802.16-family standards among other networks. The present disclosure is not intended to be limited to the implementation of any particular wireless communication system architecture or protocol.
  • the remote units 105 may include computing devices, such as desktop computers, laptop computers, personal digital assistants (“PDAs”), tablet computers, smart phones, smart televisions (e.g., televisions connected to the Internet), smart appliances (e.g., appliances connected to the Internet), set-top boxes, game consoles, security systems (including security cameras), vehicle on-board computers, network devices (e.g., routers, switches, modems), or the like.
  • the remote units 105 include wearable devices, such as smart watches, fitness bands, optical head-mounted displays, or the like.
  • the remote units 105 may be referred to as the UEs, subscriber units, mobiles, mobile stations, users, terminals, mobile terminals, fixed terminals, subscriber stations, user terminals, wireless transmit/receive unit (”WTRU”), a device, or by other terminology used in the art.
  • the remote unit 105 includes a subscriber identity and/or identification module (“SIM”) and the mobile equipment (“ME”) providing mobile termination functions (e.g., radio transmission, handover, speech encoding and decoding, error detection and correction, signaling and access to the SIM).
  • SIM subscriber identity and/or identification module
  • ME mobile equipment
  • the remote unit 105 may include a terminal equipment (“TE”) and/or be embedded in an appliance or device (e.g., a computing device, as described above).
  • the remote units 105 may communicate directly with one or more of the base units 121 in the RAN 120 via uplink (“UL”) and downlink (“DL”) communication signals. Furthermore, the UL and DL communication signals may be carried over the wireless communication links 123.
  • the RAN 120 is an intermediate network that provides the remote units 105 with access to the mobile core network 140. As described in greater detail below, the RAN 120 may send a measurement and reporting configuration 111 to the remote unit 105, wherein the remote unit 105 sends a measurement report 113 to the RAN 120.
  • the remote units 105 communicate with an application server 151 via a network connection with the mobile core network 140.
  • an application 107 e.g., web browser, media client, telephone and/or Voice-over-Intemet-Protocol (“VoIP”) application
  • VoIP Voice-over-Intemet-Protocol
  • a remote unit 105 may trigger the remote unit 105 to establish a protocol data unit (“PDU”) session (or other data connection) with the mobile core network 140 via the RAN 120.
  • the mobile core network 140 then relays traffic between the remote unit 105 and the application server 151 in the packet data network 150 using the PDU session.
  • the PDU session represents a logical connection between the remote unit 105 and the User Plane Function (“UPF”) 141.
  • UPF User Plane Function
  • the remote unit 105 In order to establish the PDU session (or PDN connection), the remote unit 105 must be registered with the mobile core network 140 (also referred to as “attached to the mobile core network” in the context of a Fourth Generation (“4G”) system). Note that the remote unit 105 may establish one or more PDU sessions (or other data connections) with the mobile core network 140. As such, the remote unit 105 may have at least one PDU session for communicating with the packet data network 150. The remote unit 105 may establish additional PDU sessions for communicating with other data networks and/or other communication peers.
  • 4G Fourth Generation
  • PDU Session refers to a data connection that provides end-to-end (“E2E”) user plane (“UP”) connectivity between the remote unit 105 and a specific Data Network (“DN”) through the UPF 141.
  • E2E end-to-end
  • UP user plane
  • DN Data Network
  • a PDU Session supports one or more Quality of Service (“QoS”) Flows.
  • QoS Quality of Service
  • EPS Evolved Packet System
  • PDN Packet Data Network
  • the PDN connectivity procedure establishes an EPS Bearer, i.e., atunnel between the remote unit 105 and a Packet Gateway (“PGW”, not shown) in the mobile core network 140.
  • PGW Packet Gateway
  • QCI QoS Class Identifier
  • the base units 121 may be distributed over a geographic region.
  • a base unit 121 may also be referred to as an access terminal, an access point, a base, a base station, aNode-B (“NB”), an Evolved Node B (abbreviated as eNodeB or “eNB,” also known as Evolved Universal Terrestrial Radio Access Network (“E-UTRAN”) Node B), a 5G/NR Node B (“gNB”), a Home Node-B, a relay node, a RAN node, or by any other terminology used in the art.
  • NB Node-B
  • eNB Evolved Node B
  • gNB 5G/NR Node B
  • the base units 121 are generally part of a RAN, such as the RAN 120, that may include one or more controllers communicably coupled to one or more corresponding base units 121. These and other elements of radio access network are not illustrated but are well known generally by those having ordinary skill in the art.
  • the base units 121 connect to the mobile core network 140 via the RAN 120.
  • the base units 121 may serve a number of remote units 105 within a serving area, for example, a cell or a cell sector, via a wireless communication link 123.
  • the base units 121 may communicate directly with one or more of the remote units 105 via communication signals.
  • the base units 121 transmit DL communication signals to serve the remote units 105 in the time, frequency, and/or spatial domain.
  • the DL communication signals may be carried over the wireless communication links 123.
  • the wireless communication links 123 may be any suitable carrier in licensed or unlicensed radio spectrum.
  • the wireless communication links 123 facilitate communication between one or more of the remote units 105 and/or one or more of the base units 121. Note that during NR-U operation, the base unit 121 and the remote unit 105 communicate over unlicensed radio spectrum.
  • the mobile core network 140 is a 5GC or an Evolved Packet Core (“EPC”), which may be coupled to a packet data network 150, like the Internet and private data networks, among other data networks.
  • a remote unit 105 may have a subscription or other account with the mobile core network 140.
  • Each mobile core network 140 belongs to a single PLMN.
  • the present disclosure is not intended to be limited to the implementation of any particular wireless communication system architecture or protocol.
  • the mobile core network 140 includes several network functions (“NFs”). As depicted, the mobile core network 140 includes at least one UPF 141.
  • the mobile core network 140 also includes multiple control plane (“CP”) functions including, but not limited to, an Access and Mobility Management Function (“AMF”) 143 that serves the RAN 120, a Session Management Function (“SMF”) 145, a Policy Control Function (“PCF”) 147, and a Unified Data Management function (“UDM”).
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • PCF Policy Control Function
  • UDM Unified Data Management function
  • the UDM is co-located with a User Data Repository (“UDR”), depicted as combined entity “UDM/UDR” 149.
  • UDR User Data Repository
  • the mobile core network 140 may also include an Authentication Server Function (“AUSF”), a Network Repository Function (“NRF”) (used by the various NFs to discover and communicate with each other over Application Programming Interfaces (“APIs”)), or other NFs defined for the 5GC.
  • AUSF Authentication Server Function
  • NRF Network Repository Function
  • the mobile core network 140 may include an authentication, authorization, and accounting (“AAA”) server.
  • the mobile core network 140 supports different types of mobile data connections and different types of network slices, wherein each mobile data connection utilizes a specific network slice.
  • a “network slice” refers to a portion of the mobile core network 140 optimized for a certain traffic type or communication service.
  • a network instance may be identified by a single-network slice selection assistance information (“S-NSSAI”) while a set of network slices for which the remote unit 105 is authorized to use is identified by network slice selection assistance information (“NSSAI”).
  • S-NSSAI single-network slice selection assistance information
  • NSSAI network slice selection assistance information
  • “NSSAI” refers to a vector value including one or more S-NSSAI values.
  • the various network slices may include separate instances of network functions, such as the SMF 145 and UPF 141.
  • the different network slices may share some common network functions, such as the AMF 143. The different network slices are not shown in Figure 1 for ease of illustration, but their support is assumed.
  • the depicted network functions may be replaced with appropriate EPC entities, such as a Mobility Management Entity (“MME”), a Serving Gateway (“SGW”), a PGW, a Home Subscriber Server (“HSS”), and the like.
  • MME Mobility Management Entity
  • SGW Serving Gateway
  • PGW Packet Data Network
  • HSS Home Subscriber Server
  • the AMF 143 may be mapped to an MME
  • the SMF 145 may be mapped to a control plane portion of a PGW and/or to an MME
  • the UPF 141 may be mapped to an SGW and a user plane portion of the PGW
  • the UDM/UDR 149 may be mapped to an HSS, etc.
  • Figure 1 depicts components of a 5G RAN and a 5G core network
  • the described embodiments for on-demand system information provisioning apply to other types of communication networks and RATs, including IEEE 802.11 variants, Global System for Mobile Communications (“GSM”, i.e., a 2G digital cellular network), General Packet Radio Service (“GPRS”), Universal Mobile Telecommunications System (“UMTS”), UTE variants, CDMA 2000, Bluetooth, ZigBee, Sigfox, and the like.
  • GSM Global System for Mobile Communications
  • GPRS General Packet Radio Service
  • UMTS Universal Mobile Telecommunications System
  • CDMA 2000 Code Division Multiple Access 2000
  • Bluetooth ZigBee
  • ZigBee ZigBee
  • Sigfox and the like.
  • the term “RAN node” is used for the base station but it is replaceable by any other radio access node, e.g., gNB, eNB, Base Station (“BS”), Access Point (“AP”), etc. Further, the operations are described mainly in the context of 5G NR. However, the proposed solutions/methods are also equally applicable to other mobile communication systems supporting measurement reporting in non-public networks.
  • Figure 2 depicts a NR protocol stack 200, according to embodiments of the disclosure. While Figure 2 shows a UE 205, a RAN node 210 and an AMF 215 in a 5G core network (“5GC”), these are representative of a set of remote units 105 interacting with a base unit 121 and a mobile core network 140. As depicted, the protocol stack 200 comprises a User Plane protocol stack 220 and a Control Plane protocol stack 225.
  • 5GC 5G core network
  • the User Plane protocol stack 220 includes a physical (“PHY”) layer 230, a Medium Access Control (“MAC”) sublayer 235, the Radio Fink Control (“RFC”) sublayer 240, a Packet Data Convergence Protocol (“PDCP”) sublayer 245, and Service Data Adaptation Protocol (“SDAP”) layer 250.
  • the Control Plane protocol stack 225 includes a physical layer 230, a MAC sublayer 235, a RFC sublayer 240, and a PDCP sublayer 245.
  • the Control Plane protocol stack 225 also includes a Radio Resource Control (“RRC”) layer 255 and a Non-Access Stratum (“NAS”) layer 260.
  • RRC Radio Resource Control
  • NAS Non-Access Stratum
  • the AS layer (also referred to as “AS protocol stack”) for the User Plane protocol stack 220 consists of at least SDAP, PDCP, RFC and MAC sublayers, and the physical layer.
  • the AS layer for the Control Plane protocol stack 225 consists of at least RRC, PDCP, RFC and MAC sublayers, and the physical layer.
  • the Fayer-2 (“F2”) is split into the SDAP, PDCP, RFC and MAC sublayers.
  • the Fayer-3 (“F3”) includes the RRC sublayer 255 and the NAS layer 260 for the control plane and includes, e.g., an Internet Protocol (“IP”) layer or PDU Fayer (not depicted) for the user plane.
  • IP Internet Protocol
  • FI and F2 are referred to as “lower layers,” while F3 and above (e.g., transport layer, application layer) are referred to as “higher layers” or “upper layers.”
  • the physical layer 230 offers transport channels to the MAC sublayer 235.
  • the physical layer 230 may perform CCA/FBT procedure as described herein. In certain embodiments, the physical layer 230 may send a notification of UF FBT failure to a MAC entity at the MAC sublayer 235.
  • the MAC sublayer 235 offers logical channels to the RFC sublayer 240.
  • the RFC sublayer 240 offers RFC channels to the PDCP sublayer 245.
  • the PDCP sublayer 245 offers radio bearers to the SDAP sublayer 250 and/or RRC layer 255.
  • the SDAP sublayer 250 offers QoS flows to the core network (e.g., 5GC).
  • the RRC layer 255 provides for the addition, modification, and release of Carrier Aggregation and/or Dual Connectivity.
  • the RRC layer 255 also manages the establishment, configuration, maintenance, and release of Signaling Radio Bearers (“SRBs”) and Data Radio Bearers (“DRBs”).
  • SRBs Signaling Radio Bearers
  • DRBs Data Radio Bearers
  • the NAS layer 260 is between the UE 205 and the 5GC 215. NAS messages are passed transparently through the RAN.
  • the NAS layer 260 is used to manage the establishment of communication sessions and for maintaining continuous communications with the UE 205 as it moves between different cells of the RAN.
  • the AS layer is between the UE 205 and the RAN carries information over the wireless portion of the network.
  • FIG. 3 depicts a procedure 300 for on-demand SI request, according to embodiments of the disclosure.
  • the procedure 300 is implemented by a UE 205 and a RAN node 210.
  • the procedure 300 starts as the UE 205 switches to a bandwidth part (“BWP”) for which no Common Search Space (“CSS”) is configured (see block 305); therefore, the UE 205 is not able to receive System Information Block (“SIB”) broadcast by the RAN node 210.
  • BWP bandwidth part
  • SIB System Information Block
  • SIB System Information Block
  • FIG. 4 depicts an example 400 of bandwidth parts (“BWPs”) in a NR carrier.
  • each BWP is a set of (e.g., contiguous) physical resource blocks (“PRBs”) selected from the carrier bandwidth.
  • PRBs physical resource blocks
  • a UE is configured with one or more BWPs by the network.
  • the UE is configured with a first bandwidth part (“BWP1”), a second bandwidth part (“BWP2”), and a third bandwidth part (“BWP3”).
  • BWP1 and BWP2 are configured with CSS.
  • the UE switches to a BWP for which no CSS is configured.
  • the UE 205 may not have the latest SIB1 information. Consequently, the UE 205 may request for SIB(s) that may not be even provided by the cell at all (at least not at the time of requesting). Additionally, the UE 205 deletes any stored version of a SIB after 3 hours from the moment it was successfully confirmed as valid. It might so happen that all the SIBs need to be deleted when the UE 205 is on a DL active BWP without CSS and 3 hours expire since the respective valid version were last acquired. In this case as well, the UE 205 may request for some SIBs that are no more supported (i.e., provided) by the cell.
  • the UE 205 transmits a System Information Request message 310 to the RAN node 210, and may receive an acknowledgement message (“ACK”) in response.
  • the System Information Request message 310 requests on-demand delivery of a SIB or a portion thereof.
  • the System Information Request message is a RRC message, such as the DedicatedSIBRequest message.
  • the DedicatedSIBRequest message is used for on-demand request of certain information elements (“IEs”) of a particular SIB, such as Sl-Schedulinglnfo in SIB1.
  • IEs information elements
  • the DedicatedSIBRequest message is used to request all SIBs of interest to the UE 205 (i.e., required SIB(s)).
  • the RAN node 210 processes the request and the UE monitors for System Information (“SI”) messages, i.e., during a window oftime (see block 315).
  • SI System Information
  • the RAN node 210 delivers one or more SIBs 320 (or portions thereof) to the UE 205 in response to the System Information Request 310.
  • FIG. 5 depicts example Abstract Syntax Notation One (“ASN.1 ”) code of an RRC DedicatedSIBRequest message 500 for communicating system information, according to aspects of the disclosure.
  • the message 500 may be sent by the UE 205 in RRC Connected states to the RAN node 210 (e.g., gNB).
  • the RAN node 210 e.g., gNB
  • the UE 205 requests SIB 1 on-demand and specifically just the information element Sl-Schedulinglnfo.
  • the message 500 requests the Sl-Schedulinglnfo, e.g., by adding a Boolean .v i-Schedi 11 inglnfoRe quested indication 505 in the RRC DedicatedSIBRequest message 500, as shown in Figure 5.
  • a bitmap may be used for the purpose of requesting one or more specific IEs; each bit of the bitmap indicating a specific IE, e.g., from SIB1.
  • the RRC DedicatedSIBRequest message 500 to include a BITMAP field for requesting one or more specific IEs (i.e., the BTIMAP replacing the Boolean ‘si- SchedulinglnfoRequested’ indication 505).
  • the UE 205 sends the request and waits until it receives SIB1 (or just the Sl-Schedulinglnfo).
  • the UE 205 After having received the Sl-Schedulinglnfo the UE 205 decides if the needed SIB(s) is/are being provided by the cell. If so, it checks if the areaScope and valueTag (as defined in TS 38.331) received for the required SIB(s) are same as the ones stored for that corresponding SIB. If the corresponding SIB(s) is not stored or at least areaScope or valueTag is different from the values stored, then the UE 205 requests those SIB(s).
  • the UE 205 may be unable to request SIB1 (or even ⁇ 57- Schedulinglnfo) on-demand (e.g., due to network configuration disallowing on-demand requests for SIB1 or portions thereof) and thus sends the UL Dedicated SIB request message (DedicatedSIBRequest) requesting all the SIBs of interest (i.e., required SIB(s)).
  • the RAN node 210 sends the RRC Reconfiguration message including the requested SIBs that are being provided in the cell. Further, the RAN node 210 indicates clearly for the SIBs that are not provided dedicatedly to the UE 205 as: A) Not supported SIB, or B) SIB(s) to be provided later (e.g., in subsequent RRC messaging).
  • UE 205 For SIB(s) not supported, UE 205 does not request them again in this cell for the current RRC Connection lifetime or until the RAN node 210 explicitly indicates the corresponding SIB as being provided, e.g., using an updated Sl-Schedulinglnfo that can be provided in broadcast or dedicated manner in the same or different Bandwidth part (“BWP”).
  • BWP Bandwidth part
  • the UE 205 can send the valueTag and areaScope of the requested SIB(s) in the DedicatedSIBRequest message if the SIB(s) being requested are stored.
  • the RAN node 210 provides in the RRC Reconfiguration message only SIBs (it believes) has been updated based on the UE 205 provided valueTag and areaScope information, i.e., when at least one of these values are different from the ones currently in use.
  • the following Info is sent: A) Not supported SIB, or B) SIB(s) to be provided later (e.g., in subsequent RRC messaging), or C) information indicating for which SIB(s) the UE 205 already has the latest version.
  • the UE 205 is not to request such SIB(s) again in this cell for the current RRC Connection lifetime or until the RAN node 210 explicitly indicates the corresponding SIB as being provided, e.g., using an updated Sl-Schedulinglnfo that can be provided in broadcast or dedicated manner.
  • an RRC Transaction identifier is used for RRC DedicatedSIBRequest message.
  • UE 205 receives the same Transaction identifier in a response message like RRC Reconfiguration, it knows that RAN node 210 has received and processed the request, even if the received response (RRC Reconfiguration) is otherwise empty, i.e., it does not carry any SIB information.
  • a RAN node 210 provides only part of a SIB (i.e., not the entire SIB that is broadcasted) that is relevant to a particular UE 205 based on the specific capability and requirement of the UE 205.
  • UE 205 autonomously switches to a configured BWP for which a CSS is configured in order to acquire the latest up to date SIB1, i.e., si-BroadcastStatus.
  • SIB1 i.e., si-BroadcastStatus.
  • the UE “autonomously switching” the BWP refers to UE-initiated switching of at least the DL BWP.
  • the UE 205 only switches the DL BWP (i.e., in order to acquire SIB1 information)
  • the UE 205 When autonomously switching the BWP, the UE 205 is to minimize the interruption time on the current active BWP. Because BWP switching for receipt of SI may lead to some inefficiency as the time to acquire the required SIB(s) could take longer than just a couple of milliseconds, e.g., due to the si-Window Length that could be up to 1280 ms, the UE 205 may inform the RAN node 210 before initiating the autonomous DL BWP change and also once it tunes back to the original BWP.
  • the UE 205 makes a request for certain SIB(s) to the RAN node 210 (optionally also indicating the new DL BWP where the UE 205 intends to switch to) following which it makes a BWP switch to a second BWP autonomously.
  • the RAN node 210 could anticipate the absence of UE 205 in the currently activated BWP for a reasonable time proportional and multiple of the SI Window period over the second BWP and implicitly allow the UE 205 to change to another BWP with CSS.
  • the RAN node 210 may use a PDCCH order or make a specific DL signaling transmission (RRC or LI) asking the UE 205 to report back its presence in the original UL active BWP or in an UL BWP that is linked to the new DL BWP where the UE 205 may have switched itself to.
  • RRC DL signaling transmission
  • the UE 205 may choose to stay on the new switched DL BWP and may also change the UL BWP to the corresponding UL BWP linked with the new DL BWP, in this case UE 205 may perform a RACH (or just use UL RRC signaling) from the new UL BWP to inform the RAN node 210.
  • the UE 205 may inform the RAN node 210 about the DL/ UL BWP switch while making a request for certain SIB(s) to the RAN node 210.
  • the Sl-Schedulinglnfo in SIB1 or in dedicated RRC signaling to the UE 205 will also map one or more BWPs to one or more SIBs (or Si-messages), i.e., the RAN node 210 can tell the UE 205 that SIB-x is only being provided in DL BWP-y.
  • the other SIB(s) may not be affected and therefore will continue to be provided in any BWP having a CSS.
  • Figure 6 depicts a user equipment apparatus 600 that may be used for on-demand system information provisioning, according to embodiments of the disclosure.
  • the user equipment apparatus 600 is used to implement one or more of the solutions described above.
  • the user equipment apparatus 600 may be one embodiment of the remote unit 105 and/or the UE 205, described above.
  • the user equipment apparatus 600 may include a processor 605, a memory 610, an input device 615, an output device 620, and a transceiver 625.
  • the input device 615 and the output device 620 are combined into a single device, such as a touchscreen.
  • the user equipment apparatus 600 may not include any input device 615 and/or output device 620.
  • the user equipment apparatus 600 may include one or more of: the processor 605, the memory 610, and the transceiver 625, and may not include the input device 615 and/or the output device 620.
  • the transceiver 625 includes at least one transmitter 630 and at least one receiver 635.
  • the transceiver 625 communicates with one or more cells (or wireless coverage areas) supported by one or more base units 121.
  • the transceiver 625 is operable on unlicensed spectrum.
  • the transceiver 625 may include multiple UE panel supporting one or more beams.
  • the transceiver 625 may support at least one network interface 640 and/or application interface 645.
  • the application interface(s) 645 may support one or more APIs.
  • the network interface(s) 640 may support 3GPP reference points, such as Uu, Nl, PC5, etc. Other network interfaces 640 may be supported, as understood by one of ordinary skill in the art.
  • the processor 605 may include any known controller capable of executing computer-readable instructions and/or capable of performing logical operations.
  • the processor 605 may be a microcontroller, a microprocessor, a central processing unit (“CPU”), a graphics processing unit (“GPU”), an auxiliary processing unit, a field programmable gate array (“FPGA”), or similar programmable controller.
  • the processor 605 executes instructions stored in the memory 610 to perform the methods and routines described herein.
  • the processor 605 is communicatively coupled to the memory 610, the input device 615, the output device 620, and the transceiver 625.
  • the processor 605 may include an application processor (also known as “main processor”) which manages application- domain and operating system (“OS”) functions and a baseband processor (also known as “baseband radio processor”) which manages radio functions.
  • main processor also known as “main processor”
  • baseband processor also known as “baseband radio processor”
  • the processor 605 controls the user equipment apparatus 600 to implement the above described UE behaviors.
  • the processor 605 may activate a first bandwidth part (“BWP”), wherein the first BWP is not configured with a Common Search Space (“CSS”) used to receive a system information block (“SIB”).
  • the processor 605 sends a system information request message for at least one information element (“IE”) of a first SIB and monitors for a response during a window of time.
  • IE information element
  • the processor 605 requests and receives only a portion of the first SIB from the RAN (i.e., does not receive the entire SIB).
  • the request message comprises a Radio Resource Control (“RRC”) request message (i.e., RRC DedicatedSIBRequest message).
  • RRC Radio Resource Control
  • the system information request message comprises a Boolean indicator for requesting a scheduling information IE.
  • the system information request message comprises a bitmap with each bit in the bitmap indicating a specific information element from the first SIB.
  • the processor 605 receives system information scheduling information in response to the request message and sends a second system information request message for at least one SIB for which a valid copy is not stored at the apparatus 600 (i.e., not stored in memory 610).
  • the system information scheduling information comprises an areaScope value (i.e., a flag) and a valueTag value.
  • the processor 605 605 further determines that at least one stored SIB is invalid in response to the received areaScope and valueTag values differing from stored areaScope and valueTag values of the at least one stored SIB, wherein the second system information request message comprises a request for the at least one invalid SIB.
  • the processor 605 identifies a plurality of required SIBs, wherein the system information request message comprises a request for the plurality of required SIBs, and receives a set of required SIBs from the RAN. In certain embodiments, at least one of the plurality of required SIBs is missing from the received set of required SIBs. In such embodiments, the processor 605 receives an indication from the RAN that the at least one missing SIB is not supported or that the at least one missing SIB is to be provided at a later time. [0088] In various embodiments, the processor 605 determines that a first active BWP is not configured with a CSS used to receive a SIB.
  • the first active BWP comprises a first UL BWP and a first DL BWP.
  • the processor 605 sends a first indication of autonomous BWP switching to the RAN and switches the first DL BWP to a second DL BWP for which a CSS is configured.
  • the processor 605 acquires a first SIB using the second DL BWP.
  • the first indication of autonomous BWP switching to a radio access network comprises a system information request message for at least one IE of the first SIB .
  • the first indication identifies the second DL BWP.
  • the first indication further indicates an autonomous BWP switch from the first active BWP to a second configured BWP, the second configured BWP comprising the second DL BWP and a second UL BWP.
  • the processor 605 switches from the second DL BWP to the first DL BWP in response to acquiring the first SIB and sends a second indication to the RAN in response to returning to the first DL BWP.
  • the processor 605 receives a signaling order (i.e., PDCCH, RRC message, LI message) from the RAN using the second DL. In such embodiments, switching from the second DL BWP to the first DL BWP occurs in response to the signaling order.
  • a signaling order i.e., PDCCH, RRC message, LI message
  • the processor 605 receives a signaling order (i.e., PDCCH, RRC message, LI message) from the RAN using the second DL and switches from the first UL BWP to a second UL BWP occurs in response to the signaling order, the second UL BWP linked to the second DL BWP.
  • the processor 605 switches the first UL BWP to a second UL BWP and initiates a random access procedure in response to switching to the second UL BWP.
  • the memory 610 in one embodiment, is a computer readable storage medium.
  • the memory 610 includes volatile computer storage media.
  • the memory 610 may include a RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/or static RAM (“SRAM”).
  • the memory 610 includes non-volatile computer storage media.
  • the memory 610 may include a hard disk drive, a flash memory, or any other suitable non-volatile computer storage device.
  • the memory 610 includes both volatile and non-volatile computer storage media.
  • the memory 610 stores data related to on-demand system information provisioning.
  • the memory 610 may store various parameters, panel/beam configurations, resource assignments, policies, and the like as described above.
  • the memory 610 also stores program code and related data, such as an operating system or other controller algorithms operating on the apparatus 600.
  • the input device 615 may include any known computer input device including a touch panel, a button, a keyboard, a stylus, a microphone, or the like.
  • the input device 615 may be integrated with the output device 620, for example, as a touchscreen or similar touch-sensitive display.
  • the input device 615 includes a touchscreen such that text may be input using a virtual keyboard displayed on the touchscreen and/or by handwriting on the touchscreen.
  • the input device 615 includes two or more different devices, such as a keyboard and a touch panel .
  • the output device 620 in one embodiment, is designed to output visual, audible, and/or haptic signals.
  • the output device 620 includes an electronically controllable display or display device capable of outputting visual data to a user.
  • the output device 620 may include, but is not limited to, an LCD display, an LED display, an OLED display, a projector, or similar display device capable of outputting images, text, or the like to a user.
  • the output device 620 may include a wearable display separate from, but communicatively coupled to, the rest of the user equipment apparatus 600, such as a smart watch, smart glasses, a heads-up display, or the like.
  • the output device 620 may be a component of a smart phone, a personal digital assistant, a television, a table computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, or the like.
  • the output device 620 includes one or more speakers for producing sound.
  • the output device 620 may produce an audible alert or notification (e.g., a beep or chime).
  • the output device 620 includes one or more haptic devices for producing vibrations, motion, or other haptic feedback.
  • all or portions of the output device 620 may be integrated with the input device 615.
  • the input device 615 and output device 620 may form a touchscreen or similar touch-sensitive display.
  • the output device 620 may be located near the input device 615.
  • the transceiver 625 communicates with one or more network functions of a mobile communication network via one or more access networks.
  • the transceiver 625 operates under the control of the processor 605 to transmit messages, data, and other signals and also to receive messages, data, and other signals.
  • the processor 605 may selectively activate the transceiver 625 (or portions thereof) at particular times in order to send and receive messages.
  • the transceiver 625 includes at least transmitter 630 and at least one receiver 635.
  • One or more transmitters 630 may be used to provide UL communication signals to a base unit 121, such as the UL transmissions described herein.
  • one or more receivers 635 may be used to receive DL communication signals from the base unit 121, as described herein.
  • the user equipment apparatus 600 may have any suitable number of transmitters 630 and receivers 635.
  • the transmitter(s) 630 and the receiver(s) 635 may be any suitable type of transmitters and receivers.
  • the transceiver 625 includes a first transmitter/receiver pair used to communicate with a mobile communication network over licensed radio spectrum and a second transmitter/receiver pair used to communicate with a mobile communication network over unlicensed radio spectrum.
  • the first transmitter/receiver pair used to communicate with a mobile communication network over licensed radio spectrum and the second transmitter/receiver pair used to communicate with a mobile communication network over unlicensed radio spectrum may be combined into a single transceiver unit, for example a single chip performing functions for use with both licensed and unlicensed radio spectrum.
  • the first transmitter/receiver pair and the second transmitter/receiver pair may share one or more hardware components.
  • certain transceivers 625, transmitters 630, and receivers 635 may be implemented as physically separate components that access a shared hardware resource and/or software resource, such as for example, the network interface 640.
  • one or more transmitters 630 and/or one or more receivers 635 may be implemented and/or integrated into a single hardware component, such as a multi transceiver chip, a system-on-a-chip, an application-specific integrated circuit (“ASIC”), or other type of hardware component.
  • ASIC application-specific integrated circuit
  • one or more transmitters 630 and/or one or more receivers 635 may be implemented and/or integrated into a multi-chip module.
  • other components such as the network interface 640 or other hardware components/circuits may be integrated with any number of transmitters 630 and/or receivers 635 into a single chip.
  • the transmitters 630 and receivers 635 may be logically configured as a transceiver 625 that uses one more common control signals or as modular transmitters 630 and receivers 635 implemented in the same hardware chip or in a multi -chip module.
  • FIG. 7 depicts a network equipment apparatus 700 that may be used for on- demand system information provisioning, according to embodiments of the disclosure.
  • network equipment apparatus 700 may be one implementation of a RAN node, such as the base unit 121, the RAN node 210, or gNB, described above.
  • the base network equipment apparatus 700 may include a processor 705, a memory 710, an input device 715, an output device 720, and a transceiver 725.
  • the input device 715 and the output device 720 are combined into a single device, such as a touchscreen.
  • the network equipment apparatus 700 may not include any input device 715 and/or output device 720.
  • the network equipment apparatus 700 may include one or more of: the processor 705, the memory 710, and the transceiver 725, and may not include the input device 715 and/or the output device 720.
  • the transceiver 725 includes at least one transmitter 730 and at least one receiver 735.
  • the transceiver 725 communicates with one or more remote units 105.
  • the transceiver 725 may support at least one network interface 740 and/or application interface 745.
  • the application interface(s) 745 may support one or more APIs.
  • the network interface(s) 740 may support 3GPP reference points, such as Uu, Nl, N2 and N3. Other network interfaces 740 may be supported, as understood by one of ordinary skill in the art.
  • the processor 705, in one embodiment, may include any known controller capable of executing computer-readable instructions and/or capable of performing logical operations.
  • the processor 705 may be a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or similar programmable controller.
  • the processor 705 executes instructions stored in the memory 710 to perform the methods and routines described herein.
  • the processor 705 is communicatively coupled to the memory 710, the input device 715, the output device 720, and the transceiver 725.
  • the processor 705 may include an application processor (also known as “main processor”) which manages application-domain and operating system (“OS”) functions and a baseband processor (also known as “baseband radio processor”) which manages radio functions.
  • an application processor also known as “main processor” which manages application-domain and operating system (“OS”) functions
  • a baseband processor also known as “baseband radio processor” which manages radio functions.
  • the processor 705 controls the network apparatus 700 to implement the above described RAN behaviors.
  • the transceiver 725 may receive a SI request message for at least one IE of a first SIB.
  • the processor 705 may control the transceiver 725 to send the requested IE to the UE.
  • only the portion of the first SIB containing the requested IE(s) is sent to the UE (i.e., the entire first SIB is not sent).
  • the processor may receive - via the transceiver 725 - an indication of autonomous (i.e., UE-initiated) BWP switching from a UE.
  • the switching indication includes a SI request message for at least one IE of a first SIB.
  • the processor 705 also controls the transceiver 725 to send the requested IE to the UE.
  • the requested IE is sent via resources in a second DL BWP to which the UE has switched.
  • the memory 710 in one embodiment, is a computer readable storage medium.
  • the memory 710 includes volatile computer storage media.
  • the memory 710 may include a RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/or static RAM (“SRAM”).
  • the memory 710 includes non-volatile computer storage media.
  • the memory 710 may include a hard disk drive, a flash memory, or any other suitable non-volatile computer storage device.
  • the memory 710 includes both volatile and non-volatile computer storage media.
  • the memory 710 stores data related to on-demand system information provisioning.
  • the memory 710 may store parameters, configurations, resource assignments, policies, and the like, as described above.
  • the memory 710 also stores program code and related data, such as an operating system or other controller algorithms operating on the apparatus 700.
  • the input device 715 may include any known computer input device including a touch panel, a button, a keyboard, a stylus, a microphone, or the like.
  • the input device 715 may be integrated with the output device 720, for example, as a touchscreen or similar touch-sensitive display.
  • the input device 715 includes a touchscreen such that text may be input using a virtual keyboard displayed on the touchscreen and/or by handwriting on the touchscreen.
  • the input device 715 includes two or more different devices, such as a keyboard and a touch panel .
  • the output device 720 in one embodiment, is designed to output visual, audible, and/or haptic signals.
  • the output device 720 includes an electronically controllable display or display device capable of outputting visual data to a user.
  • the output device 720 may include, but is not limited to, an LCD display, an LED display, an OLED display, a projector, or similar display device capable of outputting images, text, or the like to a user.
  • the output device 720 may include a wearable display separate from, but communicatively coupled to, the rest of the network equipment apparatus 700, such as a smart watch, smart glasses, a heads-up display, or the like.
  • the output device 720 may be a component of a smart phone, a personal digital assistant, a television, a table computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, or the like.
  • the output device 720 includes one or more speakers for producing sound.
  • the output device 720 may produce an audible alert or notification (e.g., a beep or chime).
  • the output device 720 includes one or more haptic devices for producing vibrations, motion, or other haptic feedback.
  • all or portions of the output device 720 may be integrated with the input device 715.
  • the input device 715 and output device 720 may form a touchscreen or similar touch-sensitive display.
  • the output device 720 may be located near the input device 715.
  • the transceiver 725 includes at least transmitter 730 and at least one receiver 735.
  • One or more transmitters 730 may be used to communicate with the UE, as described herein.
  • one or more receivers 735 may be used to communicate with network functions in the PLMN and/or RAN, as described herein.
  • the network equipment apparatus 700 may have any suitable number of transmitters 730 and receivers 735.
  • the transmitter(s) 730 and the receiver(s) 735 may be any suitable type of transmitters and receivers.
  • Figure 8 depicts one embodiment of a method 800 for on-demand system information provisioning, according to embodiments of the disclosure.
  • the method 800 is performed by a user equipment device in a mobile communication network, such as the remote unit 105, the UE 205, and/or the user equipment apparatus 600, described above.
  • the method 800 is performed by a processor, such as a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.
  • the method 800 begins and activates 805 a first BWP, where the first BWP is not configured with a CSS used to receive a SIB.
  • the method 800 includes sending 810 a system information request message for at least one IE of a first SIB.
  • the method 800 includes monitoring
  • the method 800 ends.
  • Figure 9 depicts one embodiment of a method 900 for on-demand system information provisioning, according to embodiments of the disclosure.
  • the method 900 is performed by a user equipment device in a mobile communication network, such as the remote unit 105, the UE 205, and/or the user equipment apparatus 600, described above.
  • the method 900 is performed by a processor, such as a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.
  • the method 900 begins and determines 905 that a first active BWP is not configured with a CSS used to receive a SIB.
  • the method 900 includes sending 910 a first indication of autonomous BWP switching to a RAN.
  • the first active BWP comprises a first UL BWP and a first DL BWP.
  • the method 900 includes switching 915 the first DL BWP to a second DL BWP for which a CSS is configured.
  • the method 900 includes acquiring 920 a first SIB using the second DL BWP.
  • the method 900 ends.
  • Disclosed herein is a first apparatus for on-demand system information provisioning, according to embodiments of the disclosure.
  • the first apparatus may be implemented by a user equipment device in a mobile communication network, such as the remote unit 105, the UE 205, and/or the user equipment apparatus 600, described above.
  • the first apparatus includes a processor and a transceiver that communicates with a Radio Access Network (“RAN”).
  • the processor activates a first bandwidth part (“BWP”), wherein the first BWP is not configured with a Common Search Space (“CSS”) used to receive a system information block (“SIB”).
  • the processor sends a system information request message for at least one information element (“IE”) of a system information block and monitors for a response during a window of time.
  • IE information element
  • the UE requests and receives only a portion of the SIB from the RAN (i.e., does not receive the entire SIB).
  • the request message comprises a Radio Resource Control (“RRC”) request message (i.e., RRC DedicatedSIBRequest message).
  • RRC Radio Resource Control
  • the system information request message comprises a Boolean indicator for requesting a scheduling information IE.
  • the system information request message comprises a bitmap with each bit in the bitmap indicating a specific information element from the SIB.
  • the processor receives system information scheduling information in response to the request message and sends a second system information request message for at least one SIB for which a valid copy is not stored at the UE.
  • the system information scheduling information comprises an areaScope value (i.e., a flag) and a valueTag value.
  • the processor further determines that at least one stored SIB is invalid in response to the received areaScope and valueTag values differing from stored areaScope and valueTag values of the at least one stored SIB, wherein the second system information request message comprises a request for the at least one invalid SIB.
  • the processor identifies a plurality of required SIBs, wherein the system information request message comprises a request for the plurality of required SIBs, and receives a set of required SIBs from the RAN.
  • the processor receives an indication from the RAN that the at least one missing SIB is not supported or that the at least one missing SIB is to be provided at a later time.
  • the first method may be performed by a user equipment device in a mobile communication network, such as the remote unit 105, the UE 205, and/or the user equipment apparatus 600.
  • the first method includes activating a first bandwidth part (“BWP”), where the first BWP is not configured with a Common Search Space (“CSS”) used to receive a system information block (“SIB”).
  • BWP bandwidth part
  • SCS Common Search Space
  • the first method includes sending a system information request message for at least one information element (“IE”) of a system information block and monitoring for a response during a window of time.
  • IE information element
  • the UE requests and receives only a portion of the SIB from the RAN (i.e., does not receive the entire SIB).
  • the request message comprises a Radio Resource Control (“RRC”) request message (i.e., a RRC DedicatedSIBRequest message).
  • RRC Radio Resource Control
  • the system information request message comprises a Boolean indicator for requesting a scheduling information IE.
  • the system information request message comprises a bitmap with each bit in the bitmap indicating a specific information element from the SIB.
  • the first method includes receiving system information scheduling information in response to the request message and sending a second system information request message for at least one SIB for which a valid copy is not stored at the UE.
  • the system information scheduling information comprises an areaScope (i.e., flag) value and a valueTag value.
  • the first method includes determining that at least one stored SIB is invalid in response to the received areaScope and valueTag values differing from stored areaScope and valueTag values of the at least one stored SIB, wherein the second system information request message comprises a request for the at least one invalid SIB.
  • the first method includes identifying a plurality of required SIBs, wherein the system information request message comprises a request for the plurality of required SIBs, and receiving a set of required SIBs from the RAN.
  • the first method includes receiving an indication from the RAN that the at least one missing SIB is not supported or that the at least one missing SIB is to be provided at a later time.
  • the second apparatus may be implemented by a user equipment device in a mobile communication network, such as the remote unit 105, the UE 205, and/or the user equipment apparatus 600, described above.
  • the second apparatus includes a processor and a transceiver that communicates with a Radio Access Network (“RAN”).
  • the processor determines that a first active bandwidth part (“BWP”) is not configured with a Common Search Space (“CSS”) used to receive a system information block (“SIB”).
  • the first active BWP comprises a first uplink (“UL”) BWP and a first downlink (“DL”) BWP.
  • the processor sends a first indication of autonomous BWP switching to the RAN and switches the first DL BWP to a second DL BWP for which a CSS is configured.
  • the processor acquires a first SIB using the second DL BWP.
  • the first indication of autonomous BWP switching to a radio access network comprises a system information request message for at least one information element (“IE”) of a SIB.
  • the first indication identifies the second DL BWP.
  • the first indication further indicates an autonomous BWP switch from the first active BWP to a second configured BWP, the second configured BWP comprising the second DL BWP and a second UL BWP.
  • the processor switches from the second DL BWP to the first DL BWP in response to acquiring the first SIB and sends a second indication to the RAN in response to returning to the first DL BWP.
  • the processor receives a signaling order (i.e., PDCCH, RRC message, LI message) from the RAN using the second DL. In such embodiments, switching from the second DL BWP to the first DL BWP occurs in response to the signaling order.
  • a signaling order i.e., PDCCH, RRC message, LI message
  • the processor receives a signaling order (i.e., PDCCH, RRC message, LI message) from the RAN using the second DL and switches from the first UL BWP to a second UL BWP occurs in response to the signaling order, the second UL BWP linked to the second DL BWP.
  • the processor switches the first UL BWP to a second UL BWP and initiates a random access procedure in response to switching to the second UL BWP.
  • the second method may be performed by a user equipment device in a mobile communication network, such as the remote unit 105, the UE 205, and/or the user equipment apparatus 600.
  • the second method includes determining that a first active BWP is not configured with a CSS used to receive a SIB and sending a first indication of autonomous BWP switching to a RAN.
  • the first active BWP comprises a first UL BWP and a first DL BWP.
  • the second method includes switching the first DL BWP to a second DL BWP for which a CSS is configured and acquiring a first SIB using the second DL BWP.
  • the first indication of autonomous BWP switching to a radio access network comprises a system information request message for at least one IE of a SIB. In some embodiments, the first indication identifies the second DL BWP. In certain embodiments, the first indication further indicates an autonomous BWP switch from the first active BWP to a second configured BWP, the second configured BWP comprising the second DL BWP and a second UL BWP.
  • the second method includes switching from the second DL BWP to the first DL BWP in response to acquiring the first SIB and sending a second indication to the RAN in response to returning to the first DL BWP.
  • the second method further includes receiving a signaling order (i.e., PDCCH, RRC message, LI message) from the RAN using the second DL.
  • switching from the second DL BWP to the first DL BWP occurs in response to the signaling order.
  • the second method includes receiving a signaling order (i.e., PDCCH, RRC message, LI message) from the RAN using the second DL and switching from the first UL BWP to a second UL BWP occurs in response to the signaling order, the second UL BWP linked to the second DL BWP.
  • the second method includes switching the first UL BWP to a second UL BWP and initiating a random access procedure in response to switching to the second UL BWP.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Sont divulgués des appareils, des procédés et des systèmes permettant de transmettre des informations système à la demande. Un appareil (600) comprend un processeur (605) et un émetteur-récepteur (625) qui communique avec un réseau d'accès radio (RAN). Le processeur (605) active (805) une première partie de bande passante (BWP), la première BWP n'étant pas configurée avec un espace de recherche commun (CSS) utilisé pour recevoir un bloc d'informations système (SIB). Le processeur (605) envoie (810) un message de demande d'informations système pour au moins un élément d'information (IE) d'un bloc d'informations système et surveille (815) une réponse pendant une fenêtre de temps.
PCT/IB2021/052545 2020-03-26 2021-03-26 Demande d'un élément d'information d'un bloc d'informations système WO2021191873A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202063000365P 2020-03-26 2020-03-26
US63/000,365 2020-03-26

Publications (1)

Publication Number Publication Date
WO2021191873A1 true WO2021191873A1 (fr) 2021-09-30

Family

ID=75581541

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2021/052545 WO2021191873A1 (fr) 2020-03-26 2021-03-26 Demande d'un élément d'information d'un bloc d'informations système

Country Status (1)

Country Link
WO (1) WO2021191873A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023124823A1 (fr) * 2021-12-30 2023-07-06 华为技术有限公司 Procédé et appareil de communication
WO2024034991A1 (fr) * 2022-08-10 2024-02-15 엘지전자 주식회사 Procédé et dispositif d'émission/réception de signal dans un système de communication sans fil

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "Feature summary for on-demand SIB in CONNECTED", vol. RAN WG2, no. Electronic Meeting; 20200224 - 20200306, 20 February 2020 (2020-02-20), XP051849998, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG2_RL2/TSGR2_109_e/Docs/R2-2001670.zip R2-2001670- Feature summary for on-demand SIB in CONNECTED.docx> [retrieved on 20200220] *
ERICSSON: "Summary of [108#61][R16] On-demand SI procedure in RRC_CONNECTED", vol. RAN WG2, no. Electronic Meeting; 20200224 - 20200306, 13 February 2020 (2020-02-13), XP051848659, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG2_RL2/TSGR2_109_e/Docs/R2-2000875.zip R2-2000875- Summary of [108#61][R16] On-demand SI procedure in RRC_CONNECTED_summary.docx> [retrieved on 20200213] *
LENOVO ET AL: "Discussion on open issues of on-demand SI procedure in connected", vol. RAN WG2, no. Elbonia; 20200224 - 20200306, 13 February 2020 (2020-02-13), XP051848751, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG2_RL2/TSGR2_109_e/Docs/R2-2001154.zip R2-2001154_NR On-demand SIB in connected.doc> [retrieved on 20200213] *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023124823A1 (fr) * 2021-12-30 2023-07-06 华为技术有限公司 Procédé et appareil de communication
WO2024034991A1 (fr) * 2022-08-10 2024-02-15 엘지전자 주식회사 Procédé et dispositif d'émission/réception de signal dans un système de communication sans fil

Similar Documents

Publication Publication Date Title
JP6949205B2 (ja) 無線通信システムにおけるｖ２ｘ通信を行う方法、及びこのための装置
US20230209453A1 (en) Selection assistance information for a network slice
US20230098840A1 (en) Measurement configuration for non-public radio cell
US20230156584A1 (en) Target network slice information for target network slices
EP3831160A1 (fr) Gestion de défaillance de reprise après resélection de cellule
WO2021191873A1 (fr) Demande d&#39;un élément d&#39;information d&#39;un bloc d&#39;informations système
KR20220038103A (ko) 핸드오버 방법 및 장치
WO2023002454A1 (fr) Configuration de mobilité basée sur un groupe
EP4190057A1 (fr) Gestion de radiomessagerie
US20240064817A1 (en) Slice-specific random access configuration
US20230319780A1 (en) Receiving collected data from a group of devices
US20230300725A1 (en) Acquiring on-demand system information
US20230422341A1 (en) Configuring discontinuous reception for pc5 interface
US20240147574A1 (en) User equipment power saving for v2x communications
WO2023131907A1 (fr) Resélection de cellule sur la base d&#39;un découpage en tranches de réseau tenant compte de la mobilité
WO2023170611A1 (fr) Signalisation de mappage de tranche à groupe de tranches à un dispositif d&#39;équipement utilisateur
WO2023126909A1 (fr) Prise en charge d&#39;appel vocal dans des systèmes de communication sans fil
WO2023139558A1 (fr) Détermination de temporisateurs de connexion de liaison latérale pour établir une communication via un relais de liaison latérale
WO2023161907A1 (fr) Détermination de prise en charge de tranche d&#39;une cellule voisine
WO2022208474A1 (fr) Maintien d&#39;un terminal dans un état connecté tandis que le terminal est à l&#39;écart d&#39;un réseau de communication
WO2022009177A1 (fr) Gestion de radiomessagerie pour de multiples modules d&#39;identités d&#39;abonnés universels
WO2022009179A1 (fr) Gestion de radiomessagerie pour de multiples modules d&#39;identité d&#39;abonné universels
WO2023208392A1 (fr) Commutation de trajet entre trajets d&#39;accès n0n-3gpp
CA3227594A1 (fr) Informations de tranche pour cellules de desserte et voisines
CN117796043A (zh) 向受制于准入控制的网络切片的注册

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21719967

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21719967

Country of ref document: EP

Kind code of ref document: A1