WO2024072275A1 - Enhancements to mobility history information (mhi) for non-public networks (npn) - Google Patents

Enhancements to mobility history information (mhi) for non-public networks (npn) Download PDF

Info

Publication number
WO2024072275A1
WO2024072275A1 PCT/SE2023/050860 SE2023050860W WO2024072275A1 WO 2024072275 A1 WO2024072275 A1 WO 2024072275A1 SE 2023050860 W SE2023050860 W SE 2023050860W WO 2024072275 A1 WO2024072275 A1 WO 2024072275A1
Authority
WO
WIPO (PCT)
Prior art keywords
mhi
network
visited
public networks
logged
Prior art date
Application number
PCT/SE2023/050860
Other languages
French (fr)
Inventor
Tahmineh TORABIAN ESFAHANI
Ali PARICHEHREHTEROUJENI
Sakib BIN REDHWAN
Gautham NAYAK SEETANADI
Angelo Centonza
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Publication of WO2024072275A1 publication Critical patent/WO2024072275A1/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0083—Determination of parameters used for hand-off, e.g. generation or modification of neighbour cell lists
    • H04W36/00833—Handover statistics
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/18—Selecting a network or a communication service
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W64/00—Locating users or terminals or network equipment for network management purposes, e.g. mobility management
    • H04W64/006—Locating users or terminals or network equipment for network management purposes, e.g. mobility management with additional information processing, e.g. for direction or speed determination

Definitions

  • the present disclosure relates generally to wireless communication networks, and more specifically to techniques for a network to use mobility history information (MHI) provided by a user equipment (UE) to estimate and/or determine various mobility characteristics of the UE.
  • MHI mobility history information
  • UE user equipment
  • 5G fifth generation
  • NR New Radio
  • 3GPP Third-Generation Partnership Project
  • 5G/NR is developed for maximum flexibility to support multiple and substantially different use cases.
  • MTC machine type communication
  • URLCC ultralow latency critical communications
  • D2D side-link device-to-device
  • NR uses CP-OFDM (Cyclic Prefix Orthogonal Frequency Division Multiplexing) in the DL and either CP-OFDM or DFT-spread OFDM (DFT-S-OFDM) in the UL.
  • CP-OFDM Cyclic Prefix Orthogonal Frequency Division Multiplexing
  • DFT-S-OFDM DFT-spread OFDM
  • NR DL and UL physical resources are organized into equal-sized 1-ms subframes.
  • a subframe is further divided into multiple slots of equal duration, with each slot including multiple OFDM-based symbols.
  • An NR slot can include 14 OFDM symbols for normal cyclic prefix and 12 symbols for extended cyclic prefix.
  • a resource block (RB) consists of a group of 12 contiguous OFDM subcarriers for a duration of a 12- or 14-symbol slot.
  • a resource element (RE) corresponds to one OFDM subcarrier during one OFDM symbol interval.
  • Mobility history information was introduced in LTE and is also supported in NR. As part of its MHI measurements, a UE stores a cell identifier of its current serving cell and also stores information about to how long the UE has stayed in this cell. The UE keeps such MHI for up to 16 previous serving cells. UE MHI also includes information about how long the UE has been out of the coverage.
  • 3GPP-specified technology is deployed in public land mobile networks (PLMNs) that are accessible to any user with a valid subscription.
  • 3GPP Release 16 (Rel-16) introduced support for Non-Public Networks (NPN), as described in 3GPP TS 23.501 (vl6.5.0).
  • NPN Non-Public Networks
  • An example NPN is a factory or other industrial facility that deploys its own 5GS to provide connectivity for both equipment and workers, with non-affiliated users restricted from access.
  • NPNs can be deployed as a Stand-alone Non-Public Network (SNPN) when not relying on network functions provided by a PLMN.
  • An SNPN is identified by a PLMN ID and network ID (NID) broadcast in SIB1.
  • An SNPN-capable UE supports the SNPN access mode.
  • the UE When the UE is set to operate in SNPN access mode, the UE only selects and registers with SNPNs.
  • the UE When the UE is not set to operate in SNPN access mode, the UE performs normal PLMN selection procedures.
  • UEs operating in SNPN access mode only (re)select cells within the selected/registered SNPN and a cell can only be considered as suitable if the PLMN and NID broadcast by the cell matches the selected/registered SNPN.
  • NPNs can be deployed as a Public Network Integrated (PNI) NPN when relying on functions provided by a PLMN.
  • PNI-NPNs Closed Access Groups (CAGs) identify groups of subscribers permitted to access one or more cells associated with the CAG.
  • a CAG is identified by a CAG identifier broadcast in SIB1.
  • a C AG-capable UE can be configured with the following per PLMN:
  • CAG-only indication if the UE is only allowed to access 5GS via CAG cells.
  • the UE checks the suitability of CAG cells based on the Allowed CAG list provided by upper layers.
  • the UE is configured with a CAG-only indication
  • only CAG Member Cells can be suitable.
  • a non-suitable cell can be acceptable though if the UE is configured with a CAG- only indication for one of the PLMN broadcast by the cell.
  • a UE may perform mobility procedures (e.g., handover) between PLMNs and NPNs.
  • a UE is successfully registered on an NPN (e.g., SNPN) when the UE has found a suitable NPN cell to camp on and a registration from the UE has been accepted in the registration area to which the camped cell belongs.
  • NPN e.g., SNPN
  • a UE that has access and subscription to several networks or different network types e.g., SNPN, PNI-NPN, and PLMN
  • can perform registration on a private network e.g., SNPN
  • Some embodiments include methods (e.g., procedures) for a UE configured to operate in public networks (PNs, e.g., PLMNs) and in non-public networks (NPNs).
  • PNs public networks
  • NPNs non-public networks
  • These exemplary methods include logging first MHI associated with one or more public networks and/or with visited cells in the one or more public networks. These exemplary methods include logging second MHI associated with one or more non-public networks and/or with visited cells in the one or more non-public networks. These exemplary methods include, after subsequently connecting to a first network, sending to the first network one or more MHI reports that includes one or more of the following: at least part of the logged first MHI, and at least part of the logged second MHI.
  • the logged second MHI includes an indication of a duration of time the UE spent outside of a public network and one of the following: an indication that the duration of time was spent in a non-public network, or an indication that the duration of time was spent in a network whose type and/or identity cannot be revealed.
  • the logged second MHI for a non-public network includes the indication that the duration of time was spent in a non-public network
  • the logged second MHI also includes an identity of the non- public network.
  • the logged first MHI includes an indication of a duration of time the UE spent outside of a non-public network and one of the following: an indication that the duration of time was spent in a public network, or an indication that the duration of time was spent in a network whose type and/or identity cannot be revealed.
  • the logged second MHI includes, for each visited cell in a non- public network, an indication of a duration of time the UE spent in the visited cell and one of the following: an indication that the visited cell is part of a non-public network, or an indication that the visited cell is part of a network whose type and/or identity cannot be revealed.
  • the one or more MHI reports are arranged according to one of the following:
  • the at least part of the first MHI included in the single MHI report corresponds to one of the following:
  • the at least part of the second MHI included in the single MHI report or the second MHI report corresponds to one of the following:
  • these exemplary methods also include, after sending the single MHI report that includes at least part of the second MHI but excludes the first MHI, discarding the first MHI in response to the earlier of the following events:
  • At least one entry in the MHI report is associated with respective at least one visited cell,.
  • Each of the at least one entry indicates one of the following for the associated visited cell:
  • each entry associated with a visited NPN cell includes a cell global identity (CGI) of the visited NPN cell.
  • CGI cell global identity
  • the first MHI and the second MHI are logged in separate UE variables. In other embodiments, the first MHI and the second MHI are logged in a single UE variable.
  • these exemplary methods also include, after subsequently connecting to the first network, receiving from the first network an information request for MHI logged for public networks and for MHI logged for non-public networks. In such case, sending the one or more MHI reports is responsive to the information request.
  • the information request includes a single indication of a request for MHI logged for public networks and for MHI logged for non-public networks. In other of these embodiments, the information request includes a first indication of a request for MHI logged for public networks and a second indication of a request for MHI logged for non-public networks.
  • these exemplary methods also include receiving, from the first network or from a second network, a configuration for logging and reporting MHI. In such case logging the first and second MHI and sending the one or more MHI reports are in accordance with the configuration.
  • Other embodiments include additional methods (e.g., procedures) for a RAN node configured to operate in a first network.
  • These exemplary methods can include receiving from a UE one or more MHI reports that include one or more of the following logged by the UE:
  • These exemplary methods also include identifying a second RAN node based on the received one or more MHI reports.
  • the second RAN node serves one or more of the cells identified in the one or more MHI reports.
  • These exemplary methods also include sending at least a portion of the received one or more MHI reports to the second RAN node.
  • the first and second MBH can have any of the same content, form, and/or structure as the corresponding first and second MHI logged by a UE, as summarized above for UE embodiments.
  • the one or more MHI reports can have any of the same content, form, and/or structure as the corresponding one or more MHI reports summarized above for UE embodiments.
  • first and second MHI report are sent to the second RAN node as one of the following: separate fields of a single information element (IE) in a message, or separate IES in the message.
  • IE information element
  • these exemplary methods also include sending to the UE an information request for MHI logged for public networks and for MHI logged for non-public networks. In such case, receiving the one or more MHI reports is responsive to the information request.
  • the information request includes a single indication of a request for MHI logged for public networks and for MHI logged for non-public networks. In other of these embodiments, the information request includes a first indication of a request for MHI logged for public networks and a second indication of a request for MHI logged for non-public networks.
  • these exemplary methods also include sending to the UE a configuration for logging and reporting MHI.
  • the contents of the one or more MHI reports are in accordance with the configuration.
  • the RAN node and the second RAN node are arranged in dual connectivity with the UE.
  • a cell served by the second RAN node is a target cell for a UE mobility procedure, and the at least a portion of the received one or more MHI reports is sent to the second RAN node in conjunction with the mobility procedure.
  • the second RAN node serves one or more of the cells identified in the one or more MHI reports.
  • UEs e.g., wireless devices, etc.
  • RAN nodes e.g., base stations, eNBs, gNBs, ng-eNBs, etc.
  • Other embodiments include non-transitory, computer-readable media storing computer-executable instructions that, when executed by processing circuitry, configure such UEs and RAN nodes to perform operations corresponding to any of the exemplary methods described herein.
  • embodiments can enable a network (e.g., PLMN) to determine, based on UE MHI, whether the UE was not connected to network cells because it was out of coverage of the network or because it was connected to an NPN but remained in coverage.
  • a network e.g., PLMN
  • embodiments can prevent a UE from sending sensitive, confidential, and/or proprietary information about a visited NPN to a PLMN or to another NPN.
  • clear labelling of NPN relation can prevent a PLMN from sharing the information with other PLMNs and/or NPNs. In this manner, embodiments can protect privacy and security of NPNs and their users.
  • Figures 1-2 illustrate two high-level views of an exemplary 5G/NR network architecture.
  • Figure 3 shows exemplary NR user plane (UP) and control plane (CP) protocol stacks.
  • UP NR user plane
  • CP control plane
  • Figure 4 shows an ASN.l data structure for an exemplary VisitedCelllnfoList mio m ⁇ on element (IE).
  • Figure 5 shows an ASN.1 data structure for an exemplary UEInformationRe quest message.
  • Figure 6 shows an ASN. l data structure for an exemplary UEInformationRe sponse message.
  • Figures 7-9 show ASN. l data structures for various exemplary VisitedCelllnfoList IES, according to various embodiments of the present disclosure.
  • Figure 10 shows an ASN. l data structure for an exemplary UEInformationRe quest message, according to various embodiments of the present disclosure.
  • Figure 11 shows a flow diagram of an exemplary method for a UE (e.g., wireless device), according to various embodiments of the present disclosure.
  • a UE e.g., wireless device
  • Figure 12 shows a flow diagram of an exemplary method for a RAN node (e.g., base station, eNB, gNB, ng-eNB, etcf according to various embodiments of the present disclosure.
  • a RAN node e.g., base station, eNB, gNB, ng-eNB, etcf according to various embodiments of the present disclosure.
  • Figure 13 shows a flow diagram of another exemplary method for a UE (e.g., wireless device), according to various embodiments of the present disclosure.
  • a UE e.g., wireless device
  • Figure 14 shows a flow diagram of another exemplary method for a RAN node (e.g., base station, eNB, gNB, ng-eNB, etcf according to various embodiments of the present disclosure.
  • a RAN node e.g., base station, eNB, gNB, ng-eNB, etcf according to various embodiments of the present disclosure.
  • Figure 15 shows a communication system according to various embodiments of the present disclosure.
  • Figure 16 shows a UE according to various embodiments of the present disclosure.
  • Figure 17 shows a network node according to various embodiments of the present disclosure.
  • Figure 18 shows host computing system according to various embodiments of the present disclosure.
  • Figure 19 is a block diagram of a virtualization environment in which functions implemented by some embodiments of the present disclosure may be virtualized.
  • Figure 20 illustrates communication between a host computing system, a network node, and a UE via multiple connections, at least one of which is wireless, according to various embodiments of the present disclosure.
  • Radio Access Node As used herein, a “radio access node” (or equivalently “radio network node,” “radio access network node,” or “RAN node”) can be any node in a radio access network (RAN) that operates to wirelessly transmit and/or receive signals.
  • RAN radio access network
  • a radio access node examples include, but are not limited to, a base station (e.g., gNB in a 3 GPP 5G/NR network or an enhanced or eNB in a 3GPP LTE network), base station distributed components (e.g., CU and DU), a high-power or macro base station, a low-power base station (e.g., micro, pico, femto, or home base station, or the like), an integrated access backhaul (IAB) node, a transmission point (TP), a transmission reception point (TRP), a remote radio unit (RRU or RRH), and a relay node.
  • a base station e.g., gNB in a 3 GPP 5G/NR network or an enhanced or eNB in a 3GPP LTE network
  • base station distributed components e.g., CU and DU
  • a high-power or macro base station e.g., a low-power base station (e.g., micro
  • a “core network node” is any type of node in a core network.
  • Some examples of a core network node include, e.g., a Mobility Management Entity (MME), a serving gateway (SGW), a PDN Gateway (P-GW), a Policy and Charging Rules Function (PCRF), an access and mobility management function (AMF), a session management function (SMF), a user plane function (UPF), a Charging Function (CHF), a Policy Control Function (PCF), an Authentication Server Function (AUSF), a location management function (LMF), or the like.
  • MME Mobility Management Entity
  • SGW serving gateway
  • P-GW PDN Gateway
  • PCRF Policy and Charging Rules Function
  • AMF access and mobility management function
  • SMF session management function
  • UPF user plane function
  • Charging Function CHF
  • PCF Policy Control Function
  • AUSF Authentication Server Function
  • LMF location management function
  • Wireless Device As used herein, a “wireless device” (or “WD” for short) is any type of device that is capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices. Communicating wirelessly can involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air.
  • wireless device is used interchangeably herein with the term “user equipment” (or “UE” for short), with both of these terms having a different meaning than the term “network node”.
  • Radio Node can be either a “radio access node” (or equivalent term) or a “wireless device.”
  • Network Node is any node that is either part of the radio access network (c.g, a radio access node or equivalent term) or of the core network (c.g, a core network node discussed above) of a cellular communications network.
  • a network node is equipment capable, configured, arranged, and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the cellular communications network, to enable and/or provide wireless access to the wireless device, and/or to perform other functions (e.g., administration) in the cellular communications network.
  • node can be any type of node that can in or with a wireless network (including RAN and/or core network), including a radio access node (or equivalent term), core network node, or wireless device.
  • a wireless network including RAN and/or core network
  • radio access node or equivalent term
  • core network node or wireless device.
  • node may be limited to a particular type (e.g., radio access node, IAB node) based on its specific characteristics in any given context.
  • FIG. 1 illustrates a high-level view of an exemplary 5G network architecture, consisting of a Next Generation Radio Access Network (NG-RAN, 199) and a 5G Core (5GC, 198).
  • the NG-RAN can include one or more gNodeB’s (gNBs) connected to the 5GC via one or more NG interfaces, such as gNBs (100, 150) connected via respective interfaces (102, 152). More specifically, the gNBs can be connected to one or more Access and Mobility Management Functions (AMFs) in the 5GC via respective NG-C interfaces and to one or more User Plane Functions (UPFs) in 5GC via respective NG-U interfaces.
  • the 5GC can include various other network functions (NFs), such as Session Management Function(s) (SMF).
  • NFs Session Management Function(s) (SMF).
  • the 5GC can be replaced by an Evolved Packet Core (EPC, 198), which conventionally has been used together with a Long-Term Evolution (LTE) Evolved UMTS RAN (E-UTRAN).
  • EPC Evolved Packet Core
  • gNBs e.g., 100, 150
  • MMEs Mobility Management Entities
  • SGWs Serving Gateways
  • each of the gNBs can support frequency division duplexing (FDD), time division duplexing (TDD), or a combination thereof.
  • FDD frequency division duplexing
  • TDD time division duplexing
  • Each of the gNBs can serve a geographic coverage area including one or more cells and, in some cases, can also use various directional beams to provide coverage in the respective cells.
  • a DL “beam” is a coverage area of a network-transmitted reference signal (RS) that may be measured or monitored by a UE.
  • RS network-transmitted reference signal
  • the NG-RAN is layered into a Radio Network Layer (RNL) and a Transport Network Layer (TNL).
  • RNL Radio Network Layer
  • TNL Transport Network Layer
  • NG, Xn, Fl the related TNL protocol and the functionality are specified.
  • the TNL provides services for user plane transport and signaling transport.
  • NG RAN logical nodes include a Central Unit (CU or gNB-CU, e.g., 110) and one or more Distributed Units (DU or gNB-DU, e.g., 120, 130).
  • CUs are logical nodes that host higher-layer protocols and perform various gNB functions such controlling the operation of DUs.
  • DUs are decentralized logical nodes that host lower layer protocols and can include, depending on the functional split option, various subsets of the gNB functions.
  • Each CU and DU can include various circuitry needed to perform their respective functions, including processing circuitry, communication interface circuitry (e.g., transceivers), and power supply circuitry.
  • a gNB-CU connects to one or more gNB-DUs over respective Fl logical interfaces (e.g., 122 and 132 shown in Figure 1).
  • a gNB-DU can be connected to only a single gNB-CU.
  • the gNB-CU and its connected gNB-DU(s) are only visible to other gNBs and the 5GC as a gNB. In other words, the Fl interface is not visible beyond gNB-CU.
  • Centralized control plane protocols can be hosted in a different CU than centralized user plane protocols (e.g., PDCP-U).
  • a gNB-CU can be divided logically into a CU-CP function (including RRC and PDCP for signaling radio bearers) and CULT? function (including PDCP for UP).
  • a single CU-CP can be associated with multiple CU-UPs in a gNB.
  • the CU-CP and CU-UP communicate with each other using the El-AP protocol over the El interface.
  • the Fl interface between CU and DU (see Figure 1) is functionally split into Fl-C between DU and CU-CP and Fl-U between DU and CU-UP.
  • Three deployment scenarios for the split gNB architecture shown in Figure 1 are CU-CP and CU-UP centralized, CU-CP distributed/CU-UP centralized, and CU-CP centralized/CU-UP distributed.
  • Figure 2 shows another high-level view of an exemplary 5G network architecture, including an NG-RAN (299) and a 5GC (298).
  • the NG-RAN can include gNBs (e.g., 210a,b) and ng-eNBs (e.g., 220a, b) that are interconnected with each other via respective Xn interfaces.
  • gNBs e.g., 210a,b
  • ng-eNBs e.g., 220a, b
  • the gNBs and ng-eNBs are also connected via the NG interfaces to the 5GC, more specifically to Access and Mobility Management Functions (AMFs, e.g., 230a, b) via respective NG-C interfaces and to User Plane Functions (UPFs, e.g., 240a, b) via respective NG- U interfaces.
  • AMFs Access and Mobility Management Functions
  • UPFs User Plane Functions
  • the AMFs can communicate with Policy Control Functions (PCFs, e.g., 250a, b) and Network Exposure Functions (NEFs, e.g., 260a, b).
  • PCFs Policy Control Functions
  • NEFs Network Exposure Functions
  • Each of the gNBs can support the NR radio interface including frequency division duplexing (FDD), time division duplexing (TDD), or a combination thereof.
  • Each of ng-eNBs can support the fourth generation (4G) Long-Term Evolution (LTE) radio interface. Unlike conventional LTE eNBs, however, ng-eNBs connect to the 5GC via the NG interface.
  • Each of the gNBs and ng-eNBs can serve a geographic coverage area including one or more cells (e.g., 211a- b, 221a-b).
  • a UE (205) can communicate with the gNB or ng-eNB serving that cell via the NR or LTE radio interface, respectively.
  • Figure 2 shows gNBs and ng-eNBs separately, it is also possible that a single NG-RAN node provides both types of functionality.
  • NR networks In addition to providing coverage via cells as in LTE, NR networks also provide coverage via “beams.”
  • a downlink (DL, i.e., network to UE) “beam” is a coverage area of a network-transmitted reference signal (RS) that may be measured or monitored by a UE.
  • RS can include any of the following: synchronization signal/PBCH block (SSB), channel state information RS (CSLRS), tertiary reference signals (or any other sync signal), positioning RS (PRS), demodulation RS (DMRS), phase-tracking reference signals (PTRS), etc.
  • SSB is available to all UEs regardless of the state of their connection with the network, while other RS (e.g., CSLRS, DM-RS, PTRS) are associated with specific UEs that have a network connection.
  • Figure 3 shows an exemplary configuration of NR user plane (UP) and control plane (CP) protocol stacks between a UE (310), a gNB (320), and an AMF (330), such as those shown in Figures 1-2.
  • Physical (PHY), Medium Access Control (MAC), Radio Link Control (RLC), and Packet Data Convergence Protocol (PDCP) layers between the UE and the gNB are common to UP and CP.
  • PDCP provides ciphering/deciphering, integrity protection, sequence numbering, reordering, and duplicate detection for both CP and UP.
  • PDCP provides header compression and retransmission for UP data.
  • IP Internet protocol
  • SDU service data units
  • PDU protocol data units
  • SDAP Service Data Adaptation Protocol
  • QoS quality-of-service
  • DRB Data Radio Bearers
  • QFI QoS flow identifiers
  • RLC transfers PDCP PDUs to MAC through logical channels (LCH).
  • LCH logical channels
  • RLC provides error detection/correction, concatenation, segmentation/reassembly, sequence numbering, reordering of data transferred to/from the upper layers.
  • MAC provides mapping between LCHs and PHY transport channels, LCH prioritization, multiplexing into or demultiplexing from transport blocks (TBs), hybrid ARQ (HARQ) error correction, and dynamic scheduling (on gNB side).
  • PHY provides transport channel services to MAC and handles transfer over the NR radio interface, e.g., via modulation, coding, antenna mapping, and beam forming.
  • the non-access stratum (NAS) layer is between UE and AMF and handles UE/gNB authentication, mobility management, and security control.
  • RRC sits below NAS in the UE but terminates in the gNB rather than the AMF.
  • RRC controls communications between UE and gNB at the radio interface as well as the mobility of a UE between cells in the NG-RAN.
  • RRC also broadcasts system information (SI) and performs establishment, configuration, maintenance, and release of DRBs and Signaling Radio Bearers (SRBs) and used by UEs.
  • SI system information
  • SRBs Signaling Radio Bearers
  • RRC controls addition, modification, and release of carrier aggregation (CA) and dual -connectivity (DC) configurations for UEs, and performs various security functions such as key management.
  • CA carrier aggregation
  • DC dual -connectivity
  • RRC IDLE state the UE’s radio is active on a discontinuous reception (DRX) schedule configured by upper layers.
  • DRX active periods also referred to as “DRX On durations”
  • an RRC IDLE UE receives SI broadcast in the cell where the UE is camping, performs measurements of neighbor cells to support cell reselection, and monitors a paging channel on PDCCH for pages from 5GC via gNB.
  • NR RRC__IDLE state An NR UE in RRC__IDLE state is not known to the gNB serving the cell where the UE is camping.
  • NR RRC includes an RRC_INACTIVE state in which a UE is known (e.g., via UE context) by the serving gNB.
  • RRC INACTIVE has some properties similar to a “suspended” condition used in LTE.
  • Seamless mobility is a key feature of 3GPP radio access technologies (RATs).
  • a RAN e.g., NG-RAN
  • RRM radio resource management
  • Seamless handovers ensure that the UE moves around in the coverage area of different cells without excessive interruption to data transmission.
  • RLF radio link failure
  • HAF handover failure
  • An RLF reporting procedure was introduced as part of the mobility robustness optimization (MRO) in LTE Rel-9.
  • MRO mobility robustness optimization
  • a UE logs relevant information at the time of RLF and later reports such information to the network via a target cell to which the UE ultimately connects (e.g., after reestablishment).
  • the reported information can include RRM measurements of various neighbor cells prior to the mobility operation (e.g., handover).
  • 3GPP Rel-17 introduced a successful handover report (SHR) whereby a UE reports various information about a successful handover to a target cell.
  • SHR successful handover report
  • both RLF reports and SHRs can include information about the UE’s random access towards the target cell.
  • the random access (RA) information can include the bandwidth part (BWP) in which the RA was attempted, DL pathloss experienced at the time of initiating the RA procedure, information related to each RA preamble transmission attempt (e.g., whether contention was experienced, number of preamble transmission attempts in a certain SSB or CSL RS, etc.).
  • 3GPP TS 38.331 (vl7.1.0) section 5.7.10.4 describes UE actions upon successful completion of a RA procedure, including various RA information collected and stored in UE variable VarRA-Report.
  • a UE may release (i.e., discard) VarRA-Report 48 hours after the last successful RA procedure or failed/successful on-demand SI acquisition procedure for which information was added to the stored VarRA-Report.
  • Mobility history information was introduced in LTE and is also supported in NR. As part of its MHI measurements, a UE stores a cell identifier of its current serving cell and also stores information about to how long the UE has stayed in this cell. The UE keeps such MHI for up to 16 previous serving cells. UE MHI also includes information about how long the UE has been out of the coverage.
  • 3GPP TS 38.331 (vl7.1.0) section 5.7.9 describes UE MHI collection in more detail, including how MHI is accumulated by the UE in RRC CONNECTED, RRC IDLE, and RRC IN ACTIVE states.
  • the UE In response to camping in or connecting to a different cell (“visited cell”), the UE includes an entry for the visited cell in visitedCelllnfoList of the UE variable VarMobilityHistory Report possibly after removing the oldest entry, if necessary.
  • 3GPP TS 38.331 (vl7.1.0) section 6.3.4 specifies the VisitedCelllnfoList information element (IE), which is also shown as an ASN.1 data structure in Figure 4.
  • This IE includes MHI of up to 16 most recently visited primary cells or time spent in any cell selection state and/or camped on any cell state in NR or E-UTRA and, in case of Dual Connectivity, the MHI of maxPSCellHistory most recently visited primary secondary cell group cells across all primary cells included in the VisitedCelllnfoList .
  • the most recently visited cell is stored first in the list.
  • the list includes cells visited in RRC IDLE, RRC INACTIVE and RRC CONNECTED states for NR and RRC IDLE and RRC CONNECTED for LTE/E-UTRA.
  • a UE can indicate availability of MHI via the mobilityHistoryAvail field in various RRC messages, including RRCSetupComplete, RRCReestablishmentComplete , and RRCResume- Complete.
  • the network can initiate a UE Information procedure to obtain the MHI from the UE.
  • 3GPP TS 38.331 (vl7.1.0) section 5.7.10 (including subsections) specifies the UE Information procedure in more detail.
  • FIG. 5 shows an ASN.l data structure for an exemplary UEInformationRequest message, which is further described in 3GPP TS 38.331 (vl7.1.0) section 6.3.4.
  • the mobilityHistoryReportReq-rl6 field in the UEInformationRe quest-r 16-IEs is an optional field, but if present it is set to “true” indicating that the network is requesting available MHI from the UE. Its absence indicates that the network is not requesting MHI.
  • a similar convention is used for the ra-ReportReq-r!6 field, which relates to RA information.
  • the message includes fields for the network to request various other information following similar conventions.
  • FIG. 6 shows an ASN.l data structure for an exemplary UEInformationRe sponse message, which is further described in 3GPP TS 38.331 (vl7.1.0) section 6.3.4. Note that each report field (e.g., ra- ReportList-rl6, rlf-Report-r 16. mobilityHistoryReport-r 16. etc.) is optional but if included, it contains various relevant information logged by the UE.
  • report field e.g., ra- ReportList-rl6, rlf-Report-r 16. mobilityHistoryReport-r 16. etc.
  • NPN Non-Public Networks
  • 3GPP Rel-16 introduced support for Non-Public Networks (NPN), as described in 3GPP TS 23.501 (v!6.5.0).
  • NPN Non-Public Networks
  • An example NPN is a factory or other industrial facility that deploys its own 5GS to provide connectivity for both equipment and workers, with non-affiliated users restricted from access.
  • An NPN can be deployed as a Stand-alone Non-Public Network (SNPN) when not relying on network functions provided by a PLMN.
  • An SNPN is identified by a PLMN ID and network ID (NID) broadcast in SIB1.
  • NID network ID
  • an NPN can be deployed as a Public Network Integrated (PNI) NPN when relying on functions provided by a PLMN.
  • PNI NPN is identified by a PLMN ID and Closed Access Group (C AG) identifier broadcast in SIB 1.
  • this operation by the UE may expose sensitive, confidential, and/or proprietary information about a visited NPN to a PLMN or to another NPN. This can put at risk the privacy of the UEs connected to the NPN.
  • the UE collecting and reporting MHI for a visited cell in the SNPN can expose cell identities, locations, coverage details, etc. of the SNPN to other networks. This can create external security risks for the SNPN and its users.
  • Embodiments of the present disclosure address these and other problems, issues, and/or difficulties by providing techniques in which a UE collects visited cell information for MHI per network type, i.e., visited PN cells in PN-related MHI and visited NPN cells information in NPN-related MHI.
  • the UE also logs time spent in each network as well as a flag indicating that UE spent the logged time in an NPN.
  • the UE logs the network identity in each MHI so that it can be reported to the proper network.
  • the UE logs the time spent in another network without specifying which network that was.
  • the UE can log visited NPN cells in PN-related MHI but also includes cell global identity (CGI) of the visited cells in addition to or instead of physical cell identity (PCI) and frequency information.
  • CGI cell global identity
  • embodiments can provide various benefits and/or advantages. For example, embodiments can enable a network (e.g., PLMN) to determine, based on UE MHI, whether the UE was not connected to network cells because it was out of coverage of the network or because it was connected to an NPN but remained in coverage. Furthermore, embodiments can prevent a UE from sending sensitive, confidential, and/or proprietary information about a visited NPN to a PLMN or to another NPN. In embodiments where the UE does provide such information, clear labelling of NPN relation can prevent a PLMN from sharing the information with other PLMNs and/or NPNs. In this manner, embodiments can protect privacy and security of NPNs and their users.
  • a network e.g., PLMN
  • Some embodiments include methods performed by a UE capable of mobility between public and non-public networks (e.g., PLMNs and NPNs).
  • the UE is configured by the network (e.g., PLMN) with instructions for handling visited cell information for NPNs that could be potentially included in UE -reported MHI.
  • the UE may also be configured with instructions for handling visited cell information for PLMNs.
  • the UE Upon visiting cells in an NPN or a PLMN, the UE manages the collection of MHI in accordance with the configured instructions.
  • the UE is configured to not include MHI for visited cells associated with different network types (i.e., public and non-public) or different networks of the same type (e.g., two NPNs) in the same MHI report.
  • This restriction can prevent conveying sensitive, confidential, and/or proprietary information about a visited NPN to a PLMN or to another NPN.
  • the information protected in this manner can include, for example, measurements and other information that enables an entity to track users in the NPN.
  • this restriction may be limited to not including visited NPN cells in an MHI report sent to a PN or another NPN, such that the UE may include visited PN cells in an MHI report sent to an NPN.
  • the configuration may indicate one or more particular networks (e.g., PLMN IDs) to which the restriction policy applies.
  • the configuration may indicate particular types of cell information that should be included or excluded from a MHI report. For example, in the case of dual connectivity (DC) with a master cell group (MCG) and a secondary cell group (SCG), the configuration may indicate whether identifiers of visited primary SCG cells (PSCells) should be included along with identifiers of visited PCells (i.e., of MCG).
  • DC dual connectivity
  • MCG master cell group
  • SCG secondary cell group
  • the UE logs the time spent in an NPN and an indication that the time was spent in an NPN. In other embodiments, the UE logs time spent in a network whose information should not be revealed, without providing information identifying the particular network (or network type) that the UE visited.
  • the UE is configured to include information about visited cells associated with different network types (i.e., public and non-public) or different networks of the same type (e.g., two NPNs) in the same MHI report.
  • the UE is also configured to include in MHI the cell global identities (CGIs) associated with visited NPN cells, which also includes information about visited PN cells.
  • CGIs cell global identities
  • the UE is configured to provides MHI for a particular network (which may be a PLMN, SNPN, or PNI-NPN) only when served by that network, with the provided MHI only including visited cells of the particular network.
  • a particular network which may be a PLMN, SNPN, or PNI-NPN
  • the UE has to log visited cell information along with the network identity (e.g., PLMN ID).
  • a UE stores up to a maximum number of cells (e.g., PCells) recently visited in RRC IDLE, RRC INACTIVE, and RRC CONNECTED states associated with a network type (e.g., PN or NPN) according to the configuration.
  • a network type e.g., PN or NPN
  • a UE capable of mobility between PN and NPN follows the configuration and policy options described above when reporting PN and/or NPN information in MHI.
  • FIG. 7 shows an ASN. l data structure for an exemplary VisitedCelllnfoList IE, according to some embodiments of the present disclosure.
  • the VisitedCelllnfoList includes up to the maximum number (16) of VisitedCelllnfo IES, each of which includes information for a visited cell.
  • each VisitedCelllnfo IE includes a networkType-r!8 field which can take on two different enumerated values: “PN”, which indicates that the visited cell is associated with a public network, and “SNPN” which indicates that the visited cell is associated with an SNPN.
  • FIG. 8 shows an ASN. l data structure for another exemplary VisitedCelllnfoList IE, according to other embodiments of the present disclosure.
  • each VisitedCelllnfo IE includes a privateNetwork-r!8 field that when present indicates the visited cell is associated with an NPN and when absent indicates that the visited cell is associated with a public network.
  • FIG. 9 shows an ASN. l data structure for another exemplary VisitedCelllnfoList IE, according to other embodiments of the present disclosure.
  • each VisitedCelllnfo IE includes only one following (by choice): an nr-CellId-r!6 field including information about a visited NR cell; an eutra-CellId-rl6 field including information about a visited LTE cell; and a notDisclosedCelllnfo field that indicates information about the visited cell cannot be disclosed (but does not specify the reason, such as being part of a SNPN).
  • Embodiments can also be realized as text included in a 3GPP specification.
  • the following shows some exemplary text that can be added to the description of UE MHI procedures in 3GPP TS 38.331 (17.1.0), with ellipses denoted existing text omitted for brevity.
  • *** Begin proposed 3 GPP specification text *** 5.7.9 Mobility History Information
  • the UE shall: l>upon entering NR PN (in RRC CONNECTED or RRC IDLE) while previously using another network type e.g., SNPN; or: l>upon entering NR SNPN (in RRC CONNECTED or RRC IDLE) while previously using another network type e.g., PN:
  • VarMobilityHistoryReport possibly after removing the oldest entry, if necessary, according to following:
  • the UE may be configured (or it may be specified) to log CGI information for cells of the second network type in the MHI report sent to a network of the first network type.
  • the following shows exemplary text according to these embodiments that can be added to the description of UE MHI procedures in 3GPP TS 38.331 (17.1.0), with ellipses denoted existing text omitted for brevity.
  • This procedure specifies how the mobility history information is stored by the UE, covering RRC IDLE, RRC INACTIVE and RRC CONNECTED.
  • the UE shall:
  • the UE logs information about visited primary cells of first and second network types (e.g., PN and NPN) in different UE variables. For example, the UE logs information about visited PN cells in the existing VarMobilityHistoryReport and logs information about visited NPN cells in a new variable, e.g., VarMobilityHistoryNPNReport or similar.
  • first and second network types e.g., PN and NPN
  • the UE reports information about visited NPN cells (e.g., VarMobilityHistoryNPNReport) to the NPN after registering with that network.
  • the UE reports information about visited NPN cells (e.g., VarMobilityHistoryNPNReport) to a PLMN upon request by that network, e.g., based on a confidentiality agreement between PLMN and NPN operators.
  • the UE retains the VarMobilityHistoryReport with information about visited PN cells after leaving the PN (e.g., registering with an NPN) and deletes it if the UE does not return to the PN within a time limit.
  • Figure 10 shows an ASN. l data structure for an exemplary UEInformationRe quest message, according to some embodiments of the present disclosure.
  • This message includes an optional mobilityHistoryReportReqSNPN-rl6 field, which if present indicates that the network requesting available SNPN MHI from the UE. Its absence indicates that the network is not requesting SNPN MHI. Note that this field is in addition to the mobilityHistoryReportReq-rl6 field by which the network requests available PN MHI from the UE, in the manner described above in relation to Figure 5.
  • the following shows exemplary text according to these embodiments that can be added to the description of the UE Information procedure in 3GPP TS 38.331 (17.1.0), with ellipses denoted existing text omitted for brevity.
  • the UE information procedure is used by the network to request the UE to report information.
  • This procedure specifies how the mobility history information is stored by the UE, covering RRC IDLE, RRC INACTIVE and RRC CONNECTED.
  • the network initiates the procedure by sending the UEInformationRequest message.
  • the network should initiate this procedure only after successful security activation.
  • the UE Upon receiving the UEInformationRequest message, the UE shall, only after successful security activation:
  • a RAN node Upon receiving an MHI report from a UE containing information about visited cells in an NPN (e.g., mobilityHistoryReportNPN IE), the RAN node identifies a second RAN node based on the cell identities in the MHI and sends the received MHI to the identified second RAN node, which may use it for mobility robustness optimization (MRO), coverage and capacity optimization (CCO), or other improvements.
  • MRO mobility robustness optimization
  • CCO coverage and capacity optimization
  • the UE may be in dual connectivity, with the RAN node as the MN and the second RAN node as the SN.
  • the MN sends the MHI received from the UE to the SN.
  • the SN can receive the MHI from the UE and send it to the MN.
  • the second RAN node may be the target node for a mobility procedure (e.g., handover) involving the UE that generated the MHI.
  • the RAN node can send the received MHI to the second RAN node during the mobility procedure, e.g., as part of a handover request message.
  • 3GPP TS 38.423 (vl7.1.0), which specifies the Xn interface between RAN nodes, can be modified in a similar manner.
  • the UE History Information IE defined in 3GPP TS 38.423 (vl7.1.0) can be modified to include a new container with NPN information.
  • This IE contains information about mobility history report for a UE.
  • NR Mobility History Report for NPN can be included in a separate IE, e.g., Non-Public Network UE History Information.
  • a separate IE e.g., Non-Public Network UE History Information.
  • the following text illustrates how an example of how these embodiments can be specified in 3GPP TS 38.473 (vl7.1.0) and 38.423 (vl7.1.0), based on the addition of the optional NR Mobility History Report for NPN IE.
  • the UE History Information IE contains information about cells that a UE has been served by in active state prior to the target cell. The overall mechanism is described in TS 36.300 [12], NOTE: The definition of this IE is aligned with the definition of the UE History Information IE in TS 38.413 [5],
  • the Last Visited Cell Information may contain cell specific information.
  • Figures 11- 14 depict exemplary methods (e.g., procedures) performed by UEs or by RAN nodes.
  • various features of the operations described below correspond to various embodiments described above.
  • Some of the exemplary methods shown in Figures 11-14 can be complementary to each other such that they can be used cooperatively to provide benefits, advantages, and/or solutions to problems described herein.
  • the exemplary methods are illustrated in Figures 11-14 by specific blocks in particular orders, the operations corresponding to the blocks can be performed in different orders than shown and can be combined and/or divided into operations having different functionality than shown.
  • Optional blocks and/or operations are indicated by dashed lines.
  • Figure 11 illustrates an exemplary method (e.g., procedure) for a user equipment (UE) configured to operate in public networks (PN) and in non-public networks (NPN), according to various embodiments of the present disclosure.
  • UE user equipment
  • NPN non-public networks
  • the exemplary method shown in Figure 11 can be performed by a UE (e.g., wireless device) described herein with reference to other figures.
  • the exemplary method can include the operations of block 1120, where while visiting one or more cells in one or more PNs, the UE can log first MHI associated with the visited PN cells.
  • the exemplary method can also include the operations of block 1130, where while visiting one or more cells in one or more NPNs, the UE can log second MHI associated with the visited NPN cells.
  • the exemplary method can also include the operations of block 1150, where after subsequently connecting to a first network, the UE can send to the first network one or more MHI reports that includes one or more of the following: at least part of the first MHI, and at least part of the second MHI.
  • the one or more MHI reports are arranged according to one of the following:
  • the at least part of the first MHI included in the single MHI report corresponds to one of the following:
  • the one or more MHI reports are arranged according to one of the following:
  • the at least part of the second MHI included in the single MHI report or the second MHI report corresponds to one of the following:
  • the exemplary method can also include the operations of block 1160, where after sending the single MHI report that includes at least part of the second MHI but excludes the first MHI (e.g., in block 1150), the UE can delete the first MHI in response to the earlier of the following events:
  • each MHI report entry corresponds to a visited cell and indicates one of the following for the visited cell:
  • each MHI report entry corresponding to a visited NPN cell includes a cell global identity (CGI) of the visited NPN cell.
  • CGI cell global identity
  • each MHI report entry corresponding to a visited NPN cell includes a first indication of a duration of time the UE spent in the visited NPN cell and a second indication that the visited NPN cell is associated with one of the following: an NPN, or a network and/or a network type that cannot be revealed.
  • the first MHI and the second MHI can be logged in separate UE variables or in a single UE variable.
  • the exemplary method can also include the operations of block 1140, where after subsequently connecting to the first network, the UE can receive from the first network an information request for MHI logged for PNs and MHI logged for NPNs. In such case, sending the one or more MHI reports in block 1150 is responsive to the information request.
  • the information request includes one of the following:
  • the exemplary method can also include the operations of block 1110, where the UE can receive, from the first network or from a second network, a configuration for logging and reporting MHI. In such case, logging the first and second MHI (e.g., in blocks 1120-1130) and sending the one or more MHI reports (e.g., in block 1150) are in accordance with the configuration.
  • Figure 12 illustrates an exemplary method e.g., procedure) for a RAN node in a first network, according to various embodiments of the present disclosure.
  • the exemplary method shown in Figure 12 can be performed by an RAN node (e.g., base station, eNB, gNB, ng-eNB, etc.) such as described elsewhere herein.
  • an RAN node e.g., base station, eNB, gNB, ng-eNB, etc.
  • the exemplary method can include the operations of block 1230, where the RAN node can receive from a UE one or more MHI reports that include one or more of the following: • at least part of first MHI logged by the UE while visiting cells in one or more public networks (PNs), and
  • PNs public networks
  • NPNs nonpublic networks
  • the exemplary method can also include the operations of block 1240, where the RAN node can identify a second RAN node based on the received one or more MHI reports. For example, the second RAN node serves one or more of the cells identified in the one or more MHI reports.
  • the exemplary method can also include the operations of block 1250, where the RAN node can send at least a portion of the received one or more MHI reports to the second RAN node.
  • the one or more MHI reports are arranged according to one of the following:
  • the at least part of the first MHI included in the single MHI report corresponds to one of the following:
  • the one or more MHI reports are arranged according to one of the following:
  • the at least part of the second MHI included in the single MHI report or the second MHI report corresponds to one of the following:
  • each MHI report entry corresponds to a visited cell and indicates one of the following for the visited cell: • whether the visited cell is associated with a PN or an NPN (e.g., as illustrated in Figures 7-8); or
  • each MHI report entry corresponding to a visited NPN cell includes a cell global identity (CGI) of the visited NPN cell.
  • CGI cell global identity
  • each MHI report entry corresponding to a visited NPN cell includes a first indication of a duration of time the UE spent in the visited NPN cell and a second indication that the visited NPN cell is associated with one of the following: an NPN, or a network and/or a network type that cannot be revealed.
  • the exemplary method can also include the operation of block 1220, where the RAN node can send to the UE an information request for MHI logged for PNs and MHI logged for NPNs. In such case, receiving the one or more MHI reports in block 1230 is responsive to the information request.
  • the information request includes one of the following:
  • the exemplary method can also include the operations of block 1210, where the RAN node can send to the UE a configuration for logging and reporting MHI. In such case, the contents of the received one or more MHI reports are in accordance with the configuration.
  • the RAN node and the second RAN node are arranged in dual connectivity with the UE.
  • a cell served by the second RAN node is a target cell for a UE mobility procedure (e.g., handover), and the at least a portion of the received one or more MHI reports are sent to the second RAN node in conjunction with the mobility procedure (e.g., in a handover request).
  • the one or more MHI reports include a first MHI report that includes the at least a part of the first MHI and a second MHI report that includes the at least a part of the second MHI.
  • the first and second MHI reports are sent to the second RAN node as one of the following: separate fields of a single IE in a message, or separate IES in the message.
  • Figure 13 illustrates another exemplary method e.g., procedure) for a UE configured to operate in public networks and in non-public networks, according to various embodiments of the present disclosure.
  • the exemplary method shown in Figure 13 can be performed by a UE (e.g., wireless device) described herein with reference to other figures.
  • the exemplary method includes the operations of block 1320, where the UE can log first mobility history information (MHI) associated with one or more public networks and/or with visited cells in the one or more public networks.
  • MHI mobility history information
  • the exemplary method also includes the operations of block 1330, where the UE can log second MHI associated with one or more nonpublic networks and/or with visited cells in the one or more non-public networks.
  • the exemplary method includes the operations of block 1350, where after subsequently connecting to a first network, the UE can send to the first network one or more MHI reports that includes one or more of the following: at least part of the logged first MHI, and at least part of the logged second MHI.
  • the logged second MHI includes an indication of a duration of time the UE spent outside of a public network and one of the following: an indication that the duration of time was spent in a non-public network, or an indication that the duration of time was spent in a network whose type and/or identity cannot be revealed.
  • an indication that the duration of time was spent in a non-public network or an indication that the duration of time was spent in a network whose type and/or identity cannot be revealed.
  • An example of these embodiments is the proposed 3GPP specification discussed above, where upon entering NR PN while previously using another network type (e.g., SNPN), the UE sets the following fields of an entry in variable VarMobilityHistoryReport'.
  • NetworkType as the selected network type (e.g., non-public network) where the UE was connected (in RRC CONNECTED, RRC IDLE or RRC INACTIVE) before entering the current network type (i.e., public network).
  • the logged second MHI for a non-public network when the logged second MHI for a non-public network includes the indication that the duration of time was spent in a non-public network, the logged second MHI also includes an identity of the non-public network.
  • the logged first MHI includes an indication of a duration of time the UE spent outside of a non-public network and one of the following: an indication that the duration of time was spent in a public network, or an indication that the duration of time was spent in a network whose type and/or identity cannot be revealed.
  • an indication that the duration of time was spent in a public network or an indication that the duration of time was spent in a network whose type and/or identity cannot be revealed.
  • An example of these embodiments is the proposed 3GPP specification discussed above, where upon entering NR SNPN while previously using another network type (e.g., PN), the UE sets the following fields of an entry in vari able VarMobilityH istoryReport.
  • NetworkType as the selected network type (e.g., public network) where the UE was connected (in RRC CONNECTED, RRC IDLE or RRC INACTIVE) before entering the current network type (i.e., non-public network).
  • the logged second MHI includes, for each visited cell in a nonpublic network, an indication of a duration of time the UE spent in the visited cell and one of the following: an indication that the visited cell is part of a non-public network, or an indication that the visited cell is part of a network whose type and/or identity cannot be revealed.
  • the one or more MHI reports are arranged according to one of the following:
  • the at least part of the first MHI included in the single MHI report corresponds to one of the following:
  • the at least part of the second MHI included in the single MHI report (i.e., in the second and third options above) or the second MHI report (i.e., in the fourth option above) corresponds to one of the following:
  • the exemplary method can also include the operations of block 1360, where after sending the single MHI report that includes at least part of the second MHI but excludes the first MHI, the UE can discard (e.g., delete or other make unusable) the first MHI in response to the earlier of the following events: • connecting to a second network that is a public network and sending the first MHI to the second network; or
  • At least one entry in the MHI report is associated with respective at least one visited cell,.
  • Each of the at least one entry indicates one of the following for the associated visited cell:
  • each entry associated with a visited NPN cell includes a cell global identity (CGI) of the visited NPN cell.
  • CGI cell global identity
  • the first MHI and the second MHI are logged in separate UE variables. In other embodiments, the first MHI and the second MHI are logged in a single UE variable.
  • the exemplary method can also include the operations of block 1340, where after subsequently connecting to the first network, the UE can receive from the first network an information request for MHI logged for public networks and for MHI logged for nonpublic networks. In such case, sending the one or more MHI reports in block 1350 is responsive to the information request.
  • the information request includes a single indication of a request for MHI logged for public networks and for MHI logged for nonpublic networks. In other of these embodiments, the information request includes a first indication of a request for MHI logged for public networks and a second indication of a request for MHI logged for non-public networks.
  • the exemplary method can also include the operations of block 1340, where the UE can receive, from the first network or from a second network, a configuration for logging and reporting MHI. In such case logging the first and second MHI in blocks 1320- 1330 and sending the one or more MHI reports in block 1350 are in accordance with the configuration.
  • Figure 14 illustrates another exemplary method (e.g., procedure) for a RAN node configured to operate in a first network, according to various embodiments of the present disclosure.
  • the exemplary method shown in Figure 14 can be performed by an RAN node (e.g., base station, eNB, gNB, ng-eNB, etc.) such as described elsewhere herein.
  • the exemplary method shown in Figure 14 can be used cooperatively with the exemplary method shown in Figure 13.
  • the exemplary method includes the operations of block 1430, where the RAN node can receive from a UE one or more MHI reports that include one or more of the following that was logged by the UE:
  • the exemplary method also includes the operations of blocks 1440-1450, where the RAN node can identify a second RAN node based on the received one or more MHI reports and send at least a portion of the received one or more MHI reports to the second RAN node.
  • the first and second MHI can have any of the same content, form, and/or structure as the corresponding first and second MHI logged by a UE, as described above for UE embodiments shown in Figure 13.
  • the one or more MHI reports can have any of the same content, form, and/or structure as the corresponding one or more MHI reports described above for UE embodiments shown in Figure 13.
  • the one or more MHI reports received by the RAN node correspond to the one or more MHI reports sent by the UE.
  • first and second MHI report are sent to the second RAN node as one of the following: separate fields of a single information element (IE) in a message, or separate IES in the message.
  • IE information element
  • the exemplary method also includes the operations of block 1420, where the RAN node can send to the UE an information request for MHI logged for public networks and for MHI logged for non-public networks.
  • receiving the one or more MHI reports in block 1430 is responsive to the information request.
  • the information request includes a single indication of a request for MHI logged for public networks and for MHI logged for non-public networks.
  • the information request includes a first indication of a request for MHI logged for public networks and a second indication of a request for MHI logged for non-public networks.
  • the exemplary method also includes the operations of block 1410, where the RAN node can send to the UE a configuration for logging and reporting MHI.
  • the contents of the one or more MHI reports are in accordance with the configuration.
  • the RAN node and the second RAN node are arranged in dual connectivity with the UE.
  • a cell served by the second RAN node is a target cell for a UE mobility procedure, and the at least a portion of the received one or more MHI reports is sent to the second RAN node in conjunction with the mobility procedure.
  • the second RAN node serves one or more of the cells identified in the one or more MHI reports.
  • FIG. 15 shows an example of a communication system 1500 in accordance with some embodiments.
  • communication system 1500 includes a telecommunication network 1502 that includes an access network 1504 (e.g., RAN) and a core network 1506, which includes one or more core network nodes 1508.
  • Access network 1504 includes one or more access network nodes, such as network nodes 1510a-b (one or more of which may be generally referred to as network nodes 1510), or any other similar 3 GPP access node or non-3GPP access point.
  • Network nodes 1510 facilitate direct or indirect connection of UEs, such as by connecting UEs 1512a-d (one or more of which may be generally referred to as UEs 1512) to core network 1506 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.
  • communication system 1500 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.
  • Communication system 1500 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.
  • UEs 1512 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and/or operable to communicate wirelessly with network nodes 1510 and other communication devices.
  • network nodes 1510 are arranged, capable, configured, and/or operable to communicate directly or indirectly with UEs 1512 and/or with other network nodes or equipment in telecommunication network 1502 to enable and/or provide network access, such as wireless network access, and/or to perform other functions, such as administration in telecommunication network 1502.
  • core network 1506 connects network nodes 1510 to one or more hosts, such as host 1516. 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.
  • Core network 1506 includes one or more core network nodes (e.g., 1508) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and/or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 1508.
  • Example core network nodes include 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).
  • MSC Mobile Switching Center
  • MME Mobility Management Entity
  • HSS Home Subscriber Server
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • AUSF Authentication Server Function
  • SIDF Subscription Identifier De-concealing function
  • UDM Unified Data Management
  • SEPP Security Edge Protection Proxy
  • NEF Network Exposure Function
  • UPF User Plane Function
  • Host 1516 may be under the ownership or control of a service provider other than an operator or provider of access network 1504 and/or telecommunication network 1502, and may be operated by the service provider or on behalf of the service provider.
  • Host 1516 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.
  • communication system 1500 of Figure 15 enables connectivity between the UEs, network nodes, and hosts.
  • the communication system 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 Electronics Engineers (IEEE) 802.11 standards (WiFi); and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and/or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.
  • GSM Global System for Mobile Communications
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • telecommunication network 1502 is a cellular network that implements 3GPP standardized features. Accordingly, telecommunication network 1502 may support network slicing to provide different logical networks to different devices that are connected to telecommunication network 1502. For example, telecommunication network 1502 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)/Massive loT services to yet further UEs.
  • UEs 1512 are configured to transmit and/or receive information without direct human interaction.
  • a UE may be designed to transmit information to access network 1504 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from access network 1504.
  • a UE may be configured for operating in single- or multi-RAT or multi-standard mode.
  • a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, 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).
  • MR-DC multi-radio dual connectivity
  • E-UTRAN Evolved-UMTS Terrestrial Radio Access Network
  • EN-DC New Radio - Dual Connectivity
  • hub 1514 communicates with access network 1504 to facilitate indirect communication between one or more UEs (e.g., 1512c and/or 1512d) and network nodes (e.g., network node 1510b).
  • hub 1514 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs.
  • hub 1514 may be a broadband router enabling access to core network 1506 for the UEs.
  • hub 1514 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 1510, or by executable code, script, process, or other instructions in hub 1514.
  • hub 1514 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.
  • hub 1514 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, hub 1514 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which hub 1514 then provides to the UE either directly, after performing local processing, and/or after adding additional local content.
  • hub 1514 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy loT devices.
  • Hub 1514 may have a constant/persistent or intermittent connection to network node 1510b. Hub 1514 may also allow for a different communication scheme and/or schedule between hub 1514 and UEs (e.g., 1512c and/or 1512d), and between hub 1514 and core network 1506. In other examples, hub 1514 is connected to core network 1506 and/or one or more UEs via a wired connection. Moreover, hub 1514 may be configured to connect to an M2M service provider over access network 1504 and/or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with network nodes 1510 while still connected via hub 1514 via a wired or wireless connection.
  • UEs may establish a wireless connection with network nodes 1510 while still connected via hub 1514 via a wired or wireless connection.
  • hub 1514 may be a dedicated hub - that is, a hub whose primary function is to route communications to/from the UEs from/to network node 1510b.
  • hub 1514 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 1510b, but which is additionally capable of operating as a communication start and/or end point for certain data channels.
  • FIG 16 shows a UE 1600 in accordance with some embodiments.
  • a UE 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-mounted or vehicle embedded/integrated wireless device, etc.
  • Other examples include any UE identified by 3 GPP, including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.
  • NB-IoT narrow band internet of things
  • MTC machine type communication
  • eMTC enhanced MTC
  • a UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X).
  • D2D device-to-device
  • DSRC Dedicated Short-Range Communication
  • V2V vehicle-to-vehicle
  • V2I vehicle-to-infrastructure
  • V2X vehicle-to-everything
  • a UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device.
  • a UE 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).
  • a UE may represent a device that is not intended for sale
  • UE 1600 includes processing circuitry 1602 that is operatively coupled via bus 1604 to input/output interface 1606, power source 1608, memory 1610, communication interface 1612, and possibly other components not specifically shown. Certain UEs may utilize all or a subset of the components shown in Figure 16. 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.
  • Processing circuitry 1602 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 memory 1610.
  • Processing circuitry 1602 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.
  • processing circuitry 1602 may include multiple central processing units (CPUs).
  • input/output interface 1606 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 UE 1600.
  • 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 a user.
  • 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.
  • USB Universal Serial Bus
  • power source 1608 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. Power source 1608 may further include power circuitry for delivering power from power source 1608 itself, and/or an external power source, to the various parts of UE 1600 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of power source 1608. Power circuitry may perform any formatting, converting, or other modification to the power from power source 1608 to make the power suitable for the respective components of UE 1600 to which power is supplied.
  • an external power source e.g., an electricity outlet
  • Photovoltaic device e.g., or power cell
  • Power source 1608 may further include power circuitry for delivering power from power source 1608 itself, and/or an external power source, to the various parts of UE 1600 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of
  • Memory 1610 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.
  • memory 1610 includes one or more application programs 1614, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 1616.
  • Memory 1610 may store, for use by UE 1600, any of a variety of various operating systems or combinations of operating systems.
  • Memory 1610 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.
  • RAID redundant array of independent disks
  • HD-DVD high-density digital versatile disc
  • HDDS holographic digital data storage
  • DIMM external mini-dual in-line memory module
  • SDRAM synchronous dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • the UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’
  • Memory 1610 may allow UE 1600 to access instructions, application 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 memory 1610, which may be or comprise a device-readable storage medium.
  • Processing circuitry 1602 may be configured to communicate with an access network or other network using communication interface 1612.
  • Communication interface 1612 may comprise one or more communication subsystems and may include or be communicatively coupled to antenna 1622.
  • Communication interface 1612 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 UE or a network node in an access network).
  • Each transceiver may include transmitter 1618 and/or receiver 1620 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth).
  • transmitter 1618 and/or receiver 1620 may be coupled to one or more antennas (e.g., 1622) and may share circuit components, software, or firmware, or alternatively be implemented separately.
  • communication functions of communication interface 1612 may include cellular communication, Wi-Fi communication, 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 in 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.
  • a UE may provide an output of data captured by its sensors, through its communication interface 1612, via a wireless connection to a network node.
  • Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE.
  • the 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., an alert is sent when moisture is detected), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).
  • a UE 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.
  • the states of the actuator, the motor, or the switch may change.
  • the UE 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.
  • a UE 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, city wearable technology, extended industrial application and healthcare.
  • 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 head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-t
  • AR Augmented
  • a UE may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another UE and/or a network node.
  • the UE may in this case be an M2M device, which may in a 3 GPP context be referred to as an MTC device.
  • the UE may implement the 3GPP NB-IoT standard.
  • a UE 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.
  • any number of UEs may be used together with respect to a single use case.
  • a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone.
  • the first UE 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 UE can also include more than one of the functionalities described above.
  • a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.
  • Figure 17 shows a network node 1700 in accordance with some embodiments.
  • network nodes include, but are not limited to, access points (e.g., radio access points) and base stations (e.g., radio base stations, Node Bs, eNBs, and gNBs).
  • access points e.g., radio access points
  • base stations e.g., radio base stations, Node Bs, eNBs, and gNBs.
  • Base stations 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.
  • a base station may be a relay node or a relay donor node controlling a relay.
  • a network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units 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.
  • RRUs remote radio units
  • RRHs Remote Radio Heads
  • 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).
  • DAS distributed antenna system
  • network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, 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).
  • MSR multi-standard radio
  • RNCs radio network controllers
  • BSCs base station controllers
  • BTSs base transceiver stations
  • OFDM Operation and Maintenance
  • OSS Operations Support System
  • SON Self-Organizing Network
  • positioning nodes e.g., Evolved Serving Mobile Location Centers (E-SMLCs)
  • Network node 1700 includes processing circuitry 1702, memory 1704, communication interface 1706, and power source 1708.
  • Network node 1700 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components.
  • network node 1700 comprises multiple separate components (e.g., BTS and BSC components)
  • one or more of the separate components may be shared among several network nodes.
  • a single RNC may control multiple NodeBs.
  • each unique NodeB and RNC pair may in some instances be considered a single separate network node.
  • network node 1700 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 1704 for different RATs) and some components may be reused (e.g., a same antenna 1710 may be shared by different RATs).
  • Network node 1700 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1700, for example GSM, WCDMA, LTE, NR, WiFi, 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 1700.
  • RFID Radio Frequency Identification
  • Processing circuitry 1702 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 network node 1700 components, such as memory 1704, to provide network node 1700 functionality.
  • processing circuitry 1702 includes a system on a chip (SOC).
  • processing circuitry 1702 includes radio frequency (RF) transceiver circuitry 1712 and/or baseband processing circuitry 1714.
  • RF transceiver circuitry 1712 and/or baseband processing circuitry 1714 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units.
  • part or all of RF transceiver circuitry 1712 and baseband processing circuitry 1714 may be on the same chip or set of chips, boards, or units.
  • Memory 1704 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), 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 circuitry 1702.
  • 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-vola
  • Memory 1704 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 (collectively denoted computer program 1704a, which may be in the form of a computer program product) capable of being executed by processing circuitry 1702 and utilized by network node 1700. Memory 1704 may be used to store any calculations made by processing circuitry 1702 and/or any data received via communication interface 1706. In some embodiments, processing circuitry 1702 and memory 1704 is integrated.
  • Communication interface 1706 is used in wired or wireless communication of signaling and/or data between a network node, access network, and/or UE. As illustrated, communication interface 1706 comprises port(s)/terminal(s) 1716 to send and receive data, for example to and from a network over a wired connection. Communication interface 1706 also includes radio frontend circuitry 1718 that may be coupled to, or in certain embodiments a part of, antenna 1710. Radio front-end circuitry 1718 comprises filters 1720 and amplifiers 1722. Radio front-end circuitry 1718 may be connected to an antenna 1710 and processing circuitry 1702. Radio frontend circuitry 1718 may be configured to condition signals communicated between antenna 1710 and processing circuitry 1702.
  • Radio front-end circuitry 1718 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. Radio front-end circuitry 1718 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1720 and/or amplifiers 1722. The radio signal may then be transmitted via antenna 1710. Similarly, when receiving data, antenna 1710 may collect radio signals which are then converted into digital data by radio front-end circuitry 1718. The digital data may be passed to processing circuitry 1702. In other embodiments, the communication interface may comprise different components and/or different combinations of components.
  • network node 1700 does not include separate radio front-end circuitry 1718, instead, processing circuitry 1702 includes radio front-end circuitry and is connected to antenna 1710. Similarly, in some embodiments, all or some of RF transceiver circuitry 1712 is part of communication interface 1706. In still other embodiments, communication interface 1706 includes one or more ports or terminals 1716, radio front-end circuitry 1718, and RF transceiver circuitry 1712, as part of a radio unit (not shown), and communication interface 1706 communicates with baseband processing circuitry 1714, which is part of a digital unit (not shown).
  • Antenna 1710 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals.
  • Antenna 1710 may be coupled to radio front-end circuitry 1718 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly.
  • antenna 1710 is separate from network node 1700 and connectable to network node 1700 through an interface or port.
  • Antenna 1710, communication interface 1706, and/or processing circuitry 1702 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node. Any information, data and/or signals may be received from a UE, another network node and/or any other network equipment. Similarly, antenna 1710, communication interface 1706, and/or processing circuitry 1702 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and/or signals may be transmitted to a UE, another network node and/or any other network equipment. Power source 1708 provides power to the various components of network node 1700 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component).
  • Power source 1708 may further comprise, or be coupled to, power management circuitry to supply the components of network node 1700 with power for performing the functionality described herein.
  • network node 1700 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 power source 1708.
  • power source 1708 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.
  • Embodiments of network node 1700 may include additional components beyond those shown in Figure 17 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.
  • network node 1700 may include user interface equipment to allow input of information into network node 1700 and to allow output of information from network node 1700. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node 1700.
  • FIG 18 is a block diagram of a host 1800, which may be an embodiment of host 1318 of Figure 15, in accordance with various aspects described herein.
  • host 1800 may be or comprise various combinations hardware and/or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm.
  • Host 1800 may provide one or more services to one or more UEs.
  • Host 1800 includes processing circuitry 1802 that is operatively coupled via a bus 1804 to an input/output interface 1806, a network interface 1808, a power source 1810, and a memory 1812.
  • Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 16 and 17, such that the descriptions thereof are generally applicable to the corresponding components of host 1800.
  • Memory 1812 may include one or more computer programs including one or more host application programs 1814 and data 1816, which may include user data, e.g., data generated by a UE for host 1800 or data generated by host 1800 for a UE.
  • host 1800 may utilize only a subset or all of the components shown.
  • Host application programs 1814 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems).
  • Host application programs 1814 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network.
  • host 1800 may select and/or indicate a different host for over-the-top services for a UE.
  • Host application programs 1814 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real- Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.
  • HTTP Live Streaming HLS
  • RTMP Real-Time Messaging Protocol
  • RTSP Real- Time Streaming Protocol
  • MPEG-DASH Dynamic Adaptive Streaming over HTTP
  • FIG 19 is a block diagram illustrating a virtualization environment 1900 in which functions implemented by some embodiments may be virtualized.
  • virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources.
  • 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 1900 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host.
  • VMs virtual machines
  • the node may be entirely virtualized.
  • Applications 1902 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment 1900 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.
  • Hardware 1904 includes processing circuitry, memory that stores software and/or instructions (collectively denoted computer program 1904a, which may be in the form of a computer program product) 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 1906 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 1908a-b (one or more of which may be generally referred to as VMs 1908), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein.
  • Virtualization layer 1906 may present a virtual operating platform that appears like networking hardware to VMs 1908.
  • VMs 1908 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 1906.
  • Different embodiments of the instance of a virtual appliance 1902 may be implemented on one or more of VMs 1908, 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.
  • NFV network function virtualization
  • each VM 1908 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine.
  • Each VM 1908, and that part of hardware 1904 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.
  • a virtual network function is responsible for handling specific network functions that run in one or more VMs 1908 on top of hardware 1904 and corresponds to application 1902.
  • Hardware 1904 may be implemented in a standalone network node with generic or specific components. Hardware 1904 may implement some functions via virtualization. Alternatively, hardware 1904 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 1910, which, among others, oversees lifecycle management of applications 1902.
  • hardware 1904 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.
  • some signaling can be provided with the use of a control system 1912 which may alternatively be used for communication between hardware nodes and radio units.
  • Figure 20 shows a communication diagram of a host 2002 communicating via a network node 2004 with a UE 2006 over a partially wireless connection in accordance with some embodiments.
  • Example implementations, in accordance with various embodiments, of the UE such as a UE 1512a of Figure 15 and/or UE 1600 of Figure 16
  • network node such as network node 1510a of Figure 15 and/or network node 1700 of Figure 17
  • host such as host 1518 of Figure 15 and/or host 1800 of Figure 18
  • embodiments of host 2002 include hardware, such as a communication interface, processing circuitry, and memory.
  • Host 2002 also includes software, which is stored in or accessible by host 2002 and executable by the processing circuitry.
  • the software includes a host application that may be operable to provide a service to a remote user, such as UE 2006 connecting via an over-the-top (OTT) connection 2050 extending between UE 2006 and host 2002.
  • OTT over-the-top
  • a host application may provide user data which is transmitted using OTT connection 2050.
  • Network node 2004 includes hardware enabling it to communicate with host 2002 and UE 2006.
  • Connection 2060 may be direct or pass through a core network (like core network 1506 of Figure 15) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks.
  • an intermediate network may be a backbone network or the Internet.
  • UE 2006 includes hardware and software, which is stored in or accessible by UE 2006 and executable by the UE’s processing circuitry.
  • the software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 2006 with the support of host 2002.
  • client application such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 2006 with the support of host 2002.
  • an executing host application may communicate with the executing client application via OTT connection 2050 terminating at UE 2006 and host 2002.
  • the UE's client application may receive request data from the host's host application and provide user data in response to the request data.
  • OTT connection 2050 may transfer both the request data and the user data.
  • the UE's client application may interact with the user to generate the user data that it provides to the host application through OTT connection 2050.
  • OTT connection 2050 may extend via a connection 2060 between host 2002 and network node 2004 and via a wireless connection 2070 between network node 2004 and UE 2006 to provide the connection between host 2002 and UE 2006.
  • Connection 2060 and wireless connection 2070, over which OTT connection 2050 may be provided, have been drawn abstractly to illustrate the communication between host 2002 and UE 2006 via network node 2004, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • host 2002 provides user data, which may be performed by executing a host application.
  • the user data is associated with a particular human user interacting with UE 2006.
  • the user data is associated with a UE 2006 that shares data with host 2002 without explicit human interaction.
  • host 2002 initiates a transmission carrying the user data towards UE 2006.
  • Host 2002 may initiate the transmission responsive to a request transmitted by UE 2006. The request may be caused by human interaction with UE 2006 or by operation of the client application executing on UE 2006.
  • the transmission may pass via network node 2004, in accordance with the teachings of the embodiments described throughout this disclosure.
  • network node 2004 transmits to UE 2006 the user data that was carried in the transmission that host 2002 initiated, in accordance with the teachings of the embodiments described throughout this disclosure.
  • UE 2006 receives the user data carried in the transmission, which may be performed by a client application executed on UE 2006 associated with the host application executed by host 2002.
  • UE 2006 executes a client application which provides user data to host 2002.
  • the user data may be provided in reaction or response to the data received from host 2002.
  • UE 2006 may provide user data, which may be performed by executing the client application.
  • the client application may further consider user input received from the user via an input/output interface of UE 2006.
  • UE 2006 initiates, in step 2018, transmission of the user data towards host 2002 via network node 2004.
  • network node 2004 receives user data from UE 2006 and initiates transmission of the received user data towards host 2002.
  • host 2002 receives the user data carried in the transmission initiated by UE 2006.
  • One or more of the various embodiments improve the performance of OTT services provided to UE 2006 using OTT connection 2050, in which wireless connection 2070 forms the last segment. More precisely, embodiments described herein can enable a network (e.g., PLMN) to determine, based on UE MHI, whether the UE was not connected to network cells because it was out of coverage of the network or because it was connected to an NPN but remained in coverage. Furthermore, embodiments can prevent a UE from sending sensitive, confidential, and/or proprietary information about a visited NPN to a PLMN or to another NPN. In embodiments where the UE does provide such information, clear labelling of NPN relation can prevent a PLMN from sharing the information with other PLMNs and/or NPNs. In this manner, embodiments can protect privacy and security of NPNs and their users. By improving security of networks in this manner, embodiments increase the value of OTT services delivered over the improved networks to both end users and service providers.
  • a network e.g., PLMN
  • factory status information may be collected and analyzed by host 2002.
  • host 2002 may process audio and video data which may have been retrieved from a UE for use in creating maps.
  • host 2002 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights).
  • host 2002 may store surveillance video uploaded by a UE.
  • host 2002 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs.
  • host 2002 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and/or transmitting data.
  • 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.
  • the measurement procedure and/or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of host 2002 and/or UE 2006.
  • sensors (not shown) may be deployed in or in association with other devices through which OTT connection 2050 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities.
  • the reconfiguring of OTT connection 2050 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of network node 2004. Such procedures and functionalities may be known and practiced in the art.
  • measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by host 2002.
  • the measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using OTT connection 2050 while monitoring propagation times, errors, etc.
  • the term unit can have conventional meaning in the field of electronics, electrical devices and/or electronic devices and can include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.
  • any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses.
  • Each virtual apparatus may comprise a number of these functional units.
  • These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include Digital Signal Processor (DSPs), special-purpose digital logic, and the like.
  • the processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as Read Only Memory (ROM), Random Access Memory (RAM), cache memory, flash memory devices, optical storage devices, etc.
  • Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein.
  • the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according to one or more embodiments of the present disclosure.
  • device and/or apparatus can be represented by a semiconductor chip, a chipset, or a (hardware) module comprising such chip or chipset; this, however, does not exclude the possibility that a functionality of a device or apparatus, instead of being hardware implemented, be implemented as a software module such as a computer program or a computer program product comprising executable software code portions for execution or being run on a processor.
  • functionality of a device or apparatus can be implemented by any combination of hardware and software.
  • a device or apparatus can also be regarded as an assembly of multiple devices and/or apparatuses, whether functionally in cooperation with or independently of each other.
  • devices and apparatuses can be implemented in a distributed fashion throughout a system, so long as the functionality of the device or apparatus is preserved. Such and similar principles are considered as known to a skilled person.
  • Embodiments of the techniques and apparatus described herein also include, but are not limited to, the following enumerated examples:
  • a method for a user equipment (UE) configured to operate in public networks (PN) and in non-public networks (NPN), the method comprising: while visiting one or more cells in one or more PNs, logging first mobility history information (MHI) associated with the visited PN cells; while visiting one or more cells in one or more NPNs, logging second MHI associated with the visited NPN cells; and after subsequently connecting to a first network, sending to the first network one or more MHI reports that includes one or more of the following: at least part of the first MHI, and at least part of the second MHI.
  • MHI mobility history information
  • the one or more MHI reports are arranged according to one of the following: a single MHI report that includes at least part of the first MHI but excludes the second MHI; a single MHI report that includes the first MHI and the second MHI; or a first MHI report that includes the first MHI and a second MHI report that includes the second MHI.
  • the one or more MHI reports are arranged according to one of the following: a single MHI report that includes at least part of the second MHI but excludes the first MHI; a single MHI report that includes the first MHI and the second MHI; or a first MHI report that includes the first MHI and a second MHI report that includes at least part of the second MHI.
  • A5. The method of embodiment A4, wherein the at least part of the second MHI included in the single MHI report or the second MHI report corresponds to one of the following: all second MHI collected for all visited NPN cells; or only second MHI collected for visited NPN cells associated with the first network.
  • A6 The method of any of embodiments A4-A5, further comprising, after sending the single MHI report that includes at least part of the second MHI but excludes the first MHI, deleting the first MHI in response to the earlier of the following events: connecting to a second network that is a PN and sending the first MHI to the second network; or expiration of a time limit without sending the first MHI to a PN.
  • each MHI report entry corresponds to a visited cell and indicates one of the following for the visited cell: whether the visited cell is associated with a PN or an NPN; or whether or not information reported for the visited cell should be disclosed to other networks.
  • each MHI report entry corresponding to a visited NPN cell includes a cell global identity (CGI) of the visited NPN cell.
  • CGI cell global identity
  • each MHI report entry corresponding to a visited NPN cell includes a first indication of a duration of time the UE spent in the visited NPN cell and a second indication that the visited NPN cell is associated with one of the following: an NPN, or a network and/or a network type that cannot be revealed.
  • the method further comprises, after subsequently connecting to the first network, receiving from the first network an information request for MHI logged for PNs and MHI logged for NPNs; and sending the one or more MHI reports is responsive to the information request.
  • the information request includes one of the following: a single indication of a request for MHI logged for PNs and for MHI logged for NPNs; or a first indication of a request for MHI logged for PNs and a second indication of a request for MHI logged for NPNs.
  • A13 The method of any of embodiments A1-A12, further comprising receiving, from the first network or from a second network, a configuration for logging and reporting MHI, wherein logging the first and second MHI and sending the one or more MHI reports are in accordance with the configuration.
  • a method for a radio access network (RAN) node in a first network comprising: receiving from a user equipment (UE) one or more mobility history information (MHI) reports that include one or more of the following: at least part of first MHI logged by the UE while visiting cells in one or more public networks (PNs), and at least part of second MHI logged by the UE while visiting cells in one or more non-public networks (NPNs); identifying a second RAN node based on the received one or more MHI reports; and sending at least a portion of the received one or more MHI reports to the second RAN node.
  • MHI mobility history information
  • the one or more MHI reports are arranged according to one of the following: a single MHI report that includes at least part of the first MHI but excludes the second MHI; a single MHI report that includes the first MHI and the second MHI; or a first MHI report that includes the first MHI and a second MHI report that includes the second MHI.
  • the one or more MHI reports are arranged according to one of the following: a single MHI report that includes at least part of the second MHI but excludes the first MHI; a single MHI report that includes the first MHI and the second MHI; or a first MHI report that includes the first MHI and a second MHI report that includes at least part of the second MHI.
  • each MHI report entry corresponds to a visited cell and indicates one of the following for the visited cell: whether the visited cell is associated with a PN or an NPN; or whether or not information reported for the visited cell should be disclosed to other networks.
  • each MHI report entry corresponding to a visited NPN cell includes a cell global identity (CGI) of the visited NPN cell.
  • CGI cell global identity
  • each MHI report entry corresponding to a visited NPN cell includes a first indication of a duration of time the UE spent in the visited NPN cell and a second indication that the visited NPN cell is associated with one of the following: an NPN, or a network and/or a network type that cannot be revealed.
  • the method further comprises sending to the UE an information request for MHI logged for PNs and MHI logged for NPNs; and receiving the one or more MHI reports is responsive to the information request.
  • the information request includes one of the following: a single indication of a request for MHI logged for PNs and for MHI logged for NPNs; or a first indication of a request for MHI logged for PNs and a second indication of a request for MHI logged for NPNs.
  • the one or more MHI reports include a first MHI report that includes the at least a part of the first MHI and a second MHI report that includes the at least a part of the second MHI; and the first and second MHI reports are sent to the second RAN node as one of the following: separate fields of a single information element (IE) in a message, or separate IES in the message.
  • IE information element
  • a user equipment configured to operate in public networks (PN) and in non-public networks (NPN), the UE comprising: communication interface circuitry configured to communicate with RAN nodes in PNs and NPNs; and processing circuitry operatively coupled to the communication interface circuitry, whereby the processing circuitry and the communication interface circuitry are configured to perform operations corresponding to the methods of any of embodiments Al -Al 3.
  • a user equipment configured to operate in public networks (PN) and in non-public networks (NPN), the UE being further arranged to perform operations corresponding to the methods of any of embodiments Al -Al 3.
  • a non-transitory, computer-readable medium storing computer-executable instructions that, when executed by processing circuitry of a user equipment (UE) configured to operate in public networks (PN) and in non-public networks (NPN), configure the UE to perform operations corresponding to the methods of any of embodiments Al -Al 3.
  • UE user equipment
  • PN public networks
  • NPN non-public networks
  • a computer program product comprising computer-executable instructions that, when executed by processing circuitry of a user equipment (UE) configured to operate in public networks (PN) and in non-public networks (NPN), configure the UE to perform operations corresponding to the methods of any of embodiments Al -Al 3.
  • UE user equipment
  • PN public networks
  • NPN non-public networks
  • a radio access network (RAN) node configured to operate in a first network, the RAN node comprising: communication interface circuitry configured to communicate with UEs; and processing circuitry operatively coupled to the communication interface circuitry, whereby the processing circuitry and the communication interface circuitry are configured to perform operations corresponding to the methods of any of embodiments B1-B14.
  • RAN radio access network
  • a radio access network (RAN) node configured to operate in a first network, the RAN node being further arranged to perform operations corresponding to the methods of any of embodiments B1-B14.
  • D3. A non-transitory, computer-readable medium storing computer-executable instructions that, when executed by processing circuitry of a radio access network (RAN) node configured to operate in a first network, configure the RAN node to perform operations corresponding to the methods of any of embodiments B1-B14.
  • a computer program product comprising computer-executable instructions that, when executed by processing circuitry of a radio access network (RAN) node configured to operate in a first network, configure the RAN node to perform operations corresponding to the methods of any of embodiments B1-B14.
  • RAN radio access network

Landscapes

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

Abstract

Embodiments includes methods for a user equipment (UE) configured to operate in public networks and in non-public networks. Such methods include logging first mobility history information, MHI, associated with one or more public networks and/or with visited cells in the one or more public networks. Such methods include logging second MHI associated with one or more non-public networks and/or with visited cells in the one or more non-public networks. Such methods include, after subsequently connecting to a first network, sending to the first network one or more MHI reports that includes one or more of the following: at least part of the logged first MHI, and at least part of the logged second MHI. Other embodiments include complementary methods for a RAN node as well as UEs and RAN nodes configured to perform such methods.

Description

ENHANCEMENTS TO MOBILITY HISTORY INFORMATION (MHI) FOR NON-PUBLIC NETWORKS (NPN)
TECHNICAL FIELD
The present disclosure relates generally to wireless communication networks, and more specifically to techniques for a network to use mobility history information (MHI) provided by a user equipment (UE) to estimate and/or determine various mobility characteristics of the UE.
INTRODUCTION
Currently the fifth generation (5G) of cellular systems, also referred to as New Radio (NR), is being standardized within the Third-Generation Partnership Project (3GPP). 5G/NR is developed for maximum flexibility to support multiple and substantially different use cases. Besides the typical mobile broadband use case, also machine type communication (MTC), ultralow latency critical communications (URLCC), side-link device-to-device (D2D), and several other use cases too.
5G/NR technology shares many similarities with fourth-generation Long-Term Evolution (LTE). For example, NR uses CP-OFDM (Cyclic Prefix Orthogonal Frequency Division Multiplexing) in the DL and either CP-OFDM or DFT-spread OFDM (DFT-S-OFDM) in the UL. As another example, in the time domain, NR DL and UL physical resources are organized into equal-sized 1-ms subframes. A subframe is further divided into multiple slots of equal duration, with each slot including multiple OFDM-based symbols. An NR slot can include 14 OFDM symbols for normal cyclic prefix and 12 symbols for extended cyclic prefix. A resource block (RB) consists of a group of 12 contiguous OFDM subcarriers for a duration of a 12- or 14-symbol slot. A resource element (RE) corresponds to one OFDM subcarrier during one OFDM symbol interval.
Mobility history information (MHI) was introduced in LTE and is also supported in NR. As part of its MHI measurements, a UE stores a cell identifier of its current serving cell and also stores information about to how long the UE has stayed in this cell. The UE keeps such MHI for up to 16 previous serving cells. UE MHI also includes information about how long the UE has been out of the coverage.
Conventionally, 3GPP-specified technology is deployed in public land mobile networks (PLMNs) that are accessible to any user with a valid subscription. 3GPP Release 16 (Rel-16) introduced support for Non-Public Networks (NPN), as described in 3GPP TS 23.501 (vl6.5.0). An example NPN is a factory or other industrial facility that deploys its own 5GS to provide connectivity for both equipment and workers, with non-affiliated users restricted from access. NPNs can be deployed as a Stand-alone Non-Public Network (SNPN) when not relying on network functions provided by a PLMN. An SNPN is identified by a PLMN ID and network ID (NID) broadcast in SIB1. An SNPN-capable UE supports the SNPN access mode. When the UE is set to operate in SNPN access mode, the UE only selects and registers with SNPNs. When the UE is not set to operate in SNPN access mode, the UE performs normal PLMN selection procedures. UEs operating in SNPN access mode only (re)select cells within the selected/registered SNPN and a cell can only be considered as suitable if the PLMN and NID broadcast by the cell matches the selected/registered SNPN.
Alternately, NPNs can be deployed as a Public Network Integrated (PNI) NPN when relying on functions provided by a PLMN. For PNI-NPNs, Closed Access Groups (CAGs) identify groups of subscribers permitted to access one or more cells associated with the CAG. A CAG is identified by a CAG identifier broadcast in SIB1. A C AG-capable UE can be configured with the following per PLMN:
• Allowed CAG list containing the CAG identifiers that the UE is allowed to access; and
• CAG-only indication if the UE is only allowed to access 5GS via CAG cells.
The UE checks the suitability of CAG cells based on the Allowed CAG list provided by upper layers. When the UE is configured with a CAG-only indication, only CAG Member Cells can be suitable. A non-suitable cell can be acceptable though if the UE is configured with a CAG- only indication for one of the PLMN broadcast by the cell.
A UE may perform mobility procedures (e.g., handover) between PLMNs and NPNs. In general, a UE is successfully registered on an NPN (e.g., SNPN) when the UE has found a suitable NPN cell to camp on and a registration from the UE has been accepted in the registration area to which the camped cell belongs. A UE that has access and subscription to several networks or different network types (e.g., SNPN, PNI-NPN, and PLMN) can perform registration on a private network (e.g., SNPN) so long as the UE is capable of services that require specific subscriptions for registration.
SUMMARY
Even so, existing solutions specify UE MHI collection only in PLMNs. Moreover, there is no way to distinguish between network types (e.g., NPN and PLMN) in NR. when the UE collects information for MHI reporting. According to current specifications, when visiting a cell in an NPN, the UE would not discard previously stored MHI for PLMN cells and does not generate a new MHI for cells of the NPN. Rather, the UE may add the newly visited NPN cell to existing MHI, such that the UE logs and reports MHI consisting of a mixture of PLMN and NPN visited cells. This can cause various problems, issues, and/or difficulties. An object of embodiments of the present disclosure is to address these and other problems, issues, and/or difficulties that can occur for UE MHI reporting, thereby enabling the otherwise- advantageous deployment of NPNs based on 5GS.
Some embodiments include methods (e.g., procedures) for a UE configured to operate in public networks (PNs, e.g., PLMNs) and in non-public networks (NPNs).
These exemplary methods include logging first MHI associated with one or more public networks and/or with visited cells in the one or more public networks. These exemplary methods include logging second MHI associated with one or more non-public networks and/or with visited cells in the one or more non-public networks. These exemplary methods include, after subsequently connecting to a first network, sending to the first network one or more MHI reports that includes one or more of the following: at least part of the logged first MHI, and at least part of the logged second MHI.
In some embodiments, the logged second MHI includes an indication of a duration of time the UE spent outside of a public network and one of the following: an indication that the duration of time was spent in a non-public network, or an indication that the duration of time was spent in a network whose type and/or identity cannot be revealed. In some of these embodiment, when the logged second MHI for a non-public network includes the indication that the duration of time was spent in a non-public network, the logged second MHI also includes an identity of the non- public network.
In some embodiments, the logged first MHI includes an indication of a duration of time the UE spent outside of a non-public network and one of the following: an indication that the duration of time was spent in a public network, or an indication that the duration of time was spent in a network whose type and/or identity cannot be revealed.
In some embodiments, the logged second MHI includes, for each visited cell in a non- public network, an indication of a duration of time the UE spent in the visited cell and one of the following: an indication that the visited cell is part of a non-public network, or an indication that the visited cell is part of a network whose type and/or identity cannot be revealed.
In various embodiments, the one or more MHI reports are arranged according to one of the following:
• a single MHI report that includes at least part of the first MHI but excludes the second MHI;
• a single MHI report that includes at least part of the second MHI but excludes the first MHI;
• a single MHI report that includes at least part of the first MHI and at least part of the second MHI; or • a first MHI report that includes at least part of the first MHI and a second MHI report that includes at least part of the second MHI.
In some of these embodiments, when the first network is a public network, the at least part of the first MHI included in the single MHI report corresponds to one of the following:
• all first MHI logged for all visited public networks and/or all visited cells in public networks; or
• only first MHI logged for the first network and/or visited cells in the first network.
In other of these embodiments, when the first network is a non-public network, the at least part of the second MHI included in the single MHI report or the second MHI report corresponds to one of the following:
• all second MHI logged for all visited non-public networks and/or all visited cells in nonpublic networks; or
• only second MHI logged for the first network and/or visited cells in the first network.
In some of these embodiments, these exemplary methods also include, after sending the single MHI report that includes at least part of the second MHI but excludes the first MHI, discarding the first MHI in response to the earlier of the following events:
• connecting to a second network that is a public network and sending the first MHI to the second network; or
• expiration of a time limit without sending the first MHI to a public network.
In some of these embodiments, for any single MHI report that includes at least part of the first MHI and at least part of the second MHI, at least one entry in the MHI report is associated with respective at least one visited cell,. Each of the at least one entry indicates one of the following for the associated visited cell:
• whether the visited cell is associated with a public network or a non-public network; or
• whether or not information reported for the visited cell should be disclosed to other networks.
In some variants of these embodiments, each entry associated with a visited NPN cell includes a cell global identity (CGI) of the visited NPN cell.
In some embodiments, the first MHI and the second MHI are logged in separate UE variables. In other embodiments, the first MHI and the second MHI are logged in a single UE variable.
In some embodiments, these exemplary methods also include, after subsequently connecting to the first network, receiving from the first network an information request for MHI logged for public networks and for MHI logged for non-public networks. In such case, sending the one or more MHI reports is responsive to the information request. In some of these embodiments, the information request includes a single indication of a request for MHI logged for public networks and for MHI logged for non-public networks. In other of these embodiments, the information request includes a first indication of a request for MHI logged for public networks and a second indication of a request for MHI logged for non-public networks.
In some embodiments, these exemplary methods also include receiving, from the first network or from a second network, a configuration for logging and reporting MHI. In such case logging the first and second MHI and sending the one or more MHI reports are in accordance with the configuration.
Other embodiments include additional methods (e.g., procedures) for a RAN node configured to operate in a first network.
These exemplary methods can include receiving from a UE one or more MHI reports that include one or more of the following logged by the UE:
• first MHI associated with one or more visited public networks and/or with visited cells in the one or more public networks, and
* second MHI associated with one or more non-public networks and/or with visited cells in the one or more non-public networks.
These exemplary methods also include identifying a second RAN node based on the received one or more MHI reports. For example, the second RAN node serves one or more of the cells identified in the one or more MHI reports. These exemplary methods also include sending at least a portion of the received one or more MHI reports to the second RAN node.
In various embodiments, the first and second MBH can have any of the same content, form, and/or structure as the corresponding first and second MHI logged by a UE, as summarized above for UE embodiments. Likewise, the one or more MHI reports can have any of the same content, form, and/or structure as the corresponding one or more MHI reports summarized above for UE embodiments.
In some embodiments, first and second MHI report are sent to the second RAN node as one of the following: separate fields of a single information element (IE) in a message, or separate IES in the message.
In some embodiments, these exemplary methods also include sending to the UE an information request for MHI logged for public networks and for MHI logged for non-public networks. In such case, receiving the one or more MHI reports is responsive to the information request. In some of these embodiments, the information request includes a single indication of a request for MHI logged for public networks and for MHI logged for non-public networks. In other of these embodiments, the information request includes a first indication of a request for MHI logged for public networks and a second indication of a request for MHI logged for non-public networks.
In some embodiments, these exemplary methods also include sending to the UE a configuration for logging and reporting MHI. The contents of the one or more MHI reports are in accordance with the configuration.
In some embodiments, the RAN node and the second RAN node are arranged in dual connectivity with the UE. In other embodiments, a cell served by the second RAN node is a target cell for a UE mobility procedure, and the at least a portion of the received one or more MHI reports is sent to the second RAN node in conjunction with the mobility procedure. In some embodiments, the second RAN node serves one or more of the cells identified in the one or more MHI reports.
Other embodiments include UEs (e.g., wireless devices, etc.) and RAN nodes (e.g., base stations, eNBs, gNBs, ng-eNBs, etc.) configured to perform the operations corresponding to any of the exemplary methods described herein. Other embodiments include non-transitory, computer-readable media storing computer-executable instructions that, when executed by processing circuitry, configure such UEs and RAN nodes to perform operations corresponding to any of the exemplary methods described herein.
These and other embodiments described herein can provide various benefits and/or advantages. For example, embodiments can enable a network (e.g., PLMN) to determine, based on UE MHI, whether the UE was not connected to network cells because it was out of coverage of the network or because it was connected to an NPN but remained in coverage. Furthermore, embodiments can prevent a UE from sending sensitive, confidential, and/or proprietary information about a visited NPN to a PLMN or to another NPN. In embodiments where the UE does provide such information, clear labelling of NPN relation can prevent a PLMN from sharing the information with other PLMNs and/or NPNs. In this manner, embodiments can protect privacy and security of NPNs and their users.
These and other objects, features, and advantages of the present disclosure will become apparent upon reading the following Detailed Description in view of the Drawings briefly described below.
BRIEF DESCRIPTION OF THE DRAWINGS
Figures 1-2 illustrate two high-level views of an exemplary 5G/NR network architecture.
Figure 3 shows exemplary NR user plane (UP) and control plane (CP) protocol stacks.
Figure 4 shows an ASN.l data structure for an exemplary VisitedCelllnfoList mio m^on element (IE). Figure 5 shows an ASN.1 data structure for an exemplary UEInformationRe quest message.
Figure 6 shows an ASN. l data structure for an exemplary UEInformationRe sponse message.
Figures 7-9 show ASN. l data structures for various exemplary VisitedCelllnfoList IES, according to various embodiments of the present disclosure.
Figure 10 shows an ASN. l data structure for an exemplary UEInformationRe quest message, according to various embodiments of the present disclosure.
Figure 11 shows a flow diagram of an exemplary method for a UE (e.g., wireless device), according to various embodiments of the present disclosure.
Figure 12 shows a flow diagram of an exemplary method for a RAN node (e.g., base station, eNB, gNB, ng-eNB, etcf according to various embodiments of the present disclosure.
Figure 13 shows a flow diagram of another exemplary method for a UE (e.g., wireless device), according to various embodiments of the present disclosure.
Figure 14 shows a flow diagram of another exemplary method for a RAN node (e.g., base station, eNB, gNB, ng-eNB, etcf according to various embodiments of the present disclosure.
Figure 15 shows a communication system according to various embodiments of the present disclosure.
Figure 16 shows a UE according to various embodiments of the present disclosure.
Figure 17 shows a network node according to various embodiments of the present disclosure.
Figure 18 shows host computing system according to various embodiments of the present disclosure.
Figure 19 is a block diagram of a virtualization environment in which functions implemented by some embodiments of the present disclosure may be virtualized.
Figure 20 illustrates communication between a host computing system, a network node, and a UE via multiple connections, at least one of which is wireless, according to various embodiments of the present disclosure.
DETAILED DESCRIPTION
Embodiments briefly summarized above will now be described more fully with reference to the accompanying drawings. These descriptions are provided by way of example to explain the subject matter to those skilled in the art and should not be construed as limiting the scope of the subject matter to only the embodiments described herein. More specifically, examples are provided below that illustrate the operation of various embodiments according to the advantages discussed above.
In general, all terms used herein are to be interpreted according to their ordinary meaning to a person of ordinary skill in the relevant technical field, unless a different meaning is expressly defined and/or implied from the context of use. All references to a/an/the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise or clearly implied from the context of use. The operations of any methods and/or procedures disclosed herein do not have to be performed in the exact order disclosed, unless an operation is explicitly described as following or preceding another operation and/or where it is implicit that an operation must follow or precede another operation. Any feature of any embodiment disclosed herein can apply to any other disclosed embodiment, as appropriate. Likewise, any advantage of any embodiment described herein can apply to any other disclosed embodiment, as appropriate.
Furthermore, the following terms are used throughout the description given below:
• Radio Access Node: As used herein, a “radio access node” (or equivalently “radio network node,” “radio access network node,” or “RAN node”) can be any node in a radio access network (RAN) that operates to wirelessly transmit and/or receive signals. Some examples of a radio access node include, but are not limited to, a base station (e.g., gNB in a 3 GPP 5G/NR network or an enhanced or eNB in a 3GPP LTE network), base station distributed components (e.g., CU and DU), a high-power or macro base station, a low-power base station (e.g., micro, pico, femto, or home base station, or the like), an integrated access backhaul (IAB) node, a transmission point (TP), a transmission reception point (TRP), a remote radio unit (RRU or RRH), and a relay node.
• Core Network Node: As used herein, a “core network node” is any type of node in a core network. Some examples of a core network node include, e.g., a Mobility Management Entity (MME), a serving gateway (SGW), a PDN Gateway (P-GW), a Policy and Charging Rules Function (PCRF), an access and mobility management function (AMF), a session management function (SMF), a user plane function (UPF), a Charging Function (CHF), a Policy Control Function (PCF), an Authentication Server Function (AUSF), a location management function (LMF), or the like.
• Wireless Device: As used herein, a “wireless device” (or “WD” for short) is any type of device that is capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices. Communicating wirelessly can involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air. Unless otherwise noted, the term “wireless device” is used interchangeably herein with the term “user equipment” (or “UE” for short), with both of these terms having a different meaning than the term “network node”.
• Radio Node: As used herein, a “radio node” can be either a “radio access node” (or equivalent term) or a “wireless device.”
• Network Node: As used herein, a “network node” is any node that is either part of the radio access network (c.g, a radio access node or equivalent term) or of the core network (c.g, a core network node discussed above) of a cellular communications network. Functionally, a network node is equipment capable, configured, arranged, and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the cellular communications network, to enable and/or provide wireless access to the wireless device, and/or to perform other functions (e.g., administration) in the cellular communications network.
• Node: As used herein, the term “node” (without prefix) can be any type of node that can in or with a wireless network (including RAN and/or core network), including a radio access node (or equivalent term), core network node, or wireless device. However, the term “node” may be limited to a particular type (e.g., radio access node, IAB node) based on its specific characteristics in any given context.
The above definitions are not meant to be exclusive. In other words, various ones of the above terms may be explained and/or described elsewhere in the present disclosure using the same or similar terminology. Nevertheless, to the extent that such other explanations and/or descriptions conflict with the above definitions, the above definitions should control.
Note that the description given herein focuses on a 3 GPP cellular communications system and, as such, 3GPP terminology or terminology similar to 3GPP terminology is oftentimes used. However, the concepts disclosed herein are not limited to a 3GPP system and can be applied to any communication system that may benefit from them. Furthermore, although the term “cell” is used herein, it should be understood that (particularly with respect to 5GNR) beams may be used instead of cells and, as such, concepts described herein apply equally to both cells and beams.
Figure 1 illustrates a high-level view of an exemplary 5G network architecture, consisting of a Next Generation Radio Access Network (NG-RAN, 199) and a 5G Core (5GC, 198). The NG-RAN can include one or more gNodeB’s (gNBs) connected to the 5GC via one or more NG interfaces, such as gNBs (100, 150) connected via respective interfaces (102, 152). More specifically, the gNBs can be connected to one or more Access and Mobility Management Functions (AMFs) in the 5GC via respective NG-C interfaces and to one or more User Plane Functions (UPFs) in 5GC via respective NG-U interfaces. The 5GC can include various other network functions (NFs), such as Session Management Function(s) (SMF).
Although not shown, in some deployments the 5GC can be replaced by an Evolved Packet Core (EPC, 198), which conventionally has been used together with a Long-Term Evolution (LTE) Evolved UMTS RAN (E-UTRAN). In such deployments, gNBs (e.g., 100, 150) can connect to one or more Mobility Management Entities (MMEs) in the EPC via respective Sl-C interfaces and to one or more Serving Gateways (SGWs) in EPC via respective NG-U interfaces.
In addition, the gNBs can be connected to each other via one or more Xn interfaces, such as Xn interface (140) between gNBs (100, 150). The radio technology for the NG-RAN is often referred to as “New Radio” (NR). With respect to the NR interface to UEs, each of the gNBs can support frequency division duplexing (FDD), time division duplexing (TDD), or a combination thereof. Each of the gNBs can serve a geographic coverage area including one or more cells and, in some cases, can also use various directional beams to provide coverage in the respective cells. In general, a DL “beam” is a coverage area of a network-transmitted reference signal (RS) that may be measured or monitored by a UE.
The NG-RAN is layered into a Radio Network Layer (RNL) and a Transport Network Layer (TNL). The NG-RAN logical nodes and interfaces between them, is defined as part of the RNL. For each NG-RAN interface (NG, Xn, Fl) the related TNL protocol and the functionality are specified. The TNL provides services for user plane transport and signaling transport.
NG RAN logical nodes (e.g., gNB 100) include a Central Unit (CU or gNB-CU, e.g., 110) and one or more Distributed Units (DU or gNB-DU, e.g., 120, 130). CUs are logical nodes that host higher-layer protocols and perform various gNB functions such controlling the operation of DUs. DUs are decentralized logical nodes that host lower layer protocols and can include, depending on the functional split option, various subsets of the gNB functions. Each CU and DU can include various circuitry needed to perform their respective functions, including processing circuitry, communication interface circuitry (e.g., transceivers), and power supply circuitry.
A gNB-CU connects to one or more gNB-DUs over respective Fl logical interfaces (e.g., 122 and 132 shown in Figure 1). However, a gNB-DU can be connected to only a single gNB-CU. The gNB-CU and its connected gNB-DU(s) are only visible to other gNBs and the 5GC as a gNB. In other words, the Fl interface is not visible beyond gNB-CU.
Centralized control plane protocols (e.g., PDCP-C and RRC) can be hosted in a different CU than centralized user plane protocols (e.g., PDCP-U). For example, a gNB-CU can be divided logically into a CU-CP function (including RRC and PDCP for signaling radio bearers) and CULT? function (including PDCP for UP). A single CU-CP can be associated with multiple CU-UPs in a gNB. The CU-CP and CU-UP communicate with each other using the El-AP protocol over the El interface. Furthermore, the Fl interface between CU and DU (see Figure 1) is functionally split into Fl-C between DU and CU-CP and Fl-U between DU and CU-UP. Three deployment scenarios for the split gNB architecture shown in Figure 1 are CU-CP and CU-UP centralized, CU-CP distributed/CU-UP centralized, and CU-CP centralized/CU-UP distributed.
Figure 2 shows another high-level view of an exemplary 5G network architecture, including an NG-RAN (299) and a 5GC (298). As shown in the figure, the NG-RAN can include gNBs (e.g., 210a,b) and ng-eNBs (e.g., 220a, b) that are interconnected with each other via respective Xn interfaces. The gNBs and ng-eNBs are also connected via the NG interfaces to the 5GC, more specifically to Access and Mobility Management Functions (AMFs, e.g., 230a, b) via respective NG-C interfaces and to User Plane Functions (UPFs, e.g., 240a, b) via respective NG- U interfaces. Moreover, the AMFs can communicate with Policy Control Functions (PCFs, e.g., 250a, b) and Network Exposure Functions (NEFs, e.g., 260a, b).
Each of the gNBs can support the NR radio interface including frequency division duplexing (FDD), time division duplexing (TDD), or a combination thereof. Each of ng-eNBs can support the fourth generation (4G) Long-Term Evolution (LTE) radio interface. Unlike conventional LTE eNBs, however, ng-eNBs connect to the 5GC via the NG interface. Each of the gNBs and ng-eNBs can serve a geographic coverage area including one or more cells (e.g., 211a- b, 221a-b). Depending on the cell in which it is located, a UE (205) can communicate with the gNB or ng-eNB serving that cell via the NR or LTE radio interface, respectively. Although Figure 2 shows gNBs and ng-eNBs separately, it is also possible that a single NG-RAN node provides both types of functionality.
In addition to providing coverage via cells as in LTE, NR networks also provide coverage via “beams.” In general, a downlink (DL, i.e., network to UE) “beam” is a coverage area of a network-transmitted reference signal (RS) that may be measured or monitored by a UE. In NR, for example, RS can include any of the following: synchronization signal/PBCH block (SSB), channel state information RS (CSLRS), tertiary reference signals (or any other sync signal), positioning RS (PRS), demodulation RS (DMRS), phase-tracking reference signals (PTRS), etc. In general, SSB is available to all UEs regardless of the state of their connection with the network, while other RS (e.g., CSLRS, DM-RS, PTRS) are associated with specific UEs that have a network connection.
Figure 3 shows an exemplary configuration of NR user plane (UP) and control plane (CP) protocol stacks between a UE (310), a gNB (320), and an AMF (330), such as those shown in Figures 1-2. Physical (PHY), Medium Access Control (MAC), Radio Link Control (RLC), and Packet Data Convergence Protocol (PDCP) layers between the UE and the gNB are common to UP and CP. PDCP provides ciphering/deciphering, integrity protection, sequence numbering, reordering, and duplicate detection for both CP and UP. In addition, PDCP provides header compression and retransmission for UP data.
On the UP side, Internet protocol (IP) packets arrive to PDCP as service data units (SDUs), and PDCP creates protocol data units (PDUs) to deliver to RLC. The Service Data Adaptation Protocol (SDAP) layer handles quality-of-service (QoS) including mapping between QoS flows and Data Radio Bearers (DRBs) and marking QoS flow identifiers (QFI) in UU and DL packets. RLC transfers PDCP PDUs to MAC through logical channels (LCH). RLC provides error detection/correction, concatenation, segmentation/reassembly, sequence numbering, reordering of data transferred to/from the upper layers. MAC provides mapping between LCHs and PHY transport channels, LCH prioritization, multiplexing into or demultiplexing from transport blocks (TBs), hybrid ARQ (HARQ) error correction, and dynamic scheduling (on gNB side). PHY provides transport channel services to MAC and handles transfer over the NR radio interface, e.g., via modulation, coding, antenna mapping, and beam forming.
On CP side, the non-access stratum (NAS) layer is between UE and AMF and handles UE/gNB authentication, mobility management, and security control. RRC sits below NAS in the UE but terminates in the gNB rather than the AMF. RRC controls communications between UE and gNB at the radio interface as well as the mobility of a UE between cells in the NG-RAN. RRC also broadcasts system information (SI) and performs establishment, configuration, maintenance, and release of DRBs and Signaling Radio Bearers (SRBs) and used by UEs. Additionally, RRC controls addition, modification, and release of carrier aggregation (CA) and dual -connectivity (DC) configurations for UEs, and performs various security functions such as key management.
After a UE is powered ON it will be in the RRCJODLE state until an RRC connection is established with the network, at which time the UE will transition to RRC CONNECTED state e.g., where data transfer can occur). The UE returns to RRCJODLE after the connection with the network is released. In RRC IDLE state, the UE’s radio is active on a discontinuous reception ( DRX) schedule configured by upper layers. During DRX active periods (also referred to as “DRX On durations”), an RRC IDLE UE receives SI broadcast in the cell where the UE is camping, performs measurements of neighbor cells to support cell reselection, and monitors a paging channel on PDCCH for pages from 5GC via gNB. An NR UE in RRC__IDLE state is not known to the gNB serving the cell where the UE is camping. However, NR RRC includes an RRC_INACTIVE state in which a UE is known (e.g., via UE context) by the serving gNB. RRC INACTIVE has some properties similar to a “suspended” condition used in LTE.
Seamless mobility is a key feature of 3GPP radio access technologies (RATs). In general, a RAN (e.g., NG-RAN) configures a UE to perform and report radio resource management (RRM) measurements to assist network-controlled mobility decisions, such as for handover from a serving cell to a neighbor cell. Seamless handovers ensure that the UE moves around in the coverage area of different cells without excessive interruption to data transmission. However, there will be scenarios when the network fails to handover the UE to the “correct” neighbor cell in time, which can cause the UE to declare radio link failure (RLF) or handover failure (HOF). This can occur before the UE sends a measurement report in a source cell, before the UE receives a handover command to a target cell, shortly after the UE executes a successful handover to the target cell, or upon a HOF to the target cell (e.g., upon expiry of timer T304, started when the UE starts synchronization with the target cell).
An RLF reporting procedure was introduced as part of the mobility robustness optimization (MRO) in LTE Rel-9. In this procedure, a UE logs relevant information at the time of RLF and later reports such information to the network via a target cell to which the UE ultimately connects (e.g., after reestablishment). The reported information can include RRM measurements of various neighbor cells prior to the mobility operation (e.g., handover). 3GPP Rel-17 introduced a successful handover report (SHR) whereby a UE reports various information about a successful handover to a target cell.
For example, both RLF reports and SHRs can include information about the UE’s random access towards the target cell. The random access (RA) information can include the bandwidth part (BWP) in which the RA was attempted, DL pathloss experienced at the time of initiating the RA procedure, information related to each RA preamble transmission attempt (e.g., whether contention was experienced, number of preamble transmission attempts in a certain SSB or CSL RS, etc.).
3GPP TS 38.331 (vl7.1.0) section 5.7.10.4 describes UE actions upon successful completion of a RA procedure, including various RA information collected and stored in UE variable VarRA-Report. A UE may release (i.e., discard) VarRA-Report 48 hours after the last successful RA procedure or failed/successful on-demand SI acquisition procedure for which information was added to the stored VarRA-Report.
Mobility history information (MHI) was introduced in LTE and is also supported in NR. As part of its MHI measurements, a UE stores a cell identifier of its current serving cell and also stores information about to how long the UE has stayed in this cell. The UE keeps such MHI for up to 16 previous serving cells. UE MHI also includes information about how long the UE has been out of the coverage.
3GPP TS 38.331 (vl7.1.0) section 5.7.9 describes UE MHI collection in more detail, including how MHI is accumulated by the UE in RRC CONNECTED, RRC IDLE, and RRC IN ACTIVE states. In response to camping in or connecting to a different cell (“visited cell”), the UE includes an entry for the visited cell in visitedCelllnfoList of the UE variable VarMobilityHistory Report possibly after removing the oldest entry, if necessary.
3GPP TS 38.331 (vl7.1.0) section 6.3.4 specifies the VisitedCelllnfoList information element (IE), which is also shown as an ASN.1 data structure in Figure 4. This IE includes MHI of up to 16 most recently visited primary cells or time spent in any cell selection state and/or camped on any cell state in NR or E-UTRA and, in case of Dual Connectivity, the MHI of maxPSCellHistory most recently visited primary secondary cell group cells across all primary cells included in the VisitedCelllnfoList . The most recently visited cell is stored first in the list. The list includes cells visited in RRC IDLE, RRC INACTIVE and RRC CONNECTED states for NR and RRC IDLE and RRC CONNECTED for LTE/E-UTRA.
A UE can indicate availability of MHI via the mobilityHistoryAvail field in various RRC messages, including RRCSetupComplete, RRCReestablishmentComplete , and RRCResume- Complete. After being notified of MHI availability, the network can initiate a UE Information procedure to obtain the MHI from the UE. 3GPP TS 38.331 (vl7.1.0) section 5.7.10 (including subsections) specifies the UE Information procedure in more detail.
The network initiates this procedure by sending a UEInformationRe quest message to the UE. Figure 5 shows an ASN.l data structure for an exemplary UEInformationRequest message, which is further described in 3GPP TS 38.331 (vl7.1.0) section 6.3.4. Note that the mobilityHistoryReportReq-rl6 field in the UEInformationRe quest-r 16-IEs is an optional field, but if present it is set to “true” indicating that the network is requesting available MHI from the UE. Its absence indicates that the network is not requesting MHI. A similar convention is used for the ra-ReportReq-r!6 field, which relates to RA information. In addition, the message includes fields for the network to request various other information following similar conventions.
Upon receiving the UEInformationRequest message, the UE responds with a UEInformationRe sponse message that includes the requested information. Figure 6 shows an ASN.l data structure for an exemplary UEInformationRe sponse message, which is further described in 3GPP TS 38.331 (vl7.1.0) section 6.3.4. Note that each report field (e.g., ra- ReportList-rl6, rlf-Report-r 16. mobilityHistoryReport-r 16. etc.) is optional but if included, it contains various relevant information logged by the UE.
As mentioned above, 3GPP-specified technology traditionally has been deployed in PLMNs (also referred to as public networks, PNs) that are accessible to any user with a valid subscription. 3GPP Rel-16 introduced support for Non-Public Networks (NPN), as described in 3GPP TS 23.501 (v!6.5.0). An example NPN is a factory or other industrial facility that deploys its own 5GS to provide connectivity for both equipment and workers, with non-affiliated users restricted from access.
An NPN can be deployed as a Stand-alone Non-Public Network (SNPN) when not relying on network functions provided by a PLMN. An SNPN is identified by a PLMN ID and network ID (NID) broadcast in SIB1. Alternately, an NPN can be deployed as a Public Network Integrated (PNI) NPN when relying on functions provided by a PLMN. A PNI NPN is identified by a PLMN ID and Closed Access Group (C AG) identifier broadcast in SIB 1.
Even so, existing solutions specify UE MHI collection only in PLMNs. Moreover, there is no way to distinguish between network types (e.g., NPN and PLMN) in NR. when the UE collects information for MHI reporting. According to current specifications, when visiting a cell in an NPN, the UE would not discard previously stored MHI for PLMN cells and does not generate a new MHI for cells of the NPN. Rather, the UE may add the newly visited NPN cell to existing MHI, such that the UE logs and reports MHI consisting of a mixture of PLMN and NPN visited cells. This can cause various problems, issues, and/or difficulties.
For example, this operation by the UE may expose sensitive, confidential, and/or proprietary information about a visited NPN to a PLMN or to another NPN. This can put at risk the privacy of the UEs connected to the NPN. As a more specific example, if an SNPN is managed so to avoid interaction and information exposure with other networks, the UE collecting and reporting MHI for a visited cell in the SNPN can expose cell identities, locations, coverage details, etc. of the SNPN to other networks. This can create external security risks for the SNPN and its users.
Embodiments of the present disclosure address these and other problems, issues, and/or difficulties by providing techniques in which a UE collects visited cell information for MHI per network type, i.e., visited PN cells in PN-related MHI and visited NPN cells information in NPN-related MHI. In some embodiments, the UE also logs time spent in each network as well as a flag indicating that UE spent the logged time in an NPN. In other embodiments, the UE logs the network identity in each MHI so that it can be reported to the proper network. In other embodiments, the UE logs the time spent in another network without specifying which network that was. In other embodiments, the UE can log visited NPN cells in PN-related MHI but also includes cell global identity (CGI) of the visited cells in addition to or instead of physical cell identity (PCI) and frequency information.
Disclosed embodiments can provide various benefits and/or advantages. For example, embodiments can enable a network (e.g., PLMN) to determine, based on UE MHI, whether the UE was not connected to network cells because it was out of coverage of the network or because it was connected to an NPN but remained in coverage. Furthermore, embodiments can prevent a UE from sending sensitive, confidential, and/or proprietary information about a visited NPN to a PLMN or to another NPN. In embodiments where the UE does provide such information, clear labelling of NPN relation can prevent a PLMN from sharing the information with other PLMNs and/or NPNs. In this manner, embodiments can protect privacy and security of NPNs and their users.
Some embodiments include methods performed by a UE capable of mobility between public and non-public networks (e.g., PLMNs and NPNs). In such embodiments, the UE is configured by the network (e.g., PLMN) with instructions for handling visited cell information for NPNs that could be potentially included in UE -reported MHI. In some embodiments, the UE may also be configured with instructions for handling visited cell information for PLMNs. Upon visiting cells in an NPN or a PLMN, the UE manages the collection of MHI in accordance with the configured instructions.
In some embodiments, the UE is configured to not include MHI for visited cells associated with different network types (i.e., public and non-public) or different networks of the same type (e.g., two NPNs) in the same MHI report. This restriction can prevent conveying sensitive, confidential, and/or proprietary information about a visited NPN to a PLMN or to another NPN. The information protected in this manner can include, for example, measurements and other information that enables an entity to track users in the NPN.
In some variants, this restriction may be limited to not including visited NPN cells in an MHI report sent to a PN or another NPN, such that the UE may include visited PN cells in an MHI report sent to an NPN.
In some embodiments, the configuration may indicate one or more particular networks (e.g., PLMN IDs) to which the restriction policy applies. In some embodiments, the configuration may indicate particular types of cell information that should be included or excluded from a MHI report. For example, in the case of dual connectivity (DC) with a master cell group (MCG) and a secondary cell group (SCG), the configuration may indicate whether identifiers of visited primary SCG cells (PSCells) should be included along with identifiers of visited PCells (i.e., of MCG).
In some embodiments, the UE logs the time spent in an NPN and an indication that the time was spent in an NPN. In other embodiments, the UE logs time spent in a network whose information should not be revealed, without providing information identifying the particular network (or network type) that the UE visited.
In other embodiments, the UE is configured to include information about visited cells associated with different network types (i.e., public and non-public) or different networks of the same type (e.g., two NPNs) in the same MHI report. In such case, the UE is also configured to include in MHI the cell global identities (CGIs) associated with visited NPN cells, which also includes information about visited PN cells.
In other embodiments, the UE is configured to provides MHI for a particular network (which may be a PLMN, SNPN, or PNI-NPN) only when served by that network, with the provided MHI only including visited cells of the particular network. In such case, the UE has to log visited cell information along with the network identity (e.g., PLMN ID).
To summarize the above, once configured, a UE stores up to a maximum number of cells (e.g., PCells) recently visited in RRC IDLE, RRC INACTIVE, and RRC CONNECTED states associated with a network type (e.g., PN or NPN) according to the configuration. A UE capable of mobility between PN and NPN follows the configuration and policy options described above when reporting PN and/or NPN information in MHI.
Figure 7 shows an ASN. l data structure for an exemplary VisitedCelllnfoList IE, according to some embodiments of the present disclosure. The VisitedCelllnfoList includes up to the maximum number (16) of VisitedCelllnfo IES, each of which includes information for a visited cell. In these embodiments, each VisitedCelllnfo IE includes a networkType-r!8 field which can take on two different enumerated values: “PN”, which indicates that the visited cell is associated with a public network, and “SNPN” which indicates that the visited cell is associated with an SNPN.
Figure 8 shows an ASN. l data structure for another exemplary VisitedCelllnfoList IE, according to other embodiments of the present disclosure. In these embodiments, each VisitedCelllnfo IE includes a privateNetwork-r!8 field that when present indicates the visited cell is associated with an NPN and when absent indicates that the visited cell is associated with a public network.
Figure 9 shows an ASN. l data structure for another exemplary VisitedCelllnfoList IE, according to other embodiments of the present disclosure. In these embodiments, each VisitedCelllnfo IE includes only one following (by choice): an nr-CellId-r!6 field including information about a visited NR cell; an eutra-CellId-rl6 field including information about a visited LTE cell; and a notDisclosedCelllnfo field that indicates information about the visited cell cannot be disclosed (but does not specify the reason, such as being part of a SNPN).
Embodiments can also be realized as text included in a 3GPP specification. For example, the following shows some exemplary text that can be added to the description of UE MHI procedures in 3GPP TS 38.331 (17.1.0), with ellipses denoted existing text omitted for brevity. *** Begin proposed 3 GPP specification text *** 5.7.9 Mobility History Information
5.7.9.1 General This procedure specifies how the mobility history information is stored by the UE, covering RRC IDLE, RRC INACTIVE and RRC CONNECTED.
5.7.9.2 Initiation
If the UE supports storage of mobility history information, the UE shall: l>upon entering NR PN (in RRC CONNECTED or RRC IDLE) while previously using another network type e.g., SNPN; or: l>upon entering NR SNPN (in RRC CONNECTED or RRC IDLE) while previously using another network type e.g., PN:
2> include an entry in variable VarMobilityHistoryReport possibly after removing the oldest entry, if necessary, according to following:
3>set the field timeSpent of the entry as the time spent outside of current network type;
3> set the field NetworkType of the entry as the selected network type where the UE was connected (in RRC CONNECTED, RRC IDLE or RRC INACTIVE) before entering the current network type.
*** End proposed 3 GPP specification text ***
In embodiments where the UE includes visited primary cells of first and second network types (i.e., PN and NPN) in the same MHI report, the UE may be configured (or it may be specified) to log CGI information for cells of the second network type in the MHI report sent to a network of the first network type. The following shows exemplary text according to these embodiments that can be added to the description of UE MHI procedures in 3GPP TS 38.331 (17.1.0), with ellipses denoted existing text omitted for brevity.
*** Begin proposed 3 GPP specification text ***
5.7.9 Mobility History Information
5.7.9.1 General
This procedure specifies how the mobility history information is stored by the UE, covering RRC IDLE, RRC INACTIVE and RRC CONNECTED.
5.7.9.2 Initiation
If the UE supports storage of mobility history information, the UE shall:
1> Upon change of suitable cell, consisting of SNPN PCell in RRC CONNECTED (for NR cell) or serving cell in RRC INACTIVE (for NR cell) or in RRC IDLE (for NR or E- UTRA cell), to another NR, or when entering any cell selection' state from 'camped normally' state in NR or when entering 'any cell selection' state from a suitable cell in RRC CONNECTED state in NR: 2> include an entry in visitedCelllnfoList of the variable VarMobilityHistoryReport possibly after removing the oldest entry, if necessary, according to following:
3>include the global cell identity of the previous SNPN PCell/serving cell in the field visitedCellld of the entry;
*** End proposed 3 GPP specification text ***
In other embodiments, the UE logs information about visited primary cells of first and second network types (e.g., PN and NPN) in different UE variables. For example, the UE logs information about visited PN cells in the existing VarMobilityHistoryReport and logs information about visited NPN cells in a new variable, e.g., VarMobilityHistoryNPNReport or similar.
In some variants, the UE reports information about visited NPN cells (e.g., VarMobilityHistoryNPNReport) to the NPN after registering with that network. In other variants, the UE reports information about visited NPN cells (e.g., VarMobilityHistoryNPNReport) to a PLMN upon request by that network, e.g., based on a confidentiality agreement between PLMN and NPN operators.
In some embodiments, the UE retains the VarMobilityHistoryReport with information about visited PN cells after leaving the PN (e.g., registering with an NPN) and deletes it if the UE does not return to the PN within a time limit.
Figure 10 shows an ASN. l data structure for an exemplary UEInformationRe quest message, according to some embodiments of the present disclosure. This message includes an optional mobilityHistoryReportReqSNPN-rl6 field, which if present indicates that the network requesting available SNPN MHI from the UE. Its absence indicates that the network is not requesting SNPN MHI. Note that this field is in addition to the mobilityHistoryReportReq-rl6 field by which the network requests available PN MHI from the UE, in the manner described above in relation to Figure 5. The following shows exemplary text according to these embodiments that can be added to the description of the UE Information procedure in 3GPP TS 38.331 (17.1.0), with ellipses denoted existing text omitted for brevity.
*** Begin proposed 3 GPP specification text ***
5.7.10 UE Information
The UE information procedure is used by the network to request the UE to report information.
5.7.9.1 General
This procedure specifies how the mobility history information is stored by the UE, covering RRC IDLE, RRC INACTIVE and RRC CONNECTED.
5.7.10.2 Initiation The network initiates the procedure by sending the UEInformationRequest message. The network should initiate this procedure only after successful security activation.
5.7.10.3 Reception of the UEInformationRequest message
Upon receiving the UEInformationRequest message, the UE shall, only after successful security activation:
1> if the mobilityHistoryReportReqforSNPN is set to true '.
2> include the mobilityHistoryReport and set it to include visitedCelllnfoList from VarMobilityH istoryReportSNPN,'
2> include in the mobilityHistoryReport an entry for the current SNPN PCell, possibly after removing the oldest entry if required, and set its fields as follows:
3>set visitedCellld to the global cell identity or the physical cell identity and carrier frequency of the current PCell:
1> if the logMeasReport is included in the UEInformationResponse'.
2> submit the UEInformationResponse message to lower layers for transmission via SRB2;
2> discard the logged measurement entries included in the logMeasInfoList from
Var LogMeasReport upon successful delivery of the UEInformationResponse message confirmed by lower layers; l>else:
2> submit the UEInformationResponse message to lower layers for transmission via SRB1. *** End proposed 3 GPP specification text ***
Other embodiments include methods performed by a RAN node. Upon receiving an MHI report from a UE containing information about visited cells in an NPN (e.g., mobilityHistoryReportNPN IE), the RAN node identifies a second RAN node based on the cell identities in the MHI and sends the received MHI to the identified second RAN node, which may use it for mobility robustness optimization (MRO), coverage and capacity optimization (CCO), or other improvements.
In some embodiments, the UE may be in dual connectivity, with the RAN node as the MN and the second RAN node as the SN. In such case, the MN sends the MHI received from the UE to the SN. Alternately, the SN can receive the MHI from the UE and send it to the MN.
In other embodiments, the second RAN node may be the target node for a mobility procedure (e.g., handover) involving the UE that generated the MHI. In such case, the RAN node can send the received MHI to the second RAN node during the mobility procedure, e.g., as part of a handover request message. The following text illustrates how an example of how various embodiments can be specified in 3GPP TS 38.473 (vl7.1.0), based on the addition of the optional NR Mobility History Report for NPN field. 3GPP TS 38.423 (vl7.1.0), which specifies the Xn interface between RAN nodes, can be modified in a similar manner. For example, the UE History Information IE defined in 3GPP TS 38.423 (vl7.1.0) can be modified to include a new container with NPN information.
*** Begin proposed 3 GPP specification text ***
9.2.3.110 UE History Information from the UE
This IE contains information about mobility history report for a UE.
Figure imgf000023_0001
*** End proposed 3 GPP specification text ***
Alternately, the information in NR Mobility History Report for NPN can be included in a separate IE, e.g., Non-Public Network UE History Information. The following text illustrates how an example of how these embodiments can be specified in 3GPP TS 38.473 (vl7.1.0) and 38.423 (vl7.1.0), based on the addition of the optional NR Mobility History Report for NPN IE.
*** Begin proposed 3 GPP specification text ***
9.3.1.x Non-Public Network UE History Information
Figure imgf000023_0002
*** End proposed 3 GPP specification text *** In other embodiments the existing UE History Information IE (as defined in 3GPP TS 38.423 (vl7.1.0)) may be modified to account for the policies applied by the UE at collection and reporting of the MHI (e.g., as illustrated in Figure 9). The following text illustrates how an example of how these embodiments can be specified in 3GPP TS 38.423 (vl7.1.0). *** Begin proposed 3 GPP specification text ***
9.2.3.64 UE History Information
The UE History Information IE contains information about cells that a UE has been served by in active state prior to the target cell. The overall mechanism is described in TS 36.300 [12], NOTE: The definition of this IE is aligned with the definition of the UE History Information IE in TS 38.413 [5],
Figure imgf000024_0001
Figure imgf000024_0002
9.2.3.65 Last Visited Cell Information
The Last Visited Cell Information may contain cell specific information.
Figure imgf000025_0001
*** End proposed 3 GPP specification text ***
The embodiments described above can be further illustrated with reference to Figures 11- 14, which depict exemplary methods (e.g., procedures) performed by UEs or by RAN nodes. Put differently, various features of the operations described below correspond to various embodiments described above. Some of the exemplary methods shown in Figures 11-14 can be complementary to each other such that they can be used cooperatively to provide benefits, advantages, and/or solutions to problems described herein. Although the exemplary methods are illustrated in Figures 11-14 by specific blocks in particular orders, the operations corresponding to the blocks can be performed in different orders than shown and can be combined and/or divided into operations having different functionality than shown. Optional blocks and/or operations are indicated by dashed lines.
More specifically, Figure 11 illustrates an exemplary method (e.g., procedure) for a user equipment (UE) configured to operate in public networks (PN) and in non-public networks (NPN), according to various embodiments of the present disclosure. For example, the exemplary method shown in Figure 11 can be performed by a UE (e.g., wireless device) described herein with reference to other figures.
The exemplary method can include the operations of block 1120, where while visiting one or more cells in one or more PNs, the UE can log first MHI associated with the visited PN cells. The exemplary method can also include the operations of block 1130, where while visiting one or more cells in one or more NPNs, the UE can log second MHI associated with the visited NPN cells. The exemplary method can also include the operations of block 1150, where after subsequently connecting to a first network, the UE can send to the first network one or more MHI reports that includes one or more of the following: at least part of the first MHI, and at least part of the second MHI.
In some embodiments, when the first network is a PN, the one or more MHI reports are arranged according to one of the following:
• a single MHI report that includes at least part of the first MHI but excludes the second MHI;
• a single MHI report that includes the first MHI and the second MHI; or
• a first MHI report that includes the first MHI and a second MHI report that includes the second MHI.
In some of these embodiments, the at least part of the first MHI included in the single MHI report corresponds to one of the following:
• all first MHI collected for all visited PN cells; or
• only first MHI collected for visited PN cells associated with the first network.
In some embodiments, when the first network is an NPN, the one or more MHI reports are arranged according to one of the following:
• a single MHI report that includes at least part of the second MHI but excludes the first MHI;
• a single MHI report that includes the first MHI and the second MHI; or
• a first MHI report that includes the first MHI and a second MHI report that includes at least part of the second MHI.
In some of these embodiments, the at least part of the second MHI included in the single MHI report or the second MHI report corresponds to one of the following:
• all second MHI collected for all visited NPN cells; or
• only second MHI collected for visited NPN cells associated with the first network.
In some of these embodiments, the exemplary method can also include the operations of block 1160, where after sending the single MHI report that includes at least part of the second MHI but excludes the first MHI (e.g., in block 1150), the UE can delete the first MHI in response to the earlier of the following events:
• connecting to a second network that is a PN and sending the first MHI to the second network; or • expiration of a time limit without sending the first MHI to a PN.
In some embodiments, for any single MHI report that includes at least part of the first MHI and at least part of the second MHI, each MHI report entry corresponds to a visited cell and indicates one of the following for the visited cell:
• whether the visited cell is associated with a PN or an NPN (e.g., as illustrated in Figures 7-8); or
• whether or not information reported for the visited cell should be disclosed to other networks (e.g., as illustrated in Figure 9).
In some of these embodiments, each MHI report entry corresponding to a visited NPN cell includes a cell global identity (CGI) of the visited NPN cell.
In some embodiments, each MHI report entry corresponding to a visited NPN cell includes a first indication of a duration of time the UE spent in the visited NPN cell and a second indication that the visited NPN cell is associated with one of the following: an NPN, or a network and/or a network type that cannot be revealed.
In different embodiments, the first MHI and the second MHI can be logged in separate UE variables or in a single UE variable.
In some embodiments, the exemplary method can also include the operations of block 1140, where after subsequently connecting to the first network, the UE can receive from the first network an information request for MHI logged for PNs and MHI logged for NPNs. In such case, sending the one or more MHI reports in block 1150 is responsive to the information request. In various embodiments, the information request includes one of the following:
• a single indication of a request for MHI logged for PNs and for MHI logged for NPNs; or
• a first indication of a request for MHI logged for PNs and a second indication of a request for MHI logged for NPNs.
In some embodiments, the exemplary method can also include the operations of block 1110, where the UE can receive, from the first network or from a second network, a configuration for logging and reporting MHI. In such case, logging the first and second MHI (e.g., in blocks 1120-1130) and sending the one or more MHI reports (e.g., in block 1150) are in accordance with the configuration.
In addition, Figure 12 illustrates an exemplary method e.g., procedure) for a RAN node in a first network, according to various embodiments of the present disclosure. For example, the exemplary method shown in Figure 12 can be performed by an RAN node (e.g., base station, eNB, gNB, ng-eNB, etc.) such as described elsewhere herein.
The exemplary method can include the operations of block 1230, where the RAN node can receive from a UE one or more MHI reports that include one or more of the following: • at least part of first MHI logged by the UE while visiting cells in one or more public networks (PNs), and
& at least part of second MHI logged by the UE while visiting cells in one or more nonpublic networks (NPNs);
The exemplary method can also include the operations of block 1240, where the RAN node can identify a second RAN node based on the received one or more MHI reports. For example, the second RAN node serves one or more of the cells identified in the one or more MHI reports. The exemplary method can also include the operations of block 1250, where the RAN node can send at least a portion of the received one or more MHI reports to the second RAN node.
In some embodiments, when the first network is a PN, the one or more MHI reports are arranged according to one of the following:
• a single MHI report that includes at least part of the first MHI but excludes the second MHI;
• a single MHI report that includes the first MHI and the second MHI; or
• a first MHI report that includes the first MHI and a second MHI report that includes the second MHI.
In some of these embodiments, the at least part of the first MHI included in the single MHI report corresponds to one of the following:
• all first MHI collected for all visited PN cells; or
• only first MHI collected for visited PN cells associated with the first network.
In some embodiments, when the first network is an NPN, the one or more MHI reports are arranged according to one of the following:
• a single MHI report that includes at least part of the second MHI but excludes the first MHI;
• a single MHI report that includes the first MHI and the second MHI; or
• a first MHI report that includes the first MHI and a second MHI report that includes at least part of the second MHI.
In some of these embodiments, the at least part of the second MHI included in the single MHI report or the second MHI report corresponds to one of the following:
• all second MHI collected for all visited NPN cells; or
• only second MHI collected for visited NPN cells associated with the first network.
In some embodiments, for any single MHI report that includes at least part of the first MHI and at least part of the second MHI, each MHI report entry corresponds to a visited cell and indicates one of the following for the visited cell: • whether the visited cell is associated with a PN or an NPN (e.g., as illustrated in Figures 7-8); or
• whether or not information reported for the visited cell should be disclosed to other networks (e.g., as illustrated in Figure 9).
In some of these embodiments, each MHI report entry corresponding to a visited NPN cell includes a cell global identity (CGI) of the visited NPN cell.
In some embodiments, each MHI report entry corresponding to a visited NPN cell includes a first indication of a duration of time the UE spent in the visited NPN cell and a second indication that the visited NPN cell is associated with one of the following: an NPN, or a network and/or a network type that cannot be revealed.
In some embodiments, the exemplary method can also include the operation of block 1220, where the RAN node can send to the UE an information request for MHI logged for PNs and MHI logged for NPNs. In such case, receiving the one or more MHI reports in block 1230 is responsive to the information request. In various embodiments, the information request includes one of the following:
• a single indication of a request for MHI logged for PNs and for MHI logged for NPNs; or
• a first indication of a request for MHI logged for PNs and a second indication of a request for MHI logged for NPNs.
In some embodiments, the exemplary method can also include the operations of block 1210, where the RAN node can send to the UE a configuration for logging and reporting MHI. In such case, the contents of the received one or more MHI reports are in accordance with the configuration.
In some embodiments, the RAN node and the second RAN node are arranged in dual connectivity with the UE. In other embodiments, a cell served by the second RAN node is a target cell for a UE mobility procedure (e.g., handover), and the at least a portion of the received one or more MHI reports are sent to the second RAN node in conjunction with the mobility procedure (e.g., in a handover request).
In some embodiments, the one or more MHI reports include a first MHI report that includes the at least a part of the first MHI and a second MHI report that includes the at least a part of the second MHI. In such embodiments, the first and second MHI reports are sent to the second RAN node as one of the following: separate fields of a single IE in a message, or separate IES in the message. Various examples of these arrangements were described above in the context of text for 3GPP specifications.
In addition, Figure 13 illustrates another exemplary method e.g., procedure) for a UE configured to operate in public networks and in non-public networks, according to various embodiments of the present disclosure. For example, the exemplary method shown in Figure 13 can be performed by a UE (e.g., wireless device) described herein with reference to other figures.
The exemplary method includes the operations of block 1320, where the UE can log first mobility history information (MHI) associated with one or more public networks and/or with visited cells in the one or more public networks. The exemplary method also includes the operations of block 1330, where the UE can log second MHI associated with one or more nonpublic networks and/or with visited cells in the one or more non-public networks. The exemplary method includes the operations of block 1350, where after subsequently connecting to a first network, the UE can send to the first network one or more MHI reports that includes one or more of the following: at least part of the logged first MHI, and at least part of the logged second MHI.
In some embodiments, the logged second MHI includes an indication of a duration of time the UE spent outside of a public network and one of the following: an indication that the duration of time was spent in a non-public network, or an indication that the duration of time was spent in a network whose type and/or identity cannot be revealed. An example of these embodiments is the proposed 3GPP specification discussed above, where upon entering NR PN while previously using another network type (e.g., SNPN), the UE sets the following fields of an entry in variable VarMobilityHistoryReport'.
• the field timeSpent as the time spent outside of current network type (i.e., public network); and
• the field NetworkType as the selected network type (e.g., non-public network) where the UE was connected (in RRC CONNECTED, RRC IDLE or RRC INACTIVE) before entering the current network type (i.e., public network).
In some of these embodiment, when the logged second MHI for a non-public network includes the indication that the duration of time was spent in a non-public network, the logged second MHI also includes an identity of the non-public network.
In some embodiments, the logged first MHI includes an indication of a duration of time the UE spent outside of a non-public network and one of the following: an indication that the duration of time was spent in a public network, or an indication that the duration of time was spent in a network whose type and/or identity cannot be revealed. An example of these embodiments is the proposed 3GPP specification discussed above, where upon entering NR SNPN while previously using another network type (e.g., PN), the UE sets the following fields of an entry in vari able VarMobilityH istoryReport.
• the field timeSpent as the time spent outside of current network type (i.e., non-public network); and
• the field NetworkType as the selected network type (e.g., public network) where the UE was connected (in RRC CONNECTED, RRC IDLE or RRC INACTIVE) before entering the current network type (i.e., non-public network).
In some embodiments, the logged second MHI includes, for each visited cell in a nonpublic network, an indication of a duration of time the UE spent in the visited cell and one of the following: an indication that the visited cell is part of a non-public network, or an indication that the visited cell is part of a network whose type and/or identity cannot be revealed.
In some embodiments, the one or more MHI reports are arranged according to one of the following:
• a single MHI report that includes at least part of the first MHI but excludes the second MHI;
• a single MHI report that includes at least part of the second MHI but excludes the first MHI;
• a single MHI report that includes at least part of the first MHI and at least part of the second MHI; or
• a first MHI report that includes at least part of the first MHI and a second MHI report that includes at least part of the second MHI.
In some of these embodiments, when the first network is a public network, the at least part of the first MHI included in the single MHI report (i.e., in the first option above) corresponds to one of the following:
• all first MHI logged for all visited public networks and/or all visited cells in public networks; or
• only first MHI logged for the first network and/or visited cells in the first network.
In other of these embodiments, when the first network is a non-public network, the at least part of the second MHI included in the single MHI report (i.e., in the second and third options above) or the second MHI report (i.e., in the fourth option above) corresponds to one of the following:
• all second MHI logged for all visited non-public networks and/or all visited cells in non- public networks; or
• only second MHI logged for the first network and/or visited cells in the first network.
In some of these embodiments, the exemplary method can also include the operations of block 1360, where after sending the single MHI report that includes at least part of the second MHI but excludes the first MHI, the UE can discard (e.g., delete or other make unusable) the first MHI in response to the earlier of the following events: • connecting to a second network that is a public network and sending the first MHI to the second network; or
• expiration of a time limit without sending the first MHI to a public network.
In some of these embodiments, for any single MHI report that includes at least part of the first MHI and at least part of the second MHI, at least one entry in the MHI report is associated with respective at least one visited cell,. Each of the at least one entry indicates one of the following for the associated visited cell:
• whether the visited cell is associated with a public network or a non-public network; or
• whether or not information reported for the visited cell should be disclosed to other networks.
In some variants of these embodiments, each entry associated with a visited NPN cell includes a cell global identity (CGI) of the visited NPN cell.
In some embodiments, the first MHI and the second MHI are logged in separate UE variables. In other embodiments, the first MHI and the second MHI are logged in a single UE variable.
In some embodiments, the exemplary method can also include the operations of block 1340, where after subsequently connecting to the first network, the UE can receive from the first network an information request for MHI logged for public networks and for MHI logged for nonpublic networks. In such case, sending the one or more MHI reports in block 1350 is responsive to the information request. In some of these embodiments, the information request includes a single indication of a request for MHI logged for public networks and for MHI logged for nonpublic networks. In other of these embodiments, the information request includes a first indication of a request for MHI logged for public networks and a second indication of a request for MHI logged for non-public networks.
In some embodiments, the exemplary method can also include the operations of block 1340, where the UE can receive, from the first network or from a second network, a configuration for logging and reporting MHI. In such case logging the first and second MHI in blocks 1320- 1330 and sending the one or more MHI reports in block 1350 are in accordance with the configuration.
In addition, Figure 14 illustrates another exemplary method (e.g., procedure) for a RAN node configured to operate in a first network, according to various embodiments of the present disclosure. For example, the exemplary method shown in Figure 14 can be performed by an RAN node (e.g., base station, eNB, gNB, ng-eNB, etc.) such as described elsewhere herein. Also, the exemplary method shown in Figure 14 can be used cooperatively with the exemplary method shown in Figure 13. The exemplary method includes the operations of block 1430, where the RAN node can receive from a UE one or more MHI reports that include one or more of the following that was logged by the UE:
• first MHI associated with one or more visited public networks and/or with visited cells in the one or more public networks, and
« second MHI associated with one or more non-public networks and/or with visited cells in the one or more non-public networks.
The exemplary method also includes the operations of blocks 1440-1450, where the RAN node can identify a second RAN node based on the received one or more MHI reports and send at least a portion of the received one or more MHI reports to the second RAN node.
In various embodiments, the first and second MHI can have any of the same content, form, and/or structure as the corresponding first and second MHI logged by a UE, as described above for UE embodiments shown in Figure 13. Likewise, the one or more MHI reports can have any of the same content, form, and/or structure as the corresponding one or more MHI reports described above for UE embodiments shown in Figure 13. Put differently, the one or more MHI reports received by the RAN node correspond to the one or more MHI reports sent by the UE.
In some embodiments, first and second MHI report are sent to the second RAN node as one of the following: separate fields of a single information element (IE) in a message, or separate IES in the message.
In some embodiments, the exemplary method also includes the operations of block 1420, where the RAN node can send to the UE an information request for MHI logged for public networks and for MHI logged for non-public networks. In such case, receiving the one or more MHI reports in block 1430 is responsive to the information request. In some of these embodiments, the information request includes a single indication of a request for MHI logged for public networks and for MHI logged for non-public networks. In other of these embodiments, the information request includes a first indication of a request for MHI logged for public networks and a second indication of a request for MHI logged for non-public networks.
In some embodiments, the exemplary method also includes the operations of block 1410, where the RAN node can send to the UE a configuration for logging and reporting MHI. The contents of the one or more MHI reports are in accordance with the configuration.
In some embodiments, the RAN node and the second RAN node are arranged in dual connectivity with the UE. In other embodiments, a cell served by the second RAN node is a target cell for a UE mobility procedure, and the at least a portion of the received one or more MHI reports is sent to the second RAN node in conjunction with the mobility procedure. In some embodiments, the second RAN node serves one or more of the cells identified in the one or more MHI reports. Although various embodiments are described above in terms of methods, techniques, and/or procedures, the person of ordinary skill will readily comprehend that such methods, techniques, and/or procedures can be embodied by various combinations of hardware and software in various systems, communication devices, computing devices, control devices, apparatuses, non-transitory computer-readable media, computer program products, etc.
Figure 15 shows an example of a communication system 1500 in accordance with some embodiments. In this example, communication system 1500 includes a telecommunication network 1502 that includes an access network 1504 (e.g., RAN) and a core network 1506, which includes one or more core network nodes 1508. Access network 1504 includes one or more access network nodes, such as network nodes 1510a-b (one or more of which may be generally referred to as network nodes 1510), or any other similar 3 GPP access node or non-3GPP access point. Network nodes 1510 facilitate direct or indirect connection of UEs, such as by connecting UEs 1512a-d (one or more of which may be generally referred to as UEs 1512) to core network 1506 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, communication system 1500 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. Communication system 1500 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.
UEs 1512 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and/or operable to communicate wirelessly with network nodes 1510 and other communication devices. Similarly, network nodes 1510 are arranged, capable, configured, and/or operable to communicate directly or indirectly with UEs 1512 and/or with other network nodes or equipment in telecommunication network 1502 to enable and/or provide network access, such as wireless network access, and/or to perform other functions, such as administration in telecommunication network 1502.
In the depicted example, core network 1506 connects network nodes 1510 to one or more hosts, such as host 1516. 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. Core network 1506 includes one or more core network nodes (e.g., 1508) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and/or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 1508. Example core network nodes include 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).
Host 1516 may be under the ownership or control of a service provider other than an operator or provider of access network 1504 and/or telecommunication network 1502, and may be operated by the service provider or on behalf of the service provider. Host 1516 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.
As a whole, communication system 1500 of Figure 15 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system 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 Electronics Engineers (IEEE) 802.11 standards (WiFi); and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and/or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.
In some examples, telecommunication network 1502 is a cellular network that implements 3GPP standardized features. Accordingly, telecommunication network 1502 may support network slicing to provide different logical networks to different devices that are connected to telecommunication network 1502. For example, telecommunication network 1502 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)/Massive loT services to yet further UEs. In some examples, UEs 1512 are configured to transmit and/or receive information without direct human interaction. For instance, a UE may be designed to transmit information to access network 1504 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from access network 1504. 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 LTE, 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).
In the example, hub 1514 communicates with access network 1504 to facilitate indirect communication between one or more UEs (e.g., 1512c and/or 1512d) and network nodes (e.g., network node 1510b). In some examples, hub 1514 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, hub 1514 may be a broadband router enabling access to core network 1506 for the UEs. As another example, hub 1514 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 1510, or by executable code, script, process, or other instructions in hub 1514. As another example, hub 1514 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, hub 1514 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, hub 1514 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which hub 1514 then provides to the UE either directly, after performing local processing, and/or after adding additional local content. In still another example, hub 1514 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy loT devices.
Hub 1514 may have a constant/persistent or intermittent connection to network node 1510b. Hub 1514 may also allow for a different communication scheme and/or schedule between hub 1514 and UEs (e.g., 1512c and/or 1512d), and between hub 1514 and core network 1506. In other examples, hub 1514 is connected to core network 1506 and/or one or more UEs via a wired connection. Moreover, hub 1514 may be configured to connect to an M2M service provider over access network 1504 and/or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with network nodes 1510 while still connected via hub 1514 via a wired or wireless connection. In some embodiments, hub 1514 may be a dedicated hub - that is, a hub whose primary function is to route communications to/from the UEs from/to network node 1510b. In other embodiments, hub 1514 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 1510b, but which is additionally capable of operating as a communication start and/or end point for certain data channels.
Figure 16 shows a UE 1600 in accordance with some embodiments. Examples of a UE 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-mounted or vehicle embedded/integrated wireless device, etc. Other examples include any UE identified by 3 GPP, including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.
A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP 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, a UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device. Instead, a UE 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, a UE 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).
UE 1600 includes processing circuitry 1602 that is operatively coupled via bus 1604 to input/output interface 1606, power source 1608, memory 1610, communication interface 1612, and possibly other components not specifically shown. Certain UEs may utilize all or a subset of the components shown in Figure 16. 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.
Processing circuitry 1602 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 memory 1610. Processing circuitry 1602 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, processing circuitry 1602 may include multiple central processing units (CPUs). In the example, input/output interface 1606 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 UE 1600. 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 a user. 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.
In some embodiments, power source 1608 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. Power source 1608 may further include power circuitry for delivering power from power source 1608 itself, and/or an external power source, to the various parts of UE 1600 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of power source 1608. Power circuitry may perform any formatting, converting, or other modification to the power from power source 1608 to make the power suitable for the respective components of UE 1600 to which power is supplied.
Memory 1610 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, memory 1610 includes one or more application programs 1614, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 1616. Memory 1610 may store, for use by UE 1600, any of a variety of various operating systems or combinations of operating systems.
Memory 1610 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 embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ Memory 1610 may allow UE 1600 to access instructions, application 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 memory 1610, which may be or comprise a device-readable storage medium.
Processing circuitry 1602 may be configured to communicate with an access network or other network using communication interface 1612. Communication interface 1612 may comprise one or more communication subsystems and may include or be communicatively coupled to antenna 1622. Communication interface 1612 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 UE or a network node in an access network). Each transceiver may include transmitter 1618 and/or receiver 1620 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, transmitter 1618 and/or receiver 1620 may be coupled to one or more antennas (e.g., 1622) and may share circuit components, software, or firmware, or alternatively be implemented separately.
In the illustrated embodiment, communication functions of communication interface 1612 may include cellular communication, Wi-Fi communication, 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 in 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.
Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 1612, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The 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., an alert is sent when moisture is detected), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).
As another example, a UE 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, the UE 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.
A UE, 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, city wearable technology, extended industrial application and healthcare. Non-limiting 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 head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), 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. A UE in the form of an loT device 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 UE 1600 shown in Figure 16.
As yet another specific example, in an loT scenario, a UE may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another UE and/or a network node. The UE 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, the UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE 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.
In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE 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 UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.
Figure 17 shows a network node 1700 in accordance with some embodiments. Examples of network nodes include, but are not limited to, access points (e.g., radio access points) and base stations (e.g., radio base stations, Node Bs, eNBs, and gNBs).
Base stations 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. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units 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).
Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, 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).
Network node 1700 includes processing circuitry 1702, memory 1704, communication interface 1706, and power source 1708. Network node 1700 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which network node 1700 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components 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, network node 1700 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 1704 for different RATs) and some components may be reused (e.g., a same antenna 1710 may be shared by different RATs). Network node 1700 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1700, for example GSM, WCDMA, LTE, NR, WiFi, 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 1700.
Processing circuitry 1702 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 network node 1700 components, such as memory 1704, to provide network node 1700 functionality.
In some embodiments, processing circuitry 1702 includes a system on a chip (SOC). In some embodiments, processing circuitry 1702 includes radio frequency (RF) transceiver circuitry 1712 and/or baseband processing circuitry 1714. In some embodiments, RF transceiver circuitry 1712 and/or baseband processing circuitry 1714 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 1712 and baseband processing circuitry 1714 may be on the same chip or set of chips, boards, or units.
Memory 1704 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), 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 circuitry 1702. Memory 1704 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 (collectively denoted computer program 1704a, which may be in the form of a computer program product) capable of being executed by processing circuitry 1702 and utilized by network node 1700. Memory 1704 may be used to store any calculations made by processing circuitry 1702 and/or any data received via communication interface 1706. In some embodiments, processing circuitry 1702 and memory 1704 is integrated.
Communication interface 1706 is used in wired or wireless communication of signaling and/or data between a network node, access network, and/or UE. As illustrated, communication interface 1706 comprises port(s)/terminal(s) 1716 to send and receive data, for example to and from a network over a wired connection. Communication interface 1706 also includes radio frontend circuitry 1718 that may be coupled to, or in certain embodiments a part of, antenna 1710. Radio front-end circuitry 1718 comprises filters 1720 and amplifiers 1722. Radio front-end circuitry 1718 may be connected to an antenna 1710 and processing circuitry 1702. Radio frontend circuitry 1718 may be configured to condition signals communicated between antenna 1710 and processing circuitry 1702. Radio front-end circuitry 1718 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. Radio front-end circuitry 1718 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1720 and/or amplifiers 1722. The radio signal may then be transmitted via antenna 1710. Similarly, when receiving data, antenna 1710 may collect radio signals which are then converted into digital data by radio front-end circuitry 1718. The digital data may be passed to processing circuitry 1702. In other embodiments, the communication interface may comprise different components and/or different combinations of components.
In certain alternative embodiments, network node 1700 does not include separate radio front-end circuitry 1718, instead, processing circuitry 1702 includes radio front-end circuitry and is connected to antenna 1710. Similarly, in some embodiments, all or some of RF transceiver circuitry 1712 is part of communication interface 1706. In still other embodiments, communication interface 1706 includes one or more ports or terminals 1716, radio front-end circuitry 1718, and RF transceiver circuitry 1712, as part of a radio unit (not shown), and communication interface 1706 communicates with baseband processing circuitry 1714, which is part of a digital unit (not shown).
Antenna 1710 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna 1710 may be coupled to radio front-end circuitry 1718 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In certain embodiments, antenna 1710 is separate from network node 1700 and connectable to network node 1700 through an interface or port.
Antenna 1710, communication interface 1706, and/or processing circuitry 1702 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node. Any information, data and/or signals may be received from a UE, another network node and/or any other network equipment. Similarly, antenna 1710, communication interface 1706, and/or processing circuitry 1702 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and/or signals may be transmitted to a UE, another network node and/or any other network equipment. Power source 1708 provides power to the various components of network node 1700 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source 1708 may further comprise, or be coupled to, power management circuitry to supply the components of network node 1700 with power for performing the functionality described herein. For example, network node 1700 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 power source 1708. As a further example, power source 1708 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.
Embodiments of network node 1700 may include additional components beyond those shown in Figure 17 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 node 1700 may include user interface equipment to allow input of information into network node 1700 and to allow output of information from network node 1700. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node 1700.
Figure 18 is a block diagram of a host 1800, which may be an embodiment of host 1318 of Figure 15, in accordance with various aspects described herein. As used herein, host 1800 may be or comprise various combinations hardware and/or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. Host 1800 may provide one or more services to one or more UEs.
Host 1800 includes processing circuitry 1802 that is operatively coupled via a bus 1804 to an input/output interface 1806, a network interface 1808, a power source 1810, and a memory 1812. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 16 and 17, such that the descriptions thereof are generally applicable to the corresponding components of host 1800.
Memory 1812 may include one or more computer programs including one or more host application programs 1814 and data 1816, which may include user data, e.g., data generated by a UE for host 1800 or data generated by host 1800 for a UE. Embodiments of host 1800 may utilize only a subset or all of the components shown. Host application programs 1814 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). Host application programs 1814 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, host 1800 may select and/or indicate a different host for over-the-top services for a UE. Host application programs 1814 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real- Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.
Figure 19 is a block diagram illustrating a virtualization environment 1900 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 1900 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized.
Applications 1902 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment 1900 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.
Hardware 1904 includes processing circuitry, memory that stores software and/or instructions (collectively denoted computer program 1904a, which may be in the form of a computer program product) 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 1906 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 1908a-b (one or more of which may be generally referred to as VMs 1908), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein. Virtualization layer 1906 may present a virtual operating platform that appears like networking hardware to VMs 1908. VMs 1908 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 1906. Different embodiments of the instance of a virtual appliance 1902 may be implemented on one or more of VMs 1908, 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.
In the context of NFV, each VM 1908 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each VM 1908, and that part of hardware 1904 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 VMs 1908 on top of hardware 1904 and corresponds to application 1902.
Hardware 1904 may be implemented in a standalone network node with generic or specific components. Hardware 1904 may implement some functions via virtualization. Alternatively, hardware 1904 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 1910, which, among others, oversees lifecycle management of applications 1902. In some embodiments, hardware 1904 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 1912 which may alternatively be used for communication between hardware nodes and radio units.
Figure 20 shows a communication diagram of a host 2002 communicating via a network node 2004 with a UE 2006 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE 1512a of Figure 15 and/or UE 1600 of Figure 16), network node (such as network node 1510a of Figure 15 and/or network node 1700 of Figure 17), and host (such as host 1518 of Figure 15 and/or host 1800 of Figure 18) discussed in the preceding paragraphs will now be described with reference to Figure 20. Like host 1800, embodiments of host 2002 include hardware, such as a communication interface, processing circuitry, and memory. Host 2002 also includes software, which is stored in or accessible by host 2002 and executable by the processing circuitry. The software includes a host application that may be operable to provide a service to a remote user, such as UE 2006 connecting via an over-the-top (OTT) connection 2050 extending between UE 2006 and host 2002. In providing the service to the remote user, a host application may provide user data which is transmitted using OTT connection 2050.
Network node 2004 includes hardware enabling it to communicate with host 2002 and UE 2006. Connection 2060 may be direct or pass through a core network (like core network 1506 of Figure 15) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet.
UE 2006 includes hardware and software, which is stored in or accessible by UE 2006 and executable by the UE’s processing circuitry. The software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 2006 with the support of host 2002. In host 2002, an executing host application may communicate with the executing client application via OTT connection 2050 terminating at UE 2006 and host 2002. In providing the service to the user, the UE's client application may receive request data from the host's host application and provide user data in response to the request data. OTT connection 2050 may transfer both the request data and the user data. The UE's client application may interact with the user to generate the user data that it provides to the host application through OTT connection 2050.
OTT connection 2050 may extend via a connection 2060 between host 2002 and network node 2004 and via a wireless connection 2070 between network node 2004 and UE 2006 to provide the connection between host 2002 and UE 2006. Connection 2060 and wireless connection 2070, over which OTT connection 2050 may be provided, have been drawn abstractly to illustrate the communication between host 2002 and UE 2006 via network node 2004, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
As an example of transmitting data via OTT connection 2050, in step 2008, host 2002 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with UE 2006. In other embodiments, the user data is associated with a UE 2006 that shares data with host 2002 without explicit human interaction. In step 2010, host 2002 initiates a transmission carrying the user data towards UE 2006. Host 2002 may initiate the transmission responsive to a request transmitted by UE 2006. The request may be caused by human interaction with UE 2006 or by operation of the client application executing on UE 2006. The transmission may pass via network node 2004, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 2012, network node 2004 transmits to UE 2006 the user data that was carried in the transmission that host 2002 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 2014, UE 2006 receives the user data carried in the transmission, which may be performed by a client application executed on UE 2006 associated with the host application executed by host 2002.
In some examples, UE 2006 executes a client application which provides user data to host 2002. The user data may be provided in reaction or response to the data received from host 2002. Accordingly, in step 2016, UE 2006 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input/output interface of UE 2006. Regardless of how the user data was provided, UE 2006 initiates, in step 2018, transmission of the user data towards host 2002 via network node 2004. In step 2020, in accordance with the teachings of the embodiments described throughout this disclosure, network node 2004 receives user data from UE 2006 and initiates transmission of the received user data towards host 2002. In step 2022, host 2002 receives the user data carried in the transmission initiated by UE 2006.
One or more of the various embodiments improve the performance of OTT services provided to UE 2006 using OTT connection 2050, in which wireless connection 2070 forms the last segment. More precisely, embodiments described herein can enable a network (e.g., PLMN) to determine, based on UE MHI, whether the UE was not connected to network cells because it was out of coverage of the network or because it was connected to an NPN but remained in coverage. Furthermore, embodiments can prevent a UE from sending sensitive, confidential, and/or proprietary information about a visited NPN to a PLMN or to another NPN. In embodiments where the UE does provide such information, clear labelling of NPN relation can prevent a PLMN from sharing the information with other PLMNs and/or NPNs. In this manner, embodiments can protect privacy and security of NPNs and their users. By improving security of networks in this manner, embodiments increase the value of OTT services delivered over the improved networks to both end users and service providers.
In an example scenario, factory status information may be collected and analyzed by host 2002. As another example, host 2002 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, host 2002 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, host 2002 may store surveillance video uploaded by a UE. As another example, host 2002 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs. As other examples, host 2002 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and/or transmitting data.
In some examples, 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 connection 2050 between host 2002 and UE 2006, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of host 2002 and/or UE 2006. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which OTT connection 2050 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities. The reconfiguring of OTT connection 2050 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of network node 2004. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by host 2002. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using OTT connection 2050 while monitoring propagation times, errors, etc.
The foregoing merely illustrates the principles of the disclosure. Various modifications and alterations to the described embodiments will be apparent to those skilled in the art in view of the teachings herein. It will thus be appreciated that those skilled in the art will be able to devise numerous systems, arrangements, and procedures that, although not explicitly shown or described herein, embody the principles of the disclosure and can be thus within the spirit and scope of the disclosure. Various embodiments can be used together with one another, as well as interchangeably therewith, as should be understood by those having ordinary skill in the art.
The term unit, as used herein, can have conventional meaning in the field of electronics, electrical devices and/or electronic devices and can include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.
Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include Digital Signal Processor (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as Read Only Memory (ROM), Random Access Memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according to one or more embodiments of the present disclosure.
As described herein, device and/or apparatus can be represented by a semiconductor chip, a chipset, or a (hardware) module comprising such chip or chipset; this, however, does not exclude the possibility that a functionality of a device or apparatus, instead of being hardware implemented, be implemented as a software module such as a computer program or a computer program product comprising executable software code portions for execution or being run on a processor. Furthermore, functionality of a device or apparatus can be implemented by any combination of hardware and software. A device or apparatus can also be regarded as an assembly of multiple devices and/or apparatuses, whether functionally in cooperation with or independently of each other. Moreover, devices and apparatuses can be implemented in a distributed fashion throughout a system, so long as the functionality of the device or apparatus is preserved. Such and similar principles are considered as known to a skilled person.
Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. It will be further understood that terms used herein should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.
In addition, certain terms used in the present disclosure, including the specification and drawings, can be used synonymously in certain instances (e.g., “data” and “information”). It should be understood, that although these terms (and/or other terms that can be synonymous to one another) can be used synonymously herein, there can be instances when such words can be intended to not be used synonymously.
Embodiments of the techniques and apparatus described herein also include, but are not limited to, the following enumerated examples:
Al . A method for a user equipment (UE) configured to operate in public networks (PN) and in non-public networks (NPN), the method comprising: while visiting one or more cells in one or more PNs, logging first mobility history information (MHI) associated with the visited PN cells; while visiting one or more cells in one or more NPNs, logging second MHI associated with the visited NPN cells; and after subsequently connecting to a first network, sending to the first network one or more MHI reports that includes one or more of the following: at least part of the first MHI, and at least part of the second MHI.
A2. The method of embodiment Al, wherein when the first network is a PN, the one or more MHI reports are arranged according to one of the following: a single MHI report that includes at least part of the first MHI but excludes the second MHI; a single MHI report that includes the first MHI and the second MHI; or a first MHI report that includes the first MHI and a second MHI report that includes the second MHI.
A3. The method of embodiment A2, wherein the at least part of the first MHI included in the single MHI report corresponds to one of the following: all first MHI collected for all visited PN cells; or only first MHI collected for visited PN cells associated with the first network.
A4. The method of any of embodiments A1-A3, when the first network is an NPN, the one or more MHI reports are arranged according to one of the following: a single MHI report that includes at least part of the second MHI but excludes the first MHI; a single MHI report that includes the first MHI and the second MHI; or a first MHI report that includes the first MHI and a second MHI report that includes at least part of the second MHI. A5. The method of embodiment A4, wherein the at least part of the second MHI included in the single MHI report or the second MHI report corresponds to one of the following: all second MHI collected for all visited NPN cells; or only second MHI collected for visited NPN cells associated with the first network.
A6. The method of any of embodiments A4-A5, further comprising, after sending the single MHI report that includes at least part of the second MHI but excludes the first MHI, deleting the first MHI in response to the earlier of the following events: connecting to a second network that is a PN and sending the first MHI to the second network; or expiration of a time limit without sending the first MHI to a PN.
A7. The method of any of embodiments A2-A6, wherein for any single MHI report that includes at least part of the first MHI and at least part of the second MHI, each MHI report entry corresponds to a visited cell and indicates one of the following for the visited cell: whether the visited cell is associated with a PN or an NPN; or whether or not information reported for the visited cell should be disclosed to other networks.
A8. The method of embodiment A7, wherein each MHI report entry corresponding to a visited NPN cell includes a cell global identity (CGI) of the visited NPN cell.
A9. The method of any of embodiments A2-A8, wherein each MHI report entry corresponding to a visited NPN cell includes a first indication of a duration of time the UE spent in the visited NPN cell and a second indication that the visited NPN cell is associated with one of the following: an NPN, or a network and/or a network type that cannot be revealed.
A10. The method of any of embodiments A1-A9, wherein one of the following applies: the first MHI and the second MHI are logged in separate UE variables; or the first MHI and the second MHI are logged in a single UE variable.
Al l. The method of any of embodiments A1-A10, wherein: the method further comprises, after subsequently connecting to the first network, receiving from the first network an information request for MHI logged for PNs and MHI logged for NPNs; and sending the one or more MHI reports is responsive to the information request.
A12. The method of embodiment Al l, wherein the information request includes one of the following: a single indication of a request for MHI logged for PNs and for MHI logged for NPNs; or a first indication of a request for MHI logged for PNs and a second indication of a request for MHI logged for NPNs.
A13. The method of any of embodiments A1-A12, further comprising receiving, from the first network or from a second network, a configuration for logging and reporting MHI, wherein logging the first and second MHI and sending the one or more MHI reports are in accordance with the configuration.
Bl. A method for a radio access network (RAN) node in a first network, the method comprising: receiving from a user equipment (UE) one or more mobility history information (MHI) reports that include one or more of the following: at least part of first MHI logged by the UE while visiting cells in one or more public networks (PNs), and at least part of second MHI logged by the UE while visiting cells in one or more non-public networks (NPNs); identifying a second RAN node based on the received one or more MHI reports; and sending at least a portion of the received one or more MHI reports to the second RAN node.
B2. The method of embodiment Bl, wherein when the first network is a PN, the one or more MHI reports are arranged according to one of the following: a single MHI report that includes at least part of the first MHI but excludes the second MHI; a single MHI report that includes the first MHI and the second MHI; or a first MHI report that includes the first MHI and a second MHI report that includes the second MHI.
B3. The method of embodiment B2, wherein the at least part of the first MHI included in the single MHI report corresponds to one of the following: all first MHI collected for all visited PN cells; or only first MHI collected for visited PN cells associated with the first network.
B4. The method of any of embodiments B1-B3, when the first network is an NPN, the one or more MHI reports are arranged according to one of the following: a single MHI report that includes at least part of the second MHI but excludes the first MHI; a single MHI report that includes the first MHI and the second MHI; or a first MHI report that includes the first MHI and a second MHI report that includes at least part of the second MHI.
B5. The method of embodiment B4, wherein the at least part of the second MHI included in the single MHI report or the second MHI report corresponds to one of the following: all second MHI collected for all visited NPN cells; or only second MHI collected for visited NPN cells associated with the first network.
B6. The method of any of embodiments B2-B5, wherein for any single MHI report that includes at least part of the first MHI and at least part of the second MHI, each MHI report entry corresponds to a visited cell and indicates one of the following for the visited cell: whether the visited cell is associated with a PN or an NPN; or whether or not information reported for the visited cell should be disclosed to other networks.
B7. The method of embodiment B6, wherein each MHI report entry corresponding to a visited NPN cell includes a cell global identity (CGI) of the visited NPN cell.
B8. The method of any of embodiments B2-B7, wherein each MHI report entry corresponding to a visited NPN cell includes a first indication of a duration of time the UE spent in the visited NPN cell and a second indication that the visited NPN cell is associated with one of the following: an NPN, or a network and/or a network type that cannot be revealed. B9. The method of any of embodiments B1-B8, wherein: the method further comprises sending to the UE an information request for MHI logged for PNs and MHI logged for NPNs; and receiving the one or more MHI reports is responsive to the information request.
BIO. The method of embodiment B9, wherein the information request includes one of the following: a single indication of a request for MHI logged for PNs and for MHI logged for NPNs; or a first indication of a request for MHI logged for PNs and a second indication of a request for MHI logged for NPNs.
B 11. The method of any of embodiments B 1 -B 11 , further comprising sending to the UE a configuration for logging and reporting MHI, wherein the contents of the one or more MHI reports are in accordance with the configuration.
B12. The method of any of embodiments Bl-Bl 1, wherein one of the following applies: the RAN node and the second RAN node are arranged in dual connectivity with the UE; or a cell served by the second RAN node is a target cell for a UE mobility procedure, and the at least a portion of the received one or more MHI reports are sent to the second RAN node in conjunction with the mobility procedure.
B13. The method of any of embodiments B1-B12, wherein: the one or more MHI reports include a first MHI report that includes the at least a part of the first MHI and a second MHI report that includes the at least a part of the second MHI; and the first and second MHI reports are sent to the second RAN node as one of the following: separate fields of a single information element (IE) in a message, or separate IES in the message.
B14. The method of any of embodiments B1-B13, wherein the second RAN node serves one or more of the cells identified in the one or more MHI reports. Cl . A user equipment (UE) configured to operate in public networks (PN) and in non-public networks (NPN), the UE comprising: communication interface circuitry configured to communicate with RAN nodes in PNs and NPNs; and processing circuitry operatively coupled to the communication interface circuitry, whereby the processing circuitry and the communication interface circuitry are configured to perform operations corresponding to the methods of any of embodiments Al -Al 3.
C2. A user equipment (UE) configured to operate in public networks (PN) and in non-public networks (NPN), the UE being further arranged to perform operations corresponding to the methods of any of embodiments Al -Al 3.
C3. A non-transitory, computer-readable medium storing computer-executable instructions that, when executed by processing circuitry of a user equipment (UE) configured to operate in public networks (PN) and in non-public networks (NPN), configure the UE to perform operations corresponding to the methods of any of embodiments Al -Al 3.
C4. A computer program product comprising computer-executable instructions that, when executed by processing circuitry of a user equipment (UE) configured to operate in public networks (PN) and in non-public networks (NPN), configure the UE to perform operations corresponding to the methods of any of embodiments Al -Al 3.
DI . A radio access network (RAN) node configured to operate in a first network, the RAN node comprising: communication interface circuitry configured to communicate with UEs; and processing circuitry operatively coupled to the communication interface circuitry, whereby the processing circuitry and the communication interface circuitry are configured to perform operations corresponding to the methods of any of embodiments B1-B14.
D2. A radio access network (RAN) node configured to operate in a first network, the RAN node being further arranged to perform operations corresponding to the methods of any of embodiments B1-B14. D3. A non-transitory, computer-readable medium storing computer-executable instructions that, when executed by processing circuitry of a radio access network (RAN) node configured to operate in a first network, configure the RAN node to perform operations corresponding to the methods of any of embodiments B1-B14.
D4. A computer program product comprising computer-executable instructions that, when executed by processing circuitry of a radio access network (RAN) node configured to operate in a first network, configure the RAN node to perform operations corresponding to the methods of any of embodiments B1-B14.

Claims

1. A method for a user equipment, UE, configured to operate in public networks and in non-public networks, the method comprising: logging (1320) first mobility history information, MHI, associated with one or more public networks and/or with visited cells in the one or more public networks; logging (1330) second MHI associated with one or more non-public networks and/or with visited cells in the one or more non-public networks; and after subsequently connecting to a first network, sending (1350) to the first network one or more MHI reports that includes one or more of the following: at least part of the logged first MHI, and at least part of the logged second MHI.
2. The method of claim 1, wherein the logged second MHI includes an indication of a duration of time the UE spent outside of a public network and one of the following: an indication that the duration of time was spent in a non-public network, or an indication that the duration of time was spent in a network whose type and/or identity cannot be revealed.
3. The method of claim 2, wherein when the logged second MHI for a non-public network includes the indication that the duration of time was spent in a non-public network, the logged second MHI also includes an identity of the non-public network.
4. The method of any of claims 1-3, wherein the logged first MHI includes an indication of a duration of time the UE spent outside of a non-public network and one of the following: an indication that the duration of time was spent in a public network, or an indication that the duration of time was spent in a network whose type and/or identity cannot be revealed.
5. The method of any of claims 1-4, wherein the logged second MHI includes, for each visited cell in a non-public network, an indication of a duration of time the UE spent in the visited cell and one of the following: an indication that the visited cell is part of a non-public network, or an indication that the visited cell is part of a network whose type and/or identity cannot be revealed.
6. The method of any of claims 1-5, wherein the one or more MHI reports are arranged according to one of the following: a single MHI report that includes at least part of the first MHI but excludes the second MHI; a single MHI report that includes at least part of the second MHI but excludes the first MHI; a single MHI report that includes at least part of the first MHI and at least part of the second MHI; or a first MHI report that includes at least part of the first MHI and a second MHI report that includes at least part of the second MHI.
7. The method of claim 6, wherein when the first network is a public network, the at least part of the first MHI included in the single MHI report corresponds to one of the following: all first MHI logged for all visited public networks and/or all visited cells in public networks; or only first MHI logged for the first network and/or visited cells in the first network.
8. The method of claim 6, wherein when the first network is a non-public network, the at least part of the second MHI included in the single MHI report or the second MHI report corresponds to one of the following: all second MHI logged for all visited non-public networks and/or all visited cells in nonpublic networks; or only second MHI logged for the first network and/or visited cells in the first network.
9. The method of any of claims 6-8, further comprising, after sending (1350) the single MHI report that includes at least part of the second MHI but excludes the first MHI, discarding the first MHI in response to the earlier of the following events: connecting to a second network that is a public network and sending the first MHI to the second network; or expiration of a time limit without sending the first MHI to a public network.
10. The method of any of claims 6-9, wherein for any single MHI report that includes at least part of the first MHI and at least part of the second MHI, at least one entry in the MHI report is associated with respective at least one visited cell, and each of the at least one entry indicates one of the following for the associated visited cell: whether the visited cell is associated with a public network or a non-public network; or whether or not information reported for the visited cell should be disclosed to other networks.
11. The method of claim 10, wherein each entry associated with a visited NPN cell includes a cell global identity, CGI, of the visited NPN cell.
12. The method of any of claims 1-11, wherein one of the following applies: the first MHI and the second MHI are logged in separate UE variables; or the first MHI and the second MHI are logged in a single UE variable.
13. The method of any of claims 1-12, wherein: the method further comprises, after subsequently connecting to the first network, receiving (1340) from the first network an information request for MHI logged for public networks and for MHI logged for non-public networks; and sending (1350) the one or more MHI reports is responsive to the information request.
14. The method of claim 13, wherein the information request includes one of the following: a single indication of a request for MHI logged for public networks and for MHI logged for non-public networks; or a first indication of a request for MHI logged for public networks and a second indication of a request for MHI logged for non-public networks.
15. The method of any of claims 1-14, further comprising receiving (1310), from the first network or from a second network, a configuration for logging and reporting MHI, wherein logging (1320, 1330) the first and second MHI and sending (1350) the one or more MHI reports are in accordance with the configuration.
16. A method for a radio access network, RAN, node configured to operate in a first network, the method comprising: receiving (1430) from a user equipment, UE, one or more mobility history information, MHI, reports that include one or more of the following that was logged by the UE: first MHI associated with one or more visited public networks and/or with visited cells in the one or more public networks, and second MHI associated with one or more non-public networks and/or with visited cells in the one or more non-public networks; identifying (1440) a second RAN node based on the received one or more MHI reports; and sending (1450) at least a portion of the received one or more MHI reports to the second RAN node.
17. The method of claim 16, wherein the second MHI includes an indication of a duration of time the UE spent outside of a public network and one of the following: an indication that the duration of time was spent in a non-public network, or an indication that the duration of time was spent in a network whose type and/or identity cannot be revealed.
18. The method of claim 17, wherein when the second MHI includes the indication that the duration of time was spent in a non-public network, the second MHI also includes an identity of the non-public network.
19. The method of any of claims 16-18, wherein the first MHI includes an indication of a duration of time the UE spent outside of a non-public network and one of the following: an indication that the duration of time was spent in a public network, or an indication that the duration of time was spent in a network whose type and/or identity cannot be revealed.
20. The method of any of claims 16-19, wherein the second MHI includes, for each visited cell in a non-public network, an indication of a duration of time the UE spent in the visited cell and one of the following: an indication that the visited cell is part of a non-public network, or an indication that the visited cell is part of a network whose type and/or identity cannot be revealed.
21. The method of any of claims 16-20, wherein the one or more MHI reports are arranged according to one of the following: a single MHI report that includes the first MHI but excludes the second MHI; a single MHI report that includes the second MHI but excludes the first MHI; a single MHI report that includes the first MHI and the second MHI; or a first MHI report that includes the first MHI and a second MHI report that the second MHI.
22. The method of claim 21, wherein when the first network is a public network, the first MHI included in the single MHI report corresponds to one of the following: all first MHI logged for all visited public networks and/or all visited cells in public networks; or only first MHI logged for the first network and/or visited cells in the first network.
23. The method of claim 21, wherein when the first network is a non-public network, the second MHI included in the single MHI report or the second MHI report corresponds to one of the following: all second MHI logged for all visited non-public networks and/or all visited cells in nonpublic networks; or only second MHI logged for the first network and/or visited cells in the first network.
24. The method of any of claims 21-23, wherein for any single MHI report that includes the first MHI and the second MHI, at least one entry in the MHI report is associated with respective at least one visited cell, and each of the at least one entry indicates one of the following for the associated visited cell: whether the visited cell is associated with a public network or a non-public network; or whether or not information reported for the visited cell should be disclosed to other networks.
25. The method of claim 24, wherein each entry associated with a visited NPN cell includes a cell global identity, CGI, of the visited NPN cell.
26. The method of any of claims 21-25, wherein the first MHI report and the second MHI report are sent to the second RAN node as one of the following: separate fields of a single information element, IE, in a message; or separate IES in the message.
27. The method of any of claims 16-26, wherein: the method further comprises sending (1420) to the UE an information request for MHI logged for public networks and for MHI logged for non-public networks; and receiving (1430) the one or more MHI reports is responsive to the information request.
28. The method of claim 27, wherein the information request includes one of the following: a single indication of a request for MHI logged for public networks and for MHI logged for non-public networks; or a first indication of a request for MHI logged for public networks and a second indication of a request for MHI logged for non-public networks.
29. The method of any of claims 16-28, further comprising sending (1410) to the UE a configuration for logging and reporting MHI, wherein the contents of the one or more MHI reports are in accordance with the configuration.
30. The method of any of claims 16-29, wherein one of the following applies: the RAN node and the second RAN node are arranged in dual connectivity with the UE; or a cell served by the second RAN node is a target cell for a UE mobility procedure, and the at least a portion of the received one or more MHI reports is sent to the second RAN node in conjunction with the mobility procedure.
31. The method of any of claims 16-31, wherein the second RAN node serves one or more of the cells identified in the one or more MHI reports.
32. A user equipment, UE (205, 310, 1512, 1600, 2006) configured to operate in public networks (1502), and in non-public networks (1502), the UE comprising: communication interface circuitry (1610) configured to communicate with radio access network, RAN, nodes (100, 150, 210, 220, 320, 1510, 1700, 1902, 2004) in public networks and non-public networks; and processing circuitry (1602) operatively coupled to the communication interface circuitry, whereby the processing circuitry and the communication interface circuitry are configured to: log first mobility history information, MHI, associated with one or more public networks and/or with visited cells in the one or more public networks; log second MHI associated with one or more non-public networks and/or with visited cells in the one or more non-public networks; and after subsequently connecting to a first network, send to the first network one or more MHI reports that includes one or more of the following: at least part of the logged first MHI, and at least part of the logged second MHI.
33. The UE of claim 32, wherein the processing circuitry and the communication interface circuitry are further configured to perform operations corresponding to the methods of any of claims 2-15.
34. A user equipment, UE (205, 310, 1512, 1600, 2006) configured to operate in public networks (1502), and in non-public networks (1502), the UE being further configured to: log first mobility history information, MHI, associated with one or more public networks and/or with visited cells in the one or more public networks; log second MHI associated with one or more non-public networks and/or with visited cells in the one or more non-public networks; and after subsequently connecting to a first network, send to the first network one or more MHI reports that includes one or more of the following: at least part of the logged first MHI, and at least part of the logged second MHI.
35. The UE of claim 34, being further configured to perform operations corresponding to the methods of any of claims 2-15.
36. A non-transitory, computer-readable medium (1610) storing computer-executable instructions that, when executed by processing circuitry (1602) of a user equipment, UE (205, 310, 1512, 1600, 2006) configured to operate in public networks (1502), and in non-public networks (1502), configure the UE to perform operations corresponding to the methods of any of claims 1-15.
37. A computer program product (1614) comprising computer-executable instructions that, when executed by processing circuitry (1602) of a user equipment, UE (205, 310, 1512, 1600, 2006) configured to operate in public networks (1502), and in non-public networks (1502), configure the UE to perform operations corresponding to the methods of any of claims 1-15.
38. A radio access network, RAN, node (100, 150, 210, 220, 320, 1510, 1700, 1902, 2004) configured to operate in a first network (1502), the RAN node comprising: communication interface circuitry (1706, 1904) configured to communicate with user equipment, UEs (205, 310, 1512, 1600, 2006) and with a second RAN node (100, 150, 210, 220, 320, 1510, 1700, 1902, 2004); and processing circuitry (1702, 1904) operatively coupled to the communication interface circuitry, whereby the processing circuitry and the communication interface circuitry are configured to: receive from a UE one or more mobility history information, MHI, reports that include one or more of the following that was logged by the UE: first MHI associated with one or more visited public networks and/or with visited cells in the one or more public networks, and second MHI associated with one or more non-public networks and/or with visited cells in the one or more non-public networks; identify the second RAN node based on the received one or more MHI reports; and send at least a portion of the received one or more MHI reports to the second RAN node.
39. The RAN node of claim 38, wherein the processing circuitry and the communication interface circuitry are further configured to perform operations corresponding to the methods of any of claims 17-31.
40. A radio access network, RAN, node (100, 150, 210, 220, 320, 1510, 1700, 1902, 2004) configured to operate in a first network (1502), the RAN node being further configured to: receive from a user equipment, UE (205, 310, 1512, 1600, 2006) one or more mobility history information, MHI, reports that include one or more of the following that was logged by the UE: first MHI associated with one or more visited public networks and/or with visited cells in the one or more public networks, and second MHI associated with one or more non-public networks and/or with visited cells in the one or more non-public networks; identify a second RAN node (100, 150, 210, 220, 320, 1510, 1700, 1902, 2004) based on the received one or more MHI reports; and send at least a portion of the received one or more MHI reports to the second RAN node.
41. The RAN node of claim 40, being further configured to perform operations corresponding to the methods of any of claims 17-31.
42. A non-transitory, computer-readable medium (1704, 1904) storing computer-executable instructions that, when executed by processing circuitry (1702, 1904) of a radio access network, RAN, node (100, 150, 210, 220, 320, 1510, 1700, 1902, 2004) configured to operate in a first network (1502), configure the RAN node to perform operations corresponding to the methods of any of claims 16-31.
43. A computer program product (1704a, 1904a) comprising computer-executable instructions that, when executed by processing circuitry (1702, 1904) of a radio access network, RAN, node (100, 150, 210, 220, 320, 1510, 1700, 1902, 2004) configured to operate in a first network (1502), configure the RAN node to perform operations corresponding to the methods of any of claims 16-31.
PCT/SE2023/050860 2022-09-27 2023-08-30 Enhancements to mobility history information (mhi) for non-public networks (npn) WO2024072275A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202263410258P 2022-09-27 2022-09-27
US63/410,258 2022-09-27

Publications (1)

Publication Number Publication Date
WO2024072275A1 true WO2024072275A1 (en) 2024-04-04

Family

ID=87934136

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2023/050860 WO2024072275A1 (en) 2022-09-27 2023-08-30 Enhancements to mobility history information (mhi) for non-public networks (npn)

Country Status (1)

Country Link
WO (1) WO2024072275A1 (en)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022039657A1 (en) * 2020-08-18 2022-02-24 Telefonaktiebolaget Lm Ericsson (Publ) Failure reporting for non-public networks in 5g

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022039657A1 (en) * 2020-08-18 2022-02-24 Telefonaktiebolaget Lm Ericsson (Publ) Failure reporting for non-public networks in 5g

Non-Patent Citations (6)

* Cited by examiner, † Cited by third party
Title
3GPP TS 23.501
3GPP TS 38.331
3GPP TS 38.423
3GPP TS 38.473
ERICSSON: "SON support for NPN", vol. RAN WG2, no. Electronic meeting; 20220817 - 20220829, 10 August 2022 (2022-08-10), XP052261488, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG2_RL2/TSGR2_119-e/Docs/R2-2208176.zip R2-2208176 - SON support for NPN.docx> [retrieved on 20220810] *
ERICSSON: "Summary of AI 8.13.2 - SON, RAN2 scope and requirements", vol. RAN WG2, no. Electronic meeting; 20200817 - 20200828, 1 September 2020 (2020-09-01), XP052361357, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG2_RL2/TSGR2_111-e/Docs/R2-2008288.zip R2-2008288.docx> [retrieved on 20200901] *

Similar Documents

Publication Publication Date Title
US11792693B2 (en) Methods and apparatuses for redirecting users of multimedia priority services
US20240129704A1 (en) Public Warning System (PWS) Reception by Aerial User Equipment (UE)
WO2024072275A1 (en) Enhancements to mobility history information (mhi) for non-public networks (npn)
US20240172074A1 (en) Handling of User Equipment (UE) Context Information after Inter-System Handover
WO2023132764A1 (en) Coordinated coverage updates for radio access network nodes with distributed architecture
WO2023014254A1 (en) Reporting ue-initiated network release
WO2023022645A1 (en) Managing configured application-layer measurements in response to a connection setup message
WO2024005702A1 (en) Time aligned radio-layer and application-layer measurements for dual connectivity
WO2024035297A1 (en) Reporting random access partition information
WO2024005700A1 (en) Configuring inter-du l1/l2 mobility candidates
WO2023027619A1 (en) Managing configured application-layer measurements during handover
WO2023132776A1 (en) Time-aligned radio-layer and application-layer measurements
WO2023001491A1 (en) Indicating handover-persistent release preference
WO2023277764A2 (en) Handling of secondary node (sn) configurations during multi-rat dual connectivity (mr-dc) release
WO2023136764A1 (en) Methods for handling logging of different types of measurements in son reports
WO2023287336A1 (en) Preventing radio resource control (rrc) state mismatch between network and user equipment
WO2022264090A1 (en) Logging and reporting of aerial ue-specific information
WO2023277752A1 (en) Reporting erroneous reconfigurations
WO2024030060A1 (en) Reporting random access information for events or operations in shared channels
WO2023069000A1 (en) Handling quality-of-experience (qoe) configurations exceeding maximum number
WO2024035290A1 (en) L1/l2 inter-cell mobility execution
WO2024079717A1 (en) Reporting of qoe reports to the sn
WO2023131896A1 (en) Systems and methods for management of network slices requested by a ue
WO2023224527A1 (en) Distribution of ran-visible qoe measurements
WO2023132774A1 (en) Handling of triggers for ran-visible qoe reporting

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23765332

Country of ref document: EP

Kind code of ref document: A1