Apparatus for terminal device

Abstract

To enable a coordinated leave from a Multi-Radio Dual Connectivity connection to initiate a radio resource control connection to another subscriber identification module of a terminal device.SOLUTION: An apparatus is equipped in a terminal device and includes at least one processor and a memory for storing an instruction. When the instruction is executed by the at least one processor, the instruction causes a terminal device configured to support multi-radio dual connectivity connection having at least two different connections to execute: a step of determining temporary performance limitation related to a plurality of subscriber identification modules; and a step of transmitting, to a network device, information indicating that at least one of the two different connections should be released. The terminal device has a plurality of subscriber identification modules including a first subscriber identification module and a second subscriber identification module.SELECTED DRAWING: Figure 4

Description

[Technical field]

[0001] The various exemplary embodiments relate to an apparatus for a terminal device comprising at least one processor.

[0002] A further embodiment relates to a method of operating a terminal device.

[0003] A further embodiment relates to an apparatus for a network device comprising at least one processor.

[0004] A further embodiment relates to a method of operating a network device. [Background technology]

[0005] A wireless communication system may be used for the wireless exchange of information between two or more entities, such as, for example, between user equipment comprising one or more terminal devices and one or more network devices, such as base stations.

[0006] Some terminal devices may have more than one, e.g., simultaneous, network subscription, e.g., multiple corresponding International Mobile Subscriber Identity (IMSI) in Evolved Packet System (EPS) or SUbscription Permanent Identifier (SUPI) in 5th Generation Core (5GC), each associated with a specific Universal Subscriber Identity Module (USIM) belonging to the same or different Mobile Network Operator (MNO) or Mobile Network Virtual Operator (MNVO). Such terminal devices may be denoted as multiple USIM devices, MUSIM devices.

[0007] Some terminal devices are capable of Multi-Radio Dual Connectivity (MR-DC), which is dual connectivity between an Evolved Universal Terrestrial Radio Access (E-UTRA) and a (5G) New Radio (NR) node, or between two NR nodes. MR-DC is possible in both Evolved Packet Core (EPC) and 5GC. The four variants of MR-DC are EN-DC, NGEN-DC, NE-DC, and NR-DC.

[0008] For MR-DC with EPC, E-UTRAN supports MR-DC via E-UTRA-NR dual connectivity (EN-DC) where a user equipment (UE) is connected to one eNB (eNodeB) acting as a master node (MN) and one EN-gNB acting as a secondary node (SN). The eNB is connected to the EPC via an S1 interface and to an en-gNB via an X2 interface. The en-gNB may also be connected to the EPC via an S1-U interface and to other en-gNBs via an X2-U interface.

[0009] For MR-DC with 5GC, E-UTRA-NR dual connectivity (NGEN-DC) is defined, where a UE is connected to one ng-eNB acting as an MN and one gNB acting as an SN. Furthermore, NR-E-UTRA dual connectivity (NE-DC) is defined, where a UE is connected to one gNB acting as an MN and one ng-eNB acting as an SN. Furthermore, NR-NR dual connectivity is defined, where a UE is connected to one gNB acting as an MN and another gNB acting as an SN. Summary of the Invention

[0010] The scope of protection sought for various embodiments of the present disclosure is indicated by the independent claims. The exemplary embodiments and features described herein that do not fall within the scope of the independent claims, if any, should be interpreted as examples useful for understanding various exemplary embodiments of the present disclosure.

[0011] Some embodiments include an apparatus comprising at least one processor and a memory storing instructions that, when executed by the at least one processor, cause a terminal device configured to support multi-radio dual connectivity having at least two distinct connections to transmit cooperative leave information to a network indicating that at least one of the two distinct connections should be released.

[0012] In some embodiments, the cooperative departure information indicates to the network device that at least one of the two different connections should be interrupted.

[0013] In some embodiments, transmitting the cooperation departure information to the network device is used to release at least one transceiver resource of the terminal device.

[0014] In some embodiments, transmitting the cooperation departure information to the network device is used to temporarily release at least one transceiver resource of the terminal device.

[0015] In some embodiments, the apparatus may be an apparatus for a wireless communication system.

[0016] In some embodiments, the apparatus or functionality thereof, respectively, may be provided in a terminal device of a communications system, for example in a user equipment (UE).

[0017] In some embodiments, the apparatus according to the embodiments or its functionality may be used for or in a wireless communication system, e.g., a network, based on or at least partially compliant with a wireless standard such as 3rd Generation Partnership Project, 3GPP, 4G E-UTRAN or 5G NR (Fifth Generation New Radio), or other radio access technology, respectively. In some embodiments, the apparatus according to the embodiments or its functionality may be used for at least one of MR-DC, e.g., EN-DC, NGEN-DC, NE-DC, and NR-DC, respectively.

[0018] In some embodiments, a terminal device may have several transceiver resources that may be used, for example, in a dual connectivity configuration. In some embodiments, it may be desirable to release at least one of the several transceiver resources, for example to enable a further (e.g., second) connection, for example, a further USIM connection. In some embodiments, the terminal device may use the cooperation departure information according to the embodiment to inform the network that it is desirable to release at least one of the several transceiver resources, thus enabling, for example, to perform a cooperation departure.

[0019] According to some embodiments, the instructions, when executed by at least one processor, cause the terminal device to use at least one of a Radio Resource Control (RRC) message, a Secondary Cell Group Failure Information message (SCG Failure Information), e.g., SCG Failure Information according to some recognized specifications, to transmit the cooperative departure information.

[0020] According to some embodiments, when using an SCG failure information message according to some recognized specifications, a cause value may be defined by which the cooperation departure may be characterized, which may for example be included in the SCG failure information. According to some embodiments, since the SCG failure information message is used to indicate the cooperation departure purpose and not as an indication of link degradation of e.g. a secondary cell group, the terminal device does not need to include any measurements in the SCG failure information message according to some recognized specifications.

[0021] According to some embodiments, the instructions, when executed by the at least one processor, cause the terminal device to receive first configuration information, e.g., from a network device, e.g., a master node, characterizing a reconfiguration of a bearer associated with the terminal device.

[0022] According to some embodiments, a network node, e.g., a master node, may trigger a bearer re-mapping, i.e., a “pullback”, e.g., secondary cell group (SCG) bearer, e.g., single connectivity, to the master cell group MCG, to avoid interruption of ongoing services.

[0023] According to some embodiments, the network node, for example the master node, may further suspend the secondary cell group.

[0024] According to some embodiments, the instructions, when executed by the at least one processor, cause the terminal device to receive second configuration information instructing the terminal device to suspend at least one bearer associated with the master cell group, and suspend the at least one bearer associated with the master cell group based on the second configuration information.

[0025] According to some embodiments, a network element, e.g., a master node, may not be able to perform bearer remapping, e.g., due to resource constraints (or expected priority traffic on the secondary cell group and / or any other network internal reasons). According to some embodiments, the network element, e.g., a master node, may, e.g., in lieu of bearer remapping, instruct the terminal device to continue with the secondary cell group of the current EN-DC connection with the suspended master cell group.

[0026] According to some embodiments, the instructions, when executed by the at least one processor, further cause the first subscriber identity module of the terminal device to perform at least one of: a) sending a resource release request to the second subscriber identity module of the terminal device; and b) receiving a resource release confirmation from the second subscriber identity module of the terminal device.

[0027] According to some embodiments, when the terminal device receives a resource release request to the second subscriber identity module of the terminal device, the terminal device can send cooperation leaving information according to an embodiment.

[0028] According to some embodiments, upon receiving the first configuration information, the terminal device may send a resource release confirmation to the first subscriber identity module of the terminal device, e.g. signaling that the respective resources have been released and may be used, e.g., by the first subscriber identity module.

[0029] A further embodiment relates to a method of operating a terminal device, e.g., a UE, configured to support Multi-Radio Dual Connectivity (MR-DC) with at least two different connections, comprising transmitting cooperation departure information to a network device, e.g., a master node, indicating that at least one of the two different connections should be released.

[0030] A further embodiment relates to an apparatus comprising means for causing a terminal device, e.g., a UE, configured to support Multi-Radio Dual Connectivity (MR-DC) with at least two different connections, to transmit cooperation departure information to a network device, e.g., a master node, indicating that at least one of the two different connections should be released.

[0031] A further embodiment relates to an apparatus comprising at least one processor and a memory storing instructions that, when executed by the at least one processor, cause a network device, e.g., a master node, to at least receive coordinated departure information indicating that at least one of two different connections of a terminal device configured to support a multi-radio dual connection with at least two different connections should be released.

[0032] According to some embodiments, the instructions, when executed by the at least one processor, further cause the network device to determine whether bearers associated with the secondary cell group can be remapped to the master cell group, and based on the determination, transmit to the terminal device first configuration information characterizing a reconfiguration of bearers associated with the terminal device or second configuration information instructing the terminal device to suspend at least one bearer associated with the master cell group.

[0033] According to some embodiments, the instructions, when executed by the at least one processor, further cause the network device to notify the handover target of the cooperation leaving condition of the terminal device based on the cooperation leaving information. By way of example, according to some embodiments, when the secondary cell group resource is relinquished and the master node undergoes handover, e.g., as a result of master node layer mobility, the secondary cell group is suspended for cooperation leaving according to some embodiments, while the (source) master node can notify and / or instruct the target master node of the handover to avoid secondary cell group configuration during inter-master node mobility execution, e.g., until the cooperation leaving condition based on the cooperation leaving information is revoked (e.g., the prohibition of not having secondary cell group resource for dual connectivity is active).

[0034] A further embodiment comprises a method of operating a network device, e.g., a master node, comprising receiving coordinated departure information indicating that at least one of two different connections of a terminal device configured to support multi-radio dual connectivity with at least two different connections should be released.

[0035] A further embodiment relates to a system comprising at least one apparatus for a terminal device according to an embodiment and at least one apparatus for a network device according to an embodiment. [Brief description of the drawings]

[0036] [Figure 1] 1 illustrates generally a simplified block diagram of an apparatus according to some embodiments. [Diagram 2] 1 illustrates generally a simplified block diagram of an apparatus according to some embodiments. [Diagram 3] 1 illustrates generally a simplified block diagram of a system according to some embodiments. [Figure 4]1 illustrates generally a simplified flow chart according to some embodiments. [Diagram 5] 1 illustrates generally a simplified flow chart according to some embodiments. [Figure 6] 1 illustrates generally a simplified flow chart according to some embodiments. [Figure 7] 1 illustrates generally a simplified flow chart according to some embodiments. [Figure 8] 1 illustrates generally a simplified flow chart according to some embodiments. [Figure 9A] 1 illustrates generally a simplified flow chart according to some embodiments. [Figure 9B] 1 illustrates generally a simplified flow chart according to some embodiments. [Figure 10] 1 illustrates generally a simplified block diagram of an apparatus according to some embodiments. [Figure 11] 1 illustrates generally a simplified block diagram of an apparatus according to some embodiments. [Figure 12] 1 illustrates a simplified signaling chart according to some embodiments. [Figure 13] 1 illustrates a simplified signaling chart according to some embodiments. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0037] Some embodiments relate to an apparatus, for example for a terminal device of a wireless communication system. Figure 1 illustrates generally a simplified block diagram of an apparatus 100 according to some embodiments, and Figure 4 illustrates generally a simplified flow chart of a method of operating the apparatus 100 according to some embodiments.

[0038] The apparatus 100 (FIG. 1) comprises at least one processor 102 and a memory 104 storing instructions 106 which, when executed by the at least one processor 102, cause the terminal device 10 to execute 302 (FIG. 4) transmitting cooperation departure information CL-I to the network device 20 (FIG. 3) configured to support multi-radio dual connectivity with at least two different connections C1, C2 (see, e.g., FIG. 3), indicating that at least one of the two different connections C1, C2 should be released.

[0039] In some embodiments, the apparatus 100 or its functionality, respectively, may be provided in a terminal device 10 of the communication system 1 (FIG. 3), for example in a user equipment (UE).

[0040] In some embodiments, the apparatus 100 according to the embodiments or functions thereof may be used for or in a wireless communications system 1, e.g., a network, based on or at least partially compliant with a wireless standard such as 3rd Generation Partnership Project, 3GPP, 4G E-UTRAN or 5G NR (Fifth Generation New Radio), or other radio access technology, respectively.

[0041] In some embodiments, the apparatus 100 according to the embodiment or functions thereof may be used for MR-DC, e.g., at least one of EN-DC, NGEN-DC, NE-DC, and NR-DC, respectively, and / or for other types of multi-radio dual connectivity.

[0042] In some embodiments, the terminal device 10 may have several transceiver resources TRX that may be used, for example, in a dual connectivity configuration.

[0043] In some embodiments, the terminal device 10 may have several Universal Subscriber Identity Modules (USIM) 10-1, 10-2.

[0044] In some embodiments, the terminal devices 10 may share some transceiver resources TRX, for example by means of Universal Subscriber Identity Modules (USIMs) 10-1, 10-2.

[0045] In some embodiments, at least some of the transceiver resources TRX may be configured for dual connectivity, for example. In some embodiments, at least some of the transceiver resources TRX may be shared across universal subscriber identity modules (USIMs) 10-1, 10-2, for example. In some embodiments, the transceiver resources TRX may be either configured for dual connectivity or shared across universal subscriber identity modules (USIMs) 10-1, 10-2.

[0046] In some embodiments, the first connection C1 may be, for example, a connection with a master node of an EN-DC configuration using a master cell group. In some embodiments, the second connection C2 may be, for example, a connection with a secondary node of an EN-DC configuration using a secondary cell group. In other words, according to some embodiments, the first connection C1 may represent an MCG leg of an MR-DC radio connection, and the second connection C2 may represent an SCG leg of the MR-DC radio connection.

[0047] In some embodiments, the first connection C1 and / or the second connection C2 are not limited to respective physical connections, but may, for example, include one logical connection or multiple logical connections, respectively.

[0048] In some embodiments, the cooperation departure information CL-I indicates to the network device 20 that at least one of the two different connections C1, C2 should be interrupted.

[0049] In some embodiments, the cooperation departure information CL-I indicates to the network device 20 that a secondary cell group associated with at least one of the two different connections C1, C2 should be suspended.

[0050] In some embodiments, transmitting 302 the cooperation leaving information CL-I to the network device 20 is used to release at least one transceiver resource TRX of the terminal device 10.

[0051] In some embodiments, transmitting 302 the cooperation leaving information CL-I to the network device 20 is used to temporarily release at least one transceiver resource TRX of the terminal device 10.

[0052] In some embodiments, for example due to a shared use of some transceiver resources TRX, it may be desirable to release at least one of the some transceiver resources TRX, for example to enable a further (e.g., second) connection, for example a further USIM connection. In some embodiments, the terminal device 10 may use the cooperation leaving information CL-I according to the embodiment to inform the network, for example via the network device 20, that it is desirable to release at least one of the some transceiver resources TRX, thus enabling for example to perform a cooperation leaving.

[0053] In some embodiments, the terminal device 10, e.g., a second USIM 10-2 of the terminal device 10 (FIG. 3), may receive a resource release request at 300 (FIG. 4), e.g., from a first USIM 10-1 of the terminal device 10, indicating that it is desirable to release at least one of a number of transceiver resources TRX. In some embodiments, the terminal device 10 may transmit cooperation leaving information CL-I after receiving (300) the resource release request, block 302 of FIG. 4.

[0054] According to some embodiments, the instructions 106 (FIG. 1), when executed by the at least one processor 102, cause the terminal device 10 (FIG. 3) to use at least one of a radio resource control message, a secondary cell group failure information message (SCG failure information), e.g., SCG failure information according to some recognized specifications, for transmitting 302 (FIG. 4) the cooperation departure information CL-I.

[0055] According to some embodiments, when using the SCG failure information message according to some accepted specifications, a cause value characterizing the cooperation departure may be defined, which may be included in the SCG failure information, for example. In other words, by including a cause value characterizing the cooperation departure, the terminal device 10 may signal to the network device 20 that there is, for example, no link degradation, but that cooperation departure is desired, for example due to a resource release request (block 300 in FIG. 4).

[0056] According to some embodiments, the terminal device 10 does not need to include any measurements in the SCG failure information message according to some accepted specifications, since the SCG failure information message is used to indicate cooperation departure purposes, e.g. using a cause value, and not as an indication of link degradation of, e.g., a secondary cell group.

[0057] According to some embodiments of FIG. 5, the instructions 106 (FIG. 1), when executed by at least one processor 102, cause the terminal device 10 (FIG. 3) to receive 304 first configuration information CF-II from, for example, a network device 20 (FIG. 3), which may be, for example, a master node for Multi-Radio Dual Connectivity (MR-DC) over E-UTRA-NR Dual Connectivity (EN-DC), and the first configuration information CF-I1 characterizes a reconfiguration of bearers associated with the terminal device.

[0058] According to some embodiments, the network node 20, e.g., a master node, may trigger a bearer re-mapping, i.e., a "pullback" of, e.g., a secondary cell group (SCG) bearer to the master cell group MCG, e.g., single connectivity, e.g., to avoid interruption of ongoing services. In some embodiments, information regarding the bearer re-mapping may be signaled by the master node 20 to the terminal device 10 using the first configuration information CF-I1.

[0059] According to some embodiments, the network node 20, for example the master node, may further suspend the secondary cell group. In some embodiments, information regarding the suspension of the secondary cell group may be signaled by the master node 20 to the terminal device 10 using the first configuration information CF-I1.

[0060] According to some embodiments, after receiving 304 the first configuration information CF-I1, the terminal device 10, e.g. its second USIM 10-2 (Figure 3), may transmit a first USIM 10-1a resource release confirmation, e.g. based on the first configuration information CF-I1 (see block 306 in Figure 5).

[0061] According to some embodiments, the master node 20 may not be able to perform bearer remapping from the secondary cell group to the master cell group, e.g., due to resource constraints (or priority traffic expected on the secondary cell group and / or any other network internal reasons). According to some embodiments, the master node, e.g., instead of bearer remapping, instructs the terminal device 10 to continue the secondary cell group of the current EN-DC connection, e.g., the master cell group is interrupted. In some embodiments, the instruction to the terminal device 10 to continue the secondary cell group of the current EN-DC connection (e.g., see FIG. 6 described below) may be signaled to the terminal device 10 by the master node 20 using the second configuration information CF-I2. According to some embodiments of FIG. 6, the instructions 106 (FIG. 1), when executed by at least one processor 102, cause the terminal device 10 to receive 310 second configuration information CF-I2 instructing the terminal device 10 to suspend at least one bearer associated with the master cell group, and suspend 312 the at least one bearer associated with the master cell group based on the second configuration information CF-I2.

[0062] According to some embodiments, similar to, for example, block 306 of FIG. 5, the terminal device 10, for example its second USIM 10-2, transmits a resource release confirmation 314 to the first USIM 10-1, which may be done, for example, upon reception 310 of the second configuration information CF-I2 (FIG. 6) and / or upon suspension 312 of at least one bearer associated with the master cell group.

[0063] According to some embodiments of FIG. 7, the instructions 106, when executed by the at least one processor 102, further cause the first subscriber identity module, e.g., USIM 10-1, of the terminal device 10 to perform at least one of: a) sending 320 a resource release request to a second subscriber identity module, e.g., USIM 10-2, of the terminal device 10; and b) receiving 322 a resource release confirmation from the second subscriber identity module, e.g., USIM 10-2, of the terminal device 10.

[0064] As described above, according to some embodiments, upon receiving 300 (FIG. 4) a resource release request to the second subscriber identity module 10-2 of the terminal device 10, the terminal device 10 may transmit cooperation leaving information CL-I according to an embodiment (see block 302 in FIG. 4).

[0065] As described above, according to some embodiments, upon receiving 304 (FIG. 5) the first configuration information CF-I1 (see block 306 in FIG. 5), the terminal device 10 may send a resource release confirmation to the first subscriber identity module 10-2 of the terminal device 10, e.g., signaling that the respective resources have been released and can be used, for example, by the first subscriber identity module 10-1.

[0066] A further embodiment (Figure 4) relates to a method of operating a terminal device 10 (Figure 3), e.g. a UE, configured to support Multi-Radio Dual Connectivity (MR-DC) with at least two different connections, comprising transmitting 302 cooperation leaving information CL-I to a network device 20, e.g. a master node, indicating that at least one of the two different connections C1, C2 should be released.

[0067] A further embodiment (see, for example, FIG. 10 ) relates to an apparatus 100′ comprising means 102′ for causing a terminal device 10 ( FIG. 3 ), a terminal device 10 ( FIG. 3 ), configured to support Multi-Radio Dual Connectivity (MR-DC), e.g. a UE, to transmit 302 ( FIG. 4 ) cooperation leaving information CL-I to a network device 20, e.g. a master node, indicating that at least one of two different connections C1, C2 should be released.

[0068] In some embodiments, the means 102′ may comprise, for example, at least one processor 102 (FIG. 1) and at least one memory 104 storing instructions 106, e.g., the at least one memory 104 and the instructions 106 configured to execute, with the at least one processor 102, aspects and / or steps of a method according to an embodiment.

[0069] A further embodiment (see, e.g., FIG. 2) relates to an apparatus 200, comprising at least one processor 202 and a memory 204 storing instructions 206, which when executed by the at least one processor 202, cause a network device 20 (FIG. 3), e.g., a master node of an exemplary EN-DC connection, to at least receive 350 (FIG. 8) cooperation leaving information CL-I indicating that at least one of two different connections C1, C1 of a terminal device configured to support multi-radio dual connectivity with at least two different connections should be released. As an example, the master node 20 may receive the cooperation leaving information CL-I from the terminal device 10 of FIG. 3.

[0070] In some embodiments, for example, referring to optional block 352 of FIG. 8, the master node 20 may perform further operations based on the cooperation departure information CL-I received in block 350.

[0071] According to some embodiments, the instructions 206 (FIG. 2), when executed by the at least one processor 202, further cause the network device 20 to determine, at 352a of FIG. 9A, whether a bearer associated with the secondary cell group can be remapped to the master cell group, and, at 352b, based on the determination 352a, transmit to the terminal device 10 first configuration information CF-I1 characterizing a reconfiguration of a bearer associated with the terminal device 10 if, for example, a bearer associated with the secondary cell group can be remapped to the master cell group, or transmit to the terminal device 10 second configuration information CF-I2 instructing the terminal device 10 to suspend at least one bearer associated with the master cell group if, for example, a bearer associated with the secondary cell group cannot be remapped to the master cell group.

[0072] According to some embodiments, the instructions 206, when executed by the at least one processor 202, further cause the network device 20 (FIG. 3) to notify (354) (FIG. 9A) a handover target (not shown in FIG. 3) of a cooperation leaving condition of the terminal device 10 based on the cooperation leaving information. By way of example, according to some embodiments, when the secondary cell group resources are relinquished and the master node 20 undergoes a handover, e.g., as a result of master node layer mobility, the secondary cell group is suspended for cooperation leaving according to some embodiments, while the (source) master node 20 can notify and / or instruct the target master node of the handover to avoid secondary cell group configuration during inter-master node mobility execution, e.g., until the cooperation leaving condition based on the cooperation leaving information CL-I is revoked (e.g., the prohibition of not having secondary cell group resources for dual connectivity is active).

[0073] According to some embodiments of FIG. 9B, the instructions 206, when executed by at least one processor 202, further cause the network device 20 (FIG. 3) to send first configuration information CF-I1 to the terminal device 10 characterizing a reconfiguration of a bearer associated with the terminal device 10 (352b'), suspend (353) the secondary cell group, and notify (354') a handover target (e.g., a target master node) of the suspension 353 of the secondary cell group.

[0074] As mentioned above, in some embodiments, the cooperation departure information CL-I may indicate to the network device 20 that a secondary cell group associated with at least one of the two different connections C1, C2 of the terminal device 10 should be suspended. However, according to some embodiments, upon receiving the cooperation departure information CL-I (350), the network device 20 may override this indication and, for example, decide or determine to suspend the master cell group instead (e.g., see block 352 of FIG. 8 ).

[0075] A further embodiment comprises a method of operating a network device 20, e.g. a master node, comprising receiving (350) cooperation departure information CL-I, e.g. from a terminal device 10, indicating that at least one of two different connections C1, C2 of the terminal device 10 configured to support multi-radio dual connectivity with at least two different connections C1, C2 should be released (FIG. 8).

[0076] A further embodiment (see, e.g., FIG. 11 ) relates to an apparatus 200′ comprising means 202′ for causing a network device 20 ( FIG. 3 ), e.g. a master node of an EN-DC connection, to at least receive (350) ( FIG. 8 ) cooperation leaving information CL-I, e.g. from a terminal device 10, indicating that at least one of two different connections C1, C2 of the terminal device 10 configured to support multi-radio dual connectivity with at least two different connections C1, C2 should be released.

[0077] In some embodiments, the means 202′ may comprise, for example, at least one processor 202 (FIG. 2) and at least one memory 204 storing instructions 206, e.g., the at least one memory 204 and the instructions 206 configured to execute, with the at least one processor 202, aspects and / or steps of a method according to an embodiment.

[0078] A further embodiment relates to a system 1 (see, for example, FIG. 3) comprising at least one apparatus 100, 100' for a terminal device 10 according to an embodiment and at least one apparatus 200, 200' for a network device 20 according to an embodiment.

[0079] Figure 12 illustrates a simplified signaling chart according to some embodiments. Block 10-1 illustrates a first USIM 10-1 (see also Figure 3 for example) of a terminal device 10 configured to support multi-radio dual connectivity with at least two different connections C1, C2, for example according to an EN-DC scheme, where E-UTRAN supports MR-DC via E-UTRA-NR dual connectivity. Block 10-2 illustrates a second USIM 10-2 of the terminal device 10. Block 20 illustrates a master node of the EN-DC scheme, and block 30 illustrates a secondary node 30 of the EN-DC scheme.

[0080] According to some embodiments, based on the two USIMs 10-1, 10-2, the terminal device 10 may also be referred to as a "dual USIM device." According to some embodiments, the terminal device 10 may be connected to an LTE network via the first USIM 10-1 and by an NR-NSA connection via the second USIM 10-2, e.g., based on EN-DC-LTE / NR dual connectivity as described in some recognized specifications.

[0081] According to some embodiments, the terminal device 10 is in an RRC_connected state with the second USIM 10-2 in an EN-DC dual connectivity mode, where in some embodiments the terminal device 10 may already be using its transceiver resources TRX, e.g., dual transceivers, for dual connectivity.

[0082] According to some embodiments, when the first USIM 10-1 tries to set up a radio resource control connection, the second USIM 10-2 may need to suspend one of the cell groups used in the dual connectivity, e.g., the Master Cell Group (MCG) or the Secondary Cell Group (SCG), in order to utilize / release one transceiver resource TRX, e.g., one receiver (RX) / transmitter (TX) chain for the first USIM 10-1. In some embodiments, this may be signaled using a method according to the embodiment, e.g., by transmitting cooperation departure information CL-I (302) (FIG. 4).

[0083] In this regard, Fig. 12 exemplarily illustrates a connection mode with dual connectivity of the second USIM 10-2 (see element e1 of Fig. 12). Block e2 illustrates the first USIM 10-1 deciding or deciding to initiate a radio resource control connection, and block e3 illustrates, for example, a resource release request being sent internally (to the terminal device 10) from the first USIM 10-1 to the currently (dual) connected second USIM 10-2.

[0084] 12 illustrates an exemplary transmission of cooperation leaving information CL-I (diagram 302), e.g., indicating cooperation leaving, from the terminal device 10, e.g., the second USIM 10-2, to the master node 10. In other words, according to some embodiments, the terminal device 10 may use the cooperation leaving information CL-I to propose to the master node 20, e.g., to relinquish a secondary cell group.

[0085] In some embodiments, the transmission e4 may include, for example, using a secondary cell group failure information message (“SCG failure information”), e.g., SCG failure information according to some recognized specifications that may optionally include a cause value that characterizes the cooperation departure, thus enabling, for example, the master node 20 to distinguish the cooperation departure information CL-I from, for example, other types of secondary cell group failure information messages, e.g., associated with different cause values.

[0086] According to a further embodiment, the cause value may be forwarded by the master node 20 to the secondary node 30, for example using radio resource control signaling, for example a radio resource control forwarding message according to some recognized specifications.

[0087] In some embodiments, transmission e4 may use another message or type of signaling, such as, for example, radio resource control signal (e.g., a newly defined message) signaling, or other type of signaling that enables notifying the master node 20 of the cooperation departure condition.

[0088] According to a further embodiment, upon receiving the cooperation leaving information CL-I in transmission e4, in block e5 the master node 20 may determine that the bearers associated with the secondary cell group may be remapped to the master cell group. Thus, the master node transmits to the terminal device 10 first configuration information CF-I1, e.g. the second USIM 10-2, indicating that the bearers associated with the secondary cell group may be remapped to the master cell group. Block e6 exemplarily illustrates the transmission of the first configuration information CF-I1.

[0089] According to a further embodiment, for example after or upon receipt of the transmission e6 of the first configuration information CF-I1, the terminal device 10, for example the second USIM 10-2, may transmit (for example internally) a resource release confirmation e7 to the first USIM 10-1, which indicates to the first USIM 10-1 that, for example, some transceiver resources TRX are now available for use by the first USIM 10-1.

[0090] According to a further embodiment, if the master node 20 determines that the bearers associated with the secondary cell group cannot be remapped to the master cell group (see, for example, block e8 of FIG. 12 ), the master node 20 may send second configuration information CF-I2, e.g., a second USIM 10-2, to the terminal device 10 (see, for example, block e10), e.g. instructing the terminal device 10 to suspend at least one bearer associated with the master cell group.

[0091] According to a further embodiment, for example before transmitting the second configuration information CF-I2 to the terminal device 10 (e5), the master node 20 can transmit handover preparation information (see block 20) ​​to the target master node, which handover preparation information for example informs the target master node about a potential future handover.

[0092] In other words, according to some embodiments, the master node 20 may inform the handover target 30 of the cooperation leaving status of the terminal device 10 (e.g., second USIM 10-2) based on the cooperation leaving information CL-I via block e9 (FIG. 12) (see, e.g., block e4). By way of example, according to some embodiments, if the secondary cell group resources are relinquished and the master node 20 undergoes a handover, e.g., as a result of master node layer mobility, the secondary cell group is suspended for cooperation leaving according to some embodiments, while the (source) master node 20 may inform and / or instruct the handover target master node to avoid secondary cell group configuration during inter-master node mobility execution, e.g., until the cooperation leaving condition based on the cooperation leaving information CL-I is revoked (e.g., until the prohibition of not having secondary cell group resources for dual connectivity is active).

[0093] According to some embodiments, for example, in response to SCG failure information e4 from the terminal device 10, the master node 20 can respond to the terminal device 10 with an alternative “MCG interrupt message” e10 to interrupt the MCG leg to release transceiver resources, for example with a specific timer for the terminal device 10 to resume dual connectivity (e.g., the SCG now continues normal operation, but this is single radio leg operation) or until SCG mobility requests it (e.g., SCG mobility requests master node 20 intervention).

[0094] According to some embodiments, for example, if the terminal device 10 does not resume dual connectivity within a specific duration, such as characterized by a specific timer (e.g., shown as “T_SUSPEND”), the network on the EN-DC may release the suspended master cell group and release the RRC connection, or the terminal device 10 may hand over the RRC connection from the master cell group to the secondary cell group.

[0095] In some embodiments, a specific timer, which may be indicated as, for example, "T_SUSPEND", may be signaled to the UE 10, for example, in the second configuration information CF-I2. In some embodiments, the specific timer may indicate to the UE 10 a maximum duration for which the master cell group may remain suspended. Within the network, this specific timer may, for example, enable the network to take further action, for example, to release the RRC connection or the terminal device 10 may handover the RRC connection from the master cell group to a secondary cell group. In some embodiments, within the UE 10, the USIMs 10-1, 10-2 may cooperate to release transceiver resources to resume the master cell group.

[0096] According to some embodiments, in block e11, the terminal device 10 may, for example, suspend the MCG bearer and resume the SCG.

[0097] According to some embodiments, block e12 indicates expiry of a timer specific for the release of resources associated with the first USIM 10-1, for example for resumed dual connectivity.

[0098] According to some embodiments, block e13 indicates a resource release confirmation to the first USIM 10-1, for example similar to block e7 described above.

[0099] According to some embodiments, element e14 indicates a message from the terminal device 10 to the secondary node 30, for example its second USIM 10-2, message e14 indicating, for example, that radio resource control reconfiguration is complete.

[0100] In some embodiments, for example, upon release of the connection of the second USIM 10-2, the terminal device 10 may signal reactivation of the SCG over the master node radio link to enable the network to resume dual connectivity operation for the given USIM 10-2. In some embodiments, for example, if the MCG was suspended prior to the second USIM connection, the terminal device 10 may signal to resume the MCG over the secondary node 30.

[0101] FIG. 13 illustrates a simplified signaling chart according to some embodiments. As in FIG. 12, block 10-1 illustrates a first USIM 10-1 (see also FIG. 3 for example) of a terminal device 10 configured to support multi-radio dual connectivity with at least two different connections C1, C2, for example according to the EN-DC scheme, and E-UTRAN supports MR-DC via E-UTRA-NR dual connectivity. Block 10-2 illustrates a second USIM 10-2 of the terminal device 10. Block 20-1 illustrates a source master node of the EN-DC scheme, block 20-2 illustrates a target master node, and block 30 illustrates a secondary node 30 of the EN-DC scheme.

[0102] According to some embodiments, the double block arrow e20 indicates that the MUSIM UE 10 (FIG. 3) has a second USIM 10-2 with an EN-DC subscription and is in an RRC_connected state with LTE-NR dual connectivity. As an example, an RRC connection may be desired for the first USIM 10-1 (e.g., to retrieve some information from an associated public land mobile network), and that desire may be signaled, for example, by sending a resource release request e21 from the first USIM 10-1 to the second USIM 10-2.

[0103] In some embodiments, the UE 10 can transmit cooperation leaving information CL-I e22 (see also FIG. 4) to the source master node 20-1, for example via its second USIM 10-2, where the cooperation leaving information CL-I indicates to the source master node 20-1 that cooperation leaving of the UE's second USIM 10-2 is desirable. As an example, the cooperation leaving information e22 may be transmitted in the form of SCG failure information (e.g., according to some accepted specifications), for example with a "new" cause (e.g., a cause indicating the desired cooperation leaving to suspend the SCG), for example, the USIM 10-1 waits for a response before the UE 10 starts a new connection for the first, for example, LTE.

[0104] According to some embodiments, block e23 illustrates a network reaction for cooperation leaving. As an example, upon receiving the SCG failure information e22 for cooperation leaving, the network node 20-1 attempts bearer remapping of SCG traffic to the MCG in block e23.

[0105] According to further embodiments, for example according to the first alternative (see for example block b1 of FIG. 13), if bearer remapping is possible, the network node 20-1 transmits first configuration information CF-I1 (see arrow e24) to the UE 10, for example the second USIM 10-2. In some embodiments, the first configuration information e24 may comprise an SCG-Dormant via MCG message, for example using an RRC message or a MAC message, for example in response to message e22.

[0106] In some embodiments, element e25 indicates a resource release confirmation from the second USIM 10-2 to the first USIM 10-1, for example after receiving the first configuration information e24.

[0107] In some embodiments, element e26 indicates an RRC completion message from the second USIM 10-2 to the source master node 20-1.

[0108] In some embodiments, element e27 indicates the first USIM 10-1 with which to establish the desired connection, eg, its associated PLMN.

[0109] In some embodiments, block b2 of FIG. 13 indicates that an inter-master node handover is triggered, for example from the source master node 20-1 to the target master node 20-2, and element e28 illustratively indicates a respective handover request.

[0110] In some embodiments, when an SCG suspension is in progress (see, e.g., block b3), an inter-master node handover may not be able to add an SCG, which may be signaled to the UE 10 (not shown) according to further embodiments, e.g., to prevent reporting measurements on the secondary node frequency until conditions to resume are further in time.

[0111] According to a further embodiment, for example according to a second alternative (see, for example, block b4 of FIG. 13), the master node 20-1 may determine that bearer remapping is not possible (see block e29).

[0112] In some embodiments, referring to block e30, the master node 20-1 may forward the master node terminated bearer to the secondary node 30.

[0113] In some embodiments, if it is not possible to remap the bearer from the SCG to the MCG, e.g. according to block e29, e.g. due to an ongoing voice call or critical traffic, the network may indicate Suspend-MCG instead to the UE10, e.g. as a response e31 to an SCG failure causing Suspend-SCG (or Leave Cooperation) e22 from the UE10.

[0114] According to some embodiments, the network 20-1 may later send another indication if the MCG can be resumed by suspending the SCG after this critical traffic (e.g., in both cases the UE may continue with single connectivity).

[0115] In some embodiments, referring to block e32, the UE 10, e.g. its second USIM 10-2, may suspend the MCG bearers as instructed by element 31 and may, e.g., continue the SCG terminated bearers and updated RRC mappings with the suspended master cell group (see also double block arrow e35).

[0116] In some embodiments, for example referring to element e33, which is similar to element e25, a resource release confirmation e33 is sent from the second USIM 10-2 to the first USIM 10-1, and using element e34, the second USIM 10-2 sends an RRC completion message to the secondary node 30.

[0117] In some embodiments, the UE 10 may respond to an "MCG-Suspend" indication e31 from the network, e.g., the master node 20-1, as follows: Instead of suspending the SCG, the UE 10 may suspend the MCG and proceed with another USIM connection.

[0118] Additionally, in some embodiments, a specific "T_SUSPEND" timer may be signaled to the UE 10 in element e31, e.g., indicating to the UE 10 a maximum duration for which the master cell group may remain suspended. In the network, this specific timer may, e.g., allow the network to take further action to release the RRC connection, or the terminal device 10 may handover the RRC connection from the master cell group to a secondary cell group. In some embodiments, in the UE 10, the USIMs 10-1, 10-2 may coordinate to release transceiver resources TRX to resume the master cell group.

[0119] In some embodiments, referring to block e32, the UE 10, e.g. its second USIM 10-2, may suspend the MCG bearers as indicated by element e31 and may, e.g., continue the SCG terminated bearers and updated RRC mapping with the suspended master cell group (see also double block arrow e35).

[0120] In some embodiments, after transmission of elements e33, e34, the first USIM 10-1 may be used, for example, for a given period of time.

[0121] According to some embodiments, element e36 may represent a call release of the first USIM 10-1, such that transceiver resources used by the first USIM 10-1 may be released for use by the second USIM 10-2, for example. For example, in block e37, the first USIM 10-1 informs the second USIM 10-2 that the transceiver resources are free, indicating, for example, a "resources available" message (see also element e38).

[0122] According to some embodiments, the UE 10, e.g. the second USIM 10-2, notifies the network (e.g. the secondary node 30) by element e39 that dual connectivity may be resumed (see, e.g., blocks b1, b4, SCG or MCG, respectively, in either of alternatives 1 or 2 above). Thus, in some embodiments, the double block arrow e40 indicates the resumption of dual connectivity, e.g. based on the notification e39.

[0123] According to some embodiments, another option of keeping the SC may be preferred by the network, and the UE 10 may get an SCG suspend indication via the SCG, for example, when the network is ready to return traffic to the MCG. The UE 10 suspends the SCG after resuming the MCG.

[0124] According to some embodiments, a further option not shown in FIG. 13 relates to not resuming dual connectivity (e.g., at all), for example because the second USIM 10-2 may not have terminated its session yet, and thus the UE 10 can, for example, continue to remain in single connectivity, i.e., one radio leg is operational.

[0125] An advantage of some embodiments is that they enable cooperative disengagement from a multi-radio dual connectivity connection, for example to initiate an RRC connection to another USIM 10-1 of the MUSIM device 10. In some embodiments, the existing RRC connection does not need to be released to allow the further USIM 10-1 to at least temporarily use the transceiver resources TRX of the UE 10. In some embodiments, the UE 10 can request release of one dual connectivity connection of the USIM 10-2, for example, to proceed with an RRC connection of another USIM 10-1 of the MUSIM UE 10. Further embodiments enable the network, for example the network device 20, to determine cell groups based on traffic conditions (e.g. release of MCG or SCG depending on traffic conditions). Some embodiments enable handling transition to connected mode operation for MUSIM scenarios with dual connectivity on one USIM 10-2 with minimal interruption to the user plane for active connections.

Claims

1. An apparatus provided in a terminal device, comprising: and a memory storing instructions that, when executed by the at least one processor, configure the terminal device to support multi-radio dual connectivity having at least two distinct connections. determining temporary performance limitations associated with a plurality of subscriber identity modules; sending information to a network device indicating that at least one of the two different connections should be released; Run the command, The terminal device has a plurality of subscriber identity modules including a first subscriber identity module and a second subscriber identity module. An apparatus comprising:

2. 2. The apparatus of claim 1, wherein the temporary performance limitation is determined based on a decision to temporarily release at least one transceiver resource of the terminal device for the first USIM.

3. 3. The apparatus of claim 2, wherein the decision to temporarily release the at least one transceiver resource is determined based on a decision to establish a radio resource control connection on a first USIM.

4. The instructions, when executed by the at least one processor, cause the terminal device to: causing a first subscriber identity module of the terminal device to send a resource release request to a second subscriber identity module of the terminal device before the step of transmitting the information; having a first subscriber identity module of the terminal device receive a resource release confirmation from the second subscriber identity module of the terminal device after the step of transmitting the information; Further execute at least one of 2. The apparatus of claim 1 .

5. 2. The apparatus of claim 1, wherein the information indicating that at least one of the two different connections should be released is transmitted to a master node of the network device using a radio resource control message.

6. 2. The apparatus of claim 1 , wherein the instructions, when executed by the at least one processor, further cause the terminal device to use at least one of a radio resource control message, a secondary cell group failure information message to transmit the information.

7. 2. The apparatus of claim 1, wherein the instructions, when executed by the at least one processor, further cause the terminal device to perform, after the step of transmitting information, a step of receiving first configuration information characterizing a reconfiguration of a bearer associated with the terminal device.

8. 8. The apparatus of claim 7, wherein the instructions, when executed by the at least one processor, further cause the terminal device to perform, after the step of receiving the first configuration information, the steps of receiving second configuration information instructing the terminal device to suspend at least one bearer associated with a master cell group, and suspending the at least one bearer associated with the master cell group based on the second configuration information.

9. 1. A method of operating a terminal device configured to support multi-radio dual connectivity having at least two different Universal Subscriber Identity Modules (USIM) connections, comprising: determining temporary performance limitations; sending information to a network device indicating that at least one of the two different USIM connections should be released; 23. A method comprising:

10. 16. An apparatus, disposed within a network device, comprising: at least one processor; and a memory storing instructions that, when executed by the at least one processor, cause the network device to: receiving information indicating that at least one of the two different connections of a terminal device configured to support multiple dual connectivity having at least two different connections should be released; determining whether a bearer associated with the secondary cell group can be remapped to the master cell group after the step of receiving the information; An apparatus for executing at least the above.

11. 11. The apparatus of claim 10, wherein the instructions, when executed by the at least one processor, further cause the network device to perform the step of transmitting, based on the determination, to the terminal device, first configuration information characterizing a reconfiguration of a bearer associated with the terminal device after the step of receiving information, or second configuration information instructing the terminal device to suspend at least one bearer associated with a master cell group.

12. 11. The apparatus of claim 10, wherein the instructions, when executed by the at least one processor, further cause the network device to perform a step of notifying a handover target of a prohibition that the terminal device does not have resources of the secondary cell group for the multiple dual connectivity based on the information.

Images