System information download

Abstract

A user equipment (UE) sends a request to a network node for system information associated with a system information service of a wireless network. The UE receives the system information from the system information service of the wireless network via the network node. The network node obtains the request for the system information of the UE and provides the request for the system information to the system information service of the wireless network. The network node receives the system information from the system information service in response to the request and provides the system information from the system information service to the UE.

Description

Background Technology

[0001] This disclosure relates in general to communication systems, and more specifically to wireless communication including the transmission and reception of system information.

[0002] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems.

[0003] These multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different wireless devices to communicate at the city, national, regional, and even global levels. An example telecommunications standard is 5G New Radio (NR). 5G NR is part of the Continuous Evolution of Mobile Broadband (CWB) program issued by the 3rd Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT),) and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable low-latency communications (URLLC). Some aspects of 5G NR are based on the 4G Long Term Evolution (LTE) standard. Further improvements to 5G NR technology are needed. Furthermore, these improvements can also be applied to other multiple access technologies and telecommunications standards that adopt these technologies. Summary of the Invention

[0004] The following is a simplified summary of one or more aspects to provide a basic understanding of these aspects. This summary is not a comprehensive overview of all conceived aspects. It neither identifies key or essential elements of all aspects nor describes the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed descriptions that follow.

[0005] In some aspects, the technology described herein relates to an apparatus for wireless communication at a user equipment (UE), the apparatus comprising: one or more memories; and one or more processors coupled to the one or more memories and configured to cause the UE to: send a request to a network node for system information associated with a system information service of the wireless network; and receive the system information from the system information service of the wireless network via the network node.

[0006] In some respects, the techniques described herein relate to a method for wireless communication at a UE, the method comprising: sending a request to a network node for system information associated with a system information service of a wireless network; and receiving the system information from the system information service of the wireless network via the network node.

[0007] In some aspects, the technology described herein relates to an apparatus for wireless communication at a UE, the apparatus comprising: components for sending a request to a network node for system information associated with a system information service of a wireless network; and components for receiving the system information from the system information service of the wireless network via the network node.

[0008] In one aspect of this disclosure, a computer-readable medium is provided. The computer-readable medium stores computer-executable code at a UE, which, when executed by one or more processors, causes the UE to: send a request to a network node for system information associated with a system information service of a wireless network; and receive the system information from the system information service of the wireless network via the network node.

[0009] In some aspects, the technology described herein relates to an apparatus for wireless communication at a network node, the apparatus comprising: one or more memories; and one or more processors coupled to the one or more memories and configured to cause the network node to: obtain a request for system information from a UE; provide the request for system information to a system information service of a wireless network; receive system information from the system information service in response to the request; and provide the system information from the system information service to the UE.

[0010] In some aspects, the technology described herein relates to a method for wireless communication at a network node, the method comprising: obtaining a request for system information from a UE; providing the request for the system information to a system information service of a wireless network; receiving the system information from the system information service in response to providing the request; and providing the system information from the system information service to the UE.

[0011] In some aspects, the technology described herein relates to an apparatus for wireless communication at a network node, the apparatus comprising: components for obtaining a request for system information from a UE; components for providing the request for system information to a system information service of a wireless network; components for receiving system information from the system information service in response to providing the request; and components for providing the system information from the system information service to the UE.

[0012] In one aspect of this disclosure, a computer-readable medium is provided. The computer-readable medium stores computer-executable code at a network node, which, when executed by one or more processors, causes the network node to: obtain a request for system information from a UE; provide the request for the system information to a system information service of a wireless network; receive the system information from the system information service in response to the request; and provide the system information from the system information service to the UE.

[0013] In some aspects, the technology described herein relates to an apparatus for wireless communication at a network node, the apparatus comprising: one or more memories; and one or more processors coupled to the one or more memories and configured to cause the network node to: obtain system information from a system information service; obtain a request from a UE for the system information; and, in response to the request, provide the system information to the UE, wherein the system information was obtained from the system information service prior to the request.

[0014] In some respects, the technology described herein relates to a method for wireless communication at a network node, the method comprising: obtaining system information from a system information service; obtaining a request from a UE for the system information; and providing the system information to the UE in response to the request, wherein the system information was obtained from the system information service prior to the request.

[0015] In some aspects, the technology described herein relates to an apparatus for wireless communication at a network node, the apparatus comprising: components for obtaining system information from a system information service; obtaining a request from a UE for the system information; and components for providing the system information to the UE in response to the request, wherein the system information was obtained from the system information service prior to the request.

[0016] In one aspect of this disclosure, a computer-readable medium is provided. The computer-readable medium stores computer-executable code at a network node, which, when executed by one or more processors, causes the network node to: obtain system information from a system information service; obtain a request from a UE for the system information; and, in response to the request, provide the system information to the UE, wherein the system information was obtained from the system information service prior to the request.

[0017] In some aspects, the technology described herein relates to an apparatus for wireless communication at a system information service in a wireless network, the apparatus comprising: one or more memories; and one or more processors coupled to the one or more memories and configured to cause the system information service to: receive a request for system information from a UE served by a network node; and, in response to the request, provide the system information to the network node serving the UE.

[0018] In some respects, the technology described herein relates to a method for wireless communication at a system information service in a wireless network, the method comprising: receiving a request for system information from a UE served by a network node; and, in response to the request, providing the system information to the network node serving the UE.

[0019] In some respects, the technology described herein relates to an apparatus for wireless communication at a system information service in a wireless network, the apparatus comprising: components for receiving a request for system information from a UE served by a network node; and components for providing the system information to the network node serving the UE in response to the request.

[0020] In one aspect of this disclosure, a computer-readable medium is provided. The computer-readable medium stores computer-executable code at a system information service, which, when executed by one or more processors, enables the system information service to: receive a request for system information from a UE served by a network node; and, in response to the request, provide the system information to the network node serving the UE.

[0021] In some aspects, the technology described herein relates to an apparatus for wireless communication at a system information service of a wireless network, the apparatus comprising: one or more memories; and one or more processors coupled to the one or more memories and configured to cause the system information service to: obtain system information from one or more of the service of the wireless network or radio nodes of the wireless network; and provide the system information from the system information service to one or more network nodes.

[0022] In some respects, the technology described herein relates to a method for wireless communication at a system information service of a wireless network, the method comprising: obtaining system information from one or more of the service of the wireless network or radio nodes of the wireless network; and providing the system information from the system information service to one or more network nodes.

[0023] In some respects, the technology described herein relates to an apparatus for wireless communication at a system information service of a wireless network, the apparatus comprising: components for obtaining system information from one or more of the service of the wireless network or radio nodes of the wireless network; and components for providing the system information from the system information service to one or more network nodes.

[0024] In one aspect of this disclosure, a computer-readable medium is provided. The computer-readable medium stores computer-executable code at a system information service, which, when executed by one or more processors, causes the system information service to: obtain system information from one or more of the services of the wireless network or the radio nodes of the wireless network; and provide the system information from the system information service to one or more network nodes.

[0025] To achieve the foregoing and related objectives, one or more aspects may include the features fully described below and specifically pointed out in the claims. The following description and drawings set forth some exemplary features of one or more aspects in detail. However, these features indicate only a few of the various ways in which the principles of the various aspects may be employed. Attached Figure Description

[0026] Figure 1 This is a diagram illustrating examples of wireless communication systems and access networks (NW) according to various aspects of this disclosure.

[0027] Figure 2 A diagram illustrating the architecture of an example of a decomposed base station according to various aspects of this disclosure is shown.

[0028] Figure 3A This is a diagram illustrating an example of a first subframe within a frame structure according to various aspects of this disclosure.

[0029] Figure 3B This is a diagram illustrating examples of downlink (DL) channels within a subframe according to various aspects of this disclosure.

[0030] Figure 3C This is a diagram illustrating examples of a second subframe within a frame structure according to various aspects of this disclosure.

[0031] Figure 3D This is a diagram illustrating examples of uplink (UL) channels within a subframe according to various aspects of this disclosure.

[0032] Figure 4 This is a block diagram illustrating examples of communication between a base station and a user equipment (UE) in an access network according to various aspects of this disclosure.

[0033] Figure 5A This is a diagram illustrating an example of functional partitioning between the core network and the RAN.

[0034] Figure 5B This is an illustration of an example aspect of a cloud-native platform for a wireless network according to various aspects of this disclosure, which may include the integration of core network and RAN services.

[0035] Figure 6Examples of functional partitioning between the core network and the RAN are illustrated according to various aspects of this disclosure.

[0036] Figure 7A This is a diagram illustrating the service-separated RLC and / or MAC functions and PHY layer aspects according to various aspects of this disclosure.

[0037] Figure 7B This is a diagram illustrating examples of addressing and routing of packet transmissions between the service and the UE via a RAN (e.g., including an eDU) according to various aspects of this disclosure.

[0038] Figure 8A Example aspects of uplink packet handling according to various aspects of this disclosure are illustrated.

[0039] Figure 8B Example aspects of downlink packet handling according to various aspects of this disclosure are illustrated.

[0040] Figure 9 Examples of architectural aspects for the generation and delivery of system information (SI) in a service-based wireless network, according to various aspects of this disclosure, are illustrated.

[0041] Figure 10 Example communication flows according to various aspects of this disclosure are illustrated, in which the SI service collects, stores, and generates SIs.

[0042] Figure 11A This is a diagram illustrating the handling of an SI request according to various aspects of this disclosure, the SI request being used for, for example, connection-based SI download from an SI service via a user plane.

[0043] Figure 11B Example aspects of SI downloading for delivering SI as downlink information to the UE, according to various aspects of this disclosure, are illustrated.

[0044] Figure 12 Examples of UEs downloading SIs via the user plane according to various aspects of this disclosure are illustrated.

[0045] Figure 13 Examples are illustrated of eDU obtaining SI for UE according to various aspects of this disclosure.

[0046] Figure 14 Examples of ACMS obtaining SI for UE according to various aspects of this disclosure are illustrated.

[0047] Figure 15 Example communication flow 1500 for obtaining SI / SIB from eDU according to various aspects of this disclosure is illustrated.

[0048] Figure 16 Examples are illustrated whereby a UE without access connectivity requests inclusion in an L2PDU, according to various aspects of this disclosure.

[0049] Figure 17 This is a flowchart of a method for performing wireless communication at a UE according to various aspects of this disclosure.

[0050] Figure 18 This is a flowchart of a method for wireless communication at a network node according to various aspects of this disclosure.

[0051] Figure 19 This is a flowchart of a method for wireless communication at a network node according to various aspects of this disclosure.

[0052] Figure 20 This is a flowchart of a method for conducting wireless communication at an SI service center according to various aspects of this disclosure.

[0053] Figure 21 This is a flowchart of a method for conducting wireless communication at an SI service center according to various aspects of this disclosure.

[0054] Figure 22 These are illustrations of specific hardware implementations for an apparatus or UE according to various aspects of this disclosure.

[0055] Figure 23 These are illustrations of specific hardware implementations for network entities according to various aspects of this disclosure.

[0056] Figure 24 These are illustrations of specific hardware implementations for network entities according to various aspects of this disclosure.

[0057] Figure 25 These are illustrations of specific hardware implementations for network entities according to various aspects of this disclosure. Detailed Implementation

[0058] A wireless network can have a service-based architecture that combines the functionality of core network and radio access network (RAN) nodes. This service-based architecture can be provided on a cloud platform using application programming (API) interfaces. The service can provide various functionalities for the wireless network. Examples of services may include access control services, mobility services, public warning system (PWS) services, vehicle-to-everything (V2X) services, multicast and broadcast services (MBS) services, location services, and system information (SI) services, among others. The service-based architecture allows individual services hosted on the wireless network platform to be adapted or upgraded independently of other services. For example, an SI service may obtain SI inputs and / or system information blocks (SIBs) from various services that are part of the wireless network and from one or more radio nodes (in some respects, these nodes may be referred to as distributed units (DUs) or enhanced distributed units (eDUs)). The SI service can collect and maintain the obtained system information inputs and can generate SI / SIBs that can be provided to one or more user equipment (UEs) served by the wireless network. The SI service can control the delivery mode of the SI / SIBs to the UE. Examples of delivery modes may include, for example, broadcast, on-demand in response to a request, and / or user plane (UP) download.

[0059] The aspects presented herein provide various procedures for acquiring SIs in a service-based wireless network, enabling more efficient use of system overhead through targeted delivery of system information. For example, compared to periodic broadcasts of SIs / SIBs, the aspects specify that SIs / SIBs are provided to the UE in response to a request from the UE, which saves radio resources and allows for improved system efficiency and reduced system overhead. For instance, SIs / SIBs can be provided in response to a UE request, rather than reserving radio resource windows for periodic broadcasts of SIs / SIBs. Targeted delivery to the UE uses radio resources more efficiently than periodic broadcasts of SIs / SIBs and allows for an increase in the maximum number of SIs or SIBs. Delivering SIs / SIBs in response to a UE request enables finer-grained control over SIs / SIBs, such as allowing for independent updates of SIs / SIBs for different services. The aspects presented herein also reduce UE power consumption because the UE can request specific SIs / SIBs and can reduce or skip monitoring of periodic SI broadcasts. The aspects presented in this article allow for improved security and increased network control over access to SI / SIBs by enabling authentication and authorization of the UE before the requested SI or SIB is provided to the UE.

[0060] Alternatively or additionally, the UE may transmit a request for a specific SI or SIB to the SI service in Internet Protocol (IP) packets, and the UE may receive the requested SI / SIB in IP packets from the SI service. Requests and delivery via IP packets enable transparent routing at the eDU and allow switching on the user plane (UP) without the need for a control plane (CP) between the UE and the SI service.

[0061] In some respects, the UE may transmit a request for one or more SIs / SIBs to a network node such as an eDU or a core network service such as Access Connection Management Service (ACMS). Then, before providing one or more SIs / SIBs to the UE in response to the UE's request, the network node may request and receive the indicated SIs / SIBs from the SI service via an API interface. In some respects, the eDU or ACMS may maintain a subscription to the SI service.

[0062] Additionally or alternatively, a network node such as an eDU may receive an SI / SIB from an SI service before receiving a request from a UE. For example, the SI service may determine the SI / SIB to be delivered from the eDU and may provide the determined SI / SIB to the eDU. When the eDU receives a request from the UE, the eDU may respond by transmitting the requested SI / SIB that it previously received from the SI service. For example, the UE may request the SI / SIB in a Layer 2 (L2) Protocol Data Unit (PDU) it sends to the eDU. The eDU may respond by transmitting the requested SI / SIB in one or more L2 PDUs. Unicast delivery from a network node such as an eDU enables the provision of SI / SIBs in response to requests from connected UEs (e.g., from the UE) or from UEs that are idle or inactive and not connected to the eDU.

[0063] The detailed descriptions following, illustrated with reference to the accompanying drawings, describe various configurations and do not represent the only configurations in which the concepts described herein can be practiced. To provide a thorough understanding of the various concepts, the detailed descriptions include specific details. However, these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring these concepts.

[0064] Various apparatuses and methods are presented with reference to several aspects of a telecommunications system. These apparatuses and methods are described in detail below and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively, “elements”). These elements can be implemented using electronic hardware, computer software, or any combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole.

[0065] As an example, an element, any part of an element, or any combination of elements may be implemented as a "processing system" including one or more processors. When multiple processors are implemented, the multiple processors may perform functions individually or in combination. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, system-on-a-chip (SoCs), baseband processors, field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gate logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionalities described throughout this disclosure. One or more processors in a processing system may execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other terms, software should be broadly interpreted as instructions, instruction sets, code, code segments, program code, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, or any combination thereof.

[0066] Therefore, in one or more example aspects, specific implementations, and / or use cases, the described functionality may be implemented in hardware, software, or any combination thereof. If implemented in software, the functionality may be stored or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media include computer storage media. Storage media can be any available medium that can be accessed by a computer. By way of example, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disc storage devices, magnetic disk storage devices, other magnetic storage devices, combinations of these types of computer-readable media, or any other medium that can be used to store computer-executable code in the form of instructions or data structures accessible by a computer.

[0067] While aspects, implementations, and / or use cases are described herein by way of example, additional or different aspects, implementations, and / or use cases may arise in many different arrangements and scenarios. The aspects, implementations, and / or use cases described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and package arrangements. For example, aspects, implementations, and / or use cases may arise via integrated chip implementations and other devices based on non-modular components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, AI-enabled devices, etc.). While some examples may or may not be specific to a use case or application, the described examples may exhibit broad applicability. Aspects, implementations, and / or use cases can range from chip-level or modular components to non-modular, non-chip-level implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more of the technologies described herein. In some practical settings, devices incorporating the described aspects and features may also include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily involve multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The techniques described herein can be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or decomposed components, end-user equipment, etc., of various sizes, shapes, and configurations.

[0068] The deployment of communication systems such as 5G NR systems can be arranged in a variety of ways using various components or parts. In a 5G NR system or network, network nodes, network entities, network mobility elements, radio access network (RAN) nodes, core network nodes, network elements or network equipment (such as base stations (BS)) or one or more units (or components) performing base station functions can be implemented in aggregated or decomposed architectures. For example, BSs (such as Node B (NB), evolved NB (eNB), NR BS, 5G NB, access point (AP), transmit / receive point (TRP), or cell, etc.) can be implemented as aggregated base stations (also known as standalone BS or monolithic BS) or decomposed base stations.

[0069] Aggregated base stations can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. Decentralized base stations can be configured to utilize a protocol stack that is physically or logically distributed across two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some respects, the CU may be implemented within a RAN node, and one or more DUs may co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other RAN nodes. DUs may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may be implemented as a virtual unit, namely a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0070] Base station operation or network design can take into account the aggregation characteristics of base station functionality. For example, decomposed base stations can be utilized in Integrated Access Backhaul (IAB) networks, Open Radio Access Networks (O-RAN (such as network configurations initiated by the O-RAN Alliance)), or Virtualized Radio Access Networks (vRAN, also known as Cloud Radio Access Networks (C-RAN)). Decomposition can include distributing functionality across two or more units in various physical locations, as well as virtually distributing the functionality of at least one unit, which enables flexibility in network design. The various units of a decomposed base station or decomposed RAN architecture can be configured to communicate wirelessly with at least one other unit.

[0071] Figure 1 This is an example diagram illustrating a wireless communication system and access network 100. The wireless communication system (also referred to as a wireless wide area network (WWAN)) includes a base station 102, a UE 104, an evolved packet core (e.g., EPC 160), and another core network 190 (e.g., a 5G core (5GC)). As presented herein, the wireless communication system may have a merged core network and RAN platform with a service-based architecture on a cloud-native platform, such as, for example, combining... Figure 5B , Figure 6 , Figure 7A , Figure 7B , Figure 9 Described by any of them.

[0072] The radio node, which may be referred to as base station 102, may include macro cells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Small cells include femtocells, picocells, and microcells.

[0073] Base station 102 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can interface with EPC 160 via a first backhaul link 132 (e.g., S1 interface). Base station 102 configured for 5G NR (collectively referred to as Next Generation RAN (NG-RAN)) can interface with core network 190 via a second backhaul link 184. Radio nodes configured for 6G or other service-based architectures may have API interfaces 178 related to various services of the core network, such as, for example, combined with Figure 5B , Figure 6 , Figure 7A , Figure 7B , Figure 9 As described in any of them. A service-based architecture may include, for example, services represented by service 175 and SI service 173, and application 177. Figure 1 The example shown is eDU 171, which is a radio node, but such radio nodes may also be referred to as DU, network node, network entity, or other names.

[0074] In addition to other functions, base station 102 may perform one or more of the following functions: user data transmission, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment tracking, RAN information management (RIM), paging, location, and delivery of alarm messages. Base stations 102 may communicate directly or indirectly with each other via a third backhaul link 134 (e.g., an X2 interface) (e.g., via EPC 160 or core network 190). The first backhaul link 132, the second backhaul link 184, and the third backhaul link 134 may be wired or wireless.

[0075] In some aspects, a base station (e.g., one of base stations 102 or one of base stations 180) may be referred to as a RAN or radio node, and may include aggregated or decomposed components. As an example of a decomposed RAN, a base station or radio node may include a central unit (CU) (e.g., CU 106), one or more DUs (e.g., DU 105), and / or one or more remote units (RUs) (e.g., RU 109), such as... Figure 1As illustrated in the diagram. RAN can be decomposed using the split between RU 109 and the aggregation CU / DU. RAN can be decomposed using the split between CU 106, DU 105, and RU 109. RAN can be decomposed using the split between CU 106 and the aggregation DU / RU. CU 106 and one or more DUs can be connected via F1 interfaces. DU 105 and RU 109 can be connected via fronthaul interfaces. The connection between CU 106 and DU 105 can be referred to as midhaul, and the connection between DU 105 and RU 109 can be referred to as fronthaul. The connection between CU 106 and the core network 190 can be referred to as backhaul.

[0076] The RAN can be based on functional splitting between various components of the RAN (e.g., between CU 106, DU 105, or RU 109). CU 106 can be configured to perform one or more aspects of a wireless communication protocol, such as handling one or more layers of a protocol stack, and one or more DUs can be configured to handle other aspects of the wireless communication protocol, such as other layers of the protocol stack. In different implementations, the splitting between layers handled by the CU and layers handled by the DU can occur at different layers of the protocol stack. As a non-limiting example, DU 105 can provide a logical node for hosting at least a portion of the Radio Link Control (RLC) layer, Medium Access Control (MAC) layer, and Physical (PHY) layer based on functional splitting. RU can provide a logical node configured to host at least a portion of the PHY layer and radio frequency (RF) processing. CU 106 can host higher-layer functions, such as the Serving Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, and / or upper layers, for example, above the RLC layer. In other implementations, the splitting between layer functions provided by the CU, DU, or RU can differ.

[0077] Different functional divisions can be provided for eDUs in service-based architectures, for example, such as combining Figure 5B and Figure 6 As described.

[0078] Base station 102 or a radio node can wirelessly communicate with UE 104. Each base station in base station 102 can provide communication coverage for a corresponding geographic coverage area 110. Overlapping geographic coverage areas may exist. For example, a small cell may have a coverage area 111 that overlaps with the corresponding geographic coverage area 110 of one or more base stations (e.g., one or more macro base stations, such as base station 102). A network that includes both small cells and macro cells can be referred to as a heterogeneous network. A heterogeneous network may also include a Home Evolution Node B (eNB) (HeNB), which can provide services to a restricted group referred to as a Closed Subscriber Group (CSG). The communication link 120 between base station 102 and UE 104 may include uplink (UL) (also referred to as reverse link) transmission from UE to base station and / or downlink (DL) (also referred to as forward link) transmission from base station to UE. The communication link 120 may use multiple-input multiple-output (MIMO) antenna techniques, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may carry one or more carriers. For a total of up to one carrier used for transmission in each direction. Yx MHz ( x For each carrier allocated in carrier aggregation (of component carriers), base station 102 / UE 104 can use up to [number missing] carriers. Y A spectrum with a bandwidth of MHz (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz, etc.). Carriers may be adjacent to each other or may not be adjacent to each other. Carrier allocation may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL compared to UL). Component carriers may include primary component carriers and one or more secondary component carriers. The primary component carrier may be referred to as the primary cell (PCell) and the secondary component carrier may be referred to as the secondary cell (SCell).

[0079] Some UEs can communicate with each other using device-to-device (D2D) communication links, such as D2D communication link 158. D2D communication link 158 can use DL / UL WWAN spectrum. D2D communication link 158 can use one or more sidelink channels, such as the Physical Sidelink Broadcast Channel (PSBCH), Physical Sidelink Discovery Channel (PSDCH), Physical Sidelink Shared Channel (PSSCH), and Physical Sidelink Control Channel (PSCCH). D2D communication can be achieved through various wireless D2D communication systems, such as Bluetooth. ™ (Bluetooth is a trademark of the Bluetooth Special Interest Group (SIG), based on Wi-Fi from the Institute of Electrical and Electronics Engineers (IEEE). ™(Wi-Fi is a trademark of the Wi-Fi Alliance), Wi-Fi based on the IEEE 802.11 standard, LTE, or NR. Some wireless communication networks may include vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I) (e.g., from a vehicle-based communication device to a road infrastructure node (such as a roadside unit (RSU)), vehicle-to-network (V2N) (e.g., from a vehicle-based communication device to one or more network nodes (such as a base station)), vehicle-to-pedestrian (V2P), cellular vehicle-to-everything (C-V2X), and / or combinations thereof and / or with other devices, which can be collectively referred to as vehicle-to-everything (V2X) communication. See again. Figure 1 In some respects, UE 104 (e.g., a Vehicle User Equipment (VUE) or other UE) can be configured to send messages directly to another UE 104. The communication can be based on V2X or other D2D communication, such as Proximity Service (ProSe).

[0080] The wireless communication system may also include a Wi-Fi access point (AP) (such as AP 150) that communicates with a Wi-Fi station (STA) (such as STA 152) via a communication link 154, for example, in unlicensed spectrum at 5 GHz. When communicating in unlicensed spectrum, STA 152 / AP 150 may perform a free channel assessment (CCA) before communication to determine whether the channel is available.

[0081] Small cells can operate in licensed and / or unlicensed spectrum. When operating in unlicensed spectrum, small cells can employ NR and use the same unlicensed spectrum (e.g., 5 GHz, etc.) as the AP 150. Small cells employing NR in unlicensed spectrum can improve coverage of the access network and / or increase the capabilities of the access network.

[0082] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc., based on frequency / wavelength. In 5G NR, two initial operating bands have been designated as frequency ranges FR1 (410MHz to 7.125GHz) and FR2 (24.25GHz to 52.6GHz). Although a portion of FR1 is greater than 6GHz, in various documents and articles, FR1 is often (interchangeably) referred to as the "sub-6GHz" band. Similar naming issues sometimes occur with FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although this is distinct from the Extremely High Frequency (EHF) band (30GHz to 300GHz) designated as "millimeter wave" by the International Telecommunication Union (ITU).

[0083] The frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR studies have designated the operating bands for these mid-band frequencies as the frequency range designation FR3 (7.125 GHz to 24.25 GHz). Bands falling within FR3 can inherit FR1 and / or FR2 characteristics, thus effectively extending the features of FR1 and / or FR2 to mid-band frequencies. Additionally, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been designated as the frequency range designations FR2-2 (52.6 GHz to 71 GHz), FR4 (71 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher bands falls within the EHF band.

[0084] In view of the above, unless otherwise specifically stated, the term "below 6 GHz" as used herein can broadly refer to frequencies less than 6 GHz, within FR1, or including intermediate frequency band frequencies. Furthermore, unless otherwise specifically stated, the term "millimeter wave" as used herein can broadly refer to frequencies that can include intermediate frequency band frequencies, within FR2, FR4, FR2-2 and / or FR5, or within the EHF band.

[0085] Base stations (whether small cells or macro cells (e.g., large base stations)) may include and / or be referred to as eDUs, radio nodes, network nodes, network entities, eNBs, gNodeBs (gNBs), or other types of base stations. Some base stations (such as gNBs) may operate in conventional sub-6 GHz spectrum, millimeter wave frequencies, and / or near-millimeter wave frequencies to communicate with UE 104. When a gNB operates in millimeter wave frequencies or near-millimeter wave frequencies, base station 180 may be referred to as a millimeter wave base station. The millimeter wave base station may utilize beamforming 182 with UE 104 to compensate for path loss and short range. Base station 180 and UE 104 may each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming.

[0086] Base station 180 may transmit beamformed signals to UE 104 in one or more transmit directions 185. UE 104 may receive beamformed signals from base station 180 in one or more receive directions 183. UE 104 may also transmit beamformed signals to base station 180 in one or more transmit directions (e.g., 183). Base station 180 may receive beamformed signals from UE 104 in one or more receive directions (e.g., 185). Base station 180 / UE 104 may perform beamforming to determine the optimal receive and transmit directions for each of base station 180 / UE 104. The transmit and receive directions of base station 180 may be the same or different. The transmit and receive directions of UE 104 may be the same or different.

[0087] EPC 160 may include a mobility management entity (e.g., MME 162), other MMEs 164, a serving gateway 166, a multimedia broadcast multicast service (MBMS) gateway (e.g., MBMS gateway 168), a broadcast multicast service center (BM-SC) (e.g., BM-SC 170), and a packet data network (PDN) gateway (e.g., PDN gateway 172). MME 162 may communicate with a Home Subscriber Server (HSS) (e.g., HSS 174). MME 162 is the control node that handles signaling between UE 104 and EPC 160. Generally, MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are delivered through the serving gateway 166, which is itself connected to the PDN gateway 172. PDN gateway 172 provides UE IP address allocation and other functions. PDN gateway 172 and BM-SC 170 are connected to IP service 176. IP service 176 may include the Internet, intranet, IP Multimedia Subsystem (IMS), PS streaming service, and / or other IP services. BM-SC 170 provides functions for MBMS user service dispatch and delivery. BM-SC 170 can act as an entry point for content provider MBMS transmission, can be used to authorize and initiate MBMS bearer services in a Public Land Mobile Network (PLMN), and can be used to schedule MBMS transmission. MBMS gateway 168 can be used to allocate MBMS services to base station 102 belonging to a Broadcast-Specific Service Multicast Single Frequency Network (MBSFN) area, and can be responsible for session management (start / stop) and collecting eMBMS-related billing information.

[0088] The core network 190 may include Access and Mobility Management Functions (AMF) (e.g., AMF 192), other AMFs 193, Session Management Functions (SMF) 194, and User Plane Functions (UPF) (e.g., UPF 195). AMF 192 may communicate with Unified Data Management (UDM) 196. AMF 192 is the control node that handles signaling between UE 104 and the core network 190. Generally, AMF 192 provides QoS flow and session management. All user Internet Protocol (IP) packets are delivered through UPF 195. UPF 195 provides UE IP address allocation and other functions. UPF 195 connects to IP service 197. IP service 197 may include the Internet, intranet, IP Multimedia Subsystem (IMS), Packet Switched (PS) Streaming (PSS) service, and / or other IP services.

[0089] Base station 102 may include and / or be referred to as gNB, Node B, eNB, access point, transceiver base station, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), transmit / receive point (TRP), network node, network entity, network equipment, eDU, or some other suitable terminology. Base station 102 may be implemented as an integrated access and backhaul (IAB) node, relay node, sidelink node, aggregated (monolithic) base station with baseband units (BBU) (including CU and DU) and RU, or as a decomposed base station including one or more of CU, DU, eDU, and / or RU. In some aspects, a base station that may include a decomposed base station and / or an aggregated base station may be referred to as Next Generation (NG) RAN (NG-RAN). Base station 102 provides access points to the core network, such as EPC 160 for UE 104, core network 190, and / or service 175.

[0090] Examples of UEs include cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, GPS devices, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablets, smart devices, wearable devices, vehicles, electricity meters, air pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other similarly functional device. Some UEs may be referred to as IoT devices (e.g., parking timers, air pumps, toasters, vehicles, heart monitors, etc.). UEs may also be referred to as stations, mobile stations, subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless terminals, remote terminals, mobile phones, user agents, mobile clients, clients, or some other suitable terms. In some scenarios, the term UE may also be applied to one or more companion devices, such as in a device constellation arrangement. One or more of these devices may jointly access the network and / or individually access the network.

[0091] In some aspects, UE 104 may include a system information component 198, which is configured to: cause UE 104 to send a request to a network node for system information associated with a system information service of the wireless network; and receive system information from the system information service of the wireless network via the network node.

[0092] Network nodes such as base stations 102, 180, base station components, or radio nodes (e.g., CU 106, DU 105, eDU 171, and / or RU 109) may include a system information component 199. In some aspects, the system information component 199 may be configured to cause the network node to: obtain a request for system information from the UE; provide the request for system information to the system information service 173 of the wireless network; receive system information from the system information service in response to the request; and provide the system information from the system information service to the UE 104. In some aspects, the system information component 199 may be configured to cause the network node to: obtain system information from the system information service; obtain a request for system information from the UE 104; and provide the system information to the UE in response to the request, wherein the system information was obtained from the system information service prior to the request.

[0093] In some aspects, system information service 173 may include system information component 191. In some aspects, system information component 191 may be configured to cause system information service 173 to: receive a request for system information from UE 104 served by a network node; and, in response to the request, provide the system information to the network node serving the UE. In some aspects, system information component 191 may be configured to cause system information service 173 to: obtain system information from one or more of the service 175 of the wireless network or the radio nodes of the wireless network; and provide the system information from system information service 173 to one or more network nodes.

[0094] The deployment of communication systems, such as 5G NR systems or other communication systems, can be arranged in a variety of ways using various components or constituent parts. In a 5G NR system or network, network nodes, network entities, network mobility elements, radio access network (RAN) nodes, core network nodes, network elements or network equipment (such as base stations (BS)) or one or more units (or components) performing base station functions can be implemented in aggregated or decomposed architectures. For example, BSs (such as Node B (NB), evolved NB (eNB), NR BS, 5G NB, access point (AP), transmit / receive point (TRP), or cell, etc.) can be implemented as aggregated base stations (also known as standalone BS or monolithic BS) or decomposed base stations.

[0095] Aggregated base stations can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. Decentralized base stations can be configured to utilize a protocol stack that is physically or logically distributed across two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some respects, the CU may be implemented within a RAN node, and one or more DUs may co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other RAN nodes. DUs may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may be implemented as a virtual unit, namely a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0096] Base station operation or network design can take into account the aggregation characteristics of base station functionality. For example, decomposed base stations can be utilized in Integrated Access Backhaul (IAB) networks, Open Radio Access Networks (O-RAN (such as network configurations initiated by the O-RAN Alliance)), or Virtualized Radio Access Networks (vRAN, also known as Cloud Radio Access Networks (C-RAN)). Decomposition can include distributing functionality across two or more units in various physical locations, as well as virtually distributing the functionality of at least one unit, which enables flexibility in network design. The various units of a decomposed base station or decomposed RAN architecture can be configured to communicate wirelessly with at least one other unit.

[0097] As an example, Figure 2 A diagram illustrating an example architecture of a decomposed base station 200 is shown. The architecture of the decomposed base station 200 may include one or more CUs (e.g., CU 210) that can communicate directly with the core network 220 via a backhaul link, or indirectly with the core network 220 via one or more decomposed base station units (such as a near real-time (near RT) RAN Intelligent Controller (RIC) via an E2 link (e.g., near RT RIC 225), or a non-real-time (non-RT) RIC (e.g., non-RT RIC 215) associated with a Service Management and Orchestration (SMO) framework (e.g., SMO framework 205), or both). CU 210 may communicate with one or more DUs (e.g., DU 230) via a corresponding midhaul link (such as an F1 interface). DU 230 may communicate with one or more RUs (e.g., RU 240) via a corresponding fronthaul link. RU 240 may communicate with a corresponding UE (e.g., UE 204) via one or more radio frequency (RF) access links. In some specific implementations, UE 204 can be served by multiple RUs simultaneously.

[0098] Each of the units (i.e., CUs (e.g., CU 210), DUs (e.g., DU 230), RUs (e.g., RU 240), and near-RT RICs (e.g., near-RT RIC 225), non-RT RICs (e.g., non-RT RIC 215), and SMO framework 205) may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via wired or wireless transmission media. Each unit in the units, or an associated processor or controller that provides instructions to the communication interfaces of these units, may be configured to communicate with one or more other units in the other units via transmission media. For example, these units may include wired interfaces configured to receive signals or transmit signals to one or more other units via wired transmission media. Additionally, these units may include wireless interfaces that may include receivers, transmitters, or transceivers (such as RF transceivers) configured to receive signals via wireless transmission media and / or transmit signals to one or more other units.

[0099] In some aspects, CU 210 can host one or more higher-level control functions. Such control functions may include Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Serving Data Adaptation Protocol (SDAP), etc. Each control function can be implemented using an interface configured to communicate signaling with other control functions hosted by CU 210. CU 210 can be configured to handle user plane functionality (i.e., Central Unit-User Plane (CU-UP)), control plane functionality (i.e., Central Unit-Control Plane (CU-CP)), or a combination thereof. In some implementations, CU 210 can be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, CU-UP units can communicate bidirectionally with CU-CP units via an interface such as an E1 interface. CU 210 can be implemented to communicate with DU 230 for network control and signaling purposes, as needed.

[0100] DU 230 may correspond to a logic unit that includes one or more base station functions for controlling the operation of one or more RUs. In some aspects, DU 230 may at least partially host one or more of the Radio Link Control (RLC) layer, the Media Access Control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation, demodulation, etc.) according to functional splits (such as those defined by 3GPP). In some aspects, DU 230 may further host one or more low PHY layers. Each layer (or module) may be implemented using an interface configured to communicate signaling with other layers (and modules) hosted by DU 230 or with control functions hosted by CU 210.

[0101] Lower-layer functionality can be implemented by one or more RUs. In some deployments, the RU 240 controlled by the DU 230 can correspond to a logical node that hosts RF processing functions or low-PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, or Physical Random Access Channel (PRACH) extraction and filtering, or both, at least in part based on functional decomposition (such as lower-layer functional decomposition). In this architecture, the RU 240 can be implemented to handle over-the-air (OTA) communications with one or more UEs (e.g., UE 204). In some specific implementations, the real-time and non-real-time aspects of control plane and user plane communications with the RU 240 can be controlled by the corresponding DU. In some scenarios, this configuration allows the DU and CU210 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0102] SMO framework 205 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, SMO framework 205 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces such as the O1 interface. For virtualized network elements, SMO framework 205 can be configured to interact with a cloud computing platform such as Open Cloud (O-Cloud) 290 to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface such as the O2 interface. Such virtualized network elements may include, but are not limited to, CUs, DUs, RUs, and near-RT RICs. In some implementations, SMO framework 205 can communicate with the hardware aspects of the 4G RAN (such as Open eNB (O-eNB) 211) via the O1 interface. Additionally, in some implementations, SMO framework 205 can communicate directly with one or more RUs via the O1 interface. SMO framework 205 may also include a non-RT RIC 215 configured to support the functionality of SMO framework 205.

[0103] The non-RT RIC 215 can be configured to include logical functions enabling non-real-time control and optimization of RAN elements and resources, including artificial intelligence (AI) / machine learning (ML) workflows for model training and updates, or policy-based guidance for applications / features in the near-RT RIC 225. The non-RT RIC 215 can be coupled to or communicate with the near-RT RIC 225, such as via an A1 interface. The near-RT RIC 225 can be configured to include logical functions enabling near real-time control and optimization of RAN elements and resources via an interface, such as an E2 interface, connecting one or more CUs, one or more DUs, or both, and O-eNBs to the near-RT RIC 225.

[0104] In some implementations, to generate AI / ML models to be deployed in the near-RT RIC 225, the non-RT RIC 215 may receive parameters or external enrichment information from an external server. This information can be utilized by the near-RT RIC 225 and may be received from non-network data sources or network functions at the SMO framework 205 or the non-RT RIC 215. In some examples, the non-RT RIC 215 or the near-RT RIC 225 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 215 may monitor long-term trends and patterns in performance and employ AI / ML models to perform corrective actions via the SMO framework 205 (such as reconfiguration via O1) or by creating RAN management policies (such as A1 policies).

[0105] At least one of CU 210, DU 230, and RU 240 may be referred to as base station 202. Therefore, base station 202 may include one or more of CU 210, DU 230, and RU 240 (each component is indicated by a dashed line to indicate that each component may or may not be included in base station 202). Base station 202 provides UE 204 with an access point to core network 220. The communication link between RU (e.g., RU 240) and UE (e.g., UE 204) may include uplink (UL) (also referred to as reverse link) transmission from UE 204 to RU 240 and / or downlink (DL) (also referred to as forward link) transmission from RU 240 to UE 204.

[0106] Some UEs can communicate with each other using D2D communication (e.g., D2D communication link 258). D2D communication link 258 can use DL / UL WWAN spectrum. D2D communication link 258 can use one or more sidelink channels. D2D communication can be achieved through various wireless D2D communication systems, such as, for example, Bluetooth, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.

[0107] The wireless communication system may also include a Wi-Fi AP 250, which communicates with the UE 204 (also referred to as a Wi-Fi STA) via a communication link 254, for example, in an unlicensed spectrum such as 5 GHz. When communicating in unlicensed spectrum, the UE 204 / Wi-Fi AP 250 may perform a CCA before communication to determine whether the channel is available.

[0108] Base station 202 and UE 204 may each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming. Base station 202 may transmit beamformed signals 282 to UE 204 in one or more transmit directions. UE 204 may receive beamformed signals from base station 202 in one or more receive directions. UE 204 may also transmit beamformed signals 284 to base station 202 in one or more transmit directions. Base station 202 may receive beamformed signals from UE 204 in one or more receive directions. Base station 202 / UE 204 may perform beamforming training to determine the optimal receive and transmit directions for each of base station 202 / UE 204. The transmit and receive directions of base station 202 may be the same or different. The transmit and receive directions of UE 204 may be the same or different.

[0109] The core network 220 may include Access and Mobility Management Functions (AMF) (e.g., AMF 261), Session Management Functions (SMF) (e.g., SMF 262), User Plane Functions (UPF) (e.g., UPF 263), Unified Data Management (UDM) (e.g., UDM 264), one or more location servers 268, and other functional entities. AMF 261 is the control node that processes signaling between the UE and the core network 220. AMF 261 supports registration management, connection management, mobility management, and other functions. SMF 262 supports session management and other functions. UPF 263 supports packet routing, packet forwarding, and other functions. UDM 264 supports the generation of authentication and key negotiation (AKA) credentials, user identity processing, access authorization, and subscription management. One or more location servers 268 are exemplified as including Gateway Mobile Location Center (GMLC) (e.g., GMLC 265) and Location Management Functions (LMF) (e.g., LMF 266). However, generally, one or more location servers 268 may include one or more location / positioning servers, which may include one or more of GMLC 265, LMF 266, Position Determination Entity (PDE), Serving Mobile Location Center (SMLC), Mobile Location Center (MPC), etc. GMLC 265 and LMF 266 support UE location services. GMLC 265 provides an interface for clients / applications (e.g., emergency services) to access UE location information. LMF 266 receives measurement and auxiliary information from NG-RAN and UE 204 via AMF 261 to calculate the location of UE 204. NG-RAN may use one or more positioning methods to determine the location of UE 204. Positioning UE 204 may involve signal measurement, location estimation, and optional speed calculation based on these measurements. Signal measurement may be performed by UE 204 and / or base station 202 serving UE 204. The measured signals may be based on one or more of the following systems / signals / sensors: Satellite Positioning System (SPS) 270 (e.g., one or more of Global Navigation Satellite System (GNSS), Global Positioning System (GPS), Non-Terrestrial Network (NTN) or other position / location systems), LTE signals, Wireless Local Area Network (WLAN) signals, Bluetooth signals, Terrestrial Beacon System (TBS), sensor-based information (e.g., barometric pressure sensor, motion sensor), NR Enhanced Cell ID (NR E-CID) method, NR signals (e.g., multiple round-trip time (multiple RTT), DL departure angle (DL-AoD), DL time difference of arrival (DL-TDOA), UL time difference of arrival (UL-TDOA), and UL angle of arrival (UL-AoA) positioning) and / or other systems / signals / sensors.

[0110] Refer again Figure 2 In some respects, UE 204 and Figure 1 Similar to UE 104, it may include a system information component 198, which is configured to enable UE 204 to: send a request to a network node for system information associated with a system information service of the wireless network; and receive system information from the system information service of the wireless network via the network node.

[0111] Network nodes, such as base station 202 or components of a base station (e.g., CU 210, DU 230, eDU, and / or RU 240), may include system information component 199. In some aspects, system information component 199 may be configured to cause the network node to: obtain a request for system information from the UE; provide the request for system information to the system information service of the wireless network; receive system information from the system information service in response to the request; and provide the system information from the system information service to the UE 104. In some aspects, system information component 199 may be configured to cause the network node to: obtain system information from the system information service; obtain a request for system information from the UE 104; and provide the system information to the UE in response to the request, wherein the system information was obtained from the system information service prior to the request.

[0112] In some aspects, the system information service may include a system information component 191. In some aspects, the system information component 191 may be configured to enable the system information service to: receive a request for system information from a UE 204 served by a network node; and, in response to the request, provide the system information to the network node serving the UE. In some aspects, the system information component 191 may be configured to enable the system information service to: obtain system information from one or more of the services of the wireless network or the radio nodes of the wireless network; and provide the system information from the system information service to one or more network nodes.

[0113] Figure 3A Figure 300 illustrates an example of the first subframe within an exemplary frame structure. This example aspect can be applied to a 5G NR frame structure to illustrate an example radio frame with time and frequency resources. This aspect can also be applied to other wireless communication systems. Figure 3B Figure 330 illustrates an example of a DL channel within a subframe. Figure 3C Figure 350 shows an example of the second subframe within an example frame structure. Figure 3DFigure 380 illustrates an example of a UL channel within a subframe. The frame structure can be Frequency Division Duplex (FDD) (where subframes within a specific set of subcarriers (carrier system bandwidth) are dedicated to either DL or UL), or Time Division Duplex (TDD) (where subframes within a specific set of subcarriers (carrier system bandwidth) are dedicated to both DL and UL). Figure 3A , Figure 3C In the provided example, the frame structure is assumed to be TDD, where subframe 4 is configured using slot format 28 (most of which are DL), where D is DL, U is UL, and F is flexible and can be used between DL / UL, and subframe 3 is configured using slot format 1 (all of which are UL). Although subframes 3 and 4 are shown as having slot formats 1 and 28 respectively, any particular subframe can be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are both DL and UL, respectively. Other slot formats 2-61 include a mixture of DL, UL, and flexible symbols. The slot format is configured for the UE via the received Slot Format Indicator (SFI) (dynamically configured via DL Control Information (DCI) or semi-statically / statically configured via Radio Resource Control (RRC) signaling). Note that the following description also applies to 5G NR frame structures as TDD.

[0114] Figures 3A to 3D The frame structure is illustrated, and aspects of this disclosure may be applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10 ms) can be divided into 10 equal-sized subframes (1 ms). Each subframe may include one or more time slots. Subframes may also include micro-time slots, which may include 7, 4, or 2 symbols. Each time slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. For normal CP, each time slot may include 14 symbols, and for extended CP, each time slot may include 12 symbols. Symbols on the DL may be CP Orthogonal Frequency Division Multiplexing (OFDM) (CP-OFDM) symbols. Symbols on the UL may be CP-OFDM symbols (for high-throughput scenarios) or Discrete Fourier Transform (DFT) Extended OFDM (DFT-s-OFDM) symbols (for power-constrained scenarios; limited to single-stream transmission). The number of time slots within a subframe is based on the CP and parameter set. The parameter set defines the subcarrier spacing (SCS) (see Table 1). The symbol length / duration can be scaled by 1 / SCS. Table 1: Parameter Set, SCS, and CP

[0115] For a normal CP (14 symbols / slot), different parameter sets µ 0 through 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For an extended CP, parameter set 2 allows 4 slots per subframe. Therefore, for a normal CP and parameter set µ, there are 14 symbols / slot and 2... µ One time slot / subframe. As shown in Table 1, the subcarrier spacing can be equal to... ,in The parameter sets are 0 to 4. Therefore, the subcarrier spacing for parameter set µ=0 is 15kHz, and the subcarrier spacing for parameter set µ=4 is 240kHz. The symbol length / duration is negatively correlated with the subcarrier spacing. Figures 3A to 3D Examples of a normal frequency division multiplexing (CP) with 14 symbols per time slot and a parameter set of µ=2 with 4 time slots per subframe are provided. The time slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within the frame set, there may be one or more distinct bandwidth portions (BWPs) of frequency division multiplexing (see [link to relevant documentation]). Figure 3B Each BWP can have a specific set of parameters and CP (normal or extended).

[0116] A resource grid can be used to represent the frame structure. Each time slot consists of a resource block (RB) extending for 12 consecutive subcarriers (also known as a physical RB (PRB)). The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0117] like Figure 3A As illustrated, some of the REs carry reference (pilot) signals (RS) for the UE. RS may include demodulation RS (DM-RS) (indicated as R for a particular configuration, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RS) for channel estimation at the UE. RS may also include beam measurement RS (BRS), beam refinement RS (BRRS), and phase tracking RS (PT-RS).

[0118] Figure 3BExamples of various DL channels within a subframe of a frame are illustrated. The Physical Downlink Control Channel (PDCCH) carries the DCI within one or more Control Channel Elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE comprising six RE Groups (REGs), each REG comprising 12 consecutive REs in the OFDM symbol of the RB. The PDCCH within a BWP can be referred to as a Control Resource Set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., a common search space, a UE-specific search space) during PDCCH monitoring timing on the CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at higher and / or lower frequencies on the channel bandwidth. The Primary Synchronization Signal (PSS) may be located within symbol 2 of a specific subframe of the frame. The PSS is generated by the UE (such as...) Figure 1 One of the UEs in UE 104 and / or Figure 2 The UE (204) is used to determine subframe / symbol timing and physical layer identifiers. The secondary synchronization signal (SSS) is located within symbol 4 of a specific subframe of the frame. The SSS is used by the UE to determine the physical layer cell identifier group number and radio frame timing. Based on the physical layer identifier and physical layer cell identifier group number, the UE can determine the physical cell identifier (PCI). Based on this PCI, the UE can determine the location of the DM-RS. The physical broadcast channel (PBCH) carrying the primary information block (MIB) can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (also known as an SS block (SSB)). The MIB provides the number of RBs in the system bandwidth and the system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information not transmitted via the PBCH (such as system information blocks (SIBs)), and paging messages. As presented herein, the UE can request an SI / SIB associated with an SI service and can receive an SI / SIB in response to that request. In some respects, a minimum SI can be provided to enable the UE to request a specific SI / SIB, for example, as combined with Figure 9 and Figures 12 to 16 A more detailed description.

[0119] like Figure 3CAs illustrated, some REs in the REs carry DM-RS (indicated as R for one particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE can transmit DM-RS for the Physical Uplink Control Channel (PUCCH) and DM-RS for the Physical Uplink Shared Channel (PUSCH). The PUSCH DM-RS can be transmitted in the first or first two symbols of the PUSCH. Depending on whether a short or long PUCCH is transmitted and depending on the specific PUCCH format used, the PUCCH DM-RS can be transmitted in different configurations. The UE can transmit a Sounding Reference Signal (SRS). The SRS can be transmitted in the last symbol of a subframe. The SRS can have a comb structure, and the UE can transmit the SRS on one of the comb teeth. The SRS can be used by the base station for channel quality estimation to enable frequency-dependent scheduling of the UL.

[0120] Figure 3D Examples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), pre-decoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgment (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUCCH carries data and may additionally be used to carry buffer status reports (BSR), power clearance reports (PHR), and / or UCIs.

[0121] Figure 4 This is a block diagram illustrating an example of a first wireless device configured to exchange wireless communications with a second wireless device. Figure 4 In the illustrated example, the first wireless device may include a network node, which may be referred to as a radio node, DU, eDU, or base station 410. The second wireless device may include UE 450, and base station 410 may communicate with UE 450 in the access network. Figure 4As shown, base station 410 includes a transmit processor (TX processor 416), a transmitter 418Tx, a receiver 418Rx, an antenna 420, a receive processor (RX processor 470), a channel estimator 474, a controller / processor 475, and at least one memory 476 (e.g., one or more memories). Example UE 450 includes an antenna 452, a transmitter 454Tx, a receiver 454Rx, an RX processor 456, a channel estimator 458, a controller / processor 459, at least one memory 460 (e.g., one or more memories), and a TX processor 468. In other examples, base station 410 and / or UE 450 may include additional or alternative components.

[0122] In the DL, Internet Protocol (IP) packets can be provided to the controller / processor 475. The controller / processor 475 implements Layer 3 and Layer 2 functionality. Layer 3 includes the Radio Resource Control (RRC) layer, and Layer 2 includes the Service Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Media Access Control (MAC) layer. The controller / processor 475 provides RRC layer functionality associated with broadcasting system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-Radio Access Technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with the delivery of upper-layer packet data units (PDUs), error correction via ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel priority ordering.

[0123] TX processor 416 and RX processor 470 implement Layer 1 functionality associated with various signal processing functions. Layer 1 (which includes the physical (PHY) layer) may include error detection on the transport channel, forward error correction (FEC) decoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. TX processor 416 processes the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-order phase shift keying (M-PSK), M-order quadrature amplitude modulation (M-QAM)). The decoded and modulated symbols can then be divided into parallel streams. Each stream can then be mapped to OFDM subcarriers, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domains, and subsequently combined using inverse fast Fourier transform (IFFT) to generate a physical channel carrying a stream of time-domain OFDM symbols. The OFDM streams are spatially pre-decoded to generate multiple spatial streams. The channel estimate from channel estimator 474 can be used to determine the decoding and modulation scheme and for spatial processing. The channel estimate can be derived from a reference signal transmitted by UE 450 and / or channel condition feedback. Each spatial stream can then be provided to different antennas in antenna 420 via a separate transmitter (e.g., transmitter 418Tx). Each transmitter 418Tx can use the corresponding spatial stream to modulate a radio frequency (RF) carrier for transmission.

[0124] At UE 450, each receiver 454Rx receives signals via its corresponding antenna in antenna 452. Each receiver 454Rx recovers the information modulated onto the RF carrier and provides this information to RX processor 456. TX processor 468 and RX processor 456 implement Layer 1 functionality associated with various signal processing functions. RX processor 456 can perform spatial processing on the information to recover any spatial stream destined for UE 450. In cases where multiple spatial streams are destined for UE 450, RX processor 456 can combine two or more of these spatial streams into a single OFDM symbol stream. RX processor 456 then uses a Fast Fourier Transform (FFT) to transform the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal comprises a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, along with the reference signal, are recovered and demodulated by determining the most probable signal constellation point transmitted by base station 410. These soft decisions can be based on a channel estimate calculated by channel estimator 458. Subsequently, the soft decision is decoded and deinterleaved to recover the data and control signals originally transmitted by base station 410 on the physical channel. The data and control signals are then provided to controller / processor 459, which implements layer 3 and layer 2 functionality.

[0125] The controller / processor 459 may be associated with at least one memory 460 storing program code and data. The at least one memory 460 may be referred to as a computer-readable medium. In the UL, the controller / processor 459 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between transport and logical channels to recover IP packets. The controller / processor 459 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operation.

[0126] Similar to the functionality described in conjunction with DL transmission performed by base station 410, controller / processor 459 provides RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connectivity, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with upper-layer PDU delivery, error correction via ARQ, concatenation, segmentation, and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs to TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel priority ordering.

[0127] The channel estimate derived by channel estimator 458 from the reference signal or feedback transmitted by base station 410 can be used by TX processor 468 to select appropriate decoding and modulation schemes and facilitate spatial processing. The spatial stream generated by TX processor 468 can be provided to different antennas in antenna 452 via individual transmitters (e.g., transmitter 454Tx). Each transmitter 454Tx can use the corresponding spatial stream to modulate an RF carrier for transmission.

[0128] UL transmission is processed at base station 410 in a manner similar to that described in conjunction with the receiver function at UE 450. Each receiver 418Rx receives signals via its corresponding antenna in antenna 420. Each receiver 418Rx recovers the information modulated onto the RF carrier and provides that information to RX processor 470.

[0129] The controller / processor 475 may be associated with at least one memory 476 storing program code and data. The at least one memory 476 may be referred to as a computer-readable medium. In the UL, the controller / processor 475 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between transport and logical channels to recover IP packets. The controller / processor 475 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operation.

[0130] At least one of the TX processor 468, RX processor 456, and controller / processor 459 can be configured to combine Figure 1 The system information component 198 performs various aspects.

[0131] At least one of the TX processor 416, RX processor 470, and controller / processor 475 can be configured to combine Figure 1 The system information component 199 performs various aspects.

[0132] Some wireless communication systems may include a service-based architecture and may include system information services (which may be referred to as SI services) for system information operations. The aspects presented herein provide a process for acquiring system information (SI) for a service-based architecture.

[0133] Figure 5A This is a diagram 500 illustrating an example functional partitioning between the core network 530 and the RAN 540. Figure 1 and Figure 2 Various example aspects of the core network (e.g., EPC 160, core network 190, 220) are illustrated, and Figure 1 An example of a base station 102 / 180 as a RAN is shown. Figure 5A The UPF 595, SMF 594, and AMF592, which are part of the core network 530, are shown. Figure 5A The diagram illustrates CU-UP 502 (e.g., providing user plane functionality), CU-CP 504 (e.g., providing control plane functionality), and DU 506, all provided as part of RAN 540. CU-CP and / or CU-UP may include features for… Figure 2 The aspects described in CU 106 and / or 210. DU 506 may include those for... Figure 1 DU 105 or Figure 2 The various aspects described in DU 230. As an example, Figure 5A The various aspects of the core network / RAN hierarchy can be adopted in, for example, 3G, 4G and / or 5G wireless networks. Figure 5A Functional partitioning helps maintain the performance and security of the wireless network, as well as the accessibility of field equipment. Figure 5A Some aspects of the core network 530 may include cloud platform 508, and some aspects of the RAN 540 may include cloud platform 510.

[0134] Figure 5BFigure 525 illustrates an example aspect of a cloud-native platform for a wireless network (e.g., as shown at 526), ​​which may include the combined (or integrated) functionality of core network and RAN services. For example, the platform may be referred to as a combined core / RAN platform 550. The combination of functions between the core network and RAN simplifies protocols and reduces duplication between the core network and RAN. Figure 5B Examples are provided of services that can be hosted in a wireless network based on the deployment topology and / or capabilities required for each service (these services may include merged services that combine core network and RAN functionality). Figure 5B Examples include several services 512, 514, and 516; several applications 520 and 522; and an enhanced distributed unit (eDU) 524, which is part of the consolidated core / RAN platform 550. This platform enables each service 512 to be updated independently of other services. These services provide various functionalities for the wireless network. Examples of services may include access control services, mobility services, PWS services, V2X services, MBS services, and location services, among others. For example, the platform may use API interface 517.

[0135] Figure 6 This illustrates the core network and RAN based on aggregation services and shows the various functions performed by the core network (e.g., AMF 692) and RAN (e.g., CU-CP 602 and / or DU 604) that can be combined. Figure 5B The diagram 600 illustrates the service-based platform distribution. Figure 6 An example functional partitioning 610 between the core network (e.g., 692) and the RAN (e.g., 602 and 604) is illustrated. As illustrated by the arrows, various aspects of the inter-DU functions 606 performed by AMF 692 and / or CU-CP 602 can be performed by different services 612 and 614 in a service-based architecture. Figure 6 An example is provided showing that the in-DU function 608 performed by CU-CP 602 and / or DU 604 can be performed by eDU 624 (as an example of a network node or radio node) using a cloud-based architecture 626. Figure 6 The example also illustrates that a service-based architecture may include one or more applications 620 and 622.

[0136] For example, a service-based core network and RAN may include a single cloud platform for hosting applications as well as core network and RAN services. The architecture extends the advantages of a service-based architecture to the RAN. The architecture enables benefits associated with cloud-based systems, such as scalability, resilience, robustness, reusability, agility, visibility, automation, and / or protection in failure scenarios. Each service (e.g., 512 or 612) can be scaled independently, and resources can be added or removed for individual services.

[0137] The functional partitioning of the core network and RAN can be adjusted (e.g., as shown at 610) to leverage cloud deployments (e.g., compared to an appliance-centric architecture). Such cloud platforms enable the redistribution of services or functions between the core network and RAN, allowing applications to share a common platform. Cloud-based architectures enable real-time link management at the RAN edge. Adaptation at DUs (e.g., eDUs or radio nodes) enables more efficient activation / deactivation / selection of features based on the anticipated user experience.

[0138] Configuration aspects for performance-sensitive features (e.g., RRC configuration) and activation / deactivation aspects (e.g., MAC layer aspects) can be decoupled from the service-based architecture. Figure 7A It is shown, for example, for such as Figure 5B or Figure 6 In the service-based architecture, the L2 functionality 702 (e.g., RLC and / or MAC functionality) and the PHY layer aspect 704 are separated from services 712, 714, and 716, as illustrated in Figure 700. Protocols can be specialized for each service and can be updated individually. The architecture is adaptable to different vertical domains and deployment types. Different providers or hosts may offer different services.

[0139] Figure 7B Figure 725 illustrates an example of addressing and routing for packet transmission between service 712 and UE 724 via a RAN (e.g., including eDU 722). Although the eDU is illustrated as an example of a radio node, a radio node may also be referred to by other names, such as network node, network entity, or network equipment, etc. Aspects can be applied to, for example, combining... Figure 5B , Figure 6 or Figure 7A The service-based architecture described in various aspects. Figure 7B An example of direct communication between a UE and a wireless network service is illustrated. UE 724 discovers service routing information, which may include, for example, a Uniform Resource Identifier (URI) or a port. The UE marks packets destined for the service with a service address, which may include or be based on an IP address. Packets are served to the service via an end-to-end routing layer from UE 724 to network service 712, for example, by binding access stratum (AS) resources to the uplink (e.g., at the UE) and downlink (e.g., at the eDU). Packet addressing enables transparent routing at eDU 722; for example, the service protocol layer may be transparent to eDU 722. Similarly, when packets are transmitted to UE 724, service 712 marks the packets with the UE address (e.g., the UE's IP address).

[0140] Figure 8A and Figure 8B Figures 800 and 850 illustrate additional example aspects of uplink and downlink packet handling for direct communication between UE 804 and service 812 via eDU 802. Although the eDU is illustrated as an example of a radio node, a radio node may also be referred to by other names, such as network node, network entity, or network equipment, etc. Aspects can be applied to, for example, combinations of... Figure 5B , Figure 6 , Figure 7A or Figure 7B The service-based architecture described in various aspects. Figure 8A An example aspect of uplink packet handling is illustrated. UE 804 is aware of the service URI and / or port of service 812 and binds packets to uplink resources (e.g., access stratum (AS) resources or radio bearers), such as in combination with... Figure 7B As described. Figure 8A AS layer 806 and service protocol layer 810 are illustrated, and routing layer 808 is also illustrated, where packets are associated with the UE address as the source and the service address as the destination. Routing at the eDU is transparent, for example, based on the source and destination addresses at the routing layer.

[0141] Figure 8B A corresponding example of downlink packet handling is illustrated. Serving 812 transmits packets to UE 804, and routing layer 818 is based on the serving address as the source and the UE address as the destination. Routing at eDU 802 is transparent, for example, using routing layer information instead of service protocol layer 814. eDU binds packets to AS downlink resources, such as radio bearers, resulting in AS layer 816, routing layer 818, and service protocol layer 814 for downlink packets.

[0142] Figure 9 Example aspects of an architecture for System Information (SI) generation and delivery in a service-based wireless network are illustrated. These aspects can be applied to, for example, combining... Figure 5B , Figure 6 , Figure 7A , Figure 7B , Figure 8A or Figure 8B The described aspects represent a service-based architecture. SI Service 908 can store and deliver service-specific SIs and / or SIBs for one or more services used in a wireless network. SI Service 908 supports APIs for configuring service-specific SIBs for various services. Figure 9An example of a single service (e.g., service X) is illustrated. However, the network may include any number of services, and the aspects described for service 912 can be applied to any of one or more services that provide system information to SI service 912. Examples of services may include access control services, mobility services, PWS services, V2X services, MBS services, and location services, etc. Service 912 provides service-specific SIs (e.g., service X) to SI service 908, for example, via an API interface of a cloud platform 910 that includes service 912 and SI service 908. For example, the SI may include service-specific SIB configurations for service X. SI service 908 may store SIs received from service 912 and may generate and provide SI messages to UE 902, the SI messages including the SIs from service 912. In some aspects, SI service 908 may manage the delivery mode of SIs to the UE. The delivery mode may be, for example, broadcast, on-demand delivery, and / or download (e.g., on UP). In some respects, SI service 908 may provide delivery information (which may be referred to as a delivery request in some examples) to eDU 906. Although eDU is exemplified as an example of a radio node, a radio node may also be referred to by other names, such as a network node, network entity, or network equipment, etc. SI delivery information 907 may be referred to as SI for SI service, for example. SI service may handle SI updates, for example, based on update information received from various services (e.g., 712) and / or based on adjustments to the delivery of SI.

[0143] The eDU 906 generates radio interface-related information, such as the MIB and / or minimum SI, etc. The eDU 906 supports APIs for service SI radio configuration (e.g., SI delivery information 907). The eDU 906 then provides minimum SI delivery 909 at access layer 904. Minimum SI delivery provides information that enables the UE to obtain other SIs, for example, rather than providing all SIs. For example, the eDU 906 may send minimum SIs for reception by one or more UEs 902. The eDU may also provide service-specific SI delivery (e.g., in broadcast or on-demand transmission) when receiving SIs from SI service 908 for delivery to one or more UEs 902 via access layer 904.

[0144] Figure 10 Example communication flow 1000 is illustrated, in which SI service 1006 collects, stores and generates SI / SIB. Figure 10Example: SI service 1006 may receive service-related SIs 1010 and 1011 from one or more services (e.g., 1008 and 1012). For example, SI 1010 may include SIs related to service 1008, and SI 1011 may include SIs related to service 1012. SI service 1012 may receive SIs 1010 and 1011 from services 1008 and 1012 via an API interface that is part of a cloud-based platform, for example, as in combination. Figure 5B , Figure 6 , Figure 7A , Figure 7B , Figure 8A , Figure 8B or Figure 9 As described in any of the above. In some aspects, one or more of SIs 1010 or 1011 may include an SI update of a previously provided SI. Additionally, SI service 1006 may transmit a request (e.g., via an API interface) to an eDU to request an SI. Although an eDU is illustrated as an example of a radio node, a radio node may also be referred to by other names, such as a network node, network entity, or network equipment, etc. As illustrated, SI service 1006 may transmit such requests (e.g., 1012 and 1014) to one or more eDUs, such as 1002 and 1003. Each eDU 1002 and 1003 responds by providing SI service 1006 with an SI or SIB associated with the corresponding eDU. For example, eDU 1002 provides SI service 1006 with one or more SIBs 1018 associated with eDU 1002. eDU 1003 provides SI service 1006 with one or more SIBs 1016 associated with eDU 1003. SI services collect, store, and manage SIs received from various sources, including one or more services and one or more eDUs. Figure 10 An example is shown where the SI service generates an SI at 1020 based on the SI received from the service and / or eDU.

[0145] The aspects presented herein provide solutions for providing SIs from SI services to one or more UEs, for example, via eDUs or core network services such as ACMS. Examples include delivery mechanisms to UEs with different eDU states (e.g., connected, authenticated, or disconnected). The aspects presented enable more efficient use of radio resources by allowing targeted delivery of SIs / SIBs upon UE request. The aspects allow for independent updates of SIs for different services. The aspects provide greater network control over SIs / SIBs by authenticating or authorizing UE access information before providing SIs / SIBs to the UE. The aspects help save power at the UE by reducing the time the UE spends monitoring system information.

[0146] As an example, a UE can connect to the SI service via UP to download the SI. In this example, the UE may be in a connected and authenticated state with the eDU (e.g., it may be referred to as the eDU state), and the UE may establish and authorize with the SI service. In some aspects, this method of receiving the SI may be referred to as connection-based SI download. In this example, the UE may exchange communications with the SI service to access other services in the wireless network. Figure 12 An example of a UE downloading an SI via UP is shown.

[0147] As another example, a UE can connect to an eDU, which can act as a proxy for the UE to retrieve SIs from the SI service. In this example, the UE can be connected to the eDU or not (e.g., with or without authentication). In this example, the SI service is visible to the eDU but not to the UE, and the eDU can query the SI service for different UEs. In this example, the SI service acts as a service for the eDU, which simplifies how the UE retrieves the SI. For example, the eDU can register the SI service and cache the SIs or retrieve them on each UE request. Figure 13 An example is shown where eDU obtains SI for UE.

[0148] As another example, a network node such as an Access Connection Management Service (ACMS) can query the SI service to obtain an SI for the UE. In this example, the UE may have a connection state with the eDU (e.g., with or without authentication). The SI service is visible to the ACMS, not the UE, which allows the ACMS to request SIs for different UEs. In this example, the SI service acts as a service for the ACMS, which simplifies how the UE retrieves the SI. Figure 14 An example is shown where ACMS obtains the SI for the UE.

[0149] As another example, the UE can query the SI from the eDU. In this example, the UE may be connected to the eDU or not. The UE may not have a connection to or authorization with the SI service. The SI service can provide the requested SI to the eDU before the UE makes a request. As an example, the SI can be provided to the eDU based on a subscription to the SI service (e.g., eDU subscription information). Figure 15 and Figure 16 An example of an eDU receiving an SI from the SI service before the UE requests an SI.

[0150] Figure 11A and Figure 11B Examples of uplink and downlink handling of SI requests and SI delivery for connection-based SI download from SI services are illustrated. Figure 11AFigure 1100 illustrates the processing of an SI request, used for, for example, a connection-based SI download from an SI service via a user plane. Service 1112 may be a cloud-based wireless network service, such as a combination of... Figure 5B , Figure 6 , Figure 7A , Figure 7B , Figure 9 and Figure 10 As described by either of them. The treatment may include, for example, combining Figure 8A This describes any aspect of the uplink handling described in the documentation. UE 1104 is aware of the SI service address and uses a Data Radio Bearer (DRB) to download the SI. For example, the UE may be assigned an IP address (e.g., the UE address) and may be notified of routing information for SI service 1112. The routing information for SI service 1112 may include the IP address of the SI service, the Transmission Control Protocol (TCP) or User Datagram Protocol (UDP) port number, and / or the Fully Qualified Domain Name (FQDN). Since the UE has already established an access connection with the eDU, the UE can use the configured radio bearer (e.g., the DRB for SI download) to transmit requests for the SI. Although the eDU is exemplified as an example of a radio node, a radio node may also be referred to by other names, such as a network node, network entity, or network equipment, etc. The request from the UE is provided in the IP packet from the UE to SI service 1112. Figure 11A Example: AS layer 1106 and service protocol layer 1110 (for requests to SIs or SIBs), and routing layer 1108 for routing at the eDU with the UE address as the source and the SI service address as the destination. For example, the UE can encapsulate requests to one or more SIs and / or one or more SIBs (e.g., with one or more SI indices or SIB indices) into UP packets, setting the destination address based on the SI service routing information and setting the source address to its own IP address. Routing at eDU 1102 is transparent, for example, based on a routing layer using the UE address as the source and the SI service address as the destination.

[0151] Figure 11B Example 1150 illustrates an aspect of SI downloading used to deliver SI as downlink information to the UE. Service 1112 can be a cloud-based wireless network service, such as combining... Figure 5B , Figure 6 , Figure 7A , Figure 7B , Figure 9 and Figure 10 As described by either of them. The treatment may include, for example, combining Figure 8BThis describes any aspect of the downlink handling described in the documentation. SI service 1112 uses routing layer 1118 to transmit the SI to UE 104 based on the SI service address as the source and the UE address as the destination. Routing at eDU 1102 is transparent, for example, using routing layer information instead of service protocol layer 1114 to download the SI. Although eDU is illustrated as an example of a radio node, a radio node may also be referred to by other names, such as a network node, network entity, or network equipment, etc. eDU 1102 provides the SI to UE 1104 via the access layer (e.g., using AS layer 1116) using the DRB for SI download. SI service 1112 may encapsulate one or more requested SIs or SIBs (e.g., based on one or more SI indices or SIB indices indicated by the UE) in one or more IP packets destined for UE 1104. The downloaded SI or SIB is then routed between UE 1104 and SI service 1112 via eDU 1102.

[0152] Figure 12 An example communication flow 1200 for connection-based SI download from an SI service is illustrated. Packet handling may include combining... Figure 11A and / or Figure 11B Any aspect described. eDU 1202, SI service 1206, service 1208, and authorized service 1210 can be part of a service-based architecture in a cloud-based wireless network, and may include combinations Figure 5B , Figure 6 , Figure 7A , Figure 7B , Figure 8A , Figure 8B , Figure 9 , Figure 10 The aspects described in either of Figure 11. Although the eDU is illustrated as an example of a radio node, a radio node may also be referred to by other names, such as a network node, network entity, or network equipment, etc.

[0153] At 1212, service 1208 provides SI input 1212 to the SI service. Although a single service is illustrated, SI service 1206 can receive SI input from any number of services in the wireless network. Each service (e.g., as represented by 1208) provides an SI corresponding to that specific service. For example, Figure 10Examples of services that provide a specific SI to an SI service are illustrated. Examples of services (e.g., 1208) may include access control services, mobility services, PWS services, V2X services, MBS services, and / or location services, etc. As an example, service 1208 may correspond to a service that requests SI delivery by the SI service. By providing the SI to the SI service, SI service 1206 can then manage individual delivery to the UE. SI input 1212 may include, for example, any of the following: the SI content of the service, the service's range area, periodicity, value tag, authorization requirements for accessing the service, and / or aspects related to authentication of the service. For example, SI input 1212 may be provided by service 1208 to SI service 1206 via an API interface.

[0154] At 1214, SI service 1206 transmits scheduling information 1214 to eDU 1202. The scheduling information may indicate system information enabling the UE to access the SI service to obtain a reduced amount of other SIs. For example, scheduling information 1214 may indicate the range area of ​​SI service 1206 and / or the delivery mode for obtaining SIs from SI service 1206. For example, the scheduling information may indicate that the delivery mode for obtaining SIs is via download from the SI service, and may indicate a service ID (e.g., SI service ID).

[0155] As shown at 1216, eDU 1202 may provide (e.g., send) a reduced amount of SI (which may be referred to as minimum SI 1216 or other names), which may include the SI service ID (e.g., received by eDU 1202 from SI service 1206) and scheduling information of SI service 1206. For example, minimum SI 1216 may indicate the delivery mode of the SI, such as broadcast, on-demand, and / or download. In some aspects, the indication of the delivery mode may be per SIB or per SI. For example, minimum SI 1216 may indicate different delivery modes for different SIs or different SIBs. For example, minimum SI 1216 may include scheduling information 1214 provided by SI service 1206. In some aspects, eDU 1202 may send scheduling information in SIB1.

[0156] If UE 1204 does not yet have the SI routing information of SI service 1206, then the UE can obtain the SI routing information. The UE can obtain the SI routing information in any of a variety of ways. As shown at 1218, UE 1204 can also be authorized and authenticated by the authorization service 1210 as part of obtaining the SI routing information.

[0157] In some respects, as part of obtaining SI routing information, UE 1204 can establish a PDU session and can be assigned an IP address (e.g., for the UE). SI routing information for SI service 1206 can also be provided to the UE. During PDU session establishment, UE 1204 can request the establishment of a service ID (e.g., the SI service ID received in minimum SI 1216).

[0158] In some respects, UE 1204 may obtain SI routing information, for example, from the discovery service. The UE may send a query message to the discovery service including the SI ID (received in the minimum SI). The discovery service responds to the UE's query message by transmitting the routing information of SI service 1206 based on the SI ID indicated in the UE's query.

[0159] In some respects, UE 1204 can be pre-configured using SI routing information, or it can receive configuration including SI routing information from the network. As an example, SI routing information can be provided to the UE by the network in UE policies or configurations. The network providing the SI routing information can be a core network, such as a 6G core network, etc.

[0160] In some respects, UE 1204 can obtain SI routing information from system information (e.g., in minimum SI 1216).

[0161] In some respects, UE 1204 may construct (e.g., determine or generate) the UE’s FQDN based on some information received in the minimum SI 1216, such as PLMN ID, Tracking Area Code (TAC) or SI Service ID.

[0162] After obtaining SI routing information, UE 1204 transmits (e.g., sends) IP packet 1220, which requests one or more SIs or multiple SIBs from SI service 1206. The IP packet may include combinations of... Figure 11A The described aspects. SI or SIB can be used for one or more specific services (e.g., including service 1208). eDU 1202 routes IP packets to SI service 1206, as in combination. Figure 11A As described. SI service 1206 responds to a request from UE 1204 by transmitting one or more IP packets 1222 including one or more requested SIs or SIBs. IP packet 1222 may include, for example, combinations of... Figure 11B The SI delivery described in the text.

[0163] like Figure 11A , Figure 11B and Figure 12As illustrated in the example, the UE can request system information from the SI service using IP packets, and the SI service can encapsulate the SI or SIB payload using one or more IP packets when transmitting the SI to the UE. Combined with... Figure 12 It also provides a mechanism that enables the UE to obtain the SI service address or other SI routing information. Combined with Figure 12 The described aspects also enable the UE to be identified, authenticated, and / or authorized for access to the SI.

[0164] By requesting and receiving SI / SIBs in IP packets, exchange can occur between UE 1204 and SI service 1206 without a control plane. For example, UE 1204 may have an eDU access connection, but there is no control plane between the UE and the SI service. This is achieved by enabling authentication and authorization of the requested SI or SIB, combined with... Figure 12 The various aspects presented allow for improved security and increased network control over SI access. Figure 12 The aspects presented herein save radio resources and achieve increased system efficiency with reduced system overhead. For example, SIs can be provided in response to UE requests, rather than reserving resource windows for periodic SI broadcasts. More efficient delivery allows for an increase in the maximum number of SIs or SIBs. Delivery in response to UE requests enables finer-grained control over SIs, such as enabling independent updates of SIs for different services. The aspects presented herein also reduce UE power consumption because the UE can request SIs and skip monitoring of periodic SI broadcasts.

[0165] exist Figure 12 In some examples, UE 1204 may already have an access connection with eDU 1202. In some aspects, SI service 1206 may transmit UE-specific SIBs to UE 1204, such as V2X SIB, MBSSIB, etc.

[0166] Figure 13 An example communication flow 1300 illustrating an API-based SI retrieval process is provided, in which UE 1304 receives an SI from eDU 1302. Although the eDU is illustrated as an example of a radio node, a radio node may also be referred to by other names, such as a network node, network entity, or network equipment, etc. eDU 1302, SI service 1306, and authorized service 1310 can be part of a service-based architecture in a cloud-based wireless network and may include combinations of... Figure 5B , Figure 6 , Figure 7A , Figure 7B , Figure 8A , Figure 8B , Figure 9 or Figure 10Any aspect described in the above. For example, UE 1304 may connect to eDU 1302, which then acts as a proxy for UE 1304 to retrieve SI for UE 1304 from SI service 1306. In this example, UE 1304 may be connected to the eDU or not (e.g., with or without authentication). In this example, the SI service may be visible to eDU 1302 but not to UE 1304. Although only a single UE 1304 and a single service 1308 are illustrated, Figure 13 The concepts presented herein can be applied to any number of UEs served by eDU 1202 and any number of services 1208 in the wireless network. For example, eDU 1202 can query SI services 1206 for different UEs. In this example, SI service 1206 can be considered as acting as a service for eDU 1202 (e.g., not for UE 1204), which simplifies how UE 1204 retrieves SIs. For example, eDU can register SI services and cache SIs or retrieve SIs on each UE request.

[0167] At 1312, the SI can be obtained by SI service 1206 and prepared for delivery to the UE. For example, SI generation at 1312 may include combining... Figure 9 , Figure 10 or Figure 12 The SI input 1212 describes any one of the aspects.

[0168] UE 1304 can receive SIB or SI scheduling information in the minimum SI 1314. In some aspects, the scheduling information may indicate whether one or more SIs or SIBs can be downloaded from SI service 1306. For example, SI service 1306 may be identified by an SI service ID. In some aspects, eDU 1302 can subscribe to SI service 1306.

[0169] At 1316, UE 1304 transmits (e.g., sends) a request 1316 for an SI to eDU 1302. In some aspects, such as for a UE in an RRC idle state, the request may include a UE ID. Request 1316 may request one or more SIs or SIBs, and may include one or more indices (e.g., SI index or SIB index) of the requested SI / SIB. In some aspects, request 1316 may include an SI service ID identifying the SI service 1306 from which the UE is requesting system information.

[0170] In some respects, if UE 1304 is in an RRC idle or RRC inactive state, UE 1304 may use the configured uplink resources (e.g., configured frequency resources, time resources, and / or preamble resources) indicated in minimum SI1314 to transmit request 1316. As an example, request 1316 may be included in a random access message, such as MSG 1.

[0171] In response to receiving a request from UE 1304, eDU 1302 retrieves the requested SIB / SI from SI service 1306. As an example, eDU 1302 may obtain or receive system information (e.g., one or more requested SIs or SIBs) from SI service 1306 via an API interface. Figure 13 An example is shown where eDU 1302 can transmit request 1318 (e.g., via API), which requests a set of one or more SIs or SIBs for a UE. Request 1318 from eDU 1302 may include an indication of one or more SI or SIB indices indicated in request 1316 from the UE. In some aspects, request 1318 may indicate the UE for which the request is being made, such as the UE ID.

[0172] In some respects, prior to responding to a request from an eDU, SI service 1306 may utilize authorization and authentication services (e.g., 1310) to trigger the UE authorization and / or authentication process.

[0173] As illustrated at 1322, SI service 1306 may respond to request 1318 from eDU 1302 by transmitting one or more requested SIs or SIBs identified in request 1318. For example, similar to request 1318, SIs / SIBs may be provided to eDU 1302 via an API interface. eDU 1302 receives the requested one or more SIs or SIBs and transmits (e.g., sends) an SI container to the UE, which includes the requested one or more SIs or SIBs. The UE receives the SI / SIBs in message 1324 of eDU 1302. In some aspects, message 1324 may indicate the UE ID. In some aspects, message 1324 may indicate the SI service ID of SI service 1306 from which system information is obtained. In the example where the UE may transmit request 1316 in random access MSG1, eDU 1302 may respond to the UE's request by transmitting the requested system information (e.g., SI / SIB) in random access MSG2. In some respects, MSG2 may use the UE’s Radio Network Temporary Identifier (RNTI).

[0174] Figure 13The various aspects presented herein save radio resources and achieve increased system efficiency with reduced system overhead. For example, SIs can be provided via eDU in response to UE requests, instead of reserving resource windows for periodic SI broadcasts. More efficient delivery allows for an increase in the maximum number of SIs or SIBs. Delivery in response to UE requests enables finer-grained control over SIs, such as enabling independent updates of SIs for different services. The aspects presented herein also reduce UE power consumption because the UE can request SIs and skip monitoring of periodic SI broadcasts. This is achieved by enabling authentication and authorization of requested SIs or SIBs at 1320, combined with... Figure 13 The various aspects presented also allow for improved security and increased network control over SI access.

[0175] Figure 14 An example communication flow 1400 is illustrated for API-based SI retrieval from core network services such as ACMS 1408. eDU 1402, SI service 1406, and ACMS 1408 can be part of a service-based architecture in a cloud-based wireless network and may include combinations of... Figure 5B , Figure 6 , Figure 7A , Figure 7B , Figure 8A , Figure 8B , Figure 9 or Figure 10 Any aspect described in the text. Although the eDU is illustrated as an example of a radio node, a radio node can also be referred to by other names, such as a network node, network entity, or network equipment, etc. ACMS 1408 can query SI service 1406 to obtain an SI for UE 1404. In this example, the UE may have a connection status with eDU 1402 (e.g., with or without authentication). SI service 1406 is visible to ACMS 1408 but not to UE 1404. Although this concept is illustrated for a single UE 1404, Figure 14 This also enables ACMS 1408 to request SIs for different UEs. In this example, SI service 1406 can be considered as acting as a service of ACMS 1408. This simplifies how UE 1404 retrieves SIs. In this example, UE 1404 can request SI downloads via the control plane (e.g., via the NAS layer).

[0176] At 1409, the SI can be obtained from SI service 1306 and prepared for delivery to the UE. For example, SI generation at 1409 may include combining... Figure 9 , Figure 10 or Figure 12 The SI input 1212 describes any one of the aspects.

[0177] UE 1404 may receive SIB or SI scheduling information in minimum SI 1410. In some aspects, the scheduling information may indicate whether one or more SIs or SIBs can be downloaded from SI service 1406 via the control plane (e.g., NAS layer). Minimum SI 1410 may include aspects such as those described in combination with 1216 or 1314.

[0178] At 1414, UE 1404 transmits (e.g., sends) a NAS message to ACMS 1408 containing a request 1416 for an SI. As illustrated at 1412, in some aspects, UE 1404 may establish eDU access with eDU 1402 before transmitting request 1414. Request 1414 may include one or more indices of the requested SI / SIB (e.g., SI index or SIB index). In response to receiving request 1414, ACMS 1408 transmits the requested SI / SIB index and UE ID of UE 1404 to SI service 1406. For example, ACMS 1408 may transmit request 1416 for SI / SIB via an API interface. In some aspects, UE ID may be, for example, a Subscription Persistent Identifier (SUPI) or a General Public Subscription Identifier (GPSI).

[0179] SI service 1406 responds to request 1416 from ACMS 1408 by transmitting one or more requested SIs or SIBs identified in request 1416. For example, SI service 1406 may transmit SIs / SIBs in an SIB or SI container 1420 via an API interface. SI container 1420 may be included in the NAS message.

[0180] In some respects, SI service 1406 may perform an authorization process at 1418 to determine whether the UE is authorized to download the requested system information before transmitting the SI container 1422, which includes the requested SI / SIB.

[0181] Figure 14 The various aspects presented herein save radio resources and achieve increased system efficiency with reduced system overhead. For example, SIs can be provided via ACMS in response to UE requests, instead of reserving resource windows for periodic SI broadcasts. More efficient delivery allows for an increase in the maximum number of SIs or SIBs. Delivery in response to UE requests enables finer-grained control over SIs, such as independently updating SIs for different services. The aspects presented herein also reduce UE power consumption because the UE can request SIs and skip monitoring of periodic SI broadcasts. By enabling authorization of requested SIs or SIBs at 1418, combined with... Figure 14 The various aspects presented also allow for improved security and increased network control over SI access.

[0182] Figure 15 An example communication flow 1500 for obtaining SI / SIB from an eDU is illustrated. Although the eDU is illustrated as an example of a radio node, a radio node may also be referred to by other names, such as a network node, network entity, or network equipment, etc. Obtaining may be based on unicast delivery of SI / SIB from the eDU. eDU 1502, SI service 1506, and services 1508 and 1509 may be part of a service-based architecture in a cloud-based wireless network and may include combinations of... Figure 5B , Figure 6 , Figure 7A , Figure 7B , Figure 8A , Figure 8B , Figure 9 or Figure 10 Each of the aspects described in the text. Although this concept is illustrated for a single UE 1504, Figure 15 It is applicable to any number of UEs.

[0183] As shown at 1510 and 1512, the SI can be obtained from SI service 1506. For example, SI service 1506 can generate combinations such as Figure 9 , Figure 10 or Figure 12 The SI described by SI input 1212 in the text. eDU 1502 can provide a minimum SI 1516 with scheduling information about the SI obtained from SI service 1506, for example, as combined with Figures 12 to 14 The smallest SI among them is described.

[0184] exist Figure 15 In the example, UE 1504 can query SI from eDU 1502. In Figure 15 In this scenario, UE 1504 is in a connected state and has already established a connection with eDU 1502 at 1518 before requesting system information. UE 1504 may not have a connection to SI service 1506 or may not be authorized to use SI service 1506. SI service 1506 may provide the requested SI to eDU 1502 at 1514 before the UE issues a request at 1520. As an example, SI may be provided to eDU 1502 based on a subscription to SI service 1506 (e.g., eDU subscription information).

[0185] UE 1504 sends a request 1520 to eDU 1502 for one or more SIs or SIBs, and eDU 1502 responds to request 1520 by transmitting (e.g., sending) the requested SIB / SI to UE 1504. In this example, the UE has an eDU access connection, such as an established radio bearer, and the UE may indicate the requested SIB / SI index in an L2 PDU (e.g., in a MAC CE). Therefore, request 1520 may be a MAC-CE or L2 PDU indicating one or more SI or SIB indexes that UE 1504 is requesting. At 1522, the eDU delivers the requested system information (e.g., SI / SIB) via the established radio bearer. In some aspects, UE 1504 may use a default (e.g., specified) radio bearer or a configured radio bearer to transmit request 1520 to request system information.

[0186] SI service 1506 can determine the SIB / SI delivered by eDU 1502 and can transmit the SIB / SI to eDU 1502 at 1514. SI service 1506 can also transmit scheduling information to eDU 1502, for example, at 1514 or in a separate message. The scheduling information can indicate one or more SIBs or SIs that the UE can obtain from eDU 1502. eDU 1502 can then provide similar information in minimum SI 1516, for example, indicating one or more SIBs or SIs that the UE can request from eDU 1502.

[0187] Figure 15 The various aspects presented herein save radio resources and achieve increased system efficiency with reduced system overhead. For example, SIs can be provided in response to UE requests, rather than reserving resource windows for periodic SI broadcasts. More efficient delivery allows for an increase in the maximum number of SIs or SIBs. Delivery in response to UE requests enables finer-grained control over SIs, such as allowing independent updates of SIs for different services. The aspects presented in this paper also reduce UE power consumption because the UE can request SIs and skip monitoring of periodic SI broadcasts. Figure 15 The presentation also allows for faster delivery of system information, since the system information is already stored at eDU 1502 when a request is received from UE 1604.

[0188] Figure 16 Examples similar to Figure 15Example communication procedure 1600 for obtaining SI / SIB from eDU, but for UE 1604 which has not established a connection to eDU 1602. Although eDU is illustrated as an example of a radio node, a radio node may also be referred to by other names, such as network node, network entity, or network equipment, etc. For example, as shown at 1618, the UE may be in an RRC idle or inactive state. Obtaining may be based on unicast delivery of SI / SIB from eDU. eDU 1602, SI service 1606, and services 1608 and 1609 may be part of a service-based architecture in a cloud-based wireless network and may include combinations Figure 5B , Figure 6 , Figure 7A , Figure 7B , Figure 8A , Figure 8B , Figure 9 or Figure 10 Each of the aspects described in the text. Although this concept is illustrated for a single UE 1604, Figure 16 It is applicable to any number of UEs.

[0189] As shown at 1610 and 1612, the SI can be obtained from SI service 1606. For example, SI service 1506 can generate combinations such as Figure 9 , Figure 10 or Figure 12 The SI described by SI input 1212 in the text. eDU 1602 can provide a minimum SI 1616 with scheduling information about the SI obtained from SI service 1606, for example, as combined with Figures 12 to 14 The smallest SI among them is described.

[0190] exist Figure 16 In the example, UE 1604 can query the SI from eDU 1602. UE 1604 does not have a connection to SI service 1606 or is not authorized to SI service 1506. SI service 1606 can provide the requested SI to eDU 1602 at 1614 before the UE issues a request 1620. As an example, the SI can be provided to eDU 1502 based on a subscription to SI service 1606 (e.g., eDU subscription information).

[0191] UE 1604 sends a request 1614 to eDU 1602 for one or more SIs or SIBs, and eDU 1602 responds to request 1620 by transmitting (e.g., sending) the requested SIB / SI to UE 1604.

[0192] In this example, the UE is in an idle or inactive state (e.g., an RRC idle or RRC inactive state with no connection established). UE 1604 may transmit a request for one or more SIs or SIBs to eDU 1602 in a PDU (e.g., an SIB / SI request PDU). The PDU may be an L2 PDU and may include the UE ID of UE 1604 and the index of one or more SIs or SIBs requested by UE 1604. In some aspects, the PDU may be included, for example, in a MAC-CE message from UE 1604.

[0193] At 1624, the eDU delivers the requested system information (e.g., SI / SIB). eDU 1602 may include one or more requested SIBs in the L2 PDU transmitted from eDU 1602 to UE 1604.

[0194] As an example, in the RRC idle or RRC inactive state, UE 1604 can send a request along with a preamble, and eDU 1602 can respond by transmitting the requested SI / SIB and preamble.

[0195] Figure 16 The various aspects presented herein save radio resources and achieve increased system efficiency with reduced system overhead. For example, SIs can be provided in response to UE requests, rather than reserving resource windows for periodic SI broadcasts. More efficient delivery allows for an increase in the maximum number of SIs or SIBs. Delivery in response to UE requests enables finer-grained control over SIs, such as allowing independent updates of SIs for different services. The aspects presented in this paper also reduce UE power consumption because the UE can request SIs and skip monitoring of periodic SI broadcasts. Figure 16 The presentation also allows for faster delivery of system information, since the system information is already stored in eDU 1602 when a request is received from UE 1604.

[0196] Figure 17This is a flowchart 1700 of a wireless communication method. The method can be performed by a UE (e.g., UE 104, 204, 450, 724, 804, 902, 1104, 1204, 1304, 1404, 1504, 1604; device 2204). By enabling authentication and authorization of the requested SI or SIB, aspects of the method allow for improved security and increased network control over SI access. These aspects conserve radio resources and achieve increased system efficiency with reduced system overhead. For example, SIs can be provided in response to UE requests, rather than reserving resource windows for periodic SI broadcasts. More efficient delivery allows for an increase in the maximum number of SIs or SIBs. Delivery in response to UE requests enables finer-grained control over SIs, such as enabling independent updates of SIs for different services. The aspects presented herein also reduce UE power consumption because the UE can request SIs and skip monitoring of periodic SI broadcasts.

[0197] At 1702, the UE sends a request to the network node for system information associated with the system information service of the wireless network. Figures 12 to 16 Various examples of a UE sending a request for system information associated with the SI service are illustrated. For example, the sending may be performed by, for example, the system information component 198 of device 2204. In some aspects, the UE's request includes a first Internet Protocol (IP) packet that includes the UE's source IP address and the destination IP address of the system information service, and wherein the system information is received in a second IP packet encapsulating the system information. Figure 12 An example is illustrated where the UE may encapsulate a request in an IP packet. In some aspects, the UE also establishes a Protocol Data Unit (PDU) session before making the request. In some aspects, the UE's request is directed to one or more radio nodes and includes one or more of the following: the UE's first identifier (ID), the service ID of the system information service, or the system information index. Figure 13 , Figure 14 and Figure 15 An example is shown in which the UE directs the request to the eDU or ACMS.

[0198] In some aspects, prior to sending a request, the UE also receives initial system information indicating the service identifier of the system information service and the delivery mode of the system information. For example, receiving may be performed by, for example, the system information component 198 of device 2204. In some aspects, the initial system information indicates the delivery mode of the system information based on one or more of the following: broadcast, on-demand download, download via user plane, download for each system information or system information block (SIB), download from the system information service, download via radio node, or download via Access Connection Management Service (ACMS).

[0199] In some aspects, the UE also obtains routing information for the system information service from one or more of the following: service discovery, previously configured SI routing information, or minimum system information. In some aspects, the UE may also generate the fully qualified domain name (FQDN) for the system information service based on one or more of the Public Land Mobile Network Identifier (PLMN ID), Tracking Area Code (TAC), and Service Identifier (ID) of the system information service. In some aspects, the UE may also receive minimum system information indicating the Service ID of the system information service from one or more radio nodes.

[0200] At 1704, the UE receives system information from the system information service of the wireless network via a network node. For example, reception may be performed by system information component 198 of device 2204. In some aspects, the system information is located in a message or system information container from the radio node. In some aspects, the request is located in a first random access message, and the system information is included in a second random access message. In some aspects, the UE's request is included in a first non-access stratum (NAS) message directed to the Access Connection Management Service (ACMS) and indicating a system information index, wherein the system information is received in a second NAS message from the ACMS, which encapsulates the system information indicated by the system information index. In some aspects, the UE's request is included in a first protocol data unit (PDU) directed to the radio node, wherein the system information is received in a second PDU from the radio node.

[0201] In some respects, the UE has an access connection with a radio node, wherein the request is included in a Layer 2 (L2) PDU to the radio node, and wherein system information is included in a response L2 PDU from the radio node. Figure 15 An example is illustrated where a UE with an access connection requests inclusion in an L2 PDU. In some cases, the UE does not have an established connection with a radio node, and the request is included in a System Information Block (SIB) or System Information (SI) Request PDU destined for the radio node, and the system information is included in a Layer 2 (L2) PDU from the radio node. Figure 16 An example is shown in which a UE without access connectivity requests to be included in an L2 PDU.

[0202] In some respects, the UE also exchanges communications via wireless networks based on system information associated with system information services.

[0203] Figure 18This is a flowchart 1800 of a wireless communication method. The method can be executed by a network node, which can be a base station or a component of a base station (e.g., base stations 102, 202, 410; CU 106, DU 105, 230; RU 109, 240; eDU 171, 524, 624, 722, t802, 906, 1002, 1003, 1102, 1202, 1302, 1402, 1502; ACMS 1408; network entities 2302, 2560). By enabling authentication and authorization of the requested SI or SIB, aspects of the method allow for improved security and increased network control over SI access. Aspects save radio resources and achieve increased system efficiency with reduced system overhead. For example, SIs can be provided in response to UE requests, rather than reserving resource windows for periodic SI broadcasts. More efficient delivery allows for an increase in the maximum number of SIs or SIBs. The delivery of SIs in response to UE requests enables finer-grained control, such as allowing independent updates of SIs for different services. The aspects presented in this paper also reduce UE power consumption because the UE can request SIs and skip monitoring of periodic SI broadcasts.

[0204] At position 1802, the network node receives the UE's request for system information. Figures 12 to 16 Examples of various scenarios illustrate how a network node obtains (e.g., receives) a UE's request for system information. For example, the request may be obtained by the system information component 199 of network entity 2302. In some aspects, the UE's request includes a first IP packet containing the UE's source IP address and the destination IP address of the system information service, with the system information contained in a second IP packet encapsulating the system information. In some aspects, the network node is a radio node, the UE's request is directed to the radio node, and includes one or more of the following: the UE's UE ID, the system information service's service ID, or the system information index. In some aspects, the network node includes an Access Connection Management Service (ACMS), and the UE's request is included in a first Non-Access Stratum (NAS) message directed to the ACMS.

[0205] At 1804, the network node provides a request for system information to the system information service of the wireless network. For example, the request may be provided by the system information component 199 of network entity 2302. In some aspects, providing a request to the system information service includes providing a first IP packet to the system information service. In some aspects, the network node is a radio node, the UE's request is directed to the radio node and includes one or more of the following: the UE's UE ID, the service ID of the system information service, or the system information index, and providing a request for system information to the system information service includes transmitting an additional request indicating one or more of the UE ID or the system information index to the system information service.

[0206] At 1806, the network node responds to a request to receive system information from the system information service. For example, the system information may be obtained by the system information component 199 of network entity 2302. Figure 12 , Figure 13 and Figure 14 Various examples of network nodes that receive system information from the SI service are illustrated.

[0207] At point 1808, the network node provides system information from the system information service to the UE. For example, the system information may be provided by the system information component 199 of network entity 2302. In some aspects, the network node may send system information from the SI service to the UE. Figures 12 to 16 Examples of network nodes providing (e.g., sending) system information to a UE in response to a request are illustrated. In some aspects, the system information is contained in a second IP packet encapsulating the system information. In some aspects, the system information is contained in a message to the UE from a radio node, a system information container, or a random access message. In some aspects, the network node includes an Access Connection Management Service (ACMS), and the UE's request is included in a first Non-Access Stratum (NAS) message directed to the ACMS and indicating a system information index, and the system information is provided in a second NAS message from the ACMS, which encapsulates the system information indicated by the system information index.

[0208] In some respects, prior to a request, network nodes also provide initial system information, including a service identifier indicating the system information service and the delivery mode of the system information. For example, Figures 12 to 16 An example is shown in which a network node can provide a minimum SI to the UE before the SI request from the UE.

[0209] Figure 19This is a flowchart 1900 of a wireless communication method. The method can be executed by a network node, which can be a base station or a component of a base station (e.g., base stations 102, 202, 410; CU 106, DU 105, 230; RU 109, 240; eDU 171, 524, 624, 722, t802, 906, 1002, 1003, 1102, 1502; network entities 2302, 2560). By enabling authentication and authorization of the requested SI or SIB, aspects of the method allow for improved security and increased network control over SI access. Aspects save radio resources and achieve increased system efficiency with reduced system overhead. For example, SIs can be provided in response to UE requests, rather than reserving resource windows for periodic broadcasts of SIs. More efficient delivery allows for an increase in the maximum number of SIs or SIBs. Delivery in response to UE requests enables finer-grained control over SIs, such as enabling independent updates of SIs for different services. The aspects presented in this article can also reduce UE power consumption, because the UE can request SI and skip monitoring of periodic SI broadcasts.

[0210] At point 1902, the network node obtains system information from the system information service. For example, the system information may be obtained from the system information component 199 of network entity 2302. Figure 15 and Figure 16 An example of a network node (e.g., an eDU) that obtains system information from the SI service is shown.

[0211] At 1904, the network node receives the UE's request for system information. In some aspects, the network node may receive the request from the UE. For example, the request may be obtained by the system information component 199 of network entity 2302. Figure 15 and Figure 16 An example is illustrated where a network node (e.g., an eDU) receives a request for system information (e.g., one or more SIs or SIBs) from a UE.

[0212] At 1906, a network node may provide system information to the UE in response to a request, wherein the system information is obtained from a system information service prior to the request (e.g., previously obtained). In some aspects, a network node may send system information to the UE in response to a request. For example, the system information may be provided by the system information component 199 of network entity 2302. Figure 15 and Figure 16 An example is illustrated where a network node (e.g., an eDU) responds to a UE request by providing system information (e.g., one or more SIs or SIBs). Because the eDU already possesses the system information, such as stored system information, it can provide the system information to the UE more quickly in response to the UE's request.

[0213] In some respects, the techniques described herein relate to a method in which the network node is a radio node, and wherein a request from a UE is included in a first Protocol Data Unit (PDU) directed to the radio node, and system information is located in a second PDU from the radio node to the UE.

[0214] In some respects, the techniques described herein relate to a method in which a radio node has a connection with a UE, and a request is included in a Layer 2 (L2) PDU destined for the radio node, and system information is included in a response L2 PDU from the radio node. Figure 15 An example aspect of a UE that has a connection to an eDU is illustrated.

[0215] In some cases, the radio node does not have a connection established with the UE, and the request is included in the SIB or SI request PDU destined for the radio node, while system information is included in the L2 PDU from the radio node. For example, the UE may be in an RRC idle or inactive state. The UE may not have established a connection yet; for example, the UE may request SI / SIB while performing initial access to the cell. Figure 16 An example aspect is illustrated for a UE that does not have a connection to the eDU (e.g., is in an RRC idle or RRC inactive state).

[0216] Figure 20 This is a flowchart 2000 of a wireless communication method. The method can be performed by system information services (e.g., SI services 173, 908, 1006, 1112, 1206, 1306, 1406, 1506, 1606; services 512, 612, 712, 812; network entity 2560) in a service-based wireless network. By enabling authentication and authorization of the requested SI or SIB, aspects of the method allow for improved security and increased network control over SI access. These aspects conserve radio resources and achieve increased system efficiency with reduced system overhead. For example, SIs can be provided in response to UE requests, rather than reserving resource windows for periodic SI broadcasts. More efficient delivery allows for an increase in the maximum number of SIs or SIBs. Delivery in response to UE requests enables finer-grained control over SIs, such as enabling independent updates of SIs for different services. The aspects presented herein also reduce UE power consumption because the UE can request SIs and skip monitoring of periodic SI broadcasts.

[0217] At 2002, the System Information Service receives requests for system information from UEs served by network nodes. For example, this reception may be performed by the System Information Component 191 of network entity 2560. In some aspects, the request is included in a first Internet Protocol (IP) packet of the UE and includes the UE's source IP address and the System Information Service's destination IP address. In some aspects, the network node is a serving radio node serving the UE, and the request originates from the serving radio node and includes one or more of the following: the UE's UE identifier (ID), the System Information Service's service ID, and the System Information Index. In some aspects, the network node includes an Access Connection Management Service (ACMS), where the request originates from the ACMS and indicates the UE identifier. In some aspects, the UE identifier may be a Subscription Permanent Identifier (SUPI) or a General Public Subscriber Identifier (GPSI). For example, Figure 12 , Figure 13 and Figure 14 An example of an SI service receiving requests for SI is shown.

[0218] At 2004, the system information service responds to a request by providing system information to the network node serving the UE. For example, this provision can be performed by the system information component 191 of network entity 2560. In some aspects, the system information is provided in a second IP packet that encapsulates the system information from the system information service. For example, Figure 12 , Figure 13 and Figure 14 An example of providing SI services to network nodes is shown.

[0219] In some respects, the system information service also obtains system information from one or more of the services of the wireless network or from the radio nodes of the wireless network. For example, obtaining this information may be performed by the system information component 191 of network entity 2560.

[0220] In some respects, before providing system information to the serving radio node in response to a request, the system information service also uses the authorization service to perform at least one of authorization or authentication on the UE.

[0221] In some respects, before providing system information to ACMS in response to a request, the system information service also uses the authorization service to perform at least one of authorization or authentication on the UE.

[0222] Figure 21This is a flowchart 2100 of a wireless communication method. The method can be performed by system information services (e.g., SI services 173, 908, 1006, 1112, 1206, 1306, 1406, 1506, 1606; services 512, 612, 712, 812; network entity 2560) in a service-based wireless network. By enabling authentication and authorization of the requested SI or SIB, aspects of the method allow for improved security and increased network control over SI access. These aspects conserve radio resources and achieve increased system efficiency with reduced system overhead. For example, SIs can be provided in response to UE requests, rather than reserving resource windows for periodic SI broadcasts. More efficient delivery allows for an increase in the maximum number of SIs or SIBs. Delivery in response to UE requests enables finer-grained control over SIs, such as enabling independent updates of SIs for different services. The aspects presented herein also reduce UE power consumption because the UE can request SIs and skip monitoring of periodic SI broadcasts.

[0223] At 2102, the system information service obtains system information from one or more of the services of the wireless network or from the radio nodes of the wireless network. In some aspects, the radio node may be an eDU or a DU. As an example, the radio node may provide messages or signaling to one or more UEs. For example, obtaining this information may be performed by the system information component 191 of network entity 2560. Figure 15 and Figure 16 An example of an SI service that receives system information from a service or radio node (e.g., an eDU) is illustrated.

[0224] At 2104, the system information service provides system information to one or more network nodes. For example, this provision can be performed by the system information component 191 of network entity 2560. Figure 15 and Figure 16 Examples of SI services that provide system information to services (e.g., ACMS) or radio nodes (e.g., eDU) are illustrated.

[0225] In some respects, the system information service can also provide scheduling information to the radio nodes for system information to be obtained from them.

[0226] Figure 22Figure 2200 illustrates an example of a specific hardware implementation for device 2204. Device 2204 may be a UE, a component of a UE, or implement UE functionality. In some aspects, device 2204 may include at least one cellular baseband processor 2224 (also referred to as a modem or processor circuit) coupled to one or more transceivers 2222 (e.g., cellular RF transceivers). Cellular baseband processor 2224 may include at least one on-chip memory 2224' (or memory circuit). In some aspects, device 2204 may also include one or more Subscriber Identity Module (SIM) cards 2220 and at least one application processor 2206 (or processor circuit) coupled to a Secure Digital Card (SD) card 2208 and a screen 2210. Application processor 2206 may include on-chip memory 2206' (or memory circuit). In some aspects, device 2204 may also include a Bluetooth module 2212, a WLAN module 2214, an SPS module 2216 (e.g., a GNSS module), one or more sensor modules 2218 (e.g., an atmospheric pressure sensor / altimeter; motion sensors such as an inertial measurement unit (IMU), a gyroscope, and / or an accelerometer; light detection and ranging (LIDAR), radio-assisted detection and ranging (RADAR), sound navigation and ranging (SONAR), a magnetometer, audio, and / or other technologies for positioning), an additional memory module (e.g., 2226), a power supply 2230, and / or a camera 2232. Bluetooth module 2212, WLAN module 2214, and SPS module 2216 may include an on-chip transceiver (TRX) (or in some cases, only a receiver (RX)). Bluetooth module 2212, WLAN module 2214, and SPS module 2216 may include their own dedicated antennas and / or communicate using antenna 2280. Cellular baseband processor 2224 communicates with UE 104 and / or network entity 2202 (e.g., an RU or eDU associated with network entity 2202) via transceiver 2222 through one or more antennas 2280, for example, to obtain SI from SI service 2250. Cellular baseband processor 2224 and application processor 2206 may each include computer-readable media / memory 2224', 2206' respectively. Additional memory modules (e.g., 2226) may also be considered as computer-readable media / memory. Each computer-readable media / memory 2224', 2206', 2226 may be non-transitory. Cellular baseband processor 2224 and application processor 2206 are each responsible for general processing, including the execution of software stored on the computer-readable media / memory. When executed by cellular baseband processor 2224 / application processor 2206, the software causes cellular baseband processor 2224 / application processor 2206 to perform the various functions described above.Cellular baseband processor 2224 and application processor 2206 are configured to perform the various functions described above, at least in part, based on information stored in memory. That is, cellular baseband processor 2224 and application processor 2206 can be configured to perform a first subset of the various functions described above without information stored in memory, and can be configured to perform a second subset of the various functions described above based on information stored in memory. The computer-readable medium / memory can also be used to store data manipulated by cellular baseband processor 2224 / application processor 2206 during software execution. Cellular baseband processor 2224 / application processor 2206 can be a component of UE 450 and can include at least one of memory 460 and / or at least one of TX processor 468, RX processor 456, and controller / processor 459. In one configuration, device 2204 can be at least one processor chip (modem and / or application) and includes only cellular baseband processor 2224 and / or application processor 2206, while in another configuration, device 2204 can be the entire UE (e.g., see below). Figure 4 The UE 450 includes an additional module of the device 2204.

[0227] As discussed above, component 198 can be configured to: send a request to a network node for system information associated with a system information service of the wireless network; and receive system information from the system information service of the wireless network via the network node. In some aspects, system information component 198 is also configured to: receive initial system information indicating the service identifier of the system information service and the delivery mode of the system information before sending the request. In some aspects, system information component 198 is also configured to establish a PDU session before the request. In some aspects, system information component 198 is also configured to obtain routing information for the system information service from one or more of the following: service discovery, previously configured SI routing information, or minimum system information. In some aspects, system information component 198 is also configured to generate the FQDN of the system information service based on one or more of the PLMN ID, TAC, and service ID of the system information service. In some aspects, system information component 198 is also configured to receive minimum system information indicating the service ID of the system information service from one or more radio nodes. In some aspects, system information component 198 is also configured to: exchange communication via the wireless network based on the system information associated with the system information service. Component 198 can also be configured to perform union. Figure 17 The flowchart described in the or Figures 12 to 16Any aspect executed by the UE in either of the following. Component 198 may be located within the cellular baseband processor 2224, the application processor 2206, or both the cellular baseband processor 2224 and the application processor 2206. Component 198 may be one or more hardware components specifically configured to execute the stated process / algorithm, implemented by one or more processors configured to execute the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. When multiple processors are implemented, the multiple processors may execute the stated process / algorithm individually or in combination. As shown, device 2204 may include a variety of components configured for various functions. In one configuration, device 2204, and in particular the cellular baseband processor 2224 and / or application processor 2206, may include components for sending a request to a network node for system information associated with a system information service of the wireless network; and components for receiving system information from the system information service of the wireless network via the network node. Apparatus 2204 may further include components for receiving initial system information indicating a service identifier of the system information service and a delivery mode of the system information before sending a request. Apparatus 2204 may further include components for establishing a Protocol Data Unit (PDU) session before the request. Apparatus 2204 may further include components for obtaining routing information for the system information service from one or more of the following: service discovery, previously configured SI routing information, or minimal system information. Apparatus 2204 may further include components for generating the FQDN of the system information service based on one or more of the PLMN ID, TAC, and service ID of the system information service. Apparatus 2204 may further include components for receiving minimal system information indicating a service ID of the system information service from one or more radio nodes. Apparatus 2204 may further include components for exchanging communication via a wireless network based on system information associated with the system information service. Apparatus 2204 may further include components for performing combination. Figure 17 The flowchart described in the or Figures 12 to 16 The component may be a component of any aspect of the aspects performed by the UE. The component may be a component 198 of device 2204 configured to perform the functions described therein. As described above, device 2204 may include a TX processor 468, an RX processor 456, and a controller / processor 459. Therefore, in one configuration, these components may be the TX processor 468, the RX processor 456, and / or the controller / processor 459 configured to perform the functions described therein.

[0228] Figure 23Figure 2300 illustrates an example of a hardware implementation for network entity 2302. Network entity 2302 may be a BS, a component of a BS, or implement BS functionality. Network entity 2302 may include at least one of CU 2310, DU 2330, or eDU or RU, which may be referred to as radio node 2340. For example, depending on the layer functionality handled by component 199, network entity 2302 may include CU 2310; both CU 2310 and DU 2330; each of CU 2310, DU 2330, and RU; DU 2330; both DU 2330 and RU; or RU. CU 2310 may include at least one CU processor 2312. CU processor 2312 (or processor circuitry) may include on-chip memory 2312'. In some aspects, CU 2310 may also include an additional memory module 2314 and a communication interface 2318. CU 2310 communicates with DU 2330 via a midhaul link (such as an F1 interface). DU 2330 may include at least one DU processor 2332. DU processor 2332 (or processor circuitry) may include on-chip memory 2332'. In some aspects, DU 2330 may also include an additional memory module 2334 and a communication interface 2338. DU 2330 communicates with RU, eDU, or radio node 2340 via a fronthaul link. Radio node 2340 may include at least one processor 2342. Processor 2342 (or processor circuitry) may include on-chip memory 2342'. In some aspects, radio node 2340 may also include an additional memory module 2344, one or more transceivers 2346, an antenna 2380, and a communication interface 2348. Radio node 2340 communicates with UE 104. As described herein, radio nodes (e.g., such as eDUs) may obtain SI from SI service 2350 using an API. On-chip memories 2312', 2332', 2342' and additional memory modules 2314, 2334, 2344 can each be considered as computer-readable media / memory. Each computer-readable medium / memory can be non-transitory. Each of processors 2312, 2332, 2342 is responsible for general processing, including executing software stored on the computer-readable medium / memory. When executed by the corresponding processor, the software causes that processor to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by the processor when executing the software.

[0229] As discussed above, system information component 199 can be configured to: obtain a request for system information from a UE; provide the request for system information to a system information service of the wireless network; receive system information from the system information service in response to providing the request; and provide system information from the system information service to the UE. System information component 199 can be configured to: provide initial system information indicating a service identifier of the system information service and a delivery mode of the system information prior to the request. System information component 199 can be configured to: obtain system information from the system information service; obtain (e.g., a request for system information from a UE); and provide system information to the UE in response to the request, wherein the system information is obtained from the system information service prior to the request. System information component 199 can also be configured to perform a combination Figure 18 and / or Figure 19 Any aspect described in the flowchart, and / or by or in combination with Figures 12 to 16 The system information component 199 may reside within one or more processors of one or more of the CU 2310, DU 2330, and radio node 2340. The system information component 199 may be one or more hardware components specifically configured to execute the stated process / algorithm, implemented by one or more processors configured to execute the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. When multiple processors are implemented, the multiple processors may execute the stated process / algorithm individually or in combination. The network entity 2302 may include a variety of components configured for various functions. In one configuration, network entity 2302 may include components for obtaining a request for system information from a user equipment (UE); components for providing the request for system information to a system information service of the wireless network; components for receiving system information from the system information service in response to providing the request; and components for providing system information from the system information service to the UE. Network entity 2302 may include components for providing initial system information indicating a service identifier of the system information service and a delivery mode of the system information prior to the request. Network entity 2302 may include components for obtaining system information from the system information service; components for obtaining (e.g., a request for system information from / to the UE); and components for providing system information to the UE in response to the request, wherein the system information is obtained from the system information service prior to the request. Network entity 2302 may also include components for performing a combination. Figure 18 and / or Figure 19 Any aspect described in the flowchart, and / or by or in combination with Figures 12 to 16Any aspect performed by eDU 1202, 1302, 1402, 1502, 1602 or ACMS 1408. A component may be a component 199 of network entity 2302 configured to perform the functions described therein. As described above, network entity 2302 may include TX processor 416, RX processor 470 and controller / processor 475. Therefore, in one configuration, these components may be TX processor 416, RX processor 470 and / or controller / processor 475 configured to perform the functions described therein.

[0230] Figure 24 Figure 2400 illustrates an example of a hardware implementation for network entity 2460. In some aspects, network entity 2460 may be a core network service, such as ACMS 1408, etc. In one example, network entity 2460 may reside within a core network having a service-based architecture as described herein. Network entity 2460 may include at least one network processor 2412 (or processor circuitry). Network processor 2412 may include on-chip memory 2412' (or memory circuitry). In some aspects, network entity 2460 may also include an additional memory module 2414. Network entity 2460 communicates with radio node 2402 directly (e.g., via a backhaul link) or indirectly (e.g., via RIC) through network interface 2480. Network entity 2460 may also communicate with SI service 2450, for example, via API. On-chip memory 2412' and additional memory module 2414 may each be considered as computer-readable media / memory. Each computer-readable media / memory may be non-transitory. The network processor 2412 is responsible for general processing, including executing software stored on a computer-readable medium / memory. When executed by the corresponding processor, this software causes the processor to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by the processor while executing the software.

[0231] As discussed above, system information component 199 can be configured to: obtain a request for system information from a UE; provide the request for system information to a system information service of the wireless network; receive system information from the system information service in response to providing the request; and provide system information from the system information service to the UE. System information component 199 can be configured to: provide initial system information indicating a service identifier of the system information service and a delivery mode of the system information prior to the request. System information component 199 can be configured to: obtain system information from the system information service; obtain (e.g., a request for system information from / from the UE); and provide system information to the UE in response to the request, wherein the system information was obtained from the system information service prior to the request. System information component 199 can also be configured to perform a combination Figure 18 and / or Figure 19 Any aspect described in the flowchart, and / or by or in combination with Figures 12 to 16 The system information component 199 may reside within one or more processors of one or more of the CU 2310, DU 2330, and radio node 2340. The system information component 199 may be one or more hardware components specifically configured to execute the stated process / algorithm, implemented by one or more processors configured to execute the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. When multiple processors are implemented, the multiple processors may execute the stated process / algorithm individually or in combination. Network entity 2302 may include a variety of components configured for various functions. Network entity 2460 may include a variety of components configured for various functions. In one configuration, network entity 2460 may include components for obtaining a request for system information from a user equipment (UE); components for providing the request for system information to a system information service of the wireless network; components for receiving system information from the system information service in response to providing the request; and components for providing system information from the system information service to the UE. Network entity 2302 may include components for providing initial system information indicating a service identifier of the system information service and a delivery mode of the system information prior to the request. Network entity 2302 may include components for obtaining system information from the system information service; components for obtaining (e.g., a request for system information from / to the UE); and components for providing system information to the UE in response to the request, wherein the system information was previously obtained from the system information service prior to the request. Network entity 2302 may also include components for performing a combination. Figure 18 and / or Figure 19 Any aspect described in the flowchart, and / or by or in combination with Figures 12 to 16 Any aspect performed by eDU 1202, 1302, 1402, 1502, 1602 or ACMS 1408 in any of the above. The component may be a system information component 191 of network entity 2460 configured to perform the functions described by the component.

[0232] Figure 25Figure 2500 illustrates an example of a hardware implementation for network entity 2560. In some aspects, network entity 2560 may be an SI service, such as 1206, 1306, 1406, 1506, 1606, etc. In one example, network entity 2560 may reside within a core network that is part of a service-based architecture as described herein. Network entity 2560 may include at least one network processor 2512 (or processor circuitry). Network processor 2512 may include on-chip memory 2512' (or memory circuitry). In some aspects, network entity 2560 may also include an additional memory module 2514. Network entity 2560 communicates with radio node 2502 directly (e.g., via a backhaul link) or indirectly (e.g., via RIC) through network interface 2580. On-chip memory 2512' and additional memory module 2514 may each be considered as computer-readable media / memory. Each computer-readable media / memory may be non-transitory. Network processor 2512 is responsible for general processing, including executing software stored on computer-readable media / memory. When executed by the corresponding processor, this software causes the processor to perform the various functions described above. The computer-readable media / memory can also be used to store data manipulated by the processor while executing the software.

[0233] As discussed above, System Information Component 191 can be configured to: receive a request for system information from a UE served by a network node; and provide system information to the network node serving the UE in response to the request. System Information Component 191 can be configured to obtain system information from one or more of the service of the wireless network or the radio nodes of the wireless network. System Information Component 191 can be configured to: perform at least one of authorization or authentication on the UE using an authorization service before providing system information to the serving radio node in response to the request. System Information Component 191 can be configured to: perform at least one of authorization or authentication on the UE using an authorization service before providing system information to the ACMS in response to the request. System Information Component 191 can be configured to: obtain system information from one or more of the service of the wireless network or the radio nodes of the wireless network; and provide system information from the system information service to one or more network nodes. System Information Component 191 can be configured to provide scheduling information for system information to be obtained from the radio node to the radio node. System Information Component 191 can also be configured to perform a combination... Figure 20 and / or Figure 21 Any aspect described in the flowchart, and / or by or in combination with Figures 12 to 16The system information component 191 may reside within the network processor 2512. The system information component 191 may be one or more hardware components specifically configured to execute the process / algorithm, implemented by one or more processors configured to execute the process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. When multiple processors are implemented, the multiple processors may execute the stated process / algorithm individually or in combination. The network entity 2560 may include various components configured for various functions. In one configuration, the network entity 2560 may include components for receiving a request for system information from a user equipment (UE) served by a network node; and components for providing system information to the network node serving the UE in response to the request. The network entity 2560 may include components for obtaining system information from one or more of the services of the wireless network or the radio nodes of the wireless network. Network entity 2560 may include components for performing at least one of authorization or authentication on the UE using an authorization service before providing system information to the serving radio node in response to a request. Network entity 2560 may include components for performing at least one of authorization or authentication on the UE using an authorization service before providing system information to the ACMS in response to a request. Network entity 2560 may include components for obtaining system information from one or more of the service of the wireless network or the radio nodes of the wireless network; and components for providing system information from the system information service to one or more network nodes. Network entity 2560 may include components for providing scheduling information for system information to be obtained from the radio nodes to the radio nodes. Network entity 2560 may also include components for performing combination. Figure 20 and / or Figure 21 Any aspect described in the flowchart, and / or by or in combination with Figures 12 to 16 Any aspect of the SI services 1206, 1306, 1406, 1506, and 1606 performed in any of them. The component may be a system information component 191 of network entity 2560 configured to perform the functions described by the component.

[0234] It should be understood that the specific order or hierarchy of the boxes in the disclosed process / flowcharts is merely an example of the exemplary method. It should be understood that the specific order or hierarchy of the boxes in the process / flowcharts may be rearranged based on design preferences. Furthermore, some boxes may be combined or omitted. The appended method claims present the elements of various boxes in a sample order, but are not limited to the given specific order or hierarchy.

[0235] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not limited to the aspects described herein but should be given the full scope consistent with the language of the claims. Unless specifically stated otherwise, references to elements in the singular form do not mean “one and only one” but rather “one or more.” Terms such as “if,” “when,” and “simultaneously” do not imply a direct temporal relationship or reaction. That is, these phrases, such as “when…”, do not imply an immediate action in response to the occurrence of an action or during the occurrence of an action, but simply suggest that if a condition is met, then the action will occur, without requiring a specific or immediate time limit for the occurrence of the action. The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or superior to other aspects. Unless otherwise specifically stated, the term “some” refers to one or more. Combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, and may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" can be only A, only B, only C, A and B, A and C, B and C, or A and B and C, where any such combination may contain one or more members of A, B, or C. A set should be interpreted as a collection of elements with a number of one or more elements. Therefore, for a set of X, X will include one or more elements. When at least one processor is configured to execute a set of functions, the at least one processor is configured to execute the set of functions individually or in any combination. Therefore, each processor in at least one processor can be configured to perform a specific subset of the set of functions, wherein the subset is the complete set, a suitable subset of the set, or an empty subset of the set. A processor may be referred to as a processor circuit. A memory / memory module may be referred to as a memory circuit. If a first device receives data from or sends data to a second device, data can be received / sent directly between the first and second devices, or indirectly between the first and second devices through a set of devices. A device configured to "output" or "provide" data (such as transmission, signaling, or messaging) may, for example, transmit data using a transceiver, or may transmit the data to the device that sent the data.A device configured to "acquire" data (such as, transmit, signal, or message) may, for example, receive the data using a transceiver, or may obtain the data from a device that receives the data. Information stored in memory includes instructions and / or data. All structural and functional equivalents of the elements throughout the various aspects described herein that are known to those skilled in the art or will later be known are expressly incorporated herein by reference and are covered by the claims. Furthermore, nothing disclosed herein is intended to be offered to the public, whether or not such disclosure is expressly recited in the claims. The words "module," "mechanism," "element," "device," etc., cannot replace the word "component." Therefore, no claim element will be construed as a functional component unless the element is expressly recited using the phrase "component for..."

[0236] As used in this article, the phrase “based on” should not be interpreted as referring to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase “based on A” (where “A” can be information, conditions, factors, etc.) should be interpreted as “based on at least A”, unless otherwise stated otherwise.

[0237] The following aspects are merely illustrative and may be combined with other aspects or teachings described herein without limitation.

[0238] Aspect 1 is a method for wireless communication at a user equipment (UE), the method comprising: sending a request to a network node for system information associated with a system information service of a wireless network; and receiving the system information from the system information service of the wireless network via the network node.

[0239] Aspect 2 is the method according to aspect 1, the method further comprising: receiving initial system information indicating a service identifier of the system information service and a delivery mode of the system information before sending the request.

[0240] Aspect 3 is the method according to aspect 1 or aspect 2, wherein the initial system information is based on one or more of the following indicating the delivery mode of the system information: broadcast, on-demand download, download via user plane, download for each system information or system information block (SIB), download from the system information service, download via radio node, or download via access connection management service (ACMS).

[0241] Aspect 4 is the method according to any one of Aspects 1 to 3, wherein the request from the UE includes a first Internet Protocol (IP) packet, the first Internet Protocol (IP) packet including the source IP address of the UE and the destination IP address of the system information service, and wherein the system information is received in a second IP packet encapsulating the system information.

[0242] Aspect 5 is the method according to aspect 4, the method further comprising: establishing a Protocol Data Unit (PDU) session prior to the request.

[0243] Aspect 6 is the method according to aspect 4 or 5, the method further comprising: obtaining routing information of the system information service from one or more of the following: discovery service, previously configured SI routing information, or minimum system information.

[0244] Aspect 7 is the method according to aspect 4 or 5, the method further comprising: obtaining routing information of the system information service from the discovery service.

[0245] Aspect 8 is the method according to aspect 4 or 5, the method further comprising: obtaining routing information of the system information service from configured SI routing information.

[0246] Aspect 9 is the method according to aspect 4 or 5, the method further comprising: obtaining routing information of the system information service from minimal system information.

[0247] Aspect 10 is the method according to any one of Aspects 1 to 9, the method further comprising: generating a fully qualified domain name (FQDN) for the system information service based on one or more of a Public Land Mobile Network Identifier (PLMN ID), a Tracking Area Code (TAC), and a Service Identifier (ID) for the system information service.

[0248] Aspect 11 is the method according to any one of Aspects 1 to 10, wherein the request from the UE is directed to one or more radio nodes and includes one or more of the following: a first identifier (ID) of the UE, a service ID of the system information service, or a system information index.

[0249] Aspect 12 is a method according to any one of aspects 1 to 11, the method further comprising: receiving minimum system information from the one or more radio nodes indicating the service ID of the system information service.

[0250] Aspect 13 is the method according to any one of aspects 1 to 11, wherein the system information is located in a message or system information container from a radio node.

[0251] Aspect 14 is the method according to any one of aspects 1 to 11, wherein the request is located in a first random access message and the system information is included in a second random access message.

[0252] Aspect 15 is a method according to any one of Aspects 1 to 4, wherein the request from the UE is included in a first Non-Access Stratum (NAS) message directed to the Access Connection Management Service (ACMS) and indicating a system information index, and wherein the system information is received in a second NAS message from the ACMS, the second NAS message encapsulating the system information indicated by the system information index.

[0253] Aspect 16 is the method according to any one of Aspects 1 to 4, wherein the request from the UE is included in a first non-access stratum (NAS) message directed to the Access Connection Management Service (ACMS) and indicates a system information index.

[0254] Aspect 17 is the method according to any one of Aspects 1 to 4, wherein the system information is received in a second NAS message from the ACMS, the second NAS message encapsulating the system information indicated by the system information index.

[0255] Aspect 18 is a method according to any one of aspects 1 to 4, wherein the request from the UE is included in a first protocol data unit (PDU) directed to a radio node, and wherein the system information is received in a second PDU from the radio node.

[0256] Aspect 19 is a method according to any one of Aspects 1 to 4 or 18, wherein the UE has an access connection with the radio node, wherein the request is included in a Layer 2 (L2) PDU to the radio node, and wherein the system information is included in a response L2 PDU from the radio node.

[0257] Aspect 20 is a method according to any one of Aspects 1 to 4 or 18, wherein the UE does not have a connection established with the radio node, and the request is included in a System Information Block (SIB) or System Information (SI) Request PDU to the radio node, and the system information is included in a Layer 2 (L2) PDU from the radio node.

[0258] Aspect 21 is the method according to any one of aspects 1 to 20, the method further comprising: exchanging communication via the wireless network based on the system information associated with the system information service.

[0259] Aspect 22 is a method for wireless communication at a network node, the method comprising: obtaining a request for system information from a user equipment (UE); providing the request for the system information to a system information service of a wireless network; receiving the system information from the system information service in response to providing the request; and providing the system information from the system information service to the UE.

[0260] Aspect 23 is the method according to aspect 22, the method further comprising: prior to the request, providing initial system information indicating a service identifier of the system information service and a delivery mode of the system information.

[0261] Aspect 24 is the method according to aspect 22 or 23, wherein the request of the UE includes a first Internet Protocol (IP) packet, the first Internet Protocol (IP) packet including the source IP address of the UE and the destination IP address of the system information service, and wherein the system information is located in a second IP packet encapsulating the system information, wherein providing the request to the system information service includes providing the first IP packet to the system information service.

[0262] Aspect 25 is the method according to aspect 22 or 23, wherein the request of the UE includes a first Internet Protocol (IP) packet, the first Internet Protocol (IP) packet including the source IP address of the UE and the destination IP address of the system information service, and wherein the system information is located in a second IP packet encapsulating the system information.

[0263] Aspect 26 is the method according to aspect 22 or 23, wherein the system information is located in a second IP packet encapsulating the system information, wherein providing the request to the system information service includes providing the first IP packet to the system information service.

[0264] Aspect 27 is the method according to aspect 22 or 23, wherein the network node is a radio node, and wherein the request of the UE is directed to the radio node and includes one or more of the following: the UE identifier (ID) of the UE, the service ID of the system information service, or the system information index, wherein providing the request for the system information to the system information service includes transmitting an additional request indicating one or more of the UE ID or the system information index to the system information service.

[0265] Aspect 28 is the method according to aspect 22 or 23, wherein the network node is a radio node, and wherein the request for the UE is directed to the radio node and includes one or more of the following: the UE identifier (ID) of the UE, the service ID of the system information service, or the system information index.

[0266] Aspect 29 is the method according to aspect 22 or 23, wherein providing the request for the system information to the system information service includes transmitting an additional request indicating one or more of the UE ID or the system information index to the system information service.

[0267] Aspect 30 is the method according to aspect 22 or 23, wherein the system information is located in a message for the UE from the radio node, a system information container, or a random access message.

[0268] Aspect 31 is the method according to aspect 22 or 23, wherein the network node includes an Access Connection Management Service (ACMS), and wherein the UE's request is included in a first Non-Access Stratum (NAS) message directed to the ACMS and indicating a system information index, and the system information is provided in a second NAS message from the ACMS, the second NAS message encapsulating the system information indicated by the system information index.

[0269] Aspect 32 is the method according to aspect 22 or 23, wherein the network node includes an access connection management service (ACMS).

[0270] Aspect 33 is the method according to aspect 22 or 23, wherein the UE’s request is included in a first non-access stratum (NAS) message directed to the ACMS and indicating a system information index.

[0271] Aspect 34 is the method according to aspect 22 or 23, and the system information is provided in a second NAS message from the ACMS, the second NAS message encapsulating the system information indicated by the system information index.

[0272] Aspect 35 is a method for wireless communication at a network node, the method comprising: obtaining system information from a system information service; obtaining a request for the system information from a user equipment (UE); and providing the system information to the UE in response to the request, wherein the system information was previously obtained from the system information service prior to the request.

[0273] Aspect 36 is the method according to aspect 35, wherein the network node is a radio node, wherein the UE's request is included in a first protocol data unit (PDU) directed to the radio node, and the system information is located in a second PDU for the UE from the radio node.

[0274] Aspect 37 is the method according to aspect 35, wherein the request of the UE is included in a first protocol data unit (PDU) directed to a radio node, and the system information is located in a second PDU for the UE from the radio node.

[0275] Aspect 38 is the method according to aspect 35, wherein the network node is a radio node and the system information is located in a second PDU for the UE from the radio node.

[0276] Aspect 39 is the method according to aspect 35, wherein the radio node has a connection with the UE, wherein the request is included in a Layer 2 (L2) PDU to the radio node, and the system information is included in a response L2 PDU from the radio node.

[0277] Aspect 40 is the method according to aspect 35, wherein the radio node has a connection with the UE, and wherein the request is included in a layer 2 (L2) PDU to the radio node.

[0278] Aspect 41 is the method according to aspect 35, wherein the radio node has a connection with the UE, and the system information is included in a response L2 PDU from the radio node.

[0279] Aspect 42 is the method according to aspect 35, wherein the radio node does not have a connection established with the UE, and wherein the request is included in a System Information Block (SIB) or System Information (SI) Request PDU to the radio node, and the system information is included in a Layer 2 (L2) PDU from the radio node.

[0280] Aspect 43 is the method according to aspect 35, wherein the radio node has a connection established with the UE, and the system information is included in a layer 2 (L2) PDU from the radio node.

[0281] Aspect 44 is the method according to aspect 35, wherein the radio node does not have a connection established with the UE, and wherein the request is included in a System Information Block (SIB) or System Information (SI) Request PDU destined for the radio node.

[0282] Aspect 45 is a method for wireless communication at a system information service in a wireless network, the method comprising: receiving a request for system information from a user equipment (UE) served by a network node; and providing the system information to the network node serving the UE in response to the request.

[0283] Aspect 46 is the method according to aspect 45, the method further comprising: obtaining the system information from one or more of the services of the wireless network or the radio nodes of the wireless network.

[0284] Aspect 47 is the method according to aspect 45 or 46, wherein the request is included in a first Internet Protocol (IP) packet for the UE and includes the source IP address of the UE and the destination IP address of the system information service, and wherein the system information is provided in a second IP packet, the second IP packet encapsulating the system information from the system information service.

[0285] Aspect 48 is the method according to aspect 45 or 46, wherein the request is included in a first Internet Protocol (IP) packet for the UE and includes the source IP address of the UE and the destination IP address of the system information service.

[0286] Aspect 49 is the method according to aspect 45 or 46, wherein the system information is provided in a second IP packet, the second IP packet encapsulating the system information from the system information service.

[0287] Aspect 50 is the method according to aspect 45 or 46, wherein the network node is a serving radio node serving the UE, and wherein the request originates from the serving radio node and includes one or more of the following: the UE identifier (ID) of the UE, the service ID of the system information service, and the system information index.

[0288] Aspect 51 is the method according to aspect 50, the method further comprising: performing at least one of authorization or authentication on the UE using an authorization service before providing the system information to the serving radio node in response to the request.

[0289] Aspect 52 is the method according to aspect 45 or 46, wherein the network node includes an Access Connection Management Service (ACMS), wherein the request originates from the ACMS and indicates a UE identifier.

[0290] Aspect 53 is the method according to aspect 52, wherein the UE identifier is a Subscription Permanent Identifier (SUPI) or a General Public Subscriber Identifier (GPSI).

[0291] Aspect 54 is the method according to aspect 52 or 53, the method further comprising: performing at least one of authorization or authentication on the UE using an authorization service before providing the system information to the ACMS in response to the request.

[0292] Aspect 55 is a method for wireless communication at a system information service of a wireless network, the method comprising: obtaining system information from one or more of the service of the wireless network or radio nodes of the wireless network; and providing the system information from the system information service to one or more network nodes.

[0293] Aspect 56 is the method according to aspect 55, the method further comprising: providing scheduling information of the system information to be obtained from the radio node to the radio node.

[0294] Aspect 57 is an apparatus for wireless communication at a UE, the apparatus comprising: one or more memories; and one or more processors coupled to the one or more memories and configured to cause the UE to perform a method according to any one of aspects 1 to 21.

[0295] Aspect 58 is an apparatus for wireless communication at a UE, the apparatus comprising components for performing each step of the method according to any one of aspects 1 to 21.

[0296] Aspect 59 is a UE, the UE comprising: a processing system including processor circuitry and memory circuitry storing code and coupled to the processor circuitry, the processing system being configured to cause the UE to perform a method according to any one of aspects 1 to 21.

[0297] Aspect 60 is an apparatus according to any one of aspects 57 to 59, the apparatus further comprising one or more transceivers or antennas configured to receive or transmit in association with the method according to any one of aspects 1 to 21.

[0298] Aspect 61 is a computer-readable storage medium (e.g., a non-transitory computer-readable storage medium) storing computer-executable code at a UE, the code causing the UE to perform a method according to any one of aspects 1 to 21 when executed by at least one processor.

[0299] Aspect 62 is an apparatus for wireless communication at a UE, the apparatus comprising: one or more memories; and one or more processors coupled to the one or more memories and configured to cause the UE to perform a method according to any one of aspects 23 to 34.

[0300] Aspect 63 is an apparatus for wireless communication at a UE, the apparatus comprising components for performing each step of the method according to any one of aspects 23 to 34.

[0301] Aspect 64 is a UE comprising: a processing system including processor circuitry and memory circuitry storing code and coupled to the processor circuitry, the processing system being configured to cause the UE to perform a method according to any one of aspects 23 to 34.

[0302] Aspect 66 is an apparatus according to any one of aspects 62 to 64, the apparatus further comprising one or more transceivers or antennas configured to receive or transmit in association with the method according to any one of aspects 22 to 34.

[0303] Aspect 66 is a computer-readable storage medium (e.g., a non-transitory computer-readable storage medium) that stores computer-executable code at a UE, the code causing the UE to perform a method according to any one of aspects 22 to 34 when executed by at least one processor.

[0304] Aspect 67 is an apparatus for wireless communication at a network node, the apparatus comprising: one or more memories; and one or more processors coupled to the one or more memories and configured to cause the network node to perform the method according to any one of aspects 35 to 44.

[0305] Aspect 68 is an apparatus for wireless communication at a network node, the apparatus comprising components for performing each step of the method according to any one of aspects 35 to 44.

[0306] Aspect 69 is a network entity comprising: a processing system including processor circuitry and memory circuitry storing code and coupled to the processor circuitry, the processing system being configured to cause the network entity to: perform the method according to any one of aspects 35 to 44.

[0307] Aspect 70 is an apparatus according to any one of aspects 67 to 69, the apparatus further comprising one or more transceivers or antennas configured to receive or transmit in association with the method according to any one of aspects 35 to 44.

[0308] Aspect 71 is a computer-readable storage medium (e.g., a non-transitory computer-readable storage medium) that stores computer-executable code at a network node, the code causing the network node to perform the method according to any one of aspects 34 to 43 when executed by at least one processor.

[0309] Aspect 72 is an apparatus for wireless communication at a system information service, the apparatus comprising: one or more memories; and one or more processors coupled to the one or more memories and configured to cause the system information service to perform the method according to any one of aspects 45 to 54.

[0310] Aspect 73 is an apparatus for wireless communication at a system information service, the apparatus comprising components for performing each step of the method according to any one of aspects 45 to 54.

[0311] Aspect 74 is a system information service comprising: a processing system including processor circuitry and memory circuitry storing code and coupled to the processor circuitry, the processing system being configured to cause the system information service to: perform a method according to any one of aspects 45 to 54.

[0312] Aspect 75 is an apparatus according to any one of aspects 72 to 74, the apparatus further comprising one or more transceivers or antennas configured to receive or transmit in association with the method according to any one of aspects 45 to 54.

[0313] Aspect 76 is a computer-readable storage medium (e.g., a non-transitory computer-readable storage medium) that stores computer-executable code at a system information service, said code causing the system information service to perform the method according to any one of aspects 45 to 54 when executed by at least one processor.

[0314] Aspect 77 is an apparatus for wireless communication at a system information service, the apparatus comprising: one or more memories; and one or more processors coupled to the one or more memories and configured to cause the system information service to perform the method according to any one of aspects 55 to 56.

[0315] Aspect 78 is an apparatus for wireless communication at a system information service, the apparatus comprising components for performing each step of the method according to any one of aspects 55 to 56.

[0316] Aspect 79 is a system information service comprising: a processing system including processor circuitry and memory circuitry storing code and coupled to the processor circuitry, the processing system being configured to cause the system information service to: perform the method according to any one of aspects 55 to 56.

[0317] Aspect 80 is an apparatus according to any one of aspects 77 to 79, the apparatus further comprising one or more transceivers or antennas configured to receive or transmit in association with the method according to any one of aspects 55 to 56.

[0318] Aspect 81 is a computer-readable storage medium (e.g., a non-transitory computer-readable storage medium) that stores computer-executable code at a system information service, said code causing the system information service to perform the method according to any one of aspects 56 to 56 when executed by at least one processor.

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: One or more memory units; and One or more processors, said one or more processors being coupled to said one or more memories and configured to cause the UE to: Send a request to a network node for system information associated with the system information service of the wireless network; as well as The system information is received from the system information service of the wireless network via the network node.

2. The apparatus of claim 1, further comprising at least one antenna coupled to the one or more processors, wherein the one or more processors are further configured to cause the UE to: Before sending the request, initial system information indicating the service identifier of the system information service and the delivery mode of the system information is received.

3. The apparatus of claim 2, wherein the initial system information indicates the delivery mode of the system information based on one or more of the following: broadcast, Download on demand. Download via user plane For each system information or system information block (SIB) download, Download from the system information service. Download via radio node, or Downloaded via Access Connection Management Service (ACMS).

4. The apparatus of claim 1, wherein the request from the UE includes a first Internet Protocol (IP) packet, the first Internet Protocol (IP) packet including a source IP address of the UE and a destination IP address of the system information service, and wherein the system information is located in a second IP packet for the UE.

5. The apparatus of claim 4, wherein the one or more processors are further configured to cause the UE to: A Protocol Data Unit (PDU) session is established prior to the request.

6. The apparatus of claim 4, wherein the one or more processors are further configured to cause the UE to: The routing information for the system information service may be obtained from one or more of the following: Discovery service Previously configured SI routing information, or Minimal system information.

7. The apparatus of claim 6, wherein the one or more processors are further configured to cause the UE to: The fully qualified domain name (FQDN) of the system information service is generated based on one or more of the Public Land Mobile Network Identifier (PLMN ID), Tracking Area Code (TAC), and Service Identifier (ID) of the system information service.

8. The apparatus of claim 1, wherein the request from the UE is directed to one or more radio nodes, and includes one or more of the following: The UE's first identifier (ID). The service ID of the system information service, or System information index.

9. The apparatus of claim 8, wherein the one or more processors are further configured to cause the UE to: Receive minimum system information indicating the service ID of the system information service from the one or more radio nodes.

10. The apparatus of claim 8, wherein the system information is located in a message or system information container from a radio node.

11. The apparatus of claim 8, wherein the request is located in a first random access message and the system information is included in a second random access message.

12. The apparatus of claim 1, wherein the request from the UE is included in a first non-access stratum (NAS) message directed to the Access Connection Management Service (ACMS) and indicating a system information index, and wherein the system information is located in a second NAS message from the ACMS, the second NAS message encapsulating the system information indicated by the system information index.

13. The apparatus of claim 1, wherein the request from the UE is included in a first protocol data unit (PDU) directed to a radio node, and wherein the system information is located in a second PDU from the radio node.

14. The apparatus of claim 13, wherein the UE has an access connection with the radio node, wherein the request is included in a Layer 2 (L2) PDU toward the radio node, and wherein the system information is included in a response L2 PDU from the radio node.

15. The apparatus of claim 13, wherein the UE does not have a connection established with the radio node, wherein the request is included in a System Information Block (SIB) or System Information (SI) Request PDU to the radio node, and wherein the system information is included in a Layer 2 (L2) PDU from the radio node.

16. The apparatus of claim 1, wherein the one or more processors are further configured to cause the UE to: Based on the system information associated with the system information service, communication is exchanged via the wireless network.

17. An apparatus for wireless communication at a network node, the apparatus comprising: One or more memory units; and One or more processors, said one or more processors coupled to said one or more memories and configured to cause the network node to: Obtain the user equipment's (UE) request for system information; The request for the system information will be provided to the system information service of the wireless network; In response to the request, receive the system information from the system information service; as well as The system information from the system information service is provided to the UE.

18. The apparatus of claim 17, further comprising one or more antennas coupled to the one or more processors, wherein the one or more processors are further configured to cause the network node to: Prior to the request, initial system information is provided, which indicates the service identifier of the system information service and the delivery mode of the system information.

19. The apparatus of claim 17, wherein the request of the UE includes a first Internet Protocol (IP) packet, the first Internet Protocol (IP) packet including the source IP address of the UE and the destination IP address of the system information service, wherein the system information is located in a second IP packet encapsulating the system information, and In order to provide the request to the system information service, the one or more processors are configured to cause the network node to provide the first IP packet to the system information service.

20. The apparatus of claim 17, wherein the network node is a radio node, and wherein the request of the UE is directed to the radio node and includes one or more of the following: The UE identifier (ID) of the UE. The service ID of the system information service, or System information index In order to provide the request for the system information to the system information service, the one or more processors are configured to cause the network node to transmit an additional request indicating one or more of the UE ID or the system information index to the system information service.

21. The apparatus of claim 20, wherein the system information is included in one of a message to the UE from the radio node, a system information container, or a random access message.

22. The apparatus of claim 17, wherein the network node includes an Access Connection Management Service (ACMS), wherein the UE's request is included in a first Non-Access Stratum (NAS) message directed to the ACMS indicating a system information index, and wherein the system information is provided in a second NAS message from the ACMS, the second NAS message encapsulating the system information indicated by the system information index.

23. An apparatus for wireless communication at a network node, the apparatus comprising: One or more memory units; and One or more processors, said one or more processors coupled to said one or more memories and configured to cause the network node to: Obtain system information from system information services; Obtain a request from the user equipment (UE) for information about the system; as well as In response to the request, the system information is provided to the UE, wherein the system information is obtained from the system information service prior to the request.

24. The apparatus of claim 23, wherein the network node is a radio node, wherein the request of the UE is included in a first protocol data unit (PDU) directed to the radio node, and wherein the system information is located in a second PDU for the UE from the radio node.

25. The apparatus of claim 24, wherein the radio node has a connection with the UE, wherein the request is included in a Layer 2 (L2) PDU destined for the radio node, and wherein the system information is included in a response L2 PDU from the radio node.

26. The apparatus of claim 24, wherein the radio node does not have a connection established with the UE, wherein the request is included in a System Information Block (SIB) or System Information (SI) Request PDU to the radio node, and wherein the system information is included in a Layer 2 (L2) PDU from the radio node.

27. An apparatus for wireless communication at a system information service in a wireless network, the apparatus comprising: One or more memory units; and One or more processors, said one or more processors being coupled to said one or more memories and configured to enable the system information services: Receive requests for system information from user equipment (UE) served by network nodes; as well as In response to the request, the system information is provided to the network node serving the UE.

28. The apparatus of claim 27, wherein the one or more processors are further configured to enable the system information service: The system information is obtained from one or more of the services of the wireless network or the radio nodes of the wireless network.

29. The apparatus of claim 27, wherein the request is included in a first Internet Protocol (IP) packet for the UE and includes the source IP address of the UE and the destination IP address of the system information service, and wherein the system information is located in a second IP packet, the second IP packet encapsulating the system information from the system information service.

30. The apparatus of claim 27, wherein the network node is a serving radio node serving the UE, and wherein the request originates from the serving radio node and includes one or more of the following: The UE identifier (ID) of the UE. The service ID of the system information service, or System information index.

31. The apparatus of claim 30, wherein the one or more processors are further configured to enable the system information service: Before sending the system information to the serving radio node in response to the request, at least one of authorization or authentication is performed on the UE using the authorization service.

32. The apparatus of claim 27, wherein the network node includes an Access Connection Management Service (ACMS), wherein the request originates from the ACMS and indicates a UE identifier.

33. The apparatus of claim 32, wherein the UE identifier is a Subscription Permanent Identifier (SUPI) or a General Public Subscriber Identifier (GPSI).

34. The apparatus of claim 33, wherein the one or more processors are further configured to enable the system information service: Before sending the system information to the ACMS in response to the request, at least one of authorization or authentication is performed on the UE using the authorization service.

35. An apparatus for wireless communication at a system information service in a wireless network, the apparatus comprising: One or more memory units; and One or more processors, said one or more processors being coupled to said one or more memories and configured to enable the system information services: System information is obtained from one or more of the services of the wireless network or the radio nodes of the wireless network; as well as The system information from the system information service is provided to one or more network nodes.

36. The apparatus of claim 35, wherein the one or more processors are further configured to enable the system information service: The scheduling information for the system information to be obtained from the radio node is provided to the radio node.

Images