[go: up one dir, main page]

WO2025190066A1 - Gestion de régulation de l'encombrement pour le transport de données d'utilisateur par l'intermédiaire d'un plan de commande dans des communications mobiles - Google Patents

Gestion de régulation de l'encombrement pour le transport de données d'utilisateur par l'intermédiaire d'un plan de commande dans des communications mobiles

Info

Publication number
WO2025190066A1
WO2025190066A1 PCT/CN2025/078705 CN2025078705W WO2025190066A1 WO 2025190066 A1 WO2025190066 A1 WO 2025190066A1 CN 2025078705 W CN2025078705 W CN 2025078705W WO 2025190066 A1 WO2025190066 A1 WO 2025190066A1
Authority
WO
WIPO (PCT)
Prior art keywords
follow
request
mobility
emergency
updating procedure
Prior art date
Legal status (The legal status 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 status listed.)
Pending
Application number
PCT/CN2025/078705
Other languages
English (en)
Inventor
Puneet PUNEET
Yu-Hsin Lin
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
MediaTek Inc
Original Assignee
MediaTek Inc
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 MediaTek Inc filed Critical MediaTek Inc
Publication of WO2025190066A1 publication Critical patent/WO2025190066A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0252—Traffic management, e.g. flow control or congestion control per individual bearer or channel

Definitions

  • the present disclosure is generally related to mobile communications and, more particularly, to handling congestion control for transport of user data via a control plane in mobile communications.
  • a network may activate congestion control for transport of user data via the control plane, as specified in 3GPP Technial Specification (TS) 23.501.
  • a user equipment UE
  • the network may include a value for the control plane data back-off timer T3448 in a REGISTRATION ACCEPT, SERVICE ACCEPT or SERVICE REJECT message, and the network is to store an control plane data back-off time on a per-UE basis.
  • the UE starts the timer T3448 with the value informed in the message.
  • the network should select the value for the timer T3448 for the informed UEs so that timeouts are not synchronised.
  • Mobility Registration Update MRU
  • T3448 Mobility Registration Update
  • An objective of the present disclosure is to propose solutions or schemes that address the issue (s) described herein. More specifically, various schemes proposed in the present disclosure are believed to provide solutions pertaining to handling congestion control for transport of user data via a control plane in mobile communications. It is believed that implementations of one or more of the schemes proposed herein may address or otherwise alleviate the issues described above.
  • a method may involve a UE determining that a control plane data back-off timer T3448 is running. In response to the determining, the method may also involve the UE starting any mobility and periodic registration updating procedure with a follow-on request indicator set to “follow-on request pending” .
  • a method may involve a UE determining that a control plane data back-off timer T3448 is running. In response to the determining, the method may also involve the UE performing one or more actions.
  • radio access technologies such as 5 th Generation (5G) /New Radio (NR) /Beyond Fifth-Generation (B5G) mobile communications
  • 5G 5 th Generation
  • NR New Radio
  • B5G Beyond Fifth-Generation
  • the proposed concepts, schemes and any variation (s) /derivative (s) thereof may be implemented in, for and by other types of radio access technologies, networks and network topologies such as, for example and without limitation, 4 th Generation (4G) /Long-Term Evolution (LTE) , LTE-Advanced, LTE-Advanced Pro, Internet-of-Things (IoT) , Narrow Band Internet of Things (NB-IoT) , Industrial Internet of Things (IIoT) , vehicle-to-everything (V2X) , and non-terrestrial network (NTN) communications.
  • 4G 4 th Generation
  • LTE Long-Term Evolution
  • LTE-Advanced LTE-Advanced
  • FIG. 1 is a diagram of an example network environment in which various solutions and schemes in accordance with the present disclosure may be implemented.
  • FIG. 2 is a block diagram of an example communication system under a proposed scheme in accordance with the present disclosure.
  • FIG. 3 is a flowchart of a second example process under a proposed scheme in accordance with the present disclosure.
  • FIG. 4 is a flowchart of a second example process under a proposed scheme in accordance with the present disclosure. DETAILED DESCRIPTION OF PREFERRED IMPLEMENTATIONS
  • Implementations in accordance with the present disclosure relate to various techniques, methods, schemes and/or solutions pertaining to handling congestion control for transport of user data via a control plane in mobile communications.
  • a number of possible solutions may be implemented separately or jointly. That is, although these possible solutions may be described below separately, two or more of these possible solutions may be implemented in one combination or another.
  • FIG. 1 illustrates an example network environment 100 in which various solutions and schemes in accordance with the present disclosure may be implemented.
  • FIG. 2 ⁇ FIG. 4 illustrate examples of implementation of various proposed schemes in network environment 100 in accordance with the present disclosure. The following description of various proposed schemes is provided with reference to FIG. 1 ⁇ FIG. 4.
  • network environment 100 may involve a UE 110, such as a mobile device or smartphone, in wireless communication with a wireless network 120 as part of a communication network.
  • the wireless network 120 may be one or more public land mobile networks (PLMNs) including 5G/NR domain, 4G/LTE domain, and 2 nd Generation/3 rd Generation (2G/3G) domain.
  • PLMNs public land mobile networks
  • UE 110 may initially be in wireless communication with wireless network 120 via a base station or network node 125 (e.g., an eNB, gNB or transmit-receive point (TRP) ) .
  • UE 110 and the wireless network 120 may implement various schemes pertaining to handling congestion control for transport of user data via a control plane in mobile communications in accordance with the present disclosure, as described herein.
  • a lower layer may refer to a layer in the 5GMM protocol stack that is lower than the radio resource control (RRC) layer, such as a packet data convergence protocol (PDCP) layer, a radio control link (RLC) layer, a medium access control (MAC) layer, a physical (PHY) layer, or so forth.
  • RRC radio resource control
  • PDCP packet data convergence protocol
  • RLC radio control link
  • MAC medium access control
  • PHY physical
  • UE 110 when a timer T3448 is running, UE 110 may be allowed to perform one or more of a number of actions. For instance, when timer T3448 is running, UE 110 may send a REGISTRATION REQUEST message to wireless network 120 for emergency services or for emergency services fallback. Alternatively, or additionally, when timer T3448 is running, UE 110 may start any mobility and periodic registration update procedure with a follow-on request indicator set to "Follow-on request pending" when: (a) UE 110 has an emergency protocol data unit (PDU) session established or is establishing an emergency PDU session; and/or (b) UE 110 receives a request from the upper layers to perform emergency services fallback.
  • PDU emergency protocol data unit
  • UE 110 may send a CONTROL PLANE SERVICE REQUEST message or a TRACKING AREA UPDATE REQUEST message to wireless network 120 for emergency services or circuit switching (CS) fallback for emergency call.
  • UE 110 may start a tracking area updating (TAU) procedure with the "signaling active" flag set when: (a) UE 110 has a packet data network (PDN) connection for emergency bearer services established or is establishing a PDN connection for emergency bearer services; and/or (b) UE 110 is requested by the upper layer for a CS fallback for emergency call.
  • PDN packet data network
  • UE 110 may initiate a service request procedure for transport of user data via the control plane when: (a) UE 110 has a PDN connection for emergency bearer services established or is establishing a PDN connection for emergency bearer services; and/or (b) UE 110 is requested by the upper layer for a CS fallback for emergency call.
  • UE 110 in a 5 th Generation Mobility Management idle (5GMM-IDLE) mode may not start any mobility and periodic registration update procedure with the follow-on request indicator set to "Follow-on request pending" unless any of the following conditions exists: (1) UE 110 is a UE configured for high priority access in a selected public land mobile network (PLMN) ; (2) UE 110, which is only using 5GS services with control plane CIoT 5GS optimization, received a paging request; (3) UE 110 in the NB-N1 mode is requested by an upper layer to transmit user data related to an exceptional event and UE 110 is allowed to use exception data reporting; (4) UE 110 has an emergency PDU session established or is establishing an emergency PDU session; or (5) UE 110 receives a request from the upper layers to perform emergency services fallback. Moreover, UE 110 may stay in the current serving cell and apply the normal cell reselection process.
  • UE 110 may be allowed to respond to paging with a CONTROL PLANE SERVICE REQUEST message without uplink data.
  • UE 110 may be allowed to send a CONTROL PLANE SERVICE REQUEST message or a TRACKING AREA UPDATE REQUEST message for emergency services or CS fallback for emergency call.
  • FIG. 2 illustrates an example communication system 200 having at least an example apparatus 210 and an example apparatus 220 in accordance with an implementation of the present disclosure.
  • apparatus 210 and apparatus 220 may perform various functions to implement schemes, techniques, processes and methods described herein pertaining to handling congestion control for transport of user data via a control plane in mobile communications, including the various schemes described above with respect to various proposed designs, concepts, schemes, systems and methods described above, including network environment 100, as well as processes described below.
  • Each of apparatus 210 and apparatus 220 may be a part of an electronic apparatus, which may be a network apparatus or a UE (e.g., UE 110) , such as a portable or mobile apparatus, a wearable apparatus, a vehicular device or a vehicle, a wireless communication apparatus or a computing apparatus.
  • a network apparatus e.g., UE 110
  • UE e.g., UE 110
  • each of apparatus 210 and apparatus 220 may be implemented in a smartphone, a smart watch, a personal digital assistant, an electronic control unit (ECU) in a vehicle, a digital camera, or a computing equipment such as a tablet computer, a laptop computer or a notebook computer.
  • ECU electronice control unit
  • Each of apparatus 210 and apparatus 220 may also be a part of a machine type apparatus, which may be an IoT apparatus such as an immobile or a stationary apparatus, a home apparatus, a roadside unit (RSU) , a wire communication apparatus or a computing apparatus.
  • IoT apparatus such as an immobile or a stationary apparatus, a home apparatus, a roadside unit (RSU) , a wire communication apparatus or a computing apparatus.
  • RSU roadside unit
  • each of apparatus 210 and apparatus 220 may be implemented in a smart thermostat, a smart fridge, a smart door lock, a wireless speaker or a home control center.
  • apparatus 210 and/or apparatus 220 may be implemented in an eNodeB in an LTE, LTE-Advanced or LTE-Advanced Pro network or in a gNB or TRP in a 5G network, an NR network, or an IoT network.
  • each of apparatus 210 and apparatus 220 may be implemented in the form of one or more integrated-circuit (IC) chips such as, for example and without limitation, one or more single-core processors, one or more multi-core processors, one or more complex-instruction-set-computing (CISC) processors, or one or more reduced-instruction-set-computing (RISC) processors.
  • IC integrated-circuit
  • CISC complex-instruction-set-computing
  • RISC reduced-instruction-set-computing
  • each of apparatus 210 and apparatus 220 may be implemented in or as a network apparatus or a UE.
  • Each of apparatus 210 and apparatus 220 may include at least some of those components shown in FIG. 2 such as a processor 212 and a processor 222, respectively, for example.
  • Each of apparatus 210 and apparatus 220 may further include one or more other components not pertinent to the proposed scheme of the present disclosure (e.g., internal power supply, display device and/or user interface device) , and, thus, such component (s) of apparatus 210 and apparatus 220 are neither shown in FIG. 2 nor described below in the interest of simplicity and brevity.
  • components not pertinent to the proposed scheme of the present disclosure e.g., internal power supply, display device and/or user interface device
  • each of processor 212 and processor 222 may be implemented in the form of one or more single-core processors, one or more multi-core processors, or one or more CISC or RISC processors. That is, even though a singular term “a processor” is used herein to refer to processor 212 and processor 222, each of processor 212 and processor 222 may include multiple processors in some implementations and a single processor in other implementations in accordance with the present disclosure.
  • each of processor 212 and processor 222 may be implemented in the form of hardware (and, optionally, firmware) with electronic components including, for example and without limitation, one or more transistors, one or more diodes, one or more capacitors, one or more resistors, one or more inductors, one or more memristors and/or one or more varactors that are configured and arranged to achieve specific purposes in accordance with the present disclosure.
  • each of processor 212 and processor 222 is a special-purpose machine specifically designed, arranged, and configured to perform specific tasks including those pertaining to handling congestion control for transport of user data via a control plane in mobile communications in accordance with various implementations of the present disclosure.
  • apparatus 210 may also include a transceiver 216 coupled to processor 212.
  • Transceiver 216 may be capable of wirelessly transmitting and receiving data.
  • transceiver 216 may be capable of wirelessly communicating with different types of wireless networks of different radio access technologies (RATs) .
  • RATs radio access technologies
  • transceiver 216 may be equipped with a plurality of antenna ports (not shown) such as, for example, four antenna ports. That is, transceiver 216 may be equipped with multiple transmit antennas and multiple receive antennas for multiple-input multiple-output (MIMO) wireless communications.
  • apparatus 220 may also include a transceiver 226 coupled to processor 222.
  • Transceiver 226 may include a transceiver capable of wirelessly transmitting and receiving data.
  • transceiver 226 may be capable of wirelessly communicating with different types of UEs/wireless networks of different RATs.
  • transceiver 226 may be equipped with a plurality of antenna ports (not shown) such as, for example, four antenna ports. That is, transceiver 226 may be equipped with multiple transmit antennas and multiple receive antennas for MIMO wireless communications.
  • apparatus 210 may further include a memory 214 coupled to processor 212 and capable of being accessed by processor 212 and storing data therein.
  • apparatus 220 may further include a memory 224 coupled to processor 222 and capable of being accessed by processor 222 and storing data therein.
  • Each of memory 214 and memory 224 may include a type of random-access memory (RAM) such as dynamic RAM (DRAM) , static RAM (SRAM) , thyristor RAM (T-RAM) and/or zero-capacitor RAM (Z-RAM) .
  • RAM random-access memory
  • DRAM dynamic RAM
  • SRAM static RAM
  • T-RAM thyristor RAM
  • Z-RAM zero-capacitor RAM
  • each of memory 214 and memory 224 may include a type of read-only memory (ROM) such as mask ROM, programmable ROM (PROM) , erasable programmable ROM (EPROM) and/or electrically erasable programmable ROM (EEPROM) .
  • ROM read-only memory
  • PROM programmable ROM
  • EPROM erasable programmable ROM
  • EEPROM electrically erasable programmable ROM
  • each of memory 214 and memory 224 may include a type of non-volatile random-access memory (NVRAM) such as flash memory, solid-state memory, ferroelectric RAM (FeRAM) , magnetoresistive RAM (MRAM) and/or phase-change memory.
  • NVRAM non-volatile random-access memory
  • Each of apparatus 210 and apparatus 220 may be a communication entity capable of communicating with each other using various proposed schemes in accordance with the present disclosure.
  • a description of capabilities of apparatus 210, as a UE (e.g., UE 110) , and apparatus 220, as a network node (e.g., network node 125) of a network is provided below in the context of example processes 300 and 400.
  • FIG. 3 illustrates an example process 300 in accordance with an implementation of the present disclosure.
  • Process 300 may represent an aspect of implementing various proposed designs, concepts, schemes, systems and methods described above. More specifically, process 300 may represent an aspect of the proposed concepts and schemes pertaining to handling congestion control for transport of user data via a control plane in mobile communications in accordance with the present disclosure.
  • Process 300 may include one or more operations, actions, or functions as illustrated by one or more of blocks 310 and 320. Although illustrated as discrete blocks, various blocks of process 300 may be divided into additional blocks, combined into fewer blocks, or eliminated, depending on the desired implementation. Moreover, the blocks/sub-blocks of process 300 may be executed in the order shown in FIG. 3 or, alternatively, in a different order.
  • Process 300 may be implemented by or in apparatus 210 and apparatus 220 as well as any variations thereof. Solely for illustrative purposes and without limiting the scope, process 300 is described below in the context of apparatus 210 as a UE (e.g., UE 110) and apparatus 220 as a communication entity such as a network node or base station (e.g., network node 125) of a network (e.g., wireless network 120) . Process 300 may begin at block 310.
  • UE e.g., UE 110
  • apparatus 220 as a communication entity such as a network node or base station (e.g., network node 125) of a network (e.g., wireless network 120) .
  • Process 300 may begin at block 310.
  • process 300 may involve processor 212 of apparatus 210, as UE 110, determining that a control plane data back-off timer T3448 is running. Process 300 may proceed from 310 to 320.
  • process 300 may involve processor 212 starting any mobility and periodic registration updating procedure with a follow-on request indicator set to “follow-on request pending” responsive to the determining.
  • process 300 may involve processor 212 starting any mobility and periodic registration updating procedure with the follow-on request indicator set to “follow-on request pending” when apparatus 210 has an emergency PDU session established.
  • process 300 may involve processor 212 starting any mobility and periodic registration updating procedure with the follow-on request indicator set to “follow-on request pending” when apparatus 210 is establishing an emergency PDU session.
  • process 300 may involve processor 212 starting any mobility and periodic registration updating procedure with the follow-on request indicator set to “follow-on request pending” when apparatus 210 receives a request from an upper layer to perform an emergency services fallback.
  • process 300 may further involve processor 212 sending, via transceiver 216, a registration request message for emergency services or for emergency services fallback.
  • FIG. 4 illustrates an example process 400 in accordance with an implementation of the present disclosure.
  • Process 400 may represent an aspect of implementing various proposed designs, concepts, schemes, systems and methods described above. More specifically, process 400 may represent an aspect of the proposed concepts and schemes pertaining to handling congestion control for transport of user data via a control plane in mobile communications in accordance with the present disclosure.
  • Process 400 may include one or more operations, actions, or functions as illustrated by one or more of blocks 410 and 420. Although illustrated as discrete blocks, various blocks of process 400 may be divided into additional blocks, combined into fewer blocks, or eliminated, depending on the desired implementation. Moreover, the blocks/sub-blocks of process 400 may be executed in the order shown in FIG. 4 or, alternatively, in a different order.
  • Process 400 may be implemented by or in apparatus 210 and apparatus 220 as well as any variations thereof. Solely for illustrative purposes and without limiting the scope, process 400 is described below in the context of apparatus 210 as a UE (e.g., UE 110) and apparatus 220 as a communication entity such as a network node or base station (e.g., network node 125) of a network (e.g., wireless network 120) . Process 400 may begin at block 410.
  • process 400 may involve processor 212 of apparatus 210, as UE 110, determining that a control plane data back-off timer T3448 is running. Process 400 may proceed from 410 to 420.
  • process 400 may involve processor 212 performing one or more actions responsive to the determining.
  • process 400 may involve processor 212 starting any mobility and periodic registration updating procedure with a follow-on request indicator set to “follow-on request pending” .
  • process 400 may involve processor 212 starting any mobility and periodic registration updating procedure with the follow-on request indicator set to “follow-on request pending” when apparatus 210 has an emergency PDU session established.
  • process 400 may involve processor 212 starting any mobility and periodic registration updating procedure with the follow-on request indicator set to “follow-on request pending” when apparatus 210 is establishing an emergency PDU session.
  • process 400 may involve processor 212 starting any mobility and periodic registration updating procedure with the follow-on request indicator set to “follow-on request pending” when apparatus 210 receives a request from an upper layer to perform an emergency services fallback.
  • process 400 may involve processor 212 sending, via transceiver 216, a registration request message for emergency services or for emergency services fallback.
  • process 400 may involve processor 212 sending, via transceiver 216, a control plane service request message or a tracking area update request message for emergency services or CS fallback for an emergency call.
  • process 400 may involve processor 212 starting a tracking area updating procedure with a “signaling active” flag set when apparatus 210 has a PDN connection for emergency bearer services established or is establishing the PDN connection for the emergency bearer services.
  • process 400 may involve processor 212 starting a tracking area updating procedure with a “signaling active” flag set when apparatus 210 is requested by an upper layer for a CS fallback for an emergency call.
  • process 400 may involve processor 212 initiating a service request procedure for transport of user data via a control plane when apparatus 210 has a PDN connection for emergency bearer services established or is establishing the PDN connection for the emergency bearer services.
  • process 400 may involve processor 212 initiating a service request procedure for transport of user data via a control plane when apparatus 210 is requested by an upper layer for a CS fallback for an emergency call. Additional Notes
  • any two components so associated can also be viewed as being “operably connected” , or “operably coupled” , to each other to achieve the desired functionality, and any two components capable of being so associated can also be viewed as being “operably couplable” , to each other to achieve the desired functionality.
  • operably couplable include but are not limited to physically mateable and/or physically interacting components and/or wirelessly interactable and/or wirelessly interacting components and/or logically interacting and/or logically interactable components.

Landscapes

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

Abstract

L'invention concerne des techniques se rapportant à la gestion de la régulation de l'encombrement pour le transport de données d'utilisateur par l'intermédiaire d'un plan de commande dans des communications mobiles. Un appareil (par exemple, un équipement utilisateur (UE)) détermine qu'un temporisateur T3448 de réduction de puissance de données de plan de commande est en cours d'exécution. En réponse à la détermination, l'appareil lance toute procédure de mise à jour de mobilité et d'enregistrement périodique avec l'indicateur de demande de suivi réglé sur "demande de suivi en attente" lorsqu'une session d'unité de données de protocole d'urgence (PDU) est établie pour l'appareil.
PCT/CN2025/078705 2024-03-13 2025-02-24 Gestion de régulation de l'encombrement pour le transport de données d'utilisateur par l'intermédiaire d'un plan de commande dans des communications mobiles Pending WO2025190066A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
IN202421018266 2024-03-13
IN202421018266 2024-03-13

Publications (1)

Publication Number Publication Date
WO2025190066A1 true WO2025190066A1 (fr) 2025-09-18

Family

ID=97062783

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2025/078705 Pending WO2025190066A1 (fr) 2024-03-13 2025-02-24 Gestion de régulation de l'encombrement pour le transport de données d'utilisateur par l'intermédiaire d'un plan de commande dans des communications mobiles

Country Status (1)

Country Link
WO (1) WO2025190066A1 (fr)

Similar Documents

Publication Publication Date Title
WO2020078417A1 (fr) Amélioration d'une attribution de guti après l'établissement d'une connexion terminée dans un mobile dans des communications mobiles
EP3958648A1 (fr) Comportement d'équipement utilisateur (ue) en cas d'échec d'une requête d'enregistrement ou d'une demande de service pour la reprise de services d'urgences
US12245328B2 (en) UE behavior for failed registration request or service request for emergency services fallback
WO2025190066A1 (fr) Gestion de régulation de l'encombrement pour le transport de données d'utilisateur par l'intermédiaire d'un plan de commande dans des communications mobiles
WO2025190374A1 (fr) Gestion de régulation de l'encombrement d'apn à la réception d'un message de transport de données esm dans des communications mobiles
WO2025171748A1 (fr) Gestion de début de période d'indisponibilité pendant une procédure d'enregistrement initiale dans des communications mobiles
WO2025237121A1 (fr) Gestion de compteurs de tentatives dans une procédure d'inactivité d'ecall dans des communications mobiles
WO2025020641A1 (fr) Procédés et appareil pour permettre la libération d'une connexion après un message de statut provenant d'un réseau
WO2025232713A1 (fr) Procédés et appareil de réglage d'un indicateur de demande de suivi dans une mru pour une période d'indisponibilité dans des communications mobiles
WO2025055677A1 (fr) Activation d'indisponibilité à l'aide d'une procédure d'enregistrement initiale dans des communications mobiles
WO2025055595A1 (fr) Gestion de collision entre une notification et une période d'indisponibilité dans des communications mobiles
WO2025039818A1 (fr) Procédé de démarrage d'un temporisateur de garde pour une période d'indisponibilité dans des communications sans fil
WO2025082077A1 (fr) Période d'indisponibilité et indication de notification de couverture dans des communications mobiles
WO2025251979A1 (fr) Procédés et appareil de gestion de procédure de repli de services d'urgence et de libération et de connexion de signalisation nas dans un découpage de réseau dans des communications mobiles
WO2025055668A1 (fr) Connexion de signalisation de strate de non-accès et aucune optimisation de service dans des communications mobiles
WO2025171706A1 (fr) Comportement d'équipement utilisateur lors de la réception d'un message de notification pendant une période d'indisponibilité dans des communications mobiles
WO2025161612A1 (fr) Gestion de temporisateur de repli mbs pendant une activation de période d'indisponibilité dans des communications mobiles
WO2025256425A1 (fr) Procédés et appareil de gestion de temporisateur pour plmn avec ng-ran satellite non autorisé durant une optimisation d'économie d'énergie dans des communications mobiles
WO2025209041A1 (fr) Gestion de n3iwf ou de tngf sélectionnée non compatible avec des nssai autorisées dans des communications mobiles non 3gpp
WO2025077515A1 (fr) Traitement de temporisateur de gestion d'encombrement pour le transport de données d'utilisateur par l'intermédiaire d'un plan de contrôle lors de l'existence de conditions
WO2025237173A1 (fr) Procédés et appareil de gestion de services d'urgence et de liste interdite dans des communications mobiles
WO2025214166A1 (fr) Amélioration du comportement de joignabilité d'un équipement utilisateur dans un état de signalisation nas suspendu dans des communications mobiles
WO2025242022A1 (fr) Procédés et appareil de gestion de services priorisés réglementaires dans une zone non autorisée dans des communications mobiles
WO2025228403A1 (fr) Gestion de temporisateur d'inactivité de désenregistrement de tranche et de plmn non autorisés à fonctionner au niveau d'un temporisateur de localisation d'équipement utilisateur présent dans une optimisation d'économie d'énergie dans des communications mobiles
WO2025011238A1 (fr) Comportement d'équipement utilisateur pour sélection de plmn et de rat pendant une signalisation nas suspendue

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

Country of ref document: EP

Kind code of ref document: A1