Methods, readers and device for handling data transmission in a communications system

Abstract

A method is performed by a device (903) for handling a data transmission in a communications system. The method comprises initiating (1001) a data transmission related to a procedure to a first reader (901a). The data transmission is associated with a transaction / service identity, ID. The method comprises performing (1003) an offloading process which comprises stopping the procedure with the first reader and continuing the procedure with a second reader (901b). The method comprises providing (1004) a remaining portion of the data transmission to the second reader. The remaining portion of the data transmission provided to the second reader is associated with the same transaction / service ID as the data transmission that was initiated to the first reader.

Description

[0001] METHODS, READERS AND DEVICE FOR HANDLING DATA TRANSMISSION IN A COMMUNICATIONS SYSTEM

[0002] TECHNICAL FIELD

[0003] The present disclosure relates generally to a device, a method performed by the device, a first reader, a method performed by the first reader, a second reader and a method performed by the second reader. More particularly, the present disclosure relates to handling data transmission in a communications system.

[0004] BACKGROUND

[0005] 3GPP Ambient-loT

[0006] In the 3rdgeneration partnership project (3GPP), a study on zero energy internet of things (ZE-loT) was started in Release 18, and is referred to as ‘Ambient loT’ in 3GPP. It was agreed to continue with work to specify a limited solution:

[0007] • Indoor inventory, indoor command only.

[0008] • Backscattering Device Type 1 only.

[0009] • D1T1-B, e.g. micro BS indoor; device indoor, only.

[0010] • CW outside topology

[0011] • R2D in DL spectrum; D2R and CW in UL spectrum

[0012] That is, the only services supported in Release 19 are ‘inventory’, e.g. reporting of device identified to the network, and ‘command’, e.g. transmitting a small payload to the device. Further, the deployment scenario supported are indoor devices which receive Carrier Wave (CW) transmissions for network nodes and the reflected signals are received by indoor micro base stations, e.g. in frequency division duplex (FDD) uplink spectrum. For downlink, direct transmission from the indoor micro base station to the device is supported, e.g. in FDD downlink spectrum. This is illustrated in FIG. 1. FIG. 1 illustrates a carrier wave transmitter, a reader, e.g. gNB, and a passive tag in an indoor location. FIG. 1 illustrates both uplink (UL) and downlink (DL) signaling.

[0013] Functional and protocol simplifications for Ambient loT

[0014] For ambient internet of things (A-loT), 3GPP will target an loT segment well below the existing cellular loT technologies, e.g. narrowband internet of things (NB-loT), with significantly lower energy consumption and device complexity / cost. This requiressimplifications in physical layer design, and the higher layer (L2 / L3) design will also be much more lightweight with a minimal set of functionalities. For random access and multiple access devices the Release 19 scope is limited to the following:

[0015] • A-loT Random access, including re-access for failure handling. Contention-based and contention-free cases are supported. For the contention-based random access, only Solution 1 (3-step only) is included (unless RAN2 decides to use Solution 3 (unified solution) by RAN2#129).

[0016] Contention-based random access types

[0017] An overview of contention-based random access types is provided in Table 1 below:

[0018] Table 1

[0019]

[0020] FIG. 2 is a flow chart illustrating a 2-step contention-based random access method. The device provides message 1 to the reader in step 201. Message 1 (Msg1) comprises a contention resolution (CR) identity / identifier (ID) and data, e.g. device ID. The reader provides message 2 (Msg2) to the device in step 202. Message 2 comprises the CR ID.

[0021] FIG. 3 is a flow chart illustrating a 3-step and 4-step contention-based random access method or procedure. The device provides message 1 to the reader in step 301.

[0022] Message 1 comprises a CR ID. The reader provides message 2 to the device in step 302. Message 2 comprises a CR ID echo. The device 303 provides message 3 to the reader in step 303. Message 3 comprises data, e.g. device ID. The reader provides message 4 to the device in step 304. Message 4 comprises feedback.

[0023] There currently exist certain challenge(s).

[0024] The A-loT device connected with a reader for ongoing inventory procedure or related transmissions may incur transmissions losses and this may be attributed due to reasons, such as:

[0025] • Channel conditions with existing reader are bad.

[0026] • Device energy is draining with current reader, e.g. high path loss, poor channel conditions.

[0027] • Large charging time with current reader.

[0028] • Readers are mobile, e.g., one reader moves out of the coverage area and it is replaced by another reader.

[0029] • Device is moving, e.g., asset tracking use cases, and needs to connect to the network via another reader.

[0030] If the above failure conditions are temporary, it is wise to maintain connection with the existing reader and network / device should strive to improve connection parameters, for instance:

[0031] • Select better modulation and coding scheme (MCS) or perform link adaptation. In the RAN1#118 meeting on the A-loT study item (SI), the following agreement was made:

[0032] —start of agreement—For D2R scheduling, the following information potentially can be explicitly / implicitly indicated to the device via corresponding PRDCH:

[0033] Time domain resources

[0034] Frequency domain resources

[0035] MCS-like information

[0036] Chip duration

[0037] ID associated with device(s)

[0038] Repetitions

[0039] FFS: other information

[0040] FFS: For each information, whether higher-layer signaling and / or L1 R2D control signaling is used

[0041] —end of agreement—

[0042] • Allow device to harvest and retransmit with higher power, etc.

[0043] However, it is not always suitable to continue connecting with the current reader as failure conditions may persist for long and cannot not be improved for a certain time period, for instance:

[0044] • Persistent shadow fade, which means channels can remain bad with existing reader for considerable amount of time.

[0045] • The current reader is loaded or prioritizing other traffic.

[0046] In addition, Release (Rel) 20 focuses on outdoor macro gNB / base station deployment along device type 2 (higher complexity), which provides much larger coverage for devices and also the possibility to select the reader from the potential list as device type 2 is an active type of device which can be expected to perform offloading unlike passive devices in addition to device type 1. The proposal for workplan for Rel 20 is as follows:

[0047] • Includes D2T2

[0048] • Includes Device 2

[0049] • A limited number of additional use cases, deployments, connectivity topologies, devices, traffic types in TR38.848 as a starting point

[0050] • Note: work on D2T2, device 2 shall follow the Rel-19 study conclusions, and further down-selection of architecture options for topology 2 may be needed. For indoor use cases, deviations from Rel-19 study conclusion shall be well justified and agreed.Details to be discussed at a later RAN plenary meeting, including the need for study phase.

[0051] SUMMARY

[0052] An objective is to address at least one of the abovementioned challenges / issues and to provide improved handling of data transmissions in a communications system.

[0053] A first aspect provides embodiments of a method performed by a device for handling a data transmission in a communications system. The device initiates a data transmission related to a procedure to a first reader. The data transmission is associated with a transaction / service ID. The device performs an offloading process which comprises stopping the procedure with the first reader and continuing with the procedure with a second reader. The device provides a remaining portion of the data transmission to the second reader. The remaining portion of the data transmission provided to the second reader is associated with the same transaction / service ID as the data transmission that was initiated to the first reader.

[0054] Corresponding embodiments of device are also provided.

[0055] A second aspect provides embodiments of a method performed by a first reader for handling a data transmission in a communications system. The first reader obtains an initial portion of a data transmission related to a procedure from a device. The initial portion of the data transmission is associated with a transaction / service ID. The first reader coordinates an offloading process with a second reader and / or the device. The offloading process comprises that the device stops its procedure with the first reader and continues the procedure with the second reader for providing a remaining poertion of the data transmission to the second reader. The remaining portion of the data transmission provided to the second reader is associated with the same transaction / service ID as the initial portion of the data transmission that was obtained by the first reader.

[0056] Corresponding embodiments of a first reader are also provided.

[0057] A third aspect provides embodiments of a method performed by a second reader for handling a data transmission in a communications system. The second readercoordinates an offloading process with a first reader and / or a device. The offloading process comprises that the device stops a procedure with the first reader after having initiated a data transmission related to the procedure to the first reader and continues the procedure with the second reader. The second reader obtains a remaining portion of the data transmission from the device. The remaining portion of the data transmission obtained from the device is associated with the same transaction / service ID as the data transmission that was initiated to the first reader.

[0058] Corresponding embodiments of a second reader are also provided.

[0059] Thanks to the offloading process the handling of data transmissions in a communications system may be improved.

[0060] Certain embodiments may provide one or more of the following technical advantage(s). An advantage of at least some embodiments is that devices does not need to perform re-access or reinitiate an inventory procedure from scratch. This saves energy (which may be quite critical due to device being ambient in nature), and resources. Another advantage of at least some embodiments is that a reader does not need to do contention resolution again, as the offloaded device can be addressed directly using a coordinated access stratum identity (AS ID) of the device. This prevents collisions as CBRA is bypassed, and results in saving energy and resources.

[0061] The present disclosure is not limited to the features and advantages mentioned above. A person skilled in the art will recognize additional features and advantages upon reading the following detailed description.

[0062] BRIEF DESCRIPTION OF THE DRAWINGS

[0063] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0064] FIG. 1 is a schematic drawing illustrating communication between a carrier wave transmitter, a passive tag, and a reader.

[0065] FIG. 2 is a flow chart illustrating a method.FIG. 3 is a flow chart illustrating a method.

[0066] FIG. 4 is a schematic drawing illustrating a communications system.

[0067] FIG. 5 is a schematic drawing illustrating a communications system.

[0068] FIG. 6 is a schematic drawing illustrating a communications system.

[0069] FIG. 7 is a schematic drawing illustrating a communications system.

[0070] FIG. 8 is a schematic drawing illustrating a communications system.

[0071] FIG. 9 is a schematic drawing illustrating a communications system.

[0072] FIG. 10 is a signaling diagram illustrating a method.

[0073] FIG. 11 is a signaling diagram illustrating a method.

[0074] FIG. 12 is a flow chart illustrating a method.

[0075] FIG. 13 is a schematic block diagram illustrating a device.

[0076] FIG. 14 is a flow chart illustrating a method.

[0077] FIG. 15 is a schematic block diagram illustrating a first reader.

[0078] FIG. 16 is a flow chart illustrating a method.

[0079] FIG. 17 is a schematic block diagram illustrating a second reader.

[0080] Fig. 18 is an example of a communication system.

[0081] Fig. 19 is an example of a communication system.

[0082] Fig. 20 shows a wireless device

[0083] Fig. 21 shows a network node.

[0084] Fig. 22 is a block diagram illustrating a virtualization environment

[0085] The drawings are not necessarily to scale, and the dimensions of certain features may have been exaggerated for the sake of clarity. Emphasis is instead placed upon illustrating the principle.

[0086] DETAILED DESCRIPTION

[0087] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges.

[0088] Some embodiments relate to a scenario where an inventory procedure for a given device is initiated by a reader and is offloaded to another reader for its inventory completion.

[0089] Some embodiments relate to a method, where a device which is performing inventory related transmissions over a CBRA or CFRA occasion where the occasion allocated by apaging message from the reader associated with a transaction ID (e.g. comprised in paging message as well) terminates the inventory procedure with the current reader and is offloaded to new reader for its inventory related transmissions associated with same transaction ID.

[0090] For instance, if a given device performing a read command, where it is reporting all contents of a user memory, and only 20% of the user memory is reported to a core network (CN) or application function (AF) via the current reader, and for some reason, if the device cannot continue with the current reader, it offloads to new reader and aims to report remaining 80% of the user memory to the CN / AF via the new reader. The offloading from the current reader to the new reader may use a temporary access stratum ID (tempASJD), where both of the readers address the device with this ID in order to perform offloading.

[0091] Under some conditions, it may be beneficial for the device to look for a new reader if the communication link gets worse with the current reader. Hence, it is explored herein, a solution for the problem for a device looking to offload itself to a new reader when undergoing an inventory procedure forced by inventory related transmissions failure with the current reader.

[0092] FIG. 4 depicts a non-limiting example of a communications system 100, which may be a wireless communications system, sometimes also referred to as a wireless communications network, cellular radio system, or cellular network, in which the present disclosure may be implemented. The communications system 100 may be a 5G system, 5G network, NR-U or Next Generation system or network. The communications system 100 may alternatively be a younger system or older system than a 5G system, such as e.g. a 2G system, a 3G system, a 4G system, a 6G system a 7G system etc. The communications system 100 may support other technologies such as, for example, Long-Term Evolution (LTE), LTE-Advanced / LTE-Advanced Pro, e.g. LTE Frequency Division Duplex (FDD), LTE Time Division Duplex (TDD), LTE Half-Duplex Frequency Division Duplex (HD-FDD), LTE operating in an unlicensed band, NB-loT. Thus, although terminology from 5G / NR and LTE may be used in this disclosure to exemplify, this should not be seen as limiting to only the aforementioned systems.The communications system 100 comprises one or a plurality of network nodes, whereof a first network node 101a and a second network node 101b are depicted in the nonlimiting example of FIG. 4. Any of the first network node 101a, and the second network node 101b may be a radio network node, such as a radio base station, or any other network node with similar features capable of serving a user equipment, such as a wireless device or a machine type communication device, in the communications system 100. The first network node 101a may be an eNB and the second network node 101b may be a gNB. The first network node 101a may be a first eNB, and the second network node 101b may be a second eNB. The first network node 101a may be a first gNB, and the second network node 101b may be a second gNB. The first network node 101a may be an eNB and the second network node 101b may be a gNB. Any of the first network node 101a and the second network node 101b may be co-localized, or they may be part of the same network node. The first network node 101a may be referred to as a source node or source network node, whereas the second network node 101b may be referred to as a target node or target network node. When the reference number 101 is used herein without the letters a or b, it refers to a network node in general, i.e. it refers to any of the first network node 101a or second network node 101b.

[0093] The communications system 100 covers a geographical area which may be divided into cell areas, wherein each cell area may be served by a network node, although, one network node may serve one or several cells. In FIG. 4, the communications system 100 comprises a first cell 103a and a second cell 103b. Note that two cells are exemplified in FIG. 4 only as an example, and that any n number of cells may be comprised in the communication system 100, where n is any positive integer. A cell is a geographical area where radio coverage is provided by the network node at a network node site. Each cell is identified by an identity within the local network node area, which is broadcast in the cell. In FIG. 4, first network node 101a serves the first cell 103a, and the second network node 101b serves the second cell 103b. Any of the first network node 101a and the second network node 101b may be of different classes, such as, e.g., macro base station (BS), home BS or pico BS, based on transmission power and thereby also cell size. Any of the first network node 101a and the second network node 101b may be directly connected to one or more core networks, which are not depicted in FIG. 4 for the sake of simplicity. Any of the first network node 101a and the second network node 101n may be a distributed node, such as a virtual node in the cloud, and it may perform itsfunctions entirely on the cloud, or partially, in collaboration with another network node. The first cell 103a may be referred to as a source cell, whereas the second cell 103b may be referred to as a target cell. When the reference number 103 is used herein without the letters a or b, it refers to a cell in general, i.e. it refers to any of the first cell 103a or second cell 103b.

[0094] One or a plurality of UEs 105 is comprised in the communication system 100. Only one UE 105 is exemplified in FIG. 4 for the sake of simplicity. A UE 105 may also be referred to simply as a device. The UE 105, e.g. a LTE UE or a 5G / NR UE, may be a wireless communication device which may also be known as e.g., a wireless device, a mobile terminal, wireless terminal and / or mobile station, a mobile telephone, cellular telephone, or laptop with wireless capability, just to mention some examples. The UE 105 may be a device by which a subscriber may access services offered by an operator’s network and services outside operator’s network to which the operator’s radio access network and core network provide access, e.g. access to the Internet. The UE 105 may be any device, mobile or stationary, enabled to communicate over a radio channel in the communications system 100, for instance but not limited to e.g. UE, mobile phone, smart phone, sensors, meters, vehicles, household appliances, medical appliances, media players, cameras, Machine to Machine (M2M) device, Internet of Things (IOT) device, terminal device, communication device or any type of consumer electronic, for instance but not limited to television, radio, lighting arrangements, tablet computer, laptop or Personal Computer (PC). The UE 105 may be portable, pocket storable, hand held, computer comprised, or vehicle mounted devices, enabled to communicate voice and / or data, via the radio access network, with another entity, such as another UE, a server, a laptop, a Personal Digital Assistant (PDA), or a tablet, Machine-to-Machine (M2M) device, device equipped with a wireless interface, such as a printer or a file storage device, modem, or any other radio network unit capable of communicating over a radio link in the communications system 100.

[0095] The UE 105 is enabled to communicate wirelessly within the communications system 100. The communication may be performed e.g. between two UEs 105, between a UE 105 and a regular telephone, between the UE 105 and a network node, between network nodes, and / or between the UE 105 and a server via the radio access network and possibly one or more core networks and possibly the internet.The first network node 101a may be configured to communicate in the communications system 100 with the UE 105 over a first communication link 108a, e.g., a radio link. The second network node 101b may be configured to communicate in the communications system 100 with the UE 105 over a second communication link 108b, e.g., a radio link. The first network node 101a may be configured to communicate in the communications system 100 with the second network node 101b over a third communication link 108c, e.g., a radio link or a wired link, although communication over more links may be possible. When the reference number 108 is used herein without the letters a, b or c, it refers to a communication link in general, i.e. it refers to any of the first communication link 108a, the second communication link 108b and the third communication link 108c.

[0096] It should be noted that the communication links 108 in the communications system 100 may be of any suitable kind comprising either a wired or wireless link. The link may use any suitable protocol depending on type and level of layer (e.g. as indicated by the Open Systems Interconnection (OSI) model) as understood by the person skilled in the art.

[0097] 3GPP has defined four deployment topologies for A-loT in Rel-18. In the Rel-19 study item (SI), the scope was limited to Topology 1 and 2 and later in the work item (Wl) phase further limited to Topology 1. However, Rel-20 is expected to comprise at least Topology 2 leaving the other topologies for future A-loT studies. The four different topologies are summarized in FIGs. 5, 6, 7 and 8.

[0098] Topology 1: Topology 1 is schematically illustrated in FIG. 5. In FIG. 5, the A-loT device communicates directly with a base station in a bi-directional manner. The communication comprises data A-loT data and / or signaling, as illustrated with the solid arrow in FIG. 5.

[0099] Topology 2: Topology 2 is schematically illustrated in FIG. 6. In FIG. 6, the A-loT device communicates bidirectionally with an intermediate node (IN) which may be a relay, IAB node, UE, repeater, etc. The IN transfers the A-loT data and / or signaling between the base station(BS) and the A-loT device, as illustrated with the dotted and solid arrows in FIG. 6.Topology 3: Topology 3 is schematically illustrated in FIG. 7. In FIG. 7, the A-loT device transmits data / signaling to a base station and receives data / signaling from the assisting node or the other way around, as illustrated with the dotted arrow and the solid arrows in FIG. 7.

[0100] Topology 4: Topology 4 is schematically illustrated in FIG. 8. The A-loT device communicates bidirectionally with a UE. The communication comprises A-loT data and / or signaling, as illustrated with the arrow in FIG. 8.

[0101] In the below embodiments, use cases with ultra-low power devices, zero-energy devices or 3GPP A-loT devices have been considered or assumed.

[0102] The term RAN node is used which may be a network node or a user equipment (UE). Examples of network nodes are NodeB, base station (BS), multi-standard radio (MSR) radio node such as MSR BS, eNodeB, gNodeB, MeNB, SeNB, location measurement unit (LMU), integrated access backhaul (IAB) node, network controller, radio network controller (RNC), base station controller (BSC), relay, IAB, repeater, donor node controlling relay, base transceiver station (BTS), Central Unit (e.g. in a gNB), Distributed Unit (e.g. in a gNB), Baseband Unit, Centralized Baseband, C-RAN, access point (AP), transmission points, transmission nodes, transmission reception point (TRP), RRU, RRH, nodes in distributed antenna system (DAS), core network node (e.g. MCS, MME etc), O&M, OSS, SON, positioning node (e.g. E-SMLC), etc. In particular, in Ambient loT scenario the RAN nodes comprise intermediate node / UE (e.g., relay UE, IAB, repeater etc.) and assisting node / UE (e.g., relay UE, IAB, repeater etc.).

[0103] In particular, in an A-loT scenario, the RAN nodes comprise intermediate node / UE, e.g., relay UE, IAB, repeater etc., and assisting node / UE, e.g., relay UE, IAB, repeater etc.Herein, ‘polling’ ‘, ‘poll’ and ‘paging’, ‘page’, ‘inventory’, ‘query’, ‘interrogate’, is used to represent one or more than one signal transmitted by a network node broadcast wise or specially to a dedicated UE. The purpose of the signal is to facilitate / serve / manage / command one or more than one UE to synchronize to the network node, e.g. downlink / uplink (DL / UL) synchronize to a reference time / frame / symbol, or synchronize to one or more than one signal which the UE receives from the network node, or synchronize based on a pre-defined rule, receive DL data, response and transmit UL data correctly in intended resources. The content of such a signal may be a particular reference signal or a signal carrying control information and / or data. Such a signal may be transmitted periodically or a periodically configured by the network node.

[0104] Herein, ‘A-loT UE’, ‘A-loT device’, ‘device’, or ‘UE’ are used interchangeably without losing the meaning.

[0105] Herein, ‘intermediate node’, ‘intermediate UE’, ‘UE’ are applied interchangeably without losing the meaning.

[0106] During a contention-based access procedure / round, an access occasion for a device starts from the time when the device receives a first DL or reader to device (R2D) signaling indicating the start of the access occasion until the time when the device receives a second DL or R2D signaling indicating the end of the access occasion or the start of the next access occasion.

[0107] The device performs re-access in case of contention resolution failure. The device performs re-access or retransmission in case of data transmission failure. Re-access means that the device accesses and transmits in a different access occasion from the access occasion where the device has experienced failures. Retransmission means that device uses the same or different resources to retransmit the data on the same access occasion in time domain.

[0108] The reader may be gNB, UE or intermediate UE.

[0109] The inventory or inventory procedure may mean the device is engaged or executing:inventory

[0110] command

[0111] inventory plus command.

[0112] Herein, this plurality of classifications may be represented by the single term ‘inventory’.

[0113] The term offloading may be referred to as or may comprise switching, handover, moving etc., and these terms may be used interchangeably herein.

[0114] FIG. 9 is a schematic drawing illustrating a communication system 900. The communication system 900 comprises a first reader 901a, a second reader 90b and a device 903. The first reader 901a may be a first network node. The second reader 901b may be a second network node. The device 903 may be a wireless device. The communications system 900 may comprise other entities, for example at least one of the entities illustrated in FIG. 4, but they are not repeated here for the sake of simplicity. When the term 901 is used herein without the letters a or b, it may refer to any of the first reader 901a and the second reader 901b.

[0115] The first reader 901a and the second reader 901b may be referred to using at least one of the following terms, and these terms may be used interchangeably herein:

[0116] • First reader 901a: Current reader, past reader, old reader, previous reader, R0, R1

[0117] • Second reader 901b: Other reader, new reader, R1, R2

[0118] The device 903 may be referred to as device D1 herein. The device 903 may be comprised in group of devices. The group of device comprises n number of devices, where n is a positive integer. Each device may be named using the reference Dn, where n is a positive integer.

[0119] In some embodiments, the device 903 which is currently engaged with a reader, say reader R1, for its inventory related data transmission for a given transaction / service ID, decides to or is commanded and / or is allowed by the network to terminate the communication link or ongoing inventory procedure with current reader 901a and camps on or connects with another reader, say reader R2, to continue with inventory relateddata transmission associated with the same service / transaction ID where two readers 901a, 901b coordinate to attempt to offload the targeted device 903 by creating a common temporary AS ID for the target device 903. The two readers 901a, 901b may or may not belong to the same topology, i.e., the devices 903 could move from one of the connection topologies described in FIGs. 5, 6, 7, 8 to another. The network or the device may initiate the reader switching / adaptation / offloading process due to but not limited to mobility of the reader, mobility of the A-loT device, link adaptation, offloading the load of the reader.

[0120] An overview of some differences of the present disclosure compared to the prior art is provided in Table 2 below.

[0121] Table 2

[0122]

[0123] FIG. 10 is a signalling diagram illustrating a method. The method comprises at least one of the following steps:

[0124] 1001The device 903, which is currently engaged with or connected to the first reader 901a provides at least one data transmission to the first reader 901a. The first reader 901a obtains the at least one data transmission from the device 903.

[0125] The at least one data transmission may be related to a procedure. The procedure may be an inventory procedure, i.e. the data transmission is an inventory related data transmission. The procedure may mean that the device 901 is engaged or executing at least one of the following:

[0126] • Inventory

[0127] • Command

[0128] • Inventory plus command.

[0129] The at least one data transmission provided in step 1001 may be a first data transmission.

[0130] The data transmission is associated with a transaction / service identity (ID).

[0131] Step 1002

[0132] The device 903 connects to or engages with a second reader 901b. The connection or engagement may be done using any suitable method for connection or engagement. After the device 903 has connected to or engaged with the second reader 901b, the connection or engagement with the first reader 901a may continue or it may be ended, e.g. disconnected.

[0133] Step 1003

[0134] An offloading process may be performed. The offloading process may be initiated by at least one of the device 903 and the first reader 901a. The offloading process may comprise stopping the procedure with the first reader 901a and continuing with the remaining data transmission of the procedure with the second reader 901 b.

[0135] Step 1004

[0136] The device 903 provides the remaining part or second part of the procedure’s data transmission to the second reader 901b. The remaining part of the data transmission may be a second data transmission. The remaining part of the procedure’s datatransmission that is provided to the second reader 901b, i.e. offloaded to the second reader 901b, is associated with the same transaction / service ID as the data transmission that was provided to the first reader 901a. Thus, the data transmission in step 1001 is associated with the same transaction / service ID as the remaining part of the data transmission that is provided in step 1004.

[0137] Data transmission that does not have the same transaction / service ID as the ones provided in step 1001 may continue to be provided to the first reader 901a, or it may be stopped or discarded, or it may be provided to the second reader 901b.

[0138] In order to offload the device 903 from one reader 901a to another reader 901b, a coordination may be performed among readers 901a, 901b, and an exemplary behavior of such coordination is listed below. In the list below, the device 903 is referred to as device D1, the first reader 901a is referred to as reader R1 and the second reader 901b is referred to as reader R2.

[0139] Step 0: This step corresponds to step 1003 in FIG. 10. The device D1 may initiate the offloading process with the reader R1, or, the reader R1 may initiate the offloading process for device D1 which is currently participating in an inventory or command or inventory plus command procedure or session. By offloading means, a device 903 may stop an ongoing procedure (such as an inventory procedure) with a current reader, e.g. the first reader 901a, in the midst, and may continue with a new reader, e.g. the second reader 901b.

[0140] Step 1: The reader R1 may promote the device DTs collision resolution ID, e.g. RN16 or X bit random number, to AS ID for inter-reader coordination purpose. The AS ID may be referred to as tempAS_ID_D1.

[0141] Step 2: The reader R1 may communicate ID tempAS_ID_D1 to the reader R2 for offloading. The reader R1 may check if the communicated ID is already in use or not.

[0142] Step 2a-1: If tempAS_ID_D1 is not in use at the reader R2, then the reader R2 may communicate this information to the reader R1. Based on this information, the reader R1 may prepare for device D1 exit. The reader R2 may proceed with, e.g., CFRA basedallocation by directly addressing the device D1 using the ID tempAS_ID_D1. Until this transfer or offloading of device D1 happens successfully, the reader R1 may disallow its device 903 to use the same ID for their AS based identity. The successful access of device D1 by the reader R2 may be indicated by the reader R2 to the reader R1 , after which the reader R1 may use the same ID for its AS purpose.

[0143] Step 2b-1: Following Step 2, if tempAS_ID_D1 is already in use at the reader R2, then it may communicate this information to the reader R1 and possibly suggest a new tempAS_ID_D1 , which is not in use at the reader R2.

[0144] Step 2b-2: If the same ID is not in use by the reader R1, then the reader R1 may:

[0145] • First allocate the suggested ID new tempAS_ID_D1 to device D1,

[0146] • Then, follow the procedure described in Step 2a-1.

[0147] Step 2b-3: Following Step 2b-1, if the new tempAS_ID_D1 suggested by the reader R2 is already in use at the reader R1, then both readers may continue information exchanges until they arrive at an ID suggestion which is not in use at both readers. Afterwards, the reader R2 may continue with procedure described in Step 2b-2.

[0148] Some embodiments are summarized figuratively in FIG. 11, as one example. In FIG. 11, the device 903 is referred to as device D1, the first reader 901a is referred to as reader R1 and the second reader 901b is referred to as reader R2.

[0149] Step 1101

[0150] The reader R1 may provide paging to the device D1. The device D1 may obtain paging from the first reader 901a.

[0151] The reader R1 may send paging to a group of devices for inventory and allocates contention based random access (CBRA) resources. The device D1 may be comprised in the group of devices.

[0152] Step 1102This step corresponds to step 1001 in FIG. 10. The device D1 provides a data transmission to the reader R1. The data transmission may be or may comprise Msg1 to MsgX. The reader R1 obtains the data transmission from the device D1.

[0153] The device D1 may pick one of the CBRA occasions and transmit Msg1 comprising a random ID or RN16. After passing contention, the device D1 may transmit data, say some segments of Msg3.

[0154] Step 1103

[0155] This step corresponds to step 1003 in FIG. 10 and step 1 in the list above. The reader R1 may provide a temporary (temp) AS ID to the device D1. The device D1 may obtain the temp AS ID from the reader R1.

[0156] Steps 1102 and 1103 may be comprised in or related to a CBRA access occasion.

[0157] The reader R1 and / or device D1 may decide to offload device D1 to the new reader R2. For this, the reader R1 may allocate temp AS ID which may be same as RN16, e.g. random ID in Msg1 , or a new ID which may be allocated in Msg2 or other reader to device (R2D) message.

[0158] Step 1104

[0159] This step corresponds to step 1003 in FIG. 10 and step 2 in the list above. The reader R1 may provide device information to the reader R2. The device information may be or may comprise the temp AS ID. The reader R2 may obtain the device information from the reader R1.

[0160] The reader R1 may communicate the temp AS ID to reader R2.

[0161] Step 1105

[0162] This step corresponds to step 1003 in FIG. 10. The reader R2 may provide paging with CRFA to the device D1. The paging with CRFA may be addressed to the device with the temp AS ID. The device D1 may obtain the paging / CRFA from the reader R2.The reader R2 may send paging with CFRA access to the device D1 to follow up on with remaining transmissions in or from device D1.

[0163] Step 1106

[0164] This step corresponds to step 1004 in FIG. 10. The device D1 may provide a data transmission to the reader R2. The data transmission may be or may comprise MsgX+1 to MsgY. The reader R2 may obtain the data transmission from the device D1.

[0165] Steps 1102-1106 may be or may be comprised in an access round or paging round.

[0166] In one embodiment, the entire offloading process of device D1 from the reader R1 to the reader R2 may be transparent to device D1 with respect to reader identities. For instance, in all DL signaling, identity information for the reader R1 or other reader specific signatures may not be included.

[0167] In another embodiment, the device 903 may be aware of changing reader identities especially if a reader-initiated offloading process is implemented, as indicated in embodiments described above. This may be useful in case if the device 903 receives any DL signaling, such as paging trigger from the previous reader, it may ignore those signaling received from the previous reader and monitors any control or trigger messages sent by the new reader.

[0168] In one embodiment, if termination, as described in embodiments above, is initiated by the device D1, then it may send “end of data transmission” indication to the reader R1. The device 903 may then wait for offloading to new reader subsequently in coordination with the old and new readers.

[0169] In one embodiment, the device 903 may indicate a list of potential readers to current reader R1 which it may be offloaded to. The device 903 may create such a list based on at least one of the following characteristics:

[0170] • One or more carrier waves (CW) it receives from potential readers. Here, the underlying assumption may be that the device 903 may identify the reader originating the CW e.g., the CW may comprise a reader ID or signature.

[0171] • Paging message(s) it receives from potential readers.Preambles, or midambles, or postambles or synchronization messages / signaling it receives from potential readers.

[0172] Query-rep like signaling it receives from potential readers.

[0173] In one embodiment, the reader R1 may select any potential reader, e.g., based on a minimal distance with respect to device 903 as a new potential reader for device D1. This may be useful because if the reader R1 is a gNB based node, and when the reader R1 activates an intermediate UE which may be physically located closer to device D1 as compared to the reader R1, then the gNB based reader may initiate an offloading process for device D1 to a nearby intermediate UE based reader.

[0174] In one embodiment, if the termination is reader initiated, the reader, e.g. the first reader 901a, may also forward the control information of the transmitted carrier wave (CW) for device illumination (if any) to the new potential reader, e.g. the second reader 901b. The reader, e.g. the first reader 901a, may choose to continue transmitting the illuminating CW, or delegate the CW transmission to the new reader, e.g. the second reader 901b, or jointly transmit the illuminating CW to the device 903 to accumulate more energy at the device 903 and / or enhance the backscattered signal strength and diversity, e.g. for passive devices. In an alternative embodiment, CW transmission may be agnostic to the reader(s).

[0175] In some embodiments, if the termination is reader initiated, the reader, e.g. the first reader 901a, may also forward the device’s frequency shift (allowable) or current frequent shift frequency in use to the new reader, e.g. the second reader 901b, so the new reader may configure the resources such as frequency shift related, frequency domain with minimal changes at device side which it was using for communication with previous reader, e.g. the first reader 901a.

[0176] In one embodiment, the device 903 may terminate the connection with the first reader 901a due to poor signal strength, which may be because of increased distance, possible obstacles, or increase in interference, after time T has elapsed. This time T may be similar to the hysteresis time used in cellular networks to prevent unnecessary handovers between base stations due to fluctuations in signal strength. Here it mayprevent the unnecessary switching of readers by the devices due to minor fluctuations of signal strength or moving obstacles.

[0177] In one embodiment, the first reader 901a may be congested with too many devices and / or users, the network may offload some devices 903 to a less crowded reader in the vicinity, even if the signal strength is still acceptable. The information exchange on the number of devices 903 served by a reader may be done via the Xn or the llu interface, where the Xn interface is between two base stations acting as readers 901 and the llu interface is between the base station and the intermediate UE acting as a reader 901.

[0178] In another related embodiment, the reader 901 may dynamically shrink or expand the coverage area based on traffic load or the number of devices 903. When the traffic load is high the reader 901 may shrink the coverage area while it expands the coverage area when the traffic load is low. Such changes may also be notified to nearby readers 901, so they may prepare to accept or offload devices 903 from / to reader 901 which had changed its coverage region. In one option, the coverage region may be defined with reference regions, and the reader 901 may indicate the valid coverage area associated with reference region IDs. A reference region ID may be assigned overlapping set of time / frequency / spatial resources.

[0179] In one embodiment, the first reader 901a and the second reader 90b may coordinate to adjust their output powers or coverage area while offloading devices 903 from one of the reader’s coverage edge, e.g. similar to cell edge, say at the first reader 901a, to another reader’s coverage, say at the second reader 901b. The coordination or exchange may occur via Xn interface or via a core network (CN) between readers.

[0180] In one embodiment, the first reader 901a may adopt the offload strategy based on positioning information of the device 903 and the new reader, e.g. the second reader 901b. The procedure is, first the first reader 901a may:

[0181] • find / query / pol I the nearby reader 901 relative to the device’s position via the Xn or the llu interface, or

[0182] • the first reader 901a may query from a database maintained by the network, e.g.

[0183] CN or gNB, or• the first reader 901a may ask the device 903 to provide a list of potential readers, i.e. , the second readers 901b with which the device 903 connected in the past and has maintained its reader ID for future communication, or the second readers 901b from which the device is currently receiving signalling.

[0184] In a related embodiment, when the first reader 901a may receive a list of potential new readers to which the device 903 can be offloaded, the first reader 901a may select the best new reader from it. The criteria for choosing the new best reader 901b may be based on at least one of: proximity, link quality, devices currently inventories / served, or other factors. Upon selecting the new reader 901b, the old reader 901a may request the new reader to modify / increase the coverage area by either moving close to the A-loT device 903, e.g. this may be applicable to network-controlled readers 901 which may be moved on demand basis, or by increasing the transmission power.

[0185] In a sub-embodiment, when a device 903 provides a list of potential new readers 901b to the first reader 901a, the device 903 may identify them by relying on the reader signatures, which refers to a unique radio frequency (RF) fingerprint or identifier associated with each reader, and it may comprise at least one of:

[0186] • Signal Strength Profile - The way a reader’s signal attenuates over distance. • Phase Angle - Variations in phase shift based on the device’s relative position.

[0187] • Frequency Response - The way a reader’s signal propagates in a given environment.

[0188] By leveraging these reader-specific characteristics, network or existing reader may estimate A-loT device location, movement direction, and proximity to different readers to coordinate offloading.

[0189] In one embodiment, the CN may provide the total number of devices 903 to be inventoried along with their IDs. In response to this request the reader 901 may either acknowledge that it had inventoried all the devices 901 , or the reader 901 may acknowledge inventorying a fraction of devices 903, which may be indicated with for example a flag ‘partial inventory success’, or the reader 901 may send a negative acknowledgement if it cannot inventory any of the devices 903 due to an ongoingprocedure. The information related flag or negative acknowledgment may be sent via NGAP to CN.

[0190] In one embodiment, reader 901 may indicate that it cannot inventory the unsuccessful devices anymore for at least one of the following reasons:

[0191] • poor channel with failed devices 903,

[0192] • heavy load and thus failed devices 903 may not be granted resources consistently,

[0193] • prioritization of traffic, for instance, eMBB or other NR traffic over A-IOT traffic.

[0194] In another related embodiment, when the CN may receive the partial inventory success flag along with the device IDs, it may look for another reader 901 in the vicinity to perform the inventory of the devices IDs which are not received with signaling indicating partial inventory success flag. In this manner, the CN may instruct other readers 901 to initiate inventory / command procedure for the prospective devices 903 which may not be completed by the old reader 901, which had indicated ‘partial inventory success’.

[0195] In one embodiment, when the reader 901 sends an inventory report it may comprise the device IDs of the inventoried devices 903 and the partial inventory success flag. The flag may be indicated by explicit or implicit means, e.g., in one case it is sufficient to indicate device IDs and remaining devices IDs which are not comprised in inventory reporting automatically indicate partial inventory success, for example instead of explicit flag. The reason for partial inventory may be to let CN / gNB know that reader 901 was unable to fulfil the request of inventorying remaining device 903, which may be due to the constrained resources, e.g. existing load, priority of other traffic i.e. , NR eMBB, LIRLLC, or the channel condition, and the CN / gNB may look for new reader 901.

[0196] Due to resource constraint, the reader 901 may apply a reader mask on group ID and reduce the group size by itself for inventorying. For instance, the CN may send a 20 bit ID, where the last 5 bits are masked. It may mean that the CN intends to inventory maximum load of 2A5 = 32 devices via this reader. However, due to resource constraint, the reader 901 may apply an additional mask of 2 bits, and only does inventorying 2A(5-2) = 8 devices. The reader 901 may provide the inventory reporting of devices 903 withmax group size of 8 devices, the reader 901 may mask information, which bits may be masked in ID from reader 901, and possibly the flag information.

[0197] In one embodiment, the device 903 may initiate reader switching based on the received signal strength of the CW, and / or some light-weight measurements of received signal received power (RSRP) on the preamble or sync sequencies of DL messages, for example paging, MSG2, MSG4, etc. The threshold for the device 903 to switch the reader 901 may be predefined or hardcoded at the device 903 or based on online measurement comparison of different reader nodes messages.

[0198] In one embodiment, if the device 903 is commanded to report its specific fields or all of USER MEMORY, i.e. , CN / AF sends read command, and with existing reader 901, if the device 903 had sent number of segments correspond to specific part or fields of memory content associated with given service, then upon offloading, the device 903 may send remaining segments to new reader 901 correspond to remaining fields or parts of USER MEMEORY associated with same service.

[0199] In an additional embodiment, similar to above, if a CN / AF triggers a write command associated with given service, and if the device 903 has been written or received some segments of data via current reader 901, and upon offloading to new reader 901, the device 903 may receive remaining segments via new reader 901 from the CN / AF correspond to same service.

[0200] In another embodiment, the reader 901, e.g. the first reader 901a, may decide to initiate a reader switching procedure based on the received signal strength of the device UL PDRCH data. Mobile readers.

[0201] In the below, embodiments are presented for use cases where one or more readers 901 are expected to be, and one reader 901 may serve the devices 903 in a certain area for a certain time duration before another incoming reader replaces the first reader 901a and so on. Readers 901 that are expected to be mobile may be e.g. drones, robots, moving vehicles, etc. serving a certain factory.In one embodiment, the reader RO may be configured or provided with the identities of the one or more potential neighboring readers R1, R2, R3, Rn by the network, n is a non-negative integer and n=0 refers to the serving reader, e.g., in a certain region. In one embodiment, the reader RO may indicate the identities of the one or more potential neighboring readers 901 in addition to its own identity to the devices 903. In one embodiment, a reader RO may indicate the time duration TO until which RO may serve the current set of devices 903 and / or serve a certain region. In one embodiment, a reader R0901 may indicate a set of time durations TO, T1 , T2, ... , Tn until which a set of readers R0, R1, R2, ... , Rn will successively serve the current set of devices and / or successively serve a certain region. The duration TO may correspond to reader R0, duration T 1 may correspond to reader R1 , and so on. The reference time for the time duration(s) {TO, T1, ...} may be relative to the time instant the message comprising the time durations {TO, T1, ...} is received by the device 903. This choice of reference time may also suggest that a reader 901 may need to frequently update the set of values for {TO, T1 , ... , Tn} when it transmits the message comprising the time durations {TO, T1 , ... , Tn}. Alternatively, the reference time may be relative to UTC or the start of a slot / subframe or the end of a slot / subframe, e.g. slot number, subframe number / system frame number / hyper-system frame number, etc. However, if the A-loT devices 903 cannot identify or maintain the start or end of slots / subframes with sufficient accuracy, this solution may be infeasible.

[0202] Example: A reader R0 may broadcast time durations TO and T 1 for readers R0, i.e. the serving reader, and R1, e.g. the incoming reader, as well as the identities of readers R0 and R1. A device 903 may know that the reader R0 may be active for a time duration TO following the instant message comprising the time durations {TO, T1} is received and that the reader R1 may be active for a time duration T 1 following the end of duration TO. These readers 901, for instance, may correspond to two drone-based readers flying over a designated area in a factory, e.g., on a certain trajectory.

[0203] In one embodiment, when a UE-as-a-Reader (IIE-R) is handed over from one gNB to another gNB during an ongoing communication session, e.g. inventory or command round, with A-loT devices 903, then the temporary ID associated with the previous gNB may be changed to that of the current gNB and the IIE-R may communicate thetemporary ID associated with its current gNB to A-loT devices 903 in the ongoing communication session, e.g. inventory or command round.

[0204] In one embodiment, when a UE-R is handed over from one gNB to another gNB during an ongoing communication session, e.g. inventory or command round, with A-loT devices, then even if the temporary ID associated with the previous gNB is changed to that of the current gNB, the IIE-R may not communicate the temporary ID associated with its current gNB to A-loT devices 903 in the ongoing communication session, e.g. inventory or command round. That is, the change of gNB for a IIE-R may be transparent to the A-loT devices 903 in an ongoing communication session and the updated temporary ID may be communicated to the A-loT devices 903 in a future communication session. In a variant of the previous embodiments, the IIE-R may not be expected to communicate the changed temporary ID for a duration X, where X may be specified in the standard or configured by the network.

[0205] In one embodiment, when a IIE-R is handed over from one gNB to another gNB during an ongoing communication session, e.g. inventory or command round, with A-loT devices, then if there is a handover failure and the A-loT communication sessions is terminated, a failure case may be comprised in the failure notification.

[0206] The method described above will now be described seen from the perspective of the device 903. Fig. 12 is a flowchart describing the present method in the device 903 for handling data transmission in a communication system 100, 900. The device 903 may be at least one of or is comprised in at least one of:

[0207] • A-loT;

[0208] • A-loT UE;

[0209] • A-loT device;

[0210] • Wireless device;

[0211] • UE;

[0212] • Intermediate UE; and

[0213] • RFID device.

[0214] The method comprises at least one of the following steps to be performed by the device 903, which steps may be performed in any suitable order than described below:Step 1200

[0215] The device 903 may obtain paging information from the first reader 901a.

[0216] Step 1201

[0217] This step corresponds to step 1001 in FIG. 10 and step 1102 in FIG. 11. The device 903 provides a data transmission related to a procedure to a first reader 901a. The data transmission is associated with a transaction / service ID. The data transmission may be a first data transmission.

[0218] The procedure to which the data transmission is related may be at least one of or may be comprised in at least one of:

[0219] • an inventory procedure;

[0220] • a command procedure; and

[0221] • an inventor and a command procedure.

[0222] Step 1202

[0223] This step may correspond to steps 1002-1003 in FIG. 10 and step 1105 in FIG. 11. The device 903 may determine to perform the offloading process.

[0224] The determining to perform the offloading process may comprise at least one of:

[0225] initiating the offloading process; and

[0226] obtaining information from at least one of the first reader 901a and the second reader 901b to perform the offloading process, i.e. it may be at least one of the first reader 901a and the second reader 901b that initiates the offloading process.

[0227] The offloading process may be determined to be performed when at least one of the following triggers is detected:

[0228] • a transmission failure related to the procedure between the device 903 and the first reader 901a has occurred;

[0229] • a mobility of the first reader 901a;

[0230] • a mobility of the device 903;

[0231] • a link adaptation; and

[0232] • an offloading the load of the first reader 901a.The transmission failure may be an inventory related transmission failure over a CBRA or CFRA occasion.

[0233] Step 1203

[0234] This step may correspond to step 1003 in FIG. 10. The device 903 may provide, to at least one of the first reader 901a and the second reader 901b, information indicating that the device 903 has determined to perform the offload process, e.g. that the device 903 has initiated the offloading process.

[0235] Step 1204

[0236] This step may correspond to step 1003 in FIG. 10 and step 1105 in FIG. 11. The device 903 may obtain, from at least one of the first reader 901a and the second reader 901b, information indicating that at least one of the first reader 901a and the second reader 901b has determined to perform the offloading process, e.g. that at least one of the first reader 901a and the second reader 901b has initiated the offloading process

[0237] Step 1205

[0238] This step may correspond to step 1003 in FIG. 10 and steps 1103 and 1105 in FIG. 11. The device 903 may obtain information indicating a temporary AS ID from at least one of the first reader 901a and the second reader 901b. The temporary AS ID may be used in relation to the data transmission with at least one of the first reader 901a and the second reader 901b.

[0239] Step 1206

[0240] This step corresponds to step 1003 in FIG. 10 and steps 1105-1106 in FIG. 11. The device 903 performs an offloading process by stopping the procedure with the first reader 901a and continuing with the remaining data transmission of the procedure with a second reader 901b. The remaining data transmission is associated with the same transaction / service ID as the data transmission that was performed with the first reader 901a. The remaining data transmission may be a second data transmission.

[0241] The offloading process may be initiated by the device 903 or by at least one of the first reader 901a and the second reader 901b.Using other words, the offloading process may comprise:

[0242] the device 903 stops its ongoing process with the first reader 901a; and

[0243] the device 903 continues with the remaining data transmission of the procedure with the second reader 901b instead of the first reader 901a.

[0244] Step 1207

[0245] This step corresponds to step 1002 in FIG. 10 and step 1105 in FIG. 11. The device 903 may connect to the second reader 901b. Connection to the second reader may be triggered by that the device 903 has initiated the offloading process, or that the device 903 has obtained information from at least one of the first reader 901a and the second reader 901b to perform the offloading process.

[0246] Step 1208

[0247] This step corresponds to step 1004 in FIG. 10 and step 1106 in FIG. 11. The device 903 provides the remaining data transmission to the second reader 901b. The remaining data transmission may be a second data transmission.

[0248] Step 1209

[0249] This step may correspond to step 1003 in FIG. 10. The device 903 may disconnect from the first reader 901a. The disconnection may be done at any suitable time, for example, when the offloading process has started, when the connection to the second reader 901b has been established, when a first part of the remaining data transmission has been successfully provided to the second reader 901b, when all remaining data transmission has been successfully provided to the second reader 901b etc.

[0250] Step 1210

[0251] The device 903 may provide user data, for example to at least one of the first reader 901a and the second reader 901b.

[0252] 1211

[0253] The device 903 may forward the user data to a host via the transmission to at least one of the first reader 901a and the second reader 901b.Fig. 13 is a schematic drawing illustrating the device 903 for handling data transmission in a communication system 100, 900.

[0254] The device 903 may comprise processing circuitry 1301 e.g. one or more processors, configured to perform the methods herein.

[0255] At least one of the device 903 and / or the processing circuitry 1301 is configured to perform the method of FIG. 12.

[0256] At least one of the device 903 and / or the processing circuitry 1301 is arranged to provide a data transmission related to a procedure to a first reader. The data transmission is associated with a transaction / service ID. At least one of the device 903 and / or the processing circuitry 1301 is arranged to perform an offloading process by stopping the procedure with the first reader and continuing with the remaining data transmission of the procedure with a second reader. The remaining data transmission is associated with the same transaction / service ID as the data transmission that was performed with the first reader. At least one of the device 903 and / or the processing circuitry 1301 is arranged to provide the remaining data transmission to the second reader.

[0257] The device 903 further comprises a memory 1305. The memory 1305 comprises one or more units to be used to store data on, such as indications, data transmission, AS ID, offloading information, connection information, transaction / service ID, measurements, thresholds, data related to nodes, and applications to perform the methods disclosed herein when being executed, and similar. Furthermore, the device 903 may comprise a communication interface 1306 such as comprising a transmitter, a receiver, a transceiver and / or one or more antennas.

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

[0259] The device 903 for handling data transmissions in a communications system 100, 900, may comprise:

[0260] • processing circuitry configured to perform any of the operations of the method in FIG. 12; and

[0261] • a power source circuitry configured to supply power to the processing circuitry.

[0262] The device 903 for handling data transmissions in a communications system (100, 900) may comprise:

[0263] • one or more antennas;

[0264] • communication interface connected to the one or more antennas and to processing circuitry;

[0265] • the processing circuitry being configured to perform any of the operations of FIG.

[0266] 12;

[0267] • an input interface connected to the processing circuitry and configured to allow input of information into the device to be processed by the processing circuitry;

[0268] • an output interface connected to the processing circuitry and configured to output information from the device that has been processed by the processing circuitry; and

[0269] • a power source connected to the processing circuitry and configured to supply power to the device.

[0270] The method described above will now be described seen from the perspective of the first reader 901a. Fig. 14 is a flowchart describing the present method in the first reader 901a for handling data transmission in the communications system 100, 900.The first reader 901a may be or may be comprised in at least one of:

[0271] • a network node,

[0272] • an access node,

[0273] • a RAN node,

[0274] • a User Equipment, UE, and

[0275] • an intermediate node.

[0276] The method comprises at least one of the following steps to be performed by the first reader 901a, which steps may be performed in any suitable order than described below:

[0277] Step 1400

[0278] This step may correspond to step 1101 in FIG. 11. The first reader 901a may provide paging information to the device 903.

[0279] Step 1401

[0280] This step may correspond to step 1001 in FIG. 10 and step 1102 in FIG. 11. The first reader 901a obtains a data transmission related to a procedure from a device 903. The data transmission is associated with a transaction / service ID. The data transmission may be a first data transmission.

[0281] Step 1402

[0282] This step may correspond to step 1003 in FIG. 10. The first reader 901a coordinates an offloading process with a second reader 901b. The offloading process comprises that the device 903 stops its procedure with the first reader 901a and continues with the remaining data transmission of the procedure with the second reader 901 b. The remaining data transmission is associated with the same transaction / service ID as the data transmission that was performed with the first reader 901a.

[0283] The offloading process may be initiated by the device 903 or by at least one of the first reader 901a and the second reader 901b.Coordinating of the offloading process comprises that the first reader 901a provides, to the second reader 901b, information indicating to perform the offloading process, e.g. information indicating that it should be started.

[0284] The information indicating to perform the offloading process may comprise a temporary AS ID determined by the first reader 901a. The temporary AS ID may be for example a temporary ID, a temporary UE ID, a first ID, a first temporary ID, a first temporary UE ID, a common ID that is common for the first reader 901a and the second reader 901b etc.

[0285] Step 1403

[0286] This step may correspond to step 1003 in FIG. 10. The first reader 901a may obtain, from the device 903, information indicating that the device 903 has determined to perform the offloading process to be performed, e.g. that the device 903 has initiated the offloading process.

[0287] Step 1404

[0288] This step may correspond to step 1002 in FIG. 10, step 1003 in FIG. 10 and step 1105 in FIG. 11. The first reader 901a may determine to perform the offloading process, e.g. the first reader 901a may be the one that initiates the offloading process.

[0289] Step 1405

[0290] This step may correspond to step 1003 in FIG. 10. The reader 901a may provide, to at least one of the device 903 and the second reader 901b, information indicating to perform the offloading process, e.g. that it is initiated by the first reader 901a.

[0291] Step 1406

[0292] This step may correspond to step 1003 in FIG. 10. The first reader 901 may disconnect the device 903. Thereby, the first reader 901a and the device 903 may not communicate with each other anymore. Disconnecting the device 903 may comprise terminating or pausing the communication link between them.

[0293] Step 1407This step may correspond to step 1003 in FIG. 10. The first reader 901a may obtain, from the second reader 901b information indicating that the temporary AS ID is already in use at the second reader 901b.

[0294] Step 1408

[0295] This step may correspond to step 1003 in FIG. 10. The first reader 901a may determine, together with the second reader 901b, another temporary AS ID to be used instead. The other temporary AS ID is not already used by any of the first reader 901a and the second reader 901b.

[0296] The other temporary AS ID may be for example another temporary ID, another temporary UE ID, a second ID, a second temporary ID, a second temporary UE ID etc.

[0297] Step 1409

[0298] This step may correspond to step 1003 in FIG. 10. The first reader 901a may provide the other temporary AS ID to at least one of the device 903 and the second reader 901b.

[0299] Step 1410

[0300] The first reader 901a may obtain, from the second reader 901b, information indicating at least one of:

[0301] success of connection of the device 903 to the second reader 901b; and success of the offloading process.

[0302] Success of the offloading process may comprise that the second reader 901b has successfully obtained at least part of the remaining data transmission from the device 903.

[0303] 1411

[0304] The first reader 901a may obtain user data. The user data may be obtained from at least one of the device 903 and the second reader 901b.

[0305] 1412

[0306] The first reader 901a may forward the user data to a host or a user equipment.Fig. 15 is a schematic drawing illustrating the first reader 901a for handling data transmission in a communications system 100, 900.

[0307] The first reader 901a may comprise processing circuitry 1501 e.g. one or more processors, configured to perform the methods herein.

[0308] At least one of the first reader 901a and / or the processing circuitry 1501 is configured to perform the method of FIG. 14.

[0309] At least one of the first reader 901a and / or the processing circuitry 1501 is arranged to obtain a data transmission related to a procedure from a device. The data transmission is associated with a transaction / service ID. At least one of the first reader 901a and / or the processing circuitry 1501 is arranged to coordinate an offloading process with a second reader. The offloading process comprises that the device stops its procedure with the first reader and continues with the remaining data transmission of the procedure with the second reader. The remaining data transmission is associated with the same transaction / service ID as the data transmission that was performed with the first reader.

[0310] The first reader 901a further comprises a memory 1505. The memory 1505 comprises one or more units to be used to store data on, such as indications, data transmission, AS ID, offloading information, connection information, transaction / service ID, measurements, thresholds, data related to nodes, and applications to perform the methods disclosed herein when being executed, and similar. Furthermore, the first reader 901a may comprise a communication interface 1506 such as comprising a transmitter, a receiver, a transceiver and / or one or more antennas.

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

[0312] A first reader 901a for handling data transmissions in a communications system 100, 900 may comprise:

[0313] • processing circuitry configured to perform any of the operations of FIG. 14; and • a power source circuitry configured to supply power to the processing circuitry.

[0314] The method described above will now be described seen from the perspective of the second reader 901b. Fig. 16 is a flowchart describing the present method in the second reader 901b for handling data transmission in a communications system 100, 900.

[0315] The second reader 901b may be or may be comprised in at least one of:

[0316] • a network node,

[0317] • an access node,

[0318] • a RAN node,

[0319] • a User Equipment, UE, and

[0320] • an intermediate node.

[0321] The method comprises at least one of the following steps to be performed by the second reader 901, which steps may be performed in any suitable order than described below:

[0322] Step 1601

[0323] This step may correspond to step 1002 in FIG. 10. The second reader 901b connects to a device 903.

[0324] Step 1602This step may correspond to step 1003 in FIG. 10. The second reader 901b coordinates an offloading process with a first reader 901a. The offloading process comprises that the device 903 stops its procedure with the first reader 901a and continues with the remaining data transmission of the procedure with the second reader 901 b. The remaining data transmission is associated with the same transaction / service ID as the data transmission that was performed with the first reader 901a.

[0325] The coordinating of the offloading process may comprise that the second reader 901b obtains, from the first reader 901a, information indicating to perform the offloading process

[0326] The information indicating to perform the offloading process may comprise a temporary AS ID determined by the first reader 901a.

[0327] Coordinating of the offloading process may comprise coordinating use of an ID, e.g. the temporary AS ID, as will described in more detail in some steps below. The ID may be a common ID that is common for the first reader 901a and the second reader 901b

[0328] Step 1603

[0329] This step may correspond to step 1003 in FIG. 10. The second reader 901b may apply the temporary AS ID.

[0330] Step 1604

[0331] This step may correspond to step 1003 in FIG. 10. Based on a result of a comparison between the obtained temporary AS ID and at least one temporary AS ID already in use at the second reader 901b, the second reader 901b may determine whether or not the temporary AS ID is already in use at the second reader 901b.

[0332] The second reader 901b may determine, together with the first reader 901a, another temporary AS ID to be used instead. The other temporary AS ID is not already used by any of the first reader 901a and the second reader 901b.

[0333] 1605This step may correspond to step 1003 in FIG. 10. When a temporary AS ID is already in use, the second reader 901b may provide, to the first reader 901a, information indicating that the temporary AS ID is already in use at the second reader 901b.

[0334] 1606

[0335] This step may correspond to step 1003 in FIG. 10. The second reader 901b may provide the other temporary AS ID to at least one of the first reader 901a and the device 903.

[0336] 1607

[0337] This step may correspond to step 1003 in FIG: 10. When a temporary AS ID is not already in use, the second reader 901b may determine to apply the temporary AS ID.

[0338] Step 1608

[0339] This step may correspond to step 1004 in FIG. 10. The second reader 901b obtains the remaining data transmission from the device 903.

[0340] Step 1609

[0341] The second reader 901b may provide, to the first reader 901a, information indicating at least one of:

[0342] success of connection of the device 903 to the second reader 901b; and success of the offloading process.

[0343] Step 1610

[0344] The second reader 901b may obtain user data.

[0345] Step 1611

[0346] The second reader 901b may forward the user data to a host or a user equipment.

[0347] Fig. 17 is a schematic drawing illustrating the second reader 901b for handling data transmission in a communications system 100, 900.

[0348] The second reader 901b may comprise processing circuitry 1701 e.g. one or more processors, configured to perform the methods herein.At least one of the second reader 901b and the processing circuitry 1701 is configured to perform the method of FIG. 16.

[0349] At least one of the second reader 901b and the processing circuitry 1701 is arranged to connect to a device. At least one of the second reader 901b and the processing circuitry 1701 is arranged to coordinate an offloading process with a first reader. The offloading process comprises that the device stops its procedure with the first reader and continues with the remaining data transmission of the procedure with the second reader. The remaining data transmission is associated with the same transaction / service ID as the data transmission that was performed with the first reader. At least one of the second reader 901b and the processing circuitry 1701 is arranged to obtain the remaining data transmission from the device.

[0350] The second reader 901b further comprises a memory 1705. The memory 1705 comprises one or more units to be used to store data on, such as indications, data transmission, AS ID, offloading information, connection information, transaction / service ID, measurements, thresholds, data related to nodes, and applications to perform the methods disclosed herein when being executed, and similar. Furthermore, the second reader 901b may comprise a communication interface 1706 such as comprising a transmitter, a receiver, a transceiver and / or one or more antennas.

[0351] The methods according to the embodiments described herein for the second reader 901b are respectively implemented using e.g., a computer program product 1707 or a computer program, comprising instructions, i.e. , software code portions, which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the second reader 901b. The computer program product 1707 may be stored on a computer-readable storage medium 1708 e.g. a disc, a universal serial bus (USB) stick or similar. The computer-readable storage medium 1708 having stored thereon the computer program product, may comprise the instructions which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the second reader 901b. In some embodiments, the computer-readable storage medium may be a transitory or a non-transitory computer-readable storage medium. Thus, embodiments herein may disclose a second reader 901b for handling data transmission in a wirelesscommunication network 100, 900, wherein the second reader 901b comprises processing circuitry 1701 and a memory 1705, the memory 1705 comprising instructions executable by the processing circuitry 1701 whereby the second reader 901b is operative to perform any of the methods herein.

[0352] A second reader 901b for handling data transmissions in a communications system 100, 900 may comprise:

[0353] • processing circuitry configured to perform any of the operations of FIG. 16; and • a power source circuitry configured to supply power to the processing circuitry.

[0354] A computer program product may comprise program code for performing, when executed by the processing circuitry, the method of at least one of FIG. 12, 14 and 16.

[0355] A non-transitory computer-readable storage medium may comprise instructions, which when executed by the processing circuitry, cause the processing circuitry to perform the method of at least one of FIG. 12, 14 and 16.

[0356] FIG. 18 shows an example of a communication system 1800 in accordance with some embodiments.

[0357] In the example, the communication system 1800 includes a telecommunications network 1802 that includes an access network 1804, such as a radio access network (RAN), and a core network 1806, which includes one or more core network nodes 1808. The access network 1804 includes one or more access network nodes or base stations of various types, access network nodes 1810A and 1810B are depicted (which may be collectively referred to as network nodes 1810), or any other similar 3rdGeneration Partnership Project (3GPP) access nodes or non-3GPP access points (APs). Some embodiments of the access network 1804 may include more than one access network technology. The network nodes 1810 of access network 1804 facilitate direct or indirect connection of wireless devices, also referred to as user equipments (UEs), such as by connecting UEs 1812A, 1812B, 1812C, and 1812D (one or more of which may be generally referred to as UEs 1812) to the core network 1806 over one or more wireless connections.Moreover, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunications network 1802 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a network node in the telecommunications network 1802 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other network nodes to implement one or more functionalities of any network node in the telecommunications network 1802, including one or more access network nodes 1810 and / or core network nodes 1808.

[0358] Examples of an ORAN network node include an open radio unit (0-Rll), an open distributed unit (0-Dll), an open central unit (O-CU), including an O-CU control plane (O-CLI-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). An ORAN network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an A1, F1, W1, E1, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN network node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an O-2 interface defined by the O-RAN Alliance or comparable technologies.

[0359] The network nodes 1810 facilitate direct or indirect connection of one or more UEs 1812 to the core network 1806 over one or more wireless connections. Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, orother material conductors. Moreover, in different embodiments, the communication system 1800 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 1800 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0360] The UEs 1812 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes 1810 and other communication devices. Similarly, the network nodes 1808, 1810 are arranged, capable, configured, and / or operable to communicate directly or indirectly (e.g., via other devices of telecommunications network 1802) with the UEs 1812 and / or with other network nodes or equipment in the telecommunications network 1802 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunications network 1802. More specifically, UEs 1812 may send messages, data, and / or other signals to network nodes 1808, 1810 or other elements of the telecommunications network 1802 by transmitting such signals to the relevant device directly without the signals passing through any intervening devices or by transmitting such signals to the relevant device indirectly through an intervening device (or multiple intervening devices) that then transmit the signal to the relevant device. Similarly, network nodes 1808, 1810 may send messages, data, and other signals to UEs 18122, other network nodes 1808, 1810, and other devices in telecommunications network 1802 directly or indirectly. As one specific example, a core network node 108 may transmit a particular message to a UE 1812 by transmitting the message to an access network node 1810 that will then transmit the message to the intended UE 1812. Similarly, a core network node 108 may receive a particular message from a UE 1812 by receiving the message from an access network node 1810 that itself received the message from the UE 1812.

[0361] In the depicted example, the core network 1806 connects elements of the access network 1804 (e.g., one or more of the network nodes 1810) to one or more host computing systems, such as host 1816. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes maybe directly coupled to hosts. The core network 1806 includes one or more core network nodes (e.g., core network node 1808) of various types, one or more of which may be generally referred to as network nodes 1808. Network nodes 1808 are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, access network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 1808. Example core network nodes provide functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (ALISF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0362] The host 1816 may be under the ownership or control of a service provider other than an operator or provider of the access network 1804 and / or the telecommunications network 1802. The host 1816 may be operated by the service provider or on behalf of the service provider. The host 1816 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0363] As a whole, the communication system 1800 of FIG. 18 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system 1800 may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (Wi-Fi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (Wi-Max), Bluetooth, Z-Wave, Near FieldCommunication (NFC) ZigBee, Li-Fi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox. Moreover, the communication system 1800 may be configured to support multiple different standards, protocols, or other rule sets, with individual components supporting all of the relevant rule sets or with different components or sub-systems within the communication system 1800 supporting different standards, protocols, or rule sets.

[0364] As one example, in certain embodiments, access network 1804 may contain some access network nodes 1810 that support 3GPP radio access technologies (RAT), such as LTE or NR, while other access network nodes 1810 support (or the same access network nodes 1810 additionally support) non-3GPP RATs, such as Wi-Fi or a proprietary RAT. As another example, telecommunications network 1802 may support multiple generations of related communication standards (e.g., 4G and 5G 3GPP communication standards) and, as a result, may include an access network 104 and / or a core network 106 that supports multiple different standard generations or may include multiple access networks 104 and / or multiple core networks 106 with individual networks 104, 106 supporting different standard generations.

[0365] Telecommunications network 1802 may support network slicing to provide different logical networks to different devices that are connected to the telecommunications network 1802. For example, the telecommunications network 1802 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC) / Massive loT services to yet further UEs.

[0366] In some examples, one or more of the UEs 1812 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 1804 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 1804. Additionally, a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multiradio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).In the example, the hub 1814 communicates with the access network 1804 to facilitate indirect communication between one or more UEs (e.g., UE 1812C and / or 1812D) and network nodes (e.g., network node 1810B). In some examples, the hub 1814 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 1814 may be a broadband router enabling access to the core network 1806 for the UEs. As another example, the hub 1814 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 1810, or by executable code, script, process, or other instructions in the hub 1814.

[0367] As another example, the hub 1814 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 1814 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 1814 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 1814 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 1814 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0368] The hub 1814 may have a constant / persistent or intermittent connection to the network node 1810B. The hub 1814 may also allow for a different communication scheme and / or schedule between the hub 1814 and UEs (e.g., UE 1812C and / or 1812D), and between the hub 1814 and the core network 1806. In other examples, the hub 1814 is connected to the core network 1806 and / or one or more UEs via a wired connection. Moreover, the hub 1814 may be configured to connect to an M2M service provider over the access network 1804 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 1810 while still connected via the hub 1814 via a wired or wireless connection. In some embodiments, the hub 1814 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 1810B. In otherembodiments, the hub 1814 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 181 OB, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0369] FIG. 19 is another example of a communication system 1900 according to some embodiments. As used herein, the communication system 1900 includes multiple access points (APs) 1910 (with four exemplary APs 1910A, 1910B, 1910C, and 1910D being depicted) and multiple wireless devices, referred to in the context of communication system 1900 as stations (STAs) 1912 (referred to individually as STA 1912A, STA 1912B, STA 1912C, STA 1912D, and STA 1912E). STA 1912A is served by AP 1910A in a first basic service set (BSS) 1920A. STA 1910B and STA 1910C are served by AP 1910B in a second BSS, BSS 1920B. STA 1912D is served by AP 1910C in a third BSS, BSS 1920C. STA 1912E is served by AP 1910D in a fourth BSS, BSS 1920D. Stations 1912 may be non-AP STAs and correspond to various kinds of wireless devices, for example, user terminals, such as mobile or stationary computing devices like smartphones, laptop computers, desktop computers, tablet computers, gaming devices, head-mounted displays (HMDs) for Augmented Reality (AR) or Virtual Reality (VR), or the like. Further, stations 1912 could, for example, correspond to other kinds of equipment like smart home devices, printers, multimedia devices, data storage devices, or the like.

[0370] Each of STAs 1912 may connect through a radio link to one of APs 1910. For example, depending on location or channel conditions experienced by a given STA 1912, the STA may select an appropriate AP and BSS for establishing the radio link. The radio link may be based on one or more orthogonal frequency-division multiplexing (OFDM) carriers from a frequency spectrum that is shared on the basis of a contention-based mechanism, e.g., an unlicensed or license exempt band like 2.4 GHz Industrial, Scientific, and Medical (ISM) band, the 5 GHz band, the 6 GHz band, or the 60 GHz band.

[0371] Each AP 1910 may provide data connectivity to STAs 1912 connected to a particular AP 1910. As illustrated, APs 1910 may be connected to a data network 1930. In this way, APs 1910 may also provide data connectivity between STAs 1912 and other entities,e.g., to one or more servers, service providers, data sources, data sinks, user terminals, or the like. Accordingly, the radio link established between a given STA 1912 and its serving AP 1910 may be used for providing various kinds of services to STA 1912, e.g., a voice service, a multimedia service, or other data service. Such services may be based on applications that are executed on STA 1912 and / or on a device linked to STA 1912. By way of example, FIG. 19 illustrates an application service platform 1932 provided in data network 1930. The application(s) executed on STA 1912 and / or on one or more other devices linked to STA 1912 may use the radio link for data communication with one or more other STA 1912 and / or the application service platform 1932, thereby enabling utilization of the corresponding service(s) at STA 1912.

[0372] FIG. 20 shows a wireless device 2000, which may be configured to operate in communication system 1800 of FIG. 18 or in communication system 1900 of FIG. 190. The wireless device 2000 may be alternatively referred to as a UE 2000, like a UE 1812 within the context of communication system 1800, or as a station (STA) 2000 or as a non-access-point station (non-AP STA) 2000, like a STA 1912 within the context of the communication system 1900, in accordance with respective embodiments. As used herein, a wireless device refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other wireless devices. Examples of a wireless device include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, and wireless terminal. Other examples include any type of UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-loT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0373] A wireless device 2000 may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, wireless device 2000 may notnecessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, wireless device 2000 may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller).

[0374] Alternatively, wireless device 2000 may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0375] In particular embodiments, wireless device 2000 includes processing circuitry 2002 that is operatively coupled via a bus 2004 to an input / output interface 2006, a power source 2008, a memory 2010, a communication interface 2012, and / or any other component, or any combination thereof. Certain embodiments of wireless device 2000 may include all or a subset of the components shown in FIG. 20. The level of integration between the components may vary from one embodiment of wireless device 2000 to another. In general, in a particular embodiment of wireless device 2000, processing circuitry 2002, input / output interface 2006, power source 2008, memory 2010, and communication interface 2012 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of wireless device 2000. Further, certain embodiments of wireless devices 2000 may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0376] The processing circuitry 2002 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 2010. The processing circuitry 2002 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 2002 may include multiple central processing units (CPUs).In the example, the input / output interface 2006 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into wireless device 2000. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

[0377] In some embodiments, the power source 2008 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used to supply power to circuitry or to charge an associated battery. The power source 2008 may further include power circuitry for delivering power from the power source 2008 itself, and / or an external power source, to the various parts of wireless device 2000 via input circuitry or an interface such as an electrical power cable. Power source 2008 may perform any formatting, converting, or other modification to make accessible power suitable for the respective components of the wireless device 2000 to which power is supplied. The power source 2008 comprised in the device 903 may be different from a power source of an ordinary UE, e.g. a cell phone. The power source 2008 may be any suitable circuit arranged to obtain or harvest energy from the surroundings, e.g. from received radio signals. The externa power source providing power to the power source 2008 may be for example the sun or received radio signal, which are external from the device. The power source 2008 may be referred to as a power source circuitry.

[0378] The memory 2010 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM),erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 2010 includes one or more programs 2014, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 2016. The memory 2010 may store, for use by wireless device 2000, any of a variety of various operating systems or combinations of operating systems.

[0379] The memory 2010 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUlCC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 2010 may allow wireless device 2000 to access instructions, programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 2010, which may be or comprise a device-readable storage medium.

[0380] The processing circuitry 2002 may be configured to communicate with an access network or other network via or using the communication interface 2012. The communication interface 2012 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 2022. The communication interface 2012 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another wireless device or a network node in an access network). Each transceiver may include a transmitter 2018 and / or a receiver 2020 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 2018 andreceiver 2020 may be coupled to one or more antennas (e.g., antenna 2022) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0381] In the illustrated embodiment, communication functions of the communication interface 2012 may include cellular communication, Wi-Fi communication (e.g., according to an IEEE 802.11 family standard), LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / internet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0382] In particular embodiments, wireless device 2000 may provide an output of data captured via a sensor, through its communication interface 2012, via a wireless connection to a network node, and / or in any appropriate manner. Data captured by sensors of a wireless device 2000 can be communicated through a wireless connection to a network node via another wireless device 2000. In particular embodiments, such output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0383] As another example, wireless device 2000 comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, wireless device 2000 may comprise a motor that adjusts the control surfaces or rotors of a drone in flightaccording to the received input or to a robotic arm performing a medical procedure according to the received input.

[0384] Wireless device 2000, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, wearable technology, extended industrial application and healthcare. Nonlimiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smartwatch, a fitness tracker, a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. In particular embodiments, wireless device 2000 represents an loT device that comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the example embodiment of wireless device 2000 shown in FIG. 20.

[0385] As yet another specific example, in an loT scenario, wireless device 2000 may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another wireless device and / or a network node. Wireless device 2000 may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, wireless device 2000 may implement the 3GPP NB-loT standard. In other scenarios, wireless device 2000 may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0386] In practice, any number of wireless devices 2000 may be used together with respect to a single use case. For example, a first wireless device 2000 might be or be integrated in adrone and provide the drone’s speed information (obtained through a speed sensor) to a second wireless device 2000 that is a remote controller operating the drone. When a user makes changes from the remote controller, the first wireless device 2000 may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second wireless device 2000 can also include more than one of the functionalities described above. For example, wireless device 2000 might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0387] FIG. 21 shows a network node 2100 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunications network. In accordance with respective embodiments, network node 2100 may be configured to operate in communication system 1800 of FIG. 18, like network nodes 1808 or 1810, or in communication system 1900 of FIG. 19, like an AP 1910 or a station 1912. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), O-RAN nodes or components of an O-RAN node (e.g., 0-Rll, 0-Dll, O-CU).

[0388] Network nodes 2100 may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. Network node 2100 may be a relay node or a relay donor node controlling a relay. Network nodes 2100 may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an O-RAN access node) and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0389] Other examples of network nodes 2100 include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, networkcontrollers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).

[0390] In particular embodiments, network node 2100 includes a processing circuitry 2102, a memory 2104, a communication interface 2106, and a power source 2108. In general, in a particular embodiment of network node 2100, processing circuitry 2102, memory 2104, communication interface 2106, and power source 2108 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of network node 2100.

[0391] The network node 2100 may be composed of multiple distinct network entities (e.g., a NodeB entity and a RNC entity, or a BTS entity and a BSC entity, etc.), which may each have or utilize their own respective physical components. In certain scenarios in which the network node 2100 comprises multiple such entities (e.g., BTS and BSC), one or more of the separate entities may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 2100 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memories 2104 or portions of memory 2104 for different RATs) and some components may be reused (e.g., a same antenna 2110 may be shared by different RATs). The network node 2100 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 2100, for example GSM, WCDMA, LTE, NR, Wi-Fi (e.g., according to an IEEE 802.11 family standard), Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 2100.The processing circuitry 2102 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other components, such as the memory 2104, to provide network node 2100 functionality.

[0392] In some embodiments, the processing circuitry 2102 includes a system on a chip (SOC). In some embodiments, the processing circuitry 2102 includes one or more of radio frequency (RF) transceiver circuitry 2112 and baseband processing circuitry 2114. In some embodiments, the RF transceiver circuitry 2112 and the baseband processing circuitry 2114 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 2112 and baseband processing circuitry 2114 may be on the same chip or set of chips, boards, or units.

[0393] The memory 2104 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), readonly memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computerexecutable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 2102. The memory 2104 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 2102 and utilized by the network node 2100. The memory 2104 may be used to store any calculations made by the processing circuitry 2102 and / or any data received via the communication interface 2106. In some embodiments, the processing circuitry 2102 and memory 2104 is integrated.

[0394] The communication interface 2106 is used in wired or wireless communication of signaling and / or data with UEs, other network nodes, and / or any other network equipment. In the illustrated embodiment, communication interface 2106 comprisesport(s) / terminal(s) 2116 to send and receive data, for example to and from a network over a wired connection. In particular embodiments, network node 2000 may be capable of wireless communication and communication interface 2106 may also include radio front-end circuitry 2118 that may be coupled to, or in certain embodiments a part of, an antenna 2110. Particular embodiments of radio front-end circuitry 2118 include filter(s) 2120 and amplifier(s) 2122. The radio front-end circuitry 2118 may be connected to an antenna 2110 and processing circuitry 2102. The radio front-end circuitry may be configured to condition signals communicated between antenna 2110 and processing circuitry 2102. The radio front-end circuitry 2118 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 2118 may convert the digital data into a radio signal(s) having the appropriate channel and bandwidth parameters using a combination of filters 2120 and / or amplifiers 2122. The radio signal(s) may then be transmitted via the antenna 2110. Similarly, when receiving data, the antenna 2110 may collect radio signals which are then converted into digital data by the radio front-end circuitry 2118. The digital data may be passed to the processing circuitry 2102. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0395] In certain alternative embodiments, network node 2100 may be capable of wireless communication but does not include separate radio front-end circuitry 2118, instead, the processing circuitry 2102 includes radio front-end circuitry and is connected to the antenna 2110. Similarly, in some embodiments, all or some of the RF transceiver circuitry 2112 is part of the communication interface 2106. In still other embodiments, the communication interface 2106 includes one or more ports or terminals 2116, the radio front-end circuitry 2118, and the RF transceiver circuitry 2112, as part of a radio unit (not shown), and the communication interface 2106 communicates with the baseband processing circuitry 2114, which is part of a digital unit (not shown).

[0396] The antenna 2110 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 2110 may be coupled to the radio front-end circuitry 2118 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 2110 is separate from the network node 2100 and connectable to the network node 2100 through one or more interfaces or ports.The antenna 2110, communication interface 2106, and / or the processing circuitry 2102 may be configured to perform some or all of the receiving operations and / or obtaining operations described herein as being performed by the network node 2100. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna 2110, the communication interface 2106, and / or the processing circuitry 2102 may be configured to perform some or all of the transmitting or sending operations described herein as being performed by the network node 2100. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

[0397] The power source 2108 provides power to the various components of network node 2100 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 2108 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 2100 with power for performing the functionality described herein. For example, the network node 2100 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 2108. As a further example, the power source 2108 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0398] Embodiments of the network node 2100 may include additional components beyond those shown in FIG. 21 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 2100 may include user interface equipment to allow input of information into the network node 2100 and to allow output of information from the network node 2100. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 2100.FIG. 22 is a block diagram illustrating a virtualization environment 2200 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 2200 hosted by one or more of hardware nodes, such as a hardware computing device that operates as an access network node, UE, core network node, or host. Further, in embodiments in which a virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 2200 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface.

[0399] Applications 2202 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0400] Hardware 2204 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 2206 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VM 2208A and VM 2208B (which may be collectively referred to as VMs 2208), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 2206 may present a virtual operating platform that appears like networking hardware to one or more of the VMs 2208.The VMs 2208 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by virtualization layer 2206. Different embodiments of the instance of a virtual appliance 2202 may be implemented on one or more of VMs 2208, and the implementations may be made in different ways.

[0401] Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

[0402] In the context of NFV, each of the VMs 2208 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, nonvirtualized machine. Each of the VMs 2208, and that part of hardware 2204 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more of the VMs 2208 on top of the hardware 2204 and corresponds to an application 2202.

[0403] Hardware 2204 may be implemented in a standalone network node with generic or specific components. Hardware 2204 may implement some functions via virtualization. Alternatively, hardware 2204 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 2210, which, among others, oversees lifecycle management of applications 2202. In some embodiments, hardware 2204 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 2212 which may alternatively be used for communication between hardware nodes and radio units.

[0404] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments maycomprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.

[0405] Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0406] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hardwired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and / or is implied from the context in which it is used. All references to a / an / the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and / or where it is implicit that a step must follow or precede another step.

[0407] In general, the usage of “first”, “second”, “third”, “fourth”, and / or “fifth” herein may be understood to be an arbitrary way to denote different elements or entities, and may be understood to not confer a cumulative or chronological character to the nouns they modify, unless otherwise noted, based on context.

[0408] The present disclosure is not limited to the above. Various alternatives, modifications and equivalents may be used. Therefore, disclosure herein should not be taken as limiting the scope. A feature may be combined with one or more other features.

[0409] The term “at least one of A and B” should be understood to mean “only A, only B, or both A and B.”, where A and B are any parameter, number, indication used herein etc.

[0410] It should be emphasized that the term “comprises / comprising” when used in this specification is taken to specify the presence of stated features, integers, steps or components, but does not preclude the presence or addition of one or more other features, integers, steps, components or groups thereof. It should also be noted that the words “a” or “an” preceding an element do not exclude the presence of a plurality of such elements.

[0411] The term “configured to” used herein may also be referred to as “arranged to”, “adapted to”, “capable of” or “operative to”.

[0412] The steps of the methods may be performed in another order than the order in which they appear herein.EXAMPLE EMBODIMENTS

[0413] Group A Embodiments

[0414] 1. A method performed by a device (903) for handling data transmissions in a communications system (100, 900), the method comprising:

[0415] providing (1001, 1102, 1201) a data transmission related to a procedure to a first reader (901a), wherein the data transmission is associated with a transaction / service identity, ID;

[0416] performing (1003, 1105, 1106, 1206) an offloading process by stopping the procedure with the first reader (901a) and continuing with the remaining data transmission of the procedure with a second reader (901b), wherein the remaining data transmission is associated with the same transaction / service ID as the data transmission that was performed with the first reader (901a); and

[0417] providing (1004, 1106, 1208) the remaining data transmission to the second reader

[0418] (901b).

[0419] 2. The method according to any of the preceding embodiments, comprising:

[0420] determining (1002, 1003, 1105, 1202) to perform the offloading process;

[0421] 3. The method according to any of the preceding embodiments, comprising:

[0422] connecting (1002, 1105, 1207) to the second reader (901b).

[0423] 4. The method according to any of the preceding embodiments, wherein the offloading process is initiated by the device (903) or by at least one of the first reader (901a) and the second reader (901b).

[0424] 5. The method according to any of the preceding embodiments, comprising:

[0425] providing (1003, 1203), to at least one of the first reader (901a) and the second reader (901b), information indicating that the device (903) has determined to perform the offload process, e.g. that the device (903) has initiated the offloading process.

[0426] 6. The method according to any of the preceding embodiments, comprising:obtaining (1003, 1105, 1204), from at least one of the first reader (901a) and the second reader (901b), information indicating that at least one of the first reader (901a) and the second reader (901b) has determined to perform the offloading process, e.g. that at least one of the first reader (901a) and the second reader (901b) has initiated the offloading process.

[0427] 7. The method according to any of the preceding embodiments, comprising:

[0428] disconnecting (1003, 1209) from the first reader (901a).

[0429] 8. The method according to any of the preceding embodiments, comprising:

[0430] obtaining (1200) paging information from the first reader (901a).

[0431] 9. The method according to any of the preceding embodiments, wherein the offloading process is determined to be performed when at least one of the following triggers is detected:

[0432] • a transmission failure related to the procedure between the device (903) and the first reader (901a) has occurred;

[0433] • a mobility of the first reader (901 a);

[0434] • a mobility of the device (903);

[0435] • a link adaptation; and

[0436] • an offloading the load of the first reader (901a).

[0437] 10. The method according to any of the preceding embodiments, wherein the transmission failure is an inventory related transmission failure over a CBRA or CFRA occasion.

[0438] 11. The method of any of the preceding embodiments, comprising:

[0439] obtaining (1003, 1103, 1105, 1205) information indicating a temporary AS ID from at least one of the first reader (901a) and the second reader (901b).

[0440] 12. The method of any of the previous embodiments, further comprising:

[0441] providing (1210) user data; and

[0442] forwarding (1211) the user data to a host via the transmission to at least one of the first reader (901a) and the second reader (901b).13. The method according to any of the preceding embodiments, wherein the procedure to which the data transmission is related is at least one of or is comprised in at least one of:

[0443] • an inventory procedure;

[0444] • a command procedure; and

[0445] • an inventor and a command procedure.

[0446] 14. The method of any of the preceding embodiments, wherein the device (903) is at least one of or is comprised in at least one of:

[0447] • A-loT;

[0448] • A- loT UE;

[0449] • A-loT device;

[0450] • Wireless device;

[0451] • UE;

[0452] • Intermediate UE; and

[0453] • RFID device.

[0454] Group B Embodiments

[0455] 15. A method performed by a first reader (901a) for handling data transmissions in a communications system (100, 900), the method comprising:

[0456] obtaining (1001, 1102, 1401) a data transmission related to a procedure from a device (903), wherein the data transmission is associated with a transaction / service identity, ID; and

[0457] coordinating (1003, 1402) an offloading process with a second reader (901b), wherein the offloading process comprises that the device (903) stops its procedure with the first reader (901a) and continues with the remaining data transmission of the procedure with the second reader (901b), wherein the remaining data transmission is associated with the same transaction / service ID as the data transmission that was performed with the first reader (901a).

[0458] 16. The method according to any of the preceding embodiments, wherein the offloading process is initiated by the device (903) or by at least one of the first reader (901a) and the second reader (901b).17. The method according to any of the preceding embodiments, comprising: obtaining (1003, 1403), from the device (903), information indicating that the device (903) has determined to perform the offloading process to be performed, e.g. that the device (903) has initiated the offloading process.

[0459] 18. The method according to any of the preceding embodiments, comprising:

[0460] determining (1002, 1003, 1105, 1404) to perform the offloading process, e.g. initiating the offloading process.

[0461] 19. The method according to any of the preceding embodiments, comprising:

[0462] providing (1003, 1405), to at least one of the device (903) and the second reader (901b), information indicating to perform the offloading process, e.g. that it is initiated by the first reader (901a).

[0463] 20. The method according to any of the preceding embodiments, comprising:

[0464] disconnecting (1003, 1406) the device (903).

[0465] 21. The method according to any of the preceding embodiments, wherein the coordinating of the offloading process comprises:

[0466] providing (1003,1402), to the second reader (901b), information indicating to perform the offloading process.

[0467] 22. The method of any of the preceding embodiments, wherein the information indicating to perform the offloading process comprises:

[0468] • a temporary AS ID determined by the first reader (901a).

[0469] 23. The method of any of the preceding embodiments, comprising:

[0470] obtaining (1003, 1407), from the second reader (901b) information indicating that the temporary AS ID is already in use at the second reader (901b)

[0471] determining (1003, 1408), together with the second reader (901b), another temporary AS ID to be used instead and that is not already used by any of the first reader (901a) and the second reader (901b).24. The method of any of the preceding embodiment, comprising:

[0472] providing (1003, 1409) the other temporary AS ID to at least one of the device (903) and the second reader (901b).

[0473] 25. The method of any of the preceding embodiments, comprising:

[0474] obtaining (1410), from the second reader (901b), information indicating at least one of:

[0475] • success of connection of the device (903) to the second reader (901 b);

[0476] and

[0477] • success of the offloading process.

[0478] 26. The method according to any of the preceding embodiments, comprising:

[0479] providing (1101, 1400) paging information to the device (903).

[0480] 27. The method of any of the previous embodiments, further comprising:

[0481] obtaining (1411) user data; and

[0482] forwarding (1412) the user data to a host or a user equipment.

[0483] 28. The method according to any of the preceding embodiments, wherein the first reader (901a) is or is comprised in at least one of:

[0484] • a network node,

[0485] • an access node,

[0486] • a RAN node,

[0487] • a User Equipment, UE, and

[0488] • an intermediate node.

[0489] Group C Embodiments

[0490] 29. A method performed by a second reader (901b) for handling data transmissions in a communications system (100, 900), the method comprising:

[0491] connecting (1002, 1601) to a device (903);

[0492] coordinating (1003, 1602) an offloading process with a first reader (901a), wherein the offloading process comprises that the device (903) stops its procedure with the first reader (901a) and continues with the remaining data transmission of the procedure with the second reader (901b), wherein the remaining data transmission isassociated with the same transaction / service ID as the data transmission that was performed with the first reader (901a); and

[0493] obtaining (1004, 1608) the remaining data transmission from the device (903).

[0494] 30. The method according to any of the preceding embodiments, wherein the coordinating of the offloading process comprises:

[0495] obtaining (1003, 1602), from the first reader (901a), information indicating to perform the offloading process.

[0496] 31. The method of any of the preceding embodiments, wherein the information indicating to perform the offloading process comprises:

[0497] • a temporary AS ID determined by the first reader (901a).

[0498] 32. The method of any of the preceding embodiments, comprising:

[0499] applying (1003, 1603) the temporary AS ID.

[0500] 33. The method of any of the preceding embodiments, comprising:

[0501] based on a result of a comparison between the obtained temporary AS ID and at least one temporary AS ID already in use at the second reader (901b), determining (1003, 1604) whether or not the temporary AS ID is already in use at the second reader (901b).

[0502] 34. The method of any of the preceding embodiments, comprising:

[0503] when temporary AS ID is already in use, providing (1003, 1605), to the first reader (901a), information indicating that the temporary AS ID is already in use at the second reader (901b); determining (1003, 1605), together with the first reader (901a), another temporary AS ID to be used instead and that is not already used by any of the first reader (901a) and the second reader (901b).

[0504] 35. The method of any of the preceding embodiments, comprising:

[0505] providing (1003, 1606) another temporary AS ID to at least one of the first reader (901a) and the device (903).

[0506] 36. The method of any of the preceding embodiments, comprising:when temporary AS ID is not already in use, determining (1003, 1607) to apply the temporary AS ID.

[0507] 37. The method of any of the preceding embodiments, comprising:

[0508] providing (1609), to the first reader (901a), information indicating at least one of:

[0509] • success of connection of the device (903) to the second reader (901 b); and

[0510] • success of the offloading process.

[0511] 38. The method of any of the previous embodiments, further comprising:

[0512] obtaining (1610) user data; and

[0513] forwarding (1611) the user data to a host or a user equipment.

[0514] 39. The method according to any of the preceding embodiments, wherein the second reader (901b) is or is comprised in at least one of:

[0515] • a network node,

[0516] • an access node,

[0517] • a RAN node,

[0518] • a User Equipment, UE, and

[0519] • an intermediate node.

[0520] Group D Embodiments

[0521] 40. A device (903) for handling data transmissions in a communications system (100, 900), comprising:

[0522] processing circuitry configured to perform any of the operations of any of the Group A embodiments; and

[0523] a power source circuitry configured to supply power to the processing circuitry.

[0524] 41. A first reader (901a) for handling data transmissions in a communications system (100, 900), the first reader (901a) comprising:

[0525] processing circuitry configured to perform any of the operations of any of the Group B embodiments;

[0526] a power source circuitry configured to supply power to the processing circuitry.42. A second reader (901b) for handling data transmissions in a communications system (100, 900), the second reader (901b) comprising:

[0527] processing circuitry configured to perform any of the operations of any of the Group C embodiments;

[0528] a power source circuitry configured to supply power to the processing circuitry.

[0529] 43. A device (903) for handling data transmissions in a communications system (100, 900), the device (903) comprising:

[0530] one or more antennas;

[0531] communication interface connected to the one or more antennas and to processing circuitry;

[0532] the processing circuitry being configured to perform any of the operations of any of the Group A embodiments;

[0533] an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry;

[0534] an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a power source connected to the processing circuitry and configured to supply power to the UE.

[0535] 44. A computer program product comprising program code for performing, when executed by the processing circuitry, the method of at least one of the Group A embodiments, Group B embodiments and Group C embodiments.

[0536] 45. A non-transitory computer-readable storage medium comprising instructions, which when executed by the processing circuitry, cause the processing circuitry to perform the method of at least one of the Group A embodiments, Group B embodiments and Group C embodiments.

Claims

CLAIMS1. A method performed by a device (903) for handling a data transmission in a communications system (100, 900), the method comprising:initiating (1001 , 1102, 1201) a data transmission related to a procedure to a first reader (901a), wherein the data transmission is associated with a transaction / service identity, ID;performing (1003, 1105, 1106, 1206) an offloading process which comprises stopping the procedure with the first reader and continuing the procedure with a second reader (901b); andproviding (1004, 1106, 1208) a remaining portion of the data transmission to the second reader, wherein the remaining portion of the data transmission provided to the second reader is associated with the same transaction / service ID as the data transmission that was initiated to the first reader.

2. The method according to claim 1, comprising:determining (1002, 1003, 1105, 1202) to perform the offloading process.

3. The method according to any of the preceding claims, wherein the offloading process is initiated by the device or by the first reader or by the second reader.

4. The method according to any of the preceding claims, comprising:providing (1003, 1203), to at least one of the first reader and the second reader, information indicating that the device has determined to perform the offloading process..

5. The method according to claim 1 or claim 3, comprising:obtaining (1003, 1105, 1204), from at least one of the first reader and the second reader, information indicating that at least one of the first reader (901a) and the second reader has determined that the offloading process is to be performed.

6. The method according to any of the preceding claims, comprising:obtaining (1200) paging information from the first reader.

7. The method according to any of the preceding claims, wherein the offloading process is determined to be performed when at least one of the following triggers is detected:• a transmission failure related to the procedure between the device and the first reader has occurred;• a mobility of the first reader;• a mobility of the device;• a link adaptation; and• an offloading the load of the first reader.

8. The method according to claim 7, wherein the transmission failure is an inventory related transmission failure over a contention-based random access, CBRA, or contention-free random access, CFRA, occasion.

9. The method according to any of the preceding claims, comprising:obtaining (1003, 1103, 1105, 1205) information indicating a temporary access stratum identity (AS ID) from the first reader .

10. The method according to claim 9, comprising:receiving, from the second reader, a paging message or contention-free random access, CFRA, message addressed to the temporary AS ID.

11. The method according to any of the preceding claims, wherein the procedure to which the data transmission is related is or is comprised in:• an inventory procedure; or• a command procedure; or• an inventor and a command procedure.

12. The method according to any of the preceding claims, wherein the device (903) is an ambient internet of things, A-loT, device.

13. A method performed by a first reader (901a) for handling a data transmission in a communications system (100, 900), the method comprising:obtaining (1001, 1102, 1401) an initial portion of a data transmission related to a procedure from a device (903), wherein the initial portion of the data transmission is associated with a transaction / service identity, ID; andcoordinating (1003, 1402) an offloading process with a second reader (901b) and / or the device, wherein the offloading process comprises that the device stops its procedure with the first reader and continues the procedure with the second reader for providing a remaining portion of the data transmission to the second reader, wherein the remaining portion of the data transmission provided to the second reader is associated with the same transaction / service ID as the initial portion of the data transmission that was obtained by the first reader.

14. The method according to claim 13, wherein the offloading process is initiated by the device or by the first reader or by the second reader.

15. The method according to any of claims 13-14, comprising:obtaining (1003, 1403), from the device , information indicating that the device has determined to perform the offloading process.

16. The method according to any of claims 13-14, comprising:determining (1002, 1003, 1105, 1404) to perform the offloading process.

17. The method according to any claims 13-14 or 16, comprising:providing (1003, 1405), to at least one of the device and the second reader, information indicating to perform the offloading process.

18. The method according to any of claims 13-14 or 16-17, wherein the coordinating of the offloading process comprises:providing (1003,1402), to the second reader, information indicating to perform the offloading process.

19. The method according to any of claims 13-18, comprising:providing information indicating a temporary access stratum identity (AS ID) to the device.

20. The method according to claim 19, wherein the coordinating of the offloading process comprises:• providing, to the second reader, information indicating the temporary AS ID.

21. The method according to claim 20, comprising:obtaining (1003, 1407), from the second reader information indicating that the temporary AS ID is already in use at the second reader; anddetermining (1003, 1408), together with the second reader, another temporary AS ID to be used instead and that is not already used by any of the first reader and the second reader.

22. The method according to claim 21 , comprising:providing (1003, 1409) the other temporary AS ID to at least one of the device and the second reader.

23. The method according to any of claims 13-22, comprising:obtaining (1410), from the second reader, information indicating at least one of:• success of connection of the device to the second reader; and • success of the offloading process.

24. The method according to any of claims 13-23, comprising:providing (1101, 1400) paging information to the device.

25. A method performed by a second reader (901b) for handling a data transmission in a communications system (100, 900), the method comprising:coordinating (1003, 1602) an offloading process with a first reader (901a) and / or a device (903), wherein the offloading process comprises that the device stops a procedure with the first reader after having initiated a data transmission related to the procedure to the first reader and continues the procedure with the second reader; and obtaining (1004, 1608) a remaining portion of the data transmission from the device, wherein the remaining portion of the data transmission obtained from the device is associated with the same transaction / service ID as the data transmission that was initiated to the first reader.

26. The method according to claim 25, wherein the coordinating of the offloading process comprises:obtaining (1003, 1602), from the first reader, information indicating to perform the offloading process.

27. The method according to any of claims 25-26, wherein the coordinating of the offloading process comprises:• obtaining, from the first reader, a temporary access stratum identity (AS ID),28. The method according to claim 27, comprising:applying (1003, 1603) the temporary AS ID.

29. The method according to any of claims 27-28, comprising:providing, to the device, a paging message or contention-free random access, CFRA, message addressed to the temporary AS ID.

30. The method according to claim 27, comprising:based on a result of a comparison between the obtained temporary AS ID and at least one temporary AS ID already in use at the second reader, determining (1003, 1604) whether or not the temporary AS ID is already in use at the second reader.

31. The method according to claim 30, comprising:when temporary AS ID is already in use at the second reader, providing (1003, 1605), to the first reader, information indicating that the temporary AS ID is already in use at the second reader; determining (1003, 1605), together with the first reader, another temporary AS ID to be used instead and that is not already used by any of the first reader and the second reader.

32. The method according to claim 31 , comprising:providing (1003, 1606) the other temporary AS ID to at least one of the first reader and the device.

33. The method according to claim 30 or claim 31, comprising:when the temporary AS ID is not already in use at the second reader, determining (1003, 1607) to apply the temporary AS ID.

34. The method of any of claims 25-33, comprising:providing (1609), to the first reader, information indicating at least one of:• success of connection of the device to the second reader; and • success of the offloading process.

35. The method according to any of the preceding claims, wherein:the first reader is a user equipment and the second reader is a network node; or the first reader is a network node and the second reader is a user equipment; or the first and second readers are network nodes; orthe first and second readers are user equipments.

36. A device (903) for handling a data transmission in a communications system (100, 900), the device comprising:processing circuitry configured to:initiate a data transmission related to a procedure to a first reader (901a), wherein the data transmission is associated with a transaction / service identity, ID;perform an offloading process which comprises stopping the procedure with the first reader and continuing the procedure with a second reader (901b); andprovide a remaining portion of the data transmission to the second reader, wherein the remaining portion of the data transmission provided to the second reader is associated with the same transaction / service ID as the data transmission that was initiated to the first reader, anda power source circuitry configured to supply power to the processing circuitry.

37. A first reader (901a) for handling a data transmission in a communications system (100, 900), the first reader comprising:processing circuitry configured to:obtain an initial portion of a data transmission related to a procedure from a device (903), wherein the initial portion of the data transmission is associated with a transaction / service identity, ID; andcoordinate an offloading process with a second reader (901b) and / or the device, wherein the offloading process comprises that the device stops its procedure with the first reader and continues the procedure with the second reader for providing a remaining portion of the data transmission to the second reader, wherein the remaining portion of the data transmission provided to the second reader is associated with the same transaction / service ID as the initial portion of the data transmission that was obtained by the first reader, and a power source circuitry configured to supply power to the processing circuitry.

38. A second reader (901b) for handling a data transmission in a communications system (100, 900), the second reader comprising:processing circuitry configured to:coordinate (1003, 1602) an offloading process with a first reader (901a) and / or a device (903), wherein the offloading process comprises that the device stops a procedure with the first reader after having initiated a data transmission related to the procedure to the first reader and continues the procedure with the second reader; andobtain (1004, 1608) a remaining portion of the data transmission from the device, wherein the remaining portion of the data transmission obtained from the device is associated with the same transaction / service ID as the data transmission that was initiated to the first reader, anda power source circuitry configured to supply power to the processing circuitry.

Images