Patent Description:
<CIT> discloses apparatuses and methods for a wireless communication device having a first Subscriber Identity Module (SIM) and a second SIM to manage communication via the first SIM and the second SIM. The method can include, but is not limited to, sending a first message including an indication of an extended signaling capability, receiving a second message including an inquiry regarding the extended signaling capability, and sending a third message including extended capability information, responsive to receiving the second message.

<CIT> discloses a user equipment (UE) that provides a capability-type indication for each of one or more UE capabilities. Each indication corresponds to a capability type, the type being one of a persistent capability or a second-type capability. Information corresponding to the capability-type indication may be provided to an eNB associated with the UE by RRC signaling. The UE provides a capability-change indication for each of one or more UE capabilities that has changed capability type. Information corresponding to the capability-change indication may be provided to an eNB by lower layer signaling, RRC signaling, or a combination thereof. Capability change information may be sent to the eNB autonomously by the UE, or in response to an inquiry from the eNB. The inquiry from the eNB may be triggered by the UE.

<CIT> relates to user equipment (UE) circuitry comprising: a lookup table configured to provide for at least one bitrate requirement of a first subscriber identity module (SIM) of a multi-SIM module and at least one bitrate requirement of a second SIM of the multi-SIM module a respective combination of UE categories for both SIMs, wherein a specific UE category indicates a specific hardware resources configuration supported by the UE; and an arbitration entity configured to select a specific combination of UE categories from the lookup table based on a bitrate change request from any one of the first SIM or the second SIM. Next using the NAS-AS Framework in the Protocol Stack the above selected UE Category combination from the Look Up Table is reported to the network in the ECM-Idle state without network detach and network re-attach to minimize the delays using the method provided in the MSCs.

<NPL> relates to an initial context setup procedure comprising sending by a CN node, MME, an initial context setup request message comprising a service gap information of the UE.

<CIT> relates to a method for facilitating wireless communication in multi-subscriber identity module user equipment, involves determining whether to abort tuning away from first subscriber identity module to second identity module at user equipment.

<CIT> discloses a multi-SIM UE and transitions from the first SIM to the second SIM.

The scope of protection of the present invention is defined in the independent claims.

After considering this discussion, and particularly after reading the section entitled "Detailed Description" one will understand how the features of this disclosure provide advantages that include improved techniques for supporting scheduling gaps for UEs equipped with multiple universal subscriber identity modules (USIMs).

Certain aspects provide a method for wireless communication by a UE, as defined in claim <NUM>.

Certain aspects provide a method for wireless communication by a radio access network (RAN) node, as defined in claim <NUM>.

Certain aspects provide a method for wireless communication by a core network node, as defined in claim <NUM>.

Certain aspects provide an apparatus for wireless communication, as defined in claim <NUM>.

Certain aspects provide a computer program, as defined in claim <NUM>.

Aspects of the present disclosure provide apparatus, methods, processing systems, and computer readable mediums for enabling UEs equipped with multiple USIMs to request scheduling (or schedule) gaps from a RAN serving the UE via a first USIM (e.g., the RAN is in a connected mode with the UE via the first USIM), such that the UE can communicate with other RANs via other USIM(s) without missing downlink data received by the serving RAN that is destined for the UE.

Certain systems (e.g., <NUM> NR, LTE, etc.) may support communications with UEs equipped with multiple USIMs. A multi-USIM device implementation generally involves the use of common radio and baseband components that are shared among the multiple USIMs. For example, while actively communicating with a first system (e.g., RAN/CN A) via a first USIM, the UE may occasionally transition to one or more second systems (e.g., RAN/CN B to RAN/CN K) via one or more second USIMs to perform one or more communication operations (e.g., monitor a paging channel used by the second system, perform signal measurements, read system information, etc.). In such situations, if the first system is unaware that the UE has to transition (or already has transitioned) to other systems, the first system may send downlink data to the UE during a time in which the UE has transitioned to another system and is in connected mode with the other system. This can cause the UE to miss (e.g., not receive) the downlink data transmission from the first system, significantly reducing network efficiency and performance.

To address this, aspects provide techniques for configuring schedule gap support information that can be used to enable the UE to request scheduling gaps from a network (e.g., RAN/CN). The schedule gap support information, for example, may include information associated with transitioning (or tuning away) from a first RAN associated with a first USIM of the UE to at least a second RAN associated with a second USIM of the UE. As described in more detail below, in some aspects, the schedule gap support information may indicate whether the UE is allowed to request a schedule gap, under what conditions (e.g., time periods, operating bands, operating radio access technologies (RATs), network conditions, etc.) the UE is allowed to request a schedule gap, and/or parameter(s) of the schedule gaps (e.g., duration of the schedule gap(s), periodicity of the schedule gap(s), etc.).

As described in more detail below, in some aspects, the schedule gap support information may be based in part on capabilities of the UE, capabilities of the network (e.g., RAN and/or CN), and/or (UE or network) policies. In some aspects, the schedule gap support information may be negotiated based on information exchanged between the UE, the RAN, and/or the CN. By configuring scheduling gap support information that can be used by the UE to request particular schedule gaps from the network, aspects herein can significantly reduce the chances of the UE missing downlink data due to transitioning to another system.

Though certain aspects are described with respect to UEs equipped with two USIMs, it should be noted that the aspects herein may be applied to UEs equipped with any number of USIMs.

The following description provides examples of configuring schedule gap support information for multi-USIM devices in communication systems, and is not limiting of the scope, applicability, or examples set forth in the claims.

For example, the wireless communication network <NUM> may be an NR system (e.g., a <NUM> NR network), a LTE system, or system that supports both NR and LTE.

The BS <NUM>X may be a pico BS for a pico cell 102x.

A RAN <NUM> may include a network controller <NUM> and the BS(s) <NUM>. The RAN <NUM> may be in communication with a core network (CN) <NUM>, which includes one or more CN nodes 132a. The network controller <NUM> may couple to a set of BSs <NUM> and provide coordination and control for these BSs <NUM>. Although a single RAN <NUM> and a single CN <NUM> are depicted in <FIG>, the wireless communication network <NUM> may include multiple RANs <NUM> and/or multiple CNs <NUM>. Further, in some cases, the wireless communication network <NUM> may support RANs/CNs of same RATs, different RATs, or a combination of RATs.

As illustrated, UE 120a includes a scheduling gap component <NUM>, which is configured to implement one or more techniques described herein for configuring scheduling gap support information. Using the scheduling gap component <NUM>, the UE 120a may identify a network (e.g., RAN/CN) to access for communications and may transmit an indication of schedule gap support information for the UE to the network. The schedule gap support information may include information associated with the UE transitioning from a first RAN associated with a first USIM of the UE to at least a second RAN associated with a second USIM of the UE.

As also illustrated, BS 110a (e.g., RAN entity or RAN node, such as a gNB or eNB) includes a scheduling gap component <NUM>, which is configured to implement one or more techniques described herein for configuring scheduling gap support information. Using the scheduling gap component <NUM>, the BS 110a may receive an initial context setup request message from a CN node (e.g., CN node 132a, such as an Access and Mobility Management Function (AMF) or Mobility Management Entity (MME)) during an initial context setup procedure with the CN node. The initial context setup request message may include schedule gap support information for a UE (e.g., UE 120a) associated with the BS 110a. For example, the BS 110a may be in a radio resource control (RRC) connected mode with a particular USIM (e.g., USIM A) of the UE. Using the scheduling gap component <NUM>, the BS 110a may generate an initial context setup response message after receiving the initial context setup request message and transmit the initial context setup response message (e.g., to the CN node).

As further illustrated, CN node 132a (e.g., AMF or MME) includes a scheduling gap component <NUM>, which is configured to implement one or more techniques described herein for configuring scheduling gap support information. Using the scheduling gap component <NUM>, the CN node 132a may transmit an initial context setup request message to a RAN node (e.g., BS 110a) during an initial context setup procedure with the RAN node. The initial context setup request message may include schedule gap support information for a UE (e.g., UE 120a) associated with the RAN node. For example, as noted, the RAN node may be in an RRC connected mode with a particular USIM (e.g., USIM A) of the UE. The CN 132a (using the scheduling gap component <NUM>) may receive, in response to the initial context setup request message, an initial context setup response message from the RAN node during the initial context setup procedure.

At the BS 110a, a transmit processor <NUM> may receive data from a data source <NUM> and control information from a controller/processor <NUM>. The transmit processor <NUM> may also generate reference symbols, such as for the primary synchronization signal (PSS), secondary synchronization signal (SSS), and cell-specific reference signal (CRS). A transmit (TX) multiple-input multiple-output (MIMO) processor <NUM> may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, and/or the reference symbols, if applicable, and may provide output symbol streams to the modulators (MODs) 232a-232t. Downlink signals from modulators 232a-232t may be transmitted via the antennas 234a-234t, respectively.

At the UE 120a, the antennas 252a-252r may receive the downlink signals from the BS 110a and may provide received signals to the demodulators (DEMODs) in transceivers 254a-254r, respectively. A MIMO detector <NUM> may obtain received symbols from all the demodulators 254a-254r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. A receive processor <NUM> may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for the UE 120a to a data sink <NUM>, and provide decoded control information to a controller/processor <NUM>.

On the uplink, at UE 120a, a transmit processor <NUM> may receive and process data (e.g., for the physical uplink shared channel (PUSCH)) from a data source <NUM> and control information (e.g., for the physical uplink control channel (PUCCH) from the controller/processor <NUM>. The symbols from the transmit processor <NUM> may be precoded by a TX MIMO processor <NUM> if applicable, further processed by the demodulators in transceivers 254a-254r (e.g., for SC-FDM, etc.), and transmitted to the BS 110a. At the BS 110a, the uplink signals from the UE 120a may be received by the antennas <NUM>, processed by the modulators <NUM>, detected by a MIMO detector <NUM> if applicable, and further processed by a receive processor <NUM> to obtain decoded data and control information sent by the UE 120a.

The controller/processor <NUM> and/or other processors and modules at the UE 120a may perform or direct the execution of processes for the techniques described herein. For example, as shown in <FIG>, the controller/processor <NUM> of the UE 120a has a scheduling gap component <NUM>, which is configured to implement one or more techniques described herein for configuring schedule gap support information, according to aspects described herein. Similarly, the controller/processor <NUM> and/or other processors and modules at the BS 110a may perform or direct the execution of processes for the techniques described herein. For example, as shown in <FIG>, the controller/processor <NUM> of the BS 110a has a scheduling gap component <NUM>, which is configured to implement one or more techniques described herein for configuring schedule gap support information, according to aspects described herein. Further, although not shown in <FIG>, a CN node may include a controller/processor and/or other processors and modules that perform or direct the execution of processes for the techniques described herein. For example, the controller/processor of the CN node may include a scheduling gap component <NUM>, which is configured to implement one or more techniques described herein for configuring schedule gap support information, according to aspects described herein. Although shown at the Controller/Processor, other components of the UE 120a and BS 110a may be used performing the operations described herein.

<FIG> is a block diagram illustrating an example architecture of a CN <NUM> (e.g., the CN <NUM> in <FIG>) in communication with a RAN <NUM>, in accordance with certain aspects of the present disclosure. As shown in <FIG>, the example architecture includes the CN <NUM>, RAN <NUM>, UE <NUM>, and data network (DN) <NUM> (e.g. operator services, Internet access or third party services).

The CN <NUM> may host core network functions. CN <NUM> may be centrally deployed. CN <NUM> functionality may be offloaded (e.g., to advanced wireless services (AWS)), in an effort to handle peak capacity. As shown in <FIG>, the example CN <NUM> may be implemented by one or more network entities that perform network functions (NF) including Network Slice Selection Function (NSSF) <NUM>, Network Exposure Function (NEF) <NUM>, NF Repository Function (NRF) <NUM>, Policy Control Function (PCF) <NUM>, Unified Data Management (UDM) <NUM>, Application Function (AF) <NUM>, Authentication Server Function (AUSF) <NUM>, AMF <NUM>, Session Management Function (SMF) <NUM>; User Plane Function (UPF) <NUM>, and various other functions (not shown) such as Unstructured Data Storage Function (UDSF); Unified Data Repository (UDR); <NUM>-Equipment Identity Register (<NUM>-EIR); and/or Security Edge Protection Proxy (SEPP).

The AMF <NUM> may include the following functionality (some or all of the AMF functionalities may be supported in one or more instances of an AMF): termination of RAN control plane (CP) interface (N2); termination of non-access stratum (NAS) (e.g., N1), NAS ciphering and integrity protection; registration management; connection management; reachability management; mobility management; lawful intercept (for AMF events and interface to L1 system); transport for session management (SM) messages between UE <NUM> and SMF <NUM>; transparent proxy for routing SM messages; access authentication; access authorization; transport for short message service (SMS) messages between UE <NUM> and a SMS function (SMSF); Security Anchor Functionality (SEAF); Security Context Management (SCM), which receives a key from the SEAF that it uses to derive access-network specific keys; Location Services management for regulatory services; transport for Location Services messages between UE <NUM> and a location management function (LMF) as well as between RAN <NUM> and LMF; evolved packet service (EPS) bearer ID allocation for interworking with EPS; and/or UE mobility event notification; and/or other functionality.

SMF <NUM> may support: session management (e.g., session establishment, modification, and release), UE IP address allocation and management, dynamic host configuration protocol (DHCP) functions, termination of NAS signaling related to session management, downlink data notification, and traffic steering configuration for UPF for proper traffic routing. UPF <NUM> may support: packet routing and forwarding, packet inspection, quality-of-service (QoS) handling, external protocol data unit (PDU) session point of interconnect to DN <NUM>, and anchor point for intra-RAT and inter-RAT mobility. PCF <NUM> may support: unified policy framework, providing policy rules to control protocol functions, and/or access subscription information for policy decisions in UDR. AUSF <NUM> may acts as an authentication server. UDM <NUM> may support: generation of Authentication and Key Agreement (AKA) credentials, user identification handling, access authorization, and subscription management. NRF <NUM> may support: service discovery function, and maintain NF profile and available NF instances. NSSF may support: selecting of the Network Slice instances to serve the UE <NUM>, determining the allowed network slice selection assistance information (NSSAI), and/or determining the AMF set to be used to serve the UE <NUM>.

NEF <NUM> may support: exposure of capabilities and events, secure provision of information from external application to 3GPP network, translation of internal/external information. AF <NUM> may support: application influence on traffic routing, accessing NEF <NUM>, and/or interaction with policy framework for policy control. As shown in <FIG>, the CN <NUM> may be in communication with the UE <NUM>, RAN <NUM>, and DN <NUM>.

<FIG> illustrates an example system architecture <NUM> for a multi-USIM UE interworking between two systems/networks, in accordance with certain aspects of the present disclosure. As shown in <FIG>, the UE may be served by separate RANs 404A (e.g., E-UTRAN or NR RAN) and 404B (e.g., E-UTRAN or NR RAN) controlled by separate CNs 406A (e.g., EPC or 5GC) and 406B (e.g., EPC or 5GC). The RAN 404A may provide E-UTRA services or <NUM> NR services. Similarly, the RAN 404B may provide E-UTRA services or <NUM> NR services. The UE <NUM> may operate under one RAN/CN at a time.

In one example, in RAN 404A and RAN 404B, the network node(s) may include gNB(s) and, in CN 406A and CN 406B, the network node(s) may include AMF(s). In one example, in RAN 404A and RAN 404B, the network node(s) may include eNB(s) and, in CN 406A and CN 406B, the network node(s) may include MME(s). In one example, RAN 404A may include eNB(s), CN 406A may include MME(s), RAN 404B may include gNB(s), and CN 406B may include AMF(s).

As noted above, in some cases, a UE equipped with multiple USIMs may not receive downlink data from a first network associated with a first USIM of the UE during periods in which the UE transitions from the first network to a second network associated with a second USIM of the UE.

In the reference example shown in <FIG>, assume a UE (e.g., UE 120a) is equipped with two USIMs (e.g., USIM A and USIM B). In this example, USIM A is associated with RAN 404A and CN 406A and USIM B is associated with RAN 404B and CN 406B. As shown, the UE may be actively communicating with RAN 404A/CN 406A via USIM A (e.g., USIM A may be in connected mode with RAN 404A). While actively communicating with RAN 404A/CN 406A, the UE may decide to transition to RAN 404B/CN 406B to perform one or more communication operations. Here, for example, the UE monitors a paging channel used by RAN 404B and decides to respond to a paging request from RAN 404B. In this case, the UE may enter a connected mode for USIM B in order to monitor the paging channel and/or respond to the paging request. In these situations, if RAN 404A/CN 406A is not aware that the UE has transitioned (or aware of the times that the UE will attempt to transition) to RAN 404B/CN 406B, the RAN 404A/CN 406A may send downlink data to the UE during a time in which the UE is in connected mode via USIM B, and the UE may not receive the downlink data transmission. Missing data in these situations can impact the performance and efficiency of the communication system.

Accordingly, it may be desirable to provide techniques for configuring scheduling gap support information that can be used by the UE to request schedule gaps from a network.

Aspects of the present disclosure provide techniques for configuring schedule gap support information that can be used by UEs to request scheduling gaps from a RAN serving the UE via a first USIM (e.g., in connected mode with the RAN). Note, that while many of the following aspects are described with respect to <NUM>/NR systems, the techniques described herein can be applied to both LTE and <NUM>. In some aspects, the techniques described herein can also be applied to multi-USIM devices from separate mobile network operators (MNOs) and same MNOs.

The scheduling gap support information (also referred to as schedule gap support information) may include information associated with the UE's transition to other networks/systems via other USIM(s) of the UE. For example, the schedule gap support information may indicate at least one of: (i) whether the UE is allowed to tune away to another system during connected mode; (ii) whether the UE is allowed to request a schedule gap from a particular network; (iii) whether to allow a schedule gap request from the UE; (iv) different types of schedule gaps supported by the network (e.g., "hard gap," in which the UE completely tunes away from a serving RAN, is supported, or a "soft gap," in which the UE stays on the serving RAN with limited capability, is supported); (v) which band(s) or band combination(s) are supported by schedule gap(s) (e.g., frequency range <NUM> (FR1) and/or frequency range <NUM> (FR2)); (vi) duration of schedule gap(s) (e.g., gap length, periodicity etc.) per RAT of the other system; (vii) schedule gap capability for each dual connectivity (DC) combination; (viii) schedule gap policy for each of one or more RATs, etc..

In some aspects, the RAN node may also broadcast its support for allowing schedule gaps, which the UE can take into account before requesting a schedule gap from the RAN node. In some aspects, the UE may use the scheduling gap support information to request a schedule gap from a network (e.g., RAN). The RAN, after receiving the scheduling gap request from the UE, may determine whether to allow the schedule gap, based on the scheduling gap support information.

In some aspects, the scheduling gap support information may be based on a set of UE capabilities. For example, the UE may include scheduling gap support information in the set of UE capabilities and provide the set of UE capabilities to the core network. In this case, the set of UE capabilities (along with the scheduling gap support information) may be transparent to the core network. That is, the core network may not be able to parse (or have knowledge of) the information contained within the set of UE capabilities. The core network may just store the UE capabilities. The core network, in turn, may provide the set of UE capabilities to the RAN during an initial context setup procedure.

<FIG> depicts an example call flow <NUM> in which the CN provides the schedule gap support information to the RAN in a transparent manner, in accordance with certain aspects of the present disclosure.

Although not shown, prior to step <NUM>, the UE may include the schedule gap support information in a set of UE radio capabilities. In one aspect, the UE may transmit the set of UE radio capabilities to the RAN (e.g., during connected mode), and when the UE transitions to idle mode, the RAN may provide the set of UE radio capabilities to the CN. In one aspect, the UE may transmit a radio capability identifier (ID) that identifies a particular set of UE radio capabilities, which includes the schedule gap support information. The UE may transmit the radio capability ID to indicate a set of UE radio capabilities in situations in which the network supports radio capabilities signaling optimization (RACS). The UE may transmit the radio capability ID via a NAS message to the CN.

During an idle to connected mode transition procedure (e.g., in which the UE attempts to transition to connected mode with the RAN), the CN may trigger an initial context setup procedure with the RAN to deliver the set of UE radio capabilities. In step <NUM>, for example, the CN may transmit an initial context setup request to the RAN. The initial context setup request may include the set of UE radio capabilities, which may include the schedule gap support information. At <NUM>, the RAN may transmit an initial context setup response to the CN.

Subsequently, if the UE requests a schedule gap from the RAN (e.g., via an RRC or MAC message), the RAN can use the schedule gap support information to determine whether to allow the schedule gap request from the UE. In one particular case, for example, the schedule gap support information include RAT specific information, such as a schedule gap to <NUM>/<NUM> systems is allowed but a schedule gap to <NUM>/<NUM> systems is not allowed. Thus, in this reference example, assuming the UE requests a schedule gap to a <NUM>/<NUM> system, the RAN may allow (or grant) the request.

Additionally, although not shown in <FIG>, in some aspects, the RAN node broadcasts allowed schedule gap information (e.g., in a system information block (SIB)) for the UE to use when requesting a schedule gap from the RAN node.

In some aspects, the scheduling gap support information may be based on one or more types of support information received from different devices. For example, in one aspect, the CN (e.g., AMF) may determine the scheduling gap support information based on UE network capability information received from the UE, UE subscription information received from another core network entity (e.g., Home Subscriber Server (HSS), UDM), and/or network policy information received from another core network entity (e.g., PCF). In some aspects, each of the UE network capability information, the UE subscription information, and the network policy information may include a subset of schedule gap support information. For example, the UE network capability information may indicate whether the UE has a capability of requesting schedule gaps to <NUM> systems when the UE is in connected mode with a <NUM> system. Continuing with this example, the UE subscription information may indicate whether the <NUM> system allows UEs to request schedule gaps to <NUM> systems (and, if so, under what conditions). Still continuing with this example, assuming the RAN receives schedule gap policy information from a PCF (e.g., in a <NUM> network), the policy information may indicate the maximum duration of schedule gaps in <NUM> systems. Note, however, that the above scenario is provided as merely a reference example of how the schedule gap support information can be determined based on multiple types of schedule gap information received from different entities in the network. Those of ordinary skill in the art will recognize that other types of conditions and/or parameters may be provided by the UE network capability information, the UE subscription information, and the network policy information.

<FIG> depicts an example call flow <NUM> in which the core network determines schedule gap support information based on different types of schedule gap information received from different entities, in accordance with certain aspects of the present disclosure.

At <NUM>, the UE may perform an attach procedure, tracking area update procedure, or a registration procedure, during which the UE sends UE network capability information to the CN (e.g., via a NAS message). The UE network capability information may include at least a portion of the schedule gap support information. In <FIG>, for example, the UE network capability information may include information regarding the UE's capability to negotiate for scheduling gaps (referred to as "Schedule gap negotiation capable" information). The NAS message may include an attach request (e.g., for attach procedure), a tracking area update request (e.g., for tracking area update procedure), or a registration request (e.g., for a registration procedure).

As part of the attach/tracking area update/registration procedure, the CN may retrieve subscription information associated with the UE from a HSS (e.g., in EPC (or <NUM>) systems) or UDM (e.g., in <NUM> systems). At <NUM>, for example, the CN may send an update location request to HSS/UDM, and, at <NUM>, may receive an update location acknowledgement from HSS/UDM. The update location acknowledgement may include UE subscription information, which includes at least a(nother) portion of the schedule gap support information. In <FIG>, for example, the UE subscription information may include information regarding the schedule gaps allowed by the (serving) network (e.g., which band(s)/band combination(s), which RAT(s), which time periods, allowed duration of schedule gaps, DC combinations supported, etc.) (referred to as "Schedule gap allowed information").

In some cases, the CN may also interact with one or more other entities to receive other portions of the schedule gap support information. As shown in <FIG>, for example, for <NUM> systems, the CN may retrieve policy information from a PCF during the registration procedure (step <NUM>). The policy information may include at least a(nother) portion of the schedule gap support information. In <FIG>, for example, the policy information may include information regarding the condition(s) in which schedule gap(s) are allowed (or can be requested), parameters of the schedule gap(s) (e.g., duration, periodicity, etc.), etc. In some cases, the policy information may reflect information regarding a desired operation of the network by an MNO.

At step <NUM>, the CN determines the schedule gap support information based on the information received at steps <NUM>, <NUM>, and/or <NUM>. In one aspect, the CN may determine the schedule gap support information based on an intersection of the information received at steps <NUM>, <NUM>, and/or <NUM>. At step <NUM>, the CN transmits an initial context setup request message that includes the schedule gap support information to the RAN. Although not shown, the CN may receive an initial context setup response from the RAN, after transmitting the initial context setup request message.

<FIG> is a flow diagram illustrating example operations <NUM> for wireless communication, in accordance with certain aspects of the present disclosure. The operations <NUM> may be performed, for example, by UE (e.g., such as a UE 120a in the wireless communication network <NUM>). Operations <NUM> may be implemented as software components that are executed and run on one or more processors (e.g., controller/processor <NUM> of <FIG>). Further, the transmission and reception of signals by the UE in operations <NUM> may be enabled, for example, by one or more antennas (e.g., antennas <NUM> of <FIG>). In certain aspects, the transmission and/or reception of signals by the UE may be implemented via a bus interface of one or more processors (e.g., controller/processor <NUM>) obtaining and/or outputting signals.

The operations <NUM> may begin, at <NUM>, where the UE identifies a network (e.g., RAN/CN) to access for communications. At <NUM>, the UE transmits an indication of schedule gap support information for the UE to the network. The schedule gap support information includes information associated with transitioning from a first RAN associated with a first USIM of the UE to at least a second RAN associated with a second USIM of the UE.

In some aspects, the UE (e.g., at <NUM>) may transmit a set of UE radio capabilities to the network. The set of UE radio capabilities may include the schedule gap support information.

In some aspects, the UE (e.g., at <NUM>) may transmit a capability identifier associated with a set of UE radio capabilities to the network. The set of UE radio capabilities associated with the capability identifier may include the schedule gap support information. The capability identifier may be transmitted via a NAS message.

In some aspects, the UE (e.g., as part of operations <NUM>) may transmit UE network capability information to the network (e.g., step <NUM> in <FIG>). The UE network capability information may include at least a portion of the schedule gap support information. The UE network capability information may be transmitted via a NAS message (e.g., attach message during an attach procedure, tracking area update via a tracking area update procedure, or a registration request during a registration procedure).

In some aspects, the UE (e.g., as part of operations <NUM>) may receive information regarding one or more schedule gaps allowed by the network. The UE may transmit a request for a schedule gap, based on the information regarding the one or more schedule gaps allowed by the network.

<FIG> is a flow diagram illustrating example operations <NUM> for wireless communication, in accordance with certain aspects of the present disclosure. The operations <NUM> may be performed, for example, by a RAN node (e.g., BS 110a in the wireless communication network <NUM>). Operations <NUM> may be implemented as software components that are executed and run on one or more processors (e.g., controller/processor <NUM> of <FIG>). Further, the transmission and reception of signals by the RAN node in operations <NUM> may be enabled, for example, by one or more antennas (e.g., antennas <NUM> of <FIG>). In certain aspects, the transmission and/or reception of signals by the RAN node may be implemented via a bus interface of one or more processors (e.g., controller/processor <NUM>) obtaining and/or outputting signals.

The operations <NUM> may begin, at <NUM>, where the RAN node receives an initial context setup request message (e.g., step <NUM> in <FIG>, step <NUM> in <FIG>) from a CN node (e.g., AMF/MME) during an initial context setup procedure with the CN node, wherein the initial context setup request message comprises schedule gap support information for a UE associated with the RAN node. The schedule gap support information may include information associated with transitioning from a first RAN associated with a first USIM of the UE to a second RAN associated with a second USIM of the UE. At <NUM>, the RAN node generates an initial context setup response message (e.g., step <NUM> in <FIG>) after receiving the initial context setup request message. At <NUM>, the RAN node transmits the initial context setup response message (e.g., step <NUM> in <FIG>).

In some aspects, the initial context setup request message (e.g., at <NUM>) comprises a set of UE radio capabilities associated with the UE (e.g., step <NUM> in <FIG>). The set of UE radio capabilities may include the schedule gap support information.

In some aspects, the RAN node may transmit an indication of a capability of the RAN node to support one or more schedule gaps and/or an indication of one or more allowed schedule gaps in which the UE transitions from a first connected mode via the RAN node to a second connected mode via another RAN node. For example, the RAN node (e.g., RAN 404A) maybe associated with a first USIM (e.g., USIM A) of the UE and the other RAN node (e.g., RAN 404B) may be associated with a second USIM (e.g., USIM B) of the UE. In some aspects, the indication(s) may be transmitted via broadcast signaling (e.g., via a SIB).

<FIG> is a flow diagram illustrating example operations <NUM> for wireless communication, in accordance with certain aspects of the present disclosure. The operations <NUM> may be performed, for example, by a CN node (e.g., CN node 132a in the wireless communication network <NUM>). Operations <NUM> may be implemented as software components that are executed and run on one or more processors of the CN node. Further, the transmission and reception of signals by the CN node in operations <NUM> may be enabled, for example, by one or more antennas. In certain aspects, the transmission and/or reception of signals by the CN node may be implemented via a bus interface of one or more processors obtaining and/or outputting signals.

The operations <NUM> may begin, at <NUM>, where the CN node transmits an initial context setup request message (e.g., step <NUM> in <FIG>, step <NUM> in <FIG>) to a RAN node (e.g., eNB, gNB) during an initial context setup procedure with the RAN node. The initial context setup request message comprises schedule gap support information for a UE associated with the RAN node. At <NUM>, the CN node receives, in response to the initial context setup request message, an initial context setup response message from the RAN node during the initial context setup procedure (e.g., step <NUM> in <FIG>).

In some aspects, the initial context setup request message (e.g., at <NUM>) includes a set of UE radio capabilities associated with the UE. The set of UE radio capabilities may include the schedule gap support information. The set of UE radio capabilities may be transparent to the CN node.

In some aspects, the CN node may determine (e.g., at step <NUM> in <FIG>) the schedule gap support information based on a first type of schedule gap information (e.g., UE network capability information), a second type of schedule gap information (e.g., UE subscription information), and a third type of schedule gap information (e.g., UE (or network) policy information). At least one of the UE network capability information, the UE subscription information, or the UE policy information may include a (same or different) portion of the schedule gap support information.

In some aspects, the schedule gap support information may be determined prior to transmitting the initial context setup request message.

In some aspects, the schedule gap support information is determined based on an intersection of the first type of schedule gap information, the second type of schedule gap information, and the third type of schedule gap information.

In some aspects, the CN node (e.g., as part of operations <NUM>) may perform an attach procedure, a tracking area update procedure, or a registration procedure with the UE. The first type of schedule gap information may be received from the UE during the attach procedure, the tracking area update procedure, or the registration procedure (e.g., step <NUM> in <FIG>). For example, the first type of schedule gap information may be received via a NAS message (e.g., an attach request, a tracking area update, or a registration request).

In some aspects, the CN node (e.g., as part of operations <NUM>) may retrieve the second type of schedule gap information from another CN node during the attach procedure, the tracking area update procedure, or the registration procedure (e.g., steps <NUM>-<NUM> in <FIG>). The other CN node may be a HSS or UDM.

In some aspects, the CN node (e.g., as part of operations <NUM>) may retrieve the third type of schedule gap information from another CN node (e.g., step <NUM> in <FIG>). The other CN node may be a PCF.

The schedule gap support information (e.g., in operations <NUM>, <NUM>, and <NUM>) may include information associated with transitioning from a first RAN associated with a first USIM of the UE to a second RAN associated with a second USIM of the UE. For example, the schedule gap support information may include at least one of: (i) an indication of whether the UE is allowed to tune away to another RAN during connected mode; (ii) an indication of whether to allow a schedule gap request from the UE; (iii) an indication of one or more types of schedule gaps supported by the CN node (e.g., a "hard gap," in which the UE completely tunes away from the serving RAN may be supported or a "soft gap," in which the UE can stay on the serving RAN with limited capability may be supported); (iv) an indication of one or more bands supported by the schedule gap (e.g., the gap support can be per band or per band combination, the schedule gap may be applied to FR1, the schedule gap may be applied to FR2, the schedule gap may be applied to FR1 but not FR2, the schedule gap may be applied to FR2 but not FR1, or the schedule gap may be applied to a combination of frequencies in FR1 and/or FR2); (v) an indication of amount of time of the schedule gap or the amount of time between schedule gaps (e.g., a maximum or allowed duration for the schedule gap, gap length, periodicity, etc.); (vi) an indication of a schedule gap capability per DC combination (e.g., schedule gap(s) are allowed for EN-DC); or (vii) an indication of a schedule gap policy for each of one or more RATs (e.g., allow schedule gap corresponding to <NUM>/<NUM>, forbid the schedule gap for <NUM>/<NUM>).

The transceiver <NUM> is configured to transmit and receive signals for the communications device <NUM> via an antenna <NUM>, such as the various signals described herein.

The processing system <NUM> includes a processor <NUM> coupled to a computer-readable medium/memory <NUM> via a bus <NUM>. In certain aspects, the computer-readable medium/memory <NUM> is configured to store instructions that when executed by processor <NUM>, cause the processor <NUM> to perform the operations illustrated in <FIG> and/or other operations for performing the various techniques discussed herein.

In certain aspects, the processing system <NUM> further includes a communicating component <NUM> for performing the operations illustrated at <NUM> in <FIG> and/or other communication operations described herein. Additionally, the processing system <NUM> includes a schedule gap component <NUM> for performing the operations illustrated at <NUM>-<NUM> in <FIG> and/or operations described herein. The communicating component <NUM> and schedule gap component <NUM> may be coupled to the processor <NUM> via bus <NUM>. In certain aspects, the communicating component <NUM> and schedule gap component <NUM> may be hardware circuits. In certain aspects, the communicating component <NUM> and schedule gap component <NUM> may be software components that are executed and run on processor <NUM>.

In certain aspects, the processing system <NUM> further includes a communicating component <NUM> for performing the operations illustrated at <NUM> and <NUM> in <FIG> and/or other communication operations described herein. Additionally, the processing system <NUM> includes a schedule gap component <NUM> for performing the operations illustrated at <NUM>-<NUM> in <FIG> and/or operations described herein. The communicating component <NUM> and schedule gap component <NUM> may be coupled to the processor <NUM> via bus <NUM>. In certain aspects, the communicating component <NUM> and schedule gap component <NUM> may be hardware circuits. In certain aspects, the communicating component <NUM> and schedule gap component <NUM> may be software components that are executed and run on processor <NUM>.

In certain aspects, the processing system <NUM> further includes a communicating component <NUM> for performing the operations illustrated at <NUM> and <NUM> in <FIG> and/or other communication operations described herein. Additionally, the processing system <NUM> includes a schedule gap component <NUM> for performing the operations illustrated at <NUM> and <NUM> in <FIG> and/or operations described herein. The communicating component <NUM> and schedule gap component <NUM> may be coupled to the processor <NUM> via bus <NUM>. In certain aspects, the communicating component <NUM> and schedule gap component <NUM> may be hardware circuits. In certain aspects, the communicating component <NUM> and schedule gap component <NUM> may be software components that are executed and run on processor <NUM>.

Claim 1:
A method for wireless communication by a user equipment (<NUM>), UE (<NUM>), comprising:
identifying a network (<NUM>) to access for communications;
transmitting an indication of schedule gap support information for the UE (<NUM>) to the network (<NUM>), the schedule gap support information comprising information associated with transitioning or tuning away from a first RAN associated with a first universal subscriber identity module, USIM, of the UE (<NUM>) to at least a second RAN associated with a second USIM of the UE (<NUM>); and
receiving, from a RAN node, allowed schedule gap information for the UE (<NUM>) based on the schedule gap support information, to use when requesting a schedule gap from the RAN node.