Roaming for UE of a NPN

A first network node (20N) in a first communication network (20) transmits information to a second network node (10N) in a second communication network (10). The information indicates a third communication network (30) is in a control signaling path (15) between a communication device (2) and the second communication network (10). In some embodiments, the first network node (20N) and/or the second network node (10N) may apply one or more policies based on the information, e.g., whether to authenticate a subscription of the communication device (2) to the second communication network (10).

TECHNICAL FIELD

The present application relates generally to a communication network, and relates more particularly to access to such a network.

BACKGROUND

A communication network provides communication services to a subscriber that subscribes to receive those services. The communication network to which a subscriber has subscribed is referred to as the subscriber's home network. A subscriber can access its home network using any radio access network (RAN) provided by the home network itself. The geographical coverage area of the home network's RAN may be limited, though. The home network operator can nonetheless extend the geographical reach over which its communication services are accessible to its subscribers, by partnering with another communication network operator that agrees to share its RAN with the home network operator. With such a roaming partnership in place, subscribers can use the RAN that a so-called visited communication network shares with the home communication network in order to access the communication services of the home communication network, even when roaming outside of the home network's radio access coverage area.

The direct partnership between a communication device's home network and a visited network means that the communication device can roam to the visited network without compromising security requirements imposed by the home network. Indeed, the direct nature of the partnership means that the home network can remain in control of which visited network(s) are usable to access the home network. However, limiting roaming to only those visited networks with which the home network has a direct partnership in turn limits the coverage areas over which communication devices can access the services of the home network.

SUMMARY

Some embodiments herein inform a communication network about any intermediate communication network(s) that are in the control signaling path between a communication device and the communication network. One or more embodiments, for example, inform the communication network about the existence of and/or identity of such intermediate communication network(s), e.g., which may form a chain of intermediate networks via which the communication device accesses the communication network. Accordingly, rather than being ignorant of an intermediate network via which the communication device accesses the communication network, because the communication network does not have a direct roaming partnership with that intermediate network, the communication network is equipped with information about such an intermediate network. The communication network can then use this information for any number of policy decisions, e.g., whether to permit access via the intermediate network, whether to permit a certain service when accessed via the intermediate network, etc. Some embodiments thereby safeguard the communication network's ability to control which intermediate network(s) are used to access the communication network, even when the communication devices access the communication network via a an intermediate network that does not have a direct roaming partnership with the communication network.

More particularly, embodiments herein include a method performed by a first network node in a first communication network. The method comprises transmitting, to a second network node in a second communication network, information that indicates a third communication network is in a control signaling path between a communication device and the second communication network.

In some embodiments, the information indicates at least a portion of an identity or name of the third communication network that is in the control signaling path.

In some embodiments, the information indicates a third communication network is in the control signaling path, without indicating any portion of an identity or name of the third communication network.

In some embodiments, the information indicates a third communication network is in the control signaling path by indicating that the communication device is roaming or that the communication device is served by a visited communication network.

In some embodiments, the information indicates a third communication network is in the control signaling path by indicating that a visited communication network of the communication device is in the control signaling path. Additionally or alternatively, the information indicates a third communication network is in the control signaling path by indicating an identity or name of the visited communication network.

In some embodiments, the method further comprises receiving control signaling from a third network node in the third communication network, and based on receiving the control signaling from the third network node in the third communication network, transmitting control signaling to the second network node. In this case, the information is transmitted to the second network node in association with transmitting the control signaling to the second network node. In one or more of these embodiments, the control signaling received from the third network node is an authentication request requesting authentication of a subscription of the communication device to the second communication network. Additionally or alternatively, the control signaling transmitted to the second network node is an authentication request requesting authentication of a subscription of the communication device to the second communication network.

In some embodiments, the method further comprises transmitting, to the second network node, an authentication request requesting authentication of a subscription of the communication device to the second communication network. In this case, the information is included in the authentication request.

In some embodiments, the information further indicates the first communication network is in the control signaling path between the communication device and the second communication network.

In some embodiments, the second communication network is a non-public network, NPN.

In some embodiments, the second communication network is a public network.

In some embodiments, the first communication network is a public network. Additionally or alternatively, the third communication network is a public network.

In some embodiments, the first communication network is a non-public network. Additionally or alternatively, the third communication network is a non-public network.

In some embodiments, the first network node is an authentication server or implements an authentication server function. Additionally or alternatively, the second network node is an authentication server or implements an authentication server function.

In some embodiments, the third communication network is a roaming partner of the first communication network. In this case, the first communication network is a home public network of the communication device, and the third communication network is a visited network of the communication device.

In some embodiments, the method further comprises applying one or more policies based on the information. In one or more of these embodiments, the one or more policies include a policy that specifies, based on the information, whether the communication device is allowed to register with the first communication network, the second communication network, and/or the third communication network. In one or more of these embodiments, the one or more policies include a policy that specifies, based on the information, which one or more services of the first communication network, the second communication network, and/or the third communication network the communication device is allowed to use. Additionally or alternatively, the one or more policies include a policy that specifies, based on the information, which one or more network slices of the first communication network, the second communication network, and/or the third communication network the communication device is allowed to use.

Other embodiments herein include a method performed by a second network node in a second communication network. The method comprises receiving, from a first network node in a first communication network, information that indicates a third communication network is in a control signaling path between a communication device and the second communication network.

In some embodiments, the information indicates at least a portion of an identity or name of the third communication network that is in the control signaling path.

In some embodiments, the information indicates a third communication network is in the control signaling path, without indicating any portion of an identity or name of the third communication network.

In some embodiments, the information indicates a third communication network is in the control signaling path by indicating that the communication device is roaming or that the communication device is served by a visited communication network.

In some embodiments, the information indicates a third communication network is in the control signaling path by indicating that a visited communication network of the communication device is in the control signaling path. Additionally or alternatively, the information indicates a third communication network is in the control signaling path by indicating an identity or name of the visited communication network.

In some embodiments, the method further comprises receiving control signaling from the first network node in the first communication network. In this case, the information is received in association with receiving the control signaling from the first network node. In one or more of these embodiments, the control signaling received from the first network node is an authentication request requesting authentication of a subscription of the communication device to the second communication network.

In some embodiments, the method further comprises receiving, from the first network node, an authentication request requesting authentication of a subscription of the communication device to the second communication network, wherein the information is included in the authentication request.

In some embodiments, the information further indicates the first communication network is in the control signaling path between the communication device and the second communication network.

In some embodiments, the second communication network is a non-public network, NPN.

In some embodiments, the second communication network is a public network.

In some embodiments, the first communication network is a public network. Additionally or alternatively, the third communication network is a public network.

In some embodiments, the first communication network is a non-public network. Additionally or alternatively, the third communication network is a non-public network.

In some embodiments, first network node is an authentication server or implements an authentication server function. Additionally or alternatively, the second network node is an authentication server or implements an authentication server function.

In some embodiments, the third communication network is a roaming partner of the first communication network, the first communication network is a home public network of the communication device, and the third communication network is a visited network of the communication device.

In some embodiments, the method further comprises applying, based on the information, one or more policies with respect to a subscription of the communication device to the second communication network. In one or more of these embodiments, the one or more policies include a policy that specifies, based on the information, whether the communication device is allowed to register with the first communication network, the second communication network, and/or the third communication network. Additionally or alternatively, the one or more policies include a policy that specifies, based on the information, whether to authenticate the subscription of the communication device to the second communication network. In one or more of these embodiments, the one or more policies include a policy that specifies, based on the information, which one or more services of the first communication network, the second communication network, and/or the third communication network the communication device is allowed to use. Additionally or alternatively, the one or more policies include a policy that specifies, based on the information, which one or more network slices of the first communication network, the second communication network, and/or the third communication network the communication device is allowed to use.

Other embodiments herein include a first network node configured for use in a first communication network. The first network node comprises communication circuitry and processing circuitry. The processing circuitry is configured to transmit, to a second network node in a second communication network, information that indicates a third communication network is in a control signaling path between a communication device and the second communication network.

In some embodiments, the processing circuitry configured to perform the steps described above for the first network node.

Other embodiments herein include a second network node in a second communication network. The second communication network comprises communication circuitry and processing circuitry. The processing circuitry is configured to receive, from a first network node in a first communication network, information that indicates a third communication network is in a control signaling path between a communication device and the second wireless communication network.

In some embodiments, the processing circuitry configured to perform the steps described above for the second network node.

Other embodiments herein include a computer program comprising instructions which, when executed by at least one processor of a network node, causes the network node to perform the steps described above for the first network node and the second network node. In some embodiments, carrier containing the computer program described above is one of an electronic signal, optical signal, radio signal, or computer readable storage medium.

DETAILED DESCRIPTION

FIG.1shows a communication device2configured for communication. In some embodiments, the communication device2is a wireless communication device configured for wireless communication. As shown inFIG.1, for example, the communication device is exemplified as a user equipment (UE) or mobile device.

In any event, the communication device2is associated with a subscription to communication network10.FIG.1depicts this association as being by way of an integrated circuit card4(e.g., a subscriber identity module, SIM) that is configured to be removably inserted into or embedded or integrated in the communication device2. This integrated circuit card4stores in memory a subscription identifier10S that identifies the subscription to communication network10. The subscription identifier10S may for example be an International Mobile Subscriber Identity (IMSI), a Network Access Identifier (NAI), or any other type of Subscription Permanent Identifier (SUPI). The integrated circuit card4may also store credentials (e.g., one or more keys) associated with the subscription identifier10S. In other embodiments not shown, though, the subscription identifier10S and any associated credentials may be stored directly on the communication device2itself, e.g., on mobile equipment (ME)6. Regardless of how the subscription identifier10S is associated with the communication device2, the communication device2may indicate the subscription identifier10S to communication network10as part of a procedure to register with and/or authenticate itself to the communication network10, e.g., as a prerequisite to being provided communication service from the communication network10.

As shown inFIG.1, though, the communication device2does not necessarily access communication network10directly. Instead, the communication device2accesses communication network10via intermediate communication networks20and30. Intermediate communication networks20,30are different from one another and different from communication network10, e.g., in the sense that the networks10,20, and30have different operators and/or use different communication technologies. In any event, as shown, the intermediate communication networks20and30form a chain of networks via which the communication device2accesses communication network10.

In some embodiments, for example, communication network20shares its radio access network (RAN) with communication network10so as to provide radio access to subscribers of communication network10. And communication network20may in turn have a direct roaming partnership with communication network30, so that communication device2may roam to communication network30and access communication network20via communication network30. In this case, even though communication network30does not have a direct roaming partnership with communication network10, the communication device2is still able to access communication network10via communication network30by way of the roaming partnership between communication network20and communication network30.

In these and other embodiments, then, the path15that control signaling takes between the communication device2and communication network10traverses intermediate communication networks20and30. For example, control signaling for registering with and/or authenticating to communication network10traverses intermediate communication networks20and30on the path15between the communication device2and communication network10. The path15may thereby represent the end-to-end connection between the communication device2and communication network10.

In this context, some embodiments herein inform communication network10about any intermediate communication network(s)20,30that are in the control signaling path15between the communication device2and communication network10. One or more embodiments, for example, inform communication network10about the existence of and/or identity of one or more of the intermediate communication networks20and30. Accordingly, rather than being ignorant of whether the communication device2accesses communication network10via an intermediate network (e.g., because the communication network10does not have a direct roaming partnership with that intermediate network), communication network10is equipped with information about such an intermediate network. Communication network10can then use this information for any number of policy decisions, e.g., whether to permit access via an intermediate network, whether to permit a certain service when accessed via an intermediate network, how to treat a session of the communication device, etc. Some embodiments thereby safeguard the communication network's ability to control whether and/or which intermediate network(s) are usable to access the communication network10, even when the communication devices2access the communication network10via an intermediate network that does not have a direct roaming partnership with the communication network10.

More particularly,FIG.1shows that communication network20transmits intermediate network information40to communication network10. This intermediate network information40indicates communication network30is in the control signaling path15between the communication device2and communication network10. That is, the intermediate network information40indicates control signaling between the communication device2and communication network10passes through communication network30.

In some embodiments, for example, the intermediate network information40includes network identifying information42as shown. The network identifying information42indicates at least a portion of the identity or name of communication network30. The network identifying information42thereby actually identifies which communication network (namely, communication network30) is in the control signaling path15. The network identifying information42may for instance indicate at least a portion of a Serving Network Name (SNN) which identifies communication network30. Or, the network identifying information42may indicate a Mobile Network Code (MNC) and/or Mobile Country Code (MCC) associated with communication network30.

In other embodiments, the intermediate network information40simply indicates the existence of some unidentified intermediate communication network in the control signaling path15. In this case, for instance, the intermediate network information40may indicate communication network30is in the control signaling path15, without indicating any portion of the identity or name of communication network30. In these and other embodiments, for example, the intermediate network information40may just be a binary flag that indicates whether or not some intermediate communication network is in the control signaling path15. And, based on communication network30being in the control signaling path15, that flag may be set to indicate that indeed some intermediate communication network is in the control signaling path15. As another example, the intermediate network information40may indicate that the communication device2is roaming or that the communication device2is served by a visited communication network, i.e., a roaming partner of communication network20. As still another example, the intermediate network information40may indicate that such a visited communication network of the communication device2is in the control signaling path15.

Of course, the intermediate network information40may similarly also indicate communication network20as being in the control signaling path15, e.g., in the same way(s) as described above with respect to communication network30. In this case, then, the intermediate network information40indicates multiple communication networks20,30are in the control signaling path15.

No matter the particular nature of the intermediate network information40, though, communication network20in some embodiments transmits the intermediate network information40to communication network10along with, included in, and/or otherwise in association with other control signaling (e.g., an authentication request) that the communication network20transmits to communication network10. In one or more embodiments, for example, communication network20receives control signaling (e.g., an authentication request) from communication network30that prompts communication network20to transmit the same or different control signaling (e.g., a corresponding authentication request) to communication network10. In this case, communication equipment20may transmit intermediate network information40within or in association with the control signaling to communication network10.

Consider an example communication network10is a non-public network (NPN), whereas communication networks20and30are each a public network. An NPN as used herein is a network intended for non-public use. An NPN may for example be a network that is at least partly private. An NPN may thereby have one or more parts in an isolated network deployment that does not interact with a public network. At least one or more parts of an NPN may for example be operated by a private network operator which only allows certain pre-registered clients to attach to it. In some embodiments, though, some network functionality may be provided by a public network operator. For example, some network functionality, such as radio access and/or the control plane, may be provided by a public network operator, e.g., as a service for the private network operator.

As a particular concrete use case, an NPN may be a so-called standalone NPN (SNPN). In some embodiments, all functionality of the SNPN is provided by a private network operator. In other embodiments, all functionality of the SNPN except for radio access is provided by a private network operator, with radio access being provided by (e.g., shared with) a public network operator. The public network in this case may advertise a so-called network identifier (NID) of the NPN over the radio interface, so that communication devices can discover the NID and know that the NPN can be accessed via the public network. In some embodiments, globally unique NIDs identify different NPNs, whereas in other embodiments different combinations of PLMN IDs and NIDs identify different NPNs. An SNPN in either case may for example be a smart factory network that uses an intermediate private or public 5G network for radio access.

Regardless, in embodiments where communication network10is an NPN10, communication network20may be a public network that provides an access network for communication network10, e.g., according to a business agreement between the communication network operators. Communication network20may in this case be referred to as a home public network20(e.g., home public land mobile network, HPLMN) of the communication device2, with respect to the NPN10. The home public network20may in some cases even advertise, over at least a part of its coverage area, an NID of the NPN10. In one or more of these embodiments, the communication device2may be preconfigured with information about the home public network20, e.g., PLMN ID. The communication device2may in this case be configured to scan for the home public network20, based on the understanding that the home public network20provides radio access for the NPN10. When the communication device2discovers the home public network20, in conjunction with the NID being advertised by the home public network20, the communication device2can attempt to access the NPN10via the home public network20. For example, the communication device2can perform a procedure to register with and/or authenticate itself to the NPN10, via the home public network20. This procedure may involve transmitting the subscription identifier10S, or a concealed version thereof, to the home public network20.

Notably,FIG.1also shows that embodiments herein enable the communication device2to access, register with, and/or authenticate to the NPN10even when roaming away from the home public network20.FIG.1in this regard shows that the communication network30may be another public network that is a roaming partner of the home public network20, e.g., according to a business agreement. Communication network30is therefore referred to as a visited public network30. This visited public network30may provide radio access to the communication device2when the communication device2is outside of the geographical area(s) within which the home public network20provides radio coverage and/or advertises the NID of the NPN10. Indeed, the communication device2according to some embodiments may scan not only for the home public network20, but also scan for the visited public network30. The visited public network30may for example be included in a list at the communication device2that indicates one or more allowed visited networks, e.g., that are each a roaming partner of the home public network20. That is, the communication device2may be preconfigured with information about the roaming partner(s) of the home public network20. If the communication device2discovers the visited public network30, the communication device2may register with and/or authenticate with the NPN10via the home public network20and the visited public network30. In this case, then, the authentication procedure between the communication device2and the NPN2is performed through both the home public network20and the visited public network30.

In the context of this example, the home public network20transmits the intermediate network information40to the NPN10in order to indicate to the NPN10that a visited public network30is in the control plane path15between the communication device2and the NPN10. The intermediate network information40may thereby indicate to the NPN10the existence of and/or identity of the visited public network30used by the communication device2. The intermediate network information40in some embodiments may also indicate to the NPN10the existence of and/or identity of the home public network20used by the communication device. Based on this intermediate network information40, the NPN10can implement policy-based decisions on how to treat a session of the communication device2, e.g., from a security perspective. The intermediate network information40therefore enables the NPN10to more precisely understand the communication setup for the communication device's session and correspondingly have a more detailed security policy for that session.

FIG.2shows a call flow for an example where communication network10is an NPN, and the communication device2registers with the NPN10via the HPLMN20and VPLMN30according to some embodiments. As shown, the communication device2wants to connect to the NPN10, but cannot see the NID of the NPN10being broadcasted. But the communication device2does detect the VPLMN30, which is on a list of roaming partners of the HPLMN20for the NPN10(Step1). Accordingly, the communication device2transmits a registration request to an Access and Mobility Function (AMF) in the VPLMN30, e.g., where the registration request indicates the subscription identifier10S (or a concealed version thereof) which identifies the communication device's subscription to the NPN10(Step2).

The AMF in the VPLMN30identifies the communication device2as being a roaming subscriber of the HPLMN20. The AMF in some embodiments may be unaware that the communication device2is actually a client of the NPN10instead of the HPLMN20. The AMF in the VPLMN30correspondingly transmits a request (e.g., an authentication request) to the HPLMN20, e.g., an Authentication Server Function (AUSF) in the HPLMN20(Step3). The AUSF in the HPLMN in this case exemplifies the network node20N inFIG.1. The request includes the serving network name (SNN) of the VPLMN30via which the communication device2is requesting registration.

The HPLMN20processes the request as the HPLMN20would any other request from the VPLMN30as a roaming partner. But the HPLMN20notices that the wireless device2is a subscriber of the NPN10, meaning that primary authentication is to be performed by the NPN10. So the HPLMN20(e.g., the AUSF in the HPLMN20) transmits a request (e.g., an authentication request) to the NPN10, e.g., an AUSF in the NPN10(Step4). The request message may be similar to a Nausf UEAuthentication Authenticate Request message. Regardless, this request includes the intermediate network information40, e.g., in the form of the SNN received in the authentication request from the VPLMN30or in the form of an MCC and/or MNC associated with the VPLMN30. The HPLMN20knows to include the intermediate network information40in the request because the wireless device2is to be served by a further network, which in this case is the NPN10, e.g., such that the HPLMN20only includes the intermediate network information40in this example if the wireless device2is to be served by an NPN.

The NPN10correspondingly makes a policy-based decision based at least in part on this intermediate network information40. This decision may be made for instance by an AUSF in the NPN10, or a node that has one or more AUSF-like functions. Regardless, the policy-based decision may for example include a decision about whether or not to allow the registration and/or authentication requested by the communication device2. The NPN10may for example accept the registration or authentication only if the communication device2is not registering or authenticating via any intermediate communication network. Or, as another example, the NPN10may accept the registration or authentication if the communication device2is registering or authenticating via the HPLMN20alone but reject the registration or authentication if the communication device2is registering or authenticating also via the VPLMN30. Or, as still another example, the NPN10may accept the registration or authentication if the communication device2is registering or authenticating via the HPLMN20alone or if the communication device2is registering or authenticating via a VPLMN included in a list of one or more trusted VPLMNs, but reject the registration or authentication if the communication device2is registering or authenticating via a VPLMN not included in the list of trusted VPLMN(s). This list of trusted VPLMN(s) may for example be formulated based on reputation for security, confirmation of security measurements taken by the VPLMN(s), operator country, or the like. Generally, then, the policy-based decision may include a decision about whether the communication device2is allowed to register with the NPN10or about whether to authenticate the communication device2to the NPN10.

As another example, the policy-based decision may include a decision about which service(s) are allowed to be provided to the communication device2. The NPN10may for example limit available services based on whether or which VPLMN(s) are in the control signaling path15via which the communication device2is registering. In one such embodiment, the NPN10may implement a special network slice for a VPLMN-connected communication device, in order to keep that device's traffic isolated from other traffic and to keep the communication device from certain services in the NPN. A VPLMN-connected communication device may for instance be limited to services provided by a User Plane Function (UPF) in the NPN10, e.g., for Internet access. This may be useful to, for example, allow the communication device2to have Internet connectivity even when roaming to a VPLMN but to only allow the communication device2to have access to NPN-internal services and data when connected locally, either directly to the NPN10or indirectly via only the HPLMN20. This approach would remove the need for a second PLMN subscription in the communication device2as everything could be handled with the NPN subscription. Generally, though, the policy-based decision may include a decision about which one or more services of communication network10, communication network20, or communication30the communication device2is allowed to use and/or which one or more network slices of communication network10, communication network20, or communication30the communication device2is allowed to use.

Note, too, that any policy-based decision may be made with finer granularity, on a country by country basis for example. In one such embodiment, the decision about whether or not to allow a registration depends on a country-specific limitation. The country-specific limitation may for instance mean that the NPN10accepts a registration if the communication device2is registering via a VPLMN that is located in any of one or more allowed countries but rejects the registration if the communication device2is registering via a VPLMN that is not located in any of the one or more allowed countries. The country-specific limitation may thereby allow the NPN10to discriminate registration acceptance on the basis that different countries implement different security requirements or different data usage/storage rules.

Note further that a local policy on which the policy-based decision is made may be generally applicable to all subscriptions or communication devices, or may be specific to a certain subscription or communication device. In the latter case, a suitable policy may be included in the NPN subscriber database, i.e., for each subscription the database indicates what policy is to be applied for deciding whether to allow registration via a VPLMN. The subscriber database may for example include the policy itself in each subscription, or include a pointer to a policy in a policy database. Or, a default policy may be applied if a subscription lacks an explicit policy to be applied.

In any event,FIG.2shows that if the NPN10allows the registration request of the roaming communication device2, the procedure for authentication and registration proceeds (Step6). This may involve the NPN10responding to the registration (or authentication) request and allowing for the procedure to run its course to get the communication device2registered or authenticated. That said, even if the policy-based decision is to allow registration, the decision may further concern limitations on the allowed registration. For example, the decision may be to apply rules or restrictions on the registration, e.g., that certain services (such as Ultra Reliance Low Latency Communications, URLLC, or local breakout) are not allowed via a certain VPLMN. In such case, the rules or restrictions may be returned to the VPLMN30via the HPLMN20. Regardless, if the decision is to reject the registration, a reject reply may be returned to the communication device2via the HPLMN20and VPLMN30(not shown). The reject reply may be a currently standardized reject reply, or a new reject message may be defined which indicates that registration (or authentication) to the NPN10is not allowed via the VPLMN30.

As this example demonstrates, then, some embodiments bolster the trust that the NPN10has in the HPLMN20because the HPLMN20makes known the existence and/or identity of a VPLMN via which the communication device2registers. Alternatively or additionally, some embodiments enable the NPN10to impose different requirements for different communication devices or subscriptions with respect to how they are allowed to connect to the NPN10and/or what types of services are available to a communication device based on how that device connects to the NPN10. Alternatively or additionally, the NPN10may use the intermediate network information40to generate suitable identifiers (e.g., a Subscription Permanent Identifier, SUPI) and security key(s) during registration of the communication device2with the NPN10.

In some embodiments, the intermediate network information40may also indicate if the communication device2accesses the NPN10via a radio network node of the HPLMN20that does not advertise the NID of the NPN10. The intermediate network information40may for instance include an indication “HPLMN_NO_NID”. An example scenario is if the NID is only advertised in the location of a factory with the NPN10. In this case, if the communication device2accesses the NPN via a radio network node of the HPLMN20that is in some location other than the factory, the NPN10may have a policy that limits the service(s) that the NPN10provides to the communication device2when accessed from such location.

Note further that, although some embodiments are described above with focus on registration of the communication device2with the subscribed communication network10(e.g., NPN), registration herein may be performed (or viewed as being performed) with any of the subscribed communication network10, the intermediate communication network20, and/or the serving communication network30. Embodiments described above for registration with the subscribed communication network10may be similarly applied for registration with the intermediate communication network20and/or the serving communication network30, e.g., in terms of a policy-based decision for whether to allow such registration.

In view of the modifications and variations herein,FIG.3depicts a method performed by a first network node20N in a first communication network20in accordance with particular embodiments. The method includes transmitting, to a second network node10N in a second communication network10, information40that indicates a third communication network30is in a control signaling path15between a communication device2and the second communication network10(Block310).

In some embodiments, the information40indicates at least a portion of an identity or name of the third communication network30that is in the control signaling path15. In other embodiments, by contrast, the information40indicates a third communication network30is in the control signaling path15, without indicating any portion of an identity or name of the third communication network30. In these and other embodiments, for example, the information40may indicate a third communication network is in the control signaling path by indicate that the communication device2is roaming or that the communication device2is served by a visited communication network.

In some embodiments, the information40indicates a third communication network30is in the control signaling path15by indicating that a visited communication network of the communication device2is in the control signaling path15and/or by indicating an identity or name of the visited communication network.

FIG.3shows that the method may further comprise receiving control signaling from a third network node in the third communication network30(Block300). The control signaling may for example be an authentication request requesting authentication of a subscription of the communication device2to the second communication network10. Regardless, based on receiving the control signaling from the third network node in the third communication network30, the method may also comprise transmitting control signaling to the second network node10N (Block305). For example, the transmitted control signaling may be the same or a different authentication request requesting authentication of a subscription of the communication device to the second communication network10. In any event, in one or more of these embodiments, the information40is transmitted to the second network node10N in association with transmitting the control signaling to the second network node10N.

Although not shown, the method in some embodiments may further comprise transmitting, to the second network node10N, an authentication request requesting authentication of a subscription of the communication device2to the second communication network10. In this case, the information40may be included in the authentication request.

In some embodiments, the information40further indicates the first communication network20is in the control signaling path15between the wireless device2and the second communication network10.

In some embodiments, the second communication network10is a non-public network (NPN). In other embodiments, the second communication network10is a public network.

In some embodiments, the first communication network20is a public network and/or the third communication network30is a public network. In other embodiments, the first communication network20is a non-public network and/or the third communication network30is a non-public network.

In some embodiments, the first network node20N is an authentication server or implements an authentication server function, and/or the second network node10N is an authentication server or implements an authentication server function.

In some embodiments, the third communication network30is a roaming partner of the first communication network20, the first communication network20is a home public network of the communication device2, and wherein the third communication network is a visited network of the communication device2.

In some embodiments, the method also includes applying one or more policies based on the information40(Block320). For example, the one or more policies may include a policy that specifies, based on the information40, whether the communication device2is allowed to register with the first communication network20. Alternatively or additionally, the one or more policies may include a policy that specifies, based on the information40, which one or more services of the first communication network20, the second communication network10, and/or the third communication network30the communication device2is allowed to use and/or which one or more network slices of the first communication network20, the second communication network10, and/or the third communication network30the communication device2is allowed to use.

FIG.4depicts a method performed by a second network node10N in a second communication network10in accordance with other particular embodiments. The method includes receiving, from a first network node20N in a first communication network20, information40that indicates a third communication network30is in a control signaling path15between a communication device2and the second communication network10(Block400).

In some embodiments, the information40indicates at least a portion of an identity or name of the third communication network30that is in the control signaling path15. In other embodiments, by contrast, the information40indicates a third communication network30is in the control signaling path15, without indicating any portion of an identity or name of the third communication network30. In these and other embodiments, for example, the information40may indicates a third communication network30is in the control signaling path by indicate that the communication device2is roaming or that the communication device2is served by a visited communication network.

In some embodiments, the information40indicates a third communication network30is in the control signaling path15by indicating that a visited communication network of the communication device2is in the control signaling path15and/or by indicating an identity or name of the visited communication network.

In some embodiments, the method may comprise receiving control signaling from the first network node20N in the first communication network20, where the information40is received in association with receiving the control signaling from the first network node20N.

In some embodiments, the control signaling received from the first network node20N is an authentication request requesting authentication of a subscription of the communication device2to the second communication network10.

In some embodiments, the method further comprises receiving, from the first network node20N, an authentication request requesting authentication of a subscription of the communication device2to the second communication network10, where the information40is included in the authentication request.

In some embodiments, the information40further indicates the first communication network20is in the control signaling path15between the communication device2and the second communication network10.

In some embodiments, the second communication network10is a non-public network (NPN). In other embodiments, the second communication network10is a public network.

In some embodiments, the first communication network20is a public network and/or the third communication network30is a public network. In other embodiments, the first communication network20is a non-public network and/or the third communication network30is a non-public network.

In some embodiments, the first network node20N is an authentication server or implements an authentication server function, and/or wherein the second network node10N is an authentication server or implements an authentication server function.

In some embodiments, the third communication network30is a roaming partner of the first communication network20, the first communication network20is a home public network of the communication device2, and the third communication network30is a visited network of the communication device2.

Regardless, the method as shown may further comprise applying, based on the information40, one or more policies with respect to a subscription of the communication device2to the second communication network10(Block410). This may entail, for instance, making a policy-based decision as described herein. In any event, the one or more policies may include a policy that specifies, based on the information40, whether the communication device2is allowed to register with the second communication network10and/or whether to authenticate the subscription of the communication device2to the second communication network10. Alternatively or additionally, the one or more policies may include a policy that specifies, based on the information40, which one or more services of the first communication network20, the second communication network10, and/or the third communication network30the communication device2is allowed to use and/or which one or more network slices of the first communication network20, the second communication network10, and/or the third communication network30the communication device2is allowed to use.

Embodiments herein also include corresponding apparatuses. Embodiments herein for instance include a communication device2configured to perform any of the steps of any of the embodiments described above for the communication device2.

Embodiments also include a first network node20N comprising processing circuitry and power supply circuitry. The processing circuitry is configured to perform any of the steps of any of the embodiments described above for the first network node20N. The power supply circuitry is configured to supply power to the first network node20N.

Embodiments further include a first network node20N comprising processing circuitry. The processing circuitry is configured to perform any of the steps of any of the embodiments described above for the first network node20N. In some embodiments, the first network node20N further comprises communication circuitry.

Embodiments further include a first network node20N comprising processing circuitry and memory. The memory contains instructions executable by the processing circuitry whereby the first network node20N is configured to perform any of the steps of any of the embodiments described above for the first network node20N.

Embodiments herein also include a second network node10N configured to perform any of the steps of any of the embodiments described above for the second network node10N.

Embodiments also include a second network node10N comprising processing circuitry and power supply circuitry. The processing circuitry is configured to perform any of the steps of any of the embodiments described above for the second network node10N. The power supply circuitry is configured to supply power to the second network node10N.

Embodiments further include a second network node10N comprising processing circuitry. The processing circuitry is configured to perform any of the steps of any of the embodiments described above for the second network node10N. In some embodiments, the second network node10N further comprises communication circuitry.

Embodiments further include a second network node10N comprising processing circuitry and memory. The memory contains instructions executable by the processing circuitry whereby the second network node10N is configured to perform any of the steps of any of the embodiments described above for the second network node10N.

FIG.5for example illustrates a first network node20N as implemented in accordance with one or more embodiments. As shown, the first network node20N includes processing circuitry510and communication circuitry520. The communication circuitry520(e.g., radio circuitry) is configured to transmit and/or receive information to and/or from one or more other nodes, e.g., via any communication technology. The processing circuitry510is configured to perform processing described above, e.g., inFIG.3, such as by executing instructions stored in memory530. The processing circuitry510in this regard may implement certain functional means, units, or modules.

FIG.6illustrates a second network node10N as implemented in accordance with one or more embodiments. As shown, the second network node10N includes processing circuitry610and communication circuitry620. The communication circuitry620is configured to transmit and/or receive information to and/or from one or more other nodes, e.g., via any communication technology. The processing circuitry610is configured to perform processing described above, e.g., inFIG.4, such as by executing instructions stored in memory630. The processing circuitry610in this regard may implement certain functional means, units, or modules.

Embodiments herein may apply to any type of communication, whether wireless or wireline. When applied to wireless communication, for example, the communication device2may be a wireless communication device and one or more of the networks10,20,30may be a wireless communication network.

More particularly, although the subject matter described herein may be implemented in any appropriate type of system using any suitable components, the embodiments disclosed herein may in particular be applicable in a wireless network, such as the example wireless network illustrated inFIG.7. For simplicity, the wireless network ofFIG.7only depicts network706, network nodes760and760b, and WDs710,710b, and710c. In practice, a wireless network may further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device. Of the illustrated components, network node760and wireless device (WD)710are depicted with additional detail. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless devices' access to and/or use of the services provided by, or via, the wireless network.

InFIG.7, network node760includes processing circuitry770, device readable medium780, interface790, auxiliary equipment784, power source786, power circuitry787, and antenna762. Although network node760illustrated in the example wireless network ofFIG.7may represent a device that includes the illustrated combination of hardware components, other embodiments may comprise network nodes with different combinations of components. It is to be understood that a network node comprises any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Moreover, while the components of network node760are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, a network node may comprise multiple different physical components that make up a single illustrated component (e.g., device readable medium780may comprise multiple separate hard drives as well as multiple RAM modules).

Processing circuitry770may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node760components, such as device readable medium780, network node760functionality. For example, processing circuitry770may execute instructions stored in device readable medium780or in memory within processing circuitry770. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, processing circuitry770may include a system on a chip (SOC).

In some embodiments, processing circuitry770may include one or more of radio frequency (RF) transceiver circuitry772and baseband processing circuitry774. In some embodiments, radio frequency (RF) transceiver circuitry772and baseband processing circuitry774may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry772and baseband processing circuitry774may be on the same chip or set of chips, boards, or units

In certain embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB or other such network device may be performed by processing circuitry770executing instructions stored on device readable medium780or memory within processing circuitry770. In alternative embodiments, some or all of the functionality may be provided by processing circuitry770without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner. In any of those embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry770can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry770alone or to other components of network node760, but are enjoyed by network node760as a whole, and/or by end users and the wireless network generally.

Device readable medium780may comprise any form of volatile or non-volatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by processing circuitry770. Device readable medium780may store any suitable instructions, data or information, including a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry770and, utilized by network node760. Device readable medium780may be used to store any calculations made by processing circuitry770and/or any data received via interface790. In some embodiments, processing circuitry770and device readable medium780may be considered to be integrated.

Interface790is used in the wired or wireless communication of signalling and/or data between network node760, network706, and/or WDs710. As illustrated, interface790comprises port(s)/terminal(s)794to send and receive data, for example to and from network706over a wired connection. Interface790also includes radio front end circuitry792that may be coupled to, or in certain embodiments a part of, antenna762. Radio front end circuitry792comprises filters798and amplifiers796. Radio front end circuitry792may be connected to antenna762and processing circuitry770. Radio front end circuitry may be configured to condition signals communicated between antenna762and processing circuitry770. Radio front end circuitry792may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry792may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters798and/or amplifiers796. The radio signal may then be transmitted via antenna762. Similarly, when receiving data, antenna762may collect radio signals which are then converted into digital data by radio front end circuitry792. The digital data may be passed to processing circuitry770. In other embodiments, the interface may comprise different components and/or different combinations of components.

In certain alternative embodiments, network node760may not include separate radio front end circuitry792, instead, processing circuitry770may comprise radio front end circuitry and may be connected to antenna762without separate radio front end circuitry792. Similarly, in some embodiments, all or some of RF transceiver circuitry772may be considered a part of interface790. In still other embodiments, interface790may include one or more ports or terminals794, radio front end circuitry792, and RF transceiver circuitry772, as part of a radio unit (not shown), and interface790may communicate with baseband processing circuitry774, which is part of a digital unit (not shown).

Antenna762, interface790, and/or processing circuitry770may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by a network node. Any information, data and/or signals may be received from a wireless device, another network node and/or any other network equipment. Similarly, antenna762, interface790, and/or processing circuitry770may be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data and/or signals may be transmitted to a wireless device, another network node and/or any other network equipment.

Power circuitry787may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node760with power for performing the functionality described herein. Power circuitry787may receive power from power source786. Power source786and/or power circuitry787may be configured to provide power to the various components of network node760in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source786may either be included in, or external to, power circuitry787and/or network node760. For example, network node760may be connectable to an external power source (e.g., an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry787. As a further example, power source786may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry787. The battery may provide backup power should the external power source fail. Other types of power sources, such as photovoltaic devices, may also be used.

Alternative embodiments of network node760may include additional components beyond those shown inFIG.7that may be responsible for providing certain aspects of the network node's functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein. For example, network node760may include user interface equipment to allow input of information into network node760and to allow output of information from network node760. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node760.

As illustrated, wireless device710includes antenna711, interface714, processing circuitry720, device readable medium730, user interface equipment732, auxiliary equipment734, power source736and power circuitry737. WD710may include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD710, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, NB-IoT, or Bluetooth wireless technologies, just to mention a few. These wireless technologies may be integrated into the same or different chips or set of chips as other components within WD710.

Antenna711may include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface714. In certain alternative embodiments, antenna711may be separate from WD710and be connectable to WD710through an interface or port. Antenna711, interface714, and/or processing circuitry720may be configured to perform any receiving or transmitting operations described herein as being performed by a WD. Any information, data and/or signals may be received from a network node and/or another WD. In some embodiments, radio front end circuitry and/or antenna711may be considered an interface.

As illustrated, interface714comprises radio front end circuitry712and antenna711. Radio front end circuitry712comprise one or more filters718and amplifiers716. Radio front end circuitry714is connected to antenna711and processing circuitry720, and is configured to condition signals communicated between antenna711and processing circuitry720. Radio front end circuitry712may be coupled to or a part of antenna711. In some embodiments, WD710may not include separate radio front end circuitry712; rather, processing circuitry720may comprise radio front end circuitry and may be connected to antenna711. Similarly, in some embodiments, some or all of RF transceiver circuitry722may be considered a part of interface714. Radio front end circuitry712may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry712may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters718and/or amplifiers716. The radio signal may then be transmitted via antenna711. Similarly, when receiving data, antenna711may collect radio signals which are then converted into digital data by radio front end circuitry712. The digital data may be passed to processing circuitry720. In other embodiments, the interface may comprise different components and/or different combinations of components.

Processing circuitry720may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and/or encoded logic operable to provide, either alone or in conjunction with other WD710components, such as device readable medium730, WD710functionality. Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry720may execute instructions stored in device readable medium730or in memory within processing circuitry720to provide the functionality disclosed herein.

As illustrated, processing circuitry720includes one or more of RF transceiver circuitry722, baseband processing circuitry724, and application processing circuitry726. In other embodiments, the processing circuitry may comprise different components and/or different combinations of components. In certain embodiments processing circuitry720of WD710may comprise a SOC. In some embodiments, RF transceiver circuitry722, baseband processing circuitry724, and application processing circuitry726may be on separate chips or sets of chips. In alternative embodiments, part or all of baseband processing circuitry724and application processing circuitry726may be combined into one chip or set of chips, and RF transceiver circuitry722may be on a separate chip or set of chips. In still alternative embodiments, part or all of RF transceiver circuitry722and baseband processing circuitry724may be on the same chip or set of chips, and application processing circuitry726may be on a separate chip or set of chips. In yet other alternative embodiments, part or all of RF transceiver circuitry722, baseband processing circuitry724, and application processing circuitry726may be combined in the same chip or set of chips. In some embodiments, RF transceiver circuitry722may be a part of interface714. RF transceiver circuitry722may condition RF signals for processing circuitry720.

Processing circuitry720may be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being performed by a WD. These operations, as performed by processing circuitry720, may include processing information obtained by processing circuitry720by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD710, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.

Device readable medium730may be operable to store a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry720. Device readable medium730may include computer memory (e.g., Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (e.g., a hard disk), removable storage media (e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer executable memory devices that store information, data, and/or instructions that may be used by processing circuitry720. In some embodiments, processing circuitry720and device readable medium730may be considered to be integrated.

User interface equipment732may provide components that allow for a human user to interact with WD710. Such interaction may be of many forms, such as visual, audial, tactile, etc. User interface equipment732may be operable to produce output to the user and to allow the user to provide input to WD710. The type of interaction may vary depending on the type of user interface equipment732installed in WD710. For example, if WD710is a smart phone, the interaction may be via a touch screen; if WD710is a smart meter, the interaction may be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected). User interface equipment732may include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment732is configured to allow input of information into WD710, and is connected to processing circuitry720to allow processing circuitry720to process the input information. User interface equipment732may include, for example, a microphone, a proximity or other sensor, keys/buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface equipment732is also configured to allow output of information from WD710, and to allow processing circuitry720to output information from WD710. User interface equipment732may include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits, of user interface equipment732, WD710may communicate with end users and/or the wireless network, and allow them to benefit from the functionality described herein.

Auxiliary equipment734is operable to provide more specific functionality which may not be generally performed by WDs. This may comprise specialized sensors for doing measurements for various purposes, interfaces for additional types of communication such as wired communications etc. The inclusion and type of components of auxiliary equipment734may vary depending on the embodiment and/or scenario.

Power source736may, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic devices or power cells, may also be used. WD710may further comprise power circuitry737for delivering power from power source736to the various parts of WD710which need power from power source736to carry out any functionality described or indicated herein. Power circuitry737may in certain embodiments comprise power management circuitry. Power circuitry737may additionally or alternatively be operable to receive power from an external power source; in which case WD710may be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical power cable. Power circuitry737may also in certain embodiments be operable to deliver power from an external power source to power source736. This may be, for example, for the charging of power source736. Power circuitry737may perform any formatting, converting, or other modification to the power from power source736to make the power suitable for the respective components of WD710to which power is supplied.

InFIG.8, UE800includes processing circuitry801that is operatively coupled to input/output interface805, radio frequency (RF) interface809, network connection interface811, memory815including random access memory (RAM)817, read-only memory (ROM)819, and storage medium821or the like, communication subsystem831, power source833, and/or any other component, or any combination thereof. Storage medium821includes operating system823, application program825, and data827. In other embodiments, storage medium821may include other similar types of information. Certain UEs may utilize all of the components shown inFIG.8, or only a subset of the components. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

InFIG.8, RF interface809may be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna. Network connection interface811may be configured to provide a communication interface to network843a. Network843amay encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network843amay comprise a Wi-Fi network. Network connection interface811may be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, TCP/IP, SONET, ATM, or the like. Network connection interface811may implement receiver and transmitter functionality appropriate to the communication network links (e.g., optical, electrical, and the like). The transmitter and receiver functions may share circuit components, software or firmware, or alternatively may be implemented separately.

RAM817may be configured to interface via bus802to processing circuitry801to provide storage or caching of data or computer instructions during the execution of software programs such as the operating system, application programs, and device drivers. ROM819may be configured to provide computer instructions or data to processing circuitry801. For example, ROM819may be configured to store invariant low-level system code or data for basic system functions such as basic input and output (I/O), startup, or reception of keystrokes from a keyboard that are stored in a non-volatile memory. Storage medium821may be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives. In one example, storage medium821may be configured to include operating system823, application program825such as a web browser application, a widget or gadget engine or another application, and data file827. Storage medium821may store, for use by UE800, any of a variety of various operating systems or combinations of operating systems.

InFIG.8, processing circuitry801may be configured to communicate with network843busing communication subsystem831. Network843aand network843bmay be the same network or networks or different network or networks. Communication subsystem831may be configured to include one or more transceivers used to communicate with network843b. For example, communication subsystem831may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another WD, UE, or base station of a radio access network (RAN) according to one or more communication protocols, such as IEEE 802.11, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like. Each transceiver may include transmitter833and/or receiver835to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter833and receiver835of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately.

The features, benefits and/or functions described herein may be implemented in one of the components of UE800or partitioned across multiple components of UE800. Further, the features, benefits, and/or functions described herein may be implemented in any combination of hardware, software or firmware. In one example, communication subsystem831may be configured to include any of the components described herein. Further, processing circuitry801may be configured to communicate with any of such components over bus802. In another example, any of such components may be represented by program instructions stored in memory that when executed by processing circuitry801perform the corresponding functions described herein. In another example, the functionality of any of such components may be partitioned between processing circuitry801and communication subsystem831. In another example, the non-computationally intensive functions of any of such components may be implemented in software or firmware and the computationally intensive functions may be implemented in hardware.

In some embodiments, some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments900hosted by one or more of hardware nodes930. Further, in embodiments in which the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), then the network node may be entirely virtualized.

The functions may be implemented by one or more applications920(which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operative to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein. Applications920are run in virtualization environment900which provides hardware930comprising processing circuitry960and memory990. Memory990contains instructions995executable by processing circuitry960whereby application920is operative to provide one or more of the features, benefits, and/or functions disclosed herein.

Virtualization environment900, comprises general-purpose or special-purpose network hardware devices930comprising a set of one or more processors or processing circuitry960, which may be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors. Each hardware device may comprise memory990-1which may be non-persistent memory for temporarily storing instructions995or software executed by processing circuitry960. Each hardware device may comprise one or more network interface controllers (NICs)970, also known as network interface cards, which include physical network interface980. Each hardware device may also include non-transitory, persistent, machine-readable storage media990-2having stored therein software995and/or instructions executable by processing circuitry960. Software995may include any type of software including software for instantiating one or more virtualization layers950(also referred to as hypervisors), software to execute virtual machines940as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.

Virtual machines940, comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer950or hypervisor. Different embodiments of the instance of virtual appliance920may be implemented on one or more of virtual machines940, and the implementations may be made in different ways.

During operation, processing circuitry960executes software995to instantiate the hypervisor or virtualization layer950, which may sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer950may present a virtual operating platform that appears like networking hardware to virtual machine940.

As shown inFIG.9, hardware930may be a standalone network node with generic or specific components. Hardware930may comprise antenna9225and may implement some functions via virtualization. Alternatively, hardware930may be part of a larger cluster of hardware (e.g. such as in a data center or customer premise equipment (CPE)) where many hardware nodes work together and are managed via management and orchestration (MANO)9100, which, among others, oversees lifecycle management of applications920.

In the context of NFV, virtual machine940may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of virtual machines940, and that part of hardware930that executes that virtual machine, be it hardware dedicated to that virtual machine and/or hardware shared by that virtual machine with others of the virtual machines940, forms a separate virtual network elements (VNE).

Still in the context of NFV, Virtual Network Function (VNF) is responsible for handling specific network functions that run in one or more virtual machines940on top of hardware networking infrastructure930and corresponds to application920inFIG.9.

In some embodiments, one or more radio units9200that each include one or more transmitters9220and one or more receivers9210may be coupled to one or more antennas9225. Radio units9200may communicate directly with hardware nodes930via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.

In some embodiments, some signalling can be effected with the use of control system9230which may alternatively be used for communication between the hardware nodes930and radio units9200.

FIG.10illustrates a telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments. In particular, with reference toFIG.10, in accordance with an embodiment, a communication system includes telecommunication network1010, such as a 3GPP-type cellular network, which comprises access network1011, such as a radio access network, and core network1014. Access network1011comprises a plurality of base stations1012a,1012b,1012c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area1013a,1013b,1013c. Each base station1012a,1012b,1012cis connectable to core network1014over a wired or wireless connection1015. A first UE1091located in coverage area1013cis configured to wirelessly connect to, or be paged by, the corresponding base station1012c. A second UE1092in coverage area1013ais wirelessly connectable to the corresponding base station1012a. While a plurality of UEs1091,1092are 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 station1012.

Telecommunication network1010is itself connected to host computer1030, 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. Host computer1030may 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. Connections1021and1022between telecommunication network1010and host computer1030may extend directly from core network1014to host computer1030or may go via an optional intermediate network1020. Intermediate network1020may be one of, or a combination of more than one of, a public, private or hosted network; intermediate network1020, if any, may be a backbone network or the Internet; in particular, intermediate network1020may comprise two or more sub-networks (not shown).

The communication system ofFIG.10as a whole enables connectivity between the connected UEs1091,1092and host computer1030. The connectivity may be described as an over-the-top (OTT) connection1050. Host computer1030and the connected UEs1091,1092are configured to communicate data and/or signaling via OTT connection1050, using access network1011, core network1014, any intermediate network1020and possible further infrastructure (not shown) as intermediaries. OTT connection1050may be transparent in the sense that the participating communication devices through which OTT connection1050passes are unaware of routing of uplink and downlink communications. For example, base station1012may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer1030to be forwarded (e.g., handed over) to a connected UE1091. Similarly, base station1012need not be aware of the future routing of an outgoing uplink communication originating from the UE1091towards the host computer1030.

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 toFIG.11.FIG.11illustrates host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments In communication system1100, host computer1110comprises hardware1115including communication interface1116configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system1100. Host computer1110further comprises processing circuitry1118, which may have storage and/or processing capabilities. In particular, processing circuitry1118may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Host computer1110further comprises software1111, which is stored in or accessible by host computer1110and executable by processing circuitry1118. Software1111includes host application1112. Host application1112may be operable to provide a service to a remote user, such as UE1130connecting via OTT connection1150terminating at UE1130and host computer1110. In providing the service to the remote user, host application1112may provide user data which is transmitted using OTT connection1150.

Communication system1100further includes base station1120provided in a telecommunication system and comprising hardware1125enabling it to communicate with host computer1110and with UE1130. Hardware1125may include communication interface1126for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system1100, as well as radio interface1127for setting up and maintaining at least wireless connection1170with UE1130located in a coverage area (not shown inFIG.11) served by base station1120. Communication interface1126may be configured to facilitate connection1160to host computer1110. Connection1160may be direct or it may pass through a core network (not shown inFIG.11) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, hardware1125of base station1120further includes processing circuitry1128, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Base station1120further has software1121stored internally or accessible via an external connection.

Communication system1100further includes UE1130already referred to. Its hardware1135may include radio interface1137configured to set up and maintain wireless connection1170with a base station serving a coverage area in which UE1130is currently located. Hardware1135of UE1130further includes processing circuitry1138, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. UE1130further comprises software1131, which is stored in or accessible by UE1130and executable by processing circuitry1138. Software1131includes client application1132. Client application1132may be operable to provide a service to a human or non-human user via UE1130, with the support of host computer1110. In host computer1110, an executing host application1112may communicate with the executing client application1132via OTT connection1150terminating at UE1130and host computer1110. In providing the service to the user, client application1132may receive request data from host application1112and provide user data in response to the request data. OTT connection1150may transfer both the request data and the user data. Client application1132may interact with the user to generate the user data that it provides.

It is noted that host computer1110, base station1120and UE1130illustrated inFIG.11may be similar or identical to host computer1030, one of base stations1012a,1012b,1012cand one of UEs1091,1092ofFIG.10, respectively. This is to say, the inner workings of these entities may be as shown inFIG.11and independently, the surrounding network topology may be that ofFIG.10.

InFIG.11, OTT connection1150has been drawn abstractly to illustrate the communication between host computer1110and UE1130via base station1120, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure may determine the routing, which it may be configured to hide from UE1130or from the service provider operating host computer1110, or both. While OTT connection1150is 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).

Wireless connection1170between UE1130and base station1120is 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 UE1130using OTT connection1150, in which wireless connection1170forms the last segment.

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 OTT connection1150between host computer1110and UE1130, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring OTT connection1150may be implemented in software1111and hardware1115of host computer1110or in software1131and hardware1135of UE1130, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which OTT connection1150passes; 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 software1111,1131may compute or estimate the monitored quantities. The reconfiguring of OTT connection1150may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect base station1120, and it may be unknown or imperceptible to base station1120. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling facilitating host computer1110's measurements of throughput, propagation times, latency and the like. The measurements may be implemented in that software1111and1131causes messages to be transmitted, in particular empty or ‘dummy’ messages, using OTT connection1150while it monitors propagation times, errors etc.

FIG.12is 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 toFIGS.10and11. For simplicity of the present disclosure, only drawing references toFIG.12will be included in this section. In step1210, the host computer provides user data. In substep1211(which may be optional) of step1210, the host computer provides the user data by executing a host application. In step1220, the host computer initiates a transmission carrying the user data to the UE. In step1230(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 step1240(which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

In view of the above, then, embodiments herein generally include a communication system including a host computer. The host computer may comprise processing circuitry configured to provide user data. The host computer may also comprise a communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE). The cellular network may comprise a base station having a radio interface and processing circuitry, the base station's processing circuitry configured to perform any of the steps of any of the embodiments described above for a base station.

In some embodiments, the communication system further includes the base station.

In some embodiments, the communication system further includes the UE, wherein the UE is configured to communicate with the base station.

In some embodiments, the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data. In this case, the UE comprises processing circuitry configured to execute a client application associated with the host application.

Embodiments herein also include a method implemented in a communication system including a host computer, a base station and a user equipment (UE). The method comprises, at the host computer, providing user data. The method may also comprise, at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station. The base station performs any of the steps of any of the embodiments described above for a base station.

In some embodiments, the method further comprising, at the base station, transmitting the user data.

In some embodiments, the user data is provided at the host computer by executing a host application. In this case, the method further comprises, at the UE, executing a client application associated with the host application.

Embodiments herein also include a user equipment (UE) configured to communicate with a base station. The UE comprises a radio interface and processing circuitry configured to perform any of the embodiments above described for a UE.

Embodiments herein further include a communication system including a host computer. The host computer comprises 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). The UE comprises a radio interface and processing circuitry. The UE's components are configured to perform any of the steps of any of the embodiments described above for a UE.

In some embodiments, the cellular network further includes a base station configured to communicate with the UE.

In some embodiments, the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data. The UE's processing circuitry is configured to execute a client application associated with the host application.

Embodiments also include a method implemented in a communication system including a host computer, a base station and a user equipment (UE). The method comprises, at the host computer, providing user data and initiating a transmission carrying the user data to the UE via a cellular network comprising the base station. The UE performs any of the steps of any of the embodiments described above for a UE.

In some embodiments, the method further comprises, at the UE, receiving the user data from the base station.

Embodiments herein further include a communication system including a host computer. The host computer comprises a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station. The UE comprises a radio interface and processing circuitry. The UE's processing circuitry is configured to perform any of the steps of any of the embodiments described above for a UE.

In some embodiments the communication system further includes the UE.

In some embodiments, the communication system further including the base station. In this case, the base station 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.

Embodiments herein also include a method implemented in a communication system including a host computer, a base station and a user equipment (UE). The method comprises, at the host computer, receiving user data transmitted to the base station from the UE. The UE performs any of the steps of any of the embodiments described above for the UE.

In some embodiments, the method further comprises, at the UE, providing the user data to the base station.

In some embodiments, the method also comprises, at the UE, executing a client application, thereby providing the user data to be transmitted. The method may further comprise, at the host computer, executing a host application associated with the client application.

In some embodiments, the method further comprises, at the UE, executing a client application, and, at the UE, receiving input data to the client application. The input data is provided at the host computer by executing a host application associated with the client application. The user data to be transmitted is provided by the client application in response to the input data.

Embodiments also include a communication system including a host computer. The host computer comprises a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station. The base station comprises a radio interface and processing circuitry. The base station's processing circuitry is configured to perform any of the steps of any of the embodiments described above for a base station.

In some embodiments, the communication system further includes the base station.

In some embodiments, the communication system further includes the UE. The UE is configured to communicate with the base station.

Embodiments moreover include a method implemented in a communication system including a host computer, a base station and a user equipment (UE). The method comprises, at the host computer, receiving, from the base station, user data originating from a transmission which the base station has received from the UE. The UE performs any of the steps of any of the embodiments described above for a UE.

In some embodiments, the method further comprises, at the base station, receiving the user data from the UE.

In some embodiments, the method further comprises, at the base station, initiating a transmission of the received user data to the host computer.

The term “A and/or B” as used herein covers embodiments having A alone, B alone, or both A and B together. The term “A and/or B” may therefore equivalently mean “at least one of any one or more of A and B”.