Method, device and computer storage medium for communication
By introducing timer and TDM modes into the terminal equipment, the performance problems of multiple USIM terminal equipment when switching between networks are solved, ensuring the stability of network performance and the smooth progress of data transmission.
Patent Information
- Application Number
- CN202080097767.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2020-03-02
- Publication Date
- 2024-11-01
- Estimated Expiration
- 2040-03-02
AI Technical Summary
When existing multiple USIM terminal devices switch between networks, they fail to effectively notify the first network, resulting in incorrect network performance records and affecting the performance of the equipment.
The timer and TDM mode are introduced in the terminal device to ensure stability of network performance by sending a conversion request to the first network device and maintaining a connected state during the conversion to avoid interrupting emergency services.
By notifying network conversion, incorrect performance records are avoided, the performance of terminal devices is enhanced, and data transmission during network conversion is ensured smoothly.
Smart Images

Figure CN115191131B_ABST
Abstract
Description
Technical Field
[0001] Embodiments of the present disclosure relate generally to the field of telecommunications, and more particularly to methods, devices, and computer storage media for communicating during transitions between communication networks. Background Art
[0002] Currently, multi-Universal Subscriber Identity Module (USIM) terminal devices occupy a large market share. Two USIM cards can comply with the same or different communication standards, such as Long Term Evolution (LTE), New Radio (NR), etc., and the radio frequency (RF) capability of the terminal device can be 1 transmit port (Tx) / 1 receive port (Rx), 1Tx / 2Rx, 2Tx / 2Rx, etc. However, no specification enhancements have been made to improve the performance of multi-USIM terminal devices.
[0003] Assume that a multi-USIM terminal device with a single Tx is registered to more than one network, for example, a network of USIM A (hereinafter also referred to as the first network) and a network of USIM B (hereinafter also referred to as the second network), and the terminal device has established a connection in the first network, but remains idle or inactive in the second network. Currently, when the terminal device needs to perform data transmission in the second network, the terminal device simply releases the connection with the first network without notifying the first network. In this case, the first network regards the terminal device as a connection failure, which results in incorrect network performance records. Therefore, the performance of the multi-USIM terminal device cannot be guaranteed. Summary of the invention
[0004] Generally speaking, embodiments of the present disclosure provide methods, devices, and computer storage media for communications.
[0005] In a first aspect, a method for communication is provided. The method comprises: determining at a terminal device whether to perform a switch from a first network device of a first communication network to a second network device of a second communication network, the first communication network and the second communication network being associated with a first identifier and a second identifier of the terminal device, respectively; and in response to determining that the switch is to be performed, sending a request for switching from the first network device to the second network device to the first network device.
[0006] In a second aspect, a method for communication is provided. The method comprises: receiving, at a first network device of a first communication network, from a terminal device, a request for handover from the first network device to a second network device of a second communication network, the first communication network and the second communication network being associated with a first identifier and a second identifier of the terminal device, respectively.
[0007] In a third aspect, a terminal device is provided. The terminal device includes a processor and a memory coupled to the processor. The memory stores instructions, which, when executed by the processor, cause the terminal device to perform the method according to the first aspect of the present disclosure.
[0008] In a fourth aspect, a network device is provided. The network device includes a processor and a memory coupled to the processor. The memory stores instructions, which, when executed by the processor, cause the network device to perform the method according to the second aspect of the present disclosure.
[0009] In a fifth aspect, a computer readable medium is provided, on which instructions are stored, wherein when the instructions are executed on at least one processor, the at least one processor is caused to execute the method according to the first aspect of the present disclosure.
[0010] In a sixth aspect, a computer readable medium is provided, on which instructions are stored, wherein when the instructions are executed on at least one processor, the at least one processor executes the method according to the second aspect of the present disclosure.
[0011] Other features of the present disclosure will become readily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS
[0012] The above and other objects, features and advantageous effects of the present disclosure will become more apparent through a more detailed description of some embodiments of the present disclosure in the accompanying drawings, in which:
[0013] Figure 1 An example communication scenario is shown in which some embodiments of the present disclosure may be implemented;
[0014] Figure 2 shows a schematic diagram illustrating a communication process during a transition from a first network to a second network according to some embodiments of the present disclosure;
[0015] Figure 3 An example communication method implemented at a terminal device according to some embodiments of the present disclosure is shown;
[0016] Figure 4 Another example communication method implemented at a terminal device according to some embodiments of the present disclosure is shown;
[0017] Figure 5 Another example communication method implemented at a terminal device according to some embodiments of the present disclosure is shown;
[0018] Figure 6 Another example communication method implemented at a terminal device according to some embodiments of the present disclosure is shown;
[0019] Figure 7Another example communication method implemented at a terminal device according to some embodiments of the present disclosure is shown;
[0020] Figure 8 An example communication method implemented at a network device according to some embodiments of the present disclosure is shown;
[0021] Fig. 9 Another example communication method implemented at a network device according to some embodiments of the present disclosure is shown;
[0022] Fig.10 Another example communication method implemented at a network device according to some embodiments of the present disclosure is shown; and
[0023] Fig.11 is a simplified block diagram of a device suitable for implementing embodiments of the present disclosure.
[0024] Throughout the drawings, the same or similar reference numerals refer to the same or similar elements. DETAILED DESCRIPTION
[0025] The principle of the present disclosure will now be described with reference to some embodiments. It should be understood that these embodiments are described only for illustrative purposes and to help those skilled in the art understand and implement the present disclosure without implying any limitation on the scope of the disclosure. The disclosure described herein can be implemented in various ways different from the modes described below.
[0026] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.
[0027] As used herein, the term "terminal device" refers to any device with wireless or wired communication capabilities. Examples of terminal devices include, but are not limited to: user equipment (UE), personal computer, desktop, mobile phone, cellular phone, smart phone, personal digital assistant (PDA), portable computer, tablet computer, wearable device, Internet of Things (IoT) device, Internet of Everything (IoE) device, machine type communication (MTC) device, vehicle-mounted device for V2X communication (where X represents pedestrian, vehicle or infrastructure / network), or image capture device such as digital camera, gaming device, music storage and playback device, or Internet tool that allows wireless or wired Internet access and browsing, etc. The term "terminal device" can be used interchangeably with UE, mobile station, subscriber station, mobile terminal, user terminal or wireless device. In addition, the term "network device" refers to a device that can provide or host a cell or coverage with which a terminal device can communicate. Examples of network devices include, but are not limited to, Node B (NodeB or NB), evolved Node B (eNodeB or eNB), next generation Node B (gNB), transmit receive point (TRP), remote radio unit (RRU), radio head (RH), remote radio head (RRH), low power nodes such as femto nodes, pico nodes, etc.
[0028] In one embodiment, the terminal device may be connected to a first network device and a second network device. One of the first network device and the second network device may be a primary node, and the other may be a secondary node. The first network device and the second network device may use different radio access technologies (RATs). In one embodiment, the first network device may be a first RAT device, and the second network device may be a second RAT device. In one embodiment, the first RAT device is an eNB and the second RAT device is a gNB. Information related to different RATs may be sent from at least one of the first network device and the second network device to the terminal device. In one embodiment, the first information may be sent from the first network device to the terminal device, and the second information may be sent directly or via the first network device from the second network device to the terminal device. In one embodiment, information related to the configuration of the terminal device configured by the second network device may be sent from the second network device via the first network device. Information related to the reconfiguration of the terminal device configured by the second network device may be sent directly or via the first network device from the second network device to the terminal device.
[0029] As used herein, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. The term "including" and its variations are to be interpreted as open-ended terms, which mean "including but not limited to". The term "based on" is to be interpreted as "based at least in part on". The terms "one embodiment" and "embodiment" are to be interpreted as "at least one embodiment". The term "another embodiment" is to be interpreted as "at least one other embodiment". The terms "first", "second", etc. may refer to different or the same objects. Other explicit and implicit definitions may be included below.
[0030] In some examples, values, processes, or devices are referred to as "best," "lowest," "highest," "minimum," "maximum," etc. It should be understood that such descriptions are intended to indicate that a selection may be made among a number of functional alternatives used, and that such a selection is not necessarily better, lesser, higher, or more preferred than other selections.
[0031] As described above, currently, when the terminal device needs to perform data transmission in the second network, the terminal device simply releases the connection with the first network without notifying the first network. In this case, the first network regards the terminal device as a connection failure, which leads to incorrect network performance records.
[0032] Embodiments of the present disclosure provide a solution for notifying a transition from a first network to a second network to solve the above and other problems. The solution can avoid incorrect network performance records and facilitate enhancing the performance of terminal devices. The principles and implementations of the present disclosure will be described in detail below with reference to the accompanying drawings.
[0033] Figure 1 1 is a schematic diagram of an example communication scenario 100 in which embodiments of the present disclosure may be implemented. Figure 1 As shown, the communication scenario 100 may include a network device 110 (hereinafter also referred to as the first network device 110) and a terminal device 120 carrying a first USIM card 121 and a second USIM card 122. The first network device 110 may serve at least one of the first USIM card 121 and the second USIM card 122. The first USIM card 121 and the second USIM card 122 may conform to the same or different RATs, which exist now or will be developed in the future. It should be noted that the number of USIM cards carried by the terminal device 120 is not limited to two, and more than two USIM cards may also be applied. For convenience, the following description is given by taking two USIM cards as an example.
[0034] like Figure 1 As shown, the communication scenario 100 may also involve at least one adjacent network device 111 (hereinafter also referred to as the second network device 111). Figure 1Only one second network device 111 is shown in the figure. The adjacent network device 111 may also serve at least one of the first USIM card 121 and the second USIM card 122. For convenience, unless otherwise specified, the following description is made under the assumption that the first network device 110 serves the first USIM card 121 and the second network device 111 serves the second USIM card 122. However, it should be noted that it is merely an example for illustration and does not limit the present disclosure. For example, the first USIM card 121 and the second USIM card 122 may be served by the same network device such as the first network device 110 or the second network device 111.
[0035] In addition, the first network device 110 may communicate with the terminal device 120 via a channel such as a wireless communication channel. Similarly, the second network device 111 may also communicate with the terminal device 120 via a channel such as a wireless communication channel.
[0036] It should be understood that Figure 1 The number of devices in is given for illustrative purposes and does not imply any limitation to the present disclosure. The communication scenario 100 may include any suitable number of network devices and / or terminal devices suitable for implementing the present disclosure.
[0037] The communication in the communication scenario 100 may conform to any suitable standard, including but not limited to Global System for Mobile Communications (GSM), Long Term Evolution (LTE), LTE Evolution, Advanced LTE (LTE-A), Wideband Code Division Multiple Access (WCDMA), Code Division Multiple Access (CDMA), GSM EDGE Radio Access Network (GERAN), Machine Type Communication (MTC), etc. In addition, the communication may be performed according to any generation of communication protocols currently known or to be developed in the future. Examples of communication protocols include but are not limited to: first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, fifth generation (5G) communication protocols, sixth generation (6G) communication protocols or higher.
[0038] For convenience, the communication network formed between the first network device 110 and the terminal device 120 is called the first network (hereinafter also referred to as the first communication network), and the communication network formed between the second network device 111 and the terminal device 120 is called the second network (hereinafter also referred to as the second communication network).
[0039] It should be noted that a terminal device may involve multiple networks in multiple communication network systems. In some embodiments, multiple networks may be associated with multiple identifiers of the terminal device. It should be noted that multiple networks may be associated with other aspects of the terminal device, and the application is not limited to this. For illustration, the following description is given with the first network and the second network associated with the first subscriber identification module and the second subscriber identification module of the terminal device as an example.
[0040] like Figure 1 As shown, when the terminal device 120 has established a connection with the first network device 110 in the first network and remains in an idle state or an inactive state in the second network, if the terminal device 120 needs to perform data transmission with the second network device 111 in the second network, the terminal device 120 needs to perform a transition from the first network device 110 of the first network to the second network device 111 of the second network.
[0041] According to an embodiment of the present application, if it is determined that a switch from the first network device 110 to the second network device 111 is to be performed, the terminal device 120 sends a request for the switch to the first network device 110. In this way, the network device can be notified of the switch, thereby avoiding incorrect network performance records. Figure 2 Describe in more detail.
[0042] Figure 2 A schematic diagram illustrating a communication process 200 during a transition from a first network to a second network according to an embodiment of the present disclosure is shown. For discussion purposes, reference will be made to Figure 1 Describe process 200. Process 200 may involve Figure 1 The terminal device 120, the first network device 110 and the second network device 111 are shown. In this embodiment, it is assumed that the terminal device 120 is in a connected state in the first network of the first network device 110 and is in an idle state or inactive state in the second network of the second network device 111.
[0043] like Figure 2 As shown, the terminal device 120 determines 210 whether to perform a transition from the first network device 110 to the second network device 111. In some embodiments, the terminal device 120 may determine whether to send data between the terminal device 120 and the second network device 111, and if it is determined that data is to be sent, the terminal device 120 may determine whether there is an ongoing emergency service in the first network. If it is determined that there is no ongoing emergency service in the first network, the terminal device 120 may determine to perform a transition.
[0044] For example, if the terminal device 120 has mobile origination (MO) data to be sent to the second network device 111 and there is no ongoing emergency service in the first network, the terminal device 120 may determine to perform a switch. Alternatively, if the terminal device 120 receives a paging message from the second network device 111 and there is no ongoing emergency service in the first network, the terminal device 120 may determine to perform a switch. If it is determined that there is an ongoing emergency service in the first network, the terminal device 120 will ignore the paging information to avoid interrupting the emergency service. In this way, the quality of the emergency service is ensured.
[0045] When determining to perform the conversion, the terminal device 120 sends 220 a request for the conversion to the first network device 110. In some embodiments, the terminal device 120 may send the request via a radio resource control (RRC) message. For example, the terminal device 120 may send the request via a UE Assistance Information message. It should be noted that any other existing or future developed RRC messages may also be used, and the present application is not limited thereto.
[0046] In some embodiments, the request may include an expected RRC state in the first communication network. For example, the expected RRC state may include an idle state, an inactive state, or a connected state. In some alternative or additional embodiments, the request may include a reason for the request. For example, the reason may include power saving for power saving situations. As another example, the reason may include a network conversion for a second network conversion situation. It should be noted that any other appropriate form of reason is also feasible. In this way, it is helpful for the first network device 110 to distinguish the reason for the release request.
[0047] In some embodiments where the reason for the request includes a network switch, the request may include service information for the second communication network. In some embodiments, the service information may include an expected switch period or absence mode. For example, the service information may include an expected periodicity, a time domain offset, and an absence time per period.
[0048] In some embodiments in which the terminal device 120 decides to use a time division multiplexing (TDM) mode, the request may include a suggestion for the TDM mode. In some embodiments, the request may include a list of candidate TDM modes. In this case, the first network device 110 may select a TDM mode from the list. In some embodiments, the suggestion for the TDM mode may be sent in the request. For example, the terminal device 120 may send a suggestion for the TDM mode in the request via a UEAssistantInformation message. In some alternative embodiments, the suggestion for the TDM mode may be sent separately from the request. For example, the terminal device 120 may send a suggestion for the TDM mode via an RRC Setup Complete message.
[0049] According to an embodiment of the present application, the TDM mode (also referred to herein as a transition gap) is configured for the terminal device 120 to switch to the second network within a certain period of time (for example, within a short period of time) to send small data while maintaining a connection in the first network.
[0050] During the off period of the TDM mode, the first network device 110 should avoid scheduling the terminal device 120, and the medium access control (MAC) entity of the terminal device 120 should not perform any uplink (UL) transmission except Msg3 and MsgA on all configured service cells or specific service cells, and should not perform physical downlink control channel (PDCCH) monitoring and downlink (DL) reception unless the random access response (RAR) window, msgB response window or contention resolution timer is running.
[0051] In some embodiments, the first network device 110 may broadcast whether it supports the TDM mode in the system information, and the terminal device 120 may determine whether the first network device 110 supports the TDM mode based on the system information. If it is determined that the first network device 110 supports the TDM mode, the terminal device 120 may determine the TDM mode and incorporate the TDM mode into the request for conversion.
[0052] In some embodiments, the TDM mode information may include the start information and duration of the conversion. This may be considered a one shot conversion gap. In some embodiments, the start information may include any one of a system frame number (SFN), a time slot number, and an orthogonal frequency division multiplexing (OFDM) symbol number. In some alternative embodiments, the TDM mode information may include the periodicity of the conversion, the time domain offset, and the length of the absence time per period. This may be considered a periodic conversion gap.
[0053] It should be noted that the request is not limited to the above examples but may also include any other suitable information associated with the data transmission to be performed in the second communication network. In this way, the first network device 10 is facilitated to decide the TDM mode to be used.
[0054] In some embodiments in which the terminal device 120 is configured with dual connectivity (DC) and the terminal device 120 wants to maintain a connected state in the first network, the request may include releasing or deactivating at least a portion of the serving cells while maintaining a connected state in the first communication network. For example, the terminal device 120 may set the expected RRC state to a connected state and indicate the release or deactivation of the entire secondary node (SN). Alternatively, the terminal device 120 may set the expected RRC state to a connected state and indicate the release or deactivation of a specific one or more serving cells of the SN. In some embodiments, DC may be LTE-DC, LTE-NR DC (EN-DC), next generation core NR-LTE DC (NG EN-DC), NR-LTE DC (NE-DC) or NR-DC.
[0055] In some embodiments where the terminal device 120 is configured with carrier aggregation and the terminal device 120 wants to remain connected in the first network, the request may include a suggestion to release or deactivate at least some of the serving cells while remaining connected in the first communication network. For example, the terminal device 120 may set the expected RRC state to the connected state and indicate the release or deactivation of all configured serving cells. Alternatively, the terminal device 120 may set the expected RRC state to the connected state and indicate the release or deactivation of specific one or more serving cells.
[0056] According to an embodiment of the present application, a timer for network switching is defined. Figure 2 In some embodiments, when sending 220 the request, the terminal device 120 may start 230 a timer. In some embodiments, the upper limit value of the timer may be broadcast by system information from the first network device 110. Alternatively, the upper limit value of the timer may be configured by an RRC message from the first network device 110. It should be noted that the upper limit value may also be determined in any other suitable form.
[0057] In some embodiments, if it is determined that the timer is not running, the terminal device 120 may send a request for conversion. For example, if the conversion has not been performed and the timer is running, the terminal device 120 should not send another request for conversion even if it is determined that the next data is to be performed between the terminal device 120 and the first network device 110. In this way, repeated transmission of requests can be avoided and transmission resources can be saved.
[0058] In some embodiments in which the first network device 110 ignores the request and does not give a response to the request, the terminal device 120 may autonomously perform 270 a switch to the second network device 111 when the timer expires. In some embodiments for performing the switch, the terminal device 120 may release the connection with the first network device 110 so as to be idle in the first network and switch to the second network. In some alternative embodiments, the terminal device 120 may maintain the connection with the first network device 110 and perform the switch between the first network device 110 and the second network device 111 using a TDM mode.
[0059] In some alternative embodiments, Figure 2 As shown, upon receiving a request for conversion, the first network device 110 may determine 240 a response to the request and send 250 the response to the terminal device 120 within a time period corresponding to the upper limit value of the timer. Upon receiving a response to the request, the terminal device 120 may stop 260 the timer. In some embodiments, the response may be sent in an RRC release (RRCRelease) message. Alternatively, the response may be sent in an RRC reconfiguration (RRCReconfiguration) message with a conversion gap configuration. It should be noted that the above is only an example, and the response may be sent in any other suitable existing or future developed RRC message.
[0060] In some embodiments, the first network device 110 may send a response indicating that the conversion is rejected (hereinafter also referred to as the first response). In some embodiments, the response may include a waiting time, during which the terminal device 120 is prohibited from sending another request for conversion. During the waiting time, the first network device 110 expects to maintain a connection with the terminal device 120, and the terminal device 120 should not initiate another conversion request within the waiting time. In some alternative or additional embodiments, the response may include the reason for the rejection. For example, the reason may indicate that an important service will be performed between the terminal device 120 and the first network device 110. It should be noted that the response may also include any other suitable content. It should also be noted that the reason may include any other suitable content.
[0061] In some alternative embodiments, the first network device 110 may send a response indicating that the conversion is allowed (hereinafter also referred to as a second response). In some embodiments in which the first network device 110 supports the TDM mode, the response may include the TDM mode to be used in the conversion between the first network device 110 and the second network device 111.
[0062] In some embodiments where the TDM mode is determined by the first network device 110, the first network device 110 may determine the TDM mode based on the service information of the second network device 111 and the suggestion of the TDM mode (if received from the request), and incorporate the TDM mode into the response to the request. In some embodiments where the TDM mode is determined by the terminal device 120, the first network device 110 may reject the suggestion of the TDM mode by the terminal device 120 and provide the suggested TDM mode in the second response.
[0063] For example, the first network device 110 may send an RRC message for processing the request, such as an RRCRelease message and an RRCReconfiguration message with a transition gap configuration, to the terminal device 120. Upon receiving the RRC message, the terminal device 120 may stop the timer. It should be noted that any other existing or future developed RRC message may also be used, and the present application is not limited thereto.
[0064] In some alternative embodiments, upon determining to initiate the reestablishment of the connection with the first network device 110, the terminal device 120 may stop the timer. In some alternative embodiments, upon receiving a message of a switch from the first network device 110 to the third network device of the first communication network, the terminal device 120 may stop the timer. For example, upon receiving an RRCReconfiguration message including reconfigurationWithSync, the terminal device 120 may stop the timer. In some embodiments in which the first network device 110 has a transition gap configuration for the terminal device 120, the transition gap configuration may be passed from the first network device 110 as the source network device to the third network device as the target network device during the handover. For example, the transition gap configuration may be passed via a handover preparation information (HandoverPreparationInformation) message. It should be noted that any other suitable message is also feasible.
[0065] As described above, upon receiving a response from the first network device 110 before the timer expires, the terminal device 120 may stop 260 the timer. The terminal device 120 may then perform 270 a transition to the second network device 111 based on the response to the request. In some embodiments, the terminal device 120 may release the connection with the first network device 110 so as to be in an idle or inactive state in the first network and transition to the second network. In some alternative embodiments, the terminal device 120 may maintain the connection with the first network device 110 and perform the transition between the first network device 110 and the second network device 111 using a TDM mode.
[0066] like Figure 2 As shown, in some embodiments where the terminal device 120 wants to stop the TDM mode, the terminal device 120 can send 280 or 280' to the relevant network device for an indication to stop the TDM mode. In some embodiments, if it is determined that no data is to be sent between the terminal device 120 and the second network device 111, the terminal device 120 can send 280 the indication to the first network device 110. In some alternative embodiments, if it is determined that no data is to be sent between the terminal device 120 and the first network device 110, the terminal device 120 can send 280' the indication to the second network device 111.
[0067] In some embodiments, the terminal device 120 may send the indication via an RRC message. In some embodiments, the terminal device 120 may send the indication in an implicit manner. For example, the terminal device 120 may send an RRC message such as a UEAssistanceInformation message with an expected RRC state as a connected state and without TDM mode information. Alternatively, the terminal device 120 may send the indication in an explicit manner. For example, the terminal device 120 may send an RRC message such as a UEAssistanceInformation message with an explicit indication (e.g., a bit value).
[0068] In some alternative embodiments, the terminal device 120 may send the indication via a Medium Access Control (MAC) Control Element (CE). In this way, the terminal device 120 may use the MAC CE to activate or deactivate the TDM mode.
[0069] In some embodiments where the terminal device 120 cannot return to the first network at the end of the TDM mode, the terminal device 120 may release the connection with the first network device 110 and perform the process of entering the idle state. Alternatively, the terminal device 120 may not take any action. That is, whether to maintain the connection with the first network device 110 depends on the terminal device 120.
[0070] It should be noted that Figure 2 The actions shown are not always necessary to implement the embodiments of the present disclosure, and more or fewer actions may be modified as needed. Figure 2 The process described in the embodiment of the present disclosure provides a communication method implemented at a terminal device and a network device. Figures 3 to 10 Describe these methods.
[0071] Figure 3 An example communication method 300 implemented at a terminal device according to some embodiments of the present disclosure is shown. For example, the method 300 may be implemented in a Figure 1For the purpose of discussion, reference will be made to Figure 1 Method 300 is described. It should be understood that method 300 may include additional blocks not shown and / or may omit some of the blocks shown, and the scope of the present disclosure is not limited in this regard.
[0072] like Figure 3 As shown, in block 310, the terminal device 120 determines whether to perform a transition from the first network device 110 to the second network device 111. In some embodiments, the first network of the first network device 110 may be associated with a first identifier of the terminal device 120 (such as a first USIM card 121), and the second network of the second network device 111 may be associated with a second identifier of the terminal device 120 (such as a second USIM card 122). It should be noted that the first network and the second network may be distinguished from each other in other aspects of the terminal device 120 rather than in terms of identifiers.
[0073] When it is determined that the switch is to be performed, in block 320, the terminal device 120 sends a request to the first network device 110 for a switch from the first network device 110 to the second network device 111. In this way, the network side is notified of the switch, and incorrect network performance records can be avoided. Therefore, performance enhancement during network switch can be achieved.
[0074] According to some embodiments of the present application, a timer is introduced to adjust the network conversion behavior of the terminal device 120. In some embodiments, the terminal device 120 can start the timer when sending the request. In some embodiments in which it is determined to send data to the second network device 111, the terminal device 120 can determine whether the timer is running, and if it is determined that the timer is not running, send a request for conversion. In this way, repeated transmission of requests for conversion can be effectively avoided.
[0075] In some embodiments, the terminal device 120 may perform the transition when the timer expires. In some embodiments, the terminal device 120 may stop the timer in response to at least one of: receiving a response to the request from the first network device 110; determining to initiate a connection reestablishment with the first network device 110; or receiving a message of a switch from the first network device 110 to a third network device of the first network. Figures 4 to 7 Describe in more detail.
[0076] Figure 4 Another example communication method 400 implemented at a terminal device according to some embodiments of the present disclosure is shown. For example, the method 400 may be implemented in a Figure 1 For the purpose of discussion, reference will be made to Figure 1Method 400 is described. It should be understood that method 400 may include additional blocks not shown and / or may omit some of the blocks shown, and the scope of the present disclosure is not limited in this regard.
[0077] like Figure 4 As shown, in block 410, the terminal device 120 may determine whether to send data between the terminal device 120 and the second network device 111. In some embodiments, the terminal device 120 may determine to send data if there is MO data to be sent to the second network device 111. In some alternative embodiments, the terminal device 120 may determine to send data if a paging message is received from the second network device 111.
[0078] Once it is determined that data is to be sent, at block 420, the terminal device 120 may determine whether there is an ongoing emergency service between the terminal device 120 and the first network device 110. If it is determined at block 403 that there is no ongoing emergency service between the terminal device 120 and the first network device 110, the terminal device 120 may send a request to the first network device 110 for switching from the first network device 110 to the second network device 111. In this way, the quality of the emergency service may be ensured.
[0079] In some embodiments, the terminal device 120 may determine whether a timer for network switching is running, and if it is determined that the timer is running, the terminal device 120 does not send the request to the first network device 110, and if it is determined that the timer is not running, the terminal device 120 sends the request to the first network device 110. In this way, unnecessary request retransmissions can be avoided.
[0080] In some embodiments, the request may include at least one of the following: an expected RRC state in the first network; a reason for the request; service information of the second network; a suggestion for a TDM mode; and a suggestion to release or deactivate at least part of the serving cell while maintaining a connection state in the first network. Figure 2 The description of action 220 in is similar and will not be repeated here.
[0081] After sending the request, the terminal device 120 may start a timer at block 404. In some embodiments, the terminal device 120 may receive an upper limit value of the timer in system information from the first network device 110. Alternatively, the terminal device 120 may receive an upper limit value of the timer in a dedicated RRC message from the first network device 110. Based on the upper limit value, the terminal device 120 may manage the timing of the timer.
[0082] At block 405, terminal device 120 may determine whether the timer has expired. If it is determined that the timer has not expired, then at block 406, terminal device 120 may determine whether a response to the request has been received from first network device 110. If it is determined at block 406 that a response has been received, terminal device 120 may stop the timer at block 407.
[0083] At block 408, terminal device 120 may determine whether to allow or deny the transition based on the response. If the response indicates that the transition is denied (i.e., the first response), then at block 409, terminal device 120 may not cause another request for the transition to be sent within the wait time. In some embodiments where the wait time is configured by first network device 110, terminal device 120 may obtain the wait time from the response. It should be noted that the wait time may be determined in any other suitable manner.
[0084] If the response indicates that the transition is allowed (i.e., the second response), the terminal device 120 may perform the transition at block 410. If it is determined at block 406 that no response has been received, the terminal device 120 may return to block 405. If it is determined at block 405 that the timer has expired, the terminal device 120 may proceed to block 410 to perform the transition.
[0085] In some embodiments for performing the conversion, the terminal device 120 may release the first connection with the first network device 110 and establish a second connection with the second network device 111. In this way, the terminal device 120 may be in an idle or inactive state in the first network and in a connected state in the second network.
[0086] In some alternative embodiments, the terminal device 120 may perform a TDM mode between the first network and the second network. In this way, the terminal device 120 may perform the desired data transmission in the second network while maintaining a connection state in the first network. This will refer to Figure 5 and Figure 6 Detailed description.
[0087] Figure 5 Another example communication method 500 implemented at a terminal device according to some embodiments of the present disclosure is shown. For example, the method 500 may be implemented in a Figure 1 For the purpose of discussion, reference will be made to Figure 1 The method 500 is described. It should be understood that the method 500 may include additional blocks not shown and / or may omit some of the blocks shown, and the scope of the present disclosure is not limited in this regard. In this embodiment, the TDM mode is determined by the terminal device 120.
[0088] like Figure 5As shown, in block 510, the terminal device 120 may determine a TDM mode associated with the conversion. In some embodiments, the terminal device 120 may decide to use the TDM mode based on understanding the support of the TDM mode by the first network device 110. The understanding may be obtained from system information broadcast by the first network device 110. In some embodiments, the terminal device 120 may determine the TDM mode by determining at least one of the following: the start information and duration of the conversion (i.e., a conversion gap); or the periodicity of the conversion, the time domain offset, and the length of the absence time per period (i.e., a periodic conversion gap).
[0089] At block 520, the terminal device 120 may perform conversion according to the TDM mode. In some embodiments, the terminal device 120 may perform data transmission in the first network and the second network according to the TDM mode between the first network and the second network.
[0090] At block 530, terminal device 120 may generate first information of a TDM mode for first network device 110 and second information of a TDM mode for second network device 111. In some embodiments, the first information and the second information may be adapted to meet respective time domain requirements in the first network and the second network.
[0091] At block 540, the terminal device 120 may send the first information to the first network device 110. For example, the terminal device 120 may send the first information via a UEAssistanceInformation message. It should be noted that any other suitable messages are also feasible.
[0092] At block 550, the terminal device 120 may send the second information to the second network device 111. For example, the terminal device 120 may send the second information via an RRCSetupComplete message. It should be noted that any other suitable messages are also feasible.
[0093] In some alternative embodiments, the first network device 110 may renegotiate the TDM mode with the terminal device 120. In some embodiments, the terminal device 120 may provide a list of candidate TDM modes for the first network device 110 to select one of them. In some embodiments, in the case where the terminal device 120 provides a TDM mode, the first network device 110 may reject the TDM mode and provide the terminal device 120 with a suggested TDM mode.
[0094] So far, refer to Figure 5 The embodiment of the case where the TDM mode is determined by the terminal device 120 is described. Figure 6 A case where the TDM mode is determined by the first network device 110 will be described.
[0095] Figure 6 Another example communication method 600 implemented at a terminal device according to some embodiments of the present disclosure is shown. For example, the method 600 may be implemented in a Figure 1 For the purpose of discussion, reference will be made to Figure 1 Method 600 is described. It should be understood that method 600 may include additional blocks not shown and / or may omit some of the blocks shown, and the scope of the present disclosure is not limited in this regard.
[0096] like Figure 6 As shown, at block 610, the terminal device 120 may receive a TDM pattern associated with the transition from the first network device 110. In some embodiments, the terminal device 120 may obtain the TDM pattern from a response to a request for transition, the response being received from the first network device 110. In some embodiments, the terminal device 120 may obtain at least one of: the start information and duration of the transition (i.e., a one-time transition gap); or the periodicity of the transition, the time domain offset, and the length of the absence time per period (i.e., a periodic transition gap).
[0097] At block 620, the terminal device 120 may perform conversion according to the TDM mode. In some embodiments, the terminal device 120 may perform data transmission in the first network and the second network according to the TDM mode between the first network and the second network.
[0098] At block 630, the terminal device 120 may generate second information of a TDM pattern for the second network device 111 based on the TDM pattern received from the network device 110. In some embodiments, the second information may be adapted to meet time domain requirements in the second network.
[0099] At block 640, the terminal device 120 may send the second information to the second network device 111. For example, the terminal device 120 may send the second information via an RRCSetupComplete message. It should be noted that any other suitable messages are also feasible.
[0100] So far, activation of the TDM mode has been described. Next, deactivation of the TDM mode will be described. Figure 7 Another example communication method 700 implemented at a terminal device according to some embodiments of the present disclosure is shown. For example, the method 700 may be implemented in a Figure 1 For the purpose of discussion, reference will be made to Figure 1 Method 700 is described. It should be understood that method 700 may include additional blocks not shown and / or may omit some of the blocks shown, and the scope of the present disclosure is not limited in this regard.
[0101] like Figure 7 As shown, in block 710, the terminal device 120 may determine whether there is no data transmission between the terminal device 120 and one of the first network device 110 and the second network device 111. Once it is determined that there is no data transmission between the terminal device 120 and one of the first network device 110 and the second network device 111, in block 720, the terminal device 120 may send an instruction for stopping the TDM mode to the other of the first network device 110 and the second network device 111.
[0102] In some embodiments, if it is determined that there is no data transmission between the terminal device 120 and the second network device 111, the terminal device 120 may send an indication to the first network device 110. In some embodiments, if it is determined that there is no data transmission between the terminal device 120 and the first network device 110, the terminal device 120 may send an indication to the second network device 111.
[0103] In some embodiments, the terminal device 120 may send the indication via an RRC message. In some embodiments, the terminal device 120 may send the indication in an implicit manner. For example, the terminal device 120 may send an RRC message such as a UEAssistanceInformation message with an expected RRC state as a connected state and without TDM mode information. Alternatively, the terminal device 120 may send the indication in an explicit manner. For example, the terminal device 120 may send an RRC message such as a UEAssistanceInformation message with an explicit indication (e.g., a bit value).
[0104] In some alternative embodiments, the terminal device 120 may send the indication via a Medium Access Control (MAC) Control Element (CE). In this way, the terminal device 120 may use the MAC CE to activate or deactivate the TDM mode.
[0105] In block 730 , the terminal device 120 may stop the TDM mode and maintain a connection with the other network device of the first network device 110 and the second network device 111 .
[0106] In some embodiments where the terminal device 120 cannot return to the first network at the end of the TDM mode, the terminal device 120 may release the connection with the first network device 110 and perform a process of entering an idle state or an inactive state. Alternatively, the terminal device 120 may not take any action. That is, whether to maintain the connection with the first network device 110 depends on the terminal device 120.
[0107] So far, a communication method implemented at a terminal device has been described. Accordingly, an embodiment of the present application also provides a communication method implemented at a network device. This will be referred to below. Figures 8 to 10 Give a description.
[0108] Figure 8 An example communication method 800 implemented at a network device according to some embodiments of the present disclosure is shown. For example, the method 800 may be implemented in a Figure 1 The first network device 110 or the second network device 111 is shown as being executed. For the purpose of discussion, reference will be made to Figure 1 The method 800 is described with reference to the first network device 110. It should be understood that the method 800 may include additional blocks not shown and / or may omit some of the blocks shown, and the scope of the present disclosure is not limited in this regard.
[0109] like Figure 8 As shown, in block 810, the first network device 110 receives a request for a switch from the first network device 110 to the second network device 111 from the terminal device 120. In some embodiments, the first network of the first network device 110 may be associated with a first identifier (such as a first USIM card 121) of the terminal device 120, and the second network of the second network device 111 may be associated with a second identifier (such as a second USIM card 122) of the terminal device 120. It should be noted that the first network and the second network may be distinguished from each other by other aspects of the terminal device 120 rather than by the identifier.
[0110] In some embodiments, the request may include at least one of: an expected RRC state in the first network; a reason for the request; service information of the second network; a suggestion for a TDM mode; and a suggestion to release or deactivate at least part of the serving cells while maintaining a connected state in the first network.
[0111] In some embodiments, the first network device 110 may not provide a response to the request. In some alternative embodiments, the first network device 110 may send a response to the request within a time period. In some embodiments, the time period may correspond to an upper limit value of a timer managed by the terminal device 120 and started at the time of sending the request. In some embodiments, the first network device 110 may configure the upper limit value and send the upper limit value to the terminal device 120. For example, the upper limit value may be broadcast in the system information. Alternatively, the upper limit value may be configured in an RRC message.
[0112] In some embodiments, the first network device 110 may send a first response indicating that the conversion is rejected. In some embodiments, the first response may include a waiting time during which another request for conversion is prohibited from being transmitted. In this way, repeated transmission of the conversion request can be avoided and transmission resources can be saved.
[0113] In some embodiments, the first network device 110 may send a second response indicating that the conversion is allowed. In some embodiments, the second response may include a TDM mode associated with the conversion. In this way, repeated transmission of requests for conversion can be avoided and transmission resources can be saved. Figures 9 and 10 Describe in more detail.
[0114] Fig. 9 Another example communication method 900 implemented at a network device according to some embodiments of the present disclosure is shown. For example, the method 900 may be implemented in a Figure 1 The first network device 110 or the second network device 111 is shown as being executed. For the purpose of discussion, reference will be made to Figure 1 The method 900 is described with reference to the first network device 110. It should be understood that the method 900 may include additional blocks not shown and / or may omit some of the blocks shown, and the scope of the present disclosure is not limited thereto. In this embodiment, the TDM mode is determined by the first network device 110.
[0115] like Fig. 9 As shown, at block 910, the first network device 110 may determine a TDM mode associated with the conversion. In some embodiments, the first network device 110 may obtain service information of the second network from the received request, and determine the TDM mode based on the service information. In some embodiments in which the request includes a suggestion for a TDM mode, the first network device 110 may obtain the service information and the suggestion for the TDM mode from the received request, and determine the TDM mode based on the service information and the suggestion for the TDM mode.
[0116] In some embodiments, the first network device 110 may determine the TDM mode by determining at least one of: the start information and duration of the transition; or the periodicity of the transition, the time domain offset, and the length of the absence time per period.
[0117] At block 920, the first network device 110 may send the TDM pattern to the terminal device 120. In some embodiments, the first network device 110 may send the TDM pattern to the terminal device 120 in the second response. Alternatively, the first network device 110 may send the TDM pattern separately from the second response. In some embodiments, the TDM pattern may be sent in an RRC message such as an RRCReconfiguration message. It should be noted that any other suitable RRC message is also feasible.
[0118] The above describes an embodiment of the case where the TDM mode is determined by the first network device 110. The following description will be given for the case where the TDM mode is determined by the terminal device 120. Fig.10 Another example communication method 1000 implemented at a network device according to some embodiments of the present disclosure is shown. For example, the method 1000 may be implemented in a Figure 1 The first network device 110 or the second network device 111 is shown as being executed. For the purpose of discussion, reference will be made to Figure 1 The method 1000 is described with reference to the first network device 110. It should be understood that the method 1000 may include additional blocks not shown and / or may omit some of the blocks shown, and the scope of the present disclosure is not limited in this regard.
[0119] like Fig.10 As shown, at block 1010, the first network device 110 may receive a TDM pattern associated with a conversion from the terminal device 120. In some embodiments, the first network device 110 may receive at least one of the following: start information and duration of the conversion; or periodicity of the conversion, time domain offset, and length of absence time per period. At block 1020, the first network device 110 may perform data transmission with the terminal device 120 according to the TDM pattern between the first network and the second network.
[0120] During the TDM mode, the first network device 110 may receive an indication for stopping the TDM mode from the terminal device 120. In this case, the first network device 110 may proceed to block 1030. In block 1030, the first network device 110 may determine whether an indication for stopping the TDM mode is received.
[0121] In some embodiments, the first network device 110 may receive the indication via an RRC message. In some embodiments, the first network device 110 may receive the indication in an implicit manner. For example, if an RRC message (such as a UEAssistanceInformation message) with an expected RRC state as a connected state and no TDM mode information is received, the first network device 110 may determine that an indication for stopping the TDM mode is received. In some alternative embodiments, the terminal device 120 may receive the indication in an explicit manner. For example, if an RRC message (such as a UEAssistanceInformation message) with an explicit indication is received, the explicit indication is, for example, a bit value indicating that the TDM mode should be stopped, the first network device 110 may determine that an indication for stopping the TDM mode is received.
[0122] In some alternative embodiments, the first network device 110 may receive the indication via a MAC CE. For example, if a MAC CE indicating that the TDM mode should be stopped is received, the first network device 110 may determine that an indication for stopping the TDM mode is received.
[0123] When it is determined that the indication is received, in block 1040 , the first network device 110 may stop the TDM mode and maintain the connection with the terminal device 120 .
[0124] Figures 3 to 10 The implementation of the method described in substantially corresponds to combining Figure 2 The process described above is not repeated here, so other details are not repeated here. Using the methods 300 to 1000 according to the embodiments of the present disclosure, the network performance during the network transition can be enhanced.
[0125] Fig.11 1 is a simplified block diagram of a device 1100 suitable for implementing embodiments of the present disclosure. The device 1100 may be considered as Figure 1 Another example implementation of the terminal device 120 or the first network device 110 or the second network device 111 is shown. Therefore, the device 1100 can be implemented at the terminal device 120 or the first network device 110 or the second network device 111 or implemented as at least a part thereof.
[0126] As shown, the device 1100 includes a processor 1110, a memory 1120 coupled to the processor 1110, a suitable transmitter (TX) and receiver (RX) 1140 coupled to the processor 1110, and a communication interface coupled to the TX / RX 1140. The memory 1110 stores at least a portion of the program 1130. The TX / RX 1140 is used for bidirectional communication. The TX / RX 1140 has at least one antenna to facilitate communication, but in fact the access node mentioned in this application may have several antennas. The communication interface may represent any interface required for communication with other network elements, such as an X2 interface for bidirectional communication between eNBs, an S1 interface for communication between a mobility management entity (MME) / serving gateway (S-GW) and an eNB, a Un interface for communication between an eNB and a relay node (RN), or a Uu interface for communication between an eNB and a terminal device.
[0127] Assume that the program 1130 includes program instructions that, when executed by the associated processor 1110, enable the device 1100 to operate in accordance with embodiments of the present disclosure, as referred to herein. Figures 1 to 10 As discussed above. The embodiments herein may be implemented by computer software executable by a processor 1110 of the device 1100, or by hardware, or by a combination of software and hardware. The processor 1110 may be configured to implement various embodiments of the present invention. In addition, the combination of the processor 1110 and the memory 1120 may form a processing component 1150 suitable for implementing various embodiments of the present disclosure.
[0128] The memory 1120 may be of any type suitable for the local technology network and may be implemented using any suitable data storage technology, such as, as non-limiting examples, non-transitory computer-readable storage media, semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. Although only one memory 1120 is shown in the device 1100, there may be several physically distinct memory modules in the device 1100. As non-limiting examples, the processor 1110 may be of any type suitable for the local technology network and may include one or more of a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture. The device 1100 may have multiple processors, such as a dedicated integrated circuit chip that is time-slaved to a clock that synchronizes a main processor.
[0129] In general, various embodiments of the present disclosure may be implemented in hardware or dedicated circuits, software, logic, or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software, which may be executed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of the present disclosure are shown and described as block diagrams, flow charts, or using some other graphical representations, it will be understood that the blocks, devices, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuits or logic, general hardware, or controllers or other computing devices, or some combination thereof, as non-limiting examples.
[0130] The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer readable storage medium. The computer program product includes computer executable instructions such as those included in a program module that are executed in a device on a target real or virtual processor to perform the above-referenced Figures 1 to 10 The process or method described. In general, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The functions of program modules can be combined or separated between program modules as needed in various embodiments. The machine executable instructions of program modules can be executed in local or distributed devices. In distributed devices, program modules can be located in both local storage media and remote storage media.
[0131] The program code for executing the disclosed method can be written in any combination of one or more programming languages. These program codes can be provided to a processor or controller of a general-purpose computer, a special-purpose computer or other programmable data processing device so that the program code enables the function / operation specified in the flow chart and / or block diagram to be realized when the program code is executed by the processor or controller. The program code can be executed completely on the machine, partially on the machine, as an independent software package, partially on the machine and partially on a remote machine, or completely on a remote machine or server.
[0132] The above program code may be contained on a machine-readable medium, which may be any tangible medium that may contain or store a program used by or in conjunction with an instruction execution system, device, or apparatus. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. The machine-readable medium may include, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or device, or any suitable combination of the foregoing. More specific examples of machine-readable storage media would include: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
[0133] In addition, although operations are described in a particular order, this should not be understood as requiring the specific order shown or to perform these operations in sequence, or to perform all the operations shown, to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details are included in the above discussion, these details should not be interpreted as limitations on the scope of the present disclosure, but should be interpreted as descriptions of features peculiar to a particular embodiment. Certain features described in the context of a separate embodiment may also be implemented in combination in a single embodiment. On the contrary, the various features described in the context of a single embodiment may also be implemented in multiple embodiments individually or in any suitable sub-combination.
[0134] Although the disclosure has been described in language specific to structural features and / or methodological actions, it should be understood that the disclosure defined in the appended claims is not necessarily limited to the specific features or actions described above. Instead, the specific features and actions described above are disclosed as example forms of implementing the claims.
Claims
1. A communication method performed by a terminal device, the method comprising: Determining to switch from a first network to a second network, the first network and the second network being associated with corresponding universal subscriber identity modules USIM; as well as Sending a first request to the first network through first UE auxiliary information, wherein the first request includes first information, and the first information indicates a first gap mode for the terminal device to switch to the second network while remaining in a connected state in the first network; and Based on determining that the terminal device no longer has a preference for gaps, second UE assistance information is sent to the first network without including information indicating a gap pattern.
2. The method of claim 1 , wherein sending the first request comprises: Determine if the timer is running; as well as When it is determined that the timer is not running, the first request is sent.
3. The method according to claim 2, further comprising: When sending the first request, the timer is started.
4. The method according to claim 2, further comprising: The value of the timer is received from the first network in an RRC message.
5. The method according to claim 1, further comprising: receiving second information from the first network, wherein the second information indicates a second gap pattern for multiple USIMs, and The second gap pattern is determined by the first network device based on the first information.
6. The method of claim 1, wherein the first gap pattern indicates: The starting system frame number (SFN) in case the gap is aperiodic, or the period and time offset in case the gap is periodic.
7. The method of claim 5, wherein the second gap pattern indicates: The starting System Frame Number (SFN) in the case where the gap is aperiodic, or The period and time offset in case the gap is periodic.
8. The method according to claim 1, wherein: The first UE assistance information further indicates one or more serving cells, or cells belonging to a secondary node to be released for multiple USIMs.
9. A method of communication performed by a network device of a first network, the first network being associated with a first universal subscriber identity module (USIM), the method comprising: Receiving, from a terminal device, a first request from the terminal device through first UE assistance information, wherein the first request includes first information indicating a first gap mode for the terminal device to switch to a second network while remaining in a connected state in the first network; as well as Based on determining that the terminal device no longer has a preference for gaps, second UE assistance information is received from the terminal device, wherein the second UE assistance information is sent without information indicating a gap pattern.
10. The method according to claim 9, further comprising: The value of the timer is sent to the terminal device in a radio resource control (RRC) message, wherein the first request is received based on a determination that the timer is not running.
11. The method according to claim 10, further comprising: Based on the first information, determining a second gap pattern for multiple USIMs; as well as Sending second information indicating the second gap pattern to the terminal device.
12. The method of claim 9, wherein the first gap pattern indicates: The starting system frame number (SFN) and the length of the gap if the gap is aperiodic, or The period, time offset and length of the gap in case the gap is periodic.
13. The method of claim 11, wherein the second gap pattern indicates: The starting system frame number (SFN) and the length of the gap if the gap is aperiodic, or The period, time offset and length of the gap in case the gap is periodic.
14. The method according to claim 9, wherein the first UE assistance information further indicates one or more serving cells, or cells belonging to a secondary node to be released for multiple USIMs.
