UE, network node and methods for handling an MBS broadcast session

Abstract

This disclosure relates to a method performed by a user equipment, UE, (105) for handling a Multicast Broadcast Service, MBS, broadcast session in a communications system (100) The UE obtains (302, 407, 410, 412) a broadcasted MBS broadcast session from a network node (101).

Description

UE, NETWORK NODE AND METHODS FOR HANDLING AN MBS BROADCAST SESSION TECHNICAL FIELD

[0001] The present disclosure relates generally to a network node, a method performed by the network node, a User Equipment (UE) and a method performed by the UE.

[0002] More particularly the present disclosure relates to handling Multicast Broadcast Service (MBS) broadcast sessions in a communications system.

[0003] The present disclosure relates to a method for scheduling restrictions with Reduced Capability (RedCap) Common Frequency Resources (CFR) and Extra Reduced Capability (eRedCap) UEs. BACKGROUND

[0004] MBS broadcast procedure

[0005] MBS may be described as a service for delivering the data to all UEs within a certain area. An MBS session may be either a multicast session or a broadcast session.

[0006] Via service announcement in the higher layers, the UE supporting MBS broadcast may receive information about the MBS broadcast sessions, e.g. Temporary Mobile Group Identity (TMGI) identifying the MBS broadcast session comprising start time, stop time, frequency where the session can be received. The UE stores this information in the User Service Description (USD). The UE can use this information when to try to receive the session and reselect to the frequency. Via Operation And Maintenance (OAM) protocol, the network node, e.g. a base station such as a gNode B (gNB), can be configured on which frequency(ies) MBS sessions can be received.

[0007] A UE supporting MBS broadcast, can receive MBS broadcast sessions in all Radio Resource Control (RRC) states. When the UE transits to RRC_CONNECTED, the UE can indicate via MBSInterestIndication (MMI) message, which MBS broadcast sessions the UE is interested to receive. The UE is able to receive MBS broadcast on Primary Cell (PCell), and optionally on the Secondar Cell (SCell) based on UE capability signalling. The information in the MMI message enables the network node to configure the UE properly in RRC_CONNECTED with respect to PCell / SCell. While the UE is in RRC_IDLE and / or RRC_INACTIVE, the network node does not know if the UEs in the cell are interested in and / or receiving MBS broadcast sessions.

[0008] Certain UE types operate in Receive Only Mode (ROM), e.g. UEs receiving TV services using MBS broadcast. For ROM devices a separate Temporary Mobile Group Identity (TMGI) value range has been standardised, identifying that the MBS broadcast session is intended for ROM devices, see section 6.3 in TS 24.116 [3].

[0009] MBS broadcast and Common Frequency Resources (CFR)

[0010] To receive MBS broadcast the concept of Common Frequency Resources (CFR) is used, see TS 38.300 [1]. A CFR is an “MBS frequency region” with a number of contiguous Physical Resource Blocks (PRB) where the UE can receive MBS broadcast. It has the same numerology as CORESET0 and the broadcast scheduling may have specific characteristics, e.g., Physical downlink control channel (PDCCH) and Physical Downlink Shared Channel (PDSCH) configuration. CORESET is short for Control REsourceSET.

[0011] RedCap UEs and RedCap CFR

[0012] A Reduced Capability (RedCap) UE is a UE with reduced capabilities. A RedCap UE has bandwidth restrictions e.g. to receive MBS broadcast. The maximum bandwidth is 20 MHz for Frequency Range 1 (FR1) and 100 MHz for Frequency Range 2 (FR2) for RedCap UEs. If the bandwidth of the default CFR exceeds the RedCap UE capability, the network node can configure an additional RedCap CFR to enable RedCap UEs to receive MBS broadcast. The bandwidth configured in LocationAndBandwidthBroadcast in cfr-ConfigMCCH-MTCH- RedCap-r18 does not exceed the RedCap UE capabilities.

[0013] When both default and RedCap CFR are configured, then the network node can schedule simultaneously transmit sessions requiring high bandwidth via default CFR and sessions requiring low bandwidth via RedCap CFR.

[0014] eRedCap UEs

[0015] An eRedCap UE has the same maximum bandwidth restrictions as a RedCap UE, and therefore can also use the RedCap CFR to receive MBS broadcast. eRedCap UE does not support FR2 nor FR160kHz SCS. An eRedCap UE has additional restrictions compared to RedCap UE concerning the peak data rate. These additional eRedCap restrictions pose restrictions on the network node scheduling e.g. the number of PRBs that can be “configured” in Layer 1 (L1) scheduling.

[0016] Comparison of the UEs with reduced capabilities

[0017] A RedCap UE can receive MBS broadcast sessions that can be received by eRedCap UEs, with and without reduced based bandwidth. However an eRedCap UE may not be able to receive an MBS broadcast session that can be received by a RedCap UE, because the session is scheduled with a peak data rate that exceeds the eRedCap UE capability. Asimilar comparison can be made between eRedCap UE without reduced baseband bandwidth and with reduced baseband bandwidth.

[0018] An eRedCap UE may not be able to receive multiple sessions simultaneously, even the individual sessions are transmitted on a low data rate, but the aggregated data rate exceeds the eRedCap capabilities.

[0019] Quality of Service (QoS)

[0020] In case the QoS, e.g. Guaranteed Bit Rate (GBR), of the MBS session is such that it requires transmission on a high data rate, then an eRedCap UE is just not able to receive such a session. The high data rate may be a high peak data rate.

[0021] Barring of (e)RedCap UEs

[0022] The network is able to bar RedCap and / or eRedCap UEs from camping on the cell and receive MBS broadcast sessions in System Information Block 1 (SIB1), which is seen in Table 1 below: Table 1 intraFreqReselection-eRedCap Controls cell selection / reselection to intra-frequency cells for eRedCap UEs when this cell is barred, or treated as barred by the eRedCap UE, as specified in TS 38.304

[0020] . If not present, an eRedCap UE treats the cell as barred, i.e., the UE considers that the cell does not support eRedCap. intraFreqReselectionRedCap Controls cell selection / reselection to intra-frequency cells for RedCap UEs when this cell is barred, or treated as barred by the RedCap UE, as specified in TS 38.304

[0020] . If not present, a RedCap UE treats the cell as barred, i.e.,the UE considers that the cell does not support RedCap.

[0023] In additional the network node can bar 1Rx or 2Rx eRedCap UEs:

[0024] Core Network (CN) assistance information

[0025] The CN can indicate when an MBS broadcast session is intended to be received by RedCap UEs, see Supported UE Type parameter in BROADCAST SESSION SETUP / MODIFICATION REQUEST message (TS 38.413) in Table 2 below: Table 2 IE / Group Presence Range IE type and Semantics Criticality Assigned Name reference description Criticalit y <text omitted>Supported UE 0..<maxnoo YES ignore Type List fUETypes> >Supported M ENUMERATE - UE Type D (Non- RedCap UE, RedCap UE, ...)

[0026] Network node assurance for eRedCap UEs

[0027] RAN2 did not agree to clarify in TS 38.331 [2] for SIB20 when RedCap CFR is configured that if an MBS broadcast session is intended for eRedCap UEs, then the network node ensures that the scheduling restrictions for eRedCap UE are met, see R2-2403401. This is shown in Table 3 below: Table 3 Conditional Explanation presence CFR- The field is optionally present, Need R, if the configured bandwidth in cfr- RedCap ConfigMCCH-MTCH exceeds the (e)RedCap UE capability. It is absent otherwise. If the session is intended for eRedCap UEs and CFR is configured for RedCap UEs, network ensures that scheduling restrictions for eRedCap are met.

[0028] But in chairman notes the RAN2 understanding was captured: If the session is intended for eRedCap UEs and CFR is configured for RedCap UEs, the network may ensure that scheduling restrictions for eRedCap are met.

[0029] There currently exist certain challenge(s).

[0030] Problem 1: The network node may not know if an MBS broadcast session is intended to be received by eRedCap UEs.

[0031] This can be because the Third Generation Partnership Project (3GPP) did not introduce Supported UE Type for eRedCap UE, or the CN does not support Supported UE Type signalling, or this type of information is not available at the source, e.g. MBS service center.

[0032] Problem 2: In case the network node schedules MBS broadcast sessions with the peak data rate supported by eRedCap UEs, then RedCap UEs cannot receive MBS broadcast sessions with the peak data rate supported by RedCap UEs.

[0033] The scheduling restrictions of eRedCap UEs with reduced baseband bandwidth determine the maximum data rate for MBS broadcast sessions scheduled using the RedCap CFR.

[0034] Problem 3: The UE may not know if an MBS broadcast session is intended to be received by eRedCap UEs.

[0035] When the network node is simultaneously transmitting MBS broadcast sessions, that can only be received by RedCap UEs and MBS broadcast sessions that can be received by eRedCap UEs, then an eRedCap UE may try to receive sessions that it cannot receive, prohibiting it to receive sessions that it can received. SUMMARY

[0036] An objective of the embodiments herein is therefore to obviate at least one of the above disadvantages and to improve handling of an MBS broadcast session in a communications system.

[0037] According to a first aspect, the object is achieved by a method performed by a UE for handling a MBS broadcast session in a communications system. The UE obtains a broadcasted MBS broadcast session from a network node.

[0038] According to a second aspect, the object is achieved by a method performed by a network node for handling MBS broadcast session. in a communications system The network node determines that it is about to schedule an MBS broadcast session. The network node determines that the network node allows eRedCap UE and RedCap UE to camp in a same cell where the network node is broadcasting the MBS broadcast session. The network ndoe determines that network node has configured a RedCap CRF in the cell. The network node determines a scheduling strategy for the MBS broadcast session and broadcasts the MBS broadcast session using the determined scheduling strategy.

[0039] Embodiments herein afford many advantages, of which a non-exhaustive list of examples follows:

[0040] An advantage of the embodiments herein is that the scheduling strategy of the embodiments herein enables: - An eRedCap UE to receive MBS broadcast session when the UE capabilities support this. - The transmissions of simultaneous high data rate session that can only be received by RedCap UEs and low data rate sessions that can be received by eRedCap UEs. - eRedCap UEs to receive concurrent MBS broadcast sessions according to its scheduling restrictions.

[0041] Another advantage of the embodiments herein is that the eRedCap UE can avoid to try to receive sessions that it cannot receive, which can prohibit it to receive sessions that it can receive.

[0042] Another advantage of the embodiments herein is that they improve MBS broadcast sessions.

[0043] A further advantage of the embodiments herein is that they increase the probability of success of a UE receiving a MBS broadcast session that it is capable of receiving, i.e. it avoids receiving sessions that it cannot receive.

[0044] The embodiments herein are not limited to the features and advantages mentioned above. A person skilled in the art will recognize additional features and advantages upon reading the following detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

[0045] The embodiments herein will now be further described in more detail by way of example only in the following detailed description by reference to the appended drawings illustrating the embodiments and in which:

[0046] FIG.1 is a schematic drawing illustrating a communications system.

[0047] FIG.2 is a flow chart illustrating a method.

[0048] FIG.3 is a flow chart illustrating a method.

[0049] FIG.4A is a flow chart illustrating a method.

[0050] FIG.4B is a flow chart illustrating a method.

[0051] FIG.4C is a flow chart illustrating a method.

[0052] FIG.5 is a schematic drawing illustrating a network node.

[0053] FIG.6 is a schematic drawing illustrating a UE.

[0054] FIG.7 is a schematic drawing illustrating a communication system.

[0055] FIG.8 is a schematic drawing illustrating a UE.

[0056] FIG.9 is a schematic drawing illustrating a network node.

[0057] FIG.10 is a block diagram illustrating a virtualization environment.

[0058] The drawings are not necessarily to scale and the dimensions of certain features may have been exaggerated for the sake of clarity. Emphasis is instead placed upon illustrating the principle of the embodiments herein. DETAILED DESCRIPTION

[0059] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art. Additional information may also be found in the document(s) provided in the Appendix.

[0060] When RedCap CFR is configured and eRedCap UEs are allowed to camp on the cell, then the network node schedules the MBS broadcast session, provided that the QoS, e.g. guaranteed bitrate, of the MBS broadcast session allows this: 1) According to eRedCap UE with reduced baseband restrictions, otherwise; 2) According to eRedCap UE without reduced baseband restrictions.

[0061] In case, due to QoS requirements, the MBS broadcast session cannot be scheduled taking eRedCap restrictions into account, then no eRedCap specific scheduling restrictions are applied.

[0062] The UE is informed if an MBS broadcast session is intended for eRedCap UEs.

[0063] When RedCap CFR is configured and eRedCap UEs are allowed to camp on the cell, then the network node takes the eRedCap scheduling restrictions into account, if possible. If the required bitrate of the MBS broadcast session exceeds the eRedCap UE capability, then an eRedCap UE is not able to receive the MBS broadcast session scheduled via the RedCap CFR, but a RedCap UE is able to receive this session.

[0064] If an eRedCap UE knows that a session is not intended and cannot be received by eRedCap UEs, then the UE can avoid trying to receive such session.

[0065] FIG. 1 depicts a non-limiting example of a communications system 100, which may be a wireless communications system, sometimes also referred to as a wireless communications network, cellular radio system, or cellular network, in which the present disclosure may be implemented. The communications system 100 may be a 5G system, 5G network, NR-U or Next Gen system or network. The communications system 100 may alternatively be a younger system or older system than a 5G system, such as e.g. a 2G system, a 3G system, a 4G system, a 6G system a 7G system etc. The communications system 100 may support other technologies such as, for example, Long-Term Evolution (LTE), LTE- Advanced / LTE-Advanced Pro, e.g. LTE Frequency Division Duplex (FDD), LTE Time Division Duplex (TDD), LTE Half-Duplex Frequency Division Duplex (HD-FDD), LTE operating in an unlicensed band, NB-IoT. Thus, although terminology from 5G / NR and LTE may be used in this disclosure to exemplify, this should not be seen as limiting to only the aforementioned systems.

[0066] The communications system 100 comprises one or a plurality of network nodes, whereof a first network node 101a and a second network node 101b are depicted in the non- limiting example of FIG 1. Any of the first network node 101a, and the second network node 101b may be a radio network node, such as a radio base station, or any other network node with similar features capable of serving a user equipment, such as a wireless device or a machine type communication device, in the communications system 100. The first network node 101a may be an eNB and the second network node 101b may be a gNB. The first network node 101a may be a first eNB, and the second network node 101b may be a second eNB. The first network node 101a may be a first gNB, and the second network node 101b may be a second gNB. The first network node 101a may be a MeNB and the second network node 101b may be a gNB. Any of the first network node 101a and the second network node 101b may be co-localized, or they may be part of the same network node. The first network node 101a may be referred to as a source node or source network node, whereas the second network node 101b may be referred to as a target node or target network node. When the reference number 101 is used herein without the letters a or b, it refers to a network node in general, i.e. it refers to any of the first network node 101a or second network node 101b.

[0067] The communications system 100 covers a geographical area which may be divided into cell areas, wherein each cell area may be served by a network node, although, one network node may serve one or several cells. In FIG 1, the communications system 100 comprises a first cell 103a and a second cell 103b. Note that two cells are exemplified in FIG 1 only as an example, and that any n number of cells may be comprised in the communication system 100, where n is any positive integer. A cell is a geographical area where radio coverage is provided by the network node at a network node site. Each cell is identified by an identity within the local network node area, which is broadcast in the cell. In FIG 1, first network node 101a serves the first cell 103a, and the second network node 101b serves the second cell 103b. Any of the first network node 101a and the second network node 101b may be of different classes, such as, e.g., macro base station (BS), home BS or pico BS, based on transmission power and thereby also cell size. Any of the first network node 101a and the second network node 101b may be directly connected to one or more core networks, which are not depicted in FIG 1 for the sake of simplicity. Any of the first network node 101a and the second network node 101n may be a distributed node, such as a virtual node in the cloud, and it may perform its functions entirely on the cloud, or partially, in collaboration with another network node. The first cell 103a may be referred to as a source cell, whereas the second cell 103b may be referred to as a target cell.When the reference number 103 is used herein without the letters a or b, it refers to a cell in general, i.e. it refers to any of the first cell 103a or second cell 103b.

[0068] One or a plurality of UEs 105 is comprised in the communication system 100. Only one UE 105 is exemplified in FIG 1 for the sake of simplicity. A UE 105 may also be referred to simply as a device. The UE 105, e.g. an LTE UE or a 5G / NR UE, may be a wireless communication device which may also be known as e.g., a wireless device, a mobile terminal, wireless terminal and / or mobile station, a mobile telephone, cellular telephone, or laptop with wireless capability, just to mention some examples. The UE 105 may be a device by which a subscriber may access services offered by an operator’s network and services outside the operator’s network to which the operator’s radio access network and core network provide access, e.g. access to the Internet. The UE 105 may be any device, mobile or stationary, enabled to communicate over a radio channel in the communications system 100, for instance but not limited to e.g. UE, mobile phone, smart phone, sensors, meters, vehicles, household appliances, medical appliances, media players, cameras, Machine to Machine (M2M) device, Internet of Things (IOT) device, terminal device, communication device or any type of consumer electronic, for instance but not limited to television, radio, lighting arrangements, tablet computer, laptop or Personal Computer (PC). The UE 105 may be portable, pocket storable, hand held, computer comprised, or vehicle mounted devices, enabled to communicate voice and / or data, via the radio access network, with another entity, such as another UE, a server, a laptop, a Personal Digital Assistant (PDA), or a tablet, Machine-to-Machine (M2M) device, device equipped with a wireless interface, such as a printer or a file storage device, modem, or any other radio network unit capable of communicating over a radio link in the communications system 100.

[0069] The UE 105 is a RedCap UE or an eRedCap UE. A RedCap UE may be a UE having a first capability. An eRedCap UE may be a UE having a second capability.

[0070] The UE 105 is enabled to communicate wirelessly within the communications system 100. The communication may be performed e.g. between two UEs 105, between a UE 105 and a regular telephone, between the UE 105 and a network node, between network nodes, and / or between the UE 105 and a server via the radio access network and possibly one or more core networks and possibly the internet.

[0071] The first network node 101a may be configured to communicate in the communications system 100 with the UE 105 over a first communication link 108a, e.g., a radio link. The second network node 101b may be configured to communicate in the communications system 100 with the UE 105 over a second communication link 108b, e.g., aradio link. The first network node 101a may be configured to communicate in the communications system 100 with the second network node 101b over a third communication link 108c, e.g., a radio link or a wired link, although communication over more links may be possible. When the reference number 108 is used herein without the letters a, b or c, it refers to a communication link in general, i.e. it refers to any of the first communication link 108a, the second communication link 108b and the third communication link 108c.

[0072] It should be noted that the communication links 108 in the communications system 100 may be of any suitable kind comprising either a wired or wireless link. The link may use any suitable protocol depending on type and level of layer, e.g. as indicated by the Open Systems Interconnection (OSI) model, as understood by the person skilled in the art.

[0073] The embodiments herein relate to a method performed by a network node such as at least one of a gNB a UE in a cellular network.

[0074] The network node 101 evaluates its scheduling strategy according to the proposed solution in case: 1) the network node 101 is scheduling an MBS broadcast session in a cell, and 2) it allows eRedCap and RedCap UEs 105 to camp in the same cell where it is broadcasting the MBS broadcast session, and 3) he network node 101 has configured a RedCap CFR in the cell.

[0075] In one embodiment, the network node 101 may schedule an MBS broadcast session taking the scheduling restrictions of eRedCap UEs 105 with reduced baseband bandwidth into account, otherwise the network node 101 may schedule the MBS broadcast session taking the scheduling restrictions of eRedCap UEs 105 without reduced baseband bandwidth into account, if the required QoS, e.g. bitrate, allows this.

[0076] In one embodiment, to avoid eRedCap UEs 105 not using the RedCap CFR because they are afraid to waste their energy and time on MBS broadcast sessions they cannot receive, it is clarified in TS 38.300 that the network node 101 may schedule the MBS broadcast sessions such that all RedCap UEs 105 and eRedCap UEs 105 may receive MBS broadcast according to their capabilities, without knowing that an MBS broadcast session is intended for eRedCap UEs 105.

[0077] In one embodiment, when in a cell where the UE 105 is camping, the network node 101 may schedule an MBS broadcast session and where the network node 101 has configured a RedCap CFR, the UE 105 may take into account the received bitrate information about the MBS broadcast session, e.g. via Over The Air (ATO) configuration, when deciding to try to receive one or multiple MBS broadcast session(s) transmitted via RedCap CFR or default CFR.

[0078] In one embodiment, the eRedCap UE 105 may send an MMI message to the network node 101, where the provided information in the MMI message tells the network node 101 that the UE 105 is an eRedCap UE 105 with or without reduced baseband bandwidth and that the UE 105 is interested in a particular MBS session. This way the network node 101 may understand that a particular MBS session is intended for eRedCap UEs 105 and schedule the MBS session accordingly. This information may only be available in the network node 101 when an eRedCap UE 105 transits to RRC_CONNECTED state and wants to receive an MBS broadcast session in RRC_CONNECTED state. This information may not be available to the network node 101 when eRedCap UEs 105 remain in at least one of RRC_IDLE state and RRC_INACTIVE state while interested in and / or receiving MBS broadcast.

[0079] In one embodiment, the network node 101 may be informed about which MBS broadcast sessions are intended for eRedCap UEs 105 via OAM signalling.

[0080] In one embodiment, a specific TMGI value range may be standardized, which may only be used for MBS broadcast sessions for eRedCap UEs 105. A different range may be defined for eRedCap UEs 105 with and without reduced baseband bandwidth. Based on the TMGI value, the network node 101 may derive if the MBS broadcast session is intended for eRedCap UEs 105. This may also enable the eRedCap UE 105 to be selective in which MBS broadcast session to receive.

[0081] In one embodiment, a new parameter may be added to the service announcement, which indicates that the MBS broadcast session is intended for eRedCap UEs 105 with and without reduced baseband bandwidth. This may enable the eRedCap UE 105 to be selective in which MBS broadcast session to receive. The service announcement is provided from the network node 101 to the UE 105.

[0082] If the MBS Session is for broadcast, i.e. it is an MBS broadcast session or a broadcast MBS session, the Service Announcement may comprise at least one of: • the MBS FSA ID(s); • frequency information associated with the broadcast MBS session; • an indication that the MBS Session is intended for NR (e)RedCap UEs, UEs that are neither NR RedCap UEs nor NR eRedCap UEs, or any kind of UEs as defined in TS 26.502.

[0083] The method described above will now be described seen from the perspective of the network node 101. FIG 2 is a flowchart describing the present method in the network node 101 for handling a MBS broadcast session in a communications system 100. The methodcomprises at least one of the following steps to be performed by the network node 101, which steps may be performed in any suitable order than described below:

[0084] Step 200: This step may correspond to step 402 in FIG 4. The network node 101 determines that the network node 101 is about to schedule an MBS broadcast session. There may be one, two or more MBS broadcast sessions to be scheduled and sent. In other words, there may be at least one MBS broadcast session to be scheduled and sent. The phrase “is about to schedule an MBS broadcast session” may comprise that the MBS broadcast session will be scheduled soon, that the next thing that will occur is the scheduling of the MBS broadcast session, that the scheduling is imminent or is expected to occur shortly, e.g. within a time period.

[0085] The network node 101 know that it is about to schedule an MBS broadcast session from to the information provided to the UE 105, for example in the User Service Description (USD) using the Service Announcement.

[0086] The network node 101 may inform the UE 105 that an MBS broadcast session is intended for eRedCap UEs. Informing the UE 105 may comprise for example to provide information indicating that an MBS broadcast session is intended for eRedCap UEs, to send information indicating that an MBS broadcast session is intended for eRedCap UEs, etc. The UE 105 may be informed directly from the network node 101 or via some intermediate node.

[0087] The network node 101 may obtain information about UE capability from the UE 105. The UE capability may indicate that the UE 105 is an eRedCap UE with reduced baseband bandwidth. The UE capability may indicate that the UE 105 is an eRedCap UE without reduced baseband bandwidth. The UE capability may indicate whether the UE 105 is a RedCap or eRedCap UE. The capability information may be used in connected mode to schedule and configure the UE appropriately.

[0088] The network node 101 may obtain information about the UE’s interest in a particular MBS session from the UE 105.

[0089] The network node 101 may provide, to the UE 105, information indicating at least one of: • at least one MBS Frequency Selection Area, FSA, identity, ID; • frequency information associated with the broadcast MBS session; and

[0090] an indication that the MBS Session is intended for at least one of: New Radio, NR, eRedCap UEs, UEs that are neither NR RedCap UEs nor NR eRedCap UEs or any kind of UEsthat fulfills a criterion.The criterion may be that the UE is as defined in at least one of 3GPP TS 26.502 and 3GPP 38.306.

[0091] For example, chapter 4.2.21.1 in 3GPP 38.306 describes the RedCap UE as follows, and the items below may be one of the criterions mentioned above: “RedCap UE is the UE with reduced capability: - “The maximum bandwidth is 20 MHz for FR1, and is 100 MHz for FR2. UE features and corresponding capabilities related to UE bandwidths wider than 20 MHz in FR1 or wider than 100 MHz in FR2 are not supported by RedCap UEs; - The mandatory support (with capability signalling, enhancedChannelRaster-r18) of the channel raster as specified in TS 38.101-1 [2], clause 5.4I, for all bands supported by the UE; - The maximum mandatory supported DRB number is 8; - The mandatory supported PDCP SN length is 12 bits while 18 bits being optional; - The mandatory supported RLC AM SN length is 12 bits while 18 bits being optional; - For FR1, 1 DL MIMO layer if 1 Rx branch is supported, and 2 DL MIMO layers if 2 Rx branches are supported; for FR2, either 1 or 2 DL MIMO layers can be supported, while 2 Rx branches are always supported. For FR1 and FR2, UE features and corresponding capabilities related to more than 2 UE Rx branches or more than 2 DL MIMO layers, as well as UE features and capabilities related to more than 1 UE Tx branch or more than 1 UL MIMO layer are not supported by RedCap UEs; - CA, MR-DC, DAPS, CPAC, IAB (i.e., the RedCap UE is not expected to act as IAB node), and NCR (i.e., the RedCap UE is not expected to act as NCR-MT) related UE features and corresponding capabilities are not supported by RedCap UEs. All other feature groups or components of the feature groups as captured in TR 38.822

[0024] as well as capabilities specified in this specification remain applicable for RedCap UEs same as other UEs, unless indicated otherwise.”

[0092] For example, chapter 4.2.22.1 in 3GPP 38.306 describes the eRedCap UE as follows, and the items below may be one of the criterions mentioned above:

[0093] “eRedCap UE is the UE with reduced peak data rate and, with or without reduced baseband bandwidth in FR1: - The maximum bandwidth is 20 MHz for FR1. UE features and corresponding capabilities related to UE bandwidths wider than 20 MHz in FR1 are not supported by eRedCap UEs. eRedCap UEs do not support operation in FR2 and in FR160kHz SCS.- The mandatory support (with capability signalling, enhancedChannelRaster-r18) of the channel raster as specified in TS 38.101-1 [2], clause 5.4I, for all bands supported by the UE; - The maximum mandatory supported DRB number is 8; - The mandatory supported PDCP SN length is 12 bits while 18 bits being optional; - The mandatory supported RLC AM SN length is 12 bits while 18 bits being optional; - 1 DL MIMO layer if 1 Rx branch is supported, and 2 DL MIMO layers if 2 Rx branches are supported. UE features and corresponding capabilities related to more than 2 UE Rx branches or more than 2 DL MIMO layers, as well as UE features and capabilities related to more than 1 UE Tx branch or more than 1 UL MIMO layer are not supported by eRedCap UEs; - CA, MR-DC, DAPS, CPAC, IAB (i.e., the eRedCap UE is not expected to act as IAB node), and NCR (i.e., the eRedCap UE is not expected to act as NCR-MT) related UE features and corresponding capabilities are not supported by eRedCap UEs. All other feature groups or components of the feature groups as captured in TR 38.822

[0024] as well as capabilities specified in this specification remain applicable for eRedCap UEs same as other UEs, unless indicated otherwise.”

[0094] Step 201: This step may correspond to step 403 in FIG 4. The network node 101 determines that it allows eRedCap UE and RedCap UEs to camp in the same cell where it is broadcasting the MBS broadcast session. The cell may be for example the first cell 103a or the second cell 103b, as exemplified in FIG.1.

[0095] The basis for the decision of allowing eRedCap UE and RedCap UE to camp in the same cell may be found in the network implementation. It may be up to the network node implementation to support RedCap UEs and eRedCap UEs in the cell, see intraFreqReselection-eRedCap and intraFreqReselectionRedCap in SIB1. And it may be up to the network implementation to broadcast MBS session for RedCap UEs and eRedCap UEs.

[0096] Step 202: This step may correspond to step 404 in FIG 4. The network node 101 determines that it has configured a RedCap CRF in the cell.

[0097] Step 203: This step may correspond to steps 405, 406, 408, 409 and 411 in FIG 4. The network node 101 determines a scheduling strategy for the MBS broadcast session. The scheduling strategy may be as described in one or more of steps 405, 406, 408, 409, 411 in relation to FIG 4 below.

[0098] There may be a QoS flow associated with the MBS session, i.e. the QoS flow may indicate or determine the characteristics of the MBS Radio Bearer (MRB) required to carry the MBS session which provides the info about the QoS requirements to the network node 101.

[0099] The network node 101 may determine if at least one QoS requirement of the MBS broadcast session allows scheduling taking eRedCap restrictions into account. The QoS requirement may comprise a bitrate of the MBMS broadcast session being below a bitrate threshold, e.g. a guaranteed bitrate. There may be a QoS flow associated with the MBS session, i.e. the QoS flow may indicate or determine the characteristics of the MBS Radio Bearer (MRB) required to carry the MBS session.

[0100] When the at least one QoS requirement does not allow scheduling taking eRedCap restrictions into account, the network node 101 may determine to schedule MBS broadcast session not taking into account the scheduling restrictions of eRedCap UE 105 and the scheduling strategy may comprises to broadcast the MBS broadcast session not taking eRedCap into account.

[0101] When the at least one QoS requirement allows scheduling taking eRedCap restrictions into account, the network node 101 may determine if the MBS broadcast session can be scheduled taking into account eRedCap with reduced bandwidth restriction.

[0102] When the MBS broadcast session cannot be scheduled taking into account eRedCap with reduced bandwidth restriction, the network node 101 may determine to schedule MBS broadcasting session taking into account scheduling restrictions of eRedCap UE without reduced baseband bandwidth, and the scheduling strategy may comprise to broadcast the MBS broadcast session taking eRedCap into account and without reduced baseband bandwidth.

[0103] When the MBS broadcast session can be scheduled taking into account eRedCap with reduced bandwidth restriction, the network node 101 may determine to schedule MBS broadcast session taking into account the scheduling restrictions of eRedCap UE with reduced baseband bandwidth, and the scheduling strategy may comprise to broadcast the MBS broadcast session taking eRedCap into account and with reduced baseband bandwidth.

[0104]

[0105] Step 204: This step may correspond to step 407, 410 and 412 in FIG 4. The network node 101 broadcasts the MBS broadcast session using the determined scheduling strategy from step 203. Broadcasting may comprise to send the MBS broadcast session, to provide the MBS broadcasting session etc. Broadcasting the MBS broadcast session may comprise scheduling the MBS broadcast session.

[0106] The method described above will now be described seen from the perspective of the UE 105. FIG 3 is a flowchart describing the present method in the UE 105 for handling a MBS broadcast session in a communications system 100. The method comprises at least one of the following steps to be performed by the UE 105, which steps may be performed in any suitable order than described below:

[0107] Step 300: This step may correspond to step 400 in FIG 4. The UE 105 may transit from a first state to a second state. The UE 105 may determine that it wants to receive a MBS broadcast session. The first state may be at least one of a RRC_IDLE state and a RRC_INACTIVE, state. The second state may be a RRC_CONNECTED state.

[0108] Step 301: This step may correspond to step 401 in FIG 4. The UE 105 may provide information about UE capability to the network node 101. The UE 105 may provide information about the UE’s interest in a particular MBS session to the network node 101. The information about UE capability and the information about the UE’s interest in a particular MBS session may be provided in separate messages or in one common message.

[0109] The network node 101 may request information about the UE capabilities from the UE 105 during initial registration to the NW / PLMN. Information about the UE capabilities may be stored in the CN and sent to the network node 101, e.g. RAN node, when needed. So the UE 105 is requested to send the information about the UE capabilities, i.e. the UE 105 does not necessarily send them unsolicited.

[0110] If the UE 105 is interested to receive MBS broadcast sessions in connected mode, then the UE 105 may inform the network node 101 about this, for example via MII signalling. Dependent on the UE capabilities, the network noe 101 may be required to configure the UE 105 in a specific way such that the UE 105 may receive the session, e.g. when UE does not support MBS reception on SCell, then the Pcell of the UE has to be configured on the frequency where the MBS broadcast session is transmitted.

[0111] The UE capability may indicate that the UE 105 is an eRedCap UE with reduced baseband bandwidth. The UE capability may indicate that the UE 105 is an eRedCap UE without reduced baseband bandwidth.

[0112] The UE 105 may obtain, from the network node 101, information indicating that the MBS broadcast session is intended for eRedCap, UEs. A RedCap UE or eRedCap UE may use this information to determine which sessions to receive. The network node 101 may use this information to determine if the network node 101 has to configure a RedCap CFR that has a smaller bandwidth than the default CFR. If the default CFR exceeds the bandwidth supported by the RedCap, then the UE 105 may not necessarily be able to receive MBS.

[0113] The UE 105 may obtain, from the network node 101, information indicating at least one of: • at least one MBS Frequency Selection Area, FSA, identity, ID; • frequency information associated with the broadcast MBS session; and • an indication that the MBS Session is intended for at least one of: New Radio, NR, eRedCap UEs, UEs that are neither NR RedCap UEs nor NR eRedCap UEs or any kind of UEs that fulfills a criterion.

[0114] The UE 105 may use the above listed information to: • determine if the UE 105 is inside the MBS service area where it may receive MBS; and / or • determine which frequency to prioritize and reselect to when it wants to receive a session; and / or • determine whether the session is intended for RedCap and therefore the UE 105 may be capable to receive the session, i.e. UE meets the bandwidth requirements.

[0115] The criterion may be that the UE is as defined in at least one of 3GPP TS 26.502 and 38.306. From the User Service Description (USD) that the UE 105 receives via Service Announcement, the UE 105 may learn what are the start and stop times of a broadcast sessions. The USD may provide information about the frequency where the session is transmitted. The USD may provide geographical information indicating where the session is transmitted.

[0116] Step 302: This step may correspond to one or more of steps 407, 410, 412 in FIG 4. The UE 105 obtains a broadcasted MBS broadcast session from a network node 101.

[0117] FIG 4A, FIG.4B and FIG.4C are flowcharts illustrating a method. The steps of FIG. 4A may be performed first, then the steps of FIG. 4B may be performed an finally the steps of FIG.4C may be performed. However, the steps may be performed in any suitable order than described below. FIG. 4A illustrates steps 400-404. FIG. 4B illustrates steps 405-408. FIG.4C illustrates steps 409-412. The method comprises at least one of the following steps:

[0118] Step 400: This step is seen in FIG.4A. The UE 105 transits to RRC_CONNECTED state and wants to receive an MBS broadcast session. Transiting to RRC_CONNECTED state may comprise that the UE 105 changes from RRC_IDLE state to RRC_CONNECTED state or changes from RRC_INACTIVE state to RRC_CONNECTED state. In other words, the UE 105 transits from a first state to a second state.

[0119] Step 401: This step is seen in FIG.4A. This may be an optional step. The UE 105 may provide information about UE capability to the network node 101. The UE capability maybe that the UE 105 is an eRedCap UE with or without reduced baseband bandwidth. The UE 105 may provide information to the network node 101 indicating that UE 105 is interested in a particular MBS session. The information about the UE capability and the information indicating interest in a particular MBS session may be sent in separate messages or they may be sent in the same message.

[0120] The UE 105 may obtain, from the network node 101, information indicating at least one of: • at least one MBS Frequency Selection Area, FSA, identity, ID; • frequency information associated with the broadcast MBS session; and • an indication that the MBS Session is intended for at least one of: New Radio, NR, eRedCap UEs, UEs that are neither NR RedCap UEs nor NR eRedCap UEs or any kind of UEs that fulfills a criterion. The criterion may be that the UE is as defined in TS 26.502.

[0121] Step 402: This step is seen in FIG.4A . The network node 101 detects that an MBS broadcast session is to be started.

[0122] The network node 101 may schedule the MBS broadcast sessions according to the information provided to the UE 105 in the USD. The network node 101 knows that the UE 105 wants to receive an MBS broadcast session for a UE 105 in RRC_CONNECTED when the UE 105 sends the MII message with a list of broadcast sessions the UE 105 is interested to receive. The network node 101 does not know this for UEs in RRC_IDLE or RRC_INACTIVE. When the network node 101 receives a broadcast session from the CN for transmission over Uu interface, then the CN may indicate using Supported UE type whether the session is intended for RedCap or eRedCap UEs.

[0123] Step 403: This step is seen in FIG.4A. The network node 101 may determine that network node 101 allows eRedCap and RedCap UEs 105 to camp in the same cell where it is broadcasting the MBS broadcast session.

[0124] Step 404: This step is seen in FIG.4A. The network node 101 may determine that it has configured a RedCap CRF in the cell, i.e. the cell where the network node 101 is to broadcast the MBS broadcast session. The configuration may have been done at a previous time.

[0125] Step 405: This step is seen in FIG.4B. The network node 101 checks whether the QoS requirements, e.g. bitrate or guaranteed bitrate, of the MBS broadcast session allows scheduling taking eRedCap restrictions into account or not.

[0126] Step 406: This step is seen in FIG.4B. This step may be performed when the result of the check in step 405 is no. When the result of the check in step 405 is that the QoS requirements does not allow scheduling taking eRedCap restriction into account, the network node 101 may determine to schedule MBS broadcast session not taking into account the scheduling restrictions of eRedCap UE 105.

[0127] Step 407: This step is seen in FIG.4B. This step is performed after step 406. The network node 101 may send the MBS broadcast session not taking eRedCap into account.

[0128] Step 408: This step is seen in FIG.4B. This step may be performed when the result of the check in step 504 is yes. This step may be performed after step 405. When the result of the check in step 405 is that the QoS requirements do allow scheduling taking eRedCap restriction into account, the network node 101 may check if the MBS broadcast session can be scheduled taking into account eRedCap with reduced bandwidth restriction or not.

[0129] Step 409: This step is seen in FIG.4C. This step may be performed when the result of the check in step 408 is no. When the MBS broadcast session cannot be scheduled taking into account eRedCap with reduced bandwidth restriction, then the network node 101 may determine to schedule MBS broadcasting session taking into account scheduling restrictions of eRedCap UE without reduced baseband bandwidth.

[0130] Step 410: This step is seen in FIG.4C. This step may be performed after step 409. The network node may send the MBS broadcast session taking eRedCap into account and without reduced baseband bandwidth.

[0131] Step 411: This step is seen in FIG.4C. This step may be performed when a result of the check in step 408 is yes. When the MBS broadcast session can be scheduled taking into account eRedCap with reduced bandwidth restriction, the network node 101 may determine to schedule MBS broadcast session taking into account the scheduling restrictions of eRedCap UE with reduced baseband bandwidth.

[0132] Step 412: This step is seen in FIG.4C. The network node 101 may send the MBS broadcast session taking eRedCap into account and with reduced baseband bandwidth.

[0133] FIG 5 is a schematic drawing illustrating a network node 101.

[0134] The network node 101 may comprise processing circuitry 501, e.g. one or more processors, configured to perform the methods herein.

[0135] The network node 101 further comprises a memory 505. The memory 505, comprises one or more units to be used to store data on, such as indications, MBS broadcast session information, scheduling strategy, UE capability information, RedCap CRF information, measurements, thresholds, data related to nodes, and applications to perform themethods disclosed herein when being executed, and similar. Furthermore, the network node 101 may comprise a communication interface 506 such as comprising a transmitter, a receiver, a transceiver and / or one or more antennas.

[0136] The methods according to the embodiments described herein for handling a MBS broadcast session, the network node 101 are respectively implemented using e.g., a computer program product 507 or a computer program, comprising instructions, i.e., software code portions, which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the network node 101. The computer program product 507 may be stored on a computer-readable storage medium 508 e.g. a disc, a universal serial bus (USB) stick or similar. The computer-readable storage medium 508 having stored thereon the computer program product, may comprise the instructions which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the network node 101. In some embodiments, the computer- readable storage medium may be a transitory or a non-transitory computer-readable storage medium. Thus, embodiments herein may disclose a network node 101 for handling a MBS broadcast session in a wireless communication network, wherein the network node 101 comprises processing circuitry and a memory, the memory comprising instructions executable by the processing circuitry whereby the network node 101 is operative to perform any of the methods herein.

[0137] FIG 6 is a schematic drawing illustrating a UE 105.

[0138] The UE 105 may comprise processing circuitry 601, e.g. one or more processors, configured to perform the methods herein.

[0139] The UE 105 further comprises a memory 605. The memory 605, comprises one or more units to be used to store data on, such as indications, MBS broadcast session information, scheduling strategy, UE capability information, RedCap CRF information, measurements, thresholds, data related to nodes, and applications to perform the methods disclosed herein when being executed, and similar. Furthermore, the UE 105 may comprise a communication interface 606 such as comprising a transmitter, a receiver, a transceiver and / or one or more antennas.

[0140] The methods according to the embodiments described herein for handling a MBS broadcast session, the UE 105 are respectively implemented using e.g., a computer program product 607 or a computer program, comprising instructions, i.e., software code portions, which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the UE 105. The computer program product 607may be stored on a computer-readable storage medium 608 e.g. a disc, a universal serial bus (USB) stick or similar. The computer-readable storage medium 608 having stored thereon the computer program product, may comprise the instructions which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the UE 105. In some embodiments, the computer-readable storage medium may be a transitory or a non-transitory computer-readable storage medium. Thus, embodiments herein may disclose a UE 105 for handling a MBS broadcast session in a wireless communication network, wherein the UE 105 comprises processing circuitry and a memory, the memory comprising instructions executable by the processing circuitry whereby the UE 105 is operative to perform any of the methods herein.

[0141] FIG 7 shows an example of a communication system 700 in accordance with some embodiments.

[0142] In the example, the communication system 700 includes a telecommunication network 702 that includes an access network 704, such as a radio access network (RAN), and a core network 706, which includes one or more core network nodes 708. The access network 704 includes one or more access network nodes, such as network nodes 710a and 710b (one or more of which may be generally referred to as network nodes 710), or any other similar 3rdGeneration Partnership Project (3GPP) access nodes or non-3GPP access points. Moreover, as will be appreciated by those of skill in the art, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network 702 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network 702 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network 702, including one or more network nodes 710 and / or core network nodes 708.

[0143] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O- CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). The networknode may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an A1, F1, W1, E1, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an O-2 interface defined by the O-RAN Alliance or comparable technologies. The network nodes 710 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 712a, 712b, 712c, and 712d (one or more of which may be generally referred to as UEs 712) to the core network 706 over one or more wireless connections.

[0144] Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 700 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 700 may include and / or interface with a0ny type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0145] The UEs 712 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes 710 and other communication devices. Similarly, the network nodes 710 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 712 and / or with other network nodes or equipment in the telecommunication network 702 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network 702.

[0146] In the depicted example, the core network 706 connects the network nodes 710 to one or more host computing systems, such as host 716. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 706 includes one more core network nodes (e.g., core network node 708) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, such that the descriptions thereof are generallyapplicable to the corresponding components of the core network node 708. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0147] The host 716 may be under the ownership or control of a service provider other than an operator or provider of the access network 704 and / or the telecommunication network 702. The host 716 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0148] As a whole, the communication system 700 of FIG 7 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.

[0149] In some examples, the telecommunication network 702 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 702 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 702. For example, the telecommunications network 702 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC) / Massive IoT services to yet further UEs.

[0150] In some examples, the UEs 712 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 704 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 704. Additionally, a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved- UMTS Terrestrial Radio Access Network) New Radio – Dual Connectivity (EN-DC).

[0151] In the example, the hub 714 communicates with the access network 704 to facilitate indirect communication between one or more UEs (e.g., UE 712c and / or 712d) and network nodes (e.g., network node 710b). In some examples, the hub 714 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 714 may be a broadband router enabling access to the core network 706 for the UEs. As another example, the hub 714 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 710, or by executable code, script, process, or other instructions in the hub 714. As another example, the hub 714 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 714 may be a content source. For example, for a UE that is a VR device, display, loudspeaker, or other media delivery device, the hub 714 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 714 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 714 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy IoT devices.

[0152] The hub 714 may have a constant / persistent or intermittent connection to the network node 710b. The hub 714 may also allow for a different communication scheme and / or schedule between the hub 714 and UEs (e.g., UE 712c and / or 712d), and between the hub 714 and the core network 706. In other examples, the hub 714 is connected to the core network 706 and / or one or more UEs via a wired connection. Moreover, the hub 714 may be configured to connect to an M2M service provider over the access network 704 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 710 while still connected via the hub 714 via a wired or wireless connection. In some embodiments, the hub 714 may be a dedicated hub – that is, a hub whose primary function isto route communications to / from the UEs from / to the network node 710b. In other embodiments, the hub 714 may be a non-dedicated hub – that is, a device which is capable of operating to route communications between the UEs and network node 710b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0153] FIG 8 shows a UE 800 in accordance with some embodiments. The UE 800 presents additional details of some embodiments of the UE 712 of FIG 1. As used herein, a UE refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage / playback device, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), an Augmented Reality (AR) or Virtual Reality (VR) device, wireless customer-premise equipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0154] A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle- to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0155] The UE 800 includes processing circuitry 802 that is operatively coupled via a bus 804 to an input / output interface 806, a power source 808, a memory 810, a communication interface 812, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in FIG 8. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multipleinstances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0156] The processing circuitry 802 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 810. The processing circuitry 802 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 802 may include multiple central processing units (CPUs).

[0157] In the example, the input / output interface 806 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE 800. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

[0158] In some embodiments, the power source 808 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source 808 may further include power circuitry for delivering power from the power source 808 itself, and / or an external power source, to the various parts of the UE 800 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 808. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 808 to make the power suitable for the respective components of the UE 800 to which power is supplied.

[0159] The memory 810 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 810 includes one or more application programs 814, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 816. The memory 810 may store, for use by the UE 800, any of a variety of various operating systems or combinations of operating systems.

[0160] The memory 810 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD- DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 810 may allow the UE 800 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 810, which may be or comprise a device-readable storage medium.

[0161] The processing circuitry 802 may be configured to communicate with an access network or other network using the communication interface 812. The communication interface 812 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 822. The communication interface 812 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter 818 and / or a receiver 820 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 818 and receiver 820 may becoupled to one or more antennas (e.g., antenna 822) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0162] In the illustrated embodiment, communication functions of the communication interface 812 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / internet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0163] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 812, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0164] As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0165] A UE, when in the form of an Internet of Things (IoT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an IoT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, asmoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an IoT device comprises circuitry and / or software in dependence of the intended application of the IoT device in addition to other components as described in relation to the UE 800 shown in FIG 8.

[0166] As yet another specific example, in an IoT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another UE and / or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0167] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0168] FIG 9 shows a network node 900 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).

[0169] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an O-RAN access node) and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0170] Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).

[0171] The network node 900 includes a processing circuitry 902, a memory 904, a communication interface 906, and a power source 908. The network node 900 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 900 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 900 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 904 for different RATs) and some components may be reused (e.g., a same antenna 910 may be shared by different RATs). The network node 900 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 900, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may beintegrated into the same or different chip or set of chips and other components within network node 900.

[0172] The processing circuitry 902 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other network node 900 components, such as the memory 904, to provide network node 900 functionality.

[0173] In some embodiments, the processing circuitry 902 includes a system on a chip (SOC). In some embodiments, the processing circuitry 902 includes one or more of radio frequency (RF) transceiver circuitry 912 and baseband processing circuitry 914. In some embodiments, the radio frequency (RF) transceiver circuitry 912 and the baseband processing circuitry 914 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 912 and baseband processing circuitry 914 may be on the same chip or set of chips, boards, or units.

[0174] The memory 904 may comprise any form of volatile or non-volatile computer- readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer- executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 902. The memory 904 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 902 and utilized by the network node 900. The memory 904 may be used to store any calculations made by the processing circuitry 902 and / or any data received via the communication interface 906. In some embodiments, the processing circuitry 902 and memory 904 is integrated.

[0175] The communication interface 906 is used in wired or wireless communication of signaling and / or data between a network node, access network, and / or UE. As illustrated, the communication interface 906 comprises port(s) / terminal(s) 916 to send and receive data, for example to and from a network over a wired connection. The communication interface 906 also includes radio front-end circuitry 918 that may be coupled to, or in certain embodimentsa part of, the antenna 910. Radio front-end circuitry 918 comprises filters 920 and amplifiers 922. The radio front-end circuitry 918 may be connected to an antenna 910 and processing circuitry 902. The radio front-end circuitry may be configured to condition signals communicated between antenna 910 and processing circuitry 902. The radio front-end circuitry 918 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 918 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 920 and / or amplifiers 922. The radio signal may then be transmitted via the antenna 910. Similarly, when receiving data, the antenna 910 may collect radio signals which are then converted into digital data by the radio front-end circuitry 918. The digital data may be passed to the processing circuitry 902. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0176] In certain alternative embodiments, the network node 900 does not include separate radio front-end circuitry 918, instead, the processing circuitry 902 includes radio front-end circuitry and is connected to the antenna 910. Similarly, in some embodiments, all or some of the RF transceiver circuitry 912 is part of the communication interface 906. In still other embodiments, the communication interface 906 includes one or more ports or terminals 916, the radio front-end circuitry 918, and the RF transceiver circuitry 912, as part of a radio unit (not shown), and the communication interface 906 communicates with the baseband processing circuitry 914, which is part of a digital unit (not shown).

[0177] The antenna 910 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 910 may be coupled to the radio front-end circuitry 918 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 910 is separate from the network node 900 and connectable to the network node 900 through an interface or port.

[0178] The antenna 910, communication interface 906, and / or the processing circuitry 902 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the network node. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna 910, the communication interface 906, and / or the processing circuitry 902 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

[0179] The power source 908 provides power to the various components of network node 900 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 908 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 900 with power for performing the functionality described herein. For example, the network node 900 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 908. As a further example, the power source 908 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0180] Embodiments of the network node 900 may include additional components beyond those shown in FIG 9 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 900 may include user interface equipment to allow input of information into the network node 900 and to allow output of information from the network node 900. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 900. In some embodiments providing a core network node, such as core network node 108 of FIG. 7, some components, such as the radio front-end circuitry 918 and the RF transceiver circuitry 912 may be omitted.

[0181] FIG 10 is a block diagram illustrating a virtualization environment 1000 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 1000 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 1000 includes components defined by the O-RAN Alliance,such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface. Virtualization may facilitate distributed implementations of a network node, UE, core network node, or host.

[0182] Applications 1002 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0183] Hardware 1004 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 1006 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 1008a and 1008b (one or more of which may be generally referred to as VMs 1008), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 1006 may present a virtual operating platform that appears like networking hardware to the VMs 1008.

[0184] The VMs 1008 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 1006. Different embodiments of the instance of a virtual appliance 1002 may be implemented on one or more of VMs 1008, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

[0185] In the context of NFV, a VM 1008 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 1008, and that part of hardware 1004 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 1008 on top of the hardware 1004 and corresponds to the application 1002.

[0186] Hardware 1004 may be implemented in a standalone network node with generic or specific components. Hardware 1004 may implement some functions via virtualization. Alternatively, hardware 1004 may be part of a larger cluster of hardware (e.g. such as in a datacenter or CPE) where many hardware nodes work together and are managed via management and orchestration 1010, which, among others, oversees lifecycle management of applications 1002. In some embodiments, hardware 1004 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 1012 which may alternatively be used for communication between hardware nodes and radio units.

[0187] Although the computing devices described herein (e.g., UEs, network nodes) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0188] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer- readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of thoseparticular embodiments, whether executing instructions stored on a non-transitory computer- readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.REFERENCES 1. 3GPP 38.300 "NR and NG-RAN Overall Description; Stage 2", v18.1.0 2. 3GPP 38.331 "NR; Radio Resource Control (RRC) protocol specification", v18.1.0 3. 3GPP 24.116 "Stage 3 aspects of system architecture enhancements for TV services", v18.0.0ABBEVIATIONS Abbreviation Explanation GBR Guaranteed Bit Rate CFR Common Frequency Resources eRedCap Extra Reduced Capability MBS Multicast / Broadcast Service MMI MBSInterestIndication OAM Operation And Maintenance OTA Over The Air RedCap Reduced Capability USD User Service Description TMGI Temporary Mobile Group IdentityAPPENDIX 3GPP TSG-RAN2 Meeting #126 R2-24xxxxx Fukuoka, Japan, 20 – 24 May 2024 Agenda Item: 7.24.2 TEI proposals by RAN2 Source: Ericsson Title: Scheduling restrictions with RedCap CFR and eRedCap UEs Document for: Discussion and Decision 1 Introduction In this contribution it is discussed how the gNB can ensure that eRedCap UEs can receive MBS broadcast taking into account their scheduling restrictions. 2 Background eRedCap scheduling restrictions An eRedCap UE has additional restrictions compared to RedCap UE concerning the supported peak data rate. These additional eRedCap restrictions pose restrictions on the gNB scheduling e.g. the number of PRBs that can be “configured” in L1 scheduling. Barring of (e)RedCap UEs The network is able to bar RedCap and / or eRedCap UEs from camping on the cell (and receive MBS broadcast sessions) in SIB1: intraFreqReselection-eRedCap Controls cell selection / reselection to intra-frequency cells for eRedCap UEs when this cell is barred, or treated as barred by the eRedCap UE, as specified in TS 38.304

[0020] . If not present, an eRedCap UE treats the cell as barred, i.e., the UE considers that the cell does not support eRedCap. intraFreqReselectionRedCap Controls cell selection / reselection to intra-frequency cells for RedCap UEs when this cell is barred, or treated as barred by the RedCap UE, as specified in TS 38.304

[0020] . If not present, a RedCap UE treats the cell as barred, i.e.,the UE considers that the cell does not support RedCap. CN assistance information The CN can indicate when an MBS broadcast session is intended to be received by RedCap UEs, see Supported UE Type parameter in BROADCAST SESSION SETUP / MODIFICATION REQUEST message (TS 38.413): IE / Group Name Presence Range IE type and Semantics description Criticality Assigned reference Criticality <text omitted> Supported UE Type List 0..<maxnoof YES ignore UETypes> >Supported UE Type M ENUMERATED - (Non-RedCap UE, RedCap UE, ...)Introduction of an indication that the MBS broadcast session is intended for eRedCap UEs has been discussed in RAN2 [1] but will not be discussed further in RAN2: Not pursued in RAN2. If something is needed, it should be done by RAN3. gNB assurance for eRedCap UEs RAN2 did not agree to clarify in TS 38.331 [2] (for the RedCap CFR configured in SIB20) that if an MBS broadcast session is intended for eRedCap UEs, then the gNB ensures that the scheduling restrictions for eRedCap UE are met [2]:But in chairman notes the RAN2 understanding was captured: RAN2 understanding is that if the session is intended for eRedCap UEs and CFR is configured for RedCap UEs, network ensures that scheduling restrictions for eRedCap are met.” 3 Discussion eRedCap scheduling restrictions A RedCap UE can receive MBS broadcast sessions that can be received by eRedCap UEs (with and without reduced based bandwidth). However an eRedCap UE may not be able to receive an MBS broadcast session that can be received by a RedCap UE, because the session is scheduled with a peak data rate that exceed the eRedCap UE capability. A similar comparison can be made between eRedCap UE without and with reduced baseband bandwidth. An eRedCap UE may not be able to receive multiple session simultaneously, even the individual sessions are transmitted on a low data rate, but the aggregated data rate exceeds the eRedCap capabilities. QoS In case the QoS, e.g. Guaranteed Bit Rate (GBR), of the MBS session is such that it requires transmission on a high (peak) data rate, then an eRedCap UE is just not able to receive such a session. MBS session intended for eRedCap UEs In case 3GPP does not introduce Supported UE Type for eRedCap UE, or the CN does not support Supported UE Type signalling, or this information is not available outside 3GPP (MBS service center), the gNB may not know if an MBS broadcast session is intended for eRedCap UEs: Observation 1 The gNB may not know if an MBS broadcast session is intended to be received by eRedCap UEs. One size fits all approach In case the gNB schedules MBS broadcast sessions via RedCap CFR at a low data rate, when eRedCap UEs are allowed to camp on the cell, then RedCap UEs cannot receive high data rate sessions. In such case the scheduling restrictions of eRedCap UEs with reduced basebandbandwidth determine the maximum data rate for MBS broadcast sessions scheduled using the RedCap CFR. When using the default CFR for both RedCap and non-RedCap UEs, a similar problem was observed, i.e. the RedCap UEs would determine the maximum bandwidth that can be used for the MBS broadcast sessions. For that reason a separate RedCap CFR was introduced to enable simultaneous “RedCap bandwidth” and “non-RedCap bandwidth” transmissions. However with eRedCap UEs a separate eRedCap CFR would not have solved this problem, because the existing RedCap CFR can be used with RedCap and eRedCap peak data rates. Proposed way forward (when the gNB does not know if the session is intended for eRedCap UEs) When RedCap CFR is configured and eRedCap UEs are allowed to camp on the cell, then the gNB takes the eRedCap scheduling restrictions into account, if possible. In more details: When RedCap CFR is configured and eRedCap UEs are allowed to camp on the cell, then the gNB schedules an MBS broadcast session, provided that the QoS requirements (e.g. bitrate) of the MBS broadcast session allows this: 1. According to eRedCap UE with reduced baseband restrictions, otherwise; 2. According to eRedCap UE without reduced baseband restrictions In case the MBS broadcast session cannot be scheduled taking eRedCap restrictions into account the due to the QoS bitrate requirements, then no eRedCap scheduling restrictions are applied. This scheduling strategy enables: • an eRedCap UE to receive the MBS broadcast session when the UE capabilities support this. • the transmissions of simultaneous high data rate session that can only be received by RedCap UEs and low data rate sessions that can be received by eRedCap UEs using the RedCap CFR. • eRedCap UEs to receive concurrent MBS broadcast sessions according to its scheduling restrictions. Observation 2 The gNB is not dependent on CN assistance to meet the eRedCap scheduling restrictions. It would be good to clarify that gNB can also meet the eRedCap scheduling restrictions when the gNB does not know that the MBS broadcast session is intended for eRedCap UEs: Proposal 1 Clarify in 38.300 that gNB can meet the eRedCap scheduling restrictions also when the gNB does not know that the MBS broadcast session is intended for eRedCap UEs. A TP is provided in the Annex for further discussion and agreement. It can be beneficial to the gNB to explicitly know if an MBS broadcast session is intended for eRedCap UEs, but it is not strictly needed. The gNB has more scheduling flexibility when it does not need to follow the eRedCap scheduling restrictions. In case an eRedCap does not know if a session is intended for and can be received by eRedCap UEs then the UE may try to receive sessions it cannot receive, which can prohibit it to receive sessions that it can receive:Observation 3 In case an eRedCap does not know if a session is intended for and can be received by eRedCap UEs then the UE may try to receive sessions it cannot receive, which can prohibit it to receive sessions that it can receive. There are different ways this can be resolved: • Reserved TMGI range for eRedCap UEs • New parameter in service announcement indicating that the session is intended for eRedCap UEs However these options are outside RAN2 scope. 4 Summary RAN2 is kindly asked to discuss MBS broadcast and eRedCap UEs: Observation 1 The gNB may not know if an MBS broadcast session is intended to be received by eRedCap UEs. Observation 2 The gNB is not dependent on CN assistance to meet the eRedCap scheduling restrictions. Observation 3 In case an eRedCap does not know if a session is intended for and can be received by eRedCap UEs then the UE may try to receive sessions it cannot receive, which can prohibit it to receive sessions that it can receive. Proposal 1 Clarify in 38.300 that gNB can meet the eRedCap scheduling restrictions also when the gNB does not know that the MBS broadcast session is intended for eRedCap UEs. 5 References [1] R2-2403549, MBS and eRedCap UE, Ericsson, DISC, RAN2#125-bis [2] R2-2403401, Discussion on RILs E158, E159 and V179 for eRedCap UEs, Ericsson, DISC, RAN2#a25-bis 6 Annex: TP 38.300 16.10.6.6 Physical Layer A CFR configured by SIB is defined for broadcast scheduling as an 'MBS frequency region' with a number of contiguous PRBs with a bandwidth equal to or larger than CORESET0, with the same numerology as CORESET0, and broadcast scheduling may have specific characteristics (e.g., PDCCH and PDSCH configurations). The NG-RAN node may configure an additional RedCap CFR when the bandwidth of the configured default CFR is outside the (e)RedCap UE capability. A UE only monitors one CFR at a time. An (e)RedCap UE monitors the RedCap CFR, if configured, otherwise the (e)RedCap UE monitors the default CFR, if the bandwidth of the default CFR is within the UE capability. If RedCap CFR is configured, the UE is not expected to receive two DCIs scrambled with the same g-RNTI or the same MCCH-RNTI. NOTE: When the RedCap CFR is configured and the cell is not barred for eRedCap UEs and the gNB does not know if the MBS broadcast session is intended for eRedCap UEs then the gNB may decide to schedule the MBS broadcast session taking into account the scheduling restrictions of eRedCap UE with reduced baseband bandwidth, otherwise the scheduling restrictions of eRedCap UE without reduced baseband bandwidth. The eRedCap scheduling restrictions are taken into account when this results in that the QoS requirements (e.g. bitrate) cannot be met.The maximum number of MIMO layers is one for MBS broadcast scheduling. RB-level rate matching, and RE- level rate matching around LTE-CRS configured by higher layer signalling are supported for MCCH and MTCH. Slot-level repetition is supported for MTCH. HARQ-ACK feedback is not supported for MBS broadcast. Only dynamic scheduling is supported for MBS broadcast.

Claims

CLAIMS 1. A method performed by a user equipment, UE, (105) for handling a Multicast Broadcast Service, MBS, broadcast session in a communications system (100), the method comprising: obtaining (302, 407, 410, 412) a broadcasted MBS broadcast session from a network node (101).

2. The method of claim 1, comprising: transiting (300, 400) from a first state to a second state.

3. The method of claim 2, wherein the first state is at least one of a Radio Resource Control_IDLE, RRC_IDLE state and a Radio Resource Control_INACTIVE, RRC_INACTIVE, state and the second state is a Radio Resource Control_CONNECTED, RRC_CONNECTED, state.

4. The method of any of the preceding claims, comprising: determining (300, 400) that the UE (105) wants to receive an MBS broadcast session.

5. The method of any of the preceding claims, comprising: providing (301, 401) information about UE capability to the network node (101).

6. The method of claim 5, wherein the UE capability indicates that the UE (105) is an extended Reduced Capability, eRedCap, UE with reduced baseband bandwidth.

7. The method of claim 5, wherein the UE capability indicates that the UE (105) is an extended Reduced Capability, eRedCap, UE without reduced baseband bandwidth.

8. The method of any of the preceding claims, comprising: providing (301, 401) information about the UE’s interest in a particular MBS session to the network node (101).

9. The method of any of the preceding claims, comprising: obtaining (301), from the network node (101), information indicating that the MBS broadcast session is intended for extra Reduced Capability, eRedCap, UEs.

10. The method of any of the preceding claims, comprising: obtaining (301), from the network node (101), information indicating at least one of: • at least one MBS Frequency Selection Area, FSA, identity, ID; • frequency information associated with the broadcast MBS session; and • an indication that the MBS Session is intended for at least one of: New Radio, NR, eRedCap UEs, UEs that are neither NR RedCap UEs nor NR eRedCap UEs or any kind of UEs that fulfills a criterion.

11. A method performed by a network node (101) for handling a Multicast Broadcast Service, MBS, broadcast session in a communications system (100), the method comprising: determining (200, 402) that the network node (101) is about to schedule an MBS broadcast session; determining (201, 403) that the network node (101) allows extra Reduced Capability, eRedCap, User Equipment, UE, and Reduced Capability, RedCap, UE, to camp in a same cell where the network node (101) is broadcasting the MBS broadcast session; determining (202, 404) that network node (101) has configured a RedCap Common Frequency Resource, CRF, in the cell; determining (203, 405, 406, 408, 409, 411) a scheduling strategy for the MBS broadcast session; and broadcasting (204, 407, 410, 412) the MBS broadcast session using the determined scheduling strategy.

12. The method of claim 11, comprising: informing (200) the UE (105) that an MBS broadcast session is intended for eRedCap UEs.

13. The method of any of claims 11-12, comprising: determining (203, 405) if at least one Quality of Service, QoS, requirement of the MBS broadcast session allows scheduling taking eRedCap restrictions into account.

14. The method of claim 13, comprising:when the at least one QoS requirement does not allow scheduling taking eRedCap restrictions into account, determining (203, 406) to schedule MBS broadcast session not taking into account the scheduling restrictions of eRedCap UE (105); and wherein the scheduling strategy comprises to broadcast (204, 407) the MBS broadcast session not taking eRedCap into account.

15. The method of any of claims 13-14, wherein the QoS requirement comprises a bitrate of the MBMS broadcast session being below a bitrate threshold.

16. The method of any of claims, 13-15 comprising: when the at least one QoS requirement allows scheduling taking eRedCap restrictions into account, determining (203, 408) if the MBS broadcast session can be scheduled taking into account eRedCap with reduced bandwidth restriction.

17. The method of any of claims 13-16, comprising: when the MBS broadcast session cannot be scheduled taking into account eRedCap with reduced bandwidth restriction, determining (203, 409) to schedule MBS broadcasting session taking into account scheduling restrictions of eRedCap UE without reduced baseband bandwidth; and wherein the scheduling strategy comprises to broadcast (204, 410) the MBS broadcast session taking eRedCap into account and without reduced baseband bandwidth.

18. The method of any of claims 13-17, comprising: when the MBS broadcast session can be scheduled taking into account eRedCap with reduced bandwidth restriction, determining (203, 411) to schedule MBS broadcast session taking into account the scheduling restrictions of eRedCap UE with reduced baseband bandwidth; and wherein the scheduling strategy comprises to broadcast (204, 412) the MBS broadcast session taking eRedCap into account and with reduced baseband bandwidth.

19. The method of any of the preceding claims, comprising: obtaining (200, 401) information about UE capability from the UE (105).

20. The method of claim 19, wherein the UE capability indicates that the UE (105) is anextended Reduced Capability, eRedCap, UE with reduced baseband bandwidth.

21. The method of claim 196, wherein the UE capability indicates that the UE (105) is an extended Reduced Capability, eRedCap, UE without reduced baseband bandwidth.

22. The method of any of the claims 11-21, comprising: obtaining (200, 401) information about the UE’s interest in a particular MBS session from the UE (105).

23. The method of any of claims 11-22, comprising: (200), to the UE (105), information indicating at least one of: • at least one MBS Frequency Selection Area, FSA, identity, ID; • frequency information associated with the broadcast MBS session; and • an indication that the MBS Session is intended for at least one of: New Radio, NR, eRedCap UEs, UEs that are neither NR RedCap UEs nor NR eRedCap UEs or any kind of UEs that fulfills a criterion.

24. A user equipment, UE, (105) for handling a Multicast Broadcast Service, MBS, broadcast session in a communications system (100), comprising: processing circuitry (601) configured to perform a method of any of claims 1-10; and power supply circuitry configured to supply power to the processing circuitry (601).

21. A network node for handling a Multicast Broadcast Service, MBS, broadcast session in a communications system (100), the network node (101) comprising: processing circuitry (501) configured to perform a method of any of claims 11-19; power supply circuitry configured to supply power to the processing circuitry (501).

22. A user equipment, UE, (105) for handling a Multicast Broadcast Service, MBS, broadcast session in a communications system (100), the UE (105) comprising: an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry (601), and configured to condition signals communicated between the antenna and the processing circuitry (501);the processing circuitry (601) being configured to perform a method of any of claims 1-10; an input interface (606) connected to the processing circuitry (601) and configured to allow input of information into the UE (105) to be processed by the processing circuitry (601); an output interface (606) connected to the processing circuitry (601) and configured to output information from the UE (105) that has been processed by the processing circuitry (601); and a battery connected to the processing circuitry (601) and configured to supply power to the UE (105).

Images