Frequency prioritization for terminal devices receiving a multicast broadcast service

Abstract

According to one embodiment, an apparatus configured to perform the following operations is provided. The apparatus receives a service announcement for a multicast service. The apparatus receives at least one indication in the service announcement and / or in at least one message following the service announcement, the at least one indication indicating support for all or at least some capability-degraded terminal devices for the multicast service. The apparatus performs a cell reselection procedure based on cell measurements and the at least one indication.

Description

Technical Field

[0001] Field of the Invention: Various exemplary embodiments relate to wireless communication. Prior Technology

[0002] Background of the Invention: RedCap terminal devices are terminal devices that adhere to certain predefined bandwidth (BW) limitations. In other words, RedCap terminal devices cannot use a receiving bandwidth greater than the predefined maximum bandwidth (e.g., 20 MHz). Accordingly, RedCap-specific common frequency resources (CFRs) have been introduced for receiving multicast broadcast services (MBS) by RedCap terminal devices. Since the service area of ​​a specific temporary action group identifier (TMGI) can include access nodes that support and do not support RedCap CFRs, the same frequency selection guidance used for cell reselection is not applicable to both RedCap and non-RedCap terminal devices due to the fact that RedCap terminal devices can only receive services in some cells of the service area. Therefore, a new mechanism is needed to guide RedCap and non-RedCap terminal devices differently in cell reselection decisions. Summary of the Invention

[0003] Summary of the Invention: Based on a prototype, an object within the scope of the independent patent application is provided. Embodiments are defined in the appendix patent applications.

[0004] One or more embodiments are illustrated in the following figures and description. Other features will become apparent from the description and figures, as well as the claims. Simple Explanation of the Diagram

[0005] Figure 1 illustrates some embodiments of the system to which they can be applied;

[0006] Figures 2 to 4 illustrate the procedure according to the embodiment;

[0007] Figure 5 illustrates the communication scenario between the terminal device, three access nodes, and the core network according to an embodiment;

[0008] Figures 6A and 6B illustrate two exemplary communication scenarios between a terminal device, three access nodes, and a core network for performing cell reselection according to an embodiment;

[0009] Figures 7 and 8 illustrate two alternative core network communication scenarios between the Multicast / Broadcast Talk Management Function (MB-SMF), Network Open Function (NEF), and Application Function (AF) according to an embodiment capable of performing cell reselection;

[0010] Figures 9 to 11 illustrate the procedures according to the embodiments;

[0011] Figure 12 illustrates the communication scenario between the terminal device, three access nodes, and the core network according to an embodiment; and

[0012] Figure 13 illustrates a device according to some embodiments. Implementation

[0013] Detailed Description of Preferred Embodiments: The following embodiments are presented as examples only. Although references to "a," "an," or "some" embodiments and / or examples may be made in various places throughout this specification, this does not necessarily mean that the references are made to the same embodiment or example, or that a particular feature is applicable only to a single embodiment and / or example. Individual features of different embodiments and / or examples may also be combined to provide other embodiments and / or examples.

[0014] As used herein, “at least one of the following: ” and “at least one of the following: ” and similar wording, wherein the list of two or more elements is connected by “and” or “or”, means at least any one of the elements, or at least any two or more of the elements, or at least all of the elements.

[0015] As used herein, the equivalent terms "RedCap UE," "RedCap UE," "RedCap User Equipment," and "RedCap UE" are defined below. The 3GPP (3rd Generation Partnership Project) introduced RedCap devices in New Radio (NR) Release 17 (Rel-17). For example, a RedCap device may also be referred to as a RedCap UE, NR-Lite device, or NR-Light device. 3GPP RedCap NR features reduce UE complexity, decrease UE bandwidth, reduce UE power consumption, relax data rates, and relax UE processing time and capabilities by requiring fewer receiver / transmitter (Rx / Tx) antennas, thus enabling groundbreaking use cases such as those surrounding industrial wireless sensors, video surveillance, and wearables.

[0016] In NR, the frequency range below 6 GHz or 7 GHz is designated FR1, and the range above 24 GHz (or more precisely, 24 GHz to 52.6 GHz) is designated FR2. During initial access and afterwards, the maximum bandwidth for an FR1 RedCap UE is 20 MHz. During initial access and afterwards, the maximum bandwidth for an FR2 RedCap UE is 100 MHz. For older NR UEs requiring a band with at least 2 receive (Rx) antenna ports or at least 4 Rx antenna ports, the minimum number of Rx branches supported for RedCap UEs is 1. For a RedCap UE with 1 Rx branch, 1 downlink (DL) multiple-input multiple-output (MIMO) layer is supported. For a RedCap UE with 2 Rx branches, 2 DL MIMO layers are supported.

[0017] RedCap devices can coexist with non-RedCap UEs (i.e., both RedCap devices and non-RedCap UEs can exist in a given cell).

[0018] In the following description, different exemplary embodiments will be used with radio access architectures based on Long Term Evolution (LTE-A) or New Radio (NR, 5G) (as examples of access architectures to which the embodiments may be applied), but the embodiments are not limited to such architectures. It will be apparent to those skilled in the art that the embodiments can also be applied to other types of communication networks with suitable components by appropriately adjusting parameters and procedures. Some examples of other options for suitable systems are Global System for Mobile Telecommunications (UMTS) radio access networks (UTRAN or E-UTRAN), Long Term Evolution (LTE, the same as E-UTRA), wireless local area networks (WLAN or WiFi), WiMAX, Bluetooth®, Personal Communication Services (PCS), ZigBee®, Wideband Code Division Multiple Access (WCDMA), systems using Ultra Wideband (UWB) technology, sensor networks, Mobile Specialty Networks (MANET), and Internet Protocol Multimedia Subsystem (IMS) or any combination thereof.

[0019] Figure 1 depicts an example of a simplified system architecture that only shows some elements and functional entities that are all logical units. The implementation of these logical units may differ from what is shown. The connections shown in Figure 1 are logical connections; the actual physical connections may differ. It will be apparent to those skilled in the art that the system typically includes other functions and structures besides those shown in Figure 1.

[0020] However, the embodiments are not limited to the system given as an example, but those skilled in the art can apply the solution to other communication systems that have the necessary properties.

[0021] Figure 1 illustrates a portion of an exemplary radio access network.

[0022] A communication system typically comprises more than one (e / g)NodeB, in which case the (e / g)NodeBs can also be configured to communicate with each other via wired or wireless links designed for this purpose. These links can be used for signaling purposes. The (e / g)NodeB is a computing device configured to control the radio resources of the communication system to which it is coupled. A NodeB may also be referred to as a base station, access point, or any other type of interfacing device including repeaters capable of operating in a wireless environment. The (e / g)NodeB includes or is coupled to a transceiver. Starting from the transceiver of the (e / g)NodeB, a connection is provided to an antenna unit, which establishes a bidirectional radio link to the user device. The antenna unit may contain multiple antennas or antenna elements. The (e / g)NodeB is further connected to the core network 110 (CN or Next Generation Core NGC). Depending on the system, the counterpart on the CN side can be a Service Gateway (S-GW, which routes and forwards user data packets) or a Packet Data Network Gateway (P-GW) to provide user equipment (UE) with connections to external packet data networks or mobile management entities (MMEs).

[0023] In some embodiments, core network 110 may include application functions (AFs). An AF is a functional element that provides service or application-related information to network function (NF) service consumers. An AF can provide one or more services. The AF resides in the control plane of a 5G Service-Based Architecture (SBA). The AF's responsibilities include, for example, accessing network open functions (NEFs) for resource acquisition, interacting with policy control functions (PCFs) for policy control, performing service routing for applications, and providing application services to users.

[0024] In some embodiments, core network 110 may include a Network Open Function (NEF). The NEF can be configured to, for example, securely open the services and capacity provided by 3GPP network functions.

[0025] In some embodiments, core network 110 may include a multicast / broadcast session management function (MB-SMF). The MBS-SMF can be configured to, for example, manage multicast / broadcast service (MBS) sessions and interact with the RAN and multicast / broadcast user plane function (MB-UPF) for data transmission. It should be noted that the term "multicast / broadcast" is equivalent to the alternative terms "multicast-broadcast" or "multicast broadcast," and is used entirely in the relevant technical field.

[0026] A user equipment (also referred to as a UE, user terminal, terminal device, etc.) describes a type of device to which resources on the space interface are allocated and assigned, and therefore any features described herein with respect to a user equipment can be implemented by a corresponding device such as a relay node. An example of such a relay node is a Layer 3 relay (self-backhaul relay) toward a base station. A user equipment may include a mobile device and at least one Universal Integrated Circuit Card (UICC).

[0027] User devices generally refer to portable computing devices that operate with or without a Subscriber Identity Module (SIM) or User Interface Control (UICC), including but not limited to: mobile radios (mobile phones), smartphones, personal digital assistants (PDAs), handheld devices, devices using wireless modems (alarms or measuring devices, etc.), laptops and / or touchscreen computers, tablets, gaming consoles, notebook computers, and multimedia devices. It should be understood that a user device can also be a single, almost exclusively uplink device, an example being a camera or video camera that loads images or video clips onto a network. A user device can also be a device capable of operating in an Internet of Things (IoT) network, where objects are capable of transmitting data over a network without human-to-human or human-to-computer interaction. The user device (or, in some embodiments, a Layer 3 relay node) is configured to perform one or more of the user device functions. User equipment may also be referred to as user unit, mobile station, remote terminal, access terminal, user terminal or user equipment (UE), only some of these names or devices are mentioned.

[0028] The various technologies described in this article can also be applied to cyber-physical systems (CPS) (systems that enable computing elements controlling physical entities to collaborate). CPS enables the implementation and utilization of a large number of interconnected ICT devices (sensors, actuators, processors, microcontrollers, etc.) embedded in physical objects at different locations. Mobile cyber-physical systems, where the physical systems discussed possess inherent mobility, are a subcategory of cyber-physical systems. Examples of mobile physical systems include mobile robots and electronic components transported by humans or animals.

[0029] It should be understood that in Figure 1, the user device is depicted with two antennas for clarity only. The number of receiving and / or transmitting antennas may naturally vary depending on the current implementation.

[0030] In addition, although the device is depicted as a single entity, different units, processors and / or memory units may be implemented (not all of which are shown in Figure 1).

[0031] 5G can utilize multiple-input multiple-output (MIMO) antennas, more base stations or nodes than LTE (the so-called small cell concept), including gigabit sites operating in cooperation with smaller stations, and employs a variety of radio technologies depending on service requirements, usage scenarios, and / or available spectrum. 5G mobile communications support a wide range of use cases and related applications, including video streaming, augmented reality, various forms of data sharing, and various types of machine applications, including vehicle safety, different sensors, and real-time control. 5G is expected to have multiple radio interfaces, namely sub-6 GHz centimeter waves and millimeter waves, and can also be integrated with existing legacy radio access technologies such as LTE. Integration with LTE can be implemented, at least in the early stages, as a system where macro coverage is provided by LTE, and 5G radio interface access is aggregated from small cells via LTE. In other words, 5G is planned to support both RAT interoperability (such as LTE-5G) and RI interoperability (radio interface interoperability, such as sub-6 GHz-cm wave and sub-6 GHz-cm wave-millimeter wave). One concept considered for use in 5G networks is network slicing, in which multiple independent and dedicated virtual subnetworks (network examples) can be built within the same infrastructure to run services with different requirements for latency, reliability, throughput, and mobility.

[0032] The current architecture of LTE networks is entirely distributed across the radio and entirely centralized in the core network. Low-latency applications and services in 5G require content to be closer to the radio, leading to local offloading and multiple access edge computing (MEC). 5G enables analytics and knowledge generation to occur at the data source. This approach requires leveraging resources that may not be discontinuously connected to the network, such as laptops, smartphones, tablets, and sensors. MEC provides a distributed computing environment for application and service hosting. It can also store and process content very close to the cellular user for faster response times. Edge computing encompasses a wide range of technologies, such as wireless sensor networks, mobile data acquisition, mobile signature analysis, collaborative distributed peer-to-peer special purpose network connectivity and processing, and can also be categorized into local cloud / fog computing and grid / mesh computing, dew point computing, mobile edge computing, micro-cloud, distributed data storage and retrieval, self-healing networks, remote cloud services, augmented and virtual reality, data caching, Internet of Things (massive connectivity and / or latent critical), and critical communications (autonomous vehicles, business security, real-time analytics, time-critical control, medical applications).

[0033] The communication system may also communicate with or utilize services provided by other networks such as the public switched telephone network or the Internet 112. The communication network may also support the use of cloud services; for example, at least a portion of the core network operation may be performed as a cloud service (depicted as "cloud" 114 in Figure 1). The communication system may also include a central control entity or the like, thereby providing facilities for different operators' networks to collaborate, for example, through spectrum sharing.

[0034] Edge cloud can be introduced into the RAN by utilizing Network Functions Virtualization (NVF) and Software Defined Networking (SDN). Using an edge cloud means that access node operations are at least partially performed on servers, hosts, or nodes that are operatively coupled to remote radio heads or units (RUs) or base stations containing radio components. Node operations may also be distributed across multiple servers, nodes, or hosts. The application of a cloud-based RAN architecture allows real-time RAN functions to be performed on the RAN side (in distributed unit DU 104), while non-real-time functions can be performed centrally (in central or centralized unit CU 108). Therefore, in general, the RAN may include at least one distributed access node comprising a central unit, one or more distributed units communicatively connected to the central unit, and one or more (remote) radio heads or units, each communicatively connected to at least one of the distributed units.

[0035] It should also be understood that the workforce allocation between core network operations and base station operations may differ from, or even not exist, in LTE. It is highly likely that some other technological advancements will be made towards big data and all-IP, which could change how networks are built and managed. 5G (or New Radio, NR) networks are designed to support multiple layers, with MEC servers positioned between the core and base stations or NodeBs (gNBs). It should be understood that MEC can also be used in 4G networks.

[0036] 5G can also utilize satellite communications to enhance or complete 5G service coverage, for example, by providing backhaul. Possible use cases include providing service continuity to passengers on machine-to-machine (M2M) or Internet of Things (IoT) devices or vehicle motherboards, ensuring service availability for critical communications, and future rail / maritime / aviation communications. Satellite communications can utilize geostationary orbit (GEO) satellite systems and low Earth orbit (LEO) satellite systems, specifically mega-constellations (systems deploying hundreds of (nano) satellites). Each satellite 106 in a mega-constellation can cover several satellite-supported network entities that establish terrestrial cells. Terrestrial cells can be established via terrestrial relay nodes 104 or via gNBs located on the ground or in satellites.

[0037] It will be apparent to those skilled in the art that the system depicted is only an example of one type of radio access system, and in practice, the system may contain multiple (e / g)NodeBs, user devices may have access to multiple radio cells, and the system may also include other devices, such as physical layer relay nodes or other network elements. At least one of the (e / g)NodeBs may be a home (e / g)NodeB. Furthermore, multiple different types of radio cells and multiple radio cells may be available in the geographical area of ​​the radio communication system. Radio cells may be giant cells (or umbrella cells), which are large cells typically with diameters up to tens of kilometers, or smaller cells such as micro, micro, or pico cells. The (e / g)NodeB in Figure 1 can provide any type of such cell. Cellular radio systems can be implemented as multi-layer networks comprising several types of cells. Typically, in a multi-layer network, one access node provides one or more types of cells, and therefore multiple (e / g)NodeBs are required to provide such a network structure.

[0038] To meet the need for improved deployment and performance of communication systems, the concept of "plug-and-play" (e / g) NodeBs has been introduced. Typically, in addition to home (e / g) NodeBs (H(e / g) NodeBs), networks capable of using "plug-and-play" (e / g) NodeBs also include home NodeB gateways or HNB-GWs (not shown in Figure 1). HNB gateways (HNB-GWs), typically installed within carrier networks, can aggregate traffic from a large number of HNBs back to the core network.

[0039] The 6G architecture aims to easily integrate everything, such as networks, interconnected communications and sensing, non-terrestrial networks and terrestrial communication networks. The 6G system envisions encompassing machine learning algorithms and local and distributed computing capabilities, where virtualized networking functions can be distributed across core and edge computing resources. The outermost edge computing, pushed to the network's edge, will be part of a distributed computing environment, such as in a "zero-latency" scenario. 5G systems can also utilize these capabilities. More generally, a practical (radio) communication system is envisioned as consisting of one or more computer programs running within a scalable infrastructure, such as general-purpose computing entities (servers, processors, and the like).

[0040] The embodiments discussed below contain at least some systematic references to broadcasting as defined in 3GPP Release 17. Broadcast service is defined as an alternative to multicast service. In broadcast service, a transmitter transmits the service to all users (or UEs) within the broadcast service area. In multicast service, one or more transmitters transmit the service to a dedicated group of users (or UEs). Broadcast service enables UEs to receive the service in any Radio Resource Control (RRC) state, as long as the UE is within coverage area. Unlike multicast service, broadcast service requires the use of specific service announcements related to MBS broadcast service and Public Land Mobile Network (PLMN). Temporary Action Group Identifier (TMGI) is supported as an identifier for MBS broadcast sessions.

[0041] A UE in any RRC state can receive broadcast services. The configuration of MBS broadcast services is provided via System Information Block 20 (SIB20) / Multicast Control Channel (MCCH), which is periodically transmitted in each cell within the MBS service area. The MCCH and broadcast data themselves can be received by the UE in frequency areas known as Common Frequency Resources (CFR).

[0042] For broadcast, the UE receives the Frequency Selection Area Identifier (FSAI) or (for broadcast MBS sessions) identifier applicable to that MBS service via the service announcement of the MBS service (which may be transmitted via unicast or using another broadcast session). Generally, the (MBS) FSAI is used in broadcast MBS sessions to guide the UE's frequency selection. The FSAI is sometimes also referred to as the FSA identifier (FSA ID). Specifically, the (MBS) FSAI identifies a pre-configured area, and the cell announces the MBS FSAI and associated frequencies in and around that pre-configured area. The same FSAI can be applied to multiple MBS services and / or multiple broadcast MBS sessions.

[0043] RAN nodes (e.g., access nodes) can be configured with FSAI. FSAI configuration can be performed via, for example, an Operations, Administration, and Maintenance (OAM) entity. RAN nodes can exchange this information with neighboring RAN nodes. This information can be exchanged via the Xn interface. Based on the FSAI configuration, RAN nodes can inform the SIB of information about the configured MBS FSAI and operating frequencies of the RAN node via the radio interface. That is, in the cell's System Information Block 21 (SIB21), the UE can see the mapping from the FSAI to neighboring cell frequencies (i.e., frequencies used by neighboring RAN nodes of the UE's serving node). The UE can then prioritize neighboring cell frequencies in frequency selection based on the exchanged information. For example, a UE in an RRC idle or inactive state can prioritize the frequencies of cells residing in which the UE is interested in receiving a specific broadcast conversation. The UE can compare the MBS FSAI included in the Service Bulletin with the MBS FSAI included in the SIB to perform frequency selection. It should be noted that the UE may also, or alternatively, directly receive the frequencies providing the service from the service announcement. In that case, the UE can directly prioritize the frequencies indicated in the service announcement. Therefore, the UE may not necessarily need FSAI or SIB21 for frequency selection.

[0044] When a broadcast MBS meeting occurs, the AF can provide the MBS FSAI based on the (enterprise) protocol. If the AF does not provide the MBS FSAI, the MB-SMF can determine the MBS FSAI based on a pre-configured mapping from the MBS service area and / or broadcast MBS meeting information (e.g., application ID) to the MBS FSAI, and send the determined MBS FSAI to the AF (optionally via the NEF).

[0045] In some cases, during the start and update of an MBS conversation for broadcast, the MB-SMF may include an MBS FSAI for the MBS conversation and send it to the RAN node via the Application Management Function (AMF). The RAN node can then use the MBS FSAI to determine cells and / or frequencies within the MBS service area to broadcast MBS conversation data.

[0046] The following provides a more detailed discussion of the background and context for providing the content used in the embodiments of the reduced capability UE or terminal device. A reduced capability (RedCap) terminal device is a terminal device with certain predefined bandwidth (BW) limitations. That is, a RedCap terminal device cannot use a receive bandwidth greater than a predefined maximum bandwidth (e.g., 20 MHz). If the initial bandwidth portion (BWP) of the system exceeds such limitations, the RedCap terminal device utilizes an initial BWP configured, for example, separately via System Information Block 1 (SIB1). If the CFR of the MBS is properly configured for the RedCap terminal device, the RedCap terminal device may be able to receive broadcast data. That is, broadcast data reception is possible as long as the CFR bandwidth is less than or equal to the bandwidth supported by the RedCap terminal device. Services (e.g., MBS) can be delivered in a dedicated RedCap CFR. This depends on which CFR should utilize the access node (e.g., gNB) for a specific service, because there is no instruction from the core network to the access node for broadcast conversations that will be received by non-RedCap / RedCap terminal devices.

[0047] As described above, a new RedCap MBS CFR, different from the earlier Broadcast MBS CFR, has been introduced for broadcast control and data reception. It is assumed that some services will be transmitted in the RedCap CFR and the choice of whether to use this type of CFR is left to the OAM configuration.

[0048] Non-RedCap terminal devices were not expected to read the RedCap CFR, and RedCap terminal devices were unable to read the non-RedCap CFR due to capability limitations. Therefore, if a broadcast service targets both RedCap and non-RedCap terminal devices, the access nodes should transmit the same service in two different CFRs. For this reason, separate SIB20 and MCCH are used for RedCap terminal devices. In cases where one or more access nodes in a particular TMGI service area do not utilize a separate RedCap CFR (e.g., due to the access node not being configured for this function, or due to congestion leading to a decision to transmit service only in the non-RedCap CFR), same-frequency selection guidance does not apply to both RedCap and non-RedCap terminal devices. That is, if same-frequency selection guidance based on a separate RedCap CFR is used, RedCap terminal devices will be able to receive service only in some cells of the service area.

[0049] Therefore, a new mechanism is needed to guide RedCap and non-RedCap terminal devices to receive broadcast services (e.g., MBS) differently in cell reselection decisions. The embodiments discussed below are used to provide such a mechanism.

[0050] Figure 2 illustrates a procedure for performing informed cell reselection decisions according to an embodiment. The procedure illustrated in Figure 2 can be executed by a terminal device (or UE) or a portion thereof. Here, the terminal device can be one of UE 100 or UE 102 in Figure 1. The terminal device can be a RedCap terminal device or a non-RedCap terminal device. In the following text, for simplicity, the entity executing the procedure of Figure 2 will be referred to as a device.

[0051] Referring to Figure 2, in block 201, the device receives a service announcement from the MBS. The service announcement received in block 201 may correspond to a broadcast transmission. The service announcement may be transmitted (or broadcast) by an access node (e.g., a gNB). The service announcement may be initiated by an AF.

[0052] The service announcement for block 201 includes at least one of the following: 1) at least one FSAI and at least one indication indicating that the at least one FSAI is defined for use with a RedCap terminal device, or 2) at least one frequency and at least one indication indicating that the at least one frequency is defined for use with a RedCap terminal device. The at least one FSAI and / or at least one frequency is associated with the MBS indicated in the service announcement. In other words, a new indication for at least one FSAI or at least one frequency (or both) is included in the service announcement to indicate that the at least one FSAI or frequency is specifically used to direct a RedCap terminal device to an adjacent cell frequency, by which MBS can be provided according to the BWP limitation of the RedCap UE using that adjacent cell frequency. Based on at least one indication (of any type mentioned above), the receiving device is able to distinguish between FSAIs / frequency optimized for RedCap and non-RedCap.

[0053] In some alternative embodiments, at least one (new) instruction discussed in the preceding paragraphs may be received in a message other than a service announcement.

[0054] In some embodiments, the service announcement for block 201 may further include at least one FSAI or at least one frequency without any indication that the at least one FSAI or at least one frequency will be defined for use with RedCap terminal devices. In other words, at least another FSAI or frequency may not be associated with any indication that the at least another FSAI / frequency is defined for use with RedCap terminal devices. However, it should be emphasized that even if the at least another FSAI / frequency is not specifically adapted for use with RedCap terminal devices, it may still be used with at least some RedCap terminal devices in some cases.

[0055] In some embodiments, for at least one of at least one FSAI or at least one frequency defined for use with a RedCap terminal device, the service announcement may further include information regarding at least one bandwidth limitation condition, which indicates that the at least one FSAI or at least one frequency defined for use with a capability-reduced terminal device is subject to. The at least one bandwidth limitation condition may include, for example, at least one condition specifying a limitation regarding the terminal device type (e.g., UE type 1 only) and / or at least one condition specifying a limitation regarding bandwidth or bandwidth portion (e.g., a 100 MHz bandwidth limitation). Here, it is assumed that the terminal device type is associated with a bandwidth or band that can be used by a terminal device of the defined type. For example, each terminal device type is associated with at least one bandwidth or at least one band. The terminal device may store information in memory regarding the mapping between one or more terminal device types and lists of one or more associated bandwidths and / or bands. At least one FSAI and / or at least one frequency can be used by the terminal device only if the terminal device satisfies or is compatible with at least one bandwidth limitation condition.

[0056] A device (e.g., a terminal device) may be in any RRC state when it receives a service announcement for an MBS in block 201. After receiving the service announcement for an MBS, the device may transition to an RRC inactive or idle state and begin receiving the MBS specified in the service announcement.

[0057] Subsequently, in block 202, the device performs a cell reselection procedure based on cell measurement and service announcement. Specifically, in addition to cell measurement, the cell reselection procedure may also employ the at least one FSAI and at least one associated indicator (Option 1) or the at least one frequency and at least one associated indicator (Option 2).

[0058] Cell measurements can be performed by the device itself. Cell measurements can include measurements of signals transmitted by one or more access nodes. Cell measurements can include measurements of at least one of the following: Reference Signal Received Power (RSRP), Reference Signal Receiver Quality (RSRQ), Signal-to-Noise Ratio (SNR), or Signal-to-Interference Plus Noise Ratio (SINR). Cell measurements can include measurements involving one or more (radio) frequencies (used in one or more adjacent cells). Cell measurements can include any cell measurement performed in the RRC non-operational or idle state as defined in 3GPP TS 38.306 and / or TS 38.304.

[0059] How the service announcement is used in the cell reselection procedure depends on whether the device is a RedCap terminal device (or a portion thereof) or a non-RedCap terminal device (or a portion thereof).

[0060] If the device is a RedCap terminal device (or part thereof), then the cell reselection procedure based on the service announcement in block 202 may include: in the cell reselection procedure, prioritizing frequencies associated with at least one FSAI or at least one frequency defined for use with a RedCap terminal device. In this context and in the following discussion of block 202, the prioritized frequency may specifically refer to adjacent cell frequencies (i.e., frequencies used in one or more adjacent cells of the terminal device). Adjacent cell frequencies are the operating frequencies of adjacent cells of a service cell of the device. If the service announcement in block 201 contains the aforementioned FSAIs or frequencies not defined for use with a RedCap terminal device, then in the cell reselection procedure, the device may specifically prioritize frequencies associated with at least one FSAI or at least one frequency defined for use with a RedCap terminal device over frequencies not defined for use with one or more FSAIs or one or more frequencies. Alternatively, if one or more FSAIs or frequencies used for a RedCap terminal device are not available in the current cell of the device (e.g., due to SIB21 not containing a corresponding FSAI to an adjacent cell mapping), the device may prioritize one or more undefined FSAIs or frequencies used for a RedCap terminal device over at least one defined FSAI or frequency used for a RedCap terminal device. If the device's limitations allow it to receive non-RedCap CFRs, the device may still be able to receive MBS in non-RedCap CFRs.

[0061] If the device is not a RedCap terminal device (or part thereof), the cell reselection procedure based on the service announcement in block 202 may include: in the cell reselection procedure, avoiding or ignoring frequencies associated with at least one FSAI or at least one frequency defined for use with a RedCap terminal device.

[0062] If the device is a non-RedCap terminal device (or part thereof) and the service announcement of block 201 also includes the aforementioned FSAIs or frequencies not explicitly defined for RedCap terminal devices, then the cell reselection procedure based on the service announcement in block 202 may include: in the cell reselection procedure, giving priority to frequencies associated with one or more FSAIs or frequencies not explicitly defined for RedCap terminal devices over frequencies associated with at least one FSAI or frequency explicitly defined for RedCap terminal devices. Alternatively, if one or more FSAIs or frequencies for non-RedCap terminal devices are not available in the current cell of the device (e.g., due to SIB21 not containing a corresponding FSAI to adjacent cell mapping), the device may give priority to at least one FSAI or frequency defined for RedCap terminal devices over one or more FSAIs or frequencies defined for non-RedCap terminal devices. This may be used, for example, in scenarios where service is provided only in RedCap CFR (and normal terminal devices are directed to RedCap CFR).

[0063] If the device is a RedCap terminal device and the service announcement for block 201 contains information regarding at least one bandwidth limitation condition, which indicates that at least one FSAI or at least one frequency defined for use by the RedCap terminal device is followed, then the device may perform the following operations. First, for at least one frequency or at least one FSAI associated with the at least one bandwidth limitation condition, the device may determine whether the RedCap terminal device satisfies the at least one bandwidth limitation condition. Subsequently, in a cell reselection procedure, the device may prioritize frequencies associated with at least one FSAI or at least one frequency for which the RedCap terminal device satisfies the at least one bandwidth limitation condition.

[0064] In some more general embodiments, the device may receive a service announcement for MBS and, in the service announcement or in at least one message following the service announcement (or both), receive at least one indication indicating that adjacent cells support all or at least some RedCap terminal devices for MBS (or MBS conversation). These at least some RedCap terminal devices may correspond to, for example, RedCap terminal devices that meet at least one UE type or bandwidth limitation. The at least one message following the service announcement may include, for example, at least one SIB21 message. Subsequently, the device may perform a cell reselection procedure based on cell measurements and at least one indication (and optionally, also based on the service announcement), similar to that described in block 201.

[0065] Figure 3 illustrates a procedure for performing informed cell reselection decisions according to an embodiment. The procedure illustrated in Figure 3 can be executed by a terminal device (or UE) or a portion thereof. Here, the terminal device can be one of UE 100 or UE 102 in Figure 1. The terminal device can be a RedCap terminal device or a non-RedCap terminal device. In the following text, for simplicity, the entity executing the procedure of Figure 3 will be referred to as a device.

[0066] The procedure in Figure 3 largely corresponds to the procedure in Figure 2. The procedure in Figure 3 can be adapted by making necessary modifications to the details, taking into account any of the features and definitions provided in Figure 2.

[0067] Referring to Figure 3, in block 301, the device receives a service announcement from the MBS. The service announcement received in block 301 may correspond to a broadcast transmission. The service announcement may be transmitted via an access node (e.g., a gNB). The service announcement may be initiated by an AF.

[0068] The service announcement in block 301 includes at least the following: at least one frequency and at least one indication that the at least one frequency is defined for use with a RedCap terminal device (i.e., the service announcement corresponds to option 2 discussed in conjunction with block 201). The at least one frequency may include (or consist of) at least one adjacent cell frequency of the device (i.e., at least one frequency of adjacent cells of the device's service cell). The at least one frequency is associated with an MBS indicated in the service announcement. If the frequency associated with the MBS is already given in the service announcement, the UE may directly prioritize that frequency.

[0069] A service announcement may include at least one FSAI and at least one indication that the at least one FSAI is defined for use with a RedCap terminal device. A service announcement may include at least one frequency or at least one FSAI and at least one indication that the at least one frequency or at least one FSAI is defined for use with a RedCap terminal device.

[0070] Upon receiving the MBS service announcement, in block 302, the device receives at least one FSAI-to-frequency mapping containing at least one frequency. Therefore, based on the at least one FSAI-to-frequency mapping, the device can determine at least one FSAI corresponding to at least one frequency. The access node may receive at least one FSAI-to-frequency mapping. The at least one FSAI-to-frequency mapping may form part of the access node's broadcast transmission. Reception in block 302 may include, for example, receiving a SIB21 broadcast containing the at least one FSAI-to-frequency mapping, which contains at least one frequency. During the reception of at least one FSAI-to-frequency mapping in block 302, the device may be in any RRC state. The device may transition to an RRC inactive or idle state and begin receiving the MBS specified in the service announcement.

[0071] Subsequently, in block 303, the device performs a cell reselection procedure based on cell measurements, service announcements, and at least one FSAI-to-frequency mapping. Specifically, in addition to cell measurements and at least one FSAI-to-frequency mapping, the cell reselection procedure may also utilize the at least one (adjacent cell) frequency and the associated at least one indication contained in the service announcement. Besides using at least one FSAI-to-frequency mapping to perform the cell reselection procedure, a cell selection procedure may be performed as described in conjunction with block 202 of FIG2.

[0072] Figure 4 illustrates a procedure according to an embodiment for enabling informed cell reselection decisions. The procedure illustrated in Figure 4 can be executed by an application function (AF) or a portion thereof. Here, the AF may be included in the core network 110 of Figure 1. Dashed lines are used in Figure 4 to indicate selectability features. In the following text, for simplicity, the entity executing the procedure of Figure 4 will be referred to as a device.

[0073] Referring to Figure 4, in block 401, the device transmits the MBS service announcement to at least one terminal device via at least one access node (and optionally, one or more core network nodes). Here, the service announcement includes (similar to what is described in conjunction with the embodiments above) at least one FSAI and at least one indication indicating that the at least one FSAI is defined for RedCap terminal devices, or at least one frequency defined for capability-degraded terminal devices and at least one indication indicating that the at least one frequency is defined for RedCap terminal devices. The at least one frequency may include one or more adjacent cell frequencies of the device (or consist of them). The service announcement may be defined as described in conjunction with the embodiments above. At least one access node may only broadcast / transmit the service announcement without accessing its content.

[0074] In block 402, the device initiates or triggers the MB-SMF to transmit a broadcast MBS session establishment request to at least one access node. This initiation or triggering may include transmitting an MBS session creation (or generation) request for the MBS session to the MB-SMF via the NEF. The MBS session creation (or generation) request may include at least one FSAI and at least one indication indicating that the at least one FSAI is defined for use with RedCap terminal devices. Upon receiving the MBS session creation request, the MB-SMF may use at least one indication indicating that the at least one FSAI is used to transmit the broadcast MBS session establishment request. This function is described in further detail with reference to Figure 7.

[0075] In some embodiments, block 402 may be omitted. That is, in these embodiments, the transmission of the broadcast MBS session establishment request may still be performed by a device (e.g., AF), but not (directly) triggered by that device; instead, it is triggered by the MB-SMF itself after at least one FSAI is generated for the RedCap terminal device. In these embodiments, the device may still transmit the MBS session creation (or generation) request, but excluding at least one FSAI and at least one indication that the at least one FSAI is defined as being associated with the RedCap terminal device. This functionality is described in further detail with reference to FIG8.

[0076] Figure 5 illustrates the communication between the RedCap terminal device (hereinafter referred to as the terminal device for simplicity), the first access node, the second access node, the third access node, and the core network. The first access node, the second access node, and the third access node (e.g., gNB) can use separate (carrier) frequencies f1, f2, and f3, and separate FSAIs, namely FSAI2, FSAI2, and FSAI1, service cells 1, 2, and 3, respectively. Here, FSAI2 can be a defined FSAI for the RedCap terminal device, while FSAI1 can be a non-defined FSAI for the RedCap terminal device. The terminal device can operate in cell 1. Functions associated with the core network can be performed by the application functions (AF) of the core network that communicate with the network open function (NEF) and the multicast / broadcast session management function (MB-SMF) of the core network. Although Figure 5 illustrates a communication scenario where the first access node providing the (initial) service cell for the terminal device has two adjacent access nodes, the features and functions described below in conjunction with Figure 5 can also be applied to cases where the first access node has a single adjacent access node or more than two adjacent access nodes.

[0077] Referring to Figure 5, as an initial pre-configuration step, in block 501, the access node obtains or receives configuration information from or receives configuration information from an OAM entity. One or more OAM entities may be located in the core network. The configuration information includes at least one indication that at least one FSAI is defined for a capability-reduced terminal device. Here, the at least one FSAI includes at least FSAI2. In other words, in this example, one or more OAM entities configure FSAI2, which is designated for use with a RedCap terminal device. In some embodiments, block 501 may be omitted (i.e., the associated features may be considered optional).

[0078] In some embodiments, the configuration information of block 501 may further define the bandwidth of the CFR defined for the capability reduction terminal device.

[0079] In some embodiments, the configuration information of block 501 may optionally further include a mapping between FSAI and the (operating) frequencies of one or more adjacent cells (provided by the second access node and the third access node).

[0080] In block 502, it is assumed that the terminal device initially operates in any RRC state. During this operation, in message 503, a core network entity (or node or function) of the core network transmits a service announcement for a specific MBS (hereinafter referred to as MBS1) to the terminal device via a first access node, and in block 504, the terminal device receives the service announcement. The core network node that initiates the transmission may be an AF (but the service announcement may also be transmitted via one or more other core network nodes). In response to or based on the receipt of the service announcement, the first access node may forward the service announcement only to the terminal device (or more generally, to one or more terminal devices). In block 504, when the terminal device operates in an RRC connected state, the service announcement may be received by the terminal device via unicast, or when the terminal device operates in any RRC state, the service announcement may be received as a broadcast transmission.

[0081] Generally, a service announcement can be defined as described in conjunction with the preceding embodiments. That is, in this exemplary scenario, the service announcement includes two FSAIs: FSAI1 and FSAI2. Additionally, the service announcement includes FSAI2 as an instruction for RedCap terminal devices (and therefore for RedCap-based cell reselection). The service announcement may be associated with a specific TMGI (used to identify MBS sessions).

[0082] In message 505, a core network entity (or node or function) transmits a broadcast MBS conversation establishment request for a conversation of MBS1 (hereinafter referred to as MBS conversation 1) to the first access node. The broadcast MBS conversation establishment request may, for example, be transmitted by an AF via zero or more other core network nodes to the access node. In the configuration information of block 501, the broadcast MBS conversation establishment request includes at least one FSAI indicated as defined for a RedCap terminal device, and optionally includes one or more FSAIs not indicated as defined for a RedCap terminal device. In this particular instance, the broadcast MBS conversation establishment request includes at least FSAI1 (not specifically for a RedCap terminal device) and FSAI2 (for a RedCap terminal device). Alternatively, the broadcast MBS conversation establishment request may also include an indication that FSAI2 is for a RedCap terminal device (i.e., applicable to RedCap-based cell reselection). In block 506, the first access node receives the broadcast MBS conversation establishment request for MBS conversation 1.

[0083] In some embodiments, for at least one FSAI (e.g., for FSAI2) or at least one frequency, the service announcement received by the terminal device in block 504 and / or the broadcast MBS session establishment request received by the first access node in block 506 includes information regarding at least one bandwidth limitation condition defined for the FSAI or frequency used to degrade the terminal device. In other words, the service announcement and / or broadcast MBS session establishment request may include granularity related to, for example, a UE type limitation of MBS1 (implicitly defining at least one bandwidth limitation) or a bandwidth limitation (e.g., a 100 MHz bandwidth limitation).

[0084] In block 507, the first access node triggers or initiates the transmission of an MBS session (i.e., MBS session 1) within the RedCap CFR based on information obtained in blocks 501 and / or 506. This information may include at least one FSAI (FSAI2 in this example) and at least one indication that the at least one FSAI is defined for use with a RedCap terminal device.

[0085] After triggering the MBS conversation transmission in block 507, the first access node transmits one or more messages 508, 512 to one or more adjacent access nodes. Each of the one or more messages 508, 512 includes at least one FSAI (i.e., FSAI2 in the illustrated example) and at least one indication indicating that the at least one FSAI is defined as being used for a capability-reduced terminal device. In other words, the FSAI transmitted to the adjacent access nodes is supplemented by a RedCap indication (i.e., indicating that the associated FSAI is being used for a RedCap terminal device). In the illustrated example, the one or more adjacent access nodes include a second access node and a third access node. The content of the one or more messages 508, 512 may be derived or generated based on the configuration of the first access node and / or the broadcast MBS conversation establishment request 505.

[0086] One or more messages 508, 512 may be or may specifically include one or more Xn establishment and / or modification messages. In other words, when using another access node (Xn establishment) or establishing a new Xn connection for an existing Xn connection (Xn modification), the first access node transmits FSAI2 in the Xn establishment or modification message 508, 512 along with an implicit or explicit indication that it is currently in use (i.e., the first access node will broadcast the start of transmission of the establishment and transmission trigger FSAI information to adjacent access nodes). It is worth noting that if the first access node does not start transmission in the RCap CFR, it will not transmit FSAI2 to any adjacent access node. Therefore, any adjacent access node can determine that the RCap CFR is in use based on the received FSAI2.

[0087] In the example of Figure 5, in block 509, the second access node receives from the first access node a message containing FSAI2 and an indication that FSAI2 is currently in use (e.g., a message to create or modify Xn), and in block 513, the third access node receives from the first access node a message containing FSAI2 and an indication that FSAI2 is currently in use (e.g., a message to create or modify Xn).

[0088] In some embodiments where FSAI2 and RedCap CFR are also used in a second access node (such as the access node illustrated in Figure 5), in message 510, the second access node may also transmit a message containing FSAI2 and an indication that FSAI2 is currently being used by the second access node (e.g., a message to create or modify Xn) to the first access node. In block 511, this message is received by the first access node. In other embodiments (i.e., when FSAI2 is not currently being used by the second access node), elements 510 and 511 may be omitted.

[0089] In some embodiments of FSAI1 and its associated non-RedCap CFR for use with a third access node (such as the access node illustrated in Figure 5), in message 514, the third access node may also transmit a message containing FSAI1 and an indication that FSAI1 is currently used by the third access node (e.g., a message for creating or modifying Xn) to the first access node. In block 515, this message is received by the first access node. In other embodiments (i.e., when FSAI1 is not currently used by the third access node), elements 514 and 515 may be omitted.

[0090] It should be noted that, with the inclusion of elements 510, 511 and / or elements 514, 515, broadcast MBS session establishment requests can also be transmitted from the core network to the second and / or third access nodes (similar to what is illustrated for the first access node in Figure 5). For the sake of simplicity, these broadcast MBS session establishment requests have been omitted from Figure 5 (i.e., Figure 5 attempts to primarily depict the operation of the first access node rather than fully illustrating the operations of the first, second, and third access nodes).

[0091] In some alternative embodiments (not depicted in Figure 5), the exchange of information between elements 508 to 515 may occur before the transmission and reception of broadcast MBS session establishment requests (elements 505, 506). The content of the transmitted messages 508 / 510 / 512 / 514 may be derived or generated based on the configuration of the transport access node.

[0092] In some embodiments, elements 508 to 515 may be omitted. For example, it may be assumed that in some embodiments, the FSAI configuration is (relatively) static, and therefore it is not necessary to transmit the FSAI and associated RedCap indication after the initial configuration or after transmitting the broadcast MBS session establishment request.

[0093] In message 516, the first access node transmits at least a mapping between at least one FSAI defined for a capability-degraded terminal device and at least one frequency (i.e., an FSAI-to-frequency mapping). The mapping may be generated or formed by the first access node based on messages received in blocks 511 and / or 515 (e.g., Xn establishment or modification messages). In block 516, the terminal device receives this mapping. Message 516 may be SIB21. The transmission of message 516 may correspond to a broadcast. Generally, the information transmitted in message 516 may include mappings between any FSAI received in blocks 511 and / or 515 and frequencies associated with those FSAIs. The same FSAI may also be defined in a service announcement (but the first access node itself cannot access the content of the service announcement). In a specific example of Figure 5, the transmitted information in the form of SIB21 includes FSAI2 to f2 mappings and FSAI1 to f3 mappings.

[0094] After receiving the mapping (e.g., SIB21), in block 518, the terminal device operates in an RRC idle or inactive state. Similar to what has been described in conjunction with previous embodiments, in block 519, the terminal device performs cell measurement via the first access node, the second access node, and the third access node. Based on these cell measurements and the service announcement (and mapping where the service announcement does not include a frequency), in block 520, the terminal device performs cell reselection. In the example of FIG5, since this frequency is specifically defined for RedCap terminal devices, the terminal device can consider f2 as the highest priority for cell reselection. Alternatively, the terminal device can consider f2 as the highest priority for cell reselection only if FSAI2 complies with the terminal device's limitations, i.e., the terminal device meets at least one bandwidth limitation defined in the service announcement. An example of this cell reselection is discussed below in conjunction with FIG6A and FIG6B.

[0095] While in some embodiments the use of RedCap / non-RedCap CFRs at the access node may correspond to a (relatively) static configuration, in other embodiments, the use of RedCap / non-RedCap CFRs can be adjusted more dynamically based on the decisions of a given access node (i.e., it is not statically configured). In this more dynamic embodiment, for example, the indication of the FSAI to frequency mapping used in SIB21 (message 516) can be more dynamically adapted to enable appropriate cell reselection at the terminal device. For that purpose, in the Xn communication (elements 508 to 515) of the configured FSAI to the adjacent access node, non-RedCap and / or RedCap FSAIs are included only if the given MBS is currently being transmitted in the corresponding CFR. In other words, the access node may not necessarily share all the configured FSAIs in the Xn setup / modification messages transmitted to the adjacent access node, but only the FSAI associated with the CFR currently in use.

[0096] Figures 6A and 6B illustrate two alternative communication scenarios for performing cell reselection in block 520 of Figure 5. Therefore, the procedures in Figures 6A and 6B can be performed after the procedures for elements 501 to 519 of Figure 5 are completed. The RedCap terminal device (hereinafter referred to simply as the terminal device), the first access node, the second access node, and the third access node, as well as the core network in Figures 6A and 6B, can be defined as described in conjunction with Figure 5.

[0097] Referring to Figure 6A, and as also described in conjunction with Figure 5, the terminal device prioritizes the frequency f2 defined for RedCap terminal devices during cell reselection (i.e., when searching for a cell to be selected). Therefore, in block 601, the terminal device initially attempts but fails to find a suitable cell for cell reselection using frequency f2 based on cell measurement results. Next, the terminal device attempts to find a suitable cell at a frequency f3 that is not specifically defined for RedCap terminal devices. That is, the terminal device knows that, in addition to the preferred but unavailable frequency f2, it must also use frequency f3 to provide MBS1 / MBS conversation 1. In block 602, the terminal device finds cell 3 using frequency f3 and reselects cell 3 in block 603. In other words, the terminal device transitions from the current cell 1 to the new cell 3. In block 604, the terminal device operates in cell 3 in an RRC inactive or idle state. In other words, the terminal device begins to reside in cell 3. Finally, in message 605, the third access node transmits MBS1 / MBS conference 1 to the terminal device via cell 3. In block 606, the terminal device receives MBS1 / MBS conference 1. In this example, it is assumed that the non-RedCap CFR of message 605 is compatible with the RedCap terminal device and its bandwidth limitations, and therefore MBS1 / MBS conference 1 is successfully received via cell 3. If this is not the case, MBS1 / MBS conference 1 cannot be successfully received.

[0098] Referring to Figure 6B, and as described in conjunction with Figures 5 and 6A, the terminal device prioritizes the frequency f2 defined for the RedCap terminal device during cell reselection (i.e., when searching for a cell to be selected). Therefore, in block 611, the terminal device initially attempts to find a suitable cell for cell reselection using frequency f2 based on cell measurement results. In this example, in block 611, it is assumed that the terminal device successfully finds cell 2 suitable for cell reselection using frequency f2. In block 612, the terminal device reselects cell 2. In other words, the terminal device transitions from the current cell 1 to the new cell 2. In block 613, the terminal device operates in cell 2 in an RRC inactive or idle state. In other words, the terminal device begins residing in cell 2. Finally, in message 614, the second access node transmits MBS1 / MBS conversation 1 to the terminal device via cell 2. In block 615, the terminal device receives MBS1 / MBS conversation 1. When frequency f2 is specifically defined for use with a RedCap terminal device, compatibility cannot be achieved because the terminal device is a RedCap terminal device (in contrast to the example in Figure 6A).

[0099] Figures 7 and 8 illustrate two alternative core network communication scenarios between the MB-SMF, NEF, and AF of the core network according to an embodiment capable of performing cell reselection. Specifically, Figures 7 and 8 illustrate the procedure for creating an FSAI instruction for a RedCap-specific cell reselection. These procedures also cause or enable the transmission of an MBS session establishment request from the AF to at least one access node, as discussed in conjunction with previous embodiments. The procedures of Figures 7 and 8 can be performed after any of the procedures discussed in conjunction with Figures 2 through 5, Figures 6A and 6B. It can be assumed that the AF of Figures 7 and 8 provides at least one MBS.

[0100] In the communication scenario of Figure 7, the AF is configured to provide FSAI for the MBS (or MBS conversation). In Figure 7, it is assumed that the AF knows (e.g., based on a predefined protocol) a specific MBS whose target is a RedCap terminal device (and optionally a non-RedCap terminal device). In other words, the AF knows the UE type targeted by the MBS.

[0101] In elements 701 to 703, the AF transmits the MBS session creation request to the MB-SMF via the NEF, enabling the MBS session establishment request to be transmitted to at least one access node. Specifically, in message 701, the AF transmits a first MBS session creation request to the NEF. Here, the first MBS session creation request includes at least one FSAI and at least one indication indicating that the at least one FSAI is defined for use with a RedCap terminal device. Alternatively, the first MBS session creation request may also include one or more FSAIs not specifically for use with a RedCap terminal device (i.e., it is not accompanied by an indication that it will be defined for use with a RedCap terminal device). The NEF receives the first MBS session creation request in block 702 and transmits a second MBS session creation request to the NEF in message 703. The above description of the first MBS session creation request also applies to the second MBS session creation request (i.e., the NEF can actually forward the contents of the first MBS session creation request to the MB-SMF). Therefore, the second MBS session creation request also includes at least one FSAI and at least one (RedCap related) instruction, and optionally includes one or more FSAIs without such instructions. The first MBS session creation request (message 701) may be an Nnef_MBS_NBSSession_Create_Request message. The second MBS session creation request (message 703) may be an Nmbsmf_MMBSSession_Create_Request message.

[0102] In some embodiments, for at least one of the at least one FSAI defined for use with the RedCap terminal device, the first MBS session creation request and the second MBS session creation request may also include information regarding at least one bandwidth limitation condition that is followed by the FSAI (or frequency) defined for use with the RedCap terminal device. In other words, the first MBS session creation request and the second MBS session creation request may include granularity related to, for example, UE type restrictions (implicitly defining at least one bandwidth limitation) or bandwidth restrictions (e.g., a 100 MHz bandwidth restriction) for the MBS1 session.

[0103] In block 704, the MB-SMF receives a second MBS session creation request from the NEF. Subsequently, the MB-SMF may use at least one indication in other interactions with one or more access nodes (not shown in Figure 7). That is, the MB-SMF may subsequently transmit a broadcast MBS session establishment request for that MBS, wherein the broadcast MBS session establishment request includes at least one FSAI and at least one indication indicating that the at least one FSAI is defined for use with a RedCap terminal device.

[0104] After receiving the response in block 704, the MB-SMF transmits the first MBS session creation response back to the NEF in message 705. After receiving the first MBS session creation response in block 706, the NEF transmits the second MBS session creation response to the AF in message 707. In block 708, the AF receives the second MBS session creation response. The first and second MBS session creation responses are only used to confirm that the second MBS session creation request was successfully received at the MB-SMF. The first MBS session creation response (message 705) can be an Nmbsmf_MMBSSession_Create_Response message. The second MBS session creation response (message 707) can be an Nnef_MBSSession_Create_Response message.

[0105] In some embodiments, elements 705 to 708 may be omitted.

[0106] As mentioned above, Figure 8 illustrates an alternative core network communication scenario to the core network communication in Figure 7. The fundamental difference between the two solutions is that in the communication scenario of Figure 8, the AF is not configured to provide FSAI for the MBS (or MBS conversation) as shown in Figure 7. Instead, the FSAI is generated by the MB-SMF.

[0107] Referring to Figure 8, in elements 801 to 803, the AF transmits the MBS session creation request to the MB-SMF via the NEF, enabling the MBS session establishment request to be transmitted to at least one access node, similar to Figure 7. However, here, no FSAI or associated RedCap indication is included in the MBS session creation request because the AF is unaware of the FSAI or associated RedCap indication. Therefore, more specifically, in message 801, the AF transmits the first MBS session creation request to the NEF. The NEF receives the first MBS session creation request in block 802 and transmits the second MBS session creation request to the NEF in message 803. Neither the first nor the second MBS session creation request may contain any FSAI or associated indication related to the MBS session to be created. The first MBS session creation request (message 801) may be an Nnef_MBS_NBSSession_Create_Request message. The second MBS session creation request (message 803) can be the Nmbsmf_MMBSSession_Create_Request message.

[0108] In block 804, the MB-SMF receives a second MBS session creation request from the NEF. Subsequently, in block 805, the MB-SMF generates (or produces or determines) at least one FSAI for a RedCap terminal device, and optionally generates one or more FSAIs not specifically defined for RedCap terminal devices. This generation (or production or determination) may be based on pre-configuration information or on another indication received from the AF that indicates the service is for RedCap / non-RedCap terminal devices. The pre-configuration information may include predefined mappings, such as mappings between MBS service areas and FSAIs. Alternatively, the predefined mappings may be mappings between broadcast MBS session information (e.g., application identifier ID) and FSAIs, or mappings between a combination of MBS service areas and broadcast MBS session information (e.g., application identifier ID) and FSAIs. Furthermore, in block 806, the MB-SMF generates or produces at least one indication indicating that the at least one FSAI (determined in block 805) is defined for a RedCap terminal device.

[0109] In message 807, the MB-SMF transmits the first MBS session creation response back to the NEF. Here, the first MBS session creation request includes at least one FSAI (and optionally one or more non-RedCap-specific FSAIs) generated in block 805 for a RedCap terminal device and at least one (RedCap) indication generated in block 806. After receiving the first MBS session creation response in block 808, the NEF transmits the second MBS session creation response to the AF in message 809. The second MBS session creation response also includes at least one FSAI (and optionally one or more non-RedCap-specific FSAIs) generated in block 805 for a RedCap terminal device and at least one (RedCap) indication generated in block 806. In block 810, the AF receives the second MBS session creation response. The AF may store the contents of the second MBS session creation response in memory. Therefore, the first MBS session creation response and the second MBS session creation response are used here not only to confirm that the second MBS session creation request was successfully received at the MB-SMF, but also to transmit the generated FSAI and instructions back to the AF. The first MBS session creation response (message 807) can be an Nmbsmf_MMBSSession_Create_Response message. The second MBS session creation response (message 809) can be an Nnef_MBSSession_Create_Response message.

[0110] In some embodiments, elements 807 to 810 may be omitted.

[0111] It should be noted that although Figures 7 and 8 illustrate the creation of a meeting without Policy Control Check (PCC), similar decisions and procedures can be made and applied during the creation of a meeting with PCC. If PCC is used, some of the communication interactions between AF and MB-SMF discussed in Figures 7 and / or 8 can be subject to further checks, and the specific names of the messages may differ, but the basic principles of operation remain unchanged.

[0112] The above embodiments are based on the introduction of new instructions for FSAI in the MBS service bulletin. These new instructions indicate that a specific FSAI / frequency is used to guide RedCap terminal devices to adjacent cell frequencies, where the MBS will provide this according to the limitations of the RedCap terminal device. Therefore, in these embodiments, RedCap-specific guidance is primarily driven and implemented by the core network. In other embodiments, this may not be the case. That is, in some other embodiments, RedCap-specific guidance may be primarily driven and implemented by the RAN. In these embodiments, RedCap-specific additional information may be omitted from the service bulletin (i.e., the service bulletin is not enhanced), and the corresponding information may actually be determined and communicated by the terminal device, rather than by the server access node. In these embodiments, the service bulletin generally still provides information about the FSAI of adjacent access nodes, but the FSAI supported by RedCap is not specifically indicated therein.

[0113] Figure 9 illustrates a procedure for performing informed cell reselection decisions according to an embodiment. The procedure illustrated in Figure 9 can be executed by a terminal device (or UE) or a portion thereof. Here, the terminal device can be one of UE 100 or UE 102 in Figure 1. The terminal device can be a RedCap terminal device or a non-RedCap terminal device. In the following text, for simplicity, the entity executing the procedure of Figure 9 will be referred to as a device.

[0114] Referring to Figure 9, the illustrated function can be executed upon receiving a service announcement for MBS meetings. This service announcement may define one or more FSAIs for MBS meetings, but it may not include any of the RedCap terminal device-specific information discussed in conjunction with previous embodiments (e.g., in conjunction with block 201 of Figure 2). Therefore, the device still needs to be able to execute such information for cell reselection in an optimal manner. The device can operate in RRC inactive or idle state at the start of the procedure in Figure 9 (and during blocks 901, 902).

[0115] In block 901, the device receives neighbor cell frequency information. This neighbor cell frequency information contains a mapping between at least one neighbor cell frequency of at least one neighbor cell and at least one FSAI used for at least one MBS session. Here and below, neighbor cell frequency refers to the operating frequency of neighbor cells of the device's service cells. The neighbor cell frequency information may relate to one or more neighboring access nodes. The neighbor cell frequency information may be received from the access node. The neighbor cell frequency information may be received as part of a broadcast transmission.

[0116] In block 902, the device receives at least one indication. Each indication may be associated with a single neighboring cell or multiple neighboring cells (at least one indication, thus providing information about one or more distinct neighboring cells together). Each indication provides information about RedCap support capabilities associated with at least one FSAI or at least one MBS session, or at least provides information that can be used to determine such RedCap support capabilities. That is, each of the at least one indication indicates at least one of the following: • Is the RedCap terminal device supported for at least one FSAI or at least one MBS meeting? • Supported by at least one type of RedCap terminal device for at least one FSAI or at least one MBS conversation, or • Can be used for at least one size of CFR in at least one FSAI or at least one MBS meeting. The bulleted information types listed above can be displayed for adjacent cells (that is, the information can be specific to adjacent cells).

[0117] The type of RedCap terminal device can be associated with the bandwidth or frequency band supported by the RedCap terminal device. For example, a Type 1 device can be a RedCap terminal device that supports bandwidth size 1, and a Type 2 device can be a RedCap terminal device that supports bandwidth size 2. In some embodiments, if no RedCap terminal device type is supported for at least one FSAI or at least one MBS session, it indicates that an indication of at least one RedCap terminal device type can obtain a null value (or other predefined value).

[0118] In some embodiments, at least one type of RedCap terminal device that supports CFR is associated with at least one (maximum) bandwidth size supported by the RedCap terminal device.

[0119] It should be noted that at least one size of the CFR (or equivalent CFR bandwidth) can be used by the device to determine whether it supports a general RedCap terminal device or a RedCap terminal device of a specific type of RedCap by comparing the bandwidth supported by (a certain type of) RedCap terminal device with at least one size of the CFR. Therefore, all the indication types listed above enable the device to consider the RedCap terminal device support capabilities of adjacent cells when performing cell reselection.

[0120] At least one indication in block 902 may be associated with at least one neighboring cell (and provide information about at least one neighboring cell). Each of the at least one indication in block 902 may be associated with a different neighboring cell (or a different set of one or more neighboring cells). Thus, a given indication defined for a neighboring cell may indicate at least one of the following: whether a capability-degraded terminal device is supported for at least one FSAI or at least one MBS conversation at that neighboring cell; at least one type of RedCap terminal device supported for at least one FSAI or at least one MBS conversation at that neighboring cell; or at least one size of CFR available for at least one FSAI or at least one MBS conversation at that neighboring cell.

[0121] At least one indication of block 902 may be received from an access node (e.g., an access node transmitting adjacent cell frequency information). At least one indication of block 902 may be received as a broadcast transmission or as part of a broadcast transmission.

[0122] In some embodiments, the information received in blocks 901 and 902 may form (different) portions of a single message. This single message may be, for example, an SIB21 message. The SIB21 message may further include a mapping between at least one FSAI and at least one frequency defined according to a previous service announcement for the RedCap terminal device.

[0123] In some embodiments, the information received in blocks 901, 902 (e.g., in the form of SIB21 messages) corresponds to information regarding at least one neighboring cell frequency, and for each of the at least one neighboring cell frequency, it corresponds to one or more datasets. The at least one neighboring cell frequency may relate to one or more different neighboring cells provided by a single neighboring access node or one or more different neighboring access nodes. Each dataset associated with a given neighboring cell frequency contains FSAI for MBS sessions, and the at least one indication in block 902 explicitly or implicitly describes support for RedCap terminal devices.

[0124] In block 903, the device performs a cell reselection procedure based on cell measurements and adjacent cell frequency information, as well as at least one instruction.

[0125] Cell measurements in Block 903 can be performed by the device itself. Cell measurements may include measurements of signals transmitted by one or more access nodes that provide adjacent cells (i.e., adjacent to the device's currently serving cell). Cell measurements may include measurements of at least one of the following: Reference Signal Received Power (RSRP), Reference Signal Receiver Quality (RSRQ), Signal-to-Noise Ratio (SNR), or Signal-to-Interference Plus Noise Ratio (SINR). Cell measurements may include measurements involving one or more (radio) frequencies (used in one or more adjacent cells). Cell measurements may include any cell measurements performed in the RRC non-operational or idle state as defined in 3GPP TS 38.306 and / or TS 38.304.

[0126] In some embodiments, the device is a RedCap terminal device and at least one indication in block 902 indicates that the RedCap terminal device is supported for at least one FSAI, without indicating any of the at least one size of the CFR for at least one FSAI and at least one type of RedCap terminal device supported for at least one FSAI (i.e., only basic information about RedCap support is provided). In these embodiments, the device may prioritize any adjacent cell frequency associated with at least one indication in the cell reselection procedure of block 903, which indicates that the capability-reduced terminal device is supported for at least one FSAI or at least one MBS conversation. In other words, any adjacent cell frequency associated with at least one FSAI or at least one MBS conversation indicated as supporting a RedCap terminal device may be prioritized. Alternatively, the device may prioritize any adjacent cell frequency associated with at least one indication in the cell reselection procedure of block 903, which indicates that the capability-reduced terminal device is supported for at least one FSAI or at least one MBS conversation only if the BWP limitation (or other limitation) of the terminal device allows the terminal device to receive MBS in the associated adjacent cell.

[0127] In some embodiments, the device is a RedCap terminal device and at least one indication of block 902 indicates at least one size of a CFR for at least one FSAI or at least one MBS session. In these embodiments, during the cell reselection procedure of block 903, the device may prioritize at least one adjacent cell frequency (or any adjacent cell frequency) associated with one of the sizes of CFRs supported by the RedCap terminal device (i.e., the device).

[0128] In some embodiments, the device is a RedCap terminal device and at least one indication in block 902 indicates at least one type of terminal device with reduced capability for at least one FSAI or at least one MBS session. In these embodiments, during the cell reselection procedure in block 903, the device may prioritize at least one adjacent cell frequency (or any adjacent cell frequency) associated with a type of RedCap terminal device corresponding to the RedCap terminal device (i.e., the device).

[0129] In some embodiments, two of the prioritization functions discussed in the two preceding paragraphs may be implemented.

[0130] In some embodiments, the device is a non-RedCap terminal device (i.e., a terminal device not defined as a RedCap terminal device). In these embodiments, during the cell reselection procedure of block 903, the device may prioritize at least one adjacent cell frequency (or any adjacent cell frequency) that does not support RedCap terminal devices. In this way, any adjacent cell frequency defined for RedCap terminal devices remains available for RedCap terminal devices (the selection of adjacent cell frequencies for such RedCap terminal devices is more limited compared to that for non-RedCap terminal devices). Whether a given adjacent cell frequency supports a RedCap terminal device can be determined based on at least one indication and adjacent cell frequency information. Alternatively, during the cell reselection procedure of block 903, the device (if it is a non-RedCap terminal device) may avoid or ignore any adjacent cell frequencies that support RedCap terminal devices.

[0131] Figure 10 illustrates a procedure according to an embodiment for enabling informed cell reselection decisions to be performed. The procedure illustrated in Figure 10 may be executed by an access node or a portion thereof. An access node may be, for example, access node 104 of Figure 1. In the following text, for simplicity, the entity executing the procedure of Figure 4 will be referred to as a device.

[0132] Referring to Figure 10, in block 1001, the device receives at least one indication from at least one adjacent access node. This at least one indication provides information regarding the RedCap terminal device support capabilities of the at least one adjacent access node. Specifically, the at least one indication indicates at least one of the following: • Whether the capability-reduced terminal device is supported at at least one of the adjacent access nodes for at least one FSAI or at least one MBS conversation. • At the adjacent access node (or in the adjacent cell provided by the adjacent access node), at least one type of RedCap terminal device is supported for at least one FSAI or at least one MBS conversation. • At least one size of CFR used for at least one FSAI or at least one MBS session at adjacent access nodes, or • Currently, the CFR is of at least one type used by adjacent access nodes for at least one FSAI or at least one MBS session.

[0133] Here, an adjacent access node can be defined as an access node adjacent to the device (and thus provides one or more cells adjacent to one or more cells provided by the device). The at least one type of RedCap terminal device supported at the adjacent access node for at least one FSAI or at least one MBS conversation may have been determined based on the available CFRs in the associated adjacent cells.

[0134] At least one indication in block 1001 may be associated with at least one adjacent access node (and provide information about at least one adjacent access node). In block 1001, the device may receive indications from each of the at least one adjacent access node. Therefore, each of the at least one indication in block 1002 may be associated with different adjacent access nodes. Each indication may be associated with one or more adjacent cells provided by the adjacent access nodes (i.e., providing information about one or more adjacent cells).

[0135] In some embodiments, at least one indication of block 1001 may be included in the Xn creation or modification message or response.

[0136] In block 1002, the device transmits neighbor cell frequency information to the terminal device. This neighbor cell frequency information includes a mapping between at least one neighbor cell frequency and at least one FSAI used for at least one MBS session. Here, the neighbor cell frequency is the operating frequency of the neighbor cells of the service cell provided by the device. Generally, the neighbor cell frequency information transmitted in block 1002 can be defined as described above in conjunction with the corresponding receiving steps of block 901 in FIG9. The transmission in block 1002 can correspond to a broadcast transmission.

[0137] In block 1003, the device transmits at least one indication to the terminal device. The at least one indication indicates at least one of the following for at least one neighboring cell provided by at least one neighboring access node: • Whether the reduced-capacity terminal device is supported for at least one FSAI or at least one MBS meeting. • Supported by at least one type of terminal device with reduced capability for at least one FSAI or at least one MBS conversation, or • Can be used for at least one size of CFR in at least one FSAI or at least one MBS meeting.

[0138] The device can derive or generate at least one indication for block 1003 based on at least one indication for block 1001. Generally, at least one indication transmitted in block 1003 can be defined as described above in conjunction with the corresponding receiving steps of block 902 in FIG9. The transmission of block 1003 can correspond to a broadcast transmission.

[0139] In some embodiments, the information transmitted (or broadcast) in blocks 1002 and 1003 may be contained in a single message. This single message may be, for example, an SIB21 message.

[0140] Figure 11 illustrates another procedure according to an embodiment for enabling informed cell reselection decisions to be performed. The procedure illustrated in Figure 11 may be executed by an access node or a portion thereof. An access node may be, for example, access node 104 of Figure 1. In the following text, for simplicity, the entity executing the procedure of Figure 4 will be referred to as a device.

[0141] In block 1101, the device receives from each of one or more adjacent access nodes at at least one TMGI associated with at least one MBS conversation taking place at an adjacent access node, and for each of the at least one TMGI, receives at least one indication relating to the RedCap terminal device support capability of the TMGI of a given adjacent access node. The at least one indication indicates at least one of the following: • Is the RedCap endpoint supported for TMGI at adjacent access nodes? • At least one type of RedCap terminal device supported for TMGI at adjacent access nodes, or • At least one size of the CFR used for TMGI at adjacent access nodes.

[0142] In block 1102, the device transmits neighbor cell frequency information to the terminal device. This neighbor cell frequency information includes a mapping between at least one neighbor cell frequency and at least one FSAI used for at least one MBS session. Here, the neighbor cell frequency is the operating frequency of the neighbor cells of the service cell provided by the device. The neighbor cell frequency information can be derived or generated based on at least one TMGI, at least one indicator, and the mapping between at least one TMGI and at least one FSAI used for at least one MBS session.

[0143] In block 1103, the device transmits at least one indication to the terminal device. This at least one indication indicates, for the sake of a neighboring cell (or for the sake of at least one neighboring cell), at least one of the following: • Whether the reduced-capacity terminal device is supported for at least one FSAI or at least one MBS meeting. • Supported by at least one type of terminal device with reduced capability for at least one FSAI or at least one MBS conversation, or • At least one size of a public frequency resource CFR available for at least one FSAI or at least one MBS meeting.

[0144] In some embodiments, the information transmitted (or broadcast) in blocks 1102 and 1103 may be contained in a single message. This single message may be, for example, an SIB21 message.

[0145] Figure 12 illustrates the communication between the RedCap terminal device (hereinafter referred to as the terminal device for simplicity), the first access node, the second access node, the third access node, and the core network. The first access node, the second access node, and the third access node (e.g., gNB) can use separate (carrier) frequencies f1, f2, and f3, and separate FSAIs, namely FSAI2, FSAI2, and FSAI1, service cells 1, 2, and 3, respectively. Here, FSAI2 can be a defined FSAI for the RedCap terminal device, while FSAI1 can be a non-defined FSAI for the RedCap terminal device. The terminal device can operate in cell 1. Functions associated with the core network can be performed by the application functions (AF) of the core network that communicate with the network open function (NEF) and the multicast / broadcast session management function (MB-SMF) of the core network. Although Figure 12 illustrates a communication scenario where the first access node providing the (initial) service cell for the terminal device has two adjacent access nodes, the features and functions described below in conjunction with Figure 12 can also be applied to cases where the first access node has a single adjacent access node or more than two adjacent access nodes.

[0146] Referring to Figure 12, in block 1201, it is assumed that the terminal device initially operates in any RRC state. During this operation, in message 1202, a core network entity (or node or function) of the core network transmits a service announcement for a specific MBS (hereinafter referred to as MBS1) to the terminal device via a first access node, and in block 1203, the terminal device receives the service announcement. The core network node that initiates the transmission may be AF (but may also transmit the service announcement via one or more other core network nodes). In response to or based on the receipt of the service announcement, the first access node may forward the service announcement only to the terminal device (or more generally, to one or more terminal devices). In block 1203, when the terminal device operates in an RRC connected state, the service announcement may be received by the terminal device via unicast, or when the terminal device operates in any RRC state, the service announcement may be received as a broadcast transmission.

[0147] In this exemplary scenario, the service announcement includes two FSAIs: FSAI1 and FSAI2. Compared to Figure 5, the service announcement does not include any instructions for FSAI2 to be used by RedCap terminal devices. In other words, the service announcement can be a "common" service announcement without additional functionality. The service announcement can be associated with a specific TMGI (used to identify MBS meetings).

[0148] In message 1204, a core network entity (or node or function) transmits a broadcast MBS conversation establishment request for the conversation of MBS1 (hereinafter referred to as MBS conversation 1) to the first access node. The broadcast MBS conversation establishment request may be transmitted to the access node, for example, by an AF via zero or more other core network nodes. The broadcast MBS conversation establishment request includes one or more FSAIs. In this particular instance, the broadcast MBS conversation establishment request includes at least FSAI1 and FSAI2. In this embodiment (compared to, for example, the embodiment in FIG5), the RedCap terminal device support capability of one or more FSAIs (e.g., FSAI1 and FSAI2) is unknown at this time. In block 1205, the first access node receives the broadcast MBS conversation establishment request for MBS conversation 1.

[0149] In block 1206, the first access node triggers or initiates a transmission of the MBS conversation (i.e., MBS conversation 1) within the RedCap CFR. This transmission can be triggered or initiated based on the OAM configuration.

[0150] After triggering the transmission of the MBS conversation in block 1206, the first access node transmits one or more messages 1207, 1211 to one or more adjacent access nodes (in this example, two messages 1207, 1211 are transmitted to two adjacent access nodes respectively). Each of the one or more messages 1207, 1211 includes at least one FSAI (i.e., FSAI2 in the illustrated example) and at least one indication indicating that the at least one FSAI is defined as being used for a capability-reduced terminal device. In other words, the FSAI transmitted to adjacent access nodes is supplemented by a RedCap indication (i.e., indicating that the associated FSAI is being used for a RedCap terminal device). In the illustrated example, the one or more adjacent access nodes include a second access node and a third access node. The content of the one or more messages 1207, 1211 can be derived or generated based on the configuration of the first access node and the broadcast MBS conversation establishment request 1204.

[0151] One or more messages 1207 and 1211 may be or may specifically include one or more Xn establishment and / or modification messages. In other words, when using another access node (Xn establishment) or establishing a new Xn connection for an existing Xn connection (Xn modification), the first access node transmits FSAI2 in the Xn establishment or modification message 1207 along with an implicit or explicit indication that it is currently in use (i.e., the first access node will broadcast the start of transmission of the establishment and transmission trigger FSAI information to adjacent access nodes). It is worth noting that if the first access node does not start transmission in the RCap CFR, it will not transmit FSAI2 to any adjacent access node. Therefore, any adjacent access node can determine that the RCap CFR is in use based on the received FSAI2.

[0152] In this embodiment, one or more messages 1207, 1211 may include any information described in conjunction with block 1001 of FIG10 and / or block 1101 of FIG11. In this example, when the first access node is currently using a RedCap CFR with FSAI2 and MBS session 1, each of one or more messages 1207, 1211 may include at least one indication indicating at least one of the following: • RedCap terminal devices are supported at the first access node for use in FSAI2 or MBS Meeting 1. • At least one type of RedCap terminal device supported for FSAI2 or MBS Conversation 1 is provided at the first access node (or in an adjacent cell provided by the first access node). • The size of at least one CFR used for FSAI2 or MBS meeting 1 at the first access node. • Currently, the first access node is used for at least one type of CFR for FSAI2 or MBS meeting 1.

[0153] In some embodiments, the type of a CFR in use may have other granularities, such as indicating (implicitly or explicitly) compliance with UE type restrictions or predefined bandwidth restrictions (e.g., a 100 MHz bandwidth restriction). It can be assumed that each UE type is associated with one or more bandwidths or bands supported by the UE. In other words, one or more messages 1207, 1211 may contain bandwidth restriction conditions as discussed in conjunction with the above embodiments.

[0154] In block 1208, the second access node receives a message containing FSAI2 and at least one indication (e.g., an Xn create or modify message) from the first access node. Similarly, in block 1212, the third access node receives a message containing FSAI2 and at least one indication (e.g., an Xn create or modify message) from the first access node. In individual messages 1209 and 1213, the second and third access nodes transmit response messages (e.g., for an Xn create or modify message) back to the first access node. In blocks 1210 and 1214, the first access node receives response messages 1209 and 1213.

[0155] In the example of Figure 12, it is assumed that the second access node is currently using RedCap CFR, while the third access node is currently using a non-RedCap CFR. Therefore, response message 1209 (e.g., a message to create or modify Xn) may contain at least one indication indicating at least one of the following, similar to messages 1207 and 1211: • RedCap terminal devices are supported at the second access node for use in FSAI2 or MBS Meeting 1. • At the second access node (or in an adjacent cell provided by the first access node), at least one type of RedCap terminal device supported for FSAI2 or MBS Conversation 1 is provided. • At least one size of the CFR used for FSAI2 or MBS meeting 1 at the second access node. • Currently, the second access node is used for at least one type of CFR for FSAI2 or MBS meeting 1.

[0156] In this example, when the third access node is currently using a non-RedCap CFR with FSAI1 and MBS session 2, response message 1213 (e.g., Xn establish or modify message) may contain at least one indication indicating at least one of the following: • RedCap terminal devices are not supported for FSAI1 or MBS Session 2 at the first access node (i.e., only non-RedCap terminal devices are supported for FSAI1 or MBS Session 2 at the first access node). • No type of RedCap terminal device is supported at the third access node for use in FSAI1 or MBS Meeting 2. • At least one size of the CFR used for FSAI1 or MBS meeting 2 at the third access node. • Currently, the third access node is used for at least one type of CFR for FSAI1 or MBS meeting 2.

[0157] In some embodiments, the information listed in the preceding paragraphs may be omitted from message 1213. Message 1213 may be a known Xn creation or modification message. In these embodiments, the third access node may be an access node as defined in 3GPP Release 17 (without additional functionality).

[0158] In some embodiments, one or more messages 1209, 1213 may also include bandwidth limitations as discussed in conjunction with the above embodiments.

[0159] Based on the information received in messages 1209 and / or 1213, in message 1215, the first access node transmits a SIB21 message for cell reselection to at least one terminal device via at least one access node. Here, the SIB21 message includes adjacent cell frequency information related to cells provided by the second and third access nodes, and at least one indication (implicitly or explicitly) of possible RedCap terminal device support associated with the FSAI or MBS conversation of the second and third access nodes. The at least one terminal device includes at least the RedCap terminal device illustrated in FIG12. The transmission of message 1215 may correspond to a broadcast. The transmission (or broadcast) may be regular or periodic. Generally, the transmission of SIB21 message 1215 may correspond to the combination of blocks 1002 and 1003 of FIG10 as discussed above. The adjacent cell frequency information and at least one indication may be defined as described in conjunction with FIG10.

[0160] In block 1216, the (RedCap) terminal device receives the SIB21 message. After receiving the SIB21 message, in block 1217, the terminal device operates in an RRC idle or inactive state while receiving a broadcast MBS conversation (MBS conversation 1) from cell 1 of the first access node. Similar to what has been described in conjunction with previous embodiments, in block 1218, the terminal device performs cell measurements via the first access node, the second access node, and the third access node. Based on these cell measurements and the SIB21 message (and optionally also based on the service announcement), in block 1219, the terminal device performs a cell reselection. In the example of Figure 12, similar to the example of Figure 5, since this frequency is specifically defined for the RedCap terminal device, the terminal device can consider f2 as the highest priority for cell reselection. Alternatively, the terminal device may consider f2 as the highest priority for cell reselection only if FSAI2 complies with the terminal device's limitations, that is, if the terminal device meets at least one bandwidth limitation defined in messages 1209 and / or 1213.

[0161] The cell reselection examples described above in conjunction with Figures 6A and 6B, with necessary modifications to the details, can also be applied here (i.e., in conjunction with block 1219 of Figure 12). In other words, either of the procedures in Figures 6A and 6B can be performed after completing elements 1201 to 1218 of Figure 12.

[0162] In some simplified embodiments, the access node is configured via OAM to associate a specific FSAI with a RedCap terminal device (i.e., it supports RedCap terminal devices) and optionally to have appropriate bandwidth. Based on this configuration, when a signal is received to initiate an MBS conversation including any of the FSAIs, the access node transmits services (i.e., MBS) in the RedCap CFR, and may add non-RedCap CFR transmissions if the bandwidth is suitable for the RedCap UE.

[0163] The embodiments discussed above provide at least some of the following technical advantages. These embodiments allow RedCap and non-RedCap terminal devices to perform different cell reselection priorities, which in turn enable the terminal devices to properly (i.e., correctly or appropriately) receive broadcasts when RRC is inactive or idle. The embodiments enable access nodes to make reasonable decisions about which CFR(s) ...

[0164] The blocks, related functions, and information exchanges described above with the aid of Figures 2 to 5, 6A, 6B, and 7 to 12 are not in absolute chronological order, and some of them may be executed simultaneously or in a different order than given. Other functions may also be executed during or within these blocks, and other information and / or other applied rules may be sent. Some or part of a block's information, or one or more messages, may be omitted or replaced with the corresponding block or part or more messages of a block.

[0165] Figure 13 illustrates an apparatus 1301 according to some embodiments. Specifically, Figure 13 may illustrate an apparatus 1301 as a terminal device, access node, or core network node (e.g., AF, NEF, or MB-SMF). Alternatively, Figure 13 may illustrate an apparatus 1301 as part of a terminal device, access node, or core network node (e.g., AF, NEF, or MB-SMF).

[0166] Device 1301 may include: one or more communication control circuitry systems 1320, such as at least one processor; and at least one memory 1340 including one or more algorithms 1331 (instructions), such as computer code (software), wherein at least one memory 1340 and the computer code (software) are configured, together with at least one processor, to enable device 1301 to perform any of the exemplary functions of the devices described above (e.g., terminal devices, access nodes, AF, NEF, or MB-SMF). The at least one memory 1340 may also include at least one database 1332.

[0167] When one or more communication control circuitry systems 1320 include more than one processor, device 1301 can be a distributed device in which task processing occurs in more than one physical unit. Each of the at least one processor may include one or more processor cores. Processing cores may include, for example, a Cortex-A8 processing core manufactured by ARM Holdings or a Zen processing core designed by Advanced Micro Devices Corporation. One or more communication control circuitry systems 1320 may include at least one Qualcomm Snapdragon and / or Intel Atom processor. One or more communication control circuitry systems 1320 may include at least one application-specific integrated circuit (ASIC). One or more control circuitry systems 1320 may include at least one field-programmable gate array (FPGA).

[0168] Referring to Figure 13, one or more communication control circuit systems 1320 of device 1301 are configured to perform the functions described above by means of any of Figures 2 to 5, 6A, 6B and 7 to 12 using one or more individual circuit systems. Specifically, in the cases of Figures 5, 6A, 6B, 7, 8 and 12, one or more communication control circuit systems 1320 of device 1301 are configured to perform the functions of at least one of the illustrated devices. It is also possible to implement the functions according to different embodiments using specific integrated circuits, such as application-specific integrated circuits (ASICs) or other components and devices.

[0169] Referring to Figure 13, device 1301 may further include different interfaces 1310, such as one or more communication interfaces including hardware and / or software for implementing communication connectivity according to one or more communication protocols. Specifically, when device 1301 is a terminal device or part thereof, one or more communication interfaces 1310 may include, for example, a communication interface providing a connection between device 1301 and one or more access nodes for providing a connection to a core network (including, for example, MB-SMF, NEF, and AF). If device 1301 is an access node or part thereof, one or more communication interfaces 1310 may include, for example, a communication interface between device 1301 and one or more terminal devices and between device 1301 and one or more core network nodes (including, for example, MB-SMF, NEF, and AF). One or more communication interfaces 1310 may include standard, well-known components, such as amplifiers, filters, frequency converters, modulators (demodulators), and encoder / decoder circuitry controlled by corresponding control units, and one or more antennas. Device 1301 may also include one or more user interfaces.

[0170] Referring to Figure 13, memory 1340 can be implemented using any suitable data storage technology, such as semiconductor-based memory devices, flash memory, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory.

[0171] As used in this application, the term "circuit system" may refer to one or more or all of the following: (a) a purely hardware circuit implementation, such as an implementation only in analog and / or digital circuit systems; and (b) a combination of hardware circuitry and software (and / or firmware), such as (if applicable): (i) a combination of analog and / or digital hardware circuitry and software / firmware; and (ii) any part of a hardware processor and software, including digital signal processors, software, and memory that work together to enable devices such as terminal devices or access nodes to perform various functions; and (c) hardware circuitry and processors, such as microprocessors or parts thereof, that require software (e.g., firmware) to operate, but may be absent when operation is not required. This definition of "circuit system" is used for all uses of the term in this application (including any claim). As another example, as used in this application, the term "circuit system" also covers only hardware circuitry or processors (or processors), or a portion of hardware circuitry or processors and their accompanying software and / or firmware implementation.

[0172] In embodiments, at least some of the programs described in conjunction with Figures 2-5, 6A, 6B, and 7-12 may be executed by a device comprising corresponding components for executing at least some of the described programs. Some exemplary components for executing the programs may include at least one of the following: a detector, a processor (including dual-core and multi-core processors), a digital signal processor, a controller, a receiver, a transmitter, an encoder, a decoder, memory, RAM, ROM, software, firmware, a display, a user interface, a display circuitry, a user interface circuitry, user interface software, display software, circuitry, filters (low-pass, high-pass, band-pass, and / or band-stop), sensors, circuitry, inverters, capacitors, inductors, resistors, operational amplifiers, diodes, and transistors. In embodiments, at least one processor, memory, and computer code form a processing component, or include portions of computer code for performing one or more operations or operations thereof according to any of the embodiments of Figures 2-5, 6A, 6B, and 7-12. In some embodiments, discrete components may be used to implement at least some of the procedures.

[0173] According to an embodiment, a device (e.g., a terminal device or a UE or part thereof) is provided, which includes components for performing the following operations: Receive service announcements for the Multicast Broadcast Service (MBS), which include: - At least one Frequency Selection Area Identifier (FSAI), and at least one indication indicating that the at least one FSAI is defined for use in a capability-reduced terminal device, or - At least one frequency, and at least one indication indicating that the at least one frequency is defined for use in a capability-reducing terminal device; The components are further configured to perform a cell reselection procedure based on cell measurement and service announcements.

[0174] According to an embodiment, a device (e.g., AF or a portion thereof) is provided, which includes components for performing the following operations: Receive service announcements for the Multicast Broadcast Service (MBS), which include: - At least one Frequency Selection Area Identifier (FSAI), and at least one indication indicating that the at least one FSAI is defined for use in a capability-reduced terminal device, or - At least one frequency, and at least one indication indicating that the at least one frequency is defined for use in a capability-reducing terminal device; The components are further configured to perform a cell reselection procedure based on cell measurement and service announcements.

[0175] According to an embodiment, a device (e.g., an access node or a portion thereof) is provided, which includes components for performing the following operations: The core network function receives a broadcast multicast service MBS session establishment request, wherein the broadcast MBS session establishment request includes at least one Frequency Selection Area Identifier (FSAI) and at least one indication indicating that the at least one FSAI is defined for a capability-reduced terminal device; or The system receives a broadcast MBS session establishment request from the core network and configuration information from the operations, administration, and management OAM entities. The broadcast MBS session establishment request includes at least one FSAI, and the configuration information includes at least one indication that the at least one FSAI is defined for use with a capability-reducing terminal device. The components are further configured to perform the following operations: Based on at least one FSAI and at least one instruction, MBS talks are triggered for transmission within the Capability Reduced Common Frequency Resource (CFR).

[0176] According to an embodiment, a device (e.g., MB-SMF or a portion thereof) is provided, which includes components for performing the following operations: Receive MBS Session Multicast Broadcast Service MBS Session Creation Request; In response to or based on the reception, generate at least one Frequency Selection Area Identifier (FSAI) defined for a capability-reduced terminal device for the MBS conference, and at least one indication indicating that the at least one FSAI is defined for a capability-reduced terminal device; and The broadcast MBS session establishment request is transmitted to at least one access node, wherein the broadcast MBS session establishment request includes at least one FSAI and at least one instruction.

[0177] According to an embodiment, a device (e.g., a portion of a terminal device) is provided, which includes components for performing the following operations: Receive neighbor cell frequency information, which includes a mapping between at least one neighbor cell frequency and at least one Frequency Selection Area Identifier (FSAI) for at least one Multicast Broadcast Service (MBS) session, wherein the neighbor cell frequency is the operating frequency of the neighbor cell of the device's service cell; Receive at least one instruction for at least one adjacent cell indicating at least one of the following: • Whether the reduced-capacity terminal device is supported for at least one FSAI or at least one MBS meeting. • Supported by at least one type of terminal device with reduced capability for at least one FSAI or at least one MBS conversation, or • At least one size of a public frequency resource CFR available for at least one FSAI or at least one MBS meeting; and A cell reselection procedure is performed based on cell measurements, adjacent cell frequency information, and at least one instruction.

[0178] According to an embodiment, a device (e.g., an access node or a portion thereof) is provided, which includes components for performing the following operations: Receive at least one indication from at least one adjacent access node indicating at least one of the following: • Whether the capability-reduced terminal device is supported at at least one adjacent access node in at least one adjacent access node for at least one Frequency Selection Area Identifier (FSAI) or at least one Multicast Broadcast Service (MBS) meeting. • At adjacent access nodes, the capability of supporting at least one type of terminal device for at least one FSAI or at least one MBS conversation is reduced. • At least one size of the common frequency resource CFR used for at least one FSAI or at least one MBS negotiation at adjacent access nodes. • Currently, at least one type of CFR used by adjacent access nodes for at least one FSAI or at least one MBS session; Neighbor cell frequency information, including a mapping between at least one neighbor cell frequency and at least one FSAI used for at least one MBS session, is transmitted to the terminal device, wherein the neighbor cell frequency is the operating frequency of the neighbor cells of the service cell provided by the device; and At least one indication is transmitted to the terminal device, the at least one indication indicating at least one of the following for at least one neighboring cell provided by at least one neighboring access node: • Whether the reduced-capacity terminal device is supported for at least one FSAI or at least one MBS meeting. • Supported by at least one type of terminal device with reduced capability for at least one FSAI or at least one MBS conversation, or • Can be used for at least one size of CFR in at least one FSAI or at least one MBS meeting.

[0179] According to an embodiment, a device (e.g., an access node or a portion thereof) is provided, which includes components for performing the following operations: Each of one or more adjacent access nodes receives at least one Temporary Action Group Identifier (TMGI) associated with at least one Multicast Broadcast Service (MBS) session conducted at an adjacent access node, and for each of the at least one TMGI, receives at least one instruction indicating at least one of the following: • Whether the capability-reduced terminal device is supported for TMGI at adjacent access nodes. • At least one type of terminal device with reduced capability for TMGI supported at adjacent access nodes, or • At least one size of the CFR used for TMGI at adjacent access nodes; Neighbor cell frequency information, comprising a mapping between at least one neighbor cell frequency and at least one FSAI used for at least one MBS session, is transmitted to a terminal device, wherein the neighbor cell frequency is the operating frequency of the neighbor cells of the service cell provided by the device, and the neighbor cell frequency information is based on at least one TMGI, at least one indicator, and the mapping between at least one TMGI and at least one FSAI used for at least one MBS session; and At least one indication for at least one neighboring cell provided by one or more adjacent access nodes is transmitted to the terminal device, wherein the at least one indication for the neighboring cell (or for at least one neighboring cell) indicates at least one of the following: • Whether the reduced-capacity terminal device is supported for at least one FSAI or at least one MBS meeting. • Supported by at least one type of terminal device with reduced capability for at least one FSAI or at least one MBS conversation, or • At least one size of a public frequency resource CFR available for at least one FSAI or at least one MBS meeting.

[0180] The embodiments described may also be implemented wholly or at least partially in the form of a computer program defined by a computer program or parts thereof. Embodiments of the methods described in conjunction with Figures 2-5, 6A, 6B, and 7-12 can be executed by executing at least a portion of a computer program containing corresponding instructions. The computer program may be provided as a computer-readable medium containing program instructions stored thereon, or as a non-transitory computer-readable medium containing program instructions stored thereon. The computer program may be in the form of source code, object code, or some intermediate form, and may be stored on some kind of carrier, which may be any entity or device capable of carrying the program. For example, the computer program may be stored on a computer program distribution medium readable by a computer or processor. For example, the computer program medium may be, for example, but not limited to, recording media, computer memory, read-only memory, electrical carrier signals, telecommunication signals, and software distribution packages. The computer program medium may be a non-transitory medium. The coding of the software used to perform the embodiments shown and described is entirely within the scope of those skilled in the art.

[0181] According to an embodiment, a non-transitory computer-readable medium is provided having instructions stored thereon, which, when executed by a computing device, cause the computing device to perform the following operations: Receive service announcements for the Multicast Broadcast Service (MBS), which include: - At least one Frequency Selection Area Identifier (FSAI), and at least one indication indicating that the at least one FSAI is defined for use in a capability-reduced terminal device, or - At least one frequency, and at least one indication indicating that the at least one frequency is defined for use in a capability-reducing terminal device; When these instructions are executed by a computing device, the computing device further performs a cell reselection procedure based on cell measurement and service announcements.

[0182] According to an embodiment, a non-transitory computer-readable medium is provided having instructions stored thereon, which, when executed by a computing device, cause the computing device to perform the following operations: The service announcement of the Multicast Broadcast Service (MBS) is transmitted to at least one terminal device via at least one access node, wherein the service announcement contains... - At least one Frequency Selection Area Identifier (FSAI), and at least one indication indicating that the at least one FSAI is defined for use in a capability-reduced terminal device, or - At least one frequency defined for a capability-reducing terminal device, and at least one indication indicating that the at least one frequency is defined for a capability-reducing terminal device.

[0183] According to an embodiment, a non-transitory computer-readable medium is provided having instructions stored thereon, which, when executed by a computing device, cause the computing device to perform the following operations: The core network function receives a broadcast multicast service MBS session establishment request, wherein the broadcast MBS session establishment request includes at least one Frequency Selection Area Identifier (FSAI) and at least one indication indicating that the at least one FSAI is defined for a capability-reduced terminal device; or The system receives a broadcast MBS session establishment request from the core network and configuration information from the operations, administration, and management OAM entities. The broadcast MBS session establishment request includes at least one FSAI, and the configuration information includes at least one indication that the at least one FSAI is defined for a capability-reducing terminal device. Furthermore, when executed by the computing device, the instruction further causes the computing device to perform the following operations: Based on at least one FSAI and at least one instruction, MBS talks are triggered for transmission within the Capability Reduced Common Frequency Resource (CFR).

[0184] According to an embodiment, a non-transitory computer-readable medium is provided having instructions stored thereon, which, when executed by a computing device, cause the computing device to perform the following operations: Receive MBS Session Multicast Broadcast Service MBS Session Creation Request; In response to or based on the reception, generate at least one Frequency Selection Area Identifier (FSAI) defined for a capability-reduced terminal device for the MBS conference, and at least one indication indicating that the at least one FSAI is defined for a capability-reduced terminal device; and The broadcast MBS session establishment request is transmitted to at least one access node, wherein the broadcast MBS session establishment request includes at least one FSAI and at least one instruction.

[0185] As used in this article, the term "non-transitory" refers to a limitation on the medium itself (i.e., tangible, not signaling), rather than a limitation on the persistence of data storage (e.g., RAM versus ROM).

[0186] According to an embodiment, a method is provided, comprising: Receive service announcements for the Multicast Broadcast Service (MBS), which include: - At least one Frequency Selection Area Identifier (FSAI), and at least one indication indicating that the at least one FSAI is defined for use in a capability-reduced terminal device, or - At least one frequency, and at least one indication indicating that the at least one frequency is defined for use in a capability-reducing terminal device; The method further includes performing a cell reselection procedure based on cell measurement and service announcements.

[0187] According to an embodiment, a method is provided, comprising: The service announcement of the Multicast Broadcast Service (MBS) is transmitted to at least one terminal device via at least one access node, wherein the service announcement contains... - At least one Frequency Selection Area Identifier (FSAI), and at least one indication indicating that the at least one FSAI is defined for use in a capability-reduced terminal device, or - At least one frequency defined for a capability-reducing terminal device, and at least one indication indicating that the at least one frequency is defined for a capability-reducing terminal device.

[0188] According to an embodiment, a method is provided, comprising: The core network function receives a broadcast multicast service MBS session establishment request, wherein the broadcast MBS session establishment request includes at least one Frequency Selection Area Identifier (FSAI) and at least one indication indicating that the at least one FSAI is defined for a capability-reduced terminal device; or The method involves receiving a broadcast MBS conversation establishment request from the core network and receiving configuration information from the operations, administration, and management OAM entities, wherein the broadcast MBS conversation establishment request includes at least one FSAI, and the configuration information includes at least one indication indicating that at least one FSAI is defined for a capability-reduced terminal device; and wherein the method further includes: Based on at least one FSAI and at least one instruction, MBS talks are triggered for transmission within the Capability Reduced Common Frequency Resource (CFR).

[0189] According to an embodiment, a method is provided, comprising: Receive MBS Session Multicast Broadcast Service MBS Session Creation Request; In response to or based on the reception, generate at least one Frequency Selection Area Identifier (FSAI) defined for a capability-reduced terminal device for the MBS conference, and at least one indication indicating that the at least one FSAI is defined for a capability-reduced terminal device; and The broadcast MBS session establishment request is transmitted to at least one access node, wherein the broadcast MBS session establishment request includes at least one FSAI and at least one instruction.

[0190] Example 1: A device comprising: at least one processor; and at least one memory storing instructions, which, when executed by the at least one processor, cause the device to perform at least the following operations: Receive neighbor cell frequency information, which includes a mapping between at least one neighbor cell frequency and at least one Frequency Selection Area Identifier (FSAI) for at least one Multicast Broadcast Service (MBS) session, wherein the neighbor cell frequency is the operating frequency of the neighbor cell of the device's service cell; Receive at least one instruction for at least one adjacent cell indicating at least one of the following: • Whether the reduced-capacity terminal device is supported for at least one FSAI or at least one MBS meeting. • Supported by at least one type of terminal device with reduced capability for at least one FSAI or at least one MBS conversation, or • At least one size of a public frequency resource CFR available for at least one FSAI or at least one MBS meeting; and A cell reselection procedure is performed based on cell measurements, adjacent cell frequency information, and at least one instruction.

[0191] Example 2: The device as in Example 1, wherein adjacent cell frequency information and at least one indication are received in the System Information Block 21 (SIB21) message.

[0192] Example 3: The device as in Example 1 or 2, wherein the device is a capability-reduced terminal device.

[0193] Example 4: A device as in Example 3, wherein at least one indication indicates that a capability-reduced terminal device is supported for at least one FSAI or at least one MBS session, without indicating any of the following: at least one size of a CFR that can be used for at least one FSAI or at least one MBS session, and at least one type of capability-reduced terminal device supported for at least one FSAI or at least one MBS session; and wherein the execution of the cell reselection procedure includes: In the cell reselection procedure, at least one adjacent cell frequency associated with at least one indication indicating that a capability-reduced terminal device is supported for at least one FSAI or at least one MBS conversation is prioritized.

[0194] Example 5: A device as in Example 3, wherein at least one indication indicates at least one size of a CFR available for at least one FSAI or at least one MBS session and / or at least one type of terminal device with reduced capability supported for at least one FSAI or at least one MBS session; and wherein the execution of the cell reselection procedure includes: In the cell reselection procedure, priority is associated with the size of one of the CFRs supported by the capability reduction terminal device and / or with at least one adjacent cell frequency associated with one of the capability reduction terminal device types corresponding to the capability reduction terminal device.

[0195] Example 6: A device similar to Example 1 or 2, wherein the device is a non-capacity-degrading terminal device; and wherein the execution of the cell reselection procedure includes: In the cell reselection process, prioritization based on at least one indication and adjacent cell frequency information fails to support the capability to reduce at least one adjacent cell frequency of the terminal device.

[0196] Example 7: A device as described in any of Examples 1 to 6, wherein at least one memory and the instructions are configured, together with at least one processor, to cause the device to perform the following operations before receiving adjacent cell frequency information: Receive service announcements for MBS talks, wherein the service announcements indicate at least one FSAI associated with the MBS talks or at least one frequency associated with the MBS talks, wherein the execution of cell reselection procedures is further based on the service announcements.

[0197] Example 8: A device as described in any of Examples 1 to 7, wherein at least one memory and such instructions are configured, together with at least one processor, to cause the device to further perform the following operations: It operates in the Radio Resource Control (RRC) idle or inactive state during the execution of the cell reselection procedure.

[0198] Example 9: A device comprising: At least one processor; and At least one memory contains storage instructions that, when executed by at least one processor, cause the device to perform at least the following operations: Receive at least one indication from at least one adjacent access node indicating at least one of the following: • Whether the capability-reduced terminal device is supported at at least one adjacent access node in at least one adjacent access node for at least one Frequency Selection Area Identifier (FSAI) or at least one Multicast Broadcast Service (MBS) meeting. • At adjacent access nodes, the capability of supporting at least one type of terminal device for at least one FSAI or at least one MBS conversation is reduced. • At least one size of the common frequency resource CFR used for at least one FSAI or at least one MBS negotiation at adjacent access nodes. • Currently, at least one type of CFR used by adjacent access nodes for at least one FSAI or at least one MBS session; Neighbor cell frequency information, including a mapping between at least one neighbor cell frequency and at least one FSAI used for at least one MBS session, is transmitted to the terminal device, wherein the neighbor cell frequency is the operating frequency of the neighbor cells of the service cell provided by the device; and At least one indication is transmitted to the terminal device, the at least one indication indicating at least one of the following for at least one neighboring cell provided by at least one neighboring access node: • Whether the reduced-capacity terminal device is supported for at least one FSAI or at least one MBS meeting. • Supported by at least one type of terminal device with reduced capability for at least one FSAI or at least one MBS conversation, or • Can be used for at least one size of CFR in at least one FSAI or at least one MBS meeting.

[0199] Example 10: A device as in Example 9, wherein at least one memory and such instructions are configured to, together with at least one processor, cause the device to perform the following operations: The core network function receives a broadcast multicast service MBS meeting establishment request for an MBS meeting, wherein the broadcast MBS meeting establishment request includes at least one FSAI associated with the MBS meeting.

[0200] Example 11: A device such as in Example 9 or 10, wherein at least one memory and such instructions are configured, together with at least one processor, to cause the device to further perform the following operations: The self-operation, administration, and management OAM entity receives configuration information, wherein the configuration information includes at least one indication that at least one FSAI associated with the MBS meeting is defined for a capability-reduced terminal device; and MBS talks are triggered based on configuration information and transmitted within the CFR defined for use with the capability-reduced terminal device.

[0201] Example 12: A device such as in Example 10 or 11, wherein at least one memory and such instructions are configured to, together with at least one processor, cause the device to perform the following operations: At least one indication indicating at least one of the following will be transmitted to at least one adjacent access node: • Whether the capability-reduced terminal device is supported at the equipment level for at least one FSAI or at least one MBS meeting. • The terminal device is supported at least one type of reduced capability for at least one FSAI or at least one MBS conversation, or • At least one size of CFR used for at least one FSAI or at least one MBS meeting at the equipment location, or • Currently, the equipment is used for at least one type of CFR for at least one FSAI or at least one MBS meeting.

[0202] Example 13: A device comprising: At least one processor; and At least one memory contains storage instructions that, when executed by at least one processor, cause the device to perform at least the following operations: Each of one or more adjacent access nodes receives at least one Temporary Action Group Identifier (TMGI) associated with at least one Multicast Broadcast Service (MBS) session conducted at an adjacent access node, and for each of the at least one TMGI, receives at least one instruction indicating at least one of the following: • Whether the capability-reduced terminal device is supported for TMGI at adjacent access nodes. • At least one type of terminal device with reduced capability for TMGI supported at adjacent access nodes, or • At least one size of the CFR used for TMGI at adjacent access nodes; Neighbor cell frequency information, comprising a mapping between at least one neighbor cell frequency and at least one FSAI used for at least one MBS session, is transmitted to a terminal device, wherein the neighbor cell frequency is the operating frequency of the neighbor cells of the service cell provided by the device, and the neighbor cell frequency information is based on at least one TMGI, at least one indicator, and the mapping between at least one TMGI and at least one FSAI used for at least one MBS session; and At least one indication for at least one neighboring cell provided by one or more adjacent access nodes is transmitted to the terminal device, wherein the at least one indication for the at least one neighboring cell indicates at least one of the following: • Whether the reduced-capacity terminal device is supported for at least one FSAI or at least one MBS meeting. • Supported by at least one type of terminal device with reduced capability for at least one FSAI or at least one MBS conversation, or • At least one size of a public frequency resource CFR available for at least one FSAI or at least one MBS meeting.

[0203] Example 14: A device as in Example 13, wherein at least one memory and such instructions are configured to, together with at least one processor, cause the device to perform the following operations: At least one TMGI associated with at least one MBS session conducted at the device is transmitted to each of one or more adjacent access nodes, and for each of the at least one TMGI associated with at least one MBS session conducted at the device, at least one indication indicates at least one of the following: • Capability reduction: Is the terminal device supported for TMGI at the device level? • At least one type of terminal device that is supported for TMGI capability reduction at the device level, or • At least one size of the CFR used for TMGI at the device.

[0204] Example 15: A device as in Example 13, wherein at least one memory and the instructions are configured, together with at least one processor, to cause the device to perform the following operations before transmitting adjacent cell frequency information: The core network function receives a broadcast MBS session establishment request for an MBS session, wherein the broadcast MBS session establishment request includes at least one FSAI associated with the MBS session; and Based on a broadcast MBS session establishment request and at least one TMGI and at least one indication received from one or more adjacent access nodes, determine the mapping between at least one TMGI and at least one FSAI used for at least one MBS session.

[0205] Example 16: A device as in Example 15, wherein at least one memory and such instructions are configured to, together with at least one processor, cause the device to perform the following operations: The self-operation, administration, and management OAM entity receives configuration information, which includes at least one indication of at least one FSAI defined for a capability-reduced terminal device, indicating that it is associated with at least one MBS conversation supported by the device; and MBS talks are triggered based on configuration information and transmitted within the CFR defined for use with the capability-reduced terminal device.

[0206] Example 17: A device as described in any of Examples 9 to 16, wherein adjacent cell frequency information and at least one indication are transmitted to the terminal device in a System Information Block 21 (SIB21) message.

[0207] Example 18: A method that includes: Receive neighbor cell frequency information, which includes a mapping between at least one neighbor cell frequency and at least one Frequency Selection Area Identifier (FSAI) for at least one Multicast Broadcast Service (MBS) session, wherein the neighbor cell frequency is the operating frequency of the neighbor cell of the device's service cell; Receive at least one instruction for at least one adjacent cell indicating at least one of the following: • Whether the reduced-capacity terminal device is supported for at least one FSAI or at least one MBS meeting. • Supported for at least one FSAI or at least one MBS conversation support capability reduction terminal device of at least one type, or • At least one size of a public frequency resource CFR available for at least one FSAI or at least one MBS meeting; and A cell reselection procedure is performed based on cell measurements, adjacent cell frequency information, and at least one instruction.

[0208] Example 19: A method that includes: Receive at least one indication from at least one adjacent access node indicating at least one of the following: • Whether the capability-reduced terminal device is supported at at least one adjacent access node in at least one adjacent access node for at least one Frequency Selection Area Identifier (FSAI) or at least one Multicast Broadcast Service (MBS) meeting. • At adjacent access nodes, the capability of supporting at least one type of terminal device for at least one FSAI or at least one MBS conversation is reduced. • At least one size of the common frequency resource CFR used for at least one FSAI or at least one MBS negotiation at adjacent access nodes. • Currently, at least one type of CFR used by adjacent access nodes for at least one FSAI or at least one MBS session; Neighbor cell frequency information, including a mapping between at least one neighbor cell frequency and at least one FSAI used for at least one MBS session, is transmitted to the terminal device, wherein the neighbor cell frequency is the operating frequency of the neighbor cells of the service cell provided by the device; and At least one indication is transmitted to the terminal device, the at least one indication indicating at least one of the following for at least one neighboring cell provided by at least one neighboring access node: • Whether the reduced-capacity terminal device is supported for at least one FSAI or at least one MBS meeting. • Supported by at least one type of terminal device with reduced capability for at least one FSAI or at least one MBS conversation, or • Can be used for at least one size of CFR in at least one FSAI or at least one MBS meeting.

[0209] Example 20: A method that includes: Each of one or more adjacent access nodes receives at least one Temporary Action Group Identifier (TMGI) associated with at least one Multicast Broadcast Service (MBS) session conducted at an adjacent access node, and for each of the at least one TMGI, receives at least one instruction indicating at least one of the following: • Whether the capability-reduced terminal device is supported for TMGI at adjacent access nodes. • At least one type of terminal device with reduced capability for TMGI supported at adjacent access nodes, or • At least one size of the CFR used for TMGI at adjacent access nodes; Neighbor cell frequency information, comprising a mapping between at least one neighbor cell frequency and at least one FSAI used for at least one MBS session, is transmitted to a terminal device, wherein the neighbor cell frequency is the operating frequency of the neighbor cells of the service cell provided by the device, and the neighbor cell frequency information is based on at least one TMGI, at least one indicator, and the mapping between at least one TMGI and at least one FSAI used for at least one MBS session; and At least one indication for at least one neighboring cell provided by one or more adjacent access nodes is transmitted to the terminal device, wherein the at least one indication for the at least one neighboring cell indicates at least one of the following: • Whether the reduced-capacity terminal device is supported for at least one FSAI or at least one MBS meeting. • Supported by at least one type of terminal device with reduced capability for at least one FSAI or at least one MBS conversation, or • At least one size of a public frequency resource CFR available for at least one FSAI or at least one MBS meeting.

[0210] Example 21: A non-transitory computer-readable medium having instructions stored thereon, which, when executed by a computing device, cause the computing device to perform the following operations: Receive neighbor cell frequency information, which includes a mapping between at least one neighbor cell frequency and at least one Frequency Selection Area Identifier (FSAI) for at least one Multicast Broadcast Service (MBS) session, wherein the neighbor cell frequency is the operating frequency of the neighbor cell of the device's service cell; Receive at least one instruction for at least one adjacent cell indicating at least one of the following: • Whether the reduced-capacity terminal device is supported for at least one FSAI or at least one MBS meeting. • Supported by at least one type of terminal device with reduced capability for at least one FSAI or at least one MBS conversation, or • At least one size of a public frequency resource CFR available for at least one FSAI or at least one MBS meeting; and A cell reselection procedure is performed based on cell measurements, adjacent cell frequency information, and at least one instruction.

[0211] Example 22: A non-transitory computer-readable medium having instructions stored thereon, which, when executed by a computing device, cause the computing device to perform the following operations: Receive at least one indication from at least one adjacent access node indicating at least one of the following: • Whether the capability-reduced terminal device is supported at at least one adjacent access node in at least one adjacent access node for at least one Frequency Selection Area Identifier (FSAI) or at least one Multicast Broadcast Service (MBS) meeting. • At adjacent access nodes, the capability of supporting at least one type of terminal device for at least one FSAI or at least one MBS conversation is reduced. • At least one size of the common frequency resource CFR used for at least one FSAI or at least one MBS negotiation at adjacent access nodes. • Currently, at least one type of CFR used by adjacent access nodes for at least one FSAI or at least one MBS session; Neighbor cell frequency information, including a mapping between at least one neighbor cell frequency and at least one FSAI used for at least one MBS session, is transmitted to the terminal device, wherein the neighbor cell frequency is the operating frequency of the neighbor cells of the service cell provided by the device; and At least one indication is transmitted to the terminal device, the at least one indication indicating at least one of the following for at least one neighboring cell provided by at least one neighboring access node: • Whether the reduced-capacity terminal device is supported for at least one FSAI or at least one MBS meeting. • Supported by at least one type of terminal device with reduced capability for at least one FSAI or at least one MBS conversation, or • Can be used for at least one size of CFR in at least one FSAI or at least one MBS meeting.

[0212] Example 23: A non-transitory computer-readable medium having instructions stored thereon, which, when executed by a computing device, cause the computing device to perform the following operations: Each of one or more adjacent access nodes receives at least one Temporary Action Group Identifier (TMGI) associated with at least one Multicast Broadcast Service (MBS) session conducted at an adjacent access node, and for each of the at least one TMGI, receives at least one instruction indicating at least one of the following: • Whether the capability-reduced terminal device is supported for TMGI at adjacent access nodes. • At least one type of terminal device with reduced capability for TMGI supported at adjacent access nodes, or • At least one size of the CFR used for TMGI at adjacent access nodes; Neighbor cell frequency information, comprising a mapping between at least one neighbor cell frequency and at least one FSAI used for at least one MBS session, is transmitted to a terminal device, wherein the neighbor cell frequency is the operating frequency of the neighbor cells of the service cell provided by the device, and the neighbor cell frequency information is based on at least one TMGI, at least one indicator, and the mapping between at least one TMGI and at least one FSAI used for at least one MBS session; and At least one indication for at least one neighboring cell provided by one or more adjacent access nodes is transmitted to the terminal device, wherein the at least one indication for the at least one neighboring cell indicates at least one of the following: • Whether the reduced-capacity terminal device is supported for at least one FSAI or at least one MBS meeting. • Supported by at least one type of terminal device with reduced capability for at least one FSAI or at least one MBS conversation, or • At least one size of a public frequency resource CFR available for at least one FSAI or at least one MBS meeting.

[0213] Additional or alternative sets of numbered instances:

[0214] Example 1: A device comprising: at least one processor; and at least one memory storing instructions, which, when executed by the at least one processor, cause the device to perform at least the following operations: receiving neighbor cell frequency information, including a mapping between at least one neighbor cell frequency and at least one Frequency Selection Area Identifier (FSAI) for at least one Multicast Broadcast Service (MBS) session, wherein the neighbor cell frequency is the operating frequency of a neighbor cell of a service cell of the device; and receiving at least one indication for the at least one neighbor cell indicating at least one of the following: • Whether the reduced-capacity terminal device is supported for at least one FSAI or at least one MBS meeting. • Supported by at least one type of terminal device with reduced capability for at least one FSAI or at least one MBS conversation, or • At least one size of a public frequency resource CFR available for at least one FSAI or at least one MBS meeting; and A cell reselection procedure is performed based on cell measurements, adjacent cell frequency information, and at least one instruction.

[0215] Example 2. The device as in Example 1, wherein adjacent cell frequency information and at least one indication are received in the System Information Block 21 (SIB21) message.

[0216] Example 3. The device as in any of the preceding examples, wherein the device is a capability-reduced terminal device.

[0217] Example 4. The device of Example 3, wherein at least one indication indicates that the capability-reduced terminal device is supported for at least one FSAI or at least one MBS conversation, without indicating any of the following: at least one size of the CFR that can be used for at least one FSAI or at least one MBS conversation and at least one type of capability-reduced terminal device supported for at least one FSAI or at least one MBS conversation; and wherein the execution of the cell reselection procedure includes: in the cell reselection procedure, prioritizing at least one adjacent cell frequency associated with at least one indication that indicates the capability-reduced terminal device is supported for at least one FSAI or at least one MBS conversation.

[0218] Example 5. The device of Example 3, wherein at least one indication indicates at least one size of a CFR that can be used for at least one FSAI or at least one MBS session and / or at least one type of capability-reduced terminal device supported for at least one FSAI or at least one MBS session; and wherein the execution of the cell reselection procedure includes: in the cell reselection procedure, prioritizing at least one adjacent cell frequency associated with one size of a CFR supported by the capability-reduced terminal device and / or associated with one type of capability-reduced terminal device corresponding to the capability-reduced terminal device.

[0219] Example 6. The device as in Example 1 or 2, wherein the device is a non-capability-reduced terminal device; and wherein the execution of the cell reselection procedure includes: in the cell reselection procedure, prioritizing at least one adjacent cell frequency of the capability-reduced terminal device based on at least one indication and adjacent cell frequency information fails to support at least one adjacent cell frequency of the capability-reduced terminal device.

[0220] Example 7. A device as described in any of the preceding examples, wherein at least one memory and the instructions are configured together with at least one processor to cause the device to perform the following operations before receiving adjacent cell frequency information: receiving a service announcement of an MBS session, wherein the service announcement indicates at least one FSAI associated with the MBS session or at least one frequency associated with the MBS session, wherein the execution of a cell reselection procedure is further based on the service announcement.

[0221] Example 8. A device as described in any of the preceding examples, wherein at least one memory and such instructions are configured together with at least one processor to cause the device to perform the following operation: operating in a Radio Resource Control (RRC) idle or inactive state during the execution of a cell reselection procedure.

[0222] Example 9. A device comprising: at least one processor; and at least one memory storing instructions, which, when executed by the at least one processor, cause the device to perform at least the following operations: receiving from at least one adjacent access node at least one instruction indicating at least one of the following: • Whether the capability-reduced terminal device is supported at at least one adjacent access node in at least one adjacent access node for at least one Frequency Selection Area Identifier (FSAI) or at least one Multicast Broadcast Service (MBS) meeting. • At adjacent access nodes, the capability of supporting at least one type of terminal device for at least one FSAI or at least one MBS conversation is reduced. • At least one size of the common frequency resource CFR used for at least one FSAI or at least one MBS negotiation at adjacent access nodes, or • Currently, at least one type of CFR used by adjacent access nodes for at least one FSAI or at least one MBS session; Neighbor cell frequency information, including a mapping between at least one neighbor cell frequency and at least one FSAI used for at least one MBS session, is transmitted to the terminal device, wherein the neighbor cell frequency is the operating frequency of the neighbor cells of the service cell provided by the device; and At least one indication is transmitted to the terminal device, the at least one indication indicating at least one of the following for at least one neighboring cell provided by at least one neighboring access node: • Whether the reduced-capacity terminal device is supported for at least one FSAI or at least one MBS meeting. • Supported by at least one type of terminal device with reduced capability for at least one FSAI or at least one MBS conversation, or • Can be used for at least one size of CFR in at least one FSAI or at least one MBS meeting.

[0223] Example 10. A device as in Example 9, wherein at least one memory and the instructions are configured together with at least one processor to cause the device to perform the following operations: receive a broadcast multicast service MBS session establishment request from the core network function, wherein the broadcast MBS session establishment request includes at least one FSAI associated with the MBS session.

[0224] Example 11. A device as in Example 10, wherein at least one memory and such instructions are configured, together with at least one processor, to cause the device to further perform the following operations: receive configuration information from an operational, administrative, and management OAM entity, wherein the configuration information includes at least one indication indicating at least one FSAI associated with an MBS conversation defined for a capability-reduced terminal device; and trigger the transmission of the MBS conversation within a CFR defined for a capability-reduced terminal device based on the configuration information.

[0225] Example 12. A device as described in any of Examples 9 to 11, wherein at least one memory and the instructions are configured, together with at least one processor, to cause the device to perform the following operation: transmit at least one instruction indicating at least one of the following to at least one adjacent access node: • Whether the capability-reduced terminal device is supported at the equipment level for at least one FSAI or at least one MBS meeting. • The terminal device is supported at least one type of reduced capability for at least one FSAI or at least one MBS conversation, or • At least one size of CFR used for at least one FSAI or at least one MBS meeting at the equipment location, or • Currently, the equipment is used for one type of CFR for at least one FSAI or at least one MBS meeting.

[0226] Example 13. An apparatus comprising: at least one processor; and at least one memory storing instructions, which, when executed by the at least one processor, cause the apparatus to perform at least the following operations: receiving from each of one or more adjacent access nodes at at least one temporary action group identifier (TMGI) associated with at least one multicast broadcast service (MBS) session being conducted at the adjacent access nodes, and receiving, for each of the at least one TMGI, at least one instruction indicating at least one of the following: • Whether the capability-reduced terminal device is supported for TMGI at adjacent access nodes. • At least one type of terminal device with reduced capability for TMGI supported at adjacent access nodes, or • At least one size of the CFR used for TMGI at adjacent access nodes; The neighbor cell frequency information, comprising a mapping between at least one neighbor cell frequency and at least one FSAI for at least one MBS session, is transmitted to the terminal device, wherein the neighbor cell frequency is the operating frequency of the neighbor cells of the service cell provided by the device, and the neighbor cell frequency information is based on at least one TMGI, at least one indication, and the mapping between at least one TMGI and at least one FSAI for at least one MBS session; and at least one indication for at least one neighbor cell provided by one or more neighboring access nodes is transmitted to the terminal device, wherein the at least one indication indicates at least one of the following for at least one neighbor cell: • Whether the reduced-capacity terminal device is supported for at least one FSAI or at least one MBS meeting. • Supported by at least one type of terminal device with reduced capability for at least one FSAI or at least one MBS conversation, or • At least one size of a public frequency resource CFR available for at least one FSAI or at least one MBS meeting.

[0227] Example 14. A device as in Example 13, wherein at least one memory and the instructions are configured, together with at least one processor, to cause the device to perform the following operations: transmit at least one TMGI associated with at least one MBS session at the device to each of one or more adjacent access nodes, and for each of the at least one TMGI associated with at least one MBS session at the device, at least one indication indicates at least one of the following: • Whether the capability-reduced terminal device is supported for TMGI at the device level. • At least one type of terminal device that is supported for TMGI capability reduction at the device level, or • At least one size of the CFR used for TMGI at the device.

[0228] Example 15. A device such as in Example 13 or 14, wherein at least one memory and the instructions are configured, together with at least one processor, to cause the device to perform the following operations before transmitting adjacent cell frequency information: receiving a broadcast MBS session establishment request from the core network function, wherein the broadcast MBS session establishment request includes at least one FSAI associated with the MBS session; and determining, based on the broadcast MBS session establishment request, at least one TMGI, and at least one indication received from one or more adjacent access nodes, a mapping between at least one TMGI and at least one FSAI for at least one MBS session.

[0229] Example 16. A device as in Example 15, wherein at least one memory and such instructions are configured together with at least one processor to cause the device to perform the following operations: receive configuration information from an operational, administrative, and management OAM entity, wherein the configuration information includes at least one indication indicating at least one FSAI associated with an MBS conversation supported by the device, defined for a degraded terminal device; and trigger the transmission of the MBS conversation within a CFR defined for a degraded terminal device based on the configuration information.

[0230] Example 17. A device as described in any of Examples 9 to 16, wherein adjacent cell frequency information and at least one indication are transmitted to the terminal device in a System Information Block 21 (SIB21) message.

[0231] Example 18. A method comprising: receiving neighboring cell frequency information, comprising a mapping between at least one neighboring cell frequency and at least one Frequency Selection Area Identifier (FSAI) for at least one Multicast Broadcast Service (MBS) session, wherein the neighboring cell frequency is the operating frequency of a neighboring cell of a device's service cell; and receiving at least one indication for at least one neighboring cell indicating at least one of the following: • Whether the reduced-capacity terminal device is supported for at least one FSAI or at least one MBS meeting. • Supported by at least one type of terminal device with reduced capability for at least one FSAI or at least one MBS conversation, or • At least one size of a public frequency resource CFR available for at least one FSAI or at least one MBS meeting; and A cell reselection procedure is performed based on cell measurements, adjacent cell frequency information, and at least one instruction.

[0232] Example 19. A method comprising: Receive at least one indication from at least one adjacent access node indicating at least one of the following: • Whether the capability-reduced terminal device is supported at at least one adjacent access node in at least one adjacent access node for at least one Frequency Selection Area Identifier (FSAI) or at least one Multicast Broadcast Service (MBS) meeting. • At adjacent access nodes, the capability of supporting at least one type of terminal device for at least one FSAI or at least one MBS conversation is reduced. • At least one size of the common frequency resource CFR used for at least one FSAI or at least one MBS negotiation at adjacent access nodes. • Currently, at least one type of CFR used by adjacent access nodes for at least one FSAI or at least one MBS session; The neighbor cell frequency information, comprising a mapping between at least one neighbor cell frequency and at least one FSAI used for at least one MBS session, is transmitted to the terminal device, wherein the neighbor cell frequency is the operating frequency of the neighbor cells of the service cell provided by the device; and at least one indication is transmitted to the terminal device, the at least one indication indicating at least one of the following for at least one neighbor cell provided by at least one neighbor access node: • Whether the reduced-capacity terminal device is supported for at least one FSAI or at least one MBS meeting. • Supported by at least one type of terminal device with reduced capability for at least one FSAI or at least one MBS conversation, or • Can be used for at least one size of CFR in at least one FSAI or at least one MBS meeting.

[0233] Example 20. A method comprising: receiving from each of one or more adjacent access nodes at at least one Multicast Broadcast Service (MBS) session being conducted at the adjacent access nodes at at least one of the adjacent access nodes, and for each of the at least one TMGI at least at least receiving at least one indication indicating at least one of the following: • Whether the capability-reduced terminal device is supported for TMGI at adjacent access nodes. • At least one type of terminal device with reduced capability for TMGI supported at adjacent access nodes, or • At least one size of the CFR used for TMGI at adjacent access nodes; The neighbor cell frequency information, comprising a mapping between at least one neighbor cell frequency and at least one FSAI for at least one MBS session, is transmitted to the terminal device, wherein the neighbor cell frequency is the operating frequency of the neighbor cells of the service cell provided by the device, and the neighbor cell frequency information is based on at least one TMGI, at least one indication, and the mapping between at least one TMGI and at least one FSAI for at least one MBS session; and at least one indication for at least one neighbor cell provided by one or more neighboring access nodes is transmitted to the terminal device, wherein the at least one indication indicates at least one of the following for at least one neighbor cell: • Whether the reduced-capacity terminal device is supported for at least one FSAI or at least one MBS meeting. • Supported by at least one type of terminal device with reduced capability for at least one FSAI or at least one MBS conversation, or • At least one size of a public frequency resource CFR available for at least one FSAI or at least one MBS meeting.

[0234] Example 21. A non-transitory computer-readable medium having instructions stored thereon, which, when executed by a computing device, cause the computing device to perform the following operations: receiving neighboring cell frequency information, including a mapping between at least one neighboring cell frequency and at least one Frequency Selection Area Identifier (FSAI) for at least one Multicast Broadcast Service (MBS) session, wherein the neighboring cell frequency is the operating frequency of a neighboring cell of a device's service cell; receiving at least one instruction indicating at least one of the following for at least one neighboring cell: • Whether the reduced-capacity terminal device is supported for at least one FSAI or at least one MBS meeting. • Supported by at least one type of terminal device with reduced capability for at least one FSAI or at least one MBS conversation, or • At least one size of a public frequency resource CFR available for at least one FSAI or at least one MBS meeting; and A cell reselection procedure is performed based on cell measurements, adjacent cell frequency information, and at least one instruction.

[0235] Example 22. A non-transitory computer-readable medium having instructions stored thereon, which, when executed by a computing device, cause the computing device to perform the following operations: receive from at least one adjacent access node at least one of the following: • Whether the capability-reduced terminal device is supported at at least one adjacent access node in at least one adjacent access node for at least one Frequency Selection Area Identifier (FSAI) or at least one Multicast Broadcast Service (MBS) meeting. • At adjacent access nodes, the capability of supporting at least one type of terminal device for at least one FSAI or at least one MBS conversation is reduced. • At least one size of the common frequency resource CFR used for at least one FSAI or at least one MBS negotiation at adjacent access nodes. • Currently, at least one type of CFR used by adjacent access nodes for at least one FSAI or at least one MBS session; The neighbor cell frequency information, comprising a mapping between at least one neighbor cell frequency and at least one FSAI used for at least one MBS session, is transmitted to the terminal device, wherein the neighbor cell frequency is the operating frequency of the neighbor cells of the service cell provided by the device; and at least one indication is transmitted to the terminal device, the at least one indication indicating at least one of the following for at least one neighbor cell provided by at least one neighbor access node: • Whether the reduced-capacity terminal device is supported for at least one FSAI or at least one MBS meeting. • Supported by at least one type of terminal device with reduced capability for at least one FSAI or at least one MBS conversation, or • Can be used for at least one size of CFR in at least one FSAI or at least one MBS meeting.

[0236] Example 23. A non-transitory computer-readable medium having instructions stored thereon, which, when executed by a computing device, cause the computing device to perform the following operations: receive from each of one or more adjacent access nodes at at least one of at least one Multicast Broadcast Service (MBS) session being conducted at the adjacent access nodes at at least one of the adjacent access nodes at each of the at least one TMGI at each of the at least one TMGI at each of the at least one access node at ... • Whether the capability-reduced terminal device is supported for TMGI at adjacent access nodes. • At least one type of terminal device with reduced capability for TMGI supported at adjacent access nodes, or • At least one size of the CFR used for TMGI at adjacent access nodes; The neighbor cell frequency information, comprising a mapping between at least one neighbor cell frequency and at least one FSAI for at least one MBS session, is transmitted to the terminal device, wherein the neighbor cell frequency is the operating frequency of the neighbor cells of the service cell provided by the device, and the neighbor cell frequency information is based on at least one TMGI, at least one indication, and the mapping between at least one TMGI and at least one FSAI for at least one MBS session; and at least one indication for at least one neighbor cell provided by one or more neighboring access nodes is transmitted to the terminal device, wherein the at least one indication indicates at least one of the following for at least one neighbor cell: • Whether the reduced-capacity terminal device is supported for at least one FSAI or at least one MBS meeting. • Supported by at least one type of terminal device with reduced capability for at least one FSAI or at least one MBS conversation, or • At least one size of a public frequency resource CFR available for at least one FSAI or at least one MBS meeting.

[0237] Throughout this specification, reference to an embodiment or an embodiment means that a particular feature, structure, or characteristic described in connection with that embodiment is included in at least one embodiment of the solution of the invention. Therefore, the phrases "in one embodiment" or "in an embodiment" appearing in various places throughout this specification do not necessarily refer to the same embodiment.

[0238] As used herein, for convenience, multiple project objects, structural elements, composite elements, and / or materials may be presented in a common list. However, such lists should be understood as if each member of the list were individually identified as a separate and unique member. Therefore, unless indicated otherwise, an individual member of this list should not be construed as substantially equivalent to any other member of the same list solely based on its presentation in the common group. Furthermore, various embodiments and examples of the solutions of the present invention may be referenced herein together with alternatives for its various components. It should be understood that such embodiments, examples, and alternatives should not be construed as actual equivalents of each other, but are to be considered as independent and autonomous representations of the solutions of the present invention.

[0239] Although embodiments have been described above with reference to examples accompanying the accompanying drawings, it is clear that the embodiments are not limited thereto but can be modified in several ways within the scope of the appended claims. Therefore, all phrases and expressions should be interpreted broadly, and are intended to illustrate rather than limit the embodiments. It will be apparent to those skilled in the art that the inventive concept can be implemented in various ways as technology advances. Furthermore, it will be clear to those skilled in the art that the described embodiments can, but are not necessarily, combined with other embodiments in various ways.

[0240] Industrial applicability: At least some embodiments have industrial applications in wireless communications.

[0241] 100,102:UE 104: Distributed Unit / Ground Relay Node / Access Node 106: Satellite 108: Centralized Unit 110: Core Network 112: Publicly switched telephone network or Internet 114: Cloud 201,202,301,302,303,401,402,501,502,504,506,507,509,511,513,515,517,518,519, 520,601,602,603,604,606,611,612,613,615,702,704,705,706,708,802,804,805,806, 808,810,901,902,1001,1002,1003,1101,1102,1103,1201,1203,1205,1206,1208,1210, Blocks 1212, 1214, 1216, 1217, 1218, 1219: 503,510,514,516,605,614,701,703,707,801,803,807,809,1202,1209,1211,1213,1215: Messages 505,1204: Broadcast MBS meeting setup request / message 508,512,1207:Xn Create or Modify Message 1301: Equipment 1310: Interface 1320: Communication control circuit system 1330: Memory 1331:Algorithm 1332: Database

Claims

1. A user equipment (100) comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the user equipment to perform at least the following operations: receiving a service announcement of a multicast broadcast service (MBS); receiving at least one indication in the service announcement indicating support for all or at least some capability-degraded user equipment for the multicast broadcast service; and performing a cell reselection procedure based on cell measurement and the at least one indication.

2. The user equipment (100) of request item 1, wherein the service announcement includes at least one Frequency Selection Area Identifier (FSAI) associated with the multicast service and at least one indication indicating that the at least one Frequency Selection Area Identifier is defined for a degraded user equipment, and / or the service announcement includes at least one frequency associated with the multicast service and at least one indication indicating that the at least one frequency is defined for a degraded user equipment, the execution of the cell reselection procedure is further based on the at least one Frequency Selection Area Identifier and / or the at least one frequency.

3. The user equipment (100) of claim 2, wherein the user equipment is a capability-degraded user equipment; and wherein the execution of the cell reselection procedure includes: in the cell reselection procedure, prioritizing frequencies associated with the at least one frequency selection region identifier or the at least one frequency defined for the capability-degraded user equipment.

4. User equipment (100) as requested in claim 3, wherein the service announcement further includes one or more frequency selection area identifiers or one or more frequencies without any indication that the one or more frequency selection area identifiers or the one or more frequencies are defined for a degraded user equipment; and wherein the prioritization includes: in the cell reselection procedure, giving priority at least to frequencies associated with the at least one frequency selection area identifier or the at least one frequency indicated as defined for a degraded user equipment over frequencies not associated with the one or more frequency selection area identifiers or one or more frequencies not indicated as defined for a degraded user equipment.

5. The user equipment (100) of claim 2, wherein the user equipment is a non-capacitated user equipment, the service announcement further includes one or more frequency selection area identifiers or one or more frequencies without any indication that the one or more frequency selection area identifiers or the one or more frequencies are defined for a capacity-depressed user equipment; and wherein the execution of the cell reselection procedure includes: in the cell reselection procedure, giving priority to frequencies associated with the one or more frequency selection area identifiers or the one or more frequencies not indicated as defined for a capacity-depressed user equipment over frequencies associated with at least one frequency selection area identifier or the at least one frequency indicated as defined for a capacity-depressed user equipment.

6. The user equipment (100) of request item 2, wherein, for at least one frequency selection area identifier or at least one of the at least one frequencies, the service announcement further includes information regarding at least one bandwidth limitation condition indicated to be followed by the at least one frequency selection area identifier or at least one frequency defined for the user equipment with reduced capabilities.

7. User equipment (100) as claimed in claim 6, wherein the at least one bandwidth limitation includes a condition for a bandwidth size and / or a condition for a type of user equipment with reduced capabilities.

8. User equipment (100) as requested in item 6 or 7, wherein the user equipment is a capability-reduced user equipment; and wherein the execution of the cell reselection procedure includes: determining whether the capability-reduced user equipment satisfies the at least one bandwidth limitation for the at least one frequency or the at least one frequency selection region identifier associated with the at least one bandwidth limitation; and in the cell reselection procedure, prioritizing the frequency associated with the at least one frequency selection region identifier or the at least one frequency for which the capability-reduced user equipment satisfies the at least one bandwidth limitation.

9. User equipment (100) as requested in item 8, wherein the service announcement contains one or more frequency selection area identifiers or one or more frequencies without any indication that the one or more frequency selection area identifiers or the one or more frequencies are defined for a degraded user equipment, the prioritization includes: in the cell reselection procedure, giving priority to frequencies associated with the at least one frequency selection area identifier or the at least one frequency that satisfies the at least one bandwidth limitation condition for the degraded user equipment at least over frequencies not associated with the one or more frequency selection area identifiers or the one or more frequencies that are not defined for a degraded user equipment.

10. The user equipment (100) of request item 1, wherein the user equipment is a capability-degraded user equipment.

11. The user equipment (100) of request item 1, wherein the at least one indication explicitly indicates that the user equipment is supported for the multicast service with reduced capabilities.

12. User equipment (100) of any of the requests 1 to 7, wherein the service announcement indicates at least one frequency selection area identifier associated with the multicast broadcast service session or at least one frequency associated with the multicast broadcast service session, wherein the execution of the cell reselection procedure is further based on the service announcement.

13. User equipment (100) of any of the requests 1 to 7, wherein the at least one message is or includes a system information block 21 message, namely SIB21 message.

14. A user equipment (100) of any of claims 1 to 7, wherein the at least one memory and the instructions are configured together with the at least one processor to cause the user equipment to perform the following operations: operate in a Radio Resource Control (RRC) idle or inactive state during the execution of the cell reselection procedure.

15. A method for communication, comprising: receiving a service announcement of a multicast service (MBS) via a user equipment; receiving at least one instruction in the service announcement via the user equipment, the at least one instruction indicating support for all or at least some capabilities of the user equipment for the multicast service; and performing a cell reselection procedure via the user equipment based on cell measurement and the at least one instruction.

16. A non-transitory computer-readable medium having instructions stored thereon, which, when executed by a computing device, cause the computing device to perform the following operations: receiving a service announcement of a multicast broadcast service (MBS); receiving at least one instruction in the service announcement indicating support for all or at least some capability-degraded user devices for the multicast broadcast service; and performing a cell reselection procedure based on cell measurement and the at least one instruction.

Images