WO2023132776A1 - Mesures de couche radio et de couche application alignées dans le temps - Google Patents

Mesures de couche radio et de couche application alignées dans le temps Download PDF

Info

Publication number
WO2023132776A1
WO2023132776A1 PCT/SE2023/050004 SE2023050004W WO2023132776A1 WO 2023132776 A1 WO2023132776 A1 WO 2023132776A1 SE 2023050004 W SE2023050004 W SE 2023050004W WO 2023132776 A1 WO2023132776 A1 WO 2023132776A1
Authority
WO
WIPO (PCT)
Prior art keywords
configuration
measurements
qoe
function
mdt
Prior art date
Application number
PCT/SE2023/050004
Other languages
English (en)
Inventor
Ali PARICHEHREHTEROUJENI
Filip BARAC
Luca LUNARDI
Johan Rune
Panagiotis Saltsidis
Cecilia EKLÖF
Angelo Centonza
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Publication of WO2023132776A1 publication Critical patent/WO2023132776A1/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

  • NR New Radio
  • 3GPP Third-Generation Partnership Project
  • eMBB enhanced mobile broadband
  • MTC machine type communications
  • URLLC ultra-reliable low latency communications
  • D2D side-link device-to-device
  • the NG RAN logical nodes shown in Figure 1 include a central (or centralized) unit (CU or gNB-CU) and one or more distributed (or decentralized) units (DU or gNB-DU).
  • gNB 100 includes gNB-CU 110 and gNB-DUs 120 and 130.
  • CUs e.g., gNB-CU 110
  • CUs 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.”
  • FIG. 2 shows another high-level view of an exemplary 5G network architecture, including a NG-RAN 299 and 5GC 298.
  • NG-RAN 299 can include gNBs (e.g., 210a,b) and ng-eNBs (e.g., 220a, b) that are interconnected with each other via respective Xn interfaces.
  • the gNBs and ng-eNBs are also connected via the NG interfaces to 5GC 298, more specifically to access and mobility management functions (AMFs, e.g., 230a, b) via respective NG- C interfaces and to user plane functions (UPFs, e.g., 240a, b) via respective NG-U interfaces.
  • AMFs access and mobility management functions
  • UPFs user plane functions
  • the AMFs can communicate with one or more policy control functions (PCFs, e.g., 250a, b) and network exposure functions (NEFs, e.g.,
  • Each of the gNBs can support the NR radio interface including frequency division duplexing (FDD), time division duplexing (TDD), or a combination thereof.
  • Each of ng-eNBs can support the fourth generation (4G) Long-Term Evolution (LTE) radio interface. Unlike conventional LTE eNBs, however, ng-eNBs connect to the 5GC via the NG interface.
  • Each of the gNBs and ng-eNBs can serve a geographic coverage area including one more cells, such as cells 21 la-b and 221a-b shown in Figure 2.
  • a UE 205 can communicate with the gNB or ng-eNB serving that cell via the NR or LTE radio interface, respectively.
  • Figure 2 shows gNBs and ng-eNBs separately, it is also possible that a single NG-RAN node provides both types of functionality.
  • QoE measurements were specified for UEs operating in earlier- generation LTE and UMTS networks and are being specified in 3 GPP for UEs operating in NR networks. Measurements in all of these networks operate according to similar high-level principles, with the purpose of measuring the end-user experience for certain applications over the network. For example, QoE measurements for streaming services and for MTSI (Mobility Telephony Service for IMS) are supported in LTE and NR networks.
  • QoE measurements for streaming services and for MTSI Mobility Telephony Service for IMS
  • Radio resource control (RRC) signaling is used to configure application-layer QoE measurements in UEs and to collect QoE measurement result files from configured UEs.
  • an application-layer measurement configuration from a core network (e.g., EPC, 5GC) or a network operations/administration/maintenance (0AM) function is encapsulated in a transparent container and sent to a UE’s serving base station (e.g., eNB, gNB), which forwards it to the UE access stratum (AS) in an RRC message.
  • a UE access stratum AS
  • Application-layer measurements made by the UE are encapsulated in a transparent container that is sent by the UE AS to the serving base station in an RRC message.
  • the serving base station then forwards the container to a Trace Collector Entity (TCE) or a Measurement Collection Entity (MCE) associated with the CN.
  • TCE Trace Collector Entity
  • MCE Measurement Collection Entity
  • These exemplary methods can also include sending the first configuration to a UE and storing the second configuration. These exemplary methods can also include receiving from the UE a first indication that an event associated with the QoE measurements has occurred. These exemplary methods can also include, in response to the first indication, sending the second configuration or an associated command to one or more second units or functions of the RAN node.
  • the first unit or function can be a CU-CP and the one or more second units or functions include one of more of the following: a CU-UP, and one or more DUs.
  • the other node or function associated with the RAN is one of the following: an 0AM node coupled to the RAN; or a node or function of a core network (CN) coupled to the RAN.
  • CN core network
  • one of the first configuration and the second configuration includes an indication of the event associated with the QoE measurements.
  • the event is one of the following: initiation of a UE application session with characteristics related to the first configuration; or an event that occurs after initiation of the UE application session.
  • the measurement configuration includes a plurality of second configurations of MDT measurements and an indication of which of the second configurations should be time- aligned with the QoE measurements.
  • these exemplary methods can also include, after sending the second configuration or the associated command, receiving from the UE a second indication that QoE measurements for the first configuration have ended, stopped, or paused.
  • these exemplary method can also include, in response to the second indication, sending one of the following commands to each of the second units or functions: a command to release the first configuration; or a command to maintain the first configuration in an inactive state.
  • these exemplary methods can also include the following operations of blocks: after sending the command, receiving from the UE a third indication that QoE measurements for the first configuration have restarted or resumed; and sending one of the following to each of the second units or functions: the first configuration; an updated first configuration; or a command to activate the first configuration and resume the QoE measurements.
  • the first configuration is sent to the UE together with a command to maintain the first configuration in an inactive state.
  • these exemplary methods can also include, upon receiving the second configuration, sending the second configuration to the one or more second units or functions together with a command to maintain the second configuration in an inactive state.
  • a command to activate the second configuration is sent in response to the receiving the first indication from the UE.
  • these exemplary methods can also include receiving, from the one or more second units or functions, results of the MDT measurements performed according to the second configuration. In some of these embodiments, the second configuration is received and the MDT measurements are initiated before the first configuration is received. In some variants , these exemplary methods can also include pausing the MDT measurements upon receiving the first configuration. In other variants, these exemplary methods can also include appending to the results of the MDT measurements an indication that QoE measurements were initiated upon receiving the first configuration.
  • Other embodiments include methods (e.g., procedures) for a second unit or function of a RAN node. These exemplary methods can include receiving, from a first unit or function of the RAN node, a configuration for MDT measurements that should be time-aligned with QoE measurements performed by a UE. These exemplary method can also include initiating time- aligned MDT measurements in accordance with the second configuration. These exemplary methods can also include sending results of the time-aligned MDT measurements to the first unit or function.
  • these exemplary methods can also include receiving one of the following commands from the first unit or function: a command to release the first configuration; or a command to maintain the first configuration in an inactive state. In such case, the time- aligned MDT measurements are stopped or paused based on the command.
  • these exemplary methods can also include subsequently receive one of the following information from the first unit or function: the configuration; an updated configuration for MDT measurements; or a command to activate the configuration and resume the QoE measurements.
  • the time-aligned MDT measurements are started, restarted, or resumed based on the received information.
  • the configuration is received together with a command to maintain the configuration in an inactive state and these exemplary methods can also include subsequently receiving a command to activate the configuration. In such case, the time-aligned MDT measurements are initiated in response to the command.
  • the first unit or function is a CU-CP and the second unit or function is a CU-UP or a DU.
  • RAN node units or functions e.g., CUs, CU-CPs, CU-UP, DUs, etc. of gNBs, eNBs, etc.
  • Other embodiments include non-transitory, computer- readable media storing program instructions that, when executed by processing circuitry, configure such RAN node units or functions to perform operations corresponding to any of the exemplary methods described herein.
  • embodiments described herein can facilitate a RAN node arranged in a distributed architecture to perform MDT measurements that are time-aligned with QoE measurements (including both legacy and RVQoE measurements) performed by a UE.
  • embodiments facilitate MDT measurements with corresponding QoE measurements that facilitate detection, interpretation, and/or understanding of possible application-related issues, as well as QoE measurements with corresponding MDT measurements that facilitate detection, interpretation, and/or understanding of possible radio- and network-related issues.
  • Availability of time-aligned measurements in this manner can lead to improved network performance.
  • Figures 1-2 illustrate two high-level views of an exemplary 5G/NR network architecture.
  • Figure 3 shows an exemplary configuration of NR user plane (UP) and control plane (CP) protocol stacks.
  • UP user plane
  • CP control plane
  • Figures 4A-B illustrate various aspects of QoE measurement configuration for a UE in an LTE network.
  • Figures 5 A-C illustrate various aspects of QoE measurement collection for a UE in an LTE network.
  • Figure 6 is a signal flow diagram that illustrates QoE measurement collection and reporting in an LTE network.
  • Figures 7-8 show signal flow diagrams of exemplary management-based MDT activations in a gNB-DU and a gNB-CU-CP, respectively.
  • Figure 9 shows a signaling diagram of a technique to control start/execution of MDT measurements in RAN distributed architecture for time alignment of the MDT and QoE measurements, according to various embodiments of the present disclosure.
  • Figure 10 shows a flow diagram of an exemplary method (e.g., procedure) for a first unit or function (e.g., CU-CP) of a RAN node (e.g., base station, eNB, gNB, ng-eNB, etc.), according to various embodiments of the present disclosure.
  • a first unit or function e.g., CU-CP
  • a RAN node e.g., base station, eNB, gNB, ng-eNB, etc.
  • Figure 11 shows a flow diagram of an exemplary method (e.g., procedure) for a second unit or function (e.g., CU-UP, DU) of a RAN node (e.g., base station, eNB, gNB, ng-eNB, etc.), according to various embodiments of the present disclosure.
  • a second unit or function e.g., CU-UP, DU
  • a RAN node e.g., base station, eNB, gNB, ng-eNB, etc.
  • Figure 12 shows a communication system according to various embodiments of the present disclosure.
  • Figure 13 shows a UE according to various embodiments of the present disclosure.
  • Figure 14 shows a network node according to various embodiments of the present disclosure.
  • Figure 15 shows host computing system according to various embodiments of the present disclosure.
  • Figure 16 is a block diagram of a virtualization environment in which functions implemented by some embodiments of the present disclosure may be virtualized.
  • Figure 17 illustrates communication between a host computing system, a network node, and a UE via multiple connections, at least one of which is wireless, according to various embodiments of the present disclosure.
  • Radio 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 (TP), a transmission reception point (TRP), 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.,
  • a “core network node” is any type of node in a core network.
  • Some examples of a core network node include, e.g., a Mobility Management Entity (MME), a serving gateway (SGW), a PDN Gateway (P-GW), a Policy and Charging Rules Function (PCRF), an access and mobility management function (AMF), a session management function (SMF), a user plane function (UPF), a Charging Function (CHF), a Policy Control Function (PCF), an Authentication Server Function (AUSF), a location management function (LMF), or the like.
  • MME Mobility Management Entity
  • SGW serving gateway
  • P-GW PDN Gateway
  • PCRF Policy and Charging Rules Function
  • AMF access and mobility management function
  • SMF session management function
  • UPF user plane function
  • Charging Function CHF
  • PCF Policy Control Function
  • AUSF Authentication Server Function
  • LMF location management function
  • Wireless Device As used herein, a “wireless device” (or “WD” for short) is any type of device that 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. Unless otherwise noted, the term “wireless device” is used interchangeably herein with “user equipment” (or “UE” for short).
  • 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.
  • VoIP voice over IP
  • PDAs personal digital assistants
  • LME laptop-embedded equipment
  • CPE wireless customer-premise equipment
  • MTC mobile-type communication
  • LoT Internet-of-Things
  • 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.
  • Base station may comprise a physical or a logical node transmitting or controlling the transmission of radio signals, e.g., eNB, gNB, ng-eNB, en- gNB, centralized unit (CU)/distributed unit (DU), transmitting radio network node, transmission point (TP), transmission reception point (TRP), remote radio head (RRH), remote radio unit (RRU), Distributed Antenna System (DAS), relay, etc.
  • eNB e.g., eNB, gNB, ng-eNB, en- gNB, centralized unit (CU)/distributed unit (DU), transmitting radio network node, transmission point (TP), transmission reception point (TRP), remote radio head (RRH), remote radio unit (RRU), Distributed Antenna System (DAS), relay, etc.
  • 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.
  • CP-OFDM Cyclic Prefix Orthogonal Frequency Division Multiplexing
  • DFT-S-OFDM DFT-spread OFDM
  • NR DL and UL physical resources are organized into equal-sized 1-ms subframes. A subframe is further divided into multiple slots of equal duration, with each slot including multiple OFDM-based symbols.
  • time-frequency resources can be configured much more flexibly for an NR cell than for an LTE cell.
  • SCS 15-kHz OFDM sub-carrier spacing
  • NR SCS can range from 15 to 240 kHz, with even greater SCS considered for future NR releases.
  • NR networks In addition to providing coverage via cells as in LTE, NR networks also provide coverage via “beams.”
  • a downlink (DL, i.e., network to UE) “beam” is a coverage area of a network-transmitted reference signal (RS) that may be measured or monitored by a UE.
  • RS can include any of the following: synchronization signal/PBCH block (SSB), channel state information RS (CSLRS), tertiary reference signals (or any other sync signal), positioning RS (PRS), demodulation RS (DMRS), phase-tracking reference signals (PTRS), etc.
  • SSB is available to all UEs regardless of the state of their connection with the network, while other RS (e.g., CSLRS, DM-RS, PTRS) are associated with specific UEs that have a network connection.
  • Figure 3 shows an exemplary configuration of NR user plane (UP) and control plane (CP) protocol stacks between a UE, a gNB, and an AMF, such as those shown in Figures 1-2.
  • the Physical (PHY), Medium Access Control (MAC), Radio Link Control (RLC), and Packet Data Convergence Protocol (PDCP) layers between the UE and the gNB are common to UP and CP.
  • the PDCP layer provides ciphering/deciphering, integrity protection, sequence numbering, reordering, and duplicate detection for both CP and UP.
  • PDCP provides header compression and retransmission for UP data.
  • IP Internet protocol
  • SDAP Service Data Adaptation Protocol
  • QoS quality-of-service
  • DRBs Data Radio Bearers
  • QFI QoS flow identifiers
  • the MAC layer provides mapping between LCHs and PHY transport channels, LCH prioritization, multiplexing into or demultiplexing from transport blocks (TBs), hybrid ARQ (HARQ) error correction, and dynamic scheduling (on gNB side).
  • the PHY layer provides transport channel services to the MAC layer and handles transfer over the NR radio interface, e.g., via modulation, coding, antenna mapping, and beam forming.
  • the non-access stratum (NAS) layer is between UE and AMF and handles UE/gNB authentication, mobility management, and security control.
  • the RRC layer sits below NAS in the UE but terminates in the gNB rather than the AMF.
  • RRC controls communications between UE and gNB at the radio interface as well as the mobility of a UE between cells in the NG-RAN.
  • RRC also broadcasts system information (SI) and performs establishment, configuration, maintenance, and release of DRBs and Signaling Radio Bearers (SRBs) and used by UEs. Additionally, RRC controls addition, modification, and release of carrier aggregation (CA) and dual -connectivity (DC) configurations for UEs.
  • CA carrier aggregation
  • DC dual -connectivity
  • RRC also performs various security functions such as key management.
  • RRC IDLE After a UE is powered ON it will be in the RRC IDLE 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 IDLE, after the connection with the network is released.
  • RRC IDLE state the UE’s radio is active on a discontinuous reception (DRX) schedule configured by upper layers.
  • DRX active periods also referred to as “DRX On durations”
  • an RRC_IDLE UE receives SI broadcast in the cell where the UE is camping, performs measurements of neighbor cells to support cell reselection, and monitors a paging channel on PDCCH for pages from 5GC via gNB.
  • NR RRC includes an RRC_INACTIVE state in which a UE is known (e.g., via UE context) by the serving gNB.
  • RRC INACTIVE has some properties similar to a “suspended” condition used in LTE.
  • QoE measurements were specified for UEs operating in earlier-generation LTE and UMTS networks and are being specified in 3 GPP for UEs operating in NR networks. QoE measurements in all of these networks operate according to similar high- level principles, with the purpose of measuring the end-user experience for certain applications over the network. For example, QoE measurements for streaming services and for MTSI (Mobility Telephony Service for IMS) are supported in LTE and NR networks.
  • MTSI Mobility Telephony Service for IMS
  • QoE measurements may be initiated towards the RAN from an 0AM node generically for a group of UEs (e.g., all UEs meeting one or more criteria), or they may also be initiated from the CN to the RAN for a specific UE.
  • the former is often referred to as “managementbased QoE” (or “m-based QoE” for short) and is used when the 0AM system is interested in general QoE statistics from a certain area (which is configured as an area scope).
  • the management-based QoE configuration is sent directly from the 0AM system to the RAN nodes controlling cells that are within the area scope.
  • Each RAN node selects UEs that are within the area scope (and that also fulfill any other relevant condition, such as supporting a particular application/service type) and sends the QoE configuration to these UEs.
  • Signaling-based QoE is used by the 0AM system to collect QoE measurement results from a specific UE, e.g., because the user of the UE has filed a complaint.
  • the 0AM system sends the s-based QoE configuration to the HSS (in EPS/LTE) or UDM (in 5GS/NR), which forwards the QoE configuration to the UE’s CN, e.g., to MME in EPS/LTE or AMF in 5G/NR.
  • the CN then forwards the s-based QoE configuration to the RAN node that serves the specific UE, and the RAN node sends it to the UE.
  • the UE is not aware of whether a received QoE configuration is m-based or s-based.
  • the QoE framework is integrated with the Trace functionality and a Trace ID is associated with each QoE configuration.
  • the QoE functionality will be logically separated from the Trace functionality, but it will still partly reuse the Trace signaling mechanisms.
  • a globally unique QoE reference (formed of MCC+MNC+QMC ID, where the QMC ID is a string of 24 bits) will be associated with each QoE configuration.
  • the QoE reference is included in the container with measurement instructions and sent to the serving RAN node (e.g., gNB).
  • the QoE reference is replaced by a shorter identifier denoted as measConfigAppLayerld, which is locally unique within a UE (i.e., one-to-one mapping between a measConfigAppLayerld and a QoE reference for each QoE configuration provided to a UE).
  • the measConfigAppLayerld is stored in the UE AS and also forwarded to the UE application layer in an AT Command together with the service type indication and the container with the measurement instructions.
  • QoE reports are sent from the UE application layer to the UE AS, which forwards them to the serving RAN node, which in turn forwards them to the MCE.
  • QoE measurement results are placed in a “container”, which is uninterpretable by the UE AS and the RAN.
  • QoE reporting can be configured to be periodic or only at the end of an application session.
  • the RAN can instruct the UE to pause QoE reporting, e.g., in case the cell/gNB is in a state of overload.
  • session start/ stop indications can be sent from the UE application layer to the UE AS and from the UE AS to the RAN.
  • a session stop indication may be implicit in the form of a QoE report sent when the application session and the associated QoE measurement session have ended.
  • the RAN may decide to release a QoE configuration in a UE at any time, as an implementation-based decision. Typically, it is done when the UE has moved outside an area configured for the QoE measurements, commonly referred to as the area scope.
  • One benefit of legacy or conventional QoE solutions is the ability to keep the QoE measurement for an entire session, even during a handover.
  • the UE can continue QoE measurements on an ongoing application session until the application session ends, even if the UE in the meantime moves out of the configured area scope.
  • a "TRACE START" S1AP message is used by the Evolved Packet Core (EPC) to initiate QoE measurements by a specific UE.
  • EPC Evolved Packet Core
  • This message carries details about the measurement configuration the application should collect in the Container for application-layer measurement configuration IE, which transparent to the RAN.
  • This message also includes details needed to reach the TCE to which the measurements should be sent.
  • Figures 4A-B illustrate a procedure between an E-UTRAN and a UE for configuring QoE measurements in an LTE network.
  • Figure 4A shows an exemplary UE capability transfer procedure used to transfer UE radio access capability information from the UE to E-UTRAN.
  • the E-UTRAN can send a UECapabilityEnquiry message.
  • the UE can respond with a UECapabilitylnformation message that includes a UE-EUTRA-Capability IE.
  • This IE may further include a UE-EUTRA-Capability-v 1530 IE, which can be used to indicate whether the UE supports QoE Measurement Collection for streaming services and/or MTSI services.
  • the UE-EUTRA-Capability-v 1530 IE can include a measParameters-vl 530 IE containing the information about the UE’s measurement support.
  • Figure 4B shows exemplary ASN. l data structures for UE-EUTRA-Capability-v 1530 and measParameters-vl 530 IES, with relevant fields defined in Table 1 below.
  • Figures 5A-C illustrate various aspects of QoE measurement configuration collection for a UE in an LTE network.
  • Figure 5A shows an exemplary signal flow diagram of a QoE measurement collection process for LTE.
  • the serving eNB sends to a UE in RRC CONNECTED state an RRCConnectionReconfiguration message that includes a QoE configuration file, e.g., a measConfigAppLayer IE within an OtherConfig IE.
  • the QoE configuration file is an application-layer measurement configuration received by the eNB (e.g., from EPC) encapsulated in a transparent container, which is forwarded to UE in the RRC message.
  • the UE responds with an RRCConnectionReconfigurationComplete message.
  • a UE can perform various operations when it receives an RRCConnectionReconfiguration message including an OtherConfig IE that includes a measConfigAppLayer IE.
  • measConfigAppLayerContainer e.g., Figure 5B
  • the UE forwards measConfigAppLayerContainer (e.g., Figure 5B) to upper layers considering the serviceType and considers itself to be configured to send application layer measurement reports. Otherwise (i.e., if measConfigAppLayer is set to release), the UE informs upper layers to clear the stored application layer measurement configuration, discards application layer measurement report information received from upper layers, and considers itself not to be configured to send application layer measurement reports.
  • the UE When configured to do so, the UE performs the configured measurements and sends a MeasReportAppLayer RRC message to the eNB, including a QoE measurement result file. Although not shown, the eNB can forward this result file transparently (e.g., to EPC). More specifically, if the UE has been configured with SRB4, the UE can:
  • Figure 5B shows an exemplary ASN.
  • l data structure for a measConfigAppLayer IE The setup includes the transparent container measConfigAppLayerContainer which specifies the QoE measurement configuration for the Application of interest.
  • measConfigAppLayerContainer specifies the QoE measurement configuration for the Application of interest.
  • serviceType field a value of “qoe” indicates Quality of Experience Measurement Collection for streaming services and a value of “qoemtsi” indicates Enhanced Quality of Experience Measurement Collection for MTSI. This field also includes various spare values.
  • Figure 5C shows an exemplary ASN.l data structure for a measReportAppLayer IE, by which a UE can send to the E-UTRAN (e.g., via SRB4) the QoE measurement results of an application (or service).
  • the service for which the report is being sent is indicated in the serviceType IE.
  • the UE Application layer measurement configuration IE described in 3GPP TS 36.413 (v.16.7.0) section 9.2.1.128 carries configuration information provided by a QoE Measurement Collection (QMC) function.
  • QMC QoE Measurement Collection
  • This IE is signaled to the RAN (eNB) from the mobility management entity (MME) in the EPC via the SI interface CP (e.g., S1AP protocol) as further specified in 3GPP TS 36.413.
  • MME mobility management entity
  • SI interface CP e.g., S1AP protocol
  • this IE is included in the Trace Activation IE, which also includes the Trace Collection Entity (TCE) IP Address IE.
  • Table 2 below defines the container for the application layer measurement configuration.
  • Figure 6 shows a more detailed signal flow of activation of QoE measurement collection and reporting of collected information without UE mobility in an LTE network.
  • This signal flow is between a measurement collection entity (MCE, 650), a network manager (NM, 640), a domain manager (DMZEM, 630), one or more eNBs (620) in E-UTRAN, and the UE (610) - particularly access stratum (or access, for short) and application parts of the UE.
  • MCE measurement collection entity
  • NM network manager
  • DZEM domain manager
  • 630 domain manager
  • eNBs 620
  • the following description omits these reference numbers for brevity.
  • the operations shown in Figure 6 are given numerical labels, these labels are intended to facilitate the following description rather than to require and/or imply a particular order of the operations.
  • the NM sends an Activate Measurement Job message to the DM, which forwards the message to the eNB in operation 2.
  • the message includes a service type (e.g., streaming), an area scope, a measurement configuration file for the QoE measurements to be performed, and a QoE reference identifier.
  • the eNB identifies served cells matching the area scope, as well as UEs in these served cells that match other parameters in the message (e.g., service type). The eNB can base this determination on UE capability information sent from the UE to the eNB (not shown).
  • the eNB sends an RRCConnectionReconfiguration message to the AS (e.g. , RRC layer) of the UE.
  • the eNB includes the service type, the area scope (e.g, one or more cells, tracking areas, etc.), the measurement configuration file, and the QoE reference .
  • AT command +CAPPLEVMC is of the following form when used for QoE measurement configuration:
  • +CAPPLEVMC ⁇ app-meas_service_type>, ⁇ start-stop_reporting>[, ⁇ app- meas_config_file_length>, ⁇ app-meas_config-file>], where the various fields are defined below:
  • ⁇ n> integer type. Disable and enable presentation of the unsolicited result code +CAPPLEVMC to the TE.
  • ⁇ start-stop_reporting> integer type. Indicates the start and stop of the application-level measurement reporting for the application indicated by the ⁇ app-meas_service_type>.
  • ⁇ app-meas_config_file_length> integer type. Indicates the number of octets of the ⁇ app- meas_config-file> parameter.
  • ⁇ app-meas_config-file> string of octets.
  • the UE starts an application associated with the service type and initiates measurement collection according to the received configuration and area.
  • the UE assigns this measurement collection a recording session ID and reports this ID (in operation 7) to the UE AS using the same AT command.
  • the UE AS sends this ID to the eNB in a MeasReportAppLayer RRC message, and the eNB notifies the NM of the initiation of the measurement collection in operation 9.
  • the UE application layer completes the QoE measurement collection according to the received configuration (operation 10) and reports the results to the UE AS via AT command +CAPPLEVMR (operation 11) along with the associated QoE reference ID received earlier.
  • the report can be a transparent container, as discussed earlier.
  • AT command +CAPPLEVMC is of the following form when used for QoE measurement reporting:
  • ⁇ app_meas_service_type> integer type. Contains the indication of what application that is providing the application-level measurement report.
  • ⁇ app-meas_report_length> integer type. Indicates the number of octets of the ⁇ app- meas_report> parameter.
  • ⁇ app-meas_report> string of octets. Contains the application-level measurement configuration file for the application indicated by the ⁇ app-meas_service_type>. The parameter shall not be subject to conventional character conversion as per +CSCS.
  • the UE AS sends the report and the QoE reference ID to the eNB in a MeasReportAppLayer RRC message.
  • the eNB subsequently forwards the report to the MCE (operation 13).
  • the MCE may forward the QoE measurement report another entity in the network for analysis and further action (e.g., in the 0AM system).
  • round trip time e.g., average, max/min, standard deviation, instant value, etc.
  • downlink delay e.g., average, max/min, standard deviation, instant value, etc.
  • jitter of arriving packets e.g., average, max/min, standard deviation, instant value, etc.
  • timeliness of the packets e.g., average, max/min, standard deviation, instant value, etc.
  • application level buffer e.g., average, max/min, standard deviation, instant value, etc.
  • lightweight QoE metrics can be derived from a single conventional QoE metric or from multiple (e.g., all) conventional QoE metrics for an application.
  • An example of the former is a lightweight representation of the average throughput (AvgThroughput) conventional QoE metric and a lightweight representation of the initial playout delay (InitialPlayoutDelay) conventional QoE metric for Progressive Download and DASH.
  • An example of the latter is a lightweight QoE metric that represents both of these conventional QoE metrics.
  • different subsets of conventional QoE metrics for an application can be represented by respective lightweight QoE metrics. Each subset can include one or more conventional QoE metrics.
  • RV RAN-visible
  • Conventional QoE reports are intended for the MCE outside the RAN (e.g., in 0AM system) and the RAN are unable to read conventional QoE reports (although gNB/eNB implementations are not prevented from doing so).
  • RVQoE metrics or values are intended for the RAN and are delivered to the RAN in a format that the RAN understands.
  • the RVQoE metrics or values are derived from the regular QoE metrics, collected and compiled in reports by the UE application layer, and delivered to the RAN, which may use the reports for various types of optimizations.
  • RVQoE metrics and values can be considered a form of lightweight QoE metrics previously disclosed by Applicant in U.S. App. 63/092,984.
  • a UE can be configured by the network to perform logged MDT and/or immediate MDT measurements.
  • a UE in RRC IDLE state can be configured (e.g., via a LoggedMeasurementConfiguration RRC message from the network) to perform periodical MDT measurement logging.
  • An MDT configuration can include logginginterval and loggingduration. The UE starts a timer (T330) set to loggingduration (e.g., 10-120 min) upon receiving the configuration, and perform periodical MDT logging every logginginterval (1.28- 61.44 s) within the loggingduration while the UE is in RRC IDLE state.
  • T330 timer
  • loggingduration e.g., 10-120 min
  • the UE collects DL reference signal received strength and quality (i.e., RSRP, RSRQ) based on existing measurements required for cell reselection purposes.
  • the UE reports the collected/logged information to the network when the UE returns to RRC CONNECTED state.
  • a UE can be configured to perform and report immediate MDT measurements while in RRC CONNECTED state. Similar to logged MDT, immediate MDT measurements are based on existing UE and/or network measurements performed while a UE is in RRC CONNECTED, and can include any of the following measurement quantities:
  • M5 Scheduled IP layer Throughput for MDT measurement separately for DL and UL, per RAB per UE and per UE for the DL, per UE for the UL, by eNB.
  • RS SI received signal strength
  • M9 round trip time (RTT) measurement by UE.
  • the gNB-DU shall initiate the requested MDT session ignore the Interfaces To Trace IE and Trace Depth IE (if included), when the Trace Activation IE includes the MDT Activation IE set to "Immediate MDT Only".
  • the gNB-CU-CP can send the gNB-CU- UP a TRACE START message (via El AP) that requests the gNB-CU-UP to initiate a trace session for a specific UE.
  • the TRACE START message Upon reception of the TRACE START message, the gNB-CU-UP initiates the requested trace session for the requested UE, as further described in 3GPP TS 32.422 (vl6.8.0).
  • the gNB-CU-UP shall initiate the requested MDT session ignore the Interfaces To Trace IE and Trace Depth IE (if included), when the MDT Activation IE is set to "Immediate MDT Only".
  • the RAN is not capable of aligning MDT measurements performed by the DU(s) and/or CU-UP(s) with QoE/RVQoE/MDT measurements performed by a UE.
  • a CU-CP when a CU-CP receives a QoE measurement configuration and an MDT measurement configuration (e.g., concurrently or non-concurrently), it does not immediately send the MDT configurations to CU-UPs and/or DUs of the same RAN node. Rather, the CU-CP refrains from sending until receiving a trigger from the UE, e.g., a session start indication for an application for which the QoE measurement configuration applies.
  • a trigger e.g., a session start indication for an application for which the QoE measurement configuration applies.
  • each of the CU- UPs and/or DUs starts executing it immediately as in the legacy or conventional MDT measurement framework.
  • MDT uses a variety of triggers (periodic, event based, etc.) for initiating and collecting measurements depending on the type of activation (e.g., logged or immediate) and the particular measurement type (e.g., Ml, M2, etc.).
  • triggers periodic, event based, etc.
  • Ml the particular measurement type
  • M2 the particular measurement type
  • QoE measurement configuration alignment is required, then such requirement should be signaled with an MDT/QoE alignment parameter signaled by the 0AM when the QoE activation is initiated.
  • This parameter needs to be carried to the UE that will perform the measurements. When this parameter is set then the relevant QoE measurement will be performed in alignment with ongoing/existing MDT measurements.
  • RAN visible QoE may refer to RAN visible QoE measurements, RAN visible QoE measurement reporting, RAN visible QoE parameters and metrics, processing of information to derive RAN visible QoE parameters/metrics/ information/data, and an overall framework for these and related activities.
  • RVQoE report refers to a QoE report that includes RVQoE metrics and/or RVQoE values.
  • An RVQoE report can be associated with one or more service types, one or more network slices, one or more service subtypes, one or more subservice types, etc.
  • the term “conventional QoE metric” refers to any of the QoE measurements specified in 3GPP TS 26.247 (vl6.4.1), 26.114 (vl6.7.0), 26.118 (v 16.0.2), and 26.346 (v 16.6.0) that are delivered from the UE to a network entity via the RAN, particularly when the RAN is unable to read the QoE reports containing the measured values of these metrics.
  • RVQoE metrics and values can be carried in information elements (IES) of protocol messages, including RRC and inter-node signaling protocols.
  • RVQoE metrics and values can be representations (e.g., in modified, adapted, or otherwise processed forms) of at least one conventional (or legacy) QoE metric as that term is defined above. Each representation can be condensed, compact, simplified, and/or more abstract with respect to the conventional QoE metric(s). For each, a RVQoE metric or value can require fewer information bits to transmit than corresponding conventional QoE metric(s).
  • embodiments disclosed herein are applicable to both signaling- and management-based MDT and QoE measurements.
  • embodiments disclosed herein are applicable to UEs and RANs used in UMTS, LTE, and NR.
  • the CU-CP triggers the MDT measurements at the CU-UP and/or DU upon receiving an indication from the UE about an event at the UE (e.g., associated with the UE application layer).
  • the MDT configuration and the QoE configuration may be sent to the CU-CP in in the same message (as indicated in the figure) or in separate messages.
  • the order and timing of separate messages may be arbitrary, e.g., with the QoE configuration being sent to the CU-CP first and the MDT configuration being sent to the CU-CP at a later point in time.
  • a first unit or function of a RAN node receives at least one QoE measurement configuration and at least one MDT measurement configuration from another network node (e.g., 0AM node, CN node such as AMF, etc.).
  • At least one of the received configurations includes an indication to perform the configured QoE and MDT measurements in a time-aligned manner, i.e., the RAN node starts (and possibly ends) performing the configured MDT and QoE measurements at the same time.
  • 0AM when alignment of the MDT and QoE measurement is required, 0AM sends the MDT configuration (even for management-based MDT) to the CU-CP. This restriction at the 0AM enables the CU-CP to control the alignment of the MDT measurement performed at DU and/or CU-UP and the QoE measurements performed at the UE.
  • the first unit or function of the RAN node can store and maintain the received MDT configuration in memory while sending the QoE configuration to the UE.
  • the first unit or function can maintain the stored MDT configuration until receiving from the UE an indication associated with a UE event related to the QoE configuration (e.g., an event for an application to which the QoE configuration applies, such as streaming).
  • the first unit or function of the RAN node sends the MDT configuration to one or more other units or functions of the RAN node, i.e., that should perform measurements according to the MDT configuration.
  • the indication from the UE is that an application session has started or that the status of an application session has changed.
  • the indication from the UE can be related to occurrence of one or more non-session-related events or conditions that are predefined or have been configured by the first unit or function (also referred to as “eventbased measurement triggering”).
  • a triggering event or condition may occur after the start of application session.
  • the first unit or function e.g., CU-CP
  • the first unit or function sends the MDT configuration to other units or functions of the RAN node (e.g., CU-UP and/or DUs) when it receives an explicit or implicit indication that the RVQoE measurement has started.
  • a CU-CP can send the MDT configuration to a CU-UP that should perform the MDT measurements using Trace Start signaling via the El interface and to one or more DUs that should perform the MDT measurements using Trace Start signaling via the Fl interface.
  • the CU-UP and/or the DUs can immediately (i.e., as quickly as technically feasible) begin executing the MDT measurements, according to current 3 GPP specifications.
  • a first unit or function e.g., CU-CP
  • the above-described operations by a first unit or function are primarily concerned with time alignment between MDT measurements and conventional QoE measurements, they are also applicable to time alignment between MDT measurements and RVQoE measurements.
  • the first unit or function may create the RVQoE measurement configuration rather than receiving it from another network node, which may optionally provide instruction or command for the first unit or function to create it.
  • the first unit or function may send the same MDT configuration or different MDT configurations to other units or functions of the RAN node that should perform the MDT measurements.
  • a CU-CP can send a first MDT configuration to a CU- UP and a second MDT configuration to one or more DUs.
  • the first unit or function of the RAN node may take one or more actions when receiving an indication that the MDT measurements to be aligned are no longer aligned with the QoE measurements, e.g., because no corresponding QoE measurements session is ongoing at the UE.
  • Such an indication may be an explicit or implicit indication from the UE that the QoE measurement session has stopped or ended.
  • the first unit or function may take no action towards the one or more second units or functions that are performing the MDT measurements and allow the MDT report(s) to cover time beyond the end of the QoE measurement session.
  • the first unit or function may send an instruction to each of the second units or functions that are performing the MDT measurements to release the MDT configuration and, if needed, to send a final MDT report with the measurement results collected up to the time of release. If the UE later starts a new QoE measurement session for the same QoE configuration and indicates this to the first unit or function, the first unit or function may send the same or equivalent MDT configuration (i.e., to the one that was released) to each of the second units or functions that were performing the MDT measurements, which can cause an immediate restart of the configured MDT measurements.
  • the first unit or function may send an instruction to each of the second units or functions that are performing the MDT measurements to pause, suspend or inactivate the MDT configuration and, if needed, to send an MDT report with the measurement results collected up to the time of pause or suspend.
  • the first unit or function may instruct each of the second units or functions to stop the ongoing MDT measurements but to retain the associated MDT configuration. If a new measurement session of the same QoE configuration is later started and the first unit or function receives an indication of this from the UE, the first unit or function may send an instruction to each of the second units or functions to resume or reactivate the paused, suspended, or inactivated MDT configuration. In case the MDT configuration was retained when the measurements were stopped by the second units or functions, the first unit or function can send an instruction to restart the stopped MDT measurement.
  • the first unit or function may have already received a QoE configuration (and/or created or received a RVQoE configuration) when a management- or signaling-based MDT configuration is activated for a second unit or function (e.g., DU) of the RAN node (with MDT measurements potentially already ongoing).
  • a QoE configuration and/or created or received a RVQoE configuration
  • a management- or signaling-based MDT configuration is activated for a second unit or function (e.g., DU) of the RAN node (with MDT measurements potentially already ongoing).
  • the first unit or function acts as the coordinating entity and uses the reference identifying the MDT Trace (e.g., Trace ID) as the MDT reference to send together with the QoE reports to MCE. If the RAN is the consumer of QoE measurements (e.g., for RVQoE case), the first unit or function can send the reference identifying the MDT Trace (e.g., Trace ID) together with the QoE reports to other RAN nodes.
  • the reference identifying the MDT Trace e.g., Trace ID
  • the first unit or function may replace an MDT configuration with measurements ongoing in one or more second units or functions with a new or equivalent MDT configuration, when the first unit or function receives an indication of a start of a QoE measurement session with which the MDT measurements should be time-aligned. This may be done by releasing the existing MDT configuration with an identical or similar MDT configuration.
  • the first unit or function may indicate to the one or more second units or functions that the measurements of the MDT configuration should be restarted (e.g., reset and started as if newly initiated).
  • Pause the MDT measurements collected by the first unit or function (e.g., pause Ml and M2 measurements collected by the gNB-CU-CP) and thereby create a “gap” in the MDT report, which can be interpreted by 0AM as an indication that QoE measurements were started at the time of the gap.
  • the 0AM needs to align the MDT traces from each RAN node that has multiple units or functions (e.g., gNB-CU-CP, gNB-CU-UP, gNB-DU), and given that the 0AM is able to find an indication of QoE trace start in one of such MDT traces (i.e., the trace collected and reported by the RAN node receiving the Alignment Request), the 0AM will be able to also determine at which point of the MDT measurement trace collected by nodes different from the one receiving the Alignment Request, the QoE Trace was started
  • the first unit or function When the first unit or function subsequently receives from the UE (or 0AM, or CN such as AMF) an indication of an event (e.g., an indication from the UE of a start of a session of QoE measurements with which the MDT measurements should be aligned), the first unit or function sends to the second units or functions an indication to start the measurements for the MDT configuration that was previously inactive.
  • an indication of an event e.g., an indication from the UE of a start of a session of QoE measurements with which the MDT measurements should be aligned
  • the first unit or function in response to the UE indication, can cause (e.g., by a command or instruction) the one or more second units or functions to store the MDT configuration in an inactive state ready to be activated again, e.g., if another session of the QoE measurements it/they should be aligned with starts.
  • the first unit or function can cause (e.g., by a command or instruction) the one or more second units or functions to release (e.g., delete) the MDT configuration.
  • the first unit or function may keep the maintain the stored MDT configuration in case the first unit or function subsequently receives an indication from the UE (or 0AM) of an event that initiates QoE measurements with which the MDT measurements should be aligned. In such case, the first unit or function sends the MDT configuration again to the one or more second units or functions, which start the measurements of the MDT configuration immediately.
  • the alternative embodiments described in this section are applicable both to alignment of MDT measurements with regular QoE measurements and alignment of MDT measurements with RVQoE measurements (and alignment between MDT measurements and combined QoE and RVQoE measurements).
  • the MDT/QoE indication is a bit map.
  • One bit in the bit map indication configuration alignment for all measurement types other bits refer to configuration alignment for logged measurement, other for immediate configuration, other bits for reporting alignment, other bit for specific measurement types like Ml, M2, M4, M5, M6, M7, etc.
  • the exemplary method can include the operations of block 1010, where the first unit or function can receive from another node or function associated with the RAN a measurement configuration that includes the following:
  • the first unit or function can be a CU-CP and the one or more second units or functions including one of more of the following: a CU-UP and one or more DUs.
  • the other node or function associated with the RAN is one of the following: an 0AM node coupled to the RAN; or a node or function of a core network (CN) coupled to the RAN.
  • CN core network
  • the exemplary method can also include the operations of block 1050, where the first unit or function can, after sending the second configuration or the associated command (e.g., in block 1040), receive from the UE a second indication that QoE measurements for the first configuration have ended, stopped, or paused.
  • the exemplary method can also include the operations of block 1055, where the first unit or function can, in response to the second indication, send one of the following commands to each of the second units or functions: a command to release the first configuration; or a command to maintain the first configuration in an inactive state.
  • Figure 11 shows an exemplary method (e.g., procedure) for a second unit or function of a RAN node, according to various embodiments of the present disclosure.
  • the exemplary method can be performed by RAN node units or functions (e.g., CU-UP, DU) such as described elsewhere herein.
  • the exemplary method can include the operations of block 1110, where the second unit or function can receive, from a first unit or function of the RAN node, a configuration for MDT measurements that should be time-aligned with QoE measurements performed by a UE.
  • the exemplary method can also include the operations of block 1130, where the second unit or function can initiate time-aligned MDT measurements in accordance with the second configuration.
  • the exemplary method can also include the operations of block 1160, where the second unit or function can send results of the time-aligned MDT measurements to the first unit or function.
  • the first unit or function is a CU-CP and the second unit or function is a CU-UP or a DU.
  • FIG. 12 shows an example of a communication system 1200 in accordance with some embodiments.
  • the communication system 1200 includes a telecommunication network 1202 that includes an access network 1204, such as a radio access network (RAN), and a core network 1206, which includes one or more core network nodes 1208.
  • the access network 1204 includes one or more access network nodes, such as network nodes 1210a and 1210b (one or more of which may be generally referred to as network nodes 1210), or any other similar 3 rd Generation Partnership Project (3 GPP) access node or non-3GPP access point.
  • 3 GPP 3 rd Generation Partnership Project
  • the network nodes 1210 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 1212a, 1212b, 1212c, and 1212d (one or more of which may be generally referred to as UEs 1212) to the core network 1206 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 1200 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 1200 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.
  • the UEs 1212 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 1210 and other communication devices.
  • the network nodes 1210 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 1212 and/or with other network nodes or equipment in the telecommunication network 1202 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 1202.
  • 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 1216 may be under the ownership or control of a service provider other than an operator or provider of the access network 1204 and/or the telecommunication network 1202, and may be operated by the service provider or on behalf of the service provider.
  • the host 1216 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 1200 of Figure 12 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 1202 is a cellular network that implements 3 GPP standardized features. Accordingly, the telecommunications network 1202 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 1202. For example, the telecommunications network 1202 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 1212 are configured to transmit and/or receive information without direct human interaction.
  • a UE may be designed to transmit information to the access network 1204 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 1204.
  • 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 1214 communicates with the access network 1204 to facilitate indirect communication between one or more UEs (e.g., UE 1212c and/or 1212d) and network nodes (e.g., network node 1210b).
  • the hub 1214 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs.
  • the hub 1214 may be a broadband router enabling access to the core network 1206 for the UEs.
  • the hub 1214 may be a controller that sends commands or instructions to one or more actuators in the UEs.
  • the hub 1214 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 1214 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 1214 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 1214 then provides to the UE either directly, after performing local processing, and/or after adding additional local content.
  • the hub 1214 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 1214 may have a constant/persistent or intermittent connection to the network node 1210b.
  • the hub 1214 may also allow for a different communication scheme and/or schedule between the hub 1214 and UEs (e.g., UE 1212c and/or 1212d), and between the hub 1214 and the core network 1206.
  • the hub 1214 is connected to the core network 1206 and/or one or more UEs via a wired connection.
  • the hub 1214 may be configured to connect to an M2M service provider over the access network 1204 and/or to another UE over a direct connection.
  • UEs may establish a wireless connection with the network nodes 1210 while still connected via the hub 1214 via a wired or wireless connection.
  • the hub 1214 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 1210b.
  • the hub 1214 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 1210b, 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 cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle-mounted or vehicle embedded/integrated wireless device, etc.
  • Other examples include any UE identified by 3 GPP, including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.
  • NB-IoT narrow band internet of things
  • MTC machine type communication
  • eMTC enhanced MTC
  • a UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X).
  • D2D device-to-device
  • DSRC Dedicated Short-Range Communication
  • V2V vehicle-to-vehicle
  • V2I vehicle-to-infrastructure
  • V2X vehicle-to-everything
  • a UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device.
  • a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller).
  • a UE may represent a device that is not intended for sale
  • the UE 1300 includes processing circuitry 1302 that is operatively coupled via a bus 1304 to an input/output interface 1306, a power source 1308, a memory 1310, a communication interface 1312, and/or any other component, or any combination thereof.
  • Certain UEs may utilize all or a subset of the components shown in Figure 13. 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 1302 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 1310.
  • the processing circuitry 1302 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 1302 may include multiple central processing units (CPUs).
  • the input/output interface 1306 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 1300.
  • 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 1308 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 1308 may further include power circuitry for delivering power from the power source 1308 itself, and/or an external power source, to the various parts of the UE 1300 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 1308.
  • Power circuitry may perform any formatting, converting, or other modification to the power from the power source 1308 to make the power suitable for the respective components of the UE 1300 to which power is supplied.
  • the memory 1310 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 1310 includes one or more application programs 1314, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 1316.
  • the memory 1310 may store, for use by the UE 1300, any of a variety of various operating systems or combinations of operating systems.
  • the memory 1310 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 1310 may allow the UE 1300 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 1310, which may be or comprise a device-readable storage medium.
  • Processing circuitry 1302 may be configured to communicate with an access network or other network using communication interface 1312.
  • Communication interface 1312 may comprise one or more communication subsystems and may include or be communicatively coupled to antenna 1322.
  • Communication interface 1312 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network).
  • Each transceiver may include transmitter 1318 and/or receiver 1320 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth).
  • transmitter 1318 and receiver 1320 may be coupled to one or more antennas (e.g., antenna 1322) and may share circuit components, software or firmware, or alternatively be implemented separately.
  • communication functions of communication interface 1312 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 CDMA (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 1312, via a wireless connection to a network node.
  • Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE.
  • the output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., an alert is sent when moisture is detected), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).
  • a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection.
  • the states of the actuator, the motor, or the switch may change.
  • the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.
  • a UE when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare.
  • loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door/window sensor, a flood/moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-t
  • AR Augmented
  • a UE may represent a machine or other device that performs monitoring and/or measurements and transmits the results of such monitoring and/or measurements to another UE and/or a network node.
  • the UE may in this case be an M2M device, which may in a 3 GPP context be referred to as an MTC device.
  • the UE may implement the 3 GPP 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 14 shows a network node 1400 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 NRNodeBs (gNBs)).
  • APs access points
  • BSs base stations
  • Node Bs Node Bs
  • eNBs evolved Node Bs
  • gNBs NRNodeBs
  • 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 1400 includes a processing circuitry 1402, a memory 1404, a communication interface 1406, and a power source 1408.
  • the network node 1400 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 1400 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 1400 may be configured to support multiple radio access technologies (RATs).
  • RATs radio access technologies
  • some components may be duplicated (e.g., separate memory 1404 for different RATs) and some components may be reused (e.g., a same antenna 1410 may be shared by different RATs).
  • the network node 1400 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1400, 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 1400.
  • RFID Radio Frequency Identification
  • the processing circuitry 1402 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 1400 components, such as the memory 1404, to provide network node 1400 functionality.
  • the processing circuitry 1402 includes a system on a chip (SOC). In some embodiments, the processing circuitry 1402 includes one or more of radio frequency (RF) transceiver circuitry 1412 and baseband processing circuitry 1414. In some embodiments, the radio frequency (RF) transceiver circuitry 1412 and the baseband processing circuitry 1414 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 1412 and baseband processing circuitry 1414 may be on the same chip or set of chips, boards, or units.
  • SOC system on a chip
  • the memory 1404 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 1402.
  • 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-
  • the memory 1404 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and/or other instructions (collectively denoted computer program product 1404a) capable of being executed by the processing circuitry 1402 and utilized by the network node 1400.
  • the memory 1404 may be used to store any calculations made by the processing circuitry 1402 and/or any data received via the communication interface 1406.
  • the processing circuitry 1402 and memory 1404 is integrated.
  • the communication interface 1406 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 1406 comprises port(s)/terminal(s) 1416 to send and receive data, for example to and from a network over a wired connection.
  • the communication interface 1406 also includes radio front-end circuitry 1418 that may be coupled to, or in certain embodiments a part of, the antenna 1410. Radio front-end circuitry 1418 comprises filters 1420 and amplifiers 1422.
  • the radio front-end circuitry 1418 may be connected to an antenna 1410 and processing circuitry 1402.
  • the radio front-end circuitry may be configured to condition signals communicated between antenna 1410 and processing circuitry 1402.
  • the radio front-end circuitry 1418 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection.
  • the radio frontend circuitry 1418 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1420 and/or amplifiers 1422.
  • the radio signal may then be transmitted via the antenna 1410.
  • the antenna 1410 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1418.
  • the digital data may be passed to the processing circuitry 1402.
  • the communication interface may comprise different components and/or different combinations of components.
  • the network node 1400 does not include separate radio front-end circuitry 1418, instead, the processing circuitry 1402 includes radio front-end circuitry and is connected to the antenna 1410.
  • the processing circuitry 1402 includes radio front-end circuitry and is connected to the antenna 1410.
  • all or some of the RF transceiver circuitry 1412 is part of the communication interface 1406.
  • the communication interface 1406 includes one or more ports or terminals 1416, the radio frontend circuitry 1418, and the RF transceiver circuitry 1412, as part of a radio unit (not shown), and the communication interface 1406 communicates with the baseband processing circuitry 1414, which is part of a digital unit (not shown).
  • the antenna 1410 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals.
  • the antenna 1410 may be coupled to the radio front-end circuitry 1418 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly.
  • the antenna 1410 is separate from the network node 1400 and connectable to the network node 1400 through an interface or port.
  • the antenna 1410, communication interface 1406, and/or the processing circuitry 1402 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 1410, the communication interface 1406, and/or the processing circuitry 1402 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 1408 provides power to the various components of network node 1400 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component).
  • the power source 1408 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 1400 with power for performing the functionality described herein.
  • the network node 1400 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 1408.
  • the power source 1408 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 1400 may include additional components beyond those shown in Figure 14 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 1400 may include user interface equipment to allow input of information into the network node 1400 and to allow output of information from the network node 1400. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1400.
  • Figure 15 is a block diagram of a host 1500, which may be an embodiment of the host 1216 of Figure 12, in accordance with various aspects described herein.
  • the host 1500 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 1500 may provide one or more services to one or more UEs.
  • the host 1500 includes processing circuitry 1502 that is operatively coupled via a bus 1504 to an input/output interface 1506, a network interface 1508, a power source 1510, and a memory 1512.
  • processing circuitry 1502 that is operatively coupled via a bus 1504 to an input/output interface 1506, a network interface 1508, a power source 1510, and a memory 1512.
  • 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 13 and 14, such that the descriptions thereof are generally applicable to the corresponding components of host 1500.
  • the memory 1512 may include one or more computer programs including one or more host application programs 1514 and data 1516, which may include user data, e.g., data generated by a UE for the host 1500 or data generated by the host 1500 for a UE.
  • Embodiments of the host 1500 may utilize only a subset or all of the components shown.
  • the host application programs 1514 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 1514 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 1500 may select and/or indicate a different host for over-the-top services for a UE.
  • the host application programs 1514 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 16 is a block diagram illustrating a virtualization environment 1600 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 1600 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 1602 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment 1600 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.
  • Hardware 1604 includes processing circuitry, memory that stores software and/or instructions (collectively denoted computer program product 1604a) 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 1606 (also referred to as hypervisors or virtual machine monitors, VMMs), provide VMs 1608a-b (one or more of which may be generally referred to as VMs 1608), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein.
  • the virtualization layer 1606 may present a virtual operating platform that appears like networking hardware to the VMs 1608.
  • VMs 1608 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 1606.
  • VMs 1608 may be implemented on one or more of VMs 1608, 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
  • VM 1608 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 1608, and that part of hardware 1604 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 1608 on top of hardware 1604 and corresponds to application 1602.
  • Hardware 1604 may be implemented in a standalone network node with generic or specific components. Hardware 1604 may implement some functions via virtualization. Alternatively, hardware 1604 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 1610, which, among others, oversees lifecycle management of applications 1602.
  • hardware 1604 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 1612 which may alternatively be used for communication between hardware nodes and radio units.
  • Figure 17 shows a communication diagram of a host 1702 communicating via a network node 1704 with a UE 1706 over a partially wireless connection in accordance with some embodiments.
  • host 1702 Like host 1500, embodiments of host 1702 include hardware, such as a communication interface, processing circuitry, and memory.
  • the host 1702 also includes software, which is stored in or accessible by the host 1702 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 1706 connecting via an over-the-top (OTT) connection 1750 extending between the UE 1706 and host 1702.
  • OTT over-the-top
  • the network node 1704 includes hardware enabling it to communicate with the host 1702 and UE 1706.
  • the connection 1760 may be direct or pass through a core network (like core network 1206 of Figure 12) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks.
  • a core network like core network 1206 of Figure 12
  • 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 1706 includes hardware and software, which is stored in or accessible by UE 1706 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 1706 with the support of the host 1702.
  • 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 1706 with the support of the host 1702.
  • an executing host application may communicate with the executing client application via the OTT connection 1750 terminating at the UE 1706 and host 1702.
  • 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 1750 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
  • OTT connection 1750 may extend via a connection 1760 between host 1702 and network node 1704 and via a wireless connection 1770 between network node 1704 and UE 1706 to provide the connection between host 1702 and UE 1706.
  • Connection 1760 and wireless connection 1770, over which OTT connection 1750 may be provided, have been drawn abstractly to illustrate the communication between host 1702 and UE 1706 via network node 1704, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • host 1702 provides user data, which may be performed by executing a host application.
  • the user data is associated with a particular human user interacting with UE 1706.
  • the user data is associated with a UE 1706 that shares data with host 1702 without explicit human interaction.
  • host 1702 initiates a transmission carrying the user data towards UE 1706.
  • the host 1702 may initiate the transmission responsive to a request transmitted by UE 1706.
  • the request may be caused by human interaction with UE 1706 or by operation of the client application executing on UE 1706.
  • the transmission may pass via network node 1704, in accordance with the teachings of the embodiments described throughout this disclosure.
  • network node 1704 transmits to UE 1706 the user data that was carried in the transmission that host 1702 initiated, in accordance with the teachings of the embodiments described throughout this disclosure.
  • UE 1706 receives the user data carried in the transmission, which may be performed by a client application executed on UE 1706 associated with the host application executed by the host 1702.
  • UE 1706 executes a client application which provides user data to host 1702.
  • the user data may be provided in reaction or response to the data received from host 1702.
  • UE 1706 may provide user data, which may be performed by executing the client application.
  • the client application may further consider user input received from the user via an input/output interface of UE 1706.
  • UE 1706 initiates, in step 1718, transmission of the user data towards the 1702 via network node 1704.
  • network node 1704 receives user data from UE 1706 and initiates transmission of the received user data towards host 1702.
  • step 1722 host 1702 receives the user data carried in the transmission initiated by UE 1706.
  • One or more of the various embodiments improve the performance of OTT services provided to UE 1706 using OTT connection 1750, in which wireless connection 1770 forms the last segment. More precisely, the teachings of these embodiments facilitate a RAN node arranged in a distributed architecture to perform MDT measurements that are time-aligned with QoE measurements performed by a UE. In this manner, embodiments facilitate MDT measurements with corresponding QoE measurements that facilitate detection, interpretation, and/or understanding of possible application-related issues, as well as QoE measurements with corresponding MDT measurements that facilitate detection, interpretation, and/or understanding of possible radio- and network-related issues. Availability of time-aligned measurements can lead to improved network performance experienced by OTT services, which increases the value of such OTT services to end users and service providers.
  • factory status information may be collected and analyzed by host 1702.
  • host 1702 may process audio and video data which may have been retrieved from a UE for use in creating maps.
  • host 1702 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights).
  • host 1702 may store surveillance video uploaded by a UE.
  • host 1702 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs.
  • host 1702 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and/or transmitting data.
  • a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve.
  • the measurement procedure and/or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of host 1702 and/or UE 1706.
  • sensors (not shown) may be deployed in or in association with other devices through which OTT connection 1750 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above or by supplying values of other physical quantities from which software may compute or estimate the monitored quantities.
  • the reconfiguring of OTT connection 1750 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of network node 1704. Such procedures and functionalities may be known and practiced in the art.
  • measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by host 1702.
  • the measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 1750 while monitoring propagation times, errors, etc.
  • the term unit can have conventional meaning in the field of electronics, electrical devices and/or electronic devices and can include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.
  • any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses.
  • Each virtual apparatus may comprise a number of these functional units.
  • These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include Digital Signal Processor (DSPs), special-purpose digital logic, and the like.
  • the processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as Read Only Memory (ROM), Random Access Memory (RAM), cache memory, flash memory devices, optical storage devices, etc.
  • Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein.
  • the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.
  • device and/or apparatus can be represented by a semiconductor chip, a chipset, or a (hardware) module comprising such chip or chipset; this, however, does not exclude the possibility that a functionality of a device or apparatus, instead of being hardware implemented, be implemented as a software module such as a computer program or a computer program product comprising executable software code portions for execution or being run on a processor.
  • functionality of a device or apparatus can be implemented by any combination of hardware and software.
  • a device or apparatus can also be regarded as an assembly of multiple devices and/or apparatuses, whether functionally in cooperation with or independently of each other.
  • devices and apparatuses can be implemented in a distributed fashion throughout a system, so long as the functionality of the device or apparatus is preserved. Such and similar principles are considered as known to a skilled person.
  • Embodiments of the techniques and apparatus described herein also include, but are not limited to, the following enumerated examples:
  • a method performed by a first unit or function of a radio access network (RAN) node comprising: receiving from another node or function associated with the RAN a measurement configuration that includes the following: a first configuration for quality-of-experience (QoE) measurements; a second configuration for minimization of drive testing (MDT) measurements; and an indication that the QoE measurements and the MDT measurements should be time-aligned; sending the first configuration to a user equipment (UE) and storing the second configuration; receiving from the UE a first indication that an event associated with the QoE measurements has occurred; and in response to the first indication, sending the second configuration or an associated command to one or more second units or functions of the RAN node.
  • QoE quality-of-experience
  • MDT minimization of drive testing
  • A3 The method of any of embodiments A1-A2, wherein the event is one of the following: initiation of a UE application session with characteristics related to the first configuration; or an event that occurs after initiation of the UE application session.
  • A4 The method of any of embodiments A1-A3, wherein the other node or function associated with the RAN is one of the following: an operations administration maintenance (0AM) node coupled to the RAN; or a node or function of a core network (CN) coupled to the RAN.
  • an operations administration maintenance (0AM) node coupled to the RAN
  • CN core network
  • A5 The method of any of embodiments A1-A4, wherein the measurement configuration includes a plurality of second configurations of MDT measurements and an indication of which of the second configurations should be time-aligned with the QoE measurements.
  • A6 The method of any of embodiments A1-A5, wherein a different portion of the second configuration is sent to each of a plurality of second units or functions of the RAN node.
  • A7 The method of any of embodiments A1-A6, further comprising, after sending the second configuration or the associated command, receiving from the UE a second indication that QoE measurements for the first configuration have ended, stopped, or paused.
  • A9 The method of embodiment A8, further comprising: after sending the command, receiving from the UE a third indication that QoE measurements for the first configuration have restarted or resumed; and sending one of the following to each of the second units or functions: the first configuration; an updated first configuration; or a command to activate the first configuration and resume the QoE measurements.
  • Al 1 The method of any of embodiments A1-A10, further comprising upon receiving the second configuration, sending the second configuration to the one or more second units or functions together with a command to maintain the second configuration in an inactive state, wherein a command to activate the second configuration is sent in response to the receiving the first indication from the UE.
  • A12 The method of any of embodiments Al-Al l, further comprising receiving, from the one or more second units or functions, results of the MDT measurements performed according to the second configuration.
  • A13 The method of embodiment A12, wherein: the second configuration is received and the MDT measurements are initiated before the first configuration is received; and the method further comprises performing one of the following: pausing the MDT measurements upon receiving the first configuration; or appending to the results of the MDT measurements an indication that QoE measurements were initiated upon receiving the first configuration.
  • A14 The method of any of embodiments A1-A13, wherein the first unit or function is a centralized unit control plane (CU-CP) and the one or more second units or functions including one of more of the following: a centralized unit user plane (CU-UP) and one or more distributed units (DU).
  • CU-CP centralized unit control plane
  • CU-UP centralized unit user plane
  • DU distributed units
  • a method performed by a second unit or function of a radio access network (RAN) node comprising: receiving, from a first unit or function of the RAN node, a configuration for minimization of drive testing (MDT) measurements that should be time-aligned with quality-of-experience (QoE) measurements performed by a user equipment (UE); initiating time-aligned MDT measurements in accordance with the second configuration; and sending results of the time-aligned MDT measurements to the first unit or function.
  • MDT drive testing
  • QoE quality-of-experience
  • invention B2 further comprising receiving one of the following commands from the first unit or function: a command to release the first configuration; or a command to maintain the first configuration in an inactive state, wherein the time-aligned MDT measurements are stopped or paused based on the command.
  • embodiment B3 further comprising subsequently receiving one of the following information from the first unit or function: the configuration; an updated configuration for MDT measurements; or a command to activate the configuration and resume the QoE measurements, wherein the time-aligned MDT measurements are started, restarted, or resumed based on the received information.
  • a first unit or function of a radio access network (RAN) node comprising: communication interface circuitry configured to communicate with one or more second units or functions of the RAN node and with 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 A1-A14.
  • RAN radio access network
  • a first unit or function of a radio access network (RAN) node the first unit or function being configured to perform operations corresponding to any of the methods of embodiments A1-A14.
  • RAN radio access network
  • a non-transitory, computer-readable medium storing computer-executable instructions that, when executed by processing circuitry associated with a first unit or function of a radio access network (RAN) node, configure the first unit or function to perform operations corresponding to any of the methods of embodiments A1-A14.
  • RAN radio access network
  • a computer program product comprising computer-executable instructions that, when executed by processing circuitry associated with a first unit or function of a radio access network (RAN) node, configure the first unit or function to perform operations corresponding to any of the methods of embodiments A1-A14.
  • RAN radio access network
  • a second unit or function of a radio access network (RAN) node comprising: communication interface circuitry configured to communicate with a first unit or function of the RAN node and with 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 B1-B5.
  • RAN radio access network
  • a second unit or function of a radio access network (RAN) node being configured to perform operations corresponding to any of the methods of embodiments B1-B5.
  • RAN radio access network
  • a non-transitory, computer-readable medium storing computer-executable instructions that, when executed by processing circuitry associated with a second unit or function of a radio access network (RAN) node, configure the second unit or function to perform operations corresponding to any of the methods of embodiments B1-B5.
  • RAN radio access network
  • a computer program product comprising computer-executable instructions that, when executed by processing circuitry associated with a second unit or function of a radio access network (RAN) node, configure the second unit or function to perform operations corresponding to any of the methods of embodiments B1-B5.
  • RAN radio access network

Landscapes

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

Abstract

Les modes de réalisation concernent des procédés exécutés par une première unité ou fonction d'un nœud de RAN. De tels procédés comprennent les étapes consistant à : recevoir (1010) d'un autre nœud ou fonction en association avec le RAN une configuration de mesures contenant une première configuration de mesures de QoE, une seconde configuration de mesures de MDT et une indication précisant que les mesures de QoE et de MDT doivent être alignées dans le temps ; envoyer (1020) la première configuration à un UE et stocker la seconde configuration ; recevoir (1030) de l'UE une première indication précisant qu'un événement associé aux mesures de QoE s'est produit ; et en réponse à la première indication, envoyer (1040) la seconde configuration ou une instruction associée à une ou plusieurs secondes unités ou fonctions du nœud de RAN. D'autres modes de réalisation concernent des premières unités ou fonctions du nœud de RAN qui sont configurées pour exécuter de tels procédés.
PCT/SE2023/050004 2022-01-06 2023-01-03 Mesures de couche radio et de couche application alignées dans le temps WO2023132776A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202263297200P 2022-01-06 2022-01-06
US63/297,200 2022-01-06

Publications (1)

Publication Number Publication Date
WO2023132776A1 true WO2023132776A1 (fr) 2023-07-13

Family

ID=84981797

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2023/050004 WO2023132776A1 (fr) 2022-01-06 2023-01-03 Mesures de couche radio et de couche application alignées dans le temps

Country Status (1)

Country Link
WO (1) WO2023132776A1 (fr)

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "The Alignment of Radio-related Measurements and QoE Measurements", vol. RAN WG3, no. Online; 20211101 - 20211111, 22 October 2021 (2021-10-22), XP052067734, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG3_Iu/TSGR3_114-e/Docs/R3-214732.zip R3-214732 - The Alignment of Radio-Related Measurements and QoE Measurements.docx> [retrieved on 20211022] *
ZTE ET AL: "(TP for 38.401) Alignment of MDT and QoE Measurements", vol. RAN WG3, no. Online; 20211101 - 20211111, 22 October 2021 (2021-10-22), XP052068647, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG3_Iu/TSGR3_114-e/Docs/R3-215668.zip R3-215668 (TP for 38.401) Alignment of MDT and QoE Measurements.doc> [retrieved on 20211022] *
ZTE ET AL: "Stage 2 TP to 38.300 BL CR on QoE", vol. RAN WG3, no. E-meeting; 20211101 - 20211111, 15 November 2021 (2021-11-15), XP052098514, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG3_Iu/TSGR3_114-e/Docs/R3-216150.zip R3-216150 Stage 2 TP to 38.300 BL CR on QoE.docx> [retrieved on 20211115] *

Similar Documents

Publication Publication Date Title
WO2023132776A1 (fr) Mesures de couche radio et de couche application alignées dans le temps
WO2024005702A1 (fr) Mesures de couche radio et de couche application alignées dans le temps pour connectivité double
US20240172074A1 (en) Handling of User Equipment (UE) Context Information after Inter-System Handover
WO2023027619A1 (fr) Gestion de mesures de couche d&#39;application configurées pendant un transfert intercellulaire
WO2023022645A1 (fr) Gestion de mesures de couche d&#39;application configurées en réponse à un message d&#39;établissement de connexion
WO2023080818A1 (fr) Détection et récupération de défaillance de faisceau pour un groupe de cellules secondaires (scg) désactivé
WO2023132774A1 (fr) Gestion de déclencheurs pour rapport qoe visible par ran
WO2023224527A1 (fr) Distribution de mesures de qoe visibles par ran
WO2023277752A1 (fr) Rapport de reconfigurations erronées
WO2024025449A1 (fr) Rapport de défaillances radio avec informations de relaxation rlm/bld
WO2023014254A1 (fr) Rapport de libération de réseau initiée par un ue
WO2023069000A1 (fr) Gestion de configurations de qualité d&#39;expérience (qoe) dépassant un nombre maximal
WO2023128854A1 (fr) Activation d&#39;un groupe de cellules secondaires (scg) déclenchée par un équipement utilisateur (ue) avec des informations radio
WO2023204748A1 (fr) Informations d&#39;assistance d&#39;équipement utilisateur (ue) avec groupe de cellules secondaires (scg) désactivé
WO2023014258A1 (fr) Prédiction et gestion proactive de défaillances de liaison radio (rlf)
WO2024028840A1 (fr) Rapport d&#39;informations d&#39;assistance d&#39;équipement utilisateur pour faciliter des économies d&#39;énergie de réseau d&#39;accès radio
WO2024107095A1 (fr) Rapport de qualité d&#39;expérience au niveau d&#39;un groupe de cellules secondaires désactivé
WO2024107093A1 (fr) Rapport de qualité d&#39;expérience, et rapport de qualité d&#39;expérience visible de réseau d&#39;accès radio lors de défaillances de la liaison radio dans une double connectivité new radio
WO2024035293A1 (fr) Sélection d&#39;équipement utilisateur (ue) de cellules candidates à mesurer pour une mobilité inter-cellules l1/l2
WO2023136764A1 (fr) Procédés de gestion de journalisation de différents types de mesures dans des rapports son
WO2023218383A1 (fr) Systèmes et procédés pour permettre une configuration par service pour mt-sdt
WO2023113670A1 (fr) Fonctionnement d&#39;un équipement utilisateur (ue) avec une configuration d&#39;économie d&#39;énergie d&#39;une station de base
WO2023148335A1 (fr) Configurabilité améliorée pour planification semi-persistante et autorisations configurées
EP4371368A1 (fr) Prévention de désadaptation d&#39;états de contrôle de ressources radio (rrc) entre un réseau et un équipement utilisateur
WO2023132764A1 (fr) Mises à jour de couverture coordonnées pour nœuds de réseau d&#39;accès radio à architecture distribuée

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

Country of ref document: EP

Kind code of ref document: A1