WO2022195161A1

WO2022195161A1 - Configurations for gaps in device having multiple user subscription identities

Info

Publication number: WO2022195161A1
Application number: PCT/FI2022/050153
Authority: WO
Inventors: Srinivasan Selvaganapathy; Aby KANNEATH ABRAHAM; Faranaz SABOURI-SICHANI
Original assignee: Nokia Technologies Oy
Priority date: 2021-03-15
Filing date: 2022-03-10
Publication date: 2022-09-22
Also published as: EP4309420A1; CN117322054A

Abstract

When multiple user subscriptions are supported, an apparatus is configured to use, for a first subscription entity, which is in an active state, during a multiple user subscription gap for one or more inactive or idle state subscription entities, a gap configuration comprising one or more parameters defining information for processing one or more events relating to the first subscription entity which remains in the active state during the gap.

Description

TITLE

CONFIGURATIONS FOR GAPS IN DEVICE HAVING MULTIPLE USER SUBSCRIPTION

IDENTITIES

TECHNICAL FIELD Various example embodiments relate to wireless communications.

BACKGROUND

Wireless devices supporting multiple user subscription identities per a device are becoming more and more popular thanks to their flexibility relating to service options and other features. While one of the user subscription identity en- tit_les is in an active state, a subscription identity entity in an inactive or idle state may need to shortly monitor its network or shortly communicate with its network. To enable this, a scheduled gap may be requested. During the gap the network con nection for the subscription identity entity that is in the active state is not released even though the gap is used for the subscription identity entity that is in the inac- tive or idle state.

BRIEF DESCRIPTION

The scope of protection sought for various embodiments is set out by the independent claims. The embodiments, examples and features, if any, de- scribed in this specification that do not fall under the scope of the independent claims are to be interpreted as examples useful for understanding various embod- iments falling under the scope of the independent claims.

An aspect provides an apparatus comprising at least one processor; and at least one memory including computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the apparatus at least to perform: supporting multiple user subscriptions; sending a multiple user subscription gap request to an access node using a first subscription entity which is in an active state; receiving in a radio resource reconfiguration mes- sage at least one gap configuration to be used during one or more multiple user subscription gaps, a gap configuration comprising one or more parameters defin- ing information for processing one or more events relating to the first subscription which remains in the active state during the gap; and using one of the at least one gap configuration during multiple user subscription gaps. In an embodiment, the at least one memory and computer program code are configured to, with the at least one processor, cause the apparatus further to send the multiple user subscription gap request in response to receiving from the access node a configured grant to the first subscription entity.

An aspect provides an apparatus comprising means for performing: supporting multiple user subscriptions; sending a multiple user subscription gap request to an access node using a first subscription entity which is in an active state; receiving in a radio resource reconfiguration message at least one gap con- figuration to be used during one or more multiple user subscription gap, a gap con- figuration comprising one or more parameters defining information for processing one or more events relating to the first subscription which remains in the active state during the gap; and using one of the at least one gap configuration during multiple user subscription gaps.

In an embodiment, the apparatus further comprises means for perform- ing receiving from the access node a configured grant to the first subscription en- tity, wherein the means for performing sending the multiple user subscription gap request are configured to perform the sending in response to receiving the config- ured.

An aspect provides an apparatus comprising at least one processor; and at least one memory including computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the apparatus at least to perform: providing access node functionalities; determin- ing, when a multiple user subscription gap request has been received from a served apparatus, at least one gap configuration to be used during one or more multiple user subscription gaps, a gap configuration comprising one or more parameters defining information for processing one or more events relating to the served ap- paratus which remains in the active state during a gap; sending in a radio resource reconfiguration message the gap configuration; and using the at least one gap con- figuration for the served apparatus.

An aspect provides an apparatus comprising means for performing: providing access node functionalities; determining, when a multiple user subscrip- tion gap request has been received from a served apparatus, at least one gap con- figuration to be used during one or more multiple user subscription gaps, a gap configuration comprising one or more parameters defining information for pro- cessing one or more events relating to the served apparatus which remains in the active state during the gap; sending in a radio resource reconfiguration message the at least one gap configuration; and using the at least one gap configuration for the served apparatus.

In embodiments, the one or more parameters in a gap configuration configures uplink data transmissions by setting parameters providing enhanced transmission and disabling reception feedback.

In embodiments, the reception feedback is disabled by disabling a hy- brid automatic repeat request operation.

In embodiments, the parameters providing the enhanced transmission relate to one or more of a modulation coding scheme, a transport block size, a pre- coding, or a number of layers.

In embodiments, the one or more parameters in a gap configuration configures downlink data transmissions by setting an offset to semi-persistent scheduling of configured grants in downlink.

In embodiments, the one or more parameters in a gap configuration configures one or more timer actions.

In embodiments, the one or more timer actions include an action per a timer class.

In embodiments, a timer action is one of the following: suspend, stop and restart after the gap with initial value, stop and restart after the gap with mod- ified value, continue running during the gap starting with a current value, continue running during the gap starting with a modified value, or if one or more conditions are fulfilled, continue running during the gap starting with a modified value, other- wise continue running with the current value.

In embodiments, default timer actions are used when a gap configura- tion is silent on the timer actions.

In embodiments, a default timer action for timers belonging to a discon- tinuous timer class is to continue running if the apparatus starts with on-duration timer after the gap.

According to an aspect there is provided a method comprising: using, by an apparatus, for a first subscription entity, which is in an active state, during a multiple user subscription gap for one or more inactive or idle state subscription entities, a gap configuration comprising one or more parameters defining infor- mation for processing one or more events relating to the first subscription entity which remains in the active state during the gap. According to an aspect there is provided a computer-readable medium comprising program instructions, which, when run by an apparatus, causes the ap- paratus to to carry out at least one of a first process or a second process, wherein the first process comprises at least: supporting multiple user subscriptions; send- ing a multiple user subscription gap request to an access node using a first sub- scription entity which is in an active state; using, in response to receiving in a radio resource reconfiguration message at least one gap configuration to be used during one or more multiple user subscription gaps, a gap configuration comprising one or more parameters defining information for processing one or more events relat- ing to the first subscription which remains in the active state during the gap, one of the at least one gap configuration received during multiple user subscription gaps, wherein the second process comprises at least: providing access node functionali- ties; determining, when a multiple user subscription gap request has been received from a served apparatus, at least one gap configuration to be used during one or more multiple user subscription gap, a gap configuration comprising one or more parameters defining information for processing one or more events relating to the served apparatus which remains in the active state during the gap; sending in a radio resource reconfiguration message the at least one gap configuration; and us- ing the at least one gap configuration for the served apparatus.

According to an aspect there is provided a non-transitory computer- readable medium comprising program instructions, which, when run by an appa- ratus, causes the apparatus to to carry out at least one of a first process or a second process, wherein the first process comprises at least: supporting multiple user sub- scriptions; sending a multiple user subscription gap request to an access node us- ing a first subscription entity which is in an active state; using, in response to re- ceiving in a radio resource reconfiguration message at least one gap configuration to be used during one or more multiple user subscription gaps, a gap configuration comprising one or more parameters defining information for processing one or more events relating to the first subscription which remains in the active state dur- ing the gap, one of the at least one gap configuration received during multiple user subscription gaps, wherein the second process comprises at least: providing access node functionalities; determining, when a multiple user subscription gap request has been received from a served apparatus, at least one gap configuration to be used during one or more multiple user subscription gap, a gap configuration com- prising one or more parameters defining information for processing one or more events relating to the served apparatus which remains in the active state during the gap; sending in a radio resource reconfiguration message the at least one gap configuration; and using the at least one gap configuration for the served appa- ratus.

According to an aspect there is provided a computer program compris- ing instructions which, when the program is executed by an apparatus, cause the apparatus to carry out at least one of a first process or a second process, wherein the first process comprises at least: supporting multiple user subscriptions; send- ing a multiple user subscription gap request to an access node using a first sub- scription entity which is in an active state; using, in response to receiving in a radio resource reconfiguration message at least one gap configuration to be used during one or more multiple user subscription gap, a gap configuration comprising one or more parameters defining information for processing one or more events relating to the first subscription which remains in the active state during the gap, one of the at least one gap configuration received during multiple user subscription gaps, wherein the second process comprises at least: providing access node functionali- ties; determining, when a multiple user subscription gap request has been received from a served apparatus, at least one gap configuration to be used during one or more multiple user subscription gap, a gap configuration comprising one or more parameters defining information for processing one or more events relating to the served apparatus which remains in the active state during the gap; sending in a radio resource reconfiguration message the at least one gap configuration; and us- ing the at least one gap configuration for the served apparatus.

BRIEF DESCRIPTION OF DRAWINGS

Embodiments are described below, by way of example only, with refer- ence to the accompanying drawings, in which

Figure 1 illustrates an exemplified wireless communication system;

Figure 2 illustrates an example of information exchange;

Figures 3 to 7 illustrate example functionalities; and

Figures 8 and 9 are schematic block diagrams.

DETAILED DESCRIPTION OF SOME EMBODIMENTS

The following embodiments are examples. Although the specification may refer to "an", "one", or "some" embodiment(s) in several locations, this does not necessarily mean that each such reference is to the same embodiment(s), or that the feature only applies to a single embodiment. Single features of different embodiments may also be combined to provide other embodiments. Furthermore, words "comprising" and "including" should be understood as not limiting the de- scribed embodiments to consist of only those features that have been mentioned and such embodiments may contain also features/structures that have not been specifically mentioned. Further, although terms including ordinal numbers, such as "first", "second", etc., may be used for describing various elements, the structural elements are not restricted by the terms. The terms are used merely for the pur- pose of distinguishing an element from other elements. For example, a first element could be termed a second element, and similarly, a second element could be also termed a first element without departing from the scope of the present disclosure.

Embodiments and examples described herein may be implemented in any communications system comprising wireless connection (s). In the following, different exemplifying embodiments will be described using, as an example of an access architecture to which the embodiments may be applied, a radio access ar- chitecture based on new radio (NR, 5G) or long term evolution advanced (LTE Ad- vanced, LTE-A), without restricting the embodiments to such an architecture, how- ever. It is obvious for a person skilled in the art that the embodiments may also be applied to other kinds of communications networks having suitable means by ad- justing parameters and procedures appropriately. Some examples of other options for suitable systems are the universal mobile telecommunications system (UMTS) radio access network (UTRAN or E-UTRAN), long term evolution (LTE, the substan- tially same as E-UTRA), beyond 5G, wireless local area network (WLAN or WiFi), worldwide interoperability for microwave access (WiMAX), Bluetooth®, personal communications services (PCS), ZigBee®, wideband code division multiple access (WCDMA), systems using ultra-wideband (UWB) technology, sensor networks, mo- bile ad-hoc networks (MANETs) and Internet Protocol multimedia subsystems (IMS) or any combination thereof.

Figure 1 depicts examples of simplified system architectures showing some elements and functional entities, all being logical units, whose implementa- tion may differ from what is shown. The connections shown in Figure 1 are logical connections; the actual physical connections may be different. It is apparent to a person skilled in the art that the system typically comprises also other functions and structures than those shown in Figure 1.

The embodiments are not, however, restricted to the system given as an example but a person skilled in the art may apply the solution to other communi- cation systems provided with necessary properties. The example of Figure 1 shows a part of an exemplifying radio access network.

Figure 1 shows user devices 101 and 101’ configured to be in a wireless connection on one or more communication channels in a cell with an access node (such as (e/g) NodeB) 102 providing the cell. The physical link from a user device to a (e/g)NodeB is called uplink or reverse link and the physical link from the (e/g)NodeB to the user device is called downlink or forward link. It should be ap- preciated that (e/g)NodeBs or their functionalities may be implemented by using any node, host, server or access point (AP) etc. entity suitable for such a usage.

A communications system 100 typically comprises more than one (e/g) NodeB in which case the (e/g)NodeBs may also be configured to communicate with one another over links, wired or wireless, designed for the purpose. These links may be used for signalling purposes. The (e/g) NodeB is a computing device configured to control the radio resources of communication system it is coupled to. The NodeB may also be referred to as a base station, an access point or any other type of interfacing device including a relay station capable of operating in a wire- less environment. The (e/g)NodeB includes or is coupled to transceivers. From the transceivers of the (e/g) NodeB, a connection is provided to an antenna unit that establishes bi-directional radio links to user devices. The antenna unit may com- prise a plurality of antennas or antenna elements. The (e/g)NodeB is further con- nected to core network 105 (CN or next generation core NGC). Depending on the system, the counterpart on the CN side can be a serving gateway (S-GW, routing and forwarding user data packets), packet data network gateway (P-GW), for providing connectivity of user devices (UEs) to external packet data networks, or mobile management entity (MME), etc.

The user device (also called UE, user equipment, user terminal, terminal device, etc.) illustrates one type of an apparatus to which resources on the air in- terface are allocated and assigned, and thus any feature described herein with a user device may be implemented with a corresponding apparatus, such as a relay node. An example of such a relay node is a layer 3 relay (self-backhauling relay) towards the base station.

The user device typically refers to a portable computing device that in- cludes wireless mobile communication devices operating with or without a sub- scriber identification module (SIM), including, but not limited to, the following types of wireless devices: a mobile station (mobile phone), smartphone, personal digital assistant (PDA), handset, device using a wireless modem (alarm or meas- urement device, etc.), laptop and/or touch screen computer, tablet, game console, notebook, and multimedia device. It should be appreciated that a user device may also be a nearly exclusive uplink only device, of which an example is a camera or video camera loading images or video clips to a network. A user device may also be a device having capability to operate in Internet of Things (loT) network which is a scenario in which objects are provided with the ability to transfer data over a network without requiring human-to-human or human-to-computer interaction. The user device may also utilise cloud. In some applications, a user device may comprise a small portable device with radio parts (such as a watch, earphones or eyeglasses) and the computation is carried out in the cloud. The user device (or in some embodiments a relay node, such as a mobile termination (MT) part of the integrated access and backhaul (1AB) Node), is configured to perform one or more of user equipment functionalities. The user device may also be called a subscriber unit, mobile station, remote terminal, access terminal, user terminal or user equip- ment (UE) just to mention but a few names or apparatuses.

Various techniques described herein may also be applied to a cyber- physical system (CPS) (a system of collaborating computational elements control- ling physical entities). CPS may enable the implementation and exploitation of mas- sive amounts of interconnected 1CT devices (sensors, actuators, processors micro- controllers, etc.) embedded in physical objects at different locations. Mobile cyber physical systems, in which the physical system in question has inherent mobility, are a subcategory of cyber-physical systems. Examples of mobile physical systems include mobile robotics and electronics transported by humans or animals.

Additionally, although the apparatuses have been depicted as single en- tities, different units, processors and/or memory units (not all shown in Figure 1) may be implemented.

5G enables using, many more base stations or nodes or corresponding network devices than the LTE (a so-called small cell concept), including macro sites operating in co-operation with smaller stations and employing a variety of radio technologies depending on service needs, use cases and/or spectrum available. 5G mobile communications supports a wide range of use cases and related applica- tions including video streaming, augmented reality, different ways of data sharing and various forms of machine type applications (such as (massive) machine-type communications (mMTC), including vehicular safety, different sensors and real- time control. 5G is expected to have multiple radio interfaces, namely below 6GHz, cmWave and mmWave, and also being integradable with existing legacy radio ac- cess technologies, such as the LTE. Integration with the LTE may be implemented, at least in the early phase, as a system, where macro coverage is provided by the LTE and 5G radio interface access comes from small cells by aggregation to the LTE. In other words, 5G is planned to support both inter-RAT operability (such as LTE- 5G) and inter-RI operability (inter-radio interface operability, such as below 6GHz - cmWave, below 6GHz - cmWave - mmWave). One of the concepts considered to be used in 5G networks is network slicing in which multiple independent and ded- icated virtual sub-networks (network instances) may be created within the sub- stantially same infrastructure to run services that have different requirements on latency, reliability, throughput and mobility.

The current architecture in LTE networks is fully distributed in the ra- dio and fully centralized in the core network. The low latency applications and ser- vices in 5G require to bring the content close to the radio which leads to local break out and multi-access edge computing (MEC). 5G enables analytics and knowledge generation to occur at the source of the data. This approach requires leveraging resources that may not be continuously connected to a network such as laptops, smartphones, tablets and sensors. MEC provides a distributed computing environ- ment for application and service hosting. It also has the ability to store and process content in close proximity to cellular subscribers for faster response time. Edge computing covers a wide range of technologies such as wireless sensor networks, mobile data acquisition, mobile signature analysis, cooperative distributed peer- to-peer ad hoc networking and processing also classifiable as local cloud/fog com- puting and grid/mesh computing, dew computing, mobile edge computing, cloud- let, distributed data storage and retrieval, autonomic self-healing networks, remote cloud services, augmented and virtual reality, data caching, Internet of Things (massive connectivity and/or latency critical), critical communications (autono- mous vehicles, traffic safety, real-time analytics, time-critical control, healthcare applications).

The communication system is also able to communicate with other net- works, such as a public switched telephone network or the Internet 106, or utilise services provided by them. The communication network may also be able to sup- port the usage of cloud services, for example at least part of core network opera- tions may be carried out as a cloud service (this is depicted in Figure 1 by "cloud" 107). The communication system may also comprise a central control entity, or a like, providing facilities for networks of different operators to cooperate for exam- ple in spectrum sharing.

Edge cloud may be brought into radio access network (RAN) by utilizing network function virtualization (NVF) and software defined networking (SDN). Us- ing edge cloud may mean access node operations to be carried out, at least partly, in a server, host or node operationally coupled to a remote radio head or base sta- tion comprising radio parts. It is also possible that node operations will be distrib- uted among a plurality of servers, nodes or hosts. Application of cloudRAN archi- tecture enables RAN real time functions being carried out at the RAN side (in a dis- tributed unit, DU 102) and non-real time functions being carried out in a central- ized manner (in a centralized unit, CU 104).

It should also be understood that the distribution of labour between core network operations and base station operations may differ from that of the LTE or even be non-existent. Some other technology advancements probably to be used are Big Data and all-IP, which may change the way networks are being con- structed and managed. 5G (or new radio, NR) networks are being designed to sup- port multiple hierarchies, where MEC servers can be placed between the core and the base station or nodeB (gNB). It should be appreciated that MEC can be applied in 4G networks as well.

5G may also utilize satellite communication to enhance or complement the coverage of 5G service, for example by providing backhauling. Possible use cases are providing service continuity for machine-to-machine (M2M) or Internet of Things (IoT) devices or for passengers on board of vehicles, or ensuring service availability for critical communications, and future railway/maritime /aeronautical communications. Satellite communication may utilise geostationary earth orbit (GEO) satellite systems, but also low earth orbit (LEO) satellite systems, in partic- ular mega-constellations (systems in which hundreds of (nano) satellites are de- ployed). At least one satellite 103 in the mega-constellation may cover several sat- ellite-enabled network entities that create on-ground cells. The on-ground cells may be created through an on-ground relay node 102 or by a gNB located on- ground or in a satellite.

It is obvious for a person skilled in the art that the depicted system is only an example of a part of a radio access system and in practice, the system may comprise a plurality of (e/g)NodeBs, the user device may have an access to a plu- rality of radio cells and the system may comprise also other apparatuses, such as relay nodes, for example distributed unit (DU) parts of one or more IAB nodes, or other network elements, etc. At least one of the (e/g)NodeBs or may be a Home(e/g)nodeB. Additionally, in a geographical area of a radio communication system a plurality of different kinds of radio cells as well as a plurality of radio cells may be provided. Radio cells may be macro cells (or umbrella cells) which are large cells, usually having a diameter of up to tens of kilometers, or smaller cells such as micro-, femto- or picocells. The (e/g)NodeBs of Figure 1 may provide any kind of these cells. A cellular radio system may be implemented as a multilayer network including several kinds of cells. Typically, in multilayer networks, one access node provides one kind of a cell or cells, and thus a plurality of (e/g)NodeBs may be needed to provide such a network structure.

For fulfilling the need for improving the deployment and performance of communication systems, the concept of "plug-and-play" (e/g)NodeBs has been introduced. Typically, a network which is able to use "plug-and-play" (e/g)Node Bs, includes, in addition to Home (e/g)NodeBs (H(e/g)nodeBs), a home node B gate- way, or HNB-GW (not shown in Figure 1). A HNB Gateway (HNB-GW), which is typ- ically installed within an operator’s network may aggregate traffic from a large number of HNBs back to a core network.

Subscription identities are used to access wireless network services. For that purpose, a user device may comprise one or more subscriber identity mod- ules, a module per a subscription identity, for example. In 5G, a universal sub- scriber identity module (USIM) is a software application residing in a hardware part, called a universal integrated circuit card. The universal integrated circuit card may contain multiple universal subscriber identity modules, thereby supporting multiple subscription identities. For example, there may be subscription identities for different generations of mobile wireless networks, including predecessors of 5G, and future networks beyond 5G, and/or multiple subscription identities for the substantially same generation wireless networks. Further, subscription identities may be from different network operators and/or two or more of them may be from the substantially same network operator. A user device configured to support mul- tiple subscription identities, called in 5G a multi-USIM device, or a MUSIM device, may use common radio network operator. A user device configured to support mul- tiple subscription identities, may be implemented to allow one, or some, of corre- sponding multiple subscription identity entities to be in an active state, while the other/others is/are in an inactive state or in an idle state. For example, the user device implementation may be based on use of common radio and baseband com- ponents shared among the multiple subscription identity entities. A user device configured to support multiple subscription identities is called in 5 G a multi-USIM device, or an MUSIM-device.

Figure 2 illustrates an example of information exchange between a user device, denoted by UE in Figure 2, and an access node, denoted by gNB in Figure 2, providing radio access to a network to user devices having subscriptions, identified by subscription identities, that allow access to the network.

The user device UE has multiple subscription identities and corre- sponding entities, a subscription identity entity being denoted by US1M in Figure 2, and called below a subscription entity. Further, there are several timers, examples of which are given below with Figure 7, configured in the user device to run for an subscriber entity in the active state.

In the example of Figure 2 it is assumed that a first subscription entity is in an active state, having a first connection via the access node gNB to a network corresponding with the first subscription entity, and one or more timers for the connection may be running. In other words, the user device, or its first subscription entity, is served by the access node. For the clarity of description, in the examples one gap configuration is used as an example. However, two or more gap configura- tions may be determined for the user device (for the first subscription entity).

Referring to Figure 2, the user device request a scheduled gap from the first connection by sending message 2-1 over the first connection to the access node. The gap is intended for one or more inactive or idle state subscription iden- tities (identity entities) to perform a procedure/activity that is short enough to al- low the first subscription entity to stay in the active state during the gap without leaving the first connection. Message 2-1 may be a MUS1M Gap Request. The sched- uled gap may be requested to be a periodic gap, for example for fixed time activities (procedures) for the other subscriber identities, or a non-periodic gap for non- fixed time activities (procedures). A non-limiting list of examples of the fixed time activities for an idle subscription entity include paging related procedures (moni- toring for paging downlink control information, receiving a paging message, re- sponding to the paging message, etc.) and receiving updated system information blocks. A non-limiting list of examples of the non-fixed time, flexible activities in- clude performing radio resource management measurement for cell reselection, performing mobile originated signaling (for registration, for tracking area updates, for routing area updates, for sending busy indication, etc.), and receiving an on- demand system information block. When the access node gNB receives the message 2-1, the access node gNB determines, in the illustrated example, in block 2-2 a gap configuration for the first subscription entity to be used during one or more gaps. (In other examples, two or more gap configurations may be determined. In other words, at least one gap configuration is determined in block 2-2). More precisely, at least one or more parameters defining information for processing (e.g., how to process) one or more events relating to the first subscription which remains in the active state during the gap are determined in block 2-2. By means of the gap configuration it is possible to address issues relating to possible configured grants for uplink and/or downlink transmissions to/from the first subscription that may occur during the gap and/or to timers configured to control functionality in the active state. For example, a run- ning timer expiring during a gap may result in a false evaluation, for example to detection of a radio link failure.

The gap configuration may configure uplink data transmissions during the gap to use enhanced or more robust transmission and disabling reception feed- back. The more robust transmission allows disabling the reception feedback. This addresses an issue that when a scheduled gap collides in time with a reception feedback of a transmission transmitted using configured grant to uplink, the feed- back, like acknowledgement, cannot be received during the gap. A more detailed example is described with Figure 4.

The gap configuration may configure an offset to downlink data trans- mission for initial feedback to the user device (first subscription entity), which are scheduled with configured grant to downlink. By using the offset, it is also ensured that the feedback is received since it is not transmitted during the gap. A more de- tailed example is described with Figure 5.

The gap configuration may configure the user device (first subscription entity) to handle possible various timers during the gap. For example, actions may be given for timers, for example per a timer class, as will be described in more detail with Figures 6 and 7.

The determined gap configuration is then sent to the user device (first subscription entity) in message 2-3. Message 2-3 may be a radio resource control (RRC) reconfiguration message, which may include, as information elements, for gap configuration configuring uplink configured grants operation during a gap, downlink configured grants operation during the gap and timers during the gap, for example following: MusimGapConfigParams { rrc-ConfiguredUplinkGrantParamsDuringGap{ precodingAndNumberOfLayers INTEGER (0..63), mcsAndTBS INTEGER (0..31), disableHARQ BOOL

}

Sps-offset-afterGap INTEGER (0..63)

} timerHandlingDuringGaps Sequence of TimerClass{ TimerClass choice{prohibitTimer, Inactivity Timer, FailureDetectionan- dRecoveryTimer,DrxTimer,periodicBSRTimer etc.}

TimerActionDuringGap { run, pause, restart }

TimerOffsetDuringGap INTEGER (0..63]

RestartTimerOffsetAfterGap INTEGER (0..63) }

}

In the above example, the more robust uplink transmission is config- ured by setting values for parameters defining precoding, a number of layers, a modulation coding scheme (MCS), a transport block size (TBS], and by disabling hybrid automatic repeat request (HARQ). For example, in the new radio, the user device monitors after transmitting data as scheduled by a configured grant, a new data indicator (NDI) bit in the physical downlink control channel(PDCCH) (The new data indicator bit set as one to indicates HARQ NACK (negative acknowledge- ment), i.e. that a transmission failed. When the gap configuration comprises "disa- bleHARQ =true", the user device is not expecting such transmission after transmit- ting the data. Even though not illustrated, other parameters, such as number of rep- etitions and/or redundancy version, may be configured in the gap configuration to have a different value for the more robust uplink transmission. Further, for down- link transmission an offset specifying a number of slots after the gap is configured, and different timer handling ways per a timer class is configured. It should be ap- preciated that message 2-3 may comprise one or two of the sets, or any of the sets may be sent in a separate message.

For example, message 2-3 may configure mere uplink configured grant operations during one or more gaps, and contain following information elements: MusimGapConfigParams { rrc-ConfiguredUplinkGrantParamsDuringGap{ precodingAndNumberOfLayers INTEGER (0..63), mcsAndTBS INTEGER (0..31), disableHARQ BOOL

}

Correspondingly, message 2-3 may configure mere downlink config- ured grant operations during one or more gaps, and contain following information elements:

MusimGapConfigParams {

Sps-offset-afterGap INTEGER (0..63)

}

Message 2-3 may also configure mere timers, i.e. one or more timers, and contain following information elements:

MusimGapConfigParams { timerHandlingDuringGaps Sequence of TimerClass{

TimerClass choice{prohibitTimer, Inactivity Timer, FailureDetectionan- dRecoveryTimer,DrxTimer,periodicBSRTimer etc.}

TimerActionDuringGap { run, pause, restart }

TimerOffsetDuringGap INTEGER (0..63)

RestartTimerOffsetAfterGap INTEGER (0..63)

}

In another timer related gap configuration example, the access node gNB may have determined in point 2-2 to configure timers in general to continue running during the gap with existing timer values with one or more exception. For example, message 2-3 may contain for the gap configuration following timer con- figuration for timers belonging to a prohibit timer class to run with existing values, except for a timer called sr-ProhibitTimer, which is provided with an offset to the timer value. The information elements in message 2-3 may be: timerHandlingDuringGaps Sequence of TimerClass}

TimerClass {prohibitTimer} {

TimerAction {run}

} sr-ProhibitTimer {

TimerOffsetDuringGap 60

}

It should be appreciated that the above are mere examples of possible gap configurations, without limiting the gap configurations to the examples. For example, the gap configuration may also comprise information defining when a gap starts, duration of the gap and periodicity of the gaps.

After receiving message 2-3, the user device (first subscription entity] uses (block 2-4} the gap configuration during one or more gaps, depending on whether the request (message 2-1} scheduled periodic gaps or one gap. Corre- spondingly, the access node uses (block 2-5} the gap configuration during the one or more gaps.

Below different functionalities are described assuming, for the sake of clarity of description, that scheduled gaps are periodic gaps, and that the function- ality is performed by a user device as long as a subscription entity remains in an active state, and no updates to configurations are received. It is a straightforward solution for one skilled in the art to implement the solutions to one gap and/or performed by an access node (to operate in a synchronous manner with the user device} and howto update configurations.

In the example illustrated in Figure 3, it is assumed that the user device has received (block 300} a configured grant configuration for uplink and/or down- link transmissions and a gap configuration. When the user device detects that a transmission occasion according to the configured grant will occur (block 301: yes} with data to be transmitted or scheduled to be received, it is checked in block 302, whether the transmission occasion is during a scheduled gap. In other words, it is checked whether the transmission occasion is within the gap or collides with the gap. If the transmission occasion is during the scheduled gap (block 302: yes), the gap configuration is used in block 303 for the transmission. Then the pro- cess returns to block 301 to monitor when the next transmission occasion occurs. If the transmission occasion is not during the scheduled gap (block 302: no), the configured grant configuration is used in block 304 for the transmission. Then the process returns to block 301 to monitor when the next transmission occasion oc- curs.

Figure 4 illustrates a more detailed example relating to uplink config- ured grant operations in 5G environment.

Referring to Figure 4, when the user device (a subscription entity in an active state) receives in block 401 a radio resource control (RRC) reconfiguration message with an uplink configured grant (UL CG) configuration, sending a gap re- quest for multiple subscription entities (MUSIM gap request) is caused in step 402. A response to the request is received in block 403, the response being a radio re- source control (RRC) reconfiguration message with uplink (UL) gap configuration, i.e. gap configuration for uplink. Examples of such a gap configuration are given above with Figure 2. The gap configuration configures an enhanced or a more ro- bust configured grant to avoid a need for hybrid automatic repeat request, i.e. feed- back on uplink transmission, during gaps to mitigate a collision of a gap with an uplink configured grant transmission where the gap collides with reception of feed- back (ack or nack) for the uplink transmission. The reason is that during the gap uplink transmission from the subscription entity in the active state may take place but since during the gap a downlink path (reception path) is not available for the subscription entity in the active state since it is reserved for one or more subscrip- tion entities in the idle or inactive state.

When a scheduled transmission (tx) occasion, i.e. a scheduled uplink transmission according to the uplink configured grant, with data to be transmitted is detected in block 404, it is checked in block 405, whether it collides with a gap. In other words, it is checked, whether feedback (downlink transmission) on the uplink transmission collides with the gap, when the gap is for downlink infor- mation.

If the scheduled transmission occasion collides with the gap (block 405: yes), the data is transmitted in block 406 using the gap configuration, and the hy- brid automatic repeat request is disabled in block 406 for this data transmission. Then the process proceeds to block 404 to wait the next scheduled transmission to be detected. If the scheduled transmission occasion does not collide with the gap (block 405: no), the data is transmitted in block 407 using the configured grant (CG) configuration with the hybrid automatic repeat request. Then the process pro- ceeds to block 404 to wait the next scheduled transmission to be detected.

Thanks to use of the gap configuration, the user device avoids resending the uplink data mere because no feedback was received because of the feedback colliding with the gap. (Correspondingly, the access node does not in vain try to send the feedback.)

Figure 5 illustrates a more detailed example relating to downlink con- figured grant operations in 5G environment.

Referring to Figure 5, when the user device (a subscription entity in an active state) receives in block 501 a radio resource control (RRC) reconfiguration message with a downlink configured grant (DL CG) configuration, sending a gap request for multiple subscription entities (MUS1M gap request) is caused in step 502. The downlink configured grant configuration may configure semi persistent scheduling (SPS) in downlink, the configuration defining the periodicity of down- link transmissions, i.e. reception occasions in view of the user device, while a phys- ical downlink control channel targeted (addressed) to the subscription entity in the active state may activate or deactivate the configured downlink transmission. A re- sponse to the request is received in block 503, the response being a radio resource control (RRC) reconfiguration message with an offset to the semi persistent sched- uling, the offset defining the number of slots after the end of the gap, the number of slots defining where the next downlink transmission in a physical downlink shared channel is. In other words, the offset configures a new location for the downlink data. The reason is that during the gap the downlink path (reception path) is not available for the subscription entity in the active state since it is reserved for one or more subscription entities in the idle or inactive state.

When a scheduled reception occasion, i.e. a scheduled assignment for downlink transmission according to the semi persistent scheduling for downlink (DL) configured grant is detected in block 504, it is checked in block 505, whether it is during the gap. In other words, it is checked, whether downlink transmission collides with the gap, when the gap is for downlink information.

If the scheduled downlink assignment is during the gap (block 505: yes), the physical downlink shared channel (PDSCH) is received in block 506 using the gap configuration, by receiving downlink based on the end of the gap and the offset (SPS offset). Then the process proceeds to block 504 to wait the next scheduled occurrence of downlink assignment to be detected.

If the scheduled downlink assignment is not during the gap (block 505: no), the physical downlink shared channel (PDSCH) is received in block 507 as scheduled in the semi persistent scheduling (SPS). Then the process proceeds to block 504 to wait the next scheduled transmission to be detected.

Thanks to use of the gap configuration, a collision of downlink data and the gap is avoided and the downlink data can be transmitted and received earlier than would be the case if the configuration received in block 501 would be used.

The principles disclosed above with Figure 5 may be used for uplink gaps, that are used for example for responding to a paging message. In other words, an offset, similar to the SPS offset, may be used for uplink.

Figures 6 and 7 illustrate different examples of timer operations that are configured to take into account gaps. Figure 6 illustrates an example in which there exists default timer actions to be used during gaps, and Figure 7 illustrates an example how the timer operations may be implemented during a gap.

Depending on an implementation, one or more or all timers may be clas- sified to a timer class. For example, a timer may be classified to one of the following classes: a prohibition timer, an inactivity timer, a failure detection and recovery timer, a discontinuous reception timer, and a buffer status timer.

In the new radio, timers that can be classified to be a prohibition timer include, using the terminology in the new radio, include following timers: sr-Pro- hibitTimer, logicalChannelSR-DelayTimerApplied, bitRateQueryProhibitTimer, phr-PeriodicTimer, delayBudgetReportingProhibitTimer, overheatinglndica- tionProhibitTimer, drx-PreferenceProhibitTimer, maxBW-PreferencePro- hibitTimer, maxCC-PreferenceProhibitTimer, maxMIMO-LayerPreferencePro- hibitTimer, minSchedulingOffsetPreferenceProhibitTimer; ReleasePreferencePro- hibitTimer; onDemandSIB-RequestProhibitTimer-rl6.

Correspondingly, in the new radio, timers that can be classified to be an inactivity timer include, using the terminology in the new radio: bwp-Inactivity- Timer, and datalnactivityTimer.

In the new radio, timers that can be classified to be a failure detection and recovery timer, using the terminology in the new radio, include following tim- ers: bt-FailureDetectionTimer, and beamFailureRecoveryTimer.

It should be appreciated that the above classes and lists are only exem- plary and any other classification may be used. Referring to Figure 6, when the gap configurations are received (block 601), for example in block 403 or in block 503, or in response to a request for the gap (message 2-1), it is checked in block 602, whether the gap configurations con- tain any configurations for timer actions.

Timers having one or more timer actions configured in the gap configu- ration (block 602: yes) are run (block 603) during gaps as defined in the received timer action configuration.

Timers having no timer action configured in the gap configuration (block 602: no) are run (block 604) during the gaps according to default timer ac- tions. For example, the default timer actions may be defined per a timer (timer type), and/or per a timer class, and/or a common timer may be used for timers.

For example, following default actions may be used: for timers belong- ing (classified) to the prohibition timer class or to the buffer status timer class a default action may be to continue running, for timers belonging to the inactivity timer class, a default action may be to suspend, for timers belonging to the failure detection and recovery timer class, a default action may be to stop and restart after the gap, and for timers belonging to the discontinuous reception timer class, a de- fault action may be to run with a specific condition that the user device starts with an on-duration timer after the gap.

As can be seen, a default action for a timer may be overridden by the gap configuration comprising definitions configuring the timer to perform another action.

Figure 7 illustrates an example how to implement timer actions during a gap. In the illustrated example, it is assumed that a gap configuration with timer actions have been received (block 700). For the sake of description timers are pro- cessed in a serial manner. However it should be appreciated that timers may be processed, using the substantially same principles, in a parallel manner as well. Further, the timers are timers running for a subscription entity that is in the active state and which has requested the gaps.

When it is detected in block 701 that a gap starts, an unprocessed timer is taken in block 702 to be processed. In step 703 it is checked, whether there is an individual gap configuration for the timer.

If not (block 703: no), the timer class of the timer and corresponding configured action for the timer class is determined in block 704. If the action is to suspend (block 705: yes), the timer is stopped in block 706 with an indication to restart after the gap with the current value of the timer (i.e. with the value at the time the gap starts).

If the action is to stop with an offset (block 705: no, block 707: yes), the timer is stopped in block 708 with an indication to restart after the gap with the offset value.

If the action is to stop (block 705: no, block 707: no, block 709: yes), the timer is stopped in block 710 with an indication to restart after the gap with an initial start value of the timer.

If the action is to continue with an offset (block 705: no, block 707: no, block 709: no, block 711: no), the timer continues to run in block 712 with its cur- rent value. In other words, the gap does not affect to the timer.

If the action is to continue with a modified value (block 705: no, block 707: no, block 709: no, block 711: yes), the timer continues to run in block 713 with a modified value which is its value at the time the gap starts added with the offset value.

When the action has been determined (i.e. after block 706, or after block 708, or after block 710, or after block 712 or after block 713), it is checked in block 714 whether an action has been determined for timers to which an action is to be determined (i.e. whether such timers have undergone the process). If not (block 714: no), the process continues to block 702 to take another timer to be processed.

When there is an individual gap configuration for the timer (block 703: yes), the process checks in block 715, whether the timer is a timing advance (TA) timer. If not (block 715: no), the process proceeds to block 705 to determine the action configured for the timer.

If the timer is the timing advance timer (block 715: yes), the parameters in the gap configuration may define a condition when to continue running with an offset and when without an offset. The offset, if any, may depend on downlink measurement results. Therefore, depending whether there is a condition, and whether the condition is fulfilled, the timing advance timer continues to run in block 716 with a possible offset to its current value, or with the current value.

When the timers have been processed (block 714: yes), it is monitored in block 717 when the gap ends. When the gap ends (block 717: yes), the timers running continue to run and stopped timers are restarted in block 718 with the indicated value. It should be appreciated that the actions described with Figure 7 are mere examples and any other actions, or a subset of the actions may be used as well.

As can be seen especially from Figure 7, there may be for a subscription entity in an active state a number of timers running differently during a gap and outside the gap.

As can be seen from the above examples, different solutions providing interworking of configured grants and/or different timers during one or more mul- tiple user subscription gaps (MUS1M gaps) in a subscription entity being in an ac- tive state in a user device (an RRC connected MUS1M UE).

The blocks, related functions, and information exchanges described above by means of Figures 2 to 7 are in no absolute chronological order, and some of them may be performed simultaneously or in an order differing from the given one. Other functions can also be executed between them or within them, and other information may be transmitted, and/or other rules applied. For example, a user device may request a gap configuration when a subscription identity transits from the idle or inactive state to the active state, and the first gap configuration may de- fine when a gap is started, a duration of the gap and a periodicity of the gap, and when a configured grant is received, the user device requests an updated gap con- figuration, the updated gap configuration comprising one or more parameters de- fining information for processing (e.g., how to process) one or more events, as de- scribed above. Correspondingly, the access node is configured to determine whether the gap configuration is a first one or an updated one, and provide corre- sponding gap configurations. The first gap configuration may configure timer ac- tions, and the updated configuration may configure further timer actions and/or parameters for more robust transmission and disabling feedback. In a still further example, the access node may send a configured grant with updated gap configu- ration, i.e. without a specific request for updated gap configuration from the user device, based on an earlier received gap request and an existing gap configuration (the first or updated) for the user device. Some of the blocks or part of the blocks or one or more pieces of information can also be left out or replaced by a corre- sponding block or part of the block or one or more pieces of information.

Figures 8 and 9 illustrate apparatuses comprising a communication controller 810, 910 such as at least one processor or processing circuitry, and at least one memory 820, 920 including a computer program code (software, algo- rithm) ALG. 821, 921, wherein the at least one memory and the computer program code (software, algorithm) are configured, with the at least one processor, to cause the respective apparatus to carry out any one of the embodiments, examples and implementations described above. Figure 8 illustrates an apparatus configured to provide wireless access and gap configurations to user devices, or any correspond- ing apparatus, supporting multiple user subscription identities, and Figure 9 illus- trates an apparatus for operating during gaps as configured by the apparatus in Figure 8. It should be appreciated that an apparatus may be configured to be a com- bination of the apparatuses of Figures 8 and 9, i.e. serving one or more apparatuses supporting multiple user subscription entities while itself supporting multiple user subscription entities and using one of them towards a core network. The apparat- uses of Figures 8 and 9 may be electronic devices, for example a wearable device, a home appliance device, a smart device, like smart phone or smart screen, a vehicu- lar device, just to name couple of examples in addition to those listed with Figure 1.

Referring to Figures 8 and 9, the memory 820, 920 may be implemented using any suitable data storage technology, such as semiconductor based memory devices, flash memory, magnetic memory devices and systems, optical memory de- vices and systems, fixed memory and removable memory. The memory may com- prise a configuration storage CONF. 821, 921, such as a configuration database, for at least storing gap configurations. The memory 820, 920 may further store a data buffer for data waiting to be processed (including transmission).

Referring to Figure 8, the apparatus, for example gNB, comprises a com- munication interface 830 comprising hardware and/or software for realizing com- munication connectivity according to one or more wireless and/or wired commu- nication protocols. The communication interface 830 may provide the apparatus with radio communication capabilities with user devices (terminal devices, appa- ratuses) camping in one or more cells controlled by the apparatus, as well as com- munication capabilities towards a wired network.

Digital signal processing regarding transmission and reception of sig- nals may be performed in a communication controller 810. The communication in- terface may comprise standard well-known components such as an amplifier, filter, frequency-converter, (de) modulator, and encoder/decoder circuitries and one or more antennas.

The communication controller 810 comprises a gap configuring pro- cessing circuitry 811 configured to configure user devices with gap configura- tion(s) according to any one of the embodiments/examples/implementations de- scribed above. The communication controller 810 may control the gap configuring processing circuitry 811. Further, the communication controller 810 may control information exchange and/or related timers according to a corresponding gap con- figuration so that the apparatus of Figure 8 and a configured apparatus operate in a synchronous manner.

In an embodiment, at least some of the functionalities of the apparatus of Figure 8 may be shared between two physically separate devices, forming one operational entity. Therefore, the apparatus may be seen to depict the operational entity comprising one or more physically separate devices for executing at least some of the processes described with respect to the gNB.

Referring to Figure 9, the apparatus 900 may further comprise a com- munication interface 930 comprising hardware and/or software for realizing com- munication connectivity according to one or more communication protocols. The communication interface 930 may provide the apparatus 900 with communication capabilities with the apparatus of Figure 8. The communication interface may com- prise standard well-known analog components such as an amplifier, filter, fre- quency-converter and circuitries, and conversion circuitries transforming signals between analog and digital domains. Digital signal processing regarding transmis- sion and reception of signals may be performed in a communication controller 910.

The communication controller 910 comprises a multiple subscriber identity (MUSIM) supporting processing circuitry 911 configured to use received gap configurations according to any one of the embodiments/examples/imple- mentations described above. The multiple subscriber identity supporting pro- cessing circuitry 911 may be configured to request gap configurations according to any one of the embodiments/examples/implementations described above. The communication controller 910 may control the multiple subscriber identity sup- porting processing circuitry 911. Depending on an implementation, one or more timers may be controlled by the communication controller 910 and/or by the mul- tiple subscriber identity supporting processing circuitry 911.

As used in this application, the term 'circuitry' refers to all of the follow- ing: (a) hardware-only circuit implementations, such as implementations in only analog and/or digital circuitry, and (b) combinations of circuits and soft- ware (and/or firmware), such as (as applicable): (i) a combination of processor(s) or (ii) portions of processor(s)/software including digital signal processor(s), software, and memory(ies) that work together to cause an apparatus to perform various functions, and (c) circuits, such as a microprocessor(s) or a portion of a micropro- cessor(s), that require software or firmware for operation, even if the software or firmware is not physically present. This definition of 'circuitry' applies to all uses of this term in this application. As a further example, as used in this application, the term 'circuitry' would also cover an implementation of merely a processor (or mul- tiple processors) or a portion of a processor and its (or their) accompanying soft- ware and/or firmware. The term 'circuitry' would also cover, for example and if applicable to the particular element, a baseband integrated circuit or applications processor integrated circuit for a mobile phone or a similar integrated circuit in a server, a cellular network device, or another network device.

In an embodiment, at least some of the processes described in connec- tion with Figures 2 to 7 may be carried out by an apparatus comprising correspond- ing means for carrying out at least some of the described processes. The apparatus may comprise separate means for separate phases of a process, or means may per- form several phases or the whole process. Some example means for carrying out the processes may include at least one of the following: detector, processor (includ- ing dual-core and multiple-core processors), digital signal processor, controller, re- ceiver, transmitter, encoder, decoder, memory, RAM, ROM, software, firmware, dis- play, user interface, display circuitry, user interface circuitry, user interface soft- ware, display software, circuit, antenna, antenna circuitry, and circuitry. In an em- bodiment, the at least one processor, the memory, and the computer program code form processing means or comprises one or more computer program code por- tions for carrying out one or more operations according to any one of the embodi- ments/examples/implementations described herein.

According to yet another embodiment, the apparatus carrying out the embodiments/examples comprises a circuitry including at least one processor and at least one memory including computer program code. When activated, the cir- cuitry causes the apparatus to perform at least some of the functionalities accord- ing to any one of the embodiments/examples/implementations of Figures 2 to 7, or operations thereof.

The techniques and methods described herein may be implemented by various means. For example, these techniques may be implemented in hardware (one or more devices), firmware (one or more devices), software (one or more modules), or combinations thereof. For a hardware implementation, the appa- ratus (es) of embodiments may be implemented within one or more application- specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programma- ble gate arrays (FPGAs), processors, controllers, micro-controllers, microproces- sors, other electronic units designed to perform the functions described herein, or a combination thereof. For firmware or software, the implementation can be car- ried out through modules of at least one chip set (e.g. procedures, functions, and so on) that perform the functions described herein. The software codes may be stored in a memory unit and executed by processors. The memory unit may be imple- mented within the processor or externally to the processor. In the latter case, it can be communicatively coupled to the processor via various means, as is known in the art. Additionally, the components of the apparatuses (nodes) described herein may be rearranged and/or complemented by additional components in order to facili- tate the achievements of the various aspects, etc., described with regard thereto, and they are not limited to the precise configurations set forth in the given figures, as will be appreciated by one skilled in the art.

Embodiments/examples/implementations as described may also be carried out in the form of a computer process defined by a computer program or portions thereof. Embodiments of the methods described in connection with Fig- ures 2 to 7 may be carried out by executing at least one portion of a computer pro- gram comprising corresponding instructions. The computer program may be in source code form, object code form, or in some intermediate form, and it may be stored in some sort of carrier, which may be any entity or device capable of carry- ing the program. For example, the computer program may be stored on a computer program distribution medium readable by a computer or a processor. The com- puter program medium may be, for example but not limited to, a record medium, computer memory, read-only memory, electrical carrier signal, telecommunica- tions signal, and software distribution package, for example. The computer pro- gram medium may be a non-transitory medium, for example. Coding of software for carrying out the embodiments as shown and described is well within the scope of a person of ordinary skill in the art. In an embodiment, a computer-readable me- dium comprises said computer program.

It will be obvious to a person skilled in the art that, as technology ad- vances, the inventive concept may be implemented in various ways. The embodi- ments are not limited to the exemplary embodiments described above, but may vary within the scope of the claims. Therefore, all words and expressions should be interpreted broadly, and they are intended to illustrate, not to restrict, the exem- plary embodiments. ABBREVIATIONS 4G: fourth generation 5G: fifth generation ACK: acknowledgement AP: access point CG: configured grant CU: centralized unit CN: core network CPS: cyber-physical system DL: downlink DU: distributed unit

(e/g)NodeB: (evolved/next generation) node B E-UTRA: evolved UMTS terrestrial radio access E-UTRAN: evolved universal mobile telecommunications system radio access net- work

GEO: geostationary earth orbit GHz: gigahertz gNB: next generation nodeB HARQ: hybrid automatic repeat request

H(e/g)nodeBs: home (evolved/next generation) node Bs HNB: home node B HNB-GW: home node B gateway IAB: integrated access and backhaul ICT: information and communications technology IMS: Internet Protocol multimedia subsystems IP: internet protocol IoT: internet of things kHz: kilohertz LTE: longterm evolution

LTE-A: long term evolution advanced MANET: mobile ad-hoc network MEC: multi-access edge computing MME: mobile management entity mMTC: (massive) machine-type communications ms: milliseconds MSC: modulation coding scheme MT: mobile termination M2M: machine-to-machine

MUSIM: multi universal subscriber identity module NACK: negative acknowledgement NDI: new data indicator NGC: next generation core NR: new radio

NVF: network function virtualization PCS: personal communications services PDA: personal digital assistant PDCCH: physical downlink control channel PDSCH: physical downlink shared channel P-GW: packet data network gateway RAN: radio access network RAT: radio access technology RI: radio interface RRC: radio resource control rx: reception S-GW: serving gateway

UE: user device or user equipment SDN: software defined networking SIM: subscriber identification module SPS: semi persistent scheduling TA: timing advance

TBS: transport block size tx: transmission UL: uplink

UMTS: universal mobile telecommunications system USIM: universal subscriber identity module

UTRAN: universal mobile telecommunications system radio access network UWB: ultra-wideband

WCDMA: wideband code division multiple access WiFi: wireless local area network WiMAX: worldwide interoperability for microwave access WLAN: wireless local area network

Claims

1. An apparatus comprising at least one processor; and at least one memory including computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the apparatus at least to perform: supporting multiple user subscriptions; sending a multiple user subscription gap request to an access node us- ing a first subscription entity which is in an active state; receiving in a radio resource reconfiguration message at least a gap con- figuration to be used during one or more multiple user subscription gaps, the gap configuration comprising one or more parameters defining information for pro- cessing one or more events relating to the first subscription which remains in the active state during the gap; and using the gap configuration during multiple user subscription gaps.

2. An apparatus of claim 1, wherein the multiple user subscription gap request is sent in response to receiving from the access node a configured grant to a first subscription entity, which is in an active state.

3. An apparatus comprising at least one processor; and at least one memory including computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the apparatus at least to perform: providing access node functionalities; determining, when a multiple user subscription gap request has been received from a served apparatus, at least a gap configuration to be used during one or more multiple user subscription gap, the gap configuration comprising one or more parameters defining information for processing one or more events relat- ing to the served apparatus which remains in the active state during the gap; sending in a radio resource reconfiguration message at least the gap configuration; and using the gap configuration for the served apparatus.

4. An apparatus of claim 1, 2 or 3, wherein the one or more parameters in the gap configuration configures uplink data transmissions by setting parame- ters providing enhanced transmission and disabling reception feedback.

5. An apparatus of claim 4, wherein the reception feedback is disabled by disabling a hybrid automatic repeat request operation.

6. An apparatus of claim 4 or 5, wherein the parameters providing the enhanced transmission relate to one or more of a modulation coding scheme, a transport block size, a precoding, or a number of layers.

7. An apparatus of any preceding claim, wherein the one or more pa- rameters in the gap configuration configures downlink data transmissions by set- ting an offset to semi-persistent scheduling of configured grants in downlink.

8. An apparatus of any preceding claim, wherein the one or more pa- rameters in the gap configuration configures one or more timer actions.

9. An apparatus of claim 8, wherein the one or more timer actions in- clude an action per a timer class.

10. An apparatus of claim 8 or 9, wherein a timer action is one of the following: suspend, stop and restart after the gap with initial value, stop and restart after the gap with modified value, continue running during the gap starting with a current value, continue running during the gap starting with a modified value, or if one or more conditions are fulfilled, continue running during the gap starting with a modified value, otherwise continue running with the current value.

11. An apparatus of claim 8, 9 or 10, wherein default timer actions are used when a gap configuration is silent on the timer actions.

12. An apparatus of claim 11, wherein a default timer action for timers belonging to a discontinuous timer class is to continue running if the apparatus starts with on-duration timer after the gap.

13. A method comprising: using, by an apparatus, for a first subscription entity, which is in an ac- tive state, during a multiple user subscription gap for one or more inactive or idle state subscription entities, a gap configuration comprising one or more parameters defining information for processing one or more events relating to the first sub- scription entity which remains in the active state during the gap.

14. A computer-readable medium comprising program instructions, which, when run by an apparatus, causes the apparatus to carry out at least one of a first process or a second process, wherein the first process comprises at least: supporting multiple user subscriptions; sending a multiple user subscription gap request to an access node us- ing a first subscription entity which is in an active state; using, in response to receiving in a radio resource reconfiguration mes- sage at least a gap configuration to be used during one or more multiple user sub- scription gaps, the gap configuration comprising one or more parameters defining information for processing one or more events relating to the first subscription which remains in the active state during the gap, the gap configuration received during multiple user subscription gaps, wherein the second process comprises at least: providing access node functionalities; determining, when a multiple user subscription gap request has been received from a served apparatus, at least a gap configuration to be used during one or more multiple user subscription gaps, the gap configuration comprising one or more parameters defining information for processing one or more events relat- ing to the served apparatus which remains in the active state during the gap; sending in a radio resource reconfiguration message at least the gap configuration; and using the gap configuration for the served apparatus.

15. A computer readable medium of claim 14, wherein the computer readable medium is a non-transitory computer readable medium.

16. A computer program comprising instructions which, when the pro- gram is executed by an apparatus, cause the apparatus to carry out at least one of a first process or a second process, wherein the first process comprises at least: supporting multiple user subscriptions; sending a multiple user subscription gap request to an access node us- ing a first subscription entity which is in an active state; using, in response to receiving in a radio resource reconfiguration mes- sage at least a gap configuration to be used during one or more multiple user sub- scription gaps, the gap configuration comprising one or more parameters defining information for processing one or more events relating to the first subscription which remains in the active state during the gap, the gap configuration received during multiple user subscription gaps, wherein the second process comprises at least: providing access node functionalities; determining, when a multiple user subscription gap request has been received from a served apparatus, at least a gap configuration to be used during one or more multiple user subscription gaps, the gap configuration comprising one or more parameters defining information for processing one or more events relat- ing to the served apparatus which remains in the active state during the gap; sending in a radio resource reconfiguration message at least the gap configuration; and using the gap configuration for the served apparatus.

17. An apparatus comprising means for: supporting multiple user subscriptions; sending a multiple user subscription gap request to an access node us- ing a first subscription entity which is in an active state; receiving in a radio resource reconfiguration message at least a gap con- figuration to be used during one or more multiple user subscription gaps, the gap configuration comprising one or more parameters defining information for pro- cessing one or more events relating to the first subscription which remains in the active state during the gap; and using the gap configuration during multiple user subscription gaps.

18. An apparatus comprising means for: providing access node functionalities; determining, when a multiple user subscription gap request has been received from a served apparatus, at least a gap configuration to be used during one or more multiple user subscription gap, the gap configuration comprising one or more parameters defining information for processing one or more events relat- ing to the served apparatus which remains in the active state during the gap; sending in a radio resource reconfiguration message at least the gap configuration; and using the gap configuration for the served apparatus.