Field

Embodiments as set out in this document relate to sidelink positioning, for example to providing sidelink positioning assistance in mobile communication systems.

Background

Sidelinks can be provided in mobile communication systems to enable direct communications between user equipment (UEs). Positioning information can be provided using such sidelinks. There remains a need for further developments in this field.

Summary

In a first aspect, this specification describes a third user device of a mobile communication system comprising a target user device, an anchor user device and the third user device, the third user device comprising: means for performing: receiving a sidelink positioning signal (such as a sidelink positioning reference signal (S-PRS)) sent by the target user device to the anchor user device; means for performing: detecting a trigger for the use of a substitute anchor device; means for performing: determining whether to act as the substitute anchor device based, at least in part, on whether said trigger is detected; and means for performing: providing sidelink positioning assistance to the target user device in the event that a determination is made to act as the substitute anchor device. The sidelink positioning signal may have a payload. The sidelink positioning signal may have a/the trigger.

The trigger may be based on a breakdown of a handshaking between the target and anchor user devices. This breakdown may be caused, for example, by a resource conflict (e.g. at the anchor user device). In some example embodiments, providing sidelink positioning assistance comprises transmitting (at least) a sidelink positioning reference signal and providing position data (e.g. in accordance with a configuration) for the third user device to the target user device. It should be noted that the positioning assistance data may include more than said sidelink positioning reference signal and said positioning data. The position data for the third user device may comprise an indication of an absolute position of said third user device. The third user device may further comprise means for performing: receiving a configuration message from the target user device indicating that the third user device is one of one or more candidate substitute anchor devices. The configuration message may be sent together with the sidelink positioning signal sent by the target user device to the anchor user device (i.e. the sidelink positioning signal sent by the target user device to the anchor user device may include configuration information). Alternatively, a separate configuration step may be provided. The determination of whether to act as the substitute anchor device may be based, at least in part, on whether the third user device is one of one or more candidate substitute anchor devices. However, in some example embodiments, a user device may be able to act as the third user device while not being part of a candidate substitute anchor set.

The third user device may further comprise: means for performing: determining, at the third user device, whether the third user device is a candidate substitute anchor device for the target user device. The determination of whether the third user device is a candidate substitute anchor device may be based, at least in part, on a location of the third user device relative to the anchor user device.

In some example embodiments, the means for performing determining the trigger for the use of the substitute anchor device comprises detecting a resource conflict. The resource conflict may be at the anchor user device (e.g. a resource collision at the anchor user device). In some example embodiments, the resource conflict may be at the target user device.

In a second aspect, this specification describes a target user device of a mobile communication system comprising the target user device, an anchor user device and a third user device, the target user device comprising: means for performing: sending a sidelink positioning signal to the anchor user device; and means for performing: receiving sidelink positioning assistance (e.g. the position of the (substitute) anchor device) in response to said request, from the third user device (e.g. in the event that a resource conflict is detected at the anchor user device, or based on some other trigger, such as a breakdown of a handshaking between the target and anchor user devices). The sidelink positioning assistance may comprise (at least) a sidelink positioning reference signal and position data (e.g. in accordance with a configuration) for the third user device to the target user device. The position data for the third user device may comprise an indication of an absolute position of said third user device. It should be noted that the positioning assistance data may include more than said sidelink positioning reference signal and said positioning data.

The target user device may further comprise: means for performing: determining a position of the target user device based, at least in part, on the received sidelink positioning assistance.

The target user device may further comprise: means for performing: sending a configuration message to the third user device, wherein the configuration message indicates that the third user device is one of one or more candidate substitute anchor devices. Alternatively, or in addition, the sidelink positioning signal may identify the third user device as one of one or more candidate substitute anchor devices. In some example embodiments, the one or more candidate substitute anchor devices are identified in order of preference. In the first and second aspects described above, the said means may comprise: at least one processor; and at least one memory including computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the performance of the apparatus. In a third aspect, this specification describes a method comprising: receiving (e.g. at a third user device) a sidelink positioning signal (such as a sidelink positioning reference signal (S-PRS)) sent by a target user device of a mobile communication to an anchor user device of the mobile communication system; detecting a trigger for the use of a substitute anchor device; determining whether a third user device should act as the substitute anchor device based, at least in part, on whether said trigger is detected; and providing sidelink positioning assistance from the third user device to the target user device in the event that a determination is made to act as the substitute anchor device.

The sidelink positioning signal may have a payload. The sidelink positioning signal may have a trigger. The determination of whether to act as the substitute anchor device may be based, at least in part, on whether the third user device is one of one or more candidate substitute anchor devices. The method may further comprise: receiving (at the third user device) a configuration message from the target user device indicating that the third user device is one of said one or more candidate substitute anchor devices. The configuration message may be sent together with the sidelink positioning signal sent by the target user device to the anchor user device (i.e. the sidelink positioning signal sent by the target user device to the anchor user device may include configuration information). Alternatively, a separate configuration step maybe provided. The method may further comprise: determining (e.g. at the third user device) whether the third user device is a candidate substitute anchor device for the target user device.

The determination of whether the third user device is a candidate substitute anchor device maybe based, at least in part, on a location of the third user device relative to the anchor user device.

In a fourth aspect, this specification describes a method comprising: sending a sidelink positioning signal from a target user device to an anchor user device of a mobile communication system comprising the target user device, the anchor user device and a third user device; and receiving sidelink positioning assistance (e.g. the position of the (substitute) anchor device) in response to said request, from the third user device (e.g. in the event that a resource conflict is detected at the anchor user device, or based on some other trigger, such as a breakdown of a handshaking between the target and anchor user devices). The method may comprise: determining (at the target user device) a position of the target user device based, at least in part, on the received sidelink positioning assistance.

The method may comprise: sending a configuration message from the target user device to the third user device, wherein the configuration message indicates that the third user device is one of one or more candidate substitute anchor devices.

Alternatively, or in addition, the sidelink positioning signal may identify the third user device as one of one or more candidate substitute anchor devices. In some example embodiments, the one or more candidate substitute anchor devices are identified in order of preference. In a fifth aspect, this specification describes computer-readable instructions which, when executed by a computing apparatus, cause the computing apparatus to perform (at least) any method as described with reference to the third or fourth aspects. In a sixth aspect, this specification describes a computer-readable medium (such as a non-transitory computer-readable medium) comprising program instructions stored thereon for performing (at least) any method as described with reference to the third or fourth aspects. In a seventh aspect, this specification describes an apparatus comprising: at least one processor; and at least one memory including computer program code which, when executed by the at least one processor, causes the apparatus to perform (at least) any method as described with reference to the third or fourth aspects. In an eighth aspect, this specification describes a computer program comprising instructions for causing an apparatus to perform at least the following: receiving a sidelink positioning signal (such as a sidelink positioning reference signal (S-PRS)) sent by a target user device of a mobile communication to an anchor user device of the mobile communication system; detecting a trigger for the use of a substitute anchor device; determining whether a third user device should act as the substitute anchor device based, at least in part, on whether said trigger is detected; and providing sidelink positioning assistance from the third user device to the target user device in the event that a determination is made to act as the substitute anchor device. The sidelink positioning signal may have a payload. The sidelink positioning signal may have a trigger. The determination of whether to act as the substitute anchor device may be based, at least in part, on whether the third user device is one of one or more candidate substitute anchor devices.

In a ninth aspect, this specification describes a computer program comprising instructions for causing an apparatus to perform at least the following: sending a sidelink positioning signal from a target user device to an anchor user device of a mobile communication system comprising the target user device, the anchor user device and a third user device; and receiving sidelink positioning assistance (e.g. the position of the (substitute) anchor device) in response to said request, from the third user device (e.g. in the event that a resource conflict is detected at the anchor user device, or based on some other trigger, such as a breakdown of a handshaking between the target and anchor user devices).

In a tenth aspect, this specification describes an apparatus comprising a sidelink receiver of a user device (or some other means) for receiving a sidelink positioning signal sent by a target user device of a mobile communication to an anchor user device of the mobile communication system; a processor (or some other means) for detecting a trigger for the use of a substitute anchor device; a processor (or some other means) for determining whether a third user device should act as the substitute anchor device based, at least in part, on whether said trigger is detected; and a sidelink transmitter (or some other means) for providing sidelink positioning assistance from the third user device to the target user device in the event that a determination is made to act as the substitute anchor device. In an eleventh aspect, this specification describes an apparatus comprising a sidelink transmitter (or some other means) for sending a sidelink positioning signal from a target user device to an anchor user device of a mobile communication system comprising the target user device, the anchor user device and a third user device; and a sidelink receiver (or some other means) for receiving sidelink positioning assistance in response to said request, from the third user device.

Brief Description of Drawings

Example embodiments will now be described, by way of non-limiting examples, with reference to the following schematic drawings, in which:

FIG. i is a block diagram of a system in accordance with an example embodiment;

FIG. 2 is a message flow sequence in accordance with an example embodiment;

FIGS. 3 to 5 are block diagrams of systems in accordance with example embodiments; FIGS. 6 and 7 are message flow sequences in accordance with example embodiments; FIGS. 8 and 9 are flow charts showing algorithms or methods in accordance with example embodiments;

FIG. 10 is a block diagram of components of a system in accordance with an example embodiment; and

FIG. 11 shows an example of tangible media for storing computer-readable code which when run by a computer may perform methods according to example embodiments described above. Detailed Description

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

In the description and drawings, like reference numerals refer to like elements throughout.

FIG. i is a block diagram of a system, indicated generally by the reference numeral io, in accordance with an example embodiment. The system io comprises a plurality of user devices or user equipments 12, 14, 16 and 18 (generally referred to herein as user devices). Those user devices include a target user device (UE-T) 12 and an anchor user device (UE-A) 14.

FIG. 2 is a message flow sequence, indicated generally by the reference numeral 20, in accordance with an example embodiment. The message flow sequence 20 shows messages between the target user device 12 and the anchor user device 14 of the system

10. As discussed further below, the message flow sequence 20 can be used to enable the target user device 12 to use sidelink techniques to obtain support from the anchor user device 14 to obtain positioning information (e.g. absolute location information of the anchor device) with low latency for the target user device.

In the message sequence 20, the target user device 12 transmits a sidelink positioning signal (SL-PRS_T) 22 to the anchor user device 14. The SL-PRS_T may include a sidelink positioning reference signal (PRS).

The anchor user device 14 responds to the message 22 by sending a sidelink positioning signal response (SL-PRS_A) transmission 24 to the target user device. The SL-PRS_A response 24 may include sidelink PRS and metadata such as an absolute location of the anchor user device. The absolute position of the anchor user device 14, and the position of the anchor user device relative to the target user device (determined, for example, based on data such a time-of-arrival, angle-of-arrival and/ or round trip delay) can then be used to determine an estimate of the absolute position of the target user device. That determination may be made at the target user device.

The selection of the anchor user device can be implemented in many ways, such as by the anchor user device 14 announcing in a resource pool (e.g. by broadcasting a discovery message) that the anchor user device is aware of its absolute position (or that it has the means to acquire said position, e.g. via GNSS) or via prior PC5-RRC signalling exchanges between the target and anchor user devices. The message exchange 20 between the target and anchor user devices 12 and 14 is subject to the challenges of sidelink communication. These include the hidden node problem and the half-duplex constraint in distributed sidelink resource scheduling (as discussed below with reference to FIGS. 3 and 4). Thus, when the target user device 12 transmits the SL-PRS_T message to the anchor user device 14, the anchor user device may not be able to successfully receive SL-PRS_T and/ or may not be able to successfully transmit the SL-PRS_A response.

FIG. 3 is a block diagram of a system, indicated generally by the reference numeral 30, in accordance with an example embodiment. The system 30 comprises a target user device (UE-T) 32, an anchor user device (UE-A) 34 and a further user device (UE-Z) 36.

The target and anchor user devices 32 and 34 may be the target and anchor user device 12 and 14 described above. Similarly, the further user device 36 may be one of the user devices 16 and 18 described above. As shown in the system 30, the anchor user device 34 is transmitting to the further user device 36 (e.g. using a physical sidelink shared channel (PSSCH), a physical sidelink control channel (PSCCH) or sidelink PRS transmission). As a result, the anchor user device 34 is unable to receive a SL-PRS_T message from the target user device 32 (a so- called half-duplex constraint).

FIG. 4 is a block diagram of a system, indicated generally by the reference numeral 40, in accordance with an example embodiment. The system 40 comprises the target user device (UE-T) 32 and the anchor user device (UE-A) 34 described above and further comprises a further user device (UE-Z) 42 (which further user device 42 may be another of the user devices 16 and 18 described above). As shown in the system 40, the anchor user device 34 is a recipient of a transmission or interference from the further user device 42. As a result, the anchor user device 34 is unable to receive a SL-PRS_T message from the target user device 32 (a resource conflict due to a half-duplex constraint).

The example resource conflicts at the anchor user device 34 break the SL-PRS exchange (2-way handshake) between the target user device 32 and the anchor user device that is needed for determining a position estimate at the target user device. That is, due to the unsuccessful reception of sidelink positioning signals from the target user device 32, the anchor user device 34 will not be able to respond with positioning data and hence the target user device will not be able to generate a position estimate.

Even when HARQ-like feedback is enabled, a retransmission of the SL-PRS_T from the target user device 32 to the anchor user device 34 may add additional latency. Depending on the severity of the resource conflict (e.g. whether more/ all semi- persistent scheduling (SPS) resources are conflicted and/or whether more/all retransmissions are conflicted) the latency may be increased to a degree that is not acceptable for a low latency positioning embodiment (e.g. IIoT and V2X applications may require less than 10 ms maximum latency for position determination).

It is noted that although the resource conflicts described above with reference to the message flow sequences 30 and 40 occur at the anchor user device, it is possible for conflicts to occur at the target user device 32, such that the target user device is not able to successfully receive a SL-PRS_A message sent by the anchor user device.

FIG. 5 is a block diagram of a system, indicated generally by the reference numeral 50, in accordance with an example embodiment. The system 50 comprises a target user device (UE-T) 52, an anchor user device (UE-A) 54 and a third user device (UE-X) 56.

The target user device 52 maybe similar to the target user devices 12 and 32 described above. Similarly, the anchor user device 54 may be similar to the anchor user devices 14 and 34 described above.

The third user device 56 receives a sidelink positioning signal sent by the target user device 52 to the anchor user device 54. As described in detail below, the third user device has the ability to act as a substitute anchor device, for example in the event that the handshaking procedure between the target and anchor user devices is not possible (as described above). Thus, the third user device 56 is able to provide sidelink positioning assistance (in response to the sidelink positioning signal sent to the anchor user device) in the event that a determination is made that the third user device 56 should act as a substitute anchor device.

FIG. 6 is a message flow sequence, indicated generally by the reference numeral 60, in accordance with an example embodiment. The message flow sequence 60 shows an example use of the system 50. The message flow sequence 60 starts at operation 61, where the target user device (UE- T) 52 selects the anchor user device (UE-A) 54 to operate as an anchor UE as part of an anchor UE selection process. During the operation 61, the target user device 52 may have identified a third user device (UE-X) 56 as a candidate anchor UE (e.g. due to being a neighbouring UE), but has not selected it as anchor UE due to e.g., high collinearity with UE-A.

The target user device (UE-T) 52 sends a message 62 to the third user device 56 to explicitly indicate that the third user device should act as a substitute anchor user device in the event that the selected anchor user device (UE-A) 54 cannot respond (e.g. due to half-duplex, interference or some other constraints). The message 62 may include SL-PRS configuration information.

In an alternative embodiment, the message 62 may be replaced with a message that is broadcast to all nearby user devices capable of taking the role of substitute anchor user device. That broadcast may result in one of one or more candidate substitute anchor user devices deciding to take the role of the substitute anchor user device.

In the message sequence 60, the target user device 52 sends a sidelink positioning signal (SL-PRS_T) message 63 to the anchor user device (UE-A) 54, requesting a sidelink positioning signal response (SL-PRS_A) from the anchor user device (e.g. for low latency positioning).

In the message sequence 60, the anchor user device 54 is unable to respond to the message 63 as the anchor user device is concurrently performing sidelink transmission (e.g. sidelink PRS or PSCCH/PSSCH) to another UE, such that a half-duplex conflict occurs. In an operation 64, the third user device 56 detects the resource conflict. For example the third user device (UE-X) 56 may monitor a sidelink resource pool and thereby receive transmissions from both the target user device (UE-T) 52 and the anchor user device (UE-A) 54 for use in detecting conflicts.

The detection of a resource conflict can be based on the sidelink control information (SCIs) transmitted from the target user device to the anchor user device for SL-PRS transmission occurring in the same slot and at different sub-channels or different symbols within the slot.

At operation 65, the third user device (UE-X) 56 prepares a sidelink positioning signal response (SL-PRS_X) as a positioning assistance message for the target user device, where that response is prepared based on SL-PRS configuration associated with the anchor UE (e.g. the SL-PRS_X is derived from the SL-PRS_A of the anchor user device obtained in the operation 61). The third user device 56 may also include its own position as metadata of the positioning message and may also include other data such as time of arrival (TOA), time of departure (TOD) and/or round trip time (RTT) data. The third user device 56 transmits a SL-PRS_X message 66 to the target user device 52 on the same resource in which the target user device is expecting a response from the anchor user device 54.

Finally, at operation 67, the target user device 52 uses the SL-PRS_X message 66 received from the third user device 56 (and the location of the third user device) for sidelink positioning. The message 66 can thereby be used in place of the expected message from the anchor user device 54.

The message sequence 60 is one example embodiment of the principles described herein; alternative embodiments are possible, as discussed further below.

FIG. 7 is a message flow sequence, indicated generally by the reference numeral 70, in accordance with an example embodiment. The message flow sequence 70 starts at operation 71, where the target user device (UE- T) 52 selects the anchor user device (UE-A) 54 to operate as an anchor UE as part of an anchor UE selection process. During the operation 71, the target user device 52 may have identified a third user device (UE-X) 56 as a candidate anchor UE (e.g. due to being a neighbouring UE), but has not selected it as anchor UE due to e.g., high collinearity with the anchor user device.

The target user device 52 transmits a message 72 comprising SL-PRS configuration (e.g. including SL-PRS_A sequence identifier) that is to be used by the anchor user device 54 for responding to the target user device 52. The target user device 52 transmits a SL-PRS_T message 73 to the anchor user device 54, requesting a SL-PRS_A response from the anchor user device for use in low latency positioning. Concurrently, the anchor user device 54 is transmitting a sidelink message (e.g. sidelink PRS or PSCCH/PSSCH) to another user device, such that a half-duplex conflict occurs.

At operation 74, the third user device 56 determines whether or not to act as a substitute anchor user device in case the anchor user device (UE-A) 54 does not respond. As discussed further below, the third user device 56 may make use of distance-based criteria in a determination of whether the third user device 56 is in the same zone as the anchor user device in order to determine whether to take the role of the substitute anchor user device. Here, a zone-ID of the anchor user device may be known by the third user device from past sidelink control information (SCI) transmissions from the anchor user device. If the third user device 56 decides to act as the substitute user device, then, at operation 75, the third user device monitors the sidelink resource pool and receives transmissions from both the target user device 52 and the anchor user device 54. In this way, the third user device can detect resource conflicts at the anchor user device (UE-A) for SL- PRS_T transmissions from the target user device.

The detection of resource conflict can be based on sidelink control information (SCIs) transmitted from the target user device to the anchor user device occurring in the same slot and at different sub-channels or different symbols within the slot. Alternatively, or in addition, the third user device can detect that the anchor user device has not replied to the target user device within an expected time window (e.g. pre-configured time period or a time period indicated in the UE-A request) or on the resource indicated by UE-A in its initial request. In other words, the absence of a SL-PRS transmission from the anchor user device may act as a trigger for the third user device to become the substitute anchor user device. At operation 76, the third user device 56 (which is acting as the substitute anchor user device) prepares a sidelink positioning signal response message (SL-PRS_X) as a positioning assistance to the target user device, where the sidelink positioning signal response is prepared based on SL-PRS configuration associated with the anchor user device (e.g., SL-PRS_X is derived from SL-PRS_A of anchor UE) obtained in the operation 72. The third user device 56 may also include its own position as metadata of the positing message and may also include other data such as time of arrival (TO A), time of departure (TOD) and/or round trip time (RTT) data.

The third user device 56 transmits a SL-PRS_X message 77 to the target user device 52 on the same resource in which the target user device is expecting a response from the anchor user device 54.

Finally, at operation 78, the target user device 52 uses the SL-PRS_X message 77 received from the third user device 56 (and the location of the third user device) for sidelink positioning. The message 77 can thereby be used in place of the expected message from the anchor user device 54.

A number of variants of the algorithms 60 and 70 are possible. For example, in one example embodiment, the anchor user device, upon detecting the sidelink positioning signal transmission from the third user device, releases its role as anchor user device towards the target user device and does not proceed with the positioning session (i.e. it will not send additional SL-PRS). This detection can occur by the anchor user device detecting that the SL-PRS transmission is towards the target user device, e.g. based on the identity fields in the second stage SCI or based on the used resource by the third user device to transmit to target user device.

FIG. 8 is a flow chart, indicated generally by the reference numeral 80, in accordance with an example embodiment. The algorithm 80 maybe implemented at the third user device 56 described above (e.g. when implementing the message sequences 60 or 70 described above). The algorithm 80 starts at operation 82, where a sidelink positioning signal sent by a target user device to an anchor user device is received at a third user device (e.g. the device 56) of a mobile communication system. The sidelink positioning signal may be a sidelink positioning reference signal (S-PRS) and may have a payload.

At operation 84, a trigger for the use of a substitute anchor device is detected. The trigger may, for example, be based on a breakdown of a handshaking between the target and anchor user devices (e.g. due to a resource conflict, such as a resource collision at the anchor user device, as discussed above).

At operation 86, a determination is made regarding whether the third user device should act as the substitute anchor device. This determination may be based, at least in part, on whether said trigger is detected (in the operation 84). The determination may also be based, at least in part, on whether the third user device is one of one or more candidate substitute anchor devices. If a determination is made (in the operation 86) that the third user device should act at the substitute anchor device, then sidelink positioning assistance is provided to the target user device in the operation 88; otherwise the algorithm moves to operation 89, where the algorithm terminates. The operation 88 may comprise transmitting a sidelink positioning reference signal and providing position data (e.g. in accordance with a configuration) for the third user device to the target user device. The algorithm 80 then terminates at the operation 89.

FIG. 9 is a flow chart, indicated generally by the reference numeral 90, in accordance with an example embodiment.

The algorithm 90 starts at operation 91, where a slink positioning signal (e.g. SL- PRS_T) is transmitted by a target user device (UE-T) to an anchor user device (UE-A). The target and anchor user devices may be the user devices 52 and 54 described above, respectively.

At operation 92, a third user device (such as the third user device 56 described above) checks whether it has been explicitly identified by the target user device as a substitute anchor user device in place of anchor user device by means of an indication such as a SL-PRS transmission. If not, the algorithm 90 moves to operation 93, where the third user device determines whether it has been identified as a substitute anchor user device by pre-configuration during anchor user device selection (e.g. on receipt of a configuration message). If the third user device is determined in either the operation 92 or the operation 93 to be the substitute anchor user device, then the algorithm 90 proceeds to operation 96; otherwise the algorithm process to operation 94.

At operation 94, the third user device checks autonomously if the anchor user device is the expected responder. If not, the algorithm moves to operation 95; otherwise, the algorithm moves to operation 97. At operation 95, a determination is made regarding whether the third user device is close to the anchor user device (distance-based criteria for autonomous determination). If so, the algorithm 90 moves to operation 96; otherwise the algorithm moves to operation 97.

At operation 96, a determination is made regarding whether a resource collision is detected (e.g. at the anchor user device). If so, the algorithm moves to operation 98, where the third user device provides the requested sidelink positioning assistance (in place of the anchor user device). If not, the algorithm terminates at operation 97, without the third user device providing sidelink positioning assistance.

For completeness, FIG. 10 is a schematic diagram of components of one or more of the example embodiments described previously, which hereafter are referred to generically as a processing system 300. The processing system 300 may, for example, be (or may include) the apparatus referred to in the claims below.

The processing system 300 may have a processor 302, a memory 304 coupled to the processor and comprised of a random access memory (RAM) 314 and a read only memory (ROM) 312, and, optionally, a user input 310 and a display 318. The processing system 300 may comprise one or more network/ apparatus interfaces 308 for connection to a network/ apparatus, e.g. a modem which may be wired or wireless.

The network/ apparatus interface 308 may also operate as a connection to other apparatus such as device/ apparatus which is not network side apparatus. Thus, direct connection between devices/apparatus without network participation is possible.

The processor 302 is connected to each of the other components in order to control operation thereof. The memory 304 may comprise a non-volatile memory, such as a hard disk drive (HDD) or a solid state drive (SSD). The ROM 312 of the memory 304 stores, amongst other things, an operating system 315 and may store software applications 316. The RAM 314 of the memory 304 is used by the processor 302 for the temporary storage of data. The operating system 315 may contain code which, when executed by the processor implements aspects of the methods, algorithms and message flow sequences 20, 60, 70, 80 and 90 described above. Note that in the case of small device/apparatus the memory can be most suitable for small size usage i.e. not always a hard disk drive (HDD) or a solid state drive (SSD) is used.

The processor 302 may take any suitable form. For instance, it may be a microcontroller, a plurality of microcontrollers, a processor, or a plurality of processors. The processing system 300 may be a standalone computer, a server, a console, or a network thereof. The processing system 300 and needed structural parts maybe all inside device/apparatus such as loT device/apparatus i.e. embedded to very small size.

In some example embodiments, the processing system 300 may also be associated with external software applications. These may be applications stored on a remote server device/apparatus and may run partly or exclusively on the remote server device/apparatus. These applications maybe termed cloud-hosted applications. The processing system 300 maybe in communication with the remote server device/apparatus in order to utilize the software application stored there.

FIG. 11 shows tangible media, specifically a removable memory unit 365, storing computer-readable code which when run by a computer may perform methods according to example embodiments described above. The removable memory unit 365 may be a memory stick, e.g. a USB memory stick, having internal memory 366 for storing the computer-readable code. The internal memory 366 may be accessed by a computer system via a connector 367. Other forms of tangible storage media may be used. Tangible media can be any device/apparatus capable of storing data/information which data/information can be exchanged between devices/apparatus/network. Embodiments of the present invention may be implemented in software, hardware, application logic or a combination of software, hardware and application logic. The software, application logic and/or hardware may reside on memory, or any computer media. In an example embodiment, the application logic, software or an instruction set is maintained on any one of various conventional computer-readable media. In the context of this document, a “memory” or “computer-readable medium” maybe any non-transitory media or means that can contain, store, communicate, propagate or transport the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer.

Reference to, where relevant, “computer-readable medium”, “computer program product”, “tangibly embodied computer program” etc., or a “processor” or “processing circuitry” etc. should be understood to encompass not only computers having differing architectures such as single/multi-processor architectures and sequencers/parallel architectures, but also specialised circuits such as field programmable gate arrays

FPGA, application specify circuits ASIC, signal processing devices/ apparatus and other devices/apparatus. References to computer program, instructions, code etc. should be understood to express software for a programmable processor firmware such as the programmable content of a hardware device/apparatus as instructions for a processor or configured or configuration settings for a fixed function device/apparatus, gate array, programmable logic device/apparatus, etc.

If desired, the different functions discussed herein maybe performed in a different order and/or concurrently with each other. Furthermore, if desired, one or more of the above-described functions may be optional or may be combined. Similarly, it will also be appreciated that the flow diagrams and message flow sequences of FIGS. 2 and 6 to 9 are examples only and that various operations depicted therein may be omitted, reordered and/ or combined. It will be appreciated that the above described example embodiments are purely illustrative and are not limiting on the scope of the invention. Other variations and modifications will be apparent to persons skilled in the art upon reading the present specification. Moreover, the disclosure of the present application should be understood to include any novel features or any novel combination of features either explicitly or implicitly disclosed herein or any generalization thereof and during the prosecution of the present application or of any application derived therefrom, new claims may be formulated to cover any such features and/or combination of such features. Although various aspects of the invention are set out in the independent claims, other aspects of the invention comprise other combinations of features from the described example embodiments and/ or the dependent claims with the features of the independent claims, and not solely the combinations explicitly set out in the claims. It is also noted herein that while the above describes various examples, these descriptions should not be viewed in a limiting sense. Rather, there are several variations and modifications which may be made without departing from the scope of the present invention as defined in the appended claims.