Patent Description:
A wireless network comprises a plurality of network nodes including terminal nodes and access nodes. Communication between the terminal nodes and the access nodes is wireless.

In some circumstances, it may be desirable to modify or enhance how paging is configured in the wireless network. Prior art related to paging on multiple mobile network connections is to be found in the following documents:.

The invention is defined in the appended dependent claims. Specific embodiments of the invention are defined in the appended dependent claims.

According to various, but not necessarily all, examples there is provided an apparatus comprising.

In some examples, the configuration information comprises at least one uplink grant and monitoring for a response from the first user equipment comprises monitoring for a response from the first user equipment on the at least one uplink grant.

In some examples, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus to perform:
receiving assistance information, the assistance information comprising information at least indicative of an early paging indication configuration of the second user equipment at a network.

In some examples, the part of the scheduling gap comprises at least a portion of the scheduling gap after a part of the scheduling gap corresponding to possible reception of an early paging indication by the second user equipment.

In some examples, the configuration information comprises information to inform the first user equipment that there is traffic to be scheduled for the first user equipment during the part of the scheduling gap.

In some examples, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus to perform:.

In some examples, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus to perform:
transmitting pre-configuration information to the first user equipment, the pre-configuration information comprising information to inform the first user equipment that early end of the scheduling gap is possible and/or to configure the first user equipment to monitor for the configuration information.

In some examples, the configuration information comprises a physical downlink control channel with a single uplink grant.

In some examples, the configuration information comprises information at least indicative of a traffic type and/or a service type associated with the traffic.

In some examples, the assistance information comprises paging probability information and the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus to perform:
determining whether to transmit the configuration information based, at least in part, on the paging probability information or determining whether to schedule traffic for the first user equipment during the part of the scheduling gap based, at least in part on the paging probability information.

In some examples, the configuration information comprises information to configure the first user equipment to resume radio connected operation during the part of the scheduling gap unless the second user equipment receives an early indication of paging.

According to various, but not necessarily all, examples there is provided a method comprising:
enabling scheduling gap usage in relation to a device with multiple subscriptions comprising at least a first subscription configured to enable a first user equipment at the device and a second subscription configured to enable a second user equipment at the device by:.

In some examples the method comprising:
receiving assistance information, the assistance information comprising information at least indicative of an early paging indication configuration of the second user equipment at a network.

In some examples, the method comprising:.

In some examples, the method comprising:
transmitting pre-configuration information to the first user equipment, the pre-configuration information comprising information to inform the first user equipment that early end of the scheduling gap is possible and/or to configure the first user equipment to monitor for the configuration information.

In some examples, the assistance information comprises paging probability information and the method comprising:
determining whether to transmit the configuration information based, at least in part, on the paging probability information or determining whether to schedule traffic for the first user equipment during the part of the scheduling gap based, at least in part on the paging probability information.

According to various, but not necessarily all, examples there is provided a computer program comprising instructions for causing an apparatus to perform at least the following:
enabling scheduling gap usage in relation to a device with multiple subscriptions comprising at least a first subscription configured to enable a first user equipment at the device and a second subscription configured to enable a second user equipment at the device by:.

In some examples, the computer program comprising instructions for causing an apparatus to perform:
receiving assistance information, the assistance information comprising information at least indicative of an early paging indication configuration of the second user equipment at a network.

In some examples, the computer program comprising instructions for causing an apparatus to perform:.

In some examples, the computer program comprising instructions for causing an apparatus to perform:
transmitting pre-configuration information to the first user equipment, the pre-configuration information comprising information to inform the first user equipment that early end of the scheduling gap is possible and/or to configure the first user equipment to monitor for the configuration information.

In some examples, the assistance information comprises paging probability information and the computer program comprising instructions for causing an apparatus to perform:
determining whether to transmit the configuration information based, at least in part, on the paging probability information or determining whether to schedule traffic for the first user equipment during the part of the scheduling gap based, at least in part on the paging probability information.

According to various, but not necessarily all, embodiments there is provided an apparatus comprising means for:
enabling scheduling gap usage in relation to a device with multiple subscriptions comprising at least a first subscription configured to enable a first user equipment at the device and a second subscription configured to enable a second user equipment at the device by:.

In some examples, the means are configured to:
receive assistance information, the assistance information comprising information at least indicative of an early paging indication configuration of the second user equipment at a network.

In some examples, the means are configured to:.

In some examples, the means are configured to:
transmit pre-configuration information to the first user equipment, the pre-configuration information comprising information to inform the first user equipment that early end of the scheduling gap is possible and/or to configure the first user equipment to monitor for the configuration information.

In some examples, the assistance information comprises paging probability information and wherein the means are configured to:
determine whether to transmit the configuration information based, at least in part, on the paging probability information or determine whether to schedule traffic for the first user equipment during the part of the scheduling gap based, at least in part on the paging probability information.

In some examples the configuration information comprises at least one uplink grant;.

In some examples, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus to perform:
transmitting assistance information comprising information at least indicative of an early paging indication configuration of the second user equipment at a network.

In some examples, transmitting a response comprises transmitting a response indicating that the first user equipment is available for scheduling of traffic in the part of the scheduling gap; and
the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus to perform:
receiving traffic for the first user equipment during the part of the scheduling gap.

In some examples, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus to perform:
receiving pre-configuration information, the pre-configuration information comprising information to inform the first user equipment that early end of the scheduling gap is possible and/or to configure the first user equipment to monitor for the configuration information.

In some examples, transmitting a response comprises transmitting a response indicating that the first user equipment is not available for scheduling of traffic in the part of the scheduling gap.

According to various, but not necessarily all, examples there is provided a method comprising:
supporting scheduling gap usage in relation to a device with multiple subscriptions comprising at least a first subscription configured to enable a first user equipment at the device and a second subscription configured to enable a second user equipment at the device by:.

In some examples, the method comprising:
transmitting assistance information comprising information at least indicative of an early paging indication configuration of the second user equipment at a network.

In some examples, transmitting a response comprises transmitting a response indicating that the first user equipment is available for scheduling of traffic in the part of the scheduling gap; and
the method comprising:
receiving traffic for the first user equipment during the part of the scheduling gap.

In some examples, the method comprising:
receiving pre-configuration information, the pre-configuration information comprising information to inform the first user equipment that early end of the scheduling gap is possible and/or to configure the first user equipment to monitor for the configuration information.

In some examples transmitting a response comprises transmitting a response indicating that the first user equipment is not available for scheduling of traffic in the part of the scheduling gap.

According to various, but not necessarily all, examples there is provided a computer program comprising instructions for causing an apparatus to perform:
supporting scheduling gap usage in relation to a device with multiple subscriptions comprising at least a first subscription configured to enable a first user equipment at the device and a second subscription configured to enable a second user equipment at the device by:.

In some examples, the configuration information comprises at least one uplink grant;.

In some examples, the computer program comprising instructions for causing an apparatus to perform:
transmitting assistance information comprising information at least indicative of an early paging indication configuration of the second user equipment at a network.

In some examples, transmitting a response comprises transmitting a response indicating that the first user equipment is available for scheduling of traffic in the part of the scheduling gap; and
the computer program comprising instructions for causing an apparatus to perform:
receiving traffic for the first user equipment during the part of the scheduling gap.

In some examples, the computer program comprising instructions for causing an apparatus to perform:
receiving pre-configuration information, the pre-configuration information comprising information to inform the first user equipment that early end of the scheduling gap is possible and/or to configure the first user equipment to monitor for the configuration information.

In some exampes, the configuration information comprises information at least indicative of a traffic type and/or a service type associated with the traffic.

According to various, but not necessarily all, embodiments there is provided an apparatus comprising means for:
supporting scheduling gap usage in relation to a device with multiple subscriptions comprising at least a first subscription configured to enable a first user equipment at the device and a second subscription configured to enable a second user equipment at the device by:.

In some examples, the means are configured to:
transmit assistance information comprising information at least indicative of an early paging indication configuration of the second user equipment at a network.

In some examples, transmitting a response comprises transmitting a response indicating that the first user equipment is available for scheduling of traffic in the part of the scheduling gap; and
wherein the means are configured to:
receive traffic for the first user equipment during the part of the scheduling gap.

In some examples, the means are configured to:
receive pre-configuration information, the pre-configuration information comprising information to inform the first user equipment that early end of the scheduling gap is possible and/or to configure the first user equipment to monitor for the configuration information.

According to various, but not necessarily all, examples there is provided an apparatus comprising means for performing at least part of one or more methods disclosed herein.

According to various, but not necessarily all, examples there is provided examples as claimed in the appended claims.

The description of a function and/or action should additionally be considered to also disclose any means suitable for performing that function and/or action.

RRC_CONNECTED - A state where UE has dedicated radio connection for active data transmission.

RRC_INACTIVE - A state where UE monitors for paging and needs to establish radio connection with gNodeB (gNB) to start data transmission. In this state the radio-resource related configuration is stored at UE for quick resuming of RRC connection. Likewise, the UE context is not released at the network. This state is maintained between UE and gNB (base station).

RRC_IDLE - A state where UE monitors for paging and needs to establish radio connection to start data transmission. As there is no radio-resource configuration stored the RRC connection setup procedure is used to configure radio resources.

<FIG> illustrates an example of a network <NUM> comprising a plurality of network nodes including terminal nodes <NUM>, access nodes <NUM> and one or more core nodes <NUM>. The terminal nodes <NUM> and access nodes <NUM> communicate with each other. The one or more core nodes <NUM> communicate with the access nodes <NUM>.

The network <NUM> is in this example a telecommunications network, in which at least some of the terminal nodes <NUM> and access nodes <NUM> communicate with each other using transmission/reception of radio waves/signals.

The one or more core nodes <NUM> may, in some examples, communicate with each other. The one or more access nodes <NUM> may, in some examples, communicate with each other.

The one or more terminal nodes <NUM> may, in some examples, communicate with each other.

The network <NUM> may be a cellular network comprising a plurality of cells <NUM> at least one served by an access node <NUM>. In this example, the interface between the terminal nodes <NUM> and an access node <NUM> defining a cell <NUM> is a wireless interface <NUM>.

The access node(s) <NUM> is a cellular radio transceiver. The terminal nodes <NUM> are cellular radio transceivers.

In the example illustrated the cellular network <NUM> is a third generation Partnership Project (3GPP) network in which the terminal nodes <NUM> are user equipment (UE) and the access nodes <NUM> are base stations (for example, gNBs).

Functionality of a base station may be distributed between a central unit (CU), for example a gNB-CU, and one or more distributed units (DU), for example gNB-DUs.

In the particular example illustrated the network <NUM> is an Evolved Universal Terrestrial Radio Access network (E-UTRAN). The E-UTRAN consists of E-UTRAN NodeBs (eNBs), providing the E-UTRA user plane and control plane (for example, RRC) protocol terminations towards the UE. The eNBs <NUM> are interconnected with each other by means of an X2 interface <NUM>. The eNBs are also connected by means of the S1 interface <NUM> to the Mobility Management Entity (MME) <NUM>.

In other example the network <NUM> is a Next Generation (or New Radio, NR) Radio Access network (NG-RAN). The NG-RAN consists of gNodeBs (gNBs), providing the user plane and control plane (for example, RRC) protocol terminations towards the UE. The gNBs are interconnected with each other by means of an X2/Xn interface <NUM>. The gNBs are also connected by means of the N2 interface <NUM> to the Access and Mobility management Function (AMF).

In examples, the network <NUM> can comprise a combination of E-UTRAN and NG-RAN.

In examples, a terminal node <NUM> can monitor for paging signals. Paging configuration at a terminal node <NUM> can be configured by the network, for example by an access node <NUM> or core node <NUM>.

<FIG> illustrates an example of a method <NUM>.

In examples, <FIG> can be considered to illustrate a plurality of methods. For example, <FIG> illustrates one or more actions at a plurality of actors/entities. In examples, <FIG> can be considered to illustrate a plurality of methods performed by the individual actors/entities.

One or more of the features discussed in relation to <FIG> can be found in one or more of the other FIGs. During discussion of <FIG>, reference will be made to other FIGs for the purposes of explanation.

In the example of <FIG>, a plurality of apparatuses transmit and/or receive one or more signals and/or one or more messages across and/or via and/or using a network. In examples, any suitable form of communication in any suitable network can be used. For example, at least a portion of the network <NUM> of <FIG> can be used.

Accordingly, in examples, the plurality of apparatuses in <FIG> form at least a portion of a network <NUM> as described in relation to <FIG>.

In the illustrated example, a terminal node <NUM> and a network node transmit and/or receive one or more signals and/or one or more messages.

In examples, communications and/or transmissions between elements illustrated in <FIG> can proceed via any number of intervening elements, including no intervening elements.

In examples, method <NUM> and/or parts of method <NUM> can be considered a method of controlling scheduling gaps for paging monitoring at a terminal node <NUM> and/or a method of reducing scheduling gaps for paging monitoring at a terminal node <NUM> at a terminal node <NUM>.

In some examples, method <NUM> and/or parts of method <NUM> can be considered a method of efficiently using scheduling gaps for paging monitoring and/or a method of minimizing scheduling gaps for paging monitoring.

In some examples, the network node is/comprises an access node <NUM>, such as a gNodeB (gNB). In some examples, the network node is/comprises a core node <NUM>.

In some examples, the terminal node <NUM> is a device with multiple subscriptions comprising at least a first subscription configured to enable a first user equipment (UE1) at the device and a second subscription configured to enable a second user equipment (UE2) at the device. However, in examples, the terminal node <NUM> can have any suitable number of subscriptions configured to enable any suitable number of UEs at the terminal node <NUM>.

Any suitable subscription can be used. In examples, a subscription can be a 3GPP subscription, a 3GPP2 subscription, an Enhanced Support of Non-Public Networks (eNPN) subscription and so on.

In some examples, the terminal node <NUM> is a multiple SIM device and/or a multiple USIM (MUSIM) device comprising a plurality of SIMs/USIMs configured to enable a plurality of UEs at the terminal node <NUM>.

Accordingly, in examples, the terminal node <NUM> is a MUSIM device comprising at least a first USIM configured to enable a first UE (UE1) at the device and a second USIM configured to enable a second UE (UE2) at the device. However, in examples, the terminal node <NUM> can have any suitable number of USIMs configured to enable any suitable number of UEs at the terminal node <NUM>.

In examples, the terminal node <NUM> can be considered a device configured for multiple USIM operation.

In examples, a subscription and/or USIM can be considered to enable and/or configure and/or provide a UE at the terminal node <NUM>.

In examples, enabling and/or configuring and/or providing a UE at the terminal node <NUM> can be considered enabling and/or configuring and/or providing UE functionality at the terminal node <NUM>.

In examples, enabling and/or configuring and/or providing a UE at the terminal node <NUM> can be considered enabling and/or configuring and/or providing the terminal node <NUM> to function as a UE.

For example, a terminal node <NUM> configured with multiple subscriptions and/or multiple USIMs is enabled to receive paging for each of the registered subscriptions and/or USIMs.

Accordingly, in examples, enabling a first UE at the terminal node <NUM> can be considered enabling the terminal node <NUM> to function as a first UE.

Accordingly, in examples, enabling a second UE at the terminal node <NUM> can be considered enabling the terminal node <NUM> to function as a second UE.

Accordingly, in examples, enabling a first and second UE at the terminal node <NUM> can be considered enabling the terminal node <NUM> to function as a first UE and also as a second UE.

In examples, the subscriptions at the terminal node <NUM> and/or USIMS at the terminal node <NUM> and/or UEs enabled at the terminal node <NUM> have at least one associated identifier. For example, a first subscription and/or first USIM and/or first UE (UE1) enabled at the terminal node <NUM> has an associated identifier, a second subscription and/or USIM and/or UE (UE2) enabled at the terminal node <NUM> has a different associated identifier and so on.

Any suitable identifier(s) can be used. For example, International Mobile Subscriber Identities (IMSI) in case of evolved packet system (EPS) or Subscription Permanent Identifier (SUPI) in case of <NUM> system.

In examples, the subscriptions at the terminal node <NUM> and/or USIMS at the terminal node <NUM> and/or UEs enabled at the terminal node <NUM> can be assigned a temporary identifier such as Temporary Mobile Subscriber Identity (TMSI) or a Global Unique Temporary Identifier (GUTI) and so on.

Accordingly, in examples, from the point of view of the network, the terminal node <NUM> represents a plurality of UEs having different associated identifiers.

In examples, a paging configuration for a UE can be based, at least in part, on one or more identifiers associated with a subscription and/or USIM and/or UE enabled at the terminal node.

In examples, the plurality of subscriptions and/or USIMS and/or UEs enabled at the terminal node <NUM> are associated with one or more networks.

In some examples, one or more subscriptions and/or USIMS and/or UEs enabled at the terminal node <NUM> can be associated with one or more different networks.

In examples, a first subscription and/or USIM and/or UE (UE1) enabled at the terminal node <NUM> is associated with a first network and a second subscription and/or USIM and/or UE (UE2) enabled at the terminal node <NUM> is associated with a second, different network.

Accordingly, in examples, the terminal node <NUM> can be considered a MUSIM device comprising at least a first USIM configured to enable a first UE (UE1) associated with a first network and a second USIM configured to enable a second UE (UE2) associated with a second, different network.

In examples, different network nodes can be associated with different networks. See, for example, <FIG>.

In examples, the receiving capability and/or receiving configuration of the terminal node <NUM> is restricted and/or limited compared to the number of subscriptions and/or USIMs and/or UEs enabled at the terminal node <NUM>.

In some examples, the receiving capability and/or configuration of the terminal node <NUM> can be considered to be restricted and/or limited compared to the number of different networks associated with the subscriptions and/or USIMs and/or UEs enabled at the terminal node <NUM>.

For example, the terminal node <NUM> can have enabled UEs associated with a first network and second, different network but be configured to receive from one network at a time.

Similarly, the terminal node <NUM> can have enabled UEs associated with three different networks but be configured to receive from one or two different networks at a time and so on.

The terminal node <NUM> having restricted and/or limited receiving capability compared to the number of associated networks can cause problems in relation to paging.

For example, a radio connection at a first UE enabled at the terminal node <NUM> with a first network can be interrupted by paging for a second UE enabled at the terminal node and in radio inactive mode with a second, different network, if the terminal node cannot receive from both networks simultaneously.

In examples, a scheduling gap <NUM> is configured for the first UE to allow for paging of the second UE. For example, a scheduling gap <NUM> can be configured for the first UE corresponding with a paging occasion <NUM> of the second UE.

In examples, a scheduling gap can be considered a period of time in which there is no uplink or downlink scheduling for a UE.

In examples, a scheduling gap <NUM> can be considered a scheduling break, a scheduling pause and/or a scheduling hiatus and so on.

By way of example, reference is made to <FIG>.

In the upper portion of <FIG>, a scheduling gap <NUM> for a first UE is illustrated by a shaded rectangle corresponding to a paging occasion <NUM> as illustrated in the lower portion of <FIG>.

Accordingly, as can be seen from the example of <FIG>, scheduling of traffic for the first UE is interrupted for the duration of the scheduling gap <NUM>, to allow for reception at the second UE for the paging occasion <NUM> of the second UE.

Referring back to <FIG>, in examples, method <NUM> and/or parts of method <NUM> can be considered a method <NUM> of enabling and/or supporting scheduling gap usage in relation to a device with multiple subscriptions comprising at least a first subscription configured to enable a first user equipment (UE) <NUM> at the device and a second subscription configured to enable a second user equipment (UE) <NUM> at the device.

In examples, the first UE <NUM> is in radio connected mode and the second UE <NUM> is not in radio connected mode. For example, the second UE <NUM> can be in radio idle mode or radio inactive mode.

In examples, the network node in <FIG> is a network node to which the first UE <NUM> is connected in radio connected mode.

A radio connected mode, a radio idle mode and/or a radio inactive mode can comprise/be any suitable mode of a UE at the terminal node <NUM>.

For example, a radio connected mode can be a mode where a UE has a dedicated radio connection for active data transmission.

For example, a radio inactive mode can be a mode where a UE monitors for paging and has to establish a radio connection to start data transmission. In a radio inactive mode, a radio-resource related configuration is stored at a UE for resuming of a radio connection, such as an RRC connection.

For example, a radio idle mode can be a mode where a UE monitors for paging and has to establish a radio connection to start data transmission. In this mode, a radio connection procedure, such as an RRC connection procedure, is used to configure radio resources.

A radio connected mode can be an RRC_CONNECTED mode. A radio inactive mode can be an RRC_INACTIVE mode. A radio idle mode can be an RRC_IDLE mode.

In examples, a radio mode can be considered a radio state.

At block <NUM>, method <NUM> comprises transmitting assistance information <NUM> comprising information at least indicative of an early paging indication configuration of the second UE <NUM> at a network.

In the illustrated example, the location of the blocks indicates the entity performing the action(s). For example, in <FIG>, block <NUM> is performed at and/or by the terminal node <NUM>.

In the example of <FIG>, block <NUM> can be considered to be performed by the terminal node <NUM> and/or the first UE <NUM> at the terminal node <NUM>.

As <FIG> illustrates one or more actions of transmission, <FIG> also illustrates the corresponding receiving feature(s)/action(s) and vice versa.

For example, from the point of view of the network node, block <NUM> can be considered to illustrate receiving assistance information <NUM> comprising information at least indicative of an early paging indication configuration of the second UE <NUM> at a network.

This is illustrated in the example of <FIG>, by the arrow pointing from block <NUM> to the line representing the network node.

In examples, the assistance information <NUM> can comprise any suitable information. For example, the assistance information <NUM> can comprise any suitable information to inform the network node of an early paging indication configuration of the second UE <NUM> as configured by the second network associated with the second UE <NUM> (not illustrated in the example of <FIG>).

In examples, the assistance information <NUM> comprises information to allow the network node, and therefore the network associated with the first UE <NUM>, to know the configuration of the second UE <NUM> to receive early paging indication.

In examples, an early paging indication configuration can be considered a configuration to receive an early paging indication.

An early paging indication can be and/or comprise any suitable information to inform the second UE <NUM> if there is paging present during a paging occasion <NUM> of the second UE <NUM>.

In examples, the early paging indication is and/or comprises a paging early indicator (PEI). In such examples, the early paging indication configuration of the second UE <NUM> can be considered a PEI configuration of the second UE <NUM>.

In examples, the terminal node <NUM> can determine the assistance information <NUM>. In some examples, the first UE <NUM> can be considered to determine the assistance information <NUM>.

Accordingly, in some examples, method <NUM> can be considered to comprise determining assistance information <NUM>.

As used herein, the term "determining" (and grammatical variants thereof) can include, not least: calculating, computing, processing, deriving, investigating, looking up (for example, looking up in a table, a database or another data structure), ascertaining and the like. Also, "determining" can include receiving (for example, receiving information), accessing (for example, accessing data in a memory) and the like. Also, "determining" can include resolving, selecting, choosing, establishing, and the like.

In examples, information at least indicative of an early paging indication configuration of the second UE <NUM> can be received by the first UE <NUM> from the second UE <NUM>.

Accordingly, in some examples, an early paging indication configuration is received by the second UE <NUM>, from the network associated with the second UE <NUM>, and information at least indicative of the early paging indication configuration internally provided to the first UE <NUM> in the terminal node <NUM>.

In some examples, the assistance information <NUM> comprises information for/to be used by the network node in determining if configuration information <NUM> should be transmitted to the terminal node <NUM>. See, for example, block <NUM>.

In examples, the assistance information <NUM> comprises paging probability information of the second UE <NUM>.

In examples paging probability information can be considered any suitable information at least indicative of and/or configured to allow and/or enable a determination of paging probability of the second UE <NUM>.

For example, paging probability information can comprise information at least indicative of the probability that the second UE <NUM> will be paged at a given paging occasion <NUM> of the second UE <NUM>.

In some examples, paging probability information can comprise information at least indicative of how frequently the second UE <NUM> has been paged over a number of previous paging occasions <NUM>.

In examples, paging probability information can be determined at and/or by the terminal node <NUM> in any suitable way using any suitable method.

In some examples, the second UE <NUM> can monitor the number of times that the second UE <NUM> is paged across a number of paging occasions <NUM> and determine the paging probability information based, at least in part, on the monitoring.

In some examples, the second UE <NUM> can internally provide data from the monitoring to the first UE <NUM> to allow the first UE <NUM> to determine the paging probability information.

In some examples, the data from the monitoring can be considered paging probability information and can be transmitted to the network node.

Accordingly, in examples, method <NUM> comprises determining paging probability information and transmitting the determined paging probability information in and/or with the assistance information <NUM>.

In some examples, method <NUM> does not comprise block <NUM>. Accordingly, in some examples, block <NUM> can be omitted.

In the example of <FIG> a scheduling gap <NUM> is configured for the first UE <NUM> corresponding to a paging occasion <NUM> of the second UE <NUM>.

In some examples, a plurality of scheduling gaps <NUM> are configured for the first UE <NUM> corresponding to a plurality of paging occasions <NUM> of the second UE <NUM>. In examples, the plurality of scheduling gaps <NUM> can be periodic.

At block <NUM>, method <NUM> comprises transmitting pre-configuration information <NUM> to the first UE <NUM>, the pre-configuration information <NUM> comprising information to inform the first UE <NUM> that early end of the scheduling gap <NUM> is possible and/or to configure the first UE <NUM> to monitor for configuration information <NUM>. See, for example, block <NUM>.

In examples, the pre-configuration information <NUM> can be transmitted with information to configure one or more scheduling gaps <NUM> for the first UE <NUM>. For example, the pre-configuration information <NUM> can be transmitted with a radio connection configuration message, for example an RRCConnectionReconfiguration message to the first UE <NUM>. See, for example, <FIG> and <FIG>.

In examples, the pre-configuration information <NUM> can comprise any suitable information to inform the first UE <NUM> that early end of the scheduling gap <NUM> is possible and/or to configure the first UE <NUM> to monitor for configuration information <NUM>.

In examples, information to inform the first UE <NUM> that early end of the scheduling gap <NUM> is possible can be considered information to inform the first UE <NUM> that it is possible that scheduling of traffic for the first UE <NUM> will start prior to the end of the scheduling gap <NUM>.

In some examples, the pre-configuration information <NUM> comprises information to inform the first UE <NUM> that it is possible that the scheduling gap <NUM> will end after a part of the scheduling gap <NUM> corresponding to possible reception of an early paging indicator by the second UE <NUM>.

In some examples, the pre-configuration information <NUM> comprises information to configure the first UE <NUM> to monitor for configuration information <NUM> after a part of the scheduling gap <NUM> corresponding to possible reception of an early paging indicator by the second UE.

In examples, the pre-configuration information <NUM> can be considered configuration information.

In examples, the pre-configuration information <NUM> is transmitted based, at least in part, on the type of traffic and/or service type at the first UE <NUM>. For example, the pre-configuration information <NUM> can be transmitted when it is possible, but not certain, that there is traffic to schedule for the first UE <NUM> during the scheduling gap <NUM>.

Accordingly, in examples, the pre-configuration information <NUM> can be considered information to prepare and/or configure the first UE <NUM> for an early end of the scheduling gap <NUM>.

In some examples, there can be ongoing traffic with the first UE <NUM> and the pre-configuration information <NUM> is not transmitted. That is, in some examples, block <NUM> can be omitted.

In some examples, the configuration information <NUM> can be used to inform the first UE <NUM> that there is traffic to be scheduled during the scheduling gap <NUM>. Accordingly, in such examples, the pre-configuration information <NUM> can be transmitted to configure the first UE <NUM> to monitor for the configuration information <NUM>. See, for example, <FIG> and <FIG>.

However, in examples where there is ongoing traffic with the first UE <NUM>, the network node does not have to inform the first UE <NUM> that there is traffic to be scheduled during the scheduling gap <NUM> and therefore, in some examples, the pre-configuration information <NUM> can be omitted as the first UE <NUM> is already aware that there is traffic to be scheduled during the scheduling gap and does not have to monitor for an indication that there is traffic to be scheduled in the scheduling gap <NUM>. See, for example, <FIG>.

At block <NUM>, method <NUM> comprises determining if there is traffic to schedule for the first UE <NUM>, in radio connected mode, during a part <NUM> of a configured scheduling gap <NUM> for the first user equipment <NUM> corresponding to a paging occasion <NUM> of the second UE <NUM>, the second UE <NUM> not in radio connected mode.

In examples, determining if there is traffic to schedule for the first UE <NUM> at block <NUM> can be performed in any suitable way using any suitable method.

In some examples, determining if there is traffic to schedule for the first UE <NUM> at block <NUM> comprises determining if there is ongoing traffic with the first UE <NUM>.

In some examples, determining if there is traffic to schedule for the first UE <NUM> at block <NUM> comprises determining if there is ongoing traffic with the first UE <NUM> that is sensitive to interruption.

For example, there can already be ongoing traffic with the first UE <NUM> when a request for a scheduling gap <NUM> is received by the network node.

Accordingly, in examples, block <NUM> can be performed prior to the scheduling gap <NUM> starting.

In some examples, determining if there is traffic to schedule for the first UE <NUM> at block <NUM> comprises determining if data has been received for transmission to the first UE <NUM> during the part <NUM> of the scheduling gap <NUM>.

Accordingly, in examples, determining if there is traffic to schedule for the first UE <NUM> at block <NUM> can be performed after the scheduling gap <NUM> has started. For example, block <NUM> can, in some examples, be performed during and/or after a part of the scheduling gap <NUM> corresponding to possible reception of an early paging indicator by the second UE <NUM>.

In examples, the part <NUM> of the scheduling gap <NUM> can be and/or comprise any suitable part <NUM> of the scheduling gap <NUM>.

In some examples, the part <NUM> of the scheduling gap <NUM> comprises at least a portion of the scheduling gap after a part of the scheduling gap <NUM> corresponding to possible reception of an early paging indication by the second UE <NUM>, for example a PEI.

In <FIG>, the upper portion relates to the first UE <NUM> on the first network and the lower portion relates to the second UE <NUM> on the second network.

Two different examples are shown in the left and right portions of <FIG> respectively.

The shaded rectangle in the upper portion of <FIG> illustrates the duration of the configured scheduling gap <NUM> for the first UE <NUM>. The scheduling gap <NUM> corresponds to a paging occasion <NUM> of the second UE <NUM>, as illustrated in the lower portion of <FIG>.

In the example of <FIG> a dashed line separating the scheduling gap <NUM> into two parts is also shown.

In the illustrated example, the part of the scheduling gap <NUM> to the left of the dashed line corresponds to possible reception of an early paging indication by the second UE <NUM>, such as a PEI.

For example, in the left portion of <FIG> an early paging indication is received by the second UE <NUM> and in the right portion of <FIG> an early paging indication is not received by the second UE <NUM>.

In examples, the part <NUM> of the scheduling gap <NUM> is/comprises the part <NUM> of the scheduling gap <NUM> to the right of the dashed line in <FIG> which is the portion of the scheduling gap <NUM> after a part of the scheduling gap <NUM> corresponding to possible reception of an early paging indication by the second UE <NUM>.

Other features of <FIG> will be discussed in greater detail below.

Referring to <FIG>, at block <NUM>, method <NUM> comprises if it is determined that there is traffic to schedule for the first UE <NUM> during a part <NUM> of the scheduling gap <NUM>, transmitting configuration information <NUM> to the first UE <NUM> to configure the first UE <NUM> to provide a response indicating device availability of the device for the part <NUM> of the scheduling gap <NUM>.

Accordingly, from the point of view of the terminal node <NUM> and/or the first UE <NUM>, block <NUM> comprises receiving configuration information <NUM> to configure the first UE <NUM>, in radio connected mode, to provide a response indicating device availability of the device for a part <NUM> of a configured scheduling gap <NUM> for the first UE <NUM> corresponding to a paging occasion <NUM> of the second UE <NUM>, the second UE <NUM> not in radio connected mode.

In examples, providing a response indicating device availability of the device can be considered providing information and/or an indication of device availability.

In some examples, block <NUM> can be considered to comprise receiving configuration information <NUM> to configure the first UE <NUM>, in radio connected mode, to provide a response indicating first UE <NUM> availability for a part <NUM> of a configured scheduling gap <NUM> for the first UE <NUM> corresponding to a paging occasion <NUM> of the second UE <NUM>, the second UE <NUM> not in radio connected mode.

In examples, device availability and/or first UE <NUM> availability for the part <NUM> of the configured scheduling gap <NUM> can be considered device availability and/or first UE <NUM> availability for scheduling of traffic during the part <NUM> of the configured scheduling gap <NUM>.

In examples, the configuration information <NUM> can have any suitable form and/or comprise any suitable information.

In examples, the form of the configuration information <NUM> can depend on the type of traffic and/or service at the first UE <NUM>. For example, the form of the configuration information <NUM> can be different for ongoing traffic at the first UE <NUM> compared to no ongoing traffic at the first UE <NUM>.

In examples, the configuration information <NUM> can be transmitted in any suitable way. In some examples, such as some examples where there is ongoing traffic with the first UE <NUM>, the configuration information <NUM> can be transmitted with a radio connection reconfiguration message, such as an RRCConnectionReconfiguration message.

In some examples, the configuration information <NUM> comprises at least one uplink grant. For example, the configuration information <NUM> can comprise a single uplink grant or a configured grant.

In examples, the configuration information <NUM> comprises a physical downlink control channel with a single uplink grant.

In some examples, the configuration information <NUM> comprises information to configure the terminal node <NUM> and/or first UE <NUM> to provide an appropriate acknowledgement, such as a control channel acknowledgement.

In some examples, such as some examples where there is no ongoing traffic with the first UE <NUM>, the configuration information <NUM> comprises information to inform the first UE <NUM> that there is traffic to be scheduled for the first UE <NUM> during the part <NUM> of the scheduling gap <NUM>. See, for example, <FIG> and <FIG>.

In examples, such as some examples where there is no ongoing traffic with the first UE <NUM>, the configuration information <NUM> can be considered to be and/or comprise an indication of traffic for scheduling.

In some examples, such as some examples where there is no ongoing traffic with the first UE <NUM>, the configuration information <NUM> can be considered a scheduling early indication (SEI) and/or an activation signal.

By way of example, reference is again made to <FIG>.

In the examples illustrated in <FIG>, the arrow pointing downwards across the illustrated scheduling gap <NUM> in the upper portion of <FIG> shows transmission/receipt of configuration information <NUM> in the form of an SEI.

In the example of <FIG>, the SEI is transmitted/received after the part of the scheduling gap <NUM> corresponding to possible reception of an early paging indication by the second UE <NUM>, such as a PEI.

Accordingly, in the examples shown in <FIG>, the network node transmits the configuration information <NUM>, which in these examples is in the form of an SEI, to inform the first UE <NUM> that there is traffic to be scheduled in the part <NUM> of the scheduling gap <NUM>.

In the illustrated example, the first UE <NUM> is configured by the pre-configuration information <NUM> to monitor for the configuration information <NUM>.

In the example to the left of <FIG>, the second UE <NUM> receives an early paging indication, in the form of a PEI, and therefore the first UE <NUM> is not available during the part <NUM> of the scheduling gap <NUM> as the second UE <NUM> monitors for paging during the part <NUM> of the scheduling gap <NUM>.

However, in the example to the right of <FIG>, the second UE <NUM> does not receive an early paging indication and therefore the first UE <NUM> is available during the part <NUM> of the scheduling gap <NUM>.

In the illustrated example, as an SEI has been received, the first UE <NUM> can respond to inform the network node that the first UE <NUM> is available for scheduling during the part <NUM> of the scheduling gap <NUM>.

Referring to <FIG>, in examples, the response indicating device availability of the device for the part <NUM> of the scheduling gap <NUM> can comprise any suitable information having any suitable form.

For example, the response indicating device availability of the device can comprise an acknowledgement, such as a control channel acknowledgement, and/or a response on at least one uplink grant configured by the configuration information <NUM>.

In examples, the response indicating device availability of the device can be positive or negative in nature. For example, the response indicating device availability of the device can indicate that that the first UE <NUM> is or is not available for scheduling of traffic during the part <NUM> of the scheduling gap <NUM>.

In examples, such as some examples where there is no ongoing traffic with the first UE <NUM>, the configuration information <NUM> comprises information at least indicative of a traffic type and/or service type associated with the traffic.

Accordingly, in examples, the configuration information <NUM>, which can be in the form of an SEI, comprises information at least indicative of a traffic type and/or service type associated with the traffic to be scheduled for the first UE <NUM> during the part <NUM> of the scheduling gap <NUM>.

In examples, the information at least indicative of a traffic type and/or service type associated with the traffic can be used by the terminal node <NUM> and/or first UE <NUM> in determining if the first UE <NUM> should be made available for scheduling of traffic during the part <NUM> of the scheduling gap <NUM>.

For example, for a given traffic and/or service type, the first UE <NUM> is made available for scheduling during the part <NUM> of the scheduling gap <NUM> but for a different traffic and/or service type priority is given to the second UE <NUM> during the part <NUM> of the scheduling gap <NUM> and the first UE <NUM> is not made available for scheduling during the part of the scheduling gap <NUM>.

In some examples where the assistance information <NUM> comprises paging probability information method <NUM> comprises determining whether to transmit the configuration information <NUM> based, at least in part, on the paging probability information or determining whether to schedule traffic for the first user equipment during the part of the scheduling gap based, at least in part on the paging probability information.

In examples, determining whether to transmit the configuration information <NUM> based, at least in part, on the paging probability information or determining whether to schedule traffic for the first user equipment during the part of the scheduling gap based, at least in part on the paging probability information can be performed in any suitable way using any suitable method.

For example, the network node can start a persistence test and/or probability test prior to sending the configuration information <NUM>, which can be in the form of an SEI/activation signal.

In examples, such as some examples where there is ongoing traffic at the first UE <NUM>, the configuration information <NUM> comprises information to configure the first UE <NUM> to resume radio connected operation during the part <NUM> of the scheduling gap <NUM> unless the second UE <NUM> receives an early indication of paging. See, for example, <FIG>.

For example, the configuration information <NUM> can be transmitted as part of an RRCConnectionReConfiguration message to configure the first UE <NUM> to resume radio connected operation during the part of the scheduling gap <NUM> unless the second UE <NUM> receives an early indication of paging, such as a PEI.

At block <NUM>, method <NUM> comprises monitoring for a response <NUM> from the first user equipment <NUM>.

Consequently, <FIG> illustrates a method <NUM> comprising:
enabling scheduling gap usage in relation to a device with multiple subscriptions comprising at least a first subscription configured to enable a first user equipment <NUM> at the device and a second user equipment <NUM> at the device by:.

In examples, monitoring for a response <NUM> from the first UE <NUM> can be performed in any suitable way using any suitable method.

In examples, monitoring for a response <NUM> comprises monitoring for a response <NUM> configured by the configuration information <NUM>.

In examples, the response <NUM> can have any suitable form. For example, the response <NUM> can have any suitable form to provide information of the device/first UE <NUM> availability for the part <NUM> of the scheduling gap <NUM>.

In examples, the response <NUM> can be and/or comprise an acknowledgement configured by the configuration information <NUM>, such as a control channel acknowledgement.

In some examples, the response <NUM> can be a response <NUM> transmitted on at least one uplink grant configured by the configuration information <NUM>.

Accordingly, in examples the configuration information <NUM> comprises at least one uplink grant and monitoring for a response <NUM> from the first UE <NUM> comprises monitoring for a response <NUM> from the first UE <NUM> on the at least one uplink grant and/or at least one of the at least one uplink grant.

At block <NUM>, method <NUM> comprises determining whether to transmit a response <NUM> indicating device availability of the device for the part <NUM> of the configured scheduling gap <NUM>.

In examples, at block <NUM>, method <NUM> can be considered to comprise determining whether to transmit a response <NUM> indicating first UE <NUM> availability for the part <NUM> of the configured scheduling gap <NUM>.

In examples, block <NUM> can be performed by the terminal node <NUM> and/or the first UE <NUM>.

In examples, determining whether to transmit a response <NUM> can be performed in any suitable way using any suitable method and based on any suitable information.

In examples, determining whether to transmit a response <NUM> comprises determining if the first UE <NUM> is available for scheduling of traffic during the part <NUM> of the scheduling gap <NUM>.

In examples, determining whether to transmit a response <NUM> comprises determining if an early indication of paging, such as a PEI, has been received by the second UE <NUM>.

For example, the second UE <NUM> can provide information to the first UE <NUM> to inform the first UE <NUM> if an early indication of paging, such as a PEI, has and/or has not been received and, in examples, determining whether to transmit a response <NUM> can be performed based, at least in part, on the information.

In examples, a response <NUM> can have any suitable form as described in relation to block <NUM>.

In examples, a response <NUM> can comprise an indication of device and/or first UE <NUM> availability as described in relation to block <NUM>. For example, a response <NUM> can be positive in nature, indicating availability, or negative in nature, indicating no availability.

In some examples, determining whether to transmit a response can comprise consideration of other information, such as traffic and/or service type of traffic to be scheduled for the first UE <NUM> during the part <NUM> of the scheduling gap <NUM>.

For example, in some examples where the configuration information <NUM> comprises information at least indicative of a traffic type and/or service type, determining whether to transmit a response can be based, at least in part, on the information.

For example, in some examples where no early paging indication is received by the second UE <NUM>, the terminal node <NUM> and/or first UE <NUM> can determine that priority should be given to the second UE <NUM> for the full duration of the scheduling gap <NUM> based, at least in part, on the traffic type and/or service type of traffic to be scheduled for the first UE <NUM> during the part <NUM> of the scheduling gap <NUM>.

In examples, such as some examples where there is no ongoing traffic with the first UE <NUM>, if no configuration information <NUM> is transmitted/received because there is no traffic to schedule for the first UE <NUM> during the scheduling gap <NUM>, blocks <NUM> and <NUM> are not performed as early return of the first UE to scheduling is not needed and therefore the second UE <NUM> can make use of the full scheduling gap <NUM>. See, for example, <FIG>.

At block <NUM>, method <NUM> comprises if it is determined that a response <NUM> is to be sent, transmitting a response <NUM>.

Consequently, <FIG> illustrates a method <NUM> comprising:
supporting scheduling gap usage in relation to a device with multiple subscriptions comprising at least a first subscription configured to enable a first user equipment <NUM> at the device and a second user equipment <NUM> at the device by:.

In examples, at block <NUM>, method <NUM> can be considered to comprise if it is determined that a response <NUM> is to be sent, transmitting a response <NUM> indicating device and/or first UE <NUM> availability for the part <NUM> of the configured scheduling gap <NUM>.

In examples, at block <NUM>, method <NUM> can be considered to comprise if it is determined that a response <NUM> is to be sent, transmitting a response <NUM> comprising information <NUM> of the device and/or first UE <NUM> availability for the part <NUM> of the configured scheduling gap <NUM>.

In examples, any suitable response comprising any suitable information can be transmitted in any suitable way.

For example, the response <NUM> can have any suitable form as described in relation to block <NUM>.

For example, the response <NUM> can comprise any suitable indication of device and/or first UE <NUM> availability as described in relation to block <NUM>.

In examples, the configuration information <NUM> comprises at least one uplink grant. In some such examples, determining whether to transmit a response <NUM> comprises determining whether to transmit a response <NUM> comprises determining whether to transmit a response <NUM> on the at least one uplink grant and transmitting a response <NUM> comprises transmitting a response <NUM> on at least one of the at least one uplink grant.

In some examples, transmitting a response <NUM> comprises transmitting an acknowledgement, such as a control channel acknowledgement, to appropriately indicate device and/or first UE <NUM> availability during the part <NUM> of the scheduling gap <NUM>.

In examples, the response <NUM> can indicate that the device and/or first UE <NUM> is available or is not available for scheduling of traffic during the part <NUM> of the scheduling gap <NUM>.

Accordingly, in examples, from the point of view of the network node, method <NUM> comprises receiving a response <NUM> indicating that the device and/or the first UE <NUM> is or is not available for scheduling of traffic during the part <NUM> of the scheduling gap <NUM>.

For example, in some examples where there is no ongoing traffic with the first UE <NUM>, the response can indicate that the device and/or first UE <NUM> is available for scheduling of traffic during the part <NUM> of the scheduling gap <NUM>.

Accordingly, in some examples, method <NUM> comprises receiving a response <NUM> from the first UE <NUM>, the response <NUM> indicating that the first UE <NUM> is available for scheduling of traffic in the part <NUM> of the scheduling gap <NUM> and in response to receiving the response <NUM> from the first UE <NUM>, scheduling traffic for the first UE <NUM> during the part <NUM> of the scheduling gap <NUM>.

For example, in some examples where there is ongoing traffic with the first UE <NUM>, the response <NUM> can indicate that the device and/or first UE <NUM> is not available for scheduling of traffic during the part <NUM> of the scheduling gap <NUM>.

Accordingly, in some examples, method <NUM> comprises receiving a response <NUM> from the first UE <NUM>, the response <NUM> indicating that the first UE <NUM> is not available for scheduling of traffic in the part <NUM> of the scheduling gap <NUM> and in response to receiving the response <NUM> from the first UE <NUM>, preventing scheduling of traffic for the first UE <NUM> during the part <NUM> of the scheduling gap <NUM>.

In examples, the terminal node <NUM> is configured to switch between the first and second UEs <NUM>, <NUM> appropriately to transmit the response <NUM> to the network node. For example, the terminal node <NUM> can be configured to switch to the first network between the early paging indication, such as PEI, and subsequent receipt of paging information, such as PDCCH occasions, for the second UE <NUM>.

In some examples, such as some examples where there is ongoing traffic with the first UE <NUM>, method <NUM> comprises detecting no response <NUM> from the first UE <NUM> and in response to not detecting a response <NUM> from the first UE <NUM>, scheduling traffic for the first UE <NUM> during the part <NUM> of the scheduling gap <NUM>.

Accordingly, in some examples where there is ongoing traffic with the first UE <NUM>, the configuration information <NUM> configures the first UE <NUM> to resume radio connected operation during the part <NUM> of the scheduling gap <NUM> if possible and when no response <NUM> indicating that the first UE <NUM> is unavailable is detected, scheduling of traffic for the first UE <NUM> in the part <NUM> of the scheduling gap <NUM> can proceed.

In some examples, from the point of view of the terminal node <NUM> and/or first UE <NUM>, method <NUM> comprises determining that the first UE <NUM> is available for scheduling of traffic during the part <NUM> of the scheduling gap <NUM> and in response to determining that the first UE <NUM> is available for scheduling of traffic during the part <NUM> of the scheduling gap <NUM>, resuming radio connected operation during the part <NUM> of the gap <NUM> without transmitting a response <NUM> on at least one of the at least one uplink grant.

Examples of the disclosure provide technical benefits. For example, examples of the disclosure provide means to prepare efficient and/or proper use of a configured scheduling gap by a network associated with a UE, of a multi-subscription device, in radio connected mode.

Examples provide for a network associated with a UE, of a multi-subscription device, in radio connected mode to prepare for the early return of the UE to scheduling of traffic, prior to the end of a configured scheduling gap.

In examples, the method <NUM> can be performed by any suitable apparatus comprising any suitable means for performing the method <NUM>.

In examples, the method <NUM> can be performed by a network node such as an access node <NUM> or a core node <NUM>.

Method <NUM> comprises enabling scheduling gap usage in relation to a device with multiple subscriptions comprising at least a first subscription configured to enable a first user equipment <NUM> at the device and a second user equipment <NUM> at the device by performing, at least, the blocks illustrated in the example of <FIG>.

At block <NUM>, method <NUM> comprises determining if there is traffic to schedule for the first user equipment <NUM>, in radio connected mode, during a part <NUM> of a configured scheduling gap <NUM> for the first user equipment <NUM> corresponding to a paging occasion <NUM> of the second user equipment <NUM>, the second user equipment <NUM> not in radio connected mode.

At block <NUM>, method <NUM> comprises if it is determined that there is traffic to schedule for the first user equipment <NUM> during a part <NUM> of the scheduling gap <NUM>, transmitting configuration information <NUM> to the first user equipment <NUM> to configure the first user equipment <NUM> to provide a response indicating device availability of the device for the part <NUM> of the scheduling gap <NUM>.

Consequently, <FIG> illustrates a method <NUM> comprising:
enabling scheduling gap usage in relation to a device with multiple subscriptions comprising at least a first subscription configured to enable a first user equipment at the device and a second subscription configured to enable a second user equipment at the device by:.

In examples, the method <NUM> can be performed by a terminal node <NUM>, such as a MUSIM device.

Method <NUM> comprises supporting scheduling gap usage in relation to a device with multiple subscriptions comprising at least a first subscription configured to enable a first user equipment <NUM> at the device and a second subscription configured to enable a second user equipment <NUM> at the device by performing, at least, the blocks illustrated in the example of <FIG>.

At block <NUM>, method <NUM> comprises receiving configuration information <NUM> to configure the first user equipment <NUM>, in radio connected mode, to provide a response indicating device availability of the device for a part <NUM> of a configured scheduling gap <NUM> for the first user equipment <NUM> corresponding to a paging occasion <NUM> of the second user equipment <NUM>, the second user equipment <NUM> not in radio connected mode.

Consequently, <FIG> illustrates a method <NUM> comprising:
supporting scheduling gap usage in relation to a device with multiple subscriptions comprising at least a first subscription configured to enable a first user equipment <NUM> at the device and a second subscription configured to enable a second user equipment <NUM> at the device by:.

<FIG> shows an example of scheduling gap usage at a MUSIM device.

In the example of <FIG> a MUSIM device comprises a first USIM (USIM1) that enables a first UE 110a and a second USIM (USIM2) that enables a second UE 110b.

In the illustrated example, separate lines are presented to indicate actions at UE-<NUM> and UE-<NUM>, although the UEs are enabled at one device.

Also represented in the example of <FIG> is a gNB associated with UE-<NUM> and network <NUM> (NW-<NUM>) and a gNB associated with UE-<NUM> and network <NUM> (NW-<NUM>) which, in the example of <FIG>, is different to NW-<NUM>.

At block <NUM>, UE1 is in RRC_CONNECTED with NW1 corresponding to its first USIM (NW-<NUM>, USIM-<NUM>).

At block <NUM>, UE2 is in RRC_IDLE or RRC_INACTIVE with NW2 corresponding to its other USIM (NW-<NUM>, USIM2).

In the example of <FIG>, NW-<NUM> supports PEI and has given PEI configuration (for example, signal carrying PEI, UE's group, etc.).

At block <NUM> the device internally provides this information to the protocol stack instance corresponding to its connected USIM (USIM-<NUM>) which passes the information to its NW (NW-<NUM>).

This information can be provided to NW-<NUM> at block <NUM> using UE assistance information signaling or as an information element in the UE's request for periodic gap at block <NUM>.

At block <NUM>, NW-<NUM> provides configuration for the periodic gap with the possibility for early return. In examples, this can be considered pre-configuration information <NUM>.

At block <NUM>, this information is internally in the device forwarded to the protocol stack instance corresponding to its idle/inactive USIM (USIM-<NUM>).

If, as indicated at block <NUM>, the NW1 receives data for the UE1 which needs scheduling during the gap, it will transmit a scheduling early indication (SEI) as indicated at block <NUM>.

The SEI can be PDCCH with a configured grant (CG) for UE1 to transmit its response if it can return. The SEI can be considered configuration information <NUM>.

The SEI can optionally include the service/traffic type for UE1 to decide if it wants to return even if the device does not find PEI or use the rest of the gap for other RX operations at UE2.

Case <NUM>: if device does not detect any PEI, it will monitor for SEI at block <NUM> and can use the CG to inform the NW1 about its return or ignore if it decides to continue using the remaining part of the gap, e.g. for measurement.

At block <NUM> UE2 informs UE1 that early return is possible (no PEI) at block <NUM> UE1 informs NW-<NUM> that it can return early.

When the NW received UE's early return at CG (block <NUM>), it can end the gap and proceed with the scheduling of the arrived traffic at block <NUM>.

Case <NUM>: If the device does detect PEI at block <NUM>, it will complete its paging task (block <NUM>) and return when finished at planned gap end.

<FIG> is similar to the example of <FIG>. However, in the example of <FIG>, at block <NUM> there is no traffic to schedule during the gap.

In case there is no traffic for the UE1 during the gap, the NW1 will not transmit SEI.

In this case if the device does not find PEl nor SEI, it can use the remaining gap time to perform other idle/inactive mode operations like RRM measurements. See blocks <NUM> to <NUM>.

The example of <FIG> begins in a similar way to the examples of <FIG> and <FIG>.

However, in the example of <FIG>, at block <NUM> NW1 has already ongoing critical traffic when the gap request arrives from UE1 at block <NUM>.

NW1 will consider the main gap for the device to receive the PEI while expecting a tentative longer gap in case the UE2 has identified paging addressed to it by receiving the PEI signal.

Accordingly, at block <NUM>, NW1 transmits a RRCConnectionReConfiguration message including a CG for PEI indication. This can be considered configuration information <NUM>. As there is ongoing traffic in the example of <FIG> there is no pre-configuration information <NUM>.

If no paging indication is received the gap can be ended and RRC connected operation resumed as indicated at blocks <NUM> and <NUM>.

If UE2 receives the PEI and thereby determines there is a paging addressed to it (block <NUM>), it will inform UE1 (block <NUM>) and UE1 will apply the configured uplink to indicate PEI reception to NW1 to inform UE2 is going to use the full gap as indicated at blocks <NUM> to <NUM>.

Examples of the disclosure provide technical benefits. For example, examples of the disclosure provide for efficient use of a scheduling gap at a multi-subscription device.

<FIG> illustrates an example of a controller <NUM>. The controller <NUM> can be used in an apparatus such as a network node <NUM>, <NUM>, <NUM> such as a mobile terminal or UE and/or a gNB. In examples, controller <NUM> can be considered an apparatus <NUM>.

Implementation of a controller <NUM> may be as controller circuitry. The controller <NUM> may be implemented in hardware alone, have certain aspects in software including firmware alone or can be a combination of hardware and software (including firmware).

As illustrated in <FIG> the controller <NUM> may be implemented using instructions that enable hardware functionality, for example, by using executable instructions of a computer program <NUM> in a general-purpose or special-purpose processor <NUM> that may be stored on a computer readable storage medium (disk, memory etc.) to be executed by such a processor <NUM>.

The memory <NUM> stores a computer program <NUM> comprising computer program instructions (computer program code) that controls the operation of the apparatus when loaded into the processor <NUM>. The computer program instructions, of the computer program <NUM>, provide the logic and routines that enables the apparatus to perform the methods illustrated in <FIG> and/or <NUM> and/or <NUM> and/or <NUM> and/or <NUM> and/or <NUM>. The processor <NUM> by reading the memory <NUM> is able to load and execute the computer program <NUM>.

As illustrated in <FIG>, the computer program <NUM> may arrive at the apparatus via any suitable delivery mechanism <NUM>. The delivery mechanism <NUM> may be, for example, a machine-readable medium, a computer-readable medium, a non-transitory computer-readable storage medium, a computer program product, a memory device, a record medium such as a Compact Disc Read-Only Memory (CD-ROM) or a Digital Versatile Disc (DVD) or a solid-state memory, an article of manufacture that comprises or tangibly embodies the computer program <NUM>. The delivery mechanism may be a signal configured to reliably transfer the computer program <NUM>. The apparatus may propagate or transmit the computer program <NUM> as a computer data signal.

Computer program instructions for causing an apparatus to perform at least the following or for performing at least the following:
enabling scheduling gap usage in relation to a device with multiple subscriptions comprising at least a first subscription configured to enable a first user equipment at the device and a second subscription configured to enable a second user equipment at the device by:.

Computer program instructions for causing an apparatus to perform at least the following or for performing at least the following:
supporting scheduling gap usage in relation to a device with multiple subscriptions comprising at least a first subscription configured to enable a first user equipment at the device and a second subscription configured to enable a second user equipment at the device by:.

The computer program instructions may be comprised in a computer program, a non-transitory computer readable medium, a computer program product, a machine-readable medium.

In examples the memory <NUM> comprises a random-access memory <NUM> and a read only memory <NUM>. In examples the computer program <NUM> can be stored in the read only memory <NUM>. See, for example, <FIG>.

In some examples the memory <NUM> can be split into random access memory <NUM> and read only memory <NUM>.

The blocks illustrated in the <FIG> and/or <NUM> and/or <NUM> and/or <NUM> and/or <NUM> and/or <NUM> may represent steps in a method and/or sections of code in the computer program <NUM>. The illustration of a particular order to the blocks does not necessarily imply that there is a required or preferred order for the blocks and the order and arrangement of the block may be varied. Furthermore, it may be possible for some blocks to be omitted.

Thus, the apparatus can, in examples, comprise means for:
enabling scheduling gap usage in relation to a device with multiple subscriptions comprising at least a first subscription configured to enable a first user equipment at the device and a second subscription configured to enable a second user equipment at the device by:.

Thus, the apparatus can, in examples, comprise means for:
supporting scheduling gap usage in relation to a device with multiple subscriptions comprising at least a first subscription configured to enable a first user equipment at the device and a second subscription configured to enable a second user equipment at the device by:.

In examples, an apparatus can comprise means for performing one or more methods, and/or at least part of one or more methods, as disclosed herein.

In examples, an apparatus can be configured to perform one or more methods, and/or at least part of one or more methods, as disclosed herein.

The above described examples find application as enabling components of: automotive systems; telecommunication systems; electronic systems including consumer electronic products; distributed computing systems; media systems for generating or rendering media content including audio, visual and audio visual content and mixed, mediated, virtual and/or augmented reality; personal systems including personal health systems or personal fitness systems; navigation systems; user interfaces also known as human machine interfaces; networks including cellular, non-cellular, and optical networks; ad-hoc networks; the internet; the internet of things; virtualized networks; and related software and services.

Although examples have been described in the preceding paragraphs with reference to various examples, it should be appreciated that modifications to the examples given can be made without departing from the scope of the of the invention which is only defined by the appended claims.

The term 'a' or 'the' is used in this document with an inclusive not an exclusive meaning. That is any reference to X comprising a/the Y indicates that X may comprise only one Y or may comprise more than one Y unless the context clearly indicates the contrary. If it is intended to use 'a' or 'the' with an exclusive meaning then it will be made clear in the context. In some circumstances the use of 'at least one' or 'one or more' may be used to emphasis an inclusive meaning but the absence of these terms should not be taken to infer any exclusive meaning.

The presence of a feature (or combination of features) in a claim is a reference to that feature or (combination of features) itself and also to features that achieve substantially the same technical effect (equivalent features). The equivalent features include, for example, features that are variants and achieve substantially the same result in substantially the same way. The equivalent features include, for example, features that perform substantially the same function, in substantially the same way to achieve substantially the same result.

Claim 1:
An apparatus comprising means for:
enabling scheduling gap usage in relation to a device with multiple subscriptions comprising at least a first subscription configured to enable a first user equipment at the device and a second subscription configured to enable a second user equipment at the device by:
determining if there is traffic to schedule for the first user equipment, in radio connected mode, during a part of a configured scheduling gap for the first user equipment corresponding to a paging occasion of the second user equipment, the second user equipment not in radio connected mode;
the means being characterised by being configured for:
if it is determined that there is traffic to schedule for the first user equipment during a part of the scheduling gap, transmitting configuration information to the first user equipment to configure the first user equipment to provide a response indicating device availability of the device for the part of the scheduling gap; and
monitoring for a response from the first user equipment.