Positioning protocol enhancements for sidelink positioning

Abstract

The disclosure relates to techniques for positioning protocol enhancements for sidelink positioning. In one example, a method to be performed by a first user equipment (UE) includes receiving a positioning message over a sidelink interface between the first UE and a second UE; generating, by the first UE, a response to the positioning message; and sending the response to the second UE through the sidelink interface.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. Provisional Application No. 63 / 395,526, filed on August 5, 2022, entitled “POSITIONING PROTOCOLENHANCEMENTS FOR SIDELINK POSITIONING,” which is incorporated herein by reference in its entirety. Background Art

[0003] Wireless communication networks provide integrated communication platforms and telecommunication services to wireless user devices. Example telecommunication services include telephone, data (e.g., voice, audio and / or video data), messaging, Internet access and / or other services. Wireless communication networks have wireless access nodes that exchange wireless signals with wireless user devices using wireless network protocols (such as protocols described in various telecommunication standards promulgated by the Third Generation Partnership Project (3GPP)). Example wireless communication networks include time division multiple access (TDMA) networks, frequency division multiple access (FDMA) networks, orthogonal frequency division multiple access (OFDMA) networks, long term evolution (LTE) and fifth generation new radio (5G NR). Wireless communication networks use technologies such as OFDM, multiple input multiple output (MIMO), advanced channel coding, massive MIMO, beamforming and / or other features to facilitate mobile broadband services.

[0004] Recently, wireless communication networks have been extended to allow user equipment (UE) to connect directly to each other using a technology known as sidelink communication. This allows UEs to communicate with each other without relying on the radio access network as an intermediary. By using sidelink communication, UEs can exchange data at high data rates and with low latency even when one or both UEs are out of network coverage. Summary of the invention

[0005] The present disclosure describes techniques for positioning protocol enhancements for sidelink positioning. These techniques may be used to implement positioning protocols such as the Long Term Evolution (LTE) Positioning Protocol (LPP) in a manner that enables positioning protocols such as the Long Term Evolution (LTE) Positioning Protocol (LPP) to be used between UEs over a sidelink (including scenarios where the UE is out of coverage). According to one aspect of the present disclosure, an enhanced sidelink protocol stack is described to carry LPP. Specifically, a new LPP transmission mechanism for the sidelink is disclosed that adds and / or enhances messages to support LPP transmissions over, for example, PC5-RRC, PC5-S, and / or Packet Data Convergence Protocol (PDCP). Enhancements to LPP functionality are also disclosed to support capability transfer, auxiliary data transfer, location information transfer, and other functionality over the sidelink.

[0006] In general, in one aspect, a method to be performed by a first user equipment (UE) includes: receiving a positioning message via a sidelink interface between the first UE and a second UE; generating a response to the positioning message by the first UE; and sending the response to the second UE via the sidelink interface.

[0007] Generally, on the one hand, a device such as a first UE includes: one or more processors, and a memory storing instructions, which can be executed by the one or more processors to: receive a positioning message through a side link interface between the device and a second device (e.g., a second UE), generate a response to the positioning message by the device, and send the response to the second device through the side link interface.

[0008] In general, on the one hand, a system includes: one or more processors, and a memory storing instructions, which can be executed by the one or more processors to: receive a positioning message through a side link interface between a first UE and a second UE, generate a response to the positioning message by the first UE, and send the response to the second UE through the side link interface.

[0009] Generally, in one aspect, a non-transitory computer-readable medium stores instructions that can be executed by one or more processors to cause the one or more processors to: receive a positioning message via a side link interface between a first UE and a second UE, generate a response to the positioning message by the first UE, and send the response to the second UE via the side link interface.

[0010] Generally, on the one hand, one or more processors of a first UE are configured to cause the first UE to perform operations including: receiving a positioning message via a side link interface between the first UE and a second UE; generating a response to the positioning message by the first UE; and sending the response to the second UE via the side link interface.

[0011] Generally, in one aspect, one or more processors of a first UE are configured to cause the first UE to perform operations, the operations comprising: receiving a positioning message through a side link interface between the first UE and a second UE, wherein the positioning message comprises at least one of a dedicated positioning message received through PC5-RRC, a broadcast positioning message received through PC5-S, or a positioning system information block (posSIB); generating, by the first UE, a response to the positioning message; and sending the response to the second UE through the side link interface.

[0012] The foregoing and other aspects may each optionally include one or more of the following features, alone or in combination.

[0013] In some examples, the side link interface is a PC5 interface. In some examples, receiving the positioning message via the side link interface includes receiving the positioning message via PC5-RRC or a packet data convergence protocol (PDCP). In some examples, receiving the positioning message via the side link interface includes receiving a broadcast of the positioning message via PC5-S.

[0014] In some examples, the positioning message includes a long term evolution positioning protocol (LPP) message. In some examples, the positioning message includes a sidelink specific LPP message or a sidelink specific information element. In some examples, the operations include receiving an LPP message via a sidelink interface, the LPP message including an information element including the positioning message.

[0015] In some examples, the operations include receiving a shared control channel (SCCH) message via a side link interface, the SCCH message including a positioning message. In some examples, the operations include receiving a radio resource control (RRC) reconfiguration side link message or an RRC reconfiguration complete side link message including a positioning message via a side link interface.

[0016] In some examples, the operations include decoding the positioning message to determine one or more of: a sidelink positioning method supported by the second UE, a bandwidth supported by the second UE, or whether the second UE knows its absolute coordinates.

[0017] In some examples, the operations include decoding the positioning message to determine the absolute coordinates of the second UE. In some examples, the operations include decoding the positioning message to determine a sidelink positioning reference signal configuration of the second UE.

[0018] In some examples, the positioning message includes a request for a positioning measurement, and the operations include performing a positioning measurement based on the request, and generating a response to the positioning message, the response including the positioning measurement.

[0019] In some examples, the positioning message includes a request for the location of the first UE, and the operations include: determining, by the first UE, the location of the first UE, and generating a response to the positioning message, the response including the location of the first UE.

[0020] The details of one or more embodiments of these systems and methods are set forth in the following drawings and description. Other features, objects, and advantages of these systems and methods will be apparent from the description and drawings, and from the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] Figure 1 An example positioning architecture for a wireless communication system is illustrated.

[0022] Figure 2 An example protocol stack is illustrated.

[0023] Figure 3 An example wireless communication system including sidelink communications is illustrated.

[0024] Figure 4 An example sidelink positioning architecture is illustrated.

[0025] Figure 5 , Figure 6 and Figure 7 Each illustrates an example of an enhanced protocol stack.

[0026] Figure 8 A flow chart of an example sidelink positioning process is illustrated.

[0027] Fig. 9 A user equipment (UE) according to some embodiments is illustrated.

[0028] Fig.10 An access node according to some embodiments is illustrated. DETAILED DESCRIPTION

[0029] Some wireless communication systems (including those configured according to the 3rd Generation Partnership Project (3GPP) wireless communication standards) include functionality for determining the geographic location of a user equipment (UE). Once determined, the location of the UE can be used to support radio resource management functions, as well as location-based services (such as navigation, positioning, and emergency services, etc.).

[0030] To support the positioning of UE, the wireless communication system may include a positioning framework. For example, Figure 1 A positioning architecture 100 of a wireless communication system according to some implementations is shown. In this example, the wireless communication system includes a radio access network (RAN) and a core network (CN), each of which includes multiple entities that make up the positioning architecture 100. For example, the CN may include an access and mobility management function (AMF) 102 and a location management function (LMF) 104. The RAN may be a next generation (NG) radio access network (NG-RAN) 106, which includes a gNB 108 and / or an eNB 110. The gNB 108 and / or the eNB 110 may include one or more transmit / receive points (TRPs). A TRP is a set of geographically co-located antennas (e.g., an antenna array including one or more antenna elements) that supports transmit and / or receive functionality with a UE (such as UE 112) in a particular area.

[0031] In operation, the AMF 102 may receive a request for location services associated with the UE 112 from another entity (e.g., a UE or a Gateway Mobile Location Center [GMLC]), or the AMF 102 itself may decide to initiate location services on behalf of the UE 112 (e.g., to locate the UE for an emergency call). The AMF 102 may then send a location service request to the LMF 104. The LMF 104 processes the location service request, which may include determining the location of the UE 112, delivering assistance data to the UE 112 to assist in UE-based and / or UE-assisted positioning, etc. The LMF 104 may then return the result of the location service (e.g., a position estimate for the UE 112) to the AMF 102. In the event that the location service is requested by an entity other than the AMF 102 (e.g., a GMLC or a UE), the AMF 102 may return the location service result to this entity.

[0032] As described above, the LMF 104 may interact with the UE 112 to obtain a position estimate or positioning measurements, or to deliver assistance data to the UE, etc. To this end, the LMF 104 may utilize a positioning protocol, such as the Long Term Evolution (LTE) Positioning Protocol (LPP). In general, the LPP is a point-to-point protocol used between a positioning server (e.g., the LMF 104 in the control plane or the SLP in the user plane) and a target device (e.g., the UE 112 in the control plane or the SET in the user plane). The LPP may use various protocols as underlying transports, including (but not limited to) control plane and user plane protocols. For example, in the control plane case, LPP messages (e.g., LPP protocol data units [PDUs]) may be transmitted between the LMF 104 and the UE 112 over a non-access stratum (NAS), such as Figure 2 200 in FIG. 1. Other LPP configurations and underlying transports may be used without departing from the scope of the present disclosure.

[0033] Recently, wireless communication networks have been extended to allow UEs to communicate directly with each other via side links. One of the goals of Release 18 (Rel-18) of the 3GPP communication standard is to support side link positioning, including when the UE is out of coverage (e.g., out of communication range or otherwise unable to communicate with the RAN and / or CN). However, when the UE is out of coverage, there is no connection to the wireless communication network, and therefore there is no connection to the LMF (or another positioning server). Therefore, the positioning function provided by the LPP cannot be used.

[0034] The present disclosure describes techniques for implementing LPP in a manner that enables LPP to be used between UEs over a sidelink, including scenarios where the UE is out of coverage. According to one aspect of the present disclosure, a sidelink protocol stack enhancement that carries LPP over a sidelink is described. Specifically, a new LPP transmission mechanism for a sidelink is disclosed that adds and / or enhances messages to support LPP transmission over, for example, PC5-RRC, PC5-S, and / or a packet data convergence protocol (PDCP) interface. Enhancements to LPP functionality are also disclosed to support capability transfer, auxiliary data transfer, location information transfer, and other functionality over a sidelink. Although aspects of the present disclosure are described in the context of LPP, these aspects may be applied to other positioning protocols (or used to define a new sidelink positioning protocol) without departing from the scope of the present disclosure.

[0035] refer to Figure 3 , shows an example wireless communication system 300 including sidelink communication. Note that Figure 3 The system is only one example of a possible system, and those features of the present disclosure may be implemented in other wireless communication systems.

[0036] The following description is provided for an example communication system 300 operating in conjunction with a fifth generation (5G) network provided by a 3GPP technical specification (TS). However, the example implementation is not limited in this regard, and the described implementation may be applied to other networks that may benefit from the principles described herein, such as 3GPP Long Term Evolution (LTE) networks, Wi-Fi networks, etc. In addition, other types of communication standards are also possible, including future 3GPP systems (e.g., sixth generation (6G)) systems. Although various aspects may be described herein using terms typically associated with 5G NR, various aspects of the present disclosure may be applied to other systems, such as 3G, 4G, and / or systems after 5G (e.g., 6G).

[0037] like Figure 3 As shown, the communication system 300 includes a UE 305 (UE 305-1 and UE 305-2 are collectively referred to as "UE 305" or "multiple UE 305s"), a base station 310 (base station 310-1 and base station 310-2 are collectively referred to as "base station 310" or "multiple base stations 310"), a cell 315 (cell 315-1 and cell 315-2 are collectively referred to as "cell 315" or "multiple cells 315"), and one or more servers 335 in a core network (CN) 340 connected to the Internet 345.

[0038] In some examples, UE 305 can be a physical hardware device that runs one or more applications and is capable of communicating with one or more base stations 310 and / or other UEs. Radio link 320 (radio link 320-1 and radio link 320-2 are collectively referred to as "radio link 320" or "multiple radio links 320") allows UE 305 to send and receive data from base station 310 providing link 320. In some examples, radio link 320 can be a Uu interface (e.g., NR-Uu and / or LTE-Uu, etc.) between UE 305 and base station 310. Side link interface 325 can allow UE 305 to send and receive data directly to each other (e.g., without the need for intermediary infrastructure equipment such as base station 310). In some examples, side link 325 can be a PC5 interface between UE 305 (and / or other UEs, such as roadside unit [RSU] UEs). The PC5 and Uu interfaces are used as examples only, and as used herein, PC5 may represent various other possible wireless communication technologies that allow direct sidelink communication between user equipment, while Uu may represent cellular communication between user equipment and infrastructure equipment (such as a base station). In some examples, the base stations 310 can communicate with each other via a backhaul connection 330 (e.g., an X2 interface) and can communicate with one or more servers 335 within a core network (CN) 340 via other connections 333 (e.g., NG-C or NG-U).

[0039] In order to transmit / receive data to / from one or more base stations 310 or other UEs, UE 305 may include a transmitter / receiver (or alternatively, a transceiver), a memory, one or more processors, and / or other similar components that enable UE 305 to operate according to one or more wireless communication protocols and / or one or more cellular communication protocols. UE 305 may have multiple antenna elements that enable UE 305 to maintain multiple links 320 and / or side links 325 to transmit / receive data to / from multiple base stations 310 and / or multiple UEs 305. For example, as Figure 3 As shown, UE 305-1 may be connected to base station 310-1 via link 320-1 and simultaneously connected to UE 305-2 via side link 325. In some examples, one or both of UEs 305 may be outside the coverage of base station 310 (e.g., outside cell 315 and unable to communicate with base station 310), but may still communicate with each other via side link 325.

[0040] The side link 325 between UEs 305 may include a communication channel for transmitting data between UE 305-1 and UE 305-2 and / or between UE 305 and UE type RSU ( Figure 3The sidelink 325 may be a PC5 interface that includes, but is not limited to, a physical sidelink control channel (PSCCH), a physical sidelink shared channel (PSSCH), a physical sidelink discovery channel (PSDCH), and a physical sidelink broadcast channel (PSBCH). In some examples, the sidelink 325 may operate on an unlicensed spectrum (e.g., in the unlicensed 5 gigahertz (GHz) and 6 GHz bands) or a (licensed) shared spectrum. The UE 305 may use the PC5 interface for radio resource control (RRC) signaling (e.g., PC5-RRC) exchanges between UEs, as well as other protocols (e.g., PC5-S and / or PDCP).

[0041] In some examples, UE 305 is configured to use a resource pool for sidelink communication. The sidelink resource pool can be divided into multiple time slots, frequency channels, and frequency subchannels. In some examples, UE 305 is synchronized and performs sidelink transmission aligned with time slot boundaries. It is expected that the UE selects several time slots and subchannels for the transmission of a transport block. In some examples, the UE can use different subchannels to send a transport block across multiple time slots within its own resource selection window, which can be determined using packet delay budget information.

[0042] In some examples, the communication system 300 is configured to perform sidelink positioning for one or both of the UEs 305 served by the communication system 300. For example, the CN 340 of the communication system 300 may include a positioning server such as an LMF (not shown) that is configured to interact with the UE 305 to obtain a position estimate or positioning measurement, or to deliver assistance data to the UE 305, etc. However, as described above, in some scenarios, the UE may not be able to connect to the communication system 300 (e.g., due to being outside the coverage area of ​​the base station 310) and therefore cannot communicate with the LMF (or another positioning server). Therefore, the positioning functionality provided by the LPP terminated at the LMF cannot be used.

[0043] According to one aspect of the present disclosure, the sidelink protocol stack may be enhanced to support LPP (or another positioning protocol) on the sidelink. These enhancements may enable LPP messages to be transmitted over a sidelink interface (e.g., PC5 interface) between UEs, such as Figure 4 By enhancing the sidelink protocol in this way, the techniques described herein enable UE positioning on the sidelink, including when the UE is out of coverage.

[0044] In some examples, a new LPP transport mechanism for the sidelink may be defined on top of PC5-RRC, such as Figure 5As shown in the enhanced protocol stack 500 in FIG. 1 . For example, a new PC5-RRC procedure / message (referred to herein as "information transfer") may be defined to carry LPP messages on the side link. In some examples, the information transfer message may be incorporated into the SCCH-Message class and may carry the LPP PDU in an OCTET STRING container, as shown in the following table.

[0045]

[0046] In some examples, transmission of LPP messages over the sidelink may be accomplished by means other than the definition of new messages. For example, the RRCReconfigurationSidelink and / or RRCReconfigurationCompleteSidelink messages (or another message in the SCCH-Message class) may be extended with a new container information element (IE) to carry LPP messages on the sidelink. As another example, new sidelink signal radio bearers (SRBs) and / or logical channel identifiers (LCIDs) may be defined to carry LPP messages over PDCP (e.g., as a replacement or supplement to RRC). For example, a new LCID (e.g., in the range 20 to 61 of Table 6.2.4-1 in 3GPP TS 36.321 Version 17.1.0 and / or 3GPP TS 38.321 Version 17.1.0) may be reserved for LPP transmissions over the sidelink. This modification is accomplished by Figure 6 The enhanced protocol stack 600 is shown in FIG.

[0047] In some scenarios, positioning assistance information is delivered via positioning system information blocks (posSIBs) in addition to dedicated LPP signaling. However, some sidelink implementations may not support SIB delivery. According to one aspect of the present disclosure, dedicated LPP signaling may be used to deliver positioning assistance data. In some examples, the sidelink protocol stack may be enhanced to support SIB delivery by, for example, defining and / or extending messages on PC5-RRC, PDCP to carry posSIBs in a manner similar to Uu. In some examples, upper layer protocols (e.g., PC5-S) may be extended to support broadcasting of positioning assistance data, such as Figure 7 As shown in the enhanced protocol stack 700.

[0048] According to one aspect of the present disclosure, LPP functionality may be enhanced to support UE positioning via a sidelink. To this end, new sidelink-specific functionality may be added to the LPP functionality and / or existing LPP functionality may be extended to support sidelink operations. Enhancements to LPP functionality may include, but are not limited to, enhancements to capability delivery, auxiliary data delivery, and / or location information delivery.

[0049] In some examples, sidelink specific functionality is added to some or all LPP IEs. For example, the sidelink specific functionality may be added by extending the data carried by some or all of RequestCapabilities, ProvideCapabilities, RequestAssistanceData, ProvideAssistanceData, RequestLocationInformation, and ProvideLocationInformation included in the LPP-MessageBody in the 3GPP standard. Alternatively or in addition, a new sidelink specific LPP message is defined (e.g., SL-LPP-Message, which may be similar to the LPP-Message in the 3GPP standard). This may be beneficial in cases where the sidelink requires transport layer enhancements that are not supported by LPP. In some examples, a new sidelink specific LPP advanced IE is defined (e.g., SL-LPP-MessageBody, which may be similar to the LPP-MessageBody defined in the 3GPP standard). This may be beneficial in cases where it is desired to keep sidelink related positioning functionality separate from legacy positioning. In some examples, the LPP-MessageBody itself may remain unchanged.

[0050] In some examples, to support LPP capability transfer over the sidelink, an NR-SL-RequestCapabilities IE is added to RequestCapabilities and / or an NR-SL-ProvideCapabilities IE is added to ProvideCapabilities. In some examples, new functionality to support sidelink capability transfer may be added, including, but not limited to, one or more of the following: supported sidelink positioning methods (e.g., sidelink time difference of arrival [TDOA], sidelink round trip time [RTT], sidelink angle of arrival [AoA], sidelink angle of departure [AoD]); supported bandwidths; and / or supported bands and frequency ranges. One or more of these new features may be implemented by extending or adding messages within the sidelink protocol stack, as described herein.

[0051] In general, LPP may be used to measure or otherwise estimate the absolute coordinates of a UE. However, when the UE is mobile, measurement of absolute coordinates may not be possible in the sidelink due to the lack of a fixed reference point. However, if one of the UEs is fixed, such as in the case of a UE type RSU, the fixed UE may have known absolute coordinates that the UE may use to measure its own absolute coordinates on the sidelink. Therefore, in some examples, a new sidelink capability transfer function may be added to indicate that the absolute coordinates are known (e.g., in the case of a UE type RSU).

[0052] In some examples, to support LPP auxiliary data delivery over the side link, an NR-SL-RequestAssistanceData IE is added to RequestAssistanceData, and / or an NR-SL-ProvideAssistanceData IE is added to ProvideAssistanceData. In some examples, new functionality to support sidelink auxiliary data delivery may be added, including (but not limited to) known absolute coordinates and / or sidelink positioning reference signal (PRS) configurations. As discussed herein, sidelink positioning assistance data may be delivered over the side link using dedicated LPP signaling, posSIB in the sidelink SIB, and / or broadcast over PC5-S, etc. One or more of these new features may be implemented by extending or adding messages within the sidelink protocol stack, as described herein.

[0053] In some examples, to support LPP location information delivery over the sidelink, an NR-SL-XYZ-RequestLocationInformation IE is added to RequestLocationInformation and / or an NR-SL-XYZ-ProvideLocationInformation IE is added to ProvideLocationInformation, where "XYZ" is a positioning method supported on the sidelink (e.g., sidelink TDOA, sidelink RTT, sidelink AoA, sidelink AoD).

[0054] In some examples, for each positioning method, two IEs may be included: a measurement information element (e.g., NR-SL-TDOA-SignalMeasurementInformation) for carrying the corresponding measurement, and a location information element (e.g., NR-SL-TDOA-LocationInformation) for carrying the location estimated using the corresponding positioning method. In the former case, a first UE (e.g., UE1) requests a second UE (e.g., UE2) to perform, for example, a sidelink TDOA measurement, and UE2 reports the measurement to UE1 to enable UE1 to calculate the location of UE2. In the latter case, UE1 calculates its position and may provide its position estimate to UE2. Even if the LPP is peer-to-peer, a UE will typically still need to perform PRS measurements with at least three other UEs to calculate its absolute position. When only ranging is required (e.g., with SL RxTx time difference measurement or other RTT measurement), the procedure may be performed only between two UEs.

[0055] Figure 8 A flow chart of an example process 800 according to some specific implementations is illustrated. For clarity of presentation, the following description generally describes the method 800 in the context of other figures in this specification. For example, the process 800 may be performed by a first UE (e.g., Figure 3 It should be understood that process 800 may be performed by, for example, any suitable system, environment, software, hardware, or a combination of systems, environments, software, and hardware. In some specific implementations, the steps of process 800 may be executed in parallel, in combination, in a loop, or in any order.

[0056] The operations of process 800 include receiving a positioning message (802) via a side link interface between a first UE and a second UE. For example, the first UE may be UE 305-1, which receives a positioning message from a second UE 305-2 via a side link interface 325, which may be a PC5 interface. In some examples, the positioning message is an LPP positioning message received via the side link interface. One or both of the UEs may be outside the coverage of the network (e.g., outside of cell 315 or otherwise unable to communicate with base station 310).

[0057] In some examples, the positioning message is received via PC5-RRC. For example, the positioning message may be included in an SCCH message received via PC5-RRC on a side link interface. As another example, an RRCReconfigurationSidelink or RRCReconfigurationCompleteSidelink message including the positioning message may be received via PC5-RRC on a side link interface. In some examples, the positioning message may be received via other transport protocols such as PDCP or PC5-S. In some examples, any combination of the above may be used to receive the positioning message.

[0058] In some examples, the positioning message includes a sidelink specific LPP message (e.g., SL-LPP-Message, which may be similar to LPP-Message) or a sidelink specific IE (e.g., SL-LPP-MessageBody, which may be similar to LPP-MessageBody). In some examples, an LPP-MessageBody message / IE may be received over a sidelink interface, the LPP-MessageBody message / IE including an IE containing the positioning message. For example, the received LPP-MessageBody may include a sidelink specific IE carrying the positioning message in one of RequestCapabilities, ProvideCapabilities, RequestAssistanceData, ProvideAssistanceData, RequestLocationInformation, or ProvideLocationInformation. In some examples, the positioning message includes any combination of the above.

[0059] After receiving the positioning message, the first UE may generate a response (804). In some examples, the first UE decodes the positioning message and responds accordingly. For example, the first UE may decode the positioning message to determine capability information about the second UE, such as one or more sidelink positioning methods supported by the second UE, bandwidth supported by the second UE, and / or whether the second UE knows its absolute coordinates. In some examples, the first UE may decode the positioning message to obtain assistance data from the second UE, such as the absolute coordinates of the second UE and / or the sidelink positioning reference signal configuration of the second UE.

[0060] The first UE then sends the generated response to the second UE via the sidelink interface (806). For example, the positioning message may include a request for positioning measurements (which may include an indication of a particular sidelink positioning method). In response, the first UE may perform positioning measurements (e.g., based on the positioning method indicated in the request) and generate a response including the positioning measurements. The second UE may then use the positioning measurements included in the response to calculate the position of the first UE. As another example, the positioning message may include a request for the position of the first UE, and the first UE may calculate its position and include it in a response sent to the second UE via the sidelink interface.

[0061] Although process 800 is described in the context of a first UE receiving a positioning message and generating a response, it will be apparent in light of this disclosure that the process may be performed from the perspective of a first UE sending a positioning message and receiving a response.

[0062] Fig. 9 UE 900 according to some embodiments is shown. UE 900 may be similar to Figure 3 UE 305 and is essentially interchangeable therewith.

[0063] UE 900 can be any mobile or non-mobile computing device, such as, for example, a mobile phone, a computer, a tablet, an industrial wireless sensor (e.g., microphone, carbon dioxide sensor, pressure sensor, humidity sensor, thermometer, motion sensor, accelerometer, laser scanner, fluid level sensor, inventory sensor, voltage / current meter, actuator, etc.), video monitoring / surveillance equipment (e.g., camera, camcorder, etc.), a wearable device (e.g., a smart watch), or a loose IoT device.

[0064] The UE 900 may include a processor 902, an RF interface circuit 904, a memory / storage device 906, a user interface 908, a sensor 910, a driver circuit 912, a power management integrated circuit (PMIC) 914, one or more antennas 916, and a battery 918. The components of the UE 900 may be implemented as an integrated circuit (IC), a portion of an integrated circuit, a discrete electronic device or other module, logic component, hardware, software, firmware, or a combination thereof. Fig. 9 The block diagram of UE 900 is intended to show a high-level view of certain of the components of UE 900. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may occur in other implementations.

[0065] Components of UE 900 may be coupled to various other components via one or more interconnects 920, which may represent any type of interface, input / output, bus (local, system, or extension), transmission line, trace, optical connection, etc., which allows various circuit components (on a common or different chip or chipset) to interact with each other.

[0066] The processor 902 may include processor circuits such as, for example, a baseband processor circuit (BB) 922A, a central processor unit circuit (CPU) 922B, and a graphics processor unit circuit (GPU) 922C. The processor 902 may include any type of circuit or processor circuit that executes or otherwise operates computer-executable instructions (such as program codes, software modules, or functional processes from the memory / storage device 906) to cause the UE 900 to perform operations as described herein.

[0067] In some embodiments, the baseband processor circuit 922A can access the communication protocol stack 924 in the memory / storage device 906 to communicate through a 3GPP compatible network. Generally speaking, the baseband processor circuit 922A can access the communication protocol stack to: perform user plane functions at the PHY layer, MAC layer, RLC layer, PDCP layer, SDAP layer, and PDU layer; and perform control plane functions at the PHY layer, MAC layer, RLC layer, PDCP layer, RRC layer, and non-access layer. In some embodiments, the PHY layer operation may be additionally / alternatively performed by components of the RF interface circuit 904. The baseband processor circuit 922A may generate or process a baseband signal or waveform that carries information in a 3GPP compatible network. In some embodiments, the waveform for NR may be based on cyclic prefix OFDM ("CP-OFDM") in the uplink or downlink, and discrete Fourier transform spread OFDM ("DFT-S-OFDM") in the uplink.

[0068] The memory / storage 906 may include one or more non-transitory computer-readable media including instructions (e.g., a communication protocol stack 924) that may be executed by one or more processors in the processor 902 to enable the UE 900 to perform various operations described herein. The memory / storage 906 includes any type of volatile or non-volatile memory that may be distributed throughout the UE 900. In some embodiments, some of the memory / storage 906 may be located on the processor 902 itself (e.g., L1 cache and L2 cache), while other memory / storage 906 is located outside the processor 902 but can be accessed via a memory interface. The memory / storage 906 may include any suitable volatile or non-volatile memory, such as, but not limited to, dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory, or any other type of memory device technology.

[0069] The RF interface circuit 904 may include a transceiver circuit and a radio frequency front end module (RFEM), which allows the UE 900 to communicate with other devices through a radio access network. The RF interface circuit 904 may include various elements arranged in a transmit path or a receive path. These elements may include, for example, switches, mixers, amplifiers, filters, synthesizer circuits, control circuits, etc.

[0070] In the receive path, the RFEM may receive the radiated signal from the air interface via one or more antennas 916 and proceed to filter and amplify the signal (using a low noise amplifier). The signal may be provided to a transceiver's receiver, which down-converts the RF signal to a baseband signal provided to a baseband processor of processor 902.

[0071] In the transmit path, the transmitter of the transceiver up-converts the baseband signal received from the baseband processor and provides the RF signal to the RFEM. The RFEM may amplify the RF signal through a power amplifier before the signal is radiated across the air interface via one or more antennas 916.

[0072] In various embodiments, the RF interface circuit 904 may be configured to send / receive signals in a manner compatible with NR access technology.

[0073] One or more antennas 916 may include antenna elements to convert electrical signals into radio waves to travel through the air and convert received radio waves into electrical signals. These antenna elements may be arranged into one or more antenna panels. Antenna 916 may have an antenna panel that is omnidirectional, directional, or a combination thereof to achieve beamforming and multiple input / multiple output communications. One or more antennas 916 may include microstrip antennas, printed antennas manufactured on the surface of one or more printed circuit boards, patch antennas, phased array antennas, etc. One or more antennas 916 may have one or more panels that are designed for a specific frequency band including a band in FRI or FR2.

[0074] The user interface 908 includes various input / output (I / O) devices designed to enable a user to interact with the UE 900. The user interface 908 includes input device circuits and output device circuits. The input device circuit includes any physical or virtual components for accepting input, including in particular one or more physical or virtual buttons (e.g., reset button), physical keyboards, keypads, mice, touch pads, touch screens, microphones, scanners, headphones, etc. The output device circuit includes any physical or virtual components for displaying information or otherwise conveying information (such as sensor readings, actuator positions, or other similar information). The output device circuit may include any number or combination of audio or visual displays, including in particular one or more simple visual outputs / indicators (e.g., binary state indicators, such as light emitting diodes "LEDs" and multi-character visual outputs), or more complex outputs, such as display devices or touch screens (e.g., liquid crystal displays "LCDs", LED displays, quantum dot displays, projectors, etc.), where the output of characters, graphics, multimedia objects, etc. is generated or produced by the operation of the UE 900.

[0075] Sensor 910 may include a device, module, or subsystem that is designed to detect events or changes in its environment and send information about the detected events (sensor data) to some other device, module, subsystem, etc. Examples of such sensors include, among others: an inertial measurement unit including an accelerometer, gyroscope, or magnetometer; a microelectromechanical system or nanoelectromechanical system including a three-axis accelerometer, three-axis gyroscope, or magnetometer; a level sensor; a flow sensor; a temperature sensor (e.g., a thermistor); a pressure sensor; a barometric pressure sensor; a gravity meter; an altimeter; an image capture device (e.g., a camera or a lensless aperture); a light detection and ranging sensor; a proximity sensor (e.g., an infrared radiation detector, etc.); a depth sensor; an ambient light sensor; an ultrasonic transceiver; a microphone or other similar audio capture device; and the like.

[0076] The driver circuit 912 may include software elements and hardware elements for controlling specific devices embedded in the UE 900, attached to the UE 900, or otherwise communicatively coupled to the UE 900. The driver circuit 912 may include separate drivers to allow other components to interact with or control various input / output (I / O) devices that may be present in the UE 900 or connected to the UE. For example, the driver circuit 912 may include: a display driver for controlling and allowing access to a display device, a touch screen driver for controlling and allowing access to a touch screen interface, a sensor driver for obtaining sensor readings of the sensor 910 and controlling and allowing access to the sensor 910, a driver for obtaining an actuator position of an electromechanical component or controlling and allowing access to an electromechanical component, a camera driver for controlling and allowing access to an embedded image capture device, and an audio driver for controlling and allowing access to one or more audio devices.

[0077] The PMIC 914 may manage power provided to various components of the UE 900. Specifically, with respect to the processor 902, the PMIC 914 may control power source selection, voltage scaling, battery charging, or DC-DC conversion.

[0078] In some embodiments, the PMIC 914 may control or otherwise be part of various power saving mechanisms of the UE 900, including DRX, as discussed herein. The battery 918 may power the UE 900, but in some examples, the UE 900 may be mounted in a fixed location and may have a power source coupled to the grid. The battery 918 may be a lithium-ion battery, a metal-air battery such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, etc. In some implementations, such as in vehicle-based applications, the battery 918 may be a typical lead-acid automotive battery.

[0079] Fig.10 An access node 1000 (e.g., a base station or gNB) according to some embodiments is shown. The access node 1000 may be similar to Figure 3 The access node 1000 may include a processor 1002, an RF interface circuit 1004, a core network (CN) interface circuit 1006, a memory / storage device circuit 1008, and one or more antennas 1010.

[0080] The components of access node 1000 may be coupled to various other components via one or more interconnects 1012. Processor 1002, RF interface circuitry 1004, memory / storage circuitry 1008 (including communication protocol stack 1014), one or more antennas 1010, and interconnects 1012 may be similar to those of reference 1. Figure 8Like-named elements are shown and described.For example, processor 1002 may include processor circuits such as, for example, baseband processor circuit (BB) 1016A, central processor unit circuit (CPU) 1016B, and graphics processor unit circuit (GPU) 1016C.

[0081] The CN interface circuit 1006 may provide connectivity to a core network (e.g., a 5GC using a 5th Generation Core Network (5GC) compatible network interface protocol such as a Carrier Ethernet protocol or some other suitable protocol). Network connectivity may be provided to / from the access node 1000 via optical fiber or wireless backhaul. The CN interface circuit 1006 may include one or more dedicated processors or FPGAs for communicating using one or more of the aforementioned protocols. In some implementations, the CN interface circuit 1006 may include multiple controllers for providing connectivity to other networks using the same or different protocols.

[0082] As used herein, the terms "access node", "access point", etc. may be described as equipment that provides radio baseband functionality for data and / or voice connections between a network and one or more users. These access nodes may be referred to as BS, gNB, RAN node, eNB, Node B, RSU, TRxP or TRP, etc., and may include ground stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographic area (e.g., a cell). As used herein, the terms "NG RAN node", etc. may refer to an access node 1000 (e.g., a gNB) operating in an NR or 5G system, and the terms "E-UTRAN node", etc. may refer to an access node 1000 (e.g., an eNB) operating in an LTE or 4G system. According to various embodiments, the access node 1000 may be implemented as one or more of a dedicated physical device such as a macrocell base station and / or a low power (LP) base station for providing a femtocell, picocell or other similar cell with a smaller coverage area, smaller user capacity or higher bandwidth than a macrocell.

[0083] In some embodiments, all or part of the access node 1000 may be implemented as one or more software entities running on a server computer as part of a virtual network that may be referred to as a CRAN and / or a virtual baseband unit pool (vBBUP). In these embodiments, the CRAN or vBBUP may implement a RAN functional split, such as a PDCP split, where the RRC and PDCP layers are operated by the CRAN / vBBUP and other L2 protocol entities are operated by the access node 1000; a MAC / PHY split, where the RRC, PDCP, RLC, and MAC layers are operated by the CRAN / vBBUP and the PHY layer is operated by the access node 1000; or a "lower PHY" split, where the RRC, PDCP, RLC, MAC layer, and upper portions of the PHY layer are operated by the CRAN / vBBUP and the lower portions of the PHY layer are operated by the access node 1000.

[0084] In the V2X scenario, the access node 1000 may be an RSU or act as an RSU. The term "road side unit" or "RSU" may refer to any traffic infrastructure entity used for V2X communication. The RSU may be implemented in or by a suitable RAN node or a stationed (or relatively stationed) UE, wherein an RSU implemented in or by a UE may be referred to as a "UE-type RSU", an RSU implemented in or by an eNB may be referred to as an "eNB-type RSU", an RSU implemented in or by a gNB may be referred to as a "gNB-type RSU", and so on.

[0085] For ease of description, various components may be described as performing one or more tasks. Such descriptions should be interpreted as including the phrase "configured to". The statement that a component is configured to perform one or more tasks is expressly intended not to invoke 35 U.S.C. §112(f) interpretation of that component.

[0086] For one or more embodiments, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, or methods described in the following example section. For example, the baseband circuit described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples described below. For another example, the circuits associated with the UE, base station, network element, etc. described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples described below in the example section.

[0087] Example

[0088] Embodiment 1 includes one or more processors of a first user equipment (UE), and the one or more processors are configured to cause the first UE to perform operations, and the operations include: receiving a positioning message through a side link interface between the first UE and a second UE; generating a response to the positioning message by the first UE; and sending the response to the second UE through the side link interface.

[0089] Embodiment 2 is one or more processors according to embodiment 1, wherein the side link interface comprises a PC5 interface.

[0090] Embodiment 3 is one or more processors according to embodiment 1 or 2, wherein the positioning message comprises a Long Term Evolution Positioning Protocol (LPP) message.

[0091] Embodiment 4 is one or more processors according to any one of embodiments 1 to 3, wherein receiving the positioning message through the side link interface includes receiving the positioning message through PC5-RRC.

[0092] Embodiment 5 is one or more processors according to any one of embodiments 1 to 4, and the operation also includes receiving a shared control channel (SCCH) message through the side link interface, and the SCCH message includes the positioning message.

[0093] Embodiment 6 is one or more processors according to any one of embodiments 1 to 5, and the operation also includes receiving a radio resource control (RRC) reconfiguration side link message or an RRC reconfiguration completion side link message including the positioning message through the side link interface.

[0094] Embodiment 7 is one or more processors according to any one of embodiments 1 to 6, wherein receiving the positioning message through the sidelink interface includes receiving the positioning message through a packet data convergence protocol (PDCP).

[0095] Embodiment 8 is one or more processors according to any one of embodiments 1 to 7, wherein receiving the positioning message through the side link interface includes receiving a broadcast of the positioning message through PC5-S.

[0096] Embodiment 9 is one or more processors according to any one of embodiments 1 to 8, wherein the positioning message includes a sidelink specific LPP message or a sidelink specific information element.

[0097] Embodiment 10 is one or more processors according to any one of embodiments 1 to 9, and the operation also includes receiving a long-term evolution positioning protocol (LPP) message through the side link interface, and the LPP message contains an information element including the positioning message.

[0098] Embodiment 11 is one or more processors according to any one of embodiments 1 to 10, and the operation also includes decoding the positioning message to determine one or more sidelink positioning methods supported by the second UE.

[0099] Embodiment 12 is one or more processors according to any one of embodiments 1 to 11, and the operation also includes decoding the positioning message to determine the bandwidth supported by the second UE.

[0100] Embodiment 13 is one or more processors according to any one of embodiments 1 to 12, and the operation also includes decoding the positioning message to determine whether the second UE knows its absolute coordinates.

[0101] Embodiment 14 is one or more processors according to any one of embodiments 1 to 13, and the operation also includes decoding the positioning message to determine the absolute coordinates of the second UE.

[0102] Embodiment 15 is one or more processors according to any one of embodiments 1 to 14, and the operation also includes decoding the positioning message to determine the sidelink positioning reference signal configuration of the second UE.

[0103] Embodiment 16 is one or more processors according to any one of embodiments 1 to 15, wherein the positioning message includes a request for a positioning measurement, and the operation further includes: performing the positioning measurement based on the request; and generating the response to the positioning message, the response including the positioning measurement.

[0104] Embodiment 17 is one or more processors according to any one of embodiments 1 to 16, wherein the positioning message includes a request for the location of the first UE, and the operation further includes: determining the location of the first UE by the first UE; and generating the response to the positioning message, the response including the location of the first UE.

[0105] Embodiment 18 is one or more processors according to any one of embodiments 1 to 17, wherein at least one of the first UE and the second UE is out of coverage of a wireless communication network.

[0106] Embodiment 19 includes one or more processors of a first user equipment (UE), the one or more processors being configured to cause the first UE to perform operations, the operations comprising: receiving a positioning message via a side link interface between the first UE and a second UE, wherein the positioning message comprises at least one of a dedicated positioning message received via PC5-RRC, a broadcast positioning message received via PC5-S, or a positioning system information block (posSIB); generating, by the first UE, a response to the positioning message; and sending the response to the second UE via the side link interface.

[0107] Embodiment 20 includes a non-transitory computer storage medium encoded with instructions executable by one or more processors to cause the one or more processors to perform operations according to any one of Embodiments 1-19.

[0108] Embodiment 21 includes a device comprising: one or more processors, and a memory storing instructions, wherein the instructions are executable by the one or more processors to cause the one or more processors to perform operations according to any one of embodiments 1 to 19.

[0109] Embodiment 22 includes a method for performing the operations according to any one of Embodiments 1 to 19.

[0110] Embodiment 23 includes a user equipment (UE), wherein the user equipment (UE) includes: one or more processors, and a memory, wherein the memory stores instructions, and the instructions are executable by the one or more processors to enable the one or more processors to perform operations according to any one of embodiments 1 to 19.

[0111] Embodiment 24 includes a system comprising: one or more processors, and a memory storing instructions, wherein the instructions are executable by the one or more processors to cause the one or more processors to perform operations according to any one of embodiments 1 to 19.

[0112] Embodiment 25 may include an apparatus comprising logical components, modules, or circuits for performing one or more elements of operations described or associated with any of Embodiments 1 to 19, or any other operations or processes described herein.

[0113] Embodiment 26 may include a method, technique or process described or associated with the operation of any one of Embodiments 1 to 19, or a portion or component thereof.

[0114] Embodiment 27 may include a device, such as user equipment, comprising: one or more processors, and one or more computer-readable media, wherein the one or more computer-readable media include instructions that, when executed by the one or more processors, cause the one or more processors to perform a method, technique, or process, or a portion thereof, described in or related to an operation described in any one of Embodiments 1 to 19.

[0115] Embodiment 28 may include a signal as described or related to any one of embodiments 1 to 19, or a portion or component thereof.

[0116] Embodiment 29 may include a datagram, information element, packet, frame, fragment, PDU or message, or a portion or component thereof, as described or related to any one of Embodiments 1 to 19 or otherwise described in the present disclosure.

[0117] Embodiment 30 may include a signal encoded with data as described or associated with any one of Embodiments 1 to 19, or a portion or component thereof, or otherwise described in this disclosure.

[0118] Embodiment 31 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors will cause the one or more processors to perform a method, technique, or process, or a portion thereof, described or related to the operation described in any one of Embodiments 1 to 19.

[0119] Embodiment 32 may include a computer program including instructions, wherein execution of the program by a processing element causes the processing element to perform a method, technique, or process, or a portion thereof, described in or related to the operation according to any one of Embodiments 1 to 19. The operations or actions performed by the instructions executed by the processing element may include the operations according to any one of Embodiments 1 to 19.

[0120] Embodiment 33 may include signals in a wireless network as shown and described herein.

[0121] Embodiment 34 may include a method of communicating in a wireless network as shown and described herein.

[0122] Embodiment 35 may include a system for providing wireless communication as shown and described herein. The operations or actions performed by the system may include operations according to any one of Embodiments 1 to 19.

[0123] Embodiment 36 may include an apparatus for providing wireless communication as shown and described herein. The operations or actions performed by the apparatus may include operations according to any one of Embodiments 1 to 19.

[0124] The previously described operations of Examples 1 to 19 can be implemented using a computer-implemented method; a non-transitory computer-readable medium storing computer-readable instructions to perform the computer-implemented method; and a computer system comprising a computer memory interoperably coupled to a hardware processor configured to execute the computer-implemented method or instructions stored on the non-transitory computer-readable medium.

[0125] Unless explicitly stated otherwise, any of the above embodiments may be combined with any other embodiment (or combination of embodiments). The foregoing description of one or more specific implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise form disclosed. Modifications and variations are possible in view of the above teachings or may be obtained from the practice of various embodiments.

[0126] Although the above embodiments have been described in considerable detail, numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. It is intended that the following claims be interpreted to include all such variations and modifications.

[0127] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of the authorized use should be clearly stated to users.

Claims

1. One or more processors of a first user equipment (UE), the one or more processors configured to cause the first UE to perform operations, the operations comprising: receiving a positioning message via a side link interface between the first UE and the second UE; Generating, by the first UE, a response to the positioning message; as well as The response is sent to the second UE via the sidelink interface.

2. The one or more processors of claim 1, wherein the side link interface comprises a PC5 interface.

3. The one or more processors of claim 1 or 2, wherein the positioning message comprises a Long Term Evolution Positioning Protocol (LPP) message.

4. The one or more processors of any one of claims 1 to 3, wherein receiving the positioning message through the side link interface comprises receiving the positioning message through PC5-RRC.

5. According to one or more processors of any one of claims 1 to 4, the operation also includes receiving a shared control channel (SCCH) message through the sidelink interface, the SCCH message including the positioning message.

6. According to one or more processors described in any one of claims 1 to 5, the operation also includes receiving a radio resource control (RRC) reconfiguration side link message or an RRC reconfiguration completion side link message including the positioning message through the side link interface.

7. The one or more processors of any one of claims 1 to 6, wherein receiving the positioning message via the sidelink interface comprises receiving the positioning message via a packet data convergence protocol (PDCP).

8. The one or more processors of any one of claims 1 to 7, wherein receiving the positioning message via the side link interface comprises receiving a broadcast of the positioning message via PC5-S.

9. The one or more processors of any one of claims 1 to 8, wherein the positioning message comprises a sidelink specific LPP message or a sidelink specific information element.

10. The one or more processors of any one of claims 1 to 9, the operations further comprising receiving a Long Term Evolution Positioning Protocol (LPP) message via the sidelink interface, the LPP message containing an information element comprising the positioning message.

11. The one or more processors of any one of claims 1 to 10, the operations further comprising decoding the positioning message to determine one or more sidelink positioning methods supported by the second UE.

12. The one or more processors of any one of claims 1 to 11, the operations further comprising decoding the positioning message to determine a bandwidth supported by the second UE.

13. The one or more processors of any one of claims 1 to 12, the operations further comprising decoding the positioning message to determine whether the second UE knows its absolute coordinates.

14. The one or more processors of any one of claims 1 to 13, the operations further comprising decoding the positioning message to determine the absolute coordinates of the second UE.

15. The one or more processors of any one of claims 1 to 14, the operations further comprising decoding the positioning message to determine a sidelink positioning reference signal configuration for the second UE.

16. The one or more processors of any one of claims 1 to 15, wherein the positioning message comprises a request for positioning measurements, the operations further comprising: performing the positioning measurement based on the request; as well as The response to the positioning message is generated, the response comprising the positioning measurement.

17. The one or more processors of any one of claims 1 to 16, wherein the positioning message comprises a request for a location of the first UE, the operations further comprising: determining, by the first UE, the location of the first UE; as well as The response to the positioning message is generated, the response comprising the location of the first UE.

18. The one or more processors of any one of claims 1 to 17, wherein at least one of the first UE and the second UE is out of coverage of a wireless communication network.

19. One or more processors of a first user equipment (UE), the one or more processors configured to cause the first UE to perform operations comprising: receiving a positioning message through a sidelink interface between the first UE and the second UE, wherein the positioning message comprises at least one of a dedicated positioning message received through PC5-RRC, a broadcast positioning message received through PC5-S, or a positioning system information block (posSIB); generating, by the first UE, a response to the positioning message; and The response is sent to the second UE via the sidelink interface.

20. A non-transitory computer storage medium encoded with instructions executable by one or more processors to cause the one or more processors to perform the operations of any one of claims 1 to 19.

21. A device comprising: One or more processors, and a memory storing instructions, the instructions being executable by the one or more processors to cause the one or more processors to perform the operations according to any one of claims 1 to 19.

22. A method for performing the operations according to any one of claims 1 to 19.

Images