WO2023218383A1 - Systèmes et procédés pour permettre une configuration par service pour mt-sdt - Google Patents

Systèmes et procédés pour permettre une configuration par service pour mt-sdt Download PDF

Info

Publication number
WO2023218383A1
WO2023218383A1 PCT/IB2023/054849 IB2023054849W WO2023218383A1 WO 2023218383 A1 WO2023218383 A1 WO 2023218383A1 IB 2023054849 W IB2023054849 W IB 2023054849W WO 2023218383 A1 WO2023218383 A1 WO 2023218383A1
Authority
WO
WIPO (PCT)
Prior art keywords
transmission
expected
response
network node
per
Prior art date
Application number
PCT/IB2023/054849
Other languages
English (en)
Inventor
Luca FELTRIN
Revathy Narayanan
Henrik Enbuske
Jan Christoffersson
Andreas HÖGLUND
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 WO2023218383A1 publication Critical patent/WO2023218383A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release

Definitions

  • the present disclosure generally relates to Small Data Transmissions (SDTs).
  • SDTs Small Data Transmissions
  • NR New Radio
  • the device can be in RRC idle, in RRC connected or in RRC inactive state.
  • the data transmission was possible only in RRC connected. Therefore, UE must be moved to a connected state from idle or inactive states every time there is data to be transferred between UE and gNB. This leads to significant signaling overhead and power consumption, in particular for UEs that need infrequent transmission of small data packets.
  • inactive state the UE has established RRC context and core network connection. Therefore, the transition from inactive to connected state is relatively fast and requires less signaling, compared to the transition from idle to connected.
  • 3GPP has approved a new study item on NR small data transmissions in RRC inactive state.
  • MO-SDT Mobile Originated Small Data Transmission
  • the new Release 18 expects Mobile Terminated (MT) SDT, that is DL-triggered small data, to allow similar benefits, i.e., 1) reducing signalling overhead and UE power consumption by not transitioning to RRC_CONNECTED and reducing latency by allowing fast transmission of (small and infrequent) packets, e.g., for positioning.
  • MT Mobile Terminated
  • MT-SDT addresses application use-cases by typically reducing the overall signalling overhead and UE power consumption.
  • the overall skeleton of MT-SDT involves an initial paging trigger followed by a DL data transmission from the gNB. This is followed by an optional UL transmission from the UE end, after which the connection can be released.
  • the UL transmission is optional, it would be extremely efficient from an energy point of view for the gNB to know in advance whether or not to expect an UL reply, i.e., it is beneficial to allow to UE to go back a configured energy saving state as quickly as possible after the procedure has been terminated.
  • Radio Bearer specific RAI RRC variant
  • RRCSetupComplete-IEs : : SEQUENCE ⁇ selectedPLMN-Identity INTEGER (L.maxPLMN), registeredAMF RegisteredAMF OPTIONAL, guami-Type ENUMERATED ⁇ native, mapped ⁇ OPTIONAL, s-NSSAI-List SEQUENCE (SIZE (L.maxNrofS-NSSAI)) OF S-NSSAI
  • OPTIONAL dedicatedNAS-Message DedicatedNAS-Message, ng-5G-S-TMSI-Value CHOICE ⁇ ng-5G-S-TMSI NG-5G-S-TMSI, ng-5G-S-TMSI-Part2 BIT STRING (SIZE (9)) ⁇ OPTIONAL, lateN onCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension RRCSetupComplete-v 1610-IEs OPTIONAL
  • RRCSetupComplete-vl610-IEs SEQUENCE ⁇ iab-NodeIndication-rl6 ENUMERATED ⁇ true ⁇ OPTIONAL, idleMeasAvailable-rl6 ENUMERATED ⁇ true ⁇ OPTIONAL, ue-MeasurementsAvailable-r 16 UE-MeasurementsAvailable-r 16 OPTIONAL, mobilityHistoryAvail-rl6 ENUMERATED ⁇ true ⁇ OPTIONAL, mobilityState-rl6 ENUMERATED ⁇ normal, medium, high, spare ⁇ OPTIONAL, nonCriticalExtension RRCSetupComplete-vXXXX-IEs
  • OPTIONAL RRCSetupComplete-vXXXX-IEs :: SEQUENCE ⁇ expectedTraffic SEQUENCE (SIZE (1..FFS)) OF ExpectedRadioBearerTraffic-rl7 OPTIONAL, nonCriticalExtension SEQUENCER OPTIONAL
  • ExpectedRadioBearerTraffic-rl7 SEQUENCE ⁇ rb-Identity CHOICE ⁇ drb-Id DRB-Identity, srb-Id SRB-Identity
  • Radio Bearer (RB) specific RAI (MAC CE variant):
  • the UE provides information for “m” Radio Bearer with this variable-length MAC
  • CE For each RB one octet is used. In each octet the “S” bit indicates if the Radio Bearer is an SRB or DRB. RB Identity (5 bit) provide the RB identity, while the last 2 bits are used to provide the RAI as shown in Figure 1.
  • SDAP Service Data Adaptation Protocol
  • QoS Quality of Service
  • the UE For UEs supporting reflective QoS, when the UE receives a DL SDAP PDU from lower layers it simply checks the header to forward the data to the right QoS flow. In case the header is not present, or if the DRB configuration does not match the QoS identity in the header, the sub-layer modifies the mapping accordingly.
  • Figure 2 illustrates a DL SDAP Data PDU format with SDAP header.
  • PDU has the following structure when the SDAP header is configured.
  • QFI represents the QoS Flow Identity (6 bit)
  • RDI when set, indicates that the QoS flow to DRB mapping rule should be updated
  • Rel-17 SDT UEs currently do not support reflective QoS feature, but this could be introduced in the new Rel-18 MT-SDT, making SDAP based QoS flow matching for DRBs a feasible option.
  • a method performed by a User Equipment (UE) for enabling per-service configuration for MT-SDT includes: determining information on an expected Uplink (UL) response to a Downlink (DL) transmission from a gNB; sending, to the gNB, an indication regarding the expected UL response; receiving a DL transmission; and responding to the DL transmission based on the expected UL response.
  • the expected UL response can be configured for a particular service, e.g., per DRB or QoS-flow on RAN level. This means the UE can now know in advance whether a UL is expected once it receives a DL from the gNB, thereby enabling a possible early release of the UE for some applications to save power.
  • the solution proposes specifying MT-SDT Release Assistance Indication (RAI) which can be configured per DRB or QoS flow.
  • RAI MT-SDT Release Assistance Indication
  • a 5G-specific transmission pattern can be defined based on the QoS flow characteristics.
  • the rationale for this is that for mobile originated traffic, the UE can have a good knowledge of whether a response in DL is expected on application-layer after the UL data transmission (e.g., an indication could be sent down from the application layer to RRC or MAC in the UE as assistance information).
  • RRC Radio Resource Control
  • a “per service” configuration is a better option, where an expected UL response can be configured for a particular service, e.g., per DRB or QoS-flow on RAN level, if a UL response is to be expected or not to be able to timely release the UE to save power. (Unlike the existing RAI, which gNB receives from the UE, this new RAI per DRB is instead received from CN.) [0021] Some embodiments herein introduce a MT-SDT Release Assistance Indication that is configurable per DRB or QoS flow. Alternatively, a 5G-specific transmission pattern can be defined based on the QoS flow characteristics. The two options aim at providing information on whether or not to expect an UL transmission from the UE in response to the DL transmission from the gNB.
  • Figure 1 illustrates a Radio Bearer (RB) Identity (5 bit) provides the RB identity, while the last 2 bits are used to provide the Release Assistance Indication (RAI);
  • RB Radio Bearer
  • RAI Release Assistance Indication
  • Figure 2 illustrates a Downlink (DE) Service Data Adaptation Protocol (SDAP) Data Protocol Data Unit (PDU) format with SDAP header;
  • SDAP Service Data Adaptation Protocol
  • PDU Protocol Data Unit
  • Figure 3 illustrates a User Plane Protocol Stack
  • Figure 4 illustrates that a gNB needs to keep waiting for the User Equipment (UE) to ask for a scheduling grant until a configured time Rel-18 Mobile Terminated (MT)- Small Data Transmission (SDT) involves an initial paging trigger followed by a DL and optional Uplink (UL) transmission;
  • UE User Equipment
  • MT Mobile Terminated
  • SDT Small Data Transmission
  • Figure 5A illustrates a method performed by a UE for enabling per-service configuration for MT-SDT, according to some embodiments of the current disclosure
  • FIG. 5B illustrates configuring RAI on Quality of Service (QoS) flow basis using Medium Access Control (MAC) Control Element (CE), according to some embodiments of the current disclosure;
  • MAC Medium Access Control
  • CE Control Element
  • Figure 6 illustrates configuring RAI based on the PDU session ID, according to some embodiments of the current disclosure
  • Figure 7 illustrates the setting of Reflective QoS to DRB mapping Indication (RD I), Reflective QoS Identifier (RQI) or a combination used in the existing DL SDAP Data PDU format to configure or indicate RAI for a corresponding QoS Flow Identity (QFI), according to some embodiments of the current disclosure;
  • RD I Reflective QoS to DRB mapping Indication
  • RQI Reflective QoS Identifier
  • QFI QoS Flow Identity
  • Figure 8 shows an example of a communication system in accordance with some embodiments
  • Figure 9 shows a UE in accordance with some embodiments.
  • Figure 10 shows a network node in accordance with some embodiments
  • Figure 11 is a block diagram of a host, which may be an embodiment of the host of
  • Figure 12 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized.
  • Figure 13 shows a communication diagram of a host communicating via a network node with a UE over a partially wireless connection in accordance with some embodiments.
  • Figure 4 illustrates that a gNB needs to keep waiting for the User Equipment (UE) to ask for a scheduling grant until a configured time Rel-18 Mobile Terminated (MT)- Small Data Transmission (SDT) involves an initial paging trigger followed by a Downlink (DL) and optional Uplink (UL) transmission.
  • MT Mobile Terminated
  • SDT Small Data Transmission
  • optional UL transmission means that the gNB needs to wait (indefinitely or based on a configured timer) until receiving a scheduling request and associated UL response from the UE.
  • a method performed by a UE for enabling per-service configuration for MT-SDT includes: determining information on an expected UL response to a DL transmission from a gNB; sending, to the gNB, an indication regarding the expected UL response; receiving a DL transmission; and responding to the DL transmission based on the expected UL response.
  • the expected UL response can be configured for a particular service, e.g., per DRB or QoS-flow on RAN level. This means the UE can now know in advance whether a UL is expected once it receives a DL from the gNB, thereby enabling a possible early release of the UE for some applications to save power.
  • the solution proposes specifying MT-SDT Release Assistance Indication (RAI) which can be configured per DRB or QoS flow.
  • RAI MT-SDT Release Assistance Indication
  • a 5G-specific transmission pattern can be defined based on the QoS flow characteristics.
  • the rationale for this is that for mobile originated traffic, the UE can have a good knowledge of whether a response in DL is expected on application-layer after the UL data transmission (e.g., an indication could be sent down from the application layer to RRC or MAC in the UE as assistance information).
  • RRC Radio Resource Control
  • a “per service” configuration is a better option, where an expected UL response can be configured for a particular service, e.g., per DRB or QoS-flow on RAN level, if a UL response is to be expected or not to be able to timely release the UE to save power. (Unlike the existing RAI, which gNB receives from the UE, this new RAI per DRB is instead received from CN.) [0041] In some embodiments, a MT-SDT Release Assistance Indication that is configurable per DRB or QoS flow. Alternatively, a 5G-specific transmission pattern can be defined based on the QoS flow characteristics. The two options aim at providing information on whether or not to expect an UL transmission from the UE in response to the DL transmission from the gNB.
  • the expected UL response can be configured for a particular service, e.g., per DRB or QoS-flow on RAN level. This means the UE can now know in advance whether a UL is expected once it receives a DL from the gNB, thereby enabling a possible early release of the UE for some applications to save power.
  • Figure 5A illustrates a method performed by a UE for enabling per-service configuration for MT-SDT, according to some embodiments of the current disclosure.
  • the method includes: determining (step 500) information on an expected UL response to a DL transmission from a gNB; sending (step 502), to the gNB, an indication regarding the expected UL response; receiving (step 504) a DL transmission; and responding (step 506) to the DL transmission based on the expected UL response.
  • a previous disclosure covered the case of Mobile Originated data, and thus describes the gNB behavior in case UL data from an RB configured with a RAI is received.
  • the RAI can contain the information on the radio bearer.
  • the gNB depending on which RB the DL data is directed to, decides whether UL data is to be expected from the UE or not.
  • the UE AS with suspended RB has no knowledge of which RB a QoS flow maps to before processing in SDAP.
  • NAS/application is not aware of any DRB/SDT mapping. Therefore, it is important to figure out how this information could be handled.
  • the indication when received, the indication is processed by SDAP to determine if QoS flows belong to a suspended SDT-DRB at the initiation of the MT-SDT session.
  • An indication from AS to NAS or Application may then be provided by the AS layer in the UE using the SDT RAI configuration/indication, i.e., NAS or an Application at higher layers can be made aware of an ongoing MT-SDT session in which expected UL data (response) can be transmitted resuming an RB for a single or a group of QoS Flows when AS is configured with QoS Flow specific RAI.
  • the same idea can be extended to configure the RAI on a QoS flow basis instead of an RB basis.
  • the following IE can be used in case of an RRC-based signalling (addition in bold text).
  • RRCSetupComplete-IEs : : SEQUENCE ⁇ selectedPLMN-Identity INTEGER (L.maxPLMN), registeredAMF RegisteredAMF OPTIONAL, guami-Type ENUMERATED ⁇ native, mapped ⁇ OPTIONAL, s-NSSAI-List SEQUENCE (SIZE (L.maxNrofS-NSSAI)) OF S-NSSAI
  • OPTIONAL dedicatedNAS-Message DedicatedNAS-Message, ng-5G-S-TMSI-Value CHOICE ⁇ ng-5G-S-TMSI NG-5G-S-TMSI, ng-5G-S-TMSI-Part2 BIT STRING (SIZE (9)) ⁇ OPTIONAL, lateN onCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension RRCSetupComplete-v 1610-IEs OPTIONAL
  • RRCSetupComplete-vl610-IEs SEQUENCE ⁇ iab-NodeIndication-rl6 ENUMERATED ⁇ true ⁇ OPTIONAL, idleMeasAvailable-rl6 ENUMERATED ⁇ true ⁇ OPTIONAL, ue-MeasurementsAvailable-r 16 UE-MeasurementsAvailable-r 16 OPTIONAL, mobilityHistoryAvail-rl6 ENUMERATED ⁇ true ⁇ OPTIONAL, mobilityState-r!6 ENUMERATED ⁇ normal, medium, high, spare ⁇ OPTIONAL, nonCriticalExtension RRCSetupComplete-vXXXX-IEs
  • RRCSetupComplete-vXXXX-IEs :: SEQUENCE ⁇ expectedTraffic SEQUENCE (SIZE (1..FFS)) OF ExpectedQFITraffic
  • Figure 5B illustrates configuring RAI on QoS flow basis using MAC CE.
  • CE in Figure 5B can be used in case of a MAC CE-based signalling.
  • the following IE can be used in case of an RRC-based signalling.
  • RRCSetupComplete-IEs : : SEQUENCE ⁇ selectedPLMN-Identity INTEGER (L.maxPLMN), registeredAMF RegisteredAMF OPTIONAL, guami-Type ENUMERATED ⁇ native, mapped ⁇ OPTIONAL, s-NSSAI-List SEQUENCE (SIZE (L.maxNrofS-NSSAI)) OF S-NSSAI
  • OPTIONAL dedicatedNAS-Message DedicatedNAS-Message, ng-5G-S-TMS LValue CHOICE ⁇ ng-5G-S-TMSI NG-5G-S-TMSI, ng-5G-S-TMSI-Part2 BIT STRING (SIZE (9)) ⁇ OPTIONAL, lateN onCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension RRCSetupComplete-v 1610-IEs OPTIONAL
  • RRCSetupComplete-vl610-IEs SEQUENCE ⁇ iab-NodeIndication-rl6 ENUMERATED ⁇ true ⁇ OPTIONAL, idleMeasAvailable-rl6 ENUMERATED ⁇ true ⁇ OPTIONAL, ue-MeasurementsAvailable-r 16 UE-MeasurementsAvailable-r 16 OPTIONAL, mobilityHistoryAvail-rl6 ENUMERATED ⁇ true ⁇ OPTIONAL, mobilityState-rl6 ENUMERATED ⁇ normal, medium, high, spare ⁇ OPTIONAL, nonCriticalExtension RRCSetupComplete-vXXXX-IEs
  • RRCSetupComplete-vXXXX-IEs :: SEQUENCE ⁇ expectedTraffic SEQUENCE (SIZE (1..FFS)) OF ExpectedPDUsessionTraffic OPTIONAL, nonCriticalExtension SEQUENCE ⁇ OPTIONAL
  • the gNB includes an SDAP header of one octet in the MT-SDT data.
  • the DL SDAP Data PDU format includes an alternative handling of the RDI or RQI bit setting in the UE SDAP so that the setting of those corresponds to a RAI configuration related to the QFLfield (QFI field representing the QoS Flow Identifier).
  • Figure 7 illustrates the setting of RDI, RQI or a combination used in the existing DL SDAP Data PDU format to configure or indicate RAI for a corresponding QFI.
  • a new 5G QoS Identifier (5QI) characteristic is defined (in
  • the legacy 5G QoS characteristics comprise the following characteristics:
  • One UL response is expected to a DL transmission
  • This new characteristic can be used to define new standardized 5QI values similar to what is done in Table 5.7.4-1 in TS 23.501.
  • the new standardized 5QI values can then be used to map a QFI to a QoS flow where e.g., no UL response is expected after a DL transmission.
  • the termination of the MT-SDT procedure is up to gNB. i.e., whether to use (Option
  • One embodiment involves purely network implementation, i.e., the gNB learns which QoS-flows typically involve UL responses and stores that information. For a new MT-SDT procedure, gNB would check the QFI in the header of the SDAP DL PDU and based on comparison to this stored information decide whether Option A or Option B should be applied for the MT-SDT procedure of this UE.
  • new signaling (e.g., see above) is specified in the signaling from CN to guide the gNB decision to determine which QoS-flows should use Option A and which should use Option B.
  • a table with the configured QoS-flows and a bit indicating Option A or B is signaled to gNB (i.e., preconfiguration).
  • new information is appended in the SDAP PDU header to indicate dynamically to gNB whether Option A or B should be used. In these examples, early termination of the MT-SDT procedure and early release of the UE would be possible already from the first transmission without any need of observation and learning in gNB.
  • Figure 8 shows an example of a communication system 800 in accordance with some embodiments.
  • the communication system 800 includes a telecommunication network 802 that includes an access network 804, such as a Radio Access Network (RAN), and a core network 806, which includes one or more core network nodes 808.
  • the access network 804 includes one or more access network nodes, such as network nodes 810A and 810B (one or more of which may be generally referred to as network nodes 810), or any other similar Third Generation Partnership Project (3GPP) access node or non-3GPP Access Point (AP).
  • 3GPP Third Generation Partnership Project
  • the network nodes 810 facilitate direct or indirect connection of User Equipment (UE), such as by connecting UEs 812A, 812B, 812C, and 812D (one or more of which may be generally referred to as UEs 812) to the core network 806 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 800 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 800 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.
  • the UEs 812 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 810 and other communication devices.
  • the network nodes 810 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 812 and/or with other network nodes or equipment in the telecommunication network 802 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 802.
  • the core network 806 connects the network nodes 810 to one or more hosts, such as host 816. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts.
  • the core network 806 includes one more core network nodes (e.g., core network node 808) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and/or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 808.
  • 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 816 may be under the ownership or control of a service provider other than an operator or provider of the access network 804 and/or the telecommunication network 802 and may be operated by the service provider or on behalf of the service provider.
  • the host 816 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 800 of Figure 8 enables connectivity between the UEs, network nodes, and hosts.
  • the communication system 800 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 Second, Third, Fourth, or Fifth Generation (2G, 3G, 4G, or 5G) standards, or any applicable future generation standard (e.g., Sixth Generation (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
  • the telecommunication network 802 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunication network 802 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 802. For example, the telecommunication network 802 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 Internet of Things (loT) services to yet further UEs.
  • URLLC Ultra Reliable Low Latency Communication
  • eMBB enhanced Mobile Broadband
  • mMTC massive Machine Type Communication
  • LoT massive Internet of Things
  • the UEs 812 are configured to transmit and/or receive information without direct human interaction.
  • a UE may be designed to transmit information to the access network 804 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 804.
  • a UE may be configured for operating in single- or multi-Radio Access Technology (RAT) or multi-standard mode.
  • RAT Radio Access Technology
  • a UE may operate with any one or combination of WiFi, New Radio (NR), and LTE, i.e., be configured for Multi-Radio Dual Connectivity (MR-DC), such as Evolved UMTS Terrestrial RAN (E-UTRAN) NR - Dual Connectivity (EN-DC).
  • MR-DC Multi-Radio Dual Connectivity
  • E-UTRAN Evolved UMTS Terrestrial RAN
  • EN-DC Dual Connectivity
  • a hub 814 communicates with the access network 804 to facilitate indirect communication between one or more UEs (e.g., UE 812C and/or 812D) and network nodes (e.g., network node 810B).
  • the hub 814 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs.
  • the hub 814 may be a broadband router enabling access to the core network 806 for the UEs.
  • the hub 814 may be a controller that sends commands or instructions to one or more actuators in the UEs.
  • the hub 814 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 814 may be a content source. For example, for a UE that is a Virtual Reality (VR) headset, display, loudspeaker or other media delivery device, the hub 814 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 814 then provides to the UE either directly, after performing local processing, and/or after adding additional local content.
  • the hub 814 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 814 may have a constant/persistent or intermittent connection to the network node 81 OB.
  • the hub 814 may also allow for a different communication scheme and/or schedule between the hub 814 and UEs (e.g., UE 812C and/or 812D), and between the hub 814 and the core network 806.
  • the hub 814 is connected to the core network 806 and/or one or more UEs via a wired connection.
  • the hub 814 may be configured to connect to a Machine-to-Machine (M2M) service provider over the access network 804 and/or to another UE over a direct connection.
  • M2M Machine-to-Machine
  • UEs may establish a wireless connection with the network nodes 810 while still connected via the hub 814 via a wired or wireless connection.
  • the hub 814 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 810B.
  • the hub 814 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and the network node 810B, 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 Internet Protocol (VoIP) phone, wireless local loop phone, desktop computer, Personal Digital Assistant (PDA), wireless camera, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, Laptop Embedded Equipment (LEE), Laptop Mounted Equipment (LME), smart device, wireless Customer Premise Equipment (CPE), vehicle-mounted or vehicle embedded/integrated wireless device, etc.
  • Other examples include any UE identified by the 3GPP, including a Narrowband Internet of Things (NB-IoT) UE, a Machine Type Communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.
  • NB-IoT Narrowband Internet of Things
  • MTC Machine Type Communication
  • eMTC
  • a UE may support Device-to-Device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), Vehicle-to- Vehicle (V2V), Vehicle-to-Infrastructure (V2I), or Vehicle- to-Everything (V2X).
  • D2D Device-to-Device
  • DSRC Dedicated Short-Range Communication
  • V2V Vehicle-to- Vehicle
  • V2I Vehicle-to-Infrastructure
  • V2X Vehicle- to-Everything
  • a UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device.
  • a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller).
  • a UE may represent a device that is not intended for sale to, or operation by,
  • the UE 900 includes processing circuitry 902 that is operatively coupled via a bus 904 to an input/output interface 906, a power source 908, memory 910, a communication interface 912, and/or any other component, or any combination thereof.
  • processing circuitry 902 that is operatively coupled via a bus 904 to an input/output interface 906, a power source 908, memory 910, a communication interface 912, and/or any other component, or any combination thereof.
  • Certain UEs may utilize all or a subset of the components shown in Figure 9. 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 902 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 910.
  • the processing circuitry 902 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 902 may include multiple Central Processing Units (CPUs).
  • the input/output interface 906 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 900.
  • 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.
  • the power source 908 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 908 may further include power circuitry for delivering power from the power source 908 itself, and/or an external power source, to the various parts of the UE 900 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging the power source 908.
  • Power circuitry may perform any formatting, converting, or other modification to the power from the power source 908 to make the power suitable for the respective components of the UE 900 to which power is supplied.
  • the memory 910 may be or be configured to include memory such as Random Access Memory (RAM), Read Only Memory (ROM), Programmable ROM (PROM), Erasable PROM (EPROM), Electrically EPROM (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth.
  • the memory 910 includes one or more application programs 914, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 916.
  • the memory 910 may store, for use by the UE 900, any of a variety of various operating systems or combinations of operating systems.
  • the memory 910 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 RAM (SDRAM), external micro-DIMM SDRAM, smartcard memory such as a tamper resistant module in the form of a Universal Integrated Circuit Card (UICC) including one or more Subscriber Identity Modules (SIMs), such as a Universal SIM (USIM) and/or Internet Protocol Multimedia Services Identity Module (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 Dual In-line Memory Module
  • the UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as a ‘SIM card.’
  • the memory 910 may allow the UE 900 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 910, which may be or comprise a device-readable storage medium.
  • the processing circuitry 902 may be configured to communicate with an access network or other network using the communication interface 912.
  • the communication interface 912 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 922.
  • the communication interface 912 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network).
  • Each transceiver may include a transmitter 918 and/or a receiver 920 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth).
  • the transmitter 918 and receiver 920 may be coupled to one or more antennas (e.g., the antenna 922) and may share circuit components, software, or firmware, or alternatively be implemented separately.
  • communication functions of the communication interface 912 may include cellular communication, WiFi communication, LPWAN communication, data communication, voice communication, multimedia communication, short- range communications such as Bluetooth, NFC, location-based communication such as the use of the Global Positioning System (GPS) to determine a location, another like communication function, or any combination thereof.
  • GPS Global Positioning System
  • Communications may be implemented 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, NR, UMTS, WiMax, Ethernet, Transmission Control Protocol/Internet Protocol (TCP/IP), Synchronous Optical Networking (SONET), Asynchronous Transfer Mode (ATM), Quick User Datagram Protocol Internet Connection (QUIC), Hypertext Transfer Protocol (HTTP), and so forth.
  • CDMA Code Division Multiplexing Access
  • WCDMA Wideband CDMA
  • GSM Global System for Mobile communications
  • LTE Long Term Evolution
  • NR Fifth Generation
  • UMTS Worldwide Interoperability for Mobile communications
  • WiMax Ethernet
  • TCP/IP Transmission Control Protocol/Internet Protocol
  • SONET Synchronous Optical Networking
  • ATM Asynchronous Transfer Mode
  • QUIC Quick User Datagram Protocol Internet Connection
  • HTTP Hypertext Transfer Protocol
  • a UE may provide an output of data captured by its sensors, through its communication interface 912, or via a wireless connection to a network node.
  • Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE.
  • the output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected, an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).
  • a UE comprises an actuator, a motor, or a switch related to a communication interface configured to receive wireless input from a network node via a wireless connection.
  • the states of the actuator, the motor, or the switch may change.
  • the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.
  • a UE when in the form of an loT device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application, and healthcare.
  • Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a television, 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 VR, a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or itemtracking device, a
  • a UE may represent a machine or other device that performs monitoring and/or measurements and transmits the results of such monitoring and/or measurements to another UE and/or a network node.
  • the UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device.
  • the UE may implement the 3GPP NB-IoT standard.
  • a UE may represent a vehicle, such as a car, a bus, a truck, a ship, an airplane, or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.
  • 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 10 shows a network node 1000 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.
  • Examples of network nodes include, but are not limited to, APs (e.g., radio APs), Base Stations (BSs) (e.g., radio BSs, Node Bs, evolved Node Bs (eNBs), and NR Node Bs (gNBs)).
  • APs e.g., radio APs
  • BSs Base Stations
  • eNBs evolved Node Bs
  • gNBs NR Node Bs
  • BSs 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 BSs, pico BSs, micro BSs, or macro BSs.
  • a BS 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 BS such as centralized digital units and/or Remote Radio Units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such RRUs may or may not be integrated with an antenna as an antenna integrated radio.
  • RRUs Remote Radio Heads
  • Parts of a distributed radio BS 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 BS 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 Transmission Point
  • MSR Multi-Standard Radio
  • RNCs Radio Network Controllers
  • BSCs Base Transceiver Stations
  • MCEs Multi-Cell/Multicast Coordination Entities
  • OFM Operation and Maintenance
  • OSS Operations Support System
  • SON Self-Organizing Network
  • positioning nodes
  • the network node 1000 includes processing circuitry 1002, memory 1004, a communication interface 1006, and a power source 1008.
  • the network node 1000 may be composed of multiple physically separate components (e.g., a Node B component and an RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components.
  • the network node 1000 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 Node Bs.
  • each unique Node B and RNC pair may in some instances be considered a single separate network node.
  • the network node 1000 may be configured to support multiple RATs. In such embodiments, some components may be duplicated (e.g., separate memory 1004 for different RATs) and some components may be reused (e.g., an antenna 1010 may be shared by different RATs).
  • the network node 1000 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1000, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z- wave, Long Range Wide Area Network (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 the network node 1000.
  • the processing circuitry 1002 may comprise a combination of one or more of a microprocessor, controller, microcontroller, CPU, DSP, ASIC, FPGA, 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 1000 components, such as the memory 1004, to provide network node 1000 functionality.
  • the processing circuitry 1002 includes a System on a Chip (SOC).
  • the processing circuitry 1002 includes one or more of Radio Frequency (RF) transceiver circuitry 1012 and baseband processing circuitry 1014.
  • RF Radio Frequency
  • the RF transceiver circuitry 1012 and the baseband processing circuitry 1014 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units.
  • part or all of the RF transceiver circuitry 1012 and the baseband processing circuitry 1014 may be on the same chip or set of chips, boards, or units.
  • the memory 1004 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, RAM, 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 1002.
  • volatile or non-volatile computer- readable memory including, without limitation, persistent storage, solid state memory, remotely mounted memory, magnetic media, optical media, RAM, 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/
  • the memory 1004 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and/or other instructions capable of being executed by the processing circuitry 1002 and utilized by the network node 1000.
  • the memory 1004 may be used to store any calculations made by the processing circuitry 1002 and/or any data received via the communication interface 1006.
  • the processing circuitry 1002 and the memory 1004 are integrated.
  • the communication interface 1006 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 1006 comprises port(s)/terminal(s) 1016 to send and receive data, for example to and from a network over a wired connection.
  • the communication interface 1006 also includes radio front-end circuitry 1018 that may be coupled to, or in certain embodiments a part of, the antenna 1010.
  • the radio front-end circuitry 1018 comprises filters 1020 and amplifiers 1022.
  • the radio front-end circuitry 1018 may be connected to the antenna 1010 and the processing circuitry 1002.
  • the radio front-end circuitry 1018 may be configured to condition signals communicated between the antenna 1010 and the processing circuitry 1002.
  • the radio front-end circuitry 1018 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection.
  • the radio front-end circuitry 1018 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of the filters 1020 and/or the amplifiers 1022.
  • the radio signal may then be transmitted via the antenna 1010.
  • the antenna 1010 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1018.
  • the digital data may be passed to the processing circuitry 1002.
  • the communication interface 1006 may comprise different components and/or different combinations of components.
  • the network node 1000 does not include separate radio front-end circuitry 1018; instead, the processing circuitry 1002 includes radio front-end circuitry and is connected to the antenna 1010. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1012 is part of the communication interface 1006. In still other embodiments, the communication interface 1006 includes the one or more ports or terminals 1016, the radio front-end circuitry 1018, and the RF transceiver circuitry 1012 as part of a radio unit (not shown), and the communication interface 1006 communicates with the baseband processing circuitry 1014, which is part of a digital unit (not shown).
  • the antenna 1010 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals.
  • the antenna 1010 may be coupled to the radio front-end circuitry 1018 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly.
  • the antenna 1010 is separate from the network node 1000 and connectable to the network node 1000 through an interface or port.
  • the antenna 1010, the communication interface 1006, and/or the processing circuitry 1002 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node 1000. Any information, data, and/or signals may be received from a UE, another network node, and/or any other network equipment. Similarly, the antenna 1010, the communication interface 1006, and/or the processing circuitry 1002 may be configured to perform any transmitting operations described herein as being performed by the network node 1000. Any information, data, and/or signals may be transmitted to a UE, another network node, and/or any other network equipment.
  • the power source 1008 provides power to the various components of the network node 1000 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component).
  • the power source 1008 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 1000 with power for performing the functionality described herein.
  • the network node 1000 may be connectable to an external power source (e.g., the power grid or an electricity outlet) via input circuitry or an interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 1008.
  • the power source 1008 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 1000 may include additional components beyond those shown in Figure 10 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 1000 may include user interface equipment to allow input of information into the network node 1000 and to allow output of information from the network node 1000. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1000.
  • FIG 11 is a block diagram of a host 1100, which may be an embodiment of the host 816 of Figure 8, in accordance with various aspects described herein.
  • the host 1100 may be or comprise various combinations of 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 1100 may provide one or more services to one or more UEs.
  • the host 1100 includes processing circuitry 1102 that is operatively coupled via a bus 1104 to an input/output interface 1106, a network interface 1108, a power source 1110, and memory 1112.
  • processing circuitry 1102 that is operatively coupled via a bus 1104 to an input/output interface 1106, a network interface 1108, a power source 1110, and memory 1112.
  • 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 9 and 10, such that the descriptions thereof are generally applicable to the corresponding components of the host 1100.
  • the memory 1112 may include one or more computer programs including one or more host application programs 1114 and data 1116, which may include user data, e.g., data generated by a UE for the host 1100 or data generated by the host 1100 for a UE.
  • Embodiments of the host 1100 may utilize only a subset or all of the components shown.
  • the host application programs 1114 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), Moving Picture Experts Group (MPEG), VP9) and audio codecs (e.g., Free Lossless Audio Codec (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, and heads-up display systems).
  • VVC Versatile Video Coding
  • HEVC High Efficiency Video Coding
  • AVC Advanced Video Coding
  • MPEG Moving Picture Experts Group
  • VP9 Moving Picture Experts Group
  • audio codecs e.g., Free Lossless Audio Codec (FLAC), Advanced Audio Coding (AAC), MPEG, G.711
  • FLAC Free Lossless Audio Codec
  • AAC Advanced Audio Coding
  • the host application programs 1114 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host 1100 may select and/or indicate a different host for Over-The-Top (OTT) services for a UE.
  • the host application programs 1114 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 (DASH or MPEG-DASH), etc.
  • FIG. 12 is a block diagram illustrating a virtualization environment 1200 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 1200 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 1202 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.
  • Hardware 1204 includes processing circuitry, memory that stores software and/or instructions executable by hardware processing circuitry, and/or other hardware devices as described herein, such as a network interface, input/output interface, and so forth.
  • Software may be executed by the processing circuitry to instantiate one or more virtualization layers 1206 (also referred to as hypervisors or VM Monitors (VMMs)), provide VMs 1208A and 1208B (one or more of which may be generally referred to as VMs 1208), and/or perform any of the functions, features, and/or benefits described in relation with some embodiments described herein.
  • the virtualization layer 1206 may present a virtual operating platform that appears like networking hardware to the VMs 1208.
  • the VMs 1208 comprise virtual processing, virtual memory, virtual networking, or interface and virtual storage, and may be run by a corresponding virtualization layer 1206.
  • Different embodiments of the instance of a virtual appliance 1202 may be implemented on one or more of the VMs 1208, and the implementations may be made in different ways.
  • Virtualization of the hardware is in some contexts referred to as Network Function Virtualization (NFV).
  • NFV Network Function Virtualization
  • NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers and customer premise equipment.
  • a VM 1208 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 1208, and that part of the hardware 1204 that executes that VM be it hardware dedicated to that VM and/or hardware shared by that VM with others of the VMs 1208, forms separate virtual network elements.
  • a virtual network function is responsible for handling specific network functions that run in one or more VMs 1208 on top of the hardware 1204 and corresponds to the application 1202.
  • the hardware 1204 may be implemented in a standalone network node with generic or specific components.
  • the hardware 1204 may implement some functions via virtualization.
  • the hardware 1204 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 1210, which, among others, oversees lifecycle management of the applications 1202.
  • the hardware 1204 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 RAN or a BS.
  • some signaling can be provided with the use of a control system 1212 which may alternatively be used for communication between hardware nodes and radio units.
  • FIG. 13 shows a communication diagram of a host 1302 communicating via a network node 1304 with a UE 1306 over a partially wireless connection in accordance with some embodiments.
  • the host 1302 include hardware, such as a communication interface, processing circuitry, and memory.
  • the host 1302 also includes software, which is stored in or is accessible by the host 1302 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 1306 connecting via an OTT connection 1350 extending between the UE 1306 and the host 1302.
  • a host application may provide user data which is transmitted using the OTT connection 1350.
  • the network node 1304 includes hardware enabling it to communicate with the host 1302 and the UE 1306 via a connection 1360.
  • the connection 1360 may be direct or pass through a core network (like the core network 806 of Figure 8) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks.
  • an intermediate network may be a backbone network or the Internet.
  • the UE 1306 includes hardware and software, which is stored in or accessible by the UE 1306 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 the UE 1306 with the support of the host 1302.
  • 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 the UE 1306 with the support of the host 1302.
  • an executing host application may communicate with the executing client application via the OTT connection 1350 terminating at the UE 1306 and the host 1302.
  • 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 1350 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
  • the OTT connection 1350 may extend via the connection 1360 between the host 1302 and the network node 1304 and via a wireless connection 1370 between the network node 1304 and the UE 1306 to provide the connection between the host 1302 and the UE 1306.
  • the connection 1360 and the wireless connection 1370, over which the OTT connection 1350 may be provided, have been drawn abstractly to illustrate the communication between the host 1302 and the UE 1306 via the network node 1304, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • the host 1302 provides user data, which may be performed by executing a host application.
  • the user data is associated with a particular human user interacting with the UE 1306.
  • the user data is associated with a UE 1306 that shares data with the host 1302 without explicit human interaction.
  • the host 1302 initiates a transmission carrying the user data towards the UE 1306.
  • the host 1302 may initiate the transmission responsive to a request transmitted by the UE 1306.
  • the request may be caused by human interaction with the UE 1306 or by operation of the client application executing on the UE 1306.
  • the transmission may pass via the network node 1304 in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 1312, the network node 1304 transmits to the UE 1306 the user data that was carried in the transmission that the host 1302 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1314, the UE 1306 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 1306 associated with the host application executed by the host 1302.
  • the UE 1306 executes a client application which provides user data to the host 1302.
  • the user data may be provided in reaction or response to the data received from the host 1302.
  • the UE 1306 may provide user data, which may be performed by executing the client application.
  • the client application may further consider user input received from the user via an input/output interface of the UE 1306. Regardless of the specific manner in which the user data was provided, the UE 1306 initiates, in step 1318, transmission of the user data towards the host 1302 via the network node 1304.
  • the network node 1304 receives user data from the UE 1306 and initiates transmission of the received user data towards the host 1302.
  • the host 1302 receives the user data carried in the transmission initiated by the UE 1306.
  • One or more of the various embodiments improve the performance of OTT services provided to the UE 1306 using the OTT connection 1350, in which the wireless connection 1370 forms the last segment. More precisely, the teachings of these embodiments may improve the e.g., data rate, latency, power consumption, etc. and thereby provide benefits such as e.g., reduced user waiting time, relaxed restriction on file size, improved content resolution, better responsiveness, extended battery lifetime, etc.
  • factory status information may be collected and analyzed by the host 1302.
  • the host 1302 may process audio and video data which may have been retrieved from a UE for use in creating maps.
  • the host 1302 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights).
  • the host 1302 may store surveillance video uploaded by a UE.
  • the host 1302 may store or control access to media content such as video, audio, VR, or AR which it can broadcast, multicast, or unicast to UEs.
  • the host 1302 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 1350 may be implemented in software and hardware of the host 1302 and/or the UE 1306.
  • sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 1350 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 the OTT connection 1350 may include message format, retransmission settings, preferred routing, etc.; the reconfiguring need not directly alter the operation of the network node 1304. Such procedures and functionalities may be known and practiced in the art.
  • measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency, and the like by the host 1302.
  • the measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 1350 while monitoring propagation times, errors, etc.
  • computing devices described herein may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and/or software needed to perform the tasks, features, functions, and methods disclosed herein. Determining, calculating, obtaining, or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • processing circuitry may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components.
  • a communication interface may be configured to include any of the components described herein, and/or the functionality of the components may be partitioned between the processing circuitry and the communication interface.
  • non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.
  • processing circuitry executing instructions stored in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer- readable storage medium.
  • some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hardwired manner.
  • the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device but are enjoyed by the computing device as a whole and/or by end users and a wireless network generally.
  • Embodiment 1 A method performed by a User Equipment, UE, for receiving or transmitting data, the method comprising one or more of: determining whether a response in Downlink, DL, is expected on application-layer after an Uplink, UL, data transmission; determining information on whether or not to expect an UL transmission from the UE in response to a DL transmission from the gNB; receiving a DL transmission; if no UL transmission is expected from the UE, being released.
  • Embodiment 2 The method of the previous embodiment wherein an indication is sent from the application layer to Radio Resource Control, RRC, or Medium Access Control, MAC, in the UE (e.g., as assistance information).
  • RRC Radio Resource Control
  • MAC Medium Access Control
  • Embodiment 3 The method of any of the previous embodiments wherein an expected UL response can be configured for a particular service, e.g., per DRB or QoS-flow on RAN level.
  • Embodiment 4 The method of any of the previous embodiments wherein the expected UL response can be configured for a particular service, e.g., per DRB or QoS-flow.
  • Embodiment 5 The method of any of the previous embodiments wherein the UE can now know in advance whether a UL is expected once it receives a DL from the gNB.
  • Embodiment 6 The method of any of the previous embodiments wherein a possible early release of the UE is enabled for some applications.
  • Embodiment 7 The method of any of the previous embodiments wherein the QoS flows can be categorized based on a new 5G QoS identifier, on which the expected traffic pattern can be defined.
  • Embodiment 8 The method of any of the previous embodiments, further comprising: providing user data; and forwarding the user data to a host via the transmission to the network node.
  • Embodiment 9 A method performed by a network node for receiving or transmitting data, the method comprising one or more of: determining information on whether or not to expect an UL transmission from the UE in response to a DL transmission from the gNB; determining a MT-SDT Release Assistance Indication, RAI, that is configurable per DRB or QoS flow; determining a 5G-specific transmission pattern based on the QoS flow characteristics; transmitting a DL transmission to the UE; if no UL transmission is expected from the UE, releasing the UE.
  • RAI MT-SDT Release Assistance Indication
  • Embodiment 10 The method of the previous embodiment wherein the RAI is received from the Core Network, CN.
  • Embodiment 11 The method of any of the previous embodiments wherein an expected UL response can be configured for a particular service, e.g., per DRB or QoS-flow on RAN level.
  • Embodiment 12 The method of any of the previous embodiments wherein the expected UL response can be configured for a particular service, e.g., per DRB or QoS-flow.
  • Embodiment 13 The method of any of the previous embodiments wherein the UE can now know in advance whether a UL is expected once it receives a DL from the gNB.
  • Embodiment 14 The method of any of the previous embodiments wherein a possible early release of the UE is enabled for some applications.
  • Embodiment 15 The method of any of the previous embodiments wherein the QoS flows can be categorized based on a new 5G QoS identifier, on which the expected traffic pattern can be defined.
  • Embodiment 16 The method of any of the previous embodiments, further comprising: obtaining user data; and forwarding the user data to a host or a user equipment. [0147] Group C Embodiments
  • Embodiment 17 A user equipment for receiving or transmitting data, comprising: processing circuitry configured to perform any of the steps of any of the Group A embodiments; and power supply circuitry configured to supply power to the processing circuitry.
  • Embodiment 18 A network node for receiving or transmitting data, the network node comprising: processing circuitry configured to perform any of the steps of any of the Group B embodiments; power supply circuitry configured to supply power to the processing circuitry.
  • Embodiment 19 A user equipment (UE) for receiving or transmitting data, the UE comprising: an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; the processing circuitry being configured to perform any of the steps of any of the Group A embodiments; an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the UE.
  • UE user equipment
  • Embodiment 20 A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform any of the steps of any of the Group A embodiments to receive the user data from the host.
  • OTT over-the-top
  • Embodiment 21 The host of the previous embodiment, wherein the cellular network further includes a network node configured to communicate with the UE to transmit the user data to the UE from the host.
  • Embodiment 22 The host of the previous 2 embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.
  • Embodiment 23 A method implemented by a host operating in a communication system that further includes a network node and a user equipment (UE), the method comprising: providing user data for the UE; and initiating a transmission carrying the user data to the UE via a cellular network comprising the network node, wherein the UE performs any of the operations of any of the Group A embodiments to receive the user data from the host.
  • UE user equipment
  • Embodiment 24 The method of the previous embodiment, further comprising: at the host, executing a host application associated with a client application executing on the UE to receive the user data from the UE.
  • Embodiment 25 The method of the previous embodiment, further comprising: at the host, transmitting input data to the client application executing on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application.
  • Embodiment 26 A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform any of the steps of any of the Group A embodiments to transmit the user data to the host.
  • OTT over-the-top
  • Embodiment 27 The host of the previous embodiment, wherein the cellular network further includes a network node configured to communicate with the UE to transmit the user data from the UE to the host.
  • Embodiment 28 The host of the previous 2 embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.
  • Embodiment 29 A method implemented by a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: at the host, receiving user data transmitted to the host via the network node by the UE, wherein the UE performs any of the steps of any of the Group A embodiments to transmit the user data to the host.
  • UE user equipment
  • Embodiment 30 The method of the previous embodiment, further comprising: at the host, executing a host application associated with a client application executing on the UE to receive the user data from the UE.
  • Embodiment 31 The method of the previous embodiment, further comprising: at the host, transmitting input data to the client application executing on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application.
  • Embodiment 32 A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a network node in a cellular network for transmission to a user equipment (UE), the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE.
  • OTT over-the-top
  • Embodiment 33 The host of the previous embodiment, wherein: the processing circuitry of the host is configured to execute a host application that provides the user data; and the UE comprises processing circuitry configured to execute a client application associated with the host application to receive the transmission of user data from the host.
  • Embodiment 34 A method implemented in a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: providing user data for the UE; and initiating a transmission carrying the user data to the UE via a cellular network comprising the network node, wherein the network node performs any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE.
  • UE user equipment
  • Embodiment 35 The method of the previous embodiment, further comprising, at the network node, transmitting the user data provided by the host for the UE.
  • Embodiment 36 The method of any of the previous 2 embodiments, wherein the user data is provided at the host by executing a host application that interacts with a client application executing on the UE, the client application being associated with the host application.
  • Embodiment 37 A communication system configured to provide an over-the-top service, the communication system comprising: a host comprising: processing circuitry configured to provide user data for a user equipment (UE), the user data being associated with the over-the-top service; and a network interface configured to initiate transmission of the user data toward a cellular network node for transmission to the UE, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE.
  • Embodiment 38 The communication system of the previous embodiment, further comprising: the network node; and/or the user equipment.
  • Embodiment 39 A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to initiate receipt of user data; and a network interface configured to receive the user data from a network node in a cellular network, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to receive the user data from a user equipment (UE) for the host.
  • OTT over-the-top
  • Embodiment 40 The host of the previous 2 embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.
  • Embodiment 41 The host of the any of the previous 2 embodiments, wherein the initiating receipt of the user data comprises requesting the user data.
  • Embodiment 42 A method implemented by a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: at the host, initiating receipt of user data from the UE, the user data originating from a transmission which the network node has received from the UE, wherein the network node performs any of the steps of any of the Group B embodiments to receive the user data from the UE for the host.
  • UE user equipment
  • Embodiment 43 The method of the previous embodiment, further comprising at the network node, transmitting the received user data to the host.
  • E-UTRA Evolved Universal Terrestrial Radio Access

Landscapes

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

Abstract

L'invention concerne des systèmes et des procédés pour permettre une configuration par service pour une transmission de petites données (SDT) à terminaison mobile (MT). Selon certains modes de réalisation, un procédé mis en œuvre par un équipement utilisateur (UE) pour permettre une configuration par service pour MT-SDT consiste : à déterminer des informations sur une réponse de liaison montante (UL) attendue à une transmission de liaison descendante (DL) à partir d'un gNB; à envoyer, au gNB, une indication concernant la réponse d'UL attendue; à recevoir une transmission de DL; et à répondre à la transmission de DL sur la base de la réponse d'UL attendue. Par la mise en œuvre de la solution mentionnée ci-dessus dans le MT-SDT Rel-18, la réponse d'UL attendue peut être configurée pour un service particulier, par exemple, par DRB ou un flux QoS sur un niveau RAN. Cela signifie que l'UE peut désormais savoir à l'avance si une UL est attendue une fois qu'il reçoit une DL du gNB, ce qui permet une libération précoce possible de l'UE pour certaines applications afin d'économiser de l'énergie.
PCT/IB2023/054849 2022-05-10 2023-05-10 Systèmes et procédés pour permettre une configuration par service pour mt-sdt WO2023218383A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202263340238P 2022-05-10 2022-05-10
US63/340,238 2022-05-10

Publications (1)

Publication Number Publication Date
WO2023218383A1 true WO2023218383A1 (fr) 2023-11-16

Family

ID=86731984

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2023/054849 WO2023218383A1 (fr) 2022-05-10 2023-05-10 Systèmes et procédés pour permettre une configuration par service pour mt-sdt

Country Status (1)

Country Link
WO (1) WO2023218383A1 (fr)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022087275A1 (fr) * 2020-10-21 2022-04-28 Ofinno, Llc Téléavertissement pour la transmission de petites données

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022087275A1 (fr) * 2020-10-21 2022-04-28 Ofinno, Llc Téléavertissement pour la transmission de petites données

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "CP aspects for SDT", vol. RAN WG2, no. Electronic meeting; 20220221, 15 February 2022 (2022-02-15), XP052114973, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG2_RL2/TSGR2_117-e/Docs/R2-2203155.zip R2-2203155 - CP aspects for SDT.docx> [retrieved on 20220215] *
INTEL CORPORATION: "Details on MT EDT for UP solution (Msg4-based)", vol. RAN WG2, no. Reno, USA; 20190513 - 20190517, 13 May 2019 (2019-05-13), XP051729899, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings%5F3GPP%5FSYNC/RAN2/Docs/R2%2D1906434%2Ezip> [retrieved on 20190513] *

Similar Documents

Publication Publication Date Title
WO2023105073A1 (fr) Commande d&#39;admission inter-nœuds de réseau pour un ue relais de liaison latérale
WO2023058009A1 (fr) Indication d&#39;itinérance en cas de catastrophe pour session et politique
WO2023012705A1 (fr) Partitionnement d&#39;accès aléatoire et rapport d&#39;accès aléatoire
WO2023218383A1 (fr) Systèmes et procédés pour permettre une configuration par service pour mt-sdt
WO2023185737A1 (fr) Procédé et appareil permettant d&#39;effectuer une authentification/autorisation secondaire pour un dispositif terminal dans un réseau de communication
WO2024028838A1 (fr) Économie d&#39;énergie de réseau dans un ng-ran scindé
WO2023101593A2 (fr) Systèmes et procédés pour rapporter des indications de couche supérieure et une qualité d&#39;expérience dans une connectivité multiple
WO2024019652A1 (fr) Stockage de configurations qoe et rvqoe dans rrc_idle
WO2023224527A1 (fr) Distribution de mesures de qoe visibles par ran
WO2023209684A1 (fr) Informations d&#39;assistance pour économie d&#39;énergie de réseau
WO2023204752A1 (fr) Radiomessagerie pour commande de réseau mt-sdt et signalisation inter-nœuds
WO2023011942A1 (fr) Rapport de relaxation de mesure radio précoce
WO2023131929A1 (fr) Fourniture d&#39;informations d&#39;emplacement
WO2023068983A1 (fr) Rapport de mesurage basé sur des configurations de mesurage utilisant des indications de priorité spécifiques à la fréquence
WO2024035309A1 (fr) Procédés, appareil et support lisible par ordinateur associés à un changement conditionnel de cellule
WO2023239280A1 (fr) Sélection de réponse ul pour transmission de petites données à terminaison mobile
WO2023031877A1 (fr) Procédés de prise en charge de multiples configurations de réception discontinue (drx)
WO2024019646A1 (fr) Envoi d&#39;une unité de données à un nœud de réseau d&#39;accès radio, et transmission d&#39;une unité de données à un équipement utilisateur
CA3235729A1 (fr) Configurations de drx multiples avec informations de flux de trafic
WO2023132774A1 (fr) Gestion de déclencheurs pour rapport qoe visible par ran
WO2023166448A1 (fr) Rapport de mesurage b1/a4 optimisé
WO2023214919A1 (fr) Procédés pour améliorer des capacités d&#39;économie d&#39;énergie pour un ue après la réception de données dl dans une mt-sdt
WO2023062509A1 (fr) Activation de cellule secondaire basée sur un signal de référence temporaire par l&#39;intermédiaire d&#39;une commande de ressources radio
WO2023249529A1 (fr) Gestion de problèmes de coexistence dans un dispositif
WO2023161819A1 (fr) Systèmes et procédés de prise en charge d&#39;intervalle de multiples modules d&#39;identité d&#39;abonné universels

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

Country of ref document: EP

Kind code of ref document: A1