Method and apparatus for sidelink positioning in mobile communications

Abstract

Examples related to sidelink positioning in mobile communications are described. In an example, an apparatus operating as a target user equipment (UE) determines whether the target UE requires support from a location server UE during a sidelink location request (LR). If the target UE requires support from a location server UE, the apparatus selects a location server UE. The apparatus performs UE positioning to determine a location of a target UE with or without selected location server UE support. In another example, an apparatus operating as a location server UE performs selection of the location server UE with a target UE or a location service (LCS) client in a sidelink LR procedure. Where the target UE requires support from a location server UE, the apparatus performs UE positioning to determine the location of the target UE.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] The present invention claims priority to U.S. Provisional Application No. 63 / 367,658, filed on July 5, 2022, which is incorporated herein by reference in its entirety. Technical Field

[0003] The present invention relates generally to mobile communications, and more particularly to sidelink positioning in mobile communications. Background Art

[0004] Unless otherwise stated, the approaches described in this section do not constitute prior art to the claims listed below, and the inclusion of this section is not an admission that they are prior art.

[0005] Cellular-based vehicle-to-everything (V2X) (e.g., long-term evolution (LTE) V2X or new radio (NR) V2X) is a radio access technology developed by the 3rd generation partnership project (3GPP) to support enhanced vehicle applications. In V2X, a direct radio link (also called a side link) can be established between two user equipment (UE) (e.g., installed on a vehicle). When the UE is within the coverage of the cellular network, the side link can operate under the control of the cellular network (e.g., for radio resource allocation). Alternatively, the side link can operate independently, for example, when no cellular network is present or reachable. In particular, side link communication is performed through a direct communication interface called the PC5 interface.

[0006] In wireless communications, such as mobile communications under 3GPP standards, including fifth generation (5G) NR and fourth generation (4G) LTE, UE positioning requires network participation to estimate the position of the UE. The current positioning framework in 5G NR generally requires network entities (including access and mobility management (AMF), location management function (LMF), gateway mobile location center (GMLC) and unified data management (UDM)), target UE and the location services (LCS) client to interact with each other in the positioning operation. However, in an end-to-end scenario, there will be no network participation in sidelink positioning, especially when no cellular network exists or is reachable. Therefore, there is a need to provide a signaling framework for sidelink positioning in mobile communications. Summary of the invention

[0007] The following summary is illustrative only and is not intended to be limiting in any way. That is, the following summary is provided to introduce the concepts, highlights, benefits and advantages of the novel and non-obvious technology described in the present invention. Selected embodiments are further described in the detailed description below. Therefore, the following summary is not intended to identify essential features of the claimed subject matter, nor is it intended to be used to determine the scope of the claimed subject matter.

[0008] The purpose of the present invention is to propose solutions, concepts, designs, systems, methods and devices related to side link positioning in mobile communications. It is believed that by implementing one or more of the proposed solutions described in the present invention, the above problems can be avoided or otherwise alleviated.

[0009] In one aspect, a method may include a processor of an apparatus operating as a target UE, determining whether the target UE requires support from a location server UE during a sidelink location request (LR) process. The method may also include the processor selecting a location server UE if the target UE requires support from a location server UE. The method further includes the processor performing UE positioning to determine a location of the target UE with or without support from the selected location server UE.

[0010] In another aspect, a method may include a processor of an apparatus operating as a location server UE performing location server UE selection with a target UE or a location services (LCS) client in a sidelink LR process. The method may also include the processor performing UE positioning to determine the location of the target UE if the target UE requires support from a location server UE.

[0011] In another aspect, the apparatus may include a transceiver that wirelessly communicates with one or more UEs during operation. The apparatus also includes a processor communicatively coupled to the transceiver. During operation, the processor may perform operations including determining whether the target UE requires support from a location server UE during a sidelink LR process. The processor may also perform operations including selecting a location server UE through the transceiver if the target UE requires support from a location server UE. The processor may further perform operations including performing UE positioning through the transceiver to determine the location of the target UE with or without support from the selected location server UE.

[0012] It is worth noting that although the description provided by the present invention may be about some radio access technologies, networks and network topologies, for example, in networks such as LTE, enhanced LTE, enhanced LTE-Pro, 5G, NR, Internet-of-Things (IoT) and narrowband Internet of Things (NB-IoT), Industrial Internet of Things (IIoT) and 6th Generation (6G), etc., the proposed concepts, schemes and any variants / derivations thereof can be used or implemented by other types of radio access technologies, networks and network topologies. Therefore, the scope of the present invention is not limited to the examples described in the present invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] The accompanying drawings are included to provide a further understanding of the present invention and are incorporated into and constitute a part of this invention. The accompanying drawings illustrate embodiments of the present invention and together with the description are used to explain the principles of the present invention. It should be noted that the accompanying drawings are not necessarily drawn to scale, as some components may be shown out of scale in actual implementations in order to clearly illustrate the concepts of the present invention.

[0014] Figure 1 is an exemplary message sequence flow chart describing a case-I signaling framework of a location request (LR) procedure for a PC5 mobile-terminated (MT) according to an embodiment of the present invention.

[0015] Figure 2 is an exemplary message sequence flow chart describing a case-I signaling framework for a mobile-originated (MO) LR procedure for PC5 according to an embodiment of the present invention.

[0016] Figure 3 is an exemplary message sequence flow chart describing a case-II signaling framework for a PC5 MT LR procedure in accordance with a solution of an embodiment of the present invention.

[0017] Figure 4 is an exemplary message sequence flow chart describing a case-II signaling framework for a PC5 MO LR process in accordance with a solution of an embodiment of the present invention.

[0018] Figure 5 is a block diagram of an example communication system in accordance with an embodiment of the present invention.

[0019] Figure 6 is a flow chart of example steps according to an embodiment of the present invention.

[0020] Figure 7 is a flow chart of another exemplary process according to an embodiment of the present invention. DETAILED DESCRIPTION

[0021] The present invention discloses detailed embodiments and implementations of the claimed subject matter. However, it should be understood that the disclosed embodiments and implementations are merely illustrations of the claimed subject matter that may be embodied in various forms. However, the present invention may be embodied in many different forms and should not be construed as being limited to the exemplary embodiments and implementations set forth herein. On the contrary, these exemplary embodiments and implementations are provided to make the description of the present invention thorough and complete, and will fully convey the scope of the present invention to those skilled in the art. In the following description, details of well-known features and technologies may be omitted to avoid unnecessary confusion of the presented embodiments and implementations.

[0022] Overview

[0023] Embodiments of the present invention relate to various technologies, methods, schemes and / or solutions related to side link positioning in mobile communications, or specifically, to end-to-end side link positioning in mobile communications. According to the present invention, some possible solutions can be implemented separately or in combination. That is, although these possible solutions may be described separately below, two or more of these possible solutions may be implemented in one combination or another combination.

[0024] The current positioning framework in 5G NR generally requires network entities (including AMF, LMF, GMLC and UDM), target UE and LCS client to interact with each other in positioning operations. For example, GMLC (with the assistance of UDM) is responsible for authorizing the LCS client or application function (AF) and ensuring that the privacy of the target UE is respected. However, in an end-to-end scenario, there will be no network involvement in sidelink positioning, especially when no cellular network exists or is reachable. Therefore, there is a need to provide a signaling framework for sidelink positioning in mobile communications.

[0025] In view of the above, the present invention proposes many schemes related to sidelink positioning in mobile communications. According to the scheme of the present invention, different "GMLC / UDM UEs" are not introduced, but the necessary functions are hosted in the target UE or the location server UE. The target UE can store its own subscriber LCS privacy profile (SLPP) information. The target UE can interact directly with the location server UE. Specifically, the situation in which the necessary functions for sidelink positioning are hosted on the target UE is referred to as the case-I signaling framework in the present invention, and the situation in which the necessary functions for sidelink positioning are hosted on the location server UE is referred to as the case-II signaling framework in the present invention.

[0026] In the case-I signaling framework, the target UE hosts GMLC-like functionality (e.g., the target UE interacts directly with the LCS client). The target UE itself examines any incoming location requests addressed to it and responds only to requests that are successfully examined, so that illegal requests do not cause unnecessary signaling. It is worth noting that in the network-based scenario, the LCS client is verified whether it is authorized to retrieve the UE location as a function of the SLPP and LCS client data (e.g., location request type, client identity, etc.) stored as part of the subscription data in the UDM. The SLPP is subscriber-specific and can be updated by the UE, for example, based on user input. In contrast, in the end-to-end scenario, it is therefore expected that the target UE itself holds its own SLPP information and uses this information and LCS client data, such as location request type (e.g., positioning or ranging), accuracy and client identity, etc., to be able to determine whether the LCS client is authorized to retrieve its location. In addition, without the AMF, the target UE needs to assume the role of the AMF. In particular, if the target UE determines that it needs assistance / support from a location server UE to locate the target UE, the target UE itself can select and interact with the location server UE.

[0027] In the case-II signaling framework, the location server UE hosts GMLC / UDM-like functionality. The location server UE interacts with the LCS client, that is, it acts as a "proxy" between the LCS client and the target UE. Unlike the case-I signaling framework, in this case, the target UE does not interact directly with the LCS client. However, as with the case-I signaling framework, it is also expected that the target UE itself holds its own SLPP information, which can be queried / used by the location server UE when interacting with the LCS client. The location server UE may be able to store the SLPP information of the target UE. In addition, the LCS client needs to select a location server UE (with GMLC / UDM-like functionality) so that the LCS client can issue a location service request.

[0028] Therefore, by applying the scheme of the present invention, sidelink positioning (and ranging) can be achieved only between UEs, with a simplified and efficient signaling framework without introducing different "GMLC / UDM UEs".

[0029] Figure 1 An example scenario 100 according to an embodiment of the present invention is shown. The scenario 100 involves a target UE 110 (having GMLC-like functionality), a location server UE 120, a reference UE 130, and an LCS client 140. The scenario 100 shows an exemplary message sequence flow chart of a case-I signaling framework for a location request (LR) procedure for a PC5 mobile terminated (MT). At step 101, the LCS client 140 (e.g., in a UE) needs to retrieve location information of the target UE 110, so the LCS client 140 issues / transmits an LCS service request message to the target UE 110 over a PC5 interface to retrieve the location of the target UE 110. The LCS service request message contains LCS client data, which includes an LCS client identifier that allows the target UE 110 to identify the LCS client 140, a location request type (e.g., positioning / ranging), the accuracy of the location, etc. At step 102, upon receiving the LCS service request message, the target UE 110 verifies / determines whether the initiated LCS client 140 and its location request are authorized. The target UE may use its own stored SLPP information and the LCS client data identified in the LCS service request message to determine whether the LCS client 140 and its location request are authorized. If the target UE 110 determines that the LCS client 140 and its location request are not authorized, the target UE 110 does not respond to the LCS service request message, and the process stops or ends. Otherwise, if the target UE 110 determines that the LCS client 140 and its location request are authorized, the process continues to step 103.

[0030] At step 103, the target UE 110 determines whether it needs support from a location server UE, and if so, the target UE 110 selects the location server UE. Otherwise, if the target UE 110 determines that it does not need support from a location server UE, the process continues to step 105. Using direct discovery, the target UE 110 selects the location server UE to be performed. In order to facilitate direct discovery, the following model A discovery or model B discovery can be adopted (the definition of model A discovery and model B discovery, see 3GPP technical specification (technical specification, TS) 23.303 for details). Through model A discovery, the location server UE 120 (or notifying UE) at least notifies itself as a location server UE, and the target UE 110 (or monitoring UE) monitors such notifications. Through model B discovery, the target UE 110 (or discoverer UE) sends a request, including information that it wants to discover the location server UE (or discoverer UE). Once a location server UE is selected, direct communication is established between the target UE 110 and the selected location server UE 120 , allowing the process to continue to step 104 .

[0031] At step 104, if the target UE 110 requires support from a location server UE, the target UE 110 issues / transmits a determine location request message to the selected location server UE 120. The determine location request message contains the necessary information required by the LCS client in step 101. Otherwise, if the target UE 110 does not require support from a location server UE, this step can be skipped.

[0032] At step 105, according to the result of step 103, the target UE 110 performs UE positioning (and / or ranging) alone or with the support of the selected location server UE 120 in order to determine the location of the target UE 110. It is worth noting that, if necessary, the reference UE 130 (or multiple reference UEs) may also be called at this point to assist the target UE 110 or the location server UE 120 in determining the location of the target UE 110.

[0033] At step 106, if the determine location request message is received earlier, the location server UE 120 reports the calculated location information of the target UE 110 to the target UE 110 in a determine location response message.

[0034] At step 107, the target UE 110 reports its location information to the LCS client 140 in an LCS service response message.

[0035] Figure 2An example scenario 200 according to a solution of an embodiment of the present invention is shown. Scenario 200 includes a target UE 210 (having a GMLC-like function), a location server UE 220, a reference UE 230, and an LCS client 240. Scenario 200 shows an exemplary message sequence flow chart of a case-I signaling framework for a PC5 mobile initiated (MO) LR process. In step 201, the target UE 210 determines whether it needs support from a location server UE, and if so, the target UE 210 selects a location server UE. Otherwise, if the target UE 210 determines that it does not need support from a location server UE, step 203 is performed. Using direct discovery, the target UE 210 selects the location server UE to be performed. In order to facilitate direct discovery, the following model A discovery or model B discovery can be adopted (the definition of model A discovery and model B discovery, see 3GPP TS23.303 for details). Through model A discovery, the location server UE 220 (or referred to as a notifying UE) at least notifies itself as a location server UE, and the target UE 210 (or referred to as a monitoring UE) monitors such notifications. Through model B discovery, the target UE 210 (or discoverer UE) sends a request including information that it wishes to discover the location server UE (or discoverer UE). Once the location server UE is selected, direct communication is established between the target UE 210 and the selected location server UE 220, allowing the process to continue to step 202.

[0036] At step 202, if the target UE 210 requires support from a location server UE, the target UE 210 issues / transmits a determine location request message to the selected location server UE 220. The determine location request message contains the necessary information required for the intended location operation. Otherwise, if the target UE 210 does not require support from a location server UE, this step can be skipped.

[0037] At step 203, according to the result of step 201, the target UE 210 performs UE positioning (and / or ranging) alone or with the support of the selected location server UE 220 to determine the location of the target UE 210. It is worth noting that, if necessary, the reference UE 230 (or multiple reference UEs) may also be called at this point to assist the target UE 210 or the location server UE 220 in determining the location of the target UE 210.

[0038] At step 204, if the determine location request message was received earlier, the location server UE 220 responds to the determine location request message with a determine location response message to the target UE 210. The determine location response message contains information indicating the calculated location of the target UE 210.

[0039] At step 205, if reporting to the LCS client is required as required for the expected location operation, the target UE 210 reports its location information to the authorized LCS client 240. Otherwise, if reporting to the LCS client is not required, this step can be skipped.

[0040] At step 206 , the LCS client 240 responds with an acknowledgement of receiving the location information from the target UE 210 .

[0041] Figure 3 An example scenario 300 according to a solution of an embodiment of the present invention is shown. Scenario 300 involves a target UE 310, a location server UE 320 (having GMLC / UDM-like functionality), a reference UE 330, and an LCS client 340. Scenario 300 shows an exemplary message sequence flow chart of a case-II signaling framework for a PC5 MT LR procedure. In step 3001, an LCS client 340 (e.g., in a UE) needs to retrieve location information of a target UE 310, and therefore, the LCS client UE 340 selects a location server UE (having GMLC / UDM-like functionality). Selecting a location server UE may be performed by using direct discovery by the LCS client UE 340 and the location server UE 320. To facilitate direct discovery, the following Model A discovery or Model B discovery may be adopted (for the definition of Model A discovery and Model B discovery, see 3GPP TS23.303 for details). Through model A discovery, the location server UE 320 (or notifying UE) at least notifies itself as a location server UE, and the LCS client UE 340 (or monitoring UE) monitors such notifications. Through model B discovery, the LCS client UE 340 (or discoverer UE) issues a request including information about the location server UE (or discoverer UE) it wishes to discover. Once a location server UE is selected, direct communication is established between the LCS client UE 340 and the selected location server UE 320, allowing the process to continue to step 3002.

[0042] In step 3002, the LCS client 340 issues / transmits an LCS service request message to the location server UE 320 on the PC5 interface in order to retrieve the location of the target UE 310. The LCS service request message contains LCS client data including an LCS client identifier that allows the location server UE 320 to identify the LCS client 340, a location request type (e.g., positioning / ranging), the accuracy of the location, etc., and contains information that allows the location server UE 320 to identify the target UE 310. If the location server UE 320 holds / stores the SLPP information of the target UE 310, the process continues to step 3005. Otherwise, if the location server UE 320 does not hold / store the SLPP information of the target UE 310, the process continues to step 3003.

[0043] In step 3003, after discovering the target UE 310 and establishing direct communication with the target UE 310, the location server UE 320 issues / transmits a SLPP information request message to the target UE 310 to retrieve its SLPP information.

[0044] In step 3004 , after receiving the SLPP Information Request message, the target UE 310 replies with a SLPP Information Response message including the SLPP information of the target UE 310 .

[0045] In step 3005, the location server UE 320 verifies / determines whether the initiating LCS client 340 and its location request are authorized. The location server UE 320 uses the SLPP information of the target UE 310 and the identified LCS client data in the LCS service request message to determine whether the LCS client 340 and its location request are authorized. If the location server UE 320 determines that the LCS client and its location request are not authorized, the location server UE 320 can reject the location request from the LCS client 340 (e.g., by not responding to the LCS service request message, the process stops or ends). Otherwise, if the location server UE 320 determines that the LCS client and its location request are authorized, the process continues to step 3006.

[0046] In step 3006, the location server UE 320 forwards the authorized LCS service request to the target UE 310. If the target UE 310 determines that it needs support from a location server UE to determine its location, the process continues to step 3007. Otherwise, if the target UE 310 determines that it does not need support from a location server UE to determine its location, the process continues to step 3008.

[0047] In step 3007, the target UE 310 issues / transmits a determine location request message to the location server UE 320. The determine location request message contains necessary information required by the LCS client 340 in step 3001.

[0048] In step 3008, according to the result of step 3006, the target UE 310 performs UE positioning (and / or ranging) alone or with the support of the location server UE 320 to determine the location of the target UE 310. It is worth noting that, if necessary, the reference UE 330 (or multiple reference UEs) may also be called at this point to assist the target UE 310 or the location server UE 320 in determining the location of the target UE 310.

[0049] In step 3009, if the determine location request message is received earlier, the location server UE 320 reports the calculated location information of the UE 310 to the target UE 310 in a determine location response message.

[0050] In step 3010 , the target UE 310 reports its location information to the location server UE 320 in an LCS service response message, and the location server UE 320 in turn forwards the LCS service response message to the LCS client 340 .

[0051] Figure 4An example scenario 400 according to a solution of an embodiment of the present invention is shown. Scenario 400 includes a target UE 410, a location server UE 420 (having GMLC / UDM-like functionality), a reference UE 430, and an LCS client 440. Scenario 400 shows an exemplary message sequence flow chart of a case-II signaling framework for a PC5 MO LR process. In step 401, the target UE 410 determines whether it needs support from a location server UE, and if so, the target UE 410 selects a location server UE. Otherwise, if the target UE 410 determines that it does not need support from a location server UE, the process continues to step 403. Using direct discovery by the target UE 410 and the location server UE 420, selection of a location server UE is performed. In order to facilitate direct discovery, the following Model A discovery or Model B discovery may be adopted (for the definition of Model A discovery and Model B discovery, see 3GPP TS23.303 for details). Through model A discovery, the location server UE 420 (or notifying UE) at least notifies itself as a location server UE, and the target UE 410 (or monitoring UE) monitors such notifications. Through model B discovery, the target UE 410 (or discoverer UE) issues a request including information about the location server UE (or discoverer UE) it wishes to discover. Once a location server UE is selected, direct communication is established between the target UE 410 and the selected location server UE 420, allowing the process to continue to step 402.

[0052] In step 402, if the target UE 410 requires support from a location server UE, the target UE 410 issues / transmits a determine location request message to the selected location server UE 420. The determine location request message contains the necessary information required for the intended location operation. Otherwise, if the target UE 410 does not require support from a location server UE, this step can be skipped.

[0053] In step 403, according to the result of step 401, the target UE 410 performs UE positioning (and / or ranging) alone or with the support of the selected location server UE 420 to determine the location of the target UE 410. It is worth noting that, if necessary, the reference UE 430 (or more reference UEs) may also be called at this point to assist the target UE 410 or the location server UE 420 in determining the location of the target UE 410.

[0054] In step 404, if the determine location request message is received earlier, the location server UE 220 replies with a determine location response message to the target UE 410. The determine location response message contains information indicating the calculated location of the target UE 410.

[0055] In step 405, if reporting to the LCS client is required as required for the intended location operation, the target UE 410 reports its location information report to the location server UE 420, along with the necessary information to allow identification of the LCS client 340. The target UE 410 includes its SLPP information, as well as LCS client data that allows the location server UE 420 to determine whether the LCS client 440 is authorized. If necessary, the location server UE 420 forwards the location information of the target UE 410 to the authorized LCS client 440. If reporting to the LCS client is not required, this step can be skipped.

[0056] In step 406 , the LCS client 440 replies with an acknowledgement of receiving the location information from the location server UE 420 , and the location server UE 420 in turn forwards the acknowledgement to the target UE 410 .

[0057] Illustrative Implementation

[0058] Figure 5 An example communication system 500 having at least an example device 510 and an example device 520 according to an embodiment of the present invention is shown. Each of the devices 510 and 520 can perform various functions to implement the schemes, techniques, steps and methods related to side link positioning in mobile communications described in the present invention, including the above-mentioned scenarios / schemes and steps 600 and 700 described below.

[0059] Each of the apparatus 510 and the apparatus 520 may be part of an electronic device, which may be a UE (e.g., a UE operating as a target UE or a location server UE), such as a portable or mobile device, a wearable device, an in-vehicle device or vehicle, a wireless communication device, or a computing device. For example, each of the apparatus 510 and the apparatus 520 may be implemented in a smart phone, a smart watch, a personal digital assistant, an electronic control unit (ECU) in a vehicle, a digital camera, or a computing device such as a tablet, a laptop, or a notebook computer. Each of the apparatus 510 and the apparatus 520 may also be part of a machine-type device, which may be an IoT device, such as a fixed or stationary device, a home device, a roadside unit (RSU), a wired communication device, or a computing device. For example, each of the apparatus 510 and the apparatus 520 may be implemented in a smart thermostat, a smart refrigerator, a smart door lock, a wireless speaker, or a home control center.

[0060] In some embodiments, each of the apparatus 510 and the apparatus 520 may be implemented in the form of one or more integrated circuit (IC) chips, such as, but not limited to, one or more single-core processors, one or more multi-core processors, one or more complex instruction set computing (CISC) processors, or one or more reduced instruction set computing (RISC) processors. In the various schemes described above, each of the apparatus 510 and the apparatus 520 may be implemented in a UE or as a UE. Each of the apparatus 510 and the apparatus 520 may include Figure 5 At least some of those components shown in the drawings, for example, processor 512 and processor 522, respectively. Each of apparatus 510 and apparatus 520 may further include one or more other components (e.g., an internal power supply, a display device, and / or a user interface device) that are not related to the proposed solution of the present invention, and, therefore, for the sake of brevity, these components of apparatus 510 and apparatus 520 are neither shown in the drawings nor in the drawings. Figure 5 It is not shown in the figure and is not described below.

[0061] On the one hand, each of processor 512 and processor 522 can be implemented in the form of one or more single-core processors, one or more multi-core processors, or one or more CISC or RISC processors. That is, even if the singular term "a processor" is used in the present invention to refer to processor 512 and processor 522, each of processor 512 and processor 522 can include multiple processors in some embodiments and a single processor in other embodiments. On the other hand, each of processor 512 and processor 522 can be implemented in the form of hardware (and optional firmware), with electronic components, including, for example but not limited to, one or more transistors, one or more diodes, one or more capacitors, one or more resistors, one or more inductors, one or more memristors and / or one or more varactors, which are configured and set to implement specific purposes according to the present invention. In other words, in at least some embodiments, each of processor 512 and processor 522 is a special-purpose machine that is specially designed, set and configured to perform specific tasks, including tasks related to side link positioning in mobile communications according to various embodiments of the present invention.

[0062] In some embodiments, the device 510 may further include a transceiver 516, coupled to the processor 512, and capable of wirelessly transmitting and receiving data. In some embodiments, the transceiver 516 may be capable of wirelessly communicating with different types of UE / wireless networks of different radio access technologies (RAT). In some embodiments, the transceiver 516 may be equipped with multiple antenna ports (not shown), for example, four antenna ports. That is, the transceiver 516 may be equipped with multiple transmit antennas and multiple receive antennas for multiple-input multiple-output (MIMO) wireless communication. In some embodiments, the device 520 may further include a transceiver 526, coupled to the processor 522, and capable of wirelessly transmitting and receiving data. In some embodiments, the transceiver 526 may be capable of wirelessly communicating with different types of UE / wireless networks of different RATs. In some embodiments, the transceiver 526 may be equipped with multiple antenna ports (not shown), for example, four antenna ports. That is, the transceiver 526 may be equipped with multiple transmit antennas and multiple receive antennas for MIMO wireless communication.

[0063] In some embodiments, the apparatus 510 may further include a memory 514 coupled to the processor 512 and accessible to the processor 512 and storing data therein (e.g., SLPP information of the target UE). In some embodiments, the apparatus 520 may further include a memory 524 coupled to the processor 522 and accessible to the processor 522 and storing data therein. Each of the memory 514 and the memory 524 may include a random-access memory (RAM), such as a dynamic RAM (DRAM), a static RAM (SRAM), a thyristor RAM (T-RAM), and / or a zero-capacitor RAM (Z-RAM). Optionally or additionally, each of the memory 514 and the memory 524 may include a read-only memory (ROM), such as a shielded ROM, a programmable ROM (PROM), an erasable programmable ROM (EPROM), and / or an electrically erasable programmable ROM (EEPROM). Optionally or additionally, each of the memory 514 and the memory 524 may include a non-volatile random-access memory (NVRAM), such as a flash memory, a solid-state memory, a ferroelectric RAM (FeRAM), a magnetoresistive RAM (MRAM), and / or a phase change memory. Optionally or additionally, each of the memory 514 and the memory 524 may include a universal integrated circuit card (UICC).

[0064] Each of the apparatus 510 and the apparatus 520 may be a communication entity capable of communicating with each other using various proposed schemes according to the present invention. For illustrative purposes and not limited thereto, the following provides a capability description of the apparatus 510 as a target UE (e.g., target UE 110 / 210 / 310 / 410) and the apparatus 520 as a location server UE (e.g., location server UE 120 / 220 / 320 / 420).

[0065] Under various schemes proposed according to the present invention regarding sidelink positioning in mobile communications, the processor 512 of the device 510 implemented in the target UE or implemented as the target UE can determine whether the target UE needs support from a location server UE during the sidelink LR process. In addition, in the case where the target UE needs support from a location server UE, the processor 512 can select the location server UE through the transceiver 516. In addition, the processor 512 can perform UE positioning through the transceiver 516 to determine the location of the target UE with or without the support of the selected location server UE.

[0066] In some embodiments, in the case where the target UE requires support from a location server UE, the processor 512 may also transmit a first request for determining the location of the target UE to the selected location server UE via the transceiver 516. UE positioning may be performed in response to the first request. In addition, the processor 512 may receive a first response from the selected location server UE via the transceiver 516, the first response including information indicating the location of the target UE.

[0067] In some embodiments, the sidelink LR process is initiated by the LCS client, and the processor 512 may also receive a second request for the location of the target UE from the LCS client via the transceiver 516, and determine whether the LCS client and the second request are authorized. In the case where the LCS client and the second request are authorized, the location server UE selection is performed. In addition, the processor 512 may transmit a second response to the LCS client via the transceiver 516, and the second response includes information indicating the location of the target UE.

[0068] In some embodiments, the second request may include LCS client data including at least one of an identification of the LCS client, a type of location request, and an accuracy of the location of the target UE.

[0069] In some embodiments, based on the LCS client data in the second request and the SLPP information of the target UE, determining whether the LCS client and the second request are authorized may be performed.

[0070] In some embodiments, the sidelink LR process is initiated by the target UE, and the processor 512 may also transmit a report including information indicating the location of the target UE to the authorized LCS client via the transceiver 516. In addition, the processor 512 may receive an acknowledgement of receipt of the report from the authorized LCS client via the transceiver 516.

[0071] In some embodiments, location server UE selection may be performed using direct discovery including one of: receiving, via the transceiver 516, a notification from a selected location server UE that its service is a location server UE; and transmitting, via the transceiver 516, a third request for discovering location server UEs to the selected location server UE.

[0072] In some embodiments, UE positioning may include invoking one or more reference UEs to assist the target UE or the selected location server UE in determining the location of the target UE.

[0073] According to other proposed solutions for sidelink positioning in mobile communications of the present invention, a processor 522 of an apparatus 520 implemented in or as a location server UE performs location server UE selection with a target UE or LCS client in a sidelink LR process via a transceiver 526. In addition, the processor 522 may perform UE positioning via the transceiver 526 to determine the location of the target UE if the target UE requires support from a location server UE.

[0074] In some implementations, in the case where the target UE requires support from a location server UE, the processor 522 may also receive a first request for determining the location of the target UE from the target UE via the transceiver 526, and UE positioning may be performed in response to the first request. In addition, the processor 522 may transmit a first response to the target UE via the transceiver 526, the first response including information indicating the location of the target UE.

[0075] In some embodiments, the sidelink LR process is initiated by the LCS client, and the processor 522 may also receive a second request for the location of the target UE from the LCS client through the transceiver 526, and determine whether the LCS client and the second request are authorized. In addition, if the LCS client and the second request are authorized, the processor 522 may forward the second request to the target UE through the transceiver 526. In addition, the processor 522 may receive a second response from the target UE through the transceiver 526, and the second response includes information indicating the location of the target UE. The processor 522 may forward the second response to the LCS client through the transceiver 526.

[0076] In some embodiments, the sidelink LR procedure is initiated by the LCS client, and the processor 522, in response to the second request, may also transmit a third request for SLPP information of the target UE to the target UE via the transceiver 526. In addition, the processor 522 may receive a third response from the target UE via the transceiver 526, the third response including the SLPP information of the target UE. Based on the LCS client data in the second request and the SLPP information of the target UE, determining whether the LCS client and the second request are authorized may be performed.

[0077] In some embodiments, the sidelink LR process is initiated by the target UE, and the processor 522 may also forward a report received from the target UE to the LCS client via the transceiver 526, which may include information indicating the location of the target UE. In addition, the processor 522 may forward a confirmation received from the LCS client to the target UE via the transceiver 526. The confirmation is used to confirm receipt of the report.

[0078] Demonstration process

[0079] Figure 6 An exemplary process 600 is shown in accordance with an embodiment of the present invention. Process 600 may represent an aspect of implementing the various proposed designs, concepts, schemes, systems and methods described above, in part or in whole, including those described above. More specifically, process 600 may represent an aspect of proposed concepts and schemes regarding sidelink positioning in mobile communications, and more specifically, regarding the case-IPC5 MT / MO LR process. Process 600 may include one or more operations, actions, or functions as shown in one or more of blocks 610, 620, and 630. Although shown as discrete blocks, corresponding blocks of process 600 may be split into additional blocks, combined into fewer blocks, or eliminated, depending on the desired implementation. In addition, the blocks / sub-blocks of process 600 may be arranged in blocks. Figure 6 600 may be performed in the order shown, or, optionally, in a different order. In addition, one or more blocks / sub-blocks of process 600 may be repeatedly performed. Process 600 may be implemented by or in apparatus 510 and apparatus 520 and any variants thereof. For illustrative purposes only and without limiting the scope, process 600 is described below in the context of apparatus 510 as a target UE (e.g., target UE 110 / 210) with GMLC-like functionality and apparatus 520 as a location server UE (e.g., location server UE 120 / 220). Process 600 may start from block 610.

[0080] At block 610 , process 600 may include processor 512 of apparatus 510 operating in or as a target UE determining whether the target UE requires support from a location server UE during a sidelink LR procedure. Process 600 may continue from block 610 to block 620 .

[0081] At block 620, process 600 may include, if the target UE requires support from a location server UE, processor 512 selecting, via transceiver 516, a location server UE (eg, device 520). Process 600 may continue from block 620 to block 630.

[0082] At block 630, process 600 may include processor 512 performing UE positioning via transceiver 516 to determine the location of the target UE with or without support from the selected location server UE.

[0083] In some embodiments, the process 600 may further include, in the case where the target UE requires support from a location server UE, the processor 512 transmitting a first request for determining the location of the target UE to the selected location server UE via the transceiver 516. UE positioning may be performed in response to the first request. In addition, the process 600 may include the processor 512 receiving a first response from the selected location server UE via the transceiver 516, the first response including information indicating the location of the target UE.

[0084] In some embodiments, the sidelink LR process is initiated by the LCS client, and the process 600 may further include the processor 512 receiving a second request for the location of the target UE from the LCS client via the transceiver 516, and determining whether the LCS client and the second request are authorized. In the case where the LCS client and the second request are authorized, location server UE selection may be performed. In addition, the process 600 may include the processor 512 transmitting a second response to the LCS client via the transceiver 516, the second response including information indicating the location of the target UE.

[0085] In some embodiments, the second request may include LCS client data including at least one of an identification of the LCS client, a type of location request, and an accuracy of the location of the target UE.

[0086] In some embodiments, based on the LCS client data in the second request and the SLPP information of the target UE, determining whether to authorize the LCS client and the second request may be performed.

[0087] In some embodiments, the sidelink LR process is initiated by the target UE, and the process 600 may further include the processor 512 transmitting a report including information indicating the location of the target UE to the authorized LCS client via the transceiver 516. In addition, the process 600 may include the processor 512 receiving, via the transceiver 516, an acknowledgement of receipt of the report from the authorized LCS client.

[0088] In some embodiments, location server UE selection may be performed using direct discovery including one of: receiving a notification from a selected location server UE that it serves as a location server UE via the transceiver 516; and transmitting a third request for discovering the location server UE to the selected location server UE via the transceiver 516.

[0089] In some embodiments, UE positioning may include invoking one or more reference UEs to assist the target UE or the selected location server UE in determining the location of the target UE.

[0090] Figure 7 An exemplary process 700 is shown in accordance with an embodiment of the present invention. Process 700 may represent an aspect of implementing the various proposed designs, concepts, schemes, systems and methods described above, in part or in whole, including those described above. More specifically, process 700 may represent an aspect of proposed concepts and schemes regarding sidelink positioning in mobile communications, and more specifically, regarding the case-IIPC5 MT / MO LR process. Process 700 may include one or more operations, actions, or functions as shown in one or more of blocks 710 and 720. Although shown as discrete blocks, corresponding blocks of process 700 may be split into additional blocks, combined into fewer blocks, or eliminated, depending on the desired implementation. In addition, the blocks / sub-blocks of process 700 may be arranged in blocks. Figure 7 700 may be performed in the order shown, or, optionally, in a different order. In addition, one or more blocks / sub-blocks of process 700 may be repeatedly performed. Process 700 may be implemented by or in apparatus 510 and apparatus 520 and any variants thereof. For illustrative purposes only and without limiting the scope, process 700 is described below in the context of apparatus 510 as a target UE (e.g., target UE 310 / 410) and apparatus 520 as a location server UE with GMLC / UDM-like functionality (e.g., location server UE 320 / 420). Process 700 may start from block 710.

[0091] At block 710, process 700 may include processor 522 of apparatus 520 implemented in or as a target UE, performing selection of a location server UE with the target UE (e.g., apparatus 510) or an LCS client during a sidelink LR procedure. Process 700 may proceed from block 710 to block 720.

[0092] At block 720, process 700 may include processor 522 performing UE positioning via transceiver 526 to determine the location of the target UE if the target UE requires support from a location server UE.

[0093] In some embodiments, in the case where the target UE requires support from a location server UE, the process 700 may further include the processor 522 receiving a first request for determining the location of the target UE from the target UE via the transceiver 526. UE positioning may be performed in response to the first request. In addition, the process 700 may include the processor 522 transmitting a first response to the target UE via the transceiver 526, the first response including information indicating the location of the target UE.

[0094] In some embodiments, the sidelink LR process is initiated by the LCS client, and the process 700 may further include the processor 522 receiving a second request for the location of the target UE from the LCS client via the transceiver 526, and determining whether the LCS client and the second request are authorized. In addition, in the case where the LCS client and the second request are authorized, the process 700 may include the processor 522 forwarding the second request to the target UE via the transceiver 526. In addition, the process 700 may include the processor 522 receiving a second response from the target UE via the transceiver 526, the second response including information indicating the location of the target UE. The process 700 may further include the processor 522 forwarding the second response to the LCS client via the transceiver 526.

[0095] In some embodiments, the sidelink LR process is initiated by the LCS client, and the process 700 may further include the processor 522 transmitting, in response to the second request, to the target UE via the transceiver 526, a third request for subscriber LCS privacy profile (SLPP) information for the target UE. In addition, the process 700 may include the processor 522 receiving a third response from the target UE via the transceiver 526, the third response including the SLPP information of the target UE. Based on the LCS client data in the second request and the SLPP information of the target UE, determining whether the LCS client and the second request are authorized may be performed.

[0096] In some embodiments, the sidelink LR process is initiated by the target UE, and the process 700 may further include the processor 522 forwarding the report received from the target UE to the LCS client via the transceiver 526. The report may include information indicating the location of the target UE. In addition, the process 700 may include the processor 522 forwarding the confirmation received from the LCS client to the target UE via the transceiver 526. The confirmation is used to confirm the receipt of the report.

[0097] Additional Notes

[0098] The subject matter described in the present invention sometimes illustrates different components contained in or connected to different other components. It should be understood that this depicted architecture is only an example, and many other architectures that realize the same function can actually be implemented. In a conceptual sense, any arrangement of components that realize the same function is effectively "associated" to achieve the desired function. Therefore, no matter how the architecture or intermediate components are, the present invention is combined to achieve any two components of a specific function and can be regarded as "associated" to each other, so that the desired function is achieved. Similarly, any two components so associated can also be regarded as "workingly connected" or "workingly coupled" to each other to achieve the desired function, and any two components that can be so associated can also be regarded as "workingly coupleable" to each other to achieve the desired function. Specific examples of coupling at work include, but are not limited to: physically matching and / or physically interactive components and / or wirelessly interactive and / or wirelessly interactive components and / or logically interactive and / or logically interactive components.

[0099] Further, with respect to the extensive use of any plural and / or singular terms of the present invention, those skilled in the art may convert from plural to singular and / or from singular to plural as appropriate for context and / or application. For the sake of clarity, the present invention may explicitly set forth various singular / plural reciprocities.

[0100] Moreover, those skilled in the art will understand that, in general, the terms used in the present invention and especially in the appended claims (e.g., the body of the appended claims) are generally intended to be "open" terms (e.g., the term "including" should be interpreted as "including but not limited to", the term "having" should be interpreted as "having at least", the term "comprising" should be interpreted as "including but not limited to", etc.). Those skilled in the art will also understand that if a specific number of claim recitations is intentionally introduced, such intent will be explicitly recited in the claim, and in the absence of such a recitation, no such intent is present. For example, as an aid to understanding, the appended claims of the present invention may contain the use of the introductory phrases "at least one" and "one or more" to introduce claim recitations. However, the use of such phrases should not be interpreted as implying that the introduction of a claim recitation by the indefinite article "a" or "an" will include any particular claim of such introduced claim recitation limited to embodiments containing only one such recitation, even when the same claim includes the introductory phrases "one or more" or "at least one" and an indefinite article such as "a" or "an" (e.g., "a" and / or "an" should be interpreted as meaning "at least one" or "one or more"); the same applies to the use of definite articles used to introduce claim recitations. In addition, even if a specific number of introduced claim recitations is explicitly recited, those skilled in the art will recognize that such recitation should be interpreted as meaning at least the recited number (e.g., the unmodified recitation of "two recitations" means at least two recitations, or two or more recitations, in the absence of other modifiers). Furthermore, in those cases where a convention similar to "at least one of A, B, and C, etc." is used, generally, such interpretation will be understood by those skilled in the art to mean, for example, that "a system having at least one of A, B, and C" will include, but is not limited to, systems having A alone, B alone, C alone, A and B together, A and C together, B and C together, and / or A, B, and C together, etc. In those cases where a convention similar to "at least one of A, B, or C, etc." is used, generally, such interpretation will be understood by those skilled in the art to mean, for example, that "a system having at least one of A, B, or C" will include, but is not limited to, systems having A alone, B alone, C alone, A and B together, A and C together, B and C together, and / or A, B, and C together, etc. Those skilled in the art will also understand that any transitional words and / or phrases that actually present two or more alternatives, whether in the specification, claims, or drawings, should be understood to contemplate the possibility of including one, either, or both of these items. For example, the phrase "A or B" will be understood to include the possibilities of "A" or "B" or "A and B."

[0101] According to the foregoing, it will be understood that the present invention has been described various embodiments of the present invention for the purpose of illustration, and various modifications can be made without departing from the scope and spirit of the present invention. Therefore, the various embodiments disclosed by the present invention are not intended to be limiting, and the true scope and spirit are represented by the appended claims.

Claims

1. A method comprising: A processor of the device operating as a target user equipment (UE) determines whether the target UE requires support from a location server UE in a sidelink location request (LR) procedure; The processor selects a location server UE if the target UE requires support from a location server UE; as well as The processor performs UE positioning to determine the location of the target UE with or without UE support from a selected location server.

2. The method according to claim 1, wherein: Further including: In case the target UE requires support from a location server UE, the processor transmits a first request to the selected location server UE for determining the location of the target UE, wherein the UE positioning is performed in response to the first request; and The processor receives a first response from the selected location server UE, the first response including information indicating a location of the target UE.

3. The method according to claim 1, wherein: The side link LR process is initiated by a location service (LCS) client, and the method further includes: The processor receives a second request for the location of the target UE from the LCS client; The processor determines whether the LCS client and the second request are authorized, wherein if the LCS client and the second request are authorized, selecting the location server UE is performed; and The processor transmits a second response to the LCS client, the second response including information indicating the location of the target UE.

4. The method according to claim 3, wherein: The second request includes LCS client data including at least one of an identification of the LCS client, a type of location request, and an accuracy of the location of the target UE.

5. The method according to claim 4, wherein: Based on the LCS client data in the second request and the subscriber LCS privacy profile (SLPP) information of the target UE, it is determined whether the LCS client and the second request are authorized to be executed.

6. The method according to claim 1, wherein: The side link LR process is initiated by the target UE, and the method further includes: The processor transmits a report including information indicating the location of the target UE to an authorized LCS client; and The processor receives an acknowledgement of receipt of the report from the authorized LCS client.

7. The method according to claim 1, wherein: Selection of the location server UE is performed using direct discovery including one of the following: The processor receives a notification from the selected location server UE that its service is a location server UE; and The processor transmits a third request for discovering a location server UE to the selected location server UE.

8. The method according to claim 1, wherein: The UE positioning includes calling one or more reference UEs to assist the target UE or the selected location server UE in determining the location of the target UE.

9. A method comprising: A processor of the apparatus operating as a location server user equipment (UE) performs selection of a location server UE in a sidelink location request (LR) procedure with a target UE or a location service (LCS) client; as well as In case the target UE requires support from a location server UE, the processor performs UE positioning to determine the location of the target UE.

10. The method according to claim 9, wherein: Further including: In case the target UE requires support from a location server UE, the processor receives a first request from the target UE for determining the location of the target UE, wherein the UE positioning is performed in response to the first request; and The processor transmits a first response to the target UE, the first response including information indicating a location of the target UE.

11. The method according to claim 9, wherein: The side link LR process is initiated by the LCS client, and the method further includes: The processor receives a second request for the location of the target UE from the LCS client; The processor determines whether the LCS client and the second request are authorized; If the LCS client and the second request are authorized, the processor forwards the second request to the target UE; The processor receives a second response from the target UE, the second response including information indicating a location of the target UE; and The processor forwards the second response to the LCS client.

12. The method according to claim 11, wherein: The side link LR process is initiated by the LCS client, and the method further comprises: The processor transmits, in response to the second request, to the target UE a third request for subscriber LCS privacy profile (SLPP) information for the target UE; and The processor receives a third response from the target UE, the third response including SLPP information of the target UE; Wherein, based on the LCS client data in the second request and the SLPP information of the target UE, it is determined whether to authorize the LCS client and the second request to be executed.

13. The method according to claim 9, wherein: The side link LR process is initiated by the target UE, and the method further includes: The processor forwards a report received from the target UE to the LCS client, wherein the report includes information indicating a location of the target UE; and The processor forwards a confirmation received from the LCS client to the target UE, wherein the confirmation is used to confirm receipt of the report.

14. An apparatus, operating as a target user equipment (UE), the apparatus comprising: a transceiver that wirelessly communicates with one or more UEs during operation; as well as A processor is communicatively coupled to the transceiver, the processor performing operations during operation including: determining whether the target UE requires support from a location server UE during a sidelink location request (LR) process; In case the target UE requires support from a location server UE, selecting, by the transceiver, a location server UE; and UE positioning is performed by the transceiver to determine the location of the target UE with or without UE support from a selected location server.

15. The device according to claim 14, wherein: The processor further performs operations during operation including: In case the target UE requires support from a location server UE, transmitting, by a transceiver, a first request for determining the location of the target UE to a selected location server UE, wherein positioning of the UE is performed in response to the first request; and A first response is received by the transceiver from the selected location server UE, the first response including information indicating the location of the target UE.

16. The device according to claim 14, wherein: The side link LR process is initiated by a location service (LCS) client, and the processor further performs operations in the operating device, including: receiving, by the transceiver, from the LCS client, a second request for the location of the target UE; determining whether the LCS client and the second request are authorized, wherein if the LCS client and the second request are authorized, selecting the location server UE is performed; and A second response is transmitted to the LCS client by the transceiver, the second response including information indicating the location of the target UE.

17. The device according to claim 16, wherein: The second request includes LCS client data, wherein the LCS client data includes at least one of an identification of the LCS client, a type of location request, and an accuracy of the location of the target UE; as well as Based on the LCS client data in the second request and the subscriber LCS privacy profile (SLPP) information of the target UE, it is determined whether to authorize the LCS client and the second request to be executed.

18. The device according to claim 14, wherein: The sidelink LR process is initiated by the target UE, and the processor further performs operations during operation, including: transmitting, by the transceiver, to an authorized LCS client, a report including information indicating a location of the target UE; as well as An acknowledgement of receipt of the report is received from the authorized LCS client by the transceiver.

19. The device according to claim 14, wherein: Selection of the location server by the UE is performed using direct discovery including one of the following: receiving, by the transceiver, a notification from the selected location server UE that its service is a location server UE; and A third request for discovering a location server UE is transmitted to the selected location server UE through the transceiver.

20. The device according to claim 14, wherein: The UE positioning includes calling one or more reference UEs to assist the target UE or the selected location server UE in determining the location of the target UE.

Images