[go: up one dir, main page]

WO2025055595A1 - Gestion de collision entre une notification et une période d'indisponibilité dans des communications mobiles - Google Patents

Gestion de collision entre une notification et une période d'indisponibilité dans des communications mobiles Download PDF

Info

Publication number
WO2025055595A1
WO2025055595A1 PCT/CN2024/109695 CN2024109695W WO2025055595A1 WO 2025055595 A1 WO2025055595 A1 WO 2025055595A1 CN 2024109695 W CN2024109695 W CN 2024109695W WO 2025055595 A1 WO2025055595 A1 WO 2025055595A1
Authority
WO
WIPO (PCT)
Prior art keywords
unavailability period
processor
3gpp access
condition comprises
over
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/CN2024/109695
Other languages
English (en)
Inventor
Puneet PUNEET
Marko NIEMI
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 Singapore Pte Ltd
MediaTek Inc
Original Assignee
MediaTek Singapore Pte Ltd
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 Singapore Pte Ltd, MediaTek Inc filed Critical MediaTek Singapore Pte Ltd
Publication of WO2025055595A1 publication Critical patent/WO2025055595A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/28—Discontinuous transmission [DTX]; Discontinuous reception [DRX]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0212—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is leader and terminal is follower
    • H04W52/0216—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is leader and terminal is follower using a pre-established activity schedule, e.g. traffic indication frame

Definitions

  • the present disclosure is generally related to mobile communications and, more particularly, to handling collision between a notification and an unavailability period in mobile communications.
  • a notification procedure may be used by a network to request a user equipment (UE) (e.g., by sending a NOTIFICATION message over a 3GPP access) to re-establish the user-plane resources of protocol data unit (PDU) session (s) associated with a non-3GPP access over the 3GPP access or to deliver 5 th Generation Session Management (5GSM) downlink signaling messages associated with the non-3GPP access over the 3GPP access when the UE is in a 5GMM-IDLE mode over the non-3GPP access and in a 5GMM-CONNECTED mode over the 3GPP access.
  • UE user equipment
  • PDU protocol data unit
  • 5GSM 5 th Generation Session Management
  • the network may use the notification procedure to request the UE (e.g., by sending the NOTIFICATION message over the non-3GPP access) to re-establish user-plane resources of the PDU session (s) or to deliver downlink signaling associated with the 3GPP access over the 3GPP access when the UE is in the 5GMM-CONNECTED mode over the non-3GPP access and either in the 5GMM-IDLE mode over the 3GPP access when the UE is not in a mobile-initiated connection-only (MICO) mode or in the 5GMM-IDLE mode with suspend indication over the 3GPP access when the UE is not in the MICO mode.
  • MICO mobile-initiated connection-only
  • 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 collision between a notification and an unavailability period 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 network determining a status of an unavailability period with respect to a UE. The method may also involve the network refraining from sending a notification message to the UE responsive to determining that a condition exists regarding the unavailability period or the UE.
  • an apparatus may include a transceiver configured to communicate wirelessly and a processor coupled to the transceiver.
  • the processor may determine a status of an unavailability period with respect to a UE.
  • the processor may also refrain from sending a notification message to the UE responsive to determining that a condition exists regarding the unavailability period or the UE.
  • 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 in accordance with an implementation of the present disclosure.
  • FIG. 3 is a flowchart of a second example process in accordance with an implementation of the present disclosure.
  • Implementations in accordance with the present disclosure relate to various techniques, methods, schemes and/or solutions pertaining to handling collision between a notification and an unavailability period 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. 3 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. 3.
  • 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 a PLMN including 5G/NR domain and 4G/LTE domain.
  • 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 collision between a notification and an unavailability period 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
  • an Access &Mobility Management Function (AMF) of wireless network 120 may not send any notification message to UE 110.
  • Such one or more conditions may include: (1) an unavailability period is activated due to a discontinuous coverage; and/or (2) the unavailability period is activated due to one or more other reasons (e.g., an upper layer of UE 110 triggering an event to render UE 110 unavailable) ; and/or (3) an access stratum (AS) is deactivated due to the discontinuous coverage; and/or (4) UE 110 is about to activate the unavailability period.
  • a notification procedure may be used by wireless network 120 to request UE 110 (e.g., by sending a NOTIFICATION message over a non-3GPP access) to re-establish user-plane resources of one or more PDU sessions or to deliver downlink (DL) signaling associated with a 3GPP access over the 3GPP access when UE 110 is in a 5GMM-CONNECTED mode over the non-3GPP access while the unavailability period is not activated over the 3GPP access in UE 110.
  • DL downlink
  • 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 collision between a notification and an unavailability period 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 “aprocessor” 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 collision between a notification and an unavailability period 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 process 300.
  • 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 collision between a notification and an unavailability period 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 222 of apparatus 220 determining a status of an unavailability period with respect to a UE (e.g., apparatus 210) .
  • Process 300 may proceed from 310 to 320.
  • process 300 may involve processor 222 refraining from sending a notification message to the UE responsive to determining that a condition exists regarding the unavailability period or the UE.
  • the condition may involve an unavailability period being activated due to a discontinuous coverage.
  • the condition may involve an unavailability period being activated due to one or more reasons other than a discontinuous coverage.
  • the condition may involve an upper layer triggering an event that renders the UE unavailable.
  • condition may involve an AS being deactivated due to a discontinuous coverage.
  • the condition may involve the unavailability period being about to be activated by the UE.
  • process 300 may involve processor 222 performing additional operations. For instance, process 300 may involve processor 222 determining that the unavailability period is not activated over a 3GPP access in the UE. Moreover, process 300 may involve processor 222 requesting the UE to re-establish user-plane resources of one or more PDU sessions or to deliver DL signaling associated with the 3GPP access over the 3GPP access responsive to the UE being in a 5GMM-CONNECTED mode over a non-3GPP access. For instance, in requesting, process 300 may involve processor 222 sending a NOTIFICATION message to the UE over the non-3GPP access.
  • 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 d'une collision entre une notification et une période d'indisponibilité dans des communications mobiles. Un appareil (par exemple, un nœud de réseau d'un réseau sans fil) détermine un état d'une période d'indisponibilité par rapport à un équipement utilisateur (UE). L'appareil s'abstient alors d'envoyer un message de notification à l'UE après avoir déterminé qu'il existe une condition concernant la période d'indisponibilité ou l'UE.
PCT/CN2024/109695 2023-09-11 2024-08-05 Gestion de collision entre une notification et une période d'indisponibilité dans des communications mobiles Pending WO2025055595A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
IN202321061058 2023-09-11
IN202321061058 2023-09-11

Publications (1)

Publication Number Publication Date
WO2025055595A1 true WO2025055595A1 (fr) 2025-03-20

Family

ID=95020904

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2024/109695 Pending WO2025055595A1 (fr) 2023-09-11 2024-08-05 Gestion de collision entre une notification et une période d'indisponibilité dans des communications mobiles

Country Status (1)

Country Link
WO (1) WO2025055595A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102378195A (zh) * 2010-08-23 2012-03-14 中国移动通信集团公司 一种终端共存干扰的抑制方法和设备
US20190174458A1 (en) * 2016-07-21 2019-06-06 Huawei Technologies Co., Ltd. Communication method, network device, and terminal device
US20190379792A1 (en) * 2018-06-11 2019-12-12 T-Mobile Usa, Inc. Automated unavailability response for call handling
US20220338161A1 (en) * 2020-01-20 2022-10-20 Vivo Mobile Communication Co., Ltd. Message notification method, terminal, and network device

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102378195A (zh) * 2010-08-23 2012-03-14 中国移动通信集团公司 一种终端共存干扰的抑制方法和设备
US20190174458A1 (en) * 2016-07-21 2019-06-06 Huawei Technologies Co., Ltd. Communication method, network device, and terminal device
US20190379792A1 (en) * 2018-06-11 2019-12-12 T-Mobile Usa, Inc. Automated unavailability response for call handling
US20220338161A1 (en) * 2020-01-20 2022-10-20 Vivo Mobile Communication Co., Ltd. Message notification method, terminal, and network device

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
LG ELECTRONICS: "Evaluation", 3GPP DRAFT; S2-2204007, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. e-meeting ;20220516 - 20220520, 6 May 2022 (2022-05-06), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052159512 *

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
WO2022028263A1 (fr) Identification de la prise en charge d'une capacité réduite 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
CN113301630B (zh) 关于移动通信中通知之后的用户设备可达性的方法及装置
US20240014886A1 (en) Signaling Over Satellite Access In Mobile Communications
WO2025055595A1 (fr) Gestion de collision entre une notification et une période d'indisponibilité 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
US12245328B2 (en) UE behavior for failed registration request or service request for emergency services fallback
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
WO2025039818A1 (fr) Procédé de démarrage d'un temporisateur de garde pour une période d'indisponibilité dans des communications sans fil
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
WO2025055677A1 (fr) Activation d'indisponibilité à l'aide d'une procédure d'enregistrement initiale dans des communications mobiles
WO2025055668A1 (fr) Connexion de signalisation de strate de non-accès et aucune optimisation de service dans des communications mobiles
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
WO2025011238A1 (fr) Comportement d'équipement utilisateur pour sélection de plmn et de rat pendant une signalisation nas suspendue
WO2025082077A1 (fr) Période d'indisponibilité et indication de notification de couverture 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
WO2025050887A1 (fr) Procédés et appareil de gestion de snpn équivalent pour des services localisés
WO2025237173A1 (fr) Procédés et appareil de gestion de services d'urgence et de liste interdite 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
WO2025214166A1 (fr) Amélioration du comportement de joignabilité d'un équipement utilisateur dans un état de signalisation nas suspendu dans des communications mobiles
WO2025011278A1 (fr) Procédés et appareil d'évitement de sélection et de resélection de cellule lorsqu'une période d'indisponibilité est activée
WO2025161612A1 (fr) Gestion de temporisateur de repli mbs pendant une activation de période d'indisponibilité dans des communications mobiles
WO2025237121A1 (fr) Gestion de compteurs de tentatives dans une procédure d'inactivité d'ecall dans des communications mobiles

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

Country of ref document: EP

Kind code of ref document: A1