Techniques for system information broadcasting in service-based wireless system

Abstract

Methods, systems, and devices for wireless communication are described. In the context of a service-based wireless system, a network entity of a random access network (RAN) may aggregate system information block (SIB) configurations from a plurality of core network services, where the core network services are provisioned or provided by a service-based network interfacing with the RAN. After aggregating the SIB configuration, the network entity may relay or broadcast system information (e.g., an SIB container) to UEs communicatively coupled to the RAN on behalf of the core network service.

Description

Cross-references

[0001] This patent application claims priority to U.S. patent application No. 17 / 948,107, filed by GHOLMIEH et al. on September 19, 2022, and entitled “TECHNIQUES FOR SYSTEM INFORMATION BROADCAST IN A SERVICE-BASED WIRELESS SYSTEM,” which is assigned to the assignee of this application and the contents thereof are expressly incorporated herein by reference. Technical Field

[0002] The following relates to wireless communications, including techniques for system information broadcast in a service-based wireless system. Background Art

[0003] Wireless communication systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcasting, etc. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency and power). Examples of such multiple access systems include fourth generation (4G) systems (e.g., long term evolution (LTE) systems, improved LTE (LTE-A) systems or LTE-A Pro systems), fifth generation (5G) systems (which may be referred to as new radio (NR) systems) and sixth generation (6G) systems. These systems may use techniques such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA) or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include a radio access network (RAN) that supports wireless communication for a communication device (which may be referred to as a user equipment (UE)).

[0004] In the context of a service-based wireless system, different core network services may be expected to share information (e.g., system information, such as system information block (SIB) messages / containers) with UEs and other wireless devices in the network, enabling the respective devices to communicate with the core network services. Summary of the invention

[0005] The described technology relates to improved methods, systems, devices and apparatuses for supporting technology for broadcasting system information in a service-based wireless system. In general, various aspects of the present disclosure relate to signaling, configuration and other mechanisms for distributing system information (e.g., system information block (SIB) messages) in a service-based wireless system. In particular, various aspects of the present disclosure relate to signaling that enables a network entity (e.g., a distributed unit (DU)) to compile SIB configurations for multiple different core network services and distribute SIBs for corresponding core network services based on the acquired SIB configurations.

[0006] A method is described. The method may include: receiving first signaling from a first core network service provided by a service-based network indicating a first SIB configuration associated with the first core network service, the first SIB configuration including first information associated with communications with the first core network service; receiving second signaling from a second core network service provided by the service-based network indicating a second SIB configuration associated with the second core network service, the second SIB configuration including second information associated with communications with the second core network service; sending a first SIB container including the first information to one or more UEs; and sending a second SIB container including the second information to the one or more UEs.

[0007] A device is described. The device may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the device to perform the following operations: receiving a first signaling indicating a first SIB configuration associated with a first core network service provided by a service-based network, the first SIB configuration including first information associated with communication with the first core network service; receiving a second signaling indicating a second SIB configuration associated with a second core network service provided by the service-based network, the second SIB configuration including second information associated with communication with the second core network service; sending a first SIB container including the first information to one or more UEs; and sending a second SIB container including the second information to the one or more UEs.

[0008] Another apparatus is described. The apparatus may include: a unit for receiving first signaling indicating a first SIB configuration associated with a first core network service provided by a service-based network, the first SIB configuration including first information associated with communications with the first core network service; a unit for receiving second signaling indicating a second SIB configuration associated with a second core network service provided by the service-based network, the second SIB configuration including second information associated with communications with the second core network service; a unit for sending a first SIB container including the first information to one or more UEs; and a unit for sending a second SIB container including the second information to the one or more UEs.

[0009] A non-transitory computer-readable medium storing code is described. The code may include instructions executable by a processor to perform the following operations: receiving first signaling indicating a first SIB configuration associated with a first core network service provided by a service-based network, the first SIB configuration including first information associated with communication with the first core network service; receiving second signaling indicating a second SIB configuration associated with a second core network service provided by the service-based network, the second SIB configuration including second information associated with communication with the second core network service; sending a first SIB container including the first information to one or more UEs; and sending a second SIB container including the second information to the one or more UEs.

[0010] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first signaling, the second signaling, or both may be received according to application programming interface (API) information associated with the DU.

[0011] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: receiving a first parameter set associated with the first SIB configuration via the first signaling, wherein the first parameter set includes scheduling information for the first SIB container, a size of the first SIB container, a quality of service (QoS) metric for the first SIB container, a delivery delay for the first SIB container, a coverage area for the first SIB container, or any combination thereof, wherein the first SIB container may be sent according to the first parameter set.

[0012] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: receiving, via the first signaling, an indication that a SIB container associated with the first SIB configuration can be provided on demand in response to a request from the one or more UEs, wherein sending the first SIB container can be based on the indication.

[0013] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: sending an indication to the one or more UEs that a SIB container associated with the first SIB configuration can be provided on demand in response to a request from the one or more UEs; and receiving a request for the first SIB container from a UE among the one or more UEs based on sending the indication, wherein the first SIB container can be sent to the UE in response to the request.

[0014] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: sending a third SIB container to the one or more UEs, the third SIB container including third information associated with communication between the DU and the one or more UEs.

[0015] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: sending third signaling indicating API information associated with the DU to the first core network service, the second core network service, an additional core network service, or any combination thereof, wherein the first signaling, the second signaling, or both may be received based on the application programming interface information.

[0016] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: sending third signaling to the one or more UEs indicating first scheduling information associated with the first SIB container and second scheduling information associated with the second SIB container, wherein the first SIB container and the second SIB container can be sent according to the first scheduling information and the second scheduling information, respectively.

[0017] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the methods, apparatus, and non-transitory computer-readable media may also include operations, features, units, or instructions for performing the following operations: sending a third SIB container including the third information to the one or more UEs.

[0018] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: receiving the first SIB container via the first signaling, wherein sending the first SIB container includes: relaying the first SIB container without decoding the first SIB container.

[0019] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: transmitting a first service message between the one or more UEs and the first core network service based on sending the first SIB container; and transmitting a second service message between the one or more UEs and the second core network service based on sending the second SIB container.

[0020] A method is described. The method may include: receiving a first SIB container via a DU, the first SIB container including first information associated with communication with a first core network service provided by a service-based network; receiving a second SIB container via the DU, the second SIB container including second information associated with communication with a second core network service provided by the service-based network; transmitting a first service message with the first core network service via the DU based on the first SIB container; and transmitting a second service message with the second core network service via the DU based on the second SIB container.

[0021] A device is described. The device may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the device to perform the following operations: receiving a first SIB container via a DU, the first SIB container including first information associated with communication with a first core network service provided by a service-based network; receiving a second SIB container via the DU, the second SIB container including second information associated with communication with a second core network service provided by the service-based network; transmitting a first service message to the first core network service via the DU based on the first SIB container; and transmitting a second service message to the second core network service via the DU based on the second SIB container.

[0022] Another apparatus is described. The apparatus may include: a unit for receiving a first SIB container via a DU, the first SIB container including first information associated with communication with a first core network service provided by a service-based network; a unit for receiving a second SIB container via the DU, the second SIB container including second information associated with communication with a second core network service provided by the service-based network; a unit for transmitting a first service message to the first core network service via the DU based on the first SIB container; and a unit for transmitting a second service message to the second core network service via the DU based on the second SIB container.

[0023] A non-transitory computer-readable medium storing code is described. The code may include instructions executable by a processor to: receive a first SIB container via a DU, the first SIB container including first information associated with communication with a first core network service provided by a service-based network; receive a second SIB container via the DU, the second SIB container including second information associated with communication with a second core network service provided by the service-based network; transmit a first service message with the first core network service via the DU based on the first SIB container; and transmit a second service message with the second core network service via the DU based on the second SIB container.

[0024] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first signaling, the second signaling, or both may be received according to API information associated with the DU.

[0025] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: receiving an indication from the DU that a SIB container associated with the first core network service can be provided on demand in response to a request from the UE; and sending a request for the first SIB container to the DU based on receiving the indication, wherein the first SIB container can be received in response to the request.

[0026] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: receiving a third SIB container via the DU, the third SIB container including third information associated with communication with the first core network service, wherein transmitting the first service message may be based on receiving the third SIB container.

[0027] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: receiving a third SIB container from the DU, the third SIB container including third information associated with communication between the DU and the UE, wherein transmitting the first service message, the second service message, or both may be based on the third SIB container.

[0028] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: receiving third signaling from the DU indicating first scheduling information associated with the first SIB container and second scheduling information associated with the second SIB container; and monitoring the first SIB container and the second SIB container based on the first scheduling information and the second scheduling information, respectively, wherein receiving the first SIB container and the second SIB container can be based on the monitoring.

[0029] A method is described. The method may include: sending first signaling indicating a SIB configuration associated with a core network service to a DU, the SIB configuration including first information associated with communication with the core network service; sending an instruction to the DU for the DU to transmit the first information to one or more UEs via a first SIB container based on the SIB configuration; and transmitting a service message to a UE among the one or more UEs based on the instruction.

[0030] An apparatus is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to perform the following operations: send a first signaling indicating a SIB configuration associated with a core network service to a DU, the SIB configuration including first information associated with communication with the core network service; send an instruction to the DU for the DU to transmit the first information to one or more UEs via a first SIB container based on the SIB configuration; and transmit a service message to a UE among the one or more UEs based on the instruction.

[0031] Another apparatus is described. The apparatus may include: a unit for sending a first signaling indicating a SIB configuration associated with a core network service to a DU, the SIB configuration including first information associated with communication with the core network service; a unit for sending an instruction to the DU for the DU to transmit the first information to one or more UEs via a first SIB container based on the SIB configuration; and a unit for transmitting a service message to a UE among the one or more UEs based on the instruction.

[0032] A non-transitory computer-readable medium storing code is described. The code may include instructions executable by a processor to perform the following operations: send first signaling indicating a SIB configuration associated with a core network service to a DU, the SIB configuration including first information associated with communication with the core network service; send instructions to the DU for the DU to transmit the first information to one or more UEs via a first SIB container based on the SIB configuration; and transmit a service message to a UE among the one or more UEs based on the instructions.

[0033] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first signaling, the second signaling, or both are sent according to API information associated with the DU.

[0034] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: sending a set of parameters associated with the SIB configuration via the first signaling, wherein the set of parameters includes scheduling information for the first information block container, a size of the first SIB container, a QoS metric for the first SIB container, a delivery delay for the first SIB container, a coverage area for the first SIB container, or any combination thereof.

[0035] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: sending an indication via the first signaling that a SIB container associated with the SIB configuration can be transmitted on demand in response to a request from the one or more UEs, wherein transmitting the service message can be based on the indication.

[0036] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: receiving API information associated with the DU, wherein sending the first signaling to the DU, sending the instruction to the DU, or both may be based on the API information.

[0037] Some examples of the methods, devices, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: receiving second signaling indicating API information associated with the DU from the DU, a second core network service, or both, wherein the first signaling may be sent based on the application programming interface information.

[0038] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the SIB configuration also includes second information associated with communications with the core network service, and the methods, apparatus, and non-transitory computer-readable media may also include operations, features, units, or instructions for performing the following operations: sending instructions to the DU for the DU to transmit the second information to the one or more UEs via a second SIB container. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] Figure 1 An example of a wireless communication system supporting techniques for system information broadcast in a service-based wireless system in accordance with one or more aspects of the present disclosure is shown.

[0040] Figure 2 An example of a wireless communication system supporting techniques for system information broadcast in a service-based wireless system in accordance with one or more aspects of the present disclosure is shown.

[0041] Figure 3 An example of a network architecture supporting techniques for system information broadcast in a service-based wireless system in accordance with one or more aspects of the present disclosure is shown.

[0042] Figure 4 An example of a wireless communication system supporting techniques for system information broadcast in a service-based wireless system in accordance with one or more aspects of the present disclosure is shown.

[0043] Figure 5 An example of a process flow supporting techniques for system information broadcast in a service-based wireless system in accordance with one or more aspects of the present disclosure is shown.

[0044] Figure 6 and 7 A block diagram of a device supporting techniques for system information broadcast in a service-based wireless system in accordance with one or more aspects of the present disclosure is shown.

[0045] Figure 8 A block diagram of a communications manager supporting techniques for system information broadcast in a service-based wireless system is shown in accordance with one or more aspects of the present disclosure.

[0046] Fig. 9 A diagram of a system including devices supporting techniques for system information broadcast in a service-based wireless system is shown in accordance with one or more aspects of the present disclosure.

[0047] Fig.10 and 11A block diagram of a device supporting techniques for system information broadcast in a service-based wireless system in accordance with one or more aspects of the present disclosure is shown.

[0048] Fig.12 A block diagram of a communications manager supporting techniques for system information broadcast in a service-based wireless system is shown in accordance with one or more aspects of the present disclosure.

[0049] Fig.13 A diagram of a system including devices supporting techniques for system information broadcast in a service-based wireless system is shown in accordance with one or more aspects of the present disclosure.

[0050] Figures 14 to 17 A flow chart illustrating a method of supporting techniques for system information broadcast in a service-based wireless system in accordance with one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0051] Some wireless systems may exhibit a relatively vertical layered architecture that includes many different "layers" of devices that perform functions for the system. For example, a wireless system may include user equipment (UE), base stations / network entities, and a large number of back-end (e.g., core network) devices associated with one or more functions for the system. This layered structure may result in processing and other functions being performed on multiple devices (e.g., duplicate processing or capabilities across multiple back-end devices), resulting in wasted resources and excessive power consumption. In addition, the back-end architecture of some wireless systems may be owned and maintained by a small number of operators, which may make it difficult for other parties / entities to integrate with the system and may complicate the system's ability to provide customized services and functions to wireless devices.

[0052] In contrast, some wireless systems (such as sixth generation (6G) systems) may exhibit a flatter service-based architecture, in which a radio access network (RAN) (e.g., a network entity) interfaces with a service-based network to connect UEs to core network services maintained at various network addresses within the service-based network. In the context of a service-based system, operations and functions that might otherwise be performed by a few centralized backend components (e.g., in some systems) may be distributed across multiple core network services that may be hosted at different network addresses, such as in a cloud-based architecture. Thus, a UE in a service-based system is able to establish and maintain connections (e.g., "subscriptions") with different core network services or groups thereof on an aàla carte basis, where each core network service supplies or provides a respective network function or service. For example, a service-based system may include mobility services, security services, privacy services, location services, etc. In this regard, each UE within a service-based system is able to select which core network services the UE will subscribe to based on the personalized characteristics or needs of the respective UE.

[0053] In the context of a service-based wireless system (such as a service-based 6G network), different core network services may be expected to share information (e.g., system information, such as system information block (SIB) messages / containers) with UEs and other wireless devices in the network so that the corresponding devices can communicate with the core network services. In some traditional systems (e.g., 5G networks), a network entity may receive system information from a core network, decode the system information, and encapsulate the system information into a SIB that is broadcast to the UE. However, requiring a network entity to decode and encapsulate SIBs for a large number of core network services may result in increased complexity and processing power at the network entity. In addition, compared to some traditional systems that exhibit a centralized backend network that compiles and encapsulates system information to be distributed throughout the network, a service-based system may include many different core network services associated with different operators, protocols, and communication parameters. Therefore, each corresponding core network service may have its own system information to be broadcast, which further complicates the communication of system information within a service-based architecture.

[0054] Thus, aspects of the present disclosure relate to signaling, configuration, and other mechanisms for distributing system information (e.g., SIBs) in a service-based wireless system. In particular, aspects of the present disclosure relate to signaling that enables a network entity (e.g., a distributed unit (DU)) to compile SIB configurations for a plurality of different core network services and distribute SIBs for the corresponding core network services according to the acquired SIB settings.

[0055] For example, a service-based network may include a first core network service and a second core network service. In this example, the network entity may receive a first SIB configuration from the first core network service and a second SIB configuration from the second core network service. The SIB configuration may indicate a SIB container (e.g., a SIB message) to be relayed by the network entity to the UE. In some cases, the corresponding SIB configuration may indicate various parameters for sending / broadcasting the SIB container, including scheduling information for the SIB container, the size of the SIB container, the coverage area for the corresponding SIB container, whether the SIB container will be provided on demand (e.g., in response to a request from the UE), etc. The network entity may then send / broadcast different SIB containers for core network services according to the corresponding SIB configuration.

[0056] In some implementations, a network entity may be configured to broadcast / relay a SIB container received from a core network service without decoding the SIB container. In other words, the SIB container included in the SIB configuration may be transparent to the network entity. In contrast, other portions of the SIB configuration (e.g., parameters for transmitting the SIB container, such as scheduling information) may be decoded by the network entity so that the network entity may distribute the SIB container according to the corresponding parameters. In some aspects, the network entity may indicate application programming interface (API) information to the corresponding core network service, wherein the API information enables the core network service to generate and format signaling in such a manner that the network entity can receive the SIB configuration, decode the parameters for SIB communication, and / or relay / broadcast the SIB container according to the parameters.

[0057] Aspects of the disclosure are first described in the context of a wireless communication system. Additional aspects of the disclosure are described in the context of an example network architecture and an example process flow. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flow diagrams relating to techniques for broadcasting system information in a service-based wireless system.

[0058] Figure 1An example of a wireless communication system 100 supporting techniques for capability indication for multiple services in a service-based wireless system in accordance with one or more aspects of the present disclosure is shown. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a service-based network 130. In some examples, the wireless communication system 100 may implement aspects of a 6G network, a 5G network (e.g., a New Radio (NR) network), a 4G network (e.g., a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network), or a network operating according to other systems and radio technologies (including future systems and radio technologies not explicitly mentioned herein).

[0059] The network entities 105 may be dispersed throughout a geographic area to form the wireless communication system 100, and may include devices of different forms or with different capabilities. In various examples, the network entities 105 may be referred to as network elements, mobility elements, radio access network (RAN) nodes, access points, or network devices, among other terms. In some examples, the network entities 105 and the UE 115 may communicate wirelessly via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, the network entity 105 may support a coverage area 110 (e.g., a geographic coverage area), and the UE 115 and the network entity 105 may establish one or more communication links 125 over the coverage area 110. The coverage area 110 may be an example of a geographic area over which the network entity 105 and the UE 115 may support transmitting signals according to one or more radio access technologies (RATs).

[0060] UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary, mobile, or both at different times. UEs 115 may be devices of different forms or with different capabilities. Figure 1 Some example UEs 115 are shown in FIG. 1. The UEs 115 described herein are capable of supporting communications with various types of devices (such as other UEs 115 or network entities 105), such as Figure 1 shown.

[0061] As described herein, a node (which may be referred to as a network node) or a wireless node of the wireless communication system 100 may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, the node may be a UE 115. As another example, the node may be a network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of the example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a UE 115. In another aspect of the example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a network entity 105. In other aspects of the example, the first node, the second node, and the third node may be different relative to these examples. Similarly, references to UE 115, network entity 105, apparatus, device, computing system, etc. may include disclosure of UE 115, network entity 105, apparatus, device, computing system, etc. as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that the first node is configured to receive information from the second node.

[0062] In some examples, the network entities 105 can communicate with the service-based network 130, or communicate with each other, or both. For example, the network entities 105 can communicate with the service-based network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3, or other interface protocols). Similarly, one or more UEs 115 can communicate with the service-based network 130 via communication links 155. In some examples, the network entities 105 can communicate with each other directly (e.g., directly between the network entities 105) or indirectly (e.g., via the service-based network 130) via the backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, the network entities 105 can communicate with each other via one or more communication links such as the fronthaul communication link 168 (e.g., between the radio unit 170 and the distributed unit 165). The backhaul communication link 120 or the fronthaul communication link 168, or other communication links between the network entities 105, may be or include one or more wired links (e.g., electrical links, fiber optic links), one or more wireless links (e.g., radio links, wireless optical links), and other examples or various combinations thereof.

[0063] In some examples, the network entity 105 can communicate with a service platform 150 (e.g., a cloud platform) that provides one or more core network services (CN services), one or more radio access network services (RAN services), or any combination thereof (CN / RAN services 185). The CN / RAN services can be provided via the service-based network 130 using one or more APIs. For example, one or more DU service APIs 175 can provide an interface for one or more services at the UE 115. The services at the UE 115 can correspond to one or more CN / RAN services 185 at the service platform 150. For example, the network service API 180 at the service-based network 130 can interface with a corresponding DU service API 175 at the DU 165, which interfaces with a corresponding API at the UE 115 to provide service connectivity between the one or more UE 115 services and the corresponding CN / RAN services 185.

[0064] One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., a base station transceiver, a radio base station, an access point, a radio transceiver, a node B, an evolved node B (eNB), a next generation node B, or a gigabit node B (any of which may be referred to as a gNB), a 5G NB, a next generation eNB (ng-eNB), a home node B, a home evolved node B, a 6G NB, or other suitable terms). In some examples, the network entity 105 (e.g., a base station 140) may be implemented in an aggregated (e.g., monolithic, independent) base station architecture that may be configured to utilize a service-based architecture and provide radio access within a single network entity 105 (e.g., a single RAN node such as a base station 140 may include a RU 170, a DU 165, and a DU API 175 for a CN / RAN service 185). The RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmit receive point (TRP).

[0065] Additionally, in some examples, one or more network entities 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that may be configured to utilize a protocol stack that is physically or logically distributed across two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entity 105 may include one or more of the following: a central unit (CU), a DU 165, a RU 170, a RAN intelligent controller (RIC) (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) system, or any combination thereof. One or more components of the network entity 105 in the disaggregated RAN architecture may be co-located, or one or more components of the network entity 105 may be located at distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of the disaggregated RAN architecture may be implemented as virtual units (eg, virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0066] The functional split between components (e.g., CU, DU, and RU) is flexible and can support different functionalities, depending on which functions are performed at the component (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof). For example, a functional split of the protocol stack can be adopted between the CU and DU 165, so that the CU can support one or more layers of the protocol stack and the DU 165 can support one or more different layers of the protocol stack. In some examples, the CU can host upper layer protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionality and signaling (e.g., Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). In some examples, the CU can host one or more service APIs for one or more CN / RAN services 185 via the corresponding network service API 180 of the service-based network 130. The CU may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layer functionality and signaling, such as Layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer), and may each be at least partially controlled by the CU. Additionally or alternatively, a functional split of the protocol stack may be employed between the DUs 165 and RUs 170, such that the DUs 165 may support one or more layers of the protocol stack, and the RUs 170 may support one or more different layers of the protocol stack. The DUs 165 may support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional split between the CU and DU 165 or between the DU 165 and the RU 170 may be within the protocol layer (e.g., some functions of the protocol layer may be performed by one of the CU, DU 165, or RU 170, while other functions of the protocol layer are performed by a different one of the CU, DU 165, or RU 170). The DU 165 may be connected to one or more RUs 170 via a fronthaul communication link 168 (e.g., an open fronthaul (FH) interface). In some examples, the fronthaul communication link 168 may be implemented according to an interface (e.g., a channel) between layers of a protocol stack supported by a corresponding network entity 105 communicating via such a communication link.

[0067] In a wireless communication system (e.g., wireless communication system 100), infrastructure and spectrum resources for wireless access may support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to a service-based network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DUs 165 or one or more RUs 170 may be partially controlled by a donor network entity 105 (e.g., a donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120). The IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a DU 165 of a coupled IAB donor. The IAB-MT may include an independent set of antennas for relaying communications with the UE 115, or may share the same antennas of the IAB node 104 (e.g., the same antennas of the RU 170) for access via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, the IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration of an access network (e.g., downstream). In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of the IAB node 104) may be configured to operate according to the techniques described herein.

[0068] Where the techniques described herein are applied in the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture may be configured to support the techniques for system information broadcast in a service-based wireless system as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may be performed in addition or alternatively by one or more components of the decomposed RAN architecture (e.g., an IAB node 104, a DU 165, a CU, a RU 170, a RIC, a SMO).

[0069] UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other appropriate terminology, where a "device" may also be referred to as a unit, a station, a terminal, or a client, among other examples. UE 115 may also include or may be referred to as a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, UE 115 may include or be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, among other examples, which may be implemented in various items such as appliances, or vehicles, meters, and among other examples.

[0070] The UE 115 described herein may be able to communicate with various types of devices, such as other UEs 115, which may sometimes act as relays, as well as network entities 105 and network devices (including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, among other examples), such as Figure 1 shown.

[0071] The UE 115 and the network entity 105 can communicate with each other wirelessly via one or more communication links 125 (e.g., access links) using resources associated with one or more carriers. The term "carrier" can refer to a set of RF spectrum resources having a defined physical layer structure for supporting the communication link 125. For example, a carrier for the communication link 125 may include a portion of an RF spectrum band (e.g., a bandwidth portion (BWP)) that operates according to one or more physical layer channels for a given radio access technology (e.g., 4G, 5G, 6G radio access technology). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling for coordinating operations for the carrier, user data, or other signaling. The wireless communication system 100 may support communication with the UE 115 using carrier aggregation or multi-carrier operation. According to the carrier aggregation configuration, the UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used with both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers. Communication between the network entity 105 and other devices may refer to communication between a device and any portion (e.g., entity, sub-entity) of the network entity 105. For example, when referring to the network entity 105, the terms "sending," "receiving," or "communicating" may refer to any portion of the network entity 105 (e.g., base station 140, CU, DU 165, RU 170) of the RAN communicating with another device (e.g., directly or via one or more other network entities 105).

[0072] In some examples (e.g., in a carrier aggregation configuration), a carrier may also have acquisition signaling or control signaling to coordinate operations for other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be identified based on a channel grid for discovery by a UE 115. A carrier may operate in a standalone mode, in which case a UE 115 may perform initial acquisition and connection via the carrier, or a carrier may operate in a non-standalone mode, in which case a different carrier (e.g., of the same or different radio access technology) is used to anchor the connection.

[0073] The communication links 125 shown in the wireless communication system 100 may include downlink transmissions (e.g., forward link transmissions) from the network entity 105 to the UE 115, uplink transmissions (e.g., return link transmissions) from the UE 115 to the network entity 105, or both, as well as other configurations of transmissions. A carrier may carry downlink or uplink communications (e.g., in FDD mode) or may be configured to carry both downlink and uplink communications (e.g., in TDD mode).

[0074] A carrier may be associated with a particular bandwidth of the RF spectrum, and in some examples, the carrier bandwidth may be referred to as the "system bandwidth" of the carrier or wireless communication system 100. For example, the carrier bandwidth may be one of a set of bandwidths for carriers of a particular radio access technology (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz (MHz)). Devices of the wireless communication system 100 (e.g., the network entity 105, the UE 115, or both) may have a hardware configuration that supports communications using a particular carrier bandwidth, or may be configurable to support communications using one of the carrier bandwidths in the set of carrier bandwidths. In some examples, the wireless communication system 100 may include a network entity 105 or a UE 115 that supports concurrent communications using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate using a portion (e.g., subband, BWP) or all of the carrier bandwidth.

[0075] The signal waveform transmitted via the carrier wave may be composed of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system using MCM techniques, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and the subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both), so that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high order modulation scheme may correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, time resources, and spatial resources (e.g., spatial layers, beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0076] One or more numerologies for a carrier may be supported, and the numerologies may include subcarrier spacing (Δf) and cyclic prefixes. A carrier may be divided into one or more BWPs with the same or different numerologies. In some examples, a UE 115 may be configured with multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time, and communications for a UE 115 may be limited to one or more active BWPs.

[0077] The basic time unit (which may be referred to as T s =1 / (Δf max ·N f ) seconds sampling period, where Δf max It can indicate the supported subcarrier spacing, and N f The time intervals for the network entity 105 or the UE 115 may be expressed as multiples of a supported discrete Fourier transform (DFT) size). The time intervals of the communication resources may be organized according to radio frames each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0078] Each frame may include a plurality of consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into a number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a number of symbol periods (e.g., depending on the length of a cyclic prefix added in front of each symbol period). In some wireless communication systems 100, a time slot may be further divided into a plurality of micro-time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., N) time slots. f The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.

[0079] A subframe, a time slot, a mini-time slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100 and may be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., the number of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in the form of bursts of shortened TTIs (sTTIs)).

[0080] Physical channels may be multiplexed according to various techniques to communicate using carriers. For example, physical control channels and physical data channels may be multiplexed using one or more of a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique to signal via a downlink carrier. A control region (e.g., a control resource set (CORESET)) for a physical control channel may be defined by a set of symbol periods and may extend across a system bandwidth or a subset of a system bandwidth of a carrier. One or more control regions (e.g., CORESETs) may be configured for a group of UEs 115. For example, one or more of the UEs 115 may monitor or search a control region for control information according to one or more search space sets, and each search space set may include one or more control channel candidates at one or more aggregation levels arranged in a cascaded manner. The aggregation level for a control channel candidate may refer to the number of control channel resources (e.g., control channel elements (CCEs)) associated with coding information for a control information format having a given payload size. The search space sets may include a common search space set configured for transmitting control information to multiple UEs 115 and a UE-specific search space set for transmitting control information to a specific UE 115 .

[0081] The network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hot spots or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used to communicate with the network entity 105 (e.g., using a carrier), and may be associated with an identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or other identifier) ​​used to distinguish adjacent cells. In some examples, a cell may also refer to a coverage area 110 or a portion of a coverage area 110 (e.g., a sector) on which a logical communication entity operates. Depending on various factors (such as the capabilities of the network entity 105), such a cell may range from a smaller area (e.g., a structure, a subset of a structure) to a larger area. For example, a cell may be or include a building, a subset of a building, or an external space between or overlapping coverage areas 110, as well as other examples.

[0082] A macro cell typically covers a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by a UE 115 with a service subscription to a network provider that supports the macro cell. A small cell may be associated with a lower-power network entity 105 (e.g., a lower-power base station 140) than a macro cell, and the small cell may operate using the same or different (e.g., licensed, unlicensed) frequency band as the macro cell. A small cell may provide unrestricted access to a UE 115 with a service subscription to a network provider, or may provide restricted access to a UE 115 associated with a small cell (e.g., a UE 115 in a closed subscriber group (CSG), a UE 115 associated with a user in a residence or office). A network entity 105105 may support one or more cells, and may also support communication via one or more cells using one or more component carriers.

[0083] In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB)) that may provide access to different types of devices.

[0084] In some examples, the network entities 105 (e.g., base stations 140, RUs 170) may be mobile and, therefore, provide communication coverage for mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 provide coverage for respective coverage areas 110 using the same or different radio access technologies.

[0085] Some UEs 115 (e.g., MTC or IoT devices) may be low-cost or low-complexity devices and may provide automated communications between machines (e.g., via machine-to-machine (M2M) communications). M2M communications or MTC may refer to data communications technology that allows devices to communicate with each other or a network entity 105 (e.g., a base station 140) without human intervention. In some examples, M2M communications or MTC may include communications from devices that integrate sensors or meters to measure or capture information and relay such information to a central server or application that utilizes the information or presents the information to a human interacting with the application. Some UEs 115 may be designed to collect information or implement automated behavior of machines or other devices. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, climate and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based service billing.

[0086] The wireless communication system 100 can be configured to support ultra-reliable communication or low-latency communication, or various combinations thereof. For example, the wireless communication system 100 can be configured to support ultra-reliable low-latency communication (URLLC). UE 115 can be designed to support ultra-reliable, low-latency or critical functions. Ultra-reliable communication can include private communication or group communication, and can be supported by one or more services (such as push-to-talk, video or data). Support for ultra-reliable, low-latency functions can include prioritization of services, and such services can be used for public safety or general commercial applications. The terms ultra-reliable, low-latency and ultra-reliable low-latency can be used interchangeably in this article.

[0087] In some examples, the UE 115 may be configured to support direct communication with other UEs 115 via a device-to-device (D2D) communication link 135 (e.g., according to a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 of a group that are performing D2D communication may be within a coverage area 110 of a network entity 105 (e.g., a base station 140, a RU 170), and the network entity 105 may support aspects of such D2D communication configured by the network entity 105 (e.g., scheduled by the network entity 105). In some examples, one or more UEs 115 in such a group may be outside the coverage area 110 of the network entity 105 or may otherwise be unable or not configured to receive transmissions from the network entity 105. In some examples, groups of UEs 115 communicating via D2D communication may support a one-to-many (1:M) system, in which each UE 115 transmits to each of the other UEs 115 in the group. In some examples, network entity 105 may facilitate scheduling of resources for D2D communications. In some other examples, D2D communications may be performed between UEs 115 without involving network entity 105.

[0088] In some systems, the D2D communication link 135 can be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some examples, vehicles can communicate using vehicle-to-everything (V2X) communication, vehicle-to-vehicle (V2V) communication, or some combination of these items. Vehicles can use signals to send information related to traffic conditions, signal scheduling, weather, safety, emergency situations, or any other information related to the V2X system. In some examples, vehicles in a V2X system can communicate with roadside infrastructure (such as roadside units), or communicate with a network via one or more network nodes (e.g., network entity 105, base station 140, RU 170) using vehicle-to-network (V2N) communication, or both.

[0089] In some deployments, one or more UEs 115 or network entities 105 may access multiple RANs, such as 6G RAT and 5G RAT. In some examples, 6G RAT may be associated with a service-based network 130, and 5G RAT may be associated with a 5G core 190. The 5G core 190 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The 5G core 190 may be an evolved packet core (EPC), which may include at least one control plane entity (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) that manages access and mobility, and at least one user plane entity (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)) that routes packets to an external network or interconnects to an external network. The control plane entities may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management for UEs 115 served by network entities 105 (e.g., base stations 140) associated with the 5G core 190. User IP packets may be transported through user plane entities, which may provide IP address allocation and other functions. The user plane entities may be connected to IP services 195 for one or more network operators. IP services 195 may include access to the Internet, an intranet, an IP multimedia subsystem (IMS), or a packet-switched streaming service.

[0090] The wireless communication system 100 may operate using one or more frequency bands, which may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Typically, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band, because the wavelengths range from approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but the waves may be sufficient to penetrate the structure for macro cells to provide service to UEs 115 located indoors. Communications using UHF waves may be associated with smaller antennas and shorter distances (e.g., less than 100 kilometers) compared to communications using smaller frequencies and longer waves in the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0091] The wireless communication system 100 may also operate using a super high frequency (SHF) region that may be in the range of from 3 GHz to 30 GHz (also referred to as a centimeter band) or an extremely high frequency (EHF) region (e.g., from 30 GHz to 300 GHz) (also referred to as a millimeter band) using a spectrum. In some examples, the wireless communication system 100 may support millimeter wave (mmW) communications between UE 115 and a network entity (e.g., base station 140, RU 170), and the EHF antenna of the corresponding device may be smaller and more closely spaced than the UHF antenna. In some examples, such technology may facilitate the use of antenna arrays within the device. However, the propagation of EHF transmissions may suffer from even greater attenuation and shorter distances than SHF or UHF transmissions. The technology disclosed herein may be employed across transmissions using one or more different frequency regions, and the designated use of frequency bands across these frequency regions may differ according to countries or regulatory agencies.

[0092] The wireless communication system 100 can utilize both licensed and unlicensed RF spectrum bands. For example, the wireless communication system 100 can employ licensed assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology using unlicensed bands (such as the 5 GHz industrial, scientific, and medical (ISM) band). When operating using unlicensed RF spectrum bands, devices (such as network entities 105 and UE 115) can employ carrier sensing for conflict detection and avoidance. In some examples, operations using unlicensed bands can be based on a carrier aggregation configuration of component carriers in combination with operations using licensed bands (e.g., LAA). Operations using unlicensed spectrum can include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, as well as other examples.

[0093] The network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas, which may be used to employ technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of the network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels (which may support MIMO operations or transmit or receive beamforming). For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly (e.g., an antenna tower). In some examples, antennas or antenna arrays associated with the network entity 105 may be located at different geographical locations. The network entity 105 may include an antenna array having a set of rows and columns of antenna ports that the network entity 105 may use to support beamforming for communications with the UE 115. Similarly, the UE 115 may include one or more antenna arrays that may support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals sent via the antenna ports.

[0094] The network entity 105 or UE 115 can use MIMO communication to exploit multipath signal propagation and improve spectral efficiency by sending or receiving multiple signals via different spatial layers. Such technology can be referred to as spatial multiplexing. For example, a transmitting device can send multiple signals via different antennas or different combinations of antennas. Similarly, a receiving device can receive multiple signals via different antennas or different combinations of antennas. Each of the multiple signals can be referred to as a separate spatial stream and can carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers can be associated with different antenna ports for channel measurement and reporting. MIMO technology includes single-user MIMO (SU-MIMO) (where multiple spatial layers are sent to the same receiving device) and multi-user MIMO (MU-MIMO) (where multiple spatial layers are sent to multiple devices).

[0095] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to form or direct an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming can be achieved by combining signals transmitted via antenna elements of an antenna array so that some signals propagating along a specific orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals transmitted via antenna elements may include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to signals carried via antenna elements associated with the device. Adjustments associated with each of the antenna elements may be defined by a set of beamforming weights associated with a specific orientation (e.g., relative to the antenna array of the transmitting device or the receiving device, or relative to some other orientation).

[0096] The network entity 105 or UE 115 may use beam scanning techniques as part of a beamforming operation. For example, the network entity 105 (e.g., base station 140, RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communications with UE 115. The network entity 105 may send some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) multiple times along different directions. For example, the network entity 105 may send signals according to different sets of beamforming weights associated with different transmission directions. Transmissions along different beam directions may be used (e.g., by a transmitting device (such as network entity 105) or by a receiving device (such as UE 115)) to identify a beam direction for subsequent transmission or reception by the network entity 105.

[0097] A transmitting device (e.g., transmitting network entity 105, transmitting UE 115) may transmit some signals (e.g., data signals associated with a specific receiving device (e.g., receiving network entity 105 or receiving UE 115)) along a single beam direction (e.g., a direction associated with the receiving device). In some examples, the beam direction associated with the transmission along the single beam direction may be determined based on signals transmitted along one or more beam directions. For example, UE 115 may receive one or more of the signals transmitted by network entity 105 along different directions, and may report to network entity 105 an indication of the signal received by UE 115 having the highest signal quality or otherwise acceptable signal quality.

[0098] In some examples, transmissions by a device (e.g., by network entity 105 or UE 115) may be performed using multiple beam directions, and the device may generate a combined beam for transmission (e.g., from network entity 105 to UE 115) using a combination of digital precoding or beamforming. UE 115 may report feedback indicating precoding weights for one or more beam directions, and the feedback may correspond to a configured set of beams across a system bandwidth or one or more subbands. Network entity 105 may send reference signals (e.g., cell-specific reference signals (CRS), channel state information reference signals (CSI-RS)) that may be precoded or not precoded. UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-panel type of codebook, a linear combination type of codebook, a port selection type of codebook). Although these techniques are described with reference to signals sent along one or more directions by a network entity 105 (e.g., base station 140, RU 170), UE 115 may employ similar techniques to send signals multiple times along different directions (e.g., for identifying a beam direction for subsequent transmission or reception by UE 115) or to send signals along a single direction (e.g., for sending data to a receiving device).

[0099] When receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from a receiving device (e.g., network entity 105), the receiving device (e.g., UE 115) can perform receiving operations according to multiple receiving configurations (e.g., directional listening). For example, the receiving device can receive according to multiple receiving directions by receiving via different antenna subarrays, by processing received signals according to different antenna subarrays, by receiving according to different receiving beamforming weight sets applied to signals received at multiple antenna elements of an antenna array (e.g., different directional listening weight sets), or by processing received signals according to different receiving beamforming weight sets applied to signals received at multiple antenna elements of an antenna array (any of the above operations may be referred to as "listening" according to different receiving configurations or receiving directions). In some examples, the receiving device can use a single receiving configuration to receive along a single beam direction (e.g., when receiving a data signal). A single receive configuration may be aligned along a beam direction determined based on listening according to different receive configuration directions (e.g., a beam direction determined to have the highest signal strength, the highest signal-to-noise ratio (SNR), or otherwise acceptable signal quality based on listening according to multiple beam directions).

[0100] In some examples, the wireless communication system 100 may include a packet-based network that operates using a cloud platform, such as a service platform 150 that provides CN / RAN services 185. In some examples, the CN / RAN services 185 may be hosted based on the capabilities of the deployment topology and service parameters associated with each service. Providing the CN / RAN services 185 allows for separation of specific services (e.g., mobility, connection state management, security, paging, radio access services, quality of service (QoS) configuration and data services, UE capability management, location, messaging, etc.) from transport functions (e.g., data radio bearer (DRB) and logical channel (LC) management, data service configuration, etc.). Service-based functions (e.g., message brokers decouple radio network processes from network delivery mechanisms) may allow for the flexibility of hosting some functions (e.g., layer 2 (L2) functions) anywhere in the cloud, and may enable enhanced scalability, resilience, elasticity, agility, reuse, visibility, automation, failover, or any combination thereof (e.g., each service across the RAN and core network may be independently scalable by independently increasing or decreasing resources allocated across the functions). Furthermore, efficiency may be enhanced by providing real-time link management to the RAN edge and allowing adaptation at the DU 165 to more efficiently activate, deactivate, or select features based on UE conditions.

[0101] In some implementations, the wireless communication system 100 supports signaling, configuration, and other mechanisms for distributing system information (e.g., SIB) in a service-based wireless system. In particular, the wireless communication system 100 may support signaling that enables the network entity 105 (e.g., DU) to compile SIB configurations for multiple different core network services (e.g., CN / RAN services 185) of the service-based network 130, and distribute SIBs for the corresponding core network services according to the acquired SIB configurations.

[0102] For example, the service-based network 130 may include a first core network service (e.g., a first CN / RAN service 185) and a second core network service (e.g., a second CN / RAN service 185). In this example, the network entity 105 may receive a first SIB configuration from the first core network service and a second SIB configuration from the second core network service. The SIB configuration may indicate a SIB container (e.g., a SIB message) to be relayed by the network entity 105 to the UE 115. In some cases, the corresponding SIB configuration may indicate various parameters for sending / broadcasting the SIB container, including scheduling information for the SIB container, the size of the SIB container, the coverage area for the corresponding SIB container, whether the SIB container will be provided on demand (e.g., in response to a request from the UE 115), etc. The network entity 105 may then send / broadcast different SIB containers for the core network services according to the corresponding SIB configuration.

[0103] In some implementations, the network entity 105 may be configured to broadcast / relay SIB containers received from the core network service without decoding the SIB containers. In other words, the SIB containers included in the SIB configuration may be transparent to the network entity 105. In contrast, other portions of the SIB configuration (e.g., parameters for transmitting the SIB container, such as scheduling information) may be decoded by the network entity 105 so that the network entity may distribute the SIB container according to the corresponding parameters. In some aspects, the network entity 105 may indicate API information to the corresponding core network service, wherein the API information enables the core network service to generate and format signaling in such a manner that the network entity 105 can receive the SIB configuration, decode the parameters for SIB communication, and relay / broadcast the SIB container according to the parameters.

[0104] The techniques described herein may enable the network entity 105 to broadcast system information to the UE 115 on behalf of the core network services of the service-based network 130. In addition, the techniques described herein may enable the network entity 105 to receive SIB containers from the core network services and relay the SIB containers to the UE 115 without decoding the corresponding SIB containers (e.g., transparent SIB containers). In this regard, aspects of the present disclosure may enable the network entity 105 to efficiently aggregate system information from multiple core network services and relay the system information to other wireless devices, thereby enabling efficient communication of system information and facilitating more efficient and reliable wireless communications. In addition, by enabling the network entity 105 to relay SIB containers without decoding the SIB containers, the techniques described herein may reduce processing requirements at the network entity 105, thereby reducing network complexity and power consumption.

[0105] Figure 2An example of a wireless communication system that supports techniques for broadcasting system information in a service-based wireless system according to one or more aspects of the present disclosure is shown. Aspects of the wireless communication system 200 may implement aspects of or be implemented by aspects of the wireless communication system 100. In some implementations, the wireless communication system 200 illustrates a service-based wireless communication system (such as a wireless communication system based on a wireless communication service). Figure 1 An example architecture of a 6G network described herein.

[0106] The wireless communication system 200 may include one or more UEs 115 (e.g., UE 115-a), one or more network entities (e.g., network entity 105-a), and a service-based network 205. In some aspects, the service-based network 205 may be configured to communicate or interface with a RAN 210 of the wireless communication system 200, wherein the RAN 210 includes one or more network entities (e.g., network entity 105-a). The service-based network 205 may support or provide a set of core network services 215 (e.g., core network services 215-a, 215-b, 215-c, 215-d, 215-d, and 215-e). In some implementations, the service-based network 205 may include a cloud platform or be associated with a cloud platform, wherein the corresponding core network services 215 are hosted at corresponding network addresses in the cloud platform.

[0107] The UE 115-a may communicate with the network entity 105-a using one or more communication links 220, which may include an example of an access link (e.g., a Uu link). The communication link 220 may include a bidirectional link, which may include uplink communication and downlink communication. Similarly, the network entity 105-a of the RAN 210 may be configured to communicate (e.g., dock) with the service-based network 205 via one or more communication links (e.g., communication link 225), wherein the communication link 215 may be configured to facilitate bidirectional communication between the network entity 105-a and the corresponding core network service 215 of the service-based network 205.

[0108] like Figure 2As shown, the wireless communication system 200 may present a service-based architecture in which entities of the RAN 210 (e.g., the network entity 105-a) are configured to connect the UE 115-a to the core network services 215 of the service-based network 205. In particular, the RAN 210 (e.g., the network entity 105-a) may be configured to relay communications between the UE 115-a and various core network services 215 of the service-based network to enable the UE 115-a to establish and maintain a wireless connection 215 with the corresponding core network service in order to exchange communications associated with various network functions supported by the corresponding core network service 215. In other words, the wireless communication system 200 may enable the UE 115-a to "subscribe" to the corresponding core network services 215 on a per-order basis, based on the needs or requirements of the UE 115-a. In this regard, different UEs 115 within the wireless communication system 200 may be able to subscribe to different subsets of the core network services 215 based on the capabilities of the UE 115, the applications executed at the UE 115, the mobility of the UE 115, etc.

[0109] Each core network service 215 can be associated with a corresponding network address within the service-based network 205. In other words, each core network service 215 can be hosted at one or more components of a cloud-based network, wherein the components of each core network service 215 can be associated with a corresponding network address. The corresponding core network service 215 can be provided by a network provider, a third-party entity, etc., wherein each core network service 215 is configured to support a corresponding service or function provided to a component (e.g., UE 115-a, network entity 105-a) of the wireless communication system 200.

[0110] The different services, functions, and core network functions that the corresponding core network services 215 can support or provide can include, but are not limited to, mobility services, security services, privacy services, location services, etc. For example, the first core network service 215-a may include a core network mobility service that hosts information and provides signaling that facilitates the geographic mobility of the UE 115-a throughout the wireless communication system. As another example, the second core network service 215-b may include a security service that provides security and encryption services to subscribing UEs 115 within the wireless communication system 200.

[0111] In some aspects, each core network service 215 may include a corresponding API configured to facilitate wireless communications with the network entity 105-a and the UE 115-a, such as Figure 1. The API at the corresponding core network service 215 may include a routing API, a configuration API, or both. The routing API may be configured for service data unit communication between the UE 115-a and the corresponding core network service 215. In contrast, the configuration API may be configured to facilitate communication between the network entity 105-a and the corresponding core network service 215 to negotiate service requirements and service specific operations.

[0112] In some aspects, the network entity 105-a (e.g., eDU) can facilitate traffic routing (e.g., service data unit routing) from the UE 115-a to the core network service 215, and vice versa. The network entity 105-a can facilitate traffic routing between the respective devices directly, via other network entities 105-a, via a proxy, or any combination thereof. In addition, in some cases, the UE 115-a can be communicatively coupled to multiple network entities 105 (e.g., dual connectivity), wherein the multiple network entities 105 facilitate traffic routing with the same or different groups of core network services 215. In addition, the network entity 105-a can support service configurations or service contexts associated with communication parameters within the system, such as QoS flows, security, and UE 115 service contexts. In some aspects, the communication link 220 between the network entity 105-a and the UE 115-a can be associated with an access layer configuration that facilitates air service awareness. The access layer configuration can include logical channels, access layer security, access layer contexts, and the like. For example, access layer configuration may be associated with service specific configuration (eg, logical channels corresponding to QoS flows for each respective core network service 215) and service agnostic configuration (eg, parameters common to all core network services 215).

[0113] Compared to some other types of wireless systems, such as networks that instead exhibit a relatively more vertical layered architecture that includes multiple "layers" of different devices that perform the functions of the network, Figure 2 The service-based wireless communication system 200 (e.g., a 6G network) shown in FIG. 2 may exhibit several differences and advantages. A more layered structure may result in processing and other functions being performed at multiple devices (e.g., the network entity 105 and one or more backend devices), resulting in inefficient use of resources and high power consumption. In addition, the backend architecture of a network with a more vertical layered architecture may be owned and maintained by a few operators, which may make it difficult for other parties / entities to integrate with such a system, and the services provided to the UE 115 and other devices may be difficult to customize within such a system.

[0114] In contrast, Figure 2The service-based wireless communication system 200 shown in exemplifies a flatter horizontal architecture that enables the respective functions of the wireless communication system to be distributed across different components of the system (e.g., core network services 215). For example, such functions and protocols may be partitioned and distributed across a set of core network services 215 such that each core network service 215 may support or enable a small subset of the capabilities and functions of a traditional wireless communication system. In other words, the service-based architecture may enable functions and protocols to be split into self-contained services (e.g., core network services 215) as compared to components that provide all-encompassing network functions and protocols (e.g., modularization of network services / functions across multiple core network services 215).

[0115] In this regard, the wireless communication system 200 may illustrate an example of a merged cloud-native platform configured to host CORE and RAN services, which may simplify protocols and reduce duplication of processing operations between CORE and RAN (e.g., reallocation of CORE and RAN 210 services). In other words, the fusion of RAN 210 and CN functions may reduce duplication of operations and functions at different layers to serve one UE.

[0116] The wireless communication system 200 can extend the benefits associated with the service-based architecture of the service-based network 205 to the RAN 210, including the benefits of increased scalability, resilience, elasticity, flexibility, reuse, visibility, automation, and failover. In addition, the service-based architecture can enable each core network service 215 across the RAN 210 and the CORE to scale independently by independently increasing or decreasing the resources allocated across the corresponding core network service 215.

[0117] In some implementations, as will be described in further detail herein, the wireless communication system 200 may support signaling, configuration, and other mechanisms for distributing system information (e.g., SIBs) in a service-based wireless system. In particular, the wireless communication system 200 may support signaling that enables a network entity 105-b (e.g., a DU) to compile SIB configurations for a plurality of different core network services 215 of a service-based network 205, and to distribute SIBs for corresponding core network services 215 based on the acquired SIB configurations.

[0118] Figure 3An example of a network architecture 300 (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) supporting techniques for system information broadcast in a service-based wireless system according to one or more aspects of the present disclosure is shown. The network architecture 300 may illustrate an example for implementing one or more aspects of the wireless communication system 100. The network architecture 300 may include a service-based network 305, which may be an example of a service-based network 130 or 205 that communicates with the DU 165-a via a link 120-b. In this example, the DU 165 may also communicate with one or more CUs 310, which may communicate directly with the 5G core 190-a via the backhaul communication link 120-a, or indirectly with the 5G core 190-a through one or more disaggregated network entities 105 (e.g., a near RT RIC 330-a via an E2 link, or a non-RT RIC 330-b associated with a SMO 335 (e.g., an SMO framework), or both). The CU 310 may communicate with one or more DUs 165-a via corresponding mid-range communication links 315 (e.g., F1 interfaces). The DU 165-a may communicate with one or more RUs 170-a via corresponding front-haul communication links 168-a. The RU 170-a may be associated with a corresponding coverage area 110-a and may communicate with a UE 115-b via one or more communication links 125-a. In some implementations, a UE 115-b may be served simultaneously by multiple RUs 170-a.

[0119] Each network entity 105 (e.g., CU 310, DU 165-a, RU 170-a, non-RT RIC 330-a, near-RT RIC 330-b, SMO 335, open cloud (O-cloud) 320, open eNB (O-eNB) 325) of the network architecture 300 may include one or more interfaces, or may be coupled to one or more interfaces configured to receive or send signals (e.g., data, information) via a wired or wireless transmission medium. Each network entity 105 or an associated processor (e.g., a controller) that provides instructions to an interface of the network entity 105 may be configured to communicate with one or more of the other network entities 105 via a transmission medium. For example, the network entity 105 may include a wired interface that is configured to receive or send signals to one or more of the other network entities 105 via a wired transmission medium. Additionally or alternatively, the network entity 105 may include a wireless interface, which may include a receiver, a transmitter, or a transceiver (e.g., an RF transceiver) configured to receive or send signals, or both, to one or more other network entities 105 via a wireless transmission medium.

[0120] In some examples, CU 310 may host one or more higher layer control functions. Such control functions may include RRC, PDCP, SDAP, etc. Each control function may be implemented using an interface configured to transmit signals to other control functions hosted by CU 310. CU 310 may be configured to process user plane functions (e.g., CU-UP), control plane functions (e.g., CU-CP), or a combination thereof. In some examples, CU 310 may be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface such as an E1 interface. CU 310 may be implemented to communicate with DU 165-a as needed for network control and signaling.

[0121] DU 165-a may correspond to a logical unit including one or more functions (e.g., base station functions, RAN functions) to control the operation of one or more RUs 170-a. In some examples, when docking with a service-based network 305, DU165-a may host one or more APIs for one or more services of the service-based network 305 and one or more corresponding services at one or more UEs 115-b. In some examples, when docking with CU 310, DU 165-a may at least partially host one or more aspects of the RLC layer, MAC layer, and PHY layer (e.g., a high PHY layer, such as a module for FEC encoding and decoding, scrambling, modulation, and demodulation, etc.), which depends at least in part on the functional split, such as the functional split defined by the Third Generation Partnership Project (3GPP). In some examples, DU 165-a may also host one or more low PHY layers. Each layer may be implemented using an interface configured to transmit signals to other layers hosted by DU 165-a, or implemented using a control function hosted by CU 310.

[0122] In some examples, lower layer functions may be implemented by one or more RUs 170-a. For example, a RU 170-a controlled by a DU 165-a may correspond to a logical node that hosts RF processing functions or low PHY layer functions (e.g., performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.) or both based at least in part on functional splitting (such as lower layer functional splitting). In such an architecture, RU 170-a may be implemented to handle over-the-air (OTA) communications with one or more UEs 115-b. In some implementations, real-time and non-real-time aspects of control and user plane communications with RU 170-a may be controlled by the corresponding DU 165-a. In some examples, such a configuration may enable DU 165-a and CU 310 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0123] SMO 335 can be configured to support RAN deployment and provisioning of non-virtualized and virtualized network entities 105. For non-virtualized network entities 105, SMO 335 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via an operation and maintenance interface (e.g., O1 interface). For virtualized network entities 105, SMO 335 can be configured to interact with a cloud computing platform (e.g., O-cloud 320) via a cloud computing platform interface (e.g., O2 interface) to perform network entity lifecycle management (e.g., instantiate virtualized network entities 105). Such virtualized network entities 105 may include, but are not limited to, CU 310, DU 165-a, RU 170-a, and near-RT RIC 330-a. In some implementations, SMO 335 can communicate with components configured according to 4G RAN (e.g., via O1 interface). Additionally or alternatively, in some implementations, SMO 335 can communicate directly with one or more RU 170-a via O1 interface. The SMO 335 may also include a non-RT RIC 330 - b configured to support the functionality of the SMO 335 .

[0124] The non-RT RIC 330-b can be configured to include logic functions that implement non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) or machine learning (ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 330-a. The non-RT RIC 330-b can be coupled to or communicate with the near-RT RIC 330-a (e.g., via an A1 interface). The near-RT RIC 330-a can be configured to include logic functions that implement near real-time control and optimization of RAN elements and resources via data collection and actions through an interface (e.g., via an E2 interface) that connects one or more CUs 310, one or more DUs 165-a, or both, and the O-eNB 325 with the near-RT RIC 330-a.

[0125] In some examples, in order to generate an AI / ML model to be deployed in the near-RT RIC 330-b, the non-RT RIC 330-b may receive parameters or external enrichment information from an external server. Such information may be used by the near-RT RIC 330-a and may be received from a non-network data source or from a network function at the SMO 335 or the non-RT RIC 330-b. In some examples, the non-RT RIC 330-b or the near-RT RIC 330-a may be configured to adjust RAN behavior or performance. For example, the non-RT RIC 330-b may monitor long-term trends and patterns of performance and use AI or ML models to perform corrective actions through the SMO (e.g., via reconfiguration of O1) or via the generation of RAN management policies (e.g., A1 policies).

[0126] In some implementations, as will be described in further detail herein, the network architecture 300 may support signaling, configuration, and other mechanisms for distributing system information (e.g., SIBs) in a service-based wireless system. In particular, the network architecture 300 may support signaling that enables the network entity 105 (e.g., DU 165) to compile SIB configurations for multiple different core network services of a service-based network and distribute SIBs for corresponding core network services based on the acquired SIB configurations.

[0127] Figure 4An example of a wireless communication system 400 that supports techniques for system information broadcast in a service-based wireless system in accordance with one or more aspects of the present disclosure is shown. In some examples, aspects of the wireless communication system 400 can implement or be implemented by aspects of the wireless communication system 100, the wireless communication system 200, the network architecture 300, or any combination thereof. In particular, the wireless communication system 400 can support signaling, configuration, and other mechanisms that enable the network entity 105-a to broadcast SIB messages for one or more core network services 405, such as information about the service provider, the service provider, and the service provider. Figure 1 Described.

[0128] The wireless communication system 400 may include a UE 115-b, a network entity 105-b, a first core network service 405-a, and a second core network service 405-b. In some implementations, the network entity 105-b may include an example of an O-RAN entity, which includes multiple components, such as one or more DUs, as shown in FIG. Figure 3 In this regard, Figure 4 The network entity 105 - b shown in FIG. 1 may additionally or alternatively be referred to as a DU (eg, eDU).

[0129] The first core network service 405-a and the second core network service 405-b may be coupled to a service-based network such as Figure 2 405-b). In some aspects, the service-based network including core network services 405-a, 405-b can be configured to communicate or interface with a RAN of the wireless communication system 400, wherein the RAN includes one or more network entities (e.g., network entity 105-b). In some implementations, the core network services 405-a, 405-b can be associated with a cloud platform or hosted by a cloud platform, wherein the corresponding core network service 405 is hosted at a corresponding network address in the cloud platform.

[0130] The UE 115-b may communicate with the network entity 105-b using a communication link 410, which may be an example of an NR, LTE, or 6G link between the UE 115-b and the network entity 105-b. In some cases, the communication link 410 may include an example of an access link (e.g., a Uu link), which may include a bidirectional link that implements both uplink and downlink communications. Similarly, the network entity 105-b of the RAN may be configured to communicate with (e.g., interface with) a core network service 405 of a service-based network via communication links 415-a, 415-b, where the communication link 415 may be configured to facilitate bidirectional communication between the network entity 105-b and each of the corresponding core network services 405. In some aspects, each core network service 405-a, 405-b may include a corresponding API configured to facilitate wireless communication with the network entity 105-b and the UE 115-b, such as Figure 1 The web service API 180 shown in .

[0131] In some aspects, the network entity 105-b (e.g., eDU) may facilitate traffic routing (e.g., service data unit routing) from the UE 115-b to the core network services 405, or vice versa. In other words, the network entity 105-b may be configured to relay communications (e.g., service messages) from the UE 115-b to the core network services 405, or vice versa. The network entity 105-b may facilitate traffic routing between the respective devices directly, via other network entities 105-b, via a proxy, or any combination thereof.

[0132] As mentioned previously herein, in the context of a service-based wireless system such as the wireless communication system 400 or another service-based 6G network, it may be desirable for different core network services 405 to share information (e.g., system information, such as SIB messages / containers) with UEs 115 and other wireless devices in the network so that the corresponding devices can communicate with the core network services 405. In some legacy systems (e.g., 5G networks), there may be an assumption that one operator is configuring all parameters for system information that will be compiled at a centralized point (e.g., network entity 105, eNB, gNB) and distributed throughout the network (even in a network sharing scenario). In this case, the network entity 105 may receive the system information from the operator / core network, decode the system information, and encapsulate the system information into SIBs that are broadcast to the UE 115.

[0133] However, requiring the network entity 105 to decode and encapsulate SIBs for a large number of core network services 405 may result in increased complexity and processing power at the network entity 105. Furthermore, compared to some conventional systems that exhibit a centralized backend network that compiles and encapsulates system information to be distributed throughout the network, a service-based system may include many different core network services 405 associated with different operators, protocols, and communication parameters (e.g., without one central operator). As a result, each respective core network service 405 may have its own system information to broadcast, which further complicates the communication of system information within a service-based architecture.

[0134] Thus, aspects of the present disclosure relate to signaling, configuration, and other mechanisms for distributing system information (e.g., SIBs) in a service-based wireless system. In particular, aspects of the present disclosure relate to signaling that enables a network entity 105-b (e.g., a DU of the network entity 105-b) to compile SIB configurations for a plurality of different core network services 405, and to distribute SIBs for the corresponding core network services 405 according to the acquired SIB configurations. In other words, aspects of the present disclosure relate to techniques that enable a RAN (e.g., a network entity 105-b) to distribute system information for a core network service 405.

[0135] Additionally or alternatively, aspects of the present disclosure may enable the network entity 105-b to distribute SIB containers / messages associated with communications with a corresponding core network service 405 (e.g., core network service-specific SIBs), as well as SIB containers / messages associated with communications with the network entity 105-b (e.g., RAN-specific or network entity-specific SIBs). In this regard, some aspects of the present disclosure may enable the network entity 105-b to distribute system information as a service to the corresponding core network service 405, thereby enabling the network entity 105-b to meet QoS requirements for the corresponding core network service 405 (compared to some traditional systems in which the SIBs are simply provided to the network entity 105 for transmission at a given schedule).

[0136] For example, Figure 4As shown, the network entity 105-b can send a SIB container 430-a to the UE 115-b, and the SIB container 430-a includes information associated with the communication with the network entity 105-b. In other words, the SIB container can indicate parameters or other characteristics (e.g., RAN communication parameters) that the UE 115-b can use to perform communications with the network entity 105-b. In other words, the RAN (e.g., the network entity 105-b) can announce system information via the SIB container 430-a, where the system information includes SIB scheduling, RAN-specific system information (e.g., RACH configuration), announced service availability and SIB, service discovery information (e.g., service discovery for unannounced core network services 405), etc.

[0137] In some aspects, the network entity 105-b may send first signaling indicating API information 420 associated with the network entity 105-b to the first core network service 405-a, the second core network service 405-b, the additional core network service, or any combination thereof. In some aspects, the core network service 405 may use the API information 420 to format and generate signaling and other information (e.g., SIB configuration 425) in such a way that the signaling or other information is successfully received at the network entity 105-b via the API. In other words, the network entity 105-b (e.g., DU, eDU) may expose an API associated with the network entity 105-b to allow the core network service 405 to configure system information for notification.

[0138] In some cases, the network entity 105 - b may send the API information 420 to another core network service 405 that is configured to store information associated with the network entity 105 within the network, such as applicable coverage areas of the network entity 105 , capability information of the network entity 105 , etc. In such a case, the core network services 505 - a , 505 - b may be configured to retrieve the API information 420 from the additional core network service 405 , for example, by querying the additional core network service 405 .

[0139] In some implementations, the network entity 105-b may receive signaling indicating a first SIB configuration 425-a associated with a first core network service 405-a. Similarly, the network entity 105-b may receive signaling indicating a second SIB configuration 425-b associated with a second core network service 405-b. In some aspects, the first SIB configuration 425-a and the second SIB configuration 425-b may include information associated with communications with the corresponding core network service 405-a to be relayed / broadcasted to the UE 115-b (e.g., parameters for communicating with the corresponding core network service 405).

[0140] For example, the first SIB configuration 425-a may indicate first information to be relayed to the UE 115-b via the first SIB container 430-b, together with instructions for the network entity 105-b to relay the first SIB container 430-b to the UE 115-b. Similarly, the second SIB configuration 425-b may indicate second information to be relayed to the UE 115-b via the second SIB container 430-c, together with instructions for the network entity 105-b to relay the second SIB container 430-c to the UE 115-b. In some aspects, the core network service 405 may send signaling indicating the corresponding SIB configuration 425 based on the API information 420 associated with the network entity 105-b. In other words, the authorized core network service 405 may format and send signaling indicating the corresponding SIB configuration 425 so that the signaling can be received by the API at the network entity 105-b.

[0141] In some aspects, the SIB configuration 425 may indicate additional parameters or characteristics associated with the SIB container 430 to be relayed on behalf of the corresponding core network service 405. In other words, each core network service 405 may specify broadcast requirements or parameters associated with the corresponding SIB container 430. The parameters associated with the corresponding SIB configuration 425 may include, but are not limited to, scheduling information of the corresponding SIB container 430 (e.g., a period for sending / broadcasting the SIB container 430), a size of the corresponding SIB container 430, a QoS metric for the corresponding SIB container 430, a delivery delay for the corresponding SIB container 430 (e.g., a delay in delivery), a coverage area for the corresponding SIB container 430 (e.g., a coverage requirement), a reliability metric for the corresponding SIB container 430 (e.g., a reliability requirement), or any combination thereof. As another example, in some cases, the SIB configuration 425 may indicate the format of the corresponding SIB container 430, such as a type-length-value (TLV) associated with the SIB container 430, an Internet Assigned Numbers Authority (IANA) service number associated with the SIB container 430, and the like.

[0142] In addition, the SIB configuration 425 may indicate whether the SIB container 430 associated with the corresponding SIB configuration 425 is to be sent by the network entity 105-b continuously or periodically, or whether the corresponding SIB container 430 is to be transmitted on demand (e.g., in response to a request from the UE 115-b). That is, the network entity 105-b may be configured to provide SIBs on demand for each core network service 405 or each group of core network services 405 (e.g., aggregated to save round trips).

[0143] In some implementations, a single core network service 405 may include multiple SIBs (e.g., multiple SIB containers 430) to be transmitted to a UE 115-b. For example, a first SIB configuration 425-a may include multiple sets of information to be transmitted to a UE 115-b via multiple SIB containers 430. In such a case, the first SIB configuration 425-a may include multiple SIB containers 430 to be relayed to the UE 115-b, along with instructions for the network entity 105-b to relay the SIB containers 430.

[0144] In some implementations, the core network service 405 may "subscribe" to one or more network entities 105 for relaying SIB containers 430 to UEs 115 within the wireless communication system 400. The core network service 405 may subscribe to a network entity 105 for relaying system information based on network topology or other operator configuration (e.g., request frequency, delivery delay, coverage, etc.). As previously described herein, the core network service 405 may obtain information associated with a network entity 105 that may be used to relay system information from the respective network entity 105 itself, from another core network service 405 that stores information associated with the network / network entity 105, or both.

[0145] In some aspects, the network entity 105-b may send scheduling information associated with the corresponding SIB container 430 to the UE 115-b so that the UE 115-b may monitor the corresponding SIB container 430. In other words, the network entity 105-b (e.g., a DU / eDU of the network entity 105-b) may be configured to send / broadcast SIB schedules for different core network services 405, including access stratum (AS) and RAN SIBs added by the network entity 105-b. In addition, the network entity 105-b may be configured to broadcast service availability (e.g., broadcast available / provided core network services 405) (if requested to be announced).

[0146] For example, the network entity 105-b may send first scheduling information (e.g., a first period) associated with the first SIB container 430-b and second scheduling information (e.g., a second period) associated with the second SIB container 430-c. In some aspects, the network entity 105-b may indicate other parameters or characteristics associated with the SIB container 430, such as size, delivery delay, coverage area, etc. In this regard, the network entity 105-b may send the scheduling information based on sending the API information 420, receiving the first SIB configuration 425-a, receiving the second SIB configuration 425-b, or any combination thereof. The scheduling information may be transmitted via RRC signaling, DCI signaling, MAC-CE signaling, system information signaling, or any combination thereof.

[0147] In some implementations, the network entity 105-b may send or broadcast scheduling information for all core network services 505 provided or supported by the network entity 105-b and / or the service-based network so that the corresponding UEs 115 can monitor the SIBs associated with the core network services 505 to which they are subscribing. In some aspects, the network entity 105-b may indicate which (if any) SIB containers 430 will be transmitted on demand in response to a request from the UE 115-b. For example, the network entity 105-b may indicate that a first SIB container 430-b will be broadcast according to a regular period, but a second SIB container 430-c will be transmitted on demand (e.g., in response to a request from the UE 115-b).

[0148] In some aspects, the network entity 105-b may receive a request for the first SIB container 430-b, the second SIB container 430-c, or both from the UE 115-b. In particular, the UE 115-b may send the request based on receiving an indication that one of the first or second SIB containers 430 will be transmitted on demand in response to the request from the UE 115-b. Thus, the UE 115-b may send the request based on receiving signaling indicating scheduling information and / or other parameters of the SIB container 430.

[0149] The network entity 105-b may send (e.g., broadcast) a first SIB container 430-b (e.g., SIB message) associated with the first core network service 405-a to the UE 115-b. Similarly, the network entity 105-b may send (e.g., broadcast) a second SIB container 430-c (e.g., SIB message) associated with the second core network service 405-b to the UE 115-b. In some implementations, the SIB container may be sent via the MAC layer, the physical layer. For example, the network entity 105 may perform concatenation on the SIB container and send the bits of the SIB container via both the MAC layer and the physical layer.

[0150] As previously mentioned herein, the respective SIB containers 430 may include information that may be used for communication with the respective core network service 405-a. For example, the first SIB container 430-b may include information associated with communication with the first core network service 405-a, and the second SIB container 430-c may include information associated with communication with the second core network service 405-b.

[0151] The network entity 105-b may send the SIB containers 430-b, 430-c based on receiving the SIB configurations 425-a, 425-b, sending scheduling information, receiving a request from the UE 115-b, or any combination thereof. For example, the network entity 105-b may send the first SIB container 430-b based on the scheduling information transmitted via the first SIB configuration 425-a and / or the scheduling information transmitted to the UE 115-b. As another example, the network entity 105-b may send the second SIB container 430-c in response to receiving a request for the second SIB container 430-c.

[0152] In some implementations, the network entity 105-b may send or relay SIB containers 430-b, 430-c associated with the corresponding core network service 405 without decoding the corresponding SIB container 430. That is, since the network entity 105-b cannot understand, decode and / or construct the corresponding SIB container 430-b, 430-c, the first SIB container 430-b and / or the second SIB container 430-c may be transparent to the network entity 105-b. For example, the first SIB configuration 425-a may include the first SIB container 430-b, and the network entity 105-b may be configured to relay the first SIB container 430-b to the UE 115-b without decoding the first SIB container 430-b. In this regard, at least a portion of the first SIB configuration 425-a may be transparent to the network entity 105-b.

[0153] Furthermore, as previously mentioned herein, in some implementations, the network entity 105-b may be configured to send, broadcast, or relay multiple SIB containers 430 for a single core network service 405. For example, a first SIB configuration 425-a may include first information to be relayed via a first SIB container 430-b, and additional information to be relayed via additional SIB containers 430. In some implementations, transparent SIB containers from the same core network service 405 may be aggregated if the network entity 105-b is to send the corresponding SIB containers 430 simultaneously.

[0154] Subsequently, the network entity 105-b can relay service messages between the UE 115-b, the first core network service 405-a, and the second core network service 405-b based on the relayed system information (e.g., based on the SIB container 430). In other words, the UE 115-b can communicate (e.g., send and receive service messages) with the corresponding core network service 405 via the relay provided by the network entity 105-b and based on the information transmitted via the corresponding SIB container 430.

[0155] For example, UE 115-b may communicate service messages with a first core network service 405-a (via network entity 105-b) based on information included within a first SIB container 430-b. Similarly, as another example, UE 115-b may communicate service messages with a second core network service 405-b (via network entity 105-b) based on information included within a second SIB container 430-c. In addition, UE 115-b and network entity 105-b may communicate with each other (e.g., send, receive, and relay service messages) based on a RAN-specific SIB container 430-a associated with communications with network entity 105-b.

[0156] The techniques described herein may enable the network entity 105-b to broadcast system information to the UE 115 on behalf of the core network service 405 of the service-based network. In addition, the techniques described herein may enable the network entity 105-b to receive the SIB container 430 from the core network service 405 and relay the SIB container to the UE 115-b without decoding the corresponding SIB container 430 (e.g., a transparent SIB container 430). In this regard, various aspects of the present disclosure may enable the network entity 105-b to efficiently aggregate system information from multiple core network services 405 and relay the system information to other wireless devices, thereby enabling efficient transmission of system information and facilitating more efficient and reliable wireless communications. In addition, by enabling the network entity 105-b to relay the SIB container 430 without decoding the SIB container 430, the techniques described herein may reduce processing requirements at the network entity 105, thereby reducing network complexity and power consumption.

[0157] Figure 5 An example of a process flow 500 is shown for supporting techniques for system information broadcast in a service-based wireless system in accordance with one or more aspects of the present disclosure. In some examples, aspects of the process flow 500 may implement aspects of, or be implemented by aspects of, the wireless communication system 100, the wireless communication system 200, the network architecture 300, the wireless communication system 400, or any combination thereof. In particular, the process flow 500 illustrates signaling between a network entity 105-c (e.g., an eDU) and a plurality of core network services 505-a, 505-b that enables the network entity 105-c to aggregate SIB configurations for respective core network services 505 and relay the SIB containers to the UE 115-c based on the SIB configurations, as described with reference to FIG. Figure 1-4 described, and other aspects.

[0158] The process flow 500 may include a UE 115-c, a network entity 105-c (eg, an eDU), a first core network service 505-a, and a second core network service 505-b, which may be referenced. Figure 1-4 Examples of UE 115, network entity 105, core network services, and other wireless devices are described. For example, Figure 5 The UE 115-c and the network entity 105-c shown in FIG. 1 may be as follows: Figure 4 105 - c and a network entity 105 - c. In this regard, the network entity 105 - c may include a DU (e.g., an eDU) or be associated with a DU. Similarly, Figure 5 The first core network service 505-a and the second core network service 505-b shown in FIG. 5 can be as follows: Figure 4 An example of a first core network service 405 - a and a second core network service 405 - b is shown.

[0159] In some aspects, the first core network service 505-a and the second core network service 505-b may be included in a service-based network such as Figure 2 In such a case, the service-based network including the core network services 505 can be configured to interface with (e.g., communicate with) a RAN including a network entity 105-c (e.g., an eDU) to facilitate communication between the service-based network and the UE 115-c. In this regard, Figure 5 The signaling shown in may include example signaling within a network with a service-based architecture, such as a 6G system.

[0160] In some examples, the operations shown in process flow 500 can be performed by hardware (e.g., including circuits, processing blocks, logic components, and other components), code executed by a processor (e.g., software), or any combination thereof. The following alternative examples can be implemented in which some of the steps are performed in a different order than described or not performed at all. In some cases, the steps may include additional features not mentioned below, or additional steps may be added.

[0161] At 510, the network entity 105-c may send first signaling indicating API information associated with the network entity 105-c to the first core network service 505-a, the second core network service 505-b, the additional core network service, or any combination thereof. In some aspects, the core network service 505 may use the API information to format and generate signaling and other information (e.g., SIB configuration) in such a way that the signaling or other information can be successfully received at the network entity 105-c via the API.

[0162] In some cases, the network entity 105-c may send the API information to another core network service 505 that is configured to store information associated with the network entity 105 within the network, such as applicable coverage areas of the network entity 105, capability information of the network entity 105, etc. In such cases, the core network services 505-a, 505-b may be configured to retrieve the API information from the additional core network service 505 (e.g., by querying the additional core network service 505). In additional or alternative implementations, the additional core network service 505, such as a discovery service, may obtain the API associated with the corresponding network entity 105 and provide the API to the corresponding core network service 505.

[0163] At 515, the network entity 105-c may receive signaling from the first core network service 505-a indicating a first SIB configuration associated with the first core network service 505-a. In some aspects, the first SIB configuration may include first information associated with communication with the first core network service 505-a (e.g., parameters for communicating with the first core network service 505-a). In other words, the first SIB configuration may indicate first information to be relayed to the UE 115-c via the first SIB container, and instructions for the network entity 105-c to relay the first SIB container to the UE 115-c. In some aspects, the first core network service 505-a may send the first SIB configuration based on the API information associated with the network entity 105-c obtained at 510. In other words, the first core network service 505-a may format and send signaling indicating the first SIB configuration so that the signaling can be received by the API at the network entity 105-c.

[0164] In some aspects, the signaling indicating the first SIB configuration may indicate additional parameters or characteristics associated with the SIB to be relayed for the first core network service 505-a. Parameters associated with the first SIB configuration of the first core network service 505-a may include, but are not limited to, scheduling information for the first SIB container (e.g., a period for sending / broadcasting the first SIB container), the size of the first SIB container, a QoS metric for the first SIB container, a delivery delay for the first SIB container, a coverage area for the first SIB container, or any combination thereof. In addition, the first SIB configuration may indicate whether the first SIB container will be sent continuously or periodically by the network entity 105-c, or whether the first SIB container will be transmitted on demand (e.g., in response to a request from the UE 115).

[0165] In some implementations, the core network service 505-a may include multiple SIBs (e.g., SIB containers) to be transmitted to the UE 115-c. In such a case, the SIB configuration may include multiple SIB containers to be relayed to the UE 115-c, together with instructions for relaying the SIB containers. For example, the SIB configuration may include: a first SIB container that includes first information associated with communication with the first core network service 505-a; and an additional SIB container that includes additional information associated with communication with the first core network service 505-a. In such a case, the SIB configuration may indicate parameters for each SIB container in the corresponding SIB container (e.g., scheduling information, the size of the SIB container, whether the SIB container is on-demand, etc.).

[0166] At 520, the network entity 105-c may receive signaling from the second core network service 505-b indicating a second SIB configuration associated with the second core network service 505-b. The second SIB configuration may include second information associated with communications with the second core network service 505-b (e.g., parameters for communicating with the second core network service 505-b). In other words, as previously described herein, the second SIB configuration may indicate second information to be relayed to the UE 115-c via the second SIB container, together with instructions for the network entity 105-c to relay the second SIB container to the UE 115-c.

[0167] In some aspects, the second core network service 505-b may send a second SIB configuration based on the API information associated with the network entity 105-c obtained at 510. In addition, as previously described herein at 515 with respect to the first SIB configuration, the second SIB configuration may indicate additional parameters or characteristics associated with the second SIB container (e.g., scheduling information for the second SIB container, the size of the second SIB container, a QoS metric for the second SIB container, a delivery delay for the second SIB container, a coverage area for the second SIB container, whether to transmit the second SIB container on demand in response to a request, etc.). In addition, in some aspects, the second SIB configuration may indicate or include multiple SIB containers containing different information for communicating with the second core network service 505-b, wherein each respective SIB container may be associated with a respective set of communication parameters.

[0168] At 525, the network entity 105-c may send scheduling information associated with the corresponding SIB container to the UE 115-c so that the UE 115-c may monitor the corresponding SIB container. For example, the network entity 105-c may send first scheduling information associated with the first SIB container (e.g., the first period) and second scheduling information associated with the second SIB container (e.g., the second period). In some aspects, the network entity 105-c may indicate other parameters or characteristics associated with the SIB container, such as size, delivery delay, coverage area, etc. In this regard, the network entity 105-c may send the scheduling information based on sending API information at 510, receiving signaling indicating the first SIB configuration at 515, receiving signaling indicating the second SIB configuration at 520, or any combination thereof. The scheduling information may be transmitted via RRC signaling, DCI signaling, MAC-CE signaling, system information signaling, or any combination thereof.

[0169] In some implementations, the network entity 105-c may send or broadcast scheduling information for all core network services 505 provided or supported by the network entity 105-c and / or the service-based network so that the corresponding UEs 115 can monitor the SIBs associated with the core network services 505 to which they are subscribing. In some aspects, the network entity 105-c may indicate which (if any) SIB containers will be transmitted on demand in response to a request from the UE 115-c. For example, the network entity 105-c may indicate that a first SIB container will be broadcast according to a regular period, but a second SIB container will be transmitted on demand (e.g., in response to a request from the UE 115-c).

[0170] At 530, the network entity 105-c may receive a request for the first SIB container, the second SIB container, or both from the UE 115-c. In particular, the UE 115-c may send the request at 530 based on receiving an indication that one of the first or second SIB containers will be transmitted on demand in response to the request from the UE 115-c. Thus, the UE 115-c may send the request at 530 based on receiving signaling indicating scheduling information and / or other parameters of the SIB container at 525.

[0171] At 535, the network entity 105-c may send (e.g., broadcast) a first SIB container (e.g., a SIB message) associated with the first core network service 505-a to the UE 115-c. As previously described herein, the first SIB container may include first information that may be used to communicate with the first core network service 505-a. The network entity 105-c may send the first SIB container at 535 based on receiving the first SIB configuration at 515, sending the scheduling information at 525, receiving the request at 530, or any combination thereof. For example, the network entity 105-c may send the first SIB container based on the scheduling information transmitted via the first SIB configuration at 515 and / or the scheduling information transmitted to the UE 115-c at 525. As another example, the network entity 105-c may send the first SIB container at 535 in response to receiving the request for the first SIB container at 530.

[0172] In some implementations, the network entity 105-c may send or relay the first SIB container to the UE 115-c without decoding the first SIB container. That is, the first SIB container may be transparent to the network entity 105-c because the network entity 105-c cannot understand or decode the SIB container. For example, the first SIB configuration at 515 may include the first SIB container, and the network entity 105-c may be configured to relay the first SIB container to the UE 115-c without decoding the first SIB container. In this regard, at least a portion of the first SIB configuration may be transparent to the network entity 105-c.

[0173] At 540, the network entity 105-c may send (e.g., broadcast) a second SIB container (e.g., a SIB message) associated with the second core network service 505-b to the UE 115-c. As previously mentioned herein, the first SIB container may include first information that may be used to communicate with the first core network service 505-a. The network entity 105-c may send the second SIB container at 540 based on receiving the second SIB configuration at 520, sending the scheduling information at 525, receiving the request at 530, or any combination thereof. For example, the network entity 105-c may send the second SIB container based on the scheduling information transmitted via the second SIB configuration at 520 and / or the scheduling information transmitted to the UE 115-c at 525. As another example, the network entity 105-c may send the second SIB container at 540 in response to receiving a request for the second SIB container at 530.

[0174] As previously described herein with respect to the first SIB container, in some implementations, the network entity 105-c may send or relay the second SIB container to the UE 115-c without decoding the second SIB container. That is, the first SIB container may be transparent to the network entity 105-c because the network entity 105-c cannot understand or decode the SIB container.

[0175] At 545, the network entity 105-c may send (e.g., broadcast) a third SIB container (e.g., a SIB message) associated with the first core network service 505-a to the UE 115-c. In this regard, the first core network service 505-a may be associated with both the first SIB container and the third SIB container. In this example, the corresponding SIB containers may include different information associated with communications with the first core network service 505-a. In addition, both the first and third SIB containers (as well as parameters for transmitting the SIB containers) may be included or indicated within the first SIB configuration. In addition, as previously mentioned herein with respect to the first and second SIB containers, in some implementations, the network entity 105-c may send or relay the third SIB container to the UE 115-c without decoding the third SIB container.

[0176] At 550, the network entity 105-c may send a fourth SIB container (e.g., a fourth SIB.message) to the UE 115-c, the fourth SIB container including information associated with communications with the network entity 105-c. In other words, the fourth SIB container may include information (e.g., RAN communication parameters) that may be used to communicate with the network entity 105-c, as compared to the first and second SIB containers associated with communications with the first and second core network services 505, respectively. In this regard, the network entity 105-c may be configured to send or broadcast both the core network service 505-specific SIB container and the network entity 105-c-specific SIB container.

[0177] Although a fourth SIB container associated with communications with the network entity 105-c is shown at 550, this should not be considered a limitation of the present disclosure unless otherwise noted herein. For example, in some implementations, the network entity 105-c may send the fourth SIB container during a connection establishment process between the UE 115-c and the network entity 105-c. In this case, Figure 5 The communication between the UE 115 - c and the network entity 105 - c shown in FIG. 1 may be based on information included in a fourth SIB container.

[0178] At 555, the network entity 105-c may relay service messages between the UE 115-c, the first core network service 505-a, and the second core network service 505-b. In other words, the UE 115-c may communicate (e.g., send and receive service messages) with the corresponding core network service 505 via the relay provided by the network entity 105-c. In particular, the network entity 105-c may relay service messages between the UE 115-c and the corresponding core network service 505 based on information transmitted via the corresponding SIB container. In addition, the UE 115-c and the network entity 105-c may communicate with each other (e.g., send, receive, and relay service messages) based on a fourth SIB container associated with the communication with the network entity 105-c.

[0179] For example, UE 115-c may transmit service messages with a first core network service 505-a (via network entity 105-c) based on information included in a first SIB container and / or a third SIB container. Similarly, as another example, UE 115-c may transmit service messages with a second core network service 505-b (via network entity 105-c) based on information included in a second SIB container.

[0180] Figure 6 A block diagram 600 of a device 605 supporting techniques for broadcasting system information in a service-based wireless system according to one or more aspects of the present disclosure is shown. The device 605 may be an example of aspects of a network entity 105 (e.g., DU) as described herein. The device 605 may include a receiver 610, a transmitter 615, and a communication manager 620. The device 605 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0181] Receiver 610 may provide means for obtaining (e.g., receiving, determining, identifying) information such as user data associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be passed to other components of device 605. In some examples, receiver 610 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, receiver 610 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical fiber) interfaces, wireless interfaces, or any combination thereof.

[0182] The transmitter 615 may provide a means for outputting (e.g., sending, providing, transmitting, emitting) information generated by other components of the device 605. For example, the transmitter 615 may output information such as user data associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 615 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 615 may support outputting information by sending signals via one or more wired (e.g., electrical, optical fiber) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 615 and the receiver 610 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0183] The communication manager 620, the receiver 610, the transmitter 615, or various combinations thereof, or various components thereof may be examples of means for performing various aspects of the techniques for system information broadcast in a service-based wireless system as described herein. For example, the communication manager 620, the receiver 610, the transmitter 615, or various combinations thereof, or components thereof may support methods for performing one or more of the functions described herein.

[0184] In some examples, the communication manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof can be implemented in hardware (e.g., in a communication management circuit). The hardware can include a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof that is configured as or otherwise supports means for performing the functions described in the present disclosure. In some examples, a processor and a memory coupled to the processor can be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0185] Additionally or alternatively, in some examples, the communication manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof may be performed by a general purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting means for performing the functionality described in the present disclosure).

[0186] In some examples, the communication manager 620 can be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with the receiver 610, the transmitter 615, or both. For example, the communication manager 620 can receive information from the receiver 610, send information to the transmitter 615, or integrate with the receiver 1010, the transmitter 1015, or both in combination to obtain information, output information, or perform various other operations as described herein.

[0187] For example, the communication manager 620 may be configured to or otherwise support a unit for receiving, from a first core network service provided by a service-based network, a first signaling indicating a first SIB configuration associated with the first core network service, the first SIB configuration including first information associated with communications with the first core network service. The communication manager 620 may be configured to or otherwise support a unit for receiving, from a second core network service provided by a service-based network, a second signaling indicating a second SIB configuration associated with the second core network service, the second SIB configuration including second information associated with communications with the second core network service. The communication manager 620 may be configured to or otherwise support a unit for sending, to one or more UEs, a first SIB container including first information. The communication manager 620 may be configured to or otherwise support a unit for sending, to one or more UEs, a second SIB container including second information.

[0188] For example, the communication manager 620 may be configured to or otherwise support a unit for sending a first signaling indicating a SIB configuration associated with a core network service to the DU, the SIB configuration including first information associated with communication with the core network service. The communication manager 620 may be configured to or otherwise support a unit for sending an instruction to the DU for the DU to transmit the first information to one or more UEs via the first SIB container based on the SIB configuration. The communication manager 620 may be configured to or otherwise support a unit for transmitting a service message to a UE in one or more UEs based on the instruction.

[0189] By including or configuring the communication manager 620 according to the examples as described herein, the device 605 (e.g., a processor controlling the receiver 610, the transmitter 615, the communication manager 620, or a combination thereof or otherwise coupled thereto) may support techniques that enable the network entity 105 to broadcast system information to the UE 115 on behalf of the core network services of the service-based network 130. In addition, the techniques described herein may enable the network entity 105 to receive SIB containers from the core network services and relay the SIB containers to the UE 115 without decoding the corresponding SIB containers (e.g., transparent SIB containers). In this regard, aspects of the present disclosure may enable the network entity 105 to efficiently aggregate system information from multiple core network services and relay the system information to other wireless devices, thereby enabling efficient communication of system information and facilitating more efficient and reliable wireless communications. In addition, by enabling the network entity 105 to relay the SIB containers without decoding the SIB containers, the techniques described herein may reduce processing requirements at the network entity 105, thereby reducing network complexity and power consumption.

[0190] Figure 7 A block diagram 700 of a device 705 supporting techniques for system information broadcast in a service-based wireless system according to one or more aspects of the present disclosure is shown. The device 705 may be an example of aspects of the device 605 or the network entity 105 as described herein. The device 705 may include a receiver 710, a transmitter 715, and a communication manager 720. The device 705 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0191] Receiver 710 may provide means for obtaining (e.g., receiving, determining, identifying) information such as user data associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be passed to other components of device 705. In some examples, receiver 710 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, receiver 710 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical fiber) interfaces, wireless interfaces, or any combination thereof.

[0192] The transmitter 715 may provide a means for outputting (e.g., sending, providing, transmitting, emitting) information generated by other components of the device 705. For example, the transmitter 715 may output information such as user data associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 715 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 1015 may support outputting information by sending signals via one or more wired (e.g., electrical, optical fiber) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 715 and the receiver 710 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0193] The device 705 or its various components may be examples of units for performing various aspects of the technology for broadcasting system information in a service-based wireless system as described herein. For example, the communication manager 720 may include a SIB configuration manager 725, a SIB transmission manager 730, a service message transmission manager 735, or any combination thereof. The communication manager 720 may be an example of various aspects of the communication manager 620 as described herein. In some examples, the communication manager 720 or its various components may be configured to use the receiver 710, the transmitter 715, or both or otherwise cooperate with the receiver 710, the transmitter 715, or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, the communication manager 720 may receive information from the receiver 710, send information to the transmitter 715, or integrate with the receiver 710, the transmitter 715, or both in combination to obtain information, output information, or perform various other operations as described herein.

[0194] The SIB configuration manager 725 may be configured to or otherwise support means for receiving, from a first core network service provided by a service-based network, first signaling indicating a first SIB configuration associated with the first core network service, the first SIB configuration including first information associated with communications with the first core network service. The SIB configuration manager 725 may be configured to or otherwise support means for receiving, from a second core network service provided by a service-based network, second signaling indicating a second SIB configuration associated with the second core network service, the second SIB configuration including second information associated with communications with the second core network service. The SIB transmission manager 730 may be configured to or otherwise support means for transmitting, to one or more UEs, a first SIB container including first information. The SIB transmission manager 730 may be configured to or otherwise support means for transmitting, to one or more UEs, a second SIB container including second information.

[0195] The SIB configuration manager 725 may be configured as or otherwise support means for sending a first signaling indicating a SIB configuration associated with a core network service to the DU, the SIB configuration including first information associated with communication with the core network service. The SIB configuration manager 725 may be configured as or otherwise support means for sending an instruction to the DU for the DU to transmit first information to one or more UEs via a first SIB container based on the SIB configuration. The service message transmission manager 735 may be configured as or otherwise support means for transmitting a service message to a UE in one or more UEs based on the instruction.

[0196] Figure 8A block diagram 800 of a communication manager 820 supporting techniques for broadcasting system information in a service-based wireless system according to one or more aspects of the present disclosure is shown. The communication manager 820 may be an example of aspects of the communication manager 620, the communication manager 720, or both as described herein. The communication manager 820 or its various components may be examples of units for performing various aspects of the techniques for broadcasting system information in a service-based wireless system as described herein. For example, the communication manager 820 may include a SIB configuration manager 825, a SIB transmission manager 830, a service message transmission manager 835, an API manager 840, a control signaling manager 845, a service message relay manager 850, a request reception manager 855, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses), which may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with the network entity 105, between devices, components, or virtualized components associated with the network entity 105), or any combination thereof.

[0197] The SIB configuration manager 825 may be configured as or otherwise support a unit for receiving a first signaling indicating a first SIB configuration associated with the first core network service from a first core network service provided by a service-based network, the first SIB configuration including first information associated with communication with the first core network service. In some examples, the SIB configuration manager 825 may be configured as or otherwise support a unit for receiving a second signaling indicating a second SIB configuration associated with the second core network service from a second core network service provided by a service-based network, the second SIB configuration including second information associated with communication with the second core network service. The SIB transmission manager 830 may be configured as or otherwise support a unit for transmitting a first SIB container including first information to one or more UEs. In some examples, the SIB transmission manager 830 may be configured as or otherwise support a unit for transmitting a second SIB container including second information to one or more UEs.

[0198] In some examples, the SIB configuration manager 825 can be configured as or otherwise support a unit for receiving a first set of parameters associated with a first SIB configuration via first signaling, wherein the first set of parameters includes scheduling information for a first SIB container, a size of the first SIB container, a quality of service metric for the first SIB container, a delivery delay for the first SIB container, a coverage area for the first SIB container, or any combination thereof, wherein the first SIB container is sent according to the first set of parameters.

[0199] In some examples, the SIB configuration manager 825 may be configured or otherwise support a unit for receiving an indication via first signaling that a SIB container associated with a first SIB configuration will be provided on demand in response to a request from one or more UEs, wherein sending the first SIB container is based on the indication.

[0200] In some examples, the control signaling manager 845 may be configured or otherwise support a unit for sending an indication to one or more UEs that a SIB container associated with a first SIB configuration will be provided on demand in response to a request from the one or more UEs. In some examples, the request reception manager 855 may be configured or otherwise support a unit for receiving a request for a first SIB container from a UE in the one or more UEs based on sending the indication, wherein the first SIB container is sent to the UE in response to the request.

[0201] In some examples, the SIB transmission manager 830 may be configured or otherwise support means for transmitting a third SIB container to one or more UEs, the third SIB container including third information associated with communication between the DU and the one or more UEs.

[0202] In some examples, the API manager 840 can be configured as or otherwise support a unit for sending third signaling indicating API information associated with the DU to a first core network service, a second core network service, an additional core network service, or any combination thereof, wherein the first signaling, the second signaling, or both are received based on the API information.

[0203] In some examples, the control signaling manager 845 can be configured to or otherwise support a unit for sending third signaling to one or more user equipment indicating first scheduling information associated with a first SIB container and second scheduling information associated with a second SIB container, wherein the first SIB container and the second SIB container are sent based on the first scheduling information and the second scheduling information, respectively.

[0204] In some examples, the SIB transmission manager 830 may be configured to or otherwise support a unit for transmitting a third SIB container including third information to one or more UEs. In some examples, the SIB transmission manager 830 may be configured to or otherwise support a unit for receiving a first SIB container via a first signaling, wherein transmitting the first SIB container includes: relaying the first SIB container without decoding the first SIB container.

[0205] In some examples, the service message relay manager 850 may be configured to or otherwise support a unit for transmitting a first service message between one or more UEs and a first core network service based on sending a first SIB container. In some examples, the service message relay manager 850 may be configured to or otherwise support a unit for transmitting a second service message between one or more UEs and a second core network service based on sending a second SIB container.

[0206] In some examples, the SIB configuration manager 825 may be configured as or otherwise support a unit for sending a first signaling indicating a SIB configuration associated with a core network service to the DU, the SIB configuration including first information associated with communication with the core network service. In some examples, the SIB configuration manager 825 may be configured as or otherwise support a unit for sending an instruction to the DU based on the SIB configuration for the DU to transmit the first information to one or more UEs via the first SIB container. The service message transmission manager 835 may be configured as or otherwise support a unit for transmitting a service message to a UE in one or more UEs based on the instruction.

[0207] In some examples, the SIB configuration manager 825 can be configured as or otherwise support a unit for sending a set of parameters associated with the SIB configuration via a first signaling, wherein the set of parameters includes scheduling information for a first SIB container, a size of the first SIB container, a quality of service metric for the first SIB container, a delivery delay for the first SIB container, a coverage area for the first SIB container, or any combination thereof.

[0208] In some examples, the control signaling manager 845 may be configured or otherwise support means for sending an indication via first signaling that a SIB container associated with a SIB configuration will be transmitted on demand in response to a request from one or more UEs, wherein transmitting the service message is based on the indication.

[0209] In some examples, API manager 840 may be configured or otherwise support means for receiving second signaling indicating API information associated with the DU from the DU, the second core network service, or both, wherein the first signaling is sent based on the API information.

[0210] In some examples, the SIB configuration also includes second information associated with communications with the core network service, and the SIB configuration manager 825 can be configured as or otherwise support a unit for sending instructions to the DU for the DU to transmit the second information to one or more UEs via a second SIB container.

[0211] Fig. 9A diagram of a system 900 including a device 905 supporting techniques for broadcasting system information in a service-based wireless system according to one or more aspects of the present disclosure is shown. The device 905 may be an example of a device 605, a device 705, or a network entity 105 as described herein or include components thereof. The device 905 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which may include communicating through one or more wired interfaces, through one or more wireless interfaces, or any combination thereof. The device 905 may include components that support output and acquisition of communications, such as a communication manager 920, a transceiver 910, an antenna 915, a memory 925, a code 930, and a processor 935. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 940).

[0212] The transceiver 910 may support bidirectional communication via a wired link, a wireless link, or both, as described herein. In some examples, the transceiver 910 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 910 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 905 may include one or more antennas 915, which are capable of sending or receiving wireless transmissions (e.g., concurrently). The transceiver 910 may also include a modem for modulating signals, providing modulated signals for transmission (e.g., through one or more antennas 915, through a wired transmitter), receiving modulated signals (e.g., from one or more antennas 915, from a wired receiver), and demodulating signals. In some implementations, the transceiver 910 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 915 configured to support various receiving or obtaining operations, or one or more interfaces coupled to one or more antennas 915 configured to support various sending or output operations, or a combination thereof. In some implementations, the transceiver 910 may include or be configured to be coupled to one or more processors or memory components that are operable to perform or support operations based on received or obtained information or signals, or to generate information or other signals for transmission or other output, or any combination thereof. In some implementations, the transceiver 910, or the transceiver 910 and one or more antennas 915, or the transceiver 910 and one or more antennas 915 and one or more processors or memory components (e.g., processor 935, or memory 925, or both) may be included in a chip or chip assembly installed in the device 905. In some examples, the transceiver may be operable to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, mid-range communication link, fronthaul communication link 168).

[0213] The memory 925 may include RAM and ROM. The memory 925 may store computer-readable, computer-executable code 930, which includes instructions that, when executed by the processor 935, cause the device 905 to perform various functions described herein. The code 930 may be stored in a non-temporary computer-readable medium (such as system memory or another type of memory). In some cases, the code 930 may not be directly executable by the processor 935, but may cause the computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, in addition to this, the memory 925 may also include a BIOS, which may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0214] The processor 935 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, a discrete gate or transistor logic, a discrete hardware component, or any combination thereof). In some cases, the processor 935 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 935. The processor 935 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 925) so that the device 905 performs various functions (e.g., functions or tasks that support the technology for broadcasting system information in a service-based wireless system). For example, the device 905 or a component of the device 905 may include a processor 935 and a memory 925 coupled to the processor 935, and the processor 935 and the memory 925 are configured to perform various functions described herein. The processor 935 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, a virtual machine, or a container instance), which may host functions (e.g., by executing code 930) to perform the functions of the device 905. Processor 935 can be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 905 (such as, in memory 925). In some implementations, processor 935 can be a component of a processing system. A processing system can generally refer to a system or a series of machines or components that receive input and process input to produce a set of outputs (which can be passed to, for example, other systems or components of device 905). For example, the processing system of device 905 can refer to a system including various other components or subcomponents of device 905, such as processor 935, or transceiver 910, or communication manager 920, or a combination of other components or components of device 905. The processing system of device 905 can be docked with other components of device 905, and can process information (such as input or signal) received from other components or output information to other components. For example, a chip or modem of device 905 can include a processing system and one or more interfaces to output information, or obtain information, or both. The one or more interfaces may be implemented as or otherwise include a first interface configured to output information and a second interface configured to obtain information, or the same interface configured to output information and obtain information, as well as other implementations. In some implementations, the one or more interfaces may refer to an interface between a processing system of a chip or modem and a transmitter, so that the device 905 can send information output from the chip or modem. Additionally or alternatively, in some implementations, the one or more interfaces may refer to an interface between a processing system of a chip or modem and a receiver, so that the device 905 can obtain information or signal input, and the information can be passed to the processing system.One of ordinary skill in the art will readily recognize that the first interface may also obtain information or signal input, and the second interface may also output information or signal output.

[0215] In some examples, bus 940 may support communications of protocol layers (e.g., within protocol layers) of a protocol stack. In some examples, bus 940 may support communications associated with logical channels of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within components of device 905, or communications performed between different components of device 905 that may be co-located or located in different locations (e.g., where device 905 may refer to a system in which one or more of communication manager 920, transceiver 910, memory 925, code 930, and processor 935 may be located in one of the different components or divided between the different components).

[0216] In some examples, the communication manager 920 can manage aspects of communications with the service-based network 130 (e.g., via one or more wired or wireless backhaul links). For example, the communication manager 920 can manage the transmission of data communications for client devices, such as one or more UEs 115. In some examples, the communication manager 920 can manage communications with other network entities 105 and can include a controller or scheduler for controlling communications with the UE 115 in cooperation with the other network entities 105. In some examples, the communication manager 920 can support an X2 interface within an LTE / LTE-A wireless communication network technology to provide communications between network entities 105.

[0217] For example, the communication manager 920 may be configured to or otherwise support a unit for receiving, from a first core network service provided by a service-based network, a first signaling indicating a first SIB configuration associated with the first core network service, the first SIB configuration including first information associated with communications with the first core network service. The communication manager 920 may be configured to or otherwise support a unit for receiving, from a second core network service provided by a service-based network, a second signaling indicating a second SIB configuration associated with the second core network service, the second SIB configuration including second information associated with communications with the second core network service. The communication manager 920 may be configured to or otherwise support a unit for sending a first SIB container including first information to one or more UEs. The communication manager 920 may be configured to or otherwise support a unit for sending a second SIB container including second information to one or more UEs.

[0218] For example, the communication manager 920 may be configured to or otherwise support a unit for sending a first signaling indicating a SIB configuration associated with a core network service to the DU, the SIB configuration including first information associated with communication with the core network service. The communication manager 920 may be configured to or otherwise support a unit for sending an instruction to the DU for the DU to transmit the first information to one or more UEs via the first SIB container based on the SIB configuration. The communication manager 920 may be configured to or otherwise support a unit for transmitting a service message to a UE in one or more UEs based on the instruction.

[0219] By including or configuring the communication manager 920 according to the examples as described herein, the device 905 may support techniques that enable the network entity 105 to broadcast system information to the UE 115 on behalf of the core network service of the service-based network 130. In addition, the techniques described herein may enable the network entity 105 to receive SIB containers from the core network service and relay the SIB containers to the UE 115 without decoding the corresponding SIB containers (e.g., transparent SIB containers). In this regard, aspects of the present disclosure may enable the network entity 105 to efficiently aggregate system information from multiple core network services and relay the system information to other wireless devices, thereby enabling efficient communication of system information and facilitating more efficient and reliable wireless communications. In addition, by enabling the network entity 105 to relay the SIB containers without decoding the SIB containers, the techniques described herein may reduce processing requirements at the network entity 105, thereby reducing network complexity and power consumption.

[0220] In some examples, the communication manager 920 can be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or in cooperation with the transceiver 910, one or more antennas 915 (e.g., when applicable), or any combination thereof. Although the communication manager 920 is shown as a separate component, in some examples, one or more functions described with reference to the communication manager 920 can be supported or performed by the transceiver 910, the processor 935, the memory 925, the code 930, or any combination thereof. For example, the code 930 may include instructions executable by the processor 935 to cause the device 905 to perform various aspects of the techniques for broadcasting system information in a service-based wireless system as described herein, or the processor 935 and the memory 925 may be otherwise configured to perform or support such operations.

[0221] Fig.10A block diagram 1000 of a device 1005 supporting techniques for system information broadcast in a service-based wireless system according to one or more aspects of the present disclosure is shown. The device 1005 may be an example of aspects of a UE 115 as described herein. The device 1005 may include a receiver 1010, a transmitter 1015, and a communication manager 1020. The device 1005 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0222] The receiver 1010 may provide a means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to techniques for broadcasting system information in service-based wireless systems). The information may be communicated to other components of the device 1005. The receiver 1010 may utilize a single antenna or a collection of multiple antennas.

[0223] The transmitter 1015 may provide a means for transmitting signals generated by other components of the device 1005. For example, the transmitter 1015 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to techniques for broadcasting system information in service-based wireless systems). In some examples, the transmitter 1015 may be co-located with the receiver 1010 in a transceiver module. The transmitter 1015 may utilize a single antenna or a collection of multiple antennas.

[0224] The communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations thereof, or various components thereof may be examples of means for performing various aspects of the techniques for system information broadcast in a service-based wireless system as described herein. For example, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations thereof, or components thereof may support methods for performing one or more of the functions described herein.

[0225] In some examples, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a digital signal processor (DSP), a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof that is configured as or otherwise supports means for performing the functions described in the present disclosure. In some examples, the processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0226] Additionally or alternatively, in some examples, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functions of the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be performed by a general purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting means for performing the functions described in the present disclosure).

[0227] In some examples, the communication manager 1020 can be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with the receiver 1010, the transmitter 1015, or both. For example, the communication manager 1020 can receive information from the receiver 1010, send information to the transmitter 1015, or integrate with the receiver 1010, the transmitter 1015, or both in combination to obtain information, output information, or perform various other operations as described herein.

[0228] For example, the communication manager 1020 may be configured to or otherwise support a unit for receiving a first SIB container via a DU, the first SIB container including first information associated with communication with a first core network service provided by a service-based network. The communication manager 1020 may be configured to or otherwise support a unit for receiving a second SIB container via a DU, the second SIB container including second information associated with communication with a second core network service provided by the service-based network. The communication manager 1020 may be configured to or otherwise support a unit for transmitting a first service message with the first core network service via the DU based on the first SIB container. The communication manager 1020 may be configured to or otherwise support a unit for transmitting a second service message with the second core network service via the DU based on the second SIB container.

[0229] By including or configuring the communication manager 1020 according to the examples as described herein, the device 1005 (e.g., a processor controlling the receiver 1010, the transmitter 1015, the communication manager 1020, or a combination thereof or otherwise coupled thereto) can support techniques that enable the network entity 105 to broadcast system information to the UE 115 on behalf of the core network services of the service-based network 130. In addition, the techniques described herein can enable the network entity 105 to receive SIB containers from the core network services and relay the SIB containers to the UE 115 without decoding the corresponding SIB containers (e.g., transparent SIB containers). In this regard, aspects of the present disclosure can enable the network entity 105 to efficiently aggregate system information from multiple core network services and relay the system information to other wireless devices, thereby enabling efficient communication of system information and facilitating more efficient and reliable wireless communications. In addition, by enabling the network entity 105 to relay the SIB containers without decoding the SIB containers, the techniques described herein can reduce processing requirements at the network entity 105, thereby reducing network complexity and power consumption.

[0230] Fig.11 A block diagram 1100 of a device 1105 supporting techniques for system information broadcast in a service-based wireless system according to one or more aspects of the present disclosure is shown. The device 1105 may be an example of aspects of the device 1005 or UE 115 as described herein. The device 1105 may include a receiver 1110, a transmitter 1115, and a communication manager 1120. The device 1105 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0231] The receiver 1110 may provide a means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to techniques for broadcasting system information in service-based wireless systems). The information may be communicated to other components of the device 1105. The receiver 1110 may utilize a single antenna or a collection of multiple antennas.

[0232] The transmitter 1115 may provide a means for transmitting signals generated by other components of the device 1105. For example, the transmitter 1115 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to techniques for broadcasting system information in service-based wireless systems). In some examples, the transmitter 1115 may be co-located with the receiver 1110 in a transceiver module. The transmitter 1115 may utilize a single antenna or a collection of multiple antennas.

[0233] The device 1105 or its various components may be examples of units for performing various aspects of the technology for system information broadcast in a service-based wireless system as described herein. For example, the communication manager 1120 may include a SIB reception manager 1125, a service message transmission manager 1130, or any combination thereof. The communication manager 1120 may be an example of various aspects of the communication manager 1020 as described herein. In some examples, the communication manager 1120 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using a receiver 1110, a transmitter 1115, or both, or otherwise cooperate with a receiver 1110, a transmitter 1115, or both. For example, the communication manager 1120 may receive information from the receiver 1110, send information to the transmitter 1115, or integrate with the receiver 1110, the transmitter 1115, or both in combination to obtain information, output information, or perform various other operations as described herein.

[0234] The SIB reception manager 1125 may be configured to or otherwise support a unit for receiving a first SIB container via a DU, the first SIB container including first information associated with communication with a first core network service provided by a service-based network. The SIB reception manager 1125 may be configured to or otherwise support a unit for receiving a second SIB container via a DU, the second SIB container including second information associated with communication with a second core network service provided by the service-based network. The service message transmission manager 1130 may be configured to or otherwise support a unit for transmitting a first service message with the first core network service via the DU based on the first SIB container. The service message transmission manager 1130 may be configured to or otherwise support a unit for transmitting a second service message with the second core network service via the DU based on the second SIB container.

[0235] Fig.12 A block diagram 1200 of a communication manager 1220 supporting techniques for system information broadcast in a service-based wireless system according to one or more aspects of the present disclosure is shown. The communication manager 1220 may be an example of aspects of the communication manager 1020, the communication manager 1120, or both as described herein. The communication manager 1220 or its various components may be examples of units for performing various aspects of the techniques for system information broadcast in a service-based wireless system as described herein. For example, the communication manager 1220 may include a SIB reception manager 1225, a service message transmission manager 1230, a control signaling reception manager 1235, a request transmission manager 1240, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses).

[0236] The SIB reception manager 1225 may be configured as or otherwise support a unit for receiving a first SIB container via a DU, the first SIB container including first information associated with communication with a first core network service provided by a service-based network. In some examples, the SIB reception manager 1225 may be configured as or otherwise support a unit for receiving a second SIB container via a DU, the second SIB container including second information associated with communication with a second core network service provided by a service-based network. The service message transmission manager 1230 may be configured as or otherwise support a unit for transmitting a first service message to a first core network service via a DU based on the first SIB container. In some examples, the service message transmission manager 1230 may be configured as or otherwise support a unit for transmitting a second service message to a second core network service via a DU based on a second SIB container.

[0237] In some examples, the control signaling reception manager 1235 may be configured or otherwise support a unit for receiving an indication from the DU that a SIB container associated with the first core network service will be provided on demand in response to a request from the UE. In some examples, the request transmission manager 1240 may be configured or otherwise support a unit for transmitting a request for a first SIB container to the DU based on the received indication, wherein the first SIB container is received in response to the request.

[0238] In some examples, the SIB reception manager 1225 may be configured as or otherwise support a unit for receiving a third SIB container via the DU, the third SIB container comprising third information associated with communications with the first core network service, wherein transmitting the first service message is based on receiving the third SIB container.

[0239] In some examples, the SIB reception manager 1225 can be configured as or otherwise support a unit for receiving a third SIB container from the DU, the third SIB container comprising third information associated with communication between the DU and the UE, wherein transmission of the first service message, the second service message, or both is based on the third SIB container.

[0240] In some examples, the control signaling reception manager 1235 may be configured to or otherwise support a unit for receiving, from the DU, third signaling indicating first scheduling information associated with the first SIB container and second scheduling information associated with the second SIB container. In some examples, the SIB reception manager 1225 may be configured to or otherwise support a unit for monitoring the first SIB container and the second SIB container according to the first scheduling information and the second scheduling information, respectively, wherein receiving the first SIB container and the second SIB container is based on monitoring.

[0241] Fig.13A diagram of a system 1300 including a device 1305 supporting techniques for system information broadcast in a service-based wireless system according to one or more aspects of the present disclosure is shown. The device 1305 may be an example of a device 1005, a device 1105, or a UE 115 as described herein or include components thereof. The device 1305 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 1305 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 1320, an input / output (I / O) controller 1310, a transceiver 1315, an antenna 1325, a memory 1330, a code 1335, and a processor 1340. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1345).

[0242] I / O controller 1310 can manage input and output signals for device 1305. I / O controller 1310 can also manage peripheral devices that are not integrated into device 1305. In some cases, I / O controller 1310 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 1310 can utilize a computer such as a MS- , or another known operating system. Additionally or alternatively, I / O controller 1310 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 1310 may be implemented as part of a processor, such as processor 1340. In some cases, a user may interact with device 1305 via I / O controller 1310 or via hardware components controlled by I / O controller 1310.

[0243] In some cases, the device 1305 may include a single antenna 1325. However, in some other cases, the device 1305 may have more than one antenna 1325, which can simultaneously send or receive multiple wireless transmissions. The transceiver 1315 can communicate bidirectionally via one or more antennas 1325, wired or wireless links as described herein. For example, the transceiver 1315 can represent a wireless transceiver and can communicate bidirectionally with another wireless transceiver. The transceiver 1315 may also include a modem for modulating packets, providing the modulated packets to one or more antennas 1325 for transmission, and demodulating packets received from one or more antennas 1325. The transceiver 1315 or the transceiver 1315 and one or more antennas 1325 can be examples of transmitters 1015, transmitters 1115, receivers 1010, receivers 1110, or any combination thereof or components thereof as described herein.

[0244] The memory 1330 may include random access memory (RAM) and read-only memory (ROM). The memory 1330 may store computer-readable, computer-executable code 1335, which includes instructions that, when executed by the processor 1340, cause the device 1305 to perform various functions described herein. The code 1335 may be stored in a non-transitory computer-readable medium (such as system memory or another type of memory). In some cases, the code 1335 may not be directly executable by the processor 1340, but may cause the computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, in addition to this, the memory 1330 may also contain a basic I / O system (BIOS), which may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0245] The processor 1340 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 1340 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 1340. The processor 1340 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 1330) to enable the device 1305 to perform various functions (e.g., functions or tasks that support techniques for broadcasting system information in a service-based wireless system). For example, the device 1305 or a component of the device 1305 may include a processor 1340 and a memory 1330 coupled to or coupled to the processor 1340, and the processor 1340 and the memory 1330 are configured to perform various functions described herein.

[0246] For example, the communication manager 1320 may be configured to or otherwise support a unit for receiving a first SIB container via a DU, the first SIB container including first information associated with communication with a first core network service provided by a service-based network. The communication manager 1320 may be configured to or otherwise support a unit for receiving a second SIB container via a DU, the second SIB container including second information associated with communication with a second core network service provided by a service-based network. The communication manager 1320 may be configured to or otherwise support a unit for transmitting a first service message with the first core network service via the DU based on the first SIB container. The communication manager 1320 may be configured to or otherwise support a unit for transmitting a second service message with the second core network service via the DU based on the second SIB container.

[0247] By including or configuring the communication manager 1320 according to the examples as described herein, the device 1305 may support techniques that enable the network entity 105 to broadcast system information to the UE 115 on behalf of the core network service of the service-based network 130. In addition, the techniques described herein may enable the network entity 105 to receive SIB containers from the core network services and relay the SIB containers to the UE 115 without decoding the corresponding SIB containers (e.g., transparent SIB containers). In this regard, aspects of the present disclosure may enable the network entity 105 to efficiently aggregate system information from multiple core network services and relay the system information to other wireless devices, thereby enabling efficient communication of system information and facilitating more efficient and reliable wireless communications. In addition, by enabling the network entity 105 to relay the SIB containers without decoding the SIB containers, the techniques described herein may reduce processing requirements at the network entity 105, thereby reducing network complexity and power consumption.

[0248] In some examples, the communication manager 1320 can be configured to perform various operations (e.g., receive, monitor, transmit) using or in cooperation with the transceiver 1315, one or more antennas 1325, or any combination thereof. Although the communication manager 1320 is shown as a separate component, in some examples, one or more functions described with reference to the communication manager 1320 can be supported or performed by the processor 1340, the memory 1330, the code 1335, or any combination thereof. For example, the code 1335 may include instructions executable by the processor 1340 to cause the device 1305 to perform various aspects of the techniques for system information broadcast in a service-based wireless system as described herein, or the processor 1340 and the memory 1330 may be otherwise configured to perform or support such operations.

[0249] Fig.14 A flow chart illustrating a method 1400 for supporting techniques for broadcasting system information in a service-based wireless system according to one or more aspects of the present disclosure is shown. The operations of the method 1400 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1400 may be implemented by a network entity or a component thereof as described herein. Figures 1 to 9 In some examples, the network entity may execute an instruction set to control a functional unit of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0250] At 1405, the method may include: receiving, from a first core network service provided by a service-based network, first signaling indicating a first SIB configuration associated with the first core network service, the first SIB configuration including first information associated with communications with the first core network service. The operations of 1405 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1405 may be performed as described with reference to Figure 8 The SIB configuration manager 825 described above is executed.

[0251] At 1410, the method may include: receiving, from a second core network service provided by the service-based network, second signaling indicating a second SIB configuration associated with the second core network service, the second SIB configuration including second information associated with communications with the second core network service. The operations of 1410 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1410 may be performed as described with reference to Figure 8 The SIB configuration manager 825 described above is executed.

[0252] At 1415, the method may include: sending a first SIB container including the first information to one or more UEs. The operations of 1415 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1415 may be performed as described with reference to Figure 8 The SIB transmission manager 830 described above is used for execution.

[0253] At 1420, the method may include sending a second SIB container including the second information to one or more UEs. The operations of 1420 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1420 may be performed as described with reference to Figure 8 The SIB transmission manager 830 described above is used for execution.

[0254] Fig.15A flow chart illustrating a method 1500 for supporting techniques for broadcasting system information in a service-based wireless system according to one or more aspects of the present disclosure is shown. The operations of the method 1500 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1500 may be implemented by a network entity or a component thereof as described herein. Figures 1 to 9 In some examples, the network entity may execute an instruction set to control a functional unit of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0255] At 1505, the method may include: receiving, from a first core network service provided by a service-based network, first signaling indicating a first SIB configuration associated with the first core network service, the first SIB configuration including first information associated with communications with the first core network service. The operations of 1505 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1505 may be performed as described with reference to Figure 8 The SIB configuration manager 825 described above is executed.

[0256] At 1510, the method may include: receiving, via first signaling, a first set of parameters associated with a first SIB configuration, wherein the first set of parameters includes scheduling information for a first SIB container, a size of the first SIB container, a quality of service metric for the first SIB container, a delivery delay for the first SIB container, a coverage area for the first SIB container, or any combination thereof. The operations of 1510 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1510 may be performed by referring to Figure 8 The SIB configuration manager 825 described above is executed.

[0257] At 1515, the method may include: receiving, from a second core network service provided by the service-based network, second signaling indicating a second SIB configuration associated with the second core network service, the second SIB configuration including second information associated with communications with the second core network service. The operations of 1515 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1515 may be performed as described with reference to Figure 8 The SIB configuration manager 825 described above is executed.

[0258] At 1520, the method may include: sending a first SIB container including the first information to one or more UEs, wherein the first SIB container is sent according to the first parameter set. The operations of 1520 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1520 may be performed as described with reference to Figure 8The SIB transmission manager 830 described above is used for execution.

[0259] At 1525, the method may include: sending a second SIB container including the second information to one or more UEs. The operations of 1525 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1525 may be performed as described with reference to Figure 8 The SIB transmission manager 830 described above is used for execution.

[0260] Fig.16 A flow chart illustrating a method 1600 for supporting techniques for broadcasting system information in a service-based wireless system according to one or more aspects of the present disclosure is shown. The operations of the method 1600 may be implemented by a UE or components thereof as described herein. For example, the operations of the method 1600 may be implemented by a UE or components thereof as described herein. Figures 1 to 5 10 to 13 are performed by the UE 115 described. In some examples, the UE can execute an instruction set to control the functional units of the UE to perform the described functions. Additionally or alternatively, the UE can use dedicated hardware to perform various aspects of the described functions.

[0261] At 1605, the method may include: receiving, via the DU, a first SIB container, the first SIB container including first information associated with communications with a first core network service provided by the service-based network. The operations of 1605 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1605 may be performed as described with reference to Fig.12 The SIB reception manager 1225 described above is used to perform.

[0262] At 1610, the method may include: receiving, via the DU, a second SIB container, the second SIB container including second information associated with communications with a second core network service provided by the service-based network. The operations of 1610 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1610 may be performed as described with reference to Fig.12 The SIB reception manager 1225 described above is used to perform.

[0263] At 1615, the method may include: transmitting a first service message with a first core network service via the DU based on the first SIB container. The operations of 1615 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1615 may be described by referring to Fig.12 The described service message delivery manager 1230 is executed.

[0264] At 1620, the method may include: transmitting a second service message with a second core network service via the DU based on the second SIB container. The operations of 1620 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1620 may be described with reference to Fig.12 The described service message delivery manager 1230 is executed.

[0265] Fig.17 A flow chart illustrating a method 1700 for supporting techniques for broadcasting system information in a service-based wireless system according to one or more aspects of the present disclosure is shown. The operations of the method 1700 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1700 may be implemented by a network entity or a component thereof as described herein. Figures 1 to 9 In some examples, the network entity may execute an instruction set to control a functional unit of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0266] At 1705, the method may include: sending first signaling to the DU indicating a SIB configuration associated with the core network service, the SIB configuration including first information associated with communication with the core network service. The operations of 1705 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1705 may be performed as described with reference to Figure 8 The SIB configuration manager 825 described above is executed.

[0267] At 1710, the method may include: sending an instruction to the DU for the DU to transmit first information to one or more UEs via a first SIB container based on the SIB configuration. The operations of 1710 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1710 may be performed as described in reference to Figure 8 The SIB configuration manager 825 described above is executed.

[0268] At 1715, the method may include: transmitting a service message with a UE in one or more UEs based on the instruction. The operations of 1715 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1715 may be performed as described with reference to Figure 8 The described service messaging manager 835 is executed.

[0269] The following provides an overview of various aspects of the present disclosure:

[0270] Aspect 1: A method for wireless communication at a DU, comprising: receiving first signaling indicating a first SIB configuration associated with a first core network service provided by a service-based network, the first SIB configuration including first information associated with communication with the first core network service; receiving second signaling indicating a second SIB configuration associated with a second core network service provided by the service-based network, the second SIB configuration including second information associated with communication with the second core network service; sending a first SIB container including the first information to one or more UEs; and sending a second SIB container including the second information to the one or more UEs.

[0271] Aspect 2: The method according to aspect 1, wherein the first signaling, the second signaling, or both are received according to API information associated with the DU.

[0272] Aspect 3: The method according to any one of Aspects 1 to 2 also includes: receiving a first parameter set associated with the first SIB configuration via the first signaling, wherein the first parameter set includes scheduling information of the first SIB container, the size of the first SIB container, a QoS metric for the first SIB container, a delivery delay for the first SIB container, a coverage area for the first SIB container, or any combination thereof, wherein the first SIB container is sent according to the first parameter set.

[0273] Aspect 4: The method according to any one of Aspects 1 to 3 further includes: receiving, via the first signaling, an indication that a SIB container associated with the first SIB configuration will be provided on demand in response to a request from the one or more UEs, wherein sending the first SIB container is at least partially based on the indication.

[0274] Aspect 5: The method according to Aspect 4 further includes: sending an indication to the one or more UEs that a SIB container associated with the first SIB configuration will be provided on demand in response to a request from the one or more UEs; and receiving a request for the first SIB container from a UE among the one or more UEs based at least in part on sending the indication, wherein the first SIB container is sent to the UE in response to the request.

[0275] Aspect 6: The method according to any one of aspects 1 to 5 further includes: sending a third SIB container to the one or more UEs, wherein the third SIB container includes third information associated with communication between the DU and the one or more UEs.

[0276] Aspect 7: The method according to any one of Aspects 1 to 6 further includes: sending a third signaling indicating API information associated with the DU to the first core network service, the second core network service, an additional core network service, or any combination thereof, wherein the first signaling, the second signaling, or both are received based on the application programming interface information.

[0277] Aspect 8: The method according to any one of Aspects 1 to 7 further includes: sending third signaling to the one or more UEs indicating first scheduling information associated with the first SIB container and second scheduling information associated with the second SIB container, wherein the first SIB container and the second SIB container are sent according to the first scheduling information and the second scheduling information, respectively.

[0278] Aspect 9: A method according to any one of Aspects 1 to 8, wherein the first SIB configuration also includes third information associated with communication with the first core network service, and the method further includes: sending a third SIB container including the third information to the one or more UEs.

[0279] Aspect 10: The method according to any one of aspects 1 to 9 further includes: receiving the first SIB container via the first signaling, wherein sending the first SIB container includes: relaying the first SIB container without decoding the first SIB container.

[0280] Aspect 11: The method according to any one of Aspects 1 to 10 further includes: transmitting a first service message between the one or more UEs and the first core network service based at least in part on sending the first SIB container; and transmitting a second service message between the one or more UEs and the second core network service based at least in part on sending the second SIB container.

[0281] Aspect 12: A method for wireless communication at a UE, comprising: receiving a first SIB container via a DU, the first SIB container including first information associated with communication with a first core network service provided by a service-based network; receiving a second SIB container via the DU, the second SIB container including second information associated with communication with a second core network service provided by the service-based network; transmitting a first service message to the first core network service via the DU based at least in part on the first SIB container; and transmitting a second service message to the second core network service via the DU based at least in part on the second SIB container.

[0282] Aspect 13: The method according to aspect 12, wherein the first signaling, the second signaling, or both are received according to API information associated with the DU.

[0283] Aspect 14: The method according to any one of Aspects 12 to 13 further includes: receiving an indication from the DU that a SIB container associated with the first core network service will be provided on demand in response to a request from the UE; and sending a request for the first SIB container to the DU based at least in part on receiving the indication, wherein the first SIB container is received in response to the request.

[0284] Aspect 15: The method according to any one of Aspects 12 to 14 further includes: receiving a third SIB container via the DU, the third SIB container including third information associated with communication with the first core network service, wherein transmitting the first service message is at least partially based on receiving the third SIB container.

[0285] Aspect 16: The method according to any one of Aspects 12 to 15 further includes: receiving a third SIB container from the DU, the third SIB container including third information associated with the communication between the DU and the UE, wherein transmitting the first service message, the second service message, or both is at least partially based on the third SIB container.

[0286] Aspect 17: The method according to any one of Aspects 12 to 16 further includes: receiving third signaling from the DU indicating first scheduling information associated with the first SIB container and second scheduling information associated with the second SIB container; and monitoring the first SIB container and the second SIB container according to the first scheduling information and the second scheduling information, respectively, wherein receiving the first SIB container and the second SIB container is at least partially based on the monitoring.

[0287] Aspect 18: A method for wireless communication at a core network service provided by a service-based network, comprising: sending a first signaling to a DU indicating a SIB configuration associated with the core network service, the SIB configuration including first information associated with communication with the core network service; sending an instruction to the DU for the DU to transmit the first information to one or more UEs via a first SIB container based at least in part on the SIB configuration; and transmitting a service message to a UE among the one or more UEs based at least in part on the instruction.

[0288] Aspect 19: The method according to aspect 18, wherein the first signaling, the second signaling, or both are sent according to API information associated with the DU.

[0289] Aspect 20: The method according to any one of Aspects 18 to 19 further includes: sending a parameter set associated with the SIB configuration via the first signaling, wherein the parameter set includes scheduling information of the first information block container, the size of the first SIB container, a QoS metric for the first SIB container, a delivery delay for the first SIB container, a coverage area for the first SIB container, or any combination thereof.

[0290] Aspect 21: The method according to any one of Aspects 18 to 20 further includes: sending an indication via the first signaling that a SIB container associated with the SIB configuration will be transmitted on demand in response to a request from the one or more UEs, wherein transmitting the service message is at least partially based on the indication.

[0291] Aspect 22: The method according to any one of Aspects 18 to 21 further includes: receiving API information associated with the DU, wherein sending the first signaling to the DU, sending the instruction to the DU, or both is at least partially based on the API information.

[0292] Aspect 23: The method according to any one of Aspects 18 to 22 further includes: receiving second signaling indicating API information associated with the DU from the DU, a second core network service, or both, wherein the first signaling is sent based on the application programming interface information.

[0293] Aspect 24: A method according to any one of Aspects 18 to 23, wherein the SIB configuration also includes second information associated with the communication with the core network service, and the method further includes: sending an instruction to the DU for the DU to transmit the second information to the one or more UEs via a second SIB container.

[0294] Aspect 25: An apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of aspects 1 to 11.

[0295] Aspect 26: An apparatus comprising at least one unit for performing the method according to any one of aspects 1 to 11.

[0296] Aspect 27: A non-transitory computer-readable medium storing code, the code comprising instructions executable by a processor to perform the method according to any one of aspects 1 to 11.

[0297] Aspect 28: An apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of aspects 12 to 17.

[0298] Aspect 29: An apparatus comprising at least one unit for performing the method according to any one of aspects 12 to 17.

[0299] Aspect 30: A non-transitory computer-readable medium storing code, the code comprising instructions executable by a processor to perform the method according to any one of aspects 12 to 17.

[0300] Aspect 31: An apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of aspects 18 to 24.

[0301] Aspect 32: An apparatus comprising at least one unit for performing the method according to any one of aspects 18 to 24.

[0302] Aspect 33: A non-transitory computer-readable medium storing code, the code comprising instructions executable by a processor to perform the method according to any one of aspects 18 to 24.

[0303] It should be noted that the methods described herein describe possible implementations, and that the operations and steps may be rearranged or otherwise modified, and other implementations are possible. Furthermore, aspects from two or more methods may be combined.

[0304] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for purposes of example, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein are applicable beyond LTE, LTE-A, LTE-A Pro, or NR networks. For example, the described techniques may be applicable to various other wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0305] The information and signals described herein may be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0306] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or executed using a general purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, a combination of one or more microprocessors and a DSP core, or any other such configuration).

[0307] The functions described herein may be implemented using hardware, software executed by a processor, firmware, or any combination thereof. If implemented using software executed by a processor, the functions may be stored as one or more instructions or codes of a computer-readable medium or sent using it. Other examples and implementations are within the scope of the present disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hard wiring, or a combination of any of these items. Features that implement the functions may also be physically located at various locations, including being distributed so that parts of the functions are implemented at different physical locations.

[0308] Computer readable medium includes both non-transitory computer storage medium and communication medium, and communication medium includes any medium that promotes the transmission of computer program from one location to another location.Non-transitory storage medium can be any available medium that can be accessed by general-purpose computer or special-purpose computer.By way of example and not limitation, non-transitory computer readable medium can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage, disk storage or other magnetic storage device, or can be used for carrying or storing desired program code unit and can be accessed by general-purpose or special-purpose computer or general-purpose or special-purpose processor in the form of instruction or data structure Any other non-transitory medium.In addition, any connection is appropriately referred to as computer readable medium.For example, if software is to send from website, server or other remote source using coaxial cable, optical fiber cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave, then coaxial cable, optical fiber cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are included in the definition of computer readable medium. As used herein, disks and optical disks include CDs, laser disks, optical disks, digital versatile disks (DVDs), floppy disks, and Blu-ray disks. Disks can copy data magnetically, while optical disks can copy data optically using lasers. Combinations of the above are also included within the scope of computer-readable media.

[0309] As used herein (including in the claims), "or" as used in a list of items (e.g., a list of items ending with a phrase such as "at least one of" or "one or more of") indicates an inclusive list, so that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). In addition, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an example step described as "based on condition A" can be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on."

[0310] The terms "determine" or "determining" include a wide variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, looking up (e.g., looking up in a table, a database, or another data structure), ascertaining, etc. Furthermore, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), etc. Furthermore, "determining" may include resolving, obtaining, selecting, choosing, establishing, and other such similar actions.

[0311] In the accompanying drawings, similar components or features may have the same reference numeral. In addition, various components of the same type may be distinguished by following the reference numeral with a dash and a second reference numeral, the second reference numeral being used to distinguish between similar components. If only the first reference numeral is used in the specification, the description applies to any of the similar components having the same first reference numeral, without regard to the second reference numeral or other subsequent reference numerals.

[0312] The descriptions set forth herein in conjunction with the accompanying drawings describe example configurations, and do not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration," rather than "preferred" or "advantageous over other examples." For the purpose of providing an understanding of the described techniques, the detailed description includes specific details. However, these techniques may be implemented without these specific details. In some cases, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0313] To enable those skilled in the art to implement or use the present disclosure, the description herein is provided. It will be apparent to those skilled in the art that various modifications to the present disclosure will be apparent, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Therefore, the present disclosure is not limited to the examples and designs described herein, but is given the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for wireless communication at a distributed unit, comprising: receiving, from a first core network service provided by a service-based network, first signaling indicating a first system information block configuration associated with the first core network service, the first system information block configuration comprising first information associated with communications with the first core network service; receiving, from a second core network service provided by the service-based network, second signaling indicating a second system information block configuration associated with the second core network service, the second system information block configuration comprising second information associated with communications with the second core network service; Sending a first system information block container including the first information to one or more user equipments (UEs); as well as A second system information block container including the second information is sent to the one or more UEs.

2. The method according to claim 1, wherein: The first signaling, the second signaling, or both are received according to application programming interface information associated with the distributed unit.

3. The method according to claim 1, further comprising: receiving, via the first signaling, a first parameter set associated with the first system information block configuration, wherein the first parameter set comprises scheduling information of the first system information block container, a size of the first system information block container, a quality of service metric for the first system information block container, a delivery delay for the first system information block container, a coverage area for the first system information block container, or any combination thereof, wherein the first system information block container is sent according to the first parameter set.

4. The method according to claim 1, further comprising: An indication is received via the first signaling that a system information block container associated with the first system information block configuration is to be provided on demand in response to a request from the one or more UEs, wherein sending the first system information block container is based at least in part on the indication.

5. The method according to claim 4, further comprising: sending an indication to the one or more UEs that a system information block container associated with the first system information block configuration will be provided on demand in response to a request from the one or more UEs; as well as A request for the first system information block container is received from a UE of the one or more UEs based at least in part on sending the indication, wherein the first system information block container is sent to the UE in response to the request.

6. The method according to claim 1, further comprising: A third system information block container is sent to the one or more UEs, the third system information block container including third information associated with communication between the distributed unit and the one or more UEs.

7. The method according to claim 1, further comprising: Sending third signaling indicating application programming interface information associated with the distributed unit to the first core network service, the second core network service, an additional core network service, or any combination thereof, wherein the first signaling, the second signaling, or both are received based on the application programming interface information.

8. The method according to claim 1, further comprising: and sending third signaling indicating first scheduling information associated with the first system information block container and second scheduling information associated with the second system information block container to the one or more user equipments, wherein the first system information block container and the second system information block container are sent according to the first scheduling information and the second scheduling information, respectively.

9. The method according to claim 1, wherein: The first system information block configuration further includes third information associated with communication with the first core network service, and the method further includes: A third system information block container including the third information is sent to the one or more UEs.

10. The method according to claim 1, further comprising: The first system information block container is received via the first signaling, wherein sending the first system information block container comprises: relaying the first system information block container without decoding the first system information block container.

11. The method according to claim 1, further comprising: transmitting a first service message between the one or more UEs and the first core network service based at least in part on sending the first system information block container; as well as A second service message is transmitted between the one or more UEs and the second core network service based at least in part on sending the second system information block container.

12. A method for wireless communication at a user equipment (UE), comprising: receiving, via a distributed unit, a first system information block container, the first system information block container comprising first information associated with communications with a first core network service provided by a service-based network; receiving, via the distributed unit, a second system information block container, the second system information block container comprising second information associated with communications with a second core network service provided by the service-based network; transmitting a first service message with the first core network service via the distributed unit based at least in part on the first system information block container; as well as A second service message is transmitted via the distributed unit with the second core network service based at least in part on the second system information block container.

13. The method according to claim 12, wherein: The first service message, the second service message, or both are transmitted according to application programming interface information associated with the distributed unit.

14. The method according to claim 12, further comprising: receiving an indication from the distributed unit that a system information block container associated with the first core network service is to be provided on demand in response to a request from the UE; as well as A request for the first system information block container is sent to the distributed unit based at least in part on receiving the indication, wherein the first system information block container is received in response to the request.

15. The method according to claim 12, further comprising: A third system information block container is received via the distributed unit, the third system information block container comprising third information associated with communication with the first core network service, wherein transmitting the first service message is based at least in part on receiving the third system information block container.

16. The method according to claim 12, further comprising: A third system information block container is received from the distributed unit, the third system information block container comprising third information associated with communication between the distributed unit and the UE, wherein transmitting the first service message, the second service message, or both is based at least in part on the third system information block container.

17. The method according to claim 12, further comprising: receiving, from the distributed unit, third signaling indicating first scheduling information associated with the first system information block container and second scheduling information associated with the second system information block container; as well as The first system information block container and the second system information block container are monitored according to the first scheduling information and the second scheduling information, respectively, wherein receiving the first system information block container and the second system information block container is based at least in part on the monitoring.

18. A method for wireless communication at a core network service provided by a service-based network, comprising: Sending first signaling indicating a system information block configuration associated with a core network service to a distributed unit, the system information block configuration including first information associated with communication with the core network service; sending, based at least in part on the system information block configuration, an instruction to the distributed unit for the distributed unit to transmit the first information to one or more UEs via a first system information block container; as well as A service message is communicated with a UE of the one or more UEs based at least in part on the instruction.

19. The method according to claim 18, wherein: The first signaling, the instruction, or both are sent according to application programming interface information associated with the distributed unit.

20. The method of claim 18, further comprising: A parameter set associated with the system information block configuration is sent via the first signaling, wherein the parameter set includes scheduling information of the first information block container, a size of the first system information block container, a quality of service metric for the first system information block container, a delivery delay for the first system information block container, a coverage area for the first system information block container, or any combination thereof.

21. The method of claim 18, further comprising: An indication is sent via the first signaling that a system information block container associated with the system information block configuration is to be transmitted on demand in response to a request from the one or more UEs, wherein transmitting the service message is based at least in part on the indication.

22. The method of claim 18, further comprising: Second signaling indicating application programming interface information associated with the distributed unit is received from the distributed unit, a second core network service, or both, wherein the first signaling is sent according to the application programming interface information.

23. The method of claim 18, further comprising: Application programming interface information associated with the distributed unit is received, wherein sending the first signaling to the distributed unit, sending the instruction to the distributed unit, or both is based at least in part on the application programming interface information.

24. The method according to claim 18, wherein: The system information block configuration further includes second information associated with communications with the core network service, the method further comprising: An instruction is sent to the distributed unit for the distributed unit to transmit the second information to the one or more UEs via a second system information block container.

25. An apparatus for wireless communication at a user equipment (UE), comprising: processor; a memory coupled to the processor; as well as Instructions, which are stored in the memory and can be executed by the processor to cause the device to perform the following operations: receiving, via a distributed unit, a first system information block container, the first system information block container comprising first information associated with communications with a first core network service provided by a service-based network; receiving, via the distributed unit, a second system information block container, the second system information block container comprising second information associated with communications with a second core network service provided by the service-based network; transmitting a first service message with the first core network service via the distributed unit based at least in part on the first system information block container; as well as A second service message is transmitted via the distributed unit with the second core network service based at least in part on the second system information block container.

26. The device according to claim 25, wherein The first service message, the second service message, or both are transmitted according to application programming interface information associated with the distributed unit.

27. The device according to claim 25, wherein: The instructions may also be executed by the processor to cause the device to perform the following operations: receiving an indication from the distributed unit that a system information block container associated with the first core network service is to be provided on demand in response to a request from the UE; as well as A request for the first system information block container is sent to the distributed unit based at least in part on receiving the indication, wherein the first system information block container is received in response to the request.

28. The device according to claim 25, wherein The instructions may also be executed by the processor to cause the device to perform the following operations: A third system information block container is received via the distributed unit, the third system information block container comprising third information associated with communication with the first core network service, wherein transmitting the first service message is based at least in part on receiving the third system information block container.

29. The device according to claim 25, wherein: The instructions may also be executed by the processor to cause the device to perform the following operations: A third system information block container is received from the distributed unit, the third system information block container comprising third information associated with communication between the distributed unit and the UE, wherein transmitting the first service message, the second service message, or both is based at least in part on the third system information block container.

30. The device according to claim 25, wherein: The instructions may also be executed by the processor to cause the device to perform the following operations: receiving, from the distributed unit, third signaling indicating first scheduling information associated with the first system information block container and second scheduling information associated with the second system information block container; as well as The first system information block container and the second system information block container are monitored according to the first scheduling information and the second scheduling information, respectively, wherein receiving the first system information block container and the second system information block container is based at least in part on the monitoring.

Images