EP3949522B1 - Verfahren zum senden von listen öffentlicher und nichtöffentlicher netzwerke und zugehörige netzwerkknoten und drahtlose vorrichtungen - Google Patents

Verfahren zum senden von listen öffentlicher und nichtöffentlicher netzwerke und zugehörige netzwerkknoten und drahtlose vorrichtungen Download PDF

Info

Publication number
EP3949522B1
EP3949522B1 EP20718378.1A EP20718378A EP3949522B1 EP 3949522 B1 EP3949522 B1 EP 3949522B1 EP 20718378 A EP20718378 A EP 20718378A EP 3949522 B1 EP3949522 B1 EP 3949522B1
Authority
EP
European Patent Office
Prior art keywords
network
npn
plmn
cell
public
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
EP20718378.1A
Other languages
English (en)
French (fr)
Other versions
EP3949522A1 (de
Inventor
Christofer Lindheimer
Mattias BERGSTRÖM
Mats Buchmayer
Peter Hedman
Oscar Ohlsson
Paul Schliwa-Bertling
Ivo Sedlacek
Alexander Vesely
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Telefonaktiebolaget LM Ericsson AB
Original Assignee
Telefonaktiebolaget LM Ericsson AB
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget LM Ericsson AB filed Critical Telefonaktiebolaget LM Ericsson AB
Publication of EP3949522A1 publication Critical patent/EP3949522A1/de
Application granted granted Critical
Publication of EP3949522B1 publication Critical patent/EP3949522B1/de
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H04W48/10—Access restriction or access information delivery, e.g. discovery data delivery using broadcasted information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/18—Selecting a network or a communication service
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H04W48/12—Access restriction or access information delivery, e.g. discovery data delivery using downlink control channel
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04—Large scale networks; Deep hierarchical networks
    • H04W84/042—Public Land Mobile systems, e.g. cellular systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/06—Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals

Definitions

  • the present disclosure relates generally to communications, and more particularly to communication methods and related devices and nodes supporting wireless communications.
  • 3GPP is currently working on specifications of what is commonly referred to as "5G”.
  • 5G Core network 5G Core network
  • 5GS 5G System
  • 5GS may also be referred to, constituting a complete system, as in a 5G system, a 5GS.
  • the 5G system defined by 3GPP in Rel-15 includes both a new radio access (NR) and a new core network (5GC).
  • NR new radio access
  • 5GC new core network
  • the 5GC offers several new features such as support for network slicing, improved Quality of Service (QoS), and latency and battery optimizations in the form a new User Equipment (UE) state called inactive mode.
  • QoS Quality of Service
  • UE User Equipment
  • the 5G System may be known as a "public system", for example as a Public Land Mobile Network (PLMN).
  • PLMN Public Land Mobile Network
  • This may mean that anyone can get a subscription and access to the network. This, for example, is in contrast to some other networks that can only be accessed by specific UE's and for which it may not be possible to simply get a subscription/credential to access.
  • a "private" network is a Wi-Fi Router deployed as an extension to a private broadband connection, e.g., a broadband subscription over fiber or xDSL or the like. For this, access may not be available to everyone.
  • NPN non-public network
  • An NPN is a network intended for a limited group of users such as an enterprise and may typically provide service in a limited geographical area such as a factory floor or campus.
  • One example of a use case is industrial/IIoT scenarios, although other use cases are not excluded.
  • PNI-NPN Public Network Integrated PLMN
  • SNPN Standalone NPN
  • a PNI-NPN is made available via a PLMN by allocating one or more network slices to the non-public network.
  • network slicing may not enable the possibility to reduce/avoid UEs trying to access the network in areas in which the UE is not allowed to use the network slice, the usage of Closed Access Groups (CAGs) can be used in addition to network slicing to apply additional access control.
  • CAGs Closed Access Groups
  • the PNI-NPN may be identified by the combination of PLMN ID and CAG ID where the CAG ID is unique within the scope of the PLMN, or at least the cells to be used for the PNI-NPN are identified by the PLMN ID and CAG ID (i.e., the actual NPN may be identified by other means in dedicated signaling, e.g., Network Slice ID).
  • a human readable network name can also be provided to assist the user in case of manual CAG selection.
  • An SNPN may operate without dependency on a PLMN and may be identified by the combination of PLMN ID and a Network ID (NID). Unlike the PLMN ID used by a PLMN, the PLMN ID used by an SNPN is not required to be unique, i.e., it may be possible for two SNPNs to share the same PLMN ID. PLMN IDs reserved for use by private networks can be used for non-public networks, e.g., based on mobile country code (MCC) 999 assigned by ITU. The NID can be seen as an extension of the PLMN ID and may support two different assignment models:
  • Universally managed NIDs are managed by a central entity per region and are assumed to be globally unique.
  • a human readable network name can optionally be provided to assist the user in identifying an SNPN during manual network selection.
  • PNI-NPN may use PLMN ID + NID while a PNI-NPN may use PLMN ID + CAG ID.
  • PLMN ID + NID may be used in a PNI-NPN.
  • PLMN ID + CAG ID may be used in a PNI-NPN.
  • Another difference is that an SNPN may use a PLMN ID reserved for private use while a PNI-NPN may use the PLMN ID of its hosting PLMN, i.e., a public PLMN ID.
  • Network sharing may be a feature in 5G which allows multiple operators to share the same radio access network.
  • the PLMN IDs may be broadcasted in system information (more specifically in SIB 1, system information block 1).
  • SIB 1 system information block 1
  • 5G may also allow each operator to broadcast their own Cell ID and Tracking Area Code (TAC) in SIB 1.
  • TAC Tracking Area Code
  • PLMN ID + NID the physical cell is divided into several logical cells, one for each operator.
  • PNI-NPN(s) i.e. PLMN ID + CAG ID
  • cellBarred (IE type: "barred” or “not barred") Indicated in MIB message. In case of multiple PLMNs indicated in SIB1, this field is common for all PLMNs.
  • cellReservedForOperatorUse (IE type: "reserved” or “not reserved”). Indicated in SIB1 message. In case of multiple PLMNs indicated in SIB1, this field is specified per PLMN.
  • cellReservedForOtherUse (IE type: "true) Indicated in SIB1 message. In case of multiple PLMNs indicated in SIB1, this field is common for all PLMNs.
  • One drawback of the cellReservedForOtherUse indication may be that it may be common for all PLMN IDs broadcast in SIB1.
  • Non-Public Networks NPN
  • Ericsson 3GPP Tdoc R2-1900408
  • Observation 1 Changes to 38.304 related to SNPN can be made such that PLMN selection instead becomes PLMN/NPN-ID selection. Then, cell selection/reselection procedures does not need to change.
  • Observation 2 UE's should include PLMN ID and NID in msg5 in an initial registration procedure. The following proposals were made.
  • Proposal 1 Include in an LS response to SA2 (CT1, RAN3), that RAN2 expect further information on selection of MNC and uniqueness thereof, to judge whether further SIB optimization would be possible.
  • Proposal 2 Include in an LS response to SA2 (CT1, RAN3), a request for clarification on if the locally managed NIDs can result in that the combination of MCC, MNC and NID is not necessarily uniquely identifying a specific Non-Public Network. Further ask SA2 to consider alternatives to broadcast HRN. One alternative is to store HRN-information together with allowed NID information in the UE. This does not guarantee that trial-error situations don't occur, but it avoids broadcast.
  • Proposal 3 Include in an LS response to SA2 (CT1, RAN3), that RAN2 need further information on: A) If an NPN ID can be associated with a public PLMN ID, B) If, in the same cell, there can be an NPN ID that is associated with several PLMN ID, C) If, in the same cell, there can be several NPN ID's, each associated with different PLMN ID's.
  • Proposal 4 Include in an LS response to SA2 (CT1, RAN3), that it is RAN2 view that AS actions related to cell selection/reselection are not impacted.
  • Proposal 5 RAN2 should support separate Cell IDs and TAC's per MCC, MNC, NID combinations (corresponding to PLMN ID).
  • Proposal 6 Include in an LS to RAN (SA2, CT1, RAN3) that RAN2 expect to handle necessary standardization to support SNPN without the need of an SI.
  • Proposal 7 Include in an LS response to SA2 (CT1, RAN3), that RAN2 is interested in conclusions on if it shall be possible to broadcast a list of CAG identifiers per PLMN.
  • Proposal 8 Include in an LS response to SA2 (CT1, RAN3) a request for clarification on if a CAG can be used to identify more than one NPN within a PLMN?
  • RAN2 propose to remove HRN broadcast for CAG solutions and keep the mapping between a CAG ID for a PLMN to a HRN in the UE.
  • Proposal 9 Include in an LS response to SA2 (CT1, RAN3), a request for clarification on FFS of combining CAG and network slice.
  • Proposal 10 Include in an LS response to SA2 (CT1, RAN3), a request for clarification on if the CAG ID should, at any point in time be forwarded from UE AS to UE NAS, after a PLMN selection procedure or in connection to a PLMN selection procedure.
  • Proposal 11 Feedback to SA2 that if CAG and non-CAG cells are put on the same frequency, traffic to respective cells may cause additional interference. RAN2 does not expect to work on optimizations for such situations.
  • Proposal 12 RAN2 should discuss whether it is feasible to provide standardization support of a CAG solution without a separate SI/WI.
  • Proposal 13 Include in an LS to RAN (SA2, CT1, RAN3) the conclusion of RAN2 discussion on whether there is a need for a WI or SI to proceed with standardization of a CAG solution.
  • Terminology correction for type-a/type-b to non-public network may be construed to disclose an evaluation on the terms 'type-a network' and 'type-b network' to be referred to as 'non-public' network.
  • Using the terms 'type-a network' and 'type-b network' creates confusion and may give the impression that these are two fundamentally different types of networks that need to be specified separately, while in fact they are essentially the same, with one main difference: whether service continuity with a PLMN is possible (which is a matter of agreement between parties).
  • Non-public network a network that is intended for non-public use.
  • Network Identification impact Observation#1: For network identification: Include PLMN, List of NIDs and the human readable network name as part of the CellAccessRelatedInfo in SIB1.
  • Observation#3 For initial registration, the UE NAS provides the UE AS with the selected PLMN ID and its corresponding NID and the UE RRC provides them to the NG RAN via LTE RRCConnectionSetupComplete/NR RRCSetupComplete message for AMF selection.
  • Observation#6 If there is/are dedicated frequency/frequencies for such SNPN cells, then the RRM measurement configuration can be configured appropriately for the UE registered to SNPN to ensure that only SNPN neighbour cells are reported. No further impact.
  • Observation#7 If the frequency of the SNPN cells are shared with operator's public network, it may be useful to introduce PCI partitioning and/or whitelisting/blacklisting of cells to allow the network to know whether a neighbour cell reported is an SNPN cell or a non-SNPN cell and to prevent unnecessary reporting overhead from the NPN and non-NPN supporting UE. This can be further discussed.
  • Observation#8 Some other foreseeable RAN2 impact not including in the SA2 CR may be the extension of ASN.1 signalling for UAC and ANR, as well as discuss the use of SNPN cell as acceptable cell for emergency call.
  • Proposal#1 The impact on Solution#1 (SNPN mode of operation) is small/manageable from RAN2 point of view and can thus be handled by RAN2 as part of Rel-16.
  • Proposal#2 Inform RAN about the impact for Solution#1 (SNPN mode of operation) and RAN can decide how to proceed the work in RAN2 (new WI, existing WI (e.g. IIoT) or as TEI16)
  • the embodiments relating to the network identifiers including a mobile country code, MCC, a mobile network code, MNC a control access group, CAG and a network identifier, NID, fall within the scope of the claims. All other passages referring to embodiments, disclosures, examples, aspects are to be understood as not falling within the scope of the claims but useful for understanding the invention. Some embodiments herein are directed to methods of operating a network node in a cell of a wireless communication network.
  • Such methods include broadcasting, to a user equipment, UE, a first network list that includes multiple public network identifiers that correspond to public networks in the cell and broadcasting, to the UE, a second network list that includes multiple non-public network, NPN, identifiers that correspond to NPNs in the cell.
  • each of the public network identifiers and NPN identifiers includes multiple data fields.
  • the network identifiers include a mobile country code, MCC, a mobile network code, MNC and at least one of a control access group, CAG, and a network identifier, NID.
  • the NPN includes a stand-alone private network, SNPN, that is deployed separately from a public land mobile network, PLMN.
  • SNPN stand-alone private network
  • PLMN public land mobile network
  • the NPN includes an integrated private network, PNI-NPN, that is integrated with a PLMN.
  • a UE access stratum, AS, layer provides the MCC and the MNC for network selection corresponding to a detected PLMN.
  • the network identifier includes the PLMN and the NID responsive to a SNPN deployment.
  • the network identifier includes the MMC, the MNC and a control access group, CAG, responsive to a PNI-NPN deployment.
  • the CAG includes a bit that indicates whether the network identifier identifies a SNPN or PNI-NPN.
  • the UE AS layer includes the first network list and the second network. Some embodiments provide that the first network list includes a list of PLMN identifiers and NPN information that is broadcast by available cells and the second network list includes a list of PLMN identifiers of the network identifiers not broadcasting NPN identifiers.
  • the MCC is set at a value of 999.
  • Some embodiments provide that a PLMN identifier is common to the SNPN and the PNI-NPN.
  • the cell of the wireless communication network corresponds to a PLMN cell or one of a PNI-NPN cell or a SNPN cell.
  • a UE non-access stratum, NAS, layer includes information that distinguishes different NPN deployments from one another. Some embodiments provide that the UE NAS layer list of PLMNs includes identifiers of non-CAG and non SNPN cells from the UE AS layer.
  • Some embodiments provide that a cellReservedForOtherUse function prevents legacy and non-NPN UEs from selecting the PLMN.
  • the network identifiers include the MCC, the MNC and a NID that corresponds to an operator PLMN and NID/CAG that indicates that a PNI-NPN is available.
  • Some embodiments herein are directed to a base station (eNB) of a radio access network, wherein the base station is adapted to broadcast multiple network identifiers that each includes multiple data fields and that correspond to multiple non-public networks ,NPNs, to a user equipment, UE, in the cell.
  • the network identifiers include a mobile country code, MCC, and a mobile network code, MNC.
  • Some embodiments include performing operations described herein.
  • Some embodiments herein are directed to methods of operating a wireless device, UE, in a wireless communication network. Such methods include detecting broadcasted information from a network device.
  • the broadcasted information includes a first network list that includes multiple public network identifiers that correspond to public networks in a cell and a second network list that includes multiple non-public network, NPN, identifiers that correspond to NPNs in the cell.
  • Operations include reading system information corresponding to broadcasts from the network device and determining whether the cell corresponding to the broadcasted information is available for access by the UE.
  • the UE is not NPN capable
  • a UE AS layer is configured to report network identifiers to a UE NAS layer for identified networks, and the UE is configured to receive a selected network identifier from the UE NAS layer.
  • a corresponding network is not selected.
  • Some embodiments provide that the UE is NPN capable and a UE AS layer is configured to report network identifiers to a UE NAS layer for identified networks.
  • the network identifiers include: MCC and MNC for PLMNs, MCC, MNC and NID for SNPNs and/or MCC, MNC and CAG for PNI-NPNs.
  • Some embodiments provide that the UE is configured to receive a selected network identifier from the UE NAS layer.
  • the UE is NPN capable
  • a UE AS layer is configured to report network identifiers to a UE NAS layer for identified networks
  • the MCC value comprises 999
  • the UE NAS ignores networks corresponding to MCC value of 999.
  • Some embodiments include performing, by a UE AS, a search to identify available networks and reporting the available networks to a UE NAS.
  • Some embodiments are directed to a first wireless device (UE) that includes a transceiver configured to provide wireless network communication with a wireless communication network and a processor coupled with the transceiver, wherein the processor is configured to provide wireless network communication through the transceiver, and wherein the processor is configured to perform operations according to embodiments disclosed herein.
  • UE first wireless device
  • Some embodiments are directed to a base station (eNB) of a wireless communication network that includes a transceiver configured to provide wireless network communication with a wireless terminal and a processor coupled with the transceiver, wherein the processor is configured to provide wireless network communications through the transceiver, and wherein the processor is configured to perform operations according to embodiments disclosed herein.
  • eNB base station
  • Operations include broadcasting network identifiers that include multiple data fields that correspond to non-public networks, to a user equipment (block 201).
  • the network identifiers include MCC and MNC (block 203).
  • operations further include broadcasting a list of network identifiers including MCC, MNC and CAG including supported integrated private networks (block 205).
  • FIG. 3 is a block diagram illustrating elements of a wireless device UE 300 (also referred to as a mobile terminal, a mobile communication terminal, a wireless communication device, a wireless terminal, mobile device, a wireless communication terminal, user equipment, UE, a user equipment node/terminal/device, etc.) configured to provide wireless communication according to embodiments of inventive concepts.
  • wireless device UE may include an antenna 307, and transceiver circuitry 301 (also referred to as a transceiver) including a transmitter and a receiver configured to provide uplink and downlink radio communications with a base station(s) (e.g., also referred to as a RAN node) of a radio access network.
  • a base station(s) e.g., also referred to as a RAN node
  • Wireless device UE may also include processing circuitry 303 (also referred to as a processor, e.g., corresponding to processing circuitry coupled to the transceiver circuitry, and memory circuitry 305 (also referred to as memory, e.g., corresponding to device readable medium) coupled to the processing circuitry.
  • the memory circuitry 305 may include computer readable program code that when executed by the processing circuitry 303 causes the processing circuitry to perform operations according to embodiments disclosed herein. According to other embodiments, processing circuitry 303 may be defined to include memory so that separate memory circuitry is not required.
  • Wireless device UE may also include an interface (such as a user interface) coupled with processing circuitry 303, and/or wireless device UE may be incorporated in a vehicle.
  • operations of wireless device UE may be performed by processing circuitry 303 and/or transceiver circuitry 301.
  • processing circuitry 303 may control transceiver circuitry 301 to transmit communications through transceiver circuitry 301 over a radio interface to a radio access network node (also referred to as a base station) and/or to receive communications through transceiver circuitry 301 from a RAN node over a radio interface.
  • modules may be stored in memory circuitry 305, and these modules may provide instructions so that when instructions of a module are executed by processing circuitry 303, processing circuitry 303 performs respective operations (e.g., operations discussed below with respect to Example Embodiments relating to wireless devices).
  • FIG. 4 is a block diagram illustrating elements of a radio access network RAN node 400 (also referred to as a network node, base station, eNodeB/eNB, gNodeB/gNB, etc.) of a Radio Access Network (RAN) configured to provide cellular communication according to embodiments of inventive concepts.
  • the RAN node may include transceiver circuitry 401 (also referred to as a transceiver, e.g., corresponding to portions of interface including a transmitter and a receiver configured to provide uplink and downlink radio communications with mobile terminals.
  • the RAN node may include network interface circuitry 407 (also referred to as a network interface configured to provide communications with other nodes (e.g., with other base stations) of the RAN and/or core network CN.
  • the network node may also include processing circuitry 403 (also referred to as a processor coupled to the transceiver circuitry, and memory circuitry 405 (also referred to as memory) coupled to the processing circuitry.
  • the memory circuitry 405 may include computer readable program code that when executed by the processing circuitry 403 causes the processing circuitry to perform operations according to embodiments disclosed herein. According to other embodiments, processing circuitry 403 may be defined to include memory so that a separate memory circuitry is not required.
  • operations of the RAN node may be performed by processing circuitry 403, network interface 407, and/or transceiver 401.
  • processing circuitry 403 may control transceiver 401 to transmit downlink communications through transceiver 401 over a radio interface to one or more mobile terminals UEs and/or to receive uplink communications through transceiver 401 from one or more mobile terminals UEs over a radio interface.
  • processing circuitry 403 may control network interface 407 to transmit communications through network interface 407 to one or more other network nodes and/or to receive communications through network interface from one or more other network nodes.
  • modules may be stored in memory 405, and these modules may provide instructions so that when instructions of a module are executed by processing circuitry 403, processing circuitry 403 performs respective operations (e.g., operations discussed below with respect to Example Embodiments relating to RAN nodes).
  • a network node may be implemented as a core network CN node without a transceiver.
  • transmission to a wireless device UE may be initiated by the network node so that transmission to the wireless device is provided through a network node including a transceiver (e.g., through a base station or RAN node).
  • initiating transmission may include transmitting through the transceiver.
  • FIG. 5 is a block diagram illustrating elements of a core network CN node (e.g., an SMF node, an AMF node, etc.) of a communication network configured to provide cellular communication according to embodiments of inventive concepts.
  • the CN node may include network interface circuitry 507 (also referred to as a network interface) configured to provide communications with other nodes of the core network and/or the radio access network RAN.
  • the CN node may also include a processing circuitry 503 (also referred to as a processor) coupled to the network interface circuitry, and memory circuitry 505 (also referred to as memory) coupled to the processing circuitry.
  • the memory circuitry 505 may include computer readable program code that when executed by the processing circuitry 503 causes the processing circuitry to perform operations according to embodiments disclosed herein. According to other embodiments, processing circuitry 503 may be defined to include memory so that a separate memory circuitry is not required.
  • operations of the CN node may be performed by processing circuitry 503 and/or network interface circuitry 507.
  • processing circuitry 503 may control network interface circuitry 507 to transmit communications through network interface circuitry 507 to one or more other network nodes and/or to receive communications through network interface circuitry from one or more other network nodes.
  • modules may be stored in memory 505, and these modules may provide instructions so that when instructions of a module are executed by processing circuitry 503, processing circuitry 503 performs respective operations (e.g., operations discussed below with respect to Example Embodiments relating to core network nodes).
  • the present inventive concept relates to the deployment of non-public networks by partially reusing solutions and protocols for public networks.
  • Embodiments may not be directed as much to a home Wi-Fi access point, but instead may be directed to deployments of NPNs in commercial and/or industrial contexts, such as factories. In this manner, it may be possible to connect factory equipment, vehicles and/or employees. These types of deployments may have different requirements regarding, for example, security. It may be important that roaming is functional in some cases to seamlessly transfer a connection from within the private network to a network that is public. In some embodiments, other cases provide that roaming should explicitly not be supported. One such example includes machinery that is connected should preferably only work in the private network and thus not be able to connect through any other access point/cell and/or gNB.
  • operations of operating a network node in a cell of a wireless communication network may include broadcasting a list of network identifiers that include MCC and/or MNC for every supported network (block 601). Embodiments may further include broadcasting a list of identifiers that include MCC, MNC and CAG for every supported integrated private network (block 603).
  • operations may include detecting broadcasted information from a network device (block 801). Operations may include reporting found network identifiers to the UE NAS (block 803).
  • the UE NAS selects the network and provides the UE AS with a selected network identifier (805).
  • the UE is configured to receive a selected network identifier from the UE NAS layer.
  • operations may further include reporting, by the UE AS, found network identifiers to UE NAS (block 903). Responsive to the UE NAS identifying only one network identifier with MCC, MNC format, the UE AS is provided with the selected network identifier (block 905). In some embodiments, responsive to the MCC being 999, a corresponding network is not selected.
  • the network identifiers include MCC and MNC for PLMNs, MCC, MNC and NID for SNPNs and/or MCC, MNC and CAG for PNI-NPNs.
  • the UE is configured to receive a selected network identifier from the UE NAS layer.
  • operations include, reporting, by UE AS, found network identifiers to the UE NAS including MCC, MNC and NID for stand-alone non-public networks, and MCC, MNC and CAG for integrated networks (block 1003).
  • the UE NAS selects the network and provides UE AS with the selected network identifier (block 1005).
  • the UE NAS selects the network and provides the UE AS with a selected network identifier that the UE may use (block 1107).
  • operations include the UE AS determining that no network devices are broadcasting with the formats MCC, MNC, and NID or MCC, MNC and CAG and does not report to the UE NAS (block 1303).
  • 3GPP has set forth requirements for how the NPN's should work and studies have been performed on how to meet such requirements.
  • the requirements are described in a 3GPP document 22.261 (v16.6.0) and are provided as follows:
  • Non-public networks are intended for the sole use of a private entity such as an enterprise, and may be deployed in a variety of configurations, utilizing virtual and/or physical elements.
  • NPNs may be deployed as completely standalone networks, they may be hosted by a PLMN, and/or they may be offered as a slice of a PLMN.
  • unauthorized UEs those that are not associated with the enterprise, will not attempt to access the non-public network, which could result in resources being used to reject that UE and thereby not be available for the UEs of the enterprise. It is also expected that UEs of the enterprise will not attempt to access a network they are not authorized to access. For example, some enterprise UEs may be restricted to only access the non-public network of the enterprise, even if PLMN coverage is available in the same geographic area. Other enterprise UEs may be able to access both a non-public network and a PLMN where specifically allowed.
  • the 5G system shall support non-public networks.
  • the 5G system shall support non-public networks that provide coverage within a specific geographic area.
  • the 5G system shall support both physical and virtual non-public networks.
  • the 5G system shall support standalone operation of a non-public network, i.e. a non-public network may be able to operate without dependency on a PLMN.
  • the 5G system shall support for non-public network subscribers: access to subscribed PLMN services via the non-public network; seamless service continuity for subscribed PLMN services between a non-public network and a PLMN; access to selected non-public network services via a PLMN; and seamless service continuity for non-public network services between a non-public network and a PLMN.
  • a non-public network subscriber to access a PLMN service shall have a service subscription using 3GPP identifiers and credentials provided or accepted by a PLMN.
  • the 5G system shall support a mechanism for a UE to identify and select a non-public network. Different network selection mechanisms may be used for physical vs virtual non-public networks.
  • the 5G system shall support identifiers for a large number of non-public networks to minimize collision likelihood between assigned identifiers.
  • the 5G system shall support a mechanism to prevent a UE with a subscription to a non-public network from automatically selecting and attaching to a PLMN or non-public network it is not authorized to select.
  • the 5G system shall support a mechanism to prevent a UE with a subscription to a PLMN from automatically selecting and attaching to a non-public network it is not authorized to select.
  • the 5G system shall support a change of host of a non-public network from one PLMN to another PLMN without changing the network selection information stored in the UEs of the non-public network.
  • the first deployment scenario includes that in which a private network, NPN, is deployed as a stand-alone network. This scenario may be referred to as SNPN.
  • the second scenario includes that in which a private network, NPN, is deployed as a non-stand-alone network.
  • NPN is integrated with a public network, a PLMN, but may have nodes and/or cells that are for exclusive use by the private network users/subscribers.
  • the nodes may be shared, but certain resources may be dedicated to the private network in certain cells.
  • the latter may include an extension of the slicing concept (e.g., as described in 23.501).
  • This NPN-type may be referred to as PNI-NPN, Public Network-Integrated NPN.
  • NPN NPN with a stand-alone (SNPN) deployment
  • NID NID solution
  • PNI-NPN NPN public network integrated
  • CAG CAG solution
  • Principles corresponding to the SNPN/NID approach include: combination of a PLMN ID and Network identifier (NID) identifies an SNPN; NID may be globally unique or locally managed; NG-RAN node supports broadcasting a total of twelve NIDs; optionally a human-readable network name per NID for manual selection; optionally cell broadcast information to prevent UEs not supporting SNPNs from accessing the cell; when the UE is set to operate in SNPN access mode the UE only selects and registers with SNPNs; UE provides PLMN ID and NID as selected PLMN and NG-RAN provides PLMN ID and NID as selected PLMN to 5GC; AMF performs access control and rejects a UE if the UE has no subscription for an SNPN; and UAC information is configured per non-public network.
  • NID Network identifier
  • the NID may be used together with a PLMN ID during network selection and may therefore be seen as an extension to the network identity (PLMN ID). This may be determined from the statement "UEs operating in SNPN access mode only select cells and networks broadcasting both PLMN ID and NID of the selected SNPN.”
  • Figure 1 is a schematic diagram illustrating stand alone and non-stand-alone deployment options disclosed herein. Approaches supporting the two deployment options (SNPN and PNI-NPN respectively) based on two different deployment scenarios are provided.
  • Figure 1 illustrates the two deployment options mainly from a radio infrastructure point of view. While in the stand-alone option, radio resources and network equipment are owned by the NPN operator, and in the non-stand-alone NPN option, radio resources and network equipment may be operated by a PLMN operator.
  • the stand-alone NPN may be regarded as PLMN with non-public access rights only, realized in an isolated deployment, i.e. without sharing any infrastructure with a P(ublic)LMN.
  • a non-stand-alone NPN shares certain infrastructure equipment. Note, that more than one NPN may be hosted by a certain deployment.
  • the requirements provide that it should be possible to prevent UEs that are not authorized to non-public networks from automatically selecting and attaching to such networks. This may be the same requirement that already exists for public networks, with the possible exception of emergency call handling. Further, subscribers to a non-public network should not automatically select and attach to a PLMN, or another non-public network it is not authorized in.
  • This aspect may call for a unified approach for both deployment options, both on Access Stratum and Non-Access Stratum level.
  • Requirements may provide that it should be possible to access services via PLMNs and to support seamless service continuity. This may generally apply to tunneling services subscribed to in one network through another network. Such requirements may be deployment-independent.
  • the requirements further address selection and the UE should be able to identify and select a non-public network. While the requirements open for different solutions dependent on physical or virtual non-public networks, such properties do not mandate different solutions. From the above short analysis, requirements may be very similar regardless of deployment option.
  • requirements for NPN do not differ between the SNPN and the PNI-NPN deployments.
  • two approaches, one for each deployment option as described above, PNI-NPN and SNPN respectively, are provided.
  • Such approaches may include the PNI-NPN (aka CAG ID) approach, which has been specified by 23.501 CR in [4] and 23.502 CR in [5].
  • the principles of the approach include:
  • Such approaches may also include the SNPN approach, which has been specified by 23.501 CR in[2] and 23.502 CR in [3].
  • the principles of the SNPN approach provide that:
  • the NID is used together with a PLMN ID during network selection and is therefore seen as an extension to the network identity i.e. PLMN ID.
  • PLMN ID the network identity
  • UEs operating in SNPN access mode may only select cells and networks broadcasting both PLMN ID and NID of the selected SNPN.
  • both solutions can be realized by one set of Access Stratum functions, whereas the differentiation is rather made on NAS (if at all). Thus, at least from a RAN perspective, it is good to further assess if the different deployment options can be handled with one and the same solution.
  • the UE may select a CAG, which may be communicated to RAN/AMF (see [4]).
  • UE configuration and subscription aspects for SNPN provide that only UEs in SNPN access mode select and register with SNPNs. UEs not in SNPN access mode do not select and register with SNPNs. Note that UE's in SNPN access mode can also access P(ublic)LMN's, if it also has credentials or is authorized for such access.
  • UE configuration and subscription aspects for PNI-NPN w CAG ID provide that the UE is configured with CAG related information using UE Config Update procedure (23.502 ⁇ 4.2.4.2).
  • the UE may be configured to access 5GS only via CAG cells or be allowed to access both normal PLMN cells and CAG cells.
  • Embodiment 2 provides an overlap for AS functions between the SNPN solution and the PNI-NPN w CAG ID solution:
  • NPNs also in the PNI-NPN-case are isolated as in SNPN from AS perspective. For example, subscribers that have only PLMN subscriptions w/o access to NPNs shall not access radio resources reserved for NPN use only. The requirements don't differ between the deployments.
  • Embodiment 3 provides that from a radio deployment point-of-view, PNI-NPNs are as isolated as SNPN's. For example, cells are either for NPN use or for public use.
  • Assignment of Tracking Area Codes to PNI-NPN cells can either follow geographical/deployment considerations from normal PLMN cells or, if found more appropriate, be associated to separate Tracking Areas. This will depend on the required interaction between PNI-NPN and the PLMN part of the overall network. One could even think of allocating NPN specific PLMN IDs to configure an NPN PLMN within a public network. This would have the advantage that the solutions for doing this are already in place.
  • Embodiment 4 provides that for PNI-NPN's, operators can choose to either associate NPN cells with "publicly” assigned TACs or configure specific PNI-NPN TACs.
  • Embodiment 5 provides that, from an Access Stratum point of view, there is not a need for two different approaches for SNPN and PNI-NPN. For example, both options are deployment variants only and may be addressed with a single approach.
  • the "network” selection should be understood in the same way as we know "PLMN selection”, but since now, there is a possibility for a UE that is capable of accessing Non-Public Networks, to implement a "Network Selection" in NAS that includes both regular PLMNs and different types of NPN's. Thus, the treatment from a selection perspective does not need to be different for the different NPN types. If there is a need to distinguish between the NPN types on NAS layer, it is possible to do this (e.g., by being able to differentiate identifier NID/CAG) without implementing different selection mechanisms.
  • Embodiment 6 provides that UE NAS uses very similar information for all types of "PLMN" selection.
  • PLMN Packet Control Protocol
  • the AMF uses one bit to determine whether the remaining bits of the NPN-specific info (NID/CAG) contain the NID or the CAG ID. AMF can then perform specific authorization and mobility restrictions.
  • NID/CAG NPN-specific info
  • both approaches may require the following support from AS layer:
  • 5GC aspects related to N2 are the following:
  • Radio network aspects of a merged solution Radio network aspects of a merged solution.
  • the selection of the NPN is solely a task for the network selection procedures that are controlled by the UE NAS portion, and standardized by CT1.
  • the UE NAS will select a network in which there are only allowed cells for an NPN UE and it will efficiently keep away UEs that are only allowed to access other networks.
  • network is to be understood as either a public network or a non-public, and even with different deployments, if such distinguishing is desired, see above.
  • the UE AS may then need to implement functionality to receive a CAG limitation indication (in addition to a network indication) from the UE NAS, and to only select cells that have the CAG ID dictated by the UE NAS, or alternatively not, dependent on UEs being allowed to access also other cells.
  • a CAG limitation indication in addition to a network indication
  • the result may be the same, but the modelling in the UE will be different and essentially force two separate approaches.
  • the resulting behavior from a UE is that it sometimes needs to be restricted to NPN cells, and that NPN cells should efficiently keep non-authorized users away. This is true for both cases and a single approach should be enough.
  • the selection mechanisms may not need to be different and, in the case of PNI-NPN, split over both "network selection" and cell re/selection.
  • Embodiment 7 provides that there is not a reason for the selection mechanisms to be different for the SNPN deployment and for the PNI-NPN-deployment.
  • the main change may be to allow broadcast of a network identification as MCC, MNC, NID, instead of just MCC, MNC, as it is today.
  • an NPN can be identified with a MCC, MNC, NID(or CAG). However, in such case, it would be the MCC and the MNC of the Public network in which the NPN is integrated.
  • Embodiment 8 provides that if a NID together with a (public) PLMN ID is used also in the PNI-NPN case, it may not have to be as long as the NID in the SNPN case, e.g., from a uniqueness perspective. However, this factor alone does not appear to justify a separate approach. If the P(ublic)LMN ID is used as part of the identifier, the NID will be locally unique within the PLMN.
  • the NID is used as a common term for approaches that are associated with both SNPN deployments and PNI-NPN deployments, then it may still be possible to differentiate it on network level.
  • NPN can have a separate list in broadcast, or at least in one way or another be distinguished such that all UEs that are not NPN-UE's will not recognize these "network IDs" as valid PLMN ID's.
  • Both these network ID's should be viewed as and treated as a "PLMN" that was handled in earlier releases. This means that it should be possible to configure, e.g,. cell ID's and TACs separately if desired.
  • the listing of the new network ID's i.e., the elements containing MCC, MNC, NID would need new formats.
  • a NPN-capable UE that detects broadcast information from a gNB that (only) support a PNI-NPN cell will first find a Network ID 1, with broadcast MCC 999, but it will not find an associated NID. This UE will thus continue to read the system information and find Network ID 2 (possibly at a different format) and then the UE would match the NPN identity with the iNPN identities it is allowed to access and conclude whether Network ID 2 is a candidate for access. See details of how this can be signaled in the following section named "Signaling options to only admit NPN-UEs".
  • a UE that is not capable of NPN communication will not be able to detect or not configured to decode the Network ID's that are formed by the MCC-MNC-NID/CAG triplet, and thus, it will only detect Network ID 1.
  • the broadcast of this PLMN ID is an efficient method to fulfil the requirement that UE's that are not allowed to access anything but public PLMN's should not attempt access.
  • Network types Network deployments Network ID Public Network Public Network MCC, MNC Non-Public Network Stand-Alone Private Network MCC, MNC, NID Non-Public Network PNI-NPN MCC, MNC, NID/CAG* * CAG, may be used to support different identifier names/lengths based on deployments, otherwise NID will work for both.
  • the procedures in the UE and network would then be:
  • the NAS and CN may use an extended NID solution to address both PNI-NPN and SNPN deployment scenarios.
  • the solution principle is similar to what has been described above with the following differences:
  • a method provides that, when using a particular PLMN, the network would make sure that non-NPN UEs are not accessing an NPN by indicating a special PLMN associated with that NPN.
  • the operator can, if this method is applied, configure only NPN UEs to consider this special PLMN as a valid PLMN, while other UEs would not be configured to consider the special PLMN as valid and would therefore refrain from accessing a network/cell which advertises this special PLMN.
  • a method according to some other embodiments in which NPNs are added in new list only comprehended by new UEs includes the network advertising NPN IDs in a list which is only comprehended by UEs supporting NPN.
  • An ASN.1 example showing how this can be implemented in 3GPP TS 38.331 v15.4.0 is provided below. The added parts to implement this method are shown with underlined and highlighted text. What is added is a new list of PLMNs named plmn-IdentityList-r16 (compared to the old plmn-IdentityList without suffix). This new list has entries of the type PLMN-IdentityInfo-r16 (compared to the old PLMN-IdentityInfo without suffix).
  • the new type PLMN-IdentityInfo-r16 can include NPN IDs. The operator would then, if it wants only NPN-UEs to access a certain cell place the PLMN and NID of the network in the new list. Legacy UEs would not comprehend this new list and hence would not consider the cell as valid.
  • modules may be stored in memory 305 of Figure 3 , and these modules may provide instructions so that when the instructions of a module are executed by respective wireless device processing circuitry 303, processing circuitry 303 performs respective operations disclosed herein.
  • modules may be stored in memory 405 of Figure 4 , and these modules may provide instructions so that when the instructions of a module are executed by respective RAN node processing circuitry 403, processing circuitry 403 performs respective operations of the flow chart.
  • modules may be stored in memory 505 of Figure 5 , and these modules may provide instructions so that when the instructions of a module are executed by respective CN node processing circuitry 503, processing circuitry 503 performs respective operations of the flow chart.
  • Figure 14 illustrates a system information block SIB according to some embodiments of inventive concepts.
  • the SIB 1 message may include information relevant when evaluating if a UE is allowed to access a cell and defines the scheduling of other system information.
  • SIB1 of Figure 14 may also include radio resource configuration information that is common for all UEs and barring information applied to the unified access control.
  • the SIB 1 message may include cellAccessRelatedInfo-NPN.
  • SIB1 may be extended with a new field cellAccessRelatedInfo-NPN as shown in Figure 14 , which in turn includes the non-public network list as well as a non-public network specific version of the cellReservedForOtherUse indication.
  • Figure 15 illustrates a non-public network NPN information element according to some embodiments of inventive concepts.
  • Figure 15 shows that the IE CellAccessRelatedInfo-NPN information element of Figure 14 indicates cell access related information for this cell for NPN UEs as shown in Figure 15 , including npn-IdentityList and cellReservedForOtherUse-NPN information elements.
  • the NPN-IdentityInfoList information element may include a list of NPN identity information, including: npn-IdentityList, trackingAreaCode, ranac, cellIdentity, and cellReservedForOperatorUse.
  • Each entry in the non-public network list may include the identity of the non-public network and other network information such as Cell ID, TAC, RAN area code, and a cellReservedForOperatorUse indication as shown in Figure 16 .
  • Figure 17 illustrates a PLMN identity information element according to some embodiments of inventive concepts.
  • the NPN-Identity information element of Figure 3 may identify a Non-Public Network (e.g., using a plmn-identity and one or both of a nid and/or a CAG-ID). Further information regarding how to set the IE may be specified in TS 23.003.
  • the term cell can have multiple interpretations. In some cases, the term cell may refer to the "physical cell," i.e., an entity broadcasting a set of MIB/SIBs and associated with a physical cell id (e.g., the Physical Cell ID (PCI) used by NR cells).
  • PCI Physical Cell ID
  • a certain cell may broadcast an SIB in which multiple PLMNs are indicated, and these PLMNs are then all considered to be the same cell, even if there are multiple PLMNs and Cell IDs within this cell.
  • Another interpretation of the term cell is that if there are multiple PLMNs/Cell IDs in a SIB, then each of these are considered as different logical cells.
  • FIG 18 is a flow chart illustrating radio access network operations according to some embodiments of inventive concepts. Operations of a RAN node 400 (implemented using the structure of Figure 6 ) will now be discussed with reference to the flow chart of Figure 8 according to some embodiments of inventive concepts.
  • modules may be stored in memory 405 of Figure 4 , and these modules may provide instructions so that when the instructions of a module are executed by respective RAN node processing circuitry 403, processing circuitry 403 performs respective operations of the flow chart.
  • processing circuitry 403 may provide a public network list including at least one entry.
  • processing circuitry 403 may provide a private network list including at least one identifier of a private network.
  • the at least one identifier of the private network may include a Public Land Mobile Network PLMN identifier of the private network and at least one of a network identifier NID and a closed access group CAG identifier.
  • processing circuitry 403 may broadcast the public network list and the private network list through transceiver 401 over a wireless interface. Broadcasting may include broadcasting the at least one identifier of the private network with at least one of a cell identifier associated with the at least one identifier of the private network and a tracking area code associated with the at least one identifier of the private network. For example, broadcasting may include broadcasting an indication that a cell associated with the PLMN identifier of the private network is reserved for other use. According to some embodiments, broadcasting may include broadcasting a system information block SIB (e.g., SIB1) including the public network list and the private network list.
  • SIB system information block SIB
  • the at least one identifier of the private network may include a first identifier of a first private network and a second identifier of a second private network.
  • the first identifier of the first private network may include a first PLMN identifier of the first private network and a first NID
  • the second identifier of the second private network may include a second PLMN identifier of the second private network and a second NID.
  • the first identifier of the first private network may include a first PLMN identifier of the first private network and a first CAG identifier
  • the second identifier of the second private network may include a second PLMN identifier of the second private network and a second CAG identifier.
  • the first and second PLMN identifiers may be the same or different.
  • broadcasting at block 811 may include broadcasting the private network list including the first identifier of the first private network and the second identifier of the second private network with at least one of a cell identifier associated with the first and second identifiers of the first and second private networks and a tracking area code associated with the first and second identifiers of the first and second private networks.
  • broadcasting at block 811 may include broadcasting the private network list including the first identifier of the first private network with at least one of a first cell identifier associated with the first identifier of the first private network and a first tracking area code associated with the first identifier of the first identifier of the first private network, and including the second identifier of the second private network with at least one of a second cell identifier associated with the second identifier of the second private network and a tracking area code associated with the second identifier of the second private network.
  • the at least one entry of the public network list may include a dummy identifier, such as a PLMN identifier that is reserved.
  • the at least one entry of the public network list may include a dummy identifier, and the PLMN identifier of the private network may be used as the dummy identifier in the public network list.
  • broadcasting at block 811 may include broadcasting an indication that a cell associated with the dummy identifier is reserved for other use.
  • the at least one entry of the public network list may include a public land mobile network PLMN identifier of a public network.
  • broadcasting at block 811 may include broadcasting the PLMN identifier of the public network with at least one of a cell identifier associated with the PLMN identifier of the public network and a tracking area code associated with the PLMN identifier of the public network.
  • FIG. 19 is a flow chart illustrating wireless device operations according to some embodiments of inventive concepts. Operations of the wireless device 300 (implemented using the structure of the block diagram of Figure 3 ) will now be discussed with reference to the flow chart of Figure 19 according to some embodiments of inventive concepts.
  • modules may be stored in memory 305 of Figure 5 , and these modules may provide instructions so that when the instructions of a module are executed by respective wireless device processing circuitry 303, processing circuitry 303 performs respective operations of the flow chart.
  • processing circuitry 303 may receive a broadcast (through transceiver 301) from a radio access node of a wireless communication network, and the broadcast may include a public network list including at least one entry and a private network list including at least one identifier of a private network.
  • the at least one identifier of the private network may include a PLMN identifier of the private network and at least one of an NID and a CAG identifier.
  • the broadcast may include a system information block SIB (e.g., SIB1) including the public network list and the private network list.
  • SIB system information block SIB
  • processing circuitry 303 may select a network from the public network list or the private network list based on an access mode of the wireless device.
  • the access mode for example, may be based on at least one of a capability of the wireless device, a configuration of the wireless device, and/or a desired service.
  • processing circuitry 303 may perform at least one of: using the network selected from the public network list or the private network list; camping on the network selected from the public network list or the private network list; and/or accessing the network selected from the public network list or the private network list.
  • the broadcast may include the at least one identifier of the private network with at least one of a cell identifier associated with the at least one identifier of the private network and a tracking area code associated with the at least one identifier of the private network.
  • the broadcast may include an indication that a cell associated with the PLMN identifier of the private network is reserved for other use.
  • the at least one identifier of the private network may include a first identifier of a first private network and a second identifier of a second private network.
  • the first identifier of the first private network may include a first PLMN identifier of the first private network and a first NID
  • the second identifier of the second private network may include a second PLMN identifier of the second private network and a second NID.
  • the first identifier of the first private network may include a first PLMN identifier of the first private network and a first CAG identifier
  • the second identifier of the second private network may include a second PLMN identifier of the second private network and a second CAG identifier.
  • the first and second PLMN identifiers may be the same or different.
  • the broadcast may include the private network list including the first identifier of the first private network and the second identifier of the second private network with at least one of a cell identifier associated with the first and second identifiers of the first and second private networks and a tracking area code associated with the first and second identifiers of the first and second private networks.
  • the broadcast may include the private network list including the first identifier of the first private network with at least one of a first cell identifier associated with the first identifier of the first private network and a first tracking area code associated with the first identifier of the first identifier of the first private network, and including the second identifier of the second private network with at least one of a second cell identifier associated with the second identifier of the second private network and a tracking area code associated with the second identifier of the second private network.
  • the at least one entry of the public network list may include a dummy identifier, such as a PLMN identifier that is reserved.
  • the broadcast may include an indication for the public network list indicating that a cell of the public network list is reserved, the wireless device may be configured to access a private network, and selecting at block 909 may include ignoring the indication for the public network list indicating that the cell is reserved based on being configured to access a private network and selecting a private network based on the private network list.
  • the broadcast may also include an indication for the private network list indicating that a cell of the private network list is reserved, and selecting at block 909 may further include ignoring the indication for the private network list indicating that the cell of the private network list is reserved.
  • the at least one entry of the public network list may include a dummy identifier, and the PLMN identifier of the private network may be used as the dummy identifier in the public network list.
  • the broadcast may include an indication that a cell associated with the dummy identifier is reserved for other use.
  • the at least one entry of the public network list may include a PLMN identifier of a public network.
  • the broadcast may include the PLMN identifier of the public network with at least one of a cell identifier associated with the PLMN identifier of the public network and a tracking area code associated with the PLMN identifier of the public network.
  • the wireless device may be configured to access a private network
  • selecting at block 909 may include ignoring the public network list and selecting a private network from the private network list based on being configured to access a private network.
  • any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses.
  • Each virtual apparatus may comprise a number of these functional units.
  • These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like.
  • the processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory (RAM), cache memory, flash memory devices, optical storage devices, etc.
  • Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein.
  • the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.
  • the term unit may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.
  • the terms “comprise”, “comprising”, “comprises”, “include”, “including”, “includes”, “have”, “has”, “having”, or variants thereof are open-ended, and include one or more stated features, integers, elements, steps, components or functions but does not preclude the presence or addition of one or more other features, integers, elements, steps, components, functions or groups thereof.
  • the common abbreviation “e.g.”, which derives from the Latin phrase “exempli gratia” may be used to introduce or specify a general example or examples of a previously mentioned item, and is not intended to be limiting of such item.
  • the common abbreviation “i.e.”, which derives from the Latin phrase “id est,” may be used to specify a particular item from a more general recitation.
  • Example embodiments are described herein with reference to block diagrams and/or flowchart illustrations of computer-implemented methods, apparatus (systems and/or devices) and/or computer program products. It is understood that a block of the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations, can be implemented by computer program instructions that are performed by one or more computer circuits.
  • These computer program instructions may be provided to a processor circuit of a general purpose computer circuit, special purpose computer circuit, and/or other programmable data processing circuit to produce a machine, such that the instructions, which execute via the processor of the computer and/or other programmable data processing apparatus, transform and control transistors, values stored in memory locations, and other hardware components within such circuitry to implement the functions/acts specified in the block diagrams and/or flowchart block or blocks, and thereby create means (functionality) and/or structure for implementing the functions/acts specified in the block diagrams and/or flowchart block(s).

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Claims (15)

  1. Verfahren zum Betreiben einer Basisstation (400) in einer Zelle eines Drahtloskommunikationsnetzwerks, wobei das Verfahren umfasst:
    Senden (601) einer ersten Netzwerkliste, die eine Mehrzahl von Kennungen öffentlicher Netzwerke umfasst, die öffentlichen Netzwerken in der Zelle entsprechen, per Broadcast an eine Benutzereinrichtung, UE, (300);
    Senden (602) einer zweiten Netzwerkliste, die eine Mehrzahl von Kennungen nichtöffentlicher Netzwerke, NPN, umfasst, die NPNs in der Zelle entsprechen, per Broadcast an die UE;
    wobei jede der Mehrzahl von Kennungen öffentlicher Netzwerke und der NPN-Kennungen eine Mehrzahl von Datenfeldern umfasst und
    wobei die Netzwerkkennungen eine Mobilfunk-Landeskennzahl, MCC, eine Mobilfunk-Netzwerkkennzahl, MNC, eine Steuerungszugriffsgruppe, CAG, und eine Netzwerkkennung, NID, umfassen.
  2. Verfahren nach Anspruch 1, wobei:
    - das NPN ein eigenständiges privates Netzwerk, SNPN, umfasst, das getrennt von einem öffentlichen Landfunknetzwerk, PLMN, bereitgestellt wird; oder
    - das NPN ein integriertes privates Netzwerk, PNI-NPN, umfasst, das in ein öffentliches Landfunknetzwerk, PLMN, integriert ist; oder
    - die Zelle des Drahtloskommunikationsnetzwerks einer Zelle eines öffentlichen Landfunknetzwerks, PLMN, oder einer von einer PNI-NPN-Zelle oder einer Zelle eines eigenständigen privaten Netzwerks, SNPN, entspricht; oder
    - die Mehrzahl von Netzwerkkennungen, die per Broadcast gesendet wird, MCC = 999 und MNC umfasst, um Legacy- und Nicht-NPN-UEs davon abzuhalten, ein öffentliches Landfunknetzwerk, PLMN, auszuwählen; oder
    - die Mehrzahl von Netzwerkkennungen die MCC, die MNC und eine NID, die einem öffentlichen Landfunknetzwerk, PLMN, eines Betreibers entspricht, und eine NID/CAG umfasst, die anzeigt, dass ein integriertes privates Netzwerk, PNI-NPN, verfügbar ist.
  3. Verfahren nach Anspruch 1, wobei das NPN ein eigenständiges privates Netzwerk, SNPN, umfasst, das getrennt von einem öffentlichen Landfunknetzwerk, PLMN, bereitgestellt wird, und wobei:
    - die Netzwerkkennung in Reaktion auf eine SNPN-Bereitstellung das PLMN und die NID umfasst; und/oder
    - die Netzwerkkennung in Reaktion auf eine Bereitstellung eines integrierten privaten Netzwerks, PNI-NPN, die MMC, die MNC und die CAG umfasst, wobei optional die zweite Liste ein Bit umfasst, das anzeigt, ob die Netzwerkkennung ein SNPN oder ein PNI-NPN identifiziert; und/oder
    - das PLMN ein Dummy-PLMN umfasst.
  4. Verfahren nach Anspruch 3, wobei die MCC auf einen Wert von 999 gesetzt wird.
  5. Verfahren nach Anspruch 1, wobei
    das NPN ein eigenständiges privates Netzwerk, SNPN, umfasst, das getrennt von einem öffentlichen Landfunknetzwerk, PLMN, bereitgestellt wird;
    das NPN ein integriertes privates Netzwerk, PNI-NPN, umfasst, das in ein öffentliches Landfunknetzwerk, PLMN, integriert ist, und
    eine PLMN-Kennung dem SNPN und dem PNI-NPN gemeinsam ist.
  6. Verfahren nach Anspruch 1, wobei eine cellReservedForOtherUse-Funktion Legacy- und Nicht-NPN-UEs davon abhält, ein öffentliches Landfunknetzwerk, PLMN, auszuwählen.
  7. Verfahren nach Anspruch 6, wobei eine Systeminformationsblock-,SIB-,Nachricht Informationen zum Beurteilen umfasst, ob eine UE Zugang zu einer Zelle erlangt, und Disposition von Systeminformationen definiert,
    wobei die SIB-Nachricht eine Feldzelle zum Speichern von CellAccessRelatedlnfo-NPN umfasst, die eine NPN-Liste und eine NPN-spezifische Version der cellReservedForOtherUse-Anzeige umfasst.
  8. Verfahren nach Anspruch 7, wobei ein NPN-Informationselement ein IE-CellAccessRelatedlnfo-NPN-Informationselement umfasst, das zellzugangsbezogene Informationen und eine npn-ldentitylist und cellReservedForOtherUse-NPN-Informationen anzeigt.
  9. Basisstation (400) eines Funkzugangsnetzwerks, wobei die Basisstation zum Durchführen von Operationen nach einem der Ansprüche 1 bis 8 ausgelegt ist.
  10. Verfahren zum Betreiben einer drahtlosen Vorrichtung (300) in einem Drahtloskommunikationsnetzwerk, wobei das Verfahren umfasst:
    Erkennen (801) von per Broadcast gesendeten Informationen von einer Basisstation (400), wobei die per Broadcast gesendeten Informationen umfassen:
    eine erste Netzwerkliste, die eine Mehrzahl von Kennungen öffentlicher Netzwerke umfasst, die öffentlichen Netzwerken in einer Zelle entsprechen;
    eine zweite Netzwerkliste, die eine Mehrzahl von Kennungen nicht öffentlicher Netzwerke, NPN, umfasst, die NPNs in der Zelle entsprechen;
    Auslesen von Systeminformationen, die den Broadcasts von der Basisstation entsprechen; und
    Bestimmen, ob die Zelle, die den per Broadcast gesendeten Informationen entspricht, für Zugang durch die UE verfügbar ist,
    wobei jede der Mehrzahl von Kennungen öffentlicher Netzwerke und der NPN-Kennungen eine Mehrzahl von Datenfeldern umfasst und
    wobei die Netzwerkkennungen eine Mobilfunk-Landeskennzahl, MCC, eine Mobilfunk-Netzwerkkennzahl, MNC, eine Steuerungszugriffsgruppe, CAG, und eine Netzwerkkennung, NID, umfassen.
  11. Verfahren nach Anspruch 10, wobei die UE nicht-NPN-fähig ist,
    wobei eine UE-Access-Stratum,-AS-,Schicht zum Melden von Netzwerkkennungen an eine UE-Non-Access-Stratum,-NAS-,Schicht für identifizierte Netzwerke konfiguriert ist, und
    wobei die UE zum Empfangen einer Kennung eines ausgewählten Netzwerks von der UE-NAS-Schicht konfiguriert ist, wobei optional in Reaktion darauf, dass die MCC 999 ist, ein entsprechendes Netzwerk nicht ausgewählt wird.
  12. Verfahren nach Anspruch 10, wobei die UE NPN-fähig ist, und
    wobei eine UE-Access-Stratum-,AS-,Schicht zum Melden von Netzwerkkennungen an eine UE-Nicht-Access-Stratum-,NAS-,Schicht für identifizierte Netzwerke konfiguriert ist, wobei optional die Netzwerkkennungen umfassen: MCC und MNC für öffentliche Landfunknetzwerke, PLMNs, MCC, MNC und NID für eigenständige private Netzwerke, SNPNs, und/oder MCC, MNC und CAG für integrierte private Netzwerke, PNI-NPNs.
  13. Verfahren nach Anspruch 12, wobei die UE zum Empfangen einer Kennung eines ausgewählten Netzwerks von der UE-NAS-Schicht konfiguriert ist.
  14. Verfahren nach Anspruch 10, wobei:
    - die UE NPN-fähig ist, wobei eine UE-Access-Stratum-,AS-,Schicht zum Melden von Netzwerkkennungen an eine UE-Nicht-Access-Stratum-,NAS-,Schicht für identifizierte Netzwerke konfiguriert ist, wobei der MCC-Wert 999 umfasst und wobei die UE-NAS Netzwerke ignoriert, die dem MCC-Wert von 999 entsprechen; oder
    - das Verfahren ferner ein Durchführen einer Suche durch eine UE-Access-Stratum, AS, zum Identifizieren verfügbarer Netzwerke und Melden der verfügbaren Netzwerke an eine UE-NAS umfasst.
  15. Drahtlose Vorrichtung (300), umfassend:
    einen Sendeempfänger (1401), der zum Bereitstellen von Drahtlosnetzwerkkommunikation mit einem Drahtloskommunikationsnetzwerk konfiguriert ist; und
    einen Prozessor (1403), der mit dem Sendeempfänger gekoppelt ist, wobei der Prozessor zum Ausführen nach einem der Ansprüche 10 bis 14 konfiguriert ist.
EP20718378.1A 2019-03-28 2020-03-27 Verfahren zum senden von listen öffentlicher und nichtöffentlicher netzwerke und zugehörige netzwerkknoten und drahtlose vorrichtungen Active EP3949522B1 (de)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US201962825653P 2019-03-28 2019-03-28
US201962872770P 2019-07-11 2019-07-11
PCT/IB2020/052966 WO2020194273A1 (en) 2019-03-28 2020-03-27 Methods of broadcasting public and non-public network lists and related network nodes and wireless devices

Publications (2)

Publication Number Publication Date
EP3949522A1 EP3949522A1 (de) 2022-02-09
EP3949522B1 true EP3949522B1 (de) 2024-02-14

Family

ID=70277421

Family Applications (1)

Application Number Title Priority Date Filing Date
EP20718378.1A Active EP3949522B1 (de) 2019-03-28 2020-03-27 Verfahren zum senden von listen öffentlicher und nichtöffentlicher netzwerke und zugehörige netzwerkknoten und drahtlose vorrichtungen

Country Status (3)

Country Link
US (1) US20220201592A1 (de)
EP (1) EP3949522B1 (de)
WO (1) WO2020194273A1 (de)

Families Citing this family (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11711757B2 (en) * 2018-10-18 2023-07-25 Apple Inc. Systems, methods, and devices for access control for private slices in a PLMN
EP3922060A4 (de) * 2019-03-27 2022-03-23 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Benutzergerät und verfahren zur auswahl eines öffentlichen landfunknetzes davon
US20220240147A1 (en) * 2019-06-14 2022-07-28 Nokia Technologies Oy Method and apparatus for providing network triggered mobility between a stand-alone non-public network and a public land mobile network
CN112399558A (zh) * 2019-08-16 2021-02-23 华为技术有限公司 寻呼的方法和装置
WO2021057901A1 (en) * 2019-09-26 2021-04-01 FG Innovation Company Limited Methods and apparatuses for performing cell (re) selection in non-public network
KR20210144211A (ko) * 2020-05-21 2021-11-30 삼성전자주식회사 단말 가입자 데이터를 프로비저닝하기 위한 네트워크를 검색하고 선택하는 방법 및 장치
US11838860B2 (en) * 2020-06-01 2023-12-05 FG Innovation Company Limited Method of performing closed access group selection in non-public network and related device
ES2946912T3 (es) * 2020-07-09 2023-07-27 Deutsche Telekom Ag Procedimiento para una funcionalidad de interconexión mejorada entre una primera red de comunicación móvil por un lado y una segunda red de comunicación móvil por otro lado, sistema, red de comunicación móvil, identificador de red y funcionalidad de traducción de números, programa y producto de programa informático
US20220053444A1 (en) * 2020-08-13 2022-02-17 Alibaba Group Holding Limited Network Communication Method and Apparatus
US12028710B2 (en) * 2020-10-15 2024-07-02 Mediatek Inc. Stand-alone Non-Public Network as service provider
KR102539545B1 (ko) * 2021-03-31 2023-06-05 엘지전자 주식회사 연관된 네트워크 식별자의 시그널링
EP4320927A1 (de) * 2021-05-10 2024-02-14 Apple Inc. Onboarding eines benutzergeräts und netzwerküberlastungssteuerung in eigenständigen nichtöffentlichen netzwerkbereitstellungen
CN117715153A (zh) * 2022-09-06 2024-03-15 维沃移动通信有限公司 选网处理方法、装置、终端及可读存储介质

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020037086A1 (en) * 2018-08-14 2020-02-20 Liao Ching Yu Network discovery, selection, and access control in vertical domain
WO2020102292A1 (en) * 2018-11-14 2020-05-22 Apple Inc. Network selection and service continuity in non-public networks

Also Published As

Publication number Publication date
WO2020194273A1 (en) 2020-10-01
EP3949522A1 (de) 2022-02-09
US20220201592A1 (en) 2022-06-23

Similar Documents

Publication Publication Date Title
EP3949522B1 (de) Verfahren zum senden von listen öffentlicher und nichtöffentlicher netzwerke und zugehörige netzwerkknoten und drahtlose vorrichtungen
EP3253160B1 (de) Endgerätevorrichtung und verfahren
EP3297334B1 (de) Endgerätevorrichtung, basisstationsvorrichtung und verfahren
JP6544593B2 (ja) 標準および拡張カバレッジモードにおけるセル選択および再選択
EP3639564B1 (de) Wiederauswahl einer zellenauswahl und camping
CN106797534B (zh) 无线通信***中的用户设备的装置对装置(d2d)操作方法和使用该方法的用户设备
KR102165874B1 (ko) 무선 통신 시스템에서 단말에 의해 수행되는 d2d(device-to-device) 동작 방법 및 상기 방법을 이용하는 단말
KR101845178B1 (ko) 무선 통신 시스템에서 단말에 의해 수행되는 d2d 동작 방법 및 상기 방법을 이용하는 단말
US9706544B2 (en) Method for registering and updating base station information in converged network supporting multiple communication systems, and device therefor
WO2015046973A1 (ko) 무선 통신 시스템에서 단말에 의해 수행되는 d2d 통신 방법 및 이를 지원하는 장치
US20180359681A1 (en) Radio terminal, base station, and method therefor
CN106576334B (zh) 在无线通信***中由终端执行的装置对装置(d2d)操作方法和使用该方法的终端
KR20180075585A (ko) 시스템 정보를 전송하는 방법, 기지국, 단말 및 시스템
US9832711B2 (en) Method of transmitting and receiving cell information by using synchronization signal and device supporting same
WO2016060524A1 (ko) 무선 통신 시스템에서 단말의 d2d(device-to-device) 데이터 전송 방법 및 상기 방법을 이용하는 단말
US20100105380A1 (en) Method and apparatus for broadcasting system information in a wireless communication network
KR102657112B1 (ko) 무선 통신 시스템에서 단말의 사이드링크 동작 방법 및 상기 방법을 이용하는 단말
EP3949224A1 (de) Systeme und verfahren für funkbetrieb mit reduzierter bandbreite
KR101670622B1 (ko) Cellular-wifi 융합시스템에서 일반장치로부터 획득한 정보를 이용하여 wifi 망을 통해 access point를 등록하는 방법 및 장치
CN106233785B (zh) 在无线通信***中由终端执行的装置对装置(d2d)操作方法及使用该方法的终端
WO2016121538A1 (ja) 端末装置、基地局装置および方法
KR20180104017A (ko) 시스템 메시지 처리 방법, 네트워크 장치 및 사용자 기기
WO2016121514A1 (ja) 端末装置、基地局装置および方法
CN106688279A (zh) 在无线通信***中由终端执行的装置对装置d2d操作方法和使用该方法的终端
CN106688282B (zh) 在无线通信***中操作终端的方法以及使用该方法的终端

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: UNKNOWN

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20210928

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

INTG Intention to grant announced

Effective date: 20230920

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602020025648

Country of ref document: DE

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20240327

Year of fee payment: 5

Ref country code: GB

Payment date: 20240327

Year of fee payment: 5

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG9D

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20240214

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20240614

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20240214

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20240515

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1658123

Country of ref document: AT

Kind code of ref document: T

Effective date: 20240214

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20240514

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20240214

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20240214

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20240214

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20240214

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20240514

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20240514

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20240214

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20240214

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20240614

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20240214

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20240515

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20240214

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20240214

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20240214

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20240214

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20240214

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20240614