APPARARUS, METHOD, AND COMPUTER PROGRAM

Abstract

An apparatus comprising: at least one processor; and at least one memory including computer program code; the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to: determine that an onboarding standalone non private network and/or service provider hosting the apparatus does not own subscription data for a terminal, in response to the terminal performing an initial access to the onboarding standalone non private network and/or service provider; obtain subscription data for the terminal owned by another standalone non private network and/or service provider from a central provisioning server; and provide subscription data to the terminal.

Claims

1-21. (canceled)

22. A local provisioning server comprising: at least one processor; and at least one memory including computer program code; the at least one memory and the computer program code configured to, with the at least one processor, cause the local provisioning server at least to: determine that an onboarding standalone non-public network hosting the local provisioning server does not own subscription data for a terminal camping to the onboarding standalone non-public network after initial access to cells of the onboarding standalone non-public network and authentication of the terminal; obtain subscription data for the terminal owned by another standalone non-public network from a central provisioning server; and provide subscription data to the terminal.

23. The local provisioning server of claim 22, wherein the subscription data for the terminal includes at least one of: an identifier of the another standalone non-public network, an identifier of a roaming group or a parameter to establish a packet data unit session.

24. The local provisioning server of claim 22, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the local provisioning server at least to: store, in the at least one memory, subscription data for at least one other terminal owned by the onboarding standalone non-public network; and provide the subscription data for the at least one other terminal to the central provisioning server.

25. The local provisioning server of claim 24, wherein the subscription data for the at least one other terminal includes at least one of: an identifier of the onboarding standalone non-public network, an identifier of a roaming group or a parameter to establish a packet data unit session.

26. The local provisioning server of claim 22, wherein the at least one memory and the computer program code may be further configured to, with the at least one processor, cause the apparatus at least to: determine that the onboarding standalone non-public network hosting the local provisioning server owns subscription data for at least one other terminal camping to the onboarding standalone non-public network after initial access to cells of the onboarding standalone non-public network and authentication of the at least one other terminal; and provide the subscription data for the at least one other terminal to the at least one other terminal.

27. The local provisioning server of claim 22, wherein the central provisioning server is hosted outside the onboarding standalone non-public network and outside the another standalone non-public network.

28. The local provisioning server of claim 22, wherein the central provisioning server is administered by the onboarding standalone non-public network and the another standalone non-public network.

29. The local provisioning server of claim 22, wherein the onboarding standalone non-public network and the another standalone non-public network are part of a same roaming group.

30. The apparatus of claim 22, wherein the onboarding standalone non-public network and the another standalone non-public network are part of different roaming groups.

31. The local provisioning server of claim 23, wherein the subscription data for the terminal includes the parameter to establish a packet data unit session and the parameter to establish a packet data unit session comprises at least one of: single network slice selection assistance information; a data network name; a terminal route selection policy; or a quality of service rule.

32. A central provisioning server comprising: at least one processor; and at least one memory including computer program code; the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to: receive a query to obtain subscription data owned by a standalone non-public network for a terminal from a local provisioning server hosted by an onboarding standalone non-public network; and provide the subscription data owned by the standalone non-public network for the terminal to the local provisioning server.

33. The central provisioning server of claim 32, wherein the central provisioning server is hosted outside the onboarding standalone non-public network.

34. The central provisioning server of claim 32, wherein the central provisioning server is administered by the standalone non-public network and the onboarding standalone non-public network.

35. The central provisioning server of claim 32, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus at least to: receive subscription data owned by the standalone non-public network for the terminal from a local provisioning server hosted by the standalone non-public network; and store, in the at least one memory, the subscription data owned by the standalone non-public network for the terminal.

36. The central provisioning server of claim 32, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus at least to: receive subscription data owned by the onboarding standalone non-public network for another terminal from the local provisioning server hosted by the onboarding standalone non-public network; and store, in the at least one memory, subscription data owned by the onboarding standalone non-public network for another terminal.

37. The central provisioning server of claim 32, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus at least to: receive subscription data owned by at least one other onboarding standalone non-public network for at least one other terminal from the local provisioning server hosted by the at least one other onboarding standalone non-public network; and store the subscription data owned by at least one other onboarding standalone non-public network for at least one other terminal.

38. A method comprising: determining that an onboarding standalone non-public network hosting a local provisioning server does not own subscription data for a terminal camping to cells of the onboarding standalone non-public network after initial access to cells of the onboarding standalone non-public network and authentication of the terminal; obtaining subscription data for the terminal owned by another standalone non-public network from a central provisioning server; and providing subscription data to the terminal.

39. The method of claim 38, wherein the subscription data for the terminal includes at least one of: an identifier of the another standalone non-public network, an identifier of a roaming group or a parameter to establish a packet data unit session.

40. The method of claim 38, further comprising: storing subscription data for at least one other terminal owned by the onboarding standalone non-public network; and providing the subscription data for the at least one other terminal to the central provisioning server.

41. The method of claim 38, further comprising: determining that the onboarding standalone non-public network hosting the local provisioning server owns subscription data for at least one other terminal camping to the onboarding standalone non-public network after initial access to cells of the onboarding standalone non-public network and authentication of the at least one other terminal; and providing the subscription data for the at least one other terminal to the at least one other terminal.

Description

BRIEF DESCRIPTION OF THE FIGURES

[0156] Embodiments will now be described, by way of example only, with reference to the accompanying Figures in which:

[0157] FIG. 1 shows a schematic representation of a 5G system;

[0158] FIG. 2 shows a schematic representation of a control apparatus;

[0159] FIG. 3 shows a schematic representation of a terminal;

[0160] FIG. 4 shows a schematic representation of a signalling diagram of a process for providing subscription data to a terminal;

[0161] FIG. 5 shows a schematic representation of block diagram of a method performed by a local provisioning server for providing subscription data to a terminal;

[0162] FIG. 6 shows a schematic representation of block diagram of a method performed by a central provisioning server for providing subscription data to a terminal;

[0163] FIG. 7 shows a schematic representation of block diagram of a method performed by a terminal for being provided subscription data; and

[0164] FIG. 8 shows a schematic representation of a non-volatile memory medium storing instructions which when executed by a processor allow a processor to perform one or more of the steps of the methods of FIGS. 5 to 7.

DETAILED DESCRIPTION OF THE FIGURES

[0165] In the following certain embodiments are explained with reference to mobile communication devices capable of communication via a wireless cellular system and mobile communication systems serving such mobile communication devices. Before explaining in detail the exemplifying embodiments, certain general principles of a wireless communication system, access systems thereof, and mobile communication devices are briefly explained with reference to FIGS. 1, 2 and 3 to assist in understanding the technology underlying the described examples.

[0166] FIG. 1 shows a schematic representation of a 5G system (5GS). The 5GS may comprises an onboarding standalone non-private network (OSNPN) and/or an onboarding service provider (OSP) domain. The OSNPN and/or OSP domain may comprise a user equipment (UE), a radio access network (RAN) and a core network (CN). The RAN may comprise one or more gNodeB (gNB) distributed unit functions connected to one or more gNodeB (gNB) centralized unit functions. The CN may comprise an access management function (AMF), a session management function (SMF), an authentication server function (AUSF), a user data management (UDM), a user plane function (UPF), a policy control function (PCF), a network slice selection function (NSSF) and/or a local provisioning server (LPS).

[0167] The 5GS may further comprise a central provisioning server (CPS) and/or a default credential server (DCS). The CPS and/or DCS may be outside the OSNPN and/or OSP. The CPS and/or DCS may be managed by group of SNPN and/or SP who will allow terminals to onboard through their network.

[0168] FIG. 2 illustrates an example of a control apparatus 200 for controlling a function of the RAN or the CN as illustrated on FIG. 1. The control apparatus may comprise at least one random access memory (RAM) 211a, at least on read only memory (ROM) 211b, at least one processor 212, 213 and an input/output interface 214. The at least one processor 212, 213 may be coupled to the RAM 211a and the ROM 211b. The at least one processor 212, 213 may be configured to execute an appropriate software code 215. The software code 215 may for example allow to perform one or more steps to perform one or more of the present aspects. The software code 215 may be stored in the ROM 211b. The control apparatus 200 may be interconnected with another control apparatus 200 controlling another function of the RAN or the CN. In some embodiments, each function of the RAN or the CN comprises a control apparatus 200. In alternative embodiments, two or more functions of the RAN or the CN may share a control apparatus.

[0169] FIG. 3 illustrates an example of a terminal 300, such as the terminal illustrated on FIG. 1. The terminal 300 may be provided by any device capable of sending and receiving radio signals. Non-limiting examples comprise a user equipment, a mobile station (MS) or mobile device such as a mobile phone or what is known as a ‘smart phone’, a computer provided with a wireless interface card or other wireless interface facility (e.g., USB dongle), a personal data assistant (PDA) or a tablet provided with wireless communication capabilities, a machine-type communications (MTC) device, a Cellular Internet of things (CIoT) device or any combinations of these or the like. The terminal 300 may provide, for example, communication of data for carrying communications. The communications may be one or more of voice, electronic mail (email), text message, multimedia, data, machine data and so on.

[0170] The terminal 300 may receive signals over an air or radio interface 307 via appropriate apparatus for receiving and may transmit signals via appropriate apparatus for transmitting radio signals. In FIG. 3 transceiver apparatus is designated schematically by block 306. The transceiver apparatus 306 may be provided for example by means of a radio part and associated antenna arrangement. The antenna arrangement may be arranged internally or externally to the mobile device.

[0171] The terminal 300 may be provided with at least one processor 301, at least one memory ROM 302a, at least one RAM 302b and other possible components 303 for use in software and hardware aided execution of tasks it is designed to perform, including control of access to and communications with access systems and other communication devices. The at least one processor 301 is coupled to the RAM 302a and the ROM 211b. The at least one processor 301 may be configured to execute an appropriate software code 308. The software code 308 may for example allow to perform one or more of the present aspects. The software code 308 may be stored in the ROM 302b.

[0172] The processor, storage and other relevant control apparatus can be provided on an appropriate circuit board and/or in chipsets. This feature is denoted by reference 304. The device may optionally have a user interface such as keypad 305, touch sensitive screen or pad, combinations thereof or the like. Optionally one or more of a display, a speaker and a microphone may be provided depending on the type of the device.

[0173] Industry 4.0 comprises several use cases with stringent requirements in terms of latency, reliability and high-accuracy positioning. The combination of 5G technology with enterprise network solutions becomes crucial to satisfy these requirements in indoor, private environments. In this context, the concept of non-public network (NPN) has emerged.

[0174] One or more aspect of this disclosure relate to NPNs and more specifically to the problem of onboarding a terminal (i.e. providing subscription data to a terminal) by an NPN.

[0175] There are two kinds of NPN: standalone NPN (SNPN) and public network integrated (PNI-NPN) works. TS 23.501 describe how both the SNPN and the PNI-NPN work.

[0176] TR 23.700-07 (section 5) identifies multiple key issues. One or more aspect of this disclosure relate to key issue #4: UE onboarding and remote provisioning). The key issue #4 include in particular the following problems:

[0177] “Which network entity performs UE's subscription provisioning and where is the network entity located”.

[0178] “If the network entity performing UE subscription provisioning is external to the SNPN, what is the service-based interface exposed by the SNPN towards that network entity for UE onboarding and provisioning”.

[0179] One or more aspect of this disclosure relate to a deployment where a terminal has a default credential and needs to be onboarded by an onboarding SNPN (OSNPN). That is, the terminal needs to be provided with subscription data by the OSNPN.

[0180] In a scenario, the terminal may be camping to the OSNPN network and the OSNPN may own subscription data for the terminal (i.e. the OSPN may be a home SNPN).

[0181] In another scenario, the terminal may be camping to the OSNPN and the OSNPN may not own the subscription (i.e. the OSPN may be different from a home SNPN). Another SNPN different from the OSNPN may own the subscription data for the terminal (i.e. the SNPN may be a home SNPN). The other SNPN and the OSNPN may be part of a same roaming group (RG) (e.g. same area).

[0182] In another scenario, the terminal may be camping to the OSNPN and the OSNPN may not own the subscription (i.e. the OSNPN may be different from a home SNPN). A first SNPN different from the OSNPN may own the subscription data for the terminal (i.e. the first SNPN may be a home SNPN for the terminal). The first SNPN and the OSNPN may be part of different RGs (e.g. different areas). A second SNPN different from the OSNPN may not own the subscription data for the terminal (i.e. the second SNPN may be different from a home SNPN). The second SNPN and the OSNPN may be part of a same RG (e.g. same area). The first SNPN and the second SNPN may be roaming partners so that the terminal may use the subscription data owned by the first SNPN for the terminal to access the second SNPN.

[0183] One or more aspects of this disclosure provide a dynamic provisioning solution for a deployment where SNPNs may be independent from service providers (SP).

[0184] Subscription data for a terminal may be owned by a SNPN and/or by a SP. Multiple SNPNs and/or SPs may be part of a same (RG. In a RG, each SNPN and/or SP may own subscription data for its own terminals (i.e. subscribers) but not for the terminals of other SNPNs and/or SPs in the RG.

[0185] One or more aspects of this disclosure introduce the concept of central provisioning server (CPS) owned by a plurality of SNPN. The plurality of SNPN may comprise an OSNPN and/or OSP and at least one other SNPN and/or SP.

[0186] A local provisioning server (LPS) may be hosted by the OSNPN and/or OSP. The LPS may be administered by the OSNPN and/or OSP.

[0187] At least one other LPS may be hosted by the at least one other SNPN and/or SP. The at least one other LPS may be administered by the at least one other SNPN and/or SP.

[0188] The CPS may not be hosted by the OSNPN and/or OSP. The CPS may be administered the OSNPN and/or OSP and the at least one other SNPN and/or SP. The OSNPN and/or the OSP and the at least one other SNPN and/or SP may have a roaming agreement to onboard terminals.

[0189] The LPS hosted by the OSNPN and/or OSP may be configured with a OSNPN identifier (ID) and/or OSP ID along with a RG ID for its own terminals (i.e. subscribers).

[0190] The LPS hosted by the at least one other SNPN and/or SP may be configured with a SNPN ID and/or SP ID along with a RG ID for its own terminals (i.e. subscribers).

[0191] The OSNPN ID and/or SP ID of the LPS hosted by the OSNPN and/or OSP may be different from the SNPN ID and/or SP ID of the LPS hosted by the at least one other SNPN and/or SP.

[0192] The RG ID of the LPS hosted by the OSNPN and/or OSP may be the same or may be different from the RG ID of the LPS hosted by the at least one other SNPN and/or SP. The RG ID of the LPS hosted by the OSNPN and/or OSP may be the same as the RG ID of the LPS hosted by the at least one other SNPN and/or SP based on a roaming agreement to onboard terminals.

[0193] The LPS hosted by the OSNPN and/or OSP may store terminal configuration parameters. The terminal configuration parameters may comprise parameters allowing the terminal to access the OSNPN and/or OSP and establish a regular PDU session. A regular PDU session may be used to make voice calls, transfer data or the like. The terminal configuration parameters may comprise PDU session parameters such as single network slice assistance information (SNSSAI), data network name (DNN), UE route selection policies (URSP) or quality of service (QoS) rules.

[0194] The LPS hosted by the OSNPN and/or OSP may provide the SNPN ID and/or SPD ID and the terminal configuration parameters for its own terminals (i.e. subscribers) to the CPS.

[0195] Likewise, the LPS hosted by the at least one other SNPN and/or SP may store terminal configuration parameters. The terminal configuration parameters may comprise to access at least one other SNPN and/or SP and establish a regular PDU session. The terminal configuration parameters may comprise PDU session parameters such as SNSSA), DNN, URSP or QoS rules.

[0196] The LPS hosted by the at least one other SNPN and/or SP may provide the SNPN ID and/or SPD ID and terminal configuration parameters for its own terminals (i.e. subscribers) to the CPS.

[0197] When a terminal camps on the OSNPN and/or OSP after initial access to the cells and successful authentication is performed with the DCS, the LPS hosted by the OSNPN and/or OSP may check whether the OSNPN and/or OSP owns subscription data for the terminal.

[0198] If the OSNPN and/or OSP owns subscription data for the terminal, the LPS hosted by the OSNPN and/or OSP may provide the subscription data for the terminal to the terminal.

[0199] Otherwise, the LPS hosted by the OSNPN and/or OSP may obtain subscription data owned by the at least one other SNPN and/or SP from the CPS and the LPS hosted by the OSNPN and/or OSP may provide the subscription data for the terminal to the terminal. The terminal may then register using the subscription data (e.g. SNPN and/or SP ID) received from the LPS hosted by the OSNPN and/or OSP.

[0200] FIG. 4 shows a schematic representation of a signalling diagram of a process for providing subscription data to a terminal.

[0201] In step 1, the terminal may be pre-configured with a default credential. The default credential may comprise a permanent equipment identifier (PEI).

[0202] In step 2, the terminal may perform initial access with the OSNPN and/or OSP.

[0203] In step 3, the terminal may use the default credential to authenticate with the DCS.

[0204] In step 4, the terminal may establish a configuration PDU session with the OSNPN and/or OSP.

[0205] In step 5, if the OSNPN and/or OSP owns subscription data for the terminal (i.e. the OSNPN and/or OSP is a home SNPN and/or home SPN), the LPS hosted by the OSNPN and/or OSP may provide the subscription data for the terminal to the terminal.

[0206] In step 6, if the OSNPN and/or OSP does not own subscription data for the terminal (i.e. the OSNPN and/or OSP is different from a home SNPN and/or home SPN), the LPS hosted by the OSNPN and/or OSP may send a query to obtain subscription data for the terminal own by another SNPN and/or SP from the CPS. The LPS hosted by the OSNPN and/or OSP may provide the subscription data for the terminal to the terminal.

[0207] One or more aspect of this disclosure relate to a LPS. A LPS may be one of the the network nodes of a SNPN and/or SP. A CPS address may be configured at the LPS. A terminal manufacturer or SNPN and/or SP subscription owner may configure the LPS hosted by the SNPN and/or SP with subscriber data for terminals.

[0208] The LPS may be configured with the SNPN ID and/or SP ID (e.g. S-NPN1 and/or SP1) along with RG ID (e.g.RG1) for all the terminals for which the SNPN and/or SP owns subscription data. The RG ID may be based on a roaming agreement between SNPNs/SPs. The LPS may also store configuration parameters (e.g. PDU session parameters, such as SNSSAI, DNN, URSPs, QoS rules, and other required parameters to access the SNPN and establish a regular PDU session) for all the terminals for which the SNPN and/or SP owns subscription data.

[0209] PEI may be assumed to be the default credential present in a terminal and so used as key to obtain subscription data. After configuration is done successfully at the LPS of the SNPN and/or SP, the LPS may provide the subscription data to the CPS.

TABLE-US-00001 Terminal LPS (S-NPN1/SP1) CPS PEI1 PEI1: S-NPN1/SP1, RG1, terminal PEI1: S-NPN1/SP1, RG1, terminal configuration parameter (configuration parameter

[0210] Subsequently, another terminal manufacturer or another SNPN and/or SP subscription owner (S-NPN2/SP2) may configure another LPS hosted by the other SNPN and/or SP with subscriber data for other terminals.

[0211] The LPS may be configured with another SNPN ID and/or SP ID (e.g. S-NPN2 and/or SP2) along with another RG ID (e.g.RG2) for all the terminals for which the SNPN and/or SP owns subscription data. The RG ID may be based on a roaming agreement between SNPNs/SPs. The LPS may also store configuration parameters (e.g. PDU session parameters, such as SNSSAI, DNN, URSPs, QoS rules, and other required parameters to access the SNPN and establish a regular PDU session) for all the terminals for which the SNPN and/or SP owns subscription data.

TABLE-US-00002 Terminal LPS (S-NPN2/SP2) CPS1 PEI2 PEI2: S-NPN2/SP2, RG2, terminal PEI1: S-NPN1/SP1, RG1, terminal configuration parameter configuration parameter PEI2: S-NPN2/SP2, RG2, terminal configuration parameter

[0212] It will be understood that when the LPS is subsequently configured (like providing subscription data for another terminal or modifying subscription data for a terminal) then the LPS may provide the whole content or the delta content to the CPS

[0213] Whenever a terminal attaches to the SNPN and/or SP hosting the LPS, the terminal may be provided with subscription data for the terminal from the LPS if the SNPN owns subscription data for the terminal (i.e. if the LPS is configured with subscription data for the terminal). If the SNPN does not owns subscription data for the terminal (i.e. if the LPS is not configured with subscription data for the terminal), the LPS may query subscription data for the terminal owned by another SNPN and/SP from the CPS and then provides the subscription data for the terminal to the terminal.

[0214] One or more aspect of this disclosure relate to a CPS. The CPS may receive subscription data for terminals from several LPS. The CPS may be updated upon receiving subscription data for a new terminal or receiving a modification to subscription data for an existing terminal. The CPS may provide subscription data for a terminal to a LPS upon receiving a query from the LPS to obtain the subscription data for the terminal.

TABLE-US-00003 CPS PEI1: S-NPN1/SP1, RG1, terminal configuration parameter PEI2: S-NPN2/SP2, RG2, terminal configuration parameter

[0215] Three scenarios may be contemplated. In these three scenarios UE1 is pre-configured with default credential PEI 1, UE2 is pre-configured with default credential PEI2. SNPN1 and/or SP1 operates as an OSNPN and/or OSP.

[0216] In a first scenario, SNPN1 and/or SP1 owns subscriber data for the UE1. That is, SNPN1 and/or SP1 is nota home SNPN and/or SP for the UE1.

[0217] UE1 with default credential PEI1 may perform initial access with S-NPN1 and/or SP1 and may register with SNPN1 and/or SP1. LPS hosted by the S-NPN1/SP1 may provide subscription data for UE1 to UE1 (PEI1: S-NPN1/SP1, RG1, UE1 configuration parameter).

[0218] The initial access with S-NPN1 and/or SP1 is performed with default credential PEI1. Hence, UE1 may only get onboarding service (i.e. UE1 is provided with subscription data for UE1). After the onboarding procedure is completed, UE1 may deregister from S-NPN1 and/or SP1 and again register to SNPN1 and/or SP1 using the SNPN1 ID and/or SP1 ID to get normal service (as opposed to onboarding service). The normal service may be used to perform video calls, voice calls or transfer data.

[0219] In a second scenario, SNPN1 and/or SP1 does not own subscriber data for UE2. That is, SNPN1 and/or SP1 is not a home SNPN and/or SP for UE2. SNPN2 and/or SP2 owns subscriber data for UE2 and is available.

[0220] UE2 with default credential PEI2 may perform initial access with SNPN1 and/or SP1 and may register with SNPN1 and/or SP1. LPS hosted by the S-NPN1/SP1 may query CPS to obtain subscription data for UE2 (PEI2: S-NPN2/SP2, RG2, UE2 configuration parameter). LPS hosted by the S-NPN1/SP1 may provide subscription data for UE2 to UE2.

[0221] The initial access with S-NPN1 and/or SP1 is performed with default credential PEI2. Hence, UE2 may only get onboarding service (i.e. UE2 is provided with subscription data for UE2). After the onboarding procedure is completed, UE2 may deregister from S-NPN1 and/or SP1. UE2 may try to discover cells broadcasting SNPN2 ID and/or SP2 ID. Upon discovering a cell broadcasting SNPN2 ID and/or SP2 ID, UE2 may register with SNPN2 and/or SP2 via the cell to get normal service (as oppose to onboarding service).

[0222] In a third scenario, SNPN1 and/or SP1 does not own subscriber data for UE2. That is, SNPN1 and/or SP1 is not a home SNPN and/or SP for UE2. SNPN2 and/or SP2 owns subscriber data for UE2 and is not available.

[0223] UE2 with default credential PEI2 may perform initial access with SNPN1 and/or SP1 and may register with SNPN1 and/or SP1. LPS hosted by the S-NPN1/SP1 may query CPS to obtain subscription data for UE2 (PEI2: S-NPN2/SP2, RG2, UE2 configuration parameter). LPS hosted by the S-NPN1/SP1 may provide subscription data for UE2 to UE2.

[0224] The initial access with S-NPN1 and/or SP1 is performed with default credential PEI2. Hence, UE2 may only get onboarding service (i.e. UE2 is provided with subscription data for UE2). After the onboarding procedure is completed, UE2 may deregister from S-NPN1 and/or SP1. UE2 may try to discover cells broadcasting SNPN2 ID and/or SP2 ID. Upon not discovering any cell broadcasting SNPN2 ID and/or SP2 ID, UE2 discover cells broadcasting RG2 ID. Such cell These cells may belong to a SNPN and/or SPs which is part of RG2. Upon discovering a cell broadcasting RG2 ID, UE2 may register with SNPN2 and/or SP2 via the cell to get normal service (as oppose to onboarding service).

[0225] It will be understood that initial access to OSNPN cells, authentication by DCS and getting provisioning server address as part of configuration PDU session may be performed as per TS 23.700-07.

[0226] One or more aspect of this disclosure may provide several advantages.

[0227] Using a LPS may help a OSNPN and/or OSP to onboard a terminal when the OSNPN and/or OSPN owns subscription data for the terminal (i.e. when the OSNPN and/or SPN is a home SNPN and/or SP).

[0228] Using a remote CPS may help a OSNPN to onboard a terminal when the OSNPN does not own subscription data for the terminal (i.e. when the OSNPN and/or SPN is different from a home SNPN and/or SP).

[0229] Also, using remote CPS may allow to provide normal service (as oppose to onboarding service) using RG ID in the area where the home SNPN and/or SP is not available.

[0230] FIG. 5 shows a schematic representation of block diagram of a method performed by a LPS for providing subscription data to a terminal. The LPS may be different from a DCS.

[0231] In step 500 a LPS may determine whether an OSNPN and/or OSP hosting the LPS owns subscription data for a terminal, in response to the terminal performing initial access to the OSNPN and/or OSP. The LPS may be different from a DCS.

[0232] In step 502 the LPS may provide subscription data for the terminal to the terminal based on whether the OSNPN and/or OSP hosting the LPS owns subscription data for the terminal.

[0233] In an example, the LPS may determine that the OSNPN and/or OSP hosting the LPS owns subscription data for the terminal. The LPS may then provide the subscription data for the terminal.

[0234] In another example, the LPS may determine that the OSNPN and/or OSP hosting the LPS does not own subscription data for the terminal. The LPS may obtain subscription data owned by another SNPN and/or SP for the terminal from a CPS. The LPS may then provide the subscription data owned by the other SNPN and/or SP for the terminal to the terminal. The CPS may be hosted outside the OSNPN and/or OSP. The OSNPN and/or OSP and the other SNPN and/or SP may be part of a same RG. The OSNPN and/or OSP and the other SNPN and/or SP may be part of different RGs.

[0235] The CPS may is hosted outside the OSNPN and/or OSP and outside the other SNPN and/or SP.

[0236] The CPS may be administered by the OSNPN and/or OSP and the other SNPN and/or SP.

[0237] The LPS may store subscription data for at least one terminal owned by the onboarding standalone non private network The LPS may provide the subscription data for the at least one terminal owned by the OSNPN and/or OSP to the CPS.

[0238] The subscription data for the terminal may comprises at least one of: a SNPN ID, a SP ID, a RG ID or a parameter to establish a PDU session.

[0239] The parameter to establish a PDU session may comprise at least one of: SNSSAI, a DNN, a URSP or a QoS rule.

[0240] FIG. 6 shows a schematic representation of block diagram of a method performed by a CPS for providing subscription data to a terminal.

[0241] In step 600 a CPS may receive a query to obtain subscription data owned by a SNPN and/or SP for a terminal from a LPS hosted by an OSNPN and/or OSP.

[0242] In step 602 the CPS may provide the subscription data owned by the SNPN and/or SP for the terminal to the LPS.

[0243] The CPS may be hosted outside the SNPN and/or SP and outside the OSNPN and/or OSP.

[0244] The CPS may be administered by the SNPN and/or SP and the OSNPN and/or OSP.

[0245] The CPS may receive subscription data owned by the SNPN and/or SP for the terminal from a LPS hosted by the SNPN and/or SP. The CPS may store the subscription data owned by the SNPN and/or SP for the terminal.

[0246] The CPS may receive subscription data owned by the OSNPN and/or OSP from the LPS hosted by an OSNPN and/or OSP. The CPS may store the subscription data owned by the OSNPN and/or OSP for the terminal.

[0247] The CPS may receive subscription data owned by at least one other OSNPN and/or OSP from an LPS hosted by the at least one other OSNPN and/or OSP. The CPS may store the subscription data owned by the at least one other OSNPN and/or OSP for the terminal.

[0248] FIG. 7 shows a schematic representation of block diagram of a method performed by a terminal for being provided subscription data.

[0249] In step 700 the terminal may receive subscription data for the terminal from a LPS hosted by an OSNPN and/or OSP, in response to the terminal performing an initial access to the OSNPN and/or OSP. The LPS may be different from a DCS.

[0250] In step 702 the terminal may use the subscription data for the terminal.

[0251] In an example, the subscription data for the terminal may be owned by the OSNPN and/or OSP. The terminal may use the subscription data for the terminal to access the OSNPN and/or OSP.

[0252] In another example, the subscription data for the terminal may be owned by another SNPN and/or SP. The terminal may use the subscription data for the terminal to access the other SNPN and/or SP.

[0253] In another example, the subscription data for the terminal may be owned by a first other SNPN and/or SP. The terminal may using the subscription data for the terminal to access a second other SNPN and/or SP part of a same RG as the first other SNPN and/or SP.

[0254] FIG. 8 shows a schematic representation of non-volatile memory media 800a (e.g. computer disc (CD) or digital versatile disc (DVD)) and 800b (e.g. universal serial bus (USB) memory stick) storing instructions and/or parameters 802 which when executed by a processor allow the processor to perform one or more of the steps of the methods of FIGS. 5 to 7.

[0255] It will be understood that although the above concepts have been discussed in the context of a 5GS, one or more of these concepts may be applied to other cellular systems.

[0256] The embodiments may thus vary within the scope of the attached claims. In general, some embodiments may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. For example, some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device, although embodiments are not limited thereto. While various embodiments may be illustrated and described as block diagrams, flow charts, or using some other pictorial representation, it is well understood that these blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.

[0257] The embodiments may be implemented by computer software stored in a memory and executable by at least one data processor of the involved entities or by hardware, or by a combination of software and hardware. Further in this regard it should be noted that any procedures, e.g., as in FIGS. 5 to 7, may represent program steps, or interconnected logic circuits, blocks and functions, or a combination of program steps and logic circuits, blocks and functions. The software may be stored on such physical media as memory chips, or memory blocks implemented within the processor, magnetic media such as hard disk or floppy disks, and optical media such as for example DVD and the data variants thereof, CD.

[0258] The memory may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory. The data processors may be of any type suitable to the local technical environment, and may include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs), application specific integrated circuits (ASIC), gate level circuits and processors based on multi-core processor architecture, as non-limiting examples.

[0259] Alternatively or additionally some embodiments may be implemented using circuitry. The circuitry may be configured to perform one or more of the functions and/or method steps previously described. That circuitry may be provided in the base station and/or in the communications device.

[0260] As used in this application, the term “circuitry” may refer to one or more or all of the following: [0261] (a) hardware-only circuit implementations (such as implementations in only analogue and/or digital circuitry); [0262] (b) combinations of hardware circuits and software, such as: [0263] (i) a combination of analogue and/or digital hardware circuit(s) with software/firmware and [0264] (ii) any portions of hardware processor(s) with software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as the communications device or base station to perform the various functions previously described; and [0265] (c) hardware circuit(s) and or processor(s), such as a microprocessor(s) or a portion of a microprocessor(s), that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation.

[0266] This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and/or firmware. The term circuitry also covers, for example integrated device.

[0267] The foregoing description has provided by way of exemplary and non-limiting examples a full and informative description of some embodiments However, various modifications and adaptations may become apparent to those skilled in the relevant arts in view of the foregoing description, when read in conjunction with the accompanying drawings and the appended claims. However, all such and similar modifications of the teachings will still fall within the scope as defined in the appended claims.