Apparatus and method for new radio broadcast and multicast access control

Abstract

The present disclosure relates to techniques for providing access control for multicast or broadcast (MC / BC) services. A base station broadcasts one or more cell barring parameters to a group of user equipments (UEs), the one or more cell barring parameters indicating whether UEs in the group of UEs are allowed to select a cell of the base station for receiving MC / BC services. The base station also broadcasts one or more access control parameters to a set of one or more UEs in the group of UEs that are indicated to be allowed to select a cell for receiving MC / BC services based on the one or more cell barring parameters. The one or more access control parameters indicate whether the set of one or more UEs are allowed to establish or resume a RRC connected state with the base station to receive the MC / BC services.

Description

[0001] Cross-reference to related applications

[0002] This patent application claims priority and benefit to Pending Non-Provisional Application No. 17 / 357,832, filed with the U.S. Patent and Trademark Office on June 24, 2021, and Provisional Application No. 63 / 044,339, filed with the U.S. Patent and Trademark Office on June 25, 2020, each of which is assigned to the assignee of this application and is expressly incorporated herein by reference as if its entire contents were fully set forth below and for all applicable purposes. Technical Field

[0003] In summary, this disclosure relates to wireless communication systems, and more specifically, to providing access control for receiving multicast or broadcast services. Background Technology

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, and broadcasting. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth-generation (4G) systems (e.g., Long Term Evolution (LTE) systems, improved LTE (LTE-A) systems, or LTE-A Pro systems) and fifth-generation (5G) systems (which may be referred to as New Radio (NR) systems). These systems may employ technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), or Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). Wireless multiple access communication systems may include multiple base stations or network access nodes, each supporting communication with multiple communication devices (which may also be referred to as User Equipment (UE)) simultaneously.

[0005] In some aspects, a user equipment (UE) can camp on a base station or cell by selecting (e.g., via a control channel) the cell to which it wants to receive system information. In some wireless communication systems (such as fifth-generation (5G) New Radio (NR) wireless networks), a UE may seek to receive one or more unicast services or one or more multicast or broadcast services (hereinafter collectively referred to as "multicast broadcast services"). A unicast transmission is a transmission from a single point in the network (e.g., a base station) to another single point in the network (e.g., a UE). Conversely, a multicast or broadcast transmission (hereinafter collectively referred to as "multicast broadcast transmission") is a point-to-multipoint transmission, such as from a base station to a group of UEs within a cell of the base station. A base station can provide unicast services to individual UEs via independent unicast transmissions to multiple UEs, and multicast broadcast services to a group of UEs via multicast broadcast transmissions to a group of UEs. In some scenarios, such as when the number of UEs in an RRC connection state with a cell of a base station exceeds a threshold number, the base station may be overloaded. Summary of the Invention

[0006] To provide a basic understanding of one or more aspects of this disclosure, a brief overview of those aspects is given below. This overview is not an exhaustive summary of all the intended features of this disclosure, and is neither intended to identify key or essential elements of all aspects of this disclosure, nor to depict the scope of any or all aspects of this disclosure. Its sole purpose is to present some concepts of one or more aspects of this disclosure in a simplified form as a prelude to the more detailed description given later.

[0007] A method for wireless communication by a base station is provided. The method includes: broadcasting one or more cell prohibition parameters to a group of user equipments (UEs), the one or more cell prohibition parameters indicating whether a UE in the group of UEs is permitted to select a cell of the base station for receiving multicast or broadcast services. The method further includes: broadcasting one or more access control parameters to a set of one or more UEs in the group of UEs that are indicated as permitted to select a cell for receiving the multicast or broadcast services based on the one or more cell prohibition parameters. The one or more access control parameters indicate whether the set of one or more UEs is permitted to establish or restore a Radio Resource Control (RRC) connection state with the base station to receive the multicast or broadcast services.

[0008] A base station is provided. The base station includes a transceiver for wirelessly communicating with a user equipment (UE). The base station also includes one or more processors electronically coupled to the transceiver. The one or more processors are configured to broadcast one or more cell prohibition parameters to a group of UEs, the one or more cell prohibition parameters indicating whether the UEs are permitted to select a cell of the base station for receiving multicast or broadcast services. The one or more processors are further configured to broadcast one or more access control parameters to a set of one or more UEs in the group of UEs that are indicated as permitted to select a cell for receiving the multicast or broadcast services based on the one or more cell prohibition parameters. The one or more access control parameters indicate whether the set of one or more UEs is permitted to establish or restore a Radio Resource Control (RRC) connection state with the base station to receive the multicast or broadcast services.

[0009] A method is provided for wireless communication by a user equipment (UE). The method includes: receiving one or more cell prohibition parameters from a base station, the one or more cell prohibition parameters indicating whether the UE is permitted to select a cell of the base station for receiving multicast or broadcast services. The method further includes: receiving one or more access control parameters from the base station based on the one or more cell prohibition parameters indicating that the UE is permitted to select a cell of the base station for receiving multicast or broadcast services, the one or more access control parameters indicating whether the UE is permitted to establish or restore a Radio Resource Control (RRC) connection state with the base station to receive the multicast or broadcast services. The method further includes: sending an access request message based on the one or more access control parameters to establish or restore the RRC connection state with the base station to receive the multicast or broadcast services.

[0010] A user equipment (UE) is provided. The UE includes a transceiver for wirelessly communicating with a base station. The UE also includes one or more processors electrically coupled to the transceiver. The one or more processors are configured to receive one or more cell prohibition parameters from the base station, the one or more cell prohibition parameters indicating whether the UE is permitted to select a cell of the base station for receiving multicast or broadcast services. The one or more processors are further configured to receive one or more access control parameters from the base station based on the one or more cell prohibition parameters indicating that the UE is permitted to select a cell of the base station for receiving the multicast or broadcast services, the one or more access control parameters indicating whether the UE is permitted to establish or restore a Radio Resource Control (RRC) connection state with the base station to receive the multicast or broadcast services. The one or more processors are further configured to send an access request message based on the one or more access control parameters to establish or restore the RRC connection state with the base station to receive the multicast or broadcast services.

[0011] These and other aspects of this disclosure will become more fully understood after reading the following detailed description. Other aspects, features, and embodiments of this disclosure will become apparent to those skilled in the art after reading the following description of specific exemplary embodiments of this disclosure in conjunction with the accompanying drawings. While features of this disclosure may be discussed below with respect to certain embodiments and drawings, all embodiments of this disclosure may include one or more of the advantageous features discussed herein. In other words, while one or more embodiments may be discussed as having certain advantageous features, one or more such features may also be used according to the various embodiments of the disclosure discussed herein. Similarly, while exemplary embodiments may be discussed below as device, system, or method embodiments, it should be understood that such exemplary embodiments may be implemented in various devices, systems, and methods. Attached Figure Description

[0012] Figure 1 This is a schematic diagram of an example wireless communication system.

[0013] Figure 2 This is a conceptual diagram of an example wireless access network.

[0014] Figure 3 This is a conceptual diagram of an example wireless communication system for controlling New Radio (NR) multicast and broadcast access, based on some aspects of this disclosure.

[0015] Figure 4 This is a table illustrating an example mapping of access identity values ​​to prohibition parameters for controlling multicast and broadcast access, according to some aspects of this disclosure.

[0016] Figure 5 This is a table illustrating an example mapping of access category values ​​to prohibition parameters for controlling multicast and broadcast access, according to some aspects of this disclosure.

[0017] Figure 6 This is a block diagram conceptually illustrating an example hardware implementation for a base station based on some aspects of this disclosure.

[0018] Figure 7 This is a flowchart illustrating an example method for controlling multicast and broadcast access performed at a base station according to some aspects of this disclosure.

[0019] Figure 8 This is a conceptual diagram illustrating an example hardware implementation of an example user equipment (UE) according to some aspects of this disclosure.

[0020] Figure 9 This is a flowchart illustrating an example method for controlling multicast and broadcast access performed at a UE according to some aspects of this disclosure.

[0021] Figure 10 This is an example conceptual diagram illustrating an example 5G multicast broadcast system architecture based on some aspects of this disclosure. Detailed Implementation

[0022] The detailed descriptions illustrated herein, taken in conjunction with the accompanying drawings, are intended as descriptions of various configurations and not as representations of the only configurations in which the concepts described herein can be practiced. For the purpose of providing a comprehensive understanding of the various concepts, the detailed descriptions include specific details. However, it will be apparent to those skilled in the art that 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 such concepts.

[0023] In some wireless communication systems (such as fifth-generation (5G) New Radio (NR) wireless networks), one or more wireless devices may seek to receive one or more unicast services or one or more multicast or broadcast services (hereinafter collectively referred to as "multicast broadcast services"). A unicast transmission is a transmission from a single point in the network (e.g., a base station) to another single point in the network (e.g., a user equipment (UE)). Conversely, a multicast or broadcast transmission (hereinafter collectively referred to as "multicast broadcast transmission") is a point-to-multipoint transmission, such as from a base station to a group of UEs within a cell of the base station. A base station may provide unicast services to individual UEs via individual unicast transmissions to multiple UEs, and multicast broadcast services to a group of UEs via multicast broadcast transmissions to a group of UEs.

[0024] In 3GPP version 17 systems, a UE can receive NR multicast services while in an idle or inactive state (e.g., RRC_IDLE or RRC_INACTIVE state). Additionally, a UE can receive NR multicast services while in a connected state (e.g., RRC_CONNECTED state). However, when a UE is in an idle or inactive state, it may not be able to provide feedback to the network (e.g., the base station). Conversely, when a UE is in a connected state, it may be able to provide L1 / L2 feedback to the network for any multicast services received from the network or the base station. Therefore, increasing the number of UEs in a connected state when a UE is receiving multicast services may be advantageous, as the network can improve the reliability of the multicast service based on the feedback. For example, using feedback from UEs in a connected state, the base station can retransmit multicast services for higher reliability. However, too many UEs operating in RRC connected state to receive multicast services may cause overload at the base station. Accordingly, the base station can implement access overload control (or simply "access control") to limit the number of UEs allowed to enter the RRC connection state for the purpose of receiving multicast services.

[0025] Various aspects of this disclosure relate to controlling access used by a UE to receive multicast services. According to some aspects, a base station broadcasts one or more cell prohibition parameters to a group of UEs to notify them whether the base station is configured to provide multicast services. In some aspects, the base station broadcasts one or more cell prohibition parameters to restrict a UE from camping on a cell to receive multicast services, thereby preventing or mitigating congestion at the base station. A UE receiving the broadcast cell prohibition parameters may camp on a cell to receive multicast services based on the cell prohibition parameters allowing the UE to camp on the base station's cell. In some aspects, the base station may also configure one or more access control parameters for a UE to provide access to one or more multicast services for an individual UE or a group of UEs. Access control parameters may be associated with at least one of the following: one or more specific multicast services, one or more prohibition factors, or one or more prohibition times. One or more access control parameters may notify the UE whether it is permitted to establish or restore an RRC connection state with the base station. Using access control parameters, the UE can identify whether and when to send an access request message to the base station to establish or restore an RRC connection state with the base station.

[0026] For example, when one or more access control parameters are associated with a first multicast service but not with a second (e.g., a different) multicast service, the UE can send an access request message when seeking to receive the first multicast service, and can refrain from sending the access request message when seeking to receive the second multicast service (and not the first). This allows the base station to limit the number of UEs camped on the cell in RRC connected state to only UEs seeking to use one or more specific multicast services, reducing / limiting overhead and / or data throughput. As another example, the base station can set one or more cell prohibition factors (e.g., values) to control the probability that a random number generated by the UE is not less than or greater than one or more cell prohibition factors. When a random number generated by the UE is not less than or greater than the cell prohibition factor, the UE can be allowed to send an access request message for entering the RRC connected state. Increasing the cell prohibition factor increases the probability that the UE will be delayed in transitioning to the RRC connected state, and decreasing the cell prohibition factor decreases the probability that the UE will be delayed in transitioning to the RRC connected state. As yet another example, the base station can set one or more cell prohibition times to control the frequency at which the UE generates random numbers for comparison with one or more cell prohibition factors. Increasing the cell prohibition time reduces the frequency at which a UE must generate random numbers for comparison with one or more cell prohibition factors, while decreasing the cell prohibition time increases the frequency at which a UE must generate random numbers for comparison with one or more cell prohibition factors. The base station can configure one or more cell prohibition factors and one or more cell prohibition times to maintain or limit the number of UEs that can camp on the base station to receive one or more multicast services (e.g., maintain or limit them below a threshold), and / or maintain or limit the data rate at which data is transmitted through the base station (e.g., maintain or limit it below a threshold). Controlling the number of UEs and / or the data rate by the base station allows the base station to increase feedback to improve the reliability or quality of multicast services and can also prevent or reduce overload conditions.

[0027] Specific aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. In some examples, the described techniques can be used to monitor or improve the reliability of providing multicast services via feedback from a group of UEs, while maintaining service quality and reducing congestion. For example, by delaying the sending of access request messages by UEs seeking multicast services to the base station providing the multicast service, the base station can increase feedback to improve the reliability or quality of the multicast service while preventing overload conditions. As another example, by configuring a prohibition factor and a prohibition time, the base station may be able to control the likelihood that a UE can send an access request message to the base station. Delaying the sending of access request messages by UEs can also allow one or more other UEs sufficient time to transition from an RRC connected state to an RRC idle state or an RRC inactive state (and consequently, allow the UE to enter the RRC connected state). In this way, the base station can maintain the number of UEs in the RRC connected state below a threshold number.

[0028] While aspects and embodiments are described herein by way of example, those skilled in the art will understand that additional implementations and use cases may arise in many different arrangements and scenarios. The innovations described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and package arrangements. For example, various embodiments and / or uses may arise via integrated chip embodiments 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 particular use case or application, a wide variety of applicability to the described innovations is possible. Implementations can range from chip-level or modular components to non-modular, non-chip-level implementations, and further to aggregated, distributed, or OEM devices or systems incorporating one or more aspects of the described innovations. In some practical settings, devices incorporating the described aspects and features may also necessary include additional components and features for the implementation and practice of the claimed and described embodiments. 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 / converters, etc.). The innovations described herein are intended to be implemented in a wide variety of devices, chip-level components, systems, distributed arrays, end-user devices, etc., with different sizes, shapes, and constructions.

[0029] The various concepts presented in this disclosure can be implemented in a wide variety of telecommunications systems, network architectures, and communication standards. Now refer to... Figure 1Various aspects of this disclosure are illustrated with reference to a wireless communication system 100, by way of illustrative example and not limitation. The wireless communication system 100 includes three interaction domains: a core network 102, a radio access network (RAN) 104, and a user equipment (UE) 106. With the aid of the wireless communication system 100, the UE 106 can be implemented to perform data communication with an external data network 110 (e.g., (but not limited to) the Internet).

[0030] RAN 104 can implement any one or more suitable wireless communication technologies to provide radio access to UE 106. As an example, RAN 104 can operate according to the 3GPP New Radio (NR) specification (often referred to as 5G). As another example, RAN 104 can operate according to a hybrid of 5G NR and the Evolved Universal Terrestrial Radio Access Network (eUTRAN) standard (often referred to as Long Term Evolution (LTE)). 3GPP refers to this hybrid RAN as Next Generation RAN or NG-RAN. Of course, many other examples can be utilized within the scope of this disclosure.

[0031] As shown in the figure, RAN 104 includes multiple base stations 108. Broadly speaking, a base station is a network element in a radio access network responsible for radio transmission and reception to or from a UE in one or more cells. In different technologies, standards, or contexts, those skilled in the art may refer to a base station as a base transceiver unit (BTS), radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), access point (AP), node B (NB), evolved node B (eNB), gNodeB (gNB), or some other suitable term.

[0032] The wireless access network 104 is also shown to support wireless communication for multiple mobile devices. In 3GPP standards, a mobile device may be referred to as a User Equipment (UE), but those skilled in the art may also refer to it as a Mobile Station (MS), User Station, Mobile Unit, User Unit, Radio Unit, Remote Unit, Mobile Device, Radio Equipment, Wireless Communication Equipment, Remote Equipment, Mobile Subscriber Station, Access Terminal (AT), Mobile Terminal, Radio Terminal, Remote Terminal, Handset, Terminal, User Agent, Mobile Client, Client, or any other suitable term. The UE may be a device that provides access to network services to a user.

[0033] Within this document, a “mobile” device does not necessarily need to be capable of movement, and it may be stationary. The term mobile device or mobile equipment broadly refers to a wide variety of devices and technologies. A UE may include multiple hardware structural components whose size, shape, and arrangement are configured to facilitate communication; such components may include electrically coupled antennas, antenna arrays, RF chains, amplifiers, one or more processors, etc. For example, some non-limiting examples of mobile devices include mobile stations, cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal computers (PCs), notebooks, netbooks, smartbooks, tablet devices, personal digital assistants (PDAs), and a wide variety of embedded systems, for example, corresponding to the “Internet of Things” (IoT). Additionally, a mobile device may be an automobile or other means of transportation, a remote sensor or actuator, a robot or robotic device, a satellite radio unit, a Global Positioning System (GPS) device, an object tracking device, a drone, a multi-winged aircraft, a quadcopter, a remote control device, a consumer device or wearable device such as glasses, wearable cameras, virtual reality devices, smartwatches, health or fitness trackers, digital audio players (e.g., MP3 players), cameras, game consoles, etc. Additionally, mobile devices can be digital home or smart home devices, such as home audio, video, or multimedia equipment, appliances, vending machines, smart lighting, home security systems, smart meters, etc. Furthermore, mobile devices can be smart energy devices, security devices, solar panels or solar arrays, municipal infrastructure equipment controlling electricity (e.g., smart grids), lighting, water, etc.; industrial automation and enterprise equipment; logistics controllers; agricultural equipment; military defense equipment, vehicles, aircraft, ships, and weapons, etc. Moreover, mobile devices can provide connected medical or telemedicine support (e.g., telemedicine). Telemedicine devices can include telemedicine monitoring equipment and telemedicine management equipment, whose communications can be given priority processing or access relative to other types of information, for example, in terms of priority access or QoS related to the transmission of critical service data.

[0034] Wireless communication between RAN 104 and UE 106 can be described as utilizing an air interface. Transmissions over the air interface from a base station (e.g., base station 108) to one or more UEs (e.g., UE 106) can be referred to as downlink (DL) transmissions. According to certain aspects of this disclosure, the term downlink can refer to point-to-multipoint transmissions originating from a network node of a scheduling entity (further described below; e.g., base station 108). Another way to describe this scheme is to use the term broadcast channel multiplexing. Transmissions from a UE (e.g., UE 106) to a base station (e.g., base station 108) can be referred to as uplink (UL) transmissions. According to other aspects of this disclosure, the term uplink can refer to point-to-point transmissions originating from a scheduled entity (further described below; e.g., UE 106).

[0035] In some examples, access to the air interface can be scheduled, where a scheduling entity (e.g., base station 108) allocates resources for communication among some or all devices and apparatuses within its service area or cell. In this disclosure, as further discussed below, the scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more scheduled entities. That is, for scheduled communication, UE 106 (which may be a scheduled entity) can utilize resources allocated by scheduling entity 108.

[0036] Base station 108 is not the only entity that can act as a scheduling entity. That is, in some examples, a UE can act as a scheduling entity, which schedules resources for one or more scheduled entities (e.g., one or more other UEs).

[0037] like Figure 1 As shown, scheduling entity 108 can broadcast downlink service 112 to one or more scheduled entities 106. Broadly speaking, scheduling entity 108 is a node or device responsible for scheduling services (including downlink service 112, and in some examples, uplink service 116 from one or more scheduled entities 106 to scheduling entity 108) in a wireless communication network. On the other hand, scheduled entity 106 is a node or device that receives downlink control information 114 (including but not limited to scheduling information (e.g., permission), synchronization or timing information, or other control information) from another entity in the wireless communication network (such as scheduling entity 108).

[0038] Typically, base station 108 may include a backhaul interface for communicating with the backhaul section 120 of a wireless communication system. Backhaul 120 provides a link between base station 108 and core network 102. Furthermore, in some examples, the backhaul network may provide interconnection between corresponding base stations 108. Various types of backhaul interfaces can be employed, such as direct physical connections, virtual networks, or backhaul interfaces using any suitable transport network.

[0039] Core network 102 may be part of wireless communication system 100 and may be independent of the radio access technology used in RAN 104. In some examples, core network 102 may be configured according to 5G standards (e.g., 5GC). In other examples, core network 102 may be configured according to 4G Evolved Packet Core (EPC) or any other suitable standard or configuration.

[0040] Now refer to Figure 2 Instead of limiting it, a schematic diagram of RAN 200 is provided. In some examples, RAN 200 can be used in conjunction with those described above and Figure 1 The same as RAN 104 shown. The geographical area covered by RAN 200 can be divided into cellular areas (cells), and user equipment (UE) can uniquely identify a cellular area (cell) based on an identifier broadcast from an access point or base station. Figure 2 Macro cells 202, 204, and 206, and small cell 208 are shown, each of which may include one or more sectors. A sector is a sub-area of ​​a cell. All sectors in a cell are served by the same base station. Radio links within a sector can be identified by a single logical identifier belonging to that sector. In a cell divided into sectors, multiple sectors within the cell can be formed using multiple sets of antennas, each responsible for communicating with UEs within a portion of the cell.

[0041] exist Figure 2In the illustration, two base stations 210 and 212 are shown in cells 202 and 204; and a third base station 214 is shown for controlling a remote radio head (RRH) 216 in cell 206. That is, the base stations can have integrated antennas or can be connected to antennas or RRHs via feeder cables. In the illustrated example, cells 202, 204, and 216 can be referred to as macro cells because base stations 210, 212, and 214 support cells with large sizes. Furthermore, a base station 218 is shown in a small cell 208 (e.g., microcell, picocell, femtocell, home base station, home node B, home eNodeB, etc.), where small cell 208 may overlap with one or more macro cells. In this example, cell 208 can be referred to as a small cell because base station 218 supports cells with relatively small sizes. Cell size settings can be made according to system design and component constraints.

[0042] To understand, the wireless access network 200 can include any number of wireless base stations and cells. Furthermore, relay nodes can be deployed to extend the size or coverage area of ​​a given cell. Base stations 210, 212, 214, and 218 provide wireless access points to the core network for any number of mobile devices. In some examples, base stations 210, 212, 214, or 218 can be used in conjunction with those described above and... Figure 1 The base station / scheduling entity 108 shown is the same.

[0043] Figure 2 It also includes quadcopter or drone 220, which can be configured to act as a base station. That is, in some examples, the cell may not be stationary, and the geographical area of ​​the cell may move depending on the location of the mobile base station (such as quadcopter 220).

[0044] Within RAN 200, a cell may include UEs capable of communicating with one or more sectors of each cell. Furthermore, each base station 210, 212, 214, 218, and 220 may be configured to provide access to the core network 102 (see [link to core network]) to all UEs in the corresponding cell. Figure 1 Access points. For example, UEs 222 and 224 can communicate with base station 210, UEs 226 and 228 can communicate with base station 212, UEs 230 and 232 can communicate with base station 214 via RRH 216, UE 234 can communicate with base station 218, and UE 236 can communicate with mobile base station 220. In some examples, UEs 222, 224, 226, 228, 230, 232, 234, or 236 can communicate with the access points described herein and... Figure 1 The UE / scheduled entity 106 shown is the same.

[0045] In some examples, a mobile network node (e.g., quadcopter 220) can be configured to act as a UE. For example, quadcopter 220 can operate in cell 202 by communicating with base station 210.

[0046] In a radio access network 200, the ability of a UE to communicate while moving (independent of its location) is referred to as mobility. The various physical channels between the UE and the radio access network are typically communicated through the Access and Mobility Management Function (AMF). Figure 1 The AMF, established, maintained, and released under the control of the core network 102, may include a Security Context Management (SCMF) function that manages the security context for both control plane and user plane functions, and a Security Anchor (SEAF) function that performs authentication.

[0047] In various aspects of this disclosure, the radio access network 200 may utilize DL-based mobility or UL-based mobility to achieve mobility and handover (i.e., the UE's connection switching from one radio channel to another). In a network configured for DL-based mobility, during a call with a scheduling entity, or at any other time, the UE may monitor various parameters of the signal from its serving cell and various parameters of neighboring cells. Based on the quality of these parameters, the UE may maintain communication with one or more of its neighboring cells. During this time, if the UE moves from one cell to another, or if the signal quality from a neighboring cell exceeds the signal quality from the serving cell for a given amount of time, the UE may perform a handoff or handover from the serving cell to a neighboring (target) cell. For example, UE 224 (shown as a vehicle, but any suitable form of UE may be used) may move from a geographic area corresponding to its serving cell 202 to a geographic area corresponding to a neighboring cell 206. When the signal strength or quality from neighboring cell 206 exceeds that of serving cell 202 for a given amount of time, UE 224 may send a report message to its serving base station 210 indicating this condition. In response, UE 224 may receive a handover command and may perform a handover to cell 206.

[0048] In a network configured for UL-based mobility, the network can utilize UL reference signals from each UE to select a serving cell for each UE. In some examples, base stations 210, 212, and 214 / 216 can broadcast uniform synchronization signals (e.g., a uniform primary synchronization signal (PSS), a uniform secondary synchronization signal (SSS), and a uniform physical broadcast channel (PBCH)). UEs 222, 224, 226, 228, 230, and 232 can receive the uniform synchronization signals, derive carrier frequencies and time slot timings based on these synchronization signals, and transmit uplink pilots or reference signals in response to the derived timings. The uplink pilot signal transmitted by a UE (e.g., UE 224) can be simultaneously received by two or more cells (e.g., base stations 210 and 214 / 216) in the radio access network 200. Each cell in the network can measure the strength of the pilot signal, and the radio access network (e.g., one or more of base stations 210 and 214 / 216 or central nodes in the core network) can identify the serving cell for UE 224. As UE 224 moves through radio access network 200, the network can continue to monitor the uplink pilot signal transmitted by UE 224. When the signal strength or quality of the pilot signal measured by a neighboring cell exceeds the signal strength or quality measured by the serving cell, network 200 can, with or without notifying UE 224, hand over UE 224 from the serving cell to the neighboring cell.

[0049] Although the synchronization signals transmitted by base stations 210, 212, and 214 / 216 can be uniform, these signals may not identify a specific cell, but rather an area of ​​multiple cells operating on the same frequency or using the same timing sequence. Using areas in 5G networks or other next-generation communication networks enables an uplink-based mobility framework and improves the efficiency of both the UE and the network by reducing the number of mobility messages that need to be exchanged between the UE and the network.

[0050] In various implementations, the air interface in the radio access network 200 can utilize licensed spectrum, unlicensed spectrum, or shared spectrum. Licensed spectrum typically provides exclusive use of a portion of the spectrum by requiring a license purchased by the mobile network operator from a government regulatory agency. Unlicensed spectrum provides shared use of a portion of the spectrum without requiring a government-authorized license. While some technical rules are generally still required to access unlicensed spectrum, in general, any operator or device can obtain access. Shared spectrum can fall between licensed and unlicensed spectrum, where technical rules or restrictions may be required to access the spectrum, but the spectrum can still be shared by multiple operators or multiple RATs. For example, a licensee holding a license for a portion of licensed spectrum can provide a Licensed Shared Access (LSA) to share the spectrum with other parties (e.g., those with appropriate licensee-defined conditions for access).

[0051] The air interface in the wireless access network 200 can utilize one or more duplex algorithms. Duplex refers to a point-to-point communication link where two endpoints can communicate with each other in both directions. Full-duplex means that two endpoints can communicate with each other simultaneously. Half-duplex means that only one endpoint can send information to the other endpoint at any given time. In wireless links, full-duplex channels typically rely on physical isolation between the transmitter and receiver, as well as appropriate interference cancellation techniques. Full-duplex simulation is frequently implemented for wireless links using Frequency Division Duplex (FDD) or Time Division Duplex (TDD). In FDD, transmissions in different directions operate at different carrier frequencies. In TDD, transmissions in different directions on a given channel are separated using time-division multiplexing. That is, at some times, the channel is dedicated to transmission in one direction, and at other times, the channel is dedicated to transmission in the other direction, where the direction can change very rapidly (e.g., several times per time slot).

[0052] The air interface in the wireless access network 200 can utilize one or more multiplexing and multiple access algorithms to enable simultaneous communication of various devices. For example, the 5G NR specification provides multiple access for UL transmissions from UEs 222 and 224 to base station 210, and multiplexing of DL transmissions from base station 210 to one or more UEs 222 and 224 using Orthogonal Frequency Division Multiplexing (OFDM) with a Cyclic Prefix (CP). Additionally, for UL transmissions, the 5G NR specification provides support for Discrete Fourier Transform Spread Spectrum OFDM (DFT-s-OFDM) with CP (also known as Single Carrier FDMA (SC-FDMA)). However, within the scope of this disclosure, multiplexing and multiple access are not limited to the above schemes and can be provided using Time Division Multiple Access (TDMA), Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Sparse Code Multiple Access (SCMA), Resource Spread Multiple Access (RSMA), or other suitable multiple access schemes. In addition, time division multiplexing (TDM), code division multiplexing (CDM), frequency division multiplexing (FDM), orthogonal frequency division multiplexing (OFDM), sparse code multiplexing (SCM) or other appropriate multiplexing schemes can be used to provide multiplexing for DL ​​transmission from base station 210 to UEs 222 and 224.

[0053] The above description and in Figure 1 and 2 The channels or carriers shown may not be all the channels or carriers that can be used between the scheduling entity 108 and the scheduled entity 106, and those skilled in the art will recognize that other channels or carriers, such as other service, control and feedback channels, may be used in addition to the channels or carriers shown.

[0054] The physical channels described above are typically multiplexed and mapped to transport channels for processing at the Media Access Control (MAC) layer. The transport channel carries blocks of information called transport blocks (TBs). The transport block size (TBS), which can correspond to the number of bits of information, can be a controlled parameter based on the modulation and coding scheme (MCS) and the number of redundancies (RBs) in a given transmission.

[0055] In 3GPP version 17 systems, a UE can receive NR multicast services while in an idle or inactive state (e.g., RRC_IDLE or RRC_INACTIVE state). Additionally, a UE can receive NR multicast services while in a connected state (e.g., RRC_CONNECTED state). However, when a UE is in an idle or inactive state, it may not be able to provide feedback to the network (e.g., the base station). Conversely, when a UE is in a connected state, it may be able to provide L1 / L2 feedback to the network for any multicast services received from the network or the base station. Therefore, increasing the number of UEs in a connected state when a UE is receiving multicast services may be advantageous, as the network can improve the reliability of the multicast service based on the feedback. For example, using feedback from UEs in a connected state, the base station can retransmit multicast services for higher reliability. However, too many UEs operating in RRC connected state to receive multicast services may cause overload at the base station. Accordingly, the base station can perform access overload control (or simply access control) to limit the number of UEs allowed to enter the RRC connection state for the purpose of receiving multicast services.

[0056] Various aspects of this disclosure relate to controlling access used by a UE to receive multicast services. According to some aspects, a base station broadcasts one or more cell prohibition parameters to prohibit a UE from camping on a cell to receive multicast services. In some aspects, the base station may also configure uniform access control parameters for the UE to provide access for an individual UE or a set of UEs to receive one or more multicast services. A UE can camp on a base station or a cell by selecting, for example, a cell to receive system information via a control channel. A UE receiving the broadcast cell prohibition parameters can camp on a cell to receive multicast services based on the cell prohibition parameters allowing the UE to camp on the base station's cell. While or after camping on a cell, the UE may seek to transition to a connected state with the base station (e.g., a Radio Resource Control (RRC) connected state) to receive multicast services. The UE can then initiate a Random Access (RACH) procedure to establish or restore the RRC connected state. During a random access procedure, the base station may receive RACH message 3 or message A (e.g., including an RRC setup request message or an RRC recovery request message) from a UE requesting access to one or more multicast services based on one or more configured unified access control parameters. This message includes the RRC establishment reason or recovery reason for the multicast service. The base station may send a response message (e.g., an RRC_REJECT message) in RACH message 4 or message B, indicating whether the UE has been refused the establishment or recovery of the RRC connection state for receiving one or more multicast services.

[0057] Specific aspects of the disclosed technology enable a base station to control a UE's ability to enter a connected state with the base station's cell to receive multicast services, thereby preventing or mitigating congestion at the base station. For example, the base station can broadcast one or more prohibition parameters to a group of UEs, informing them whether the base station is configured to provide multicast services. Upon receiving the one or more prohibition parameters and recognizing that the base station is configured for multicast services, the UEs in the group can select a cell of the base station for receiving multicast services (e.g., camp on the base station's cell).

[0058] The base station may also provide (e.g., broadcast) one or more access control parameters to the UE (or a set of UEs), which inform the UE whether it is permitted to establish or restore an RRC connection state with the base station. Access control parameters may be associated with multicast services, one or more prohibition factors, or one or more prohibition times. By configuring prohibition factors and prohibition times, the base station may be able to control the likelihood that a UE can send an access message to the base station requesting the establishment or restoration (e.g., restoration) of an RRC connection state to receive multicast services.

[0059] In some scenarios, such as when the number of UEs in an RRC connected state with a base station's cell exceeds a threshold, the base station may experience overload. When overloaded, or to prevent overload, the base station can configure a blocking factor or blocking time to delay UEs from sending access messages or increase the likelihood of delayed UE access message transmission. Delaying UE access message transmission allows one or more other UEs sufficient time to transition from an RRC connected state to an RRC idle or RRC inactive state, thus enabling UEs to enter an RRC connected state in the future when the base station can maintain the number of UEs in the RRC connected state below a threshold, thereby alleviating congestion at the base station. In some such examples, the larger the number of UEs above the threshold, the greater the likelihood of a longer delay.

[0060] Subsequently, a UE in an RRC idle or inactive state can attempt to transition to an RRC connected state, and thus can send an access message to the base station requesting to establish or restore the RRC connected state to receive multicast services. If the base station is experiencing an overload condition, it can send a rejection message upon receiving the access message, indicating that the UE's request to establish or restore the RRC connected state is rejected. By rejecting access messages from the UE when the base station is experiencing an overload condition, the base station can prevent the increase or prolongation of overload conditions. Conversely, if the base station is not experiencing an overload condition (e.g., due to latency), it can exchange random access messages with the UE, allowing the UE to establish or restore the RRC connected state and receive multicast services.

[0061] Specific aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. In some examples, the described techniques can be used to monitor or improve the reliability of providing multicast services via feedback from a group of UEs, while maintaining service quality and reducing congestion. For example, by delaying the sending of access request messages from UEs seeking multicast services to the base station providing the multicast service, the base station can increase feedback to improve the reliability or quality of the multicast service while preventing overload conditions. The base station can use a wide variety of values ​​and parameters to indicate the state of the UE and control the UE's access to receive multicast services. As described herein, the base station can control the UE's access to receive multicast services by identifying whether the base station is configured to allow the UE to camp on the base station or cell to receive one or more multicast services. The base station can also control the UE's access to receive multicast services by providing the UE with one or more configured access parameters that enable the UE to identify whether the UE is allowed to camp on the base station or cell to receive one or more multicast services. In addition, the base station can control the UE's access for receiving multicast services based on one or more access control parameters. These one or more access control parameters enable the UE to identify whether the UE is prohibited from sending access attempts (e.g., access messages) for connection setup to receive one or more multicast services.

[0062] For example, the base station can provide the UE with one or more prohibition parameters, and can notify the UE whether the base station is configured to provide multicast services. After receiving one or more prohibition parameters, the UE can select the cell of the base station used to receive multicast services (e.g., camp on the cell of the base station), and identify that the base station is configured for multicast services.

[0063] The base station can also provide the UE with one or more access control parameters, and can notify the UE whether it is permitted to establish or restore a Radio Resource Control (RRC) connection state with the base station. Access control parameters can be associated with multicast services, one or more prohibition factors, and one or more prohibition times. By configuring prohibition factors and prohibition times, the base station may be able to control how quickly the UE will be able to send an access message to the base station requesting the establishment or re-establishment (e.g., restoration) of an RRC connection state to receive multicast services.

[0064] If a base station is overloaded (where a number of UEs (greater than a threshold number) are connected to the base station's cell), the base station can configure a blocking factor and / or a blocking time to delay UEs from sending access messages or increase the likelihood of delayed UEs sending access messages. Delaying UEs from sending access messages can allow one or more other UEs sufficient time to leave the base station and reduce the number of UEs in RRC connected states to below a threshold number, thereby alleviating congestion at the base station. In some embodiments, the larger the number of UEs above the threshold number, the greater the likelihood of a longer delay.

[0065] Subsequently, the UE can send an access message to the base station requesting to establish or restore the RRC connection state to receive multicast services. If the base station is overloaded, it can send a rejection message upon receiving the access message, indicating that the UE's request to establish or restore the RRC connection state is rejected. By rejecting access messages from the UE when the base station is overloaded, the base station can prevent the increase or prolongation of overload conditions. Conversely, if the base station is not overloaded (e.g., due to delay), it can exchange random access messages with the UE to allow the UE to establish or restore the RRC connection state and receive multicast services. By controlling the likelihood of delaying the sending of access messages to the base station, giving it time to alleviate overload conditions, the base station can more efficiently or frequently maximize the number of UEs in the connected state receiving multicast services (e.g., within a threshold number) to receive more channel quality feedback from the UEs, thereby improving the reliability and quality of the multicast service.

[0066] Figure 3This is a conceptual diagram of an example wireless communication system 300 for controlling New Radio (NR) multicast and broadcast access, based on some aspects of this disclosure. The wireless communication network may include user equipment 302 and base station 304, and may be configured to provide one or more multicast / broadcast services or one or more unicast services. In operation 306, base station 304 may identify whether a group of UEs is allowed to select a cell for receiving the multicast / broadcast service. The multicast / broadcast service may be associated with one of the following: a specific Public Land Mobile Network (PLMN), or the entire Public Land Mobile Network. In some embodiments, identifying whether a group of UEs is allowed to select a cell for receiving the multicast / broadcast service includes identifying whether the base station supports multicast / broadcast services.

[0067] For example, base station 304 can identify whether it is configured to allow user device 302 to camp on base station 304 or a cell to receive one or more multicast services. In some embodiments, base station 304 can identify whether it is configured to allow user device 302 to camp on base station 304 to receive one or more multicast services based on whether the cellBarred-MBS field has an enable information element or a disable information element. For example, base station 304 may have a cellBarred-MBS field and a cellBarred field. The cellBarred-MBS field may have a disable information element, and the cellBarred field may also have a disable information element. In this case, base station 304 may not allow user device 302 to camp on base station 304 to receive access to one or more multicast services or one or more unicast services. In some embodiments, when the cellBarred field has a disable information element, base station 304 may not allow user device 302 to camp on base station 304 to receive one or more multicast services or one or more unicast services, regardless of whether the cellBarred-MBS field has an enable information element or a disable information element.

[0068] As another example, base station 304 may have a cellBarred-MBS field and a cellBarred field. The cellBarred-MBS field may have a disabled information element, and the cellBarred field may have an enabled information element. In this case, base station 304 may not allow user device 302 to camp on base station 304 to receive one or more multicast services. However, base station 304 may be able to allow user device 302 to camp on base station 304 to receive one or more unicast services.

[0069] As another example, base station 304 may have a cellBarred-MBS field and a cellBarred field. The cellBarred-MBS field may have an enable information element, and the cellBarred field may also have an enable information element. In this case, base station 304 may be able to allow user device 302 to camp on base station 304 to receive one or more multicast broadcast services or one or more unicast services, or both.

[0070] As another example, base station 304 may have a prohibition information element for the cellBarredMBS field and a false information element for the cellReservedForMBSUse field. In this case, via an SIB1 message or another SIB, base station 304 may provide the UE with indications of one or more other frequencies associated with the same cell in which multicast services are available, to assist the UE in searching for multicast services in other frequencies. Alternatively, via an SIB1 message or another SIB, base station 304 may provide the UE with the identifiers and frequencies of different cells (e.g., neighboring cells) in which multicast services are available, to assist the UE in searching for multicast services. In some embodiments, base station 304 may provide a UE in an RRC connected state with an RRC release message containing redirection information that redirects the UE in the RRC connected state to other cells for receiving multicast services.

[0071] Base station 304 or the network supporting base station 304 can independently configure the cellBarred field and the cellBarred-MBS field, or convert the cellBarred field and the cellBarred-MBS field between enabled and disabled information elements. In some embodiments, the cellBarred-MBS field may have enabled or disabled information elements based on the capabilities of base station 304. For example, base station 304 may not be configured to provide user equipment 302 with access to any multicast services, and therefore, the cellBarred-MBS field may have a disabled information element. As another example, base station 304 may be configured to provide user equipment 302 with access to all multicast services, and therefore, the cellBarred-MBS field may have an enabled information element.

[0072] In operation 308, base station 304 may configure or generate one or more cell prohibition parameters. In some embodiments, base station 304 may configure or generate one or more cell prohibition parameters when (e.g., in response to) base station 304 allowing a group of UEs to select a cell for receiving multicast services. For example, base station 304 may configure or generate one or more cell prohibition parameters when (e.g., in response to) base station 304 recognizing that base station 304 is configured to allow user equipment 302 to camp on base station 304 or a cell to receive one or more multicast services. One or more cell prohibition parameters may be sent to user equipment 302 via System Information Block (SIB) messages (e.g., SIB Type 1 (SIB1) messages) or Master Information Block (MIB). One or more cell prohibition parameters enable user equipment 302 to recognize whether user equipment 302 is allowed to camp on base station 304 or a cell to receive one or more multicast services.

[0073] In operation 310, base station 304 may send or broadcast one or more cell prohibition parameters to a group of UEs, including UE 302, for receiving multicast services. In some embodiments, base station 304 may send or broadcast one or more cell prohibition parameters to the group of UEs, including UE 302, based on whether the group of UEs is allowed to select a cell for receiving multicast services. In some embodiments, as described herein, when base station 304 identifies that base station 304 is configured to allow user equipment 302 to camp on base station 304 or a cell to receive one or more multicast services, base station 304 may configure or generate one or more cell prohibition parameters. One or more prohibition parameters may be sent to user equipment 302 via System Information Block Type 1 (SIB1) or Master Information Block (MIB) messages to enable user equipment 302 to identify whether user equipment 302 is allowed to camp on base station 304 or a cell to receive one or more multicast services.

[0074] For example, base station 304 can rely on the cellBarred-MBS / cellReservedMBSUse information element to determine that base station 304 is configured to provide access to one or more multicast services. Base station 304 can send one or more configured cell prohibition parameters to user equipment 302 as an indication to user equipment 302 that base station 304 is configured to provide user equipment 302 with access to one or more multicast services.

[0075] In operation 312, user equipment 302 can identify whether it is permitted to camp on a cell of base station 304 to receive multicast services based on one or more cell prohibition parameters. For example, user equipment 302 can receive one or more cell prohibition parameters from base station 304 based on whether a group of user equipments, including user equipment 302, are permitted to select a cell of the base station for receiving multicast services. After receiving one or more cell prohibition parameters, user equipment 302 can identify whether it is permitted to camp on a cell of base station 304 to receive multicast services.

[0076] When user equipment 302 receives one or more cell-barred parameter information elements, such as cellBarredMBS or cellReservedforMBSUse, and if these information elements indicate that multicast service is prohibited, the user equipment will not camp on the cell to receive multicast service. If these information elements indicate that the cell is not prohibited for multicast service, the user equipment (UE) may be allowed to camp on the cell to receive multicast service.

[0077] For example, base station 304 may transmit a CellReservedforMBSUse field to user equipment 302, for instance, in a System Information Block Type 1 (SIB1) message. The CellReservedforMBSUse field indicates whether user equipment 302 is prohibited from camping on the cell to access one or more multicast services. The CellReservedforMBSUse field may have an enable information element or a true information element to indicate to user equipment 302 that user equipment 302 may be allowed to camp on the cell to receive access to one or more multicast services through base station 304. The CellReservedforMBSUse field may also have a disable information element, a false information element, or a non-true information element to indicate to user equipment 302 that user equipment 302 may be prohibited from camping on the cell to receive one or more multicast services through base station 304.

[0078] As another example, base station 304 may transmit a CellReservedforMBSUse field and a cellBarred field to user equipment 302, for example, in a System Information Block Type 1 (SIB1) message. The CellReservedforMBSUse field indicates whether user equipment 302 is prohibited from camping on the cell to receive one or more multicast services, and the cellBarred field indicates whether user equipment 302 is prohibited from camping on the cell to receive unicast services (e.g., one or more unicast services) from the cell via base station 304. In some embodiments, the CellReservedforMBSUse field may have an enable information element or a true information element, and the cellBarred field may have a non-prohibit information element. Together, these elements indicate to user equipment 302 that user equipment 302 is allowed to camp on the cell to receive unicast services from the cell, but is not allowed to receive any multicast services from the cell. In this case, when user equipment 302 receives one or more indications, user equipment 302 may not camp on base station 304, but instead search for another base station to receive one or more multicast services. In some embodiments, the CellReservedforMBSUse field may have a disabled information element or a false information element, and the cellBarred field may have a non-prohibited information element, indicating to the user equipment 302 that the user equipment 302 may be allowed to camp on the cell to receive both unicast and multicast services through the base station 304. In some embodiments, the CellReservedforMBSUse field may have an enabled information element or a true information element, and the cellBarred field may have a prohibited information element, indicating to the user equipment 302 that the user equipment 302 may be allowed to camp on the cell to receive only multicast services and the UE is not allowed to receive any type of unicast service from the base station. In this case, a UE intending to receive only multicast services from the base station 304 may camp on the cell, and a UE intending to receive unicast services may not camp on the cell but may search for other cells. The CellReservedforMBSUse field may belong to a specific Public Land Mobile Network (PLMN) among multiple Public Land Mobile Networks, or the CellReservedforMBSUse field may belong to all Public Land Mobile Networks.

[0079] Base station 304 can use system information messages to provide a list of multicast services available in the serving cell. Multicast service information at the frequency level can be provided for the serving cell and for other neighboring cells at the same or different frequencies. The presence or absence of this new system information block can be indicated in SIB1. User equipment 302 can interpret the presence or absence of new SIB scheduling information in SIB1 as an implicit indication of whether the cell supports or does not support any multicast services in that cell, and can identify whether the user equipment is camped on that cell.

[0080] To control access overload, the base station can use a unified access control mechanism. One or more access control parameters may include one or more access category parameters associated with one or more services. Access category parameters can be used in the unified access control mechanism at user equipment 302. Typically, during the unified access control mechanism, user equipment 302 can receive at least one of the following from base station 304: one or more access category parameters and one or more access identity parameters. One or more access identity parameters may include an access identity value associated with user equipment 302. The access identity value can be a value indicating how user equipment 302 is configured. For example, the access identity value may indicate that user equipment 302 is configured for high-priority services, mission-critical services, multimedia-priority services, etc. The access identity value provides an indication of who the user equipment is.

[0081] As part of the unified access control enhancement, the base station can provide radio channel condition threshold configuration to user equipment (UE) intending to receive multicast services in the Radio Resource Control (RRC) connected state. The radio channel condition threshold parameters in the configuration can indicate any combination of parameters including: Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), SSB-based Signal-to-Noise Ratio (SINR), CSI-RS Reference Signal, Channel State Information (CSI) reporting threshold, etc. When the parameters of the channel associated with the UE exceed one or more configured threshold parameters, the UE can be restricted from entering the RRC connected state for the purpose of receiving multicast services. Otherwise, based on the unified access control mechanism, the UE can be allowed to enter the RRC connected state for the purpose of receiving multicast services.

[0082] In operation 314, base station 304 can identify whether to allow a set of UEs in the group to establish or restore a Radio Resource Control (RRC) connection with base station 304 to receive multicast services. In some embodiments, identifying whether to allow a user equipment (UE) to establish or restore an RRC connection with the base station to receive multicast services may be based on an overload condition at the base station and one of the following: a received RRC establishment reason or a received RRC restoration reason. In some embodiments, identifying whether to allow a set of UEs in the group to establish or restore a RRC connection with the base station to receive multicast services may be based on allowing the group of UEs to select a cell for receiving multicast services.

[0083] In operation 316, base station 304 configures one or more access control parameters. In some embodiments, base station 304 may have configured or generated one or more access control parameters when (e.g., in response to) base station 304 being configured to provide access to one or more multicast services for user equipment 302 in a radio resource control connection state. In some embodiments, base station 304 may have configured or generated one or more access control parameters when (e.g., in response to) base station 304 allowing the group of UEs to establish or resume a radio resource control connection. These access control parameters may include one or more access class values, and each access class may be configured with a prohibition factor and a prohibition timer. One or more access control parameters may be sent to user equipment 302 via System Information Block Type 1 (SIB1) messages so that user equipment 302 can identify whether user equipment 302 is prohibited from sending access attempts (e.g., access messages) for connection setup to receive one or more multicast services. In some embodiments, one or more access control parameters are associated with all multicast services or one or more specific multicast services.

[0084] Each of one or more cell prohibition factors and each of one or more cell prohibition times may be associated with at least one access class value described herein. The cell prohibition parameter enables user equipment 302 to identify whether user equipment 302 is permitted to send an access attempt to base station 304 or a cell to establish or restore an RRC connection for the purpose of receiving one or more multicast services. The cell prohibition factor may be a number generated by base station 304 that is not less than zero (0) and not greater than one (1) (e.g., 0.4, 0.6, 0.8). The cell prohibition time may be a specified or base station-indicated amount of time between instances when user equipment generates a random number to be compared with the cell prohibition factor as described herein. Base station 304 may include cell prohibition factors and cell prohibition times to maintain or limit the number of user equipments that may camp on base station 304 to receive one or more multicast services (e.g., maintain or limit them below a threshold). Alternatively or additionally, base station 304 may include cell prohibition factors and cell prohibition times to maintain or limit the data rate at which data is transmitted through base station 304 (e.g., maintain or limit it below a threshold).

[0085] Base station 304 may configure or generate one or more cell prohibition factors and one or more cell prohibition times based on at least one of the following: one or more Quality of Service (QoS) parameters associated with one or more multicast services, the number of one or more user equipments receiving access to multiple multicast services through the base station, or the data rate at which one or more user equipments access data through the base station. For example, base station 304 may generate an access class value associated with all multicast services, as described herein. Base station 304 may also identify that the number of user equipments residing on base station 304 exceeds a threshold number. Base station 304 may configure the cell prohibition factor associated with all multicast services to a relatively low value (e.g., 0.1, 0.3) to provide user equipment 302 with a low chance of receiving access to all multicast services and a high chance of being prohibited. In some embodiments, base station 304 may configure the cell prohibition factor to a value of zero, thereby denying user equipment 302 the opportunity to access the multicast service associated with the access class value. Alternatively, base station 304 may configure the cell prohibition time associated with all multicast services as a relatively long time period between instances when user equipment 302 generates a random number for comparison with a cell prohibition factor as described herein. By giving user equipment 302 a high chance of being prohibited and a long amount of time between generating the random number, base station 304 is given time to allow other user equipment to disengage from base station 304 and reduce the number of user equipment camped on the base station to below a threshold number.

[0086] In some embodiments, when base station 304 is configured to provide access to one or more multicast services to user equipment 302 in a radio resource control (RFC) connection state, base station 304 may configure or generate one or more access control parameters. Subsequently, base station 304 may configure or generate one or more access control parameters including one or more access class values, and each access class may be configured with a prohibition factor and a prohibition timer. One or more access control parameters may be sent to user equipment 302 via System Information Block Type 1 (SIB1) messages. The one or more access control parameters enable user equipment 302 to identify whether user equipment 302 is prohibited from sending access attempts (e.g., access messages) for connection setup to receive one or more multicast services.

[0087] Upon receiving access control parameters for the access class, and when a user equipment (UE) establishes or restores a radio resource control (RRC) connection to receive multicast services in the RRC connection state, the UE can determine whether to send an access attempt based on access class parameters (e.g., a prohibition factor and prohibition time for the access class). As part of a prohibition test for a given access class, UE 302 can generate a random number not less than or greater than the access class prohibition factor. Subsequently, UE 302 can determine that it is not permitted to send access attempts to establish or restore an RRC connection to receive one or more multicast services from base station 304. When UE 302 determines that it is not permitted to send access attempts associated with the access class to establish or restore an RRC connection to receive one or more multicast services from base station 304 based on a comparison between the generated random value and the cell prohibition factor, the UE starts a timer. While the timer for that access class is running, the UE may be prohibited from initiating access attempts for the same access class. After the timer expires, if the UE seeks to access the cell for the same access class, it may be allowed to repeat the prohibition test for the same access class. If the subsequently generated random number is less than the cell prohibition factor, then user equipment 302 can recognize that user equipment 302 is permitted to send an access attempt to base station 304 or the cell to receive one or more multicast services from base station 304, and the process stops. Otherwise, user equipment 302 can restart the timer and generate another random number according to the cell prohibition timer. This process can be repeated until user equipment 302 generates a random number less than the cell prohibition factor, indicating that user equipment 302 is permitted to send an access attempt to base station 304 or the cell to receive one or more multicast services from base station 304 in a radio resource control connected state.

[0088] Base station 304 can generate one or more cell prohibition factors and one or more cell prohibition times based on at least one of the following: one or more Quality of Service (QoS) parameters associated with one or more multicast services, the number of one or more UEs receiving access to one or more multicast services through the base station, or the data rate at which one or more UEs access data through the base station. For example, base station 304 can generate an access class value associated with all multicast services. Base station 304 can also identify that the number of user equipments that can establish a radio resource control connection to base station 304 is higher than a threshold number. Base station 304 can configure the cell prohibition factor associated with all multicast services to a relatively low value (e.g., 0.1, 0.3) to provide user equipment 302 with a low chance of receiving access to all multicast services and a high chance of being prohibited. In some embodiments, base station 304 can configure the cell prohibition factor to a value of zero, thereby not giving user equipment 302 the opportunity to access multicast services. In addition, base station 304 can configure the cell prohibition time associated with all multicast services to a relatively long time period. This allows the amount of time between instances when user equipment 302 generates a random number to be extended to a relatively long period. By giving user equipment 302 a high chance of being disabled and a long amount of time between generating random numbers, time can be provided to base station 304 to allow other user equipment to disconnect from base station 304 and reduce the number of user equipment establishing or resuming RRC connections to the base station to below a threshold number.

[0089] As another example, base station 304 can also identify that the Quality of Service (QoS) associated with all multicast services is relatively high or strong. Base station 304 can configure a cell prohibition factor associated with all multicast services to a relatively high value (e.g., 0.7, 0.9) to provide user equipment 302 with a high chance of receiving access to all multicast services and a low chance of being prohibited. In some embodiments, base station 304 can configure an access class value to one (1), thereby granting user equipment access to the multicast services associated with that access class value. In some embodiments, when the access class prohibition factor is zero, user equipment 302 can identify that user equipment 302 has access to the multicast services. Furthermore, base station 304 can configure the cell prohibition time associated with all multicast services to a relatively short time period. This allows the amount of time between instances when user equipment 302 generates random numbers to be extended to a relatively short time period. By giving user equipment 302 a low chance of being prohibited and a short amount of time between generating random numbers, base station 304 can provide user equipment 302 with a fast opportunity to receive access to multicast services through base station 304, and increase the number of user equipment connected to the base station (e.g., to establish a radio resource control connection with the base station) to receive high quality of service.

[0090] After the access control check, if a user equipment is allowed to send an access attempt to establish or restore a Radio Resource Control (RRC) connection, the user equipment can initiate a Random Access (RACH) procedure. During the RACH procedure, message 3 or message A may carry a RRC setup request message or a RRC recovery request message. The RRC setup request message may include a reason for establishing a multicast service, or the RRC recovery request message may include a reason for recovering a multicast service. Upon receiving message 3 or message A containing the reason for establishment / recovery = multicast service, base station 304 may reject the connection setup or allow the connection setup / recovery procedure based on overload conditions. If base station 304 rejects the RRC connection setup or RRC recovery procedure, the base station may send a RRC rejection message including a wait timer. In some embodiments, while the wait timer is running, the user equipment may be prevented from establishing or restoring a RRC connection. When the wait time expires, the user equipment may be allowed to initiate an access attempt again, and the above procedure may be repeated.

[0091] Figure 4 Table 400 illustrates an example mapping of access identity values ​​to prohibition parameters for controlling multicast and broadcast access, according to some aspects of this disclosure. Figure 4As shown, Table 400 includes multiple access identity values, and each access identity value is used to specify the device type based on device configuration. Each of the multiple access identity values ​​can be a numerical value starting with zero (e.g., an integer value). As part of the unified access control parameters in SIB1, each access identity can be prohibited or not prohibited by setting the associated access prohibition bit (e.g., "1" for prohibition, "0" for not prohibition). The UE may seek to send an access attempt to the base station. The UE can verify whether the access attempt associated with the access identity is prohibited or not based on the prohibition bit value received for the access identity.

[0092] As described herein, each of a plurality of access identity values ​​can be mapped to a user equipment configuration. As an example, a user equipment associated with access identity value one (1) can be configured for Multimedia Priority Service (MPS). As another example, a user equipment associated with access identity value two (2) can be configured for Mission Critical Service (MCS).

[0093] One or more access class values ​​may include one or more access class values ​​associated with a service. An access class value may be a value indicating what an access message is requesting. For example, an access class value may indicate that user equipment 302 is requesting access for: paging service, emergency call service, multimedia telephony (MMTEL) voice session service, MMTEL video session service, real-time text service, IP multimedia subsystem (IMS) messaging service, short message service (SMS), etc. The access class value provides an indication of what user equipment 302 is doing or wants to do. In some embodiments, the access class value may be a standard value or a carrier-specified value. The NAS may provide a radio resource establishment reason to be used for services initiated by the NAS. For connections initiated by radio resource control, radio resource control is used to identify what the radio resource control establishment reason is. NAS TS 24.501, Table 4.5.2.2 may specify one or more mapping tables for access class and radio resource control establishment terms.

[0094] Figure 5 Table 500 illustrates an example mapping of access category values ​​to prohibition parameters for controlling multicast and broadcast access, according to some aspects of this disclosure. Figure 5 As shown, Table 500 includes multiple access category values, multiple conditions associated with the user equipment, and multiple access attempt types. Each access category value can be a numeric value starting with zero (e.g., an integer value). The numeric value can be a standard value or a value specified by the operator. The multiple conditions associated with the user equipment can be conditions related to the user equipment associated with the access category value. The multiple access attempt types can relate to the type of service the user equipment is seeking to receive access to.

[0095] Each of the multiple access category values ​​can be mapped to conditions and access attempt types associated with the user equipment. As an example, for access category value one (1), the conditions associated with the user equipment providing that access category value include: "The UE is configured for delay-tolerant service and is subject to access control for access category 1, which is determined based on the relationship between the UE's home public land mobile network (HPLMN) and the selected public land mobile network." As another example, for access category value three (3), the conditions associated with the user equipment providing that access category value include all conditions except those for access category value one (1).

[0096] Each of the multiple access category values ​​can be mapped to an access attempt type. As an example, for access category value one (1), the access attempt type can indicate that the associated user equipment includes all access attempt types except for emergency services or mobile-initiated (MO) anomalous data. As another example, for access category value three (3), the access attempt type can indicate that the associated user equipment includes access attempts associated with mobile-initiated signaling at the non-access stratum (NAS) level arising from services other than paging services.

[0097] In some embodiments, each of the multiple access category values ​​can be mapped to additional information, such as annotations indicating one or more other parameters. As an example, for access category value one (1), one or more other parameters may indicate that, for access category 1, this is accompanied by information defining whether the access category is applicable to user equipment having one of the following categories: (a) user equipment configured for delay-tolerant services; (b) user equipment configured for delay-tolerant services and neither in its home public land mobile network nor in its equivalent public land mobile network; (c) user equipment configured for delay-tolerant services and neither in the public land mobile network of the country in which the user equipment is roaming, listed in the operator-defined public land mobile network selector list on the SIM / USIM, nor in its home public land mobile network equivalent to its home public land mobile network. When the user equipment is configured for EAB, it is also configured for delay-tolerant services. In the case of user equipment configured for both EAB and EAB overriding, access category 1 is not applicable when the upper layer indicates overriding access category 1. As another example, for access category value three (3), the prohibition parameter can indicate that the associated user equipment is prohibited from accessing signaling initiated by a mobile terminal at the non-access stratum (NAS) level from services other than paging services.

[0098] As an example, for access category values ​​32-63, one or more other parameters can indicate: when both carrier-based access category and standard access (access attempts can be classified as either) exist, and the standard access category is neither 0 nor 2, the user equipment applies the carrier-based access category. When both carrier-based access category and standard access category (access attempts can be classified as either) exist, and the standard access category is 0 or 2, the user equipment can apply the standard access category.

[0099] As another example, for an access attempt type associated with access category value four (4), a multimedia telephony (MMTEL) voice session service may include a real-time text (RTT) service. As yet another example, for an access attempt type associated with access category value seven (7), MO data that does not belong to any other access category may include IP multimedia subsystem messaging. As yet another example, for an access attempt type associated with access category value nine (9), MO IP multimedia subsystem registration associated with signaling that may include data that does not belong to any other access category may include signaling-related IP multimedia subsystem registration (such as initial registration, re-registration, and subscription refresh for IP multimedia subsystem messaging). As an example, for access category value ten (10), one or more other parameters may indicate that category ten is applicable to Node B of the Internet of Things (IoT) using Node B IoT connections to 5GC.

[0100] Return to Figure 3In some embodiments, one or more access control parameters may include one or more access category values ​​associated with one or more multicast services. When base station 304 sends one or more access category access control parameter values ​​associated with one or more multicast services, user equipment 302 may receive those access category access control parameter values ​​and identify whether user equipment 302 is prohibited from sending access messages (e.g., access attempts) for connection setup to request one or more multicast services associated with the received access category value. For example, user equipment 302 may receive from base station 304 an access category value indicating a video streaming multicast service. User equipment 302 may match the received access category value with an access category value associated with the video streaming multicast service that user equipment 302 seeks to receive, and based on the match, identify that user equipment 302 is not prohibited by base station 304 from sending access messages for requesting connection setup to access the video streaming multicast service. As discussed herein, user equipment 302 may then send to base station 304 an access message (e.g., an access attempt for connection setup) requesting the video streaming multicast service from base station 304 based on one or more received access category parameters. In some embodiments, when base station 304 does not include an access class value that matches the access class value associated with the multicast service to which the user equipment is seeking access, user equipment 302 can recognize that base station 304 is preventing user equipment 302 from sending access messages for connection setup and receiving multicast services, and that the unified access control mechanism has ended. In some embodiments, one or more access class values ​​identify all multicast services or one or more specific multicast services (e.g., video streaming multicast services).

[0101] In operation 318, base station 304 sends or broadcasts one or more access control parameters to the group of UEs, including UE 302, based on whether the UE group is permitted to establish or restore its RRC connection state with base station 304 to receive multicast services. In operation 320, user equipment 302 identifies whether UE 302 is prohibited from sending access request messages for establishing or restoring its RRC connection state to receive multicast services based on one or more access control parameters. For example, user equipment 302 may receive one or more access control parameters from base station 304 based on whether user equipment 302 is permitted to establish or restore its Radio Resource Control (RRC) connection state with base station 304 to receive multicast services. After receiving one or more access control parameters, user equipment 302 may identify whether user equipment 302 is prohibited from sending access request messages for establishing or restoring its RRC connection state to receive multicast services.

[0102] In operation 322, user equipment 302 may send an access request message to base station 304 to request the establishment or restoration of an RRC connection state to receive multicast services. For example, if access attempts associated with an access class are not prohibited, the UE may send an access request message to the base station to request the establishment or restoration of an RRC connection state to receive multicast services. Base station 304 may have already sent these access control parameters to user equipment 302 via a System Information Block Type 1 (SIB1) message. One or more access control parameters may have enabled user equipment 302 to identify whether user equipment 302 is prohibited from sending access attempts (e.g., access messages) for connection setup to receive one or more multicast services. In response, user equipment 302 may send an access message to request connection setup to receive one or more multicast services. User equipment 302 may send the access message to request setup to receive one or more multicast services based on one or more access control parameters. For example, when one or more configured access parameters do not indicate that user equipment 302 is prohibited from sending access messages for requesting connection setup to receive access to one or more multicast services, or when one or more configured access parameters indicate that user equipment 302 is not prohibited from sending access messages for requesting connection setup to receive access to one or more multicast services, user equipment may send access messages for requesting connection setup to receive access to one or more multicast services to base station 304. As an example, if user equipment 302 is not prohibited from sending access messages for requesting connection setup to access one or more multicast services (e.g., as described in TS 38.331, Section 5.3.14.5: Access barring check), user equipment 302 may send access messages, such as RRCSetupRequest or RRCResumeRequest messages, which include, for example, a new reason value associated with the multicast service (e.g., an access class value). The new reason value associated with one or more multicast services may be mapped to an establishment reason or recovery reason also associated with one or more multicast services. This allows base station 304 to distinguish between user equipment attempting to establish a multicast connection and user equipment attempting to establish a unicast connection. It also allows base station 304 to identify whether a user equipment is establishing an RRC connection for the first time to receive one or more multicast services, or whether a user equipment is resuming a suspended RRC connection to receive one or more multicast services. If a user equipment wants to establish an RRC connection for unicast data, then if the user equipment receives multicast data during an ongoing unicast connection, the user equipment can utilize unicast control.

[0103] In operation 324, base station 304 can determine whether to allow user equipment 302 to establish or restore RRC connection state to receive multicast broadcast services. For example, base station 304 can receive an access request message from user equipment 302 in the UE set to request the establishment or restoration of RRC connection state to receive multicast broadcast services. After receiving the access request message, base station 304 can determine whether to allow user equipment 302 to establish or restore RRC connection state to receive multicast broadcast services.

[0104] In some embodiments, determining whether to allow a set of UEs in a group to establish or resume an RRC connection state with the base station to receive multicast services is based on overload conditions at base station 304. For example, base station 304 may receive an access message and determine whether user equipment 302 is allowed to enter an RRC connection state to receive multicast services. Base station 304 may determine whether a user equipment is allowed to enter an RRC connection state when too many user equipments (UEs) are camped on the cell of base station 304, when too much data (e.g., data rates above a threshold data rate) is passing through the base station and being transmitted with user equipments (UEs), or when the quality of service (QoS) at base station 304 is below a threshold QoS.

[0105] As another example, the reception of an access message by base station 304 may trigger base station 304 to evaluate one or more Quality of Service (QoS) parameters associated with one or more multicast services, compare the number of one or more user equipments receiving access to one or more multicast services through the base station with a threshold number (overload condition), or compare the data rate of one or more user equipments accessing data through base station 304 with a threshold data rate (overload condition) to identify whether a user equipment is prohibited from entering the RRC connection state to access one or more multicast services through the base station. In some embodiments, in response to receiving the access message, base station 304 may identify that one or more QoS parameters associated with one or more multicast services are relatively low, the number of one or more user equipments receiving access to one or more multicast services through the base station is higher than the threshold number, or the data rate of one or more user equipments accessing data through base station 304 is higher than the threshold data rate. Therefore, base station 304 may send a response message based on the access message to indicate that user equipment 302 is denied entry into the RRC connection state to receive one or more multicast services, and subsequently prohibit user equipment 302 from accessing one or more multicast services.

[0106] In some embodiments, allowing a set of UEs in the group to establish or restore an RRC connection state with base station 304 to receive multicast services is based on one of the received RRC establishment reason or received RRC recovery reason included in the access message. For example, base station 304 may receive an access message including an establishment reason and identify that user equipment 302 is allowed to enter the RRC connection state to receive multicast services because the number of user equipments (UEs) residing on base station 304 is below a threshold. As another example, base station 304 may receive an access message including a recovery reason and identify that user equipment 302 is allowed to enter the RRC connection state to receive multicast services because user equipment 302 has temporarily lost connection and is attempting to restore connection. In some embodiments, when the access message includes a recovery reason, base station 304 may identify that user equipment 302 is allowed to enter the RRC connection state to receive multicast services regardless of whether the number of user equipments (UEs) residing on base station 304 is above a threshold.

[0107] In some embodiments, when base station 304 does not receive an access message (e.g., after a predetermined time), base station 304 can identify that user equipment 302 is prohibited from receiving access to one or more multicast services. Accordingly, base station 304 can send a response message indicating that user equipment 302 is not allowed to enter the RRC connection state based on the access message and receive one or more multicast services, and subsequently prohibit user equipment 302 from accessing one or more multicast services.

[0108] In operation 326, base station 304 may send an access rejection message to user equipment 302 based on the premise that user equipment 302 is not allowed to establish or restore RRC connection state to receive multicast services. This access rejection message indicates that the request to establish or restore RRC connection state to receive multicast services has been rejected. For example, when base station 304 is in an overloaded state, base station 304 may identify whether user equipment is allowed to enter RRC connection state to receive multicast services based on access messages. In such a case, if base station 304 rejects RRC connection setup due to base station overload, base station 304 may send an RRC rejection message to user equipment 302.

[0109] In some embodiments, base station 304 may, in response to at least one of an access message indicating that a user equipment (UE) is attempting to establish access to one or more multicast services or to restore access to one or more multicast services, prevent the UE from entering an RRC connected state to receive one or more multicast services. For example, base station 304 may receive an access message from UE 302 indicating that UE 302 is attempting to establish access to one or more multicast services for the first time or after a predetermined time. Base station 304 may recognize that it does not accept new UEs camped on base station 304 and receiving access to one or more multicast services. In response, base station 304 may prevent UE 302 from entering an RRC connected state to receive one or more multicast services through base station 304 because UE 302 is attempting to establish access to one or more multicast services for the first time or after a predetermined time.

[0110] In some embodiments, base station 304 may deny user equipment 302 access to an RRC connection state and allow it to receive one or more multicast broadcast services based on the type of multicast broadcast service sought by user equipment 302. For example, base station 304 may prioritize a first type of multicast broadcast service over a second type of multicast broadcast service. For example, when the service quality for the multicast broadcast service at base station 304 is relatively high, base station 304 may allow user equipment 302 to enter an RRC connection state to receive access to both the first and second types of multicast broadcast services. However, for example, when the service quality for the multicast broadcast service at base station 304 is relatively low, base station 304 may allow user equipment 302 to enter an RRC connection state to receive access to the first type of multicast broadcast service, but deny user equipment 302 access to the second type of multicast broadcast service.

[0111] In operation 328, user equipment 302 and base station 304 may exchange random access messages based on allowing user equipment 302 to establish or restore an RRC connection state to receive multicast services. For example, in response to receiving an access message, base station 304 may identify that one or more Quality of Service (QoS) parameters associated with one or more multicast services are relatively high, the number of one or more user equipments receiving access to one or more multicast services through the base station is less than a threshold number, or the data rate at which one or more user equipments access data through base station 304 is less than a threshold data rate. Accordingly, base station 304 may send a response message based on the access message to indicate that user equipment 302 is allowed to enter an RRC connection state to receive one or more multicast services, and subsequently allow user equipment 302 to access one or more multicast services. Base station 304 and user equipment 302 may exchange random access messages based on base station 304 allowing user equipment 302 to establish or restore an RRC connection state to receive multicast services.

[0112] As another example, base station 304 may receive an access message from user equipment 302 indicating that user equipment 302 is attempting to regain access to one or more multicast services after losing access for a relatively short period of time. Base station 304 may accept the restoration of user equipment's camp on base station 304 and the restoration of access to one or more multicast services. In response, base station 304 may allow user equipment 302 to enter an RRC connected state and receive one or more multicast services through base station 304, because user equipment 302 is attempting to regain access to one or more multicast services after losing access for a relatively short period of time. Base station 304 and user equipment 302 may exchange random access messages based on base station 304 allowing user equipment 302 to establish or restore an RRC connected state to receive multicast services.

[0113] It should be understood that, in addition to the content of this article... Figure 3 In addition to the processes described herein, system 300, including user equipment 302 and base station 304, may also implement any one or more of the processes described herein. For example, besides system 300 implementing the processes described herein... Figure 3 In addition to one or more processes described herein, system 300, including user equipment 302 and base station 304, can also implement the processes described herein. Figure 1 , 2 And any one or more processes described in any one or more diagrams in 6-10.

[0114] Figure 6 This is a block diagram conceptually illustrating an example hardware implementation of a base station 600 according to some aspects of this disclosure. In some examples, the base station 600 may be as follows: Figure 1-3And any one or more of the base stations shown in Figures 7-10.

[0115] The base station 600 can be implemented using a processing system 614 including one or more processors 604. Examples of processors 604 include microprocessors, microcontrollers, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuitry, and other suitable hardware configured to perform the various functions described herein. In various examples, the base station 600 can be configured to perform any one or more of the functions described herein. That is, the processor 604 utilized in the base station 600 can be used to implement... Figure 1-3 And any one or more of the processes and procedures described and shown in 7-10.

[0116] In this example, processing system 614 may be implemented using a bus architecture (typically represented by bus 602). Depending on the specific application and overall design constraints of processing system 614, bus 602 may include any number of interconnect buses and bridges. Bus 602 communicatively couples various circuits together, including one or more processors (typically represented by processor 604), memory 605, and computer-readable media (typically represented by computer-readable media 606). Bus 602 may also link various other circuits, such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further. Bus interface 608 provides an interface between bus 602 and transceiver 610. Transceiver 610 may provide a communication interface or unit for wireless communication with various other devices over a transmission medium. Depending on the attributes of the device, a user interface 612 (e.g., keypad, display, speaker, microphone, joystick) may also be provided.

[0117] In some aspects of this disclosure, processor 604 may include identification circuitry 640 configured to perform various functions, including, for example, identifying whether a group of user equipments (UEs) is permitted to select a base station cell for receiving multicast services. Alternatively or additionally, identification circuitry 640 may be configured to perform various functions, including, for example, identifying whether a set of one or more UEs in the group is permitted to establish or restore a Radio Resource Control (RRC) connection state with the base station to receive multicast services. Alternatively or additionally, identification circuitry 640 may be configured to perform various functions, including, for example, identifying whether a UE is permitted to establish or restore an RRC connection state to receive multicast services.

[0118] In some aspects of this disclosure, processor 604 may include broadcast circuitry 642 configured to perform various functions, including, for example, broadcasting one or more cell prohibition parameters to a group of user equipments (UEs), the one or more cell prohibition parameters indicating whether UEs in the group are permitted to select a cell of the base station for receiving multicast or broadcast services. Alternatively or additionally, broadcast circuitry 642 may be configured to perform various functions, including, for example, broadcasting one or more access control parameters to a set of one or more UEs in the group who are indicated, based on one or more cell prohibition parameters, as permitted to select a cell for receiving multicast or broadcast services, the one or more access control parameters indicating whether the set of one or more UEs is permitted to establish or restore Radio Resource Control (RRC) connectivity with the base station to receive multicast or broadcast services. Alternatively or additionally, broadcast circuitry 642 may be configured to perform various functions, including, for example, broadcasting one or more access control parameters in response to receiving an access request message.

[0119] In some aspects of this disclosure, processor 604 may include receiving circuitry 644 configured to perform various functions, including, for example, receiving access request messages from a set of one or more UEs requesting the establishment or restoration of an RRC connection state to receive multicast or broadcast services. In some aspects of this disclosure, processor 604 may include transmitting circuitry 646 configured to perform various functions, including, for example, sending an access rejection message to a set of one or more UEs indicating that the set of one or more UEs is not permitted to establish or restore an RRC connection state to receive multicast or broadcast services. In some embodiments, transmitting circuitry 646 may perform one or more functions of broadcast circuitry 642. In some aspects of this disclosure, processor 604 may include switching circuitry 648 configured to perform various functions, including, for example, exchanging random access messages with a set of one or more UEs when one or more access control parameters indicate that the set of one or more UEs is permitted to establish or restore an RRC connection state to receive multicast or broadcast services. In some embodiments, receiving circuitry 644 or transmitting circuitry 646 may perform one or more functions of switching circuitry 648.

[0120] Processor 604 can manage bus 602 and general-purpose processing, including the execution of software stored on computer-readable medium 606. When executed by processor 604, the software causes processing system 614 to perform the various functions described herein (including those related to…). Figure 1-3 (And those functions described in 7-10). The computer-readable medium 606 and the memory 605 can also be used to store data manipulated by the processor 604 when executing software.

[0121] One or more processors 604 in the processing system can execute software. Software, whether referred to as software, firmware, middleware, microcode, hardware description language, or other names, should be broadly interpreted as instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc. Software may reside on computer-readable medium 606. Computer-readable medium 606 may be a non-transitory computer-readable medium. For example, non-transitory computer-readable media include magnetic storage devices (e.g., hard disks, floppy disks, magnetic tapes), optical disks (e.g., compact discs (CDs) or digital versatile discs (DVDs)), smart cards, flash memory devices (e.g., cards, sticks, or key drives), random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), registers, removable disks, and any other suitable medium for storing software or instructions that can be accessed and read by a computer. The computer-readable medium 606 may be located within, outside, or distributed across multiple entities including the processing system 614. The computer-readable medium 606 may be embodied in a computer program product. For example, the computer program product may include the computer-readable medium within encapsulation material. Those skilled in the art will recognize how the functionality described herein is optimally implemented based on a particular application and the overall design constraints imposed on the system as a whole.

[0122] In one or more examples, the computer-readable storage medium 606 may include identification software or instructions 650, broadcasting software or instructions 652, receiving software or instructions 654, transmitting software or instructions 656, or exchanging software or instructions 658. Of course, in the examples provided herein, the circuitry included in the processor 604 is merely provided as an example, and other units for performing the described functions may be included within various aspects of this disclosure, including but not limited to instructions stored in the computer-readable storage medium 606, or in… Figure 1-3 and any other suitable means or units described in any of the figures 7-10, and utilizing, for example, the processes or algorithms described herein.

[0123] Figure 7 This is a flowchart illustrating an example method 700 for controlling multicast and broadcast access performed at a base station according to some aspects of this disclosure. In some examples, method 700 may be performed by any suitable means or unit for performing the functions or algorithms described herein.

[0124] At block 702, the base station may broadcast one or more cell prohibition parameters to a group of user equipment (UEs). These parameters indicate whether a UE in the group is permitted to select a cell from the base station for receiving multicast or broadcast services. This can be used by the base station to provide base station status. Multicast / broadcast services may be associated with one of the following: a specific public land mobile network (PLMN), or all public land mobile networks. In some embodiments, identifying whether the group of UEs is permitted to select a cell for receiving multicast / broadcast services includes identifying whether the base station supports multicast / broadcast services.

[0125] For example, a base station can be configured to allow a user device to camp on the base station or a cell to receive one or more multicast services. In some embodiments, the base station can be configured to allow a user device to camp on the base station to receive one or more multicast services based on whether the cellBarred-MBS field has an enable information element or a disable information element. For example, the base station may have a cellBarred-MBS field and a cellBarred field. The cellBarred-MBS field may have a disable information element, and the cellBarred field may also have a disable information element. In this case, the base station may not allow the user device to camp on the base station to receive access to one or more multicast services or one or more unicast services. In some embodiments, when the cellBarred field has a disable information element, the base station may not allow the user device to camp on the base station to receive one or more multicast services or one or more unicast services, regardless of whether the cellBarred-MBS field has an enable information element or a disable information element.

[0126] As another example, a base station may have a cellBarred-MBS field and a cellBarred field. The cellBarred-MBS field may contain disabled information elements, and the cellBarred field may contain enabled information. In this case, the base station may not be able to allow a user device to camp on the base station to receive one or more multicast services. However, the base station may be able to allow a user device to camp on the base station to receive one or more unicast services.

[0127] As another example, a base station may have a cellBarred-MBS field and a cellBarred field. The cellBarred-MBS field may have an enable information element, and the cellBarred field may also have an enable information element. In this case, the base station may be able to allow a user device to camp on the base station to receive one or more multicast broadcast services or one or more unicast services, or both.

[0128] As another example, base station 304 may have a prohibition information element for the cellBarred-MBS field and a false information element for the cellReservedForMBSUse field. In this case, via an SIB1 message or another SIB, base station 304 may provide the UE with indications of one or more other frequencies associated with the same cell in which multicast services are available, to assist the UE in finding multicast services in other frequencies. Alternatively, via an SIB1 message or another SIB, base station 304 may provide the UE with the identifiers and frequencies of different cells (e.g., neighboring cells) in which multicast services are available, to assist the UE in finding multicast services. In some embodiments, base station 304 may provide a UE in an RRC connected state with an RRC release message containing redirection information that redirects the UE in the RRC connected state to another cell to receive multicast services.

[0129] The `cellBarred` and `cellBarred-MBS` fields can be set independently by the base station or the network supporting the base station, or can be toggled between enabled and disabled information elements. In some embodiments, the `cellBarred-MBS` field may have enabled or disabled information elements based on the base station's capabilities. For example, the base station may not be configured to provide user equipment with access to any multicast services, and therefore, the `cellBarred-MBS` field may have a disabled information element. As another example, the base station may be configured to provide user equipment with access to all multicast services, and therefore, the `cellBarred-MBS` field may have an enabled information element.

[0130] In some embodiments, allowing a group of User Equipments (UEs) to select a base station's cell for receiving multicast services can cause the base station to configure or generate one or more cell prohibition parameters. In some embodiments, when (e.g., in response to) the base station allowing a group of UEs to select a base station's cell for receiving multicast services, the base station can configure or generate one or more cell prohibition parameters. For example, when (e.g., in response to) the base station being configured to allow a user equipment to camp on a base station or cell to receive one or more multicast services, the base station can configure or generate one or more cell prohibition parameters. One or more cell prohibition parameters can be sent to the user equipment via System Information Block (SIB) messages (e.g., SIB Type 1 (SIB1) messages) or Master Information Block (MIB). One or more cell prohibition parameters enable the user equipment to identify whether the user equipment is allowed to camp on a base station or cell to receive one or more multicast services.

[0131] In some embodiments, the base station may send or broadcast one or more cell prohibition parameters to the group of UEs, including the UE, based on whether the group of UEs is allowed to select a cell for receiving multicast services. In some embodiments, as described herein, the base station may have configured or generated one or more cell prohibition parameters when (e.g., in response to) the base station being configured to allow a user equipment to camp on the base station or a cell to receive one or more multicast services. One or more prohibition parameters may be sent to the user equipment via System Information Block Type 1 (SIB1) or Master Information Block (MIB) messages, enabling the user equipment to identify whether it is allowed to camp on the base station or a cell to receive one or more multicast services.

[0132] For example, a base station can rely on the cellBarred-MBS / cellReservedMBSUse information element to identify that the base station is configured to provide access to one or more multicast services. The base station can send one or more configured cell prohibition parameters to the user equipment as an indication to the user equipment that the base station is configured to provide the user equipment with access to one or more multicast services.

[0133] At block 704, the base station may broadcast one or more access control parameters to a set of one or more UEs in the group that are indicated as permitted to select a cell for receiving multicast or broadcast services based on one or more cell prohibition parameters. The one or more access control parameters indicate whether the set of one or more UEs is permitted to establish or restore a Radio Resource Control (RRC) connection state with the base station to receive multicast or broadcast services. For example, the base station may determine whether to permit the set of one or more UEs to establish or restore an RRC connection state with the base station to receive multicast or broadcast services based on an overload condition at the base station and a received RRC establishment reason or a received RRC restoration reason. In some embodiments, the base station may determine whether to permit the set of one or more UEs in the group to establish or restore a RRC connection state with the base station to receive multicast or broadcast services based on permitting the group of UEs to receive multicast or broadcast services in an RRC connection state. In some embodiments, permitting the group of UEs to receive multicast or broadcast services may be based on an overload condition at the base station.

[0134] In some embodiments, when a base station is configured to provide access to one or more multicast services for a user equipment (UE) in a Radio Resource Control (RRC) connection state, the base station may have configured or generated one or more access control parameters. In some embodiments, when a base station allows a group of UEs to establish or resume RRC connections, the base station may have configured or generated one or more access control parameters. These access control parameters may include one or more access class values, and each access class may be configured with a prohibition factor and a prohibition timer. One or more access control parameters may be sent to the UE via a System Information Block Type 1 (SIB1) message to enable the UE to identify whether it is prohibited from sending access attempts (e.g., access messages) for connection setup to receive one or more multicast services. In some embodiments, one or more access control parameters are associated with all multicast services or one or more specific multicast services.

[0135] Each of one or more cell prohibition factors and each of one or more cell prohibition times may be associated with at least one access class value described herein. Cell prohibition parameters enable a user equipment (UE) to identify whether it is permitted to camp on a base station or cell to receive one or more multicast services. A cell prohibition factor may be a number generated by the base station that is not less than zero (0) and not greater than one (1) (e.g., 0.4, 0.6, 0.8). A cell prohibition time may be a specified amount of time between instances when the UE generates a random number to be compared with the cell prohibition factor described herein, or a time provided by the base station. A base station may include cell prohibition factors and cell prohibition times to maintain or limit the number of UEs that can camp on the base station to receive one or more multicast services (e.g., maintain or limit them below a threshold). Alternatively or concurrently, a base station may include cell prohibition factors and cell prohibition times to maintain or limit the data rate at which data is transmitted through the base station (e.g., maintain or limit it below a threshold).

[0136] A base station may configure or generate one or more cell prohibition factors and one or more cell prohibition times based on at least one of the following: one or more Quality of Service (QoS) parameters associated with one or more multicast services, the number of one or more user equipments receiving access to one or more multicast services through the base station, or the data rate at which one or more user equipments access data through the base station. For example, the base station may generate an access class value associated with all multicast services, as described herein. The base station may also identify that the number of user equipments camped on the base station exceeds a threshold number. The base station may configure the cell prohibition factor associated with all multicast services to a relatively low value (e.g., 0.1, 0.3) to provide user equipments with a low chance of receiving access to all multicast services and a high chance of being prohibited. In some embodiments, the base station may configure the cell prohibition factor to a value of zero, thereby denying user equipment the opportunity to access the multicast services associated with the access class value. Alternatively or additionally, the base station may configure the cell prohibition time associated with all multicast services to a relatively long time period between instances when user equipment generates a random number for comparison with the cell prohibition factor described herein. By giving user equipment a high chance of being banned and a long amount of time between generating random numbers, the base station is given time to allow other user equipment to leave the base station and reduce the number of user equipment camped on the base station to below a threshold.

[0137] In some embodiments, when a base station is configured to provide access to one or more multicast services to a user equipment (UE) in a Radio Resource Control (RRC) connection state, the base station may configure or generate one or more access control parameters. Subsequently, the base station may configure or generate one or more access control parameters including one or more access class values, and each access class may be configured with a prohibition factor and a prohibition timer. One or more access control parameters may be sent to the UE via a System Information Block Type 1 (SIB1) message. The one or more access control parameters enable the UE to identify whether it is prohibited from sending access attempts (e.g., access messages) for connection setup to receive one or more multicast services.

[0138] Upon receiving access control parameters for the access class, and when a user equipment (UE) establishes or restores a radio resource control (RRC) connection to receive multicast services in the RRC connection state, the UE can determine whether to send an access attempt based on access class parameters (e.g., a prohibition factor and prohibition time for the access class). As part of a prohibition test for a given access class, the UE can generate a random number not less than or greater than the access class prohibition factor. Subsequently, the UE can determine that it is not permitted to send access attempts to establish or restore an RRC connection to receive one or more multicast services from the base station. When the UE determines, based on a comparison between the generated random value and the cell prohibition factor, that it is not permitted to send access attempts associated with the access class to establish or restore an RRC connection to receive one or more multicast services from the base station, a timer is started by the UE. While the timer for that access class is running, the UE may be prohibited from initiating access attempts for the same access class. After the timer expires, if the UE seeks to access the cell for the same access class, it may be allowed to repeat the prohibition test for the same access type. If the subsequently generated random number is less than the cell prohibition factor, the user equipment may be allowed to send an access attempt to the base station or cell to receive one or more multicast services from the base station, and the process stops. Otherwise, the user equipment may restart the timer and generate another random number according to the cell prohibition timer. This process may be repeated until the user equipment generates a random number less than the cell prohibition factor, indicating that the user equipment is permitted to send an access attempt to the base station or cell to receive one or more multicast services from the base station in Radio Resource Control (RRC) connected state.

[0139] A base station can generate one or more cell prohibition factors and one or more cell prohibition times based on at least one of the following: one or more Quality of Service (QoS) parameters associated with one or more multicast services, the number of one or more UEs receiving access to one or more multicast services through the base station, or the data rate at which one or more UEs access data through the base station. For example, the base station can generate an access class value associated with all multicast services. The base station can also identify that the number of user equipments that can establish radio resource control connections to the base station is higher than a threshold number. The base station can configure the cell prohibition factor associated with all multicast services to a relatively low value (e.g., 0.1, 0.3) to provide user equipments with a low chance of receiving access to all multicast services and a high chance of being prohibited. In some embodiments, the base station can configure the cell prohibition factor to a value of zero, thereby denying user equipment the opportunity to access multicast services. Furthermore, the base station can configure the cell prohibition time associated with all multicast services to a relatively long time period. This can extend the amount of time between instances when a user equipment generates a random number to a relatively long time period. By giving user equipment a high chance of being banned and a long amount of time between generating random numbers, time can be given to the base station to allow other user equipment to disconnect from the base station and reduce the number of user equipment establishing or resuming RRC connections to the base station to below a threshold number.

[0140] As another example, the base station can also identify whether the Quality of Service (QoS) associated with all multicast services is relatively high or strong. The base station can configure a cell prohibition factor associated with all multicast services to a relatively high value (e.g., 0.7, 0.9) to provide user equipment with a high chance of receiving access to all multicast services and a low chance of being prohibited. In some embodiments, the base station can configure an access class value of one (1) to grant user equipment access to the multicast services associated with the access class value. In some embodiments, when the access class prohibition factor is zero, user equipment can have access to the multicast services. Furthermore, the base station can configure the cell prohibition time associated with all multicast services to a relatively short time period. This allows the amount of time between instances when a user equipment generates a random number to be extended to a relatively short time period. By giving user equipment a low chance of being prohibited and a short amount of time between generating random numbers, the base station can provide user equipment with a rapid opportunity to receive access to the multicast services through the base station and increase the number of user equipment connected to the base station (e.g., to establish a radio resource control connection with the base station) to receive high QoS.

[0141] After the access control check, if a user equipment is allowed to send an access attempt to establish or restore a Radio Resource Control (RRC) connection, the user equipment can initiate a Random Access (RACH) procedure. During the RACH procedure, message 3 or message A may carry a RRC setup request message or a RRC recovery request message. The RRC setup request message may include a reason for establishing a multicast service, or the RRC recovery request message may include a reason for recovering a multicast service. Upon receiving message 3 or message A containing the reason for establishment / recovery = multicast service, the base station may reject the connection setup or allow the connection setup / recovery procedure based on overload conditions. If the base station rejects the RRC connection setup or RRC recovery procedure, the base station may send a RRC rejection message including a wait timer. In some embodiments, while the wait timer is running, the user equipment may be prevented from establishing or restoring a RRC connection. When the wait time expires, the user equipment may be allowed to initiate an access attempt again, and the above procedure may be repeated.

[0142] Figure 4 Table 400 illustrates an example mapping of access identity values ​​to prohibition parameters for controlling multicast and broadcast access, according to some aspects of this disclosure. Figure 4 As shown, Table 400 includes multiple access identity values, and each access identity value is used to specify the device type based on device configuration. Each of the multiple access identity values ​​can be a numerical value starting with zero (e.g., an integer value). As part of the unified access control parameters in SIB1, each access identity can be prohibited or not prohibited by setting the associated access prohibition bit (e.g., "1" for prohibition, "0" for not prohibition). The UE may seek to send an access attempt to the base station. The UE can verify whether the access attempt associated with the access identity is prohibited or not based on the prohibition bit value received for the access identity.

[0143] As described herein, each of a plurality of access identity values ​​can be mapped to a user equipment configuration. As an example, a user equipment associated with access identity value one (1) can be configured for Multimedia Priority Service (MPS). As another example, a user equipment associated with access identity value two (2) can be configured for Mission Critical Service (MCS).

[0144] One or more access class values ​​may include one or more access class values ​​associated with a service. An access class value may be a value indicating what an access message is requesting. For example, an access class value may indicate that a user equipment is requesting access for: paging service, emergency call service, multimedia telephony (MMTEL) voice session service, MMTEL video session service, real-time text service, IP multimedia subsystem (IMS) messaging service, short message service (SMS), etc. The access class value provides an indication of what the user equipment is doing or wants to do. In some embodiments, the access class value may be a standard value or a carrier-specified value. The NAS may provide a radio resource establishment reason to be used for services initiated by the NAS. For connections initiated by radio resource control, radio resource control may identify what the radio resource control establishment reason is. NAS TS 24.501, Table 4.5.2.2 may specify one or more mapping tables for access class and radio resource control establishment terms.

[0145] Figure 5 Table 500 illustrates an example mapping of access category values ​​to prohibition parameters for controlling multicast and broadcast access, according to some aspects of this disclosure. Figure 5 As shown, Table 500 includes multiple access category values, multiple conditions associated with the user equipment, and multiple access attempt types. Each access category value can be a numeric value starting with zero (e.g., an integer value). The numeric value can be a standard value or a value specified by the operator. The multiple conditions associated with the user equipment can be conditions related to the user equipment associated with the access category value. The multiple access attempt types can relate to the type of service the user equipment is seeking to receive access to.

[0146] Each of the multiple access category values ​​can be mapped to conditions and access attempt types associated with the user equipment. As an example, for access category value one (1), the conditions associated with the user equipment providing that access category value include: "The UE is configured for delay-tolerant service and is subject to access control for access category 1, which is determined based on the relationship between the UE's home public land mobile network (HPLMN) and the selected public land mobile network." As another example, for access category value three (3), the conditions associated with the user equipment providing that access category value include all conditions except those for access category value one (1).

[0147] Each of the multiple access category values ​​can be mapped to an access attempt type. As an example, for access category value one (1), the access attempt type can indicate that the associated user equipment includes all access attempt types except for emergency services or mobile-initiated (MO) anomalous data. As another example, for access category value three (3), the access attempt type can indicate that the associated user equipment includes access attempts associated with mobile-initiated signaling at the non-access stratum (NAS) level arising from services other than paging services.

[0148] In some embodiments, each of the multiple access category values ​​can be mapped to additional information, such as annotations indicating one or more other parameters. As an example, for access category value one (1), one or more other parameters may indicate that, for access category 1, this is accompanied by information defining whether the access category is applicable to user equipment having one of the following categories: (a) user equipment configured for delay-tolerant services; (b) user equipment configured for delay-tolerant services and neither in its home public land mobile network nor in a public land mobile network equivalent to it; (c) user equipment configured for delay-tolerant services and neither in the public land mobile network of the country in which the user equipment is roaming, listed in the operator-defined public land mobile network selector list on the SIM / USIM, nor in a home public land mobile network equivalent to its home public land mobile network. When the user equipment is configured for EAB, it is also configured for delay-tolerant services. In the case of both user equipment being configured for EAB and EAB overriding, access category 1 is not applicable when the upper layer indicates overriding access category 1. As another example, for access category value three (3), the prohibition parameter can indicate that the associated user equipment is prohibited from accessing signaling initiated by a mobile terminal at the non-access stratum (NAS) level from services other than paging services.

[0149] As an example, for access category values ​​32-63, one or more other parameters can indicate: when both carrier-based access category and standard access (access attempts can be classified as either) exist and the standard access category is neither 0 nor 2, the user equipment applies the carrier-based access category. When both carrier-based access category and standard access category (access attempts can be classified as either) exist and the standard access category is 0 or 2, the user equipment can apply the standard access category.

[0150] As another example, for an access attempt type associated with access category value four (4), a multimedia telephony (MMTEL) voice session service may include a real-time text (RTT) service. As yet another example, for an access attempt type associated with access category value seven (7), MO data that does not belong to any other access category may include IP multimedia subsystem messaging. As yet another example, for an access attempt type associated with access category value nine (9), MO IP multimedia subsystem registration associated with signaling that may include data that does not belong to any other access category may include signaling-related IP multimedia subsystem registration (such as initial registration, re-registration, and subscription refresh for IP multimedia subsystem messaging). As an example, for access category value ten (10), one or more other parameters may indicate that category ten is applicable to Node B of the Internet of Things (IoT) using Node B IoT connections to 5GC.

[0151] As described herein, one or more access control parameters may include one or more access category values ​​associated with one or more multicast services. When a base station sends one or more access category access control parameter values ​​associated with one or more multicast services, a user equipment (UE) may receive those access category access control parameter values ​​and identify whether the UE is prohibited from sending access messages (e.g., access attempts) for connection setup to request one or more multicast services associated with the received access category value. For example, the UE may receive from the base station an access category value indicating a video streaming multicast service. The UE may match the received access category value with an access category value associated with the video streaming multicast service that the UE seeks to receive, and based on the match, identify that the UE is not prohibited by the base station from sending access messages for requesting connection setup to access the video streaming multicast service. As discussed herein, the UE may then send an access message (e.g., an access attempt for connection setup) to the base station to request the video streaming multicast service from the base station based on one or more received access category parameters. In some embodiments, when the base station does not include an access class value that matches the access class value associated with the multicast service to which the user equipment (UE) is seeking access, the UE can recognize that the base station is preventing the UE from sending access messages for connection setup and receiving multicast services, and that the unified access control mechanism has ended. In some embodiments, one or more access class values ​​are used to identify all multicast services or one or more specific multicast services (e.g., video streaming multicast services). In some aspects, the base station may broadcast one or more access control parameters to a group of UEs based on whether to allow the UE group to establish or restore its RRC connection state with the base station to receive multicast services.

[0152] At box 706, the base station can receive an access request message from one or more UEs in a set of UEs for requesting to establish or restore an RRC connection state to receive multicast or broadcast services. In some aspects, the base station can receive the access request message from one or more UEs in a set of UEs for requesting to establish or restore an RRC connection state to receive multicast or broadcast services, and broadcast one or more access control parameters in response to receiving the access request message. In some aspects, the base station can allow a UE to establish or restore an RRC connection state to receive multicast or broadcast services. For example, the base station can receive the access request message from a user equipment in a set of UEs for requesting to establish or restore an RRC connection state to receive multicast or broadcast services. After receiving the access request message, the base station can determine whether to allow the user equipment to establish or restore an RRC connection state to receive multicast or broadcast services.

[0153] In some embodiments, determining whether a set of UEs in a group is allowed to establish or resume an RRC connection state with the base station to receive multicast services can be based on overload conditions at the base station. For example, the base station can receive access messages and determine whether a user equipment is allowed to enter an RRC connection state to receive multicast services. The base station can determine that a user equipment is not allowed to enter an RRC connection state when too many user equipments (UEs) are camped on the base station's cell, when too much data (e.g., data rates above a threshold data rate) is passing through the base station and being transmitted with user equipments (UEs), or when the quality of service (QoS) at the base station is below a threshold QoS.

[0154] As another example, the base station's receipt of an access message can trigger the base station to evaluate one or more Quality of Service (QoS) parameters associated with one or more multicast services, compare the number of one or more user equipments (UEs) receiving access to one or more multicast services through the base station with a threshold number (overload condition), or compare the data rate of one or more UEs accessing data through the base station with a threshold data rate (overload condition) to identify whether a UE is prohibited from entering the RRC connected state to access one or more multicast services through the base station. In some embodiments, in response to receiving the access message, the base station can identify that one or more QoS parameters associated with one or more multicast services are relatively low, the number of one or more UEs receiving access to one or more multicast services through the base station is higher than the threshold number, or the data rate of one or more UEs accessing data through the base station is higher than the threshold data rate. Therefore, the base station can send a response message based on the access message to indicate that the UE is denied entry into the RRC connected state to receive one or more multicast services, and subsequently prohibit the UE from accessing one or more multicast services.

[0155] In some embodiments, identifying whether a set of UEs in a group is allowed to establish or restore an RRC connection state with the base station to receive multicast services can be based on a received RRC establishment reason or a received RRC recovery reason included in the access message. For example, the base station may receive an access message including an establishment reason and identify that a user equipment is allowed to enter an RRC connection state to receive multicast services because the number of user equipments (UEs) camped on the base station is below a threshold. As another example, the base station may receive an access message including a recovery reason and identify that a user equipment is allowed to enter an RRC connection state to receive multicast services because the user equipment has temporarily lost connection and is attempting to restore connection. In some embodiments, when the access message includes a recovery reason, the base station may identify that a user equipment is allowed to enter an RRC connection state to receive multicast services regardless of whether the number of user equipments (UEs) camped on the base station is above a threshold.

[0156] In some embodiments, when the base station does not receive an access message (e.g., after a predetermined time), the base station can identify that the user equipment is prohibited from receiving access to one or more multicast services. Accordingly, the base station can send a response message indicating that the user equipment is not allowed to enter the RRC connection state based on the access message and receive one or more multicast services, and subsequently prohibit the user equipment from accessing one or more multicast services.

[0157] At box 708, the base station can send an access rejection message to a set of one or more UEs, indicating that the set of one or more UEs is not permitted to establish or resume an RRC connection state to receive multicast or broadcast services. For example, when the base station is in an overloaded state, the base station can identify whether a user equipment is permitted to enter an RRC connection state to receive multicast or broadcast services based on access messages. In this case, if the base station rejects RRC connection setup due to base station overload, the base station can send an RRC rejection message to the user equipment.

[0158] In some embodiments, a base station may, in response to at least one of an access message indicating that a user equipment (UE) is attempting to establish access to one or more multicast services or to restore access to one or more multicast services, prevent a UE from entering an RRC connected state to receive one or more multicast services. For example, the base station may receive an access message from the UE indicating that the UE is attempting to establish access to one or more multicast services for the first time or after a predetermined time. The base station may refuse to accept new UEs camped on the base station and receiving access to one or more multicast services. In response, the base station may prevent a UE from entering an RRC connected state to receive one or more multicast services through the base station because the UE is attempting to establish access to one or more multicast services for the first time or after a predetermined time.

[0159] In some embodiments, a base station may prevent a user equipment (UE) from entering an RRC connection state and receiving one or more multicast broadcast services based on the type of multicast broadcast service sought by the UE. For example, the base station may prioritize a first type of multicast broadcast service over a second type. For instance, when the service quality for a multicast broadcast service is relatively high at the base station, the base station may allow the UE to enter an RRC connection state to receive access to both the first and second types of multicast broadcast services. However, for example, when the service quality for a multicast broadcast service is relatively low at the base station, the base station may allow the UE to enter an RRC connection state to receive access to the first type of multicast broadcast service but prevent the UE from entering an RRC connection state to receive access to the second type of multicast broadcast service.

[0160] At box 710, when one or more access control parameters indicate that a set of one or more UEs is permitted to establish or restore an RRC connection state to receive multicast or broadcast services, the base station may exchange random access messages with the set of one or more UEs. For example, in response to receiving an access message, the base station may identify that one or more Quality of Service (QoS) parameters associated with one or more multicast / broadcast services are relatively high, the number of one or more user equipments receiving access to one or more multicast / broadcast services through the base station is below a threshold number, or the data rate at which one or more user equipments access data through the base station is below a threshold data rate. Accordingly, the base station may, based on the access message, send a response message indicating that the user equipment is permitted to enter an RRC connection state to receive one or more multicast / broadcast services, and subsequently allow the user equipment to access one or more multicast / broadcast services. The base station and the user equipment may exchange random access messages based on the base station allowing the user equipment to establish or restore an RRC connection state to receive multicast / broadcast services.

[0161] As another example, a base station can receive an access message from a user equipment (UE) indicating that the UE is attempting to regain access to one or more multicast services after losing access for a relatively short period. The base station can accept the UE's request to remain on the base station and regain access to one or more multicast services. In response, the base station can allow the UE to enter an RRC connected state and receive one or more multicast services through the base station, since the UE is attempting to regain access to one or more multicast services after losing access for a relatively short period. The base station and the UE can exchange random access messages based on the base station allowing the UE to establish or restore an RRC connected state to receive multicast services.

[0162] Figure 8 This is a conceptual diagram illustrating an example hardware implementation of an example user equipment (UE) 800 according to some aspects of this disclosure. For example, the user equipment 800 may perform... Figure 1-3 Any functions shown and described in 6, 7, 9 and 10.

[0163] User equipment 800 can be implemented using a processing system 814 including one or more processors 804. Examples of processors 804 include microprocessors, microcontrollers, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuitry, and other suitable hardware configured to perform the various functions described herein. In various examples, user equipment 800 can be configured to perform any one or more of the functions described herein. That is, the processor 804 utilized in user equipment 800 can be used to implement... Figure 1-3 Any one or more of the processes and procedures described in 6, 7, 9 and 10 and further illustrated in the flowcharts discussed herein.

[0164] In this example, processing system 814 can be implemented using a bus architecture (typically represented by bus 802). Depending on the specific application and overall design constraints of processing system 814, bus 802 may include any number of interconnect buses and bridges. Bus 802 communicatively couples various circuits together, including one or more processors (typically represented by processor 804), memory 805, and computer-readable media (typically represented by computer-readable media 806). Bus 802 may also link various other circuits, such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and will not be described further. Bus interface 808 provides an interface between bus 802 and transceiver 810. Transceiver 810 can provide a communication interface or unit for wireless communication with various other devices over a transmission medium. Depending on the properties of the device, a user interface 812 (e.g., keypad, display, speaker, microphone, joystick) may also be provided.

[0165] In some aspects of this disclosure, processor 804 may include receiver circuitry 840 configured for various functions, including, for example, receiving one or more cell prohibition parameters from a base station, the one or more cell prohibition parameters indicating whether the UE is permitted to select a cell of the base station for receiving multicast or broadcast services. Receiver circuitry 840 may also be configured for various functions, including, for example, receiving one or more access control parameters from the base station based on one or more cell prohibition parameters indicating that the UE is permitted to select a cell of the base station for receiving multicast or broadcast services, the one or more access control parameters indicating whether the UE is permitted to establish or restore a Radio Resource Control (RRC) connection state with the base station to receive multicast or broadcast services. Receiver circuitry 840 may also be configured for various functions, including, for example, receiving from the base station an access rejection message indicating that the UE is not permitted to establish or restore an RRC connection state to receive multicast or broadcast services.

[0166] In some aspects of this disclosure, processor 804 may include identification circuitry 842 configured for various functions, including, for example, identifying whether a UE is permitted to camp on a base station cell to receive multicast services based on one or more cell prohibition parameters. Identification circuitry 842 may also be configured for various functions, including, for example, identifying whether a UE is prohibited from sending access request messages to establish or restore RRC connection states to receive multicast services based on one or more access control parameters.

[0167] In some aspects of this disclosure, processor 804 may include transmitting circuitry 844 configured for various functions, including, for example, transmitting access request messages based on one or more access control parameters to establish or restore an RRC connection state with a base station to receive multicast or broadcast services. In some aspects of this disclosure, processor 804 may include switching circuitry 846 configured for various functions, including, for example, instructing a UE to establish or restore an RRC connection state to receive multicast or broadcast services based on one or more access control parameters to exchange random access messages with a base station. In some embodiments, receiving circuitry 840 or transmitting circuitry 842 may be configured to perform one or more functions of switching circuitry 846.

[0168] Processor 804 is responsible for managing bus 802 and general-purpose processing, including the execution of software stored on computer-readable medium 806. When executed by processor 804, the software causes processing system 814 to perform various functions described below for any particular device. Computer-readable medium 806 and memory 805 may also be used to store data manipulated by processor 804 during software execution.

[0169] One or more processors 804 in the processing system can execute software. Software, whether referred to as software, firmware, middleware, microcode, hardware description language, or other names, should be broadly interpreted as instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc. Software may reside on a computer-readable medium 806. The computer-readable medium 806 may be a non-transitory computer-readable medium. For example, non-transitory computer-readable media include magnetic storage devices (e.g., hard disks, floppy disks, magnetic tapes), optical disks (e.g., compact discs (CDs) or digital versatile discs (DVDs)), smart cards, flash memory devices (e.g., cards, sticks, or key drives), random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), registers, removable disks, and any other suitable medium for storing software or instructions that can be accessed and read by a computer. The computer-readable medium 806 may be located within, outside, or distributed across multiple entities including the processing system 814. The computer-readable medium 806 may be embodied in a computer program product. For example, the computer program product may include the computer-readable medium within encapsulation material. Those skilled in the art will recognize how the functionality described herein is optimally implemented based on a particular application and the overall design constraints imposed on the system as a whole.

[0170] In one or more examples, the computer-readable storage medium 806 may include receiving software or instructions 850, identification software or instructions 852, transmitting software or instructions 854, or exchanging software or instructions 856. Of course, in the above examples, the circuitry included in the processor 804 is provided merely as an example, and other units for performing the described functions may be included within various aspects of this disclosure, including but not limited to instructions stored in the computer-readable storage medium 806, or in… Figure 1-3 The apparatus or unit described in any of the figures 6, 7, 9 and 10, and any other suitable means or units that utilize, for example, the processes or algorithms described herein.

[0171] Figure 9 This is a flowchart illustrating an example method 900 for controlling multicast and broadcast access performed at a UE according to some aspects of this disclosure. In some examples, method 900 may be performed by any suitable means or unit for performing the functions or algorithms described herein.

[0172] At block 902, a user equipment (UE) can receive one or more cell prohibition parameters from a base station based on whether the UE is allowed to select a cell for receiving multicast services. For example, the base station can identify whether it is configured to allow a user equipment to camp on the base station or a cell to receive one or more multicast services. In some embodiments, the base station can identify whether it is configured to allow a user equipment to camp on the base station to receive one or more multicast services based on whether the cellBarred-MBS field has an enable information element or a disable information element. For example, the base station may have a cellBarred-MBS field and a cellBarred field. The cellBarred-MBS field may have a disable information element, and the cellBarred field may also have a disable information element. In this case, the base station may prevent the user equipment from camping on the base station to receive access to one or more multicast services or one or more unicast services. In some embodiments, when the cellBarred field has a disable information element, the base station may prevent the user equipment from camping on the base station to receive one or more multicast services or one or more unicast services regardless of whether the cellBarred-MBS field has an enable information element or a disable information element.

[0173] As another example, a base station may have a cellBarred-MBS field and a cellBarred field. The cellBarred-MBS field may contain disabled information elements, and the cellBarred field may contain enabled information. In this case, the base station may not be able to allow a user device to camp on the base station to receive one or more multicast services. However, the base station may be able to allow a user device to camp on the base station to receive one or more unicast services.

[0174] As another example, a base station may have a cellBarred-MBS field and a cellBarred field. The cellBarred-MBS field may have an enable information element, and the cellBarred field may also have an enable information element. In this case, the base station may be able to allow a user device to camp on the base station to receive one or more multicast broadcast services or one or more unicast services, or both.

[0175] As another example, base station 304 may have a prohibition information element for the cellBarred-MBS field and a false information element for the cellReservedForMBSUse field. In this case, via an SIB1 message or another SIB, base station 304 may provide the UE with indications of one or more other frequencies associated with the same cell in which multicast services are available, to assist the UE in finding multicast services in other frequencies. Alternatively, via an SIB1 message or another SIB, base station 304 may provide the UE with the identifiers and frequencies of different cells (e.g., neighboring cells) in which multicast services are available, to assist the UE in finding multicast services. In some embodiments, base station 304 may provide a UE in an RRC connected state with an RRC release message containing redirection information that redirects the UE in the RRC connected state to another cell to receive multicast services.

[0176] The `cellBarred` and `cellBarred-MBS` fields can be set independently by the base station or the network supporting the base station, or can be toggled between enabled and disabled information elements. In some embodiments, the `cellBarred-MBS` field may have enabled or disabled information elements based on the base station's capabilities. For example, the base station may not be configured to provide user equipment with access to any multicast services, and therefore, the `cellBarred-MBS` field may have a disabled information element. As another example, the base station may be configured to provide user equipment with access to all multicast services, and therefore, the `cellBarred-MBS` field may have an enabled information element.

[0177] In some embodiments, the base station may have configured or generated one or more cell prohibition parameters. In some embodiments, the base station may have configured or generated one or more cell prohibition parameters when (e.g., in response to) allowing a group of UEs to select a cell for receiving multicast services. For example, the base station may have configured or generated one or more cell prohibition parameters when (e.g., in response to) allowing a user equipment to camp on the base station or a cell to receive one or more multicast services. One or more cell prohibition parameters may be sent to the user equipment via System Information Block (SIB) messages (e.g., SIB Type 1 (SIB1) messages) or Master Information Block (MIB). One or more cell prohibition parameters enable the user equipment to identify whether it is permitted to camp on the base station or a cell to receive one or more multicast services.

[0178] Subsequently, the base station may have sent or broadcast one or more cell prohibition parameters to the group of UEs, including the UE, for receiving multicast services. In some embodiments, the base station may have sent or broadcast one or more cell prohibition parameters to the group of UEs based on whether the group of UEs, including the UE, is allowed to select a cell for receiving multicast services. In some embodiments, as described herein, when (e.g., in response to) the base station being configured to allow a user equipment to camp on the base station or cell to receive one or more multicast services, the base station may have configured or generated one or more cell prohibition parameters. One or more prohibition parameters may be sent to the user equipment via System Information Block Type 1 (SIB1) or Master Information Block (MIB) messages to enable the user equipment to be allowed to camp on the base station or cell to receive one or more multicast services.

[0179] For example, a base station can rely on the cellBarred-MBS / cellReservedMBSUse information element to identify that the base station is configured to provide access to one or more multicast services. The base station can send one or more configured cell prohibition parameters to the user equipment as an indication to the user equipment that the base station is configured to provide the user equipment with access to one or more multicast services.

[0180] In some aspects, a user equipment (UE) can identify whether it is permitted to camp on a base station's cell to receive multicast services based on one or more cell prohibition parameters. For example, a UE can receive one or more cell prohibition parameters from a base station based on whether a group of UEs, including the UE, is permitted to select a cell of the base station for receiving multicast services. After receiving one or more cell prohibition parameters, the UE can identify whether it is permitted to camp on a base station's cell to receive multicast services.

[0181] When a user equipment (UE) receives one or more cell-barred-MBS or cell-reserved-MBSUse cell-barred parameter information elements, and if these information elements indicate that multicast services are disabled, the UE will not camp on the cell to receive multicast services. If these information elements indicate that the cell is not disabled for multicast services, the UE may camp on the cell to receive multicast services.

[0182] For example, a base station may transmit a `cellReservedMBSUse` field to a user equipment (UE) in a System Information Block Type 1 (SIB1) message. The `cellReservedMBSUse` field indicates whether the UE is prohibited from camping on the cell to access one or more multicast services. The `cellReservedMBSUse` field may have an enable information element or a true information element to indicate to the UE that it may be allowed to camp on the cell to receive access to one or more multicast services through the base station. The `cellReservedMBSUse` field may also have a disable information element, a false information element, or a non-true information element to indicate to the UE that it may be prohibited from camping on the cell to receive one or more multicast services through the base station.

[0183] As another example, a base station may transmit a CellReservedforMBSUse field and a cellBarred field to a user equipment (UE) in a System Information Block Type 1 (SIB1) message. The CellReservedforMBSUse field indicates whether the UE is prohibited from camping on the cell to receive one or more multicast services, and the cellBarred field indicates whether the UE is prohibited from camping on the cell to receive unicast services (e.g., one or more unicast services) from the cell via the base station. In some embodiments, the CellReservedforMBSUse field may have an enable information element or a true information element, and the cellBarred field may have a non-prohibit information element. Together, these elements indicate to the UE that the UE is allowed to camp on the cell to receive unicast services from the cell, but is not allowed to receive any multicast services from the cell. In this case, when the UE receives one or more indications, the UE may not camp on the base station but instead search for another base station to receive one or more multicast services. In some embodiments, the CellReservedforMBSUse field may have a disabled information element or a false information element, and the cellBarred field may have a non-prohibited information element, indicating to the user equipment that the user equipment can be allowed to camp on the cell to receive both unicast and multicast services from the base station. In some embodiments, the CellReservedforMBSUse field may have an enabled information element or a true information element, and the cellBarred field may have a prohibited information element, indicating to the user equipment that the user equipment can be allowed to camp on the cell to receive only multicast services and the UE is not allowed to receive any type of unicast service from the base station. In this case, a UE intending to receive only multicast services from the base station can camp on the cell, and a UE intending to receive unicast services can not camp on the cell but can search for other cells. The CellReservedforMBSUse field may belong to a specific Public Land Mobile Network (PLMN) among multiple Public Land Mobile Networks, or the CellReservedforMBSUse field may belong to all Public Land Mobile Networks.

[0184] Base stations can use system information messages to provide a list of multicast services available in the serving cell. Multicast service information at the frequency level can be provided for the serving cell and for other neighboring cells in the same or different frequencies. The presence or absence of this new system information block can be indicated in SIB1. User equipment can interpret the presence or absence of new SIB scheduling information in SIB1 as an implicit indication of whether the cell supports or does not support any multicast services in that cell, and the user equipment can identify whether it is camped on that cell.

[0185] To control access overload, base stations can use a unified access control mechanism. One or more access control parameters may include one or more access category parameters associated with one or more services. Access category parameters can be used in the unified access control mechanism at the user equipment. Typically, during the unified access control mechanism, the user equipment can receive at least one of the following from the base station: one or more access category parameters and one or more access identity parameters. One or more access identity parameters may include an access identity value associated with the user equipment. The access identity value can be a value indicating how the user equipment is configured. For example, the access identity value may indicate that the user equipment is configured for high-priority services, mission-critical services, multimedia-priority services, etc. The access identity value provides an indication of who the user equipment is.

[0186] As part of the unified access control enhancement, the base station can provide radio channel condition threshold configuration to user equipment (UE) intending to receive multicast services in the Radio Resource Control (RRC) connected state. The radio channel condition threshold parameters in the configuration can indicate any combination of parameters including: Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), SSB-based Signal-to-Noise Ratio (SINR), CSI-RS Reference Signal, Channel State Information (CSI) reporting threshold, etc. When the parameters of the channel associated with the UE exceed one or more configured threshold parameters, the UE can be restricted from entering the RRC connected state for the purpose of receiving multicast services. Otherwise, based on the unified access control mechanism, the UE can be allowed to enter the RRC connected state for the purpose of receiving multicast services.

[0187] At block 904, a user equipment (UE) may receive one or more access control parameters from a base station based on one or more cell prohibition parameters instructing the UE to select a cell from the base station for receiving multicast or broadcast services. These access control parameters indicate whether the UE is permitted to establish or restore a Radio Resource Control (RRC) connection with the base station to receive multicast or broadcast services. For example, the base station may have identified whether to allow a set of UEs in a group to establish or restore a RRC connection with the base station to receive multicast or broadcast services. In some embodiments, identifying whether to allow a user equipment (UE) to establish or restore an RRC connection with the base station to receive multicast or broadcast services may be based on an overload condition at the base station and one of the following: a received RRC establishment reason or a received RRC restoration reason. In some embodiments, identifying whether to allow a set of UEs in a group to establish or restore a RRC connection with the base station to receive multicast or broadcast services may be based on allowing the group of UEs to receive multicast or broadcast services in an RRC connection state. In some embodiments, allowing the group of UEs to receive multicast or broadcast services may be based on an overload condition at the base station.

[0188] The base station may also have configured one or more access control parameters. In some embodiments, the base station may have configured or generated one or more access control parameters when (e.g., in response to) the base station being configured to provide access to one or more multicast services for a user equipment (UE) in a Radio Resource Control (RRC) connection state. In some embodiments, the base station may have configured or generated one or more access control parameters when (e.g., in response to) the base station allowing the group of UEs to establish or resume RRC connections. These access control parameters may include one or more access class values, and each access class may be configured with a prohibition factor and a prohibition timer. One or more access control parameters may be sent to the UE via System Information Block Type 1 (SIB1) messages to enable the UE to identify whether the UE is prohibited from sending access attempts (e.g., access messages) for connection setup to receive one or more multicast services. In some embodiments, one or more access control parameters are associated with all multicast services or one or more specific multicast services.

[0189] Each of one or more cell prohibition factors and each of one or more cell prohibition times may be associated with at least one access class value described herein. A cell prohibition factor may be a number generated by a base station that is not less than zero (0) and not greater than one (1) (e.g., 0.4, 0.6, 0.8). A cell prohibition time may be a specified amount of time between instances when a user equipment generates a random number to be compared with a cell prohibition factor as described herein, or a time provided by the base station. A base station may include cell prohibition factors and cell prohibition times to maintain or limit the number of user equipments that can remain on the base station to receive one or more multicast services (e.g., maintain or limit them below a threshold). Alternatively or additionally, a base station may already include cell prohibition factors and cell prohibition times to maintain or limit the data rate at which data is transmitted through the base station (e.g., maintain or limit it below a threshold).

[0190] The base station may have configured or generated one or more cell prohibition factors and one or more cell prohibition times based on at least one of the following: one or more Quality of Service (QoS) parameters associated with one or more multicast services, the number of one or more user equipments receiving access to multiple multicast services through the base station, or the data rate at which one or more user equipments access data through the base station. For example, the base station may have generated the access class value associated with all multicast services as described herein. The base station may also have identified that the number of user equipments camped on the base station exceeds a threshold number. The base station may have configured the cell prohibition factor associated with all multicast services to a relatively low value (e.g., 0.1, 0.3) to provide user equipments with a low chance of receiving access to all multicast services and a high chance of being prohibited. In some embodiments, the base station may configure the cell prohibition factor to a value of zero, thereby denying user equipment the opportunity to access the multicast services associated with the access class value. Alternatively or additionally, the base station may have configured the cell prohibition time associated with all multicast services to be a relatively long time period between instances when user equipment generates a random number for comparison with the cell prohibition factor as described herein. By giving user equipment a high chance of being banned and a long amount of time between generating random numbers, the base station is given time to allow other user equipment to disengage from the base station and reduce the number of user equipment camped on the base station to below a threshold number.

[0191] In some embodiments, when a base station is configured to provide access to one or more multicast services to a user equipment (UE) in a Radio Resource Control (RRC) connection state, the base station may have configured or generated one or more access control parameters. Subsequently, the base station may configure or generate one or more access control parameters including one or more access class values, and each access class may be configured with a prohibition factor and a prohibition timer. One or more access control parameters can be sent to the UE via a System Information Block Type 1 (SIB1) message. The one or more access control parameters enable the UE to identify whether it is prohibited from sending access attempts (e.g., access messages) for connection setup to receive one or more multicast services.

[0192] Upon receiving access control parameters for the access class, and when a user equipment (UE) establishes or restores a radio resource control (RRC) connection to receive multicast services in the RRC connection state, the UE can determine whether to send an access attempt based on access class parameters (e.g., a prohibition factor and prohibition time for the access class). As part of a prohibition test for a given access class, the UE can generate a random number not less than or greater than the access class prohibition factor. Subsequently, the UE can determine that it is not permitted to send access attempts to establish or restore an RRC connection to receive one or more multicast services from the base station. When the UE determines that it is not permitted to send access attempts associated with the access class to establish or restore an RRC connection to receive one or more multicast services from the base station based on a comparison between the generated random value and the cell prohibition factor, the UE starts a timer. While the timer for that access class is running, the UE may be prevented from initiating access attempts for the same access class. After the timer expires, if the UE seeks to access the cell for the same access class, it may be allowed to repeat the prohibition test for the same access class. If the subsequently generated random number is less than the cell prohibition factor, the user equipment may be permitted to send an access attempt to the base station or cell to receive one or more multicast services from the base station, and the process stops. Otherwise, the user equipment may restart the timer and generate another random number based on the cell prohibition timer. This process may be repeated until the user equipment generates a random number less than the cell prohibition factor, indicating that the user equipment is permitted to send an access attempt to the base station or cell to receive one or more multicast services from the base station in Radio Resource Control (RRC) connected state.

[0193] In some embodiments, the base station may have generated one or more cell prohibition factors and one or more cell prohibition times based on at least one of the following: one or more Quality of Service (QoS) parameters associated with one or more multicast services, the number of one or more UEs receiving access to one or more multicast services through the base station, or the data rate at which one or more UEs access data through the base station. For example, the base station may have generated an access class value associated with all multicast services. The base station may also have identified that the number of user equipments that can establish radio resource control connections to the base station is higher than a threshold number. The base station may have configured the cell prohibition factor associated with all multicast services to a relatively low value (e.g., 0.1, 0.3) to provide user equipments with a low chance of receiving access to all multicast services and a high chance of being prohibited. In some embodiments, the base station may have configured the cell prohibition factor to a value of zero, thereby denying user equipment the opportunity to access multicast services. Furthermore, the base station may have configured the cell prohibition time associated with all multicast services to a relatively long time period. This can extend the amount of time between instances when a user equipment generates a random number to a relatively long time period. By giving user equipment a high chance of being banned and a long amount of time between generating random numbers, time can be given to the base station to allow other user equipment to disconnect from the base station and reduce the number of user equipment establishing or resuming RRC connections to the base station to below a threshold number.

[0194] As another example, the base station can also identify that the Quality of Service (QoS) associated with all multicast services is relatively high or strong. The base station may have configured the cell prohibition factor associated with all multicast services to a relatively high value (e.g., 0.7, 0.9) to provide the user equipment with a high chance of receiving access to all multicast services and a low chance of being prohibited. In some embodiments, the base station may configure the access class value to one (1), thereby granting the user equipment access to the multicast services associated with that access class value. In some embodiments, when the access class prohibition factor is zero, the user equipment can identify that it has access to the multicast services. Furthermore, the base station may configure the cell prohibition time associated with all multicast services to a relatively short time period. This allows the amount of time between instances when the user equipment generates random numbers to be extended to a relatively short time period. By giving user equipment a low chance of being prohibited and a short amount of time between generating random numbers, the base station can provide user equipment with a rapid opportunity to receive multicast services through the base station and increase the number of user equipment connected to the base station (e.g., to establish a radio resource control connection with the base station) to receive high quality of service.

[0195] After the access control check, if a user equipment is allowed to send an access attempt to establish or restore a Radio Resource Control (RRC) connection, the user equipment can initiate a Random Access (RACH) procedure. During the RACH procedure, message 3 or message A may carry a RRC setup request message or a RRC recovery request message. The RRC setup request message may include a reason for establishing a multicast service, or the RRC recovery request message may include a reason for recovering a multicast service. Upon receiving message 3 or message A containing the reason for establishment / recovery = multicast service, the base station may reject the connection setup or allow the connection setup / recovery procedure based on overload conditions. If the base station rejects the RRC connection setup or RRC recovery procedure, the base station may send a RRC rejection message including a wait timer. In some embodiments, while the wait timer is running, the user equipment may be prevented from establishing or restoring a RRC connection. When the wait time expires, the user equipment may be allowed to initiate an access attempt again, and the above procedure may be repeated.

[0196] Figure 4 Table 400 illustrates an example mapping of access identity values ​​to prohibition parameters for controlling multicast and broadcast access, according to some aspects of this disclosure. Figure 4 As shown, Table 400 includes multiple access identity values, and each access identity value is used to specify the device type based on device configuration. Each of the multiple access identity values ​​can be a numerical value starting with zero (e.g., an integer value). As part of the unified access control parameters in SIB1, each access identity can be prohibited or not prohibited by setting the associated access prohibition bit (e.g., "1" for prohibition, "0" for not prohibition). The UE may seek to send an access attempt to the base station. The UE can verify whether the access attempt associated with the access identity is prohibited or not based on the prohibition bit value received for the access identity.

[0197] As described herein, each of a plurality of access identity values ​​can be mapped to a user equipment configuration. As an example, a user equipment associated with access identity value one (1) can be configured for Multimedia Priority Service (MPS). As another example, a user equipment associated with access identity value two (2) can be configured for Mission Critical Service (MCS).

[0198] One or more access class values ​​may include one or more access class values ​​associated with a service. An access class value may be a value indicating what the access message is requesting. For example, an access class value may indicate that the user equipment is requesting access for: paging service, emergency call service, multimedia telephony (MMTEL) voice session service, MMTEL video session service, real-time text service, IP multimedia subsystem (IMS) messaging service, short message service (SMS), etc. The access class value provides an indication of what the user equipment is doing or wants to do. In some embodiments, the access class value may be a standard value or a carrier-specified value. The NAS may provide a radio resource establishment reason to be used for services initiated by the NAS. For connections initiated by radio resource control, radio resource control is used to identify what the radio resource control establishment reason is. NAS TS 24.501, Table 4.5.2.2 may specify one or more mapping tables for access class and radio resource control establishment terms.

[0199] Figure 5 Table 500 illustrates an example mapping of access category values ​​to prohibition parameters for controlling multicast and broadcast access, according to some aspects of this disclosure. Figure 5 As shown, Table 500 includes multiple access category values, multiple conditions associated with the user equipment, and multiple access attempt types. Each access category value can be a numeric value starting with zero (e.g., an integer value). The numeric value can be a standard value or a value specified by the operator. The multiple conditions associated with the user equipment can be conditions related to the user equipment associated with the access category value. The multiple access attempt types can relate to the type of service the user equipment is seeking to receive access to.

[0200] Each of the multiple access category values ​​can be mapped to conditions and access attempt types associated with the user equipment. As an example, for access category value one (1), the conditions associated with the user equipment providing that access category value include: "The UE is configured for delay-tolerant service and is subject to access control for access category 1, which is determined based on the relationship between the UE's home public land mobile network (HPLMN) and the selected public land mobile network." As another example, for access category value three (3), the conditions associated with the user equipment providing that access category value include all conditions except those for access category value one (1).

[0201] Each of the multiple access category values ​​can be mapped to an access attempt type. As an example, for access category value one (1), the access attempt type can indicate that the associated user equipment includes all access attempt types except for emergency services or mobile-initiated (MO) anomalous data. As another example, for access category value three (3), the access attempt type can indicate that the associated user equipment includes access attempts associated with mobile-initiated signaling at the non-access stratum (NAS) level arising from services other than paging services.

[0202] In some embodiments, each of the multiple access category values ​​can be mapped to additional information, such as annotations indicating one or more other parameters. As an example, for access category value one (1), one or more other parameters may indicate that, for access category 1, this is accompanied by information defining whether the access category is applicable to user equipment having one of the following categories: (a) user equipment configured for delay-tolerant services; (b) user equipment configured for delay-tolerant services and neither in its home public land mobile network nor in its equivalent public land mobile network; (c) user equipment configured for delay-tolerant services and neither in the public land mobile network of the country in which the user equipment is roaming, listed in the operator-defined public land mobile network selector list on the SIM / USIM, nor in its home public land mobile network equivalent to its home public land mobile network. When the user equipment is configured for EAB, it is also configured for delay-tolerant services. In the case of user equipment configured for both EAB and EAB overriding, access category 1 is not applicable when the upper layer indicates overriding access category 1. As another example, for access category value three (3), the prohibition parameter can indicate that the associated user equipment is prohibited from accessing signaling initiated by a mobile terminal at the non-access stratum (NAS) level from services other than paging services.

[0203] As an example, for access category values ​​32-63, one or more other parameters can indicate: when both carrier-based access category and standard access (access attempts can be classified as either) exist, and the standard access category is neither 0 nor 2, the user equipment applies the carrier-based access category. When both carrier-based access category and standard access category (access attempts can be classified as either) exist, and the standard access category is 0 or 2, the user equipment can apply the standard access category.

[0204] As another example, for an access attempt type associated with access category value four (4), a multimedia telephony (MMTEL) voice session service may include a real-time text (RTT) service. As yet another example, for an access attempt type associated with access category value seven (7), MO data that does not belong to any other access category may include IP multimedia subsystem messaging. As yet another example, for an access attempt type associated with access category value nine (9), MO IP multimedia subsystem registration associated with signaling that may include data that does not belong to any other access category may include signaling-related IP multimedia subsystem registration (such as initial registration, re-registration, and subscription refresh for IP multimedia subsystem messaging). As an example, for access category value ten (10), one or more other parameters may indicate that category ten is applicable to Node B of the Internet of Things (IoT) using Node B IoT connections to 5GC.

[0205] In some embodiments, one or more access control parameters may include one or more access class values ​​associated with one or more multicast services. When a base station sends one or more access class access control parameter values ​​associated with one or more multicast services, the user equipment (UE) may receive those access classes associated with the access control parameter values ​​and identify whether the UE is prohibited from sending access messages (e.g., access attempts) for connection setup to request one or more multicast services associated with the received access class values. For example, the UE may receive access class values ​​from the base station indicating video streaming multicast services. The UE may match the received access class values ​​with access class values ​​associated with the video streaming multicast services that the UE seeks to receive, and based on the match, identify that the UE is not prohibited by the base station from sending access messages for requesting connection setup to access the video streaming multicast services. As discussed herein, the UE may then send access messages (e.g., access attempts for connection setup) to the base station to request video streaming multicast services from the base station based on one or more received access class parameters. In some embodiments, when the base station does not include an access class value that matches the access class value associated with the multicast service that the user equipment is seeking access to, the user equipment can recognize that the base station is preventing the user equipment from sending access messages for connection setup and receiving multicast services, and that the unified access control mechanism has ended. In some embodiments, one or more access class values ​​are used to identify all multicast services or one or more specific multicast services (e.g., video streaming multicast services).

[0206] For example, a base station may send or broadcast one or more access control parameters to a group of UEs, including the UEs, based on whether the UE set is allowed to establish or restore an RRC connection with the base station to receive multicast broadcast services.

[0207] In some aspects, a user equipment (UE) can identify whether it is prohibited from sending access request messages to establish or restore an RRC connection state to receive multicast services based on one or more access control parameters. For example, the UE can receive one or more access control parameters from the base station based on whether it is allowed to establish or restore a Radio Resource Control (RRC) connection state with the base station to receive multicast services. After receiving one or more access control parameters, the UE can identify whether it is prohibited from sending access request messages to establish or restore an RRC connection state to receive multicast services.

[0208] At box 906, a User Equipment (UE) may send an Access Request message based on one or more Access Control (ACH) parameters to establish or restore an RRC connection state with a base station to receive multicast or broadcast services. For example, if an access attempt associated with an access class is not prohibited, the UE may send an ACH request message to the base station to request the establishment or restoration of an RRC connection state to receive multicast or broadcast services. The base station may have already sent these ACH parameters to the UE via a System Information Block Type 1 (SIB1) message. One or more ACH parameters enable the UE to identify whether it is prohibited from sending access attempts (e.g., access messages) for connection setup to receive one or more multicast or broadcast services. In response, the UE may send an Access Message to request connection setup to receive one or more multicast or broadcast services. The UE may send an Access Message to request setup to receive one or more multicast or broadcast services based on one or more ACH parameters. For example, when one or more configured access parameters do not indicate that the user equipment is prohibited from sending access messages for requesting connection setup to receive access to one or more multicast services, or when one or more configured access parameters indicate that the user equipment is not prohibited from sending access messages for requesting connection setup to receive access to said one or more multicast services, the user equipment may send an access message to the base station for requesting connection setup to receive access to one or more multicast services. As an example, if the user equipment is not prohibited from sending access messages for requesting connection setup to access one or more multicast services (e.g., as described in the following document: TS38.331, Section 5.3.14.5: Access barring check), the user equipment may send access messages, such as RRCSetupRequest messages or RRCResumeRequest messages, which, for example, include a new reason value associated with the multicast service (e.g., an access category value). The new reason value associated with one or more multicast services may be mapped to an establishment reason or recovery reason also associated with one or more multicast services. The new reason value mapped to the establishment or recovery reason allows the base station to distinguish between a UE attempting to establish a multicast broadcast and a UE attempting to establish a unicast broadcast. The new reason value mapped to the establishment or recovery reason also allows the base station to identify whether the UE is establishing an RRC connection for the first time to receive one or more multicast broadcast services, or whether the UE is resuming a suspended RRC connection to receive one or more multicast broadcast services. If the UE establishes an RRC connection for unicast data and identifies the need to obtain multicast broadcast data during the ongoing unicast connection, the UE can utilize unicast control to obtain the multicast broadcast data.

[0209] At box 908, the User Equipment (UE) can receive an Access Rejection message from the base station. This message indicates that the UE is not permitted to establish or restore an RRC connection state to receive multicast or broadcast services. For example, the base station may send an Access Rejection message to the UE based on the identification that it does not allow the UE to establish or restore an RRC connection state to receive multicast or broadcast services. This message indicates that the request to establish or restore the RRC connection state has been rejected. When the base station is overloaded, it can identify whether the UE is permitted to enter an RRC connection state to receive multicast or broadcast services based on the access message. In such a case, if the base station rejects RRC connection setup due to base station overload, it can send an RRC Rejection message to the UE.

[0210] In some embodiments, a base station may, in response to at least one of an access message indicating that a user equipment (UE) is attempting to establish access to one or more multicast services or to restore access to one or more multicast services, prevent a UE from entering an RRC connected state to receive one or more multicast services. For example, the base station may receive an access message from the UE indicating that the UE is attempting to establish access to one or more multicast services for the first time or after a predetermined time. The base station may refuse to accept new UEs camped on the base station and receiving access to one or more multicast services. In response, the base station may prevent a UE from entering an RRC connected state to receive one or more multicast services through the base station because the UE is attempting to establish access to one or more multicast services for the first time or after a predetermined time.

[0211] In some embodiments, a base station may prevent a user equipment (UE) from entering an RRC connection state and receiving one or more multicast broadcast services based on the type of multicast broadcast service sought by the UE. For example, the base station may prioritize a first type of multicast broadcast service over a second type. For instance, when the service quality for a multicast broadcast service is relatively high at the base station, the base station may allow the UE to enter an RRC connection state to receive access to both the first and second types of multicast broadcast services. However, for example, when the service quality for a multicast broadcast service is relatively low at the base station, the base station may allow the UE to enter an RRC connection state to receive access to the first type of multicast broadcast service but prevent the UE from entering an RRC connection state to receive access to the second type of multicast broadcast service.

[0212] At box 910, a User Equipment (UE) may exchange random access messages with a base station by instructing the UE to establish or restore an RRC connection state to receive multicast or broadcast services based on one or more access control parameters. For example, in response to receiving an access message, the base station may identify that one or more Quality of Service (QoS) parameters associated with one or more multicast / broadcast services are relatively high, the number of one or more UEs receiving access to one or more multicast / broadcast services through the base station is below a threshold number, or the data rate at which one or more UEs access data through the base station is below a threshold data rate. Accordingly, the base station may send a response message based on the access message to instruct the UE to enter an RRC connection state to receive one or more multicast / broadcast services, and subsequently allow the UE to access one or more multicast / broadcast services. The base station and the UE may exchange random access messages based on the base station allowing the UE to establish or restore an RRC connection state to receive multicast / broadcast services.

[0213] As another example, a base station can receive an access message from a user equipment (UE) indicating that the UE is attempting to regain access to one or more multicast services after losing access for a relatively short period. The base station can accept the UE's request to remain on the base station and regain access to one or more multicast services. In response, the base station can allow the UE to enter an RRC connected state and receive one or more multicast services through the base station, since the UE is attempting to regain access to one or more multicast services after losing access for a relatively short period. The base station and the UE can exchange random access messages based on the base station allowing the UE to establish or restore an RRC connected state to receive multicast services.

[0214] Figure 10 This is an example conceptual diagram illustrating some aspects of an example 5G multicast broadcast system architecture 1000 according to this disclosure. The 5G multicast broadcast system architecture 1000 may include aspects described herein. Figure 1-9The system and components described may include one or more of the following: System Architecture 1000 may include a Multicast / Broadcast User Plane Function Interface 1002, an Access and Mobility Management Function Interface 1004, a base station (e.g., gNB-CN) 1006, a first set of one or more user equipments 1008, and a second set of one or more user equipments 1010. System Architecture 1000 may be used to transmit a combination of unicast and multicast services using the Physical Downlink Shared Channel (PDSCH), with LTE Single Cell Point-to-Multipoint (LTE SC-PTM) as a reference. It should be understood that LTE Single Cell Point-to-Multipoint may include single cell point-to-multipoint transmissions such that single cell broadcasts, as first defined in LTE Release 13 and broadcast on the Physical Downlink Shared Channel, are addressed using a Geographic Location-Based Radio Network Temporary Identifier (G-RNTI). Base station 1006 can receive multicast broadcast service quality streams or Temporary Mobile Group Identity (TMGI) via multicast-N3 tunnel 1012, and can map service quality to one or more multicast radio bearers (MRBs) 1014 and 1016 (or dedicated radio bearers (DRBs)) associated with user equipment (e.g., a first set 1008 of one or more user equipments, a second set 1010 of one or more user equipments) and via distributed units (e.g., DU1 1020, DU1 1022). System architecture 1000 can combine or utilize tight coordination between multicast broadcast services and unicast services by providing flexible switching between dedicated radio bearers and multicast radio bearers and by providing unicast assistance to multicast radio bearers in lower layers. Regarding the interface, control signaling for setting and modifying multicast broadcast streams / TMGI can be provided to base station 1006 from access and mobility management function interface 1004 via N2 tunnel 1018. The GTP-based multicast broadcast stream / temporary mobile group identity delivery can be provided to the base station 1006 via the multicast broadcast user plane interface 1002 through multicast broadcast-N3 1012.

[0215] In the first aspect, the base station may broadcast one or more cell prohibition parameters to a group of user equipments (UEs), the one or more cell prohibition parameters indicating whether the UEs in the group are permitted to select a cell from the base station for receiving multicast or broadcast services. The base station may also broadcast one or more access control parameters to a set of one or more UEs in the group who are indicated as permitted to select a cell for receiving multicast or broadcast services based on the one or more cell prohibition parameters, the one or more access control parameters indicating whether the set of one or more UEs is permitted to establish or restore a Radio Resource Control (RRC) connection with the base station to receive multicast or broadcast services.

[0216] In the second aspect, in conjunction with at least the first aspect, the base station can receive an access request message from a set of one or more UEs for requesting to establish or restore an RRC connection state to receive multicast or broadcast services, and can broadcast one or more access control parameters in response to receiving the access request message.

[0217] In the third aspect, in conjunction with one or more aspects of the first to second aspects, one or more access control parameters indicate whether a set of one or more UEs is permitted to establish or restore an RRC connection state with the base station to receive multicast or broadcast services, based on the overload condition at the base station and one of the RRC establishment reasons or RRC recovery reasons indicated in the access request message.

[0218] In the fourth aspect, in conjunction with one or more aspects of the first to third aspects, the base station may send an access rejection message to a set of one or more UEs, the access rejection message indicating that the set of one or more UEs is not permitted to establish or restore RRC connection state to receive multicast or broadcast services.

[0219] In the fifth aspect, in conjunction with one or more aspects of the first to fourth aspects, when one or more access control parameters indicate that a set of one or more UEs is allowed to establish or restore an RRC connection state to receive multicast or broadcast services, the base station may exchange random access messages with a set of one or more UEs.

[0220] In the sixth aspect, in conjunction with one or more of the first to fifth aspects, wherein when the base station supports multicast or broadcast services, one or more cell prohibition parameters indicate that the group of UEs is allowed to select the base station's cell for receiving multicast or broadcast services.

[0221] In the seventh aspect, in conjunction with one or more aspects of the first to sixth aspects, one or more access control parameters indicate that a set of one or more UEs is permitted to establish or restore an RRC connection state with a base station to receive multicast or broadcast services based on one or more access control parameters.

[0222] In the eighth aspect, in conjunction with one or more aspects from the first to the seventh aspect, one or more access control parameters indicate, based on the overload condition at the base station and one of the received RRC establishment reason or received RRC recovery reason, that a set of one or more UEs is permitted to establish or recover an RRC connection state with the base station to receive multicast or broadcast services.

[0223] In the ninth aspect, in conjunction with one or more aspects from the first to the eighth aspects, wherein the set of one or more UEs is a UE seeking to establish or restore an RRC connection state to receive only multicast or broadcast services.

[0224] In the tenth aspect, one or more aspects from the first to the ninth aspects are combined, wherein one or more access control parameters are associated with a specific access class.

[0225] In the eleventh aspect, in conjunction with one or more aspects from the first to the tenth aspects, one or more prohibition parameters may be broadcast in the System Information Block (SIB) or the Master Information Block (MIB).

[0226] In the twelfth aspect, in conjunction with one or more aspects of the first to eleventh aspects, one or more access control parameters may be broadcast in the SIB.

[0227] In the thirteenth aspect, in conjunction with one or more aspects of the first to twelfth aspects, wherein one or more cell prohibition parameters may include at least one of the cellBarred field and the CellReservedforMBSUse field, each of the cellBarred field and the CellReservedforMBSUse field having information elements for indicating whether the group of UEs is allowed to select a cell for receiving multicast or broadcast services from a base station.

[0228] In the fourteenth aspect, in conjunction with one or more of the first to thirteenth aspects, the multicast or broadcast service may be associated with one of the following: a specific public land mobile network (PLMN) or all public land mobile networks.

[0229] In the fifteenth aspect, in conjunction with one or more aspects from the first to the fourteenth aspects, one or more access control parameters may be associated with all multicast or broadcast services or one or more specific multicast or broadcast services.

[0230] In the sixteenth aspect, in conjunction with one or more aspects from the first to the fifteenth aspects, the base station may also use a System Information Block (SIB) to send a list of one or more multicast or broadcast services to the user equipment.

[0231] In the seventeenth aspect, in conjunction with one or more aspects from the first to the sixteenth aspects, the base station may also send one or more radio channel condition thresholds to at least a set of UEs in the group who intend to receive multicast or broadcast services in the RRC connection state.

[0232] In the eighteenth aspect, in conjunction with one or more aspects from the first to the seventeenth aspects, the base station may also send an indication of available multicast or broadcast services to the group of UEs in the System Information Block (SIB).

[0233] In the nineteenth aspect, in conjunction with one or more of the first to eighteenth aspects, it is possible to enable at least one UE in the group of UEs to identify whether to select a cell of a base station based on whether the UE receives an SIB containing an indication of available multicast or broadcast services.

[0234] In the twentieth aspect, in conjunction with one or more aspects from the first to the nineteenth aspects, the one or more cell prohibition parameters may include a cellBarredMBS field with prohibition information elements and a cellReservedForMBSUse field with false information elements, and the base station may also send to the group of UEs an indication of one or more other frequencies or one or more other cells for receiving multicast or broadcast services.

[0235] In aspect twenty-one, the user equipment (UE) can receive one or more cell prohibition parameters from the base station, the one or more cell prohibition parameters indicating whether the UE is permitted to select a cell of the base station for receiving multicast or broadcast services. The UE can also receive one or more access control parameters from the base station based on the one or more cell prohibition parameters indicating whether the UE is permitted to establish or restore a Radio Resource Control (RRC) connection with the base station to receive multicast or broadcast services. The UE can also send access request messages based on one or more access control parameters to establish or restore an RRC connection with the base station to receive multicast or broadcast services.

[0236] In aspect 22, in conjunction with aspect 21, the access request message is sent to the base station based on one or more access control parameters instructing the UE to establish or restore an RRC connection state with the base station to receive multicast or broadcast services.

[0237] In aspect 23, in conjunction with one or more aspects 21 to 22, the access request message includes one of the following: an RRC establishment reason for enabling the base station to allow the UE to establish an RRC connection state with the base station, or an RRC recovery reason for enabling the base station to allow the UE to restore the RRC connection state with the base station.

[0238] In aspect 24, in conjunction with one or more aspects 21 to 23, the UE may also receive an access denial message from the base station indicating that the UE is not permitted to establish or restore an RRC connection state to receive multicast or broadcast services.

[0239] In aspect 25, in conjunction with one or more aspects 21 to 24, the UE may also exchange random access messages with the base station by instructing the UE to establish or restore RRC connection state to receive multicast or broadcast services based on one or more access control parameters.

[0240] In aspect 26, in conjunction with one or more aspects 21 to 35, the UE may seek to establish or restore the RRC connection state to receive only multicast or broadcast services.

[0241] In aspect 27, in conjunction with one or more aspects 21 to 26, one or more access control parameters may be associated with a specific access class.

[0242] In aspect 28, in conjunction with one or more aspects 21 to 27, one or more prohibition parameters may be received in the System Information Block (SIB) or the Master Information Block (MIB).

[0243] In aspect 29, in conjunction with one or more aspects 21 to 38, one or more access control parameters may be received in the SIB.

[0244] In the thirtieth aspect, in conjunction with one or more aspects of the twenty-first to twenty-ninth aspects, wherein one or more cell prohibition parameters may include at least one of the cellBarred field and the CellReservedforMBSUse field, each of the cellBarred field and the CellReservedforMBSUse field having information elements for indicating whether the UE is allowed to select a cell for receiving multicast or broadcast services from a base station.

[0245] In the thirty-first aspect, in conjunction with one or more of aspects 21 to 30, the multicast or broadcast service may be associated with one of the following: a specific public land mobile network (PLMN) or all public land mobile networks.

[0246] In aspect thirty-two, in conjunction with one or more aspects of aspects twenty-one to thirty-one, one or more access control parameters may be associated with all multicast or broadcast services or one or more specific multicast or broadcast services.

[0247] In aspect 33, in conjunction with one or more aspects of aspects 21 to 32, the UE may also receive a list of one or more multicast or broadcast services from the base station via a System Information Block (SIB) message.

[0248] In aspect 34, in conjunction with one or more aspects from aspects 21 to 33, the UE may also receive one or more radio channel condition thresholds from the base station based on the UE's intention to receive multicast or broadcast services in RRC connection state.

[0249] In aspect thirty-six, in conjunction with one or more aspects from aspects twenty-one to thirty-five, the UE may also receive from the base station an indication of available multicast or broadcast services in the system information block (SIB).

[0250] In aspect 37, in conjunction with one or more aspects 21 to 36, the UE may identify whether to select a cell for a base station based on whether the UE receives an SIB containing an indication of available multicast or broadcast services.

[0251] In one configuration, the base station may include: a unit for broadcasting one or more cell prohibition parameters to a group of user equipments (UEs), the one or more cell prohibition parameters indicating whether the UEs in the group of UEs are allowed to select a cell of the base station for receiving multicast or broadcast services; and a unit for broadcasting one or more access control parameters to a set of one or more UEs in the group of UEs that are indicated as allowed to select a cell for receiving multicast or broadcast services based on the one or more cell prohibition parameters, the one or more access control parameters indicating whether the set of one or more UEs is allowed to establish or restore a Radio Resource Control (RRC) connection state with the base station to receive multicast or broadcast services.

[0252] In one aspect, the aforementioned unit for broadcasting one or more cell prohibition parameters to a group of user equipments (UEs) indicating whether a UE in the group is permitted to select a cell of the base station for receiving multicast or broadcast services, and the unit for broadcasting one or more access control parameters (one or more access control parameters indicating whether the set of one or more UEs is permitted to establish or restore a Radio Resource Control (RRC) connection state with the base station to receive multicast or broadcast services) to a set of one or more UEs in the group that are indicated as permitted to select a cell for receiving multicast or broadcast services based on one or more cell prohibition parameters, may be in... Figure 6 The processor 604 shown is configured to perform the functions described in the above-described unit. For example, the unit for broadcasting to a group of user equipment (UEs) an indication of whether a UE in the group is allowed to select one or more cell prohibition parameters of a base station cell for receiving multicast or broadcast services may include... Figure 6The broadcast circuit 642 and transceiver 610 are included. As another example, the unit described above for broadcasting one or more access control parameters (one or more access control parameters indicating whether the set of one or more UEs is allowed to establish or restore a Radio Resource Control (RRC) connection with the base station to receive multicast or broadcast services) to a set of one or more UEs in the group of UEs that are indicated as permitted to select a cell for receiving multicast or broadcast services based on one or more cell prohibition parameters may include in... Figure 6 The broadcast circuit 642 and transceiver 610 are shown in the diagram. Alternatively, the aforementioned units may be circuits or any devices configured to perform the functions described therein.

[0253] In one configuration, a user equipment (UE) may include: a unit for receiving one or more cell prohibition parameters from a base station, the one or more cell prohibition parameters indicating whether the UE is allowed to select a cell of the base station for receiving multicast or broadcast services; a unit for receiving one or more access control parameters from the base station based on the one or more cell prohibition parameters indicating whether the UE is allowed to establish or restore a Radio Resource Control (RRC) connection state with the base station to receive multicast or broadcast services; and a unit for sending an access request message based on one or more access control parameters to establish or restore an RRC connection state with the base station to receive multicast or broadcast services.

[0254] In one aspect, the aforementioned unit for receiving from a base station one or more cell prohibition parameters indicating whether a UE is allowed to select a cell of the base station for receiving multicast or broadcast services, the unit for receiving from a base station one or more access control parameters indicating whether a UE is allowed to establish or restore a Radio Resource Control (RRC) connection state with the base station to receive multicast or broadcast services based on one or more cell prohibition parameters, and the unit for sending an access request message based on one or more access control parameters to establish or restore an RRC connection state with the base station to receive multicast or broadcast services may be in the form of... Figure 8 The processor 804 shown is configured to perform the functions described in the above-described units. For example, the unit for receiving from the base station one or more cell prohibition parameters indicating whether the UE is allowed to select a cell for receiving multicast or broadcast services from the base station, and the unit for receiving from the base station one or more access control parameters indicating whether the UE is allowed to establish or restore a Radio Resource Control (RRC) connection state with the base station to receive multicast or broadcast services based on one or more cell prohibition parameters to indicate whether the UE is allowed to select a cell for receiving multicast or broadcast services from the base station, may include... Figure 8 The receiving circuit 840 and transceiver 810 shown are illustrated. As another example, the unit described above for sending an access request message based on one or more access control parameters to establish or restore an RRC connection state with a base station to receive multicast or broadcast services may include... Figure 8 The transmitting circuit 844 and transceiver 810 are shown. In another example, the above-mentioned units may be circuits or any devices configured to perform the functions described therein.

[0255] Several aspects of wireless communication networks have been described with reference to example implementations. As will be readily recognized by those skilled in the art, the various aspects described herein can be extended to other telecommunications systems, network architectures, and communication standards.

[0256] As used herein, unless otherwise expressly indicated, the use of "or" is intended to be interpreted in an inclusive sense. For example, "a or b" could include only a, only b, or a combination of a and b. As used herein, phrases referring to "at least one" or "one or more" of a list of items refer to any combination of those items, including a single member. For example, "at least one of a, b, or c" is intended to cover the following examples: only a, only b, only c, a combination of a and b, a combination of a and c, a combination of b and c, and a combination of a, b, and c.

[0257] The various illustrative components, logic, logic blocks, modules, circuits, operations, and algorithmic processes described in conjunction with the implementations disclosed herein can be implemented as electronic hardware, firmware, software, or a combination of hardware, firmware, or software, including the structures disclosed in this specification and their structural equivalents. The interchangeability of hardware, firmware, and software has been generally described around functionality and illustrated in the various illustrative components, blocks, modules, circuits, and processes described above. Whether such functionality is implemented in hardware, firmware, or software depends on the specific application and the design constraints imposed on the entire system.

[0258] Various modifications to the implementations described in this disclosure will be readily apparent to those skilled in the art, and the general principles defined herein can be applied to other implementations without departing from the spirit or scope of this disclosure. Therefore, the claims are not intended to be limited to the implementations shown herein, but are to be given the broadest scope consistent with this disclosure, the principles disclosed herein, and the novel features.

[0259] Furthermore, the various features described in this specification within the context of individual implementations can also be implemented in combination within a single implementation. Conversely, the various features described in the context of a single implementation can also be implemented individually or in any suitable sub-combination in multiple implementations. Accordingly, although features may be described above as functioning in a particular combination and even initially claimed in this way, in some cases, one or more features from the claimed combination can be removed from that combination, and the claimed combination can be for sub-combinations or variations thereof.

[0260] Similarly, although operations are depicted in a specific order in the figures, this should not be construed as requiring such operations to be performed in the specific order or sequence shown, or to perform all the operations shown, to achieve the desired result. Furthermore, the figures may schematically depict one or more example processes in the form of flowcharts or schematic diagrams. However, other operations not depicted may be incorporated into the schematically illustrated example processes. For example, one or more additional operations may be performed before, after, simultaneously with, or between any of the operations shown. In some cases, multitasking and parallel processing may be advantageous. Moreover, the separation of the various system components in the implementations described above should not be construed as requiring such separation in all implementations, but rather should be understood as meaning that the described program components and systems can generally be integrated together in a single software product or encapsulated in multiple software products.

Claims

1. A method for wireless communication via a base station, comprising: One or more cell prohibition parameters are broadcast to a group of user equipment (UEs), the one or more cell prohibition parameters indicating whether the UEs in the group of UEs are allowed to select the cell of the base station for receiving multicast or broadcast services; as well as One or more access control parameters are broadcast to a set of one or more UEs in the group of UEs that are indicated as being allowed to select the cell for receiving the multicast or broadcast service based on one or more cell prohibition parameters, the one or more access control parameters indicating whether the set of one or more UEs is allowed to establish or restore a Radio Resource Control (RRC) connection state with the base station to receive the multicast or broadcast service; The UE receives an access request message from one or more UEs in the set of UEs for requesting to establish or restore the RRC connection state to receive the multicast or broadcast service, the access request message indicating one of the RRC establishment reason or RRC restoration reason; as well as In response to receiving the access request message, broadcast one or more access control parameters.

2. The method according to claim 1, wherein, The one or more access control parameters indicate, based on the overload condition at the base station, whether the set of one or more UEs is allowed to establish or restore the RRC connection state with the base station to receive the multicast or broadcast service.

3. The method according to claim 1, further comprising: Send an access denial message to the set of one or more UEs, the access denial message indicating that the set of one or more UEs is not allowed to establish or restore the RRC connection state to receive the multicast or broadcast service.

4. The method according to claim 1, further comprising: When one or more access control parameters indicate that the set of one or more UEs is allowed to establish or restore the RRC connection state to receive the multicast or broadcast service, random access messages are exchanged with the set of one or more UEs.

5. The method according to claim 1, wherein, When the base station supports multicast or broadcast services, the one or more cell prohibition parameters indicate that the group of UEs is allowed to select the cell of the base station for receiving the multicast or broadcast services.

6. The method according to claim 1, wherein, The one or more access control parameters indicate that the set of one or more UEs is allowed to establish or restore the RRC connection state with the base station to receive the multicast or broadcast service, based on the one or more access control parameters.

7. The method according to claim 1, wherein, The one or more access control parameters indicate that the set of one or more UEs is allowed to establish or restore the RRC connection state with the base station to receive the multicast or broadcast service, based on the overload status at the base station and one of the received RRC establishment reasons or received RRC recovery reasons.

8. The method according to claim 1, wherein, The set of one or more UEs is a UE seeking to establish or restore the RRC connection state to receive only multicast or broadcast services.

9. The method according to claim 1, wherein, One or more access control parameters are associated with a specific access category.

10. A base station, comprising: A transceiver is used for wireless communication with a user equipment (UE). as well as One or more processors, electrically coupled to the transceiver and configured to: One or more cell prohibition parameters are broadcast to a group of user equipment (UEs), the one or more cell prohibition parameters indicating whether the UEs in the group of UEs are allowed to select the cell of the base station for receiving multicast or broadcast services; as well as One or more access control parameters are broadcast to a set of one or more UEs in the group of UEs that are indicated as being allowed to select the cell for receiving the multicast or broadcast service based on one or more cell prohibition parameters, the one or more access control parameters indicating whether the set of one or more UEs is allowed to establish or restore a Radio Resource Control (RRC) connection state with the base station to receive the multicast or broadcast service; The UE receives an access request message from one or more UEs in the set of UEs for requesting to establish or restore the RRC connection state to receive the multicast or broadcast service, the access request message indicating one of the RRC establishment reason or RRC restoration reason; as well as In response to receiving the access request message, broadcast one or more access control parameters.

11. The base station according to claim 10, wherein, The one or more access control parameters indicate, based on the overload condition at the base station, whether the set of one or more UEs is allowed to establish or restore the RRC connection state with the base station to receive the multicast or broadcast service.

12. The base station according to claim 10, wherein, The one or more processors are further configured to: Send an access denial message to the set of one or more UEs, the access denial message indicating that the set of one or more UEs is not allowed to establish or restore the RRC connection state to receive the multicast or broadcast service.

13. The base station according to claim 10, wherein, The one or more processors are further configured to: When one or more access control parameters indicate that the set of one or more UEs is allowed to establish or restore the RRC connection state to receive the multicast or broadcast service, random access messages are exchanged with the set of one or more UEs.

14. The base station according to claim 10, wherein, When the base station supports multicast or broadcast services, the one or more cell prohibition parameters indicate that the group of UEs is allowed to select the cell for receiving the multicast or broadcast services.

15. The base station according to claim 10, wherein, Based on the one or more cell prohibition parameters, the group of UEs is allowed to select the cell for receiving the multicast or broadcast service, and the one or more access control parameters indicate that the set of one or more UEs is allowed to establish or restore the RRC connection state with the base station to receive the multicast or broadcast service.

16. The base station according to claim 10, wherein, The one or more access control parameters indicate that the set of one or more UEs is allowed to establish or restore the RRC connection state with the base station to receive the multicast or broadcast service, based on the overload status at the base station and one of the received RRC establishment reasons or received RRC recovery reasons.

17. The base station according to claim 10, wherein, The set of one or more UEs is a UE seeking to establish or restore the RRC connection state to receive only multicast or broadcast services.

18. The base station according to claim 10, wherein, One or more access control parameters are associated with a specific access category.

19. A method for wireless communication by a user equipment (UE), comprising: The UE receives one or more cell prohibition parameters from the base station, the one or more cell prohibition parameters indicating whether the UE is allowed to select the base station's cell for receiving multicast or broadcast services; Based on the one or more cell prohibition parameters, the UE is allowed to select the cell of the base station for receiving multicast or broadcast services to receive one or more access control parameters from the base station. The one or more access control parameters indicate whether the UE is allowed to establish or restore a radio resource control (RRC) connection with the base station to receive the multicast or broadcast services. as well as Based on one or more access control parameters, an access request message is sent to establish or restore the RRC connection state with the base station to receive the multicast or broadcast service, wherein the access request message includes one of the following: The RRC establishment reason used to enable the base station to allow the UE to establish an RRC connection with the base station; or The RRC recovery reason is used to enable the base station to allow the UE to restore its RRC connection state with the base station.

20. The method according to claim 19, wherein, The access request message is sent to the base station based on one or more access control parameters instructing the UE to establish or restore the RRC connection state with the base station to receive the multicast or broadcast service.

21. The method of claim 19, further comprising: The UE receives an access rejection message from the base station, the access rejection message indicating that the UE is not allowed to establish or restore the RRC connection state to receive the multicast or broadcast service.

22. The method of claim 19, further comprising: Based on one or more access control parameters, the UE is instructed to establish or restore the RRC connection state to receive the multicast or broadcast service, in order to exchange random access messages with the base station.

23. A user equipment (UE), comprising: A transceiver, used for wireless communication with a base station; as well as One or more processors, electrically coupled to the transceiver and configured to: The UE receives one or more cell prohibition parameters from the base station, the one or more cell prohibition parameters indicating whether the UE is allowed to select the base station's cell for receiving multicast or broadcast services; Based on the one or more cell prohibition parameters, the UE is allowed to select the cell of the base station for receiving the multicast or broadcast service to receive one or more access control parameters from the base station. The one or more access control parameters indicate whether the UE is allowed to establish or restore the radio resource control (RRC) connection state with the base station to receive the multicast or broadcast service. as well as Based on one or more access control parameters, an access request message is sent to establish or restore the RRC connection state with the base station to receive the multicast or broadcast service, wherein the access request message includes one of the following: The RRC establishment reason used to enable the base station to allow the UE to establish an RRC connection with the base station; or The RRC recovery reason is used to enable the base station to allow the UE to restore its RRC connection state with the base station.

24. The UE according to claim 23, wherein, The access request message is sent to the base station based on one or more access control parameters instructing the UE to establish or restore the RRC connection state with the base station to receive the multicast or broadcast service.

25. The UE according to claim 23, wherein, The one or more processors are further configured to receive an access rejection message from the base station, the access rejection message indicating that the UE is not permitted to establish or restore the RRC connection state to receive the multicast or broadcast service.

26. The UE according to claim 23, wherein, The one or more processors are further configured to: Based on one or more access control parameters, the UE is instructed to establish or restore the RRC connection state to receive the multicast or broadcast service, in order to exchange random access messages with the base station.

Images