[go: up one dir, main page]

WO2025011501A1 - Gestion de collision pour dispositif de module d'identité d'abonné universel multiple - Google Patents

Gestion de collision pour dispositif de module d'identité d'abonné universel multiple Download PDF

Info

Publication number
WO2025011501A1
WO2025011501A1 PCT/CN2024/104092 CN2024104092W WO2025011501A1 WO 2025011501 A1 WO2025011501 A1 WO 2025011501A1 CN 2024104092 W CN2024104092 W CN 2024104092W WO 2025011501 A1 WO2025011501 A1 WO 2025011501A1
Authority
WO
WIPO (PCT)
Prior art keywords
occasion
type gap
gap
type
dropped
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/104092
Other languages
English (en)
Inventor
Ogeen Hanna Toma Toma
Tsang-Wei Yu
Hsuan-Li 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 Singapore Pte Ltd
Original Assignee
MediaTek Singapore Pte Ltd
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 filed Critical MediaTek Singapore Pte Ltd
Publication of WO2025011501A1 publication Critical patent/WO2025011501A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports

Definitions

  • the present disclosure is generally related to mobile communications and, more particularly, to collision handling for a multi-universal subscriber identity module (MUSIM) device.
  • MUSIM multi-universal subscriber identity module
  • a user equipment (UE) implementation supports MUSIM (e.g., Subscriber Identity Module (SIM) #1 on network A and SIM #2 on network B)
  • MUSIM Subscriber Identity Module
  • SIM #2 on network B
  • the UE can request MUSIM gap from network A to monitor activities of network B (e.g., paging, measurement, and system information (SI) reading)
  • SI system information
  • the number of colliding gaps is more than two and the colliding gaps comprise a mix of MUSIM gaps and MGs, as there is no proper collision handling mechanism specified in the current 3GPP specifications for such collision, it may lead to unpredictable UE behaviors and could impact the performance in network A and network B. Therefore, there is a need for a solution of collision handling for the foregoing situation in mobile communications.
  • An objective of the present disclosure is to propose solutions or schemes that address the aforementioned issue pertaining to collision handling for a multi-universal subscriber identity module (MUSIM) device.
  • MUSIM multi-universal subscriber identity module
  • a method may involve an apparatus receiving at least one configuration for at least one first-type gap and at least one second-type gap from a network.
  • the method may also involve the apparatus determining a plurality of collisions associated with occasions of the at least one first-type gap and the at least one second-type gap.
  • the method may further involve the apparatus performing a collision handling in an event that a keep solution is granted for certain of the collisions, wherein the collision handling comprises using a priority solution to handle one or more specific collisions among the collisions before using the keep solution to handle one or more remaining collisions among the collision.
  • an apparatus may comprise a transceiver which, during operation, communicates wirelessly.
  • the apparatus may also comprise a processor communicatively coupled to the transceiver.
  • the processor may perform operations comprising receiving, via the transceiver, at least one configuration for at least one first-type gap and at least one second-type gap from a network. Also, the processor may perform operations comprising determining a plurality of collisions associated with occasions of the at least one first-type gap and the at least one second-type gap.
  • the processor may further perform operations comprising performing a collision handling in an event that a keep solution is granted for certain of the collisions, the collision handling comprises using a priority solution to handle one or more specific collisions among the collisions before using the keep solution to handle one or more remaining collisions among the collisions.
  • radio access technologies such as LTE, LTE-Advanced, LTE-Advanced Pro, 5G, NR, 5G-Advanced, Internet-of-Things (IoT) , Narrow Band Internet of Things (NB-IoT) , Industrial Internet of Things (IIoT) , beyond 5G (B5G) , and 6th Generation (6G)
  • IoT Internet-of-Things
  • NB-IoT Narrow Band Internet of Things
  • IIoT Industrial Internet of Things
  • 6G 6th Generation
  • FIG. 1 is a diagram depicting an example scenario of a communication environment in which various solutions and schemes in accordance with the present disclosure may be implemented.
  • FIG. 2 is a diagram depicting example scenarios of collision handling in accordance with an embodiment of the present disclosure.
  • FIG. 3 is a diagram depicting example scenarios of collision handling in accordance with another embodiment of the present disclosure.
  • FIG. 4 is a diagram depicting example scenarios of collision handling in accordance with still another embodiment of the present disclosure.
  • FIG. 5 is a diagram depicting example scenarios of collision handling in accordance with yet another embodiment of the present disclosure.
  • FIG. 6 is a block diagram of an example communication apparatus in accordance with an implementation of the present disclosure.
  • FIG. 7 is a flowchart of an 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 collision handling for a multi-universal subscriber identity module (MUSIM) device.
  • MUSIM multi-universal subscriber identity module
  • 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 scenario 100 of a communication environment in which various solutions and schemes in accordance with the present disclosure may be implemented.
  • Scenario 100 involves a user equipment (UE) 110, a network A comprising a network device 121 and a network B comprising a network device 122.
  • the UE 110 may be a smart phone, a wearable device, an IoT device, and a tablet, etc.
  • the network devices 121 and 122 may be the base stations such as evolved NodeB (eNB) , Next Generation Node B (gNB) and/or transmission/reception point (TRP) .
  • eNB evolved NodeB
  • gNB Next Generation Node B
  • TRP transmission/reception point
  • the UE 110 supports MUSIM, which carries a SIM 111 served by the network devices in the network A (e.g., the network device 121) and a SIM 113 served by the network devices in the network B (e.g., the network device 122) .
  • the UE 110 can request up to four MUSIM gaps from the network A to monitor activities of the network B (e.g., paging, measurement, and system information (SI) reading) .
  • the UE 110 can also request measurement gap (MG) from network A.
  • the MG can be Release 17 (Rel-17) concurrent MG, Pre-MG, or NCSG.
  • the UE 110 may implement various schemes pertaining to collision handling in mobile communications in accordance with the present disclosure. Especially for handling the collision caused by more than two colliding gaps with a mix of gap types.
  • the UE 110 when the UE 110 is configured with gaps having different types (e.g., one or more MUSIM gaps and one or more MGs) , in an event that the occasions of the configured MUSIM gap (s) and MG (s) are colliding and a keep solution is granted for certain of the collisions, the UE 110 first handles the collision (s) which a priority solution is granted for. Then, the UE 110 uses the keep solution to handle the remaining collision (s) .
  • gaps having different types e.g., one or more MUSIM gaps and one or more MGs
  • FIG. 2 is a diagram depicting example scenarios of collision handling in accordance with an embodiment of the present disclosure.
  • the UE 110 receives at least one configuration for two MUSIM gaps and one MG from the network A.
  • the priority level of each of the MUSIM gaps and the MG is different and is configured by the network A.
  • the two MUSIM gap occasions and the MG occasion are colliding.
  • the scenarios 210 to 230 show how the UE 110 perform a collision handling under the proposed scheme.
  • the priority level of the MUSIM gap 211 is higher than that of the MUSIM gap 213, and the priority level of the MUSIM gap 213 is higher than that of the MG 215. Since a keep solution is granted for the collision between the occasion of the MUSIM gap 211 and the occasion of the MUSIM gap 213, the UE 110 first uses a priority solution for a collision associated with the occasion of the MG 215 to determine a non-dropped occasion.
  • the UE 110 determines the occasion of the MUSIM gap 213 as the non-dropped occasion (i.e., the occasion of the MUSIM gap 213 is kept and the occasion of the MG 215 is dropped) . Then, the UE 110 uses the keep solution for the collision between the occasion of the MUSIM gap 211 and the occasion of the MUSIM gap 213, resulting in keeping the occasion of the MUSIM gap 211 and the occasion of the MUSIM gap 213.
  • the UE 110 first uses a priority solution for a collision associated with the occasion of the MG 223 to determine a non-dropped occasion. As the priority level of the MG 223 is higher than that of the MUSIM gap 225, the UE 110 determines the occasion of the MG 223 as the non-dropped occasion (i.e., the occasion of the MG 223 is kept and the occasion of the MUSIM gap 225 is dropped) .
  • the UE 110 determines the occasion of the MUSIM gap 211 as another non-dropped occasion, resulting in keeping the occasion of the MUSIM gap 211 and the occasion of the MG 223.
  • the UE 110 since a keep solution is granted for the collision between the occasion of the MUSIM gap 233 and the occasion of the MUSIM gap 235, the UE 110 first uses a priority solution for a collision associated with the occasion of the MG 231 for determining a non-dropped occasion. As the priority level of the MG 231 is higher than that of the MUSIM gap 233, the UE 110 determines the occasion of the MG 231 as the non-dropped occasion (i.e., the occasion of the MG 231 is kept and the occasion of the MUSIM gap 233 is dropped) .
  • the UE 110 determines the occasion of the MUSIM gap 235 as another non-dropped occasion, resulting in keeping the occasion of the MG 231 and the occasion of the MUSIM gap 235.
  • FIG. 3 is a diagram depicting example scenarios of collision handling in accordance with another embodiment of the present disclosure.
  • the UE 110 receives at least one configuration for two MUSIM gaps and one MG from the network A.
  • the two MUSIM gap occasions and the MG occasion are colliding.
  • the scenarios 310 to 330 show how the UE 110 perform a collision handling under the proposed scheme.
  • the UE 110 handles all collisions sequentially in order of decreasing priority and starting from a gap with a highest priority level regardless of the type of gap involved in the collision.
  • the occasion of the MUSIM gap 313 colliding with the occasion of the MUSIM gap 311 is dropped. Then, the non-dropped MUSIM gap 311 is compared with the remaining MG 315. The UE 110 determines that the occasion of the MG 315 as another non-dropped occasion since it is not colliding with the occasion of the MUSIM 311.
  • the occasion of the MUSIM gap 325 colliding with the occasion of the MUSIM gap 321 is dropped.
  • the non-dropped MUSIM gap 321 is compared with the remaining MG 323.
  • the UE 110 determines that the occasion of the MG 323 as another non-dropped occasion since it is not colliding with the occasion of the MUSIM 321.
  • scenario 330 as the MG 331 has the highest priority level, the occasion of the MUSIM gap 333 colliding with the occasion of the MG 331 is dropped. Then, the non-dropped MG 331 is compared with the remaining MUSIM gap 335. As the occasion of the MUSIM gap 335 is colliding with the occasion of the MG 331, the UE 110 drops the occasion of the MUSIM gap 335, resulting in only keeping the occasion of the MG 331.
  • FIG. 4 is a diagram depicting example scenarios of collision handling in accordance with still another embodiment of the present disclosure.
  • the UE 110 receives at lease one configuration for two MUSIM gaps 411 and 417 and two MGs 413 and 415 from the network A.
  • the priority level of each of the MUSIM gaps and the MGs is different and is configured by the network A.
  • the keep solution is granted for the collision between the occasion of the MUSIM gap 411 and the occasion of the MUSIM gap 417.
  • the UE 110 first uses the priority solution for the collision between the occasion of the MG 413, the occasion of the MG 415, and the occasion of the MUSIM gap 417.
  • the occasion of the MG 415 is dropped, and the occasion of the MG 413 and the occasion of the MUSIM gap 417 is kept.
  • the UE 110 then use the keep solution for the collision between the occasion of the MUSIM gap 411 and the occasion of the MUSIM gap 417, resulting in keeping the occasion of the MUSIM gap 411, the occasion of the MUSIM gap 417, and the occasion of the MG 413.
  • the keep solution will be applied between the occasions of the MUSIM gaps only after resolving other collisions based on priority solution.
  • the example of other collisions could be between the occasion of the MUSIM gap and the occasion of the MG, or even between the occasion of the MG and the occasion of the MG.
  • the priority solution is granted for the collision between the occasion of the MUSIM gap 411 and the occasion of the MUSIM gap 417.
  • all collisions are handled sequentially in order of decreasing priority and starting from the MUSIM gap 411 with the highest priority level.
  • the occasion of the MUSIM gap 417 colliding with the occasion of the MUSIM gap 411 is dropped.
  • the occasion of the MG 413 with the second highest priority level is kept as it is not colliding with the occasion of the MUSIM gap 411.
  • the occasion of the MG 415 colliding with the occasion of the MG 413 is dropped.
  • the UE 110 keep the occasion of the MUSIM gap 411 and the occasion of the MG 413 in this embodiment.
  • the MG can be a Rel-17 concurrent MG with priority level configured via GapConfig-r17.
  • the MG may also be a Pre-MG with priority level configured via preConfigInd-r17, or a Network Controlled Small Gap (NCSG) with priority level configured via ncsgInd-r17.
  • NCSG Network Controlled Small Gap
  • the UE 110 may be configured with the gap (s) with no priority level.
  • the UE 110 can handle the collision between the occasion of a MUSIM gap and the occasion of a gap without priority level based on the measurement gap repetition period (MGRP) of the colliding gaps.
  • the UE 110 receives at least one configuration for MUSIM gaps 511 and 513, and MGs 522, 524, 526 and 528.
  • the MUSIM gaps 511 and 513 are configured via MUSIM-GapConfig-r17.
  • the MGs 522, 524, 526 and 528 are configured via GapConfig or configured via GapConfig-r17 without assigned priority level.
  • the MGs 522, 524, 526 and 528 may be Release 15 (Rel-15) and Release 16 (Rel-16) MG. Since shorter MGRP gap has more opportunities (occasions) than the larger MGRP gap, the collided gap which has larger MGRP should be kept and the one with shorter MGRP can be dropped. For example, the occasion of the MUSIM gap 511 and the occasion of the MG 522 are colliding. Under a proposed scheme, the UE 110 keeps the occasion of the MUSIM gap 511 as the MGPR_MUSIM is longer than the MGPR_MG. The collision between the occasion of the MUSIM gap 513 and the occasion of the MG 528 can be handled in a similar way.
  • FIG. 6 illustrates an example communication apparatus 610 in accordance with an implementation of the present disclosure.
  • the communication apparatus 610 may perform various functions to implement schemes, techniques, processes and methods described herein pertaining to collision handling for a MUSIM device in mobile communications, including scenarios/schemes described above as well as process 700 described below.
  • Communication apparatus 610 may be a part of an electronic apparatus, which may be a UE such as a portable or mobile apparatus, a wearable apparatus, a wireless communication apparatus or a computing apparatus.
  • communication apparatus 610 may be implemented in a smartphone, a smartwatch, a personal digital assistant, a digital camera, or a computing equipment such as a tablet computer, a laptop computer or a notebook computer.
  • Communication apparatus 610 may also be a part of a machine type apparatus, which may be an IoT, NB-IoT, or IIoT apparatus such as an immobile or a stationary apparatus, a home apparatus, a wire communication apparatus or a computing apparatus.
  • communication apparatus 610 may be implemented in a smart thermostat, a smart fridge, a smart door lock, a wireless speaker or a home control center.
  • communication apparatus 610 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 reduced-instruction set computing (RISC) processors, or one or more complex-instruction-set-computing (CISC) processors.
  • IC integrated-circuit
  • RISC reduced-instruction set computing
  • CISC complex-instruction-set-computing
  • Communication apparatus 610 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 communication apparatus 610 are neither shown in FIG. 6 nor described below in the interest of simplicity and brevity.
  • other components e.g., internal power supply, display device and/or user interface device
  • processor 612 may be implemented in the form of one or more single-core processors, one or more multi-core processors, or one or more CISC processors. That is, even though a singular term “a processor” is used herein to refer to processor 612, processor 612 may include multiple processors in some implementations and a single processor in other implementations in accordance with the present disclosure.
  • processor 612 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.
  • processor 612 is a special-purpose machine specifically designed, arranged and configured to perform at least a part of the specific tasks including collision handling in a UE (e.g., as represented by communication apparatus 610) in accordance with various implementations of the present disclosure.
  • communication apparatus 610 may also include a transceiver 616 coupled to processor 612 and capable of wirelessly transmitting and receiving data.
  • transceiver 616 may be capable of wirelessly communicating with different types of wireless networks of different radio access technologies (RATs) .
  • RATs radio access technologies
  • transceiver 616 may be equipped with a plurality of antenna ports (not shown) such as, for example, four antenna ports. That is, transceiver 616 may be equipped with multiple transmit antennas and multiple receive antennas for multiple-input multiple-output (MIMO) wireless communications.
  • MIMO multiple-input multiple-output
  • communication apparatus 610 may further include a memory 614 coupled to processor 612 and capable of being accessed by processor 612 and storing data therein.
  • Memory 614 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
  • SRAM static RAM
  • T-RAM thyristor RAM
  • Z-RAM zero-capacitor RAM
  • memory 614 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
  • memory 614 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
  • flash memory solid-state memory
  • FeRAM ferroelectric RAM
  • MRAM magnetoresistive RAM
  • phase-change memory phase-change memory
  • Communication apparatus 610 may be a communication entity capable of using various proposed schemes in accordance with the present disclosure. For illustrative purposes and without limitation, descriptions of capabilities of communication apparatus 610, implemented in or as a UE are provided below with process 700.
  • FIG. 7 illustrates an example process 700 in accordance with an implementation of the present disclosure.
  • Process 700 may be an example implementation of above scenarios/schemes, whether partially or completely, with respect to collision handling for a MUSIM device in mobile communications.
  • Process 700 may represent an aspect of implementation of features of communication apparatus 610.
  • Process 700 may include one or more operations, actions, or functions as illustrated by one or more of blocks 710, 720, and 730. Although illustrated as discrete blocks, various blocks of process 700 may be divided into additional blocks, combined into fewer blocks, or eliminated, depending on the desired implementation. Moreover, the blocks of process 700 may be executed in the order shown in FIG. 7 or, alternatively, in a different order.
  • Process 700 may be implemented by communication apparatus 610 or any suitable UE or machine type devices. Solely for illustrative purposes and without limitation, process 700 is described below in the context of communication apparatus 610 as a UE. Process 700 may begin at block 710.
  • process 700 may involve processor 612 of communication apparatus 610 receiving at least one configuration for at least one first-type gap and at least one second-type gap from a network (e.g., the network A) .
  • Process 700 may proceed from 710 to 720.
  • process 700 may involve processor 612 determining a plurality of collisions associated with occasions of the at least one first-type gap and the at least one second-type gap.
  • Process 600 may proceed from 720 to 730.
  • process 700 may involve processor 612 performing a collision handling in an event that a keep solution is granted for certain of the collisions, comprising using a priority solution to handle one or more specific collisions among the collisions before using the keep solution to handle one or more remaining collisions among the collisions.
  • the at least one first-type gap comprises a first first-type gap and a second first-type gap
  • the at least one second-type gap comprises a first second-type gap
  • process 700 may further involve processor 612 using a priority solution for a collision associated with the occasion of the first second-type gap to determine a first non-dropped occasion (e.g., the occasion of the MUSIM gap 213 in scenario 210, the occasion of the MG 223 in scenario 220, the occasion of the MG 231 in scenario 230) in an event that a keep solution is granted for a collision between the occasion of the first first-type gap and the occasion of the second first-type gap, and using the keep solution for the collision between the occasion of the first-type gap and the occasion of the second first-type gap in an event that the first non-dropped occasion is that of either the first first-type gap or the second first-type gap.
  • a first non-dropped occasion e.g., the occasion of the MUSIM gap 213 in scenario 210, the occasion of
  • process 700 may further involve processor 612 determining one specific occasion among the occasion of the first first-type gap and the occasion of the second first-type gap that is not colliding with the occasion of the first second-type gap as a second non-dropped occasion (e.g., the occasion of the MUSIM gap 221 in scenario 220, the occasion of the MUSIM gap 235 in scenario 230) in an event that the first non-dropped occasion is that of the first second-type gap.
  • a second non-dropped occasion e.g., the occasion of the MUSIM gap 221 in scenario 220, the occasion of the MUSIM gap 235 in scenario 230
  • the collision associated with the occasion of the first second-type gap is also associated with a specific first-type gap.
  • Process 700 may further involve processor 612 determining that the first non-dropped occasion is that of the first second- type gap in an event that the first second-type gap has a higher priority than that of the specific first-type gap. Additionally, process 700 may further involve processor 612 determining that the first non-dropped occasion is that of the specific first-type gap in an event that the specific first-type gap has a higher priority than that of the first second-type gap.
  • process 700 may further involve processor 612 handling all collisions sequentially in order of decreasing priority and starting from a gap with a highest priority level in an event that the priority solution is granted for the collision between the occasion of the first first-type gap and the occasion of the second first-type gap.
  • the handling is, for example, performed regardless of a gap type (in an event that the priority solution is granted for the collision between the occasion of the first first-type gap and the occasion of the second first-type gap) .
  • process 700 may further involve processor 612 comparing a gap associated with a third non-dropped occasion (e.g., the occasion of the MUSIM gap 311 in scenario 310, the occasion of the MUSIM gap 321 in scenario 320, the occasion of MG 331 in scenario 330) with a remaining gap (e.g., the MG 315 in scenario 310, the MG 323 in scenario 320, the MUSIM gap 335 in scenario 330) . Additionally, process 700 may further involve processor 612 determining that an occasion of the remaining gap as a fourth non-dropped occasion in an event that the third non-dropped occasion and the occasion of the remaining gap are not colliding. Moreover, process 700 may further involve processor 612 dropping the occasion of the remaining gap in an event that the third non-dropped occasion and the occasion of the remaining gap are colliding.
  • a gap associated with a third non-dropped occasion e.g., the occasion of the MUSIM gap 311 in scenario 310, the occasion of the MUSIM gap 321 in
  • each of the at least one first-type gap comprises a multiple-universal subscriber identity modules (MUSIM) gap
  • each of the at least one second-type gap comprises a measurement gap (MG) .
  • MUSIM multiple-universal subscriber identity modules
  • MG measurement gap
  • a priority level of each of the at least one first-type gap and the at least one second-type gap is configured by the network.
  • process 700 may further involve processor 612 receiving at least one configuration of a third first-type gap and a first third-type gap from the network, wherein the first third-type gap is configured without priority level. Moreover, process 700 may further involve processor 612 handling a collision between an occasion of the third first-type gap and an occasion of the first third-type gap based on a first MGRP associated with the third first-type gap (e.g., MGPR_MUSIM in scenario 510) and a second MGRP associated with the first third-type gap (e.g., MGPR_MG in scenario 510) .
  • a first MGRP associated with the third first-type gap e.g., MGPR_MUSIM in scenario 510
  • a second MGRP associated with the first third-type gap e.g., MGPR_MG in scenario 510 .
  • 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 diverses solutions de gestion de collision d'un dispositif de module d'identité d'abonné universel multiple (MUSIM). Un appareil peut recevoir au moins une configuration d'au moins un intervalle de premier type et d'au moins un intervalle de second type émanant d'un réseau. L'appareil peut déterminer une pluralité de collisions associées à des occasions du ou des intervalles de premier type et du ou des intervalles de second type. L'appareil peut effectuer une gestion de collision dans un cas dans lequel une solution de maintien est accordée pour certaines des collisions, la gestion de collisions comprenant l'utilisation d'une solution de priorité pour gérer une ou plusieurs collisions spécifiques parmi les collisions avant utilisation de la solution de maintien pour gérer une ou plusieurs collisions restantes parmi les collisions.
PCT/CN2024/104092 2023-07-07 2024-07-05 Gestion de collision pour dispositif de module d'identité d'abonné universel multiple Pending WO2025011501A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US202363512306P 2023-07-07 2023-07-07
US63/512,306 2023-07-07
US202363512668P 2023-07-10 2023-07-10
US63/512,668 2023-07-10

Publications (1)

Publication Number Publication Date
WO2025011501A1 true WO2025011501A1 (fr) 2025-01-16

Family

ID=94214650

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2024/104092 Pending WO2025011501A1 (fr) 2023-07-07 2024-07-05 Gestion de collision pour dispositif de module d'identité d'abonné universel multiple

Country Status (1)

Country Link
WO (1) WO2025011501A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4539533A1 (fr) * 2023-10-09 2025-04-16 Nokia Technologies Oy Collision d'intervalle de mesure avec gestion de maintien

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017028046A1 (fr) * 2015-08-14 2017-02-23 华为技术有限公司 Procédé et appareil pour sélectionner un intervalle
CN112106399A (zh) * 2018-05-11 2020-12-18 上海诺基亚贝尔股份有限公司 用于确定测量间隙的方法、设备和计算机可读介质
CN115379472A (zh) * 2021-05-18 2022-11-22 维沃移动通信有限公司 测量间隙的确定方法、终端及网络侧设备
CN115443677A (zh) * 2021-04-01 2022-12-06 苹果公司 Ue的多个测量间隙的配置
WO2023076763A1 (fr) * 2021-10-29 2023-05-04 Qualcomm Incorporated Considérations concernant de multiples intervalles de mesure configurés avec différents mécanismes de signalisation

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017028046A1 (fr) * 2015-08-14 2017-02-23 华为技术有限公司 Procédé et appareil pour sélectionner un intervalle
CN112106399A (zh) * 2018-05-11 2020-12-18 上海诺基亚贝尔股份有限公司 用于确定测量间隙的方法、设备和计算机可读介质
CN115443677A (zh) * 2021-04-01 2022-12-06 苹果公司 Ue的多个测量间隙的配置
CN115379472A (zh) * 2021-05-18 2022-11-22 维沃移动通信有限公司 测量间隙的确定方法、终端及网络侧设备
WO2023076763A1 (fr) * 2021-10-29 2023-05-04 Qualcomm Incorporated Considérations concernant de multiples intervalles de mesure configurés avec différents mécanismes de signalisation

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4539533A1 (fr) * 2023-10-09 2025-04-16 Nokia Technologies Oy Collision d'intervalle de mesure avec gestion de maintien

Similar Documents

Publication Publication Date Title
US12063685B2 (en) Floating frame-based channel occupancy time in fixed frame period in mobile communications
US10911300B2 (en) Optimization for device provisioning protocol onboarding in wireless networks
US20230300723A1 (en) Identifying Support Of Reduced Capability In Mobile Communications
US11368343B2 (en) Reserving channel by cyclic prefix extension for alignment with symbol boundary in mobile communications
WO2025011501A1 (fr) Gestion de collision pour dispositif de module d'identité d'abonné universel multiple
US20230345534A1 (en) Transmission Protection With Static Puncturing In Wireless Communications
US20250240138A1 (en) Method And Apparatus For Supporting Enhanced Bandwidth Part (BWP) Operation For Reduced Capability (RedCap) User Equipment (UE)
US11570812B2 (en) Conditions on listen-before-talk impact on mac counters in mobile communications
US10917838B2 (en) Handling of PLMN-specific attempt counter in mobile communications
US11457353B2 (en) Indication of additional security capabilities using NAS signaling in 5G mobile communications
US20240314824A1 (en) Selective BWP Interruptions for L1 Measurements
EP4418709A1 (fr) Gestion de collision entre des intervalles musim et un intervalle de mesure de type 1 dans des communications mobiles
WO2025020937A1 (fr) Procédé et appareil de commutation de transmission de liaison montante à porteuses multiples
US20240048960A1 (en) Handling Of MUSIM Gaps Collision In Mobile Communications
WO2025161774A1 (fr) Procédé et appareil de transmission de bloc de signal de synchronisation dans des communications mobiles
US20250113211A1 (en) Methods And Apparatus For Response Of Beam Reporting In Mobile Communications
WO2025051265A1 (fr) Procédé et appareil de conception à faible complexité d'une transmission mimo de rang élevé distribuée dans des communications mobiles
WO2025007876A1 (fr) Formation de faisceau coordonnée à multiples points d'accès dans des communications sans fil
WO2025050887A1 (fr) Procédés et appareil de gestion de snpn équivalent pour des services localisés
EP4429341A1 (fr) Comportement d'ue pour collision de services de désenregistrement et d'urgence initiés par réseau
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
WO2023207766A1 (fr) Améliorations supplémentaires dans une opération drx pour un jeu xr et en nuage 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
US12452922B2 (en) Special dual CTS mode for improvement in collision avoidance
WO2025036080A1 (fr) Procédé et appareil de transmission de signal de référence de sondage pour une mesure d'interférence de liaison croisée d'équipement utilisateur 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: 24838754

Country of ref document: EP

Kind code of ref document: A1