Methods, equipment, and systems for coordinating departure processes

Abstract

This disclosure describes methods, systems, and apparatus for configuring signal resources for a coordinated departure process, the departure process being used by one or more devices including multiple Subscriber Identity Modules (Multi-SIMs) or by one or more devices connected to multiple networks using a single Subscriber Identity Module (SIM). One method includes configuring a departure process for multiple networks by a User Equipment (UE) in such a way that: the UE determines a departure type in response to a specific scenario; and the UE coordinates the departure process based on at least one of the departure type or the specific scenario.

Description

Technical Field

[0001] This disclosure generally relates to wireless communications. Specifically, this disclosure relates to methods, apparatus, and systems for coordinating the departure process of one or more devices including multiple Subscriber Identity Modules (Multi-SIMs) or one or more devices connected to multiple networks using a single Subscriber Identity Module (SIM). Background Technology

[0002] Wireless communication technology is driving the world towards an increasingly interconnected and networked society. High-speed and low-latency wireless communication relies on efficient network resource management and allocation between user equipment and wireless access network nodes (including but not limited to base stations). Next-generation networks promise to provide high-speed, low-latency, and ultra-reliable communication capabilities, meeting the requirements of various industries and users.

[0003] For fifth-generation mobile communication technology, user equipment (UE) (e.g., smartphone) may have multiple subscriber identity modules (Multi-SIM). The UE can register with and connect to more than one network node, such as more than one radio access network (RAN) node and / or more than one core network (CN) node. The UE can connect to a first network. When the UE needs to connect to a second network, the UE needs to configure and / or coordinate the departure procedure for both the first and second networks to provide an efficient system for various scenarios. However, the details of the departure procedure and the configuration / coordination of the departure procedure between the UE and more than one network remain unclear, hindering efficient wireless communication systems.

[0004] This disclosure can solve at least some of the problems / difficulties associated with existing systems and describes various embodiments for departure processes and their configuration / coordination, thereby improving the performance of wireless communication. Summary of the Invention

[0005] This document relates to methods, systems, and apparatuses for wireless communication, and more specifically to methods, systems, and apparatuses for coordinating the departure process of one or more devices comprising multiple Subscriber Identity Modules (Multi-SIMs) or one or more devices connected to multiple networks using a single Subscriber Identity Module (SIM). For one or more devices connected to multiple networks using a single Subscriber Identity Module (SIM), it includes at least two scenarios: for a roaming UE, it can connect to multiple networks in different slices, which also requires coordination between the UE and multiple networks; and for specialized applications such as Video, Imaging, and Audio (VIAPA), it may be necessary to investigate means that enable the UE to receive data services from one network and simultaneously receive paging and data services from another network, which also requires coordination between the UE and multiple networks.

[0006] In one embodiment, this disclosure describes a method for wireless communication. The method includes configuring a departure process for multiple networks by a user equipment (UE) by: determining a departure type by the UE in response to a specific scenario; and coordinating the departure process by the UE based on at least one of the departure type or the specific scenario.

[0007] In another embodiment, this disclosure describes a method for wireless communication. The method includes: receiving a transition notification indicating a departure type or scenario by a radio access network (RAN) node; determining a transition configuration for the departure type or scenario by the RAN node; and sending a transition response by the RAN node to a user equipment (UE).

[0008] In another embodiment, this disclosure describes a method for wireless communication. The method includes: receiving information indicating a simple procedure by a RAN node; and the RAN node, upon receiving the information, avoiding triggering a specific procedure.

[0009] In some other embodiments, an apparatus for wireless communication may include a memory storing instructions and a processing circuitry system communicating with the memory. When the processing circuitry system executes the instructions, the processing circuitry system is configured to perform the methods described above.

[0010] In some other embodiments, a device for wireless communication may include a memory storing instructions and a processing circuitry system communicating with the memory. When the processing circuitry system executes the instructions, the processing circuitry system is configured to perform the methods described above.

[0011] In some other embodiments, a computer-readable medium includes instructions that, when executed by a computer, cause the computer to perform the methods described above.

[0012] The above and other aspects, and their implementations, are described in more detail in the drawings, description and claims. Attached Figure Description

[0013] Figure 1 An example of a wireless communication system including more than one network node and one or more user devices is shown.

[0014] Figure 2 An example of a network node is shown.

[0015] Figure 3 An example of a user device is shown.

[0016] Figure 4 A flowchart of a method for wireless communication is shown.

[0017] Figure 5A flowchart of a method for wireless communication is shown.

[0018] Figure 6 A flowchart of a method for wireless communication is shown.

[0019] Figure 7 A schematic diagram of an exemplary embodiment for wireless communication is shown.

[0020] Figure 8 A schematic diagram of an exemplary embodiment for wireless communication is shown.

[0021] Figure 9 A schematic diagram of an exemplary embodiment for wireless communication is shown.

[0022] Figure 10 A schematic diagram of an exemplary embodiment for wireless communication is shown.

[0023] Figure 11 A schematic diagram of an exemplary embodiment for wireless communication is shown.

[0024] Figure 12 A schematic diagram of an exemplary embodiment for wireless communication is shown.

[0025] Figure 13 A schematic diagram of an exemplary embodiment for wireless communication is shown.

[0026] Figure 14 A schematic diagram of an exemplary embodiment for wireless communication is shown.

[0027] Figure 15 A schematic diagram of an exemplary embodiment for wireless communication is shown.

[0028] Figure 16 A schematic diagram of an exemplary embodiment for wireless communication is shown.

[0029] Figure 17 A schematic diagram of an exemplary embodiment for wireless communication is shown.

[0030] Figure 18 A schematic diagram of an exemplary embodiment for wireless communication is shown. Detailed Implementation

[0031] The present disclosure will now be described in detail below with reference to the accompanying drawings, which form part of the disclosure and illustrate specific examples of embodiments by way of illustration. However, it should be noted that the present disclosure may be embodied in various different forms, and therefore, the subject matter covered or claimed is intended to be construed as not being limited to any of the embodiments set forth below.

[0032] Throughout the specification and claims, terms may have a meaning implied or implicit in the context, rather than an explicitly stated meaning. Similarly, the phrases “in one embodiment” or “in some embodiments” as used herein do not necessarily refer to the same embodiment, and the phrases “in another embodiment” or “in other embodiments” as used herein do not necessarily refer to different embodiments. The phrases “in one implementation” or “in some implementations” as used herein do not necessarily refer to the same implementation, and the phrases “in another implementation” or “in other implementations” as used herein do not necessarily refer to different implementations. For example, the claimed subject matter includes combinations of all or part of exemplary embodiments or implementations.

[0033] Generally, terms can be understood, at least in part, from their usage in the context. For example, terms used herein, such as “and,” “or,” or “and / or,” can include a variety of meanings, which can depend at least in part on the context in which such terms are used. Generally, “or,” if used to relate a list, such as A, B, or C, is intended to indicate A, B, and C used in an inclusive sense; and A, B, or C used in an exclusive sense. Furthermore, depending at least in part on the context, the terms “one or more” or “at least one” used herein can be used to describe any feature, structure, or characteristic in a single sense, or can be used to describe a combination of features, structures, or characteristics in a plural sense. Similarly, depending at least in part on the context, terms such as “a,” “an,” or “the” can also be understood to express singular or plural usage. Furthermore, depending at least in part on the context, the terms “based on” or “determined by” can be understood not necessarily to convey a set of exclusive factors; rather, they can allow for the presence of additional factors that are not necessarily explicitly described.

[0034] This disclosure describes a method and apparatus for coordinating a departure process for one or more devices including multiple subscriber identity modules (Multi-SIM).

[0035] Next-generation (NG) mobile communication systems are propelling the world towards an increasingly interconnected and networked society. High-speed and low-latency wireless communication relies on efficient network resource management and allocation between user equipment and radio access network nodes (including but not limited to wireless base stations). NG networks promise to provide high-speed, low-latency, and ultra-reliable communication capabilities, meeting the needs of diverse industries and users.

[0036] This disclosure describes various embodiments for sending initial access information to a user equipment. Figure 1 A wireless communication system 100 is shown, comprising more than one wireless network node (118 and 119) and one or more user equipment (UE) (110, 111 and 112).

[0037] For fifth-generation mobile communication technology, the UE 110 (e.g., a smartphone) may have a single Subscriber Identity Module (SIM) or multiple Subscriber Identity Modules (Multi-SIM). When the UE has a single SIM, the UE may connect to one network node 118, such as a Radio Access Network (RAN) node and / or a Core Network (CN) node, or it may connect to more than one network node (118 and 119), such as two RAN nodes and / or two CN nodes. When the UE has a Multi-SIM, the UE may connect to more than one network node (118 and 119), such as two RAN nodes, two CN nodes, and / or one RAN node and one CN node.

[0038] The wireless network nodes (118 and 119) may include a network base station, which may be a nodeB (NB, e.g., gNB) in a mobile telecommunications context. Each of the UEs (110, 111, and / or 112) may wirelessly communicate with the wireless network nodes (118 and / or 119) via one or more radio channels 115. For example, the first UE 110 may wirelessly communicate with the first network node 118 via a channel including multiple radio channels during a specific time period; during another time period, the first UE 110 may wirelessly communicate with the second network node 119 via a channel including multiple radio channels.

[0039] When a UE has a Multi-SIM, it can be referred to as a Multi-SIM device. A UE with a Multi-SIM can register with more than one network. For example, the UE's first SIM (USIM1) registers with network A (first network); and the UE's second SIM (USIM2) registers with network B (second network). When USIM1 is connected to network A, once the UE determines that it needs to perform some work on network B, the UE needs to coordinate with network A. In various embodiments, "some work on network B" can include scenarios such as, but not limited to, the following.

[0040] The first scenario may include a periodic switch, which includes at least one of paging reception or serving cell measurement. In one implementation, the scenario may include at least one of the following: synchronization signal block (SSB) detection and / or paging timing (PO) reception.

[0041] The second scenario may include measurements for cell reselection, including at least one of intra-frequency detection, inter-frequency detection, or inter-Radio Access Technology (RAT) detection. In one implementation, the scenario may include at least one of the following: serving cell measurement, intra-frequency cell detection, intra-frequency cell measurement, inter-frequency cell detection, inter-frequency cell measurement, inter-Radio Access Technology (RAT) cell detection, or inter-RAT cell measurement.

[0042] The third scenario may include receiving System Information Block Type 1 (SIB1) or System Information (SI) from at least one of the neighboring cells or the serving cell.

[0043] The fourth scenario may include at least one of a control plane (CP) procedure triggered by an upper layer, a mobile origin (MO) signaling, or a CP procedure triggered by radio resource control (RRC). In one implementation, the upper layer-triggered CP procedure includes a registration procedure, the MO signaling includes Short Message Service (SMS), or the RRC-triggered CP procedure includes a Routing Area Update (RAU).

[0044] The fifth scenario may include a radio access network / core network (RAN / CN) paging response. In one implementation, the RAN / CN paging response includes a busy indication.

[0045] The sixth scenario may include MO data / call services.

[0046] This disclosure describes various embodiments for coordinating a departure process for at least one scenario, including but not limited to the scenario described above. This disclosure also describes methods, systems, and storage media for classifying at least one scenario into different departure types and performing detailed departure processes for each departure type.

[0047] Figure 2 An example of an electronic device 200 for implementing a network node or network base station is shown. The example electronic device 200 may include a radio transmit / receive (Tx / Rx) circuitry system 208 for transmitting / receiving communications with a UE and / or other base stations. The electronic device 200 may also include a network interface circuitry system 209 for enabling the base station to communicate with other base stations and / or the core network (e.g., optical or wired interconnects, Ethernet, and / or other data transmission media / protocols). The electronic device 200 may optionally include an input / output (I / O) interface 206 for communicating with operators, etc.

[0048] Electronic device 200 may also include system circuitry 204. System circuitry 204 may include processor(s) 221 and / or memory 222. Memory 222 may include operating system 224, instructions 226, and parameters 228. Instructions 226 may be configured for use by one or more processors 221 to perform the functions of a network node. Parameters 228 may include parameters to support the execution of instructions 226. For example, parameters may include network protocol settings, bandwidth parameters, radio frequency mapping allocation, and / or other parameters.

[0049] Figure 3 An example of an electronic device for implementing a terminal device 300 (e.g., a user equipment (UE)) is shown. The UE 300 may be a mobile device, such as a smartphone or a mobile communication module installed in a vehicle. The UE 300 may include a communication interface 302, a system circuitry 304, input / output interfaces (I / O) 306, a display circuitry 308, and a storage device 309. The display circuitry may include a user interface 310. The system circuitry 304 may include any combination of hardware, software, firmware, or other logic / circuit systems. The system circuitry 304 may be implemented, for example, using one or more system-on-chip (SoC), application-specific integrated circuits (ASIC), discrete analog and digital circuits, and other circuit systems. The system circuitry 304 may be part of the implementation of any desired functionality in the UE 300. In this regard, system circuitry 304 may include logic that facilitates, for example, the following: decoding and playing music and video, such as MP3, MP4, MPEG, AVI, FLAC, AC3, or WAV decoding and playback; running applications; accepting user input; saving and retrieving application data; establishing, maintaining, and terminating cellular phone calls or data connections, as an example, for internet connections; establishing, maintaining, and terminating wireless network connections, Bluetooth connections, or other connections; and displaying relevant information on user interface 310. User interface 310 and input / output (I / O) interface 306 may include a graphical user interface, a touch-sensitive display, haptic feedback or other haptic outputs, voice or facial recognition inputs, buttons, switches, speakers, and other user interface elements. Other examples of I / O interface 306 may include microphones, video and still image cameras, temperature sensors, vibration sensors, rotation and orientation sensors, headphone and microphone input / output jacks, universal serial bus (USB) connectors, memory card slots, radiation sensors (e.g., IR sensors), and other types of inputs.

[0050] refer to Figure 3The communication interface 302 may include a radio frequency (RF) transmit (Tx) and receive (Rx) circuitry 316 for processing the transmission and reception of signals via one or more antennas 314. The communication interface 302 may include one or more transceivers. The transceiver may be a wireless transceiver, including a modulation / demodulation circuitry, a digital-to-analog converter (DAC), a shaping table, an analog-to-digital converter (ADC), filters, waveform shapers, preamplifiers, power amplifiers, and / or other logic for transmission and reception via one or more antennas or (for some devices) via a physical (e.g., wired) medium. The transmitted and received signals may follow any of a variety of formats, protocols, modulations (e.g., QPSK, 16-QAM, 64-QAM, or 256-QAM), frequency channels, bit rates, and encodings. As a specific example, communication interface 302 may include a transceiver supporting transmission and reception under 2G, 3G, BT, WiFi, Universal Mobile Telecommunications System (UMTS), High-Speed ​​Packet Access (HSPA)+, 4G / Long Term Evolution (LTE), and 5G standards. However, the technologies described below are applicable to other wireless communication technologies, whether originating from the 3rd Generation Partnership Project (3GPP), the GSM Association, 3GPP2, IEEE, or other partners or standards bodies.

[0051] refer to Figure 3 The system circuitry 304 may include one or more processors 321 and a memory 322. The memory 322 stores, for example, an operating system 324, instructions 326, and parameters 328. The processor 321 is configured to execute instructions 326 to implement the desired functions of the UE 300. Parameters 328 can provide and specify configuration and operation options for instructions 326. The memory 322 may also store any BT, WiFi, 3G, 4G, 5G, or other data that the UE 300 will send or has received via the communication interface 302. In various implementations, the system power of the UE 300 may be provided by power storage devices such as batteries or transformers.

[0052] This disclosure describes several embodiments, which may be partially or wholly based on the above. Figures 2-3 Implemented on the network base stations and / or user equipment described herein.

[0053] refer to Figure 4 This disclosure describes an embodiment of a method 400 for configuring a departure procedure for multiple networks by a user equipment (UE). Method 400 may include some or all of the following steps: step 410: determining a departure type by the UE in response to a specific scenario; and step 420: coordinating the departure procedure by the UE based on at least one of the departure type or the specific scenario.

[0054] refer to Figure 5 This disclosure describes an embodiment of a method 500 for configuring a departure process by a radio access network (RAN) node. Method 500 may include some or all of the following steps: step 510: receiving a transition notification indicating departure assistance information by the RAN node; step 520: determining a transition configuration for departure configuration by the RAN node; and step 530: sending a transition response by the RAN node to a user equipment (UE).

[0055] refer to Figure 6 This disclosure describes an embodiment of a method 600 for configuring a leave procedure by a radio access network (RAN) node. Method 600 may include some or all of the following steps: step 610: receiving information indicating a simple procedure by the RAN node; and step 620: avoiding triggering a specific procedure by the RAN node upon receiving the information.

[0056] In various embodiments, the UE registers with multiple networks by at least one of the following: registering multiple networks with multiple user identity modules (Multi-SIM); or registering multiple networks with a subscribed user identity module (SIM).

[0057] In various embodiments, the multiple networks include at least one of the following: multiple radio access networks (RANs), including a first RAN and a second RAN; multiple core networks (CNs), including a first CN and a second CN; or RANs and CNs.

[0058] In various embodiments, the departure type may include one of two types: a long departure type and a short departure type. In one implementation, for the long departure type, the UE may enter an idle / inactive state in network A (first network) and enter a connected state in network B (second network); for the short departure type, the UE may remain in the connected state. In another implementation, the short departure type may include a periodic departure type and a one-shot departure type.

[0059] In various embodiments, the departure type includes at least one of the following: a long departure type for a transition notification procedure to transfer the UE to an idle or inactive state with respect to the first RAN; a periodic departure type for a transition notification procedure to keep the UE in an RRC_CONNECTED state with respect to the first RAN; and a single departure type for a transition notification procedure to keep the UE in an RRC_CONNECTED state with respect to the first RAN.

[0060] In various embodiments, a cause may be added to indicate a Multi-SIM or multiple network connection between at least one of the following: UE and a first RAN; UE and a core network (CN) node; first RAN and a CN node; second RAN and a CN node; or first RAN and second RAN.

[0061] Determine the departure type

[0062] In various embodiments, the first, second, third, and fifth scenarios discussed above can be identified as short departure types; the sixth scenario can be identified as a long departure type. Depending on other factors, the fourth scenario can be identified as either a long departure type or a short departure type.

[0063] In one implementation, the second network may not specify the situation in the fourth scenario as a long departure trigger condition, thus leaving it to the UE to decide whether it should be a long departure type or a short departure type.

[0064] In another implementation, the second network can specify some or all of the cases in the fourth scenario as long departure type or short departure type, for example, specifying it as a short single departure trigger condition.

[0065] For the triggering event in the fourth scenario, the time delay can vary. For example, but not limited to, the registration process can be triggered by parameter changes or by moving to a new Tracking Area Identity (TAI). For parameter changes, the registration process may not involve changes to Access and Mobility Management Functions (AMF), but for moving to a new TAI, it may involve changes to AMF. Furthermore, the time delay can be determined based on the type of service in progress. In the case of only non-guaranteed bit rate (non-GBR) bearers, the UE can use a long departure procedure; otherwise, a short departure procedure can be used to maintain connectivity as much as possible.

[0066] In such Figure 7 In the various embodiments shown, for CP plane procedures triggered by an upper layer (e.g., UE NAS layer 710), such as registration in the fourth scenario or other MO signaling (e.g., SMS), the upper layer can determine the departure type and indicate the departure type to the lower layer of the UE (e.g., UE AS 720) in step 751. In one implementation, the upper layer of the UE can also indicate the triggering reason and / or the expected duration. In another implementation, in step 752, the lower layer of the UE can trigger a departure procedure based on the upper layer's indication.

[0067] Long departure type process

[0068] In various embodiments, a long-term transition process for long-departure types can be used as a transition notification process that moves the UE to an idle or inactive state in network A after sending a transition notification to network A (the first network). In one implementation, the idle or inactive state can be indicated by RRC_IDLE or RRC_INACTIVE.

[0069] In various embodiments, some of the auxiliary information for mobility termination (MT) restrictions may include at least one of the following: information for temporarily restricting / filtering MT data / signaling processing; an indication that the UE should only be paged for voice (MMTel voice or CS domain voice (for EPS)); an indication that the UE should not be paged at all; or multiple packet data network (PDN) connections for MT notification / paging restrictions.

[0070] For long-term departure, the UE can enter an idle / inactive state, and this auxiliary information should be sent to the network. Therefore, it is best to use NAS signaling for long-term departure.

[0071] Figure 8 An example of a long departure procedure based on NAS signaling is shown. Referring to step 851, UE 810 sends a service request to AMF 830, including, for example, MUSIM MT filtering assistance information and a departure indication. In step 852, AMF sends an N2 message to NG-RAN 820, which includes MUSIM MT filtering assistance information indicating service acceptance. In step 853, NG-RAN determines whether to enter an inactive / idle state. Optionally, in step 854, NG-RAN indicates service acceptance to UE. In step 855, NG-RAN sends Radio Resource Control (RRC) signaling to UE to indicate an idle / inactive state. Optionally, in step 856.1, NG-RAN sends a UE context release request to AMF. In step 856.2, NG-RAN goes to an inactive state, and RAN filters paging based on assistance information. In step 856.1a, AMF goes to an idle state, and CN filters paging based on assistance information.

[0072] Another issue concerns whether the UE needs to indicate the preferred state. If NAS signaling will be used, the network can distinguish between long and short departures, and the network should be left to determine the idle / inactive state; therefore, indicating the preferred state is unnecessary.

[0073] Figure 9An example of a long departure procedure based on AS signaling is shown. Referring to step 951, UE NAS 910 sends MT filtering assistance information to UE AS 920. In step 952, UE AS sends UE assistance information with MT filtering information to NG-RAN 930. In step 953, NG-RAN determines whether to enter an inactive / idle state. In step 954, NG-RAN sends an RRCConnection release to UEAS. In step 955.1, NG-RAN sends a UE context release request with MT filtering assistance information to AMF 940. In step 955.2, NG-RAN goes to the inactive state, where RAN filters paging according to the assistance information. In step 955.1a, AMF goes to the idle state, where CN filters paging according to the assistance information.

[0074] Short-term departure types: periodic short-term departure and single short-term departure

[0075] In various embodiments, short departure types may include periodic departure types and single departure types. In one implementation, a periodic departure type includes a transition notification procedure that keeps the UE in RRC_CONNECTED with respect to the first network; and a single departure type includes a transition notification procedure that keeps the UE in RRC_CONNECTED with respect to the first network. In another implementation, a short transition procedure may be used for a transition notification procedure that keeps the UE in RRC_CONNECTED in network A (the first network) after sending a transition notification to network A.

[0076] In various embodiments, the third, fourth, and fifth scenarios discussed above can be identified as single-leave types, and the paging detection in the first scenario can be identified as a periodic-leave type.

[0077] In one implementation, for serving cell measurement in the first scenario, the UE can measure the SS-RSRP and SS-RSRQ levels of the serving cell, and evaluate the cell selection criterion S of the serving cell at least once every M1*N1 DRX cycles; wherein if the SMTC cycle (TSMTC) > 20 milliseconds (ms) and the DRX cycle ≤ 0.64 seconds, then M1 = 2, otherwise M1 = 1.

[0078] In another implementation, the UE can use at least two measurements to filter the SS-RSRP and SS-RSRQ measurements of the serving cell. Within a set of measurements used for filtering, at least two measurements should be spaced at least DRX cycles / 2 apart.

[0079] In another implementation, measurements of the serving cell can also be considered periodic events, and therefore periodic departures are also required. Therefore, measurements of the serving cell in the first scenario can be considered periodic events and may also require periodic departures.

[0080] In various embodiments, the second scenario discussed above can be identified as either periodic or single-leave. Depending on the reselection requirements, it can have periodic properties. For example, for intra-frequency reselection, once the serving cell satisfies Srxlev ≤ S IntraSearchP Or Squal≤S IntraSearch The UE can then perform in-frequency measurements according to the following requirements: When Treselection = 0, the UE can evaluate the newly detected in-frequency cell in T... detect，NR_Intra Whether the cell within the frequency range meets the reselection criteria. The UE can target cells within the frequency range identified and measured according to measurement rules at least every T. measure，NR_Intra (See Table 1) Measure SS-RSRP and SS-RSRQ.

[0081] Table 1: T detect，NR_Intra T measure，NR_Intra and T evaluate，NR_Intra

[0082]

[0083] Based on Table 1, for in-frequency measurements, during the DRX cycle, the UE can first detect the SSB to be synchronized, then detect paging. After paging detection, the UE can perform detection or measurement, or both. The detection / measurement gap (Gap) can be continuous or discontinuous with the PO, depending on the in-frequency SMTC.

[0084] Figure 10 An example of a periodic gap pattern is shown. For example, but not limited to, for FR1, the DRX period can be 0.32 seconds, and the UE may need the following gaps: T1 = DRX period, length = SSB detection (optional) + PO (1010); T2 = 36 DRX periods, length = SSB detection (optional) + PO + in-frequency detection (1020); T3 = 4 DRX periods, length = SSB detection (optional) + PO + measurement (1030).

[0085] In one implementation, one or more gap patterns may include at least one set of a reference subcarrier spacing (SCS) for at least one gap pattern, a gap start time, a gap repetition period, a duration, and one or more gap purposes. The duration of the gap may include at least one of the following: the number of Ts; or the number of symbols. The reference SCS can be implicitly indicated by using the SCS of the initial bandwidth portion (BWP) of the first network.

[0086] In various embodiments, measurements between frequencies and between RATs can be similar to those within a frequency range, and periodic gaps may also be required for detection / measurement. In one implementation, periodic gaps may also be required for detection / measurement within a frequency range, between frequencies, and between RATs.

[0087] In various embodiments, it can also be implemented by the UE. When the measurement used for cell reselection is treated as a short event, the UE may need to frequently coordinate to leave with network A, which will severely impact the performance of network A.

[0088] In various embodiments, the UE may indicate one or more gap modes having one or more purposes to the network. In one implementation, the purpose may include at least one of the following: SSB detection, PO detection, serving cell measurement, intra-frequency cell detection, intra-frequency cell measurement, inter-frequency cell detection, inter-frequency cell measurement, inter-RAT cell detection, and inter-RAT cell measurement.

[0089] In various embodiments, the network can receive one or more gap patterns with one or more purposes from the UE. In one implementation, the purpose may include at least one of the following: SSB detection, PO detection, serving cell measurement, intra-frequency cell detection, intra-frequency cell measurement, inter-frequency cell detection, inter-frequency cell measurement, inter-RAT cell detection, and inter-RAT cell measurement. In another implementation, the network determines whether to retain or not retain the gap based on the purpose.

[0090] Periodic short departure type (or periodic departure type)

[0091] Figure 11 An example of a periodic departure process is shown. In step 1151, UE 1110 sends a notification indicating a periodic, short-duration transition to network A (first network, 1120). In step 1152, network A sends an RRCReconfiguration message to the UE. In step 1153, the UE sends an RRCReconfigurationComplete message to network A.

[0092] In various embodiments, for the first scenario discussed above, which includes paging reception and serving cell measurement, the parameters for indicating a gap in paging may include at least one of the following: an indication of the need for a gap, for example, that the UE may need a gap, or that the need for a gap is disabled (e.g., if another SIM is disabled); a gap mode request, such as a gap start time, a gap repetition period, etc.; and / or a gap length.

[0093] In one implementation, the gap length can be calculated using either the number of Ts or the number of symbols. When using the number of symbols, the SCS of the initial BWP of network A can be taken.

[0094] Figure 12 An example of the duration of a periodic gap is shown. The UE can map the periodic gap pattern of network B (second network 1220) to network A (first network 1210). For example, the parameter set with (start FN, SFN, symbol, duration) can be (x, 2, n, 2) instead of (y, 0, m, 4).

[0095] In various embodiments, for each gap pattern, the UE may indicate the gap duration, gap start time, gap repetition period, and reference SCS. In one implementation, the gap duration may be the number of Ts or the number of symbols. In another implementation, for the number of symbols, the SCS of the initial BWP of the current network may be used as the reference SCS. In yet another implementation, the current network may refer to the network to which the UE will send gap information.

[0096] In various embodiments, the network may receive the duration of each gap and determine the scheduling based on that duration and the SCS of the initial BWP or a reference SCS indicated by the UE.

[0097] For example, an Asn.1 encoding of one or more gap patterns with one or more purposes can be represented as follows.

[0098]

[0099]

[0100] Where startSFN can refer to the start subframe number of the periodic gap, which is based on the timing of the cell that will retain the periodic gap; startFN can refer to the start frame number of the gap, which is based on the timing of the cell that will retain the periodic gap; subcarrierSpacing can refer to the reference SCS of the periodic gap. If not included, the SCS of the initial BWP of the cell that will retain the periodic gap will be used as the reference SCS; startSymbol can refer to the start symbol of the periodic gap, which is based on the timing of the cell that will retain the periodic gap; Duration can refer to the duration of the periodic gap in symbols; Period can refer to the period of the periodic gap.

[0101] Single departure type

[0102] In various embodiments, the second, third, fourth, and fifth scenarios discussed above can trigger a single-departure type process.

[0103] Figure 13 An example of a single departure process is shown. In step 1351, UE 1310 sends a brief transition notification to network A (first network, 1320). In step 1352, network A sends a transition response to the UE. In step 1353, the UE sends a return message to network A.

[0104] In one implementation, the transition response includes RRC signaling with a gap pattern.

[0105] In another implementation, the gap pattern includes at least one of the following: long scheduling gap; gap with time division multiplexing (TDM) mode; or autonomous gap.

[0106] In another implementation, in response to the gap mode being configured as a long scheduling gap: the gap duration is equal to the departure duration; and the UE avoids downlink (DL) and uplink (UL) reception during the gap duration.

[0107] In another implementation, in response to the gap mode being determined as a gap with TDM mode: the UE periodically communicates with the second RAN multiple gaps during a short departure duration.

[0108] In another implementation, the UE indicates a gap with TDM mode to a second network.

[0109] In another implementation, the TDM mode includes at least one of the following: a bitmap for one or more subframes; a bitmap for one or more frames; or one or more indications of start time, duration, period, or reference SCS.

[0110] In another implementation, in response to the gap mode being determined as an autonomous gap: during the gap duration, the UE determines communication with either the first RAN or the second RAN.

[0111] In various embodiments, the UE receives gap pattern information from a first RAN; and the UE leaves the first RAN based on the gap pattern information. In one implementation, the UE uses a timer to control the gap duration by at least one of the following: starting the timer when a gap pattern configuration is received; stopping the timer when a procedure concerning the second network ends; or terminating the procedure on the second network and resuming return to the first RAN when the timer expires. In another implementation, the length of the timer is equal to the gap duration configured in the gap pattern.

[0112] Figure 14 An example of a long scheduling gap (or long scheduled gap) is shown. Network A 1410 is the first network; and network B 1420 is the second network. The gap length can be equal to the short departure duration, and during the gap, the network can avoid DL and UL scheduling. In one implementation, for a dual-Rx UE, such as for the second and third scenarios described above, a reduced Rx capability for DL ​​scheduling can be employed. Considering that neither DL nor UL can be scheduled, and a single process can take tens of milliseconds, this mode may impact the UE experience.

[0113] Figure 15 An example of a gap with a TDM mode is shown. Network A 1510 is the first network; and network B 1520 is the second network. A scheduled gap with a TDM mode can be similar to a measurement gap, where network A can periodically retain some gaps during the departure duration. In one implementation, the UE can inform the network of the preferred TDM mode as auxiliary information. In another implementation, the UE needs to provide network A with sufficient auxiliary information to determine the TDM mode during the scheduled gap.

[0114] Figure 16 An example of an autonomous gap is shown. Network A 1610 is the first network; and network B 1620 is the second network. During the autonomous gap, similar to a conventional MUSIM UE, it is left to the UE to decide how to communicate with both networks (1610 and 1620). In one implementation, during the autonomous gap, the UE can maintain a temporary and short dual-activity state via TDM methods.

[0115] refer to Figure 17In step 1751, UE 1710 sends a single departure indication to NG-RAN 1720. The single departure indication may include at least one of a departure reason or a departure duration. In step 1752, NG-RAN determines which gap mode is preferred. In step 1753, NG-RAN sends RRC signaling with the preferred gap mode. Optionally, in step 1754, UE sends a response message to NG-RAN.

[0116] In various embodiments, the network may indicate a gap mode for leaving to the UE.

[0117] In one implementation, the gap pattern can be a long scheduling gap, a gap with a TDM pattern, or an autonomous gap.

[0118] In another implementation, for long scheduled gaps, the gap length can be equal to the short departure duration. During the gap, the network should avoid both DL and UL scheduling.

[0119] In another implementation, the gap length can be broadcast in system information or configured via dedicated signaling. For dedicated signaling, the network can adopt a value recommended by the UE.

[0120] In another implementation, for gaps with TDM modes, network A can periodically retain the gap during the departure duration.

[0121] In another implementation, the duration of the gap with TDM mode can be broadcast in system information or configured via dedicated signaling, for which the network can adopt a value recommended by the UE.

[0122] In another implementation, the network can determine the TDM mode based on the TDM mode recommended by the UE, the ongoing service, and the radio environment.

[0123] In another implementation, the TDM mode can be a bitmap for subframes or frames, or indicated by start time, duration, period, and / or reference SCS.

[0124] In another implementation, for autonomous gaps, how to communicate with the two networks during the gap is left to the UE implementation.

[0125] In another implementation, the network can determine the gap pattern based on the ongoing service type and / or the quality of service (QoS) of the PDU session.

[0126] In another implementation, the network can send gap mode information via RRC signaling.

[0127] In another implementation, the RRC signal can be an RRCReconfiguration message.

[0128] In another implementation, the network can also reject leave requests by not allocating any gaps.

[0129] In various embodiments, the UE may receive gap pattern information from the gNB and leave the current operation based on the gap.

[0130] In one implementation, the gap pattern can be a long scheduling gap, a gap with a TDM pattern, or an autonomous gap.

[0131] In another implementation, for the scheduled gap, the gap length can be equal to the short departure duration. During the gap, the network should avoid both DL and UL scheduling.

[0132] In another implementation, the UE can indicate the gap length or the reason for leaving to the network.

[0133] In another implementation, the reasons for leaving may include the second, third, fourth, and fifth scenarios as described above.

[0134] In another implementation, for gaps with TDM mode, the gap can be periodically retained during the departure duration.

[0135] In another implementation, the UE can indicate the TDM mode to the network.

[0136] In another implementation, the TDM mode can be a bitmap for subframes or frames, or indicated by start time, duration, period, and / or reference SCS.

[0137] In another implementation, for autonomous gaps, during the gap, it is left to the UE to decide how to communicate with the two networks.

[0138] In another implementation, for autonomous gaps, the UE can start a timer to control the duration of the autonomous gap.

[0139] In another implementation, for autonomous gaps, the UE can stop the autonomous gap timer when the work with another USIM is completed.

[0140] In another implementation, for autonomous gaps, the UE can abort the process with another USIM and return to the first USIM when the timer expires.

[0141] In another implementation, the UE can receive gap mode information via RRC signaling.

[0142] In another implementation, the RRC signal can be an RRCReconfiguration message.

[0143] In another implementation, when the UE does not receive any gap mode information from the gNB, the UE can either implement the gap mode information or maintain the connection at the current network.

[0144] In this disclosure, various embodiments address at least one of the following problems regarding single departure: whether the UE needs to indicate to network A when communication with network B ends before the scheduled / autonomous gap; and / or whether network A should remain connected or return to an idle / inactive state when communication with network B cannot be completed before the scheduled / autonomous gap. In one implementation, for the first problem, the UE can send an indication to network A once communication with network B is complete; and network A can then resume its previous configuration and data transmission as soon as possible. In another implementation, for the second problem, whether network A remains connected or returns to an idle / inactive state can be determined based on the service / procedure priority of one or more USIMs. For example, a single departure procedure can be employed for the second, third, fourth, and fifth scenarios as described above. For the second and third scenarios as described above, it can have a lower priority compared to data / voice services on network A. For the fourth scenario, for registration, the UE can retransmit it several times according to the CT1 specification. For MO signaling (e.g., SMS), a long departure procedure can be employed if it has a high priority. For RAU, this could cause the UE to enter an idle state, and this problem can be reduced by configuring a sufficiently long interval. For the fifth scenario, if it is still necessary, the UE can retransmit in the next DRX cycle, for example, by detecting paging again in the next DRX cycle.

[0145] As discussed above, the purpose of a single departure process can be to minimize the impact on network A; therefore, it is best to keep network A connected. In another implementation, network A can also determine whether to remain connected, or the UE can provide suggestions when a gap is needed.

[0146] In another implementation, if communication with network B cannot be completed before the scheduled / autonomous gap timer expires, the ongoing process on network B can be suspended and services on network A can continue.

[0147] In another implementation, for the short departure procedures in scenarios four and five, the UE can attempt to complete the procedure on network B as quickly as possible. Simultaneously, network B can be aware that the UE is in a short departure state of another USIM, and therefore network B may not trigger mobility procedures, such as, but not limited to, handover or redirection, measurement, and DC-related procedures. The UE may also not trigger a reconstruction procedure.

[0148] In another implementation, the UE can notify Network B that it is in a short departure process on another network, and then Network B can avoid triggering mobility (e.g., handover, redirection), measurement, and / or DC-related processes.

[0149] In another implementation, for the idle state, the UE can indicate this information in message 5 (msg5). For the inactive state, the UE can also enter the connected state unless there is an rna-Update procedure, so the UE can also include this information in message 5.

[0150] In another implementation, the UE can notify network B via RRC signaling that it is in a short departure process on another network.

[0151] In another implementation, the RRC signaling can be Msg 5, such as RRCSetupComplete / RRCResumeComplete.

[0152] In another implementation, the RRC signaling can be Msg 3 with a different establishment reason.

[0153] Figure 18 An example of a short departure procedure indication for a second network is shown. In step 1851, SIM1 1820 is in a connected state, so SIM2 1810 needs to establish a connection with SIM2 gNB 1840. Therefore, the UE coordinates departure with SIM1 gNB 1830; and after coordination, SIM2 establishes an RRC connection with SIM2. In step 1852, SIM2 AS sends an RRC establishment request or recovery request to SIM2 gNB. In step 1853, SIM2 gNB sends an RRC establishment or RRC recovery request to SIM2 AS. In step 1854, SIM2 AS sends an RRC establishment or recovery completion message to SIM2 gNB (with an indication, such as MUSIMShortLeavingIndication or a simple procedure indication). In step 1855, SIM2 gNB avoids triggering a handover or measurement.

[0154] In various embodiments, the Asn.1 encoding of the Multi-Sim short departure indicator for Msg5 can be as follows.

[0155]

[0156] One or more of these indicators (e.g., shortLeavingIndication or simpleProcedureIndication) can be used with a Multi-SIM UE. When the UE is in a short-leaving state on another USIM card, the UE can indicate this indicator to the current network so that the current network can complete the process as quickly as possible, without triggering a handover / measurement process.

[0157] In various embodiments, the UE may have a Multi-SIM and a USIM1 connected to network A and a USIM2 connected to network B. When USIM1 is connected to network A and briefly leaves to network B, the QoS of USIM1 may be affected. A PDU session may be affected or must be released, so a clear reason (e.g., MUSIM or MUSIM short departure) can be added to the interface between the UE / RAN node / CN node. For example, for a PDU session resource notification message, the purpose of the PDU session resource notification procedure may be to notify that established QoS flows or PDU sessions for a given UE have been released or are no longer satisfied, or have been requested to be satisfied again by the NG-RAN node in control. Once a PDU session is released or no longer satisfied due to MUSIM short departure, it can include a new reason (e.g., MUSIM or MUSIM short departure) to the CN node.

[0158] In one implementation, a new cause (e.g., MUSIM or MUSIM short departure) can be added between the UE and the RAN node, or between the UE and the CN node, or between the RAN and the CN node, or between two CN nodes.

[0159] This disclosure describes methods, apparatus, and computer-readable media for wireless communication. This disclosure addresses a problem in the coordinated departure process for one or more devices including multiple subscriber identity modules (Multi-SIM). The methods, apparatus, and computer-readable media described in this disclosure can improve the performance of wireless transmissions between user equipment and multiple network nodes, thereby improving efficiency and overall performance. The methods, apparatus, and computer-readable media described in this disclosure can improve the overall efficiency of wireless communication systems.

[0160] References to features, advantages, or similar language in this specification do not imply that all features and advantages achievable with this solution should or are included in any single implementation thereof. Rather, references to features and advantages are to be understood as indicating that a particular feature, advantage, or characteristic described in connection with an embodiment is included in at least one embodiment of this solution. Therefore, the discussion of these features and advantages, and similar language, throughout this specification may, but not necessarily, refer to the same embodiments.

[0161] Furthermore, the features, advantages, and characteristics described in this solution can be combined in any suitable manner in one or more embodiments. Based on the description herein, those skilled in the art will recognize that this solution can be practiced without one or more specific features or advantages of a particular embodiment. In other instances, additional features and advantages that may not be present in all embodiments of this solution may be recognized in certain embodiments.

Claims

1. A method for wireless communication, comprising: The user equipment (UE) configures the departure process for multiple networks using the following items: The departure type is determined by the UE in response to a specific scenario; The UE coordinates the departure process based on the departure type, wherein the plurality of networks includes a plurality of radio access networks (RANs), and the plurality of RANs includes a first RAN and a second RAN; as well as In response to the departure type being determined to be a predetermined type, and: The UE sends a switching notification to the first RAN; and The UE receives the configuration message from the first RAN. The predetermined type includes periodic departures, and the transition notification includes one or more intermittent patterns. The predetermined type includes a single departure type, and the conversion notification includes the departure duration. The configuration message includes RRC signaling with a gap pattern. The gap pattern mentioned above includes long scheduling gaps. The gap mode is configured as a long scheduling gap in response to the gap: the gap duration is equal to the departure duration.

2. The method according to claim 1, further comprising: The UE indicates one or more gap patterns to the first RAN, the one or more gap patterns being used for paging timing PO reception.

3. The method according to claim 1 or 2, wherein: The configuration message includes configurations for the one or more gap patterns.

4. A method for wireless communication, comprising: A transition notification indicating departure assistance information is received by a radio access network (RAN) node, wherein, in response to a corresponding departure type including periodic departure, the transition notification includes one or more intermittent patterns; and in response to a corresponding departure type including a single departure type, the transition notification includes a departure duration. The RAN node determines the transition configuration for leaving the configuration; and The RAN node sends a configuration message to the user equipment (UE), wherein, in response to the corresponding departure type, including a single departure type, the configuration message includes RRC signaling with a gap mode, the gap duration being equal to the departure duration.

5. The method according to claim 4, further comprising: The RAN node receives the transition notification from the UE, the transition notification including one or more gap patterns, the one or more gap patterns being used for paging timing (PO) detection.

6. A communication device, comprising: The memory stores instructions; as well as A processor, which communicates with the memory, wherein, when the processor executes the instructions, the processor is configured to cause the device to configure an outgoing process for multiple networks by: Determine the departure type in response to a specific scenario; The departure process is coordinated based on the departure type, wherein the plurality of networks includes a plurality of radio access networks (RANs), the plurality of RANs including a first RAN and a second RAN; and In response to the departure type being determined to be a predetermined type, and: Send a conversion notification to the first RAN; and Receive configuration messages from the first RAN. The predetermined type includes periodic departures, and the transition notification includes one or more intermittent patterns. The predetermined type includes a single departure type, and the conversion notification includes the departure duration. The configuration message includes RRC signaling with a gap pattern. The gap pattern mentioned above includes long scheduling gaps. The gap mode is configured as a long scheduling gap in response to the gap: the gap duration is equal to the departure duration.

7. The communication apparatus of claim 6, wherein the processor is configured to cause the communication apparatus to perform: The first RAN is instructed with one or more gap patterns, which are used for paging timing PO reception.

8. The communication device according to claim 6 or 7, wherein: The configuration message includes configurations for the one or more gap patterns.

9. A wireless node, comprising: The memory stores instructions; as well as A processor, which communicates with the memory, wherein, when the processor executes the instructions, the processor is configured to cause the wireless node to execute: Receive a transition notification indicating departure assistance information, wherein in response to a corresponding departure type including periodic departure, the transition notification includes one or more intermittent patterns; and in response to the corresponding departure type including a single departure type, the transition notification includes the departure duration; Determine the transition configuration to use for leaving the configuration; and A configuration message is sent to the user equipment (UE), wherein, in response to the corresponding departure type, including a single departure type, the configuration message includes RRC signaling with a gap mode, the gap duration being equal to the departure duration.

10. The wireless node of claim 9, wherein the processor is configured to cause the wireless node to perform: The UE receives the transition notification, which includes one or more gap patterns used for paging timing (PO) detection.

Images