Method and electronic apparatus for transmitting capability of dual SIM dual activation device in wireless

Abstract

A method of transmitting, by an electronic device, user equipment (UE) capabilities of a dual subscriber identity module (SIM) dual active (DSDA) user equipment (DSDA UE) is disclosed. The method includes determining a respective service category for each of the first stack and the second stack based on at least one stack parameter indicated by the first stack and the second stack. The method includes determining a mode associated with the DSDA UE based on respective service categories of the first stack and the second stack. The method includes receiving respective band information associated with the first stack and the second stack from at least one network entity associated with the network. The method includes adjusting the UE based on the pattern and respective band information associated with the first stack and the second stack. The method includes transmitting the adjusted UE capabilities to at least one network entity.

Description

Technical Field

[0001] The present disclosure relates to a wireless communication system, for example, to a system and method for transmitting user equipment (UE) capabilities by a dual subscriber identity module (SIM) dual activation (DSDA) user equipment (DSDA UE) to a network. Background Art

[0002] Multiple Universal Subscriber Identity Module (MUSIM) devices are becoming increasingly popular in various countries. Currently, support for multiple USIMs within a device is handled in an implementation-specific manner, which results in various implementations and UE behaviors. Standardized support for such UEs is beneficial from a performance perspective, and the UE behavior is also predictable. Therefore, new work items (WIs), such as Dual Tx / Rx MUSIM (DSDA MUSIM), have been added to the R18 RAN2 discussion to standardize support for such UEs.

[0003] The hardware capabilities of DSDA UEs are shared by the Subscriber Identity Module (SIM), and in order to use the hardware efficiently and economically, the relevant capabilities need to be dynamically divided between the two SIMs. This may cause temporary hardware conflicts in the UE. In some cases, the UE may have to release some resources (e.g., SCell / SCG) from one of the two SIMs.

[0004] For example, in a UE having SIM A and SIM B, when SIM A of the UE is in a radio resource control (RRC) connected state in network (NW) A, and SIM B of the UE is in an RRC idle or RRC inactive state in NW B, two transmission chains will be occupied by SIM A for communication in NW A. Once SIM B of the UE enters the RRC connected state, one of the transmission chains needs to be switched to SIM B. In this case, if NW A is not aware of the reduced UE capability change in the transmission chain, data loss may occur due to demodulation failure and waste of radio resources in NW A.

[0005] One of the goals of the WI is to specify a mechanism to indicate to NW A a preference for temporary UE capability restrictions when the UE wishes to start / stop connection to NW B for MUSIM purposes (e.g. capability update, cell release, activation (deactivation) of configuration resources). One DSDA device design currently on the market (without R18 MuSIM) includes separate RF chips for both stacks, which provides good performance for both stacks. However, this hardware is expensive. If the RF capabilities are shared between the stacks, the cost will be lower than the above case, while the performance will be 50% of the performance achieved with separate RF chips.

[0006] Therefore, with the introduction of WI (NW controlled DSDA behavior) for MuSIM in the DSDA case, it is possible to use a separate RF chip for both stacks, which provides the best performance for both stacks. However, using such a separate RF chip may mean additional hardware cost and it will not make a difference whether the described features are supported or not. If the RF capabilities are shared between the stacks, the cost will be reduced and the performance will be improved compared to the above case, because sharing will only occur when it is needed. Considering the hardware cost, especially with the introduction of R18 MuSIM, most DSDA devices will use RF capabilities on a shared basis.

[0007] refer to Figure 1 , Figure 1 A capability exchange and / or RF splitting process 100 for a DSDA device according to the prior art is shown. The UE may include stack 1 and stack 2 that communicate with network 1 and network 2. The example scenario illustrates identifying that there is a problem with the current DSDA device. Stack 1 is in connected mode and is using the full capabilities of the device. Stack 2 is in RRC idle or inactive state and is moving to connected mode. At this point, the UE will have to share RF capabilities between stacks / SIMs and should update the network with capability changes for stack 1 and the limited capabilities available for stack 2. However, there is currently no mechanism defined for devices to share capabilities between stacks. Likewise, when stack 1 is in idle mode, the UE should update the network with capability changes, and, when stack 2 is in idle mode, the UE should update the network with capability changes.

[0008] A convenient and simple option could be to share 50% of the capabilities between the two stacks. However, this is not an effective approach because it limits the user from getting better QoS in many cases. In addition, it is not easy to share capabilities between stacks and provide the exact same capabilities to both stacks. Therefore, there must be a solution to split the capabilities between the stacks. The solution must ensure that the capability split provides the best QoS for the user.

[0009] Based on the above identified WI and objectives, due to the various state changes of SIM / network, it is necessary to introduce capability exchange between the device and the network. Therefore, the UE needs to indicate the difference and updated UE capabilities to the NW when applicable and when the state changes. In addition, it is also necessary to provide better QoS to the user after splitting the RF capabilities. Therefore, it is necessary to overcome the above shortcomings. For example, there is a need for methods and systems to enable the UE to seamlessly reselect neighboring cells without facing service interruption or loss. Summary of the invention

[0010] Problem Solution According to an example embodiment, a method for transmitting user equipment (UE) capabilities by a dual subscriber identity module (SIM) dual activation (DSDA) user equipment (DSDA UE) is disclosed. The method may include determining a corresponding service class for each of the first stack and the second stack based on one or more stack parameters indicated by the first stack and the second stack. The method may include determining a mode associated with the DSDA UE based on the corresponding service classes of the first and second stacks. The method may include receiving corresponding frequency band information associated with the first stack and the second stack from at least one network entity associated with a network. The method may include adjusting the UE based on the mode and the corresponding frequency band information associated with the first and second stacks. The method may include transmitting the adjusted UE capabilities to the at least one network entity.

[0011] According to an example embodiment, an electronic device is disclosed, the electronic device being configured to transmit user equipment (UE) capabilities by a dual subscriber identity module (SIM) dual activation (DSDA) user equipment (DSDA UE). The electronic device includes a first stack, a second stack, and at least one processor. The at least one processor is configured to determine a corresponding service class of each of the first stack and the second stack based on at least one stack parameter. The at least one stack parameter is indicated by each of the first stack and the second stack. The at least one processor is configured to determine a mode associated with the DSDA UE based on the corresponding service class of the first stack and the second stack. The at least one processor is configured to receive corresponding frequency band information associated with the first stack and the second stack from at least one network entity associated with a network communicating with the DSDA UE. The at least one processor is configured to adjust the UE capabilities associated with the DSDA UE based on the mode and the corresponding frequency band information associated with the first stack and the second stack. The at least one processor is configured to send the adjusted UE capabilities to at least one network entity associated with the network.

[0012] The above-mentioned electronic device may be associated with a user equipment (UE).

[0013] To further illustrate the advantages and features of the present disclosure, the present disclosure will be described in more detail with reference to various exemplary embodiments shown in the accompanying drawings. It will be understood that these drawings only describe exemplary embodiments and should not be considered as limiting the scope thereof. The present disclosure will be described and illustrated in more detail using the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] The above and other aspects, features and advantages of certain embodiments of the present disclosure will become more apparent through the following detailed description in conjunction with the accompanying drawings, in which like characters in the accompanying drawings represent like parts throughout the drawings, wherein: Figure 1 is a diagram showing a capability exchange and / or RF partitioning process for a DSDA device according to the prior art; Figure 2 is a signal flow diagram showing an overview of a UE transmitting capabilities to a network according to various embodiments; Figure 3 is a flow chart illustrating an example method of transmitting UE capabilities by a DSDA UE according to various embodiments; Figure 4A is a diagram illustrating an example method of adjusting UE capabilities according to various embodiments; Figure 4B is a signal flow diagram illustrating an example of adjusting UE capabilities according to various embodiments; Figure 5A is a flow chart illustrating an example method of adjusting UE capabilities according to various embodiments; Figure 5B is a signal flow diagram illustrating an example of adjusting UE capabilities according to various embodiments; Fig. 6A is a flow chart illustrating an example method of adjusting UE capabilities according to various embodiments; Figure 6B is a signal flow diagram illustrating an example method of adjusting UE capabilities according to various embodiments; Figure 7 is a flow chart illustrating an example method of sharing transmit power between a first stack and a second stack according to various embodiments; Fig. 8A and Figure 8B is a flow chart illustrating an example method for updating UE capabilities for a device that does not support the R18 MuSIM feature according to various embodiments; Fig. 9 is a block diagram illustrating an example configuration of a network entity according to various embodiments; Fig.10 is a block diagram illustrating an example configuration of a user equipment according to various embodiments; Fig.11 is a diagram showing an example hardware configuration of a DSDA UE device according to various embodiments; and Fig.12 is a block diagram illustrating an example configuration of a decision entity and an RF module implemented by a processor of a DSDA UE according to various embodiments.

[0015] Furthermore, those skilled in the art will appreciate that the elements in the drawings are drawn for simplicity and are not necessarily drawn to scale. For example, a flow chart illustrates a method. Furthermore, with respect to the structure of the device, one or more components of the device may have been represented in the drawings with conventional symbols, and the drawings may only show specific details relevant to understanding the various exemplary embodiments to avoid obscuring the drawings with details that would be clear to those skilled in the art having the benefit of the description herein. DETAILED DESCRIPTION

[0016] Reference will now be made to the various exemplary embodiments shown in the drawings and specific language will be used to describe them. It will be understood, however, that the scope of the present disclosure is not thereby limited in any way and that such changes and further modifications to the illustrated systems, as well as further applications of the illustrated principles of the present disclosure, are all within the ordinary contemplation of those skilled in the art to which the present disclosure relates.

[0017] It will be understood by those skilled in the art that the foregoing general description and the following detailed description are intended to explain the present disclosure rather than to limit the present disclosure.

[0018] "One aspect," "another aspect," or similar language appearing throughout this disclosure may mean, for example, that a particular feature, structure, or characteristic described in conjunction with an embodiment is included in at least one embodiment of the present disclosure. Thus, phrases "in one embodiment," "in another embodiment," and similar language appearing throughout this disclosure may, but do not necessarily, all refer to the same embodiment.

[0019] The terms "include", "comprises" or any other variations thereof are intended to cover a non-exclusive inclusion, for example, a process or method that includes a series of steps does not include only these steps, but may also include other steps not expressly listed or inherent to the process or method. Similarly, one or more devices or subsystems or elements or structures or components introduced by "including...a" does not exclude the existence of other devices or other subsystems or other elements or other structures or other components or additional devices or additional subsystems or additional elements or additional structures or additional components without more limitations.

[0020] The present disclosure provides a method and system for a DSDA UE to transmit user equipment (UE) capabilities to a network. For example, the UE may include two SIM stacks, and the capabilities may be divided between the two stacks. The UE may notify the network of the UE capabilities. The capabilities may be divided based on the stack, the UE's serving cell, and / or the services being used by the UE's neighboring cells. Therefore, a mechanism may be provided to indicate UE capability-related information to the network, such as, but not limited to, preferences for temporary UE capability restrictions, capability updates, cell release, and activation (deactivation) of configuration resources. For example, the network may be notified of a capability change in one of the two stacks and / or a limited capability of one of the two stacks. Therefore, the network may be aware of the UE capabilities, thereby preventing and / or reducing quality of service losses at the UE.

[0021] Figure 2 2 is a signal flow diagram 200 illustrating an example of transmitting capabilities from a UE to a network according to various embodiments. Fig.10 The UE and its related functions and architecture are explained in more detail. In various embodiments, the UE may transmit the modified capabilities to the network. Figure 2 As shown, the UE communicates with the first network entity and the second network entity. Fig. 9 The network entities and their related functions and architecture are explained. The UE may include a first stack and a second stack, wherein the first stack may communicate with a first network entity and the second stack may communicate with a second network entity.

[0022] In the illustrated embodiment, the first network entity may provide browsing-related data to the first stack, as shown in block 202a, and the second network entity may provide call-related data to the second stack, as shown in block 202b. The first stack may be in a connected mode with the first network entity, and the second stack may be moving to a connected mode with the second network entity. Therefore, as shown by arrows 204a and 204b, the UE may update UE capabilities based on frequency bands associated with the first network entity and the second network entity (e.g., shared frequency band A and frequency band B). The updated UE capabilities may then be transmitted to the network entities.

[0023] In various embodiments, both the first stack and the second stack can be in connected mode. The second stack can use low data services, such as audio calls. As shown in block 206, the first stack can trigger high data services, such as video streaming. In this case, as shown by arrows 208a and 208b, the UE can release carrier aggregation (CA) for the second stack because the low data services are being used, and in addition, the UE capabilities can be updated to keep more possibilities for the first stack. The updated UE capabilities can then be transmitted to the network entity.

[0024] Furthermore, once the first stack completes the high data service, the first stack may not require carrier aggregation, as shown in block 210. As shown by arrows 212a and 212b, the UE may update the UE capabilities to share the UE capabilities equally with both the first stack and the second stack, and then transmit the updated UE capabilities to the network entity.

[0025] In various embodiments, the UE capabilities may be updated when a cell change or a frequency band information change is identified. In various embodiments, services triggered or ongoing in both stacks may be considered to split the capabilities. In various embodiments, the capabilities may be split considering the serving cell and neighboring cells of each stack. In various embodiments of service-based splitting, the capabilities may be split based on the type of service required by the stack. After receiving a request to move to connected mode, the split mode may be determined. In various embodiments of cell-based splitting, the capabilities may be split based on the serving cell and optional neighboring cells (e.g., from a system information block SIB) of each stack. After receiving a request to move to connected mode, the serving cell and neighboring cells of the stack may be checked, and the frequency band information may be indicated. In various embodiments, the updated capabilities may be sent to the RRC of both stacks, and further, the RRC may also send the updated capabilities to the respective network entities.

[0026] Figure 3 3 is a flow chart illustrating an example method 300 for transmitting UE capabilities by a DSDA UE according to various embodiments. The method 300 may be performed by a UE. In various embodiments, the UE may include a first stack and a second stack. In various embodiments, the first stack may be associated with a first subscriber identity module (SIM) of the UE, and the second stack may be associated with a second SIM of the UE. Fig.10 The UE and its related functions and architecture are explained in more detail. UE may include but is not limited to mobile phones, tablets, smart watches, and any other electronic devices capable of connecting to 4G and / or 5G networks.

[0027] The UE may communicate with one or more network entities. Fig. 9 The network entity and related functions and the corresponding architecture are explained in more detail. In various embodiments, the network entity may be a network node in a 5G network, for example, a 5G core network (5GC), or a network node in an LTE network.

[0028] In various embodiments, the network entity may be associated with one or more network operators, for example, a first operator and a second operator. In various embodiments, the first operator may be associated with a first stack, and the second operator may be associated with a second stack.

[0029] In step 302, a corresponding service class is determined for each stack in the first stack and the second stack based on one or more stack parameters. The corresponding service class may refer to the type of service triggered or ongoing in the stack. For example, the first stack may use a first class of service and the second stack may use a different second class of service. The UE capabilities may be segmented based on the types of services being used by the first stack and the second stack.

[0030] In various embodiments, the service type may include a high data service and a low data service. For example, the service type may include an audio call, a video call, a video streaming, etc. In various embodiments, the service class may be classified based on one or more stack parameters. In various non-limiting examples, the service class may be classified as small data (SD), high data (HD), and call (Call) based on one or more stack parameters.

[0031] In various embodiments, one or more stack parameters may be indicated by each stack in the first stack and the second stack. In various embodiments, the one or more stack parameters include one or more of buffer occupancy, data arrival, delay details, and data type. In various embodiments, the first stack and the second stack may both indicate one or more stack parameters of each, and the UE may segment capabilities based on the one or more stack parameters.

[0032] In various embodiments, the buffer occupancy may be one of low, medium, or high. In various embodiments, the data arrival may be one of low, medium, or high. In various embodiments, the latency requirement may be one of low requirement, fixed requirement, or no requirement. In various embodiments, the data type may be one of a combination of frequent data, urgent data, small data, medium data, high data, call, message (SMS), etc.

[0033] In addition, based on different combinations of one or more stack parameters, corresponding service classes may be determined. Table 1 shows service classes based on one or more stack parameters for a specific stack according to a non-limiting example:

Table 1

[0034] As shown in Table 1, the service class of a particular stack may be determined based on one or more stack parameters associated with the particular stack. Thus, the service class of the first stack and the service class of the second stack may be determined based on one or more stack parameters of each, such as SD1, SD2, HD1, HD2, call, etc. In step 304, a mode associated with the UE may be determined based on the respective service classes of the first stack and the second stack. In various embodiments, in the UE, the first stack and the second stack may have their respective service classes, wherein a combination of the service class of the first stack and the service class of the second stack may be provided. In various embodiments, a current combination of the respective service class of the first stack and the respective service class of the second stack may be determined. The current combination may define the respective service classes of the first stack and the second stack based on the services being used by the first stack and the second stack.

[0035] In addition, in various embodiments, the list of pre-stored service category combinations may be stored in a database, for example, a database accessible to the UE. In various embodiments, the list of pre-stored service category combinations may include multiple service combinations of corresponding service categories of the first stack and the second stack. In various embodiments, each of the multiple service combinations may be associated with a linking mode, wherein a specific service category combination may be associated with a linking mode, so that when a specific service category combination is identified, the UE can know the linking mode of the specific service category combination.

[0036] Furthermore, in various embodiments, a matching service class combination may be determined from a list of pre-stored service class combinations. The matching service class combination may match a determined combination of a corresponding service class of the first stack and a corresponding service class of the second stack.

[0037] Tables 2 and 3 show the linking patterns associated with various pre-stored service class combinations, as follows: Table 2

[0038] Table 3

[0039] As can be seen from Tables 2 and 3, if the service category of stack 1 is HD1 and the service category of stack 2 is HD2, the link mode can be 1. Similarly, if the service category of stack 1 is HD2 and the service category of stack 2 is call, the link mode can be 3. Therefore, a list of pre-stored service category combinations associated with various link modes can be provided. In addition, in various embodiments, the link mode associated with the matching service category combination can be accessed and the link mode is determined as the mode associated with the UE. For example, based on the service being used by the UE, the first stack can be associated with service category SD1, and stack 2 can be associated with service category call. In this case, based on the pre-stored service category combination, the mode of the UE can be determined as mode 2.

[0040] In various embodiments, the modes may define specific capabilities of the first stack and the second stack. For example, in mode 1, the first stack may have full capabilities, while the second stack may have capabilities specific to the service band and adjacent bands. In mode 2, both the first stack and the second stack may have capabilities specific to the service band and adjacent bands. In mode 3, the first stack may have full capabilities, while the second stack may only have frequency band support without carrier aggregation.

[0041] At step 306, corresponding frequency band information associated with the first stack and the second stack may be received from one or more network entities associated with a network. The network may be a network communicating with the UE. In addition, as described above, the one or more network entities may include a first entity communicating with the first stack and a second entity communicating with the second stack.

[0042] In various embodiments, for each of the first stack and the second stack, the UE may receive a corresponding system information block (SIB) from one or more network entities, for example, in a communication signal. In addition, the frequency band information may be extracted from the corresponding SIB to obtain the cell information. In particular, the frequency band information may include serving cell information and neighboring cell information for each of the first stack and the second stack.

[0043] At step 308, UE capabilities associated with the UE may be adjusted based on the mode and corresponding frequency band information associated with the first stack and the second stack. In various embodiments, a complete list of carrier aggregation (CA) / multiple radio access technology (RAT) dual connectivity (MRDC) capability combinations may be stored in a database, such as an internal or external database accessible to the UE. The UE may access the complete list of CA / MRDC capability combinations and may generate a corresponding subset combination list for each of the first stack and the second stack. Based on changes in frequency band information associated with the first stack and the second stack, such as changes in SIBs from one or more network entities, the corresponding subset combination lists of the first stack and the second stack may be updated.

[0044] At step 310, the adjusted UE capabilities may be transmitted to one or more network entities associated with the network. In various embodiments, the adjusted UE capabilities may be transmitted to one or more network entities of the network via a radio resource control (RRC) of the first stack and / or the second stack. In various embodiments, adjusting the UE capabilities may include segmenting the UE capabilities based on frequency band information. In various embodiments, the capabilities may be segmented based on frequency band into all capabilities, capabilities specific to the serving frequency band and the adjacent frequency band, and capabilities supported by the frequency band only without carrier aggregation (CA).

[0045] In various embodiments, the subset combination list may be hashed based on the frequency band information, and the subset combination list is shared by network entities associated with the first stack and the second stack. In various embodiments, the subset combination list may be updated for each carrier aggregation (CA) addition or removal of one of the first stack and the second stack.

[0046] Please refer to Figure 4A . Figure 4A is a flow chart illustrating an example method 400A of adjusting UE capabilities according to various embodiments. The method 400A may be performed by a UE.

[0047] At step 402, the UE accesses a complete list of carrier aggregation (CA) / multiple radio access technology (RAT) dual connectivity (MRDC) capability combinations associated with the DSDA UE from a database.

[0048] As described above, respective service classes associated with the first stack and the second stack and respective frequency band information associated with the first stack and the second stack are determined.

[0049] At step 404, a respective subset combination list of the first stack may be generated based on the respective service class associated with the first stack and the respective frequency band information associated with each of the first stack and the second stack.

[0050] Furthermore, at step 406, a corresponding subset combination list of the second stack may be generated based on the corresponding service class associated with the second stack and the corresponding frequency band information associated with each of the first stack and the second stack.

[0051] At step 408, a change in frequency band information associated with one of the first stack and the second stack is determined. In various embodiments, the change in frequency band information may be determined based on SIBs received from one or more network entities. In various embodiments, the change in frequency band information may occur when a secondary cell frequency band is added or removed.

[0052] At step 410, a corresponding subset combination list associated with one of the first stack and the second stack is updated based on the change in the frequency band information. For example, if the frequency band information of the first stack changes, the subset combination list associated with the first stack is updated.

[0053] At step 412, the updated corresponding subset combination list is accessed by the other stack of the first stack and the second stack. For example, if the frequency band information of the first stack changes, the subset combination list associated with the first stack is updated, and the subset combination list associated with the first stack is accessed by the second stack. Similarly, if the frequency band information of the second stack changes, the subset combination list associated with the second stack is updated, and the subset combination list associated with the second stack is accessed by the first stack.

[0054] In various embodiments, the subset combination list can be updated in the event that there is a change in the service associated with the first stack or the second stack. In this case, a change in the service class associated with one of the first stack and the second stack is determined. In addition, upon determining a change in the service class associated with one of the first stack and the second stack, a corresponding subset combination list associated with the first stack and a corresponding subset combination list associated with the second stack are updated based on frequency band information associated with the first stack and the second stack. In addition, the first stack and the second stack access the updated corresponding subset combination list associated with the first stack and the updated corresponding subset combination list associated with the second stack, respectively.

[0055] Please refer to Figure 4B . Figure 4B is a signal flow diagram illustrating an example process flow 400B for adjusting UE capabilities according to various embodiments. Fig.10 Explain the UE and its related functions and architecture in more detail.

[0056] At block 420, the UE accesses a complete list of CA / Multi-RAT Dual Connectivity (MRDC) capability combinations associated with the DSDA UE from the database. At blocks 422a and 422b, the first stack may be connected to a first frequency band (e.g., Band A) and the second stack may be connected to a second frequency band (e.g., Band B).

[0057] At 424, subset combination lists are determined for the first stack and the second stack. For the first stack, the subset combination list may be determined based on the service category of band A (serving cell) and band B (multiple SIM). For the second stack, the subset combination list may be determined based on the service category of band B (serving cell) and band A (multiple SIM).

[0058] At block 426, the first stack may add the secondary cell Scell ​​C and determine a change in the frequency band information associated with the first stack. At 428, a subset combination list associated with the first stack is updated based on the change in the frequency band information, and the updated corresponding subset combination list is accessed by the other stack of the first stack and the second stack.

[0059] At block 430, the second stack may add the secondary cell Scell ​​D and determine a change in the frequency band information associated with the second stack. At 432, a subset combination list associated with the second stack is updated based on the change in the frequency band information, and the updated corresponding subset combination list is accessed by the first stack.

[0060] At block 434, a change in the service class associated with one of the first stack and the second stack is determined. Based on the frequency band information associated with the first stack and the second stack, the subset combination list is updated at 436. For example, the subset combination list associated with the first stack is adjusted based on the serving cell of the first stack and the multiple SIMs of the first stack. In addition, the subset combination list associated with the second stack is adjusted based on the serving cell of the second stack and the multiple SIMs of the second stack, and the adjusted subset combination list is accessed by the UE.

[0061] Please refer to Figure 5A . Figure 5A 1 is a flow chart illustrating an example method 500A for adjusting UE capabilities according to various embodiments. The method 500A may be performed by a UE. In various embodiments, the addition of a single frequency band may be notified to the network and updated for each carrier aggregation addition or removal of both the first stack and the second stack. In this case, the size of the message may be reduced.

[0062] At step 502, a complete list of carrier aggregation (CA) / multiple radio access technology (RAT) dual connectivity (MRDC) capability combinations associated with the DSDA UE is accessed by the UE from a database.

[0063] As described above, respective service classes associated with the first stack and the second stack and respective frequency band information associated with the first stack and the second stack are determined.

[0064] At step 504, a corresponding frequency band list for the first stack may be generated based on the corresponding service class associated with the first stack and the corresponding frequency band information associated with each of the first stack and the second stack. In various embodiments, the frequency band list associated with the first stack may include one or more suggested frequency bands for establishing a connection with the first stack.

[0065] At step 506, a corresponding frequency band list for the second stack may be generated based on the corresponding service class associated with the second stack and the corresponding frequency band information associated with each of the first stack and the second stack. In various embodiments, the frequency band list associated with the second stack may include one or more suggested frequency bands for establishing a connection with the second stack.

[0066] At step 508, a change in frequency band information associated with one of the first stack and the second stack is determined. In various embodiments, the change in frequency band information may be identified when the first stack and / or the second stack adds a secondary cell. In various embodiments, the change in frequency band information may be identified when the first stack and / or the second stack discards a secondary cell. In various embodiments, the change in frequency band information may be identified when the first stack and / or the second stack is using a high priority service.

[0067] At step 510, based on the change in the frequency band information, a corresponding frequency band list associated with the first stack and a corresponding frequency band list associated with the second stack are updated.

[0068] At step 512, the updated corresponding frequency band list associated with the first stack and the corresponding frequency band list associated with the second stack are accessed by the first stack and the second stack, respectively. In various embodiments, if the first stack has a higher carrier aggregation than required based on the service being used by the first stack, the carrier aggregation bands may be made available to the second stack. In addition, if the second stack requests to add carrier aggregation bands, the carrier aggregation band(s) may be dropped from the first stack and added to the second stack.

[0069] Please refer to Figure 5B . Figure 5B is a signal flow diagram illustrating an example process 500B for adjusting UE capabilities according to various embodiments. Fig.10 Explain the UE and its related functions and architecture in more detail.

[0070] At block 520, the UE accesses a complete list of CA / Multi-RAT Dual Connectivity (MRDC) capability combinations associated with the DSDA UE from a database.

[0071] At blocks 522a and 522b, the first stack may be connected to a first frequency band, such as frequency band A, and the second stack may be connected to a second stack, such as frequency band B.

[0072] At 524a and 524b, corresponding frequency band lists of the first stack and the second stack are generated based on the corresponding service categories associated with the first stack and the second stack. For example, for the first stack, the frequency band list can be generated based on the services of frequency band A (serving cell) and frequency band B (MSIM). Similarly, for the second stack, the frequency band list can be generated based on the services of frequency band B (serving cell) and frequency band A (MSIM). In various embodiments, the frequency band list can have a one-band depth combination.

[0073] At block 526 , the first stack may add secondary cells Scell ​​bands B and C.

[0074] At 528, the band lists are updated for both the first stack and the second stack. That is, the corresponding band list of the first stack is updated with Band C (serving cell), and the corresponding band list of the second stack is updated with Band C (MSIM).

[0075] At block 530, the second stack may add the secondary cell Scell ​​band D. At 532, the band lists are updated for both the first stack and the second stack. That is, the corresponding band list of the first stack is updated with band D (MSIM), and the corresponding band list of the second stack is updated with band D (serving cell).

[0076] At block 534, a change in the service class associated with one of the first stack and the second stack is determined. Based on the frequency band information associated with the first stack and the second stack, the frequency band list is updated at 536. For example, the frequency band list associated with the first stack is adjusted based on the serving cells of the first stack (frequency bands A and C) and the frequency bands B and D associated with the second stack. Similarly, the frequency band list associated with the second stack is adjusted based on the serving cells of the second stack (frequency bands B and D) and the frequency bands A and C associated with the first stack. The UE can then access the adjusted frequency band list.

[0077] Please refer to Fig. 6A . Fig. 6A 6 is a flow chart illustrating an example method 600A for adjusting UE capabilities according to various embodiments. The method 600A may be performed by the UE. In various embodiments, if one of the first stack and the second stack has a higher carrier aggregation than required based on the service being used, the carrier aggregation band may be considered available, and further, if the other stack of the first stack and the second stack requests carrier aggregation, the specific carrier aggregation band may be discarded and provided to the other stack of the first stack and the second stack.

[0078] At step 602, the UE accesses a complete list of carrier aggregation (CA) / multiple radio access technology (RAT) dual connectivity (MRDC) capability combinations associated with the DSDA UE from a database.

[0079] As described above, respective service classes associated with the first stack and the second stack and respective frequency band information associated with the first stack and the second stack are determined.

[0080] At step 604, a corresponding frequency band list of a first stack associated with the first frequency band and a second stack associated with the second frequency band may be generated based on the complete list of CA / MRDC combinations. In various embodiments, the corresponding frequency band list of the first stack and the second stack is generated based on a priority of a service associated with the first frequency band and a priority of a service associated with the second frequency band.

[0081] At step 606, it is determined whether the first stack is associated with a high priority service and whether the first stack has established a connection with the second frequency band. When it is determined that the first stack is associated with a high priority service and the first stack has established a connection with the second frequency band, the method proceeds to steps 608-612.

[0082] At step 608, the second stack is caused to drop the second frequency band.

[0083] At step 610, a corresponding frequency band list associated with the first stack and a corresponding frequency band list associated with the second stack are updated based on the discarding of the second frequency band.

[0084] Furthermore, at step 612, the UE accesses, through the first stack and the second stack, an updated corresponding frequency band list associated with the first stack and a corresponding frequency band list associated with the second stack.

[0085] Please refer to Figure 6B . Figure 6B 600B is a signal flow diagram illustrating an example process flow 600B for adjusting UE capabilities according to various embodiments. Fig.10 Explain the UE and its related functions and architecture in more detail.

[0086] At block 620, the UE accesses a complete list of CA / Multi-RAT Dual Connectivity (MRDC) capability combinations associated with the DSDA UE from the database. At blocks 622a and 622b, the first stack may be connected to the first frequency band (ie, Band A) and the second stack may be connected to the second stack (ie, Band B).

[0087] At 624a and 624b, corresponding frequency band lists of the first stack and the second stack are generated based on the corresponding service categories associated with the first stack and the second stack. For example, for the first stack, the frequency band list can be generated based on the service priority of frequency band A (serving cell) and frequency band B (MSIM). Similarly, for the second stack, the frequency band list can be generated based on the service priority of frequency band B (serving cell) and frequency band A (MSIM). In various embodiments, the frequency band list can have a 1-frequency band depth combination.

[0088] At block 626, the first stack may add the secondary cells Scell ​​bands B and C. In addition, the first stack may have a high priority service.

[0089] At block 628, the second stack may drop the Scell ​​(if such dropping is required to support Band B and Band C).

[0090] At 630, the band lists are updated for both the first stack and the second stack. That is, the corresponding band list of the first stack is updated with Band C (serving cell), and the corresponding band list of the second stack is updated with Band C (MSIM).

[0091] At block 632 , the second stack may add a secondary cell Scell ​​D.

[0092] At 634, the band lists are updated for both the first stack and the second stack. That is, the corresponding band list of the first stack is updated with band D (MSIM), and the corresponding band list of the second stack is updated with band D (serving cell).

[0093] At block 636, a change in the service class associated with one of the first stack and the second stack is determined. Based on the frequency band information associated with the first stack and the second stack, the frequency band list is updated at 638. For example, the frequency band list associated with the first stack is adjusted based on the serving cells of the first stack (frequency bands A and C) and the frequency bands B and D associated with the second stack. Similarly, the frequency band list associated with the second stack is adjusted based on the serving cells of the second stack (frequency bands B and D) and the frequency bands A and C associated with the first stack. The UE can then access the adjusted frequency band list.

[0094] In various embodiments, the first stack may be associated with a first transmit power and the second stack may be associated with a second transmit power. The DSDA UE may be associated with a total transmit power that is the sum of the first transmit power and the second transmit power. Similar to the ULCA / SVTE scenario, the transmit power may be shared. In various embodiments, the transmit power may be shared between the first stack and the second stack based on the services being used. In various embodiments, full carrier aggregation combinations may be generated and considered on a simultaneously allowed list. For example, if the hardware does not simultaneously allow the MID band + MID band MSIM combination, the MID band + MID band MSIM combination may be restricted. Priority will be given based on the service to withstand the highest carrier aggregation combination.

[0095] Please refer to Figure 7 . Figure 7 is a flow chart illustrating an example method 700 of sharing transmit power between a first stack and a second stack in accordance with various embodiments.

[0096] At step 702, it is determined whether the priority service is associated with one of the first stack and the second stack. As described above, the total power may be the sum of the first transmit power and the second transmit power. If the priority service is not running, the method may move to step 704, where the total power is still the sum of the first transmit power and the second transmit power.

[0097] At step 706, it is determined whether the priority service is running in the first stack. After determining that the priority service is associated with the first stack, at step 708, the first transmit power may be increased by a first value and the second transmit power may be decreased by a second value.

[0098] In step 710, after determining that the priority service is associated with the second stack (eg, the priority service is not running in the first stack), the second transmit power may be increased by a first value, and the first transmit power may be decreased by a second value. The total transmit power may still be the sum of the first transmit power and the second transmit power.

[0099] In various embodiments, the UE may not support the R18 MuSIM feature. In this case, similar UE capability segmentation may be provided, i.e., when the ongoing service in the stack that needs to be disconnected is not a low-latency required service and / or is not a voice call, the stack may choose to trigger a Tracking Area Update (TAU). In various embodiments, criteria may be defined based on the type of service that may trigger a TAU update. In addition, any Dual SIM Dual Standby (DSDS) device (e.g., a pre-R18 device) may have a shared stack for two SIMs and work simultaneously by segmenting the capabilities and indicating them to the network. As a result, hardware costs may be reduced.

[0100] Please refer to Fig. 8A and Figure 8B . Fig. 8A and 8B is a flow chart illustrating example methods 800 and 820 associated with updating UE capabilities of a device that does not support the R18 MuSIM feature according to various embodiments.

[0101] like Fig. 8A As shown, in step 802, it is determined whether both the first stack and the second stack are in the connection mode and whether the RRC connection is released in one of the first stack and the second stack.

[0102] At step 804, it is determined whether predefined criteria for sending updated UE capabilities are met. If the criteria are met, at step 806, the stack may leave connected mode when the criteria are met. At step 808, a TAU may be triggered by a UE capability change indication. At step 810, the UE capabilities are updated to the network.

[0103] like Figure 8BAs shown, at step 822, it is determined whether the first stack has moved to the connected mode. At step 824, it is determined whether the second stack is in the connected mode. If the second stack is not in the connected mode, then at step 826, the RRC state of the second stack may be monitored.

[0104] In addition, in the case where the second stack is in connected mode, at step 828, it is determined whether the predefined criteria for sending updated UE capabilities are met. If the criteria are not met, then at step 830, the activity of the stack can continue to be monitored in connected mode. In the case where the criteria are met, at step 832, the stack can leave connected mode when the criteria are met. At step 834, a TAU can be triggered by a UE capability change indication. At step 836, the UE capabilities are updated to the network.

[0105] Fig. 9 is a block diagram illustrating an example configuration of a network entity 900 according to various embodiments. Fig. 9 The network entity shown in can communicate with a DSDA UE, for example, for sharing UE capability information. The network entity 900 can be associated with an LTE, NR SA, or NSA network. The network entity 900 may include at least one processor (e.g., including a processing circuit) 902, a memory 904 (e.g., a storage device), and a communication unit (e.g., including a communication circuit) 906 (e.g., a communicator or a communication interface). The communication unit 906 may perform one or more functions for sending and receiving signals through a wireless channel.

[0106] For example, the processor 902 may be a single processing unit or multiple units, all of which may include multiple computing units. The processor 902 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuits, and / or any device that manipulates signals based on operating instructions. In addition to other capabilities, the processor 802 is also configured to obtain and execute computer-readable instructions and data stored in the memory. The processor 902 may include one or more processors. At this point, one or more processors 902 may be a general-purpose processor, such as a central processing unit (CPU), an application processor (AP), etc., or a pure graphics processing unit, such as a graphics processing unit (GPU), a visual processing unit (VPU), and / or an AI-specific processor, such as a neural processing unit (NPU). One or more processors 802 may control the processing of input data according to predefined operating rules or artificial intelligence (AI) models stored in non-volatile memory and volatile memory (e.g., memory unit 904). The predefined operating rules or artificial intelligence models are provided by training or learning.

[0107] The memory 904 may include, but is not limited to, non-transitory computer-readable storage media, such as volatile memory, such as static random access memory (SRAM) and dynamic random access memory (DRAM), and / or non-volatile memory, such as read-only memory (ROM), erasable programmable ROM, flash memory, hard disk, optical disk, and magnetic tape.

[0108] In one example, the memory 904 may include a cache or random access memory for the processor 902. In various embodiments, the memory 904 may include one or more modules, which include a set of instructions, and the execution of these instructions may enable the network entity 900 to perform any one or more methods / processes disclosed herein. One or more modules may be configured to perform the steps of the present disclosure. In an embodiment, each of the one or more modules may be a hardware unit located outside the memory 904. Hereinafter, it will be understood that the term including "module" may correspond to a unit for processing and performing at least one function or operation, or a method step discussed throughout the present disclosure. In addition, the "module" may be implemented by hardware, software, or a combination of hardware and software.

[0109] In various embodiments, the memory 904 may be communicatively coupled to at least one processor (or controller) 902. The memory 904 may be configured to store data and instructions executable by at least one processor 902. In an embodiment, the memory 904 may communicate via a bus within the network entity 900. The functions, behaviors, or tasks shown or described in the figures may be performed by programming the processor 902 to run the instructions stored in the memory 904. These functions, behaviors, or tasks are independent of a specific type of instruction set, storage medium, processor, or processing strategy, and may be performed by software, hardware, integrated circuits, firmware, microcode, etc., alone or in combination. Likewise, processing strategies may include multi-processing, multi-tasking, parallel processing, etc.

[0110] Fig.10 is a block diagram illustrating an example configuration of a user equipment (UE) according to various embodiments. Fig.10 The UE shown in FIG. 1 may be configured to perform or may include performing the above Figure 2 A system or electronic device that describes in detail functions and methods related to the UE to FIG8 .

[0111] Reference Fig.10, UE 1000 may include at least one processor (e.g., including processing circuitry) 1002, a communication unit (e.g., including communication circuitry) 1006 (e.g., a communicator or communication interface), a memory 1004 (e.g., a storage device), a first stack 1008, and a second stack 1010. For example, UE 1000 may be a user equipment, such as a cellular phone or other device that communicates through multiple cellular networks (e.g., 3G, 4G, 5G or pre-5G, 6G networks, or any future wireless communication networks). The communication unit 1006 may include various communication circuits and perform the functions of sending and receiving signals through wireless channels. The first stack 1008 and the second stack 1010 may have functions related to Figure 2 Similar functionality as described in detail in FIG8 .

[0112] For example, processor 1002 may be a single processing unit or multiple units, all of which may include multiple computing units. Processor 1002 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuits, and / or any device that manipulates signals based on operating instructions. Among other capabilities, processor 1002 is configured to acquire and execute computer-readable instructions and data stored in memory. Processor 1002 may include one or more processors. At this point, one or more processors 1002 may be general-purpose processors, such as central processing units (CPUs), application processors (APs), etc., or may be pure graphics processing units, such as graphics processing units (GPUs), visual processing units (VPUs), and / or AI-specific processors, such as neural processing units (NPUs). One or more processors 902 may control the processing of input data according to predefined operating rules or artificial intelligence (AI) models stored in non-volatile memory and volatile memory (e.g., memory 1004). Predefined operating rules or artificial intelligence models are provided by training or learning.

[0113] The memory 1004 may include, but is not limited to, non-transitory computer-readable storage media, such as volatile memory, such as static random access memory (SRAM) and dynamic random access memory (DRAM), and / or non-volatile memory, such as read-only memory (ROM), erasable programmable ROM, flash memory, hard disk, optical disk, and magnetic tape.

[0114] In one example, the memory 1004 may include a cache or random access memory for the processor 1002. In various embodiments, the memory 1004 may include one or more modules, which include a set of instructions, and the execution of these instructions may enable the UE 1000 to perform any one or more methods / processes disclosed herein. As discussed herein, one or more modules may be configured to perform the steps of the present disclosure. In an embodiment, each of the one or more modules may be a hardware unit located outside the memory 1004. Hereinafter, it will be understood that the term including "module" may correspond to a unit for processing and performing at least one function or operation, or a method step discussed throughout the present disclosure. In addition, the "module" may be implemented by hardware, software, or a combination of hardware and software.

[0115] In various embodiments, the memory 1004 may be communicatively coupled to at least one processor (or controller) 1002. The memory 1004 may be configured to store data and instructions executable by at least one processor 1002. In an embodiment, the memory 1004 may communicate via a bus within the UE 1000. The functions, behaviors, or tasks shown or described in the figures may be performed by programming the processor 1002 to run the instructions stored in the memory 1004. These functions, behaviors, or tasks are independent of a particular type of instruction set, storage medium, processor, or processing strategy, and may be performed by software, hardware, integrated circuits, firmware, microcode, etc., alone or in combination. Likewise, processing strategies may include multi-processing, multi-tasking, parallel processing, etc.

[0116] Fig.11 is a diagram showing an example implementation and hardware configuration of the DSDA UE in the foregoing figures by a computer system according to various embodiments. The computer system may include a set of instructions that can be executed to cause the computer system to perform any one or more of the disclosed methods. The computer system may operate as a standalone device or may be connected to other computer systems or peripheral devices, for example, using a network.

[0117] In a network deployment, the computer system may operate in the capacity of a server, or as a client-user computer in a server-client user network environment, or as a peer computer system in a peer-to-peer (or distributed) network environment. The computer system may also be implemented as or integrated on a variety of devices, such as a personal computer (PC), a tablet computer, a personal digital assistant (PDA), a mobile device, a handheld computer, a laptop computer, a desktop computer, a communication device, a wireless phone, a landline phone, a network appliance, a network router, a switch or a bridge, or any other machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by the machine. In addition, although a single computer system is shown in the drawings, the term "system" should also be construed to include any collection of systems or subsystems that can individually or jointly execute one or more sets of instructions to perform one or more computer functions.

[0118] The computer system may include a processor (e.g., including a processing circuit) 1102, such as a central processing unit (CPU), a graphics processing unit (GPU), or both. The processor 1102 may be a component in a variety of systems. For example, the processor 1102 may be part of a standard personal computer or workstation. The processor 1102 may be one or more general-purpose processors, digital signal processors, application-specific integrated circuits, field programmable gate arrays, servers, networks, digital circuits, analog circuits, combinations thereof, or other devices now known or later developed for analyzing and processing data. The processor 1102 may implement a software program, such as manually generated code (e.g., programming).

[0119] In various embodiments, the processor 1102 may execute the decision making entity and the RF module to update the UE capabilities. Fig.12 , the decision entity may be configured to communicate with the first stack, the second stack, and the RF module. The first stack and the second stack may indicate one or more stack parameters to the decision entity, such as buffer occupancy, data arrival amount, latency details, frequency band information, etc. In various embodiments, when the connection is just established, the lower layer may not have all the details about the stack parameters. In this case, available data may be shared with the entity, for example, the service for which the connection is triggered, because the upper layer will understand the service based on the slice / service being used by the user equipment. Based on the received details, the decision entity may be configured to decide the segmentation mode and share the mode and frequency band details with the RF module. The RF module may be configured to segment the data based on the mode and frequency band details and share the updated capabilities with the RRC of the respective stack.

[0120] The computer system may include a memory 1104, such as a memory that can communicate via a bus. The memory 1104 may include, but is not limited to, computer-readable storage media, such as various types of volatile and non-volatile storage media, including but not limited to random access memory, read-only memory, programmable read-only memory, electrically programmable read-only memory, electrically erasable read-only memory, flash memory, tape or disk, optical media, etc. In one example, the memory includes a cache or random access memory for a processor. In various examples, the memory is separate from the processor, such as a cache memory of the processor, a system memory, or other memory. The memory 1104 may be an external storage device or a database for storing data. The memory 1104 is operable to store instructions executable by the processor. The functions, behaviors, or tasks shown or described in the figures may be performed by a programmed processor to run the instructions stored in the memory. These functions, behaviors, or tasks are independent of a particular type of instruction set, storage medium, processor, or processing strategy, and may be performed by software, hardware, integrated circuits, firmware, microcode, etc., alone or in combination. Similarly, processing strategies may include multi-processing, multi-tasking, parallel processing, etc.

[0121] As shown in the figure, the computer system may further include or may not include a display 1106, such as a liquid crystal display (LCD), an organic light emitting diode (OLED), a flat panel display, a solid state display, a cathode ray tube (CRT), a projector, a printer, or other display devices known now or developed later for outputting certain information. The display can be used as an interface for a user to view the operation of the processor, or specifically as an interface with software stored in a memory or a drive unit.

[0122] In addition, the computer system may also include an input device (e.g., including various input circuits) 1108, which is configured to allow a user to interact with any component of the system. The computer system may also include a disk or optical drive unit 1110. The disk drive unit may include a computer-readable medium in which one or more sets of instructions, such as software, may be embedded. In addition, these instructions may embody one or more methods or logics described. In a specific example, during execution of the computer system, the instructions may reside completely or at least partially in the memory or processor.

[0123] The present disclosure contemplates a computer-readable medium that includes instructions or receives and executes instructions in response to a propagation signal, thereby enabling a device connected to a network to transmit voice, video, audio, image, or any other data through the network. In addition, instructions can be sent or received on the network through a communication port or interface (e.g., including various communication circuits) 1112 or using a bus. The communication port or interface can be part of the processor or a separate component. The communication port can be created in software or can be a physical connection in hardware. The communication port can be configured to connect to a network, external media, a display, or any other component in the system, or a combination thereof. The connection to the network can be a physical connection, such as a wired Ethernet connection, or can be a wireless connection as discussed later. Similarly, additional connections to other components of the system can be physical connections or can be established wirelessly. Alternatively, the network can be directly connected to the bus.

[0124] The network may include a wired network, a wireless network, an Ethernet AVB network, or a combination thereof. The wireless network may be a cellular telephone network, an 802.11, 802.16, 802.20, 802.1Q, or WiMax network. In addition, the network 826 may be a public network (e.g., the Internet), a private network (e.g., an intranet), or a combination thereof, and may utilize various existing or later developed network protocols, including but not limited to TCP / IP-based network protocols. The system is not limited to operation using any particular standard and protocol. For example, standards for Internet and other packet-switched network transmissions (e.g., TCP / IP, UDP / IP, HTML, and HTTP) may be used.

[0125] Therefore, a mechanism is defined to split and share UE capabilities for both stacks when both stacks are connected to the network at the same time. In current devices on the market, if a device is DSDA, then the device will have 2 separate RF stacks to support the 2 protocol stacks independently. With the introduction of R18 MuSIM WI, separate stacks are no longer required and devices with a shared RF entity can also act as DSDA devices, so a mechanism must be defined to split capabilities.

[0126] In the present disclosure, service information is derived based on buffer occupancy, data arrival, latency and band information of both stacks to partition RF capabilities between the stacks. Thus, a method is described to partition UE capabilities based on ongoing services and cell / band information derived from both stacks.

[0127] In addition, the present disclosure may be used in any order and in any combination. Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those commonly understood by those of ordinary skill in the art to which the present disclosure belongs. The systems, methods, and examples provided herein are illustrative only and are not limiting.

[0128] Although the present disclosure has been illustrated and described with reference to various exemplary embodiments, it will be understood that the various exemplary embodiments are intended to be illustrative rather than limiting. Those skilled in the art will further understand that various changes in form and details may be made without departing from the true spirit and full scope of the present disclosure (including the appended claims and their equivalents). In addition, it should be understood that any embodiment described herein may be used in combination with any other embodiment described herein.

Claims

1. A method (300) for transmitting Dual Subscriber Identity Module (SIM) Dual Activated (DSDA) User Equipment (DSDA) UE capabilities by an electronic device, the method comprising: determining (302) a respective service class for each of a first stack and a second stack of the DSDA UE based on at least one stack parameter, wherein the at least one stack parameter is indicated by each of the first stack and the second stack; determining (304) a mode associated with the DSDA UE based on respective service classes of the first stack and the second stack; receiving (306) respective frequency band information associated with the first stack and the second stack from at least one network entity, wherein the at least one network entity is associated with a network in communication with the DSDA UE; adjusting (308) the UE capabilities associated with the DSDA UE based on the mode and the respective frequency band information associated with the first stack and the second stack; as well as The adjusted UE capabilities are transmitted (310) to the at least one network entity.

2. The method (300) according to claim 1, wherein: Adjusting the UE capability includes: Access a complete list of CA / RAT dual connectivity MRDC capability combinations associated with the DSDA UE; generating a corresponding subset combination list for each of the first stack and the second stack; and The respective subset combination lists are updated based on changes in frequency band information associated with the first stack and the second stack.

3. The method (300) according to claim 1, wherein: Adjusting the UE capability includes: Accessing (402) a complete list of carrier aggregation CA / multiple radio access technology RAT dual connectivity MRDC capability combinations associated with the DSDA UE, wherein the complete list of CA / MRDC capability combinations is stored in a database; Based on the complete list of CA / MRDC capability combinations, generating (404) a list of respective subset combinations of the first stack based on respective service classes associated with the first stack and respective frequency band information associated with each of the first stack and the second stack; Based on the complete list of CA / MRDC capability combinations, generating (406) a list of respective subset combinations of the second stack based on respective service classes associated with the second stack and respective frequency band information associated with each of the first stack and the second stack; determining (408) a change in frequency band information associated with one of the first stack and the second stack; Based on the change in the frequency band information, updating (410) a corresponding subset combination list associated with one of the first stack and the second stack; and The updated corresponding subset combination list is accessed ( 412 ) by the other of the first stack and the second stack.

4. The method (300) according to claim 3, comprising: determining a change in a class of service associated with one of the first stack and the second stack; Based on determining a change in a service class associated with one of the first stack and the second stack, updating a corresponding subset combination list associated with the first stack and a corresponding subset combination list associated with the second stack based on frequency band information associated with the first stack and the second stack; as well as An updated respective subset combination list associated with the first stack and an updated respective subset combination list associated with the second stack are accessed by the first stack and the second stack.

5. The method (300) of claim 1, wherein: Adjusting the UE capability includes: Accessing (502) a complete list of carrier aggregation CA / multiple radio access technology RAT dual connectivity MRDC capability combinations associated with the DSDA UE, wherein the complete list of CA / MRDC capability combinations is stored in a database; generating (504) a corresponding frequency band list for the first stack based on the complete list of CA / MRDC capability combinations and based on a corresponding service class associated with the first stack and corresponding frequency band information associated with each of the first stack and the second stack, wherein the frequency band list associated with the first stack includes at least one suggested frequency band for establishing a connection with the first stack; generating (506) a corresponding frequency band list for the second stack based on the complete list of CA / MRDC capability combinations and based on a corresponding service class associated with the second stack and corresponding frequency band information associated with each of the first stack and the second stack, wherein the frequency band list associated with the second stack includes at least one suggested frequency band for establishing a connection with the second stack; determining (508) a change in frequency band information associated with one of the first stack and the second stack; Based on the change in the frequency band information, updating (510) a corresponding frequency band list associated with the first stack and a corresponding frequency band list associated with the second stack; and The updated corresponding frequency band list associated with the first stack and the corresponding frequency band list associated with the second stack are accessed (512) by the first stack and the second stack, respectively.

6. The method (300) of claim 1, wherein: Adjusting the UE capability includes: Accessing (602) a complete list of carrier aggregation CA / multiple radio access technology RAT dual connectivity MRDC capability combinations associated with the DSDA UE, wherein the complete list of CA / MRDC capability combinations is stored in a database; generating (604) a respective frequency band list of the first stack associated with a first frequency band and the second stack associated with a second frequency band based on the complete list of CA / MRDC capability combinations, wherein the respective frequency band list of the first stack and the second stack is generated based on a priority of a service associated with the first frequency band and a priority of a service associated with the second frequency band; determining (606) whether the first stack is associated with a high priority service and whether the first stack has established a connection with the second frequency band; and When it is determined that the first stack is associated with a high priority service and the first stack has established a connection with the second frequency band, performing the following operations: causing (608) the second stack to discard the second frequency band; Based on the discarding of the second frequency band, updating (610) a corresponding frequency band list associated with the first stack and a corresponding frequency band list associated with the second stack; and The updated respective frequency band list associated with the first stack and the respective frequency band list associated with the second stack are accessed (612) by the first stack and the second stack.

7. The method (300) of claim 1, wherein: The at least one stack parameter includes at least one of buffer occupancy, data arrival volume, latency details, and data type.

8. The method (300) of claim 1, wherein: Determining the mode includes: determining a current combination of a corresponding service class of the first stack and a corresponding service class of the second stack; accessing a pre-stored list of service class combinations, the pre-stored list of service class combinations comprising a plurality of service combinations of respective service classes of the first stack and the second stack, wherein each service combination of the plurality of service combinations is associated with a linking mode; identifying, from the pre-stored list of service class combinations, a matching service class combination that matches the determined current combination of the corresponding service class of the first stack and the corresponding service class of the second stack; accessing the linking mode associated with the matching service class combination; and The linked mode is determined to be a mode associated with the DSDA UE.

9. The method (300) according to claim 1, wherein: Receiving the corresponding frequency band information includes: for each of the first stack and the second stack, receiving a corresponding system information block SIB from the at least one network entity, and The frequency band information is extracted from the corresponding SIB, wherein the corresponding frequency band information includes serving cell information and neighboring cell information.

10. The method (300) according to claim 1, wherein: The first stack is associated with a first transmit power, the second stack is associated with a second transmit power, and the DSDA UE is associated with a total transmit power corresponding to a sum of the first transmit power and the second transmit power, and wherein the method comprises: determining (702) whether a priority service is associated with one of the first stack and the second stack; upon determining that the priority service is associated with the first stack, increasing (708) the first transmit power by a first value and decreasing the second transmit power by a second value, and Upon determining that the priority service is associated with the second stack, the second transmit power is increased (710) by the first value and the first transmit power is decreased by the second value, wherein the total transmit power remains the sum of the first transmit power and the second transmit power.

11. An electronic device, the electronic device being configured to transmit user equipment UE capabilities of a dual subscriber identity module SIM dual activated DSDA user equipment DSDA UE, the electronic device comprising: First Stack (1008); Second stack (1010); as well as At least one processor (1002), the at least one processor (1002) being configured to: determining a respective service class for each of the first stack (1008) and the second stack (1010) based on at least one stack parameter, wherein the at least one stack parameter is indicated by each of the first stack (1008) and the second stack (1010); determining a mode associated with the DSDA UE (1000) based on respective service classes of the first stack (1008) and the second stack (1010); receiving respective frequency band information associated with the first stack (1008) and the second stack (1010) from at least one network entity, wherein the at least one network entity is associated with a network in communication with the DSDA UE (1000); adjusting UE capabilities associated with the DSDA UE (1000) based on the mode and respective frequency band information associated with the first stack (1008) and the second stack (1010); and The adjusted UE capabilities are sent to at least one network entity associated with the network.

12. The electronic device according to claim 11, wherein: To adjust the UE capabilities, the at least one processor (1002) is configured to: Accessing a complete list of carrier aggregation CA / multiple radio access technology RAT dual connectivity MRDC capability combinations associated with the DSDA UE (1000); generating a corresponding subset combination list for each of the first stack and the second stack; and The respective subset combination lists are updated based on changes in frequency band information associated with the first stack (1008) and the second stack (1010).

13. The electronic device according to claim 11, wherein: To adjust the UE capabilities, the at least one processor (1002) is configured to: Accessing a complete list of carrier aggregation CA / multiple radio access technology RAT dual connectivity MRDC capability combinations associated with the DSDA UE, wherein the complete list of CA / MRDC capability combinations is stored in a database; generating, based on the complete list of CA / MRDC capability combinations, a list of respective subset combinations of the first stack (1008) based on respective service classes associated with the first stack (1008) and respective frequency band information associated with each of the first stack (1008) and the second stack (1010); generating, based on the complete list of CA / MRDC capability combinations, a list of respective subset combinations of the second stack (1010) based on respective service classes associated with the second stack (1010) and respective frequency band information associated with each of the first stack (1008) and the second stack (1010); determining a change in frequency band information associated with one of the first stack and the second stack (1010); updating a corresponding subset combination list associated with one of the first stack (1008) and the second stack (1010) based on the change in the frequency band information; and The updated corresponding subset combination list is accessed through the other of the first stack (1008) and the second stack (1010).

14. The electronic device according to claim 13, wherein: The at least one processor is configured to: determining a change in a class of service associated with one of the first stack (1008) and the second stack (1010); Upon determining a change in a service class associated with one of the first stack (1008) and the second stack (1010), updating a corresponding subset combination list associated with the first stack (1008) and a corresponding subset combination list associated with the second stack (1010) based on frequency band information associated with the first stack (1008) and the second stack (1010); and An updated respective subset combination list associated with the first stack (1008) and an updated respective subset combination list associated with the second stack (1010) are accessed by the first stack (1008) and the second stack (1010).

15. The electronic device according to claim 11, wherein: The at least one processor is configured to perform the method of any one of claims 5-10.

Images