Method of broadcast and index generation in ue

Abstract

According to certain embodiments, a method in a wireless device includes detecting system information broadcast from a network node. The system information includes a list of network public network (NPN) identifiers identifying a plurality of NPNs. The method includes selecting a network from the plurality of NPNs and determining an index value associated with the selected network. When the NPN identifier associated with the selected network includes a closed access group (CAG) identifier, determining the index value is based at least in part on a public land mobile network (PLMN) element included in the list of NPN identifiers in combination with at least one CAG identifier. When the NPN identifier associated with the selected network includes a network identifier (NID), determining the index value is based at least in part on a number of NIDs included in the list of NPN identifiers.

Description

BACKGROUND

[0001] The Third Generation Partnership Project (3GPP) is currently working on specifications commonly referred to as "5G" or "Fifth Generation". In these works, various requirements are listed and various solutions are proposed. For example, solutions exist for connecting New Radio Access to a New Core Network. New Radio Access is commonly referred to as "NR". New Core Network is commonly referred to as "5G Core Network" or simply "5GC". The term "5G System" or simply "5GS" is sometimes also referred to as the complete system consisting of.

[0002] Thus, the 5G System defined by 3GPP in Release 15 (Rel-15) comprises both New Radio Access (NR) and New Core Network (5GC). The 5GC provides several new features such as support for network slicing, improved Quality of Service (QoS) and latency and battery optimization in the form of a new User Equipment (UE) state called "Inactivity Mode".

[0003] 5G System is commonly referred to as "public system", i.e. Public Land Mobile Network (PLMN). This means that anyone can obtain a subscription and access to the network. This is for example in contrast to some other networks that can only be accessed by specific UEs and for which it is not possible to simply obtain access with a subscription / credentials. One such example of a "private" network is a Wi-Fi router that is deployed as an extension of a private broadband connection, e.g. a broadband subscription over fiber, xDSL ("Digital Subscriber Line" where "x" is a wildcard that can represent a type of DSL such as Asynchronous DSL or Synchronous DSL) or similar connection. For this, not anyone can obtain access. This is a type of private network. A private network can also be referred to as "non-public network" or simply "NPN".

[0004] While Wide Local Area Networks (WLAN) are a different access than 5G, there is currently activity related to the possibility to provide deployments that also use 5G access and 5G core network for these NPNs. The target can not be exactly corresponding to a home Wi-Fi access point, but for example to deploy an NPN in a factory, possibly connecting factory equipment, vehicles and employees. These types of deployments can pose completely different requirements. As an example, these types of networks can have different security requirements. As another example, these types of networks can have different roaming requirements - in some cases, roaming work (i.e. in order to seamlessly transfer a connection from within a private network to a "public" network) can be important. In other cases, roaming should definitely not be supported. One example can be that connected machinery should preferably only work in the private network and should not be able to connect, for example, through any other access point / cell or gNB ("gNB" denotes a base station in NR).

[0005] 3GPP has made requirements on how NPNs should work and has performed a study on how to meet the requirements. The requirements are described in 3GPP document 22.261 (vl6.6.0) and are copied below:

[0006] * ~ * ~ * ~ *~ *~ *~ *~ *~ *~ *~ *~ *~ *~ *~ *~ *~ *~ *~ *~ *~ *~ *~

[0007] Non-public networks are intended to be used by private entities, such as enterprises, only and can be deployed in a variety of configurations, making use of both virtual and physical elements. In particular, they can be deployed as fully independent networks, they can be hosted by a PLMN, or they can be provided as a slice of a PLMN.

[0008] In any of these deployment options, it is expected that an unauthorized UE (not those associated with the enterprise) will not attempt to access the non-public network, which can result in resources being used to reject that UE and thereby unavailable to the enterprise's UEs. It is also expected that the enterprise's UEs will not attempt to access networks they are not authorized to access. For example, some enterprise UEs can be restricted to accessing only the enterprise's non-public network, even if a PLMN coverage is available in the same geographical area. Other enterprise UEs can be able to access both the non-public network and the PLMN, with specific permission.

[0009] 6.25.2 Requirements

[0010] The 5G system shall support non-public networks.

[0011] The 5G system shall support non-public networks providing coverage within a specific geographical area.

[0012] The 5G system shall support both physical and virtual non-public networks.

[0013] The 5G system shall support independent operation of non-public networks, i.e. a non-public network can be able to operate without relevance to a PLMN.

[0014] The 5G system shall support non-public network subscribers:

[0015] - access to subscribed PLMN services via the non-public network;

[0016] - seamless service continuity of subscribed PLMN services between the non-public network and the PLMN;

[0017] - access to selected non-public network services via the PLMN;

[0018] Seamless service continuity of non-public network services between non-public networks and PLMNs.

[0019] Non-public network subscribers accessing PLMN services should have a service subscription using 3GPP identifiers and credentials provided or accepted by the PLMN.

[0020] The 5G system shall support mechanisms for UEs to identify and select non-public networks.

[0021] NOTE: Different network selection mechanisms can be used for physical and virtual non-public networks.

[0022] The 5G system shall support a large number of identifiers for non-public networks to minimize the likelihood of collisions between assigned identifiers.

[0023] The 5G system shall support a mechanism that prevents a UE with a subscription to a non-public network from automatically selecting and attaching to a PLMN or non-public network that it is not authorized to select.

[0024] The 5G system shall support a mechanism that prevents a UE with a subscription to a PLMN from automatically selecting and attaching to a non-public network that it is not authorized to select.

[0025] The 5G system shall support a host of a non-public network to change from one PLMN to another without changing the network selection information stored in UEs of the non-public network.

[0026] * ~ * ~ * ~ *~ *~ *~ *~ *~ *~ *~ *~ *~ *~ *~ *~ *~ *~ *~ *~ *~ *~ *~

[0027] Requirements have been studied and there are two different solutions that have been standardized.

[0028] Integration of private networks (PNI-NPN) via public network of a PLMN

[0029] By allocating one or more network slices or data networks to a non-public network, the PNI-NPN is made available via the PLMN. Since network slices cannot achieve to avoid the possibility that a UE manages to access a network in an area where the UE is not allowed to use the network slice, the use of a closed access group (CAG) can be used in addition to network slices to apply additional access control. In this case, the PNI-NPN is identified by a combination of a PLMN ID and a CAG ID, where the CAG ID is unique within the scope of the PLMN or at least the cells that will be used for the PNI-NPN are identified by the PLMN ID and the CAG ID (i.e. the actual NPN can be identified by other means in dedicated signaling, e.g. a network slice ID). Optionally, in case of manual CAG selection, a human-readable network name (HRNN) can also be provided to help the user. The human-readable network name shall support the manual network selection procedure. There is no need to associate a CAG with a specific data network or slice, it will be fully possible to use a CAG that is also related to the same slice as used without a CAG.

[0030] Stand-alone NPN (SNPN)

[0031] SNPNs operate without relevance to a PLMN and are identified by a combination of a PLMN ID and a network ID (NID). Unlike the PLMN ID used by PLMNs, the PLMN ID used by SNPNs is not required to be unique, i.e. it is possible that two SNPNs share the same PLMN ID. For example, based on the Mobile Country Code (MCC) 999 assigned by the International Telecommunication Union (ITU), a PLMN ID reserved for private networks can be used for non-public networks. The NID can be seen as an extension of the PLMN ID and supports different assignment models. For example,

[0032] - A locally managed NID is assumed to be chosen by the SNPN individually at deployment time (and thus can not be unique in all cases);

[0033] - A universally managed NID is managed by a central entity per region and is assumed to be globally unique.

[0034] Similar to PNI-NPNs, a HRNN can optionally be provided to help the user to identify the SNPN during manual network selection.

[0035] As can be seen from the above, the identities used by PNI-NPN and SNPN are similar. The SNPN uses a PLMN ID + NID, while the PNI-NPN uses a PLMN ID + CAG ID. The other difference is that the SNPN can use a PLMN ID reserved for private use, while the PNI-NPN uses the PLMN ID of its hosting PLMN, i.e. a public PLMN ID.

[0036] Thus, the SNPN / NID solution principles are:

[0037] - The combination of PLMN ID and NID identifies the SNPN;

[0038] - The NID can be globally unique or locally managed;

[0039] - The NG-RAN node supports broadcasting a total of twelve NIDs;

[0040] - Optional per-NID human-readable network name for manual selection;

[0041] - Optional cell broadcast information preventing UEs not supporting SNPN from accessing the cell;

[0042] - When a UE is set to work in SNPN access mode, the UE only selects and registers with SNPNs;

[0043] - The UE provides the PLMN ID and NID as the selected PLMN, and the NG-RAN provides the PLMN ID and NID as the selected PLMN to the 5GC;

[0044] - The Access and Mobility Management Function (AMF) performs access control and rejects the UE if it has no subscription for SNPN;

[0045] - Unified Access Control (UAC) information is configured per non-public network.

[0046] The NID is used together with the PLMN ID during network selection and is thus seen as an extension of the network identity (i.e. the PLMN ID). This is understood from the statement: "A UE working in SNPN access mode only selects cells and networks that broadcast both the PLMN ID and the NID of the selected SNPN".

[0047] The PNI-NPN / CAG solution principle is that existing functionality (e.g. network slicing) is used to deploy NPNs within a public network, and in addition, for access control purposes, a closed access group can be used as described below:

[0048] - CAG cells broadcast one or more CAG identifiers per PLMN (assuming next generation radio access network (NG-RAN) nodes support broadcasting a total of twelve CAG identifiers) and optionally a human-readable network name per CAG identifier;

[0049] - PLMN / network selection using the PLMN ID and, within the selected PLMN, using the allowed CAG list and optionally an indication that only CAG cells are allowed to be accessed by the UE to derive allowed cells. Then cell selection / reselection is performed using the CAG information and knowledge of whether the UE is provided with an indication of only CAG access, then cell selection is also able to perform cell (re)selection to non-CAG non-SNPN cells of the selected PLMN-ID.

[0050] - Since there can be multiple CAG identifiers per PLMN ID, the UE provides the selected CAG identifier to the NG-RAN and the NG-RAN provides the CAG identifier to the AMF over N2;

[0051] - Mobile restrictions are extended (for the UE in NAS and the NG-RAN over N2) with the allowed CAG list and an indication of whether only CAG cells are allowed to be accessed by the UE; and

[0052] - CAG cells should broadcast information so that only CAG-enabled UEs are accessing the cell (i.e. the cell is a CAG cell or a normal PLMN cell).

[0053] Some of the features of the solution include allowing the PLMN operator to manage its network and the identities used without the need for external registration, as the CAGs are defined within the scope of the PLMN ID.

[0054] In defining a new network type as described above, there is a need to support some kind of broadcast so that the UE can obtain information about what networks are supported in the cell. This is typically done so that the RAN sends the broadcast information. In systems according to the 3GPP NR and 5G system standards, the networks are typically listed in a message called System Information Block 1 (SIB1).

[0055] SIB 1 includes information such as whether the cell is accessible or whether it is barred, whether the cell supports emergency services, and whether there are any restrictions in terms of what the UE can access. Another information element included is a list of supported PLMNs. This list also provides the opportunity to assign a particular cell identity (Cell Identity), tracking area code (TAC), and ran area code (RAN AC) to different PLMNs or different networks. In the 3GPP Technical Specification (TS) 38.331 standard, the information element (IE) that includes such a network list or PLMN list is called cellAccessRelatedlnfo, and it is included in SIB1. The following excerpt from the specification describes the cellAccessRelatedlnfo information element:

[0056] CellAccessRelatedlnfo

[0057] The IE CellAccessRelatedlnfo indicates the cell access related information of this cell.

[0058] CellAccessRelatedlnfo information element

[0059] -- ASN1START

[0060] -- TAG-CELLACCESSRELATEDINFO-START

[0061] CellAccessRelatedlnfo ::= SEQUENCE {

[0062] plmn-IdentityList PLMN-IdentitylnfoList,

[0063] cellReservedForOtherUse ENUMERATED {true} OPTIONAL, -- Need R ...

[0064] }

[0065] -- TAG-CELLACCESSRELATEDINFO-STOP

[0066] -- ASN1STOP

[0067]

[0068] Now, there are proposals that NPNs should be listed in a separate information element. As described below:

[0069] - CellAccessRelatedInfo

[0070] IE CellAccessRelatedInfo indicates the cell access related information of this cell.

[0071] CellAccessRelatedInfo information element

[0072] -- ASN1START

[0073] -- TAG-CELLACCESSRELATEDINFO-START

[0074] CellAccessRelatedInfo ::= SEQUENCE {

[0075] plmn-IdentityList PLMN-IdentityInfoList,

[0076] cellReservedForOtherUse ENUMERATED {true} OPTIONAL, --Need R ... [[

[0078] cellReservedForFutureUse-r16 ENUMERATED {true} OPTIONAL, --Need R

[0079] NPN-IdentityInfoList-r16 NPN-IdentityInfoList-r16 OPTIONAL --Need R ]]

[0081] }

[0082] -- TAG-CELLACCESSRELATEDINFO-STOP

[0083] -- ASN1STOP

[0084]

[0085] Editor's note: The definition of the network index for NPN is FFS.

[0086] Next modification subclause (new information element in 6.3.2)

[0087] NPN-Identity

[0088] The IENPN-Identity includes a list of NIDs or a list of CAG-IDs per PLMN identity. Further information on how to set the IE is specified in TS 23.003

[21] .

[0089] NPN-Identity information element

[0090] -- ASN1START

[0091] -- TAG-NPN-IDENTITY-START

[0092] NPN-Identity-r16 ::= CHOICE {

[0093] pni-npn-r16 SEQUENCE {

[0094] plmn-Identity-r16 PLMN-Identity,

[0095] cag-IdentityList-r16 SEQUENCE (SIZE (1..maxNPN-r16)) OF CAG-Identity-r16

[0096] },

[0097] snpn-r16 SEQUENCE {

[0098] plmn-Identity PLMN-Identity,

[0099] nid-List-r16 SEQUENCE (SIZE (1..maxNPN-r16)) OF NID-r16

[0100] }

[0101] }

[0102] CAG-Identity-r16 ::= BIT STRING (SIZE (32))

[0103] NID-r16 ::= BIT STRING (SIZE (52))

[0104] -- TAG-NPN-IDENTITY-STOP

[0105] -- ASN1STOP

[0106]

[0107] Editor's note: (1) The size of NID will be checked based on the CT4 agreement, (2) The need for a list of NIDs depends on the RAN sharing scenarios to be supported, and (3) Whether all CAG identities associated to the same PLMN identity should be listed in the same cag-IdentityList is FFS.

[0108] Next modification (new information element in 6.3.2)

[0109] NPN-IdentityInfoList

[0110] The IE NPN-IdentityInfoList includes a list of NPN identity information.

[0111] NPN-IdentityInfoList information element

[0112] -- ASN1START

[0113] -- TAG-NPN-IDENTITYINFOLIST-START

[0114] NPN-IdentityInfoList-r16 ::= SEQUENCE (SIZE (1..maxNPN-r16)) OF NPN-IdentityInfo-r16

[0115] NPN-IdentityInfo-r16 ::= SEQUENCE {

[0116] NPN-IdentityList-r16 SEQUENCE (SIZE (1..maxNPN-r16)) OF NPN-Identity-r16,

[0117] trackingAreaCode-r16 TrackingAreaCode,

[0118] ranac-r16 RAN-AreaCode OPTIONAL, -- Need R

[0119] CellIdentity-r16 CellIdentity,

[0120] cellReservedForOperatorUse-r16 ENUMERATED {reserved,notReserved}, ...

[0121] }

[0122] -- TAG-NPN-IDENTITYINFOLIST-STOP

[0123] -- ASN1STOP

[0124]

[0125] As can be seen above, the NPN identity is introduced in the standalone network list, i.e. the NPN-IdentityInfoList in the cellAccessRelatedInfo. In this way, the broadcast information (SIB1) will be able to indicate to the listening UEs whether the cell represented by the SIB1 supports access for various NPN network identities or not. SUMMARY

[0126] There is currently certain problem(s). For example, when a UE signals about what network, what PLMN or NPN it wants to access, it does so in a procedure called Radio Resource Control (RRC) setup procedure. This procedure is detailed in TS 38.331 and it consists of three RRC message exchanges between the UE and the network. The three messages are shown in Figure 1 . Note that there are actually more messages hidden in this figure, but they have been omitted for the purpose of concentrating on the RRC layer. The reason for mentioning this is that the RRCSetupRequest is sometimes called msg3 (as in message 3) and the RRCSetupComplete is called msg5 (or message 5). These msg3 and msg5 references need to be read in context, although in other procedures, the msg5 can be other messages, e.g. resume complete message.

[0127] The RRC setup request message is a very short message, including the UE identity or reference and the setup cause value (i.e. the reason for the access). The RRC setup message includes information from the network about radio bearer configuration and the RRC setup complete message includes further details about what network the UE wants to access. In particular, this message includes a reference to the network the UE wants to access. This indication is not explicit, although it is not the full PLMN ID, but an index to a list of PLMNs included in the SIB1 message.

[0128] In the standards for PLMNs, the PLMN-IdentityInfoList of the PLMNs the UE can access is an input to generate the PLMN-Index, such as:

[0129] For the PLMN contained in the n-th entry of the PLMN-IdentityInfoList and the i-th entry of its corresponding PLMN-IdentityInfo, the PLMN index is defined as b1 + b2 +... + b(n-1) + i, where b(j) is the number of PLMN-Identity entries in each PLMN-IdentityInfo, respectively.

[0130] where

[0131] - PLMN-Identity

[0132] IE PLMN-Identity identifies a Public Land Mobile Network. Further information on how to set the IE is specified in TS 23.003

[21] .

[0133] PLMN-Identity information element

[0134] -- ASN1START

[0135] -- TAG-PLMN-IDENTITY-START

[0136] PLMN-Identity ::= SEQUENCE {

[0137] mcc MCC OPTIONAL, -- Cond MCC

[0138] mnc MNC

[0139] }

[0140] MCC ::= SEQUENCE (SIZE (3)) OF MCC-MNC-Digit

[0141] MNC ::= SEQUENCE (SIZE (2..3)) OF MCC-MNC-Digit

[0142] MCC-MNC-Digit ::= INTEGER (0..9)

[0143] -- TAG-PLMN-IDENTITY-STOP

[0144] -- ASN1STOP

[0145]

[0146]

[0147] – PLMN-IdentityInfoList

[0148] The IE PLMN-IdentityInfoList includes a list of PLMN identity information.

[0149] PLMN-IdentityInfoList information element

[0150] -- ASN1START

[0151] -- TAG-PLMN-IDENTITYINFOLIST-START

[0152] PLMN-IdentityInfoList ::= SEQUENCE (SIZE (1..maxPLMN)) OF PLMN-IdentityInfo

[0153] PLMN-IdentityInfo ::= SEQUENCE {

[0154] plmn-IdentityList SEQUENCE (SIZE (1..maxPLMN)) OF PLMN-Identity,

[0155] trackingAreaCode TrackingAreaCode OPTIONAL, -- Need R

[0156] ranac RAN-AreaCode OPTIONAL, -- Need R

[0157] CellIdentity CellIdentity,

[0158] cellReservedForOperatorUse ENUMERATED {reserved, notReserved}, ...

[0159] }

[0160] -- TAG-PLMN-IDENTITYINFOLIST-STOP

[0161] -- ASN1STOP

[0162]

[0163] The rules only apply to one list for obvious reasons as the principle of the UE generating the index only extends to the PLMN.

[0164] There is currently no solution on how the index generation for NPNs should be done.

[0165] Certain aspects of the present disclosure and their embodiments can provide solutions to these or other difficulties. Generally, certain embodiments of the present disclosure provide solutions for deploying non-public networks and for broadcast and network index generation by networks and UEs in such networks.

[0166] In one aspect of the present disclosure, a method for a UE is provided to generate a network identification index from information provided in a broadcast. The network identification index is valid for signaling an intention to access a non-public network.

[0167] In another aspect of the present disclosure, a method in a network is provided for broadcasting a human-readable network name of an NPN connected to the network in such a way that there is a one-to-one mapping between the hrnn element in the broadcast of CAG and NID from SIB1 and the new broadcast / new SIB carrying the HRNN.

[0168] Various embodiments are presented herein that address one or more of the problems disclosed herein.

[0169] According to certain embodiments, a wireless device includes power supply circuitry configured to supply power to the wireless device and processing circuitry. The processing circuitry is configured to detect system information broadcast from a network node. The system information includes a list of non-public network (NPN) identifiers identifying a plurality of NPNs. The processing circuitry is configured to select a network from the plurality of NPNs and determine an index value associated with the selected network. When the NPN identifier associated with the selected network includes a closed access group (CAG) identifier, the index value is determined based at least in part on a public land mobile network (PLMN) identity included in the list of NPN identifiers in combination with at least one CAG identifier. When the NPN identifier associated with the selected network includes a network identifier (NID), the index value is determined based at least in part on a number of NIDs included in the list of NPN identifiers.

[0170] According to certain embodiments, a method in a wireless device includes detecting system information broadcast from a network node. The system information includes a list of network public network (NPN) identifiers identifying a plurality of NPNs. The method includes selecting a network from the plurality of NPNs and determining an index value associated with the selected network. When the NPN identifier associated with the selected network includes a closed access group (CAG) identifier, determining the index value is based at least in part on a public land mobile network (PLMN) identity included in the list of NPN identifiers in combination with at least one CAG identifier. When the NPN identifier associated with the selected network includes a network identifier (NID), determining the index value is based at least in part on a number of NIDs included in the list of NPN identifiers.

[0171] According to certain embodiments, a network node includes power supply circuitry configured to supply power to the network node. The network node further includes processing circuitry configured to broadcast system information and determine an index value associated with a network of a plurality of non-public networks (NPNs), the system information including a list of NPN identifiers identifying the plurality of NPNs. When the NPN identifier associated with the network includes a closed access group (CAG) identifier, determining the index value is based at least in part on a public land mobile network (PLMN) identity included in the list of NPN identifiers in combination with at least one CAG identifier. When the NPN identifier associated with the network includes a network identifier (NID), determining the index value is based at least in part on a number of NIDs included in the list of NPN identifiers.

[0172] According to certain embodiments, a method in a network node includes broadcasting system information and determining an index value associated with a network of a plurality of non-public networks (NPNs), the system information including a list of NPN identifiers identifying the plurality of NPNs. When the NPN identifier associated with the network includes a closed access group (CAG) identifier, determining the index value is based at least in part on a public land mobile network (PLMN) identity included in the list of NPN identifiers in combination with at least one CAG identifier. When the NPN identifier associated with the network includes a network identifier (NID), determining the index value is based at least in part on a number of NIDs included in the list of NPN identifiers.

[0173] According to certain embodiments, a wireless device comprises power supply circuitry configured to supply power to the wireless device, and processing circuitry. The processing circuitry is configured to detect first system information broadcast from a network node. The first system information comprises a plurality of non-public network (NPN) elements identifying a plurality of NPNs. The processing circuitry is further configured to detect second system information broadcast from the network node. The second system information comprises a plurality of human-readable network name (HRNN) elements. Each HRNN element corresponds to a respective NPN element of the first system information, and each HRNN element indicates name information. The name information comprises an HRNN associated with the respective NPN or, if the second system information does not comprise any HRNN associated with the respective NPN, a "no name" indicator. The processing circuitry is further configured to associate the name information of the second system information with the corresponding NPN element of the first system information. The association is based on an ithNPN element corresponding to an ithHRNN element. The processing circuitry is configured to use an HRNN corresponding to one of the NPN elements to identify a respective NPN associated with the one of the NPN elements.

[0174] According to certain embodiments, a method in a wireless device comprises detecting first system information broadcast from a network node. The first system information comprises a plurality of non-public network (NPN) elements identifying a plurality of NPNs. The method further comprises detecting second system information broadcast from the network node. The second system information comprises a plurality of human-readable network name (HRNN) elements. Each HRNN element corresponds to a respective NPN element of the first system information, and each HRNN element indicates name information. The name information comprises an HRNN associated with the respective NPN or, if the second system information does not comprise any HRNN associated with the respective NPN, a "no name" indicator. The method further comprises associating the name information of the second system information with the corresponding NPN element of the first system information. The association is based on an ithNPN element corresponding to an ithHRNN element. The method further comprises using an HRNN corresponding to one of the NPN elements to identify a respective NPN associated with the one of the NPN elements.

[0175] According to certain embodiments, a network node includes power supply circuitry and processing circuitry. The power supply circuitry is configured to supply power to the network node. The processing circuitry, which is configured to transmit first system information, and transmit second system information. The first system information includes a plurality of non-public network (NPN) elements that identify a plurality of NPNs. The second system information includes a plurality of human-readable network name (HRNN) elements, each HRNN element corresponding to a respective NPN element of the first system information, such that an ithNPN element corresponds to an ithHRNN element. Each HRNN element indicates name information. The name information includes an HRNN associated with the respective NPN or, if the second system information does not include any HRNN associated with the respective NPN, a "no name" indicator. The processing circuitry is further configured to use the HRNN corresponding to one of the NPN elements to identify a respective NPN associated with the one of the NPN elements.

[0176] According to certain embodiments, a method in a network node includes transmitting first system information, and transmitting second system information. The first system information includes a plurality of non-public network (NPN) elements that identify a plurality of NPNs. The second system information includes a plurality of human-readable network name (HRNN) elements, each HRNN element corresponding to a respective NPN element of the first system information, such that an ithNPN element corresponds to an ithHRNN element. Each HRNN element indicates name information. The name information includes an HRNN associated with the respective NPN or, if the second system information does not include any HRNN associated with the respective NPN, a "no name" indicator. The method further includes using the HRNN corresponding to one of the NPN elements to identify a respective NPN associated with the one of the NPN elements.

[0177] According to certain embodiments, a wireless device comprises power supply circuitry configured to supply power to the wireless device, and processing circuitry configured to detect system information broadcast from a network node. The system information comprises a list of non-public network (NPN) identifiers. The processing circuitry is further configured to generate a network index based on the system information. The network index comprises at least an NPN index. To generate the network index, the processing circuitry is further configured to identify whether the list of NPN identifiers comprises at least one element comprising at least one closed access group (CAG) identifier, and when the list of NPN identifiers comprises at least one element comprising at least one CAG identifier, generate a CAG index to be included as at least part of the NPN index. The CAG index is based at least in part on a number of public land mobile network (PLMN) elements included on the list of NPN identifiers in combination with the at least one CAG identifier. To generate the network index, the processing circuitry is also configured to identify whether the list of NPN identifiers comprises at least one element comprising at least one network identifier (NID), and when the list of NPN identifiers comprises at least one element comprising at least one NID, generate a NID index to be included as at least part of the NPN index. The NID index is based at least in part on a number of NIDs included in the list of NIDs.

[0178] According to certain embodiments, a wireless device comprises power supply circuitry configured to supply power to the wireless device, and processing circuitry configured to detect a first system information broadcast. The first system information broadcast comprises a non-public network (NPN) list. The NPN list indicates a plurality of NPN identifiers, each NPN identifier associated with a respective network of a plurality of networks. The processing circuitry is further configured to detect a second system information broadcast. The second system information broadcast comprises a human-readable network name (HRNN) list. The HRNN list indicates a plurality of HRNNs. The processing circuitry is further configured to associate each HRNN of the second system information broadcast with a corresponding NPN identifier of the first system information broadcast, and use an HRNN corresponding to one of the NPN identifiers to identify a respective network associated with the one of the NPN identifiers.

[0179] According to certain embodiments, a wireless device comprises power supply circuitry configured to supply power to the wireless device, and processing circuitry configured to determine whether a parameter received from a network node indicates that a cell is a non-public network (NPN) only cell, and select a network identity. When the parameter indicates that the cell is NPN only, the network identity is selected from a list of NPNs, and when the parameter indicates that the cell is not NPN only, the network identity is selected from a list of public land mobile networks (PLMNs).

[0180] According to certain embodiments, a wireless device comprises power supply circuitry configured to supply power to the wireless device; and processing circuitry configured to read a first element from a list of public land mobile networks, and in response to detecting the first element as indicating that no normal service is available, select a network identity from a list of non-public networks (NPNs). The method further comprises using the network identity to verify system information already stored by the wireless device.

[0181] According to certain embodiments, a network node comprises processing circuitry configured to generate a network index associated with system information broadcast by the network node. The system information comprises a list of non-public network (NPN) identifiers. The network index comprises at least a NPN index. Generating the network index comprises identifying whether the list of NPN identifiers comprises at least one element comprising at least one closed access group (CAG) identifier, and when the list of NPN identifiers comprises the at least one element comprising at least one CAG identifier, generating a CAG index to be included as at least part of the NPN index. The CAG index is based at least in part on a number of public land mobile network (PLMN) elements included on the list of NPN identifiers in combination with at least one CAG identifier. Generating the network index further comprises identifying whether the list of NPN identifiers comprises at least one element comprising at least one network identifier (NID), and when the list of NPN identifiers comprises the at least one element comprising at least one NID, generating a NID index to be included as at least part of the NPN index. The NID index is based at least in part on a number of NIDs included in the list of NIDs. According to certain embodiments, the network node further comprises power supply circuitry configured to supply power to the network node.

[0182] According to certain embodiments, a network node includes processing circuitry configured to transmit a first system information broadcast. The first system information broadcast includes a non-public network (NPN) list. The NPN list indicates a plurality of NPN identifiers. Each NPN identifier is associated with a respective network of a plurality of networks. The processing circuitry is further configured to prepare a second system information broadcast. The second system information broadcast includes a human-readable network name (HRNN) list. The HRNN list indicates a plurality of HRNNs. The second system information broadcast is configured to enable a wireless device to associate each HRNN of the second system information broadcast with a corresponding NPN identifier of the first system information broadcast. The processing circuitry is further configured to transmit the second system information broadcast. In some embodiments, the processing circuitry is further configured to identify a respective network associated with one of the NPN identifiers using an HRNN corresponding to the one of the NPN identifiers. According to certain embodiments, the network node further includes power supply circuitry configured to supply power to the network node.

[0183] According to certain embodiments, a network node includes processing circuitry configured to transmit a parameter to a wireless device. The parameter indicates that a cell is a non-public network (NPN) only cell. The processing circuitry is further configured to receive a selection of a network identity from the wireless device, wherein the network identity is selected from a non-public network (NPN) list when the parameter indicates that the cell is NPN only, and the network identity is selected from a public land mobile network (PLMN) list when the parameter indicates that the cell is not NPN only. According to certain embodiments, the network node further includes power supply circuitry configured to supply power to the network node.

[0184] According to certain embodiments, a network node includes processing circuitry configured to transmit a first element of a public land mobile network (PLMN) list to a wireless device, the first element of the PLMN list indicating that no normal service is available, thereby indicating that the wireless device is to select a network identity from a non-public network (NPN) list and use the network identity to validate system information already stored by the wireless device. According to certain embodiments, the network node further includes power supply circuitry configured to supply power to the network node.

[0185] According to certain embodiments, a method in a wireless device includes detecting a system information broadcast from a network node. The system information includes a list of non-public network (NPN) identifiers. The method further includes generating a network index based on the system information. The network index includes at least an NPN index. Generating the network index includes identifying whether the list of NPN identifiers includes at least one element that includes at least one closed access group (CAG) identifier, and when the list of NPN identifiers includes at least one element that includes at least one CAG identifier, generating a CAG index to be included as at least part of the NPN index. The CAG index is based at least in part on a number of public land mobile network (PLMN) elements that are included on the list of NPN identifiers in combination with the at least one CAG identifier. Generating the network index also includes identifying whether the list of NPN identifiers includes at least one element that includes at least one network identifier (NID), and when the list of NPN identifiers includes at least one element that includes at least one NID, generating a NID index to be included as at least part of the NPN index. The NID index is based at least in part on a number of NIDs included in the list of NIDs.

[0186] According to certain embodiments, a method in a wireless network includes detecting a first system information broadcast. The first system information broadcast includes a non-public network (NPN) list. The NPN list indicates a plurality of NPN identifiers, each NPN identifier associated with a respective network of a plurality of networks. The method further includes detecting a second system information broadcast. The second system information broadcast includes a human-readable network name (HRNN) list. The HRNN list indicates a plurality of HRNNs. The method further includes associating each HRNN of the second system information broadcast with a corresponding NPN identifier of the first system information broadcast, and using an HRNN corresponding to one of the NPN identifiers to identify a respective network associated with the one of the NPN identifiers.

[0187] According to certain embodiments, a method in a wireless device includes determining whether a parameter received from a network node indicates that a cell is a non-public network (NPN) only cell, and selecting a network identity. When the parameter indicates that the cell is NPN only, the network identity is selected from a NPN list, and when the parameter indicates that the cell is not NPN only, the network identity is selected from a public land mobile network (PLMN) list.

[0188] According to certain embodiments, a method in a wireless device includes reading a first element from a public land mobile network list and, in response to detecting the first element as indicating that no normal service is available, selecting a network identity from a non-public network (NPN) list. The method further includes using the network identity to verify system information already stored by the wireless device.

[0189] According to certain embodiments, a method in a network node includes generating a network index associated with system information broadcast by the network node. The system information includes a list of non-public network (NPN) identifiers. The network index includes at least an NPN index. Generating the network index includes identifying whether the list of NPN identifiers includes at least one element that includes at least one closed access group (CAG) identifier, and when the list of NPN identifiers includes at least one element that includes at least one CAG identifier, generating a CAG index to be included as at least part of the NPN index. The CAG index is based at least in part on a number of public land mobile network (PLMN) elements that are included on the list of NPN identifiers in combination with at least one CAG identifier. Generating the network index further includes identifying whether the list of NPN identifiers includes at least one element that includes at least one network identifier (NID), and when the list of NPN identifiers includes at least one element that includes at least one NID, generating a NID index to be included as at least part of the NPN index. The NID index is based at least in part on a number of NIDs included in the list of NIDs.

[0190] According to certain embodiments, a method in a network node includes transmitting a first system information broadcast. The first system information broadcast includes a non-public network (NPN) list. The NPN list indicates a plurality of NPN identifiers. Each NPN identifier is associated with a respective network of a plurality of networks. The method further includes preparing a second system information broadcast. The second system information broadcast includes a human-readable network name (HRNN) list. The HRNN list indicates a plurality of HRNNs. The second system information broadcast is configured to enable a wireless device to associate each HRNN of the second system information broadcast with a corresponding NPN identifier of the first system information broadcast. The method further includes transmitting the second system information broadcast. In some embodiments, the method further includes using an HRNN corresponding to one of the NPN identifiers to identify a respective network associated with the one of the NPN identifiers.

[0191] According to some embodiments, a method in a network node comprises transmitting a parameter to a wireless device. The parameter indicates that a cell is a non-public network (NPN) only cell. The method further comprises receiving a selection of a network identity from the wireless device, wherein the network identity is selected from a list of NPNs when the parameter indicates that the cell is NPN only, and the network identity is selected from a list of public land mobile networks (PLMNs) when the parameter indicates that the cell is not NPN only.

[0192] According to some embodiments, a method in a network node comprises transmitting a first element of a list of public land mobile networks (PLMNs) to a wireless device, the first element of the list of PLMNs indicating that no normal service is available, thereby indicating that the wireless device is to select a network identity from a list of non-public networks (NPNs) and use the network identity to verify system information already stored by the wireless device.

[0193] According to some embodiments, a computer program comprises instructions which, when executed on a computer, perform any of the steps of any of the methods described above.

[0194] According to some embodiments, a computer program product comprises a computer program. The computer program comprises instructions which, when executed on a computer, perform any of the steps of any of the methods described above.

[0195] According to some embodiments, a non-transitory computer-readable storage medium or carrier comprises a computer program. The computer program comprises instructions which, when executed on a computer, perform any of the steps of any of the methods described above.

[0196] Certain embodiments can provide one or more of the following (one or more) technical advantages. For example, the present disclosure provides a simple way of generating an index of network identities that spans both NPN and PLMN identity lists. One of the main advantages of this aspect is that it is a solution that is compatible with other parts of the standard and does not force new implementations of generic messages, such as, for example, the setupcomplete message. Another advantage of the present disclosure is that it provides a simple solution for how the HRNN should be broadcasted and how it should be connected to the NPN list broadcasted as in SIB1. BRIEF DESCRIPTION OF DRAWINGS

[0197] For a more complete understanding of the disclosed embodiments and their features and advantages, reference is now made to the following description, taken in conjunction with the accompanying drawings, in which:

[0198] Figure 1 An example of a message flow for radio resource control (RRC) setup is shown;

[0199] Figure 2An example illustrating a method according to some embodiments is shown;

[0200] Figure 3 An example illustrating a wireless network according to some embodiments is shown;

[0201] Figure 4 An example illustrating a user equipment according to some embodiments is shown;

[0202] Figure 5 An example illustrating a virtualization environment according to some embodiments is shown;

[0203] Figure 6 An example illustrating a telecommunication network connected via an intermediate network to a host computer according to some embodiments is shown;

[0204] Figure 7 An example illustrating a host computer communicating via a base station with a user equipment over a partially wireless connection according to some embodiments is shown;

[0205] Figure 8 An example illustrating a method implemented in a communication system including a host computer, a base station, and a user equipment according to some embodiments is shown;

[0206] Figure 9 An example illustrating a method implemented in a communication system including a host computer, a base station, and a user equipment according to some embodiments is shown;

[0207] Figure 10 An example illustrating a method implemented in a communication system including a host computer, a base station, and a user equipment according to some embodiments is shown;

[0208] Figure 11 An example illustrating a method implemented in a communication system including a host computer, a base station, and a user equipment according to some embodiments is shown;

[0209] Figure 12 An example illustrating a method according to some embodiments is shown;

[0210] Figure 13 An example illustrating a method according to some embodiments is shown;

[0211] Figure 14 An example illustrating a virtualization device according to some embodiments is shown;

[0212] Figure 15A and Figure 15B An example illustrating a method according to some embodiments is shown;

[0213] Figure 16 An example illustrating a network index according to some embodiments is shown;

[0214] Figure 17 An example of a method according to some embodiments is shown;

[0215] Figure 18 An example of a method according to some embodiments is shown;

[0216] Figure 19 An example of a method according to some embodiments is shown;

[0217] Figure 20 An example of a method according to some embodiments is shown;

[0218] Figure 21 An example of a method according to some embodiments is shown;

[0219] Figure 22 An example of a method according to some embodiments is shown;

[0220] Figure 23 An example of a method according to some embodiments is shown; and

[0221] Figure 24 An example of a method according to some embodiments is shown. DETAILED DESCRIPTION

[0222] Some embodiments of the embodiments anticipated herein will now be described in greater detail with reference to the drawings. Other embodiments, however, are included within the scope of the subject matter disclosed herein, which is not to be limited to the embodiments presented herein as being exemplary. These embodiments are presented by way of example only, and are not intended to exhaust the scope of the subject matter.

[0223] Generally, all terms used herein are to be interpreted according to their ordinary meaning in the technical field of the present disclosure, unless a different meaning is clearly given and / or is implied by the context of their use. All references to a / an / the item, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one and only one instance of whatever is being referred to unless otherwise indicated. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless explicitly stated otherwise. Any of the embodiments of the disclosed embodiments can be appropriate as long as the technical features of the method are retained. Likewise, any advantages of any of the embodiments of the embodiments can be applied to any of the other embodiments, and vice versa. Other objectives, features and advantages of the disclosed embodiments will be apparent from the following description.

[0224] CAG identifier related to the same PLMN

[0225] In one aspect of the disclosure, a solution is provided how to generate a network index by more than one network list. The network lists are in one embodiment a list of PLMNs and a list of NPNs.

[0226] The list of NPNs can be further split into the following lists:

[0227] PLMN + CAG ID; and

[0228] PLMN + Network ID (also referred to as “NID”).

[0229] Depending on the context, the notation “PLMN” sometimes denotes the identifier PLMN ID (consisting of a mobile country code (MCC) and a mobile network code (MNC)), and the notation “PLMN” sometimes denotes the public network identified by the PLMN ID. To clarify when the ID part is denoted, the PLMN ID can sometimes be denoted by the “MCC, MNC” notation. It should be understood that the “MCC, MNC” notation denotes the same as the PLMN ID.

[0230] When generating a network index for various network types, some rules are needed about what information is to be indicated by the index and how that information is to be indicated. For example, in case of an operator operating a PLMN denoted by a PLMN ID, one such rule should clarify whether a CAG ID broadcasted together with that PLMN ID can have the same network index as another CAG ID broadcasted together with the same PLMN ID.

[0231] The proposed structure of the element containing the CAG ID indicates that if several CAG IDs are served using the same PLMN ID, they can be collected. This aspect is shown below:

[0232] NPN-Identity information element

[0233] -- ASN1START

[0234] -- TAG-NPN-IDENTITY-START

[0235] NPN-Identity-r16 ::= CHOICE {

[0236] pni-npn-r16 SEQUENCE {

[0237] plmn-Identity-r16 PLMN-Identity,

[0238] cag-IdentityList-r16 SEQUENCE (SIZE (1..maxNPN-r16)) OF CAG-Identity-r16

[0239] },

[0240] snpn-r16 SEQUENCE {

[0241] plmn-Identity PLMN-Identity,

[0242] nid-List-r16 SEQUENCE (SIZE (1..maxNPN-r16)) OF NID-r16

[0243] }

[0244] }

[0245] CAG-Identity-r16 ::= BITSTRING (SIZE (32))

[0246] NID-r16 ::= BIT STRING (SIZE (52))

[0247] -- TAG-NPN-IDENTITY-STOP

[0248] -- ASN1STOP

[0249] Thus, it is possible to collect CAG IDs in one NPN-Identity element, or to create several NPN-Identity elements and assign different CAG IDs to each element, but it is possible to repeat the same plmn-Identity for elements. Both are possible. In case CAG IDs of the same PLMN ID are broadcasted in different NPN-Identity elements, it would be possible to assign them different cellIdentities by listing them in different NPN-IdentityInfo elements, see below.

[0250] NPN-IdentityInfoList information element

[0251] -- ASN1START

[0252] -- TAG-NPN-IDENTITYINFOLIST-START

[0253] NPN-IdentityInfoList-r16 ::= SEQUENCE (SIZE (1..maxNPN-r16)) OF NPN-IdentityInfo-r16

[0254] NPN-IdentityInfo-r16 ::= SEQUENCE {

[0255] NPN-IdentityList-r16 SEQUENCE (SIZE (1..maxNPN-r16)) OF NPN-Identity-r16,

[0256] trackingAreaCode-r16 TrackingAreaCode,

[0257] ranac-r16 RAN-AreaCode OPTIONAL, -- Need R

[0258] CellIdentity-r16 CellIdentity,

[0259] cellReservedForOperatorUse-r16 ENUMERATED {reserved, notReserved}, ...

[0260] }

[0261] -- TAG-NPN-IDENTITYINFOLIST-STOP

[0262] -- ASN1STOP

[0263] In the case where an operator wants to handle a CAG ID that is different from the other CAG IDs broadcast by the operator, certain embodiments create an NPN-Identity element with only that particular CAG. This element, if listed as a single element in the NPN-IdentityList, can then be provided with a unique tracking area code, a unique RANAC and a unique CellIdentity value, and since it is getting a unique network index, even independent Unified Access Control parameters UAC.

[0264] By recognizing this, the problem associated with defining the index comes from the fact that the index definition needs to be handled differently depending on whether the NPN-Identity element (defined above) contains a CAG or whether the NPN-Identity contains an NID. Similarly, the problem associated with generating the index (e.g. in the case of a UE) comes from the fact that the index generation needs to be handled differently depending on whether the NPN-Identity element contains a CAG or an NID.

[0265] One of the main reasons for this aspect is that it can be desirable not to create index values for different CAGs within the same NPN-Identity element (i.e. within the same list). According to one aspect of the present disclosure, all CAGs listed within the same NPN-Identity will be defined to have the same network index value, and rules are provided on how a UE should generate an index value for a certain network type.

[0266] Definition of NPN-IdentityInfoList and plmn-IdentityList.

[0267]

[0268] The network index is mainly used to inform the network side (access node, e.g. gNB) about what network the user / UE intends to access. The network index is also used by the network to represent the unified access control parameters (e.g. limit factor and limit time) per network level (as indicated as UAC-BarringPerPLMN as shown below).

[0269] For a PLMN, the UE needs to signal about the selected network to the RAN at connection setup (setup complete) so that the RAN can select the correct AMF. This is done by indicating the index, see below:

[0270] RRCSetupComplete-IEs ::= SEQUENCE{

[0271] selectedPLMN-Identity INTEGER (1..maxPLMN),

[0272] registeredAMF RegisteredAMF OPTIONAL,

[0273] guami-Type ENUMERATED {native, mapped} OPTIONAL,

[0274] s-NSSAI-List SEQUENCE (SIZE (1..maxNrofS-NSSAI)) OF S-NSSAIOPTIONAL,

[0275] dedicatedNAS-Message DedicatedNAS-Message,

[0276] ng-5G-S-TMSI-Value CHOICE {

[0277] ng-5G-S-TMSI NG-5G-S-TMSI,

[0278] ng-5G-S-TMSI-Part2 BIT STRING (SIZE (9))

[0279] } OPTIONAL,

[0280] lateNonCriticalExtension OCTET STRING OPTIONAL,

[0281] nonCriticalExtension SEQUENCE{} OPTIONAL

[0282] }

[0283] Similarly, for Unified Access Control (UAC), the PLMN index is used to signal specific restriction parameters for UAC.

[0284] UAC-BarringPerPLMN-List ::= SEQUENCE (SIZE (1..maxPLMN)) OF UAC-BarringPerPLMN

[0285] UAC-BarringPerPLMN ::= SEQUENCE {

[0286] plmn-IdentityIndex INTEGER (1..maxPLMN),

[0287] uac-ACBarringListType CHOICE{

[0288] uac-ImplicitACBarringList SEQUENCE (SIZE(maxAccessCat-1)) OFUAC-BarringInfoSetIndex,

[0289] uac-ExplicitACBarringList UAC-BarringPerCatList

[0290] } OPTIONAL -- Need S

[0291] }

[0292] The index is not explicitly contained in SIB1 but is generated by the UE from the SIB1 broadcast using the rules as contained in TS 38.331 stated above, i.e.:

[0293] For the PLMN contained in the n-th entry of the PLMN-IdentityInfoList and the i-th entry of its corresponding PLMN-IdentityInfo, the PLMN index is defined as b1 + b2 +... + b(n-1) + i, where b(j) is the number of PLMN-Identity entries in each PLMN-IdentityInfo, respectively.

[0294] Since the framework and functionality related to plmn-IdentityIndex and selectedPLMN-Identity is all in place, it would be preferred if it could be reused as much as possible. This embodiment proposes to build the plmn-IdentityIndex also for NPNs in order to avoid changes beyond the broadcast information in SIB1. Thus, according to the present disclosure, for indexing NPNs, the NPN index should be possible to use in exactly the same way as using the PLMN index.

[0295] An important aspect of the index is that it should point to a specific PLMN or network (PNINPN represented by CAG or SNPN). Thus, the index must be made such that it needs to be stepped when the PLMN can change. It is currently proposed that the PLMN is contained in the NPN Identity element and thus the NPN-Identity needs to be the basis for stepping the index. Thus, the index needs to be based on an element that can change PLMN, such as NPN-Identity.

[0296] With the proposed NPN list and structure of the NPN-IdentityInfoList, one way to describe and generate the index is to split it into three parts:

[0297] PLMN-index (as defined)

[0298] CAG-index - PIN-NIN w CAG index (see below)

[0299] NID-index - SNPN / NID index

[0300] Certain embodiments use this separation to control when to step the index. For example, the list of CAG indices in the same cag-IdentityList shall not step the index, while the NIDs in the nid-List shall step the index.

[0301] In this context, for the shared scenario, it is required that the list of cag-IdentityList and nid-IdentityList are not mixed. One possible way to proceed is to always broadcast the PLMNs with the lowest indices, then the CAGs, then the NIDs. The order of indices from low to high should be PLMN - CAG / PNI-NPN - NID / SNPN.

[0302] According to one aspect of the present disclosure, the CAG-index is defined as:

[0303] PLMN-index + x for the CAG ID in the xth cag-IdentityList (in order). Thus, all CAG IDs within the same cag-IdentityList shall have the same CAG-index.

[0304] The NID-index is defined as:

[0305] PLMN-index + CAG index + N1-N2+…+N(n-1) + p for the NID in position p in the nth nid-List, where N(s) are the number of NIDs in each nid-List, respectively.

[0306] Using the above index definitions, all NIDs will have independent indices, and all CAGs gathered in the same cag-IdentityList will have the same index. Thus, the CAG-index and NID index are generated at the UE and in the network such that:

[0307] CAG index = PLMN-index + x for the xth cag-IdentityList, and NID index = PLMN-index + CAG-index + N1-N2+…+N(n-1) + p for the NID in position p in the nth nid-List, where N(s) are the number of NIDs in each nid-List, respectively.

[0308] The above described can be expressed in other ways, such as with reference to the structure of the signaling, where it can be referred to that:

[0309] NPN-IdentityInfoList

[0310] NPN-IdentityInfo

[0311] NPN-IdentityList

[0312] NPN Identity

[0313] PLMN-Identity and cag or NID list

[0314] For the sake of brevity, the above description omits the steps between NPN-IdentityInfoList and the CAG / NID elements in the cag-Identity list or NID list, as they would cause a more complex expression.

[0315] It is of course also possible to refer to that a certain CAG ID is contained in what identityLists and Identity Info elements, but as long as there is a well-defined order, this does not change the index value.

[0316] Another aspect related to the index definition is when the parameter cellReservedForOtherUse is set to true. This means that there is no element in the PLMN list that can be accessed (the networks in the PLMN list will be restricted).

[0317] This actually means that the complete PLMN-list is disabled (restricted for all UEs) and then it makes sense that the plmn-IdentityIndex count is completely absent, i.e. the PLMN index value should be zero when signaling the NPN. Therefore, some embodiments include the following additional condition when generating the index for CAG or NID: When cellReservedForOtherUse is set to true, the generation of the NPN-index (CAG index, NID index) should count the PLMN-index part to zero.

[0318] An illustration of the different steps in the generation of the index value in the UE is shown in Figure 2 .

[0319] In a first step 20, the UE reads SIB1 and first detects whether cellReservedForOtherUse is set to "true" or "false". If it is set to "true", the UE shall jump to step 26. If it is set to "false", the UE shall generate an index of the PLMNs listed in the PLMN Identity list as defined (PLMN-index shown in step 24) and then shall continue to step 26. In the next step 26, it shall be checked whether an NPN-Identity list is present in the broadcast. If the NPN-Identity list is not present, the UE shall jump to step 36. If the NPN-Identity list is present, it shall be checked whether the list includes CAG IDs (step 28). If the list does not include any CAG ID, the UE jumps to step 32. If the list includes one or more CAG IDs, the UE performs step 30 to generate a set of indices for the CAG IDs as listed above and then continues to step 32. As next step 32, a check is made to see whether there are NIDs present in the NPN-IdentityList. If there are no NIDs present in the NPN-IdentityList, the procedure jumps to step 36. If there is one or more NIDs present in the NPN-IdentityList, the UE performs step 34 (generating NID indices as described above) and then continues to step 36. In step 36, the method ends with the UE transmitting the calculated indices, which indicate the network identity of the network the UE intends to access and establish an RRC connection.

[0320] Even though the above description is for a UE, the generation of indices according to the same procedure is actually a network task, as it needs to be combined with the determination whether or when a network shall be configured to broadcast PLMNs or network specific UAC parameters.

[0321] After the procedure described above, the next step of the UE, e.g. in a situation where an attempt to access a network is ongoing, the UE shall format the RRCSetupComplete message, which includes the index indication corresponding to the network the UE / user intends to access.

[0322] In another aspect of the disclosure, there is a need to support broadcast of all CAG broadcast and SNPN (MCC, MNC, NID combination) human readable network name (HRNN). Thus, it is possible to broadcast readable names for CAG cells and SNPN cells.

[0323] According to one aspect of the present disclosure, instead of using the index created in the previous step, a new SIB (SIBx) is used for the HRNN broadcast, the new SIB including as many elements as the number of CAGs and NIDs contained in the SIB1 broadcast. If there are networks that should not have a HRNN, then the element is included anyway, but the content of this element is set to "empty" or "no name" or some other indication that indicates that some networks do not actually broadcast a human readable network name. This parameter can also just be a "false" indication.

[0324] According to one aspect of the present disclosure, advantages are recognized in including as many elements as there are CAG IDs and NIDs. Alternative ways of using an index, e.g. as generated by the UE or the network and as described above, would not allow the possibility to list the HRNNs of CAGs that are part of the same CAG list, as these CAGs can then have the same network index. Thus, a solution that uses an index would need to consider an index that is stepped over all CAGs and all NIDs. However, the challenge is that CAGs in the same list should not have the index stepped over, and then it cannot be used directly to associate with the HRNN. If it would be possible to reuse the index for UAC and msg5 (as described above), it would be advantageous. However, as this would not allow different HRNNs of CAGs that are harvested under the same Cag-IdentityList element, another index would be needed. An alternative solution (and perhaps the most straightforward solution) would be to create a separate index that is stepped over all CAGs and NIDs, and to associate this index with the HRNN list. According to another embodiment of the present disclosure, the alternative would thus be to create a second index, CAG-NID-index, and to associate this index with the HRNNs in the HRNN broadcast. This is considered to be the alternative to the case where the new SIB for HRNN would have the same number of HRNN elements as the number of CAGs and NIDs in SIB1, where the elements can also be empty.

[0325] An example of HRNN according to one embodiment of the present disclosure is provided below:

[0326] SIBx

[0327] IE SIBx contains the Human Readable Network Name (HRNN)

[0328] SIBx information element

[0329] -- ASN1START

[0330] -- TAG-SIBx-START

[0331] SIBx ::= SEQUENCE {

[0332] hrnn-List SEQUENCE (SIZE (1..maxNPN-r16) OF HRNN ...

[0333] }

[0334] HRNN ::= CHOICE {

[0335] hrnn OCTET STRING (size (1..48)),

[0336] noHRNN ENUMERATED {true}

[0337] }

[0338] -- TAG-SIBx-STOP

[0339] -- ASN1STOP

[0340]

[0341] With respect to when the UE is reading system information and in particular when it is acquiring SIB1 information to enable the UE to reuse stored system information, SIBs in NR (other than SIB1, SIB6, SIB7 or SIB8) are associated with a value tag. If a stored SIB was acquired less than 3 hours ago and the value tag matches the one provided for that SIB in SIB1, it is considered valid. A SIB can also be associated with a validity area tag to allow the same SIB to be reused in more than one cell - in this case the area id must also match the one in SIB1 for the stored SIB to be considered valid.

[0342] When verifying the value tag, the UE must also check that the PLMN ID and optionally (depending on whether the SIB is cell specific or not) the Cell ID of the stored SIB matches the PLMN ID and Cell ID broadcast in SIB1. But comparing the PLMN ID has a slight problem as there can be multiple PLMN IDs associated with the cell due to RAN sharing. In Rel-15 this is solved by comparing using the first PLMN ID broadcast in SIB1.

[0343]

[0344] The first PLMN ID can potentially cause problems for the fact that only NPN cells in SI verification. Since it has been agreed to provide NPN in the standalone network list, in case of "only npn cell", the PLMN list value can just be a "dummy value" for the purpose of SI validity without relying on. Further, and especially for SNPN, just having the PLMN part can not be enough, as that can not be unique, especially not when using MCC=999 when not using the operator PLMN. For SNPN, actually also the NID is needed.

[0345] For the above purpose and in accordance with another aspect of the present disclosure, it is proposed that if cellReservedForOperatorUse is set to "false", the UE shall verify as described above. If cellReservedForOperatorUse is set to "true" (only npn), the first network element in NPN-IdentityInfoList shall be used. If this element is a SNPN element, it shall also include the NID part.

[0346] In another aspect of the present disclosure, if the "PLMN Dummy value" is a standardized value used for basically having a non-empty PLMN list, the UE can well recognize that the first element of the NPN list shall be taken instead by detecting the dummy value. Then it would not be necessary to detect or read the cellReservedForOtherUse value. Thus, in accordance with one aspect of the present disclosure, when cellReservedForOtherUse is set to true, the UE shall use the first network identity (PLMN, SNPN) in NPN-IdentityInfoList instead of PLMN-IdentityInfoList. If the first network identity is a SNPN identity, both PLMN and NID shall be used when verifying the stored SI.

[0347] The following shows the changes made to the 3GPP TS 38.331 specification.

[0348] 5.2.2.2.1 SIB validity

[0349] The UE shall apply the system information (SI) acquisition procedure as defined in clause 5.2.2.3 at cell selection (e.g. at power on), cell reselection, upon returning from out-of-coverage, after reconfiguration with sync completion, after entering the network from another RAT, upon receiving an indication that system information has been changed, upon receiving a PWS notification, and whenever the UE does not have a stored valid version of a SIB.

[0350] When the UE acquires the MIB (Master Information Block) or SIB1 or SI message in a serving cell as described in clause 5.2.2.3 and if the UE stores the acquired SIB, the UE shall store the associated areaScope (if present), network identity (PLMN-Identity or PLMN-Identity + NID), CellIdentity, systemInformationAreaID (if present) and valueTag (if present) as indicated in si-SchedulingInfo of the SIB. The UE can use the valid stored version of the SI, except for MIB, SIB1, SIB6, SIB7 or SIB8, e.g. after cell reselection, upon returning from out of coverage or after receiving an SI change indication.

[0351] NOTE: The storage and management of stored SIBs other than the SIBs valid for the current serving cell is left to UE implementation.

[0352] The UE shall:

[0353] 1> if cellReservedForOtherUse is set to false:

[0354] 2> use the first PLMN-Identity in the PLMN-IdentityInfoList as network identity and the associated CellIdentity for SIB validity checking;

[0355] 2> else:

[0356] 2> if the first NPN-Identity in the NPN-IdentityInfoList is pni-npn:

[0357] 3> use the PLMN-Identity in the NPN-Identity as network identity and the associated CellIdentity for SIB validity checking;

[0358] 2> if the first NPN-Identity in the NPN-IdentityInfoList is snpn:

[0359] 3> use the PLMN-Identity and the first NID in the NPN-Identity as network identity and the associated CellIdentity for SIB validity checking;

[0360] 1> delete any stored version of a SIB after 3 hours from the time it was successfully confirmed to be valid;

[0361] 1> for each stored version of a SIB:

[0362] 2> if areaScope is associated and its value for the stored version of the SIB is the same as the received value in si-SchedulingInfo for that SIB from the serving cell:

[0363] 3> if the valueTag, systemInformationAreaID and network identity contained in si-SchedulingInfo for the SIB received from the serving cell are the same as the network identity, systemInformationAreaID and valueTag associated with the stored version of that SIB:

[0364] 4> consider the stored SIB valid for the cell;

[0365] 2> if areaScope is not present for the stored version of a SIB and the areaScope value is not contained in si-SchedulingInfo for that SIB from the serving cell:

[0366] 3> if the valueTag, CellIdentity and network identity contained in si-SchedulingInfo for the SIB received from the serving cell are the same as the network identity, CellIdentity and valueTag associated with the stored version of that SIB:

[0367] 4> consider the stored SIB valid for the cell;

[0368] Next modification subclause

[0369] The following paragraphs describe additional changes to the 3GPP TS 38.331 specification, starting with section 5.5.5.1 (“General”). This section of TS 38.331 includes “ Figure 5 .5.5.1-1: Measurement reporting”, which shows a UE sending a MeasurementReport message to the network. The purpose of this procedure is to transfer measurement results from the UE to the network. The UE shall only initiate this procedure after successful Access Stratum (AS) security activation.

[0370] For each measId for which the measurement reporting procedure is triggered, the UE shall set the measResults within the MeasurementReport message as follows:

[0371] 1> set measId to the measurement identity that triggered the measurement report;

[0372] 1> for each serving cell configured with servingCellMO:

[0373] 2> if the reportConfig associated with the measId that triggered the measurement report includes rsType:

[0374] 3> if serving cell measurements based on the rsType contained in the reportConfig that triggered the measurement report are available:

[0375] 4> set the measResultServingCell within measResultServingMOList to include the reference signal received power (RSRP), reference signal received quality (RSRQ) and available signal to interference plus noise ratio (SINR) of the serving cell based on the rsType contained in the reportConfig that triggered the measurement report;

[0376] 2> else:

[0377] 3> if serving cell measurements based on synchronization signal block (SSB) are available:

[0378] 4> set the measResultServingCell within measResultServingMOList to include the RSRP, RSRQ and available SINR of the serving cell based on SSB;

[0379] 3> else, if serving cell measurements based on channel state information reference signal (CSI-RS) are available:

[0380] 4> set the measResultServingCell within measResultServingMOList to include the RSRP, RSRQ and available SINR of the serving cell based on CSI-RS;

[0381] 1> set the servCellId within measResultServingMOList to include each NR serving cell configured with servingCellMO, if any;

[0382] 1> if the reportConfig associated with the measId that triggered the measurement report includes reportQuantityRS-Indexes and maxNrofRS-IndexesToReport:

[0383] 2> For each serving cell configured with a measObjectNR, include beam measurement information according to the associated reportConfig as specified in 5.5.5.2;

[0384] 1> If the reportConfig associated with the measId that triggered the measurement reporting includes reportAddNeighMeas:

[0385] 2> For each measObjectId referred to in the measIdList (which also takes a measObjectNR to refer to) other than the one corresponding to the measId that triggered the measurement reporting:

[0386] 3> If the measObjectNR indicated by the servingCellMO includes RS resource configuration corresponding to the rsType indicated in the reportConfig:

[0387] 4> Set the measResultBestNeighCell within the measResultServingMOList to include the physCellId and the available measurement quantities of reportQuantityCell and rsType indicated in the non-serving cell based reportConfig corresponding to the involved measObjectNR with the highest measured RSRP if RSRP measurement results are available for the cell corresponding to this measObjectNR, otherwise with the highest measured RSRQ if RSRQ measurement results are available for the cell corresponding to this measObjectNR, otherwise with the highest measured SINR;

[0388] 4> If the reportConfig associated with the measId that triggered the measurement reporting includes reportQuantityRS-Indexes and maxNrofRS-IndexesToReport:

[0389] 5> For each best non-serving cell included in the measurement reporting:

[0390] 6> Include beam measurement information according to the associated reportConfig as specified in 5.5.5.2;

[0391] 1> if the reportConfig associated with the measId that triggered the measurement report is set to eventTriggered and the eventID is set to eventA3 or eventA4 or eventA5 or eventB1 or eventB2:

[0392] 2> if the UE is in NE-DC and the measurement configuration that triggered this measurement report is associated with the MCG:

[0393] 3> set the measResultServFreqListEUTRA-SCG to include an entry for each E-UTRA SCG serving frequency with the following aspects:

[0394] 4> the carrierFreq of the E-UTRA serving frequency;

[0395] 4> set the measResultServingCell to include the available measurement quantities that the UE is configured to measure by the measurement configuration associated with the SCG;

[0396] 4> if the reportConfig associated with the measId that triggered the measurement report includes reportAddNeighMeas:

[0397] 5> set the measResultServFreqListEUTRA-SCG to include within the measResultBestNeighCell the quantities of the best non-serving cell based on RSRP on the concerned serving frequencies;

[0398] 1> if the reportConfig associated with the measId that triggered the measurement report is set to eventTriggered and the eventID is set to eventA3 or eventA4 or eventA5:

[0399] 2> if the UE is in NR-DC and the measurement configuration that triggered this measurement report is associated with the MCG:

[0400] 3> set the measResultServFreqListNR-SCG to include for each NR SCG serving cell configured with a servingCellMO, if any, the following aspects:

[0401] 4> if the reportConfig associated with the measId that triggered the measurement report includes rsType:

[0402] 5> if the serving cell measurements based on the rsType contained in the reportConfig triggering the measurement report are available according to the measurement configuration associated with the SCG, then:

[0403] 6> set the measResultServingCell within measResultServFreqListNR-SCG to include the RSRP, RSRQ and available SINR of the serving cell derived based on the rsType contained in the reportConfig triggering the measurement report;

[0404] 4> else:

[0405] 5> if the SSB based serving cell measurements are available according to the measurement configuration associated with the SCG, then:

[0406] 6> set the measResultServingCell within measResultServFreqListNR-SCG to include the RSRP, RSRQ and available SINR of the serving cell derived based on SSB;

[0407] 5> else, if the CSI-RS based serving cell measurements are available according to the measurement configuration associated with the SCG, then:

[0408] 6> set the measResultServingCell within measResultServFreqListNR-SCG to include the RSRP, RSRQ and available SINR of the serving cell derived based on CSI-RS;

[0409] 4> if the results for the serving cell derived based on SSB are included, then:

[0410] 5> include ssbFrequency to the value indicated by ssbFrequency contained in the MeasObjectNR for the serving cell;

[0411] 4> if the results for the serving cell derived based on CSI-RS are included, then:

[0412] 5> include refFreqCSI-RS to the value indicated by refFreqCSI-RS contained in the MeasObjectNR for the serving cell;

[0413] 4> if the reportConfig associated with the measId triggering the measurement report includes reportQuantityRS-Indexes and maxNrofRS-IndexesToReport, then:

[0414] 5> For each serving cell configured with servingCellMO, include beam measurement information according to the associated reportConfig as described in 5.5.5.2, where availability is considered according to the measurement configuration associated with the SCG;

[0415] 4> If the reportConfig associated with the measId that triggered the measurement report includes reportAddNeighMeas:

[0416] 5> If the measObjectNR indicated by the servingCellMO includes RS resource configuration corresponding to the rsType indicated in the reportConfig:

[0417] 6> Set the measResultBestNeighCellListNR within the measResultServFreqListNR-SCG to include one entry with physCellId and available measurement quantities of reportQuantityCell and rsType indicated in the non-serving cell based reportConfig corresponding to the involved measObjectNR with the highest measured RSRP if RSRP measurement results are available for the cell corresponding to this measObjectNR, or with the highest measured RSRQ if RSRQ measurement results are available for the cell corresponding to this measObjectNR, or with the highest measured SINR otherwise, where availability is considered according to the measurement configuration associated with the SCG;

[0418] 7> If the reportConfig associated with the measId that triggered the measurement report includes reportQuantityRS-Indexes and maxNrofRS-IndexesToReport:

[0419] 8> For each best non-serving cell included in the measurement report:

[0420] 9> Include beam measurement information according to the associated reportConfig as described in 5.5.5.2, where availability is considered according to the measurement configuration associated with the SCG;

[0421] 1> If there is at least one applicable neighbour cell to report:

[0422] 2> If the reportType is set to eventTriggered or periodic:

[0423] 3> set measResultNeighCells to include at most maxReportCells best neighbour cells according to:

[0424] 4> if reportType is set to eventTriggered:

[0425] 5> include the cells contained in cellsTriggeredList as defined in VarMeasReportList for this measId;

[0426] 4> else:

[0427] 5> include applicable cells for which new measurement results have become available since the last periodic reporting or since the measurement was initiated or reset;

[0428] 4> for each cell included in measResultNeighCells, include physCellId;

[0429] 4> if reportType is set to eventTriggered or periodic:

[0430] 5> for each included cell, include layer 3 filtered measurement results according to the reportConfig for this measId, ordered as follows:

[0431] 6> if the measObject associated with this measId concerns NR:

[0432] 7> if rsType in the associated reportConfig is set to ssb:

[0433] 8> set resultsSSB-Cell within measResult to include the synchronization signal (SS) / physical broadcast channel (PBCH) block based quantity(s) indicated in reportQuantityCell within the concerned reportConfig, determined as specified in 5.5.5.3 in descending order of the categorized quantities, i.e. the best cell is included first;

[0434] 8> if reportQuantityRS-Indexes and maxNrofRS-IndexesToReport are configured, include beam measurement information as specified in 5.5.5.2;

[0435] 7> else if rsType in the associated reportConfig is set to csi-rs:

[0436] 8> set resultsCSI-RS-Cell within measResult to include the CSI-RS based quantity(s) indicated in reportQuantityCell within the concerned reportConfig in descending order of ranked quantities as specified in 5.5.5.3, i.e. the best cell is included first;

[0437] 8> if reportQuantityRS-Indexes and maxNrofRS-IndexesToReport are configured, include beam measurement information as described in 5.5.5.2;

[0438] 6> if the measObject associated with this measId concerns E-UTRA:

[0439] 7> set measResult to include the quantity(s) indicated in reportQuantity within the concerned reportConfigInterRAT in descending order of ranked quantities as specified in 5.5.5.3, i.e. the best cell is included first;

[0440] 2> else:

[0441] 3> if the cell indicated by cellForWhichToReportCGI is an NR cell:

[0442] 4> if the plmn-IdentityInfoList of the cgi-Info of the concerned cell has been obtained:

[0443] 5> include the plmn-IdentityInfoList including plmn-IdentityList, trackingAreaCode if available, ranac if available, CellIdentity and cellReservedForOperatorUse for each entry of the plmn-IdentityInfoList;

[0444] 5> include frequencyBandList if available;

[0445] 4> if the UE is NPN capable and the NPN-IdentityInfoList of the cgi-Info of the concerned cell has been obtained:

[0446] 5> include NPN-IdentityInfoList which includes NPN-IdentityList, trackingAreaCode if available, ranac if available, CellIdentity and cellReservedForOperatorUse for each entry of NPN-IdentityInfoList;

[0447] 4> else if the MIB indicates that SIB1 is not broadcast:

[0448] 5> include noSIB1 which includes ssb-SubcarrierOffset and pdcch-ConfigSIB1 obtained from the MIB of the concerned cell (where "pdcch" means Physical Downlink Control Channel);

[0449] 3> if the cell indicated by cellForWhichToReportCGI is an E-UTRA cell:

[0450] 4> if all mandatory fields of cgi-Info-EPC of the concerned cell have been obtained:

[0451] 5> include in cgi-Info-EPC the fields broadcast in E-UTRA SystemInformationBlockType1 associated to EPC;

[0452] 4> if the UE is E-UTRA / 5GC capable and all mandatory fields of cgi-Info-5GC of the concerned cell have been obtained:

[0453] 5> include in cgi-Info-5GC the fields broadcast in E-UTRA SystemInformationBlockType1 associated to 5GC;

[0454] 4> if the mandatory present fields of cgi-Info of the cell indicated by cellForWhichToReportCGI in the associated measObject have been obtained:

[0455] 5> include freqBandIndicator;

[0456] 5> include multiBandInfoList if broadcast by the cell;

[0457] 5> include freqBandIndicatorPriority if broadcast by the cell;

[0458] 1> if the corresponding measObject concerns NR:

[0459] 2> if reportSFTD-Meas is set to TRUE within the corresponding reportConfigNR for this measId:

[0460] 3> set measResultSFTD-NR according to:

[0461] 4> set sfn-OffsetResult (where SFN denotes System Frame Number) and frameBoundaryOffsetResult to the results provided by lower layers;

[0462] 4> if reportRSRP is set to TRUE:

[0463] 5> set rsrp-Result to the RSRP of the NR PSCell (primary cell of the secondary cell group) derived based on SSB;

[0464] 2> else if reportSFTD-NeighMeas is included within the corresponding reportConfigNR for this measId:

[0465] 3> include an entry in measResultCellListSFTD-NR for each applicable cell for which measurement results are available, and set the content as follows:

[0466] 4> set physCellId to the physical cell identity of the concerned NR neighbour cell,

[0467] 4> set sfn-OffsetResult and frameBoundaryOffsetResult to the results provided by lower layers;

[0468] 4> if reportRSRP is set to TRUE:

[0469] 5> set rsrp-Result to the RSRP of the concerned cell derived based on SSB;

[0470] 1> else if the corresponding measObject concerns E-UTRA:

[0471] 2> if reportSFTD-Meas is set to TRUE within the corresponding reportConfigInterRAT for this measId:

[0472] 3> set measResultSFTD-EUTRA according to:

[0473] 4> set sfn-OffsetResult and frameBoundaryOffsetResult to the lower layer provided measurement results;

[0474] 4> if reportRSRP is set to TRUE:

[0475] 5> set rsrpResult-EUTRA to the RSRP of the EUTRA PSCell;

[0476] 1> increment numberOfReportsSent as defined within the VarMeasReportList for this measId by 1;

[0477] 1> if running, stop the periodic reporting timer;

[0478] 1> if numberOfReportsSent as defined within the VarMeasReportList for this measId is less than reportAmount as defined within the corresponding reportConfig for this measId:

[0479] 2> start the periodic reporting timer with the value of reportInterval as defined within the corresponding reportConfig for this measId;

[0480] 1> else:

[0481] 2> if reportType is set to periodic:

[0482] 3> remove the entry within the VarMeasReportList for this measId;

[0483] 3> remove this measId from the measIdList within the VarMeasConfig;

[0484] 1> if the UE is in (NG)EN-DC:

[0485] 2> if SRB3 is configured:

[0486] 3> submit the MeasurementReport message to lower layers for transmission via SRB3, at which point the procedure ends;

[0487] 2> else:

[0488] 3> submit the MeasurementReport message via the E-UTRA MCG embedded in the E-UTRA RRC message ULInformationTransferMRDC as specified in TS 36.331

[10] (where UL stands for Uplink, and MRDC stands for Multi-RAT Dual Connectivity).

[0489] 1> else if the UE is in NR-DC:

[0490] 2> if the measurement configuration that triggered this measurement report is associated with the SCG:

[0491] 3> if SRB3 is configured:

[0492] 4> submit the MeasurementReport message to lower layers for transmission via SRB3, at which point the procedure ends;

[0493] 3> else:

[0494] 4> submit the MeasurementReport message via the NR MCG embedded in the NR RRC message ULInformationTransferMRDC as specified in 5.7.2a.3;

[0495] 2> else:

[0496] 3> submit the MeasurementReport message to lower layers for transmission via SRB1, at which point the procedure ends;

[0497] 1> else:

[0498] 2> submit the MeasurementReport message to lower layers for transmission, at which point the procedure ends.

[0499] Next modification subclause

[0500] 6.2.2 Message definitions

[0501] […]

[0502] – RRCResumeComplete

[0503] RRCResumeComplete message is used to confirm successful completion of RRC connection resume.

[0504] Signaling Radio Bearer: SRB1

[0505] RLC-SAP: AM

[0506] Logical Channel: Dedicated Control Channel (DCCH)

[0507] Direction: UE to Network

[0508] RRCResumeComplete message

[0509] -- ASN1START

[0510] -- TAG-RRCRESUMECOMPLETE-START

[0511] RRCResumeComplete ::= SEQUENCE {

[0512] rrc-TransactionIdentifier RRC-TransactionIdentifier,

[0513] criticalExtensions CHOICE {

[0514] rrcResumeComplete RRCResumeComplete-IEs,

[0515] criticalExtensionsFuture SEQUENCE {}

[0516] }

[0517] }

[0518] RRCResumeComplete-IEs ::= SEQUENCE {

[0519] dedicatedNAS-Message DedicatedNAS-Message OPTIONAL,

[0520] selectedPLMN-Identity INTEGER (1..maxPLMN)

[0521] OPTIONAL,

[0522] uplinkTxDirectCurrentList UplinkTxDirectCurrentList OPTIONAL,

[0523] lateNonCriticalExtension OCTET STRING

[0524] OPTIONAL,

[0525] nonCriticalExtension SEQUENCE{} OPTIONAL

[0526] }

[0527] -- TAG-RRCRESUMECOMPLETE-STOP

[0528] -- ASN1STOP

[0529]

[0530] […]

[0531] Next modification subclause - changes to SIB3 and new SIBx

[0532] 6.3.1 System Information Block

[0533] […]

[0534] – SIB3

[0535] SIB3 contains neighbour cell related information relevant only for intra-frequency cell reselection. The IE includes cells with specific reselection parameters as well as cells that are blacklisted.

[0536] SIB3 information element

[0537] -- ASN1START

[0538] -- TAG-SIB3-START

[0539] SIB3 ::= SEQUENCE {

[0540] intraFreqNeighCellList IntraFreqNeighCellList OPTIONAL, -- Need R

[0541] intraFreqBlackCellList IntraFreqBlackCellList OPTIONAL, --Need R

[0542] lateNonCriticalExtension OCTET STRING OPTIONAL, ...

[0543] }

[0544] IntraFreqNeighCellList ::= SEQUENCE (SIZE (1..maxCellIntra)) OFIntraFreqNeighCellInfo

[0545] IntraFreqNeighCellInfo ::= SEQUENCE {

[0546] physCellId PhysCellId,

[0547] q-OffsetCell Q-OffsetRange,

[0548] q-RxLevMinOffsetCell INTEGER (1..8) OPTIONAL, -- Need R

[0549] q-RxLevMinOffsetCellSUL INTEGER (1..8) OPTIONAL, -- Need R

[0550] q-QualMinOffsetCell INTEGER (1..8) OPTIONAL, -- Need R ...

[0551] [[ cag-PCI-Range-r16 PCI-Range OPTIONAL -- Need R ]]

[0553] }

[0554] IntraFreqBlackCellList ::= SEQUENCE (SIZE (1..maxCellBlack)) OF PCI-Range

[0555] -- TAG-SIB3-STOP

[0556] -- ASN1STOP

[0557]

[0558] […]

[0559] SIBx

[0560] IE SIBx contains a human-readable network name (HRNN)

[0561] SIBx information element

[0562] -- ASN1START

[0563] -- TAG-SIBx-START

[0564] SIBx ::= SEQUENCE {

[0565] hrnn-List SEQUENCE (SIZE (1..maxNPN-r16) OF HRNN ...

[0566] }

[0567] HRNN ::= CHOICE {

[0568] hrnn OCTET STRING (size (1..48)),

[0569] noHRNN ENUMERATED {true}

[0570] }

[0571] -- TAG-SIBx-STOP

[0572] -- ASN1STOP

[0573]

[0574] Next modification subclause (based on CR from 108#37)

[0575] 6.3.2 Radio resource control information elements

[0576] […]

[0577] – CellAccessRelatedInfo

[0578] IE CellAccessRelatedInfo indicates the cell access related information of this cell.

[0579] CellAccessRelatedInfo information element

[0580] -- ASN1START

[0581] -- TAG-CELLACCESSRELATEDINFO-START

[0582] CellAccessRelatedInfo ::= SEQUENCE {

[0583] plmn-IdentityList PLMN-IdentityInfoList,

[0584] cellReservedForOtherUse ENUMERATED {true} OPTIONAL, --Need R ... [[

[0586] cellReservedForFutureUse-r16 ENUMERATED {true} OPTIONAL, -- NeedR

[0587] NPN-IdentityInfoList-r16 NPN-IdentityInfoList-r16 OPTIONAL --Need R ]]

[0589] }

[0590] -- TAG-CELLACCESSRELATEDINFO-STOP

[0591] -- ASN1STOP

[0592]

[0593]

[0594] […]

[0595] – CGI-InfoNR

[0596] IE CGI-InfoNR indicates the cell access related information reported by the UE as part of the reporting CGI procedure.

[0597] CGI-InfoNR information element

[0598] -- ASN1START

[0599] -- TAG-CGI-INFO-NR-START

[0600] CGI-InfoNR ::= SEQUENCE {

[0601] plmn-IdentityInfoList PLMN-IdentityInfoList OPTIONAL,

[0602] frequencyBandList MultiFrequencyBandListNR OPTIONAL,

[0603] noSIB1 SEQUENCE {

[0604] ssb-SubcarrierOffset INTEGER (0..15),

[0605] pdcch-ConfigSIB1 PDCCH-ConfigSIB1

[0606] } OPTIONAL, ...

[0607] [[ NPN-IdentityInfoList-r16 NPN-IdentityInfoList OPTIONAL ]]

[0609] }

[0610] -- TAG-CGI-INFO-NR-STOP

[0611] -- ASN1STOP

[0612]

[0613] […]

[0614] – UAC-BarringPerPLMN-List

[0615] IE UAC-BarringPerPLMN-List provides access class specific access control parameters, which are configured per PLMN.

[0616] UAC-BarringPerPLMN-List information element

[0617] -- ASN1START

[0618] -- TAG-UAC-BARRINGPERPLMN-LIST-START

[0619] UAC-BarringPerPLMN-List ::= SEQUENCE (SIZE (1..maxPLMN)) OF UAC-BarringPerPLMN

[0620] UAC-BarringPerPLMN ::= SEQUENCE {

[0621] plmn-IdentityIndex INTEGER (1..maxPLMN),

[0622] uac-ACBarringListType CHOICE{

[0623] uac-ImplicitACBarringList SEQUENCE (SIZE (maxAccessCat-1)) OF UAC-BarringInfoSetIndex,

[0624] uac-ExplicitACBarringList UAC-BarringPerCatList

[0625] } OPTIONAL -- Need S

[0626] }

[0627] -- TAG-UAC-BARRINGPERPLMN-LIST-STOP

[0628] -- ASN1STOP

[0629]

[0630] While the subject matter described herein can be implemented in any appropriate type of system using any suitable components, the embodiments disclosed herein are described in relation to example wireless networks, such as the example wireless network illustrated in Figure 1. For simplicity, the wireless network of Figure 1 only shows network 106, network nodes 160 and 160b, and WDs 110, 110b, and 110c. In practice, a wireless network can further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device (such as a landline telephone, a service provider, or any other network node or terminal device). Of the components shown, network node 160 and wireless device (WD) 110 are illustrated with additional specificity. A wireless network can provide communication and other types of services to one or more wireless devices to facilitate the wireless devices' access to and / or use of the services provided by, or via, the wireless network. Figure 3 Figure 3 wireless network only shows network 106, network nodes 160 and 160b, and WDs 110, 110b, and 110c. In practice, a wireless network can further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device (such as a landline telephone, a service provider, or any other network node or terminal device). Of the components shown, network node 160 and wireless device (WD) 110 are illustrated with additional specificity. A wireless network can provide communication and other types of services to one or more wireless devices to facilitate the wireless devices' access to and / or use of the services provided by, or via, the wireless network.​

[0631] The wireless network can comprise and / or interface with any type of network that is suitable to transmit and receive data, including, but not limited to a core network, a public switched telephone network (PSTN), the Internet, a local area network (LAN), a metropolitan area network (MAN), a wide area network (WAN) such as a wireless LAN (WLAN) or a metropolitan area network (MAN), a broadband network, and the like, or any combination thereof. In some embodiments, the wireless network can be configured to allow access to information on networks, such as the Internet, via, for example, laptops, personal computers (PCs), tablets, and the like. The wireless network can be configured to allow connection to a data network, such as a cellular or Wi-Fi network.

[0632] The network 106 can comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTNs), packet data networks, optical networks, wide-area networks (WANs), local-area networks (LANs), wireless local-area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.

[0633] The network node 160 and the WD 110 include various components described in greater detail below. These components work together to provide network node and / or wireless device functionality such as providing wireless connections in a wireless network. In different embodiments, the wireless network can comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and / or any other components or systems that can facilitate or participate in the communication of data and / or signals whether via wired or wireless connections.

[0634] As used herein, "network node" refers to a device, which can be, be configured as, be arranged to, and / or be operational to communicate with a wireless device and / or with other network nodes or devices in a wireless network, directly or indirectly, to enable and / or provide wireless access to the wireless device and / or to perform other functions of the wireless network, e.g., management. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs), and NR NodeBs (gNBs)). Base stations can be categorized based on the amount of their provided coverage (or in other words, their transmission power level) and can then also be called femto base stations, pico base stations, micro base stations, or macro base stations. Base stations can be stand-alone nodes or can be centralized in a base station controller (BSC) or radio base station controller. Network nodes can also include one or more (or all) parts of distributed radio base stations, such as centralized digital and / or remote radio units (RRUs), sometimes called remote radio heads (RRHs). Such remote radio units can or can not be integrated with antennas. Parts of distributed radio base stations can also be called nodes in a distributed antenna system (DAS). Further examples of network nodes include multi-standard radio (MSR) devices, such as MSR BSs, network controllers, such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), core network nodes (e.g., mobile switching centers (MSCs), mobile management entities (MMEs)), Operation and Maintenance (O&M) nodes, Operation Support Systems (OSS) nodes, Self-Optimizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Center (E-SMLC)), and / or Minimization of Drive Test (MDT) nodes. As another example, a network node can be a virtual network node as described in more detail below. More generally, however, network nodes can represent any suitable device (or group of devices) that is capable of, configured for, arranged to, and / or operable for enabling and / or providing wireless access to a wireless device, or providing some service to a wireless device that is connected or is to be connected to a wireless network.

[0635] Figure 3 In some embodiments, network node 160 includes processing circuitry 170, device readable medium 180, interface 190, auxiliary equipment 184, power source 186, power circuitry 187, and antenna 162. While Figure 3The network node 160 illustrated in the example wireless network can represent an apparatus comprising the illustrated combination of hardware components, but other embodiments can include network nodes with different combinations of components. It is understood that a network node comprises any combination of hardware and / or software needed to perform the tasks described herein as provided by a network node. Moreover, while the components of the network node 160 are shown as single boxes located within a larger box, or nested within multiple boxes, in practice, a network node can comprise multiple different physical components that make up a single illustrated component (e.g., the device readable medium 180 can comprise multiple individual disk drives, as well as multiple RAM modules).

[0636] Similarly, the network node 160 can be composed of multiple physical separate components (e.g., NodeB components and RNC components, or BTS components and BSC components, etc.), which can each have their own respective components. In certain scenarios where the network node 160 includes multiple separate components (e.g., BTS and BSC components), one or more of the separate components can be shared among several network nodes. For example, a single RNC can control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, in some instances, can be considered a single separate network node. In some embodiments, the network node 160 can be configured to support multiple radio access technologies (RATs). In such embodiments, some components can be duplicated (e.g., separate device readable medium 180 for the different RATs) and some components can be reused (e.g., the same antenna 162 can be shared by the RATs). The network node 160 can also include multiple sets of various illustrated components that are integrated into the network node 160 as different wireless technologies (e.g., various illustrated components for wireless technologies such as Global System for Mobile Communications (GSM), Wide Code Division Multiple Access (WCDMA), Long Term Evolution (LTE), New Radio (NR), WiFi, or Bluetooth wireless technologies). These wireless technologies can be integrated into the same or different chip or set of chips and other components within the network node 160.

[0637] The processing circuitry 170 is configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being provided by a network node. These operations performed by the processing circuitry 170 can include processing information obtained by the processing circuitry 170 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by 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.

[0638] The processing circuit 170 can comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field-programmable gate array, or any other processing circuit, whether implemented with logic component, tangible or transitory software, or a combination of hardware, software and / or encoded logic embodied in hardware, that can operate alone or in conjunction with other network node 160 components, such as the device readable medium 180, to provide the functionality of the network node 160. For example, the processing circuit 170 can execute instructions stored in the device readable medium 180 or in memory within the processing circuit 170. Such functionality can include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, the processing circuit 170 can include a system on a chip (SOC).

[0639] In some embodiments, the processing circuit 170 can include one or more of radio frequency (RF) transceiver circuitry 172 and baseband processing circuitry 174. In some embodiments, the radio frequency (RF) transceiver circuitry 172 and the baseband processing circuitry 174 can 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 172 and the baseband processing circuitry 174 can be on the same chip or set of chips, boards, or units.

[0640] In certain embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB or other such network device can be carried out by the processing circuit 170 executing instructions stored in memory within the processing circuit 170 or instructions stored on the device readable medium 180. In alternative embodiments, some or all of the functionality can be provided by the processing circuit 170 without executing instructions stored on a device readable medium, such as in a hard-wired or hard-coded manner. In any of those embodiments, whether executing instructions stored on a device readable storage medium or not, the processing circuit 170 is configured to provide the described functionality. The benefits provided by such functionality are not limited to the processing circuit 170 alone or to other components of the network node 160, but are enjoyed by the network node 160 as a whole, and / or by end users and the wireless network generally.

[0641] Device readable medium 180 can include any form of volatile or non-volatile computer readable memory including, by way of non-limiting example, volatile semiconductor memory devices such as DRAM, SRAM, ROM, etc. and / or non-volatile semiconductor memory devices such as ROM, etc. 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 can be used with processing circuitry 170. Device readable medium 180 can store any appropriate instructions, data or information, including a computer program, software, an application including one or more of logic, rules, code, tables, etc. and / or other instructions capable of being executed by processing circuitry 170 and utilized by network node 160. Device readable medium 180 can be used to store any calculations made by processing circuitry 170 and / or any data received via interface 190. In some embodiments, processing circuitry 170 and device readable medium 180 can be considered to be integrated.

[0642] Interface 190 is used in the wired or wireless communication of signaling and / or data between network node 160, network 106, and / or WDs 110. As illustrated, interface 190 comprises port(s) / terminal(s) 194 to send and receive data, for example to and from network 106 over a wired connection. Interface 190 also includes radio front end circuitry 192 that can be coupled to, or in some embodiments a part of, antenna 162. Radio front end circuitry 192 comprises filters 198 and amplifiers 196. Radio front end circuitry 192 can be connected to antenna 162 and processing circuitry 170. Radio front end circuitry can be configured to condition signals communicated between antenna 162 and processing circuitry 170. Radio front end circuitry 192 can receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 192 can convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 198 and / or amplifiers 196. The radio signal can then be transmitted via antenna 162. Similarly, when receiving data, antenna 162 can collect radio signals, which are then converted into digital data by radio front end circuitry 192. The digital data can be passed to processing circuitry 170. In other embodiments, the interface can comprise different components and / or different combinations of components.

[0643] In certain alternative embodiments, network node 160 can not include separate radio front-end circuitry 192, instead processing circuitry 170 can include radio front-end circuitry and can be connected to antenna 162 without separate radio front-end circuitry 192. Similarly, in some embodiments, all or some of RF transceiver circuitry 172 can be considered a part of interface 190. In still yet other embodiments, interface 190 can include one or more ports or terminals 194 that are part of a radio (not shown), radio front-end circuitry 192, and RF transceiver circuitry 172, and interface 190 can be in communication with baseband processing circuitry 174, which is part of a digital unit (not shown).

[0644] Antenna 162 can include one or more antennas or antenna arrays configured to send and / or receive wireless signals. Antenna 162 can be coupled to radio front-end circuitry 192 and can be any type of antenna and / or antenna array capable of transmitting and / or receiving wireless communications. In some embodiments, antenna 162 can include one or more omni-directional, sector or panel antennas operable to transmit / receive radio signals between, for example, 2 GHz and 66 GHz. Omni-directional antennas can be used to transmit / receive radio signals in all directions, sector antennas can be used to transmit / receive radio signals from devices within a particular area or region, and panel antennas can be line of sight antennas used to transmit / receive radio signals in a relatively straight line. In some instances, the use of more than one antenna can be referred to as MIMO. In certain embodiments, antenna 162 can be separate from network node 160 and can be connectable to network node 160 through an interface or port.

[0645] Antenna 162, interface 190, and / or processing circuitry 170 can be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by a network node. Any information, data and / or signals can be received from a wireless device, another network node and / or any other network equipment. Similarly, antenna 162, interface 190, and / or processing circuitry 170 can be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data and / or signals can be transmitted to a wireless device, another network node and / or any other network equipment.

[0646] Power circuitry 187 can comprise, or be coupled to, power management circuitry and is configured to supply the components of the network node 160 with power for performing the functionality described herein. Power circuitry 187 can receive power from power source 186. Power source 186 and / or power circuitry 187 can be configured to provide power to the various components of the network node 160 in a form suitable for use by each respective component (e.g., at a voltage and current level needed for each respective component). Power source 186 can be incorporated into, or external to, power circuitry 187 and / or the network node 160. For example, network node 160 can be connectable to an external power source (e.g., an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry 187. As a further example, power source 186 can comprise a power source attached to, or incorporated into power circuitry 187, such as a battery or battery pack. The battery can provide backup power should the external power source fail, allowing the network node 160 to perform a controlled shutdown if power is no longer available from the power source 186. Other types of power sources, such as photovoltaic devices, can also be used.

[0647] Alternative embodiments of the network node 160 can include additional components Figure 3 not shown in FIG. 1 1, that can be responsible 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 160 can include user interface devices to allow input of information into the network node 160 and to allow output of information from the network node 160. This can allow a user to perform diagnostic, maintenance, repair, and other administrative functions of the network node 160.

[0648] A "wireless device," as used herein, refers to a device that can communicate, either with or without direct human interaction, with a network and / or with another wireless device. The term "WD" can be used interchangeably, unless otherwise clear from the context, with a user equipment (UE). Wireless communication can involve the transmission and / or reception of wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information over a network. In some embodiments, a WD can be configured to transmit and / or receive information without direct human interaction. For example, a WD can be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network. Examples of a WD include, but are not limited to, a smart phone, a mobile phone, a cell phone, a voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless cameras, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop-mounted device, a laptop installed device, a smart device, a wireless customer-premise equipment (CPE), a vehicle-mounted wireless terminal device, etc. A WD can support device-to-device (D2D) communication, such as using proximity services (ProSe) or traffic advertisement (Ta), for example by implementing a 3GPP standard for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-everything (V2X), and can in this case be referred to as a D2D communication device. As yet another specific example, in an Internet of Things (IoT) scenario, a WD can represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another WD and / or a network node. The WD can in this case be a machine-to-machine (M2M) device, which can in a 3GPP context be referred to as an MTC device. As a particular example, a WD can be a UE implementing the 3GPP narrow band internet of things (NB-IoT) standard. Particular examples of such machines or devices are sensors, metering devices (e.g., power meters), industrial machinery, or home or personal appliances (e.g., refrigerators, televisions, etc.), personal wearables (e.g., watches, fitness trackers, etc.). In other scenarios, a WD can represent a vehicle or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation. A WD as described above can represent the endpoint of a wireless connection, in which case the device can be referred to as a wireless terminal. Further, a WD as described above can be mobile, in which case it can also be referred to as a mobile device or mobile terminal.

[0649] As illustrated, wireless device 110 includes antenna 111, interface 114, processing circuitry 120, device readable medium 130, user interface equipment 132, auxiliary equipment 134, power source 136, and power circuitry 137. WD 110 can include multiple sets of one or more of the illustrated components of WD 110 for different wireless technologies supported by WD 110, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to mention few. These wireless technologies can be integrated into the same or different chip sets as other components within WD 110.

[0650] Antenna 111 can include one or more antennas or antenna arrays, configured to send and / or receive wireless signals, and is connected to interface 114. In some alternatives, antenna 111 can be separate from WD 110, and be connectable to WD 110 through an interface or port. Antenna 111, interface 114, and / or processing circuitry 120 can be configured to perform any receiving or transmitting described herein as being performed by a WD. Any information, data and / or signals can be received from a network node and / or another WD. In some embodiments, radio front end and / or antenna 111 can be considered an interface.

[0651] As illustrated, interface 114 includes radio front end circuitry 112 and antenna 111. Radio front end circuitry 112 includes one or more filters 118 and amplifiers 116. Radio front end circuitry 112 is connected to antenna 111 and processing circuitry 120, and is configured to condition signals communicated between antenna 111 and processing circuitry 120. Radio front end circuitry 112 can be coupled to or a part of antenna 111. In some embodiments, WD 110 can not include separate radio front end circuitry 112, and instead, processing circuitry 120 can comprise radio front end circuitry and can be connected to antenna 111. Similarly, in some embodiments, some or all of RF transceiver circuitry 122 can be considered a part of interface 114. Radio front end circuitry 112 can receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 112 can convert the digital data into a signal with the appropriate channel and bandwidth parameters for transmission by antenna 111. The signal can then be transmitted by antenna 111. Similarly, when receiving data, antenna 111 can collect signals transmitted by other network nodes or WDs. The signals can then be converted by radio front end circuitry 112 into digital data, which can be passed to processing circuitry 120. In other embodiments, the interface can comprise different components and / or different combinations of components.

[0652] Processing circuitry 120 may include a combination of one or more of the following: a microprocessor, controller, central processing unit, digital signal processor, application-specific integrated circuit, field-programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and / or coded logic operable alone or in combination with other WD 110 components (such as device-readable medium 130) to provide WD 110 functionality. Such functionality may include any wireless features or benefits that provide the various wireless features or benefits described herein. For example, processing circuitry 120 may execute instructions stored in device-readable medium 130 or in memory within processing circuitry 120 to provide the functionality disclosed herein.

[0653] As shown, the processing circuitry 120 includes one or more of an RF transceiver circuitry 122, a baseband processing circuitry 124, and an application processing circuitry 126. In other embodiments, the processing circuitry may include different components and / or different combinations of components. In some embodiments, the processing circuitry 120 of the WD 110 may include a System-on-a-Chip (SOC). In some embodiments, the RF transceiver circuitry 122, the baseband processing circuitry 124, and the application processing circuitry 126 may reside on separate chips or chip sets. In alternative embodiments, some or all of the baseband processing circuitry 124 and the application processing circuitry 126 may be combined into a single chip or chip set, and the RF transceiver circuitry 122 may reside on a separate chip or chip set. In yet another alternative embodiment, some or all of the RF transceiver circuitry 122 and the baseband processing circuitry 124 may reside on the same chip or chip set, and the application processing circuitry 126 may reside on a separate chip or chip set. In yet another alternative embodiment, some or all of the RF transceiver circuitry 122, the baseband processing circuitry 124, and the application processing circuitry 126 may be combined into the same chip or chip set. In some embodiments, the RF transceiver circuit 122 may be part of the interface 114. The RF transceiver circuit 122 may regulate the RF signal of the processing circuit 120.

[0654] In some embodiments, some or all of the functionality described herein as being performed by WD may be provided by processing circuitry 120 executing instructions stored on device-readable medium 130, which in some embodiments may be a computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by processing circuitry 120, such as in a hard-wired manner, without executing instructions stored on a separate or discrete device-readable storage medium. In any embodiment of those particular embodiments, processing circuitry 120 may be configured to perform the functionality regardless of whether instructions stored on a device-readable storage medium are executed. The benefits provided by this functionality are not limited to processing circuitry 120 alone or other components of WD 110, but are enjoyed generally by WD 110 and / or generally by end users and wireless networks.

[0655] Processing circuitry 120 can be configured to perform any determining, calculating, or similar operations (such as certain obtaining operations) described herein as being performed by a WD. These operations, as performed by processing circuitry 120, can include processing information obtained by processing circuitry 120 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD 110, 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.

[0656] Device readable medium 130 can be operable to store a computer program, software, an application including one or more of logic, rules, code, tables, etc. and / or other instructions (i.e., to store instructions that can be executed by processing circuitry 120). Device readable medium 130 can include computer memory (e.g., Random Access Memory

[0657] User interface equipment 132 can provide means by which a human user can interact with WD 110. Such interaction can be of many forms, such as visual, audial, tactile, etc. User interface equipment 132 can be operable to generate output to the user and to allow input to be provided from the user. The type of interaction can vary depending on the type of user interface equipment 132 installed in WD 110. For example, if WD 110 is a smart phone, interaction can be via a touch screen; if WD 110 is a smart meter, interaction can be via a screen providing usage

[0658] Auxiliary equipment 134 is operable to provide more specialized functionality that can not be generally performed by WDs. This can include specialized sensors for making measurements for various purposes, interfaces for additional types of communication, such as wired communication etc. The inclusion and type of components of auxiliary equipment 134 can vary depending on the embodiment and / or scenario.

[0659] Power source 136 may, in some embodiments, take the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic devices or power cells, can also be used. WD 110 can further comprise power circuitry 137 for delivering power from power source 136 to the various parts of WD 110 which need power from power source 136 to carry out any of the functionality described or illustrated herein. Power circuitry 137 may, in certain embodiments, comprise power management circuitry. Additionally or alternatively, power circuitry 137 can be operable to receive power from an external power source; in which case WD 110 can be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical cable. Power circuitry 137 can also, in certain embodiments, be operable to deliver power from an external power source to power source 136. This could be, for example, for the charging of power source 136. Power circuitry 137 can perform any formatting, converting, or other modification of the power from power source 136, in order to make the power suitable for use by those parts of WD 110 which use power from power source 136.

[0660] Figure 4 One embodiment of a UE in accordance with various aspects described herein is shown. As used herein, a "user equipment" or "UE" can not necessarily have a user in the sense of a human being that owns and / or operates the relevant device. Instead a UE can represent a device that is intended for sale to, or operation by, a human user, but which can not, or initially can not, have an associated specific human user (e.g., a smart sprinkler controller). Alternatively, a UE can represent a device that is not intended for sale to, or operation by, an end user, but which can be associated with or operated for the benefit of a user (e.g., a smart power meter). UE 200 can be any UE recognized by the Third Generation Partnership Project (3GPP), including NB-IoT UEs, Machine Type Communication (MTC) UEs, and / or Enhanced MTC (eMTC) UEs. As used herein, a "UE" can be a device that is not a "WD." For example, a UE can be a head unit of a vehicle. Figure 4 As shown, UE 200 is one example of a WD configured for communication in accordance with one or more communication standards promulgated by the Third Generation Partnership Project (3GPP), such as 3GPP's GSM, UMTS, LTE, and / or 5G standards. As described previously, the terms "WD" and "UE" can be used interchangeably. Accordingly, although UE 200 is shown as a UE, the components described herein can equally be applicable to a WD, and vice versa. Figure 4 As shown, UE 200 is one example of a WD configured for communication in accordance with one or more communication standards promulgated by the Third Generation Partnership Project (3GPP), such as 3GPP's GSM, UMTS, LTE, and / or 5G standards. As described previously, the terms "WD" and "UE" can be used interchangeably. Accordingly, although UE 200 is shown as a UE, the components described herein can equally be applicable to a WD, and vice versa.

[0661] Figure 4In some embodiments, the UE 200 includes: processing circuitry 201 operatively coupled to input / output interface 205; radio frequency (RF) interface 209; network connection interface 211; memory 215 including random access memory (RAM), read-only memory (ROM), and storage medium 221 or the like; communication subsystem 231; power source 213; and / or any other component; or any combination thereof. Storage medium 221 includes operating system 223, application program 225, and data 227. In other embodiments, storage medium 221 can include other similar types of information. Some embodiments of UE can utilize all of these components, others can utilize only a subset of these components, and others can utilize none. The level of integration among the components can vary from embodiment to embodiment. Furthermore, some embodiments can include multiple instances of a component, such as multiple processing circuitry 201, which can process different Figure 4 The various components of UE 200 can be implemented as part of one or more chips on one or more motherboards, substrates, or other types of circuit boards. In some embodiments, some of the components of UE 200 can not be present or can be integrated into other components. In other embodiments, some of the components of UE 200 can be implemented or provided in hardware, which might include, for example, one or more processors, ASICs, and / or other hardware. Furthermore, in some embodiments, one or more of the components of UE 200 can be downloaded, streams, received, or otherwise obtained by UE 200 over one or more networks such as network 230.

[0662] Figure 4 In some embodiments, processing circuitry 201 can be configured to process computer instructions and data. Processing circuitry 201 can be configured to implement any sequential state machine operative to read and write data to / from computer program instructions. This state machine can implement the machine-readable instructions using hardware and / or software. For example, processing circuitry 201 can include one or more processors, ASICs, and / or other hardware. Examples of processors include Central Processing Units (CPUs), Graphics Processing Units (GPUs), and / or other processors. Processing circuitry 201 can be configured to process data in accordance with one or more computer programs and / or one or more computer applications. Data can be information stored in a format that can be read by a computer.

[0663] In the illustrated embodiment, the input / output interface 205 can be configured to provide a communication interface to either an input device, an output device, or both. The UE 200 can be configured to use the output device via the input / output interface 205. The output device can use a same type of interface port as the input device. For example, a USB port can be used to provide both input and output to and from the UE 200. The output device can be 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. The UE 200 can be configured to use the input device via the input / output interface 205 to allow a user to capture information into the UE 200. The input device can include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital still 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 can include a capacitive or resistive touch sensor to sense input from a user. The sensor can be, for example, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another like sensor, or any combination thereof. For example, the input device can be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.

[0664] Figure 4 In the illustrated embodiment, the RF interface 209 can be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna. The network connection interface 211 can be configured to provide a communication interface to a network 243a. The network 243a can encompass wired and / or wireless networks, such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network, or any combination thereof. For example, the network 243a can include a Wi-Fi network. The network connection interface 211 can be configured to include a receiver and a transmitter interface to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, TCP / IP, SONET, ATM, or the like. The network connection interface 211 can implement receiver and transmitter functionality appropriate to the communication network links (e.g., optical, electrical, and the like). The transmitter and receiver functions can share circuit components, software, or firmware, or alternatively can be implemented separately.

[0665] The RAM 217 can be configured to interface via the bus 202 to the processing circuitry 201 to provide storage or caching of data or computer instructions during the execution of software programs such as the operating system, application programs, and device drivers. The ROM 219 can be configured to provide computer instructions or data to the processing circuitry 201. For example, the ROM 219 can be configured to store invariant low-level system code or data for basic system functions such as basic input and output (I / O) operations, startup, or reception of keystrokes from a keyboard that are stored in non-volatile memory. The storage medium 221 can be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash memories. In one example, the storage medium 221 can be configured to include operating system 223, application program 225 such as a web browser application, a widget or gadget engine, or another application, and data file 227. The storage medium 221 can store any of a variety of operating systems usable by the UE 200 or combinations of operating systems.

[0666] The storage medium 221 can be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), soft plastic disk, flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, High-Density Digital Versatile Disk (DVD) optical disk drive, internal hard disk drive, Blu-Ray optical disk drive, holographic data storage (HDDS) optical disk drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smart card memory such as a subscriber identity module or a removable user identity (SIM / RUIM) module, other memory, or any combination thereof. The storage medium 221 can allow the UE 200 to access computer-executable instructions, application programs or the like stored on transitory or non-transitory memory media, to off-load data, or to upload data. A manufacturing product, such as an article of manufacture compliant with the communication system, can be tangibly embodied in the storage medium 221, which can comprise a device readable medium.

[0667] Figure 4In particular embodiments, processing circuitry 201 can be configured to use communication subsystem 231 to communicate with network 243b. Network 243a and network 243b can be one or more of the same network or one or more different networks. Communication subsystem 231 can be configured to include one or more transceivers used to communicate with network 243b. For example, communication subsystem 231 can be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication according to one or more communication protocols, such as IEEE 802.2, CDMA, WCDMA, GSM, LTE, Universal Terrestrial Radio Access (UTRA) network (UTRAN), Evolved UTRA (E-UTRA) network (E-UTRAN), WiMax, or the like. Each transceiver can include transmitter 233 and / or receiver 235 to implement transmitter or receiver functionality, respectively, as appropriate for transceivers of a RAN link (e.g., frequency allocation and the like). Further, transmitter 233 and receiver 235 of each transceiver can share circuit components, software, or firmware, or alternatively can be implemented separately.

[0668] In the illustrated embodiment, communication functions of communication subsystem 231 can include data communication, voice communication, multimedia communication, short-range communications, such as Bluetooth, near-field communication, location-based communication, such as the use of the global positioning system (GPS) to determine a location, another like function, or any combination thereof. For example, communication subsystem 231 can include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. Network 243b can encompass wired and / or wireless networks, such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network, or any combination thereof. For example, network 243b can be a cellular network, a Wi-Fi network, and / or a near-field network. Power source 213 can be configured to provide alternating current (AC) or direct current (DC) power to components of UE 200.

[0669] The features, benefits and / or functions described herein can be implemented in one of the components of UE 200 or divided among several components of UE 200. Further, the features, benefits and / or functions described herein can be implemented in any combination of hardware, software or firmware. In one example, communication subsystem 231 can be configured to include any of the components described herein. Further, processing circuitry 201 can be configured to communicate with any of such components over bus 202. In another example, any of such components can be represented by

[0670] Figure 5 is a schematic block diagram illustrating a virtualization environment 300 in which functions implemented by some embodiments can be virtualized. In the present context, virtualizing means creating virtual versions of physical devices or arrangements, which can include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to a node (such as a virtualized base station or a virtualized radio access node) or to an apparatus (such as a UE, a wireless device or any other type of communication device or component thereof), and relates to an implementation in which at least a part of the functionality is implemented as a virtual component(s) (such as one or more applications, components, functions, virtual machines or containers running on one or more physical processing nodes in one or more networks).

[0671] In some embodiments, some or all of the functions described herein can be implemented in a virtual component executed by one or more virtual machines implemented in one or more virtual environments 300 hosted by one or more of hardware nodes 330. Further, in embodiments in which the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), then the network node can be entirely virtualized.

[0672] The functions can be implemented by one or more applications 320 (which alternatively can be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operative to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein. The applications 320 are run in virtualization environment 300 which provides hardware 330 including processing circuitry 360 and memory 390. The memory 390 contains instructions 395 executable by the processing circuitry 360 whereby the application 320 is operative to provide one or more of the features, benefits, and / or functions disclosed herein.

[0673] Virtualization environment 300 comprises general-purpose or special-purpose network hardware devices 330 comprising a set of one or more processors or processing circuitry 360, which can be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors. Each hardware device can comprise memory 390-1 which can be non-persistent memory for temporarily storing instructions 395 or software executed by processing circuitry 360. Each hardware device can comprise one or more network interface controllers (NICs) 370 (also referred to as network interface cards) comprising physical network interface 380. Each hardware device can also include non-transitory, persistent, machine-readable storage media 390-2 having stored therein software 395 and / or instructions executable by processing circuitry 360. Software 395 can include any type of software including software to instantiate one or more virtualization layers 350 (also referred to as hypervisors), software to execute virtual machines 340 and allow them to execute software without

[0674] Virtual machines 340 comprise virtual processing, virtual memory, virtual networking or interface, and virtual storage, and can be run by a corresponding virtualization layer 350 or hypervisor. Different embodiments of the instance of virtual appliance 320 can be implemented on one or more of virtual machines 340, and the implementations can be made in different ways.

[0675] During operation, processing circuitry 360 executes software 395 to instantiate the hypervisor or virtualization layer 350, which can sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer 350 can provide a virtual operating platform that appears like networking hardware to virtual machine 340.

[0676] As Figure 5As shown, hardware 330 can be a standalone network node with generic or specific components. Hardware 330 can comprise antenna 3225 and can implement some functions via virtualization. Alternatively, hardware 330 can be part of a larger cluster of hardware, e.g., in a data center or customer premise equipment (CPE), where many hardware nodes work together as part of a bigger system and are managed via management and orchestration (MANO) 3100, which, among others, oversees lifecycle management of applications 320.

[0677] Virtualization of the hardware is in some contexts referred to as Network Function Virtualization (NFV). NFV can 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.

[0678] In the context of NFV, virtual machine 340 can be a software implementation of a physical machine, which, among others, run programs, resembling a physical non-virtualized machine. Each of virtual machine 340, and that part of hardware 330 that executes that virtual machine, if it is hardware dedicated to that virtual machine and / or hardware that is shared by that virtual machine with other virtual machines 340 of the software implementation, form a separate Virtual Network Element (VNE).

[0679] Also in the context of NFV, Virtual Network Function (VNF) is responsible for the control- plane and user-plane protocol functions executable within one or more virtual machines 340 on top of hardware networking infrastructure 330, and corresponds to Figure 5 application 320 in

[0680] In some embodiments, one or more radio units 3200 that each include one or more transmitters 3220 and one or more receivers 3210 can be coupled to one or more antennas 3225. Radio units 3200 can communicate directly with hardware nodes 330 via one or more appropriate network interfaces and can be used in combination with virtual components to provide virtual nodes with radio capabilities (such as a radio access node or base station).

[0681] In some embodiments, some signaling can be able to be implemented by using control system 3230 which can alternatively be used for communication between hardware nodes 330 and radio units 3200.

[0682] Referring to Figure 6According to an embodiment, the communication system includes a telecommunication network 410, such as a 3GPP-type cellular network, which comprises an access network 411, such as a radio access network, and a core network 414. The access network 411 comprises a plurality of base stations 412a, 412b, 412c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 413a, 413b, 413c. Each base station 412a, 412b, 412c is connectable to the core network 414 over a wired or wireless connection 415. A first UE 491 located in coverage area 413c is configured to wirelessly connect to, or be paged by, the corresponding base station 412c. A second UE 492 in coverage area 413a is wirelessly connectable to the corresponding base station 412a. While a plurality of UEs 491, 492 are illustrated in this example, the

[0683] The telecommunication network 410 is itself connected to a host computer 430, which can be embodied in the hardware and / or software of a standalone server, a cloud-implemented server, a distributed server, or as processing resources in a server farm. The host computer 430 can be under the ownership or control of a service provider, or can be operated by the service provider or on behalf of the service provider. Connections 421 and 422 between the telecommunication network 410 and the host computer 430 can be implemented via wired or wireless connections. The connections 421 and 422 can be direct connections or can pass through intermediate networks, such as the Internet, between the telecommunication network 410 and the host computer 430. The intermediate networks can be access networks operated by operators other than the operator of the telecommunication network 410 or the host computer 430.

[0684] Figure 6The communication system as a whole enables connectivity between the connected UEs 491, 492 and the host computer 430. The connectivity can be described as an over-the-top (OTT) connection 450. The host computer 430 and the connected UEs 491, 492 are configured to communicate data and / or signaling over the OTT connection 450 using the access network 41 1, the core network 414, any intermediate network 420 and possible further infrastructure (not shown) as intermediaries. The OTT connection 450 can be transparent in the sense that the participating communication devices through which the OTT connection 450 passes are unaware of routing of uplink and downlink communications. For example, a base station 412 can not or need not be aware of the past routing of an incoming downlink communication with data originating from a host computer 430 to be forwarded (e.g., handed over) to a connected UE 491. Similarly, the base station 412 need not be aware of the future routing of an outgoing uplink communication with data originating from the connected UE 491 to be forwarded (e.g., handed over) to the host computer 430.

[0685] Example implementations, in accordance with an embodiment, of the UE, base station and host computer as outlined abov Figure 7 In the communication system 500, host computer 510 comprises hardware 515 enabling communication with the communication system 500. The hardware 515 can comprise communication interface 516 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system 500. The host computer 510 further comprises processing circuitry 518, which can comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. The host computer 510 further comprises software 511, which is stored in or accessible by the host computer 510 and executable by the processing circuitry 518. The software 511 includes a host application 512. The host application 512 can be operable to provide services to a remote user, such as a UE 530 connecting via an OTT connection 550 terminating at the UE 530 and the host computer 510. In providing services to the remote user, the host application 512 can provide user data which is transmitted using the OTT connection 550.

[0686] The communication system 500 further includes a base station 520 provided in a telecommunication system and comprising hardware 525 enabling it to communicate with the host computer 510 and with the UE 530. The hardware 525 can include a communication interface 526 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 500 as well as a radio interface 527 for setting up and maintaining at least a wireless connection 570 with the UE 530 located in a coverage area 520a served by the base station 520. Figure 7The communication interface 526 is configured to facilitate a connection 560 to the host computer 510. The connection 560 can be direct or it can pass through a core network (not shown) of the telecommunication system 500 (not shown) and / or one or more intermediate networks outside the telecommunication system. Figure 7 The base station 520 is configured to perform functions of a base station 412a, 412b, 412c or 414a, 414b, 414c, as described above. In the embodiment shown, the base station 520 has a hardware 525, which can comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. The base station 520 further has software 521 stored internally or accessible via an external connection.

[0687] The communication system 500 further includes the UE 530 already referred to. Its hardware 535 can include a radio interface 537 configured to set up and maintain a wireless connection 570 with a base station serving a coverage area in which the UE 530 resides. The hardware 535 of the UE 530 further includes processing circuitry 538, which can comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. The UE 530 further comprises software 531 stored internally or accessible via an external connection. The software 531 includes a client application 532. The client application 532 can be operable to provide a service to a human or non-human user via the UE 530 with the support of the host computer 510. In the host computer 510, an executing host application 512 can communicate with the executing client application 532 via the OTT connection 550 terminating at the UE 530 and the host computer 510. In providing the service to the user, the client application 532 can receive request data from the host application 512 and provide user data in response to the request data. The OTT connection 550 can transfer both the request data and the user data. The client application 532 can interact with the user to generate the user data.

[0688] It is noted that Figure 7 The host computer 510, base station 520 and UE 530 illustrated can be similar or identical to the host computer 430, one of the base stations 412a, 412b, 412c and one of the UEs 491, 492 of Figure 6 respectively. That is, the inner workings of these entities can be as shown in Figure 7 and the surrounding network topology can independently be Figure 6 the topology of

[0689] Figure 7In the example of Figure 5, OTT connection 550 is illustrated as a single connection; however, it will be appreciated that OTT connection 550 could be formed from multiple connections. For example, OTT connection 550 could be formed from a combination of wired and / or wireless connections. In one embodiment, OTT connection 550 can be formed from a combination of connections including an Internet connection, a telephone line, a radio frequency connection, or any combination of these. In one embodiment, a connection can be formed between UE 530 and host computer 510 via base station 520 and one or more network nodes of the core network. In one embodiment, base station 520 can be implemented as a base transceiver station and a controller. In one embodiment, the base transceiver station can be a base station, a nodeB, an eNodeB, or another type of apparatus. In one embodiment, the base transceiver station can be part of multihop relay or relay node. In one embodiment, the base transceiver station can be a gNB for a 5G network. In one embodiment, the base transceiver station can be a base station for a network other than a 5G network.

[0690] Wireless connection 570 between UE 530 and base station 520 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to UE 530 using OTT connection 550, in which wireless connection 570 forms the last segment. More precisely, the teachings of these embodiments can improve the data rate, latency, power consumption, and thereby provide benefits such as reduced user waiting time, relaxed restrictions on file size, better responsiveness, or extended battery lifetime.

[0691] A measurement procedure can be implemented to measure data rates, latencies, and other factors on which one or more embodiments improve. There can further be an optional network functionality to reconfigure OTT connection 550 between host computer 510 and UE 530 in response to variations in the measurement results. The measurement procedure and / or the network functionality to reconfigure OTT connection 550 can be implemented in software 511 and hardware 515 of host computer 510 or in software 531 and hardware 535 of UE 530, or both. In embodiments, sensors (not shown) can be deployed in or in association with communication devices through which OTT connection 550 passes; the sensors can participate in the measurement procedure by supplying values of the physical quantities exemplified above, or supplying values of other physical quantities from which software 511, 531 can compute or estimate the monitored quantities. The reconfiguring of OTT connection 550 can include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect base station 520, and it can be unknown or invisible for base station 520. Such procedures and functionalities can be known in the art and put into practice. The measurements can in some embodiments involve

[0692] Figure 8is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which can be those described with reference to Figure 6 and Figure 7 Figures 1 1 and 12. For simplicity of the present disclosure, only drawing references to Figure 8 will be included in this section. In step 610, the host computer provides user data. In substep 61 1 (which can be optional) of step 610, the host computer provides the user data by executing a host application. In step 620, the host computer initiates a transmission carrying the user data to the UE. In step 630 (which can be optional), the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, according to the teachings of the embodiments described throughout this disclosure. In step 640 (which can also be optional), the UE executes a client application associated with the host application executed by the host computer.

[0693] Figure 9 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which can be those described with reference to Figure 6 and Figure 7 Figures 1 1 and 12. For simplicity of the present disclosure, only drawing references to Figure 9 will be included in this section. In step 710 of the method, the host computer provides user data. In an optional substep (not shown), the host computer provides the user data by executing a host application. In step 720, the host computer initiates a transmission carrying the user data to the UE. The transmission can pass via the base station, according to the teachings of the embodiments described throughout this disclosure. In step 730 (which can be optional), the UE receives the user data carried in the transmission.

[0694] Figure 10 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which can be those described with reference to Figure 6 and Figure 7 Figures 1 1 and 12. For simplicity of the present disclosure, only drawing references to Figure 10The accompanying drawings are referenced. In step 810 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 820, the UE provides user data. In sub-step 821 of step 820 (which may be optional), the UE provides user data by executing a client application. In sub-step 811 of step 810 (which may be optional), the UE executes a client application that responds to the received input data provided by the host computer to provide user data. In providing user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which user data is provided, the UE initiates the transmission of user data to the host computer in sub-step 830 (which may be optional). According to the teachings of the embodiments described throughout this disclosure, in step 840 of the method, the host computer receives user data transmitted from the UE.

[0695] Figure 11 This is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be referenced... Figure 6 and Figure 7 The host computers, base stations, and UEs mentioned above. For the sake of brevity, this section will only include descriptions of... Figure 11 The accompanying drawings are referenced. In step 910 (which may be optional), the base station receives user data from the UE in accordance with the teachings of the embodiments described throughout this disclosure. In step 920 (which may be optional), the base station initiates a transmission of the received user data to the host computer. In step 930 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

[0696] Any appropriate steps, methods, features, functions, or benefits disclosed herein can be performed, either manually or by one or more virtual devices or modules of one or more virtual devices. Each virtual device can comprise a number of these functional units. These functional units can be implemented via processing circuitry, which can include one or more microprocessor or microcontroller, along with other digital hardware. The processing circuitry can be configured to execute program code stored in memory, which can include one or several types of memory such as read-only memory (ROM), random-access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and / or data

[0697] Figure 12 A method according to certain embodiments is shown. In certain embodiments, the method can be performed by a wireless device, such as the wireless device 110 or a UE described above, in order to generate a network index corresponding to an NPN index of a combination of a PLMN and a CAG ID or an index of a combination of a PLMN and a network ID (NID). At step 1201, the method detects a system information broadcast, where the broadcast includes a list of non-public network identifiers (NPNs). At step 1202, the method identifies whether the list of non-public network identifiers includes at least an element containing at least one CAG identifier and whether it includes such an element. At step 1203, the method generates a CAG index based at least in part on a number of PLMN elements contained in combination with a cag-IdentityList element. At step 1204, the method identifies whether the list of non-public network identifiers includes at least an element containing at least one NID identifier and whether it includes such an element. At step 1205, the method generates a NID index based at least in part on a number of NIDs contained in a nid-List. Figure 12 Certain steps of the method of FIG. 12 can be optional, depending on the embodiment. As an example, step 1203 can be optional in some embodiments (e.g., if at step 1202, the list of non-public network identifiers does not include at least an element containing at least one CAG identifier, then step 1203 can be omitted). As another example, step 1205 can be optional in some embodiments (e.g., if at step 1204, the list of non-public network identifiers does not include at least an element containing at least one NID identifier, then step 1205 can be omitted).

[0698] Figure 13 A method according to certain embodiments is shown. In certain embodiments, the method can be performed by a wireless device, such as the wireless device 110 or a UE described above, or by a network node, such as the network node 160 described above, in order to generate a network index corresponding to an NPN index of a combination of a PLMN and a CAG ID or an index of a combination of a PLMN and a network ID (NID). At step 1301, the method determines whether a list of non-public network identifiers (NPNs) contained in system information broadcast by a network node comprises at least an element containing at least one CAG identifier and / or at least an element containing at least one NID identifier. At step 1302, in response to determining that the list of non-public network identifiers comprises at least an element containing at least one CAG identifier and whether it comprises such an element, the method generates a CAG index based at least in part on a number of PLMN elements contained in combination with the cag-IdentityList element. At step 1303, in response to determining that the list of non-public network identifiers comprises at least an element containing at least one NID identifier and whether it comprises such an element, the method generates a NID index based at least in part on a number of NIDs contained in the nid-List. In certain embodiments, step 1302 and / or step 1303 can be optional, e.g. depending on the result of the determination made in step 1301. If it is determined in step 1301 that the list of non-public network identifiers does not comprise at least an element containing at least one CAG identifier, certain embodiments can omit step 1302. If it is determined in step 1301 that the list of non-public network identifiers does not comprise at least an element containing at least one NID identifier, certain embodiments can omit step 1303.

[0699] Figure 14 A schematic block diagram of a device 1400 in a wireless network (e.g., the wireless network shown in Figure 3 Fig. 1). The device can be implemented in a wireless device or network node, e.g., the wireless device 110 or network node 160 shown in Figure 3 Fig. 1. The device 1400 is operable to carry out the example method for generating a network index corresponding to an NPN index of a combination of a PLMN and a CAG ID or an index of a combination of a PLMN and a network ID (NID) as described in relation to Figure 13 Fig. 13 and any other processes or methods disclosed herein. It is also to be understood that the method of Figure 13 Fig. 13 need not necessarily be executed by the device 1400 alone. At least some operations of the method can be performed by one or more other entities.

[0700] The virtual device 1400 may include processing circuitry, which may include one or more microprocessors or microcontrollers, as well as other digital hardware such as digital signal processors (DSPs), dedicated digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or more types of memory, such as read-only memory (ROM), random access memory, cache memory, flash memory devices, optical storage devices, etc. In several embodiments, the program code stored in the memory includes program instructions for executing one or more telecommunications and / or data communication protocols and instructions for executing one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause system information unit 1402, CAD index unit 1404, NID index unit 1406, and any other suitable unit of device 1400 to perform corresponding functions according to one or more embodiments of this disclosure.

[0701] like Figure 14 As shown, device 1400 includes a system information unit 1402, a CAD indexing unit 1404, and an NID indexing unit 1406. System information unit 1402 is configured to obtain system information broadcast by network nodes and determine whether a list of non-public network identifiers (NPNs) contained in the system information includes at least one element containing at least one CAG identifier and / or at least one element containing at least one NID identifier. In response to determining that the list of non-public network identifiers (NPNs) contained in the system information includes at least one element containing at least one CAG identifier, system information unit 1402 may provide the list of NPNs to CAD indexing unit 1404, which is configured to generate a CAG index based at least in part on the number of PLMN elements included in combination with the cag-IdentityList elements. In response to determining that the list of non-public network identifiers (NPNs) contained in the system information includes at least one element containing at least one NID identifier, the system information unit 1402 may provide the list of NPNs to the NID indexing unit 1406, the NID indexing unit being configured to generate an NID index based at least in part on the number of NIDs contained in the nid-list.

[0702] Other embodiments can allocate functionality among the system information unit 1402, the CAD indexing unit 1404, and the NID indexing unit 1406 in any other suitable manner. As an example, in certain embodiments, the system information unit 1402 can be configured to obtain system information broadcast by a network node, and provide a list of NPNs contained in the system information to the CAD indexing unit 1404 and the NID indexing unit 1406. The CAD indexing unit 1404 can be configured to determine whether the list of NPNs includes at least an element containing at least one CAG identifier and whether it includes such an element. If “yes”, the CAD indexing unit 1404 can be further configured to generate a CAG index based at least in part on a number of PLMN elements contained in combination with the cag-IdentityList element. The NID indexing unit 1406 can be configured to determine whether the list of NPNs includes at least an element containing at least one NID identifier and whether it includes such an element. If “yes”, the NID indexing unit 1406 can be further configured to generate a NID index based at least in part on a number of NIDs contained in the nid-List.

[0703] The term unit can have conventional meaning in the field of electronics, electrical engineering, and / or electronics arts, and can include, for example, electrical and / or

[0704] In some embodiments, a computer program, computer program product, or computer readable storage medium includes instructions that, when executed on a computer, perform any of the embodiments disclosed herein. In further examples, the instructions are carried on a signal or carrier wave and the instructions are executable on a computer, where, when executed, perform any of the embodiments disclosed herein. Embodiments

[0705] Group A Embodiments

[0706] 1. A method in a wireless device (e.g., a UE) for generating a network index corresponding to an index of a combination of a public land mobile network (PLMN) and a closed access group (CAG) ID of a non-public network (NPN) or an index of a combination of a PLMN and a network ID (NID), wherein the generating comprises the following steps:

[0707] - detecting a system information broadcast, wherein the broadcast includes a list of non-public network identifiers (NPNs);

[0708] - identifying whether the list of non-public network identifiers comprises at least an element containing at least one CAG identifier and whether it comprises such an element;

[0709] - generating CAG indices based at least partly on the number of PLMN elements contained in combination with the cag-IdentityList element;

[0710] - identifying whether the list of non-public network identifiers comprises at least an element containing at least one NID identifier and whether it comprises such an element; and

[0711] - generating NID indices based at least partly on the number of NIDs contained in the nid-List.

[0712] 2. The method according to embodiment 1, wherein generating the CAG indices further takes into account whether a list of PLMN identities contained in the system information broadcast is present and, if so, arranging the CAG indices such that they inherit the index values generated for the PLMN identities.

[0713] 3. The method according to embodiment 1, wherein generating the NID indices further takes into account whether a list of PLMN identities contained in the system information broadcast is present and, if so, arranging the NID indices such that they inherit the index values generated for the CAG indices.

[0714] 4. The method according to embodiment 1, wherein generating the CAG or NID indices further comprises the following steps:

[0715] - detecting the value of the cellReservedForOtherUse parameter and when the value of the parameter is set to true;

[0716] - generating CAG indices assuming that no previous PLMN index values are present; and

[0717] - generating NID indices assuming that no previous PLMN index values are present.

[0718] 5. The method according to any of the previous embodiments, wherein the generated indices are used when transmitting an RRC setup complete message, the indices being contained in the message as a representation of the network for which access is requested.

[0719] 6. A method in a wireless network for associating network types of different network identifiers in a first system information broadcast with human-readable network names of the different network identifiers in a second system information broadcast.

[0720] 7. The method according to embodiment 6, wherein the association is based on a quantity of network identifiers in the first system information broadcast corresponding to a quantity of human-readable network name elements in the second system information broadcast.

[0721] 8. The method according to embodiment 7, wherein at least one of the human-readable network name elements is assigned a value corresponding to “no name” being broadcast.

[0722] 9. A method in a wireless device (e.g. UE) for verifying system information, wherein the verifying step comprises:

[0723] - reading the cellReservedForOtherUse parameter; and

[0724] - selecting a network identity from the NPN-IdentityInfoList if the cellReservedForOtherUse parameter has the value “true”, and from the PLMN-IdentityInfoList if the cellReservedForOtherUse parameter has the value “false”.

[0725] 10. The method according to embodiment 9, wherein the selecting comprises selecting a first network identity from any of the lists.

[0726] 11. A method in a wireless device (e.g. UE) for verifying system information, wherein the verifying step comprises:

[0727] - reading a first element from the PLMN-IdentityInfoList; and

[0728] - selecting a network identity from the NPN-IdentityInfoList for use in verifying system information if the first element is detected as a standardized element indicating no normal service available.

[0729] 12. The method of any of the previous embodiments, further comprising:

[0730] - providing user data; and

[0731] - forwarding the user data to a host computer via a transmission to a base station.

[0732] B group embodiments

[0733] 13. A method in a network node for generating a network index corresponding to an index of a combination of a PLMN and a CAG ID or a combination of a PLMN and a Network ID (NID), wherein the generating comprises the steps of:

[0734] for system information broadcasted by the network node, wherein the broadcast includes a list of non-public network identifiers (NPNs);

[0735] - if the list of non-public network identifiers includes at least an element containing at least one CAG identifier and if it includes such an element, generating a CAG index based at least in part on the number of PLMN elements contained in combination with the cag-IdentityList element; and

[0736] - if the list of non-public network identifiers includes at least an element containing at least one NID identifier and if it includes such an element, generating a NID index based at least in part on the number of NIDs contained in the nid-List.

[0737] 14. The method of embodiment 13, wherein the network node associates the NID index as a reference when broadcasting or transmitting unified access control parameters.

[0738] 15. The method of any of the previous embodiments, further comprising:

[0739] - obtaining user data; and

[0740] - forwarding the user data to a host computer or a wireless device.

[0741] C Group Embodiments

[0742] 16. A wireless device, the wireless device comprising:

[0743] - processing circuitry configured to perform any of the steps of any of the Group A embodiments; and

[0744] - power supply circuitry configured to supply power to the wireless device.

[0745] 17. A base station, the base station comprising:

[0746] - processing circuitry configured to perform any of the steps of any of the Group B embodiments; and

[0747] - power supply circuitry configured to supply power to the base station.

[0748] 18. A user equipment (UE), the UE comprising:

[0749] - an antenna configured to transmit and receive wireless signals;

[0750] - a radio front-end circuit connected to the antenna and to the processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry;

[0751] - the processing circuitry configured to perform any of the steps of any of the embodiments of group A;

[0752] - the input interface connected to the processing circuitry, and configured to allow input of information into the UE to be processed by the processing circuitry;

[0753] - the output interface connected to the processing circuitry, and configured to output information from the UE that has been processed by the processing circuitry; and

[0754] - the battery connected to the processing circuitry, and configured to supply power to the UE.

[0755] 19. A computer program comprising instructions which when executed on a computer perform any of the steps of any of the embodiments of group A.

[0756] 20. A computer program product comprising a computer program comprising instructions which when executed on a computer perform any of the steps of any of the embodiments of group A.

[0757] 21. A non-transitory computer-readable storage medium or carrier comprising a computer program comprising instructions which when executed on a computer perform any of the steps of any of the embodiments of group A.

[0758] 22. A computer program comprising instructions which when executed on a computer perform any of the steps of any of the embodiments of group B.

[0759] 23. A computer program product comprising a computer program comprising instructions which when executed on a computer perform any of the steps of any of the embodiments of group B.

[0760] 24. A non-transitory computer-readable storage medium or carrier comprising a computer program comprising instructions which when executed on a computer perform any of the steps of any of the embodiments of group B.

[0761] 25. A communication system including a host computer comprising:

[0762] - the processing circuitry configured to provide user data; and

[0763] - a communications interface configured to forward the user data to a cellular network for transmission to a user equipment (UE),

[0764] - wherein the cellular network comprises a base station having a radio interface and processing circuitry, the base station's processing circuitry being configured to perform any of the steps of any of the embodiments of group B.

[0765] 26. The communication system of the previous embodiment, further including the base station.

[0766] 27. The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station.

[0767] 28. The communication system of the previous 3 embodiments, wherein:

[0768] - the host computer has processing circuitry configured to execute a host application, thereby providing the user data; and

[0769] - the UE includes processing circuitry configured to execute a client application associated with the host application.

[0770] 29. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:

[0771] - providing, at the host computer, user data; and

[0772] - initiating, at the host computer, a transmission carrying the user data to the UE via a cellular network, the cellular network comprising the base station, wherein the base station performs any of the steps of any of the embodiments of group B.

[0773] 30. The method of the previous embodiment, further comprising transmitting, at the base station, the user data.

[0774] 31. The method of the previous 2 embodiments, wherein the user data is provided at the host computer by execution of a host application, the method further comprising executing, at the UE, a client application associated with the host application.

[0775] 32. A user equipment (UE) configured to communicate with a base station, the UE comprising a radio interface and processing circuitry, the processing circuitry being configured to perform the method of the previous 3 embodiments.

[0776] 33. A communication system including a host computer comprising:

[0777] - processing circuitry configured to provide user data; and

[0778] - a communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE),

[0779] - wherein the UE comprises a radio interface and processing circuitry, components of the UE configured to perform any of the steps of any of the embodiments of Group A.

[0780] 34. The communication system of the previous embodiment, wherein the cellular network further comprises a base station configured to communicate with the UE.

[0781] 35. The communication system of the previous 2 embodiments, wherein:

[0782] - the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and

[0783] - the processing circuitry of the UE is configured to execute a client application associated with the host application.

[0784] 36. A method implemented in a communication system including a host computer, a base station, and a user equipment (UE), the method comprising:

[0785] - providing, at the host computer, user data; and

[0786] - initiating, at the host computer, a transmission carrying the user data to the UE via a cellular network, the cellular network comprising the base station, wherein the UE performs any of the steps of any of the embodiments of Group A.

[0787] 37. The method of the previous embodiment, further comprising receiving, at the UE from the base station, the user data.

[0788] 38. A communication system including a host computer comprising:

[0789] - a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station,

[0790] - wherein the UE comprises a radio interface and processing circuitry, the processing circuitry of the UE configured to perform any of the steps of any of the embodiments of Group A.

[0791] 39. The communication system of the previous embodiment, further comprising the UE.

[0792] 40. The communication system of the previous 2 embodiments, further comprising the base station, wherein the base station comprises a radio interface configured to communicate with the UE and a communication interface configured to forward user data carried by transmissions from the UE to the base station to the host computer.

[0793] 41. The communication system of the previous 3 embodiments, wherein:

[0794] - the processing circuitry of the host computer is configured to execute a host application; and

[0795] - the processing circuitry of the UE is configured to execute a client application associated with the host application, thereby providing the user data.

[0796] 42. The communication system of the previous 4 embodiments, wherein:

[0797] - the processing circuitry of the host computer is configured to execute a host application, thereby providing request data; and

[0798] - the processing circuitry of the UE is configured to execute a client application associated with the host application, thereby providing the user data in response to the request data.

[0799] 43. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:

[0800] - receiving, at the host computer, user data transmitted from the UE to the base station, wherein the UE performs any of the steps of any of the Group A embodiments.

[0801] 44. The method of the previous embodiment, further comprising providing, at the UE, user data to the base station.

[0802] 45. The method of the previous 2 embodiments, further comprising:

[0803] - at the UE, executing a client application thereby providing user data for transmission; and

[0804] - at the host computer, executing a host application associated with the client application.

[0805] 46. The method of the previous 3 embodiments, further comprising:

[0806] - at the UE, executing a client application; and

[0807] - at the UE, receiving input data for the client application, the input data being provided at the host computer by executing a host application associated with the client application,

[0808] - wherein the user data to be transmitted is provided by the client application in response to the input data.

[0809] 47. A communication system including a host computer comprising a communication interface configured to receive user data originating from a transmission from a user equipment, UE, to a base station, wherein the base station comprises a radio interface and processing circuitry, the base station's processing circuitry configured to perform any of the steps of any of the Group B embodiments.

[0810] 48. The communication system of the previous embodiment, further including the base station.

[0811] 49. The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station.

[0812] 50. The communication system of the previous 3 embodiments, wherein:

[0813] - the host computer's processing circuitry is configured to execute a host application;

[0814] - the UE is configured to execute a client application associated with the host application, thereby providing the user data for receipt by the host computer.

[0815] 51. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:

[0816] - the host computer receiving user data transmitted from the base station, the user data originating from a transmission by the UE to the base station, wherein the UE performs any of the steps of any of the Group A embodiments.

[0817] 52. The method of the previous embodiment, further including the base station receiving the user data from the UE.

[0818] 53. The method of the previous 2 embodiments, further including the base station initiating transmission of the received user data to the host computer.

[0819] Figure 15A , Figure 15B , Figure 17 , Figure 18 and Figure 19Examples of methods that can be performed by a wireless device, such as wireless device 110 or UE 200, are each described. For example, a wireless device can comprise processing circuitry, such as processing circuitry 120 or processor(s), configured to perform one or more steps of one or more of the methods performed by the wireless device. A network node, such as network node 160, can be configured to perform similar or reciprocal functionality. For example, certain embodiments describe a wireless device transmitting certain information to a network node. In reciprocal embodiments, the network node would receive that information from the wireless device. Similarly, certain embodiments describe a wireless device receiving certain information from a network node. In reciprocal embodiments, the network node would transmit that information to the wireless device. A network node can comprise processing circuitry, such as processing circuitry 170, configured to perform one or more steps of one or more of the methods performed by the network node. Figure 20 , Figure 21 and Figure 22 Examples of methods that can be performed by a network node to support functionality performed by wireless devices in Figure 17 , Figure 18 and Figure 19 , respectively, are provided.

[0820] Turning now to the methods of Figure 15A and Figure 15B , the methods begin with step 1502 of Figure 15A , in which system information broadcast from a network node is detected. The system information includes a list of NPN identifiers. The method continues to step 1504, in which a network index is generated based on the system information. Step 1504 can include one or more steps / sub-steps shown in Figure 15B . Because the system information received in step 1502 includes a list of NPN identifiers, the network index generated in step 1504 includes at least an NPN index. The NPN index can include a CAG index (e.g., an index including one or more CAG index values) and / or an NID index (e.g., an index including one or more NID index values). Further information regarding CAG indices can be found in the discussion of steps 1506 and 1508 of Figure 15B , and further information regarding NID indices can be found in the discussion of steps 1510 and 1512 of Figure 15B .

[0821] At step 1506, the method identifies whether the list of NPN identifiers includes at least one element / list entry that includes at least one CAG identifier. When the list of NPN identifiers does not include any element that includes at least one CAG identifier, the method can jump to step 1510 (no CAG index is generated). Alternatively, when the list of NPN identifiers includes at least one element that includes at least one CAG identifier, the method continues to step 1508, where a CAG index is generated to be included as at least part of the NPN index. The CAG index is based at least in part on a PLMN element that is included on the list of NPN identifiers in combination with at least one CAG identifier.

[0822] As an example, a CAG is identified by a PLMN ID and a CAG ID. In certain embodiments, CAGs associated with the same PLMN ID can be assigned the same CAG index value, e.g.:

[0823]

[0824] In the above example, it is the PLMN ID part of the PLMN ID + CAG ID pair that determines the index value. In this way, the core network selection can be based on the PLMN ID part only. Generating the index value based on the PLMN ID only can increase privacy associated with the CAG ID. Further examples are described above under the heading “CAG identifiers related to the same PLMN”. Note that in certain embodiments, a CAG can also be described as a PNI-NPN, and in certain embodiments, a CAG ID can correspond to a cag-IdentityList element.

[0825] In other embodiments, CAGs associated with the same PLMN ID can be assigned different CAG index values, e.g.:

[0826]

[0827] At step 1510, the method identifies whether the list of NPN identifiers includes at least one element that includes at least one NID. When the list of NPN identifiers does not include any element that includes at least one NID, the method does not need to generate any NID index (the method can skip step 1512). Alternatively, when the list of NPN identifiers includes at least one element that includes at least one NID, the method continues to step 1512, where a NID index is generated to be included as at least part of the NPN index. In certain embodiments, the NID index is based at least in part on the number of NIDs included in the list of NIDs, e.g.:

[0828]

[0829] Certain embodiments include a step of identifying whether the system information includes a PLMN identity list. Figure 15B This operation is shown in step 1514. The PLMN identity list contains public networks identified by PLMN ID. As noted above, the NPN identity list (containing a list of non-public networks) also uses PLMN IDs, as PLMN IDs are included in the SNPN and PNI-NPN identities of non-public networks. In certain embodiments, the method can determine whether the system information includes a PLMN identity list based on a parameter indicating whether the cell is NPN-only. As an example, the cellReservedForOtherUse parameter can be set to true when the cell is NPN-only, and set to false when the cell is not NPN-only. In response to detecting that the parameter indicates that the cell is an NPN-only cell, the method can skip step 1516. In response to detecting that the parameter indicates that the cell is not NPN-only, the method can continue to step 1516.

[0830] Step 1516 shows that, when the system information includes a PLMN identity list, the method generates an index value for at least the PLMN identities included as part of the network index. Thus, in certain embodiments, the network index includes an index value for each PLMN identity, and the network index also includes an NPN index. As noted above, the NPN index can include a CAG index (e.g., an index including one or more CAG index values) and / or an NID index (e.g., an index including one or more NID index values). When the network index includes a CAG index as well as index values for PLMN identities, certain embodiments arrange the CAG index to inherit the index values for the PLMN identities. When the network index includes an NID index as well as index values for PLMN identities, certain embodiments arrange the NID index to inherit the index values for the PLMN identities. When the network index includes both an NID index and a CAG index, certain embodiments arrange the NID index to inherit the CAG index. When the network index includes all three indices, certain embodiments arrange the NID index to inherit the CAG index, and arrange the CAG index to inherit the index values for the PLMN identities. Figure 16 An example is shown. Alternatively, in embodiments where a parameter (e.g., cellReservedForOtherUse) indicates that the cell is NPN-only, generating the network index includes assuming that no PLMN index precedes the CAG index or the NID index.

[0831] Turning to FIG. 15, the method continues to step 1518, where the network index is used. Certain embodiments use the network index during connection establishment to indicate the network that the wireless device requests access to. As an example, certain embodiments can indicate an index value of the network that the wireless device requests access to. Certain embodiments use the network index to determine a UAC parameter associated with the NPN. As an example, certain embodiments determine the UAC parameter based on an association between the index value and the UAC parameter.

[0832] Figure 15A and Figure 15B The steps of FIG. 15 can be performed in any suitable order. As an example, certain embodiments can perform the steps in the order shown by similar steps of Figure 2 FIG. 15.

[0833] As described above, in certain embodiments, a network node can be configured to perform similar or reciprocal functionality. For example, a network node can generate a network index associated with system information broadcast by the network node. The system information includes a list of NPN identifiers. The network index includes at least an NPN index. Generating the NPN index is based on steps 1506, 1508, 1510, and 1512 of Figure 15B In certain embodiments, generating the network index is further based on steps 1514 and 1516 of Figure 15B In this way, a network node can generate a network index according to the same rules as a wireless device to ensure that the network node and the wireless device use the same network index value to identify a particular network. As an example, a network node can use the network index during connection establishment to determine the network that the wireless device requests access to. As another example, a network node can use the network index to indicate one or more unified access control (UAC) parameters associated with an NPN to a wireless device.

[0834] Figure 17An example of a method that can be performed by a wireless device, such as wireless device 110 or UE 200, is shown in accordance with certain embodiments. In certain embodiments, the method detects a first system information broadcast at step 1702. The first system information broadcast includes a NPN list. The NPN list indicates a plurality of NPN identifiers. Each NPN identifier is associated with a respective network of a plurality of networks. The NPN identifier may, for example, identify a CAG (e.g., PNI-NPN) or a NID (e.g., SNPN). The method continues to step 1704, where a second system information broadcast is detected. The second system information broadcast includes a HRNN list. The HRNN list indicates a plurality of HRNNs. At step 1706, the method associates each HRNN of the second system information broadcast with a corresponding NPN identifier of the first system information broadcast. In certain embodiments, the association is based on a number of elements / list entries in the NPN list corresponding to a number of elements in the HRNN list. As an example, in certain embodiments, the association is based on an i-th element of the NPN list corresponding to an i-th element of the HRNN list. If there is no HRNN associated with a given NPN, the corresponding element in the HRNN list can be absent (e.g., a value corresponding to “no name” can be assigned to that element of the HRNN list). At step 1708, the method uses a HRNN corresponding to one of the NPN identifiers to identify a respective network associated with the one of the NPN identifiers.

[0835] Figure 18An example of a method that can be performed by a wireless device, such as wireless device 110 or UE 200, according to certain embodiments is shown. In certain embodiments, the method starts at step 1802, where it is determined whether a parameter received from a network node indicates that a cell is an NPN only cell. In certain embodiments, the parameter is the cellReservedForOtherUse parameter. The cellReservedForOtherUse parameter indicates that the cell is NPN only when set to true, and the cellReservedForOtherUse parameter indicates that the cell is not NPN only when set to false. The method continues to step 1804, where a network identity is selected based on whether the parameter indicates that the cell is an NPN only cell. When the parameter indicates that the cell is NPN only, the network identity is selected from a list of NPNs (e.g., NPN-IdentitylnfoList), and when the parameter indicates that the cell is not NPN only, the network identity is selected from a list of PLMNs (e.g., PLMN-IdentitylnfoList). In some embodiments, selecting the network identity from the list of NPNs includes selecting the first listed network identity on the list of NPNs, and selecting the network identity from the list of PLMNs includes selecting the first listed network identity on the list of PLMNs. In certain embodiments, the method further includes verifying system information already stored by the wireless device using the selected network identity, as shown in step 1806.

[0836] Figure 19 An example of a method that can be performed by a wireless device, such as wireless device 110 or UE 200, according to certain embodiments is shown. At step 1902, the method includes reading a first element / list entry from a list of PLMNs (e.g., PLMN-IdentitylnfoList). In response to detecting that the first element is indicative of no normal service available, the method continues to step 1904, where a network identity is selected from a list of NPNs (e.g., NPN-IdentitylnfoList). The method then continues to step 1906, where system information already stored by the wireless device is verified using the network identity. In certain embodiments, verifying the system information includes checking that the selected network identity matches a network identity associated with the stored copy of the system information.

[0837] Figure 20An example of a method performed by a network node according to certain embodiments is shown. The method starts in step 2002, where a first system information broadcast is transmitted. The first system information broadcast includes a NPN list. The NPN list indicates a plurality of NPN identifiers. Each NPN identifier is associated with a respective network of a plurality of networks. The method continues to step 2004, where a second system information broadcast is prepared. The second system information broadcast includes a HRNN list. The HRNN list indicates a plurality of HRNNs. The second system information broadcast is configured to enable a wireless device to associate each HRNN of the second system information broadcast with a corresponding NPN identifier of the first system information broadcast. The method continues to step 2006, where the second system information broadcast is transmitted. The method ends in step 2008, where a respective network associated with one of the NPN identifiers is identified using a HRNN corresponding to the one of the NPN identifiers. For example, the network node can send a message to the wireless device identifying a network by a HRNN, or the network node can receive a message from the wireless device identifying a network by a HRNN.

[0838] Figure 21 An example of a method performed by a network node according to certain embodiments is shown. The method starts in step 2102, where a parameter is transmitted to a wireless device. The parameter indicates that a cell is an NPN only cell. The method continues to step 2104, where a selection of a network identity is received from the wireless device, wherein the network identity is selected from a NPN list when the parameter indicates that the cell is NPN only, and the network identity is selected from a PLMN list when the parameter indicates that the cell is not NPN only.

[0839] Figure 22 An example of a method performed by a network node according to certain embodiments is shown. The method includes step 2202, sending a first element of a PLMN list to a wireless device, the first element of the PLMN list indicating that no normal service is available, thereby indicating that the wireless device is to select a network identity from a NPN list and use the network identity to validate system information already stored by the wireless device.

[0840] Figure 23An example of a method performed by a wireless device according to some embodiments is shown. The method begins at step 2302, where system information broadcast from a network node is detected. The system information includes a list of NPN identifiers identifying a plurality of non-public networks (NPNs). The method continues to step 2304, where a network is selected from the plurality of NPNs. The method then continues to step 2306, where an index value associated with the selected network is determined. The method can then use the index value to perform operations of the wireless device. As an example, certain embodiments use the index value to indicate to the network node that the wireless device requests access to the selected network during connection establishment. As another example, certain embodiments use the index value to determine a UAC parameter associated with the selected network. For example, the wireless device can receive a message from the network node including the UAC parameter and the index value, and can use the index value to associate the UAC parameter with the selected network.

[0841] Certain embodiments determine the index value in step 2306 based on whether the NPN identifier associated with the selected network includes a CAG identifier or an NID. When the NPN identifier associated with the selected network includes a CAG identifier, the index value is determined based at least in part on a PLMN identity included in the list of NPN identifiers in combination with the at least one CAG identifier. As an example, certain embodiments determine the index value based on using the same index value for all NPNs identified by a respective CAG identifier and associated with the same PLMN in the system information. The discussion above of FIG. 15 provides a table as an example (Example 1) where CAG Al and CAG A2 are each identified by a respective CAG identifier (CAG identifier 1 and CAG identifier 2, respectively), and CAG Al and CAG A2 are associated with the same PLMN (PLMN ID A), such that the index value would be the same (index value 1) for CAG Al and CAG A2.

[0842] Alternatively, determining the index value can be based on using different index values for each PLMN- CAG identifier pair (NPNs identified by different CAG identifiers will have different index values, regardless of whether they are associated with the same PLMN). The above discussion of FIG. 15 provides a table as an example (Example 2) in which CAG Al and CAG A2 are identified by different CAG identifiers (CAG identifier 1 and CAG identifier 2, respectively), and thus have different index values (index value 1 and index value 2, respectively), even though CAG Al and CAG A2 are associated with the same PLMN (PLMN ID A). CAG Bl also has a different index value (index value 3) because CAG Bl is associated with a different PLMN (PLMN ID B). That is, CAG identifier 1 associated with PLMN ID B is understood to be a different CAG identifier than CAG identifier 1 associated with PLMN ID A because it is associated with a different PLMN.

[0843] In certain embodiments, when the NPN identifier associated with the selected network includes an NID, determining the index value is based at least in part on a number of NIDs contained in the list of NPN identifiers. For example, certain embodiments determine the index value based on each NPN identified by a corresponding NID with its own index value based on system information. The above discussion of FIG. 15 provides a table as an example (Example 3) in which NID Al and NID A2 are identified by different NIDs (NID 1 and NID 2, respectively), and thus have different index values (index value 1 and index value 2, respectively), even though NID Al and NID A2 are associated with the same PLMN (PLMN ID A). NID Bl also has a different index value (index value 3) because NID Bl is associated with a different PLMN (PLMN ID B). That is, NID 1 associated with PLMN ID B is understood to be a different NID than NID 1 associated with PLMN ID A because it is associated with a different PLMN.

[0844] In certain embodiments, the wireless device supports different types of NPNs. The wireless device determines whether the NPN identifier associated with the selected network includes a CAG identifier or an NID, and then determines the index value accordingly. For example, the wireless device selects a network whose associated NPN identifier includes a CAG identifier during a first time period, and the wireless device selects a network whose associated NPN identifier includes an NID during a second time period. The second time period can occur before or after the first time period. During the first time period (when the NPN identifier associated with the selected network includes a CAG identifier), the wireless device determines the index value based at least in part on the PLMN identity included in combination with at least one CAG identifier in the list of NPN identifiers (see, e.g., the Example 1 table or the Example 2 table of FIG. 15), and during the second time period (when the NPN identifier associated with the selected network includes an NID), the wireless device determines the index value based at least in part on the number of NIDs included in the list of NPN identifiers (see, e.g., the Example 3 table of FIG. 15). Certain embodiments determine the index value for the first time period based on using the same index value for all NPNs identified by a respective CAG identifier and associated with the same PLMN in the system information, and determine the index value for the second time period based on each NPN identified by a respective NID in the system information having its own index value.

[0845] Certain embodiments can generate a network index (such as the network index in Figure 16 The index value associated with the selected network (the index value determined in step 2306) can be determined based on the network index. As an example, the index value associated with the selected network (i) can be determined to correspond to the i-th index value in the network index. In certain embodiments, the lower layers of the wireless device can read the SIB and can report the available PLMNs, CAGs, and / or NIDs to the higher layers of the wireless device. The higher layers of the wireless device can then select one of the networks. For example, if the wireless device selects to use an NPN, the wireless device can select a PLMN-CAG ID or a PLMN-NID combination. Based on this selection, the lower layers of the wireless device will calculate the corresponding index value for the selected network. To be able to accurately calculate the index value for the selected network, the wireless device will take into account the other available networks. In other words, the wireless device generates the network index at least in the sense that the wireless device takes into account the other available networks when calculating the index value associated with the selected network. In this way, the wireless device is able to increment the index value when appropriate (e.g., to avoid using the same index value for two networks that intend to use different index values).

[0846] In embodiments, generating the network index includes determining whether the system information includes a list containing one or more PLMN identities (meaning its own PLMN identity, such as in combination with a PLMN-CAG ID or a PLMN-NID) and including one or more index values for the one or more PLMN identities in the network index when the system information includes the list containing one or more PLMN identities; determining whether the list of NPN identifiers includes a list containing one or more CAG identifiers (including a PLMN-CAG ID combination) and including one or more index values for the one or more CAG identifiers in the network index when the list of NPN identifiers includes the list containing one or more CAG identifiers (as described above, in certain embodiments, CAG identifiers associated with the same PLMN can have the same index value); and determining whether the list of NPN identifiers includes a list containing one or more NIDs (including a PLMN-NID combination) and including one or more index values for the one or more NIDs in the network index when the list of NPN identifiers includes the list containing one or more NIDs. In certain embodiments, the wireless device detects a parameter indicating that the cell is an NPN-only cell and, in response, generates the network index, assuming that there are no index values for PLMN identities to include in the network index. In certain embodiments, the network index can be generated prior to step 2306 and the determining of the index value in step 2306 can be based on using the network index to obtain an association between the selected network and its index value. For example, to determine the index value (i) for the selected network, the wireless device can obtain the i-th index value of the network index.

[0847] Figure 24 An example of a method performed by a network node is shown. In general, Figure 24 The steps of Figure 23 may be similar / mutual with the steps performed by a wireless device in The method begins at step 2402, where system information is broadcast, the system information including a list of NPN identifiers identifying a plurality of non-public networks (NPNs). The method continues to step 2404, where index values are determined that are associated with networks of the plurality of NPNs. In certain embodiments, the method uses the index values to perform operations of the network node. As an example, certain embodiments determine that a wireless device requests access to a network based on receiving an index value associated with the network from the wireless device during connection setup. The network node can then facilitate a connection with the network. As another example, certain embodiments transmit a UAC parameter having an index value associated with the network in order to indicate that the UAC parameter is associated with the network.

[0848] Certain embodiments determine the index value in step 2404 based on whether the NPN identifier associated with the network includes a CAG identifier or an NID. When the NPN identifier associated with the network includes a CAG identifier, the index value is determined based at least in part on the PLMN identity included in the list of NPN identifiers in combination with the at least one CAG identifier. As an example, the index value is determined based on using the same index value for all NPNs identified by a respective CAG identifier and associated with the same PLMN in the system information. The discussion above for FIG. 15 provides a table as an example (Example 1) (e.g., for Figure 23 further explanation). Alternatively, the index value can be determined based on using a different index value for each PLMN identity-CAG identifier pair (NPNs identified by different CAG identifiers will have different index values regardless of whether they are associated with the same PLMN). The discussion above for FIG. 15 provides a table as an example (Example 2) (e.g., for Figure 23 further explanation).

[0849] In certain embodiments, when the NPN identifier associated with the network includes an NID, the index value is determined based at least in part on the number of NIDs included in the list of NPN identifiers. For example, certain embodiments determine the index value based on each NPN identified by a respective NID in the system information with its own index value. The discussion above for FIG. 15 provides a table as an example (Example 3) (e.g., for Figure 23 further explanation).

[0850] In certain embodiments, the network node supports different types of NPNs. For example, the network node determines whether the NPN identifier associated with a network selected by a wireless device includes a CAG identifier or an NID, and then determines the index value accordingly. For example, the NPN identifier associated with a network selected during a first time period can include a CAG identifier, and the NPN identifier associated with a network selected during a second time period can include an NID. The second time period can occur before or after the first time period. During the first time period (when the NPN identifier associated with the selected network includes a CAG identifier), the network node determines the index value based at least in part on the PLMN identity included in the list of NPN identifiers in combination with at least one CAG identifier (see, e.g., Example 1 table or Example 2 table of FIG. 15), and during the second time period (when the NPN identifier associated with the selected network includes an NID), the network node determines the index value based at least in part on the number of NIDs included in the list of NPN identifiers (see, e.g., Example 3 table of FIG. 15). Certain embodiments determine the index value for the first time period based on using the same index value for all NPNs identified by a respective CAG identifier and associated with the same PLMN in the system information, and determine the index value for the second time period based on each NPN identified by a respective NID in the system information having its own index value.

[0851] With Figure 23 Similar to the method performed by the wireless device in Figure 24 Certain embodiments of the method performed by the network node in Figure 16 Examples of the network index are shown. If the cell is an NPN-only cell, the network index need not include an index value associated with any PLMN identity (meaning its own PLMN identity, as opposed to being combined with a PLMN-CAG ID or PLMN-NID). Certain embodiments transmit a parameter indicating that the cell is an NPN-only cell, thereby indicating to the wireless device that there is no index value of a PLMN identity to include in the network index.

[0852] Certain embodiments can store the network index, and later use the network index when the network node needs to determine the association between an index value and a network. For example, when the network node receives an index value in a connection request from a wireless device, the network node can use the network index to determine the requested network (i.e., the network associated with the index value). As another example, when the network node is preparing to transmit UAC parameters for a particular network, the network node can use the network index to determine the index value associated with that network. The network node can then provide the index value when transmitting the UAC parameters, in order to indicate that the UAC parameters are for the particular network.

[0853] Modifications, additions, or omissions can be made to the systems and apparatuses described herein without departing from the scope of the disclosure. The components of the systems and apparatuses can be integrated or separated. Moreover, the operations of the systems and apparatuses can be performed by more, fewer, or other components. Additionally, operations of the systems and apparatuses can be performed using any suitable logic comprising software, hardware, and / or other logic. As used in this document, "each" refers to each member of a set or each member of a subset of a set.

[0854] Modifications, additions, or omissions can be made to the methods described herein without departing from the scope of the disclosure. The methods can include more, fewer, or other steps. Additionally, steps can be performed in any suitable order.

[0855] While the disclosure has been described in terms of certain embodiments, alterations and permutations of the embodiments will be apparent to those skilled in the art. Accordingly, the above description of the embodiments does not restrict the disclosure. Other changes, modifications, and variations can be made to the methods and apparatuses described herein without departing from the scope of the present disclosure as defined in the following claims.

Claims

1. A wireless device (110, 200), the wireless device comprising: A power supply circuit (137, 213) is configured to supply power to the wireless device; as well as Processing circuits (120, 201), the processing circuits being configured to: Detect system information broadcast from network nodes, the system information including a list of NPN identifiers that identify multiple non-public network NPNs; Select a network from the plurality of NPNs; as well as Determine the index value associated with the selected network, where: When the NPN identifier associated with the selected network includes a Closed Access Group (CAG) identifier, the index value is determined based at least in part on a Public Land Mobile Network (PLMN) identifier, which is included in the list of NPN identifiers in combination with at least one CAG identifier. or When the NPN identifier associated with the selected network includes a network identifier (NID), the index value is determined based at least in part on the number of NIDs contained in the list of NPN identifiers.

2. The wireless device as claimed in claim 1, wherein, The NPN identifier associated with the selected network includes a CAG identifier, and the index value is determined based on using the same index value for all NPNs identified by the corresponding CAG identifier and associated with the same PLMN in the system information.

3. The wireless device as claimed in claim 1, wherein, The NPN identifier associated with the selected network includes the NID, and each NPN is identified based on the system information through its corresponding NID, which has its own index value.

4. The wireless device according to any one of claims 1-3, wherein the processing circuit is further configured to: The index value is used during connection establishment to instruct the wireless device to request access to the selected network; or The index value is used to determine the Unified Access Control (UAC) parameters associated with the selected network.

5. The wireless device according to any one of claims 1-3, wherein the processing circuit is further configured to: A network index is generated based on the system information, wherein, in order to generate the network index, the processing circuit is configured to: Determine whether the system information includes a list containing one or more PLMN identifiers, and when the system information includes the list containing one or more PLMN identifiers, include one or more index values ​​of the one or more PLMN identifiers in the network index; Determine whether the list of NPN identifiers includes a list containing one or more CAG identifiers, and when the list of NPN identifiers includes a list containing one or more CAG identifiers, include one or more index values ​​of the one or more CAG identifiers in the network index; and Determine whether the list of NPN identifiers includes a list containing one or more NIDs, and when the list of NPN identifiers includes the list containing one or more NIDs, include one or more index values ​​of the one or more NIDs in the network index; The index value associated with the selected network is determined based on the network index.

6. The wireless device of claim 5, wherein the processing circuit is further configured to: The detection indicates that the cell is an NPN cell-only parameter, and in response, the network index is generated, assuming that there is no index value for the PLMN identifier to be included in the network index.

7. A method in a wireless device, the method comprising: Detect (2302) system information broadcast from the network node, the system information including a list of NPN identifiers that identify multiple non-public network NPNs; Select network (2304) from the plurality of NPNs; as well as Determine (2306) the index value associated with the selected network, where: When the NPN identifier associated with the selected network includes a Closed Access Group (CAG) identifier, the index value is determined based at least in part on a Public Land Mobile Network (PLMN) identifier, which is included in the list of NPN identifiers in combination with at least one CAG identifier. or When the NPN identifier associated with the selected network includes a network identifier (NID), the index value is determined based at least in part on the number of NIDs contained in the list of NPN identifiers.

8. The method of claim 7, wherein, The NPN identifier associated with the selected network includes a CAG identifier, and the index value is determined based on using the same index value for all NPNs identified by the corresponding CAG identifier and associated with the same PLMN in the system information.

9. The method of claim 7, wherein, The NPN identifier associated with the selected network includes the NID, and each NPN is identified based on the system information through its corresponding NID, which has its own index value.

10. The method according to any one of claims 7-9, further comprising: The index value is used during connection establishment to indicate that the wireless device requests access to the selected network; or The index value is used to determine the Unified Access Control (UAC) parameters associated with the selected network.

11. A network node (160), the network node comprising: A power supply circuit (187) is configured to supply power to the network node; as well as Processing circuit (170), the processing circuit being configured to: Broadcast system information, which includes a list of NPN identifiers that identify multiple non-public network NPNs; as well as Determine the index value associated with the network of the plurality of NPNs, wherein: When the NPN identifier associated with the network includes a Closed Access Group (CAG) identifier, the index value is determined based at least in part on a Public Land Mobile Network (PLMN) identifier, which is included in the list of NPN identifiers in combination with at least one CAG identifier. or When the NPN identifier associated with the network includes a network identifier (NID), the index value is determined based at least in part on the number of NIDs contained in the list of NPN identifiers.

12. The network node as described in claim 11, wherein, The NPN identifier associated with the network includes the CAG identifier, and the index value is determined based on using the same index value for all NPNs identified by the corresponding CAG identifier and associated with the same PLMN in the system information.

13. The network node as described in claim 11, wherein, The NPN identifier associated with the network includes the NID, and each NPN is identified based on the system information through its corresponding NID, which has its own index value.

14. The network node according to any one of claims 11-13, wherein the processing circuitry is further configured to: The wireless device's request for access to the network is determined based on the index value associated with the network received from the wireless device during connection establishment; or Transmit unified access control (UAC) parameters having the index value associated with the network to indicate that the UAC parameters are associated with the network.

15. The network node of any one of claims 11-13, wherein the processing circuitry is further configured to generate a network index based on the system information, wherein: When the system information includes a list containing one or more PLMN identifiers, the network index includes one or more index values ​​of the one or more PLMN identifiers; When the list of NPN identifiers includes a list containing one or more CAG identifiers, the network index includes one or more index values ​​of the one or more CAG identifiers; and When the list of NPN identifiers includes a list containing one or more NIDs, the network index includes one or more index values ​​including the one or more NIDs; The index value associated with the network is determined based on the network index.

16. The network node according to any one of claims 11-13, wherein the processing circuitry is further configured to: The transmission indication cell is a parameter of the NPN cell only, thereby indicating to the radio device that there is no index value for the PLMN identifier to be included in the network index.

17. A method in a network node, the method comprising: Broadcast (2402) system information, which includes a list of NPN identifiers that identify multiple non-public network NPNs; as well as Determine (2404) the index value associated with the network of the plurality of NPNs, wherein: When the NPN identifier associated with the network includes a Closed Access Group (CAG) identifier, the index value is determined based at least in part on a Public Land Mobile Network (PLMN) identifier, which is included in the list of NPN identifiers in combination with at least one CAG identifier. or When the NPN identifier associated with the network includes a network identifier (NID), the index value is determined based at least in part on the number of NIDs contained in the list of NPN identifiers.

18. The method of claim 17, wherein, The NPN identifier associated with the network includes the CAG identifier, and the index value is determined based on using the same index value for all NPNs identified by the corresponding CAG identifier and associated with the same PLMN in the system information.

19. The method of claim 17, wherein, The NPN identifier associated with the network includes the NID, and each NPN is identified based on the system information through its corresponding NID, which has its own index value.

20. The method according to any one of claims 17-19, further comprising: The wireless device's request for access to the network is determined based on the index value associated with the network received from the wireless device during connection establishment. or Transmit unified access control (UAC) parameters having the index value associated with the network to indicate that the UAC parameters are associated with the network.

Images