WO2023186902A1

WO2023186902A1 - Broker network for localized services

Info

Publication number: WO2023186902A1
Application number: PCT/EP2023/058013
Authority: WO
Inventors: Jinyao CAO; David Castellanos Zamora; Peter Hedman; Paul Schliwa-Bertling; Mai-Anh Phan; Divya PEDDIREDDY
Original assignee: Telefonaktiebolaget Lm Ericsson (Publ)
Priority date: 2022-03-28
Filing date: 2023-03-28
Publication date: 2023-10-05

Abstract

Disclosed is a method performed by a wireless device for accessing localized services, the method comprising one or more of: receiving an indication that a broker function is supported in the network; obtaining a set of service parameters of localized service, including broker network IDs; selecting one or more specific hosting networks to access the desired localized service, or one or more specific localized services; requesting Provisioning Server, PVS, associated with the selected hosting networks or the selected localized services; receiving PVS address associated with the selected hosting network; receiving credentials to be used to access the hosting network that provides access to the localized service; receiving a redirection to the selected hosting network, based on trigger from wireless device; differentiating the request of PVS by indicating the selected hosting network or the selected localized service, either via "Protocol Data Unit, PDU, Session Establishment Request message'', or "Uplink, UL, Non-Access Stratum, NAS, Transport message'', or via Domain Name System, DNS, queries with Full Qualified Domain Name, FQDN, constructed by the wireless device; accessing the hosting network for localized services, using the received credentials.

Description

Applicant’s Ref. P104833W001

2023-03-27

1

BROKER NETWORK FOR LOCALIZED SERVICES

BACKGROUND

Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and/or is implied from the context in which it is used. All references to a/an/the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and/or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features, and advantages of the enclosed embodiments will be apparent from the following description.

3GPP is currently standardizing solutions for requirements associated to localized services, as known as Providing Access to Localized Services (PALS), which is studied by SA1 and described in 3GPP TR 22.844. The requirements are included in the 3GPP TS 22.261 (clause 6.41) 5G Service requirement specification.

Figure 1

An example of using PALS is described in Figure 1. Figure 1 illustrates an example of a hosting network providing services at an arena.

• 3^rd party service provider is the entity offering services to end user. The services are normally restricted in time and geographically.

• 3^rd party service provider negotiates a service level agreement with the hosting network.

• The hosting network (which can be either a regular PLMN, or a non-public network) is responsible for delivering localized services to the UE regardless of whether the UE has prior relationship with the hosting network or not.

• The UE may originally have a subscription from its home network and registered in a 3GPP network by using its home network subscription. SUMMARY

There currently exist certain challenge(s). As described herein, UE may not have any prior relationship with the hosting network. Then for the UE to be able to access the hosting network, there are a few options:

1. UE has a regular network credential (e.g., a credential from a PLMN operator).

The network owning the credential is the home network of the UE. In this scenario, it requires business agreement between hosting network and the home network, and also requires interfaces between the two networks. So that the UE can reuse this regular network credential from home network to access the hosting network, via existing features in 3GPP (e.g., roaming architecture defined in 3GPP TS 23.501 clause 4.2.4; access an SNPN using Credentials Holder defined in 3GPP TS 23.501 clause 5.30.2.9)

2. UE has a regular network credential, but the regular network credential cannot be used to access hosting network.

Then, UE can perform onboarding and remote provisioning procedure and obtain credential/subscription of the hosting network, as defined in 3GPP TS 23.501 clause 5.30.2.10

In some cases, the UE is required to be pre-configured with certain information (e.g., "Default UE credential", "ON-SNPN selection information" as described in 3GPP TS 23.501 clause 5.30.2.10.2.4).

In other cases, UE can utilize the regular network credential to perform User Plane remote provisioning in a network which the UE can access by using this regular network credential.

3. UE does not have any regular network credentials.

In option 1, it is technically possible for one hosting network to establish business agreements with many other home networks and the corresponding interfaces. But, according to the use cases studied in 3GPP TR 22.844, the hosting network usually is assumed to be small which covers limited geographic area and even a temporary network which is commissioned during the time period of the localized services and decommissioned when the localized services are over. So, in practice it may not be feasible for a hosting network to establish interfaces with home networks.

In option 2, if pre-configuration on UE is necessary, then it deviates from the SA1 requirement that the localized service and the hosting network shall be accessed in an efficient and convenient way from end user point of view.

Some embodiments of the current disclosure cover the solution for option 1 and 2.

Certain aspects of the present disclosure and their embodiments may provide solutions to the aforementioned or other challenges. Some embodiments propose a solution to use an intermediate network to address the problem listed above. This intermediate network later on in this current disclosure is referred to as a "broker network”. In some embodiments, the broker network has one or more of the following characteristics: Broker network is a network that maintains conventional business relation with other home networks operators (e.g., PLMN operator), and establishes interfaces with home networks. Broker network is a partner network of the hosting networks which are deployed in the same region or same country. So, the hosting network can have easy or direct contact with the broker network. Broker network is a role and any network (e.g., a PLMN) can take this role. Broker network is responsible for provisioning UE with the credentials to be used to access hosting network that provides access to the localized service. In some embodiments, the broker network can be referred to as e.g., "a network enabling access to hosting networks for localized services.”

Some embodiments of the present disclosure propose enhanced remote provisioning solution in a broker network.

Network to indicate to the UE that the broker function (or remote provisioning function) is supported in the network. Existing SIB is that onboarding is enabled, and this might be reused. In some embodiments, onboarding includes a step for remote provisioning.

UE differentiates the request of Provisioning Server (PVS) by indicating the selected hosting network or the selected localized service, either via "PDU Session Establishment Request message”, or "UL NAS Transport message”, or via Domain Name System (DNS) queries with Full Qualified Domain Name (FQDN) constructed by the UE.

Network is configured with hosting network/localized service mapping table with PVS, and provides extra information associated with the PVS FQDN/IP provided to UE.

There are, proposed herein, various embodiments which address one or more of the issues disclosed herein. In some embodiments, a method performed by a wireless device for accessing localized services includes one or more of: receiving an indication that the broker function (or remote provisioning function) is supported in the network; obtaining a set of service parameters of localized service, including broker network IDs; selecting one or more specific hosting networks to access the desired localized service, or one or more specific localized service; requesting PVS associated with the selected hosting networks; receiving PVS address associated with the selected hosting network or the selected localized services; receiving credentials to be used to access the hosting network that provides access to the localized service; receiving a redirection to the selected hosting network, based on trigger from wireless device; differentiating the request of PVS by indicating the selected hosting network or the selected localized service, either via "Protocol Data Unit (PDU) Session Establishment Request message”, or "Uplink (UL) Non-Access Stratum (NAS) Transport message”, or via Domain Name System, DNS, queries with Full Qualified Domain Name, FQDN, constructed by the wireless device; and accessing the hosting network for localized services, using the received credentials.

In some embodiments, receiving the indication that the broker function (or remote provisioning function) is supported in the network comprises receiving a (R)AN broadcast of an indication bit of supporting broker function. In some embodiments, receiving the indication that the broker function (or remote provisioning function) is supported in the network comprises receiving in a Registration Accept message that the network supports broker function.

In some embodiments, the broker network is a network that maintains conventional business relation with other home networks operators (e.g., Public Land Mobile Network (PLMN) operator), and establishes interfaces with home networks.

In some embodiments, the broker network is a partner network of the hosting networks which are deployed in the same region or same country.

In some embodiments, the serving network is a home network or can be a network which has relationship with a home network.

Certain embodiments may provide one or more of the following technical advantage(s). Some embodiments of the current disclosure enable easy/fast deployment of a hosting network. The credential to be used for accessing a hosting network is anchored in the broker network.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated herein and form part of the specification, illustrate various embodiments.

Figure 1 illustrates an example of a hosting network providing services at an arena;

Figure 2 illustrates a deployment of a broker network, according to some embodiments of the current disclosure;

Figure 3 illustrates an enhanced remote provisioning procedure in broker network;

Figure 4 illustrates an enhanced remote provisioning via DNS in broker network;

Figure 5 illustrates one example of a cellular communications system 500 in which embodiments of the present disclosure may be implemented;

Figure 6 illustrates a wireless communication system represented as a 5G network architecture composed of core Network Functions (NFs);

Figure 7 illustrates a 5G network architecture using service-based interfaces between the NFs in the CP;

Figure 8 is a schematic block diagram of a radio access node 800 according to some embodiments of the present disclosure;

Figure 9 is a schematic block diagram that illustrates a virtualized embodiment of the radio access node 800 according to some embodiments of the present disclosure;

Figure 10 is a schematic block diagram of the radio access node 800 according to some other embodiments of the present disclosure; Figure 11 is a schematic block diagram of a wireless communication device 1100 according to some embodiments of the present disclosure;

Figure 12 is a schematic block diagram of the wireless communication device 1100 according to some other embodiments of the present disclosure;

Figure 13 is an embodiment of a communication system includes a telecommunication network in accordance with an embodiment of the present disclosure;

Figure 14 is an example implementation, in accordance with an embodiment, of a UE, base station, and a host computer;

Figure 15 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment;

Figure 16 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment;

Figure 17 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment;

Figure 18 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.

DETAILED DESCRIPTION

Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the subject matter disclosed herein, the disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

Radio Node: As used herein, a "radio node” is either a radio access node or a wireless communication device.

Radio Access Node: As used herein, a "radio access node” or "radio network node” or "radio access network node” is any node in a Radio Access Network (RAN) of a cellular communications network that operates to wirelessly transmit and/or receive signals. Some examples of a radio access node include, but are not limited to, a base station (e.g., a New Radio (NR) base station (gNB) in a Third Generation Partnership Project (3GPP) Fifth Generation (5G) NR network or an enhanced or evolved Node B (eNB) in a 3GPP Long Term Evolution (LTE) network), a high-power or macro base station, a low-power base station (e.g., a micro base station, a pico base station, a home eNB, or the like), a relay node, a network node that implements part of the functionality of a base station (e.g., a network node that implements a gNB Central Unit (gNB-CU) or a network node that implements a gNB Distributed Unit (gNB-DU)) or a network node that implements part of the functionality of some other type of radio access node.

Core Network Node: As used herein, a "core network node” is any type of node in a core network or any node that implements a core network function. Some examples of a core network node include, e.g., a Mobility Management Entity (MME), a Packet Data Network Gateway (P-GW), a Service Capability Exposure Function (SCEF), a Home Subscriber Server (HSS), or the like. Some other examples of a core network node include a node implementing an Access and Mobility Management Function (AMF), a User Plane Function (UPF), a Session Management Function (SMF), an Authentication Server Function (AUSF), a Network Slice Selection Function (NSSF), a Network Exposure Function (NEF), a Network Function (NF) Repository Function (NRF), a Policy Control Function (PCF), a Unified Data Management (UDM), or the like.

Communication Device: As used herein, a "communication device” is any type of device that has access to an access network. Some examples of a communication device include, but are not limited to: mobile phone, smart phone, sensor device, meter, vehicle, household appliance, medical appliance, media player, camera, or any type of consumer electronic, for instance, but not limited to, a television, radio, lighting arrangement, tablet computer, laptop, or Personal Computer (PC). The communication device may be a portable, hand-held, computer-comprised, or vehicle-mounted mobile device, enabled to communicate voice and/or data via a wireless or wireline connection.

Wireless Communication Device: One type of communication device is a wireless communication device, which may be any type of wireless device that has access to (i.e. , is served by) a wireless network (e.g., a cellular network). Some examples of a wireless communication device include but are not limited to: a User Equipment device (UE) in a 3GPP network, a Machine Type Communication (MTC) device, and an Internet of Things (loT) device. Such wireless communication devices may be, or may be integrated into, a mobile phone, smart phone, sensor device, meter, vehicle, household appliance, medical appliance, media player, camera, or any type of consumer electronic, for instance, but not limited to, a television, radio, lighting arrangement, tablet computer, laptop, or PC. The wireless communication device may be a portable, hand-held, computer-comprised, or vehicle-mounted mobile device, enabled to communicate voice and/or data via a wireless connection.

Network Node: As used herein, a "network node” is any node that is either part of the RAN or the core network of a cellular communications network/system.

Transmission/Reception Point (TRP): In some embodiments, a TRP may be either a network node, a radio head, a spatial relation, or a Transmission Configuration Indicator (TCI) state. A TRP may be represented by a spatial relation or a TCI state in some embodiments. In some embodiments, a TRP may be using multiple TCI states. In some embodiments, a TRP may a part of the gNB transmitting and receiving radio signals to/from UE according to physical layer properties and parameters inherent to that element. In some embodiments, in Multiple TRP (multi-TRP) operation, a serving cell can schedule UE from two TRPs, providing better Physical Downlink Shared Channel (PDSCH) coverage, reliability and/or data rates. There are two different operation modes for multi-TRP: single Downlink Control Information (DCI) and multi-DCI. For both modes, control of uplink and downlink operation is done by both physical layer and Medium Access Control (MAC). In single-DCI mode, UE is scheduled by the same DCI for both TRPs and in multi-DCI mode, UE is scheduled by independent DCIs from each TRP.

In some embodiments, a set Transmission Points (TPs) is a set of geographically co-located transmit antennas (e.g., an antenna array (with one or more antenna elements)) for one cell, part of one cell or one Positioning Reference Signal (PRS) -only TP. TPs can include base station (eNB) antennas, Remote Radio Heads (RRHs), a remote antenna of a base station, an antenna of a PRS-only TP, etc. One cell can be formed by one or multiple TPs. For a homogeneous deployment, each TP may correspond to one cell.

In some embodiments, a set of TRPs is a set of geographically co-located antennas (e.g., an antenna array (with one or more antenna elements)) supporting TP and/or Reception Point (RP) functionality.

Note that the description given herein focuses on a 3GPP cellular communications system and, as such, 3GPP terminology or terminology similar to 3GPP terminology is oftentimes used. However, the concepts disclosed herein are not limited to a 3GPP system.

Note that, in the description herein, reference may be made to the term "cell”; however, particularly with respect to 5G NR concepts, beams may be used instead of cells and, as such, it is important to note that the concepts described herein are equally applicable to both cells and beams.

Figure 2

Figure 2 illustrates a deployment of a broker network, according to some embodiments of the current disclosure. As described in clause 2, the broker network depicted in Figure 2 establishes interfaces with home networks, on behalf of the hosting network to authenticate UE which has regular network credential. The current serving network can provision UE with service parameters related to the localized service, as described in a previous disclosure, including information related to broker network. Then the UE selects and registers in broker network to obtain credential to be used to access the hosting network for localized service.

Note that the serving network in the Figure 2 can be a home network or can be a network which has relationship with a home network.

The UE is assumed to have regular network credential from an operator (e.g., a PLMN operator). But this regular network credential cannot be used directly to access hosting networks due to the reasons described herein (e.g., hosting network is not capable of establishing interfaces with home networks).

Then, the broker network can be seen as an intermediate network that authenticates the UE and provisions the UE with the credential to be used for accessing hosting network. Figure 3

Figure 3 illustrates an enhanced remote provisioning procedure in broker network.

0. (Optional) UE is provisioned with service parameters of localized service, as described in a previous disclosure in serving network. The service parameter includes a combination of localized service, the hosting networks that can provide access to such localized service, associated quality/charging cost etc. of the hosting network.

In some embodiments of the current disclosure, the provisioned information described in a previous disclosure also contains identifiers of the potential broker networks. UE uses this information to select and find a broker network to obtain credentials to access hosting networks.

1 . There are two options to inform UE that the broker function is supported by the network. One embodiment of the current disclosure is shown in this step that (R)AN broadcasts an indication bit of supporting broker function (Option a).

2. Another option of the current disclosure is to inform UE in Registration Accept message (see 3GPP TS 24.501) that the network supports broker function (Option b).

The broker function indication in step 1 and step 2 can also be represented by different names, e.g., remote provisioning function indication.

The purpose of this indication in both Option a and b is to inform UE that the current network is able to provision UE with credentials for accessing hosting network of localized service.

During the registration procedure, the primary authentication is performed between UE/broker network/home network, by using the regular network credential from the UE's home network. Then, the connection between UE and broker network is secured.

In some embodiments of the current disclosure, the broker network can indicate to the home network the UE is registered for obtaining credentials from a broker network and request the home network to authorize. If the UE can access broker network with credentials from Service Provider (SP), then the SP may authorize the access. 2a. (Optional)

This step is an alternative step for step 0. Step 0 will happen if the serving network is different than the broker network. But if the serving network and the broker network are the same, then the provisioning of service parameters of localized service to UE can be done in broker network as shown in this step 2a.

3. Based on the service parameters of the localized service received in step 0 or step 2a, end user/UE make a selection of one or more specific hosting network(s) to access the desired localized service, or one or more specific localized service(s).

4. Because the UE was informed by the network there is broker function (or remote provisioning function) supported in this network in step 1 or step 2, the UE initiates a User Plane remote provisioning procedure with the broker network to obtain the credential of the selected hosting network/localized service.

The UE requests FQDN or IP address of PVS from the broker network.

It some embodiments of the current disclosure, such request from UE is sent together with one or more identifier(s) of the selected hosting network(s), and/or one or more identifier(s) of the selected localized service(s). The UE's request is either included as a. a separated Information Element (IE) in the UL NAS Transport message or b. included in PDU Session Establishment Request message. PDU Session Establishment Request message is included as payload container in the UL NAS Transport message. The payload container in UL NAS Transport message is transparent to AMF.

So, if the UE's request is included in a separate IE in UL NAS Transport message (a), such request is handled by AMF, and AMF can select specific SMF for enabling remote provisioning based on the request.

If the UE's request is included in payload container (i.e., PDU Session Establishment Request), then such request is handled by SMF (b). The SMF of the broker network accepts the PDU Session.

In some embodiments of the current disclosure, it depends on which NF handles the UE's request in step 4, AMF or SMF is locally configured with mapping table between [PVS information] and [hosting network identifier], or a mapping table between [PVS information] and [localized service identifier]. So, AMF/SMF can, based on the UE's request, return the corresponding PVS information back to the UE. In some embodiments, the [PVS information] includes: PVS FQDN or IP address + credential type + hosting network ID.

In some embodiments of the current disclosure, if the UE's request is handled by AMF, the response is included in a separated IE in DL NAS Transport message. If the UE's request is handled by SMF, the response is included in PDU Session Establishment Accept message.

In some embodiments of the current disclosure, the PVS information in the response to UE includes not only FQDN/IP address of the PVS, but also extra information associated with the FQDN/IP address The extra information associated with the PVS's FQDN/IP can include followings:

The type of the credential: o Native credential. In this case, the credential is native to the selected hosting network, and the UE can use this credential to access hosting network directly via normal registration procedure as specified in 3GPP TS 23.502 clause 4.2.2.2.2. o Onboarding credential. In this case, this credential is handled as "Default UE credential" from hosting network point of view. The broker network owns the credential and acts as "Default Credential Server (DCS)" for the hosting network, as specified in TS 23.501 clause 5.30.2.10.2. The UE can use this credential to perform onboard registration in the hosting network, as specified in 3GPP TS 23.502 clause 4.2.2.2.4. o Credentials Holder (CH) credential. In this case, this credential is also owned by the broker network. The broker network acts as CH for the hosting network, as specified in 3GPP TS 23.501 clause 5.30.2.9. The UE can use this credential to access hosting network via normal registration procedure, as specified in 3GPP TS 23.502 clause 4.2.2.2.2.

The identifiers of the hosting networks. The UE is then made aware of for which hosting networks this PVS can be used for credential provisioning. Such identifiers of the hosting network are needed, especially when UE has not specified the identifier of the hosting network but only the identifier of localized service in step 4. 6. UE connects to PVS for remote provisioning using the User Plane established in the broker network.

7. The UE initiates the de-registration procedure. If the selected localized service(s) are about to start (or have started), the UE needs to select the hosting network.

In some embodiments of the current disclosure, one or more of the following can be used for UE to trigger the redirection to hosting network:

I. The UE includes in the de-registration request the identifier of the selected hosting network for accessing a localized service, in case there are PVS information of multiple hosting networks requested and received by UE in previous step 4 and 5; or ii. The UE indicates in the de-registration request message with cause "redirection is requested”, in case in step 4 only single hosting network identifier is requested by UE and the request is handled by AMF (case a); or ill. The UE does not need to indicate anything explicitly in the de-registration request, but the AMF is aware of the selected localized service and selected hosting network in step 4 (case a), if the AMF has knowledge about localized service start (e.g., by querying service parameter with UDR as described in a previous disclosure), it can assist the UE to find the hosting network.

After de-registration confirm, the AMF informs the NG-RAN via NGAP about the selected hosting network ID, e.g., as new IE in the UE CONTEXT RELEASE COMMAND for that UE. If the NG-RAN is aware of neighboring cells within the UE's selected hosting network ID, the NG-RAN assists the UE in finding the hosting network by sending an RRC release with redirect message (frequency and optionally cell information) or RRC release with multiple frequencies to the UE.

If the UE does not receive any redirect information in the RRC release message, the UE performs cell/network search to find/select the hosting network.

In case the AMF or SMF in broker network does not provide PVS information to the UE, the UE can construct FQDNs to query with the DNS server in broker network, to obtain PVS address.

Figure 4

Figure 4 illustrates an enhanced remote provisioning via DNS in broker network. The steps in Figure 4 are the same as Figure 3, except the following:

5. AMF/SMF does not provide the PVS information to UE during the PDU Session Establishment procedure. But as usual, there is DNS server address provided to UE by SMF. The DNS server is administrated by the broker network.

5a. UE performs DNS query to obtain PVS information. Due to no PVS information from AMF/SMF received and the network has informed UE that there is broker function (or remote provisioning function) supported in step 1 or step 2, the UE constructs FQDN to query the PVS address.

In some embodiments of the current disclosure, the constructed FQDN can include the identifier of the selected hosting network or identifier of the selected localized service. The DNS server will return a response with the IP address of the Provisioning Server (PVS) associated with the selected hosting network. If UE's request is based on the identifier of the selected localized service, the DNS response can include a list of hosting networks which can provide access to the selected localized service. After UE receives such response, it selects a hosting network, and queries DNS server ask for IP address of the PVS associated with the selected hosting network.

6. UE connects to the PVS to obtain credential, and optionally other information (e.g., hosting network id in case that has not been received before) to be used for accessing the selected hosting network.

Figure 5

Figure 5 illustrates one example of a cellular communications system 500 in which embodiments of the present disclosure may be implemented. In the embodiments described herein, the cellular communications system 500 is a 5G system (5GS) including a Next Generation RAN (NG-RAN) and a 5G Core (5GC). In this example, the RAN includes base stations 502-1 and 502-2, which in the 5GS include NR base stations (gNBs) and optionally next generation eNBs (ng-eNBs) (e.g., LTE RAN nodes connected to the 5GC), controlling corresponding (macro) cells 504-1 and 504-2. The base stations 502-1 and 502-2 are generally referred to herein collectively as base stations 502 and individually as base station 502. Likewise, the (macro) cells 504-1 and 504-2 are generally referred to herein collectively as (macro) cells 504 and individually as (macro) cell 504. The RAN may also include a number of low power nodes 506-1 through 506-4 controlling corresponding small cells 508-1 through 508-4. The low power nodes 506-1 through 506-4 can be small base stations (such as pico or femto base stations) or RRHs, or the like. Notably, while not illustrated, one or more of the small cells 508-1 through 508-4 may alternatively be provided by the base stations 502. The low power nodes 506-1 through 506-4 are generally referred to herein collectively as low power nodes 506 and individually as low power node 506. Likewise, the small cells 508-1 through 508-4 are generally referred to herein collectively as small cells 508 and individually as small cell 508. The cellular communications system 500 also includes a core network 510, which in the 5G System (5GS) is referred to as the 5GC. The base stations 502 (and optionally the low power nodes 506) are connected to the core network 510.

The base stations 502 and the low power nodes 506 provide service to wireless communication devices 512-1 through 512-5 in the corresponding cells 504 and 508. The wireless communication devices 512-1 through 512-5 are generally referred to herein collectively as wireless communication devices 512 and individually as wireless communication device 512. In the following description, the wireless communication devices 512 are oftentimes UEs, but the present disclosure is not limited thereto.

Figure 6

Figure 6 illustrates a wireless communication system represented as a 5G network architecture composed of core Network Functions (NFs), where interaction between any two NFs is represented by a point-to-point reference poi nt/i nterface. Figure 6 can be viewed as one particular implementation of the system 500 of Figure 5.

Seen from the access side the 5G network architecture shown in Figure 6 comprises a plurality of UEs 512 connected to either a RAN 502 or an Access Network (AN) as well as an AMF 600. Typically, the R(AN) 502 comprises base stations, e.g., such as eNBs or gNBs or similar. Seen from the core network side, the 5GC NFs shown in Figure 6 include a NSSF 602, an AUSF 604, a UDM 606, the AMF 600, a SMF 608, a PCF 610, and an Application Function (AF) 612.

Reference point representations of the 5G network architecture are used to develop detailed call flows in the normative standardization. The N1 reference point is defined to carry signaling between the UE 512 and AMF 600. The reference points for connecting between the AN 502 and AMF 600 and between the AN 502 and UPF 614 are defined as N2 and N3, respectively. There is a reference point, N11, between the AMF 600 and SMF 608, which implies that the SMF 608 is at least partly controlled by the AMF 600. N4 is used by the SMF 608 and UPF 614 so that the UPF 614 can be set using the control signal generated by the SMF 608, and the UPF 614 can report its state to the SMF 608. N9 is the reference point for the connection between different UPFs 614, and N14 is the reference point connecting between different AMFs 600, respectively. N15 and N7 are defined since the PCF 610 applies policy to the AMF 600 and SMF 608, respectively. N12 is required for the AMF 600 to perform authentication of the UE 512. N8 and N10 are defined because the subscription data of the UE 512 is required for the AMF 600 and SMF 608.

The 5GC network aims at separating UP and CP. The UP carries user traffic while the CP carries signaling in the network. In Figure 6, the UPF 614 is in the UP and all other NFs, i.e., the AMF 600, SMF 608, PCF 610, AF 612, NSSF 602, AUSF 604, and UDM 606, are in the CP. Separating the UP and CP guarantees each plane resource to be scaled independently. It also allows UPFs to be deployed separately from CP functions in a distributed fashion. In this architecture, UPFs may be deployed very close to UEs to shorten the Round Trip Time (RTT) between UEs and data network for some applications requiring low latency.

The core 5G network architecture is composed of modularized functions. For example, the AMF 600 and SMF 608 are independent functions in the CP. Separated AMF 600 and SMF 608 allow independent evolution and scaling. Other CP functions like the PCF 610 and AUSF 604 can be separated as shown in Figure 6. Modularized function design enables the 5GC network to support various services flexibly.

Each NF interacts with another NF directly. It is possible to use intermediate functions to route messages from one NF to another NF. In the CP, a set of interactions between two NFs is defined as service so that its reuse is possible. This service enables support for modularity. The UP supports interactions such as forwarding operations between different UPFs.

Figure 7

Figure 7 illustrates a 5G network architecture using service-based interfaces between the NFs in the CP, instead of the point-to-point reference points/interfaces used in the 5G network architecture of Figure 6. However, the NFs described above with reference to Figure 6 correspond to the NFs shown in Figure 7. The service(s) etc. that a NF provides to other authorized NFs can be exposed to the authorized NFs through the service-based interface. In Figure 7 the service-based interfaces are indicated by the letter “N” followed by the name of the NF, e.g., Namf for the service-based interface of the AMF 600 and Nsmf for the service-based interface of the SMF 608, etc. The NEF 700 and the NRF 702 in Figure 7 are not shown in Figure 6 discussed above. However, it should be clarified that all NFs depicted in Figure 6 can interact with the NEF 700 and the NRF 702 of Figure 7 as necessary, though not explicitly indicated in Figure 6.

Some properties of the NFs shown in Figures 6 and 7 may be described in the following manner. The AMF 600 provides UE-based authentication, authorization, mobility management, etc. A UE 512 even using multiple access technologies is basically connected to a single AMF 600 because the AMF 600 is independent of the access technologies. The SMF 608 is responsible for session management and allocates Internet Protocol (IP) addresses to UEs. It also selects and controls the UPF 614 for data transfer. If a UE 512 has multiple sessions, different SMFs 608 may be allocated to each session to manage them individually and possibly provide different functionalities per session. The AF 612 provides information on the packet flow to the PCF 610 responsible for policy control in order to support QoS. Based on the information, the PCF 610 determines policies about mobility and session management to make the AMF 600 and SMF 608 operate properly.

The AUSF 604 supports authentication function for UEs or similar and thus stores data for authentication of UEs or similar while the UDM 606 stores subscription data of the UE 512. The Data Network (DN), not part of the 5GC network, provides Internet access or operator services and similar.

An NF may be implemented either as a network element on a dedicated hardware, as a software instance running on a dedicated hardware, or as a virtualized function instantiated on an appropriate platform, e.g., a cloud infrastructure.

Figure 8

Figure 8 is a schematic block diagram of a radio access node 800 according to some embodiments of the present disclosure. Optional features are represented by dashed boxes. The radio access node 800 may be, for example, a base station 502 or 506 or a network node that implements all or part of the functionality of the base station 502 or gNB described herein. As illustrated, the radio access node 800 includes a control system 802 that includes one or more processors 804 (e.g., Central Processing Units (CPUs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), and/or the like), memory 806, and a network interface 808. The one or more processors 804 are also referred to herein as processing circuitry. In addition, the radio access node 800 may include one or more radio units 810 that each includes one or more transmitters 812 and one or more receivers 814 coupled to one or more antennas 816. The radio units 810 may be referred to or be part of radio interface circuitry. In some embodiments, the radio unit(s) 810 is external to the control system 802 and connected to the control system 802 via, e.g., a wired connection (e.g., an optical cable). However, in some other embodiments, the radio unit(s) 810 and potentially the antenna(s) 816 are integrated together with the control system 802. The one or more processors 804 operate to provide one or more functions of a radio access node 800 as described herein. In some embodiments, the function(s) are implemented in software that is stored, e.g., in the memory 806 and executed by the one or more processors 804.

Figure 9

Figure 9 is a schematic block diagram that illustrates a virtualized embodiment of the radio access node 800 according to some embodiments of the present disclosure. This discussion is equally applicable to other types of network nodes. Further, other types of network nodes may have similar virtualized architectures. Again, optional features are represented by dashed boxes.

As used herein, a "virtualized” radio access node is an implementation of the radio access node 800 in which at least a portion of the functionality of the radio access node 800 is implemented as a virtual component(s) (e.g., via a virtual machine(s) executing on a physical processing node(s) in a network(s)). As illustrated, in this example, the radio access node 800 may include the control system 802 and/or the one or more radio units 810, as described above. The control system 802 may be connected to the radio unit(s) 810 via, for example, an optical cable or the like. The radio access node 800 includes one or more processing nodes 900 coupled to or included as part of a network(s) 902. If present, the control system 802 or the radio unit(s) are connected to the processing node(s) 900 via the network 902. Each processing node 900 includes one or more processors 904 (e.g., CPUs, ASICs, FPGAs, and/or the like), memory 906, and a network interface 908.

In this example, functions 910 of the radio access node 800 described herein are implemented at the one or more processing nodes 900 or distributed across the one or more processing nodes 900 and the control system 802 and/or the radio unit(s) 810 in any desired manner. In some particular embodiments, some or all of the functions 910 of the radio access node 800 described herein are implemented as virtual components executed by one or more virtual machines implemented in a virtual environment(s) hosted by the processing node(s) 900. As will be appreciated by one of ordinary skill in the art, additional signaling or communication between the processing node(s) 900 and the control system 802 is used in order to carry out at least some of the desired functions 910. Notably, in some embodiments, the control system 802 may not be included, in which case the radio unit(s) 810 communicate directly with the processing node(s) 900 via an appropriate network interface(s).

In some embodiments, a computer program including instructions which, when executed by at least one processor, causes the at least one processor to carry out the functionality of radio access node 800 or a node (e.g., a processing node 900) implementing one or more of the functions 910 of the radio access node 800 in a virtual environment according to any of the embodiments described herein is provided. In some embodiments, a carrier comprising the aforementioned computer program product is provided. The carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium (e.g., a non-transitory computer readable medium such as memory).

Figure 10

Figure 10 is a schematic block diagram of the radio access node 800 according to some other embodiments of the present disclosure. The radio access node 800 includes one or more modules 1000, each of which is implemented in software. The module(s) 1000 provide the functionality of the radio access node 800 described herein. This discussion is equally applicable to the processing node 900 of Figure 9 where the modules 1000 may be implemented at one of the processing nodes 900 or distributed across multiple processing nodes 900 and/or distributed across the processing node(s) 900 and the control system 802.

Figure 11

Figure 11 is a schematic block diagram of a wireless communication device 1100 according to some embodiments of the present disclosure. As illustrated, the wireless communication device 1100 includes one or more processors 1102 (e.g., CPUs, ASICs, FPGAs, and/or the like), memory 1104, and one or more transceivers 1106 each including one or more transmitters 1108 and one or more receivers 1110 coupled to one or more antennas 1112. The transceiver(s) 1106 includes radio-front end circuitry connected to the antenna(s) 1112 that is configured to condition signals communicated between the antenna(s) 1112 and the processor(s) 1102, as will be appreciated by on of ordinary skill in the art. The processors 1102 are also referred to herein as processing circuitry. The transceivers 1106 are also referred to herein as radio circuitry. In some embodiments, the functionality of the wireless communication device 1100 described above may be fully or partially implemented in software that is, e.g., stored in the memory 1104 and executed by the processor(s) 1102. Note that the wireless communication device 1100 may include additional components not illustrated in Figure 11 such as, e.g., one or more user interface components (e.g., an input/output interface including a display, buttons, a touch screen, a microphone, a speaker(s), and/or the like and/or any other components for allowing input of information into the wireless communication device 1100 and/or allowing output of information from the wireless communication device 1100), a power supply (e.g., a battery and associated power circuitry), etc.

In some embodiments, a computer program including instructions which, when executed by at least one processor, causes the at least one processor to carry out the functionality of the wireless communication device 1100 according to any of the embodiments described herein is provided. In some embodiments, a carrier comprising the aforementioned computer program product is provided. The carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium (e.g., a non-transitory computer readable medium such as memory). Figure 12

Figure 12 is a schematic block diagram of the wireless communication device 1100 according to some other embodiments of the present disclosure. The wireless communication device 1100 includes one or more modules 1200, each of which is implemented in software. The module(s) 1200 provide the functionality of the wireless communication device 1100 described herein.

Figure 13

With reference to Figure 13, in accordance with an embodiment, a communication system includes a telecommunication network 1300, such as a 3GPP-type cellular network, which comprises an access network 1302, such as a RAN, and a core network 1304. The access network 1302 comprises a plurality of base stations 1306A, 1306B, 1306C, such as Node Bs, eNBs, gNBs, or other types of wireless Access Points (APs), each defining a corresponding coverage area 1308A, 1308B, 1308C. Each base station 1306A, 1306B, 1306C is connectable to the core network 1304 over a wired or wireless connection 1310. A first UE 1312 located in coverage area 1308C is configured to wirelessly connect to, or be paged by, the corresponding base station 1306C. A second UE 1314 in coverage area 1308A is wirelessly connectable to the corresponding base station 1306A. While a plurality of UEs 1312, 1314 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station 1306.

The telecommunication network 1300 is itself connected to a host computer 1316, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server, or as processing resources in a server farm. The host computer 1316 may be under the ownership or control of a service provider or may be operated by the service provider or on behalf of the service provider. Connections 1318 and 1320 between the telecommunication network 1300 and the host computer 1316 may extend directly from the core network 1304 to the host computer 1316 or may go via an optional intermediate network 1322. The intermediate network 1322 may be one of, or a combination of more than one of, a public, private, or hosted network; the intermediate network 1322, if any, may be a backbone network or the Internet; in particular, the intermediate network 1322 may comprise two or more sub-networks (not shown).

The communication system of Figure 13 as a whole enables connectivity between the connected UEs 1312, 1314 and the host computer 1316. The connectivity may be described as an Over-the-Top (OTT) connection 1324. The host computer 1316 and the connected UEs 1312, 1314 are configured to communicate data and/or signaling via the OTT connection 1324, using the access network 1302, the core network 1304, any intermediate network 1322, and possible further infrastructure (not shown) as intermediaries. The OTT connection 1324 may be transparent in the sense that the participating communication devices through which the OTT connection 1324 passes are unaware of routing of uplink and downlink communications. For example, the base station 1306 may not or need not be informed about the past routing of an incoming downlink communication with data originating from the host computer 1316 to be forwarded (e.g., handed over) to a connected UE 1312. Similarly, the base station 1306 need not be aware of the future routing of an outgoing uplink communication originating from the UE 1312 towards the host computer 1316.

Figure 14

Example implementations, in accordance with an embodiment, of the UE, base station, and host computer discussed in the preceding paragraphs will now be described with reference to Figure 14. In a communication system 1400, a host computer 1402 comprises hardware 1404 including a communication interface 1406 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system 1400. The host computer 1402 further comprises processing circuitry 1408, which may have storage and/or processing capabilities. In particular, the processing circuitry 1408 may comprise one or more programmable processors, ASICs, FPGAs, or combinations of these (not shown) adapted to execute instructions. The host computer 1402 further comprises software 1410, which is stored in or accessible by the host computer 1402 and executable by the processing circuitry 1408. The software 1410 includes a host application 1412. The host application 1412 may be operable to provide a service to a remote user, such as a UE 1414 connecting via an OTT connection 1416 terminating at the UE 1414 and the host computer 1402. In providing the service to the remote user, the host application 1412 may provide user data which is transmitted using the OTT connection 1416.

The communication system 1400 further includes a base station 1418 provided in a telecommunication system and comprising hardware 1420 enabling it to communicate with the host computer 1402 and with the UE 1414. The hardware 1420 may include a communication interface 1422 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 1400, as well as a radio interface 1424 for setting up and maintaining at least a wireless connection 1426 with the UE 1414 located in a coverage area (not shown in Figure 14) served by the base station 1418. The communication interface 1422 may be configured to facilitate a connection 1428 to the host computer 1402. The connection 1428 may be direct or it may pass through a core network (not shown in Figure 14) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, the hardware 1420 of the base station 1418 further includes processing circuitry 1430, which may comprise one or more programmable processors, ASICs, FPGAs, or combinations of these (not shown) adapted to execute instructions. The base station 1418 further has software 1432 stored internally or accessible via an external connection.

The communication system 1400 further includes the UE 1414 already referred to. The UE's 1414 hardware 1434 may include a radio interface 1436 configured to set up and maintain a wireless connection 1426 with a base station serving a coverage area in which the UE 1414 is currently located. The hardware 1434 of the UE 1414 further includes processing circuitry 1438, which may comprise one or more programmable processors, ASICs, FPGAs, or combinations of these (not shown) adapted to execute instructions. The UE 1414 further comprises software 1440, which is stored in or accessible by the UE 1414 and executable by the processing circuitry 1438. The software 1440 includes a client application 1442. The client application 1442 may be operable to provide a service to a human or non-human user via the UE 1414, with the support of the host computer 1402. In the host computer 1402, the executing host application 1412 may communicate with the executing client application 1442 via the OTT connection 1416 terminating at the UE 1414 and the host computer 1402. In providing the service to the user, the client application 1442 may receive request data from the host application 1412 and provide user data in response to the request data. The OTT connection 1416 may transfer both the request data and the user data. The client application 1442 may interact with the user to generate the user data that it provides.

It is noted that the host computer 1402, the base station 1418, and the UE 1414 illustrated in Figure 14 may be similar or identical to the host computer 1316, one of the base stations 1306A, 1306B, 1306C, and one of the UEs 1312, 1314 of Figure 13, respectively. This is to say, the inner workings of these entities may be as shown in Figure 14 and independently, the surrounding network topology may be that of Figure 13.

In Figure 14, the OTT connection 1416 has been drawn abstractly to illustrate the communication between the host computer 1402 and the UE 1414 via the base station 1418 without explicit reference to any intermediary devices and the precise routing of messages via these devices. The network infrastructure may determine the routing, which may be configured to hide from the UE 1414 or from the service provider operating the host computer 1402, or both. While the OTT connection 1416 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).

The wireless connection 1426 between the UE 1414 and the base station 1418 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to the UE 1414 using the OTT connection 1416, in which the wireless connection 1426 forms the last segment. More precisely, the teachings of these embodiments may improve the e.g., data rate, latency, power consumption, etc. and thereby provide benefits such as e.g., reduced user waiting time, relaxed restriction on file size, better responsiveness, extended battery lifetime, etc.

A measurement procedure may be provided for the purpose of monitoring data rate, latency, and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 1416 between the host computer 1402 and the UE 1414, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection 1416 may be implemented in the software 1410 and the hardware 1404 of the host computer 1402 or in the software 1440 and the hardware 1434 of the UE 1414, or both. In some embodiments, sensors (not shown) may be deployed in or in association with communication devices through which the OTT connection 1416 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which the software 1410, 1440 may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 1416 may include message format, retransmission settings, preferred routing, etc.; the reconfiguring need not affect the base station 1418, and it may be unknown or imperceptible to the base station 1418. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling facilitating the host computer 1402's measurements of throughput, propagation times, latency, and the like. The measurements may be implemented in that the software 1410 and 1440 causes messages to be transmitted, in particular empty or 'dummy' messages, using the OTT connection 1416 while it monitors propagation times, errors, etc.

Figure 15

Figure 15 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station, and a UE which may be those described with reference to Figures 13 and 14. For simplicity of the present disclosure, only drawing references to Figure

15 will be included in this section. In step 1500, the host computer provides user data. In sub-step 1502 (which may be optional) of step 1500, the host computer provides the user data by executing a host application. In step 1504, the host computer initiates a transmission carrying the user data to the UE. In step 1506 (which may be optional), the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1508 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

Figure 16

Figure 16 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station, and a UE which may be those described with reference to Figures 13 and 14. For simplicity of the present disclosure, only drawing references to Figure

16 will be included in this section. In step 1600 of the method, the host computer provides user data. In an optional substep (not shown) the host computer provides the user data by executing a host application. In step 1602, the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1604 (which may be optional), the UE receives the user data carried in the transmission.

Figure 17

Figure 17 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station, and a UE which may be those described with reference to Figures 13 and 14. For simplicity of the present disclosure, only drawing references to Figure 17 will be included in this section. In step 1700 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 1702, the UE provides user data. In sub-step 1704 (which may be optional) of step 1700, the UE provides the user data by executing a client application. In sub-step 1706 (which may be optional) of step 1702, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. In providing the user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the UE initiates, in sub-step 1708 (which may be optional), transmission of the user data to the host computer. In step 1710 of the method, the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.

Figure 18

Figure 18 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station, and a UE which may be those described with reference to Figures 13 and 14. For simplicity of the present disclosure, only drawing references to Figure 18 will be included in this section. In step 1800 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station receives user data from the UE. In step 1802 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step 1804 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

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 Processor (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. In some implementations, 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.

While processes in the figures may show a particular order of operations performed by certain embodiments of the present disclosure, it should be understood that such order is exemplary (e.g., alternative embodiments may perform the operations in a different order, combine certain operations, overlap certain operations, etc.). Embodiments

Some of the embodiments described above may be summarized in the following manner:

Group A Embodiments

1 . A method performed by a wireless device for accessing localized services, the method comprising one or more of:

- receiving (Figure 3, steps 1-2; Figure 4, steps 1-2) an indication that the broker function (or remote provisioning function (e.g., onboarding includes a step for remote provisioning)) is supported in the network;

- obtaining (Figure 3, step 0; Figure 4, step 0) a set of service parameters of localized service, including broker network IDs;

- selecting (Figure 3, step 3; Figure 4, step 3) one or more specific hosting networks to access the desired localized service, or one or more specific localized services;

- requesting (Figure 3, step 4; Figure 4, step 4) Provisioning Server, PVS, associated with the selected hosting networks or the selected localized services;

- receiving (Figure 3, step 5; Figure 4, step 5) PVS address associated with the selected hosting network;

- receiving (Figure 3, step 6; Figure 4, step 6) credentials to be used to access the hosting network that provides access to the localized service;

- receiving (Figure 3, step 7; Figure 4, step 7) a redirection to the selected hosting network, based on trigger (e.g., de-registration request with selected hosting network ID, de-registration request with new cause "redirection is requested, etc.) from wireless device;

- differentiating the request of PVS by indicating the selected hosting network or the selected localized service, either via "Protocol Data Unit, PDU, Session Establishment Request message”, or "Uplink, UL, Non-Access Stratum, NAS, Transport message”, or via Domain Name System, DNS, queries with Full Qualified Domain Name, FQDN, constructed by the wireless device

- accessing the hosting network for localized services, using the received credentials.

2. The method of embodiment 1 wherein receiving the indication that the broker function (or remote provisioning function) is supported in the network comprises receiving a (R)AN broadcast of an indication bit of supporting broker function.

3. The method of embodiment 1 wherein receiving the indication that the broker function (or remote provisioning function) is supported in the network comprises receiving in a Registration Accept message that the network supports broker function. 4. The method of any of embodiments 1 to 3 wherein the broker network is a network that maintains conventional business relation with other home networks operators (e.g., Public Land Mobile Network, PLMN, operator), and establishes interfaces with home networks.

5. The method of any of embodiments 1 to 4 wherein the broker network is a partner network of the hosting networks which are deployed in the same region or same country.

6. The method of embodiment 1 wherein the serving network is a home network or can be a network which has relationship with a home network.

7. The method of any of the previous embodiments, further comprising:

- providing user data; and

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

Group B Embodiments

8. A method performed by a base station or a network node for providing access to localized services, the method comprising one or more of:

- transmitting (Figure 3, steps 1-2; Figure 4, steps 1-2) an indication that the broker function (or remote provisioning function) is supported in the network;

- transmitting (Figure 3, step 0; Figure 4, step 0) a set of service parameters of localized service, including broker network IDs;

- receiving (Figure 3, step 4; Figure 4, step 4) a request for Provisioning Server, PVS, associated with the selected hosting networks or the selected localized services.;

- transmitting (Figure 3, step 5; Figure 4, step 5) PVS address associated with the selected hosting network (e.g., hosting network ID and credential type: (native I onboarding/ credentials holder), etc.);

- transmitting (Figure 3, step 6; Figure 4, step 6) credentials to be used to access the hosting network that provides access to the localized service;

- transmitting (Figure 3, step 7; Figure 4, step 7) a redirection to the selected hosting network, based on trigger from wireless device; and

- differentiating the request of PVS by indicating the selected hosting network or the selected localized service, either via "Protocol Data Unit, PDU, Session Establishment Request message”, or "Uplink, UL, Non-Access Stratum, NAS, Transport message”, or via Domain Name System, DNS, queries with Full Qualified Domain Name, FQDN, constructed by the wireless device. 9. The method of embodiment 8 wherein transmitting the indication that the broker function (or remote provisioning function) is supported in the network comprises transmitting a (R)AN broadcast of an indication bit of supporting broker function.

10. The method of embodiment 8 wherein transmitting the indication that the broker function (or remote provisioning function) is supported in the network comprises transmitting in a Registration Accept message that the network supports broker function.

11 . The method of any of embodiments 8 to 10 wherein the broker network is a network that maintains conventional business relation with other home networks operators (e.g., Public Land Mobile Network, PLMN, operator), and establishes interfaces with home networks.

12. The method of any of embodiments 8 to 11 wherein the broker network is a partner network of the hosting networks which are deployed in the same region or same country.

13. The method of embodiment 8 wherein the serving network is a home network or can be a network which has relationship with a home network.

14. The method of any of the previous embodiments wherein the network node comprises one or more of: an Access and Mobility Management Function (AMF); a Policy Control Function (PCF); a Session Management Function (SMF); Application Function (AF); a Domain Name System (DNS) server; and a PVS.

15. The method of any of the previous embodiments wherein the AMF informs the NG-RAN via NGAP about the selected hosting network ID, e.g., as new IE in the UE CONTEXT RELEASE COMMAND for that UE.

16. The method of any of the previous embodiments wherein the NG-RAN assists the UE in finding the hosting network by sending an RRC release with redirect message (e.g., frequency and optionally cell information) or RRC release with multiple frequencies to the UE.

17. The method of any of the previous embodiments wherein the DNS response can include a list of hosting networks which can provide access to the selected localized service.

18. The method of the previous embodiment wherein, after the UE receives such response, it selects a hosting network and queries DNS server to ask for IP address of the PVS associated with the selected hosting network. 19. The method of any of the previous embodiments wherein AMF or SMF is locally configured with mapping table between [PVS information] and [hosting network identifier], or a mapping table between [PVS information] and [localized service identifier].

20. The method of any of the previous embodiments wherein the DNS server will return a response with the IP address of the Provisioning Server (PVS) associated with the selected hosting network.

21 . The method of any of the previous embodiments, further comprising:

- obtaining user data; and

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

Group C Embodiments

22. A wireless device for accessing localized services, the wireless device comprising:

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

- power supply circuitry configured to supply power to the wireless device.

23. A base station or a network node for providing access to localized services, the base station comprising:

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

- power supply circuitry configured to supply power to the base station.

24. A User Equipment, UE, for accessing localized services, the UE comprising:

- an antenna configured to send and receive wireless signals;

- radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry;

- the processing circuitry being configured to perform any of the steps of any of the Group A embodiments;

- an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry;

- an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and

- a battery connected to the processing circuitry and configured to supply power to the UE.

25. A communication system including a host computer comprising:

- processing circuitry configured to provide user data; and - a communication interface configured to forward the user data to a cellular network for transmission to a User Equipment, UE;

- wherein the cellular network comprises a base station or a network node having a radio interface and processing circuitry, the base station's or network node's processing circuitry configured to perform any of the steps of any of the Group B embodiments.

26. The communication system of the previous embodiment further including the base station and/or a network node.

27. The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station or the network node.

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

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

- the UE comprises processing circuitry configured to execute a client application associated with the host application.

29. A method implemented in a communication system including a host computer, a base station or a network node, and a User Equipment, UE, the method comprising:

- at the host computer, providing user data; and

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

30. The method of the previous embodiment, further comprising, at the base station or the network node, transmitting the user data.

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

32. A User Equipment, UE, configured to communicate with a base station or a network node, the UE comprising a radio interface and processing circuitry configured to perform the method of the previous 3 embodiments. 33. A communication system including a host computer comprising:

- processing circuitry configured to provide user data; and

- a communication interface configured to forward user data to a cellular network for transmission to a User Equipment, UE;

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

34. The communication system of the previous embodiment, wherein the cellular network further includes a base station or a network node configured to communicate with the UE.

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

- the UE's processing circuitry is configured to execute a client application associated with the host application.

36. A method implemented in a communication system including a host computer, a base station or a network node, and a User Equipment, UE, the method comprising:

- at the host computer, providing user data; and

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

37. The method of the previous embodiment, further comprising at the UE, receiving the user data from the base station or the network node.

38. A communication system including a host computer comprising:

- communication interface configured to receive user data originating from a transmission from a User Equipment, UE, to a base station or a network node;

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

39. The communication system of the previous embodiment, further including the UE. 40. The communication system of the previous 2 embodiments, further including the base station or the network node, wherein the base station or the network node comprises a radio interface configured to communicate with the UE and a communication interface configured to forward to the host computer the user data carried by a transmission from the UE to the base station or the network node.

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

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

- the UE's processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data.

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

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

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

43. A method implemented in a communication system including a host computer, a base station or a network node, and a User Equipment, UE, the method comprising:

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

44. The method of the previous embodiment, further comprising, at the UE, providing the user data to the base station or the network node.

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

- at the UE, executing a client application, thereby providing the user data to be transmitted; and

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

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

- at the UE, executing a client application; and

- at the UE, receiving input data to the client application, the input data being provided at the host computer by executing a host application associated with the client application;

- wherein the user data to be transmitted is provided by the client application in response to the input data. 47. A communication system including a host computer comprising a communication interface configured to receive user data originating from a transmission from a User Equipment, UE, to a base station or a network node, wherein the base station or the network node comprises a radio interface and processing circuitry, the base station's or the network node's processing circuitry configured to perform any of the steps of any of the Group B embodiments.

48. The communication system of the previous embodiment further including the base station or the network node.

49. The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station or the network node.

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

- the UE is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer.

51 . A method implemented in a communication system including a host computer, a base station or a network node, and a User Equipment, UE, the method comprising:

- at the host computer, receiving, from the base station or the network node, user data originating from a transmission which the base station or the network node has received from the UE, wherein the UE performs any of the steps of any of the Group A embodiments.

52. The method of the previous embodiment, further comprising at the base station or the network node, receiving the user data from the UE.

53. The method of the previous 2 embodiments, further comprising at the base station or the network node, initiating a transmission of the received user data to the host computer.

At least some of the following abbreviations may be used in this disclosure. If there is an inconsistency between abbreviations, preference should be given to how it is used above. If listed multiple times below, the first listing should be preferred over any subsequent listing(s).

• 3GPP Third Generation Partnership Project

• 5G Fifth Generation

• 5GC Fifth Generation Core

• 5GS Fifth Generation System

• AF Application Function

• AMF Access and Mobility Management Function

• AN Access Network

• AP Access Point

• AUSF Authentication Server Function

• DL Downlink

• DNS Domain Name System

• eNB Enhanced or Evolved Node B

• FQDN Full Qualified Domain Name

• gNB New Radio Base Station

• HSS Home Subscriber Server

• IE Information Element

• loT Internet of Things

• IP Internet Protocol

• LTE Long Term Evolution

• MME Mobility Management Entity

• NAS Non-Access Stratum

• NEF Network Exposure Function

• NF Network Function

• NG Next Generation

• NR New Radio

• NRF Network Function Repository Function

• NSSF Network Slice Selection Function

• OTT Over-the-Top

• PCF Policy Control Function P-GW Packet Data Network Gateway

PLMN Public Land Mobile Network

PDU Protocol Data Unit

P-GW Packet Data Network Gateway

PLMN Public Land Mobile Network

PVS Provisioning Server

QoS Quality of Service

RAN Radio Access Network

SCEF Service Capability Exposure Function

SMF Session Management Function

SNPN Stand Alone Non-Public Networks

SP Service Provider

TCI Transmission Configuration Indicator

TP Transmission Point

TRP Transmission/Reception Point

TS Technical Specification

UDM Unified Data Management

UE User Equipment

UL Uplink

UPF User Plane Function

Claims

CLAIMS What is claimed is:

2. The method of claim 1 wherein receiving the indication that the broker function (or remote provisioning function) is supported in the network comprises receiving a (R)AN broadcast of an indication bit of supporting broker function.

3. The method of claim 1 wherein receiving the indication that the broker function (or remote provisioning function) is supported in the network comprises receiving in a Registration Accept message that the network supports broker function.

4. The method of any one of claims 1 to 3 wherein the broker network is a network that maintains conventional business relation with other home networks operators (e.g., Public Land Mobile Network, PLMN, operator), and establishes interfaces with home networks.

5. The method of any one of claims 1 to 4 wherein the broker network is a partner network of the hosting networks which are deployed in the same region or same country.

6. The method of claim 1 wherein the serving network is a home network or can be a network which has relationship with a home network.

7. The method of any one of claims 1-6, further comprising:

- providing user data; and

- differentiating the request of PVS by indicating the selected hosting network or the selected localized service, either via "Protocol Data Unit, PDU, Session Establishment Request message”, or "Uplink, UL, Non-Access Stratum, NAS, Transport message”, or via Domain Name System, DNS, queries with Full Qualified Domain Name, FQDN, constructed by the wireless device.

9. The method of claim 8 wherein transmitting the indication that the broker function (or remote provisioning function) is supported in the network comprises transmitting a (R)AN broadcast of an indication bit of supporting broker function.

10. The method of claim 8 wherein transmitting the indication that the broker function (or remote provisioning function) is supported in the network comprises transmitting in a Registration Accept message that the network supports broker function.

11 . The method of any one of claims 8 to 10 wherein the broker network is a network that maintains conventional business relation with other home networks operators (e.g., Public Land Mobile Network, PLMN, operator), and establishes interfaces with home networks.

12. The method of any one of claims 8 to 11 wherein the broker network is a partner network of the hosting networks which are deployed in the same region or same country.

13. The method of claim 8 wherein the serving network is a home network or can be a network which has relationship with a home network.

14. The method of any one of claims 8-13 wherein the network node comprises one or more of: an Access and Mobility Management Function (AMF); a Policy Control Function (PCF); a Session Management Function (SMF);

Application Function (AF); a Domain Name System (DNS) server; and a PVS.

15. The method of any one of claims 8-14 wherein the AMF informs the NG-RAN via NGAP about the selected hosting network ID, e.g., as new IE in the UE CONTEXT RELEASE COMMAND for that UE.

16. The method of any one of claims 8-15 wherein the NG-RAN assists the UE in finding the hosting network by sending an RRC release with redirect message (e.g., frequency and optionally cell information) or RRC release with multiple frequencies to the UE.

17. The method of any one of claims 8-16 wherein the DNS response can include a list of hosting networks which can provide access to the selected localized service.

18. The method of the previous claim 17 wherein, after the UE receives such response, it selects a hosting network and queries DNS server to ask for IP address of the PVS associated with the selected hosting network.

19. The method of any one of claims 8-18 wherein AMF or SMF is locally configured with mapping table between [PVS information] and [hosting network identifier], or a mapping table between [PVS information] and [localized service identifier].

20. The method of any one of claims 8-19 wherein the DNS server will return a response with the IP address of the Provisioning Server (PVS) associated with the selected hosting network.

21 . The method of any one of claims 8-20, further comprising:

- obtaining user data; and

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

- processing circuitry configured to perform any of the steps of any one of claims 1-7; and

- power supply circuitry configured to supply power to the wireless device.

- processing circuitry configured to perform any of the steps of any one of claims 8-21 ; and

- power supply circuitry configured to supply power to the base station.

24. A User Equipment, UE, for accessing localized services, the UE comprising:

- an antenna configured to send and receive wireless signals;

- the processing circuitry being configured to perform any of the steps of any one of claims 1-7;

25. A communication system including a host computer comprising:

- wherein the cellular network comprises a base station or a network node having a radio interface and processing circuitry, the base station's or network node's processing circuitry configured to perform any of the steps of any one of claims 8-21 .

26. The communication system of claim 25 further including the base station and/or a network node.

27. The communication system of claim 25 or 26, further including the UE, wherein the UE is configured to communicate with the base station or the network node.

28. The communication system of any one of claims 25-27, wherein:

- at the host computer, providing user data; and

- at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station or the network node, wherein the base station or the network node performs any of the steps of any one of claims 8-21 .

30. The method of the claim 29, further comprising, at the base station or the network node, transmitting the user data.

31 . The method of any one of claims 29-30, wherein the user data is provided at the host computer by executing a host application, the method further comprising, at the UE, executing a client application associated with the host application.

32. A User Equipment, UE, configured to communicate with a base station or a network node, the UE comprising a radio interface and processing circuitry configured to perform the method any one of claims 29-31 . 31

33. A communication system including a host computer comprising:

- processing circuitry configured to provide user data; and

- wherein the UE comprises a radio interface and processing circuitry, the UE's components configured to perform any of the steps of any one of claims 1-7.

34. The communication system of claim 33, wherein the cellular network further includes a base station or a network node configured to communicate with the UE.

35. The communication system of any one of claims 33-34, wherein:

- at the host computer, providing user data; and

- at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station or the network node, wherein the UE performs any of the steps of any one of claims 1-7.

37. The method of claim 26, further comprising at the UE, receiving the user data from the base station or the network node.

38. A communication system including a host computer comprising:

- wherein the UE comprises a radio interface and processing circuitry, the UE's processing circuitry configured to perform any of the steps of any one of claims 1-7.

39. The communication system of claim 38, further including the UE.

40. The communication system of any one of claims 38-39, further including the base station or the network node, wherein the base station or the network node comprises a radio interface configured to communicate with the UE and a communication interface configured to forward to the host computer the user data carried by a transmission from the UE to the base station or the network node.

41 . The communication system of any one of claims 38-40, wherein:

42. The communication system of any one of claims 38-41 , wherein:

- at the host computer, receiving user data transmitted to the base station or the network node from the UE, wherein the UE performs any of the steps of any one of claims 1-7.

44. The method of claim 43, further comprising, at the UE, providing the user data to the base station or the network node.

45. The method of any one of claims 43-44, further comprising:

46. The method any one of claims 42-44, further comprising:

- at the UE, executing a client application; and

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

47. A communication system including a host computer comprising a communication interface configured to receive user data originating from a transmission from a User Equipment, UE, to a base station or a network node, wherein the base station or the network node comprises a radio interface and processing circuitry, the base station's or the network node's processing circuitry configured to perform any of the steps of any one of claims 8-21 .

48. The communication system of claim 47 further including the base station or the network node.

49. The communication system of any one of claims 47-48, further including the UE, wherein the UE is configured to communicate with the base station or the network node.

50. The communication system of any one of claims 47-49, wherein:

- at the host computer, receiving, from the base station or the network node, user data originating from a transmission which the base station or the network node has received from the UE, wherein the UE performs any of the steps of any one of claims 1-7.

52. The method of claim 51 , further comprising at the base station or the network node, receiving the user data from the UE.

53. The method of any one of claims 51-52, further comprising at the base station or the network node, initiating a transmission of the received user data to the host computer.