Abstract: A user device, UE,(300) for one or more wireless communication systems, includes one or more transceiver chains. The UE shares at least one transceiver chain with at least two connections to the one or more wireless communication systems (308, 310). The UE is connected to one or more network entities, like a gNB or another UE, with the connections, and perform one or more operations on the connections at respective operation occasions. When the UE transmits or receives on a current one of the connections, it does not to transmit or receive on the other connections.
ENHANCED MULTI-CONNECTION OPERATIONS
Description
The present invention concerns the field of wireless communication systems or networks, more specifically communications between a user device, like a UE, and one or more network entities, like a base station or a receiving user device, where the UE is a multiconnection UE sharing a transmitter/receiver chain with two or more connections.
Fig. 1 is a schematic representation of an example of a terrestrial wireless network 100 including, as is shown in Fig. 1(a), a core network 102 and one or more radio access networks RANi, RAN2, ...RANn. Fig. 1(b) is a schematic representation of an example of a radio access network RANn that may include one or more base stations gNBi to gNB5, each serving a specific area surrounding the base station schematically represented by respective cells 106i to IO65. The base stations are provided to serve users within a cell. It is noted that a base station may also operate multiple, i.e. , two or more cells (not illustrated in Fig. 1), and, in case a base station operates multiple cells, neighboring cells may include cells operated by the same base station and/or cells operated by the different base stations, i.e., a neighboring cell may also be a different cell of the same base station or a different cell of a different same base station. The one or more base stations may serve users in licensed and/or unlicensed bands. The term base station, BS, refers to a gNB in 5G networks, an eNB in UMTS/LTE/LTE-A/ LTE-A Pro, or just a BS in other mobile communication standards. A user may be a stationary device or a mobile device. The wireless communication system may also be accessed by mobile or stationary loT devices which connect to a base station or to a user. The mobile devices or the loT devices may include physical devices, ground based vehicles, such as robots or cars, aerial vehicles, such as manned or unmanned aerial vehicles (UAVs), the latter also referred to as drones, buildings and other items or devices having embedded therein electronics, software, sensors, actuators, or the like as well as network connectivity that enables these devices to collect and exchange data across an existing network infrastructure. Fig. 1(b) shows an exemplary view of five cells, however, the RANn may include more or less such cells, and RANn may also include only one base station. Fig. 1(b) shows two users UEi and UE2, also referred to as user equipment, UE, that are in cell 1062 and that are served by base station gNB2. Another user UE3 is shown in cell IO64 which is served by base station gNB.4. The arrows IO81, 1082 and IO83 schematically represent uplink/downlink connections for
transmitting data from a user UEi, UE2 and UE3 to the base stations gNB2, gNB4 or for transmitting data from the base stations gNB2, gNB4 to the users UEi, UE2, UE3. This may be realized on licensed bands or on unlicensed bands. Further, Fig. 1(b) shows two loT devices 110i and 1102 in cell IO64, which may be stationary or mobile devices. The loT device 110i accesses the wireless communication system via the base station gNB to receive and transmit data as schematically represented by arrow 112i. The loT device 1102 accesses the wireless communication system via the user UE3 as is schematically represented by arrow 1122. The respective base station gNBi to gNBs may be connected to the core network 102, e.g. via the S1 interface, via respective backhaul links 114i to 114s, which are schematically represented in Fig. 1(b) by the arrows pointing to “core”. The core network 102 may be connected to one or more external networks. Further, some or all of the respective base station gNBi to gNBs may connected, e.g. via the S1 or X2 interface or the XN interface in NR, with each other via respective backhaul links 1161 to 1165, which are schematically represented in Fig. 1(b) by the arrows pointing to “gNBs”.
For data transmission a physical resource grid may be used. The physical resource grid may comprise a set of resource elements to which various physical channels and physical signals are mapped. For example, the physical channels may include the physical downlink, uplink and sidelink shared channels (PDSCH, PUSCH, PSSCH) carrying user specific data, also referred to as downlink, uplink and sidelink payload data, the physical broadcast channel (PBCH) carrying for example a master information block (MIB) and a system information block (SIB), the physical downlink, uplink and sidelink control channels (PDCCH, PUCCH, PSCCH) carrying for example the downlink control information (DCI), the uplink control information (UCI) and the sidelink control information (SCI). For the uplink, the physical channels may further include the physical random access channel (PRACH or RACH) used by UEs for accessing the network once a UE synchronized and obtained the MIB and SIB. The physical signals may comprise reference signals or symbols (RS), synchronization signals and the like. The resource grid may comprise a frame or radio frame having a certain duration in the time domain and having a given bandwidth in the frequency domain. The frame may have a certain number of subframes of a predefined length, e.g.
1ms. Each subframe may include one or more slots of 12 or 14 OFDM symbols depending on the cyclic prefix (CP) length. A frame may also consist of a smaller number of OFDM symbols, e.g. when utilizing shortened transmission time intervals (sTTI) or a mini-slot/non-slot-based frame structure comprising just a few OFDM symbols.
The wireless communication system may be any single-tone or multicarrier system using frequency-division multiplexing, like the orthogonal frequency-division multiplexing (OFDM) system, the orthogonal frequency-division multiple access (OFDMA) system, or any other IFFT-based signal with or without CP, e.g. DFT-s-OFDM. Other waveforms, like non-orthogonal waveforms for multiple access, e.g. filter-bank multicarrier (FBMC), generalized frequency division multiplexing (GFDM) or universal filtered multi carrier (UFMC), may be used. The wireless communication system may operate, e.g., in accordance with the LTE-Advanced pro standard, or the 5G or NR, New Radio, standard, or the NU-U, New Radio Unlicensed, standard.
The wireless network or communication system depicted in Fig. 1 may by a heterogeneous network having distinct overlaid networks, e.g., a network of macro cells with each macro cell including a macro base station, like base station gNBi to gNB5, and a network of small cell base stations (not shown in Fig. 1), like femto or pico base stations.
In addition to the above described terrestrial wireless network also non-terrestrial wireless communication networks exist including spaceborne transceivers, like satellites, and/or airborne transceivers, like unmanned aircraft systems. The non-terrestrial wireless communication network or system may operate in a similar way as the terrestrial system described above with reference to Fig. 1 , for example in accordance with the LTE-Advanced Pro standard or the 5G or NR, new radio, standard.
In mobile communication systems or networks, like those described above with reference to Fig. 1 , for example in a LTE or 5G/NR network, the respective entities may communicate using a plurality of frequency bands, also referred to as a wideband operation. In a wideband operation, for example, the base station, gNB, and/or the user device, UE, may transmit on multiple subbands. The subbands may have different bandwidths or the same bandwidth, like 20MHz. Some or all of the subbands may be unlicensed bands. For communicating on an unlicensed band, the gNB and UE perform listen-before-talk, LBT, separately per unlicensed subband which may lead to a situation that one or more of the subbands to be used for the wideband operation, also referred to as a subset of the subbands, is busy or occupied due to a transmission or interference by one or more other public land mobile networks, PLMNs, or by one or more other communication systems coexisting on the same frequency band, for example systems operating in accordance with the IEEE 802.11 specification.
It is noted that the information in the above section is only for enhancing the understanding of the background of the invention and therefore it may contain information that does not form prior art that is already known to a person of ordinary skill in the art.
Starting from prior art as described above, there may be a need for improvements for multiconnection communications between a user device sharing its RF chain with two or more of the connections and respective network entities.
Embodiments of the present invention are now described in further detail with reference to the accompanying drawings:
Fig. 1 shows a schematic representation of an example of a wireless communication system;
Fig. 2 is a schematic representation of a wireless communication system including a transmitter, like a base station, and one or more receivers, like user devices, UEs;
Fig. 3 illustrates an embodiment of a multi-connection UE identifying towards a network entity operation occasions of respective connections sharing an RF chain of the UE;
Fig. 4 illustrates an embodiment employing a tune away signal which is signaled to a serving network entity before switching to one or more operations on another connection;
Fig. 5 illustrates an embodiment of the third aspect of the present invention placing a current connection of a multi-connection UE into a hold condition based on the network entity’s knowledge about the certain operation occasions on the other connections without using a tune away signal;
Fig. 6 illustrates a further embodiment of the third aspect of the present invention employing the hold condition and the tune away timer responsive to the tune away signal;
Fig. 7 is a flowchart illustrating an embodiment in which the hold condition expiry timer is employed; and
Fig. 8 illustrates an example of a computer system on which units or modules as well as the steps of the methods described in accordance with the inventive approach may execute.
Embodiments of the present invention are now described in more detail with reference to the accompanying drawings in which the same or similar elements have the same reference signs assigned.
In wireless communication systems or networks, like the one described above with reference to Fig. 1 , one or more of the mobile users, UEs, may be so-called multi-connection mobile users or multi-connection UEs. A multi-connection UE may include one or more transmitter (Tx) / receiver (Rx) chains, also referred to as radio frequency, RF, transceiver chains. The multi-connection UE shares an RF transceiver chain with two or more connections, which also may be referred to as independent or shared connections, so that, at a certain point in time only one of the connections has access to the RF transceiver chain. In other words, at a certain point in time the UE is connected to a network entity with a current one of the connections that share the RF transceiver chain, and the network entity may be a base station in case of a communication over the Uu interface, or it may be a other UE in case of a sidelink communication using, for example, the PC5 interface. The current connection may also be referred to as being in the connected state. The other connections that share with the current connection the RF transceiver chain are in a state in which they have no active connection to a network entity, however, the other connections are able to perform one or more operations at respective operation occasions. The network entity may be a network entity different from the one to which the current connection communicates. For example, when considering the a wireless communication system, some of the base stations may be operated in accordance with a first standard, like the GSM or LTE standard, while other base stations may be operated in accordance with another standard, like the NR standard. Thus, the multi-connection UE may provide for a first connection to the GSM network and for a second connection to the NR network via a common RF transceiver chain so that, when the UE is connected via its current connection to the GSM network, this connection is in the connected state, while the second connection to the NR system is not active, for example is in an idle state or in an inactive state or in a DRX cycle. The respective network entities are not necessarily associated with different standards, rather, the network entities may employ the same standard, for example, the UE may provide for two independent connections to two different network entities of the same network, like a NR network. The entities may be operated by the same or by different mobile network operators, MNOs.
Thus, in a scenario as explained above, the current connection is in the connected state, also referred to as to the RRC connected state. In this state, a data transfer between the UE and the network is possible. The RRC context is established. Also the core network connection is established and a network-controlled mobility is enabled. On the other hand, the other connections are in a non-active state, for example in an idle state, also referred to as the RRC idle state. In this state, no data transfer is possible, there is no RRC context and there is no core network connection. However, a device controlled mobility is enabled. In accordance with the NR approach, a new RRC state is introduced, which is referred to as the RRC inactive state. This state may be seen as being somewhat in-between the RRC idle state and the RRC connected state as it is known from the LTE standard. The RRC inactive state allows a UE to receive certain control messages as well as to send a limited set of control messages to make it easier to track a moving UE within a cell, for example in case of vehicular UEs, also referred to as V-UEs. Thus, a connection of the UE sharing the RF transceiver chain with another connection and being in the non-active state may also be in an inactive state, like the just-mentioned RRC inactive state. During the RRC inactive state, no data transfer is possible, however, the RRC context as well as the core network connection is established and also device-controlled mobility is enabled. Furthermore, the non-active connection may be in a DRX state where the UE is RRC connected but not receiving any data from the network for the duration of the DRX cycle.
The multi-connection UE may provide for an identification of the connections to the one or more wireless communication systems or the entities thereof. For example, the respective connections sharing the RF transceiver chain of the UE may be identified by one or more subscriber identities module, SIM, cards in the UE, and each SIM card is associated with one of the connections. The connections may also be identified by one or more of:
• one or more universal Subscriber Identity Module, USIM, cards, each USIM card associated with one of the connections,
• one or more universal integrated circuit cards, ICCs, each ICC associated with one of the connections,
• one or more embedded Subscriber Identity Modules, eSIMs, each eSIM associated with one of the connections,
• one or more certificates, each certificate associated with one of the connections,
• one or more pairs of username and password, each pair associated with one of the connections,
• one or more International Mobile Station Equipment Identities (IMEI) each associated with one of the connections,
• one or more Mobile Equipment Identifiers (MEID) each associated with one of the connections.
Thus, when considering a multi-connection UE as described above, the respective connections that share the RF transceiver chain, which have associated therewith the respective identifiers, may be seen from a network perspective as separate UEs being served by the respective network entities. The connections may be associated with the same or different network operators.
In a multi-connection UE as described above, certain operations may be performed at certain occasions also referred to as certain instances in time, over the respective connections that share the RF transceiver chain. Sharing the RF transceiver chain among one or more connections, however, results in a situation that a service for the UE may be provided only using of the connections, thereby rendering the UE to be not reachable using the other connections. Thus, operations may only be performed using the current connection at the certain occasions while other operations over the non-current connections which are in the non-active state, may not be performed. Thus, operations for the non-current connection may be missed by the UE. On the other hand, in case the implementation is such that the other connections become active at the occasions where their respective operations are to be performed, this results in a service interruption of the current connection to the network entity which currently serves the UE via the current connection.
The above-referenced operations may include a variety of different operations to be performed between the UE and the network at different points in time. For example, the operations may include one or more of the following:
• reading a broadcast of system information, MIB/SIB,
• receiving RAN-based notification area (RNA) updates,
• reading a paging channel during a paging occasion, PO,
• reading a PDCCH monitoring occasion, MO,
• receiving or transmitting according to a semi-persistent scheduling, SPS,
• transmitting on a configured grant, CG,
• performing a measurement, e.g. SMTC or DMTC or mobility measurements,
» performing a random access, RACH,
• transmitting on a scheduled grant, PUSCH,
• transmitting any control information, e.g. via PUCCH,
• receiving scheduled data, PDCCH or PDSCH,
• transmitting on a sidelink interface using any sidelink physical channel, e.g.
PSSCH/PSCCH/PSFCH via PC5.
With reference to the reading of a paging channel during the paging occasion, PO, some problems with regard to the respective operations occurring at certain occasions on the different shared connections, one of which is in the connected state while the others are in the idle state or in the inactive state shall, now be discussed. The paging is a process in which an idle mode UE wakes up periodically based on a DRX, discontinuous reception, cycle to read a paging channel during the paging occasion. In case the UE finds relevant information in the paging channel, the UE will transition to the connected mode. Otherwise, the UE continues to monitor subsequent paging occasions, POs. This feature is supported by the UEs, and in case of a multi-connection UE all of the connections need to monitor the respective paging channels. A first problem in a multi-connection UE having a single RF transceiver chain or sharing one of its RF transceiver chains among at least two connections is that the need for each connection to monitor the respective paging channel may lead to an overlap in the paging occasions which, in turn, may result in a delay or a loss of data on any of the connections. In other words, at least some of the connections may be associated with paging occasions that occur at the same time or that overlap, so that when being connected via the current connection to read the paging channel, the paging information on another paging channel for a non-current connection that occurs substantially at the same time, cannot be read by the UE and is lost. Therefore, data may be lost because the other connection is not aware that data is to be sent via this connection or at least a delay in receiving the data may occur until the paging channel can be read by the other connection.
Another issue regarding multi-connection UEs is the above-mentioned service interruption. For example, when considering the current connection to the network entity which is in the RRC connected state, and in case it is required that also the other connections monitor their paging occasion or monitor system information, the UE may abruptly tune away from the network entity to which it is currently connected and by which the UE is currently served via the current connection. The tuning away may include that the UE connects to another network entity using another one of the shared connections so as to perform the paging or system information update using the other one of the connections sharing with the current connection the RF transceiver chain of the multi-connection UE. This leads to a service interruption on the current connection which, in turn, may lead to an unexpected behavior in the network.
In other words, when an operation is to be performed at a certain operation occasion on another one of the connections which is not the current connection, the UE tunes away from the current connection so as to be in active or connected state to another network entity via the other connection so as to allow to perform the certain operation at the operation occasion or time. This may also be referred to as the UE temporarily tuning away from the current connection and returning to the current connection after completing the operation on the other connection.
The service interruption may lead to an undesired error situation at the network entity because the time that the UE is catering to the services or operations using another one of the non-current connections, this, conventionally, leads to an error case for the serving network entity because the serving network entity is not aware of the UE procedure and the type of operations using the other connections. Thus, the network entity may continue scheduling resources for a connection to the temporarily suspended connection because of the tune away which leads to a waste of resources which cannot be used for connections to other UEs in the wireless system, and also an unexpected behavior may result since the current connection may except some control information, e.g. PUCCH, and/or a data transmission, e.g. PUSCH, from the UE. For example, if the UE does not transmit a PUCCH, the HARQ state of previous transmissions stays unclear. In the worst scenario, the gNB may falsely detect a PUCCH transmission including HARQ feedback and interpret a false acknowledgement for the previous transmissions.
As mentioned above, the above problems may not only arise when reading the paging channel of the respective systems or networks to which the connections sharing the RF transceiver chain are connected, but it may also occur for the above-summarized operations requiring the one or more other connections which are in the idle state or in the inactive state to connect to the entities which serve the UE via the respective connection so as to obtain information or data. In other words, the situation that certain operations at certain occasions need to be carried out on the different connections that share a RF transceiver chain in the UE may result in situations in which the respective occasions overlap so that only one of the connections can receive the information and/or it may lead to a service interruption of the current operation.
The present invention addresses the above-discussed issues and provides improvements and enhancements for the operation of multi-connection UEs within one or more wireless communication systems or networks.
Embodiments of the present invention may be implemented in a wireless communication system as depicted in Fig. 1 including base stations and users, like mobile terminals or loT devices. Fig. 2 is a schematic representation of a wireless communication system including a transmitter 300, like a base station, and one or more receivers 302i to 302n, like user devices, UEs. The transmitter 300 and the receivers 302 may communicate via one or more wireless communication links or channels 304a, 304b, 304c, like a radio link. The transmitter 300 may include one or more antennas ANTT or an antenna array having a plurality of antenna elements, a signal processor 300a and a transceiver 300b, coupled with each other. The receivers 302 include one or more antennas ANTR or an antenna array having a plurality of antennas, a signal processor 302ai, 302an, and a transceiver 302bi, 302bn coupled with each other. The base station 300 and the UEs 302 may communicate via respective first wireless communication links 304a and 304b, like a radio link using the Uu interface, while the UEs 302 may communicate with each other via a second wireless communication link 304c, like a radio link using the PC5 interface. When the UEs are not served by the base station, are not be connected to a base station, for example, they are not in an RRC connected state, or, more generally, when no SL resource allocation configuration or assistance is provided by a base station, the UEs may communicate with each other over the sidelink. The system, the one or more UEs 302 and the base stations 300 may operate in accordance with the inventive teachings described herein.
USER DEVICE / NETWORK ENTITY
The present invention provides (see for example claim 1 ) a user device, UE, for one or more wireless communication systems, the UE comprising:
one or more transceiver chains,
wherein the UE is to share at least one transceiver chain with at least two connections to the one or more wireless communication systems,
wherein the UE is to be connected to one or more network entities, like a gNB or another UE, with the connections, and to perform one or more operations on the connections at respective operation occasions,
wherein, when the UE is to transmit or receive on a current one of the connections, the UE is not to transmit or receive on the other connections.
In accordance with embodiments (see for example claim 2), the UE is to signal to the network entity, to/from which it transmits/receives on the current connection, information about the one or more operation occasions associated with one or more or all of the other connections.
In accordance with embodiments (see for example claim 3), the UE is to signal an indication from which the operation occasions on one or some or all the connections are derivable, e.g., by the one or more network entities.
In accordance with embodiments (see for example claim 4), the indication includes
• a device identifier, the device identifier being unique for each UE in the wireless communication system and being associated with identifications of the connections, so as to indicate that the UE provides the at least two connections, and/or
• identifications of one or more or all of the connections, so as to indicate that the UE provides the at least two connections.
In accordance with embodiments (see for example claim 5), when attaching to a wireless communication system, the UE is to signal the information about the one or more operation occasions associated with one or more or all of the other connections, e.g., as part of an RRC signaling, and/or the indication from which the operation occasions on one or some or all the connections are derivable, e.g., as part of the UE capability information.
In accordance with embodiments (see for example claim 6), the UE signals the information or the indication so as to
• inform the one or more network entities about instances at which the UE is not available for the network entity, or
• allow the one or more network entities to avoid clashes or overlaps or collisions of one or more or all operation occasions associated with the current connection with the operation occasions associated with the remaining connections.
In accordance with embodiments (see for example claim 7), the UE is to provide for an identification, e.g., a unique identification or ID, of the respective connections to the one or more wireless communication systems, the identification including one or more of the following:
• one or more Subscriber Identity Module, SIM, cards, each SIM card associated with one of the connections,
• one or more universal Subscriber Identity Module, USIM, cards, each USIM card associated with one of the connections,
• one or more universal integrated circuit cards, ICCs, each ICC associated with one of the connections,
• one or more embedded Subscriber Identity Modules, eSIMs, each eSIM associated with one of the connections,
• one or more certificates, each certificate associated with one of the connections,
• one or more pairs of username and password, each pair associated with one of the connections,
• one or more International Mobile Station Equipment Identities (IMEI) each associated with one of the connections,
• one or more Mobile Equipment Identifiers (MEID) each associated with one of the connections.
In accordance with embodiments (see for example claim 8), the operations include one or more of the following
• reading a broadcast of system information, MIB/SIB,
• receiving RAN-based notification area (RNA) updates,
• reading a paging channel during a paging occasion, PO,
• reading a PDCCH monitoring occasion, MO,
• receiving or transmitting according to a semi-persistent scheduling, SPS,
• transmitting on a configured grant, CG,
• performing a measurement, e.g. SMTC or DMTC or mobility measurements, performing a random access, RACH,
• transmitting on a scheduled grant, PUSCH,
• transmitting any control information, e.g. via PUCCH,
• receiving scheduled data, PDCCH or PDSCH,
• transmitting on a sidelink interface using any sidelink physical channel, e.g.
PSSCH/PSCCH/PSFCH via PC5.
In accordance with embodiments (see for example claim 9), the connections are ranked or prioritized, and wherein the UE is to signal to the network entity only information about operation occasions associated with the other connections having a rank or priority that is the same or higher than the rank or priority of the current connection.
In accordance with embodiments (see for example claim 10), the rank or priority of a connection may be decided or determined by the UE, or by a network entity, or by an over-the-top, OTT, application.
In accordance with embodiments (see for example claim 11), the UE is to switch from the current connection, which becomes an old current connection, to one of the other connections, which becomes a new current connection, so as to signal to a network entity, to which it is connected with the new current connection to which the UE switched, information about the one or more or all operation occasions associated with the old current connection and/or one or more or all of the remaining connections.
In accordance with embodiments (see for example claim 12), the network entities, to/from which the UE is to transmit/receive using the respective connections, belong to the same mobile network operator, MNO, or to different mobile network operators, MNOs.
In accordance with embodiments (see for example claim 13), the connections are in the same state or are in different states, the states including, for example, one or more of:
• an RRC_CONNECTED state,
• an RRCJNACTIVE state, and
an IDLE state.
In accordance with embodiments (see for example claim 14), the UE is to be configured or pre-configured to use the at least two connections by the one or more wireless communication systems or by one or more of the network entities, like a gNB or another UE, by an application, APP, running on the UE or over-the-top, OTT.
The present invention provides (see for example claim 15) a network entity for a wireless communication system, wherein
the network entity is to be connected to a UE in the wireless communication system, the UE sharing at least one of its transceiver chains with at least two connections to one or more wireless communication systems, wherein the UE is to perform one or more operations on the connections at respective operation occasions, and wherein the UE is transmitting/receiving to/from the network entity on a current one of the connections,
wherein the network entity is to receive
• from the UE information about the one or more or all operation occasions associated with one or more or all of the other connections, and/or
• from the UE or from one or more other network entities an indication of the operation occasions on one or some or all the connections, and/or
• respective unique identifications of the connections, and
wherein, responsive to the information and/or the indication and/or the unique identifications, the network entity is to
• determine periods during which the UE is not available for the network entity, or
• calculate or recalculate one or more operation occasions associated with the current connection to avoid clashes or overlaps or collisions with the operation occasions associated with the remaining connections.
In accordance with embodiments (see for example claim 16), the; network entity is to extend a timer for declaring a radio link failure, RLF, at least by a duration of an period during which the UE is not available, or by a duration of operation occasions associated with the other connections.
In accordance with embodiments (see for example claim 17), the network entity is not to schedule data for the UE while a duration of a period during which the UE is not available, or while a duration of operation occasions associated with the other connections.
The present invention provides (see for example claim 18) a user device, UE, for one or more wireless communication system, the UE comprising:
one or more transceiver chains,
wherein the UE is to share at least one transceiver chain with at least two connections to the one or more wireless communication systems,
wherein the UE is to is to be connected to one or more network entities, like a gNB or another UE, with the connections, and to perform one or more operations on the connections at respective operation occasions,
wherein, when the UE is to transmit or receive on a current one of the connections, the UE is not to transmit or receive on the other connections, and
wherein, when the UE tunes away from an operation on the current connection to perform an operation on another one of the at least two connections, the UE is to signal a tune away signal, TAS, to the network entity, to which it is connected with the current connection.
In accordance with embodiments (see for example claim 19), the operation on the other one of the at least two connections includes one or more of the following
• reading a broadcast of system information, MIB/SIB,
• receiving RAN-based notification area (RNA) updates,
• reading a paging channel during a paging occasion, PO,
• reading a PDCCH monitoring occasion, MO,
• receiving or transmitting according to a semi-persistent scheduling, SPS,
• transmitting on a configured grant, CG,
• performing a measurement, e.g. SMTC or DMTC or mobility measurements, performing a random access, RACH,
transmitting on a scheduled grant, PUSCH,
® transmitting any control information, e.g. via PUCCH,
® receiving scheduled data, PDCCH or PDSCH,
transmitting on a sidelink interface using any sidelink physical channel, e.g. PSSCH/PSCCH/PSFCH via PC5.
In accordance with embodiments (see for example claim 20), the resources for the TAS are preconfigured and the UE is to receive them in an RRC configuration/reconfiguration message, or the resources for the TAS are dynamically assigned as a part of a resource assignment during an RRC_CONNECTED state.
In accordance with embodiments (see for example claim 21), theTAS includes an indication of the operation the UE tunes to and/or a time the UE is tuned away from the operation on the current connection.
In accordance with embodiments (see for example claim 22), responsive to an indication that the operation on the other connection, to which the UE tuned away, takes more time, e.g., more time than the predefined amount of time, the UE is to inform the network entity of the current connection that the tune away duration is longer than a tune away duration defined for the TAS, e.g., by:
• signaling a long tune away signal, Long TAS, to the network entity of the current connection, e.g., in case the indication is provided at the time of tuning away, or
• signaling a TAS update to the network entity of the current connection, e.g., in case the indication is provided at some time while the UE is tuned away.
In accordance with embodiments (see for example claim 23), the operation taking more time includes one or more of the following
• receiving a call in a paging occasion, PO,
• receiving an indication that data is to be received,
• receiving an indication that a high priority operation is to be performed.
In accordance with embodiments (see for example claim 24), the connections are in the same state or are in different states, the states including, for example, one or more of:
• an RRC_CONNECTED state,
• an RRCJNACTIVE state, and
« an IDLE state.
In accordance with embodiments (see for example claim 25), when tuning away, the current connection transitions to the RRCJNACTIVE state.
The present invention provides (see for example claim 26) a network entity for a wireless communication system, wherein
the network entity is to be connected to a UE in the wireless communication system, the UE sharing at least one of its transceiver chains with at least two connections to one or more wireless communication systems, wherein the UE is to perform one or more operations on the connections at respective operation occasions, and wherein the UE is transmitting/receiving to/from the network entity on a current one of the connections, and
the network entity is to receive a tune away signal, TAS, from the UE, the TAS indicating to the network entity that the UE tunes away from an operation on the current connection that is served by the network entity to perform an operation on another connection that is served by another network entity.
The present invention provides (see for example claim 27) a network entity for a wireless communication system, wherein
the network entity is to be connected to a UE in the wireless communication system, the UE sharing at least one of its transceiver chains with at least two connections to one or more wireless communication systems, wherein the UE is to perform one or more operations on the connections at respective operation occasions, and wherein the UE is transmitting/receiving to/from the network entity on a current one of the connections,
the network entity is aware of the one or more operation occasions associated with one or more or all of the other connections, and
using the knowledge about the one or more operation occasions, the network entity is to
• determine the UE tuning away from an operation on the current connection that is served by the network entity to perform an operation on another connection that is served by another network entity, and
• start a timer or put the current connection into a hold condition so as to avoid an error situation for the network entity.
The present invention provides (see for example claim 28) a network entity for a wireless communication system, wherein
the network entity is to be connected to a UE in the wireless communication system, the UE sharing at least one of its transceiver chains with at least two connections to one or more wireless communication systems, wherein the UE is to perform one or more operations on the connections at respective operation occasions, and wherein the UE is transmitting/receiving to/from the network entity on a current one of the connections, the network entity is to receive one or more tune away signals, TASs, from the UE, the TAS indicating to the network entity that the UE tunes away from an operation on the current connection that is served by the network entity to perform an operation on another connection that is served by another network entity, and
responsive to the TAS, the network entity is to start a timer or to put the current connection into a hold condition so as to avoid an error situation for the network entity.
In accordance with embodiments (see for example claim 29), a range of the timer includes a switching time across the connections plus and the time for performing the operation, like the time for processing data.
In accordance with embodiments (see for example claim 30), the length of the timer depends on one or more of the UE capabilities, and a time required to perform the one or more operations, like cell selection/reselection, paging, system information and tracking/routing area update, SPS transmissions, CG transmissions, measurements.
In accordance with embodiments (see for example claim 31), the network entity is not to schedule any data for the current connection during the length of the timer.
In accordance with embodiments (see for example claim 32), in the HOLD condition,
• a context of the current connection is maintained, and/or
• a reuse of the resources assigned to the current connection is allowed, and/or
® the network entity does not expect any configured UL transmissions from the current connection, such as PUCCH, PUSCH or CG, and/or
• extent or delay the start of the RLF timer at least by the duration of the HOLD condition.
CLAIMS
1. A user device, UE, for one or more wireless communication systems, the UE comprising:
one or more transceiver chains,
wherein the UE is to share at least one transceiver chain with at least two connections to the one or more wireless communication systems,
wherein the UE is to be connected to one or more network entities, like a gNB or another UE, with the connections, and to perform one or more operations on the connections at respective operation occasions,
wherein, when the UE is to transmit or receive on a current one of the connections, the UE is not to transmit or receive on the other connections.
2. The UE of claim 1 , wherein the UE is to signal to the network entity, to/from which it transmits/receives on the current connection, information about the one or more operation occasions associated with one or more or all of the other connections.
3. The UE of claim 1 or 2, wherein the UE is to signal an indication from which the operation occasions on one or some or all the connections are derivable, e.g., by the one or more network entities.
4. The UE of claim 3, wherein the indication includes
• a device identifier, the device identifier being unique for each UE in the wireless communication system and being associated with identifications of the connections, so as to indicate that the UE provides the at least two connections, and/or
• identifications of one or more or all of the connections, so as to indicate that the UE provides the at least two connections.
5. The UE of any one of claims 2 to 4, wherein, when attaching to a wireless communication system, the UE is to signal the information about the one or more operation occasions associated with one or more or all of the other connections, e.g., as part of an RRC signaling, and/or the indication from which the operation occasions on one or some or all the connections are derivable, e.g., as part of the UE capability information.
6. The UE of any one of claims 2 to 5, wherein the UE signals the information or the indication so as to
inform the one or more network entities about instances at which the UE is not available for the network entity, or
allow the one or more network entities to avoid clashes or overlaps or collisions of one or more or all operation occasions associated with the current connection with the operation occasions associated with the remaining connections.
7. The UE of any one of the preceding claims, wherein the UE is to provide for an identification, e.g., a unique identification or ID, of the respective connections to the one or more wireless communication systems, the identification including one or more of the following:
• one or more Subscriber Identity Module, SIM, cards, each SIM card associated with one of the connections,
• one or more universal Subscriber Identity Module, USIM, cards, each USIM card associated with one of the connections,
• one or more universal integrated circuit cards, ICCs, each ICC associated with one of the connections,
• one or more embedded Subscriber Identity Modules, eSIMs, each eSIM associated with one of the connections,
• one or more certificates, each certificate associated with one of the connections,
• one or more pairs of username and password, each pair associated with one of the connections,
• one or more International Mobile Station Equipment Identities (IMEI) each associated with one of the connections,
• one or more Mobile Equipment Identifiers (MEID) each associated with one of the connections.
8. The UE of any one of the preceding claims, wherein the operations include one or more of the following
• reading a broadcast of system information, MIB/SIB,
• receiving RAN-based notification area (RNA) updates,
• reading a paging channel during a paging occasion, PO,
• reading a PDCCH monitoring occasion, MO,
• receiving or transmitting according to a semi-persistent scheduling, SPS,
• transmitting on a configured grant, CG,
« performing a measurement, e.g. SMTC or DMTC or mobility measurements,
• performing a random access, RACH,
• transmitting on a scheduled grant, PUSCH,
• transmitting any control information, e.g. via PUCCH,
• receiving scheduled data, PDCCH or PDSCH,
• transmitting on a sidelink interface using any sidelink physical channel, e.g.
PSSCH/PSCCH/PSFCH via PC5.
9. The UE of any one of the preceding claims, wherein the connections are ranked or prioritized, and wherein the UE is to signal to the network entity only information about operation occasions associated with the other connections having a rank or priority that is the same or higher than the rank or priority of the current connection.
10. The UE of claim 9, wherein the rank or priority of a connection may be decided or determined by the UE, or by a network entity, or by an over-the-top, OTT, application.
11. The UE of any one of the preceding claims, wherein the UE is to switch from the current connection, which becomes an old current connection, to one of the other connections, which becomes a new current connection, so as to signal to a network entity, to which it is connected with the new current connection to which the UE switched, information about the one or more or all operation occasions associated with the old current connection and/or one or more or all of the remaining connections.
12. The UE of any one of the preceding claims, wherein the network entities, to/from which the UE is to transmit/receive using the respective connections, belong to the same mobile network operator, MNO, or to different mobile network operators, MNOs.
13. The UE of any one of the preceding claims, wherein the connections are in the same state or are in different states, the states including, for example, one or more of: • an RRC_CONNECTED state,
• an RRCJNACTIVE state, and
• an IDLE state.
14. The UE of any one of the preceding claims, wherein the UE is to be configured or preconfigured to use the at least two connections by the one or more wireless communication systems or by one or more of the network entities, like a gNB or another UE, by an application, APP, running on the UE or over-the-top, OTT.
15. A network entity for a wireless communication system, wherein
the network entity is to be connected to a UE in the wireless communication system, the UE sharing at least one of its transceiver chains with at least two connections to one or more wireless communication systems, wherein the UE is to perform one or more operations on the connections at respective operation occasions, and wherein the UE is transmitting/receiving to/from the network entity on a current one of the connections,
wherein the network entity is to receive
• from the UE information about the one or more or all operation occasions associated with one or more or all of the other connections, and/or
• from the UE or from one or more other network entities an indication of the operation occasions on one or some or all the connections, and/or
• respective unique identifications of the connections, and
wherein, responsive to the information and/or the indication and/or the unique identifications, the network entity is to
• determine periods during which the UE is not available for the network entity, or
• calculate or recalculate one or more operation occasions associated with the current connection to avoid clashes or overlaps or collisions with the operation occasions associated with the remaining connections.
16. The network entity of claim 15, wherein the network entity is to extend a timer for declaring a radio link failure, RLF, at least by a duration of an period during which the UE is not available, or by a duration of operation occasions associated with the other connections.
17. The network entity of claim 15 or 16, wherein the network entity is not to schedule data for the UE while a duration of a period during which the UE is not available, or while a duration of operation occasions associated with the other connections.
18. A user device, UE, for one or more wireless communication system, the UE comprising:
one or more transceiver chains,
wherein the UE is to share at least one transceiver chain with at least two connections to the one or more wireless communication systems,
wherein the UE is to is to be connected to one or more network entities, like a gNB or another UE, with the connections, and to perform one or more operations on the connections at respective operation occasions,
wherein, when the UE is to transmit or receive on a current one of the connections, the UE is not to transmit or receive on the other connections, and
wherein, when the UE tunes away from an operation on the current connection to perform an operation on another one of the at least two connections, the UE is to signal a tune away signal, TAS, to the network entity, to which it is connected with the current connection.
19. The UE of claim 18, wherein the operation on the other one of the at least two connections includes one or more of the following
reading a broadcast of system information, MIB/SIB,
• receiving RAN-based notification area (RNA) updates,
• reading a paging channel during a paging occasion, PO,
• reading a PDCCH monitoring occasion, MO,
• receiving or transmitting according to a semi-persistent scheduling, SPS,
• transmitting on a configured grant, CG,
• performing a measurement, e.g. SMTC or DMTC or mobility measurements,
• performing a random access, RACH,
• transmitting on a scheduled grant, PUSCH,
• transmitting any control information, e.g. via PUCCH,
• receiving scheduled data, PDCCH or PDSCH,
• transmitting on a sidelink interface using any sidelink physical channel, e.g.
PSSCH/PSCCH/PSFCH via PC5.
20. The UE of claim 18 or 19, wherein the resources for the TAS are preconfigured and the UE is to receive them in an RRC configuration/reconfiguration message, or the resources for the TAS are dynamically assigned as a part of a resource assignment during an RRC_CONNECTED state.
21. The UE of any one of claims 18 to 20, wherein the TAS includes an indication of the operation the UE tunes to and/or a time the UE is tuned away from the operation on the current connection.
22. The UE of any of claims 18 to 21, wherein, responsive to an indication that the operation on the other connection, to which the UE tuned away, takes more time, e.g., more time than the predefined amount of time, the UE is to inform the network entity of the current connection that the tune away duration is longer than a tune away duration defined for the TAS, e.g., by:
• signaling a long tune away signal, Long TAS, to the network entity of the current connection, e.g., in case the indication is provided at the time of tuning away, or
« signaling a TAS update to the network entity of the current connection, e.g., in case the indication is provided at some time while the UE is tuned away.
23. The UE of claim 22, wherein the operation taking more time includes one or more of the following
• receiving a call in a paging occasion, PO,
• receiving an indication that data is to be received, :
e receiving an indication that a high priority operation is to be performed.
24. The UE of any one claims 18 to 23, wherein the connections are in the same state or are in different states, the states including, for example, one or more of:
• an RRC_CONNECTED state,
e an RRCJNACTIVE state, and
« an IDLE state.
25. The UE of any one of claims 18 to 24, wherein, when tuning away, the current connection transitions to the RRCJNACTIVE state.
26. A network entity for a wireless communication system, wherein
the network entity is to be connected to a UE in the wireless communication system, the UE sharing at least one of its transceiver chains with at least two connections to one or more wireless communication systems, wherein the UE is to perform one or more operations on the connections at respective operation occasions, and wherein the UE is transmitting/receiving to/from the network entity on a current one of the connections, and
the network entity is to receive a tune away signal, TAS, from the UE, the TAS indicating to the network entity that the UE tunes away from an operation on the current connection that is served by the network entity to perform an operation on another connection that is served by another network entity.
27. A network entity for a wireless communication system, wherein
the network entity is to be connected to a UE in the wireless communication system, the UE sharing at least one of its transceiver chains with at least two connections to one or more wireless communication systems, wherein the UE is to perform one or more operations on the connections at respective operation occasions, and wherein the UE is transmitting/receiving to/from the network entity on a current one of the connections,
the network entity is aware of the one or more operation occasions associated with one or more or all of the other connections, and
using the knowledge about the one or more operation occasions, the network entity is to
determine the UE tuning away from an operation on the current connection that is served by the network entity to perform an operation on another connection that is served by another network entity, and
• start a timer or put the current connection into a hold condition so as to avoid an error situation for the network entity.
28. A network entity for a wireless communication system, wherein
the network entity is to be connected to a UE in the wireless communication system, the UE sharing at least one of its transceiver chains with at least two connections to one or more wireless communication systems, wherein the UE is to perform one or more operations on the connections at respective operation occasions, and wherein the UE is transmitting/receiving to/from the network entity on a current one of the connections,
the network entity is to receive one or more tune away signals, TASs, from the UE, the TAS indicating to the network entity that the UE tunes away from an operation on the current connection that is served by the network entity to perform an operation on another connection that is served by another network entity, and
responsive to the TAS, the network entity is to start a timer or to put the current connection into a hold condition so as to avoid an error situation for the network entity.
29. The network entity of claim 27 or 28, wherein a range of the timer includes a switching time across the connections plus and the time for performing the operation, like the time for processing data.
30. The network entity of any one of claims 27 to 29, wherein the length of the timer depends on one or more of the UE capabilities, and a time required to perform the one or more operations, like cell selection/reselection, paging, system information and tracking/routing area update, SPS transmissions, CG transmissions, measurements.
31. The network entity of any one of claims 27 to 30, wherein the network entity is not to schedule any data for the current connection during the length of the timer.
32. The network entity of any one of claims 27 to 31, wherein, in the HOLD condition,
• a context of the current connection is maintained, and/or
• a reuse of the resources assigned to the current connection is allowed, and/or
• the network entity does not expect any configured UL transmissions from the current connection, such as PUCCH, PUSCH or CG, and/or
• extent or delay the start of the RLF timer at least by the duration of the HOLD condition.
33. The network entity of any one of claims 27 to 32, wherein the network entity is to start a timer and to put the current connection into the hold condition, and wherein the network entity is to keep the current connection in the hold condition for the time duration of the timer.
34. The network entity of any one of claims 27 to 33, wherein, at the expiry of the timer,
• the network entity is to continue scheduling to the current connection and is to expect configured UL transmissions from the current connection, such as PUCCH and CG, or
• the network entity is to receive form the UE a signal e.g., the tune away signal, that the UE returned from the tune away state, and, responsive to the signal, the network entity is to continue scheduling to the current connection, or
• the network entity is to start a further timer that defines a period over which the network entity maintains the context of the current connection.
35. The network entity of any one of claims 27 to 34, wherein, at the expiry of the timer, the network entity is to start a further timer that defines a period over which the network entity maintains the context of the current connection.
36. The network entity of claim 35, wherein, at the expiry of the further timer, the network entity is to declare a radio link failure, RLF, and continue to RLF recovery procedures.
37. The network entity of any one of claims 27 to 36, wherein the network entity is to receive from the UE an information that the tune away duration is longer than a tune away duration defined for the TAS, e.g.,
• a long tune away signal, Long TAS, e.g., in case the indication is provided at the time of tuning away, or
• a TAS update, e.g., in case the indication is provided at some time while the UE is tuned away.
38. The network entity of claim 37, wherein
responsive to the long tune away signal or the TAS update within the timer,
• in case the network entity is only to start the timer, the network entity is to stop the timer,
• in case the network entity is only to put the current connection into the hold condition, the network entity is remove the hold condition,
• in case the network entity is to start the timer and to put the current connection into the hold condition, the network entity is to stop the timer and remove the hold condition, and
responsive to the long tune away signal or the TAS update within the further timer, the network entity is to stop the further timer and remove the hold condition.
39. The network entity of claim 37 or 38, wherein
responsive to the TAS, in case of a predefined situation, e.g., the delivery of an important message by the network entity over the current connection, the network entity is to tell the UE that the tune away is to be deferred, e.g., by signaling to the UE a delta-timer, or
responsive to the long tune away signal or to the TAS update, in case of a predefined situation, e.g., the delivery an important message by the network entity over the current connection, the network entity is to tell the UE that an extension of the tune away is to be deferred, e.g., by signaling to the UE a delta-timer.
40. The network entity of any one of claims 27 to 39, wherein, when tuning away, the current connection transitions to the RRCJNACTIVE state.
41. The UE of any one claims 18 to 40, wherein the connections are in the same state or are in different states, the states including, for example, one or more of:
• an RRC_CONNECTED state,
• an RRCJNACTIVE state, and
• an IDLE state.
42. A wireless communication system, comprising:
one or more UEs, and
one or more network entities,
wherein one or more of the UEs comprises a UE of any one of claims 1 to 14 and 18 to 25, and/or
wherein one or more network entities comprises a network entity of any one of claims 15 to 17 and 26 to 41.
43. The wireless communication system of claim 42, wherein
the UE comprises one or more of a mobile terminal, or stationary terminal, or cellular loT-UE, or vehicular UE, or vehicular group leader (GL) UE, an loT or narrowband loT, NB-loT, device, or a ground based vehicle, or an aerial vehicle, or a drone, or a moving base station, or road side unit, or a building, or any other item or device provided with network connectivity enabling the item/device to communicate using the wireless communication network, e.g., a sensor or actuator, and/or
the network entity comprises one or more of a macro cell base station, or a small cell base station, or a central unit of a base station, or a distributed unit of a base station, or a road side unit, or a UE, or a group leader (GL), or a relay, or a remote radio head, or an AMF, or an SMF, or a core network entity, or mobile edge computing entity, or a network slice as in the NR or 5G core context, or any transmission/reception point, TRP, enabling an item or a device to communicate using the wireless communication network, the item or device being provided with network connectivity to communicate using the wireless communication network.
44. A method for operating one or more wireless communication systems,
wherein the one or more wireless communication systems comprise one or more user devices, UEs, and one or more network entities, like a gNB or another UE,
wherein one or more of the UE include one or more transceiver chains, shares at least one transceiver chain with at least two connections to the one or more wireless communication systems, and is connected to one or more network entities, like a gNB
or another UE, with the connections for performing one or more operations on the connections at respective operation occasions, and
wherein the method comprises:
transmitting or receiving, by the UE, on a current one of the connections, while not transmitting or receiving on the other connections,
receiving, at a network entity,
• from a UE information about the one or more or all operation occasions associated with one or more or all of the other connections, and/or
• from a UE or from one or more other network entities an indication of the operation occasions on one or some or all the connections, and/or
• respective unique identifications of the connections, and
responsive to the information and/or the indication and/or the unique identifications,
• determining periods during which the UE is not available for the network entity, or
• calculating or recalculating one or more operation occasions associated with the current connection to avoid clashes or overlaps or collisions with the operation occasions associated with the remaining connections.
45. A method for operating one or more wireless communication systems,
wherein the one or more wireless communication systems comprise one or more user devices, UEs, and one or more network entities, like a gNB or another UE,
wherein one or more of the UE include one or more transceiver chains, shares at least one transceiver chain with at least two connections to the one or more wireless communication systems, and is connected to one or more network entities, like a gNB or another UE, with the connections for performing one or more operations on the connections at respective operation occasions, and
wherein the method comprises:
transmitting or receiving, by the UE, on a current one of the connections, while not transmitting or receiving on the other connections,
responsive to the UE tuning away from an operation on the current connection to perform an operation on another one of the at least two connections, providing a tune away signal, TAS, to the network entity, to which the UE is connected with the current connection.
46. A method for operating one or more wireless communication systems,
wherein the one or more wireless communication systems comprise one or more user devices, UEs, and one or more network entities, like a gNB or another UE,
wherein one or more of the UE include one or more transceiver chains, shares at least one transceiver chain with at least two connections to the one or more wireless communication systems, and is connected to one or more network entities, like a gNB or another UE, with the connections for performing one or more operations on the connections at respective operation occasions, the network entity being aware of the one or more operation occasions associated with one or more or all of the other connections, and
wherein the method comprises:
transmitting or receiving, by the UE, on a current one of the connections, while not transmitting or receiving on the other connections,
using the knowledge about the one or more operation occasions, determining a UE tuning away from an operation on the current connection that is served by a network entity to perform an operation on another connection that is served by another network entity, and
starting a timer or putting the current connection into a hold condition so as to avoid an error situation for the network entity.
47. A method for operating one or more wireless communication systems,
wherein the one or more wireless communication systems comprise one or more user devices, UEs, and one or more network entities, like a gNB or another UE,
wherein one or more of the UE include one or more transceiver chains, shares at least one transceiver chain with at least two connections to the one or more wireless communication systems, and is connected to one or more network entities, like a gNB or another UE, with the connections for performing one or more operations on the connections at respective operation occasions, and
wherein the method comprises:
transmitting or receiving, by the UE, on a current one of the connections, while not transmitting or receiving on the other connections, and
receiving, at a the network entity, one or more tune away signals, TASs, the TAS indicating to the network entity that the UE tunes away from an operation on the current connection that is served by the network entity to perform an operation on another connection that is served by another network entity, and
responsive to the TAS, starting, by the network entity, a timer or putting the current connection into a hold condition, by the network entity, so as to avoid an error situation for the network entity.
48. A computer program product comprising instructions which, when the program is executed by a computer, causes the computer to carry out one or more methods in accordance with one of claims 44 to 47.
| # | Name | Date |
|---|---|---|
| 1 | 202217006982-STATEMENT OF UNDERTAKING (FORM 3) [09-02-2022(online)].pdf | 2022-02-09 |
| 2 | 202217006982-REQUEST FOR EXAMINATION (FORM-18) [09-02-2022(online)].pdf | 2022-02-09 |
| 3 | 202217006982-NOTIFICATION OF INT. APPLN. NO. & FILING DATE (PCT-RO-105-PCT Pamphlet) [09-02-2022(online)].pdf | 2022-02-09 |
| 4 | 202217006982-FORM 18 [09-02-2022(online)].pdf | 2022-02-09 |
| 5 | 202217006982-FORM 1 [09-02-2022(online)].pdf | 2022-02-09 |
| 6 | 202217006982-DRAWINGS [09-02-2022(online)].pdf | 2022-02-09 |
| 7 | 202217006982-DECLARATION OF INVENTORSHIP (FORM 5) [09-02-2022(online)].pdf | 2022-02-09 |
| 8 | 202217006982-COMPLETE SPECIFICATION [09-02-2022(online)].pdf | 2022-02-09 |
| 9 | 202217006982.pdf | 2022-02-10 |
| 10 | 202217006982-FORM-26 [12-04-2022(online)].pdf | 2022-04-12 |
| 11 | 202217006982-Proof of Right [11-05-2022(online)].pdf | 2022-05-11 |
| 12 | 202217006982-FORM 3 [06-07-2022(online)].pdf | 2022-07-06 |
| 13 | 202217006982-FER.pdf | 2022-07-26 |
| 14 | 202217006982-FORM 3 [25-11-2022(online)].pdf | 2022-11-25 |
| 15 | 202217006982-RELEVANT DOCUMENTS [21-12-2022(online)].pdf | 2022-12-21 |
| 16 | 202217006982-POA [21-12-2022(online)].pdf | 2022-12-21 |
| 17 | 202217006982-PA [21-12-2022(online)].pdf | 2022-12-21 |
| 18 | 202217006982-FORM 13 [21-12-2022(online)].pdf | 2022-12-21 |
| 19 | 202217006982-ASSIGNMENT DOCUMENTS [21-12-2022(online)].pdf | 2022-12-21 |
| 20 | 202217006982-8(i)-Substitution-Change Of Applicant - Form 6 [21-12-2022(online)].pdf | 2022-12-21 |
| 21 | 202217006982-FORM 4(ii) [20-01-2023(online)].pdf | 2023-01-20 |
| 22 | 202217006982-PETITION UNDER RULE 137 [22-02-2023(online)].pdf | 2023-02-22 |
| 23 | 202217006982-OTHERS [23-02-2023(online)].pdf | 2023-02-23 |
| 24 | 202217006982-Information under section 8(2) [23-02-2023(online)].pdf | 2023-02-23 |
| 25 | 202217006982-FORM 3 [23-02-2023(online)].pdf | 2023-02-23 |
| 26 | 202217006982-FER_SER_REPLY [23-02-2023(online)].pdf | 2023-02-23 |
| 27 | 202217006982-ENDORSEMENT BY INVENTORS [23-02-2023(online)].pdf | 2023-02-23 |
| 28 | 202217006982-DRAWING [23-02-2023(online)].pdf | 2023-02-23 |
| 29 | 202217006982-CLAIMS [23-02-2023(online)].pdf | 2023-02-23 |
| 30 | 202217006982-ABSTRACT [23-02-2023(online)].pdf | 2023-02-23 |
| 31 | 202217006982-PatentCertificate03-03-2025.pdf | 2025-03-03 |
| 32 | 202217006982-IntimationOfGrant03-03-2025.pdf | 2025-03-03 |
| 1 | SearchHistory(12)E_26-07-2022.pdf |