EP4616628A1

EP4616628A1 - User equipment, network node, and methods for handling communications

Info

Publication number: EP4616628A1
Application number: EP23798766.4A
Authority: EP
Inventors: Muhammad Ali Kazmi; Zhixun Tang; Ming Li
Original assignee: Telefonaktiebolaget LM Ericsson AB
Current assignee: Telefonaktiebolaget LM Ericsson AB
Priority date: 2022-11-07
Filing date: 2023-10-30
Publication date: 2025-09-17
Also published as: WO2024099811A1

Abstract

A method performed by a user equipment with multi-SIM is provided. The user equipment firstly determines a collision between a pair of measurement gaps belonging to respective measurement gap patterns configured by different networks. Then, a priority rule that a measurement gap with longer MGRP would have higher priority in the colliding pair is used for determining priority of those two measurement gaps. The measurement gap with lower priority might be canceled afterwards. A method by a network node regarding priority of colliding measurement gaps configured by different networks is also provided.

Description

USER EQUIPMENT, NETWORK NODE, AND METHODS FOR HANDLING COMMUNICATIONS

TECHNICAL FIELD

Embodiments herein relate to a user equipment (UE), a network node, and methods performed therein regarding wireless communication. In particular, embodiments herein relate to handling communication, such as handling operation of a multiSubscriber Identity Module (SIM) user equipment.

BACKGROUND

In a typical wireless communications network, UEs, also known as wireless communication devices, mobile stations, stations (STA) and/or wireless devices, communicate via a Radio Access Network (RAN) with one or more core networks (CN). The RAN covers a geographical area which is divided into service areas or cell areas, with each service area or cell area being served by radio network node such as an access node, e.g., a Wi-Fi access point or a radio base station (RBS), which in some networks may also be called, for example, a NodeB, a gNodeB, or an eNodeB. The service area or cell area is a geographical area where radio coverage is provided by the radio network node. The radio network node operates on radio frequencies to communicate over an air interface with the UEs within range of the radio network node. The radio network node communicates over a downlink (DL) to the UE, and the UE communicates over an uplink (UL) to the radio network node.

A Universal Mobile Telecommunications System (UMTS) is a third generation telecommunication network, which evolved from the second generation (2G) Global System for Mobile Communications (GSM). The UMTS terrestrial radio access network (UTRAN) is essentially a RAN using wideband code division multiple access (WCDMA) and/or High-Speed Packet Access (HSPA) for communication with user equipment. In a forum known as the Third Generation Partnership Project (3GPP), telecommunications suppliers propose and agree upon standards for present and future generation networks and UTRAN specifically, and investigate enhanced data rate and radio capacity. In some RANs, e.g., as in UMTS, several radio network nodes may be connected, e.g., by landlines or microwave, to a controller node, such as a radio network controller (RNC) or a base station controller (BSC), which supervises and coordinates various activities of the plural radio network nodes connected thereto. The RNCs are typically connected to one or more core networks.

Specifications for the Evolved Packet System (EPS) have been completed within the 3GPP and this work continues in the coming 3GPP releases, such as 6G networks and development of 5G such as New Radio (NR). The EPS comprises the Evolved Universal Terrestrial Radio Access Network (E-UTRAN), also known as the Long-Term Evolution (LTE) radio access network, and the Evolved Packet Core (EPC), also known as System Architecture Evolution (SAE) core network. E-UTRAN/LTE is a 3GPP radio access technology wherein the radio network nodes are directly connected to the EPC core network. As such, the Radio Access Network (RAN) of an EPS has an essentially “flat” architecture comprising radio network nodes connected directly to one or more core networks.

With the emerging 5G technologies, such as new radio (NR), the use of very many transmit- and receive-antenna elements is of great interest as it makes it possible to utilize beamforming, such as transmit-side and receive-side beamforming. Transmit-side beamforming means that the transmitter can amplify the transmitted signals in a selected direction or directions, while suppressing the transmitted signals in other directions. Similarly, on the receive-side, a receiver can amplify signals from a selected direction or directions, while suppressing unwanted signals from other directions.

Multi-SIM operation

A multi-USIM (MUSIM) UE has two or more subscriptions for different services (e.g., use one individual subscription and one family circle plan). Each USIM or SIM may be associated with one subscription. Different USIM or SIM in the UE may be associated with or belong to or registered with the same operator or different operators. In one MUSIM scenario the UE may be in radio resource control (RRC) idle or inactive with respect to (wrt) all the registered networks. In this case the UE need to monitor and receive paging from more than one network. In another MUSIM scenario the UE may be in RRC idle or inactive wrt one of the registered networks while in RRC connected wrt to another network. In this case the UE need to monitor and receive paging from one network while receiving/transmitting data in another network.

In 3GPP Release 17, the focus was standardizing Multi-USIM for UEs having a single transmitter (1TX) and a single receiver (1RX), or a single transmitter and dual receivers (2RX). This means that the UE cannot communicate in two networks at the same time. MUSIM gaps, similar to the measurement gaps described in Section 4, were therefore defined which enable the UE to be connected to one network but (temporarily) switch to the other network, e.g., to monitor paging or to perform measurements in that network. The 3GPP specification defines both periodic and aperiodic MUSIM gaps.

Measurements.

The UE performs measurements on one or more DL and/or UL reference signal (RS) of one or more cells in different UE activity states e.g. RRC idle state, RRC inactive state, RRC connected state etc. The measured cell may belong to or operate on the same carrier frequency as of the serving cell (e.g. intra-frequency carrier) or it may belong to or operate on different carrier frequency as of the serving cell (e.g. non-serving carrier frequency). Examples of RS are discovery signal or discovery reference signal (DRS), CSI-RS, CRS, DMRS, SRS, signals in SS/PBCH block (SSB), PSS, SSS etc. Each SSB carries NR-PSS, NR-SSS and NR-PBCH in 4 successive symbols. One or multiple SSBs are transmit in one SSB burst which is repeated with certain periodicity e.g. 5 ms, 10 ms, 20 ms, 40 ms, 80 ms and 160 ms. The UE is configured with information about SSB on cells of certain carrier frequency by one or more SS/PBCH block measurement timing configuration (SMTC) configurations. The SMTC configuration comprising parameters such as SMTC periodicity, SMTC occasion length in time or duration, SMTC time offset wrt reference time, e.g. serving cell’s SFN, etc. Therefore, SMTC occasion may also occur with certain periodicity e.g. 5 ms, 10 ms, 20 ms, 40 ms, 80 ms and 160 ms.

A measurement may also be called RRM measurement. The measurement may be used for one or more procedures e.g. mobility, positioning, self-organizing network (SON), minimization of drive test (MDT) etc. Examples of measurements are cell identification (e.g. PCI acquisition, cell detection), Reference Symbol Received Power (RSRP), Reference Symbol Received Quality (RSRQ), secondary synchronization RSRP (SS-RSRP), SS-RSRQ, SINR, RS-SINR, SS-SINR, CSI-RSRP, CSI-RSRQ, acquisition of system information (SI), cell global ID (CGI) acquisition, Reference Signal Time Difference (RSTD), UE RX-TX time difference measurement, radio link quality, Radio Link Monitoring (RLM), which consists of Out of Synchronization (out of sync) detection and In Synchronization (in-sync) detection, Layer-1 RSRP (L1-RSRP), Layer-1 SINR (L1-SINR) etc.

UE Operation in RRC _IDLE and RRCJNACTIVE states

In RRCJDLE the UE monitors the paging channels for core network-initiated paging. In RRCJNACTIVE the UE also monitors paging channels for RAN-initiated paging. In RRCJNACTIVE the UE can move within an area configured by NG-RAN (the RAN without notifying NG-RAN. The UE in RRCJDLE or RRCJNACTIVE typically monitors paging channels during one Paging Occasion (PO) per DRX cycle in the serving cell. This is called as the paging DRX cycle, which is configured by the network. The RRCJNACTIVE UEs however may look for its RAN identity in the RRCJDLE DRX occasions (overlapping with RRCJNACTIVE DRX occasions) in case the network pages the UE. The different PCs in a DRX cycle is configurable via system information and the network may distribute UEs to the PCs based on their IDs. A PO is a set of DL control channel, e.g. PDCCH, monitoring occasions and may consist of one or more time resources (e.g. time slots, subframes etc). The UE may further monitor and receive system information (SI) of a cell. The paging occasions in the two states (RRRC IDLE/INACTIVE state) are multiples of each other; e.g. the RRCJNACTIVE DRX cycles might be 1 .28 seconds while RRCJDLE state DRX occasions are once per 2.56 seconds; however in this case they coincide every second occasion. Examples of SI are master information block (MIB), one or more system information block (SIB) etc. MIB and SIB are mapped or transmitted on physical channels such as PBCH and PDSCH respectively. The UE may further monitor and receive short messages.

In RRCJDLE and RRCJNACTIVE, the UE can perform serving cell evaluation, cell selection, and cell reselection including detection and measurements. In RRCJDLE or RRCJNACTIVE, the UE measures the serving cell (e.g. SS-RSRP and SS-RSRQ level of the serving cell) and based on the serving cell measurement evaluates the cell selection criterion S defined in TS 38.304 v17.2.0 for the serving cell at least once every M1*N1 DRX cycle; where N1 is the scaling factor given in Table 1 and:

• M1=2 if SMTC periodicity (TSMTC) > 20 ms and DRX cycle < 0.64 second,

• otherwise M 1=1.

The UE filters each of the serving cell measurements (e.g. SS-RSRP and SS- RSRQ measurements of the serving cell) using at least 2 measurements. Within the set of measurements used for the filtering, at least two measurements shall be spaced by, at least DRX cycle/2. If the UE has evaluated according to Table 1 , that in Nserv consecutive DRX cycles the serving cell does not fulfil the cell selection criterion S defined in TS 38.304 v17.2.0, then the UE shall initiate the measurements of all neighbour cells indicated by the serving cell, regardless of the measurement rules currently limiting UE measurement activities.

Table 1 : Evaluation of serving cell during N_serv

Another example of requirements for different NR intra-frequency measurements (e.g. NR cell identification, SS-RSRP, SS-RSRQ etc) performed by the UE in RRCJDLE and RRCJNACTIVE is shown in table 2. The UE identifies new intra-frequency cells and perform SS-RSRP and SS-RSRQ measurements of the identified intra-frequency cells within Tdetect,NRjntra. The UE measures SS-RSRP and SS-RSRQ of the identified intra- frequency cells at least every Tmeasure.NRjntra. The UE evaluates an identified cell for cell reselection within T_evaiuate,N _intra. SS-RSRP and SS-RSRQ of the identified intra-frequency cells at least every Tmeasure.NRjntra. The UE filters SS-RSRP and SS-RSRQ measurements of each measured intra-frequency cell using at least 2 measurements. Within the set of measurements used for the filtering, at least two measurements shall be spaced by at least Tmeasure,NR_lntra/2.

The UE shall not consider a NR neighbour cell in cell reselection if it is indicated as not allowed in the measurement control system information of the serving cell.

Similar requirements are specified for NR inter-frequency measurements (e.g. cell identification, SS-RSRP, SS-RSRQ, etc.) and inter-RAT measurements (e.g. LTE cell identification, LTE RSRP, LTE RSRQ, etc.) performed by the UE in RRCJDLE and RRC INACTIVE.

Table 2: Intra-frequency cell reselection requirements in NR: T_detect,NR_intra,

Tmeasure.NR ntra and Tevaluate.NRJntra

Measurement gaps

Measurement gap pattern (MGP) is used by the UE for performing measurements on cells of the non-serving carriers (e.g., inter-frequency carrier, inter-RAT carriers etc.). In NR gaps are also used for measurements on cells of the serving carrier in some scenarios, e.g., if the measured signals (e.g., SSB) are outside the bandwidth part (BWP) of the serving cell. The UE is scheduled in the serving cell only within the BWP. During the gap the UE cannot be scheduled for receiving/transmitting signals in the serving cell.

A measurement gap pattern is characterized or defined by several parameters: measurement gap length (MGL), measurement gap repetition period (MGRP), measurement gap time offset (MGTO) wrt reference time, e.g., slot offset wrt serving cell’s system frame number (SFN) such as SFN = 0, measurement gap timing advance (MGTA) etc. An example of MGP is shown in figure 1. Examples of MGL are 1 .5, 3, 3.5, 4, 5.5, 6, 10, 20 ms etc. Examples of MGRP are 20, 40, 80, 160, 320, 640, 1280, 2560 ms. Such type of MGP is configured by the network node and is also called as network controlled or network configurable MGP. Therefore, the serving base station is fully aware of the timing of each gap within the MGP.

Fig. 1 : An example of the measurement gap pattern in NR.

In NR there are two major categories of MGPs: per-UE measurement gap patterns and per-FR measurement gap patterns. In NR the spectrum is divided into two frequency ranges namely FR1 and FR2. FR1 is currently defined from 410 MHz to 7125 MHz. FR2 range is currently defined from 24250 MHz to 52600 MHz. In another example FR2 range can be from 24250 MHz to 71000 MHz, where the frequency range 24250-52600MHz is called FR2-1 and frequency range 52600-71000 MHz is called FR2-2. The FR2 range is also interchangeably called as millimeter wave (mmwave) and corresponding bands in FR2 are called as mmwave bands. In future more frequency ranges can be specified e.g. FR3. An example of FR3 is frequency ranging between 7125 MHz and 24250 MHz.

When configured with per-UE MGP, the UE creates gaps on all the serving cells (e.g. PCell, PSCell, SCells etc) regardless of their frequency range. The per-UE MGP can be used by the UE for performing measurements on cells of any carrier frequency belonging to any RAT (e.g., 5G NR, 4G LTE/LTE-advanced, 3G WCDMA/HSPA/CDMA2000, 2G GSM) or frequency range (FR). When configured with per-FR MGP (if UE supports this capability), the UE creates gaps only on the serving cells of the indicated FR whose carriers are to be measured. For example, if the UE is configured with per-FR1 MGP then the UE creates measurement gaps only on serving cells (e.g. PCell, PSCell, SCells etc) of FR1 while no gaps are created on serving cells on carriers of FR2. The per-FR1 gaps can be used for measurement on cells of only FR1 carriers. Similarly, per-FR2 gaps when configured are only created on FR2 serving cells and can be used for measurement on cells of only FR2 carriers. Support for per FR gaps is a UE capability, i.e. certain UE may only support per UE gaps according to their capability.

Pre-configured measurement gaps (Pre-MG) (or Pre-MG pattern) have also been specified in Rel-17. The one or more gaps which are not used for the measurement (e.g., SSB to be measured is within the UE’s active BWP) are considered to be ‘deactivated’ or the status of Pre-MG is set to ‘deactivation’. The one or more gaps which are used for the measurement (e.g., SSB to be measured is NOT within the UE’s active BWP) are considered to be ‘activated’ or the status of Pre-MG is set to ‘activation’. The UE can be scheduled with data in DL and/or in UL by the base station during the deactivated gaps in the serving cell i.e., when the status of Pre-MG is deactivated. The UE is not expected to receive any data from or transmit any data to the base station during the activated gaps in the serving cell i.e., when the status of Pre-MG is activated. An example of Pre-MG is illustrated in Fig. 2. Figure 2: An example of pre-configured measurement gap pattern in NR. Network control small gap (NCSG) pattern is used by the UE for measurements, which do not need gaps e.g. measurement performed on a serving carrier frequency when the serving cell (e.g. SCell, PSCell etc) is deactivated, on carrier frequency when UE has spare radio chain etc. To perform measurement without gap the UE can retune its receiver anytime causing unpredictable interruptions on one or more serving cells. But with NCSG, the UE is allowed to retune only during VIL1 and VIL2. This in turn ensures the interruptions occur only during VIL1 and VIL2 enabling the base station to avoid scheduling during VIL1 and VIL2. This prevents the loss of scheduling grants, UE feedback signaling such as HARQ feedback etc. VIL1 and VIL2 comprises of only 1 or few slots. However, the UE measures during the measurement length (ML) of the NCSG pattern and can be scheduled with data unless there is scheduling restriction. ML, VIL1 and VIL2 occur periodically once every VIRP. During the VIL1 and VIL2, the UE is not expected to transmit and receive any data. Where, VIL1 is the visible interruption length before the ML and VIL2 is the visible interruption length after the ML. During ML, whether the UE is expected to transmit and receive data on the corresponding serving carrier(s) depends on the scheduling restriction requirements specified in TS 38.133 v17.6.0. The NCSG configuration parameters VIL1 , ML, VIL2 and visible interruption repetition period (VIRP) are illustrated in Fig. 3. Figure 3: An example of NCSG pattern.

Concurrent measurement gap pattern (C-MGP) or interchangeably called as concurrent gaps or concurrent measurement gaps are also specified. C-MGP comprises of multiple measurement gap patterns (e.g., 2 or more MGPs) which can be configured by the network node using the same message or by different messages (e.g., the same or different RRC messages). The C-MGP typically comprises of at least two simultaneous configured measurement gap patterns (e.g., two individual MGP each of the type shown in figure 1 , in figure 2 or figure 3 or combination of any two or more types of MGP). The at least two MGPs may be configured using the same or different MGP related parameters. For example, MGL, MGRP etc. for the at least 2 MGPs may be the same or they may be different. C-MGP comprising of at least two MGPs of different types may also be called as heterogeneous concurrent measurement par pattern (H-CMP) or heterogeneous concurrent measurement gaps. The gaps of different MGPs within the C-MGP may fully or partially overlap with each other in time or they may not overlap at all with each other in time. The examples of the C-MGP comprising of 2 MGPs are shown in Fig. 4.

SUMMARY

As part of developing embodiments herein one or more problems have been identified. In a multi-USIM scenario the UE capable of multi-USIM is served by at least two serving cells which belong to different networks. The UE configured to perform one or more procedures in one or more cells of one of the networks, e.g., in NW2, requires gaps for these procedures, i.e., gaps are created on serving cell(s) in NW1. The UE will typically be configured with multiple gap patterns for different purposes, e.g., for measurements, monitoring paging, acquisition of system information etc. The gaps in NW1 can last very long especially when used for certain periodic procedures like measurements and paging monitoring e.g. in RRC idle or RRC inactive state. During the gaps, serving cell(s) in NW1 cannot schedule the UE with data. This degrades user throughput and service quality in NW1 especially when the UE is in RRC connected state in NW1.

The 3GPP Release 18 work item on multi-USIM enhancement will consider UEs with two or more receivers (RX) and/or transmitters (TX). This enables the UE to be connected to two (or more) networks at the same time. The UE typically supports multicarrier configuration e.g. CA, dual connectivity. This enhanced UE RX/TX architecture coupled with supported multi-carrier configuration can be exploited to optimize the use of gaps in multi-SIM operation. However, currently there is no such framework or mechanism exists. The discloses solutions to provide such framework enabling the network to tradeoff between number of gap patterns and multi-carrier configuration in multi-USIM operation.

An object herein is to provide improved handling of operation of a multi-SIM UE.

According to an aspect of the present disclosure, the object is achieved by providing a method performed by a UE having at least two SIMs for communication with two or more wireless communication networks, wherein the UE has a first SIM associated with a first wireless communication network with a first MGP comprising a first network node, and has a second SIM associated with a second wireless communication network with a second MGP and comprising a second network node. The UE obtains a priority indication associated with a first MG of the first MGP relative a second MG of the second MGP based on one or more rules. The UE further uses the obtained priority indication for performing one or more operational tasks provided that the first MG and the second MG collide with each other in time.

According to another aspect of the present disclosure, the object is achieved by providing a method performed by a first network node associated with a first wireless communications network configured with a first MGP, and further being associated with a first SIM of a UE. The first network node obtains a priority indication associated with a first MG of the first MGP relative a second MG of a second MGP based on one or more rules, wherein the second MGP is associated with a second network node associated with a second wireless communications network configured with the second MGP, and further being associated with a second SIM of the UE. The first network node further uses the obtained priority indication for performing one or more operational tasks provided that the first MG and the second MG collide with each other in time.

It is furthermore provided herein a computer program product comprising instructions, which, when executed on at least one processor, cause the at least one processor to carry out the methods herein, as performed by the UE and the first network node, respectively. It is additionally provided herein a computer-readable storage medium, having stored thereon a computer program product comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the methods herein, as performed by the UE and the first network node, respectively.

The object is achieved by providing a UE and a network node configured to perform the methods herein, respectively.

Embodiments herein show a UE which is configured to operate in multi-USIM scenario in which the UE’s first serving cell and a first network node managing or serving celU are comprised in a first network; and the UE’s second serving cell and a second network node managing or serving cell2 are comprised in a second network.

According to a first embodiment, the UE determines based on one or more rules a priority between a first measurement gap belonging to a first set of measurement gap patterns configured for performing at least one procedure on at least one cell in NW1 and second measurement gap belonging to a second set of measurement gap patterns configured for performing at least one procedure on at least one cell in NW2; and uses the determined priority for performing one or more operational tasks provided that MG1 and MG2 collide at least partly with each other in time. Examples of the operational tasks are transmitting information related to the priority to a network node (e.g. NN1 , NN2 etc.), cancelling one of the MGs and using the other one for performing the at least one procedure based on the determined priority etc.

According to a second embodiment, NN1 serving a UE, obtains based on one or more rules a priority between MG1 and MG2; and uses the obtained priority for performing one or more operational tasks provided that MG1 and MG2 collide with each other in time. Examples of the tasks are scheduling the UE with data during a MG if it is cancelled and not scheduling the UE with data during the MG if it is not cancelled etc.

The rules for determining the priority between the gaps may be pre-defined, determined by the UE or configured by a network node (e.g. by NN1). The MG which has lower priority is cancelled while the other MG which has higher priority can be used by the UE for performing one or more procedures. The MG which is cancelled is not used by the UE for performing one or more procedures

In one example of the rule, the priority between the gaps belonging to MGPS1 and MGPS2 is based on a configuration of MGPS1. In another example of the rule, the priority between the gaps belonging to MGPS1 and MGPS2 is based on a configuration of MGPS2. In another example of the rule, the priority between the gaps belonging to MGPS1 and MGPS2 is based on the configurations of MGPS1 and MGPS2.

Examples of the procedures are performing one or more measurements, monitoring or receiving a paging signal, receiving a SI, operating one or more signals related to a random access procedure etc.

The gaps (e.g. MG1 and MG2) are assumed to collide with each other provided that they at least partially overlap with each other in time or if the distance between them in time is below certain threshold (e.g. 4 ms).

According to embodiments herein, when there is a collision between any two gaps used for performing procedures (e.g. measurements) in different networks in multi-SIM operational scenario, the gap belonging to a MGP with a shorter MGRP on one network is cancelled (i.e. not used for performing the procedure such as measurement, paging etc), while the other gap belonging to MGP with longer MGRP in the other network is not cancelled. It is herein provided a mechanism that ensures that under collision between gaps across different networks in multi-SIM operational scenario at least one of the gaps is still used for performing a procedure. The mechanism ensures that under collision between gaps, the gaps which occur less frequently are used for performing the procedure and the gaps which occur more frequently are cancelled. This in turn enables the UE to perform the procedure, e.g., measurements, with acceptable performance in both networks. Thus, embodiments herein enable communication of multi-SIM UEs in an efficient manner in a wireless communications network, and thereby improve the overall performance of the wireless communications network and/or improve user experience.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments will now be described in more detail in relation to the enclosed drawings, in which:

Fig. 1 illustrates an example of measurement gap pattern in NR according to prior art;

Fig. 2 illustrates an example of pre-configured measurement gap pattern in NR according to prior art; Fig. 3 illustrates an example of NCSG pattern according to prior art;

Fig. 4 illustrates examples of the C-MGP comprising of 2 MGPs according to prior art;

Fig. 5 is a schematic overview depicting a wireless communications network in accordance with some embodiments of the present disclosure;

Fig. 6 is a schematic overview depicting a wireless communications network in accordance with some embodiments of the present disclosure;

Fig. 7 illustrates examples measurement gaps according to embodiments herein;

Fig. 8 is a schematic flowchart illustrating a method performed by a UE, in accordance with some embodiments;

Fig. 9 is a schematic flowchart illustrating a method performed by a network node, in accordance with some embodiments;

Fig. 10 is a block diagram depicting a UE in accordance with some embodiments;

Fig. 11 is a block diagram depicting a network node in accordance with some embodiments;

Fig. 12 illustrates a telecommunication network connected via an intermediate network to a host computer, in accordance with some embodiments;

Fig. 13 illustrates a host computer communicating via a base station with a user equipment over a partially wireless connection, in accordance with some embodiments;

Fig. 14 is a flowchart illustrating methods implemented in a communication system including a host computer, a base station, and a user equipment, in accordance with some embodiments;

Fig. 15 is another flowchart illustrating methods implemented in a communication system including a host computer, a base station, and a user equipment, in accordance with some embodiments;

Fig. 16 is another flowchart illustrating methods implemented in a communication system including a host computer, a base station, and a user equipment, in accordance with some embodiments; and

Fig. 17 is another flowchart illustrating methods implemented in a communication system including a host computer, a base station, and a user equipment, in accordance with some embodiments.

DETAILED DESCRIPTION

Embodiments herein relate to wireless communications networks in general. Fig. 5 is a schematic overview depicting a wireless communications network 10. The wireless communications network 10 comprises one or more RANs and one or more CNs. The wireless communications network 10 may use one or a number of different technologies. Embodiments herein relate to recent technology trends that are of particular interest in a New Radio (NR) context, however, embodiments are also applicable in further developments of existing wireless communications systems such as e.g. LTE or Wideband Code Division Multiple Access (WCDMA).

In the wireless communications network 10, a user equipment (UE) 102, such as a mobile station, a wireless device, a non-access point (non-AP) STA, a STA, and/or a wireless terminal, is communicating via e.g. one or more Access Networks (AN), e.g. RAN, to one or more core networks (CN). It should be understood by the skilled in the art that “UE” is a non-limiting term which means any terminal, wireless communications terminal or device, user equipment, NB-loT device, Machine Type Communication (MTC) device, Device to Device (D2D) terminal, or node, e.g. smart phone, laptop, mobile phone, sensor, relay, mobile tablets or even a small base station capable of communicating using radio communication with a radio network node within an area served by the radio network node.

The wireless communications network 10 comprises one or more first network nodes.

The wireless communications network 10 comprises a first network node 104, e.g., an access node, an access controller, a base station, e.g. a radio base station such as a gNodeB (gNB), an evolved Node B (eNB, eNode B), a NodeB, a base transceiver station, a radio remote unit, an Access Point Base Station, a base station router, a Wireless Local Area Network (WLAN) access point or an Access Point Station (AP STA), MME, AMF, a stand-alone access point, or any other network unit or node capable of communicating with a wireless device within a service area 14 served by the radio network node depending e.g., on a radio access technology and terminology used. The service area 14 may also be referred to as a beam or a beam group of a first radio access technology (RAT), such as 5G, LTE, Wi-Fi, or similar. The first network node 104 may be associated with and provide radio communication in a first wireless communications network 140, such as, e.g., a first Public Land Mobile Network (PLMN) or a first NonPublic Network (NPN). In some embodiments, the first wireless communications network 140 may be implemented as a combination of a PLMN and an NPN.

The wireless communications network 10 also comprises a second network node 106, e.g., an access node, an access controller, a base station, e.g. a radio base station such as a gNodeB (gNB), an evolved Node B (eNB, eNode B), a NodeB, a base transceiver station, a radio remote unit, an Access Point Base Station, a base station router, a Wireless Local Area Network (WLAN) access point or an Access Point Station (AP STA), MME, AMF, a stand-alone access point, or any other network unit or node capable of communicating with a wireless device within a service area 16 served by the radio network node depending e.g., on a radio access technology and terminology used. The service area 16 may also be referred to as a beam or a beam group of a first radio access technology (RAT), such as 5G, LTE, Wi-Fi, or similar. The second network node 106 may be associated with and provide radio communication in a second wireless communications network 160, such as, e.g., a second PLMN or a second NPN. In some embodiments, the second wireless communications network 160 may be implemented as a combination of a PLMN and an NPN.

Embodiments of the present disclosure relate to multi-SIM, or MUSIM, devices that can enable users to be registered to multiple networks, such as PLMNs, NPNs, or a combination thereof. For instance, UEs equipped with dual radio capabilities may enable simultaneous connection to two wireless communications networks.

As shown in Fig. 5, the UE 102 may thus be a multi-SIM UE and it may have a first SIM, shown as SIM1 , and a second SIM, shown as SIM2, though it should be appreciated that the UE 102 may have more than two SIMs. In the illustrated embodiment, the first wireless communications network 140, such as the first PLMN or NPN, is associated with the first SIM of the UE 102, and the second wireless communications network 160, such as the second PLMN or NPN, is associated with the second SIM of the wireless communication device.

The UE 102 may be registered with both the first and second wireless communications networks 140, 160, which may be respective PLMNs, NPNs, a combination of PLMN(s) and NPN(s), or any other wireless communications networks that may be of the same or different types. As used herein, a PLMN is defined as a wireless communications network that provides a combination of wireless communication services offered by an operator. As used herein, an NPN is defined as a private network that is deployed for private use by an entity such as a government, company, or another entity. In some embodiments, when the UE 102 has multiple SIMs, the different SIMs are associated with different PLMNs or NPNs. In some embodiments, the UE 102 may have more than one SIM which is associated with the same network such as a PLMN and/or NPN, e.g., the UE 102 may have two SIMs from the same operator.

Some aspects of the present disclosure may be implemented in connection with the radio resource control (RRC) protocol. In some embodiments, aspects of the present disclosure may be implemented in a cloud environment.

The UE 102 may have more than one radio, such as, e.g., both dual receive (Rx) and dual transmit (Tx) capability. The radios may support RRC Connected mode in a network, e.g., one of the first and second wireless communications networks 140, 160, without interrupting service of the other network, e.g., the other one of the first and second wireless communications networks 140, 160.

The number of Rx/Tx radio chains may play a role on how multi-SIM UEs are managed. Furthermore, different possible network configurations and a changing demand for diverse types of operations may affect the complexity of handling communications of multi-SIM UEs which may communicate with multiple wireless communications networks.

In this disclosure a term node is used which can be a network node or a user equipment (UE).

Examples of network nodes are NodeB, base station (BS), multi-standard radio (MSR) radio node such as MSR BS, eNodeB, gNodeB, MeNB, SeNB, location measurement unit (LMU), integrated access backhaul (IAB) node, network controller, radio network controller (RNC), base station controller (BSC), relay, donor node controlling relay, base transceiver station (BTS), Central Unit (e.g. in a gNB), Distributed Unit (e.g. in a gNB), Baseband Unit, Centralized Baseband, C-RAN, access point (AP), transmission points, transmission nodes, transmission reception point (TRP), RRU, RRH, nodes in distributed antenna system (DAS), core network node (e.g. MSC, MME etc.), O&M, OSS, SON, positioning node (e.g. E-SMLC),etc.

The non-limiting term UE refers to any type of wireless device communicating with a network node and/or with another UE in a cellular or mobile communication system. Examples of UE are target device, device to device (D2D) UE, vehicular to vehicular (V2V), machine type UE, internet of things (loT) capable device, machine type communication (MTC) UE or UE capable of machine to machine (M2M) communication, PDA, tablet, mobile terminals, smart phone, laptop embedded equipment (LEE), laptop mounted equipment (LME), USB dongles etc.

The term radio access technology, or RAT, may refer to any RAT e.g. UTRA, E- UTRA, narrow band internet of things (NB-loT), WiFi, Bluetooth, next generation RAT, New Radio (NR), 4G, 5G, etc. Any of the equipment denoted by the term node, network node or radio network node may be capable of supporting a single or multiple RATs. The term signal or radio signal used herein can be any physical signal or physical channel. Examples of DL physical signals are reference signal (RS) such as PSS, SSS, CSI-RS, DMRS signals in SS/PBCH block (SSB), discovery reference signal (DRS), CRS, PRS etc. RS may be periodic e.g. RS occasion carrying one or more RSs may occur with certain periodicity e.g. 20 ms, 40 ms etc. The RS may also be aperiodic. Each SSB carries NR-PSS, NR-SSS and NR-PBCH in 4 successive symbols. One or multiple SSBs are transmit in one SSB burst which is repeated with certain periodicity e.g. 5 ms, 10 ms, 20 ms, 40 ms, 80 ms and 160 ms. The UE is configured with information about SSB on cells of certain carrier frequency by one or more SS/PBCH block measurement timing configuration (SMTC) configurations. The SMTC configuration comprises parameters such as SMTC periodicity, SMTC occasion length in time or duration, SMTC time offset wrt reference time (e.g. serving cell’s SFN) etc. Therefore, SMTC occasion may also occur with certain periodicity e.g. 5 ms, 10 ms, 20 ms, 40 ms, 80 ms and 160 ms. Examples of UL physical signals are reference signal such as SRS, DMRS etc. The term physical channel refers to any channel carrying higher layer information e.g. data, control etc. Examples of physical channels are PBCH, NPBCH, PDCCH, PDSCH, sPUCCH, sPDSCH. sPUCCH. sPUSCH, MPDCCH, NPDCCH, NPDSCH, E-PDCCH, PUSCH, PUCCH, NPUSCH etc.

The term time resource used herein may correspond to any type of physical resource or radio resource expressed in terms of length of time. Examples of time resources are: symbol, sub-slot, mini-slot, slot or time slot, subframe, radio frame, TTI, interleaving time, SFN cycle, hyper-SFN cycle etc.

The term multi-USIM used herein may also be called as multi-subscription, multi- SIM or dual SIM or dual-USIM etc. The term USIM may also be simply called as SIM. For consistency, multi-USIM term may be used hereinafter. Each USIM (or SIM) in the UE may be associated with at least subscription of a mobile network operator (MNO).

The term measurement gap configuration (MGC) used herein may refer to one or more measurement gap patterns (MGPs), which are configured or can be configured for the UE for one or more purposes or procedures or operations e.g. performing measurements, monitoring and/or receiving paging, monitoring and/or receiving SI, monitoring and/or receiving short messages, operating (transmitting and/or receiving) random access (RA) related signals (e.g. preamble, RA response message etc) etc. MGPs may be any type of gap pattern, e.g., legacy MGP, Pre-MGP, NCSG etc. One or more MGPs may be periodic, aperiodic or semi-persistent. The MGC may also be called as MUSIM MGC (MMGC) as they are used in the MUSIM scenario. The MGP may also be called as MUSIM MGP (MMGP).

Scenario description.

The scenario comprises a UE served by at least two cells: a first cell (celH) and a second cell (cell2). Celli and cell2 may operate on or belong to or configured using: a first carrier frequency (F1) and a second carrier frequency (F2) respectively. In one example, F1 and F2 are different carrier frequencies (e.g. with different ARFCNs). In another example, F1 and F2 are the same carrier frequencies (e.g. with same ARFCN). The carrier frequency is also called as component carrier (CC), frequency layer, serving carrier, frequency channel etc. The carrier frequency related information is signaled to the UE using a channel number e.g., ARFCN, NR-ARFCN etc. F1 and F2 may belong to the same or different frequency bands. The coverage areas of celU and cell2 may fully overlap or may not overlap at all or may partially with respect to each other.

CelU is served or managed or controlled by a first network node (NN1) which is comprised in a first network (NW1). Cell2 is served or managed or controlled by a second network node (NN2) which is comprised in a second network (NW2). Therefore, the UE is served by or managed by the at least two networks (NW1 and NW2). In one example, NW1 and NW2 may be managed by or belong to the same operator. In another example, NW1 and NW2 may be managed by or belong to different operators. This is realized by the UE capable of multi-USIM operation, i.e., supporting at least 2 USIMs. For example, one of the supported USIM is associated with subscription to NW1 , while the other supported USIM is associated with subscription to NW2. In one scenario the UE is served by one serving cell in each NW, e.g., by celU and cell2 in NW1 and NW2 respectively. In another exemplary scenario the UE may further be served by more than one cell in NW1 and/or by more than one cell in NW2.

Examples of cells are serving cell, neighbor cell, non-serving cell etc. In multicarrier (MC) operation the UE is served by more than one serving cells. Each cell may operate or belong to a carrier frequency.

The UE may be served by celU and cell2 during at least partially overlapping time period. The UE may also be served by more than one cells in NW1 and/or in NW2 e.g. when the UE is configured with multicarrier (MC) configuration by a network node.

NN1 and NN2 may be two different logical network nodes as well as two different physical network nodes. In another example NN1 and NN2 may be two different logical network nodes but may be comprised in the same physical network node. NN1 and NN2 may or may not be physically located at the same site. In one example the UE 102 may be configured to operate in the same RRC activity state wrt celll and cell2 during at least partially overlapping time. In another example the UE 102 may be configured to operate in different RRC activity states wrt celll and cell2 during at least partially overlapping time. Examples of RRC activity states are low activity RRC state, high activity state etc. In low activity RRC state the UE may typically be configured to operate using a DRX cycle which is equal to or larger than certain threshold, e.g., 320 ms or longer. In low activity RRC state the UE may further be configured with extended DRX cycle (eDRX). In high activity RRC state the UE may or may not be configured to operate with a DRX cycle or may be configured with any DRX cycle when configured. Examples of low activity RRC state are RRC idle state, RRC inactive state etc. An examples of high activity RRC state is RRC connected state etc.

In some embodiments the UE is served by celll in NN1 in high activity RRC state (e.g., RRC connected state) but is served by cell2 in NN2 any of the low activity state and high activity RRC state. In some embodiments the UE is served by celll in NN1 in high activity RRC state but is served by cell2 in NN2 in any of the low activity states (e.g., RRC idle state or RRC inactive state).

In some embodiments, NW1 is a primary network and NW2 is a secondary network. In this case, the UE is configured by NN1 with one set of MGPs for performing the procedures on cells of NW1 and also with another set of MGPs for performing the procedures on cells of NW2. The former set of the MGPs may also be called as legacy MGP set (LMGPS) and latter set of the MGPs may also be called as MUSIM MGP set (MMGPS).

Fig. 6 illustrates an example of multi-USIM operation of the UE where the UE is served at celll and cell2 in the operators’ network, NN1 and NN2 respectively. The scenario described in this section and illustrated in figure 6 is applicable to all the embodiments described hereinafter. Figure 6 shows an example of multi-USIM capable UE being served by two different cells (celll and cell2) belonging to two different mobile networks (NW1 and NW2).

Embodiment # 1 : Method in a UE of determining gap priority and using it for operational tasks.

According to a first embodiment, the UE 102: obtains or determines based on one or more rules a priority between a first measurement gap (MG1) belonging to a first set of measurement gap patterns (MGPS1) configured for performing at least one procedure on at least one cell in NW1 and second measurement gap (MG2) belonging to a second set of measurement gap patterns (MGPS2) configured for performing at least one procedure on at least one cell in NW2; and uses the determined priority for performing one or more operational tasks provided that MG1 and MG2 collide with each other in time.

The UE 102 is further configured by a network node (e.g. by NN1) with MGPS1 and MGPS2. For example, the UE 102 may be configured with MGPS1 and MGPS2 before the UE 102 determines the priority between MG1 and MG2. MG1 and MG2 may refer to any pair of MGs, which belong to a first MGP (MGP1) and a second MGP (MGP2) respectively, and that are close to each other in time. MGP1 and MGP2 belong to MGPS1 and MGPS2 respectively. MGPS1 comprises of M number of measurement gap patterns (MGP) and MGPS2 comprises of N number of MGPs. Where M > 1 and N > 1 . Therefore, MGPS1 and/or MGPS2 can also be configured as concurrent measurement gaps (homogeneous or heterogeneous) e.g. when M > 1 and/or N > 1 respectively. The term MGP used herein may refer to any type of measurement gap pattern e.g. legacy MGP, Pre-MG or NCSG. An example illustrating MGPS1 with M=1 and MGPS2 with N=1 is shown in Fig. 7. The figure also illustrates the magnitude of the shortest distance (D) between the MGs, which determines whether the MGs can be considered as colliding or not (described later).

Fig. 7: An example of MGPS1 with one MGP (i.e. M=1) and MGPS2 with one MGP (i.e. 1X1=1). The magnitude of distance between any two closes gaps (MG1 and MG2) in time is D.

The priority of a measurement gap (MG) can be expressed in terms of a numerical value e.g. integer such as 1 , 2, 3 etc. In one example, the lowest numerical value may indicate the highest priority and the highest numerical value may indicate the lowest priority. For example, if MG1 and MG2 are associated with priority values of 1 and 2 respectively, then MG1 has higher priority compared to the priority of MG2. In another example, if MG1 and MG2 are associated with priority values of 2 and 1 respectively, then MG1 has lower priority compared to the priority of MG2. The term MG may also be called as a measurement gap (MG) occasion, a MG opportunity etc.

Examples of the operational tasks performed by the UE 10 are: • transmitting information related to the determined priority to a network node (e.g. NN1 , NN2 etc.) e.g. via RRC, MAC-CE message etc. For example, the information may indicate the determined priority level associated with the MGs. The information may be sent as part of a UE assistance information (UAI). In one example, the transmitted information may provide a recommendation to the network node. In this case the network node (e.g. NN1) may further decide whether to follow the UE 10 recommendation or configure the UE 10 with different set of priorities associated with the MGs e.g. MG1 , MG2 etc. In another example, the transmitted information may indicate that it is followed by both the UE and the network node (e.g. NN1 , NN2 etc).

• cancelling one of the MGs and using the other one for performing the at least one procedure based on the determined priority. For example, the UE 102 cancels one of MG1 and MG2, whichever has lower priority and uses the other one of MG1 and MG2, whichever has higher priority for performing the at least one procedure (e.g. for measurements, monitoring paging etc). The cancelled MG is not used by the UE for performing any procedure. The term cancelling the MG may also be called as discarding, dropping or not using the MG.

Any pair of MGs, e.g. MG1 and MG2, belonging to their respective MGPs in their respective MGPSs are assumed or considered to be colliding with each provided that at least one of the following conditions is met:

• MG1 and MG2 at least partially overlap with each in time domain.

• The magnitude of the difference between ending point of MG1 in time domain and the starting of MG2 in time domain is less than or equal to certain threshold (H11).

• The magnitude of the difference between ending point of MG2 in time domain and the starting of MG1 in time domain is less than or equal to certain threshold (H12).

The term colliding MGs may also be called as overlapping MGs or MGs in close proximity in time domain.

Examples of rule for determining MG priority:

The one or more rules for determining the priority associated with different MGs belonging to different MGPSs may be pre-defined or determined by the UE or configured by the network node. Several examples of rules for determining the priority associated with different MGs belonging to different MGPSs are provided below:

1. In one example of the rule, the priority between the MGs (e.g. between MG1 and MG2) is determined by the UE based on one or more parameters associated with the configuration of MGPS1 . Examples of the one or more parameters related to the configuration of MGPS1 are value of M (i.e. number of MGPs configured within MGPS1), MGRP associated with MG1 , MGL of MG1 etc. This rule is further elaborated with examples below: a) In one example the priority levels of MG1 and MG2 depends on a relation between M and a threshold. In one specific example, MG1 has higher priority over MG2 if M < H21 ; otherwise MG1 has lower priority over MG2. In another specific example, MG1 has higher priority over MG2 if M > H22; otherwise MG1 has lower priority over MG2. Examples of thresholds, H21 and H22 are 2, 3 etc. b) In another example the priority levels of MG1 and MG2 depends on a relation between a first MGRP (MGRP1) of a first MGP (MGP1) associated with MG1 and a threshold. In one specific example, MG1 has lower priority over MG2 if MGRP1 < H23; otherwise MG1 has higher priority over MG2. In another specific example, MG1 has higher priority over MG2 if MGRP1 > H24; otherwise MG1 has higher priority over MG2. Examples of thresholds, H23 and H24 are 80 ms, 160 ms etc. c) In another example the priority levels of MG1 and MG2 depends on a relation between a first MGL (MGL1) of MG1 and a threshold. In one specific example, MG1 has higher priority over MG2 if MGL1 < H25; otherwise MG1 has lower priority over MG2. In another specific example, MG1 has higher priority over MG2 if MGL1 > H26; otherwise MG1 has lower priority over MG2. Examples of thresholds, H25 and H26 are 6 ms, 10 ms etc. In another example of the rule, the priority between the MGs (e.g. between MG1 and MG2) is determined by the UE based on one or more parameters associated with the configuration of MGPS2. Examples of the one or more parameters related to the configuration of MGPS2 are value of N (i.e. number of MGPs configured within MGPS2), MGRP associated with MG2, MGL of MG2 etc. This rule is further elaborated with examples below: a) In one example the priority levels of MG1 and MG2 depends on a relation between N and a threshold. In one specific example, MG2 has higher priority over MG1 if M < H31 ; otherwise MG2 has lower priority over MG1 . In another specific example, MG2 has higher priority over MG2 if N > H32; otherwise MG2 has lower priority over MG1. Examples of thresholds, H31 , H32 are 2, 3 etc. b) In another example the priority levels of MG1 and MG2 depends on a relation between a second MGRP (MGRP2) of a second MGP (MGP2) associated with MG2 and a threshold. In one specific example, MG2 has lower priority over MG2 if MGRP2 < H33; otherwise MG2 has higher priority over MG1 . In another specific example, MG2 has higher priority over MG1 if MGRP2 > H34; otherwise MG2 has higher priority over MG1 . Examples of thresholds, H33 and H34 are 80ms, 160 ms, 320 ms, 640 ms etc. c) In another example the priority levels of MG1 and MG2 depends on a relation between a second MGL (MGL2) of MG1 and a threshold. In one specific example, MG2 has higher priority over MG1 if MGL2 < H35; otherwise MG2 has lower priority over MG1. In another specific example, MG2 has higher priority over MG1 if MGL2 > H36; otherwise MG2 has lower priority over MG1. Examples of thresholds, H35 and H36 are 6 ms, 10 ms etc. In another example of the rule, the priority between the MGs (e.g. between MG1 and MG2) is determined by the UE based on one or more parameters associated with the configurations of both MGPS1 and MGPS2. This rule is further elaborated with examples below: a) In one example the priority levels of MG1 and MG2 depends on a relation between M (i.e number of MGPs in MGPS1) and a N (i.e number of MGPs in MGPS2). In one specific example, MG1 has higher priority over MG2 if M < N; otherwise MG1 has lower priority over MG2. In another specific example, MG1 has higher priority over MG2 if M < N; otherwise MG1 has lower priority over MG2. In another specific example, MG1 has higher priority over MG2 if M = N; otherwise MG1 has lower priority over MG2. In another specific example, MG2 has higher priority over MG1 if M = N; otherwise MG2 has lower priority over MG1. In another specific example, MG1 has higher priority over MG2 if [M < (N+H41)]; otherwise MG1 has lower priority over MG2. In another specific example, MG1 has higher priority over MG2 if [(M+H42) < (N)]; otherwise MG1 has lower priority over MG2. In another specific example, MG1 has higher priority over MG2 if [(M+H43) < (N+H44)]); otherwise MG1 has lower priority over MG2. The parameters H41 , H42, H43 and H44 are thresholds and can be positive or negative integer values. b) In another example the priority levels of MG1 and MG2 depend on a relation between M and a threshold (H45) and between N and a threshold (H46). In one specific example, MG1 has higher priority over MG1 if [(M < H45) AND (N > H46)]; otherwise MG1 has lower priority over MG2. Examples of H45, H46 are 2, 3 etc. In one specific example if [M=1 AND (N > 1)], then MG1 is of higher priority compared to that of MG2; otherwise MG1 is of lower priority compared to that of MG2. c) In another example the priority levels of MG1 and MG2 depends on a relation between MGRP1 and MGRP2. In one specific example, MG1 has higher priority over MG2 if (MGRP1>MGRP2); otherwise MG1 has lower priority over MG2. In another specific example, MG1 has higher priority over MG2 if [MGRP1 > (MGRP2+H47)]; otherwise MG1 has lower priority over MG2. In another specific example, MG1 has higher priority over MG2 if [(MGRP1+H48) > MGRP2]; otherwise MG1 has lower priority over MG2. In another specific example, MG1 has higher priority over MG2 if [(MGRP1+H49) > (MGRP2+H50)]; otherwise MG1 has lower priority over MG2. Examples of H47 and H48 are 160 ms, 320 ms, 640 ms etc. The parameters H47, H48, H49 and H50 are thresholds. In one example the thresholds can be positive or negative integer values. In another example the thresholds can be positive or negative values which are multiple of 10 ms. In another example the thresholds can be positive or negative values with magnitude equal to any MGRP. d) In another example the priority levels of MG1 and MG2 depends on a relation between MGRP1 and a threshold (H51) and MGRP2 and a threshold (H52). In one specific example, MG1 has higher priority over MG2 if [(MGRP1 > H51) AND (MGRP2 < H52)]; otherwise MG1 has lower priority over MG2. Examples of H51 and H52 are 160 ms, 320 ms, 640 ms etc. e) In another example the priority levels of MG1 and MG2 depends on a relation between MGL1 and MGL2. In one specific example, MG1 has higher priority over MG1 if MGL1 < MGL2; otherwise MG2 has lower priority over MG1 . In another specific example, MG1 has higher priority over MG1 if [MGL1 < (MGL2+H53)]; otherwise MG1 has lower priority over MG1 . In another specific example, MG1 has higher priority over MG1 if [(MGL1+H54) < (MGL2)]; otherwise MG1 has lower priority over MG 1 . In another specific example, MG1 has higher priority over MG1 if [(MGL1+H55) < (MGL2+H56)]; otherwise MG1 has lower priority over MG1. The parameters H53, H54, H55 and H56 are thresholds and can be positive or negative integer values. f) In another example the priority levels of MG1 and MG2 depends on a relation between MGL1 and a threshold (H58) and MGL2 and a threshold (H59). In one specific example, MG1 has higher priority over MG2 if [(MGL1 < H58) AND (MGL2 > H59)]; otherwise MG1 has lower priority over MG2. Examples of H58 and H59 are 6 ms, 10 ms etc. In another example of the rule, the UE autonomously determines the priority between the MGs, e.g., between MG1 and MG2, provided that at least one of the following conditions are met. In this case the UE further transmits the information about the determined priority levels associated with MG1 and MG2 to a network node, e.g., NN1 , NN2 etc., e.g., in a UE assistance information (UAI). In one example the network node also follows the UE indicated priority levels, e.g., for scheduling data etc. In another example the network node may override the UE indicated priority levels (e.g. for scheduling data etc) and configure the UE with different priority levels for MG1 and MG2: a) In one example of the condition, the UE autonomously determines the priority levels of MG1 and MG2 depends on the one or more parameters related to the configuration of MGPS1 ; and further transmits the determined priority information to a network node. This is explained with examples below:

I. In one example, the UE autonomously determines the priority levels of MG1 and MG2 based on M and a threshold. In one example, the UE autonomously determines the priority levels if M < H61 ; otherwise, the UE does not autonomously determine the priority levels. In the latter case the UE may follow a rule, which is predefined or configured by the network. In another example, the UE autonomously determines the priority levels if M > H62; otherwise, the UE does not autonomously determine the priority levels. In the latter case the UE may follow a rule, which is pre-defined or configured by the network. In another example, the UE autonomously determines the priority levels if MGPS1 is concurrent measurement gaps (e.g. when M>1); otherwise, the UE does not autonomously determine the priority levels. Examples of the threshold, H61 are 2, 3, 4 etc. Examples of the threshold, H62 are 1 , 2, 3, 4 etc.

II. In another example, the UE autonomously determines the priority levels of MG1 and MG2 based on MGRP1 and a threshold. In one example, the UE autonomously determines the priority levels if MGRP1 < H63; otherwise, the UE does not autonomously determine the priority levels. In the latter case the UE may follow a rule, which is pre-defined or configured by the network. In another example, the UE autonomously determines the priority levels if MGRP1 > H64; otherwise, the UE does not autonomously determine the priority levels. In the latter case the UE may follow a rule, which is pre-defined or configured by the network. Examples of the threshold, H63, H64 are 40, 80, 160 ms etc.

III. In another example, the UE autonomously determines the priority levels of MG1 and MG2 based on MGL1 and a threshold. In one example, the UE autonomously determines the priority levels if MGL1 < H65; otherwise, the UE does not autonomously determine the priority levels. In the latter case the UE may follow a rule, which is pre-defined or configured by the network. In another example, the UE autonomously determines the priority levels if MGL1 > H66; otherwise, the UE does not autonomously determine the priority levels. In the latter case the UE may follow a rule, which is predefined or configured by the network. Examples of the threshold, H65, H66 are 6, 10 ms etc. b) In another example of the condition, the UE autonomously determines the priority levels of MG1 and MG2 depends on the one or more parameters related to the configuration of MGPS2; and further transmits the determined priority information to a network node. This is explained with examples below:

I. In one example, the UE autonomously determines the priority levels of MG1 and MG2 based on N and a threshold. In one example, the UE autonomously determines the priority levels if N < H71 ; otherwise, the UE does not autonomously determine the priority levels. In the latter case the UE may follow a rule, which is pre- defined or configured by the network. In another example, the UE autonomously determines the priority levels if N > H72; otherwise, the UE does not autonomously determine the priority levels. In the latter case the UE may follow a rule, which is pre-defined or configured by the network. In another example, the UE autonomously determines the priority levels if MGPS2 is concurrent measurement gaps (e.g. when N>1); otherwise, the UE does not autonomously determine the priority levels. Examples of the threshold, H71 are 2, 3, 4 etc. Examples of the threshold, H72 are 1 , 2, 3, 4 etc.

II. In another example, the UE autonomously determines the priority levels of MG1 and MG2 based on MGRP2 and a threshold. In one example, the UE autonomously determines the priority levels if MGRP2 < H73; otherwise, the UE does not autonomously determine the priority levels. In the latter case the UE may follow a rule, which is pre-defined or configured by the network. In another example, the UE autonomously determines the priority levels if MGRP2 > H74; otherwise, the UE does not autonomously determine the priority levels. In the latter case the UE may follow a rule, which is pre-defined or configured by the network. Examples of the threshold, H73, H74 are 40, 80, 160 ms etc.

III. In another example, the UE autonomously determines the priority levels of MG1 and MG2 based on MGL2 and a threshold. In one example, the UE autonomously determines the priority levels if MGL2 < H75; otherwise, the UE does not autonomously determine the priority levels. In the latter case the UE may follow a rule, which is pre-defined or configured by the network. In another example, the UE autonomously determines the priority levels if MGL2 > H76; otherwise, the UE does not autonomously determine the priority levels. In the latter case the UE may follow a rule, which is predefined or configured by the network. Examples of the threshold, H75, H76 are 6, 10 ms etc. c) In another example of the condition, the UE autonomously determines the priority levels of MG1 and MG2 depends on the one or more parameters related to the configuration of MGPS2 and the one or more parameters related to the configuration of MGPS1 ; and further transmits the determined priority information to a network node. This is explained with examples below:

I. In one example, the UE autonomously determines the priority levels of MG1 and MG2 based on M and its respective threshold and based on M and its respective threshold. In one example, the UE autonomously determines the priority levels if [(M>H81) AND (N>H82)]; otherwise, the UE does not autonomously determine the priority levels. In the latter case the UE may follow a rule, which is pre-defined or configured by the network. In another example, the UE autonomously determines the priority levels if [(M<H83) AND (N<H84)]; otherwise, the UE does not autonomously determine the priority levels. In the latter case the UE may follow a rule, which is pre-defined or configured by the network. In another example, the UE autonomously determines the priority levels if [(M>H85) AND (N<H86)]; otherwise, the UE does not autonomously determine the priority levels. In the latter case the UE may follow a rule, which is pre-defined or configured by the network. In another example, the UE autonomously determines the priority levels if [(M<H87) AND (N>H88)]; otherwise, the UE does not autonomously determine the priority levels. In the latter case the UE may follow a rule, which is pre-defined or configured by the network. Examples of the thresholds, H81 , H82, H83, H85, H88 are 1 , 2, 3, 4 etc. Examples of the thresholds, H83, H84, H86, H87 are 1 , 2, 3, 4 etc.

II. In another example, the UE autonomously determines the priority levels of MG1 and MG2 based on MGRP1 and its respective threshold and MGRP2 and its respective threshold. In one example, the UE autonomously determines the priority levels if [(MGRP1 < H89) AND (MGRP1 < H90)]; otherwise, the UE does not autonomously determine the priority levels. In the latter case the UE may follow a rule, which is pre-defined or configured by the network. In another example, the UE autonomously determines the priority levels if [(MGRP1 > H91) AND (MGRP1 > H92)]; otherwise, the UE does not autonomously determine the priority levels. In the latter case the UE may follow a rule, which is pre-defined or configured by the network. In another example, the UE autonomously determines the priority levels if [(MGRP1 < H93) AND (MGRP1 > H94)]; otherwise, the UE does not autonomously determine the priority levels. In the latter case the UE may follow a rule, which is pre-defined or configured by the network. In another example, the UE autonomously determines the priority levels if [(MGRP1 > H94) AND (MGRP1 < H95)]; otherwise, the UE does not autonomously determine the priority levels. In the latter case the UE may follow a rule, which is pre-defined or configured by the network. Examples of the thresholds, H89, H90, H91 , H92, H93, H94, H95 are 40, 80, 160 ms etc.

III. In another example, the UE autonomously determines the priority levels of MG1 and MG2 based on MGL1 and its respective threshold and MGL2 and its respective threshold. In one example, the UE autonomously determines the priority levels if [(MGL1 < H96) AND (MGL2 < H97)]; otherwise, the UE does not autonomously determine the priority levels. In the latter case the UE may follow a rule, which is pre-defined or configured by the network. In another example, the UE autonomously determines the priority levels if [(MGL1 > H98) AND (MGL2 > H99)]; otherwise, the UE does not autonomously determine the priority levels. In the latter case the UE may follow a rule, which is pre-defined or configured by the network. In another example, the UE autonomously determines the priority levels if [(MGL1 < H100) AND (MGL2 > H101)]; otherwise, the UE does not autonomously determine the priority levels. In the latter case the UE may follow a rule, which is pre-defined or configured by the network. In another example, the UE autonomously determines the priority levels if [(MGL1 > H102) AND (MGL2 < H103)]; otherwise, the UE does not autonomously determine the priority levels. In the latter case the UE may follow a rule, which is pre-defined or configured by the network. Examples of the thresholds, H96, H97, H98, H99, H100, H101 , H102 are 6, 10 ms etc. In another example of the rule, the priority between the MGs is pre-defined or the NN1 of NW1 autonomously determines the priority within the following scenarios. a) In one example, the UE doesn’t indicate the priority information to NN1 of NW1 . NN1 autonomously determines the priority based on the priority determined rules defined in rules in bullets 1 , 2, 3, 4 as follows:

I. the one or more parameters related to the configuration of MGPS1 .

II. the one or more parameters related to the configuration of MGPS2.

III. the one or more parameters related to the configuration of MGPS1 and MGPS2. b) In another example, the NN1 of NW1 doesn’t configure the priority information together with configured MGPs. For example, any of the collided gaps doesn’t associate with a priority. The pre-defined priority between MG1 and MG2 is determined by rules in bullets 1 , 2, 3, 4 as follows:

I. the one or more parameters related to the configuration of MGPS1 .

II. the one or more parameters related to the configuration of MGPS2.

III. the one or more parameters related to the configuration of MGPS1 and MGPS2. c) In another example, the NN1 of NW1 configures a MGP via a message (e.g. GapConfig) without suffix. No priority information can be associated with such MGP. The pre-defined priority between MG1 and MG2 is determined by rules in bullets 1 , 2, 3, 4 as follows:

I. the one or more parameters related to the configuration of MGPS1 .

II. the one or more parameters related to the configuration of MGPS2.

III. the one or more parameters related to the configuration of MGPS1 and MGPS2.

In one embodiment, the MUSIM gap’s priority is always valid when MUSIM gap collides with NN1 ’s MGs or collides with other MUSIM gaps.

In another embodiment, the MUSIM gap’s priority is only valid when MUSIM gap collides with NN1 ’s MG. The MUSIM gap’s priority is invalid when MUSIM gap collides with other MUSIM gaps.

In another embodiment, the MUSIM gap’s priority is only invalid when collision happens within MUSIM gaps and one of collision MUSIM gap is for paging. In other collision scenario, the MUSIM gap’s priority is valid. Embodiment # 2: Method in a first network node of determining the priority between MGs and using it for operational tasks

According to a second embodiment, NN1 serving or managing a UE:

I. obtains based on one or more rules a priority between MG1 and MG2 used by the UE for performing one or more procedures on one or more cells operating in NW1 and NW2 respectively; and

II. uses the obtained priority for performing one or more operational tasks provided that MG1 and MG2 collide with each other in time.

The examples of the one or more rules for obtaining the priority between MG1 and MG2, described in the UE embodiment (in section 6.1.3), also apply for this embodiment (i.e. method in NN1). In one example, NN1 obtains the priority levels associated with MG1 and MG2 by determining it based on a pre-defined rule i.e. the one or more rules are pre-defined. In another example, NN1 obtains the priority levels associated with MG1 and MG2 by receiving the information from the UE i.e. the UE sends the priority information according to one or more rules described in in the UE embodiment (in section 6.1.3).

I. The one or more conditions under which the MG1 and MG2 are considered to collide with each other in time are the same as described in the UE embodiment (in section 6.1.3).

Examples of the operational tasks performed by the network node are:

I. scheduling the UE with data (e.g. PDSCH, PUSCH etc) during a MG if it is cancelled and not scheduling the UE with data during MG if it is not cancelled etc.

II. configuring the UE whether the UE autonomously determines the priority levels of MG1 and MG2 and transmits the determined priority levels of MG1 and MG2, or the UE determines the priority levels of MG1 and MG2 based on the one or more rules which are predefined.

III. deciding whether NN1 follows the priority levels of MG1 and MG2 indicated/transmitted by the UE, or rejects the indicated priority information. In the latter case, NN1 may further configure the UE with another set of priority levels of MG1 and MG2.

Fig. 8 illustrates an example of a method performed by a multi-SIM enabled UE, such as the UE 102, in accordance with embodiments of the present disclosure. The UE 102 has the first and second SIMs. In some embodiments, the UE has multiple SIMs, e.g., three, four, five, six, or more than six SIMs.

The acts of Fig. 8 may be performed in any suitable order. Thus, it is herein provided a method performed by the UE 102 having at least two SIMs, for communication with two or more wireless communication networks. The UE has a first SIM associated with a first wireless communication network with a first MGP comprising a first network node, and has a second SIM associated with a second wireless communication network with a second MGP and comprising a second network node.

Action 801. The UE 10 obtains the priority indication associated with a first MG of the first MGP relative a second MG of the second MGP based on one or more rules.

Action 802. The UE further uses the obtained priority indication for performing one or more operational tasks provided that the first MG and the second MG collide with each other in time.

Fig. 9 illustrates an example of a method performed by a first network node associated with a first wireless communications network configured with a first MGP, and further being associated with a first SIM of a UE.

Action 901 . The first network node obtains a priority indication associated with a first MG of the first MGP relative a second MG of a second MGP based on one or more rules, wherein the second MGP is associated with a second network node associated with a second wireless communications network configured with the second MGP, and further being associated with a second SIM of the UE.

Action 902. The first network node uses the obtained priority indication for performing one or more operational tasks provided that the first MG and the second MG collide with each other in time.

Fig. 10 depicts an example of a UE, such as the UE 102, in accordance with embodiments herein. The UE 102 may have at least a first SIM and a second SIM. The UE 102 has at least two SIMs, for communication with two or more wireless communication networks. The UE is configured to have a first SIM associated with a first wireless communication network with a first MGP comprising a first network node, and to have a second SIM associated with a second wireless communication network with a second MGP and comprising a second network node.

The UE 102 may comprise processing circuitry 511 , e.g., one or more processors, configured to perform the methods herein. The UE 102, and/or the processing circuitry 511 is configured to obtain the priority indication associated with a first MG of the first MGP relative a second MG of the second MGP based on one or more rules.

The UE 102, and/or the processing circuitry 511 is configured to use the obtained priority indication for performing one or more operational tasks provided that the first MG and the second MG collide with each other in time.

The UE 102 further comprises a memory 515. The memory 515 comprises one or more units to be used to store data on, such as indications, MGs, one or more rules, contexts, measurements, thresholds, data related to nodes, and applications to perform the methods disclosed herein when being executed, and similar. Furthermore, the UE 102 may comprise a communication interface 520 such as comprising a transmitter, a receiver, one or more antennas, and/or a transceiver. In embodiments herein, the communication interface 520 may comprise dual Rx and Tx radios. In some embodiments, the communication interface 520 comprises more than two radios.

The methods according to the embodiments described herein for the UE 102 are respectively implemented using e.g., a computer program product 526 or a computer program, comprising instructions, i.e., software code portions, which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the UE 102. The computer program product 526 may be stored on a computer-readable storage medium 527, e.g. a disc, a universal serial bus (USB) stick or similar. The computer-readable storage medium 527, having stored thereon the computer program product, may comprise the instructions which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the UE 102. In some embodiments, the computer-readable storage medium may be a transitory or a non-transitory computer-readable storage medium. Thus, embodiments herein may disclose a UE for handling communication in a wireless communications network, wherein the UE comprises processing circuitry and a memory, the memory comprising instructions executable by the processing circuitry whereby the UE is operative to perform any of the methods herein.

Fig. 11 depicts an example of a first network node, such as the first network 104 or the second network node 106, referred to as a network node, in accordance with embodiments herein. It should be appreciated that the first network node 104 and the second network node 106 (see Fig. 5) may have the same or similar configurations, and are therefore not described separately herein. The first network node may be associated with a first wireless communication network, such as, e.g., the first wireless communication network 140 and the second wireless communication network 160, referred to herein as a wireless communication network. The first wireless communication network may be associated with one of SIMs of a UE, such that the UE 102. For example, the first wireless communication network may be associated with the first SIM, though it should be appreciated that SIMs are referred to herein as first and second for description purposes only. Thus, the first network node is associated with a first wireless communications network configured with a first MGP, and further being associated with a first SIM of a UE.

The first network node may comprise processing circuitry 611 , e.g. one or more processors, configured to perform the methods herein.

The first network node and/or the processing circuitry 611 is configured to obtain the priority indication associated with the first MG of the first MGP relative the second MG of the second MGP based on one or more rules, wherein the second MGP is associated with a second network node associated with the second wireless communications network configured with the second MGP, and further being associated with the second SIM of the UE.

The first network node and/or the processing circuitry 611 is configured to use the obtained priority indication for performing one or more operational tasks provided that the first MG and the second MG collide with each other in time.

As mentioned above and as shown in Fig. 10, the first network node comprises the memory 615. The memory 615 comprises one or more units to be used to store data on, such as indications, contexts, one or more rules, MGPs, measurements, thresholds, data related to nodes, and applications to perform the methods disclosed herein when being executed, and similar. Furthermore, the first network node may comprise a communication interface 620 such as comprising a transmitter, a receiver, one or more antennas, and/or a transceiver.

The methods according to the embodiments described herein for the the first network node are respectively implemented using e.g., a computer program product 626 or a computer program, comprising instructions, i.e., software code portions, which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the the first network node. The computer program product 626 may be stored on a computer-readable storage medium 627, e.g. a disc, a universal serial bus (USB) stick or similar. The computer-readable storage medium 627, having stored thereon the computer program product, may comprise the instructions which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the the first network node. In some embodiments, the computer-readable storage medium may be a transitory or a non-transitory computer-readable storage medium. Thus, embodiments herein may disclose a first network node for handling communication in a wireless communications network, wherein the first network node comprises processing circuitry and a memory, the memory comprising instructions executable by the processing circuitry whereby the first network node is operative to perform any of the methods herein.

In some embodiments, a more general term “network node” is used and it can correspond to any type of radio-network node or any network node, which communicates with a wireless device and/or with another network node. Examples of network nodes are NodeB, MeNB, SeNB, a network node belonging to Master cell group (MCG) or Secondary cell group (SCG), base station (BS), multi-standard radio (MSR) radio node such as MSR BS, eNodeB, network controller, radio-network controller (RNC), base station controller (BSC), relay, donor node controlling relay, base transceiver station (BTS), access point (AP), transmission points, transmission nodes, Remote radio Unit (RRU), Remote Radio Head (RRH), nodes in distributed antenna system (DAS), etc.

In some embodiments, the non-limiting term wireless device or user equipment (UE) is used and it refers to any type of wireless device communicating with a network node and/or with another wireless device in a cellular or mobile communication system. Examples of UE are loT capable device, target device, device to device (D2D) UE, proximity capable UE (aka ProSe UE), machine type UE or UE capable of machine to machine (M2M) communication, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, etc.

Embodiments are applicable to any RAT or multi-RAT systems, where the wireless device receives and/or transmit signals (e.g. data) e.g. New Radio (NR), Wi-Fi, Long Term Evolution (LTE), LTE-Advanced, Wideband Code Division Multiple Access (WCDMA), Global System for Mobile communications/enhanced Data rate for GSM Evolution (GSM/EDGE), Worldwide Interoperability for Microwave Access (WiMax), or Ultra Mobile Broadband (UMB), just to mention a few possible implementations.

As will be readily understood by those familiar with communications design, that functions means or circuits may be implemented using digital logic and/or one or more microcontrollers, microprocessors, or other digital hardware. In some embodiments, several or all of the various functions may be implemented together, such as in a single application-specific integrated circuit (ASIC), or in two or more separate devices with appropriate hardware and/or software interfaces between them. Several of the functions may be implemented on a processor shared with other functional components of a wireless device or network node, for example.

Alternatively, several of the functional elements of the processing means discussed may be provided through the use of dedicated hardware, while others are provided with hardware for executing software, in association with the appropriate software or firmware. Thus, the term “processor” or “controller” as used herein does not exclusively refer to hardware capable of executing software and may implicitly include, without limitation, digital signal processor (DSP) hardware and/or program or application data. Other hardware, conventional and/or custom, may also be included. Designers of communications devices will appreciate the cost, performance, and maintenance trade-offs inherent in these design choices.

Embodiments herein relate to:

Embodiment A1 :

A method performed by a user equipment, UE, (102) having at least two Subscriber Identity Modules, SIMs, for communication with two or more wireless communication networks, wherein the UE has a first SIM associated with a first wireless communication network with a first MGP comprising a first network node, and has a second SIM associated with a second wireless communication network with a second MGP and comprising a second network node; the method comprising obtaining a priority indication associated with a first MG of the first MGP relative a second MG of the second MGP based on one or more rules; and using the obtained priority indication for performing one or more operational tasks provided that the first MG and the second MG collide with each other in time.

Embodiment B1 :

A method performed by a first network node associated with a first wireless communications network configured with a first MGP, and further being associated with a first SIM of a UE, the method comprising: obtaining a priority indication associated with a first MG of the first MGP relative a second MG of a second MGP based on one or more rules, wherein the second MGP is associated with a second network node associated with a second wireless communications network configured with the second MGP, and further being associated with a second SIM of the UE; and using the obtained priority indication for performing one or more operational tasks provided that the first MG and the second MG collide with each other in time.

Embodiment C1 :

A user equipment, UE, (102) having at least two Subscriber Identity Modules, SIMs, for communication with two or more wireless communication networks, wherein the UE has a first SIM associated with a first wireless communication network with a first MGP comprising a first network node, and has a second SIM associated with a second wireless communication network with a second MGP and comprising a second network node; wherein the UE is configured to obtain a priority indication associated with a first MG of the first MGP relative a second MG of the second MGP based on one or more rules; and use the obtained priority indication for performing one or more operational tasks provided that the first MG and the second MG collide with each other in time.

Embodiment D1 :

A first network node associated with a first wireless communications network configured with a first MGP, and further being associated with a first SIM of a UE, wherein the first network node is configured to obtain a priority indication associated with a first MG of the first MGP relative a second MG of a second MGP based on one or more rules, wherein the second MGP is associated with a second network node associated with a second wireless communications network configured with the second MGP, and further being associated with a second SIM of the UE; and use the obtained priority indication for performing one or more operational tasks provided that the first MG and the second MG collide with each other in time.

Fig. 12 shows a telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments. With reference to Fig. 12, in accordance with an embodiment, a communication system includes a telecommunication network 3210, such as a 3GPP-type cellular network, which comprises access network 3211 , such as a radio access network, and core network 3214. Access network 3211 comprises a plurality of base stations 3212a, 3212b, 3212c, such as NBs, eNBs, gNBs or other types of wireless access points being examples of the network nodes above, each defining a corresponding coverage area 3213a, 3213b, 3213c. Each base station 3212a, 3212b, 3212c is connectable to core network 3214 over a wired or wireless connection 3215. A first UE 3291 located in coverage area 3213c is configured to wirelessly connect to, or be paged by, the corresponding base station 3212c. A second UE 3292 in coverage area 3213a is wirelessly connectable to the corresponding base station 3212a. While a plurality of Ues 3291 , 3292 are illustrated in this example being examples of the UE 102 above, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station 3212.

Telecommunication network 3210 is itself connected to host computer 3230, which may be embodied in the hardware and/or software of a standalone server, a cloud- implemented server, a distributed server or as processing resources in a server farm. Host computer 3230 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. Connections 3221 and 3222 between telecommunication network 3210 and host computer 3230 may extend directly from core network 3214 to host computer 3230 or may go via an optional intermediate network 3220. Intermediate network 3220 may be one of, or a combination of more than one of, a public, private or hosted network; intermediate network 3220, if any, may be a backbone network or the Internet; in particular, intermediate network 3220 may comprise two or more sub-networks (not shown).

The communication system of FIG. 12 as a whole enables connectivity between the connected UEs 3291 , 3292 and host computer 3230. The connectivity may be described as an over-the-top (OTT) connection 3250. Host computer 3230 and the connected UEs 3291 , 3292 are configured to communicate data and/or signalling via OTT connection 3250, using access network 3211 , core network 3214, any intermediate network 3220 and possible further infrastructure (not shown) as intermediaries. OTT connection 3250 may be transparent in the sense that the participating communication devices through which OTT connection 3250 passes are unaware of routing of uplink and downlink communications. For example, base station 3212 may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer 3230 to be forwarded (e.g., handed over) to a connected UE 3291. Similarly, base station 3212 need not be aware of the future routing of an outgoing uplink communication originating from the UE 3291 towards the host computer 3230.

FIG. 13 shows a host computer communicating via a base station and with a user equipment over a partially wireless connection in accordance with some embodiments Example implementations, in accordance with an embodiment, of the UE, base station and host computer discussed in the preceding paragraphs will now be described with reference to FIG. 13. In communication system 3300, host computer 3310 comprises hardware 3315 including communication interface 3316 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system 3300. Host computer 3310 further comprises processing circuitry 3318, which may have storage and/or processing capabilities. In particular, processing circuitry 3318 may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Host computer 3310 further comprises software 3311 , which is stored in or accessible by host computer 3310 and executable by processing circuitry 3318. Software 3311 includes host application 3312. Host application 3312 may be operable to provide a service to a remote user, such as UE 3330 connecting via OTT connection 3350 terminating at UE 3330 and host computer 3310. In providing the service to the remote user, host application 3312 may provide user data which is transmitted using OTT connection 3350.

Communication system 3300 further includes base station 3320 provided in a telecommunication system and comprising hardware 3325 enabling it to communicate with host computer 3310 and with UE 3330. Hardware 3325 may include communication interface 3326 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system 3300, as well as radio interface 3327 for setting up and maintaining at least wireless connection 3370 with UE 3330 located in a coverage area (not shown in FIG. 8) served by base station 3320. Communication interface 3326 may be configured to facilitate connection 3360 to host computer 3310. Connection 3360 may be direct or it may pass through a core network (not shown in FIG. 13) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, hardware 3325 of base station 3320 further includes processing circuitry 3328, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Base station 3320 further has software 3321 stored internally or accessible via an external connection.

Communication system 3300 further includes UE 3330 already referred to. It’s hardware 3333 may include radio interface 3337 configured to set up and maintain wireless connection 3370 with a base station serving a coverage area in which UE 3330 is currently located. Hardware 3333 of UE 3330 further includes processing circuitry 3338, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. UE 3330 further comprises software 3331 , which is stored in or accessible by UE 3330 and executable by processing circuitry 3338.

Software 3331 includes client application 3332. Client application 3332 may be operable to provide a service to a human or non-human user via UE 3330, with the support of host computer 3310. In host computer 3310, an executing host application 3312 may communicate with the executing client application 3332 via OTT connection 3350 terminating at UE 3330 and host computer 3310. In providing the service to the user, client application 3332 may receive request data from host application 3312 and provide user data in response to the request data. OTT connection 3350 may transfer both the request data and the user data. Client application 3332 may interact with the user to generate the user data that it provides.

It is noted that host computer 3310, base station 3320 and UE 3330 illustrated in FIG. 13 may be similar or identical to host computer 3230, one of base stations 3212a, 3212b, 3212c and one of Ues 3291 , 3292 of FIG. 12, respectively. This is to say, the inner workings of these entities may be as shown in FIG. 13 and independently, the surrounding network topology may be that of FIG. 12.

In FIG. 13, OTT connection 3350 has been drawn abstractly to illustrate the communication between host computer 3310 and UE 3330 via base station 3320, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure may determine the routing, which it may be configured to hide from UE 3330 or from the service provider operating host computer 3310, or both. While OTT connection 3350 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).

Wireless connection 3370 between UE 3330 and base station 3320 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to UE 3330 using OTT connection 3350, in which wireless connection 3370 forms the last segment. More precisely, the teachings of these embodiments make it possible communicate using a UE with multiple SIMs in an efficient manner. Thereby the communication may be performed in an efficient manner resulting in better responsiveness. A measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring OTT connection 3350 between host computer 3310 and UE 3330, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring OTT connection 3350 may be implemented in software 3311 and hardware 3315 of host computer 3310 or in software 3331 and hardware 3333 of UE 3330, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which OTT connection 3350 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 3311 , 3331 may compute or estimate the monitored quantities. The reconfiguring of OTT connection 3350 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect base station 3320, and it may be unknown or imperceptible to base station 3320. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signalling facilitating host computer 3310’s measurements of throughput, propagation times, latency and the like. The measurements may be implemented in that software 3311 and 3331 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using OTT connection 3350 while it monitors propagation times, errors, etc.

FIG. 14 shows methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments.

FIG. 14 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to FIG. 12 and Fig. 13. For simplicity of the present disclosure, only drawing references to FIG. 14 will be included in this section. In step 3410, the host computer provides user data. In substep 3411 (which may be optional) of step 3410, the host computer provides the user data by executing a host application. In step 3420, the host computer initiates a transmission carrying the user data to the UE. In step 3430 (which may be optional), the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 3440 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer. FIG. 15 showsmethods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments.

FIG. 15 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to FIGs. 12 and 13. For simplicity of the present disclosure, only drawing references to FIG. 15 will be included in this section. In step 3510 of the method, the host computer provides user data. In an optional substep (not shown) the host computer provides the user data by executing a host application. In step 3520, the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure. In step 3530 (which may be optional), the UE receives the user data carried in the transmission.

FIG. 16 shows methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments.

FIG. 16 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to FIGs. 12 and 13. For simplicity of the present disclosure, only drawing references to FIG. 16 will be included in this section. In step 3610 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 3620, the UE provides user data. In substep 3621 (which may be optional) of step 3620, the UE provides the user data by executing a client application. In substep 3611 (which may be optional) of step 3610, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. In providing the user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the UE initiates, in substep 3630 (which may be optional), transmission of the user data to the host computer. In step 3640 of the method, the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.

FIG. 17 shows methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments.

FIG. 17 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to FIG. 12 and FIG. 13. For simplicity of the present disclosure, only drawing references to FIG. 17 will be included in this section. In step 3710 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station receives user data from the UE. In step 3720 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step 3730 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.

Modifications and other embodiments of the disclosed embodiments will come to mind to one skilled in the art having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that the embodiment(s) is/are not to be limited to the specific embodiments disclosed and that modifications and other embodiments are intended to be included within the scope of this disclosure. Although specific terms may be employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.

Abbreviation Explanation

ACK Acknowledgement

AR Augmented reality

BLER Block error rate BWP Bandwidth part

C-MGP Concurrent MGP

CA Carrier Aggregation

CC Component carrier

CCA Clear Channel Assessment

CG Cell Group

CORSET Control resource set

CP Cyclic prefix

CSI-RS Channel state information reference signals

CSSF Carrier-specific scaling factor

DC Dual Connectivity

DCI Downlink control information

DL Downlink eMBB Evolved mobile broadband

FDD Frequency division duplex

FDM Frequency division multiplexing

FR1 Frequency range 1

FR2 Frequency range 2

FR3 Frequency range 3 gNB Next generation Node B (5G base station)

HARQ Hybrid automatic repeat request

LBT listen before talk

MAC Medium access control

MCG Master CG

MGC Measurement Gap Configuration

MGL Measurement gap length

MGO Measurement gap offset

MGOD Measurement gap on duration

MGP Measurement gap pattern

MGPS Measurement gap pattern set MGRP Measurement gap repetition period

MGTA Measurement gap timing advance

MC Multi-Carrier operation

MuC Multi-Connectivity

MUSIM Multi-SIM

NACK Negative acknowledgement

NR New radio (5G)

PBCH Physical broadcast channel

PCC Primary CC

PCell Primary Cell

PSCell Primary Secondary Cell

SCell Secondary Cell

SCG Secondary CG

SCC Secondary CC

PSCC Primary Secondary CC

PDCCH Physical downlink control channel

PDSCH Physical downlink shared channel

PRS Positioning reference signals

PUCCH Physcial uplink control channel

PUSCH Physcial uplink shared channel

RA Random access

RAT Radio access technology

RRC Radio resource control

RRM Radio resource management

SCS Subcarrier spacing

SFN System frame number

SIM Subscriber interface module

SMTC SSB measurement timing configuration

SRS Sounding reference signal

SSB Synchronization signal and PBCH block TDD Time division duplex

TDM Time division multiplexing

UAI UE assistance information

UE User equipment

UL Uplink

UL-SCH Uplink Shared Channel

Claims

1 . A method performed by a user equipment, UE, having a first and a second Subscriber Identity Modules, SIMs, respectively associated with a first and a second wireless communication networks, wherein the UE is configured by a first network node in the first wireless communication network with a first measurement gap pattern, MGP and by a second network node in the second wireless communication network with a second MGP, the method comprising: determining a collision between a pair of measurement gaps, MGs, wherein a first MG belongs to the first MGP and a second MG belongs to the second MGP; and determining priority of the pair of colliding MGs based on a first measurement gap repetition period, MGRP, in configuration of the first MGP and a second MGRP in configuration of the second MGP, that priority of the first MG is higher when the first MGRP is longer than the second MGRP.

2. The method of Claim 1 , wherein determining collision between the first and the second MG comprises: when the first and the second MG at least partially overlap with each other in time domain, or a distance between the first and the second MG is shorter than a threshold, determining that there is a collision between the first and the second MG.

3. The method of Claims 1 or 2, further comprising: transmitting the determined priority of MG1 and MG2 to the first network node and/or the second network node.

4. The method of any of Claims 1 to 3, further comprising: canceling the second MG and performing any of the following during the first MG: performing measurement in the first wireless communication network; monitoring paging signals in the first wireless communication network; or receiving system information in the first wireless communication network.

5. The method of Claim 3, further comprising: receiving from the first network node and/or the second network node configuration of priority levels for MGs in the first MGP and MGs in the second MGP.

6. The method of any of Claims 1 to 5, wherein the first MGP belongs to a first MGP set, MGPS configured by the first network node and the second MGP belongs to a second MGPS configured by the second network node.

7. The method of Claim 2, wherein a distance between the first and the second MG is shorter than a threshold comprises: a distance between an ending point of a prior MG of the first and second MGs in time domain and a starting point of a latter MG of the first and second MGs in time domain is less than or equal to the threshold.

8. A user equipment, UE, having a first and a second Subscriber Identity Modules, SIMs, respectively associated with a first and a second wireless communication networks, wherein the UE is configured by a first network node in the first wireless communication network with a first measurement gap pattern, MGP and by a second network node in the second wireless communication network with a second MGP; wherein the UE is configured to: determine a collision between a pair of measurement gaps, MGs, wherein a first MG belongs to the first MGP and a second MG belongs to the second MGP; and determine priority of the pair of colliding MGs based on a first measurement gap repetition period, MGRP, in configuration of the first MGP and a second MGRP in configuration of the second MGP, that priority of the first MG is higher when the first MGRP is longer than the second MGRP.

9. The user equipment of Claim 8, adapted to perform the method of any of claims 2 to 7.

10. A method performed by a first network node associated with a first wireless communications network and further being associated with a first SIM of a User Equipment, UE, wherein the UE has a second SIM associated with a second wireless communication network, the method comprising: configuring the UE with a first measurement gap pattern, MGP, including a parameter of a first measurement gap repetition period, MGRP, and obtaining a priority indication of a pair of colliding measurement gaps, MGs, including a first MG of the first MGP and a second MG of a second MGP configured by a second network node in the second wireless communication network, indicating that the first MG has higher priority than the second MG.

11. The method of Claim 10, further comprising: transmitting system information during the first MG; or sending paging signals during the first MG.

12. The method of Claims 10 or 11 , further comprising: configuring the UE with priority levels for MGs in the first MGP.

13. A first network node associated with a first wireless communications network and further being associated with a first SIM of a User Equipment, UE, wherein the UE has a second SIM associated with a second wireless communication network, the first network node is configured to: configure the UE with a first measurement gap pattern, MGP, including a parameter of a first measurement gap repetition period, MGRP, and obtain a priority indication of a pair of colliding measurement gaps, MGs, including a first MG of the first MGP and a second MG of a second MGP configured by a second network node in the second wireless communication network, indicating that the first MG has higher priority than the second MG.

14. The first network node of Claim 13, further configured to: transmit system information during the first MG or send paging signals during the first MG.

15. The first network node of Claims 13 or 14, further configured to: configure the UE with priority levels for MGs in the first MGP.