System for controlled access to public communication networks
A neutral host network using shared spectrum and a dedicated NH core with HSS/UDM provides secure and cost-effective roaming with priority access for critical users, addressing inefficiencies in MNO architectures.
Patent Information
- Application Number
- PCT/IB2025/054688
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-05-05
- Publication Date
- 2026-11-12
AI Technical Summary
Current MNO architectures face challenges such as high cost due to individual BBUs, lack of control over shared spectrum usage, inability to secure highest priority on spectrum, and lack of local network access control, especially with shared spectrum solutions like CBRS, and inferior performance of WiFi-based systems.
Implementing a neutral host network that uses shared spectrum like CBRS, with a dedicated NH core and HSS/UDM for secure roaming, allowing priority access for first responders and controlling device access based on SIM ID, and providing QoS management for priority users.
This solution enables cost-effective sharing of RAN hardware, secures network access, and ensures priority QoS for critical users, while preventing unauthorized access and enhancing network control.
Smart Images

Figure IB2025054688_12112026_PF_FP_ABST
Abstract
Description
SYSTEM FOR CONTROLLED ACCESS TO PUBLIC COMMUNICATION NETWORKSTECHNICAL FIELD
[0001] The present disclosure generally relates to systems and methods for supporting roaming between a private network and one or more public networks.BACKGROUND
[0002] Currently PSTN operators, mobile network operators (MNO), often share RAN (Radio Access Network) equipment and have individual access for their subscribers using their standard public land mobile network (PLMN) ID, (MORAN (Multi-Operator Radio Access Network) and MOCN (Multi-Operator Core Network)solutions). In some countries, this implies each MNO deploys their own baseband, (RAN Compute, BBU (baseband unit)), and then connect to their own core network for call processing. This architecture allows any user equipment with the right SIM provisioning to access their network.
[0003] In each case, an MNO often uses their own spectrum. This often works for first responders as the MNOs have full control of the traffic use of their spectrums. However, if shared spectrum is used, such as CBRS (Citizens Broadband Radio Service), then the MNO often has no control over the total spectrum use when sharing with other MNOs.SUMMARY
[0004] One embodiment under the present disclosure comprises a method for supporting roaming between a Private Network and one or more Public Networks. The method comprises: receiving, from a private network node in a private network, a PLMN ID for each of one or more public networks; sending, by the wireless device, a registration request to the private network node, wherein the private network node forwards the registration request to an appropriate one of the one or more public networks, and wherein the appropriate one of the one or more public networks performs authentication of the registration request; and receiving, from the private network node, an initiation of a secure session if the authentication is successful.
[0005] Another embodiment of a method under the present disclosure is a method for supporting roaming between a wireless device and one or more public networks. The method comprises: broadcasting, by the private network node, a PLMN ID for each of one or more public networks; receiving, from the wireless device, a registration request for one of the one or more public networks; forwarding, by the private network node, the registration request to an appropriate public network of the one or more public networks so that the appropriate public network can perform authentication of the wireless device; if the wireless device is authenticated, then receiving an initiation of a secure session between the private network node and the public network; and enabling, by the private network node, the wireless device to consume services from the appropriate public network.
[0006] Another embodiment comprises a neutral host for supporting roaming between a private network and one or more public networks. The neutral host comprises: processing circuitry and a memory. The memory contains instructions executable by the processing circuitry whereby the system / apparatus is operative to: broadcast, by a private network node, a PLMN ID for each of one or more public networks; receive, by the private network node, a registration request for one of the one or more public networks; forward, by the private network node, the registration request to an appropriate public network of the one or more public networks so that the appropriate public network can perform authentication of a wireless device; if the wireless device is authenticated, then receive an initiation of a secure session between the private network node and the public network; and enable, by the private network node, the network node to consume services from the appropriate public network.
[0007] This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the detailed description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an indication of the scope of the claimed subject matter.BRIEF DESCRIPTION OF THE DRAWINGS
[0008] For a more complete understanding of the present disclosure, reference is now made to the following descriptions taken in conjunction with the accompanying drawings, in which:
[0009] Fig. 1 illustrates an example MOCN architecture with shared spectrum and access control;
[0010] Fig. 2 illustrates a method of this call flow which may include registration with AMF reallocation;
[0011] Fig. 3 illustrates a purpose of a SEPP, if SEPP is used as part of the method;
[0012] Fig. 4 illustrates a method, performed by a wireless device, for supporting roaming between a Private Network and one or more Public Networks;
[0013] Fig. 5 illustrates a method performed by a private network node for supporting roaming between a wireless device and one or more public networks;
[0014] Fig. 6 illustrates an example of a communication system in accordance with some embodiments;
[0015] Fig. 7 illustrates another example of a communication system according to some embodiments; and
[0016] Fig. 8 illustrates an embodiment of a wireless device in accordance with some embodiments;
[0017] Fig. 9 illustrates an embodiment of a network node in accordance with some embodiments; and
[0018] Fig. 10 illustrates an embodiment of a virtualization environment in accordance with some embodiments.DETAILED DESCRIPTION
[0019] Before describing various embodiments of the present disclosure in detail, it is to be understood that this disclosure is not limited to the parameters of the particularly exemplified systems, methods, apparatus, products, processes, and / or kits, which may, of course, vary. Thus, while certain embodiments of the present disclosure will be described in detail, with reference to specific configurations, parameters, components, elements, etc., the descriptions are illustrative and are not to be construed as limiting the scope of the claimed embodiments. In addition, the terminology used herein is for the purpose of describing the embodiments and is not necessarily intended to limit the scope of the claimed embodiments.
[0020] There currently exist certain challenge(s) which may include deploying one BBU per MNO causing poor cost efficiency compared to sharing the hardware; lack of ability tosecure highest priority on spectrum across all MNOs with shared spectrum; lack of local control of access to network, i.e. any rogue device can access the network with a SIM card; inferior performance of comparative WiFi-based solutions; and / or higher system cost for proprietary solutions, i.e. walkie-talkie solution.
[0021] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. These solutions may include creating a low-cost neutral host network for ROAMing traffic to regular public operators and controlling device access to the network per SIM id; and / or a separate neutral host (NH) which may use shared spectrum, like CBRS, which may use an NH host core and then roam to an appropriate MNO core which may allow traffic for devices / subscribers. In addition, solutions may include an access control function that can selectively allow access to a network or not based on the subscriber identity and / or SIM card. In some embodiments, all traffic may use the same NH core, while priority users, which may include first responders and / or other priority users, can have priority access over other subscribers across MNOs. Furthermore, the NH core can report a location and / or an identity of potential rogue devices that may try to access the network. Other solutions may include using 3 GPP ROAMing from a dedicated NH Core with HSS / UDM (Home Subscriber Server / Unified Data Management) which may be provisioned with approved devices; a neutral host controlled quality of service (QoS) for priority users to manage other traffic with lower priority; and / or an access controller that can provision NH HSS / UDM per device giving access. Some Private Network Operators may wish to restrict roaming on their network to employees, specific visitors, and / or other controlled groups to prevent global access to their RAN by all roaming partner network customers. Current Neutral Host solutions to not provide a mechanism to do this.
[0022] Certain embodiments may provide one or more of the following technical advantage(s). These advantages may include the ability to share a reduced RAN hardware & software capital expenditure across MNOs, which may drive down the cost of the solution. Some embodiments may provide the ability to control who can access the network using provisioning on the HSS / UDM, which may prevent rogue devices from obtaining access. For example, in a prison or other location with a sensitive network, a network controller may be able to prevent unauthorized devices from accessing the network. Other technical advantages may include an ability to secure a proper QoS for priority devices in a shared spectrum scenario, which may be mandatory for first responders.
[0023] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.
[0024] Turning to Fig. 1 , an example MOCN architecture 100 with shared spectrum and access control is illustrated. Each of the one or more MNOs 102 may be a ROAMing partner to a neutral host (NH) 108. ROAMing may be a standard 3 GPP function and may be made more secure using Security Edge Protection Proxy (SEPP). In some embodiments, SEPP may not be used. A new device management function 112 may provision a database with approved device identities and / or SIM card, and may block all other devices, which may include a rogue device 106. The PLMN that may be transmitted may be NH PLMN 114. All interfaces may be according to the 3GPP relevant specifications. Any device (user equipment, UE) 104 entering the system may listen for the NH PLMN 114 and then attempt to register. An NH Core network may evaluate if the UE 104 may be allowed to access the network 110, and if allowed, may ROAM the traffic to the respective MNO core for further processing.
[0025] In some embodiments, in case of an emergency situation, priority devices, like a first responder’s device and / or other priority device, may use 3 GPP QoS attributes to request priority. The NH Core can allow such priority, across all MNO. All other traffic can be preempted and managed to secure access for the priority devices.
[0026] In some embodiments, a visited public land mobile network (vPLMN) of a private network may broadcast one or more PLMN IDs for each public network supported (i.e. AT&T, T Mobile, Verizon Wireless). A call flow may then ensue to enable a user to attach to, and consume services from, a public network operator via the private network. Fig. 2 illustrates a method 200 of this call flow which may include registration with AMF reallocation. This call flow may support user devices that have migrated outside of their public network operator’s coverage footprint. This migration may be due to domestic or international travel and may be common when devices from regional carriers (i.e. USCC) travel to other states where the regional carrier may not operate. In these cases, the regional carriers may have roaming agreements with larger carriers to support their customers.
[0027] Method 200 may enable user devices from the public networks to consume RAN resources from dedicated radio assets which may be deployed by a third party. This method 200 may be useful as, for example, an indoor coverage solution at an airport, mall, hotel, or officedeployed by building owners. Such solutions may be based on an unlicensed spectrum (i.e. CBRS in the US). The method may offer an alternative to traditional distributed antenna systems (DAS) or other neutral host multi-operator technologies which mandate the use of licensed spectrum owned by the public network operators.
[0028] Method 200 may begin by a UE sending a registration request 1 to an initial AMF. The initial AMF may then perform an Authentication Server Function (AUSF) discovery procedure 2 and select an AUSF 3. Then the network may perform authentication and security procedures 4 for the UE. Then the UDM discovery procedure 5 may begin and a UDM may be selected 6. The initial AMF may then determine if it can serve the UE 9. Then the initial AMF may perform AMF discovery and selection 12 to determine the appropriate AMF. From there, the registration procedure may continue in the chosen AMF 15.
[0029] Fig. 3 illustrates a purpose of the SEPP, if SEPP is used as part of the method 200. SEPP may be used in the roaming procedure to assess if a UE is permitted to continue the roaming procedure based on a list of authorized UEs. A registration request message may be used by a UE to identify itself to a 5G network when initiating registration. The registration request may contain the UE’s International Mobile Subscriber Identity (IMSI) or other unique identifier, such as a Temporary Mobile Subscriber Identity (TMSI) or a 5G Globally Unique Temporary Identity (5G-GUTI). However, during 5G roaming, the SUPI of a user may only be known after authentication by the Home PLMN (hPLMN = Public Network Operator). Because of this, after the hPLMN has authenticated the device, the AMF may continue normal call-flows, or reject the UE, based on the SUPI (IMSI). To do this, the AMF may be configured with a list of SUPI / IMSI of explicitly authorized devices or a list of SUPI / IMSI of explicitly unauthorized devices.
[0030] Using SEPP may provide benefits to the method 200. These benefits may include SEPP performing routing from vPLMN to hPLMN and vice versa; SEPP supporting dedicated TLS certificates for external connections; SEPP hiding network topology towards remaining partners; and / or SEPP supporting GSMA compliant signaling firewall.
[0031] Fig. 4 illustrates a method 400, performed by a wireless device, for supporting roaming between a Private Network and one or more Public Networks. First, the wireless device may receive 402, from a private network node in a private network, a public land mobile network identifier, PLMN ID, for each of one or more public networks. The wireless device may then send 404 a registration request to the private network node. The private network nodemay then forward the registration request to an appropriate one of the one or more public networks. The appropriate public network may then perform authentication of the registration request. Next, the wireless device may receive, from the private network node, an initiation 410 of a secure session if the authentication is successful. This may enable 412 the wireless device to begin consuming services from the public network.
[0032] Method 400 can comprise a variety of additional, alternative, and / or optional steps. For example, in some embodiments, the wireless device may receive a denial of service, instead of an initiation of a secure connection, if the authentication is not successful. If the wireless device is not authenticated successfully, then the private network node may log one or more details of the wireless device and connection attempt in a failed access data log. In some embodiments, identifying whether the wireless device is permitted to connect with the Public Network may be selectively enabled by a user. For example, a network operator may be able to turn on permitted connections such that all connections may be confirmed to be authorized devices or turn this off such that any device may connect to the network without authentication.
[0033] In some embodiments, after a secure connection is initiated, the wireless device may be limited to consuming services from the public network within a predetermined timeframe. For example, in the case of a federal prison, this method may prevent contraband phones from being used by inmates but allow time permitted use of phones by prison staff and registered visitors. A suite of operation, administration, and management functions may be used to allow this selective authorization. Such systems are called Contraband Interdiction Systems with this specific class being termed Managed Access Systems.
[0034] In some embodiments, identifying whether the wireless device may be permitted to connect with the Public Network may include comparing the wireless device to devices on a devices data log. The devices data log may be similar to the list of SUPI / IMSI of explicitly authorized devices or of SUPI / IMSI of explicitly unauthorized devices.
[0035] In some embodiments, the registration request may include a unique identifier. The unique identifier may be an International Mobile Subscriber Identity (IMSI), a Temporary Mobile Subscriber Identity (TMSI), a 5G Globally Unique Temporary Identity (5G-GUTI), or another identifier.
[0036] In some embodiments, the devices data log may comprise a list of unpermitted devices and associated unique identifiers.
[0037] In some embodiments, the private network may be based on an unlicensed spectrum.
[0038] Fig. 5 illustrates a method 500 performed by a private network node for supporting roaming between a wireless device and one or more public networks. First, the private network node may broadcast 502 a PLMN ID for each of one or more public networks. The private network node may then receive 504 a registration request for one of the one or more public networks from the wireless device. The private network node may then forward 506 the registration request to an appropriate one of the one or more public networks so that the appropriate public network can perform authentication 508 of the wireless device. If the wireless device is authenticated, the private network node may receive 510 an initiation of a secure session between the private network node and the public network. Then the wireless device may be enabled 512, by the private network node, to consume services from the appropriate public network.
[0039] Method 500 can comprise a variety of additional, alternative, and / or optional steps. For example, in some embodiments, if the wireless device is not authenticated, then the private network node may receive a denial of service from the appropriate public network. The private network node may also log one or more details of the network node and connection attempt in a failed access data log. In some embodiments, a user may select an option to be connected to a public network such that the network node receives an indication of such.
[0040] In some embodiments, after a secure connection is initiated, the private network node may limit the wireless device to consuming services from the public network within a predetermined timeframe. This may be similar to this predetermined timeframe described in Fig.4.
[0041] In some embodiments, identifying whether the private network node may be permitted to connect with the public network may include comparing the private network node to devices on a devices data log. The devices data log may be similar to the list of SUPI / IMSI of explicitly authorized devices or of SUPI / IMSI of explicitly unauthorized devices.
[0042] In some embodiments, the registration request may include a unique identifier. The unique identifier may be an International Mobile Subscriber Identity (IMSI), a Temporary Mobile Subscriber Identity (TMSI), a 5G Globally Unique Temporary Identity (5G-GUTI), or another identifier.
[0043] In some embodiments, user data may be collected as UEs attempt to connect to the public networks. This may be done by logging metadata, UE data, or other data. This user data may be shared with a host via transmission to the private network node.
[0044] In some embodiments, the devices data log may comprise a list of unpermitted devices and associated unique identifiers.
[0045] In some embodiments, the private network may be based on an unlicensed spectrum.
[0046] Certain embodiments can comprise non-terrestrial networks (NTNs). For example, either / both of the public and the private networks can comprise NTNs, such as satellite networks. In addition, certain embodiments can comprise NR (New Radio) over Cable, e.g., DOCSIS (Data Over Cable Service Interface Specifications). Such embodiments could comprise a private network provided by a cable operator (MSO (multiple systems operator)) which could then support roaming to public networks.
[0047] A neutral host may support roaming between a private network and one or more public networks as well. This neutral host may include processing circuitry and a memory with instructions executable by the processing circuity. These instructions may enable a system and / or apparatus to receive, by a private network node, a registration request for one of the one or more public networks; forward, by the private network node, the registration request to an appropriate public network of the one or more public networks so that the appropriate public network can perform authentication of a wireless device; if the wireless device is authenticated, then receive an initiation of a secure session between the private network node and the public network; and enable, by the private network node, the network node to consume services from the appropriate public network.Additional Embodiments
[0048] Figure 6 shows an example of a communication system 4100 in accordance with some embodiments. In the example, the communication system 4100 includes a telecommunications network 4102 that includes an access network 4104, such as a radio access network (RAN), and a core network 4106, which includes one or more core network nodes 4108. The access network 4104 includes one or more access network nodes or base stations of various types, access network nodes 4110A and 4110B are depicted (which may be collectively referredto as network nodes 4110), or any other similar 3rdGeneration Partnership Project (3GPP) access nodes or non-3GPP access points (APs). Some embodiments of the access network 4104 may include more than one access network technology. The network nodes 4110 of access network 4104 facilitate direct or indirect connection of wireless devices, also referred to as user equipments (UEs), such as by connecting UEs 4112A, 4112B, 4112C, and 4112D (one or more of which may be generally referred to as UEs 4112) to the core network 4106 over one or more wireless connections.
[0049] Moreover, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunications network 4102 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a network node in the telecommunications network 4102 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other network nodes to implement one or more functionalities of any network node in the telecommunications network 4102, including one or more access network nodes 4110 and / or core network nodes 4108.
[0050] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). An ORAN network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN network node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an O-2 interface defined by the O-RAN Alliance or comparable technologies.
[0051] The network nodes 4110 facilitate direct or indirect connection of one or more UEs 4112 to the core network 4106 over one or more wireless connections. Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 4100 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 4100 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.
[0052] The UEs 4112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes 4110 and other communication devices. Similarly, the network nodes 4108, 4110 are arranged, capable, configured, and / or operable to communicate directly or indirectly (e.g., via other devices of telecommunications network 4102) with the UEs 4112 and / or with other network nodes or equipment in the telecommunications network 4102 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunications network 4102. More specifically, UEs 4112 may send messages, data, and / or other signals to network nodes 4108, 4110 or other elements of the telecommunications network 4102 by transmitting such signals to the relevant device directly without the signals passing through any intervening devices or by transmitting such signals to the relevant device indirectly through an intervening device (or multiple intervening devices) that then transmit the signal to the relevant device. Similarly, network nodes 4108, 4110 may send messages, data, and other signals to UEs 41122, other network nodes 4108, 4110, and other devices in telecommunications network 4102 directly or indirectly. As one specific example, a core network node 108 may transmit a particular message to a UE 4112 by transmitting the message to an access network node 4110 that will then transmit the message to the intended UE 4112. Similarly, a core network node 108 may receive a particular message from a UE 4112 by receiving the message from an access network node 4110 that itself received the message from the UE 4112.
[0053] In the depicted example, the core network 4106 connects elements of the access network 4104 (e.g., one or more of the network nodes 4110) to one or more host computing systems, such as host 4116. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 4106 includes one or more core network nodes (e.g., core network node 4108) of various types, one or more of which may be generally referred to as network nodes 4108. Network nodes 4108 are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, access network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 4108. Example core network nodes provide functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).
[0054] The host 4116 may be under the ownership or control of a service provider other than an operator or provider of the access network 4104 and / or the telecommunications network 4102. The host 4116 may be operated by the service provider or on behalf of the service provider. The host 4116 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.
[0055] As a whole, the communication system 4100 of Figure 6 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system 4100 may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and ElectronicsEngineers (IEEE) 802.11 standards (Wi-Fi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (Wi-Max), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, Li-Fi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox. Moreover, the communication system 4100 may be configured to support multiple different standards, protocols, or other rule sets, with individual components supporting all of the relevant rule sets or with different components or sub-systems within the communication system 4100 supporting different standards, protocols, or rule sets.
[0056] As one example, in certain embodiments, access network 4104 may contain some access network nodes 4110 that support 3 GPP radio access technologies (RAT), such as LIE or NR, while other access network nodes 4110 support (or the same access network nodes 4110 additionally support) non-3GPP RATs, such as Wi-Fi or a proprietary RAT. As another example, telecommunications network 4102 may support multiple generations of related communication standards (e.g., 4G and 5G 3 GPP communication standards) and, as a result, may include an access network 104 and / or a core network 106 that supports multiple different standard generations or may include multiple access networks 104 and / or multiple core networks 106 with individual networks 104, 106 supporting different standard generations.
[0057] Telecommunications network 4102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunications network 4102. For example, the telecommunications network 4102 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC)ZMassive loT services to yet further UEs.
[0058] In some examples, one or more of the UEs 4112 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 4104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 4104. Additionally, a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LIE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).
[0059] In the example, the hub 4114 communicates with the access network 4104 to facilitate indirect communication between one or more UEs (e.g., UE 4112C and / or 4112D) and network nodes (e.g., network node 4110B). In some examples, the hub 4114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 4114 may be a broadband router enabling access to the core network 4106 for the UEs. As another example, the hub 4114 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 4110, or by executable code, script, process, or other instructions in the hub 4114.
[0060] As another example, the hub 4114 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 4114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 4114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 4114 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 4114 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.
[0061] The hub 4114 may have a constant / persistent or intermittent connection to the network node 4110B. The hub 4114 may also allow for a different communication scheme and / or schedule between the hub 4114 and UEs (e.g., UE 4112C and / or 4112D), and between the hub 4114 and the core network 4106. In other examples, the hub 4114 is connected to the core network 4106 and / or one or more UEs via a wired connection. Moreover, the hub 4114 may be configured to connect to an M2M service provider over the access network 4104 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 4110 while still connected via the hub 4114 via a wired or wireless connection. In some embodiments, the hub 4114 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 4110B. In other embodiments, the hub 4114 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 4110B, but which isadditionally capable of operating as a communication start and / or end point for certain data channels.
[0062] Figure 7 is another example of a communication system 4200 according to some embodiments. As used herein, the communication system 4200 includes multiple access points (APs) 4210 (with four exemplary APs 4210A, 4210B, 4210C, and 4210D being depicted) and multiple wireless devices, referred to in the context of communication system 4200 as stations (STAs) 4212 (referred to individually as STA 4212A, STA 4212B, STA 4212C, STA 4212D, and STA 4212E). STA 4212A is served by AP 4210A in a first basic service set (BSS) 4220A. STA 4210B and STA 4210C are served by AP 4210B in a second BSS, BSS 4220B. STA 4212D is served by AP 4210C in a third BSS, BSS 4220C. STA 4212E is served by AP 4210D in a fourth BSS, BSS 4220D. Stations 4212 may be non-AP STAs and correspond to various kinds of wireless devices, for example, user terminals, such as mobile or stationary computing devices like smartphones, laptop computers, desktop computers, tablet computers, gaming devices, headmounted displays (HMDs) for Augmented Reality (AR) or Virtual Reality (VR), or the like. Further, stations 4212 could, for example, correspond to other kinds of equipment like smart home devices, printers, multimedia devices, data storage devices, or the like.
[0063] Each of STAs 4212 may connect through a radio link to one of APs 4210. For example, depending on location or channel conditions experienced by a given STA 4212, the STA may select an appropriate AP and BSS for establishing the radio link. The radio link may be based on one or more orthogonal frequency-division multiplexing (OFDM) carriers from a frequency spectrum that is shared on the basis of a contention-based mechanism, e.g., an unlicensed or license exempt band like 2.4 GHz Industrial, Scientific, and Medical (ISM) band, the 5 GHz band, the 6 GHz band, or the 60 GHz band.
[0064] Each AP 4210 may provide data connectivity to STAs 4212 connected to a particular AP 4210. As illustrated, APs 4210 may be connected to a data network 4230. In this way, APs 4210 may also provide data connectivity between STAs 4212 and other entities, e.g., to one or more servers, service providers, data sources, data sinks, user terminals, or the like. Accordingly, the radio link established between a given STA 4212 and its serving AP 4210 may be used for providing various kinds of services to STA 4212, e.g., a voice service, a multimedia service, or other data service. Such services may be based on applications that are executed on STA 4212 and / or on a device linked to STA 4212. By way of example, Figure 7 illustrates anapplication service platform 4232 provided in data network 4230. The application(s) executed on STA 4212 and / or on one or more other devices linked to STA 4212 may use the radio link for data communication with one or more other STA 4212 and / or the application service platform 4232, thereby enabling utilization of the corresponding service(s) at STA 4212.
[0065] Figure 8 shows a wireless device 4300, which may be configured to operate in communication system 4100 of Figure 6 or in communication system 4200 of Figure 7. The wireless device 4300 may be alternatively referred to as a UE 4300, like a UE 4112 within the context of communication system 4100, or as a station (STA) 4300 or as a non-access-point station (non-AP STA) 4300, like a STA 4212 within the context of the communication system 4200, in accordance with respective embodiments. As used herein, a wireless device refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other wireless devices. Examples of a wireless device include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop- embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, and wireless terminal. Other examples include any type of UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.
[0066] A wireless device 4300 may support device-to-device (D2D) communication, for example by implementing a 3 GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, wireless device 4300 may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, wireless device 4300 may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, wireless device 4300 may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).
[0067] In particular embodiments, wireless device 4300 includes processing circuitry 4302 that is operatively coupled via a bus 4304 to an input / output interface 4306, a power source 4308, a memory 4310, a communication interface 4312, and / or any other component, or any combination thereof. Certain embodiments of wireless device 4300 may include all or a subset of the components shown in Figure 8. The level of integration between the components may vary from one embodiment of wireless device 4300 to another. In general, in a particular embodiment of wireless device 4300, processing circuitry 4302, input / output interface 4306, power source 4308, memory 4310, and communication interface 4312 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of wireless device 4300. Further, certain embodiments of wireless devices 4300 may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.
[0068] The processing circuitry 4302 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine- readable computer programs in the memory 4310. The processing circuitry 4302 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 4302 may include multiple central processing units (CPUs), tensor processing unit(s) (TPUs), graphical processing unit(s) (GPUs), and any other type of accelerator.
[0069] In the example, the input / output interface 4306 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into wireless device 4300. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from auser. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.
[0070] In some embodiments, the power source 4308 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used to supply power to circuitry or to charge an associated battery. The power source 4308 may further include power circuitry for delivering power from the power source 4308 itself, and / or an external power source, to the various parts of wireless device 4300 via input circuitry or an interface such as an electrical power cable. Power source 4308 may perform any formatting, converting, or other modification to make accessible power suitable for the respective components of the wireless device 4300 to which power is supplied.
[0071] The memory 4310 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 4310 includes one or more programs 4314, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 4316. The memory 4310 may store, for use by wireless device 4300, any of a variety of various operating systems or combinations of operating systems.
[0072] The memory 4310 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embeddedUICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 4310 may allow wireless device 4300 to access instructions, programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 4310, which may be or comprise a device-readable storage medium.
[0073] The processing circuitry 4302 may be configured to communicate with an access network or other network via or using the communication interface 4312. The communication interface 4312 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 4322. The communication interface 4312 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another wireless device or a network node in an access network). Each transceiver may include a transmitter 4318 and / or a receiver 4320 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 4318 and receiver 4320 may be coupled to one or more antennas (e.g., antenna 4322) and may share circuit components, software or firmware, or alternatively be implemented separately.
[0074] In the illustrated embodiment, communication functions of the communication interface 4312 may include cellular communication, Wi-Fi communication (e.g., according to an IEEE 802.11 family standard), LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / internet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.
[0075] In particular embodiments, wireless device 4300 may provide an output of data captured via a sensor, through its communication interface 4312, via a wireless connection to a network node, and / or in any appropriate manner. Data captured by sensors of a wireless device4300 can be communicated through a wireless connection to a network node via another wireless device 4300. In particular embodiments, such output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).
[0076] As another example, wireless device 4300 comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, wireless device 4300 may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.
[0077] Wireless device 4300, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, wearable technology, extended industrial application and healthcare. Nonlimiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. In particular embodiments, wireless device 4300 represents an loT device that comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the example embodiment of wireless device 4300 shown in Figure 8.
[0078] As yet another specific example, in an loT scenario, wireless device 4300 may represent a machine or other device that performs monitoring and / or measurements, andtransmits the results of such monitoring and / or measurements to another wireless device and / or a network node. Wireless device 4300 may in this case be an M2M device, which may in a 3 GPP context be referred to as an MTC device. As one particular example, wireless device 4300 may implement the 3GPP NB-IoT standard. In other scenarios, wireless device 4300 may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.
[0079] In practice, any number of wireless devices 4300 may be used together with respect to a single use case. For example, a first wireless device 4300 might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second wireless device 4300 that is a remote controller operating the drone. When a user makes changes from the remote controller, the first wireless device 4300 may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second wireless device 4300 can also include more than one of the functionalities described above. For example, wireless device 4300 might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.
[0080] Figure 9 shows a network node 4400 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunications network. In accordance with respective embodiments, network node 4400 may be configured to operate in communication system 4100 of Figure 6, like network nodes 4108 or 4110, or in communication system 4200 of Figure 7, like an AP 4210 or a station 4212. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), 0-RAN nodes or components of an O-RAN node (e.g., 0-RU, 0-DU, O-CU).
[0081] Network nodes 4400 may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. Network node 4400 may be a relay node or a relay donor node controlling a relay. Network nodes 4400 may also include one or more (or all) parts of a distributedradio base station such as centralized digital units, distributed units (e.g., in an O-RAN access node) and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).
[0082] Other examples of network nodes 4400 include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSRBSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).
[0083] In particular embodiments, network node 4400 includes a processing circuitry 4402, a memory 4404, a communication interface 4406, and a power source 4408. In general, in a particular embodiment of network node 4400, processing circuitry 4402, memory 4404, communication interface 4406, and power source 4408 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of network node 4400.
[0084] The network node 4400 may be composed of multiple distinct network entities (e.g., a NodeB entity and a RNC entity, or a BTS entity and a BSC entity, etc.), which may each have or utilize their own respective physical components. In certain scenarios in which the network node 4400 comprises multiple such entities (e.g., BTS and BSC), one or more of the separate entities may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 4400 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memories 4404 or portions of memory 4404 for different RATs) and some components may be reused (e.g., a same antenna 4410 may be shared by different RATs). The network node 4400 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 4400, for example GSM, WCDMA, LTE, NR, Wi-Fi (e.g., according to an IEEE 802.11 family1standard), Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 4400.
[0085] The processing circuitry 4402 may 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 components, such as the memory 4404, to provide network node 4400 functionality.
[0086] In some embodiments, the processing circuitry 4402 includes a system on a chip (SOC). In some embodiments, the processing circuitry 4402 includes one or more of radio frequency (RF) transceiver circuitry 4412 and baseband processing circuitry 4414. In some embodiments, the RF transceiver circuitry 4412 and the baseband processing circuitry 4414 may 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 circuitry 4412 and baseband processing circuitry 4414 may be on the same chip or set of chips, boards, or units.
[0087] The memory 4404 may 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), readonly 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 the processing circuitry 4402. The memory 4404 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 4402 and utilized by the network node 4400. The memory 4404 may be used to store any calculations made by the processing circuitry 4402 and / or any data received via the communication interface 4406. In some embodiments, the processing circuitry 4402 and memory 4404 is integrated.
[0088] The communication interface 4406 is used in wired or wireless communication of signaling and / or data with UEs, other network nodes, and / or any other networkequipment. In the illustrated embodiment, communication interface 4406 comprises port(s) / terminal(s) 4416 to send and receive data, for example to and from a network over a wired connection. In particular embodiments, network node 4300 may be capable of wireless communication and communication interface 4406 may also include radio front-end circuitry 4418 that may be coupled to, or in certain embodiments a part of, an antenna 4410. Particular embodiments of radio front-end circuitry 4418 include filter(s) 4420 and amplifier(s) 4422. The radio front-end circuitry 4418 may be connected to an antenna 4410 and processing circuitry 4402. The radio front-end circuitry may be configured to condition signals communicated between antenna 4410 and processing circuitry 4402. The radio front-end circuitry 4418 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio frontend circuitry 4418 may convert the digital data into a radio signal(s) having the appropriate channel and bandwidth parameters using a combination of filters 4420 and / or amplifiers 4422. The radio signal(s) may then be transmitted via the antenna 4410. Similarly, when receiving data, the antenna 4410 may collect radio signals which are then converted into digital data by the radio front-end circuitry 4418. The digital data may be passed to the processing circuitry 4402. In other embodiments, the communication interface may comprise different components and / or different combinations of components.
[0089] In certain alternative embodiments, network node 4400 may be capable of wireless communication but does not include separate radio front-end circuitry 4418, instead, the processing circuitry 4402 includes radio front-end circuitry and is connected to the antenna 4410. Similarly, in some embodiments, all or some of the RF transceiver circuitry 4412 is part of the communication interface 4406. In still other embodiments, the communication interface 4406 includes one or more ports or terminals 4416, the radio front-end circuitry 4418, and the RF transceiver circuitry 4412, as part of a radio unit (not shown), and the communication interface 4406 communicates with the baseband processing circuitry 4414, which is part of a digital unit (not shown).
[0090] The antenna 4410 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 4410 may be coupled to the radio front-end circuitry 4418 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 4410 is separate from the network node 4400 and connectable to the network node 4400 through one or more interfaces or ports.
[0091] The antenna 4410, communication interface 4406, and / or the processing circuitry 4402 may be configured to perform some or all of the receiving operations and / or obtaining operations described herein as being performed by the network node 4400. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna 4410, the communication interface 4406, and / or the processing circuitry 4402 may be configured to perform some or all of the transmitting or sending operations described herein as being performed by the network node 4400. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.
[0092] The power source 4408 provides power to the various components of network node 4400 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 4408 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 4400 with power for performing the functionality described herein. For example, the network node 4400 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 4408. As a further example, the power source 4408 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.
[0093] Embodiments of the network node 4400 may include additional components beyond those shown in Figure 9 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, the network node 4400 may include user interface equipment to allow input of information into the network node 4400 and to allow output of information from the network node 4400. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 4400.
[0094] Figure 10 is a block diagram illustrating a virtualization environment 4500 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein,virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 4500 hosted by one or more of hardware nodes, such as a hardware computing device that operates as an access network node, UE, core network node, or host. Further, in embodiments in which a virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 4500 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an 0-2 interface.
[0095] Applications 4502 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.
[0096] Hardware 4504 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 4506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VM 4508A and VM 4508B (which may be collectively referred to as VMs 4508), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 4506 may present a virtual operating platform that appears like networking hardware to one or more of the VMs 4508.
[0097] The VMs 4508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by virtualization layer 4506. Different embodiments of the instance of a virtual appliance 4502 may be implemented on one or more of VMs 4508, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware,physical switches, and physical storage, which can be located in data centers, and customer premise equipment.
[0098] In the context of NFV, each of the VMs 4508 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 4508, and that part of hardware 4504 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more of the VMs 4508 on top of the hardware 4504 and corresponds to an application 4502.
[0099] Hardware 4504 may be implemented in a standalone network node with generic or specific components. Hardware 4504 may implement some functions via virtualization. Alternatively, hardware 4504 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 4510, which, among others, oversees lifecycle management of applications 4502. In some embodiments, hardware 4504 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via 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 signaling can be provided with the use of a control system 4512 which may alternatively be used for communication between hardware nodes and radio units.[000100] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making adetermination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.[000101] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.
Claims
CLAIMSWhat is claimed is:
1. A method (400) performed by a wireless device for supporting roaming between a Private Network and one or more Public Networks, the method comprising:receiving (402), from a private network node in a private network, a public land mobile network identifier, PLMN ID, for each of one or more public networks;sending (404), by the wireless device, a registration request to the private network node, wherein the private network node forwards the registration request to an appropriate one of the one or more public networks, and wherein the appropriate one of the one or more public networks performs authentication of the registration request; andreceiving (410), from the private network node, an initiation of a secure session if the authentication is successful.
2. The method of claim 1 further comprising:receiving a denial of service if the authentication is not successful.
3. The method of claim 2, wherein identifying whether the wireless device is permitted to connect with the Public Network is selectively enabled by a user.
4. The method of claim 2, wherein if a wireless device is not permitted, then the private network node logs one or more details of the wireless device and connection attempt in a failed access data log.
5. The method of any of the previous claims, wherein the wireless device is limited to consume services from the public network to a predetermined timeframe.
6. The method of claim 2, wherein identifying whether the wireless device is permitted to connect with the Public Network comprises: comparing the wireless device to devices on a devices data log.
7. The method of claim 6 wherein the devices data log comprises a list of permitted devicesand associated unique identifiers.
8. The method of claim 6 wherein the devices data log comprises a list ofunpermitted devices and associated unique identifiers.
9. The method of any of the previous claims wherein the registration request comprises a unique identifier comprising at least one of: an International Mobile Subscriber Identity (IMSI), a Temporary Mobile Subscriber Identity (TMSI), and a 5G Globally Unique Temporary Identity (5G-GUTI).
10. The method of any of the previous claims, wherein the Private Network is based on an unlicensed spectrum.
11. A method (500) performed by a private network node for supporting roaming between a wireless device and one or more public networks, the method comprising:broadcasting (502), by the private network node, a public land mobile network identifier, PLMN ID, for each of one or more public networks;receiving (504), from the wireless device, a registration request for one of the one or more public networks;forwarding (506), by the private network node, the registration request to an appropriate public network of the one or more public networks so that the appropriate public network can perform authentication (508) of the wireless device;if the wireless device is authenticated, then receiving (510) an initiation of a secure session between the private network node and the public network; andenabling (512), by the private network node, the wireless device to consume services from the appropriate public network.
12. The method of claim 11 further comprising: if the wireless device is not authenticated, then receiving a denial of service from the appropriate public network.
13. The method of claim 12, further comprising receiving an indication that a user has selectedan option to be connected to the public network.
14. The method of claim 12 further comprising, if the wireless device is rejected by the appropriate public network, then logging one or more details of the private network node and connection attempt in a failed access data log.
15. The method of any of claims 11-14 further comprising, limiting the connection from the appropriate public network to a predetermined timeframe.
16. The method of claim 12, further comprising comparing the private network node to devices on a devices data log.
17. The method of claim 16 wherein the devices data log comprises a list ofpermitted devices and associated unique identifiers.
18. The method of claim 16 wherein the devices data log comprises a list of unpermitted devices and associated unique identifiers.
19. The method of any of claims 11-18 wherein the registration request comprises a unique identifier comprising at least one of: an International Mobile Subscriber Identity (IMSI), a Temporary Mobile Subscriber Identity (TMSI), and a 5G Globally Unique Temporary Identity (5G-GUTI).
20. The method of any of claims 11-19 wherein the private network is based on an unlicensed spectrum.
21. A neutral host for supporting roaming between a private network and one or more public networks, comprising:processing circuitry; anda memory, the memory containing instructions executable by the processing circuitry whereby the system / apparatus is operative to:broadcast, by a private network node, a public land mobile network identifier, PLMN ID, for each of one or more public networks;receive, by the private network node, a registration request for one of the one or more public networks;forward, by the private network node, the registration request to an appropriate public network of the one or more public networks so that the appropriate public network can perform authentication of a wireless device;if the wireless device is authenticated, then receive an initiation of a secure session between the private network node and the public network; and enable, by the private network node, the network node to consume services from the appropriate public network.
