WO2023239280A1 - Sélection de réponse ul pour transmission de petites données à terminaison mobile - Google Patents

Sélection de réponse ul pour transmission de petites données à terminaison mobile Download PDF

Info

Publication number
WO2023239280A1
WO2023239280A1 PCT/SE2023/050559 SE2023050559W WO2023239280A1 WO 2023239280 A1 WO2023239280 A1 WO 2023239280A1 SE 2023050559 W SE2023050559 W SE 2023050559W WO 2023239280 A1 WO2023239280 A1 WO 2023239280A1
Authority
WO
WIPO (PCT)
Prior art keywords
sdt
response
indication
configuration
host
Prior art date
Application number
PCT/SE2023/050559
Other languages
English (en)
Inventor
Andreas HÖGLUND
Luca FELTRIN
Revathy Narayanan
Jan Christoffersson
Henrik Enbuske
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 WO2023239280A1 publication Critical patent/WO2023239280A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • 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

Definitions

  • the present disclosure generally relates to Small Data Transmissions (SDTs).
  • SDTs Small Data Transmissions
  • the method also includes: receiving what procedures are available as the UL reply.
  • receiving the configuration comprises receiving a configuration from the network.
  • the configuration is received via one or more of the group consisting of: the ‘MT indication’ provided in the paging message; common RRC signaling; system information; dedicated RRC signaling; and RRCRelease in an earlier RRC connection.
  • the method also includes: informing the network of which type of response is to be expected based on the Contention Free Random Access, CFRA, preamble it chooses to send.
  • the received configuration comprises: CG-SDT should be selected if it is configured for the UE and the subsequent CG-SDT occasion is within X ms from when MT-SDT is received.
  • Figure 2 illustrates a method performed by a User Equipment (UE) for responding, according to some embodiments of the current disclosure
  • Figure 3 illustrates a method performed by a network node for receiving a response, according to some embodiments of the current disclosure
  • Figure 4 shows an example of a communication system in accordance with some embodiments
  • Figure 5 shows a UE in accordance with some embodiments
  • Figure 6 shows a network node in accordance with some embodiments
  • Figure 7 is a block diagram of a host, which may be an embodiment of the host of
  • Figure 8 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized.
  • Figure 9 shows a communication diagram of a host communicating via a network node with a UE over a partially wireless connection in accordance with some embodiments.
  • ‘legacy RA’ refers to the RA procedure specified for NR Rel-15 and Rel-16 and where the UE uses the RACH resources and configuration, including time and frequency resources and selection of the random access preamble, which are meant for random access in a general case and specifically not use the resources and random access preambles which may have been configured for RA-SDT as specified in Rel-17 specifications.
  • CG-SDT should be selected by the UE as the uplink response if it is configured for the UE and the subsequent CG-SDT occasion (or UL grant) is within X ms from when MT-SDT (or the ‘MT indication’) is received, when the value X is configurable.
  • the UE can inform the gNB on which type of response is to be expected based on the CFRA preamble it chooses to send in Step 2 of Figure 1.
  • this could be feature-specific whether certain UEs support certain types of response. For instance, based on the features that the UE supports, the gNB can know in advance which kind of response could be expected from the UE side.
  • Figure 2 illustrates a method performed by a UE for responding, according to some embodiments of the current disclosure.
  • the method includes one or more of receiving (200) a configuration regarding whether the UE shall use legacy RA; CG-SDT; or RA-SDT for the response to MT-SDT downlink transmission; receiving (202) what procedures are available as the U, reply; informing (204) the network of which type of response is to be expected based on the CFRA preamble it chooses to send; receiving (206) an MT-SDT indication; determining (208) which UL response should be selected by the UE among the group consisting of legacy RA, CG-SDT, and RA-SDT; and using (210) legacy RA as uplink reply even in the case when no configuration for SDT has been provided in the cell in system information or dedicated configuration.
  • the network nodes 410 facilitate direct or indirect connection of User Equipment (UE), such as by connecting UEs 412A, 412B, 412C, and 412D (one or more of which may be generally referred to as UEs 412) to the core network 406 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 400 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 400 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.
  • the UEs 412 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 410 and other communication devices.
  • the network nodes 410 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 412 and/or with other network nodes or equipment in the telecommunication network 402 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 402.
  • the core network 406 connects the network nodes 410 to one or more hosts, such as host 416. 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 406 includes one more core network nodes (e.g., core network node 408) 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 408.
  • 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 communication system 400 of Figure 4 enables connectivity between the UEs, network nodes, and hosts.
  • the communication system 400 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 402 is a cellular network that implements 3 GPP standardized features. Accordingly, the telecommunication network 402 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 402. For example, the telecommunication network 402 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 412 are configured to transmit and/or receive information without direct human interaction.
  • a UE may be designed to transmit information to the access network 404 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 404.
  • 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 414 communicates with the access network 404 to facilitate indirect communication between one or more UEs (e.g., UE 412C and/or 412D) and network nodes (e.g., network node 410B).
  • the hub 414 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs.
  • the hub 414 may be a broadband router enabling access to the core network 406 for the UEs.
  • the hub 414 may be a controller that sends commands or instructions to one or more actuators in the UEs.
  • the hub 414 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 414 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 414 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 414 then provides to the UE either directly, after performing local processing, and/or after adding additional local content.
  • the hub 414 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 414 may have a constant/persistent or intermittent connection to the network node 410B.
  • the hub 414 may also allow for a different communication scheme and/or schedule between the hub 414 and UEs (e.g., UE 412C and/or 412D), and between the hub 414 and the core network 406.
  • the hub 414 is connected to the core network 406 and/or one or more UEs via a wired connection.
  • the hub 414 may be configured to connect to a Machine-to-Machine (M2M) service provider over the access network 404 and/or to another UE over a direct connection.
  • M2M Machine-to-Machine
  • UEs may establish a wireless connection with the network nodes 410 while still connected via the hub 414 via a wired or wireless connection.
  • the hub 414 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 410B.
  • the hub 414 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 410B, 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 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. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller).
  • a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).
  • the UE 500 includes processing circuitry 502 that is operatively coupled via a bus 504 to an input/output interface 506, a power source 508, memory 510, a communication interface 512, and/or any other component, or any combination thereof.
  • Certain UEs may utilize all or a subset of the components shown in Figure 5. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.
  • the processing circuitry 502 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 510.
  • the processing circuitry 502 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 502 may include multiple Central Processing Units (CPUs).
  • the input/output interface 506 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 500.
  • 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 508 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 508 may further include power circuitry for delivering power from the power source 508 itself, and/or an external power source, to the various parts of the UE 500 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging the power source 508.
  • Power circuitry may perform any formatting, converting, or other modification to the power from the power source 508 to make the power suitable for the respective components of the UE 500 to which power is supplied.
  • the memory 510 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 510 includes one or more application programs 514, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 516.
  • the memory 510 may store, for use by the UE 500, any of a variety of various operating systems or combinations of operating systems.
  • the memory 510 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 510 may allow the UE 500 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 510, which may be or comprise a device-readable storage medium.
  • the processing circuitry 502 may be configured to communicate with an access network or other network using the communication interface 512.
  • the communication interface 512 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 522.
  • the communication interface 512 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 518 and/or a receiver 520 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth).
  • the transmitter 518 and receiver 520 may be coupled to one or more antennas (e.g., the antenna 522) and may share circuit components, software, or firmware, or alternatively be implemented separately.
  • communication functions of the communication interface 512 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/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.
  • 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
  • Ethernet Transmission Control Protocol/Intemet Protocol
  • TCP/IP Transmission Control 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 512, 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 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.
  • a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone.
  • the first UE may adjust the throttle on the drone (e.g., by controlling an actuator) to increase or decrease the drone’s speed.
  • the first and/or the second UE can also include more than one of the functionalities described above.
  • a UE might comprise the sensor and the actuator and handle communication of data for both the speed sensor and the actuators.
  • FIG. 6 shows a network node 600 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
  • the network node 600 includes processing circuitry 602, memory 604, a communication interface 606, and a power source 608.
  • the network node 600 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 600 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 memory 604 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 602.
  • 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)
  • the memory 604 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 602 and utilized by the network node 600.
  • the memory 604 may be used to store any calculations made by the processing circuitry 602 and/or any data received via the communication interface 606.
  • the processing circuitry 602 and the memory 604 are integrated.
  • the communication interface 606 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 606 comprises port(s)/terminal(s) 616 to send and receive data, for example to and from a network over a wired connection.
  • the communication interface 606 also includes radio front-end circuitry 618 that may be coupled to, or in certain embodiments a part of, the antenna 610.
  • the radio front-end circuitry 618 comprises filters 620 and amplifiers 622.
  • the radio front-end circuitry 618 may be connected to the antenna 610 and the processing circuitry 602.
  • the radio front-end circuitry 618 may be configured to condition signals communicated between the antenna 610 and the processing circuitry 602.
  • the network node 600 does not include separate radio front-end circuitry 618; instead, the processing circuitry 602 includes radio front-end circuitry and is connected to the antenna 610. Similarly, in some embodiments, all or some of the RF transceiver circuitry 612 is part of the communication interface 606. In still other embodiments, the communication interface 606 includes the one or more ports or terminals 616, the radio front-end circuitry 618, and the RF transceiver circuitry 612 as part of a radio unit (not shown), and the communication interface 606 communicates with the baseband processing circuitry 614, which is part of a digital unit (not shown).
  • the antenna 610, the communication interface 606, and/or the processing circuitry 602 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node 600. Any information, data, and/or signals may be received from a UE, another network node, and/or any other network equipment. Similarly, the antenna 610, the communication interface 606, and/or the processing circuitry 602 may be configured to perform any transmitting operations described herein as being performed by the network node 600. Any information, data, and/or signals may be transmitted to a UE, another network node, and/or any other network equipment.
  • the power source 608 provides power to the various components of the network node 600 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component).
  • the power source 608 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 600 with power for performing the functionality described herein.
  • the network node 600 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 608.
  • the power source 608 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 600 may include additional components beyond those shown in Figure 6 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein.
  • the network node 600 may include user interface equipment to allow input of information into the network node 600 and to allow output of information from the network node 600. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 600.
  • FIG. 7 is a block diagram of a host 700, which may be an embodiment of the host 416 of Figure 4, in accordance with various aspects described herein.
  • the host 700 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 700 may provide one or more services to one or more UEs.
  • the host 700 includes processing circuitry 702 that is operatively coupled via a bus 704 to an input/output interface 706, a network interface 708, a power source 710, and memory 712.
  • Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 5 and 6, such that the descriptions thereof are generally applicable to the corresponding components of the host 700.
  • the memory 712 may include one or more computer programs including one or more host application programs 714 and data 716, which may include user data, e.g., data generated by a UE for the host 700 or data generated by the host 700 for a UE.
  • Embodiments of the host 700 may utilize only a subset or all of the components shown.
  • the host application programs 714 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 700 may select and/or indicate a different host for Over-The-Top (OTT) services for a UE.
  • the host application programs 714 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.
  • Applications 802 (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.
  • the VMs 808 comprise virtual processing, virtual memory, virtual networking, or interface and virtual storage, and may be run by a corresponding virtualization layer 806.
  • Different embodiments of the instance of a virtual appliance 802 may be implemented on one or more of the VMs 808, 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 808 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 808, and that part of the hardware 804 that executes that VM be it hardware dedicated to that VM and/or hardware shared by that VM with others of the VMs 808, forms separate virtual network elements.
  • a virtual network function is responsible for handling specific network functions that run in one or more VMs 808 on top of the hardware 804 and corresponds to the application 802.
  • the hardware 804 may be implemented in a standalone network node with generic or specific components.
  • the hardware 804 may implement some functions via virtualization.
  • the hardware 804 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 810, which, among others, oversees lifecycle management of the applications 802.
  • the hardware 804 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 812 which may alternatively be used for communication between hardware nodes and radio units.
  • Figure 9 shows a communication diagram of a host 902 communicating via a network node 904 with a UE 906 over a partially wireless connection in accordance with some embodiments.
  • Example implementations, in accordance with various embodiments, of the UE (such as the UE 412A of Figure 4 and/or the UE 500 of Figure 5), the network node (such as the network node 410A of Figure 4 and/or the network node 600 of Figure 6), and the host (such as the host 416 of Figure 4 and/or the host 700 of Figure 7) discussed in the preceding paragraphs will now be described with reference to Figure 9.
  • the network node 904 includes hardware enabling it to communicate with the host 902 and the UE 906 via a connection 960.
  • the connection 960 may be direct or pass through a core network (like the core network 406 of Figure 4) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks.
  • an intermediate network may be a backbone network or the Internet.
  • the UE 906 includes hardware and software, which is stored in or accessible by the UE 906 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 906 with the support of the host 902.
  • 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 906 with the support of the host 902.
  • an executing host application may communicate with the executing client application via the OTT connection 950 terminating at the UE 906 and the host 902.
  • 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 950 may transfer both the request data and the user data.
  • the UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT connection 950.
  • the OTT connection 950 may extend via the connection 960 between the host 902 and the network node 904 and via a wireless connection 970 between the network node 904 and the UE 906 to provide the connection between the host 902 and the UE 906.
  • the connection 960 and the wireless connection 970, over which the OTT connection 950 may be provided, have been drawn abstractly to illustrate the communication between the host 902 and the UE 906 via the network node 904, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • the host 902 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 906.
  • the user data is associated with a UE 906 that shares data with the host 902 without explicit human interaction.
  • the host 902 initiates a transmission carrying the user data towards the UE 906.
  • the host 902 may initiate the transmission responsive to a request transmitted by the UE 906.
  • the request may be caused by human interaction with the UE 906 or by operation of the client application executing on the UE 906.
  • the UE 906 executes a client application which provides user data to the host 902.
  • the user data may be provided in reaction or response to the data received from the host 902.
  • the UE 906 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 906. Regardless of the specific manner in which the user data was provided, the UE 906 initiates, in step 918, transmission of the user data towards the host 902 via the network node 904.
  • the network node 904 receives user data from the UE 906 and initiates transmission of the received user data towards the host 902.
  • the host 902 receives the user data carried in the transmission initiated by the UE 906.
  • One or more of the various embodiments improve the performance of OTT services provided to the UE 906 using the OTT connection 950, in which the wireless connection 970 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 902.
  • the host 902 may process audio and video data which may have been retrieved from a UE for use in creating maps.
  • the host 902 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights).
  • the host 902 may store surveillance video uploaded by a UE.
  • the host 902 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 reconfiguring of the OTT connection 950 may include message format, retransmission settings, preferred routing, etc.; the reconfiguring need not directly alter the operation of the network node 904. 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 902.
  • the measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 950 while monitoring propagation times, errors, etc.
  • 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 responding, the method comprising one or more of: receiving (200) a configuration regarding whether the UE shall use legacy Random Access, RA; Configured Grant - Small Data Transmission, CG-SDT; or RA-SDT for the response to Mobile Terminated-SDT, MT-SDT, downlink transmission; receiving (202) what procedures are available as the Uplink, UL, reply; informing (204) the network of which type of response is to be expected based on the Contention Free Random Access, CFRA, preamble it chooses to send; receiving (206) an MT-SDT indication; determining (208) which UL response should be selected by the UE among the group consisting of: legacy RA, CG-SDT, and RA-SDT; and using (210) legacy RA as uplink reply even in the case when no configuration for SDT has been provided in the cell in system information or dedicated configuration.
  • Embodiment 3 The method of any of the previous embodiments wherein the UE uses legacy RA as the response to MT-SDT.
  • Embodiment 4 The method of any of the previous embodiments wherein receiving the configuration comprises receiving a configuration from the network.
  • Embodiment 5 The method of any of the previous embodiments wherein the configuration is provided to the UE as part of the MT-SDT configuration.
  • Embodiment 6 The method of any of the previous embodiments wherein the configuration is received via one or more of the group consisting of: the ‘MT indication’ provided in the paging message; common RRC signaling; system information; dedicated RRC signaling; and RRCRelease in an earlier RRC connection.
  • Embodiment 9 The method of any of the previous embodiments wherein the received configuration comprises one or more of the group consisting of: CG-SDT should be selected if it is configured for the UE and the subsequent CG-SDT occasion (e.g., or UL grant) is within X ms from when MT-SDT (e.g., or the ‘MT indication’) is received.
  • Embodiment 10 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 14 The method of any of the previous embodiments wherein the configuration is provided to the UE as part of the MT-SDT configuration.
  • Embodiment 15 The method of any of the previous embodiments wherein the configuration is transmitted via one or more of the group consisting of: the ‘MT indication’ provided in the paging message; common RRC signaling; system information; dedicated RRC signaling; and RRCRelease in an earlier RRC connection.
  • Embodiment 16 The method of any of the previous embodiments wherein the ‘MT indication’ and the configuration are provided to the UE either: in the DCI in the paging occasion (e.g., on PDCCH); or in the paging or MT-SDT data message scheduled (e.g., on PDSCH).
  • Embodiment 17 The method of any of the previous embodiments wherein the transmitted configuration comprises rules and/or thresholds for the determination of whether the UE shall use legacy RA, CG-SDT, or RA-SDT for the response.
  • Embodiment 18 The method of any of the previous embodiments wherein the transmitted configuration comprises one or more of the group consisting of: CG-SDT should be selected if it is configured for the UE and the subsequent CG-SDT occasion (e.g., or UL grant) is within X ms from when MT-SDT (e.g., or the ‘MT indication’) is received.
  • CG-SDT e.g., or UL grant
  • Embodiment 19 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. [0133] Group C Embodiments
  • Embodiment 20 A user equipment for responding, 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 21 A network node for receiving a response, 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 22 A user equipment (UE) for responding, 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 23 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 24 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 25 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 26 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 27 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 28 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 29 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 30 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 31 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 32 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 33 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 34 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 35 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 36 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 37 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 38 The method of the previous embodiment, further comprising, at the network node, transmitting the user data provided by the host for the UE.
  • Embodiment 39 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 40 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 41 The communication system of the previous embodiment, further comprising: the network node; and/or the user equipment.
  • Embodiment 42 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 43 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 44 The host of the any of the previous 2 embodiments, wherein the initiating receipt of the user data comprises requesting the user data.
  • Embodiment 45 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

Landscapes

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

Abstract

L'invention fournit des systèmes et des procédés de sélection de réponse de liaison montante (UL) pour une transmission de petites données à terminaison mobile (MT-SDT). Dans certains modes de réalisation, un procédé mis en œuvre par un équipement utilisateur (UE) pour répondre consiste à : recevoir une indication MT-SDT; déterminer quelle réponse UL doit être sélectionnée par l'UE parmi le groupe comprenant : un accès aléatoire patrimonial (RA); une autorisation configurée SDT (CG-SDT); et RA-SDT; et répondre à l'indication MT-SDT reçue à l'aide de la réponse UL déterminée. L'avantage de certains modes de réalisation de la présente divulgation est de permettre un RA patrimonial en tant que réponse à MT-SDT qui conduit à une réduction de déchets de ressources et à une possibilité de déployer MT-SDT également dans des cellules où Rel-17 MO-SDT n'a pas été mis en œuvre. FIG. 2 :
PCT/SE2023/050559 2022-06-06 2023-06-05 Sélection de réponse ul pour transmission de petites données à terminaison mobile WO2023239280A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202263349483P 2022-06-06 2022-06-06
US63/349,483 2022-06-06

Publications (1)

Publication Number Publication Date
WO2023239280A1 true WO2023239280A1 (fr) 2023-12-14

Family

ID=86896122

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2023/050559 WO2023239280A1 (fr) 2022-06-06 2023-06-05 Sélection de réponse ul pour transmission de petites données à terminaison mobile

Country Status (1)

Country Link
WO (1) WO2023239280A1 (fr)

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "On MT-SDTWID formulation regarding UL response", vol. TSG RAN, no. Budapest, Hungary; 20220606 - 20220609, 30 May 2022 (2022-05-30), XP052154445, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/TSG_RAN/TSGR_96/Docs/RP-221422.zip RP-221422 - On Rel-18 MT-SDT scope.pptx> [retrieved on 20220530] *
ETSI MCC: "Report of 3GPP TSG RAN WG2 meeting #117-e, Online", no. 20220221 - 20220303, 23 May 2022 (2022-05-23), XP052204616, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG2_RL2/TSGR2_117-e/Report/R2-2204401.zip R2-2204401.docx> [retrieved on 20220523] *

Similar Documents

Publication Publication Date Title
WO2023012705A1 (fr) Partitionnement d&#39;accès aléatoire et rapport d&#39;accès aléatoire
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
WO2023031836A1 (fr) Dissimulation de topologie en 5gc avec itinérance
WO2023239280A1 (fr) Sélection de réponse ul pour transmission de petites données à terminaison mobile
WO2023185737A1 (fr) Procédé et appareil permettant d&#39;effectuer une authentification/autorisation secondaire pour un dispositif terminal dans un réseau de communication
WO2024027839A1 (fr) Procédé et appareil de configuration de type de rapport d&#39;emplacement
WO2024027838A9 (fr) Procédé et appareil pour arrêter un rapport de localisation
WO2023204752A1 (fr) Radiomessagerie pour commande de réseau mt-sdt et signalisation inter-nœuds
WO2024144446A1 (fr) Optimisation de plan de commande pendant un changement d&#39;amf
WO2024099949A1 (fr) Inclusion d&#39;identité de pcell (cellule primaire) dans un rapport ra tout en effectuant une procédure ra vers une cellule scg
WO2023131929A1 (fr) Fourniture d&#39;informations d&#39;emplacement
WO2023166448A1 (fr) Rapport de mesurage b1/a4 optimisé
WO2024096789A1 (fr) Accès aléatoire pendant cg-sdt
WO2024068354A1 (fr) Extension de paramètres d&#39;interdiction
WO2024117960A1 (fr) Filtre de liste de bandes de fréquences appliquées prédéfinies
WO2024033811A1 (fr) Signalisation de contexte d&#39;ue et de données de ng-ran à un réseau cœur
WO2023152043A1 (fr) Mesure et notification efficaces de l1-rsrp entre cellules
WO2024019652A1 (fr) Stockage de configurations qoe et rvqoe dans rrc_idle
WO2024015000A1 (fr) Transmission de petites données à terminaison mobile
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
WO2023068983A1 (fr) Rapport de mesurage basé sur des configurations de mesurage utilisant des indications de priorité spécifiques à la fréquence
WO2023153978A1 (fr) Informations d&#39;historique d&#39;eu (uhi) et informations d&#39;historique de mobilité (mhi) pendant l&#39;activation/désactivation de scg
WO2023218383A1 (fr) Systèmes et procédés pour permettre une configuration par service pour mt-sdt
EP4338469A1 (fr) Mises à jour de paramètres de sécurité pendant une resélection de cellule pour sdt nr

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

Country of ref document: EP

Kind code of ref document: A1