WO2023204752A1 - Radiomessagerie pour commande de réseau mt-sdt et signalisation inter-nœuds - Google Patents

Radiomessagerie pour commande de réseau mt-sdt et signalisation inter-nœuds Download PDF

Info

Publication number
WO2023204752A1
WO2023204752A1 PCT/SE2023/050371 SE2023050371W WO2023204752A1 WO 2023204752 A1 WO2023204752 A1 WO 2023204752A1 SE 2023050371 W SE2023050371 W SE 2023050371W WO 2023204752 A1 WO2023204752 A1 WO 2023204752A1
Authority
WO
WIPO (PCT)
Prior art keywords
network node
sdt
paging
paging message
indication
Prior art date
Application number
PCT/SE2023/050371
Other languages
English (en)
Inventor
Jan Christoffersson
Stefan WÄNSTEDT
Liwei QIU
Yazid LYAZIDI
Andreas HÖGLUND
Tuomas TIRRONEN
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 WO2023204752A1 publication Critical patent/WO2023204752A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices
    • H04W88/085—Access point devices with remote components
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/20—Interfaces between hierarchically similar devices between access points

Definitions

  • the present disclosure relates generally to paging a User Equipment (UE).
  • UE User Equipment
  • the WI contains the following relevant objectives:
  • SUBSTITUTE SHEET (Rule 26) The Small Data Transmission (SDT) procedure in NR Rel-17 is only for Mobile Originated (MO)-SDT meaning that it is only triggered by UL data transmissions.
  • NR SDT For NB-IoT and LTE-M UEs, similar signaling optimizations for small data transmission have been introduced through Rel-15 Early Data Transmission (EDT) and Rel-16 Preconfigured Uplink Resources (PUR).
  • EDT Early Data Transmission
  • PUR Preconfigured Uplink Resources
  • NR SDT also unlike LTE EDT, supports transmission of subsequent data, that is larger payload sizes which require more than one transmission.
  • RA-SDT means that either legacy 4-step RACH or 2-step RACH procedure is used as a baseline but that a user-plane data payload can be appended (multiplexed with the RRCResumeRequest message) in Msg3 (or MsgA).
  • Msg3 or MsgA
  • CG-SDT means that the UEs configured via RRC to have periodic CG-SDT occasions which can, contention-free, be used for uplink transmission. In this way Msgl and Msg2 can be omitted but it is a requirement that the UE has a valid Timing Advance (TA) and is uplink synchronized to be able to use the resources for transmission.
  • TA Timing Advance
  • the CG-SDT procedure uses CG PUSCH resources that are PUSCH resources configured in advance for the UE. When there is uplink data available at the UE’s buffer, it can immediately start uplink transmission using the pre-configured PUSCH resources without waiting for an UL grant from the gNB, thus reducing the latency.
  • NR supports CG type 1 PUSCH transmission and CG type 2 PUSCH transmission. For both types, the PUSCH resources (time and frequency allocation, periodicity, etc.) are preconfigured via dedicated RRC signaling.
  • the CG type 1 PUSCH transmission is activated/deactivated by RRC signaling, while the CG type 2 PUSCH transmission is activated/deactivated by an UL grant using downlink control information (DCI) signaling.
  • DCI downlink control information
  • the CG-SDT configuration will be sent to the UE in the RRCRelease message and will specify associations between CG resources (transmission opportunities) and SSBs.
  • the UE will upon initiating the CG-SDT procedure select an SSB with SS-RSRP above a configured RSRP threshold.
  • SDT transmission will contain the RRCResumeRequest multiplexed with data and possibly a BSR MAC CE and possibly a PHR MAC CE. If the gNB receives the transmission successfully it will reply with dynamic scheduling of uplink new transmission for the same HARQ process as acknowledgement or possibly with a DL data transmission. After this the UE may use the following CG-SDT resources for transmission of new UL data after successful TA validation and SSB selection.
  • the TA validation means that the CG-SDT TA timer is running and the change of the SS-RSRP(s) are within configured thresholds.
  • the CG-SDT procedure is terminated when the CG-SDT-TA timer expires, the UE reselects to a different cell or the gNB sends an RRCResume or RRCRelease to the UE.
  • NR MT-SDT is being introduced in Rel-18.
  • a Rel-18 MT-SDT work item description was approved in RAN#94e (Dec 2021) and can be found in RP-213583.
  • the WID contains the following objectives:
  • UE responds to the paging by initiating an SDT procedure, either CG-SDT or RA-SDT. This means that the UE sends an RRCResumeRequest message.
  • the NW (after contention resolution in case of RA-SDT) schedules a DL transmission including the data that triggered the MT-SDT procedure.
  • the UE may optionally acknowledge the DL transmission.
  • SUBSTITUTE SHEET (Rule 26) 6.
  • the NW either moves the UE to connected mode or releases the UE to Idle or Inactive mode.
  • Figure 1 An example of baseline procedures for RA-SDT is shown in Figure 1 and for CG-SDT in Figure 2.
  • Figure 1 illustrates MT-SDT using RA-SDT procedure. UE triggers RA-SDT upon reception of paging.
  • Figure 2 illustrates MT-SDT using CG-SDT. UE triggers CG-SDT upon reception of paging.
  • RAN paging is used for DL reachability, at the same time UE still monitors CN paging but this is a fail-safe mechanism in case of state mismatch.
  • DL data arrives in the CN for a UE in the RRC INACTIVE state, the data will be forwarded to the last serving gNB which has the UEs context. If the UE is located in any of the cells of the last serving gNB, it is the last serving gNB that will be responsible for the paging.
  • the paging message is sent from the anchor gNB-CU to its gNB-DUs.
  • the last serving gNB will send a paging message over Xn to the other gNBs configured in the RAN Notification Area (RNA) upon network’s implementation, which in turn will send (Fl) paging messages in their cells.
  • RNA RAN Notification Area
  • the UE When the UE receives the paging, it will trigger a RA procedure in the cell where it is camping.
  • a method performed by a network node for enabling triggering of a MT-SDT procedure includes: receiving downlink data for a User Equipment (UE); and sending a paging message to a new network node with an MT-SDT indication.
  • UE User Equipment
  • a paging message to a new network node with an MT-SDT indication.
  • triggering of MT-SDT procedure in other cells than those belonging to the anchor gNB may be enabled. This might allow for MT- SDT mechanism to work in the Radio Access Network (RAN) Notification Area (RNA) when configured by the anchor gNB.
  • RAN Radio Access Network
  • RNA Radio Access Network
  • Some embodiments include providing a network entity with information needed to decide whether to invoke a legacy paging procedure or a paging to initiate an MT-SDT procedure to the UE.
  • SUBSTITUTE SHEET (Rule 26) Some embodiments outline enhancements to existing RAN paging procedures and signaling (XnAP and F1AP) to enable the use of MT-SDT for delivery of DL data.
  • the information transferred in the paging message over Xn from the last serving gNB to paging gNB(s) can aid the gNB to decide either sending a legacy paging, or a paging to initiate a MT-SDT procedure (over Fl and Uu interfaces).
  • Some embodiments indicate in the F1AP Paging message sent from gNB-CU to gNB-DU of the anchor or receiving gNB, an indication that MT-SDT can be initiated towards the UE.
  • Figure 1 illustrates an example of baseline procedures for MT-SDT using RA-SDT, in accordance with various aspects described herein;
  • Figure 2 illustrates an example of baseline procedures for MT-SDT using CG-SDT, in accordance with various aspects described herein;
  • Figure 3 illustrates the last serving gNB receives DL SDT data from UPF, and then triggers the MT-SDT procedures towards the new gNB and UE, in accordance with various aspects described herein;
  • Figure 4 illustrates the last serving gNB includes an MT-SDT indication in the F1AP paging message from the gNB-CU to gNB-DU, in accordance with various aspects described herein;
  • Figure 5 shows an example of a communication system in accordance with some embodiments
  • Figure 6 shows a UE in accordance with some embodiments
  • Figure 7 shows a network node in accordance with some embodiments
  • FIG 8 is a block diagram of a host, which may be an embodiment of the host of Figure 5, in accordance with various aspects described herein;
  • Figure 9 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized.
  • Figure 10 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.
  • MT-SDT Mobile Terminated - Small Data Transmission
  • UEs User Equipments
  • RAN Radio Access Network
  • RAN paging is carried out over XnAP in the RAN Paging area and also in the Fl Paging message sent from gNB-CU to the gNB-DU where the cells are located so that the paging can be sent to the UE over the air interface (Uu).
  • the receiving gNB cannot trigger MT-SDT since it has not received the DL data at the time when the paging message is sent.
  • Some embodiments may provide solutions to these or other challenges. Some embodiments include providing a network entity with information needed to decide whether to invoke a legacy paging procedure or a paging to initiate an MT-SDT procedure to the UE.
  • a method performed by a network node for enabling triggering of a MT-SDT procedure includes: receiving downlink data for a UE; and sending a paging message to a new network node with an MT-SDT indication.
  • triggering of MT-SDT procedure in other cells than those belonging to the anchor gNB may be enabled. This might allow for MT-SDT mechanism to work in the RAN Notification Area (RNA) when configured by the anchor gNB.
  • RNA RAN Notification Area
  • Some embodiments outline enhancements to existing RAN paging procedures and signaling (XnAP and F1AP) to enable the use of MT-SDT for delivery of DL data.
  • the information transferred in the paging message over Xn from the last serving gNB to paging gNB(s) can aid the gNB to decide either sending a legacy paging, or a paging to initiate a MT-SDT procedure (over Fl and Uu interfaces).
  • Some embodiments indicate in the F1AP Paging message sent from gNB-CU to gNB-DU of the anchor or receiving gNB, an indication that MT-SDT can be initiated towards the UE.
  • Certain embodiments may provide one or more of the following technical advantage(s).
  • the advantage of the solution is to enable triggering of MT-SDT procedure in other cells than those belonging to the anchor gNB. It would allow for MT-SDT mechanism to work in the RNA, when configured by anchor gNB.
  • the last serving gNB receives DL SDT data from UPF, and then triggers the MT- SDT procedures towards the new gNB and UE.
  • the last serving gNB buffers the DL data received from CN until it receives an indication from the new gNB, e.g., after the RAN Paging message.
  • the last serving gNB includes a MT-SDT indication in the XnAP RAN Paging message towards to the new gNB.
  • the last serving gNB includes an MT-SDT indication in the F1AP paging message from the gNB-CU to gNB-DU, as depicted in Figure 4.
  • the MT-SDT indication is an explicit enumerated value, e.g., ENUMERATED (true, . . .) Information Element (IE).
  • IE Information Element
  • the MT-SDT indication is an implicit indication, e.g., “data volume” represented by number of bits (e.g., ‘N’ bits).
  • a data volume indicator is used as MT-SDT indication, i.e., a few signaling bits are used to indicate the size of the DL data, see example below:
  • the MT-SDT indication can be the data itself coming from the UPF.
  • the MT-SDT indication refers to a service or bearer category through its QoS or PDU session association (e.g., indication of a DRB would mean that there is DL data suited for MT-SDT on that DRB, i.e., an implicit indication.)
  • the last serving gNB includes additional information, together with an explicit or implicit MT-SDT indication, on UE expected traffic pattern or behavior after initiating SDT procedure.
  • the new gNB may use this information to decide
  • SUBSTITUTE SHEET (Rule 26) whether to initiate MT-SDT and whether and when to move the UE to RRC CONNECTED (instead of initiating or continuing with the SDT procedure (e.g., for subsequent data)).
  • the above could in one alternative be seen as a network assistance information, i.e., not only the DL data volume is used for determining the suitability of MT-SDT, but also whether more data is expected (in which case it is more efficient to use legacy paging procedure and move the UE to RRC CONNECTED).
  • last serving gNB that decides to use MT-SDT or not when paging the UE. That is, last serving gNB will compare the DL data buffer to a DL data volume threshold (likely not standardized but up to NW implementation) and decide whether to use MT- SDT or not.
  • a DL data volume threshold likely not standardized but up to NW implementation
  • gNB from different vendors could apply different DL data volume thresholds and in different ways determine when MT-SDT procedure is suitable for the transmission of the data (the decision could also be based on other factors than the data size, e.g., cell load, which DRB the data is received on, QoS flow indication, the type of UE, other MT-SDT procedures in process, etc.).
  • the support of MT-SDT in gNBs can be coordinated between the nodes, and the last serving gNB would only include the MT-SDT indication in the RAN paging message sent to paging gNBs which it knows supports MT-SDT (typically done via Operations, Administration and Maintenance/OAM).
  • gNB blindly include the MT-SDT indication in the paging request but the indication is ignored by paging gNBs not supporting MT- SDT (if the ‘Assigned Criticality’ in the table above is set to ‘ignore’, a paging gNB not capable of MT-SDT will simply ignore the new IE and page UEs in the legacy manner.
  • a MT -indication would be included by the last serving gNB in the RAN paging message to paging gNB.
  • paging gNB gets no indication of the data volume and has no means to determine if MT-SDT is suitable or not). It would then be the paging gNB that decides whether it should use MT-SDT procedure or legacy procedure of the delivery of the DL data.
  • the DL data volume threshold could either be the same for all gNBs, or individually set (see above).
  • This message is sent by the NG-RAN nodel to NG-RAN node2 to page a UE.
  • the New gNB after receiving the MT-SDT indication (either explicit or implicit) the New gNB takes decision of triggering MT-SDT towards the cell where the UE is camping.
  • the new serving gNB includes an MT-SDT indication (either explicit or implicit) in the F1AP paging message from the gNB-CU to gNB-DU where the UE has sent a RA message.
  • the gNB-DU after receiving the MT-SDT indication (either explicit or implicit) over Fl AP paging message, the gNB-DU takes decision of triggering MT-SDT from the cell where the UE is camping.
  • absence of the MT-SDT indication from the initiating network entity can be interpreted by the receiving network entity (receiving gNB) as an indication to proceed with legacy paging.
  • absence of the MT-SDT indication from the initiating network entity e.g., gNB-CU
  • the receiving network entity gNB-DU
  • This message is sent by the gNB-CU and is used to request the gNB-DU to page UEs.
  • an indication for MT-SDT (either explicit IE or data volume size or the data itself) is signaled over El interface from gNB-CU-UP to gNB-CU-CP of the anchor gNB. This can be done for example during the Bearer context management procedures.
  • Figure 5 shows an example of a communication system 500 in accordance with some embodiments.
  • the communication system 500 includes a telecommunication network 502 that includes an access network 504, such as a Radio Access Network (RAN), and a core
  • an access network 504 such as a Radio Access Network (RAN)
  • RAN Radio Access Network
  • the access network 504 includes one or more access network nodes, such as network nodes 510A and 510B (one or more of which may be generally referred to as network nodes 510), or any other similar Third Generation Partnership Project (3GPP) access node or non-3GPP Access Point (AP).
  • the network nodes 510 facilitate direct or indirect connection of User Equipment (UE), such as by connecting UEs 512A, 512B, 512C, and 512D (one or more of which may be generally referred to as UEs 512) to the core network 506 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 500 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 500 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.
  • the UEs 512 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 510 and other communication devices.
  • the network nodes 510 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 512 and/or with other network nodes or equipment in the telecommunication network 502 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 502.
  • the core network 506 connects the network nodes 510 to one or more hosts, such as host 516. 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 506 includes one more core network nodes (e.g., core network node 508) 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 508.
  • 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
  • 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
  • SUBSTITUTE SHEET (Rule 26) De-Concealing Function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and/or a User Plane Function (UPF).
  • SIDF De-Concealing Function
  • UDM Unified Data Management
  • SEPP Security Edge Protection Proxy
  • NEF Network Exposure Function
  • UPF User Plane Function
  • the host 516 may be under the ownership or control of a service provider other than an operator or provider of the access network 504 and/or the telecommunication network 502 and may be operated by the service provider or on behalf of the service provider.
  • the host 516 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 500 of Figure 5 enables connectivity between the UEs, network nodes, and hosts.
  • the communication system 500 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 502 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunication network 502 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 502. For example, the telecommunication network 502 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 512 are configured to transmit and/or receive information without direct human interaction.
  • a UE may be designed to transmit information to the access network 504 on a predetermined schedule, when triggered by an internal or external
  • 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 514 communicates with the access network 504 to facilitate indirect communication between one or more UEs (e.g., UE 512C and/or 512D) and network nodes (e.g., network node 510B).
  • the hub 514 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs.
  • the hub 514 may be a broadband router enabling access to the core network 506 for the UEs.
  • the hub 514 may be a controller that sends commands or instructions to one or more actuators in the UEs.
  • the hub 514 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 514 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 514 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 514 then provides to the UE either directly, after performing local processing, and/or after adding additional local content.
  • the hub 514 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 514 may have a constant/persistent or intermittent connection to the network node 510B.
  • the hub 514 may also allow for a different communication scheme and/or schedule between the hub 514 and UEs (e.g., UE 512C and/or 512D), and between the hub 514 and the core network 506.
  • the hub 514 is connected to the core network 506 and/or one or more UEs via a wired connection.
  • the hub 514 may be configured to connect to a Machine-to-Machine (M2M) service provider over the access network 504 and/or to another UE over a direct connection.
  • M2M Machine-to-Machine
  • UEs may establish a wireless connection with the network nodes 510 while still connected via the hub 514 via a wired or wireless connection.
  • the hub 514 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 510B.
  • the hub 514 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 510B, but which is
  • SUBSTITUTE SHEET (Rule 26) 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 3 GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), Vehi cl e-to- Vehicle (V2V), Vehicle-to-Infrastructure (V2I), or Vehicle- to-Everything (V2X).
  • D2D Device-to-Device
  • DSRC Dedicated Short-Range Communication
  • V2V Vehi cl e-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
  • the UE 600 includes processing circuitry 602 that is operatively coupled via a bus 604 to an input/output interface 606, a power source 608, memory 610, a communication interface 612, and/or any other component, or any combination thereof.
  • processing circuitry 602 that is operatively coupled via a bus 604 to an input/output interface 606, a power source 608, memory 610, a communication interface 612, and/or any other component, or any combination thereof.
  • Certain UEs may utilize all or a subset of the components shown in Figure 6. 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 602 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 610.
  • the processing circuitry 602 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.);
  • SUBSTITUTE SHEET (Rule 26) 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 602 may include multiple Central Processing Units (CPUs).
  • the input/output interface 606 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 600.
  • 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 608 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 608 may further include power circuitry for delivering power from the power source 608 itself, and/or an external power source, to the various parts of the UE 600 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging the power source 608.
  • Power circuitry may perform any formatting, converting, or other modification to the power from the power source 608 to make the power suitable for the respective components of the UE 600 to which power is supplied.
  • the memory 610 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 610 includes one or more application programs 614, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 616.
  • the memory 610 may store, for use by the UE 600, any of a variety of various operating systems or combinations of operating systems.
  • the memory 610 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 610 may allow the UE 600 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 610, which may be or comprise a device-readable storage medium.
  • the processing circuitry 602 may be configured to communicate with an access network or other network using the communication interface 612.
  • the communication interface 612 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 622.
  • the communication interface 612 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 618 and/or a receiver 620 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth).
  • the transmitter 618 and receiver 620 may be coupled to one or more antennas (e.g., the antenna 622) and may share circuit components, software, or firmware, or alternatively be implemented separately.
  • communication functions of the communication interface 612 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.
  • 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
  • SUBSTITUTE SHEET (Rule 26) Protocol/Intemet 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.
  • TCP/IP Protocol/Intemet 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 612, 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 sensor for
  • 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, 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. 7 shows a network node 700 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
  • Node Bs Node Bs
  • eNBs evolved Node Bs
  • gNBs 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
  • MSR Multi -Standard Radio
  • RNCs Radio Network Controllers
  • BSCs Base Transceiver Stations
  • transmission points transmission nodes
  • SUBSTITUTE SHEET (Rule 26) (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).
  • MCEs Operation and Maintenance
  • O&M Operations Support System
  • SON Self-Organizing Network
  • positioning nodes e.g., Evolved Serving Mobile Location Centers (E-SMLCs)
  • E-SMLCs Evolved Serving Mobile Location Centers
  • MDTs Minimization of Drive Tests
  • the network node 700 includes processing circuitry 702, memory 704, a communication interface 706, and a power source 708.
  • the network node 700 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 700 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 700 may be configured to support multiple RATs.
  • the network node 700 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 700, 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 700.
  • the processing circuitry 702 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 700 components, such as the memory 704, to provide network node 700 functionality.
  • the processing circuitry 702 includes a System on a Chip (SOC). In some embodiments, the processing circuitry 702 includes one or more of Radio Frequency (RF) transceiver circuitry 712 and baseband processing circuitry 714. In some embodiments, the RF transceiver circuitry 712 and the baseband processing circuitry 714 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 the RF transceiver circuitry 712 and the baseband processing circuitry 714 may be on the same chip or set of chips, boards, or units.
  • SOC System on a Chip
  • the processing circuitry 702 includes one or more of Radio Frequency (RF) transceiver circuitry 712 and baseband processing circuitry 714.
  • RF transceiver circuitry 712 and the baseband processing circuitry 714 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 the
  • the memory 704 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid state memory, remotely mounted
  • SUBSTITUTE SHEET (Rule 26) 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 702.
  • the memory 704 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 702 and utilized by the network node 700.
  • the memory 704 may be used to store any calculations made by the processing circuitry 702 and/or any data received via the communication interface 706.
  • the processing circuitry 702 and the memory 704 are integrated.
  • the communication interface 706 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 706 comprises port(s)/terminal(s) 716 to send and receive data, for example to and from a network over a wired connection.
  • the communication interface 706 also includes radio front-end circuitry 718 that may be coupled to, or in certain embodiments a part of, the antenna 710.
  • the radio front-end circuitry 718 comprises filters 720 and amplifiers 722.
  • the radio front-end circuitry 718 may be connected to the antenna 710 and the processing circuitry 702.
  • the radio front-end circuitry 718 may be configured to condition signals communicated between the antenna 710 and the processing circuitry 702.
  • the radio front-end circuitry 718 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 718 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of the filters 720 and/or the amplifiers 722.
  • the radio signal may then be transmitted via the antenna 710.
  • the antenna 710 may collect radio signals which are then converted into digital data by the radio front-end circuitry 718.
  • the digital data may be passed to the processing circuitry 702.
  • the communication interface 706 may comprise different components and/or different combinations of components.
  • the network node 700 does not include separate radio front-end circuitry 718; instead, the processing circuitry 702 includes radio front-end circuitry and is connected to the antenna 710. Similarly, in some embodiments, all or some of the RF transceiver circuitry 712 is part of the communication interface 706. In still other embodiments, the communication interface 706 includes the one or more ports or terminals 716, the radio frontend circuitry 718, and the RF transceiver circuitry 712 as part of a radio unit (not shown), and the
  • SUBSTITUTE SHEET (Rule 26) communication interface 706 communicates with the baseband processing circuitry 714, which is part of a digital unit (not shown).
  • the antenna 710 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals.
  • the antenna 710 may be coupled to the radio front-end circuitry 718 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly.
  • the antenna 710 is separate from the network node 700 and connectable to the network node 700 through an interface or port.
  • the antenna 710, the communication interface 706, and/or the processing circuitry 702 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node 700. Any information, data, and/or signals may be received from a UE, another network node, and/or any other network equipment. Similarly, the antenna 710, the communication interface 706, and/or the processing circuitry 702 may be configured to perform any transmitting operations described herein as being performed by the network node 700. Any information, data, and/or signals may be transmitted to a UE, another network node, and/or any other network equipment.
  • the power source 708 provides power to the various components of the network node 700 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component).
  • the power source 708 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 700 with power for performing the functionality described herein.
  • the network node 700 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 708.
  • the power source 708 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 700 may include additional components beyond those shown in Figure 7 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 700 may include user interface equipment to allow input of information into the network node 700 and to allow output of information from the network node 700. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 700.
  • FIG 8 is a block diagram of a host 800, which may be an embodiment of the host 516 of Figure 5, in accordance with various aspects described herein.
  • the host 800 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 800 may provide one or more services to one or more UEs.
  • the host 800 includes processing circuitry 802 that is operatively coupled via a bus 804 to an input/output interface 806, a network interface 808, a power source 810, and memory 812.
  • processing circuitry 802 that is operatively coupled via a bus 804 to an input/output interface 806, a network interface 808, a power source 810, and memory 812.
  • 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 6 and 7, such that the descriptions thereof are generally applicable to the corresponding components of the host 800.
  • the memory 812 may include one or more computer programs including one or more host application programs 814 and data 816, which may include user data, e.g., data generated by a UE for the host 800 or data generated by the host 800 for a UE.
  • Embodiments of the host 800 may utilize only a subset or all of the components shown.
  • the host application programs 814 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 (FL AC), 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 Voice over IP
  • audio codecs e.g., Free Lossless Audio Codec (FL AC), Advanced Audio Coding (AAC), MPEG, G.711
  • FL AC Free Lossless Audio Codec
  • AAC Advanced Audio Coding
  • the host application programs 814 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 800 may select and/or indicate a different host for Over-The-Top (OTT) services for a UE.
  • the host application programs 814 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. 9 is a block diagram illustrating a virtualization environment 900 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
  • SUBSTITUTE SHEET (Rule 26) 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 900 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 902 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment 900 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.
  • Hardware 904 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 906 (also referred to as hypervisors or VM Monitors (VMMs)), provide VMs 908A and 908B (one or more of which may be generally referred to as VMs 908), and/or perform any of the functions, features, and/or benefits described in relation with some embodiments described herein.
  • the virtualization layer 906 may present a virtual operating platform that appears like networking hardware to the VMs 908.
  • the VMs 908 comprise virtual processing, virtual memory, virtual networking, or interface and virtual storage, and may be run by a corresponding virtualization layer 906. Different embodiments of the instance of a virtual appliance 902 may be implemented on one or more of the VMs 908, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as Network Function Virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers and customer premise equipment.
  • NFV Network Function Virtualization
  • a VM 908 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 908, and that part of the hardware 904 that executes that VM be it hardware dedicated to that VM and/or hardware shared by that VM with others of the VMs 908, forms separate virtual network elements.
  • a virtual network function is
  • SUBSTITUTE SHEET responsible for handling specific network functions that run in one or more VMs 908 on top of the hardware 904 and corresponds to the application 902.
  • the hardware 904 may be implemented in a standalone network node with generic or specific components.
  • the hardware 904 may implement some functions via virtualization.
  • the hardware 904 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 910, which, among others, oversees lifecycle management of the applications 902.
  • the hardware 904 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 912 which may alternatively be used for communication between hardware nodes and radio units.
  • Figure 10 shows a communication diagram of a host 1002 communicating via a network node 1004 with a UE 1006 over a partially wireless connection in accordance with some embodiments.
  • Example implementations, in accordance with various embodiments, of the UE (such as the UE 512A of Figure 5 and/or the UE 600 of Figure 6), the network node (such as the network node 510A of Figure 5 and/or the network node 700 of Figure 7), and the host (such as the host 516 of Figure 5 and/or the host 800 of Figure 8) discussed in the preceding paragraphs will now be described with reference to Figure 10.
  • embodiments of the host 1002 include hardware, such as a communication interface, processing circuitry, and memory.
  • the host 1002 also includes software, which is stored in or is accessible by the host 1002 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 1006 connecting via an OTT connection 1050 extending between the UE 1006 and the host 1002.
  • a host application may provide user data which is transmitted using the OTT connection 1050.
  • the network node 1004 includes hardware enabling it to communicate with the host 1002 and the UE 1006 via a connection 1060.
  • the connection 1060 may be direct or pass through a core network (like the core network 506 of Figure 5) 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 1006 includes hardware and software, which is stored in or accessible by the UE 1006 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 1006 with the support of the host 1002.
  • 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 1006 with the support of the host 1002.
  • an executing host application may communicate with the executing client application via the OTT connection 1050 terminating at the UE 1006 and the host 1002.
  • 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 1050 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 1050 may extend via the connection 1060 between the host 1002 and the network node 1004 and via a wireless connection 1070 between the network node 1004 and the UE 1006 to provide the connection between the host 1002 and the UE 1006.
  • the connection 1060 and the wireless connection 1070, over which the OTT connection 1050 may be provided, have been drawn abstractly to illustrate the communication between the host 1002 and the UE 1006 via the network node 1004, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • the host 1002 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 1006.
  • the user data is associated with a UE 1006 that shares data with the host 1002 without explicit human interaction.
  • the host 1002 initiates a transmission carrying the user data towards the UE 1006.
  • the host 1002 may initiate the transmission responsive to a request transmitted by the UE 1006.
  • the request may be caused by human interaction with the UE 1006 or by operation of the client application executing on the UE 1006.
  • the transmission may pass via the network node 1004 in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 1012, the network node 1004 transmits to the UE 1006 the user data that was carried in the transmission that the host 1002 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1014, the UE 1006 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 1006 associated with the host application executed by the host 1002.
  • the UE 1006 executes a client application which provides user data to the host 1002.
  • the user data may be provided in reaction or response to the data received from
  • the UE 1006 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input/output interface of the UE 1006. Regardless of the specific manner in which the user data was provided, the UE 1006 initiates, in step 1018, transmission of the user data towards the host 1002 via the network node 1004.
  • the network node 1004 receives user data from the UE 1006 and initiates transmission of the received user data towards the host 1002.
  • the host 1002 receives the user data carried in the transmission initiated by the UE 1006.
  • One or more of the various embodiments improve the performance of OTT services provided to the UE 1006 using the OTT connection 1050, in which the wireless connection 1070 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 1002.
  • the host 1002 may process audio and video data which may have been retrieved from a UE for use in creating maps.
  • the host 1002 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights).
  • the host 1002 may store surveillance video uploaded by a UE.
  • the host 1002 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 1002 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 1050 may be implemented in software and hardware of the host 1002 and/or the UE 1006.
  • sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 1050 passes; the sensors may participate in the
  • SUBSTITUTE SHEET (Rule 26) 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 1050 may include message format, retransmission settings, preferred routing, etc.; the reconfiguring need not directly alter the operation of the network node 1004. 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 1002.
  • the measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 1050 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. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-
  • SUBSTITUTE SHEET (Rule 26) 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 for enabling triggering of a Mobile Terminated - Small Data Transmission, MT-SDT, procedure, the method comprising one or more of: receiving a paging message; triggering a MT-SDT procedure; performing an RRCResumeRequest; and receiving downlink data.
  • MT-SDT Mobile Terminated - Small Data Transmission
  • Embodiment 2 The method of the previous embodiment wherein the paging message includes an MT-SDT indicator.
  • Embodiment 3 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 4 A method performed by a network node for enabling triggering of a Mobile Terminated - Small Data Transmission, MT-SDT, procedure, the method comprising: receiving downlink data for a User Equipment, UE; transmitting, to a gNB- Distributed Unit, DU, an Fl Paging with MT-SDT indication (e.g., explicit indicator and/or data volume); receiving, from a gNB- Central Unit, CU, the Fl Paging with MT-SDT indication (e.g., explicit indicator and/or data volume); paging the network node’s new cells and/or neighboring network nodes; sending a paging message to a new network node; receiving the paging message to a last serving network node; determining whether to trigger paging to the UE based on the received information about MT-SDT; paging the UE; transmitting, to the last serving network node, an XN-U address indication; providing the received downlink data to the UE.
  • Embodiment 5 The method of the previous embodiment wherein the paging message sent from the last serving network node to the new network node comprises: an MT- SDT indicator and/or data volume.
  • Embodiment 6 The method of any of the previous embodiments wherein the information transferred in the paging message over Xn from the last serving gNB to paging
  • gNB(s) can aid the gNB to decide either to send a legacy paging, or a paging to initiate a MT- SDT procedure (e.g., over Fl and Uu interfaces).
  • Embodiment 7 The method of any of the previous embodiments wherein the paging message sent from the last serving network node to the new network node comprises: an XnAP paging message.
  • Embodiment 8 The method of any of the previous embodiments wherein the network node comprises one of the group consisting of: the new network node, the last serving network node, the gNB-CU, and the gNB-DU.
  • Embodiment 9 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.
  • Embodiment 10 A user equipment for enabling triggering of a Mobile Terminated -
  • Small Data Transmission, MT-SDT, procedure 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 11 A network node for enabling triggering of a Mobile Terminated -
  • 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 12 A user equipment (UE) for enabling triggering of a Mobile
  • Terminated - Small Data Transmission, MT-SDT, procedure 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.
  • Embodiment 13 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
  • OTT over-the-top
  • UE user equipment
  • SUBSTITUTE SHEET (Rule 26) UE being configured to perform any of the steps of any of the Group A embodiments to receive the user data from the host.
  • Embodiment 14 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 15 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 16 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 17 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 18 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 19 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 20 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 21 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;
  • SUBSTITUTE SHEET (Rule 26) 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 22 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 23 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 24 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 25 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 26 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 27 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 28 The method of the previous embodiment, further comprising, at the network node, transmitting the user data provided by the host for the UE.
  • Embodiment 29 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 30 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.
  • 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
  • Embodiment 31 The communication system of the previous embodiment, further comprising: the network node; and/or the user equipment.
  • 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 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 33 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 34 The host of the any of the previous 2 embodiments, wherein the initiating receipt of the user data comprises requesting the user data.
  • Embodiment 35 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 36 The method of the previous embodiment, further comprising at the network node, transmitting the received user data to the host.
  • SUBSTITUTE SHEET (Rule 26) At least some of the following abbreviations may be used in this disclosure. If there is an inconsistency between abbreviations, preference should be given to how it is used above. If listed multiple times below, the first listing should be preferred over any subsequent listing(s).
  • E-UTRAN Evolved UMTS Terrestrial RAN

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 de radiomessagerie pour une commande de réseau de transmission de petites données à terminaison mobile (MT-SDT) et une signalisation inter-nœuds. Dans certains modes de réalisation, un procédé mis en œuvre par un nœud de réseau pour activer le déclenchement d'une procédure MT-SDT consiste à : recevoir des données de liaison descendante pour un équipement utilisateur (UE) ; et envoyer un message de radiomessagerie à un nouveau nœud de réseau avec une indication MT-SDT. De cette manière, le déclenchement d'une procédure MT-SDT dans d'autres cellules que celles appartenant au gNB d'ancrage peut être activé. Ceci peut permettre au mécanisme MT-SDT de fonctionner dans la zone de notification (ARN) de réseau d'accès radio (RAN) lorsqu'il est configuré par le gNB d'ancrage.
PCT/SE2023/050371 2022-04-22 2023-04-24 Radiomessagerie pour commande de réseau mt-sdt et signalisation inter-nœuds WO2023204752A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202263333837P 2022-04-22 2022-04-22
US63/333,837 2022-04-22

Publications (1)

Publication Number Publication Date
WO2023204752A1 true WO2023204752A1 (fr) 2023-10-26

Family

ID=86286188

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2023/050371 WO2023204752A1 (fr) 2022-04-22 2023-04-24 Radiomessagerie pour commande de réseau mt-sdt et signalisation inter-nœuds

Country Status (1)

Country Link
WO (1) WO2023204752A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190208500A1 (en) * 2016-09-21 2019-07-04 Fujitsu Limited Downlink Data Transmission Method and Apparatus and Communication System
EP3837900A1 (fr) * 2018-08-13 2021-06-23 Qualcomm Incorporated Transmission de données de liaison descendante en mode inactif rrc
WO2021163394A1 (fr) * 2020-02-13 2021-08-19 Ofinno, Llc Transmission de petites données (sdt)

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190208500A1 (en) * 2016-09-21 2019-07-04 Fujitsu Limited Downlink Data Transmission Method and Apparatus and Communication System
EP3837900A1 (fr) * 2018-08-13 2021-06-23 Qualcomm Incorporated Transmission de données de liaison descendante en mode inactif rrc
WO2021163394A1 (fr) * 2020-02-13 2021-08-19 Ofinno, Llc Transmission de petites données (sdt)

Similar Documents

Publication Publication Date Title
WO2023012705A1 (fr) Partitionnement d'accès aléatoire et rapport d'accès aléatoire
WO2023105073A1 (fr) Commande d'admission inter-nœuds de réseau pour un ue relais de liaison latérale
WO2023277775A1 (fr) Enregistrement de types de défaillance différents pour des procédures de requête d'informations de système à la demande
WO2023204752A1 (fr) Radiomessagerie pour commande de réseau mt-sdt et signalisation inter-nœuds
WO2023185737A1 (fr) Procédé et appareil permettant d'effectuer une authentification/autorisation secondaire pour un dispositif terminal dans un réseau de communication
WO2024015000A1 (fr) Transmission de petites données à terminaison mobile
WO2023239280A1 (fr) Sélection de réponse ul pour transmission de petites données à terminaison mobile
WO2024096789A1 (fr) Accès aléatoire pendant cg-sdt
WO2023214919A1 (fr) Procédés pour améliorer des capacités d'économie d'énergie pour un ue après la réception de données dl dans une mt-sdt
WO2024099949A1 (fr) Inclusion d'identité de pcell (cellule primaire) dans un rapport ra tout en effectuant une procédure ra vers une cellule scg
WO2024144446A1 (fr) Optimisation de plan de commande pendant un changement d'amf
WO2024019652A1 (fr) Stockage de configurations qoe et rvqoe dans rrc_idle
WO2024172726A1 (fr) Systèmes et procédés de signalisation de paramètres de différenciation de radiomessagerie
WO2024068354A1 (fr) Extension de paramètres d'interdiction
WO2023166448A1 (fr) Rapport de mesurage b1/a4 optimisé
WO2023131929A1 (fr) Fourniture d'informations d'emplacement
WO2023218383A1 (fr) Systèmes et procédés pour permettre une configuration par service pour mt-sdt
WO2024094806A1 (fr) Ensembles de ressources de commande et blocs de signaux de synchronisation pour nouvelle radio ayant une largeur de bande inférieure à 5 mhz
WO2023153999A1 (fr) Indication d'aide à la libération pour une transmission de petites données de new radio (nr sdt)
WO2023166499A1 (fr) Systèmes et procédés pour partager un temps d'occupation de canal dans des communications de liaison latérale
WO2024210808A1 (fr) Procédure de commutation de cellule de mobilité déclenchée par couche 1/couche 2 (ltm)
WO2024218713A1 (fr) Interface pour partitionner des fonctions de réseau en bande de base
WO2024210807A1 (fr) Procédure de commutation de cellule de mobilité déclenchée par couche 1/couche 2 (ltm)
WO2023152043A1 (fr) Mesure et notification efficaces de l1-rsrp entre cellules
WO2023239272A1 (fr) Reconfiguration conditionnelle impliquant de multiples nœuds de réseau

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

Country of ref document: EP

Kind code of ref document: A1

DPE1 Request for preliminary examination filed after expiration of 19th month from priority date (pct application filed from 20040101)