WO2023047255A1 - Enhancements of logged mdt report - Google Patents

Enhancements of logged mdt report Download PDF

Info

Publication number
WO2023047255A1
WO2023047255A1 PCT/IB2022/058730 IB2022058730W WO2023047255A1 WO 2023047255 A1 WO2023047255 A1 WO 2023047255A1 IB 2022058730 W IB2022058730 W IB 2022058730W WO 2023047255 A1 WO2023047255 A1 WO 2023047255A1
Authority
WO
WIPO (PCT)
Prior art keywords
cell
communication device
information
state
camped
Prior art date
Application number
PCT/IB2022/058730
Other languages
French (fr)
Inventor
Pradeepa Ramachandra
Sakib BIN REDHWAN
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 WO2023047255A1 publication Critical patent/WO2023047255A1/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/02—Access restriction performed under specific conditions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/20—Selecting an access point

Definitions

  • the present disclosure relates generally to communications, and more particularly to communication methods and related devices and nodes supporting wireless communications.
  • LTE Long-Term Evolution
  • 4G fourth generation
  • 3GPP Third-Generation Partnership Project
  • Release 8 Release 8
  • Release 9 Release 9
  • SAE System Architecture Evolution
  • EPC Evolved Packet Core
  • E-UTRAN 100 includes one or more evolved Node B’s (eNB), such as eNBs 105, 110, and 115, and one or more user equipment (UE), such as UE 120.
  • eNB evolved Node B
  • UE user equipment
  • “user equipment” or “UE” means any wireless communication device (e.g., smartphone or computing device) that is capable of communicating with 3GPP- standard- compliant network equipment, including E-UTRAN as well as UTRAN and/or GER AN (GSM (global system for mobile communication) EDGE (enhanced data rates for GSM evolution) radio access network), as the third generation (“3G”) and second-generation (“2G”) 3GPP RANs are commonly known.
  • GSM global system for mobile communication
  • EDGE enhanced data rates for GSM evolution
  • 3G third generation
  • 2G second-generation
  • E-UTRAN 100 is responsible for all radio-related functions in the network, including radio bearer control, radio admission control, radio mobility control, scheduling, and dynamic allocation of resources to UEs in uplink and downlink, as well as security of the communications with the UE.
  • These functions reside in the eNBs, such as eNBs 105, 110, and 115.
  • Each of the eNBs can serve a geographic coverage area including one more cells, including cells 106, 111, and 115 served by eNBs 105, 110, and 115, respectively.
  • the eNBs in the E-UTRAN communicate with each other via the X2 interface, as shown in Figure 1.
  • the eNBs also are responsible for the E-UTRAN interface to the EPC 130, specifically the SI interface to the Mobility Management Entity (MME) and the Serving Gateway (SGW), shown collectively as MME/S-GWs 134 and 138 in Figure 1.
  • MME/S-GW handles both the overall control of the UE and data flow between the UE and the rest of the EPC. More specifically, the MME processes the signaling (e.g., control plane) protocols between the UE and the EPC, which are known as the Non-Access Stratum (NAS) protocols.
  • NAS Non-Access Stratum
  • the S-GW handles all Internet Protocol (IP) data packets (e.g., data or user plane) between the UE and the EPC and serves as the local mobility anchor for the data bearers when the UE moves between eNBs, such as eNBs 105, 110, and 115.
  • IP Internet Protocol
  • EPC 130 can also include a Home Subscriber Server (HSS) 131, which manages user- and subscriber-related information.
  • HSS 131 can also provide support functions in mobility management, call and session setup, user authentication and access authorization.
  • the functions of HSS 131 can be related to the functions of legacy Home Location Register (HLR) and Authentication Centre (AuC) functions or operations.
  • HSS 131 can also communicate with MMEs 134 and 138 via respective S6a interfaces.
  • HSS 131 can communicate with a user data repository (UDR) - labelled EPC-UDR 135 in Figure 1 - via a Ud interface.
  • EPC-UDR 135 can store user credentials after they have been encrypted by AuC algorithms. These algorithms are not standardized (i.e., vendor- specific), such that encrypted credentials stored in EPC-UDR 135 are inaccessible by any other vendor than the vendor of HSS 131.
  • FIG. 2 illustrates a block diagram of an exemplary control plane (CP) protocol stack between a UE, an eNB, and an MME.
  • the exemplary protocol stack includes Physical (PHY), Medium Access Control (MAC), Radio Link Control (RLC), Packet Data Convergence Protocol (PDCP), and Radio Resource Control (RRC) layers between the UE and eNB.
  • the PHY layer is concerned with how and what characteristics are used to transfer data over transport channels on the LTE radio interface.
  • the MAC layer provides data transfer services on logical channels, maps logical channels to PHY transport channels, and reallocates PHY resources to support these services.
  • the RLC layer provides error detection and/or correction, concatenation, segmentation, and reassembly, reordering of data transferred to or from the upper layers.
  • the PDCP layer provides ciphering/deciphering and integrity protection for both CP and user plane (UP), as well as other UP functions such as header compression.
  • the exemplary protocol stack also includes non-access stratum (NAS) signaling between the UE and the MME.
  • NAS non-access stratum
  • the RRC layer controls communications between a UE and an eNB at the radio interface, as well as the mobility of a UE between cells in the E-UTRAN.
  • a UE After a UE is powered ON it will be in the RRC DLE 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 RRC JDLE after the connection with the network is released.
  • RRC_ IDLE state the UE does not belong to any cell, no RRC context has been established for the UE (e.g., in E-UTRAN), and the UE is out of UL synchronization with the network. Even so, a UE in RRCJDLE state is known in the EPC and has an assigned IP address.
  • the UE’s radio is active on a discontinuous reception (DRX) schedule configured by upper layers.
  • DRX active periods also referred to as “On durations”.
  • SI system information
  • an RRC.. IDLE UE receives system information (SI) broadcast by a serving cell, performs measurements of neighbor cells to support cell reselection, and monitors a paging channel for pages from the EPC via an eNB serving the cell in which the UE is camping.
  • SI system information
  • eNB serving the cell in which the UE is camping.
  • CONNECTED state is often referred to as a “suitable cell”, and UE’s state when performing these actions (i.e., before moving to RRC_CONNECTED) is often referred to as “camped normally”.
  • a UE must perform a random-access (RA) procedure to move from RRC_IDLE to RRC_CONNECTED.
  • RRC_CONNECTED state the cell serving the UE is known and an RRC context is established for the UE in the serving eNB, such that the UE and eNB can communicate.
  • a Cell Radio Network Temporary Identifier (C-RNTI) - a UE identity used for signaling between UE and network - is configured for a UE in RRC_CONNECTED state.
  • C-RNTI Cell Radio Network Temporary Identifier
  • NR New Radio
  • 3GPP Third-Generation Partnership Project
  • NR is developed for maximum flexibility to support multiple and substantially different use cases but shares many similarities with fourth-generation LTE.
  • 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 that are further divided into slots having multiple OFDM-based symbols.
  • RRC_IDLE and RRC_CONNECTED the NR RRC layer also includes an RRC_INACTIVE state with properties similar to a “suspended” condition in LTE Rel-13.
  • Seamless mobility is a key feature of 3GPP radio access technologies (RATs).
  • a network 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.
  • RRM radio resource management
  • Seamless handovers ensure that the UE moves around in the coverage area of different cells without causing too many interruptions in data transmission.
  • RLF radio link failure
  • HAF handover failure
  • the UE may experience failure when trying to reestablish a failed connection with the network, causing the UE to declare connection establishment failure (CEF).
  • RLF radio link failure
  • CEF connection establishment failure
  • UE failure reporting procedures were introduced as part of the mobility robustness optimization (MRO) in LTE Rel-9.
  • MRO mobility robustness optimization
  • UEs log relevant information at the time of failure (e.g., RLF) and later report such information to the network via target cells to which UEs ultimately connect (e.g., after reestablishment).
  • the reported information can include RRM measurements of various neighbor cells prior to the mobility operation (e.g., handover).
  • UEs can be configured to perform and report measurements to support minimization of drive tests (MDT), which is intended to reduce and/or minimize the requirements for manual testing of actual network performance (i.e., by driving around the coverage area of the network).
  • MDT drive tests
  • MDT was standardized for NR in Rel-16 to reduce the amount of drive tests performed manually.
  • MDT is a UE assisted framework where network measurements are collected by both IDLE/INACTIVE and RRC (radio resource control) Connected UE(s) in order to aid the network in gathering valuable information.
  • MDT has been specified for both LTE and NE in 3GPP TS 37.320.
  • a UE in RRC_IDLE/RRC_INACTIVE state is configured to perform periodical and event triggered MDT logging after receiving the MDT configurations from the network.
  • the UE shall report the DL (downlink) pilot strength measurements (RSRP (reference signal received power/RSRQ (reference signal received quality) together with time information, detailed location information if available, and WLAN, Bluetooth to the network via using the UE information framework when it is in RRC_CONNECTED state.
  • RSRP reference signal received power/RSRQ (reference signal received quality)
  • the DL pilot strength measurement of Logged MDT is collected based on the existing measurements required for cell reselection purpose, without imposing UE to perform additional measurements.
  • Table 1 lists measurement logging for Logged MDT
  • UE For Periodical Logged MDT, UE receives the MDT configurations including logginginterval and logging duration in the RRC message, i.e., LoggedMeasurementConfiguration, from the network.
  • a timer (T330) is started at the UE upon receiving the configurations and set to loggingduration (10 min - 120 min).
  • the UE shall perform periodical MDT logging with the interval set to logginginterval (1.28 s - 61.44 s) when the UE is in RRC_IDLE.
  • An example of the MDT logging is shown in Figure 3.
  • For event triggered Logged MDT UE receives eventType and logginginterval from the network. The UE logs the measurement reports at every logginginterval if event configured in eventType is satisfied
  • 3GPP TS 38.304 different categories of cells and state of a UE in those cells are defined.
  • One category of cell is called accepted cell, where UEs may camp to obtain limited service (obtain Emergency Calls and receive ETWS and CMAS notification).
  • a UE camping on an acceptable cell is defined as being in “camped on any cell state”.
  • the UE If the UE cannot find a cell that belongs to suitable cell or acceptable cell, it declares itself being in an any cell selection state. Further details are available in 3GPP TS 38.304.
  • UE access to cells can be controlled at multiple levels; cells can be barred for all UEs or a specific group of UEs based on some network-controlled criteria. Examples include UEs having certain access identities might be allowed on cells which the operator reserves for its internal use. Details of cell reservations and UE access identities can be found in 3GPP TS 38.304 and 3GPP TS 22.261, respectively.
  • UEs in “camped on any cell” state should also include some reports as part of logged MDT framework. Details of which are still not published or discussed. Furthermore, logged MDT configuration while UE is in “any cell selection” state or “camped normally” state is standardized and can be found in 3GPP TS 38.331.
  • UEs will log different measurement results only if it is “camped normally” state or “Any cell selection” state.
  • the network may interpret the result as the particular cell being the best cell for UE, i.e., in the particular environment.
  • the UE has another possible state known as “camped on any cell state”, logging on which is not covered under current specifications.
  • the UE can be camped normally in a cell that is suitable but not best cell due to some network barring configuration which could be optimized by network.
  • Various embodiments of inventive concepts provides a first set of information logged by a wireless terminal as a report while in “camped on any cell” state.
  • the first set of information logged by the UE may or may not be dependent on a configuration policy associated to “camped on any cell” state set by the network.
  • a second set of information logged by a wireless terminal as part of the logged MDT report or as a separate logged MDT report while in the "any cell selection" state.
  • the second set of information logged by the UE may or may not be dependent on a configuration policy associated to the "any cell selection" set by the network.
  • a method by a communication device includes while being in an any cell section state or a camped on any cell state: logging at least one of a first set of information while in a camped on an any cell state as a report and a second set of information while in an any cell selection state, the second set of information being different from the first set of information and including a reason for the communication device being in the any cell selection state, the second set of information added to the report.
  • the method includes transmitting the report towards a network node.
  • the method further includes based on one or more cell reselection criteria, determining that a first cell in a radio access network, RAN, is a best cell for camping in a non-connected state.
  • the method further includes based on determining that the communication device is barred from accessing the first cell, selecting a second cell for camping in the non-connected state.
  • the method further includes that the logging further comprises logging the following first information while camping normally on the second cell: measurement information related to the second cell being camped on in the any cell state, and an identifier of the first cell as the best cell determined according to the cell reselection criteria.
  • a method performed by a network node includes transmitting at least one of: a first configuration that configures the communication device with a periodical logged measurements configuration including a first set of information while in a camped on any cell state; and a second configuration that configures the communication device with a periodical logged measurements configuration including a second set of information while in the any cell selection state.
  • the method includes receiving a report having logged at least one of: the first set of information when the communication device was in the camped on any cell state; and the second set of information when the communication device was in the any cell selection state.
  • the method further includes receiving, from a user equipment (UE), a measurement report including the following first information: an identifier of a first cell in the RAN, the first cell being selected by the UE as a best cell for camping in a non-connected state according to cell reselection criteria; and measurement information related to a second cell in the RAN, the second cell being selected by the UE instead of the first cell because the UE was barred from accessing the first cell.
  • the method further includes performing one or more of the following based on the measurement report: determining coverage for at least one of the first cell and the second cell; and selecting an accessing barring configuration for at least one of the first cell and the second cell.
  • Certain embodiments may provide one or more of the following technical advantage(s).
  • the various embodiments of inventive concepts enable the UE to log additional information in logged MDT report to aid the network in gaining further insight about the coverage condition and allows the network to gather information from the UEs while they are in “camped on any cell” state.
  • the various embodiments further allow the network to gain insights about conditions when the UE is in “any cell selection” state. This information in turn allows the network to create better coverage map.
  • the network is further enabled to understand the impact of certain configuration, e.g., impact of barring some cells and possibly optimize such configuration.
  • Figure 1 is a high-level illustration of an exemplary LTE network architecture
  • Figure 2 shows an exemplary LTE control-plane (CP) protocol stack
  • Figure 3 is an example of a logged MDT procedure
  • Figures 4-5 show two exemplary views of a 5G network architecture
  • Figure 6 is a block diagram illustrating a communication device according to some embodiments of the present disclosure.
  • FIG. 7 is a block diagram illustrating a radio access network RAN node (e.g., a base station eNB/gNB) according to some embodiments of the present disclosure
  • Figure 8 shows a flow diagram of an exemplary method (e.g., procedure) for a UE (e.g., wireless device, MTC device, NB-IoT device, modem, etc. or component thereof), according to various embodiments of the present disclosure;
  • a UE e.g., wireless device, MTC device, NB-IoT device, modem, etc. or component thereof
  • Figure 9 shows a flow diagram of an exemplary method (e.g., procedure) for a network node (e.g., base station, eNB, gNB, ng-eNB, en-gNB, etc. or component thereof), according to various embodiments of the present disclosure
  • a network node e.g., base station, eNB, gNB, ng-eNB, en-gNB, etc. or component thereof
  • Figures 10-15 are flow chart illustrating operations of a communication device according to some embodiments of the present disclosure.
  • Figure 16 is a flow chart illustrating operations of a network node according to some embodiments of the present disclosure.
  • Figure 17 is a block diagram of a communication system in accordance with some embodiments.
  • Figure 18 is a block diagram of a user equipment in accordance with some embodiments
  • Figure 19 is a block diagram of a network node in accordance with some embodiments.
  • Figure 20 is a block diagram of a host computer communicating with a user equipment in accordance with some embodiments.
  • Figure 21 is a block diagram of a virtualization environment in accordance with some embodiments.
  • Figure 22 is a block diagram of a host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments in accordance with some embodiments.
  • Radio Node As used herein, a “radio node” can be either a “radio access node” or a “wireless device.”
  • 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) of a cellular communications network 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., a New Radio (NR) base station (gNB) in a 3GPP Fifth Generation (5G) NR network or an enhanced or evolved Node B (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, a remote radio unit (RRU or RRH), and a relay node.
  • a base station e.g., a New Radio (NR) base station (gNB) in a 3GPP Fifth Generation (5G) NR network or an enhanced or evolved Node B (eNB) in a 3GPP LTE network
  • base station distributed components e.g., CU and DU
  • 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 Packet Data Network Gateway (P-GW), an access and mobility management function (AMF), a session management function (SMF), a location management function (LMF), a user plane function (UPF), a Network Exposure Function (NEF), or the like.
  • MME Mobility Management Entity
  • SGW serving gateway
  • P-GW Packet Data Network Gateway
  • AMF access and mobility management function
  • SMF session management function
  • LMF location management function
  • UPF user plane function
  • NEF Network Exposure Function
  • Wireless Device As used herein, a “wireless device” (or “WD” for short) is any type of device that has access to (i.e., is served by) a cellular communications network by 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 examples include, but are not limited to, smart phones, mobile phones, cell phones, voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, gaming consoles or devices, music storage devices, playback appliances, wearable devices, wireless endpoints, mobile stations, tablets, laptops, laptop- embedded equipment (LEE), laptop-mounted equipment (LME), smart devices, wireless customer-premise equipment (CPE), mobile-type communication (MTC) devices, Internet-of-Things (loT) devices, vehicle-mounted wireless terminal devices, etc.
  • the term “wireless device” is used interchangeably herein with the term “user equipment” (or “UE” for short).
  • Network Node is any node that is either part of the radio access network (e.g., a radio access node or equivalent name discussed above) or of the core network (e.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.
  • FIG 4 illustrates a high-level view of an exemplary 5G network architecture, consisting of a Next Generation RAN (NG-RAN 499) and a 5G Core (5GC 498).
  • NG-RAN 499 can include a set of gNodeB’s (gNBs) connected to the 5GC via one or more NG interfaces, whereas the gNBs can be connected to each other via one or more Xn interfaces, such as Xn interface 440 between gNBs 400 and 450 in Figure 4.
  • gNBs can support frequency division duplexing (FDD), time division duplexing (TDD), or a combination thereof on the NR interface to UEs.
  • FDD frequency division duplexing
  • TDD time division duplexing
  • NG-RAN 499 is layered into a Radio Network Layer (RNL) and a Transport Network Layer (TNL).
  • RNL Radio Network Layer
  • TNL Transport Network Layer
  • the NG-RAN architecture i.e., the NG-RAN logical nodes and interfaces between them, is defined as part of the RNL.
  • NG, Xn, Fl the related TNL protocol and the functionality are specified.
  • the TNL provides services for user plane transport and signaling transport.
  • each gNB is connected to all 5GC nodes within an “AMF Region,” with the term “AMF” being discussed in more detail below.
  • the NG RAN logical nodes shown in Figure 4 include a central (or centralized) unit (CU or gNB-CU) and one or more distributed (or decentralized) units (DU or gNB-DU).
  • gNB 400 in Figure 4 includes gNB-CU 410 and gNB-DUs 420 and 430.
  • CUs e.g., gNB-CU 410) are logical nodes that host higher-layer protocols and perform various gNB functions such controlling the operation of DUs.
  • Each DU is a logical node that hosts lower- layer protocols and can include, depending on the functional split, various subsets of the gNB functions.
  • each of the CUs and DUs can include various circuitry needed to perform their respective functions, including processing circuitry, transceiver circuitry (e.g., for communication), and power supply circuitry.
  • processing circuitry e.g., for communication
  • transceiver circuitry e.g., for communication
  • power supply circuitry e.g., for power supply circuitry.
  • central unit and centralized unit are used interchangeably herein, as are the terms “distributed unit” and “decentralized unit.”
  • a gNB-CU connects to its associated gNB-DUs over respective Fl logical interfaces, such as interfaces 422 and 432 shown in Figure 4.
  • the gNB-CU and connected gNB-DUs are only visible to other gNBs and the 5GC as a gNB, e.g., the Fl interface is not visible beyond gNB-CU.
  • DC can be achieved by allowing a UE to connect to multiple DUs served by the same CU or by allowing a UE to connect to multiple DUs served by different CUs.
  • FIG. 5 shows another high-level view of an exemplary 5G network architecture, including NG-RAN 599 and 5GC 598.
  • NG-RAN 599 can include gNBs 510 (e.g., 510a, b) and ng-eNBs 520 (e.g., 520a, b) that are interconnected with each other via respective Xn interfaces.
  • gNBs 510 e.g., 510a, b
  • ng-eNBs 520 e.g., 520a, b
  • the gNBs and ng-eNBs are also connected via the NG interfaces to 5GC 598, more specifically to the AMF (Access and Mobility Management Function) 530 (e.g., AMFs 530a, b) via respective NG-C interfaces and to the UPF (User Plane Function) 540 (e.g., UPFs 540a, b) via respective NG-U interfaces.
  • the AMFs 530a, b can communicate with one or more policy control functions (PCFs, e.g., PCFs 550a, b) and network exposure functions (NEFs, e.g., NEFs 560a, b).
  • PCFs policy control functions
  • NEFs network exposure functions
  • Each of the gNBs 510 can support the NR radio interface including FDD, TDD, or a combination thereof.
  • each of ng-eNBs 520 can support the LTE radio interface but, unlike conventional LTE eNBs (e.g., in Figure 1), connect to the 5GC via the NG interface.
  • Each or gNB or ng-eNB can serve a geographic coverage area including one more cells, such as cells 51 la-b and 521a-b shown in Figure 5.
  • a UE 505 can communicate with the gNB or ng-eNB serving that cell via the NR or LTE radio interface, respectively.
  • UE 505 can operate in multi-connectivity (MC) with any two or more of gNBs 510a,b and ng-eNBs 520a, b via the cells served by those respective nodes.
  • MC multi-connectivity
  • the gNBs and ng-eNBs 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
  • a UE in RRC_CONNECTED state can be handed over from a serving (or source) cell to a target cell for various reasons, including mobility load balancing (MLB) for capacity purposes and radio link failure (RLF) avoidance for coverage purposes.
  • MLB mobility load balancing
  • RLF radio link failure
  • a UE in RRC_IDLE or RRC_INACTIVE performs cell reselection primarily for coverage purposes and these decisions are very static in nature.
  • RRC_CONNECTED state the network typically configures the UE to perform and report radio resource management (RRM) measurements to assist network-controlled mobility decisions such as handover from one cell to another.
  • RRM radio resource management
  • a RLF procedure is typically triggered in the UE when something unexpected happens in any of the mobility-related procedures, including handover.
  • the RLF procedure involves interactions between RRC and lower layer protocols such as PHY (or LI), MAC, RLC, etc. including radio link monitoring (RLM) on LI.
  • the UE may take autonomous actions such as trying to select a cell and initiate reestablishment procedure so that the UE can remain reachable by the network.
  • a UE declares RLF only when the UE realizes that there is no reliable communication channel (or radio link) available between itself and the network, which can result in poor user experience.
  • reestablishing the connection requires signaling with a newly selected cell (e.g., random access procedure, exchanging various RRC messages, etc.), introducing latency until the UE can again reliably transmit and/or receive user data with the network.
  • the two sets of information are independent of each other and independent to the configuration policy of the network.
  • Figure 6 is a block diagram illustrating elements of a communication device 600 (also referred to as a mobile terminal, a mobile communication terminal, a wireless device, a wireless communication device, a wireless terminal, mobile device, a wireless communication terminal, user equipment, UE, a user equipment node/terminal/device, etc.) configured to provide wireless communication according to embodiments of inventive concepts.
  • a communication device 600 also referred to as a mobile terminal, a mobile communication terminal, a wireless device, a wireless communication device, a wireless terminal, mobile device, a wireless communication terminal, user equipment, UE, a user equipment node/terminal/device, etc.
  • Communication device 600 may be provided, for example, as discussed below with respect to wireless devices UE 1712A, UE 1712B, and wired or wireless devices UE 1712C, UE 1712D of Figure 17, UE 1800 of Figure 18, virtualization hardware 2104 and virtual machines 2108A, 2108B of Figure 21, and UE 2206 of Figure 22, all of which should be considered interchangeable in the examples and embodiments described herein and be within the intended scope of this disclosure, unless otherwise noted.
  • communication device 600 may include an antenna 607 (e.g., corresponding to antenna 1822 of Figure 18), and transceiver circuitry 601 (also referred to as a transceiver, e.g., corresponding to interface 1812 of Figure 18 having transmitter 1818 and receiver 1820) including a transmitter and a receiver configured to provide uplink and downlink radio communications with a base station(s) (e.g., corresponding to network node 1710A, 1710B of Figure 17, network node 1900 of Figure 19, and network node 2204 of
  • Communication device UE 600 may also include processing circuitry 603 (also referred to as a processor, e.g., corresponding to processing circuitry 1802 of Figure 18, and control system 2112 of Figure 21) coupled to the transceiver circuitry, and memory circuitry 605 (also referred to as memory, e.g., corresponding to memory 1810 of Figure 17) coupled to the processing circuitry.
  • the memory circuitry 605 may include computer readable program code that when executed by the processing circuitry 603 causes the processing circuitry to perform operations according to embodiments disclosed herein. According to other embodiments, processing circuitry 603 may be defined to include memory so that separate memory circuitry is not required.
  • Communication device 600 may also include an interface (such as a user interface) coupled with processing circuitry 603, and/or communication device 600 may be incorporated in a vehicle. Further details of an embodiment of the communication device 600 are illustrated in Figures 17, 18, 21, and 22.
  • operations of communication device 600 may be performed by processing circuitry 603 and/or transceiver circuitry 601.
  • processing circuitry 603 may control transceiver circuitry 601 to transmit communications through transceiver circuitry 601 over a radio interface to a radio access network node (also referred to as a base station) and/or to receive communications through transceiver circuitry 601 from a RAN node over a radio interface.
  • modules may be stored in memory circuitry 605, and these modules may provide instructions so that when instructions of a module are executed by processing circuitry 603, processing circuitry 603 performs respective operations (e.g., operations discussed below with respect to Example Embodiments relating to communication devices).
  • a communication device UE 600 and/or an element(s)/function(s) thereof may be embodied as a virtual node/nodes and/or a virtual machine/machines.
  • FIG. 7 is a block diagram illustrating elements of a radio access network RAN node 700 (also referred to as a network node, base station, eNodeB/eNB, gNodeB/gNB, etc.) of a Radio Access Network (RAN) configured to provide cellular communication according to embodiments of inventive concepts.
  • RAN Radio Access Network
  • RAN node 700 may be provided, for example, as discussed below with respect to network node 1710A, 1710B of Figure 17, network node 1900 of Figure 19, hardware 2104 or virtual machine 2108A, 2108B of Figure 21, and/or base station 2204 of Figure 22, all of which should be considered interchangeable in the examples and embodiments described herein and be within the intended scope of this disclosure, unless otherwise noted.
  • the RAN node 700 may include transceiver circuitry 701 (also referred to as a transceiver, e.g., corresponding to portions of RF transceiver circuitry 1912 and radio front end circuitry 1918 of Figure 19) including a transmitter and a receiver configured to provide uplink and downlink radio communications with mobile terminals.
  • the RAN node may include network interface circuitry 707 (also referred to as a network interface, e.g., corresponding to portions of communication interface 1906 of Figure 19) configured to provide communications with other nodes (e.g., with other base stations) of the RAN and/or core network CN.
  • the network node may also include processing circuitry 703703 (also referred to as a processor, e.g., corresponding to processing circuitry 1902 of Figure 19) coupled to the transceiver circuitry, and memory circuitry 705 (also referred to as memory, e.g., corresponding to memory 1904 of Figure 19) coupled to the processing circuitry.
  • the memory circuitry 705 may include computer readable program code that when executed by the processing circuitry 703703 causes the processing circuitry to perform operations according to embodiments disclosed herein. According to other embodiments, processing circuitry 703703 may be defined to include memory so that a separate memory circuitry is not required.
  • operations of the RAN node 700 may be performed by processing circuitry 703703, network interface 707, and/or transceiver 701.
  • processing circuitry 703703 may control transceiver 701 to transmit downlink communications through transceiver 701 over a radio interface to one or more mobile terminals UEs and/or to receive uplink communications through transceiver 701 from one or more mobile terminals UEs over a radio interface.
  • processing circuitry 703703 may control network interface 707 to transmit communications through network interface 707 to one or more other network nodes and/or to receive communications through network interface from one or more other network nodes.
  • modules may be stored in memory 705, and these modules may provide instructions so that when instructions of a module are executed by processing circuitry 703703, processing circuitry 703703 performs respective operations (e.g., operations discussed below with respect to Example Embodiments relating to RAN nodes).
  • RAN node 700 and/or an element(s)/function(s) thereof may be embodied as a virtual node/nodes and/or a virtual machine/machines.
  • a network node may be implemented as a core network CN node without a transceiver.
  • transmission to a wireless communication device UE may be initiated by the network node so that transmission to the wireless communication device UE is provided through a network node including a transceiver (e.g., through a base station or RAN node).
  • initiating transmission may include transmitting through the transceiver.
  • the communication device 600 will be used to describe the various embodiments.
  • the communication device 600 performs periodic MDT logging every logginginterval (1.28-61.44 s) within the loggingduration while the communication device 600 is in RRC_IDLE state (or in RRC_INACTIVE, not shown).
  • the communication device 600 transitions to RRC_CONNECTED during the loggingduration, the communication device 600 pauses or stops the ongoing MDT measurement logging while leaving timer T330 running, and then resumes the MDT measurement logging with the same logginginterval upon returning to RRC_IDLE.
  • the communication device 600 stops the logging upon expiration of T330.
  • the communication device 600 collects DL RS received strength and quality (i.e., RSRP, RSRQ) based on existing measurements required for cell reselection purposes. In other words, the communication device 600 is not required to perform additional LTE or NR measurements beyond those existing ones.
  • the communication device 600 also logs detailed location information, WLAN measurements, and BT measurements, to the extent that these are available. The communication device 600 reports the logged information to the network when the communication device 600 returns to RRC_CONNECTED state.
  • An ASN.l data structure for an exemplary LoggedMeasurement-Configuration message is shown below.
  • This configuration can include the logginginterval and loggingduration fields, as well as an areaConfiguration field that indicates a geographic area for which the communication device 600 is requested to perform measurement logging.
  • LoggedMeasurementConfiguration-rlO SEQUENCE ⁇ criticalExtensions CHOICE ⁇ cl CHOICE ⁇ loggedMeasurementConfiguration-r 10 LoggedMeasurementConfiguration-rlO-IEs, spare3 NULL, spare2 NULL, sparel NULL ⁇ , criticalExtensionsFuture SEQUENCE ⁇ ⁇
  • ⁇ ⁇ LoggedMeasurementConfiguration-rlO-Ies SEQUENCE ⁇ traceReference-r 10 TraceReference-r 10, traceRecordingSessionRef-rlO OCTET STRING (SIZE (2)), tce-Id-rlO OCTET STRING (SIZE (1)), absoluteTimelnfo-rlO AbsoluteTimelnfo-rlO, areaConfiguration-rlO AreaConfiguration-rlO OPTIONAL, — Need OR loggingDuration-r 10 LoggingDuration-r 10, logginglnterval-r 10 Logginglnterval-r 10, nonCriticalExtension LoggedMeasurementConfiguration-v 1080- les OPTIONAL
  • LoggedMeasurementConfiguration-vl080-Ies SEQUENCE ⁇ lateNonCriticalExtension-rlO OCTET STRING OPTIONAL, nonCriticalExtension LoggedMeasurementConfiguration-vl 130-Ies OPTIONAL ⁇
  • LoggedMeasurementConfiguration-vl l30-Ies SEQUENCE ⁇ plmn-IdentityList-rll PLMN-IdentityList3-rll OPTIONAL, — Need OR areaConfiguration-vl l30 AreaConfiguration-vll30 OPTIONAL, — Need OR nonCriticalExtension LoggedMeasurementConfiguration-v 1250-Ies OPTIONAL
  • LoggedMeasurementConfiguration-vl 250-Ies SEQUENCE ⁇ targetMBSFN-AreaList-rl2 TargetMBSFN-AreaList-rl2 OPTIONAL, — Need OP nonCriticalExtension LoggedMeasurementConfiguration-vl 530-Ies OPTIONAL ⁇
  • LoggedMeasurementConfiguration- v 1530-Ies :: SEQUENCE ⁇ bt-NameList-rl5 B T-N ameList-r 15
  • TargetMBSFN-AreaList-rl2 SEQUENCE (SIZE (O..maxMBSFN-Area)) OF
  • TargetMBSFN-Area-rl2 SEQUENCE ⁇ mbsfn-AreaId-rl2
  • ASN.1 data structure for an exemplary areaConfiguration field is illustrated below:
  • AreaConfiguration-rlO CHOICE ⁇ cellGloballdList-rlO CellGloballdList-rlO, trackingAreaCodeList-r 10 Tracking AreaCodeList-r 10
  • CellGloballdList-rlO :: SEQUENCE (SIZE (1..32)) OF CellGloballdEUTRA
  • TrackingAreaCodeList-r 10 :: SEQUENCE (SIZE (1..8)) OF TrackingAreaCode
  • TrackingAreaCodeList-vl l30 :: SEQUENCE ⁇ plmn-Identity-perTAC-List-rl 1 SEQUENCE (SIZE (1..8)) OF PLMN-Identity
  • a communication device 600 camping on a cell Upon receiving such information, a communication device 600 camping on a cell will check if the cell is part of the area scope identified in areaConfiguration and will perform MDT logging if the serving cell is part of the area scope. If areaConfiguration is not present/configured, measurement logging is not restricted to specific cells or tracking areas but applies as long as the public land mobile network in which the communication device 600 is registered (referred to as “RPLMN”) is included in a plmn-IdentityList stored in the communication device 600’ s VarLogMeasReport.
  • RPLMN public land mobile network in which the communication device 600 is registered
  • the above configuration also includes a traceReference, tce-Id, and traceRecordingSessionRef parameters that identify the trace collection entity (TCE) that originated the request and should receive the MDT report.
  • TCE trace collection entity
  • An ASN.1 data structure for an exemplary traceReference field, which includes a PLMN identity and a trace identifier is illustrated below:
  • TraceReference-rlO SEQUENCE ⁇ plmn-Identity-rlO PLMN-Identity, traceld-rlO OCTET STRING (SIZE (3))
  • the communication device 600 After receiving a LoggedMeasurementConfiguration RRC message from the network, the communication device 600 stores the received configuration in the communication device 600 variable VarLogMeasConfig.
  • VarLogMeasConfig variable and/or IE is shown below:
  • VarLogMeasConfig-rlO SEQUENCE ⁇ areaConfiguration-r 10 AreaConfiguration-r 10 OPTIONAL, loggingDuration-r 10 LoggingDuration-rlO, logginglnterval-rlO Logginglnterval-r 10 ⁇
  • V arLogMeasConfig-r 11 SEQUENCE ⁇ areaConfiguration-r 10 AreaConfiguration-r 10 OPTIONAL, areaConfiguration-vl 130 AreaConfiguration- v 1130 OPTIONAL, loggingDuration-r 10 LoggingDuration-rlO, logginglnterval-rlO Logginglnterval-r 10
  • VarLogMeasConfig-rl2 SEQUENCE ⁇ areaConfiguration-r 10 AreaConfiguration-r 10 OPTIONAL, areaConfiguration-vl 130 AreaConfiguration- v 1130 OPTIONAL, loggingDuration-r 10 LoggingDuration-rlO, logginglnterval-rlO Logginglnterval-r 10, targetMB SFN- AreaList-r 12 T argetMB SFN- AreaList-r 12 OPTIONAL ⁇
  • VarLogMeasConfig-rl5 SEQUENCE ⁇ areaConfiguration-r 10 AreaConfiguration-r 10 OPTIONAL, areaConfiguration-vl 130 AreaConfiguration- v 1130 OPTIONAL, loggingDuration-r 10 LoggingDuration-r 10, logginglnterval-rlO Logginglnterval-rlO, targetMB SFN- AreaList-r 12 T argetMB SFN- AreaList-r 12 OPTIONAL, bt-NameList-rl5 BT-NameList-rl5 OPTIONAL, wlan-NameList-rl5 WL AN-N ameList-r 15 OPTIONAL
  • the communication device 600 stores measurements logged according to this configuration in the communication device 600 variable VarLogMeasReport.
  • VarLogMeasReport An ASN.1 data structure for an exemplary VarLogMeasReport variable and/or IE is shown below:
  • VarLogMeasReport-rlO SEQUENCE ⁇ traceReference-r 10 TraceReference-rlO, traceRecordingSessionRef-r 10 OCTET STRING (SIZE (2)), tce-Id-rlO OCTET STRING (SIZE (1)) plmn-Identity-r 10 PLMN-Identity, absoluteT imelnfo-r 10 AbsoluteTimelnfo-rlO, logMeasInfoList-r 10 LogMeasInfoList2-rlO
  • LogMeasInfoList2-rlO :: SEQUENCE (SIZE (L.maxLogMeas-rlO)) OF LogMeasInfo-rlO
  • LogMeasInfo-rlO :: SEQUENCE ⁇ locationlnfo-rlO Locationlnfo-rlO OPTIONAL. relativeT imeStamp-r 10 INTEGER (0..7200), servCellldentity-r 10 CellGloballdEUTRA, measResultServCell-rl SEQUENCE ⁇ rsrpResult-rlO RSRP-Range, rsrqResult-rlO RSRQ-Range ⁇ , measResultNeighCells-r 10 SEQUENCE ⁇ measResultListEUTR A-r 10 MeasResultList2EUTR A-r9
  • measResultListGERAN -r 10 MeasResultList2GER AN -r 10
  • MeasResultList2EUTRA-r9 SEQUENCE (SIZE (L.maxFreq)) OF MeasResult2EUTRA-r9
  • MeasResult2EUTRA-r9 SEQUENCE ⁇ carrierFreq-r9 ARFCN-ValueEUTRA, measResultList-r9 MeasResultListEUTRA
  • MeasResultListEUTRA SEQUENCE (SIZE (L.maxCellReport)) OF MeasResultEUTRA
  • MeasResultEUTRA SEQUENCE ⁇ physCellld PhysCellld, cgi-Info SEQUENCE ⁇ cellGloballd CellGloballdEUTRA, trackingAreaCode TrackingAreaCode, plmn-IdentityList PLMN -Identity List2 OPTIONAL ⁇
  • cgi-Info-vl310 SEQUENCE ⁇ freqB andlndicator-r 13 FreqB andlndicator-rl 1 OPTIONAL, multiB andlnfoList-r 13 MultiBandlnfoList-rl 1 OPTIONAL, freqB andlndicatorPriority-r 13 ENUMERATED ⁇ true ⁇ OPTIONAL
  • the network can request the communication device 600 to provide a logged measurement report by sending a UEInformationRequest message with the logMeasReportReq field set to “true”.
  • the communication device 600 responds with a UEInformationResponse message that includes the indicated/requested logged measurement report.
  • a cell in which an RRC...IDLE LIE can receive broadcast SI, perform measurements of neighbor cells to support cell reselection, monitor a paging channel, and move to RRC_CONNECTED state as needed is often referred to as a “suitable cell”.
  • the communication device 600’ s state when performing these actions in such a cell is often referred to as "camped normally”.
  • a network can control communication device 600 access to each cell in various ways and/or on various levels. For example, access to a particular cell (or group of cells) can be barred for all communication devices 600, a specific group of communication device 600s, all except a specific group of communication devices 600, etc. based on various network- controlled criteria. For example, communication devices 600 having certain access identities might be allowed on cells reserved by a network operator for its internal use, while all other communication devices 600 are barred from accessing these cells. More details about 3GPP- specific cell barring mechanisms are given in 3GPP TS 38.304 (vl6.5.0) and 22.261 (vl8.3.0).
  • the communication device 600 may have selected the particular cell for camping because the communication device 600 is barred from accessing one or more other cells in the same environment that the communication device 600 would otherwise prefer (e.g., due to stronger/better signal than the particular cell). If configured by the network, the communication device 600 will log MDT -related information for the particular cell and report the logged information upon returning to RRC_CONNECTED.
  • the network may interpret the particular cell being the best cell for communication device 600 in that environment. This is not the case, however, due to the access barring for the other cells. Based on this misinformation, the network may take various actions to build and/or improve coverage in the vicinity of the particular cell. However, these misinformed actions may not improve coverage and/or may degrade coverage in the vicinity of the particular cell and/or other coverage areas.
  • some embodiments of the present disclosure provide flexible and efficient techniques for a communication device 600 to log additional information about cell barring while it is camped normally in a cell and to include this information into a subsequent logged MDT report.
  • This additional information facilitates better insight into actual coverage conditions experienced by communication devices 600 in the network.
  • embodiments enable the network to understand impacts of different access barring configurations (e.g., access barring of different subsets of cells and/or different groups of communication devices 600), and to select an appropriate access barring configuration based on this information.
  • a communication device 600 can be configured (e.g., by receiving a LoggedMeasurementConfiguration message from the network and storing in VarLogMeasConfig) to log various measurement-related information when the communication device 600 is camped normally in cells.
  • the measurement-related information can include any measurements and/or information currently logged by the communication device 600 in this scenario.
  • the communication device 600 when the communication device 600 is camped normally on a cell that is not a “best cell” according to cell reselection criteria and the communication device 600 is barred from accessing the best cell (i.e., best cell is a barred cell) , the communication device 600 also logs an identifier of the barred cell that is the best cell, according to one of the following:
  • PLMN public land mobile network
  • the communication device 600 can condition the logging of the identifier on the identifier being part of a PLMN in the list and being associated with the areaConfig.
  • the communication device 600 when the communication device 600 logs the identifier of the barred cell, the communication device 600 can also log one of the more of the following information related to the barred cell:
  • MIB master information block
  • SIBs SI blocks
  • the communication device 600 can store the logged measurement-related information and the identifier of the barred cell (along any of the related information logged) in the communication device 600 variable VarLogMeasReport.
  • VarLogMeasReport the exemplary ASN.1 data structure of the VarLogMeasReport can be modified to include such additional information.
  • the network can request the communication device 600 to provide the logged measurement report by sending a UEInformationRequest message with the logMeasReportReq field set to “true”.
  • the communication device 600 responds with a UEInformationResponse message that includes the indicated/requested logged measurement report with the additional information related to the barred cell encountered by the communication device 600.
  • FIG. 8-9 show exemplary methods (e.g., procedures) for a communication device 600 and a network node, respectively.
  • Figures 8-9 show specific blocks in particular orders, the operations of the respective methods can be performed in different orders than shown and can be combined and/or divided into blocks having different functionality than shown.
  • Figure 8 shows a flow diagram of an exemplary method (e.g., procedure) for a communication device 600 configured to operate in a radio access network (RAN), according to various embodiments of the present disclosure.
  • the exemplary method can be performed by a communication device 600 e.g., wireless device, MTC device, NB-IoT device, modem, etc. or component thereof) such as described elsewhere herein.
  • the exemplary method can include the operations of block 803, in which the communication device 600 can, based on one or more cell reselection criteria, determine that a first cell in the RAN is a best cell for camping in a non-connected state. In other words, the communication device 600 is determining that the first cell in the RAN is a best cell for camping in a camped normally state.
  • the exemplary method can also include the operations of block 805, in which the communication device 600 can, based on determining that the communication device 600 is barred from accessing the first cell, select a second cell in the RAN for camping in the non-connected state.
  • the exemplary method can also include the operations of block 807, in which the communication device 600 can log the following first information while camping normally on the second cell:
  • the exemplary method can also include the operations of block 817, where the communication device 600 can send, to the RAN, a measurement report including the first information.
  • the exemplary method can also include the operations of block 801, where the communication device 600 can receive a measurement reporting configuration from the RAN. In such case, logging the first information while camping normally on the second cell (e.g., block 807) and sending the measurement report (e.g., block 807) is based on the measurement reporting configuration.
  • the measurement reporting configuration is a logged MDT configuration and the measurement report is a logged MDT report.
  • logging the identifier of the first cell is responsive to one or more of the following conditions:
  • the public land mobile network (PLMN) of the first cell is in a list of PLMNs included in the measurement reporting configuration or stored in the communication device 600;
  • the first cell is included in or associated with an area configuration included in the measurement reporting configuration.
  • the exemplary method can also include the operations of block 950, where the communication device 600 can log one or more of the following second information while camping normally in the second cell:
  • MIB master information block
  • SIBs SI blocks
  • the logged second information is included in the measurement report.
  • the second information when the second information indicates that access barring was indicated in a SIB broadcast in the first cell, the second information also includes indications of one or more of the following:
  • PLMNs public land mobile networks
  • NPNs non-public networks
  • SNPN standalone NPN
  • the communication device 600 is not authorized to access the SNPN (i.e., non-SNPN UE);
  • the exemplary method can also include the operations of block 811, where the communication device 600 can exit the non-connected state and enter a connected state with the RAN. The measurement report is sent after entering the connected state.
  • the exemplary method can also include the operations of blocks 813-815, where the communication device 600 can, after entering the connected state, send to the RAN an indication that a measurement report is available and receive a request for the measurement report from the RAN in response to the indication . The measurement report can be sent in response to the request.
  • Figure 9 shows a flow diagram of an exemplary method (e.g., procedure) for a network node in a RAN, according to various embodiments of the present disclosure.
  • the exemplary method shown in Figure 9 can be performed by a network node e.g., base station, eNB, gNB, ng-eNB, en-gNB, etc. or component thereof) such as described elsewhere herein.
  • the exemplary method can include the operations of block 907, in which the network node can receive, from a communication device 600, a measurement report including the following first information:
  • the exemplary method can also include the operations of block 909, where the network node can perform one or more of the following based on the measurement report:
  • the exemplary method can also include the operations of block 901, where the network node can send a measurement reporting configuration to the communication device 600.
  • the measurement report (e.g., in block 907) is based on the measurement reporting configuration.
  • the measurement reporting configuration is a logged MDT configuration and the measurement report is a logged MDT report.
  • the identifier of the first cell is included in the measurement report based on one or more of the following conditions:
  • the PLMN of the first cell is in a list of PLMNs included in the measurement reporting configuration or stored in the communication device 600;
  • the first cell is included in or associated with an area configuration included in the measurement reporting configuration.
  • the measurement report also includes one or more of the following second information:
  • the second information when the second information indicates that access barring was indicated in a SIB broadcast in the first cell, the second information also includes indications of one or more of the following:
  • the measurement report is received (e.g., in 907) after the communication device 600 exits the non-connected state and enters a connected state with the RAN.
  • the exemplary method can also include the operations of blocks 903-905, where the network node can, after the communication device 600 enters the connected state, receive from the communication device 600 an indication that a measurement report is available and send a request for the measurement report to the communication device 600 in response to the indication. The measurement report can be received in response to the request.
  • the above embodiments describe overall operation of communication device 600s when a cell is barred for the communication devices 600 to camp on, reserved for future use, etc..
  • 3GPP TS 38.304 different categories of cells and state of a communication device 600 in those cells are defined.
  • One category of cell is called accepted cell, where communication devices 600 may camp to obtain limited service (obtain Emergency Calls and receive ETWS and CM AS notification).
  • a communication device 600 camping on an acceptable cell is defined as being in “camped on any cell state”.
  • the above embodiments may be used when the communication device 600 does not explicitly declare itself to be in the any cell selection state.
  • the communication device 600 cannot find a cell that belongs to suitable cell or acceptable cell, it declares itself being in an any cell selection state. Further details are available in 3GPP TS 38.304.
  • a first set of information logged by a communication device 600 is provided as a report while in “camped on any cell” state.
  • the first set of information logged by the communication device 600 may or may not be dependent on a configuration policy set by the network.
  • the report in some embodiments of inventive concepts is a new logged MDT report defined and generated by the communication device 600.
  • the report can be a part of the existing logged MDT report.
  • the first set of information logged by the communication device 600 in various embodiments of inventive concepts includes the various embodiments described hereinbelow.
  • the communication device 600 logs the identifier of the cell while being in “camped on any cell” state.
  • the communication device 600 includes an indication that the current state is 'camped on any cell' state.
  • the communication device 600 logs the cell identifier only if the public land mobile network (PLMN) is in a stored list of logged MDT PLMNs. In other embodiments of this embodiment, the communication device 600 logs the cell identifier without considering the PLMN information.
  • PLMN public land mobile network
  • the communication device 600 logs the first suitable cell where the communication device 600 goes to (i.e., going to) “camped normally” state upon leaving the camped on any cell state.
  • the communication device 600 logs the cell identifier of the first suitable cell only if the public land mobile network (PLMN) is in a stored list of logged MDT PLMNs. In other embodiments of this embodiment, the communication device 600 logs the cell identifier of the first suitable cell without considering the PLMN information.
  • PLMN public land mobile network
  • the communication device 600 logs the last suitable cell that the communication device 600 was camping on in “camped normally” state to before entering “any cell selection” state from which the communication device 600 transitioned to “camped on any cell” state.
  • the communication device 600 logs the cell identifier of the last suitable cell only if the public land mobile network (PLMN) is in a stored list of logged MDT PLMNs. In other embodiments of this embodiment, the communication device 600 logs the cell identifier of the last suitable cell without considering the PLMN information.
  • PLMN public land mobile network
  • the communication device 600 indicates if the communication device has any emergency calls while being in the camped on any cell state. Thus, the communication device 600 indicates if the communication device 600 had received any tsunami or earthquake warning while being in “camped on any cell” state.
  • the communication device 600 includes the total duration for which the communication device 600 was in the camped on any cell state.
  • a second set of information logged by a communication device 600 is provided as a report while in “any cell selection” state.
  • the second set of information logged by the communication device 600 may or may not be dependent on a configuration policy set by the network.
  • the second set of information logged by the communication device 600 in various embodiments of inventive concepts includes the current standard set of measurement information and the information described in the various embodiments described hereinbelow
  • the communication device 600 logs the reason for the communication device 600 being in the "any cell selection" state.
  • reasons are presented below.
  • the communication device 600 did not find any cell that fulfills the cell selection quality criterion as mentioned in various standards.
  • the communication device 600 If the reason for being in “any cell selection” state is that the communication device 600 did not find any cell that fulfills the cell selection quality criterion then the communication device 600 also includes identifier of the cell that was deemed not to fulfil the cell selection criterion.
  • the communication device 600 logs the cell identifier of the cell that was deemed not to fulfil the cell selection criterion only if the public land mobile network (PLMN) is in a stored list of logged MDT PLMNs. In other embodiments of this embodiment, the communication device 600 logs the cell identifier of the cell that was deemed not to fulfil the cell selection criterion without considering the PLMN information.
  • PLMN public land mobile network
  • the communication device 600 determines that cell selection criterion (e.g., cell selection quality criterion) was fulfilled but the cell was barred.
  • the barred information could be broadcasted in the master information block (MIB) or broadcasted in the system information block (SIB).
  • the communication device 600 also includes identifier of the cell whose MIB indicated the barring.
  • the communication device 600 logs the cell identifier of the cell whose MIB indicated the barring only if the public land mobile network (PLMN) is in a stored list of logged MDT PLMNs. In other embodiments of this embodiment, the communication device 600 logs the cell identifier of the cell whose MIB indicated the barring only without considering the PLMN information.
  • PLMN public land mobile network
  • the communication device 600 also includes the identifier of the cell whose SIB(s) indicated the barring.
  • the communication device 600 also includes the identifier of the cell:
  • the cell is a standalone non-public network (SNPN) cell and the communication device 600 is not an SNPN communication device
  • the configuration policy transmitted from a network node of a network consists of the below embodiments:
  • the network configures the communication device 600 with periodical logged measurements configuration including while in “camped on any cell” state.
  • the communication device 600 is configured to log information when the communication device 600 is in the "camped on any cell” state.
  • the network configures the communication device 600 with event triggered logged measurement configurations where the event encompasses the period while the communication device 600 is in out of coverage as per current standard.
  • the configuration stipulates:
  • the network configures the communication device with triggered logged measurement configurations where the event encompasses the period while the communication device 600 is in “camped on any cell” state.
  • the communication device 600 logs information when the communication device is in the "camped on any cell” state.
  • the communication device may be any of the communication device 600, wireless device 1712A, 1712B, wired or wireless devices UE 1712C, UE 1712D, UE 1800, virtualization hardware 2104, virtual machines 2108A, 2108B, or UE 2206
  • the communication device 600 shall be used to describe the functionality of the operations of the communication device.
  • Operations of the communication device 600 (implemented using the structure of the block diagram of Figure 6) will now be discussed with reference to the flow charts of Figures 10-15 according to some embodiments of inventive concepts.
  • modules may be stored in memory 605 of Figure 6, and these modules may provide instructions so that when the instructions of a module are executed by respective communication device processing circuitry 603, processing circuitry 603 performs respective operations of the flow chart.
  • Figure 10 illustrates operations the communication device 600 performs in various embodiments of inventive concepts.
  • the processing circuitry 603 in block 1001 while being in an any cell selection state or a camped on any cell state: logs at least one of: a first set of information while in the camped on any cell state as a report; and a second set of information while in the any cell selection state, the second set of information being different from the first set of information and including a reason for the communication device being in the any cell selection state, the second set of information added to the report.
  • the processing circuitry 603 transmits, via transceiver 601, the report towards a network node.
  • the communication device 600 is configured by a network via a network node.
  • Figures 11-13 illustrate various embodiments of inventive concepts of the communication device 600 being configured.
  • the processing circuitry 603 receives a first configuration that configures the communication device 600 with a periodical logged measurements configuration for including the first set of information while in the camped on any cell state.
  • the processing circuitry 603 logs the first set of information when in the camped on any cell state.
  • the processing circuitry 603 periodically logs measurements including the first set of information while in the camped on any cell state.
  • the processing circuitry 603 in block 1201 receives a second configuration that configures the communication device with a periodical logged measurements configuration for including the second set of information while in the any cell selection state.
  • the processing circuitry 603 logs the second set of information when in the any cell selection state.
  • the processing circuitry 603 periodically logs measurements including the second set of information while in the any cell selection state.
  • the processing circuitry in block 1301 receives a configuration that configures the communication device 600 with event triggered logged measurement configurations where the event encompasses the period while the communication device 600 is in out of coverage wherein the event triggered logged measurement configurations configure the communication device 600 to log at least one of: the first set of information when the communication device 600 is in the camped on any cell state; and the second set of information when the communication device 600 is in the any cell selection state.
  • Figure 14 illustrates various embodiments of information in the first set of information that is logged by the processing circuitry 603.
  • the processing circuitry 603 logs an emergency indication indicating whether the communication device 600 had any emergency calls while being in the camped on any cell state.
  • the processing circuitry 603 logs a tsunami/earthquake indication indicating whether the communication device 600 received any tsunami warning or earthquake warning while being in the camped on any cell state.
  • the processing circuitry 603 logs a total duration for which the communication device 600 was in the camped on any cell state.
  • the processing circuitry 603 logs a cell identifier of a cell the communication device 600 is in while being in the camped on any cell state with an indication that a current state is the camped on any cell state.
  • the processing circuitry 603 logs the cell identifier responsive to a public land mobile network, PLMN, on which the communication device is on is in a stored list of logged minimization of drive test, MDT, PLMNs.
  • the processing circuitry 603 logs the cell identifier (regardless of whether the PLMN on which the communication device 600 is on is in the stored list of logged MDT PLMNs).
  • the processing circuitry 603 logs a last suitable cell that the communication device 600 was camping on in a camped normally state before entering the any cell selection state from which the communication device 600 transitioned to the camped on any cell state. In some of the embodiments of logging the last suitable cell, the processing circuitry 603 logs a cell identifier (of the last suitable cell) responsive to a PLMN on which the communication device 600 is on is in a stored list of logged MDT PLMNs.
  • the processing circuitry 603 logs the cell identifier (regardless of whether the PLMN on which the communication device 600 is on is in the stored list of logged MDT PLMNs).
  • the processing circuitry 603 logs a first suitable cell that the communication device 600 is going to a camped normally state upon leaving the camped on any cell state. In some of the embodiments of logging the first suitable cell, the processing circuitry 603 logs a cell identifier (of the first suitable cell) responsive to a PLMN on which the communication device 600 is on is in a stored list of logged MDT PLMNs. In other embodiments of logging the cell identifier (of the last suitable cell), the processing circuitry 603 logs the cell identifier (regardless of whether the PLMN on which the communication device 600 is on is in the stored list of logged MDT PLMNs).
  • Figure 15 illustrates various embodiments of inventive concepts of logging the second set of information.
  • the processing circuitry 603 logs a reason for the communication device 600 for being in the any cell selection state.
  • the processing circuitry 603 logs that the communication device 600 did not find any cell that fulfills a cell selection quality criterion. In some of the embodiments of logging that the communication device 600 did not find any cell, the processing circuitry 603 logs a cell identifier of the cell that was deemed to not fulfill the cell selection quality criterion responsive to a PLMN on which the communication device 600 is on is in a stored list of logged MDT PLMNs.
  • the processing circuitry 603 logs the cell identifier of the cell that was deemed to not fulfill the cell selection quality criterion (regardless of whether the PLMN on which the communication device 600 is on is in the stored list of logged MDT PLMNs).
  • the processing circuitry 603 logs that the communication device 600 found a cell that fulfills a cell selection quality criterion but the cell was barred.
  • barred information was broadcast in a master information block, MIB).
  • the processing circuitry 603 logs a cell identifier of the cell whose MIB indicated the barring responsive to a PLMN on which the communication device 600 is on is in a stored list of logged MDT PLMNs. In other embodiments of logging the cell identifier of the cell whose MIB indicated the barring, the processing circuitry 603 logs the cell identifier of the cell whose MIB indicated the barring (regardless of whether the PLMN on which the communication device 600 is on is in the stored list of logged MDT PLMNs).
  • barred information was broadcast in a system information block, SIB.
  • the processing circuitry 603 in logging the reason includes logging a cell identifier of the cell whose SIB indicated the barring responsive to at least one of:
  • NPNs NPNs
  • the cell being barred is a standalone NPN, SNPN, cell and the communication device 600 is not an SNPN communication device
  • the network node may be any of the RAN node 700, network node 1710A, 1710B, 1900, 2206, hardware 2104, or virtual machine 2108A, 2108B
  • the RAN node 700 shall be used to describe the functionality of the operations of the network node.
  • Operations of the RAN node 700 (implemented using the structure of Figure7) will now be discussed with reference to the flow chart of Figure 16 according to some embodiments of inventive concepts.
  • modules may be stored in memory 705 of Figure 7, and these modules may provide instructions so that when the instructions of a module are executed by respective RAN node processing circuitry 703, processing circuitry 703 performs respective operations of the flow chart.
  • Figure 16 illustrates operations the RAN node 700 performs in various embodiments of inventive concepts.
  • the processing circuitry 703 in block 1601 transmits at least one of: a first configuration that configures the communication device 600 with a periodical logged measurements configuration including a first set of information while in a camped on any cell state; and a second configuration that configures the communication device 600 with a periodical logged measurements configuration including a second set of information while in the any cell selection state.
  • the processing circuitry 703 receives a report having at least one of: the first set of information when the communication device 600 was in the camped on any cell state and the second set of information when the communication device 600 was in the any cell selection state.
  • the first set of information includes one or more of an identifier of a cell the communication device while the communication device was in camped on any cell state and explicitly includes an indication that the current state is camped on any cell state; a log of a first suitable cell where the communication device is going to a camped normally state upon leaving the camped on any cell state; a log of a last suitable cell that the communication device was camping on in a camped normally state before entering the any cell selection state from which the communication device transitioned to the camped on any cell state; an emergency indication indicating whether the communication device had any emergency calls while being in the camped on any cell state; a tsunami/earthquake indication indicating whether the communication device received any tsunami warning or earthquake warning while being in the camped on any cell state; and/or a total duration for which the communication device was in the camped on any cell state.
  • the second set of information includes one or more of the identifiers, logs, indications, and total duration in the
  • the second set of information includes a reason for the communication device 600 being in an any cell selection state.
  • the reason for the communication device 600 being in the any cell selection state includes at least one of: the communication device did not find any cell that fulfills a cell selection quality criterion; and the cell selection quality criterion was fulfilled but the cell was barred.
  • Figure 17 shows an example of a communication system 1700 in accordance with some embodiments.
  • the communication system 1700 includes a telecommunication network 1702 that includes an access network 1704, such as a radio access network (RAN), and a core network 1706, which includes one or more core network nodes 1708.
  • the access network 1704 includes one or more access network nodes, such as network nodes 1710a and 1710b (one or more of which may be generally referred to as network nodes 1710), or any other similar 3 rd Generation Partnership Project (3GPP) access node or non-3GPP access point.
  • 3GPP 3 rd Generation Partnership Project
  • the network nodes 1710 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 1712a, 1712b, 1712c, and 1712d (one or more of which may be generally referred to as UEs 1712) to the core network 1706 over one or more wireless connections.
  • UE user equipment
  • 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.
  • the communication system 1700 may include any number of wired or wireless networks, network nodes, communication devices 600 (e.g., UEs), and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.
  • the communication system 1700 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.
  • the UEs 1712 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and/or operable to communicate wirelessly with the network nodes 1710 and other communication devices.
  • the network nodes 1710 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 1712 and/or with other network nodes or equipment in the telecommunication network 1702 to enable and/or provide network access, such as wireless network access, and/or to perform other functions, such as administration in the telecommunication network 1702.
  • the core network 1706 connects the network nodes 1710 to one or more hosts, such as host 1716. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts.
  • the core network 1706 includes one more core network nodes (e.g., core network node 1708) 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 1708.
  • 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 (SIDE), 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
  • SIDE Subscription Identifier De-concealing function
  • UDM Unified Data Management
  • SEPP Security Edge Protection Proxy
  • NEF Network Exposure Function
  • UPF User Plane Function
  • the host 1716 may be under the ownership or control of a service provider other than an operator or provider of the access network 1704 and/or the telecommunication network 1702, and may be operated by the service provider or on behalf of the service provider.
  • the host 1716 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.
  • the communication system 1700 of Figure 17 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
  • the telecommunication network 1702 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 1702 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 1702. For example, the telecommunications network 1702 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.
  • URLLC Ultra Reliable Low Latency Communication
  • eMBB Enhanced Mobile Broadband
  • mMTC Massive Machine Type Communication
  • the UEs 1712 are configured to transmit and/or receive information without direct human interaction.
  • a UE may be designed to transmit information to the access network 1704 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 1704.
  • 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
  • the hub 1714 communicates with the access network 1704 to facilitate indirect communication between one or more UEs (e.g., UE 1712c and/or 1712d) and network nodes (e.g., network node 1710b).
  • the hub 1714 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs.
  • the hub 1714 may be a broadband router enabling access to the core network 1706 for the UEs.
  • the hub 1714 may be a controller that sends commands or instructions to one or more actuators in the UEs.
  • the hub 1714 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.
  • the hub 1714 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 1714 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 1714 then provides to the UE either directly, after performing local processing, and/or after adding additional local content.
  • the hub 1714 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.
  • the hub 1714 may have a constant/persistent or intermittent connection to the network node 1710b.
  • the hub 1714 may also allow for a different communication scheme and/or schedule between the hub 1714 and UEs (e.g., UE 1712c and/or 1712d), and between the hub 1714 and the core network 1706.
  • the hub 1714 is connected to the core network 1706 and/or one or more UEs via a wired connection.
  • the hub 1714 may be configured to connect to an M2M service provider over the access network 1704 and/or to another UE over a direct connection.
  • UEs may establish a wireless connection with the network nodes 1710 while still connected via the hub 1714 via a wired or wireless connection.
  • the hub 1714 may be a dedicated hub - that is, a hub whose primary function is to route communications to/from the UEs from/to the network node 1710b.
  • the hub 1714 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 1710b, but which is additionally capable of operating as a communication start and/or end point for certain data channels.
  • FIG. 18 shows a UE 1800 in accordance with some embodiments.
  • a UE refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other UEs.
  • 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.
  • VoIP voice over IP
  • LME laptop-embedded equipment
  • LME laptop-mounted equipment
  • CPE wireless customer-premise equipment
  • UEs identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.
  • 3GPP 3rd Generation Partnership Project
  • 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 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).
  • the UE 1800 includes processing circuitry 1802 that is operatively coupled via a bus 1804 to an input/output interface 1806, a power source 1808, a memory 1810, a communication interface 1812, and/or any other component, or any combination thereof.
  • Certain UEs may utilize all or a subset of the components shown in Figure 18. 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.
  • the processing circuitry 1802 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 1810.
  • the processing circuitry 1802 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.
  • the processing circuitry 1802 may include multiple central processing units (CPUs).
  • the input/output interface 1806 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 the UE 1800.
  • 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
  • the power source 1808 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.
  • the power source 1808 may further include power circuitry for delivering power from the power source 1808 itself, and/or an external power source, to the various parts of the UE 1800 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 1808.
  • Power circuitry may perform any formatting, converting, or other modification to the power from the power source 1808 to make the power suitable for the respective components of the UE 1800 to which power is supplied.
  • the memory 1810 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 readonly memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth.
  • the memory 1810 includes one or more application programs 1814, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 1816.
  • the memory 1810 may store, for use by the UE 1800, any of a variety of various operating systems or combinations of operating systems.
  • the memory 1810 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.’
  • eUICC embedded UICC
  • iUICC integrated UICC
  • SIM card removable UICC commonly known as ‘SIM card.’
  • the memory 1810 may allow the UE 1800 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 the memory 1810, which may be or comprise a device-readable storage medium.
  • the processing circuitry 1802 may be configured to communicate with an access network or other network using the communication interface 1812.
  • the communication interface 1812 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 1822.
  • the communication interface 1812 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 a transmitter 1818 and/or a receiver 1820 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth).
  • the transmitter 1818 and receiver 1820 may be coupled to one or more antennas (e.g., antenna 1822) and may share circuit components, software or firmware, or alternatively be implemented separately.
  • communication functions of the communication interface 1812 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.
  • GPS global positioning system
  • 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 1812, 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., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).
  • 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-
  • AR Augmented Reality
  • VR
  • 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 3GPP 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.
  • FIG 19 shows a network node 1900 in accordance with some embodiments.
  • network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a UE and/or with other network nodes or equipment, in a telecommunication network.
  • network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)).
  • APs access points
  • BSs base stations
  • Node Bs Node Bs
  • eNBs evolved Node Bs
  • gNBs NR NodeBs
  • 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)
  • the network node 1900 includes a processing circuitry 1902, a memory 1904, a communication interface 1906, and a power source 1908.
  • the network node 1900 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.
  • the network node 1900 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.
  • the network node 1900 may be configured to support multiple radio access technologies (RATs).
  • RATs radio access technologies
  • some components may be duplicated (e.g., separate memory 1904 for different RATs) and some components may be reused (e.g., a same antenna 1910 may be shared by different RATs).
  • the network node 1900 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1900, 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 1900.
  • RFID Radio Frequency Identification
  • the processing circuitry 1902 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 1900 components, such as the memory 1904, to provide network node 1900 functionality.
  • the processing circuitry 1902 includes a system on a chip (SOC).
  • the processing circuitry 1902 includes one or more of radio frequency (RF) transceiver circuitry 1912 and baseband processing circuitry 1914.
  • the radio frequency (RF) transceiver circuitry 1912 and the baseband processing circuitry 1914 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 1912 and baseband processing circuitry 1914 may be on the same chip or set of chips, boards, or units.
  • the memory 1904 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 the processing circuitry 1902.
  • 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
  • the memory 1904 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and/or other instructions capable of being executed by the processing circuitry 1902 and utilized by the network node 1900.
  • the memory 1904 may be used to store any calculations made by the processing circuitry 1902 and/or any data received via the communication interface 1906.
  • the processing circuitry 1902 and memory 1904 is integrated.
  • the communication interface 1906 is used in wired or wireless communication of signaling and/or data between a network node, access network, and/or UE. As illustrated, the communication interface 1906 comprises port(s)/terminal(s) 1916 to send and receive data, for example to and from a network over a wired connection.
  • the communication interface 1906 also includes radio front-end circuitry 1918 that may be coupled to, or in certain embodiments a part of, the antenna 1910.
  • Radio front-end circuitry 1918 comprises filters 1920 and amplifiers 1922.
  • the radio front-end circuitry 1918 may be connected to an antenna 1910 and processing circuitry 1902.
  • the radio front-end circuitry may be configured to condition signals communicated between antenna 1910 and processing circuitry 1902.
  • the radio front-end circuitry 1918 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection.
  • the radio front-end circuitry 1918 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1920 and/or amplifiers 1922.
  • the radio signal may then be transmitted via the antenna 1910.
  • the antenna 1910 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1918.
  • the digital data may be passed to the processing circuitry 1902.
  • the communication interface may comprise different components and/or different combinations of components.
  • the network node 1900 does not include separate radio front-end circuitry 1918, instead, the processing circuitry 1902 includes radio front-end circuitry and is connected to the antenna 1910.
  • the processing circuitry 1902 includes radio front-end circuitry and is connected to the antenna 1910.
  • all or some of the RF transceiver circuitry 1912 is part of the communication interface 1906.
  • the communication interface 1906 includes one or more ports or terminals 1916, the radio front-end circuitry 1918, and the RF transceiver circuitry 1912, as part of a radio unit (not shown), and the communication interface 1906 communicates with the baseband processing circuitry 1914, which is part of a digital unit (not shown).
  • the antenna 1910 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals.
  • the antenna 1910 may be coupled to the radio front-end circuitry 1918 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly.
  • the antenna 1910 is separate from the network node 1900 and connectable to the network node 1900 through an interface or port.
  • the antenna 1910, communication interface 1906, and/or the processing circuitry 1902 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, the antenna 1910, the communication interface 1906, and/or the processing circuitry 1902 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.
  • the power source 1908 provides power to the various components of network node 1900 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component).
  • the power source 1908 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 1900 with power for performing the functionality described herein.
  • the network node 1900 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 1908.
  • the power source 1908 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 the network node 1900 may include additional components beyond those shown in Figure 19 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.
  • the network node 1900 may include user interface equipment to allow input of information into the network node 1900 and to allow output of information from the network node 1900. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1900.
  • FIG 20 is a block diagram of a host 2000, which may be an embodiment of the host 1716 of Figure 17, in accordance with various aspects described herein.
  • the host 2000 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.
  • the host 2000 may provide one or more services to one or more UEs.
  • the host 2000 includes processing circuitry 2002 that is operatively coupled via a bus 2004 to an input/output interface 2006, a network interface 2008, a power source 2010, and a memory 2012.
  • 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 18 and 19, such that the descriptions thereof are generally applicable to the corresponding components of host 2000.
  • the memory 2012 may include one or more computer programs including one or more host application programs 2014 and data 2016, which may include user data, e.g., data generated by a UE for the host 2000 or data generated by the host 2000 for a UE.
  • Embodiments of the host 2000 may utilize only a subset or all of the components shown.
  • the host application programs 2014 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).
  • the host application programs 2014 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.
  • the host 2000 may select and/or indicate a different host for over-the-top services for a UE.
  • the host application programs 2014 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. 21 is a block diagram illustrating a virtualization environment 2100 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 2100 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 virtual node does not require radio connectivity (e.g., a core network node or host)
  • the node may be entirely virtualized.
  • Applications 2102 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.
  • Hardware 2104 includes processing circuitry, memory that stores software and/or instructions executable by hardware processing circuitry, and/or other hardware devices as described herein, such as a network interface, input/output interface, and so forth.
  • Software may be executed by the processing circuitry to instantiate one or more virtualization layers 2106 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 2108a and 2108b (one or more of which may be generally referred to as VMs 2108), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein.
  • the virtualization layer 2106 may present a virtual operating platform that appears like networking hardware to the VMs 2108.
  • the VMs 2108 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 2106.
  • a virtualization layer 2106 Different embodiments of the instance of a virtual appliance 2102 may be implemented on one or more of VMs 2108, 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 network function virtualization
  • 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.
  • a VM 2108 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine.
  • Each of the VMs 2108, and that part of hardware 2104 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 2108 on top of the hardware 2104 and corresponds to the application 2102.
  • Hardware 2104 may be implemented in a standalone network node with generic or specific components. Hardware 2104 may implement some functions via virtualization.
  • hardware 2104 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 2110, which, among others, oversees lifecycle management of applications 2102.
  • hardware 2104 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 2112 which may alternatively be used for communication between hardware nodes and radio units.
  • Figure 22 shows a communication diagram of a host 2202 communicating via a network node 2204 with a UE 2206 over a partially wireless connection in accordance with some embodiments.
  • host 2202 Like host 2000, embodiments of host 2202 include hardware, such as a communication interface, processing circuitry, and memory.
  • the host 2202 also includes software, which is stored in or accessible by the host 2202 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 the UE 2206 connecting via an over-the-top (OTT) connection 2250 extending between the UE 2206 and host 2202. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection 2250.
  • OTT over-the-top
  • the network node 2204 includes hardware enabling it to communicate with the host 2202 and UE 2206.
  • connection 2260 may be direct or pass through a core network (like core network 1706 of Figure 17) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks.
  • a core network like core network 1706 of Figure 17
  • intermediate networks such as one or more public, private, or hosted networks.
  • an intermediate network may be a backbone network or the Internet.
  • the UE 2206 includes hardware and software, which is stored in or accessible by UE 2206 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 2206 with the support of the host 2202.
  • 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 2206 with the support of the host 2202.
  • an executing host application may communicate with the executing client application via the OTT connection 2250 terminating at the UE 2206 and host 2202.
  • 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.
  • the OTT connection 2250 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 the OTT
  • the OTT connection 2250 may extend via a connection 2260 between the host 2202 and the network node 2204 and via a wireless connection 2270 between the network node 2204 and the UE 2206 to provide the connection between the host 2202 and the UE 2206.
  • the connection 2260 and wireless connection 2270, over which the OTT connection 2250 may be provided, have been drawn abstractly to illustrate the communication between the host 2202 and the UE 2206 via the network node 2204, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • the host 2202 provides user data, which may be performed by executing a host application.
  • the user data is associated with a particular human user interacting with the UE 2206.
  • the user data is associated with a UE 2206 that shares data with the host 2202 without explicit human interaction.
  • the host 2202 initiates a transmission carrying the user data towards the UE 2206.
  • the host 2202 may initiate the transmission responsive to a request transmitted by the UE 2206.
  • the request may be caused by human interaction with the UE 2206 or by operation of the client application executing on the UE 2206.
  • the transmission may pass via the network node 2204, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 2212, the network node 2204 transmits to the UE 2206 the user data that was carried in the transmission that the host 2202 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 2214, the UE 2206 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 2206 associated with the host application executed by the host 2202.
  • the UE 2206 executes a client application which provides user data to the host 2202.
  • the user data may be provided in reaction or response to the data received from the host 2202.
  • the UE 2206 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 the UE 2206. Regardless of the specific manner in which the user data was provided, the UE 2206 initiates, in step 2218, transmission of the user data towards the host 2202 via the network node 2204.
  • the network node 2204 receives user data from the UE 2206 and initiates transmission of the received user data towards the host 2202.
  • the host 2202 receives the user data carried in the transmission initiated by the UE 2206.
  • factory status information may be collected and analyzed by the host 2202.
  • the host 2202 may process audio and video data which may have been retrieved from a UE for use in creating maps.
  • the host 2202 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights).
  • the host 2202 may store surveillance video uploaded by a UE.
  • the host 2202 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs.
  • the host 2202 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 the host 2202 and/or UE 2206.
  • sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 2250 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 the OTT connection 2250 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 2204. 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 the host 2202.
  • the measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 2250 while monitoring propagation times, errors, etc.
  • computing devices described herein may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • processing circuitry may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components.
  • a communication interface may be configured to include any of the components described herein, and/or the functionality of the components may be partitioned between the processing circuitry and the communication interface.
  • non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.
  • processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer- readable storage medium.
  • some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner.
  • the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and/or by end users and a wireless network generally.
  • the terms “comprise”, “comprising”, “comprises”, “include”, “including”, “includes”, “have”, “has”, “having”, or variants thereof are open-ended, and include one or more stated features, integers, elements, steps, components or functions but does not preclude the presence or addition of one or more other features, integers, elements, steps, components, functions or groups thereof.
  • the common abbreviation “e.g.”, which derives from the Latin phrase “exempli gratia” may be used to introduce or specify a general example or examples of a previously mentioned item, and is not intended to be limiting of such item.
  • the common abbreviation “i.e.”, which derives from the Latin phrase “id est,” may be used to specify a particular item from a more general recitation.
  • Example embodiments are described herein with reference to block diagrams and/or flowchart illustrations of computer-implemented methods, apparatus (systems and/or devices) and/or computer program products. It is understood that a block of the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations, can be implemented by computer program instructions that are performed by one or more computer circuits.
  • These computer program instructions may be provided to a processor circuit of a general purpose computer circuit, special purpose computer circuit, and/or other programmable data processing circuit to produce a machine, such that the instructions, which execute via the processor of the computer and/or other programmable data processing apparatus, transform and control transistors, values stored in memory locations, and other hardware components within such circuitry to implement the functions/acts specified in the block diagrams and/or flowchart block or blocks, and thereby create means (functionality) and/or structure for implementing the functions/acts specified in the block diagrams and/or flowchart block(s).
  • a method performed by a communication device (600, 1712A, 1712B, 1712C, 1712D, 1800, 2104, 2108A, 2108B, 2206), the method comprising: logging (1001) at least one of: a first set of information while in a camped on an any cell state as a report; and a second set of information while in an any cell selection state, the second set of information being different from the first set of information and including a reason for the communication device being in the any cell selection state, the second set of information added to the report; and transmitting (1003) the report towards a network node.
  • Embodiment 2 further comprising: receiving (1101) a first configuration that configures the communication device with a periodical logged measurements configuration for including the first set of information while in the camped on any cell state; and logging (1103) the first set of information when in the camped on any cell state.
  • Embodiment 4 further comprising: receiving (1301) a configuration that configures the communication device with event triggered logged measurement configurations where the event encompasses the period while the communication device is in out of coverage wherein the event triggered logged measurement configurations configure the communication device to log at least one of: the first set of information when the communication device is in the camped on any cell state; and the second set of information when the communication device is in the any cell selection state.
  • logging the first set of information comprises: logging (1401) an emergency indication indicating whether the communication device had any emergency calls while being in the camped on any cell state.
  • logging the first set of information comprises: logging (1403) a tsunami/earthquake indication indicating whether the communication device received any tsunami warning or earthquake warning while being in the camped on any cell state.
  • logging the first set of information comprises: logging (1405) a total duration for which the communication device was in the camped on any cell state.
  • logging the first set of information comprises: logging (1407) a cell identifier of a cell the communication device is in while being in the camped on any cell state with an indication that a current state is the camped on any cell state.
  • logging the last cell identifier comprises logging the cell identifier responsive to a public land mobile network, PLMN, on which the communication device is on is in a stored list of logged minimization of drive test, MDT, PLMNs.
  • logging the first set of information comprises: logging (1409) a last suitable cell that the communication device was camping on in a camped normally state before entering the any cell selection state from which the communication device transitioned to the camped on any cell state.
  • logging the last suitable cell comprises logging a cell identifier of the last suitable cell responsive to a public land mobile network, PLMN, on which the communication device is on is in a stored list of logged minimization of drive test, MDT, PLMNs. 12. The method of Embodiment 10 wherein logging the last suitable cell comprises logging a cell identifier of the last suitable cell.
  • logging the first set of information comprises: logging (1411) a first suitable cell where the communication device is going to a camped normally state upon leaving the camped on any cell state.
  • logging the first suitable cell comprises logging a cell identifier responsive to a public land mobile network, PLMN, on which the communication device is on is in a stored list of logged minimization of drive test, MDT, PLMNs.
  • Embodiment 13 The method of Embodiment 13 wherein logging the first suitable cell comprises logging a cell identifier of the first suitable cell.
  • logging the second set of information comprises logging (1501) a reason for the communication device for being in the any cell selection state.
  • Embodiment 14 wherein logging the reason comprises logging (1503) that the communication device did not find any cell that fulfills a cell selection quality criterion.
  • logging the reason further comprises logging a cell identifier of the cell that was deemed to not fulfill the cell selection quality criterion responsive to a public land mobile network, PLMN, on which the communication device is on is in a stored list of logged minimization of drive test, MDT, PLMNs.
  • logging the reason further comprises logging a cell identifier of the cell that was deemed to not fulfil the cell selection quality criterion.
  • logging the reason comprises logging (1505) that the communication device found a cell that fulfills a cell selection quality criterion but the cell was barred.
  • Embodiment 18 wherein barred information was broadcast in a master information block, MIB, and logging the reason further comprises logging a cell identifier of the cell whose MIB indicated the barring responsive to a public land mobile network, PLMN, on which the communication device is on is in a stored list of logged minimization of drive test, MDT, PLMNs.
  • Embodiment 18 wherein barred information was broadcast in a master information block, MIB, and logging the reason further comprises logging a cell identifier of the cell whose MIB indicated the barring.
  • Embodiment 21 The method of Embodiment 18 wherein barred information was broadcast in a system information block, SIB, and logging the reason further comprises logging a cell identifier of the cell whose SIB indicated the barring responsive to at least one of: the cell being barred for multiple public land mobile networks or multiple non-public networks, NPNs the cell being barred is a standalone NPN, SNPN cell and the communication device is not an SNPN communication device the cell being barred is reserved for operator use; or the cell being barred is reserved for future use.
  • SIB system information block
  • a method performed by a network node (700, 1710A, 1710B, 1900, 2104, 2108A, 2108B, 2204), the method comprising: transmitting (1601) at least one of: a first configuration that configures the communication device with a periodical logged measurements configuration including a first set of information while in a camped on any cell state; and a second configuration that configures the communication device with a periodical logged measurements configuration including a second set of information while in the any cell selection state; and receiving (1603) a report having logged at least one of: the first set of information when the communication device was in the camped on any cell state; and the second set of information when the communication device was in the any cell selection state.
  • the first set of information and the second set of information comprises one or more of: an identifier of a cell the communication device while the communication device was in camped on any cell state and explicitly includes an indication that the current state is camped on any cell state; a log of a first suitable cell where the communication device is going to a camped normally state upon leaving the camped on any cell state; a log of a last suitable cell that the communication device was camping on in a camped normally state before entering the any cell selection state from which the communication device transitioned to the camped on any cell state; an emergency indication indicating whether the communication device had any emergency calls while being in the camped on any cell state; a tsunami/earthquake indication indicating whether the communication device received any tsunami warning or earthquake warning while being in the camped on any cell state; and/or a total duration for which the communication device was in the camped on any cell state.
  • Embodiment 24 The method of Embodiment 23 wherein the second set of information further comprises a reason for the communication device being in any cell selection state.
  • a communication device (600, 1712A, 1712B, 1712C, 1712D, 1800, 2104, 2108A, 2108B, 2206) adapted to: log (1001) at least one of: a first set of information while in a camped on any cell state as a report; and a second set of information while in an any cell selection state, the second set of information being different from the first set of information and including a reason for the communication device being in the any cell selection state, the second set of information added to the report; and transmit (1003) the report towards a network node.
  • a communication device (600, 1712A, 1712B, 1712C, 1712D, 1800, 2104, 2108A, 2108B, 2206) comprising: processing circuitry (603, 1802, 2112); and memory (605, 1810) coupled with the processing circuitry, wherein the memory includes instructions that when executed by the processing circuitry causes the communication device to: log (1010) at least one of: a first set of information while in a camped on any cell state as a report; and a second set of information while in an any cell selection state, the second set of information being different from the first set of information and including a reason for the communication device being in the any cell selection state, the second set of information added to the report; and transmit (1003) the report towards a network node.
  • a computer program comprising program code to be executed by processing circuitry (603, 1802, 2112) of a communication device (600, 1712A, 1712B, 1712C, 1712D, 1800, 2104, 2108A, 2108B, 2206), whereby execution of the program code causes the communication device (600, 1712A, 1712B, 1712C, 1712D, 1800, 2104, 2108A, 2108B, 2206) to: log (1001) at least one of: a first set of information while in a camped on any cell state as a report; and a second set of information while in an any cell selection state, the second set of information being different from the first set of information and including a reason for the communication device being in the any cell selection state, the second set of information added to the report; and transmit (1003) the report towards a network node.
  • a computer program product comprising a non-transitory storage medium including program code to be executed by processing circuitry (603, 1802, 2112) of a communication device (600, 1712A, 1712B, 1712C, 1712D, 1800, 2104, 2108A, 2108B, 2206), whereby execution of the program code causes the communication device (200, 1712A, 1712B, 1712C, 1712D, 1800, 2104, 2108A, 2108B, 2206) to: log (1001) at least one of: a first set of information while in a camped on any cell state as a report; and a second set of information while in an any cell selection state, the second set of information being different from the first set of information and including a reason for the communication device being in the any cell selection state, the second set of information added to the report; and transmit (1003) the
  • a network node (700, 1710A, 1710B, 1900, 2104, 2108A, 2108B, 2204) adapted to: transmit (1601) at least one of: a first configuration that configures the communication device with a periodical logged measurements configuration including a first set of information while in a camped on any cell state; and a second configuration that configures the communication device with a periodical logged measurements configuration including a second set of information while in the any cell selection state; and receive (1603) a report having logged at least one of: the first set of information when the communication device was in the camped on any cell state; and the second set of information when the communication device was in the any cell selection state.
  • a network node (700, 1710A, 1710B, 1900, 2104, 2108A, 2108B, 2204) comprising: processing circuitry (703, 1802, 2112); and memory (705, 1810) coupled with the processing circuitry, wherein the memory includes instructions that when executed by the processing circuitry causes the network node to: transmit (1601) at least one of: a first configuration that configures the communication device with a periodical logged measurements configuration including a first set of information while in a camped on any cell state; and a second configuration that configures the communication device with a periodical logged measurements configuration including a second set of information while in the any cell selection state; and receive (1603) a report having logged at least one of: the first set of information when the communication device was in the camped on any cell state; and the second set of information when the communication device was in the any cell selection state.
  • a computer program comprising program code to be executed by processing circuitry (703, 1902) of a radio access network, RAN, node (700, 1710A, 1710B, 1900, 2104, 2108A, 2108B, 2204), whereby execution of the program code causes the RAN node (700, 1710A, 1710B, 1900, 2104, 2108A, 2108B, 2204) to: transmit (1601) at least one of: a first configuration that configures the communication device with a periodical logged measurements configuration including a first set of information while in a camped on any cell state; and a second configuration that configures the communication device with a periodical logged measurements configuration including a second set of information while in the any cell selection state; and receive (1603) a report having logged at least one of: the first set of information when the communication device was in the camped on any cell state; and the second set of information when the communication device was in the any cell selection state.
  • Embodiment 38 comprising further program code whereby execution of the further program code causes the network node to perform according to any of Embodiments 23-26.
  • a computer program product comprising a non-transitory storage medium including program code to be executed by processing circuitry (703, 1902) of a radio access network, RAN, node (700, 1710A, 1710B, 1900, 2104, 2108A, 2108B, 2204), whereby execution of the program code causes the RAN node (700, 1710A, 1710B, 1900, 2104, 2108A, 2108B, 2204) to: transmit (1601) at least one of: a first configuration that configures the communication device with a periodical logged measurements configuration including a first set of information while in a camped on any cell state; and a second configuration that configures the communication device with a periodical logged measurements configuration including a second set of information while in the any cell selection state; and receive (1603) a report having logged at least one of: the first set of information when the communication device was in the camped on any cell state; and the second set of information when the communication device was in the any cell selection state.
  • UE user equipment
  • RAN radio access network
  • logging the identifier of the first cell is responsive to one or more of the following conditions: the public land mobile network (PLMN) of the first cell is in a list of PLMNs included in the measurement reporting configuration or stored in the UE; and the first cell is included in or associated with an area configuration included in the measurement reporting configuration.
  • PLMN public land mobile network
  • the second information when the second information indicates that access barring was indicated in a SIB broadcast in the first cell, the second information also includes indications of one or more of the following: whether the first cell is barred for multiple networks, including public land mobile networks (PLMNs) and non-public networks (NPNs); whether the first cell is part of a standalone NPN (SNPN) and the UE is not authorized to access the SNPN (i.e., non-SNPN UE); whether the first cell is reserved for operator use; and whether the first cell is reserved for future use.
  • PLMNs public land mobile networks
  • NPNs non-public networks
  • a method for a network node in a radio access network comprising: receiving, from a user equipment (UE), a measurement report including the following first information: an identifier of a first cell in the RAN, the first cell being selected by the UE as a best cell for camping in a non-connected state according to cell reselection criteria; measurement information related to a second cell in the RAN, the second cell being selected by the UE instead of the first cell because the UE was barred from accessing the first cell; performing one or more of the following based on the measurement report: determining coverage for at least one of the first cell and the second cell; and selecting an accessing barring configuration for at least one of the first cell and the second cell.
  • a measurement report including the following first information: an identifier of a first cell in the RAN, the first cell being selected by the UE as a best cell for camping in a non-connected state according to cell reselection criteria; measurement information related to a second cell in the RAN, the second cell being selected by
  • the identifier of the first cell is included in the measurement report based on one or more of the following conditions: the public land mobile network (PLMN) of the first cell is in a list of PLMNs included in the measurement reporting configuration or stored in the UE; and the first cell is included in or associated with an area configuration included in the measurement reporting configuration.
  • PLMN public land mobile network
  • the measurement report also includes one or more of the following second information: whether the first cell is on the same or a different frequency than the second cell; and whether access barring was indicated in a master information block (MIB) broadcast in the first cell or in SI blocks (SIBs) broadcast in the first cell.
  • MIB master information block
  • SIBs SI blocks
  • the second information when the second information indicates that access barring was indicated in a SIB broadcast in the first cell, the second information also includes indications of one or more of the following: whether the first cell is barred for multiple networks, including public land mobile networks (PLMNs) and non-public networks (NPNs); whether the first cell is part of a standalone NPN (SNPN) and the UE is not authorized to access the SNPN (i.e., non-SNPN UE); whether the first cell is reserved for operator use; and whether the first cell is reserved for future use.
  • PLMNs public land mobile networks
  • NPNs non-public networks
  • a user equipment configured to operate in a radio access network (RAN), the UE comprising: communication interface circuitry configured to communicate with one or more network nodes in the RAN; 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 any of the methods of embodiments 42-49.
  • RAN radio access network
  • a user equipment configured to operate in a radio access network (RAN), the UE being further arranged to perform operations corresponding to any of the methods of embodiments 42-49.
  • RAN radio access network
  • 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 a radio access network (RAN), configure the UE to perform operations corresponding to any of the methods of embodiments 42-49.
  • UE user equipment
  • RAN radio access network
  • a computer program product comprising computer-executable instructions that, when executed by processing circuitry of a user equipment (UE) configured to operate in a radio access network (RAN), configure the UE to perform operations corresponding to any of the methods of embodiments 42-49.
  • UE user equipment
  • RAN radio access network
  • RAN radio access network
  • RAN radio access network
  • a non-transitory, computer-readable medium storing computer-executable instructions that, when executed by processing circuitry of a network node in a radio access network (RAN), configure the network node to perform operations corresponding to any of the methods of embodiments 50-57.
  • RAN radio access network
  • a computer program product comprising computer-executable instructions that, when executed by processing circuitry of a network node in a cellular radio access network (RAN), configure the network node to perform operations corresponding to any of the methods of embodiments 50-57.
  • RAN radio access network
  • E-UTRA Terrestrial Radio Access
  • MDT Radio measurement collection for Minimization of Drive Tests
  • Overall description Stage 2, version 16.5.0

Landscapes

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

Abstract

A method performed by a communication device includes while being in an any cell selection state or a camped on any cell state: logging at least one of: a first set of information while in the camped on an any cell state as a report; and a second set of information while in the any cell selection state, the second set of information being different from the first set and including a reason for t being in the any cell selection state, the second set of information added to the report. While being in a camped normally state on a cell: logging measurement information related to an evaluated best cell is logged as the report and/or responsive to a current cell not being the best cell, a reason for not camping on the best cell is logged as the report. The method includes transmitting the report towards a network node.

Description

ENHANCEMENTS OF LOGGED MDT REPORT
TECHNICAL FIELD
[0001] The present disclosure relates generally to communications, and more particularly to communication methods and related devices and nodes supporting wireless communications.
BACKGROUND
[0002] Long-Term Evolution (LTE) is an umbrella term for so-called fourth generation (4G) radio access technologies developed within the Third-Generation Partnership Project (3GPP) and initially standardized in Release 8 (Rel-8) and Release 9 (Rel-9), also known as Evolved UTRAN (E-UTRAN- evolved universal terrestrial radio access network). LTE is targeted at various licensed frequency bands and is accompanied by improvements to non-radio aspects commonly referred to as System Architecture Evolution (SAE), which includes the Evolved Packet Core (EPC) network. LTE continues to evolve through subsequent releases.
[0003] An overall exemplary architecture of a network comprising LTE and SAE is shown in Figure 1. E-UTRAN 100 includes one or more evolved Node B’s (eNB), such as eNBs 105, 110, and 115, and one or more user equipment (UE), such as UE 120. As used within the 3GPP standards, “user equipment” or “UE” means any wireless communication device (e.g., smartphone or computing device) that is capable of communicating with 3GPP- standard- compliant network equipment, including E-UTRAN as well as UTRAN and/or GER AN (GSM (global system for mobile communication) EDGE (enhanced data rates for GSM evolution) radio access network), as the third generation (“3G”) and second-generation (“2G”) 3GPP RANs are commonly known.
[0004] As specified by 3GPP, E-UTRAN 100 is responsible for all radio-related functions in the network, including radio bearer control, radio admission control, radio mobility control, scheduling, and dynamic allocation of resources to UEs in uplink and downlink, as well as security of the communications with the UE. These functions reside in the eNBs, such as eNBs 105, 110, and 115. Each of the eNBs can serve a geographic coverage area including one more cells, including cells 106, 111, and 115 served by eNBs 105, 110, and 115, respectively.
[0005] The eNBs in the E-UTRAN communicate with each other via the X2 interface, as shown in Figure 1. The eNBs also are responsible for the E-UTRAN interface to the EPC 130, specifically the SI interface to the Mobility Management Entity (MME) and the Serving Gateway (SGW), shown collectively as MME/S-GWs 134 and 138 in Figure 1. In general, the MME/S-GW handles both the overall control of the UE and data flow between the UE and the rest of the EPC. More specifically, the MME processes the signaling (e.g., control plane) protocols between the UE and the EPC, which are known as the Non-Access Stratum (NAS) protocols. The S-GW handles all Internet Protocol (IP) data packets (e.g., data or user plane) between the UE and the EPC and serves as the local mobility anchor for the data bearers when the UE moves between eNBs, such as eNBs 105, 110, and 115.
[0006] EPC 130 can also include a Home Subscriber Server (HSS) 131, which manages user- and subscriber-related information. HSS 131 can also provide support functions in mobility management, call and session setup, user authentication and access authorization. The functions of HSS 131 can be related to the functions of legacy Home Location Register (HLR) and Authentication Centre (AuC) functions or operations. HSS 131 can also communicate with MMEs 134 and 138 via respective S6a interfaces.
[0007] In some embodiments, HSS 131 can communicate with a user data repository (UDR) - labelled EPC-UDR 135 in Figure 1 - via a Ud interface. EPC-UDR 135 can store user credentials after they have been encrypted by AuC algorithms. These algorithms are not standardized (i.e., vendor- specific), such that encrypted credentials stored in EPC-UDR 135 are inaccessible by any other vendor than the vendor of HSS 131.
[0008] Figure 2 illustrates a block diagram of an exemplary control plane (CP) protocol stack between a UE, an eNB, and an MME. The exemplary protocol stack includes Physical (PHY), Medium Access Control (MAC), Radio Link Control (RLC), Packet Data Convergence Protocol (PDCP), and Radio Resource Control (RRC) layers between the UE and eNB. The PHY layer is concerned with how and what characteristics are used to transfer data over transport channels on the LTE radio interface. The MAC layer provides data transfer services on logical channels, maps logical channels to PHY transport channels, and reallocates PHY resources to support these services. The RLC layer provides error detection and/or correction, concatenation, segmentation, and reassembly, reordering of data transferred to or from the upper layers. The PDCP layer provides ciphering/deciphering and integrity protection for both CP and user plane (UP), as well as other UP functions such as header compression. The exemplary protocol stack also includes non-access stratum (NAS) signaling between the UE and the MME.
[0009] The RRC layer controls communications between a UE and an eNB at the radio interface, as well as the mobility of a UE between cells in the E-UTRAN. After a UE is powered ON it will be in the RRC DLE 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 RRC JDLE after the connection with the network is released. In RRC_ IDLE state, the UE does not belong to any cell, no RRC context has been established for the UE (e.g., in E-UTRAN), and the UE is out of UL synchronization with the network. Even so, a UE in RRCJDLE state is known in the EPC and has an assigned IP address.
[0010] Furthermore, in RRCJDLE 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 “On durations”), an RRC.. IDLE UE receives system information (SI) broadcast by a serving cell, performs measurements of neighbor cells to support cell reselection, and monitors a paging channel for pages from the EPC via an eNB serving the cell in which the UE is camping. A cell in which an RRC...IDLE UE can perform these actions and move to RRC.. CONNECTED state is often referred to as a “suitable cell”, and UE’s state when performing these actions (i.e., before moving to RRC_CONNECTED) is often referred to as “camped normally”.
[0011] A UE must perform a random-access (RA) procedure to move from RRC_IDLE to RRC_CONNECTED. In RRC_CONNECTED state, the cell serving the UE is known and an RRC context is established for the UE in the serving eNB, such that the UE and eNB can communicate. For example, a Cell Radio Network Temporary Identifier (C-RNTI) - a UE identity used for signaling between UE and network - is configured for a UE in RRC_CONNECTED state.
[0012] 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). NR is developed for maximum flexibility to support multiple and substantially different use cases but shares many similarities with fourth-generation LTE. For example, NR uses CP-OFDM (Cyclic Prefix Orthogonal Frequency Division Multiplexing) in the DL and both CP-OFDM and 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 that are further divided into slots having multiple OFDM-based symbols. In addition to RRC_IDLE and RRC_CONNECTED, the NR RRC layer also includes an RRC_INACTIVE state with properties similar to a “suspended” condition in LTE Rel-13.
[0013] Seamless mobility is a key feature of 3GPP radio access technologies (RATs). In general, a network 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 causing too many interruptions in 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 will declare radio link failure (RLF) or handover failure (HOF). Similarly, the UE may experience failure when trying to reestablish a failed connection with the network, causing the UE to declare connection establishment failure (CEF). [0014] Various UE failure reporting procedures were introduced as part of the mobility robustness optimization (MRO) in LTE Rel-9. In these procedures, UEs log relevant information at the time of failure (e.g., RLF) and later report such information to the network via target cells to which UEs ultimately connect (e.g., after reestablishment). The reported information can include RRM measurements of various neighbor cells prior to the mobility operation (e.g., handover).
[0015] In addition, UEs can be configured to perform and report measurements to support minimization of drive tests (MDT), which is intended to reduce and/or minimize the requirements for manual testing of actual network performance (i.e., by driving around the coverage area of the network).
[0016] MDT was standardized for NR in Rel-16 to reduce the amount of drive tests performed manually. MDT is a UE assisted framework where network measurements are collected by both IDLE/INACTIVE and RRC (radio resource control) Connected UE(s) in order to aid the network in gathering valuable information. MDT has been specified for both LTE and NE in 3GPP TS 37.320.
[0017] In general, there are two types of MDT measurement logging, i.e., Logged MDT and Immediate MDT.
[0018] Logged MDT
[0019] A UE in RRC_IDLE/RRC_INACTIVE state is configured to perform periodical and event triggered MDT logging after receiving the MDT configurations from the network. The UE shall report the DL (downlink) pilot strength measurements (RSRP (reference signal received power/RSRQ (reference signal received quality) together with time information, detailed location information if available, and WLAN, Bluetooth to the network via using the UE information framework when it is in RRC_CONNECTED state. The DL pilot strength measurement of Logged MDT is collected based on the existing measurements required for cell reselection purpose, without imposing UE to perform additional measurements.
[0020] Table 1 lists measurement logging for Logged MDT
Figure imgf000006_0001
Figure imgf000007_0001
Table 1 Measurement Logging for Logged MDT
[0021] For Periodical Logged MDT, UE receives the MDT configurations including logginginterval and logging duration in the RRC message, i.e., LoggedMeasurementConfiguration, from the network. A timer (T330) is started at the UE upon receiving the configurations and set to loggingduration (10 min - 120 min). The UE shall perform periodical MDT logging with the interval set to logginginterval (1.28 s - 61.44 s) when the UE is in RRC_IDLE. An example of the MDT logging is shown in Figure 3.
[0022] For event triggered Logged MDT UE receives eventType and logginginterval from the network. The UE logs the measurement reports at every logginginterval if event configured in eventType is satisfied
[0023] Camped on any cell state
[0024] In 3GPP TS 38.304, different categories of cells and state of a UE in those cells are defined. One category of cell is called accepted cell, where UEs may camp to obtain limited service (obtain Emergency Calls and receive ETWS and CMAS notification). A UE camping on an acceptable cell is defined as being in “camped on any cell state”.
[0025] Any cell selection state
[0026] If the UE cannot find a cell that belongs to suitable cell or acceptable cell, it declares itself being in an any cell selection state. Further details are available in 3GPP TS 38.304.
[0027] Cell Reservation and Access Restrictions
[0028] In NR, UE access to cells can be controlled at multiple levels; cells can be barred for all UEs or a specific group of UEs based on some network-controlled criteria. Examples include UEs having certain access identities might be allowed on cells which the operator reserves for its internal use. Details of cell reservations and UE access identities can be found in 3GPP TS 38.304 and 3GPP TS 22.261, respectively.
SUMMARY
[0029] In 3GPP it was recently proposed that UEs in “camped on any cell” state should also include some reports as part of logged MDT framework. Details of which are still not published or discussed. Furthermore, logged MDT configuration while UE is in “any cell selection” state or “camped normally” state is standardized and can be found in 3GPP TS 38.331.
[0030] In current logged MDT framework, it is standardized that UEs will log different measurement results only if it is “camped normally” state or “Any cell selection” state. Upon receiving such information, the network may interpret the result as the particular cell being the best cell for UE, i.e., in the particular environment. However, the UE has another possible state known as “camped on any cell state”, logging on which is not covered under current specifications. Furthermore, the UE can be camped normally in a cell that is suitable but not best cell due to some network barring configuration which could be optimized by network.
[0031] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges.
[0032] Various embodiments of inventive concepts provides a first set of information logged by a wireless terminal as a report while in “camped on any cell” state. The first set of information logged by the UE may or may not be dependent on a configuration policy associated to “camped on any cell” state set by the network.
[0033] In further embodiments of inventive concepts, a second set of information logged by a wireless terminal as part of the logged MDT report or as a separate logged MDT report while in the "any cell selection" state. The second set of information logged by the UE may or may not be dependent on a configuration policy associated to the "any cell selection" set by the network. [0034] According to some embodiments, a method by a communication device (e.g., a UE) includes while being in an any cell section state or a camped on any cell state: logging at least one of a first set of information while in a camped on an any cell state as a report and a second set of information while in an any cell selection state, the second set of information being different from the first set of information and including a reason for the communication device being in the any cell selection state, the second set of information added to the report. The method includes transmitting the report towards a network node.
[0035] According to these methods, in some embodiments the method further includes based on one or more cell reselection criteria, determining that a first cell in a radio access network, RAN, is a best cell for camping in a non-connected state. The method further includes based on determining that the communication device is barred from accessing the first cell, selecting a second cell for camping in the non-connected state. The method further includes that the logging further comprises logging the following first information while camping normally on the second cell: measurement information related to the second cell being camped on in the any cell state, and an identifier of the first cell as the best cell determined according to the cell reselection criteria.
[0036] Analogous communication devices, computer programs, and computer program products are provided.
[0037] According to some other embodiments, a method performed by a network node includes transmitting at least one of: a first configuration that configures the communication device with a periodical logged measurements configuration including a first set of information while in a camped on any cell state; and a second configuration that configures the communication device with a periodical logged measurements configuration including a second set of information while in the any cell selection state. The method includes receiving a report having logged at least one of: the first set of information when the communication device was in the camped on any cell state; and the second set of information when the communication device was in the any cell selection state.
[0038] According to these methods, in some embodiments the method further includes receiving, from a user equipment (UE), a measurement report including the following first information: an identifier of a first cell in the RAN, the first cell being selected by the UE as a best cell for camping in a non-connected state according to cell reselection criteria; and measurement information related to a second cell in the RAN, the second cell being selected by the UE instead of the first cell because the UE was barred from accessing the first cell. The method further includes performing one or more of the following based on the measurement report: determining coverage for at least one of the first cell and the second cell; and selecting an accessing barring configuration for at least one of the first cell and the second cell.
[0039] Analogous network nodes, computer programs, and computer program products are provided.
[0040] Certain embodiments may provide one or more of the following technical advantage(s). The various embodiments of inventive concepts enable the UE to log additional information in logged MDT report to aid the network in gaining further insight about the coverage condition and allows the network to gather information from the UEs while they are in “camped on any cell” state. The various embodiments further allow the network to gain insights about conditions when the UE is in “any cell selection” state. This information in turn allows the network to create better coverage map. The network is further enabled to understand the impact of certain configuration, e.g., impact of barring some cells and possibly optimize such configuration.
BRIEF DESCRIPTION OF THE DRAWINGS
[0041] The accompanying drawings, which are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of this application, illustrate certain non-limiting embodiments of inventive concepts. In the drawings:
[0042] Figure 1 is a high-level illustration of an exemplary LTE network architecture; [0043] Figure 2 shows an exemplary LTE control-plane (CP) protocol stack;
[0044] Figure 3 is an example of a logged MDT procedure;
[0045] Figures 4-5 show two exemplary views of a 5G network architecture;
[0046] Figure 6 is a block diagram illustrating a communication device according to some embodiments of the present disclosure;
[0047] Figure 7 is a block diagram illustrating a radio access network RAN node (e.g., a base station eNB/gNB) according to some embodiments of the present disclosure;
[0048] Figure 8 shows a flow diagram of an exemplary method (e.g., procedure) for a UE (e.g., wireless device, MTC device, NB-IoT device, modem, etc. or component thereof), according to various embodiments of the present disclosure;
[0049] Figure 9 shows a flow diagram of an exemplary method (e.g., procedure) for a network node (e.g., base station, eNB, gNB, ng-eNB, en-gNB, etc. or component thereof), according to various embodiments of the present disclosure
[0050] Figures 10-15 are flow chart illustrating operations of a communication device according to some embodiments of the present disclosure;
[0051] Figure 16 is a flow chart illustrating operations of a network node according to some embodiments of the present disclosure;
[0052] Figure 17 is a block diagram of a communication system in accordance with some embodiments;
[0053] Figure 18 is a block diagram of a user equipment in accordance with some embodiments
[0054] Figure 19 is a block diagram of a network node in accordance with some embodiments;
[0055] Figure 20 is a block diagram of a host computer communicating with a user equipment in accordance with some embodiments;
[0056] Figure 21 is a block diagram of a virtualization environment in accordance with some embodiments; and
[0057] Figure 22 is a block diagram of a host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments in accordance with some embodiments.
DETAILED DESCRIPTION
[0058] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art. , in which examples of embodiments of inventive concepts are shown. Inventive concepts may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of present inventive concepts to those skilled in the art. It should also be noted that these embodiments are not mutually exclusive. Components from one embodiment may be tacitly assumed to be present/used in another embodiment.
[0059] The following terms are used throughout the description given below:
• Radio Node: As used herein, a “radio node” can be either a “radio access node” or a “wireless device.”
• 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) of a cellular communications network that operates to wirelessly transmit and/or receive signals. Some examples of a radio access node include, but are not limited to, a base station (e.g., a New Radio (NR) base station (gNB) in a 3GPP Fifth Generation (5G) NR network or an enhanced or evolved Node B (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, 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 Packet Data Network Gateway (P-GW), an access and mobility management function (AMF), a session management function (SMF), a location management function (LMF), a user plane function (UPF), a Network Exposure Function (NEF), or the like.
• Wireless Device: As used herein, a “wireless device” (or “WD” for short) is any type of device that has access to (i.e., is served by) a cellular communications network by 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. Some examples of a wireless device include, but are not limited to, smart phones, mobile phones, cell phones, voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, gaming consoles or devices, music storage devices, playback appliances, wearable devices, wireless endpoints, mobile stations, tablets, laptops, laptop- embedded equipment (LEE), laptop-mounted equipment (LME), smart devices, wireless customer-premise equipment (CPE), mobile-type communication (MTC) devices, Internet-of-Things (loT) devices, vehicle-mounted wireless terminal devices, etc. Unless otherwise noted, the term “wireless device” is used interchangeably herein with the term “user equipment” (or “UE” for short).
• Network Node: As used herein, a “network node” is any node that is either part of the radio access network (e.g., a radio access node or equivalent name discussed above) or of the core network (e.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.
[0060] Note that the description herein focuses on a 3GPP cellular communications system and, as such, 3GPP terminology or terminology similar to 3GPP terminology is often used.
However, the concepts disclosed herein are not limited to a 3GPP system. Furthermore, although the term “cell” is used herein, it should be understood that (particularly with respect to 5G NR) beams may be used instead of cells and, as such, concepts described herein apply equally to both cells and beams.
[0061] Figure 4 illustrates a high-level view of an exemplary 5G network architecture, consisting of a Next Generation RAN (NG-RAN 499) and a 5G Core (5GC 498). NG-RAN 499 can include a set of gNodeB’s (gNBs) connected to the 5GC via one or more NG interfaces, whereas the gNBs can be connected to each other via one or more Xn interfaces, such as Xn interface 440 between gNBs 400 and 450 in Figure 4. Each of the gNBs can support frequency division duplexing (FDD), time division duplexing (TDD), or a combination thereof on the NR interface to UEs.
[0062] NG-RAN 499 is layered into a Radio Network Layer (RNL) and a Transport Network Layer (TNL). The NG-RAN architecture, i.e., 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. In some exemplary configurations, each gNB is connected to all 5GC nodes within an “AMF Region,” with the term “AMF” being discussed in more detail below.
[0063] The NG RAN logical nodes shown in Figure 4 include a central (or centralized) unit (CU or gNB-CU) and one or more distributed (or decentralized) units (DU or gNB-DU). For example, gNB 400 in Figure 4 includes gNB-CU 410 and gNB-DUs 420 and 430. CUs (e.g., gNB-CU 410) are logical nodes that host higher-layer protocols and perform various gNB functions such controlling the operation of DUs. Each DU is a logical node that hosts lower- layer protocols and can include, depending on the functional split, various subsets of the gNB functions. As such, each of the CUs and DUs can include various circuitry needed to perform their respective functions, including processing circuitry, transceiver circuitry (e.g., for communication), and power supply circuitry. Moreover, the terms “central unit” and “centralized unit” are used interchangeably herein, as are the terms “distributed unit” and “decentralized unit.”
[0064] A gNB-CU connects to its associated gNB-DUs over respective Fl logical interfaces, such as interfaces 422 and 432 shown in Figure 4. The gNB-CU and connected gNB-DUs are only visible to other gNBs and the 5GC as a gNB, e.g., the Fl interface is not visible beyond gNB-CU. In the gNB split CU-DU architecture illustrated by Figure 4, DC can be achieved by allowing a UE to connect to multiple DUs served by the same CU or by allowing a UE to connect to multiple DUs served by different CUs.
[0065] Figure 5 shows another high-level view of an exemplary 5G network architecture, including NG-RAN 599 and 5GC 598. As shown in the figure, NG-RAN 599 can include gNBs 510 (e.g., 510a, b) and ng-eNBs 520 (e.g., 520a, b) that are interconnected with each other via respective Xn interfaces. The gNBs and ng-eNBs are also connected via the NG interfaces to 5GC 598, more specifically to the AMF (Access and Mobility Management Function) 530 (e.g., AMFs 530a, b) via respective NG-C interfaces and to the UPF (User Plane Function) 540 (e.g., UPFs 540a, b) via respective NG-U interfaces. Moreover, the AMFs 530a, b can communicate with one or more policy control functions (PCFs, e.g., PCFs 550a, b) and network exposure functions (NEFs, e.g., NEFs 560a, b).
[0066] Each of the gNBs 510 can support the NR radio interface including FDD, TDD, or a combination thereof. In contrast, each of ng-eNBs 520 can support the LTE radio interface but, unlike conventional LTE eNBs (e.g., in Figure 1), connect to the 5GC via the NG interface. Each or gNB or ng-eNB can serve a geographic coverage area including one more cells, such as cells 51 la-b and 521a-b shown in Figure 5. Depending on the particular cell in which it is located, a UE 505 can communicate with the gNB or ng-eNB serving that cell via the NR or LTE radio interface, respectively. In some embodiments, UE 505 can operate in multi-connectivity (MC) with any two or more of gNBs 510a,b and ng-eNBs 520a, b via the cells served by those respective nodes.
[0067] In some embodiments, the gNBs and ng-eNBs 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.
[0068] A UE in RRC_CONNECTED state can be handed over from a serving (or source) cell to a target cell for various reasons, including mobility load balancing (MLB) for capacity purposes and radio link failure (RLF) avoidance for coverage purposes. In contrast, a UE in RRC_IDLE or RRC_INACTIVE performs cell reselection primarily for coverage purposes and these decisions are very static in nature.
[0069] In RRC_CONNECTED state, the network typically configures the UE to perform and report radio resource management (RRM) measurements to assist network-controlled mobility decisions such as handover from one cell to another. A RLF procedure is typically triggered in the UE when something unexpected happens in any of the mobility-related procedures, including handover. The RLF procedure involves interactions between RRC and lower layer protocols such as PHY (or LI), MAC, RLC, etc. including radio link monitoring (RLM) on LI.
[0070] Upon handover failure (HOF) and RLF, the UE may take autonomous actions such as trying to select a cell and initiate reestablishment procedure so that the UE can remain reachable by the network. In general, a UE declares RLF only when the UE realizes that there is no reliable communication channel (or radio link) available between itself and the network, which can result in poor user experience. Also, reestablishing the connection requires signaling with a newly selected cell (e.g., random access procedure, exchanging various RRC messages, etc.), introducing latency until the UE can again reliably transmit and/or receive user data with the network.
[0071] As previously indicated, in 3GPP it has been proposed that UEs in “camped on any cell” state should also include some reports as part of logged MDT framework, the details of which are still not published or discussed.
[0072] In the description that follows, while there may be some information that is common between the two sets of information logged by the UE that are described hereinbelow, the two sets of information are independent of each other and independent to the configuration policy of the network.
[0073] Prior to describing the two sets of information, Figure 6 is a block diagram illustrating elements of a communication device 600 (also referred to as a mobile terminal, a mobile communication terminal, a wireless device, a wireless communication device, a wireless terminal, mobile device, a wireless communication terminal, user equipment, UE, a user equipment node/terminal/device, etc.) configured to provide wireless communication according to embodiments of inventive concepts. (Communication device 600 may be provided, for example, as discussed below with respect to wireless devices UE 1712A, UE 1712B, and wired or wireless devices UE 1712C, UE 1712D of Figure 17, UE 1800 of Figure 18, virtualization hardware 2104 and virtual machines 2108A, 2108B of Figure 21, and UE 2206 of Figure 22, all of which should be considered interchangeable in the examples and embodiments described herein and be within the intended scope of this disclosure, unless otherwise noted.) As shown, communication device 600 may include an antenna 607 (e.g., corresponding to antenna 1822 of Figure 18), and transceiver circuitry 601 (also referred to as a transceiver, e.g., corresponding to interface 1812 of Figure 18 having transmitter 1818 and receiver 1820) including a transmitter and a receiver configured to provide uplink and downlink radio communications with a base station(s) (e.g., corresponding to network node 1710A, 1710B of Figure 17, network node 1900 of Figure 19, and network node 2204 of Figure 22 also referred to as a RAN node) of a radio access network. Communication device UE 600 may also include processing circuitry 603 (also referred to as a processor, e.g., corresponding to processing circuitry 1802 of Figure 18, and control system 2112 of Figure 21) coupled to the transceiver circuitry, and memory circuitry 605 (also referred to as memory, e.g., corresponding to memory 1810 of Figure 17) coupled to the processing circuitry. The memory circuitry 605 may include computer readable program code that when executed by the processing circuitry 603 causes the processing circuitry to perform operations according to embodiments disclosed herein. According to other embodiments, processing circuitry 603 may be defined to include memory so that separate memory circuitry is not required. Communication device 600 may also include an interface (such as a user interface) coupled with processing circuitry 603, and/or communication device 600 may be incorporated in a vehicle. Further details of an embodiment of the communication device 600 are illustrated in Figures 17, 18, 21, and 22.
[0074] As discussed herein, operations of communication device 600 may be performed by processing circuitry 603 and/or transceiver circuitry 601. For example, processing circuitry 603 may control transceiver circuitry 601 to transmit communications through transceiver circuitry 601 over a radio interface to a radio access network node (also referred to as a base station) and/or to receive communications through transceiver circuitry 601 from a RAN node over a radio interface. Moreover, modules may be stored in memory circuitry 605, and these modules may provide instructions so that when instructions of a module are executed by processing circuitry 603, processing circuitry 603 performs respective operations (e.g., operations discussed below with respect to Example Embodiments relating to communication devices). According to some embodiments, a communication device UE 600 and/or an element(s)/function(s) thereof may be embodied as a virtual node/nodes and/or a virtual machine/machines.
[0075] Figure 7 is a block diagram illustrating elements of a radio access network RAN node 700 (also referred to as a network node, base station, eNodeB/eNB, gNodeB/gNB, etc.) of a Radio Access Network (RAN) configured to provide cellular communication according to embodiments of inventive concepts. (RAN node 700 may be provided, for example, as discussed below with respect to network node 1710A, 1710B of Figure 17, network node 1900 of Figure 19, hardware 2104 or virtual machine 2108A, 2108B of Figure 21, and/or base station 2204 of Figure 22, all of which should be considered interchangeable in the examples and embodiments described herein and be within the intended scope of this disclosure, unless otherwise noted.) As shown, the RAN node 700 may include transceiver circuitry 701 (also referred to as a transceiver, e.g., corresponding to portions of RF transceiver circuitry 1912 and radio front end circuitry 1918 of Figure 19) including a transmitter and a receiver configured to provide uplink and downlink radio communications with mobile terminals. The RAN node may include network interface circuitry 707 (also referred to as a network interface, e.g., corresponding to portions of communication interface 1906 of Figure 19) configured to provide communications with other nodes (e.g., with other base stations) of the RAN and/or core network CN. The network node may also include processing circuitry 703703 (also referred to as a processor, e.g., corresponding to processing circuitry 1902 of Figure 19) coupled to the transceiver circuitry, and memory circuitry 705 (also referred to as memory, e.g., corresponding to memory 1904 of Figure 19) coupled to the processing circuitry. The memory circuitry 705 may include computer readable program code that when executed by the processing circuitry 703703 causes the processing circuitry to perform operations according to embodiments disclosed herein. According to other embodiments, processing circuitry 703703 may be defined to include memory so that a separate memory circuitry is not required.
[0076] As discussed herein, operations of the RAN node 700 may be performed by processing circuitry 703703, network interface 707, and/or transceiver 701. For example, processing circuitry 703703 may control transceiver 701 to transmit downlink communications through transceiver 701 over a radio interface to one or more mobile terminals UEs and/or to receive uplink communications through transceiver 701 from one or more mobile terminals UEs over a radio interface. Similarly, processing circuitry 703703 may control network interface 707 to transmit communications through network interface 707 to one or more other network nodes and/or to receive communications through network interface from one or more other network nodes. Moreover, modules may be stored in memory 705, and these modules may provide instructions so that when instructions of a module are executed by processing circuitry 703703, processing circuitry 703703 performs respective operations (e.g., operations discussed below with respect to Example Embodiments relating to RAN nodes). According to some embodiments, RAN node 700 and/or an element(s)/function(s) thereof may be embodied as a virtual node/nodes and/or a virtual machine/machines.
[0077] According to some other embodiments, a network node may be implemented as a core network CN node without a transceiver. In such embodiments, transmission to a wireless communication device UE may be initiated by the network node so that transmission to the wireless communication device UE is provided through a network node including a transceiver (e.g., through a base station or RAN node). According to embodiments where the network node is a RAN node including a transceiver, initiating transmission may include transmitting through the transceiver.
[0078] In the description that follows, the communication device 600 will be used to describe the various embodiments.
[0079] As previously indicated, the communication device 600 performs periodic MDT logging every logginginterval (1.28-61.44 s) within the loggingduration while the communication device 600 is in RRC_IDLE state (or in RRC_INACTIVE, not shown). When the communication device 600 transitions to RRC_CONNECTED during the loggingduration, the communication device 600 pauses or stops the ongoing MDT measurement logging while leaving timer T330 running, and then resumes the MDT measurement logging with the same logginginterval upon returning to RRC_IDLE. The communication device 600 stops the logging upon expiration of T330.
[0080] During logging, the communication device 600 collects DL RS received strength and quality (i.e., RSRP, RSRQ) based on existing measurements required for cell reselection purposes. In other words, the communication device 600 is not required to perform additional LTE or NR measurements beyond those existing ones. The communication device 600 also logs detailed location information, WLAN measurements, and BT measurements, to the extent that these are available. The communication device 600 reports the logged information to the network when the communication device 600 returns to RRC_CONNECTED state.
[0081] An ASN.l data structure for an exemplary LoggedMeasurement-Configuration message is shown below. This configuration can include the logginginterval and loggingduration fields, as well as an areaConfiguration field that indicates a geographic area for which the communication device 600 is requested to perform measurement logging.
- ASN1 START
LoggedMeasurementConfiguration-rlO ::= SEQUENCE { criticalExtensions CHOICE { cl CHOICE { loggedMeasurementConfiguration-r 10 LoggedMeasurementConfiguration-rlO-IEs, spare3 NULL, spare2 NULL, sparel NULL }, criticalExtensionsFuture SEQUENCE { }
} } LoggedMeasurementConfiguration-rlO-Ies ::= SEQUENCE { traceReference-r 10 TraceReference-r 10, traceRecordingSessionRef-rlO OCTET STRING (SIZE (2)), tce-Id-rlO OCTET STRING (SIZE (1)), absoluteTimelnfo-rlO AbsoluteTimelnfo-rlO, areaConfiguration-rlO AreaConfiguration-rlO OPTIONAL, — Need OR loggingDuration-r 10 LoggingDuration-r 10, logginglnterval-r 10 Logginglnterval-r 10, nonCriticalExtension LoggedMeasurementConfiguration-v 1080- les OPTIONAL
} LoggedMeasurementConfiguration-vl080-Ies ::= SEQUENCE { lateNonCriticalExtension-rlO OCTET STRING OPTIONAL, nonCriticalExtension LoggedMeasurementConfiguration-vl 130-Ies OPTIONAL }
LoggedMeasurementConfiguration-vl l30-Ies ::= SEQUENCE { plmn-IdentityList-rll PLMN-IdentityList3-rll OPTIONAL, — Need OR areaConfiguration-vl l30 AreaConfiguration-vll30 OPTIONAL, — Need OR nonCriticalExtension LoggedMeasurementConfiguration-v 1250-Ies OPTIONAL
}
LoggedMeasurementConfiguration-vl 250-Ies ::= SEQUENCE { targetMBSFN-AreaList-rl2 TargetMBSFN-AreaList-rl2 OPTIONAL, — Need OP nonCriticalExtension LoggedMeasurementConfiguration-vl 530-Ies OPTIONAL }
LoggedMeasurementConfiguration- v 1530-Ies ::= SEQUENCE { bt-NameList-rl5 B T-N ameList-r 15
OPTIONAL, - Need OR wlan-NameList-rl5 WL AN-NameList-r 15
OPTIONAL, - Need OR nonCriticalExtension SEQUENCE { }
OPTIONAL
}
TargetMBSFN-AreaList-rl2 ::= SEQUENCE (SIZE (O..maxMBSFN-Area)) OF
TargetMBSFN-Area-rl2
TargetMBSFN-Area-rl2 ::= SEQUENCE { mbsfn-AreaId-rl2
MBSFN-AreaId-rl2 OPTIONAL, - Need OR carrierFreq-rl2 ARFCN-ValueEUTRA-r9,
}
- ASN1ST0P
[0082] An ASN.1 data structure for an exemplary areaConfiguration field is illustrated below:
- ASN 1 START
AreaConfiguration-rlO ::= CHOICE { cellGloballdList-rlO CellGloballdList-rlO, trackingAreaCodeList-r 10 Tracking AreaCodeList-r 10
}
AreaConfiguration-vl l30 ::= SEQUENCE { trackingAreaCodeList-vl 130 TrackingAreaCodeList-vl 130
}
CellGloballdList-rlO ::= SEQUENCE (SIZE (1..32)) OF CellGloballdEUTRA
TrackingAreaCodeList-r 10 ::= SEQUENCE (SIZE (1..8)) OF TrackingAreaCode
TrackingAreaCodeList-vl l30 ::= SEQUENCE { plmn-Identity-perTAC-List-rl 1 SEQUENCE (SIZE (1..8)) OF PLMN-Identity
}
- ASN 1 STOP
[0083] Upon receiving such information, a communication device 600 camping on a cell will check if the cell is part of the area scope identified in areaConfiguration and will perform MDT logging if the serving cell is part of the area scope. If areaConfiguration is not present/configured, measurement logging is not restricted to specific cells or tracking areas but applies as long as the public land mobile network in which the communication device 600 is registered (referred to as “RPLMN”) is included in a plmn-IdentityList stored in the communication device 600’ s VarLogMeasReport.
[0084] The above configuration also includes a traceReference, tce-Id, and traceRecordingSessionRef parameters that identify the trace collection entity (TCE) that originated the request and should receive the MDT report. An ASN.1 data structure for an exemplary traceReference field, which includes a PLMN identity and a trace identifier is illustrated below:
- ASN 1 START
TraceReference-rlO ::= SEQUENCE { plmn-Identity-rlO PLMN-Identity, traceld-rlO OCTET STRING (SIZE (3))
}
- ASN 1 STOP [0085] After receiving a LoggedMeasurementConfiguration RRC message from the network, the communication device 600 stores the received configuration in the communication device 600 variable VarLogMeasConfig. An ASN.1 data structure for an exemplary
VarLogMeasConfig variable and/or IE is shown below:
- ASN1 START
VarLogMeasConfig-rlO ::= SEQUENCE { areaConfiguration-r 10 AreaConfiguration-r 10 OPTIONAL, loggingDuration-r 10 LoggingDuration-rlO, logginglnterval-rlO Logginglnterval-r 10 }
V arLogMeasConfig-r 11 ::= SEQUENCE { areaConfiguration-r 10 AreaConfiguration-r 10 OPTIONAL, areaConfiguration-vl 130 AreaConfiguration- v 1130 OPTIONAL, loggingDuration-r 10 LoggingDuration-rlO, logginglnterval-rlO Logginglnterval-r 10
}
VarLogMeasConfig-rl2 ::= SEQUENCE { areaConfiguration-r 10 AreaConfiguration-r 10 OPTIONAL, areaConfiguration-vl 130 AreaConfiguration- v 1130 OPTIONAL, loggingDuration-r 10 LoggingDuration-rlO, logginglnterval-rlO Logginglnterval-r 10, targetMB SFN- AreaList-r 12 T argetMB SFN- AreaList-r 12 OPTIONAL }
VarLogMeasConfig-rl5 ::= SEQUENCE { areaConfiguration-r 10 AreaConfiguration-r 10 OPTIONAL, areaConfiguration-vl 130 AreaConfiguration- v 1130 OPTIONAL, loggingDuration-r 10 LoggingDuration-r 10, logginglnterval-rlO Logginglnterval-rlO, targetMB SFN- AreaList-r 12 T argetMB SFN- AreaList-r 12 OPTIONAL, bt-NameList-rl5 BT-NameList-rl5 OPTIONAL, wlan-NameList-rl5 WL AN-N ameList-r 15 OPTIONAL
}
- ASN1STOP
[0086] In addition, the communication device 600 stores measurements logged according to this configuration in the communication device 600 variable VarLogMeasReport. An ASN.1 data structure for an exemplary VarLogMeasReport variable and/or IE is shown below:
- ASN1 START
VarLogMeasReport-rlO ::= SEQUENCE { traceReference-r 10 TraceReference-rlO, traceRecordingSessionRef-r 10 OCTET STRING (SIZE (2)), tce-Id-rlO OCTET STRING (SIZE (1)) plmn-Identity-r 10 PLMN-Identity, absoluteT imelnfo-r 10 AbsoluteTimelnfo-rlO, logMeasInfoList-r 10 LogMeasInfoList2-rlO
} LogMeasInfoList2-rlO ::= SEQUENCE (SIZE (L.maxLogMeas-rlO)) OF LogMeasInfo-rlO
LogMeasInfo-rlO ::= SEQUENCE { locationlnfo-rlO Locationlnfo-rlO OPTIONAL. relativeT imeStamp-r 10 INTEGER (0..7200), servCellldentity-r 10 CellGloballdEUTRA, measResultServCell-rl SEQUENCE { rsrpResult-rlO RSRP-Range, rsrqResult-rlO RSRQ-Range }, measResultNeighCells-r 10 SEQUENCE { measResultListEUTR A-r 10 MeasResultList2EUTR A-r9
OPTIONAL, measResultListUTRA-r 10 MeasResultList2UTRA-r9
OPTIONAL, measResultListGERAN -r 10 MeasResultList2GER AN -r 10
OPTIONAL, measResultListCDM A2000-r 10 MeasResultList2CDMA2000-r9
OPTIONAL } OPTIONAL,
[[ measResultListEUTRA-vl090 MeasResultList2EUTRA-v9eO OPTIONAL ]],
[[ measResultListMBSFN-rl2 MeasResultListMBSFN-rl2 OPTIONAL, measResultServCell-vl250 RSRQ-Range-v 1250 OPTIONAL, servCellRSRQ-T ype-r 12 RSRQ-Type-rl2 OPTIONAL, measResultListEUTRA-vl250 MeasResultList2EUTRA-vl250 OPTIONAL ]],
[ [ inDe viceCoexDetected-r 13 ENUMERATED {true} OPTIONAL ]],
[[ measResultServCell-vl360 RSRP-Range- v 1360 OPTIONAL ]],
[[ logMeasResultListBT-r!5 LogMeasResultListB T-r 15 OPTIONAL, logMeasResultListWLAN-r!5 LogMeasResultListWLAN-rl5 OPTIONAL ]],
MeasResultList2EUTRA-r9 := SEQUENCE (SIZE (L.maxFreq)) OF MeasResult2EUTRA-r9
MeasResult2EUTRA-r9 ::= SEQUENCE { carrierFreq-r9 ARFCN-ValueEUTRA, measResultList-r9 MeasResultListEUTRA
}
MeasResultListEUTRA ::= SEQUENCE (SIZE (L.maxCellReport)) OF MeasResultEUTRA
MeasResultEUTRA ::= SEQUENCE { physCellld PhysCellld, cgi-Info SEQUENCE { cellGloballd CellGloballdEUTRA, trackingAreaCode TrackingAreaCode, plmn-IdentityList PLMN -Identity List2 OPTIONAL }
OPTIONAL, measResult SEQUENCE { rsrpResult RSRP-Range OPTIONAL, rsrqResult RSRQ-Range OPTIONAL, [[ additionalSI-Info-r9 AdditionalSI-Info-r9 OPTIONAL ]],
[[ primaryPLMN-Suitable-rl2 ENUMERATED {true}
OPTIONAL, measResult-v 1250 RSRQ-Range-v 1250
OPTIONAL ]],
[[ rs-sinr-Result-rl3 RS-SINR-Range-rl3
OPTIONAL, cgi-Info-vl310 SEQUENCE { freqB andlndicator-r 13 FreqB andlndicator-rl 1 OPTIONAL, multiB andlnfoList-r 13 MultiBandlnfoList-rl 1 OPTIONAL, freqB andlndicatorPriority-r 13 ENUMERATED {true} OPTIONAL
OPTIONAL
]],
[[ measResult-vl360 RSRP-Range- v 1360
OPTIONAL ]],
[[ cgi-Info-5GC-rl5 SEQUENCE (SIZE (L.maxPLMN-rl l)) OF
CellAccessRelatedInfo-5GC-rl5
OPTIONAL ]]
}
}
- ASN1STOP
[0087] The network can request the communication device 600 to provide a logged measurement report by sending a UEInformationRequest message with the logMeasReportReq field set to “true”. The communication device 600 responds with a UEInformationResponse message that includes the indicated/requested logged measurement report.
[0088] As briefly mentioned above, a cell in which an RRC...IDLE LIE can receive broadcast SI, perform measurements of neighbor cells to support cell reselection, monitor a paging channel, and move to RRC_CONNECTED state as needed is often referred to as a “suitable cell”. The communication device 600’ s state when performing these actions in such a cell is often referred to as "camped normally".
[0089] In NR, a network can control communication device 600 access to each cell in various ways and/or on various levels. For example, access to a particular cell (or group of cells) can be barred for all communication devices 600, a specific group of communication device 600s, all except a specific group of communication devices 600, etc. based on various network- controlled criteria. For example, communication devices 600 having certain access identities might be allowed on cells reserved by a network operator for its internal use, while all other communication devices 600 are barred from accessing these cells. More details about 3GPP- specific cell barring mechanisms are given in 3GPP TS 38.304 (vl6.5.0) and 22.261 (vl8.3.0). [0090] As such, when a communication device 600 is camped normally on a particular cell, the communication device 600 may have selected the particular cell for camping because the communication device 600 is barred from accessing one or more other cells in the same environment that the communication device 600 would otherwise prefer (e.g., due to stronger/better signal than the particular cell). If configured by the network, the communication device 600 will log MDT -related information for the particular cell and report the logged information upon returning to RRC_CONNECTED.
[0091] [0073] Upon receiving the report containing the logged measurements for the particular cell, the network may interpret the particular cell being the best cell for communication device 600 in that environment. This is not the case, however, due to the access barring for the other cells. Based on this misinformation, the network may take various actions to build and/or improve coverage in the vicinity of the particular cell. However, these misinformed actions may not improve coverage and/or may degrade coverage in the vicinity of the particular cell and/or other coverage areas.
[0092] Accordingly, some embodiments of the present disclosure provide flexible and efficient techniques for a communication device 600 to log additional information about cell barring while it is camped normally in a cell and to include this information into a subsequent logged MDT report. This additional information facilitates better insight into actual coverage conditions experienced by communication devices 600 in the network. Additionally, embodiments enable the network to understand impacts of different access barring configurations (e.g., access barring of different subsets of cells and/or different groups of communication devices 600), and to select an appropriate access barring configuration based on this information.
[0093] [0075] In various embodiments described below, a communication device 600 can be configured (e.g., by receiving a LoggedMeasurementConfiguration message from the network and storing in VarLogMeasConfig) to log various measurement-related information when the communication device 600 is camped normally in cells. The measurement-related information can include any measurements and/or information currently logged by the communication device 600 in this scenario. Additionally, when the communication device 600 is camped normally on a cell that is not a “best cell” according to cell reselection criteria and the communication device 600 is barred from accessing the best cell (i.e., best cell is a barred cell) , the communication device 600 also logs an identifier of the barred cell that is the best cell, according to one of the following:
• only when the public land mobile network (PLMN) of the barred cell is in a list of PLMNs configured for logging stored in the communication device 600 (e.g., received as part of plmn-IdentityList in LoggedMeasurementConfiguration or stored in plmn- IdentityList in VarLogMeasReport)',
• only when the identifier is included in and/or associated with an areaConfig provided by the network (e.g., as part of the LoggedMeasurementConfiguratioriy, or
• unconditionally.
[0094] In some variants, the communication device 600 can condition the logging of the identifier on the identifier being part of a PLMN in the list and being associated with the areaConfig.
[0095] In some embodiments, when the communication device 600 logs the identifier of the barred cell, the communication device 600 can also log one of the more of the following information related to the barred cell:
• whether the barred cell is on the same or a different frequency than the cell on which the communication device 600 is camped normally;
• whether access barring was indicated in the master information block (MIB) broadcast in the barred cell or in SI blocks (SIBs) broadcast in the barred cell.
• when access barring was indicated in SIB(s): o whether the cell is barred for multiple PLMNs or NPNs; o whether the barred cell is part of a standalone non-public network (SNPN) cell and the communication device 600 is not authorized to access the SNPN (i.e., non-SNPN UE); o whether the barred cell is reserved for operator use; and o whether the barred cell is reserved for future use.
[0096] After logging this information, the communication device 600 can store the logged measurement-related information and the identifier of the barred cell (along any of the related information logged) in the communication device 600 variable VarLogMeasReport. For example, the exemplary ASN.1 data structure of the VarLogMeasReport can be modified to include such additional information. The network can request the communication device 600 to provide the logged measurement report by sending a UEInformationRequest message with the logMeasReportReq field set to “true”. The communication device 600 responds with a UEInformationResponse message that includes the indicated/requested logged measurement report with the additional information related to the barred cell encountered by the communication device 600.
[0097] Some embodiments can be included in a 3GPP specification, such as 3GPP TS 38.331 NR RRC specification. Such embodiments can be implemented (e.g., in a communication device 600 or network) in accordance with the specification. [0098] The embodiments described above can be further illustrated with reference to Figures 8-9, which show exemplary methods (e.g., procedures) for a communication device 600 and a network node, respectively. In other words, various features of operations described below correspond to various embodiments described above. These exemplary methods can be used cooperatively to provide various exemplary benefits and/or advantages. Although Figures 8-9 show specific blocks in particular orders, the operations of the respective methods can be performed in different orders than shown and can be combined and/or divided into blocks having different functionality than shown. Optional blocks or operations are indicated by dashed lines. [0099] Figure 8 shows a flow diagram of an exemplary method (e.g., procedure) for a communication device 600 configured to operate in a radio access network (RAN), according to various embodiments of the present disclosure. The exemplary method can be performed by a communication device 600 e.g., wireless device, MTC device, NB-IoT device, modem, etc. or component thereof) such as described elsewhere herein.
[0100] The exemplary method can include the operations of block 803, in which the communication device 600 can, based on one or more cell reselection criteria, determine that a first cell in the RAN is a best cell for camping in a non-connected state. In other words, the communication device 600 is determining that the first cell in the RAN is a best cell for camping in a camped normally state. The exemplary method can also include the operations of block 805, in which the communication device 600 can, based on determining that the communication device 600 is barred from accessing the first cell, select a second cell in the RAN for camping in the non-connected state. The exemplary method can also include the operations of block 807, in which the communication device 600 can log the following first information while camping normally on the second cell:
• measurement information related to the second cell, and an identifier of the first cell as the best cell determined according to the cell reselection criteria. [0101] The exemplary method can also include the operations of block 817, where the communication device 600 can send, to the RAN, a measurement report including the first information.
[0102] In some embodiments, the exemplary method can also include the operations of block 801, where the communication device 600 can receive a measurement reporting configuration from the RAN. In such case, logging the first information while camping normally on the second cell (e.g., block 807) and sending the measurement report (e.g., block 807) is based on the measurement reporting configuration. In some variants, the measurement reporting configuration is a logged MDT configuration and the measurement report is a logged MDT report. In some variants, logging the identifier of the first cell (e.g., in block 807) is responsive to one or more of the following conditions:
• the public land mobile network (PLMN) of the first cell is in a list of PLMNs included in the measurement reporting configuration or stored in the communication device 600; and
• the first cell is included in or associated with an area configuration included in the measurement reporting configuration.
[0103] In some embodiments, the exemplary method can also include the operations of block 950, where the communication device 600 can log one or more of the following second information while camping normally in the second cell:
• whether the first cell is on the same or a different frequency than the second cell; and
• whether access barring was indicated in a master information block (MIB) broadcast in the first cell or in SI blocks (SIBs) broadcast in the first cell.
The logged second information is included in the measurement report. In some variants, when the second information indicates that access barring was indicated in a SIB broadcast in the first cell, the second information also includes indications of one or more of the following:
• whether the first cell is barred for multiple networks, including public land mobile networks (PLMNs) and non-public networks (NPNs);
• whether the first cell is part of a standalone NPN (SNPN) and the communication device 600 is not authorized to access the SNPN (i.e., non-SNPN UE);
• whether the first cell is reserved for operator use; and
• whether the first cell is reserved for future use.
[0104] In some embodiments, the exemplary method can also include the operations of block 811, where the communication device 600 can exit the non-connected state and enter a connected state with the RAN. The measurement report is sent after entering the connected state. In some variants, the exemplary method can also include the operations of blocks 813-815, where the communication device 600 can, after entering the connected state, send to the RAN an indication that a measurement report is available and receive a request for the measurement report from the RAN in response to the indication . The measurement report can be sent in response to the request.
[0105] Figure 9 shows a flow diagram of an exemplary method (e.g., procedure) for a network node in a RAN, according to various embodiments of the present disclosure. The exemplary method shown in Figure 9 can be performed by a network node e.g., base station, eNB, gNB, ng-eNB, en-gNB, etc. or component thereof) such as described elsewhere herein. [0106] The exemplary method can include the operations of block 907, in which the network node can receive, from a communication device 600, a measurement report including the following first information:
• an identifier of a first cell in the RAN, the first cell being selected by the communication device 600 as a best cell for camping in a non-connected state according to cell reselection criteria; and
• measurement information related to a second cell in the RAN, the second cell being selected by the communication device 600 instead of the first cell because the communication device 600 was barred from accessing the first cell.
[0107] The exemplary method can also include the operations of block 909, where the network node can perform one or more of the following based on the measurement report:
• determining coverage for at least one of the first cell and the second cell; and
• selecting an accessing barring configuration for at least one of the first cell and the second cell.
[0108] In some embodiments, the exemplary method can also include the operations of block 901, where the network node can send a measurement reporting configuration to the communication device 600. The measurement report (e.g., in block 907) is based on the measurement reporting configuration. In some variants, the measurement reporting configuration is a logged MDT configuration and the measurement report is a logged MDT report. In some variants, the identifier of the first cell is included in the measurement report based on one or more of the following conditions:
• the PLMN of the first cell is in a list of PLMNs included in the measurement reporting configuration or stored in the communication device 600; and
• the first cell is included in or associated with an area configuration included in the measurement reporting configuration.
[0109] In some embodiments, the measurement report also includes one or more of the following second information:
• whether the first cell is on the same or a different frequency than the second cell; and
• whether access barring was indicated in a MIB or SIIB(s) broadcast in the first cell.
In some variants, when the second information indicates that access barring was indicated in a SIB broadcast in the first cell, the second information also includes indications of one or more of the following:
• whether the first cell is barred for multiple networks, including PLMNs and NPNs; • whether the first cell is part of a SNPN and the communication device 600 is not authorized to access the SNPN (i.e., non-SNPN UE);
• whether the first cell is reserved for operator use; and
• whether the first cell is reserved for future use.
[0110] In some embodiments, the measurement report is received (e.g., in 907) after the communication device 600 exits the non-connected state and enters a connected state with the RAN. In some variants the exemplary method can also include the operations of blocks 903-905, where the network node can, after the communication device 600 enters the connected state, receive from the communication device 600 an indication that a measurement report is available and send a request for the measurement report to the communication device 600 in response to the indication. The measurement report can be received in response to the request.
[0111] The above embodiments describe overall operation of communication device 600s when a cell is barred for the communication devices 600 to camp on, reserved for future use, etc.. As previously indicated, in 3GPP TS 38.304, different categories of cells and state of a communication device 600 in those cells are defined. One category of cell is called accepted cell, where communication devices 600 may camp to obtain limited service (obtain Emergency Calls and receive ETWS and CM AS notification). A communication device 600 camping on an acceptable cell is defined as being in “camped on any cell state”. The above embodiments may be used when the communication device 600 does not explicitly declare itself to be in the any cell selection state.
[0112] Any cell selection state
[0113] If the communication device 600 cannot find a cell that belongs to suitable cell or acceptable cell, it declares itself being in an any cell selection state. Further details are available in 3GPP TS 38.304.
[0114] communication device 600 in camped on any cell state
[0115] In various embodiments of inventive concepts, a first set of information logged by a communication device 600 is provided as a report while in “camped on any cell” state. The first set of information logged by the communication device 600 may or may not be dependent on a configuration policy set by the network.
[0116] The report in some embodiments of inventive concepts is a new logged MDT report defined and generated by the communication device 600. In other embodiments of inventive concepts, the report can be a part of the existing logged MDT report.
[0117] The first set of information logged by the communication device 600 in various embodiments of inventive concepts includes the various embodiments described hereinbelow. [0118] In one embodiment of inventive concepts, the communication device 600 logs the identifier of the cell while being in “camped on any cell” state. In some of these embodiments, the communication device 600 includes an indication that the current state is 'camped on any cell' state.
[0119] In some embodiments of this embodiment, the communication device 600 logs the cell identifier only if the public land mobile network (PLMN) is in a stored list of logged MDT PLMNs. In other embodiments of this embodiment, the communication device 600 logs the cell identifier without considering the PLMN information.
[0120] In another embodiment of inventive concepts, the communication device 600 logs the first suitable cell where the communication device 600 goes to (i.e., going to) “camped normally” state upon leaving the camped on any cell state.
[0121] In some embodiments of this embodiment, the communication device 600 logs the cell identifier of the first suitable cell only if the public land mobile network (PLMN) is in a stored list of logged MDT PLMNs. In other embodiments of this embodiment, the communication device 600 logs the cell identifier of the first suitable cell without considering the PLMN information.
[0122] In a further embodiment of inventive concepts, the communication device 600 logs the last suitable cell that the communication device 600 was camping on in “camped normally” state to before entering “any cell selection” state from which the communication device 600 transitioned to “camped on any cell” state.
[0123] In some embodiments of this embodiment, the communication device 600 logs the cell identifier of the last suitable cell only if the public land mobile network (PLMN) is in a stored list of logged MDT PLMNs. In other embodiments of this embodiment, the communication device 600 logs the cell identifier of the last suitable cell without considering the PLMN information.
[0124] In additional embodiments of inventive concepts, the communication device 600 indicates if the communication device has any emergency calls while being in the camped on any cell state. Thus, the communication device 600 indicates if the communication device 600 had received any tsunami or earthquake warning while being in “camped on any cell” state.
[0125] In yet another embodiment of inventive concepts, the communication device 600 includes the total duration for which the communication device 600 was in the camped on any cell state.
[0126] communication device 600 in any cell selection state.
[0127] In various embodiments of inventive concepts, a second set of information logged by a communication device 600 is provided as a report while in “any cell selection” state. The second set of information logged by the communication device 600 may or may not be dependent on a configuration policy set by the network.
[0128] The second set of information logged by the communication device 600 in various embodiments of inventive concepts includes the current standard set of measurement information and the information described in the various embodiments described hereinbelow
[0129] In some of the various embodiments of inventive concepts, the communication device 600 logs the reason for the communication device 600 being in the "any cell selection" state. Various non-limiting examples of the reasons are presented below.
[0130] In a first example of the reasons, the communication device 600 did not find any cell that fulfills the cell selection quality criterion as mentioned in various standards.
[0131] If the reason for being in “any cell selection” state is that the communication device 600 did not find any cell that fulfills the cell selection quality criterion then the communication device 600 also includes identifier of the cell that was deemed not to fulfil the cell selection criterion.
[0132] In some embodiments of this embodiment, the communication device 600 logs the cell identifier of the cell that was deemed not to fulfil the cell selection criterion only if the public land mobile network (PLMN) is in a stored list of logged MDT PLMNs. In other embodiments of this embodiment, the communication device 600 logs the cell identifier of the cell that was deemed not to fulfil the cell selection criterion without considering the PLMN information.
[0133] In a second example of the reasons, the communication device 600 determines that cell selection criterion (e.g., cell selection quality criterion) was fulfilled but the cell was barred. The barred information could be broadcasted in the master information block (MIB) or broadcasted in the system information block (SIB).
[0134] If the reason for being in “any cell selection” state is that the barred information was broadcasted in MIB of the selected cell then the communication device 600 also includes identifier of the cell whose MIB indicated the barring.
[0135] In some embodiments of this embodiment, the communication device 600 logs the cell identifier of the cell whose MIB indicated the barring only if the public land mobile network (PLMN) is in a stored list of logged MDT PLMNs. In other embodiments of this embodiment, the communication device 600 logs the cell identifier of the cell whose MIB indicated the barring only without considering the PLMN information.
[0136] If the reason for being in “any cell selection” state is that the barred information was broadcasted in SIB of the selected cell then the communication device 600 also includes the identifier of the cell whose SIB(s) indicated the barring. The communication device 600 also includes the identifier of the cell:
- if the cell is barred for multiple PLMNs or non-public networks (NPNs)
- if the cell is a standalone non-public network (SNPN) cell and the communication device 600 is not an SNPN communication device
- if the cell is reserved for operator use
- if the cell is reserved for future use
[0137] Network Configurations
[0138] The configuration policy transmitted from a network node of a network consists of the below embodiments:
[0139] In one embodiment of inventive concepts, the network configures the communication device 600 with periodical logged measurements configuration including while in “camped on any cell” state. In the configuration, the communication device 600 is configured to log information when the communication device 600 is in the "camped on any cell" state.
[0140] In another embodiment of inventive concepts, the network configures the communication device 600 with event triggered logged measurement configurations where the event encompasses the period while the communication device 600 is in out of coverage as per current standard. The configuration stipulates:
- Configuring the communication device 600 to log information when the communication device 600 is in “any cell selection” state and to log information when it is in “camped on any cell” state.
[0141] In a further embodiment of inventive concepts, the network configures the communication device with triggered logged measurement configurations where the event encompasses the period while the communication device 600 is in “camped on any cell” state. The communication device 600 logs information when the communication device is in the "camped on any cell" state.
[0142] In the description that follows, while the communication device may be any of the communication device 600, wireless device 1712A, 1712B, wired or wireless devices UE 1712C, UE 1712D, UE 1800, virtualization hardware 2104, virtual machines 2108A, 2108B, or UE 2206, the communication device 600 shall be used to describe the functionality of the operations of the communication device. Operations of the communication device 600 (implemented using the structure of the block diagram of Figure 6) will now be discussed with reference to the flow charts of Figures 10-15 according to some embodiments of inventive concepts. For example, modules may be stored in memory 605 of Figure 6, and these modules may provide instructions so that when the instructions of a module are executed by respective communication device processing circuitry 603, processing circuitry 603 performs respective operations of the flow chart.
[0143] Figure 10 illustrates operations the communication device 600 performs in various embodiments of inventive concepts. Turning to Figure 10, the processing circuitry 603 in block 1001, while being in an any cell selection state or a camped on any cell state: logs at least one of: a first set of information while in the camped on any cell state as a report; and a second set of information while in the any cell selection state, the second set of information being different from the first set of information and including a reason for the communication device being in the any cell selection state, the second set of information added to the report.
[0144] In block 1003, the processing circuitry 603, while being in a camped normally state on a cell: logs measurement information related to an evaluated best cell as a report and/or responsive to a current cell not being the best cell, logging a reason for not camping on the best cell as the report.
[0145] In block 1005, the processing circuitry 603 transmits, via transceiver 601, the report towards a network node.
[0146] In some embodiments of inventive concepts, the communication device 600 is configured by a network via a network node. Figures 11-13 illustrate various embodiments of inventive concepts of the communication device 600 being configured.
[0147] Turning to Figure 11, in some of the embodiments, in block 1101, the processing circuitry 603 receives a first configuration that configures the communication device 600 with a periodical logged measurements configuration for including the first set of information while in the camped on any cell state. In block 1103, the processing circuitry 603 logs the first set of information when in the camped on any cell state. Thus, the processing circuitry 603 periodically logs measurements including the first set of information while in the camped on any cell state.
[0148] Turning to Figure 12, in some other of the embodiments, the processing circuitry 603 in block 1201 receives a second configuration that configures the communication device with a periodical logged measurements configuration for including the second set of information while in the any cell selection state. In block 1203, the processing circuitry 603 logs the second set of information when in the any cell selection state. Thus, the processing circuitry 603 periodically logs measurements including the second set of information while in the any cell selection state.
[0149] Turning to Figure 13, in yet other of the embodiments, the processing circuitry in block 1301 receives a configuration that configures the communication device 600 with event triggered logged measurement configurations where the event encompasses the period while the communication device 600 is in out of coverage wherein the event triggered logged measurement configurations configure the communication device 600 to log at least one of: the first set of information when the communication device 600 is in the camped on any cell state; and the second set of information when the communication device 600 is in the any cell selection state.
[0150] Figure 14 illustrates various embodiments of information in the first set of information that is logged by the processing circuitry 603. Turning to Figure 14, in block 1401, in some of the embodiments of logging the first set of information, the processing circuitry 603 logs an emergency indication indicating whether the communication device 600 had any emergency calls while being in the camped on any cell state. In block 1403, in some of the embodiments of logging the first set of information, the processing circuitry 603 logs a tsunami/earthquake indication indicating whether the communication device 600 received any tsunami warning or earthquake warning while being in the camped on any cell state. In block 1405, in some of the embodiments of logging the first set of information, the processing circuitry 603 logs a total duration for which the communication device 600 was in the camped on any cell state.
[0151] In block 1407, in some of the embodiments of logging the first set of information, the processing circuitry 603 logs a cell identifier of a cell the communication device 600 is in while being in the camped on any cell state with an indication that a current state is the camped on any cell state. In some of the embodiments of logging the cell identifier, the processing circuitry 603 logs the cell identifier responsive to a public land mobile network, PLMN, on which the communication device is on is in a stored list of logged minimization of drive test, MDT, PLMNs. In other embodiments of logging the cell identifier, the processing circuitry 603 logs the cell identifier (regardless of whether the PLMN on which the communication device 600 is on is in the stored list of logged MDT PLMNs).
[0152] In block 1409, in some of the embodiments of logging the first set of information, the processing circuitry 603 logs a last suitable cell that the communication device 600 was camping on in a camped normally state before entering the any cell selection state from which the communication device 600 transitioned to the camped on any cell state. In some of the embodiments of logging the last suitable cell, the processing circuitry 603 logs a cell identifier (of the last suitable cell) responsive to a PLMN on which the communication device 600 is on is in a stored list of logged MDT PLMNs. In other embodiments of logging the cell identifier (of the last suitable cell), the processing circuitry 603 logs the cell identifier (regardless of whether the PLMN on which the communication device 600 is on is in the stored list of logged MDT PLMNs).
[0153] In block 1411, in some of the embodiments of logging the first set of information, the processing circuitry 603 logs a first suitable cell that the communication device 600 is going to a camped normally state upon leaving the camped on any cell state. In some of the embodiments of logging the first suitable cell, the processing circuitry 603 logs a cell identifier (of the first suitable cell) responsive to a PLMN on which the communication device 600 is on is in a stored list of logged MDT PLMNs. In other embodiments of logging the cell identifier (of the last suitable cell), the processing circuitry 603 logs the cell identifier (regardless of whether the PLMN on which the communication device 600 is on is in the stored list of logged MDT PLMNs).
[0154] Figure 15 illustrates various embodiments of inventive concepts of logging the second set of information. Turing to Figure 15, in block 1501, the processing circuitry 603 logs a reason for the communication device 600 for being in the any cell selection state.
[0155] In block 1503, in some of the embodiments of logging the second set of information, the processing circuitry 603 logs that the communication device 600 did not find any cell that fulfills a cell selection quality criterion. In some of the embodiments of logging that the communication device 600 did not find any cell, the processing circuitry 603 logs a cell identifier of the cell that was deemed to not fulfill the cell selection quality criterion responsive to a PLMN on which the communication device 600 is on is in a stored list of logged MDT PLMNs. In other embodiments of logging the cell identifier (of the last suitable cell), the processing circuitry 603 logs the cell identifier of the cell that was deemed to not fulfill the cell selection quality criterion (regardless of whether the PLMN on which the communication device 600 is on is in the stored list of logged MDT PLMNs).
[0156] In block 1505, in some of the embodiments of logging the second set of information, the processing circuitry 603 logs that the communication device 600 found a cell that fulfills a cell selection quality criterion but the cell was barred.
[0157] In some embodiments of inventive concepts, barred information was broadcast in a master information block, MIB). In some of these embodiments, the processing circuitry 603 logs a cell identifier of the cell whose MIB indicated the barring responsive to a PLMN on which the communication device 600 is on is in a stored list of logged MDT PLMNs. In other embodiments of logging the cell identifier of the cell whose MIB indicated the barring, the processing circuitry 603 logs the cell identifier of the cell whose MIB indicated the barring (regardless of whether the PLMN on which the communication device 600 is on is in the stored list of logged MDT PLMNs).
[0158] In some embodiments of inventive concepts, barred information was broadcast in a system information block, SIB. In these embodiments of inventive concepts, the processing circuitry 603 in logging the reason includes logging a cell identifier of the cell whose SIB indicated the barring responsive to at least one of:
- the cell being barred for multiple public land mobile networks or multiple nonpublic networks, NPNs
- the cell being barred is a standalone NPN, SNPN, cell and the communication device 600 is not an SNPN communication device
- the cell being barred is reserved for operator use; or
- the cell being barred is reserved for future use.
[0159] In the description that follows, while the network node may be any of the RAN node 700, network node 1710A, 1710B, 1900, 2206, hardware 2104, or virtual machine 2108A, 2108B, the RAN node 700 shall be used to describe the functionality of the operations of the network node. Operations of the RAN node 700 (implemented using the structure of Figure7) will now be discussed with reference to the flow chart of Figure 16 according to some embodiments of inventive concepts. For example, modules may be stored in memory 705 of Figure 7, and these modules may provide instructions so that when the instructions of a module are executed by respective RAN node processing circuitry 703, processing circuitry 703 performs respective operations of the flow chart.
[0160] Figure 16 illustrates operations the RAN node 700 performs in various embodiments of inventive concepts. Turning to Figure 16, the processing circuitry 703 in block 1601 transmits at least one of: a first configuration that configures the communication device 600 with a periodical logged measurements configuration including a first set of information while in a camped on any cell state; and a second configuration that configures the communication device 600 with a periodical logged measurements configuration including a second set of information while in the any cell selection state.
[0161] In block 1603, the processing circuitry 703 receives a report having at least one of: the first set of information when the communication device 600 was in the camped on any cell state and the second set of information when the communication device 600 was in the any cell selection state.
[0162] In some embodiments of inventive concepts, the first set of information includes one or more of an identifier of a cell the communication device while the communication device was in camped on any cell state and explicitly includes an indication that the current state is camped on any cell state; a log of a first suitable cell where the communication device is going to a camped normally state upon leaving the camped on any cell state; a log of a last suitable cell that the communication device was camping on in a camped normally state before entering the any cell selection state from which the communication device transitioned to the camped on any cell state; an emergency indication indicating whether the communication device had any emergency calls while being in the camped on any cell state; a tsunami/earthquake indication indicating whether the communication device received any tsunami warning or earthquake warning while being in the camped on any cell state; and/or a total duration for which the communication device was in the camped on any cell state. In other embodiments of inventive concepts, the second set of information includes one or more of the identifiers, logs, indications, and total duration in the first set of information.
[0163] In further embodiments of inventive concepts, the second set of information includes a reason for the communication device 600 being in an any cell selection state. In some of these further embodiments, the reason for the communication device 600 being in the any cell selection state includes at least one of: the communication device did not find any cell that fulfills a cell selection quality criterion; and the cell selection quality criterion was fulfilled but the cell was barred.
[0164] Figure 17 shows an example of a communication system 1700 in accordance with some embodiments.
[0165] In the example, the communication system 1700 includes a telecommunication network 1702 that includes an access network 1704, such as a radio access network (RAN), and a core network 1706, which includes one or more core network nodes 1708. The access network 1704 includes one or more access network nodes, such as network nodes 1710a and 1710b (one or more of which may be generally referred to as network nodes 1710), or any other similar 3rd Generation Partnership Project (3GPP) access node or non-3GPP access point. The network nodes 1710 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 1712a, 1712b, 1712c, and 1712d (one or more of which may be generally referred to as UEs 1712) to the core network 1706 over one or more wireless connections.
[0166] Example wireless communications over a wireless connection include transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 1700 may include any number of wired or wireless networks, network nodes, communication devices 600 (e.g., UEs), and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections. The communication system 1700 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.
[0167] The UEs 1712 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and/or operable to communicate wirelessly with the network nodes 1710 and other communication devices. Similarly, the network nodes 1710 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 1712 and/or with other network nodes or equipment in the telecommunication network 1702 to enable and/or provide network access, such as wireless network access, and/or to perform other functions, such as administration in the telecommunication network 1702.
[0168] In the depicted example, the core network 1706 connects the network nodes 1710 to one or more hosts, such as host 1716. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 1706 includes one more core network nodes (e.g., core network node 1708) 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 1708. 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 (SIDE), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and/or a User Plane Function (UPF).
[0169] The host 1716 may be under the ownership or control of a service provider other than an operator or provider of the access network 1704 and/or the telecommunication network 1702, and may be operated by the service provider or on behalf of the service provider. The host 1716 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.
[0170] As a whole, the communication system 1700 of Figure 17 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.
[0171] In some examples, the telecommunication network 1702 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 1702 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 1702. For example, the telecommunications network 1702 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.
[0172] In some examples, the UEs 1712 are configured to transmit and/or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 1704 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 1704. 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).
[0173] In the example, the hub 1714 communicates with the access network 1704 to facilitate indirect communication between one or more UEs (e.g., UE 1712c and/or 1712d) and network nodes (e.g., network node 1710b). In some examples, the hub 1714 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 1714 may be a broadband router enabling access to the core network 1706 for the UEs. As another example, the hub 1714 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 1710, or by executable code, script, process, or other instructions in the hub 1714. As another example, the hub 1714 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 1714 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 1714 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 1714 then provides to the UE either directly, after performing local processing, and/or after adding additional local content. In still another example, the hub 1714 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.
[0174] The hub 1714 may have a constant/persistent or intermittent connection to the network node 1710b. The hub 1714 may also allow for a different communication scheme and/or schedule between the hub 1714 and UEs (e.g., UE 1712c and/or 1712d), and between the hub 1714 and the core network 1706. In other examples, the hub 1714 is connected to the core network 1706 and/or one or more UEs via a wired connection. Moreover, the hub 1714 may be configured to connect to an M2M service provider over the access network 1704 and/or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 1710 while still connected via the hub 1714 via a wired or wireless connection. In some embodiments, the hub 1714 may be a dedicated hub - that is, a hub whose primary function is to route communications to/from the UEs from/to the network node 1710b. In other embodiments, the hub 1714 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 1710b, but which is additionally capable of operating as a communication start and/or end point for certain data channels.
[0175] Figure 18 shows a UE 1800 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other UEs. 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 the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.
[0176] 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).
[0177] The UE 1800 includes processing circuitry 1802 that is operatively coupled via a bus 1804 to an input/output interface 1806, a power source 1808, a memory 1810, a communication interface 1812, and/or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 18. 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.
[0178] The processing circuitry 1802 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 1810. The processing circuitry 1802 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 1802 may include multiple central processing units (CPUs).
[0179] In the example, the input/output interface 1806 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 the UE 1800. 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.
[0180] In some embodiments, the power source 1808 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. The power source 1808 may further include power circuitry for delivering power from the power source 1808 itself, and/or an external power source, to the various parts of the UE 1800 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 1808. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 1808 to make the power suitable for the respective components of the UE 1800 to which power is supplied.
[0181] The memory 1810 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 readonly memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 1810 includes one or more application programs 1814, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 1816. The memory 1810 may store, for use by the UE 1800, any of a variety of various operating systems or combinations of operating systems. [0182] The memory 1810 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.’ The memory 1810 may allow the UE 1800 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 the memory 1810, which may be or comprise a device-readable storage medium.
[0183] The processing circuitry 1802 may be configured to communicate with an access network or other network using the communication interface 1812. The communication interface 1812 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 1822. The communication interface 1812 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 a transmitter 1818 and/or a receiver 1820 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 1818 and receiver 1820 may be coupled to one or more antennas (e.g., antenna 1822) and may share circuit components, software or firmware, or alternatively be implemented separately.
[0184] In the illustrated embodiment, communication functions of the communication interface 1812 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. [0185] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 1812, 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., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).
[0186] 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.
[0187] 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 the UE 1800 shown in Figure 18.
[0188] 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 3GPP 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.
[0189] 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.
[0190] Figure 19 shows a network node 1900 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a UE and/or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)).
[0191] 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).
[0192] 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).
[0193] The network node 1900 includes a processing circuitry 1902, a memory 1904, a communication interface 1906, and a power source 1908. The network node 1900 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 the network node 1900 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, the network node 1900 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 1904 for different RATs) and some components may be reused (e.g., a same antenna 1910 may be shared by different RATs). The network node 1900 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1900, 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 1900.
[0194] The processing circuitry 1902 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 1900 components, such as the memory 1904, to provide network node 1900 functionality.
[0195] In some embodiments, the processing circuitry 1902 includes a system on a chip (SOC). In some embodiments, the processing circuitry 1902 includes one or more of radio frequency (RF) transceiver circuitry 1912 and baseband processing circuitry 1914. In some embodiments, the radio frequency (RF) transceiver circuitry 1912 and the baseband processing circuitry 1914 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 1912 and baseband processing circuitry 1914 may be on the same chip or set of chips, boards, or units. [0196] The memory 1904 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 the processing circuitry 1902. The memory 1904 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and/or other instructions capable of being executed by the processing circuitry 1902 and utilized by the network node 1900. The memory 1904 may be used to store any calculations made by the processing circuitry 1902 and/or any data received via the communication interface 1906. In some embodiments, the processing circuitry 1902 and memory 1904 is integrated. [0197] The communication interface 1906 is used in wired or wireless communication of signaling and/or data between a network node, access network, and/or UE. As illustrated, the communication interface 1906 comprises port(s)/terminal(s) 1916 to send and receive data, for example to and from a network over a wired connection. The communication interface 1906 also includes radio front-end circuitry 1918 that may be coupled to, or in certain embodiments a part of, the antenna 1910. Radio front-end circuitry 1918 comprises filters 1920 and amplifiers 1922. The radio front-end circuitry 1918 may be connected to an antenna 1910 and processing circuitry 1902. The radio front-end circuitry may be configured to condition signals communicated between antenna 1910 and processing circuitry 1902. The radio front-end circuitry 1918 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 1918 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1920 and/or amplifiers 1922. The radio signal may then be transmitted via the antenna 1910. Similarly, when receiving data, the antenna 1910 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1918. The digital data may be passed to the processing circuitry 1902. In other embodiments, the communication interface may comprise different components and/or different combinations of components.
[0198] In certain alternative embodiments, the network node 1900 does not include separate radio front-end circuitry 1918, instead, the processing circuitry 1902 includes radio front-end circuitry and is connected to the antenna 1910. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1912 is part of the communication interface 1906. In still other embodiments, the communication interface 1906 includes one or more ports or terminals 1916, the radio front-end circuitry 1918, and the RF transceiver circuitry 1912, as part of a radio unit (not shown), and the communication interface 1906 communicates with the baseband processing circuitry 1914, which is part of a digital unit (not shown).
[0199] The antenna 1910 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. The antenna 1910 may be coupled to the radio front-end circuitry 1918 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In certain embodiments, the antenna 1910 is separate from the network node 1900 and connectable to the network node 1900 through an interface or port.
[0200] The antenna 1910, communication interface 1906, and/or the processing circuitry 1902 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, the antenna 1910, the communication interface 1906, and/or the processing circuitry 1902 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.
[0201] The power source 1908 provides power to the various components of network node 1900 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 1908 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 1900 with power for performing the functionality described herein. For example, the network node 1900 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 1908. As a further example, the power source 1908 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.
[0202] Embodiments of the network node 1900 may include additional components beyond those shown in Figure 19 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein. For example, the network node 1900 may include user interface equipment to allow input of information into the network node 1900 and to allow output of information from the network node 1900. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1900.
[0203] Figure 20 is a block diagram of a host 2000, which may be an embodiment of the host 1716 of Figure 17, in accordance with various aspects described herein. As used herein, the host 2000 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. The host 2000 may provide one or more services to one or more UEs.
[0204] The host 2000 includes processing circuitry 2002 that is operatively coupled via a bus 2004 to an input/output interface 2006, a network interface 2008, a power source 2010, and a memory 2012. 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 18 and 19, such that the descriptions thereof are generally applicable to the corresponding components of host 2000.
[0205] The memory 2012 may include one or more computer programs including one or more host application programs 2014 and data 2016, which may include user data, e.g., data generated by a UE for the host 2000 or data generated by the host 2000 for a UE. Embodiments of the host 2000 may utilize only a subset or all of the components shown. The host application programs 2014 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). The host application programs 2014 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, the host 2000 may select and/or indicate a different host for over-the-top services for a UE. The host application programs 2014 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.
[0206] Figure 21 is a block diagram illustrating a virtualization environment 2100 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 2100 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.
[0207] Applications 2102 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.
[0208] Hardware 2104 includes processing circuitry, memory that stores software and/or instructions executable by hardware processing circuitry, and/or other hardware devices as described herein, such as a network interface, input/output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 2106 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 2108a and 2108b (one or more of which may be generally referred to as VMs 2108), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein. The virtualization layer 2106 may present a virtual operating platform that appears like networking hardware to the VMs 2108.
[0209] The VMs 2108 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 2106. Different embodiments of the instance of a virtual appliance 2102 may be implemented on one or more of VMs 2108, 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.
[0210] In the context of NFV, a VM 2108 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 2108, and that part of hardware 2104 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 2108 on top of the hardware 2104 and corresponds to the application 2102.
[0211] Hardware 2104 may be implemented in a standalone network node with generic or specific components. Hardware 2104 may implement some functions via virtualization.
Alternatively, hardware 2104 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 2110, which, among others, oversees lifecycle management of applications 2102. In some embodiments, hardware 2104 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 2112 which may alternatively be used for communication between hardware nodes and radio units.
[0212] Figure 22 shows a communication diagram of a host 2202 communicating via a network node 2204 with a UE 2206 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE 1712a of Figure 17 and/or UE 1800 of Figure 18), network node (such as network node 1710a of Figure 17 and/or network node 1900 of Figure 19), and host (such as host 1716 of Figure 17 and/or host 2000 of Figure 20) discussed in the preceding paragraphs will now be described with reference to Figure 22.
[0213] Like host 2000, embodiments of host 2202 include hardware, such as a communication interface, processing circuitry, and memory. The host 2202 also includes software, which is stored in or accessible by the host 2202 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 the UE 2206 connecting via an over-the-top (OTT) connection 2250 extending between the UE 2206 and host 2202. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection 2250. [0214] The network node 2204 includes hardware enabling it to communicate with the host 2202 and UE 2206. The connection 2260 may be direct or pass through a core network (like core network 1706 of Figure 17) 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.
[0215] The UE 2206 includes hardware and software, which is stored in or accessible by UE 2206 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 2206 with the support of the host 2202. In the host 2202, an executing host application may communicate with the executing client application via the OTT connection 2250 terminating at the UE 2206 and host 2202. 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. The OTT connection 2250 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 the OTT connection 2250.
[0216] The OTT connection 2250 may extend via a connection 2260 between the host 2202 and the network node 2204 and via a wireless connection 2270 between the network node 2204 and the UE 2206 to provide the connection between the host 2202 and the UE 2206. The connection 2260 and wireless connection 2270, over which the OTT connection 2250 may be provided, have been drawn abstractly to illustrate the communication between the host 2202 and the UE 2206 via the network node 2204, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
[0217] As an example of transmitting data via the OTT connection 2250, in step 2208, the host 2202 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 the UE 2206. In other embodiments, the user data is associated with a UE 2206 that shares data with the host 2202 without explicit human interaction. In step 2210, the host 2202 initiates a transmission carrying the user data towards the UE 2206. The host 2202 may initiate the transmission responsive to a request transmitted by the UE 2206. The request may be caused by human interaction with the UE 2206 or by operation of the client application executing on the UE 2206. The transmission may pass via the network node 2204, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 2212, the network node 2204 transmits to the UE 2206 the user data that was carried in the transmission that the host 2202 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 2214, the UE 2206 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 2206 associated with the host application executed by the host 2202.
[0218] In some examples, the UE 2206 executes a client application which provides user data to the host 2202. The user data may be provided in reaction or response to the data received from the host 2202. Accordingly, in step 2216, the UE 2206 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 the UE 2206. Regardless of the specific manner in which the user data was provided, the UE 2206 initiates, in step 2218, transmission of the user data towards the host 2202 via the network node 2204. In step 2220, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 2204 receives user data from the UE 2206 and initiates transmission of the received user data towards the host 2202. In step 2222, the host 2202 receives the user data carried in the transmission initiated by the UE 2206.
[0219] In an example scenario, factory status information may be collected and analyzed by the host 2202. As another example, the host 2202 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host 2202 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host 2202 may store surveillance video uploaded by a UE. As another example, the host 2202 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, the host 2202 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.
[0220] 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 the OTT connection 2250 between the host 2202 and UE 2206, 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 the host 2202 and/or UE 2206. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 2250 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 the OTT connection 2250 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 2204. 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 the host 2202. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 2250 while monitoring propagation times, errors, etc.
[0221] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and/or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.
[0222] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer- readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer- readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and/or by end users and a wireless network generally.
[0223] Further definitions and embodiments are discussed below.
[0224] In the above-description of various embodiments of present inventive concepts, it is to be understood that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of present inventive concepts. 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 present inventive concepts belong. It will be further understood that terms, such as those defined in commonly used dictionaries, 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.
[0225] When an element is referred to as being "connected", "coupled", "responsive", or variants thereof to another element, it can be directly connected, coupled, or responsive to the other element or intervening elements may be present. In contrast, when an element is referred to as being "directly connected", "directly coupled", "directly responsive", or variants thereof to another element, there are no intervening elements present. Like numbers refer to like elements throughout. Furthermore, "coupled", "connected", "responsive", or variants thereof as used herein may include wirelessly coupled, connected, or responsive. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. Well-known functions or constructions may not be described in detail for brevity and/or clarity. The term "and/or" (abbreviated “/”) includes any and all combinations of one or more of the associated listed items.
[0226] It will be understood that although the terms first, second, third, etc. may be used herein to describe various elements/operations, these elements/operations should not be limited by these terms. These terms are only used to distinguish one element/operation from another element/operation. Thus, a first element/operation in some embodiments could be termed a second element/operation in other embodiments without departing from the teachings of present inventive concepts. The same reference numerals or the same reference designators denote the same or similar elements throughout the specification.
[0227] As used herein, the terms "comprise", "comprising", "comprises", "include", "including", "includes", "have", "has", "having", or variants thereof are open-ended, and include one or more stated features, integers, elements, steps, components or functions but does not preclude the presence or addition of one or more other features, integers, elements, steps, components, functions or groups thereof. Furthermore, as used herein, the common abbreviation "e.g.", which derives from the Latin phrase "exempli gratia," may be used to introduce or specify a general example or examples of a previously mentioned item, and is not intended to be limiting of such item. The common abbreviation "i.e.", which derives from the Latin phrase "id est," may be used to specify a particular item from a more general recitation.
[0228] Example embodiments are described herein with reference to block diagrams and/or flowchart illustrations of computer-implemented methods, apparatus (systems and/or devices) and/or computer program products. It is understood that a block of the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations, can be implemented by computer program instructions that are performed by one or more computer circuits. These computer program instructions may be provided to a processor circuit of a general purpose computer circuit, special purpose computer circuit, and/or other programmable data processing circuit to produce a machine, such that the instructions, which execute via the processor of the computer and/or other programmable data processing apparatus, transform and control transistors, values stored in memory locations, and other hardware components within such circuitry to implement the functions/acts specified in the block diagrams and/or flowchart block or blocks, and thereby create means (functionality) and/or structure for implementing the functions/acts specified in the block diagrams and/or flowchart block(s). [0229] These computer program instructions may also be stored in a tangible computer- readable medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable medium produce an article of manufacture including instructions which implement the functions/acts specified in the block diagrams and/or flowchart block or blocks. Accordingly, embodiments of present inventive concepts may be embodied in hardware and/or in software (including firmware, resident software, micro-code, etc.) that runs on a processor such as a digital signal processor, which may collectively be referred to as "circuitry," "a module" or variants thereof.
[0230] It should also be noted that in some alternate implementations, the functions/acts noted in the blocks may occur out of the order noted in the flowcharts. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality/acts involved. Moreover, the functionality of a given block of the flowcharts and/or block diagrams may be separated into multiple blocks and/or the functionality of two or more blocks of the flowcharts and/or block diagrams may be at least partially integrated. Finally, other blocks may be added/inserted between the blocks that are illustrated, and/or blocks/operations may be omitted without departing from the scope of inventive concepts. Moreover, although some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows.
[0231] Many variations and modifications can be made to the embodiments without substantially departing from the principles of the present inventive concepts. All such variations and modifications are intended to be included herein within the scope of present inventive concepts. Accordingly, the above disclosed subject matter is to be considered illustrative, and not restrictive, and the examples of embodiments are intended to cover all such modifications, enhancements, and other embodiments, which fall within the spirit and scope of present inventive concepts. Thus, to the maximum extent allowed by law, the scope of present inventive concepts are to be determined by the broadest permissible interpretation of the present disclosure including the examples of embodiments and their equivalents, and shall not be restricted or limited by the foregoing detailed description.
EMBODIMENTS
1. A method performed by a communication device (600, 1712A, 1712B, 1712C, 1712D, 1800, 2104, 2108A, 2108B, 2206), the method comprising: logging (1001) at least one of: a first set of information while in a camped on an any cell state as a report; and a second set of information while in an any cell selection state, the second set of information being different from the first set of information and including a reason for the communication device being in the any cell selection state, the second set of information added to the report; and transmitting (1003) the report towards a network node.
2. The method of Embodiment 1, further comprising: receiving (1101) a first configuration that configures the communication device with a periodical logged measurements configuration for including the first set of information while in the camped on any cell state; and logging (1103) the first set of information when in the camped on any cell state.
3. The method of any of Embodiments 1-2, further comprising: receiving (1201) a second configuration that configures the communication device with a periodical logged measurements configuration for including the second set of information while in the any cell selection state; and logging (1203) the second set of information when in the any cell selection state.
4. The method of Embodiment 1, further comprising: receiving (1301) a configuration that configures the communication device with event triggered logged measurement configurations where the event encompasses the period while the communication device is in out of coverage wherein the event triggered logged measurement configurations configure the communication device to log at least one of: the first set of information when the communication device is in the camped on any cell state; and the second set of information when the communication device is in the any cell selection state. 5. The method of any of Embodiments 1-4, wherein logging the first set of information comprises: logging (1401) an emergency indication indicating whether the communication device had any emergency calls while being in the camped on any cell state.
6. The method of any of Embodiments 1-5, wherein logging the first set of information comprises: logging (1403) a tsunami/earthquake indication indicating whether the communication device received any tsunami warning or earthquake warning while being in the camped on any cell state.
7. The method of any of Embodiments 1-6, wherein logging the first set of information comprises: logging (1405) a total duration for which the communication device was in the camped on any cell state.
8. The method of any of Embodiments 1-7 wherein logging the first set of information comprises: logging (1407) a cell identifier of a cell the communication device is in while being in the camped on any cell state with an indication that a current state is the camped on any cell state.
9. The method of Embodiment 8 wherein logging the last cell identifier comprises logging the cell identifier responsive to a public land mobile network, PLMN, on which the communication device is on is in a stored list of logged minimization of drive test, MDT, PLMNs.
10. The method of any of Embodiments 1-9, wherein logging the first set of information comprises: logging (1409) a last suitable cell that the communication device was camping on in a camped normally state before entering the any cell selection state from which the communication device transitioned to the camped on any cell state.
11. The method of Embodiment 10 wherein logging the last suitable cell comprises logging a cell identifier of the last suitable cell responsive to a public land mobile network, PLMN, on which the communication device is on is in a stored list of logged minimization of drive test, MDT, PLMNs. 12. The method of Embodiment 10 wherein logging the last suitable cell comprises logging a cell identifier of the last suitable cell.
13. The method of any of Embodiments 1-12, wherein logging the first set of information comprises: logging (1411) a first suitable cell where the communication device is going to a camped normally state upon leaving the camped on any cell state.
14. The method of Embodiment 13 wherein logging the first suitable cell comprises logging a cell identifier responsive to a public land mobile network, PLMN, on which the communication device is on is in a stored list of logged minimization of drive test, MDT, PLMNs.
13. The method of Embodiment 13 wherein logging the first suitable cell comprises logging a cell identifier of the first suitable cell.
14. The method of any of Embodiments 1-13, wherein logging the second set of information comprises logging (1501) a reason for the communication device for being in the any cell selection state.
15. The method of Embodiment 14 wherein logging the reason comprises logging (1503) that the communication device did not find any cell that fulfills a cell selection quality criterion.
16. The method of Embodiment 15 wherein logging the reason further comprises logging a cell identifier of the cell that was deemed to not fulfill the cell selection quality criterion responsive to a public land mobile network, PLMN, on which the communication device is on is in a stored list of logged minimization of drive test, MDT, PLMNs.
17. The method of Embodiment 15 wherein logging the reason further comprises logging a cell identifier of the cell that was deemed to not fulfil the cell selection quality criterion.
18. The method of Embodiment 14 wherein logging the reason comprises logging (1505) that the communication device found a cell that fulfills a cell selection quality criterion but the cell was barred.
19. The method of Embodiment 18 wherein barred information was broadcast in a master information block, MIB, and logging the reason further comprises logging a cell identifier of the cell whose MIB indicated the barring responsive to a public land mobile network, PLMN, on which the communication device is on is in a stored list of logged minimization of drive test, MDT, PLMNs.
20. The method of Embodiment 18 wherein barred information was broadcast in a master information block, MIB, and logging the reason further comprises logging a cell identifier of the cell whose MIB indicated the barring.
21. The method of Embodiment 18 wherein barred information was broadcast in a system information block, SIB, and logging the reason further comprises logging a cell identifier of the cell whose SIB indicated the barring responsive to at least one of: the cell being barred for multiple public land mobile networks or multiple non-public networks, NPNs the cell being barred is a standalone NPN, SNPN cell and the communication device is not an SNPN communication device the cell being barred is reserved for operator use; or the cell being barred is reserved for future use.
22. A method performed by a network node (700, 1710A, 1710B, 1900, 2104, 2108A, 2108B, 2204), the method comprising: transmitting (1601) at least one of: a first configuration that configures the communication device with a periodical logged measurements configuration including a first set of information while in a camped on any cell state; and a second configuration that configures the communication device with a periodical logged measurements configuration including a second set of information while in the any cell selection state; and receiving (1603) a report having logged at least one of: the first set of information when the communication device was in the camped on any cell state; and the second set of information when the communication device was in the any cell selection state.
23. The method of Embodiment 22, wherein the first set of information and the second set of information comprises one or more of: an identifier of a cell the communication device while the communication device was in camped on any cell state and explicitly includes an indication that the current state is camped on any cell state; a log of a first suitable cell where the communication device is going to a camped normally state upon leaving the camped on any cell state; a log of a last suitable cell that the communication device was camping on in a camped normally state before entering the any cell selection state from which the communication device transitioned to the camped on any cell state; an emergency indication indicating whether the communication device had any emergency calls while being in the camped on any cell state; a tsunami/earthquake indication indicating whether the communication device received any tsunami warning or earthquake warning while being in the camped on any cell state; and/or a total duration for which the communication device was in the camped on any cell state.
24. The method of Embodiment 23 wherein the second set of information further comprises a reason for the communication device being in any cell selection state.
25. The method of Embodiment 24 wherein the reason for the communication device being in the any cell selection state comprises at least one of the communication device did not find any cell that fulfills a cell selection quality criterion; and the cell selection quality criterion was fulfilled but the cell was barred.
26. A communication device (600, 1712A, 1712B, 1712C, 1712D, 1800, 2104, 2108A, 2108B, 2206) adapted to: log (1001) at least one of: a first set of information while in a camped on any cell state as a report; and a second set of information while in an any cell selection state, the second set of information being different from the first set of information and including a reason for the communication device being in the any cell selection state, the second set of information added to the report; and transmit (1003) the report towards a network node.
27. The communication device of Embodiment 26 wherein the communication device is adapted to perform according to any of Embodiments 2-21. 28. A communication device (600, 1712A, 1712B, 1712C, 1712D, 1800, 2104, 2108A, 2108B, 2206) comprising: processing circuitry (603, 1802, 2112); and memory (605, 1810) coupled with the processing circuitry, wherein the memory includes instructions that when executed by the processing circuitry causes the communication device to: log (1010) at least one of: a first set of information while in a camped on any cell state as a report; and a second set of information while in an any cell selection state, the second set of information being different from the first set of information and including a reason for the communication device being in the any cell selection state, the second set of information added to the report; and transmit (1003) the report towards a network node.
29. The communication device of Embodiment 28, wherein the memory includes further instructions that when executed by the processing circuitry causes the communication device to perform according to any of Embodiments 2-21.
30. A computer program comprising program code to be executed by processing circuitry (603, 1802, 2112) of a communication device (600, 1712A, 1712B, 1712C, 1712D, 1800, 2104, 2108A, 2108B, 2206), whereby execution of the program code causes the communication device (600, 1712A, 1712B, 1712C, 1712D, 1800, 2104, 2108A, 2108B, 2206) to: log (1001) at least one of: a first set of information while in a camped on any cell state as a report; and a second set of information while in an any cell selection state, the second set of information being different from the first set of information and including a reason for the communication device being in the any cell selection state, the second set of information added to the report; and transmit (1003) the report towards a network node.
31. The computer program of Embodiment 30 comprising further program code whereby execution of the further program code causes the communication device to perform according to any of Embodiments 2-21. 32. A computer program product comprising a non-transitory storage medium including program code to be executed by processing circuitry (603, 1802, 2112) of a communication device (600, 1712A, 1712B, 1712C, 1712D, 1800, 2104, 2108A, 2108B, 2206), whereby execution of the program code causes the communication device (200, 1712A, 1712B, 1712C, 1712D, 1800, 2104, 2108A, 2108B, 2206) to: log (1001) at least one of: a first set of information while in a camped on any cell state as a report; and a second set of information while in an any cell selection state, the second set of information being different from the first set of information and including a reason for the communication device being in the any cell selection state, the second set of information added to the report; and transmit (1003) the report towards a network node.
33. The computer program product of Embodiment 32 wherein the non-transitory storage medium includes further program code whereby execution of the further program code causes the communication device to perform according to any of Embodiments 2-21.
34. A network node (700, 1710A, 1710B, 1900, 2104, 2108A, 2108B, 2204) adapted to: transmit (1601) at least one of: a first configuration that configures the communication device with a periodical logged measurements configuration including a first set of information while in a camped on any cell state; and a second configuration that configures the communication device with a periodical logged measurements configuration including a second set of information while in the any cell selection state; and receive (1603) a report having logged at least one of: the first set of information when the communication device was in the camped on any cell state; and the second set of information when the communication device was in the any cell selection state.
35. The network node of Embodiment 34 wherein the communication device is adapted to perform according to any of Embodiments 23-26.
36. A network node (700, 1710A, 1710B, 1900, 2104, 2108A, 2108B, 2204) comprising: processing circuitry (703, 1802, 2112); and memory (705, 1810) coupled with the processing circuitry, wherein the memory includes instructions that when executed by the processing circuitry causes the network node to: transmit (1601) at least one of: a first configuration that configures the communication device with a periodical logged measurements configuration including a first set of information while in a camped on any cell state; and a second configuration that configures the communication device with a periodical logged measurements configuration including a second set of information while in the any cell selection state; and receive (1603) a report having logged at least one of: the first set of information when the communication device was in the camped on any cell state; and the second set of information when the communication device was in the any cell selection state.
37. The network node of Embodiment 36 wherein the memory includes further instructions that when executed by the processing circuitry causes the network node to perform according to any of Embodiments 23-26.
38. A computer program comprising program code to be executed by processing circuitry (703, 1902) of a radio access network, RAN, node (700, 1710A, 1710B, 1900, 2104, 2108A, 2108B, 2204), whereby execution of the program code causes the RAN node (700, 1710A, 1710B, 1900, 2104, 2108A, 2108B, 2204) to: transmit (1601) at least one of: a first configuration that configures the communication device with a periodical logged measurements configuration including a first set of information while in a camped on any cell state; and a second configuration that configures the communication device with a periodical logged measurements configuration including a second set of information while in the any cell selection state; and receive (1603) a report having logged at least one of: the first set of information when the communication device was in the camped on any cell state; and the second set of information when the communication device was in the any cell selection state.
39. The computer program of Embodiment 38 comprising further program code whereby execution of the further program code causes the network node to perform according to any of Embodiments 23-26.
40. A computer program product comprising a non-transitory storage medium including program code to be executed by processing circuitry (703, 1902) of a radio access network, RAN, node (700, 1710A, 1710B, 1900, 2104, 2108A, 2108B, 2204), whereby execution of the program code causes the RAN node (700, 1710A, 1710B, 1900, 2104, 2108A, 2108B, 2204) to: transmit (1601) at least one of: a first configuration that configures the communication device with a periodical logged measurements configuration including a first set of information while in a camped on any cell state; and a second configuration that configures the communication device with a periodical logged measurements configuration including a second set of information while in the any cell selection state; and receive (1603) a report having logged at least one of: the first set of information when the communication device was in the camped on any cell state; and the second set of information when the communication device was in the any cell selection state.
41. The computer program product of Embodiment 40 wherein the non-transitory storage medium includes further program code whereby execution of the further program code causes the network node to perform according to any of Embodiments 23-26.
Further embodiments:
42. A method for a user equipment (UE) configured to operate in a radio access network (RAN), the method comprising: based on one or more cell reselection criteria, determining that a first cell in the RAN is a best cell for camping in a non-connected state; based on determining that the UE is barred from accessing the first cell, selecting a second cell in the RAN for camping in the non-connected state; logging the following first information while camping normally on the second cell: measurement information related to the second cell, and an identifier of the first cell as the best cell determined according to the cell reselection criteria. sending, to the RAN, a measurement report including the first information.
43. The method of embodiment 42, further comprising receiving a measurement reporting configuration from the RAN, wherein logging the first information while camping normally on the second cell and sending the measurement report is based on the measurement reporting configuration.
44. The method of embodiment 43, wherein the measurement reporting configuration is a logged minimization of drive testing (MDT) configuration and the measurement report is a logged MDT report.
45. The method of any of embodiments 42-44, wherein logging the identifier of the first cell is responsive to one or more of the following conditions: the public land mobile network (PLMN) of the first cell is in a list of PLMNs included in the measurement reporting configuration or stored in the UE; and the first cell is included in or associated with an area configuration included in the measurement reporting configuration.
46. The method of any of embodiments 42-45, further comprising logging one or more of the following second information while camping normally in the second cell: whether the first cell is on the same or a different frequency than the second cell; and whether access barring was indicated in a master information block (MIB) broadcast in the first cell or in SI blocks (SIBs) broadcast in the first cell, wherein the logged second information is included in the measurement report.
47. The method of embodiment 46, wherein when the second information indicates that access barring was indicated in a SIB broadcast in the first cell, the second information also includes indications of one or more of the following: whether the first cell is barred for multiple networks, including public land mobile networks (PLMNs) and non-public networks (NPNs); whether the first cell is part of a standalone NPN (SNPN) and the UE is not authorized to access the SNPN (i.e., non-SNPN UE); whether the first cell is reserved for operator use; and whether the first cell is reserved for future use.
48. The method of any of embodiments 42-47, further comprising exiting the non-connected state and entering a connected state with the RAN, wherein the measurement report is sent after entering the connected state.
49. The method of embodiment 48, further comprising: after entering the connected state, sending to the RAN an indication that a measurement report is available; and receiving from the RAN, in response to the indication, a request for the measurement report, wherein the measurement report is sent in response to the request.
50. A method for a network node in a radio access network (RAN), the method comprising: receiving, from a user equipment (UE), a measurement report including the following first information: an identifier of a first cell in the RAN, the first cell being selected by the UE as a best cell for camping in a non-connected state according to cell reselection criteria; measurement information related to a second cell in the RAN, the second cell being selected by the UE instead of the first cell because the UE was barred from accessing the first cell; performing one or more of the following based on the measurement report: determining coverage for at least one of the first cell and the second cell; and selecting an accessing barring configuration for at least one of the first cell and the second cell.
51. The method of embodiment 50, further comprising sending a measurement reporting configuration to the UE, wherein the measurement report is based on the measurement reporting configuration.
52. The method of embodiment 51, wherein the measurement reporting configuration is a logged minimization of drive testing (MDT) configuration and the measurement report is a logged MDT report.
53. The method of any of embodiments 51-52, wherein the identifier of the first cell is included in the measurement report based on one or more of the following conditions: the public land mobile network (PLMN) of the first cell is in a list of PLMNs included in the measurement reporting configuration or stored in the UE; and the first cell is included in or associated with an area configuration included in the measurement reporting configuration.
54. The method of any of embodiments 50-53, wherein the measurement report also includes one or more of the following second information: whether the first cell is on the same or a different frequency than the second cell; and whether access barring was indicated in a master information block (MIB) broadcast in the first cell or in SI blocks (SIBs) broadcast in the first cell.
55. The method of embodiment 54, wherein when the second information indicates that access barring was indicated in a SIB broadcast in the first cell, the second information also includes indications of one or more of the following: whether the first cell is barred for multiple networks, including public land mobile networks (PLMNs) and non-public networks (NPNs); whether the first cell is part of a standalone NPN (SNPN) and the UE is not authorized to access the SNPN (i.e., non-SNPN UE); whether the first cell is reserved for operator use; and whether the first cell is reserved for future use.
56. The method of any of embodiments 50-55, wherein the measurement report is received after the UE exits the non-connected state and enters a connected state with the RAN
57. The method of embodiment 56, further comprising: after the UE enters the connected state, receiving from the UE an indication that a measurement report is available; and sending to the UE, in response to the indication, a request for the measurement report, wherein receiving the measurement report is responsive to the request.
58. A user equipment (UE) configured to operate in a radio access network (RAN), the UE comprising: communication interface circuitry configured to communicate with one or more network nodes in the RAN; 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 any of the methods of embodiments 42-49.
59. A user equipment (UE) configured to operate in a radio access network (RAN), the UE being further arranged to perform operations corresponding to any of the methods of embodiments 42-49.
60. 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 a radio access network (RAN), configure the UE to perform operations corresponding to any of the methods of embodiments 42-49.
61. A computer program product comprising computer-executable instructions that, when executed by processing circuitry of a user equipment (UE) configured to operate in a radio access network (RAN), configure the UE to perform operations corresponding to any of the methods of embodiments 42-49.
62. A network node in a radio access network (RAN), the network node comprising: communication interface circuitry configured to communicate with one or more user equipment (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 any of the methods of embodiments 50-57.
63. A network node in a radio access network (RAN), the network node being further arranged to perform operations corresponding to any of the methods of embodiments 50-57.
64. A non-transitory, computer-readable medium storing computer-executable instructions that, when executed by processing circuitry of a network node in a radio access network (RAN), configure the network node to perform operations corresponding to any of the methods of embodiments 50-57.
65. A computer program product comprising computer-executable instructions that, when executed by processing circuitry of a network node in a cellular radio access network (RAN), configure the network node to perform operations corresponding to any of the methods of embodiments 50-57.
[0232] Explanations are provided for various abbreviations/acronyms used in the present disclosure. Abbreviation Explanation RAT Radio Access Technology MDT Minimization of Drive Test
UE User Equipment RRC Radio Resource Control ETWS Earthquake and Tsunami Warning System CMAS Commercial Mobile Alert System [0233] References are identified below
1. 3GPP TS38.331, NR; Radio Resource Control (RRC); Protocol specification, version 16.5.0,
2. 3GPP TS37.320 Universal Terrestrial Radio Access (UTRA) and Evolved Universal
Terrestrial Radio Access (E-UTRA); Radio measurement collection for Minimization of Drive Tests (MDT); Overall description; Stage 2, version 16.5.0,
3. 3GPP TS 38.304, NR, User Equipment (UE) procedures in idle mode and in RRC Inactive state, version 16.5.0,
4. 3GPP TS 22.261, Service requirements for the 5G system, Version 18.3.0

Claims

1. A method performed by a communication device (600, 1712A, 1712B, 1712C, 1712D, 1800, 2104, 2108A, 2108B, 2206), the method comprising: while being in an any cell selection state or a camped on any cell state: logging (1001) at least one of: a first set of information while in the camped on an any cell state as a report; and a second set of information while in the any cell selection state, the second set of information being different from the first set of information and including a reason for the communication device being in the any cell selection state, the second set of information added to the report; and while being in a camped normally state on a cell: logging (1003) measurement information related to an evaluated best cell as a report and/or responsive to a current cell not being the best cell, logging a reason for not camping on the best cell as the report; and transmitting (1005) the report towards a network node.
2. The method of Claim 1, further comprising: based on one or more cell reselection criteria, determining (803) that a first cell in a radio access network, RAN, is a best cell for camping in a non-connected state; based on determining that the communication device is barred from accessing the first cell, selecting (805) a second cell for camping in the non-connected state; and logging (807) the following first information while camping normally on the second cell: measurement information related to the second cell, and an identifier of the first cell as the best cell determined according to the cell reselection criteria.
3. The method of any of Claims 1-2, further comprising: receiving (1101) a first configuration that configures the communication device with a periodical logged measurements configuration for including the first set of information while in the camped on any cell state; and logging (1103) the first set of information when in the camped on any cell state.
4. The method of any of Claims 1-3, further comprising: receiving (1201) a second configuration that configures the communication device with a periodical logged measurements configuration for including the second set of information while in the any cell selection state; and logging (1203) the second set of information when in the any cell selection state.
5. The method of Claim 1, further comprising: receiving (1301) a configuration that configures the communication device with event triggered logged measurement configurations where the event encompasses the period while the communication device is in out of coverage wherein the event triggered logged measurement configurations configure the communication device to log at least one of: the first set of information when the communication device is in the camped on any cell state; and the second set of information when the communication device is in the any cell selection state.
6. The method of any of Claims 1-5, wherein logging the first set of information comprises at least one of: logging (1401) an emergency indication indicating whether the communication device had any emergency calls while being in the camped on any cell state; and logging (1403) a tsunami/earthquake indication indicating whether the communication device received any tsunami warning or earthquake warning while being in the camped on any cell state.
7. The method of any of Claims 1-6, wherein logging the first set of information comprises at least one of: logging (1405) a total duration for which the communication device was in the camped on any cell state; and logging (1407) a cell identifier of a cell the communication device is in while being in the camped on any cell state with an indication that a current state is the camped on any cell state.
8. The method of Claim 7 wherein logging the last cell identifier comprises logging the cell identifier responsive to a public land mobile network, PLMN, on which the communication device is on is in a stored list of logged minimization of drive test, MDT, PLMNs.
9. The method of any of Claims 1-8, wherein logging the first set of information comprises: logging (1409) a last suitable cell that the communication device was camping on in a camped normally state before entering the any cell selection state from which the communication device transitioned to the camped on any cell state.
10. The method of Claim 9 wherein logging the last suitable cell comprises logging a cell identifier of the last suitable cell responsive to a public land mobile network, PLMN, on which the communication device is on is in a stored list of logged minimization of drive test, MDT, PLMNs.
11. The method of Claim 9 wherein logging the last suitable cell comprises logging a cell identifier of the last suitable cell.
12. The method of any of Claims 1-11, wherein logging the first set of information comprises: logging (1411) a first suitable cell where the communication device is going to a camped normally state upon leaving the camped on any cell state.
13. The method of Claim 12 wherein logging the first suitable cell comprises one of: logging a cell identifier responsive to a public land mobile network, PLMN, on which the communication device is on is in a stored list of logged minimization of drive test, MDT, PLMNs; and logging a cell identifier of the first suitable cell.
14. The method of any of Claims 1-13, wherein logging the second set of information comprises logging (1501) a reason for the communication device for being in the any cell selection state.
15. The method of Claim 14 wherein logging the reason comprises logging (1503) that the communication device did not find any cell that fulfills a cell selection quality criterion.
16. The method of Claim 14 wherein logging the reason further comprises logging at least one of: a cell identifier of the cell that was deemed to not fulfill the cell selection quality criterion responsive to a public land mobile network, PLMN, on which the communication device is on is in a stored list of logged minimization of drive test, MDT, PLMNs; and a cell identifier of the cell that was deemed to not fulfil the cell selection quality criterion.
17. The method of Claim 14 wherein logging the reason comprises logging (1505) that the communication device found a cell that fulfills a cell selection quality criterion but the cell was barred.
18. The method of Claim 17 wherein barred information was broadcast in a master information block, MIB, and logging the reason further comprises at least one of: logging a cell identifier of the cell whose MIB indicated the barring responsive to a public land mobile network, PLMN, on which the communication device is on is in a stored list of logged minimization of drive test, MDT, PLMNs; and a cell identifier of the cell whose MIB indicated the barring.
19. The method of Claim 17 wherein barred information was broadcast in a system information block, SIB, and logging the reason further comprises logging a cell identifier of the cell whose SIB indicated the barring responsive to at least one of: the cell being barred for multiple public land mobile networks or multiple non-public networks, NPNs the cell being barred is a standalone NPN, SNPN cell and the communication device is not an SNPN communication device the cell being barred is reserved for operator use; or the cell being barred is reserved for future use.
20. A method performed by a network node (700, 1710A, 1710B, 1900, 2104, 2108A, 2108B, 2204), the method comprising: transmitting (1601) at least one of: a first configuration that configures the communication device with a periodical logged measurements configuration including a first set of information while in a camped on any cell state; and a second configuration that configures the communication device with a periodical logged measurements configuration including a second set of information while in the any cell selection state; and receiving (1603) a report having logged at least one of: the first set of information when the communication device was in the camped on any cell state; and the second set of information when the communication device was in the any cell selection state.
21. The method of Claim 20, further comprising: receiving (907), from a user equipment (UE), a measurement report including the following first information: an identifier of a first cell in the RAN, the first cell being selected by the UE as a best cell for camping in a non-connected state according to cell reselection criteria; measurement information related to a second cell in the RAN, the second cell being selected by the UE instead of the first cell because the UE was barred from accessing the first cell; performing (909) one or more of the following based on the measurement report: determining coverage for at least one of the first cell and the second cell; and selecting an accessing barring configuration for at least one of the first cell and the second cell.
22. The method of any of Claims 20-21, wherein the first set of information and the second set of information comprises one or more of: an identifier of a cell the communication device while the communication device was in camped on any cell state and explicitly includes an indication that the current state is camped on any cell state; a log of a first suitable cell where the communication device is going to a camped normally state upon leaving the camped on any cell state; a log of a last suitable cell that the communication device was camping on in a camped normally state before entering the any cell selection state from which the communication device transitioned to the camped on any cell state; an emergency indication indicating whether the communication device had any emergency calls while being in the camped on any cell state; a tsunami/earthquake indication indicating whether the communication device received any tsunami warning or earthquake warning while being in the camped on any cell state; and/or a total duration for which the communication device was in the camped on any cell state.
23. The method of Claim 22 wherein the second set of information further comprises a reason for the communication device being in any cell selection state.
24. The method of Claim 23 wherein the reason for the communication device being in the any cell selection state comprises at least one of the communication device did not find any cell that fulfills a cell selection quality criterion; and the cell selection quality criterion was fulfilled but the cell was barred.
25. The method of claim 21, wherein when the second information indicates that access barring was indicated in a SIB broadcast in the first cell, the second information also includes indications of one or more of the following: whether the first cell is barred for multiple networks, including public land mobile networks (PLMNs) and non-public networks (NPNs); whether the first cell is part of a standalone NPN (SNPN) and the UE is not authorized to access the SNPN (i.e., non-SNPN UE); whether the first cell is reserved for operator use; and whether the first cell is reserved for future use.
26. A communication device (600, 1712A, 1712B, 1712C, 1712D, 1800, 2104, 2108A, 2108B, 2206) adapted to: while being in an any cell selection state or a camped on any cell state: log (1001) at least one of: a first set of information while in the camped on any cell state as a report; and a second set of information while in the any cell selection state, the second set of information being different from the first set of information and including a reason for the communication device being in the any cell selection state, the second set of information added to the report; and while being in a camped normally state on a cell: logging (1003) measurement information related to an evaluated best cell as a report and/or responsive to a current cell not being the best cell, logging a reason for not camping on the best cell as the report; and transmit (1005) the report towards a network node.
27. The communication device of Claim 26 wherein the communication device is adapted to perform according to any of Claims 2-19.
28. A communication device (600, 1712A, 1712B, 1712C, 1712D, 1800, 2104, 2108A, 2108B, 2206) comprising: processing circuitry (603, 1802, 2112); and memory (605, 1810) coupled with the processing circuitry, wherein the memory includes instructions that when executed by the processing circuitry causes the communication device to: while being in an any cell selection state or a camped on any cell state: log (1010) at least one of: a first set of information while in the camped on any cell state as a report; and a second set of information while in the any cell selection state, the second set of information being different from the first set of information and including a reason for the communication device being in the any cell selection state, the second set of information added to the report; and while being in a camped normally state on a cell: logging (1003) measurement information related to an evaluated best cell as the report and/or responsive to a current cell not being the best cell, logging a reason for not camping on the best cell as the report; and transmit (1005) the report towards a network node.
29. The communication device of Claim 28, wherein the memory includes further instructions that when executed by the processing circuitry causes the communication device to perform according to any of Claims 2-19.
30. A computer program comprising program code to be executed by processing circuitry (603, 1802, 2112) of a communication device (600, 1712A, 1712B, 1712C, 1712D, 1800, 2104, 2108A, 2108B, 2206), whereby execution of the program code causes the communication device (600, 1712A, 1712B, 1712C, 1712D, 1800, 2104, 2108A, 2108B, 2206) to: while being in an any cell selection state or a camped on any cell state: log (1001) at least one of: a first set of information while in the camped on any cell state as a report; and a second set of information while in the any cell selection state, the second set of information being different from the first set of information and including a reason for the communication device being in the any cell selection state, the second set of information added to the report; and while being in a camped normally state on a cell: logging (1003) measurement information related to an evaluated best cell as the report and/or responsive to a current cell not being the best cell, logging a reason for not camping on the best cell as the report; and transmit (1005) the report towards a network node.
31. The computer program of Claim 30 comprising further program code whereby execution of the further program code causes the communication device to perform according to any of Claims 2-19.
32. A computer program product comprising a non-transitory storage medium including program code to be executed by processing circuitry (603, 1802, 2112) of a communication device (600, 1712A, 1712B, 1712C, 1712D, 1800, 2104, 2108A, 2108B, 2206), whereby execution of the program code causes the communication device (200, 1712A, 1712B, 1712C, 1712D, 1800, 2104, 2108A, 2108B, 2206) to: while being in an any cell selection state or a camped on any cell state: log (1001) at least one of: a first set of information while in the camped on any cell state as a report; and a second set of information while in the any cell selection state, the second set of information being different from the first set of information and including a reason for the communication device being in the any cell selection state, the second set of information added to the report; and while being in a camped normally state on a cell: logging (1003) measurement information related to an evaluated best cell as the report and/or responsive to a current cell not being the best cell, logging a reason for not camping on the best cell as the report; and transmit (1005) the report towards a network node.
33. The computer program product of Claim 32 wherein the non-transitory storage medium includes further program code whereby execution of the further program code causes the communication device to perform according to any of Claims 2-19.
34. A network node (700, 1710A, 1710B, 1900, 2104, 2108A, 2108B, 2204) adapted to: transmit (1601) at least one of: a first configuration that configures the communication device with a periodical logged measurements configuration including a first set of information while in a camped on any cell state; and a second configuration that configures the communication device with a periodical logged measurements configuration including a second set of information while in the any cell selection state; and receive (1603) a report having logged at least one of: the first set of information when the communication device was in the camped on any cell state; and the second set of information when the communication device was in the any cell selection state.
35. The network node of Claim 34 wherein the communication device is adapted to perform according to any of Claims 21-25.
36. A network node (700, 1710A, 1710B, 1900, 2104, 2108A, 2108B, 2204) comprising: processing circuitry (703, 1802, 2112); and memory (705, 1810) coupled with the processing circuitry, wherein the memory includes instructions that when executed by the processing circuitry causes the network node to: transmit (1601) at least one of: a first configuration that configures the communication device with a periodical logged measurements configuration including a first set of information while in a camped on any cell state; and a second configuration that configures the communication device with a periodical logged measurements configuration including a second set of information while in the any cell selection state; and receive (1603) a report having logged at least one of: the first set of information when the communication device was in the camped on any cell state; and the second set of information when the communication device was in the any cell selection state.
37. The network node of Claim 36 wherein the memory includes further instructions that when executed by the processing circuitry causes the network node to perform according to any of Claims 21-25
38. A computer program comprising program code to be executed by processing circuitry (703, 1902) of a radio access network, RAN, node (700, 1710A, 1710B, 1900, 2104, 2108A, 2108B, 2204), whereby execution of the program code causes the RAN node (700, 1710A, 1710B, 1900, 2104, 2108A, 2108B, 2204) to: transmit (1601) at least one of: a first configuration that configures the communication device with a periodical logged measurements configuration including a first set of information while in a camped on any cell state; and a second configuration that configures the communication device with a periodical logged measurements configuration including a second set of information while in the any cell selection state; and receive (1603) a report having logged at least one of: the first set of information when the communication device was in the camped on any cell state; and the second set of information when the communication device was in the any cell selection state.
39. The computer program of Claim 38 comprising further program code whereby execution of the further program code causes the network node to perform according to any of Claims 21- 25.
40. A computer program product comprising a non-transitory storage medium including program code to be executed by processing circuitry (703, 1902) of a radio access network, RAN, node (700, 1710A, 1710B, 1900, 2104, 2108A, 2108B, 2204), whereby execution of the program code causes the RAN node (700, 1710A, 1710B, 1900, 2104, 2108A, 2108B, 2204) to: transmit (1601) at least one of: a first configuration that configures the communication device with a periodical logged measurements configuration including a first set of information while in a camped on any cell state; and a second configuration that configures the communication device with a periodical logged measurements configuration including a second set of information while in the any cell selection state; and receive (1603) a report having logged at least one of: the first set of information when the communication device was in the camped on any cell state; and the second set of information when the communication device was in the any cell selection state.
41. The computer program product of Claim 40 wherein the non-transitory storage medium includes further program code whereby execution of the further program code causes the network node to perform according to any of Claims 21-25.
80
PCT/IB2022/058730 2021-09-22 2022-09-15 Enhancements of logged mdt report WO2023047255A1 (en)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US202163247087P 2021-09-22 2021-09-22
US63/247,087 2021-09-22
US202163248794P 2021-09-27 2021-09-27
US63/248,794 2021-09-27

Publications (1)

Publication Number Publication Date
WO2023047255A1 true WO2023047255A1 (en) 2023-03-30

Family

ID=83558240

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2022/058730 WO2023047255A1 (en) 2021-09-22 2022-09-15 Enhancements of logged mdt report

Country Status (1)

Country Link
WO (1) WO2023047255A1 (en)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130196650A1 (en) * 2010-10-01 2013-08-01 Nec Corporation Radio communication system and method, radio terminal, radio base station, and operation administration and maintenance server device
US20170105136A1 (en) * 2014-04-15 2017-04-13 Telefonaktiebolaget Lm Ericsson (Publ) Technique for Event Reporting
WO2020198274A1 (en) * 2019-03-28 2020-10-01 Kyocera Corporation Inactive mdt log with inactive duration
WO2021012261A1 (en) * 2019-07-25 2021-01-28 Zte Corporation Reporting measurements for minimization of driving test in wireless communication
AU2020220897A1 (en) * 2019-02-15 2021-09-16 Huawei Technologies Co., Ltd. Information reporting method and apparatus, and device

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130196650A1 (en) * 2010-10-01 2013-08-01 Nec Corporation Radio communication system and method, radio terminal, radio base station, and operation administration and maintenance server device
US20170105136A1 (en) * 2014-04-15 2017-04-13 Telefonaktiebolaget Lm Ericsson (Publ) Technique for Event Reporting
AU2020220897A1 (en) * 2019-02-15 2021-09-16 Huawei Technologies Co., Ltd. Information reporting method and apparatus, and device
WO2020198274A1 (en) * 2019-03-28 2020-10-01 Kyocera Corporation Inactive mdt log with inactive duration
WO2021012261A1 (en) * 2019-07-25 2021-01-28 Zte Corporation Reporting measurements for minimization of driving test in wireless communication

Non-Patent Citations (5)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Radio Resource Control (RRC) protocol specification (Release 16)", 21 September 2021 (2021-09-21), XP052055911, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG2_RL2/Specifications/202109_draft_specs_after_RAN_93/Draft_38331-g60.docx> [retrieved on 20210921] *
3GPP TS 22.261
3GPP TS 38.304
3GPP TS37.320
3GPP TS38.331

Similar Documents

Publication Publication Date Title
US11792693B2 (en) Methods and apparatuses for redirecting users of multimedia priority services
WO2023012705A1 (en) Random access partitioning and random access report
WO2023113674A1 (en) User equipment (ue) operation with base station energy-saving configuration
WO2023047255A1 (en) Enhancements of logged mdt report
US20240172074A1 (en) Handling of User Equipment (UE) Context Information after Inter-System Handover
EP4371340A1 (en) Access control for dual connectivity
WO2023095037A1 (en) Logged mdt reporting involving inter-rat mobility
WO2024079717A1 (en) Reporting of qoe reports to the sn
WO2024035311A1 (en) Minimization of drive tests configuration scope for different network types
EP4381777A1 (en) Signalling based minimization of drive test configuration availability
EP4381892A1 (en) Reporting ue-initiated network release
WO2024043825A1 (en) Methods and apparatus for including information concerning the selected cell (suitable or acceptable cell) in a failure report
WO2024079721A1 (en) Non-public network (npn) id check to delete the son reports at the user equipment
WO2022264090A1 (en) Logging and reporting of aerial ue-specific information
EP4374658A1 (en) Indicating handover-persistent release preference
WO2024144446A1 (en) Control plane optimization during amf change
WO2023014255A1 (en) Event-based qoe configuration management
WO2024107093A1 (en) Quality of experience and radio access network visible quality of experience reporting upon radio link failures in new radio dual connectivity
WO2023153975A1 (en) Methods and devives for conditional inclusion of random access information in secondary cell group (scg) failure information n
WO2024035310A1 (en) Minimization drive test measurements area configuration for non-public networks
WO2023131929A1 (en) Location information provisioning
WO2023132782A1 (en) Supervision timers for successful handover reporting
WO2023277764A2 (en) Handling of secondary node (sn) configurations during multi-rat dual connectivity (mr-dc) release
WO2023166129A1 (en) Handling of establishment causes in sidelink relay scenarios
WO2024038116A1 (en) Signaling extended reality information

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: 22783568

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE