WO2023068977A1 - Rapport de mesurage de mdt pour équipements utilisateurs se trouvant dans n'importe quel état de sélection de cellule - Google Patents

Rapport de mesurage de mdt pour équipements utilisateurs se trouvant dans n'importe quel état de sélection de cellule Download PDF

Info

Publication number
WO2023068977A1
WO2023068977A1 PCT/SE2022/050822 SE2022050822W WO2023068977A1 WO 2023068977 A1 WO2023068977 A1 WO 2023068977A1 SE 2022050822 W SE2022050822 W SE 2022050822W WO 2023068977 A1 WO2023068977 A1 WO 2023068977A1
Authority
WO
WIPO (PCT)
Prior art keywords
serving cell
mdt
cell
mdt measurement
measurement report
Prior art date
Application number
PCT/SE2022/050822
Other languages
English (en)
Inventor
Sakib BIN REDHWAN
Pradeepa Ramachandra
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 WO2023068977A1 publication Critical patent/WO2023068977A1/fr

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

Definitions

  • Example embodiments of this disclosure relate to minimization of drive tests (MDT) measurement, such as for example reporting a MDT measurement and/or processing a MDT measurement report.
  • MDT drive tests
  • MDT was standardized for NR in Rel-16 to reduce the amount of drive tests performed manually. It is a UE assisted framework where network measurements are collected by both IDLE/INACTIVE and RRC Connected UE(s) in order to aid the network in gathering valuable information. It has been specified for both Long Term Evolution (LTE) and New Radio (NR) in 3GPP TS 37.320 V16.5.0. In general, there are two types of MDT measurement logging, i.e., Logged MDT and Immediate MDT.
  • a User Eguipment (UE) in RRCJDLE/RRCJNACTIVE Radio Resource Control (RRC) state is configured to perform periodical and event triggered MDT logging after receiving MDT configurations from the network.
  • the UE shall report, in a logged MDT report, the downlink (DL) pilot strength measurements (Reference Signal Received Power, RSRP, and Reference Signal Received Quality, RSRQ) together with time information, detailed location information if available, and Wireless Local Area Network (WLAN) and/or Bluetooth information (e.g. information on WLAN and/or Bluetooth beacons detected by the UE) to the network when it is in RRC_CONNECTED state.
  • DL downlink
  • RSRP Reference Signal Received Power
  • RSRQ Reference Signal Received Quality
  • WLAN Wireless Local Area Network
  • Bluetooth information e.g. information on WLAN and/or Bluetooth beacons detected by the UE
  • the logged MDT report is sent via a RRC UEinformationResponse message from UE to the network in response to a RRC UElnformationRequest message from the network to UE.
  • the DL pilot strength measurement of Logged MDT is collected based on the existing measurements reguired for cell reselection purpose, without the UE performing additional measurements.
  • UE For Periodical Logged MDT, UE receives the MDT configurations including logginginterval and loggingduration 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 RRCJDLE.
  • An example timeline for MDT logging is shown in Figure 1.
  • the UE receives eventType and logginginterval from the network.
  • the UE logs the measurement reports at every logginginterval if an event configured in eventType is satisfied.
  • the UE If the UE cannot find a cell that belongs to suitable cell or acceptable cell, it declares itself being in any cell selection state. Further details are available in 3GPP TS 38.304, V16.5.0.
  • a first example aspect of this disclosure provides a method performed by a User Equipment (UE) for reporting a Minimization of Drive Tests (MDT) measurement, wherein the UE is configured with a MDT configuration.
  • the method comprises logging a MDT measurement, wherein, if the UE is not required to log measurements for a last serving cell for the UE, including, in a MDT measurement report that includes the logged MDT measurement, an indication that the UE is not required to log measurements for the last serving cell for the UE for the logged MDT measurement, and wherein the indication comprises at least one predetermined value in at least one measurement field and/or serving cell identity field in the MDT measurement report.
  • Another example aspect of this disclosure provides a method performed by a network node for processing a Minimization of Drive Test (MDT) measurement report.
  • the method comprises receiving the MDT measurement report from a UE, and determining, based on an indication in the MDT measurement report, that the UE is not required to log measurements for a last serving cell for the UE for a MDT measurement in the MDT measurement report, wherein the indication in the MDT measurement report comprises at least one predetermined value in at least one measurement field and/or serving cell identity field in the MDT measurement report.
  • MDT Minimization of Drive Test
  • a further example aspect of this disclosure provides apparatus in a User Equipment (UE) for reporting a Minimization of Drive Tests (MDT) measurement, wherein the UE is configured with a MDT configuration.
  • the apparatus comprises a processor and a memory.
  • the memory contains instructions executable by the processor such that the apparatus is operable to log a MDT measurement, and if the UE is not required to log measurements for a last serving cell for the UE, include, in a MDT measurement report that includes the logged MDT measurement, an indication that the UE is not required to log measurements for the last serving cell for the UE for the logged MDT measurement, and wherein the indication comprises at least one predetermined value in at least one measurement field and/or serving cell identity field in the MDT measurement report.
  • a still further example aspect of this disclosure provides apparatus in a network node for processing a Minimization of Drive Test (MDT) measurement report.
  • the apparatus comprises a processor and a memory.
  • the memory contains instructions executable by the processor such that the apparatus is operable to receive the MDT measurement report from a UE, and determine, based on an indication in the MDT measurement report, that the UE is not required to log measurements for a last serving cell for the UE for a MDT measurement in the MDT measurement report, wherein the indication in the MDT measurement report comprises at least one predetermined value in at least one measurement field and/or serving cell identity field in the MDT measurement report.
  • An additional example aspect of this disclosure provides apparatus in a User Equipment (UE) for reporting a Minimization of Drive Tests (MDT) measurement, wherein the UE is configured with a MDT configuration.
  • the apparatus is configured to log a MDT measurement, and if the UE is not required to log measurements for a last serving cell for the UE, include, in a MDT measurement report that includes the logged MDT measurement, an indication that the UE is not required to log measurements for the last serving cell for the UE for the logged MDT measurement, and wherein the indication comprises at least one predetermined value in at least one measurement field and/or serving cell identity field in the MDT measurement report.
  • the apparatus is configured to receive the MDT measurement report from a UE, and determine, based on an indication in the MDT measurement report, that the UE is not required to log measurements for a last serving cell for the UE for a MDT measurement in the MDT measurement report, wherein the indication in the MDT measurement report comprises at least one predetermined value in at least one measurement field and/or serving cell identity field in the MDT measurement report.
  • MDT Minimization of Drive Test
  • Figure 1 illustrates an example of a timeline for MDT logging
  • FIG. 2 depicts a method performed by a User Equipment (UE) for reporting a Minimization of Drive Tests (MDT) measurement, wherein the UE is configured with a MDT configuration, in accordance with particular embodiments;
  • UE User Equipment
  • MDT Minimization of Drive Tests
  • FIG. 3 depicts a method performed by a network node for processing a Minimization of Drive Test (MDT) measurement report, in accordance with particular embodiments;
  • MDT Minimization of Drive Test
  • Figure 4 shows an example of a communication system in accordance with some embodiments
  • Figure 5 shows a UE in accordance with some embodiments
  • Figure 6 shows a network node in accordance with some embodiments
  • FIG. 7 is a block diagram of a host in accordance with various aspects described herein;
  • Figure 8 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized.
  • Figure 9 shows a communication diagram of a host communicating via a network node with a UE over a partially wireless connection in accordance with some embodiments.
  • Nodes that communicate using the air interface also have suitable radio communications circuitry.
  • the technology can additionally be considered to be embodied entirely within any form of computer-readable memory, such as solid-state memory, magnetic disk, or optical disk containing an appropriate set of computer instructions that would cause a processor to carry out the techniques described herein.
  • Hardware implementation may include or encompass, without limitation, digital signal processor (DSP) hardware, a reduced instruction set processor, hardware (e.g. digital or analogue) circuitry including but not limited to application specific integrated circuit(s) (ASIC) and/or field programmable gate array(s) (FPGA(s)), and (where appropriate) state machines capable of performing such functions.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • reporting serving cell information is captured in the following procedural text excerpt from TS38.331 , V16.5.0, section 5.5a.3:
  • the measurements related to last suitable are logged if the last suitable cell is part of the configured plmn-ldentityList and/or areaconfig. Otherwise, UE doesn’t log the cell identity and measurements related to that cell. However, UE logs the indication anyCellSelectionDetected to indicate to network that it was in ‘any cell selection’ state. To support this RRC procedure, compatible ASN.1 structure like below is standardized.
  • LogMeasInfo-rl6 SEQUENCE ⁇ locationlnf o-rl 6 Locationlnf o-r!6 OPTIONAL, relativeTimeStanp-rl6 INTEGER ( 0. .7200) , servCellIdentity-rl6 CGI-Info-Logging-rl6 OPTIONAL, measResultServingCell-rl6 MeasResultServingCell-rl6 OPTIONAL, measResultNeighCells-rl6 SEQUENCE ⁇ measResultNeighCellListNR Meas Res ul tLi s tLogging2NR- r 16 OPTIONAL, measResultNeighCellListEUTRA MeasResultList2EUTRA-rl6 OPTIONAL ⁇ , anyCellSelectionDetected-rl6 ENUMERATED ⁇ true ⁇ OPTIONAL,
  • logging of measurements related to serving cell is optional for a UE, it may omit logging the measurements if the serving cell (last suitable cell in this example) is not part of plmn-ldentityList, or not part of areaConfig if the latter is configured.
  • the UE behaviour is proposed to be similar, i.e. the UE would log an indication of anyCellSelectionDetected and include serving cell measurements if the latter is allowed.
  • logging of serving cell measurements is mandatory for a UE served by a LTE network.
  • the UE in “any cell selection” state it is not possible for the UE in “any cell selection” state to omit last suitable cell measurements for a logging instance if the last suitable cell is not part of the plmn-ldentityList, or not part of areaConfig if the latter is configured.
  • Certain example embodiments of this disclosure may provide solutions to these or other challenges. For example, some examples of this disclosure may allow the UE to indicate each invalid serving cell related measurement sample in a Logged MDT report. The network can in some examples ignore the samples as indicated by the UE.
  • Examples of this disclosure propose a method performed by a user equipment (UE) as part of logged MDT report to indicate network node regarding invalid measurement samples associated to serving cell information.
  • the method comprises the following steps. First, a logged MDT configuration is received from a network node. Then, the logging condition from the received MDT configuration is evaluated. For example, the logging condition may indicate that UE may log if it is in ‘any cell selection’ state, and/or UE may log if it is in ‘camped on any cell’ state. The method then comprises evaluating if the serving cell can be logged inside logged MDT report for a given logging instance.
  • the UE logs a value for the serving cell ID and the associated serving cell measurements for that logging instance if the evaluation determines the serving cell is not allowed to be logged.
  • the UE may put a random number at least in the serving cell identity and related measurement field.
  • the UE includes flags indicating the serving cell measurements are invalid.
  • the UE includes individual indicator flag for each logging instance for which the serving cell measurements are invalid.
  • the UE may put a pre-configured value in at least one of the serving cell identity and related measurement field.
  • the method comprises transmitting the logged MDT report including measurements and indication flags to network node, if requested.
  • a logged MDT configuration may be for example a MDT configuration (according to 3GPP TS 37.320 V16.5.0 for example) that comprises or includes a configuration for logged MDT measurements, or may be for example a part of a MDT configuration where the part relates to logged MDT measurements.
  • Examples of this disclosure further propose a method performed by a network node to evaluate and discard measurement samples received in a logged MDT report, if indicated by the UE.
  • the method comprises configuring a UE with a logged MDT configuration, and receiving logged MDT report from the UE.
  • the method comprises evaluating the presence of an indicator flag for some logging instance in the received logged MDT report indicating that the serving cell measurements are invalid.
  • the method comprises ignoring serving cell measurements for the associated logging instances.
  • the network may ignore the serving cell measurements for logging instances for which the indicator flag is present, and/or the network may ignore the serving cell measurements for logging instances for which at least one of the celllD and measurement value is equal to the pre-configured number.
  • inventions may provide one or more of the following technical advantage(s).
  • examples of this disclosure may allow the implementation of event triggered logged MDT configuration in network and UE under the constraints that UE must always log serving cell measurements.
  • Examples of this disclosure may enable the UE to tag individual invalid samples and network can discard those samples during its processing.
  • Figure 2 is a flow chart of an example of a method 200 in accordance with some embodiments.
  • Figure 2 depicts a method 200 performed by a User Equipment (UE) for reporting a Minimization of Drive Tests (MDT) measurement, wherein the UE is configured with a MDT configuration, in accordance with particular embodiments.
  • the method 200 may be performed by a UE or wireless device (e.g. the UE QQ112 or UE QQ200 as described later with reference to Figures 4 and 5 respectively).
  • the method begins at step 202 with logging a MDT measurement, wherein, if the UE is not required to log measurements for a last serving cell for the UE, including, in a MDT measurement report that includes the logged MDT measurement, an indication that the UE is not required to log measurements for the last serving cell for the UE for the logged MDT measurement, and wherein the indication comprises at least one predetermined value in at least one measurement field and/or serving cell identity field in the MDT measurement report.
  • the at least one predetermined value may comprise zero or all zeros in some examples.
  • the MDT configuration may comprise for example a logged MDT configuration and/or an event-driven MDT configuration.
  • the last serving cell for the UE may in some examples comprise a 4G or Long Term Evolution (LTE) cell.
  • LTE Long Term Evolution
  • the method 200 comprises determining whether the UE is not required to log measurements for a last serving cell for the UE. This may in some examples comprise determining whether the UE is not required to log measurements for the last serving cell for the UE from the MDT configuration. Additionally or alternatively, for example, this may comprise determining whether the UE is not permitted to log measurements for a last serving cell for the UE. Additionally or alternatively, for example, this may comprise determining whether the UE is not required to log measurements for the last serving cell for the UE comprises determining whether the last serving cell is in an area indicated by the MDT configuration. Determining that the UE is not required to log measurements for the last serving cell for the UE may comprise for example determining that the last serving cell for the UE is not in an area indicated by the MDT configuration.
  • the UE may in some examples be in an any cell selection state or a camped on any cell state.
  • the last serving cell for the UE may in some examples comprise one of the following:
  • the indication that the UE is not required to log measurements for the last serving cell for the UE may also in some examples comprise a flag indicating that the UE is not required to log measurements for the last serving cell for the UE.
  • the flag may be included for example in at least one measurement field and/or serving cell identity field in the MDT measurement report, or is included in a field other than a measurement field or a serving cell identity field.
  • the method 200 may comprise including, in the MDT measurement report, at least one random value in at least one measurement field and/or serving cell identity field in the MDT measurement report.
  • Logging the MDT measurement in some examples comprises determining that an event condition associated with the MDT measurement configuration has been fulfilled, and/or determining that a timer associated with the MDT measurement configuration has triggered or expired.
  • the indication that the UE is not required to log measurements for the last serving cell for the UE comprises an indication that the UE is not permitted to log measurements for the last serving cell for the UE.
  • the indication that the UE is not required to log measurements for the last serving cell for the UE may for example comprise, if the UE is not permitted to log measurements for a last serving cell for the UE, including, in the MDT measurement report, the indication that the UE is not permitted to log measurements for the last serving cell for the UE.
  • the MDT measurement report may in some examples be transmitted to a network node, and/or the MDT configuration may be received from the network node.
  • the method 200 may in some examples comprise including, in the logged MDT measurement, the indication that the UE is not required to log measurements for the last serving cell for the UE.
  • FIG 3 depicts a method performed by a network node for processing a Minimization of Drive Test (MDT) measurement report, in accordance with particular embodiments.
  • the method 300 may be performed by a network node (e.g. the network node QQ110 or network node QQ300 as described later with reference to Figures 4 and 6 respectively).
  • a network node e.g. the network node QQ110 or network node QQ300 as described later with reference to Figures 4 and 6 respectively.
  • the method begins at step 302 with receiving the MDT measurement report from a UE, and proceeds to step 304 with determining, based on an indication in the MDT measurement report, that the UE is not required to log measurements for a last serving cell for the UE for a MDT measurement in the MDT measurement report, wherein the indication in the MDT measurement report comprises at least one predetermined value in at least one measurement field and/or serving cell identity field in the MDT measurement report.
  • the MDT measurement is discarded. This may comprise for example discarding the indicated measurement field and/or serving cell identify field of the MDT measurement.
  • the at least one predetermined value comprises zero or all zeros in some examples.
  • the MDT configuration may comprises for example a logged MDT configuration and/or an event- driven MDT configuration.
  • the last serving cell for the UE may be for example a 4G or Long Term Evolution (LTE) cell.
  • LTE Long Term Evolution
  • the UE may be in an any cell selection state or a camped on any cell state.
  • the last serving cell for the UE may be one of the following:
  • the indication that the UE is not required to log measurements for the last serving cell for the UE for the MDT measurement may comprise a flag indicating that the UE is not required to log measurements for the last serving cell for the UE for the MDT measurement.
  • the flag may be included for example in at least one measurement field and/or serving cell identity field in the MDT measurement report, or is included in a field other than a measurement field or a serving cell identity field.
  • the indication that the UE is not required to log measurements for the last serving cell for the UE for the MDT measurement comprises an indication that the UE is not permitted to log measurements for the last serving cell for the UE for the MDT measurement.
  • the method 300 may comprise sending a MDT measurement configuration to the UE.
  • network node as used with examples of this disclosure may refer to any network node belonging to a wireless or fixed network and may refer to the same node or different network nodes.
  • the following particular examples may be non-limiting, illustrative examples of the methods, apparatus and/or features described above.
  • Examples of this disclosure propose a method performed by a user equipment (UE) as part of logged MDT report to indicate network node regarding invalid measurement samples associated to serving cell information.
  • An example method comprises the following steps:
  • the UE receives a logged MDT configuration from a network node.
  • UE evaluates the logging condition set by the network node. Some examples are: o UE may log if it is in “any cell selection” state. o UE may log if it is in “camped on any cell” state.
  • UE Upon evaluation for a given logging instance, if the UE determines that the last serving cell does not fulfill the criteria for logging, UE includes a value for serving cell measurements and serving cell ID in the respective fields for the logging instance.
  • the UE may include a random number in the cell identity and/or related measurement field. In such example embodiments, the UE may in some examples further include flags indicating the serving cell measurements are invalid. For each logging instance for which the serving cell measurements are invalid, UE may include said indicator flag indicating that the serving cell measurements should be ignored by the network.
  • the UE may include a pre-configured value, such as zero or all zeros, in at least one of the cell identity and/or related measurement field.
  • the UE may in some examples include a pre-configured value in cell identity field and a random value in related measurement field.
  • the UE may include a random value in cell identity field and a pre-configured value in the related measurement field, or may include a pre-configured value in both cell identity and related measurement field.
  • UE may report the logged MDT report to network node following standardized procedure.
  • Examples of this disclosure propose a method performed by a network node (e.g. a RAN node such as an eNodeB, or a core network node) to evaluate and discard measurement samples received in a logged MDT report, if indicated by the UE.
  • a network node e.g. a RAN node such as an eNodeB, or a core network node
  • An example method comprises the following steps:
  • Network node configures a UE to collect logged MDT report.
  • the configuration includes different conditions when UE is required to collect logged MDT report. For example:
  • Network receives logged MDT report from the UE using standardized methods.
  • Network evaluates if the UE has included indication for some logging instances in the received logged MDT report.
  • this is identified by the presence of the indicator flag for some logging instance in the received logged MDT report, the indicator flag indicating that the serving cell measurements are invalid.
  • this is identified by the UE including a pre-configured value of the cell identifier and the corresponding measurements for some logging instance in the received logged MDT report, the presence of the pre-configured value indicating that the serving cell measurements are invalid.
  • network may ignore the cell measurements for logging instances for which the indicator flag mentioned above is present.
  • network may ignore the cell measurements for logging instances for which at least one of the celllD and measurement value is equal to the preconfigured number.
  • network may ignore the cell measurements for logging instances for which the cell identity is equal to a pre-configured value.
  • network may ignore the cell measurements for logging instances for which the measurement is equal to a pre-configured value.
  • network may ignore the cell measurements for logging instances for which the cell identity and measurement is equal to a pre-configured value.
  • VarLogMeasReport when adding a logged measurement entry in VarLogMeasReport, include the fields in accordance with the following:
  • VarLoqMeasConfio 6> set the servCellldentity to indicate global cell identity of the last logged cell that the UE was camping on;
  • the UElnformationResponse message is used by the UE to transfer the information requested by the E-UTRAN.
  • Figure 4 shows an example of a communication system QQ100 in accordance with some embodiments.
  • the communication system QQ100 includes a telecommunication network QQ102 that includes an access network QQ104, such as a radio access network (RAN), and a core network QQ106, which includes one or more core network nodes QQ108.
  • the access network QQ104 includes one or more access network nodes, such as network nodes QQ110a and QQ110b (one or more of which may be generally referred to as network nodes QQ110), 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 QQ110 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs QQ112a, QQ112b, QQ112c, and QQ112d (one or more of which may be generally referred to as UEs QQ112) to the core network QQ106 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 QQ100 may include any number of wired or wireless networks, network nodes, UEs, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.
  • the communication system QQ100 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.
  • the UEs QQ112 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 QQ110 and other communication devices.
  • the network nodes QQ110 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs QQ112 and/or with other network nodes or equipment in the telecommunication network QQ102 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 QQ102.
  • the core network QQ106 connects the network nodes QQ110 to one or more hosts, such as host QQ116. 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 QQ106 includes one more core network nodes (e.g., core network node QQ108) 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 QQ108.
  • Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and/or a User Plane Function (UPF).
  • MSC Mobile Switching Center
  • MME Mobility Management Entity
  • HSS Home Subscriber Server
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • AUSF Authentication Server Function
  • SIDF Subscription Identifier De-concealing function
  • UDM Unified Data Management
  • SEPP Security Edge Protection Proxy
  • NEF Network Exposure Function
  • UPF User Plane Function
  • the host QQ116 may be under the ownership or control of a service provider other than an operator or provider of the access network QQ104 and/or the telecommunication network QQ102, and may be operated by the service provider or on behalf of the service provider.
  • the host QQ116 may host a variety of applications to provide one or more services. Examples of such applications include the provision of live and/or pre-recorded audio/video content, data collection services, for example, 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 QQ100 of Figure 4 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 QQ102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network QQ102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network QQ102. For example, the telecommunications network QQ102 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and/or Massive Machine Type Communication (mMTC)ZMassive loT services to yet further UEs.
  • URLLC Ultra Reliable Low Latency Communication
  • eMBB Enhanced Mobile Broadband
  • mMTC Massive Machine Type Communication
  • the UEs QQ112 are configured to transmit and/or receive information without direct human interaction.
  • a UE may be designed to transmit information to the access network QQ104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network QQ104.
  • 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 QQ114 communicates with the access network QQ104 to facilitate indirect communication between one or more UEs (e.g., UE QQ112c and/or QQ112d) and network nodes (e.g., network node QQ110b).
  • the hub QQ114 may be a controller, router, a content source and analytics node, or any of the other communication devices described herein regarding UEs.
  • the hub QQ114 may be a broadband router enabling access to the core network QQ106 for the UEs.
  • the hub QQ114 may be a controller that sends commands or instructions to one or more actuators in the UEs.
  • the hub QQ114 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 QQ114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub QQ114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub QQ114 then provides to the UE either directly, after performing local processing, and/or after adding additional local content.
  • the hub QQ114 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 QQ114 may have a constant/persistent or intermittent connection to the network node QQ110b.
  • the hub QQ114 may also allow for a different communication scheme and/or schedule between the hub QQ114 and UEs (e.g., UE QQ112c and/or QQ112d), and between the hub QQ114 and the core network QQ106.
  • the hub QQ114 is connected to the core network QQ106 and/or one or more UEs via a wired connection.
  • the hub QQ114 may be configured to connect to an M2M service provider over the access network QQ104 and/or to another UE over a direct connection.
  • UEs may establish a wireless connection with the network nodes QQ110 while still connected via the hub QQ114 via a wired or wireless connection.
  • the hub QQ114 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 QQ110b.
  • the hub QQ114 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node QQ110b, but which is additionally capable of operating as a communication start and/or end point for certain data channels.
  • a UE refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other UEs.
  • 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 camera, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptopmounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle-mounted or vehicle embedded/integrated wireless device, etc.
  • VoIP voice over IP
  • PDA personal digital assistant
  • LME laptop-embedded equipment
  • LME laptopmounted equipment
  • CPE wireless customer-premise equipment
  • UEs identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-loT) UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.
  • 3GPP 3rd Generation Partnership Project
  • NB-loT 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
  • the UE QQ200 includes processing circuitry QQ202 that is operatively coupled via a bus QQ204 to an input/output interface QQ206, a power source QQ208, a memory QQ210, a communication interface QQ212, and/or any other component, or any combination thereof.
  • Certain UEs may utilize all or a subset of the components shown in Figure 5. 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 QQ202 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 QQ210.
  • the processing circuitry QQ202 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 QQ202 may include multiple central processing units (CPUs).
  • the processing circuitry QQ202 may be operable to provide, either alone or in conjunction with other UE QQ200 components, such as the memory QQ210, UE QQ200 functionality.
  • the processing circuitry QQ202 may be configured to cause the UE QQ202 to perform the methods as described with reference to Figure 2.
  • the input/output interface QQ206 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 QQ200.
  • 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 QQ208 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 QQ208 may further include power circuitry for delivering power from the power source QQ208 itself, and/or an external power source, to the various parts of the UE QQ200 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source QQ208.
  • Power circuitry may perform any formatting, converting, or other modification to the power from the power source QQ208 to make the power suitable for the respective components of the UE QQ200 to which power is supplied.
  • the memory QQ210 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth.
  • the memory QQ210 includes one or more application programs QQ214, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data QQ216.
  • the memory QQ210 may store, for use by the UE QQ200, any of a variety of various operating systems or combinations of operating systems.
  • the memory QQ210 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
  • the UICC may for example be an embedded UICC (eUlCC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’
  • the memory QQ210 may allow the UE QQ200 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 QQ210, which may be or comprise a device-readable storage medium.
  • the processing circuitry QQ202 may be configured to communicate with an access network or other network using the communication interface QQ212.
  • the communication interface QQ212 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna QQ222.
  • the communication interface QQ212 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 QQ218 and/or a receiver QQ220 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth).
  • the transmitter QQ218 and receiver QQ220 may be coupled to one or more antennas (e.g., antenna QQ222) and may share circuit components, software or firmware, or alternatively be implemented separately.
  • communication functions of the communication interface QQ212 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.
  • CDMA Code Division Multiplexing Access
  • WCDMA Wideband Code Division Multiple Access
  • GSM Global System for Mobile communications
  • LTE Long Term Evolution
  • NR New Radio
  • UMTS Worldwide Interoperability for Microwave Access
  • WiMax Ethernet
  • TCP/IP transmission control protocol/internet protocol
  • SONET synchronous optical networking
  • ATM Asynchronous Transfer Mode
  • QUIC Hypertext Transfer Protocol
  • HTTP Hypertext Transfer Protocol
  • a UE may provide an output of data captured by its sensors, through its communication interface QQ212, 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 controls 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 devices which are or which are 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
  • AR Augmented
  • a UE may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another UE and/or a network node.
  • the UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device.
  • the UE may implement the 3GPP NB-loT 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. 6 shows a network node QQ300 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 QQ300 includes processing circuitry QQ302, a memory QQ304, a communication interface QQ306, and a power source QQ308, and/or any other component, or any combination thereof.
  • the network node QQ300 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 QQ300 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.
  • each unique NodeB and RNC pair may in some instances be considered a single separate network node.
  • the network node QQ300 may be configured to support multiple radio access technologies (RATs).
  • RATs radio access technologies
  • some components may be duplicated (e.g., separate memory QQ304 for different RATs) and some components may be reused (e.g., a same antenna QQ310 may be shared by different RATs).
  • the network node QQ300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node QQ300, 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 QQ300.
  • RFID Radio Frequency Identification
  • the processing circuitry QQ302 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 QQ300 components, such as the memory QQ304, network node QQ300 functionality.
  • the processing circuitry QQ302 may be configured to cause the network node to perform the methods as described with reference to Figure 3.
  • the processing circuitry QQ302 includes a system on a chip (SOC). In some embodiments, the processing circuitry QQ302 includes one or more of radio frequency (RF) transceiver circuitry QQ312 and baseband processing circuitry QQ314. In some embodiments, the radio frequency (RF) transceiver circuitry QQ312 and the baseband processing circuitry QQ314 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 QQ312 and baseband processing circuitry QQ314 may be on the same chip or set of chips, boards, or units.
  • SOC system on a chip
  • the processing circuitry QQ302 includes one or more of radio frequency (RF) transceiver circuitry QQ312 and baseband processing circuitry QQ314.
  • the radio frequency (RF) transceiver circuitry QQ312 and the baseband processing circuitry QQ314 may be on separate chips (or sets of chips
  • the memory QQ304 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 QQ302.
  • 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
  • the memory QQ304 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 QQ302 and utilized by the network node QQ300.
  • the memory QQ304 may be used to store any calculations made by the processing circuitry QQ302 and/or any data received via the communication interface QQ306.
  • the processing circuitry QQ302 and memory QQ304 is integrated.
  • the communication interface QQ306 is used in wired or wireless communication of signaling and/or data between a network node, access network, and/or UE.
  • the communication interface QQ306 comprises port(s)/terminal(s) QQ316 to send and receive data, for example to and from a network over a wired connection.
  • the communication interface QQ306 also includes radio front-end circuitry QQ318 that may be coupled to, or in certain embodiments a part of, the antenna QQ310.
  • Radio front-end circuitry QQ318 comprises filters QQ320 and amplifiers QQ322.
  • the radio front-end circuitry QQ318 may be connected to an antenna QQ310 and processing circuitry QQ302.
  • the radio front-end circuitry may be configured to condition signals communicated between antenna QQ310 and processing circuitry QQ302.
  • the radio front-end circuitry QQ318 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 QQ318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters QQ320 and/or amplifiers QQ322.
  • the radio signal may then be transmitted via the antenna QQ310.
  • the antenna QQ310 may collect radio signals which are then converted into digital data by the radio front-end circuitry QQ318.
  • the digital data may be passed to the processing circuitry QQ302.
  • the communication interface may comprise different components and/or different combinations of components.
  • the network node QQ300 does not include separate radio front-end circuitry QQ318, instead, the processing circuitry QQ302 includes radio frontend circuitry and is connected to the antenna QQ310. Similarly, in some embodiments, all or some of the RF transceiver circuitry QQ312 is part of the communication interface QQ306. In still other embodiments, the communication interface QQ306 includes one or more ports or terminals QQ316, the radio front-end circuitry QQ318, and the RF transceiver circuitry QQ312, as part of a radio unit (not shown), and the communication interface QQ306 communicates with the baseband processing circuitry QQ314, which is part of a digital unit (not shown).
  • the antenna QQ310 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals.
  • the antenna QQ310 may be coupled to the radio frontend circuitry QQ318 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly.
  • the antenna QQ310 is separate from the network node QQ300 and connectable to the network node QQ300 through an interface or port.
  • the antenna QQ310, communication interface QQ306, and/or the processing circuitry QQ302 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.
  • the antenna QQ310, the communication interface QQ306, and/or the processing circuitry QQ302 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 QQ308 provides power to the various components of network node QQ300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component).
  • the power source QQ308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node QQ300 with power for performing the functionality described herein.
  • the network node QQ300 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 QQ308.
  • the power source QQ308 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 QQ300 may include additional components beyond those shown in Figure 6 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 QQ300 may include user interface equipment to allow input of information into the network node QQ300 and to allow output of information from the network node QQ300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node QQ300.
  • FIG. 7 is a block diagram of a host QQ400, which may be an embodiment of the host QQ116 of Figure 4, in accordance with various aspects described herein.
  • the host QQ400 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 QQ400 may provide one or more services to one or more UEs.
  • the host QQ400 includes processing circuitry QQ402 that is operatively coupled via a bus QQ404 to an input/output interface QQ406, a network interface QQ408, a power source QQ410, and a memory QQ412.
  • 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 5 and 6, such that the descriptions thereof are generally applicable to the corresponding components of host QQ400.
  • the memory QQ412 may include one or more computer programs including one or more host application programs QQ414 and data QQ416, which may include user data, e.g., data generated by a UE for the host QQ400 or data generated by the host QQ400 for a UE.
  • Embodiments of the host QQ400 may utilize only a subset or all of the components shown.
  • the host application programs QQ414 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (WC), 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 QQ414 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 QQ400 may select and/or indicate a different host for over-the-top services for a UE.
  • the host application programs QQ414 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.
  • HLS HTTP Live Streaming
  • RTMP Real-Time Messaging Protocol
  • RTSP Real-Time Streaming Protocol
  • MPEG-DASH Dynamic Adaptive Streaming over HTTP
  • FIG. 8 is a block diagram illustrating a virtualization environment QQ500 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 QQ500 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
  • hardware nodes such as a hardware computing device that operates as a network node, UE, core network node, or host.
  • the virtual node does not require radio connectivity (e.g., a core network node or host)
  • the node may be entirely virtualized.
  • Applications QQ502 (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 QQ504 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 QQ506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs QQ508a and QQ508b (one or more of which may be generally referred to as VMs QQ508), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein.
  • the virtualization layer QQ506 may present a virtual operating platform that appears like networking hardware to the VMs QQ508.
  • the VMs QQ508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer QQ506.
  • Different embodiments of the instance of a virtual appliance QQ502 may be implemented on one or more of VMs QQ508, and the implementations may be made in different ways.
  • Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.
  • NFV network function virtualization
  • a VM QQ508 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 QQ508, and that part of hardware QQ504 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 QQ508 on top of the hardware QQ504 and corresponds to the application QQ502.
  • Hardware QQ504 may be implemented in a standalone network node with generic or specific components. Hardware QQ504 may implement some functions via virtualization. Alternatively, hardware QQ504 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 QQ510, which, among others, oversees lifecycle management of applications QQ502. In some embodiments, hardware QQ504 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 QQ512 which may alternatively be used for communication between hardware nodes and radio units.
  • Figure 9 shows a communication diagram of a host QQ602 communicating via a network node QQ604 with a UE QQ606 over a partially wireless connection in accordance with some embodiments.
  • host QQ602 Like host QQ400, embodiments of host QQ602 include hardware, such as a communication interface, processing circuitry, and memory.
  • the host QQ602 also includes software, which is stored in or accessible by the host QQ602 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 QQ606 connecting via an over-the-top (OTT) connection QQ650 extending between the UE QQ606 and host QQ602.
  • OTT over-the-top
  • a host application may provide user data which is transmitted using the OTT connection QQ650.
  • the network node QQ604 includes hardware enabling it to communicate with the host QQ602 and UE QQ606.
  • the connection QQ660 may be direct or pass through a core network (like core network QQ106 of Figure 4) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks.
  • an intermediate network may be a backbone network or the Internet.
  • the UE QQ606 includes hardware and software, which is stored in or accessible by UE QQ606 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 QQ606 with the support of the host QQ602.
  • 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 QQ606 with the support of the host QQ602.
  • an executing host application may communicate with the executing client application via the OTT connection QQ650 terminating at the UE QQ606 and host QQ602.
  • 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 QQ650 may transfer both the request data and the user data.
  • the UE's client application may interact with
  • the OTT connection QQ650 may extend via a connection QQ660 between the host QQ602 and the network node QQ604 and via a wireless connection QQ670 between the network node QQ604 and the UE QQ606 to provide the connection between the host QQ602 and the UE QQ606.
  • the connection QQ660 and wireless connection QQ670, over which the OTT connection QQ650 may be provided, have been drawn abstractly to illustrate the communication between the host QQ602 and the UE QQ606 via the network node QQ604, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • the host QQ602 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 QQ606.
  • the user data is associated with a UE QQ606 that shares data with the host QQ602 without explicit human interaction.
  • the host QQ602 initiates a transmission carrying the user data towards the UE QQ606.
  • the host QQ602 may initiate the transmission responsive to a request transmitted by the UE QQ606.
  • the request may be caused by human interaction with the UE QQ606 or by operation of the client application executing on the UE QQ606.
  • the transmission may pass via the network node QQ604, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step QQ612, the network node QQ604 transmits to the UE QQ606 the user data that was carried in the transmission that the host QQ602 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step QQ614, the UE QQ606 receives the user data carried in the transmission, which may be performed by a client application executed on the UE QQ606 associated with the host application executed by the host QQ602. In some examples, the UE QQ606 executes a client application which provides user data to the host QQ602.
  • the user data may be provided in reaction or response to the data received from the host QQ602. Accordingly, in step QQ616, the UE QQ606 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 QQ606. Regardless of the specific manner in which the user data was provided, the UE QQ606 initiates, in step QQ618, transmission of the user data towards the host QQ602 via the network node QQ604.
  • step QQ620 in accordance with the teachings of the embodiments described throughout this disclosure, the network node QQ604 receives user data from the UE QQ606 and initiates transmission of the received user data towards the host QQ602. In step QQ622, the host QQ602 receives the user data carried in the transmission initiated by the UE QQ606.
  • One or more of the various embodiments improve the performance of OTT services provided to the UE QQ606 using the OTT connection QQ650, in which the wireless connection QQ670 forms the last segment. More precisely, the teachings of these embodiments may improve the flexibility of UE behavior and thereby provide benefits such as for example allowing features of NR standards to be applied to LTE.
  • factory status information may be collected and analyzed by the host QQ602.
  • the host QQ602 may process audio and video data which may have been retrieved from a UE for use in creating maps.
  • the host QQ602 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights).
  • the host QQ602 may store surveillance video uploaded by a UE.
  • the host QQ602 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 QQ602 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 QQ602 and/or UE QQ606.
  • sensors (not shown) may be deployed in or in association with other devices through which the OTT connection QQ650 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 QQ650 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node QQ604. 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 QQ602.
  • the measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection QQ650 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.

Landscapes

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

Abstract

Des procédés et un appareil sont divulgués, comprenant, dans un exemple, un procédé exécuté par un équipement utilisateur (UE) pour rapporter un mesurage de minimisation des essais de conduite (MDT). L'UE est configuré avec une configuration MDT. Le procédé comprend la consignation d'un mesurage de MDT 5, dans lequel, s'il n'est pas demandé à l'UE de consigner des mesurages pour une dernière cellule de desserte pour l'UE, comprenant, dans un rapport de mesurage de MDT qui comprend le mesurage de MDT consigné, une indication selon laquelle il n'est pas demandé à l'UE de consigner des mesurages pour la dernière cellule de desserte pour l'UE pour le mesurage de MDT consigné, et dans lequel l'indication comprend au moins une valeur prédéterminée dans au moins un champ de mesurage et/ou un champ d'identité de cellule 0 de desserte dans le rapport de mesurage de MDT.
PCT/SE2022/050822 2021-10-18 2022-09-20 Rapport de mesurage de mdt pour équipements utilisateurs se trouvant dans n'importe quel état de sélection de cellule WO2023068977A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202163256771P 2021-10-18 2021-10-18
US63/256,771 2021-10-18

Publications (1)

Publication Number Publication Date
WO2023068977A1 true WO2023068977A1 (fr) 2023-04-27

Family

ID=83903155

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2022/050822 WO2023068977A1 (fr) 2021-10-18 2022-09-20 Rapport de mesurage de mdt pour équipements utilisateurs se trouvant dans n'importe quel état de sélection de cellule

Country Status (1)

Country Link
WO (1) WO2023068977A1 (fr)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210029569A1 (en) * 2018-04-02 2021-01-28 Lg Electronics Inc. Method for constructing logged measurement entry and device supporting the same

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210029569A1 (en) * 2018-04-02 2021-01-28 Lg Electronics Inc. Method for constructing logged measurement entry and device supporting the same

Non-Patent Citations (7)

* Cited by examiner, † Cited by third party
Title
3GPP TS 36.331
3GPP TS 37.320
3GPP TS 38.304
3GPP TS 38.331
KDDI CORPORATION ET AL: "3GPP TSG RAN2 Meeting #115-e; R2-2109027; Introduction of event-based trigger for LTE MDT logging", vol. RAN WG2, no. E-meeting; 20210816 - 20210827, 13 August 2021 (2021-08-13), XP052042941, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG2_RL2/TSGR2_115-e/Docs/R2-2109027.zip R2-2109027_MDT_event-based_36.331draftCR(Rel-17).docx> [retrieved on 20210813] *
KDDI CORPORATION ET AL: "3GPP TSG RAN2 Meeting #116-e; R2-2109715; Introduction of event-based trigger for LTE MDT logging", vol. RAN WG2, no. E-meeting; 20211101 - 20211112, 22 October 2021 (2021-10-22), XP052066193, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG2_RL2/TSGR2_116-e/Docs/R2-2109715.zip R2-2109715_36.331CR4724.docx> [retrieved on 20211022] *
QUALCOMM INC (RAPPORTEUR): "3GPP TSG RAN2 Meeting #116-e; R2-2109924; Report on [Post115-e][203][TEI] Discussion on details of event- triggered logged MDT for LTE", vol. RAN WG2, no. Electronic Meeting; 20211101 - 20211112, 22 October 2021 (2021-10-22), XP052066378, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG2_RL2/TSGR2_116-e/Docs/R2-2109924.zip R2-2109924 Report-EventTriggeredLoggeMDT-LTE_final.docx> [retrieved on 20211022] *

Similar Documents

Publication Publication Date Title
US11792693B2 (en) Methods and apparatuses for redirecting users of multimedia priority services
WO2023014257A1 (fr) Maintenance de configuration de qualité d&#39;expérience
WO2023203240A1 (fr) Cas d&#39;utilisation du découpage du réseau pour l&#39;accès sans fil fixe (fwa)
WO2023022642A1 (fr) Signalisation de surchauffe prédite d&#39;ue
WO2023012705A1 (fr) Partitionnement d&#39;accès aléatoire et rapport d&#39;accès aléatoire
WO2022240334A1 (fr) Reconfigurations conditionnelles de cellules dans des groupes de cellules secondaires
WO2023068977A1 (fr) Rapport de mesurage de mdt pour équipements utilisateurs se trouvant dans n&#39;importe quel état de sélection de cellule
WO2024027839A1 (fr) Procédé et appareil de configuration de type de rapport d&#39;emplacement
WO2024027838A9 (fr) Procédé et appareil pour arrêter un rapport de localisation
WO2023185737A1 (fr) Procédé et appareil permettant d&#39;effectuer une authentification/autorisation secondaire pour un dispositif terminal dans un réseau de communication
US20230039795A1 (en) Identifying a user equipment, ue, for subsequent network reestablishment after a radio link failure during an initial network establishment attempt
WO2023014260A1 (fr) Approches de signalisation pour plmn de catastrophe
WO2024030059A1 (fr) Mesure de qualité d&#39;expérience
WO2023011804A1 (fr) Réduction de la disponibilité d&#39;une configuration de test d&#39;entraînement basée sur la signalisation
WO2023146453A1 (fr) Journalisation d&#39;ue et notification de propriétés de hsdn
WO2024035305A1 (fr) Rapport de réussite de changement ou d&#39;ajout de pscell
WO2023095037A1 (fr) Rapport mdt journalisé faisant intervenir une mobilité inter-rat
WO2023194968A1 (fr) Liste de rapports d&#39;échec d&#39;établissement de connexion (cef) conditionnelle
WO2023059238A1 (fr) Calcul d&#39;état de mobilité de dispositif de communication à l&#39;aide d&#39;une fréquence de référence
WO2024035310A1 (fr) Configuration de zone de mesures de minimisation de test de conduite pour des réseaux non publics
WO2024038340A1 (fr) Connexions en mode relais dans un réseau de communication
WO2024063692A1 (fr) Gestion de signalisation de positionnement associée à un dispositif de communication au moyen d&#39;une fonction de gestion d&#39;accès et de mobilité locale
WO2023084464A1 (fr) Systèmes et procédés d&#39;interdiction d&#39;itinérance en cas de sinistre par des équipements d&#39;utilisateur dans des cellules réservées à une utilisation par un opérateur
WO2023153978A1 (fr) Informations d&#39;historique d&#39;eu (uhi) et informations d&#39;historique de mobilité (mhi) pendant l&#39;activation/désactivation de scg
WO2023214088A1 (fr) Automatisation pour une qos basée sur l&#39;application dans un groupe de vn 5g

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

Country of ref document: EP

Kind code of ref document: A1