Wireless communications with access control on service-based architecture

Abstract

An access control service for wireless communication obtains information for one or more services in a wireless network having a service-based architecture. The access control service provides an access control configuration for one or more cells based on the information from the one or more services. A network node provides information to the access control service in the wireless network and receives an access control configuration from the access control service based at least in part on the information and additional information for one or more services of the wireless network. The network node provides the access control configuration for at least one user equipment (UE). The UE receives the access control configuration from the access control service and determines whether to access a service of the wireless network based on the access control configuration and at least one of incoming traffic or service information.

Description

Technical Field

[0001] This disclosure relates in general to communication systems, and more specifically to wireless communications including access control. Background Technology

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

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

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

[0005] In some aspects, the technology described herein relates to an apparatus for an access control service for wireless communication, the apparatus comprising: one or more memories; and one or more processors coupled to the one or more memories and configured to cause the access control service to: obtain information at the access control service for one or more services in a wireless network having a service-based architecture; and provide access control configuration for one or more cells based on the information from the one or more services.

[0006] In some aspects, the technology described herein relates to a method for wireless communication at an access control service for wireless communication, the method comprising: obtaining information at the access control service for one or more services in a wireless network having a service-based architecture; and providing access control configuration for one or more cells based on the information from the one or more services.

[0007] In some aspects, the technology described herein relates to an apparatus for wireless communication at an access control service for wireless communication, the apparatus comprising: components for obtaining information at the access control service for one or more services in a wireless network having a service-based architecture; and components for providing access control configuration for one or more cells based on the information from the one or more services.

[0008] In one aspect of this disclosure, a computer-readable storage medium is provided. The computer-readable medium stores computer-executable code at an access control service for wireless communication, which, when executed by one or more processors, causes the access control service to: obtain information at the access control service for one or more services in a wireless network having a service-based architecture; and provide access control configuration for one or more cells based on the information from the one or more services.

[0009] In some aspects, the technology described herein relates to an apparatus for wireless communication at a network node, the apparatus comprising: one or more memories; and one or more processors coupled to the one or more memories and configured to cause the network node to: provide information to an access control service in a wireless network; receive access control configuration from the access control service based at least in part on the information and additional information for one or more services of the wireless network; and provide the access control configuration for at least one user equipment (UE).

[0010] In some aspects, the technology described herein relates to a method for wireless communication at a network node, the method comprising: providing information to an access control service in a wireless network; receiving access control configuration from the access control service based at least in part on the information and additional information for one or more services of the wireless network; and providing the access control configuration for at least one user equipment (UE).

[0011] In some aspects, the technology described herein relates to an apparatus for wireless communication at a network node, the apparatus comprising: components for providing information to an access control service in a wireless network; components for receiving access control configuration from the access control service based at least in part on the information and additional information for one or more services of the wireless network; and components for providing the access control configuration for at least one user equipment (UE).

[0012] In one aspect of this disclosure, a computer-readable storage medium is provided. The computer-readable medium stores computer-executable code at a network node, which, when executed by one or more processors, causes the network node to: provide information to an access control service in a wireless network; receive access control configuration from the access control service based at least in part on the information and additional information for one or more services of the wireless network; and provide the access control configuration for at least one user equipment (UE).

[0013] In some aspects, the technology described herein relates to an apparatus for wireless communication at a user equipment (UE), the apparatus comprising: one or more memories; and one or more processors coupled to the one or more memories and configured to cause the UE to: receive access control configuration from an access control service in a wireless network having a service-based architecture; and determine, based on at least one of the access control configuration from the access control service and incoming service information, whether to access the service of the wireless network.

[0014] In some aspects, the technology described herein relates to a method for wireless communication at a UE, the method comprising: receiving access control configuration from an access control service in a wireless network having a service-based architecture; and determining, based on at least one of the access control configuration from the access control service and incoming service information, whether to access the service of the wireless network.

[0015] In some aspects, the technology described herein relates to an apparatus for wireless communication at a UE, the apparatus comprising: components for receiving access control configuration from an access control service in a wireless network having a service-based architecture; and components for determining whether to access a service of the wireless network based on at least one of the access control configuration from the access control service and incoming service information.

[0016] In one aspect of this disclosure, a computer-readable storage medium is provided. The computer-readable medium stores computer-executable code at a UE, which, when executed by one or more processors, causes the UE to: receive access control configuration from an access control service in a wireless network having a service-based architecture; and determine, based on at least one of the access control configuration from the access control service and incoming service information, whether to access the service of the wireless network.

[0017] In some aspects, the technology described herein relates to an apparatus for a wireless communication service, the apparatus comprising: one or more memories; and one or more processors coupled to the one or more memories and configured to cause the service to: provide information for the service to one or more access control services; and receive attempts for a user equipment (UE) to access the service based on access control configurations from the one or more access control services.

[0018] In some aspects, the technology described herein relates to a method for conducting wireless communication at a service for wireless communication, the method comprising: providing information for one or more access control services; and receiving an attempt for a user equipment (UE) to access the service based on an access control configuration from one or more access control services.

[0019] In some aspects, the technology described herein relates to an apparatus for conducting wireless communication at a service for wireless communication, the apparatus comprising: components for providing information for one or more access control services; and components for receiving an attempt by a user equipment (UE) to access the service based on an access control configuration from one or more access control services.

[0020] In one aspect of this disclosure, a computer-readable storage medium is provided. The computer-readable medium stores computer-executable code at a service for wireless communication, which, when executed by one or more processors, enables the service to: provide information for the service to one or more access control services; and receive attempts for user equipment (UE) to access the service based on access control configurations from the one or more access control services.

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

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

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

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

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

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

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

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

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

[0030] Figure 5B This is an illustration of example aspects of a cloud platform that may include a core network and RAN services, illustrative of various aspects of this disclosure.

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

[0032] Figure 7A This is a diagram illustrating example protocols at the core network and radio area network (RAN).

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

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

[0035] Figure 8AExamples of centralized access control services in service-based network architectures for wireless communication according to various aspects of this disclosure are illustrated.

[0036] Figure 8B Examples of inputs and outputs for access control services according to various aspects of this disclosure are illustrated.

[0037] Figure 9 Examples of distributed access control services in a service-based network architecture for wireless communication according to various aspects of this disclosure are illustrated.

[0038] Figure 10 Example call flowcharts illustrating various aspects of this disclosure of access control configurations from a centralized access control service that can be broadcast as system information.

[0039] Figure 11 Example call flowcharts illustrating various aspects of this disclosure of access control configurations from a centralized access control service that can be provided in response to a request.

[0040] Figure 12 Example call flowcharts illustrating various aspects of this disclosure of access control configurations from a distributed access control service that can be broadcast as system information.

[0041] Figure 13 Example call flowcharts illustrating various aspects of this disclosure of access control configurations from a distributed access control service that can be provided in response to a request.

[0042] Figure 14 This is a flowchart of a method for configuring access control at an access control service in accordance with various aspects of this disclosure.

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

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

[0045] Figure 17 This is a flowchart of a method for providing services in a wireless network according to various aspects of this disclosure.

[0046] Figure 18 These are illustrations of specific hardware implementations of example devices and / or UEs according to various aspects of this disclosure.

[0047] Figure 19 These are illustrations of specific hardware implementations of example network entities according to various aspects of this disclosure.

[0048] Figure 20 This is a diagram illustrating examples of hardware implementations of an example access control service according to various aspects of this disclosure.

[0049] Figure 21 These are illustrations illustrating specific hardware implementations of example services according to various aspects of this disclosure. Detailed Implementation

[0050] Wireless networks can have a service-based architecture that combines the functions of core network and radio access network (RAN) nodes. This service-based architecture can be provided on a cloud platform using application programming interfaces (APIs). Compared to the functional division between the core network and the radio area network (RAN), a service-based architecture can host a combination of core network and RAN services on a cloud platform. A "service" refers to functionality exposed by network entities through a service-based interface and invoked by other network entities. Services can provide a variety of functionalities for wireless networks. Examples of services may include access control services, mobility services, public alert system (PWS) services, vehicle-to-everything (V2X) services, multicast and broadcast services (MBS) services, location services, system information (SI) services, slicing services, terrestrial network (TN) services, non-terrestrial network (NTN) services, standalone non-public network (SNPN) services, time-sensitive network (TSN) services, or enhanced distributed unit (eDU), etc. A service-based architecture enables the individual services hosted on the wireless network platform to be adapted or upgraded independently of other services. In wireless networks without a service-based architecture (e.g., NR wireless systems without a service-based architecture), a unified access control (UAC) framework can be employed. Depending on the network operator's policies, deployment scenarios, subscriber profiles, and available services, different criteria can be used to determine which access attempts will be allowed or blocked when congestion occurs in the system. In wireless networks supporting a service-based architecture, access control mechanisms can be adapted to the service-based architecture and can provide protection mechanisms for the intended service (e.g., if the service suffers processing overload). The aspects presented in this paper provide an access control framework that includes an access control service as one of the services in a service-based architecture. As used herein, an "access control service" refers to a service that generates, manages, and provides access control configurations with one or more access control parameters for one or more services of the wireless network. The access control service enables access control configuration based on a more global perspective of the load across various services.

[0051] "Access control configuration" includes one or more parameters that affect access control to network services (including eDU). The set of one or more parameters in the access control configuration may be referred to as the "access control profile". In some respects, these parameters may be referred to as "prohibition parameters" because they indicate to the UE the access identifier and / or access category for services that are allowed or prohibited (e.g., not permitted). The UE can use the access control configuration to determine whether to attempt to access a specific service. The term "attempt to access" may refer to sending one or more messages to attempt to establish a connection to a cell, network node, or attempt to access a network service.

[0052] As described herein, an access control service may receive access control assistance information from one or more services of the network and may use this information to generate and provide access control configurations. The access control service enables a more global perspective on the load at various service locations and allows the access control service to generate access control configurations that help protect services, including eDUs, from overload or resolve overload issues at one or more service locations (e.g., load exceeding a threshold or capacity supported by the service). "Access control assistance information" may refer to information that assists the access control service in generating access control configurations. Examples of access control assistance information include service load status (e.g., load percentage), service priority, cell load status for one or more cells, radio resource load status, associated area and / or associated timing information. For example, a cell provides network coverage and services to a UE. In some aspects, the access control service may be a centralized service that provides access control configurations for multiple eDUs. A centralized access control service enables access control configuration based on a more global perspective on the load or other aspects experienced by various services. In some aspects, the access control service may be a distributed access control service co-located with eDUs. This enables, for example, the provision of access control services that can be co-located with the eDU.

[0053] Although the example aspect is described as being performed by an eDU, which is an example of a network node in a wireless network that sends and receives signaling with the UE, the network node may also be referred to by other names, such as base station, 6G base station, radio node, RAN, RAN node, 6G RAN, network entity, or DU, etc.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0068] Different functional divisions can be provided for eDUs in a service-based architecture, for example, by combining... Figure 5B and Figure 6 As described.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0082] In some aspects, UE 104 may include access component 198, which is configured to enable UE 104 to receive access control configuration from an access control service in a wireless network with a service-based architecture, and to attempt to access a service based on at least one of the access control configuration from the access control service and incoming service or expected service information.

[0083] Network nodes (such as base stations 102, 180, components of base stations, or radio nodes (e.g., CU 106, DU 105, eDU 171, and / or RU 109) may include access control component 199. In some aspects, access control component 199 may be configured to cause network nodes to provide information to access control service 173 and to receive access control configuration from access control service 173 based at least in part on that information and additional information from one or more services of the wireless network. Access control component 199 may be configured to cause network nodes to provide access control configuration to at least one UE 104. In some aspects, service 175 may include access control component 199, which is configured to cause the service to provide information for service 175 to one or more access control services 173 and to receive an attempt to access the service from UE 104 based on the access control configuration from the access control service 173 that provided the information to it.

[0084] In some aspects, access control service 173 may include access control component 191. In some aspects, access control component 191 may be configured to enable access control service 173 to: receive information from one or more services (e.g., 175 or eDU 171) in a service-based wireless network; and provide access control configuration for one or more cells provided by a network node based on the information from the one or more services. The network node may then provide the access control configuration to one or more UEs 104.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0101] Refer again Figure 2 In some respects, with Figure 1 Similar to UE 104, UE 204 may include access component 198, which is configured to enable UE 204 to receive access control configuration from an access control service in a wireless network with a service-based architecture, and to attempt to access a service based on at least one of the access control configuration from the access control service and incoming service or expected service information.

[0102] Network nodes (such as base station 202, or components of a base station (e.g., CU 210, DU 230, eDU, and / or RU 240) may include access control component 199. In some aspects, access control component 199 may be configured to cause network nodes to provide information to access control service 173, and to receive access control configuration from access control service 173 based at least in part on that information and additional information from one or more services of the wireless network. Access control component 199 may be configured to cause network nodes to provide access control configuration to at least one UE 104.

[0103] In some aspects, the wireless network may include, for example, a service-based architecture and may include an access control service 173, which includes an access control component 191. In some aspects, the access control component 191 may be configured to enable the access control service 173 to: receive information from one or more services (e.g., 175 or eDU 171) in a wireless network with a service-based architecture; and to provide access control configuration for one or more cells provided by a network node based on the information from the one or more services. The network node may then provide the access control configuration to one or more UEs 104.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0121] At least one of the TX processor 468, RX processor 456, and controller / processor 459 can be configured to perform coupled operations. Figure 1 The access components of 198 are discussed in various aspects.

[0122] At least one of the TX processor 416, RX processor 470, and controller / processor 475 can be configured to perform combined operations. Figure 1 The various aspects of the access control component 199.

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

[0124] Figure 5A This is a diagram 500 illustrating an example functional partitioning between the core network 530 and the RAN 540. Figure 1 and Figure 2 Various example aspects of the core network (e.g., EPC 160, core network 190, 220) are illustrated, and Figure 1 An example of a base station 102 / 180 as a RAN is shown. Figure 5A Examples of UPF 595, SMF 594 and AMF592 as part of the core network 530 are shown. Figure 5A The diagram illustrates CU-UP 502 (e.g., providing user plane functionality), CU-CP 504 (e.g., providing control plane functionality), and DU 506, all provided as part of RAN 540. CU-CP and / or CU-UP may include features for… Figure 2 The aspects described in CU106 and / or 210. DU 506 may include those for... Figure 1 DU 105 or Figure 2 The various aspects described in DU 230. As an example, Figure 5A The various aspects of the core network / RAN hierarchy can be adopted, for example, in 3G, 4G and / or 5G wireless networks. Figure 5A Functional partitioning can help maintain the performance and security of the wireless network as well as the accessibility of field equipment. Figure 5AExamples of aspects of core network 530 may include cloud platform 508, and examples of aspects of RAN 540 may include cloud platform 510. The cloud platform provides a framework for an operating system that uses computing resources in a web-based data center via the Internet. In some aspects, the cloud platform may be, for example, a cloud-native platform. A cloud platform may refer to the operating system and hardware of one or more servers in an Internet-based data center.

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

[0126] Figure 6 This is a diagram 600 illustrating a converged service-based core network and RAN, and showing the various functions performed by the core network (e.g., AMF 692) and RAN (e.g., CU-CP 602 and / or DU 604) that can be combined. Figure 5B The system is described as a service-based platform distribution. It may be referred to herein as converged because at least some functions of the core network and RAN are combined into one or more of these services. Figure 6 An example functional partitioning 610 between the core network (e.g., 692) and the RAN (e.g., 602 and 604) is illustrated. As illustrated by the arrows, various aspects of the inter-DU functions 606 performed by AMF 692 and / or CU-CP 602 can be performed by different services 612 and 614 in a service-based architecture. Figure 6For example, the in-DU function 608 performed by CU-CP602 and / or DU 604 can be performed by eDU 624 (as an example of a network node or radio node) using a cloud-based architecture 626. Figure 6 The service-based architecture is also illustrated as potentially including one or more applications 620 and 622.

[0127] For example, a converged service-based core network and RAN may include a single cloud platform for hosting applications as well as core network and RAN services. This architecture extends the service-based architecture to the RAN. This architecture enables cloud-based systems that, for example, provide scalability, resilience, toughness, reusability, agility, visibility, automation, and / or protection in fault conditions, among other benefits. Each service (e.g., 512 or 612) can scale independently, and resources can be added or removed for individual services.

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

[0129] Figure 7A Examples of monolithic protocols that can be used in conjunction with the core network (e.g., Non-Access Layer (NAS)) and the RAN (e.g., RRC) (e.g., in networks without a service-based architecture) are illustrated. A single control plane protocol can be provided for all control plane functions. Figure 7A Examples of these protocols may include physical layer protocol 702, media access control (MAC) protocol 704, radio link control (RLC) protocol 706, packet data convergence protocol (PDCP) 708, radio resource control (RRC) protocol 710, NAS protocol 712, IP protocol 711, and service data adaptation protocol (SDAP) 709.

[0130] Configuration aspects for performance-sensitive features (e.g., RRC configuration) and activation / deactivation aspects (e.g., MAC layer aspects) can be decoupled from the service-based architecture. For example, group replication can be configured by RRC and activated and deactivated by MAC-CE. Figure 7B It is shown, for example, for such as Figure 5B or Figure 6The service-based architecture is illustrated in Figure 700, which separates L2 functions 703 (e.g., RLC and / or MAC functions) and the PHY layer aspect 701 from services 713, 714, and 716. Protocols can be service-specific and can be updated individually. This architecture enables adaptation across different vertical domains (e.g., services 713, 714, or 716) and deployment types (e.g., wireless network deployments). Different providers or hosts can offer different services. For example, Figure 7B The model can include separate layers for NAS and access hierarchy (AS).

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

[0132] In wireless networks without a service-based architecture (e.g., NR wireless systems without a service-based architecture), a unified access control (UAC) framework can be employed. Depending on the network operator's policies, deployment scenarios, subscriber profiles, and available services, different criteria can be used to determine which access attempts will be allowed or blocked when congestion occurs in the system. As an example, different criteria for access control can be associated with access identifiers and / or access classes. An access identifier can correspond to a UE class (e.g., such as a priority UE, mission-critical UE, or regular (or non-priority) UE, etc.). An access identifier can correspond to the service attempted to be accessed (e.g., a mobile-initiated (MO) service or a mobile-terminated (MT) service, etc.). The wireless network can provide a single unified access control, enabling the operator to control access based on access class and access identifier. In some aspects, the RAN (e.g., a base station) can broadcast prohibition control information with a list of prohibited parameters associated with the access class and access identifier (e.g., this prohibition control information may be referred to as a unified access control configuration or UAC configuration). The UAC configuration can be generated by the RAN or a core network entity (such as OAM). UAC configuration can be generated based on the current cell load and can be applied to the corresponding cell (e.g., only to the corresponding cell). As an example, the base station can broadcast prohibition control information in SIB1. In an example with network sharing, prohibition control information can be set individually for each PLMN. Each access attempt by the UE can be classified into one or more of an access identifier (e.g., the UE class of the UE attempting to access) or an access category (e.g., the service class of the service the UE is attempting to access). Based on the access control information (e.g., prohibition information received in SIB1) applicable to the access identifier and access category of the access attempt, the UE can perform access control by determining whether to perform the access attempt. For example, the UE can compare received prohibition parameters to see if the UE's access identifier (e.g., UE class) or access category (e.g., the service class the UE will attempt to access) is indicated as prohibited by the prohibition parameters broadcast by the base station. Non-access spectrum (NAS) procedures can be used to determine the access identifier and access category. RRC procedures can be used for access checks, for example, for attempted access. In some aspects, UAC triggering may include RRC idle state, RRC connected state, or RRC inactive state. As an example, the network can operate in either a standalone non-public network (SNPN) or a non-SNPN mode.

[0133] In wireless networks that support service-based architectures (e.g., as combined with...) Figure 5B , Figure 6 and Figure 7BAs described, access control mechanisms are adaptable to service-based architectures and can provide protection mechanisms for anticipated services (e.g., if the service suffers processing overload). The aspects presented herein propose the generation and management of access control configurations in wireless networks with service-based architectures, where the access control configuration prevents UE access if an anticipated network node (e.g., an anticipated service or RAN node) is overloaded. The aspects presented herein also propose network entities for generating and managing access control configurations and providing mechanisms for UEs to obtain access control configurations.

[0134] For example, the aspects presented in this paper provide access control mechanisms for wireless networks with service-based architectures. Access control configurations can be generated based on load input from other services. In some aspects, services may include eDUs (eDUs). For example, services may include eDU services and other non-eDU services. Access control services can be introduced to provide a more global perspective on access control configurations.

[0135] In some respects, access control configuration can be delivered to the UE via the user plane. Access control configuration can be configured for one or more purposes. As an example, access control configuration can be configured for eDU load control (e.g., to control the load experienced at the eDU due to access granted to a UE served by the eDU). Access control configuration can be configured to protect the eDU from overload, or to protect the eDU when it is overloaded. The UE can check the access control configuration to determine whether to allow the UE's access attempt to establish a connection with the eDU based on incoming traffic.

[0136] As another example, access control configuration can be configured for service load control (e.g., services other than the eDU). The UE can check the access control configuration to determine whether to allow an access attempt to the expected service based on information about the expected service. For example, the UE can determine whether to allow the UE to establish a connection with the eDU to achieve an access attempt to the expected service based on the access control configuration and expected service information.

[0137] As described in this article, for service-based and / or converged network architectures, access control services can be provided to generate and manage access control configurations. In some aspects, access control services can be centralized access control services. Figure 8A and Figure 9 An example of a centralized access control service is illustrated. In some respects, a distributed access control service can be provided within a network. Figure 10 An example of a distributed access control service is shown. Figure 8A The access control service 814 in the diagram 800 is a centralized access control service because the access control service 814 provides access control configuration to multiple eDUs (e.g., it is centralized for multiple eDUs), and Figure 9 The distributed access control service illustrated herein may co-locate with the eDU. eDU 802 may serve UE 804, and eDU 803 may serve UE 805.

[0138] As input, the access control service can receive information from other services, including eDU. Figure 8B This is an illustration 850 showing how access control service 814 receives input from other network nodes (e.g., from eDUs 802 and 803 and other services (e.g., services X 812 and Y 816)) via API 817. As a non-limiting example of a service, Figure 8A The example service X812 is shown as a slice service, and the example service Y is shown as an SNPN or Time-Sensitive Network (TSN). Wireless networks can include various types of services, and the examples of slice services and SNPN / TSN services are for illustrative purposes only.

[0139] In some aspects, one or more eDUs (e.g., 802 and / or 803) may provide information (such as load information) to the access control service 814. Dashed lines 822 and 824 illustrate eDUs 802 and 803 providing such information to the access control service 814 (e.g., to a centralized access control service). As an example, an eDU may provide the access control service 814 with load information for a cell (e.g., a single cell) provided by the eDU. In some aspects, an eDU may provide the access control service 814 with load information for multiple cells provided by the eDU. Figure 8ADashed lines 826 and 828 are also shown, representing information provided to access control service 814 by services X 812 and Y 816 (e.g., these services may be referred to as non-DU services or other services). In some aspects, other services (e.g., 812 or 816) may provide cell-specific information. Access control service 814 generates access control configuration, for example, at least in part, based on information received from eDU and / or other services. As output, access control service 814 may provide access control configuration for one or more UEs (e.g., UE 804 and / or 805), and in some aspects, the access control configuration may be delivered to the UE on the user plane. For example, as output, access control configuration may be provided to the UE using system information (SI) sent by the eDU, or may be provided based on (e.g., in response to) a request from the UE. In some aspects, a request for access control configuration may be referred to as an access control configuration query. The access control configuration provided by access control service 814 may be applicable to a region (e.g., a set of one or more cells). For example, the eDU may provide a single cell or multiple cells. Table 2 illustrates examples of access control configurations that access control service 814 can provide to eDU 802 and / or eDU 803. Table 2

[0140] Various network architectures can support access control services. For example, in some aspects, wireless networks can have centralized access control services. In others, wireless networks can have distributed access control services. Figure 8A An example of a wireless network with a centralized architecture is illustrated, such as a centralized access control service (e.g., 814) that provides access control configurations for multiple eDUs. As an example, an independent network node may implement access control service 814. Access control service 814 generates and manages access control configurations taking into account inputs from other services and eDUs. Access control service 814 may have a more global view of the load conditions at various network nodes and is capable of providing regional access control configurations (e.g., access control configurations across multiple eDUs).

[0141] In some respects, a service (or services) may experience processing overload (e.g., the service's processing load exceeds a threshold or the capacity supported by the service), and the service may not have sufficient processing capacity to handle the current load at the service level. Figure 8AAs shown, services (such as the examples of services X 812 and Y 816) may provide input information to access control service 814. Input information may include, for example, service load status (e.g., load percentage), service priority, area range, and / or time range. For example, service X 812 may provide service load status or current load percentage to access control service 814. Additionally or alternatively, service X 812 may provide service priority. In some aspects, service priority may be indicated as a level, such as high priority, medium priority, and / or low priority. In some aspects, priority may be indicated as, for example, priority 1, 2, 3, or 4. Additionally or alternatively, service X 812 may indicate the area associated with the provided information. For example, service load status may be associated with one or more cells, or with a geographic area. Additionally or alternatively, service X 812 may indicate a time period associated with the service information. For example, this time period may include a time range associated with the service load information. As an example, the service may indicate that the service load information is applicable within the indicated time range. One or more eDUs may also provide input information to the access control service 814. The input information may include cell load status, radio resource load status, area range, and / or time range for one or more cells. As described for service information from other services, the eDU may indicate the area (e.g., cell or geographic region) to which the cell load status / radio resource load status applies. Additionally or alternatively, the eDU may indicate the time, time period, or time range associated with the cell load status / radio resource load status provided to the access control service 814.

[0142] In some respects, wireless networks can have a distributed access control service architecture. Figure 9 Examples of distributed access control services (e.g., access control services (906 and 907)) are illustrated. In a distributed network, the access control service (e.g., 906 or 907) may co-located with the corresponding eDU. In some aspects, the eDU may implement access control functionality. For example, the access control service at the corresponding eDU may generate and manage access control configurations based on inputs from services 912, 914, and / or 916 and based on local cell load conditions. This allows for the deployment of fewer services and enables the eDU to determine the services from which it (or the access control service at the eDU) will receive access control information. Figure 9 Example 900 illustrates an access control service 906 co-located with eDU 902 and an access control service 907 co-located with eDU 903. As shown at 922, eDU 902 (and the corresponding access control service 906) may receive information from service X (e.g., 912). In some aspects, eDU 902 may also receive information from one or more services among services 914 or 916.

[0143] In some respects, the distributed access control service may be referred to as an access control function co-located with the eDU, and the access control configuration may be generated by the eDU. For example, the eDU may access other services (e.g., services 912, 914, and / or 916) via API 917, and these other services may provide auxiliary information to the access control service (e.g., 906 or 907) at the eDU (e.g., 902 or 903). This auxiliary information may include, for example, service load status (e.g., load percentage) or service priority. One or more of these services may experience processing overload (e.g., as described above), and the service may not have sufficient processing capacity to meet the current load. The eDU (e.g., the access control service at the eDU) may generate or adjust the access control configuration based on input auxiliary information from other services and the local load conditions at the eDU.

[0144] Figures 10 to 13 Various examples of obtaining access control configuration are shown. Figure 10 Example communication diagram 1000 illustrates access control configurations from a centralized access control service (e.g., 1010), which can be broadcast as system information. As shown at 1020, 1022, 1028, and 1030, access control service 1010 can receive service information from one or more services. Services may include one or more eDUs, such as eDU 1006 and / or eDU 1008. The information may correspond to a combination of... Figure 8B The inputs described. Information from service X 1012 and / or service Y 1014 may include service load status (e.g., load percentage), service priority, associated area, and / or associated timing information. Information from eDU 1006 and / or 1008 may include cell load status, radio resource load status, area information, and / or associated timing information for one or more cells. In some aspects, access control service 1010 may provide queries (or requests) for information. Figure 10 The example illustrates that the access control service 1010 provides queries 1016, 1018, 1024, and 1026 to various services, and shows that service information 1020, 1022, 1028, and 1030 can be provided to the access control service 1010 by various services in response to the corresponding queries (e.g., 1016, 1018, 1024, and 1030).

[0145] At 1032, access control service 1010 can generate one or more access control configurations based on the received service information. The access control configurations may correspond to... Figure 8BThe output is illustrated in the table. For example, Access Control Service 1010 can generate one or more access control profiles based on requests from other services and eDUs. In some aspects, access control configurations can be specific to one or more cells, as described in conjunction with Table 2.

[0146] The access control service may provide access control configuration to one or more eDUs, as shown at 1034 and 1044. The eDU may provide (e.g., transmit) the received access control configuration, as shown at 1036 and 1046. In some aspects, the eDU may broadcast the access control configuration, for example, in system information. In some aspects, the eDU may provide the access control configuration in an SIB (such as SIB1). For example, the access control configuration may be provided to the UE via system information. For example, if UE 1004 does not have a valid access control configuration, UE 1004 may obtain access control configuration 1036. In some aspects, if SIB1 indicates access control parameters (e.g., access control configuration), the UE may apply the configuration from SIB1 in the corresponding cell.

[0147] UE 1002 and / or 1004 derive applicable access control parameters (e.g., prohibition parameters) based on the access control profile indicated in access control configuration 1036 or 1044, and one or more of UE type, access attempt, service information, current area, and / or current time. Upon receiving the access control configuration at 1036, UE 1004 may determine, based on the received access control configuration, whether to attempt access (e.g., access to a cell provided by eDU 1008 and / or access to a service such as service X 1012 or service Y 1014), as illustrated at 1038. In some aspects, this determination may be referred to as an access control check. For example, UE 1004 may determine, based on access control configuration 1036 and incoming traffic, whether to allow (or prohibit) an access attempt to establish a connection with eDU 1008. As another example, UE 1004 may determine whether to allow an access attempt to establish a connection with eDU 1008 to achieve an access attempt to service X 1012 based on access control configuration and expected service information. In some aspects, this determination may be based on the access identifier and / or access category of the access attempt. As illustrated at 1040, if the UE determines that the access control configuration allows the access attempt, UE 1004 may attempt access by sending one or more messages to eDU 1008. In some aspects, if the access attempt involves a service, additional information may be exchanged with the service via eDU 1008, for example, as illustrated at 1042 for service X 1012. As illustrated at 1048, UE 1002 may determine whether to attempt access (e.g., access to a cell provided by eDU 1006 and / or access to another service X 1012 or service Y 1014) based on the access control configuration received from eDU 1006 at 1046. As an example, UE 1002 can determine that the expected access is prohibited by the access control configuration and can determine not to attempt access.

[0148] Figure 11 Example communication diagram 1100 illustrates access control configurations from a centralized access control service (e.g., 1010), which can be received by the UE in response to a request or query. Figure 11 China and its combination Figure 10 The same aspects described have the same reference numerals. Compared to broadcast access control configurations, in... Figure 11In this process, UE 1004 may send an access control configuration query 1135 (e.g., a request for one or more access control configurations) to access control service 1010 (e.g., via eDU 1008). In response, access control service 1010 sends access control configuration 1044 to UE 1004 (e.g., via eDU 1008). For example, if UE 1004 does not have a valid access control configuration, UE 1004 may obtain access control configuration 1136. In some aspects, if SIB1 indicates access control parameters (e.g., access control configurations) for the UE to download an access control profile, the UE may download the profile from access control service 1010.

[0149] Then, UE 1004 can use access control configuration to determine whether to attempt access, such as in conjunction with Figure 10 As described in section 1038. For example, after receiving the configuration, the UE can use the configuration to determine whether to attempt access. Similarly, UE 1002 can receive access control configuration 1146 from access control service 1010 in response to sending access control configuration query 1145 to access control service 1010 (e.g., via eDU 1006). In some aspects, access control configuration 1136 or 1146 can be received as an access control configuration download. For example, if the UE does not store a valid access control configuration, the UE can obtain the access control configuration from access control service 1010. In some aspects, the AC configuration can be transmitted to the UE via user plane (e.g., in user plane transmission or in user plane messages).

[0150] Figure 12 Example communication diagram 1200 illustrates the distribution of access control configurations from an access control service (e.g., 1206) with a distributed architecture. As shown in 1205, the distributed architecture may include an access control service 1206 co-located with eDU 1204, such as... Figure 9 As described in the example. In some aspects, the eDU may also include a system information service 1207 configured to manage and provide system information.

[0151] As shown at 1216, 1218, and 1222, access control service 1206 may receive service information from one or more services. Services may include eDU 1204. Information may correspond to a combination of... Figure 8BThe inputs described herein. Information from service X 1208 and / or service Y 1210 may include service load status (e.g., load percentage), service priority, associated area, and / or associated timing information. Information from eDU 1204 may include cell load status, radio resource load status, area information, and / or associated timing information for one or more cells. In some aspects, access control service 1206 may provide queries (or requests) for information. Figure 12 The example shows that access control service 1206 provides queries 1212, 1214 and 1220 to various services, and that service information 1216, 1218 and 1222 can be provided to access control service 1206 by various services in response to the corresponding queries (e.g. 1212, 1214 and 1220).

[0152] At 1224, access control service 1206 can generate one or more access control configurations based on the received service information. The access control configurations may correspond to... Figure 8B The output is illustrated in the example. For instance, Access Control Service 1206 can generate one or more access control profiles based on requests from other services and eDU 1204.

[0153] Access control service 1206 may provide access control configuration to eDU 1204, as shown at 1226. The eDU may provide (e.g., send) the received access control configuration to one or more UEs, as shown at 1228. In some aspects, eDU 1204 may broadcast access control configuration 1228, for example, in system information. In some aspects, eDU 1204 may provide access control configuration 1228 in an SIB (such as SIB1). For example, access control configuration may be provided to UE 1202 via system information. For example, if UE 1202 does not have a valid access control configuration, UE 1202 may obtain access control configuration 1228. In some aspects, if SIB1 indicates access control parameters (e.g., access control configuration), the UE may apply the configuration from SIB1 in the corresponding cell.

[0154] UE 1202 derives applicable access control parameters (e.g., prohibition parameters) based on the access control profile indicated in access control configuration 1228, and one or more of UE type, access attempt, service information, current area, and / or current time. As illustrated at 1230, UE 1202 may determine whether to attempt access (e.g., access to a cell provided by eDU 1204 and / or access to a service such as service X 1208 or service Y1210) based on the access control configuration received at 1228. This determination may be referred to as an access control check. As illustrated at 1232, if the UE determines that the access control configuration allows the access attempt, UE 1202 may attempt access by sending one or more messages to eDU 1204. In some aspects, if the access attempt involves a service, additional information may be exchanged with the service via eDU 1204, for example, as illustrated at 1234 for service X 1208. In some respects, UE 1202 can determine at 1230 that the expected access is prohibited by the access control configuration and can determine not to attempt access.

[0155] Figure 13 Example communication diagram 1300 illustrates the distribution of access control configurations from an access control service (e.g., 1206) with a distributed architecture. Figure 13 In this context, UE 1202 can receive access control configuration in response to requests or queries. Figure 13 China and its combination Figure 12 The same aspects described have the same reference numerals. Compared to broadcast access control configurations, in... Figure 12 In this process, UE 1202 may send an access control configuration query 1327 (e.g., a request for one or more access control configurations) to access control service 1206 (e.g., via eDU 1204). In response, access control service 1206 sends access control configuration 1338 to UE 1202 (e.g., via eDU 1204). For example, if UE 1202 does not have a valid access control configuration, UE 1202 may obtain access control configuration 1338. In some aspects, if SIB1 indicates access control parameters (e.g., access control configurations) for the UE to download an access control profile, the UE may download the profile from access control service 1206. UE 1202 can then use the access control configuration to determine whether to attempt access, such as in conjunction with... Figure 12 As described in 1230.

[0156] Figure 14This is a flowchart 1400 of a wireless communication method. This method can be performed by access control services (e.g., access control services 173, 814, 906, 907, 1010, 1206; network entity 2060). Various aspects of this method enable access control configurations that help avoid and / or resolve overload situations at services and / or RAN nodes (e.g., eDUs) in networks with service-based architectures. This method allows for a more global perspective when generating access control configurations.

[0157] At 1402, the access control service obtains (e.g., receives) information for one or more services in a wireless network with a service-based architecture. For example, the access control service may receive auxiliary information from services in the network. Figures 8A to 13 Examples of various services receiving service information from different services are illustrated. One or more services may include one or more network nodes, and the information may include access control information for those network nodes. As an example, Figures 10 to 13 Examples illustrate access control services 814, 906, 907, 1010, or 1206 receiving information from eDUs 802, 803, 902, 903, 1006, 1008, and 1204. In some aspects, this information may include access control auxiliary information from multiple network nodes (e.g., such as...). Figure 8A , Figure 10 or Figure 11 (As shown in the diagram). For example, the access control service can be a centralized access control service, such as combined with... Figure 8A , Figure 10 and Figure 11 As described. In some aspects, access control services can be associated with, for example, a single network node, and can be distributed access control services, such as those combined with... Figure 9 , Figure 12 and Figure 13 As described. In some respects, this acquisition or reception can be performed by, for example, the access control component 191 of network entity 2060.

[0158] In some aspects, information received from a service (e.g., any one of 1020, 1020, 1028, 1030, 1216, 1218, 1222) may include one or more of the following: service load status for one or more services, load percentage for one or more services, service priority for one or more services, network node load status, cell load status, radio resource load status, associated area, or associated time period. In some aspects, the access control service may receive information from one or more services via an API, for example, in combination with... Figure 8A or Figure 9 As described.

[0159] At 1404, the access control service provides access control configuration for one or more cells based on information from one or more services. In some aspects, the one or more cells may be provided by network nodes (e.g., eDUs 802, 803, 90, 903, 1002, 1004, 1202). In some aspects, this provision may be performed by, for example, the access control component 191 of network entity 2060. In some aspects, the access control configuration may include one or more access control profiles generated based on information received for one or more services. In some aspects, the access control configuration may be for a single cell, e.g., cell-specific. In some aspects, the access control configuration may include parameters for multiple cells, as described in conjunction with Table 2.

[0160] In some respects, the access control service may receive updated information from one or more services and provide updated access control configurations for one or more cells based on the updated information.

[0161] In some respects, the access control service can provide service status queries to one or more services, where information is received in response to the service status query. Figures 10 to 13 Examples of queries for information are shown.

[0162] In some respects, the access control service receives requests for access control configurations, which are then provided in response to the requests.

[0163] Figure 15 This is a flowchart 1500 of a wireless communication method. The method can be performed by network nodes (e.g., base stations 102, 410 (or components of base stations, such as one or more of CU 106 or 210, DU 105 or 230, or RU 109 or 240); eDUs 524, 624, 722, 802, 803, 902, 903, 1006, 1008, 1204; network entity 1902). Although the example aspect is described as being performed by an eDU as an example of a network node, the network node can also be referred to as a base station, 6G base station, RAN, RAN node, 6G RAN, network entity, DU, etc. Various aspects of the method enable access control configurations that help avoid and / or resolve overload situations at service and / or RAN nodes (e.g., eDUs) in networks with service-based architectures. The method allows for a more global perspective when generating access control configurations.

[0164] At 1502, the network node provides information to the access control service in the service-based wireless network. In some aspects, the access control configuration is for one or more cells provided by the network node. In some aspects, the access control service is associated with multiple network nodes. In some aspects, the access control service is associated with a single network node and is located at that network node. In some aspects, this provision can be performed by, for example, the access control component 199 of network entity 1902. Figure 8A , Figure 9 , Figure 10 , Figure 11 , Figure 12 and Figure 13 Examples of eDU providing information to the access control service are illustrated. In some aspects, the access control service can be a centralized service, for example, such as... Figure 8A , Figure 10 and Figure 11 As shown in the diagram. In some aspects, the access control service can be a distributed access control service, for example, such as... Figure 9 , Figure 12 and Figure 13 As shown in the image.

[0165] At point 1504, the network node receives access control configuration (e.g., generated by the access control service) from the access control service based at least in part on information and additional information for one or more services of the wireless network. In some aspects, the additional information from one or more services is received at the network node via an API. In some aspects, the information includes one or more of the following: network node load status, cell load status, radio resource load status, associated area, or associated time period. In some aspects, the additional information includes one or more of the following: service load status for one or more services, load percentage for one or more services, service priority for one or more services, area associated with the additional information, or time period associated with the additional information. Figures 10 to 13 An example is shown where the eDU receives access control configuration from the access control service. In some respects, this reception may be performed by, for example, the access control component 199 of network entity 1902.

[0166] At point 1506, the network node provides access control configuration for at least one UE. In some aspects, the network node may send the access control configuration in the SIB. For example, the access control configuration may be broadcast in SIB1. Figure 10 and Figure 12An example of an eDU transmitting access control configuration is illustrated. In some aspects, the network node may receive a service status query from the access control service, wherein information is provided in response to the service status query. In some aspects, the network node is configured to: receive a request for access control configuration from the UE; and provide the request to the access control service, wherein the access control configuration is received in response to the request, and wherein the access control configuration is provided to the UE on the user plane. Figure 11 and Figure 13 An example is illustrated of transmitting access control configuration on the user plane in response to a request from the UE. In some aspects, this provision may be performed by, for example, the access control component 199 of network entity 1902.

[0167] Figure 16 This is a flowchart 1600 of a wireless communication method. This method can be performed by a UE (e.g., UE 104; 450; 724, 804, 805, 904, 905, 1002, 1004, 1202; device 1804). Various aspects of this method enable access control configurations that help avoid and / or resolve overload situations at services and / or RAN nodes (e.g., eDUs) in networks with service-based architectures. This method allows for a more global perspective when generating access control configurations.

[0168] At 1602, the UE receives access control configuration from the access control service in a service-based wireless network. In some aspects, the access control configuration is in a System Information Block (SIB). In some aspects, the UE may send a request for the access control configuration, wherein the access control configuration is received on the user plane in response to the request. In some aspects, the UE may receive system information instructing the UE to download the access control configuration from the access control service before receiving it. This reception may be performed, for example, by the access component 198 of device 1804. Figures 10 to 13 Examples of various scenarios are illustrated whereby a UE receives an access control configuration generated by the access control service. For instance, this reception may be performed via an eDU.

[0169] At 1604, the UE determines whether to access the wireless network service based on at least one of the access control configuration (e.g., from the access control service) and incoming traffic or service information. In some aspects, to determine whether to attempt to access the service based on the access control configuration, the UE may determine a prohibition parameter based on the access control configuration and one or more of the following: UE type, access attempt, service information, current area, access control (AC) profile, or associated time. In some aspects, the UE may attempt to access the network node based on the access control configuration and incoming traffic. In some aspects, the UE may attempt to access the service based on the access control configuration and expected service information. This determination may be performed, for example, by the access component 198 of device 1804. Figures 10 to 13 An example is shown where the UE determines whether to attempt access based on the access control configuration.

[0170] Figure 17 This is a flowchart 1700 of a wireless communication method. This method can be performed by a service (e.g., 175, 516, 612, 614, 713, 714, 716, 713, 812, 816, 912, 914, 916, 1012, 1014, 1208, 1210) or a network entity 2160. Various aspects of this method enable access control configurations that help avoid and / or resolve overload situations at services and / or RAN nodes (e.g., eDUs) in networks with service-based architectures. This method allows for a more global perspective when generating access control configurations.

[0171] At 1702, the service provides information about the service to one or more access control services. In some aspects, the information includes one or more of the following: service load status for the service, load percentage for the service, service priority for one or more services, associated area, or associated time period. In some aspects, the access control service is a centralized access control service associated with multiple network nodes (e.g., for services such as...). Figure 8A , Figure 10 and Figure 11 The centralized architecture shown. In some aspects, providing information includes providing information to multiple access control services, where each access control service is associated with a single network node (e.g., in a network such as...). Figure 9 , Figure 12 and Figure 13 (As shown in the distributed architecture). In some aspects, the service may provide information to a single network node via an API. In other aspects, the service may receive queries from an access control service, in which information is provided to the access control service in response to the queries. This provision may be performed, for example, by the access control component 199 of network entity 2160. Figure 8A and Figures 9 to 13An example is shown where a service provides information to an access control service.

[0172] At 1704, the service receives an attempt to access the User Equipment (UE) service based on the access control configuration of one or more access control services. This reception may be performed, for example, by the access control component 199 of network entity 2160. Figures 10 to 13 An example is shown where the service receives a message from the UE about an access attempt.

[0173] Figure 18Figure 1800 illustrates an example of a hardware implementation of device 1804. Device 1804 may be a UE, a component of a UE, or implement UE functionality. In some aspects, device 1804 may include at least one cellular baseband processor 1824 (also referred to as a modem or processor circuit) coupled to one or more transceivers 1822 (e.g., cellular RF transceivers). Cellular baseband processor 1824 may include at least one on-chip memory 1824' (or memory circuitry). In some aspects, device 1804 may also include one or more Subscriber Identity Module (SIM) cards 1820 and at least one application processor 1806 coupled to a Secure Digital Card (SD) card 1808 and a screen 1810. Application processor 1806 may include on-chip memory 1806'. In some aspects, device 1804 may also include a Bluetooth module 1812, a WLAN module 1814, an SPS module 1816 (e.g., a GNSS module), one or more sensor modules 1818 (e.g., a barometric pressure sensor / altimeter; motion sensors such as an inertial measurement unit (IMU), a gyroscope, and / or an accelerometer; light detection and ranging (LIDAR), radio-assisted detection and ranging (RADAR), sound navigation and ranging (SONAR), a magnetometer, audio, and / or other technologies for positioning), an additional memory module 1826, a power supply 1830, and / or a camera 1832. Bluetooth module 1812, WLAN module 1814, and SPS module 1816 may include an on-chip transceiver (TRX) (or in some cases, only a receiver (RX)). Bluetooth module 1812, WLAN module 1814, and SPS module 1816 may include their own dedicated antennas and / or communicate using antenna 1880. Cellular baseband processor 1824 communicates with UE 104 and / or RU associated with network entity 1802 via transceiver 1822 through one or more antennas 1880. Cellular baseband processor 1824 and application processor 1806 may each include computer-readable media / memory 1824', 1806'. Additional memory module 1826 may also be considered computer-readable media / memory. Each computer-readable media / memory 1824', 1806', 1826 may be non-transitory. Cellular baseband processor 1824 and application processor 1806 are each responsible for general processing, including executing software stored on the computer-readable media / memory. When executed by cellular baseband processor 1824 / application processor 1806, the software causes cellular baseband processor 1824 / application processor 1806 to perform the various functions described above. Cellular baseband processor 1824 and application processor 1806 are configured to perform the various functions described above based at least in part on information stored in memory.In other words, the cellular baseband processor 1824 and application processor 1806 can be configured to perform a first subset of the various functions described above without information stored in memory, and can be configured to perform a second subset of the various functions described above based on information stored in memory. The computer-readable medium / memory can also be used to store data manipulated by the cellular baseband processor 1824 / application processor 1806 during software execution. The cellular baseband processor 1824 / application processor 1806 can be a component of the UE 450 and can include at least one of a memory 460 and / or a TX processor 468, an RX processor 456, and a controller / processor 459. In one configuration, the device 1804 can be at least one processor chip (modem and / or application) and includes only the cellular baseband processor 1824 and / or application processor 1806, while in another configuration, the device 1804 can be the entire UE (e.g., see [link]). Figure 4 The UE 450 includes an additional module of the device 1804.

[0174] As discussed above, access component 198 can be configured to: receive access control configuration from an access control service in a wireless network with a service-based architecture; and determine whether to access the wireless network service based on at least one of the access control configuration and incoming service or service information. The access component and / or UE can be further configured to: attempt to access a network node based on the access control configuration and incoming service; attempt to access a service based on the access control configuration and expected service information; receive system information instructing the UE to download the access control configuration from the access control service before receiving the access control configuration; or determine prohibition parameters based on the access control configuration. Device 1804 can be further configured to perform combination. Figure 16 Any aspect described in the flowchart and / or by Figures 7C to 13Any aspect performed by the UE in either of them. Access component 198 may reside within cellular baseband processor 1824, application processor 1806, or both cellular baseband processor 1824 and application processor 1806. Access component 198 may be one or more hardware components specifically configured to execute the stated process / algorithm, implemented by one or more processors configured to execute the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. When multiple processors are implemented, the multiple processors may execute the stated process / algorithm individually or in combination. As shown, apparatus 1804 may include various components configured for various functions. In one configuration, apparatus 1804 (and specifically cellular baseband processor 1824 and / or application processor 1806) may include: components for receiving access control configuration from an access control service in a wireless network having a service-based architecture; and components for determining whether to access the wireless network service based on at least one of the access control configuration and incoming service or service information. The apparatus 1804 may further include: components for attempting to access a network node based on access control configuration and incoming services; components for attempting to access a service based on access control configuration and expected service information; components for receiving system information instructing the UE to download access control configuration from the access control service before receiving access control configuration; or components for determining prohibition parameters based on access control configuration. The apparatus 1804 may further include components for performing a combination. Figure 16 Any aspect described in the flowchart and / or by Figures 7C to 13 Any component that performs any aspect of the UE in any of the components. The component may be an access component 198 of device 1804 configured to perform the functions described therein. As described above, device 1804 may include a TX processor 468, an RX processor 456, and a controller / processor 459. Therefore, in one configuration, these components may be the TX processor 468, the RX processor 456, and / or the controller / processor 459 configured to perform the functions described therein.

[0175] Figure 19Figure 1900 illustrates an example of a hardware implementation of network entity 1902. Network entity 1902 may be a BS, a component of a BS, or implement BS functionality. Network entity 1902 may include at least one of CU 1910, DU 1930, or RU 1940. For example, depending on the layer functionality handled by access control component 199, network entity 1902 may include CU 1910; both CU 1910 and DU 1930; each of CU 1910, DU 1930, and RU 1940; DU 1930; both DU 1930 and RU 1940; or RU 1940. CU 1910 may include at least one CU processor 1912 (or processor circuitry). CU processor 1912 may include on-chip memory 1912' (or memory circuitry). In some aspects, CU 1910 may also include an additional memory module 1914 and a communication interface 1918. CU 1910 communicates with DU 1930 via a midhaul link (such as an F1 interface). DU 1930 may include at least one DU processor 1932 (or processor circuitry). DU processor 1932 may include on-chip memory 1932' (or memory circuitry). In some aspects, DU 1930 may also include an additional memory module 1934 and a communication interface 1938. DU 1930 communicates with RU 1940 via a fronthaul link. RU 1940 may include at least one RU processor 1942 (or processor circuitry). RU processor 1942 may include on-chip memory 1942' (or memory circuitry). In some aspects, RU 1940 may also include an additional memory module 1944, one or more transceivers 1946, an antenna 1980, and a communication interface 1948. RU 1940 communicates with UE 104. On-chip memories 1912', 1932', 1942' and additional memory modules 1914, 1934, 1944 can each be considered as computer-readable media / memory. Each computer-readable medium / memory can be non-transitory. Each of processors 1912, 1932, 1942 is responsible for general processing, including executing software stored on the computer-readable medium / memory. When executed by the corresponding processor, the software causes that processor to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by the processor when executing the software.

[0176] As discussed above, access control component 199 may be configured to: provide information to an access control service in a wireless network; receive access control configuration from the access control service based at least in part on the information and additional information for one or more services of the wireless network; and provide access control configuration for at least one user equipment (UE). In some aspects, access control component 199 or network entity 1902 may be further configured to receive a service status query from the access control service, wherein information is provided in response to the service status query. In some aspects, access control component 199 or network entity 1902 may be further configured to: receive a request for access control configuration from the UE; and provide the request to the access control service, wherein access control configuration is received in response to the request, and wherein the access control configuration is provided to the UE on the user plane. The network entity may be further configured to perform a combination Figure 15 Any aspect described in the flowchart and / or by Figure 5B , Figure 6 or Figures 7C to 13 The access control component 199 may be any aspect executed by the eDU in any of the following: CU 1910, DU 1930, and RU 1940. The access control component 199 may be one or more hardware components specifically configured to execute the stated process / algorithm, implemented by one or more processors configured to execute the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. When multiple processors are implemented, the multiple processors may execute the stated process / algorithm individually or in combination. The network entity 1902 may include a variety of components configured for various functions. In one configuration, the network entity 1902 may include: components for providing information to an access control service in a wireless network; receiving access control configuration from the access control service based at least in part on the information and additional information for one or more services of the wireless network; and providing access control configuration for at least one UE. In some aspects, the network entity 1902 may also include components for receiving a service status query from the access control service, wherein information is provided in response to the service status query. In some aspects, network entity 1902 may further include components for receiving a request for access control configuration from the UE and components for providing the request to access control services, wherein the access control configuration is received in response to the request, and wherein the access control configuration is provided to the UE on the user plane. The network entity may also include components for performing combination. Figure 15 Any aspect described in the flowchart and / or by Figure 5B , Figure 6 or Figures 7C to 13Any component of the eDU in any of the components. A component may be an access control component 199 of network entity 1902 configured to perform the functions described therein. As described above, network entity 1902 may include a TX processor 416, an RX processor 470, and a controller / processor 475. Therefore, in one configuration, these components may be the TX processor 416, the RX processor 470, and / or the controller / processor 475 configured to perform the functions described therein.

[0177] Figure 20 Figure 2000 illustrates an example of a hardware implementation of network entity 2060. In some aspects, network entity 2060 may be an access control service (e.g., as combined with...). Figures 8A to 13 (As described in any of the above). In one example, network entity 2060 may be within core network 190. Network entity 2060 may include at least one network processor 2012 (or processor circuitry). Network processor 2012 may include on-chip memory 2012' (or memory circuitry). In some aspects, network entity 2060 may also include additional memory module 2014. Network entity 2060 communicates with CU 2002 directly (e.g., via a backhaul link) or indirectly (e.g., via RIC) through network interface 2080. On-chip memory 2012' and additional memory module 2014 may each be considered as computer-readable media / memory. Each computer-readable media / memory may be non-transitory. Network processor 2012 is responsible for general processing, including executing software stored on the computer-readable media / memory. The software, when executed by the corresponding processor, causes the processor to perform the various functions described above. The computer-readable media / memory may also be used to store data manipulated by the processor when executing the software.

[0178] As discussed above, access control component 191 can be configured to: obtain information from an access control service for one or more services in a wireless network with a service-based architecture; and provide access control configuration for one or more cells based on the information from the one or more services. In some aspects, access control component 191 or network entity 2060 can be further configured to: receive updated information from one or more services; and provide updated access control configuration for one or more cells based on the updated information. In some aspects, access control component 191 or network entity 2060 can be further configured to: provide service status queries to one or more services, wherein information is received in response to the service status query. In some aspects, access control component 191 or network entity 2060 can be further configured to receive requests for access control configuration, wherein access control configuration is provided in response to the requests. Access control component 191 may be within network processor 2012. In some aspects, access control component 191 or network entity 2060 may be further configured to perform coupling. Figure 14 Any aspect described in the flowchart and / or by Figures 8A to 13 Access control service in any of them or by Figure 5B , Figure 6 , Figure 7B or Figure 7C The access control component 191 may be one or more hardware components specifically configured to execute the stated process / algorithm, implemented by one or more processors configured to execute the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. When multiple processors are implemented, the multiple processors may execute the stated process / algorithm individually or in combination. The network entity 2060 may include a variety of components configured for various functions. In one configuration, the network entity 2060 may include: components for obtaining information at the access control service for one or more services in a wireless network having a service-based architecture; and components for providing access control configuration for one or more cells based on the information from one or more services. In some aspects, the network entity 2060 may also include: components for receiving updated information from one or more services; and components for providing updated access control configuration for one or more cells based on the updated information. In some aspects, the network entity 2060 may also include components for providing service status queries to one or more services, wherein information is received in response to the service status query. In some aspects, network entity 2060 may also include components for receiving requests for access control configuration, wherein the access control configuration is provided in response to the request. In some aspects, access control component 191 or network entity 2060 may also include components for performing combination. Figure 14Any aspect described in the flowchart and / or by Figures 8A to 13 Access control service in any of them or by Figure 5B , Figure 6 , Figure 7B or Figure 7C Any component that performs the services within the network entity 2060. A component may be an access control component 191 of the network entity 2060 configured to perform the functions described in the component.

[0179] Figure 21 Figure 2100 illustrates an example of a hardware implementation of network entity 2160. In some aspects, network entity 2160 may be a service in a service-based network architecture. In one example, network entity 2160 may be within core network 190. Network entity 2160 may include at least one network processor 2112 (or processor circuitry). Network processor 2112 may include on-chip memory 2112' (or memory circuitry). In some aspects, network entity 2160 may also include an additional memory module 2114. Network entity 2160 communicates with CU 2102 directly (e.g., via a backhaul link) or indirectly (e.g., via RIC) through network interface 2180. On-chip memory 2112' and additional memory module 2114 may each be considered as computer-readable media / memory. Each computer-readable media / memory may be non-transitory. Network processor 2112 is responsible for general processing, including executing software stored on the computer-readable media / memory. This software, when executed by the corresponding processor, causes the processor to perform the various functions described above. Computer-readable media / storage can also be used to store data manipulated by the processor while executing software.

[0180] As discussed above, access control component 199 can be configured to: provide service-specific information to one or more access control services; and receive attempts to access services for a UE based on access control configurations from one or more access control services. Access control component 199 may be located within network processor 2112. Access control component 199 may be one or more hardware components specifically configured to execute the stated process / algorithm, implemented by one or more processors configured to execute the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. When multiple processors are implemented, the multiple processors may execute the stated process / algorithm individually or in combination. Network entity 2160 may include various components configured for various functions. In one configuration, network entity 2160 may include: a component for providing service-specific information to one or more access control services; and a component for receiving attempts to access services for a user equipment (UE) based on access control configurations from one or more access control services. The component may be access control component 199 of network entity 2160 configured to perform the functions described by the component.

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

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

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

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

[0185] Aspect 1 is a method performed at an access control service for wireless communication, the method comprising: obtaining information at the access control service for one or more services in a wireless network having a service-based architecture; and providing access control configuration for one or more cells based on the information from the one or more services.

[0186] Aspect 2 is the method according to aspect 1, wherein the access control configuration includes one or more access control profiles generated based on the information received for the one or more services.

[0187] Aspect 3 is the method according to aspect 1 or 2, wherein the one or more services include one or more network nodes, and the information includes access control assistance information.

[0188] Aspect 4 is the method according to any one of Aspects 1 to 3, wherein the information includes the access control assistance information from a plurality of network nodes.

[0189] Aspect 5 is the method according to any one of Aspects 1 to 3, wherein the access control service is associated with a single network node.

[0190] Aspect 6 is the method according to aspect 5, wherein the access control service is located at the single network node.

[0191] Aspect 7 is the method according to any one of Aspects 1 to 6, wherein the access control configuration is for multiple cells provided by a network node.

[0192] Aspect 8 is a method according to any one of Aspects 1 to 7, wherein the information includes one or more of the following: service load status for the one or more services, load percentage for the one or more services, service priority for the one or more services, network node load status, cell load status, radio resource load status, associated area or associated time period.

[0193] Aspect 9 is the method according to any one of aspects 1 to 7, wherein the information includes: service load status for the one or more services.

[0194] Aspect 10 is the method according to any one of aspects 1 to 7, wherein the information includes: load percentage for the one or more services.

[0195] Aspect 11 is the method according to any one of aspects 1 to 7, wherein the information includes: service priority for the one or more services.

[0196] Aspect 12 is the method according to any one of aspects 1 to 7, wherein the information includes: network node load status.

[0197] Aspect 13 is the method according to any one of aspects 1 to 7, wherein the information includes: cell load status.

[0198] Aspect 14 is the method according to any one of aspects 1 to 7, wherein the information includes: radio resource load status.

[0199] Aspect 15 is the method according to any one of aspects 1 to 7, wherein the information includes: associated region.

[0200] Aspect 16 is the method according to any one of aspects 1 to 7, wherein the information includes: an associated time period.

[0201] Aspect 17 is the method according to any one of aspects 1 to 16, wherein the access control service receives the information from the one or more services via an application programming interface (API).

[0202] Aspect 18 is a method according to any one of aspects 1 to 17, the method further comprising: receiving updated information from the one or more services; and providing an updated access control configuration for the one or more cells based on the updated information.

[0203] Aspect 19 is a method according to any one of aspects 1 to 18, the method further comprising: providing a service status query to the one or more services, wherein information is received in response to the service status query.

[0204] Aspect 20 is a method according to any one of aspects 1 to 18, the method further comprising receiving a request for the access control configuration, wherein the access control configuration is provided in response to the request.

[0205] Aspect 21 is a method for wireless communication at a network node, the method comprising: providing information to an access control service in a wireless network; receiving an access control configuration from the access control service based at least in part on the information and additional information for one or more services of the wireless network; and providing the access control configuration for at least one user equipment (UE).

[0206] Aspect 22 is the method according to aspect 21, wherein the access control configuration is for one or more cells provided by the network node.

[0207] Aspect 23 is the method according to aspect 21 or 22, wherein the access control service is associated with multiple network nodes.

[0208] Aspect 24 is the method according to aspect 21 or 22, wherein the access control service is associated with and located at a single network node.

[0209] Aspect 25 is the method according to any one of aspects 21 to 24, wherein the additional information from the one or more services is received at the network node via an application programming interface (API).

[0210] Aspect 26 is the method according to any one of aspects 21 to 25, wherein the information includes one or more of the following: network node load status, cell load status, radio resource load status, associated area or associated time period.

[0211] Aspect 27 is the method according to any one of aspects 21 to 25, wherein the information includes network node load status.

[0212] Aspect 28 is the method according to any one of aspects 21 to 25, wherein the information includes cell load status.

[0213] Aspect 29 is the method according to any one of aspects 21 to 25, wherein the information includes radio resource load status.

[0214] Aspect 30 is the method according to any one of aspects 21 to 25, wherein the information includes associated regions.

[0215] Aspect 31 is the method according to any one of aspects 21 to 25, wherein the information includes an associated time period.

[0216] Aspect 32 is the method according to any one of aspects 21 to 31, wherein the additional information includes one or more of the following: service load status for the one or more services, load percentage for the one or more services, service priority for the one or more services, region associated with the additional information, or time period associated with the additional information.

[0217] Aspect 33 is the method according to any one of aspects 21 to 31, wherein the additional information includes service load status for the one or more services.

[0218] Aspect 34 is the method according to any one of aspects 21 to 31, wherein the additional information includes a load percentage for the one or more services.

[0219] Aspect 35 is the method according to any one of aspects 21 to 31, wherein the additional information includes service priority for the one or more services.

[0220] Aspect 36 is the method according to any one of aspects 21 to 31, wherein the additional information includes a region associated with the additional information.

[0221] Aspect 37 is the method according to any one of aspects 21 to 31, wherein the additional information includes a time period associated with the additional information.

[0222] Aspect 38 is a method according to any one of aspects 21 to 37, in which the access control configuration is provided to at least one UE, comprising: transmitting the access control configuration in a system information block (SIB).

[0223] Aspect 39 is a method according to any one of aspects 21 to 38, the method further comprising: receiving a service status query from the access control service, wherein the information is provided in response to the service status query.

[0224] Aspect 40 is a method according to any one of aspects 21 to 37 or 39, the method further comprising providing a request from the UE to the access control service for the access control configuration, wherein the access control configuration is received in response to the request, and wherein the access control configuration is provided to the UE on the user plane.

[0225] Aspect 41 is a method for wireless communication at a user equipment (UE), the method comprising: receiving an access control configuration from an access control service in a wireless network having a service-based architecture; and determining, based on at least one of the access control configuration and incoming service information, whether to access the service of the wireless network.

[0226] Aspect 42 is the method according to aspect 41, the method further comprising attempting to access a network node based on the access control configuration and the incoming service.

[0227] Aspect 43 is the method according to aspect 41, the method further comprising attempting to access the service based on the access control configuration and the service information.

[0228] Aspect 44 is the method according to any one of aspects 41 to 43, wherein the access control is configured in the system information block (SIB).

[0229] Aspect 45 is a method according to any one of aspects 41 to 43, the method further comprising sending a request for the access control configuration, wherein the access control configuration is received on the user plane in response to the request.

[0230] Aspect 46 is the method according to aspect 45, the method further comprising receiving system information instructing the UE to download the access control configuration from the access control service before receiving the access control configuration.

[0231] Aspect 47 is a method according to any one of Aspects 41 to 46, wherein attempting to access the service based on the access control configuration includes determining a prohibition parameter based on the access control configuration and one or more of the following: UE type, access attempt, service information, current region, access control (AC) profile, or associated time.

[0232] Aspect 48 is a method according to any one of aspects 41 to 46, wherein attempting to access the service based on the access control configuration includes determining a prohibition parameter based on the access control configuration and the UE type.

[0233] Aspect 49 is a method according to any one of aspects 41 to 46, wherein attempting to access the service based on the access control configuration includes determining a prohibition parameter based on the access control configuration and the access attempt.

[0234] Aspect 50 is the method according to any one of aspects 41 to 46, wherein attempting to access the service based on the access control configuration includes determining a prohibition parameter based on the access control configuration and service information.

[0235] Aspect 51 is the method according to any one of aspects 41 to 46, wherein attempting to access the service based on the access control configuration includes determining a blocking parameter based on the access control configuration and the current region.

[0236] Aspect 52 is the method according to any one of aspects 41 to 46, wherein attempting to access the service based on the access control configuration includes determining a prohibition parameter based on the access control configuration and the access control (AC) profile.

[0237] Aspect 53 is the method according to any one of aspects 41 to 46, wherein attempting to access the service based on the access control configuration includes determining a prohibition parameter based on the access control configuration and an associated time.

[0238] Aspect 54 is a method for a service associated with a wireless network, the method comprising: providing information for the service to one or more access control services; and receiving an attempt for a user equipment (UE) to access the service based on an access control configuration from one or more access control services.

[0239] Aspect 55 is the method according to aspect 54, wherein the information includes one or more of the following: service load status for the service, load percentage for the service, service priority for the one or more services, associated region or associated time period.

[0240] Aspect 56 is the method according to any one of aspects 54 to 55, wherein the information includes the service load status for the service.

[0241] Aspect 57 is the method according to any one of aspects 54 to 56, wherein the information includes a load percentage for the service.

[0242] Aspect 58 is the method according to any one of aspects 54 to 57, wherein the information includes service priorities for the one or more services.

[0243] Aspect 59 is the method according to any one of aspects 54 to 58, wherein the information includes associated regions.

[0244] Aspect 60 is the method according to any one of aspects 54 to 59, wherein the information includes an associated time period.

[0245] Aspect 61 is the method according to any one of aspects 54 to 60, wherein the access control service is a centralized access control service associated with multiple network nodes.

[0246] Aspect 62 is a method according to any one of aspects 54 to 60, wherein providing the information includes providing the information to a plurality of access control services, wherein each access control service is associated with a single network node.

[0247] Aspect 63 is the method according to any one of aspects 54 to 62, wherein providing the information includes providing the information to the individual network node via an application programming interface (API).

[0248] Aspect 64 is a method according to any one of aspects 54 to 61, the method further comprising: receiving a query from the access control service, wherein the information is provided to the access control service in response to the query.

[0249] Aspect 65 is an apparatus for wireless communication at an access control service, the apparatus comprising: one or more memories; and one or more processors coupled to the one or more memories and configured to cause the access control service to perform the method according to any one of aspects 1 to 20.

[0250] Aspect 66 is an apparatus for wireless communication at an access control service, the apparatus comprising: one or more memories; and one or more processors coupled to the one or more memories and configured individually or in any combination to cause the access control service to perform the method according to any one of aspects 1 to 20.

[0251] Aspect 67 is an apparatus for wireless communication at an access control service, the apparatus comprising components for performing each step of the method according to any one of aspects 1 to 20.

[0252] Aspect 68 is an access control service comprising: a processing system including processor circuitry and memory circuitry storing code and coupled to the processor circuitry, the processing system being configured to cause the access control service to: perform the method according to any one of aspects 1 to 20.

[0253] Aspect 69 is an apparatus according to any one of aspects 65 to 68, the apparatus further comprising one or more antennas configured to receive or transmit in association with the method according to any one of aspects 1 to 20.

[0254] Aspect 70 is a computer-readable storage medium (e.g., a non-transitory computer-readable storage medium) that stores computer-executable code at an access control service, the code causing the access control service to perform the method according to any one of aspects 1 to 20 when executed by one or more processors.

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

[0256] Aspect 72 is an apparatus for wireless communication at a network node, the apparatus comprising: one or more memories; and one or more processors coupled to the one or more memories and configured individually or in any combination to cause the network node to perform the method according to any one of aspects 21 to 40.

[0257] Aspect 73 is an apparatus for wireless communication at a network node, the apparatus comprising components for performing each step of the method according to any one of aspects 21 to 40.

[0258] Aspect 74 is a network node comprising: a processing system including processor circuitry and memory circuitry storing code and coupled to the processor circuitry, the processing system being configured to cause the network node to perform a method according to any one of aspects 21 to 40.

[0259] Aspect 75 is an apparatus according to any one of aspects 71 to 74, the apparatus further comprising one or more antennas configured to receive or transmit in association with the method according to any one of aspects 21 to 40.

[0260] Aspect 76 is a computer-readable storage medium (e.g., a non-transitory computer-readable storage medium) that stores computer-executable code at a network node, the code causing the network node to perform the method according to any one of aspects 21 to 40 when executed by one or more processors.

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

[0262] Aspect 78 is an apparatus for wireless communication at a UE, the apparatus comprising: one or more memories; and one or more processors coupled to the one or more memories and configured individually or in any combination to cause the UE to perform the method according to any one of aspects 41 to 53.

[0263] Aspect 79 is an apparatus for wireless communication at a UE, the apparatus comprising components for performing each step of the method according to any one of aspects 41 to 53.

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

[0265] Aspect 81 is an apparatus according to any one of aspects 77 to 80, the apparatus further comprising one or more antennas configured to receive or transmit in association with the method according to any one of aspects 41 to 53.

[0266] Aspect 82 is a computer-readable storage medium (e.g., a non-transitory computer-readable storage medium) that stores computer-executable code at a UE, the code causing the UE to perform a method according to any one of aspects 41 to 53 when executed by one or more processors.

[0267] Aspect 83 is an apparatus for a wireless communication service, the apparatus comprising: one or more memories; and one or more processors coupled to the one or more memories and configured to cause the service to perform a method according to any one of aspects 54 to 64.

[0268] Aspect 84 is an apparatus for a wireless communication service, the apparatus comprising: one or more memories; and one or more processors coupled to the one or more memories and configured individually or in any combination to cause the service to perform the method according to any one of aspects 54 to 64.

[0269] Aspect 85 is an apparatus for a wireless communication service, the apparatus comprising components for performing each step of the method according to any one of aspects 54 to 64.

[0270] Aspect 86 is a service for wireless communication, the service comprising: a processing system including processor circuitry and memory circuitry storing code and coupled to the processor circuitry, the processing system being configured to cause the service to perform a method according to any one of aspects 54 to 64.

[0271] Aspect 87 is a computer-readable storage medium (e.g., a non-transitory computer-readable storage medium) that stores computer-executable code at a service for wireless communication, the code causing the service to perform a method according to any one of aspects 54 to 64 when executed by one or more processors.

Claims

1. An apparatus for access control services in wireless communication, the apparatus comprising: One or more memory units; and One or more processors, said one or more processors coupled to said one or more memories, said one or more processors being configured to enable the access control service: Information for one or more services in a wireless network with a service-based architecture is obtained from the access control service. as well as Access control configuration for one or more cells is provided based on the information from the one or more services.

2. The apparatus of claim 1, wherein the access control configuration includes one or more access control profiles generated based on the information received for the one or more services.

3. The apparatus of claim 1, wherein the one or more services include one or more network nodes, and the information includes access control assistance information.

4. The apparatus of claim 3, wherein the information includes the access control assistance information from a plurality of network nodes.

5. The apparatus of claim 3, wherein the access control service is associated with a single network node.

6. The apparatus of claim 5, wherein the access control service is located at the single network node.

7. The apparatus of claim 1, wherein the access control configuration is for multiple cells provided by a network node.

8. The apparatus of claim 1, wherein the information includes one or more of the following: Regarding the service load status of the one or more services. Regarding the load percentage of the one or more services, Service priority for the one or more services Network node load status Cell load status Radio resource load status, Related areas, or Related time period.

9. The apparatus of claim 1, wherein the one or more processors are configured to cause the access control service to receive the information from the one or more services via an application programming interface (API).

10. The apparatus of claim 1, wherein the one or more processors are further configured to enable the access control service: A service status query is provided to the one or more services, wherein the information is received in response to the service status query; or A request for the access control configuration is received, wherein the access control configuration is provided in response to the request.

11. An apparatus for wireless communication at a network node, the apparatus comprising: One or more memory units; and One or more processors, said one or more processors coupled to said one or more memories, said one or more processors being configured to cause the network node to: Provide information to the access control service in the wireless network; Access control configuration is received from the access control service based at least in part on the information and additional information for one or more services of the wireless network; as well as Provide the access control configuration for at least one user equipment (UE).

12. The apparatus of claim 11, wherein the access control configuration is for one or more cells provided by the network node.

13. The apparatus of claim 11, wherein the access control service is associated with a plurality of network nodes or with a single network node and is located at the network node.

14. The apparatus of claim 11, wherein the information includes one or more of the following: Network node load status Cell load status Radio resource load status, Related areas, or Related time periods, and The additional information mentioned therein includes one or more of the following: Regarding the service load status of the one or more services. Regarding the load percentage of the one or more services, Service priority for the one or more services The area associated with the additional information, or The time period associated with the additional information.

15. The apparatus of claim 11, further comprising one or more antennas coupled to the one or more processors, wherein the one or more processors are further configured to cause the network node to: Receive a service status query from the access control service, wherein the information is provided in response to the service status query; or The UE provides a request for the access control configuration to the access control service, wherein the access control configuration is received in response to the request, and wherein the access control configuration is provided to the UE on the user plane.

16. An apparatus for conducting wireless communication at a user equipment (UE), the apparatus comprising: One or more memory units; and One or more processors, said one or more processors coupled to said one or more memories, said one or more processors being configured to cause the UE to: Receive access control configuration from the access control service in a service-based wireless network; as well as Whether to access the wireless network service is determined based on at least one of the access control configuration and the incoming service or service information.

17. The apparatus of claim 16, wherein the one or more processors are configured to cause the UE to: Attempt to access the network node based on the access control configuration and the incoming service; or Attempt to access the service based on the access control configuration and the service information.

18. The apparatus of claim 16, wherein the access control is configured in a System Information Block (SIB).

19. The apparatus of claim 16, further comprising one or more antennas coupled to the one or more processors, wherein the one or more processors are further configured to cause the UE to: Send a request for the access control configuration, wherein the access control configuration is received on the user plane in response to the request; and Before receiving the access control configuration, the system information instructing the UE to download the access control configuration from the access control service is received.

20. The apparatus of claim 16, wherein, in order to attempt to access the service based on the access control configuration, the one or more processors are configured to cause the UE to determine a blocking parameter based on the access control configuration and one or more of the following: UE type, Access attempt Service information Current area, Access Control (AC) configuration file, or Related time.

Images