Apparatus, method and computer program product

Abstract

An apparatus comprises 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, with the at least one processor, to cause the apparatus to determine that a configuration for at least one service a non-limited capability UE is interested to receive is not provided in an MBS control channel for the non-limited capability UE, receive a message that the at least one service is only available in a common frequency resource for a limited capability UE, receive information including at least one of a configuration of the 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 receive the at least one service based on the received information.

Description

[0001] APPARATUS, METHOD AND COMPUTER PROGRAM PRODUCT

[0002] FIELD OF THE DISCLOSURE

[0003] The invention generally relates to an apparatus, methods and computer programs, in particular, but not exclusively, for network apparatuses and user equipments (UEs) as parts of communications systems.

[0004] BACKGROUND

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

[0006] The communication system may be a wireless communication system. Examples of wireless communication systems include public land mobile networks (PLMN) operating based on radio standards, for example radio standards provided by 3GPP, satellite-based communication systems and different wireless local networks, for example wireless local area networks (WLAN). The wireless systems can be divided into cells and are often referred to as cellular systems or cellular networks.

[0007] The communication system and associated devices typically operate in accordance with a given standard or specification, which sets out how the various entities associated with system are permitted to perform, how they are allowed to interact with each other and how that should be achieved. Communication protocols and / or parameters that shall be used for the connection(s) within the network are also defined by the standard or specification. As mentioned above, some examples of standards are the radio standards provided by 3GPP, for example 2G, 3G, 4G and 5G. The communication system described herein is based on the 5G standard. However, the described embodiments are not limited to operating according to 5G and may also be applicable to future radio standards, for example 6G.

[0008] SUMMARY

[0009] According to an aspect of the invention, there is provided an apparatus. The apparatus comprises 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, with the at least one processor, to cause the apparatus to determine that a configuration for at least one service a non-limited capability UE is interested to receive is not provided in an MBS control channel for a non-limited capability UE, receive a message that the at least one service is only available in a common frequency resource for a limited capability UE, receive information including at least one of a configuration of the common frequency resource for the limited capability UE, a configuration of an MBS control channel for the limited capability UE, and / or content of the MBS control channel for the limited capability UE, and receive the at least one service based on the received information.

[0010] The service may be a broadcast service or a multicast service.

[0011] The apparatus can be a user equipment (UE), as described herein, or a component thereof. In particular, the apparatus can be non-limited capability UE, otherwise known as a non-reduced capacity UE (non-RedCap UE).

[0012] The at least one service can be received in the common frequency resource for the limited capability UE, which can also be known as a RedCap UE.

[0013] At least part of the information can provided in a system information block, for example the system information block SIB20.

[0014] At least part of the information can alternatively or also be provided in the MBS control channel for a reduced capacity UE. The MBS control channel can be a MCCH. The UE can learn how to receive the service on a MCCH for the reduced capacity UE from the received information.

[0015] Another aspect provides an apparatus. The apparatus comprises 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, with the at least one processor, to cause the apparatus to transmit that a configuration for at least one service a non-limited capability UE may be interested to receive is not provided in an MBS control channel for a non-limited capability UE, transmit a message that the at least one service is only available in a common frequency resource for a limited capability UE, transmit information including at least one of a configuration of the common frequency resource for the limited capability UE, a configuration of an MBS control channel for the limited capability UE, and / or content of the MBS control channel for the limited capability UE, and transmit the at least one broadcast service on the common frequency resource for the limited capability UE

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

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

[0018] Another aspect provides a method, comprising determining that a configuration for at least one service a non-limited capability UE is interested to receive is not provided in an MBS control channel for a non-limited capability UE, receiving a message that the at least one service is only available in a common frequency resource for a limited capability UE, receiving information including at least one of a configuration of the common frequency resource for the limited capability UE, a configuration of an MBS control channel for the limited capability UE, and / or content of the MBS control channel for the limited capability UE, and receiving the at least one service based on the received information.

[0019] In a further aspect there is provided a method. The method comprises transmitting that a configuration for at least one service a non-limited capability UE may be interested to receive is not provided in an MBS control channel for a non-limited capability UE, transmitting a message that the at least one service is only available in a common frequency resource for a limited capability UE, transmitting information including at least a configuration of the common frequency resource for the limited capability UE, a configuration of an MBS control channel for the limited capability UE, and / or content of the MBS control channel for the limited capability UE, and transmitting the at least one broadcast service.

[0020] Another aspect provides a computer program product embodied on a distribution medium readable by a computer and comprising program instructions which, when the program is executed by an apparatus, cause the apparatus to carry out the method according to the described embodiments illustrated in Figures 9 and 10.

[0021] A further aspect provides a computer program product comprising program instructions which, when the program is executed by an apparatus, cause the apparatus to carry out the method according to the embodiments described with reference to Figures 9 and 10.

[0022] In this way, the invention allows for optimal broadcast and multicast operation with a newly introduced RedCap common frequency resources (CFR) in terms of resource usage and power consumption, since a normal non-limited capacity (non- RedCap) UE does not have to receive a service using both wideband and limited CFRs.

[0023] BRIEF DESCRIPTION OF THE FIGURES

[0024] Figure 1 shows a simplified schematic illustration of a 5G network;

[0025] Figure 2 shows a simplified schematic illustration of a user equipment suitable for performing embodiments of the invention;

[0026] Figure 3 schematically shows block diagrams of some examples of non-volatile storage media;

[0027] Figure 4 shows a block diagram of a 5G network including a schematic illustration of a gNodeB suitable for performing embodiments of the invention;

[0028] Figure 5 shows a message flow diagram according to an embodiment;

[0029] Figure 6 shows a message flow diagram according to an embodiment;

[0030] Figure 7 shows a message flow diagram according to an embodiment;

[0031] Figure 8 shows a message flow diagram according to an embodiment;

[0032] Figure 9 shows a flow diagram illustrating a method according to an embodiment; and

[0033] Figure 10 shows a flow diagram illustrating a method according to an embodiment, DETAILED DESCRIPTION

[0034] The following embodiments are exemplary. Although the specification may refer to “an”, “one”, or “some” embodiment(s) in several locations of the text, this does not necessarily mean that each reference is made to the same embodiment(s), or that a particular feature only applies to a single embodiment. Single features of different embodiments may also be combined to provide other embodiments. For the purposes of the present disclosure, the phrases “at least one of A or B”, “at least one of A and B”, “A and / or B” means (A), (B), or (A and B). For the purposes of the present disclosure, the phrases “A or B” and “A and / or B” means (A), (B), or (A and B). For the purposes of the present disclosure, the phrase “A, B, and / or C” means (A), (B), (C), (A and B), (A and C), (B and C), or (A, B, and C).

[0035] It shall be understood that although 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 only used to distinguish one element from another. For example, a first element could be termed a second element, and similarly, a second element could be termed a first element, without departing from the scope of example embodiments.

[0036] 3GPP Rel-17 MBS Wl specifies broadcast reception for user equipment (UE) that can be in IDLE / INACTIVE / CONNECTED RRC states (e.g. RRCJDLE, RRCJNACTIVE, RRC_CONNECTED).

[0037] System Information Block 20 (SIB20) is a message that contains information for the UE to receive the Multicast Control Channel (MCCH) data, including the repetition period and configured transmission / reception window of MCCH. The MCCH data includes control information necessary for the UE to understand the broadcast services provided in the cell and scheduling information to receive the broadcasted data. This information is transmitted periodically by a gNB (gNodeB) with a configurable repetition period and within a configured transmission window. The MCCH provides essential information about the Multicast Traffic Channels (MTCHs), which are the data channels where the broadcast services are provided. This information includes search spaces, Discontinuous Reception (DRX) information, etc. The UE uses this information to receive the relevant MTCH(s). Each Temporary Mobile Group Identity (TMGI), which is an identifier of a specific broadcast service, is mapped to a specific MTCH.

[0038] To receive the MCCH data, the UE reads and decodes the SIB20 message to learn the MCCH configuration / scheduling details. Then the UE reads the MCCH data to learn about the services provided in the cell and their scheduling information. However, for the UEs in RRC_CONNECTED state, the SIB reading is ignored, and the UE is provided with the search space configuration to receive MCCH within PDCCH-ConfigCommon. While in RRCJNACTIVE state, the UE retrieves information from the SIB20 block such as the MCCH repetition scheduling configuration, window duration, and start slot. The MCCH contents and the repetition window of the MCCH do not change within the modification period.

[0039] Rel-17 specifications describe the RRCJNACTIVE / RRCJDLE UE behavior based on the configuration for CORESET#0, initial Bandwidth Part (BWP) and Common Frequency Resources (CFR) for reception of broadcast services. CORESET#0 is where the UE can receive only the control resources. CFR is where the UE can receive MBS control and data transmissions.

[0040] In Rel-17, UEs receiving a broadcast service in RRCJDLE / INACTIVE state can receive the relevant configuration using the following steps:

[0041] • SIB20 includes details on how to receive MCCH (periodicity and offsets) within a given modification period, in addition to the details of CFR configuration. UE first reads the SIB20 to learn about such information.

[0042] • Then, the UE reads MCCH which is transmitted in the CFR. Via reading MCCH, the UE can get to learn about which services are provided in the current cell, along with the necessary configuration how to receive those services.

[0043] • Finally, the UE can receive the broadcast data.

[0044] Note that MCCH and data are to be transmitted in the same CFR.

[0045] Reduced capability (RedCap) devices have bandwidth (BW) limitations. This means that RedCap UEs cannot receive BWs larger than a specific maximum BW they support, e.g., 20MHz. If the initial bandwidth part (BWP) of the system is larger than such limitations, RedCap UEs utilize an initial BWP separately configured by the system information block SIB1 .

[0046] In Rel-17, 3GPP concluded that a RedCap UE can receive broadcast data, if the CFR BW is configured appropriately for a RedCap UE; in other words, if CFR BW is less than or equal to the RedCap UEs’ supported BW No specific MBS enhancements were made for those UEs.

[0047] In Rel-18, some companies proposed to introduce a new lower BW CFR for BW limited UEs like RedCap UEs. However, none of the technical issues, including UE behaviour, were specified. Even if that operation is defined in Rel-18, it will be the baseline understanding, and enhancements are expected to be made in Rel- 19. Companies are inclined towards a baseline solution that does not affect a normal (non-limited capacity or non-RedCap) UE.

[0048] In RAN2#121 , an agreement has been made on introducing a separate broadcast common-frequency resource (CFR) which can be used when the configured bandwidth for the default CFR in SIB20 exceeds the bandwidth capability of bandwidth limited or RedCap UEs. The proposal was made in R2-2300797.

[0049] If two separate CFRs are introduced, one CFR is used for the Redcap UEs and the other CFR is used for the normal UE. The first option is that the legacy or wideband CFR (for non-bandwidth limited or non-RedCap UEs) and the narrowband CFR for RedCap UEs are separate or partially overlapping.

[0050] The wideband or non-RedCap CFR can be separate from the RedCap CFR, or possibly partially overlapping. In this case, “partially overlapping” means they may have some parts in common; for example, the CORESET#0, which is common and overlapping to both the wideband (non-RedCap) and the RedCap CFR. If the two CFRs are partially overlapping, it essentially implies that there will be two separate MCCH corresponding to the two CFR regions, as CORESET#0 contains only the control signaling resources. In that scenario, a normal (non-RedCap) UE would be reading the wideband CFR for broadcast control and data, whereas a RedCap UE would be reading the RedCap CFR. With this configuration, the following scenarios may arise:

[0051] The first option is that non-RedCap UE and the RedCap UE receive the common broadcast service in their respective CFRs. For a common broadcast service targeted at both the non-RedCap UE and the RedCap UE, two individual control and data streams are transmitted in the two different CFRs. The RedCap UE receives control and data in the RedCap CFR, whereas the non-RedCap UE receives control and data in the wideband non-RedCap CFR.

[0052] However, this option would necessitate transmission of the same data / control information twice over the air. As stated above, the baseline operation was defined in Rel-18, and this first option is the outcome for that, as the aim is to not change normal UE (non-limited capacity / non-RedCap) behavior.

[0053] The second option is that both the non-RedCap UE and the RedCap UE receive some part of the common broadcast service only in the RedCap CFR. This could also manifest as a non-RedCap UE reading two MCCHs in a scenario where some part of the common broadcast service data is transmitted by the gNB only in the RedCap CFR region. Therefore, the non-RedCap UE would now have to read both the RedCap and non-RedCap MCCHs to determine the configurations to retrieve broadcast data in the RedCap CFR region. However, with this approach, the non-RedCap UE would always need to monitor two different MCCHs, leading to more power consumption at the UEs. It is important to note that unless the RedCap CFR is restricted for use only by the RedCap UEs, a non-RedCap and a RedCap UE should be able to read the RedCap CFR. However, Rel-17 UEs (be it a non-RedCap or a RedCap UE) will not be able to read the RedCap CFR introduced in Rel-18. This means that as soon as any Rel-17 UE joins the broadcast session, the broadcast data now has to be transmitted within the conventional Rel-17 CFR as described in the previous section.

[0054] From the options above it is clear that from the perspective of normal UEs, reading two MCCHs transmitted in Rel-18 normal CFR and Rel-18 RedCap CFR is not the most optimal strategy. The main objective of the embodiments described herein is to optimize Rel-18 normal UE’s operation in presence of Rel-18 RedCap CFR.

[0055] Another scenario is that the legacy or wideband (non-limited capability or non- RedCap) CFR and RedCap or narrowband CFR overlaps. In this scenario, the two CFR regions are overlapping and therefore we can have a single MCCH transmitted in the common RedCap CFR and wideband CFR overlapped region. The gNB schedules to send the control signalling information within the overlapped CFR region which can be received both by the RedCap UE and normal UE. The drawback of this option is that the MCCH of the non-RedCap UE has to be transmitted within the smaller CFR region of the Redcap UEs. This could be detrimental for the non-RedCap UE, which might have an enhanced CFR requirement for MCCH.

[0056] Hence, broadcast operation when both the non-RedCap CFR and the RedCap CFR are configured is not optimal in terms of resource usage for scheduling the service or power consumption or efficient broadcast reception by non-RedCap UEs. Fig. 1 schematically shows a system 100, according to an exemplary aspect, and in which the embodiments described herein may operate. The system 100 is part of a mobile communications network and comprises a mobile device 130-1 , which may be a terminal device or user equipment (UE) or Internet of Things (loT) device.

[0057] The term “terminal device” or “UE” refers to any end device that may be capable of wireless communication. By way of example rather than limitation, a terminal device may also be referred to as a communication device, user equipment (UE), a Subscriber Station (SS), a Portable Subscriber Station, a Mobile Station (MS), or an Access Terminal (AT). The terminal device may include, but not limited to, a mobile phone, a cellular phone, a smart phone, voice over IP (VoIP) phones, wireless local loop phones, a tablet, a wearable terminal device, a personal digital assistant (PDA), portable computers, desktop computer, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback appliances, vehicle-mounted wireless terminal devices, wireless endpoints, mobile stations, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), USB dongles, smart devices, wireless customer-premises equipment (CPE), an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and / or other wireless devices operating in an industrial and / or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and / or industrial wireless networks, and the like. In the following description, the terms “terminal device”, “communication device”, “terminal”, “user equipment” and “UE” may be used interchangeably.

[0058] For the purposes of this discussion, the part of the network depicted in Figure 1 by the system 100 will be referred to as a 3GPP 5G network. However, this network could be any type of communication network, for example a 3G or 4G network, or it could be a 6G or other future network. Furthermore, the part of the 5G network shown by the system 100 could interact with another network of a different generation, for example a 4G or LTE network, or a 6G or other future network.

[0059] The system 100 further comprises a gNBs 120-1 and 120-2 with corresponding cells 130-1 and 130-2. The gNBs 120-1 , 120-2 are part of a mobile communication network, which may include additional gNBs with corresponding cells.

[0060] Embodiments described herein may be implemented in any mobile communication network or radio system, such as one comprising at least one of the following radio access technologies (RATs): Worldwide Interoperability for Micro-wave Access (WiMAX), Global System for Mobile communications (GSM, 2G), GSM EDGE radio access Network (GERAN), General Packet Radio Service (GRPS), Universal Mobile Telecommunication System (UMTS, 3G) based on basic wideband-code division multiple access (W-CDMA), high-speed packet access (HSPA), Long Term Evolution (LTE), LTE-Advanced, and enhanced LTE (eLTE). Term ‘eLTE’ here denotes the LTE evolution that connects to a 5G core. LTE is also known as evolved UMTS terrestrial radio access (EUTRA) or as evolved UMTS terrestrial radio access network (EUTRAN). A term “resource” may refer to radio resources, such as a physical resource block (PRB), a radio frame, a subframe, a time slot, a subband, a frequency region, a sub-carrier, a beam, etc. The term “transmission” and / or “reception” may refer to wirelessly transmitting and / or receiving via a wireless propagation channel on radio resources.

[0061] The embodiments are not, however, restricted to the systems / RATs given as an example but a person skilled in the art may apply the solution to other communication system s / networks provided with necessary properties. Some examples of a suitable communication networks include a 5G network and / or a 6G network. The 3GPP solution to 5G is referred to as New Radio (NR). 6G is envisaged to be a further development of 5G. NR has been envisaged to use multiple-input-multiple-output (MIMO) multi-antenna transmission techniques, more base stations or nodes than the current network deployments of LTE (a so- called small cell concept), including macro sites operating in co-operation with smaller local area access nodes and perhaps also employing a variety of radio technologies for better coverage and enhanced data rates. 5G will likely be comprised of more than one radio access technology I radio access network (RAT / RAN), each optimized for certain use cases and / or spectrum. 5G mobile communications may have a wider range of use cases and related applications including video streaming, augmented reality, different ways of data sharing and various forms of machine type applications, including vehicular safety, different sensors and real-time control. 5G is expected to have multiple radio interfaces, namely below 6GHz, cm Wave and mmWave, and being integrable with existing legacy radio access technologies, such as the LTE.

[0062] The current architecture in LTE networks is distributed in the radio and centralized in the core network. The low latency applications and services in 5G may require to bring the content close to the radio which leads to local break out and multiaccess edge computing (MEC). 5G enables analytics and knowledge generation to occur at the source of the data. This approach requires leveraging resources that may not be continuously connected to a 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 in close proximity to cellular subscribers for faster response time. Edge computing covers a wide range of technologies such as wireless sensor networks, mobile data acquisition, mobile signature analysis, cooperative distributed peer-to-peer ad hoc networking and processing also classifiable as local cloud / fog computing and grid / mesh computing, dew computing, mobile edge computing, cloudlet, distributed data storage and retrieval, autonomic self-healing networks, remote cloud services, augmented and virtual reality, data caching, Internet of Things (massive connectivity and / or latency critical), critical communications (autonomous vehicles, traffic safety, real-time analytics, time- critical control, healthcare applications). Edge cloud may be brought into RAN by utilizing network function virtualization (NVF) and software defined networking (SDN). Using edge cloud may mean access node operations to be carried out, at least partly, in a server, host or node operationally coupled to a remote radio head or base station comprising radio parts. Network slicing allows multiple virtual networks to be created on top of a common shared physical infrastructure. The virtual networks are then customised to meet the specific needs of applications, services, devices, customers or operators.

[0063] The signals of gNBs 120-1 , 120-2 are observable by the mobile devices or user equipment (UE). The UEs 140-1 , 140-2 are served by the gNB 120-1 within the cell 130-1 . There may be other UEs served by the network shown in Figure 1 , which may be UE / loT devices, e.g. a mobile phone or an autonomously driving vehicle. gNBs 120-1 and 120-2 are connected to each other by an Xn interface, and are each connected to a core network 150 by a NG interface.

[0064] A plurality of different broadcast and / or multicast services (MBS) may be provided by gNB 120-1 in cell 130-1 over Multicast Traffic Channels (MTCH) which are the data channels where the multicast / broadcast services are provided. gNB 120-1 provides information about the Multicast Traffic Channels (MTCHs) by, e.g. periodically, sending Multicast Control Channel (MCCH) messages which contain MTCH information (e.g. service configuration information) for the UEs within cell 130-1 , such as UE 140-1 , to receive the MTCH. The MTCH information may include control information necessary for the UE 140-1 to understand the multicast / broadcast services provided in the cell and scheduling information to receive the multicasted / broadcasted data.

[0065] The MCCH message is transmitted, e.g. periodically, by gNB 120-1 with a configured repetition period and within a configured transmission window. gNB 120-1 provides information about the MCCH by sending SIB20 messages.

[0066] SIB20 contains information (e.g. fallback configuration information) for mobile devices to receive the MCCH data, including the repetition period and configured transmission / reception window of MCCH.

[0067] The UE 140-1 may be in RRCJDLE, RRCJNACTIVE or RRC_CONNECTED state.

[0068] If the UE 140-1 is in RRCJDLE or RRCJNACTIVE state, in order to receive MBS, the UE 140-1 receives a SIB20 message, which is sent by the gNB 120-1. UE 140-1 then decodes the SIB20 message and therewith determines the MCCH configuration / scheduling details (e.g. service configuration set information). Then UE 140-1 receives the MCCH message sent by gNB 120-1 to learn about which MBSs are provided in the cell 140-1 and their scheduling information. The UE 140- 1 is then able to receive the desired MBSs over the respective MTCHs.

[0069] An example of a UE 140-1 , which may be any wireless communication device will now be described in more detail with reference to Figure 2 showing a schematic, partially sectioned view of a communication device 140-1 . An appropriate UE or mobile communication device may be provided by any device capable of sending and receiving radio signals. Non-limiting examples comprise a mobile station (MS) or mobile device such as a mobile phone or what is referred to as a ’smart phone’, a computer provided with a wireless interface card or other wireless interface facility (e.g., USB dongle), personal data assistant (PDA) or a tablet provided with wireless communication capabilities, or any combinations of these or the like. A mobile communication device may provide, for example, communication of data for carrying communications such as voice, electronic mail (email), text message, multimedia and so on. Users may thus be offered and provided numerous services via their communication devices. Non-limiting examples of these services comprise two-way or multi-way calls, data communication or multimedia services or simply an access to a data communications network system, such as the Internet. Users may also be provided broadcast or multicast data. Non-limiting examples of the content comprise downloads, television and radio programs, videos, advertisements, various alerts and other information. The UE 140-1 may be for example a mobile device, that is, a device not fixed to a particular location, or it may be a stationary device. The wireless device may need human interaction for communication, or may not need human interaction for communication. As described herein, the terms UE or “user” are used to refer to any type of wireless communication device.

[0070] In this discussion UE 140-1 is a non-RedCap UE, able to read a wideband or legacy CFR, whereas UE 140-2 is a RedCap UE of the type described above, which can only read a RedCap CFR. The structure of the RedCap UE 140-2 is however, to all intents and purposes the same as the UE 140-1 shown in Figure 2.

[0071] The UE 140-1 may receive signals over an air or radio interface 201 via appropriate apparatus for receiving and may transmit signals via appropriate apparatus for transmitting radio signals. In Figure 2, a transceiver apparatus is designated schematically by block 202. The transceiver apparatus 202 may be provided, for example, by means of a radio part and associated antenna arrangement. The antenna arrangement may be arranged internally or externally to the wireless device.

[0072] The 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 use in software and hardware aided execution of tasks it is designed to perform, including control of access to and communications with access systems and other communication devices. The data processing, storage and other relevant control apparatus can be provided on an appropriate circuit board and / or in chipsets. This feature is denoted by reference 206. The user may control the operation of the wireless device by means of a suitable user interface such as keypad 207, voice commands, touch sensitive screen or pad, combinations thereof or the like. A display 208, a speaker and a microphone can be also provided. Furthermore, a wireless communication device may comprise appropriate connectors (either wired or wireless) to other devices and / or for connecting external accessories, for example hands-free equipment, thereto. The components of the UE 140-1 shown in Figure 2 and / or their associated circuitry may also be known as “means for receiving...”, “means for transmitting...”, “means for determining...”, etc.

[0073] Figure 3 shows a schematic representation of non-volatile memory media 300a (e.g. computer disc (CD) or digital versatile disc (DVD)) and 300b (e.g. universal serial bus (USB) memory stick) storing instructions and / or parameters 304 which when executed by a processor allow the processor to perform one or more of the steps of the methods of Figure 5 and / or Figure 6 and / or Figure 7 and / or Figure 8, and / or Figure 9, and / or Figure 10, and / or methods otherwise described previously.

[0074] As provided herein, various aspects are described in the detailed description of examples and in the claims. In general, some examples may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. For example, some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device, although examples are not limited thereto. While various examples may be illustrated and described as block diagrams, flow charts, or using some other pictorial representation, it is well understood that these blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.

[0075] The examples may be implemented by computer software stored in a memory and executable by at least one data processor of the involved entities or by hardware, or by a combination of software and hardware. Further in this regard it should be noted that any procedures, e.g., as in Figure 5 and / or Figure 6 and / or Figure 7, and / or Figure 8, and / or Figure 9, and / or Figure 10, and / or otherwise described previously, may represent program steps, or interconnected logic circuits, blocks and functions, or a combination of program steps and logic circuits, blocks and functions. The software may be stored on such physical media as memory chips, or memory blocks implemented within the processor, magnetic media (such as hard disk or floppy disks), and optical media (such as for example DVD and the data variants thereof, CD, and so forth).

[0076] The memory may be of any type suitable to the local technical environment and may 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 processors may be of any type suitable to the local technical environment, and may include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs), application specific integrated circuits, gate level circuits and processors based on multicore processor architecture, as nonlimiting examples.

[0077] Additionally or alternatively, some examples may be implemented using circuitry. The circuitry may be configured to perform one or more of the functions and / or method steps previously described. That circuitry may be provided in the base station and / or in the communications device and / or in a core network entity.

[0078] As used in this application, the term “circuitry” may refer to one or more or all of the following:

[0079] (a) hardware-only circuit implementations (such as implementations in only analogue and / or digital circuitry);

[0080] (b) combinations of hardware circuits and software, such as:

[0081] (i) a combination of analogue and / or digital hardware circuit(s) with software / firmware and

[0082] (ii) any portions of hardware processor(s) with software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as the communications device or base station to perform the various functions previously described; and (c) hardware circuit(s) and or processor(s), such as a microprocessor(s) or a portion of a microprocessor(s), that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation.

[0083] This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also covers, for example integrated device.

[0084] The foregoing description has provided by way of non-limiting examples a full and informative description of some examples. However, various modifications and adaptations may become apparent to those skilled in the relevant arts in view of the foregoing description, when read in conjunction with the accompanying drawings and the claims. However, all such and similar modifications of the teachings will still fall within the scope of the claims.

[0085] In the above, different examples are described using, as an example of an access architecture to which the described techniques may be applied, a radio access architecture based on long term evolution advanced (LTE Advanced, LTE-A) or new radio (NR, 5G), without restricting the examples to such an architecture, however. The examples may also be applied to other kinds of communications networks having suitable means by adjusting parameters and procedures appropriately. Some examples of other options for suitable systems are the universal mobile telecommunications system (UMTS) radio access network (UTRAN), wireless local area network (WLAN or WiFi), worldwide interoperability for microwave access (WiMAX), Bluetooth®, personal communications services (PCS), ZigBee®, wideband code division multiple access (WCDMA), systems using ultra-wideband (UWB) technology, sensor networks, mobile ad-hoc networks (MANETs) and Internet Protocol multimedia subsystems (IMS) or any combination thereof. Figure 5 shows examples of simplified system architectures only showing some elements and functional entities, all being logical units, whose implementation may differ from what is shown. The connections shown in Figure 5 are logical connections; the actual physical connections may be different. It is apparent to a person skilled in the art that the system typically comprises also other functions and structures than those shown in Figure 5.

[0086] The examples are not, however, restricted to the system given as an example but a person skilled in the art may apply the solution to other communication systems provided with necessary properties.

[0087] The example of Figure 5 shows a part of an exemplifying radio access network. For example, the radio access network may support sidelink communications described below in more detail.

[0088] Figure 4 shows UEs 140-1 and 140-2. The UEs 140-1 , 140-2 are configured to be in a wireless connection on one or more communication channels with the gNB 120-1 . The gNB 120-1 is further connected to a core network 150. For the purposes of this discussion, the node 120-1 is a gNB serving UEs 140-1 , 140-2 in a cell. However, the node 120-1 may also be LTE eNB or even a non-3GPP access node. The physical link from a UE to a gNB is called uplink or reverse link and the physical link from the gNB to the UE is called downlink or forward link. It should be appreciated that gNBs or their functionalities may be implemented by using any node, host, server or access point etc. entity suitable for such a usage.

[0089] A communications system typically comprises more than one gNB, as shown in Figure 1 , in which case the gNBs may also be configured to communicate with one another over links, wired or wireless, designed for the purpose, for example a Xn interface. These links may be used for signalling purposes. The gNB 120-1 is a computing device configured to control the radio resources of communication system it is coupled to. The gNB may also be referred to as a base station, an access point or any other type of interfacing device including a relay station capable of operating in a wireless environment. The gNB includes or is coupled to transceivers. From the transceivers of the gNB, a connection is provided to an antenna unit that establishes bi-directional radio links to devices. The antenna unit may comprise a plurality of antennas or antenna elements. The gNB 120-1 is further connected to the core network 150 (CN or next generation core NGC). Depending on the deployed technology, the gNB is connected to a 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 of devices to one or more external packet data networks, and to a mobile management entity (MME) or access mobility management function (AMF), for controlling access and mobility of the devices (UEs).

[0090] Examples of a UE device 140-1 , 140-2 are a subscriber unit, a user device, a user equipment (UE), a user terminal, a terminal device, a mobile station, a mobile device, etc.

[0091] The UE device typically refers to a mobile or static device (e.g. a portable or nonportable computing device) that includes wireless mobile communication devices operating with or without an universal subscriber identification module (USIM), including, but not limited to, the following types of devices: mobile phone, smartphone, personal digital assistant (PDA), handset, device using a wireless modem (alarm or measurement device, etc.), laptop and / or touch screen computer, tablet, game console, notebook, and multimedia device. It should be appreciated that a device may also be a nearly exclusive uplink only device, of which an example is a camera or video camera loading images or video clips to a network. A device may also be a device having capability to operate in Internet of Things (loT) network which is a scenario in which objects are provided with the ability to transfer data over a network without requiring human-to-human or human-to-computer interaction, e.g. to be used in smart power grids and connected vehicles. The device may also utilise cloud. In some applications, a device may comprise a user portable device with radio parts (such as a watch, earphones or eyeglasses) and the computation is carried out in the cloud.

[0092] The UEs 140-1 , 140-2 illustrates one type of an apparatus to which resources on the air interface are allocated and assigned, and thus any feature described herein with a device may be implemented with a corresponding apparatus, such as a relay node. An example of such a relay node is a layer 3 relay (self-backhauling relay) towards the base station. The device (or, in some examples, a layer 3 relay node) is configured to perform one or more of user equipment functionalities.

[0093] Various techniques described herein may also be applied to a cyber-physical system (CPS) (a system of collaborating computational elements controlling physical entities). CPS may enable the implementation and exploitation of massive amounts of interconnected information and communications technology, ICT, devices (sensors, actuators, processors microcontrollers, etc.) embedded in physical objects at different locations. Mobile cyber physical systems, in which the physical system in question has inherent mobility, are a subcategory of cyberphysical systems. Examples of mobile physical systems include mobile robotics and electronics transported by humans or animals.

[0094] Additionally, although the apparatuses have been depicted as single entities, different units, processors and / or memory units (not all shown in Figure 4) may be implemented.

[0095] 5G enables using multiple input - multiple output (MIMO) antennas, many more base stations or nodes than the LTE (a so-called small cell concept), including macro sites operating in co-operation with smaller stations and employing a variety of radio technologies depending on service needs, use cases and / or spectrum available. 5G mobile communications supports a wide range of use cases and related applications including video streaming, augmented reality, different ways of data sharing and various forms of machine type applications (such as (massive) machine-type communications (mMTC), including vehicular safety, different sensors and real-time control). 5G is expected to have multiple radio interfaces, e.g. below 6GHz or above 24 GHz, cm Wave and mmWave, and also being integrable with existing legacy radio access technologies, such as the LTE. Integration with the LTE may be implemented, at least in the early phase, as a system, where macro coverage is provided by the LTE and 5G radio interface access comes from small cells by aggregation to the LTE. In other words, 5G is planned to support both inter-RAT operability (such as LTE-5G) and inter-RI operability (inter-radio interface operability, such as below 6GHz - cm Wave, 6 or above 24 GHz - cm Wave and mmWave). One of the concepts considered to be used in 5G networks is network slicing in which multiple independent and dedicated virtual sub-networks (network instances) may be created within the same infrastructure to run services that have different requirements on latency, reliability, throughput and mobility.

[0096] The LTE network architecture is fully distributed in the radio and fully centralized in the core network. The low latency applications and services in 5G require to bring the content close to the radio which leads to local break out and multi-access edge computing (MEC). 5G enables analytics and knowledge generation to occur at the source of the data. This approach requires leveraging resources that may not be continuously connected to a 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 in close proximity to cellular subscribers for faster response time. Edge computing covers a wide range of technologies such as wireless sensor networks, mobile data acquisition, mobile signature analysis, cooperative distributed peer-to-peer ad hoc networking and processing also classifiable as local cloud / fog computing and grid / mesh computing, dew computing, mobile edge computing, cloudlet, distributed data storage and retrieval, autonomic self-healing networks, remote cloud services, augmented and virtual reality, data caching, Internet of Things (massive connectivity and / or latency critical), critical communications (autonomous vehicles, traffic safety, real-time analytics, time-critical control, healthcare applications). The communication system via the gNB 120-1 is also able to communicate with other networks 160, such as a public switched telephone network, or a VoIP network, or the Internet, or a private network, or utilize services provided by them. The communication network may also be able to support the usage of cloud services, for example at least part of core network operations may be carried out as a cloud service. This may also be referred to as Edge computing when performed away from the core network. The communication system may also comprise a central control entity, or a like, providing facilities for networks of different operators to cooperate for example in spectrum sharing.

[0097] The technology of Edge computing may be brought into a radio access network (RAN) by utilizing network function virtualization (NFV) and software defined networking (SDN). Using the technology of edge cloud may mean access node operations to be carried out, at least partly, in a server, host or node operationally coupled to a remote radio head or base station comprising radio parts. It is also possible that node operations will be distributed among a plurality of servers, nodes or hosts. Application of cloudRAN architecture enables RAN real time functions being carried out at or close to a remote antenna site (in a distributed unit, DU 121 of the gNB 120-1) and non-real time functions being carried out in a centralized manner (in a centralized unit, CU 122 of the gNB 120-1 ).

[0098] It should also be understood that the distribution of labour between core network operations and base station operations may in future differ from that of the 5G standard or even be non-existent. Some other technology advancements probably to be used are Big Data and all-IP, which may change the way networks are being constructed and managed. 5G (or new radio, NR) networks are being designed to support multiple hierarchies, where Edge computing servers can be placed between the core and the base station or nodeB (gNB). One example of Edge computing is MEC, which is defined by the European Telecommunications Standards Institute. It should be appreciated that MEC (and other Edge computing protocols) can be applied in 4G networks as well. 5G may also utilize satellite communication to enhance or complement the coverage of 5G service, for example by providing backhauling. Possible use cases are providing service continuity for machine-to-machine (M2M) or Internet of Things (loT) devices or for passengers on board of vehicles, Mobile Broadband, (MBB) or ensuring service availability for critical communications, and future railway / maritime / aeronautical communications. Satellite communication may utilise geostationary earth orbit (GEO) satellite systems, but also low earth orbit (LEO) satellite systems, in particular mega-constellations (systems in which hundreds of (nano)satellites are deployed). Each satellite in the mega-constellation may cover several satellite-enabled network entities that create on-ground cells. The on- ground cells may be created through an on-ground relay node or by a gNB located on-ground or in a satellite.

[0099] The system shown in Figure 4 is only an example of a part of a radio access system and in practice, the system may comprise a plurality of gNBs, the UEs 140-1 , 140-2 may have an access to a plurality of radio cells and the system may comprise also other apparatuses, such as physical layer relay nodes or other network elements, etc. At least one of the gNBs may be a Home(e / g)nodeB. Additionally, in a geographical area of a radio communication system a plurality of different kinds of radio cells as well as a plurality of radio cells may be provided. Radio cells may be macro cells (or umbrella cells) which are large cells, usually having a diameter of up to tens of kilometers, or smaller cells such as micro-, femto- or picocells. The gNB 120-1 of Figure 4 may provide any kind of these cells. A cellular radio system may be implemented as a multilayer network including several kinds of cells.

[0100] The components of the gNB 120-1 shown in Figure 4 and / or associated circuitry may also be known as “means for transmitting...”, “means for receiving...”, “means for determining...”, etc. In the embodiments described below, the words “service(s)” and “session(s)” are used interchangeably and can be either broadcast or multicast services. For simplicity, the service(s) / session(s) shall be called broadcast service(s). However, the skilled person will understand that this can also refer to multicast service(s).

[0101] Broadcast operation with a newly introduced RedCap CFR for the RedCap UEs such as UE 140-2 is not optimal in terms of resource usage and power consumption. This problem is addressed by the embodiments described herein. In case the session is intended for both RedCap UE 140-2 and non-RedCap UE 140-1 , which will also be described herein as a normal UE, and Quality of Service (QoS) is met for both the Redcap 140-2 and normal UE 140-1 , there is no need to transmit broadcast related information in two different CFRs.

[0102] Instead, broadcast related information is only transmitted in the CFR for the Redcap UE 140-2 and the normal UE 140-1 just monitors the RedCap CFR when needed. This saves spectral efficiency and RAN node power at the gNB 120-1 , due to not providing the same service in separate CFRs. In this case, in order to assist the normal UE 140-1 with RedCap CFR monitoring only when needed, the network can transmit the normal UE 140-1 some indications per MBS broadcast session or per transmission group identifier (TMGI).

[0103] A service to RedCap UEs such as UE 140-2 is transmitted in RedCap CFR and normal UE 140-1 only reads that if needed. In this way, the normal non-RedCap UE 140-1 does not need to monitor 2 MCCHs.

[0104] A specific service is provided in the RedCap CFR only. The normal UE 140-1 does not read the RedCap CFR configuration that is broadcast in the cell (RedCap CFR is broadcast either in SIB20 or a new SIBx) and does not monitor the MCCH transmitted in the RedCap CFR.

[0105] Per TMGI, an indication is provided in a normal (non-RedCap) MCCH transmitted in the wideband CFR, indicating that a particular broadcast service is available in 1

[0106] RedCap CFR. This will guide the normal UE 140-1 interested in the service to read the broadcast RedCap CFR config and monitor the RedCap MCCH in the RedCap CFR to receive the data.

[0107] Instead of the MCCH, such an indication could be in SIB20. However, currently SIB20 does not include per TMGI information. Rather than a per TMGI indication, a list of TMGls can be indicated in the -normal MCCH transmitted in the wideband CFR, apart from the TMGls transmitted in the RedCap CFR.

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

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

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

[0111] Furthermore, a general indication in SIB20 or MCCH can be provided, indicating that some services can be transmitted only in RedCap CFR. This triggers the normal UE 140-1 to start monitoring the RedCap CFR if it cannot find the service that it is interested in. This can be achieved by the UE 140-1 reading the SIB20 of RedCap and monitoring the MCCH for RedCap.

[0112] The various embodiments will now be described with reference to the message flow diagrams shown in Figures 5 to 8. In the figures, and also throughout the invention, SIBx refers to the information provided in System Information Block for the Reduced Capability UEs, where CFR configuration and MCCH configuration are provided. Such SIBx could be a part of SIB20 or a new SIB.

[0113] Figure 5 shows an embodiment carried out by Steps 5-1 - 5-11 .

[0114] Step 5-1 : A normal (non-RedCap) UE 140-1 is interested to receive a specific MBS broadcast service A (TMGI A).

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

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

[0117] Step 5-4: gNB 120-1 transmits the MCCH. In addition to actual MCCH contents, it also includes information that a specific TMGI (broadcast service) is available only in RedCap CFR. Alternatively, a list of TMGls (broadcast services) can be indicated in the normal MCCH transmitted in the wideband CFR apart from the TMGls transmitted in RedCap CFR.

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

[0119] Step 5-6: A new SIB denoted as SIBx contains RedCap CFR configuration. The gNB 120-1 broadcasts SIBx. Alternatively, Step 5-6 can be skipped, if step 5-2 already contains SIBx information, since Rel-18 will be extended to contain the new RedCap CFR configuration. A normal (non-RedCap) UE can read the SIBx information in step 5-2 and UE keeps that in its memory.

[0120] Step 5-7: Normal UE 140-1 reads the SIBx and learns the RedCap MCCH scheduling information (information on how to receive RedCap MCCH contents). Step 5-8: gNB 120-1 broadcasts the RedCap MCCH.

[0121] Step 5-9: Normal UE 140-1 reads the RedCap MCCH contents and is now ready the receive the broadcast TMGI.

[0122] Step 5-10: gNB 120-1 transmits the broadcast service A with TMGI in RedCap CFR.

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

[0124] Figure 6 shows another embodiment, which is carried out according to Steps 6-1 to 6-9.

[0125] Step 6-1 : The normal UE 140-1 is interested to receive a specific MBS broadcast service (TMGI).

[0126] Step 6-2: gNB 120-1 transmits the SIB20.

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

[0128] Step 6-4: gNB 120-1 transmits the MCCH. In addition to general MCCH contents, it also includes information that a specific TMGI (broadcast service) is available only in RedCap CFR. It also includes the SIBx information.

[0129] Step 6-5: UE 140-1 reads the MCCH and determines that the specific TMGI is available only in RedCap CFR. Furthermore, it also learns RedCap MCCH scheduling information (how to receive the RedCap MCCH) without checking the SIBx information again. Step 6-6: gNB 120-1 broadcasts the RedCap MCCH.

[0130] Step 6-7: Normal UE 140-1 reads the RedCap MCCH contents and is now ready the receive the broadcast TMGI.

[0131] Step 6-8: gNB 120-1 transmits the broadcast TMGI in RedCap CFR.

[0132] Step 6-9: Normal UE 140-1 receives the broadcast TMGI.

[0133] Figure 7 shows another embodiment, which is carried out according to steps 7-1 to 7-7.

[0134] Step 7-1 : Normal UE 140-1 is interested to receive a specific MBS broadcast service (TMGI).

[0135] Step 7-2: gNB 120-1 transmits the SIB20.

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

[0137] Step 7-4: gNB 120-1 transmits the MCCH. In addition to actual MCCH contents, it also includes information that a specific TMGI (broadcast service) is available only in RedCap CFR. The MCCH also includes RedCap CFR information and RedCap MCCH content to receive the broadcast TMGI.

[0138] Step 7-5: UE 140-1 reads the MCCH and determines that the specific TMGI is available only in the RedCap CFR. UE 140-1 thus learns how to receive the TMGI without reading the SIBx or RedCap MCCH exclusively. Now the normal UE 140-1 is ready to receive the TMGI. Step 7-6: gNB 120-1 transmits the broadcast TMGI.

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

[0140] A further embodiment is shown in Figure 8, which is carried out according to steps 8-1 to 8-12.

[0141] Step 8-1 : Normal UE 140-1 is interested to receive a specific MBS broadcast service (TMGI).

[0142] Step 8-2: gNB 120-1 transmits the SIB20.

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

[0144] Step 8-4: gNB 120-1 transmits MCCH. In addition to actual MCCH contents, the transmitted MCCH also includes information that some specific broadcast services are available only in RedCap CFR. This could be a generalized indication or list of TMGls which are supported only in RedCap CFR.

[0145] Step 8-5: UE 140-1 is unable to find its interested broadcast service within the actual normal MCCH . It then interprets from Step 8-4 that some services are available only in RedCap CFR.

[0146] Step 8-6: gNB 120-1 transmits the broadcast service to the UE 140-1 but the UE 140-1 is unable to receive it.

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

[0148] Step 8-8: UE 140-1 reads the SIBx information and determines the scheduling information of the RedCap MCCH (information on how to receive the RedCap MCCH). Step 8-9: RedCap MCCH is transmitted from gNB 120-1.

[0149] Step 8-10: RedCap MCCH is received by the UE 140-1 and the UE 140-1 learns how to receive the broadcast service.

[0150] Step 8-11 : The gNB 120-1 transmits the broadcast service.

[0151] Step 8-12: The UE 140-1 receives the broadcast service.

[0152] Figure 9 shows a flow diagram depicting method according to an embodiment. The method can be performed by the UE 140-1 or similar apparatus, or a component of the UE 140-1 . For simplicity, the method will be described here as performed by the non-RedCap UE 140-1 .

[0153] In step 9-1 , the UE 140-1 determines that a configuration for one or more broadcast or multicast services, which it, a non-RedCap UE, is interested to receive is not provided in the MBS control channel for a non-RedCap UE. The UE 140-1 can indicate its interest in receiving a particular broadcast service while it is in RRC_CONNECTED or in RRCJNACTIVE / IDLE states.

[0154] In step 9-2, the UE 140-1 receives a message from the gNB 120-1 that the broadcast service(s) it is interested in is only available in a common frequency resource for a RedCap UE, for example the UE 140-2. This can happen, for example, when the UE 140-1 receives an MCCH or SIB from the gNB 120-1 containing information that the particular broadcast service it is interested in is only available in a RedCap CFR for limited capacity (RedCap) UEs.

[0155] In step 9-3, the UE 140-1 receives information from the gNB 120-1. This information includes a configuration of the CFR for RedCap UEs, and / or a configuration of an MBS control channel for the RedCap UE, and / or content of the MBS control channel for the RedCap UE. In step 9-4, the UE 140-1 receives the broadcast service(s) it is interested in from the gNB 120-1 based on the configuration of the CFR for RedCap UEs, the configuration of an MBS control channel for the RedCap UE, and content of the MBS control channel for the RedCap UE, which it received from the gNB 120-1 in step 9-3. This information (sent by the gNB 120-1 in step 9-3) can be sent to the UE 120-1 in a SIB, for example the SIB20 or SIBx described above and / or in the MCCH.

[0156] Figure 10 shows a flow diagram representing a method according to an embodiment, which can be performed by the gNB 120-1 or similar apparatus, or a component of the gNB 120-1 . For simplicity, the method will be described as being performed by the gNB 120-1 .

[0157] In step 10-1 the gNB 120-1 provides information that a configuration for one or more broadcast / multicast services that the non-RedCap UE 140-1 is interested to receive is not provided in an MBS control channel for a non-RedCap UE.

[0158] In step 10-2, the gNB 120-1 transmits a message that the service(s) is only available in a CFR for a limited capability UE. The gNB 120-1 can transmit this information, for example, in an MCCH or SIB containing information that the particular broadcast service the UE 140-1 is interested in is only available in a RedCap CFR for limited capacity (RedCap) UEs.

[0159] In step 10-3, the gNB 120-1 transmits information including a configuration of the CFR for RedCap UEs, such as UE 140-1 , and / or a configuration of an MBS control channel for the RedCap UE, and / or content of the MBS control channel for the RedCap UE. This can be in the RedCap MCCH, for example.

[0160] In step 10-4, the gNB 120-1 transmits the broadcast service(s) to the UE 140-1 that the non-RedCap UE 140-1 is interested in.

[0161] Although the invention has been described hereinabove with reference to specific embodiments, it is not limited to these embodiments, and no doubt further alternatives will occur to the skilled person, which lie within the scope of the invention as claimed.

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

Claims

CLAIMS1 . An apparatus, comprising 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, with the at least one processor, to cause the apparatus to: determine that a configuration for at least one service which a nonlimited capability UE is interested to receive is not provided in an MBS control channel for the non-limited capability UE; receive a message that the at least one service is only available in a common frequency resource for a limited capability UE; receive information including at least one of a configuration of the common frequency resource for the limited capability UE, a configuration of an MBS control channel for the limited capability UE, and / or a content of the MBS control channel for the limited capability UE; and receive the at least one service based on the received information.

2. The apparatus according to claim 1 , wherein the at least one service is received in the common frequency resource for the limited capability UE.

3. The apparatus according to claim 1 or claim 2, wherein at least part 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 according to claim 1 or claim 2, wherein at least part of the information is provided in the MBS control channel for a reduced capability UE.

6. The apparatus according to claim 5, wherein the MBS control channel is a MCCH.

7. The apparatus according to claim 6, wherein the UE learns how to receive the service on a MCCH for the reduced capability UE from the received information.

8. An apparatus, comprising 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, with the at least one processor, to cause the apparatus to: transmit that a configuration for at least one service which a nonlimited capability UE may be interested to receive is not provided in an MBS control channel for the non-limited capability UE; transmit a message that the at least one service is only available in a common frequency resource for a limited capability UE; transmit information including at least one of a configuration of the common frequency resource for the limited capability UE, a configuration of an MBS control channel for the limited capability UE, and / or content of the MBS control channel for the limited capability UE; and transmit the at least one service in the common frequency resource for a limited capability UE.

9. An apparatus, comprising: means for determining that a configuration for at least one service which a non-limited capability UE is interested to receive is not provided in an MBS control channel for the non-limited capability UE; means for receiving a message that the at least one service is only available in a common frequency resource for a limited capability UE;means for receiving information including at least one of a configuration of the common frequency resource for the limited capability UE, a configuration of an MBS control channel for the limited capability UE, and / or content of the MBS control channel for the limited capability UE; and means for receiving the at least one service based on the received information.

10. An apparatus, comprising: means for transmitting that a configuration for at least one service a nonlimited capability UE may be interested to receive is not provided in an MBS control channel for the non-limited capability UE; means for transmitting a message that the at least one service is only available in a common frequency resource for a limited capability UE; means for transmitting information including at least one of a configuration of the common frequency resource for the limited capability UE, a configuration of an MBS control channel for the limited capability UE, and / or content of the MBS control channel for the limited capability UE; and means for transmitting the at least one service in the common frequency resource for the limited capability UE.11 . The apparatus according to any preceding claim, wherein the service is a broadcast service.

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

13. A method, comprising: determining that a configuration for at least one service a non-limited capability UE is interested to receive is not provided in an MBS control channel for the non-limited capability UE;receiving a message that the at least one service is only available in a common frequency resource for a limited capability UE; receiving information including at least one of a configuration of the common frequency resource for the limited capability UE, a configuration of an MBS control channel for the limited capability UE, and / or content of the MBS control channel for the limited capability UE; and receiving the at least one service based on the received information.

14. A method, comprising: transmitting that a configuration for at least one service a non-limited capability UE may be interested to receive is not provided in an MBS control channel for the non-limited capability UE; transmitting a message that the at least one service is only available in a common frequency resource for a limited capability UE; transmitting information including at least one of a configuration of the common frequency resource for the limited capability UE, a configuration of an MBS control channel for the limited capability UE, and / or content of the MBS control channel for the limited capability UE; and transmitting the at least one service in the common frequency resource for the limited capability UE.

15. A computer program product embodied on a distribution medium readable by a computer and comprising program instructions which, when the program is executed by an apparatus, cause the apparatus to carry out the method according to claim 13 or claim 14.

16. A computer program product comprising program instructions which, when the program is executed by an apparatus, cause the apparatus to carry out the method according to claim 13 or claim 14.

Images