Methods for allowing one receiver branch UE bypassing barring access during mobility

Abstract

Systems and methods related to exempting User Equipments (UEs) from cell barring or allowing UEs to bypass cell barring are disclosed. In one embodiment, a method performed by a first node for a Radio Access Network (RAN) of a cellular communications system comprises sending, to a second node, information that indicates that the first node is exempting UEs or one or more certain groups of UEs from cell barring in case of emergency traffic. In one embodiment, the information indicates that the first node is exempting one or more certain groups of UEs from cell barring in case of emergency. In this manner, bypassing of cell barring due to an emergency is enabled.

Description

[0001] METHODS FOR ALLOWING ONE RECEIVER BRANCH UE BYPASSING BARRING ACCESS DURING MOBILITY

[0002] Related Applications

[0003] This application claims the benefit of provisional patent application serial number 63 / 551,763, filed February 9, 2024, the disclosure of which is hereby incorporated herein by reference in its entirety.

[0004] Technical Field

[0005] The present disclosure relates to a Radio Access Network (RAN) of a cellular communications system and, more particularly, to bypassing of cell barring.

[0006] Background

[0007] The overall 3rdGeneration Partnership Project (3GPP) 5thGeneration (5G) Radio Access Network (RAN) (i.e., Next Generation Radio Access Network (NG-RAN)) architecture is depicted in Figure 1, which is a reproduction of Figure 6.1-1 of 3GPP Technical Specification (TS) 38.401 V18.0.0. Further details about the NG-RAN architecture are provided in the excerpt from 3GPP TS 38.401 below.

[0008] A gNB with a split Control Plane (CP) / User Plane (UP) architecture is depicted in Figure 2, which is a reproduction of Figure 6.1.2-1 of 3GPP TS 38.401 V18.0.0. Further details about the gNB split architecture are provided in the excerpt from 3GPP TS 38.401 below.

[0009] ***** START EXCERPT FROM 3GPP TS 38.401 VI 8.0.0 *****

[0010] 6.1.1 Overall Architecture of NG-RAN

[0011] [SEE FIGURE 1]

[0012] Figure 6.1-1 : Overall architecture

[0013] The NG-RAN consists of a set of gNBs connected to the 5GC through the NG interface.

[0014] NOTE: As specified in TS 38.300 [2], NG-RAN could also consists of a set of ng-eNBs, an ng-eNB may consist of an ng-eNB-CU and one or more ng-eNB-DU(s). An ng-eNB-CU and an ng- eNB-DU is connected via W1 interface. The general principle described in this clause also applies to ng-eNB and W1 interface, if not explicitly specified otherwise.

[0015] An gNB can support FDD mode, TDD mode or dual mode operation. gNBs can be interconnected through the Xn interface.

[0016] A gNB may consist of a gNB-CU and one or more gNB-DU(s). A gNB-CU and a gNB-DU is connected via F1 interface. One gNB-DU is connected to only one gNB-CU.

[0017] NOTE: In case of network sharing with multiple cell ID broadcast, each Cell Identity associated with a subset of PLMNs corresponds to a gNB-DU and the gNB-CU it is connected to, i.e. the corresponding gNB-DUs share the same physical layer cell resources.

[0018] NOTE: For resiliency, a gNB-DU may be connected to multiple gNB-CUs by appropriate implementation.

[0019] NG, Xn and F1 are logical interfaces.

[0020] For NG-RAN, the NG and Xn-C interfaces for a gNB consisting of a gNB-CU and gNB-DUs, terminate in the gNB-CU. For EN-DC, the S1-U and X2-C interfaces for a gNB consisting of a gNB-CU and gNB-DUs, terminate in the gNB-CU. The gNB-CU and connected gNB-DUs are only visible to other gNBs and the 5GC as a gNB. A possible deployment scenario is described in Annex A.

[0021] The node hosting user plane part of NR PDCP (e.g. gNB-CU, gNB-CU-UP, and for EN-DC, MeNB or SgNB depending on the bearer split) shall perform user inactivity monitoring and further informs its inactivity or (re)activation to the node having C-plane connection towards the core network (e.g. over E1 , X2). The node hosting NR RLC (e.g. gNB-DU) may perform user inactivity monitoring and further inform its inactivity or (re)activation to the node hosting control plane, e.g. gNB-CU or gNB-CU-CP.

[0022] UL PDCP configuration (i.e. how the UE uses the UL at the assisting node) is indicated via X2-C (for EN- DC), Xn-C (for NG-RAN) and F1-C. Radio Link Outage / Resume for DL and / or UL is indicated via X2-U (for EN-DC), Xn-U (for NG-RAN) and F1-U.

[0023] The NG-RAN is layered into a Radio Network Layer (RNL) and a Transport Network Layer (TNL).

[0024] The NG-RAN architecture, i.e. the NG-RAN logical nodes and interfaces between them, is defined as part of the RNL.

[0025] For each NG-RAN interface (NG, Xn, F1) the related TNL protocol and the functionality are specified. The TNL provides services for user plane transport, signalling transport.

[0026] In NG-Flex configuration, each NG-RAN node is connected to all AMFs of AMF Sets within an AMF Region supporting at least one slice also supported by the NG-RAN node. The AMF Set and the AMF Region are defined in TS 23.501 [3],

[0027] If security protection for control plane and user plane data on TNL of NG-RAN interfaces has to be supported, NDS / IP TS 33.501

[0013] shall be applied.

[0028] 6.1.2 Overall architecture for separation of gNB-CU-CP and gNB-CU- UP

[0029] The overall architecture for separation of gNB-CU-CP and gNB-CU-UP is depicted in Figure 6.1 .2-1 .

[0030] NOTE: NG-RAN could also consist of a set of ng-eNBs, an ng-eNB may consist of an ng-eNB-CU- CP, one or more ng-eNB-CU-UP(s), and one or more ng-eNB-DU(s). An ng-eNB-CU-CP and an ng-eNB-CU-UP is connected via the E1 interface. An ng-eNB-DU is connected to an ng- eNB-CU-CP via the W1-C interface, and to an ng-eNB-CU-UP via the W1-U interface. The general principle described in this clause also applies to ng-eNB and its corresponding E1 and W1 interfaces, if not explicitly specified otherwise.

[0031] [SEE FIGURE 2]

[0032] Figure 6.1.2-1. Overall architecture for separation of gNB-CU-CP and gNB-CU-UP

[0033] - A gNB may consist of a gNB-CU-CP, multiple gNB-CU-UPs and multiple gNB-DUs;

[0034] - The gNB-CU-CP is connected to the gNB-DU through the F1-C interface;

[0035] - The gNB-CU-UP is connected to the gNB-DU through the F1-U interface; - The gNB-CU-UP is connected to the gNB-CU-CP through the E1 interface;

[0036] - One gNB-DU is connected to only one gNB-CU-CP;

[0037] - One gNB-CU-UP is connected to only one gNB-CU-CP;

[0038] NOTE 1 : For resiliency, a gNB-DU and / or a gNB-CU-UP may be connected to multiple gNB-CU- CPs by appropriate implementation.

[0039] - One gNB-DU can be connected to multiple gNB-CU-UPs under the control of the same gNB-CU- CP;

[0040] - One gNB-CU-UP can be connected to multiple DUs under the control of the same gNB-CU-CP;

[0041] NOTE 2: The connectivity between a gNB-CU-UP and a gNB-DU is established by the gNB-CU-CP using Bearer Context Management functions.

[0042] NOTE 3: The gNB-CU-CP selects the appropriate gNB-CU-UP(s) for the requested services for the UE. In case of multiple CU-UPs they belong to same security domain as defined in TS 33.210

[0018] ,

[0043] NOTE 4: Data forwarding between gNB-CU-UPs during Intra-gNB-CU-CP handover within a gNB may be supported by Xn-U.

[0044] *****ENDEXCERPT FROM 3GPP TS 38.401 V18.0.0 *****

[0045] The 3 GPP Release (Rel)-18 work item on enhanced Reduced Capability (eRedCap) introduced enhancements of Rel-17 RedCap functionality by introducing features for further User Equipment (UE) complexity reduction through UE peak data rate reduction and UE baseband bandwidth reduction and further UE power saving through enhancements to enhanced Discontinuous Reception (eDRX) in Radio Resource Control (RRC) Inactive state to expand the market for RedCap use cases with low-tier eRedCap devices similar to Long Term Evolution (LTE) UE category 1 / 1 bis, between existing 3GPP Low Power Wireless Access (LPWA) (i.e., Narrowband Internet of Things (NB-IoT) / LTE Machine Type Communication (LTE-MTC)) devices and Rel-17 RedCap devices.

[0046] Early indications have been specified for eRedCap UEs in a manner similar to that specified as for Rel-17 RedCap UEs in the Uu and Fl interfaces. This means that an eRedCap UE always indicates in Msg3 Physical Uplink Shared Channel (PUSCH) in the case of 4-step random access procedure (or MsgA PUSCH in case of 2-step random access procedure) using a special Logical Channel Identity (LCID) that it is an eRedCap UE, and that it also indicates this in Msgl (i.e., Physical Random Access Channel (PRACH) preamble) if the gNB has configured eRedCap-specific PRACH resources.

[0047] Access barring bits have been specified for eRedCap UEs in a manner that is similar to that specified for Rel-17 RedCap UEs in the Uu, Xn, and Fl interfaces. This means that the gNB can indicate separately for 1 -receive branch (Rx) eRedCap UEs and 2-Rx eRedCap UEs whether they are allowed to access the cell or not. Summary

[0048] Systems and methods related to exempting User Equipments (UEs) from cell barring or allowing UEs to bypass cell barring are disclosed. In one embodiment, a method performed by a first node for a Radio Access Network (RAN) of a cellular communications system comprises sending, to a second node, information that indicates that the first node is exempting UEs or one or more certain groups of UEs from cell barring in case of emergency traffic. In one embodiment, the information indicates that the first node is exempting one or more certain groups of UEs from cell barring in case of emergency. In this manner, bypassing of cell barring due to an emergency is enabled.

[0049] In one embodiment, the one or more certain groups of UEs comprise UEs having a single receiver chain.

[0050] In one embodiment, the first node is a first network node, and the second node is a second network node. In one embodiment, sending the information that indicates that the first network node is exempting UEs or one or more certain groups of UEs from cell barring in case of emergency traffic comprises sending the information as part of XnAP Served Cell Information NR Information Element (IE). In another embodiment, sending the information that indicates that the first network node is exempting UEs or one or more certain groups of UEs from cell barring in case of emergency traffic comprises sending the information as part of a RedCap Broadcast Information IE or an eRedCap Broadcast Information IE within an XnAP Served Cell Information NR IE. In another embodiment, sending the information that indicates that the first network node is exempting UEs or one or more certain groups of UEs from cell barring in case of emergency traffic comprises sending the information as a new System Information Block (SIB) information element.

[0051] In one embodiment, the first node is a first part of a network node, and the second node is a second part of the network node. In one embodiment, the network node is a gNodeB, the first part of the network node is a gNodeB Distributed Unit, and the second part of the network node is a gNodeB Central Unit. In one embodiment, sending the information that indicates that the first part of the network node is exempting UEs or one or more certain groups of UEs from cell barring in case of emergency traffic comprises sending the information as part of F1AP Served Cell Information NR IE. In another embodiment, sending the information that indicates that the first part of the network node is exempting UEs or one or more certain groups of UEs from cell barring in case of emergency traffic comprises sending the information as part of a RedCap Broadcast Information IE or an eRedCap Broadcast Information IE within an F1AP Served Cell Information NR IE. In another embodiment, sending the information that indicates that the first part of the network node is exempting UEs or one or more certain groups of UEs from cell barring in case of emergency traffic comprises sending the information as a new SIB information element.

[0052] Corresponding embodiments of a first node for a RAN of a cellular communications system are also disclosed. In one embodiment, a first node for a RAN of a cellular communications system is adapted to send, to a second node, information that indicates that the first node is exempting UEs or one or more certain groups of UEs from cell barring in case of emergency traffic.

[0053] In another embodiment, a first node for a RAN of a cellular communications system comprises processing circuitry configured to cause the first node to send, to a second node, information that indicates that the first node is exempting UEs or one or more certain groups of UEs from cell barring in case of emergency traffic.

[0054] Embodiments of a method performed by a second node for a RAN of a cellular communications system are also disclosed. In one embodiment, the method performed by the second node of the RAN of the communications system comprises receiving, from a first node, information that indicates that the first node is exempting UEs or one or more certain groups of UEs from cell barring in case of emergency traffic.

[0055] In one embodiment, the information indicates that the first node is exempting one or more certain groups of UEs from cell barring in case of emergency. In one embodiment, the one or more certain groups of UEs comprise UEs having a single receiver chain.

[0056] In one embodiment, the first node is a first network node, and the second node is a second network node. In one embodiment, receiving the information that indicates that the first network node is exempting UEs or one or more certain groups of UEs from cell barring in case of emergency traffic comprises receiving the information as part of XnAP Served Cell Information NR IE. In another embodiment, receiving the information that indicates that the first network node is exempting UEs or one or more certain groups of UEs from cell barring in case of emergency traffic comprises receiving the information as part of a RedCap Broadcast Information IE or an eRedCap Broadcast Information IE within an XnAP Served Cell Information NR IE. In another embodiment, receiving the information that indicates that the first network node is exempting UEs or one or more certain groups of UEs from cell barring in case of emergency traffic comprises receiving the information as a new SIB information element.

[0057] In one embodiment, the method further comprises performing one or more actions based on the received information that indicates that the first network node is exempting UEs or one or more certain groups of UEs from cell barring in case of emergency traffic. In one embodiment, performing the one or more actions comprises handing over a particular UE from the second network node to the first network node, the particular UE being one of the exempted UEs or one of the one or more certain groups of exempted UEs and having emergency traffic. In another embodiment, performing the one or more actions comprises refraining from handing over a particular UE from the second network node to the first network node, the particular UE being a barred UE that is not one of the exempted UEs or one of the one or more certain groups of exempted UEs having emergency traffic.

[0058] In one embodiment, the received information that indicates that the first network node is exempting UEs or one or more certain groups of UEs from cell barring in case of emergency traffic is a hard requirement. In one embodiment, performing the one or more actions comprises refraining from handing over a particular UE from the second network node to the first network node even if there is no other alternatives for handover of the particular UE, the particular UE being a barred UE that is not one of the exempted UEs or one of the one or more certain groups of exempted UEs having emergency traffic.

[0059] In one embodiment, the received information that indicates that the first network node is exempting UEs or one or more certain groups of UEs from cell barring in case of emergency traffic is a soft requirement. In one embodiment, performing the one or more actions comprises handing over a particular UE from the second network node to the first network node, the particular UE not being one of the exempted UEs or one of the one or more certain groups of exempted UEs having emergency traffic, but where there are no alternatives for handover of the particular UE.

[0060] In one embodiment, the first node is a first part of a network node, and the second node is a second part of the network node. In one embodiment, the network node is a gNodeB, the first part of the network node is a gNodeB Distributed Unit, and the second part of the network node is a gNodeB Central Unit. In one embodiment, receiving the information that indicates that the first part of the network node is exempting UEs or one or more certain groups of UEs from cell barring in case of emergency traffic comprises receiving the information as part of F1AP Served Cell Information NR IE. In another embodiment, receiving the information that indicates that the first part of the network node is exempting UEs or one or more certain groups of UEs from cell barring in case of emergency traffic comprises receiving the information as part of a RedCap Broadcast Information IE or an eRedCap Broadcast Information IE within an F1AP Served Cell Information NR IE. In another embodiment, receiving the information that indicates that the first part of the network node is exempting UEs or one or more certain groups of UEs from cell barring in case of emergency traffic comprises receiving the information as a new SIB information element, e.g., within an Fl AP Served Cell Information NR IE.

[0061] In one embodiment, the method further comprises performing one or more actions based on the received information that indicates that the first part of the network node is exempting UEs or one or more certain groups of UEs from cell barring in case of emergency traffic. In one embodiment, performing the one or more actions comprises sending an indication to another network node or a part of another network node that indicates which cell(s) (e.g., which cell(s) served by the first part of the network node) allow a barred UE to communicate emergency traffic.

[0062] Corresponding embodiments of a second node for a RAN of a cellular communications system are also disclosed. In one embodiment, a second node for a RAN of a cellular communications system is adapted to receive, from a first node, information that indicates that the first node is exempting UEs or one or more certain groups of UEs from cell barring in case of emergency traffic.

[0063] In another embodiment, a second node for a RAN of a cellular communications system comprises processing circuitry configured to cause the second node to receive, from a first node, information that indicates that the first node is exempting UEs or one or more certain groups of UEs from cell barring in case of emergency traffic.

[0064] Brief Description of the Drawings

[0065] The accompanying drawing figures incorporated in and forming a part of this specification illustrate several aspects of the disclosure, and together with the description serve to explain the principles of the disclosure.

[0066] Figure 1 illustrates the Next Generation Radio Access Network (NG-RAN) architecture as specified in 3rdGeneration Partnership Project (3GPP) Technical Specification (TS) 38.401 V18.0.0;

[0067] Figure 2 illustrates a gNodeB (gNB) with a split Control Plane (CP) / User Plane (UP) architecture as specified in 3GPP TS 38.401;

[0068] Figure 3 illustrates the operation of a first network node (e.g., a first gNB) and a second network node (e.g., a second gNB), in accordance with an embodiment of the present disclosure;

[0069] Figure 4 illustrates the operation of a first network node part (e.g., a gNB-Distributed Unit (DU)) and a second network node part (e.g., a gNB-Central Unit (CU)), in accordance with an embodiment of the present disclosure; Figure 5 shows an example of a communication system in which embodiments of the present disclosure may be implemented;

[0070] Figure 6 shows a User Equipment (UE) in accordance with some embodiments;

[0071] Figure 7 shows a network node in accordance with some embodiments;

[0072] Figure 8 is a block diagram of a host 800, which may be an embodiment of the host of Figure 5, in accordance with various aspects described herein;

[0073] Figure 9 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized; and

[0074] Figure 10 shows a communication diagram of a host communicating via a network node with a UE over a partially wireless connection in accordance with some embodiments.

[0075] Detailed Description

[0076] The embodiments set forth below represent information to enable those skilled in the art to practice the embodiments and illustrate the best mode of practicing the embodiments. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the disclosure and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the disclosure.

[0077] 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.

[0078] There currently exist certain challenge(s). 3rdGeneration Partnership Project (3GPP) Radio Access Network (RAN) Working Group 2 (WG2) (i.e., RAN2) will discuss as part of Release (Rel)-18 Technical Enhancements and Improvements (TEI) whether it is possible for a User Equipment (UE) to select / reselect in a cell that has status “barred”, or to be treated as if the cell status is “barred” for the purpose of emergency call.

[0079] For Rel-17 Reduced Capability (RedCap) and Rel-18 enhanced RedCap (eRedCap) UE, the barring indication is indicated as shown in the text below from 3GPP Technical Specification (TS) 38.331:

[0080] 1> if the UE is a RedCap UE and it is in RRC IDLE or in RRC IN ACTIVE, or if the RedCap UE is in RRC CONNECTED while T311 is running:

[0081] 2> if intraFreqReselectionRedCap is not present in SIB1:

[0082] 3> consider the cell as barred in accordance with TS 38.304

[0020] ; 3> perform barring as if IntraFreqReselectionRedCap is set to allowed, upon which the procedure ends;

[0083] 2> else:

[0084] 3> if the cellBarredRedCaplRx is present in the acquired SIB1 and is set to barred and the UE is equipped with 1 Rx branch; or

[0085] 3> if the cellBarredRedCap2Rx is present in the acquired SIB1 and is set to barred and the UE is equipped with 2 Rx branches; or

[0086] 3> if the halfDuplexRedCapAllowed is not present in the acquired SIB1 and the UE supports only half-duplex FDD operation:

[0087] 4> consider the cell as barred in accordance with TS 38.304

[0020] ;

[0088] 4> perform barring based on intraFreqReselectionRedCap as specified in TS 38.304

[0020] , upon which the procedure ends;

[0089] To enable an exception to the barring for IRx or 2Rx (e)RedCap UE(s), a new parameter may be introduced in System Information Block (SIB) 1 (SIB1). The New Radio (NR) base station (gNB) may indicate as part of the system broadcast information, e.g., in SIB1, that the gNB allows such UEs, e.g. IRX (e)RedCap UE or 2RX (e)RedCap UE, to bypass barring, if enabled in the serving cell, to make emergency calls.

[0090] However, for mobility purposes and in the case of a split gNB scenario, exchange of information on whether barring exemption is enabled as part of the system information broadcast between gNBs and from gNB-Distributed Unit (DU) to gNB-Central Unit (CU) requires signaling support. This is important because, in case of mobility, without such information, i.e., that such UEs can bypass barring in neighboring cells, a gNB-CU cannot indicate which node allows such an exception for emergency calls, thereby preventing the source node of handing over the UE to other target nodes where the UE can make an emergency call.

[0091] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. Embodiments of the solution(s) described herein may include either or both of the following aspects:

[0092] 1) Fl AP is enhanced accordingly, to indicate whether the gNB-DU enables (i.e., allows), e.g., as part of its system information broadcast or serving cell information, that a UE, e.g., a IRX RedCap or 1 RX eRedCap UE, can bypass barring, if barring is set, to perform emergency calls.

[0093] 2) XnAP is enhanced accordingly, to indicate whether the gNB-CU enables (i.e., allows), e.g., as part of its system information broadcast or serving cell information, that a UE, e.g., a 1RX RedCap or 1 RX eRedCap UE, can bypass barring, if baring is set, to perform emergency calls.

[0094] Certain embodiments may provide one or more of the following technical advantage(s). Embodiments of the present disclosure may allow communication of the configuration of a parameter(s) provided in system information broadcast, e.g., SIB1, from gNB-DU to gNB-CU and from gNB-CU to other gNB-CU for the purpose of mobility of UEs that are barred otherwise, in case the node allows bypassing of barring due to emergency call and / or PDU session.

[0095] Now, a more detailed description of exemplary embodiments of the present disclosure will be provided. Below inter-node indications in a network are described that allow, for example, a first gNB to know if a second gNB allows UEs to be exempt from barring in case the UEs have ongoing, or will soon have ongoing, emergency traffic.

[0096] The semantics used below to describe this indication is that it is a barring exemption for UEs, e.g., 1 Rx (e)RedCap UEs. But another possible approach is that the indication indicates that the UE shall consider the cell as an acceptable cell. An “acceptable cell” is defined in 3GPP TS 38.304 V17.2.0 section 4.5 as shown below: acceptable cell:

[0097] An "acceptable cell" is a cell on which the UE may camp to obtain limited service (originate emergency calls and receive ETWS and CMAS notifications). Such a cell shall fulfil the following requirements, which is the minimum set of requirements to initiate an emergency call and to receive ETWS and CMAS notification in an NR network:

[0098] The cell is not barred, see clause 5.3.1;

[0099] The cell selection criteria are fulfilled, see clause 5.2.3.2.

[0100] As an alternative to being “acceptable”, a cell can be considered a “suitable cell” which allows the UE to also do non-emergency services. That definition is also provided in 3GPP TS 38.304 V17.2.0 section 4.5.

[0101] A UE being exempt from barring for the purpose of communicating emergency traffic is, in some ways, similar to that a UE being able to consider the cell as acceptable. Also, it should be appreciated that even if in the description below it will be used as example that the feature allows a UE to be “exempt from barring”, the embodiments could be applied to a case when the indication indicates whether a UE shall consider the cell as acceptable, i.e., embodiments of the solution(s) described herein can be applied to different semantics of this functionality. Inter-Node Signaling

[0102] In one embodiment, a first network node indicates to a second network node that the first network node is exempting UEs, e.g., IRx UEs, from barring in case of emergency communication. In one embodiment, the first network node is a first gNB, and the second network node is a second gNB, and this indication is sent from the first gNB to the second gNB over an Xn-interface. In this regard, Figure 3 illustrates the operation of a first network node 300-1 (e.g., a first gNB) and a second network node 300-2 (e.g., a second gNB), in accordance with an embodiment of the present disclosure. Optional steps are represented by dashed lines. As illustrated, the first network node 300-1 sends, to the second network node 300-2, information that indicates that the first network node 300-1 is exempting UEs (e.g., one or more certain groups of UEs such as, e.g., IRx UEs) from cell barring in the case of emergency traffic (step 302). Optionally, the second network node 300-2 performs one or more actions (e.g., handover or refrain from handing over UEs (e.g., one or more certain groups of UEs such as, e.g., IRx UEs) from the second network node 300-2 to the first network node 300-1), based on the information received in step 302 (step 304).

[0103] Further, in one embodiment, a first part of a gNB may indicate to a second part of the gNB, e.g. in case of split gNB architecture a gNB-DU may signal to a gNB-CU over Fl interface, how the first part of the gNB (e.g., gNB-DU) encoded the barring exemption for, e.g., IRx UEs in the system information broadcast, so that the second part of the gNB (e.g., gNB-CU) can use this information to indicate to another gNB-CU which cells allow a barred UE to communicate emergency traffic. Further, the passing of this information from gNB-DU to gNB- CU is also desirable for intra-gNB mobility. In this regard, Figure 4 illustrates the operation of a first network node part 400-1 (e.g., a gNB-DU) and a second network node part 400-2 (e.g., a gNB-CU), in accordance with an embodiment of the present disclosure. Optional steps are represented by dashed lines. As illustrated, the first network node part 400-1 sends, to the second network node part 400-2, information that indicates how the first network node part 400-1 encoded cell barring exemption for UEs (e.g., for one or more certain groups of UEs such as, e.g., IRx UEs) in the case of emergency traffic in broadcast system information broadcast in a cell(s) served by the first network node part 400-1 (step 402). Optionally, the second network node part 400-2 performs one or more actions, based on the received information (step 404). These one or more actions may include, for example, indicating to another network node or network node part (e.g., another gNB-CU of another gNB) which cell(s) (which cell(s) served by the first network node part 400-1 allow a barred UE (or certain group(s) of barred UEs) to communicate emergency traffic. Below, example implementations of these indications are described.

[0104] Example Implementations

[0105] One example implementation of some example embodiments of the present disclosure is as follows:

[0106] F1AP:

[0107] 1) In one embodiment, a new bit indicating whether, e.g., IRx RedCap UE is allowed access by the gNB-DU cells for emergency call is introduced in the RedCap Broadcast Information IE in the Fl AP Served Cell Information NR IE (9.3.1.10). In one embodiment, the Fl AP Served Cell Information NR IE including the RedCap Broadcast

[0108] Information IE (which includes the new bit) corresponds to or is part of the information sent in step 402 of Figure 4.

[0109] • In a first option (“option 1”), the new bit is introduced as highlighted via bold, underlined text below. • Alternatively, in a second option (“option 2”), the new bit can be a new SIB information element, generic for any UE (IRX UE or others) e.g., the first node indicates to second node the barring exemption is allowed for emergency communication, as highlighted via bold, italicized text below.

[0110] 2) In one embodiment (possibly in addition to that described in 1) above), a new bit indicating whether a UE, e.g., IRx eRedCap UE, is allowed access by the gNB-DU cells for emergency call is introduced the eRedCap Broadcast Information IE in the F1AP Served Cell Information NR IE (9.3.1.10). In one embodiment, the Fl AP Served Cell

[0111] Information NR IE including the eRedCap Broadcast Information IE (which includes the new bit) corresponds to or is part of the information sent in step 402 of Figure 4.

[0112] • In a first option (“option 1”), the new bit can be introduced as highlighted via bold, underlined text below. • Alternatively, in a second option (“option 2”), the new bit can be a new SIB information element, generic for any UE, e.g., the first node indicates to second node the barring exemption is allowed for emergency communication as highlighted via bold, italicized text below.

[0113]

[0114] XnAP:

[0115] 3) In one embodiment (possibly in addition to that described in 1) and / or 2) above), a new bit indicating whether a UE, e.g., IRx RedCap UE, is allowed access by the gNB-CU cell for emergency call is introduced in the RedCap Broadcast Information IE in the XnAP

[0116] Served Cell Information NR IE (9.2.2.11). In one embodiment, the XnAP Served Cell Information NR IE including the RedCap Broadcast Information IE (which includes the new bit) corresponds to or is part of the information sent in step 302 of Figure 3.

[0117] • In a first option (“option 1”), the new bit can be introduced as highlighted via bold, underlined text below.

[0118] • Alternatively, in a second option (“option 2”), the new bit can be a new SIB information element, generic for any UE (IRX UE, or others), e.g., the first node indicates to second node the barring exemption is allowed for emergency communication as highlighted via bold, italicized text below.

[0119] 4) In one embodiment (possibly in addition to that described in 1) and / or 2) and / or 3) above), anew bit indicating whether a UE, e.g., IRx eRedCap UE, is allowed access by the gNB-CU cells for emergency call is introduced the eRedCap Broadcast Information IE in the XnAP Served Cell Information NR IE (9.2.2.11). In one embodiment, the XnAP

[0120] Served Cell Information NR IE including the eRedCap Broadcast Information IE (which includes the new bit) corresponds to or is part of the information sent in step 302 of Figure 3.

[0121] • In a first option (“option 1”), the new bit can be introduced as highlighted via bold, underlined text below.

[0122] • Alternatively, in a second option (“option 2”), the new bit can be a new SIB information element, generic for any UE, e.g., the first node indicates to second node the barring exemption is allowed for emergency communication as highlighted via bold, italicized text below.

[0123]

[0124] Use of the New Indication

[0125] Above, signaling has been described that allows a second network node (e.g., a second gNB) to know if a first network node (e.g., a first gNB) would allow barring exemption emergency traffic over Xn interface (see, e.g., step 302 of Figure 3). Signaling has also been described that allows a first part of a network node (e.g., a gNB-DU) to indicate to a second network node (e.g., gNB-CU) over Fl interface how the barring exemption for emergency traffic is encoded and whether it is allowed (see, e.g., step 402 of Figure 4).

[0126] If a second network node (e.g., a second gNB) gets an indication from a first network node (e.g., a first gNB) that the first network node is applying a barring exemption for a first group of UEs, the second network node may hand over UEs of that first group to the first network node (e.g., in step 304 of Figure 3). However, if the first network node indicates to the second network node that barring exemption is not applied by the first network node for the first group of UEs, the second node may refrain from handing over UEs of the first group to the first network node (e.g., in step 304 of Figure 3).

[0127] However, it may be so that there is no other cell which can serve a UE of the first group, i.e. the second network node has no other alternative than to hand over the UE to the first network node. According to a first approach, the second network node may in this situation hand over the UE of the first group to the second network node anyway assuming that it is important to ensure that the UE’s connection to the network is maintained (e.g., in step 304 of Figure 3). Alternatively, according to a second approach, the second network node may refrain from handing over the UE to the first network node meaning that the second network node would strictly adhere to the indication from the first network node (e.g., in step 304 of Figure 3).

[0128] Hard or Soft Requirement

[0129] In a further embodiment, the inter-node signaling from the first network node to the second network node (e.g., in step 302 of Figure 3) not only indicates if barring exemption is applied or not, but it further indicates if this is a hard requirement, or a soft requirement. In one embodiment, in the case of a hard requirement, the first network node does not accept that a UE is handed over to the first network node even if there is no other alternatives (see “second approach” above). Conversely, in the case of a soft requirement, the first network node can accept that the second network node hands over a UE to the first network node if there is no other alternative node to which the second network node can hand over the UE.

[0130] Further Description

[0131] Figure 5 shows an example of a communication system 500 in which embodiments of the present disclosure may be implemented.

[0132] In the example, the communication system 500 includes a telecommunication network 502 that includes an access network 504, such as a Radio Access Network (RAN), and a core network 506, which includes one or more core network nodes 508. The access network 504 includes one or more access network nodes, such as network nodes 510A and 510B (one or more of which may be generally referred to as network nodes 510), or any other similar Third Generation Partnership Project (3GPP) access nodes or non-3GPP Access Points (APs). Note that the first and second network nodes described above (e.g., first network node 300-1 and second network node 300-2) may correspond to two of the network nodes 510, respectively. In a similar manner, the first and second parts of a network node (e.g., first network node part 400-1 and second network node part 400-2) may be different parts within one of the network nodes 510. 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 502 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network 502 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 502, including one or more network nodes 510 and / or core network nodes 508.

[0133] 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 network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, 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 0-2 interface defined by the O-RAN Alliance or comparable technologies. The network nodes 510 facilitate direct or indirect connection of User Equipment (UE), such as by connecting UEs 512A, 512B, 512C, and 512D (one or more of which may be generally referred to as UEs 512) to the core network 506 over one or more wireless connections.

[0134] 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 500 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 500 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0135] The UEs 512 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 510 and other communication devices. Similarly, the network nodes 510 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 512 and / or with other network nodes or equipment in the telecommunication network 502 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 502.

[0136] In the depicted example, the core network 506 connects the network nodes 510 to one or more hosts, such as host 516. 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 506 includes one more core network nodes (e.g., core network node 508) 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 generally applicable to the corresponding components of the core network node 508. 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).

[0137] The host 516 may be under the ownership or control of a service provider other than an operator or provider of the access network 504 and / or the telecommunication network 502, and may be operated by the service provider or on behalf of the service provider. The host 516 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.

[0138] As a whole, the communication system 500 of Figure 5 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system 500 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 Second, Third, Fourth, or Fifth Generation (2G, 3G, 4G, or 5G) standards, or any applicable future generation standard (e.g., Sixth Generation (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.

[0139] In some examples, the telecommunication network 502 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunication network 502 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 502. For example, the telecommunication network 502 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 Internet of Things (loT) services to yet further UEs. In some examples, the UEs 512 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 504 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 504. Additionally, a UE may be configured for operating in single- or multi-Radio Access Technology (RAT) or multi -standard mode. For example, a UE may operate with any one or combination of WiFi, New Radio (NR), and LTE, i.e. being configured for Multi -Radio Dual Connectivity (MR-DC), such as Evolved UMTS Terrestrial RAN (E-UTRAN) NR - Dual Connectivity (EN-DC).

[0140] In the example, a hub 514 communicates with the access network 504 to facilitate indirect communication between one or more UEs (e.g., UE 512C and / or 512D) and network nodes (e.g., network node 510B). In some examples, the hub 514 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 514 may be a broadband router enabling access to the core network 506 for the UEs. As another example, the hub 514 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 510, or by executable code, script, process, or other instructions in the hub 514. As another example, the hub 514 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 514 may be a content source. For example, for a UE that is a Virtual Reality (VR) headset, display, loudspeaker or other media delivery device, the hub 514 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 514 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 514 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0141] The hub 514 may have a constant / persistent or intermittent connection to the network node 510B. The hub 514 may also allow for a different communication scheme and / or schedule between the hub 514 and UEs (e.g., UE 512C and / or 512D), and between the hub 514 and the core network 506. In other examples, the hub 514 is connected to the core network 506 and / or one or more UEs via a wired connection. Moreover, the hub 514 may be configured to connect to a Machine-to-Machine (M2M) service provider over the access network 504 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 510 while still connected via the hub 514 via a wired or wireless connection. In some embodiments, the hub 514 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 510B. In other embodiments, the hub 514 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and the network node 51 OB, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0142] Figure 6 shows a UE 600 in accordance with some embodiments. 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 Internet Protocol (VoIP) phone, wireless local loop phone, desktop computer, Personal Digital Assistant (PDA), wireless camera, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, Laptop Embedded Equipment (LEE), Laptop Mounted Equipment (LME), smart device, wireless Customer Premise Equipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3GPP, including a Narrowband Internet of Things (NB-IoT) UE, a Machine Type Communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0143] 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).

[0144] The UE 600 includes processing circuitry 602 that is operatively coupled via a bus 604 to an input / output interface 606, a power source 608, memory 610, a communication interface 612, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 6. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0145] The processing circuitry 602 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 610. The processing circuitry 602 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 602 may include multiple Central Processing Units (CPUs).

[0146] In the example, the input / output interface 606 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 600. 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.

[0147] In some embodiments, the power source 608 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 608 may further include power circuitry for delivering power from the power source 608 itself, and / or an external power source, to the various parts of the UE 600 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 608. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 608 to make the power suitable for the respective components of the UE 600 to which power is supplied.

[0148] The memory 610 may be or be configured to include memory such as Random Access Memory (RAM), Read Only Memory (ROM), Programmable ROM (PROM), Erasable PROM (EPROM), Electrically EPROM (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 610 includes one or more application programs 614, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 616. The memory 610 may store, for use by the UE 600, any of a variety of various operating systems or combinations of operating systems.

[0149] The memory 610 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 RAM (SDRAM), external micro-DIMM SDRAM, smartcard memory such as a tamper resistant module in the form of a Universal Integrated Circuit Card (UICC) including one or more Subscriber Identity Modules (SIMs), such as a Universal SIM (USIM) and / or Internet Protocol Multimedia Services Identity Module (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 a ‘SIM card. ’ The memory 610 may allow the UE 600 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 610, which may be or comprise a device-readable storage medium.

[0150] The processing circuitry 602 may be configured to communicate with an access network or other network using the communication interface 612. The communication interface 612 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 622. The communication interface 612 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 618 and / or a receiver 620 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 618 and receiver 620 may be coupled to one or more antennas (e.g., the antenna 622) and may share circuit components, software, or firmware, or alternatively be implemented separately.

[0151] In the illustrated embodiment, communication functions of the communication interface 612 may include cellular communication, WiFi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, NFC, 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 according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband CDMA (WCDMA), GSM, LTE, NR, UMTS, WiMax, Ethernet, Transmission Control Protocol / Intemet Protocol (TCP / IP), Synchronous Optical Networking (SONET), Asynchronous Transfer Mode (ATM), Quick User Datagram Protocol Internet Connection (QUIC), Hypertext Transfer Protocol (HTTP), and so forth.

[0152] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 612, 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).

[0153] 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.

[0154] A UE, when in the form of an loT 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 loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a television, 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, a smoke 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 head-mounted display for Augmented Reality (AR) or VR, a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or itemtracking 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 loT device comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE 600 shown in Figure 6.

[0155] As yet another specific example, in an loT 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, an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0156] 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.

[0157] Figure 7 shows a network node 700 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, APs (e.g., radio APs), Base Stations (BSs) (e.g., radio BSs, Node Bs, evolved Node Bs (eNBs), NR Node Bs (gNBs)), and O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O- CU).

[0158] 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 RRUs 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).

[0159] 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 BS 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).

[0160] The network node 700 includes processing circuitry 702, memory 704, a communication interface 706, and a power source 708. The network node 700 may be composed of multiple physically separate components (e.g., aNodeB component and an 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 700 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 700 may be configured to support multiple RATs. In such embodiments, some components may be duplicated (e.g., separate memory 704 for different RATs) and some components may be reused (e.g., a same antenna 710 may be shared by different RATs). The network node 700 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 700, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, Long Range Wide Area Network (LoRaWAN), Radio Frequency Identification (RFID), or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within the network node 700.

[0161] The processing circuitry 702 may comprise a combination of one or more of a microprocessor, controller, microcontroller, CPU, DSP, ASIC, FPGA, 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 700 components, such as the memory 704, to provide network node 700 functionality.

[0162] In some embodiments, the processing circuitry 702 includes a System on a Chip (SOC). In some embodiments, the processing circuitry 702 includes one or more of Radio Frequency (RF) transceiver circuitry 712 and baseband processing circuitry 714. In some embodiments, the RF transceiver circuitry 712 and the baseband processing circuitry 714 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 the RF transceiver circuitry 712 and the baseband processing circuitry 714 may be on the same chip or set of chips, boards, or units.

[0163] The memory 704 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, RAM, 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 702. The memory 704 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 702 and utilized by the network node 700. The memory 704 may be used to store any calculations made by the processing circuitry 702 and / or any data received via the communication interface 706. In some embodiments, the processing circuitry 702 and the memory 704 are integrated.

[0164] The communication interface 706 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 706 comprises port(s) / terminal(s) 716 to send and receive data, for example to and from a network over a wired connection. The communication interface 706 also includes radio front-end circuitry 718 that may be coupled to, or in certain embodiments a part of, the antenna 710. The radio front-end circuitry 718 comprises filters 720 and amplifiers 722. The radio front-end circuitry 718 may be connected to the antenna 710 and the processing circuitry 702. The radio front-end circuitry 718 may be configured to condition signals communicated between the antenna 710 and the processing circuitry 702. The radio front-end circuitry 718 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 718 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of the filters 720 and / or the amplifiers 722. The radio signal may then be transmitted via the antenna 710. Similarly, when receiving data, the antenna 710 may collect radio signals which are then converted into digital data by the radio front-end circuitry 718. The digital data may be passed to the processing circuitry 702. In other embodiments, the communication interface 706 may comprise different components and / or different combinations of components. In certain alternative embodiments, the network node 700 does not include separate radio front-end circuitry 718; instead, the processing circuitry 702 includes radio front-end circuitry and is connected to the antenna 710. Similarly, in some embodiments, all or some of the RF transceiver circuitry 712 is part of the communication interface 706. In still other embodiments, the communication interface 706 includes the one or more ports or terminals 716, the radio frontend circuitry 718, and the RF transceiver circuitry 712 as part of a radio unit (not shown), and the communication interface 706 communicates with the baseband processing circuitry 714, which is part of a digital unit (not shown).

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

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

[0167] The power source 708 provides power to the various components of the network node 700 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 708 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 700 with power for performing the functionality described herein. For example, the network node 700 may be connectable to an external power source (e.g., the power grid or an electricity outlet) via input circuitry or an interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 708. As a further example, the power source 708 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.

[0168] Embodiments of the network node 700 may include additional components beyond those shown in Figure 7 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 700 may include user interface equipment to allow input of information into the network node 700 and to allow output of information from the network node 700. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 700.

[0169] Figure 8 is a block diagram of a host 800, which may be an embodiment of the host 516 of Figure 5, in accordance with various aspects described herein. As used herein, the host 800 may be or comprise various combinations of hardware and / or software including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. The host 800 may provide one or more services to one or more UEs.

[0170] The host 800 includes processing circuitry 802 that is operatively coupled via a bus 804 to an input / output interface 806, a network interface 808, a power source 810, and memory 812. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 6 and 7, such that the descriptions thereof are generally applicable to the corresponding components of the host 800.

[0171] The memory 812 may include one or more computer programs including one or more host application programs 814 and data 816, which may include user data, e.g. data generated by a UE for the host 800 or data generated by the host 800 for a UE. Embodiments of the host 800 may utilize only a subset or all of the components shown. The host application programs 814 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), Moving Picture Experts Group (MPEG), VP9) and audio codecs (e.g., Free Lossless Audio Codec (FLAC), Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, and heads-up display systems). The host application programs 814 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host 800 may select and / or indicate a different host for Over-The-Top (OTT) services for a UE. The host application programs 814 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (DASH or MPEG-DASH), etc. Figure 9 is a block diagram illustrating a virtualization environment 900 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 900 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 900 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.

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

[0173] Hardware 904 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 906 (also referred to as hypervisors or VM Monitors (VMMs)), provide VMs 908A and 908B (one or more of which may be generally referred to as VMs 908), and / or perform any of the functions, features, and / or benefits described in relation with some embodiments described herein. The virtualization layer 906 may present a virtual operating platform that appears like networking hardware to the VMs 908.

[0174] The VMs 908 comprise virtual processing, virtual memory, virtual networking, or interface and virtual storage, and may be run by a corresponding virtualization layer 906. Different embodiments of the instance of a virtual appliance 902 may be implemented on one or more of the VMs 908, 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.

[0175] In the context of NFV, a VM 908 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 908, and that part of the hardware 904 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs 908, 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 908 on top of the hardware 904 and corresponds to the application 902.

[0176] The hardware 904 may be implemented in a standalone network node with generic or specific components. The hardware 904 may implement some functions via virtualization. Alternatively, the hardware 904 may be part of a larger cluster of hardware (e.g., such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 910, which, among others, oversees lifecycle management of the applications 902. In some embodiments, the hardware 904 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 RAN or a base station. In some embodiments, some signaling can be provided with the use of a control system 912 which may alternatively be used for communication between hardware nodes and radio units.

[0177] Figure 10 shows a communication diagram of a host 1002 communicating via a network node 1004 with a UE 1006 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as the UE 512A of Figure 5 and / or the UE 600 of Figure 6), the network node (such as the network node 510A of Figure 5 and / or the network node 700 of Figure 7), and the host (such as the host 516 of Figure 5 and / or the host 800 of Figure 8) discussed in the preceding paragraphs will now be described with reference to Figure 10.

[0178] Like the host 800, embodiments of the host 1002 include hardware, such as a communication interface, processing circuitry, and memory. The host 1002 also includes software, which is stored in or is accessible by the host 1002 and executable by the processing circuitry. The software includes a host application that may be operable to provide a service to a remote user, such as the UE 1006 connecting via an OTT connection 1050 extending between the UE 1006 and the host 1002. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection 1050.

[0179] The network node 1004 includes hardware enabling it to communicate with the host 1002 and the UE 1006. The connection 1060 may be direct or pass through a core network (like the core network 506 of Figure 5) and / or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet.

[0180] The UE 1006 includes hardware and software, which is stored in or accessible by the UE 1006 and executable by the UE’s processing circuitry. The software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via the UE 1006 with the support of the host 1002. In the host 1002, an executing host application may communicate with the executing client application via the OTT connection 1050 terminating at the UE 1006 and the host 1002. In providing the service to the user, the UE's client application may receive request data from the host's host application and provide user data in response to the request data. The OTT connection 1050 may transfer both the request data and the user data. The UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT connection 1050.

[0181] The OTT connection 1050 may extend via the connection 1060 between the host 1002 and the network node 1004 and via a wireless connection 1070 between the network node 1004 and the UE 1006 to provide the connection between the host 1002 and the UE 1006. The connection 1060 and the wireless connection 1070, over which the OTT connection 1050 may be provided, have been drawn abstractly to illustrate the communication between the host 1002 and the UE 1006 via the network node 1004, without explicit reference to any intermediary devices and the precise routing of messages via these devices.

[0182] As an example of transmitting data via the OTT connection 1050, in step 1008, the host 1002 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE 1006. In other embodiments, the user data is associated with a UE 1006 that shares data with the host 1002 without explicit human interaction. In step 1010, the host 1002 initiates a transmission carrying the user data towards the UE 1006. The host 1002 may initiate the transmission responsive to a request transmitted by the UE 1006. The request may be caused by human interaction with the UE 1006 or by operation of the client application executing on the UE 1006. The transmission may pass via the network node 1004 in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 1012, the network node 1004 transmits to the UE 1006 the user data that was carried in the transmission that the host 1002 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1014, the UE 1006 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 1006 associated with the host application executed by the host 1002.

[0183] In some examples, the UE 1006 executes a client application which provides user data to the host 1002. The user data may be provided in reaction or response to the data received from the host 1002. Accordingly, in step 1016, the UE 1006 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input / output interface of the UE 1006. Regardless of the specific manner in which the user data was provided, the UE 1006 initiates, in step 1018, transmission of the user data towards the host 1002 via the network node 1004. In step 1020, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 1004 receives user data from the UE 1006 and initiates transmission of the received user data towards the host 1002. In step 1022, the host 1002 receives the user data carried in the transmission initiated by the UE 1006.

[0184] One or more of the various embodiments improve the performance of OTT services provided to the UE 1006 using the OTT connection 1050, in which the wireless connection 1070 forms the last segment.

[0185] In an example scenario, factory status information may be collected and analyzed by the host 1002. As another example, the host 1002 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host 1002 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host 1002 may store surveillance video uploaded by a UE. As another example, the host 1002 may store or control access to media content such as video, audio, VR, or AR which it can broadcast, multicast, or unicast to UEs. As other examples, the host 1002 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing, and / or transmitting data.

[0186] In some examples, a measurement procedure may be provided for the purpose of monitoring data rate, latency, and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 1050 between the host 1002 and the UE 1006 in response to variations in the measurement results. The measurement procedure and / or the network functionality for reconfiguring the OTT connection 1050 may be implemented in software and hardware of the host 1002 and / or the UE 1006. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 1050 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or by supplying values of other physical quantities from which software may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 1050 may include message format, retransmission settings, preferred routing, etc.; the reconfiguring need not directly alter the operation of the network node 1004. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency, and the like by the host 1002. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 1050 while monitoring propagation times, errors, etc.

[0187] Although the computing devices described herein (e.g., UEs, network nodes, hosts) 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. In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored 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 hardwired manner. In any of those particular 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.

[0188] Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure. All such improvements and modifications are considered within the scope of the concepts disclosed herein.

[0189] Some example embodiments of the present disclosure include the following:

[0190] Group A Embodiments

[0191] Embodiment 1 : A method performed by a first node (300-1; 400-1), the method comprising sending (302; 402), to a second node (300-2; 400-2), information that indicates that the first node (300-1; 400-1) is exempting User Equipments, UEs, or one or more certain groups of UEs from cell barring in case of emergency traffic.

[0192] Embodiment 2: The method of embodiment 1, wherein the information indicates that the first node (300-1; 400-1) is exempting one or more certain groups of UEs from cell barring in case of emergency.

[0193] Embodiment 3 : The method of embodiment 2, wherein the one or more certain groups of UEs comprise UEs having a single receiver chain (e.g., IRx Redcap UEs or IRx eRedCap UEs).

[0194] Embodiment 4: The method of any of embodiments 1 to 3, wherein the first node (300-1) is a first network node (300-1) (e.g., a first gNB), and the second node (300-2) is a second network node (300-2) (e.g., a second gNB).

[0195] Embodiment 5: The method of embodiment 4, wherein sending (302) the information that indicates that the first network node (300-1) is exempting UEs or one or more certain groups of UEs from cell barring in case of emergency traffic comprises sending the information as part of XnAP Served Cell Information NR IE. Embodiment 6: The method of embodiment 4, wherein sending (302) the information that indicates that the first network node (300-1) is exempting UEs or one or more certain groups of UEs from cell barring in case of emergency traffic comprises sending the information as part of a RedCap Broadcast Information IE or an eRedCap Broadcast Information IE within an XnAP Served Cell Information NR IE.

[0196] Embodiment 7: The method of embodiment 4, wherein sending (302) the information that indicates that the first network node (300-1) is exempting UEs or one or more certain groups of UEs from cell barring in case of emergency traffic comprises sending the information as anew System Information Block, SIB, information element, e.g., within an XnAP Served Cell Information NR IE.

[0197] Embodiment 8: The method of any of embodiments 1 to 3, wherein the first node (400-1) is a first part of a network node (400-1) (e.g., a gNB-DU), and the second node (400-2) is a second part of the network node (400-2) (e.g., a second gNB-CU).

[0198] Embodiment 9: The method of any of embodiment 8, wherein sending (402) the information that indicates that the first part of the network node (400-1) is exempting UEs or one or more certain groups of UEs from cell barring in case of emergency traffic comprises sending the information as part of F1AP Served Cell Information NR IE.

[0199] Embodiment 10: The method of embodiment 8, wherein sending (402) the information that indicates that the first part of the network node (400-1) is exempting UEs or one or more certain groups of UEs from cell barring in case of emergency traffic comprises sending the information as part of a RedCap Broadcast Information IE or an eRedCap Broadcast Information IE within an F1AP Served Cell Information NR IE.

[0200] Embodiment 11: The method of embodiment 8, wherein sending (402) the information that indicates that the first part of the network node (400-1) is exempting UEs or one or more certain groups of UEs from cell barring in case of emergency traffic comprises sending the information as a new System Information Block, SIB, information element, e.g., within an F1AP Served Cell Information NR IE.

[0201] Embodiment 12: A method performed by a second node (300-2; 400-2), the method comprising receiving (302; 402), from a first node (300-1; 400-1), information that indicates that the first node (300-1; 400-1) is exempting User Equipments, UEs, or one or more certain groups of UEs from cell barring in case of emergency traffic.

[0202] Embodiment 13: The method of embodiment 12, wherein the information indicates that the first node (300-1; 400-1) is exempting one or more certain groups of UEs from cell barring in case of emergency. Embodiment 14: The method of embodiment 13, wherein the one or more certain groups of UEs comprise UEs having a single receiver chain (e.g., IRx Redcap UEs or IRx eRedCap UEs).

[0203] Embodiment 15: The method of any of embodiments 12 to 14, wherein the first node (300-1) is a first network node (300-1) (e.g., a first gNB), and the second node (300-2) is a second network node (300-2) (e.g., a second gNB).

[0204] Embodiment 16: The method of embodiment 15, wherein receiving (302) the information that indicates that the first network node (300-1) is exempting UEs or one or more certain groups of UEs from cell barring in case of emergency traffic comprises receiving the information as part of XnAP Served Cell Information NR IE.

[0205] Embodiment 17: The method of embodiment 15, wherein receiving (302) the information that indicates that the first network node (300-1) is exempting UEs or one or more certain groups of UEs from cell barring in case of emergency traffic comprises receiving the information as part of a RedCap Broadcast Information IE or an eRedCap Broadcast Information IE within an XnAP Served Cell Information NR IE.

[0206] Embodiment 18: The method of embodiment 15, wherein receiving (302) the information that indicates that the first network node (300-1) is exempting UEs or one or more certain groups of UEs from cell barring in case of emergency traffic comprises receiving the information as a new System Information Block, SIB, information element, e.g., within an XnAP Served Cell Information NR IE.

[0207] Embodiment 19: The method of any of embodiments 15 to 18, further comprising performing (304) one or more actions based on the received information that indicates that the first network node (300-1) is exempting UEs or one or more certain groups of UEs from cell barring in case of emergency traffic.

[0208] Embodiment 20: The method of embodiment 19, wherein performing (304) the one or more actions comprises handing over a particular UE from the second network node (300-2) to the first network node (300-1), the particular UE being one of the exempted UEs or one of the one or more certain groups of exempted UEs and having emergency traffic.

[0209] Embodiment 21: The method of embodiment 19, wherein performing (304) the one or more actions comprises refraining from handing over a particular UE from the second network node (300-2) to the first network node (300-1), the particular UE being a barred UE that is not one of the exempted UEs or one of the one or more certain groups of exempted UEs having emergency traffic. Embodiment 22: The method of embodiment 19, wherein the received information that indicates that the first network node (300-1) is exempting UEs or one or more certain groups of UEs from cell barring in case of emergency traffic is a hard requirement.

[0210] Embodiment 23: The method of embodiment 22, wherein performing (304) the one or more actions comprises refraining from handing over a particular UE from the second network node (300-2) to the first network node (300-1) even if there is no other alternatives for handover of the particular UE, the particular UE being a barred UE that is not one of the exempted UEs or one of the one or more certain groups of exempted UEs having emergency traffic.

[0211] Embodiment 24: The method of embodiment 19, wherein the received information that indicates that the first network node (300-1) is exempting UEs or one or more certain groups of UEs from cell barring in case of emergency traffic is a soft requirement.

[0212] Embodiment 25:. The method of embodiment 24, wherein performing (304) the one or more actions comprises handing over a particular UE from the second network node (300-2) to the first network node (300-1), the particular UE not being one of the exempted UEs or one of the one or more certain groups of exempted UEs having emergency traffic, but where there are no alternatives for handover of the particular UE.

[0213] Embodiment 26: The method of any of embodiments 12 to 14, wherein the first node (400-1) is a first part of a network node (400-1) (e.g., a gNB-DU), and the second node (400-2) is a second part of the network node (400-2) (e.g., a second gNB-CU).

[0214] Embodiment 27 : The method of any of embodiment 26, wherein receiving (402) the information that indicates that the first part of the network node (400-1) is exempting UEs or one or more certain groups of UEs from cell barring in case of emergency traffic comprises receiving the information as part of F1AP Served Cell Information NR IE.

[0215] Embodiment 28: The method of embodiment 26, wherein receiving (402) the information that indicates that the first part of the network node (400-1) is exempting UEs or one or more certain groups of UEs from cell barring in case of emergency traffic comprises receiving the information as part of a RedCap Broadcast Information IE or an eRedCap Broadcast Information IE within an F1AP Served Cell Information NR IE.

[0216] Embodiment 29: The method of embodiment 26, wherein receiving (402) the information that indicates that the first part of the network node (400-1) is exempting UEs or one or more certain groups of UEs from cell barring in case of emergency traffic comprises receiving the information as a new System Information Block, SIB, information element, e.g., within an Fl AP Served Cell Information NR IE. Embodiment 30: The method of any of embodiments 26 to 29, further comprising performing (404) one or more actions based on the received information that indicates that the first part of the network node (400-1) is exempting UEs or one or more certain groups of UEs from cell barring in case of emergency traffic.

[0217] Embodiment 31 : The method of embodiment 30, wherein performing (404) the one or more actions comprises sending an indication to another network node or a part of another network node that indicates which cell(s) (e.g., which cell(s) served by the first part of the network node (400-1) allow a barred UE to communicate emergency traffic).

[0218] Embodiment 32: The method of any of the previous embodiments, further comprising: obtaining user data; and forwarding the user data to a host or a user equipment.

[0219] Group B Embodiments

[0220] Embodiment 33: A network node comprising: processing circuitry configured to perform any of the steps of any of the Group A embodiments; and power supply circuitry configured to supply power to the processing circuitry.

[0221] Embodiment 34: A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a network node in a cellular network for transmission to a user equipment (UE), the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group A embodiments to transmit the user data from the host to the UE.

[0222] Embodiment 35: The host of the previous embodiment, wherein:

[0223] - the processing circuitry of the host is configured to execute a host application that provides the user data; and

[0224] - the UE comprises processing circuitry configured to execute a client application associated with the host application to receive the transmission of user data from the host.

[0225] Embodiment 36: A method implemented in a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: providing user data for the UE; and initiating a transmission carrying the user data to the UE via a cellular network comprising the network node, wherein the network node performs any of the operations of any of the Group A embodiments to transmit the user data from the host to the UE.

[0226] Embodiment 37: The method of the previous embodiment, further comprising, at the network node, transmitting the user data provided by the host for the UE.

[0227] Embodiment 38: The method of any of the previous 2 embodiments, wherein the user data is provided at the host by executing a host application that interacts with a client application executing on the UE, the client application being associated with the host application.

[0228] Embodiment 39: A communication system configured to provide an over-the-top (OTT) service, the communication system comprising: a host comprising: processing circuitry configured to provide user data for a user equipment (UE), the user data being associated with the over-the-top service; and a network interface configured to initiate transmission of the user data toward a cellular network node for transmission to the UE, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group A embodiments to transmit the user data from the host to the UE.

[0229] Embodiment 40: The communication system of the previous embodiment, further comprising:

[0230] - the network node; and / or

[0231] - the UE.

[0232] Embodiment 41 : A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to initiate receipt of user data; and a network interface configured to receive the user data from a network node in a cellular network, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group A embodiments to receive the user data from a user equipment (UE) for the host.

[0233] Embodiment 42: The host of the previous 2 embodiments, wherein:

[0234] - the processing circuitry of the host is configured to execute a host application that receives the user data; and - the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.

[0235] Embodiment 43: The host of the any of the previous 2 embodiments, wherein the initiating receipt of the user data comprises requesting the user data. Embodiment 44: A method implemented by a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: at the host, initiating receipt of user data from the UE, the user data originating from a transmission which the network node has received from the UE, wherein the network node performs any of the steps of any of the Group A embodiments to receive the user data from the UE for the host.

[0236] Embodiment 45: The method of the previous embodiment, further comprising at the network node, transmitting the received user data to the host.

[0237] Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure. All such improvements and modifications are considered within the scope of the concepts disclosed herein.

Claims

Claims1. A method performed by a first node (300-1; 400-1) for a Radio Access Network, RAN, of a cellular communications system, the method comprising: sending (302; 402), to a second node (300-2; 400-2), information that indicates that the first node (300-1; 400-1) is exempting User Equipments, UEs, or one or more certain groups of UEs from cell barring in case of emergency traffic.

2. The method of claim 1, wherein the information indicates that the first node (300-1; 400- 1) is exempting one or more certain groups of UEs from cell barring in case of emergency.

3. The method of claim 2, wherein the one or more certain groups of UEs comprise UEs having a single receiver chain.

4. The method of any of claims 1 to 3, wherein the first node (300-1) is a first network node (300-1), and the second node (300-2) is a second network node (300-2).

5. The method of claim 4, wherein sending (302) the information that indicates that the first network node (300-1) is exempting UEs or one or more certain groups of UEs from cell barring in case of emergency traffic comprises sending the information as part of XnAP Served Cell Information NR IE.

6. The method of claim 4, wherein sending (302) the information that indicates that the first network node (300-1) is exempting UEs or one or more certain groups of UEs from cell barring in case of emergency traffic comprises sending the information as part of a RedCap Broadcast Information IE or an eRedCap Broadcast Information IE within an XnAP Served Cell Information NR IE.

7. The method of claim 4, wherein sending (302) the information that indicates that the first network node (300-1) is exempting UEs or one or more certain groups of UEs from cell barring in case of emergency traffic comprises sending the information as a new System Information Block, SIB, information element.

8. The method of any of claims 1 to 3, wherein the first node (400-1) is a first part of a network node (400-1), and the second node (400-2) is a second part of the network node (400-2).

9. The method of claim 8, wherein the network node is a gNodeB, the first part of the network node is a gNodeB Distributed Unit, and the second part of the network node is a gNodeB Central Unit.

10. The method of any of claim 8 or 9, wherein sending (402) the information that indicates that the first part of the network node (400-1) is exempting UEs or one or more certain groups of UEs from cell barring in case of emergency traffic comprises sending the information as part of Fl AP Served Cell Information NR IE.

11. The method of claim 8 or 9, wherein sending (402) the information that indicates that the first part of the network node (400-1) is exempting UEs or one or more certain groups of UEs from cell barring in case of emergency traffic comprises sending the information as part of a RedCap Broadcast Information IE or an eRedCap Broadcast Information IE within an Fl AP Served Cell Information NR IE.

12. The method of claim 8 or 9, wherein sending (402) the information that indicates that the first part of the network node (400-1) is exempting UEs or one or more certain groups of UEs from cell barring in case of emergency traffic comprises sending the information as a new System Information Block, SIB, information element.

13. A first node (300-1; 400-1) for a Radio Access Network, RAN, of a cellular communications system, the first node (300-1; 400-1) adapted to: send (302; 402), to a second node (300-2; 400-2), information that indicates that the first node (300-1; 400-1) is exempting User Equipments, UEs, or one or more certain groups of UEs from cell barring in case of emergency traffic.

14. The first node (300-1; 400-1) of claim 13 further adapted to perform the method of any of claims 2 to 12.

15. A first node (300-1; 400-1) for a Radio Access Network, RAN, of a cellular communications system, the first node (300-1; 400-1) comprising processing circuitry (702) configured to cause the first node (300-1; 400-1) to:send (302; 402), to a second node (300-2; 400-2), information that indicates that the first node (300-1; 400-1) is exempting User Equipments, UEs, or one or more certain groups of UEs from cell barring in case of emergency traffic.

16. The first node (300-1; 400-1) of claim 15, wherein the processing circuitry is further configured to cause the first node (300-1; 400-1) to perform the method of any of claims 2 to 12.

17. A method performed by a second node (300-2; 400-2) for a Radio Access Network, RAN, of a cellular communications system, the method comprising: receiving (302; 402), from a first node (300-1; 400-1), information that indicates that the first node (300-1; 400-1) is exempting User Equipments, UEs, or one or more certain groups of UEs from cell barring in case of emergency traffic.

18. The method of claim 17, wherein the information indicates that the first node (300-1; 400-1) is exempting one or more certain groups of UEs from cell barring in case of emergency.

19. The method of claim 18, wherein the one or more certain groups of UEs comprise UEs having a single receiver chain.

20. The method of any of claims 17 to 19, wherein the first node (300-1) is a first network node (300-1), and the second node (300-2) is a second network node (300-2).

21. The method of claim 20, wherein receiving (302) the information that indicates that the first network node (300-1) is exempting UEs or one or more certain groups of UEs from cell barring in case of emergency traffic comprises receiving the information as part of XnAP Served Cell Information NR IE.

22. The method of claim 20, wherein receiving (302) the information that indicates that the first network node (300-1) is exempting UEs or one or more certain groups of UEs from cell barring in case of emergency traffic comprises receiving the information as part of a RedCap Broadcast Information IE or an eRedCap Broadcast Information IE within an XnAP Served Cell Information NR IE.

23. The method of claim 20, wherein receiving (302) the information that indicates that thefirst network node (300-1) is exempting UEs or one or more certain groups of UEs from cell barring in case of emergency traffic comprises receiving the information as a new System Information Block, SIB, information element.

24. The method of any of claims 20 to 23, further comprising performing (304) one or more actions based on the received information that indicates that the first network node (300-1) is exempting UEs or one or more certain groups of UEs from cell barring in case of emergency traffic.

25. The method of claim 24, wherein performing (304) the one or more actions comprises handing over a particular UE from the second network node (300-2) to the first network node (300-1), the particular UE being one of the exempted UEs or one of the one or more certain groups of exempted UEs and having emergency traffic.

26. The method of claim 24, wherein performing (304) the one or more actions comprises refraining from handing over a particular UE from the second network node (300-2) to the first network node (300-1), the particular UE being a barred UE that is not one of the exempted UEs or one of the one or more certain groups of exempted UEs having emergency traffic.

27. The method of claim 24, wherein the received information that indicates that the first network node (300-1) is exempting UEs or one or more certain groups of UEs from cell barring in case of emergency traffic is a hard requirement.

28. The method of claim 27, wherein performing (304) the one or more actions comprises refraining from handing over a particular UE from the second network node (300-2) to the first network node (300-1) even if there is no other alternatives for handover of the particular UE, the particular UE being a barred UE that is not one of the exempted UEs or one of the one or more certain groups of exempted UEs having emergency traffic.

29. The method of claim 24, wherein the received information that indicates that the first network node (300-1) is exempting UEs or one or more certain groups of UEs from cell barring in case of emergency traffic is a soft requirement.

30. The method of claim 29, wherein performing (304) the one or more actions compriseshanding over a particular UE from the second network node (300-2) to the first network node (300-1), the particular UE not being one of the exempted UEs or one of the one or more certain groups of exempted UEs having emergency traffic, but where there are no alternatives for handover of the particular UE.

31. The method of any of claims 17 to 19, wherein the first node (400-1) is a first part of a network node (400-1), and the second node (400-2) is a second part of the network node (400-2).

32. The method of claim 31, wherein the network node is a gNodeB, the first part of the network node is a gNodeB Distributed Unit, and the second part of the network node is a gNodeB Central Unit.

33. The method of any of claim 31 or 32, wherein receiving (402) the information that indicates that the first part of the network node (400-1) is exempting UEs or one or more certain groups of UEs from cell barring in case of emergency traffic comprises receiving the information as part of Fl AP Served Cell Information NR IE.

34. The method of claim 31 or 32, wherein receiving (402) the information that indicates that the first part of the network node (400-1) is exempting UEs or one or more certain groups of UEs from cell barring in case of emergency traffic comprises receiving the information as part of a RedCap Broadcast Information IE or an eRedCap Broadcast Information IE within an Fl AP Served Cell Information NR IE.

35. The method of claim 31 or 32, wherein receiving (402) the information that indicates that the first part of the network node (400-1) is exempting UEs or one or more certain groups of UEs from cell barring in case of emergency traffic comprises receiving the information as a new System Information Block, SIB, information element, e.g., within an F1AP Served Cell Information NR IE.

36. The method of any of claims 31 to 35, further comprising performing (404) one or more actions based on the received information that indicates that the first part of the network node (400-1) is exempting UEs or one or more certain groups of UEs from cell barring in case of emergency traffic.

37. The method of claim 36, wherein performing (404) the one or more actions comprises sending an indication to another network node or a part of another network node that indicates which cell(s) allow a barred UE to communicate emergency traffic.

38. A second node (300-2; 400-2) for a Radio Access Network, RAN, of a cellular communications system, the second node (300-2; 400-2) adapted to: receive (302; 402), from a first node (300-1; 400-1), information that indicates that the first node (300-1; 400-1) is exempting User Equipments, UEs, or one or more certain groups of UEs from cell barring in case of emergency traffic.

39. The second node (300-2; 400-2) of claim 38 further adapted to perform the method of any of claims 18 to 37.

40. A second node (300-2; 400-2) for a Radio Access Network, RAN, of a cellular communications system, the second node (300-2; 400-2) comprising processing circuitry configured to cause the second node (300-2; 400-2) to: receive (302; 402), from a first node (300-1; 400-1), information that indicates that the first node (300-1; 400-1) is exempting User Equipments, UEs, or one or more certain groups of UEs from cell barring in case of emergency traffic.

41. The second node (300-2; 400-2) of claim 40, wherein the processing circuitry is further configured to cause the second node (300-2; 400-2) to perform the method of any of claims 18 to 37.

Images