WO2024068354A1

WO2024068354A1 - Extension of barring parameters

Info

Publication number: WO2024068354A1
Application number: PCT/EP2023/075746
Authority: WO
Inventors: Mattias BERGSTRÖM; Håkan Palm; Christian Bergljung
Original assignee: Telefonaktiebolaget Lm Ericsson (Publ)
Priority date: 2022-09-27
Filing date: 2023-09-19
Publication date: 2024-04-04

Abstract

Systems and methods are disclosed that relate to extension of a cell barring parameter. In one embodiment, a method performed by a User Equipment (UE) comprises receiving, from a network node, information comprising a first barring associated indication and determining that the first barring associated indication is set to a value that indicates that a second barring associated indication is also included in the received information. The method further comprises obtaining the second barring associated indication from the received information responsive to determining that the first barring associated indication is set to the value that indicates that the second barring associated indication is also included in the received information and performing one or more actions based on a value of the second barring associated indication. In this manner, an extension of the signaling of an associated barring parameter is provided.

Description

EXTENSION OF BARRING PARAMETERS

Related Applications

This application claims the benefit of provisional patent application serial number 63/410,450, filed September 27, 2022, the disclosure of which is hereby incorporated herein by reference in its entirety.

Technical Field

The present disclosure relates to a cellular communications system and, more specifically, cell barring in a cellular communications system.

Background

Network Signaling (NS) values (i.e., “NS-values”) is a feature in 3^rd Generation Partnership Project (3 GPP) New Radio (NR) and Long Term Evolution (LTE) specifications. This feature allows the network to indicate to the User Equipment (UE) that additional requirements apply for a cell, e.g., additional spectrum emission requirements. It may be so that to operate in a particular cell, the UE must behave in a special way, or comply with additional (e.g., more restrictive) requirements.

NS-values are signaled using the field additionalSpectrumEmission within System Information Block 1 (SIB 1). The field additionalSpectrumEmission can take values 0. . .7. The network can indicate one or more NS-values per cell, meaning that the network can send more than one additionalSpectrumEmission field. The UE must support at least one NS-value that the network signals in order to camp on the cell. More specifically, the UE will inspect the field(s) additionalSpectrumEmission that the network sends and, if the UE does not support any of them, the UE considers the cell as barred meaning that the UE will not camp on or connect to that cell.

Some relevant excerpts from 3GPP Technical Specification (TS) 38.331 vl7.1.0 are as follows (emphasis added as bold, underlined text):

***** START EXCERPTS FROM 3GPP TS 38.331 *****

5.2.2.4.2 Actions upon reception of the SIB1

Upon receiving the SIB1 the UE shall:

1> store the acquired SIBT,

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:

2> if intraFreqReselectionRedCap is not present in SIBk 3> consider the cell as barred in accordance with TS 38.304 [20];

3> perform barring as if intraFreqReselectionRedCap is set to allowed;

2> else:

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

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

3> if the halfDuplexRedCapAllowed is not present in the acquired SIB1 and the UE supports only halfduplex FDD operation:

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

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

1> if the cellAccessRelatedlnfo contains an entry of a selected SNPN or PLMN and in case of PLMN the UE is either allowed or instructed to access the PLMN via a cell for which at least one CAG ID is broadcast:

2> in the remainder of the procedures use npn-IdentityList, trackingAreaCode, and cellldentity for the cell as received in the corresponding entry of npn-IdentitylnfoList containing the selected PLMN or SNPN;

1> else if the cellAccessRelatedlnfo contains an entry with the PLMN-Identity of the selected PLMN:

2> in the remainder of the procedures use plmn-IdentityList, trackingAreaCode, trackingAreaList, and cellldentity for the cell as received in the corresponding PLMN -Identity Info containing the selected PLMN;

1> if in RRC CONNECTED while T311 is not running:

2> disregard the frequencyBandList, if received, while in RRC CONNECTED;

2> forward the cellidentity to upper layers;

2> forward the trackingAreaCode to upper layers, if not ignored;

2> forward the trackingAreaList to upper layers, if included;

2> forward the received posSIB-Mappinglnfo to upper layers, if included;

2> apply the configuration included in the servingCellConfigCommon',

2> if the UE has a stored valid version of a SIB or posSIB, in accordance with clause 5.2.2.2.1, that the UE requires to operate within the cell in accordance with clause 5.2.2.1 :

3> use the stored version of the required SIB or posSIB;

2> else:

3> acquire the required SIB or posSIB requested by upper layer as defined in clause 5.2.2.3.5;

NOTE: Void.

1> else:

2> if the UE supports one or more of the frequency bands indicated in the frequencyBandList for downlink for TDD, or one or more of the frequency bands indicated in the frequencyBandList for uplink for FDD, and they are not downlink only bands, and

2> if the UE is I AB -MT or supports at least one additionalSpectrumEmission in the NR-NS-PmaxList for a supported band in the downlink for TDD, or a supported band in uplink for FDD, and

2> if the UE supports an uplink channel bandwidth with a maximum transmission bandwidth configuration (see TS 38.101-1 [15] and TS 38.101-2 [39]) which - is smaller than or equal to the carrierBandwidth (indicated in uplinkConfigCommon for the SCS of the initial uplink BWP or, for RedCap UE, of the initial uplink BWP for RedCap if configured), and which

- is wider than or equal to the bandwidth of the initial uplink BWP or, for RedCap UE, of the initial uplink BWP for RedCap if configured, and > if the UE supports a downlink channel bandwidth with a maximum transmission bandwidth configuration (see TS 38.101-1 [15] and TS 38.101-2 [39]) which

- is smaller than or equal to the carrier Bandwidth (indicated in downlinkConfigCommon for the SCS of the initial downlink BWP or, for RedCap UE, of the initial downlink BWP for RedCap if configured), and which

- is wider than or equal to the bandwidth of the initial downlink BWP or, for RedCap UE, of the initial downlink BWP for RedCap if configured, and > if frequencyShift7p5khz is present and the UE supports corresponding 7.5kHz frequency shift on this band; or frequencyShift7p5khz is not present:

3> if trackingAreaCode or trackingAreaList is not provided for the selected PLMN nor the registered PLMN nor PLMN of the equivalent PLMN list:

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

4> perform cell re-selection to other cells on the same frequency as the barred cell as specified in TS 38.304 [20];

3> else if UE is IAB-MT and if iab-Support is not provided for the selected PLMN nor the registered PLMN nor PLMN of the equivalent PLMN list nor the selected SNPN nor the registered SNPN:

4> consider the cell as barred for IAB-MT in accordance with TS 38.304 [20];

3> else:

4> apply a supported uplink channel bandwidth with a maximum transmission bandwidth which

- is contained within the carrierBandwidth indicated in uplinkConfigCommon for the SCS of the initial uplink BWP or, for RedCap UEs, initial uplink BWP for RedCap, if configured, and which

- is wider than or equal to the bandwidth of the initial BWP for the uplink or, for a RedCap UE, of the initial uplink BWP for RedCap if configured;

4> apply a supported downlink channel bandwidth with a maximum transmission bandwidth which

- is contained within the carrier Bandwidth indicated in downlinkCc mfigCommon for the SCS of the initial downlink BWP or, for RedCap UEs, initial downlink BWP for RedCap, if configured, and which

- is wider than or equal to the bandwidth of the initial BWP for the downlink or, for a RedCap UE, of the initial downlink BWP for RedCap if configured;

4> select the first frequency band in the frequencyBandList, for FDD from frequencyBandList for uplink, or for TDD from frequencyBandList for downlink, which the UE supports and for which the UE supports at least one of the additionalSpectrumEmission values in nr-NS-PmaxList, if present;

4> forward the cellldentity to upper layers;

4> forward the trackingAreaCode to upper layers;

4> forward the trackingAreaList to upper layers, if included;

4> forward the received posSIB-Mappinglnfo to upper layers, if included;

4> forward the PLMN identity or SNPN identity or PNI-NPN identity to upper layers;

4> if in RRC INACTIVE and the forwarded information does not trigger message transmission by upper layers: 5> if the serving cell does not belong to the configured ran-NotificationArealnfo'.

6> initiate an RNA update as specified in 5.3.13.8 ;

4> forward the ims-EmergencySupport to upper layers, if present;

4> forward the eCallOverlMS-Support to upper layers, if present;

4> forward the UAC-AccessCategoryl-SelectionAssistancelnfo or UAC-ACl-SelectAssistlnfo for the selected PLMN/SNPN to upper layers, if present and set to a, b or c;

4> if the UE is in SNPN access mode:

5> forward the imsEmergencySupportForSNPN indicators with the corresponding SNPN identities to upper layers, if present;

4> apply the configuration included in the servingCellConfigCommon',

4> apply the specified PCCH configuration defined in 9.1.1.3 ;

4> if the UE has a stored valid version of a SIB, in accordance with clause 5.2.2.2.1, that the UE requires to operate within the cell in accordance with clause 5.2.2.1:

5> use the stored version of the required SIB;

4> if the UE has not stored a valid version of a SIB, in accordance with clause 5.2.2.2.1, of one or several required SIB(s), in accordance with clause 5.2.2.1:

5> for the SI message(s) that, according to the si-Schedulinglnfo, contain at least one required SIB and for which si-BroadcastStatus is set to broadcasting:

6> acquire the SI message(s) as defined in clause 5.2.2.3.2;

5> for the SI message(s) that, according to the si-Schedulinglnfo, contain at least one required SIB and for which si-BroadcastStatus is set to notBroadcasting'.

6> trigger a request to acquire the SI message(s) as defined in clause 5.2.2.3.3;

4> if the UE has a stored valid version of a posSIB, in accordance with clause 5.2.2.2.1, of one or several required posSIB(s), in accordance with clause 5.2.2.1:

5> use the stored version of the required posSIB;

4> if the UE has not stored a valid version of a posSIB, in accordance with clause 5.2.2.2.1, of one or several posSIB(s) in accordance with clause 5.2.2.1:

5> for the SI message(s) that, according to the posSI-Schedulinglnfo, contain at least one requested posSIB and for which posSI-BroadcastStatus is set to broadcasting'.

6> acquire the SI message(s) as defined in clause 5.2.2.3.2;

5> for the SI message(s) that, according to the posSI-Schedulinglnfo, contain at least one requested posSIB for which posSI-BroadcastStatus is set to notBroadcasting'.

6> trigger a request to acquire the SI message(s) as defined in clause 5.2.2.3.3a;

4> apply the first listed additionalSpectrumEmission which it supports among the values included in NR-NS-PmaxList within frequencyBandList in uplinkConfigCommon for FDD or in downlinkConfigCommon for TDD;

4> if the additionalPmax is present in the same entry of the selected additionalSpectrumEmission within NR-NS-PmaxList'.

5> apply the additionalPmax for UL;

4> else:

5> apply the p-Max in uplinkConfigCommon for UL; 4> if supplementaryUplink is present in servingCellConfigCommorr, and

4> if the UE supports one or more of the frequency bands indicated in the frequencyBandList for the supplementaryUplink, and

4> if the UE supports at least one additionalSpectrumEmission in the NR-NS-PmaxList for a supported supplementary uplink band; and

4> if the UE supports an uplink channel bandwidth with a maximum transmission bandwidth configuration (see TS 38.101-1 [15] and TS 38.101-2 [39]) which

- is smaller than or equal to the carrier Bandwidth (indicated in supplementaryUplink for the SCS of the initial uplink BWP), and which

- is wider than or equal to the bandwidth of the initial uplink BWP of the SUL:

5> consider supplementary uplink as configured in the serving cell;

5> select the first frequency band in the frequencyBandList for the supplementaryUplink which the UE supports and for which the UE supports at least one of the additionalSpectrumEmission values in nr-NS-PmaxList, if present;

5> apply a supported supplementary uplink channel bandwidth with a maximum transmission bandwidth which

- is contained within the carrier Bandwidth (indicated in supplementaryUplink for the SCS of the initial uplink BWP), and which

- is wider than or equal to the bandwidth of the initial BWP of the SUL;

5> apply the first listed additionalSpectrumEmission which it supports among the values included in NR-NS-PmaxList within frequencyBandList for the supplementaryUplink,

5> if the additionalPmax is present in the same entry of the selected additionalSpectrumEmission within NR-NS-PmaxList for the supplementaryUplink.

6> apply the additionalPmax in supplementaryUplink for SUL;

5> else:

6> apply the p-Max in supplementaryUplink for SUL;

3> consider the cell as barred in accordance with TS 38.304 [20]; and

3> perform barring as if intraFreqReselection is set to notAllowed,

NEXT EXCERPT FROM 3GPP TS 38.331

NR-MultiBandlnf o : : = SEQUENCE { f reqBandlndicatorNR FreqBandlndicatorNR OPTIONAL , — Cond

OptULNotSIB2 nr-NS-PmaxList NR-NS-PmaxList OPTIONAL — Need S

}

NR-NS-PmaxList SEQUENCE ( SI ZE ( 1 . . maxNR-NS-Pmax ) ) OF NR-NS-PmaxValue

NR-NS-PmaxValue : : = SEQUENCE { additionalPmax P-Max OPTIONAL ,

Need N additionalSpectrumEmission AdditionalSpectrumEmission

}

Frequencylnf oUL : : = SEQUENCE { frequencyBandList MultiFrequencyBandListNR

OPTIONAL , — Cond FDD-OrSUL absolute Frequency Point A ARFCN-ValueNR

OPTIONAL , — Cond FDD-OrSUL s cs-Speci ficCarrierList SEQUENCE ( SI ZE ( 1 . . maxSCSs ) ) OF SCS-Speci ficCarrier , additionalSpectrumEmis sion AdditionalSpectrumEmis sion

OPTIONAL , — Need S p-Max P-Max

OPTIONAL , — Need S f requencyShi ft7p5khz ENUMERATED ( true )

OPTIONAL , — Cond FDD-TDD-Or SUL-Optional }

AdditionalSpectrumEmis sion INTEGER ( 0 . . 7 )

***** END EXCERPTS FROM 3GPP TS 38.331 *****

Summary

Systems and methods are disclosed that relate to extension of a cell barring parameter. In one embodiment, a method performed by a User Equipment (UE) comprises receiving, from a network node, information comprising a first barring associated indication and determining that the first barring associated indication is set to a value that indicates that a second barring associated indication is also included in the received information. The method further comprises obtaining the second barring associated indication from the received information responsive to determining that the first barring associated indication is set to the value that indicates that the second barring associated indication is also included in the received information and performing one or more actions based on a value of the second barring associated indication. In this manner, an extension of the signaling of an associated barring parameter is provided while also maintaining legacy functionality for legacy UEs via use of other values of the first barring associated indication.

In one embodiment, the first barring associated indication is an additionalSpectrumEmission field, and the second barring associated indication is a field that extends a range of permissible values of the additionalSpectrumEmission field. In one embodiment, the value of the first barring associated indication that indicates that the second barring associated indication is also included in the received information is a value of 7.

In one embodiment, the received information is system information.

In one embodiment, the first barring associated indication and the second barring associated indication are for a respective cell.

In one embodiment, a default value is defined for the first barring associated indication but not the second barring associated indication. In one embodiment, performing the one or more actions based on the value of the second barring associated indication comprises determining whether the UE is barred from a respective cell based on the value of the second barring associated indication and operating in accordance with a result of the determining.

In one embodiment, by being set to the first value, the first barring associated indication is not considered by the UE as indicating a value for the barring function, but rather to be considered by the UE as an indication that the UE is to inspect, consider, or apply the value of the second barring associated indication.

In one embodiment, the network node is a network node in a cellular communications system.

In one embodiment, the network node is a network node in a radio access network of a 3^rd Generation Partnership Project (3GPP) cellular communications system.

Corresponding embodiments of a UE are also disclosed. In one embodiment, a UE is adapted to receive, from a network node, information comprising a first barring associated indication and determine that the first barring associated indication is set to a value that indicates that a second barring associated indication is also included in the received information. The UE is further adapted to obtain the second barring associated indication from the received information responsive to determining that the first barring associated indication is set to the value that indicates that the second barring associated indication is also included in the received information and perform one or more actions based on a value of the second barring associated indication.

In one embodiment, a UE comprises a communication interface and processing circuitry associated with the communication interface. The processing circuitry is configured to cause the UE to receive, from a network node, information comprising a first barring associated indication and determine that the first barring associated indication is set to a value that indicates that a second barring associated indication is also included in the received information. The processing circuitry is further configured to cause the UE to obtain the second barring associated indication from the received information responsive to determining that the first barring associated indication is set to the value that indicates that the second barring associated indication is also included in the received information and perform one or more actions based on a value of the second barring associated indication.

Corresponding embodiments of a computer program, a carrier containing the computer program, and a non-transitory computer readable medium are also disclosed.

Embodiments of a method performed by a network node are also disclosed. In one embodiment, a method performed by a network node comprises determining a value to be signaled to one or more UEs via a barring associated indication and determining that the determined value is not supported by a first barring associated indication. The method further comprising, responsive to determining that the determined value is not supported by the first barring associated indication, setting the first barring associated indication to a value that indicates that a second barring associated indication is present and setting the second barring associated indication to the determined value. The method further comprises transmitting, to one or more UEs, information that comprises the first barring associated indication and the second barring associated indication.

In one embodiment, the first barring associated indication is an additionalSpectrumEmission field, and the second barring associated indication is a field that extended a range of permissible values of the additionalSpectrumEmission field. In one embodiment, the value of the first barring associated indication that indicates that the second barring associated indication is also included in the received information is a value of 7.

In one embodiment, the transmitted information is system information.

In one embodiment, a default value is defined for the first barring associated indication but not the second barring associated indication.

In one embodiment, by being set to the first value, the first barring associated indication is not to be considered by the UE as indicating a value for the barring function, but rather to be considered by the UE as an indication that the UE is to inspect, consider, or apply the value of the second barring associated indication.

In one embodiment, the network node is a network node in a radio access network of a 3GPP cellular communications system.

Corresponding embodiments of a network node are also disclosed. In one embodiment, a network node is adapted to determine a value to be signaled to one or more UEs via a barring associated indication and determine that the determined value is not supported by a first barring associated indication. The network node is further adapted to, responsive to determining that the determined value is not supported by the first barring associated indication, set the first barring associated indication to a value that indicates that a second barring associated indication is present and set the second barring associated indication to the determined value. The network node is further adapted to transmit, to one or more UEs, information that comprises the first barring associated indication and the second barring associated indication. In one embodiment, a network node comprises a communication interface and processing circuitry associated with the communication interface. The processing circuitry is configured to cause the network node to determine a value to be signaled to one or more UEs via a barring associated indication and determine that the determined value is not supported by a first barring associated indication. The processing circuitry is further configured to cause the network node to, responsive to determining that the determined value is not supported by the first barring associated indication, set the first barring associated indication to a value that indicates that a second barring associated indication is present and set the second barring associated indication to the determined value. The processing circuitry is further configured to cause the network node to transmit, to one or more UEs, information that comprises the first barring associated indication and the second barring associated indication.

Brief Description of the Drawings

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.

Figure 1 is a flow chart that illustrates the operation of a User Equipment (UE) in accordance with embodiments of the present disclosure;

Figure 2 is a flow chart that illustrates the operation of a network node in accordance with embodiments of the present disclosure;

Figure 3 shows an example of a communication system in which embodiments of the present disclosure may be implemented;

Figure 4 shows a UE in accordance with some embodiments;

Figure 5 shows a network node in accordance with some embodiments;

Figure 6 is a block diagram of a host, which may be an embodiment of the host of Figure 3, in accordance with various aspects described herein;

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

Figure 8 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. Detailed Description

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.

There currently exist certain challenge(s). The current Network Signaling (NS) value (NS-value) signaling framework defined in 3^rd Generation Partnership Project (3GPP) New Radio (NR) and Long Term Evolution (LTE) specifications supports only that that value the field additionalSpectrumEmission ranges from 0 to 7. This may be a limiting factor in some deployments.

Certain aspects of the present disclosure and their embodiments may provide solutions to these or other challenges. Systems and methods are disclosed herein in which a network node (e.g., a base station such as, e.g., a next generation Node B (gNB) or evolved Node B (eNB) or a Radio Access Network (RAN) node that supports some of the functionality of a base station such as, e.g., a gNB Distributed Unit (gNB-DU), a gNB Centralized Unit (gNB-CU), an eNB Distributed Unit (eNB-DU), or eNB Centralized Unit (eNB-CU)) sets a first field (e.g., the additionalSpectrumEmission field) associated with a barring functionality to a first value (e.g., value of 7), and this indicates that the network node also includes a second field (e.g., a new field referred to herein by the exemplary name ‘ddditionalSpectrumEmissionExf') also associated with a barring functionality. Additional details are described below.

Certain embodiments may provide one or more of the following technical advantage(s). Embodiments of the present disclosure may allow extension of the existing NS-value signaling while still working for User Equipments (UEs) that do not support the extension (referred to herein as “legacy UEs”).

Systems and methods are disclosed herein in which a network node (e.g., a base station such as, e.g., a next generation Node B (gNB) or evolved Node B (eNB) or a Radio Access Network (RAN) node that supports some of the functionality of a base station such as, e.g., a gNB Distributed Unit (gNB-DU), a gNB Centralized Unit (gNB-CU), an eNB Distributed Unit (eNB-DU), or eNB Centralized Unit (eNB-CU)) sets a first indication (e.g., a first field such as, e.g., the additionalSpectrumEmission field) associated with a barring functionality to a first value (e.g., value of 7), and this indicates that the network node also includes a second indication (e.g., a second field such as, e.g., a new field referred to herein by the exemplary name additionalSpectrumEmissionExf) also associated with a barring functionality. These indications are also referred to herein as “barring associated indications”.

In one embodiment, a network node signals, to one or more UEs, a first barring associated indication that is set to a first value and a second barring associated indication that is set to a second value. Alternatively, the network node signals, to one or more UEs, a single first barring associated indication that is set to a first value, and signals, to the one or more UEs, a set of second barring associated indications set to a second set of values. The first value indicates that the UE is to inspect the second indication or set of second indications.

In one embodiment, the second indication(s) is present only in case the first indication is set to the first value, but not present if the first indication is set to some other value.

The second indication(s) is used to extend the first indication.

Note that the above may be performed per cell. This means that, on a first cell, the network node may use the extended (second) barring associated indication while, on another cell, the network node applies the first barring associated indication and may not even signal any barring associated indication at all on yet another cell.

In one embodiment, the network node only sets the first indication to the first value if the UE includes the second indication. In other words, in one embodiment, the network node only sets the first indication to the first value if the network also provides the second indication.

In one embodiment, the UE will consider absence of the first indication so that a first barring associated indication is signaled, i.e., there is a default value which is applied in case of absence of the first indication. The default value may imply that no barring is indicated by the network (at least based on the mechanism associated with the first and second indication, note that the network may indicate barring associated indications using other types of mechanisms/fields). However, for the second indication, absence of the indication is not considered by the UE that any barring associated indication is signaled, i.e., there is no default value associated with the second indication.

Embodiments of the present disclosure can be applied to extending NS-value signaling, or other types of indications used to indicate barring behavior.

In one particular set of embodiments, the embodiments described above are applied to extend the existing NS-value signaling in a 3GPP LTE or NR. network. In one embodiment, a network node sets the field additionalSpectrumEmission to a first value, e.g. the highest possible value (which is 7 in the current Radio Resource Control (RRC) specification), and if so sends a second field, which is referred to herein by the exemplary name ^additionalSpectrumEmissionExt” to indicate the NS value that the UE is to consider. The first value of additionalSpectrumEmission is used to indicate that (one or more of) additionalSpectrumEmissionExt is present and indicates the NS-value(s).

If the network node indicates an NS-value which is supported by (i.e., can be signaled using) additionalSpectrumEmission (e.g., 0 to 6), the network node does not signal additionalSpectrumEmissionExt.

The first value of additionalSpectrumEmission (e.g., 7) is not considered as indicating an NS-value, but rather as an indication that the UE is to inspect, consider, or apply, the field additionalSpectrumEmissionExt, where additionalSpectrumEmissionExt is then used to indicate NS-value.

The network node determines if the NS-value that the network node should indicate can be indicated by the (non-extended) field additionalSpectrumEmission (i.e., should indicate 0 to 6). If so, the network would set the additionalSpectrumEmission to the wanted value(s). If not possible, e.g. due to that additionalSpectrumEmission cannot indicate as high value as needed (e.g., 9), the network node set additionalSpectrumEmission to the value to indicate that the extension is used, (e.g., 7) and then provides the applicable NS-value(s) in the extended field additionalSpectrumEmissionExt. Note that the network node may signal more than one extended NS-values by including more than one additionalSpectrumEmissionExt field.

A UE which is not implementing this change (referred here as a “legacy UE”), i.e. a UE which does not support extended NS-values, will only be able to interpret additionalSpectrumEmission, but not additionalSpectrumEmissionExt. The legacy UE does not, at least in some embodiments, even understand that value 7 is used to indicate that extended NS- value signaling is used (i.e., that additionalSpectrumEmissionExt is providing the actual NS- value). But the legacy UE will, as per existing behavior, see that the non-extended field (additionalSpectrumEmission) is set to a value which the UE does not support (e.g., 7). And as described, if a UE does not support a value signaled in additionalSpectrumEmission the UE will consider the cell as barred.

In one embodiment, the network node only includes additionalSpectrumEmissionExt if additionalSpectrumEmission is set to the value that indicates the extension, e.g. 7. Further, in one embodiment, the network node never indicates multiple additionalSpectrumEmission where one of them is the value to indicate the extension (e.g., 7). Meaning that additionalSpectrumEmissionExt is only set to 7 if there is only one additionalSpectrumEmission and that is set to 7.

Note, the above may all be done per cell, meaning that the restrictions/rules/etc. for how the network sets these indications, is only applied for one cell. And the UE would only consider that if additionalSpectrumEmission is set to the value to indicate the extension, the extension only applies for this cell, while of other cells, the network and UE applies another behavior.

Figure 1 is a flow chart that illustrates the operation of a UE in accordance with at least some of the embodiments described above. Optional steps are represented by dashed lines/boxes. As illustrated, the UE receives information (e.g., system information such as, e.g., SIB1) from a network node, where this information includes a first barring association indication (e.g., additionalSpectrumEmission field) (step 100). The UE determines whether the first barring association indication is set to a value (e.g., additionalSpectrumEmission = 7) that indicates that a second barring association indication (e.g., additionalSpectrumEmissionExt field) is also included in the received information (step 102). If so (step 102, YES), the UE obtains the second barring association indication (e.g., additionalSpectrumEmissionExt field) from the received information (step 104) and performs one or more actions based on a value of the second barring associated indication (step 106). For example, in one embodiment, the UE determines whether the UE is barred from a respective cell based on the value of the second barring associated indication (step 106 A) and operates in accordance with a result of the determining step 106 A (step 106B).

Returning to step 102, if the UE determines that the first barring associated indication is not set to a value that indicates that a second barring associated indication is also included (step 102, NO), the UE performs one or more actions based on the value of the first barring associated indication (step 108). For example, in one embodiment, the UE determines whether the UE is barred from the respective cell based on the value of the first barring associated indication (step 108 A) and operates in accordance with a result of the determining step 108 A (step 108B).

Note that, in one embodiment, the UE that performs the process of Figure 1 is a UE that supports the extension of the first barring associated indication via the second barring associated indication. However, a UE that does not support the extension (i.e., a legacy UE) may perform steps 100 and 108 without any knowledge of a second barring associated indication. In this case, the value of the first barring associated indication that would indicate the presence of the second barring associated indication to a non-legacy UE may be a value of the first barring associated indication that would indicate to the legacy UE that it is barred from the cell (e.g., additionalSpectrumEmission = 7 may indicate to a non-legacy UE that the second barring associated is present and be undefined for a legacy UE or otherwise indicate to a legacy UE that it is barred from the respective cell).

It should also be noted that, in one embodiment, a default value may be defined for the first barring associated indication and be used by the UE if the first barring associated indication is not present in the received information. However, in one embodiment, absence of the second barring associated indication does not provide any indication of whether the UE is barred or non-barred from the cell (i.e., no default value is defined for the second barring associated indication).

Figure 2 is a flow chart that illustrates the operation of a network node in accordance with at least some of the embodiments described above. Optional steps are represented by dashed lines/boxes. The network node may be a RAN node such as, e.g., a base station (e.g., a gNB or eNB) or a RAN node that provides some of the functionality of a base station (e.g., a gNB-DU, gNB-CU, eNB-DU, or eNB-CU). As illustrated, the network node determines a value to be signed via a barring associated indication(s) (step 200).

If the determined value is not supported by a first barring associated indication (e.g., additionalSpectrumEmission field) (step 202, NO), the network node sets the first barring associated indication (e.g., additionalSpectrumEmission field) to a value (e.g., 7) that indicates that a second barring associated indication is present (e.g., in information such as, e.g., system information such as, e.g., SIB1) in information to be transmitted to a UE(s) (step 204). The network node also sets the second barring associated indication (e.g., additionalSpectrumEmissionExt field) to the determined value from step 200 (step 206). The network node then transmits information (e.g., system information such as, e.g., SIB1) to one or more UEs, where this information includes the first barring associated indication and the second barring associated indication (step 208).

Returning to step 202, if the determined value is supported by the first barring associated indication (e.g., additionalSpectrumEmission field) (step 202, YES), the network node sets the first barring associated indication (e.g., additionalSpectrumEmission field) to the determined value (step 210). The network node then transmits information (e.g., system information such as, e.g., SIB1) to one or more UEs, where this information includes the first barring associated indication (step 212).

Figure 3 shows an example of a communication system 300 in which embodiments of the present disclosure may be implemented.

In the example, the communication system 300 includes a telecommunication network 302 that includes an access network 304, such as a Radio Access Network (RAN), and a core network 306, which includes one or more core network nodes 308. The access network 304 includes one or more access network nodes, such as network nodes 310A and 310B (one or more of which may be generally referred to as network nodes 310), or any other similar Third Generation Partnership Project (3GPP) access node or non-3GPP Access Point (AP). The network nodes 310 facilitate direct or indirect connection of User Equipment (UE), such as by connecting UEs 312 A, 312B, 312C, and 312D (one or more of which may be generally referred to as UEs 312) to the core network 306 over one or more wireless connections.

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

The UEs 312 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 310 and other communication devices. Similarly, the network nodes 310 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 312 and/or with other network nodes or equipment in the telecommunication network 302 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 302.

In the depicted example, the core network 306 connects the network nodes 310 to one or more hosts, such as host 316. 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 306 includes one more core network nodes (e.g., core network node 308) 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 308. 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).

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

As a whole, the communication system 300 of Figure 3 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system 300 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.

In some examples, the telecommunication network 302 is a cellular network that implements 3 GPP standardized features. Accordingly, the telecommunication network 302 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 302. For example, the telecommunication network 302 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 312 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 304 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 304. 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. be configured for Multi -Radio Dual Connectivity (MR-DC), such as Evolved UMTS Terrestrial RAN (E-UTRAN) NR - Dual Connectivity (EN-DC).

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

The hub 314 may have a constant/persistent or intermittent connection to the network node 310B. The hub 314 may also allow for a different communication scheme and/or schedule between the hub 314 and UEs (e.g., UE 312C and/or 312D), and between the hub 314 and the core network 306. In other examples, the hub 314 is connected to the core network 306 and/or one or more UEs via a wired connection. Moreover, the hub 314 may be configured to connect to a Machine-to-Machine (M2M) service provider over the access network 304 and/or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 310 while still connected via the hub 314 via a wired or wireless connection. In some embodiments, the hub 314 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 310B. In other embodiments, the hub 314 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 310B, but which is additionally capable of operating as a communication start and/or end point for certain data channels.

Figure 4 shows a UE 400 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-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.

A UE may support Device-to-Device (D2D) communication, for example by implementing a 3 GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), Vehi cl e-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).

The UE 400 includes processing circuitry 402 that is operatively coupled via a bus 404 to an input/output interface 406, a power source 408, memory 410, a communication interface 412, and/or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 4. 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.

The processing circuitry 402 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 410. The processing circuitry 402 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 402 may include multiple Central Processing Units (CPUs).

In the example, the input/output interface 406 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 400. 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.

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

The memory 410 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 410 includes one or more application programs 414, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 416. The memory 410 may store, for use by the UE 400, any of a variety of various operating systems or combinations of operating systems.

The memory 410 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 410 may allow the UE 400 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 410, which may be or comprise a device-readable storage medium.

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

In the illustrated embodiment, communication functions of the communication interface 412 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/Internet 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.

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

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 400 shown in Figure 4.

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 3 GPP 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.

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.

Figure 5 shows a network node 500 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), and NR Node Bs (gNBs)).

BSs 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 BSs, pico BSs, micro BSs, or macro BSs. A BS 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 BS such as centralized digital units 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 BS may also be referred to as nodes in a Distributed Antenna System (DAS).

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).

The network node 500 includes processing circuitry 502, memory 504, a communication interface 506, and a power source 508. The network node 500 may be composed of multiple physically separate components (e.g., a Node B 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 500 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 Node Bs. In such a scenario, each unique Node B and RNC pair may in some instances be considered a single separate network node. In some embodiments, the network node 500 may be configured to support multiple RATs. In such embodiments, some components may be duplicated (e.g., separate memory 504 for different RATs) and some components may be reused (e.g., an antenna 510 may be shared by different RATs). The network node 500 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 500, 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 500.

The processing circuitry 502 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 500 components, such as the memory 504, to provide network node 500 functionality.

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

The memory 504 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 502. The memory 504 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 502 and utilized by the network node 500. The memory 504 may be used to store any calculations made by the processing circuitry 502 and/or any data received via the communication interface 506. In some embodiments, the processing circuitry 502 and the memory 504 are integrated.

The communication interface 506 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 506 comprises port(s)/terminal(s) 516 to send and receive data, for example to and from a network over a wired connection. The communication interface 506 also includes radio front-end circuitry 518 that may be coupled to, or in certain embodiments a part of, the antenna 510. The radio front-end circuitry 518 comprises filters 520 and amplifiers 522.

The radio front-end circuitry 518 may be connected to the antenna 510 and the processing circuitry 502. The radio front-end circuitry 518 may be configured to condition signals communicated between the antenna 510 and the processing circuitry 502. The radio front-end circuitry 518 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 518 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of the filters 520 and/or the amplifiers 522. The radio signal may then be transmitted via the antenna 510. Similarly, when receiving data, the antenna 510 may collect radio signals which are then converted into digital data by the radio front-end circuitry 518. The digital data may be passed to the processing circuitry 502. In other embodiments, the communication interface 506 may comprise different components and/or different combinations of components.

In certain alternative embodiments, the network node 500 does not include separate radio front-end circuitry 518; instead, the processing circuitry 502 includes radio front-end circuitry and is connected to the antenna 510. Similarly, in some embodiments, all or some of the RF transceiver circuitry 512 is part of the communication interface 506. In still other embodiments, the communication interface 506 includes the one or more ports or terminals 516, the radio frontend circuitry 518, and the RF transceiver circuitry 512 as part of a radio unit (not shown), and the communication interface 506 communicates with the baseband processing circuitry 514, which is part of a digital unit (not shown).

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

The antenna 510, the communication interface 506, and/or the processing circuitry 502 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node 500. Any information, data, and/or signals may be received from a UE, another network node, and/or any other network equipment. Similarly, the antenna 510, the communication interface 506, and/or the processing circuitry 502 may be configured to perform any transmitting operations described herein as being performed by the network node 500. Any information, data, and/or signals may be transmitted to a UE, another network node, and/or any other network equipment. The power source 508 provides power to the various components of the network node 500 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 508 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 500 with power for performing the functionality described herein. For example, the network node 500 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 508. As a further example, the power source 508 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.

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

Figure 6 is a block diagram of a host 600, which may be an embodiment of the host 316 of Figure 3, in accordance with various aspects described herein. As used herein, the host 600 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 600 may provide one or more services to one or more UEs.

The host 600 includes processing circuitry 602 that is operatively coupled via a bus 604 to an input/output interface 606, a network interface 608, a power source 610, and memory 612. 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 4 and 5, such that the descriptions thereof are generally applicable to the corresponding components of the host 600.

The memory 612 may include one or more computer programs including one or more host application programs 614 and data 616, which may include user data, e.g. data generated by a UE for the host 600 or data generated by the host 600 for a UE. Embodiments of the host 600 may utilize only a subset or all of the components shown. The host application programs 614 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 614 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 600 may select and/or indicate a different host for Over-The-Top (OTT) services for a UE. The host application programs 614 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 7 is a block diagram illustrating a virtualization environment 700 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 700 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.

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

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

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

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

The hardware 704 may be implemented in a standalone network node with generic or specific components. The hardware 704 may implement some functions via virtualization. Alternatively, the hardware 704 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 710, which, among others, oversees lifecycle management of the applications 702. In some embodiments, the hardware 704 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 BS. In some embodiments, some signaling can be provided with the use of a control system 712 which may alternatively be used for communication between hardware nodes and radio units.

Figure 8 shows a communication diagram of a host 802 communicating via a network node 804 with a UE 806 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as the UE 312A of Figure 3 and/or the UE 400 of Figure 4), the network node (such as the network node 310A of Figure 3 and/or the network node 500 of Figure 5), and the host (such as the host 316 of Figure 3 and/or the host 600 of Figure 6) discussed in the preceding paragraphs will now be described with reference to Figure 8.

Like the host 600, embodiments of the host 802 include hardware, such as a communication interface, processing circuitry, and memory. The host 802 also includes software, which is stored in or is accessible by the host 802 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 806 connecting via an OTT connection 850 extending between the UE 806 and the host 802. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection 850.

The network node 804 includes hardware enabling it to communicate with the host 802 and the UE 806 via a connection 860. The connection 860 may be direct or pass through a core network (like the core network 306 of Figure 3) 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.

The UE 806 includes hardware and software, which is stored in or accessible by the UE 806 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 806 with the support of the host 802. In the host 802, an executing host application may communicate with the executing client application via the OTT connection 850 terminating at the UE 806 and the host 802. 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 850 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 850.

The OTT connection 850 may extend via the connection 860 between the host 802 and the network node 804 and via a wireless connection 870 between the network node 804 and the UE 806 to provide the connection between the host 802 and the UE 806. The connection 860 and the wireless connection 870, over which the OTT connection 850 may be provided, have been drawn abstractly to illustrate the communication between the host 802 and the UE 806 via the network node 804, without explicit reference to any intermediary devices and the precise routing of messages via these devices.

As an example of transmitting data via the OTT connection 850, in step 808, the host 802 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 806. In other embodiments, the user data is associated with a UE 806 that shares data with the host 802 without explicit human interaction. In step 810, the host 802 initiates a transmission carrying the user data towards the UE 806. The host 802 may initiate the transmission responsive to a request transmitted by the UE 806. The request may be caused by human interaction with the UE 806 or by operation of the client application executing on the UE 806. The transmission may pass via the network node 804 in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 812, the network node 804 transmits to the UE 806 the user data that was carried in the transmission that the host 802 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 814, the UE 806 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 806 associated with the host application executed by the host 802.

In some examples, the UE 806 executes a client application which provides user data to the host 802. The user data may be provided in reaction or response to the data received from the host 802. Accordingly, in step 816, the UE 806 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 806. Regardless of the specific manner in which the user data was provided, the UE 806 initiates, in step 818, transmission of the user data towards the host 802 via the network node 804. In step 820, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 804 receives user data from the UE 806 and initiates transmission of the received user data towards the host 802. In step 822, the host 802 receives the user data carried in the transmission initiated by the UE 806.

One or more of the various embodiments improve the performance of OTT services provided to the UE 806 using the OTT connection 850, in which the wireless connection 870 forms the last segment.

In an example scenario, factory status information may be collected and analyzed by the host 802. As another example, the host 802 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host 802 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host 802 may store surveillance video uploaded by a UE. As another example, the host 802 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 802 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.

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 850 between the host 802 and the UE 806 in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection 850 may be implemented in software and hardware of the host 802 and/or the UE 806. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 850 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 850 may include message format, retransmission settings, preferred routing, etc.; the reconfiguring need not directly alter the operation of the network node 804. 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 802. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 850 while monitoring propagation times, errors, etc.

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.

Some example embodiments of the present disclosure are as follows:

Group A Embodiments

Embodiment 1 : A method performed by a user equipment, UE, (312), the method comprising:

• receiving (100), from a network node (310), information comprising a first barring associated indication;

• determining (102) whether the first barring associated indication is set to a value that indicates that a second barring associated indication is also included in the information;

• if the first barring associated indication is set to the value that indicates that the second barring associated indication is also included in the received information (step 102, YES): o obtaining (104) the second barring associated indication from the received information; o performing (106) one or more actions based on a value of the second barring associated indication;

• if the first barring associated indication is not set to the value that indicates that the second barring associated indication is also included in the received information (step 102, NO): o performing (108) one or more actions based on a value of the first barring associated indication. Embodiment 2: A method performed by a user equipment, UE, (312), the method comprising:

• determining (102, YES) that the first barring associated indication is set to a value that indicates that a second barring associated indication is also included in the received information;

• responsive to determining (102, YES) that the first barring associated indication is set to the value that indicates that the second barring associated indication is also included in the received information, obtaining (104) the second barring associated indication from the received information;

• performing (106) one or more actions based on a value of the second barring associated indication.

Embodiment 3 : The method of embodiment 1 or 2 wherein the first barring associated indication and the second barring associated indication are for a respective cell (e.g., are defined per cell).

Embodiment 4: The method of any of embodiments 1 to 3 wherein the first barring associated indication is an additionalSpectrumEmission field, and the second barring associated indication is a field that extended a range of permissible values of the additionalSpectrumEmission fi el d .

Embodiment 5: The method of any of embodiments 1 to 3 wherein the first barring associated indication is an additionalSpectrumEmission field, and the second barring associated indication is an additionalSpectrumEmissionExt field.

Embodiment 6: The method of embodiment 4 or 5 wherein the value of the first barring associated indication that indicates that the second barring associated indication is also included in the received information is a value of 7.

Embodiment 7: The method of any of embodiments 4 to 6 wherein the network node is a network node in a cellular communications system.

Embodiment 8: The method of any of embodiments 4 to 6 wherein the network node is a network node in a radio access network of a 3GPP cellular communications system.

Embodiment 9: The method of any of embodiments 1 to 8 wherein a default value is defined for the first barring associated indication but not the second barring associated indication.

Embodiment 10: The method of any of embodiments 1 to 9 wherein performing (106) the one or more actions based on the value of the second barring associated indication comprises: determining (106A) whether the UE is barred from a respective cell based on the value of the second barring associated indication; and operating (106B) in accordance with a result of the determining (106A). Embodiment 11 : The method of any of the previous embodiments, further comprising: providing user data; and forwarding the user data to a host via the transmission to the network node.

Group B Embodiments

Embodiment 12: A method performed by a network node (310), the method comprising:

• determining (200) a value to be signaled to one or more User Equipments (312) via a barring associated indication;

• if the determined value is not supported by a first barring associated indication (202, NO): o setting (204) the first barring associated indication to a value that indicates that a second barring associated indication is present; o setting (206) the second barring associated indication to the determined value; and o transmitting (208), to one or more UEs, information that comprises the first barring associated indication and the second barring associated indication;

• if the determined value is supported by the first barring associated indication (202, YES): o setting (210) the first barring associated indication to the determined value; and o transmitting (212), to one or more UEs, information that comprises the first barring associated indication.

Embodiment 13 : A method performed by a network node (310), the method comprising:

• determining (202, NO) that the determined value is not supported by a first barring associated indication; and

• responsive to determining (202, NO) that the determined value is not supported by the first barring associated indication: o setting (204) the first barring associated indication to a value that indicates that a second barring associated indication is present; o setting (206) the second barring associated indication to the determined value; and

• transmitting (208), to one or more UEs, information that comprises the first barring associated indication and the second barring associated indication.

Embodiment 14: The method of embodiment 12 or 13 wherein the first barring associated indication and the second barring associated indication are for a respective cell (e.g., are defined per cell).

Embodiment 15: The method of any of embodiments 12 to 14 wherein the first barring associated indication is an additionalSpectrumEmission field, and the second barring associated indication is a field that extended a range of permissible values of the additionalSpectrumEmission fi el d .

Embodiment 16: The method of any of embodiments 12 to 14 wherein the first barring associated indication is an additionalSpectrumEmission field, and the second barring associated indication is an additionalSpectrumEmissionExt field.

Embodiment 17: The method of embodiment 15 or 16 wherein the value of the first barring associated indication that indicates that the second barring associated indication is also included in the received information is a value of 7.

Embodiment 18: The method of any of embodiments 15 to 17 wherein the network node is a network node in a cellular communications system.

Embodiment 19: The method of any of embodiments 15 to 17 wherein the network node is a network node in a radio access network of a 3GPP cellular communications system.

Embodiment 20: The method of any of embodiments 12 to 19 wherein a default value is defined for the first barring associated indication but not the second barring associated indication.

Embodiment 21 : 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.

Group C Embodiments

Embodiment 22: A user equipment 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.

Embodiment 23: A network node comprising: processing circuitry configured to perform any of the steps of any of the Group B embodiments; and power supply circuitry configured to supply power to the processing circuitry.

Embodiment 24: A user equipment (UE) comprising: an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; the processing circuitry being configured to perform any of the steps of any of the Group A embodiments; an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the UE.

Embodiment 25 : 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 cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform any of the steps of any of the Group A embodiments to receive the user data from the host.

Embodiment 26: The host of the previous embodiment, wherein the cellular network further includes a network node configured to communicate with the UE to transmit the user data to the UE from the host.

Embodiment 27: The host of the previous 2 embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing 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.

Embodiment 28: A method implemented by a host operating 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 UE performs any of the operations of any of the Group A embodiments to receive the user data from the host.

Embodiment 29: The method of the previous embodiment, further comprising: at the host, executing a host application associated with a client application executing on the UE to receive the user data from the UE.

Embodiment 30: The method of the previous embodiment, further comprising: at the host, transmitting input data to the client application executing on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application.

Embodiment 31 : 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 cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform any of the steps of any of the Group A embodiments to transmit the user data to the host.

Embodiment 32: The host of the previous embodiment, wherein the cellular network further includes a network node configured to communicate with the UE to transmit the user data from the UE to the host. Embodiment 33 : The host of the previous 2 embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing 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.

Embodiment 34: 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, receiving user data transmitted to the host via the network node by the UE, wherein the UE performs any of the steps of any of the Group A embodiments to transmit the user data to the host.

Embodiment 35: The method of the previous embodiment, further comprising: at the host, executing a host application associated with a client application executing on the UE to receive the user data from the UE.

Embodiment 36: The method of the previous embodiment, further comprising: at the host, transmitting input data to the client application executing on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application.

Embodiment 37: 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 B embodiments to transmit the user data from the host to the UE.

Embodiment 38: The host of the previous embodiment, wherein: the processing circuitry of the host is configured to execute a host application that provides the user data; and 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.

Embodiment 39: 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 B embodiments to transmit the user data from the host to the UE.

Embodiment 40: The method of the previous embodiment, further comprising, at the network node, transmitting the user data provided by the host for the UE. Embodiment 41 : 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.

Embodiment 42: A communication system configured to provide an over-the-top 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 B embodiments to transmit the user data from the host to the UE.

Embodiment 43 : The communication system of the previous embodiment, further comprising: the network node; and/or the user equipment.

Embodiment 44: 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 B embodiments to receive the user data from a user equipment (UE) for the host.

Embodiment 45: The host of the previous 2 embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing 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.

Embodiment 46: The host of the any of the previous 2 embodiments, wherein the initiating receipt of the user data comprises requesting the user data.

Embodiment 47 : 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 B embodiments to receive the user data from the UE for the host.

Embodiment 48: The method of the previous embodiment, further comprising at the network node, transmitting the received user data to the host. 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

1. A method performed by a user equipment, UE, (312), the method comprising: receiving (100), from a network node (310), information comprising a first barring associated indication; determining (102, YES) that the first barring associated indication is set to a value that indicates that a second barring associated indication is also included in the received information; responsive to determining (102, YES) that the first barring associated indication is set to the value that indicates that the second barring associated indication is also included in the received information, obtaining (104) the second barring associated indication from the received information; performing (106) one or more actions based on a value of the second barring associated indication.

2. The method of claim 1 wherein the first barring associated indication is an additionalSpectrumEmission field, and the second barring associated indication is a field that extends a range of permissible values of the additionalSpectrumEmission field.

3. The method of claim 2 wherein the value of the first barring associated indication that indicates that the second barring associated indication is also included in the received information is a value of 7.

4. The method of any of claims 1 to 3 wherein the received information is system information.

5. The method of any of claims 1 to 4 wherein the first barring associated indication and the second barring associated indication are for a respective cell.

6. The method of any of claims 1 to 5 wherein a default value is defined for the first barring associated indication but not the second barring associated indication.

7. The method of any of claims 1 to 6 wherein performing (106) the one or more actions based on the value of the second barring associated indication comprises: determining (106A) whether the UE is barred from a respective cell based on the value of the second barring associated indication; and operating (106B) in accordance with a result of the determining (106A).

8. The method of any of claims 1 to 7 wherein by being set to the first value, the first barring associated indication is not considered by the UE as indicating a value for the barring function, but rather to be considered by the UE as an indication that the UE is to inspect, consider, or apply the value of the second barring associated indication.

9. The method of any of claims 1 to 8 wherein the network node is a network node in a cellular communications system.

10. The method of any of claims 1 to 8 wherein the network node is a network node in a radio access network of a 3GPP cellular communications system.

11. A user equipment, UE, (312) adapted to: receive (100), from a network node (310), information comprising a first barring associated indication; determine (102, YES) that the first barring associated indication is set to a value that indicates that a second barring associated indication is also included in the received information; responsive to determining (102, YES) that the first barring associated indication is set to the value that indicates that the second barring associated indication is also included in the received information, obtain (104) the second barring associated indication from the received information; perform (106) one or more actions based on a value of the second barring associated indication.

12. The UE of claim 11 wherein the first barring associated indication is an additionalSpectrumEmission field, and the second barring associated indication is a field that extends a range of permissible values of the additionalSpectrumEmission field.

13. The UE of claim 12 wherein the value of the first barring associated indication that indicates that the second barring associated indication is also included in the received information is a value of 7.

14. The UE of any of claims 11 to 13 further adapted to perform the method of any of embodiments 4 to 10.

15. A user equipment, UE, (312; 400) comprising: a communication interface (412); and processing circuitry (402) associated with the communication interface (412), the processing circuitry (402) configured to cause the UE (312; 400) to: receive (100), from a network node (310), information comprising a first barring associated indication; determine (102, YES) that the first barring associated indication is set to a value that indicates that a second barring associated indication is also included in the received information; responsive to determining (102, YES) that the first barring associated indication is set to the value that indicates that the second barring associated indication is also included in the received information, obtain (104) the second barring associated indication from the received information; perform (106) one or more actions based on a value of the second barring associated indication.

16. The UE of claim 15 wherein the first barring associated indication is an additionalSpectrumEmission field, and the second barring associated indication is a field that extends a range of permissible values of the additionalSpectrumEmission field.

17. The UE of claim 16 wherein the value of the first barring associated indication that indicates that the second barring associated indication is also included in the received information is a value of 7.

18. The UE of any of claims 15 to 17 wherein the processing circuitry is further configured to cause the UE to perform the method of any of embodiments 4 to 10.

19. A computer program comprising instructions which, when executed on at least one processor, cause the processor to carry out the method according to any of claims 1 to 10.

20. A carrier containing the computer program of claim 19, wherein the carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium.

21. A non-transitory computer-readable medium comprising instructions executable by processing circuitry of a User Equipment, UE, whereby the UE is operable to: receive (100), from a network node (310), information comprising a first barring associated indication; determine (102, YES) that the first barring associated indication is set to a value that indicates that a second barring associated indication is also included in the received information; responsive to determining (102, YES) that the first barring associated indication is set to the value that indicates that the second barring associated indication is also included in the received information, obtain (104) the second barring associated indication from the received information; perform (106) one or more actions based on a value of the second barring associated indication.

22. The non-transitory computer-readable medium of claim 21 wherein the first barring associated indication is an additionalSpectrumEmission field, and the second barring associated indication is a field that extends a range of permissible values of the additionalSpectrumEmission field.

23. The non-transitory computer-readable medium of claim 22 wherein the value of the first barring associated indication that indicates that the second barring associated indication is also included in the received information is a value of 7.

24. A method performed by a network node (310), the method comprising:

• determining (200) a value to be signaled to one or more User Equipments, UEs, (312) via a barring associated indication;

25. The method of claim 24 wherein the first barring associated indication is an additionalSpectrumEmission field, and the second barring associated indication is a field that extended a range of permissible values of the additionalSpectrumEmission field.

26. The method of claim 25 wherein the value of the first barring associated indication that indicates that the second barring associated indication is also included in the received information is a value of 7.

27. The method of any of claims 24 to 26 wherein the transmitted information is system information.

28. The method of any of claims 24 to 27 wherein the first barring associated indication and the second barring associated indication are for a respective cell.

29. The method of any of claims 24 to 28 wherein a default value is defined for the first barring associated indication but not the second barring associated indication.

30. The method of any of claims 24 to 29 wherein by being set to the first value, the first barring associated indication is not to be considered by the UE as indicating a value for the barring function, but rather to be considered by the UE as an indication that the UE is to inspect, consider, or apply the value of the second barring associated indication.

31. The method of any of claims 24 to 30 wherein the network node is a network node in a cellular communications system.

32. The method of any of claims 24 to 30 wherein the network node is a network node in a radio access network of a 3GPP cellular communications system.

33. A network node (310) adapted to :

• determine (200) a value to be signaled to one or more User Equipments (312) via a barring associated indication;

• determine (202, NO) that the determined value is not supported by a first barring associated indication; and

• responsive to determining (202, NO) that the determined value is not supported by the first barring associated indication: o set (204) the first barring associated indication to a value that indicates that a second barring associated indication is present; o set (206) the second barring associated indication to the determined value; and

• transmit (208), to one or more UEs, information that comprises the first barring associated indication and the second barring associated indication.

34. The network node (310) of claim 33 further adapted to perform the method of any of claims 25 to 32.

35. A network node (310; 500) comprising:

• a communication interface (506); and

• processing circuitry (502) associated with the communication interface (506), the processing circuitry (502) configured to cause the network node (310; 500) to: o determine (200) a value to be signaled to one or more User Equipments (312) via a barring associated indication; o determine (202, NO) that the determined value is not supported by a first barring associated indication; and o responsive to determining (202, NO) that the determined value is not supported by the first barring associated indication:

■ set (204) the first barring associated indication to a value that indicates that a second barring associated indication is present;

■ set (206) the second barring associated indication to the determined value; and o transmit (208), to one or more UEs, information that comprises the first barring associated indication and the second barring associated indication.

36. The network node (310; 500) of claim 35 wherein the processing circuitry is further configured to cause the network node (310; 500) to perform the method of any of claims 25 to 32.

37. A computer program comprising instructions which, when executed on at least one processor, cause the processor to carry out the method according to any of claims 24 to 32.

38. A carrier containing the computer program of claim 37, wherein the carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium.

39. A non-transitory computer-readable medium comprising instructions executable by processing circuitry of a network node, whereby the network node is operable to: