Method of broadcast and index generation in ue

Abstract

According to some embodiments, a method in a wireless device includes detecting system information broadcast from a network node. The system information includes a list of NPN identifiers identifying a plurality of non-public networks (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, the index value is determined based at least in part on a Public Land Mobile Network (PLMN) element, which is 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 the number of NIDs included in the list of NPN identifiers.

Description

Background Technology

[0001] The 3rd Generation Partnership Project (3GPP) is currently working on the specifications commonly referred to as "5G" or "fifth generation." This work outlines various requirements and proposes various solutions. For example, solutions exist for connecting new radio access to a new core network. New radio access is commonly referred to as "NR" (New Radio). The new core network is commonly referred to as the "5G core network" or simply "5GC." The term "5G system," or simply "5GS," is sometimes used to refer to the complete system.

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

[0003] 5G systems are often referred to as “public systems,” that is, Public Land Mobile Networks (PLMNs). This means that anyone can obtain a subscription and access to the network. This contrasts with some other networks that can only be accessed by specific UEs and for which access subscriptions / credentials are not easily obtained. One such example of a “private” network is a Wi-Fi router deployed as an extension of a private broadband connection, such as a broadband subscription over fiber, xDSL (“digital subscriber line,” where “x” is a wildcard that can represent the type of DSL, such as asynchronous DSL or synchronous DSL), or a similar connection. For this purpose, not just anyone can obtain access. This is a type of private network. Private networks are also called “non-public networks” or simply “NPNs.”

[0004] While Wide Area Networks (WLANs) are a different type of access than 5G, there is currently activity related to the possibility of deploying NPNs that also use 5G access and 5G core networks. The goal may not be entirely to correspond to home Wi-Fi access points, but rather to, for example, deploying NPNs in factories, potentially connecting factory equipment, vehicles, and employees. These types of deployments can impose entirely different requirements. As an example, these types of networks may have different security requirements. As another example, these types of networks may have different roaming requirements—in some cases, roaming (i.e., to seamlessly transfer connections from a private network to a "public" network) can be important. In other cases, roaming should certainly not be supported. One example, however, is that the connected machinery should preferably operate only within a private network and not be able to connect, for example, through any other access point / cell or gNB ("gNB" stands for base station in NR).

[0005] 3GPP has set requirements for how NPN should work and has conducted studies on how to meet those requirements. The requirements are described in 3GPP document 22.261 (v16.6.0) and are reproduced below: * ~ * ~ * ~ *~ *~ *~ *~ *~ *~ *~ *~ *~ *~ *~ *~ *~ *~ *~ *~ *~ *~ *~ *~ *~ *~ *~ *~ Non-public networks are intended for use only by private entities, such as enterprises, and can be deployed in a variety of configurations, leveraging both virtual and physical elements. Specifically, they can be deployed as completely independent networks, they can be hosted by a PLMN, or they can be provided as slices of a PLMN.

[0006] In any of these deployment options, it is anticipated that unauthorized UEs (those not associated with the enterprise) will not attempt to access non-public networks, which could result in resources being used to deny that UE and thus make it unavailable to enterprise UEs. It is also anticipated that enterprise UEs will not attempt to access networks they are not authorized to access. For example, some enterprise UEs may be restricted to accessing only the enterprise's non-public networks, even if PLMN coverage is available in the same geographic area. In exceptionally permitted circumstances, other enterprise UEs may be able to access both non-public networks and the PLMN.

[0007] 6.25.2 Requirements 5G systems should support non-public networks.

[0008] 5G systems should support non-public networks that provide coverage within specific geographic areas.

[0009] 5G systems should support both physical and virtual non-public networks.

[0010] 5G systems should support the independent operation of non-public networks, meaning that non-public networks can operate without being associated with a PLMN.

[0011] Subject to agreements between operators and service providers, operator policies, and regional or national regulatory requirements, 5G systems should support subscribers of non-public networks. - Access to subscribed PLMN services via non-public networks; - Seamless service continuity of PLMN services subscribed between non-public networks and PLMNs; - Access to selected non-public network services via PLMN; - Seamless service continuity of non-public network services between the non-public network and the PLMN.

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

[0013] 5G systems should support mechanisms for UEs to identify and select non-public networks.

[0014] Note: Different network selection mechanisms can be used for both physical and virtual non-public networks.

[0015] 5G systems should support a large number of non-public network identifiers to minimize the likelihood of conflict between assigned identifiers.

[0016] 5G systems should support a mechanism that prevents UEs with subscriptions to non-public networks from automatically selecting and attaching to PLMNs or non-public networks that have not been authorized for selection.

[0017] 5G systems should support a mechanism that prevents UEs with subscriptions to PLMNs from automatically selecting and attaching to non-public networks that they have not been authorized to select.

[0018] The 5G system should support a host in a non-public network to change from one PLMN to another without changing the network selection information stored in the UE in the non-public network.

[0019] * ~ * ~ * ~ *~ *~ *~ *~ *~ *~ *~ *~ *~ *~ *~ *~ *~ *~ *~ *~ *~ *~ *~*~ The requirements have been studied, and two different solutions exist that have been standardized.

[0020] Integrating non-public networks via PLMN's public network (PNI-NPN) PNI-NPN becomes available via PLMN by allocating one or more network slices or data networks to a non-public network. Since network slices cannot prevent a UE from attempting to access a network in an area where the UE is not permitted to use a network slice, the use of Closed Access Groups (CAGs) can also be used to apply additional access control in addition to network slices. In this case, PNI-NPN is identified by a combination of PLMN ID and CAG ID, where the CAG ID is unique within the PLMN, or at least the cell used for PNI-NPN is identified by both PLMN ID and CAG ID (i.e., the actual NPN can be identified by other means in dedicated signaling, such as network slice ID). Optionally, in the case of manual CAG selection, a Human-readable Network Name (HRNN) can also be provided to assist the user. The HRNN should support the manual network selection process. It is not necessary to associate the CAG with a specific data network or slice; it is entirely possible to use a CAG associated with the same slice used in the absence of a CAG.

[0021] Independent NPN (SNPN) SNPNs operate without PLMN association and are identified by a combination of PLMN ID and Network ID (NID). Unlike the PLMN ID used by the PLMN, the PLMN ID used by an SNPN is not required to be unique; that is, two SNPNs may share the same PLMN ID. For example, PLMN IDs reserved for private networks based on the Mobile Country Code (MCC) 999 assigned by the International Telecommunication Union (ITU) can be used in non-public networks. NIDs can be seen as an extension of PLMN IDs and support different assignment models. For example, - It is assumed that the locally managed NID is selected separately by the SNPN at deployment time (and therefore may not be unique in all cases); - The NIDs managed by the general administration are managed by a central entity in each region and are assumed to be globally unique.

[0022] Similar to PNI-NPN, HRNN can optionally be provided to help users identify SNPN during manual network selection.

[0023] As can be seen from the above, the identifiers used by PNI-NPN and SNPN are similar. SNPN uses PLMNID+NID, while PNI-NPN uses PLMN ID+CAG ID. Other differences are that SNPN can use PLMN IDs reserved for private use, while PNI-NPN uses the PLMN ID of its hosted PLMN, i.e., the public PLMN ID.

[0024] Therefore, the principle of the SNPN / NID solution is: - The combination of PLMN ID and NID identifies SNPN; - NID can be globally unique or locally managed; - NG-RAN nodes support broadcasting a total of twelve NIDs; - Optional human-readable network name per NID for manual selection; - Optional: Prevent cell broadcast information from UEs that do not support SNPN from accessing the cell; - When the UE is configured to operate in SNPN access mode, the UE only selects and registers with SNPN; - The UE provides the PLMN ID and NID as the selected PLMN, and the NG-RAN provides the PLMN ID and NID to the 5GC as the selected PLMN; - The Access and Mobility Management Function (AMF) performs access control and rejects the UE if the UE does not have an SNPN subscription; - Configure unified access control (UAC) information for each non-public network.

[0025] The NID is used in conjunction with the PLMN ID during network selection and is therefore considered an extension of the network identifier (i.e., the PLMNID). This can be understood from the statement: "UEs operating in SNPN access mode select only the cell and network for which both the PLMN ID and NID of the broadcast SNPN are selected."

[0026] The PNI-NPN / CAG solution works by using existing functionalities (such as network slicing) to deploy NPN within a public network, and additionally, for access control purposes, using closed access groups as described below: - Each CAG cell broadcasts 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 broadcasts a human-readable network name per CAG identifier; - PLMN / network selection is performed using the PLMN ID, and within the selected PLMN, allowed cells are determined using the allowed CAG list and optional indications regarding allowing only UE access to CAG cells. Cell selection / reselection is then performed using CAG information and knowledge of whether the UE has been provided with an indication of CAG-only access. Cell selection can also be performed on non-CAG, non-SNPN cells of the selected PLMN-ID.

[0027] Since multiple CAG identifiers can exist 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 via N2; - Extend mobility restrictions (for UEs in NAS and NG-RAN via N2) by using an allowed CAG list and indications on whether only UEs are allowed to access CAG cells; and - The CAG cell should broadcast information so that only UEs that support CAG are accessing the cell (i.e., the cell is a CAG cell or a normal PLMN cell).

[0028] Some features of the solution include allowing PLMN operators to manage their networks and the identifiers they use without external registration, as the CAG is defined within the scope of the PLMN ID.

[0029] In defining the new network type as described above, some form of broadcasting is required, enabling the UE to obtain information about which networks are supported in the cell. This is typically done by the RAN sending broadcast information. In systems based on 3GPP NR and 5G system standards, the networks are usually listed in a message called System Information Block 1 (SIB1).

[0030] SIB 1 includes information such as whether a cell is accessible or blocked, whether the cell supports emergency services, and whether there are any restrictions on what the UE can access. Another information element included is a list of supported PLMNs. This list also provides the opportunity to assign specific cell identifiers (CellIdentity), Tracking Area Codes (TACs), and Ran Area Codes (RANACs) to different PLMNs or networks. In the 3GPP Technical Specification (TS) 38.331 standard, the information element (IE) that includes such a list of networks or PLMNs is called cellAccessRelatedInfo, and it is included in SIB 1. The following excerpt from the specification describes the cellAccessRelatedInfo information element: CellAccessRelatedInfo IE CellAccessRelatedInfo indicates cell access-related information for this cell.

[0031] CellAccessRelatedInfo information element -- ASN1START -- TAG-CELLACCESSRELATEDINFO-START CellAccessRelatedInfo ::= SEQUENCE { plmn-IdentityList PLMN-IdentityInfoList, cellReservedForOtherUse ENUMERATED {true} OPTIONAL,--Need R ... } -- TAG-CELLACCESSRELATEDINFO-STOP -- ASN1STOP Currently, there is a recommendation that NPNs should be listed in a separate information element. This is as follows: – CellAccessRelatedInfo IE CellAccessRelatedInfo indicates cell access-related information for this cell.

[0032] CellAccessRelatedInfo information element -- ASN1START -- TAG-CELLACCESSRELATEDINFO-START CellAccessRelatedInfo ::= SEQUENCE { plmn-IdentityList PLMN-IdentityInfoList, cellReservedForOtherUse ENUMERATED {true} OPTIONAL,--Need R ..., [[ cellReservedForFutureUse-r16 ENUMERATED {true}OPTIONAL, --Need R NPN-IdentityInfoList-r16 NPN-IdentityInfoList-r16OPTIONAL -- Need R ]] } -- TAG-CELLACCESSRELATEDINFO-STOP -- ASN1STOP Editor's Note: The definition of the network index of NPN requires further research (FFS).

[0033] The next amendment sub-clause (new information element in 6.3.2) NPN-Identity The IE NPN-Identity includes a list of NIDs or CAG-IDs for each PLMN. Further information regarding how to configure the IE is specified in TS 23.003

[21] .

[0034] NPN-Identity Information Element -- ASN1START -- TAG-NPN-IDENTITY-START NPN-Identity-r16 ::= CHOICE { pni-npn-r16 SEQUENCE { plmn-Identity-r16 PLMN-Identity, cag-IdentityList-r16 SEQUENCE (SIZE (1..maxNPN-r16)) OF CAG-Identity-r16 }, snpn-r16 SEQUENCE { plmn-Identity PLMN-Identity, nid-List-r16 SEQUENCE (SIZE (1..maxNPN-r16)) OF NID-r16 } } CAG-Identity-r16 ::= BIT STRING (SIZE (32)) NID-r16 ::= BIT STRING (SIZE (52)) -- TAG-NPN-IDENTITY-STOP -- ASN1STOP Editor’s Note: (1) The size of NID will be verified based on the CT4 protocol, (2) The need for a list of NIDs depends on the RAN sharing scenario to be supported, and (3) Whether all CAG identifiers associated with the same PLMN identifier should be listed in the same cag-IdentityList needs further investigation.

[0035] The next change (new information element in 6.3.2) NPN-IdentityInfoList The IE NPN-IdentityInfoList contains a list of NPN identification information.

[0036] NPN-IdentityInfoList information elements -- ASN1START -- TAG-NPN-IDENTITYINFOLIST-START NPN-IdentityInfoList-r16 ::= SEQUENCE (SIZE (1..maxNPN-r16)) OF NPN-IdentityInfo-r16 NPN-IdentityInfo-r16 ::= SEQUENCE { NPN-IdentityList-r16 SEQUENCE (SIZE (1..maxNPN-r16)) OF NPN-Identity-r16, trackingAreaCode-r16 TrackingAreaCode, ranac-r16 RAN-AreaCode OPTIONAL, --Need R CellIdentity-r16 CellIdentity, cellReservedForOperatorUse-r16 ENUMERATED {reserved,notReserved}, ... } -- TAG-NPN-IDENTITYINFOLIST-STOP -- ASN1STOP As can be seen above, NPN identifiers are introduced into the independent network list (i.e., NPN-IdentityInfoList in cellAccessRelatedInfo). In this way, broadcast information (SIB1) can indicate to the listening UE whether the cell represented by SIB1 supports access for various NPN network identifiers. Summary of the Invention

[0037] There are currently some challenges. For example, when a UE signals which network, PLMN, or NPN it wants to access, it does so during a process called Radio Resource Control (RRC) establishment. This process is detailed in TS38.331 and consists of the exchange of three RRC messages between the UE and the network. The three messages... Figure 1 This is shown in the diagram. Note that there are actually more messages hidden in this diagram, but they have been omitted for the purpose of focusing on the RRC layer. The reason for mentioning this is that RRCSetupRequest is sometimes called msg3 (as in message 3), and RRCSetupComplete is called msg5 (or message 5). These msg3 and msg5 references need to be read in context, although msg5 can be other messages in other processes, such as the recovery completion message.

[0038] The RRC Establishment Request message is a very short message, including the UE identifier or reference and the establishment reason value (i.e., the reason for access). The RRC Establishment message includes information from the network regarding the radio bearer configuration, and the RRC Establishment Complete message includes further details about which network the UE wants to access. Specifically, this message includes a reference to the network the UE wants to access. This indication is not explicit; although it is not the complete PLMN ID, it represents an index of the list of PLMNs included in the SIB1 message.

[0039] In the PLMN standard, the PLMN-IdentityInfoList, which includes the PLMNs that the UE can access, is used as input for generating the PLMN-Index, such as: For the PLMN contained in the nth entry of PLMN-IdentityInfoList and the ith 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.

[0040] in – PLMN-Identity The IE PLMN-Identity identifies the public terrestrial mobile network. Further information regarding how to configure the IE is specified in TS 23.003

[21] .

[0041] PLMN-Identity Information Element -- ASN1START -- TAG-PLMN-IDENTITY-START PLMN-Identity ::= SEQUENCE { mcc MCC OPTIONAL,-- Cond MCC mnc MNC } MCC ::= SEQUENCE (SIZE (3)) OF MCC-MNC-Digit MNC ::= SEQUENCE (SIZE (2..3)) OF MCC-MNC-Digit MCC-MNC-Digit ::= INTEGER (0..9) -- TAG-PLMN-IDENTITY-STOP -- ASN1STOP – PLMN-IdentityInfoList The IE PLMN-IdentityInfoList contains a list of PLMN identification information.

[0042] PLMN-IdentityInfoList information element -- ASN1START -- TAG-PLMN-IDENTITYINFOLIST-START PLMN-IdentityInfoList ::= SEQUENCE (SIZE (1..maxPLMN)) OF PLMN-IdentityInfo PLMN-IdentityInfo ::= SEQUENCE { plmn-IdentityList SEQUENCE (SIZE (1..maxPLMN)) OF PLMN-Identity, trackingAreaCode TrackingAreaCodeOPTIONAL, -- Need R ranac RAN-AreaCode OPTIONAL, --Need R CellIdentity CellIdentity, cellReservedForOperatorUse ENUMERATED {reserved,notReserved}, ... } -- TAG-PLMN-IDENTITYINFOLIST-STOP -- ASN1STOP The rule applies to only one list for obvious reasons, since the principle of UE index generation only extends to PLMN.

[0043] There is currently no solution on how to generate indexes for NPN.

[0044] Certain aspects of this disclosure and its embodiments may provide solutions to these or other problems. Generally, certain embodiments of this disclosure provide solutions for deploying non-public networks and for broadcasting and network index generation by the network and UEs in such networks.

[0045] In one aspect of this 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 effective for signaling intent regarding access to a non-public network.

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

[0047] This document presents various embodiments that address one or more of the problems disclosed herein.

[0048] According to some embodiments, a wireless device includes a power supply circuit and a processing circuit, the power supply circuit being configured to supply power to the wireless device. The processing circuit is configured to detect system information broadcast from a network node. The system information includes a list of NPN identifiers identifying a plurality of non-public networks (NPNs). The processing circuit 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) identifier, which is 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 the number of NIDs included in the list of NPN identifiers.

[0049] According to some embodiments, a method in a wireless device includes detecting system information broadcast from a network node. The system information includes a list of NPN identifiers identifying a plurality of non-public networks (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, 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. 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 included in the list of NPN identifiers.

[0050] According to some embodiments, a network node includes a power supply circuit configured to supply power to the network node. The network node further includes processing circuitry configured to broadcast system information and determine index values ​​associated with 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, 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. 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 included in the list of NPN identifiers.

[0051] According to some 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, 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. 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 included in the list of NPN identifiers.

[0052] According to some embodiments, a wireless device includes a power supply circuit and a processing circuit, the power supply circuit being configured to supply power to the wireless device. The processing circuit is configured to detect first system information broadcast from a network node. The first system information includes a plurality of NPN elements identifying a plurality of non-public networks (NPNs). The processing circuit is also configured to detect second system information broadcast from the network node. The second system information includes a plurality of human-readable network name (HRNN) elements. Each HRNN element corresponds to a corresponding NPN element in the first system information, and each HRNN element indicates name information. The name information includes the HRNN associated with the corresponding NPN, or, if the second system information does not include any HRNN associated with the corresponding NPN, includes a "no name" indicator. The processing circuit 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 the i-th NPN element corresponding to the i-th HRNN element. The processing circuit is configured to use the HRNN corresponding to one of the NPN elements to identify the corresponding NPN associated with said one of the NPN elements.

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

[0054] According to some embodiments, a network node includes a power supply circuit and processing circuitry. The power supply circuit is configured to supply power to the network node. The processing circuit is configured to transmit first system information and second system information. The first system information includes a plurality of NPN elements identifying a plurality of non-public networks (NPNs). The second system information includes a plurality of human-readable network name (HRNN) elements, each HRNN element corresponding to a corresponding NPN element in the first system information, such that the i-th NPN element corresponds to the i-th HRNN element. Each HRNN element indicates name information. The name information includes the HRNN associated with the corresponding NPN, or, if the second system information does not include any HRNN associated with the corresponding NPN, includes a "no name" indicator. The processing circuit is further configured to use the HRNN corresponding to one of the NPN elements to identify the corresponding NPN associated with said one of the NPN elements.

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

[0056] According to some embodiments, a wireless device includes: a power supply circuit configured to supply power to the wireless device; and a processing circuit configured to detect system information broadcast from a network node. The system information includes a list of Non-Public Network (NPN) identifiers. The processing circuit is further configured to generate a network index based on the system information. The network index includes at least an NPN index. To generate the network index, the processing circuit is further configured to identify whether the list of NPN identifiers includes at least one element, said at least one element including at least one Closed Access Group (CAG) identifier, and when the list of NPN identifiers includes at least one element, said at least one element including at least one CAG identifier, generate a CAG index to be included as at least a portion of the NPN index. The CAG index is at least partially based on the number of Public Land Mobile Network (PLMN) elements, said PLMN elements being included in the list of NPN identifiers in combination with at least one of one or more CAG identifiers. To generate the network index, the processing circuitry is further configured to identify whether the list of NPN identifiers includes at least one element, said at least one element including at least one network identifier (NID), and when the list of NPN identifiers includes at least one element, said at least one element including at least one NID, to generate an NID index to be included as at least a portion of the NPN index. The NID index is at least partially based on the number of NIDs included in the list of NIDs.

[0057] According to some embodiments, a wireless device includes: a power supply circuit configured to supply power to the wireless device; and a processing circuit configured to detect a first system information broadcast. The first system information broadcast includes a list of non-public networks (NPNs). The NPN list indicates a plurality of NPN identifiers, each NPN identifier being associated with a corresponding network of the plurality of networks. The processing circuit is further configured to detect a second system information broadcast. The second system information broadcast includes a list of human-readable network names (HRNNs). The HRNN list indicates a plurality of HRNNs. The processing circuit 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 to use the HRNN corresponding to one of the NPN identifiers to identify the corresponding network associated with said one of the NPN identifiers.

[0058] According to some embodiments, the wireless device includes: a power supply circuit configured to supply power to the wireless device; and a processing circuit configured to determine whether parameters received from a network node indicate that the cell is a non-public network only (NPN) cell, and to select a network identifier. When the parameters indicate that the cell is NPN only, a network identifier is selected from an NPN list, and when the parameters indicate that the cell is not NPN only, a network identifier is selected from a Public Land Mobile Network (PLMN) list.

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

[0060] According to some embodiments, a network node includes processing circuitry configured to generate 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 comprising at least one Closed Access Group (CAG) identifier, and when the list of NPN identifiers includes the at least one element comprising at least one CAG identifier, generating a CAG index to be included as at least a portion of the NPN index. The CAG index is at least partially based on the number of Public Land Mobile Network (PLMN) elements included in the list of NPN identifiers in combination with at least one of one or more CAG identifiers. Generating the network index also includes identifying whether the list of NPN identifiers includes at least one element comprising at least one Network Identifier (NID), and when the list of NPN identifiers includes at least one element comprising at least one NID, generating an NID index to be included as at least a portion of the NPN index. The NID index is at least partially based on the number of NIDs included in the list of NIDs. In some embodiments, the network node further includes a power supply circuit configured to supply power to the network node.

[0061] According to some embodiments, the network node includes processing circuitry configured to transmit a first system information broadcast. The first system information broadcast includes a list of non-public networks (NPNs). The NPN list indicates multiple NPN identifiers. Each NPN identifier is associated with a corresponding network of the multiple networks. The processing circuitry is further configured to prepare a second system information broadcast. The second system information broadcast includes a list of human-readable network names (HRNNs). The HRNN list indicates multiple 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 use the HRNN corresponding to one of the NPN identifiers to identify a corresponding network associated with said one NPN identifier. According to some embodiments, the network node further includes power supply circuitry configured to supply power to the network node.

[0062] In some embodiments, the network node includes processing circuitry configured to transmit parameters to a radio device. The parameters indicate whether the cell is a Non-Public Network Only (NPN) cell. The processing circuitry is further configured to receive a selection of a network identifier from the radio device, wherein when the parameters indicate the cell is NPN only, a network identifier is selected from an NPN list, and when the parameters indicate the cell is not NPN only, a network identifier is selected from a Public Land Mobile Network (PLMN) list. In some embodiments, the network node further includes power supply circuitry configured to supply power to the network node.

[0063] According to some embodiments, a network node includes processing circuitry configured to send a first element of a Public Land Mobile Network (PLMN) list to a wireless device. The first element of the PLMN list indicates that no normal service is available, thereby instructing the wireless device to select a network identifier from a Non-Public Network (NPN) list and use the network identifier to verify system information already stored by the wireless device. According to some embodiments, the network node further includes power supply circuitry configured to supply power to the network node.

[0064] According to some 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 comprising at least one Closed Access Group (CAG) identifier, and when the list of NPN identifiers includes at least one element comprising at least one CAG identifier, generating a CAG index to be included as at least a portion of the NPN index. The CAG index is at least partially based on the number of Public Land Mobile Network (PLMN) elements included in the list of NPN identifiers in combination with at least one of one or more CAG identifiers. Generating the network index also includes identifying whether the list of NPN identifiers includes at least one element comprising at least one network identifier (NID), and when the list of NPN identifiers includes at least one element comprising at least one NID, generating an NID index to be included as at least a portion of the NPN index. The NID index is at least partially based on the number of NIDs included in the list of NIDs.

[0065] According to some embodiments, a method in a wireless network includes detecting a first system information broadcast. The first system information broadcast includes a list of non-public networks (NPNs). The NPN list indicates a plurality of NPN identifiers, each NPN identifier being associated with a corresponding network of the plurality of networks. The method further includes detecting a second system information broadcast. The second system information broadcast includes a list of human-readable network names (HRNNs). 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 the HRNN corresponding to one of the NPN identifiers to identify the corresponding network associated with said one of the NPN identifiers.

[0066] According to some embodiments, a method in a wireless device includes determining whether parameters received from a network node indicate that a cell is a non-public network only (NPN) cell, and selecting a network identifier. When the parameters indicate that the cell is NPN only, a network identifier is selected from an NPN list, and when the parameters indicate that the cell is not NPN only, a network identifier is selected from a Public Land Mobile Network (PLMN) list.

[0067] According to some embodiments, a method in a wireless device includes reading a first element from a list of public terrestrial mobile networks and, in response to detecting the first element indicating that no normal service is available, selecting a network identifier from a list of non-public networks (NPNs). The method further includes using the network identifier to verify system information already stored by the wireless device.

[0068] According to some 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 comprising at least one Closed Access Group (CAG) identifier, and when the list of NPN identifiers includes at least one element comprising at least one CAG identifier, generating a CAG index to be included as at least a portion of the NPN index. The CAG index is at least partially based on the number of Public Land Mobile Network (PLMN) elements included in the list of NPN identifiers in combination with at least one of one or more CAG identifiers. Generating the network index also includes identifying whether the list of NPN identifiers includes at least one element comprising at least one Network Identifier (NID), and when the list of NPN identifiers includes at least one element comprising at least one NID, generating an NID index to be included as at least a portion of the NPN index. The NID index is at least partially based on the number of NIDs included in the list of NIDs.

[0069] According to some embodiments, a method in a network node includes transmitting a first system information broadcast. The first system information broadcast includes a list of non-public networks (NPNs). The NPN list indicates multiple NPN identifiers. Each NPN identifier is associated with a corresponding network of the multiple networks. The method further includes preparing a second system information broadcast. The second system information broadcast includes a list of human-readable network names (HRNNs). The HRNN list indicates multiple 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 the HRNN corresponding to one of the NPN identifiers to identify the corresponding network associated with said one of the NPN identifiers.

[0070] According to some embodiments, a method in a network node includes transmitting parameters to a radio device. The parameters indicate that the cell is a Non-Public Network Only (NPN) cell. The method further includes receiving a selection of a network identifier from the radio device, wherein when the parameters indicate that the cell is an NPN only cell, a network identifier is selected from an NPN list, and when the parameters indicate that the cell is not an NPN only cell, a network identifier is selected from a Public Land Mobile Network (PLMN) list.

[0071] According to some embodiments, a method in a network node includes sending a first element of a list of Public Land Mobile Networks (PLMNs) to a wireless device, the first element of the PLMN list indicating that no normal service is available, thereby instructing the wireless device to select a network identifier from a list of Non-Public Networks (NPNs), and using the network identifier to verify system information already stored by the wireless device.

[0072] According to some embodiments, a computer program includes instructions that, when executed on a computer, perform any step of any of the methods described above.

[0073] According to some embodiments, a computer program product includes a computer program. The computer program includes instructions that, when executed on a computer, perform any step of any of the methods described above.

[0074] According to some embodiments, a non-transitory computer-readable storage medium or carrier includes a computer program. The computer program includes instructions that, when executed on a computer, perform any step of any of the methods described above.

[0075] Certain embodiments may provide one or more of the following technical advantages. For example, this disclosure provides a simple way to generate a network identifier index that spans both NPN and PLMN identifier 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 common messages (e.g., such as setupcomplete messages). Another advantage of this disclosure is that it provides a simple solution for how the HRNN should be broadcast and how it should be connected to an NPN list broadcast as in SIB1. Attached Figure Description

[0076] To gain a more complete understanding of the disclosed embodiments, their features and advantages, reference is now made to the following description taken in conjunction with the accompanying drawings, in which: Figure 1 An example of the message flow for establishing Radio Resource Control (RRC) is shown; Figure 2 Examples of methods according to some embodiments are shown; Figure 3 Examples of wireless networks according to some embodiments are shown; Figure 4 Examples of user equipment according to some embodiments are shown; Figure 5 Examples of virtualized environments according to some embodiments are shown; Figure 6 Examples of telecommunications networks connected to a host computer via an intermediate network, according to some embodiments, are shown; Figure 7 An example is shown whereby a host computer communicates with a user equipment via a base station through a partial wireless connection, according to some embodiments. Figure 8 Examples of methods implemented in a communication system according to some embodiments are shown, the communication system including a host computer, a base station, and a user equipment; Figure 9 Examples of methods implemented in a communication system according to some embodiments are shown, the communication system including a host computer, a base station, and a user equipment; Figure 10 Examples of methods implemented in a communication system according to some embodiments are shown, the communication system including a host computer, a base station, and a user equipment; Figure 11 Examples of methods implemented in a communication system according to some embodiments are shown, the communication system including a host computer, a base station, and a user equipment; Figure 12 Examples of methods according to some embodiments are shown; Figure 13 Examples of methods according to some embodiments are shown; Figure 14 Examples of virtualized devices according to some embodiments are shown; Figure 15A and Figure 15B Examples of methods according to some embodiments are shown; Figure 16 Examples of network indexes according to some embodiments are shown; Figure 17 Examples of methods according to some embodiments are shown; Figure 18 Examples of methods according to some embodiments are shown; Figure 19 Examples of methods according to some embodiments are shown; Figure 20 Examples of methods according to some embodiments are shown; Figure 21 Examples of methods according to some embodiments are shown; Figure 22 Examples of methods according to some embodiments are shown; Figure 23 Examples of methods according to some embodiments are shown; and Figure 24 Examples of methods according to some embodiments are shown. Detailed Implementation

[0077] Some embodiments of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. However, other embodiments are included within the scope of the subject matter disclosed herein, and the disclosed subject matter should not be construed as being limited to the embodiments presented herein; these embodiments are provided by way of example in order to convey the scope of the subject matter to those skilled in the art.

[0078] Generally, all terms used herein shall be interpreted in accordance with their ordinary meaning in the relevant art, unless a different meaning is explicitly given and / or implied by the context in which it is used. All references to “a (a / an) / the element, device, component, part, step, etc.” are open-ended and are interpreted as referring to at least one instance of an element, device, component, part, step, etc., unless otherwise expressly stated. The steps of any method disclosed herein need not be performed in the exact order disclosed, unless the steps are explicitly described as occurring after or before another step and / or imply that a step must occur after or before another step. Any feature of any embodiment of the disclosed embodiments may be suitably applied to any other embodiment. Similarly, any advantage of any embodiment may be applied to any other embodiment, and vice versa. Other objects, features, and advantages of the disclosed embodiments will be apparent from the following description.

[0079] CAG identifiers associated with the same PLMN In one aspect of this disclosure, a solution is provided for generating a network index using more than one network list. In one embodiment, the network list is a list of PLMNs and a list of NPNs.

[0080] The list of NPNs can be further broken down into the following lists: PLMN + CAG ID; and PLMN + Network ID (also known as "NID").

[0081] Depending on the context, the symbol "PLMN" sometimes refers to the identifier PLMN ID (composed of the Mobile Country Code (MCC) and Mobile Network Code (MNC), and sometimes it refers to the public network identified by the PLMN ID. To clarify when the ID portion is used, the PLMN ID is sometimes represented by the symbols "MCC, MNC". It should be understood that the symbols "MCC, MNC" represent the same content as the PLMN ID.

[0082] When generating network indexes for various network types, rules are needed regarding what information to indicate in the index and how to indicate that information. For example, in the case of an operator operating a PLMN represented by a PLMN ID, one such rule should clarify whether a CAG ID broadcast along with that PLMN ID can have the same network index as another CAG ID broadcast along with the same PLMN ID.

[0083] The proposed structure, which includes elements with CAG IDs, demonstrates that if the same PLMN ID is used to serve several CAGIDs, they can be collected. This aspect is illustrated below: NPN-Identity Information Element -- ASN1START -- TAG-NPN-IDENTITY-START NPN-Identity-r16 ::= CHOICE { pni-npn-r16 SEQUENCE { plmn-Identity-r16 PLMN-Identity, cag-IdentityList-r16 SEQUENCE (SIZE (1..maxNPN-r16)) OF CAG-Identity-r16 }, snpn-r16 SEQUENCE { plmn-Identity PLMN-Identity, nid-List-r16 SEQUENCE (SIZE (1..maxNPN-r16)) OF NID-r16 } } CAG-Identity-r16 ::= BITSTRING (SIZE (32)) NID-r16 ::= BIT STRING (SIZE (52)) -- TAG-NPN-IDENTITY-STOP -- ASN1STOP Therefore, it is possible to collect CAG IDs within a single NPN-Identity element, or to create several NPN-Identity elements and assign a different CAG ID to each element, but it is also possible to duplicate the same PLMN-Identity for an element. Both are possible. When CAG IDs with the same PLMN ID are broadcast in different NPN-Identity elements, it is possible to assign different cellIdentities to them by listing them in different NPN-IdentityInfo elements, as described below.

[0084] NPN-IdentityInfoList information elements -- ASN1START -- TAG-NPN-IDENTITYINFOLIST-START NPN-IdentityInfoList-r16 ::= SEQUENCE (SIZE (1..maxNPN-r16)) OF NPN-IdentityInfo-r16 NPN-IdentityInfo-r16 ::= SEQUENCE { NPN-IdentityList-r16 SEQUENCE (SIZE (1..maxNPN-r16)) OF NPN-Identity-r16, trackingAreaCode-r16 TrackingAreaCode, ranac-r16 RAN-AreaCode OPTIONAL, --Need R CellIdentity-r16 CellIdentity, cellReservedForOperatorUse-r16 ENUMERATED {reserved,notReserved}, ... } -- TAG-NPN-IDENTITYINFOLIST-STOP -- ASN1STOP In situations where an operator wants to handle a CAG ID that differs from other CAG IDs broadcast by the operator, some embodiments create an NPN-Identity element that only has that specific 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 even a separate Uniform Access Control (UAC) parameter because it is acquiring a unique network index.

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

[0086] One of the main reasons for this is that it is 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 this disclosure, all CAGs listed within the same NPN-Identity will be defined as having the same network index value, and rules will be provided regarding how the UE should generate index values ​​for a certain network type.

[0087] Definitions of NPN-IdentityInfoList and plmn-IdentityList.

[0088] The network index is primarily used to inform the network side (access node, such as gNB) about which network the user / UE intends to access. The network index is also used by the network to represent uniform access control parameters (such as restriction factors and restriction times) at each network level (as indicated below, UAC-BarringPerPLMN).

[0089] For PLMNs, the UE needs to signal the RAN about the selected network upon connection establishment (completion) so that the RAN can select the correct AMF. This is done via an instruction index, see below: RRCSetupComplete-IEs ::= SEQUENCE{ selectedPLMN-Identity INTEGER (1..maxPLMN), registeredAMF RegisteredAMF OPTIONAL, guami-Type ENUMERATED {native, mapped}OPTIONAL, s-NSSAI-List SEQUENCE (SIZE (1..maxNrofS-NSSAI)) OF S-NSSAI OPTIONAL, dedicatedNAS-Message DedicatedNAS-Message, ng-5G-S-TMSI-Value CHOICE { ng-5G-S-TMSI ng-5G-S-TMSI-Part2 BIT STRING (SIZE (9)) OPTIONAL lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE{} OPTIONAL } Similarly, for Unified Access Control (UAC), the PLMN index is used to signal specific UAC-specific limiting parameters.

[0090] UAC-BarringPerPLMN-List ::= SEQUENCE (SIZE (1..maxPLMN)) OFUAC-BarringPerPLMN UAC-BarringPerPLMN ::= SEQUENCE { plmn-IdentityIndex INTEGER (1..maxPLMN), uac-ACBarringListType CHOICE{ uac-ImplicitACBarringList SEQUENCE (SIZE(maxAccessCat-1)) OF UAC-BarringInfoSetIndex, uac-ExplicitACBarringList UAC-BarringPerCatList } OPTIONAL -- Need S } The index is not explicitly included in SIB1, but is generated by the UE from the SIB1 broadcast using the rules stated above in TS 38.331, namely: For the PLMN contained in the nth entry of PLMN-IdentityInfoList and the ith 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.

[0091] Since the framework and functionality associated with plmn-IdentityIndex and selectedPLMN-Identity are all in place, it would be preferred if it could be reused as much as possible. This embodiment proposes also building a plmn-IdentityIndex for the NPN to avoid changes beyond the broadcast information in SIB1. Therefore, according to this disclosure, for indexing the NPN, the NPN index should be used in the exact same way as the PLMN index.

[0092] A crucial aspect of indexing is that it should point to a specific PLMN or network (represented by PNINPN as CAG or SNPN). Therefore, indexing must be performed so that it needs to be stepped up when the PLMN can be changed. Current recommendations suggest that the PLMN is included in the NPN Identity element, and thus the NPN-Identity needs to serve as the basis for indexing. Therefore, indexing needs to be based on elements that allow the PLMN to be changed, such as the NPN-Identity.

[0093] One way to describe and generate an index using the NPN list and structure proposed by NPN-IdentityInfoList is to divide it into three parts: PLMN-index (if already defined) CAG-index - PIN-NIN w CAG index (see below) NID-index - SNPN / NID index Some implementations use this separation to control when to step on the index. For example, a list of CAG indices in the same cag-IdentityList should not step on the index, while a list of NIDs in the nid-List should.

[0094] In this context, for shared scenarios, a list that does not mix cag-IdentityList and nid-IdentityList is required. One feasible approach is to always broadcast, so that PLMN has the lowest index, followed by CAG, and then NID. The order of indices from low to high should be PLMN – CAG / PNI-NPN – NID / SNPN.

[0095] According to one aspect of this disclosure, the CAG-index is defined as: PLMN-index + x represents the CAG IDs (in order) in the x-th cag-IdentityList. Therefore, all CAG IDs within the same cag-IdentityList should have the same CAG-index.

[0096] The NID-index is defined as: For the NID at position p in the nth nid-list, PLMN-index + CAG index + N1-N2+…+N(n-1) + p, where N(s) is the number of NIDs in each nid-list.

[0097] Using the above index definition, all NIDs will have independent indices, and all CAGs collected in the same cag-IdentityList will have the same index. Therefore, generating CAG-index and NID indices in the UE and network results in: CAG index = PLMN-index + x in the xth cag-IdentityList. For the NID at position p in the nth nid-list, NID index = PLMN-index + CAG-index + N1-N2 + ... + N(n-1) + p, where N(s) are the number of NIDs in each nid-list.

[0098] The above can be expressed in other ways, such as referring to the structure of signaling, where reference can be made to: NPN-IdentityInfoList NPN-IdentityInfo NPN-IdentityList NPN Identity PLMN-Identity and CAG or NID List For the sake of brevity, the above description omits the steps between the NPN-IdentityInfoList and the CAG / NID elements in the cag-Identity list or NID list, as these would result in a more complex expression.

[0099] It's possible to reference a CAGID within an identityLists or IdentityInfo element, but this doesn't change the index value as long as there's a clearly defined order.

[0100] Another aspect related to the index definition is when the parameter `cellReservedForOtherUse` is set to true. This means that there are no accessible elements in the PLMN list (networks in the PLMN list will be restricted).

[0101] This effectively means that the complete PLMN-list is disabled (restricted for all UEs), and then it makes sense that there is no plmn-IdentityIndex count at all; that is, the PLMN index value should be zero when signaling to the NPN. Therefore, some embodiments include the following additional condition when generating an index for CAG or NID: when cellReservedForOtherUse is set to true, generating the NPN-index (CAG index, NID index) should count the PLMN-index portion to zero.

[0102] A diagram illustrating the different steps involved in generating index values ​​in UE. Figure 2 As shown in the image.

[0103] In the first step 20, the UE reads SIB1 and first checks whether cellReservedForOtherUse is set to "true" or "false". If it is set to "true", the UE should skip to step 26. If it is set to "false", the UE should generate an index of the PLMN listed in the PLMN Identity list according to the definition (PLMN-index shown in step 24), and then should continue to step 26. In the next step 26, it should check whether the NPN-Identity list exists in the broadcast. If the NPN-Identity list does not exist, the UE should skip to step 36. If the NPN-Identity list exists, it should check whether the list includes CAG IDs (step 28). If the list does not include any CAG IDs, the UE skips to step 32. If the list includes one or more CAG IDs, the UE performs step 30 to generate an index set for the CAG IDs according to the rules listed above, and then continues to step 32. As the next step 32, a check is performed to see if an NID exists in the NPN-IdentityList. If no NID exists in the NPN-IdentityList, the process jumps to step 36. If one or more NIDs exist in the NPN-IdentityList, the UE performs step 34 (generating an NID index according to the rules described above) and then continues to step 36. In step 36, the method ends with the UE transmitting the calculated index, which indicates the network identifier of the network to which the UE intends to access and establish an RRC connection.

[0104] Even though the above instructions are for UEs, generating an index using the same process is actually a network task, as it requires determining whether or when the network should be configured to broadcast PLMN or network-specific UAC parameters.

[0105] Following the process described above, for example, in the next step of a UE while an attempt to access a network is in progress, the UE should format an RRCSetupComplete message, which includes an index indication corresponding to the network that the UE / user intends to access.

[0106] In another aspect of this disclosure, it is necessary to support broadcasting human-readable network names (HRNNs) for all CAG broadcasts and SNPN (MCC, MNC, NID combinations). Therefore, it is possible to broadcast readable names to the HRNNs of CAG cells and SNPN cells.

[0107] According to one aspect of this disclosure, instead of using the index created in the previous steps, a new SIB (SIBx) is used for HRNN broadcasting. This new SIB includes the same number of CAGs and NIDs as the SIB1 broadcast. If there are networks that should not have HRNNs, the element is included anyway, but its content is set to "empty," "unnamed," or some other indication that some network is not actually broadcasting a human-readable network name. This parameter can also simply be a "false" indication.

[0108] According to one aspect of this disclosure, an advantage is recognized in including as many elements as there are CAG IDs and NIDs. For example, an alternative approach using an index generated by the UE or network as described above would not allow the possibility of listing HRNNs for CAGs that are part of the same CAG list, since these CAGs could have the same network index. Therefore, a solution using an index would need to consider indexing all CAGs and all NIDs. However, the problem is that CAGs in the same list should not be indexed, and then it cannot be directly used to associate with HRNNs. It would be advantageous if it were possible to reuse the index used for UAC and msg5 (as described above). However, since this would not allow different HRNNs for CAGs collected 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 for all CAGs and NIDs and associate this index with the HRNN list. According to another embodiment of this disclosure, an alternative would therefore be to create a second index, CAG-NID-index, and associate this index with the HRNN in the HRNN broadcast. This is considered an alternative in the case that the new SIB of the HRNN will have the same number of HRNN elements as the number of CAGs and NIDs in SIB1, wherein these elements can also be empty.

[0109] The following provides an example of an HRNN according to an embodiment of this disclosure: SIBx IE SIBx includes human-readable network names (HRNN). SIBx Information Elements -- ASN1START -- TAG-SIBx-START SIBx ::= SEQUENCE { hrnn-List SEQUENCE (SIZE (1..maxNPN-r16)OF HRNN ... } HRNN ::= CHOICE { hrnn OCTET STRING (size (1..48)), noHRNN ENUMERATED {true} } -- TAG-SIBx-STOP -- ASN1STOP Regarding when a UE is reading system information, and specifically when it is acquiring SIB1 information to enable the UE to reuse stored system information, the SIB in the NR (other than SIB1, SIB6, SIB7, or SIB8) is associated with a value tag. If a stored SIB was acquired less than 3 hours ago, and the value tag matches the value tag provided by that SIB in SIB1, it is considered valid. SIBs can also be associated with valid area tags to allow the same SIB to be reused in more than one cell—in this case, the area ID must also match the area ID in SIB1 for the stored SIB to be considered valid.

[0110] When verifying the value label, the UE must also check the PLMN ID and, optionally (depending on whether the SIB is cell-specific), match the stored SIB's Cell ID with the PLMN ID and Cell ID broadcast in SIB1. However, comparing PLMN IDs presents a slight problem because multiple PLMN IDs can exist associated with the cell due to RAN sharing. In Rel-15, this is addressed by comparing the first PLMN ID broadcast in SIB1.

[0111] The fact that the first PLMN ID is used in SI verification may potentially cause problems for NPN-only cells. Since it has been agreed that NPNs are provided in a separate network list, in the case of "NPN-only cells," the PLMN list value can be considered a "dummy value" and not relied upon for SI validity. Furthermore, and especially for SNPNs, having only the PLMN portion may not be sufficient, as it may not be unique, particularly when MCC=999 is used whenever the operator's PLMN is not in use. For SNPNs, the NID is also practically required.

[0112] For the purposes described above and in accordance with another aspect of this disclosure, it is recommended that if cellReservedForOperatorUse is set to "false", the UE should perform the verification as described above. If cellReservedForOperatorUse is set to "true" (NPN only), the first network element in the NPN-IdentityInfoList should be used. If this element is an SNPN element, it should also include the NID portion.

[0113] In another aspect of this disclosure, if the "PLMN Dummy value" is a normalized value for a substantially non-empty list of PLMNs, the UE can readily identify, by detecting the dummy value, that the first element of the NPN list should be retrieved instead. Therefore, it is unnecessary to detect or read the cellReservedForOtherUse value. Thus, according to one aspect of this disclosure, when cellReservedForOtherUse is set to true, the UE should use the first network identifier (PLMN, SNPN) in the NPN-IdentityInfoList instead of the PLMN-IdentityInfoList. If the first network identifier is the SNPN identifier, then both the PLMN and NID should be used when verifying the stored SI.

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

[0115] 5.2.2.2.1 SIB Validity The UE shall apply the System Information (SI) acquisition procedure as defined in Clause 5.2.2.3 when selecting a cell (e.g., upon power-up), reselecting a cell, returning from outside coverage, after reconfiguration completed with synchronization, after entering the network from another RAT, upon receiving an indication that the System Information has been changed, upon receiving a PWS notification, and whenever the UE does not have a valid version of the SIB stored.

[0116] When the UE acquires a MIB (Master Information Block) or SIB1 or SI message in the serving cell as described in Clause 5.2.2.3, and if the UE stores the acquired SIB, the UE should store the associated areaScope (if it exists), network identifier (PLMN-Identity or PLMN-Identity + NID), CellIdentity, systemInformationAreaID (if it exists), and valueTag (if it exists), as indicated in the si-SchedulingInfo of the SIB. For example, after cell reselection, upon returning from outside coverage, or after receiving an SI change indication, the UE may use a valid stored version of the SI other than MIB, SIB1, SIB6, SIB7, or SIB8.

[0117] Note: The storage and management of SIBs other than those valid for the current serving cell are left to the UE.

[0118] UE should: 1> If cellReservedForOtherUse is set to false, then: 2> Use the first PLMN-Identity in the PLMN-IdentityInfoList, which serves as the network identifier, and the associated CellIdentity for SIB validity verification; 2> Otherwise: 2> If the first NPN-Identity in NPN-IdentityInfoList is pni-npn, then: 3> Use the PLMN-Identity and associated CellIdentity in the NPN-Identity, which serves as the network identifier, for SIB validity verification; 2> If the first NPN-Identity in NPN-IdentityInfoList is snpn, then: 3> Use the PLMN-Identity, the first NID, and the associated CellIdentity in the NPN-Identity as network identifiers for SIB validity verification; 1> Delete any stored versions of the SIB 3 hours after it is successfully confirmed as valid; 1> For each storage version of SIB: 2> If areaScope is associated, and the value of the version stored by the SIB is the same as the value received in the si-SchedulingInfo from the serving cell's SIB, then: 3> If the valueTag, systemInformationAreaID, and network identifier contained in the si-SchedulingInfo of the SIB received from the serving cell are the same as the network identifier, systemInformationAreaID, and valueTag of the stored version associated with that SIB, then: 4> It is assumed that the stored SIB is valid for the cell; 2> If the stored version of areaScope for the SIB does not exist, and the areaScope value is not included in the si-SchedulingInfo of the SIB from the serving cell, then: 3> If the valueTag, CellIdentity, and network identifier contained in the si-SchedulingInfo of the SIB received from the serving cell are the same as the network identifier, CellIdentity, and valueTag of the stored version associated with that SIB, then: 4> It is assumed that the stored SIB is valid for the cell; Next amendment sub-clause The following paragraphs describe the additional changes to the 3GPP TS 38.331 specification, beginning in section 5.5.5.1 (“General”). This section of TS 38.331 includes… Figure 5 5.5.1-1: Measurement Report, which shows the UE sending a MeasurementReport message to the network. The purpose of this process is to transmit measurement results from the UE to the network. The UE should only initiate this process after successful access class (AS) security activation.

[0119] For the measId that triggers the measurement reporting process, the UE should set measResults in the MeasurementReport message as follows: 1> Set measId as the measurement identifier that triggers the measurement report; 1> For each serving cell configured with servingCellMO: 2> If the reportConfig associated with the measId that triggered the measurement report includes rsType, then: 3> If the serving cell measurement based on the rsType contained in the reportConfig that triggers the measurement report is available, then: 4> Set the measResultServingCell in measResultServingMOList to include the reference signal received power (RSRP), reference signal received quality (RSRQ), and available signal interference plus noise ratio (SINR) of the serving cell, which are derived based on the rsType contained in the reportConfig that triggers the measurement report; 2> Otherwise: 3> If serving cell measurements based on the Synchronization Signal Block (SSB) are available, then: 4> Set the measResultServingCell in measResultServingMOList to include the RSRP, RSRQ and available SINR of the serving cell obtained based on SSB; 3> Otherwise, if serving cell measurements based on Channel State Information Reference Signal (CSI-RS) are available, then: 4> Set the measResultServingCell in measResultServingMOList to include the RSRP, RSRQ and available SINR of the serving cell obtained based on CSI-RS; 1> Set the servCellId in measResultServingMOList to include each NR serving cell that is configured with servingCellMO (if any); 1> If the reportConfig associated with the measId that triggered the measurement report includes reportQuantityRS-Indexes and maxNrofRS-IndexesToReport, then: 2> For each serving cell configured with servingCellMO, including beam measurement information of the associated reportConfig as described in 5.5.5.2; 1> If the reportConfig associated with the measId that triggered the measurement report includes reportAddNeighMeas, then: 2> For each measObjectId referenced in measIdList (which is also referenced using servingCellMO), except for the measObjectId corresponding to the measId that triggered the measurement report: 3> If the measObjectNR indicated by servingCellMO includes the RS resource configuration corresponding to the rsType indicated in reportConfig, then: 4> Set the measResultBestNeighCell in measResultServingMOList to include physCellId and the available measurement quantities of reportQuantityCell and rsType indicated in the reportConfig based on the non-serving cell corresponding to the measObjectNR involved. The measObjectNR involved has the highest measurement RSRP if the RSRP measurement result can be used in the cell corresponding to this measObjectNR, otherwise it has the highest measurement RSRQ if the RSRQ measurement result can be used in the cell corresponding to this measObjectNR, otherwise it has the highest measurement SINR. 4> If the reportConfig associated with the measId that triggered the measurement report includes reportQuantityRS-Indexes and maxNrofRS-IndexesToReport, then: 5> For each best non-serving cell included in the measurement report: 6> Includes beam measurement information associated with the reportConfig as described in 5.5.5.2; 1> If the reportConfig associated with the measId that triggered the measurement report is set to eventTriggered, and the eventID is set to eventA3, eventA4, eventA5, eventB1, or eventB2, then: 2> If the UE is in NE-DC and the measurement configuration that triggered this measurement report is associated with MCG, then: 3> Configure measResultServFreqListEUTRA-SCG to include entries for each E-UTRASCG service frequency that have the following characteristics: 4> Includes carrierFreq for E-UTRA service frequencies; 4> Configure measResultServingCell to include available measurements that the UE is configured to measure via the measurement configuration associated with the SCG; 4> If the reportConfig associated with the measId that triggered the measurement report includes reportAddNeighMeas, then: 5> Set measResultServFreqListEUTRA-SCG to include the amount of the best non-serving cell based on RSRP on the relevant serving frequency within measResultBestNeighCell; 1> If the reportConfig associated with the measId that triggered the measurement report is set to eventTriggered, and the eventID is set to eventA3, eventA4, or eventA5, then: 2> If the UE is in NR-DC and the measurement configuration that triggered this measurement report is associated with MCG, then: 3> Configure measResultServFreqListNR-SCG to include the following aspects for each NR SCG serving cell configured with servingCellMO (if any): 4> If the reportConfig associated with the measId that triggered the measurement report includes rsType, then: 5> If the serving cell measurement based on the rsType contained in the reportConfig of the triggered measurement report is available according to the measurement configuration associated with the SCG, then: 6> Set the measResultServingCell in measResultServFreqListNR-SCG to include the serving cell's RSRP, RSRQ, and available SINR, which are derived based on the rsType contained in the reportConfig that triggers the measurement report; 4> Otherwise: 5> If SSB-based serving cell measurements are available according to the measurement configuration associated with SCG, then: 6> Set the measResultServingCell in measResultServFreqListNR-SCG to include the RSRP, RSRQ, and available SINR of the serving cell derived from the SSB; 5> Otherwise, if the CSI-RS-based serving cell measurements are available according to the measurement configuration associated with the SCG, then: 6> Set the measResultServingCell in measResultServFreqListNR-SCG to include the RSRP, RSRQ and available SINR of the serving cell obtained based on CSI-RS; 4> If the serving cell result derived from the SSB is included, then: 5> Include ssbFrequency in the value indicated by ssbFrequency contained in, for example, the MeasObjectNR of the serving cell; 4> If the serving cell result derived from CSI-RS is included, then: 5> Include refFreqCSI-RS in the value indicated by refFreqCSI-RS as contained in the MeasObjectNR of the serving cell; 4> If the reportConfig associated with the measId that triggered the measurement report includes reportQuantityRS-Indexes and maxNrofRS-IndexesToReport, then: 5> For each serving cell configured with servingCellMO, beam measurement information is included according to the associated reportConfig as described in 5.5.5.2, wherein availability is taken into account according to the measurement configuration associated with SCG; 4> If the reportConfig associated with the measId that triggered the measurement report includes reportAddNeighMeas, then: 5> If the measObjectNR indicated by servingCellMO includes the RS resource configuration corresponding to the rsType indicated in reportConfig, then: 6> Set the measResultBestNeighCellListNR in measResultServFreqListNR-SCG to include an entry with a physCellId and an available measurement quantity indicated in the reportQuantityCell and rsType in the reportConfig based on the non-serving cell corresponding to the measObjectNR involved, wherein the measObjectNR involved has the highest measurement RSRP if the RSRP measurement result is available to the cell corresponding to this measObjectNR, otherwise it has the highest measurement RSRQ if the RSRQ measurement result is available to the cell corresponding to this measObjectNR, and otherwise it has the highest measurement SINR, wherein availability is considered according to the measurement configuration associated with the SCG; 7> If the reportConfig associated with the measId that triggered the measurement report includes reportQuantityRS-Indexes and maxNrofRS-IndexesToReport, then: 8> For each best non-serving cell included in the measurement report: 9> Includes beam measurement information according to the associated reportConfig as described in 5.5.5.2, wherein availability is taken into account according to the measurement configuration associated with the SCG; 1> If there is at least one applicable neighboring cell to be reported, then: 2> If reportType is set to eventTriggered or periodic, then: 3> Set measResultNeighCells to include the best neighboring cells based on the following description, which includes at most maxReportCells: 4> If reportType is set to eventTriggered, then: 5> Including cells contained in the cellsTriggeredList defined within the VarMeasReportList of this measId; 4> Otherwise: 5> This includes applicable cells for which new measurement results have become available since the last periodic report or since the measurement was initiated or reset; 4> For each cell included in measResultNeighCells, including physCellId; 4> If reportType is set to eventTriggered or periodic, then: 5> For each included cell, the measurement results, including Layer 3 filtering, are sorted according to the reportConfig of this measId as follows: 6> If the measObject associated with this measId involves NR, then: 7> If the rsType in the associated reportConfig is set to ssb, then: 8> Set the resultsSSB-Cell in measResult to include one or more quantities based on the Synchronization Signal (SS) / Physical Broadcast Channel (PBCH) block indicated in the reportQuantityCell in the relevant reportConfig, in descending order of the classification quantities, as determined in 5.5.5.3, i.e., the best cell is included first; 8> If reportQuantityRS-Indexes and maxNrofRS-IndexesToReport are configured, beam measurement information as described in 5.5.5.2 is included; 7> Otherwise, if the rsType in the associated reportConfig is set to csi-rs, then: 8> Set the resultsCSI-RS-Cell in measResult to include one or more CSI-RS-based quantities indicated in the reportQuantityCell in the relevant reportConfig, in descending order of classification quantities, as specified in 5.5.5.3, i.e., the best cell is included first; 8> If reportQuantityRS-Indexes and maxNrofRS-IndexesToReport are configured, beam measurement information as described in 5.5.5.2 is included; 6> If the measObject associated with this measId involves E-UTRA, then: 7> Set measResult to include one or more quantities indicated in reportQuantity within the relevant reportConfigInterRAT, in descending order of classification quantities, as specified in 5.5.5.3, i.e., the best cell is included first; 2> Otherwise: 3> If the cell indicated by cellForWhichToReportCGI (Note: CGI stands for Cell Global Identifier) ​​is an NR cell, then: 4> If the plmn-IdentityInfoList of the CGI-Info for the involved cell has been obtained, then: 5> For each entry in plmn-IdentityInfoList, including plmn-IdentityInfoList, which includes plmn-IdentityList, trackingAreaCode (if available), ranac (if available), CellIdentity, and cellReservedForOperatorUse; 5> Include frequencyBandList (if available); 4> If the UE has NPN capability and the NPN-IdentityInfoList of the CGI-Info for the involved cell has been obtained, then: 5> For each entry in NPN-IdentityInfoList, including NPN-IdentityInfoList, which includes NPN-IdentityList, trackingAreaCode (if available), ranac (if available), CellIdentity, and cellReservedForOperatorUse; 4> Otherwise, if the MIB indicates that SIB1 has not been broadcast, then: 5> Includes noSIB1, which includes ssb-SubcarrierOffset and pdcch-ConfigSIB1, which are obtained from the MIB of the cell involved (where "pdcch" represents the physical downlink control channel). 3> If the cell indicated by cellForWhichToReportCGI is an E-UTRA cell, then: 4> If all mandatory fields of the CGI-Info-EPC for the cell in question have been obtained, then: 5> Include the fields broadcast in E-UTRA SystemInformationBlockType1 that are associated with the EPC in cgi-Info-EPC; 4> If the UE is E-UTRA / 5GC capable, and all mandatory fields of the cgi-Info-5GC of the involved cell have been obtained, then: 5> Include fields broadcast in E-UTRA SystemInformationBlockType1 that are associated with 5GC in cgi-Info-5GC; 4> If the forced presence field of the cgi-Info for the cell indicated by cellForWhichToReportCGI in the associated measObject has been obtained, then: 5> Includes freqBandIndicator; 5> If the cell broadcasts multiBandInfoList, then multiBandInfoList will be included; 5> If the cell broadcasts freqBandIndicatorPriority, then freqBandIndicatorPriority is included; 1> If the corresponding measObject involves NR, then: 2> If reportSFTD-Meas is set to true in the corresponding reportConfigNR for this measId, then: 3> Configure measResultSFTD-NR as follows: 4> Set sfn-OffsetResult (where SFN represents the system frame number) and frameBoundaryOffsetResult to the measurement results provided by the lower layer; 4> If reportRSRP is set to true, then: 5> Set rsrp-Result to the RSRP of the NR PSCell (primary cell of the secondary cell group) obtained based on SSB; 2> Otherwise, if reportSFTD-NeighMeas is included in the corresponding reportConfigNR of this measId, then: 3> For each applicable cell whose measurement results are available, including entries in measResultCellListSFTD-NR, the content is set as follows: 4> Set physCellId to the physical cell identifier of the NR neighboring cells involved. 4> Set sfn-OffsetResult and frameBoundaryOffsetResult to the measurement results provided by the lower layer; 4> If reportRSRP is set to true, then: 5> Set rsrp-Result to the RSRP of the relevant cell obtained based on SSB; 1> Otherwise, if the corresponding measObject involves E-UTRA, then: 2> If reportSFTD-Meas is set to true in the corresponding reportConfigInterRAT for this measId, then: 3> Configure measResultSFTD-EUTRA as follows: 4> Set sfn-OffsetResult and frameBoundaryOffsetResult to the measurement results provided by the lower layer; 4> If reportRSRP is set to true, then: 5> Set rsrpResult-EUTRA to the RSRP of EUTRA PSCell; 1> Increment the numberOfReportsSent defined in VarMeasReportList, such as this measId, by 1; 1> If it is running, stop the periodic report timer; 1> If the numberOfReportsSent defined in the VarMeasReportList of this measId is less than the reportAmount defined in the corresponding reportConfig of this measId, then: 2> Use the value of reportInterval defined in the corresponding reportConfig for this measId to start the periodic report timer; 1> Otherwise: 2> If reportType is set to periodic, then: 3> Remove the entry from VarMeasReportList for this measId; 3> Remove this measId from the measIdList within VarMeasConfig; 1> If the UE is in (NG) EN-DC, then: 2> If SRB3 is configured, then: 3> The process ends when the MeasurementReport message is submitted to a lower layer via SRB3 for transmission; 2> Otherwise: 3> Submit MeasurementReport messages via E-UTRA MCG embedded in E-UTRA RRC message ULInformationTransferMRDC as specified in TS 36.331

[10] (where UL represents uplink and MRDC represents multi-RAT dual connectivity).

[0120] 1> Otherwise, if the UE is in an NR-DC, then: 2> If the measurement configuration that triggers this measurement report is associated with SCG, then: 3> If SRB3 is configured, then: 4> The process ends when the MeasurementReport message is submitted to the lower layer via SRB3 for transmission; 3> Otherwise: 4> Submit the MeasurementReport message via the NRMCG embedded in the NR RRC message ULInformationTransferMRDC as specified in 5.7.2a.3; 2> Otherwise: 3> The process ends when the MeasurementReport message is submitted to the lower layer via SRB1 for transmission; 1> Otherwise: 2> Submit the MeasurementReport message to a lower layer for transmission, at which point the process ends.

[0121] Next amendment sub-clause 6.2.2 Message Definition [...] – RRCResumeComplete The RRCResumeComplete message is used to confirm the successful completion of RRC connection restoration.

[0122] Signaling radio bearer: SRB1 RLC-SAP: AM Logical channel: Dedicated Control Channel (DCCH) Direction: UE to network RRCResumeComplete message -- ASN1START --TAG-RRCRESUMECOMPLETE-START RRCResumeComplete ::= SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { rrcResumeComplete RRCResumeComplete-IEs, criticalExtensionsFuture SEQUENCE {} } } RRCResumeComplete-IEs ::= SEQUENCE { dedicatedNAS-Message DedicatedNAS-MessageOPTIONAL, selectedPLMN-Identity INTEGER (1..maxPLMN) OPTIONAL uplinkTxDirectCurrentList UplinkTxDirectCurrentListOPTIONAL, lateNonCriticalExtension OCTET STRING OPTIONAL nonCriticalExtension SEQUENCE{} OPTIONAL } -- TAG-RRCRESUMECOMPLETE-STOP -- ASN1STOP [...] The next amendment sub-clause – Changes to SIB3 and the new SIBx 6.3.1 System Information Block [...] – SIB3 SIB3 contains neighboring cell information relevant only to intra-frequency cell reselection. IE includes cells with specific reselection parameters and blacklisted cells.

[0123] SIB3 Information Elements -- ASN1START -- TAG-SIB3-START SIB3 ::= SEQUENCE { intraFreqNeighCellList IntraFreqNeighCellList OPTIONAL,-- Need R intraFreqBlackCellList IntraFreqBlackCellList OPTIONAL,--Need R lateNonCriticalExtension OCTET STRING OPTIONAL, ... } IntraFreqNeighCellList ::= SEQUENCE (SIZE (1..maxCellIntra)) OF IntraFreqNeighCellInfo IntraFreqNeighCellInfo ::= SEQUENCE { physCellId PhysCellId, q-OffsetCell Q-OffsetRange, q-RxLevMinOffsetCell INTEGER (1..8) OPTIONAL, --Need R q-RxLevMinOffsetCellSUL INTEGER (1..8) OPTIONAL,--Need R q-QualMinOffsetCell INTEGER (1..8) OPTIONAL, --Need R ... [[ cag-PCI-Range-r16 PCI-Range OPTIONAL --Need R ]] } IntraFreqBlackCellList ::= SEQUENCE (SIZE (1..maxCellBlack)) OF PCI-Range -- TAG-SIB3-STOP -- ASN1STOP [...] SIBx IE SIBx includes human-readable network names (HRNN). SIBx Information Elements -- ASN1START -- TAG-SIBx-START SIBx ::= SEQUENCE { hrnn-List SEQUENCE (SIZE (1..maxNPN-r16)OF HRNN ... } HRNN ::= CHOICE { hrnn OCTET STRING (size (1..48)), noHRNN ENUMERATED {true} } -- TAG-SIBx-STOP -- ASN1STOP The next amendment to the sub-clause (based on CR from 108#37) 6.3.2 Radio Resource Control Information Elements [...] – CellAccessRelatedInfo IE CellAccessRelatedInfo indicates cell access-related information for this cell.

[0124] CellAccessRelatedInfo information element -- ASN1START -- TAG-CELLACCESSRELATEDINFO-START CellAccessRelatedInfo ::= SEQUENCE { plmn-IdentityList PLMN-IdentityInfoList, cellReservedForOtherUse ENUMERATED {true} OPTIONAL,--Need R ..., [[ cellReservedForFutureUse-r16 ENUMERATED {true} OPTIONAL,-- Need R NPN-IdentityInfoList-r16 NPN-IdentityInfoList-r16OPTIONAL -- Need R ]] } -- TAG-CELLACCESSRELATEDINFO-STOP -- ASN1STOP [...] – CGI-InfoNR The IE CGI-InfoNR indicates cell access-related information reported by the UE as part of the CGI reporting process.

[0125] CGI-InfoNR information element -- ASN1START -- TAG-CGI-INFO-NR-START CGI-InfoNR ::= SEQUENCE { plmn-IdentityInfoList PLMN-IdentityInfoListOPTIONAL, frequencyBandList MultiFrequencyBandListNROPTIONAL, noSIB1 SEQUENCE { ssb-SubcarrierOffset INTEGER (0..15), pdcch-ConfigSIB1 PDCCH-ConfigSIB1 OPTIONAL ... [[NPN-IdentityInfoList-r16 NPN-IdentityInfoListOPTIONAL ]] } -- TAG-CGI-INFO-NR-STOP -- ASN1STOP [...] – UAC-BarringPerPLMN-List The IE UAC-BarringPerPLMN-List provides access class-specific access control parameters, which are configured per PLMN.

[0126] UAC-BarringPerPLMN-List information elements -- ASN1START -- TAG-UAC-BARRINGPERPLMN-LIST-START UAC-BarringPerPLMN-List ::= SEQUENCE (SIZE (1..maxPLMN)) OFUAC-BarringPerPLMN UAC-BarringPerPLMN ::= SEQUENCE { plmn-IdentityIndex INTEGER (1..maxPLMN), uac-ACBarringListType CHOICE{ uac-ImplicitACBarringList SEQUENCE (SIZE(maxAccessCat-1)) OF UAC-BarringInfoSetIndex, uac-ExplicitACBarringList UAC-BarringPerCatList } OPTIONAL --Need S } -- TAG-UAC-BARRINGPERPLMN-LIST-STOP -- ASN1STOP While the topics described herein can be implemented in any suitable type of system using any appropriate components, the embodiments disclosed herein are relative to wireless networks (such as...). Figure 3 The example wireless network shown is used for description. For the sake of brevity, Figure 3 The wireless network shown only includes network 106, network nodes 160 and 160b, and WDs 110, 110b, and 110c. In practice, the wireless network may further include any additional elements suitable for supporting communication between wireless devices or between a wireless device and another communication device (such as a landline telephone, service provider, or any other network node or terminal device). Among the components shown, network node 160 and wireless device (WD) 110 are shown in additional detail. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate access and / or use of services provided by or via the wireless network.

[0127] Wireless networks may include any type of communications, telecommunications, data, cellular and / or radio network or other similar type of system and / or connected to it via an interface. In some embodiments, a wireless network may be configured to operate according to a specific standard or other type of predefined rules or procedures. Thus, specific embodiments of a wireless network may implement: communication standards such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE) and / or other suitable 2G, 3G, 4G or 5G standards; wireless local area network (WLAN) standards such as the IEEE 802.11 standard; and / or any other suitable wireless communication standards such as Global Microwave Access Interoperability (WiMax), Bluetooth, Z-Wave and / or ZigBee standards.

[0128] Network 106 may include one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTN), packet data networks, optical networks, wide area networks (WAN), local area networks (LAN), wireless local area networks (WLAN), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.

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

[0130] As used herein, a “network node” means a device that is capable of, configured to, arranged to, and / or operable to communicate directly or indirectly with a wireless device and / or with other network nodes or devices in a wireless network to enable and / or provide wireless access to the wireless device and / or perform other functions (e.g., management) in the wireless network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points) and base stations (BSs) (e.g., radio base stations, NodeBs, evolved Node Bs (eNBs), and NR NodeBs (gNBs)). Base stations can be classified based on the coverage they provide (or, in other words, their transmit power level) and may then be referred to as femtocells, picocells, microcells, or macrocells. A base station can be a relay node or a relay donor node that controls a relay. A network node may also include one or more (or all) portions of a distributed radio base station, such as a centralized digital unit and / or a remote radio unit (RRU), sometimes referred to as a remote radio headend (RRH). Such remote radio units may or may not be integrated with an antenna as an antenna-integrated radio. The distributed radio base station portion can also be referred to as a node in a distributed antenna system (DAS). Further examples of network nodes include multi-standard radio (MSR) equipment (such as an MSR BS), network controllers (such as a radio network controller (RNC) or base station controller (BSC)), base transceiver stations (BTS), transport points, transport nodes, multi-cell / multicast coordination entities (MCEs), core network nodes (e.g., mobile switching centers (MSCs), mobility management entities (MMEs)), operations and maintenance (O&M) nodes, operations support system (OSS) nodes, self-optimizing network (SON) nodes, location nodes (e.g., evolved servicing mobile location centers (E-SMLCs)), and / or minimized drive testing (MDTs). As another example, a network node can be a virtual network node as described in more detail below. However, more generally, a network node can represent any suitable device (or group of devices) capable of, configured to, arranged to, and / or operable to enable wireless devices to achieve and / or provide access to a wireless network or to provide a service to wireless devices already connected to a wireless network.

[0131] Figure 3In the network node 160, processing circuitry 170, device-readable medium 180, interface 190, auxiliary equipment 184, power supply 186, power circuitry 187, and antenna 162 are included. Although Figure 3 The network node 160 shown in the example wireless network may represent an apparatus including the illustrated combination of hardware components, but other embodiments may include network nodes having different combinations of components. It should be understood that a network node includes any suitable combination of hardware and / or software required to perform the tasks, features, functions, and methods disclosed herein. Furthermore, while the components of network node 160 are shown as a single box within a larger box or nested within multiple boxes, in practice, a network node may include multiple different physical components that make up a single illustrated component (e.g., apparatus-readable medium 180 may include multiple separate hard disk drives and multiple RAM modules).

[0132] Similarly, network node 160 may consist of multiple physically independent components (e.g., NodeB components and RNC components, or BTS components and BSC components, etc.), each of which may have its own corresponding components. In some cases where network node 160 includes multiple independent components (e.g., BTS and BSC components), one or more of the independent components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In this case, each unique NodeB and RNC pair may be considered a single independent network node in some instances. In some embodiments, network node 160 may be configured to support multiple Radio Access Technologies (RATs). In such embodiments, some components (e.g., independent device-readable media 180 for different RATs) may be duplicated, and some components (e.g., the same antenna 162 may be shared by RATs) may be reused. Network node 160 may also include multiple sets of various illustrated components of different wireless technologies (e.g., Global System for Mobile Communications (GSM), Wide Code Division Multiple Access (WCDMA), Long Term Evolution (LTE), New Radio (NR), WiFi, or Bluetooth wireless technologies) integrated into network node 160. These wireless technologies can be integrated into the same or different chips or chip sets and other components within network node 160.

[0133] Processing circuitry 170 is configured to perform any determination, calculation, or similar operation (e.g., certain acquisition operations) described herein as provided by a network node. These operations performed by processing circuitry 170 may include processing information acquired by processing circuitry 170 through steps such as: converting the acquired information into other information, comparing the acquired or converted information with information stored in the network node, and / or performing one or more operations based on the acquired or converted information, and making a determination as a result of said processing.

[0134] Processing circuitry 170 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 network node 160 components (such as device-readable medium 180) to provide the functionality of network node 160. For example, processing circuitry 170 may execute instructions stored in device-readable medium 180 or in memory within processing circuitry 170. Such functionality may include any wireless feature, function, or benefit that provides the various wireless features, functions, or benefits described herein. In some embodiments, processing circuitry 170 may include a system-on-a-chip (SoC).

[0135] In some embodiments, the processing circuitry 170 may include one or more of a radio frequency (RF) transceiver circuitry 172 and a baseband processing circuitry 174. In some embodiments, the RF transceiver circuitry 172 and the baseband processing circuitry 174 may be located on separate chips (or chip sets), boards, or units (such as radio units and digital units). In alternative embodiments, some or all of the RF transceiver circuitry 172 and the baseband processing circuitry 174 may be located on the same chip or chip set, board, or unit.

[0136] In some embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB, or other such network device may be executed by processing circuitry 170 by executing instructions stored in memory within processing circuitry 170 or on device-readable medium 180. In alternative embodiments, some or all of the functionality may be provided by processing circuitry 170, for example, in a hard-wired manner, without executing instructions stored on a separate or discrete device-readable medium. In any of those embodiments, processing circuitry 170 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 170 alone or other components of network node 160, but are generally enjoyed by network node 160 and / or generally by end users and wireless networks.

[0137] Device-readable medium 180 may include any form of volatile or non-volatile computer-readable memory, including, without limitation, permanent storage devices, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (e.g., hard disk), removable storage media (e.g., flash drives, CDs, or DVDs), and / or any other volatile or non-volatile non-transitory device-readable and / or computer-executable memory device that stores information, data, and / or instructions usable by processing circuitry 170. Device-readable medium 180 may store any suitable instructions, data, or information, including computer programs, software, applications (including one or more of logic, rules, codes, tables, etc.) and / or other instructions (which can be executed by processing circuitry 170 and utilized by network node 160). Device-readable medium 180 may be used to store any calculations performed by processing circuitry 170 and / or any data received via interface 190. In some embodiments, processing circuitry 170 and device-readable medium 180 may be considered integrated.

[0138] Interface 190 is used in wired or wireless communication of signaling and / or data between network node 160, network 106, and / or WD 110. As shown, interface 190 includes one or more ports / terminals 194 for sending and receiving data to and from network 106 via a wired connection, for example. Interface 190 also includes radio front-end circuitry 192, which may be coupled to antenna 162 or, in some embodiments, is part of antenna 162. Radio front-end circuitry 192 includes a filter 198 and an amplifier 196. Radio front-end circuitry 192 may be connected to antenna 162 and processing circuitry 170. Radio front-end circuitry 192 may be configured to modulate the signal transmitted between antenna 162 and processing circuitry 170. Radio front-end circuitry 192 may receive digital data that will be transmitted to other network nodes or WDs via a wireless connection. Radio front-end circuitry 192 may use a combination of filter 198 and / or amplifier 196 to convert the digital data into a radio signal with appropriate channel and bandwidth parameters. The radio signal may 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 then be passed to processing circuitry 170. In other embodiments, the interface may include different components and / or different combinations of components.

[0139] In some alternative embodiments, network node 160 may not include a separate radio front-end circuitry 192; instead, processing circuitry 170 may include the radio front-end circuitry and may be connected to antenna 162 without requiring a separate radio front-end circuitry 192. Similarly, in some embodiments, all or some of the RF transceiver circuitry 172 may be considered part of interface 190. In other embodiments, interface 190 may include one or more ports or terminals 194, radio front-end circuitry 192, and RF transceiver circuitry 172 as part of a radio unit (not shown), and interface 190 may communicate with baseband processing circuitry 174, which is part of a digital unit (not shown).

[0140] Antenna 162 may include one or more antennas or antenna arrays configured to transmit and / or receive wireless signals. Antenna 162 may be coupled to radio front-end circuitry 192 and may be any type of antenna capable of wirelessly transmitting and receiving data and / or signals. In some embodiments, antenna 162 may include one or more omnidirectional, sector, or planar antennas operable to transmit / receive radio signals, for example, between 2 GHz and 66 GHz. Omnidirectional antennas can be used to transmit / receive radio signals in any direction, sector antennas can be used to transmit / receive radio signals from devices within a specific area, and planar antennas may 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 may be referred to as MIMO. In some embodiments, antenna 162 may be detachable from network node 160 and may be connectable to network node 160 via an interface or port.

[0141] Antenna 162, interface 190, and / or processing circuitry 170 may be configured to perform any receive operation and / or certain acquire operation described herein as being performed by a network node. Any information, data, and / or signals may be received from a wireless device, another network node, and / or any other network device. Similarly, antenna 162, interface 190, and / or processing circuitry 170 may be configured to perform any transmit operation described herein as being performed by a network node. Any information, data, and / or signals may be transmitted to a wireless device, another network node, and / or any other network device.

[0142] Power circuit 187 may include or be coupled to power management circuitry and is configured to supply power to components of network node 160 for performing the functionality described herein. Power circuit 187 may receive power from power source 186. Power source 186 and / or power circuit 187 may be configured to supply power to various components of network node 160 in a form suitable to the respective components (e.g., at the voltage and current levels required by each respective component). Power source 186 may be included in power circuit 187 and / or network node 160 or external to power circuit and / or network node. For example, network node 160 may be connectable to an external power source (e.g., an electrical outlet) via input circuitry or an interface (such as a cable), whereby the external power source supplies power to power circuit 187. As a further example, power source 186 may include a power source in the form of a battery or battery pack, which is connected to or integrated into power circuit 187. The battery can provide backup power if the external power source fails. Other types of power sources (such as photovoltaic devices) may also be used.

[0143] Alternative embodiments of network node 160 may include, except Figure 3 In addition to the components shown herein, additional components may be responsible for providing certain aspects of the functionality of the network node, including any functionality described herein and / or any functionality required to support the topics described herein. For example, network node 160 may include a user interface device to allow information to enter into network node 160 and to allow information to exit from network node 160. This allows users to perform diagnostic, maintenance, repair, and other management functions of network node 160.

[0144] As used herein, “wireless device (WD)” means a device capable of, configured to, arranged to, and / or operable to wirelessly communicate with network nodes and / or other wireless devices. Unless otherwise stated, the term “WD” is used interchangeably with “User Equipment” herein. Wireless communication may involve transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for transmitting information over the air. In some embodiments, the WD may be configured to transmit and / or receive information without direct human interaction. For example, the WD may be designed to transmit information to the network based on a predetermined schedule, triggered by internal or external events, or in response to a request from the network. Examples of WDs include, but are not limited to, smartphones, mobile phones, cellular phones, Voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, game consoles or devices, music storage devices, playback devices, wearable terminal devices, wireless endpoints, mobile stations, tablets, laptops, laptop embedded devices (LEEs), laptop mounted devices (LMEs), smart devices, wireless client devices (CPEs), and in-vehicle wireless terminal devices. A WD may support device-to-device (D2D) communication, for example, by implementing 3GPP standards for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), and vehicle-to-everything (V2X), and in this case, may be referred to as a D2D communication device. As yet another specific example, in the context of the Internet of Things (IoT), a WD may represent a machine or other device that performs monitoring and / or measurement and transmits the results of such monitoring and / or measurement to another WD and / or network node. In this context, a WD can be a machine-to-machine (M2M) device, which may be referred to as an MTC device in the 3GPP context. As a specific example, a WD can be a UE implementing the 3GPP Narrowband Internet of Things (NB-IoT) standard. Specific examples of such machines or devices are sensors, metering devices (e.g., power meters), industrial machinery, or household or personal appliances (e.g., refrigerators, televisions, etc.), and wearable devices (e.g., watches, fitness trackers, etc.). In other cases, a WD can represent a vehicle or other device capable of monitoring and / or reporting its operational status or other functions associated with its operation. As described above, a WD can represent a wirelessly connected endpoint, in which case the device may be referred to as a wireless terminal. Furthermore, as described above, a WD can be mobile, in which case it may be referred to as a mobile device or mobile terminal.

[0145] As shown, the wireless device 110 includes an antenna 111, an interface 114, processing circuitry 120, a device-readable medium 130, a user interface device 132, auxiliary devices 134, a power supply 136, and a power circuit 137. WD 110 may include one or more of the components shown, representing various wireless technologies supported by WD 110, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, to name just a few. These wireless technologies may be integrated into a chip or set of chips that are the same as or different from other components within WD 110.

[0146] Antenna 111 may include one or more antennas or an antenna array configured to transmit and / or receive wireless signals and is connected to interface 114. In some alternative embodiments, antenna 111 may be detachable from WD 110 and may be connected to WD 110 via an interface or port. Antenna 111, interface 114, and / or processing circuitry 120 may be configured to perform any receive or transmit operations described herein as performed by a WD. Any information, data, and / or signals may be received from a network node and / or another WD. In some embodiments, radio front-end circuitry and / or antenna 111 may be considered as an interface.

[0147] As shown, 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 modulate the signal transmitted between antenna 111 and processing circuitry 120. Radio front-end circuitry 112 may be coupled to antenna 111 or is part of antenna 111. In some embodiments, WD 110 may not include a separate radio front-end circuitry 112; instead, processing circuitry 120 may include radio front-end circuitry and may be connected to antenna 111. Similarly, in some embodiments, some or all of RF transceiver circuitry 122 may be considered part of interface 114. Radio front-end circuitry 112 may receive digital data to be transmitted wirelessly to other network nodes or WD. Radio front-end circuitry 112 may use a combination of filters 118 and / or amplifiers 116 to convert the digital data into radio signals with appropriate channel and bandwidth parameters. The radio signals can then be transmitted via antenna 111. Similarly, when receiving data, antenna 111 can collect radio signals, which are then converted into digital data by radio front-end circuitry 112. The digital data can then be passed to processing circuitry 120. In other embodiments, the interface may include different components and / or different combinations of components.

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

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

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

[0151] Processing circuitry 120 may be configured to perform any determination, calculation, or similar operation (e.g., certain acquisition operations) described herein as being performed by the WD. Such operations performed by processing circuitry 120 may include processing information acquired by processing circuitry 120 by, for example, the following steps: converting the acquired information into other information, comparing the acquired or converted information with information stored in WD 110, and / or performing one or more operations based on the acquired or converted information, and making a determination as a result of said processing.

[0152] Device-readable medium 130 may be operable to store computer programs, software, applications (including one or more of logic, rules, code, tables, etc.) and / or other instructions (which can be executed by processing circuitry 120). Device-readable medium 130 may include computer memory (e.g., random access memory (RAM) or read-only memory (ROM)), mass storage media (e.g., hard disk), removable storage media (e.g., CD or DVD)) and / or any other volatile or non-volatile non-transitory device-readable and / or computer-executable memory device (which stores information, data, and / or instructions that can be used by processing circuitry 120). In some embodiments, processing circuitry 120 and device-readable medium 130 may be considered integrated.

[0153] User interface device 132 may provide components that allow a human user to interact with WD 110. This interaction may take many forms, such as visual, auditory, tactile, etc. User interface device 132 may be operable to produce outputs to the user and allow the user to provide inputs to WD 110. The type of interaction may vary depending on the type of user interface device 132 installed in WD 110. For example, if WD 110 is a smartphone, interaction may be via a touchscreen; if WD 110 is a smart meter, interaction may be via a screen providing usage (e.g., gallons used) or a speaker providing audible alarms (e.g., if smoke is detected). User interface device 132 may include input interfaces, means, and circuitry, as well as output interfaces, means, and circuitry. User interface device 132 is configured to allow input of information to WD 110 and is connected to processing circuitry 120 to allow processing circuitry 120 to process the input information. User interface device 132 may include, for example, a microphone, proximity or other sensors, buttons / buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface device 132 is also configured to allow output of information from WD 110, and to allow processing circuitry 120 to output information from WD 110. User interface device 132 may include, for example, a speaker, display, vibration circuitry, USB port, headphone jack, or other output circuitry. Using one or more input and output interfaces, devices, and circuitry of user interface device 132, WD 110 can communicate with end users and / or wireless networks, allowing them to benefit from the functionality described herein.

[0154] The auxiliary device 134 is operable to provide more specific functionality, which may generally not be performed by the WD. This may include dedicated sensors for measurements for various purposes, interfaces for additional types of communication (such as wired communication), etc. The inclusion and type of components of the auxiliary device 134 may vary depending on the embodiment and / or circumstances.

[0155] In some embodiments, power source 136 may take the form of a battery or battery pack. Other types of power sources may also be used, such as an external power source (e.g., an electrical outlet), a photovoltaic device, or a power battery. WD 110 may further include power circuitry 137 for supplying power from power source 136 to various portions of WD 110 that require power from power source 136 to perform any functionality described or shown herein. Power circuitry 137 may include power management circuitry in some embodiments. Additionally or alternatively, power circuitry 137 may be operable to receive power from an external power source; in this case, WD 110 may be connectable to an external power source (e.g., an electrical outlet) via input circuitry or an interface (e.g., a power cable). Power circuitry 137 may also be operable to supply power from an external power source to power source 136 in some embodiments. This may be used, for example, for charging power source 136. Power circuitry 137 may perform any formatting, conversion, or other modifications on the power from power source 136 to suit the power supplied to the respective components of WD 110.

[0156] Figure 4 An embodiment of a UE according to the various aspects described herein is illustrated. As used herein, "User Equipment" or "UE" may not necessarily have the meaning of a human user who owns and / or operates the associated device. Instead, UE may represent a device intended for sale to or operated by a human user, but may not or initially not be associated with a particular human user (e.g., a smart sprinkler controller). Alternatively, UE may represent a device not intended for sale to or operated by an end user, but may be associated with or operated for the benefit of a user (e.g., a smart power meter). UE 200 may be any UE recognized by the 3rd Generation Partnership Project (3GPP), including NB-IoT UEs, Machine Type Communication (MTC) UEs, and / or Enhanced MTC (eMTC) UEs. Figure 4 As shown, UE 200 is an example of a WD configured for communication according to one or more communication standards (such as 3GPP's GSM, UMTS, LTE, and / or 5G standards) issued by the 3rd Generation Partnership Project (3GPP). As previously stated, the terms "WD" and "UE" can be used interchangeably. Accordingly, although... Figure 4 It is a UE, but the components described in this article are also applicable to WD, and vice versa.

[0157] Figure 4In this embodiment, UE 200 includes: processing circuitry 201 operatively coupled to input / output interface 205; radio frequency (RF) interface 209; network connectivity interface 211; memory 215, including random access memory (RAM) 217, read-only memory (ROM) 219, and storage medium 221 or similar; communication subsystem 231; power supply 213; and / or any other components; or any combination thereof. Storage medium 221 contains operating system 223, application programs 225, and data 227. In other embodiments, storage medium 221 may include other similar types of information. Some UEs may utilize... Figure 4 The components shown can be all or only a subset of the components. The level of integration between components can be changed on a per-UE basis. In addition, some UEs may contain multiple instances of components, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0158] Figure 4 In this embodiment, processing circuitry 201 can be configured to process computer instructions and data. Processing circuitry 201 can be configured to implement: any sequential state machine operable to execute machine instructions stored in memory as a machine-readable computer program, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic along with appropriate firmware; one or more stored-program general-purpose processors, such as microprocessors or digital signal processors (DSPs), along with appropriate software; or any combination thereof. For example, processing circuitry 201 may include two central processing units (CPUs). Data may be information in a form suitable for computer use.

[0159] In the illustrated embodiment, the input / output interface 205 can be configured to provide a communication interface to an input device, an output device, or both input and output devices. The UE 200 can be configured to use an output device via the input / output interface 205. The output device can use an interface port of the same type as the input device. For example, a USB port can be used to provide input to and output from the UE 200. The output device can be a speaker, sound card, video card, display, monitor, printer, actuator, transmitter, smart card, another output device, or any combination thereof. The UE 200 can be configured to use an input device via the input / output interface 205 to allow a user to capture information entering the UE 200. The input device can include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, digital video camera, webcam, etc.), a microphone, a sensor, a mouse, a trackball, a navigation pad, a scroll wheel, a smart card, and the like. A presence-sensitive display can include a capacitive or resistive touch sensor to sense input from the 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 similar 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.

[0160] Figure 4 In this configuration, RF interface 209 can be configured to provide a communication interface to RF components such as transmitters, receivers, and antennas. Network connectivity interface 211 can be configured to provide a communication interface to network 243a. Network 243a may include wired and / or wireless networks, such as local area networks (LANs), wide area networks (WANs), computer networks, wireless networks, telecommunications networks, another similar network, or any combination thereof. For example, network 243a may include a Wi-Fi network. Network connectivity interface 211 can be configured to include receiver and transmitter interfaces for communicating with one or more other devices over the communication network according to one or more communication protocols such as Ethernet, TCP / IP, SONET, ATM, or the like. Network connectivity interface 211 can implement receiver and transmitter functionality suitable for communication network links (e.g., optical, electrical, and the like). Transmitter and receiver functionality may share circuit components, software, or firmware, or alternatively may be implemented separately.

[0161] RAM 217 can be configured to interface with processing circuitry 201 via bus 202 to provide storage or caching of data or computer instructions during the execution of software programs (such as operating systems, applications, and device drivers). ROM 219 can be configured to provide computer instructions or data to processing circuitry 201. For example, ROM 219 can be configured to store immutable low-level system code or data for basic system functions such as basic input and output (I / O), startup, or reception of keystrokes from a keyboard, stored in non-volatile memory. 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), disk, optical disk, floppy disk, hard disk, removable magnetic tape, or flash drive. In one example, storage medium 221 can be configured to include operating system 223, application program 225 (such as a web browser application, widget or accessory engine, or another application), and data file 227. Storage medium 221 can store any operating system or combination of operating systems for use by UE200.

[0162] Storage medium 221 may be configured to include multiple physical drive units, such as a redundant array of independent disks (RAID), a floppy disk drive, flash memory, a USB flash drive, an external hard disk drive, a thumb drive, a pen drive, a key drive, a high-density digital multifunction disc (HD-DVD) optical disc drive, an internal hard disk drive, a Blu-ray disc drive, a holographic digital data storage (HDDS) optical disc drive, an external micro dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro DIMM SDRAM, smart card memory (such as a subscriber identification module or a removable subscriber identification (SIM / RUIM) module), other memory, or any combination thereof. Storage medium 221 may allow UE 200 to access computer-executable instructions, applications, or the like stored on transient or non-transient storage media to offload or upload data. Manufactured products (such as manufactured products utilizing communication systems) may be tangibly embodied in storage medium 221, which may include device-readable media.

[0163] Figure 4In this configuration, processing circuitry 201 can be configured to communicate with network 243b using communication subsystem 231. Networks 243a and 243b can be one or more of the same networks or one or more different networks. Communication subsystem 231 can be configured to include one or more transceivers for communicating with network 243b. For example, communication subsystem 231 can be configured to include one or more transceivers for communicating with one or more remote transceivers of another device (such as another WD, UE, or base station of a radio access network (RAN)) 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 respectively implement transmitter or receiver functionality suitable for the RAN link (e.g., frequency allocation and the like). Furthermore, the transmitter 233 and receiver 235 of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately.

[0164] In the illustrated embodiment, the communication functions of the communication subsystem 231 may include data communication, voice communication, multimedia communication, short-range communication (such as Bluetooth, near-field communication), location-based communication (such as Global Positioning System (GPS) for determining location), another similar communication function, or any combination thereof. For example, the communication subsystem 231 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. The network 243b may include 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 similar network, or any combination thereof. For example, the network 243b may be a cellular network, a Wi-Fi network, and / or a near-field network. The power supply 213 may be configured to provide alternating current (AC) or direct current (DC) power to the components of the UE 200.

[0165] The features, benefits, and / or functions described herein may be implemented in one of the components of UE 200, or divided across multiple components of UE 200. Furthermore, the features, benefits, and / or functions described herein may be implemented through any combination of hardware, software, or firmware. In one example, communication subsystem 231 may be configured to include any component described herein. Additionally, processing circuitry 201 may be configured to communicate with any component of such components via bus 202. In another example, any component of such components may be represented by program instructions stored in memory, which, when executed by processing circuitry 201, perform the corresponding functions described herein. In another example, the functionality of any component of such components may be divided between processing circuitry 201 and communication subsystem 231. In yet another example, non-computationally intensive functions of any component of such components may be implemented in software or firmware, while computationally intensive functions may be implemented in hardware.

[0166] Figure 5 This is a schematic block diagram illustrating a virtualized environment 300, in which functionality implemented through some embodiments can be virtualized. In this context, virtualization means creating a virtual version of a device or apparatus, which may include virtualizing hardware platforms, storage devices, and networking resources. As used herein, virtualization can be applied to nodes (e.g., virtualized base stations or virtualized radio access nodes) or to apparatuses (e.g., UEs, wireless devices, or any other type of communication device) or their components, and involves at least a portion of its functionality being implemented as an implementation of one or more virtual components (e.g., one or more applications, components, functions, virtual machines, or containers executed via one or more physical processing nodes in one or more networks).

[0167] In some embodiments, some or all of the functionality described herein may be implemented as virtual components executed by one or more virtual machines (which are implemented in one or more virtual environments 300 hosted by one or more hardware nodes in hardware node 330). Furthermore, in embodiments where the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), the network node may be fully virtualized.

[0168] The functionality may be implemented by one or more applications 320 (which may alternatively be referred to as software instances, virtual devices, network functions, virtual nodes, virtual network functions, etc.), said applications being operable to implement some of the features, functions, and / or benefits of some embodiments disclosed herein. Application 320 runs in a virtualization environment 300, which provides hardware 330 including processing circuitry 360 and memory 390. Memory 390 contains instructions 395 executable by the processing circuitry 360, thereby enabling application 320 to operate to provide one or more of the features, benefits, and / or functions disclosed herein.

[0169] The virtualization environment 300 includes general-purpose or special-purpose network hardware devices 330, which include a collection of one or more processors or processing circuits 360. These processors or processing circuits may be commercial off-the-shelf (COTS) processors, 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 may include a memory 390-1, which may be a non-permanent memory for temporarily storing instructions 395 or software executed by the processing circuits 360. Each hardware device may include one or more network interface controllers (NICs) 370 (also referred to as network interface cards), which include physical network interfaces 380. Each hardware device may also include a non-transitory permanent machine-readable storage medium 390-2, which stores software 395 and / or instructions executable by the processing circuits 360. The software 395 may include any type of software, including software for executing one or more virtualization layers 350 (also referred to as hypervisors), software for executing virtual machines 340, and software that allows it to perform the functions, features, and / or benefits described in relation to some embodiments described herein.

[0170] Virtual machine 340 includes virtual processing, virtual memory, virtual networking or interfaces, and virtual storage devices, and can be run by a corresponding virtualization layer 350 or hypervisor. Different embodiments of instances of virtual device 320 may be implemented on one or more virtual machines 340, and the implementation may be carried out in different ways.

[0171] During operation, processing circuitry 360 executes software 395 to executor a hypervisor or virtualization layer 350, sometimes referred to as a virtual machine monitor (VMM). Virtualization layer 350 provides a virtual operating platform that appears to the virtual machine 340 as networked hardware.

[0172] like Figure 5As shown, hardware 330 can be a standalone network node with general or specific components. Hardware 330 may include antenna 3225 and may implement some functions via virtualization. Alternatively, hardware 330 may be part of a larger cluster of hardware (e.g., in a data center or customer premises equipment (CPE)) in which many hardware nodes work together and are managed via management and orchestration (MANO) 3100, which, among other things, oversees the lifecycle management of application 320.

[0173] Hardware virtualization is sometimes referred to as Network Functions Virtualization (NFV). NFV can be used to consolidate many types of network devices onto industry-standard high-capacity server hardware, physical switches, and physical storage devices, which can reside in data centers and client devices.

[0174] In the context of NFV, virtual machine 340 can be a software implementation of a physical machine that runs programs as if they were executed on a physical, non-virtualized machine. Each virtual machine 340 and the portion of hardware 330 in which that virtual machine is executed (if it is hardware dedicated to that virtual machine and / or hardware shared by that virtual machine and other virtual machines of virtual machine 340) form an independent virtual network element (VNE).

[0175] In the context of NFV, a Virtual Network Function (VNF) is responsible for controlling specific network functions running in one or more virtual machines 340 on top of the hardware networking infrastructure 330, and corresponds to Figure 5 Application 320.

[0176] In some embodiments, one or more radio units 3200, each including one or more transmitters 3220 and one or more receivers 3210, may be coupled to one or more antennas 3225. The radio unit 3200 may communicate directly with the hardware node 330 via one or more suitable network interfaces and may be combined with virtual components to provide radio capabilities (such as radio access nodes or base stations) for virtual nodes.

[0177] In some embodiments, some signaling can be implemented using a control system 3230, which can alternatively be used for communication between hardware node 330 and radio unit 3200.

[0178] Reference Figure 6According to an embodiment, the communication system includes a telecommunications network 410 (such as a 3GPP-type cellular network), which includes an access network 411 (such as a radio access network) and a core network 414. The access network 411 includes multiple 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 can be connected to the core network 414 via 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 located in coverage area 413a can wirelessly connect to the corresponding base station 412a. Although multiple UEs 491, 492 are shown in this example, the disclosed embodiments are equally applicable to situations where a single UE is located in a coverage area or where a single UE is connected to a corresponding base station 412.

[0179] Telecommunications network 410 is itself connected to host computer 430, which may be embodied in the hardware and / or software of a standalone server, a cloud-implemented server, a distributed server, or as a processing resource in a server farm. Host computer 430 may be owned or controlled by a service provider, or may be operated by or on behalf of the service provider. Connections 421 and 422 between telecommunications network 410 and host computer 430 may extend directly from core network 414 to host computer 430, or may be made via optional intermediate network 420. Intermediate network 420 may be one or more of public, private, or hosted networks; intermediate network 420 (if any) may be a backbone network or the Internet; in particular, intermediate network 420 may include two or more subnetworks (not shown).

[0180] Figure 6The overall communication system enables connectivity between the connected UEs 491 and 492 and the host computer 430. This connectivity can be described as an over-the-top (OTT) connection 450. The host computer 430 and the connected UEs 491 and 492 are configured to transmit data and / or signaling via the OTT connection 450 using the access network 411, core network 414, any intermediate network 420, and further possible infrastructure (not shown) as intermediaries. The OTT connection 450 can be transparent in the sense that the participating communication devices within it are unaware of the routing of uplink and downlink communications. For example, the base station 412 may not be informed, or need not be informed, of past routing for incoming downlink communications (where data originates from the host computer 430 to be forwarded (e.g., switched) to the connected UE 491). Similarly, the base station 412 does not need to know the future routing for outgoing uplink communications originating from UE 491 to the host computer 430.

[0181] Now refer to Figure 7 The following describes an example implementation of the UE, base station, and host computer described above according to an embodiment. In the communication system 500, the host computer 510 includes hardware 515, which includes a communication interface 516 configured to establish and maintain wired or wireless connections with interfaces of different communication devices of the communication system 500. The host computer 510 further includes processing circuitry 518, which may have storage and / or processing capabilities. In particular, the processing circuitry 518 may include one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or combinations of these devices (not shown) suitable for executing instructions. The host computer 510 further includes software 511, which is stored in the host computer 510 or accessible to the host computer 510 and executable by the processing circuitry 518. The software 511 includes a host application 512. The host application 512 may be operable to provide services to remote users, such as a UE 530 connected via an OTT connection 550 terminated between the UE 530 and the host computer 510. In providing services to remote users, host application 512 can provide user data transmitted using OTT connection 550.

[0182] The communication system 500 further includes a base station 520, provided in a telecommunications system, and includes hardware 525 enabling it to communicate with a host computer 510 and a UE 530. Hardware 525 may include: a communication interface 526 for establishing and maintaining wired or wireless connections with different communication devices of the communication system 500; and a radio interface 527 for establishing and maintaining at least a wireless connection 570 with the UE 530, the UE being located within the coverage area served by the base station 520. Figure 7(Not shown in the image). Communication interface 526 can be configured to facilitate a connection 560 to host computer 510. Connection 560 can be direct, or it can be via the core network of a telecommunications system (…). Figure 7 (Not shown) and / or via one or more intermediate networks outside the telecommunications system. In the illustrated embodiment, the hardware 525 of base station 520 further includes processing circuitry 528, which may include one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or combinations of such devices (not shown) suitable for executing instructions. Base station 520 further has software 521, which is either internally stored or accessible via an external connection.

[0183] The communication system 500 further includes the previously mentioned UE 530. Its hardware 535 may include a radio interface 537 configured to establish and maintain a wireless connection 570 with a base station serving the coverage area currently occupied by the UE 530. The hardware 535 of the UE 530 further includes processing circuitry 538, which may include one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or combinations of these devices (not shown) suitable for executing instructions. The UE 530 further includes software 531, which is stored in or accessible to the UE 530 and executable by the processing circuitry 538. The software 531 includes a client application 532. The client application 532 may be operable to provide services to human or non-human users via the UE 530 with the support of a host computer 510. In the host computer 510, a host application 512 may communicate with the client application 532 via an OTT connection 550 terminated between the UE 530 and the host computer 510. When providing services to a user, client application 532 can receive request data from host application 512 and provide user data in response to the request data. OTT connection 550 can transmit both request data and user data. Client application 532 can interact with the user to generate the user data it provides.

[0184] Please note, Figure 7 The host computer 510, base station 520, and UE 530 shown can be respectively connected to Figure 6 The host computer 430, base stations 412a, 412b, and 412c, and UEs 491 and 492 are similar to or identical to each other. That is, the internal workings of these entities can be as follows: Figure 7 As shown, and the surrounding network topology can be independently... Figure 6 The topology.

[0185] Figure 7The diagram abstractly depicts OTT connection 550 to illustrate communication between host computer 510 and UE 530 via base station 520, without explicitly mentioning any intermediate devices or the precise routing of messages via these devices. The network infrastructure can determine the routing, configuring it to be either for UE 530 or for the service provider operating host computer 510, or hidden from both. While OTT connection 550 is active, the network infrastructure can further make decisions, dynamically altering the routing (e.g., based on network load balancing considerations or reconfiguration).

[0186] The wireless connection 570 between UE 530 and base station 520 is based on the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments utilize OTT connection 550 to improve the performance of OTT services provided to UE 530, wherein wireless connection 570 forms the final segment. More precisely, the teachings of these embodiments can improve data rates, latency, power consumption, and thereby provide benefits such as reduced user wait times, relaxed file size restrictions, better responsiveness, or extended battery life.

[0187] Measurement procedures may be provided for the purpose of monitoring data rates, latency, and other factors improved in one or more embodiments. Optional network functionality may further exist for reconfiguring the OTT connection 550 between host computer 510 and UE 530 in response to changes in measurement results. The measurement procedures and / or the network functionality for reconfiguring the OTT connection 550 may be implemented in the software 511 and hardware 515 of host computer 510, or in the software 531 and hardware 535 of UE 530, or both. In embodiments, sensors (not shown) may be deployed in or associated with communication devices within the OTT connection 550; the sensors may participate in the measurement procedures by providing values ​​of the monitored quantities exemplified above, or by providing values ​​of other physical quantities from which the software 511, 531 can calculate or estimate the monitored quantities. Reconfiguration of the OTT connection 550 may include message formats, retransmission settings, preferred routing, etc.; reconfiguration does not affect base station 520, and may be unknown or undetectable to base station 520. Such procedures and functionalities are known and practiced in the art. In some embodiments, the measurement may involve proprietary UE signaling that facilitates the host computer 510 to measure throughput, propagation time, latency, and the like. Measurements are made possible because software 511 and 531 enable messages to be transmitted using OTT connection 550, particularly empty or 'fake' messages, while it monitors propagation time, errors, etc.

[0188] Figure 8This 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 aforementioned host computers, base stations, and UEs. For the sake of brevity, this section will only include descriptions of... Figure 8 The accompanying drawings are referenced. In step 610, the host computer provides user data. In sub-step 611 of step 610 (which may be optional), the host computer provides user data by executing a host application. In step 620, the host computer initiates a transmission carrying user data to the UE. According to the teachings of the embodiments described throughout this disclosure, in step 630 (which may be optional), the base station transmits user data to the UE, the user data being carried in the transmission initiated by the host computer. In step 640 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

[0189] Figure 9 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 aforementioned host computers, base stations, and UEs. For the sake of brevity, this section will only include descriptions of... Figure 9 The accompanying drawings are referenced. In step 710 of the method, the host computer provides user data. In an optional sub-step (not shown), the host computer provides user data by executing a host application. In step 720, the host computer initiates a transmission carrying user data to the UE. According to the teachings of the embodiments described throughout this disclosure, the transmission may be carried out via a base station. In step 730 (which may be optional), the UE receives the user data carried in the transmission.

[0190] Figure 10 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 aforementioned host computers, base stations, and UEs. For the sake of brevity, this section will only include descriptions of... 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.

[0191] 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 aforementioned host computers, base stations, and UEs. 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.

[0192] Any suitable steps, methods, features, functions, or benefits disclosed herein may be performed by one or more functional units or modules of one or more virtual devices. Each virtual device may include multiple such functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessors or microcontrollers and may include digital signal processors (DSPs), application-specific digital logic, and other digital hardware such as these. 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 (RAM), cache memory, flash memory devices, optical storage devices, etc. 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, according to one or more embodiments of this disclosure, the processing circuitry may be used to cause corresponding functional units to perform corresponding functions.

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

[0194] Figure 13 A method according to a specific embodiment is illustrated. In some embodiments, the method may be performed by a wireless device (such as wireless device 110 or UE described above) or by a network node (such as network node 160 described above) to generate a network index corresponding to an NPN index of a combination of PLMN and CAG ID or an index of a combination of PLMN and Network ID (NID). In step 1301, the method determines whether a list of non-public network identifiers (NPNs) included in system information broadcast by the network node includes at least an element containing at least one CAG identifier and / or at least an element containing at least one NID identifier. In step 1302, in response to determining that 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, the method generates a CAG index based at least in part on the number of PLMN elements included in combination with cag-IdentityList elements. In step 1303, in response to determining that 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, the method generates an NID index based at least in part on the number of NIDs included in the nid-List. In some embodiments, steps 1302 and / or 1303 may be optional, for example, depending on the result of the determination made in step 1301. In some embodiments, step 1302 may be omitted if the list of non-public network identifiers determined in step 1301 does not include at least one element containing at least one CAG identifier. In some embodiments, step 1303 may be omitted if the list of non-public network identifiers determined in step 1301 does not include at least one element containing at least one NID identifier.

[0195] Figure 14 Show wireless networks (e.g.) Figure 3 A schematic block diagram of device 1400 in a wireless network (as shown in the diagram). The device may be a wireless device or a network node (e.g., [missing information]). Figure 3 This is implemented in the wireless device 110 or network node 160 shown. Device 1400 is operable to perform the reference... Figure 13 The example methods described herein, as well as any other possible processes or methods disclosed herein, should also be understood. Figure 13 The method is not necessarily performed solely by device 1400. At least some operations of the method can be performed by one or more other entities.

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

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

[0198] Other embodiments may allocate functionality among the system information unit 1402, CAD index unit 1404, and NID index unit 1406 in any other suitable manner. As an example, in some embodiments, the system information unit 1402 may 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 index unit 1404 and the NID index unit 1406. The CAD index unit 1404 may be configured to determine whether the list of NPNs includes at least one element containing at least one CAG identifier and whether it includes such an element. If yes, the CAD index unit 1404 may be further configured to generate a CAG index based at least in part on the number of PLMN elements contained in the cag-IdentityList. The NID index unit 1406 may be configured to determine whether the list of NPNs includes at least one element containing at least one NID identifier and whether it includes such an element. If yes, the NID index unit 1406 may be further configured to generate an NID index based at least in part on the number of NIDs contained in the nid-List.

[0199] The term “unit” may have the conventional meaning in the field of electronic, electrical and / or electronic devices, and may include, for example, electrical and / or electronic circuits, devices, modules, processors, memories, logic solid-state and / or discrete devices, computer programs or instructions for performing corresponding tasks, processes, calculations, output and / or display functions, etc., as described herein.

[0200] 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 a further example, the instructions are carried on a signal or carrier and are executable on a computer, wherein, when executed, they perform any of the embodiments disclosed herein. Example

[0201] Group A Examples 1. A method for generating a network index in a radio device (e.g., a UE) corresponding to a non-public network (NPN) index that is a combination of a Public Land Mobile Network (PLMN) and a Closed Access Group (CAG) ID, or an index that is a combination of a PLMN and a Network ID (NID), wherein the generation includes the following steps: - Detection system information broadcast, which includes a list of non-public network identifiers (NPNs); - Whether the list of non-public network identifiers includes at least one element containing at least one CAG identifier and whether it includes such an element; - The CAG index is generated based at least in part on the number of PLMN elements that are included in combination with the cag-IdentityList elements; - Whether the list identifying non-public network identifiers includes at least one element containing at least one NID identifier and whether it includes such an element; and - The NID index is generated based at least in part on the number of NIDs contained in the nid-list.

[0202] 2. According to the method of Embodiment 1, the generation of the CAG index further considers whether there is a list of PLMN identifiers contained in the system information broadcast, and if so, arranges the CAG indexes such that they inherit the index values ​​generated by the PLMN identifiers.

[0203] 3. According to the method of Embodiment 1, the generation of the NID index further considers whether there is a list of PLMN identifiers contained in the system information broadcast, and if so, arranges the NID indexes such that they inherit the index values ​​generated by the CAG index.

[0204] 4. According to the method of Example 1, generating the CAG or NID index further includes the following steps: - Detect the value of the cellReservedForOtherUse parameter and when that parameter is set to true; - Generate a CAG index, assuming no previous PLMN index value exists; and - Generate NID index, assuming no previous PLMN index value exists.

[0205] 5. The method according to any embodiment of the preceding embodiments, wherein the generated index is used when transmitting an RRC establishment complete message, the index being included in the message as a representation of the network to which it requests access.

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

[0207] 7. According to the method of embodiment 6, wherein the amount of network identifiers associated with the first system information broadcast corresponds to the amount of human-readable network name elements in the second system information broadcast.

[0208] 8. According to the method of embodiment 7, at least one of the human-readable network name elements is assigned to a value that is broadcast as "no name".

[0209] 9. A method for verifying system information in a wireless device (e.g., a UE), wherein the verification steps include: - Read the cellReservedForOtherUse parameter; and - If the cellReservedForOtherUse parameter has a value of "true", then select a network identifier from the NPN-IdentityInfoList; and if the cellReservedForOtherUse parameter has a value of "false", then select a network identifier from the PLMN-IdentityInfoList.

[0210] 10. The method according to embodiment 9, wherein the selection includes selecting a first network identifier from any list of lists.

[0211] 11. A method for verifying system information in a wireless device (e.g., a UE), wherein the verification steps include: - Read the first element from the PLMN -IdentityInfo list; and - If the first element is detected as a standardized element indicating that no normal service is available, then a network identifier is selected from the NPN-IdentityInfoList for use in verifying system information.

[0212] 12. The method of any embodiment of the preceding embodiments, further comprising: - Provide user data; and - User data is forwarded to the host computer via transmission to the base station.

[0213] Group B Implementation Examples 13. A method for generating a network index in a network node corresponding to an NPN index that is a combination of a PLMN and a CAG ID, or an index that is a combination of a PLMN and a network ID (NID), wherein the generation includes the following steps: The system information broadcast by the network node includes a list of non-public network identifiers (NPNs); - If the list of non-public network identifiers includes at least one element containing at least one CAG identifier, and if it includes such an element, the CAG index is generated at least in part based on the number of PLMN elements that are included in combination with the cag-IdentityList elements; and - If the list of non-public network identifiers includes at least one element containing at least one NID identifier, and if it includes such an element, then the NID index is generated at least in part based on the number of NIDs contained in the nid-list.

[0214] 14. According to the method of embodiment 13, when broadcasting or transmitting unified access control parameters, the network node associates the NID index with a reference.

[0215] 15. The method of any embodiment of the preceding embodiments, further comprising: - Obtain user data; and - Forward user data to the host computer or wireless device.

[0216] Group C Implementation Examples 16. A wireless device, the wireless device comprising: - Processing circuitry, configured to perform any step of any embodiment of the Group A embodiments; and - A power supply circuit configured to supply power to the wireless device.

[0217] 17. A base station, the base station comprising: - Processing circuitry configured to perform any step of any embodiment of the Group B embodiments; - A power supply circuit configured to supply power to the base station.

[0218] 18. A user equipment (UE), the UE comprising: - Antenna, configured to transmit and receive wireless signals; - Radio front-end circuitry, connected to the antenna and to the processing circuitry, and configured to regulate the signal transmitted between the antenna and the processing circuitry; - Processing circuitry configured to perform any step of any embodiment of the Group A embodiments; - An input interface, connected to the processing circuitry, is configured to allow information to be input into the UE for processing by the processing circuitry; - An output interface, connected to the processing circuitry, and configured to output information processed by the processing circuitry from the UE; and - The battery is connected to the processing circuitry and configured to supply power to the UE.

[0219] 19. A computer program comprising instructions that, when executed on a computer, perform any step of any embodiment of the Group A embodiments.

[0220] 20. A computer program product comprising a computer program, the computer program including instructions that, when executed on a computer, perform any step of any embodiment of the Group A embodiments.

[0221] 21. A non-transitory computer-readable storage medium or carrier comprising a computer program, said computer program comprising instructions that, when executed on a computer, perform any step of any embodiment of the Group A embodiments.

[0222] 22. A computer program comprising instructions that, when executed on a computer, perform any step of any embodiment of the Group B embodiments.

[0223] 23. A computer program product comprising a computer program, the computer program including instructions that, when executed on a computer, perform any step of any embodiment of the Group B embodiments.

[0224] 24. A non-transitory computer-readable storage medium or carrier comprising a computer program, said computer program comprising instructions that, when executed on a computer, perform any step of any embodiment of the Group B embodiments.

[0225] 25. A communication system including a host computer, the host computer comprising: - Processing circuitry, configured to provide user data; and - A communication interface configured to forward user data to the cellular network for transmission to the user equipment (UE). - The cellular network includes a base station having a radio interface and processing circuitry, the processing circuitry of which is configured to perform any step of any embodiment of the Group B embodiments.

[0226] 26. The communication system of the previous embodiment further includes a base station.

[0227] 27. The communication system of the first two embodiments further includes a UE, wherein the UE is configured to communicate with a base station.

[0228] 28. The communication system of the first three embodiments, wherein: - The host computer's processing circuitry is configured to execute host applications, thereby providing user data; and - The UE includes processing circuitry configured to execute a client application associated with a host application.

[0229] 29. A method implemented in a communication system, the communication system comprising a host computer, a base station, and a user equipment (UE), the method comprising: - Providing user data on the host computer; and - When a host computer initiates the transmission of user data to a UE via a cellular network, the cellular network including a base station, wherein the base station performs any step of any embodiment of the Group B embodiments.

[0230] 30. The method of the previous embodiment further includes transmitting user data at the base station.

[0231] 31. The method of the first two embodiments, wherein user data is provided on a host computer by executing a host application, the method further comprising executing a client application associated with the host application on the UE.

[0232] 32. A user equipment (UE) configured to communicate with a base station, the UE including a radio interface and processing circuitry configured to perform the methods described in the preceding three embodiments.

[0233] 33. A communication system including a host computer, the host computer comprising: - Processing circuitry, configured to provide user data; and - A communication interface configured to forward user data to the cellular network for transmission to the user equipment (UE). - The UE includes a radio interface and processing circuitry, and the components of the UE are configured to perform any step of any embodiment of the Group A embodiments.

[0234] 34. The communication system of the prior embodiment, wherein the cellular network further includes a base station configured to communicate with the UE.

[0235] 35. The communication system of the first two embodiments, wherein: - The host computer's processing circuitry is configured to execute host applications, thereby providing user data; and - The UE's processing circuitry is configured to execute client applications associated with the host application.

[0236] 36. A method implemented in a communication system, the communication system comprising a host computer, a base station, and a user equipment (UE), the method comprising: - Providing user data on the host computer; and - When a host computer initiates the transmission of user data to a UE via a cellular network, the cellular network including a base station, the UE performs any step of any embodiment of the Group A embodiments.

[0237] 37. The method of the previous embodiment further includes the UE receiving user data from the base station.

[0238] 38. A communication system including a host computer, the host computer comprising: - Communication interface, configured to receive user data transmitted from the user equipment (UE) to the base station. - The UE includes a radio interface and processing circuitry, the processing circuitry of which is configured to perform any step of any embodiment of the Group A embodiments.

[0239] 39. The communication system of the previous embodiment further includes a UE.

[0240] 40. The communication system of the first two embodiments further includes a base station, wherein the base station includes: 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 a host computer.

[0241] 41. The communication system of the first three embodiments, wherein: - The host computer's processing circuitry is configured to execute host applications; and - The UE's processing circuitry is configured to execute client applications associated with the host application, thereby providing user data.

[0242] 42. The communication system of the first four embodiments, wherein: - The host computer's processing circuitry is configured to execute host applications, thereby providing requested data; and - The UE's processing circuitry is configured to execute a client application associated with the host application, thereby providing user data in response to requested data.

[0243] 43. A method implemented in a communication system, the communication system comprising a host computer, a base station, and a user equipment (UE), the method comprising: - When a host computer receives user data transmitted from a UE to a base station, the UE performs any step of any embodiment of the Group A embodiments.

[0244] 44. The method of the prior embodiment further includes providing user data to the base station at the UE.

[0245] 45. The method of the first two embodiments further includes: - In the UE, the client application is executed, thereby providing user data for transmission; and - Execute the host application associated with the client application on the host computer.

[0246] 46. ​​The method of the first three embodiments further includes: - Executing client applications in UE; and - When the UE receives input data for a client application, the input data is provided on the host computer by executing a host application associated with the client application. - The user data to be transmitted is provided by the client application in response to input data.

[0247] 47. A communication system comprising a host computer including a communication interface configured to receive user data transmitted from a user equipment (UE) to a base station, wherein the base station includes a radio interface and processing circuitry configured to perform any step of any embodiment of the Group B embodiments.

[0248] 48. The communication system of the previous embodiment further includes a base station.

[0249] 49. The communication system of the first two embodiments further includes a UE, wherein the UE is configured to communicate with a base station.

[0250] 50. The communication system of the first three embodiments, wherein: - The host computer's processing circuitry is configured to execute host applications; - The UE is configured to execute a client application associated with the host application, thereby providing user data for the host computer to receive.

[0251] 51. A method implemented in a communication system, the communication system comprising a host computer, a base station, and a user equipment (UE), the method comprising: - When the host computer receives user data transmitted from the base station that has been received by the base station from the UE, the UE performs any step of any embodiment of the Group A embodiments.

[0252] 52. The method of the previous embodiment further includes receiving user data from the UE at the base station.

[0253] 53. The method of the first two embodiments further includes initiating the transmission of received user data from the base station to the host computer.

[0254] 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 described respectively. For example, the wireless device may include processing circuitry, such as processing circuitry 120 or one or more processors, configured to perform one or more steps of one or more methods performed by the wireless device. A network node (such as network node 160) may be configured to perform similar or reciprocal functionality. For example, some embodiments describe a wireless device that sends a message to a network node. In a reciprocal embodiment, the network node receives that message from the wireless device. Similarly, some embodiments describe a wireless device that receives a message from a network node. In a reciprocal embodiment, the network node sends that message to the wireless device. A network node may include processing circuitry, such as processing circuitry 170, configured to perform one or more steps of one or more methods performed by the network node. Figure 20 , Figure 21 and Figure 22 Provides functions that can be performed by network nodes to support separate operations by Figure 17 , Figure 18 and Figure 19 Examples of functional methods performed by wireless devices.

[0255] Now go to Figure 15A and Figure 15B The method, the method begins at Figure 15A Step 1502 involves detecting system information broadcast from the network node. The system information includes a list of NPN identifiers. The method continues to step 1504, where a network index is generated based on the system information. Step 1504 may include... Figure 15B One or more steps / substeps are shown. 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 may include a CAG index (e.g., an index including one or more CAG index values) and / or a NID index (e.g., an index including one or more NID index values). Further information regarding the CAG index can be found in […]. Figure 15B The discussion of steps 1506 and 1508, as well as further information related to the NID index, can be found in [link to relevant documentation]. Figure 15B The discussion of steps 1510 and 1512.

[0256] In 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 may skip 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 a portion of the NPN index. The CAG index is at least partially based on PLMN elements, which are included in the list of NPN identifiers in combination with at least one of one or more CAG identifiers.

[0257] As an example, CAGs are identified by their PLMN ID and CAG ID. In some embodiments, CAGs associated with the same PLMN ID can be assigned the same CAG index value, for example: In the example above, the index value is determined by the PLMN ID portion of the PLMN ID + CAG ID pair. Following this approach, core network selection can be based solely on the PLMN ID portion. Generating index values ​​based solely on the PLMN ID increases the privacy associated with the CAG ID. Further examples are described above under the heading "CAG Identifiers Associated with the Same PLMN". Note that in some embodiments, the CAG may also be described as a PNI-NPN, and in some embodiments, the CAG ID may correspond to a cag-IdentityList element.

[0258] In other embodiments, CAGs associated with the same PLMN ID can be assigned different CAG index values, for example: In 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 may 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, wherein an NID index is generated that is at least partially included in the NPN index. In some embodiments, the NID index is at least partially based on the number of NIDs included in the list of NIDs, for example: Some embodiments include a step of identifying whether the system information includes a list of PLMN identifiers. Figure 15BThis operation is illustrated in step 1514. The PLMN identifier list contains public networks identified by their PLMN IDs. As mentioned above, the NPN identifier list (which contains a list of non-public networks) also uses PLMN IDs because PLMN IDs are included in the SNPN and PNI-NPN identifiers of non-public networks. In some embodiments, the method may determine whether the system information includes the PLMN identifier list based on a parameter indicating whether the cell is an NPN-only cell. As an example, the cellReservedForOtherUse parameter can be set to true when the cell is an NPN-only cell and false when the cell is not an NPN-only cell. In response to detecting that the parameter indicates the cell is an NPN-only cell, the method may skip step 1516. In response to detecting that the parameter indicates the cell is not an NPN-only cell, the method may continue to step 1516.

[0259] Step 1516 shows that when the system information includes a list of PLMN identifiers, the method generates index values ​​for the PLMN identifiers to be included as at least a portion of the network index. Therefore, in some embodiments, the network index includes an index value for each PLMN identifier, and the network index also includes an NPN index. As described above, the NPN index may include a CAG index (e.g., an index including one or more CAG index values) and / or a NID index (e.g., an index including one or more NID index values). When the network index includes a CAG index and index values ​​for PLMN identifiers, some embodiments arrange the CAG index to inherit the index values ​​for the PLMN identifiers. When the network index includes an NID index and index values ​​for PLMN identifiers, some embodiments arrange the NID index to inherit the index values ​​for the PLMN identifiers. When the network index includes both an NID index and a CAG index, some embodiments arrange the NID index to inherit the CAG index. When the network index includes all three indices, some embodiments arrange the NID index to inherit the CAG index and arrange the CAG index to inherit the index values ​​for the PLMN identifiers. Figure 16 An example is shown. Alternatively, in embodiments where the parameter (e.g., cellReservedForOtherUse) indicates that the cell is an NPN-only cell, generating the network index includes assuming that there is no PLMN index preceding the CAG index or NID index.

[0260] Turning to Figure 15, the method continues to step 1518, where a network index is used. Some embodiments use a network index during connection establishment to indicate the network the wireless device requests access to. As an example, some embodiments may indicate the index value of the network the wireless device requests access to. Some embodiments use the network index to determine the UAC parameters associated with the NPN. As an example, some embodiments determine the UAC parameters based on the association between the index value and the UAC parameters.

[0261] Figure 15A and Figure 15B The steps can be performed in any suitable order. As an example, some embodiments may be performed according to... Figure 2 Perform the steps in a similar order as shown.

[0262] As described above, in some embodiments, network nodes may be configured to perform similar or reciprocal functionality. For example, a network node may 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. The generation of the NPN index is based on... Figure 15B Steps 1506, 1508, 1510, and 1512. In some embodiments, the generation of the network index is further based on... Figure 15B Steps 1514 and 1516. In this manner, the network node can generate a network index according to the same rules as the wireless device, ensuring that both the network node and the wireless device use the same network index value to identify a specific network. As an example, the network node can use the network index during connection establishment to determine the network the wireless device requests access to. As another example, the network node can use the network index to indicate to the wireless device one or more Unified Access Control (UAC) parameters associated with the NPN.

[0263] Figure 17Examples of methods that can be performed by a wireless device (such as wireless device 110 or UE 200) according to certain embodiments are shown. In some embodiments, the method detects a first system information broadcast in step 1702. The first system information broadcast includes an NPN list. The NPN list indicates a plurality of NPN identifiers. Each NPN identifier is associated with a corresponding 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 an HRNN list. The HRNN list indicates a plurality of HRNNs. In step 1706, the method associates each HRNN of the second system information broadcast with the corresponding NPN identifier of the first system information broadcast. In some embodiments, the association is based on the number of elements / list entries in the NPN list corresponding to the number of elements in the HRNN list. As an example, in some embodiments, the association is based on the i-th element of the NPN list corresponding to the i-th element of the HRNN list. If no HRNN is associated with a given NPN, the corresponding element in the HRNN list may not exist (e.g., the value corresponding to "no name" can be assigned to the element in the HRNN list). In step 1708, the method uses the HRNN corresponding to one of the NPN identifiers to identify the corresponding network associated with said one of the NPN identifiers.

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

[0265] Figure 19 Examples of methods that can be performed by a wireless device (such as wireless device 110 or UE 200) according to certain embodiments are shown. In step 1902, the method includes reading a first element / list entry from a PLMN list (e.g., PLMN-IdentityInfoList). In response to detecting the first element, indicating that no normal service is available, the method continues to step 1904, where a network identifier is selected from an NPN list (e.g., NPN-IdentityInfoList). The method then continues to step 1906, where the network identifier is used to verify system information already stored by the wireless device. In some embodiments, verifying the system information includes checking that the selected network identifier matches a network identifier associated with a stored copy of the system information.

[0266] Figure 20An example of a method performed by a network node according to certain embodiments is shown. The method begins at step 2002, where a first system information broadcast is transmitted. The first system information broadcast includes an NPN list. The NPN list indicates a plurality of NPN identifiers. Each NPN identifier is associated with a corresponding 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 at step 2008, where the HRNN corresponding to one of the NPN identifiers is used to identify the corresponding network associated with said one of the NPN identifiers. For example, the network node may send a message to the wireless device identifying the network via an HRNN, or the network node may receive a message from the wireless device identifying the network via an HRNN.

[0267] Figure 21 An example of a method performed by a network node according to certain embodiments is shown. The method begins at step 2102, wherein parameters are transmitted to a wireless device. The parameters indicate that the cell is an NPN-only cell. The method continues to step 2104, wherein a selection of a network identifier is received from the wireless device, wherein when the parameters indicate that the cell is an NPN-only cell, the network identifier is selected from an NPN list, and when the parameters indicate that the cell is not an NPN-only cell, the network identifier is selected from a PLMN list.

[0268] 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 instructing the wireless device to select a network identifier from the NPN list and use the network identifier to verify system information already stored by the wireless device.

[0269] Figure 23Examples of methods performed by a wireless device according to some embodiments are 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, some embodiments use the index value to instruct the network node during connection establishment that the wireless device requests access to the selected network. As another example, some embodiments use the index value to determine UAC parameters associated with the selected network. For example, the wireless device may receive a message from the network node including UAC parameters and an index value, and may use the index value to associate the UAC parameters with the selected network.

[0270] In some embodiments, in step 2306, the index value is determined 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 at least in part based on a PLMN identifier, which is included in the list of NPN identifiers in combination with at least one CAG identifier. As an example, some embodiments determine the index value 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. The discussion in Figure 15 above provides a table as an example (Example 1), where CAG A1 and CAG A2 are each identified by corresponding CAG identifiers (CAG identifier 1 and CAG identifier 2, respectively), and CAG A1 and CAG A2 are associated with the same PLMN (PLMN ID A), such that the index value will be the same for CAG A1 and CAG A2 (index value 1).

[0271] Alternatively, the index value can be determined based on using different index values ​​for each PLMN identifier-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 in Figure 15 above provides a table as an example (Example 2), where CAG A1 and CAG A2 are identified by different CAG identifiers (CAG identifier 1 and CAG identifier 2, respectively), and therefore have different index values ​​(index value 1 and index value 2, respectively), even though CAG A1 and CAG A2 are associated with the same PLMN (PLMN ID A). CAG B1 also has a different index value (index value 3) because CAG B1 is associated with a different PLMN (PLMN ID B). That is, CAG identifier 1 associated with PLMN IDB is understood as a different CAG identifier than CAG identifier 1 associated with PLMN ID A, because it is associated with a different PLMN.

[0272] In some embodiments, when the NPN identifier associated with the selected network includes an NID, the index value is determined at least in part based on the number of NIDs contained in the list of NPN identifiers. For example, some embodiments determine the index value based on each NPN identified by its corresponding NID with its own index value, according to system information. The discussion in Figure 15 above provides a table as an example (Example 3) where NID A1 and NID A2 are identified by different NIDs (NID 1 and NID 2, respectively) and therefore have different index values ​​(index value 1 and index value 2, respectively), even though NID A1 and NID A2 are associated with the same PLMN (PLMN ID A). NID B1 also has a different index value (index value 3) because NID B1 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.

[0273] In some 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 an 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 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 a PLMN identifier that is combined with at least one CAG identifier from the list of NPN identifiers (see, for example, Example 1 or Example 2 table in Figure 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 contained in the list of NPN identifiers (see, for example, Example 3 table in Figure 15). Some embodiments determine the index value for a first time period 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, and determine the index value for a second time period based on each NPN identified by the system information through the corresponding NID having its own index value.

[0274] Some embodiments may generate network indexes based on system information (such as...) 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. For example, the index value (i) associated with the selected network can be determined to correspond to the i-th index value in the network index. In some embodiments, a lower layer of the wireless device can read the SIB and report available PLMNs, CAGs, and / or NIDs to a higher layer of the wireless device. The higher layer of the wireless device can then select one of the networks. For example, if the wireless device selects to use an NPN, it can select a combination of PLMN-CAG ID or PLMN-NID. Based on this selection, the lower layer of the wireless device will calculate the corresponding index value for the selected network. In order to accurately calculate the index value of the selected network, the wireless device will consider other available networks. In other words, the wireless device generates the network index, at least in the sense that it considers other available networks when calculating the index value associated with the selected network. In this way, the wireless device can increment the index value as appropriate (e.g., to avoid using the same index value for two networks intended to use different index values).

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

[0276] Figure 24 This shows an example of a method executed by a network node. Generally, Figure 24 The steps can be with Figure 23 The steps performed by the wireless device are similar / reciprocal, such that the index value used by the network node for a given network corresponds to the index value used by the wireless device for that network. The method begins at step 2402, where system information is broadcast, including a list of NPN identifiers identifying multiple non-public networks (NPNs). The method continues to step 2404, where an index value associated with a network of the multiple NPNs is determined. In some embodiments, the method uses the index value to perform operations of the network node. As an example, some embodiments determine that the wireless device requests access to the network based on the index value associated with the network received from the wireless device during connection establishment. The network node can then facilitate a connection to the network. As another example, some embodiments transmit UAC parameters having an index value associated with the network to indicate that the UAC parameters are associated with the network.

[0277] In some embodiments, in step 2404, an index value is determined 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 at least partially based on a PLMN identifier, which is included in the list of NPN identifiers in combination with 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 the corresponding CAG identifier and associated with the same PLMN in the system information. The discussion in Figure 15 above 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 different index values ​​for each PLMN identifier-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 in Figure 15 above provides a table as an example (Example 2) (as for... Figure 23 (Further explanation).

[0278] In some embodiments, when the NPN identifier associated with the network includes an NID, the index value is determined at least in part based on the number of NIDs contained in the list of NPN identifiers. For example, some embodiments determine the index value based on system information identifying each NPN by its corresponding NID, which has its own index value. The discussion in Figure 15 above provides a table as an example (Example 3) (as for...). Figure 23 (Further explanation).

[0279] In some embodiments, network nodes support different types of NPNs. For example, a 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 an index value accordingly. For example, the NPN identifier associated with a network selected for a first time period may include a CAG identifier, and the NPN identifier associated with a network selected for a second time period may 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 a PLMN identifier that is included in a list of NPN identifiers in combination with at least one CAG identifier (see, for example, Example 1 or Example 2 table in Figure 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, for example, Example 3 table in Figure 15). Some embodiments determine the index value for a first time period 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, and determine the index value for a second time period based on each NPN identified by the system information through the corresponding NID having its own index value.

[0280] and Figure 23 The method performed by the wireless device is similar, at least in the sense that all available networks can be considered when determining the index value associated with a particular network. Figure 24 Some embodiments of the methods performed by network nodes can generate network indexes. Figure 16 An example of a network index is shown. If the cell is an NPN-only cell, the network index does not need to include an index value associated with any PLMN identifier (meaning its own PLMN identifier, as opposed to a combination of PLMN-CAG ID or PLMN-NID). Some embodiments transmit parameters indicating that the cell is an NPN-only cell, thereby instructing the radio device that there is no index value for a PLMN identifier to be included in the network index.

[0281] Some embodiments may store a network index, which can be used later by a network node when it needs to determine the association between an index value and a network. For example, when a 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 a network node is preparing to transmit UAC parameters for a specific network, the network node can use the network index to determine the index value associated with that network. Then, when transmitting the UAC parameters, the network node can provide the index value to indicate that the UAC parameters are for a specific network.

[0282] Modifications, additions, or omissions may be made to the systems and devices described herein without departing from the scope of this disclosure. Components of the systems and devices may be integrated or separate. Furthermore, the operation of the systems and devices may be performed by more, fewer, or other components. Additionally, the operation of the systems and devices may be performed using any suitable logic, including software, hardware, and / or other logic. As used in this document, "each" means each member of a set or each member of a subset of a set.

[0283] The methods described herein may be modified, added to, or omitted without departing from the scope of this disclosure. Methods may include more, fewer, or other steps. Furthermore, the steps may be performed in any suitable order.

[0284] While this disclosure has been described with reference to certain embodiments, modifications and substitutions to the embodiments will be readily apparent to those skilled in the art. Accordingly, the above description of the embodiments does not limit this disclosure. Other variations, substitutions, and alterations are possible without departing from the scope of this disclosure as defined in the following claims.

Claims

1. A method in a wireless device, the method comprising: Detect first system information broadcast from network nodes, the first system information including multiple NPN elements identifying multiple non-public networks (NPNs); Detect second system information broadcast from the network node, the second system information including a plurality of human-readable network name (HRNN) elements, each HRNN element corresponding to a corresponding NPN element of the first system information, each HRNN element indicating name information, wherein the name information includes the HRNN associated with the corresponding NPN or, if the second system information does not include any HRNN associated with the corresponding NPN, includes a "no name" indicator; Associating the name information of the second system information with the corresponding NPN element of the first system information, the association being based on the i-th NPN element corresponding to the i-th HRNN element; and The HRNN corresponding to one of the NPN elements is used to identify the corresponding NPN associated with that one of the NPN elements.

2. The method of claim 1, wherein, Detecting the first system information includes receiving a first system information block that includes the first system information.

3. The method of claim 1, wherein, Detecting the second system information includes receiving a second system information block that includes the second system information.

4. The method according to claim 1, wherein: Detecting the first system information includes receiving a first system information block (SIB) that includes the first system information; and Detecting the second system information includes receiving a second SIB that includes the second system information.

5. The method of claim 4, wherein, The first SIB and the second SIB are different SIBs.

6. A wireless device, the wireless device comprising: A power supply circuit configured to supply power to the wireless device; as well as Processing circuit, the processing circuit being configured to: Detect first system information broadcast from network nodes, the first system information including multiple NPN elements identifying multiple non-public networks (NPNs); Detect second system information broadcast from the network node, the second system information including a plurality of human-readable network name (HRNN) elements, each HRNN element corresponding to a corresponding NPN element of the first system information, each HRNN element indicating name information, wherein the name information includes the HRNN associated with the corresponding NPN or, if the second system information does not include any HRNN associated with the corresponding NPN, includes a "no name" indicator; Associating the name information of the second system information with the corresponding NPN element of the first system information, the association being based on the i-th NPN element corresponding to the i-th HRNN element; and The HRNN corresponding to one of the NPN elements is used to identify the corresponding NPN associated with that one of the NPN elements.

7. The wireless device of claim 6, wherein, The processing circuit is further configured to detect the first system information, including receiving a first system information block that includes the first system information.

8. The wireless device of claim 6, wherein, The processing circuit is configured to detect the second system information, including receiving a second system information block that includes the second system information.

9. The wireless device of claim 6, wherein, The processing circuit is further configured to: Detecting the first system information includes receiving a first system information block (SIB) that includes the first system information; and Detecting the second system information includes receiving a second SIB that includes the second system information.

10. The wireless device of claim 9, wherein, The first SIB and the second SIB are different SIBs.

11. A network node, the network node comprising: A power supply circuit configured to supply power to the network nodes; as well as Processing circuit (170), the processing circuit being configured to: Transmit first system information, which includes multiple NPN elements that identify multiple non-public networks (NPNs); The system transmits second system information, which includes a plurality of human-readable network name (HRNN) elements, each HRNN element corresponding to a corresponding NPN element of the first system information, such that the i-th NPN element corresponds to the i-th HRNN element, and each HRNN element indicates name information, wherein the name information includes the HRNN associated with the corresponding NPN or, if the second system information does not include any HRNN associated with the corresponding NPN, includes a "no name" indicator. as well as The HRNN corresponding to one of the NPN elements is used to identify the corresponding NPN associated with that one of the NPN elements.

12. A method in a network node, the method comprising: Transmit first system information, which includes multiple NPN elements that identify multiple non-public networks (NPNs); The system transmits second system information, which includes a plurality of human-readable network name (HRNN) elements, each HRNN element corresponding to a corresponding NPN element of the first system information, such that the i-th NPN element corresponds to the i-th HRNN element, and each HRNN element indicates name information, wherein the name information includes the HRNN associated with the corresponding NPN or, if the second system information does not include any HRNN associated with the corresponding NPN, includes a "no name" indicator. as well as The HRNN corresponding to one of the NPN elements is used to identify the corresponding NPN associated with that one of the NPN elements.

13. The method of claim 12, wherein, Transmitting the first system information includes transmitting a first system information block that includes the first system information.

14. The method of claim 12, wherein, Transmitting the second system information includes transmitting a second system information block that includes the second system information.

15. The method of claim 12, wherein: Transmitting the first system information includes transmitting a first system information block (SIB) that includes the first system information; and Transmitting the second system information includes transmitting a second SIB that includes the second system information.

Images