Frequency prioritization for reduced capability terminal devices for receiving multicast broadcast services

Abstract

According to an aspect, there is provided an apparatus configured to perform the following. The apparatus receives neighbor frequency information comprising a mapping between at least one neighbor cell frequency and at least one frequency selection area identification, FSAI, for at least one multicast-broadcast service, MBS, session. The apparatus receives at least one indication indicating, for each at least one neighbor cell, at least one of whether reduced capability terminal devices are supported for the at least one FSAI or the at least one MBS session, at least one type of reduced capability terminal devices supported for the at least one FSAI or the at least one MBS session, or at least one size of common frequency resource, CFR, available for the at least one FSAI or the at least one MBS session. The apparatus performs a cell reselection procedure based on cell measurements and the neighbor cell frequency information and the at least one indication.

Description

Technical Field

[0001] Various example embodiments involve wireless communication. Background Technology

[0002] Reduced-capability (RedCap) terminal equipment refers to terminal equipment that conforms to certain predefined bandwidth (BW) limitations. In other words, RedCap terminal equipment cannot use a receive bandwidth greater than the predefined maximum bandwidth (e.g., 20 MHz). Correspondingly, RedCap-specific common frequency resources (CFRs) have been introduced for RedCap terminal equipment to receive multicast broadcast services (MBS). Since the service area of ​​a specific Temporary Mobile Group Identifier (TMGI) can include both access nodes that support and do not support RedCap CFRs, the same frequency selection guidelines used for cell reselection do not apply to both RedCap and non-RedCap terminal equipment due to the fact that RedCap terminal equipment can only receive services in some cells within its service area. Therefore, a new mechanism is needed to guide both RedCap and non-RedCap terminal equipment in cell reselection decisions in a different way. Summary of the Invention

[0003] According to one aspect, the subject matter of the independent claim is provided. Embodiments are defined in the dependent claims.

[0004] One or more examples of the implementation are illustrated in more detail in the accompanying drawings and the following description. Other features will be apparent from the description and drawings, as well as from the claims. Attached Figure Description

[0005] Figure 1 The illustrations show some of the systems to which these embodiments can be applied;

[0006] Figures 2 to 4 The process according to an embodiment is illustrated;

[0007] Figure 5 The illustration depicts a signaling scenario between a terminal device, three access nodes, and a core network according to an embodiment.

[0008] Figure 6A and Figure 6B The illustration shows two exemplary signaling scenarios between a terminal device for performing cell reselection, three access nodes, and the core network, according to an embodiment.

[0009] Figure 7 and Figure 8The illustration shows two alternative core network signaling scenarios, according to an embodiment, for enabling cell reselection between the Multicast / Broadcast Session Management Function (MB-SMF), Network Exposure Function (NEF), and Application Function (AF);

[0010] Figures 9 to 11 The process according to an embodiment is illustrated;

[0011] Figure 12 The illustration depicts a signaling scenario between a terminal device, three access nodes, and a core network according to an embodiment; and

[0012] Figure 13 The illustration shows an apparatus according to some embodiments. Detailed Implementation

[0013] The following embodiments are presented by way of example only. Although this specification may refer to "a," "an," or "some" embodiments and / or examples in several places in the text, this does not necessarily mean that each reference refers to the same(s) embodiments(s) or examples(s), or that a particular feature applies 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 ” and similar wording (where 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” can be defined as follows. The 3GPP (3rd Generation Partnership Project) has introduced RedCap devices in New Radio (NR) Release 17 (Rel-17). For example, RedCap devices may also be referred to as RedCap UEs, RedCap UEs, NR-Lite devices, or NR-Light devices. 3GPP RedCap NR features reduce UE complexity by requiring fewer receiver / transmitter (Rx / Tx) antennas, reducing UE bandwidth usage, lower UE power consumption, relaxed data rates, and relaxed UE processing time and capabilities, thus helping to enable exciting use cases such as those surrounding industrial wireless sensors, video surveillance, and wearable devices.

[0016] In NR, the frequency range below 6 GHz or 7 GHz can be referred to as FR1, while the frequency range above 24 GHz (or more precisely, 24 to 52.6 GHz) can be referred to as FR2. During and after initial access, the maximum bandwidth of an FR1 RedCap UE is 20 MHz. During and after initial access, the maximum bandwidth of an FR2 RedCap UE is 100 MHz. For frequency bands requiring a minimum of 2 receive (Rx) antenna ports for a traditional NR UE, or a minimum of 4 Rx antenna ports, the minimum number of Rx branches supported by the RedCap UE is 1. For a RedCap UE with 1 Rx branch, one 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., in a given cell, there may be both RedCap devices and non-RedCap UEs).

[0018] In the following text, radio access architectures based on Long Term Evolution Advanced (LTE-A) or New Radio (NR, 5G) will be used as examples of access architectures to which embodiments can be applied to describe different exemplary embodiments; however, the embodiments are not limited to such architectures. It will be apparent to those skilled in the art that these 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 Universal Mobile Telecommunications System (UMTS) radio access networks (UTRAN or E-UTRAN), Long Term Evolution (LTE, the same as E-UTRA), wireless local area networks (WLAN or WiFi), Microwave Access Global Interoperability (WiMAX), Bluetooth®, Personal Communication Services (PCS), ZigBee®, Wideband Code Division Multiple Access (WCDMA), systems using Ultra Wideband (UWB) technology, sensor networks, Mobile Ad Hoc Networks (MANET), and Internet Protocol Multimedia Subsystem (IMS), or any combination thereof.

[0019] Figure 1 An example of a simplified system architecture is shown, depicting only some elements and functional entities (all of which are logical units, and their implementation may differ from what is shown). Figure 1 The connections shown are logical connections; the actual physical connections may differ. It will be apparent to those skilled in the art that the system typically includes, in addition to... Figure 1 Other functions and structures besides those shown in the diagram.

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

[0021] Figure 1 The example illustrates a portion of an exemplary wireless access network.

[0022] A communication system typically includes more than one (e / g)NodeB. In this 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. An (e / g)NodeB is a computing device configured to control the radio resources of the communication system to which it is coupled. A NodeB can also be referred to as a base station, access point, or any other type of docking device, including relay stations capable of operating in a wireless environment. An (e / g)NodeB includes, or is coupled to, a transceiver. A connection is provided from the transceiver of the (e / g)NodeB to an antenna element, which establishes a bidirectional radio link to the user equipment. The antenna element may include multiple antennas or antenna elements. The (e / g)NodeB is also connected to the core network 110 (CN or Next Generation Core NGC). Depending on the system, the counterpart on the CN side may be a Serving Gateway (S-GW, which routes and forwards user data packets), a Packet Data Network Gateway (P-GW) for providing connectivity of the user equipment (UE) to external packet data networks, or a Mobility Management Entity (MME), etc.

[0023] In some embodiments, the core network 110 may include an application function (AF). 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). For example, the AF's responsibilities include accessing network exposure functions (NEF) to retrieve resources, interacting with policy control functions (PCF) to enable policy control, performing service routing for applications, and providing application services to subscribers.

[0024] In some embodiments, the core network 110 may include a network exposure function (NEF). For example, the NEF may be configured to securely expose services and capabilities provided by 3GPP network functions.

[0025] In some embodiments, the core network 110 may include a multicast / broadcast session management function (MB-SMF). For example, the MBS-SMF may be configured to 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 all alternative terms used in the relevant technical field, namely "multicast-broadcast" or "multicast broadcast".

[0026] User equipment (also referred to as UE, user equipment, user terminal, terminal equipment, etc.) illustrates a type of device to which resources on the air interface are allocated and assigned, and therefore any feature described herein using the term "user equipment" can be implemented using 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. User equipment may include mobile devices and at least one general-purpose integrated circuit card (UICC).

[0027] User equipment (UE) generally refers to portable computing devices, including wireless mobile communication devices operating with or without a Subscriber Identity Module (SIM) or User-Unified Classification (UICC), including but not limited to: mobile stations (mobile phones), smartphones, personal digital assistants (PDAs), cell phones, devices using wireless modems (alarm or measuring devices, etc.), laptops and / or touchscreen computers, tablets, game consoles, notebooks, and multimedia devices. It should be understood that UE can also be a nearly exclusive uplink-only device, an example of which is a camera or camcorder that loads images or video clips onto a network. UE can also be a device capable of operating in an Internet of Things (IoT) network, a scenario where objects are provided with the ability to transmit data over a network without human-to-human or human-to-computer interaction. UE (or, in some embodiments, a Layer 3 relay node) is configured to perform one or more UE functions. UE can also be referred to as a subscriber unit, mobile station, remote terminal, access terminal, user terminal, or user equipment (UE), to name just a few.

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

[0029] It should be understood that, Figure 1 In this illustration, for clarity only, the user equipment is depicted as having two antennas. The number of receive and / or transmit antennas may vary naturally depending on the current implementation.

[0030] Furthermore, although the device is depicted as a single entity, different units, processors, and / or memory units ( Figure 1 (Not all of them are shown in the text) can be implemented.

[0031] 5G enables the use of multiple-input multiple-output (MIMO) antennas, far more base stations or nodes than LTE (the so-called small cell concept), including macro sites operating in cooperation with even smaller stations, and the adoption of various radio technologies depending on service requirements, use cases, and / or available spectrum. 5G mobile communications support a wide range of use cases and related applications, including video streaming, augmented reality, different data sharing methods, and various forms of machine-type applications, including vehicle safety, different sensors, and real-time control. 5G is expected to have multiple radio interfaces—sub-6 GHz, centimeter wave, and millimeter wave—and will also be able to integrate with existing legacy radio access technologies such as LTE. At least in the early stages, integration with LTE can be achieved as a system, where macro coverage is provided by LTE, and 5G radio interface access comes from small cells aggregated to LTE. In other words, 5G is planned to support both RAT inter-operability (such as LTE-5G) and RI inter-operability (radio interface inter-operability, such as sub-6 GHz-centimeter wave, sub-6 GHz-centimeter wave-millimeter wave). One of the concepts being considered for use in 5G networks is network slicing, where multiple independent and dedicated virtual sub-networks (network instances) can be created within the same infrastructure to run services with different requirements for latency, reliability, throughput, and mobility.

[0032] The current architecture in LTE networks is entirely distributed across radios and centrally located within the core network. Low-latency applications and services in 5G require bringing content closer to the radio, leading to local breakthroughs and multi-access edge computing (MEC). 5G enables analytics and knowledge generation at the data source. This approach leverages resources that may not have continuous network connectivity, such as laptops, smartphones, tablets, and sensors. MEC provides a distributed computing environment for application and service hosting. It also has the ability to store and process content closer to cellular subscribers for faster response times. Edge computing encompasses a wide range of technologies, such as wireless sensor networks, mobile data acquisition, mobile signature analytics, collaborative distributed peer-to-peer self-organizing networks and processing, and can also be categorized as local cloud / fog computing and grid / mesh computing, dew computing, mobile edge computing, cloud computing, distributed data storage and retrieval, autonomous and self-healing networks, remote cloud services, augmented and virtual reality, data caching, the Internet of Things (massive connectivity and / or latency critical), and critical communications (autonomous vehicles, traffic safety, real-time analytics, time-critical control, healthcare applications).

[0033] The communication system can also communicate with other networks, such as the public switched telephone network or the Internet, or utilize services provided by them. The communication network can also support the use of cloud services; for example, at least a portion of the core network operation can be performed as a cloud service (this is in...). Figure 1 (Described by “Cloud” 114). The communication system may also include a central control entity, etc., to provide facilities for different operators’ networks to cooperate, for example, in terms of spectrum sharing.

[0034] Edge cloud can be introduced into the RAN by leveraging Network Functions Virtualization (NVF) and Software-Defined Networking (SDN). Using edge cloud can mean that access node operations are performed at least partially in servers, hosts, or nodes that are operatively coupled to remote radio heads or units (RUs), or base stations including radio components. Alternatively, node operations may be distributed across multiple servers, nodes, or hosts. The application of the cloud RAN architecture enables real-time RAN functions to be performed at the RAN side (in distributed unit DU 104), and non-real-time functions to be performed centrally (in central or centralized unit CU 108). Therefore, in summary, 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 of which is communicatively connected to at least one of the one or more distributed units.

[0035] It should also be understood that the workforce distribution between core network operations and base station operations may differ from, or even not exist, in LTE. Some other technological advancements that may be used are big data and all-IP, which could transform how networks are being built and managed. 5G (or New Radio, NR) networks are being designed to support multiple hierarchical structures, where MEC servers can be placed between the core and base stations or nodeBs (gNBs). It should be recognized that MEC can also be applied to 4G networks.

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

[0037] It will be apparent to those skilled in the art that the depicted system is merely an example of a part of a wireless access system, and in practice, the system may include multiple (e / g) NodeBs, user equipment may be able to access multiple radio cells, and the system may also include other devices, such as physical layer relay nodes or other network elements. At least one (e / g) NodeB may be a home (e / g) nodeB. Furthermore, multiple different types of radio cells, as well as multiple radio cells, may be provided in the geographical area of ​​the radio communication system. Radio cells may be macrocells (or umbrella cells), which are typically areas with a diameter of up to tens of kilometers, or smaller cells, such as microcells, femtocells, or picocells. Figure 1 The (e / g) NodeB can provide any type of these cells. 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 cells of a certain type, and therefore multiple (e / g) NodeBs are required to provide such a network structure.

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

[0039] The 6G architecture is designed to enable easy integration of everything, such as networks, joint communications and sensing, and non-terrestrial and terrestrial networks. It envisions 6G systems incorporating machine learning algorithms as well as local and distributed computing capabilities, where virtualized network functions can be distributed across core and edge computing resources. Far-edge computing, where computing resources are pushed to the very edge of the network, becomes part of a distributed computing environment, such as in “zero-latency” scenarios. 5G systems can also employ this capability. More generally, it envisions a practical (radio) communication system consisting of one or more computer programs executing within a programmable infrastructure such as general-purpose computing entities (servers, processors, etc.).

[0040] At least some of the embodiments discussed below specifically relate to broadcasting as defined in 3GPP Release 17. Broadcast service is defined as an alternative to multicast service. In broadcast service, a transmitter sends the service to all users (or UEs) within the broadcast service area. In multicast service, one or more transmitters send the service to a dedicated group of users (or UEs). Broadcast service enables UEs to receive in any Radio Resource Control (RRC) state, as long as the UE is within coverage. Unlike multicast service, broadcast service requires the use of specific service announcements associated with MBS broadcast service and Public Land Mobile Network (PLMN). Temporary Mobile 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 UE can receive the MCCH and the broadcast data itself in the frequency area known as the Common Frequency Resource (CFR).

[0042] For broadcast, the UE receives the Frequency Selection Area Identifier (FSAI) or (for broadcast MBS sessions) identifier applicable to the MBS service via a service advertisement (which may be sent via unicast or using another broadcast session). Generally, the (MBS)FSAI is used for 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 in and near which (multiple) cells advertise the MBS FSAI and associated frequencies. The same (multiple) FSAIs can apply to multiple MBS services and / or multiple broadcast MBS sessions.

[0043] RAN nodes (e.g., access nodes) can be configured with FSAIs. For example, FSAI configuration can be performed via 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, the RAN node can advertise information about the configured MBSFSAIs and the RAN node's operating frequencies in the SIB 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 the 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 preferentially camp on the frequency of the cell providing a specific broadcast session that the UE is interested in receiving. The UE can compare the MBS FSAIs included in the service advertisement with the MBS FSAIs included in the SIB to perform frequency selection. It should be noted that the UE can also, or alternatively, directly receive the frequencies providing the service in the service advertisement. In this scenario, the UE can directly prioritize the frequency indicated in the service advertisement. Therefore, the UE may not need (multiple) FSAIs or SIB21s to perform frequency selection.

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

[0045] In some cases, during the start of a broadcast MBS session and during broadcast MBS session updates, the MB-SMF may include (multiple) MBS FSAIs of the MBS session and send them to the RAN node via the Application Management Function (AMF). The RAN node can then use these (multiple) MBS FSAIs to determine the cells and / or frequencies within the MBS service area for broadcasting MBS session data.

[0046] The reduced-capability UE or terminal device will be discussed in further detail below to provide context and background for the embodiments. 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 separately, for example, by System Information Block 1 (SIB1). If the CFR of MBS is properly configured for the RedCap terminal device, the RedCap terminal device can be able to receive broadcast data. That is, broadcast data can be received 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. Which CFR should be utilized for a particular service depends on the access node (e.g., gNB), because there is no indication from the core network to the access node that a broadcast session is received by a non-RedCap / RedCap terminal device.

[0047] As described above, a new RedCap MBS CFR, different from the earlier Broadcast MBS CFR, has been introduced for receiving broadcast control and data. It is assumed that some services will be sent in the RedCap CFR, and how the gNB chooses to utilize this CFR is determined by the OAM configuration.

[0048] Non-RedCap terminal devices are not expected to read the RedCap CFR, and RedCap terminal devices are unable to read the non-RedCap CFR due to capability limitations. Therefore, if a broadcast service is intended for both RedCap and non-RedCap terminal devices, the access node should transmit the same service in two different CFRs. Thus, separate SIB20 and MCCH are used for RedCap terminal devices. If one or more access nodes in a particular TMGI service area do not utilize a separate RedCap CFR (e.g., because the access node is not configured for the function, or simply due to congestion leading to a decision to transmit service only in the non-RedCap CFR), then the same frequency selection guidelines do not apply to either RedCap or non-RedCap terminal devices. That is, if the same frequency selection guidelines based on a separate RedCap CFR were used, the RedCap terminal device would only be able to receive service in some cells within the service area.

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

[0050] Figure 2 The illustration depicts a process for performing a notified cell reselection decision according to an embodiment. Figure 2 The process illustrated can be performed by a terminal device (or UE) or a portion thereof. Here, the terminal device can be... Figure 1 One of UE 100 and UE 102. The terminal device can be a RedCap terminal device or a non-RedCap terminal device. In the following text, for simplicity, the execution... Figure 2 The physical entity involved in the process is called a device.

[0051] refer to Figure 2 The device receives service announcements from the MBS in box 201. The service announcements received in box 201 may correspond to broadcast transmissions. Service announcements may be sent (or broadcast) by the access node (e.g., gNB). Service announcements may be initiated by the AF.

[0052] The service announcement in 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 RedCap terminal equipment; or 2) at least one frequency and at least one indication indicating that the at least one frequency is defined for RedCap terminal equipment. 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 designed to guide RedCap terminal equipment to a neighboring cell frequency that can provide MBS according to the BWP restrictions of the RedCap UE. Based on at least one indication (of any type above), the receiving device is able to distinguish between optimized FSAIs / frequency for RedCap and non-RedCap.

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

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

[0055] In some embodiments, for at least one of at least one FSAI or at least one frequency defined for a RedCap terminal device, the service notification may further include: information regarding at least one bandwidth limitation condition, indicating that the at least one FSAI or at least one frequency defined for a terminal device with reduced capabilities meets the at least one bandwidth limitation condition. For example, the at least one bandwidth limitation condition may include: at least one condition specifying a limitation in terms of terminal device type (e.g., only UE type 1 is supported), and / or at least one condition specifying a limitation in terms of bandwidth or bandwidth portion (e.g., a 100 MHz bandwidth limitation). Here, it is assumed that the terminal device type is associated with (multiple) bandwidths or (multiple) frequency bands that can be used by terminal devices of the defined types. For example, each terminal device type is associated with at least one bandwidth or at least one frequency band. The terminal device may store information in memory regarding a mapping between one or more terminal device types and lists of one or more associated bandwidths and / or frequency bands. The at least one FSAI and / or at least one frequency can only be used by the terminal device if the terminal device meets or is compatible with at least one of the bandwidth limitation conditions.

[0056] When a device (e.g., a terminal device) receives a service advertisement for an MBS in box 201, the device can be in any RRC state. After receiving the service advertisement for an MBS, the device can transition to an RRC inactive or idle state and begin receiving the MBS specified in the service advertisement.

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

[0058] Cell measurements can be performed by the device itself. Cell measurements may include measurements of signals transmitted by one or more access nodes. Cell measurements may include measurements of at least one of, for example: 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 relating to one or more (radio) frequencies (used in one or more neighboring cells). Cell measurements may include any cell measurements performed in RRC inactive or idle states, as defined in 3GPP TS 38.306 and / or TS 38.304.

[0059] How service announcements are used during cell reselection depends on whether the device is a RedCap terminal device (or part thereof) or a non-RedCap terminal device (or part thereof).

[0060] If the device is a RedCap terminal device (or part thereof), then performing the cell reselection process based on the service advertisement in box 202 may include prioritizing frequencies associated with at least one FSAI or at least one frequency defined for the RedCap terminal device during the cell reselection process. Here and in the following discussion related to box 202, the prioritized frequency may specifically refer to a neighboring cell frequency (i.e., a frequency used in one or more neighboring cells of the terminal device). A neighboring cell frequency is the operating frequency of a neighboring cell of the serving cell of the device. If the service advertisement in box 201 includes one or more FSAIs or frequencies not indicated as being defined for the RedCap terminal device, then the device may specifically prioritize, during the cell reselection process, frequencies associated with at least one FSAI or at least one frequency defined for the RedCap terminal device, at least relative to frequencies associated with one or more FSAIs or frequencies not indicated as being defined for the RedCap terminal device. Optionally, if one or more FSAIs or frequencies for a RedCap terminal device are unavailable in the device's current cell (e.g., because SIB21 does not contain a corresponding FSAI-to-neighbor cell mapping), the device may prioritize one or more FSAIs or frequencies not defined for a RedCap terminal device relative to at least one FSAI or frequency defined 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 a non-RedCap terminal device (or part thereof), performing the cell reselection process based on service announcements in box 202 may include avoiding or ignoring frequencies associated with at least one FSAI or at least one frequency defined for RedCap terminal devices during the cell reselection process.

[0062] If the device is a non-RedCap terminal device (or part thereof), and the service advertisement in box 201 includes one or more FSAIs or frequencies not specified for a RedCap terminal device, then performing the cell reselection process based on the service advertisement in box 202 may include prioritizing frequencies associated with one or more FSAIs or frequencies not specified for a RedCap terminal device relative to frequencies associated with at least one FSAI or frequency specified for a RedCap terminal device. Alternatively, if one or more FSAIs or frequencies for a non-RedCap terminal device are not available in the device's current cell (e.g., because SIB21 does not contain a corresponding FSAI-to-neighbor cell mapping), the device may prioritize at least one FSAI or frequency specified for a RedCap terminal device relative to one or more FSAIs or frequencies specified for a non-RedCap terminal device. This may be useful, for example, in scenarios where service is only provided in RedCap CFRs (and ordinary terminal devices are directed to RedCap CFRs).

[0063] If the device is a RedCap terminal device, and the service announcement in box 201 includes information about at least one bandwidth limitation condition that is met by at least one FSAI or at least one frequency defined for the RedCap terminal device, the device may perform the following operations: First, for at least one frequency or at least one FSAI associated with at least one bandwidth limitation condition, the device may determine whether the RedCap terminal device meets at least one bandwidth limitation condition. Subsequently, during cell reselection, the device may prioritize frequencies associated with at least one FSAI or at least one frequency that meet at least one bandwidth limitation condition for the RedCap terminal device.

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

[0065] Figure 3 The illustration depicts a process for performing a notified cell reselection decision according to an embodiment. Figure 3 The process shown can be performed by a terminal device (or UE) or a portion thereof. Here, the terminal device can be... Figure 1 One of UE 100 and UE 102. The terminal device can be a RedCap terminal device or a non-RedCap terminal device. In the following text, for simplicity, the execution... Figure 3 The physical entity involved in the process is called a device.

[0066] Figure 3 The process largely corresponds to Figure 2 The process. Combined Figure 2 Any feature and definition provided shall apply Figure 3 The process should be adapted, but it needs to be flexible.

[0067] refer to Figure 3 In box 301, the device receives a service advertisement from the MBS. The service advertisement received in box 301 may correspond to a broadcast transmission. The service advertisement may be sent by the access node (e.g., gNB). The service advertisement may be initiated by the AF.

[0068] The service announcement in box 301 includes at least one frequency and at least one indication that the at least one frequency is defined for a RedCap terminal device (i.e., the service announcement corresponds to option 2 discussed in conjunction with box 201). The at least one frequency may include at least one neighboring cell frequency of the device (i.e., at least one frequency of a neighboring cell of the device's serving cell) (or consist of such frequencies). 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] Service announcements may include at least one FSAI and at least one indication that the at least one FSAI is defined for RedCap terminal devices. Service announcements 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 RedCap terminal devices.

[0070] Upon receiving the service advertisement for the MBS, in block 302, the device receives at least one FSAI-to-frequency mapping that includes the at least one frequency. Therefore, based on the at least one FSAI-to-frequency mapping, the device is able to determine at least one FSAI corresponding to the at least one frequency. The at least one FSAI-to-frequency mapping can be received from the access node. The at least one FSAI-to-frequency mapping can form part of a broadcast transmission of the access node. Receiving in block 302 may include, for example, receiving a SIB21 broadcast that includes the at least one FSAI-to-frequency mapping containing the at least one frequency. In block 302, during the reception of the at least one FSAI-to-frequency mapping, the device can be in any RRC state. The device can transition to an RRC inactive or idle state and begin receiving the MBS specified in the service advertisement.

[0071] Subsequently, in block 303, the device performs a cell reselection process based on cell measurements, service advertisements, 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 process may also employ the at least one (neighboring cell) frequency included in the service advertisement, and at least one associated indication. Besides using at least one FSAI-to-frequency mapping to perform the cell reselection process, the cell selection process can also be performed in combination with... Figure 2 To be performed as described in box 202.

[0072] Figure 4 The illustration depicts a process according to an embodiment for enabling the execution of a notified cell reselection decision. Figure 4 The process shown can be performed by an application function (AF) or a portion thereof. Here, the AF can be included... Figure 1 In the core network 110. In Figure 4 The dashed line is used to indicate optional features. In the following text, for simplicity, the execution... Figure 4 The physical entity involved in the process is called a device.

[0073] See Figure 4In block 401, the device sends a service advertisement for MBS to at least one terminal device via at least one access node (and optionally one or more core network nodes). Here, the service advertisement includes (similar to those 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 a RedCap terminal device; or at least one frequency defined for a degraded terminal device, and at least one indication indicating that the at least one frequency is defined for a RedCap terminal device. The at least one frequency may include (or consist of) one or more neighboring cell frequencies of the device. The service advertisement can be defined as described in conjunction with the embodiments above. At least one access node may simply broadcast / transmit the service advertisement without accessing its content.

[0074] In block 402, the device causes or triggers the transmission of a broadcast MBS session establishment request from the MB-SMF to at least one access node. This causing or triggering may include sending an MBS session creation (or creation) request for the MBS session to the MB-SMF via the NEF. The MBS session creation (or creation) request may include at least one FSAI and at least one indication indicating that the at least one FSAI is defined for a RedCap terminal device. 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 send the broadcast MBS session establishment request. (In conjunction with...) Figure 7 This feature is described in further detail.

[0075] In some embodiments, box 402 can be omitted. That is, in such embodiments, the transmission of the broadcast MBS session establishment request can still be performed, but not triggered (directly) by the device (e.g., AF), but by the MB-SMF itself when generating at least one FSAI for the RedCap terminal device. In these embodiments, the device can still send the MBS session creation (or creation) request for the MBS session, but does not include at least one FSAI and at least one associated indication that the at least one FSAI is defined for the RedCap terminal device. Figure 8 This feature is described in further detail.

[0076] Figure 5 The diagram illustrates the signaling 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., a gNB) can each use their respective (carrier) frequencies. f 1 , f 2and f 3 And corresponding FSAIs (FSAI2, FSAI1, and FSAI2.1) provide services for cells 1, 2, and 3. Here, FSAI2 can be an FSAI defined specifically for RedCap terminal equipment, while FSAI1 can be an FSAI not specifically defined for RedCap terminal equipment. Terminal equipment can operate in cell 1. Functions associated with the core network can be executed by communication between the core network's Application Function (AF) and the core network's Network Exposure Function (NEF) and Multicast / Broadcast Session Management Function (MB-SMF). Although Figure 5 The diagram illustrates a communication scenario where the first access node in the cell providing (initial) service to a terminal device has two adjacent access nodes. However, the following section combines... Figure 5 The described features and functions can also be applied to situations where the first access node has a single adjacent access node or more than two adjacent access nodes.

[0077] refer to Figure 5 As an initial pre-configuration step, in box 501, the access node obtains or receives configuration information from an OAM entity. The OAM entity (or entities) may reside in the core network. The configuration information includes at least one indication that the at least one FSAI is defined for a degraded end device. Here, the at least one FSAI includes at least FSAI2. In other words, in this example, the OAM entity (or entities) configuration is marked as FSAI2 for a RedCap end device. In some embodiments, box 501 may be omitted (i.e., the associated feature may be considered optional).

[0078] In some embodiments, the configuration information in block 501 may also define the bandwidth of the CFR defined for the reduced-capability terminal device.

[0079] In some embodiments, the configuration information in block 501 may optionally include a mapping between FSAI and the (operating) frequencies of one or more neighboring 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 sends a service advertisement 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 advertisement. The core network node initiating the transmission may be an AF (although the service advertisement may also be sent via one or more other core network nodes). In response to or based on the receipt of the service advertisement, the first access node may simply forward the service advertisement 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 advertisement may be received by the terminal device as a unicast; or when the terminal device operates in any RRC state, the service advertisement may be received as a broadcast transmission.

[0081] Service announcements can typically be defined as described in conjunction with previous embodiments. That is, in this example scenario, the service announcement includes two FSAIs: FSAI1 and FSAI2. Furthermore, the service announcement includes: FSAI2 is an indication for RedCap terminal equipment (and therefore usable for RedCap-based cell reselection). The service announcement may be associated with a specific TMGI (used to identify an MBS session).

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

[0083] In some embodiments, for at least one FSAI (e.g., for FSAI2) or at least one frequency, the service advertisement 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, which the FSAI or frequency defined for the degraded terminal device meets. In other words, the service advertisement and / or broadcast MBS session establishment request may include granularity related to, for example, UE type restrictions (which implicitly define at least one bandwidth limitation) or bandwidth limitations of MBS1 (e.g., a 100 MHz bandwidth limitation).

[0084] In box 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 boxes 501 and / or 506. The 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 a RedCap terminal device.

[0085] After triggering the transmission of the MBS session in box 507, the first access node sends one or more messages 508, 512 to one or more neighboring access nodes. Each of the one or more messages 508, 512 includes: at least one FSAI (FSAI2 in this example), and at least one indication defined to indicate that the at least one FSAI is for a degraded terminal device. In other words, the FSAI signaled to the neighboring access nodes(s) is supplemented by a RedCap indication (i.e., indicating that the associated FSAI is for a RedCap terminal device). In the illustrated example, the one or more neighboring access nodes include a second access node and a third access node. The content of one or more messages 508, 512 may be derived or generated based on the configuration of the first access node and / or broadcast MBS session establishment request 505.

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

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

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

[0089] In such Figure 5 In some embodiments where FSAI1 and associated non-RedCap CFR(s) are being used in a third access node, as shown in block 514, the third access node may also send a message (e.g., an Xn establish or modify message) to the first access node, which includes FSAI1 and an indication that FSAI1 is currently being used by the third access node. In block 515, this message is received by the first access node. In other embodiments (i.e., when FSAI1 is not currently being used by the third access node), elements 514 and 515 may be omitted.

[0090] It should be noted that, in cases including elements 510, 511 and / or elements 514, 515, broadcast MBS session establishment requests can also be sent from the core network to the second access node and / or the third access node (similar to...). Figure 5 (As illustrated in the diagram for the first access node). These broadcast MBS session establishment requests have been removed for the sake of simplicity in the demonstration. Figure 5 The middle part is omitted (i.e., Figure 5 The illustration primarily depicts 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 ( Figure 5 (Not depicted in the text), the exchange of information between elements 508 to 515 can occur before the transmission and reception of broadcast MBS session establishment requests (elements 505, 506). The content of the sent messages 508 / 510 / 512 / 514 can be derived or generated based on the configuration of the sending access node.

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

[0093] In message 516, the first access node sends at least a mapping (i.e., an FSAI-to-frequency mapping) between at least one FSAI defined for a degraded terminal device. This mapping may have been generated or formed by the first access node based on messages received in boxes 511 and / or 515 (e.g., messages for establishing or modifying Xn). In box 516, the terminal device receives the mapping. Message 516 may be SIB21. The transmission of message 516 may correspond to a broadcast. Generally, the information sent in message 516 may include mappings between any FSAIs received in boxes 511 and / or 515 and the frequencies associated with those FSAIs. The same FSAI(s)(s) may also be defined in a service advertisement (although the first access node itself cannot access the content of the service advertisement). Figure 5 In a specific example, the sent information (in SIB21 format) includes FSAI2 to f 2 Mapping, and FSAI1 to f 3 Mapping.

[0094] Upon receiving a mapping (e.g., SIB21), in box 518, the terminal device operates in an RRC idle or inactive state. Similar to that described in conjunction with previous embodiments, in box 519, the terminal device performs cell measurements using the first access node, the second access node, and the third access node. Based on these cell measurements and service advertisements (and mappings if the service advertisement does not contain frequencies), in box 520, the terminal device performs cell reselection. Figure 5 In the example, the terminal device can f 2 It is considered the highest priority for cell reselection because this frequency is specifically defined for RedCap end devices. Alternatively, the end device can only reselect if FSAI2 meets the end device's restrictions (i.e., the end device meets at least one bandwidth restriction condition defined in the service advertisement). f 2 This is considered the highest priority for cell reselection. The following is combined with... Figure 6A and Figure 6B Let's discuss an example of this cell re-election.

[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 may be adjusted more dynamically based on the decisions of a given access node (i.e., it is not a static configuration). In this more dynamic embodiment, the indication of FSAI to frequency mapping (e.g., used in SIB21 (message 516)) can be adapted more dynamically to enable appropriate cell reselection at the terminal device. For this purpose, in the Xn signaling that sends the configured FSAI to neighboring access nodes (elements 508 to 515), non-RedCap and / or (multiple) RedCap FSAIs are included only if they are sent in the CFR currently corresponding to a given MBS. In other words, access nodes may not necessarily share all configured FSAIs in the Xn establishment / modification messages sent to neighboring access nodes, but only the FSAI associated with the CFR currently in use.

[0096] Figure 6A and Figure 6B The diagram illustrates the process of execution. Figure 5 The two alternative signaling scenarios for cell reselection in box 520. Therefore, Figure 6A and Figure 6B The process can be Figure 5 The processes for elements 501 to 519 are executed after their completion. The RedCap terminal device (hereinafter referred to as the terminal device) Figure 6A and Figure 6BThe first access node, the second access node, the third access node, and the core network can be combined as follows: Figure 5 Defined as described.

[0097] refer to Figure 6A If also combined Figure 5 As described, during cell reselection (i.e., when searching for a cell to select), the terminal device uses frequencies defined for the RedCap terminal device. f 2 Priority is given to this. Therefore, in box 601, the terminal device initially attempts to use frequency based on the results of cell measurements. f 2 A suitable cell for cell reselection was found, but the attempt failed. Next, the terminal device attempted to use a frequency not specifically defined for RedCap terminal devices. f 3 The terminal device finds a suitable cell. That is, it knows the frequencies that are preferred but unavailable. f 2 In addition, MBS1 / MBS Session 1 will use frequency f 3 To provide. The terminal device looks up the usage frequency in box 602. f 3 In cell 3, the terminal device reselects cell 3 in box 603. In other words, the terminal device transitions from its current cell 1 to the new cell 3. In box 604, the terminal device operates in cell 3 in an RRC inactive or idle state. In other words, the terminal device begins to camp on cell 3. Finally, in message 605, the third access node sends MBS1 / MBS session 1 to the terminal device via cell 3. In box 606, the terminal device receives MBS1 / MBS session 1. In this example, it is assumed that the non-RedCap CFR of message 605 makes them compatible with RedCap terminal devices and their bandwidth limitations, and therefore the reception of MBS1 / MBS session 1 via cell 3 is successful. If this is not the case, MBS1 / MBS session 1 cannot be successfully received.

[0098] refer to Figure 6B If also combined Figure 5 and Figure 6A As described, during cell reselection (i.e., when searching for a cell to select), the terminal device uses frequencies defined for the RedCap terminal device. f 2. Priority. Therefore, in box 611, the terminal device initially attempts to use frequency based on the results of cell measurements. f 2 Find a suitable cell for cell reselection. In this example, in box 611, assume the terminal device uses a frequency... f 2Cell 2, suitable for cell reselection, was successfully found. The terminal device reselects cell 2 in block 612. 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 camping on cell 2. Finally, in message 614, the second access node sends MBS1 / MBS session 1 to the terminal device via cell 2. In block 615, the terminal device receives MBS1 / MBS session 1. Due to frequency... f 2 It is specifically defined for RedCap terminal devices, therefore, because the terminal device is a RedCap terminal device (and... Figure 6A (The opposite of the example), so there will be no compatibility.

[0099] Figure 7 and Figure 8 Two alternative core network signaling scenarios are illustrated according to embodiments for enabling cell reselection between the MB-SMF, NEF, and the AF of the core network. That is, Figure 7 and Figure 8 The diagram illustrates the process for creating an instruction for a RedCap-specific cell reselection FSAI. These processes also implement, or cause, the transmission of an MBS session establishment request from the AF to at least one access node, as discussed in conjunction with previous embodiments. Figure 7 and Figure 8 The process can be combined during execution Figures 2 to 5 , Figure 6A and Figure 6B Any step in the discussion process has been performed previously. It can be assumed that... Figure 7 and Figure 8 The AF provides at least one MBS.

[0100] exist Figure 7 In signaling scenarios, AF is configured to provide FSAI for MBS (or MBS sessions). Figure 7 In this context, it is assumed that the AF knows (e.g., based on a predefined protocol) a specific MBS for a RedCap terminal device (and optionally a non-RedCap terminal device). In other words, the AF knows the UE type for which the MBS is targeted.

[0101] In elements 701 to 703, the AF sends an 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 sends 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 a RedCap terminal device. Optionally, the first MBS session creation request may also include: one or more FSAIs not specifically for RedCap terminal devices (i.e., they do not include an indication indicating that they are defined for RedCap terminal devices). In block 702, the NEF receives the first MBS session creation request, and in message 703, sends a second MBS session creation request to the NEF. The above description of the first MBS session creation request also applies to the second MBS session creation request (i.e., the NEF can effectively 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) indication, and optionally, one or more FSAIs without such indication. The first MBS session creation request (message 701) can be an Nnef_MBS_NBSSession_Create_Request message. The second MBS session creation request (message 703) can be an Nmbsmf_MMBSSession_Create_Request message.

[0102] In some embodiments, for at least one of at least one FSAI defined for a RedCap terminal device, the first MBS session creation request and the second MBS session creation request may further include: information regarding at least one bandwidth limitation condition that the FSAI (or frequency) defined for the RedCap terminal device conforms to. 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 (which implicitly define at least one bandwidth limitation) or bandwidth limitations for MBS1 sessions (e.g., a 100MHz bandwidth limitation).

[0103] In box 704, the MB-SMF receives a second MBS session creation request from the NEF. Subsequently, the MB-SMF can direct the request to one or more access nodes (…). Figure 7In further interactions (not shown), at least one indication is used. That is, the MB-SMF may then send a broadcast MBS session establishment request for the MBS, wherein the broadcast MBS session establishment request includes: at least one FSAI, and at least one indication that the at least one FSAI is defined for the RedCap terminal device.

[0104] Following the reception in box 704, in message 705, the MB-SMF sends the first MBS session creation response back to the NEF. Upon receiving the first MBS session creation response in box 706, the NEF sends the second MBS session creation response back to the AF in message 707. In box 708, the AF receives the second MBS session creation response. The first and second MBS session creation responses are used only to confirm successful reception of the second MBS session creation request 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 The diagram illustrates the relationship with Figure 7 The core network signaling differs from alternative core network signaling scenarios. The fundamental difference between the two technical solutions lies in the fact that... Figure 8 In signaling scenarios, AF is not configured as... Figure 7 In contrast, FSAI is provided for MBS (or MBS sessions) in the same way. Instead, FSAI is created by MB-SMF.

[0107] refer to Figure 8 Similar to Figure 7In elements 801 to 803, the AF sends an 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. However, here, the FSAI or associated RedCap indication is not included in the MBS session creation request(s) because the AF is unaware of the FSAI or associated RedCap indication. Therefore, more specifically, in message 801, the AF sends a first MBS session creation request to the NEF. In block 802, the NEF receives the first MBS session creation request, and in message 803, a second MBS session creation request is sent to the NEF. Both the first and second MBS session creation requests may not 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) may be an Nmbsmf_MMBSSession_Create_Request message.

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

[0109] In message 807, the MB-SMF sends a 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) created in box 805 for the RedCap terminal device; and at least one (RedCap) indication created in box 806. When the first MBS session creation response is received in box 808, in message 809, the NEF sends a second MBS session creation response to the AF. The second MBS session creation response also includes: at least one FSAI (and optionally one or more non-RedCap-specific FSAIs) created in box 805 for the RedCap terminal device; and at least one (RedCap) indication created in box 806. In box 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 and second MBS session creation responses are used not only to confirm successful receipt of the second MBS session creation request at the MB-SMF, but also to transmit the generated FSAI(s) and indication(s) 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 Figure 7 and Figure 8 The diagram illustrates session creation without Policy Control Check (PCC), but similar decisions and processes can be made and applied during session creation with PCC. If PCC is used, then... Figure 7 and / or Figure 8 Some signaling interactions between the AF and MB-SMF discussed may be subject to further examination, and the specific names of the messages may differ, but the basic operating principles remain unchanged.

[0112] The above embodiments are based on introducing new indications for FSAIs (or frequencies) in the MBS service advertisement to indicate which FSAI / frequency is used to direct RedCap terminal devices to neighboring cell frequencies that provide MBS, based on RedCap terminal device limitations. 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 such embodiments, RedCap-specific additional information may be omitted from the service advertisement (i.e., the service advertisement is not enhanced), and instead, the corresponding information may be determined by the serving access node and transmitted to the terminal device. In these embodiments, the service advertisement may still provide information about the FSAI of general neighboring access nodes, although it does not specifically indicate which FSAI supports RedCap.

[0113] Figure 9 The illustration depicts a process for performing a notified cell reselection decision according to an embodiment. Figure 9 The illustrated process can be performed by a terminal device (or UE) or a portion thereof. Here, the terminal device can be... Figure 1 One of UE 100 and UE 102. The terminal device can be a RedCap terminal device or a non-RedCap terminal device. In the following text, for simplicity, the execution... Figure 9 The physical entity involved in the process is called a device.

[0114] refer to Figure 9 The illustrated function can be executed after receiving a service advertisement for an MBS session. This service advertisement may have defined one or more FSAIs for the MBS session, but it may not include features combined with previous embodiments (e.g., combined with...). Figure 2 The device still requires any information from the RedCap terminal device-specific information discussed in box 201. Therefore, the device can perform cell reselection in the most optimal way. Figure 9 The process begins (and during boxes 901 and 902) and operates in an inactive or idle state of RRC.

[0115] In block 901, the device receives neighboring cell frequency information. The neighboring cell frequency information includes a mapping between at least one neighboring cell frequency of at least one neighboring cell and at least one FSAI of at least one MBS session. Here and hereinafter, the neighboring cell frequency is the operating frequency of the neighboring cells of the serving cell of the device. The neighboring cell frequency information may be associated with one or more neighboring access nodes. The neighboring cell frequency information may be received from the access nodes. The neighboring 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 (therefore, at least one indication together provides information about one or more different neighboring cells). Each indication provides information on RedCap support capabilities associated with at least one FSAI or at least one MBS session, or at least information that can be used to determine said RedCap support capabilities. That is, each of the at least one indication specifies at least one of the following: • Whether the RedCap terminal device is supported for at least one FSAI or at least one MBS session. • Supported for at least one type of RedCap terminal device for at least one FSAI or at least one MBS session, or • A CFR of at least one size that can be used for at least one FSAI or at least one MBS session. Each type of information listed above with bullet points can be indicated for neighboring cells (i.e., the information can be specific to neighboring cells).

[0117] The type of RedCap terminal device can be associated with the bandwidth size 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, while a type 2 device can be a RedCap terminal device that supports bandwidth size 2. In some embodiments, if no type of RedCap terminal device is supported for at least one FSAI or at least one MBS session, the indication of at least one type of RedCap terminal device 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 CFR (or an equivalent CFR bandwidth) can be used by the device to determine whether to support general RedCap terminal equipment or a specific type of RedCap terminal equipment by comparing the bandwidth supported by (a specific type of) RedCap terminal equipment with at least one size of CFR. Therefore, all the indication types listed above enable the device to consider the RedCap terminal equipment support capabilities of neighboring cells when performing cell reselection.

[0120] At least one indication in box 902 may be associated with at least one neighboring cell (and provide information about that at least one neighboring cell). Each indication in at least one indication in box 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 terminal device with reduced capability at the neighboring cell is supported for at least one FSAI or at least one MBS session; at least one type of RedCap terminal device supported for at least one FSAI or at least one MBS session at the neighboring cell; or at least one size of CFR capable of being used for at least one FSAI or at least one MBS session at the neighboring cell.

[0121] At least one indication of block 902 may be received from an access node (e.g., from an access node that transmits neighboring 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) parts of a single message. The single message may be, for example, an SIB21 message. The SIB21 message may also include a mapping between at least one FSAI and at least one frequency defined for RedCap terminal devices according to previous service announcements.

[0123] In some embodiments, the information received in blocks 901 and 902 (e.g., in the form of SIB21 messages) corresponds to information about at least one neighboring cell frequency, and for each of the at least one neighboring cell frequencies, there corresponds to one or more datasets. The at least one neighboring cell frequency may be associated with 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 includes the FSAI for an MBS session, and the at least one indication in block 902 that explicitly or implicitly describes support for RedCap terminal devices.

[0124] In block 903, the device performs a cell reselection process based on cell measurements, neighboring cell frequency information, and at least one indication.

[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 providing neighboring cells (i.e., adjacent to the device's currently serving cell). Cell measurements may include measurements of at least one of, for example: 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 neighboring cells). Cell measurements may include any cell measurements performed in RRC inactive or idle states, as defined in 3GPP TS 38.306 and / or TS 38.304.

[0126] In some embodiments, the apparatus is a RedCap terminal device, and at least one indication in block 902 specifies a RedCap terminal device supporting at least one FSAI, without indicating at least one size of CFR for at least one FSAI and at least one type of RedCap terminal device supporting at least one FSAI (i.e., only basic information about RedCap support is provided). In such embodiments, during the cell reselection process in block 903, the apparatus may prioritize any neighboring cell frequency associated with at least one indication specifying a terminal device supporting degraded capability for at least one FSAI or at least one MBS session. In other words, any neighboring cell frequency associated with at least one FSAI or at least one MBS session of a terminal device indicated to support degraded capability may be prioritized. Alternatively, during the cell reselection process in block 903, the apparatus may prioritize any neighboring cell frequency associated with at least one indication specifying a terminal device supporting degraded capability for at least one FSAI or at least one MBS session only if the terminal device's BWP limitation (or other limitation) allows the terminal device to receive MBS in the associated neighboring cells.

[0127] In some embodiments, the device is a RedCap terminal device, and at least one indication in block 902 specifies a CFR of at least one size for at least one FSAI or at least one MBS session. In such embodiments, during cell reselection in block 903, the device may prioritize at least one neighboring cell frequency (or any neighboring cell frequency) associated with the size of the CFR 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 specifies a terminal device with at least one type of reduced capability supported for at least one FSAI or at least one MBS session. In such an embodiment, during the cell reselection process in block 903, the device may prioritize at least one neighboring cell frequency (or any neighboring cell frequency) associated with the type of RedCap terminal device corresponding to the RedCap terminal device (i.e., the device).

[0129] In some embodiments, both of the prioritization features discussed in the first two paragraphs can 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 such embodiments, during the cell reselection process of block 903, the device may prioritize at least one neighboring cell frequency (or any neighboring cell frequency) that does not support a RedCap terminal device. Thus, any neighboring cell frequencies defined for a RedCap terminal device can still be used by the RedCap terminal device (for RedCap terminal devices, the selection of neighboring cell frequencies is more limited than for non-RedCap terminal devices). Whether a given neighboring cell frequency supports a RedCap terminal device can be determined based on at least one indication and neighboring cell frequency information. Alternatively, during the cell reselection process of block 903, the device (for a non-RedCap terminal device) may avoid or ignore any neighboring cell frequencies that support a RedCap terminal device.

[0131] Figure 10 A process according to an embodiment is shown for enabling the execution of a notified cell reselection decision. Figure 10 The illustrated process can be performed by the access node or a portion thereof. The access node can be, for example... Figure 1 Access node 104. For simplicity, the following text will describe the execution... Figure 10 The physical entity involved in the process is called a device.

[0132] refer 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 equipment support capabilities of the at least one adjacent access node. Specifically, the at least one indication specifies at least one of the following: • At at least one of the adjacent access nodes, is the degraded terminal device supported for at least one FSAI or at least one MBS session? • At least one type of RedCap terminal device supported at a neighboring access node (or in a neighboring cell provided by a neighboring access node) for at least one FSAI or at least one MBS session. • At least one size of CFR used at an adjacent access node for at least one FSAI or at least one MBS session, or • At least one type of CFR currently being used by a neighboring access node for at least one FSAI or at least one MBS session.

[0133] Here, a neighboring 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 neighboring access node for at least one FSAI or at least one MBS session can have been determined based on the available CFRs in the associated neighboring cells.

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

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

[0136] In block 1002, the device sends neighboring cell frequency information to the terminal device. This neighboring cell frequency information includes a mapping between at least one neighboring cell frequency and at least one FSAI of at least one MBS session. Here, the neighboring cell frequency is the operating frequency of the neighboring cells of the serving cell provided by the device. Typically, the neighboring cell frequency information sent in block 1002 can be combined as described above. Figure 9 The corresponding receiving step in block 901 is defined as described. The transmission in block 1002 can correspond to a broadcast transmission.

[0137] In block 1003, the device sends at least one indication to the terminal device. For at least one neighboring cell provided by at least one neighboring access node, the at least one indication specifies at least one of the following: • Whether the reduced-capacity terminal device is supported for at least one FSAI or at least one MBS session. • A terminal device that is supported for at least one type of reduced capability for at least one FSAI or at least one MBS session, or • A CFR of at least one size that can be used for at least one FSAI or at least one MBS session.

[0138] The device can derive or generate at least one instruction in block 1003 based on at least one instruction in block 1001. Typically, the at least one instruction sent in block 1003 can be combined as described above. Figure 9 The corresponding receiving step in block 902 is defined as described. The transmission in block 1003 can correspond to a broadcast transmission.

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

[0140] Figure 11 The illustration shows another process according to an embodiment for enabling the execution of a notified cell reselection decision. Figure 11 The process described can be performed by the access node or a portion thereof. The access node can be, for example... Figure 1 Access node 104. For simplicity, the following text will describe the execution... Figure 4 The physical entity involved in the process is called a device.

[0141] In block 1101, the device receives at least one TMGI associated with at least one MBS session in progress at each of one or more adjacent access nodes, and for each of the at least one TMGI, receives at least one indication related to the RedCap terminal device support capability of the TMGI of the given adjacent access node. The at least one indication specifies at least one of the following: • At adjacent access nodes, are RedCap terminal devices supported for TMGI? • At adjacent access nodes, at least one type of RedCap terminal device is supported for TMGI, or • At adjacent access nodes, at least one size of CFR is used for TMGI.

[0142] In block 1102, the device sends neighboring cell frequency information to the terminal device. This neighboring cell frequency information includes a mapping between at least one neighboring cell frequency and at least one FSAI used for at least one MBS session. Here, the neighboring cell frequency is the operating frequency of a neighboring cell of the serving cell provided by the device. The neighboring cell frequency information can be derived or generated 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.

[0143] In block 1103, the device sends at least one indication to the terminal device. For the purpose of determining a neighboring cell (or at least one neighboring cell), the at least one indication specifies at least one of the following: • Whether the reduced-capacity terminal device is supported for at least one FSAI or at least one MBS session. • A terminal device that is supported for at least one type of reduced capability for at least one FSAI or at least one MBS session, or • A public frequency resource (CFR) of at least one size that can be used for at least one FSAI or at least one MBS session.

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

[0145] Figure 12 The diagram illustrates the signaling 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., a gNB) can each use their respective (carrier) frequencies. f 1 , f 2 and f 3 And corresponding FSAIs (FSAI2, FSAI1, and FSAI2.1) provide services for cells 1, 2, and 3. Here, FSAI2 can be an FSAI defined specifically for RedCap terminal equipment, while FSAI1 can be an FSAI not specifically defined for RedCap terminal equipment. Terminal equipment can operate in cell 1. Core network-related functions can be executed through communication between the core network's Application Function (AF), Network Exposure Function (NEF), and Multicast / Broadcast Session Management Function (MB-SMF). Although Figure 12This illustrates a communication scenario where the first access node in the (initial) serving cell for a terminal device has two adjacent access nodes, but the following section combines... Figure 12 The described features and functions can also be applied to situations where the first access node has a single adjacent access node or more than two adjacent access nodes.

[0146] refer 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 sends a service advertisement 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 advertisement. The core network node initiating the transmission may be an AF (although the service advertisement may also be sent via one or more other core network nodes). In response to or based on the receipt of the service advertisement, the first access node may simply forward the service advertisement 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 advertisement may be received by the terminal device as a unicast; or when the terminal device operates in any RRC state, the service advertisement may be received as a broadcast transmission.

[0147] In this example scenario, the service advertisement includes two FSAIs: FSAI1 and FSAI2. Figure 5 In contrast, service announcements do not include any indication that FSAI2 is specific to RedCap end devices. In other words, service announcements can be "regular" service announcements without additional features. Service announcements can be associated with a specific TMGI (used to identify MBS sessions).

[0148] In message 1204, a core network entity (or node or function) sends a broadcast MBS session establishment request to a first access node for a session of MBS1 (hereinafter referred to as MBS session 1). The broadcast MBS session establishment request may be sent to the access node, for example, by an AF via zero or more other core network nodes. The broadcast MBS session establishment request includes one or more FSAIs. In this particular example, the broadcast MBS session establishment request includes at least FSAI1 and FSAI2. In this embodiment (and, for example...) Figure 5 (In contrast to the embodiments), at this time the RedCap terminal device is unaware of its ability to support one or more FSAIs (e.g., FSAI1 and FSAI2). In block 1205, the first access node receives a broadcast MBS session establishment request for MBS session 1.

[0149] In box 1206, the first access node triggers or initiates a transmission of the MBS session (i.e., MBS session 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 session in box 1206, the first access node sends one or more messages 1207, 1211 to one or more adjacent access nodes (in this example, two messages 1207, 1211 are sent 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 defined as indicating that at least one FSAI is for a degraded terminal device. In other words, the FSAI(s) sent to the adjacent access nodes(s) are supplemented by a RedCap indication (i.e., indicating that the associated FSAI is 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 session establishment request 1204.

[0151] One or more messages 1207, 1211 may be, or specifically include, one or more Xn establishment and / or modification messages. In other words, when establishing a new Xn connection (Xn establishment) with another access node, or establishing a new Xn connection (Xn modification) for an existing Xn connection, the first access node sends 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 sends a broadcast establishment and transmission trigger FSAI information to neighboring access nodes). It is noteworthy that if the first access node does not initiate transmission in the RedCap CFR, it will not send FSAI2 to any neighboring access nodes. Therefore, any neighboring access node can determine that (multiple) RedCap CFRs are in use based on the received FSAI2.

[0152] In this embodiment, one or more messages 1207, 1211 may include combinations Figure 10 Box 1001 and / or Figure 11 The information described in 1101. In this example, since the first access node is currently using RedCap CFR with FSAI2 and MBS session 1, each of one or more messages 1207, 1211 may include at least one indication that specifies at least one of the following: • At the first access node, RedCap terminal devices are supported for use in FSAI2 or MBS session 1. • At least one type of RedCap terminal device supported for FSAI2 or MBS session 1 at the first access node (or in a neighboring cell provided by the first access node). • At least one size of CFR used at the first access node for FSAI2 or MBS session 1 • At least one type of CFR currently being used by the first access node in either FSAI 2 or MBS session 1.

[0153] In some embodiments, the type of CFR in use may have another granularity; for example, it may (implicitly or explicitly) indicate compliance with UE type restrictions or compliance with 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 frequency bands supported by the UE. In other words, one or more messages 1207, 1211 may include bandwidth limiting conditions as discussed in conjunction with the embodiments above.

[0154] In block 1208, the second access node receives a message (e.g., an establishment or modification message for Xn) from the first access node, which includes FSAI2 and at least one indication. Similarly, in block 1212, the third access node receives a message (e.g., an establishment or modification message for Xn) from the first access node, which includes FSAI2 and at least one indication. In corresponding messages 1209 and 1213, the second and third access nodes send response messages (e.g., an establishment or modification message for Xn) back to the first access node. In blocks 1210 and 1214, response messages 1209 and 1213 are received by the first access node.

[0155] exist Figure 12 In the example, assume 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., an Xn establish or modify message) may include at least one indication similar to messages 1207 and 1211, indicating at least one of the following: • At the second access node, RedCap terminal devices are supported for use in FSAI2 or MBS session 1. • At least one type of RedCap terminal device supported for FSAI2 or MBS session 1 at the second access node (or in a neighboring cell provided by the first access node). • At the second access node, at least one size of CFR was used for FSAI2 or MBS session 1. • At least one type of CFR currently being used by the second access node, either FSAI2 or MBS session 1.

[0156] In this example, since the third access node is currently using a non-RedCap CFR with FSAI1 and MBS session 2, response message 1213 (e.g., for an Xn establish or modify message) may include at least one indication that specifies 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). • At the third access node, no type of RedCap terminal device is supported for use in FSAI1 or MBS session 2. • At the third access node, at least one size of CFR is used for FSAI1 or MBS session 2. • At least one type of CFR currently being used by the third access node for FSAI2 or MBS session 2.

[0157] In some embodiments, the information listed in the preceding paragraph may be omitted from message 1213. Message 1213 may be a regular Xn establishment 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 limiting conditions as discussed in conjunction with the above embodiments.

[0159] Based on the information received in messages(s) 1209 and / or 1213, in message 1215, the first access node sends an SIB21 message for cell reselection to at least one terminal device via at least one access node. Here, the SIB21 message includes neighboring cell frequency information related to the cell provided by the second and third access nodes, and (implicitly or explicitly) at least one indication of possible RedCap terminal device support associated with the FSAI or MBS session of the second and third access nodes. The at least one terminal device includes at least... Figure 12 The diagram shows a RedCap terminal device. The transmission of message 1215 can correspond to a broadcast. Transmissions (or broadcasts) can be performed periodically or periodically. Generally, the transmission of SIB21 message 1215 can correspond to the transmissions discussed above. Figure 10 The combination of frames 1002 and 1003. Neighboring cell frequency information and at least one indicator can be combined as follows. Figure 10 Defined as described.

[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, receiving a broadcast MBS session (MBS session 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 using the first access node, the second access node, and the third access node. Based on these cell measurements and the SIB21 message (and optional service advertisements), in block 1219, the terminal device performs cell reselection. Figure 12 In the example, with Figure 5 Similar to the example, the terminal device can f 2 It is considered the highest priority for cell reselection because this frequency is specifically defined for RedCap terminal equipment. Alternatively, the terminal equipment can only reselect if FSAI2 meets the terminal equipment's restrictions (i.e., the terminal equipment meets at least one bandwidth restriction condition defined in messages (multiple) 1209 and / or 1213). f 2 It is considered the highest priority for cell reselection.

[0161] The above combination Figure 6A and Figure 6B The examples of cell reselection discussed here can also be applied (i.e., combined with...) Figure 12 (Box 1219), but it needs to be modified. In other words, Figure 6A and Figure 6B Any process in can be in Figure 12 Elements 1201 to 1218 are executed after completion.

[0162] In some simplified embodiments, the access node is configured via OAM with information that a specific FSAI(s) is associated with a RedCap terminal device (and optionally with suitable bandwidth) (i.e., they support RedCap terminal devices). Based on this configuration, when signaling is received to initiate an MBS session including any of those specific FSAIs, the access node will transmit the service (i.e., MBS) in the RedCap CFR and using bandwidth suitable for the RedCap UE; additionally, it may also transmit in non-RedCap CFRs.

[0163] The embodiments discussed above provide at least some of the following technical advantages. These embodiments allow different cell reselection priorities to be performed by RedCap and non-RedCap terminal devices, which in turn results in appropriate (i.e., correct or suitable) broadcast reception by terminal devices in RRC inactive or idle states. These embodiments enable access nodes to make informed decisions about which CFR(s) ...

[0164] The above relies on Figures 2 to 5 , Figure 6A , Figure 6B ,as well as Figures 7 to 12 The described boxes, related functions, and information exchanges 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 between or within them, and other information may be sent and / or other rules may be applied. Some boxes, or portions of boxes, or one or more pieces of information within a box may be omitted, or replaced by the corresponding box, or portions of boxes, or one or more pieces of information.

[0165] Figure 13 An apparatus 1301 according to some embodiments is provided. Specifically, Figure 13 The device 1301 can be illustrated as a terminal device, access node, or core network node (e.g., AF, NEF, or MB-SMF). Alternatively, Figure 13 The apparatus 1301 may be illustrated 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 program code (software), wherein at least one memory 1340 and the computer program code (software) are configured, together with at least one processor, to cause device 1301 to perform any of the exemplary functions of the aforementioned devices (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, wherein 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] refer to Figure 13 One or more communication control circuit systems 1320 of device 1301 are configured to use one or more separate circuit systems, by means of Figures 2 to 5 , Figure 6A , Figure 6B and Figures 7 to 12 Any one of them can be used to perform the above function. Specifically, in Figure 5 , Figure 6A , Figure 6B , Figure 7 , Figure 8 and Figure 12 In this case, one or more communication control circuitry systems 1320 of device 1301 are configured to perform the functions of at least one of the devices illustrated. Depending on the embodiment, it is also possible to implement the functions using specific integrated circuits, such as ASICs (Application-Specific Integrated Circuits), or other components and devices.

[0169] refer to Figure 13The device 1301 may also 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 the device 1301 is a terminal device or part thereof, the one or more communication interfaces 1310 may include, for example, communication interfaces providing connectivity between the device 1301 and one or more access nodes, for providing connectivity to a core network (including, for example, MB-SMF, NEF, and AF). If the device 1301 is an access node or part thereof, the one or more communication interfaces 1310 may include, for example, communication interfaces between the device 1301 and one or more terminal devices, and communication interfaces between the device 1301 and one or more core network nodes (including, for example, MB-SMF, NEF, and AF). The one or more communication interfaces 1310 may include standard, well-known components, such as amplifiers, filters, frequency converters, (de)modulators, and encoder / decoder circuitry controlled by corresponding control units, and one or more antennas. The device 1301 may also include one or more user interfaces.

[0170] refer to Figure 13 The 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 herein, the term “circuit system” may refer to one or more or all of the following: (a) a hardware-only implementation, such as an implementation of an analog and / or digital-only circuit system; and (b) a combination of hardware circuitry and software (and / or firmware), such as (where applicable): (i) a combination of (multiple) analog and / or digital hardware circuitry with software / firmware; and (ii) any portion of (multiple) hardware processors having software, including (multiple) digital signal processors, software, and (multiple) memories, which work together to enable a device (such as a terminal device or access node) to perform various functions; and (c) (multiple) hardware circuitry and (multiple) processors, such as (multiple) microprocessors, or portions thereof, which require software (e.g., firmware) to operate, but may be absent when the software is not required to operate. This definition of “circuit system” applies to all uses of the term herein (including in any claim). As another example, the term "circuit system" as used in this application also covers implementations of hardware circuitry or processors (or processors) alone, or a portion thereof and its (or their) accompanying software and / or firmware.

[0172] In one embodiment, combined Figures 2 to 5, Figure 6A , Figure 6B and Figures 7 to 12 At least some of the processes described can be performed by means including corresponding components for performing at least some of the processes described. Some example components for performing these processes 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, a memory, RAM, ROM, software, firmware, a display, a user interface, a display circuit system, a user interface circuit system, a user interface software, display software, a circuit, a filter (low-pass, high-pass, band-pass, and / or band-stop), a sensor, a circuit system, an inverter, a capacitor, an inductor, a resistor, an operational amplifier, a diode, and a transistor. In one embodiment, the at least one processor, memory, and computer program code form a processing component or include one or more portions of computer program code for performing according to Figures 2 to 5 , Figure 6A , Figure 6B and Figures 7 to 12 The embodiments thereof are used to perform one or more operations. In some embodiments, at least some of the processes in the process may be implemented using discrete components.

[0173] According to an embodiment, an apparatus (e.g., a terminal device, or a UE, or a portion thereof) is provided, the apparatus including components for performing the following: Receive service announcements from the Multicast Broadcast Service (MBS), which include: - At least one Frequency Selection Area Identifier (FSAI), and at least one indication defined for a terminal device with reduced capabilities, or - At least one frequency, and at least one indication defined to indicate that the at least one frequency is for a terminal device with reduced capabilities; This component is also configured to perform a cell reselection process based on cell measurements and service announcements.

[0174] According to an embodiment, an apparatus (e.g., AF, or a portion thereof) is provided, the apparatus including components for performing the following operations: Receive service announcements from the Multicast Broadcast Service (MBS), which include: - At least one Frequency Selection Area Identifier (FSAI), and at least one indication defined for a terminal device with reduced capabilities, or - At least one frequency, and at least one indication defined to indicate that the at least one frequency is for a terminal device with reduced capabilities; This component is also configured to perform a cell reselection process based on cell measurements and service announcements.

[0175] According to an embodiment, an apparatus (e.g., an access node, or a portion thereof) is provided, the apparatus including components for performing the following: The core network function receives a broadcast MBS session establishment request for a multicast broadcast service MBS session, wherein the broadcast MBS session establishment request includes: at least one Frequency Selection Area Identifier (FSAI), and at least one indication that the at least one FSAI is defined for a degraded terminal device; or The component receives an MBS session establishment request broadcast from the core network and configuration information from the operation, supervision, and management OAM entities, wherein the broadcast MBS session establishment request includes at least one FSAI, and the configuration information includes at least one indication defined for a degraded terminal device; and wherein the component is further configured to perform: Based on at least one FSAI and at least one indication, the transmission of an MBS session within a reduced-capacity public frequency resource (CFR) is triggered.

[0176] According to an embodiment, an apparatus (e.g., MB-SMF, or a portion thereof) is provided, the apparatus including components for performing the following: Receive MBS session creation requests for multicast broadcast service (MBS) sessions; In response to or based on the reception, at least one Frequency Selection Area Identifier (FSAI) defined for a degraded terminal device is generated for the MBS session, and at least one indication indicating that the at least one FSAI is defined for a degraded terminal device; and A broadcast MBS session establishment request is sent to at least one access node, wherein the broadcast MBS session establishment request includes at least one FSAI and at least one indication.

[0177] According to an embodiment, an apparatus (e.g., a terminal device, or a portion thereof) is provided, the apparatus including components for performing the following: Receive neighboring cell frequency information, which includes: 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 the neighboring cell of the serving cell of the device. Receive at least one indication for at least one neighboring cell, the indication specifying at least one of the following: • Whether the reduced-capacity terminal device is supported for at least one FSAI or at least one MBS session. • A terminal device that is supported for at least one type of reduced capability for at least one FSAI or at least one MBS session, or • At least one size of public frequency resource CFR capable of being used for at least one FSAI or at least one MBS session; and The cell reselection process is performed based on cell measurements, neighboring cell frequency information, and at least one indication.

[0178] According to an embodiment, an apparatus (e.g., an access node or a portion thereof) is provided, the apparatus including components for performing the following: Receive at least one indication from at least one neighboring access node, the at least one indication specifying at least one of the following: • At at least one of the adjacent access nodes, is the degraded terminal device supported for at least one Frequency Selection Area Identifier (FSAI) or at least one Multicast Broadcast Service (MBS) session? • Terminal devices that are supported at adjacent access nodes for at least one type of reduced capability for at least one FSAI or at least one MBS session. • At least one size of common frequency resource CFR used for at least one FSAI or at least one MBS session at adjacent access nodes. • The CFR of at least one type currently being used by a neighboring access node for at least one FSAI or at least one MBS session; The device sends neighboring cell frequency information to the terminal equipment. This neighboring cell frequency information includes: a mapping between at least one neighboring cell frequency and at least one FSAI used for at least one MBS session, wherein the neighboring cell frequency is the operating frequency of a neighboring cell of the serving cell provided by the device; and Send at least one indication to the terminal device, for at least one neighboring cell provided by at least one neighboring access node, the at least one indication specifying at least one of the following: • Whether the reduced-capacity terminal device is supported for at least one FSAI or at least one MBS session. • A terminal device that is supported for at least one type of reduced capability for at least one FSAI or at least one MBS session, or • A CFR of at least one size that can be used for at least one FSAI or at least one MBS session.

[0179] According to an embodiment, an apparatus (e.g., an access node, or a portion thereof) is provided, the apparatus including components for performing the following: Receive at least one Temporary Mobile Group Identifier (TMGI) associated with at least one Multicast Broadcast Service (MBS) session in progress at each of one or more adjacent access nodes, and for each of the at least one TMGI, receive at least one indication indicating at least one of the following: • At adjacent access nodes, are de-capable terminal devices supported for TMGI? • At adjacent access nodes, terminal devices supported for at least one type of reduced capability for TMGI, or • At adjacent access nodes, at least one size of CFR is used for TMGI; The device sends neighboring cell frequency information to a terminal device. This neighboring cell frequency information includes a mapping between at least one neighboring cell frequency and at least one FSAI used for at least one MBS session. The neighboring cell frequency is the operating frequency of a neighboring cell of the serving cell provided by the device, and the neighboring 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. Sending at least one indication of at least one neighboring cell provided by one or more neighboring access nodes to the terminal device, wherein, for the neighboring cell (or for at least one neighboring cell), the at least one indication specifies at least one of the following: • Whether the reduced-capacity terminal device is supported for at least one FSAI or at least one MBS session. • A terminal device that is supported for at least one type of reduced capability for at least one FSAI or at least one MBS session, or • A public frequency resource (CFR) of at least one size that can be used for at least one FSAI or at least one MBS session.

[0180] The embodiments described can also be executed, wholly or at least partially, in the form of a computer process defined by a computer program or parts thereof. Figures 2 to 5 , Figure 6A , Figure 6B and Figures 7 to 12Embodiments of the described methods can be performed by executing at least a portion of a computer program including corresponding instructions. The computer program may be provided as a computer-readable medium including program instructions stored thereon, or as a non-transitory computer-readable medium including program instructions stored thereon. The computer program may be in the form of source code, object code, or some intermediate form, and it may be stored in 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 or processor-readable computer program distribution medium. 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 that, when executed by a computing device, cause the computing device to perform the following: Receive service announcements from the Multicast Broadcast Service (MBS), which include: - At least one Frequency Selection Area Identifier (FSAI), and at least one indication defined for a terminal device with reduced capabilities, or - At least one frequency, and at least one indication defined to indicate that the at least one frequency is for a terminal device with reduced capabilities; When executed by a computing device, this instruction also causes the computing device to perform a cell reselection process based on cell measurements and service announcements.

[0182] According to an embodiment, a non-transitory computer-readable medium is provided having instructions stored thereon that, when executed by a computing device, cause the computing device to perform: A service announcement for the Multicast Broadcast Service (MBS) is sent to at least one terminal device via at least one access node, wherein the service announcement includes: - At least one Frequency Selection Area Identifier (FSAI), and at least one indication defined for a terminal device with reduced capabilities, or - At least one frequency defined for a terminal device with reduced capabilities, and at least one indication that the at least one frequency is defined for a terminal device with reduced capabilities.

[0183] According to an embodiment, a non-transitory computer-readable medium is provided having instructions stored thereon that, when executed by a computing device, cause the computing device to perform the following: The core network function receives a broadcast MBS session establishment request for a multicast broadcast service MBS session, wherein the broadcast MBS session establishment request includes: at least one Frequency Selection Area Identifier (FSAI), and at least one indication that the at least one FSAI is defined for a degraded terminal device; or The system receives an MBS session establishment request broadcast from the core network and configuration information from the operation, supervision, and management OAM entities, wherein the broadcast MBS session establishment request includes at least one FSAI, and the configuration information includes at least one indication defined for a degraded terminal device; and wherein, when executed by the computing device, the instruction further causes the computing device to perform: The transmission of an MBS session within a reduced-capacity public frequency resource (CFR) is triggered based on at least one FSAI and at least one indication.

[0184] According to an embodiment, a non-transitory computer-readable medium is provided having instructions stored thereon that, when executed by a computing device, cause the computing device to perform: Receive MBS session creation requests for multicast broadcast service (MBS) sessions; In response to or based on the reception, at least one Frequency Selection Area Identifier (FSAI) defined for a degraded terminal device is generated for the MBS session, and at least one indication indicating that the at least one FSAI is defined for a degraded terminal device; and A broadcast MBS session establishment request is sent to at least one access node, wherein the broadcast MBS session establishment request includes at least one FSAI and at least one indication.

[0185] As used herein, the term “non-transient” refers to the limitations of the medium itself (i.e., tangible, not signal-based), rather than limitations on the persistence of data storage (e.g., RAM vs. ROM).

[0186] According to an embodiment, a method is provided, comprising: Receive service announcements from the Multicast Broadcast Service (MBS), which include: - At least one Frequency Selection Area Identifier (FSAI), and at least one indication defined for a terminal device with reduced capabilities, or - At least one frequency, and at least one indication defined to indicate that the at least one frequency is for a terminal device with reduced capabilities; The method also includes: performing a cell reselection process based on cell measurements and service announcements.

[0187] According to an embodiment, a method is provided, comprising: A service announcement for the Multicast Broadcast Service (MBS) is sent to at least one terminal device via at least one access node, wherein the service announcement includes: - At least one Frequency Selection Area Identifier (FSAI), and at least one indication defined for a terminal device with reduced capabilities, or - At least one frequency defined for a terminal device with reduced capabilities, and at least one indication that the at least one frequency is defined for a terminal device with reduced capabilities.

[0188] According to an embodiment, a method is provided, comprising: The core network function receives a broadcast MBS session establishment request for a multicast broadcast service MBS session, wherein the broadcast MBS session establishment request includes: at least one Frequency Selection Area Identifier (FSAI), and at least one indication that the at least one FSAI is defined for a degraded terminal device; or The method involves receiving a broadcast MBS session establishment request from the core network and receiving configuration information from the operation, supervision, and management OAM entities, wherein the broadcast MBS session establishment request includes at least one FSAI, and the configuration information includes at least one indication defined for a degraded terminal device; and wherein the method further includes: The transmission of an MBS session within a reduced-capacity public frequency resource (CFR) is triggered based on at least one FSAI and at least one indication.

[0189] According to an embodiment, a method is provided, comprising: Receive MBS session creation requests for multicast broadcast service (MBS) sessions; In response to or based on the reception, at least one Frequency Selection Area Identifier (FSAI) defined for a degraded terminal device is generated for the MBS session, and at least one indication indicating that the at least one FSAI is defined for a degraded terminal device; and A broadcast MBS session establishment request is sent to at least one access node, wherein the broadcast MBS session establishment request includes at least one FSAI and at least one indication.

[0190] Example 1: An apparatus comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least: receive a service announcement of a multicast broadcast service (MBS), wherein the service announcement includes at least one of the following:

[0191] - At least one Frequency Selection Area Identifier (FSAI) and at least one indication defined to indicate that the at least one FSAI is for a terminal device with reduced capabilities, or

[0192] - At least one frequency and at least one indication that the at least one frequency is defined for a terminal device with reduced capabilities;

[0193] The at least one memory and instructions are configured, together with at least one processor, to cause the device to also perform: a cell reselection process based on cell measurements and service announcements.

[0194] Example 2. The apparatus according to Example 1, wherein the apparatus is a degraded terminal device; and wherein performing a cell reselection process based on a service advertisement includes: during the cell reselection process, prioritizing frequencies associated with at least one FSAI or at least one frequency defined for a degraded terminal device.

[0195] Example 3. The apparatus according to Example 2, wherein the service announcement further includes one or more FSAIs or one or more frequencies without any indication that the one or more FSAIs or one or more frequencies are defined for a degraded terminal device; and wherein prioritization includes: during a cell reselection process, prioritizing frequencies associated with at least one FSAI or at least one frequency defined for a degraded terminal device, at least relative to frequencies associated with the one or more FSAIs or one or more frequencies not indicated as being defined for a degraded terminal device.

[0196] Example 4. The apparatus according to Example 1, wherein the apparatus is a non-degraded terminal device, the service announcement further includes one or more FSAIs or one or more frequencies without any indication that the one or more FSAIs or one or more frequencies are defined for a degraded terminal device; and wherein performing a cell reselection process includes: during the cell reselection process, prioritizing frequencies associated with one or more FSAIs or one or more frequencies not defined for a degraded terminal device relative to frequencies associated with at least one FSAI or at least one frequency defined for a degraded terminal device.

[0197] Example 5. The apparatus according to Example 1, wherein for at least one FSAI or at least one frequency, the service notification further includes information about at least one bandwidth limitation condition, which is indicated to be defined for a terminal device with reduced capabilities.

[0198] Example 6. The apparatus according to Example 5, wherein at least one bandwidth limiting condition includes a condition for bandwidth size and / or a condition for the type of terminal device with reduced capabilities.

[0199] Example 7. An apparatus according to Example 5 or 6, wherein the apparatus is a degraded terminal device; and wherein performing a cell reselection process includes: determining whether the degraded terminal device satisfies at least one bandwidth limitation condition for at least one frequency or at least one FSAI associated with at least one bandwidth limitation condition; and during the cell reselection process, prioritizing the frequency associated with at least one FSAI or at least one frequency for which the degraded terminal device satisfies at least one bandwidth limitation condition.

[0200] Example 8. The apparatus according to Example 7, wherein the service advertisement includes one or more FSAIs or one or more frequencies without any indication that the one or more FSAIs or one or more frequencies are defined for a degraded terminal device, and prioritization includes: during cell reselection, prioritizing at least one FSAI or at least one frequency associated with a degraded terminal device that satisfies at least one bandwidth limitation condition, at least relative to frequencies associated with one or more FSAIs or one or more frequencies not indicated as being defined for a degraded terminal device.

[0201] Example 9. An apparatus according to any of the foregoing examples, wherein the service advertisement includes at least one FSAI and at least one instruction defined for a terminal device with reduced capability, and at least one memory and instructions are configured together with at least one processor to cause the apparatus to perform: receiving a mapping between at least one FSAI defined in the service advertisement and at least one frequency; and also performing a cell reselection process based on the mapping.

[0202] Example 10. An apparatus according to any of the foregoing examples, wherein at least one memory and instructions are configured, together with at least one processor, to cause the apparatus to perform: operation in a Radio Resource Control (RRC) idle or inactive state during the execution of a cell reselection procedure.

[0203] Example 11: An apparatus comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least: send a service announcement of a multicast broadcast service (MBS) to at least one terminal device via at least one access node, wherein the service announcement includes at least one of the following:

[0204] - At least one Frequency Selection Area Identifier (FSAI) and at least one indication defined to indicate that the at least one FSAI is for a terminal device with reduced capabilities, or

[0205] - At least one frequency defined for a terminal device with reduced capabilities and at least one indication that at least one frequency is defined for a terminal device with reduced capabilities.

[0206] Example 12. The apparatus according to Example 11, wherein the service notification further includes information regarding at least one bandwidth limitation for at least one FSAI or at least one frequency, wherein the FSAI or frequency defined for the degraded terminal device conforms to the at least one bandwidth limitation.

[0207] Example 13. The apparatus according to Example 11 or 12, wherein at least one memory and instructions are configured together with at least one processor to cause the apparatus to perform: triggering the sending of a broadcast MBS session establishment request to at least one access node via a multicast broadcast session management function MB-SMF, wherein the broadcast MBS session establishment request includes at least one FSAI and at least one indication that the at least one FSAI is defined for a degraded terminal device.

[0208] Example 14: An apparatus comprising: at least one processor; and at least one memory, the at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least: receive a broadcast MBS session establishment request for a multicast broadcast service MBS session from a core network function, 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 degraded terminal device; or receive a broadcast MBS session establishment request for an MBS session from a core network and receive configuration information from an Operation, Management and Maintenance (OAM) entity, wherein the broadcast MBS session establishment request includes at least one FSAI and the configuration information includes at least one indication indicating that the at least one FSAI is defined for a degraded terminal device; and wherein the at least one memory and the instructions are configured, together with the at least one processor, to cause the apparatus to further: trigger the transmission of an MBS session within a degraded public frequency resource (CFR) based on the at least one FSAI and the at least one indication.

[0209] Example 15. The apparatus according to Example 14, wherein at least one memory and instructions are configured, together with at least one processor, to cause the apparatus to: forward a service advertisement to one or more terminal devices in response to or based on receiving a service advertisement of MBS from a core network function, wherein the service advertisement includes at least one of the following:

[0210] - At least one FSAI and at least one indication defined as indicating that the at least one FSAI is for a terminal device with reduced capabilities, or

[0211] - At least one frequency defined for a terminal device with reduced capabilities and at least one indication that at least one frequency is defined for a terminal device with reduced capabilities.

[0212] Example 16. An apparatus according to any one of Examples 14 to 15, wherein at least one memory and instructions are configured together with at least one processor to cause the apparatus to perform: after triggering the transmission of an MBS session, sending one or more messages to one or more adjacent access nodes, wherein each of the one or more messages includes at least one FSAI and at least one indication that the at least one FSAI is defined for a degraded terminal device.

[0213] Example 17. The apparatus according to Example 16, wherein one or more messages are Xn establish or modify messages.

[0214] Example 18. An apparatus according to any one of Examples 14 to 17, wherein at least one memory and instructions are configured together with at least one processor to cause the apparatus to perform: transmitting a mapping between at least one FSAI and at least one frequency as defined in a service announcement.

[0215] Example 19. An apparatus according to any one of Examples 14 to 18, wherein the configuration information further defines the bandwidth of the common frequency resource CFR defined for the terminal device with reduced capabilities.

[0216] Example 20. The apparatus according to Example 19, wherein the service announcement and / or broadcast MBS session establishment request further includes information regarding at least one bandwidth limitation condition for at least one FSAI or at least one frequency, wherein the FSAI or frequency defined for the degraded terminal device conforms to the at least one bandwidth limitation condition.

[0217] Example 21. An apparatus comprising: at least one processor; and at least one memory, the at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least: receive an MBS session creation request for a multicast broadcast service MBS session; in response to or based on the reception, generate at least one Frequency Selection Area Identifier (FSAI) defined for a degraded terminal device for the MBS session, and at least one indication defined for the degraded terminal device; and send a broadcast MBS session establishment request for the MBS session to at least one access node, wherein the broadcast MBS session establishment request includes at least one FSAI and at least one indication.

[0218] Example 22. The apparatus according to Example 21, wherein generating a mapping between at least one of MBS service area or broadcast MBS session information and MBS FSAI is performed.

[0219] Example 23. The apparatus according to Example 21 or 22, wherein the broadcast MBS session establishment request further includes at least one indication that at least one FSAI is defined for a degraded terminal device.

[0220] Example 24. An apparatus according to any one of Examples 21 to 23, wherein at least one memory and instructions are configured together with at least one processor to cause the apparatus to perform: receiving an MBS session creation request from an application function AF; and, after generation, sending an MBS session creation response to the AF, wherein the MBS session creation request response includes at least one FSAI and at least one indication that the at least one FSAI is defined for a degraded terminal device.

[0221] Example 25. A method comprising: receiving a service announcement of a multicast broadcast service MBS, wherein the service announcement includes at least one of the following:

[0222] - At least one Frequency Selection Area Identifier (FSAI) and at least one indication defined to indicate that the at least one FSAI is for a terminal device with reduced capabilities, or

[0223] - At least one frequency and at least one indication that the at least one frequency is defined for a terminal device with reduced capabilities;

[0224] The methods also include: performing a cell reselection process based on cell measurements and service announcements.

[0225] Example 26: 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:

[0226] Receive service announcements from the Multicast Broadcast Service (MBS);

[0227] Receive at least one indication in at least one message following the service announcement, the at least one indication specifying that all or at least some of the degraded terminal devices for MBS are supported; and

[0228] The cell reselection process is performed based on cell measurements and at least one indication.

[0229] Example 27: The apparatus according to Example 26, wherein:

[0230] Service notifications include at least one Frequency Selection Area Identifier (FSAI) associated with the MBS, and at least one indication that at least one FSAI is defined for a terminal device with reduced capabilities; and / or

[0231] The service notification includes at least one frequency associated with MBS, and at least one indication that the at least one frequency is defined for terminal devices with reduced capabilities;

[0232] The cell reselection process is also based on at least one FSAI and / or at least one frequency.

[0233] Example 28: The apparatus according to Example 27, wherein the apparatus is a degraded terminal device; and wherein performing the cell reselection process includes:

[0234] During cell reselection, frequencies associated with at least one FSAI or at least one frequency defined for terminal devices with reduced capabilities are given priority.

[0235] Example 29: The apparatus according to Example 28, wherein the service announcement further includes one or more FSAIs or one or more frequencies, without any indication that the one or more FSAIs or one or more frequencies are defined for a degraded end device; and wherein prioritization includes:

[0236] During cell reselection, frequencies associated with at least one FSAI or frequency defined for a terminal device that is not indicated for a degraded capability are given priority, at least relative to frequencies associated with one or more FSAIs or frequencies not indicated for a degraded capability terminal device.

[0237] Example 30: The apparatus according to Example 27, wherein the apparatus is a non-degraded terminal device, the service advertisement also includes one or more FSAIs or one or more frequencies, without any indication that the one or more FSAIs or one or more frequencies are defined for a degraded terminal device; and wherein performing the cell reselection process includes:

[0238] During cell reselection, frequencies associated with one or more FSAIs or frequencies not associated with degraded terminal devices are given priority over frequencies associated with at least one FSAI or frequency defined for terminal devices that are indicated for degraded capabilities.

[0239] Example 31: The apparatus according to Example 27, wherein for at least one FSAI or at least one frequency, the service notification further includes information about at least one bandwidth limitation condition, which is indicated to be met by at least one FSAI or at least one frequency defined for a terminal device with reduced capabilities.

[0240] Example 32: The apparatus according to Example 31, wherein at least one bandwidth limiting condition includes a condition for bandwidth size and / or a condition for the type of terminal device with reduced capabilities.

[0241] Example 33: The apparatus according to Example 31 or 32, wherein the apparatus is a degraded terminal device; and wherein performing the cell reselection process includes:

[0242] For at least one frequency or at least one FSAI associated with at least one bandwidth limitation, determine whether the degraded terminal device meets at least one bandwidth limitation; and

[0243] During cell reselection, the frequency associated with at least one FSAI or at least one frequency that meets at least one bandwidth limitation condition of the terminal device with reduced capability is given priority.

[0244] Example 34: The apparatus according to Example 33, wherein the service announcement includes one or more FSAIs or one or more frequencies, without any indication that the one or more FSAIs or one or more frequencies are defined for a degraded end device, prioritization includes:

[0245] During cell reselection, at least one frequency associated with one or more FSAIs or frequencies that are defined for a terminal device with reduced capabilities, relative to frequencies that are not specified for a terminal device with reduced capabilities, is given priority over frequencies associated with one or more FSAIs or frequencies that meet at least one bandwidth limitation condition.

[0246] Example 35: An apparatus according to any one of Examples 28 to 34, wherein the service notification includes at least one FSAI and at least one indication defined for a degraded end device, and at least one memory and instructions are configured, together with at least one processor, to cause the apparatus to perform:

[0247] In at least one message following the service announcement, a mapping between at least one FSAI and at least one frequency defined in the service announcement is received; and

[0248] The cell reselection process is also performed based on this mapping.

[0249] Example 36: The apparatus according to Example 27, wherein at least one memory and instructions are configured, together with at least one processor, such that the apparatus further performs:

[0250] The device receives neighboring cell frequency information, which includes a mapping between at least one neighboring cell frequency and at least one FSAI used for at least one MBS session for MBS, wherein the neighboring cell frequency is the operating frequency of the neighboring cells of the device's serving cell, and cell reselection is also based on the neighboring cell frequency information.

[0251] At least one message following the service announcement includes at least one instruction, for each of at least one neighboring cell, to support all or at least some of the reduced capabilities of the terminal devices used for MBS in terms of supporting at least one FSAI or at least one MBS session.

[0252] Example 37: The apparatus according to Example 36, wherein at least one indication indicates at least one of the following for each at least one neighboring cell: • Whether the reduced-capacity terminal device is supported for at least one FSAI or at least one MBS session. • A terminal device that is supported for at least one type of reduced capability for at least one FSAI or at least one MBS session, or

[0253] • A public frequency resource (CFR) of at least one size that can be used for at least one FSAI or at least one MBS session.

[0254] Example 38: The apparatus according to Example 36 or 37, wherein the apparatus is a de-capacitated terminal device.

[0255] Example 39: The apparatus according to Example 38, wherein at least one indication specifies a terminal device that supports degraded capabilities for at least one FSAI or at least one MBS session, without indicating any of the following: a CFR of at least one size that can be used for at least one FSAI or at least one MBS session; and a terminal device that supports at least one type of degraded capabilities for at least one FSAI or at least one MBS session; and wherein performing the cell reselection process includes:

[0256] During cell reselection, the frequency of at least one neighboring cell associated with at least one indication that indicates a terminal device is supported for reduced capability for at least one FSAI or at least one MBS session is given priority.

[0257] Example 40: The apparatus according to Example 38, wherein at least one indication specifies a terminal device capable of at least one size of CFR for at least one FSAI or at least one MBS session, and / or supporting at least one type of reduced capability for at least one FSAI or at least one MBS session; and wherein performing the cell reselection process includes:

[0258] During cell reselection, priority is assigned to at least one neighboring cell frequency that is associated with the size of the CFR supported by the degraded terminal equipment and / or with the type of degraded terminal equipment corresponding to the degraded terminal equipment.

[0259] Example 41: The apparatus according to Example 36 or 37, wherein the apparatus is a non-degraded terminal device; and wherein performing the cell reselection process includes:

[0260] During cell reselection, based on at least one indication and neighboring cell frequency information, at least one neighboring cell frequency of the terminal device that cannot support reduced capabilities is given priority.

[0261] Example 42: An apparatus according to any one of Examples 26 to 41, wherein the service announcement indicates at least one FSAI associated with an MBS session or at least one frequency associated with an MBS session, and the cell reselection process is also based on the service announcement.

[0262] Example 43: The apparatus according to any one of Examples 26 to 42, wherein at least one message is a System Information Block 21 (SIB21) message or includes a SIB21 message.

[0263] Example 44: An apparatus according to any one of Examples 26 to 43, wherein at least one memory and instructions are configured, together with at least one processor, to cause the apparatus to perform:

[0264] During the cell reselection process, it operates in the idle or inactive state of the Radio Resource Electrical Control (RRC).

[0265] Example 45: A method that includes:

[0266] Receive service announcements from the Multicast Broadcast Service (MBS);

[0267] In a service announcement and / or at least one message following the service announcement, at least one instruction is received indicating that all or at least some of the degraded terminal devices used for MBS are supported; and

[0268] The cell reselection process is performed based on cell measurements and at least one indication.

[0269] Example 46: A non-transitory computer-readable medium having instructions stored thereon, which, when executed by a computing device, cause the computing device to perform:

[0270] Receive service announcements from the Multicast Broadcast Service (MBS);

[0271] In a service announcement and / or at least one message following the service announcement, at least one instruction is received indicating that all or at least some of the degraded terminal devices used for MBS are supported; and

[0272] The cell reselection process is performed based on cell measurements and at least one indication.

[0273] Throughout this specification, any 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 present invention. Therefore, the phrases "in one embodiment" or "in an embodiment" appearing throughout the specification do not necessarily all refer to the same embodiment.

[0274] As used herein, for convenience, multiple items, structural elements, components, and / or materials may be presented in a public list. However, these lists should be interpreted as if each member of the list were individually identified as a separate and unique member. Therefore, unless otherwise indicated, an individual member of such a list should not be interpreted as a de facto equivalent of any other member of the same list based solely on its presentation in a public group. Furthermore, various embodiments and examples of the present technical solution, as well as alternatives to its various components, may be referenced herein. It should be understood that such embodiments, examples, and alternatives should not be construed as de facto equivalents of each other, but should be regarded as separate and autonomous representations of the present technical solution.

[0275] Even though embodiments have been described above with reference to examples in conjunction with the accompanying drawings, it will be apparent that the embodiments are not limited thereto, but can be modified in various ways within the scope of the appended claims. Therefore, all words and expressions should be interpreted broadly, and they are intended to illustrate rather than limit the embodiments. It will be apparent to those skilled in the art that the concepts of the invention can be implemented in various ways as technology advances. Furthermore, it will be apparent to those skilled in the art that the described embodiments can, but are not necessarily, be combined with other embodiments in various ways. Industrial applicability

[0276] At least some of these embodiments have industrial applications in wireless communication.

Claims

1. An apparatus comprising: At least one processor; as well as At least one memory storing instructions that, when executed by the at least one processor, cause the device to perform at least the following: Receive neighboring cell frequency information, the 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 the neighboring cells of the serving cell of the device. Receive at least one indication, which indicates at least one of the following for each of at least one neighboring cell: • Whether the terminal device with reduced capabilities is supported for the at least one FSAI or the at least one MBS session. • A terminal device that is supported for at least one type of reduced capability for the at least one FSAI or the at least one MBS session, or • At least one size of public frequency resource CFR that can be used for the at least one FSAI or the at least one MBS session; as well as Based on cell measurements, the frequency information of the neighboring cells, and the at least one indication, a cell reselection process is performed.

2. The apparatus according to claim 1, wherein the neighboring cell frequency information and the at least one indication are received in a System Information Block 21 (SIB21) message.

3. The apparatus according to any of the preceding claims, wherein the apparatus is a reduced-capacity terminal device.

4. The apparatus of claim 3, wherein the at least one indication indicates that a de-capacitated terminal device is supported for the at least one FSAI or the at least one MBS session, without indicating either: the at least one size of the CFR that can be used for the at least one FSAI or the at least one MBS session; or a de-capacitated terminal device of the at least one type that is supported for the at least one FSAI or the at least one MBS session. and The cell reselection process includes: During the cell reselection process, at least one neighboring cell frequency is given priority, and the at least one neighboring cell frequency is associated with at least one indication that the terminal device indicating reduced capability is supported for the at least one FSAI or the at least one MBS session.

5. The apparatus of claim 3, wherein the at least one indication indicates: a terminal device capable of the at least one size of the CFR for the at least one FSAI or the at least one MBS session, and / or supported by the at least one type of reduced capability for the at least one FSAI or the at least one MBS session; and The cell reselection process includes: During the cell reselection process, at least one neighboring cell frequency is prioritized, the frequency of which is associated with the CFR size supported by the degraded terminal device and / or with the type of degraded terminal device corresponding to the degraded terminal device.

6. The apparatus of claim 1 or 2, wherein the apparatus is a non-degraded terminal device; and wherein performing the cell reselection process comprises: During the cell reselection process, at least one neighboring cell frequency is given priority, and the at least one neighboring cell frequency cannot support terminal devices with reduced capabilities based on the at least one indication and the neighboring cell frequency information.

7. The apparatus according to any preceding claim, wherein the at least one memory and the instructions are configured, together with the at least one processor, to cause the apparatus to execute the following before receiving the neighboring cell frequency information: Receive a service announcement for 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 cell reselection process is also performed based on the service announcement.

8. The apparatus according to any preceding claim, wherein the at least one memory and the instructions are configured, together with the at least one processor, to cause the apparatus to perform: During the cell reselection process, the operation is performed in the Radio Resource Control (RRC) idle or inactive state.

9. An apparatus comprising: At least one processor; as well as At least one memory, the at least one memory storing instructions, the instructions, when executed by the at least one processor, cause the device to perform at least the following: Receive at least one indication from at least one neighboring access node, the at least one indication specifying at least one of the following: • At the adjacent access node of the at least one adjacent access node, is the degraded terminal device supported for at least one Frequency Selection Area Identifier (FSAI) or at least one Multicast Broadcast Service (MBS) session? • At the adjacent access node, a terminal device is supported with at least one type of reduced capability for at least one FSAI or at least one MBS session. • At the adjacent access node, at least one size of common frequency resource CFR is used for at least one FSAI or at least one MBS session, or • The CFR of at least one type currently being used by the adjacent access node for at least one FSAI or at least one MBS session; Sending neighboring cell frequency information to the terminal device, the neighboring cell frequency information including a mapping between at least one neighboring cell frequency and at least one FSAI used for at least one MBS session, wherein the neighboring cell frequency is the operating frequency of the neighboring cells of the serving cell provided by the device; as well as Send at least one indication to the terminal device, the at least one indication indicating at least one of the following for each of the at least one neighboring cell provided by the at least one neighboring access node: • Whether the terminal device with reduced capabilities is supported for the at least one FSAI or the at least one MBS session. • A terminal device that is supported for at least one type of reduced capability for the at least one FSAI or the at least one MBS session, or • A CFR of at least one size that can be used for at least one FSAI or at least one MBS session.

10. The apparatus of claim 9, wherein the at least one memory and the instructions are configured, together with the at least one processor, to cause the apparatus to perform: The core network function receives a broadcast MBS session establishment request for a multicast broadcast service MBS session, wherein the broadcast MBS session establishment request includes at least one FSAI associated with the MBS session.

11. The apparatus of claim 10, wherein the at least one memory and the instructions are configured, together with the at least one processor, to cause the apparatus to perform: Configuration information is received from the operation, management, and control OAM entity, wherein the configuration information includes at least one indication indicating that: the at least one FSAI associated with the MBS session is defined for a degraded terminal device; and Based on the configuration information, the transmission of the MBS session within the CFR defined for the degraded terminal device is triggered.

12. The apparatus according to any one of claims 9 to 11, wherein the at least one memory and the instructions are configured, together with the at least one processor, to cause the apparatus to perform: Send at least one indication to the at least one adjacent access node, the at least one indication specifying at least one of the following: • At the device, is the de-capable terminal device supported for the at least one FSAI or the at least one MBS session? • At the device, a terminal device is supported for at least one type of reduced capability for the at least one FSAI or the at least one MBS session; or • At the device, at least one size of CFR is used for the at least one FSAI or the at least one MBS session; or • The type of CFR currently being used by the device for the at least one FSAI or the at least one MBS session.

13. An apparatus comprising: At least one processor; as well as At least one memory storing instructions that, when executed by the at least one processor, cause the device to perform at least the following: From each of one or more adjacent access nodes, receive at least one Temporary Mobile Group Identifier (TMGI) associated with at least one ongoing Multicast Broadcast Service (MBS) session at the adjacent access node, and for each of the at least one TMGI, receive at least one indication indicating at least one of the following: • At the adjacent access node, is the terminal device with reduced capability supported for TMGI? • At the adjacent access node, a terminal device with at least one type of reduced capability is supported for the TMGI; or • At the adjacent access node, a CFR of at least one size is used for the TMGI; The device sends neighboring cell frequency information to the terminal device. The neighboring cell frequency information includes a mapping between at least one neighboring cell frequency and at least one FSAI used for the at least one MBS session. The neighboring cell frequency is the operating frequency of the neighboring cell of the serving cell provided by the device. The neighboring cell frequency information is based on the at least one TMGI, the at least one indication, and the mapping between the at least one TMGI and the at least one FSAI used for the at least one MBS session. as well as Sending at least one indication to the terminal device for at least one neighboring cell provided by the one or more neighboring access nodes, wherein the at least one indication indicates at least one of the following for each at least one neighboring cell: • Whether the terminal device with reduced capabilities is supported for the at least one FSAI or the at least one MBS session. • A terminal device that is supported for at least one type of reduced capability for the at least one FSAI or the at least one MBS session, or • A public frequency resource (CFR) of at least one size that can be used for at least one FSAI or at least one MBS session.

14. The apparatus of claim 13, wherein the at least one memory and the instructions are configured, together with the at least one processor, to cause the apparatus to perform: Send at least one TMGI associated with at least one MBS session in progress at the device to each of the one or more adjacent access nodes, and send at least one indication for each of the at least one TMGI associated with the at least one MBS session in progress at the device, the at least one indication indicating at least one of the following: • At the device, is the reduced-capability terminal device supported for TMGI? • At the device, a terminal device of at least one type with reduced capability is supported for the TMGI; or • At the device, at least one size of CFR is used for the TMGI.

15. The apparatus of claim 13 or 14, wherein the at least one memory and the instructions are configured, together with the at least one processor, to cause the apparatus to execute the following before transmitting the neighboring cell frequency information: Receives a broadcast MBS session establishment request for an MBS session from the core network functions, wherein the broadcast MBS session establishment request includes at least one FSAI associated with the MBS session; and Based on the broadcast MBS session establishment request, and the at least one TMGI and the at least one indication received from the one or more adjacent access nodes, the mapping between the at least one TMGI and the at least one FSAI for the at least one MBS session is determined.

16. The apparatus of claim 15, wherein the at least one memory and the instructions are configured, together with the at least one processor, to cause the apparatus to perform: Configuration information is received from the operation, management, and control OAM entity, wherein the configuration information includes at least one indication indicating that: the at least one FSAI associated with the MBS session supported by the device is defined for a degraded terminal device; and Based on the configuration information, the transmission of the MBS session within the CFR defined for the degraded terminal device is triggered.

17. The apparatus according to any one of claims 9 to 16, wherein the neighboring cell frequency information and the at least one indication are sent to the terminal device in a System Information Block 21 (SIB21) message.

18. A method comprising: Receive neighboring cell frequency information, the 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 the neighboring cells of the serving cell of the device. Receive at least one indication, which indicates at least one of the following for each of at least one neighboring cell: • Whether the terminal device with reduced capabilities is supported for the at least one FSAI or the at least one MBS session. • A terminal device that is supported for at least one type of reduced capability for the at least one FSAI or the at least one MBS session, or • At least one size of public frequency resource CFR that can be used for the at least one FSAI or the at least one MBS session; as well as Based on cell measurements, the frequency information of the neighboring cells, and the at least one indication, a cell reselection process is performed.

19. A method comprising: Receive at least one indication from at least one neighboring access node, the at least one indication specifying at least one of the following: • At the adjacent access node of the at least one adjacent access node, is the degraded terminal device supported for at least one Frequency Selection Area Identifier (FSAI) or at least one Multicast Broadcast Service (MBS) session? • At the adjacent access node, a terminal device is supported with at least one type of reduced capability for at least one FSAI or at least one MBS session. • At the adjacent access node, at least one size of common frequency resource CFR is used for at least one FSAI or at least one MBS session. • The CFR of at least one type currently being used by the adjacent access node for at least one FSAI or at least one MBS session; Sending neighboring cell frequency information to the terminal device, the neighboring cell frequency information including a mapping between at least one neighboring cell frequency and at least one FSAI used for at least one MBS session, wherein the neighboring cell frequency is the operating frequency of the neighboring cells of the serving cell provided by the device; as well as Send at least one indication to the terminal device, the at least one indication indicating at least one of the following for each of the at least one neighboring cell provided by the at least one neighboring access node: • Whether the terminal device with reduced capabilities is supported for the at least one FSAI or the at least one MBS session. • A terminal device that is supported for at least one type of reduced capability for the at least one FSAI or the at least one MBS session, or • A CFR of at least one size that can be used for at least one FSAI or at least one MBS session.

20. A method comprising: From each of one or more adjacent access nodes, receive at least one Temporary Mobile Group Identifier (TMGI) associated with at least one ongoing Multicast Broadcast Service (MBS) session at the adjacent access node, and for each of the at least one TMGI, receive at least one indication indicating at least one of the following: • At the adjacent access node, is the terminal device with reduced capability supported for TMGI? • At the adjacent access node, a terminal device with at least one type of reduced capability is supported for the TMGI; or • At the adjacent access node, a CFR of at least one size is used for the TMGI; The device sends neighboring cell frequency information to the terminal device. The neighboring cell frequency information includes a mapping between at least one neighboring cell frequency and at least one FSAI used for the at least one MBS session. The neighboring cell frequency is the operating frequency of the neighboring cell of the serving cell provided by the device. The neighboring cell frequency information is based on the at least one TMGI, the at least one indication, and the mapping between the at least one TMGI and the at least one FSAI used for the at least one MBS session. as well as Sending at least one indication to the terminal device for at least one neighboring cell provided by the one or more neighboring access nodes, wherein the at least one indication indicates at least one of the following for each at least one neighboring cell: • Whether the terminal device with reduced capabilities is supported for the at least one FSAI or the at least one MBS session. • A terminal device that is supported for at least one type of reduced capability for the at least one FSAI or the at least one MBS session, or • A public frequency resource (CFR) of at least one size that can be used for at least one FSAI or at least one MBS session.

21. A non-transitory computer-readable medium having instructions stored thereon, the instructions, when executed by a computing device, causing the computing device to perform: Receive neighboring cell frequency information, the 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 the neighboring cells of the serving cell of the device. Receive at least one indication, which indicates at least one of the following for each of at least one neighboring cell: • Whether the terminal device with reduced capabilities is supported for the at least one FSAI or the at least one MBS session. • A terminal device that is supported for at least one type of reduced capability for the at least one FSAI or the at least one MBS session, or • At least one size of public frequency resource CFR capable of being used for the at least one FSAI or the at least one MBS session; and Based on cell measurements, the frequency information of the neighboring cells, and the at least one indication, a cell reselection process is performed.

22. A non-transitory computer-readable medium having instructions stored thereon, the instructions, when executed by a computing device, causing the computing device to perform: Receive at least one indication from at least one neighboring access node, the at least one indication specifying at least one of the following: • At the adjacent access node of the at least one adjacent access node, is the degraded terminal device supported for at least one Frequency Selection Area Identifier (FSAI) or at least one Multicast Broadcast Service (MBS) session? • At the adjacent access node, a terminal device is supported with at least one type of reduced capability for at least one FSAI or at least one MBS session. • At the adjacent access node, at least one size of common frequency resource CFR is used for at least one FSAI or at least one MBS session. • The CFR of at least one type currently being used by the adjacent access node for at least one FSAI or at least one MBS session; The device sends neighboring cell frequency information to the terminal device, the neighboring cell frequency information including a mapping between at least one neighboring cell frequency and at least one FSAI used for at least one MBS session, wherein the neighboring cell frequency is the operating frequency of the neighboring cells of the serving cell provided by the device; and Send at least one indication to the terminal device, the at least one indication indicating at least one of the following for each of the at least one neighboring cell provided by the at least one neighboring access node: • Whether the terminal device with reduced capabilities is supported for the at least one FSAI or the at least one MBS session. • A terminal device that is supported for at least one type of reduced capability for the at least one FSAI or the at least one MBS session, or • A CFR of at least one size that can be used for at least one FSAI or at least one MBS session.

23. A non-transitory computer-readable medium storing instructions thereon, said instructions, when executed by a computing device, causing the computing device to perform: From each of one or more adjacent access nodes, receive at least one Temporary Mobile Group Identifier (TMGI) associated with at least one ongoing Multicast Broadcast Service (MBS) session at the adjacent access node, and for each of the at least one TMGI, receive at least one indication indicating at least one of the following: • At the adjacent access node, is the terminal device with reduced capability supported for TMGI? • At the adjacent access node, a terminal device with at least one type of reduced capability is supported for the TMGI; or • At the adjacent access node, a CFR of at least one size is used for the TMGI; The device sends neighboring cell frequency information to the terminal device. The neighboring cell frequency information includes a mapping between at least one neighboring cell frequency and at least one FSAI used for the at least one MBS session. The neighboring cell frequency is the operating frequency of the neighboring cell of the serving cell provided by the device. The neighboring cell frequency information is based on the at least one TMGI, the at least one indication, and the mapping between the at least one TMGI and the at least one FSAI used for the at least one MBS session. and Sending at least one indication to the terminal device for at least one neighboring cell provided by the one or more neighboring access nodes, wherein the at least one indication indicates at least one of the following for each at least one neighboring cell: • Whether the terminal device with reduced capabilities is supported for the at least one FSAI or the at least one MBS session. • A terminal device that is supported for at least one type of reduced capability for the at least one FSAI or the at least one MBS session, or • A public frequency resource (CFR) of at least one size that can be used for at least one FSAI or at least one MBS session.

Images