Apparatus, method and computer program product

Abstract

An apparatus includes at least one processor and at least one memory including computer program code, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to: determine that a configuration for the at least one service that the non-limited capability UE is interested in receiving is not provided in an MBS control channel for the non-limited capability UE; receiving a message indicating that the at least one service is only available in common frequency resources for the limited capability UE; receiving information including at least one of a configuration of a common frequency resource for the limited capability UE, a configuration of an MBS control channel for the limited capability UE, and content of the MBS control channel for the limited capability UE; and receiving at least one service based on the received information.

Description

Technical Field

[0001] The present invention relates generally to an apparatus, method and computer program, particularly but not exclusively to network devices and user equipment (UE) as part of a communication system. Background Technology

[0002] A communication system enables communication between two or more entities, such as communication devices, base stations, and / or other nodes, by providing carrier waves between various entities involved in the communication path.

[0003] A communication system can be a wireless communication system. Examples of wireless communication systems include Public Land Mobile Networks (PLMNs) operating based on radio standards (e.g., radio standards provided by 3GPP), satellite-based communication systems, and various wireless local networks (e.g., wireless local area networks (WLANs)). Wireless systems can be divided into cells and are often referred to as cellular systems or cellular networks.

[0004] Communication systems and associated devices typically operate according to a given standard or specification that describes how the various entities associated with the system are permitted to perform, how these entities are allowed to interact with each other, and how this should be implemented. Communication protocols and / or parameters that should be used for connections within the network are also defined by standards or specifications. As mentioned above, some examples of standards are radio standards provided by 3GPP, such as 2G, 3G, 4G, and 5G. The communication system described herein is based on the 5G standard. However, the described embodiments are not limited to operation according to 5G and may also be applicable to future radio standards, such as 6G. Summary of the Invention

[0005] According to one aspect of the present invention, an apparatus is provided. The apparatus includes at least one processor and at least one memory including computer program code. The at least one memory and the computer program code are configured, together with the at least one processor, to cause the apparatus to: determine that a configuration for at least one service that a non-limited-capability UE is interested in receiving is not provided in an MBS control channel for the non-limited-capability UE; receive a message indicating that the at least one service is available only in common frequency resources for limited-capability UEs; receive information including at least one of the configuration of common frequency resources for limited-capability UEs, the configuration of MBS control channels for limited-capability UEs, and / or the content of MBS control channels for limited-capability UEs; and receive the at least one service based on the received information.

[0006] The service can be a broadcast service or a multicast service.

[0007] The device may be a user equipment (UE) or a component thereof as described herein. In particular, the device may be a non-limited-capacity UE, also known as a non-capacity-reduced UE (non-RedCap UE).

[0008] At least one service can be received in the common frequency resources used for limited-capability UEs (also known as RedCap UEs).

[0009] At least some of the information can be provided in a system information block, such as system information block SIB20.

[0010] At least some of the information may be provided, alternatively or alternatively, in the MBS control channel used for capacity-reducing UEs. The MBS control channel may be the MCCH.

[0011] The UE can learn from the received information how to receive services on the MCCH used for capacity-reducing UEs.

[0012] On the other hand, an apparatus is provided. The apparatus includes at least one processor and at least one memory including computer program code. The at least one memory and the computer program code are configured, together with the at least one processor, to cause the apparatus to: transmit the following: a configuration for at least one service that a non-limited-capability UE might be interested in receiving is not provided in the MBS control channel for the non-limited-capability UE; transmit a message indicating that the at least one service is available only in the common frequency resources of the limited-capability UE; transmit information including at least one of the configuration of the common frequency resources for the limited-capability UE, the configuration of the MBS control channel for the limited-capability UE, and / or the content of the MBS control channel for the limited-capability UE; and transmit at least one broadcast service on the common frequency resources of the limited-capability UE.

[0013] In another aspect, there is an apparatus comprising: components for determining that the configuration of at least one service that a non-limited capability UE is interested in receiving is not provided in the MBS control channel for the non-limited capability UE; components for receiving a message indicating that at least one service is available only in the common frequency resources of a limited capability UE; components for receiving information including at least one of the configuration of the common frequency resources for the limited capability UE, the configuration of the MBS control channel for the limited capability UE, and / or the content of the MBS control channel for the limited capability UE; and components for receiving at least one broadcast service based on the received information.

[0014] In another aspect, there is an apparatus comprising: means for transmitting a configuration for at least one service that a non-limited capability UE may be interested in receiving, which is not provided in an MBS control channel for the non-limited capability UE; means for transmitting a message indicating that at least one service is available only in a common frequency resource of a limited capability UE; means for transmitting information including at least one of a configuration of a common frequency resource for a limited capability UE, a configuration of an MBS control channel for a limited capability UE, and / or the content of an MBS control channel for a limited capability UE; and means for transmitting at least one broadcast service on a common frequency resource of a limited capability UE.

[0015] On the other hand, a method is provided, comprising: determining that a configuration for at least one service that a non-limited capability UE is interested in receiving is not provided in an MBS control channel for the non-limited capability UE; receiving a message indicating that at least one service is available only in common frequency resources for a limited capability UE; receiving information including at least one of the configuration of common frequency resources for the limited capability UE, the configuration of an MBS control channel for the limited capability UE, and / or the content of an MBS control channel for the limited capability UE; and receiving at least one service based on the received information.

[0016] In another aspect, a method is provided. The method includes: transmitting a configuration for at least one service that a non-limited-capability UE might be interested in receiving, which is not provided in an MBS control channel for the non-limited-capability UE; transmitting a message indicating that at least one service is available only in common frequency resources for a limited-capability UE; transmitting information including at least one of the configuration of the common frequency resources for the limited-capability UE, the configuration of the MBS control channel for the limited-capability UE, and / or the content of the MBS control channel for the limited-capability UE; and transmitting at least one broadcast service.

[0017] On the other hand, a computer program product is provided, which is implemented on a computer-readable distribution medium and includes program instructions that, when executed by a device, cause the device to perform actions according to... Figure 9 and Figure 10 The method of the illustrated and described embodiment.

[0018] Another aspect provides a computer program product including program instructions, which, when executed by a device, cause the device to perform actions according to a reference. Figure 9 and Figure 10 The method of the described embodiment.

[0019] In this way, the present invention allows for optimal broadcast and multicast operations with respect to the newly introduced RedCap Common Frequency Resources (CFR) in terms of resource usage and power consumption, because normal non-limited capacity (non-RedCap) UEs do not have to use both wideband CFR and limited CFR to receive services. Attached Figure Description

[0020] Figure 1 A simplified schematic diagram of a 5G network is shown.

[0021] Figure 2 A simplified schematic illustration of a user equipment suitable for carrying out embodiments of the present invention is shown;

[0022] Figure 3 A block diagram schematically illustrates some examples of non-volatile storage media;

[0023] Figure 4 A block diagram of a 5G network is shown, including a schematic illustration of a gNodeB suitable for carrying out embodiments of the present invention;

[0024] Figure 5 A message flow diagram according to an embodiment is shown;

[0025] Figure 6 A message flow diagram according to an embodiment is shown;

[0026] Figure 7 A message flow diagram according to an embodiment is shown;

[0027] Figure 8 A message flow diagram according to an embodiment is shown;

[0028] Figure 9 A flow diagram illustrating the method according to an embodiment is shown; and

[0029] Figure 10 A flow diagram illustrating the method according to an embodiment is shown. Detailed Implementation

[0030] The following embodiments are exemplary. Although this specification may refer to "an," "one," or "some" (or more) embodiments in various places throughout the text, this does not necessarily mean that each reference is to the same embodiment(s) or that a particular feature is applicable only to a single embodiment. Individual features of different embodiments may also be combined to provide other embodiments. For the purposes of this disclosure, the phrases "at least one of A or B," "at least one of A and B," and "A and / or B" mean (A), (B), or (A and B). For the purposes of this disclosure, the phrases "A or B" and "A and / or B" mean (A), (B), or (A and B). For the purposes of this disclosure, the phrases "A, B, and / or C" mean (A), (B), (C), (A and B), (A and C), (B and C), or (A, B, and C).

[0031] It should be understood that while the terms "first" and "second," etc., may be used herein to describe various elements, these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, without departing from the scope of the exemplary embodiments, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element.

[0032] 3GPP Rel-17 MBS WI specifies that broadcast reception can be performed on user equipment (UE) in idle / inactive / connected RRC states (e.g., RRC_IDLE, RRC_INACTIVE, RRC_CONNECTED).

[0033] System Information Block 20 (SIB20) is a message containing information for the UE to receive Multicast Control Channel (MCCH) data, including the MCCH repetition period and the configured transmit / receive window. The MCCH data includes control information necessary for the UE to understand the broadcast services provided in the cell, as well as scheduling information for receiving broadcast data. This information is periodically transmitted by the gNB (gNodeB) at a configurable repetition period and within a configured transmit window.

[0034] The MCCH provides basic information about the Multicast Traffic Channel (MTCH), which is the data channel providing broadcast services. This information includes the search space, Discontinuous Reception (DRX) information, etc. The UE uses this information to receive the relevant MTCH(s). Each Temporary Mobile Group Identity (TMGI), which serves as the identifier for a specific broadcast service, is mapped to a specific MTCH.

[0035] To receive MCCH data, the UE reads and decodes the SIB20 message to learn the MCCH configuration / scheduling details. The UE then reads the MCCH data to learn the services offered in the cell and their scheduling information. However, for UEs in the RRC_CONNECTED state, SIB readings are ignored, and the UE is provided with a search space configuration to receive the MCCH within PDCCH-ConfigCommon. When in the RRC_INACTIVE state, the UE retrieves information from the SIB20 block, such as the MCCH repetition scheduling configuration, window duration, and start time slot. The MCCH content and the MCCH repetition window do not change during the modification period.

[0036] The Rel-17 specification describes the RRC_INACTIVE / RRC_IDLE UE behavior based on the configuration of CORESET#0, the Initial Bandwidth Part (BWP), and the Common Frequency Resource (CFR) for receiving broadcast services. CORESET#0 is the area where the UE can only receive control resources. The CFR is the area where the UE can receive MBS control and data transmissions.

[0037] In Rel-17, a UE receiving broadcast services in the RRC_IDLE / INACTIVE state can use the following steps to receive the relevant configuration: In addition to the details of the CFR configuration, SIB20 includes details on how to receive the MCCH (periodic and offset) within a given modification period. The UE first reads SIB20 to learn this information. Then, the UE reads the MCCH sent in the CFR. By reading the MCCH, the UE can begin to learn which services are provided in the current cell and how to receive those services using the necessary configuration. Finally, the UE can receive broadcast data.

[0038] Note that the MCCH and data will be sent in the same CFR.

[0039] Capability Reduction (RedCap) devices have a bandwidth (BW) limitation. This means that a RedCap UE cannot receive a BW greater than its specific maximum supported BW (e.g., 20MHz). If the initial bandwidth portion (BWP) of the system exceeds this limitation, the RedCap UE utilizes the initial BWP configured separately by System Information Block SIB1.

[0040] In Rel-17, 3GPP concluded that RedCap UEs can receive broadcast data if the CFR BW is properly configured for the RedCap UE; in other words, if the CFR BW is less than or equal to the BW supported by the RedCap UE. No specific MBS enhancements are applied to these UEs.

[0041] In Rel-18, some companies proposed introducing a new lower BWCFR for BW-limited UEs like RedCap UEs. However, none of the technical issues, including UE behavior, were specified. Even if this operation were defined in Rel-18, it would be the baseline understanding, and enhancements are expected in Rel-19. Companies tend to favor baseline solutions that do not affect normal (non-limited capacity or non-RedCap) UEs.

[0042] In RAN2#121, an agreement has been reached to introduce a separate Common Broadcast Frequency Resource (CFR) that can be used when the configured bandwidth for the default CFR in SIB20 exceeds the bandwidth capacity of bandwidth-limited UEs or RedCap UEs. This proposal was made in R2-2300797.

[0043] If two separate CFRs are introduced, one CFR is used for the Redcap UE, and the other CFR is used for the normal UE.

[0044] The first option is that the traditional or broadband CFR (for non-bandwidth-limited UEs or non-RedCap UEs) is separate from or partially overlaps with the narrowband CFR for RedCap UEs.

[0045] Wideband CFRs or non-RedCap CFRs can be separate from RedCap CFRs, or they may partially overlap. In this case, "partial overlap" means they may share some common parts; for example, CORESET#0 is common and overlaps with both the wideband (non-RedCap) CFR and the RedCap CFR. If these two CFRs partially overlap, it essentially means there will be two separate MCCHs corresponding to these two CFR areas, since CORESET#0 only contains control signaling resources. In this scenario, a normal (non-RedCap) UE will read the wideband CFR for broadcast control and data, while a RedCap UE will read the RedCap CFR. With this configuration, the following scenarios may occur:

[0046] The first option is for both non-RedCap UEs and RedCap UEs to receive public broadcast services in their respective CFRs. For public broadcast services targeting both non-RedCap and RedCap UEs, two separate control and data streams are sent in two different CFRs. RedCap UEs receive control and data in the RedCap CFR, while non-RedCap UEs receive control and data in the broadband non-RedCap CFR.

[0047] However, this option will require the same data / control information to be transmitted twice over the air. As stated above, baseline operation is defined in Rel-18, and this first option is a consequence of that, as the goal is not to alter the normal UE (non-limited capacity / non-RedCap) behavior.

[0048] The second option is that both non-RedCap and RedCap UEs receive only a portion of the public broadcast service within the RedCap CFR. This could also manifest as the non-RedCap UE reading two MCCHs in a scenario where the gNB only transmits a portion of the public broadcast service data within the RedCap CFR area. Therefore, the non-RedCap UE must now read both the RedCap and non-RedCap MCCHs to determine the configuration used to retrieve broadcast data within the RedCap CFR area. However, with this scheme, the non-RedCap UE will always need to monitor two different MCCHs, resulting in increased power consumption at the UE. It is worth noting that both non-RedCap and RedCap UEs should be able to read the RedCap CFR unless it is restricted to use only by RedCap UEs. However, Rel-17 UEs (neither non-RedCap nor RedCap UEs) will be unable to read the RedCap CFR introduced in Rel-18. This means that once any Rel-17 UE joins a broadcast session, broadcast data must now be transmitted within the regular Rel-17 CFR, as described in previous sections.

[0049] It is evident from the above options that, from the perspective of a normal UE, reading the two MCCHs sent in the Rel-18 Normal CFR and the Rel-18 RedCap CFR is not the optimal strategy. The primary objective of the embodiments described herein is to optimize the operation of a normal Rel-18 UE in the presence of the Rel-18 RedCap CFR.

[0050] Another scenario is where a legacy or broadband (non-limited capability or non-RedCap) CFR overlaps with a RedCap or narrowband CFR. In this scenario, the two CFR areas overlap, and therefore a single MCCH can be transmitted in the common overlapping area of ​​the RedCap CFR and broadband CFR. The gNB scheduler transmits control signaling information within the overlapping CFR area, which can be received by both RedCap UEs and normal UEs. The disadvantage of this option is that the MCCH of the non-RedCap UE must be transmitted within the smaller CFR area of ​​the RedCap UE. This can be disadvantageous for non-RedCap UEs that may have enhanced CFR requirements for MCCH.

[0051] Therefore, in terms of resource usage or power consumption for scheduling services or efficient broadcast reception by non-RedCap UEs, the broadcast operation when both non-RedCap CFR and RedCap CRF are configured is not optimal.

[0052] Figure 1 A system 100 in which embodiments described herein according to exemplary aspects may be operated is schematically illustrated. System 100 is part of a mobile communication network and includes a mobile device 130-1, which may be a terminal device, a user equipment (UE), or an Internet of Things (IoT) device.

[0053] The term "terminal device" or "UE" refers to any end device capable of wireless communication. By way of example and not limitation, a terminal device may also be referred to as a communication device, user equipment (UE), subscriber station (SS), portable subscriber station, mobile station (MS), or access terminal (AT). Terminal devices may include, but are not limited to, mobile phones, cellular phones, smartphones, VoIP phones, wireless local loop phones, tablets, wearable terminal devices, personal digital assistants (PDAs), portable computers, desktop computers, image capture terminal devices (such as digital cameras), gaming terminal devices, music storage and playback devices, in-vehicle wireless terminal devices, wireless endpoints, mobile stations, laptop embedded devices (LEEs), laptop mounted devices (LMEs), USB dongles, smart devices, wireless customer premises equipment (CPEs), Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated processing chain environments), consumer electronics devices, devices operating on commercial and / or industrial wireless networks, etc. In the following description, the terms "terminal device," "communication device," "terminal," "user equipment," and "UE" are used interchangeably.

[0054] For the purposes of this discussion, System 100 in Figure 1 The network portion depicted will be referred to as a 3GPP 5G network. However, this network can be any type of communication network, such as a 3G or 4G network, or it could be a 6G or other future network. Furthermore, the 5G network portion shown in System 100 can interact with another network of a different generation, such as a 4G or LTE network, or a 6G or other future network.

[0055] System 100 also includes gNB 120-1 and gNB 120-2 with corresponding cells 130-1 and 130-2. gNB 120-1 and gNB 120-2 are part of the mobile communication network and may include additional gNBs with corresponding cells.

[0056] The embodiments described herein can be implemented in any mobile communication network or radio system, such as a mobile communication network or radio system including at least one of the following radio access technologies (RATs): Global Microwave Access Interoperability (WiMAX), Global System for Mobile Communications (GSM, 2G), GSM EDGE Radio Access Network (GERAN), General Packet Radio Service (GRPS), Universal Mobile Telecommunications System based on Basic Wideband Code Division Multiple Access (W-CDMA) (UMTS, 3G), High-Speed ​​Packet Access (HSPA), Long Term Evolution (LTE), LTE Advanced, and Enhanced LTE (eLTE). The term 'eLTE' here refers to LTE evolution connected to a 5G core. LTE is also known as Evolved UMTS Terrestrial Radio Access (EUTRA) or Evolved UMTS Terrestrial Radio Access Network (EUTRAN). The term "resource" can refer to radio resources such as Physical Resource Blocks (PRBs), radio frames, subframes, time slots, subbands, frequency regions, subcarriers, beams, etc. The terms "transmit" and / or "receive" can refer to wireless transmission and / or reception via a radio propagation channel on a radio resource.

[0057] However, the embodiments are not limited to the system / RAT given as an example, but those skilled in the art can apply the solution to other communication systems / networks that provide the necessary properties. Some examples of suitable communication networks include 5G and / or 6G networks. The 3GPP solution for 5G is called New Radio (NR). 6G is envisioned as a further development of 5G. NR has been envisioned to use multiple-input multiple-output (MIMO) multi-antenna transmission technology, deploy more base stations or nodes than current LTE networks (the so-called small cell concept), including macro sites cooperating with smaller local access nodes, and perhaps also employing various radio technologies for better coverage and enhanced data rates. 5G may consist of more than one radio access technology / radio access network (RAT / RAN), each RAT / RAN optimized for certain use cases and / or spectrum. 5G mobile communications can have a wider 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, namely, sub-6GHz, cmWave and mmWave, and will be integrated with existing legacy radio access technologies such as LTE.

[0058] The current architecture in LTE networks is distributed across radios and centralized in the core network. Low-latency applications and services in 5G may require content to be closer to the radios, leading to localized routing and multi-access edge computing (MEC). 5G enables analytics and knowledge generation to occur at the data source. This approach requires leveraging resources that may not be continuously connected to the network, 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 near cellular subscribers to accelerate 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 networking and processing (which can also be categorized as local cloud / fog computing and grid / mesh computing), dew computing, mobile edge computing, micro-cloud, distributed data storage and retrieval, autonomous self-healing networks, remote cloud services, augmented and virtual reality, data caching, the Internet of Things (IoT) (massive connectivity and / or latency critical), and critical communications (autonomous vehicles, traffic safety, real-time analytics, time-critical control, healthcare applications). Edge cloud can access the RAN by leveraging Network Functions Virtualization (NVF) and Software-Defined Networking (SDN). Using edge cloud may mean that access node operations will be performed at least partially in a server, host, or node that is operatively coupled to a remote radio head or base station, including a radio portion. Network slicing allows the creation of multiple virtual networks over a shared public physical infrastructure. These virtual networks are then customized to meet the specific needs of applications, services, devices, customers, or operators.

[0059] Signals from gNB 120-1 and gNB 120-2 can be observed by mobile devices or user equipment (UEs). UE 140-1 and UE 140-2 are served by gNB 120-1 within cell 130-1. There may be [something] caused by [something]. Figure 1 The network shown serves other UEs, which may be UE / IoT devices, such as mobile phones or autonomous vehicles.

[0060] gNB 120-1 and gNB 120-2 are connected to each other via the Xn interface and connected to the core network 150 via the NG interface respectively.

[0061] Multiple different broadcast and / or multicast services (MBS) can be provided by gNB 120-1 in cell 130-1 via the Multicast Service Channel (MTCH), which is a data channel that provides multicast / broadcast services.

[0062] gNB 120-1 provides information about the Multicast Traffic Channel (MTCH) by periodically sending, for example, Multicast Control Channel (MCCH) messages. These MCCH messages contain MTCH information (e.g., service configuration information) for UEs (such as UE 140-1) within cell 130-1 to receive the MTCH. The MTCH information may include control information necessary for UE 140-1 to understand the multicast / broadcast services provided in the cell, as well as scheduling information for receiving multicast / broadcast data.

[0063] For example, MCCH messages are sent periodically by gNB 120-1 at a configured repetition period and within a configured transmission window.

[0064] The gNB 120-1 provides information about the MCCH by sending SIB20 messages. SIB20 contains information for the mobile device to receive MCCH data (e.g., fallback configuration information), including the MCCH repetition period and the configured transmit / receive window.

[0065] UE 140-1 can be in the RRC_IDLE, RRC_INACTIVE, or RRC_CONNECTED state.

[0066] If UE 140-1 is in the RRC_IDLE or RRC_INACTIVE state, in order to receive MBS, UE 140-1 receives the SIB20 message sent by gNB 120-1. UE 140-1 then decodes the SIB20 message and thereby determines the MCCH configuration / scheduling details (e.g., service configuration set information). UE 140-1 then receives the MCCH message sent by gNB 120-1 to learn which MBS are provided in cell 140-1 and their scheduling information. UE 140-1 is then able to receive the desired MBS via the corresponding MTCH.

[0067] Reference will now be made to a schematic partial cross-sectional view showing the communication device 140-1. Figure 2Examples of UE 140-1 (which can be any wireless communication device) are described in more detail below. A suitable UE or mobile communication device can be provided by any device capable of transmitting and receiving radio signals. Non-limiting examples include mobile stations (MS) or mobile devices, such as mobile phones or so-called 'smartphones', computers equipped with wireless interface cards or other wireless interface facilities (e.g., USB dongles), personal digital assistants (PDAs) or tablets equipped with wireless communication capabilities, or any combination of these. For example, a mobile communication device can provide data communication for carrying communications such as voice, email, text messaging, multimedia, etc. Thus, users can be supplied and provided with a variety of services via their communication devices. Non-limiting examples of these services include two-way or multi-way calling, data communication or multimedia services, or simply access to a data communication network system (such as the Internet). Users may also be provided with broadcast or multicast data. Non-limiting examples of content include downloads, television and radio programs, videos, advertisements, various alarms, and other information.

[0068] UE 140-1 can be, for example, a mobile device, i.e., a device not fixed to a specific location, or it can be a stationary device. Wireless devices may or may not require human interaction to communicate. As described herein, the term UE or “user” is used to refer to any type of wireless communication device.

[0069] In this discussion, UE 140-1 is a non-RedCap UE capable of reading broadband or legacy CFRs, while UE 140-2 is a RedCap UE of the aforementioned type that can only read RedCap CFRs. However, for all intents and purposes, the structure of RedCap UE 140-2 is similar to... Figure 2 The UE 140-1 shown is the same.

[0070] UE 140-1 can receive signals via an air interface or radio interface 201 through appropriate means for receiving, and can transmit signals via appropriate means for transmitting radio signals. Figure 2 In the diagram, the transceiver device is schematically indicated by frame 202. For example, the transceiver device 202 may be provided by means of a radio section and an associated antenna arrangement. The antenna arrangement may be located inside or outside the wireless device.

[0071] UE 140-1 is typically provided with at least one data processing entity 203, at least one memory 204, and other possible components 205 for software and hardware-assisted execution of the tasks it is designed to perform, including controlling access to and communication with access systems and other communication devices. Data processing, storage, and other related control devices may be provided on a suitable circuit board and / or chipset. This feature is indicated by reference numeral 206. A user can control the operation of the wireless device by means of a suitable user interface (such as a keypad 207, voice commands, a touchscreen or touchpad, or a combination thereof). A display 208, a speaker, and a microphone may also be provided. Furthermore, the wireless communication device may include connections to other devices and / or suitable connectors (wired or wireless) for connecting external accessories (e.g., hands-free devices) to it.

[0072] Figure 2 The components of UE 140-1 and / or its associated circuitry shown may also be referred to as “components for receiving…”, “components for transmitting…”, “components for determining…”, etc.

[0073] Figure 3 A schematic representation of a non-volatile memory medium 300a (e.g., a computer disk (CD) or digital multifunction disk (DVD)) and a non-volatile memory medium 300b (e.g., a Universal Serial Bus (USB) Memory Stick) is shown, which allows the processor to execute instructions and / or parameters 304 when executed by the processor. Figure 5 and / or Figure 6 and / or Figure 7 and / or Figure 8 and / or Figure 9 and / or Figure 10 One or more steps of the method and / or the methods previously described elsewhere.

[0074] As provided herein, various aspects are described in the detailed description of the examples and the claims. Generally, some examples can be implemented in hardware or special-purpose circuitry, software, logic, or any combination thereof. For example, some aspects can be implemented in hardware, while others can be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device, although the examples are not limited thereto. While various examples may be illustrated and described as block diagrams, flowcharts, or using some other graphical representation, it is to be fully understood that the blocks, apparatuses, systems, techniques, or methods described herein can be implemented in hardware, software, firmware, special-purpose circuitry or logic, general-purpose hardware or controllers or other computing devices, or some combination thereof, as non-limiting examples.

[0075] The example can be implemented by computer software stored in memory and is executable by at least one data processor of the entity involved, or by hardware, or by a combination of software and hardware. Furthermore, it should be noted in this regard that, for example, as in... Figure 5 and / or Figure 6 and / or Figure 7 and / or Figure 8 and / or Figure 9 and / or Figure 10 Neutralization and / or any other processes previously described may represent program steps, or interconnected logic circuits, logic blocks, and logic functions, or combinations of program steps and logic circuits, logic blocks, and logic functions. Software may be stored on such physical media as memory chips, or on memory blocks implemented within a processor, magnetic media (such as hard disks or floppy disks), and optical media (such as, for example, DVDs and their data variants, CDs).

[0076] The memory can be of any type suitable for the local technical environment and can be implemented using any suitable data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. The data processor can be of any type suitable for the local technical environment and, by way of non-limiting example, can include one or more of the following: general-purpose computers, special-purpose computers, microprocessors, data signal processors (DSPs), application-specific integrated circuits (ASICs), gate-level circuits, and processors based on multi-core processor architectures.

[0077] Additionally or alternatively, some examples may be implemented using a circuit system. This circuit system may be configured to perform one or more of the previously described functions and / or method steps. This circuit system may be provided in base stations and / or communication equipment and / or core network entities.

[0078] As used in this application, the term "circuit system" may refer to one or more, or all of the following: (a) Hardware circuit implementation only (such as implementations in analog and / or digital circuit systems only). (b) A combination of hardware circuits and software, such as: (i) A combination of (multiple) analog and / or digital hardware circuits and software / firmware, and (ii) Any part of the hardware processor(s) having software (including (multiple) digital signal processors), software, and (multiple) memories, which work together to enable a device such as a communication device or base station to perform the various functions previously described; and (c) (Multiple) hardware circuits and / or (multiple) processors, such as (multiple) microprocessors or a portion thereof, which require software (e.g. firmware) for operation, but may be absent when operation is not required.

[0079] This definition of circuit system applies to all uses of the term in this application, including in any claim. As yet another example, as used herein, the term circuit system will also cover only the implementation of hardware circuitry or a processor (or processors) or a portion thereof and its accompanying software and / or firmware. The term circuit system will also cover, for example, integrated devices.

[0080] The foregoing description provides a complete and informative account of some examples through non-limiting examples. However, various modifications and adaptations may become apparent to those skilled in the art when read in conjunction with the accompanying drawings and claims, given the foregoing description. Nevertheless, all such modifications and similar alterations taught will still fall within the scope of the claims.

[0081] In the foregoing, radio access architectures based on Advanced Long Term Evolution (LTE-A, LTE-A) or New Radio (NR, 5G) are used as examples of access architectures to which the described technologies can be applied to describe different examples; however, the examples are not limited to this architecture. By appropriately adapting parameters and procedures, the examples can also be applied to other kinds of communication networks with suitable components. Some examples of other options for suitable systems are Universal Mobile Telecommunications System (UMTS) Radio Access Network (UTRAN), Wireless Local Area Network (WLAN or WiFi), Global Microwave Access 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.

[0082] Figure 5 A simplified example of a system architecture is shown, which only shows some elements and functional entities, all of which are logical units, and their implementation may differ from that shown. Figure 5 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 5 Other functions and structures besides those shown.

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

[0084] Figure 5 The example illustrates a portion of an illustrative radio access network. For instance, the radio access network may support sidelink communication, as described in more detail below.

[0085] Figure 4 UE 140-1 and UE 140-2 are shown. UE 140-1 and UE 140-2 are configured to wirelessly connect to gNB 120-1 on one or more communication channels. gNB 120-1 is also connected to core network 150. For the purposes of this discussion, node 120-1 is the gNB serving UE 140-1 and UE 140-2 in the cell. However, node 120-1 could also be an LTE eNB or even a non-3GPP access node. The physical link from the UE to the gNB is referred to as the uplink or reverse link, and the physical link from the gNB to the UE is referred to as the downlink or forward link. It should be understood that the gNB or its functionality can be implemented using any entity such as a node, host, server, or access point suitable for this use.

[0086] Communication systems typically include more than one gNB, such as Figure 1 As shown, in this configuration, the gNB can also be configured to communicate with each other via wired or wireless links designed specifically for this purpose, such as the Xn interface. These links can be used for signaling purposes. The gNB 120-1 is a computing device configured to control the radio resources of the communication system coupled thereto. The gNB can also be referred to as a base station, access point, or any other type of interface device including relay stations capable of operating in a wireless environment. The gNB includes or is coupled to a transceiver. A connection is provided from the gNB's transceiver to an antenna element, establishing a bidirectional radio link to the device. The antenna element may include multiple antennas or antenna elements. The gNB 120-1 is also connected to the core network 150 (CN or Next Generation Core NGC). Depending on the deployed technology, the gNB is connected to the Serving and Packet Data Network Gateway (S-GW+P-GW) or User Plane Function (UPF) for routing and forwarding user data packets and for providing connectivity to one or more external packet data networks, and is connected to the Mobility Management Entity (MME) or Access Mobility Management Function (AMF) for controlling device (UE) access and mobility.

[0087] Examples of UE devices 140-1 and UE 140-2 include subscriber units, user equipment, user equipment (UE), user terminals, terminal equipment, mobile stations, mobile devices, etc.

[0088] UE devices generally refer to mobile or static devices (e.g., portable or non-portable computing devices) that include wireless mobile communication devices with or without a Universal Subscriber Identity Module (USIM), including but not limited to: mobile phones, smartphones, personal digital assistants (PDAs), cell phones, devices using wireless modems (such as alarm or measuring devices), laptops and / or touchscreen computers, tablets, game consoles, and multimedia devices. It should be understood that devices can also be virtually unique uplink-only devices, examples of which are cameras or camcorders that load images or video clips onto a network. Devices can also be devices capable of operating in Internet of Things (IoT) networks, which are scenarios where objects are provided with the ability to transmit data over the network without human-to-human or human-to-computer interaction, for example, for use in smart grids and connected vehicles. Devices can also utilize the cloud. In some applications, devices may include user portable devices (such as watches, headphones, or glasses) with a radio component, and computation is performed in the cloud.

[0089] UE 140-1 and UE 140-2 illustrate a type of device where resources on the air interface can be allocated and assigned, and therefore any features described herein as devices can be implemented by corresponding devices such as relay nodes. An example of such a relay node is a Layer 3 relay (self-backhaul relay) toward a base station. The device (or, in some examples, a Layer 3 relay node) is configured to perform one or more of the user equipment functionalities.

[0090] The various techniques described in this article can also be applied to cyber-physical systems (CPS) (systems that collaboratively control computational elements of physical entities). CPS enables the implementation and development of a large number of interconnected information and communication technology (ICT) devices (sensors, actuators, processors, microcontrollers, etc.) embedded in physical objects at different locations. Mobile cyber-physical systems, which are inherently mobile physical systems, are a subcategory of cyber-physical systems. Examples of mobile physical systems include mobile robots and electronic products transported by humans or animals.

[0091] Additionally, although the device has been described as a single entity, different units, processors, and / or memory units (not listed in the original text) are present. Figure 4 (As shown in the image) can be implemented.

[0092] 5G enables the use of many more base stations or nodes than LTE (the so-called small cell concept) with multiple MIMO antennas, including macro sites that cooperate with smaller stations and employ multiple radio technologies depending on service needs, use cases, and / or available spectrum. 5G mobile communications support a wide range of use cases and related applications, including video streaming, augmented reality, data sharing in various ways, and various forms of machine-type applications such as (massive) machine-type communications (mMTC), including vehicle safety, various sensors, and real-time control. 5G is expected to have multiple radio interfaces, such as below 6 GHz or above 24 GHz, cmWave, and mmWave, 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 from small cells is achieved through aggregation to LTE. In other words, 5G is planned to support both RAT interoperability (such as LTE-5G) and RI interoperability (radio interface interoperability, such as below 6 GHz - cmWave, 6 or above 24 GHz - cmWave and mmWave). One concept considered for use in 5G networks is network slicing, where multiple independent and dedicated virtual subnets (network instances) can be created within the same infrastructure to run services with different requirements for latency, reliability, throughput, and mobility.

[0093] The LTE network architecture is entirely distributed across radio waves and centrally located within the core network. Low-latency applications and services in 5G require content to be closer to the radio waves, leading to localized routing and multi-access edge computing (MEC). 5G enables analytics and knowledge generation to occur at the data source. This approach leverages resources that may not be continuously connected to the network, such as laptops, smartphones, tablets, and sensors. MEC provides a distributed computing environment for application and service hosting. MEC also has the ability to store and process content near cellular subscribers to accelerate 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 networking and processing (which can also be categorized as local cloud / fog computing and grid / mesh computing), dew computing, mobile edge computing, micro-cloud, distributed data storage and retrieval, autonomous self-healing networks, remote cloud services, augmented and virtual reality, data caching, the Internet of Things (IoT) (massive connectivity and / or latency critical), and critical communications (autonomous vehicles, traffic safety, real-time analytics, time-critical control, healthcare applications).

[0094] The communication system can also communicate with other networks 160, such as public handover telephone networks, VoIP networks, the Internet, or private networks, via gNB 120-1, or utilize services provided by them. The communication network may also be able to support the use of cloud services; for example, at least a portion of the core network operation can be performed as a cloud service. When performed remotely from the core network, this can also be referred to as edge computing. The communication system may also include a central control entity that provides facilities for different operators' networks to collaborate, for example, in spectrum sharing.

[0095] Edge computing technologies can be brought into radio access networks (RANs) by leveraging network function virtualization (NVF) and software-defined networking (SDN). Using edge cloud technologies may mean that access node operations will be performed, at least partially, in servers, hosts, or nodes operatively coupled to remote radio heads or base stations (including the radio portion). Alternatively, node operations may be distributed across multiple servers, nodes, or hosts. The application of a cloud RAN architecture enables real-time RAN functions to be performed at or near remote antenna sites (in the distributed unit DU 121 of gNB 120-1), while non-real-time functions are performed centrally (in the centralized unit CU 122 of gNB 120-1).

[0096] It should also be understood that in the future, the labor distribution between core network operations and base station operations may differ from, or even not exist at all, in the 5G standard. Some other technological advancements that may be used are big data and all-IP, which could change how networks are built and managed. 5G (or New Radio) networks are designed to support multiple layers, where edge computing servers can be placed between the core and base stations or nodeBs (gNBs). An example of edge computing is MEC as defined by the European Telecommunications Standards Institute (ETS). It should be understood that MEC (and other edge computing protocols) can also be applied to 4G networks.

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

[0098] Figure 4 The system shown is merely an example of a portion of a radio access system, and in practice, the system can include multiple gNBs. UE 140-1 and UE 140-2 can have access to multiple radio cells, and the system can also include other devices such as physical layer relay nodes or other network elements. At least one gNB can be a home (e / g) NodeB. Additionally, multiple different types of radio cells and multiple radio cells can be provided within the geographical area of ​​the radio communication system. Radio cells can be macrocells (or umbrella cells), which are typically large areas with diameters of tens of kilometers, or small cells such as microcells, femtocells, or picocells. Figure 4 The gNB120-1 can provide any type of these cells. Cellular radio systems can be implemented as multi-layered networks comprising several types of cells.

[0099] Figure 4 The components and / or associated circuitry of the gNB 120-1 shown may also be referred to as “components for transmitting…”, “components for receiving…”, “components for determining…”, etc.

[0100] In the embodiments described below, the terms "(multiple) services" and "(multiple) sessions" are used interchangeably and can refer to either broadcast services or multicast services. For simplicity, (multiple) services / (multiple) sessions should be referred to as (multiple) broadcast services. However, those skilled in the art will understand that this can also refer to (multiple) multicast services.

[0101] In terms of resource usage and power consumption, broadcast operations using the newly introduced RedCapCFR are not optimal for RedCap UEs such as UE 140-2. The embodiments described herein address this issue.

[0102] If the session is intended for both RedCap UE 140-2 and non-RedCap UE 140-1 (which is also described in this document as a normal UE), and the Quality of Service (QoS) is satisfied for both RedCap 140-2 and normal UE 140-1, then it is not necessary to send broadcast-related information in two different CFRs.

[0103] Conversely, broadcast-related information is only sent in the RedCap UE 140-2's CFR, while the normal UE 140-1 monitors the RedCap CFR only when needed. Since the same service is not provided in separate CFRs, this saves spectral efficiency and RAN node power at gNB 120-1. In this scenario, to assist the normal UE 140-1 with RedCap CFR monitoring only when needed, the network can send some indications to the normal UE 140-1 per MBS broadcast session or per Transport Group Identifier (TMGI).

[0104] Services destined for RedCap UEs such as UE 140-2 are sent in the RedCap CFR, and normal UE 140-1 only reads the service when needed. In this way, normal non-RedCap UE 140-1 does not need to monitor two MCCHs.

[0105] The specific services are only available in RedCap CFR. Normal UE 140-1 does not read the RedCap CFR configuration broadcast in the cell (RedCap CFR is broadcast in SIB20 or new SIBx) and does not monitor MCCH sent in RedCap CR.

[0106] According to TMGI, an indication is provided in the normal (non-RedCap) MCCH sent in the broadband CFR, indicating that a specific broadcast service is available in the RedCap CFR. This will instruct normal UE 140-1s interested in that service to read the broadcast RedCap CFR configuration and monitor the RedCap MCCH in the RedCap CFR to receive data.

[0107] Instead of the MCCH, this indication can be found in SIB20. However, the current SIB20 does not include information per TMGI. In addition to the TMGI sent in the RedCap CFR, the list of TMGIs can also be indicated in the normal MCCH sent in the Broadband CFR, instead of the indication per TMGI.

[0108] Alternatively, or otherwise, a normal non-RedCap MCCH can provide RedCap CFR configuration information and RedCap MCCH scheduling information, so that UE 140-1 does not need to monitor the broadcast SIB of RedCap CFF configuration again.

[0109] Alternatively or otherwise, the normal MCCH can provide RedCap CFR information and RedCapMCCH content for the broadcast session, so that UE 140-1 does not need to monitor the SIB and MCCH for RedCap and can start receiving data immediately.

[0110] Using this embodiment, a normal UE 140-1 does not need to monitor RedCap CFR / MCCH.

[0111] Additionally, a general indication can be provided in SIB20 or MCCH, indicating that some services are only sent in the RedCap CFR. If the normal UE 140-1 cannot find the service it is interested in, this will trigger the normal UE 140-1 to start monitoring the RedCap CFR. This can be achieved by the UE 140-1 reading the RedCap SIB20 and monitoring the MCCH used for RedCap.

[0112] Now refer to Figures 5 to 8 The message flow diagrams shown illustrate various embodiments. In the accompanying drawings and throughout the invention, SIBx refers to information provided to a capability-degraded UE within a system information block, where CFR configuration and MCCH configuration are provided. This SIBx may be part of SIB20 or a new SIB.

[0113] Figure 5 An example of the execution of steps 5-1 to 5-11 is shown.

[0114] Step 5-1: Normal (non-RedCap) UE 140-1 is interested in receiving specific MBS broadcast service A (TMGI A).

[0115] Step 5-2: gNB 120-1 sends SIB20 (which may contain both normal CFR configuration and RedCap CFR configuration).

[0116] Step 5-3: Normal UE 140-1 reads SIB20 and learns normal MCCH scheduling information (information on how to receive normal MCCH content).

[0117] Step 5-4: gNB 120-1 sends the MCCH. In addition to the actual MCCH content, it includes information about specific TMGIs (Broadcast Services) that are only available in the RedCap CFR. Alternatively, in addition to the TMGIs sent in the RedCap CFR, a list of TMGIs (Broadcast Services) can also be indicated in the normal MCCH sent in the Broadband CFR.

[0118] Step 5-5: UE 140-1 reads the MCCH and determines that the specific TMGI it is interested in is only available in the RedCap CFR.

[0119] Steps 5-6: The new SIB, represented as SIBx, contains the RedCap CFR configuration. The gNB 120-1 broadcasts SIBx. Alternatively, if step 5-2 already contains SIBx information, step 5-6 can be skipped because Rel-18 will be expanded to include the new RedCap CFR configuration. A normal (non-RedCap) UE can read the SIBx information in step 5-2, and the UE retains it in its memory.

[0120] Steps 5-7: Normal UE 140-1 reads SIBx and learns RedCap MCCH scheduling information (information on how to receive RedCap MCCH content).

[0121] Steps 5-8: gNB 120-1 broadcasts RedCap MCCH.

[0122] Steps 5-9: Normal UE 140-1 reads the RedCap MCCH content and is now ready to receive broadcast TMGI.

[0123] Steps 5-10: gNB 120-1 sends broadcast service A using TMGI in RedCap CFR.

[0124] Step 5-11: Normal UE 140-1 receives broadcast service A identified by TMGI.

[0125] Figure 6 Another embodiment is shown, performed according to steps 6-1 to 6-9.

[0126] Step 6-1: Normal UE 140-1 is interested in receiving specific MBS broadcast services (TMGI).

[0127] Step 6-2: gNB 120-1 sends SIB20.

[0128] Step 6-3: Normal UE 140-1 reads SIB20 and learns MCCH scheduling information (information on how to receive MCCH content).

[0129] Step 6-4: gNB 120-1 sends the MCCH. In addition to the general MCCH content, it includes specific TMGI (Broadcast Service) information available only in the RedCap CFR. It also includes SIBx information.

[0130] Step 6-5: UE 140-1 reads the MCCH and determines that the specific TMGI is only available in the RedCap CFR. Furthermore, UE 140-1 learns the RedCap MCCH scheduling information (how to receive the RedCap MCCH) without needing to check the SIBx information again.

[0131] Step 6-6: gNB 120-1 broadcasts RedCap MCCH.

[0132] Steps 6-7: Normal UE 140-1 reads the RedCap MCCH content and is now ready to receive broadcast TMGI.

[0133] Steps 6-8: gNB 120-1 sends a broadcast TMGI in RedCap CFR.

[0134] Steps 6-9: Normal UE 140-1 receives broadcast TMGI.

[0135] Figure 7 Another embodiment is shown, performed according to steps 7-1 to 7-7.

[0136] Step 7-1: Normal UE 140-1 is interested in receiving specific MBS broadcast services (TMGI).

[0137] Step 7-2: gNB 120-1 sends SIB20.

[0138] Step 7-3: Normal UE 140-1 reads SIB20 and learns MCCH scheduling information (information on how to receive MCCH content).

[0139] Step 7-4: gNB 120-1 sends the MCCH. In addition to the actual MCCH content, it includes information specific to the TMGI (Transmission Television Service) that is only available in the RedCap CFR. The MCCH also includes RedCap CFR information for receiving broadcast TMGIs and the RedCap MCCH content.

[0140] Step 7-5: UE 140-1 reads the MCCH and determines that the specific TMGI is only available in the RedCap CFR. Therefore, UE 140-1 learns how to receive the TMGI without specifically reading the SIBx or RedCap MCCH. Now, a normal UE 140-1 is ready to receive the TMGI.

[0141] Step 7-6: gNB 120-1 sends a broadcast TMGI.

[0142] Step 7-7: Normal UE 140-1 receives broadcast TMGI.

[0143] exist Figure 8 Another embodiment is shown, performed according to steps 8-1 to 8-12.

[0144] Step 8-1: Normal UE 140-1 is interested in receiving specific MBS broadcast services (TMGI).

[0145] Step 8-2: gNB 120-1 sends SIB20.

[0146] Step 8-3: Normal UE 140-1 reads SIB20 and learns MCCH scheduling information (information on how to receive MCCH content).

[0147] Step 8-4: gNB 120-1 sends the MCCH. In addition to the actual MCCH content, the sent MCCH includes information about specific broadcast services available only in the RedCap CFR. This may be a generalized indication or list of TMGIs supported only in the RedCap CFR.

[0148] Step 8-5: UE 140-1 cannot find the broadcast service of interest within the actual normal MCCH. Then, UE 140-1 explains from step 8-4 that some services are only available in the RedCap CFR.

[0149] Step 8-6: gNB 120-1 sends a broadcast service to UE 140-1, but UE 140-1 cannot receive the broadcast service.

[0150] Step 8-7: gNB 120-1 broadcasts SIBx.

[0151] Step 8-8: Normal UE 140-1 reads SIBx information and determines the RedCap MCCH scheduling information (information on how to receive RedCap MCCH).

[0152] Steps 8-9: Send RedCap MCCH from gNB 120-1.

[0153] Steps 8-10: The RedCap MCCH is received by UE 140-1, and UE 140-1 learns how to receive broadcast services.

[0154] Steps 8-11: gNB 120-1 sends a broadcast service.

[0155] Steps 8-12: UE 140-1 receives broadcast services.

[0156] Figure 9A flow diagram depicting a method according to an embodiment is shown. This method can be performed by UE 140-1 or a similar device, or a component of UE 140-1. For simplicity, the method will be described as being performed by a non-RedCap UE 140-1.

[0157] In step 9-1, UE 140-1 determines that the configuration for one or more broadcast or multicast services that a non-RedCap UE is interested in receiving is not provided in the MBS control channel for non-RedCap UEs. UE 140-1 may indicate its interest in receiving a specific broadcast service when it is in the RRC_CONNECTED or RRC_INACTIVE / IDLE state.

[0158] In step 9-2, UE 140-1 receives a message from gNB 120-1 indicating that the broadcast services(s) it is interested in are only available in the common frequency resources used by RedCap UEs (e.g., UE 140-2). This may occur, for example, when UE 140-1 receives an MCCH or SIB from gNB 120-1 containing information that a specific broadcast service of interest to UE 140-1 is only available in the RedCap CFR used by Limited Capacity (RedCap) UEs.

[0159] In step 9-3, UE 140-1 receives information from gNB 120-1. This information includes the configuration of CFR for the RedCap UE, and / or the configuration of the MBS control channel for the RedCap UE, and / or the content of the MBS control channel for the RedCap UE.

[0160] In step 9-4, UE 140-1 receives from gNB 120-1 the CFR configuration for RedCap UE, the MBS control channel configuration for RedCap UE, and the content of the MBS control channel for RedCap UE, which it received from gNB 120-1 in step 9-3. This information (sent by gNB 120-1 in step 9-3) may be sent to UE 120-1 in the SIB (e.g., SIB20 or SIBx mentioned above) and / or MCCH.

[0161] Figure 10 A flow diagram illustrating a method according to an embodiment is shown, which can be performed by gNB 120-1 or a similar device or a component of gNB 120-1. For simplicity, the method will be described as being performed by gNB 120-1.

[0162] In step 10-1, gNB 120-1 provides the following information: the configuration for one or more broadcast / multicast services that the non-RedCap UE 140-1 is interested in receiving is not provided in the MBS control channel for the non-RedCap UE.

[0163] In step 10-2, gNB 120-1 sends a message indicating that the service(s)(s) is available only in the CFR for limited-capacity UEs. For example, gNB 120-1 may send this information in the MCCH or SIB, which contains information that the specific broadcast service of interest to UE140-1 is available only in the RedCap CFR for limited-capacity (RedCap) UEs.

[0164] In step 10-3, gNB 120-1 sends information including the configuration of the CFR for the RedCap UE (such as UR 140-1), and / or the configuration of the MBS control channel for the RedCap UE, and / or the content of the MBS control channel for the RedCap UE. For example, this could be in the RedCap MCCH.

[0165] In step 10-4, gNB 120-1 sends the broadcast services(s) that are of interest to non-RedCap UE 140-1 to UE 140-1.

[0166] Although the invention has been described above with reference to specific embodiments, the invention is not limited to these embodiments, and there is no doubt that those skilled in the art will conceive of other alternatives that are within the scope of the claimed invention.

[0167] The features of each embodiment in the examples may also be combined with features from other embodiments and are not limited to those features described herein.

Claims

1. An apparatus comprising at least one processor and at least one memory, the at least one memory including computer program code, wherein the at least one memory and the computer program code are configured to, together with the at least one processor, enable the apparatus to: The configuration for at least one service that a non-limited capability UE is interested in receiving is not provided in the MBS control channel for the non-limited capability UE; A message is received indicating that the at least one service is available only in public frequency resources for UEs with limited capabilities; Receive information, the information including at least one of the following: configuration of the common frequency resources for the limited capability UE, configuration of the MBS control channel for the limited capability UE, and / or content of the MBS control channel for the limited capability UE; as well as Based on the received information, the at least one service is received.

2. The apparatus of claim 1, wherein the at least one service is received in the public frequency resources for the limited-capability UE.

3. The apparatus according to claim 1 or claim 2, wherein at least a portion of the information is provided in a system information block.

4. The apparatus according to claim 3, wherein the system information block is SIB20.

5. The apparatus of claim 1 or claim 2, wherein at least a portion of the information is provided in the MBS control channel for a capability-degraded UE.

6. The apparatus of claim 5, wherein the MBS control channel is an MCCH.

7. The apparatus of claim 6, wherein the UE learns from the received information how to receive the service on the MCCH for the capability-degraded UE.

8. An apparatus comprising at least one processor and at least one memory, the at least one memory including computer program code, wherein the at least one memory and the computer program code are configured to, together with the at least one processor, cause the apparatus to: The following is sent: The configuration for at least one service that a non-limited capability UE may be interested in receiving is not provided in the MBS control channel for the non-limited capability UE; Send a message indicating that the at least one service is available only in public frequency resources for UEs with limited capabilities; Sending information, the information including at least one of the following: configuration of the common frequency resources for the limited capability UE, configuration of the MBS control channel for the limited capability UE, and / or content of the MBS control channel for the limited capability UE; as well as The at least one service is transmitted in the public frequency resources used for UEs with limited capabilities.

9. An apparatus comprising: Components for determining the configuration for at least one service that a non-limited capability UE is interested in receiving, which are not provided in the MBS control channel for the non-limited capability UE; A component for receiving messages indicating that the at least one service is available only in public frequency resources for UEs with limited capabilities; A component for receiving information, the information including at least one of the following: configuration of the common frequency resources for the limited capability UE, configuration of the MBS control channel for the limited capability UE, and / or content of the MBS control channel for the limited capability UE; as well as A component for receiving the at least one service based on the received information.

10. An apparatus comprising: The component for transmission, used to transmit: configurations for at least one service that a non-limited capability UE may be interested in receiving are not provided in the MBS control channel for the non-limited capability UE; A component for sending a message indicating that the at least one service is available only in public frequency resources for UEs with limited capabilities; A component for transmitting information, the information including at least one of the following: configuration of the common frequency resources for the limited capability UE, configuration of the MBS control channel for the limited capability UE, and / or content of the MBS control channel for the limited capability UE; as well as Components for transmitting the at least one service in the public frequency resources of the UE with limited capacity.

11. The apparatus according to any of the preceding claims, wherein the service is a broadcast service.

12. The apparatus according to any one of claims 1 to 10, wherein the service is a multicast service.

13. A method comprising: The configuration for at least one service that a non-limited capability UE is interested in receiving is not provided in the MBS control channel for the non-limited capability UE; A message is received indicating that the at least one service is available only in public frequency resources for UEs with limited capabilities; Receive information, the information including at least one of the following: configuration of the common frequency resources for the limited capability UE, configuration of the MBS control channel for the limited capability UE, and / or content of the MBS control channel for the limited capability UE; as well as Based on the received information, the at least one service is received.

14. A method comprising: The following is sent: The configuration for at least one service that a non-limited capability UE may be interested in receiving is not provided in the MBS control channel for the non-limited capability UE; Send a message indicating that the at least one service is available only in public frequency resources for UEs with limited capabilities; Sending information, the information including at least one of the following: configuration of the common frequency resources for the limited capability UE, configuration of the MBS control channel for the limited capability UE, and / or content of the MBS control channel for the limited capability UE; as well as The at least one service is transmitted in the public frequency resources of the UE with limited capabilities.

15. A computer program product embodied on a computer-readable distribution medium and comprising program instructions that, when executed by a device, cause the device to perform the method according to claim 13 or claim 14.

16. A computer program product comprising program instructions that, when the program is executed by a device, cause the device to perform the method according to claim 13 or claim 14.

Images